`
`Exhibit 1005.08Exhibit 1005.08
`
`
`
`ZTE Corporation and ZTE (USA) Inc.ZTE Corporation and ZTE (USA) Inc.
`
`

`

`TS 101 297 v6.1.0 (1998-07)
`
`Technical Specification
`
`Digital cellular telecommunications system (Phase 2+);
`General Packet Radio Service (GPRS);
`Mobile Station (MS) - Serving GPRS Support Node (SGSN);
`Subnetwork Dependent Convergence Protocol (SNDCP)
`(GSM 04.65 version 6.1.0 Release 1997)
`
`GSEITLT
`
`GLOBAL SYSTEM FOR
`MOBILE COMMUNICATIONS
`
`ZTE Corporation and ZTE (USA) Inc.
`Exhibit 1005.08-00001
`
`

`

`GSM 04.65 version 6.1.0 Release 1997
`
`2
`
`TS 101 297 V6.1.0 (1998-07)
`
`Reference
`
`DTS/SMG-O30465Q6 (COC030C3.PDF)
`
`Keywords
`Digital cellular telecommunications system,
`Global System for Mobile communications (GSM)
`
`ETSI
`
`Postal address
`
`F-06921 Sophia Antipolis Cedex - FRANCE
`
`Office address
`
`650 Route des Lucioles - Sophia Antipolis
`Valbonne - FRANCE
`Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 4716
`Siret N° 348 623 562 00017 — NAF 742 C
`Association a but non lucratif enregistrée a la
`Sous—Préfecture de Grasse (06) N° 7803/88
`
`Internet
`
`secretariat@etsi.fr
`http://www.etsi.fr
`http://www.etsi.org
`
`Copyright Notification
`
`No part may be reproduced except as authorized by Written permission.
`The copyright and the foregoing restriction extend to reproduction in all media.
`
`© European Telecommunications Standards institute 1998.
`All rights reserved.
`
`ETSI
`
`ZTE Corporation and ZTE (USA) Inc.
`Exhibit 1005.08-00002
`
`

