Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 31.102  Word version:  18.3.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.4.11.17…   4.4.12…   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… 
4.2.93 EFUFC (USAT Facility Control)  4.2.94 EFNASCONFIG (Non Access Stratum Configuration)  4.2.95 EFUICCIARI (UICC IARI)  4.2.96 EFPWS (Public Warning System)  4.2.97 EFFDNURI (Fixed Dialling Numbers URI)  4.2.98 EFBDNURI (Barred Dialling Numbers URI)  4.2.99 EFSDNURI (Service Dialling Numbers URI)  4.2.100 EFIAL (IMEI(SV) Allowed Lists) 
...

 

4.2.93  EFUFC (USAT Facility Control) |R10|  p. 106

This EF contains data for USAT Facility Control related to AT commands for USAT (see TS 31.111).
Identifier: '6FE6'Structure: transparentOptional
File size: X bytes, (X ≥ 1)Update activity: low
Access Conditions:
READALW
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to XFacility listMX bytes
The facility list has the same format as the TERMINAL PROFILE defined in TS 31.111.
By setting the corresponding bits to 1, the facility list defines facilities which can only be provided by the MT and which are not allowed to be provided by the TE.
If a TERMINAL PROFILE is longer than the facility list, for the purpose of facility control, the exceeding bytes of the TERMINAL PROFILE shall be compared according to the generic rules found in TS 31.111.
Up

4.2.94  EFNASCONFIG (Non Access Stratum Configuration) |R10|  p. 107

If service No. 96 is "available", this file shall be present. This EF contains some of the NAS configuration parameters defined in TS 24.368. For each of these NAS configuration parameters, a parameter provided in EFNASCONFIG shall take precedence over the corresponding parameter stored in the ME's non-volatile memory.
Identifier: '6FE8'Structure: transparentOptional
File size: Z bytesUpdate activity: low
Access Conditions:
READPIN
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to ZNAS configuration parameter TLV objectsMZ bytes
NAS configuration parameter information
Description Value M/O/C Length (bytes)
NAS signalling priority Tag'80'O1
LengthL1CNote 1
NAS signalling priority value--CL1
NMO I Behaviour Tag'81'O1
LengthL2CNote 1
NMO I Behaviour value--CL2
Attach with IMSI Tag'82'O1
LengthL3CNote 1
Attach with IMSI value--CL3
Minimum Periodic Search Timer Tag'83'O1
LengthL4CNote 1
Minimum Periodic Search Timer value--CL4
Extended access barring Tag'84'O1
LengthL5CNote 1
Extended access barring value--CL5
Timer T3245 Behaviour Tag'85'O1
LengthL6CNote 1
Timer T3245 Behaviour value--CL6
Override NAS signalling low priority Tag'86'O1
LengthL7CNote 1
Override NAS signalling low priority value--CL7
Override Extended access barring Tag'87'O1
LengthL8CNote 1
Override Extended access barring value--CL8
Fast First Higher Priority PLMN Search Tag'88'O1
LengthL9CNote 1
Fast First Higher Priority PLMN value--CL9
E-UTRA Disabling Allowed for EMM cause #15 Tag'89'O1
LengthL10CNote 1
E-UTRA Disabling Allowed for EMM cause #15 Value-CL10
SM_RetryWaitTime Tag'8A'O1
LengthL11CNote 1
SM_RetryWaitTime value--CL11
SM_RetryAtRATChange Tag'8B'O1
LengthL12CNote 1
SM_RetryAtRATChange value--CL12
Default_DCN_ID Tag'8C'O1
LengthL13CNote 1
Default_DCN_ID value--CL13
Exception Data Reporting Allowed Tag'8D'O1
LengthL14CNote 1
Exception Data Reporting Allowed value--CL14
RLOSPreferredPLMNList Tag'8E'O1
LengthL15C4n (Note 1)
RLOSPreferredPLMNList value--CL15
RLOSAllowedMCCList Tag'8F'O1
LengthL16C2n (Note 1)
RLOSAllowedMCCList value--CL16
No E-UTRA Disabling In 5GS Tag'90'O1
LengthL17CNote 1
No E-UTRA Disabling In 5GS value--CL17
Additional NAS configuration parameters Tag'91'O1
LengthL18CNote 1
Additional NAS configuration parameters value--CL18
NOTE 1:
The length is coded according to ISO/IEC 8825-1 [35].
NOTE 2:
C; if the Tag is present, this is mandatory.
NAS signalling priority
Contents:
As described in TS 24.368, used to determine the NAS signalling priority included in NAS messages.
Coding:
As defined for the NAS_SignallingPriority leaf in TS 24.368.
NMO I Behaviour
Content:
As described in TS 24.368, indicates whether the "NMO I, Network Mode of Operation I" indication is applied by the UE.
Coding:
b8 b7 b6 b5 b4 b3 b2 b1
RFU (see TS 31.101) b1 value to be interpreted as defined for the NMO_I_Behaviour leaf in TS 24.368.
 
