IP Library Granted Patent US 12,439,240
Granted Patent B2
US 12,439,240 · App. 17/897,872 · Granted Oct 7, 2025

Vehicle-to-everything (V2X) control function based on user equipment (UE) capability

Inventor: Changhong Shan (Portland, OR)
Assignee: Apple Inc.
H04W8/24H04M15/66H04W4/40H04W8/08H04W60/00H04W76/25
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,439,240
App. No.
17/897,872
Granted
Oct 7, 2025
Kind
B2
Abstract

Embodiments of the present disclosure describe methods, apparatuses, storage media, and systems for determining a capability of a UE for supporting vehicle-to-everything (V2X) communication over a PC5 interface, and determining at least a V2X policy and V2X parameters for the UE based on the capability of the UE for supporting V2X communication. Other embodiments may be described and claimed.

Claims (48)

1. A method performed by a user equipment (UE), comprising:

determining a capability of the UE for supporting vehicle-to-everything (V2X) communication over a PC5 interface;

transmitting a registration request message to an access and mobility management function (AMF), wherein the registration request message includes an indication of the capability of the UE for supporting the V2X communication over the PC5 interface;

receiving a message generated by the AMF in response to the registration request message transmitted to the AMF; and

identifying a V2X policy and V2X parameters for the UE contained in the message generated by the AMF, wherein the V2X policy and the V2X parameters include configuration parameters for the V2X communication over the PC5 interface for the UE that are determined based on the capability of the UE for supporting the V2X communication over the PC5 interface, and wherein the V2X parameters include at least an expiration time for validity of the configuration parameters for the V2X communication over the PC5 interface.

2. The method of claim 1 , further comprising:

storing the V2X policy and the V2X parameters; and

performing operations associated with the V2X policy and the V2X parameters.

3. The method of claim 1 , wherein the configuration parameters for the V2X communication over the PC5 interface for the UE include configuration parameters for V2X provisioning; configuration parameters for the V2X communication over the PC5 interface; and

configuration parameters for the V2X communication over a Uu interface.

4. The method of claim 1 , wherein the PC5 interface is a Long Term Evolution (LTE) PC5 interface or a New Radio (NR) PC5 interface.

5. The method of claim 1 , wherein the registration request message is a non-access stratum (NAS) message.

6. The method of claim 1 , wherein the message received from the AMF is a downlink (DL) NAS transport message.

7. The method of claim 1 , wherein the V2X policy and the V2X parameters for the UE are determined by a Policy Control Function (PCF) or a V2X Control Function (V2XCF) coupled to the AMF.

8. A method performed by an access and mobility management function (AMF), comprising:

receiving a registration request message from a user equipment (UE) including an indication of a capability of the UE for supporting a vehicle-to-everything (V2X) communication over a PC5 interface;

determining whether to provide at least a V2X policy and V2X parameters including configuration parameters for the V2X communication over the PC5 interface to the UE based on the capability of the UE for supporting the V2X communication, subscription data of the UE, or local policy;

obtaining the V2X policy and the V2X parameters, wherein the V2X policy and the V2X parameters are determined based on the capability of the UE for supporting the V2X communication over the PC5 interface, wherein the V2X parameters include at least an expiration time for validity of the configuration parameters for the V2X communication over the PC5 interface; and

transmitting a message to provide an indication of the V2X policy and the V2X parameters to the UE.

9. The method of claim 8 , further comprising:

retrieving the subscription data of the UE from a Unified Data Management (UDM).

10. The method of claim 8 , wherein the V2X policy and the V2X parameters for the UE are determined by a Policy Control Function (PCF) or a V2X Control Function (V2XCF).

11. The method of claim 10 , further comprising:

requesting, using a parameter request message, the V2XCF or the PCF to provide the V2X policy and the V2X parameters, wherein the parameter request message includes the capability of the UE for supporting the V2X communication; and

receiving the V2X policy and the V2X parameters from the PCF or the V2XCF.

12. The method of claim 11 , further comprising:

receiving results obtained from operations performed by the UE associated with the V2X policy and the V2X parameters.

13. The method of claim 12 , further comprising:

notifying the PCF or the V2XCF the results received from the UE; and

forwarding the received results from the UE to the PCF or the V2XCF by “Namf_EventExposure”, wherein EventID includes “V2X Policy container received” and EventInformation includes a UE V2X Policy container.

14. The method of claim 8 , wherein the PC5 interface is a Long Term Evolution (LTE) PC5 interface or a New Radio (NR) PC5 interface.

