TIA-102 BAEE-A-2004 Project 25 Radio Management Protocols New Technology Standards Project Digital Radio Technical Standards《项目25-数字无线电广播－新技术标准工程－管理协议》.pdf

《TIA-102 BAEE-A-2004 Project 25 Radio Management Protocols New Technology Standards Project Digital Radio Technical Standards《项目25-数字无线电广播－新技术标准工程－管理协议》.pdf》由会员分享，可在线阅读，更多相关《TIA-102 BAEE-A-2004 Project 25 Radio Management Protocols New Technology Standards Project Digital Radio Technical Standards《项目25-数字无线电广播－新技术标准工程－管理协议》.pdf（58页珍藏版）》请在麦多课文档分享上搜索。

1、 TIA STANDARD Project 25 Radio Management Protocols New Technology Standards Project Digital Radio Technical Standards TIA-102.BAEE-A (Revision of TIA/EIA-102.BAEE) September 2004 TELECOMMUNICATIONS INDUSTRY ASSOCIATION Representing the telecommunications industry in association with the Electronic

2、Industries Alliance ANSI/TIA-102.BAEE-A-2004Approved: June 16, 2004Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-NOTICE TIA Engineering Standards and Publications are designed

3、 to serve the 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

4、 of such Standards 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 membe

5、rs, either domestically 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 ad

6、opting the Standard 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 applica

7、bility of regulatory limitations before its use. (From Standards Proposal No. 3-4631-RV1, formulated under the cognizance of the TIA TR-8.5 Subcommittee on Signaling and Data Transmission.) Published by TELECOMMUNICATIONS INDUSTRY ASSOCIATION 2004 Standards and Technology Department 2500 Wilson Boul

8、evard Arlington, VA 22201 U.S.A. PRICE: Please refer to current Catalog of TIA TELECOMMUNICATIONS INDUSTRY ASSOCIATION STANDARDS AND ENGINEERING PUBLICATIONS or call Global Engineering Documents, USA and Canada (1-800-854-7179) International (303-397-7956) or search online at http:/www.tiaonline.org

9、/standards/search_n_order.cfm All rights reserved Printed in U.S.A. Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-NOTICE OF COPYRIGHT This document is copyrighted by the TIA.

10、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 TIA Standards Department or go to the TIA website (www.tiaonline.org) for detail

11、s on how to request permission. Details are located at: http:/www.tiaonline.org/about/faqDetail.cfm?id=18 OR Telecommunications Industry Association Standards (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)

12、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 copyrights, owned by one or more parties. TIA ma

13、kes 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 with reference to, and disclaims any o

14、bligation 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 licensing terms or conditions are reason

15、able 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. TIA does not enforce or monitor compliance with the contents of the Document. TIA does not certify, inspect

16、, 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 LIMITATION, ANY AND ALL WARRANTIES CONCERNING THE ACCURACY OF THE CONTENTS, ITS FITNESS OR APPROPRIATENES

17、S FOR A PARTICULAR PURPOSE OR USE, ITS MERCHANTABILITY AND ITS NON-INFRINGEMENT 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 AN

18、Y 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 SHALL NOT BE LIABLE FOR ANY AND ALL DAMAGES, DIRECT OR INDIRECT, ARISING FROM OR RELATING TO ANY US

19、E 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 THE LIKE), WHETHER BASED UPON BREACH OF CONTRACT, BREACH OF WARRANTY, TORT (INCLUDING NEGLIGENC

20、E), 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 WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS.Copyright Telecommunications Industry Associ

21、ation Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Foreword (This foreword is not part of this standard.) This document has been published by the Telecommunications Industry Association (TIA) in accordance with the terms and

22、 conditions provided for in a Memorandum of Understanding (MoU) executed by and between the TIA, the Associated Public -Safety Communications Officials (APCO), the National Association of State Telecommunications Directors (NASTD), and the various agencies of the Federal government (FED). Members of

23、 the APCO Project 25 Interface Committee (APIC) Data Task Group (DTG) originally authored this document under the leadership of Dr. Rich Comroe, Chairman APIC DTG. Members of APIC and the APCO Project 25 Steering Committee (APSC) authorized the further development of this document under the leadersh

24、ip of Mr. Craig M. Jorgensen, Chairman APSC. Members of the TIA TR8.5 Land Mobile Services Data it is not the intention of this document to define all possible radio management protocols and associated messages for Project 25 compliant equipment. Conversely, some radio management protocols or associ

25、ated messages may be removed from this document in subsequent releases as their descriptions are incorporated into other documents. Annex B: Network Management Mapping (Informative) is informative and is not considered part of this standard. The TIA makes no claims as to the applicability of the inf

26、ormation contained in this document for any purpose although it is believed that the information will prove to be invaluable to designers of Project 25 compliant equipment. Some aspects of the specifications contained in this document may not have been fully operationally tested; however, a great de

27、al of time and good faith effort has been invested in the preparation of this document to ensure the accuracy of the information it contains. iCopyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license

28、 from IHS-,-,-This page intentionally left blank. iiCopyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Project 25 Radio Management Protocols TIA-102.BAEE-A Table of Contents TABLE

