TIA TSB102 BAFA-A-1999 Project 25 Network Management Interface Overview - New Technology Standards Project - Digital Radio Technical Standards《项目25 网络管理接口概览-新技术标准方案-数字无线技术标准》.pdf

《TIA TSB102 BAFA-A-1999 Project 25 Network Management Interface Overview - New Technology Standards Project - Digital Radio Technical Standards《项目25 网络管理接口概览-新技术标准方案-数字无线技术标准》.pdf》由会员分享，可在线阅读，更多相关《TIA TSB102 BAFA-A-1999 Project 25 Network Management Interface Overview - New Technology Standards Project - Digital Radio Technical Standards《项目25 网络管理接口概览-新技术标准方案-数字无线技术标准》.pdf（16页珍藏版）》请在麦多课文档分享上搜索。

1、 r - STD-EIA TSBL02-BAFA-A-ENGL Lqq9 ICI 3234600 Ob24580 180 .I TIAIEIA TELECOMMUNI CATIONS SYSTEMS BULLETIN Project 25 Network Management Interface Overview - New Technology ,* Standards Ptoject - Digital Radio Technical Standards TSBl02.BAFA-A (evision of TSBIOLBAFA) JULY 1999 TELECOMMUNICATIONS I

2、NDUSTRY A manager or agent. The description of the Manager/Agent concept given here is intended to reflect the definitions given in OS1 Recommendation X.701 6. - Manager role: the part of the distributed application that issues management operation directives and receives notifications. - Agent role

3、: the part of the application process that manages the associated managed objects. The role of the Agent will be to respond to directives issued by a Manager. It will also reflect to the Manager a view of these objects and emit notifications reflecting the behavior of these objects. A Manager is the

4、 part of the distributed application for which a particular exchange of information has taken the manager role. Similarly, an Agent is the part that has taken the agent role. 4.1 .I .I ManagedAgenVObjects Relationships The Manager/Agent roles are assigned to management processes within a given commu

5、nications context. Figure 4 shows the interaction between Manager, Agent and Objects. It must be noted that a many-to-many relationship will typically exist between Managers and Agents in the sense that: 5 Copyright Electronic Industries Alliance Provided by IHS under license with EIANot for ResaleN

6、o reproduction or networking permitted without license from IHS-,-,-STD*EIA TSBL02-BAFA-A-ENGL 1999 M 3234b00 Ob24589 308 BI T IAIE IAASB 1 02. BA FA-A - One Manager may be involved in an information exchange with several Agents. These agents may span multiple RF Subsystems. In this case there will

7、be several manager roles interacting with their associated agent roles. In this scenario, synchronization between the various OMCs may be required across the DC N . Note. The issue of synchronization of directives (management operations) from the manager to multiple agents may exist. - One Agent may

8、 be involved in an information exchange with several Managers. In this case there will be several agent roles interacting with their associated manager roles. In this scenario the issue of concurrent directives may exist. Note. Concurrent requests received by an agent from rnulflple managers require

9、s further study. M an aging Managed Open System Open System Performing management operations Agent Notifications emitted Managed U Objects Local system environment Management operations Notifications - Manager FIG. 4 Interaction Between Manager, Agent and Objects An Agent may deny a Managers directi

10、ve for several reasons (e.g. security, information model consistency, etc.). A Manager will, therefore, have to be prepared to handle negative responses from an Agent. The information, events and actions, which may be transferred or affected through the use of a network management protocol, are a se

11、t of managed object attributes, identified collectively as the Management Information Base (MI B) 4. All management exchanges between Managers and Agents are expressed in terms of a consistent set of management operations (invoked via a manager role) and notifications (filtered and forwarded by the

12、agent role). These operations are all realized through the protocols of the Simple Network Management Protocol (SNMP)3. The manner in which Agents interact with the RF Network Elements is a local matter and not a subject for standardization. 4.1.2 Interworking Between Project 25 Managers / Agents Th

