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.3  Subscription related procedures

5.3.1  Phone book procedures

5.3.1.1  Initialisation

The ME first reads the content of EF PBR to determine the configuration phonebook. If the EF IAP file is indicated in EF PBR following tag 'A8' the ME reads the content of EF IAP in order to establish the relation ship between the content in the files indicated using tag 'A9' and files indicated by tag 'A8'. The ME may read the contents of the phone book related files in any order.
Up

5.3.1.2  Creation/Deletion of information

In order to avoid unlinked data to introduce fragmentation of the files containing phone book data the following procedures shall be followed when creating a new entry in the phone book. The data related to EF ADN is first stored in the relevant record. As the record number is used as a pointer the reference pointer is now defined for the entry. The rule for storing additional information for an entry is that the reference pointer shall be created before the actual data is written to the location.
In case of deletion of a complete or part of an entry the data shall be deleted first followed by the reference pointer for that data element. In case of deletion of a complete entry the contents of EF ADN is the last to be deleted.
Up

5.3.1.3  Hidden phone book entries

If a phone book entry is marked as hidden by means of EF PBC the ME first prompts the user to enter the 'Hidden Key'. The key presented by the user is compared against the value that is stored in the corresponding EF Hiddenkey. Only if the presented and stored hidden key are identical the ME displays the data stored in this phone book entry. Otherwise the content of this phone book entry is not displayed by the ME.
Even if the terminal does not support the Hidden Key Procedures, a hidden phone book entry shall not be displayed by the terminal.
Request:
The ME performs the reading procedure with EF Hiddenkey.
Update:
The ME performs the updating procedure with EF Hiddenkey.
Up

5.3.2  Dialling numbersWord‑p. 243
Requirements:
The following procedures may not only be applied to EF ADN and its associated extension files EF CCP1 and EFEXT1 as described in the procedures below, but also to EF ANR, EF FDN, EF MSISDN, EF BDN, EF SDN, EF OCI, EF ICI, and EF MBDN and their associated extension files. If these files are not "available", as denoted in the USIM service table, the current procedure shall be aborted and the appropriate EFs shall remain unchanged.
As an example, the following procedures are described as applied to ADN.
Update: The ME analyses and assembles the information to be stored as follows (the byte identifiers used below correspond to those in the definition of the relevant EFs in the present document):
  1. The ME identifies the Alpha-tagging, Capability/Configuration1 Record Identifier and Extension1 Record Identifier.
  2. The dialling number/SSC string shall be analysed and allocated to the bytes of the EF as follows:
    • if a "+" is found, the TON identifier is set to "International";
    • if 20 or less "digits" remain, they shall form the dialling number/SSC string;
    • if more than 20 "digits" remain, the procedure shall be as follows:
    • The ME seeks for a free record in EFEXT1. If an Extension1 record is not marked as "free", the ME runs the Purge procedure. If an Extension1 record is still unavailable, the procedure is aborted.
    • The first 20 "digits" are stored in the dialling number/SSC string. The value of the length of BCD number/SSC contents is set to the maximum value, which is 11. The Extension1 record identifier is coded with the associated record number in the EFEXT1. The remaining digits are stored in the selected Extension1 record where the type of the record is set to "additional data". The first byte of the Extension1 record is set with the number of bytes of the remaining additional data. The number of bytes containing digit information is the sum of the length of BCD number/SSC contents of EF ADN and byte 2 of all associated chained Extension1 records containing additional data.
  3. If a called party subaddress is associated to the ADN/SSC the procedure shall proceed as follows:
    • If the length of the called party subaddress is less than or equal to 11 bytes (see TS 24.008 for coding):
    • The ME seeks for a free record in EFEXT1. If an Extension1 record is not marked as "free", the ME runs the Purge procedure. If an Extension1 record is still unavailable, the procedure is aborted.
    • The ME stores the called party subaddress in the Extension1 record, and sets the Extension1 record type to "called party subaddress".
    • If the length of the called party subaddress is greater than 11 bytes (see TS 24.008 for coding):
    • The ME seeks for two free records in EFEXT1. If no such two records are found, the ME runs the Purge procedure. If two Extension1 records are still unavailable, the procedure is aborted.
    • The ME stores the called party subaddress in the two Extension1 records. The identifier field in the Extension1 record containing the first part of the subaddress data is coded with the associated EFEXT1 record number containing the second part of the subaddress data. Both Extension1 record types are set to "called party subaddress".
