Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.287  Word version:  18.2.0

Top   Top   Up   Prev   Next
1…   4…   4.2.1.2…   4.2.2…   4.3…   5…   5.2…   5.3…   5.4…   5.4.2…   5.5   5.6…   5.7…   5.10…   6…   6.2…   6.3…   6.3.3…   6.4…   6.5…   A…

 

5.6  Identifiersp. 36

5.6.1  Identifiers for V2X communication over PC5 reference pointp. 36

5.6.1.1  Generalp. 36

Each UE has one or more Layer-2 IDs for V2X communication over PC5 reference point, consisting of:
  • Source Layer-2 ID(s); and
  • Destination Layer-2 ID(s).
Source and destination Layer-2 IDs are included in layer-2 frames sent on the layer-2 link of the PC5 reference point identifying the layer-2 source and destination of these frames. Source Layer-2 IDs are always self-assigned by the UE originating the corresponding layer-2 frames.
The selection of the source and destination Layer-2 ID(s) by a UE depends on the communication mode of V2X communication over PC5 reference point for this layer-2 link, as described in clause 5.6.1.2, clause 5.6.1.3, and clause 5.6.1.4. The source Layer-2 IDs may differ between different communication modes.
When IP-based V2X communication is supported for broadcast and groupcast modes of V2X communication over PC5 reference point, the source IP address is allocated as described in clause 5.2.1.5.
If the UE has an active V2X application that requires privacy support in the current Geographical Area, as identified by configuration described in clause 5.1.2.1, in order to ensure that a source UE (e.g. vehicle) cannot be tracked or identified by any other UEs (e.g. vehicles) beyond a certain short time-period required by the application, the source Layer-2 ID shall be changed over time and shall be randomized. For IP-based V2X communication over PC5 reference point, the source IP address shall also be changed over time and shall be randomized. The change of the identifiers of a source UE must be synchronized across layers used for PC5, (e.g. when the Application Layer ID changes, the source Layer-2 ID and the source IP address need to be changed).
Up

5.6.1.2  Identifiers for broadcast mode V2X communication over PC5 reference pointp. 37

For broadcast mode of V2X communication over PC5 reference point, the UE is configured with the destination Layer-2 ID(s) to be used for V2X services. The destination Layer-2 ID for a V2X communication is selected based on the configuration as described in clause 5.1.2.1.
The UE self-selects a source Layer-2 ID. The UE may use different source Layer-2 IDs for different types of PC5 reference points, i.e. LTE based PC5 and NR based PC5.
Up

5.6.1.3  Identifiers for groupcast mode V2X communication over PC5 reference pointp. 37

For groupcast mode of V2X communication over PC5 reference point, the V2X application layer may provide group identifier information. When the group identifier information is provided by the V2X application layer, the UE converts the provided group identifier into a destination Layer-2 ID. When the group identifier information is not provided by the V2X application layer, the UE determines the destination Layer-2 ID based on configuration of the mapping between V2X service type and Layer-2 ID, as specified in clause 5.1.2.1.
The UE self-selects a source Layer-2 ID.
Up

5.6.1.4  Identifiers for unicast mode V2X communication over PC5 reference pointp. 37

For unicast mode of V2X communication over PC5 reference point, the destination Layer-2 ID used depends on the communication peer. The Layer-2 ID of the communication peer, identified by the Application Layer ID, may be discovered during the establishment of the PC5 unicast link, or known to the UE via prior V2X communications, e.g. existing or prior unicast link to the same Application Layer ID, or obtained from application layer service announcements. The initial signalling for the establishment of the PC5 unicast link may use the known Layer-2 ID of the communication peer, or a default destination Layer-2 ID associated with the V2X service type configured for PC5 unicast link establishment, as specified in clause 5.1.2.1. During the PC5 unicast link establishment procedure, Layer-2 IDs are exchanged, and should be used for future communication between the two UEs, as specified in clause 6.3.3.1.
The Application Layer ID is associated with one or more V2X applications within the UE. If UE has more than one Application Layer IDs, each Application Layer ID of the same UE may be seen as different UE's Application Layer ID from the peer UE's perspective.
The UE maintains a mapping between the Application Layer IDs and the source Layer-2 IDs used for the PC5 unicast links, as the V2X application layer does not use the Layer-2 IDs. This allows the change of source Layer-2 ID without interrupting the V2X applications.
When Application Layer IDs change, the source Layer-2 ID(s) of the PC5 unicast link(s) shall be changed if the link(s) was used for V2X communication with the changed Application Layer IDs.
Based on privacy configuration as specified in clause 5.1.2.1, the update of the new identifiers of a source UE to the peer UE for the established unicast link may cause the peer UE to change its Layer-2 ID and optionally IP address/prefix if IP communication is used as defined in clause 6.3.3.2.
A UE may establish multiple PC5 unicast links with a peer UE and use the same or different source Layer-2 IDs for these PC5 unicast links.
Up

Up   Top   ToC