5G; Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services (3GPP TS 23.287 version 19.1.0 Release 19)

RTS/TSGS-0223287vj10

General Information

Status
Not Published
Technical Committee
3GPP SA 2 - Architecture
Current Stage
8 - Draft receipt by ETSI Secretariat
Completion Date
13-Mar-2026

Buy Documents

Standard

ETSI TS 123 287 V19.1.0 (2026-03) - 5G; Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services (3GPP TS 23.287 version 19.1.0 Release 19)

English language (67 pages)
sale 15% off
Preview
sale 15% off
Preview

Frequently Asked Questions

ETSI TS 123 287 V19.1.0 (2026-03) is a standard published by the European Telecommunications Standards Institute (ETSI). Its full title is "5G; Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services (3GPP TS 23.287 version 19.1.0 Release 19)". This standard covers: RTS/TSGS-0223287vj10

RTS/TSGS-0223287vj10

ETSI TS 123 287 V19.1.0 (2026-03) is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.

Standards Content (Sample)


TECHNICAL SPECIFICATION
5G;
Architecture enhancements for 5G System (5GS)
to support Vehicle-to-Everything (V2X) services
(3GPP TS 23.287 version 19.1.0 Release 19)

3GPP TS 23.287 version 19.1.0 Release 19 1 ETSI TS 123 287 V19.1.0 (2026-03)

Reference
RTS/TSGS-0223287vj10
Keywords
5G
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16

Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871