Once i), ii), and iii) have been considered the ME performs the updating procedure with EF ADN. If the USIM has no available empty space to store the received ADN/SSC, or if the procedure has been aborted, the ME advises the user.
For reasons of memory efficiency, the ME may analyse all Extension1 records to recognise if the additional or subaddress data to be stored is already existing in EFEXT1. In this case, the ME may use the existing chain or the last part of the existing chain from more than one ADN. The ME is only allowed to store extension data in unused records. If existing records are used for multiple access, the ME shall not change any data in those records to prevent corruption of existing chains.
Erasure:
The ME sends the identification of the information to be erased. The content of the identified record in EF ADN is marked as "free".
Request:
The ME sends the identification of the information to be read. The ME shall analyse the data of EF ADN to ascertain, whether additional data is associated in EFEXT1 or EF CCP1. If necessary, then the ME performs the reading procedure on these EFs to assemble the complete ADN/SSC.
Purge:
The ME shall access each EF which references EFEXT1 (EF EXT2, EF EXT6) for storage and shall identify records in these files using extension data (additional data or called party subaddress). Note that existing chains have to be followed to the end. All referred Extension1 (Extension2, Extension6) records are noted by the ME. All Extension1 (Extension2, Extension6) records not noted are then marked by the ME as "free" by setting the whole record to 'FF'.
The following three procedures are only applicable to service No. 2 (FDN).
  • FDN capability request. The ME shall check the state of service No. 2, i.e. if FDN is "enabled" or "disabled". If FDN is enabled, the ME shall only allow outgoing calls as defined in the fixed number dialling description in TS 22.101. To ascertain the state of FDN, the ME shall check in EF UST and EF EST if FDN is enabled (service activated and available). In all other cases service No. 2 is disabled.
  • FDN enabling is done by activating the FDN service in EF EST.
  • FDN disabling is done by deactivating the FDN service in EF EST.
The following three procedures are only applicable to service No. 6 (BDN).
  • BDN capability request. The ME shall check the state of service No. 6, i.e. if BDN is "enabled" or "disabled". To ascertain the state of BDN, the ME shall check in EF UST and EF EST if BDN is "enabled" (service available and activated). In all other cases, the BDN service is "disabled".
  • BDN enabling is done by activating the BDN service in EF EST.
  • BDN disabling is done by deactivating the BDN service in EF EST.
Up

5.3.3  Short messagesWord‑p. 244
Requirement:
Service No. 10 "available".
Request:
The USIM seeks for the identified short message. If this message is found, the ME performs the reading procedure with EF SMS.
If service No. 10 is "available" and the status of the SMS is '1D' (status report requested, received and stored in EF SMSR), the ME performs the reading procedure with the corresponding record in EF SMSR. If the ME does not find a corresponding record in EF SMSR, then the ME shall update the status of the SMS with '15' (status report requested, received but not stored in EF SMSR).
If the short message is not found within the USIM memory, the USIM indicates that to the ME.
Update:
The ME looks for the next available area to store the short message. If such an area is available, it performs the updating procedure with EF SMS.
If there is no available empty space in the USIM to store the received short message, a specific MMI will have to take place in order not to loose the message.
Erasure:
The ME will select in the USIM the message area to be erased. Depending on the MMI, the message may be read before the area is marked as "free". After performing the updating procedure with EF SMS, the memory allocated to this short message in the USIM is made available for a new incoming message. The memory of the USIM may still contain the old message until a new message is stored in this area.
If service No. 11 is "available" and the status of the SMS is '1D' (status report requested, received and stored in EF SMSR), the ME performs the erasure procedure for EF SMSR with the corresponding record in EF SMSR.
Up

