hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
d4e1d4d5380d2442586fde111644eacb | 101 299 | 5.2.2.5 Transfer capability | This parameter is used to report to the NS user entity the current transfer capacity available for a BVC, in terms of bandwidth. This parameter may be set to any value from "0" (zero) to the maximum bandwidth provided by the complete set of NS-VCs associated to the BVC. |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 5.2.2.6 NS affecting cause | This parameter is used to indicate to the NS user entity the reason which caused the NS-STATUS-Indication primitive to be used. The cause values are: a) NS-VC failure: a failure is affecting one or more NS-VCs, the NS is still available. b) NS-VC recovery: one or more NS-VCs which were in failure are available again. c... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 6 Sub-Network Service protocol | |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 6.1 Frame Relay support of the Sub-Network Service protocol | |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 6.1.1 Overview | Frame Relay shall be the network used on the Gb interface. The Gb interface may consist of direct point-to-point connections between the BSS and the SGSN, or an intermediate Frame Relay network may be placed between both ends of the Gb interface. Other intermediate equipments may be traversed. Several configurations ar... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 6.1.2 Network configuration | The Gb interface is a User-to-Network (UNI) interface, as defined in FRF 1.1 [6]. Two configurations are possible, either a direct link configuration or PVC(s) via a Frame Relay network. Annex A shows an example of each type of configuration. In case of point-to-point connections, the BSS shall be considered as the use... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 6.1.3 Services expected from layer 1 | In the context of Frame Relay, the physical link is referred to as the bearer channel. The Frame Relay protocol shall be run across permanently reserved bearer channels on the Gb interface, see GSM 08.14 [4]. |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 6.1.4 Options selected from FRF 1.1 | |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 6.1.4.1 Support of DL-CONTROL sub-layer | No end-to-end DL-CONTROL sub-layer shall be implemented on the Gb interface. |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 6.1.4.2 Frame length | The default maximum information field size of 1600 octets shall be supported on the Gb interface. Maximum information field sizes greater than 1600 octets may be agreed to between Frame Relay network operators and users at subscription time. |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 6.1.4.3 Congestion control procedures | Congestion control is defined in FRF 1.1 [6] and consists of congestion avoidance and congestion recovery mechanisms. Congestion control on the Gb interface consists of congestion avoidance based on the DE bit and on explicit notifications via the FECN and BECN bits within the address field of the Frame Relay frame. Co... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 6.1.4.3.1 DE bit usage | The BSS and the SGSN shall always set the DE bit to 0 (zero). |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 6.1.4.3.2 FECN and BECN bit usage | Setting of the FECN and BECN bits: The FECN and BECN bits shall be set to 0 by the BSS and the SGSN. Reaction upon receipt of FECN or BECN marked frames: The reaction of the BSS and the SGSN upon reception of FECN or BECN marked frames is implementation dependent. ETSI ETSI TS 101 299 V7.1.0 (1999-07) 18 (GSM 08.16 ver... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 6.1.4.4 Signalling procedures | ITU-T Revised Q.933 [11] annex A or T1.617 [16] for PCS1900 procedures shall be implemented at the BSS and the SGSN sides as recommended in FRF 1.1 [6] clause 2.3. On the Gb interface, these procedures shall be initiated by the user side of the UNI, reverse procedures shall not be used. Only periodic polling shall be u... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 6.1.4.5 C/R bit usage | The C/R bit shall not be used and shall be set to 0 by the sending entity. It shall not be checked by the receiving entity. |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 6.1.5 Abnormal conditions | Upon detection of the unavailability of a PVC by the Frame Relay entity or when a PVC becomes available again, the Network Service Control entity shall be informed. Unavailability cases are described in Recommendations ITU-T Q.922 [9] or T1.618 [17] for PCS1900 and ITU-T Q.933 [11] annex A or T1.617 [16] for PCS1900. |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 7 Network Service Control protocol | |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 7.1 Procedures for the transmission of NS SDUs | NS SDUs are transmitted in unacknowledged mode across the Gb interface by means of an NS-UNITDATA PDU. The NS-UNITDATA PDU is used in both BSS-to-SGSN and SGSN-to-BSS directions. |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 7.1.1 Abnormal Conditions | If the BSS receives an NS-UNITDATA PDU including a BVCI not associated to the NS-VC where the PDU was received, the BSS shall return an NS-STATUS PDU on that NS-VC, cause "BVC unknown on that NSE". Depending on the implementation, the BSS may then ignore the BVCI and treat the rest of the NS-UNITDATA PDU. |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 7.2 Blocking / unblocking procedures | When a BSS (or SGSN) wishes to block an NS-VC between a BSS and SGSN, the following shall be performed: - The transmitting side at the BSS (or SGSN) shall mark the NS-VC as blocked and shall inform the load sharing function. This results in the redistribution of NS-UNIDATA PDUs to other unblocked NS-VCs of the same gro... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 7.2.1 Abnormal Conditions | If an NS-BLOCK-ACK PDU is not received for an NS-BLOCK PDU within Tns-block seconds, then the NS-BLOCK PDU procedure shall be repeated a maximum of NS-BLOCK-RETRIES attempts. After NS-BLOCK-RETRIES unsuccessful retry attempts the procedure is stopped and the O&M system is informed that the blocking procedure has failed... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 7.3 Reset procedure | The reset procedure shall be used when a new NS-VC is set-up between a BSS and an SGSN, after processor re-start, after failure recovery or any local event restoring an existing NS-VC in the dead state or when its state is undetermined between remote NS entities. Upon completion of the reset procedure, the successfully... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 7.3.1 Abnormal conditions | If the sending entity of an NS-RESET PDU receives no NS-RESET-ACK PDU before timer Tns-reset expires the corresponding NS-VCs shall remain blocked and dead and the entire reset procedure shall be repeated. If the reset procedure remains unsuccessful for a period of time established by the operator, the O&M system shall... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 7.4 Test procedure | The test procedure shall be used when a BSS (or SGSN) wishes to check that end-to-end communication with its peer entity exists on an NS-VC. Both sides of the Gb interface may initiate this procedure independently from each other. This procedure shall be initiated upon successful completion of the reset procedure (as s... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 7.4.1 Abnormal conditions | If an NS-ALIVE-ACK PDU is received when not expected, it shall be ignored. If no NS-ALIVE-ACK PDU is received before Tns-alive expires, the test procedure shall be repeated a maximum of NS-ALIVE-RETRIES attempts. After NS-ALIVE-RETRIES unsuccessful retry attempts, the procedure is stopped, the NS-VC is marked as dead a... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 7.5 Procedure for error reporting | The reporting of protocol errors to the remote entity is done by means of the NS-STATUS PDU, as further described in the rest of this Technical Specification. Upon receipt of an NS-STATUS PDU, the O&M system is informed. Further actions of the O&M system are out of the scope of this Technical Specification. |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 7.5.1 Abnormal conditions | If an error is detected in a received NS-STATUS PDU, then the error shall not be reported to the remote NS entity. |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 8 General protocol error handling | This clause is not applicable to the Sub-Network Service protocol. The following "General case" subclause applies unless otherwise stated in the "Special cases" subclause. |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 8.1 General case | This clause specifies procedures for the handling of unknown, unforeseen, and erroneous protocol data by the receiving entity. These procedures are called "error handling procedures", but in addition to providing recovery mechanisms for error situations they define a compatibility mechanism for future extensions of the... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 8.1.1 Presence requirements of Information Elements | There are three different presence requirements (M, C, or O) for an IE within a given PDU: - M ("Mandatory") means that the IE shall be included by the sending side, and that the receiver diagnoses a "missing essential IE" error when detecting that the IE is not present. - C ("Conditional") means: ETSI ETSI TS 101 299 ... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 8.1.2 Erroneous events | The following events shall be regarded as errors by the recipient and shall be treated as specified below. Certain types of error shall be reported to the sending side, in that case the erroneous PDU and the error cause shall be returned to the sending side by means of the appropriate error reporting PDU. The following... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 8.1.3 Non-erroneous events | The following events shall not be regarded as errors by the recipient: 1) spare bits with an unexpected value in any information element; 2) the use of additional octets in any information element with a length indicator, that is: when the indicated length is greater than defined in the relevant protocol specification ... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 8.1.4 Other events | The following events should be treated on a case by case basis and the outcome may depend upon the capabilities of the recipient. 1) The recipient may accept PDUs that contain information elements that do not appear to be in the correct sequence. Elements that occur more than once in a PDU shall be assumed to have been... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 8.2 Special cases | In case of conflict between this subclause and the above "General case" subclause, this subclause takes precedence. In case of conflict between this subclause and the specific "Abnormal conditions" subclauses in chapter "Network Service Control protocol", the "Abnormal conditions" subclauses take precedence over this "... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 8.2.1 Deviations from the "General case" subclause | The Cause information element (see subclauses "General PDU definitions and contents" and "General information elements coding") shall be considered as a non-essential information element even when mandatory in a PDU. |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 8.2.2 Error reporting | The NS-STATUS PDU shall be used to report error to the remote NS entity, see subclause "Procedure for error reporting". The NS-STATUS PDU shall never be used to report an error detected in a received NS-STATUS PDU. |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 9 General PDU definitions and contents | This clause is not applicable to the Sub-Network Service protocol. |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 9.1 General structure of a PDU | This subclause defines the general structure of the PDUs on the Gb interface. The general PDU structure is composed of: a) a PDU type information element; and b) other information elements, as required. ETSI ETSI TS 101 299 V7.1.0 (1999-07) 25 (GSM 08.16 version 7.1.0 Release 1998) The PDU type IE occupies the first oc... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 9.2 Network Service Control PDUs | The Network Service Control PDUs are also referred to as NS PDUs in the rest of this Technical Specification. |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 9.2.1 NS-ALIVE | This PDU is used to test an NS-VC. PDU type: NS-ALIVE Direction: BSS to SGSN, SGSN to BSS Table 1/GSM 08.16: NS-ALIVE PDU contents Information element Reference Presence Format Length PDU type M V 1 ETSI ETSI TS 101 299 V7.1.0 (1999-07) 26 (GSM 08.16 version 7.1.0 Release 1998) |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 9.2.2 NS-ALIVE-ACK | This PDU acknowledges a received NS-ALIVE PDU and is sent on the NS-VC where the NS-ALIVE PDU was received. PDU type: NS-ALIVE-ACK Direction: SGSN to BSS, BSS to SGSN Table 2/GSM 08.16: NS-ALIVE-ACK PDU contents Information element Reference Presence Format Length PDU type M V 1 |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 9.2.3 NS-BLOCK | This PDU indicates that an NS-VC shall be blocked at the recipient entity. PDU type: NS-BLOCK Direction: BSS to SGSN, SGSN to BSS Table 3/GSM 08.16: NS-BLOCK PDU contents Information element Reference Presence Format Length PDU type M V 1 Cause M TLV 3 NS-VCI M TLV 4 |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 9.2.4 NS-BLOCK-ACK | This PDU acknowledges that an NS-VC has been blocked for use. PDU type: NS-BLOCK-ACK Direction: SGSN to BSS, BSS to SGSN Table 4/GSM 08.16: NS-BLOCK-ACK PDU contents Information element Reference Presence Format Length PDU type M V 1 NS-VCI M TLV 4 |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 9.2.5 NS-RESET | This PDU indicates that the NS peer entity is trying to reset one NS-VCs. PDU type: NS-RESET Direction: BSS to SGSN, SGSN to BSS ETSI ETSI TS 101 299 V7.1.0 (1999-07) 27 (GSM 08.16 version 7.1.0 Release 1998) Table 5/GSM 08.16: NS-RESET PDU contents Information element Reference Presence Format Length PDU type M V 1 Ca... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 9.2.6 NS-RESET-ACK | This PDU acknowledges the reset of the indicated NS-VCs. PDU type: NS-RESET-ACK Direction: BSS to SGSN, SGSN to BSS Table 6/GSM 08.16: NS-RESET-ACK PDU contents Information element Reference Presence Format Length PDU type M V 1 NS-VCI M TLV 4 NSEI M TLV 4 |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 9.2.7 NS-STATUS | This PDU is used to report error conditions. PDU type: NS-STATUS Direction: SGSN to BSS, BSS to SGSN Table 7/GSM 08.16: NS-STATUS PDU contents Information element Reference Presence Format Length PDU type M V 1 Cause M TLV 3 NS-VCI C TLV 4 NS PDU C TLV 3-? BVCI C TLV 4 |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 9.2.7.1 Static conditions for NS-VCI | The "NS-VCI" IE shall be included when the "Cause" IE is set to one of the following values: a) "NS-VC blocked", b) "NS-VC unknown", and shall not be included otherwise. |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 9.2.7.2 Static conditions for NS PDU | The "NS PDU" IE shall be included if the NS-STATUS message is sent in response to a received NS PDU within which an error was detected i.e. when the "Cause" IE is set to one of the following values: ETSI ETSI TS 101 299 V7.1.0 (1999-07) 28 (GSM 08.16 version 7.1.0 Release 1998) a) - "Semantically incorrect PDU", b) - "... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 9.2.7.3 Static conditions for BVCI | The "BVCI" IE shall be included when the "Cause" IE is set to one of the following values: a) " BVCI unknown on that NSE", and shall not be included otherwise. |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 9.2.8 NS-UNBLOCK | This PDU indicates that an NS-VC shall be unblocked at the recipient entity. PDU type: NS-UNBLOCK Direction: BSS to SGSN, SGSN to BSS Table 8/GSM 08.16: NS-UNBLOCK PDU contents Information element Reference Presence Format Length PDU type M V 1 |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 9.2.9 NS-UNBLOCK-ACK | This PDU acknowledges that an NS-VC has been unblocked. PDU type: NS-UNBLOCK-ACK Direction: SGSN to BSS, BSS to SGSN Table 9/GSM 08.16: NS-UNBLOCK-ACK PDU contents Information element Reference Presence Format Length PDU type M V 1 |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 9.2.10 NS-UNITDATA | This PDU transfers one NS SDU between the BSS and SGSN. PDU type: NS-UNITDATA Direction: BSS to SGSN, SGSN to BSS ETSI ETSI TS 101 299 V7.1.0 (1999-07) 29 (GSM 08.16 version 7.1.0 Release 1998) Table 10/GSM 08.16: NS-UNITDATA PDU contents Information element Reference Presence Format Length PDU type M V 1 spare octet M... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 10 General information elements coding | This clause is not applicable to the Sub-Network Service protocol. |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 10.1 General structure of the information elements | The general information element structure is composed of (see Figure 8/GSM 08.16): a) an Information Element Identifier (also referred to as the T field), b) a length indicator (also referred to as the L field), c) the information element value (also referred to as the V field). Information elements have the TLV or the... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 10.1.1 Information Element Identifier | The first octet of an information element having the TLV format contains the IEI of the information element. If this octet does not correspond to an IEI known in the PDU, the receiver shall assume that the next octet is the first octet of the length indicator field and shall interpret it as described in the "Length ind... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 10.1.2 Length indicator | The length indicator shall be included in all information elements having the TLV format. Information elements may be variable in length. The length indicator is one or two octet long, the second octet may be absent. This field consists of the field extension bit, 0/1 ext, and the length of the value field which follow... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 10.2 Information element description | The descriptions of the information elements are organized in alphabetical order of the IE name. Each IE is described in one subclause. A figure of the subclause defines the structure of the IE indicating: - the position of the IEI, when present; - the fields the IE value part is composed of; - the position of the leng... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 10.3 Network Service Control information element description | The IEI values defined for the Network Service Control protocol are indicated in table 11/GSM 08.16: ETSI ETSI TS 101 299 V7.1.0 (1999-07) 31 (GSM 08.16 version 7.1.0 Release 1998) Table 11/GSM 08.16: IEI coding IEI coding Information element name 8 7 6 5 4 3 2 1 0 0 0 0 0 0 0 0 Cause 0 0 0 0 0 0 0 1 NS-VCI 0 0 0 0 0 0... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 10.3.1 BVCI | This IE is used for multiplexing BVCs on NS-VCs. 8 7 6 5 4 3 2 1 octet 1 IEI octets 2, 2a length indicator octet 3 most significant octet of BVCI octet 4 least significant octet of BVCI Figure 11/GSM 08.16: BVCI information element |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 10.3.2 Cause | This IE may be used to indicate to the peer NS entity the reason which triggered a procedure, or the reason of an abnormal condition. 8 7 6 5 4 3 2 1 octet 1 IEI octets 2, 2a length indicator octet 3 cause value Figure 12/GSM 08.16: Cause information element The cause values are indicated in Table 12/GSM 08.16: Table 1... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 10.3.3 NS PDU | This IE is included in the NS-STATUS PDU sent in answer to an erroneous NS PDU. This IE contains the erroneous PDU received. The erroneous PDU may be truncated in order to fit in the maximum size of the NS-STATUS PDU. 8 7 6 5 4 3 2 1 octet 1 IEI octets 2, 2a length indicator octet 3 NS PDU ... octet n Figure 13/GSM 08.... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 10.3.4 NS SDU | This IE contains one and only one NS SDU transmitted across the Gb interface. This IE has the V format. 8 7 6 5 4 3 2 1 octet 1 NS SDU ... octet n Figure 14/GSM 08.16: NS SDU information element In this "NS SDU" information element, bit i of octet j is equal to bit i of octet j of the NS SDU, as defined in the NS user ... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 10.3.5 NS-VCI | This IE unambiguously identifies one NS-VC amongst all the NS-VCs used between one SGSN and the connected BSSs. 8 7 6 5 4 3 2 1 octet 1 IEI octets 2, 2a length indicator octet 3 most significant octet of NS-VCI octet 4 least significant octet of NS-VCI Figure 15/GSM 08.16: NS-VCI information element |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 10.3.6 NSEI | This IE unambiguously identifies one NSE 8 7 6 5 4 3 2 1 octet 1 IEI octets 2, 2a length indicator octet 3 most significant octet of NSEI octet 4 least significant octet of NSEI Figure 16/GSM 08.16: NSEI information element |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 10.3.7 PDU type | The PDU type has the V format. ETSI ETSI TS 101 299 V7.1.0 (1999-07) 33 (GSM 08.16 version 7.1.0 Release 1998) Table 13/GSM 08.16: PDU type coding PDU type coding PDU name 8 7 6 5 4 3 2 1 0 0 0 0 0 0 0 0 NS-UNITDATA 0 0 0 0 0 0 1 0 NS-RESET 0 0 0 0 0 0 1 1 NS-RESET-ACK 0 0 0 0 0 1 0 0 NS-BLOCK 0 0 0 0 0 1 0 1 NS-BLOCK-... |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 10.3.8 Spare octet | This IE is included in a PDU e.g. when it is needed to align another IE on a 32 bit boundary. This IE has the V format. All bits are spare. 8 7 6 5 4 3 2 1 octet 1 spare Figure 17/GSM 08.16: NS-VCI information element |
d4e1d4d5380d2442586fde111644eacb | 101 299 | 11 List of system variables | Table 14/ GSM 08.16: System timers timer name timer value notes relation to other timers Tns-block 1s to 120s Guards the blocking and unblocking procedures none Tns-reset 1s to 120s Guards the reset procedure none Tns-test 1s to 60s Periodicity of the NS-VC test procedure none Tns-alive 3s Guards the NS-VC test procedu... |
6f7533e5ef0c8c1ccd15b70e6006c39d | 101 298 | 1 Scope | The present document specifies the physical layer on the Base Station System (BSS) to Serving GPRS Support Node (SGSN) interface (Gb interface) and references layer 1 standards to be used on this interface. The protocol stack on the Gb interface is defined in the stage 2 GSM 03.60 [3]. |
6f7533e5ef0c8c1ccd15b70e6006c39d | 101 298 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • Fo... |
6f7533e5ef0c8c1ccd15b70e6006c39d | 101 298 | 3 Definitions, symbols and abbreviations | |
6f7533e5ef0c8c1ccd15b70e6006c39d | 101 298 | 3.1 Definitions | Refer to GSM 02.60 [2]. |
6f7533e5ef0c8c1ccd15b70e6006c39d | 101 298 | 3.2 Symbols | Refer to GSM 03.60 [3]. ETSI ETSI TS 101 298 V7.0.1 (1999-08) 6 (GSM 08.14 version 7.0.1 Release 1998) |
6f7533e5ef0c8c1ccd15b70e6006c39d | 101 298 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply. Additional applicable abbreviations can be found in GSM 01.04 [1] and GSM 03.60 [3]. DCE Data Circuit-terminating Equipment DTE Data Terminal Equipment E1 A four wire symmetrical digital transmission path carrying PCM signal at 2048 kbit/s. FR... |
6f7533e5ef0c8c1ccd15b70e6006c39d | 101 298 | 4 Layer 1 specification | Since Frame Relay shall be used on the Gb interface for phase 1 of GPRS, see TS GSM 03.60 [3], this version of this Technical Specification refers to “The Frame Relay Forum User-to-Network Implementation Agreement (UNI)” [5] which recommends physical layer interfaces to be used in conjunction with Frame Relay. |
6f7533e5ef0c8c1ccd15b70e6006c39d | 101 298 | 4.1 Physical configuration of the Gb interface | The detailed physical configuration of the Gb interface is subject to negociation between operators and equipment providers and is out of the scope of this Technical Specification. For example, point-to-point physical lines or an intermediate Frame Relay network may be used. In the latter case, the two ends of the Gb i... |
6f7533e5ef0c8c1ccd15b70e6006c39d | 101 298 | 4.2 Physical layer interface | Each of the physical layer of the Gb interface shall conform to one of the following FRF 1.1 [5] clauses. This does not mean that each BSS and SGSN equipment has to support all of these physical interfaces, it means that the supported physical interfaces shall be compliant with the corresponding clause of FRF 1.1 [5]. ... |
6f7533e5ef0c8c1ccd15b70e6006c39d | 101 298 | 4.3 Error rate | The error rate experienced at the physical layer between the BSS and the SGSN shall be compatible with the operation of the upper layers. ETSI ETSI TS 101 298 V7.0.1 (1999-08) 7 (GSM 08.14 version 7.0.1 Release 1998) |
6f7533e5ef0c8c1ccd15b70e6006c39d | 101 298 | 4.4 Provision of physical channels | The physical channels on the Gb interface shall be permanently reserved by means of administrative procedures. ETSI ETSI TS 101 298 V7.0.1 (1999-08) 8 (GSM 08.14 version 7.0.1 Release 1998) Annex A (informative): Document change history SPEC SMG# CR PHA SE VERS NEW_VE RS SUBJECT 08.14 s24 new R97 2.0.0 6.0.0 Gb interfa... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 1 Scope | The present document provides the description of the Subnetwork Dependent Convergence Protocol (SNDCP) for the General Packet Radio Service (GPRS). The user of the services provided by SNDCP is a packet data protocol (PDP) at the mobile Station (MS) or the Relay at the Serving GPRS Support Node (SGSN). Additionally, a ... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • Fo... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 3 Definitions and abbreviations | |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 3.1 Definitions | In addition to abbreviations in 01.04 [1] and 02.60 [2] the following abbreviations apply: N201 LLC layer parameter (see GSM 04.64 for clarity). Defines maximum number of octets in the information field of LL-PDU. Separate values are applicable for I (see N201-I), U and UI (see N201-U) LL-PDUs. N201-I LLC layer paramet... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 3.2 Abbreviations | In addition to abbreviations in GSM 01.04 [1], GSM 02.60 [2], and GSM 03.60 [3], the following abbreviations apply: DCOMP Identifier of the user data compression algorithm used for the N-PDU F First segment indicator bit GMM GPRS Mobility Management IP Internet Protocol LLC Logical Link Control M More bit used to indic... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 4 General | The present document describes the functionality of the GPRS SNDCP. The overall GPRS logical architecture is defined in GSM 03.60 [3]. Location of the SNDCP in GPRS protocol stack can be seen in Figure 1. RLC MAC Relay Network Service GTP Application IP / X.25 SNDCP LLC RLC MAC GSM RF SNDCP LLC BSSGP L1bis GSM RF BSSGP... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 5 Service primitives and functions | |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 5.1 Service primitives | This subclause explains the service primitives used for communication between the SNDCP layer and other layers. See also GSM 04.07 [4] to get an overall picture of the service primitives. Figure 3 illustrates the service access points through which the primitives are carried out. ETSI ETSI TS 101 297 V7.3.0 (2000-03) 1... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 5.1.1 SNDCP service primitives | The primitives provided by the SNDCP layer are listed in Table 1. Table 1: SNDCP layer service primitives Generic Name Type Parameters Request Indication Response Confirm SNDCP User (PDP or the SGSN Relay) ↔ ↔ ↔ ↔SNDCP SN-DATA X - - - N-PDU, NSAPI, N-PDU Number SN-DATA - X - - N-PDU, NSAPI SN-UNITDATA X X - - N-PDU, NS... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 5.1.1.1 SN-DATA.request | Request used by the SNDCP user for acknowledged transmission of N-PDU. The successful transmission of SN-PDU shall be confirmed by the LLC layer. The SN-DATA.request primitive conveys NSAPI to identify the PDP using the service. N-PDU Number, if present, indicates the N-PDU number previously assigned to this N-PDU. NOT... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 5.1.1.2 SN-DATA.indication | Indication used by the SNDCP entity to deliver the received N-PDU to the SNDCP user. Successful reception has been acknowledged by the LLC layer. |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 5.1.1.3 SN-UNITDATA.request | Request used by the SNDCP user for unacknowledged transmission of N-PDU. The SN-UNITDATA.request primitive conveys NSAPI to identify the PDP using the service. |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 5.1.1.4 SN-UNITDATA.indication | Indication used by the SNDCP entity to deliver the received N-PDU to the SNDCP user. |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 5.1.1.5 SN-XID.request | Request used by the SNDCP user at the initiating entity to deliver the list of requested XID parameters to the peer entity. |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 5.1.1.6 SN-XID.indication | Indication used by the SNDCP entity to deliver the list of requested XID parameters to the SNDCP user. |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 5.1.1.7 SN-XID.response | Response used by the SNDCP user to deliver the list of negotiated XID parameters to the peer entity. |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 5.1.1.8 SN-XID.confirm | Confirm used by the SNDCP entity to deliver the list of negotiated XID parameters to the SNDCP user. |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 5.1.2 Service primitives used by SNDCP layer | The SNDCP layer uses the service primitives provided by the SM sublayer and the LLC layer (see Table 2). SM is specified in GSM 04.08 [5] and LLC in GSM 04.64 [6]. ETSI ETSI TS 101 297 V7.3.0 (2000-03) 13 (GSM 04.65 version 7.3.0 Release 1998) Table 2: Service primitives used by the SNDCP entity Generic Name Type Param... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 5.1.2.1 LL-RESET.indication | Indication used by the LLC layer in the SGSN to indicate to the SNDCP layer that the Reset XID parameter has been transmitted, and by the LLC layer in the MS to indicate to the SNDCP layer that the Reset XID parameter has been received. Upon receipt of the LL-RESET.indication, the SNDCP layer shall: - treat all outstan... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 5.1.2.2 LL-ESTABLISH.request | Request used by the SNDCP layer to establish or re-establish acknowledged peer-to-peer operation for a SAPI in the LLC layer. XID Requested is used to deliver the requested SNDCP XID parameters to the LLC layer. |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 5.1.2.3 LL-ESTABLISH.indication | Indication used by the LLC layer to inform the SNDCP layer about establishment or re-establishment of acknowledged peer-to-peer operation for a SAPI in the LLC layer. XID Requested is used to deliver the requested SNDCP XID parameters to the SNDCP layer. In case of a re-establishment, all NSAPIs mapped to the affected ... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 5.1.2.4 LL-ESTABLISH.response | Response used by the SNDCP layer after reception of the LL-ESTABLISH.indication. XID Negotiated is used to deliver the negotiated SNDCP XID parameters to the LLC layer. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.