hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 5.1.2.5 LL-ESTABLISH.confirm | Confirmation used by the LLC layer to inform the SNDCP layer about successful initiation of acknowledged peer-to- peer operation for a SAPI in the LLC layer. XID Negotiated is used to deliver the negotiated SNDCP XID parameters to the SNDCP layer. In case of a re-establishment, all NSAPIs mapped to the affected SAPI sh... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 5.1.2.6 LL-RELEASE.request | Request used by the SNDCP layer to release acknowledged peer-to-peer operation for a SAPI in the LLC layer. The Local parameter indicates whether the termination shall be local (see 04.64 for details). |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 5.1.2.7 LL-RELEASE.indication | Indication used by the LLC layer to inform the SNDCP layer about termination of acknowledged peer-to-peer operation for a SAPI in the LLC layer. The Cause parameter indicates the cause for the termination. On receipt of LL-RELEASE.indication, compressed N-PDUs queuing to be forwarded to the affected SAPI are deleted fr... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 5.1.2.8 LL-RELEASE.confirm | Confirmation used by the LLC layer to inform the SNDCP layer about termination of acknowledged peer-to-peer operation for a SAPI in the LLC layer. On receipt of LL-RELEASE.confirm, compressed N-PDUs queuing to be forwarded to the affected SAPI are deleted from the SNDCP layer. Also all compression entities using acknow... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 5.1.2.9 LL-XID.request | Request used by the SNDCP layer to deliver the requested SNDCP XID parameters to the LLC layer. ETSI ETSI TS 101 297 V7.3.0 (2000-03) 15 (GSM 04.65 version 7.3.0 Release 1998) |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 5.1.2.10 LL-XID.indication | Indication used by the LLC layer to deliver the requested SNDCP XID parameters to the SNDCP layer. |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 5.1.2.11 LL-XID.response | Response used by the SNDCP layer to deliver the negotiated SNDCP XID parameters to the LLC layer. |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 5.1.2.12 LL-XID.confirm | Confirm used by the LLC layer to deliver the negotiated SNDCP XID parameters to the SNDCP layer. |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 5.1.2.13 LL-DATA.request | Request used by the SNDCP layer for acknowledged transmission of an SN-PDU. The SNDCP entity shall associate a reference parameter for each LL-DATA.request. QoS Parameters in the SGSN includes precedence class, delay class, and peak throughput. QoS Parameters in the MS includes peak throughput. QoS Parameters is define... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 5.1.2.14 LL-DATA.indication | Indication used by the LLC layer to deliver the successfully received SN-PDU to the SNDCP layer. |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 5.1.2.15 LL-DATA.confirm | Confirm used by the LLC layer to inform SNDCP layer about successful transmission of SN-PDU. The primitive includes a reference parameter from which the SNDCP entity shall identify the LL-DATA.request this confirmation was associated with. All buffered N-PDUs whose complete reception is confirmed are deleted. |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 5.1.2.16 LL-UNITDATA.request | Request used by the SNDCP layer for unacknowledged transmission of a SN-PDU. Unconfirmed transmission shall be used by the LLC layer. Acknowledged peer-to-peer LLC operation does not need to be established before unacknowledged transmission is allowed. QoS Parameters in the SGSN includes precedence class, delay class, ... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 5.1.2.17 LL-UNITDATA.indication | Indication used by the LLC layer to deliver the received SN-PDU to the SNDCP layer. There is no need for acknowledged peer-to-peer LLC operation for unacknowledged transmission of SN-PDU. |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 5.1.2.18 LL-STATUS.indication | Indication used by the LLC layer to inform SNDCP when an LLC error that cannot be corrected by the LLC layer has occurred. The Cause parameter indicates the cause of the failure. On receipt of LL-STATUS.indication, SNDCP shall inform the SM sub-layer by means of the SNSM-STATUS.request primitive. ETSI ETSI TS 101 297 V... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 5.1.2.19 SNSM-ACTIVATE.indication | Indication used by the SM entity to inform the SNDCP entity that an NSAPI has been activated for data transfer. It also informs the SNDCP entity about the negotiated QoS profile (see GSM 04.08), the SAPI assigned for this NSAPI, and, in the MS, the radio priority level to be used by RLC/MAC. If the NSAPI activated uses... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 5.1.2.20 SNSM-ACTIVATE.response | Response used by the SNDCP layer to inform SM entity that the indicated NSAPI is now in use and that the acknowledged peer-to-peer LLC operation for the indicated SAPI is established, if necessary. |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 5.1.2.21 SNSM-DEACTIVATE.indication | Indication used by the SM entity to inform the SNDCP entity that an NSAPI has been deallocated and cannot be used by the SNDCP entity anymore. All buffered N-PDUs corresponding to this NSAPI are deleted. Upon reception of the SNSM-DEACTIVATE.indication, the SNDCP entity shall, if necessary, release the acknowledged pee... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 5.1.2.22 SNSM-DEACTIVATE.response | Response used by the SNDCP layer to inform SM entity that the NSAPI indicated is no longer in use and that the acknowledged peer-to-peer LLC operation for the associated SAPI is released, if necessary. |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 5.1.2.23 SNSM-MODIFY.indication | Indication used by the SM entity to trigger change of the QoS profile (see GSM 04.08) for an NSAPI and indication of the SAPI to be used. It is also used by the SM entity in the SGSN to inform the SNDCP entity that an NSAPI shall be created, together with the (re-)negotiated QoS profile, the SAPI assigned, and, in the ... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 5.1.2.24 SNSM-MODIFY.response | Response used by the SNDCP entity to inform the SM entity that the indicated NSAPI and QoS profile are now in use and the acknowledged peer-to-peer LLC operations for the appropriate SAPIs are established and/or released, if necessary. |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 5.1.2.25 SNSM-STATUS.request | This primitive is used by the SNDCP layer to inform the SM sub-layer that SNDCP cannot continue its operation due to errors at the LLC layer (as indicated with LL-RELEASE.indication) or at the SNDCP layer. The Cause parameter indicates the cause of the error. |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 5.1.2.26 SNSM-SEQUENCE.indication | This primitive is used during an inter-SGSN routeing area update and applies only to NSAPIs using acknowledged peer- to-peer LLC operation. When the primitive is used in the MS, the Receive N-PDU number parameter indicates the Receive N-PDU number in the SGSN. When the primitive is used in the SGSN, the Receive N-PDU n... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 5.1.2.27 SNSM-SEQUENCE.response | This primitive is used during an inter-SGSN routeing area update and applies only to NSAPIs using acknowledged peer- to-peer LLC operation. The primitive is used by the SNDCP layer in the MS following receipt of an SNSM- SEQUENCE.indcation, in order to return the Receive N-PDU number to the SGSN during an ongoing inter... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 5.1.2.28 SNSM-STOP-ASSIGN.indication | This primitive is used during an inter-SGSN routeing area update in the old SGSN by the SM entity to inform the SNDCP entity to stop assigning N-PDU numbers to N-PDUs received through the SN-DATA.request primitive. The primitive is sent before the Send N-PDU number and the Receive N-PDU number are transferred to the ne... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 5.2 Service functions | SNDCP shall perform the following functions (see Figure 3): - Mapping of SN-DATA primitives onto LL-DATA primitives. - Mapping of SN-UNITDATA primitives onto LL-UNITDATA primitives. - Multiplexing of N-PDUs from one or several network layer entities onto the appropriate LLC connection. ETSI ETSI TS 101 297 V7.3.0 (2000... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6 Protocol functions | |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.1 Multiplexing of N-PDUs | The NSAPI field shall be used for the identification of the specific PDP type and PDP address pair that is using the services provided by the SNDCP layer. The MS allocates NSAPIs dynamically at the PDP Context Activation. The NSAPI is delivered by the SM sub-layer to the SNDCP layer with the SNSM-ACTIVATE.indication pr... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.2.1 Establishment of acknowledged peer-to-peer LLC operation | |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.2.1.1 Establishment criteria | If acknowledged peer-to-peer LLC operation is required by an NSAPI (as indicated by the QoS profile) but is not yet established for the SAPI used by the NSAPI, then the SNDCP layer shall initiate the establishment procedure. The SNDCP layer at the MS shall initiate the establishment, using the procedure in subclause 6.... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.2.1.2 Re-establishment of the acknowledged peer-to-peer LLC operation | The SNDCP layer may initiate re-establishment of the acknowledged peer-to-peer LLC operation for a SAPI under certain situations, for example when an error is detected by a V.42 bis data compression entity used for acknowledged data transfer. The LLC layer may also initiate re-establishment of the acknowledged peer-to-... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.2.1.3 Establishment procedure | The SNDCP layer shall initiate the establishment or re-establishment by sending an LL-ESTABLISH.request primitive to the relevant LLC SAP. SNDCP XID parameters may be included in an SNDCP XID block in the LL-ESTABLISH.request primitive. If no SNDCP XID parameter is to be included, an empty SNDCP XID block shall be incl... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.2.1.4 Exceptional situations | If the originator of the establishment procedure receives an LL-RELEASE.indication with Cause "DM received", it shall inform the SM sub-layer using the SNSM-STATUS.request primitive with Cause "DM received". SM shall then deactivate all PDP contexts for that SAPI requiring acknowledged peer-to-peer LLC operation. If th... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.2.2 Release of acknowledged peer-to-peer LLC operation | |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.2.2.1 Release criteria | If acknowledged peer-to-peer LLC operation is established for the SAPI used by a PDP context that is going to be deactivated or mapped to another SAPI, and if there is no other NSAPIs that require acknowledged peer-to-peer LLC operation using the original SAPI, then the SNDCP layer shall initiate the release procedure.... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.2.2.2 Release procedure | The SNDCP layer shall initiate the release by sending a LL-RELEASE.request primitive to the relevant LLC SAP. The Local parameter shall be set if the release is the result of receipt of the SNSM-DEACTIVATE.indication primitive, otherwise it shall not be set. |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.2.2.3 Release initiated by the LLC layer | The LLC layer may initiate release of the acknowledged peer-to-peer LLC operation for a SAPI under situations described in GSM 04.64. The LLC layer shall inform the SNDCP layers of the release of acknowledged peer-to-peer LLC operation using the LL-RELEASE.indication primitive. SNDCP shall process the LL-RELEASE.indica... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.3 N-PDU buffering | The N-PDUs shall be buffered in the SNDCP layer before they are compressed segmented and transmitted to the LLC layer. The reception of an SNSM-DEACTIVATE.indication shall trigger the deletion of the buffer for the related NSAPI. For acknowledged data transfer, the SNDCP entity shall buffer an N-PDU until successful re... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.4 Management of delivery sequence | The SNDCP layer shall retain the delivery sequence of N-PDUs of each NSAPI between the peer entities. The delivery sequence of N-PDUs from different NSAPIs may be changed according to the QoS profiles. |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.5 Protocol control information compression | Protocol control information compression is an optional SNDCP feature. Only TCP/IP header compression has been specified in the present document. Negotiation of the supported algorithms and their parameters is carried out between MS and SGSN using the SNDCP XID parameters (see clause 8). 6.5.1 Negotiation of multiple p... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.5.1.1 Format of the protocol control information compression field | Bit 8 7 6 5 4 3 2 1 Octet 1 P X X Entity number Octet 2 X X X Algorithm type Octet 3 Length=n-3 Octet 4 PCOMP1 PCOMP2 … … … Octet x High-order octet … … Octet n Low-order octet Figure 7: Protocol control information compression field format for SNDCP XID negotiation |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.5.1.1.1 Spare bit (X) | The X bit shall be set to 0 by the transmitting SNDCP entity and shall be ignored by the receiving SNDCP entity.. |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.5.1.1.2 Propose bit (P) | The P bit shall be set to 1 if a new compression entity is being proposed, otherwise it shall be set to 0. If the P bit is set to 1, then all octets shall be included, otherwise octet 2 and octets 4 to x-1 shall not be included. If the P bit is set to 1, then only enough number of octets shall be included to contain th... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.5.1.1.3 Entity number | The entity number shall be used to identify a protocol control information compression entity on a SAPI. The entity number shall be assigned using the following rules: - The entity number shall be an integer from 0 to 31. - The entity number shall be assigned independently on each of the SAPIs. - An entity number shall... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.5.1.1.4 Algorithm type | Table 4 show the list of protocol control information compression algorithms supported by the SNDCP layer. When new compression algorithms are needed for SNDCP, Table 4 shall be updated. Table 4: List of protocol control information compression algorithms supported by SNDCP Compression algorithm Algorithm type (Range 0... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.5.1.1.5 PCOMP | One or more PCOMP values shall be assigned dynamically to a compression algorithm, based on the negotiation of the XID parameters for protocol control information compression. Each of the assigned PCOMP values denotes one compressed frame type of that compression algorithm. The assignment of the PCOMP values follows th... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.5.1.2 Resetting compression entities following SNDCP XID negotiation | The LL-Establish primitives shall be used for the negotiation of protocol control information compression if: - one or more parameters, excluding the applicable NSAPIs, of existing compression entities used with acknowledged peer-to-peer LLC operation are changed by the originator of the negotiation; or - one or more N... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.5.1.3 Parameters for compression entities | On negotiating a compression entity, not all the parameters of the entity have to be specified. If a parameter is to be included, all the preceding parameters shall also be specified, and the length field shall be set to the sum of the lengths of all the parameters specified. If any of the parameters is not specified, ... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.5.2 TCP/IP header compression | The protocol control information compression method is specific for each network layer protocol type. TCP/IP (IPv4) header compression is specified in RFC 1144 [9]. ETSI ETSI TS 101 297 V7.3.0 (2000-03) 27 (GSM 04.65 version 7.3.0 Release 1998) |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.5.2.1 Parameters | Table 5 contains the parameters defined for a compression entity using TCP/IP header compression. They may be negotiated during SNDCP XID negotiation. Table 5: RFC 1144 TCP/IP header compression parameters Parameters Algorithm Name Algorithm Type Length Parameter Name Format Range Sense of Negotiation Default Value RFC... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.5.2.1.1 Applicable NSAPIs | See subclause 7.1.3. |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.5.2.1.2 S0 | The number of state slots, as defined in [9]. The S0 range is 1 through 256, with 16 as default value. |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.5.2.2 Assignment of PCOMP values | The underlying service shall be able to distinguish the three types of compressed N-PDUs (i.e., Type IP, Uncompressed TCP, and Compressed TCP), as defined in RFC 1144 [9]. These three N-PDU types are differentiated by using different PCOMP values. Two PCOMP values shall be assigned to the TCP/IP header compression algo... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.5.2.3 Error Recovery | When TCP/IP header compression is used with unacknowledged peer-to-peer LLC operation, the decompression entity shall be notified in case an N-PDU is dropped, so that error recovery procedure (see [9]) can be invoked. |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.6 Data compression | Data compression is an optional SNDCP feature. Data compression applies to both SN-DATA and SN-UNITDATA primitives. Data compression, if used, shall be performed on the entire N-PDU, including the possibly compressed protocol control information. Figure 8 shows an example how the SNDCP functions may be used. Several NS... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.6.1 Negotiation of multiple data compression types | Each SNDCP entity that supports data compression shall be able to negotiate one or several data compression entities with the compression field format shown in Figure 9. The negotiation shall be carried out using the XID parameter negotiation specified in subclause 6.8. The initiating entity defines a set of requested ... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.6.1.1 Format of the data compression field | Bit 8 7 6 5 4 3 2 1 Octet 1 P X X Entity number Octet 2 X X X Algorithm type Octet 3 Length=n-3 Octet 4 DCOMP1 DCOMP2 … … … Octet x High-order octet … … Octet n Low-order octet Figure 9: Data compression field format for SNDCP XID negotiation |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.6.1.1.1 Spare bit (X) | The X bit shall be set to 0 by the transmitting SNDCP entity and shall be ignored by the receiving SNDCP entity. |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.6.1.1.2 Propose bit (P) | The P bit shall be set to 1 if a new compression entity is being proposed, otherwise it shall be set to 0. If the P bit is set to 1, then all octets shall be included, otherwise octet 2 and octets 4 to x-1 shall not be included. If the P bit is set to 1, then only enough number of octets shall be included to contain th... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.6.1.1.3 Entity number | The entity number shall be used to identify a data compression entity on a SAPI. See subclause 6.5.1.1.3 for the rules for assigning entity numbers. The assignment of entity numbers for protocol control information compression entities and data compression entities shall be independent. |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.6.1.1.4 Algorithm type | Table 6 shows the list of data compression algorithms supported by the SNDCP layer. When new compression algorithms are needed for SNDCP, Table 6 shall be updated. Table 6: List of data compression algorithms supported by SNDCP Data compression algorithm Algorithm type (Range 0-31) V.42 bis 0 - Other values Reserved |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.6.1.1.5 DCOMP | One or more DCOMP values shall be assigned dynamically to a compression algorithm, based on the negotiation of the XID parameters for data compression. Each of the assigned DCOMP values denotes one compressed frame type of that compression algorithm. ETSI ETSI TS 101 297 V7.3.0 (2000-03) 30 (GSM 04.65 version 7.3.0 Rel... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.6.1.2 Resetting compression entities following SNDCP XID negotiation | The LL-Establish primitives shall be used for the negotiation of data compression if: - one or more parameters, excluding the applicable NSAPIs, of existing compression entities used with acknowledged peer-to-peer LLC operation are changed by the originator of the negotiation; or - one or more NSAPIs are removed, by th... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.6.1.3 Parameters for compression entities | On negotiating a compression entity, not all the parameters of the entity have to be specified. If a parameter is to be included, all the preceding parameters shall also be specified, and the length field shall be set to the sum of the lengths of all the parameters specified. If any of the parameters is not specified, ... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.6.2 Management of V.42 bis data compression | ITU-T V.42 bis [8] data compression may be used with SN-DATA primitives and SN-UNITDATA primitives. |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.6.2.1 Parameters | Table 7 contains the parameters defined for a compression entity using V.42 bis data compression. They may be negotiated during SNDCP XID negotiation. Table 7: V.42 bis data compression parameters Parameters Algorithm Name Algorithm Type Length Parameter Name Format Range Sense of Negotiation Default Value V.42 bis 0 A... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.6.2.1.1 Applicable NSAPIs | See subclause 7.1.3. |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.6.2.1.2 P0 | Two bits are used to indicate the usage of compression, one bit for each direction. 00 compress neither direction 01 compress MS-to-SGSN direction only 10 compress SGSN-to-MS direction only 11 compress both directions |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.6.2.1.3 P1 | Maximum number of codewords in the compressor dictionary (see [8]). |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.6.2.1.4 P2 | Maximum number of characters in an uncompressed data string that is accepted to be encoded. |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.6.2.2 Assignment of DCOMP values | One DCOMP value shall be assigned (as DCOMP1) to the V.42 bis data compression algorithm. |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.6.2.3 Operation of V.42 bis data compression | When V.42 bis is used with SN-DATA primitives, the data in the compression entity shall be flushed (using the C-FLUSH primitive defined in [8]) and added to the compressed N-PDU before the compressed N-PDU is sent. When V.42 bis is used with SN-UNITDATA primitives, the compression entity shall be reset (using the C-INI... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.7 Segmentation and reassembly | Segmentation shall be performed by the SNDCP entity to ensure that any SN-PDU transmitted is no longer than N201 (see GSM 04.64 [6]). The receiving SNDCP entity shall reassemble the segments back to the original (possibly compressed) N-PDU. The segmentation and reassembly procedures are different for acknowledged and u... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.7.1 General | |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.7.1.1 Segmentation | A (possibly compressed) N-PDU shall be segmented into one or more SN-PDUs. The length of each SN-PDU shall not be greater than N201-I (for acknowledged mode) or N201-U (for unacknowledged mode). The F bit in the SNDCP header shall be set to 1 for the first segment, and 0 for all subsequent segments. For unacknowledged ... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.7.1.2 Reassembly | During reassembly, DCOMP and PCOMP for an N-PDU shall be retrieved from the first segment (F bit set to 1). For acknowledged peer-to-peer LLC operation, the N-PDU number shall also be retrieved from the first segment. The receiving SNDCP entity shall be in one of the following three receiving states: - the Receive Firs... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.7.2 Segmentation and reassembly in acknowledged mode | Segmentation and reassembly in acknowledged mode shall follow the general procedures stated in subclause 6.7.1. |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.7.3 Segmentation and reassembly in unacknowledged mode | In addition to the general procedure in subclause 6.7.1, a segment number shall be used due to the unreliable nature of the unacknowledged mode. The Segment number is a sequence number assigned to each SN-UNITDATA PDU. The sequence number shall be set to 0 in the first SN-UNITDATA PDU of an N-PDU, and incremented by 1 ... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.7.4 Exception situations | |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.7.4.1 Receive First Segment state | If an SN-UNITDATA PDU is received with the F bit set to 0, the SN-UNITDATA PDU shall be discarded. The Receive First Segment state shall be entered if the M bit is set to 0, otherwise the Discard state shall be entered. If an SN-DATA PDU is received with the F bit set to 0, the SN-DATA PDU shall be discarded, and the a... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.7.4.2 Receive Subsequent Segment state | If an SN-UNITDATA PDU is received with the F bit set to 1, and if DCOMP or PCOMP is different from those in the first segment, then the SN-UNITDATA PDU and all previous segments belonging to the same N-PDU shall be discarded. The Received First Segment state shall be entered if the M bit is set to 0, otherwise the Disc... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.7.4.3 Discard state | If an SN-PDU is received with the M bit set to 1, the SN-PDU shall be discarded and the SNDCP entity shall remain in the Discard state. If an SN-PDU is received with the M bit set to 0, the SN-PDU shall be discarded and the Receive First Segment state entered. |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.8 XID parameter negotiation | Negotiation of XID parameters between peer SNDCP entities may be carried out to ensure optimal information transfer. The parameters are called SNDCP exchange identity (XID) parameters. SNDCP XID parameter negotiation may be initiated by the SNDCP entity at the MS or at the SGSN. If SNDCP XID parameters are to be change... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.8.1 Negotiation of compression entities | For parameter type 1 and 2, multiple compression fields (as shown in Figure 7 and Figure 9) may be specified. Each compression field corresponds to a compression entity. In each compression field, the "Applicable NSAPIs" parameter indicates the NSAPIs that uses the compression entity. The parameter, if included, shall ... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.8.2 Values of SNDCP XID parameters | In this subclause, the term "parameter" refers to an SNDCP XID parameter, a compression field (for parameter type 1 or 2), or a parameter for a compression field. If an SNDCP XID parameter has not been negotiated, default values shall apply. The default value for a compression field (entity) is "non-existing". If the o... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.8.3 Exception handling | In this subclause, the term "parameter" may refer, wherever applicable, to an SNDCP XID parameter, a compression field (for parameter type 1 or 2), or a parameter for a compression field. If the originating SNDCP XID block includes a parameter with unrecognised Type field, the parameter shall be ignored by the responde... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.9 Data transfer | |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.9.1 Acknowledged mode | The SNDCP entity shall initiate acknowledged data transmission only if the PDP context for the NSAPI identified in the SN-DATA.request has been activated and if acknowledged LLC operation has been established. The N-PDU number in acknowledged mode is a number assigned to each N-PDU received by SNDCP through an SN-DATA.... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 6.9.2 Unacknowledged mode | The SNDCP entity shall initiate unacknowledged data transmission only if the PDP context for the NSAPI identified in the SN-DATA.request has been activated. The SNDCP entity may initiate unacknowledged data transmission even if the acknowledged peer-to-peer operation is not established for that NSAPI. The N-PDU number ... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 7 Definition of SN-PDU | |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 7.1 Format convention | |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 7.1.1 Numbering convention | The convention used in the present document is illustrated in Figure 15. The bits are grouped into octets. The bits of an octet are shown horizontally and are numbered from 1 to 8. Multiple octets are shown vertically and are numbered from 1 to N. Bit 8 7 6 5 4 3 2 1 Oct 1 2 … N-1 N Figure 15: Format convention |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 7.1.2 Order of transmission | SN-PDUs are transferred between the SNDCP layer and LLC layer in units of octets, in ascending numerical octet order (i.e., octet 1, 2, …, N-1, N). The order of bit transmission is specific to the underlying protocols used across the Um interface and the Gb interface. |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 7.1.3 Field mapping convention | When a field is contained within a single octet, the lowest bit number of the field represents the lowest order value. When a field spans more than one octet, the order of bit values within each octet progressively decreases as the octet number increases. In that part of the field contained in a given octet the lowest ... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 7.2 SN-PDU Formats | Each SN-PDU shall contain an integral number of octets, and shall comprise a header part and a data part. An SN-PDU shall contain data from a single N-PDU only. Two different SN-PDU formats are defined. The SN-DATA PDU shall be used for acknowledged data transfer and SN-UNITDATA PDU for unacknowledged data transfer. Bi... |
d668a0fb7445162b22d971d66c4fd05e | 101 297 | 8 SNDCP XID parameters | The SNDCP XID parameters are shown in Table 8: Table 8: SNDCP XID parameters Parameter name Parameter Type Length Format Range Default value Units Sense of negotiation Version number 0 1 0000bbbb 0-15 0 - down Data Compression 1 variable See subclause 6.6.1 Protocol Control Information Compression 2 variable See subcla... |
5674c1ed15972156beea0b9e811e204d | 101 293 | 1 Scope | This document specifies for Mobile Stations (MS), for the digital cellular communications system and Personal Communication Systems (PCS) operating in the 900 MHz and 1800 MHz band (GSM900 and DCS1800), standardized by ETSI SMG, those ME functions which are required for conformance testing purposes only. However, excep... |
5674c1ed15972156beea0b9e811e204d | 101 293 | 2 Normative 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... |
5674c1ed15972156beea0b9e811e204d | 101 293 | 3 Definitions, conventions, and applicability | For abbreviations and acronyms, see GSM 01.04. |
5674c1ed15972156beea0b9e811e204d | 101 293 | 3.1 Mobile station definition and configurations | In this TS, a MS can be: - a vehicle mounted station; - a portable station; - a handheld station; - a vehicle mounted/portable station; - a vehicle mounted/handheld station. For a more detailed description of MS-configurations, see GSM 02.06. |
5674c1ed15972156beea0b9e811e204d | 101 293 | 3.2 Applicability | This TS is applicable to all MSs. 4 Activation and deactivation of special test functions in the MS The functions described in this TS can be activated and deactivated from a SS by sending appropriate layer 3 commands to the MS. The protocol discriminator to be used is defined in GSM 04.08, subclause 10.2. The layer 3 ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.