5.3.4  Advice of chargeWord‑p. 245
Requirement:
Service No. 13 "available".
Accumulated Call Meter.
Request:
The ME performs the reading procedure with EF ACM. The USIM returns the last updated value of the ACM.
Initialisation:
The ME performs the updating procedure with EF ACM using the new initial value.
Increasing:
The ME performs the increasing procedure with EF ACM sending the value which has to be added.
Accumulated Call Meter Maximum Value.
Request:
The ME performs the reading procedure with EF ACMmax.
Initialisation:
The ME performs the updating procedure with EF ACMmax using the new initial maximum value.
Price per Unit and Currency Table (PUCT).
Request:
The ME performs the reading procedure with EF PUCT.
Update:
The ME performs the updating procedure with EF PUCT.
Up

5.3.5  Capability configuration parameters

Requirement:
Service No. 14 "available".
Request:
The ME performs the reading procedure with EF CCP2.
Update:
The ME performs the updating procedure with EF CCP2.
Erasure:
The ME sends the identification of the requested information to be erased. The content of the identified record in EF CCP2 is marked as "free".
Up

5.3.6  User controlled PLMN selector with Access Technology

Requirement:
Service No. 20 "available".
Request:
The ME performs the reading procedure with EFPLMNwACT.
Update:
The ME performs the updating procedure with EFPLMNwACT.

5.3.7  Cell broadcast message identifier

Requirement:
Service No. 15 "available".
Request:
The ME performs the reading procedure with EF CBMI.
Update:
The ME performs the updating procedure with EF CBMI.

5.3.8  Group identifier level 1Word‑p. 246
Requirement:
Service No. 17 "available".
Request:
The ME performs the reading procedure with EF GID1.

5.3.9  Group identifier level 2

Requirement:
Service No. 18 "available".
Request:
The ME performs the reading procedure with EF GID2.

5.3.10  Service provider name

Requirement:
Service No. 19 "available".
Request:
The ME performs the reading procedure with EF SPN.

5.3.11  Enhanced multi level precedence and pre-emption service

Requirement:
Service No. 24 "available".
Request:
The ME performs the reading procedure with EF eMLPP.

5.3.12  Cell broadcast message identifier ranges

Requirement:
Service No. 16 "available".
Request:
The ME performs the reading procedure with EF CBMIR.
Update:
The ME performs the updating procedure with EF CBMIR.

5.3.13  Short message status report

Requirement:
Service No. 11 "available".
Request:
If the status of a stored short message indicates that there is a corresponding status report, the ME performs the reading procedure on the records of EF SMSR and identifies the record containing the appropriate status report.
Update:
If a status report is received, the ME first seeks within the SMS record identifiers of EF SMSR for the same record number it used for the short message in EF SMS. If such a record identifier is found in EF SMSR, it is used for storage. If such a record identifier is not found, then the ME seeks for a free entry in EF SMSR for storage. If no free entry is found the ME runs the Purge procedure with EF SMSR. If there is still no free entry, the status report is not stored.
If the ME found an appropriate record in EF SMSR for storage, it updates the record with the status report setting the record identifier in EF SMSR to the appropriate record number of the short message in EF SMS.
The status in EF SMS is updated accordingly by performing the update procedure with EF SMS.
Erasure:
The ME runs the update procedure with EF SMSR by at least storing '00' in the first byte of the record. The ME may optionally update the following bytes with 'FF'.
Purge:
The ME shall read the SMS record identifier (byte 1) of each record of EF SMSR. With each record the ME checks the corresponding short messages in EF SMS. If the status (byte 1) of the corresponding SMS is not equal '1D' (status report requested, received and stored in EF SMSR), the ME shall perform the erasure procedure with the appropriate record in EF SMSR.
Up

