5 Profile download

31.1113GPPRelease 18TSUniversal Subscriber Identity Module (USIM) Application Toolkit (USAT)

5.1 Procedure

The profile download instruction is sent by the ME to the UICC as part of the UICC initialization procedure. The UICC initialization procedure is specified in TS 31.101 [13]. If class "s" is supported, the profile download instruction is sent also every time the TE accessing USAT functionalities over the AT interface is connected or disconnected or changes its profile. If the terminal supports class "s" the profile download instruction shall combine capabilities supported by the MT and the TE according to Annex Q.

If the UICC indicates the support of "Additional TERMINAL PROFILE after UICC activation" in its USIM Service Table, the ME shall handle the profile download procedure as specified in ETSI TS 102 223 [32] clause 5.1.

If the UICC does not indicate the support of "Additional TERMINAL PROFILE after UICC activation" in its USIM Service Table, the profile download instruction shall only be sent by the ME to the UICC as part of the UICC initialization procedure. However, if a USIM initialisation procedure is performed due to a refresh proactive command, the USIM initialisation procedure may also include a profile download.

The profile(s) sent by the ME shall state the facilities relevant to USAT that are supported by the ME.

5.2 Structure and coding of TERMINAL PROFILE

Direction: ME to UICC.

The command header is specified in TS 31.101 [13].

Command parameters/data:

Description

Clause

M/O/C

Length

Profile

–

M

lgth

– Profile:

Contents:

– The list of USAT facilities that are supported by the ME.

Coding:

– 1 bit is used to code each facility:

– bit = 1: facility supported by ME.

– bit = 0: facility not supported by ME.

NOTE: several bits may need to be set to 1 for the support of the same facility. This is because of backward compatibility with SAT: several options existed in SAT for a given facility, and they are mandatory in USAT when this facility is supported.

First byte (Download):

b8

b7

b6

b5

b4

b3

b2

b1

See TS 102 223 [32] clause 5.2

SMS-PP data download

Cell Broadcast data download

See TS 102 223 [32] clause 5.2

Bit = 1 if SMS-PP data download is supported

See TS 102 223 [32] clause 5.2

Bit = 1 if Call Control by USIM is supported

Bit = 1 if Call Control by USIM is supported

Second byte (Other):

b8

b7

b6

b5

b4

b3

b2

b1

See TS 102 223 [32] clause 5.2

Call Control by USIM

Bit = 1 if Call Control by USIM is supported

MO short message control by USIM

Bit = 1 if Call Control by USIM is supported

See TS 102 223 [32] clause 5.2

See TS 102 223 [32] clause 5.2

See TS 102 223 [32] clause 5.2

Third byte (Proactive UICC):

– See ETSI TS 102 223 [32] clause 5.2.

Fourth byte (Proactive UICC):

b8

b7

b6

b5

b4

b3

b2

b1

See TS 102 223 [32] clause 5.2

Proactive UICC: SEND SHORT MESSAGE

Proactive UICC: SEND SS

Proactive UICC: SEND USSD

See TS 102 223 [32] clause 5.2

See TS 102 223 [32] clause 5.2

See TS 102 223 [32] clause 5.2

Proactive UICC: PROVIDE LOCAL INFORMATION (NMR) – in 3GPP terms, this indicates support for GERAN

Fifth byte (Event driven information):

– See ETSI TS 102 223 [32] clause 5.2.

Sixth byte (Event driven information extensions):

– See ETSI TS 102 223 [32] clause 5.2.

Seventh byte (Multiple card proactive commands) for class "a":

– See ETSI TS 102 223 [32] clause 5.2.

Eighth byte (Proactive UICC):

b8

b7

b6

b5

b4

b3

b2

b1

See TS 102 223 [32] clause 5.2

See TS 102 223 [32] clause 5.2

See TS 102 223 [32] clause 5.2

See TS 102 223 [32] clause 5.2

See TS 102 223 [32] clause 5.2

See TS 102 223 [32] clause 5.2

See TS 102 223 [32] clause 5.2

Bit = 1 if Call Control by USIM is supported

Ninth byte:

b8

b7

b6

b5

b4

b3

b2

b1

See TS 102 223 [32] clause 5.2

See TS 102 223 [32] clause 5.2

See TS 102 223 [32] clause 5.2