Important notice
The present document can be downloaded from the
ETSI Search & Browse Standards application.
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format on ETSI deliver repository.
Users should be aware that the present document may be revised or have its status changed,
this information is available in the Milestones listing.
If you find errors in the present document, please send your comments to
the relevant service listed under Committee Support Staff.
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure (CVD) program.
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
No representation or warranty is made that this deliverable is technically accurate or sufficient or conforms to any law
and/or governmental rule and/or regulation and further, no representation or warranty is made of merchantability or fitness
for any particular purpose or against infringement of intellectual property rights.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.

Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and
microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2026.
All rights reserved.
ETSI
3GPP TS 23.287 version 19.1.0 Release 19 2 ETSI TS 123 287 V19.1.0 (2026-03)
Intellectual Property Rights
Essential patents
IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The declarations
pertaining to these essential IPRs, if any, are publicly available for ETSI members and non-members, and can be
found in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to
ETSI in respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the
ETSI IPR online database.
Pursuant to the ETSI Directives including the ETSI IPR Policy, no investigation regarding the essentiality of IPRs,
including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not
referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become,
essential to the present document.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
DECT™, PLUGTESTS™, UMTS™ and the ETSI logo are trademarks of ETSI registered for the benefit of its
Members. 3GPP™, LTE™ and 5G™ logo are trademarks of ETSI registered for the benefit of its Members and of the
3GPP Organizational Partners. oneM2M™ logo is a trademark of ETSI registered for the benefit of its Members and of ®
the oneM2M Partners. GSM and the GSM logo are trademarks registered and owned by the GSM Association.
Legal Notice
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities. These shall be
interpreted as being references to the corresponding ETSI deliverables.
The cross reference between 3GPP and ETSI identities can be found at 3GPP to ETSI numbering cross-referencing.
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI
3GPP TS 23.287 version 19.1.0 Release 19 3 ETSI TS 123 287 V19.1.0 (2026-03)
Contents
Intellectual Property Rights . 2
Legal Notice . 2
Modal verbs terminology . 2
Foreword . 6
1 Scope . 7
2 References . 7
3 Definitions and abbreviations . 8
3.1 Definitions . 8
3.2 Abbreviations . 10
4 Architecture model and concepts . 10
4.1 General concept . 10
4.2 Architectural reference model . 10
4.2.1 PC5 and Uu based V2X architecture reference model . 10
4.2.1.1 Non-roaming 5G System architecture for V2X communication over PC5 and Uu reference points . 10
4.2.1.2 Roaming 5G System architecture for V2X communication over PC5 and Uu reference points . 11
4.2.1.3 Inter-PLMN 5G System architecture for V2X communication over PC5 reference point . 12
4.2.2 AF-based service parameter provisioning for V2X communications . 12
4.2.2A MBS for Uu based V2X architecture reference model . 13
4.2.3 Reference points . 13
4.2.4 Service-based interfaces . 14
4.3 Architecture reference model for interworking with EPS V2X. 14
4.4 Functional entities . 15
4.4.1 UE . 15
4.4.2 PCF . 16
4.4.3 V2X Application Server . 16
4.4.4 AMF. 16
4.4.5 UDM . 17
4.4.6 UDR . 17
4.4.7 NRF . 17
4.4.8 NEF . 17
5 High level functionality and features . 17
5.1 Authorization and Provisioning for V2X communications . 17
5.1.1 General . 17
5.1.2 Authorization and Provisioning for V2X communications over PC5 reference point . 18
5.1.2.1 Policy/Parameter provisioning . 18
5.1.2.2 Principles for applying parameters for V2X communications over PC5 reference point . 20
5.1.3 Authorization and provisioning for V2X communications over Uu reference point . 21
5.1.3.1 Policy/Parameter provisioning . 21
5.2 V2X communication . 22
5.2.1 V2X communication over PC5 reference point . 22
5.2.1.1 General . 22
5.2.1.2 Broadcast mode communication over PC5 reference point . 23
5.2.1.3 Groupcast mode communication over PC5 reference point . 23
5.2.1.4 Unicast mode communication over PC5 reference point . 23
5.2.1.5 IP address allocation . 25
5.2.2 V2X communication over Uu reference point . 25
5.2.2.1 V2X communication via unicast . 25
5.2.2.2 V2X message reception via MBS . 25
5.2.3 V2X communication over PC5 or Uu reference point . 26
5.2.3.1 General . 26
5.3 V2X Application Server discovery. 26
5.3.1 General . 26
5.3.2 Multiple V2X Application Server and Localized V2X Application Server discovery and routing . 27
ETSI
3GPP TS 23.287 version 19.1.0 Release 19 4 ETSI TS 123 287 V19.1.0 (2026-03)
5.4 QoS handling for V2X communication . 27
5.4.1 QoS handling for V2X communication over PC5 reference point . 27
5.4.1.1 QoS model. 27
5.4.1.1.1 General overview. 27
5.4.1.1.2 Deriving PC5 QoS parameters and assigning PFI for PC5 QoS Flow . 29
5.4.1.1.3 Handling of PC5 QoS Flows based on PC5 QoS Rules . 29
5.4.1.1.4 PC5 Packet Filter Set . 31
5.4.1.2 QoS handling for broadcast mode V2X communication over PC5 reference point . 31
5.4.1.3 QoS handling for groupcast mode V2X communication over PC5 reference point . 32
5.4.1.4 QoS handling for unicast mode V2X communication over PC5 reference point . 32
5.4.2 PC5 QoS parameters . 32
5.4.2.1 PQI . 32
5.4.2.2 PC5 Flow Bit Rates . 32
5.4.2.3 PC5 Link Aggregated Bit Rates . 33
5.4.2.4 Range . 33
5.4.2.5 Default Values . 33
5.4.3 PC5 QoS characteristics . 33
5.4.3.1 General . 33
5.4.3.2 Resource Type . 33
5.4.3.3 Priority Level . 34
5.4.3.4 Packet Delay Budget . 34
5.4.3.5 Packet Error Rate . 34
5.4.3.6 Averaging Window . 34
5.4.3.7 Maximum Data Burst Volume . 34
5.4.4 Standardized PQI to QoS characteristics mapping . 34
5.4.5 QoS handling for V2X communication over Uu reference point . 36
5.4.5.1 General . 36
5.4.5.2 Notification on QoS Sustainability Analytics to the V2X Application Server . 36
5.4.5.2.1 General . 36
5.4.5.2.2 Functional description . 36
5.4.5.3 QoS Change based on Extended NG-RAN Notification to support Alternative Service
Requirements . 36
5.5 Subscription to V2X services . 37
5.6 Identifiers . 37
5.6.1 Identifiers for V2X communication over PC5 reference point . 37
5.6.1.1 General . 37
5.6.1.2 Identifiers for broadcast mode V2X communication over PC5 reference point . 38
5.6.1.3 Identifiers for groupcast mode V2X communication over PC5 reference point . 38
5.6.1.4 Identifiers for unicast mode V2X communication over PC5 reference point . 38
5.7 Support for V2X communication for UEs in limited service state . 39
5.8 Interworking between EPS V2X and 5GS V2X . 39
5.8.1 V2X Policy and parameter provisioning . 39
5.8.2 PC5 Operation . 39
5.8.3 Mobility between EPS and 5GS over Uu. 39
5.9 Support of QoS aware NR PC5 power efficiency for pedestrian UEs. 40
5.10 MBS Service Description for V2X use . 40
5.10.1 General . 40
5.10.2 MBS session announcement for V2X communication . 41
5.10.3 MBS session announcement for V2X Application Server Discovery . 41
5.11 Support of NR PC5 Carrier Aggregation operations . 42
6 Functional description and information flows . 42
6.1 Control and user plane stacks . 42
6.1.1 User plane for NR PC5 reference point supporting V2X services . 42
6.1.2 Control plane for NR PC5 reference point supporting V2X services . 43
6.2 Procedures for Service Authorization and Provisioning to UE . 44
6.2.1 General . 44
6.2.2 PCF based Service Authorization and Provisioning to UE . 44
6.2.3 PCF discovery . 44
6.2.4 Procedure for UE triggered V2X Policy provisioning . 44
6.2.5 AF-based service parameter provisioning for V2X communications over control plane . 45
6.3 Procedures for V2X communication over PC5 reference point . 45
ETSI
3GPP TS 23.287 version 19.1.0 Release 19 5 ETSI TS 123 287 V19.1.0 (2026-03)
6.3.1 Broadcast mode V2X communication over PC5 reference point . 45
6.3.2 Groupcast mode V2X communication over PC5 reference point . 47
6.3.3 Unicast mode V2X communication over PC5 reference point . 48
6.3.3.1 Layer-2 link establishment over PC5 reference point . 48
6.3.3.2 Link identifier update for a unicast link . 52
6.3.3.3 Layer-2 link release over PC5 reference point . 53
6.3.3.4 Layer-2 link modification for a unicast link . 53
6.3.3.5 Layer-2 link maintenance over PC5 reference point . 54
6.4 Procedures for V2X communication over Uu reference point . 55
6.4.1 Procedure for notification on QoS Sustainability Analytics to the V2X Application Server . 55
6.4.2 V2X Application Server discovery using broadcast MBS session . 57
6.4.3 Procedure for V2X communication with MBS . 57
6.4.3.1 MBS service area mapping . 57
6.5 Procedures for Service Authorization to NG-RAN for V2X communications over PC5 reference point . 58
6.5.1 General . 58
6.5.2 Registration procedure . 58
6.5.3 Service Request procedure . 59
6.5.4 N2 Handover procedure . 59
6.5.5 Xn Handover procedure . 59
6.5.6 Subscriber Data Update Notification to AMF . 59
6.5.7 Delivery of PC5 QoS parameters to NG-RAN . 60
6.5.8 PC5 Capability for V2X indication and V2X related information per PC5 RAT . 60
Annex A (informative): Application Function influence based edge computing for V2X services . 61
Annex B (informative): Road Side Unit (RSU) implementation options . 62
Annex C (informative): Change history . 63
History . 66