5.3.14  APN Control ListWord‑p. 247
Requirement:
Service No. 35 "available".
Request:
The ME performs the reading procedure with EF ACL.
Update:
The ME performs the updating procedure with EF ACL.
Enabling:
The ME activates service No. 3 in EF EST (bit No. 3 set to "1").
Disabling:
The ME deactivates service No. 3 in EF EST (bit No. 3 set to "0").
When the APN Control List service is enabled, the ME shall check that the entire APN of any PDP context is listed in EF ACL before requesting this PDP context activation from the network. If the APN is not present in EF ACL, the ME shall not request the corresponding PDP context activation from the network.
In the case that the APN Control List is enabled and no APN is indicated in the PDP context request, indicating that a network provided APN is to be used, then the ME shall only request the PDP context activation if "network provided APN" is contained within EF ACL.
If the APN Control List service is enabled and the ME is to provide an APN as part of attach for PDN connectivity, then the ME shall verify that the APN value is present in the EF ACL and if it is not the ME shall not proceed with the attach procedure. If the APN Control List service is enabled and the ME does not indend to provide an APN as part of the attach for PDN connectivity and use a network provided APN, the ME shall not check if "network provided APN" is contained within EF ACL.
If the APN Control List service is enabled and the ME is to provide a DNN as part of PDU session establishment, then the ME shall verify that the DNN value is present in the EF ACL and if it is not the ME shall not proceed with the PDU session establishment procedure. If the APN Control List service is enabled and the ME does not intend to provide a DNN as part of the PDU session establishment and use a network provided DNN, the ME shall not check if "network provided DNN" is contained within EF ACL.
Up

5.3.15  Depersonalisation Control Keys

Requirement:
Service No. 36 "available".
Request:
The ME performs the reading procedure with EF DCK.

5.3.16  Co-operative Network List

Requirement:
Service No. 37 "available".
Request:
The ME performs the reading procedure with EF CNL.

5.3.17  CPBCCH information

Requirement:
Service No. 39 "available".
Request:
The ME performs the reading procedure with EF CPBCCH.
Update:
The ME performs the updating procedure with EF CPBCCH.

5.3.18  Investigation Scan

Requirement:
Service No. 40 "available".
Request:
The ME performs the reading procedure with EF InvScan.

5.3.19  Enabled Services Table Request

Requirement:
Service No. 2, 6, 34 or 35 "available".
Request:
The ME performs the reading procedure with EF EST.
Update:
The ME performs the updating procedure with EF EST.

5.3.20  Operator controlled PLMN selector with Access TechnologyWord‑p. 248
Requirement:
Service No. 42 "available".
Request:
The ME performs the reading procedure with EFOPLMNwACT

5.3.21  HPLMN selector with Access Technology

Requirement:
Service No. 43 "available".
Request:
The ME performs the reading procedure with EFHPLMNwACT

5.3.22  Automatic Answer on eMLPP service |R6|

Requirement:
Service No. 25 "available"
Request:
The ME performs the reading procedure with EF AaeM.
Update:
The ME performs the updating procedure with EF AaeM.

5.3.23  Network Parameter information

Request:
The ME performs the reading procedure with EF NETPAR.
Update:
The ME performs the updating procedure with EF NETPAR.

5.3.24  PLMN network name

Requirement:
Service No. 45 "available".
Request:
The ME performs the reading procedure with EF PNN.

5.3.25  Operator PLMN List |R4|

Requirement:
Service No. 46 "available".
Request:
The ME performs the reading procedure with EF OPL

5.3.26  Message Waiting Indication |R4|

Requirement:
Service No. 48 "available".
Request:
The ME performs the reading procedure with EF MWIS.
Update:
The ME performs the updating procedure with EF MWIS.

5.3.27  Call Forwarding Indication Status |R4|

Requirement:
Service No. 49 "available".
Request:
The ME performs the reading procedure with EF CFIS.
Update:
The ME performs the updating procedure with EF CFIS.

5.3.28  Service Provider Display Information |R4|Word‑p. 249
Requirement:
Service No. 19 and 51 are "available".
Request:
The ME performs the reading procedure with EF SPDI.
Update:
The ME performs the updating procedure with EF SPDI.

5.3.29  MMS Notifications |R4|