See TS 102 223 [32] clause 5.2

Proactive UICC: PROVIDE LOCAL INFORMATION (Timing Advance)

See TS 102 223 [32] clause 5.2

See TS 102 223 [32] clause 5.2

See TS 102 223 [32] clause 5.2

Tenth byte (Soft keys support) for class "d":

– See ETSI TS 102 223 [32] clause 5.2.

Eleventh byte: (Soft keys information):

– See ETSI TS 102 223 [32] clause 5.2.

Twelfth byte (Bearer Independent protocol proactive commands) for class "e":

– See ETSI TS 102 223 [32] clause 5.2.

Thirteenth byte (Bearer Independent protocol supported bearers) for class "e":

– See ETSI TS 102 223 [32] clause 5.2.

Fourteenth byte: (Screen height):

– See ETSI TS 102 223 [32] clause 5.2.

Fifteenth byte: (Screen width):

– See ETSI TS 102 223 [32] clause 5.2.

Sixteenth byte: (Screen effects):

– See ETSI TS 102 223 [32] clause 5.2.

Seventeenth byte (Bearer independent protocol supported transport interface/bearers) for class "e":

b8

b7

b6

b5

b4

b3

b2

b1

See TS 102 223 [32] clause 5.2

E-UTRAN

HSDPA

Eighteenth byte:

b8

b7

b6

b5

b4

b3

b2

b1

See TS 102 223 [32] clause 5.2

CALL CONTROL on GPRS

See TS 102 223 [32] clause 5.2

Nineteenth byte: (reserved for TIA/EIA-136 facilities):

– See ETSI TS 102 223 [32] clause 5.2.

Twentieth byte: (reserved for TIA/EIA/IS-820 facilities):

– See ETSI TS 102 223 [32] clause 5.2.

Twenty-first byte (Extended Launch Browser Capability) for class "c":

– See ETSI TS 102 223 [32] clause 5.2.

Twenty second byte:

b8

b7

b6

b5

b4

b3

b2

b1

Support of UTRAN PS with extended parameters

See TS 102 223 [32] clause 5.2

Toolkit-initiated GBA

See TS 102 223 [32] clause 5.2

See TS 102 223 [32] clause 5.2

See TS 102 223 [32] clause 5.2

Twenty third byte:

b8

b7

b6

b5

b4

b3

b2

b1

See TS 102 223 [32] clause 5.2

Geographical Location Reporting (if class "n" is supported)

See TS 102 223 [32] clause 5.2

Proactive UICC: PROVIDE LOCAL INFORMATION (NMR(UTRAN/E-UTRAN))

USSD Data download and application mode (if class "p" is supported)

Twenty fourth byte for class "i":

– See ETSI TS 102 223 [32] clause 5.2.

Twenty-fifth byte (Event driven information extensions):

b8

b7

b6

b5

b4

b3

b2

b1

See TS 102 223 [32] clause 5.2

Event: I-WLAN Access status (if class "e" is supported)

Event: Network Rejection for GERAN/UTRAN

Reserved by ETSI SCP: HCI connectivity event (i.e. class "m" is supported)

Event: Network Rejection for E-UTRAN/Satellite E-UTRAN

See TS 102 223 [32] clause 5.2

Twenty-sixth byte (Event driven information extensions):

b8

b7

b6

b5

b4

b3

b2

b1

Event : CSG Cell Selection (if class "q" is supported)

