5 Application protocol

31.1033GPPCharacteristics of the IP Multimedia Services Identity Module (ISIM) applicationRelease 17TS

The requirements stated in the corresponding clause of TS 31.101 [3] apply to the ISIM application.

The procedures listed in clause "ISIM management procedures" are required for execution of the procedures in the subsequent clause "ISIM security related procedures". The procedures authentication procedure, IMPI request, IMPU request and SIPdomain request, which are listed in clause "ISIM security related procedures" are mandatory. If an ISIM Service table is available, the additional procedures are only executable if these services are indicated as "service available" in the ISIM Service table. However, if the procedures are implemented, it shall be in accordance with clause " ISIM security related procedures".

5.1 ISIM management procedures

5.1.1 Initialisation

5.1.1.1 ISIM application selection

If the Terminal wants to engage in IMS operation, then after UICC activation (see TS 31.101 [3]), the Terminal shall select an ISIM application, if an ISIM application is listed in the EF_DIR file, using the SELECT by DF name as defined in TS 31.101 [3].

After a successful ISIM application selection, the selected ISIM (AID) is stored on the UICC. This application is referred to as the last selected ISIM application. The last selected ISIM application shall be available on the UICC after a deactivation followed by an activation of the UICC.

If a ISIM application is selected using partial DF name, the partial DF name supplied in the command shall uniquely identify a ISIM application. Furthermore if a ISIM application is selected using a partial DF name as specified in TS 31.101 [3] indicating in the SELECT command the last occurrence the UICC shall select the ISIM application stored as the last ISIM application. If, in the SELECT command, the options first, next/previous are indicated, they have no meaning if an application has not been previously selected in the same session and shall return an appropriate error code.

5.1.1.2 ISIM initialisation

The ISIM shall not indicate any language preference. It shall use the language indicated by any other application currently active on the UICC or by default, choose a language from EF_PL at the MF level according the procedure defined in TS 31.101 [3].

If the terminal does not support the languages of EF_PL, then the terminal shall use its own internal default selection.

The Terminal then runs the user verification procedure. If the procedure is not performed successfully, the ISIM initialisation stops.

Then the Terminal performs the administrative information request.

If all these procedures have been performed successfully then the ISIM session shall start. In all other cases the ISIM session shall not start.

After the previous procedures have been completed successfully, the Terminal runs the following procedures:

– IMPI request.

– IMPU request.

– SIP Domain request.

– ISIM Service Table request. If the ISIM Service Table is not present, the terminal shall assume that no optional services are available.

– P-CSCF address request

After the ISIM initialisation has been completed successfully, the Terminal is ready for an ISIM session and shall indicate this to the ISIM by sending a particular STATUS command.

5.1.2 ISIM Session termination

NOTE 1: This procedure is not to be confused with the deactivation procedure in TS 31.101 [3].

The ISIM session is terminated by the Terminal as follows.

The Terminal shall indicate to the ISIM by sending a particular STATUS command that the termination procedure is starting.

Finally, the ME deletes all these subscriber related information elements from its memory.

NOTE 2: If the Terminal has already updated any of the subscriber related information during the ISIM session, and the value has not changed until ISIM session termination, the Terminal may omit the respective update procedure.

To actually terminate the session, the Terminal shall then use one of the mechanisms described in TS 31.101 [3].

5.1.3 ISIM application closure

After termination of the ISIM session as defined in clause 5.1.2, the ISIM application may be closed by closing the logical channels that are used to communicate with this particular ISIM application.

5.1.4 UICC presence detection

The Terminal checks for the presence of the UICC according to TS 31.101 [3] within all 30 s periods of inactivity on the UICC-Terminal interface during a IMS session. If the presence detection according to TS 31.101 [3] fails the session shall be terminated as soon as possible but at least within 5s after the presence detection has failed.

5.1.5 Administrative information request

The Terminal performs the reading procedure with EF_AD.

5.2 ISIM security related procedures

5.2.1 Authentication procedure

The Terminal selects an ISIM application and uses the AUTHENTICATE command (see clause 7.1). The response is sent to the Terminal (in case of the T=0 protocol when requested by a subsequent GET RESPONSE command).

5.2.2 IMPI request

