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.6  Contents of files at the DFA2X level |R18|p. 269

4.6.6.1  A2X configuration data related filesp. 269

The EFs in the Dedicated File DFA2X contain configuration and policy related data for A2X, as specified in TS 24.577 and TS 24.578.

4.6.6.2  EFAST (A2X Service Table)p. 269

If service No. 149 is "available" in the USIM Service Table, this file shall be present. If a service is not indicated as available in the A2X Service Table, the ME shall not select this service.
Identifier: '4F01'Structure: transparentOptional
SFI: '01'
File size: X bytes, (X ≥ 1)Update activity: low
Access Conditions:
READPIN
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1Services No. 1 to No. 8M1 byte
2Services No. 9 to No. 16O1 byte
XServices No. (8X-7) to No. (8X)O1 byte
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
A2X configuration data
Service No. 2
A2X policy data over PC5
Service No. 3
A2X Direct Detect And Avoid policy data over PC5
Service No. 4
A2X Direct C2 communication policy data over PC5
Service No. 5
A2X policy data over Uu
Coding:
Same as coding of USIM Service Table.
Up

4.6.6.3  EFA2X_CONFIG (A2X configuration data)p. 270

If service No. 1 is "available" in EFAST, this file shall be present. This EF contains zero, one or more A2X configuration data objects, as specified in TS 24.578.
Identifier: '4F02'Structure: TransparentOptional
SFI: '02'
File size: X bytes, (X ≥ 4)Update activity: low
Access Conditions:
READPIN
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to XA2X configuration data objectsMX bytes
The A2X configuration data object parameters tags:
Description Tag Value
A2X configuration data Tag'A0'
 
The A2X configuration data object contents:
Description Value M/O Length (bytes)
A2X configuration data Tag'A0'M1
LengthNote 1MNote 2
Indicator bits--M1
UE policy part contents Tag'80'O1
LengthX2ONote 2
UE policy part contents information--OX2
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].
 
Indicator bits
Contents:
The indicator bits contain bit indications about UE policy part type.
Coding:
The indicator bits are encoded as shown in Figure 5.2.1.1 and Table 5.2.1.1 of TS 24.578.
UE policy part contents Tag '80'
Contents:
The UE policy part contents contains A2XP info as part of UE policy.
Coding:
The UE policy part contents is encoded as shown in Figures 5.2.1.1 to 5.2.1.3 and Table 5.2.1.1 of TS 24.578.
 
The A2X configuration data is encoded as specified in the A2X Service Table.
Unused bytes shall be set to 'FF'.
A2X configuration data object tag:
A2X configuration data objects Tag Values Condition
A2X configuration data Tag'A0' Shall be present if service No. 1 is "available" in the A2X service table
Up

4.6.6.4  EFA2XP_PC5 (A2X policy data over PC5)p. 271

If service No. 2 is "available" in EFAST, this file shall be present. This EF contains A2X in 5GS UE policies over PC5. The format of the A2X in 5GS UE policies over PC5 are specified in TS 24.578.
Identifier: '4F03'Structure: TransparentOptional
SFI: '03'
File size: X bytes, (X ≥ 11)Update activity: low
Access Conditions:
READPIN
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to XA2X policy data over PC5 data objectsMX bytes
The A2X in 5GS UE policies over PC5 data object parameters tags:
Description Tag Value
A2X policy data over PC5 Tag'A0'
Served by NG-RAN Tag
'80'
Not served by NG-RAN Tag
'81'
A2X service identifier to PC5 RAT(s) and Tx profiles mapping rules Tag
'82'
Privacy config Tag
'83'
A2X communication in E-UTRA-PC5 Tag
'84'
A2X communication in NR-PC5 Tag
'85'
 