Attach with IMSI
Content:
As described in TS 24.368, indicates whether attach with IMSI is performed when moving to a non-equivalent PLMN.
Coding:
b8 b7 b6 b5 b4 b3 b2 b1
RFU (see TS 31.101) b1 value to be interpreted as defined for the AttachWithIMSI leaf in TS 24.368.
 
Minimum Periodic Search Timer
Content:
As described in TS 24.368, gives a minimum value in minutes for the timer T controlling the periodic search for higher prioritized PLMNs. The content applies a minimum value that may override the value in file EFHPPLMN (Higher Priority PLMN search period), as specified in clause 4.4.3.3.1 of TS 23.122.
Coding:
As defined for the MinimumPeriodicSearchTimer leaf in TS 24.368.
Extended access barring
Content:
As described in TS 24.368, indicates whether the UE applies extended access barring.
Coding:
b8 b7 b6 b5 b4 b3 b2 b1
RFU (see TS 31.101) b1 value to be interpreted as defined for ExtendedAccessBarring leaf in TS 24.368.
 
Timer T3245 Behaviour
Content:
As described in TS 24.368, indicates whether the timer T3245 and the related functionality is used by the UE.
Coding:
b8 b7 b6 b5 b4 b3 b2 b1
RFU (see TS 31.101) b1 value to be interpreted as defined for Timer_T3245_Behaviour leaf in TS 24.368.
 
Override NAS signalling low priority
Contents:
As described in TS 24.368, used to determine whether the NAS signalling priority included in NAS messages can be overriden.
Coding:
b8 b7 b6 b5 b4 b3 b2 b1
RFU (see TS 31.101) b1 value to be interpreted as defined for the Override_NAS_SignallingLowPriority leaf in TS 24.368.
 
The Override NAS signalling low priority tag and the Override Extended access barring tag shall be set to the same value, e.g., if the UE is configured to override the NAS signalling low access priority indicator, then it has also to be configured to override Extended access barring (see clause 4.3.17.4 of TS 23.401).
Override Extended access barring
Contents:
As described in TS 24.368, used to determine whether the Extended access barring included in NAS messages can be overriden.
Coding:
b8 b7 b6 b5 b4 b3 b2 b1
RFU (see TS 31.101) b1 value to be interpreted as defined for the Override_ ExtendedAccessBarring leaf in TS 24.368.
 
The Override Extended access barring tag and the Override NAS signalling low priority tag shall be set to the same value, e.g., if the UE is configured to override Extended access barring, then it has also to be configured to override the NAS signalling low access priority indicator (see clause 4.3.17.4 of TS 23.401).
Fast First Higher Priority PLMN Search
Contents:
Determine whether the UE can perform Fast First Higher Priority PLMN Search upon selecting a VPLMN as specified in TS 23.122.
Coding:
b8 b7 b6 b5 b4 b3 b2 b1
RFU (see TS 31.101) b1 value to be interpreted as defined for the FastFirstHigherPriorityPLMNSearch leaf in TS 24.368.
 
E-UTRA Disabling Allowed for EMM cause #15
Contents:
Determine whether the UE is allowed to disable the E-UTRA capability when it receives the Extended EMM IE with value cause "E-UTRAN not allowed" as specified in TS 24.301.
Coding:
b8 b7 b6 b5 b4 b3 b2 b1
RFU (see TS 31.101) b1 value to be interpreted as defined for the EUTRADisablingAllowedforEMMcause15 leaf in TS 24.368
 
