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.107 EFIMSConfigData (IMS Configuration Data)  4.2.108 EFTVCONFIG (TV Configuration)  4.2.109 EF3GPPPSDataOff (3GPP PS Data Off)  4.2.110 EF3GPPPSDataOffservicelist (3GPP PS Data Off Service List)  4.2.111 EFXCAPConfigData (XCAP Configuration Data)  4.2.112 EFEARFCNList (EARFCN list for MTC/NB-IOT UEs)  4.2.113 EFMuDMiDConfigData (MuD and MiD Configuration Data)  4.2.114 EFeAKA (enhanced AKA support)  4.2.115 EFOCST ("Operator controlled signal threshold per access technology") 
...

 

4.2.107  EFIMSConfigData (IMS Configuration Data) |R14|  p. 123

If service No. 115 is "available", this file shall be present.
This EF contains the IMS configuration data object as specified in TS 24.167.
For the structure, content and coding of this file, see EFIMSConfigData in TS 31.103.
Up

4.2.108  EFTVCONFIG (TV Configuration) |R14|  p. 124

If service No. 116 is "available", this file shall be present.
This EF contains the configuration of the parameters related to TV service provided via a PLMN.
Identifier: '6FFB'Structure: linear fixedOptional
Record size: Z bytesUpdate activity: low
Access Conditions:
READALWAYS
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to 3PLMN identityM3 bytes
54 to 4+XTMGI List TLVOX bytes
4+X+1 to 4+X+1+YEARFCN List TLVOY bytes
4+X+Y+2 to ZRFUCZ-X-Y-3 bytes
PLMN
Contents:
As described in TS 24.117, the identity of the PLMN for which the TV service configuration applies.
Coding:
According to TS 24.008.
TMGI List TLV
Contents:
List of TMGIs.
Coding:
Description Value M/O Length (bytes)
TMGI List Tag'A0'M1
Length9nMNote
ENTRY 1---C9
ENTRY 2---C9
…
ENTRY n---C9
NOTE:
The length is coded according to ISO/IEC 8825-1 [35]
Each entry is coded:
1 to 6TMGIM6 bytes
7 to 8USD File IdM2 bytes
9Service typeM1 byte
TMGI
Contents:
The TMGI is defined as specified in TS 23.003.
Coding:
TMGI is coded in 6 bytes:
  • bytes 1 to 3: contain the MBMS Service ID, with the first digit coded in the most significant nibble of the first byte, and the last digit coded in the least significant nibble of the third byte.
  • bytes 4 to 6: contain the MCC and MNC values of the TMGI, coded as a PLMN according to TS 24.008.
USD File Id
Contents:
File identifier of the EFTVUSD inside the DFTV containing the User Service Description (USD).
Coding:
According to TS 31.101
Service type
Contents:
Type of service for which the entry is valid.
Coding:
b8 b7 b6 b5 b4 b3 b2 b1
RFU For User service. This is equivalent to an entry in the TMGIListForService leaf in TS 24.117. For Service Announcement service. This is equivalent to an entry in the TMGIListForSA leaf in TS 24.117.
 
EARFCN List TLV
Contents:
List of the E-UTRA ARFCN value of MBMS frequency.
Coding:
Description Value M/O Length (bytes)
EARFCN List Tag'A1'M1
Length4mMNote
EARFCN 1---C4
EARFCN 2---C4
…
EARFCN m---C4
NOTE:
The length is coded according to ISO/IEC 8825-1 [35].
 
Each EARFCN is coded in 4 bytes, as specified in TS 36.101.
Up

4.2.109  EF3GPPPSDataOff (3GPP PS Data Off) |R14|  p. 125

