Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 31.102  Word version:  18.5.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.6.5…   4.6.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.6.5  Contents of files at the DFV2X level |R14|p. 263

4.6.5.1  V2X configuration data related filesp. 263

The EFs in the Dedicated File DFV2X contain configuration data related to V2X, as specified in TS 24.386 and TS 24.587.

4.6.5.2  EFVST (V2X Service Table)p. 264

If service No. 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: transparentOptional
SFI: '01'
File size: X bytes, (X ≥ 2)Update activity: low
Access Conditions:
READPIN
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1Coding of the V2X management objectsM1 byte
2Services No. 1 to No. 8M1 byte
3Services No. 9 to No. 16O1 byte
etc.
XServices No. (8X-7) to No. (8X)O1 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. A value of '01' indicates according to TS 24.588. 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 No. 1
V2X configuration data
Service No. 2
V2X policy configuration data over PC5
Service No. 3
V2X policy configuration data over Uu
Coding:
Same as coding of USIM Service Table.
Up

4.6.5.3  EFV2X_CONFIG (V2X configuration data)p. 264

This EF contains zero, one or more V2X configuration data objects, as specified in TS 24.385.
Identifier: '4F02'Structure: BER-TLVOptional
SFI: '02'
File size: X bytesUpdate activity: low
Access Conditions:
READPIN
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to XV2X configuration dataOX 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 No. 1 is "available" in the V2X service table
Up

4.6.5.4  EFV2XP_PC5 (V2X data policy over PC5) |R16|p. 265

If service No. 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 TS 24.588.
Identifier: '4F03'Structure: TransparentOptional
SFI: Optional
File size: X bytes, (X ≥ 3)Update activity: low
Access Conditions:
READPIN
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to XV2X data policy over PC5 TLV objectsMX 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'M1
LengthNote 1MNote 2
Validity timer--MX1
Indicator bits--M1
Served by E-UTRA or served by NR Tag'80'M1
LengthX2MNote 2
Served by E-UTRA or served by NR information--MX2
Not served by E-UTRA and not served by NR Tag'81'O1
LengthX3ONote 2
Not served by E-UTRA and not served by NR information--OX3
V2X service identifier to Tx profiles mapping rules Tag'82'O1
LengthX4ONote 2
V2X service identifier to Tx profiles mapping rules information--X4
Privacy config Tag'83'O1
LengthX5ONote 2
Privacy config information--X5
V2X communication over PC5 in E-UTRA Tag'84'O1
LengthX6ONote 2
V2X communication over PC5 in E-UTRA information--OX6
V2X communication over PC5 in NR Tag'85'O1
LengthX7ONote 2
V2X communication over PC5 in NR Information--OX7
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.
Coding:
The validity timer is encoded as shown in Figure 5.3.1.1 and Table 5.3.1.1 of TS 24.588.
Indicator bits
Contents:
The indicator bits contains bit indications about 5GS UE policies for V2X communication over PC5.
Coding:
The indicator bits are encoded as shown in Figure 5.3.1.1 and Table 5.3.1.1 of TS 24.588.
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.
Coding:
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 TS 24.588.
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.
Coding:
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 TS 24.588.
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.
Coding:
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 TS 24.588.
Privacy config Tag '83'
Contents:
The privacy config contains configuration parameters for privacy configuration.
Coding:
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 TS 24.588.
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.
Coding:
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 TS 24.588.
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.
Coding:
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 TS 24.588.
 
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 No. 2 is "available" in the V2X service table
Up

4.6.5.5  EFV2XP_Uu (V2X data policy over Uu) |R16|p. 267

If service No. 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 TS 24.588.
Identifier: '4F04'Structure: TransparentOptional
SFI: Optional
File size: X bytes, (X ≥ 3)Update activity: low
Access Conditions:
READPIN
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to XV2X data policy over Uu TLV objectsMX 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'M1
LengthNote 1MNote 2
Validity timer--MX1
Indicator bits--M1
V2X service identifier to PDU session parameters mapping rules Tag'80'M1
LengthX2MNote 2
V2X service identifier to PDU session parameters mapping rules information--MX2
PLMN infos Tag'81'O1
LengthX3ONote 2
PLMN infos information--OX3
 
Validity timer
Contents:
The validity timer contains the timer for controlling the validity of 5GS UE policies for V2X communication over PC5.
Coding:
The validity timer is encoded as shown in Figure 5.4.1.1 and Table 5.4.1.1 of TS 24.588.
Indicator bits
Contents:
The indicator bits contains bit indications about 5GS UE policies for V2X communication over PC5.
Coding:
The indicator bits are encoded as shown in Figure 5.4.1.1 and Table 5.4.1.1 of TS 24.588.
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.
Coding:
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 TS 24.588.
PLMN infos Tag '81'
Contents:
The PLMN infos a list of PLMNs in which the UE is configured to use V2X communication over Uu.
Coding:
The PLMN Infos is encoded as shown in Figures 5.4.1.2 to 5.4.1.20 and Tables 5.4.1.2 to 5.4.1.18 of TS 24.588. The V2X MBS configuration and the V2X AS MBS configuration are encoded as shown in Figures 5.4.1.8A to 5.4.1.8E and Tables 5.4.1.8A to 5.4.1.8E of TS 24.588.
 
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 No. 3 is "available" in the V2X service table
Up

Up   Top   ToC