Content for TS 31.111 Word version: 19.2.0
6.8 Structure of TERMINAL RESPONSE
6.9 Proactive UICC session and ME display interaction
6.10 Handling of unknown, unforeseen and erroneous messages
6.11 Proactive commands versus possible Terminal response
...
...
6.8 Structure of TERMINAL RESPONSE p. 53
6.8.0 Overall structure of TERMINAL RESPONSE |R14| p. 53
Direction:
ME to UICC.
The command header is specified in TS 31.101. Length (A+B+ … +AG) is indicated by P3 of the header.
Command parameters/data.
| Description | Clause | M/O/C | Min | Length |
|---|---|---|---|---|
| Command details | 8.6 | M | Y | A |
| Device identities | 8.7 | M | N | B |
| Result | 8.12 | M | Y | C |
| Duration (only required in response to a POLL INTERVAL proactive command) | 8.8 | C | N | D |
| Text string (only required in response to a GET INKEY or GET INPUT or SEND USSD proactive command) | 8.15 | C | N | E |
| Item identifier (only required in response to SELECT ITEM proactive command) | 8.10 | C | N | F |
| Local information (only required in response to PROVIDE LOCAL INFORMATION proactive command) | 8.19, 8.20, 8.29, 8.39, 8.45, 8.46, 8.62, 8.83, 8.85, 8.86, 8.87, 8.100, 8.129, 8.130, 8.131, 8.134, 8.140, 8.141, 8.144, 8.147, 8.148, 8.149 | C | N | G |
| Local information (only required in response to PROVIDE LOCAL INFORMATION (Network Measurement Results) proactive command) | 8.22, 8.119 | C | N | AB or
AB0 + … + ABn |
| Local information (only required in response to PROVIDE LOCAL INFORMATION (H(e)NB IP address request) proactive command) | 8.58 | C | N | AC or
AC0 + … + ACn |
| Local information (only required in response to PROVIDE LOCAL INFORMATION (list of surrounding macrocells) proactive command) | 8.19, 8.62 | C | N | AD or
AD0 + … + ADn |
| Call control requested action (only required if call control by USIM has modified a proactive command SET UP CALL, SEND SS or SEND USSD in another type of request). | 8.30 | C | N | H |
| Result data object 2 (only required if call control by USIM has modified a proactive command SET UP CALL, SEND SS or SEND USSD in another type of request). | 8.12 | C | N | I |
| Card reader status (only required in response to GET READER STATUS command). According to the requested information, one Card reader status object for each card interface reported, or one Card reader identifier object is required. | 8.33, 8.57 | C | N | J0 + … + Jn
or J |
| Card ATR (only required in response to POWER ON CARD). | 8.34 | C | N | K |
| R-APDU (only required in response to PERFORM CARD APDU). | 8.36 | C | N | L |
| Timer identifier (only required in response to a TIMER MANAGEMENT proactive command) | 8.37 | C | N | M |
| Timer value (only required in response to a TIMER MANAGEMENT proactive command) | 8.38 | C | N | N |
| AT Response (only required in response to RUN AT COMMAND proactive command) | 8.41 | C | N | P |
| Text string2 (only required if call control by USIM has modified the proactive command SET UP CALL or SEND SS into a USSD request) | 8.15 | C | N | Q |
| Channel data (only required in response to RECEIVE DATA) | 8.53 | C | N | R |
| Channel status (only required in response to GET CHANNEL STATUS or OPEN CHANNEL proactive command) | 8.56 | C | N | S0 + … + Sn |
| Channel data length (only required in response to RECEIVE DATA or SEND DATA proactive command) | 8.54 | C | N | T |
| Bearer description (only required in response to OPEN CHANNEL proactive command) | 8.52 | C | N | U |
| Buffer size (only required in response to OPEN CHANNEL proactive command) | 8.55 | C | N | V |
| Total display duration (only required in response to a GET INKEY proactive command) | 8.8 | C | N | W |
| Service availability (only required in response to SERVICE SEARCH proactive command) | 8.68 | C | N | X |
| Service record (only required in response to GET SERVICE INFORMATION proactive command) | 8.64 | C | N | Y |
| Other address (local address) (only required in response to OPEN CHANNEL proactive command with dynamic local address request) | 8.58 | C | N | |
| Frames Information (only required in response to SET FRAMES or GET FRAMES STATUS proactive commands) | 8.81 | C | N | AA |
| Slices Information (only required in response to PROVIDE LOCAL INFORMATION (list of slice(s) information) proactive command) | 8.145, 8.152, 8.154, 8.156, 8.159 | C | N | AE |
| Rejected Slices Information (only required in response to PROVIDE LOCAL INFORMATION (list of rejected slice(s) information proactive command) | 8.151, 8.153, 8.154 | C | N | AF |
| More data (only required if ME has more data in the buffer to be sent to the UICC and complete data cannot be included in a single response) e.g. it may be required for PROVIDE LOCAL INFORMATION (list of slice(s) information). | 8.158 | C | N | AG |
Specific rules apply for the coding of the TERMINAL RESPONSE, see ETSI TS 102 223 [32] clause 6.8.
Response parameters/data:
None.
6.8.1 Command details p. 55
See ETSI TS 102 223 [32] clause 6.8.1.
6.8.2 Device identities p. 55
See ETSI TS 102 223 [32] clause 6.8.2.
6.8.3 Result p. 55
See ETSI TS 102 223 [32] clause 6.8.3.
6.8.4 Duration p. 55
See ETSI TS 102 223 [32] clause 6.8.4.
6.8.5 Text string p. 55
ETSI TS 102 223 [32] clause 6.8.5 applies, with the addition of the following procedure.
When the ME issues a successful TERMINAL RESPONSE for a SEND USSD command, it shall supply the text returned within the Return Result message from the network, no matter what type of string was returned.
6.8.6 Item identifier p. 55
See ETSI TS 102 223 [32] clause 6.8.6.
6.8.7 Local information p. 56
For Local Information values defined in clause 8.6 then ETSI TS 102 223 [32] clause 6.8.7 applies, with the addition of the following procedures:
-
Where the UICC has requested the Network Measurement Results, the TERMINAL RESPONSE shall contain
- for GERAN: The NMR data object and the BCCH channel list data object
- for UTRAN: The Network Measurement Results are coded as the MEASUREMENT REPORT message as defined in TS 25.331.
- for E-UTRAN and Satellite E-UTRAN: The Network Measurement Results are coded as the MeasurementReport message defined in TS 36.331
- for NG-RAN or Satellite NG-RAN: The Network Measurement Results are coded as the MeasurementReport message defined in TS 38.331
- Where the UICC has requested the Network Measurement Results for multiple access technologies, TERMINAL RESPONSE shall contain the Access Technology data object listing all current access technologies, followed by one NMR data object and one BCCH channel list data object for each current access technology in the same sequence. The BCCH channel list data object shall immediately follow the NMR data object, even if not supported by a network access technology. If no NMR data or no BCCH channel list is available for an access technology, the respective data object shall have length zero.
- Where the UICC has requested the Timing Advance, the TERMINAL RESPONSE shall contain the Timing Advance data object if supported by the network access technology.
- Where the UICC has requested the WLAN Specific Identifier, the TERMINAL RESPONSE shall contain the WSID of the current I-WLAN connection.
- Where the UICC has requested the WLAN Identifier, the TERMINAL RESPONSE shall contain the SSID, the BSSID when available, and the HESSID when available, of the current WLAN connection.
- Where the UICC has requested the CSG ID list Identifier, the TERMINAL RESPONSE shall contain the CSG ID list and the corresponding HNB name (if available in the broadcasted information to the ME) of the detected CSG or Hybrid cells in the Allowed CSG list or the Operator CSG list. (if class "q" is supported)
- Where the UICC has requested the H(e)NB IP address, the TERMINAL RESPONSE shall contain the list of all IP addresses available on the H(e)NB-network interface, as a sequence of "Other Address" Data Objects in the TERMINAL RESPONSE. (if class "v" is supported)
- Where the UICC has requested the list of surrounding macrocells, the TERMINAL RESPONSE shall contain, for all supported access technologies, the Access Technology data object listing all current access technologies, followed by one location information data object for each current access technology in the same sequence, up to the limit of the TERMINAL RESPONSE APDU command size. If no location information is available for an access technology, the respective data object shall have length zero. (if class "w" is supported).
-
Where the UICC has requested the list of slice(s) information, the TERMINAL RESPONSE shall contain the Serving PLMN served S-NSSAIs list and its associated DNN(s) list, along with:
- either the slices information data object listing all slice(s) information without S-NSSAI mapping data object (if S-NSSAI mapping information is not available) or the list of slice(s) information with S-NSSAI mapping data object listing all available mapping information,
- if the S-NSSAI is supported only on a subset of Tracking Area(s) of the current Registration Area, the tracking area identity list where the S-NSSAI is supported shall be available. If ME has more data in the buffer to be sent to the UICC and complete data cannot be included within a single response, the TERMINAL RESPONSE shall contain the 'More data' data object. If 'More data' data object is part of this request, then TERMINAL RESPONSE shall contain only the associated data object (e.g., 'partial NSSAI' data object) with remaining S-NSSAI information, up to the limit of the TERMINAL RESPONSE APDU (see Annex V).
- Where the UICC has requested the CAG information list, the TERMINAL RESPONSE shall contain the CAG information list and the corresponding CAG Human-readable network name per CAG ID (if available in the broadcasted information to the ME) of the detected CAG cells. (if class "ag" is supported).
-
Where the UICC has requested the list of rejected slice(s), then TERMINAL RESPONSE shall contain:
- either the list of rejected slice(s) information with S-NSSAI mapping information (if S-NSSAI mapping information is available) or rejected slice(s) information without S-NSSAI mapping information (if S-NSSAI mapping information is not available),
- if the S-NSSAI is rejected only on a subset of Tracking Area(s) of the current Registration Area, the tracking area identity list where the S-NSSAI is rejected shall be available. If ME has more data in the buffer to be sent to the UICC and complete data cannot be included within a single response, the TERMINAL RESPONSE shall contain the 'More data' data object. If 'More data' data object is part of this request, then TERMINAL RESPONSE shall contain only the associated data object (e.g., 'partial NSSAI' data object) with remaining S-NSSAI information, up to the limit of the TERMINAL RESPONSE APDU (see Annex V).
6.8.8 Call control requested action p. 57
When the ME issues a TERMINAL RESPONSE for a proactive command SET UP CALL, SEND SS or SEND USSD which has been modified by call control by USIM in another type of request, it shall supply the response data given in response to the ENVELOPE (CALL CONTROL).
6.8.9 Result data object 2 p. 57
When the ME issues a TERMINAL RESPONSE for a proactive command SET UP CALL, SEND SS or SEND USSD which has been modified by call control by USIM in another type of request, it shall supply the Result data object it would have supplied for the proactive command equivalent to the action requested by call control, and given in the Call control request data element.
6.8.10 Card reader status p. 57
See ETSI TS 102 223 [32] clause 6.8.10.
6.8.11 Card ATR p. 57
See ETSI TS 102 223 [32] clause 6.8.11.
6.8.12 R-APDU p. 57
See ETSI TS 102 223 [32] clause 6.8.12.
6.8.13 Timer identifier p. 57
See ETSI TS 102 223 [32] clause 6.8.13.
6.8.14 Timer value p. 57
See ETSI TS 102 223 [32] clause 6.8.14.
6.8.15 AT Response p. 58
See ETSI TS 102 223 [32] clause 6.8.15.
6.8.16 Text string 2 p. 58
When the ME issues a successful TERMINAL RESPONSE for a proactive command SET UP CALL or SEND SS which has been modified by "call control" by USIM into a USSD request ('05' result value), it shall supply the Text string 2. The Text string 2 shall contain the text returned within the Return Result message from the network for the USSD response. Text string 2 is equivalent to the Text string in the Terminal Response to a SEND USSD command.
6.8.17 Channel data p. 58
See ETSI TS 102 223 [32] clause 6.8.17.
6.8.18 Channel status p. 58
See ETSI TS 102 223 [32] clause 6.8.18.
6.8.19 Channel data length p. 58
See ETSI TS 102 223 [32] clause 6.8.19.
6.8.20 Bearer description p. 58
See ETSI TS 102 223 [32] clause 6.8.20.
6.8.21 Buffer size p. 58
See ETSI TS 102 223 [32] clause 6.8.21.
6.8.22 Total Display Duration p. 58
See ETSI TS 102 223 [32] clause 6.8.22.
6.8.23 Service Availability p. 58
See ETSI TS 102 223 [32] clause 6.8.23.
6.8.24 Service Record p. 58
See ETSI TS 102 223 [32] clause 6.8.24.
6.8.25 Other address (local address) |R7| p. 58
See ETSI TS 102 223 [32] clause 6.8.25.
6.8.26 Frames Information |R7| p. 58
See ETSI TS 102 223 [32] clause 6.8.26.
6.9 Proactive UICC session and ME display interaction p. 58
See ETSI TS 102 223 [32] clause 6.9.
6.10 Handling of unknown, unforeseen and erroneous messages p. 59
See ETSI TS 102 223 [32] clause 6.10.
6.11 Proactive commands versus possible Terminal response p. 59
Table 6.1 shows for each proactive command the possible terminal response returned (marked by a "•" character), in addition to those defined in ETSI TS 102 223 [32] clause 6.11.
The commands "COMMAND CONTAINER" and "ENCAPSULATED SESSION CONTROL" listed in ETSI TS 102 223 [32] are not required by 3GPP.
| TERMINAL RESPONSE | PROACTIVE COMMAND | |||||
|---|---|---|---|---|---|---|
| SET UP CALL | SEND SS | SEND USSD | SEND SMS | Geographical Location Request | ||
| '10' | '11' | '12' | '13' | '16' | ||
| 00 | Command performed successfully | • | • | • | • | • |
| 01 | Command performed with partial comprehension | • | • | • | • | • |
| 02 | Command performed, with missing information | • | • | • | • | • |
| 03 | REFRESH performed with additional Efs read | |||||
| 04 | Command performed successfully, but requested icon could not be displayed | • | • | • | • | • |
| 05 | Command performed, but modified by call control by USIM | • | • | |||
| 06 | Command performed successfully, limited service | |||||
| 07 | Command performed with modification | |||||
| 08 | REFRESH performed but indicated USIM was not active | |||||
| 09 | Command performed successfully, tone not played | |||||
| 10 | Proactive UICC session terminated by the user | • | ||||
| 11 | Backward move in the proactive UICC session requested by the user | |||||
| 12 | No response from user | • | ||||
| 13 | Help information required by the user | |||||
| 14 | USSD or SS Transaction terminated by user | • | • | • | ||
| 15 | Reserved for 3GPP (for future usage) | |||||
| 16 | Reserved for 3GPP (for future usage) | |||||
| 20 | ME currently unable to process command | • | • | • | • | • |
| 21 | Network currently unable to process command | • | • | • | • | • |
| 22 | User did not accept the proactive command | • | • | |||
| 23 | User cleared down call before connection or network release | • | ||||
| 24 | Action in contradiction with the current timer state | |||||
| 25 | Interaction with call control by USIM, temporary problem | • | • | • | ||
| 26 | Launch browser generic error | |||||
| 27 | MMS Temporary Problem | |||||
| 28 | Reserved for 3GPP (for future usage) | |||||
| 29 | Reserved for 3GPP (for future usage) | |||||
| 30 | Command beyond Mes capabilities | • | • | • | • | • |
| 31 | Command type not understood by ME | • | • | • | • | • |
| 32 | Command data not understood by ME | • | • | • | • | • |
| 33 | Command number not known by ME | • | • | • | • | • |
| 34 | SS Return Error | • | • | |||
| 35 | SMS RPERROR | • | ||||
| 36 | Error, required values are missing | • | • | • | • | • |
| 37 | USSD return error | • | ||||
| 38 | Multiple Card command error | |||||
| 39 | Interaction with call/SM control by USIM, permanent problem | • | • | • | • | |
| 3A | Bearer Independent Protocol error | |||||
| 3B | Access Technology unable to process command | |||||
| 3C | Frames error | • | • | • | • | |
| 3D | MMS Error | |||||
| 3E | Reserved for 3GPP (for future usage) | |||||
| 3F | Reserved for 3GPP (for future usage) | |||||