The Terminal performs the reading procedure with EF_IMPI.

5.2.3 IMPU request

The Terminal performs the reading procedure with EF_IMPU.

5.2.4 SIP Domain request

The Terminal performs the reading procedure with EF_DOMAIN.

5.2.5 Void

5.2.6 ISIM Service Table request

Requirement: ISIM Service Table available in the ISIM

Request: The ME performs the reading procedure with EF_IST.

5.2.7 P-CSCF address request

Requirement: ISIM Service n°1 and/or ISIM Service n°5 "available".

Request: The ME performs the reading procedure with EF_P-CSCF.

5.2.8 Generic Bootstrapping architecture (Bootstrap)

Requirement: ISIM Service n°2 "available".

The Terminal uses the AUTHENTICATE command in GBA security context (Bootstrapping Mode) (see 7.1.1). The response is sent to the Terminal.

After a successful GBA_U Procedure, the Terminal shall update the B-TID field and the Key Life Time field in EF_GBABP.

5.2.9 Generic Bootstrapping architecture (NAF Derivation)

Requirement: ISIM Service n°2 "available".

The Terminal shall first read EF_GBABP. The Terminal then uses the AUTHENTICATE command in GBA security context (NAF Derivation Mode) (see 7.1.1). The response is sent to the Terminal.

5.2.10 HTTP-Digest security request

Requirement: ISIM Service n°3 "available".

This HTTP-Digest security request does not apply for 3GPP and shall not be used by a terminal using a 3GPP access network or a 3GPP Interworking WLAN.

5.2.11 NAF Key Centre Address request

Requirement: Service n°2 and service n°4 "available".

Request: The ME performs the reading procedure with EF_NAFKCA.

5.3 Subscription related procedures

5.3.1 SM-over-IP

Requirement: Service n°8 "available".

Request: the ME performs the reading procedure with EF_PSISMSC.

Update: The ME performs the updating procedure with EF_PSISMSC.

5.3.2 Communication Control for IMS by ISIM

Requirement: ISIM Service n°9 "available".

The procedures and commands for Communication Control for IMS by ISIM are the same as Communication Control for IMS by USIM defined in TS 31.111 [31]. It is mandatory for the ME to perform the procedures if it has indicated that it supports Communication Control for IMS by USIM in the TERMINAL PROFILE command.

5.3.3 UICC access to IMS

Requirement: Service n°10 "available.

Request: The terminal performs the reading procedure with EF_UICCIARI.

The procedures and command for "UICC access to IMS" are defined in TS 31.111 [31]. An ME supporting UICC access to IMS shall perform the reading procedure with EF_UICCIARI prior to sending a registration to the IMS.

5.3.4 From Preferred related procedures

Requirement: service n°17 is "available" in the ISIM Service Table.

Request: The ME performs the reading procedure with EF_{FromPreferred}. The UE then shall use the From Preferred value in the EF_{FromPreferred} as described in 3GPP TS 24.607 [34] clause 4.5.2.12.

5.3.5 IMS Configuration Data related procedures

Requirement: service n°18 is "available" in the ISIM Service Table.

Request: The ME may perform the reading procedure with EF_{IMSConfigData}. If the ME performs the reading procedure with EF_{IMSConfigData}, the UE shall use the IMS Configuration Data in the EF_{IMSConfigData} as described in 3GPP TS 24.229 [32] clause L.2.2.5.1D and 3GPP TS 24.229 [32] clause 6.1.1.

5.3.6 XCAP Configuration Data related procedures

Requirement: service n°19 is "available" in the ISIM Service Table.

Request: The ME may perform the reading procedure with EF_{XCAPConfigData} . If the ME performs the reading procedure with EF_{XCAPConfigData} , the UE shall use the EF_{XCAPConfigData} as described in TS 24.623 [40] clause 5.2.1.3 and TS 24.623 [40] clause B.2.

5.4 MCS related procedures

Requirement: ISIM Service n°15 "available".

The MCS related procedures by ISIM are the same as MCS related procedures by USIM defined in 3GPP TS 31.102 [2].

5.5 WebRTC related procedures

Requirement: ISIM Service n°20 "available".

Request: The ME may perform the reading procedure with EF_WebRTCURI.