6 Proactive UICC
31.1113GPPRelease 18TSUniversal Subscriber Identity Module (USIM) Application Toolkit (USAT)
6.1 Introduction
TS 31.101 [13] defines the communication protocols between the ME and the UICC, and defines a mechanism to transport "proactive" commands using these protocols. Details about how this mechanism is used for USAT are defined in TS 102 223 [32] clause 6.1. The supported proactive commands are specified in clause 6.4. of the present document.
If the UICC issues an instruction to the ME to initiate a Mobile Originated transaction (e.g. SEND SMS, SEND SS, SEND USSD or SEND DTMF), then unless explicitly stated elsewhere in the present document or in TS 31.101 [13], the content supplied by the UICC for onward transmission by the ME shall not be altered by the ME.
6.2 Identification of ME support
See ETSI TS 102 223 [32] clause 6.2.
6.3 General procedure
See ETSI TS 102 223 [32] clause 6.3.
6.4 Proactive UICC commands and procedures
6.4.1 DISPLAY TEXT
See ETSI TS 102 223 [32] clause 6.4.1.
6.4.2 GET INKEY
See ETSI TS 102 223 [32] clause 6.4.2.
6.4.3 GET INPUT
See ETSI TS 102 223 [32] clause 6.4.3.
6.4.4 MORE TIME
See ETSI TS 102 223 [32] clause 6.4.4.
6.4.5 PLAY TONE
See ETSI TS 102 223 [32] clause 6.4.5.
NOTE: Some supervisory tones are optional for mobile equipment (see TS 22.001 [22]).
6.4.6 POLL INTERVAL
See ETSI TS 102 223 [32] clause 6.4.6.
6.4.7 REFRESH
See ETSI TS 102 223 [32] clause 6.4.7 except for:
– "eUICC Profile State Change" and "Application Update" which are not required by 3GPP;
– "3G Session Reset" and "Steering of Roaming" which are defined as follows.
3G Session Reset:
This mode causes the ME to reset the 3G session, in accordance with the 3G session reset procedure defined in TS 31.102 [14]. Subsequently, the ME performs the "USIM Initialization and File Change Notification" procedure and the MM Restart procedure as defined in TS 23.122 [7].
Steering of Roaming:
This mode triggers a steering of roaming procedure with optionally SOR-CMCI as defined in TS 23.122 [7] or a steering of roaming for I-WLAN procedure as defined in TS 24.234 [42].
The ME shall store the SOR-CMCI received in the USAT REFRESH command accordingly to TS 23.122 [7].
6.4.7.1 EFIMSI changing procedure
When an EFIMSI is changed via Data Download or a USAT application and a REFRESH command is issued by the UICC the following rules apply to the UICC and ME:
– USIM Initialization. This command shall not be used if an EFIMSI is changed, as the behaviour of the UE is unpredictable;
– File Change Notification. This command shall not be used if an EFIMSI is changed, as the behaviour of the UE is unpredictable;
– USIM Initialization and File Change Notification. This command shall not be used if an EFIMSI is changed, as the behaviour of the UE is unpredictable;
– USIM Initialization and Full File Change Notification. This command shall not be used if an EFIMSI is changed, as the behaviour of the UE is unpredictable;
– UICC Reset. Normal UICC Reset procedure is carried out;
– USIM Application Reset. Normal USIM Application Reset procedure is carried out;
– 3G Session Reset. Normal 3G Session Reset procedure is carried out.
If an EFIMSI is to be updated, neither EFIMSI , EFPSLOCI , EFEPSLOCI , EFLOCI , EF5GS3GPPLOCI nor EF5GSN3GPPLOCI shall be updated in the UICC before the 3G session termination procedure has been completed by the ME.
6.4.7.2 Generic Bootstrapping Procedure Request
If Toolkit-initiated GBA is supported by the ME, as indicated in the TERMINAL PROFILE, then the following applies:
When the UICC issues a REFRESH command implying a File Change Notification on EFGBABP (GBA Bootstrapping parameters) under ADF USIM or ADF ISIM the ME shall perform a GBA bootstrapping procedure (as defined in TS 31.102 [14] or TS 31.103 [62]).
This procedure applies to REFRESH command only in the following modes: USIM File Change Notification; USIM Initialization and File Change Notification; and 3G Session Reset.
6.4.7.3 EFUICCIARI changing procedure
When an EFUICCIARI is changed in either the USIM or the ISIM via Data Download or a USAT application and a REFRESH command is issued by the UICC the following rule applies to the ME:
The ME shall read the updated list of IARIs associated with active applications installed on the UICC and follow the procedures defined in TS 24.229 [52].
6.4.7.4 Steering of roaming and steering of roaming for I-WLAN procedure
The steering of roaming procedures defined in TS 23.122 [7] and in TS 24.234 [42] might take a long time. In order to avoid blocking the Toolkit interface, the ME shall send the TERMINAL RESPONSE (Command performed successfully) immediately after starting the steering of roaming procedure, without waiting for its completion. The ME shall send TERMINAL RESPONSE (ME unable to process command or other appropriate code) in case it fails to start the steering of roaming procedure.
6.4.7.5 Steering of roaming via NAS messages
When the ME receives an SOR transparent container, as specified in 3GPP TS 24.501 [70] clause 9.11.3.51, via a REGISTRATION ACCEPT message (see 3GPP TS 23.122 [7] Annex C.2 ) or via a DL NAS TRANSPORT message (see 3GPP TS 23.122 [7] Annex C.3 ), with the indication that the transparent container shall be forwarded to the USIM using SMS-PP data download, and the integrity check of the message was successful, the ME shall pass the transparent container to the USIM by using the procedure for SMS-PP data download via REGISTRATION ACCEPT or DL NAS TRANSPORT messages as described in clause 7.1.1.1a
6.4.7.6 Routing Indicator Data update via NAS messages
When the ME receives a secure packet in a UE parameters update data set with UE parameters update data set type set to Routing Indicator update data as specified in 3GPP TS 24.501 [70] clause 9.11.3.53A, via a DL NAS TRANSPORT message, and the integrity check of the message was successful, the ME shall pass the transparent container to the USIM by using the procedure for SMS-PP data download via DL NAS TRANSPORT messages as described in clause 7.1.1.1a. Upon successfully processing the Routing Indicator data from the secure packet on the UICC, the UICC shall issue a File Change Notification REFRESH.
6.4.7.7 EFSUPI_NAI changing procedure
When an EFSUPI_NAI is changed via Data Download or a USAT application and a REFRESH command is issued by the UICC the following rules apply to the UICC and ME:
– USIM Initialization. This command shall not be used if an EFSUPI_NAI is changed, as the behaviour of the UE is unpredictable;
– File Change Notification. This command shall not be used if an EFSUPI_NAI is changed, as the behaviour of the UE is unpredictable;
– USIM Initialization and File Change Notification. This command shall not be used if an EFSUPI_NAI is changed, as the behaviour of the UE is unpredictable;
– USIM Initialization and Full File Change Notification. This command shall not be used if an EFSUPI_NAI is changed, as the behaviour of the UE is unpredictable;
– UICC Reset. Normal UICC Reset procedure is carried out;
– USIM Application Reset. Normal USIM Application Reset procedure is carried out;
– 3G Session Reset. Normal 3G Session Reset procedure is carried out.
If an EFSUPI_NAI is to be updated, neither EFSUPI_NAI , EF5GS3GPPLOCI nor EF5GSN3GPPLOCI shall be updated in the UICC before the 3G session termination procedure has been completed by the ME.
6.4.7.8 EFDRI changing procedure
When an EFDRI is changed in the USIM via Data Download or a USAT application and a REFRESH command is issued by the UICC the following rule applies to the ME:
If the ME supports MINT (see 3GPP TS 23.122 [7]), the ME shall read the updated disaster roaming information and follow the procedures defined in 3GPP TS 23.122 [7].
6.4.7.9 EF5GNSWO_CONF changing procedure
When an EF5GNSWO_CONF is changed in the USIM via Data Download or a USAT application and a REFRESH command is issued by the UICC the following rule applies to the ME:
If the ME supports 5G NSWO, the ME shall read the updated 5G NSWO configuration in the EF and follow the procedures defined in the 3GPP TS 33.501 [75] Annex S.3.
6.4.8 SET UP MENU
See ETSI TS 102 223 [32] clause 6.4.8.
6.4.9 SELECT ITEM
See ETSI TS 102 223 [32] clause 6.4.9.
6.4.10 SEND SHORT MESSAGE
This command requests the ME to send a short message.
Two types are defined in ETSI TS 102 223 [32] clause 6.4.10 and apply as follows within the context of the present document:
– a short message to be sent to the network in an SMS-SUBMIT message, or an SMS-COMMAND message, where the user data can be passed transparently;
– a short message to be sent to the network in an SMS-SUBMIT message where the text needs to be packed by the ME.
Where the text has been packed, the text string provided by the UICC shall not be longer than 160 characters. It shall use the SMS default 7-bit coded alphabet, packed into 8-bit octets, in accordance with TS 23.038 [4]. The data coding indication contained in the Data Coding Scheme byte shall be "default alphabet". The text length (which is part of the SMS TPDU) given by the UICC shall state the number of 7-bit characters in the text string. The command details shall indicate "packing not required".
8-bit data Short Messages may be sent by the UICC. The command shall indicate packing not required. The data coding indication contained in the Data Coding Scheme byte shall be "8 bit". The string shall not be longer than 140 bytes, and the length (in SMS TPDU) shall state the number of bytes in the string.
If UCS2 is supported by the ME, 16-bit data Short Messages may be sent by the UICC. The text string provided by the UICC shall not be longer than 70 characters. It shall use the 16-bit UCS2 alphabet format, in accordance with TS 23.038 [4]. The text length (which is part of the SMS TPDU) given by the UICC shall state the number of 16-bit characters in the text string. The command details shall indicate "packing not required".
SMS commands may be sent by the UICC. These shall count as packed text message. The SMS TPDU from the UICC shall indicate SMS-COMMAND. The command details shall indicate "packing not required".
Where packing by the ME is required, the text string provided by the UICC shall not be longer than 160 characters. It shall use the SMS default 7-bit coded alphabet as defined in TS 23.038 [4] with bit 8 set to 0. The text length given by the UICC shall state the number of characters in the text string. The ME shall pack the text string and modify the Data Coding Scheme byte to "default alphabet" in accordance with TS 23.038 [4] before submitting the message to the network.
Optionally, the UICC may include in this command an alpha identifier. See ETSI TS 102 223 [32] clause 6.4.10 for the use of this alpha identifier.
If the ME is capable of SMS-MO, then it shall send the data as a Short Message TPDU to the destination address. The ME shall give the result to the UICC using TERMINAL RESPONSE (indicating successful or unsuccessful transmission of the Short Message) after receiving an SMS RP-ACK or RP-Error from the network. If an alpha identifier was provided by the UICC, the ME should not give any information to the user at the reception of SMS RP-ACK or RP-Error.
If the Short Message TPDU is unsuccessfully received by the network (e.g. the reception of a CP-ERROR), the ME shall inform the UICC using TERMINAL RESPONSE (network currently unable to process command). If a null alpha identifier was provided by the UICC, the ME should not give any information to the user at the unsuccessful network reception.
6.4.11 SEND SS
Upon receiving this command, the ME shall decide if it is able to execute the command. Examples are given below, but the list is not exhaustive:
– if the command is rejected because the ME is busy on an SS transaction, the ME informs the UICC using TERMINAL RESPONSE (ME unable to process command – currently busy on SS transaction);
– if the command is rejected because the ME is busy on a USSD transaction, the ME shall inform the UICC using TERMINAL RESPONSE (ME unable to process command – currently busy on USSD transaction);
– if the command is rejected because the ME does not support that Supplementary Service, the ME informs the UICC using TERMINAL RESPONSE (Command beyond ME’s capabilities).
If the ME is able to send the SS request, the ME shall:
– send the SS request immediately, without need to alert the user first;
– optionally, the UICC may include in this command an alpha-identifier. The use of this alpha-identifier by the ME is described below:
– if the alpha identifier is provided by the UICC and is not a null data object, the ME shall use it to inform the user. This is also an indication that the ME should not give any other information to the user on the fact that the ME is sending a SS request. If an icon is provided by the UICC, the icon indicated in the command may be used by the ME to inform the user, in addition to, or instead of the alpha identifier, as indicated with the icon qualifier (see clause 6.5.4);
– if the alpha identifier is provided by the UICC and is a null data object (i.e. length = ’00’ and no value part), this is an indication that the ME should not give any information to the user on the fact that the ME is sending an SS request;
– if the alpha identifier is not provided by the UICC, the ME may give information to the user concerning what is happening.
– once an SS Return Result message not containing an error has been received from the network, the ME shall inform the UICC that the command has been successfully executed, using TERMINAL RESPONSE. This command shall include the contents of SS Return Result as additional data.
If a null alpha identifier was provided by the UICC, the ME should not give any information to the user at the reception of an SS Return Result message;
– if the command is rejected because the network cannot support or is not allowing the Supplementary Service request, the ME informs the UICC using TERMINAL RESPONSE (SS Return Result error code).
If a null alpha identifier was provided by the UICC, the ME should not give any information to the user at the reception of a SS Return Result message;
– if the SS request is unsuccessfully received by the network, the ME shall inform the UICC using TERMINAL RESPONSE (network currently unable to process command), and not retry to send the request.
If a null alpha identifier was provided by the UICC, the ME should not give any information to the user at the reception of a SS Return Result message.
A terminal of type ND shall ignore any alpha identifier provided together with this command. The terminal shall respond with "command performed successfully" upon successful completion of the command. A terminal of type ND shall also ignore any icon provided together with this command. The terminal shall respond with "command performed successfully but requested icon could not be displayed" upon successful completion of the command.
If the ME supports the Outgoing Call Information service, the ME shall not store in EFOCI the supplementary service control string sent by the UICC in this command.
The supplementary service control string included in the SEND SS proactive command shall not be checked against those of the FDN list, even if the Fixed Dialling Number service is enabled.
6.4.12 SEND USSD
6.4.12.1 MMI Mode
Upon receiving this command, the ME shall decide if it is able to execute the command. Examples are given below, but the list is not exhaustive:
– if the command is rejected because the ME is busy on a USSD transaction, the ME informs the UICC using TERMINAL RESPONSE (ME unable to process command – currently busy on USSD transaction);
– if the command is rejected because the ME is busy on a SS transaction, the ME informs the UICC using TERMINAL RESPONSE (ME unable to process command – currently busy on SS transaction).
If the ME is able to send the USSD request, the ME shall:
– send the USSD immediately, without need to alert the user first;
– optionally, the UICC may include in this command an alpha-identifier. The use of this alpha-identifier by the ME is described below:
– if the alpha identifier is provided by the UICC and is not a null data object, the ME shall use it to inform the user. This is also an indication that the ME should not give any other information to the user on the fact that the ME is sending a USSD request. If an icon is provided by the UICC, the icon indicated in the command may be used by the ME to inform the user, in addition to, or instead of the alpha identifier, as indicated with the icon qualifier (see clause 6.5.4);
– if the alpha identifier is provided by the UICC and is a null data object (i.e. length = ’00’ and no value part), this is an indication that the ME should not give any information to the user on the fact that the ME is sending a USSD request;
– if the alpha identifier is not provided by the UICC, the ME may give information to the user concerning what is happening.
A terminal of type ND shall ignore any alpha identifier provided together with this command. The terminal shall respond with "command performed successfully" upon successful completion of the command. A terminal of type ND shall also ignore any icon provided together with this command. The terminal shall respond with "command performed successfully but requested icon could not be displayed" upon successful completion of the command.
– once the USSD transaction is initiated, a dialogue between the network and the user may occur which involves the MMI of the ME. If an alpha identifier was initially provided by the UICC, this alpha identifier may be discarded during this dialogue;
– once a RELEASE COMPLETE message containing the USSD Return Result message not containing an error has been received from the network, the ME shall inform the UICC that the command has been successfully executed, using TERMINAL RESPONSE. This command shall include the text contained in the USSD Return Result in a Text String data object. If a null alpha identifier was provided by the UICC, the ME should not give any information to the user at the reception of a USSD Return Result message;
– if the UE clears the transaction by sending a RELEASE COMPLETE upon request of the user, the ME shall inform the UICC using TERMINAL RESPONSE (USSD transaction terminated by user);
– if the USSD operation is rejected because the network cannot support or is not allowing mobile initiated USSD, the ME informs the UICC using TERMINAL RESPONSE (USSD Return Result error code). If a null alpha identifier was provided by the UICC, the ME should not give any information to the user at the reception of a USSD Return Result message;
– if the USSD request is unsuccessfully received by the network, the ME shall inform the UICC using TERMINAL RESPONSE (network currently unable to process command), and not retry to send the request. If a null alpha identifier was provided by the UICC, the ME should not give any information to the user at the reception of a USSD Return Result message.
6.4.12.2 Application Mode
This clause applies if class "p" is supported.
A USSD is considered as Application Mode (Send USSD used for the transport of Data to the network) if the service "data download via USSD and USSD application mode" is allocated and activated in the USIM Service Table (see TS 31.102 [14]) and the DCS coding within the USSD string TLV is set to 8 bit data.
Upon receiving this command, the ME shall decide if it is able to execute the command. Examples are given below, but the list is not exhaustive:
– if the command is rejected because the ME is busy on a USSD transaction, the ME informs the UICC using TERMINAL RESPONSE (ME unable to process command – currently busy on USSD transaction);
– if the command is rejected because the ME is busy on a SS transaction, the ME informs the UICC using TERMINAL RESPONSE (ME unable to process command – currently busy on SS transaction).
If the ME is able to send the USSD request then the ME shall:
– send the USSD immediately, without need to alert the user first;
– optionally, the UICC may include in this command an alpha-identifier. The use of this alpha-identifier by the ME is described below:
– if the alpha identifier is provided by the UICC and is not a null data object, the ME shall use it to inform the user. This is also an indication that the ME should not give any other information to the user on the fact that the ME is sending a USSD request. If an icon is provided by the UICC, the icon indicated in the command may be used by the ME to inform the user, in addition to, or instead of the alpha identifier, as indicated with the icon qualifier (see clause 6.5.4);
– if the alpha identifier is provided by the UICC and is a null data object (i.e. length = ’00’ and no value part), this is an indication that the ME should not give any information to the user on the fact that the ME is sending a USSD request;
– if the alpha identifier is not provided by the UICC, the ME may give information to the user concerning what is happening.
– once a FACILITY (including RELEASE COMPLETE) message containing a USSD Request message has been received from the network, the ME shall inform the UICC that the network requests more information , using the command ENVELOPE (USSD Data Download). This command shall include the text contained in the USSD Request in a Text String data object. If a null alpha identifier was provided by the UICC, the ME should not give any information to the user at the reception of a USSD Request message.
A terminal of type ND shall ignore any alpha identifier provided together with this command. The terminal shall respond with "command performed successfully" upon successful completion of the command. A terminal of type ND shall also ignore any icon provided together with this command. The terminal shall respond with "command performed successfully but requested icon could not be displayed" upon successful completion of the command.
6.4.13 SET UP CALL
This command is issued by the UICC to request a call set up. The procedure is defined in ETSI TS 102 223 [32] clause 6.4.13, except when stated otherwise in the present document.
The UICC may request the use of an automatic redial mechanism according to TS 22.001 [22]
In addition to the rules given in ETSI TS 102 223 [32] clause 6.4.13 the following applies:
– If the UICC supplies a number stored in EFECC, this shall not result in an emergency call.
Upon receiving this command, the ME shall decide if it is able to execute the command. Examples are given below, but the list is not exhaustive:
– if the command is rejected because the ME is busy on another call, the ME informs the UICC using TERMINAL RESPONSE (ME unable to process command – currently busy on call);
– if the command is rejected because the ME is busy on a SS transaction, the ME informs the UICC using TERMINAL RESPONSE (ME unable to process command – currently busy on SS transaction);
– if the command is rejected because the ME cannot support Call Hold, or because the ME does not support the capability configuration parameters requested by the UICC, the ME informs the UICC using TERMINAL RESPONSE (Command beyond ME’s capabilities);
– if the command is rejected because the network cannot support or is not allowing Call Hold of a multi party call, the ME informs the UICC using TERMINAL RESPONSE (SS Return Result error code);
– if the command is rejected because the network cannot support or is not allowing Call Hold of a single call, the ME informs the UICC using TERMINAL RESPONSE (Network currently unable to process command).
If the ME supports the Outgoing Call Information service, the ME shall not store in EFOCI and in EFOCT the call set-up details (called party number and associated parameters) sent by the UICC in this command.
6.4.14 POLLING OFF
See ETSI TS 102 223 [32] clause 6.4.14.
6.4.15 PROVIDE LOCAL INFORMATION
This command requests the ME to send current local information to the UICC. At present, this information is restricted to:
– location information: the mobile country code (MCC), mobile network code (MNC), location area code/tracking area code (LAC/TAC) and cell ID of the current serving cell;
NOTE: For UTRAN the cell ID returned in terminal response is the last known cell ID which may not be the current serving cell, when the ME is on a dedicated channel.
– the IMEI or IMEISV of the ME;
– the Network Measurement Results (and the BCCH channel list if connected to GERAN);
– the current date, time and time zone;
– the current ME language setting;
– the Timing Advance, suitable for GERAN, E-UTRAN, Satellite E-UTRAN, NG-RAN and Satellite NG-RAN
– the current access technology;
– the current network search mode;
– the charge state of the battery (if class "g" is supported);
– the WSID of the current I-WLAN connection;
– the WLAN identifier of the current WLAN connection;
– the CSG ID list and corresponding HNB names (if available in the broadcasted information to the ME) of detected CSG or Hybrid cells in the Allowed CSG list or the Operator CSG list (if class "q" is supported);
– the H(e)NB IP address. (if class "v" is supported);
– the list of location information for surrounding macrocells (if class "w" is supported);
– the list of slice(s) information;
– the CAG information list and the corresponding human-readable network name per CAG ID (if available in the broadcasted information to the ME) of detected CAG cells (if class "ag" is supported).
The above information can be requested only if supported by the ME as indicated in the TERMINAL PROFILE.
The ME shall return the requested local information within a TERMINAL RESPONSE.
Where location information or Network Measurement Results or list of slice(s) information has been requested and no service is currently available, then the ME shall return TERMINAL RESPONSE (ME currently unable to process command – no service).
Where location information or Network Measurement Results or list of slice(s) information has been requested and the ME is on limited service (e.g. emergency calls only), the ME shall return the data requested in the TERMINAL RESPONSE with the general result (Limited Service).
Where Network Measurement Results has been requested and the ME is connected to a different access technology to the one requested (e.g. UTRAN Measurement Qualifier included when ME is connected to a GERAN), then the ME shall return TERMINAL RESPONSE (ME currently unable to process command – no service).
Network Measurement Results are available on a per access technology basis and indicated as such in the Terminal Profile.
Network Measurement Results for a GERAN:
If the NMR are requested and a call is in progress, the value of all the returned parameters provided by the ME in the response to the command will be valid. The NMR returned when a call is in progress from Mes supporting multiband operation, shall be according to the value of the multiband reporting parameter as defined in TS 44.018 [27]. If a call is not in progress (i.e. ME is in idle mode) some of the returned parameters (e.g. RXQUAL) may be invalid. In idle mode, Mes supporting multiband operation shall ignore the value of the multiband reporting parameter and the NMR returned shall be as defined in TS 44.018 [27] when the multiband reporting parameter equals zero.
NOTE 1: When in idle mode, the only information element on which it is possible to rely on is the RXLEV-FULL-SERVING-CELL, which contains the value of the received signal strength on the BCCH of the current serving cell.
NOTE 2: Network Measurement Results are defined in TS 44.018 [27] as Measurement Results.
The BCCH channel list is only available if the ME is connected to a GERAN.
Network Measurement Results for a UTRAN:
The USIM request for measurement information shall not trigger any measurement activities in ME in addition to those requested by UTRAN.
The ME shall only report measurement results that are valid according to the current RRC state or the UTRAN configuration requested.
NOTE 3: The returned parameters provided by the ME, in the response to the command, are subject to the ME capability, currently used radio configuration, current RRC state and the UTRAN configuration requested as defined in the TS 25.331 [38].
NOTE 4: Network Measurement Results are defined in TS 25.331 [38] as the MEASUREMENT REPORT message.
Network Measurement Results for a NG-RAN and Satellite NG-RAN:
The USIM request for measurement information shall not trigger any measurement activities in ME in addition to those requested by NG-RAN and Satellite NG-RAN.
The ME shall only report measurement results that are valid according to the current RRC state or the NG-RAN or Satellite NG-RAN configuration requested.
NOTE 7: The returned parameters provided by the ME, in the response to the command, are subject to the ME capability, currently used radio configuration, current RRC state and the NG-RAN or Satellite NG-RAN configuration requested as defined in the TS 38.331 [71].
NOTE 8: Network Measurement Results are defined in TS 38.331 [71] as the MeasurementReport message.
The ME shall return the current date and time as set by the user. An ME of type NK or type ND may return the date and time received from the network with the NITZ feature (see TS 22.042 [3]), if this is available. If available, the ME shall also return the time zone known from the network with the NITZ feature (see TS 22.042 [3]). If the time zone information is not available, the ME shall return ‘FF’ for this element.
If language setting is requested, the ME shall return the currently used language.
Timing advance is available if the ME is connected to a GERAN, E-UTRAN, Satellite E-UTRAN, NG-RAN or Satellite NG-RAN. If the Timing Advance is requested, the ME shall return the timing advance value that was received from the BTS, eNodeB or gNodeB during the last active dedicated connection (e.g. for call or SMS). Timing advance is defined for GERAN in TS 44.018 [27], for E-UTRAN and Satellite E-UTRAN in 3GPP TS 36.211 [66] and for NG-RAN and Satellite NG-RAN in 3GPP TS 38.211[73]. An ME supporting the Timing Advance feature shall be able to store the last value of timing advance. In addition to the timing advance value, the ME shall return its current status (i.e. ME is in idle mode or not) in order for the application to be aware of potential misinterpretation of the timing advance value. Caution should be taken if using the Timing Advance value for distance measurement as reflections from the external environment (buildings etc.) may affect the accuracy.
If the access technology is requested, the ME shall return the current access technology that the ME is using.
The WSID or the WLAN identifier is only available if the ME is connected to a I-WLAN or a WLAN respectively. If the WSID or the WLAN identifier is requested, the ME shall return the WSID or the WLAN identifier respectively of the currently connected I-WLAN or a WLAN respectively. Where a WSID or the WLAN identifier has been requested and no I-WLAN or WLAN respectively is currently connected, then the ME shall return TERMINAL RESPONSE (ME currently unable to process command – no service).
When CSG ID list is requested, the ME shall return the CSG ID list and the corresponding HNB name (if available in the broadcasted information to the ME). If the CSG ID list has been requested, and the ME is currently not camped on a CSG or Hybrid cell, the ME shall return TERMINAL RESPONSE (ME currently not able to process command – no service).
The proactive command PROVIDE LOCAL INFORMATION – H(e)NB IP address is issued on the H(e)NB-HPSIM interface, see TS 31.104 [56].
When the IP address is requested, the H(e)NB shall return the IP address reported to H(e)MS and/or HNB-GW for location verification based on IP address (which may be a local IP address). If no such IP address is available to the H(e)NB, the H(e)NB shall return TERMINAL RESPONSE (ME currently not able to process command – no service). If several such IP addresses are available, the H(e)NB provides all of them to the UICC.
The proactive command PROVIDE LOCAL INFORMATION – H(e)NB surrounding macrocell is issued on the H(e)NB-HPSIM interface, see TS 31.104 [56].
When the list of surrounding macrocells is requested, the H(e)NB shall provide the list of location information for detected macrocells.
– For the HNB, all cell information contained in: intra-frequency neighbor list, inter-frequency neighbor list, inter-RAT neighbor list, that are reported to the HMS, see TS 32.582 [57] sec 6.1.1.
– For the HeNB, all cell information contained in: LTE cell neighbor list, UMTS cell neighbor list, GSM cell neighbor list, that are reported to the HeMS, see TS 32.592 [58] sec 6.1.15.
Location information contains the mobile country code (MCC), mobile network code (MNC), location area code/tracking area code (LAC/TAC) and cell ID. The list of surrounding macrocells is provided for all access technologies supported by the H(e)NB, up to the limit of the TERMINAL RESPONSE APDU command size.
NOTE 9: the HPSIM request for H(e)NB surrounding macrocell does not trigger a network scan; the H(e)NB reports available information to the HPSIM.
When the list of slice(s) information is requested, the Serving PLMN S-NSSAIs list shall be returned.
An S-NSSAI, as specified in 3GPP TS 23.003 [30], is comprised of:
– A Slice/Service type (SST)
– A Slice Differentiator (SD)
When the CAG information list and the corresponding human-readable network name per CAG ID (if available in the broadcasted information to the ME) is requested, the ME shall return the CAG information list and the corresponding human-readable network name per CAG ID (if available in the broadcasted information to the ME). If the CAG information list has been requested, and the ME is currently not camped on a CAG cell, the ME shall return TERMINAL RESPONSE (ME currently not able to process command – no service).
6.4.16 SET UP EVENT LIST
See ETSI TS 102 223 [32] clause 6.4.16.
6.4.17 PERFORM CARD APDU
See ETSI TS 102 223 [32] clause 6.4.17.
6.4.18 POWER OFF CARD
See ETSI TS 102 223 [32] clause 6.4.18.
6.4.19 POWER ON CARD
See ETSI TS 102 223 [32] clause 6.4.19.
6.4.20 GET READER STATUS
See ETSI TS 102 223 [32] clause 6.4.20.
6.4.21 TIMER MANAGEMENT
See ETSI TS 102 223 [32] clause 6.4.21.
6.4.22 SET UP IDLE MODE TEXT
See ETSI TS 102 223 [32] clause 6.4.22.
6.4.23 RUN AT COMMAND
See ETSI TS 102 223 [32] clause 6.4.23.
6.4.24 SEND DTMF
See ETSI TS 102 223 [32] clause 6.4.24.
6.4.25 LANGUAGE NOTIFICATION
See ETSI TS 102 223 [32] clause 6.4.25.
6.4.26 LAUNCH BROWSER
This command is used to request a browser inside a browser-enabled ME to interpret the content corresponding to a URL. See ETSI TS 102 223 [32] clause 6.4.26.
Upon receiving this command, the ME shall decide if it is able to execute the command. In addition to the examples given in ETSI TS 102 223 [32] clause 6.4.26 the following example applies:
– if the command is rejected because the ME is busy on a SS transaction, the ME informs the UICC using TERMINAL RESPONSE (ME unable to process command – ME currently unable to process command);
6.4.27 OPEN CHANNEL
6.4.27.1 OPEN CHANNEL related to CS bearer
This command is issued by the UICC to request a channel opening. The procedure is defined in ETSI TS 102 223 [32] clause 6.4.27.1, except when stated otherwise in the present document.
The UICC may request the use of an automatic reconnection mechanism according to TS 22.001 [22].
Upon receiving this command, the ME shall decide if it is able to execute the command. In addition to the examples given in ETSI TS 102 223 [32] clause 6.4.27.1 the following example applies:
– if the command is rejected because the ME is busy on a SS transaction, the ME informs the UICC using TERMINAL RESPONSE (ME unable to process command – currently busy on SS transaction). The operation is aborted.
The "Bearer description" provided in the command gives recommended values for parameters that the ME should use to establish the data link. However if the ME or network does not support these values, the ME selects the most appropriate values.
6.4.27.2 OPEN CHANNEL related to GPRS/UTRAN packet service/E-UTRAN/Satellite E-UTRAN/NG-RAN/Satellite NG-RAN
The procedures defined in ETSI TS 102 223 [32] clause 6.4.27.2 apply, understanding that:
– "packet data service" means GPRS, UTRAN packet service, E-UTRAN, Satellite E-UTRAN, NG-RAN or Satellite NG-RAN,
– "activation of packet data service" means activation of a PDP context or EPS PDN connection or PDU session.
The UICC provides to the terminal a list of parameters necessary to activate a packet data service. The UICC has three ways to indicate to the ME the QoS it requires:
– either use a Bearer Description called "Bearer description for GPRS/UTRAN Packet Service/E-UTRAN", which is valid for GPRS, UTRAN packet service, E-UTRAN and Satellite E-UTRAN.
– or use a Bearer Description called "Bearer description for UTRAN Packet Service with extended parameters and HSDPA" which is valid for a UTRAN packet service, HSDPA, E-UTRAN and Satellite E-UTRAN.
– or use a Bearer Description called "Bearer description for E-UTRAN and mapped UTRAN packet service", which is valid for UTRAN packet service, E-UTRAN and Satellite E-UTRAN.
For NG-RAN and Satellite NG-RAN, Quality of Service parameters are not applicable
Upon receiving this command, the ME shall decide if it is able to execute the command.
If the 3GPP PS data off status is "active", and the UE is not configured with indication that Bearer Independent Protocol is a 3GPP PS data off exempt service (see Annex S), then the ME shall send the TERMINAL RESPONSE (ME currently unable to process command) immediately. The operation is aborted.
In addition to the examples given in ETSI TS 102 223 [32] clause 6.4.27.2 the following example applies:
– if the command is rejected because the ME is busy on an SS transaction and unable to activate a PDP context in parallel with this SS transaction, the ME informs the UICC using TERMINAL RESPONSE (ME unable to process command – currently busy on SS transaction). The operation is aborted.
The "Bearer description" provided in the command gives recommended values for parameters that the ME should use to establish the data link. However if the ME or network does not support these values, the ME selects the most appropriate values.
If class "ai" is supported, the "Bearer description" provided in the command shall indicate a Non-IP PDP Type in order to establish a Non-IP data link. The UICC shall provide the Network Access Name data object.
6.4.27.3 OPEN CHANNEL related to local bearer
See ETSI TS 102 223 [32] clause 6.4.27.3.
6.4.27.4 OPEN CHANNEL related to Default (network) Bearer
See ETSI TS 102 223 [32] clause 6.4.27.4.
Additionally, if the 3GPP PS data off status is "active", and the UE is not configured with indication that Bearer Independent Protocol is a 3GPP PS data off exempt service (see Annex S), then the ME shall send the TERMINAL RESPONSE (ME currently unable to process command) immediately. The operation is aborted.
If class "ai" is supported, the "Bearer description" provided in the command shall indicate Non-IP PDP Type in order to establish a Non-IP data link. The UICC shall provide the Network Access Name data object.
6.4.27.5 OPEN CHANNEL related to (I-)WLAN bearer
This clause applies if class "e" is supported.
Upon receiving this command, the ME shall decide if it is able to execute the command. The UICC shall indicate whether the ME should establish the link immediately, in background mode or upon receiving the first transmitted data (on demand).
The UICC provides to the ME a list of parameters necessary to activate a (I-)WLAN service.
The ME shall attempt at least one (I-)WLAN service activation.
Upon receiving this command, the ME shall decide if it is able to execute the command. Examples are given below, but the list is not exhaustive:
– if immediate or background (I-)WLAN service activation is requested and the ME is unable to set-up a channel using the exact parameters provided by the UICC, the ME sets up the channel according to TS 24.234 [42] for a I-WLAN service activation or according to TS 24.302 [63] for a WLAN service activation and informs the UICC of the I-WLAN identifier or the WLAN identifier respectively and the modified parameters using TERMINAL RESPONSE (Command performed with modification);
– if immediate (I-)WLAN service activation is requested and the ME is unable to activate the I-WLAN service with the network using the exact parameters provided by the UICC, the ME informs the UICC using TERMINAL RESPONSE (Network currently unable to process command). The operation is aborted;
– if background mode (I-)WLAN service activation is requested and the ME is unable to activate the I-WLAN service with the network using the exact parameters provided by the UICC, the ME informs the UICC using a channel status event (link not established – no further info). The operation is aborted;
– if the command is rejected because the ME has no channel left with the requested bearer capabilities, the ME informs the UICC using TERMINAL RESPONSE (Bearer independent protocol error). The operation is aborted;
– if the user does not accept the channel set-up, the ME informs the UICC using TERMINAL RESPONSE (User did not accept the proactive command). The operation is aborted;
– if the user has indicated the need to end the proactive UICC session, the ME informs the UICC using TERMINAL RESPONSE (Proactive UICC session terminated by the user). The operation is aborted;
– if background mode (I-)WLAN service activation is requested, the ME allocates buffers, starts activation of (I-)WLAN service, informs the UICC and reports the channel identifier immediately using TERMINAL RESPONSE (Command performed successfully). At the end of activation, the ME shall send a channel status event (link established or link not established – no further info).
The ME shall inform the UICC that the command has been successfully executed using TERMINAL RESPONSE:
– if immediate (I-)WLAN service activation is requested, the ME allocates buffers, activates the (I-)WLAN service and informs the UICC and reports the channel identifier using TERMINAL RESPONSE (Command performed successfully);
– if on demand (I-)WLAN service activation is requested, the ME allocates buffers, informs the UICC and reports the channel identifier using TERMINAL RESPONSE (Command performed successfully).
If the ME is able to set up the channel on the serving network, the ME shall then enter the confirmation phase described hereafter; optionally, the UICC may include in this command an alpha-identifier. The use of this alpha-identifier by the ME is described below:
– if the alpha identifier is provided by the UICC and is not a null data object, the ME shall use it during the user confirmation phase. This is also an indication that the ME should not give any other information to the user during the user confirmation phase. If an icon is provided by the UICC, the icon indicated in the command may be used by the terminal to inform the user, in addition to, or instead of the alpha identifier, as indicated with the icon qualifier (see clause 6.5.4);
– if the alpha identifier is provided by the UICC and is a null data object (i.e. length = ’00’ and no value part), this is an indication that the ME should not give any information to the user or ask for user confirmation;
– if the alpha identifier is not provided by the UICC, the ME may give information to the user;
A terminal of type ND shall ignore any alpha identifier provided together with this command. The terminal shall respond with "command performed successfully" upon successful completion of the command. A terminal of type ND shall also ignore any icon provided together with this command. The terminal shall respond with "command performed successfully but requested icon could not be displayed" upon successful completion of the command.
– if the user doesn’t reject the channel, the ME shall then set up a channel. A terminal of type NK or type ND may not alert the user and may open the channel without explicit confirmation by the user;
– if the user does not accept the channel or rejects the channel, then the ME informs the UICC using TERMINAL RESPONSE (user did not accept the proactive command). The operation is aborted;
– if the user has indicated the need to end the proactive UICC session, the ME shall send a TERMINAL RESPONSE with (Proactive UICC session terminated by the user) result value;
– optionally, during packet data service activation, the ME can give some audible or display indication concerning what is happening;
– if the user stops the (I-)WLAN service activation attempt before a result is received from the network, the ME informs the UICC using TERMINAL RESPONSE (user cleared down call before connection or network release).
6.4.27.6 OPEN CHANNEL related to Terminal Server Mode
See ETSI TS 102 223 [32] clause 6.4.27.6.
6.4.27.7 OPEN CHANNEL related to UICC Server Mode
See ETSI TS 102 223 [32] clause 6.4.27.5.
6.4.27.8 OPEN CHANNEL for IMS
The following applies if classes "e" and "t" are supported.
After a successful registration to IMS specified in TS 24.229 [52] and after the ME has informed the UICC of this successful registration, the UICC may attempt to open a channel to communicate with the IMS.
The UICC will include in the OPEN CHANNEL for IMS command the IARI representing an active application installed on the UICC. This IARI shall be known to the ME and populated in the EFUICCIARI as specified in TS 31.102 [14].
The ME shall encapsulate all subsequent SIP communications intended for the IMS application running on the UICC. The ME shall decapsulate all subsequent messages received from the IMS application running on the UICC. Once the application is no longer available for SIP communications the UICC shall send the CLOSE CHANNEL command for the current channel ID.
If network conditions changed after a successful IMS registration, upon receiving this command, the ME shall decide if it is able to execute the command. If the ME is unable to process the command (the list is not exhaustive)
– if the command is unable to proceed due to the absence of an active IMS PDP/PDN context, the ME shall inform the UICC using the TERMINAL RESPONSE (network currently unable to process command) upon receipt of this failure cause, the UICC shall wait until the next IMS registration event before sending another OPEN CHANNEL for IMS command to the ME.
– if the command is unable to proceed due to the inability to contact IMS, the ME shall inform the UICC using the TERMINAL RESPONSE (network currently unable to process command) upon receipt of this failure cause, the UICC shall wait until the next IMS registration event before sending another OPEN CHANNEL for IMS command to the ME.
– If the command is unable to proceed because there is no channel available, the ME shall inform the UICC using the TERMINAL RESPONSE (Bearer Independent Protocol error – no channel available).
The ME shall inform the UICC that the command has been successfully executed using TERMINAL RESPONSE (Command performed successfully)
6.4.28 CLOSE CHANNEL
ETSI TS 102 223 [32] clause 6.4.28 applies, with the following addition.
In case of OPEN CHANNEL for IMS, the UICC shall send a CLOSE CHANNEL command to close the BIP channel at the end of the SIP dialog.
6.4.29 RECEIVE DATA
See ETSI TS 102 223 [32] clause 6.4.29.
6.4.30 SEND DATA
See ETSI TS 102 223 [32] clause 6.4.30.
6.4.31 GET CHANNEL STATUS
See ETSI TS 102 223 [32] clause 6.4.31.
6.4.32 SERVICE SEARCH
See ETSI TS 102 223 [32] clause 6.4.32.
6.4.33 GET SERVICE INFORMATION
See ETSI TS 102 223 [32] clause 6.4.33.
6.4.34 DECLARE SERVICE
See ETSI TS 102 223 [32] clause 6.4.34.
6.4.35 RETRIEVE MULTIMEDIA MESSAGE
See ETSI TS 102 223 [32] clause 6.4.37.
6.4.36 SUBMIT MULTIMEDIA MESSAGE
See ETSI TS 102 223 [32] clause 6.4.38.
6.4.37 DISPLAY MULTIMEDIA MESSAGE
See ETSI TS 102 223 [32] clause 6.4.39.
6.4.38 SET FRAMES
See ETSI TS 102 223 [32] clause 6.4.35.
6.4.39 GET FRAME STATUS
See ETSI TS 102 223 [32] clause 6.4.36.
6.4.40 Geographical Location Request
This clause applies if class "n" is supported.
This command requests an ME that is equipped with a positioning feature to report the location information of the ME within a specified quality of service.
As the determination of the geographical location information may take some time, the geographical location information report is sent by the ME to the UICC using the command ENVELOPE (Geographical Location Reporting). The ME reporting can be performed either in the format of GAD shapes defined in TS 23.032 [44] or in the format of NMEA sentences defined in IEC 61162-1 [45].
The horizontal coordinates represent the minimum set of information to be sent to the UICC (i.e. latitude and longitude). The UICC may request additional geographical location information (i.e. vertical coordinate and velocity). The UICC may request a preferred quality of service (e.g. preferred accuracy, preferred maximum response time). However if the ME does not support the requested preferred parameters, the ME selects the most appropriate quality of service parameters.
Upon receiving this command, the ME shall decide if it is able to execute the command. Examples are given below, but the list is not exhaustive:
– if the command is rejected because the ME is not equipped with a positioning feature, the ME informs the UICC using TERMINAL RESPONSE (Command beyond ME’s capabilities);
– if the command is rejected because the ME is currently unable to get the location information (e.g. due to lack of GPS coverage or due to a deactivated GPS receiver), the ME shall inform the UICC using TERMINAL RESPONSE (ME currently unable to process command);
If the ME is able to attempt to retrieve the geographical location information, the ME shall:
– inform the UICC that the command has been successfully executed, using TERMINAL RESPONSE.
– once the requested location information is available, the ME shall send this information to the UICC using the command ENVELOPE (Geographical Location Reporting).
– optionally, the UICC may include in this command an alpha-identifier. The use of this alpha-identifier by the ME is described below:
– if the alpha identifier is provided by the UICC and is not a null data object, the ME shall use it to inform the user. This is also an indication that the ME should not give any other information to the user on the fact that the ME is processing the location information request for the UICC. If an icon is provided by the UICC, the icon indicated in the command may be used by the ME to inform the user, in addition to, or instead of the alpha identifier, as indicated with the icon qualifier (see clause 6.5.4);
– if the alpha identifier is provided by the UICC and is a null data object (i.e. length = ’00’ and no value part), this is an indication that the ME should not give any information to the user on the fact that the ME is determining the location information for the UICC;
A terminal of type ND shall ignore any alpha identifier provided together with this command. The terminal shall respond with "command performed successfully" upon successful completion of the command. A terminal of type ND shall also ignore any icon provided together with this command. The terminal shall respond with "command performed successfully but requested icon could not be displayed" upon successful completion of the command.
– if the alpha identifier is not provided by the UICC, the ME may give information to the user concerning what is happening.
If the ME receives a "Geographical Location Request" command during the processing of a previous "Geographical Location Request" command (i.e. after the reception of a location request and before sending the "Geographical Location Reporting" ENVELOPE command), the latest location request shall be ignored.
6.4.41 ACTIVATE
Not required by 3GPP.
6.4.42 CONTACTLESS STATE CHANGED
Not required by 3GPP.
6.4.43 COMMAND CONTAINER
Not required by 3GPP.
6.4.44 ENCAPSULATED SESSION CONTROL
Not required by 3GPP.
6.5 Common elements in proactive UICC commands
See ETSI TS 102 223 [32] clause 6.5.
6.5.1 Command number
See ETSI TS 102 223 [32] clause 6.5.1.
6.5.2 Device identities
See ETSI TS 102 223 [32] clause 6.5.2.
6.5.3 Alpha identifier
See ETSI TS 102 223 [32] clause 6.5.3.
6.5.4 Icon identifiers
The display of icons is optional for the terminal on a per command basis, see ETSI TS 102 223 [32] clause 6.5.4.
6.5.5 Text attribute
See ETSI TS 102 223 [32] clause 6.5.5.
6.5.6 Frame identifier
See ETSI TS 102 223 [32] clause 6.5.6.
6.6 Structure of proactive UICC commands
The general structure of proactive UICC commands using TLV objects is described in annex C.
6.6.1 DISPLAY TEXT
See ETSI TS 102 223 [32] clause 6.6.1.
6.6.2 GET INKEY
See ETSI TS 102 223 [32] clause 6.6.2.
6.6.3 GET INPUT
See ETSI TS 102 223 [32] clause 6.6.3.
6.6.4 MORE TIME
See ETSI TS 102 223 [32] clause 6.6.4.
6.6.5 PLAY TONE
See ETSI TS 102 223 [32] clause 6.6.5.
6.6.6 POLL INTERVAL
See ETSI TS 102 223 [32] clause 6.6.6.
6.6.7 SET-UP MENU
See ETSI TS 102 223 [32] clause 6.6.7.
6.6.8 SELECT ITEM
See ETSI TS 102 223 [32] clause 6.6.8.
6.6.9 SEND SHORT MESSAGE
|
Description |
Clause |
M/O/C |
Min |
Length |
|
Proactive UICC command Tag |
9.2 |
M |
Y |
1 |
|
Length (A+B+C+D+E+F+G+H) |
– |
M |
Y |
1 or 2 |
|
Command details |
8.6 |
M |
Y |
A |
|
Device identities |
8.7 |
M |
Y |
B |
|
Alpha identifier |
8.2 |
O |
N |
C |
|
Address data object 1 |
8.1 or 8.108 |
O |
N |
D |
|
SMS TPDU (SMS-SUBMIT or SMS-COMMAND) |
8.13 |
M |
Y |
E |
|
Icon identifier |
8.31 |
O |
N |
F |
|
Text attribute |
8.70 |
C |
N |
G |
|
Frame Identifier |
8.82 |
O |
N |
H |
|
Address data object 2 |
8.108 |
C |
N |
I |
The address data object holds the RP_Destination_Address of the Service Centre. If no RP_Destination_Address is transferred, then the ME shall insert the default Service Centre address.
The address data object 1 may optionally hold the Public Service Identity of the SM-SC in URI format that the ME shall use to submit the SMS over IP as defined in 3GPP TS 24.341 [65].
In case Address data object 1 holds a Public Service Identity, the address data object 2 shall be present and holds the URI of the receiver of the short message. If the address data object 2 is present, the ME shall use the address data object 2 to submit the SMS over IP as defined in 3GPP TS 24.341 [65] clause 5.3.1.4.2.
When Address data object 2 is present, the UICC shall set the TP_Destination_Address field in the SMS TPDU to the dummy MSISDN value as specified in 24.341 [65].
The Text attribute applies to the Alpha Identifier. It may be present only if the Alpha Identifier is present.
6.6.10 SEND SS
|
Description |
Clause |
M/O/C |
Min |
Length |
|
Proactive UICC command Tag |
9.2 |
M |
Y |
1 |
|
Length (A+B+C+D+E+F+G) |
– |
M |
Y |
1 or 2 |
|
Command details |
8.6 |
M |
Y |
A |
|
Device identities |
8.7 |
M |
Y |
B |
|
Alpha identifier |
8.2 |
O |
N |
C |
|
SS string |
8.14 |
M |
Y |
D |
|
Icon identifier |
8.31 |
O |
N |
E |
|
Text attribute |
8.70 |
C |
N |
F |
|
Frame Identifier |
8.82 |
O |
N |
G |
The Text attribute applies to the Alpha Identifier. It may be present only if the Alpha Identifier is present.
6.6.11 SEND USSD
|
Description |
Clause |
M/O/C |
Min |
Length |
|
Proactive UICC command Tag |
9.2 |
M |
Y |
1 |
|
Length (A+B+C+D+E+F+G) |
– |
M |
Y |
1 or 2 |
|
Command details |
8.6 |
M |
Y |
A |
|
Device identities |
8.7 |
M |
Y |
B |
|
Alpha identifier |
8.2 |
O |
N |
C |
|
USSD String |
8.17 |
M |
Y |
D |
|
Icon identifier |
8.31 |
O |
N |
E |
|
Text attribute |
8.70 |
C |
N |
F |
|
Frame Identifier |
8.82 |
O |
N |
G |
The Text attribute applies to the Alpha Identifier. It may be present only if the Alpha Identifier is present.
6.6.12 SET UP CALL
|
Description |
Clause |
M/O/C |
Min |
Length |
|
Proactive UICC command Tag |
9.2 |
M |
Y |
1 |
|
Length (A+B+C+D+E+F+G+H+I+J+K+L+M+N) |
– |
M |
Y |
1 or 2 |
|
Command details |
8.6 |
M |
Y |
A |
|
Device identities |
8.7 |
M |
Y |
B |
|
Alpha identifier (user confirmation phase) |
8.2 |
O |
N |
C |
|
Address or IMS URI |
8.1 or 8.108 |
M |
Y |
D |
|
Capability configuration parameters |
8.4 |
O |
N |
E |
|
Subaddress |
8.3 |
O |
N |
F |
|
Duration |
8.8 |
O |
N |
G |
|
Icon identifier (user confirmation phase) |
8.31 |
O |
N |
H |
|
Alpha identifier (call set up phase) |
8.2 |
O |
N |
I |
|
Icon identifier (call set up phase) |
8.31 |
O |
N |
J |
|
Text Attribute (user confirmation phase) |
8.72 |
C |
N |
K |
|
Text Attribute (call set up phase) |
8.72 |
C |
N |
L |
|
Frame Identifier |
8.80 |
O |
N |
M |
|
Media Type |
8.132 |
O |
N |
N |
If the capability configuration parameters are not present, the ME shall assume the call is a speech call.
If the subaddress is not present, the ME shall not provide a called party subaddress to the network.
If the duration is not present, the UICC imposes no restrictions on the ME of the maximum duration of redials.
The Text Attribute (user confirmation phase) applies to the Alpha Identifier (user confirmation phase). The Text Attribute (call set up phase) applies to the Alpha identifier (call set up call phase). One Text Attribute may be present only if at least one Alpha Identifier is present. Both Text Attributes may be present only if both Alpha Identifiers are present. If only one Text Attribute data object is present, it shall apply to the first or unique Alpha identifier present in the command.
The IMS URI data object holds the SIP URI or tel URI, as defined in TS 24.229 [52], of the called party (if class "ae" is supported).
When the Media Type data object is present, it indicates the type of media the ME shall use, if supported by the ME to set up the communication. If the ME is unable to set up the call as requested, it shall return an error code reflecting the cause of the error. For example, in case of failure due to network constraints, the error code "Access Technology unable to process command" shall be used.
6.6.13 REFRESH
For all REFRESH modes except "Steering of Roaming", see ETSI TS 102 223 [32] clause 6.6.13.
For "Steering of Roaming":
|
Description |
Clause |
M/O/C |
Min |
Length |
|
Proactive UICC command Tag |
9.2 |
M |
Y |
1 |
|
Length (A+B+C+D+E+F+G+H) |
– |
M |
Y |
1 or 2 |
|
Command details |
8.6 |
M |
Y |
A |
|
Device identities |
8.7 |
M |
Y |
B |
|
Alpha identifier |
8.2 |
O |
N |
C |
|
Icon identifier |
8.31 |
O |
N |
D |
|
Text Attribute |
8.70 |
C |
N |
E |
|
Frame Identifier |
8.82 |
O |
N |
F |
|
PLMNwAcT List |
8.90 |
C (see Note 1) |
N |
G |
|
PLMN List |
8.97 |
C (see Note 2) |
N |
H |
|
SOR-CMCI |
8.146 |
O (see Note 3) |
N |
I |
|
Note 1: This parameter is required in case of steering of roaming (according to TS 23.122 [7]). Note 2: This parameter is required in case of steering of roaming for I-WLAN (according to TS 24.234 [42]). Note 3: This parameter may be optionally present in case of steering of roaming SOR-CMCI (according to TS 23.122 [7]]). |
||||
The Text attribute applies to the Alpha Identifier. It may be present only if the Alpha Identifier is present.
6.6.14 POLLING OFF
See ETSI TS 102 223 [32] clause 6.6.14.
6.6.15 PROVIDE LOCAL INFORMATION
|
Description |
Clause |
M/O/C |
Min |
Length |
|
Proactive UICC command Tag |
9.2 |
M |
Y |
1 |
|
Length (A+B+C) |
– |
M |
Y |
1 or 2 |
|
Command details |
8.6 |
M |
Y |
A |
|
Device Identities |
8.7 |
M |
Y |
B |
|
UTRAN/E-UTRAN/Satellite E-UTRAN/NG-RAN/Satellite NG-RAN Measurement Qualifier |
8.73 |
C |
N |
C |
UTRAN/E-UTRAN/Satellite E-UTRAN/NG-RAN/Satellite NG-RAN Measurement Qualifier: This data object applies when the Command Qualifier in Command details is set to indicate "Network Measurement results". It shall be included to indicate to the ME that "Network Measurement Results for a UTRAN" or "Network Measurement Results for a E-UTRAN and Satellite E-UTRAN" or "Network Measurement Results for a NG-RAN and Satellite NG-RAN " is required. It shall be excluded to indicate to the ME that "Network Measurement Results for a GERAN" is required. It shall only be included/excluded if the ME has indicated that it supports the implied access technology via the respective Terminal Profile setting.
6.6.16 SET UP EVENT LIST
See ETSI TS 102 223 [32] clause 6.6.16.
6.6.17 PERFORM CARD APDU
See ETSI TS 102 223 [32] clause 6.6.17.
6.6.18 POWER OFF CARD
See ETSI TS 102 223 [32] clause 6.6.18.
6.6.19 POWER ON CARD
See ETSI TS 102 223 [32] clause 6.6.19.
6.6.20 GET READER STATUS
See ETSI TS 102 223 [32] clause 6.6.20.
6.6.21 TIMER MANAGEMENT
See ETSI TS 102 223 [32] clause 6.6.21.
6.6.22 SET UP IDLE MODE TEXT
See ETSI TS 102 223 [32] clause 6.6.22.
6.6.23 RUN AT COMMAND
See ETSI TS 102 223 [32] clause 6.6.23.
6.6.24 SEND DTMF COMMAND
See ETSI TS 102 223 [32] clause 6.6.24.
6.6.25 LANGUAGE NOTIFICATION
See ETSI TS 102 223 [32] clause 6.6.25.
6.6.26 LAUNCH BROWSER
See ETSI TS 102 223 [32] clause 6.6.26.
6.6.27 OPEN CHANNEL
The structure of the OPEN CHANNEL command is defined in ETSI TS 102 223 [32] clause 6.6.27. , with the addition of the following:
6.6.27.1 OPEN CHANNEL related to (I-)WLAN Bearer
|
Description |
Clause |
M/O/C |
Min |
Length |
|
Proactive UICC command Tag |
9.2 |
M |
Y |
1 |
|
Length (A+B+C+D+E+F+G+H+I+J+K+L) |
– |
M |
Y |
1 or 2 |
|
Command details |
8.6 |
M |
Y |
A |
|
Device identities |
8.7 |
M |
Y |
B |
|
Alpha identifier |
8.2 |
O |
N |
C |
|
Icon identifier |
8.31 |
O |
N |
D |
|
Bearer description |
8.52 |
M |
Y |
E |
|
Buffer size |
8.55 |
M |
Y |
F |
|
I-WLAN Identifier |
8.83 |
O |
N |
G |
|
Other address (local address) |
8.58 |
O |
N |
H |
|
UICC/terminal interface transport level |
8.59 |
O |
N |
I |
|
Data destination address |
8.58 |
C |
Y |
J |
|
Text Attribute |
8.72 |
C |
N |
K |
|
Frame Identifier |
8.82 |
O |
N |
L |
When OPEN CHANNEL is related to I-WLAN bearer:
– The I-WLAN Identifier may be requested.
– If the parameter is not present, the ME shall select the I-WLAN according to TS 24.234 [42] using the Automatic PLMN Selection Mode Procedure.
When OPEN CHANNEL is related to WLAN bearer, the ME shall select the WLAN according to TS 24.302 [63] using the automatic mode WLAN selection procedure and ignore the I-WLAN Identifier, if provided.
The local address parameter provides information to the ME necessary to identify the local device. If the parameter is present and length is not null, it provides an IP address that identifies the USAT application in the address area applicable to the PDN. If local address length is null, dynamic local address allocation is required for the USAT application. If parameter is not present, the ME may use the ME default local address configuration.
If the UICC/ME interface transport level is present in the command, then the ME shall provide the requested transport layer protocols under the channel and shall use this object containing a set of parameters required to make the transport connection. The data that is exchanged at the UICC/ME interface in the RECEIVE DATA/SEND DATA commands are SDUs. When the USAT application sends an SDU, the transport layer within the ME is in charge to add the transport header to the SDU in order to build the Transport-PDU. When the USAT application requests to receive an SDU, the transport layer within the ME is in charge to remove the transport header of the Transport-PDU, and to forward the SDU to the USAT. If the parameter is not present, the UICC/ME interface is the bearer level (serial link or packet link), and the USAT application is in charge of the network and transport layer.
The Data destination address is the end point destination address of sent data. This data destination address is requested when a UICC/ME interface transport is present, otherwise it is ignored. The data destination address is a data network address (e.g. IP address).
Text Attribute applies to the Alpha Identifier. It may be present only if the Alpha Identifier is present.
6.6.27.2 OPEN CHANNEL for IMS
|
Description |
Clause |
M/O/C |
Min |
Length |
|
Proactive UICC command Tag |
9.2 |
M |
Y |
1 |
|
Length (A+B+C+D) |
– |
M |
Y |
1 or 2 |
|
Command details |
8.6 |
M |
Y |
A |
|
Device identities |
8.7 |
M |
Y |
B |
|
Buffer size |
8.55 |
M |
Y |
C |
|
IARI |
8.110 |
M |
Y |
D |
6.6.28 CLOSE CHANNEL
See ETSI TS 102 223 [32] clause 6.6.28.
6.6.29 RECEIVE DATA
See ETSI TS 102 223 [32] clause 6.6.29.
6.6.30 SEND DATA
See ETSI TS 102 223 [32] clause 6.6.30.
6.6.31 GET CHANNEL STATUS
See ETSI TS 102 223 [32] clause 6.6.31.
6.6.32 SERVICE SEARCH
See ETSI TS 102 223 [32] clause 6.6.32.
6.6.33 GET SERVICE INFORMATION
See ETSI TS 102 223 [32] clause 6.6.33.
6.6.34 DECLARE SERVICE
See ETSI TS 102 223 [32] clause 6.6.34.
6.6.35 RETRIEVE MULTIMEDIA MESSAGE
See ETSI TS 102 223 [32] clause 6.6.37.
6.6.36 SUBMIT MULTIMEDIA MESSAGE
See ETSI TS 102 223 [32] clause 6.6.38.
6.6.37 DISPLAY MULTIMEDIA MESSAGE
See ETSI TS 102 223 [32] clause 6.6.39.
6.6.38 SET FRAMES
See ETSI TS 102 223 [32] clause 6.6.35.
6.6.39 GET FRAMES STATUS
See ETSI TS 102 223 [32] clause 6.6.36.
6.6.40 Geographical Location Request
|
Description |
Clause |
M/O/C |
Min |
Length |
|
Proactive UICC command Tag |
9.2 |
M |
Y |
1 |
|
Length (A+B+C+D+E) |
– |
M |
Y |
1 or 2 |
|
Command details |
8.6 |
M |
Y |
A |
|
Device Identities |
8.7 |
M |
Y |
B |
|
Alpha identifier |
8.2 |
O |
N |
C |
|
Icon identifier |
8.31 |
O |
N |
D |
|
Geographical Location Parameters |
8.94 |
M |
N |
E |
6.6.41 ACTIVATE
Not required by 3GPP.
6.6.42 CONTACTLESS STATE CHANGED
Not required by 3GPP.
6.6.43 COMMAND CONTAINER
Not required by 3GPP.
6.6.44 ENCAPSULATED SESSION CONTROL
Not required by 3GPP.
6.7 Command results
Once the ME has made its attempt to execute a proactive command from the UICC, the ME shall inform the UICC of the success or otherwise of that command, by using TERMINAL RESPONSE.
This procedure is defined in ETSI TS 102 223 [32] clause 6.7, and applies here except for the following statements.
Temporary problems are defined as:
– ME is currently unable to process the command. Specific causes for this are listed in ETSI TS 102 223 [32] clause 6.7; in addition to these, the following causes may be returned within the USAT context:
– ME currently busy on SS transaction;
– ME currently busy on USSD operation;
– access control class barred on serving network;
– if none of these can be made to apply, a "no cause can be given" value can be used;
– network is currently unable to process the command. Within the USAT context, specific cause values are the cause values given by the network, as defined in TS 24.008 [9];
– in some proactive commands, the ME is required to solicit and receive approval of the user before executing the proactive command. In the case that the user does not give approval for the execution of the proactive command, it shall not be executed by the ME and the terminal response "user did not accept the proactive command" shall be returned by the ME to the UICC;
– the user cleared down the call, before the call connected (CONNECT received from network, as defined in TS 24.008 [9]) or before the network released the call;
– action in contradiction with the current timer state. This is where the UICC requests an action for a timer to be taken by the ME and the state of the timer does not allow that action;
– interaction with call control by USIM, temporary problem. This is sent by the ME to indicate that call control modified the type of request indicated in the proactive command, and that the action requested by call control encounters a temporary problem.
Permanent problems are defined as in ETSI TS 102 223 [32] clause 6.7, with the addition of:
– SS Return Error. This is given to the UICC when the network returns a SS error in response to a previous SS command. Specific cause values are the same as given by the network in the Return Error message;
– USSD Return Error. This is given to the UICC when the network returns a USSD error in response to a previous USSD command. Specific cause values are the same as given by the network in a Return Error message;
– SMS RP-ERROR. This is given to the UICC when the network returns an error in response to the ME trying to send a short message. Specific cause values are the same as the cause value of RP‑Cause in an RP-ERROR message;
– interaction with MO short message control by USIM, permanent problem. This is sent by the ME to indicate that:
MO short message control by USIM does not allow the action corresponding to the proactive command; or
MO short message control by USIM has modified the type of request indicated in the proactive command and that the action requested by call control encounters a permanent problem.
6.8 Structure of TERMINAL RESPONSE
6.8.0 Overall structure of TERMINAL RESPONSE
Direction: ME to UICC.
The command header is specified in TS 31.101 [13]. Length (A+B+ … +AE) 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 |
Z |
|
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 |
C |
N |
AE or AE0 + … + AEn |
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
See ETSI TS 102 223 [32] clause 6.8.1.
6.8.2 Device identities
See ETSI TS 102 223 [32] clause 6.8.2.
6.8.3 Result
See ETSI TS 102 223 [32] clause 6.8.3.
6.8.4 Duration
See ETSI TS 102 223 [32] clause 6.8.4.
6.8.5 Text string
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
See ETSI TS 102 223 [32] clause 6.8.6.
6.8.7 Local information
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 [38].
– for E-UTRAN and Satellite E-UTRAN: The Network Measurement Results are coded as the MeasurementReport message defined in TS 36.331 [49]
– for NG-RAN or Satellite NG-RAN: The Network Measurement Results are coded as the MeasurementReport message defined in TS 38.331 [71]
– 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 slices information data object listing all slice(s) information, up to the limit of the TERMINAL RESPONSE APDU command size. If no slice information is available, the respective data object shall have length zero.
– Where the UICC has requested the CAG information list, the TERMINAL RESPONSE shall contain the CAG information list and the corresponding 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).
6.8.8 Call control requested action
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
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
See ETSI TS 102 223 [32] clause 6.8.10.
6.8.11 Card ATR
See ETSI TS 102 223 [32] clause 6.8.11.
6.8.12 R-APDU
See ETSI TS 102 223 [32] clause 6.8.12.
6.8.13 Timer identifier
See ETSI TS 102 223 [32] clause 6.8.13.
6.8.14 Timer value
See ETSI TS 102 223 [32] clause 6.8.14.
6.8.15 AT Response
See ETSI TS 102 223 [32] clause 6.8.15.
6.8.16 Text string 2
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
See ETSI TS 102 223 [32] clause 6.8.17.
6.8.18 Channel status
See ETSI TS 102 223 [32] clause 6.8.18.
6.8.19 Channel data length
See ETSI TS 102 223 [32] clause 6.8.19.
6.8.20 Bearer description
See ETSI TS 102 223 [32] clause 6.8.20.
6.8.21 Buffer size
See ETSI TS 102 223 [32] clause 6.8.21.
6.8.22 Total Display Duration
See ETSI TS 102 223 [32] clause 6.8.22.
6.8.23 Service Availability
See ETSI TS 102 223 [32] clause 6.8.23.
6.8.24 Service Record
See ETSI TS 102 223 [32] clause 6.8.24.
6.8.25 Other address (local address)
See ETSI TS 102 223 [32] clause 6.8.25.
6.8.26 Frames Information
See ETSI TS 102 223 [32] clause 6.8.26.
6.9 Proactive UICC session and ME display interaction
See ETSI TS 102 223 [32] clause 6.9.
6.10 Handling of unknown, unforeseen and erroneous messages
See ETSI TS 102 223 [32] clause 6.10.
6.11 Proactive commands versus possible Terminal response
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.
Table 6.1: Proactive commands versus possible terminal response
|
PROACTIVE COMMAND |
||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
SET UP CALL |
SEND SS |
SEND USSD |
SEND SMS |
Geographical Location Request |
||||||
|
TERMINAL RESPONSE |
’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) |
|||||||||