4.6 Contents of DFs at the TELECOM level
31.1023GPPCharacteristics of the Universal Subscriber Identity Module (USIM) applicationRelease 17TS
4.6.0 List of DFs at the TELECOM level
DFs may be present as child directories of DFTELECOM. The following DFs have been defined:
– DFGRAPHICS ‘5F50’.
– DFPHONEBOOK ‘5F3A’.
(DF for public phone book. This DF has the same structure as DFPHONEBOOK under ADF USIM).
– DFMULTIMEDIA ‘5F3B’.
– DFMMSS ‘5F3C’
(The contents of DF for MMSS are defined in C.S0074-A [53]. This DF for MMSS is not applicable to 3GPP only terminals).
– DFMCS ‘5F3D’.
– DFV2X ‘5F3E’.
4.6.1 Contents of files at the DFGRAPHICS level
The Efs in the Dedicated File DFGRAPHICS contain graphical information.
4.6.1.1 EFIMG (Image)
Each record of this EF identifies instances of one particular graphical image, which graphical image is identified by this EF’s record number.
Image instances may differ as to their size, having different resolutions, and the way they are coded, using one of several image coding schemes.
As an example, image k may represent a company logo, of which there are i instances in the UICC, of various resolutions and perhaps encoded in several image coding schemes. Then, the i instances of the company’s logo are described in record k of this EF.
|
Identifier: ‘4F20’ |
Structure: linear fixed |
Optional |
||||
|
Record length: 9n+1 or 9n+2 bytes, (n ≥ 1) |
Update activity: low |
|||||
|
Access Conditions: READ PIN UPDATE ADM DEACTIVATE ADM ACTIVATE ADM |
||||||
|
Bytes |
Description |
M/O |
Length |
|||
|
1 |
Number of Actual Image Instances |
M |
1 byte |
|||
|
2 to 10 |
Descriptor of Image Instance 1 |
M |
9 bytes |
|||
|
11 to 19 |
Descriptor of Image Instance 2 |
O |
9 bytes |
|||
|
: |
: |
: |
: |
|||
|
9(n-1)+2 to 9n+1 |
Descriptor of Image Instance n |
O |
9 bytes |
|||
|
9n + 2 |
RFU (see TS 31.101 [11]) |
O |
1 byte |
|||
‑ Number of Actual Image Instances.
Contents:
– this byte gives the number of actual image instances described in the following data items (i.e. unused descriptors are not counted).
Coding:
– binary.
‑ Image Instance Descriptor
Contents:
– a description of an image instance.
Coding:
– Byte 1: Image Instance Width
Contents:
– this byte specifies the image instance width, expressed in raster image points.
Coding:
– binary.
Byte 2: Image Instance Height.
Contents:
– this byte specifies the image instance height, expressed in raster image points.
Coding:
– binary.
Byte 3: Image Coding Scheme.
Contents:
– this byte identifies the image coding scheme that has been used in encoding the image instance.
Coding:
– ’11’ – basic image coding scheme as defined in annex B;
– ’21’ – colour image coding scheme as defined in annex B;
– ’22’ – colour image coding scheme with transparency as defined in annex B;
other values are reserved for future use.
Bytes 4 and 5: Image Instance Data File Identifier.
Contents:
– these bytes identify an EF which is the image instance data file (see clause 4.6.1.2), holding the actual image data for this particular instance.
Coding:
– byte 4: high byte of Image Instance Data File Identifier;
– byte 5: low byte of Image Instance Data File Identifier.
Bytes 6 and 7: Offset into Image Instance Data File.
Contents:
– these bytes specify an offset into the transparent Image Instance Data File identified in bytes 4 and 5. The data for this image instance is found starting at this offset in the Image Instance Data File.
Coding:
– byte 6: high byte of offset into Image Instance Data File;
byte 7: low byte of offset into Image Instance Data File.
Bytes 8 and 9: Length of Image Instance Data.
Contents:
– these bytes yield the length of the image instance data, starting at the offset identified in bytes 6 and 7. For the colour image coding scheme, as defined in annex B, the length of image instance data excludes the CLUT.
Coding:
– byte 8: high byte of Image Instance Data length;
– byte 9: low byte of Image Instance Data length.
NOTE: Transparent image instance data longer than 256 bytes may be read using successive READ BINARY commands.
4.6.1.2 EFIIDF (Image Instance Data Files)
Residing under DFGRAPHICS, there may be several image instance data files. Each Image Instance Data File contains data for one or more image instances. These Efs containing image instance data shall have the following attributes:
|
Identifier: ‘4FXX’ |
Structure: transparent |
Optional |
||||
|
File size: Y bytes |
Update activity: low |
|||||
|
Access Conditions: READ PIN UPDATE ADM DEACTIVATE ADM ACTIVATE ADM |
||||||
|
Bytes |
Description |
M/O |
Length |
|||
|
1 to Y |
Image Instance Data |
M |
Y bytes |
|||
Contents and coding:
– Image instance data are accessed using the image instance descriptors provided by EFIMG (see clause 4.6.1.1).
The identifier ‘4FXX’ shall be different from one image instance data file to the other. For the range of ‘XX’, TS 31.101 [11]. The length Y may be different from one image instance data file to the other.
4.6.1.3 EFICE_graphics (In Case of Emergency – Graphics)
This EF contains ICE graphical information, according to TS 22.101 [24].
This file shall be deactivated if the user does not wish the ICE information contained in this file to be available and activated if the user wishes the ICE information in this file to be available.
For this EF the Total File Size data object shall be present within the FCP template in order for the ME to fit the picture to the available memory.
Structure of EFICE_graphics at DFgraphics-level
|
Identifier: ‘4F21’ |
Structure: BER-TLV |
Optional |
|||
|
SFI: Optional |
|||||
|
Record length: X |
Update activity: low |
||||
|
Access Conditions: READ ALWAYS UPDATE PIN DEACTIVATE PIN or Issuer Specified PIN (see Note) ACTIVATE PIN or Issuer Specified PIN (see Note) |
|||||
|
Bytes |
Description |
M/O |
Length |
||
|
1 to X |
ICE graphics Data object |
M |
X bytes |
||
|
Note: The Issuer Specified PIN is a PIN with a global key reference (see TS 31.101 [11]) specified by the card Issuer. |
|||||
– ICE graphics Data Object
Coding of the ICE graphics Data Objects
|
Length |
Description |
Coding |
Status |
|
1 to T bytes (T ≤ 3) |
ICE graphics Data Object tag |
As defined in TS 31.101 [11] for BER-TLV structured files |
M |
|
1 to L (L ≤ 4) |
ICE graphics Data Object length |
As defined in TS 31.101 [11] for BER-TLV structured files |
M |
|
X-L-T bytes |
ICE graphics Content |
JPEG format |
M |
4.6.1.4 Void
4.6.1.5 Void
4.6.2 Contents of files at the DFPHONEBOOK under the DFTELECOM
This DF has the same structure as DFPHONEBOOK under the ADFUSIM.
4.6.3 Contents of files at the DFMULTIMEDIA level
The Efs in the Dedicated File DFMULTIMEDIA contain multimedia information. This DF shall be present if service n°67 is available, i.e. if the card supports MMS storage.
4.6.3.1 EFMML (Multimedia Messages List)
If service n°67 is "available", this file shall be present.
This file contains information about the MM data stored in EFMMDF. MM information are encapsulated in a BER-TLV data object. Each data object in EFMML points to a corresponding MM in EFMMDF.
|
Identifier: ‘4F47’ |
Structure: BER-TLV |
Optional |
|||
|
Update activity: low |
|||||
|
Access Conditions: READ PIN UPDATE PIN DEACTIVATE ADM ACTIVATE ADM |
|||||
|
Bytes |
Description |
M/O |
Length |
||
|
1 to X |
MM Descriptor Data Object(s) |
M |
X bytes |
||
– MM Descriptor Data Object
The content and coding are defined below:
Coding of the MM Descriptor Data Objects
|
Length |
Description |
Coding |
Status |
|
1 to A bytes (A ≤ 3) |
MM Descriptor Data Object tag |
As defined in TS 31.101 [11] for BER-TLV structured files |
M |
|
1 to B bytes (B ≤ 4) |
MM Descriptor Data Object length |
As defined in TS 31.101 [11] for BER-TLV structured files |
M |
|
1 byte |
MMS Implementation tag ’80’ |
M |
|
|
1 byte |
MMS Implementation length |
M |
|
|
1 byte |
MMS Implementation |
See below |
M |
|
1 byte |
MM File Identifier / SFI tag ’81’ |
M |
|
|
1 byte |
MM File Identifier / SFI length |
M |
|
|
1 or 2 bytes |
MM File Identifier / SFI |
See below |
M |
|
1 byte |
MM Content Data Object Tag tag ’82’ |
M |
|
|
1 byte |
MM Content Data Object Tag length |
M |
|
|
1 to C bytes (C ≤ 3) |
MM Content Data Object Tag |
See below |
M |
|
1 byte |
MM Size tag ’83’ |
M |
|
|
1 byte |
MM Size length |
M |
|
|
1 to D bytes (D ≤ 4) |
MM Size in bytes |
See below |
M |
|
1 byte |
MM Status tag ’84’ |
M |
|
|
1 byte |
MM Status length |
M |
|
|
2 bytes |
MM Status |
See below |
M |
|
1 byte |
MM Alpha Identifier tag ’85’ |
M |
|
|
1 byte |
MM Alpha Identifier length |
M |
|
|
1 to E bytes |
MM Alpha Identifier |
See below |
M |
– MMS Implementation
Contents:
The MMS Implementation indicates the used implementation type, e.g. WAP.
Coding:
Allocation of bits:
Bit number Parameter indicated
1 WAP implementation of MMS
2 to 8 Reserved for future use
Bit value Meaning
0 Implementation not supported.
1 Implementation supported.
– MM File Identifier / SFI
Contents:
file identifier or SFI of EFMMDF which contains the actual MM message. If the length of this TLV object is equal to 1 then the content indicates the SFI of the EFMMDF, the SFI is coded on b1 to b5. Otherwise the TLV contains the file identifier.
Coding:
according to TS 31.101 [11].
– MM Content Data Object Tag
Contents:
tag indentifying a MM (i.e. identifying a data object) within EFMMDF.
Coding:
according to TS 31.101 [11].
– MM Size
Contents:
size of the corresponding MM stored in EFMMDF.
Coding:
according to TS 31.101 [11].
– MM Status
Contents:
The status bytes contain the status information of the stored Multimedia Message.
Coding:
First byte:
bit b1 indicates whether the MM has been read or not. Bit b2 indicates the MM forwarding status. Bit b3 indicates whether it is a received MM or an originated MM. Bits b4 to b8 are reserved for future use.
Second byte:
Coding of the second byte depends on whether the MM has been identified as a received MM or originated MM in the first byte:
– Received MM coding:
bits b1 and b2 are used to provide information on Read-reply reports. Bits b3 to b8 are reserved for future use.
– Originated MM coding:
bit b1 is used to provide information on Delivery-report. Bits b2 to b8 are reserved for future use.
First byte:
|
b8 |
b7 |
b6 |
b5 |
b4 |
b3 |
b2 |
b1 |
|||||||||||
|
MM read, bit = 1 / MM not read, bit = 0 |
||||||||||||||||||
|
MM forwarded, bit = 1 |
||||||||||||||||||
|
Received MM, bit = 1 / Originated MM, bit = 0 |
||||||||||||||||||
|
RFU, bit = 0 |
||||||||||||||||||
Second byte coding for Received MM:
|
b8 |
b7 |
b6 |
b5 |
b4 |
b3 |
b2 |
b1 |
|||||||||||
|
Read-reply report requested, bit = 1 |
||||||||||||||||||
|
Read-reply report sent, bit = 1 |
||||||||||||||||||
|
Read-reply report created, bit = 1 |
||||||||||||||||||
|
Delivery report requested, bit = 1 |
||||||||||||||||||
|
Delivery report creation allowed, bit = 1 |
||||||||||||||||||
|
RFU, bit = 0 |
||||||||||||||||||
Second byte coding for Originated MM:
|
b8 |
b7 |
b6 |
b5 |
b4 |
b3 |
b2 |
b1 |
|||||||||||
|
Delivery report received, bit = 1 |
||||||||||||||||||
|
Delivery report requested, bit = 1 |
||||||||||||||||||
|
Read-Reply report requested, bit = 1 |
||||||||||||||||||
|
Read-Reply report received, bit = 1 |
||||||||||||||||||
|
MM sent, bit = 1 |
||||||||||||||||||
|
RFU, bit = 0 |
||||||||||||||||||
– MM Alpha Identifier
Contents:
information about the MM to be displayed to the user (e.g. sender, subject, date etc).
Coding:
this alpha identifier shall use either:
– the SMS default 7‑bit coded alphabet as defined in TS 23.038 [5] with bit 8 set to 0. The alpha identifier shall be left justified. Unused bytes shall be set to ‘FF’;
– or one of the UCS2 coded options as defined in the annex of TS 31.101 [11].
4.6.3.2 EFMMDF (Multimedia Messages Data File)
If service n°67 is "available", this file shall be present.
Residing under DFMULTIMEDIA, this EF contains Multimedia Messages data. The structure of this EF is BER-TLV (see TS 31.101 [11]). Each MM in this file is identified by a tag. The tag value for a particular MM in this file is stored in EFMML.
|
Identifier: ‘4F48’ |
Structure: BER-TLV |
Optional |
||||
|
Update activity: low |
||||||
|
Access Conditions: READ PIN UPDATE PIN DEACTIVATE ADM ACTIVATE ADM |
||||||
|
Bytes |
Description |
M/O |
Length |
|||
|
1 to X |
MM Content Data Object(s) |
M |
X bytes |
|||
– MM Content Data Object
The content and coding are defined below:
Coding of the MM Content Data Objects
|
Length |
Description |
Coding |
Status |
|
1 to T bytes (T ≤ 3) |
MM Content Data Object tag |
As defined in TS 31.101 [11] for BER-TLV structured files |
M |
|
1 to L (L ≤ 4) |
MM Content Data Object length |
As defined in TS 31.101 [11] for BER-TLV structured files |
M |
|
X-L-T bytes |
MM Content |
According to MMS Implementation |
M |
Contents:
The Multimedia Message content consists of MM headers and a message body. The content of the Multimedia Message data depends on whether the MM has been identified as a received MM or an originated MM:
– For a received message, the stored Multimedia Message data consists of the information elements (i.e. relevant MM control information and MM content) of the MM1_retrieve.RES (see TS 23.140 [38]).
– For an originated message, the stored Multimedia Message data consists of the information elements (i.e. relevant MM control information and MM content) of the MM1_submit.REQ (see TS 23.140 [38]).
Coding:
The MM data encapsulation scheme and encoding rules are defined by the MMS Implementation.
4.6.4 Contents of files at the DFMCS level
The EFs in the Dedicated File DFMCS contain management objects related to Mission Critical Services (including MCPTT, MCS, MCData, MCVideo), as specified in 3GPP TS 24.483 [89].
4.6.4.1 EFMST (MCS Service Table)
If service n°109 is "available" in the USIM Service Table or service n°15 is "available" in the ISIM Service Table, this file shall be present. This EF indicates the coding of the MCS management objects and which MCPTT, MCS, MCData or MCVideo services are available. If a service is not indicated as available in the MCS Service Table, the ME shall not select this service.
|
Identifier: ‘4F01’ |
Structure: transparent |
Optional |
||||
|
SFI: ’01’ |
||||||
|
File size: X bytes, (X ≥ 2) |
Update activity: low |
|||||
|
Access Conditions: READ PIN UPDATE ADM DEACTIVATE ADM ACTIVATE ADM |
||||||
|
Bytes |
Description |
M/O |
Length |
|||
|
1 |
Coding of the MCS management objects |
M |
1 byte |
|||
|
2 |
Services n°1 to n°8 |
M |
1 byte |
|||
|
3 |
Services n°9 to n°16 |
O |
1 byte |
|||
|
etc. |
||||||
|
X |
Services n°(8X‑7) to n°(8X) |
O |
1 byte |
|||
Coding of the MCS management objects
Contents:
Indicates the coding used for all the MCS management objects stored in the DFMCS.
Coding:
A value of ’00’ indicates the XML format described in TS 24.483 [89]. All other values are reserved.
The EF shall contain at least one byte for services. Further bytes may be included, but if the EF includes an optional byte, then it is mandatory for the EF to also contain all bytes before that byte. Other services are possible in the future and will be coded on further bytes in the EF.
|
‑Services |
||
|
Contents: |
Service n°1: |
MCPTT UE configuration data |
|
Service n°2: |
MCPTT User profile data |
|
|
Service n°3: |
MCS Group configuration data |
|
|
Service n°4: |
MCPTT Service configuration data |
|
|
Service n°5: |
MCS UE initial configuration data |
|
|
Service n°6: |
MCData UE configuration data |
|
|
Service n°7: |
MCData user profile data |
|
|
Service n°8: |
MCData service configuration data |
|
|
Service n°9: |
MCVideo UE configuration data |
|
|
Service n°10: |
MCVideo user profile data |
|
|
Service n°11: |
MCVideo service configuration data |
Coding:
Same as coding of USIM Service Table.
4.6.4.2 EFMCS_ CONFIG (MCS configuration data)
If at least one of the services is "available" in the MCS Service Table, this file shall be present.
This EF contains zero, one or more configuration data objects, as specified in 3GPP TS 24.483 [89].
|
Identifier: ‘4F02’ |
Structure: BER-TLV |
Optional |
||||
|
SFI: ’02’ |
||||||
|
File size: X bytes |
Update activity: low |
|||||
|
Access Conditions: READ PIN UPDATE ADM DEACTIVATE ADM ACTIVATE ADM |
||||||
|
Bytes |
Description |
M/O |
Length |
|||
|
1 to Y |
Mission Critical Services configuration data object |
O |
Y bytes |
|||
The MCS configuration data is encoded as specified in the MCS Service Table.
Unused bytes shall be set to ‘FF’.
Mission Critical Services configuration data object tag:
|
MCPTT configuration data objects |
Tag Values |
Condition |
|
MCPTT UE configuration data |
’80’ |
Shall be present if service n°1 is "available" in the MCS service table |
|
MCPTT user profile data |
’81’ |
Shall be present if service n°2 is "available" in the MCS service table |
|
MCS Group configuration data |
’82’ |
Shall be present if service n°3 is "available" in the MCS service table |
|
MCPTT Service configuration data |
’83’ |
Shall be present if service n°4 is "available" in the MCS service table |
|
MCS UE initial configuration data |
’84’ |
Shall be present if service n°5 is "available" in the MCS service table |
|
MCData UE configuration data |
’85’ |
Shall be present if service n°6 is "available" in the MCS service table |
|
MCData user profile data |
’86’ |
Shall be present if service n°7 is "available" in the MCS service table |
|
MCData service configuration data |
’87’ |
Shall be present if service n°8 is "available" in the MCS service table |
|
MCVideo UE configuration data |
’88’ |
Shall be present if service n°9 is "available" in the MCS service table |
|
MCVideo user profile data |
’89’ |
Shall be present if service n°10 is "available" in the MCS service table |
|
MCVideo service configuration data |
‘8A’ |
Shall be present if service n°11 is "available" in the MCS service table |
4.6.4.3 Void
4.6.4.4 Void
4.6.4.5 Void
4.6.5 Contents of files at the DFV2X level
4.6.5.1 V2X configuration data related files
The EFs in the Dedicated File DFV2X contain configuration data related to V2X, as specified in 3GPP TS 24.386 [98] and 3GPP TS 24.587 [112].
4.6.5.2 EFVST (V2X Service Table)
If service n°119 is "available" in the USIM Service Table, this file shall be present. This EF indicates the coding of the V2X data and which V2X services are available. If a service is not indicated as available in the V2X Service Table, the ME shall not select this service.
|
Identifier: ‘4F01’ |
Structure: transparent |
Optional |
||||
|
SFI: ’01’ |
||||||
|
File size: X bytes, (X ≥ 2) |
Update activity: low |
|||||
|
Access Conditions: READ PIN UPDATE ADM DEACTIVATE ADM ACTIVATE ADM |
||||||
|
Bytes |
Description |
M/O |
Length |
|||
|
1 |
Coding of the V2X management objects |
M |
1 byte |
|||
|
2 |
Services n°1 to n°8 |
M |
1 byte |
|||
|
3 |
Services n°9 to n°16 |
O |
1 byte |
|||
|
etc. |
||||||
|
X |
Services n°(8X‑7) to n°(8X) |
O |
1 byte |
|||
Coding of the V2X data
Contents:
Indicates the coding used for the V2X data stored in the DFV2X.
Coding:
A value of ’00’ indicates the XML format described in TS 24.385 [97]. A value of ’01’ indicates according to 3GPP TS 24.588 [113]. All other values are reserved.
Editor’s Note: the definition of other encoding formats is for future study.
The EF shall contain at least one byte for services. Further bytes may be included, but if the EF includes an optional byte, then it is mandatory for the EF to also contain all bytes before that byte. Other services are possible in the future and will be coded on further bytes in the EF.
|
Services |
||
|
Contents: |
Service n°1: |
V2X configuration data |
|
Service n°2: |
V2X policy configuration data over PC5 |
|
|
Service n°3: |
V2X policy configuration data over Uu |
Coding:
Same as coding of USIM Service Table.
4.6.5.3 EFV2X_CONFIG (V2X configuration data)
This EF contains zero, one or more V2X configuration data objects, as specified in TS 24.385 [97].
|
Identifier: ‘4F02’ |
Structure: BER-TLV |
Optional |
||||
|
SFI: ’02’ |
||||||
|
File size: X bytes |
Update activity: low |
|||||
|
Access Conditions: READ PIN UPDATE ADM DEACTIVATE ADM ACTIVATE ADM |
||||||
|
Bytes |
Description |
M/O |
Length |
|||
|
1 to X |
V2X configuration data |
O |
X bytes |
|||
The V2X configuration data is encoded as specified in the V2X Service Table.
Unused bytes shall be set to ‘FF’.
V2X configuration data object tag:
|
V2X configuration data objects |
Tag Values |
Condition |
|
V2X configuration data |
’80’ |
Shall be present if service n°1 is "available" in the V2X service table |
4.6.5.4 EFV2XP_PC5 (V2X data policy over PC5)
If service n°2 is "available" in EFVST, this file shall be present. This EF contains V2X in 5GS UE policies over PC5. The format of the V2X in 5GS UE policies over PC5 are specified in 3GPP TS 24.588 [113].
|
Identifier: ‘4F03’ |
Structure: Transparent |
Optional |
||||
|
SFI: Optional |
||||||
|
File size: X bytes bytes, (X ≥ 3) |
Update activity: low |
|||||
|
Access Conditions: READ PIN UPDATE ADM DEACTIVATE ADM ACTIVATE ADM |
||||||
|
Bytes |
Description |
M/O |
Length |
|||
|
1 to X |
V2X data policy over PC5 TLV objects |
M |
X bytes |
|||
The V2X in 5GS UE policies over PC5 data object parameters tags:
|
Description |
Tag Value |
|
V2X data policy over PC5 Tag |
‘A0’ |
|
Served by E-UTRA or served by NR Tag |
’80’ |
|
Not served by E-UTRA and not served by NR Tag |
’81’ |
|
V2X service identifier to Tx profiles mapping rules Tag |
’82’ |
|
Privacy config Tag |
’83’ |
|
V2X communication over PC5 in E-UTRA Tag |
’84’ |
|
V2X communication over PC5 in NR Tag |
’85’ |
The V2X in 5GS UE policies over PC5 contents:
|
Description |
Value |
M/O |
Length (bytes) |
|
V2X data policy over PC5 Tag |
‘A0’ |
M |
1 |
|
Length |
Note 1 |
M |
Note 2 |
|
Validity timer |
— |
M |
X1 |
|
Indicator bits |
— |
M |
1 |
|
Served by E-UTRA or served by NR Tag |
’80’ |
M |
1 |
|
Length |
X2 |
M |
Note 2 |
|
Served by E-UTRA or served by NR information |
— |
M |
X2 |
|
Not served by E-UTRA and not served by NR Tag |
’81’ |
O |
1 |
|
Length |
X3 |
O |
Note 2 |
|
Not served by E-UTRA and not served by NR information |
— |
O |
X3 |
|
V2X service identifier to Tx profiles mapping rules Tag |
’82’ |
O |
1 |
|
Length |
X4 |
O |
Note 2 |
|
V2X service identifier to Tx profiles mapping rules information |
— |
X4 |
|
|
Privacy config Tag |
’83’ |
O |
1 |
|
Length |
X5 |
O |
Note 2 |
|
Privacy config information |
— |
X5 |
|
|
V2X communication over PC5 in E-UTRA Tag |
’84’ |
O |
1 |
|
Length |
X6 |
O |
Note 2 |
|
V2X communication over PC5 in E-UTRA information |
— |
O |
X6 |
|
V2X communication over PC5 in NR Tag |
’85 |
O |
1 |
|
Length |
X7 |
O |
Note 2 |
|
V2X communication over PC5 in NR Information |
— |
O |
X7 |
|
Note 1: This is the total size of the constructed TLV object. Note 2: The length is coded according to ISO/IEC 8825-1 [35]. |
|||
– Validity timer
Contents:
‑ The validity timer contains the timer for controlling the validity of 5GS UE policies for V2X communication over PC5.
Contents:
‑ The validity timer is encoded as shown in figure 5.3.1.1 and table 5.3.1.1 of 3GPP TS 24.588 [113].
– Indicator bits
Contents:
‑ The indicator bits contains bit indications about 5GS UE policies for V2X communication over PC5.
Contents:
‑ The indicator bits are encoded as shown in figure 5.3.1.1 and table 5.3.1.1 of 3GPP TS 24.588 [113].
– Served by E-UTRA or served by NR Tag ’80’
Contents:
‑ The served by E-UTRA or served by NR contains configuration parameters for V2X communication over PC5 when the UE is served by E-UTRA or served by NR.
Contents:
‑ The served by E-UTRA or served by NR is encoded as shown in figures 5.3.1.3 to 5.3.1.5 and tables 5.3.1.3 to 5.3.1.5 of 3GPP TS 24.588 [113].
– Not served by E-UTRA and not served by NR Tag ’81’
Contents:
‑ The not served by E-UTRA and not served by NR contains configuration parameters for V2X communication over PC5 when the UE is served by E-UTRA or served by NR.
Contents:
‑ The not served by E-UTRA and not served by NR is encoded as shown in figures 5.3.1.6 to 5.3.1.11 and tables 5.3.1.6 to 5.3.1.11 of 3GPP TS 24.588 [113].
– V2X service identifier to Tx profiles mapping rules Tag ’82’
Contents:
‑ The V2X service identifier to Tx profiles mapping rules contains contains a list of V2X service identifier to Tx profiles mapping rules.
Contents:
‑ The V2X service identifier to Tx profiles mapping rules is encoded as shown in figures 5.3.1.12 to 5.3.1.14 and tables 5.3.1.12 to 5.3.1.14 of 3GPP TS 24.588 [113].
– Privacy config Tag ’83’
Contents:
‑ The privacy config contains configuration parameters for privacy configuration.
Contents:
‑ The private config is encoded as shown in figures 5.3.1.15 to 5.3.1.18 and tables 5.3.1.15 to 5.3.1.18 of 3GPP TS 24.588 [113].
– V2X communication over PC5 in E-UTRA Tag ’84’
Contents:
‑ The V2X communication over PC5 in E-UTRA contains configuration parameters for V2X communication over PC5 in E-UTRA.
Contents:
‑ The V2X communication over PC5 in E-UTRA is encoded as shown in figures 5.3.1.19 to 5.3.1.30 and tables 5.3.1.19 to 5.3.1.30 of 3GPP TS 24.588 [113].
– V2X communication over PC5 in NR Tag ’85’
Contents:
‑ The V2X communication over PC5 in NR contains configuration parameters for V2X communication over PC5 in NR.
Contents:
‑ The V2X communication over PC5 in NR is encoded as shown in figures 5.3.1.31 to 5.3.1.58 and tables 5.3.1.31 to 5.3.1.58 of 3GPP TS 24.588 [113].
V2X in 5GS UE policies over PC5 data policy object tag:
|
V2X in 5GS UE policies over PC5 data policy |
Tag Values |
Condition |
|
V2X data policy over PC5 |
‘A0’ |
Shall be present if service n°2 is "available" in the V2X service table |
4.6.5.5 EFV2XP_Uu (V2X data policy over Uu)
If service n°3 is "available" in EFVST, this file shall be present. This EF contains V2X in 5GS UE policies over Uu. The format of the V2X in 5GS UE policies over Uu are specified in 3GPP TS 24.588 [113].
|
Identifier: ‘4F04’ |
Structure: Transparent |
Optional |
||||
|
SFI: Optional |
||||||
|
File size: X bytes bytes, (X ≥ 3) |
Update activity: low |
|||||
|
Access Conditions: READ PIN UPDATE ADM DEACTIVATE ADM ACTIVATE ADM |
||||||
|
Bytes |
Description |
M/O |
Length |
|||
|
1 to X |
V2X data policy over Uu TLV objects |
M |
X bytes |
|||
The V2X in 5GS UE policies over Uu data object parameters tags:
|
Description |
Tag Value |
|
V2X data policy over Uu Tag |
‘A0’ |
|
V2X service identifier to PDU session parameters mapping rules Tag |
’80’ |
|
PLMN infos Tag |
’81’ |
The V2X in 5GS UE policies over Uu contents:
|
Description |
Value |
M/O |
Length (bytes) |
|
V2X data policy over Uu Tag |
‘A0’ |
M |
1 |
|
Length |
Note 1 |
M |
Note 2 |
|
Validity timer |
— |
M |
X1 |
|
Indicator bits |
— |
M |
1 |
|
V2X service identifier to PDU session parameters mapping rules Tag |
’80’ |
M |
1 |
|
Length |
X2 |
M |
Note 2 |
|
V2X service identifier to PDU session parameters mapping rules information |
— |
M |
X2 |
|
PLMN infos Tag |
’81’ |
O |
1 |
|
Length |
X3 |
O |
Note 2 |
|
PLMN infos information |
— |
O |
X3 |
– Validity timer
Contents:
‑ The validity timer contains the timer for controlling the validity of 5GS UE policies for V2X communication over PC5.
Contents:
‑ The validity timer is encoded as shown in figure 5.4.1.1 and table 5.4.1.1 of 3GPP TS 24.588 [113].
– Indicator bits
Contents:
‑ The indicator bits contains bit indications about 5GS UE policies for V2X communication over PC5.
Contents:
‑ The indicator bits are encoded as shown in figure 5.4.1.1 and table 5.4.1.1 of 3GPP TS 24.588 [113].
– V2X service identifier to PDU session parameters mapping rules Tag ’80’
Contents:
‑ The V2X service identifier to PDU session parameters mapping rules contains configuration parameters for V2X service identifier to PDU session parameters mapping rules.
Contents:
‑ The V2X service identifier to PDU session parameters mapping rules is encoded as shown in figures 5.4.1.17 to 5.4.1.18 and tables 5.4.1.17 to 5.4.1.18 of 3GPP TS 24.588 [113].
– PLMN infos Tag ’81’
Contents:
‑ The PLMN infos a list of PLMNs in which the UE is configured to use V2X communication over Uu.
Contents:
‑ The not served by E-UTRA and not served by NR is encoded as shown in figures 5.4.1.2 to 5.4.1.16 and tables 5.4.1.2 to 5.4.1.16 of 3GPP TS 24.588 [113].
V2X in 5GS UE policies over Uu data policy object tag:
|
V2X in 5GS UE policies over Uu data policy |
Tag Values |
Condition |
|
V2X data policy over Uu |
‘A0’ |
Shall be present if service n°3 is "available" in the V2X service table |