ANSI TIA-102.AABB-B-2011 Project 25 Trunking Control Channel Formats.pdf

《ANSI TIA-102.AABB-B-2011 Project 25 Trunking Control Channel Formats.pdf》由会员分享，可在线阅读，更多相关《ANSI TIA-102.AABB-B-2011 Project 25 Trunking Control Channel Formats.pdf（36页珍藏版）》请在麦多课文档分享上搜索。

1、 TIA-102.AABB-B (Revision of TIA-102.AABB-A) July 2011Trunking Control Channel Formats ANSI/TIA-102.AABB-B 2011 APPROVED: APRIL 22, 2011 NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchas

2、ers, 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

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

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

5、ociated 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. 3-4623-RV2, formulated under the c

6、ognizance of the TIA TR-8 Mobile and Personal Private Radio Standards, TR-8.10 Subcommittee on Trunking and Conventional Control. . Published by TELECOMMUNICATIONS INDUSTRY ASSOCIATION Standards and Technology Department 2500 Wilson Boulevard Arlington, VA 22201 U.S.A. PRICE: Please refer to current

7、 Catalog of TIA TELECOMMUNICATIONS INDUSTRY ASSOCIATION STANDARDS AND ENGINEERING PUBLICATIONS or call IHS, USA and Canada (1-877-413-5187) International (303-397-2896) or search online at http:/www.tiaonline.org/standards/catalog/ All rights reserved Printed in U.S.A. NOTICE OF COPYRIGHT This docum

8、ent is copyrighted by the TIA. Reproduction of these documents either in hard copy or soft copy (including posting on the web) is prohibited without copyright permission. For copyright permission to reproduce portions of this document, please contact the TIA Standards Department or go to the TIA web

9、site (www.tiaonline.org) for details on how to request permission. Details are located at: http:/www.tiaonline.org/standards/catalog/info.cfm#copyright or Telecommunications Industry Association Technology (b) there is no assurance that the Document will be approved by any Committee of TIA or any ot

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

11、opyrights, 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

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

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

14、 a document 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

15、the TIA 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 Sect

16、ion 6.5.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. TI

17、A does not 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

18、LIMITATION, 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 ACCUR

19、ACY OF THE 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.