SM_RetryWaitTime
Contents:
As described in TS 24.368, provides a configured UE retry wait time value applicable when in HPLMN or EHPLMN (see TS 23.122) for controlling the UE session management retry behaviour when prior session management request was rejected by the network with cause value #8, #27, #32, #33 as specified in TS 24.008 and TS 24.301, or when prior session management request was rejected by the network with cause value #8, #27, #32, #33, #70 as specified in TS 24.501.
Coding:
b8 b7 b6 b5 b4 b3 b2 b1
bits b1 to b8 to be interpreted as defined for the SM_RetryWaitTime leaf in TS 24.368
 
SM_RetryAtRATChange
Contents:
As described in TS 24.368, indicates the UE's retry behaviour when in HPLMN or EHPLMN (see TS 23.122) after inter-system change between S1 mode and A/Gb or Iu mode or N1 mode as specified in TS 24.008 and TS 24.301 and TS 24.501.
Coding:
b8 b7 b6 b5 b4 b3 b2 b1
RFU (see TS 31.101) b1 value to be interpreted as defined for the SM_RetryAtRATChange leaf in TS 24.368
 
Default_DCN_ID
Contents:
As described in TS 24.368, indicates the default DCN-ID which is provided by NAS to the lower layers at establishment of the NAS signalling connection as specified in TS 24.301.
Coding:
As the DCN-ID value inside the DCN-ID IEI defined in clause 10.5.5.35 of TS 24.008.
Exception Data Reporting Allowed
Contents:
As described in TS 24.368, for the UE in NB-S1 mode indicates whether the UE is allowed to use the RRC establishment cause mo-ExceptionData, as specified in TS 24.301.
Coding:
b8 b7 b6 b5 b4 b3 b2 b1
RFU (see TS 31.101) b1 value to be interpreted as defined for the ExceptionDataReportingAllowed leaf in TS 24.368.
 
RLOSPreferredPLMNList
Contents:
As described is TS 24.368, it contains in descending priority order, a list of preferred RLOS PLMNs configured to the UE for selection of a PLMN offering access to RLOS as specified in TS 23.122.
Coding:
Bytes Description M/O Length
1 to 31st PLMN (highest priority)M3 bytes
41st PLMN ConfigM1 byte
5 to 72nd PLMNO3 bytes
82nd PLMN ConfigO1 byte
9 to 113rd PLMNO3 bytes
123rd PLMN ConfigO1 byte
…
(4n-3) to (4n-1)nth PLMNO3 bytes
4nnth PLMN ConfigO1 byte
Coding of PLMN Config:
b8 b7 b6 b5 b4 b3 b2 b1
RFU (see TS 31.101) b1=0:
This PLMN has higher priority than the next PLMN in the list
b1=1:
This PLMN has same priority than the next PLMN in the list
 
RLOSAllowedMCCList
Contents:
As described is TS 24.368, it contains a list of allowed MCC configured to the UE to allow the UE to check whether the MCC of the PLMN ID of the serving network that advertises RLOS service is present in the list and whether the MCC part of the IMSI configured in the USIM is present in the list of MCCs before initiating the RLOS connection as specified in TS 23.122.
Coding:
Bytes Description M/O Length
1 to 21st MCCM2 bytes
3 to 42nd MCCO2 bytes
5 to 63rd MCCO2 bytes
…
(2n-1) to (2n)nth MCCO2 bytes
Coding of MCC: according to TS 24.008.
  • A BCD value of 'D' in any of the MCC digits shall be used to indicate a "wild" value for that corresponding MCC digit. A value of 'DDD' represents "any MCC" value.
 
No E-UTRA Disabling In 5GS
Contents:
As described in TS 24.368, used to indicate whether E-UTRA Disabling In 5GS is disabled or enabled.
Coding:
b8 b7 b6 b5 b4 b3 b2 b1
RFU (see TS 31.101) value to be interpreted as defined for NoEUTRADisablingIn5GS leaf in TS 24.368.
 
Additional NAS configuration parameters
Contents:
The additional NAS configuration parameters contains some of the NAS configuration parameters defined in TS 24.368.
Coding:
b8 b7 b6 b5 b4 b3 b2 b1
RFU (see TS 31.101) value to be interpreted as defined for DefaultNSSAIInclusionMode leaf in clause 5.10zz4 of TS 24.368.
 