If service No. 117 is "available", this file shall be present.
This EF contains information about which SIP and non SIP Services are 3GPP PS Data Off Exempt in Home and/or roaming.
If service No. 131 is "available", byte1 contains the 3GPP PS Data Off Exempt status for services in the Home and byte 2 contains the 3GPP PS Data Off Exempt status for services in roaming.
If service No. 131 is "not available", byte1 contains 3GPP PS Data Off Exempt status for services for both Home and roaming. The ME shall ignore byte2 in that case.
Identifier: '6FF9'Structure: transparentOptional
File size: 4 byteUpdate activity: low
Access Conditions:
READPIN
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1-4SIP and non-SIP Exempt ServicesM4 bytes
SIP and non-SIP Exempt Services
Contents:
the services that are 3GPP PS Data Off exempt as specified in TS 22.011.
Coding:
each service that can be 3GPP PS Data Off exempt is coded on one bit.
Byte 1:
b8 b7 b6 b5 b4 b3 b2 b1
RFU b7 value to be interpreted as defined for the Device_management_over_PS leaf of the Exempted_service_list in TS 24.368 b6 value to be interpreted as defined for the Bearer_independent_protocol leaf of the Exempted_service_list in TS 24.368 b5 value to be interpreted as defined for the SMSoIP_exempt leaf in TS 24.167 b4 value to be interpreted as defined for the SSP_XCAP_config_exempt leaf in TS 24.424 b3 value to be interpreted as defined for the MMTEL_video_exempt leaf in TS 24.275 b2 value to be interpreted as defined for the MMTEL_voice_exempt leaf in TS 24.275 b1 value to be interpreted as defined for the USSI_exempt leaf in TS 24.391
 
Byte 2 (if valid):
b8 b7 b6 b5 b4 b3 b2 b1
RFU b7 value to be interpreted as defined for the Device_management_over_PS leaf of the Exempted_service_list_roaming in TS 24.368 b6 value to be interpreted as defined for the Bearer_independent_protocol leaf of the Exempted_service_list_roaming in TS 24.368 b5 value to be interpreted as defined for the SMSoIP_roaming_exempt leaf in TS 24.167 b4 value to be interpreted as defined for the SSP_XCAP_config_roaming_exempt leaf in TS 24.424 b3 value to be interpreted as defined for the MMTEL_video_roaming_exempt leaf in TS 24.275 b2 value to be interpreted as defined for the MMTEL_voice_roaming_exempt leaf in TS 24.275 b1 value to be interpreted as defined for the USSI_roaming_exempt leaf in TS 24.391
 
Bytes 3 to 4 are RFU.
Up

4.2.110  EF3GPPPSDataOffservicelist (3GPP PS Data Off Service List) |R14|  p. 126

If service No. 118 is "available", this file shall be present. This file contains a list of particular IMS services not defined by 3GPP, where each such IMS service is identified by an IMS communication service identifier. (See TS 22.011). The usage of this file is described in clause 4.17 of TS 24.229, clause B.3.1.5 of TS 24.229 and clause L.3.1.5 of TS 24.229.
Identifier: '6FFA'Structure: linear fixedOptional
Record length: X bytesUpdate activity: low
Access Conditions:
READPIN
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to XICSI TLV objectMX bytes
ICSI TLV object
Contents:
The content and coding is defined below.
Coding of the ICSI TLV objects
Length Description Value Status
1 byteICSI TLV TAG'80'M
1 byteLength of ICSIYM
Y bytesICSI value-M
 
Coding:
IMS Communication Service Identifier: shall be coded as specified in TS 24.229.
Up

4.2.111  EFXCAPConfigData (XCAP Configuration Data) |R14|  p. 127

If service No. 120 is "available", this file shall be present.
This EF contains the XCAP configuration data object as specified in TS 24.424, OMA OMA-TS-XDM_MO-V1_1-20080627-A [103] and OMA-DDS-DM_ConnMO-V1_0-20081107-A [100]:
For the structure, content and coding of this file, see EFXCAPConfigData in TS 31.103.
Up

4.2.112  EFEARFCNList (EARFCN list for MTC/NB-IOT UEs) |R15|  p. 127

