Content for TS 24.587 Word version: 18.0.0
1 Scope
2 References
3 Definitions of terms and abbreviations
3.1 Terms
3.2 Abbreviations
4 General description
...
...
1 Scope p. 9
The present document specifies the protocols for vehicle-to-everything (V2X) services network as specified in TS 23.287 for:
- V2X communication among the UEs over the PC5 interface; and
- V2X communication between the UE and the V2X application server over the Uu interface.
2 References p. 9
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode".
[3]
TS 23.287: "Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services".
[4]
TS 23.502: "Procedures for the 5G System (5GS); Stage 2".
[5]
TS 24.386: "User Equipment (UE) to V2X control function; protocol aspects; Stage 3".
[6]
TS 24.501: "Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3".
[7]
TS 24.588: "Vehicle-to-Everything (V2X) services in 5G System (5GS); User Equipment (UE) policies; Stage 3".
[8]
TS 38.300: "NR; NR and NG-RAN Overall Description; Stage 2".
[9]
TS 38.304: "User Equipment (UE) procedures in Idle mode and RRC Inactive state".
[10]
TS 38.323: "NR; Packet Data Convergence Protocol (PDCP) specification".
[11]
TS 38.331: "NR; Radio Resource Control (RRC) protocol specification".
[12]
ETSI EN 302 636-3 v1.2.1: "Intelligent Transport Systems (ITS); Vehicular Communications; GeoNetworking; Part 3: Network Architecture".
[13]
IEEE 1609.3 2016: "IEEE Standard for Wireless Access in Vehicular Environments (WAVE) -- Networking Services".
[14]
RFC 768: "User Datagram Protocol".
[15]
RFC 4291: "IP Version 6 Addressing Architecture".
[16]
RFC 4862: "Neighbor Discovery for IP version 6 (IPv6)".
[17]
ISO 29281-1:2018: "Intelligent transport systems -- Communication access for land mobiles (CALM) -- Non-IP networking -- Part 1: Fast networking & transport layer protocol (FNTP)".
[18]
ISO TS 17419 ITS-AID AssignedNumbers: http://standards.iso.org/iso/ts/17419/TS17419%20Assigned%20Numbers/TS17419_ITS-AID_AssignedNumbers.pdf
[19]
RFC 1035: "DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION".
[20]
TS 33.536: "Security aspects of 3GPP support for advanced Vehicle-to-Everything (V2X) services".
[21]
TS 33.501: "Security architecture and procedures for 5G system".
[22]
TS 24.526: "User Equipment (UE) policies for 5G System (5GS); Stage 3".
[23]
ISO/IEC 10118-3:2018: "IT Security techniques - Hash-functions - Part 3: Dedicated hash-functions".
[24]
CCSA YD/T 3707-2020: "Technical requirements of network layer of LTE-based vehicular communication".
[25]
RFC 793: "Transmission Control Protocol."
[26]
TS 24.007: "Mobile radio interface signalling layer 3; General aspects".
[27]
TS 24.554: "Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3".
3 Definitions of terms and abbreviations p. 10
3.1 Terms p. 10
For the purposes of the present document, the terms given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
E-UTRA-PC5:
PC5 reference point over E-UTRA. The term E-UTRA-PC5 used in the present document corresponds to the term LTE PC5 defined in TS 23.287.
NR-PC5:
PC5 reference point over NR. The term NR-PC5 used in the present document corresponds to the term NR PC5 defined in TS 23.287.
PC5 QoS flow context:
A context which includes a set of V2X service identifiers, a PQFI value and a set of PC5 QoS parameters.
PC5 QoS rule:
A rule which includes a PC5 QoS rule identifier, a PQFI value, a precedence value and optionally a set of packet filters. The PC5 QoS rule is associated with a PC5 QoS flow context.
V2X service identifier:
an identifier of a V2X service, e.g. PSID, ITS-AID, or AID of the V2X application. The term V2X service identifier used in the present document corresponds to the term V2X service type defined in TS 23.287.
For the purposes of the present document, the following terms and definitions given in TS 23.287 apply:
Application Identifier (AID)
Intelligent Transport Systems (ITS)
ITS Application Identifier (ITS-AID)
NR Tx Profile
Provider Service Identifier (PSID)
V2X communication
V2X message
V2X service
For the purposes of the present document, the following terms and definitions given in TS 24.501 apply:
5G-EA
5G-IA
For the purposes of the present document, the following terms and definitions given in TS 24.501 apply:
UE local configuration
3.2 Abbreviations p. 11
For the purposes of the present document, the abbreviations given in TR 21.905 , TS 24.501 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 and TS 24.501.
E-UTRA
Evolved Universal Terrestrial Radio Access
FQDN
Fully Qualified Domain Name
LSB
Least Significant 8 Bits
MSB
Most Significant 8 Bits
NR
New Radio
NRPEK
NR PC5 Encryption Key
NRPIK
NR PC5 Integrity Key
V2X
Vehicle-to-Everything
V2XP
V2X Policy
PQFI
PC5 QoS Flow ID
PQI
PC5 5QI
ProSeP
5G ProSe Policy
4 General description p. 11
The present specification defines means for transport of V2X messages in 5GS and interworking to EPS. V2X messages are generated and consumed by upper layers of the UE and the V2X application server. V2X messages can contain IP data or non-IP data.
The V2X messages can be transported using:
- V2X communication over PC5; and
- V2X communication over Uu.
- V2X communication over PC5 enables transfer of V2X messages among UEs;
- both IP based and non-IP based V2X messages are supported over PC5; and
- for V2X messages containing IP data, only IPv6 is used. IPv4 is not supported in this release of the specification.
- V2X communication over Uu enables transfer of V2X messages between a UE and a V2X application server;
- both IP based and non-IP based V2X messages are supported over Uu;
- V2X messages are carried over Uu in payload of either a UDP/IP packet or TCP/IP packet towards a V2X application server address;
- V2X messages carried over Uu are sent or received over unicast only in this release of the specification; and
- V2X messages are carried over Uu using user data via user plane.