13、e Project 25 Network Management System uses the Manager/Agent relationship described above to achieve management activities. The Manager and Agents are part of the management application functions and as such are part of the Project 25 Network Management System. Figure 5 depicts a typical configurat

14、ion showing an NMC which manages RF Sub-system OMC-RF manager(s) which manages RF Network Elements (cascading of managers). The NMC interacts with the OMC-RF by reference to the information model supported by the OMC-RF at its interface to 6 Copyright Electronic Industries Alliance Provided by IHS u

15、nder license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-the NMC. Similarly, the OMC-RF interacts through another information model to the RF Network Element. In the cascaded environment, the OMC-RF provides (presents) the information model B to the NMC

16、. To do this it uses information from information model C. The OMC-RF processes the operations from the NMC on objects in the MIB of the OMC-RF. This may involve further operations on information model C. The OMC-RF processes the notifications and performs actions on the RF Network Elements, and thi

17、s may involve further notifications to the NMC. The Project 25 Network Management standard will define the OMC-RF MIB which presents the RF Network Elements managed objects to the NMC as well as the operations and notifications on those objects between the NMC and OMC-RF. Within the RF Sub-system, t

18、he relationship between the OMC-RF Manager, the RF Network Element Agents, and the Agent MIBs are not subject to standardization and are an implementation issue. RF Network NMC information information NMC Network Management Center OMC-RF SNMP Simple Network Management Protocol MIB Management Informa

19、tion Base M Manager A Agent Operations - maintaining the communications context. - concentration of data: - collection of data; - data formatting; - data translation. - workstation access ; - thresholding; - data communications back up; - routinghe-routing of data; - security (e.g. access control, v

20、erification); - fault sectionalization tests; - circuit selection and access for tests; - circuit test analysis. Processes involving data storage: - data base storage; - network configuration; - equipment identification; - memory back up. Processes in volving data handling: Processes involving decis

21、ion making: 8 Copyright Electronic Industries Alliance Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-STDmEIA TSBL02mBAFA-A-ENGL 1999 e 3234600 062Li592 9T2 H TlNEIFVTSB102.BAFA-A 5. Transportation Medium for Network Manaqemen

22、t Information In order for two or more Network Management components to exchange management information they must be connected by a communications path and each component must support the same interface onto that communications path. The recommended means for standard communications between the OMC-

23、RF and the NMC are SNMP protocols. The SNMP protocol is based on the OS1 seven layer stack to define the communication protocols. The lower layers comprise the physical, data link, network, and transport layers. These are primarily focused on different media to provide a transport service. The SNMP

24、interface will utilize the IP protocol stack. The upper layers consist of the session, presentation, and application layers. These are primarily focused on various application services, one of which is network management. For all lnternet-based network elements, it is proposed that they incorporate

25、the Internet defined MIB-II standards (RFC 121 3)4 for managing network elements. This by no means defines the network element nor its attributes. 9 Copyright Electronic Industries Alliance Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license fr

26、om IHS-,-,-STD-EIA TSBLOZ*BAFA-A-ENGL 1999 E 3234600 Ob24593 839 E TINE IPJTS 51 02. BA FA-A 6. 6.1 Definition of Project 25 Svstem Manaqement Functional Areas OS1 Description of Network Management Functional Areas The OS1 functional approach to network management categorizes the problem of managing

27、 heterogeneous vendor network devices into five sub-problem areas: Configuration Management- Responsible for setting the state of network elements and their relationship with each other. Fault Management - Responsible for detecting, presenting, and isolating abnormal network behavior with respect to

28、 both the logical and physical network entities and maintaining a fault history log. Performance Management - Responsible for monitoring throughput and error rate of link transmissions, as well as CPU usage, disk hits, etc., and alerting the manager of actual or potential problems. Past performance

