TIA-102 BAED-2013 Project 25 Packet Data Logical Link Control Procedures.pdf

1、 TIA-102.BAED October 2013Project 25 Packet Data Logical Link Control Procedures ANSI/TIA-102.BAED-2013 APPROVED: SEPTEMBER 26, 2013 NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers,

2、 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 Standards and Publications shall not in any respect preclude any member or non-member of TIA fro

3、m 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 domestically or internationally. Standards and Publications are adopted by TIA in accordance w

4、ith 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 Standard or Publication. This Standard does not purport to address all safety problems associa

5、ted 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 regulatory limitations before its use. (From Project No. ANSI/TIA-PN-102.BAED, formulated under

6、 the cognizance of the TIA TR-8 Mobile and Personal Private Radio Standards, TR-8.5 Subcommittee on Signaling and Data Transmission). Published by TELECOMMUNICATIONS INDUSTRY ASSOCIATION Technology (b) there is no assurance that the Document will be approved by any Committee of TIA or any other body

7、 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 Document may involve the use of intellectual property rights (“IPR”), including pending or issued patents, or copyright

8、s, 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 attention, a statement from the holder thereof is requested, all in accordance with the Manual. TIA takes no position

9、 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 terms or conditions, which are instead left to the parties involved, nor will TIA opine or judge whether proposed l

10、icensing 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 with as respects the Document or its contents. If the Document contains one or more Normative References to a docum

11、ent published by another organization (“other SSO”) engaged in the formulation, development or publication of standards (whether designated as a standard, specification, recommendation or otherwise), whether such reference consists of mandatory, alternate or optional elements (as defined in the TIA

12、Engineering Manual, 4thedition) 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 to any such Normative Reference; (ii) TIAs policy of encouragement of voluntary disclosure (see Engineering Manual Section 6.5.

13、1) of Essential Patent(s) and published pending patent applications shall apply; and (iii) Information as to claims of IPR in the records or publications of the other SSO shall not constitute identification to TIA of a claim of Essential Patent(s) or published pending patent applications. TIA does n

14、ot enforce or monitor compliance with the contents of the Document. TIA does not certify, inspect, test or otherwise investigate products, designs or services or any claims of compliance with the contents of the Document. ALL WARRANTIES, EXPRESS OR IMPLIED, ARE DISCLAIMED, INCLUDING WITHOUT LIMITATI

15、ON, ANY AND ALL WARRANTIES CONCERNING THE ACCURACY OF THE CONTENTS, ITS FITNESS OR APPROPRIATENESS FOR A PARTICULAR PURPOSE OR USE, ITS MERCHANTABILITY AND ITS NONINFRINGEMENT OF ANY THIRD PARTYS INTELLECTUAL PROPERTY RIGHTS. TIA EXPRESSLY DISCLAIMS ANY AND ALL RESPONSIBILITIES FOR THE ACCURACY OF T

16、HE CONTENTS AND MAKES NO REPRESENTATIONS OR WARRANTIES REGARDING THE CONTENTS COMPLIANCE WITH ANY APPLICABLE STATUTE, RULE OR REGULATION, OR THE 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 SHA

17、LL NOT BE LIABLE FOR ANY AND ALL DAMAGES, DIRECT OR INDIRECT, ARISING FROM OR RELATING TO ANY USE OF THE CONTENTS CONTAINED HEREIN, INCLUDING WITHOUT LIMITATION ANY AND ALL INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES (INCLUDING DAMAGES FOR LOSS OF BUSINESS, LOSS OF PROFITS, LITIGATION, OR

18、 THE LIKE), WHETHER BASED UPON BREACH OF CONTRACT, BREACH OF WARRANTY, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR OTHERWISE, EVEN IF ADVISED 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 WOU

19、LD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. TIA-102.BAED i Foreword (This foreword is not part of this document.) This document has been created in response to a request by the APCO/NASTD/FED1Project 25 Steering Committee as provided for in a Memorandum of Understanding (MOU) dated April 19

20、92 and amended December 1993. The MOU states APCO/NASTD/FED shall devise a Common System Standard for digital public safety communications (the Standard) commonly referred to as Project 25 or P25, and that TIA, as agreed to by the membership of the appropriate TIA Engineering Committee, will provide