Requirement:
Service No. 52 "available".
Request:
The ME sends the identification of the information to be read, then the ME performs the reading procedure with EF MMSN. If Service No. 53 is available the ME shall analyse the data of EF MMSN to ascertain, whether additional data is associated in EF EXT8. If necessary, then the ME performs the reading procedure on EF EXT8 to assemble the complete MMS notification.
Update:
The ME analyses and assembles the MMS notification to be stored as follows:
  • if the MMS notification contains not more bytes than the maximum possible number for EF MMSN then the ME looks for the next available area to store the MMS notification. If such an area is available, it performs the updating procedure with EF MMSN.
  • if the MMS notification contains more bytes than the maximum possible number for EF MMSN then the ME seeks for a sufficient number of free records in EF EXT8 to store the complete MMS notification.
  • If there is not a sufficient number of EF EXT8 records marked as "free" to store the complete MMS notification, the procedure is aborted.
  • Otherwise, the ME performs the updating procedure and stores as many bytes as possible in EF MMSN. The Extension file record number of EF MMSN is coded with the associated record number in the EF EXT8. The remaining bytes are stored in the selected EF EXT8 record where the type of the record is then set to "additional data". The second byte of the EF EXT8 record is set with the number of bytes of the remaining additional data. It is possible, if the number of additional digits exceeds the capacity of the additional record, to chain another record inside the EF EXT8 by the identifier in the last byte of the record. In this case byte 2 of each record for additional data within the same chain indicates the number of bytes within the same record.
    The ME is only allowed to store extension data in unused records of EF EXT8
    If there is no available empty space in the USIM to store the MMS notification, it is up to ME implementation how the notification is handled.
Erasure:
The ME will select in the USIM the MMS notification to be erased. Depending on the MMI, the MMS notification may be read before the area is marked as "free". The memory of the USIM may still contain the old MMS notification until a new message is stored. If Service No. 53 is available all associated records in EF EXT8 are then marked by the ME as "free" by setting them to 'FF'.
Up

5.3.30  MMS Issuer Connectivity Parameters |R4|

Requirement:
Service No. 52 "available".
Request:
the ME performs the reading procedure with EFMMSICP.
Update:
The ME performs the updating procedure with EFMMSICP.

5.3.31  MMS User Preferences |R4|

Requirement:
Service No. 52 "available".
Request:
the ME performs the reading procedure with EFMMSUP.
Update:
The ME performs the updating procedure with EFMMSUP.

5.3.32  MMS User Connectivity Parameters |R4|Word‑p. 250
Requirement:
Service No. 52 and No. 55 "available".
Request:
the ME performs the reading procedure with EFMMSUCP.
Update:
The ME performs the updating procedure with EFMMSUCP.

5.3.33  Network's indication of alerting |R4|

Requirement:
Service No. 56 "available".
Request:
The ME performs the reading procedure with EFNIA.

5.3.34  Multimedia Messages Storage |R6|

If the terminal supports Multimedia Message Storage on the USIM, then the following procedures apply.
As defined in TS 23.140 a Multimedia Message consists of content, or multimedia objects, and headers to describe various properties of that content. An MM is stored in EF MMDF, a BER-TLV structured file.
A list of multimedia messages is stored in the BER-TLV file EFMMLwhere each data object identifies one Multimedia Message stored in EF MMDF.
Prerequisite:
Service No. 67 "available".
Request:
The ME performs the reading procedures on EF MML to verify the presence and to get the location information of the targeted MM. Then the ME performs the reading procedure of the EF MMDF file to get the MM.
Update:
The ME chooses a free identity (i.e. not listed in EF MML) for the multimedia message and check for available space in the EF MMDF file. This procedure could be done for each update or once at the startup of the UE and after a REFRESH command involving one of the DFMULTIMEDIA files. Then the ME performs the following procedures:
If there is no available empty space in the EF MMDF file to store the MM, the procedure is aborted and the user is notified.
Else, the ME stores the MM in EF MMDF, then updates the information in EF MML accordingly.
Erasure:
After a successful deletion of an MM in EF MMDF the terminal updates the information in EF MML accordingly.
Up

5.3.35  Equivalent HPLMN Presentation Indication request |R7|

Requirement:
Service No. 73 "available".
Request:
The ME performs the reading procedure with EF EHPLMNPI.

5.3.36  NAF Key Centre Address request |R7|