29、logs ailow trend analysis and other resource monitoring to be carried out. Accounting Managernent - Responsible for collecting data related to resource Security Management- Responsible for controlling access to network elements and 6.2 consumption in the network. L all of the associated management i

30、nformation. Project 25 Standardization of Management Functional Areas While all of the areas of functional network management may be implemented within an RF Sub-system OMC-RF, the initial focus of the Project 25 Network Management standard will be in the areas of fault management and performance ma

31、nagement operations and notifications between the NMC and the OMC-RF. The additional network management functional areas of Configuration Management, Accounting Management, and Security Management can be made available from the NMC via standard X-window displays of the OMC-RF Configuration, Accounti

32、ng, and Security Management user interface applications actually located on the OMC-RF platform. The network management services and RF Element management information available via the X-window display is not subject to standardization. 6.2.1 Fault Management 6.2.1.1 Alarm Surveillance 6.2.1 .I .1 A

33、larm Recognition and Notification The OMC-RF network management functionality within an RF-Subsystem will monitor the status of each of the RF Network Elements which it manages. When the OMC-RF recognizes a major fault condition, either by polling or receiving a 10 Copyright Electronic Industries Al

34、liance Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-STDoEIA TSBL02-BAFA-A-ENGL 1999 3234600 Ob24594 775 111 TIAJEIAITSB102. BA FA-A trap/event from an RF Sub-system agent, the fault will be forwarded to the NMC for processin

35、g . An example of a major fault to be forwarded to the NMC is a change in functional status of an RF Sub-system Controller. The definition of the RF-System elements presented to the NMC in the OMC-RF MIB, the registration of the NMC with the OMC-RF for specific element faults, and the fault severity

36、 filtering are subject for further study. 6.2.1.1.2 Functional Status Retrieval Operations The OMC-RF will provide the capability for the NMC to retrieve the functional status of the RF-System elements presented to the NMC in the OMC-RF MIB. As an example, this will provide the NMC with the capabili

37、ty of retrieving from the OMC-RF, either scheduled or on-demand, the current functional status of an RF Sub-system Controller. The definition of the RF-System elements presented to the NMC in the OMC-RF MIB and the specific attributes of those elements are subject for further study. 6.2.1.2 Diagnost

38、ic / Test Operations Diagnostic / Test Operations sent from the NMC to the OMC-RF must be processed and forwarded to the RF Sub-system Agents by the OMC-RF. When diagnostic / test requests are sent to the OMC-RF to change the functional status of RF-System elements presented to the NMC in the OMC-RF

39、 MIB, the OMC-RF must process the request, resulting in a request for functional status change be sent to the appropriate RF Sub-system agent. An example of a diagnostic /test operation would be a request sent to an OMC-RF for a self test of a Base Controller. This diagnostic request would be proces

40、sed by the OMC-RF and result in a request sent to the Base Site Controller Agent to begin a self test sequence to test for hardware malfunctions. The definition of the RF-System elements presented to the NMC in the OMC-RF MIB and the specific diagnostic /test operations available are subject for fur

41、ther study. 6.2.2 Performance Management 6.2.2.1 Performance Retrieval Operations The OMC-RF will maintain the RF Sub-system radio call performance data to confirm the RF Sub-system is correctly sized and to obtain historical data of system usage. This information must be made available to an NMC by

42、 an OMC-RF to determine the sub-system RF traffic produced by users and control signaling. 11 Copyright Electronic Industries Alliance Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-STDeEIA TSBLO2.BAFA-A-ENCL 3999 m 3234600 Ob

43、24595 bOL MI TINE IATSB 1 02. BAFA-A An example of performance retrieval is an NMC request to an OMC-RF for the count of the number of occurrences over a fixed time interval a radio was denied access to the RF system due to the lack of available RF Sub-system Base Audio resources. The definition of

44、the RF-System elements presented in to the NMC in the OMC-RF MIB and the specific performance data available are subject for further study. 12 Copyright Electronic Industries Alliance Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-