Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 32.306  Word version:  16.0.0

Top   Top   None   None   Next
0…   2…

 

0  IntroductionWord‑p. 5

The present document is part of a TS-family covering the 3rd Generation Partnership Project: Technical Specification Group Services and System Aspects; Telecommunication management; as identified below:
  • 32.301: Configuration Management (CM); Notification Integration Reference Point (IRP): Requirements
  • 32.302: Configuration Management (CM); Notification Integration Reference Point (IRP): Information Service (IS)
  • 32.306: Configuration Management (CM); Notification Integration Reference Point (IRP): Solution Set (SS) definitions
Configuration Management (CM), in general, provides the operator with the ability to assure correct and effective operation of the 3G network as it evolves. CM actions have the objective to control and monitor the actual configuration on the Network Elements (NEs) and Network Resources (NRs), and they may be initiated by the operator or by functions in the Operations Systems (OSs) or NEs.
CM actions may be requested as part of an implementation programme (e.g. additions and deletions), as part of an optimisation programme (e.g. modifications), and to maintain the overall Quality of Service (QoS). The CM actions are initiated either as a single action on a NE of the 3G network or as part of a complex procedure involving actions on many NEs.
The Itf-N interface is built up by a number of Integration Reference Points (IRPs) and a related Name Convention, which realise the functional capabilities over this interface. The basic structure of the IRPs is defined in TS 32.101.
Network Elements (NEs) under management and element managers generate notifications of events about occurrences within the network. Different kinds of events carry different kinds of information, e.g. alarms or CM notification.
Information of an event is carried in notification. An IRPAgent (typically an EM or a NE) emits notifications. IRPManager (typically a network management system) receives notifications. The purpose of Notification IRP is to define an interface through which an IRPManager can subscribe to IRPAgent for receiving notifications.
This IRP bases its design on work captured in ITU-T Recommendation X.734 [20], and OMG Notification Service [14]. The central design ideas are:
  • Separation of notification Consumers (IRPManagers) from Producers (IRPAgents);
  • Notifications are sent to IRPManagers without the need for IRPManagers to periodically check for new notifications.
Common characteristics related to notifications in all other IRPs are gathered in one IRP.
Up

1  ScopeWord‑p. 7

The present document contains the Solution Sets for the IRP whose semantics is specified in Notification IRP: Information Service (TS 32.302).
These Solution Set specifications are related to TS 32.302 V14.0.X.

Up   Top   ToC