1、 TSB-102.BAFA-A-1999 APPROVED: JULY 1, 1999 REAFFIRMED: JANUARY 29, 2013 TSB-102.BAFA-A (Revision of TSB-102.BAFA) July 1999Project 25 Network Management Interface Overview- New Technology Standards Project- Digital Radio Technical Standards NOTICE TIA Engineering Standards and Publications are desi
2、gned 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 exist
3、ence 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 m
4、embers, 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 partie
5、s adopting 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 app
6、licability of regulatory limitations before its use. (From Project No. PN-3-4508, formulated under the cognizance of the TR-8 Mobile and Personal Private and Radio Standards. TR-8.19 Subcommittee on Wireline System Interfaces). Published by TELECOMMUNICATIONS INDUSTRY ASSOCIATION Standards and Techn
7、ology Department 1320 N. Courthouse Road Arlington, VA 22201 U.S.A. PRICE: Please refer to current 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.tia
8、online.org/standards/catalog/ All rights reserved Printed in U.S.A. NOTICE OF COPYRIGHT This document 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 rep
9、roduce portions of this document, please contact the TIA Standards Department or go to the TIA website (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 Technol
10、ogy (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 Document may
11、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 attention,
12、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 terms or
13、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 with as r
14、espects 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 or otherw
15、ise), whether such reference consists of mandatory, alternate or optional elements (as defined in 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
16、 Reference; (ii) TIAs policy of encouragement of voluntary disclosure (see Engineering Manual Section 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 id
17、entification 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, designs or services or any claims of compliance with th
18、e 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 MERCHANTABILITY AND ITS NONINFRINGEMENT OF ANY THIRD PARTY
19、S 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 SAFETY OR HEALTH EFFECTS OF THE CONTENTS OR ANY P
20、RODUCT 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 WITHOUT LIMITATION ANY AND ALL INDIRECT, SPECIAL, IN
21、CIDENTAL 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 ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE FOREGO
22、ING 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/TSB102.BAFA-AiTable of Contents1. Introduction .12. Scope22.1 Revision History32.2 References .33. Glossary of Terms.34. Network Mana
23、gement Hierarchy.44.1 OMC-RF Agent Functionality 54.1.1 Manager/Agent Concepts54.1.1.1 Manager/Agent/Objects Relationships .54.1.2 Interworking Between Project 25 Managers / Agents64.2 OMC-RF Mediation Functionality75. Transportation Medium for Network Management Information.96. Definition of Projec
24、t 25 System Management Functional Areas .106.1 OSI Description of Network Management Functional Areas.106.2 Project 25 Standardization of Management Functional Areas106.2.1 Fault Management.106.2.1.1 Alarm Surveillance 106.2.1.1.1 Alarm Recognition and Notification106.2.1.1.2 Functional Status Retri
25、eval Operations116.2.1.2 Diagnostic / Test Operations.116.2.2 Performance Management 116.2.2.1 Performance Retrieval Operations 11TIA/EIA/TSB102.BAFA-AiiTable of FiguresFIG. 1 Repeater Example Reference Configuration1FIG. 2 Reference Model 1FIG. 3 RF-Subsystem Network Management Architecture4FIG. 4
26、Interaction Between Manager, Agent and Objects .6FIG. 5 OMC-RF / NMC Manager / Agent Relationship7TIA/EIA/TSB102.BAFA-A11. IntroductionThe objective of this standard is to define the interface En between one or more RFSub-systems and one or more attached network management End Systems or otherinterc
27、onnect network management systems, as depicted in the Project 25 GeneralSystem Model Repeater Reference Configuration shown in Figure 1 below.RFSSPSTNNET MGTESDATAESRFSSFSMR MRC MES MDTMESCONESUmEtEnEdGEfEcBASUFIG. 1 Repeater Example Reference ConfigurationAccording to the Project 25 General System
28、Model, the Network ManagementInterface is the En interface between an Operations and Maintenance Center - RadioFrequency (OMC-RF) within one RF Sub-system, and a network management end-system. The RF Sub-system Gateway functional group provides network routingfunctionality for the network management
29、 information passing into / out of the RFSub-system.RFGESEnESOMC-RFFIG. 2 Reference ModelRadio infrastructure designs are beginning to realize the benefits of standardnetworks and networking protocols for the use of communicating voice, data andcontrol. Radio product vendors are capable of connectin
30、g their products to new orTIA/EIA/TSB102.BAFA-A2existing LANs and then communicating with similar or other heterogeneous networkdevices. The problem that arises with this “open“ system approach is that each ofthese new radio infrastructure devices has different ways of managing itscomponents. Theref
31、ore, it is desirable and beneficial, from a customer andengineering stand-point, to incorporate a standard means for providing networkmanagement information from within a Radio Frequency Sub-system to a higherlevel End System network manager capable of managing multiple Radio FrequencySub-systems.2.
32、 ScopeProject 25 systems have subscriber units and fixed equipment which comprises theinfrastructure. There are a number of external interfaces to the system, andspecifically this document addresses the Network Management Interface En.The objective of the Network Management Interface is to ensure a
33、standardizedinterface between the End System Network Management Center (NMC) and anOperations and Maintenance Center - Radio Frequency (OMC-RF) located within aRadio Frequency Sub-system, so that an NMC can manage Radio Frequency Sub-systems (RFSS) sourced from other vendors. The network management
34、interfacesbetween the fixed RFSS equipment and the OMC-RF could be standardized, but arebeyond the scope of the Project 25 standard.The Network Management Interface is part of an intended suite of standardsnecessary for interoperability. A general overview of the Project 25 standard existsin the Pro
35、ject 25 System and Standards Definition 1. The reader should havefamiliarity with this document.The following three sections will identify the proposed standards for: 1) the NetworkManagement hierarchy, 2) the transportation medium of Network managementinformation between an NMC and an OMC-RF, and 3
36、) the definition of the Project 25system management functional areas.TIA/EIA/TSB102.BAFA-A32.1 Revision HistoryVersion 0.1, June 28, 1995, Initial version based on, and is an enhancement to, theexisting APCO Network Management Interface documentTSB102.BAFA. This document is being proposed with the i
37、ntention tosupersede the existing Network Management Interface document.Version 1.0, June 30, 1995, Updated per internal Motorola review.Version 1.1, July 31, 1995, Updated per Project 25 System Task Group reviewcomments.Version 1.2, October 1, 1997, updated word processor file, typo corrections, de
38、letedsection 7.Version 1.3, December 15, 1997, removed CMIP and updated figure 1.Version 1.4, May 2, 1999, editorial and typographical changes and document titlechange.2.2 ReferencesThe following documents contain provisions which, through reference in this text,constitute provisions of this documen
39、t. At the time of publication, the editionsindicated were valid. All standards are subject to revision, and parties to agreementsbased on this document are encouraged to investigate the possibility of applying themost recent editions of the standards indicated below. ANSI and TIA maintainregisters o
40、f currently valid national standards published by them.1 Project 25 System and Standards Definition, TIA, TSB-102-A.2 The Simple Book, Marshall T. Rose - Prentice Hall.3 Internet RFC 1157 - Simple Network Management Protocol (SNMP).4 Internet RFC 1213 - Management Information Base for network manage
41、mentof TCP/IP-based internets.5 ITU Principles for Telecommunications Management Network,Recommendation M.3010.6 ITU Recommendation X.701, OSI System Management Overview.3. Glossary of TermsFor the purposes of this document, the following definitions apply.ASN.1 Abstract Syntax Notation 1DCN Data Co
42、mmunications NetworkMIB Management Information BaseNMC Network Management CenterOMC-RF Operations and Maintenance Center - Radio FrequencyRFG RF Sub-system GatewayRFSS RF Sub-systemSNMP Simple Network Management ProtocolWS Work StationTIA/EIA/TSB102.BAFA-A44. Network Management HierarchyWithin an RF
43、 Sub-system there will exist an Operations and Maintenance CenterOMC-RF which will provide RF Sub-system infrastructure element management andmediation services. This section of the document will outline the requiredfunctionality of the OMC-RF from the perspective of the NMC via the En interface.The
44、 interfaces between the RF Network Elements (defined as BR - Base Radio, BA -Base Audio, BC - Base Control, RFC - RF Sub-system Control, RFS - RF Sub-system Switch, CON - Console, and RFG - RF Sub-system Gateway, Et - TelephoneEnd System Interface, Ed - Data Host End System Interface) and the OMC-RF
45、 aswell as the Network Management services provided to the local RF Sub-systemnetwork management user by the OMC-RF could be standardized, but are beyondthe scope of the Project 25 Network Management standard.EnEnd SystemNMCRFSub-SystemRFSub-SystemDCNWSEnRFSub-SystemRFGOMC-RFRF Network ElementsEnEnD
46、CN Data Communications NetworkWS Work StationRFG RF Sub-system GatewayNMC Network Management CenterOMC-RF Operations and Maintenance Center - Radio FrequencyFIG. 3 RF-Subsystem Network Management ArchitectureSome of the system elements in Figure 1 which need to be managed but require theuse of a sta
47、ndard interface for communications with the OMC-RF or NMC, such asMR - Mobile radio, MRC - Mobile Routing Control, or MDP - Mobile Data Peripheralvia the Um - Air Interface, will require the definition of network managementmessages within those interface standards. The network management messagesTIA
48、/EIA/TSB102.BAFA-A5will be defined using the specific interface standard and are beyond the scope of theProject 25 Network Management Interface standard. Figure 3 identifies the RF Sub-system Network Management Architecture.4.1 OMC-RF Agent FunctionalitySince the OMC-RF provides the NMC with network
49、 management access to the RFSub-system and acts as both an agent to the NMC and a manager to the local RFSub-system RF Network Elements, an overview of the Manager/Agent concepts willbe provided at this point.4.1.1 Manager/Agent ConceptsThe Manager/Agent concepts presented here are slightly modified from the TMNM.3010 standard 5.Management of a radio system environment is an information processing application.Because the environment being managed is distributed, network management is adistributed application. This involves the exchange of management info