If Service No. 121 is "available", this file shall be present.
This EF contains NAS configuration MO having a list of EARFCNs and associated geographical area coordinates configured in the UE for initial cell search of MTC carrier or NB-IoT carrier.
Identifier: '6FFD'Structure: transparentOptional
File size: X bytesUpdate activity: low
Access Conditions:
READALWAYS
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to ZEARFCN List TLV data objectMZ bytes
This EF contains one or more EARFCN List TLV data objects
EARFCN List information:
Description Value M/O/C Length (bytes)
EARFCN List TLV 'A0'M1
LengthXMNote 1
EARFCN Tag'80'M1
LengthNote2M1
EARFCN value--MNote2
Geographical Area - Polygon Tag'81'M1
Length6*n (n>2)MNote 1
Geographical Area - Polygon value--M6*n (n>2)
NOTE 1:
The length is coded according to ISO/IEC 8825-1 [35].
NOTE 2:
EARFCN is coded in 4 bytes, as specified in TS 36.101.
Each EARFCN List TLV data object shall contain one EARFCN and one or more Geographical Area objects.
Geographical Area - Polygon Tag '81'
Contents:
A geographical area defined by a polygon with 3 or more points.
Coding:
Bytes Description M/O Length
1 to 3Latitude of point 1M3 bytes
4 to 6Longitude of point 1M3 bytes
7 to 9Latitude of point 2M3 bytes
10 to 12Longitude of point 2M3 bytes
13 to 15Latitude of point 3M3 bytes
16 to 18Longitude of point 3M3 bytes
19 to 21Latitude of point 4O3 bytes
22 to 24Longitude of point 4O3 bytes
…
(6n-5) to 6n-3Latitude of point nO3 bytes
(6n-2) to 6nLongitude of point nO3 bytes
Latitude and longitude are coded as defined in clause 6.1 of TS 23.032.
Up

4.2.113  EFMuDMiDConfigData (MuD and MiD Configuration Data) |R16|  p. 128

If service No. 134 is "available", this file shall be present.
This EF contains the MuD and MiD configuration data object as specified in TS 24.175:
For the structure, content and coding of this file, see EFMuDMiDConfigData in TS 31.103.
Up

4.2.114  EFeAKA (enhanced AKA support) |R18|  p. 128

The file EFeAKA stores information about the support of the enhanced AKA. The content of the EF may be updated via OTA. The content of this EF is internal to the USIM.
It contains information if the enhanced SQN calculation as defined in TS 33.102 Annex J is supported by the USIM. This information can be used by the USIM internally to identify which SQN calculation to use.
Identifier: '6F01'Structure: transparentOptional
File size: X bytes, (X≥1)Update activity: low
Access Conditions:
READADM
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 - XeAKA supportMX bytes
eAKA support
Contents
indicates the support of the enhanced SQN calculation
Coding
the support is indicated by bit 1 in Byte 1 as defined below
b8 b7 b6 b5 b4 b3 b2 b1
RFU b1=0:
enhanced SQN calculation not supported
b1=1:
enhanced SQN calculation supported
All other bytes are RFU.
Up

4.2.115  EFOCST ("Operator controlled signal threshold per access technology") |R18|  p. 129

If Service No. 148 is "available", this file shall be present.
The file EFOCST contains the indication of whether SENSE is enabled by the operator. It also contains "Operator controlled signal threshold per access technology" parameters as specified in TS 23.122.
Identifier: '6F02'Structure: transparentOptional
File size: X bytes, (X≥1)Update activity: low
Access Conditions:
READPIN
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1SENSE enabled by operatorM1
2 - X+1 "Operator controlled signal threshold per access technology" parameter TLV object MX bytes
SENSE enabled by operator
Contents
The indication of whether UE is configured for using SENSE.
Coding
SENSE enabled by operator is coded in one byte as follows:
b8 b7 b6 b5 b4 b3 b2 b1
RFU, bit = 0 Value '1' indicates Operator has configured UE to use SENSE, hence UE shall use the Operator controlled signal threshold per access technology parameters as described in TS 23.122
Operator controlled signal threshold per access technology parameter TLV data object
Description Value M/O/C Length (bytes)
Operator controlled signal threshold per access technology tag'80'M1
Length3nMNote
Access Technology 1--C2
Operator controlled signal threshold per access technology 1--C1
…
Access Technology n--C2
Operator controlled signal threshold per access technology n--C1
 
NOTE:
The length is coded according to ISO/IEC 8825-1 [35]
Access Technology
Contents:
Specific Access Technology of the PLMN for which an operator controlled signal threshold per access technology is defined.
Coding:
See EFPLMNwACT for coding.
Operator controlled signal threshold per access technology
Contents:
Operator controlled signal threshold per access technology value for an access technology.
Coding:
Operator controlled signal threshold per access technology value for a specified access technology is coded on 1 byte using hexadecimal coding. The Operator controlled signal threshold per access technology value is to be interpreted as Dezibel Milliwatt (dBm).
Unused bytes shall be set to 'FF'.
Up

Up   Top   ToC