`

`GSM 04.65 version 6.1.0 Release 1997
`
`3
`
`TS 101 297 V6.1.0 (1998-07)
`
`Contents
`
`Intellectual Property Rights .............................................................................................................................. ..5
`
`Foreword .......................................................................................................................................................... ..5
`
`1
`
`2
`
`3
`3.1
`3 .2
`
`4
`
`Scope ...................................................................................................................................................... ..6
`
`Normative references ............................................................................................................................. ..6
`
`Definitions and Abbreviations ............................................................................................................... ..7
`Definitions ....................................................................................................................................................... .. 7
`Abbreviations ................................................................................................................................................... .. 7
`
`General ................................................................................................................................................... ..8
`
`5
`5.1
`5.1.1
`
`Service Primitives and Functions ........................................................................................................... ..9
`Service Primitives ................................... ..
`
`SNDCP Service Primitives ....................................................................................................................... .. 10
`
`5.1.1.1
`5.1.1.2
`
`5.1.1.3
`5.1.1.4
`
`5.1.1.5
`5.1.1.6
`
`5.1.1.7
`5.1.1.8
`
`5.1.2
`5.1.2.1
`5.1.2.2
`
`5.1.2.3
`5.1.2.4
`
`5.1.2.5
`5.1.2.6
`5.1.2.7
`
`5.1.2.8
`5.1.2.9
`
`5.1.2.10
`5.1.2.11
`
`5.1.2.12
`5.1.2.13
`5.1.2.14
`5.1.2.15
`
`5.1.2.16
`5.1.2.17
`5.1.2.18
`
`5.1.2.19
`5.1.2.20
`
`5.1.2.21
`5.1.2.22
`
`5.1.2.23
`5.1.2.24
`5.2
`
`SN—DATA.request .............................................................................................................................. .. 10
`SN-DATA.indication . . . . . . . . . . . . . . . . . . . . .
`. . . . . . . . . . . . . . .. 11
`
`SN—UNITDATA.request ..................................................................................................................... .. 11
`SN-UNITDATA.indication ................................................................................................................ .. 1 1
`
`SN—XID.request .................................................................................................................................. .. 11
`SN-XID.indication .............................................................................................................................. .. 11
`
`SN—XID.response . . . . . . . . . . . . . . . . . . . . . . . . . . .
`. . . . . . . . . . . . . . .. 11
`
`SN—XID.conf1rm ................................................................................................................................. .. 11
`
`Service Primitives Used by SNDCP Layer .............................................................................................. .. l 1
`. . . . . . . . . . . . . . .. 13
`LL-ESTABLISH.request . . . . . . . . . . . . . . . . . . . . . . . . .
`
`. . . . . . . . . . . . . . .. 13
`LL—ESTABLISH.indication . . . . . . . . . . . . . . . . . . . . .
`
`LL-ESTABLISH.response . . . . . . . . . . . . . . . . . . . . . . .
`. . . . . . . . . . . . . . .. 13
`
`LL—ESTABLISH.confirm ................................................................................................................... .. 13
`
`LL—RELEASE.request ........................................................................................................................ .. 13
`LL-RELEASE.indication . . . . . . . . . . . . . . . . . . . . . . . . .
`. . . . . . . . . . . . . . . . . . . . . . . . .. 13
`
`LL—RELEASE.confirm ....................................................................................................................... .. 13
`
`LL-XID.request .................................................................................................................................. .. 13
`LL—XID.indication . . . . . . . . . . . . . . . . . . . . . . . . .
`. . . . . . . . . . . . . . . . . . . . . . . . .. 13
`
`LL-XID.response . . . . . . . . . . . . . . . . . . . . . . . . . . .
`. . . . . . . . . . . . . . . . . . . . . . . . .. 14
`
`. . . . . . . . . . .
`. . . . . . . . . . . . . . . . . . . . . . . . .. 14
`LL—XID.conf1rm . . . . . . . . . . .
`
`LL-DATA.request .............................................................................................................................. .. 14
`LL—DATA.indication .......................................................................................................................... .. 14
`LL-DATA.conf1rm ...................... ..
`LL—DATASENT.indication ......... ..
`
`
`
`LL—UNITDATA.request .............. ..
`
`LL-UN1TDATA.indication ................................................................................................................. .. 14
`SNSM—ACTIVATE.indication ........................................................................................................... .. 14
`
`SNSM—ACTIVATE.response . . . . . . . . . . .
`. . . . . . . . . . . . . . . . . . . . . . . . .. 15
`
`SNSM-DEACTIVATEindication ...................................................................................................... .. 15
`
`SNSM-DEACTIVATE.response ........................................................................................................ .. 15
`SNSM—MODIFY.indication . . . . . . . . . .
`. . . . . . . . . . . . . . . . . . . . . . . . .. 15
`
`SNSM-MODIFY.response . . . . . . . . . . . .
`. . . . . . . . . . . . . . . . . . . . . . . . .. 15
`
`SNSM—WINDOW.indication. . . . . . . . .
`. . . . . . . . . . . . . . . . . . . . . . . . .. 15
`
`Service Functions ........................................................................................................................................... .. 15
`
`6
`
`6.1
`6.2
`6.3
`6.4
`6.4.1
`6.4.1.1
`
`Protocol Functions . . . . . . . . . . . . . . . . . . . . . . .
`. . . . . . . . . .. 18
`
`Multiplexing of N—PDUs . . . . . . . . . . . . .
`. . . . . . . . . . .
`. . . . . . . . . . . . . . . . . . . . . . . . .. 18
`N-PDU buffering ........................................................................................................................................... .. 18
`Management of delivery sequence ................................................................................................................. .. 19
`Protocol Control Information Compression ............................................................................... .. 19
`
`
`Ncgotiation of multiple protocol control information compression typcs ......... ..
`Assignment of PCOMP values ........................................................................................................... .. 20
`
`ETSI
`
`ZTE Corporation and ZTE (USA) Inc.
`Exhibit 1005.08-00003
`
`

