32.3243GPPCommon Management Information Protocol (CMIP) Solution Set (SS)Release 6Telecommunication managementTest management Integration Reference Point (IRP)TS

4.1 Architectural aspects

The architecture of the Test Management IRP CMIP Solution Set is based on the test management function defined in ITU-T Recommendation X.745 [10].

4.2 Mapping

The semantics of the Test Management IRP are defined in 3GPP TS 32.322 [8]. The definitions of the management information defined there are independent of any implementation technology and protocol. This clause maps these protocol independent definitions onto their equivalents of the CMIP SS of the Test Management IRP.

4.2.1 Mapping of Information Object Classes (IOCs)

Table 1 maps the IOCs defined in 3GPP TS 32.322 [8] to the corresponding Managed Object Classes (MOCs) defined in this CMIP SS. The MOCs are qualified either as Mandatory (M) or Optional (O).

Table 1: Mapping of IOCs

4.2.2 Mapping of IOC attributes

Table 2 maps the attributes defined in 3GPP TS 32.322 [8] to the corresponding attributes of the CMIP SS.
Only attributes, that are qualified as public in the IS, require a corresponding attribute in the CMIP SS.

Table 2: Mapping of attributes

4.2.3 Mapping of operations

Table 3 and table 4 map the operations defined in 3GPP TS 32.322 [8] and 3GPP TS 32.312 [6] to corresponding GDMO actions and CMISE services. The operations are qualified either as Mandatory (M) or Optional (O).

The CMISE services are defined in ITU-T Recommendation X.710 [9].

Table 3: Mapping of operations of the Test Management IRP: IS

Table 4: Mapping of operations inherited from the Generic IRP Management: IS

4.2.4 Mapping of Operation Parameters

The tables in the following clauses list the parameters of each operation defined in 3GPP TS 32.322 [8] and their equivalents in the CMIP SS.

4.2.4.1 Parameter Mapping of the Operation initiateTest

The operation initiateTest is mapped to the GDMO action testRequestControlledAction defined in ITU-T Recommendation X.745 [10]. This action shall be implemented using the CMISE M-ACTION service.

All input parameters are mapped to the M-ACTION request parameter ‘Action information’. The syntax and semantics of this parameter is specified in ITU-T Recommendation X.745 [10] for the testRequestControlledAction by the ASN.1 definition TestRequestControlledInfo.

If all tests specified by the IS parameter toBeInitiatedTests were successfully instantiated, the output parameter response is mapped to the M-ACTION response parameter ‘Action reply’, which is specified in ITU-T Recommendation X.745 [10] for the testRequestControlledAction by the ASN.1 definition TestRequestControlledResponse.

If at least one test failed to be instantiated, the output parameter response is mapped the M-ACTION parameter ‘Errors’. The errors defined in ITU-T Recommendation X.745 [10] for testRequestControlledAction are noSuchMORT, mORTNotAvailable, mistypedTestCategoryInformation, noSuchAssociatedObject, associatedObjectNotAvailable, independentTestInvocationError.

Table 5: Parameter mapping of the operation initiateTest

4.2.4.2 Parameter Mapping of the Operation terminateTest

The operation terminateTest is mapped to the GDMO action testTerminateAction defined in ITU-T Recommendation X.745 [10]. This action shall be implemented using the CMISE M-ACTION service.

All input parameters are mapped to the M-ACTION request parameter ‘Action information’. This parameter is specified for the testTerminateAction in ITU-T Recommendation X.745 [10] by the ASN.1 definition TestTerminateInfo, which is the CMIP SS equivalent of the IS parameter toBeTerminatedTests.

If all tests specified by the IS parameter toBeTerminatedTests are successfully terminated, the output parameter response is mapped to the M-ACTION response parameter ‘Action reply’, which is specified in ITU-T Recommendation X.745 [10] for the testTerminateAction by the ASN.1 definition TestTerminateResult.

If at least one test failed to be terminated, the output parameter response is mapped the M-ACTION parameter ‘Errors’. The errors defined in ITU-T Recommendation X.745 [10] for testTerminateAction are invalidTestOperation, noSuchTestInvocationId, noSuchTestSessionId, testTerminateError.

Table 6: Parameter mapping of the operation terminateTest

4.2.4.3 Parameter Mapping of the Operation monitorTest

The TO attributes reflecting the status of the test can be retrieved by the manager using the CMISE M-GET service. The TO to be monitored is specified by the M-GET request parameter ‘Base object instance’ and the attributes to be retrieved by the M-GET request parameter ‘Attribute identifier list’.

The attribute values are returned in the M-GET response parameter ‘Attribute list’.

Table 7: Parameter mapping of the operation monitorTest

4.2.5 Mapping of Notifications

The notification notifyTestResults is mapped to the GDMO notification testResultNotification defined in ITU-T Recommendation X.745 [10]. This notification shall be implemented using the CMISE M-EVENT-REPORT service.

Table 8: Mapping of notifications of the Test Management IRP IS

4.2.6 Mapping of Notification Parameters

The tables in the following subclauses show the parameters of each notification defined in 3GPP TS 32.322 [8] and their equivalents in the CMIP Solution Set.

4.2.6.1 Parameter Mapping of the Notification notifyTestResults

Except for objectClass, objectInstance, eventTime and notificationType all parameters defined in the IS are mapped to the M-EVENT-REPORT parameter ‘Event information’. The syntax and semantics of this structured parameter are defined for the notification testResultNotification in ITU-T Recommendation X.745 [10] by the ASN.1 definition TestResultInfo.

Table 9: Parameter mapping of the notification notifyTestResults