29、OF CONTENTS I LIST OF FIGURES . III LIST OF TABLES .IV 1 INTRODUCTION1 1.1 SCOPE 1 1.1.1 Radio Control Protocol (RCP) .1 1.1.2 Simple Network Management Protocol (SNMP).1 1.2 DOCUMENT REVISION HISTORY 2 1.3 NORMATIVE REFERENCES 2 1.4 INFORMATIVE REFERENCES. 3 1.5 TERMS. 4 2 OVERVIEW 5 2.1 CONVENTION

30、S. 5 2.1.1 Symbols.5 2.2 NETWORK MANAGEMENT OVERVIEW. 5 2.3 CONTROL PLANE PROTOCOL STACK 6 3 RADIO CONTROL PROTOCOL (RCP) .7 3.1 PROTOCOL CHARACTERISTICS 7 3.1.1 Multithreaded Interface .7 3.1.2 Transaction-based Model 8 3.2 SERVICE DATA UNITS (SDUS) 8 3.2.1 General Syntax8 3.3 REQUEST CLASS SDUS (T

31、YPE RQST) . 10 3.3.1 Request-Class Syntax10 3.3.2 Request-Class Operator Commands12 3.3.2.1 Get Information 12 3.3.2.2 Get Configuration 13 3.3.2.3 Restore Default Configuration. 13 3.3.2.4 Set Configuration. 14 3.3.2.5 Save Configuration 14 3.3.2.6 Reset Operations Statistics. 15 3.3.2.7 Get Operat

32、ions Statistics 15 3.4 RESPONSE SDUS (TYPE RESP) 16 3.4.1 Response-Class Syntax.16 3.4.2 Response-Class SDUs 16 3.4.2.1 Get Information Response 17 3.4.2.2 Get Configuration Response 19 3.4.2.3 Reset Operations Statistics Response. 20 3.4.2.4 Get Operations Statistics Response 20 3.4.2.5 Restore Def

33、ault Configuration Response 21 3.4.2.6 Set Configuration Response. 21 3.4.2.7 Save Configuration Response 22 3.4.2.8 Unknown Command . 22 3.5 REPORT SDUS (TYPE RPRT) 23 3.5.1 Report-Class SDU Syntax23 3.5.2 Report-Class SDUs .24 3.5.2.1 Radio Power-Up . 24 3.5.2.2 Radio Registration . 24 3.5.2.3 Dat

34、a Service Availability . 25 iiiCopyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA-102.BAEE-A Project 25 Radio Management Protocols 4 SIMPLE NETWORK MANAGEMENT PROTOCOL (SNMP) 2

35、6 4.1 OVERVIEW 26 4.1.1 SNMP Protocol Operations.26 4.1.2 SNMP Managed Data27 4.1.3 SNMP and RCP Equivalency28 4.2 PROJECT 25 SNMP NODE DEFINITION 29 4.2.1 Object Identifier (OID).29 4.2.2 Protocol Stack29 4.2.3 SNMP Project 25 Subtree29 4.2.4 SMIv2 Conformance.30 4.3 PROJECT 25 SNMP RMP MIB DEFINIT

36、ION. 30 4.3.1 Project 25 RMP MIB Hierarchy.30 4.3.2 SNMP TR8dot5RmpInfoObjs RMP Node32 4.3.3 SNMP TR8dot5RmpConfigObjs RMP Node.32 4.3.4 SNMP TR8dot5RmpStatsObjs RMP Node33 4.3.5 SNMP TR8dot5RmpEvents Node.33 ANNEX A: ASN.1 MIB DEFINITION (NORMATIVE) 34 ANNEX B: NETWORK MANAGEMENT MAPPING (INFORMATI

37、VE) .40 B.1 NETWORK MANAGEMENT FUNCTIONAL AREA MAPPING FOR RCP . 40 B.2 NETWORK MANAGEMENT FUNCTIONAL AREA MAPPING FOR SNMP 43 ivCopyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-

38、Project 25 Radio Management Protocols TIA-102.BAEE-A List of Figures FIGURE 2-1: THE “A” INTERFACE RMP CONTROL PLANE FOR PACKET SWITCHED SERVICE. 6 FIGURE 3-1: PROJECT 25 RCP CONTROL PLANE 7 FIGURE 3-2: GENERIC RCP SDU STRUCTURE 8 FIGURE 3-3: GENERAL REQUEST -CLASS SDU SYNTAX 10 FIGURE 3-4: GET RADI

39、O INFORMATION BLOCK REQUEST SYNTAX. 12 FIGURE 3-5: GET RADIO CONFIGURATION BLOCK REQUEST SYNTAX 13 FIGURE 3-6: RESTORE DEFAULT CONFIGURATION REQUEST SYNTAX 13 FIGURE 3-7: SET CONFIGURATION REQUEST SYNTAX. 14 FIGURE 3-8: SAVE CONFIGURATION REQUEST SYNTAX 14 FIGURE 3-9: RESET OPERATIONS STATISTICS REQ

