Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TS 31.102  Word version:  17.1.0

Top   Top   Up   Prev   Next
0…   3…   4…   4.2.9…   4.2.17…   4.2.26…   4.2.34…   4.2.44…   4.2.52…   4.2.60…   4.2.68…   4.2.76…   4.2.85…   4.2.93…   4.2.101…   4.2.107…   4.3…   4.4.2…   4.4.2.4…   4.4.3…   4.4.4…   4.4.5…   4.4.6…   4.4.8…   4.4.8.7…   4.4.9…   4.4.11…   4.4.11.7…   4.5…   4.6…   4.7   5…   5.2   5.3   5.4…   5.9…   6…   7…   7.1.2…   7.3…   A   B…   D   E…   G   H…   I…   L…   M…

 

5.4  USAT related proceduresWord‑p. 254

5.4.1  Data Download via SMS-PP

Requirement:
USIM Service No. 28 "available".
The procedures and commands for Data Download via SMS-PP are defined in TS 31.111.

5.4.2  Image Request

The terminal sends the identification of the information to be read. The terminal shall analyse the data of EF IMG to identify the files containing the instances of the image. If necessary, then the terminal performs READ BINARY commands on these files to assemble the complete image instance data.

5.4.3  Data Download via SMS-CB

Requirement:
USIM Service No. 29 "available".
The ME shall perform the reading procedure with EF CBMID, and add the message identifiers to the Cell Broadcast search list. On receiving a cell broadcast message the procedure defined in TS 31.111 applies.

5.4.4  Call Control by USIM

Requirement:
USIM Service No. 30 "available".
The procedures and commands for Call Control by USIM are defined in TS 31.111. It is mandatory for the ME to perform the procedures if it has indicated that it supports Call Control by USIM in the TERMINAL PROFILE command.

5.4.5  MO-SMS control by USIM

Requirement:
USIM Service No. 31 "available".
The procedures and commands for MO-SMS control by USIM are defined in TS 31.111. It is mandatory for the ME to perform the procedures if it has indicated that it supports MO-SMS control by USIM in the TERMINAL PROFILE command.

5.4.6  Data Download via USSD and USSD application mode |R6|

Requirement:
Service No. 70 "available".
The procedures and commands for Data Download via USSD and USSD application mode are defined in TS 31.111.

5.4.7  Additional TERMINAL PROFILE after UICC activation |R6|

Requirement:
USIM Service No. 72 "available".
The procedures and commands for Additional TERMINAL PROFILE after UICC activation are defined in TS 31.111 and allow the ME to send multiple Terminal Profile downloads.

5.4.8  Terminal Applications |R8|

Requirement:
Service No. 77 "available"
The procedures and commands for "Terminal Applications" are defined in TS 31.111

5.4.9  Call control on EPS PDN connection by USIM |R8|Word‑p. 255
Requirement:
USIM Service No. 87 "available".
The procedures and commands for Call control on EPS PDN connection by USIM are defined in TS 31.111.

5.4.10  Communication Control for IMS by USIM |R10|

Requirement:
USIM Service No. 93 "available".
The procedures and commands for Communication Control for IMS by USIM are defined in TS 31.111. It is mandatory for the ME to perform the procedures if it has indicated that it supports Communication Control for IMS by USIM in the TERMINAL PROFILE command.

5.4.11  USAT Facility Control |R10|

Requirement:
The ME supports the USAT over AT feature specified in TS 31.111.
Request:
The ME performs the reading procedures of EF UFC.

5.4.12  Extended Terminal Applications |R10|

Requirement:
Service No. 77 and No. 94 "available"
The procedures and commands for "Extended Terminal Applications" are defined in TS 31.111.

5.4.13  USAT application pairing procedure |R12|