If any of these NAS configuration parameters is neither included in EFNASCONFIG nor stored in the ME's non-volatile memory, the default value as defined for the corresponding leaf in TS 24.368 shall apply.
Unused bytes shall be set to 'FF'.
Up

4.2.95  EFUICCIARI (UICC IARI) |R10|  p. 113

If service No. 95 is "available", this file shall be present.
As specified in TS 24.229 a ME includes the list of IARIs for the IMS applications it intends to use when sending an initial registration or when sending subsequent registrations to the IMS in the form of a SIP REGISTER request.
This EF contains a list of IARIs associated with active applications installed on the UICC that are included in the SIP REGISTER request in accordance with the procedures of TS 24.229.
Identifier: '6FE7'Structure: linear fixedOptional
Record length: X bytesUpdate activity: low
Access Conditions:
READPIN
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to XIARI TLV objectMX bytes
IARI TLV object
Contents:
The content and coding is defined below.
Coding of the IARI TLV objects
Length Description Value Status
1 byteIARI TLV TAG'80'M
1 byteLength of IARIYM
Y bytesIARI value-M
 
Coding:
IMS Application Reference Identifier: shall be coded as specified in TS 24.229.
Unused bytes shall be set to 'FF'.
Up

4.2.96  EFPWS (Public Warning System) |R11|  p. 114

If service No. 97 is "available", this file shall be present. This EF contains the configuration parameters for PWS, as defined in TS 22.268.
Identifier: '6FEC'Structure: transparentOptional
File size: 1+Z bytesUpdate activity: low
Access Conditions:
READALW
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to Z+1PWS configurationM1+Z bytes
Contents:
Configuration for PWS
Coding:
First byte:
b8 b7 b6 b5 b4 b3 b2 b1
RFU (see TS 31.101) b2=0 process all PWS warning messages in VPLMNs
b2=1 ignore all PWS warning messages in VPLMNs		 b1=0 process all PWS warning messages in HPLMN and equivalent PLMNs
b1=1 ignore all PWS warning messages in HPLMN and equivalent PLMNs
 
Successive bytes:
RFU (see TS 31.101)
Up

4.2.97  EFFDNURI (Fixed Dialling Numbers URI) |R12|  p. 114

If service No. 2 and service No. 99 are "available", this file may be present.
This EF contains a list of FDN stored in URI address format. It may also contain an associated alpha-tagging.
Structure of EFFDNURI
Identifier: '6FED'Structure: linear fixedOptional
Record length: X+Y bytesUpdate activity: low
Access Conditions:
READPIN
UPDATEPIN2
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to XURI AddressMX bytes
X+1 to X+YAlpha IdentifierOY bytes
URI Address
Content:
The URI Address associated to the referenced file Record number.
Coding:
Same as URI TLV data object in EFIMPU defined in TS 31.103.
Alpha Identifier
Contents:
Alpha-tagging of the associated dialling number.
Coding:
this alpha-tagging shall use
either:
  • the SMS default 7-bit coded alphabet as defined in TS 23.038 with bit 8 set to 0. The alpha identifier shall be left justified. Unused bytes shall be set to 'FF'.
or
If FDN is enabled, the ME shall only allow outgoing calls using destination addresses which are in EFFDNURI, in addition to the EFFDN entries, following the same principle as defined in the Fixed Number Dialling description in TS 22.101 applied to URI addresses.
The EFFDNURI shall be enforced:
  • If the dialling number introduced by the user is an URI
  • Or if the dialling number has been stored in the UE as a URI
Up

4.2.98  EFBDNURI (Barred Dialling Numbers URI) |R12|  p. 115