21、 technical assistance in the development of documentation for the Standard. If the abbreviation “P25” or the wording “Project 25” appears on the cover sheet of this document when published that indicates the APCO/NASTD/FED Project 25 Steering Committee has adopted this document as part of the Standa

22、rd. The appearance of the abbreviation “P25” or the wording “Project 25” on the cover sheet of this document or in the title of any document referenced herein should not be interpreted as limiting the applicability of the information contained in any document to “P25” or “Project 25” implementations

23、 exclusively. This document provides a specification of the Packet Data Logical Link Control (LLC) Procedures for TIA-102 Packet Data. This document was developed by the TIA TR-8.5 Signaling and Data Transmission Subcommittee based on materials originated by the TIA TR-8.15 Common Air Interface Subc

24、ommittee. The 1stedition (Original) of this document provides a standalone document for the Packet Data LLC Procedures based on material originally published in TIA-102.BAAD-A. This document cancels and replaces the material specific to the Packet Data LLC procedures specified in Annex E of TIA-102.

25、BAAD-A. The TIA makes no claims as to the applicability of the information contained in this document for any purpose although it is believed that the information will prove to be invaluable to manufacturers and operators of equipment based on the TIA-102 series of documents. Some aspects of the spe

26、cifications contained in this document may not have been fully operationally tested; however, a great deal of time and good faith effort has been invested in the preparation of this document to ensure the accuracy of the information it contains. 1APCO/NASTD/FED is an abbreviation for the Association

27、 of Public-Safety Communications Officials (APCO), the National Association of State Telecommunications Directors (NASTD), and the various agencies of the Federal government (FED). TIA-102.BAED ii Patent Identification The readers attention is called to the possibility that compliance with this docu

28、ment may require the use of one or more inventions covered by patent rights. By publication of this document, no position is taken with respect to the validity of those claims or any patent rights in connection therewith. The patent holders so far identified have, we believe, filed statements of wil

29、lingness to grant licenses under those rights on reasonable and nondiscriminatory terms and conditions to applicants desiring to obtain such licenses. The following patent holders and patents have been identified in accordance with the TIA intellectual property rights policy: No patents have been id

30、entified TIA shall not be responsible for identifying patents for which licenses may be required by this document or for conducting inquiries into the legal validity or scope of those patents that are brought to its attention. TIA-102.BAED iii Table of Contents 1. Introduction . 1 1.1 Scope . 1 1.2

31、References . 1 1.2.1 Normative References 1 1.2.2 Informative References 2 1.3 Acronyms and Abbreviations 2 1.4 Definitions . 3 1.5 Conventions . 4 1.5.1 Symbols 4 2. Architecture 5 2.1 Addressing . 5 2.1.1 Symmetric Addressing 5 2.1.2 Asymmetric Addressing 5 3. Procedures 6 3.1 Receiver Preprocessi

32、ng . 6 3.1.1 NAC Qualification . 7 3.1.2 MFID Qualification 7 3.1.3 Address Qualification 7 3.2 Confirmed Data Packet Conveyance 7 3.2.1 Sequence Numbering . 7 3.2.2 Resynchronization of Sequence Numbers . 9 3.2.3 Fragments 9 3.2.4 Responses . 10 3.2.5 Sender Confirmed Logical Message Procedure . 10

33、 3.2.6 Receiver Confirmed Data Packet/Logical Message Procedure 13 3.3 Unconfirmed Data Packet Conveyance 17 3.3.1 Sequence Numbering . 17 3.3.2 Fragments 17 3.3.3 Responses . 17 3.3.4 Sender Unconfirmed Logical Message Procedure . 17 3.3.5 Receiver Unconfirmed Data Packet Procedure 18 TIA-102.BAED

34、iv List of Figures Figure 1 Context of Sequence Numbers . 8 Figure 2 Sender Confirmed Logical Message Procedure State Diagram . 10 Figure 3 Receiver Confirmed Data Packet Procedure State Diagram 14 List of Tables Table 1 Data Packet Conveyance Methods 6 Table 2 Suggested Limit Constants . 6 Table 3

35、FSNF Values 9 Table 4 Subset of Response Packet Meanings . 10 Table 5 Response Disposition . 13 TIA-102.BAED v Revision History Version Date Description Original 08/21/2013 Packet Data Logical Link Control (LLC) Procedures based on material originally published in TIA-102.BAAD-A; adopted by the Proj