The A2X in 5GS UE policies over PC5 data object contents:
Description Value M/O Length (bytes)
A2X data policy over PC5 Tag'A0'M1
LengthNote 1MNote 2
Validity timer--M5
Indicator bits--M1
Served by NG-RAN Tag'80'M1
LengthX2MNote 2
Served by NG-RAN information--MX2
Not served by NG-RAN Tag'81'O1
LengthX3ONote 2
Not served by NG-RAN information--OX3
A2X service identifier to PC5 RAT(s) and Tx profiles mapping rules Tag'82'O1
LengthX4ONote 2
A2X service identifier to PC5 RAT(s) and Tx profiles mapping rules information--X4
Privacy config Tag'83'O1
LengthX5ONote 2
Privacy config information--X5
A2X communication in E-UTRA-PC5 Tag'84'O1
LengthX6ONote 2
A2X communication in E-UTRA-PC5 information--OX6
A2X communication in NR-PC5 Tag'85O1
LengthX7ONote 2
A2X communication in NR-PC5 Tag 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 A2X communication over PC5.
Coding:
The validity timer is encoded as shown in Figure 5.3.2.1 and Table 5.3.2.1 of TS 24.578.
Indicator bits
Contents:
The indicator bits contain bit indications about 5GS UE policies for A2X communication over PC5.
Coding:
The indicator bits are encoded as shown in Figure 5.3.2.1 and Table 5.3.2.1 of TS 24.578.
Served by NG-RAN Tag '80'
Contents:
The served by NG-RAN contains configuration parameters for A2X communication over PC5 when the UE is served by NG-RAN.
Coding:
The served by NG-RAN is encoded as shown in Figures 5.3.2.2 to 5.3.2.5 and Tables 5.3.2.2 to 5.3.2.5 of TS 24.578.
Not served by NG-RAN Tag '81'
Contents:
The not served by NG-RAN contains configuration parameters for A2X communication over PC5 when the UE is not served by NG-RAN.
Coding:
The not served by NG-RAN is encoded as shown in Figures 5.3.2.6 to 5.3.2.13 and Tables 5.3.2.6 to 5.3.2.13 of TS 24.578.
A2X service identifier to PC5 RAT(s) and Tx profiles mapping rules Tag '82'
Contents:
The A2X service identifier to PC5 RAT(s) and Tx profiles mapping rules contains a list of A2X service identifier to PC5 RAT(s) and Tx profiles mapping rules.
Coding:
The A2X service identifier to PC5 RAT(s) and Tx profiles mapping rules is encoded as shown in Figures 5.3.2.14 to 5.3.2.16 and Tables 5.3.2.14 to 5.3.2.16 of TS 24.578.
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.2.17 to 5.3.2.19 and Tables 5.3.2.17 to 5.3.2.19 of TS 24.578.
A2X communication in E-UTRA-PC5 Tag '84'
Contents:
A2X communication in E-UTRA-PC5 contains configuration parameters for A2X communication over PC5 in E-UTRA.
Coding:
A2X communication in E-UTRA-PC5 is encoded as shown in Figures 5.3.2.20 to 5.3.2.31 and Tables 5.3.2.20 to 5.3.2.31 of TS 24.578.
A2X communication in NR-PC5 Tag '85'
Contents:
The A2X communication in NR-PC5 contains configuration parameters for A2X communication over PC5 in NR.
Coding:
The A2X communication in NR-PC5 is encoded as shown in Figures 5.3.2.32 to 5.3.2.56 and Tables 5.3.2.32 to 5.3.2.56 of TS 24.578.
 
A2X in 5GS UE policies over PC5 data policy object tag:
A2X in 5GS UE policies over PC5 data policy Tag Values Condition
A2X policy data over PC5'A0' Shall be present if service No. 2 is "available" in the A2X service table
Up

4.6.6.5  EFA2X_DDAAP_PC5 (A2X Direct Detect And Avoid policy data over PC5)p. 274

