9 Operation and maintenance services
29.0023GPPMobile Application Part (MAP) specificationRelease 17TS
9.1 Subscriber tracing services
9.1.1 MAP-ACTIVATE-TRACE-MODE service
9.1.1.1 Definition
This service is used between the HLR and the VLR to activate subscriber tracing in the VLR.
Also this service is used between the HLR and the SGSN to activate subscriber tracing in the SGSN.
The MAP-ACTIVATE-TRACE-MODE service is a confirmed service using the primitives from table 9.1/1.
9.1.1.2 Service primitives
Table 9.1/1: MAP-ACTIVATE-TRACE-MODE
|
Parameter name |
Request |
Indication |
Response |
Confirm |
|
Invoke id |
M |
M(=) |
M(=) |
M(=) |
|
IMSI |
C |
C(=) |
||
|
Trace reference |
M |
M(=) |
||
|
Trace type |
M |
M(=) |
||
|
Trace reference 2 |
C |
C(=) |
||
|
Trace depth list |
C |
C(=) |
||
|
Trace NE type list |
C |
C(=) |
||
|
Trace interface list |
C |
C(=) |
||
|
Trace event list |
C |
C(=) |
||
|
Trace support indicator |
C |
C(=) |
||
|
OMC Id |
U |
C(=) |
||
|
MDT-Configuration |
C |
C(=) |
||
|
User error |
C |
C(=) |
||
|
Provider error |
O |
9.1.1.3 Parameter use
Invoke id
See definition in clause 7.6.1.
IMSI
See definition in clause 7.6.2. The IMSI is a mandatory parameter in a stand-alone operation.
Trace reference
See definition in clause 7.6.10. This parameter contains trace reference for GSM only tracing request.
Trace type
See definition in clause 7.6.10. This parameter contains trace type for GSM only tracing request.
OMC Id
See definition in clause 7.6.2. The use of this parameter is an operator option.
Trace reference 2
See definition in clause 7.6.10. This parameter shall be used for UMTS trace activation.
Trace depth list
See definition in clause 7.6.10. This parameter shall be used for UMTS trace activation.
Trace NE type list
See definition in clause 7.6.10. This parameter shall be used for UMTS trace activation.
Trace interface list
See definition in clause 7.6.10. This parameter shall be used for UMTS trace activation.
Trace event list
See definition in clause 7.6.10. This parameter shall be used for UMTS trace activation.
Trace support indicator
See definition in clause 7.6.10. This parameter shall be used for UMTS trace activation.
MDT-Configuration
See definition in clause 7.6.10.
User error
The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault:
– Unidentified Subscriber;
– Facility Not Supported;
– Tracing Buffer Full;
– System Failure;
– Unexpected Data Value;
– Data missing.
Provider error
For definition of provider errors see clause 7.6.1.
9.1.2 MAP-DEACTIVATE-TRACE-MODE service
9.1.2.1 Definition
This service is used between the VLR and the HLR for deactivating subscriber tracing in the VLR.
Also this service is used between the SGSN and the HLR for deactivating subscriber tracing in the SGSN.
The MAP-DEACTIVATE-TRACE-MODE service is a confirmed service using the primitives from table 9.1/2.
9.1.2.2 Service primitives
Table 9.1/2: MAP-DEACTIVATE-TRACE-MODE
|
Parameter name |
Request |
Indication |
Response |
Confirm |
|
Invoke id |
M |
M(=) |
M(=) |
M(=) |
|
IMSI |
C |
C(=) |
||
|
Trace reference |
M |
M(=) |
||
|
Trace reference 2 |
C |
C(=) |
||
|
User error |
C |
C(=) |
||
|
Provider error |
O |
9.1.2.3 Parameter use
Invoke id
See definition in clause 7.6.1.
IMSI
See definition in clause 7.6.2. The IMSI is a mandatory parameter in a stand-alone operation.
Trace reference
See definition in clause 7.6.10.
Trace reference 2
See definition in clause 7.6.10. This parameter shall be used for UMTS trace activation.
User error
The following errors defined in clause 7.6.1 may be used, depending on the nature of the fault:
– Unidentified Subscriber;
– Facility Not Supported;
– System Failure;
– Unexpected Data Value;
– Data missing.
Provider error
For definition of provider errors see clause 7.6.1.
9.1.3 MAP-TRACE-SUBSCRIBER-ACTIVITY service
9.1.3.1 Definition
This service is used between the VLR and the MSC to activate the subscriber tracing in the MSC.
The MAP-TRACE-SUBSCRIBER-ACTIVITY service is a non-confirmed service using the primitives from table 9.1/3.
9.1.3.2 Service primitives
Table 9.1/3: MAP-TRACE-SUBSCRIBER-ACTIVITY
|
Parameter name |
Request |
Indication |
|
Invoke id |
M |
M(=) |
|
IMSI |
C |
C(=) |
|
Trace reference |
M |
M(=) |
|
Trace type |
M |
M(=) |
|
OMC Id |
U |
C(=) |
9.1.3.3 Parameter use
Invoke id
See definition in clause 7.6.1.
IMSI
See definition in clause 7.6.2. The controlling MSC shall provide either the IMSI or the IMEI to the servicing MSC.
Trace reference
See definition in clause 7.6.10.
Trace type
See definition in clause 7.6.10.
OMC Id
See definition in clause 7.6.2. The use of this parameter is an operator option.
9.2 Other operation and maintenance services
9.2.1 MAP-SEND-IMSI service
9.2.1.1 Definition
This service is used by a VLR in order to fetch the IMSI of a subscriber in case of some Operation & Maintenance procedure where subscriber data are needed in the Visited PLMN and MSISDN is the only subscriber’s identity known.
It is a confirmed service and consists of the primitives shown in table 9.2/1.
9.2.1.2 Service primitives
Table 9.2/1: MAP-SEND-IMSI
|
Parameter name |
Request |
Indication |
Response |
Confirm |
|
Invoke Id |
M |
M(=) |
M(=) |
M(=) |
|
MSISDN |
M |
M(=) |
||
|
IMSI |
C |
C(=) |
||
|
User error |
C |
C(=) |
||
|
Provider error |
O |
9.2.1.3 Parameter use
All parameters are described in clause 7.6. The following clarifications are applicable.
User error
Only one of the following values is applicable:
– Unknown subscriber;
– Unexpected data value;
– Data missing.