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 23.256  Word version:  19.0.0

Top   Top   Up   Prev   Next
1…   4…   4.2…   4.2.3…   4.3…   4.4…   4.5…   5…   5.2.3…   5.2.4…   5.2.5…   5.2.5.3…   5.2.5.4…   5.2.7   5.2.8…   5.2.9…   5.3…   5.4…   5.5…   5.12…   5.13…   5.14…   6…   6.2…   6.3…   6.3.4…   A… 
6.2 High level functionality and features  6.2.1 Authorization and Provisioning for A2X communications  6.2.1.1 General  6.2.1.2 Authorization and Provisioning for A2X communications over PC5 reference point  6.2.1.2.1 Policy/Parameter provisioning  6.2.1.2.2 Principles for applying parameters for A2X communications over PC5 reference point  6.2.1.3 Authorization and Provisioning for A2X communications over Uu reference point  6.2.2 A2X communication  6.2.2.1 A2X communication over PC5 reference point  6.2.2.1.1 General  6.2.2.1.2 Broadcast mode communication over PC5 reference point  6.2.2.1.3 Unicast mode communication over PC5 reference point  6.2.2.1.4 IP address allocation  6.2.2.2 A2X communication over Uu reference point  6.2.2.2.1 A2X communication via unicast  6.2.2.2.2 A2X reception via MBS  6.2.3 A2X Application Server discovery  6.2.4 QoS handling for A2X communication  6.2.4.1 QoS handling for A2X communication over PC5 reference point  6.2.4.2 QoS handling for A2X communication over Uu reference point  6.2.5 Subscription to A2X service  6.2.6 Identifiers  6.2.6.1 Identifiers for A2X communication over PC5 reference point  6.2.7 Interworking between EPS A2X and 5GS A2X  6.2.7.1 A2X Policy and parameter provisioning  6.2.7.2 PC5 operation  6.2.8 MBS Service Description for A2X use 
...

 

6.2  High level functionality and features  p. 89

6.2.1  Authorization and Provisioning for A2X communications  p. 89

6.2.1.1  General  p. 89

Authorization and provisioning of parameters for A2X communication leverages V2X mechanisms as defined in clause 5.1.1 of TS 23.287 with the following differences:
  • V2X is replaced by A2X.
  • The V1 reference point is replaced by the A2X1 reference point.
  • The set of parameters defined for A2X are described in clause 6.2.1.2.1 and clause 6.2.1.3.1.
  • The means for PCF including A2X policy/parameters into a Policy section identified by a Policy Section Identifier (PSI) as specified in clause 6.1.2.2.2 of TS 23.503.
Up

6.2.1.2  Authorization and Provisioning for A2X communications over PC5 reference point  p. 89

6.2.1.2.1  Policy/Parameter provisioning  p. 89
A2X leverages what is defined for V2X in clause 5.1.2.1 of TS 23.287 with the following differences:
  • V2X is replaced by A2X.
  • The V1 reference point is replaced by the A2X1 reference point.
  • Tx Profiles for LTE PC5 are not required.
  • Groupcast related policy/parameters are not required.
  • In addition to existing parameters for V2X, the radio parameters per PC5 RAT (i.e. LTE PC5, NR PC5) can be configured with Altitude Range per Geographical Area. This additional information may be needed to enable policing the use of PC5 depending on the specific location of the UAV.
  • Addition of:
    • Deconflicting policy which indicates the communication mode (unicast or broadcast) used for deconflicting is defined for A2X.
Up
6.2.1.2.2  Principles for applying parameters for A2X communications over PC5 reference point  p. 89
A2X leverages what is defined for V2X in clause 5.1.2.2 of TS 23.287 with the following differences:
  • V2X is replaced by A2X.
  • The V1 reference point is replaced by the A2X1 reference point.

6.2.1.3  Authorization and Provisioning for A2X communications over Uu reference point  p. 90