If service No. 3 is "available" in EFAST, this file shall be present. This EF contains 5GS Direct Detect And Avoid policies over PC5. The format of the Direct Detect And Avoid policies over PC5 are specified in TS 24.578.
Identifier: '4F04'Structure: TransparentOptional
SFI: '04'
File size: X bytes, (X ≥ 4)Update activity: low
Access Conditions:
READPIN
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to XA2X Direct Detect And Avoid policy data over PC5 objectsMX bytes
The A2X in 5GS Direct Detect And Avoid policies over PC5 data object parameters tags:
Description Tag Value
A2X Direct Detect And Avoid policy data over PC5 Tag'A0'
A2X service identifiers for unicast communication mode of DAA deconfliction Tag'80'
A2X service identifires for broadcast communication mode of DAA deconfliction Tag'81'
 
The A2X in 5GS Direct Detect And Avoid policies over PC5 data object contents:
Description Value M/O Length (bytes)
A2X Direct Detect And Avoid policy data over PC5 Tag'A0'M1
LengthNote 1MNote 2
Indicator bits--M1
A2X service identifiers for unicast communication mode of DAA deconfliction Tag'80'O1
LengthX2ONote 2
A2X service identifiers for unicast communication mode of DAA deconfliction information--OX2
A2X service identifiers for broadcast communication mode of DAA deconfliction Tag'81'O1
LengthX3ONote 2
A2X service identifiers for broadcast communication mode of DAA deconfliction information--OX3
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].
 
Indicator bits
Contents:
The indicator bits contain bit indications about A2XUCDDI and A2XBCDDI for A2X communication over PC5.
Coding:
The indicator bits are encoded as shown in Figure 5.5.2.1 and Table 5.5.2.1 of TS 24.578.
A2X service identifiers for unicast communication mode of DAA deconfliction Tag '80'
Contents:
The A2X service identifiers for unicast communication mode of DAA deconfliction contains UE policies for DDAA over PC5.
Coding:
The A2X service identifiers for unicast communication mode of DAA deconfliction is encoded as shown in Figure 5.3.2.14 and Table 5.3.2.14 of TS 24.578.
A2X service identifiers for broadcast communication mode of DAA deconfliction Tag '81'
Contents:
The A2X service identifiers for broadcast communication mode of DAA deconfliction contains UE policies for DDAA over PC5.
Coding:
The A2X service identifiers for broadcast communication mode of DAA deconfliction is encoded as shown in Figure 5.3.2.14 and Table 5.3.2.14 of TS 24.578.
 
A2X in 5GS Direct Detect And Avoid over PC5 policy data object tag:
A2X in 5GS Direct Detect And Avoid over PC5 policy data Tag Values Condition
A2X Direct Detect And Avoid policy data over PC5 Tag'A0' Shall be present if service No. 3 is "available" in the A2X service table
Up

4.6.6.6  EFA2X_DC2P_PC5 (A2X Direct C2 communication policy data over PC5)p. 275

If service No. 4 is "available" in EFAST, this file shall be present. This EF contains direct C2 communication policies over PC5. The format of the direct C2 communication policies over PC5 are specified in TS 24.578.
Identifier: '4F05'Structure: TransparentOptional
SFI: '05'
File size: X bytes, (X ≥ 6)Update activity: low
Access Conditions:
READPIN
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to XA2X Direct C2 communication policy data over PC5 TLV objectsMX bytes
The A2X Direct C2 communication policy data over PC5 object parameters tags:
Description Tag Value
A2X Direct C2 communication policy data over PC5 Tag'A0'
Served by NG-RAN for DC2 Tag
'80'
Not served by NG-RAN for DC2 Tag
'81'
 
The A2X Direct C2 communication policy data over PC5 object contents:
Description Value M/O Length (bytes)
A2X Direct C2 communication policy data over PC5 Tag'A0'M1
LengthNote 1MNote 2
Served by NG-RAN for DC2 Tag'80'M1
LengthX1MNote 2
Served by NG-RAN for DC2 information--MX1
Not served by NG-RAN for DC2 Tag'81'O1
LengthX2ONote 2
Not served by NG-RAN for DC2 information--OX2
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].
 
