1. 3GPP V2X Interworking Potential Impact
Group Name: TP & ARC
Source: Huawei
Meeting Date:
Agenda Item: WI-0082

2. 3GPP Architecture in TS23.285
The high level view of the reference architectures for PC5 and LTE-Uu based V2X communication are given in 3GPP TS
New reference points
V1: exchange V2X messages between V2X Application Server and UEs.
V3: V2X provisioning using OMA DM.
V4: obtain subscription information from HSS using Diameter protocol.
V5: UE-UE direct communication
V6: roaming between CF and CF
New function entities
V2X Application Server
V2X Control Function

3. 3GPP Control Function in TS 24.385, TS 24.386
3GPP Control Function provisions the UE with necessary parameters (as a DM server) for V2X communication via OMA DM.
3GPP specifies the Management Object about V2XProvisioning, V2XoverPC5 and V2XoverLTEUu to the UE
Most of the MO are 3GPP network independent.
Static Network Data
Network Data in conditions
network independent
Service Related

4. 3GPP Application Server in TR 23.795
V2X application enabler server
QoS monitoring and report: QoS communicating with the underlying 3GPP network system (EPS/5GS) for unicast and multicast network resource management and QoS adaptation;
Network status monitoring and report :receiving monitoring reports/events from the underlying 3GPP network system (EPS/5GS) regarding network situation corresponding to RAN and core network;
MBMS Group: V2X USD provisioning to the connected V2X UE;
Device Management: providing V2X server USDs corresponding to the geographic locations; and
provisioning PC5 parameters to the UE
Location: UE location report over V1
V2X application enabler client
- providing UE capabilities;
- MBMS monitoring for suspension/resumption;
- MBMS listening status reporting;
- discovering local V2X service information;
- supporting PC5 parameters provisioning; and
- supporting V2X USD provisioning.
The V1-APP reference point is out of scope of 3GPP
The V5-APP reference point is out of scope of 3GPP.
The details of the V2X application client is out of scope of the present document.
Definition of reference point between the V2X application client and the VAE client function and reference point between V2X application specific server and VAE server are FFS.
The details of the V2X application specific server is out of scope of the present document.
There is no north bound interface of V2X Application enabler server

5. oneM2M interworking with 3GPP V2X architecture
The “V2X Control Function” may host on the IN-CSE as DMG CSF and can be located in the Service Layer. IN-CSE shall support to communicate with HSS via V4 reference point and communicate with other V2X Control Function in 3GPP Trust Domian via V6 reference point.
The “V2X Application server” can be splited to three logic functions:
One function is 3GPP network status & QoS monitoring and report hosted in 3GPP Trust domain. At the same time, there is no standard interface between IN-CSE and 3GPP V2X AS.
One function is Device Management, MBMS Group, Location and 3GPP QoS hosted on the platform may be IN-CSE. 3GPP QoS management is new feature for oneM2M.
The last function is application function hosted on an external network may be an IN-AE.

6. Potential Impact for oneM2M Architecture- Field domain communication directly
The “V2X Applications” hosted on the UE may be deployed as follows:
- Application only: UE may be ADN as of oneM2M entity
- Application and CSE: UE may be ASN or MN as of oneM2M entity
- CSE only: UE may be MN as of oneM2M entity
- Neither application nor CSE: UE may host a NoDN.
ADN
ADN
Maa AE AE AE AE
Mca
ASN/MN
ASN/MN
Mcc’’ AE AE AE AE
CSE
CSE
Question:
What the reference point should be in oneM2M mapping to V5 to support PC5 mode?

7. Option1: ADN<-> ADNsAE AE
IN-CSE
CSE AE
Maa AE MN
CSE
ADN AE AE
In oneM2M R3, oneM2M AE is limited to receiving only NOTIFY requests from its Registrar CSE.
In oneM2M R4, the WI-0076 Lightweight oneM2M Services , AE is allowed to host its own oneM2M resources and support other operation than Notify.
ETSI ITS defined CAM and DENM massage sets and working in progress of collective perception service, multimedia content dissemination and manoeuvre coordination service.SAE defined 15+ application message sets in J2735/J2945. oneM2M can map these message to container/flexcontainer to support PC5 mode.

8. Option2: ASN/MN<-> ASN/MNAE AE
CSE
IN-CSE
Mcc’’
CSE AE
ASN/MN AE AE
CSE
In oneM2M R4, CSE can only communicate with its registrar/register CSE via Mcc reference point.
In 3GPP PC5 mode, the ASNs/MNs hosted on the UEs do not has registration relationship with each other.
It’s new reference point Mcc’’ and may impact the current resource operations of the CSE. For example, the ASN/MN CSE of a vehicle may create <container> to restore V2X service information of other vehicles in PC5 mode.

9. Solution: R4 only support option1
In oneM2M R4, option 1 may be simpler and easy to support.

10. Potential Impact for oneM2M Architecture- 3GPP interworking
In TS-0026 of oneM2M, oneM2M has support MBMS group, Location, Network status monitoring and report function via T8 interface.

11. Option 1: Reuse SCEF T8 interface
WG1 WG2 WG4均与3GPP交互过联络函。
WG1：LS_out LS to 3GPP via WG4
WG2：LS_in LS on eV2X Normative Requirements Completion
WG4：LS_out LS on eV2X Normative Requirements, Response to 3GPP TSG-SA WG1 LS on eV2X Normative Requirements
WG4主要在推动频谱分配
Preps:
The interfaces between oneM2M and 3GPP are simple;
Reuse the existing features of MBMS group, Location and Network status monitoring and report
Cons:
New requirements for 3GPP SCEF to support V2X related service(eg. V4 and new T8 API)

12. Option 2: Support new interfaces
WG1 WG2 WG4均与3GPP交互过联络函。
WG1：LS_out LS to 3GPP via WG4
WG2：LS_in LS on eV2X Normative Requirements Completion
WG4：LS_out LS on eV2X Normative Requirements, Response to 3GPP TSG-SA WG1 LS on eV2X Normative Requirements
WG4主要在推动频谱分配
Preps: ?
Cons:
Two different interfaces to support the same function, eg, MBMS group, location, Network status
New requirements for 3GPP to support new interface to expose V2X related Service to oneM2M

13. Solution: Option1
Try to send LS with requirements to 3GPP SA2 as option1

14. Conclusion To support 3GPP V2X Service,
In oneM2M R4, support communication between ADN and ADNS only
Reuse the existing T8 interface to support MBMS group, location and network status monitoring and report and send LS with requirements to 3GPP SA2

15. Thank you