The use of a USIM can be restricted to specific MEs using the USAT Application Pairing procedure and information stored in the USIM as specified in this specification and defined in TS 33.187.
To support the USAT Application Pairing procedure, the ME shall support USAT PROVIDE LOCAL INFORMATION command (IMEI or IMEISV), as specified in TS 31.111.
USAT Application Pairing is successful when the IMEI or IMEISV retrieved from the terminal belongs to a range of values the UICC is configured with in EF IAL.
EF IAL, EF IPS, EF IPD are defined in this document to support this procedure.
If the service No. 102 is "available" in the USIM Service Table, the UICC shall start the UICC proactive session immediately after TERMINAL PROFILE and the first proactive command shall be PROVIDE LOCAL INFORMATION with IMEI or IMEISV. The ME shall respond with TERMINAL RESPONSE with IMEI or IMEISV before performing any AUTHENTICATE command.
The UICC shall respond to any AUTHENTICATE command with error status words SW1 SW2 = '69 85' if:
  • IMEI or IMEISV provided by the ME is not in the corresponding allowed list configured in the USIM (EF IAL)
  • ME has not provided any IMEI
If the AUTHENTICATE command had been executed before the pairing procedure has been successfully performed (in the case of pre-Rel-12 MEs), the UICC may need to trigger a network attachment procedure by sending a proactive command REFRESH(3G SESSION RESET).
Up

5.4.14  Call control on PDU Session by USIM |R15|

Requirement:
USIM Service No. 128 "available".
The procedures and commands for Call control on PDU Session by USIM are defined in TS 31.111.

5.5  MexE related proceduresWord‑p. 256
MexE is an optional feature. The higher level procedures, and contents and coding of the commands are given in TS 23.057. Procedures relating to the transmission of commands and responses across the USIM/ME interface are given in this clause. A USIM or ME supporting MexE shall conform to the requirements given in this clause.

5.5.1  MexE ST

Requirement:
Service No. 41 (MexE) "available".
Request:
The ME performs the reading procedure with EF MexE-ST

5.5.2  Operator root public key

Requirement:
Service No. 41 (MexE) "available" and MexE ST service No. 1 (EF ORPK) "available".
Request:
The ME performs the reading procedure with EF ORPK. The ME shall analyse the data of EF ORPK (clause 4.4.1.4.2) to identify the files containing the certificate instances. If necessary, then the ME performs READ BINARY commands on these files to assemble the complete certificate instance data.
Up

5.5.3  Administrator root public key

Requirement:
Service No. 41 (MexE) "available" and MexE ST service No. 2 (EF ARPK) "available".
Request:
The ME performs the reading procedure with EF ARPK. The ME shall analyse the data of EF ARPK (clause ;4.4.1.4.3) to identify the file containing the certificate instance. If necessary, then the ME performs READ BINARY commands on this file to assemble the complete certificate instance data.
Up

5.5.4  Third Party root public key(s)

Requirement:
Service No. 41 (MexE) "available" and MexE ST service No. 3 (EF TPRPK) "available".
Request:
The ME performs the reading procedure with EF TPRPK. The ME shall analyse the data of EF TPRPK (clause 4.4.1.4.4) to identify the files containing the certificate instances. If necessary, then the ME performs READ BINARY commands on these files to assemble the complete certificate instance data.
Up

5.5.5  Trusted Key/Certificates Data Files

Requirement:
Service No. 41 (MexE) "available".
Request:
The ME performs the reading procedure with EF TKCDF. The ME shall analyse the data of EF TKCDF and, if necessary, perform READ BINARY commands on these files

5.6  WLAN related procedures |R6|

5.6.1  WLAN Selection related Procedures

Requirement:
service No. 62 or No. 63 or No. 81 or No. 82 or No. 83 or No. 84 or No. 88 "available"
The ME shall read the User, Home and Operator controlled WSIDs, the I-WLAN Equivalent HPLMN Presentation Indication, I-WLAN HPLMN Priority Indication, the I-WLAN Last Registered PLMN and the HPLMN Direct Access Indicationfrom the corresponding list files (i.e. EF UWSIDL, EF HWSIDL, EF OWSIDL, EF WEHPLMNPI , EF WLRPLMN, EF WHPI and EFHPLMDAI)to perform WLAN selection procedures as described in TS 24.234.
The user may change the User controlled WSIDs.
Up

5.6.2  WLAN PLMN Selection related proceduresWord‑p. 257
Requirement:
service No. 60 or No. 61 "available"
The ME shall read the User controlled PLMN selector and/or Operator controlled PLMN selector in EF UPLMNWLAN and EF OPLMNWLAN respectively for WLAN PLMN Selection procedures as described in TS 24.234.
The user may change the User controlled PLMN selector for WLAN.
Up

