Content for  TS 31.111  Word version:  19.2.0

If the (I-)WLAN Access Status event is part of the current event list (as set up by the last SET UP EVENT LIST command, see clause 6.4.16), then, when the terminal detects a change in its current I-WLAN access or WLAN access respectively the terminal shall inform the UICC that this has occurred, by using the ENVELOPE (EVENT DOWNLOAD - (I-)WLAN Access Status) command as defined in clause 7.5.1.2.

Direction: The command header is specified in TS 31.101. Command parameters/data.

Event list: the Event list data object shall contain only one event (value part of length 1 byte), and terminal shall set the event to: Device identities: the terminal shall set the device identities to: (I-)WLAN Access Status: this data object shall contain the (I-)WLAN Access status of the terminal. Response parameters/data: None for this type of ENVELOPE command.

If the MT call event is part of the current event list (as set up by the last SET UP EVENT LIST command, see clause 6.4.16), then when the ME receives an incoming call setup message, the ME shall inform the UICC that this has occurred, by using the ENVELOPE (EVENT DOWNLOAD - MT call) command as defined in clause 7.5.1A.2.

Direction: The command header is specified in TS 31.101. Command parameters/data.

Event list: the event list object shall contain only one event (value part of length 1 byte), and ME shall set the event to:

• MT call.

Device identities: the ME shall set the device identities to:

• source: network;
• destination: UICC.

Transaction identifier: the transaction identifier data object shall contain one transaction identifier, and this shall be the Transaction Identifier as defined in clause 8.28. Address: the address data object holds the Calling Party number received by the ME in the call setup message. If the Calling Party number is included in the call setup message, the ME shall include the Address object. Otherwise the ME shall not include the Address object. Subaddress: The Subaddress data object holds the Calling Party Subaddress as received by the ME in the call setup message. If the Calling Party Subaddress is included in the call setup message, the ME shall include the Subaddress object, otherwise the terminal shall not include the Subaddress object. IMS URI: The IMS URI data object is a SIP or TEL URI of the Calling Party received by the ME in the call setup message. This data object will be present only if the "URI support by UICC" Service is present in the USIM or the ISIM Service Table. The IMS URI data object shall contain the SIP URI or tel URI indicated in the P-Asserted-Identity field as defined in TS 24.229. In case the P-Asserted-Identity field is missing the SIP URI or tel URI indicated in the From header field shall be used. If the URI is longer than the maximum length that can be transmitted to the UICC, then the URI shall be truncated to the maximum length that can be transmitted to the UICC and the request shall contain a URI truncated tag. Media Type: The Media Type indicates the type of media of the incoming call session and shall be coded as defined in clause 8.132. The Media Type data object shall be present, if the "Media Type support" service is allocated and activated in the USIM or ISIM Service Table. Response parameters/data:

• none.

If the Network Rejection event is part of the current event list (as set up by the last SET UP EVENT LIST command, see ETSI TS 102 223 [32] clause 6.4.16), then, in the case of GERAN/UTRAN if the terminal receives a LOCATION UPDATING REJECT message or a GPRS ATTACH REJECT message or a ROUTING AREA UPDATE REJECT message (as defined in TS 24.008) or in the case of E-UTRAN and Satellite E-UTRAN if the terminal receives an EMM ATTACH REJECT message or TRACKING AREA UPDATE REJECT message (as defined in TS 24.301), or in the case of NG-RAN and Satellite NG-RAN if the terminal receives a REGISTRATION REJECT message (as defined in TS 24.501), the terminal shall inform the UICC that this has occurred, by using the ENVELOPE (EVENT DOWNLOAD - Network Rejection Event) command as defined below.

Direction: The command header is specified in TS 31.101. Command parameters/data.

• Event list: the Event list data object shall contain only one event (value part of length 1 byte), and terminal shall set the event to:
  • Network Rejection Event.
• Device identities: the terminal shall set the device identities to:
  • source: Network;
  • destination: UICC.
• Location information: This data object shall only be present when the ME receives a LOCATION UPDATING REJECT message, and shall contain the identification (MCC, MNC, and LAC) of the rejecting network.
• Routing Area Identification: This data object shall only be present when the ME receives a GPRS ATTACH REJECT message or a ROUTING AREA UPDATE REJECT message and shall contain the identification (MCC, MNC, LAC and RAC) of the rejecting network.
• Tracking Area Identification: This data object shall only be present when the ME receives an EMM ATTACH REJECT or a TRACKING AREA UPDATE REJECT or a REGISTRATION REJECT message and shall contain the identification (MCC, MNC and TAC) of the rejecting network.
• Access Technology: This data object shall contain the access technology of the rejecting network.
• Update/Attach/Registration Type: This data object contains the location updating or attach or update or EPS attach or EPS update or 5GS registration type that was used in the LOCATION UPDATING REQUEST or GPRS ATTACH REQUEST or ROUTING AREA UPDATE REQUEST or EMM ATTACH REQUEST or TRACKING AREA UPDATE REQUEST or REGISTRATION REQUEST message.
• Rejection Cause Code: This data object contains the cause code value that was received in the LOCATION UPDATING REJECT or GPRS ATTACH REJECT or ROUTING AREA UPDATE REJECT or EMM ATTACH REJECT or TRACKING AREA UPDATE REJECT or REGISTRATION REJECT message.
• Extended Rejection Cause Code: This data object contains the extended cause code value that was received in the EMM ATTACH REJECT or TRACKING AREA UPDATE REJECT message.
• Extended information: This data object contains additional details about the type of cell and additional cell identifier of the rejecting network.