Served by NG-RAN for DC2 Tag '80'
Contents:
The served by NG-RAN for DC2 contains configuration parameters for A2X communication over PC5 when the UE is served by NG-RAN using direct C2 policy.
Coding:
The served by NG-RAN for DC2 is encoded as shown in Figures 5.6.2.2 to 5.6.2.4 and Tables 5.6.2.2 to 5.6.2.4 of TS 24.578.
Not served by NG-RAN for DC2 Tag '81'
Contents:
The not served by NG-RAN for DC2 contains configuration parameters for A2X communication over PC5 when the UE is not served by NG-RAN using direct C2 policy.
Coding:
The not served by NG-RAN for DC2 is encoded as shown in Figure 5.6.2.5 and Table 5.6.2.5 of TS 24.578.
 
A2X Direct C2 communication policy data over PC5 object tag:
A2X Direct C2 communication over PC5 policy data Tag Values Condition
A2X Direct C2 communication policy data over PC5 Tag'A0' Shall be present if service No. 4 is "available" in the A2X service table
Up

4.6.6.7  EFA2XP_Uu (A2X policy data over Uu)p. 276

If service No. 5 is "available" in EFAST, this file shall be present. This EF contains A2X in 5GS UE policies over Uu. The format of the A2X in 5GS UE policies over Uu are specified in TS 24.578.
Identifier: '4F06'Structure: TransparentOptional
SFI: '06'
File size: X bytes, (X ≥ 12)Update activity: low
Access Conditions:
READPIN
UPDATEADM
DEACTIVATEADM
ACTIVATEADM
Bytes Description M/O Length
1 to XA2X data policy over Uu data objectsMX bytes
The A2X in 5GS UE policies over Uu data object parameters tags:
Description Tag Value
A2X data policy over Uu Tag'A0'
A2X service identifier to PDU session parameters mapping rules Tag
'80'
PLMN infos Tag
'81'
 
The A2X in 5GS UE policies over Uu data object contents:
Description Value M/O Length (bytes)
A2X data policy over Uu Tag'A0'M1
LengthNote 1MNote 2
Validity timer--M5
Indicator bits--M1
A2X service identifier to PDU session parameters mapping rules Tag'80'M1
LengthX2MNote 2
A2X service identifier to PDU session parameters mapping rules information--MX2
PLMN infos Tag'81'O1
LengthX3ONote 2
PLMN infos information--OX3
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 A2X communication over PC5.
Coding:
The validity timer is encoded as shown in Figure 5.7.2.1 and Table 5.7.2.1 of TS 24.578.
Indicator bits
Contents:
The indicator bits contains bit indications about 5GS UE policies for A2X communication over PC5.
Coding:
The indicator bits are encoded as shown in Figure 5.7.2.1 and Table 5.7.2.1 of TS 24.578.
A2X service identifier to PDU session parameters mapping rules Tag '80'
Contents:
The A2X service identifier to PDU session parameters mapping rules contains configuration parameters for A2X service identifier to PDU session parameters mapping rules.
Coding:
The A2X service identifier to PDU session parameters mapping rules is encoded as shown in Figures 5.7.2.17 to 5.7.2.20 and Tables 5.7.2.17 to 5.7.2.18 of TS 24.578.
PLMN infos Tag '81'
Contents:
The PLMN infos a list of PLMNs in which the UE is configured to use A2X communication over Uu.
Coding:
The PLMN Infos is encoded as shown in Figures 5.7.2.2 to 5.7.2.20 and Tables 5.7.2.2 to 5.7.2.18 of TS 24.578. The A2X MBS configuration and the A2X AS MBS configuration are encoded as shown in Figures 5.7.2.3A to 5.7.2.8E and Tables 5.7.2.3A to 5.7.2.8E of TS 24.578.
 
A2X in 5GS UE policies over Uu data policy object tag:
A2X in 5GS UE policies over Uu data policy Tag Values Condition
A2X data policy over Uu'A0' Shall be present if service No. 5 is "available" in the A2X service table
Up

Up   Top   ToC