Requirement:
Service No. 68 and service No. 76 "available".
Request:
The ME performs the reading procedure with EF NAFKCA.

5.3.37  Service provider name Icon |R8|

Requirement:
Service No. 19 and service No. 78 "available".
Request:
The ME performs the reading procedure with EF SPN and EF SPNI.

5.3.38  PLMN network name Icon |R8|Word‑p. 251
Requirement:
Service No. 45 and service No. 79 "available".
Request:
The ME performs the reading procedure with EF PNN and EF PNNI.

5.3.39  ICE Information request |R8|

The ICE information shall be accessible even when the security features of the UE or UICC have been enabled. The ICE access procedure is described in TS 22.030. The terminal shall discover that the ICE feature is supported by the ability to select one of the ICE files i.e. EF ICE_DN, EF ICE_FF or EF ICE_graphics.
Request:
The terminal performs the read procedure with EF ICE_DN and/or EF ICE_FF and/or EF ICE_graphics.
Update:
The terminal performs the update procedure with EF ICE_DN and/or EF ICE_FF and/or EF ICE_graphics.
Disable ICE display:
The terminal performs the deactivate procedure consecutively on all the supported files (EF ICE_DN, EF ICE_FF and EF ICE_graphics).
Enable ICE display:
The terminal performs the activate procedure consecutively on all the supported files (EF ICE_DN, EF ICE_FF and EF ICE_graphics ).
The content of the EF ICE_DN, EF ICE_FF and EF ICE_graphics shall be preserved when enabling and disabling the ICE display.
Up

5.3.40  eCall Related Procedures |R8|

The eCall feature on the USIM provides two numbers or URIs, a test number or URI and a reconfiguration number or URI, to the terminal to be used with the eCall. eCall support on the USIM is indicated in the service table when Service No. 89 or Service No. 112 is "available".
Depending on the type of eCall support and the domain, EF FDN or EF SDN or EF FDNURI or EF SDNURI is used to provide the eCall functionality.
Up

5.3.40.1  eCall Only support

Requirement:
Service No. 89 is "available" and FDN is enabled (Service No. 2 is "available" and FDN service is enabled in EF EST).
Request:
The ME performs the reading procedure with EF FDN.
If eCall only calls are supported, then EF FDN shall only contain two entries. The first entry shall contain the eCall test number and the second entry shall contain the eCall reconfiguration number. These numbers are used for eCall over CS domain. If Service No. 112 or Service No. 99 are not available, these numbers are used also for eCall over IMS Emergency Services using the PS domain in E-UTRAN or in NG-RAN, after being converted into tel URIs. A terminal in eCall only mode performs the FDN related procedures.
Requirement:
Service No. 112 and Service No. 99 are "available" and FDN is enabled (Service No. 2 is "available" and FDN service is enabled in EF EST).
Request:
The ME performs the reading procedure with EF FDNURI.
If eCall only calls are supported, then EF FDNURI shall only contain two entries. The first entry shall contain the eCall test URI and the second entry shall contain the eCall reconfiguration URI. These URIs are used for eCall over IMS Emergency Services using the PS domain in E-UTRAN or in NG-RAN. A terminal in eCall only mode performs the FDN related procedures.
Up

5.3.40.2  eCall and Normal call support

Requirement:
Service No. 89 and Service No. 4 are "available" and FDN is disabled (either Service No. 2 is not "available" or FDN service is disabled in EF EST).
Request:
The ME performs the reading procedure with EF SDN.
If eCall and normal calls are supported, then the last two entries of EF SDN shall contain the eCall test number and the eCall reconfiguration number respectively. These numbers are used for eCalls over CS domain. If Service No. 112 or Service No. 99 are not available, these numbers are used also for eCall over IMS Emergency Services using the PS domain in E-UTRAN or in NG-RAN, after being converted into tel URIs. A terminal in eCall and normal mode performs the SDN related procedures.
Requirement:
Service No. 112 and Service No. 99 and Service No. 4 are "available" and FDN is disabled (either Service No. 2 is not "available" or FDN service is disabled in EF EST).
Request:
The ME performs the reading procedure with EF SDNURI.
If eCall and normal calls are supported, then the last two entries of EF SDNURI shall contain the eCall test URI and the eCall reconfiguration URI respectively. These URIs are used for eCall over IMS Emergency Services using the PS domain in E-UTRAN or in NG-RAN. A terminal in eCall and normal mode performs the SDN related procedures.
Up