20、 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 WITHOUT LIMITATION ANY AND ALL INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES (INCLUDING DAMAGES FOR LOSS OF BUSINESS, LOSS OF PROFITS, LITIGA

21、TION, OR 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 CONT

22、ENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. TIA-102.AABB-B i Foreword (This foreword is not part of the standard.) This document will be submitted to APCO/NASTD/FED by the Telecommunications Industry Association (TIA), as provided for in a Memorandum of Understanding (MoU) dated Dec

23、ember 1993. That MoU provides that APCO/NASTD/FED will devise a Common System Standard for digital public safety communications (the Standard), and that TIA shall provide technical assistance in the development of documentation for the Standard. This document has been developed with inputs from the

24、TIA/APCO Project 25 Interface Committee (APIC), the TR-8.10 Trunking and Conventional Control Subcommittee, and TIA Industry members. This document is being published because it is felt that there is an urgent need for technical information for the emerging digital systems for Land Mobile Radio Serv

25、ice. This document describes the general descriptions, packet structures, information block structures for both single and multiple block formats for trunked radios meeting the Project 25 requirements. These definitions are necessary to ensure interoperability of trunked radio units. This Standard p

26、resents a design for control channel bit structures which was recommended by TIA to APCO/NASTD/FED as being suitable for use as part of their standard for a digital public safety radio system (Project 25). TIA expects that APCO/NASTD/FED will establish and publish additional standards for trunking o

27、peration which will then provide the basis for additional TIA standards planned for the Project 25 system. There is one annex in this Standard. Annex A is informative and is not considered part of this Standard. TIA-102.AABB-B ii Contents 1 INTRODUCTION . 1 1.1 SCOPE . 1 1.2 REVISION HISTORY . 1 1.3

28、 REFERENCES 2 1.3.1 Normative References 2 1.3.2 Informative References 2 1.4 NUMBER NOMENCLATURE . 2 2 OVERVIEW . 4 2.1 CONTROL CHANNEL PACKETS . 4 2.2 PROTECTED CONTROL CHANNEL TRANSACTIONS . 5 3 GENERAL DESCRIPTIONS 6 3.1 CONTROL CHANNEL DESIGNATION 6 3.2 MODES OF CONTROL CHANNEL . 6 3.3 INBOUND

29、CONTROL CHANNEL ACCESS 7 4 PACKET STRUCTURE . 8 4.1 FRAME SYNC WORD . 8 4.2 NETWORK IDENTIFIER 8 4.3 STATUS SYMBOLS 9 4.4 DATA ERROR CORRECTION . 9 5 INFORMATION BLOCK STRUCTURE - SINGLE BLOCK PACKET 10 5.1 TRUNKING SIGNALING BLOCK FORMAT . 12 5.2 PROTECTED TSBK DESCRIPTION 14 5.3 EXAMPLE OF PROTECT

30、ED TSBKS - UNIT TO UNIT CALL 14 5.3.1 Service Request Packet 15 5.3.2 Service Response Packet 16 5.4 ISP TIMING 17 6 INFORMATION BLOCK STRUCTURE MULTIPLE BLOCK TRUNKING PACKET FORMAT 19 6.1 TRUNKING CONTROL PACKET HEADER FORMAT . 22 6.2 DATA BLOCK STRUCTURE . 24 6.3 PROTECTED MULTIPLE BLOCK TRUNKING

31、 PACKET DESCRIPTION 24 ANNEX A (INFORMATIVE): GLOSSARY OF TERMS . 25 Figures Figure 5-1 Single Block ISP Format 10 Figure 5-2 Single Block OSP Formats 11 Figure 5.1-1 Single Block Packet Transactions 12 Figure 5.3-1 ISP/OSP TSBKs for Unit to Unit call example . 15 Figure 5.4-1 ISP Timing Relationshi

32、ps . 17 Figure 6-1 Multiple Block ISP Formats 20 TIA-102.AABB-B iii Figure 6-2 Multiple Block OSP Formats . 21 Figure 6.1-1 Trunking Control Packet Header Block 22 Figure 6.1-2 Alternative Trunking Control Packet Header Block . 23 Tables Table 4.3-1 OSP Status Symbol Codes . 9 Table 4.3-2 ISP Status

33、 Symbol Codes . 9 TIA-102.AABB-B iv Patent Identification The readers attention is called to the possibility that compliance with this document 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

34、 those claims or any patent rights in connection therewith. The patent holders so far identified have, we believe, filed with APCO/NASTD/FED statements of willingness to grant licenses under those rights on reasonable and nondiscriminatory terms and conditions to applicants desiring to obtain such l

35、icenses. Details may be obtained from APCO/NASTD/FED. The following patent holders and patents have been identified in accordance with the TIA intellectual property rights policy: TIA shall not be responsible for identifying patents for which licenses may be required by this document or for conducti

36、ng inquiries into the legal validity or scope of those patents that are brought to its attention. Ericsson Inc. - Patent Nos. US 5,574,788 TIA-102.AABB-B 1 1 Introduction 1.1 Scope The intent of this document is to define the general control channel structures to be employed on the Project 25 trunki

37、ng control channel. The 9600 b/s control channel scheme is designed to be compatible per BAAA. 1.2 Revision history July, 2005 Revision A approved for TIA publication. April, 2011 Revision B approved for TIA publication. TIA-102.AABB-B 2 1.3 References The following documents contain provisions, whi

38、ch, through reference herein, constitute provisions of this standard. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this standard are encouraged to investigate the possibility of applying the most recent editi

39、ons of the standards indicated below. ANSI and TIA maintain registers of currently valid national standards maintained by them. 1.3.1 Normative References 1. BAAA “Project 25 FDMA Common Air Interface”, ANSI/TIA 102.BAAA-A, September 2003 - This document describes the basic over the air formats used

40、 on the Trunking control channel. 2. AABC “Project 25 Trunking Control Channel Messages”, ANSI/TIA-102.AABC-C, November 2009 - This is a separate companion document that describes the specific use of the general Trunking control channel structures. 3. AABD “Trunking Procedures”, TIA-102.AABD-A, Dece

41、mber 2008 4. BAAC “Project 25 - Common Air Interface - Reserved Values” , TIA-102.BAAC-A, December 2003 1.3.2 Informative References 5. Project 25 Guidelines to Assign Wide Area Communication Network and System Identities, April 2001 This document provides guidelines which explain how to assign the

42、WACN ID and System ID in a uniform manner (with and without an FCC Call Sign correlation) so that interoperability across diverse Project 25 systems is possible. 1.4 Number Nomenclature There are references to bit patterns in this document. In general the following applies: If a number is preceded b

43、y a “%“ the number is to be interpreted as a binary representation with the appropriate number of symbols (e.g. %1010 is 4 symbol binary for 10) If a number is preceded by a “$“ the number is to be interpreted as a hexadecimal representation with the appropriate number of symbols. (e.g., $0A is 2 sy

44、mbol hexadecimal for 10) TIA-102.AABB-B 3 If a number is presented with neither a “%“ or “$“ preceding it, the number is to be considered as a decimal representation with the appropriate number of symbols. (e.g., 15 is decimal 15) TIA-102.AABB-B 4 2 Overview The trunking control channel packet struc

45、ture is based upon the data packet structure of the Common Air Interface (CAI). This allows the control channel transactions to both be usable on system channel resources supporting only control channel packets or system channel resources which support both control channel packets and other system p

46、ackets (e.g. voice or data packets). The trunking control channel shall be considered to consist of two (2) separate communication paths, the inbound control channel path and the outbound control channel path. The inbound path is used for transmissions from the subscriber units to be received by the

47、 RFSS. The outbound path is used for transmissions from the RFSS to be received by the subscriber units. 2.1 Control Channel Packets A control channel packet sent from the RFSS to the subscriber unit shall be termed the Outbound Signaling Packet (OSP) using the outbound control channel. A control ch

48、annel packet sent from the subscriber unit to the RFSS shall be termed the Inbound Signaling Packet (ISP) using the inbound control channel. Control channel packets are identified as single block and multiple block formats. The majority of operations of the trunking control channel are accomplished

49、with the single block packet format to afford the greatest throughput potential. The multiple block format is reserved for the transactions which have need of greater information transfer than provided in the preferred single block format. The single block control channel format is not an unconfirmed data packet as defined by the CAI. The single block control channel format has a unique preamble to indicate it is a special trunking signaling block. With this special “trunking signaling block“ consideration, an associated Trunking Service Access Point (SAP) is imp