22.4 Activation procedure

09.023GPPMobile Application Part (MAP) specificationTS

22.4.1 General

The activation procedure is used to activate a supplementary service in the HLR. The activation 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 subclauses below.

The activation procedure is shown in figure 22.4.1/1.

The following services may be used:

MAP_PROCESS_ACCESS_REQUEST (defined in clauses 8 and 25);

MAP_TRACE_SUBSCRIBER_ACTIVITY (defined in clauses 9 and 25);

MAP_PROVIDE_IMSI (defined in clauses 8 and 25);

MAP_FORWARD_NEW_TMSI (defined in clauses 8 and 25);

MAP_AUTHENTICATE (defined in clauses 8 and 25);

MAP_SET_CIPHERING_MODE (defined in clauses 8 and 25);

MAP_CHECK_IMEI (defined in clauses 8 and 25);

MAP_READY_FOR_SM (defined in clauses 12 and 25);

MAP_GET_PASSWORD (defined in clause 11);

MAP_INSERT_SUBSCRIBER_DATA (defined in clauses 8 and 25);

MAP_ACTIVATE_SS (defined in clause 11).

+—-+ +—-+ +—-+ B +—-+ D +—-+
ª MS ª-ªEIR ª—–ªMSC ª——+——-ªVLR ª—-+——ªHLR ª
+—-+ +—-+ +—-+ +—-+ +—-+
ª ª ª ªß
ª A_CM_SERV_REQ ª ª ªß
ª—————->ªMAP_PROCESS_ACC_REQ ª ªß
ª (note 1) ª——————->… ªß
ª ª (note 2) ª ªß
ª ª ª ªß
ª A_ACTIVATE_SS ª MAP_ACTIVATE_SS ªMAP_ACTIVATE_SS ªß
ª—————->ª——————->ª—————->ªß
ª ª ª ªß
ª A_GET_PW ª MAP_GET_PW ª MAP_GET_PW ªß
ª<————— ª<——————-ª<—————-ªß
ª ª ª ªß
ª A_GET_PW ack ª MAP_GET_PW ack ªMAP_GET_PW ack ªß
ª—————->ª——————->ª—————->ªß
ª ª ª ªß
ªA_ACTIVATE_SS ackª MAP_ACTIVATE_SS ackªMAP_ACTIV_SS ack ªß
ª<—————-ª<——————-ª<—————-ªß
ª ª ªMAP_INS_SUBS_DATAªß
ª ª …<—————-ªß
ª ª ª (note 3) ªß

NOTE 1: For details of the procedure on the radio path, see GSM 04.08, 04.10, 04.8x and 04.9x. 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 on the Process Access Request procedure, please refer to clause 25 of this document.

NOTE 3: Services printed in italics are optional.

Figure 22.4.1/1: Interfaces and services for supplementary service activation

22.4.2 Procedures in the MSC

The A_ACTIVATE_SS service indication received by the MAP user in the MSC contains the SS-Code and any parameters related to the supplementary service.

The MSC transfers the received information to the VLR in the MAP_ACTIVATE_SS request without checking the contents of the service indication. Rules for the mapping are described in GSM 09.11.

The MAP user may subsequently receive the MAP_GET_PASSWORD indication from the VLR. Upon receipt of this indication, the MSC sends the A_GET_PASSWORD message towards the MS and then awaits the response from the MS. When an A_GET_PASSWORD confirm message is received from the MS, the MSC initiates the MAP_GET_PASSWORD response towards the VLR without checking further the contents of the indication. Also see GSM 09.11.

The MSC will receive a MAP_ACTIVATE_SS confirm from the VLR. The outcome of the procedure is reported to the MS in the A_ACTIVATE_SS response message, see GSM 04.8x, 04.9x and 09.11. Finally the SS connection is released.

For call independent SS operations, each message shall only contain a single component. Messages which contain more than one component will be stopped at the air interface (as specified in GSM 09.11).

The handling of MAP_P_ABORT, MAP_U_ABORT, MAP_NOTICE and unexpected MAP_CLOSE or A_CM_RELEASE in this procedure is identical to the handling in the Registration procedure in the MSC, see subclause 22.2.2 of the present document.

The activation procedure in the MSC is shown in figure 22.4.2/1.

Figure 22.4.2/1: Procedure Activate_SS_MSC

22.4.3 Procedures in the VLR

Supplementary service activation

When receiving the MAP_ACTIVATE_SS indication, the MAP user in the VLR transfers the information to the HLR in the MAP_ACTIVATE_SS request without checking the contents of the service indication.

The VLR may then receive the MAP_GET_PASSWORD indication. This information is transferred to the MSC in the MAP_GET_PASSWORD request. If a MAP_GET_PASSWORD confirm primitive is received from the MSC, the VLR initiates the MAP_GET_PASSWORD response towards the HLR.

The VLR will receive the MAP_ACTIVATE_SS confirm from the HLR. The MAP user in the VLR shall transfer the information contained in this primitive to the MSC in the MAP_ACTIVATE_SS response without checking its contents.

For call independent SS operations, each message shall only contain a single component. Messages which contain more than one component will be stopped at the air interface (as specified in GSM 09.11).

Error handling

The handling of MAP_P_ABORT, MAP_U_ABORT, MAP_NOTICE and unexpected MAP_CLOSE in this procedure is identical to the handling in the Registration procedure in the VLR, see subclause 22.2.3 of the present document.

The activation procedure in the VLR is shown in figure 22.4.3/1.

Figure 22.4.3/1 (sheet 1 of 2): Procedure Activate_SS_VLR

Figure 22.4.3/1 (sheet 2 of 2): Procedure SS_Activate_VLR

22.4.4 Procedures in the HLR

The procedure in the HLR is initiated when it receives a MAP_ACTIVATE_SS indication.

The HLR acts as follows:

– if the operator has barred the subscriber from access to supplementary services, the Call Barred error should be returned to the VLR. The parameter "operatorBarring" shall be included with the error.

The supplementary service request shall then be processed according to GSM 03.11 and the 03.8x and 03.9x-series of technical specifications. This handling may lead to either a successful result, a partially successful result, or an error being returned.

During the handling of activation, the get password procedure may be initiated (as specified in GSM 03.11). This will involve the sending of a MAP_GET_PASSWORD request to the VLR.

For call independent SS operations, each message shall only contain a single component. Messages which contain more than one component will be stopped at the air interface (as specified in GSM 09.11):

– if the VLR is to be updated after the supplementary service activation, the MAP_INSERT_SUBS_DATA_HLR process is initiated;

– handling of receipt of MAP_P_ABORT, MAP_U_ABORT or MAP_CLOSE indications from the VLR is identical to their handling in the registration procedure, see subclause 22.2.4 above.

The activation procedure in the HLR is shown in figure 22.4.4/1.

Figure 22.4.4/1 (sheet 1 of 2): Procedure Activate_SS_HLR

Figure 22.4.4/1 (sheet 2 of 2): Procedure Activate_SS_HLR