Reserved by ETSI SCP: Contactless state request (if class "r" is supported

See TS 102 223 [32] clause 5.2

Twenty-seventh byte (Event driven information extensions):

– See ETSI TS 102 223 [32] clause 5.2.

Twenty-eighth byte (Text attributes):

– See ETSI TS 102 223 [32] clause 5.2.

Twenty-ninth byte (Text attributes):

– See ETSI TS 102 223 [32] clause 5.2.

Thirtieth byte:

b8

b7

b6

b5

b4

b3

b2

b1

I-WLAN bearer support (if class "e" is supported)

Proactive UICC: PROVIDE LOCAL INFORMATION (WSID of the current I-WLAN connection)

TERMINAL APPLICATIONS (i.e. class "k" is supported)

"Steering of Roaming" REFRESH support

Reserved by ETSI SCP: Proactive UICC command ACTIVATE (i.e class "l" is supported)

Proactive UICC: Geographical Location Request (if class "n" is supported)

See TS 102 223 [32] clause 5.2

"Steering of Roaming for I-WLAN" REFRESH support

Thirty-first byte:

b8

b7

b6

b5

b4

b3

b2

b1

See TS 102 223 [32] clause 5.2

Support of CSG cell discovery (if class "q" is supported)

See TS 102 223 [32] clause 5.2

Communication Control for IMS

See TS 102 223 [32] clause 5.2

Support for Incoming IMS Data event (if classes "e" and "t" are supported)

Support for IMS Registration event (if classes "e" and "t" are supported)

Reserved by ETSI SCP: Proactive UICC: Profile Container, Envelope Container, COMMAND CONTAINER and ENCAPSULATED SESSION CONTROL (if class "u" is supported)

Thirty-second byte:

b8

b7

b6

b5

b4

b3

b2

b1

IMS support (if class "e" and "t" are supported)

Support of PROVIDE LOCAL INFORMATION, H(e)NB IP address (if class "v" is supported)

support of PROVIDE LOCAL INFORMATION, H(e)NB surrounding macrocells (if class "w" is supported)

See TS 102 223 [32] clause 5.2

See TS 102 223 [32] clause 5.2

See TS 102 223 [32] clause 5.2

See TS 102 223 [32] clause 5.2

See TS 102 223 [32] clause 5.2

…

Thirty-third byte:

b8

b7

b6

b5

b4

b3

b2

b1

See TS 102 223 [32] clause 5.2

See TS 102 223 [32] clause 5.2

See TS 102 223 [32] clause 5.2

ProSe usage information reporting (used only if class "e" is supported)

See TS 102 223 [32] clause 5.2

Event: WLAN Access status (if class "e" is supported)

WLAN bearer support (if class "e" is supported)

Proactive UICC: PROVIDE LOCAL INFORMATION (WLAN identifier of the current WLAN connection)

Thirty-fourth byte:

b8

b7

b6

b5

b4

b3

b2

b1

URI support for SEND SHORT MESSAGE

IMS URI supported for SET UP CALL (if class "ae" is supported)

Media Type "Voice" supported for SET UP CALL and Call Control by USIM

Media Type "Video" supported for SET UP CALL and Call Control by USIM

Proactive UICC: PROVIDE LOCAL INFORMATION (E-UTRAN Timing Advance Information)

See TS 102 223 [32] clause 5.2

Extended Rejection Cause Code in Event: Network Rejection for E-UTRAN

See TS 102 223 [32] clause 5.2

Thirty-fifth byte:

b8

b7

b6

b5

b4

b3

b2

b1

See TS 102 223 [32] clause 5.2

Data Connection Status Change Event support – PDP Connection

Data Connection Status Change Event support – PDN Connection

See TS 102 223 [32] clause 5.2

See TS 102 223 [32] clause 5.2

See TS 102 223 [32] clause 5.2

See TS 102 223 [32] clause 5.2

See TS 102 223 [32] clause 5.2

Thirty sixth byte:

b8

b7

b6

b5

b4

b3

b2

b1

Data Connection Status Change Event support – PDU Connection

Event: Network Rejection for NG-RAN

Non-IP Data Delivery support (if class "e" and class "ai" are supported)

Support of PROVIDE LOCAL INFORMATION, Slice information

REFRESH "Steering of Roaming” SOR-CMCI parameter support

Event: Network Rejection for Satellite NG-RAN

Support of CAG feature (if class "ag" is supported)

Event: Slices Status Change (if class "ah" is supported)

Thirty seventh byte:

b8

b7

b6

b5

b4

b3

b2

b1

Reserved for 3GPP (for future usage)

Thirty eighth byte:

b8

b7

b6

b5

b4

b3

b2

b1

Reserved for 3GPP (for future usage)

Thirty ninth byte:

b8

b7

b6

b5

b4

b3

b2

b1

Proactive UICC: PROVIDE LOCAL INFORMATION (NG‑RAN/Satellite NG-RAN Timing Advance Information)

Reserved for 3GPP (for future usage)

Subsequent bytes:

– See ETSI TS 102 223 [32] clause 5.2.

Response parameters/data:

– None.

5.3 Definition of display parameters in Profile download

See ETSI TS 102 223 [32] clause 5.3.