Response parameters/data: None for this type of ENVELOPE command.

See ETSI TS 102 223 [32] clause 7.5.2.1.

Direction: The command header is specified in TS 31.101. Command parameters/data.

Event list: the event list object shall contain only one event (value part of length 1 byte), and the ME shall set the event to:

• call connected.

Device identities:

• in the case of connecting at the near end (an MT call), the ME shall set the device identities to:
  • source: ME;
  • destination: UICC.
• in the case of connecting at the far end (an MO call), the ME shall set the device identities to:
  • source: network;
  • destination: UICC.

Transaction identifier: the Transaction identifier data object shall contain one transaction identifier. Media Type: The Media Type indicates the type of media of the call session and shall be coded as defined in clause 8.132. The Media Type data object shall be present, if the "Media Type support" service is allocated and activated in the USIM or ISIM Service Table. Response parameters/data:

• none.

If the CSG Cell Selection event is part of the current event list (as set up by the last SET UP EVENT LIST command, see ETSI TS 102 223 [32]), then, when the ME detects a change in its current CSG or Hybrid cell selection status, the ME shall inform the UICC that it has occurred, using ENVELOPE (EVENT DOWNLOAD - CSG Cell Selection) as defined below.

Direction: The command header is specified in TS 31.101 Command parameters/data

• Event list: the Event list data object shall contain only one event (value part of length 1 byte), and terminal shall set the event to:
  • CSG Cell Selection.
• Device identities: the terminal shall set the device identities to:
  • source: Network;
  • destination: UICC.
• Access Technology: This data object shall contain the access technology of the current serving cell. If the device is not camping on any cell, this data object shall not be present.
• CSG cell selection status: this data object shall contain CSG or Hybrid cell selection status. The ME should send the event indicating that it is not camped on a CSG or Hybrid cell only after a previous event that indicated that UE was camped on a CSG or Hybrid cell.
• CSG ID: If the UE is camping on a CSG or Hybrid cell in the Allowed CSG list or the Operator CSG list, this data object shall be present, and shall contain CSG id of the current serving CSG or Hybrid cell. In all other cases this data object shall not be present.
• HNB name: If the UE is camping on a CSG or Hybrid cell in the Allowed CSG list or the Operator CSG list and the HNB name of the cell is available in the broadcasted information to the ME, this data object shall be present, and shall contain the broadcasted HNB name of the current serving CSG or Hybrid cell. In all other cases this data object shall not be present.
• PLMN ID: If the UE is camping on a CSG or Hybrid cell that is listed in the Allowed CSG list or the Operator CSG list, this data object may be present, and, if present, shall contain the PLMN identity of the current serving CSG or Hybrid cell.

Response parameters/data: None for this type of ENVELOPE command.

See ETSI TS 102 223 [32] clause 7.5.3.1.

Direction: The command header is specified in TS 31.101. Command parameters/data.

Event list: the event list object shall contain only one event (value part of length 1 byte), and the ME shall set the event to:

• call disconnected.

Device identities:

• in the case of "near end" disconnection, the ME shall set the device identities to:
  • source: ME;
  • destination: UICC.
• in the case of "far end" disconnection, the ME shall set the device identities to:
  • source: network;
  • destination: UICC.

Transaction identifier: the transaction identifier data object shall contain a list of the transaction identifiers for each of the calls being disconnected. Cause: the cause shall reflect the cause information element sent or received in the disconnect message triggering the ENVELOPE command. If the cause information element was not present in the message, or the cause data object shall not be included. In the case of a radio link timeout, the cause data object shall be included, with a value part of zero length. Media Type: The Media Type indicates the type of media of the call session and shall be coded as defined in clause 8.132. The Media Type data object shall be present if the "Media Type support" service is allocated and activated in the USIM or ISIM Service Table. IMS call disconnection cause: The IMS call disconnection cause shall reflect the Reason header field in the SIP message triggering the ENVELOPE command. If the Reason header field is not present in the SIP message, the IMS call disconnection cause data object shall not be included. The cause and corresponding protocol shall not be present in the ENVELOPE command within a corresponding IMS call disconnection cause data object if the "IMS call disconnection cause" service is neither allocated and activated in the USIM nor ISIM Service Table. Response parameters/data:

• none.