20.1 General

09.023GPPMobile Application Part (MAP) specificationTS

The Operation and Maintenance procedures are needed for operating and maintaining the GSM PLMN network.

The following procedures exist for operation and maintenance purposes:

i) Tracing procedures;

ii) Subscriber Data Management procedures;

iii) Subscriber Identity procedures.

The following application contexts refer to complex MAP Users consisting of several processes:

– subscriberDataManagementContext;

– tracingContext.

These two application contexts need a co-ordinating process in the VLR or in the SGSN as described in the following subclauses.

20.1.1 Tracing Co-ordinator for the VLR

The MAP_OPEN indication opens the dialogue for the stand-alone tracing procedure when the application context tracingContext is received. If that service is successful, the Co-ordinator can receive the firs service primitive from the MAP_PM. Depending on the received primitive, the user process is created as follows:

– if the MAP_ACTIVATE_TRACE_MODE indication is received, the process ATM_VLR_Standalone is created;

– if the MAP_DEACTIVATE_TRACE_MODE indication is received, the process DTM_VLR_Standalone is created.

After creation of the user process the Co-ordinator relays the messages between the MAP_PM and the invoked process until a request or an indication for dialogue termination is received.

The Tracing Co-ordinator is shown in the figure 20.1/1.

Figure 20.1/1: Process Co_Tracing_VLR

20.1.2 Subscriber Data Management Co-ordinator for the VLR

The MAP_OPEN indication opens the dialogue for the stand-alone subscriber data management procedure when the application context subscriberDataManagementContex is received. If that service is successful, the Co-ordinator can receive the firs service primitive from the MAP_PM. Depending on the received primitive, the user process is created as follows:

– if the MAP_INSERT_SUBSCRIBER_DATA indication is received, the process INS_SUBS_DATA_VLR is created;

– if the MAP_DELETE_SUBSCRIBER_DATA indication is received, the process Delete_Subscriber_Data_VLR is created.

After creation of the user process the Co-ordinator relays the messages between the MAP_PM and the invoked process until a request or an indication for dialogue termination is received.

The Subscriber_Data_Management Co-ordinator is shown in the figure 20.1/2.

Figure 20.1/2: Process Co_Data_Management_VLR

20.1.3 Tracing Co-ordinator for the SGSN

The MAP_OPEN indication opens the dialogue for the stand-alone tracing procedure when the application context tracingContext is received. If that service is successful, the Co-ordinator can receive the firs service primitive from the MAP_PM. Depending on the received primitive, the user process is created as follows:

– if the MAP_ACTIVATE_TRACE_MODE indication is received, the process ATM_SGSN_Standalone is created;

– if the MAP_DEACTIVATE_TRACE_MODE indication is received, the process DTM_SGSN_Standalone is created.

After creation of the user process the Co-ordinator relays the messages between the MAP_PM and the invoked process until a request or an indication for dialogue termination is received.

The Tracing Co-ordinator for the SGSN is shown in the figure 20.1/3.

Figure 20.1/3: Process Co_Tracing_SGSN

20.1.4 Subscriber Data Management Co-ordinator for the SGSN

The MAP_OPEN indication opens the dialogue for the stand-alone subscriber data management procedure when the application context subscriberDataManagementContext is received. If that service is successful, the Co-ordinator can receive the first service primitive from the MAP_PM. Depending on the received primitive, the user process is created as follows:

– if the MAP_INSERT_SUBSCRIBER_DATA indication is received, the process INS_SUBS_DATA_SGSN is created;

– if the MAP_DELETE_SUBSCRIBER_DATA indication is received, the process Delete_Subscriber_Data_SGSN is created.

After creation of the user process the Co-ordinator relays the messages between the MAP_PM and the invoked process until a request or an indication for dialogue termination is received.

The Subscriber_Data_Management Co-ordinator is shown in the figure 20.1/4.

Figure 20.1/4: Process Co_Data_Management_SGSN