`

`
`
`
`
`
`
`6.4.2
`6.5
`
`6.5.1
`6.5.1.1
`6.5.2
`6.6
`6.6.1
`6.6.2
`6.7
`6.8
`
`6.8.1
`
`6.8.2
`6.9
`
`
`
`
`7
`7.1
`
`7.1.1
`7.1.2
`
`GSM 04.65 version 6.1.0 Release 1997
`
`4
`
`TS 101 297 V6.1.0 (1998-07)
`
`TCP/IP header compression ..................................................................................................................... .. 20
`
`Data compression ........................................................ ..
`Negotiation of multiple data compression types ....................................................................................... .. 22
`Assignment ofDCOMP values ........................................................................................................... .. 22
`Management ofV.42 bis data compression .... ..
`.............. .. 23
`
`Segmentation and reassembly ........................................................................................................................ .. 24
`Segmentation in acknowledged mode ...................................................................................................... .. 24
`Segmentation in unacknowledged mode ................................................................................ .. 24
`
`. . . . . . . . . . .
`. . . . . . . . . . . . . . . . . . . . . . . . .. 25
`XID parameter negotiation . . . . . .
`
`. . . . . . . . . . .
`Data transfer. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
`. . . . . . . . . . . . . . .. 27
`
`Acknowledged mode ................................................................................................................................ .. 27
`Unacknowledged mode ............................................................................................................................ .. 28
`Possible combinations of SNDCP Protocol Functions and their connection to service access points ........... .. 29
`
`Definition of SN—PDU.......................................................................................................................... ..29
`Format convention ......................................................................................................................................... .. 29
`
`Numbering convention . . . . . . .
`. . . . . . . . . . . . . . . . . . . . . . . . .. 29
`
`Order oftransmission . . . . . . . . . . . .
`. . . . . . . . . . . . . . . . . . . . . . . . .. 30
`
`
`Field mapping convention . . . . .
`. . . . . . . . . . . . . . . . . . . . . . . . .. 30
`SN—PDU Formats ........................................................................................................................................... .. 30
`
`SNDCP XID parameters ...................................................................................................................... ..32
`
`
`
`8
`
`7.1.3
`7 .2
`
`
`Annex A (informative):
`History ............................................................................................................................................................ ..35
`
`Change history ...............................................................................................33
`
`ETSI
`
`ZTE Corporation and ZTE (USA) Inc.
`Exhibit 1005.08-00004
`
`

