R.3 UICC originating a SIP message

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

UICC		ME		IMS network

OPEN CHANNEL for IMS 
IARI, buffer size
 Terminal Response (Channel identifier)
SEND DATA (store, Data) 
 Terminal Response (OK)
SEND DATA (Immediate, Data) 
	SIP : INVITE 
 Terminal Response (OK)
	 SIP : 200 OK
	[Messages specific to the current SIP dialog not shown]
	 SIP : BYE
 ENVELOPE (event download : Data available) with the Channel identifier
RECEIVE DATA 
 Terminal Response (OK)
SEND DATA (Immediate, Data) 
	SIP : 200 OK 
CLOSE CHANNEL(Channel identifier) 
 Terminal Response(OK)

Figure R.3

The UICC will close the channel at the end of the SIP dialog.

Annex S (normative):
3GPP PS data off and Bearer Independent Protocol

This annex applies if class "e" is supported.

The UE may support the 3GPP PS data off.

If the UE supports the 3GPP PS data off, the UE may be configured with an indication whether the Bearer Independent Protocol is a 3GPP PS data off exempt service using one or more of the following methods:

– the Bearer Independent Protocol indication of the EF_{3GPPPSDATAOFF} file described in 3GPP TS 31.102 [14];

– the 3GPP_PS_data_off/Bearer_independent_protocol node of 3GPP TS 24.368 [68].

If the UE is configured with both the BIP_exempt node of 3GPP TS 24.368 [68] and the Bearer Independent Protocol indication of the EF_{3GPPPSDATAOFF} file described in 3GPP TS 31.102 [14], then the Bearer Independent Protocol indication of the EF_{3GPPPSDATAOFF} file shall take precedence.

Annex T (informative):
Data Connection Status change event, command flow examples