22.1 Functional supplementary service processes

09.023GPPMobile Application Part (MAP) specificationTS

22.1.1 Functional supplementary service process co-ordinator for MSC

Upon receipt of a CM-Service request with CM-service type = SS, the MSC initiates the process access request procedure towards the VLR as described in clause 25 of the present document.

Once a CM connection is established, the MSC can handle supplementary service indications from the MS. Table 22.1/1 shows the co-ordinating process’ reaction on receipt of specific SS service indications on the air interface. After the relevant process is invoked, the received air interface service indication is sent to that process. The creation of service requests on the basis of air interface messages is described in GSM 09.11.

Table 22.1/1: Relationship between received service indication and invoked process in the MSC

Service indication received

Process invoked

A_REGISTER_SS_ind

REGISTER_SS_MSC

A_ERASE_SS_ind

ERASE_SS_MSC

A_ACTIVATE_SS_ind

ACTIVATE_SS_MSC

A_DEACTIVATE_SS_ind

DEACTIVATE_SS_MSC

A_INTERROGATE_SS_ind

INTERROGATE_SS_MSC

A_REGISTER_PASSWORD

REGISTER_PASSWORD_MSC

Figure 22.1/1 shows the co-ordinating process in the MSC.

Figure 22.1/1: Process SS_Coordinator_MSC

22.1.2 Functional supplementary service process co-ordinator for VLR

Any functional SS process in the VLR starts by the VLR receiving the MAP_PROCESS_ACCESS_REQUEST indication. The VLR then acts as described in clause 25 of the present document.

If the Process Access Request was successful, the VLR can handle supplementary service indications from the MSC. Table 22.1/2 shows the co-ordinating process’ reaction on receipt of specific SS service indications from the MSC. After the relevant process is invoked, the received service indication is sent to that process, and the co-ordinating process terminates.

Table 22.1/2: Relationship between received service indication and invoked process in the VLR

Service indication received

Process invoked

MAP_REGISTER_SS_ind

REGISTER_SS_VLR

MAP_ERASE_SS_ind

ERASE_SS_VLR

MAP_ACTIVATE_SS_ind

ACTIVATE_SS_VLR

MAP_DEACTIVATE_SS_ind

DEACTIVATE_SS_VLR

MAP_INTERROGATE_SS_ind

INTERROGATE_SS_VLR

MAP_REGISTER_PASSWORD

REGISTER_PASSWORD_VLR

Figure 22.1/2 shows the co-ordinating process in the VLR.

Figure 22.1/2 (sheet 1 of 2): Process SS_Coordinator_VLR

Figure 22.1/2 (sheet 2 of 2): Process SS_Coordinator_VLR

22.1.3 Functional supplementary service process co-ordinator for HLR

Any functional SS process in the HLR starts by the HLR receiving a MAP-OPEN service indication. If that service is successful, the HLR can handle supplementary service indications from the VLR. Table 22.1/3 shows the co-ordinating process’ reaction on receipt of specific SS service indications from the VLR. After the relevant process is invoked, the received service indication is sent to that process, and the co-ordinating process terminates.

Table 22.1/3: Relationship between received service indication and invoked process in the HLR.

Service indication received

Process invoked

MAP_REGISTER_SS_ind

REGISTER_SS_HLR

MAP_ERASE_SS_ind

ERASE_SS_HLR

MAP_ACTIVATE_SS_ind

ACTIVATE_SS_HLR

MAP_DEACTIVATE_SS_ind

DEACTIVATE_SS_HLR

MAP_INTERROGATE_SS_ind

INTERROGATE_SS_HLR

MAP_REGISTER_PASSWORD

REGISTER_PASSWORD_HLR

Figure 22.1/3 shows the co-ordinating process in the HLR.

Figure 22.1/3 (sheet 1 of 2): Process SS_Coordinator_HLR

Figure 22.1/3 (sheet 2 of 2): Process SS_Coordinator_HLR

22.1.4 Call completion supplementary service process co-ordinator for HLR

The MAP co-ordinating process in the HLR to handle a dialogue opened with the callCompletion application context is shown in figure 22.1/4. The MAP process invokes a macro not defined in this subclause; the definition of this macro can be found as follows:

Receive_Open_Ind see subclause 25.1.1.

Any call completion SS process in the HLR starts by the HLR receiving a MAP-OPEN service indication. If that service is successful, the HLR can handle call completion supplementary service indications from the VLR. Table 22.1/4 shows the co-ordinating process’ reaction on receipt of specific call completion SS service indications from the VLR. After the relevant process is invoked, the received service indication is sent to that process.

Table 22.1/4: Relationship between received service indication and invoked process in the HLR.

Service indication received

Process invoked

MAP_REGISTER_CC_ENTRY_ind

REGISTER_CC_ENTRY_HLR

MAP_ERASE_CC_ENTRY_ind

ERASE_CC_ENTRY_HLR

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 Call_Completion Co-ordinator is shown in figure 22.1/4.

Figure 22.1/4: Process_CC_Coord_HLR