22.2 Registration procedure

29.0023GPPMobile Application Part (MAP) specificationRelease 17TS

22.2.1 General

The registration procedure is used to register data related to a supplementary service in the HLR. The registration procedure is a fully transparent communication between the MS and the HLR, except that some services may be invoked as a result of the procedure, as described in the clauses below.

The registration procedure is shown in figure 22.2.1/1.

The following services may be used:

MAP_PROCESS_ACCESS_REQUEST (see clauses 8 and 25);

MAP_TRACE_SUBSCRIBER_ACTIVITY (see clauses 9 and 25);

MAP_PROVIDE_IMSI (see clauses 8 and 25);

MAP_FORWARD_NEW_TMSI (see clauses 8 and 25);

MAP_AUTHENTICATE (see clauses 8 and 25);

MAP_SET_CIPHERING_MODE (see clauses 8 and 25);

MAP_CHECK_IMEI (see clauses 8 and 25);

MAP_READY_FOR_SM (see clauses 12 and 25);

MAP_INSERT_SUBSCRIBER_DATA (see clauses 8 and 25);

The following service is certainly used:

MAP_REGISTER_SS (defined in clause 11).

1) A_CM_SERV_REQ (Note 1)

2) MAP_PROCESS_ACCESS_REQUEST (Note 2)

3) A_REGISTER_SS (Note 1)

4) MAP_REGISTER_SS_req/ind

5) MAP_REGISTER_SS_req/ind

6) MAP_REGISTER_SS_rsp/cnf

7) MAP_REGISTER_SS_rsp/cnf

8) A_REGISTER_SS ack (Note 1)

9) MAP_INSERT_SUBSCRIBER_DATA_req/ind (Note 3)

10) MAP_INSERT_SUBSCRIBER_DATA_rsp/cnf (Note 3)

NOTE 1: For details of the procedure on the radio path, see 3GPP TS 24.008 [35], 3GPP TS 24.010 [36], 3GPP TS 24.08x and 3GPP TS 24.09x. Services shown in dotted lines indicate the trigger provided by the signalling on the radio path, and the signalling triggered on the radio path.

NOTE 2: For details of the Process Access Request procedure, refer to clause 25.4 in the present document.

NOTE 3: Services printed in italics are optional.

Figure 22.2.1/1: Message flow for supplementary service registration

22.2.2 Procedure in the MSC

The A_REGISTER_SS service indication received by the MAP process in the MSC contains the SS-Code and any parameters that are related to the supplementary service.

The MAP user transfers the received information to the VLR in the MAP_REGISTER_SS request without checking the contents of the service indication. Rules for the mapping are described in 3GPP TS 29.011 [59].

The information in the MAP_REGISTER_SS confirm from the VLR is relayed to the MS in the A_REGISTER_SS response message as described in 3GPP TS 24.08x, 3GPP TS 24.08x and 3GPP TS 29.011.

For call independent SS operations, each message shall contain only a single component. Messages which contain more than one component will be stopped at the air interface (as specified in 3GPP TS 29.011 [59]).

The registration process in the MSC is shown in figure 22.2.2/1.

22.2.3 Procedure in the VLR

The MAP process invokes macros not defined in this clause; the definitions of these macros can be found as follows:

Receive_Open_Ind see clause 25.1.1;

Receive_Open_Cnf see clause 25.1.2;

Check_Confirmation see clause 25.2.2;

Process_Access_Request_VLR see clause 25.4.2.

The MAP process in the VLR transfers the information received in the MAP_REGISTER_SS indication to the HLR in the MAP_REGISTER_SS request without checking the contents. The MAP_OPEN request includes the IMSI of the subscriber as the destination reference and the VLR number as the originating reference.

If the MAP_REGISTER_SS confirm is properly formed and contains a result or a user error, the MAP process in the VLR shall transfer the information contained in this primitive to the MSC in the MAP_REGISTER_SS response.

For call independent SS operations, each message shall contain only a single component. Messages which contain more than one component will be stopped at the air interface (as specified in 3GPP TS 29.011 [59]).

The registration process in the VLR is shown in figure 22.2.3/1.

22.2.4 Procedure in the HLR

The MAP process invokes a macro and a process not defined in this clause; the definitions of the macro and process can be found as follows:

Check_Indication see clause 25.2.1;

Insert_Subs_Data_Stand_Alone_HLR see clause 25.7.3.

The supplementary service request shall be processed according to 3GPP TS 23.011 [22] and the 23.08x and 23.09x-series of technical specifications. This handling may lead to a successful result, a partially successful result or an error being returned.

For call independent SS operations, each message shall contain only a single component. Messages which contain more than one component will be stopped at the air interface (as specified in 3GPP TS 29.011 [59]):

The registration process in the HLR is shown in figure 22.2.4/1.

Figure 22.2.2/1: Process Register_SS_MSC

Figure 22.2.3/1 (sheet 1 of 2): Process Register_SS_VLR

Figure 22.2.3/1 (sheet 2 of 2): Process Register_SS_VLR

Figure 22.2.4/1: Process Register_SS_HLR