hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
d0c51713395fe5e2368cfb67eaacc91a
|
132 111-4
|
5.1 Managed Object Classes
|
..................................................................................................................................13
|
d0c51713395fe5e2368cfb67eaacc91a
|
132 111-4
|
5.1.1 alarmControl
|
...............................................................................................................................................13
|
d0c51713395fe5e2368cfb67eaacc91a
|
132 111-4
|
5.2 Packages
|
...........................................................................................................................................................14
|
d0c51713395fe5e2368cfb67eaacc91a
|
132 111-4
|
5.2.1 alarmControlBasicPackage
|
.........................................................................................................................14
|
d0c51713395fe5e2368cfb67eaacc91a
|
132 111-4
|
5.2.2 alarmAcknowledgementPackage
|
................................................................................................................14
|
d0c51713395fe5e2368cfb67eaacc91a
|
132 111-4
|
5.2.3 alarmIRPVersionPackage
|
...........................................................................................................................15
|
d0c51713395fe5e2368cfb67eaacc91a
|
132 111-4
|
5.3 Actions
|
.............................................................................................................................................................15 5.3.1 acknowledgeAlarms(M) .............................................................................................................................15 5.3.2 getAlarmCount(O)......................................................................................................................................16 5.3.3 getAlarmList(M).........................................................................................................................................17 5.3.4 getAlarmIRPVersion(M) ............................................................................................................................18 5.3.5 unacknowledgeAlarms(O)..........................................................................................................................19
|
d0c51713395fe5e2368cfb67eaacc91a
|
132 111-4
|
5.4 Notifications
|
.....................................................................................................................................................20 5.4.1 alarmListRebuilt(M)...................................................................................................................................20
|
d0c51713395fe5e2368cfb67eaacc91a
|
132 111-4
|
5.5 Attributes
|
..........................................................................................................................................................20
|
d0c51713395fe5e2368cfb67eaacc91a
|
132 111-4
|
5.5.1 alarmControlId
|
............................................................................................................................................20
|
d0c51713395fe5e2368cfb67eaacc91a
|
132 111-4
|
5.5.2 alarmsCountSummary
|
................................................................................................................................20
|
d0c51713395fe5e2368cfb67eaacc91a
|
132 111-4
|
5.5.3 supportedAlarmIRPVersions
|
......................................................................................................................21
|
d0c51713395fe5e2368cfb67eaacc91a
|
132 111-4
|
5.6 Parameters
|
........................................................................................................................................................21
|
d0c51713395fe5e2368cfb67eaacc91a
|
132 111-4
|
5.6.1 ackStateParameter
|
.......................................................................................................................................21
|
d0c51713395fe5e2368cfb67eaacc91a
|
132 111-4
|
5.6.2 ackSystemIdParameter
|
................................................................................................................................21
|
d0c51713395fe5e2368cfb67eaacc91a
|
132 111-4
|
5.6.3 ackTimeParameter
|
......................................................................................................................................22
|
d0c51713395fe5e2368cfb67eaacc91a
|
132 111-4
|
5.6.4 ackUserIdParameter
|
....................................................................................................................................22
|
d0c51713395fe5e2368cfb67eaacc91a
|
132 111-4
|
6 ASN.1 definitions for Alarm IRP
|
...........................................................................................................23 Annex A (informative): Change history .......................................................................................................26 History..............................................................................................................................................................27 ETSI ETSI TS 132 111-4 V3.2.0 (2001-12) 4 3G TS 32.111-4 version 3.2.0 Release 1999 Foreword This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). The present document is part 4 of a multi-part TS covering the 3rd Generation Partnership Project: Technical Specification Group Services and System Aspects, as identifies below: Part 1: “3G Fault Management Requirements”; Part 2: “Alarm Integration Reference Point: Information Service”; Part 3: “Alarm Integration Reference Point: CORBA Solution Set Version 1:1”; Part 4: “Alarm Integration Reference Point: CMIP Solution Set”. The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TS 132 111-4 V3.2.0 (2001-12) 5 3G TS 32.111-4 version 3.2.0 Release 1999 1 Scope The present document (3GPP TS 32.111 Part-4) defines the alarm integration reference point for the CMIP solution set. In detail: - Clause 4 contains an introduction to some basic concepts of the CMIP interfaces. - Clause 5 contains the GDMO definitions for the Alarm Management over the CMIP interfaces - Clause 6 contains the ASN.1 definitions supporting the GDMO definitions provided in clause 5. 2 References The following documents contain provisions, which through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • For a non-specific reference, the latest version applies. [1] 3GPP TS 32.101: "3G Telecom Management principles and high level requirements". [2] 3GPP TS 32.102: "3G Telecom Management architecture". [3] 3GPP TS 32.106-2: "Notification Integration Reference Point: Information Service". [4] ITU-T Recommendation X.710: "Common management information service definition for CCITT applications". [5] ITU-T Recommendation X.711: "Common management information protocol specification for CCITT applications". [6] ITU-T Recommendation X.721: "Information technology - Open Systems Interconnection - Structure of management information: Definition of management information". [7] ITU-T Recommendation X.731: "Information technology - Open Systems Interconnection - Systems Management: State management function". [8] ITU-T Recommendation X.733: "Information technology - Open Systems Interconnection - Systems Management: Alarm reporting function". [9] ITU-T Recommendation X.734: "Information technology - Open Systems Interconnection - Systems Management: Event report management function". [10] ITU-T Recommendation Q.821: “Specification of System Signalling No. 7 Q3 Interface- Stage 2 and Stage 3 description for the Q3 interface - Alarm Surveillance” [11] 3GPP TS 32.111-1: “3G Fault Management”. [12] 3GPP TS 32.111-2: “Alarm Integration Reference Point: Information Service”. [13] 3GPP TS 32.111-3: “Alarm Integration Reference Point: CORBA Solution Set Version 1:1”. [14] 3GPP TS 32.106-4: "Notification Integration Reference Point: CMIP Solution Set". ETSI ETSI TS 132 111-4 V3.2.0 (2001-12) 6 3G TS 32.111-4 version 3.2.0 Release 1999 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions defined in 3GPP TS 32.111-1 [11] apply. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: ASN.1 Abstract Syntax Notation number 1 CCITT The International Telegraph and Telephone Consultative Committee CM Configuration Management CMIP Common Management Information Protocol CMIS Common Management Information Service CMISE Common Management Information Service Element EFD Event Forwarding Discriminator EM Element Manager FTAM File Transfer Access and Management GDMO Guidelines for the Defifition of Managed Objects IRP Integration Reference Point Itf-N Interface N (between NM and EM/NE) ITU-T International Telecommunication Union – Telecommunications M Mandatory MOC Managed Object Class MOI Managed Object Instance NE Network Element NM Network Manager NMC Network Management Centre O Optional OS Operations System TMN Telecommunications Management Network 4 Basic aspects The present document provides all the GDMO and ASN.1 definitions necessary to implement the Alarm IRP Information Service for the CMIP interface. The Alarm IRP Information Service is based on Operations and Notifications. In the present document, for the CMIP interfaces the Operations are modeled as GDMO “Actions” of a MOC defined specifically for alarm management while the Notifications are modeled as GDMO “Notifications” included in MOCs that need to report events to the Manager. In more detail, the Notifications related to alarm management are included in a MOC defined in the present document while the Notifications defined for alarm reporting are not included in any MOC defined in the present document. They will be included in other MOCs defined in other CMIP Solution Set or in other CMIP Information Models. Regarding the Notifications, the present document is based on the Notification IRP CMIP Solution Set (3GPP TS 32.106-4 [14]). 4.3 Reporting cleared alarms On the CMIP interfaces the clearing of alarms is reported by the Agent to the Managers in accordance with the mechanisms defined in ITU-T Recommendation X.733 [8] and ITU-T Recommendation Q.821 [10]. ETSI ETSI TS 132 111-4 V3.2.0 (2001-12) 7 3G TS 32.111-4 version 3.2.0 Release 1999 4.4 Acknowledgment of alarms This clause relates to the co-operative alarm acknowledgment managed on Itf-N, which implies that the acknowledgment of alarms can be done on both NM and EM. The acknowledgment of alarms is managed by means of the MOC alarmControl, which includes: – One Action to acknowledge alarms; – One Action to unacknowledge alarms; – ITU-T Recommendation X.721 [6] compliant Alarm Notification to inform Managers about changes of acknowledgment state. In case an alarm is acknowledged by an operator or automatically by a management system, the ackUserId, ackSystemId, ackState and ackTime information is stored in the additionalInformation field of the alarm present in the alarm list. 4.5 Alignment of alarm conditions over the Itf-N The IRP Manager is able to trigger the alarm conditions alignment using the Action getAlarmList The following specifies the logical steps of the alignment procedure, by describing a possible implementation. Any other implementation showing the same behaviour on the Itf-N interface is compliant with the present document. – The Manager sends to the Agent a getAlarmList request containing the following information: - alarmAckState, used to select the alarms from the Agent's alarm list for the current alignment (e.g. all active alarms). - destination, identifying the destination to which event reports that have passed the filter conditions are sent. - filter, this optional parameter defines the conditions an alarm notification shall fulfil in order to be forwarded to the Manager. It applies only for the current alignment request. – After evaluation of the request, the Agent first generates an alignmentId value, which unambiguously identifies this alignment process. This value is used by the Manager to correlate alarm reports to the corresponding alignment requests, in case this Manager issues several alarm alignments in parallel. – The Agent creates a temporary Event Forwarding Discriminator (EFD) instance for the purpose of this alarm alignment, using the parameters destination and filter received in the request. If the filter parameter is absent or NULL, all alarm notifications are forwarded to the Manager through this EFD, according to the value of the parameter alarmAckState. The filter is set by the Agent automatically in order to forward to only those alarm notifications containing, at the beginning of the field additionalText, either the string "(ALIGNMENT-<alignmentId>)“ or the string „(ALIGNMENTEND-<alignmentId>)“. – The Agent sends back a getAlarmList response, which contains the alignmentId described above and the status information, indicating the result of the request. (see the message flow in Figure 1). – The Agent scans now its alarm list. For every alarm, which matches the criteria defined by the alarmAckState parameter, the Agent inserts, at the beginning of the field additionalText, the string „(ALIGNMENT- <alignmentId>)“. According to ITU-T Recommendation X.734 [9], the Agent forwards these alarm notifications towards all EFDs. In the last alarm of the list the Agent inserts the string „(ALIGNMENTEND-<alignmentId>)“ to indicate the end of the alarm alignment. NOTE: These alarm notifications can reach the current Manager only via the temporary EFD created for the current alignment. They are filtered out: a) By all the EFD instances used for „real-time“ alarm reporting, due to the presence of the sub-string „ALIGNMENT“ in the field additionalText (see 3GPP TS 32.106-4 [14]). ETSI ETSI TS 132 111-4 V3.2.0 (2001-12) 8 3G TS 32.111-4 version 3.2.0 Release 1999 b) By all temporary EFD instances possibly created for parallel alignments, due to the presence of the unambiguous sub-string „<alignmentId>“ in the additionalText field. – After sending the last alarm report (identified by the sub-string „ALIGNMENTEND“ in the additionalText), the Agent automatically deletes the temporary EFD instance (see Figure 1). Figure 1: Alignment arrow diagram M-ACTION request: getAlarmList (alarmAckState, destination, filter) Manager Agent M-EVENT-REPORT: alarm report 1 (..., additionalText = " (ALIGNMENT-alignmentId) ......", ...) M-ACTION response: getAlarmList (alignmentId, status) This is a real-time alarm, forwarded by the Agent during alarm alignment The Agent creates a temporary EFD M-EVENT-REPORT: alarm report 2 (..., additionalText = " (ALIGNMENT-alignmentId) ......", ...) M-EVENT-REPORT: alarm report (... , additionalText = " .....", ...) . . . M-EVENT-REPORT: alarm report n (..., additionalText = " (ALIGNMENTEND-alignmentId) ......", ...) Last alarm (from the Agent's alarm list) which matches the required criteria The Agent deletes automatically the temporary EFD ETSI ETSI TS 132 111-4 V3.2.0 (2001-12) 9 3G TS 32.111-4 version 3.2.0 Release 1999 Figure 2 shows the handling of a „real-time“ alarm notification (occured during the execution of the getAlarmList operation), which is forwarded by the Agent (according to ITU-T Recommendation X.734 [9]) to all currently available EFD instances. Dependent on the discriminatorConstruct setting of every EFD, such an alarm may or may not reach the related Manager. In any case, this alarm is filtered out by the temporary EFD assigned to the Manager, which triggered the getAlarmList request. Figure 2: Treatment of “real time” alarms Agent . . . . Current Manager "Real-time" EFD "Real-time" EFD Manager Temporary EFD Alarm filtered out "Real-time" alarm notification . . . . Itf-N ETSI ETSI TS 132 111-4 V3.2.0 (2001-12) 10 3G TS 32.111-4 version 3.2.0 Release 1999 Figure 3 shows the handling of an alarm notification from the alarm list, matching the criteria defined in the parameters alarmAckState of the getAlarmList request and forwarded by the Agent to all EFD instances as well. This alarm is filtered out by all EFD instances in charge of discrimination of „real-time“ alarms and can reach only the Manager, which triggered the getAlarmList request, because it passes the temporary EFD instance assigned to this Manager. Figure 3: Treatment of “alignent” alarms 4.6 Mapping The semantics of the Alarm IRP is defined in 3GPP TS 32.111-2 [12]. The definitions of the management information defined there are independent of any implementation technology and protocol. This section maps these protocol-independent definitions onto the equivalences of the CMIP solution set of Alarm IRP. 4.6.1 Mapping of Operations Table 1 maps the operations defined in the IS of the Alarm IRP to its equivalents in the CMIP SS. The equivalents are qualified as Mandatory (M) or Optional (O). Table 1: Mapping of Operations Operations of Information Services of the Alarm IRP CMIP SS Equivalents solution set for the Alarm IRP Qualifier acknowledgeAlarms acknowledgeAlarms M getAlarmCount getAlarmCount O getAlarmList getAlarmList M getAlarmIRPVersion getAlarmIRPVersion M unacknowledgeAlarms unacknowledgeAlarms O 4.6.2 Mapping of Parameters of each operation The tables in the following subclauses show the parameters of each operations defined in the IS described 3GPP TS 32.111-2 [12] and their equivalents in this CMIP SS. Agent . . . . Current Manager "Real-time" EFD "Real-time" EFD Manager Temporary EFD Alarm filtered out Alarm notification from Alarm List . . . . Itf-N Alarm filtered out ETSI ETSI TS 132 111-4 V3.2.0 (2001-12) 11 3G TS 32.111-4 version 3.2.0 Release 1999 The parameters of the IS operations are mapped, in the CMIP SS equivalents. Table 2: Mapping of parameters of ‘acknowledgementAlarms’ Operation parameters of Information Services CMIP equivalences Qualifier alarmInformationReferenceList alarmReferenceList M ackUserId ackUserId M ackSystemId ackSystemId O badAlarmInformationReferenceList errorAlarmReferenceList M status status M Table 3: Mapping of Parameters of ‘getAlarmCount’ Operation parameters of Information Services CMIP equivalents Qualifier filter filter O alarmAckState alarmAckState O criticalCount criticalCount M majorCount majorCount M minorCount minorCount M warningCount warningCount M indeterminateCount indeterminateCount M clearedCount clearedCount M status status M Table 4: Mapping of Parameters of ‘getAlarmList’ Operation parameters of Information Services CMIP equivalents Qualifier filter filter O alarmAckState alarmAckState O -- destination (input) - see NOTE 1 M alarmInformationList (sequence of alarm notifications) (see Clause 4.5) M status status M -- alignmentId (output) - see NOTE 2 M NOTE 1: destination is a CMIP specific parameter and is determined by the Manager. NOTE 2: alignmentId is a CMIP specific parameter and is determined by the Agent Table 5: Mapping of Parameters of ‘getAlarmIRPVersion’ Operation parameters of Information Services CMIP equivalents Qualifier versionNumberList versionNumberList M status status M Table 6: Mapping of Parameters of ‘unacknowledgeAlarms’ Operation parameters of Information Services CMIP equivalents Qualifier alarmInformationReferenceList alarmReferenceList M ackUserId ackUserId M ackSystemId ackSystemId O badAlarmInformationReferenceList errorAlarmReferenceList M status status M ETSI ETSI TS 132 111-4 V3.2.0 (2001-12) 12 3G TS 32.111-4 version 3.2.0 Release 1999 4.6.3 Mapping of Notifications Table 7 maps the Notifications defined in the Information Service of the Alarm IRP to the equivalent Notifications of the CMIP solution set for the Alarm IRP. The CMIP Notifications are qualified as Mandatory (M) or Optional (O). Table 7: Mapping of Notifications Notifications of Information Services of the Alarm IRP Equivalent Notifications of the CMIP solution set for the Alarm IRP Qualifier notifyNewAlarm environmentalAlarm ITU-T X.721 [6] equipmentAlarm ITU-T X.721 [6] qualityofServiceAlarm ITU-T X.721 [6] processingErrorAlarm ITU-T X.721 [6] communicationAlarm ITU-T X.721 [6] M notifyChangedAlarm environmentalAlarm ITU-T X.721 [6] equipmentAlarm ITU-T X.721 [6] qualityofServiceAlarm ITU-T X.721 [6] processingErrorAlarm ITU-T X.721 [6] communicationAlarm ITU-T X.721 [6] O notifyClearedAlarm environmentalAlarm ITU-T X.721 [6] equipmentAlarm ITU-T X.721 [6] qualityofServiceAlarm ITU-T X.721 [6] processingErrorAlarm ITU-T X.721 [6] communicationAlarm ITU-T X.721 [6] M notifyAckStateChanged environmentalAlarm ITU-T X.721 [6] equipmentAlarm ITU-T X.721 [6] qualityofServiceAlarm ITU-T X.721 [6] processingErrorAlarm ITU-T X.721 [6] communicationAlarm ITU-T X.721 [6] M notifyAlarmListRebuilt alarmListRebuilt M 4.6.4 Mapping of Parameters of each notification Table 8 and table 9 show the parameters of each notification defined in the Information Service described in 3GPP TS 32.111-2 [12] and their equivalence in this CMIP SS. The input parameters of the Information Service notifications are mapped, in the CMIP SS, onto the “event information”. ETSI ETSI TS 132 111-4 V3.2.0 (2001-12) 13 3G TS 32.111-4 version 3.2.0 Release 1999 Table 8: Mapping of Parameters of ‘notifyNewAlarm’, ‘notifyClearedAlarm’ and ‘notifyAckStateChanged’ Notification parameters of Information Services CMIP equivalences Qualifier -- notificationIdentifier (Note 1) M probableCause probableCause M specificProblems specificProblems O perceivedSeverity perceivedSeverity M backedUpStatus backedUpStatus O backUpObject backUpObject O trendIndication trendIndication O thresholdInfo thresholdInfo O correlatedNotifications correlatedNotifications O stateChangeDefinition stateChangeDefinition O monitoredAttributes monitoredAttributes O proposedRepairActions proposedRepairActions O additionalText additionalText O additionalInformation additionalInformation (Note 2) NOTE 1: notificationIdentifier is a parameter of the Notification Header defined in 3GPP TS 32.106-2 [3]. NOTE 2: See qualification information in 3GPP TS 32.111-2 [12], Table 13: Parameter-Attributes of alarmInformationBody. Table 9: Mapping of Parameters of ‘alarmListRebuilt’ Notification parameters of Information Services CMIP equivalents Qualifier notificationIdentifier (see Note) reason reason M NOTE: notificationIdentifier is a parameter of the Notification Header defined in 3GPP TS 32.106-2 [3]. 5 GDMO definitions 5.1 Managed Object Classes 5.1.1 alarmControl This Managed Object Class (MOC) models the alarm information available within the Agent and significant for the NM-EM interface. It deals with both active and cleared but not yet acknowledged alarms. The NMC may initiate the transfer of current alarms according to the required parameters in the M-ACTION request ‘getAlarmList’. alarmControl MANAGED OBJECT CLASS DERIVED FROM ”Rec. X.721 | ISO/IEC 10165-2 : 1992”:top; CHARACTERIZED BY alarmControlBasicPackage, alarmAcknowledgementPackage, alarmIRPVersionPackage; REGISTERED AS { ts32-111AlarmObjectClass 1}; ETSI ETSI TS 132 111-4 V3.2.0 (2001-12) 14 3G TS 32.111-4 version 3.2.0 Release 1999 5.2 Packages 5.2.1 alarmControlBasicPackage alarmControlBasicPackage PACKAGE BEHAVIOUR alarmControlBasicPackageBehaviour; ATTRIBUTES alarmControlId GET, alarmsCountSummary GET; ACTIONS getAlarmCount, getAlarmList; NOTIFICATIONS alarmListRebuilt; REGISTERED AS { ts32-111AlarmPackage 1}; alarmControlBasicPackageBehaviour BEHAVIOUR DEFINED AS “The MOC alarmControl has been defined to provide information to the Manager about the currently alarms controlled by the Agent. An instance of the 'alarmControl' MOC is identified by the value of the attribute 'alarmControlId'. The attribute ‘alarmsCountSummary’ provides a summary of the number of alarms managed in the Agent’s alarm list (including the number of cleared but not yet acknowledged alarms). The action 'getAlarmCount' is the means, for the Manager, to ask the number of currently available alarms in the Agent according to the specification in the action request. The action 'getAlarmList' is the means, for the Manager, to trigger an alarm alignment procedure in accordance with the parameter specified in the action request (this may be needed e.g. for first time alignment or after a link interruption between the Agent and the Manager). The alarm list is sent as a sequence of single alarm reports. The notification ‘alarmListRebuilt’ is sent by the Agent to the Manager to inform that the alarm list has changed. It is recommended that the Manager subsequently triggers an alarm alignment.”; 5.2.2 alarmAcknowledgementPackage alarmAcknowledgementPackage PACKAGE BEHAVIOUR alarmAcknowledgementPackageBehaviour; ACTIONS acknowledgeAlarms, unacknowledgeAlarms; NOTIFICATIONS "Rec. X.721 | ISO/IEC 10165-2 : 1992":communicationsAlarm, "Rec. X.721 | ISO/IEC 10165-2 : 1992":environmentalAlarm, "Rec. X.721 | ISO/IEC 10165-2 : 1992":equipmentAlarm, "Rec. X.721 | ISO/IEC 10165-2 : 1992":processingErrorAlarm, "Rec. X.721 | ISO/IEC 10165-2 : 1992":qualityofServiceAlarm; REGISTERED AS { ts32-111AlarmPackage 2}; alarmAcknowledgementPackageBehaviour BEHAVIOUR DEFINED AS “This package has been defined to provide information to the Manager about the acknowledgement status of the alarms controlled by the Agent. The action 'acknowledgeAlarms' allows the NM operator to acknowledge one or several alarms previously sent by the Agent as alarm notifications. ETSI ETSI TS 132 111-4 V3.2.0 (2001-12) 15 3G TS 32.111-4 version 3.2.0 Release 1999 The action 'unacknowledgeAlarms' allows the NM operator to unacknowledge one or several alarms previously acknowledged by himself. The ITU-T Recommendation X.721 [6] compliant alarm notifications are sent by the Agent to the Manager to inform that one alarm has been acknowledged or unacknowledged. The acknowledgement related information is carried in the additionalInformation attribute.”; 5.2.3 alarmIRPVersionPackage alarmIRPVersionPackage PACKAGE BEHAVIOUR alarmIRPVersionPackageBehaviour; ATTRIBUTES supportedAlarmIRPVersions GET; ACTIONS getAlarmIRPVersion; REGISTERED AS { ts32-111AlarmPackage 3}; alarmIRPVersionPackageBehaviour BEHAVIOUR DEFINED AS “This package has been defined to allow the Manager to get information about the Alarm IRP versions supported by the Agent. The attribute ‘supportedAlarmIRPVersions’ indicates all versions of the Alarm IRP currently supported by the Agent. The action ‘getAlarmIRPVersion’ may be invoked by the Manager to get information about the Alarm IRP versions supported by the Agent.”; 5.3 Actions
|
d0c51713395fe5e2368cfb67eaacc91a
|
132 111-4
|
5.3.1 acknowledgeAlarms (M)
|
acknowledgeAlarms ACTION BEHAVIOUR acknowledgeAlarmsBehaviour; MODE CONFIRMED; WITH INFORMATION SYNTAX TS32-111-AlarmAsn1TypeModule.AckOrUnackAlarms; WITH REPLY SYNTAX TS32-111-AlarmAsn1TypeModule.AckOrUnackAlarmsReply; REGISTERED AS { ts32-111AlarmAction 1}; acknowledgeAlarmsBehaviour BEHAVIOUR DEFINED AS ”This action is invoked by the Manager to indicate to the Agent that one or several alarms (previously sent by the Agent as alarm notifications) have to be acknowledged. In the action request the NM supplies the parameter ackUserId and ackSystemId. The other acknowledgement history parameters, i.e. alarm acknowledgement state (in this case acknowledged) and the acknowledgement time are set by the Agent itself. The 'Action information' field contains the following data: • alarmReferenceList This parameter contains a set of MOI (Managed Object Instance) and notificationIdentifier. Each pair identifies unambiguously in the scope of the Agent an alarm (previously received by the NM) that have to ETSI ETSI TS 132 111-4 V3.2.0 (2001-12) 16 3G TS 32.111-4 version 3.2.0 Release 1999 be now acknowledged. MOI can be absent if scope of uniqueness of notificationIdentifier is across the IRPAgent. • ackUserId It contains the name of the operator who acknowledged the alarm or a generic name (dependent on the operational concept). It may have also the value NULL. • ackSystemId It indicates the management system where the acknowledgment is triggered. It may have also the value NULL. The 'Action response' contains the following data: • status This parameter contains the results of the NM acknowledgement action. Possible values: noError (0, all alarms found and ack state changed according to the manager request), ackPartlySuccessful (some alarms not found / not changeable, see next parameter), error (value indicates the reason why the complete operation failed). • errorAlarmReferenceList This parameter (significant only if status = ackPartlySuccessful) contains the list of moi (managed object instance) and notificationIdentifier pairs of the alarms which could not be acknowledged and, for each alarm, also the reason of the error.“;
|
d0c51713395fe5e2368cfb67eaacc91a
|
132 111-4
|
5.3.2 getAlarmCount (O)
|
getAlarmCount ACTION BEHAVIOUR getAlarmCountBehaviour; MODE CONFIRMED; WITH INFORMATION SYNTAX TS32-111-AlarmAsn1TypeModule.GetAlarmCount; WITH REPLY SYNTAX TS32-111-AlarmAsn1TypeModule.GetAlarmCountReply; REGISTERED AS { ts32-111AlarmAction 2}; getAlarmCountBehaviour BEHAVIOUR DEFINED AS ”The NM invokes this action to receive the number of available alarms in the Agent' alarm list according to the specification in the action request. The Manager may use this action to find out the number of alarms in the alarm list before invoking a synchronisation by means of the getAlarmList operation. The request is possible also before the Manager creates an own event forwarding discriminator instance within the Agent. The ‘Action information’ field contains the following data: • alarmAckState Depending on this optional parameter value, the NM gets the number of alarms of each perceivedSeverity value according to the following possible choices: - all alarms - all active alarms (acknowledged or not yet acknowledged) - all active and acknowledged alarms - all active and unacknowledged alarms ETSI ETSI TS 132 111-4 V3.2.0 (2001-12) 17 3G TS 32.111-4 version 3.2.0 Release 1999 - all cleared and unacknowledged alarms. If the parameter is absent, all alarms from the Agent's alarm list are taken into consideration. • filter The handling of this optional parameter is as follows: - if present and not NULL, it indicates a filter constraint which shall apply in the calculation of the results - if its value is NULL, no filter shall be considered and the Agent shall return the number of all alarms according to the value of the parameter alarmAckState (see above) - if absent, the handling depends on the availability of an event forwarding discriminator instance within the Agent. If this instance is valid, the filter construct of the event forwarding discriminator shall apply. If no EFD instance is available, the Agent shall return the number of all alarms according to the value of the above-mentioned parameter alarmAckState. The ‘Action response’ is composed of: • The numbers of alarms for each perceivedSeverity value (if applicable). • The parameter status containing the results of the NM action. Possible values: noError (0), error (the value indicates the reason of the error).”;
|
d0c51713395fe5e2368cfb67eaacc91a
|
132 111-4
|
5.3.3 getAlarmList (M)
|
getAlarmList ACTION BEHAVIOUR getAlarmListBehaviour; MODE CONFIRMED; WITH INFORMATION SYNTAX TS32-111-AlarmAsn1TypeModule.GetAlarmList; WITH REPLY SYNTAX TS32-111-AlarmAsn1TypeModule.GetAlarmListReply; REGISTERED AS { ts32-111AlarmAction 3}; getAlarmListBehaviour BEHAVIOUR DEFINED AS ”This action starts an alarm alignment procedure between a NM and Agent, which takes into account the acknowledgment state of the alarms and a dedicated filter (valid only for the current request). The ‘Action information’ field contains the following data: • alarmAckState Depending on this optional parameter value, the NM gets the alarm reports according to the following possible choices: - all alarms - all active alarms (acknowledged or not yet acknowledged) - all active and acknowledged alarms - all active and unacknowledged alarms - all cleared and unacknowledged alarms. If the parameter is absent, all alarms from the Agent's alarm list are taken into consideration. • destination ETSI ETSI TS 132 111-4 V3.2.0 (2001-12) 18 3G TS 32.111-4 version 3.2.0 Release 1999 This parameter identifies the destination to which the alarm reports that have passed the test conditions specified in the parameter 'filter' are sent. According to ITU-T Recommendation X.721 [6], if no destination is specified in the request, then the discriminator is created with the destination defaulted to the AE-Title of the invoker. • filter The handling of this optional parameter (valid only for the current alignment request) is as follows: - if present and not NULL, it indicates a filter constraint which shall apply in the forwarding of the alignment-related alarm reports - if its value is NULL, no real filter shall be considered and the Manager receives the alarms according to the value of the parameter alarmAckState (see above). The ‘Action response’ contains the following data: • alignmentId The parameter is defined by the Agent and identifies unambiguously the current alarm alignment procedure. It allows the Manager to distinguish between alarm reports sent as consequence of several own alignment requests triggered in parallel. • status The parameter contains the results of the NM action. Possible values: noError (0), error (the value indicates the reason of the error). After the action response is forwarded to the NM, the Agent sends the alarm list as a sequence of single alarm notifications in accordance with the values of the request parameters. Every alarm notification contains all fields of the alarm stored in the alarm list. In particular: • The field additionalText contains at the beginning a string to allow a Manager to recognise that this alarm report is sent due to a previous getAlarmList request. The structure of this string is: - '(ALIGNMENT-alignmentId)' for every alarm report except the last one or - '(ALIGNMENTEND-alignmentId)' for the last alarm report sent by the Agent due to the current getAlarmList request. • If available, the data related to the acknowledgment history (i.e. ackState, ackTime, ackUserId, ackSystemId) are provided in the field additionalInformation. Further details about the implementation of this operation are provided in the 'Introduction'.”;
|
d0c51713395fe5e2368cfb67eaacc91a
|
132 111-4
|
5.3.4 getAlarmIRPVersion (M)
|
getAlarmIRPVersion ACTION BEHAVIOUR getAlarmIRPVersionBehaviour; MODE CONFIRMED; WITH REPLY SYNTAX TS32-111-AlarmAsn1TypeModule.GetAlarmIRPVersionReply; REGISTERED AS { ts32-111AlarmAction 4}; getAlarmIRPVersionBehaviour BEHAVIOUR DEFINED AS ”The NM invokes this action to get information about the Alarm IRP versions supported by the Agent. The 'Action information' field contains no data. ETSI ETSI TS 132 111-4 V3.2.0 (2001-12) 19 3G TS 32.111-4 version 3.2.0 Release 1999 The ‘Action response’ is composed of the following data: • versionNumbersList It defines a list of Alarm IRP versions supported by the Agent. A list containing no element, i.e. a NULL list means that the concerned Agent doesn’t support any version of the Notification IRP. • status It contains the results of the NM action. Possible values: noError (0), error (the value indicates the reason of the error).”;
|
d0c51713395fe5e2368cfb67eaacc91a
|
132 111-4
|
5.3.5 unacknowledgeAlarms (O)
|
unacknowledgeAlarms ACTION BEHAVIOUR unacknowledgeAlarmsBehaviour; MODE CONFIRMED; WITH INFORMATION SYNTAX TS32-111-AlarmAsn1TypeModule.AckOrUnackAlarms; WITH REPLY SYNTAX TS32-111-AlarmAsn1TypeModule.AckOrUnackAlarmsReply; REGISTERED AS { ts32-111AlarmAction 5}; unacknowledgeAlarmsBehaviour BEHAVIOUR DEFINED AS ”This action is used by the Manager to indicate to the Agent that one or several alarms (previously acknowledged) have to be unacknowledged. Subsequently the 'acknowledgement history' information of these alarms in the Agent’s alarm list is completely removed (this operation may be used by operators in case of a previous acknowledgement by mistake). The 'Action information' field contains the following data: • alarmReferenceList This parameter contains a set of MOI (Managed Object Instance) and notificationIdentifier pair. Each of them identifies unambiguously in the scope of the Agent an alarm (previously acknowledged by the NM) that have to be now unacknowledged. MOI can be absent if scope of uniqueness of notificationIdentifier is across the IRPAgent. • ackUserId It contains the name of the operator who unacknowledged the alarm or a generic name (dependent on the operational concept). It may have also the value NULL. Note that only the user who previously acknowledged the alarm is allowed to unacknowledge it later. • ackSystemId It indicates the management system where the acknowledgment is triggered. It may have also the value NULL. Note that the unacknowledgement is allowed only at the management system where previously the acknowledgement took place. The 'Action response' contains the following data: • status This parameter contains the results of the NM unknowledgement action. Possible values: noError (0, all alarms found and ack state changed according to the manager request), unackPartlySuccessful (some alarms not found / not changeable, see next response parameter), error (value indicates the reason why the complete operation failed). • errorAlarmReferenceList ETSI ETSI TS 132 111-4 V3.2.0 (2001-12) 20 3G TS 32.111-4 version 3.2.0 Release 1999 This parameter (significant only if status = unackPartlySuccessful) contains the list of MOI (Managed Object Instance) and notificationIdentifier pairs of the alarms which could not be unacknowledged and, for each alarm, also the reason of the error. MOI can be absent if scope of uniqueness of notificationIdentifier is across the IRPAgent. “; 5.4 Notifications
|
d0c51713395fe5e2368cfb67eaacc91a
|
132 111-4
|
5.4.1 alarmListRebuilt (M)
|
alarmListRebuilt NOTIFICATION BEHAVIOUR alarmListRebuiltBehaviour; WITH INFORMATION SYNTAX TS32-111-AlarmAsn1TypeModule.AlarmListRebuiltInfo; REGISTERED AS { ts32-111AlarmNotification 1}; alarmListRebuiltBehaviour BEHAVIOUR DEFINED AS ”This notification is used by the Agent to inform the NM that the alarm list has been rebuilt. The 'Event Information' field contains the following data: • notificationIdentifier This ITU-T X.721 standardised parameter, together with MOI (Managed Object Instance), unambiguously identifies this notification. • reason The parameter indicates the reason for alarm list rebuilding (if applicable).”; 5.5 Attributes 5.5.1 alarmControlId alarmControlId ATTRIBUTE WITH ATTRIBUTE SYNTAX TS32-111-AlarmAsn1TypeModule.GeneralObjectId; MATCHES FOR EQUALITY; BEHAVIOUR alarmControlIdBehaviour; REGISTERED AS { ts32-111AlarmAttribute 1}; alarmControlIdBehaviour BEHAVIOUR DEFINED AS ”This attribute names an instance of a ‘alarmControl’ object class.”; 5.5.2 alarmsCountSummary alarmsCountSummary ATTRIBUTE WITH ATTRIBUTE SYNTAX TS32-111-AlarmAsn1TypeModule.AlarmsCountSummary; MATCHES FOR EQUALITY; BEHAVIOUR alarmsCountSummaryBehaviour; REGISTERED AS { ts32-111AlarmAttribute 2}; ETSI ETSI TS 132 111-4 V3.2.0 (2001-12) 21 3G TS 32.111-4 version 3.2.0 Release 1999 alarmsCountSummaryBehaviour BEHAVIOUR DEFINED AS ”This attribute indicates a summary of number of alarms managed in the Agent’s alarm list sorted according to the perceived severity (including the number of cleared but not yet acknowledged alarms). Additionally the number of all currently active alarms is provided.”; 5.5.3 supportedAlarmIRPVersions supportedAlarmIRPVersions ATTRIBUTE WITH ATTRIBUTE SYNTAX TS32-111-AlarmAsn1TypeModule. SupportedAlarmIRPVersions; MATCHES FOR EQUALITY; BEHAVIOUR supportedAlarmIRPVersionsBehaviour; REGISTERED AS { ts32-111AlarmAttribute 3}; supportedAlarmIRPVersionsBehaviour BEHAVIOUR DEFINED AS ”This attribute provides the information concerning the Alarm IRP versions currently supported by the Agent.”; 5.6 Parameters 5.6.1 ackStateParameter ackStateParameter PARAMETER CONTEXT TS32-111-AlarmAsn1TypeModule.AlarmInfo.additionalInformation; WITH SYNTAX TS32-111-AlarmAsn1TypeModule.AckState; BEHAVIOUR ackStateParameterBehaviour; REGISTERED AS { ts32-111AlarmParameter 1}; ackStateParameterBehaviour BEHAVIOUR DEFINED AS ”This parameter models the optional additionalInformation field of the alarm notification. If present, it informs the NM about the current acknowledgement state of the present alarm.”; 5.6.2 ackSystemIdParameter ackSystemIdParameter PARAMETER CONTEXT TS32-111-AlarmAsn1TypeModule.AlarmInfo.additionalInformation; WITH SYNTAX TS32-111-AlarmAsn1TypeModule.AckSystemId; BEHAVIOUR ackSystemIdParameterBehaviour; REGISTERED AS { ts32-111AlarmParameter 2}; ackSystemIdParameterBehaviour BEHAVIOUR DEFINED AS ”This parameter models the optional additionalInformation field of the alarm notification. If present, it informs the NM about the identifier of the management system where the present alarm has been acknowledged.”; ETSI ETSI TS 132 111-4 V3.2.0 (2001-12) 22 3G TS 32.111-4 version 3.2.0 Release 1999 5.6.3 ackTimeParameter ackTimeParameter PARAMETER CONTEXT TS32-111-AlarmAsn1TypeModule.AlarmInfo.additionalInformation; WITH SYNTAX TS32-111-AlarmAsn1TypeModule.AckTime; BEHAVIOUR ackTimeParameterBehaviour; REGISTERED AS { ts32-111AlarmParameter 3}; ackTimeParameterBehaviour BEHAVIOUR DEFINED AS ”This parameter models the optional additionalInformation field of the alarm notification. If present, it informs the NM about the time the present alarm has been acknowledged by the Agent.”; 5.6.4 ackUserIdParameter ackUserIdParameter PARAMETER CONTEXT TS32-111-AlarmAsn1TypeModule.AlarmInfo.additionalInformation; WITH SYNTAX TS32-111-AlarmAsn1TypeModule.AckUserId; BEHAVIOUR ackUserIdParameterBehaviour; REGISTERED AS { ts32-111AlarmParameter 4}; ackUserIdParameterBehaviour BEHAVIOUR DEFINED AS ”This parameter models the optional additionalInformation field of the alarm notification. If present, it informs the NM about the identifier of the user who acknowledged the present alarm.”; ETSI ETSI TS 132 111-4 V3.2.0 (2001-12) 23 3G TS 32.111-4 version 3.2.0 Release 1999 6 ASN.1 definitions for Alarm IRP TS32-111-AlarmAsn1TypeModule --{ObjectIdentifierValueitu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-Operation-Maintenance(3) ts-32-111(111) part4(4) informationModel(0) asn1Module(2) version1(1)} DEFINITIONS IMPLICIT TAGS ::= BEGIN --EXPORTS everything IMPORTS NotificationIdentifier, Destination FROM Attribute-ASN1Module {joint-iso-ccitt ms(9) smi(3) part2(2) asn1Module(2) 1} AlarmInfo FROM Notification-ASN1Module {joint-iso-ccitt ms(9) smi(3) part2(2) asn1Module(2) 2} CMISFilter, ObjectInstance FROM CMIP-1 {joint-iso-ccitt ms(9) cmip(1) modules(0) protocol(3)}; baseNode3gpp OBJECT IDENTIFIER ::= {itu-t(0) identified-organization(4) etsi(0) mobileDomain(0) umts-Operation-Maintenance(3)} ts32-111Alarm OBJECT IDENTIFIER ::= { baseNode3gpp ts-32-111(111) part4(4) informationModel(0)} ts32-111AlarmObjectClass OBJECT IDENTIFIER ::= {ts32-111Alarm managedObjectClass(3)} ts32-111AlarmPackage OBJECT IDENTIFIER ::= {ts32-111Alarm package(4)} ts32-111AlarmParameter OBJECT IDENTIFIER ::= {ts32-111Alarm parameter(5)} ts32-111AlarmAttribute OBJECT IDENTIFIER ::= {ts32-111Alarm attribute(7)} ts32-111AlarmAction OBJECT IDENTIFIER ::= {ts32-111Alarm action(9)} ts32-111AlarmNotification OBJECT IDENTIFIER ::= {ts32-111Alarm notification(10)} -- Start of 3GPP SA5 own definitions AckErrorList ::= SET OF ErrorInfo AlarmReference ::= SEQUENCE { moi ObjectInstance OPTIONAL, -- absent if scope of uniquness of notificationId is across IRPAgent notificationIdentifier NotificationIdentifier } AckOrUnackAlarms ::= SEQUENCE { alarmReferenceList SET OF AlarmReference, -- ITU-T X.721 ackUserId AckUserId, ackSystemId AckSystemId OPTIONAL } AckOrUnackAlarmsReply ::= SEQUENCE { status ErrorCauses, errorAlarmReferenceList AckErrorList } AckState ::= ENUMERATED { acknowledged (0), unacknowledged (1) } AckSystemId ::= GraphicString AckTime ::= GeneralizedTime AckUserId ::= GraphicString AlarmChoice ::= ENUMERATED { allAlarms (0), ETSI ETSI TS 132 111-4 V3.2.0 (2001-12) 24 3G TS 32.111-4 version 3.2.0 Release 1999 allActiveAlarms (1), allActiveAndAckAlarms (2), allActiveAndUnackAlarms (3), allClearedAndUnackAlarms (4) } AlarmsCountSummary ::= SEQUENCE { activeAlarmsCount INTEGER, -- this is the sum of criticalCount, majorCount, minorCount, warningCount -- and indeterminateCount criticalCount INTEGER, majorCount INTEGER, minorCount INTEGER, warningCount INTEGER, indeterminateCount INTEGER, clearedCount INTEGER } AlarmListRebuiltInfo ::= SEQUENCE { notificationIdentifier NotificationIdentifier, -- ITU-T X.721 reason ErrorCauses } ErrorCauses ::= ENUMERATED { noError (0), -- operation / notification successfully performed wrongFilter (1), -- the value of the filter parameter is not valid wrongAlarmAckState (2), -- the value of the alarmAckState parameter (e.g. getAlarmCount) is not valid ackPartlySuccessful (3), -- acknowledgment request partly successful unackPartlySuccessful (4), -- unacknowledgment request partly successful wrongAlarmReference (5), -- alarm identifier used in the alarm reference list not found (e.g. in case of acknowledgement request) wrongAlarmReferenceList (6), -- the alarm reference list (e.g. in case of acknowledgement request) is empty or completely wrong alarmAlreadyAck (7), -- alarm to be acknowledged is already in this state alarmAlreadyUnack (8), -- alarm to be acknowledged is already in this state wrongUserId (9), -- the user identifier in the unacknowledgement operation is not the same as in the previous acknowledgementAlarms request wrongSystemId (10), -- the system identifier in the unacknowledgement operation is not the same as in the previous acknowledgementAlarms request alarmAckNotAllowed (11), -- current management system not allowed to acknowledge the alarm (e.g. due to acknowledgement competence rules) unspecifiedErrorReason (255) -- operation failed, specific error unknown } ErrorInfo ::= SEQUENCE { moi ObjectInstance OPTIONAL, -- absent if uniqueness of notificationIdentifier is across IRPAgent notificationIdentifier NotificationIdentifier, -- ITU-T X.721 reason ErrorCauses } GeneralObjectId ::= INTEGER GetAlarmCount ::= SEQUENCE { alarmAckState AlarmChoice OPTIONAL, filter CMISFilter OPTIONAL -- ITU-T X.711 } GetAlarmCountReply ::= SEQUENCE { criticalCount INTEGER, majorCount INTEGER, minorCount INTEGER, warningCount INTEGER, indeterminateCount INTEGER, clearedCount INTEGER, ETSI ETSI TS 132 111-4 V3.2.0 (2001-12) 25 3G TS 32.111-4 version 3.2.0 Release 1999 status ErrorCauses } GetAlarmIRPVersionReply ::= SEQUENCE { versionNumberList SupportedAlarmIRPVersions, status ErrorCauses } GetAlarmList ::= SEQUENCE { alarmAckState AlarmChoice OPTIONAL, destination Destination, -- ITU-T X.721 filter CMISFilter OPTIONAL -- ITU-T X.711 } GetAlarmListReply ::= SEQUENCE { alignmentId INTEGER, status ErrorCauses } IRPVersionNumber ::= GraphicString SupportedAlarmIRPVersions ::= SET OF IRPVersionNumber END -- of module TS32-111-AlarmAsn1TypeModule ETSI ETSI TS 132 111-4 V3.2.0 (2001-12) 26 3G TS 32.111-4 version 3.2.0 Release 1999 Annex A (informative): Change history Change history Date TSG # TSG Doc. CR Rev Subject/Comment Old New Mar 2000 S_07 SP-000012 -- -- Approved at TSG SA #7 and placed under Change Control 2.0.0 3.0.0 Mar 2000 -- -- -- -- cosmetic 3.0.0 3.0.1 Jun 2000 S_08 SP-000254 005 -- Split of TS - Part 4: Alarm Integration Reference Point (IRP): CMIP Solution Set (SS) 3.0.1 3.1.0 Sep 2000 -- -- -- -- cosmetic 3.1.0 3.1.1 Dec 2001 S_14 SP-010635 002 -- Correction of undefined, conflicting and invalid ASN.1 definitions 3.1.0 3.2.0 ETSI ETSI TS 132 111-4 V3.2.0 (2001-12) 27 3G TS 32.111-4 version 3.2.0 Release 1999 History Document history V3.1.0 July 2000 Publication V3.1.1 September 2001 Publication V3.2.0 December 2001 Publication
|
edce5b75ce09b6ac29afc1cdb433495e
|
132 106-1
|
1 Scope
|
........................................................................................................................................................6
|
edce5b75ce09b6ac29afc1cdb433495e
|
132 106-1
|
2 References
|
................................................................................................................................................6
|
edce5b75ce09b6ac29afc1cdb433495e
|
132 106-1
|
3 Definitions and abbreviations
|
..................................................................................................................7
|
edce5b75ce09b6ac29afc1cdb433495e
|
132 106-1
|
3.1 Definitions
|
......................................................................................................................................................... 7
|
edce5b75ce09b6ac29afc1cdb433495e
|
132 106-1
|
3.2 Abbreviations
|
..................................................................................................................................................... 8
|
edce5b75ce09b6ac29afc1cdb433495e
|
132 106-1
|
4 Network Configuration Management (CM)
|
............................................................................................9
|
edce5b75ce09b6ac29afc1cdb433495e
|
132 106-1
|
4.1 General
|
............................................................................................................................................................... 9
|
edce5b75ce09b6ac29afc1cdb433495e
|
132 106-1
|
4.1.1 Installing a 3G network
|
................................................................................................................................ 9
|
edce5b75ce09b6ac29afc1cdb433495e
|
132 106-1
|
4.1.2 Operating a 3G network
|
............................................................................................................................... 9 4.1.3 Growing/pruning a 3G network ................................................................................................................... 9
|
edce5b75ce09b6ac29afc1cdb433495e
|
132 106-1
|
4.1.3.1 System up-date
|
..................................................................................................................................... 10
|
edce5b75ce09b6ac29afc1cdb433495e
|
132 106-1
|
4.1.3.2 System up-grade
|
................................................................................................................................... 10
|
edce5b75ce09b6ac29afc1cdb433495e
|
132 106-1
|
4.2 Operational context for CM
|
............................................................................................................................. 11
|
edce5b75ce09b6ac29afc1cdb433495e
|
132 106-1
|
4.2.1 Administrative aspects of CM
|
.................................................................................................................... 11
|
edce5b75ce09b6ac29afc1cdb433495e
|
132 106-1
|
4.2.1.1 Security aspects
|
.................................................................................................................................... 11
|
edce5b75ce09b6ac29afc1cdb433495e
|
132 106-1
|
4.2.1.2 Data validity
|
......................................................................................................................................... 11
|
edce5b75ce09b6ac29afc1cdb433495e
|
132 106-1
|
4.2.1.3 Data consistency and distribution of the MIB
|
...................................................................................... 12
|
edce5b75ce09b6ac29afc1cdb433495e
|
132 106-1
|
5 CM service components
|
.........................................................................................................................13
|
edce5b75ce09b6ac29afc1cdb433495e
|
132 106-1
|
5.1 System modification service component
|
......................................................................................................... 13
|
edce5b75ce09b6ac29afc1cdb433495e
|
132 106-1
|
5.2 System monitoring service component
|
............................................................................................................ 14
|
edce5b75ce09b6ac29afc1cdb433495e
|
132 106-1
|
6 CM functions
|
.........................................................................................................................................14
|
edce5b75ce09b6ac29afc1cdb433495e
|
132 106-1
|
6.1 System modification functions
|
........................................................................................................................ 14
|
edce5b75ce09b6ac29afc1cdb433495e
|
132 106-1
|
6.1.1 Creation of NEs and NRs
|
........................................................................................................................... 15
|
edce5b75ce09b6ac29afc1cdb433495e
|
132 106-1
|
6.1.2 Deletion of NEs and NRs
|
........................................................................................................................... 15
|
edce5b75ce09b6ac29afc1cdb433495e
|
132 106-1
|
6.1.3 Conditioning of NEs and NRs
|
.................................................................................................................... 16
|
edce5b75ce09b6ac29afc1cdb433495e
|
132 106-1
|
6.1.3.1 Considerations on conditioning mechanisms
|
....................................................................................... 16
|
edce5b75ce09b6ac29afc1cdb433495e
|
132 106-1
|
6.1.3.2 Network traffic considerations
|
............................................................................................................. 17
|
edce5b75ce09b6ac29afc1cdb433495e
|
132 106-1
|
6.2 System monitoring functions
|
........................................................................................................................... 17
|
edce5b75ce09b6ac29afc1cdb433495e
|
132 106-1
|
6.2.1 Information request function
|
...................................................................................................................... 17
|
edce5b75ce09b6ac29afc1cdb433495e
|
132 106-1
|
6.2.2 Information report function
|
........................................................................................................................ 18 6.2.3 Response/report control function ............................................................................................................... 18 7 Itf-N Interface ........................................................................................................................................18
|
edce5b75ce09b6ac29afc1cdb433495e
|
132 106-1
|
7.1 CM principles
|
.................................................................................................................................................. 18
|
edce5b75ce09b6ac29afc1cdb433495e
|
132 106-1
|
7.2 Overview of IRPs related to CM
|
..................................................................................................................... 19
|
edce5b75ce09b6ac29afc1cdb433495e
|
132 106-1
|
7.3 Passive CM
|
...................................................................................................................................................... 19
|
edce5b75ce09b6ac29afc1cdb433495e
|
132 106-1
|
7.3.1 Real-time forwarding of CM-related event reports
|
.................................................................................... 19 7.3.2 Retrieval/synchronisation of CM-related information on NM request....................................................... 19
|
edce5b75ce09b6ac29afc1cdb433495e
|
132 106-1
|
7.4 Active CM
|
....................................................................................................................................................... 20 Annex A (informative): Change history...............................................................................................21 3G TS 32.106-1 version 3.1.0 Release 1999 ETSI 3G TS 32.106-1 version 3.1.0 (2000-07) 4 Foreword This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). The present document is part 1 of a multi-part TS covering the 3rd Generation Partnership Project: Technical Specification Group Services and System Aspects; Telecommunication Management; Configuration Management, as identified below: Part 1: "3G Configuration Management: Concept and Requirements"; Part 2: "Notification Integration Reference Point: Information Service Version 1"; Part 3: "Notification Integration Reference Point: CORBA Solution Set Version 1:1"; Part 4: "Notification Integration Reference Point: CMIP Solution Set Version 1:1"; Part 5: "Basic Configuration Management IRP Information Model (including NRM) Version 1"; Part 6: "Basic Configuration Management IRP CORBA Solution Set Version 1:1"; Part 7: "Basic Configuration Management IRP CMIP Solution Set Version 1:1"; Part 8: "Name Convention for Managed Objects". The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. Introduction 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. Clauses 4 to 6 give an introduction and description of the main concepts of CM, which are not mandatory for compliance with this specification in Release 99. Clause 7 contains the specific definitions for the standardised interface Itf-N, which are necessary to follow for compliance. 3G TS 32.106-1 version 3.1.0 Release 1999 ETSI 3G TS 32.106-1 version 3.1.0 (2000-07) 5 Clause 4 provides a brief background of CM while Clause 5 explains CM services available to the operator. Clause 6 breaks these services down into individual CM functions, which support the defined services. Clause 7 defines the Itf-N (see 3G TS 32.102 [2]) to be used for 3G CM. 3G TS 32.106-1 version 3.1.0 Release 1999 ETSI 3G TS 32.106-1 version 3.1.0 (2000-07) 6 1 Scope The present document describes the Configuration Management (CM) aspects of managing a 3G network. This is described from the management perspective in 3G TS 32.101 [1] and 3G TS 32.102 [2]. The present document defines a set of controls to be employed to effect set-up and changes to a 3G network in such a way that operational capability and Quality Of Service (QOS), network integrity and system inter working are ensured. In this way, the present document describes the interface definition and behaviour for the management of relevant 3G NEs in the context of the described management environment. The context is described for both the management system (OS) and Network Element (NE) functionality. Clause 7 contains the specific definitions for the standardised N interface, which are necessary to follow for compliance to this specification. The Itf-N for CM 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 3G TS 32.101 [1] and 3G TS 32.102 [2]. For CM, a number of IRPs (and the Name Convention) are defined herein, used by this as well as by other specifications for Telecom Management produced by 3GPP. All these are included in Parts 2 through 8 of the present document as follows: Notification IRP Information Service Version 1: 32.106 Part 2 Notification IRP CORBA Solution Set Version 1:1: 32.106 Part 3 Notification IRP CMIP Solution Set Version 1:1: 32.106 Part 4 Basic Configuration Management IRP Information Model (including NRM) Version 1: 32.106 Part 5 Basic Configuration Management IRP CORBA Solution Set Version 1:1: 32.106 Part 6 Basic Configuration Management IRP CMIP Solution Set Version 1:1: 32.106 Part 7 Name Convention for Managed Objects: 32.106 Part 8 2 References The following documents contain provisions, which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • For a non-specific reference, the latest version applies. [1] 3G TS 32.101: "3G Telecom Management principles and high level requirements". [2] 3G TS 32.102: "3G Telecom Management architecture". [3] 3G TS 32.106-5: "Basic Configuration Management IRP: Information Model". [4] ITU-T Recommendation X.721: "Information technology - Open Systems Interconnection - Structure of management information: Definition of management information". [5] ITU-T Recommendation X.730: "Information technology - Open Systems Interconnection - Systems Management: Object Management Function". [6] ITU-T Recommendation X.731: "Information technology - Open Systems Interconnection - Systems Management: State management function". [7] ITU-T Recommendation X.734: "Information technology - Open Systems Interconnection - Systems Management: Event report management function". 3G TS 32.106-1 version 3.1.0 Release 1999 ETSI 3G TS 32.106-1 version 3.1.0 (2000-07) 7 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply. Data: is any information or set of information required to give software or equipment or combinations thereof a specific state of functionality. Element Manager (EM): provides a package of end-user functions for management of a set of closely related types of Network Elements (NEs). These functions can be divided into two main categories: - Element Management Functions for management of NEs on an individual basis. These are basically the same functions as supported by the corresponding local terminals. - Sub-Network Management Functions that are related to a network model for a set of NEs constituting a clearly defined sub-network, which may include relations between the NEs. This model enables additional functions on the sub-network level (typically in the areas of network topology presentation, alarm correlation, service impact analysis and circuit provisioning). Firmware: is a term used in contrast to software to identify the hard-coded program, which is not downloadable on the system. Hardware: is each and every tangible item. IRP Information Model: See 3G TS 32.101 [1]. IRP Information Service: See 3G TS 32.101 [1]. IRP Solution Set: See 3G TS 32.101 [1]. Managed Object (MO): an abstract entity, which may be accessed through an open interface between two or more systems, and representing a Network Resource (NR) for the purpose of management. The Managed Object (MO) is an instance of a Managed Object Class (MOC) as defined in a Management Information Model (MIM). The MIM does not define how the MO or NR is implemented; only what can be seen in the interface. Managed Object Class (MOC): a description of all the common characteristics for a number of MOs, such as their attributes, operations, notifications and behaviour. Managed Object Instance (MOI): an instance of a MOC, which is the same as a MO as described above. Management Information Base (MIB): the set of existing managed objects in a management domain, together with their attributes, constitutes that management domain's MIB. The MIB may be distributed over several OS/NEs. Management Information Model (MIM): also referred to as NRM – see the definition below. There is a slight difference between the meaning of MIM and NRM – the term MIM is generic and can be used to denote any type of management model, while NRM denotes the model of the actual managed telecommunications Network Resources (NRs). Network Element (NE): is a discrete telecommunications entity, which can be, managed over a specific interface e.g. the RNC. Network Manager (NM): provides a package of end-user functions with the responsibility for the management of a network, mainly as supported by the EM(s) but it may also involve direct access to the NEs. All communication with the network is based on open and well-standardised interfaces supporting management of multi-vendor and multi- technology NEs. Network Resource (NR): is a component of a NE, which can be identified as a discrete separate entity and is in an object oriented environment for the purpose of management represented by an abstract entity called Managed Object (MO). 3G TS 32.106-1 version 3.1.0 Release 1999 ETSI 3G TS 32.106-1 version 3.1.0 (2000-07) 8 Network Resource Model (NRM): a model representing the actual managed telecommunications Network Resources (NRs) that a System is providing through the subject IRP. An NRM describes Managed Object Classes (MOC), their associations, attributes and operations. The NRM is also referred to as "MIM" (see above) which originates from the ITU-T TMN. Object Management Group (OMG): see http://www.omg.org. Operations System (OS): indicates a generic management system, independent of its location level within the management hierarchy. Operator: is either - a human being controlling and managing the network; or - a company running a network (the 3G network operator). Optimisation: of the network is each up-date or modification to improve the network handling and/or to enhance subscriber satisfaction. The aim is to maximise the performance of the system. Re-configuration: is the re-arrangement of the parts, hardware and/or software that make up the 3G network. A re- configuration can be of the parts of a single NE or can be the re-arrangement of the NEs themselves, as the parts of the 3G network. A re-configuration may be triggered by a human operator or by the system itself. Reversion: is a procedure by which a configuration, which existed before changes were made, is restored. Software: is a term used in contrast to firmware to refer to all programs which can be loaded to and used in a particular system. Up-Dates: generally consist of software, firmware, equipment and hardware, designed only to consolidate one or more modifications to counter-act errors. As such, they do not offer new facilities or features and only apply to existing NEs. Up-Grades: can be of the following types: - enhancement - the addition of new features or facilities to the 3G network; - extension - the addition of replicas of existing entities. 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: CM Configuration Management CMIP Common Management Information Protocol CORBA Common Object Request Broker Architecture EM Element Manager FM Fault Management FW Firmware HW Hardware IRP Integration Reference Point ITU-T International Telecommunication Union, Telecommunication Standardisation Sector MIB Management Information Base MIM Management Information Model MOC Managed Object Class MOI Managed Object Instance NE Network Element NM Network Manager NR Network Resource NRM Network Resource Model OMG Object Management Group OS Operations System OSF Operations System Function PM Performance Management 3G TS 32.106-1 version 3.1.0 Release 1999 ETSI 3G TS 32.106-1 version 3.1.0 (2000-07) 9 RNC Radio Network Controller SW Software TM Telecom Management TRX Transceiver UML Unified Modelling Language (OMG) UMTS Universal Mobile Telecommunications System 4 Network Configuration Management (CM) 4.1 General In the development of a 3G network, three general phases can be described which represent different degrees of stability. Once the first stage is over, the system will cycle between the second and the third phases. This is known as the network life-cycle and includes: 1) the 3G network is installed and put into service; 2) the 3G network reaches certain stability and is only modified (dynamically) to satisfy short-term requirements. E.g. by (dynamic) re-configuration of resources or parameter modification; this stable state of a 3G network cannot be regarded as the final one because each equipment or SW modification will let the 3G network progress to an unstable state and require optimisation actions again; 3) the 3G network is being adjusted to meet the long-term requirements of the network operator and the customer, e.g. with regard to performance, capacity and customer satisfaction through the enhancement of the network or equipment up-grade. During these phases, the operators will require adequate management functions to perform the necessary tasks. 4.1.1 Installing a 3G network When a 3G network is installed and initialised for the first time, all NEs need to be introduced to the NM, the data for initialisation and SW for proper functioning need to be provided. All these actions are carried out to create NEs and to initialise them. 4.1.2 Operating a 3G network Whilst in service, the operator needs to react to short term incidents such as traffic load requirements, which are different from the current network capabilities, NEs/NRs need to be re-configured and parameters need to be adapted to follow these day-to-day requirements. 4.1.3 Growing/pruning a 3G network As the 3G network grows and matures new equipment is installed and understanding of system behaviour increases. Subscriber requirements/wishes may demand that operators modify their system. In addition manufacturers improve the infrastructure components and add features to their products hence the operator will start modifying the 3G network to profit from these changes and to improve subscriber satisfaction. Additionally, the 3G network configuration will be modified (i.e. it will be up-dated or up-graded) to cope with a need for increasing or decreasing network capacity. These actions are carried out for the long-term strategy of the operators to optimise the network. 3G TS 32.106-1 version 3.1.0 Release 1999 ETSI 3G TS 32.106-1 version 3.1.0 (2000-07) 10 4.1.3.1 System up-date Whenever the 3G network needs to be improved for reasons of reducing failures, the system will be up-dated. In this case SW or equipment will be replaced without adding new functionality or resources to the network. The basic function required is: − the modification of existing SW/equipment; it may be necessary to introduce a different set of data to cope with the modified SW/equipment. For system up-date the network shall not be disturbed in its function until the required modification is activated. This requires mechanisms to: − do SW/data downloading in parallel with on-going traffic; − isolate the affected NEs/NRs from traffic before the actual modification is done; − minimise system outage due to the activation of up-dated components. 4.1.3.2 System up-grade System up-grade may affect all areas of 3G network activities and can be described as enhancements, whereby either new features or new facilities are implemented. This CM aspect also covers extensions, reductions or further replications of existing facilities. The CM functions employed are: − Creation of NEs and/or NRs; − Deletion of NEs and/or NRs; and − Modification of NEs and/or NRs. The following requirements are to apply: − to support expeditious handling of SW and data while minimising impact on ongoing traffic; − to follow a required sequence of up-grades: e.g. the new SW depends upon the availability of the new equipment functionality; − to provide the capability to create an additional logical NE/NR without having installed the physical resource supporting it: for example it should be possible to create a cell in an RNC without the physical equipment present or connected. However, additional mechanisms should be in place to prevent any service connection to any physically non-existent NE/NR or reporting failures from non-existing NE/NR; − to provide the capability to install an additional physical NE/NR without creation of the logical resource managing it (no management functionality) and without impact of the current functionality; − to provide the capability to prevent the erroneous taking into service of a NE/NR which is not fully installed and initialised: whenever a NE/NR is modified (extension or reduction) it shall be taken out of service until the logical part of the procedure is finished. An extended NE/NR cannot be placed into service until all needed parameters and equipment are initialised. Likewise, a reduced NE/NR cannot be placed back into service until the applicable re-configuration is performed. When the network is up-graded by the addition of NEs or NRs or a change in the configuration, it is essential that the NE/NR can be restored to the configuration, which existed before the changes were made. This procedure is called "reversion" and is useful in maintaining service if any difficulty should arise from a network up-grade. 3G TS 32.106-1 version 3.1.0 Release 1999 ETSI 3G TS 32.106-1 version 3.1.0 (2000-07) 11 4.2 Operational context for CM The CM functions available to the operator need to address various aspects beyond that which might strictly be regarded as management of the network. These include: − assisting the operator in making the most timely and accurate changes thus avoiding lengthy waiting periods or complex scenarios; − ensuring that CM actions will not have any secondary effects on the network other than the specified ones; − providing mechanisms to protect the telecommunication-related traffic from effects due to CM actions - it shall be possible to inhibit traffic if a traffic affecting CM action is expected and to gracefully release calls prior to the closure of the resource; − providing mechanisms to overcome data inconsistency problems by logging the modifications for reversion reasons, or to recover through data update from a second source. 4.2.1 Administrative aspects of CM When managing the network by creating, deleting or modifying NEs/NRs, the operator should ensure that there is no uncontrolled impact on the network. The network management system therefore needs to support the following set of management functionalities when addressing various administrative aspects: − Security; − Data Validity; − Data Consistency; and − Resource Administration. 4.2.1.1 Security aspects It is ultimately up to the operator to ensure the network security by employing the appropriate mechanisms for control of logical and physical access. Changes of the network configuration shall be possible only for operators with appropriate authorisation profiles. 4.2.1.2 Data validity It is the responsibility of all management systems and NEs that data input to and transferred between the systems is valid given the particular management context. 3G TS 32.106-1 version 3.1.0 Release 1999 ETSI 3G TS 32.106-1 version 3.1.0 (2000-07) 12 4.2.1.3 Data consistency and distribution of the MIB The Network Manager (NM) and Element Manager (EM) use different object model abstractions of the network's (NEs') physical and logical resources to be managed by these systems. This is the agreed Network Resource Model (NRM) between the NM and EM/NEs to be used at the N interface and EM-NE interface (see ref. 3G TS 32.102 [2] for the definition of these interfaces). The NRM of the N interface is fully standardised (see 3G TS 32.106-5 [3]) while the NRM for the EM-NE interface is product-specific and is not standardised in this or related TSs. The NE local representation of those physical and logical instantiated resources to be managed, as well as their accurate mapping onto the agreed object model abstraction, is also product-specific. Thus the consistency between the actual local representation of physical and logical resources to be managed within an NE, and the corresponding view of the OS, relies on: − Which information is exchanged between the NE and the management systems; For the EM-NE interface this is defined in a product-specific NRM, where the actual network infrastructure is modelled. This is internal to a specific development organisation and does not need to be open; thus it is not further discussed in the present document. In fact, by publishing the management information portion of these interfaces, too much of the internal design will be revealed and it may become impossible or at least very expensive and time-consuming to later enhance the systems using the interface. For the Itf-N between NM and EM/NE, the NRM as mentioned above is defined in 3G TS 32.106-5 [3]. − How such information is exchanged between NE and management systems - this is for the Itf-N fully standardised by the present and related documents, while for the EM-NE interface only the protocol is standardised (cf. Figure 2 in 3G TS 32.102 [2]). − How information is locally represented and treated by an NE and by its associated (OSs); this is a product- specific choice of the manufacturers of NEs and OSs. − Where this information is kept; whether it is kept only at the "origin NEs" where the Managed Object Instances (MOIs) representing the managed NRs are created (NE-local MIB), or if also a copy of that information is kept in one or several of the OSs ("mirrored MIB"). This is again a product-specific choice of the manufacturers of NEs and OSs. If the "NE-local MIB" approach is chosen, the consistency "only" has to be maintained between the NEs, while if the "mirrored MIB" approach is chosen, the consistency has to maintained between the NEs as well as the NM/EM and the NEs. A peer-to-peer data consistency between NM-EM and EM-NE does not guarantee overall data consistency from a network point of view. It is however possible for the NM to maintain consistency on the network level, as far as the information in the MIB for the Itf-N is concerned, by comparing related information (MOIs and attributes) in all connected systems (EMs and NEs) in the managed network. In order to promote data consistency, the following operational procedures are recommended: − Awareness of autonomous NE re-configuration: local NE re-configuration, for example partial or full reversion mechanisms (either triggered autonomously or by an operator), should always be reported; − Define appropriate audit procedures on the N- and EM-NE- interface to support MIB re-synchronisation: A. In case the "mirrored MIB" approach is chosen, take the following actions: 1. The NM shall be able to retrieve all management information from the EM and NE accessible via the Itf-N by applying appropriate data retrieval methods (periodically or on request); 2. The NM shall after the retrieval compare the retrieved information with its own data and if necessary also compare related information between connected NEs (if the MIB stored in the NM already has been checked and found consistent, the latter step is not necessary); 3. The NM shall report any deviations between the NE's view and the NM's view, and related NEs' views, to the operator; 4. The NM shall automatically, or on operator command, after the check in step 2 above correct the deviating information in either the NM or the NEs (depending on whether the NEs or NM are regarded as "master" for the information; this is manufacturer dependent). 3G TS 32.106-1 version 3.1.0 Release 1999 ETSI 3G TS 32.106-1 version 3.1.0 (2000-07) 13 B. In case the "NE-local MIB" approach is chosen the following actions shall be taken: 1. The NM shall be able to retrieve all management information from the EM and NE accessible via the Itf-N by applying appropriate data retrieval methods (periodically or on request); 2. The NM shall after the retrieval compare the retrieved information between connected NEs; 3. The NM shall report any deviations between the related NEs' views to the operator; 4. The NM shall automatically, or on operator command, after the check in step 2 above correct the deviating information in the NEs. − If the "mirrored MIB" approach is chosen, the NM/EM view shall be maintained. As far as possible, operational concepts for data manipulation should employ the NM/EM as the only managing system for an NE. If however access to local NE data is given to maintenance personnel, the following actions are recommended/ necessary in order to enable the NM/EM to maintain data consistency: − applying a remote OS terminal for the local access to the NE under consideration rather than directly modifying NE data without any control of the OS; − changes made locally shall be notified to the managing OS(s). 5 CM service components While a 3G network is first installed and brought into service, and following installation the 3G network operator will enhance and adapt the network to short and long term requirements. In addition, it will be optimised to satisfy customer needs. To cover these aspects of CM, the system will provide the operator with the following capabilities: − initial system installation to establish the network; − system operation to adapt the system to short term requirements; − system up-date whenever it is necessary to modify the system to overcome SW bugs or equipment faults; − system up-grade to enhance or extend the network by features or equipment respectively. These capabilities are provided by the management system through its service components: − system modification to change the network to meet the operators requirements; − system monitoring to gain an overview on the present SW, equipment and data situation of the network. The service components will be explained in more detail in the following subclauses. 5.1 System modification service component Whenever it is necessary to adapt the system data to a new requirement due to optimisation or new network configurations, it will require an operator action to introduce new or modified data into the system. The data will be distributed to: − either one EM/NE when dealing with a locally limited modification; or − each EM/NE concerned when the change affects multiple EM/NEs; and − the other NMs in the case where multiple NMs exist in the same management domain. This implies the necessity of mechanisms to ensure data integrity and to maintain system data consistency (cf. subclause 4.2.1.3). The concept of system modification includes the following aspects: 3G TS 32.106-1 version 3.1.0 Release 1999 ETSI 3G TS 32.106-1 version 3.1.0 (2000-07) 14 − if subscriber traffic impacting data modifications are performed, the NEs/NRs concerned are first cleared from traffic in a controlled way; − the necessary modification is performed by the EM/NE; − only once all needed data is given to the system, are the concerned NEs/NRs put back into traffic again; − safeguards shall be available within the NEs to prevent changes to configuration affecting service(s) in use. In emergencies, it shall be possible to override these safeguards. On occasion, modifications may not be stable or not fulfil the operator intentions. In these cases, reversion to the previous stable configuration may be necessary. Occasionally there will be changes to the network that create a new configuration, which cannot revert to any previous network status for protection. Such changes may involve major equipment modification to the core elements of the network or re-distribution of traffic across interconnected nodes to other Operators. In these cases it is necessary to implement the changes and to manage the consequences of any problems or failures without the protection of 'reversion', as equipment may have been removed or the work programme may be complex, time limited and expensive. Progress of these changes should be sequential through an agreed milestone plan which includes effective tests to prove network functionality with only one action, or a coherent series of actions, completed at a time. The decision points, beyond which there is no return, should be clearly identified. "Automatic re-configuration" shall not be dealt with in the present document as it is dependent on the implementation. However, if an automatic re-configuration occurs, the operator shall be informed of the result. 5.2 System monitoring service component The system monitoring service component provides the operator with the ability to receive reports (on request or spontaneously) on the configuration of the entire network or parts of it from managed NEs. These consist of structure, states, versions employed and data settings. The NE sends spontaneous reports if there was an autonomous change of, for example, the states or other values due to Fault Management (FM) actions. Also, the NM may ask the managed EM/NE to send the information required to the NM at any time. The data that shall be possible to provide on request is a subset of, or the whole, MIB, which is an instantiation of the NRM, defined in 3G TS 32.106-5 [3]. Any inconsistencies found during system monitoring by the NM should be reported to the operator, and it is left to the operator or an Operations System Function (OSF) to take appropriate actions. 6 CM functions 6.1 System modification functions The requirements of CM and their usage lead to basic CM functions to be defined for the network. These describe the required actions on managed elements (NEs or NRs) and the expected reactions. The system modification functions identified are: − Creation of Network Elements (NEs) and Network Resources (NRs); − Deletion of NEs and NRs; − Conditioning of NEs and NRs. 3G TS 32.106-1 version 3.1.0 Release 1999 ETSI 3G TS 32.106-1 version 3.1.0 (2000-07) 15 For all identified functions, the following major requirements apply: − minimum disturbance of the network by taking the affected resources out of service if needed; − physical modifications should be independent of the related logical modifications; − all the required actions to satisfy a defined task should be completed correctly before the resources can be brought into service; − data consistency checks shall be performed as described in subclause 4.2.1.3. There are three aspects of NE and NR management, which can be distinguished: 1) Management of the physical aspect (equipment); 2) Management of the executable aspect (SW and FW); and 3) Management of the logical/ functional aspect (data). All three management aspects are addressed by the present document. 6.1.1 Creation of NEs and NRs The creation of a NE or NR is used to initially set up a 3G network or to extend an already existing network. The action of creation is a combination of installation, initialisation and introduction of the newly installed equipment to the network and to the OS, which will control it. The creation can affect equipment, SW and data. Whenever a 3G network or parts of it are installed, the created NEs/NRs requires to be: − physically installed and tested and initialised with a possible default configuration; − logically installed by means of introduction to the network, possibly involving changes to related existing NE/NR configurations; − allowed to be put into service. The sequence of physical and logical installation may vary depending on the specific 3G network operator strategy. In case the logical creation takes place before the physical creation no related alarms shall be reported to the operator. 6.1.2 Deletion of NEs and NRs If a network is found to be over-equipped, the operator may wish to reduce the scale of the network or to re-use the spare equipment elsewhere. This can occur when an operator over-estimates the traffic in one area and, for example, under-estimates the load in a different one. The deletion of a NE or NR requires: − taking the affected NEs or NRs out of service; − logical removal from the network (possibly involving changes to other NE or NR configurations, for example, neighbour cell description); − if necessary, the physical dismantling of the equipment; − return of other affected NEs or NRs to service. The sequence of logical and physical removal will not matter if the affected NEs are taken out of service prior to their removal. This will help to protect the network from error situations. 3G TS 32.106-1 version 3.1.0 Release 1999 ETSI 3G TS 32.106-1 version 3.1.0 (2000-07) 16 6.1.3 Conditioning of NEs and NRs There are three categories of modifications to be regarded with respect to NEs or NRs. It is possible to either modify SW, equipment or data or a certain combination of them. Which aspects are affected by any particular modification is implementation dependent. When an MO/NR is to be modified the following actions shall be performed: − Locking or logical removal of the MO/NR (including first clearing it from traffic if necessary); − Required modification (physical and/or logical); and − Unlocking or logical re-installation of the MO/NR. This sequence is recommended to provide protection to the network against fault situations, which may occur during the modification process. By default, locking/modification/unlocking shall be the procedure to follow, and if logical removal/re-installation is necessary for a certain MO/NR, this shall be described in the NRM. The result of conditioning should be able to be determined by the operator by employing the appropriate mechanisms provided through the System Monitoring functions (see subclause 6.2). A modification to data, which has a controlling influence on some resources, could influence the resource throughput or its capability to originate new traffic during the modification time. This distinction is made because, for particular modifications, the capacity of the NR can be decreased without influencing the ongoing traffic. Before deciding to perform an action, the operator should consider the effects that a modification might have on capacity, throughput and current activity of a resource. 6.1.3.1 Considerations on conditioning mechanisms The data, which characterise a 3G network, will not all be subject to the same rate of change or need to be modified using the same mechanism. Changes to the logical configuration may also need to be applied across multiple NEs. These aspects are described in the following subclauses. Whenever the configuration of the network requires modification, the following questions will be important to the operator: − What will be the influence on the ongoing traffic? − What will be the impact on the capacity of the network? − How difficult and time-consuming will the modification procedure be? The answer to these questions will give an idea as to when the modification can be best performed with the aim to keep traffic disturbance as low as possible and to require the modification process itself to cause as little disturbance as possible. On the other hand, it does not seem to be reasonable to invent a "low disturbance" modification algorithm for each single parameter, especially those, which are only modified once or twice during the lifetime of the network. These rare modifications could be performed with an acceptable level of interruption to traffic. Therefore, the system data elements may be classified by: − modification once or twice during the life time of the system (e.g. protocol supervision timers); − modification required seldom; − modification is expected frequently and/or for a short term (telecom parameters). Depending on this rating the requirements on the modification mechanism for certain data elements should vary. 3G TS 32.106-1 version 3.1.0 Release 1999 ETSI 3G TS 32.106-1 version 3.1.0 (2000-07) 17 6.1.3.2 Network traffic considerations As stated previously, different types of modification mechanisms can be distinguished with regard to their impact on traffic and their extent: For the impact regarding traffic, the following types can be identified: − no impact on the traffic at all: the modified data values have no relation to the traffic capability; − impact on traffic: the data modification causes for example a change in the volume of allowable traffic without affecting existing traffic. For the impact regarding extent, the following types can be identified: − Impact on only the NR or NE The modification of SW, equipment or data is effective for a NR, or a complete NE. − Impact on more than one NE or different NRs of one NE Certain modifications on SW, equipment or data will require changes to be performed upon more than one NR in one NE or more than one NE. Such changes require consideration of data consistency, data integrity and network integrity. E.g. it should be distinguished between the NR directly affected by a modification and other impacted NRs. The relationships and dependencies between data values should be described and a mechanism defined to protect the system against inconsistency. 6.2 System monitoring functions A major aspect of CM is the ability of the operator to monitor the operation of the network. This monitoring capability is necessary for the operator to determine the current operational state of the network as well as to determine the consistency of information among various NEs. The monitoring capability requires three functions to support it: the information request function, the information report function and the response/report control function. 6.2.1 Information request function In order to support the operator's need to monitor the network, the NM needs to be able to gather information on request from the various EMs and/or NEs. The EM may then act as a mediator for one or more NEs (how this is done is product specific and outside the scope of the present document). The information request function should support the capabilities of the NM to be able to request information for any single attribute defined in the management information base. In addition, the NM should be able to gather large amounts of information in a single request by providing appropriate scope and filtering constructs in the request. On receipt of a valid request, the addressed EM/NE shall respond with the current values of the specified data elements. This response will be immediate if so requested by the NM. However, in cases where very large amounts of data are concerned and where the EM and the NE support the capabilities, the NM may request the EM/NE to store the information in a file and transfer it using a file transfer mechanism. In case there is a communication failure when a response is to be sent, the response shall be safely stored and forwarded as soon as possible after re-establishment of communication. An exception that may inhibit this type of delayed response, is if the transaction has timed out in the requesting NM. 3G TS 32.106-1 version 3.1.0 Release 1999 ETSI 3G TS 32.106-1 version 3.1.0 (2000-07) 18 6.2.2 Information report function In addition to being able to provide information on request, the NE is required to have the capability of reporting notifications about changed/removed information autonomously. Generally this will be performed when some information on the state or operation of the system has changed. The following shall be supported: - The following type of events shall be notified to the NM, if enabled by the NM (these three notification types may be enabled/disabled separately by the NM): 1. Object creation/deletion; 2. Attribute value change; 3. State change; - Optionally: The above mentioned notifications may be logged locally at the EM/NE. Logged notifications may be requested by the NM to be transferred from the EM/NE. Transfer mechanisms may be by file transfer or using messages; - In case there is a communication failure when one or more notifications are to be forwarded, the notification(s) shall be safely stored and forwarded as soon as possible after re-establishment of communication. 6.2.3 Response/report control function For responses to information requests and for information reports, it should be possible for the operator to specify where and when the information should go. The NM, EM and NE shall provide a capability to configure the response/reporting capabilities such that the following requirements are met at the Itf-N: − information forwarding shall be possible to be enabled and disabled; − information shall be possible to be forwarded to the NM as soon as it is available; − information shall be possible to be directed to any of various NMs (one or several). 7 Itf-N Interface 7.1 CM principles The Itf-N (see ref. 3G TS 32.102 [2]) is an object oriented interface, i.e. all resources of the 3G network (functional and physical resources) whose management is standardised by the present document are represented as Managed Object Instances (MOI) of a Network Resource Model (NRM). The NRM shall be highly simplified for the purpose of the NM, based on the assumption that all of the detailed CM actions, including fault correction after one or more alarms, are performed by an Element Manager (EM), which knows the vendor-specific NRM and configuration. The NRM identifies the basic Network Resources (NRs) to the level of detail required by FM and PM at the Network Management (NM) level. In addition to NR identification, the NRM also supports the alarm surveillance part of FM by defining which alarms can be notified by which Managed Object Classes (MOCs). The definition of the Network Resource Model (NRM) for the Itf-N (connecting the NM with a "subordinate entity", which may be an EM or a NE) is described in 3G TS 32.106-5 [3], which defines the Basic CM IRP Information Model including the NRM applicable to UMTS management. 3G TS 32.106-1 version 3.1.0 Release 1999 ETSI 3G TS 32.106-1 version 3.1.0 (2000-07) 19 This clause describes the specific functional requirements related to CM of Network Resources (NRs) on the Itf-N, which may be classified in two main groups: - Passive CM (configuration overview), which mainly provides to the NM current information about the current configuration changes and allows a retrieval and synchronisation of configuration related data on NM request. The forwarding of these notifications over the Itf-N is controlled by means of configuring adequate filtering mechanisms within the subordinate entities. The Itf-N also provides the means for storage ("logging") and later retrieval of desired information within the subordinate entities. - Active CM, which offers to the NM operator a real capability to change the current network configuration. 7.2 Overview of IRPs related to CM The Itf-N for CM 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 [1] and [2]. For CM, a number of IRPs (and the Name Convention) are defined herein, used by this as well as other specifications For Telecom Management (TM) produced by 3GPP. All these are included in Parts 2 through 8 of the present document as follows: Notification IRP Information Service Version 1: 32.106 Part 2 Notification IRP CORBA Solution Set Version 1:1: 32.106 Part 3 Notification IRP CMIP Solution Set Version 1:1: 32.106 Part 4 Basic Configuration Management IRP Information Model (including NRM) Version 1: 32.106 Part 5 Basic Configuration Management IRP CORBA Solution Set Version 1:1: 32.106 Part 6 Basic Configuration Management IRP CMIP Solution Set Version 1:1: 32.106 Part 7 Name Convention for Managed Objects: 32.106 Part 8 7.3 Passive CM 7.3.1 Real-time forwarding of CM-related event reports During normal operation the NM is continuously informed by the managed subordinate entities about all network configuration changes, in accordance with the Network Resource Model (NRM) applied on the Itf-N. For this purpose the following CM-related event reports with regard to the ITU-T Recommendation X.721 [4], ITU-T Recommendation X.730 [5] and ITU-T Recommendation X.731 [6] are forwarded to the NM: - Object creation; - Object deletion; - Attribute value change. The real-time forwarding of these event reports occurs via appropriate filtering mechanisms ("discriminators" on CMIP interfaces, "subscription" on CORBA interfaces) located in the subordinate entity in accordance with ITU-T Recommendation X.734 [7] or OMG event/notification service. These filters may be controlled (i.e. created, modified and eventually deleted) locally in the subordinate entities or remotely by the NM (via the Itf-N) in order to ensure that only the event reports which fulfil pre-defined criteria can reach the superior NM. In a multiple manager environment each NM may have its own filtering mechanism within every subordinate entity, which is able to generate CM-related notifications. It should be possible to pack multiple notifications together for sending to NM. This provides more efficient use of data communication resources. In order to pack multiple notifications, an EM/NE configurable parameter defines the maximum number of notifications to be packed together. Additionally an EM/NE configurable parameter defines the maximum time delay before the notifications have to be sent. 7.3.2 Retrieval/synchronisation of CM-related information on NM request As long as the network is in operation and fault free, the update of the CM-related information on NM level is continuously ensured by the real-time forwarding of concerned reports as described in subclause 7.3.1. In case of faults 3G TS 32.106-1 version 3.1.0 Release 1999 ETSI 3G TS 32.106-1 version 3.1.0 (2000-07) 20 (either on the NM or in a subordinate entity or on the communication link) it is possible that some CM-related event reports are lost. Therefore the CM-related information on the NM may become non-aligned with the real configuration of the network (depending on the strategy of the NM where to store network configuration information). In this case a synchronisation process may be necessary to align the CM-related information of the NM with the configuration information of the subordinate entities. The retrieval or synchronisation ("alignment") of network configuration information between the NM and one or more of its subordinate entities can be triggered at any time by the NM. There are two different alternatives for this synchronisation: - via a read command with appropriate filtering; - as an ordered sequence of CM-related event reports. In Release 99 of the present document it is assumed that active CM is a task that can be performed only by the Element Managers (EMs) and/or local maintenance terminal actions. Thus it is outside the scope of the present document. 3G TS 32.106-1 version 3.1.0 Release 1999 ETSI 3G TS 32.106-1 version 3.1.0 (2000-07) 21 Annex A (informative): Change history Change history TSG SA# Version CR Tdoc SA New Version Subject/Comment S_07 2.0.0 - SP-000012 3.0.0 Approved at TSG SA #7 and placed under Change Control Mar 2000 3.0.0 3.0.1 Cosmetic S_08 3.0.1 001 SP-000241 3.1.0 Split of TS - Part 1: Main part of spec - Concept and Requirements 22 ETSI ETSI TS 132 106-1 V3.1.0 (2000-07) 3G TS 32.106-1 version 3.1.0 Release 1999 History Document history V3.0.1 March 2000 Publication as TS 132 106 V3.1.0 July 2000 Publication as TS 132 106-1
|
cacf9eed93e6daf37d9a13b7cf85a487
|
132 102
|
1 Scope
|
........................................................................................................................................................6
|
cacf9eed93e6daf37d9a13b7cf85a487
|
132 102
|
2 References
|
................................................................................................................................................6
|
cacf9eed93e6daf37d9a13b7cf85a487
|
132 102
|
2.1 Normative references
|
......................................................................................................................................... 6
|
cacf9eed93e6daf37d9a13b7cf85a487
|
132 102
|
2.2 Informative references
|
....................................................................................................................................... 6
|
cacf9eed93e6daf37d9a13b7cf85a487
|
132 102
|
3 Definitions, symbols and abbreviations
|
...................................................................................................7
|
cacf9eed93e6daf37d9a13b7cf85a487
|
132 102
|
3.1 Definitions
|
......................................................................................................................................................... 7
|
cacf9eed93e6daf37d9a13b7cf85a487
|
132 102
|
3.2 Abbreviations
|
..................................................................................................................................................... 8
|
cacf9eed93e6daf37d9a13b7cf85a487
|
132 102
|
4 General
|
...................................................................................................................................................10
|
cacf9eed93e6daf37d9a13b7cf85a487
|
132 102
|
4.1 UMTS
|
.............................................................................................................................................................. 10
|
cacf9eed93e6daf37d9a13b7cf85a487
|
132 102
|
4.1.1 UMTS Reference Model
|
............................................................................................................................ 10
|
cacf9eed93e6daf37d9a13b7cf85a487
|
132 102
|
4.1.2 UMTS Provisioning Entities
|
...................................................................................................................... 10
|
cacf9eed93e6daf37d9a13b7cf85a487
|
132 102
|
4.1.3 UMTS Management Infrastructure
|
............................................................................................................ 10
|
cacf9eed93e6daf37d9a13b7cf85a487
|
132 102
|
4.2 TMN
|
................................................................................................................................................................ 11
|
cacf9eed93e6daf37d9a13b7cf85a487
|
132 102
|
5 General view of UMTS Management Physical architectures
|
................................................................11
|
cacf9eed93e6daf37d9a13b7cf85a487
|
132 102
|
6 Basic objectives for a UMTS Physical Architecture
|
.............................................................................12
|
cacf9eed93e6daf37d9a13b7cf85a487
|
132 102
|
7 TM Architectural aspects
|
.......................................................................................................................13
|
cacf9eed93e6daf37d9a13b7cf85a487
|
132 102
|
7.1 Architectural relationship
|
................................................................................................................................ 13
|
cacf9eed93e6daf37d9a13b7cf85a487
|
132 102
|
7.2 Architectural constraints
|
.................................................................................................................................. 13
|
cacf9eed93e6daf37d9a13b7cf85a487
|
132 102
|
7.3 Interoperability
|
................................................................................................................................................ 14
|
cacf9eed93e6daf37d9a13b7cf85a487
|
132 102
|
7.3.1 Interfaces
|
.................................................................................................................................................... 14
|
cacf9eed93e6daf37d9a13b7cf85a487
|
132 102
|
7.3.2 Open systems approach
|
.............................................................................................................................. 16
|
cacf9eed93e6daf37d9a13b7cf85a487
|
132 102
|
7.3.3 Level of openness
|
....................................................................................................................................... 17
|
cacf9eed93e6daf37d9a13b7cf85a487
|
132 102
|
7.3.4 Closed interfaces
|
........................................................................................................................................ 17
|
cacf9eed93e6daf37d9a13b7cf85a487
|
132 102
|
7.4 Data communication networks
|
........................................................................................................................ 17
|
cacf9eed93e6daf37d9a13b7cf85a487
|
132 102
|
7.5 New technologies
|
............................................................................................................................................. 18
|
cacf9eed93e6daf37d9a13b7cf85a487
|
132 102
|
8 UMTS Management Physical architectures
|
...........................................................................................19
|
cacf9eed93e6daf37d9a13b7cf85a487
|
132 102
|
8.1 Compliance Conditions
|
.................................................................................................................................... 19
|
cacf9eed93e6daf37d9a13b7cf85a487
|
132 102
|
8.2 Network elements management architecture
|
................................................................................................... 19
|
cacf9eed93e6daf37d9a13b7cf85a487
|
132 102
|
8.3 Network & Subnetwork Element Management Architecture
|
.......................................................................... 21
|
cacf9eed93e6daf37d9a13b7cf85a487
|
132 102
|
8.4 Operations Systems interoperability architecture.
|
........................................................................................... 22
|
cacf9eed93e6daf37d9a13b7cf85a487
|
132 102
|
8.5 Operations Systems intra-operability architecture
|
........................................................................................... 23
|
cacf9eed93e6daf37d9a13b7cf85a487
|
132 102
|
8.6 Business System interconnection architecture
|
................................................................................................. 23
|
cacf9eed93e6daf37d9a13b7cf85a487
|
132 102
|
9 TMN applications
|
..................................................................................................................................25
|
cacf9eed93e6daf37d9a13b7cf85a487
|
132 102
|
10 Integration Reference Points (IRPs)
|
......................................................................................................27
|
cacf9eed93e6daf37d9a13b7cf85a487
|
132 102
|
10.1 General
|
............................................................................................................................................................. 27
|
cacf9eed93e6daf37d9a13b7cf85a487
|
132 102
|
10.2 Integration levels
|
............................................................................................................................................. 27
|
cacf9eed93e6daf37d9a13b7cf85a487
|
132 102
|
10.2.1 Application integration
|
............................................................................................................................... 27
|
cacf9eed93e6daf37d9a13b7cf85a487
|
132 102
|
10.3 Network infrastructure IRPs
|
............................................................................................................................ 28
|
cacf9eed93e6daf37d9a13b7cf85a487
|
132 102
|
10.4 Defining the IRPs
|
............................................................................................................................................ 29
|
cacf9eed93e6daf37d9a13b7cf85a487
|
132 102
|
10.5 Mandatory, Optional and Conditional qualifiers
|
............................................................................................. 30
|
cacf9eed93e6daf37d9a13b7cf85a487
|
132 102
|
11 Implementation aspects
|
..........................................................................................................................31
|
cacf9eed93e6daf37d9a13b7cf85a487
|
132 102
|
11.1 Layering of the OS applications
|
...................................................................................................................... 31
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.