6.2.1.3.1  Policy/Parameter provisioning  p. 90
The following set of information may be provisioned to the UAV UE for A2X communication over the Uu reference point using MBS:
  1. Mapping of the A2X service type to A2X Application Server address information (consisting of IP address/FQDN and transport layer port#) for unicast.
  2. List of FQDNs or IP addresses of the A2X Application Servers, associated with served geographical area information and list of PLMNs that the configuration applies to.
  3. Mapping of the A2X service type to MBS session announcement for A2X message reception via MBS.
  4. MBS session announcement for receiving A2X Application Server information via MBS (i.e. for A2X Application Sever discovery using MBS).
Up

6.2.2  A2X communication  p. 90

6.2.2.1  A2X communication over PC5 reference point  p. 90

6.2.2.1.1  General  p. 90
A2X communication over PC5 reference point leverages V2X mechanisms to support Unicast communication mode for NR and Broadcast communication mode for both NR and LTE as defined in clause 5.2.1.1 of TS 23.287 with the following applicable differences:
  • V2X is replaced by A2X.
  • The distinction between Vehicle UE and Pedestrian UE is not applicable to A2X.
  • Groupcast mode for NR based PC5 is not supported.
  • For LTE PC5 in EPS, the network scheduled operation mode (defined in referred TS 23.285) is not supported and A2X uses only the UE autonomous resources selection mode.
Up
6.2.2.1.2  Broadcast mode communication over PC5 reference point  p. 90
A2X leverages what is defined for V2X in clause 5.2.1.2 of TS 23.287 with the following differences:
  • V2X is replaced by A2X.
  • The applicable configuration is described in clause 6.2.1.2.
  • PC5 QoS parameters are described in clause 6.2.4.
  • Enhanced QoS handling for NR based PC5 reference point is described in clause 6.2.4.
Up
6.2.2.1.3  Unicast mode communication over PC5 reference point  p. 90
A2X leverages what is defined for V2X in clause 5.2.1.4 of TS 23.287 with the following differences:
  • V2X is replaced by A2X.
  • Definitions for PC5 QoS flows are described in clause 6.2.4.
  • Definitions for A2X identifiers are described in clause 6.2.6.
  • Procedures for Unicast mode A2X communication over PC5 reference point are described in clause 6.3.3.2.
Up
6.2.2.1.4  IP address allocation  p. 91
A2X leverages what is defined for V2X in clause 5.2.1.5 of TS 23.287 with the following differences:
  • V2X is replaced by A2X.
  • Procedures for Unicast mode A2X communication over PC5 reference point are described in clause 6.3.3.2.

6.2.2.2  A2X communication over Uu reference point  p. 91

6.2.2.2.1  A2X communication via unicast  p. 91
A2X leverages what is defined for V2X in clause 5.2.2.1 of TS 23.287 with the following differences:
  • V2X is replaced by A2X.
6.2.2.2.2  A2X reception via MBS  p. 91
A2X leverages what is defined for V2X in clause 5.2.2.2 of TS 23.287 with the following differences:
  • V2X is replaced by A2X.
  • Multicast MBS session is not supported.
  • MBS session announcement is provisioned as described in clauses 6.2.1.1 and 6.2.1.3.1.
Up

6.2.3  A2X Application Server discovery  p. 91

Procedures and mechanisms for V2X Application Server discovery used for V2X communication over Uu operation mode as specified in clause 5.3 of TS 23.287 apply to A2X Application Server discovery used for A2X Broadcast MBS sessions with the following differences:
  • The A2X Application Server address information as specified in clause 6.2.1.3.1 may be configured on the UE or provisioned over N1 reference point.
  • V2X is replaced by A2X, e.g. V2X services to A2X services, V2X Application Server to A2X Application Server, etc.
Up

6.2.4  QoS handling for A2X communication  p. 91

6.2.4.1  QoS handling for A2X communication over PC5 reference point  p. 91

A2X leverages what is defined for V2X in clauses 5.4.1 to 5.4.3 of TS 23.287 with the following differences:
  • V2X is replaced by A2X.
  • Groupcast mode communication is not supported.
  • Definitions for PC5 QoS handling are described in clause 6.2.4.
  • PC5 QoS configuration parameters are described in clause 6.2.1.2.1.
  • Definitions for A2X communication over PC5 Reference point are described in clause 6.2.2.1.
  • Procedures for A2X unicast mode communication over PC5 Reference point are described in clause 6.3.3.2.
  • Procedures for A2X Delivery of PC5 QoS parameters to NG-RAN are described in clause 6.3.5.7.
  • PQI values are defined for A2X communication over PC5 reference point. The one-to-one mapping of standardized PQI values that are defined to PC5 QoS characteristics is specified in Table 6.2.4.1-1.
PQI Value Resource Type Default Prio­rity Level Packet Delay Budget Packet Error Rate Default Maxi­mum Data Burst Volume Default Avera­ging Window Example Services
40 GBR (NOTE 1)450 ms10-2N/A2000 msUnicast mode Detect and Avoid with lower latency requirement
414100 ms10-2N/A2000 msUnicast mode Detect and Avoid
4231000 ms10-3N/A2000 msC2 Communication - Steer to waypoints; C2 Communication - video used to aid UAV control (VLOS)
43340 ms10-3N/A2000 msC2 Communication - Direct stick steering
443140 ms10-4N/A2000 msC2 Communication - video used to aid UAV control (Non-VLOS)
62 Non-GBR4100 ms 10-2N/AN/ABroadcast Remote ID with lower latency requirement
634500 ms 10-2N/AN/ABroadcast Remote ID
64450 ms 10-2N/AN/ABroadcast mode Detect and Avoid with lower latency requirement
654100 ms 10-2N/AN/ABroadcast mode Detect and Avoid
NOTE 1:
GBR PQIs can only be used for unicast PC5 communications.
Up

6.2.4.2  QoS handling for A2X communication over Uu reference point  p. 92

A2X leverages what is defined for V2X in clause 5.4.5 of TS 23.287 with the following differences:
  • V2X is replaced by A2X.
  • Notification on QoS Sustainability Analytics to the V2X Application Server is not supported in this release.
  • QoS Change based on extended NG-RAN Notification to support Alternative Service Requirements is not supported in this Release.
  • 5QI 75 specified in TS 23.501 is intended to be also used for the delivery of A2X messages over MBS.
Up

6.2.5  Subscription to A2X service  p. 92

A2X leverages what is defined for V2X in clause 5.5 of TS 23.287 with the following differences:
  • V2X is replaced by A2X.
  • The distinction between Vehicle and Pedestrian UE is not supported.
  • Definitions for PC5 QoS parameters are described in clause 6.2.4.
  • The procedure PCF based A2X Service Authorization and provisioning to UE is described in clause 6.3.2.2.
Up

6.2.6  Identifiers  p. 93

6.2.6.1  Identifiers for A2X communication over PC5 reference point  p. 93

A2X leverages what is defined for V2X in clause 5.6.1 of TS 23.287 with the following differences:
  • V2X is replaced by A2X.
  • Groupcast mode communication and corresponding identifiers are not supported.
  • IP address allocation for A2X is described in clause 6.2.2.1.4.
  • A2X configuration parameters are described in clause 6.2.1.2.1.
  • Procedures for Unicast mode A2X communication over PC5 reference point are described in clause 6.3.3.2.
Up

6.2.7  Interworking between EPS A2X and 5GS A2X  p. 93

6.2.7.1  A2X Policy and parameter provisioning  p. 93

A2X leverages what is defined for V2X in clause 5.8.1 of TS 23.287 with the following differences:
  • V2X is replaced by A2X.

6.2.7.2  PC5 operation  p. 93

A2X leverages what is defined for V2X in clause 5.8.1 of TS 23.287 with the following differences:
  • V2X is replaced by A2X.

6.2.8  MBS Service Description for A2X use  p. 93

The announced service information for V2X use as specified in clauses 5.10.2 and 5.10.3 of TS 23.287 is used for the announced service information for A2X use with the following difference:
  • V2X is replaced by A2X, e.g. V2X communication to A2X communication, V2X Application Server to A2X Application Server, etc.
  • Only broadcast is used as the MBS Service Type in Table 5.10.2-1 of TS 23.287.
  • For MBS session announcement for A2X Application Server Discovery, the local Service Information contained in the broadcast is as described in clauses 6.2.3 and 6.3.4.1 and should include similar information defined in clause 6.2.1.3.1.
Up

Up   Top   ToC