R.2 Notification of Incoming IMS data
31.1113GPPRelease 18TSUniversal Subscriber Identity Module (USIM) Application Toolkit (USAT)
|
UICC |
ME |
IMS network |
|---|
|
SIP : INVITE (UICC IARI) |
|||||
|
ENVELOPE (event download : Incoming IMS data) with the IARI |
|||||
|
OPEN CHANNEL for IMS |
|||||
|
IARI, buffer size |
|||||
|
Terminal Response (Channel identifier) |
|||||
|
ENVELOPE (event download : Data Available) RECEIVE DATA |
|||||
|
Terminal Response (SIP INVITE message) |
|||||
|
SEND DATA (Immediate, Data) |
|||||
|
SIP : 200 OK |
|||||
|
Terminal Response (OK) |
|||||
|
SEND DATA (Immediate, Data) |
|
||||
|
Terminal Response (OK) |
|||||
|
ENVELOPE (event download : Data available) with the Channel identifier |
SIP : 200 OK |
||||
|
RECEIVE DATA |
|||||
|
Terminal Response (OK) |
|||||
|
CLOSE CHANNEL(Channel identifier) |
|||||
|
Terminal Response(OK) |
|||||
Figure R.2
When an incoming SIP message is received, the ME checks the IARI to see if the destination application resides on ME or on the UICC. If the IARI is associated with an active application installed on the UICC and there is not any channel to the UICC associated with that IARI, the ME informs the UICC with an ENVELOPE Incoming IMS data event command. The UICC sends an Open Channel for IMS proactive command upon reception of this ENVELOPE command. At end of the SIP dialog, the UICC closes the channel to free resources.
This flowchart occurs after a successful IMS registration is completed and the UICC is registered to the Incoming IMS data event. Otherwise the ME discards the incoming SIP INVITE message.