`

`GSM 04.65 version 6.1.0 Release 1997
`
`5
`
`TS 101 297 V6.1.0 (1998-07)
`
`Intellectual Property Rights
`
`IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
`pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
`in SR 000 314: "Intellectual Properzjv Rights (IPRs); Essential, or potentially Essential, IPRs notified to E TS] in respect
`0fETSI standards”, which is available free of charge from the ETSI Secretariat. Latest updates are available on the
`ETSI Web server (http://www.etsi.fr/ipr or http://www.etsi.org/ipr).
`
`Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
`can be given as to the existence of other IPRs not referenced in SR 000 314 (or the updates on the ETSI Web server)
`which are, or may be, or may become, essential to the present document.
`
`Foreword
`
`This ETSI Technical Specification (TS) has been produced by the Special Mobile Group (SMG) of the European
`Telecommunications Standards Institute (ETSI).
`
`This TS describes the Subnetwork Dependent Convergence Protocol (SNDCP) for the General Packet Radio Service
`(GPRS) within the digital cellular telecommunications system.
`
`The contents of this TS are subject to continuing work within SMG and may change following formal SMG approval.
`Should SMG modify the contents of this TS it will then be released by ETSI with an identifying change of release date
`and an incrcasc in vcrsion numbcr as follows:
`
`Version 6.x.y
`
`where:
`
`6 GSM Phase 2+ Release 1997
`
`X
`
`the second digit is incremented for all other types of changes, i.e. technical enhancements, corrections,
`updates, etc.
`
`y
`
`the third digit is incremented when editorial only changes have been incorporated in the specification.
`
`ETSI
`
`ZTE Corporation and ZTE (USA) Inc.
`Exhibit 1005.08-00005
`
`

`

`GSM 04.65 version 6.1.0 Release 1997
`
`6
`
`TS 101 297 V6.1.0 (1998-07)
`
`1
`
`Scope
`
`This ETSI TS 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 control entity, e.g., AT command interpreter, may be an
`SNDCP user. SNDCP uses the services provided by the Logical Link Control (LLC) layer [4] and the Session
`Management (SM) sub-layer [2].
`
`The main functions of SNDCP are:
`
`— Multiplexing of several PDPs.
`
`— Compression/decompression ofuser data.
`
`— Compression/decompression of protocol control information.
`
`-
`
`Segmentation of a network protocol data unit (N-PDU) into Logical Link Control Protocol Data Units (LL-
`PDUs) and re—assembly of LL—PDUs into a N—PDU.
`
`GSM 04.65 is applicable to GPRS MS and SGSN.
`
`2
`
`Normative references
`
`References may be made to:
`
`a) specific versions of publications (identified by date of publication, edition number, version number, etc.), in
`which case, subsequent revisions to the referenced document do not apply; or
`
`b) all versions up to and including the identified version (identified by "up to and including" before the version
`identity); or
`
`c) all versions subsequent to and including the identified version (identified by "onwards" following the version
`identity); or
`
`d) publications without mention ofa specific version, in which case the latest version applies.
`
`A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same
`number.
`
`[1]
`
`[2]
`
`[3]
`
`[4]
`
`[5]
`
`[6]
`
`[7]
`
`GSVI 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and
`acronyms".
`
`GSVI 02.60: “Digital cellular telecommunication system; General Packet Radio Service (GPRS);
`Service Description, Stage 1”.
`
`GSVI 03.60: “Digital cellular telecommunication system; General Packet Radio Service (GPRS);
`Service Description, Stage 2”.
`
`GSVI 04.07: "Digital cellular telecommunications system (Phase 2--); Mobile radio interface
`signalling layer 3; General aspects".
`
`GSVI 04.08: "Digital cellular telecommunications system (Phase 2--), Mobile radio interface layer
`3 specification".
`
`GSVI 04.64: “Digital cellular telecommunication system; General Packet Radio Service (GPRS);
`Mobile Station — Serving GPRS Support Node (MS—SGSN) Logical Link Control (LLC) Layer
`Specification”.
`
`GSM 09.60: "Digital cellular telecommunications system (Phase 2+), General Packet Radio
`Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp Interface".
`
`ETSI
`
`ZTE Corporation and ZTE (USA) Inc.
`Exhibit 1005.08-00006
`
`

`

`GSM 04.65 version 6.1.0 Release 1997
`
`7
`
`TS 101 297 V6.1.0 (1998-07)
`
`[8]
`
`[9]
`
`ITU-T, Recommendation V.42 bis: “Data compression procedures for data circuit- terminating
`equipment (DCE) using error correcting procedures”.
`
`RFC—l 144, V. Jacobson: “Compressing TCP/IP Headers for Low—Speed Serial Links”.
`
`3
`
`Definitions and Abbreviations
`
`3.1
`
`Definitions
`
`In addition to the definitions in 02.60 [2] the following definitions apply:
`
`N201
`
`N201-I
`
`N201-U
`
`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.
`
`LLC layer parameter (see GSM 04.64 for clarity). Defines maximum number of octets
`available to a SN—DATA PDU for a specific SAPI.
`
`LLC layer parameter (see GSM 04.64 for clarity). Defines maximum number of octets
`available to a SN—UNITDATA PDU for a specific SAPI.
`
`N-PDU number
`
`A sequence number assigned to N—PDUs per NSAPI in unacknowledged mode.
`
`NSAPI
`
`Protection mode
`
`For each SN—PDU the NSAPI is an index to the PDP context of the PDP that is using the
`services provided by the SNDCP layer.
`
`Identifies the transfer mode for SN-UNITDATA transfer. In the protected mode, the lower
`layers shall discard the erroneous data when an error in the check sequence of the received
`user data is noticed. The erroneous data is not delivered to SNDCP layer at the receiving
`entity. In the unprotected mode, the correctness of the received information is not
`checked. The received information is transferred transparently to the peer SNDCP layer
`and to the user of the peer SNDCP entity.
`
`SAPI
`
`SAPI identifies the Service Access Point (with which a QoS profile is associated) that the
`SN—PDU is using at the LLC layer.
`
`Segment offset
`
`Indicates the offset from the beginning of the N-PDU.
`
`SNDCP entity
`
`The SNDCP entity handles the service functions provided by the SNDCP layer. The
`SNDCP entity is temporary logical link identity specific.
`
`SNDCP management entity The SNDCP management entity handles communication with SM sub-layer and controls
`the operation of the SNDCP entity.
`
`SNDCP user
`
`Protocol entity that is using the services provided by the SNDCP layer. PDP entities and
`control entities, e.g., AT command interpreter, are the SNDCP users at the MS. Relay
`entity is the SNDCP user at the SGSN.
`
`Refer to GSM 02.60 [2] for further GPRS definitions.
`
`3.2
`
`Abbreviations
`
`In addition to abbreviations in 01.04 [1] and 02.60 [2] the following abbreviations apply:
`
`DCOMP
`E
`IP
`
`GMM
`LLC
`M
`
`Identifier of the user data compression algorithm used for the N-PDU
`Extension bit
`Internet Protocol
`
`GPRS Mobility Management
`Logical Link Control
`More bit used to indicate the last segment of N-PDU
`
`ETSI
`
`ZTE Corporation and ZTE (USA) Inc.
`Exhibit 1005.08-00007
`
`

`