If service No. 6 and service No. 99 are "available", this file may be present.
This EF contains a list of BDN stored in URI address format. It may also contain an associated alpha-tagging.
Structure of EFBDNURI
Identifier: '6FEE'Structure: linear fixedOptional
Record length: X+Y bytesUpdate activity: low
Access Conditions:
READPIN
UPDATEPIN2
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to XURI AddressMX bytes
X+1 to X+YAlpha IdentifierOY bytes
URI Address
Content:
The URI Address associated to the referenced file Record number.
Coding:
Same as URI TLV data object in EFIMPU defined in TS 31.103.
Alpha Identifier
Contents:
Alpha-tagging of the associated dialling number.
Coding:
this alpha-tagging shall use
either:
  • the SMS default 7-bit coded alphabet as defined in TS 23.038 with bit 8 set to 0. The alpha identifier shall be left justified. Unused bytes shall be set to 'FF'.
or
If BDN is enabled, the ME shall only allow outgoing calls using destination addresses which are neither in EFBDNURI nor in the EFBDN entries, following the same principle as defined in the Barring of Dialled Numbers described in TS 22.101 applied to URI addresses.
The EFBDNURI shall be enforced:
  • If the dialling number introduced by the user is an URI
  • Or if the dialling number has been stored in the UE as a URI
Up

4.2.99  EFSDNURI (Service Dialling Numbers URI) |R12|  p. 116

If service No. 4 and service No. 99 are "available", this file may be present.
This EF contains a list of SDN stored in URI address format. It may also contain an associated alpha-tagging. If the service No. 112 is available this file will contain the eCall test and reconfiguration URIs that are used by an UE in eCall and normal service mode.
Structure of EFSDNURI
Identifier: '6FEF'Structure: linear fixedOptional
Record length: X+Y bytesUpdate activity: low
Access Conditions:
READPIN
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to XURI AddressMX bytes
X+1 to X+YAlpha IdentifierOY bytes
URI Address
Content:
The URI Address associated to the referenced file Record number.
Coding:
Same as URI TLV data object in EFIMPU defined in TS 31.103.
Alpha Identifier
Contents:
Alpha-tagging of the associated dialling number.
Coding:
this alpha-tagging shall use
either:
  • the SMS default 7-bit coded alphabet as defined in TS 23.038 with bit 8 set to 0. The alpha identifier shall be left justified. Unused bytes shall be set to 'FF'.
or
If SDN is enabled, the ME shall perform SDN procedure using destination addresses which are in EFSDNURI or in EFSDN entries, following the same principle as defined in the Service Dialling Numbers description in TS 22.101 applied to URI addresses.
Up

4.2.100  EFIAL (IMEI(SV) Allowed Lists) |R18|  p. 117

The file EFIAL stores ranges of values of IMEI(SV) to which the USIM is authorized to be paired as defined in this specification.
This file shall be present if USAT Application Pairing is supported as defined in this specification.
This file shall contain at least one IMEI(SV) range of values to which the USIM is authorized to be paired.
Identifier: '6FF0'Structure: linear fixedOptional
Record length: X+2 bytes (X≥16)Update activity: low
Access Conditions:
READADM
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to X+2IMEI or IMEISV range TLV objectMX+2 bytes
IMEI(SV) range of values TLV object
The content and coding is defined below, where IMEI and IMEISV are defined in TS 23.003:
Coding of the IMEI Range TLV objects
Length Description Status
1 byteTag of Range of IMEI values: '80'M
1 byteLengthM
X bytesIMEI range of values that the USIM is authorized to be paired to (Detail 1)C
 
Coding of the IMEISV Range TLV objects
Length Description Status
1 byteTag of Range of IMEISV values: '81'M
1 byteLengthM
X bytesIMEISV range of values that the USIM is authorized to be paired to (Detail 1)C
 
Detail 1:
  • Following the Length of the TLV, the range is defined as follow: [lower value][higher value].
  • The authorized values of IMEI or IMEISV in an authorized range of values include the lower and higher values of the specified range.
  • To define an authorized individual IMEI or IMEISV, the lower value and the higher value of a range shall both be equal to the value of the authorized IMEI or IMEISV.
  • For an IMEI, the Check Digit is not considered in the evaluation
  • For an IMEISV, the TAC|SNR part and the SVN part may be evaluated separately
Coding:
Unused bytes shall be set to 'FF'.
UICC OTA mechanism is used to update the file EFIAL stored in the USIM. This mechanism provides dynamic management of the pairing to change the allowed combinations of USIM and MTC ME(s) by adding or removing authorized IMEI(SV) ranges in the file EFIAL.
Up

Up   Top   ToC