15. The method of claim 8 , wherein the registration request message is a non-access stratum (NAS) message.

16. The method of claim 8 , wherein the transmitted message is a downlink (DL) NAS transport message.

17. A user equipment (UE), comprising:

processing circuitry configured to:

determine a capability of the UE for supporting a vehicle-to-everything (V2X) communication over a PC5 interface; and

identify a V2X policy and V2X parameters for the UE contained in a message generated by an access and mobility management function (AMF), wherein the V2X policy and the V2X parameters include configuration parameters for the V2X communication over the PC5 interface for the UE that are determined based on the capability of the UE for supporting the V2X communication over the PC5 interface, and wherein the V2X parameters include at least an expiration time for validity of the configuration parameters for the V2X communication over the PC5 interface; and

network circuitry coupled to the processing circuitry and configured to:

transmit a registration request message to the AMF, wherein the registration request message includes an indication of the capability of the UE for supporting the V2X communication over the PC5 interface; and

receive the message generated by the AMF in response to the registration request message transmitted to the AMF.

18. The UE of claim 17 , wherein the processing circuitry is further configured to:

store the V2X policy and the V2X parameters; and

perform operations associated with the V2X policy and the V2X parameters.

19. The UE of claim 17 , wherein the configuration parameters for the V2X communication over the PC5 interface for the UE include configuration parameters for V2X provisioning; configuration parameters for the V2X communication over the PC5 interface; and configuration parameters for the V2X communication over a Uu interface.

20. A method performed by a Policy Control Function (PCF), comprising:

receiving a request from an access and mobility management function (AMF) to provide a vehicle-to-everything (V2X) policy and V2X parameters for a user equipment (UE), wherein the request includes a capability of the UE for supporting the V2X communication over a PC5 interface;

determining the V2X policy and the V2X parameters based on the capability of the UE for supporting the V2X communication, wherein the V2X parameters include at least an expiration time for validity of configuration parameters for the V2X communication over the PC5 interface; and

transmitting the V2X policy and the V2X parameters to the AMF.

Continuity (3)
Continuation 16431419 · Jun 4, 2019
Provisional Application 62687029 · Jun 19, 2018
Related Publication 20230063242A1 · Mar 2, 2023
References Cited (20)
US 10517110B2 · Dinan et al. · 2019 [cited by applicant]
US 11432135B2 · Shan · 2022 [cited by examiner]
US 11956122B2 · Cheng · 2024 [cited by examiner]
US 20190037448A1 · Shan et al. · 2019 [cited by applicant]
US 20190090107A1 · Kim et al. · 2019 [cited by applicant]
US 20190116520A1 · Chaponniere et al. · 2019 [cited by applicant]
US 20190289459A1 · Shan · 2019 [cited by examiner]
US 20190306754A1 · Shan · 2019 [cited by examiner]
US 20190313359A1 · Lee · 2019 [cited by examiner]
US 20190313469A1 · Karampatsis et al. · 2019 [cited by applicant]
US 20200112841A1 · Kim et al. · 2020 [cited by applicant]
US 20200178048A1 · Kim et al. · 2020 [cited by applicant]
US 20200374828A1 · Ying · 2020 [cited by examiner]
US 20220022029A1 · Di Girolamo · 2022 [cited by examiner]
US 20220095260A1 · Shan · 2022 [cited by examiner]
WO WO2019157961A1 · 2019 [cited by applicant]
Motorola Mobility, Lenovo, UE Policy management (Discussion) Nov. 27-Dec. 1, 2017, SA WG2 Meeting #124, S2-178546 (Year: 2017). [cited by applicant]
3GPP, “Technical Specification Group Services and System Aspects; Architecture enhancements for V2X services (Release 15),” 3GPP TS 23.285 V15.1.0 (Jun. 2018), 5G, 36 pages. [cited by applicant]
3GPP, “Technical Specification Group Core Network and Terminals; User Equipment (UE) to V2X control function; protocol aspects; Stage 3 (Release 14), ”3GPP TS 24.386 V14.3.0 (Dec. 2017), Lte Advanced Pro, 35 pages. [cited by applicant]
3GPP, “Technical Specification Group Core Network and Terminals; V2X Control Function to V2X Application Server Aspects; Stage 3 (Release 14),” 3GPP TS 29.387 V0.1.0 (Oct. 2016), Lte Advanced Pro, 7 pages. [cited by applicant]