5.3.40.3  Change of eCall modeWord‑p. 252
It is possible to re-configure the USIM from eCall only support to eCall and Normal call support, or vice versa, either by changing the content of the USIM Service Table, and/or by changing the content of the EF EST. The terminal shall be notified of the changes by using the REFRESH proactive command, defined in TS 31.111, using one of the following modes:
  • USIM Initialization and File Change Notification
  • USIM Initialization and Full File Change Notification
  • UICC Reset
  • USIM Application Reset
  • 3G Session Reset
Up

5.3.41  SM-over-IP |R8|

Requirement:
Service No. 12 and No. 91 "available".
Request:
the ME performs the reading procedure with EF PSISMSC.
Update:
The ME performs the updating procedure with EF PSISMSC.

5.3.42  UICC access to IMS |R10|

Requirement:
Service No. 95 is "available" and the ISIM application defined in TS 31.103 is not present on the UICC.
Request:
The terminal performs the reading procedure with EF UICCIARI.
The procedures and command for "UICC access to IMS" are defined in TS 31.111. An ME supporting UICC access to IMS shall perform the reading procedure with EF UICCIARI prior to sending a registration to the IMS.
Up

5.3.43  TV Configuration |R14|

Requirement:
Service No. 116 "available".
Request:
The ME performs the reading procedure with EF TVCONFIG.

5.3.44  3GPP PS Data Off related procedures |R14|

Requirement:
service No. 117 is "available" in the USIM Service Table.
Request:
If the ME supports 3GPP PS Data Off the ME shall perform the reading procedure with EF3GPPPSDataOff.

5.3.45  3GPP PS Data Off service list related procedures |R14|Word‑p. 253
Requirement:
service No. 118 is "available" in the USIM Service Table.
Request:
If the ME supports 3GPP PS Data Off the ME shall perform the reading procedure with EF 3GPPPSDATAOFFservicelist. If the ME performs the reading procedure with EF 3GPPPSDATAOFFservicelist, the UE shall use the 3GPP PS Data Off Service list in the EF 3GPPPSDATAOFFservicelist as described in TS 24.229, clause 4.17, TS 24.229, clause B.3.1.5 and TS 24.229, clause L.3.1.5.
Up

5.3.46  EARFCN list for MTC/NB-IOT UEs |R15|

Requirement:
Service No. 121 "available".
Request:
The ME performs the reading procedure with EF EARFCNList.

5.3.47  SUCI Calculation information procedure |R15|

Requirement:
"SUCI calculation is to be performed by the ME" (i.e. Service No. 124 is "available"and Service No. 125 is not "available").
Request:
As part of the SUCI calculation performed by the ME, the ME performs the reading procedure with EF SUCI_Calc_Info.

5.3.48  SUCI Calculation by the USIM procedure |R15|

Requirement:
"SUCI calculation is performed by the USIM" (i.e. Service No. 124 and Service No. 125 are "available").
Request:
The ME uses the GET IDENTITY command in SUCI context to retrieve the SUCI calculated by the USIM.

5.3.49  Control plane-based Steering of Roaming related procedures |R15|

If service No. 127 is "available" in the USIM Service Table, the Registration Accept shall contain control plane based Steering of Roaming information during the initial registration procedure in a VPLMN.
The control plane-based Steering of Roaming procedure and the related information from the HPLMN are specified in TS 23.122.

5.3.50  5GS Operator PLMN List |R15|

Requirement:
Service No. 129 "available".
Request:
The ME performs the reading procedure with EF OPL5G.

5.3.51  Routing Indicator procedure for ME |R15|

Requirement:
Service No. 124 is "available".
Request:
As part of the SUCI calculation performed by the ME, the ME performs the reading procedure with EFRouting_Indicator.

Up   Top   ToC