40、UEST SYNTAX. 15 FIGURE 3-10: GET OPERATIONS STATISTICS REQUEST SYNTAX 15 FIGURE 3-11: GENERAL RESPONSE-CLASS SDU SYNTAX 16 FIGURE 3-12: GET INFORMATION RESPONSE FORMAT FOR AN INFORMATION BLOCK REQUEST 17 FIGURE 3-13: GET CONFIGURATION RESPONSE FORMAT FOR A CONFIGURATION BLOCK REQUEST . 19 FIGURE 3-1

41、4: RESET OPERATIONS STATISTICS RESPONSE FORMAT 20 FIGURE 3-15: GET OPERATIONS STATISTICS RESPONSE FORMAT 20 FIGURE 3-16: RESTORE DEFAULT CONFIGURATION RESPONSE FORMAT 21 FIGURE 3-17: SET CONFIGURATION RESPONSE FORMAT. 21 FIGURE 3-18: SAVE CONFIGURATION RESPONSE FORMAT 22 FIGURE 3-19: UNKNOWN COMMAND

42、 FORMAT 22 FIGURE 3-20: GENERAL REPORT -CLASS SDU SYNTAX. 23 FIGURE 3-21: RADIO POWER-UP REPORT SYNTAX. 24 FIGURE 3-22: RADIO REGISTRATION REPORT SYNTAX 24 FIGURE 3-23: DATA SERVICE AVAILABILITY REPORT SYNTAX 25 FIGURE 4-1: BASIC SNMP NETWORK MANAGEMENT TOPOLOGY. 26 FIGURE 4-2: SNMP PROTOCOL STACK.

43、26 FIGURE 4-3: PORTION OF THE OID HIERARCHY (IETF REGISTERED). 27 FIGURE 4-4: PROJECT 25 SNMP CONTROL PLANE. 29 FIGURE 4-5: INITIAL SNMP PROJECT 25 SUBTREE. 30 FIGURE 4-6: PROJECT 25 MIB HIERARCHY. 31 vCopyright Telecommunications Industry Association Provided by IHS under license with EIANot for Re

44、saleNo reproduction or networking permitted without license from IHS-,-,-TIA-102.BAEE-A Project 25 Radio Management Protocols List of Tables TABLE 1-1: REVISION HISTORY. 2 TABLE 3-1: REQUEST CLASS SDU TYPE 10 TABLE 3-2: REQUEST -CLASS OPERATORS. 11 TABLE 3-3: REQUEST CLASS SDU OPERAND VALUES 11 TABL

45、E 3-4: RESPONSE CLASS SDU TYPE 16 TABLE 3-5: RESPONSE CLASS RESULT CODES 16 TABLE 3-6: MRC INFORMATION BLOCK PARAMETERS. 18 TABLE 3-7: MRC CONFIGURATION BLOCK PARAMETERS 19 TABLE 3-8: MRC OPERATIONS STATISTICS BLOCK PARAMETERS 21 TABLE 3-9: UNKNOWN COMMAND RESPONSE INFORMATION VALUE. 22 TABLE 3-10:

46、REPORT CLASS SDU TYPE 23 TABLE 3-11: REPORT -CLASS REPORT IDS . 23 TABLE 3-12: REGISTRATION REPORT INFORMATION VALUES 24 TABLE 3-13: DATA SERVICE AVAILABILITY REPORT INFORMATION VALUES. 25 TABLE 4-1: RCP/SNMP PROTOCOL EQUIVALENCY 28 TABLE 4-2: SNMP TR8DOT5RMPINFOOBJS RMP NODE MANAGED OBJECTS. 32 TAB

47、LE 4-3: SNMP TR8DOT5RMPCONFIGOBJS RMP NODE MANAGED OBJECTS 32 TABLE 4-4: SNMP TR8DOT5RMPSTATSOBJS RMP NODE MANAGED OBJECTS 33 TABLE 4-5: SNMP TR8DOT5RMPEVENTS NODE NOTIFICATIONS. 33 TABLE 4-6: SNMP EVENT NODE NOTIFICATION MANAGED OBJECTS 33 TABLE B - 1: RESPONSE CLASS RESULT CODES 40 TABLE B - 2: MR

48、C INFORMATION BLOCK PARAMETERS 41 TABLE B - 3: MRC CONFIGURATION BLOCK PARAMETERS. 41 TABLE B - 4: MRC OPERATIONS STATISTICS BLOCK PARAMETERS. 42 TABLE B - 5: UNKNOWN COMMAND RESPONSE INFORMATION VALUE 42 TABLE B - 6: REPORT -CLASS REPORT IDS 42 TABLE B - 7: REGISTRATION REPORT INFORMATION VALUES. 42 TABLE B - 8: DATA SERVICE AVAILABILITY REPORT INFORMATION VALUES 42 TABLE B - 9: SNMP TR8DOT5RMPINFOOBJS RMP NODE MANAGED OBJECTS 43 TABLE B - 10: SNMP TR8DOT5RMPCONFIGOBJS RMP NODE MANAGED OBJECTS 44 TABLE B - 11: SNMP TR8DOT5RMPSTATSOBJS RMP NODE MANAGED OBJECTS. 44 TABLE B - 12: SNM