ETSI
3GPP TS 23.287 version 19.1.0 Release 19 6 ETSI TS 123 287 V19.1.0 (2026-03)
Foreword
This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
ETSI
3GPP TS 23.287 version 19.1.0 Release 19 7 ETSI TS 123 287 V19.1.0 (2026-03)
1 Scope
The present document specifies architecture enhancements to the 5G System to facilitate vehicular communications for
Vehicle-to-Everything (V2X) services, over the following reference points, based on service requirements defined in
TS 22.185 [2] and TS 22.186 [3]:
- PC5 reference point: NR PC5 RAT, LTE PC5 RAT.
- Uu reference point: NR, E-UTRA.
This specification also covers interworking with EPS.
2 References
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] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 22.185: "Service requirements for V2X services; Stage 1".
[3] 3GPP TS 22.186: "Enhancement of 3GPP support for V2X scenarios; Stage 1".
[4] ISO 17419:2018: "Intelligent transport systems - Cooperative systems - Globally unique
identification".
[5] IEEE Std 1609.12-2016: "IEEE Standard for Wireless Access in Vehicular Environments
(WAVE) - Identifier Allocations".
[6] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2".
[7] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2".
[8] 3GPP TS 23.285: "Architecture enhancements for V2X services".
[9] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal
Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2".
[10] 3GPP TS 36.304: "Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE)
procedures in idle mode".
[11] 3GPP TS 38.300: "NR; NR and NG-RAN Overall Description; Stage 2".
[12] 3GPP TS 38.304: "NR; User Equipment (UE) procedures in Idle mode and RRC Inactive state".
[13] 3GPP TS 23.122: "Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle
mode".
[14] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource
Control (RRC); Protocol specification".
[15] 3GPP TS 38.331: "NR; Radio Resource Control (RRC); protocol specification".
[16] 3GPP TS 23.503: "Policy and Charging Control Framework for the 5G System; Stage 2".
ETSI
3GPP TS 23.287 version 19.1.0 Release 19 8 ETSI TS 123 287 V19.1.0 (2026-03)
[17] 3GPP TS 23.303: "Proximity-based Services (ProSe); Stage 2".
[18] IEEE Std 1609.3-2010: "IEEE Standard for Wireless Access in Vehicular Environments (WAVE)
- Networking Services".
[19] ISO 29281-1:2013: "Intelligent Transport Systems - Communications access for land mobiles
(CALM) - Non-IP networking - Part 1: Fast networking & transport layer protocol (FNTP)".
[20] 3GPP TS 23.288: "Architecture enhancements for 5G System (5GS) to support network data
analytics services".
[21] IETF RFC 4862: "IPv6 Stateless Address Autoconfiguration".
[22] 3GPP TS 38.413: "NG-RAN; NG Application Protocol (NGAP)".
[23] 3GPP TS 38.423: "NG-RAN; Xn Application Protocol (XnAP)".
[24] 3GPP TS 24.587: "Vehicle-to-Everything (V2X) services in 5G System (5GS); Stage 3".
[25] 3GPP TS 37.340: "Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-
connectivity; Stage 2".
[26] 3GPP TS 33.536: "Security aspects of 3GPP support for advanced Vehicle-to-Everything (V2X)
services".
[27] CCSA YD/T 3707-2020: "Technical requirements of network layer of LTE-based vehicular
communication".
[28] 3GPP TS 23.247: "Architectural enhancements for 5G multicast-broadcast services; Stage 2".
[29] 3GPP TS 26.502: "5G multicast-broadcast services; User Service architecture".
[30] 3GPP TS 26.517: "5G Multicast-Broadcast User Services; Protocols and Formats".
[31] ETSI TS 102 637-2 V1.2.1: "Intelligent Transport Systems (ITS); Vehicular Communications;
Basic Set of Applications; Part 2: Specification of Cooperative Awareness Basic Service".
[32] ETSI TS 102 637-3 V1.1.1: "Intelligent Transport Systems (ITS); Vehicular Communications;
Basic Set of Applications; Part 3: Specifications of Decentralized Environmental Notification
Basic Service".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in TR 21.905 [1] 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 [1].
Application Layer connection-less group: An application layer group without group formation in the V2X application
layer, e.g., sensor sharing.
Application Layer ID: An identifier identifying an entity, e.g. a vehicle, a pedestrian, an RSU within the context of a
specific V2X application. The format of this identifier is outside the scope of 3GPP.
NOTE 1: The Application Layer ID could be e.g. Station ID or Vehicle ID defined by other SDOs e.g. ETSI,
Society of Automotive Engineers (SAE), etc.
NOTE 2: The usage of Application Layer ID, e.g. one Application Layer ID is associated with one V2X
application, one Application Layer ID is associated with more than one V2X applications, or one
Application Layer ID is used for all V2X applications in the UE, is up to application layer
implementation.
ETSI
3GPP TS 23.287 version 19.1.0 Release 19 9 ETSI TS 123 287 V19.1.0 (2026-03)
Application Layer managed group: An application layer group with group formation and management in the V2X
application layer, e.g., platooning, cooperative adaptive cruise control.
Groupcast mode communication: It refers to V2X communication over PC5 reference point within a group of UEs
where any UE in the group can act as transmitting UE and the rest act as receiving UEs. See also TS 38.300 [11] for
more information. The "group" here refers to Application Layer managed group or Application Layer connection-less
group.
Member ID: An identifier uniquely identifying a member in the Application Layer managed group and that is managed
by the V2X application layer.
Mode of communication: Mode of communication to be used by the UE over PC5 reference point i.e. broadcast mode
(LTE PC5 and NR PC5), groupcast mode (NR PC5) or unicast mode (NR PC5).
NR Tx Profile: The transmission mechanism or format to be used by the UE over NR PC5 RAT (e.g. PC5 DRX
support or not), see TS 38.300 [11] and TS 38.331 [15].
NR eTx Profile: The enhanced transmission mechanism or format to be used by the UE over NR PC5 RAT (e.g.
related to PC5 carrier aggregation), see TS 38.300 [11] and TS 38.331 [15].
NOTE 3: The contents of the NR Tx Profile and the NR eTx Profile are not visible to the V2X layer.
V2X application: An application using one or more V2X services e.g. an active safety application in a vehicle, using
V2X services such as emergency warning and vehicle to vehicle safety and awareness. A V2X application may operate
towards a V2X Application Server.
V2X communication: A communication to support Vehicle-to-Everything (V2X) services leveraging Uu and / or PC5
reference points. V2X services are realized by various types of V2X applications, i.e. Vehicle-to-Vehicle (V2V),
Vehicle-to-Pedestrian (V2P), Vehicle-to-Infrastructure (V2I) and Vehicle-to-Network (V2N).
V2X message: A dedicated messaging type of V2X service, for example ITS messages.
V2X service: A data service, offered to V2X applications and optionally V2X Application Servers. A V2X service
belongs to one V2X service type. It may include message or other data delivery, as defined in TS 22.185 [2] and
TS 22.186 [3]. A V2X service can be associated with one or more V2X applications, and a V2X application can be
associated with one or more V2X services.
V2X service type: A type of V2X service, which is identified by e.g. ITS-AID (ITS Application Identifier), PSID
(Provider Service Identifier) or AID (Application Identifier).
For the purposes of the present document, the following terms and definitions given in ISO 17419:2018 [4] apply:
Intelligent Transport Systems
ITS Application Identifier
For the purposes of the present document, the following term and definition given in IEEE Std 1609.12-2016 [5] apply:
Provider Service Identifier
For the purposes of the present document, the following term and definition given in CCSA YD/T 3707-2020 [27]
applies:
Application Identifier
For the purposes of the present document, the following term and definition given in TS 23.285 [8] apply:
Tx Profile
ETSI
3GPP TS 23.287 version 19.1.0 Release 19 10 ETSI TS 123 287 V19.1.0 (2026-03)
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in TR 21.905 [1] 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 [1].
AF Application Function
AID Application Identifier
AS layer Access Stratum layer
ITS Intelligent Transport Systems
ITS-AID ITS Application Identifier
MBS Multicast/Broadcast Service
NID Network identifier
PFI PC5 QoS Flow Identifier
PQI PC5 5QI
PSID Provider Service Identifier
RSU Road Side Unit
SNPN Stand-alone Non-Public Network
V2I Vehicle-to-Infrastructure
V2N Vehicle-to-Network
V2P Vehicle-to-Pedestrian
V2V Vehicle-to-Vehicle
V2X Vehicle-to-Everything
4 Architecture model and concepts
4.1 General concept
There are two modes of operation for V2X communication, namely V2X communication over PC5 reference point and
V2X communication over Uu reference point. These two operation modes may be used by a UE independently for
transmission and reception.
V2X communications over PC5 reference point are supported by LTE and/or NR.
V2X communications over Uu reference point are supported by E-UTRA connected to 5GC and/or NR connected to
5GC:
- For E-UTRA connected to 5GC, V2X communication over Uu reference point is only unicast.
- For NR connected to 5GC, V2X communication over Uu reference point can be unicast and/or
multicast/broadcast as defined in TS 23.247 [28].
An RSU is not an architectural entity, but an implementation option. This is achieved by collocating a V2X application
logic/server with some entities of the 3GPP system, as shown in examples in Annex B.
4.2 Architectural reference model
4.2.1 PC5 and Uu based V2X architecture reference model
4.2.1.1 Non-roaming 5G System architecture for V2X communication over PC5 and
Uu reference points
Figure 4.2.1.1-1 shows the high level view of the non-roaming 5G System architecture for V2X communication over
PC5 and Uu reference points.
ETSI
3GPP TS 23.287 version 19.1.0 Release 19 11 ETSI TS 123 287 V19.1.0 (2026-03)
V2X
Data
Application
N6
Network
Server
5GC
UDM PCF NEF AF
UPF
NRF UDR AMF SMF
UE C
V2X V2X
Application Application
UE D
NG-RAN
PC5
Uu
Uu PC5
V5
PC5
UE B UE A
V5
V5
V2X
V2X
Application
Application
V1
Figure 4.2.1.1-1: Non-roaming 5G System architecture for V2X communication over PC5 and Uu
reference points
4.2.1.2 Roaming 5G System architecture for V2X communication over PC5 and Uu
reference points
Figure 4.2.1.2-1 and Figure 4.2.1.2-2 show the high level view of the roaming 5G System architectures for V2X
communication over PC5 and Uu reference points. In these figures, UE A uses a subscription of HPLMN.
5GC
NRF UDM UDR PCF NEF AF
HPLMN
VPLMN
5GC
V2X
N6 Data
Application
UPF
Network
AMF SMF
NRF PCF Server
N4
V2X
N2
Application
N3
UE C
NG-RAN
Uu
V1
Uu PC5
V5
PC5
UE B
UE A
V2X V2X
Application Application
V5
Figure 4.2.1.2-1: Roaming 5G System architecture for V2X communication over PC5 and Uu reference
points - Local breakout scenario
ETSI
3GPP TS 23.287 version 19.1.0 Release 19 12 ETSI TS 123 287 V19.1.0 (2026-03)
5GC
AF UDM UDR
NRF
V2X
UPF Data
Application
Network
NEF SMF
PCF
Server
HPLMN
VPLMN
5GC
UPF
NRF PCF AMF SMF
N4
V2X
N2
Application
N3
UE C
NG-RAN
Uu
Uu PC5
V5
PC5
UE B
UE A
V2X V2X
Application Application
V1
V5
Figure 4.2.1.2-2: Roaming 5G System architecture for V2X communication over PC5 and Uu reference
points - Home routed scenario
4.2.1.3 Inter-PLMN 5G System architecture for V2X communication over PC5
reference point
In the case of inter-PLMN V2X communication over PC5 reference point, the PC5 parameters need to be configured in
a consistent way among the UEs within a certain region. The architecture for the Inter-PLMN PC5 case is similar to the
one defined in clause 4.2.1.1.
4.2.2 AF-based service parameter provisioning for V2X communications
The 5G System provides NEF services to enable communication between NFs in the PLMN and V2X Application
Server. Figure 4.2.2-1 shows the high level view of AF-based service parameter provisioning for V2X communications.
The V2X Application Server may provide V2X service parameters to the PLMN via NEF. The NEF stores the V2X
service parameters in the UDR.
ETSI
3GPP TS 23.287 version 19.1.0 Release 19 13 ETSI TS 123 287 V19.1.0 (2026-03)
V2X
Application
Server
Nnef
5GC
NEF
N37
N30
UDR PCF
N36
V1
N15
AMF
N1 N2
5G-AN
UE
V2X
Application
Figure 4.2.2-1: 5G System architecture for AF-based service parameter provisioning for V2X
communications
4.2.2A MBS for Uu based V2X architecture reference model
The reference architectures for MBS for Uu based V2X communication are based on the MBS reference architectures
specified in clause 5.1 of TS 23.247 [28].
Configuration options at Service and/or Application for MBS specified in Annex A of TS 23.247 [28] and Interworking
at reference points MB2 and xMB specified in Annex C of TS 23.247 [28], can be applied for Uu based V2X
communication via MBS.
The V2X Application Server acts as an AF/AS defined in clause 5.1 and Annex A of TS 23.247 [28].
4.2.3 Reference points
V1: The reference point between the V2X applications in the UE and in the V2X Application Server. This
reference point is out of scope of this specification.
V5: The reference point between the V2X applications in the UEs. This reference point is not specified in this
release of the specification.
PC5: The reference point between the UEs, and it includes the LTE based PC5 and/or NR based PC5.
N1: In addition to the relevant functions defined in TS 23.501 [6] for N1, in the case of V2X Service it is also
used to convey the V2X policy and parameters (including service authorization) from AMF to UE and to
convey the UE's V2X-Uu Capability and PC5 Capability for V2X information from UE to AMF.
N2: In addition to the relevant functions defined in TS 23.501 [6] for N2, in the case of V2X Service it is also
used to convey the V2X policy and parameters (including service authorization) from AMF to NG-RAN.
Uu: The reference point between the UE and the NG-RAN.
ETSI
3GPP TS 23.287 version 19.1.0 Release 19 14 ETSI TS 123 287 V19.1.0 (2026-03)
4.2.4 Service-based interfaces
Nudm: In addition to the relevant services defined in TS 23.501 [6] for Nudm, in the case of V2X Service,
services provided by UDM are used to get V2X Service related subscription information to AMF during
Initial registration procedure or UE Configuration Update (UCU) procedure to inform AMF subscription
information has changed.
Npcf: In addition to the relevant services defined in TS 23.501 [6] for Npcf, in the case of V2X Service,
services provided by H-PCF are used to provide V2X Service related parameters to V-PCF for UE and
NG-RAN in the roaming case.
Nudr: In addition to the relevant services defined in TS 23.501 [6] for Nudr, in the case of V2X Service,
services provided by UDR are used to notify the PCF and the UDM of the update of the V2X Service
related information.
Nnef: In addition to the relevant services defined in TS 23.501 [6] for Nnef, in the case of V2X Service,
services provided by NEF are used by the V2X Application Server to update V2X Service related
information of 5GC.
Namf: In addition to the relevant services de
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.

Loading comments...