TIA-136-333-2000 TDMA - Third Generation Wireless - Packet Data Service - Logical Link Control (ANSI APPROVAL WITHDRAWN JUNE 12 2015).pdf

《TIA-136-333-2000 TDMA - Third Generation Wireless - Packet Data Service - Logical Link Control (ANSI APPROVAL WITHDRAWN JUNE 12 2015).pdf》由会员分享，可在线阅读，更多相关《TIA-136-333-2000 TDMA - Third Generation Wireless - Packet Data Service - Logical Link Control (ANSI APPROVAL WITHDRAWN JUNE 12 2015).pdf（38页珍藏版）》请在麦多课文档分享上搜索。

1、 ANSI/TIA-136-333-2000 APPROVED: MARCH 31, 2000 REAFFIRMED: OCTOBER 20, 2004 REAFFIRMED: AUGUST 14, 2013 WITHDRAWN: JUNE 12, 2015 TIA-136-333 March 2000TDMA Third Generation Wireless- Packet Data Service- Logical Link Control NOTICE TIA Engineering Standards and Publications are designed to serve th

2、e public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for their particular need. The existence of such Sta

3、ndards and Publications shall not in any respect preclude any member or non-member of TIA from manufacturing or selling products not conforming to such Standards and Publications. Neither shall the existence of such Standards and Publications preclude their voluntary use by Non-TIA members, either d

4、omestically or internationally. Standards and Publications are adopted by TIA in accordance with the American National Standards Institute (ANSI) patent policy. By such action, TIA does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the S

5、tandard or Publication. This Standard does not purport to address all safety problems associated with its use or all applicable regulatory requirements. It is the responsibility of the user of this Standard to establish appropriate safety and health practices and to determine the applicability of re