5.6.3  WLAN access authentication related procedures

Requirement:
service No. 59 "available"
When the ME tries a full authentication, it shall inspect if a valid Pseudonym is available in EF Pseudo.and use it as the user name portion of the NAI for WLAN access authentication following the procedures described in TS 24.234.
The ME shall manage pseudonyms as defined in TS 24.234.
Up

5.6.4  WLAN access re-authentication related procedures

Requirement:
service No. 66 "available"
When the ME tries a fast re-authentication, it shall inspect if a valid reauthentication identity is available in EF WRI and use it as the user name portion of the NAI for WLAN access re-authentication following the procedures described in TS 24.234.
The ME shall manage re-authentiction identities, Master Key and counter values as described in TS 24.234.
Up

5.7  Network Connectivity Parameters for UICC IP connections related procedures |R8|

The EF NCP-IP access procedures are described in ETSI TS 102 483 [50].
Requirement:
Service No. 80 is "available"
Request:
The terminal performs the read procedure with EF NCP-IP before establishing a remote data link for UICC remote IP connectivity as described in ETSI TS 102 483 [50].
Refresh:
The terminal performs the refresh procedure with EF NCP-IP.
Up

5.8  H(e)NB related procedures |R8|

5.8.1  CSG Access Control procedures

Requirement:
Service No. 86 is "available"
Request:
The terminal performs the read procedure with EF ACSGL.
Update:
The terminal performs the updating procedure with EF ACSGL
The ME shall read the allowed CSG Ids from EF ACSGL in order to perform H(e)NB selection procedures. The lists in EF ACSGL shall take precedence over the list stored in the ME non-volatile memory.
Requirement:
Service No. 90 is "available"
Request:
The terminal performs the read procedure with with EF OCSGL.
The ME shall read the Operator CSG Ids from EF OCSGL in order to perform H(e)NB selection procedures. The list in EF OCSGL shall take precedence over the list stored in the ME non-volatile memory.
Requirement:
Service No. 92 is "available"
In case of a manual CSG cell selection, the ME shall read EF AD and CSG Lists Display Indicators from EF OCSGL and display CSG Ids accordingly. The configuration in EF OCSGL shall take precedence over the configuration stored in the ME non-volatile memory.
If service No. 92 is not "available", in case of a manual CSG cell selection, all available CSGs may be displayed without any restriction.
Up

5.8.2  CSG Type related proceduresWord‑p. 258
Requirement:
Service No. 86 is "available"
Request:
The terminal performs the read procedure with EF ACSGL and EF CSGT.
Update:
The terminal performs the updating procedure with EF ACSGL
The ME shall discover the association between the selected CSG ID and a CSG Type from EF ACSGL. If this association exists, the provided CSG Type shall be displayed.
Requirement:
Service No. 90 is "available"
Request:
The terminal performs the read procedure with EF OCSGL and EF OCSGT.
The ME shall discover the association between the selected CSG ID and either a CSG Type from EF ACSGL or an Operator CSG Type from EF OCSGL. The Operator CSG Type has precedence.
Up

5.8.3  HNB name display related procedures

Requirement:
Service No. 86 is "available"
Request:
The terminal performs the read procedure with EF ACSGL and EF HNBN.
Update: The terminal performs the updating procedure with EF ACSGL and EF HNBN.
The ME shall discover the association between the selected CSG ID and a HNB name from EF ACSGL. If this association exists, the provided HNB name shall be displayed.
Requirement:
Service No. 90 is "available"
Request:
The terminal performs the read procedure with EF OCSGL and EF OHNBN.
The ME shall discover the association between the selected CSG ID and either a HNB Name from EF ACSGL or an Operator HNB from EF OCSGL. The Operator HNB Name has precedence. If this association exists, the HNB Name shall be displayed.
Requirement:
Service No. 92 is "available"
In case of a manual CSG cell selection, the ME shall read EF AD and the CSG Lists Display Indicators from EF OCSGL and display HNB Name accordingly. The configuration in EF OCSGL shall take precedence over the configuration stored in the ME non-volatile memory.
If service No. 92 is not "available", in case of a manual CSG cell selection, all available CSGs may be displayed without any restriction.
Up

Up   Top   ToC