36、ect 25 Steering Committee August 17th2013 as part of the Project 25 Standard TIA-102.BAED vi This page intentionally left blank TIA-102.BAED 1 1. Introduction The objective of this document is to provide a specification of the Logical Link Control (LLC) procedures for TIA-102 Packet Data Service spe

37、cified in 6. 1.1 Scope This document specifies the LLC procedures that permit the conveyance of Common Air Interface (CAI) data packets between air interface endpoints for all relevant packet data configurations. The information necessary to enable interoperable LLC procedures for Packet Data is pro

38、vided in this document or referenced in other documents as appropriate. This document assumes the reader has a good working knowledge of the Data Overview and Specification 6. The functions allocated to the LLC procedures include the following major aspects: Confirmed and unconfirmed CAI data packet

39、 conveyance Segmentation and re-assembly of logical messages 1.2 References The appearance of “Project 25” in references below indicates the TIA document has been adopted by the APCO/NASTD/FED Project 25 Steering Committee as part of its Project 25 standard, i.e. “the Standard.” 1.2.1 Normative Refe

40、rences The following documents contain provisions that, through reference in this text, constitute provisions of this document. At the time of publication, the editions indicated were valid. All documents are subject to revision, and parties to agreements based on this document are encouraged to inv

41、estigate the possibility of applying the most recent editions of the documents indicated below. ANSI and TIA maintain registers of currently valid national standards published by them. 1 TIA-102.AAAD-A, Project 25 Digital Land Mobile Radio Block Encryption Protocol, ANSI/TIA, August 2009 2 TIA-102.A

42、ABD-A, Trunking Procedures, TIA, December 2008 3 TIA-102.BAAA-A, Project 25 FDMA Common Air Interface, ANSI/TIA, September 2003 4 TIA-102.BAAC-C, Project 25 Common Air Interface Reserved Values, ANSI/TIA, April 2011 5 TIA-102.BAAD-A, Project 25 Conventional Procedures, TIA, February 2010 6 TIA-102.B

43、AEA-B, Project 25 Data Overview and Specification, ANSI/TIA, June 2012 7 TIA-102.BAEJ, Project 25 Conventional Management Service Specification for Packet Data, ANSI/TIA, August 2013 TIA-102.BAED 2 1.2.2 Informative References None 1.3 Acronyms and Abbreviations 2ndary Secondary ACK Acknowledgement

44、ANSI American National Standards Institute APCO Association of Public-Safety Communications Officials BTF Blocks To Follow CAI Common Air Interface CMS Conventional Management Service CRC Cyclic Redundancy Check FDMA Frequency Division Multiple Access FED Various Agencies of the Federal Government F

45、MF Full Message Flag FNE Fixed Network Equipment FSN Fragment Sequence Number FSNF Fragment Sequence Number Field FSRFixed Station Repeater ID Identifier LIC Last In Chain LLC Logical Link Control LLID Logical Link Identifier NAC Network Access Code NACK Negative Acknowledgement NASTD National Assoc

46、iation of State Telecommunications Directors NID Network Identifier P25 Project 25 PDU Protocol Data Unit RX Receive SACK Selective Acknowledgement SAP Service Access Point SNDCP Subnetwork Dependent Convergence Protocol SU Subscriber Unit TIA Telecommunications Industry Association TX Transmit TIA-

47、102.BAED 3 1.4 Definitions BTF Number of data blocks following header block of data packet; further defined in 3 CRCBLOCK9-bit CRC for each data block of data packet; further defined as CRC-9 in 3 CRCHEADER16-bit CRC for header block of data packet; further defined as Header CRC in 3 CRCLAST32-bit C

48、RC for the last successfully received data packet CRCPACKET32-bit CRC for all data blocks of data packet; further defined as Packet CRC in 3 Data Packet Implies “CAI Data Packet” throughout this document FMF See definition in 3 FNE See definition in 6 Frame Sync See definition in 3 FSN Sequence numb

49、er for data packets within a logical message. Part of the FSNF; further defined in 3 FSNF Contains FSN and LIC fields; further defined in 3 FSRSee definition in 6 L Number of octets in a logical message fragment. Includes headers added by LLC. LIC Last fragment in chain flag in FSNF; further defined in 3 LLID See definition for Logical Link Identifier in 3 Local Policy See definition in 6 Logical Message A PDU of the sending or receiving SAP. It may be fragmented prior to being encapsulated in one or more data packets fo