6、gulatory limitations before its use. Any use of trademarks in this document are for information purposes and do not constitute an endorsement by TIA or this committee of the products or services of the company. (From Project No. ANSI/TIA-PN-136.333-RF2-WD, formulated under the cognizance of the TIA

7、TR-45 Mobile (b) there is no assurance that the Document will be approved by any Committee of TIA or any other body in its present or any other form; (c) the Document may be amended, modified or changed in the standards development or any editing process. The use or practice of contents of this Docu

8、ment may involve the use of intellectual property rights (“IPR”), including pending or issued patents, or copyrights, owned by one or more parties. TIA makes no search or investigation for IPR. When IPR consisting of patents and published pending patent applications are claimed and called to TIAs at

9、tention, a statement from the holder thereof is requested, all in accordance with the Manual. TIA takes no position with reference to, and disclaims any obligation to investigate or inquire into, the scope or validity of any claims of IPR. TIA will neither be a party to discussions of any licensing

10、terms or conditions, which are instead left to the parties involved, nor will TIA opine or judge whether proposed licensing terms or conditions are reasonable or non-discriminatory. TIA does not warrant or represent that procedures or practices suggested or provided in the Manual have been complied

11、with as respects the Document or its contents. If the Document contains one or more Normative References to a document published by another organization (“other SSO”) engaged in the formulation, development or publication of standards (whether designated as a standard, specification, recommendation

12、or otherwise), whether such reference consists of mandatory, alternate or optional elements (as defined in the TIA Procedures for American National Standards) then (i) TIA disclaims any duty or obligation to search or investigate the records of any other SSO for IPR or letters of assurance relating

13、to any such Normative Reference; (ii) TIAs policy of encouragement of voluntary disclosure (see TIA Procedures for American National Standards Annex C.1.2.3) of Essential Patent(s) and published pending patent applications shall apply; and (iii) Information as to claims of IPR in the records or publ

14、ications of the other SSO shall not constitute identification to TIA of a claim of Essential Patent(s) or published pending patent applications. TIA does not enforce or monitor compliance with the contents of the Document. TIA does not certify, inspect, test or otherwise investigate products, design

15、s or services or any claims of compliance with the contents of the Document. ALL WARRANTIES, EXPRESS OR IMPLIED, ARE DISCLAIMED, INCLUDING WITHOUT LIMITATION, ANY AND ALL WARRANTIES CONCERNING THE ACCURACY OF THE CONTENTS, ITS FITNESS OR APPROPRIATENESS FOR A PARTICULAR PURPOSE OR USE, ITS MERCHANTA

16、BILITY AND ITS NONINFRINGEMENT OF ANY THIRD PARTYS INTELLECTUAL PROPERTY RIGHTS. TIA EXPRESSLY DISCLAIMS ANY AND ALL RESPONSIBILITIES FOR THE ACCURACY OF THE CONTENTS AND MAKES NO REPRESENTATIONS OR WARRANTIES REGARDING THE CONTENTS COMPLIANCE WITH ANY APPLICABLE STATUTE, RULE OR REGULATION, OR THE

17、SAFETY OR HEALTH EFFECTS OF THE CONTENTS OR ANY PRODUCT OR SERVICE REFERRED TO IN THE DOCUMENT OR PRODUCED OR RENDERED TO COMPLY WITH THE CONTENTS. TIA SHALL NOT BE LIABLE FOR ANY AND ALL DAMAGES, DIRECT OR INDIRECT, ARISING FROM OR RELATING TO ANY USE OF THE CONTENTS CONTAINED HEREIN, INCLUDING WIT

18、HOUT LIMITATION ANY AND ALL INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES (INCLUDING DAMAGES FOR LOSS OF BUSINESS, LOSS OF PROFITS, LITIGATION, OR THE LIKE), WHETHER BASED UPON BREACH OF CONTRACT, BREACH OF WARRANTY, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR OTHERWISE, EVEN IF ADVIS

19、ED OF THE POSSIBILITY OF SUCH DAMAGES. THE FOREGOING NEGATION OF DAMAGES IS A FUNDAMENTAL ELEMENT OF THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. TIA/EIA - 136 - 33 3 iForeword This forewor d is not part of TIA/EIA - 136 - 333 TIA/EIA - 1

20、36 - 333 specifies the Logical Link Control (LLC) for packet - data servic e (GPRS - 136). The LLC is used for packet - data transfer between the Mobile Station (MS) and the Serving GPRS Support Node (SGSN). LLC is intended for use with both acknowledged and unacknowledged data transfer. TIA/EIA - 1

21、36 - 333 was developed by TR45.3.2, the Data Services Working Group of TR45 - 3, the TIA/EIA TDMA Wireless Standards Subcommittee . This document references publications developed by ETSI (European Telecommunications Standards Institute). These referenced publications are freely available at http:/w

22、ww.etsi.org . TIA welcomes suggestions for improvement of this standard. Please send suggestions to the following address: Telecommunications Industry Association 2500 Wilson Boulevard - Suite 300 Arlington VA 22201 - 383 6 TIA/EIA - 136 - 333 iiTHIS PAGE INTENTIONALLY LEFT BLANK TIA/EIA - 136 - 33

23、3 iiiContents 1. Scope 1 2. Definitions and abbreviations 1 3. Overview description of LLC functions and procedures 2 3.1 Reference model 2 3.2 General description of the LLC protocol 3 3.3 Unacknowledged operation 3 3.4 Acknowledged operation . 3 3.5 Establishment of information transfer modes . 3

24、3.6 Data confidentiality . 3 3.7 LLC layer structure 4 3.7.1 Logical Link Entity . 4 3.7.2 Multiplex procedure 4 3.7.3 Logical Link Management . 5 3.8 GPRS Mobility Management . 5 3.9 Short Message Service . 5 3.10 Tunnelling Of Messages 5 4. Frame structure . 6 5. Elements of procedures and formats

25、 of fields . 7 5.1 General 7 5.2 Address field format and variabl es . 7 5.2.1 Protocol Discriminator bit (PD) . 7 5.2.2 Command/Response bit (C/R) . 7 5.2.3 Service Access Point Identifier (SAPI) . 7 5.3 Contr ol field formats, parameters, and variables 8 5.4 Commands and responses 8 5.4.1 Unnumber

26、ed (U) frames 8 5.4.1.1 Set Asynchronous Balanced Mode (SABM) command 8 5.4.1.2 Disconnect (DISC) command 8 5.4.1.3 Unnumbered Acknowledgement (UA) response 9 5.4.1.4 Disconnected Mode (DM) response 9 5.4.1.5 Fram e Reject (FRMR) response . 9 5.4.1.6 Exchange Identification (XID) command/response 9

27、5.4.2 Unconfirmed Information (UI) frame 12 5.4.3 Combined Information (I) and Sup ervisory (S) frames . 12 6. Elements for layer - to - layer communication 13 6.1 Definition of service primitives and parameters . 13 6.1.1 Primitives types . 13 TIA/EIA - 136 - 333 iv6.1.2 Generic names . 14 6.2 Prim

28、itive procedures 15 7. Definition of the LLC peer - to - peer protocol . 16 8. References 17 An nex A: Ciphering 18 Annex B: Tunnelling of Messages (TOM) 19 B.1 TOM Protocol Envelope structure 19 B.1.1 TOM Protocol Discriminator . 20 B.1.2 Remaining Length of TOM Protocol Header 20 B.1.3 Remaining O

29、ctets of TOM Protocol Header . 20 B.1.4 Message Capsule 21 Annex C: LLC layer states for peer - to - peer operation 22 TIA/EIA - 136 - 33 3 vFigures Figure 1: Protocol layering in GPRS . 2 Figure 2: Functional model of the LLC Layer . 4 Figure 3: XID parameter field format . 10 TIA/EIA - 136 - 333 v

30、iTables Table 1: Allocation of SAPI values 8 Table 2: LLC layer parameter negotiation 11 Table 3: LLC layer service primitives . 14 Table 9: LLC layer parameter default values 16 Table 4 : TOM Protocol Envelope Format . 19 Table 5: TOM Protocol Discriminator 20 Tabl e 6: TOM Protocol Header Length 2

31、0 TIA/EIA - 136 - 33 3 viiRevision History Revison Description TIA/EIA - 136 - 333 First revision TIA/EIA - 136 - 333 viiiTHIS PAGE INTENTIONALLY LEFT BLANK TIA/EIA - 136 - 33 3 11. Scope 1 This section is the same as Section 1 of GSM 04.64 3. 2 2. Definitions and abbreviations 3 This section is the

32、 same as Section 3 of GSM 04.64. 4 TIA/EIA - 136 - 333 23. Overview description of LLC functions 1 and procedures 2 This section is the same as Section 4 of GSM 04.64. 3 3.1 Reference model 4 A model of layering the protocol s in GPRS is illustrated in Figure 1. 5 Figure 1 : Protocol layering in GPR

33、S 6 Um GbMS BSS SGSNSNDC SMSGMMLLCRLCMACGSM RFRelayRLCMACGSM RFBSSGPNetworkServiceL1SNDC SMSGMMLLCBSSGPNetworkServiceL1TOM TOM7 The LLC layer operates above the RLC and BSSGP layers in the reference architecture 8 to provide logical links between an MS and its SGSN. 9 Above the LLC lay er is located

34、 the SubNetwork Dependent Convergence (SNDC) layer, 10 that controls the transfer of user data network layer PDUs (N - PDUs) between the MS 11 and SGSN. The SNDC functionality is described in GSM 03.60 and specified in 12 TIA/EIA - 136 - 334 4. 13 The logical link control layer Service Access Points

35、 (SAPs) are the points at which the 14 LLC layer provides services to the layer -3 protocols in Figure 1. In addition to the 15 SNDC protocol, LLC provides service to the GPRS Mobility Management (GMM) 16 protocol, to the SMS protocol, and to the Tunnelling of Messages (TOM) protocol. 17 An LLC laye

36、r connection is identified by the DLCI consisting of the SAP Identifier 18 (SAPI) and the MSs Temporary Logical Link Identifier (TLLI). 19 Each LLC frame consists of the header, trailer, an d information field. The header and 20 trailer fields contain information such as SAPI, frame number and check

37、sum, that are 21 TIA/EIA - 136 - 33 3 3used to identify the frame and to provide reliable transmission. The information field is 1 variable length. Both transmission and retran smission of each frame are controlled by 2 the LLC layer. 3 Many of the formats and procedures are similar to the reference

38、 protocols, and 4 differences are introduced only where needed to reflect the unique aspects of the GPRS 5 architecture and requirements. 6 3.2 Gen eral description of the LLC protocol 7 This subsection is the same as subsection 4.2 of GSM 04.64. 8 3.3 Unacknowledged operation 9 This subsection is t

39、he same as subsection 4.3 of GSM 04.64. 10 3.4 Acknowledged operation 11 With this type of operation, layer - 3 information is transmitted in order in numbered 12 Information (I) frames. The I frames are acknowledged at the LLC layer. Error recovery 13 and reordering procedures based on retransmissi

40、on of unacknowledged I frames are 14 specified. Several I frames may be unacknowledged at the same time. In the case of 15 errors that cannot be corrected by the logical link control layer, a report to GPRS 16 mobility management shall be made. 17 Flow control procedures are defined. 18 Acknowledged

41、 operation requires that ABM operation has been initiated by an 19 establishment procedure using the Set Asynchronous Balanced Mode (SABM) 20 command. 21 Acknowledged operation is allowed for all SAPIs that are not reserved (see Table 1) 22 except SAPIs 1, 2, 7, and 8. 23 3.5 Establishment of inform

42、ation transfer modes 24 This subsec tion is the same as subsection 4.5 of GSM 04.64. 25 3.6 Data confidentiality 26 This subsection is the same as subsection 4.6 of GSM 04.64. 27 TIA/EIA - 136 - 333 43.7 LLC layer structure 1 The LLC layer structure is shown in Figure 2. This figure is a model shown

43、 for 2 illustrative purposes onl y, and does not constrain implementations. 3 Figure 2 : Functional model of the LLC Layer 4 LogicalLinkEntitySAPI=7LogicalLinkEntitySAPI=8SGSNMSGPRS Mobility ManagementLogicalLinkManagementEntityMultiplex ProcedureLL5 LL9LL3 LL11SNDCPLLGMMSMSLogicalLinkEntitySAPI=2MA

44、CLogicalLinkEntitySAPI=11LogicalLinkEntitySAPI=9LogicalLinkEntitySAPI=5LogicalLinkEntitySAPI=3LogicalLinkEntitySAPI=1GRRLLGMMRR layerLLC layerLayer 3LLC layerBSSGPBSSGPBSSGP layerSignallingSignalling and data transferTOMTOM8 LLSMSTOM23.7.1 Logical Link Entity 5 This subsection is the same as subsect

45、ion 4.7.1 of GSM 04.64. 6 3.7.2 Multiplex procedure 7 This subsect ion is the same as subsection 4.7.2 of GSM 04.64. 8 TIA/EIA - 136 - 33 3 53.7.3 Logical Link Management 1 This subsection is the same as subsection 4.7.3 of GSM 04.64. 2 3.8 GPRS Mobility Management 3 This subsection is the same as s

46、ubsection 4.8 of GSM 04.64. 4 3.9 Short Message Service 5 This subse ction is the same as subsection 4.9 of GSM 04.64. 6 3.10 Tunnelling Of Messages 7 TOM is a generic protocol layer used for the exchange of TOM Protocol Envelopes 8 between the MS and the SGSN. TOM procedures are defined in Annex B.

47、 9 TIA/EIA - 136 - 333 64. Frame structure 1 This section is th e same as section 5.0 of GSM 04.64. 2 TIA/EIA - 136 - 33 3 75. Elements of procedures and formats of 1 fields 2 This section is the same as section 6 of GSM 04.64. 3 5.1 General 4 This subsection is the same as subsection 6.1 of GSM 04.

48、64. 5 5.2 Address field format and variables 6 This subsection i s the same as subsection 6.2 of GSM 04.64. 7 5.2.1 Protocol Discriminator bit (PD) 8 This subsection is the same as subsection 6.2.1 of GSM 04.64. 9 5.2.2 Command/Response bit (C/R) 10 This subsection is the same as subsection 6.2.2 of

49、 GSM 04.64. 11 5.2.3 Service Access Point Identi fier (SAPI) 12 SAPI identifies a point at which LLC services are provided by an LLE to a layer - 3 13 entity. Consequently, SAPI identifies an LLE that should process an LLC frame and also 14 a layer - 3 entity that is to receive information carried by the LLC frame. 15 TIA/EIA - 136 - 333 8S API allows 16 service access points to be specified. The SAPI values are allocated as 1 shown in Table 1 . 2 Table 1 : Allocation of SAPI values 3 SAPI Related