`GSM 04.65 version 6.1.0 Release 1997
`
`8
`
`TS 101 297 V6.1.0 (1998-07)
`
`N-PDU
`
`NSAPI
`PCOMP
`PDP
`PDU
`PTP
`
`QoS
`SAPI
`SDU
`
`SGSN
`SM
`SNDCP
`SNSM
`TCP
`
`TLLI
`X
`
`Network Protocol Data Unit
`
`Network Layer Service Access Point Identifier
`Identifier of the protocol control information compression algorithm used for the N-PDU
`Packet Data Protocol e.g., IP or X.25
`Protocol Data Unit
`Point to Point
`
`Quality of Service
`Service Access Point Identifier
`Service Data Unit
`
`Serving GPRS Support Node
`Session Management
`Subnetwork Dependent Convergence Protocol
`SNDCP-SM
`Transmission Control Protocol
`
`Temporary Logical Link Identifier
`Spare bit.
`
`4
`
`General
`
`This document describes the functionality of the GPRS SNDCP. The overall GPRS logical architecture is defined in
`GSM 03.60 [3]. Location ofthe SNDCP in GPRS protocol stack can be seen in Figure 1.
`
` Application
`
`
`SNDCP
`LLC LLC
`RLC
`BSSGP
`Nctwork
`Nctwork
`Service " Service
`Ll
`. -
`
`Gb
`SGSN
`
`
`
`
`UDP/
`
`TCP
`
`L2
`
`IP/X.25
`
`____________ _ _
`
`
`.
`
`Um
`MS
`
`BSS
`
`Figure 1: GPRS protocol stack
`
`Network layer protocols are intended to be capable of operating over services derived from a wide variety of
`subnetworks and data links. GPRS supports several network layer protocols providing protocol transparency for the
`users of the service. Introduction of new network layer protocols to be transferred over GPRS shall be possible without
`any changes to GPRS. Therefore, all functions related to transfer of Network layer Protocol Data Units (N—PDUs) shall
`be carried out in a transparent way by the GPRS network entities. This is one of the requirements for GPRS SNDCP.
`
`Another requirement for the SNDCP is to provide functions that help to improve channel efficiency. This requirement is
`fulfilled by means of compression techniques.
`
`The set of protocol entities above SNDCP consists of commonly used network protocols. They all use the same SNDCP
`entity, which then performs multiplexing of data coming from different sources to be sent using the service provided by
`the LLC layer (figure 2). The Network Service Access Point Identifier (NSAPI) is an index to the PDP context (see
`GSM 03.60 [3]) of the PDP that is using the services provided by SNDCP. One PDP may have several PDP contexts
`and NSAPIs. However, it is possible that each allocated NSAPI is used by separate PDP. Each active NSAPI shall use
`the services provided by the Service Access Point Identifier (SAPI) in the LLC layer. Several NSAPIs may be
`associated with the same SAPI.
`
`ETSI
`
`ZTE Corporation and ZTE (USA) Inc.
`Exhibit 1005.08-00008
`
`

`

`GSM 04.65 version 6.1.0 Release 1997
`
`9
`
`TS 101 297 V6.1.0 (1998-07)
`
`Since the adaptation of different network layer protocols to SNDCP is implementation dependent, it is not defined in
`this document.
`
`Packet Data
`Protocol
`
`N-PDU
`
`Packet Data
`Protocol
`
`Packet Data
`Protocol
`
`SN-PDU
`
`Figure 2: Example for multiplexing of different protocols
`
`5
`
`Service Primitives and Functions
`
`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
`
`ZTE Corporation and ZTE (USA) Inc.
`Exhibit 1005.08-00009
`
`

`

`GSM 04.65 version 6.1.0 Release 1997
`
`10
`
`TS 101 297 V6.1.0 (1998-07)
`
`Control
`
`
`
`SNDCP users
`
`Entity
`
`
`SNDCP layer
`
`
`SNDCP
`management
`entity
`
`_
`SNDCP entity
`
`
`
`Session
`Management entity
`
`SAPI
`
`
`
`LLC layer
`
`Figure 3: Service Access Points provided and used by SNDCP
`
`5.1.1
`
`SNDCP Service Primitives
`
`The primitives provided by the SNDCP layer are listed in Table 1.
`
`Table 1: SNDCP layer service primitives
`
`Parameters
`
`
`
`
`
`
`
`
`
`
`
`-- N*"’U’NS‘“”‘
`
`N—PDU, NSAPI,
`protection mode
`
`
`Requested SNDCP XID
`parameters
`
`
`
`Negotiated SNDCP XID
`parameters
`
`
`Generic
`
`
`N‘"““
`
`
`
`
`
`
`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.
`
`ETSI
`
`ZTE Corporation and ZTE (USA) Inc.
`Exhibit 1005.08-00010
`
`

`

`
`
`
`
`
`GSM 04.65 version 6.1.0 Release 1997
`
`11
`
`TS 101 297 V6.1.0 (1998-07)
`
`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.
`
`5.1.1.3
`
`SN-UN|TDATA.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 and protection mode to identify the requested transmission mode.
`
`5.1.1.4
`
`SN-UN|TDATA.indicati0n
`
`Indication used by the SNDCP entity to deliver the received N-PDU to the SNDCP user.
`
`5.1.1.5
`
`SN-X|D.request
`
`Request used by the SNDCP user at the initiating entity to deliver the list of requested XID parameters to the peer entity.
`
`
`
`
`
`
`
`
`
`
`
`5.1.1.6
`
`SN-X|D.indication
`
`Indication used by the SNDCP entity to deliver the list of requested XID parameters to the SNDCP user.
`
`5.1.1.7
`
`SN-X|D.response
`
`Response used by the SNDCP user to deliver the list of negotiated XID parameters to the peer entity.
`
`5.1.1.8
`
`SN-X|D.confirm
`
`Confirm used by the SNDCP entity to deliver the list of negotiated XID parameters to the SNDCP user.
`
`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
`
`ZTE Corporation and ZTE (USA) Inc.
`Exhibit 1005.08-00011
`
`

`

`GSM 04.65 version 6.1.0 Release 1997
`
`12
`
`TS 101 297 V6.1.0 (1998-07)
`
`Table 2: Service primitives used by the SNDCP entity
`
`Parameters
`
`Generic
`Na“
`
`LL-ESTABLI SH
`
`LL-ESTABLISH
`
`LL-XID
`
`LL-XID
`
`X
`
`X
`
`TLLI, XID Requested,
`N20l—I, N20l—U
`
`X
`
`TLLI, XID Negotiated,
`N201-I, N201-U
`
`TLLI, XID Requested,
`N201—I, N201—U
`
`X
`
`TLLI, XID Negotiated,
`N201-I, N201-U
`
`TLLI, SN—PDU,
`Reference
`
`LL—DATA
`
`X
`
`-2- W“
`
`Protection mode, Cipher
`
`TLLI, NSAPI, QoS
`profile, Ack/Unack
`indicator, SAPI
`
`TLLI, \ SAPI(s), LLC
`release indicator
`
`TLLI, \ SAPI, QoS
`profile, SAPI
`
`SNDCP <---> SM
`
`SNSM—ACTIVATE
`
`S\ SVLDEACTIVATE
`
`S\ SVI-MODIFY
`
`X
`
`X
`
`X
`
`ETSI
`
`ZTE Corporation and ZTE (USA) Inc.
`Exhibit 1005.08-00012
`
`

`

`
`
`TS 101 297 V6.1.0 (1998-07)
`
`
`5.1.2.1
`
`LL-ESTABL|SH.request
`
`GSM 04.65 version 6.1.0 Release 1997
`
`
`
`
`
`Request used by the SNDCP layer to establish acknowledged peer-to-peer operation in the LLC layer. The request may
`be used by the SNDCP layer to deliver the requested SNDCP XID parameters to the LLC layer. XID Requested is used
`to negotiate SNDCP parameters.
`
`
`
`5.1.2.2
`
`LL-ESTABL|SH.indication
`
`
`
`
`Indication used by the LLC layer to inform SNDCP layer about establishment of acknowledged peer—to—peer operation
`in the LLC layer. XID Requested is used to negotiate SNDCP parameters. In case the received LLC frameincludes the
`
`requested SNDCP XID parameters, the indication shall be used by the LLC layer to deliver the requested SNDCP XID
`
`parameters to the SNDCP layer. In case of a link re—establishment, all buffered N—PDUs (i.e. the one whose complete
`
`reception has not been acknowledged and the one which has not bee transmitted yet) are to be transmitted starting with
`the oldest N-PDU when the link is re-established. Also any compression entities associated to this LLC link at the
`SNDCP layer are reset.
`
`
`
`
`
`
`
`Confirm used by the LLC layer to inform SNDCP layer about successful initiation of acknowledged peer—to—peer
`operation in the LLC layer. XID Negotiated is used to negotiate SNDCP parameters. In case the LLC frameincludes the
`
`negotiated SNDCP XID parameters, the confirm shall be used by the LLC layer to deliver the negotiated SNDCP XID
`
`parameters to the SNDCP layer. In case of a link re—establishment, all buffered N—PDUs (i.e. the one whose complete
`
`reception has not been acknowledged and the one which has not bee transmitted yet) are to be transmitted starting with
`the oldest N-PDU when the link is re-established. Also any compression entities associated to this LLC link at the
`SNDCP layer are reset.
`
`
`
`5.1.2.3
`
`LL-ESTABL|SH.response
`
`Response used by the SNDCP layer after reception of the LL—ESTABLISH.indication. XID Negotiated is used to
`negotiate SNDCP parameters. In case the LL—ESTABLISH.indication included the requested SNDCP XID parameters,
`the response shall be used by the SNDCP layer to deliver the negotiated SNDCP XID parameters to the LLC layer.
`
`5.1.2.4
`
`LL—ESTABL|SH .C0n'firm
`
`
`
`
`
`
`Indication used by the LLC layer to inform SNDCP layer about termination of acknowledged peer-to-peer operation in
`
`the LLC layer. The primitive is triggered by the reception of disconnect mode (DISC) LL—PDU in the LLC layer.
`
`If the SNDCP entity receives LL—RELEASE.indication while there are still N—PDUs to be transmitted on that logical
`link, the SNDCP entity shall establish a new logical link using the LL-ESTABLISH.request. On receipt of LL-
`
`RELEASE.indication, compressed N—PDUs queuing to be forwarded to LLC-layer are deleted from the SNDCP layer.
`Also any compression entities associated to this LLC link are reset.
`
`
`
`
`
`
`
`
`
`
`
`5.1.2.5
`
`LL—RELEASE.request
`
`Request used by the SNDCP layer to release acknowledged peer-to-peer operation in the LLC layer.
`
`5.1.2.6
`
`LL—RELEASE.indication
`
`5.1.2.7
`
`LL-RELEASE.confirm
`
`Confirm used by the LLC layer to inform SNDCP layer about termination of acknowledged peer—to—peer operation in the
`LLC layer. On receipt of LL-RELEASE.confirm, compressed N—PDUs queuing to be forwarded to LLC-layer are
`deleted from the SNDCP layer. Also any compression entities associated to this LLC link at the SNDCP are reset.
`
`5.1.2.8
`
`LL-X|D.request
`
`Request used by the SNDCP layer to deliver the requested SNDCP XID parameters to the LLC layer.
`
`5.1.2.9
`
`LL-X|D.indiCati0n
`
`
`
`Indication used by the LLC layer to deliver the requested SNDCP XID parameters to the SNDCP layer.
`
`ETSI
`
`ZTE Corporation and ZTE (USA) Inc.
`Exhibit 1005.08-00013
`
`

`

`GSM 04.65 version 6.1.0 Release 1997
`
`
`TS 101 297 V6.1.0 (1998-07)
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`5.1.2.10
`
`LL-X|D.response
`
`Response used by the SNDCP layer to deliver the negotiated SNDCP XID parameters to the LLC layer.
`
`5.1.2.11
`
`LL-X|D.Confirm
`
`Confirm used by the LLC layer to deliver the negotiated SN DCP XID parameters to the SN DCP layer.
`
`5.1.2.12
`
`LL-DATA.request
`
`Request used by the SNDCP layer for acknowledged transmission of a SN—PDU. The SNDCP entity shall associate a
`reference parameter for each LL—DATA.request.
`
`The logical link shall be established using the LL-ESTABLISH primitives, before the LL-DATA.request may be used.
`
`5.1.2.13
`
`LL-DATA.indication
`
`Indication used by the LLC layer to deliver the successfully received SN—PDU to the SNDCP layer.
`
`5.1.2.14
`
`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.
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`5.1.2.15
`
`LL—DATASENT.indication
`
`The LL—DATASENT.indication primitive is used by the LLC layer in acknowledged mode in the SGSN to inform
`SNDCP of which LLC send sequence number that was assigned to an LLC PDU. SNDCP uses this information to
`associate the LLC send sequence number with the corresponding N—PDU.
`
`5.1.2.16
`
`LL-LIN|TDATA.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 mode does not need to be established before unacknowledged transmission is allowed.
`
`5.1.2.17
`
`LL-UN|TDATA.indication
`
`Indication used by the LLC layer to deliver the received SN—PDU to the SNDCP layer.
`
`There is no need for logical link on the acknowledged—peer—to—peer mode for unacknowledged transmission of SN—PDU.
`
`5.1.2.18
`
`SNSM—ACTIVATE.indication
`
`Indication used by the SM entity to establish or reuse the acknowledged peer-to-peer LLC operation for a specific
`NSAPI during the ongoing PDP Context Activation procedure. This primitive is used by the SM entity to inform the
`SNDCP entity about the NSAPI and the related SAPI that has been allocated for the use of the SNDCP entity.
`
`Upon reception of the SNSM—ACTIVATE.indication from the SM sublayer, the SNDCP entity of the MS shall use the
`LL-ESTABLISH.request primitive to establish the acknowledged peer-to-peer LLC operation, as requested for a
`specific NSAPI. If an appropriate acknowledged peer-to-peer operation (including the requested XID parameters) is
`already up and running, there is no need for re—establishment of the link. If an acknowledged peer-to-peer operation is
`already up and running but the XID parameters are not correct, the SN DCP entity shall issue LL-XID-request to
`negotiate the requested XID parameters.
`
`
`
`ETSI
`
`ZTE Corporation and ZTE (USA) Inc.
`Exhibit 1005.08-00014
`
`

`

`15
`
`TS 101 297 V6.1.0 (1998-07)
`
`SNSM-ACT|VATE.resp0nse
`
`Response used by the SNDCP layer to inform SM entity that the acknowledged peer-to-peer operation mode is up and
`running with the requested XID parameters.
`
`5.1.2.20
`
`SNSM-DEACTIVATE.indicati0n
`
`GSM 04.65 version 6.1.0 Release 1997
`
`
`
`5.1.2.19
`
`