Patent Description:
The following abbreviations are herewith defined, at least some of which are referred to within the following description: Third Generation Partnership Project ("3GPP"), <NUM>th Generation ("<NUM>"), <NUM>th Generation ("<NUM>"), <NUM> System ("5GS"), Positive-Acknowledgment ("ACK"), Aggregation Level ("AL"), Access and Mobility Management Function ("AMF"), Access Network ("AN"), Access Point ("AP"), Authentication Server Function ("AUSF"), Beam Failure Detection ("BFD"), Binary Phase Shift Keying ("BPSK"), Base Station ("BS"), Buffer Status Report ("BSR"), Bandwidth ("BW"), Bandwidth Part ("BWP"), Carrier Aggregation ("CA"), Contention-Based Random Access ("CBRA"), Clear Channel Assessment ("CCA"), Control Channel Element ("CCE"), Cyclic Delay Diversity ("CDD"), Code Division Multiple Access ("CDMA"), Control Element ("CE"), Contention-Free Random Access ("CFRA"), Closed-Loop ("CL"), Coordinated Multipoint ("CoMP"), Cyclic Prefix ("CP"), Cyclical Redundancy Check ("CRC"), Channel State Information ("CSI"), Channel State Information-Reference Signal ("CSI-RS"), Common Search Space ("CSS"), Control Resource Set ("CORESET"), Discrete Fourier Transform Spread ("DFTS"), Downlink Control Information ("DCI"), Downlink ("DL"), Demodulation Reference Signal ("DMRS"), Data Radio Bearer ("DRB"), Discontinuous Reception ("DRX"), Downlink Pilot Time Slot ("DwPTS"), Enhanced Clear Channel Assessment ("eCCA"), EPS Connection Management ("ECM"), Enhanced Mobile Broadband ("eMBB"), Evolved Node B ("eNB"), Effective Isotropic Radiated Power ("EIRP"), European Telecommunications Standards Institute ("ETSI"), Evolved Packet Core ("EPC"), Evolved Packet System ("EPS"), Evolved Universal Terrestrial Access ("E-UTRA"), Evolved Universal Terrestrial Access Network ("E-UTRAN"), Frame Based Equipment ("FBE"), Frequency Division Duplex ("FDD"), Frequency Division Multiplexing ("FDM"), Frequency Division Multiple Access ("FDMA"), Frequency Division Orthogonal Cover Code ("FD-OCC"), <NUM> Node B or Next Generation Node B ("gNB"), General Packet Radio Services ("GPRS"), Guard Period ("GP"), Global System for Mobile Communications ("GSM"), Globally Unique Temporary UE Identifier ("GUTI"), Home AMF ("hAMF"), Hybrid Automatic Repeat Request ("HARQ"), Home Location Register ("HLR"), Home PLMN ("HPLMN"), Home Subscriber Server ("HSS"), Identity or Identifier ("ID"), Information Element ("IE"), International Mobile Equipment Identity ("IMEI"), International Mobile Subscriber Identity ("IMSI"), International Mobile Telecommunications ("IMT"), Internet-of-Things ("IoT"), Layer <NUM> ("L2"), Licensed Assisted Access ("LAA"), Load Based Equipment ("LBE"), Listen-Before-Talk ("LBT"), Logical Channel ("LCH"), Logical Channel Prioritization ("LCP"), Log-Likelihood Ratio ("LLR"), Long Term Evolution ("LTE"), Multiple Access ("MA"), Medium Access Control ("MAC"), Multimedia Broadcast Multicast Services ("MBMS"), Modulation Coding Scheme ("MCS"), Master Information Block ("MIB"), Multiple Input Multiple Output ("MIMO"), Mobility Management ("MM"), Mobility Management Entity ("MME"), Mobile Network Operator ("MNO"), massive MTC ("mMTC"), Maximum Power Reduction ("MPR"), Machine Type Communication ("MTC"), Multi User Shared Access ("MUSA"), Non Access Stratum ("NAS"), Narrowband ("NB"), Negative-Acknowledgment ("NACK") or ("NAK"), Network Entity ("NE"), Network Function ("NF"), Next Generation RAN ("NG-RAN"), Non-Orthogonal Multiple Access ("NOMA"), New Radio ("NR"), Network Repository Function ("NRF"), Network Slice Instance ("NSI"), Network Slice Selection Assistance Information ("NSSAI"), Network Slice Selection Function ("NSSF"), Network Slice Selection Policy ("NSSP"), Operation and Maintenance System ("OAM"), Orthogonal Frequency Division Multiplexing ("OFDM"), Open-Loop ("OL"), Other System Information ("OSI"), Power Angular Spectrum ("PAS"), Physical Broadcast Channel ("PBCH"), Power Control ("PC"), LTE-to-V2X Interface ("PC5"), Primary Cell ("PCell"), Policy Control Function (""PCF"), Physical Cell ID ("PCID"), Physical Downlink Control Channel ("PDCCH"), Packet Data Convergence Protocol ("PDCP"), Physical Downlink Shared Channel ("PDSCH"), Pattern Division Multiple Access ("PDMA"), Packet Data Unit ("PDU"), Physical Hybrid ARQ Indicator Channel ("PHICH"), Power Headroom ("PH"), Power Headroom Report ("PHR"), Physical Layer ("PHY"), Public Land Mobile Network ("PLMN"), Physical Random Access Channel ("PRACH"), Physical Resource Block ("PRB"), Primary Secondary Cell ("PSCell"), Physical Uplink Control Channel ("PUCCH"), Physical Uplink Shared Channel ("PUSCH"), Quasi Co-Located ("QCL"), Quality of Service ("QoS"), Quadrature Phase Shift Keying ("QPSK"), Registration Area ("RA"), Radio Access Network ("RAN"), Radio Access Technology ("RAT"), Random Access Procedure ("RACH"), Random Access Response ("RAR"), Resource Element Group ("REG"), Radio Link Control ("RLC"), Radio Link Monitoring ("RLM"), Radio Network Temporary Identifier ("RNTI"), Reference Signal ("RS"), Remaining Minimum System Information ("RMSI"), Radio Resource Control ("RRC"), Radio Resource Management ("RRM"), Resource Spread Multiple Access ("RSMA"), Reference Signal Received Power ("RSRP"), Round Trip Time ("RTT"), Receive ("RX"), Sparse Code Multiple Access ("SCMA"), Scheduling Request ("SR"), Sounding Reference Signal ("SRS"), Single Carrier Frequency Division Multiple Access ("SC-FDMA"), Secondary Cell ("SCell"), Shared Channel ("SCH"), Sub-carrier Spacing ("SCS"), Service Data Unit ("SDU"), System Information Block ("SIB"), SystemInformationBlockType1 ("SIB1"), SystemInformationBlockType2 ("SIB2"), Subscriber Identity/Identification Module ("SIM"), Signal-to-Interference-Plus-Noise Ratio ("SINR"), Service Level Agreement ("SLA"), Session Management Function ("SMF"), Special Cell ("SpCell"), Single Network Slice Selection Assistance Information ("S-NSSAI"), Shortened TTI ("sTTI"), Synchronization Signal ("SS"), Synchronization Signal Block ("SSB"), Supplementary Uplink ("SUL"), Subscriber Permanent Identifier ("SUPI"), Tracking Area ("TA"), TA Indicator ("TAI"), Transport Block ("TB"), Transport Block Size ("TBS"), Time-Division Duplex ("TDD"), Time Division Multiplex ("TDM"), Time Division Orthogonal Cover Code ("TD-OCC"), Transmission Power Control ("TPC"), Transmission Reception Point ("TRP"), Transmission Time Interval ("TTI"), Transmit ("TX"), Uplink Control Information ("UCI"), Unified Data Management Function ("UDM"), Unified Data Repository ("UDR"), User Entity/Equipment (Mobile Terminal) ("UE"), Universal Integrated Circuit Card ("UICC"), Uplink ("UL"), Universal Mobile Telecommunications System ("UMTS"), User Plane ("UP"), Uplink Pilot Time Slot ("UpPTS"), Ultra-reliability and Low-latency Communications ("URLLC"), UE Route Selection Policy ("URSP"), LTE Radio Interface ("Uu"), Vehicle-To-Everything ("V2X"), Visiting AMF ("vAMF"), Visiting NSSF ("vNSSF"), Visiting PLMN ("VPLMN"), Interconnecting Interface ("X2") ("Xn"), and Worldwide Interoperability for Microwave Access ("WiMAX").

In certain wireless communications networks, V2X communication may be used. In such networks, devices may not be compatible with one another.

<CIT> discloses systems and methods of providing a V2X communications. <CIT> (which is believed to correspond to the earlier published <CIT>) discloses a method of sending a vehicle-to-everything (V2X) service message. 3GPP TS <NUM> v14. <NUM> from <NUM>-<NUM> describes protocol aspects of the User Equipment to V2X control function.

A method and a user equipment, UE, for V2X communication over multiple radio access types are disclosed.

<FIG> depicts an embodiment of a wireless communication system <NUM> for V2X communication over multiple radio access types. In one embodiment, the wireless communication system <NUM> includes remote units <NUM> and network units <NUM>. Even though a specific number of remote units <NUM> and network units <NUM> are depicted in <FIG>, one of skill in the art will recognize that any number of remote units <NUM> and network units <NUM> may be included in the wireless communication system <NUM>.

In one embodiment, the remote units <NUM> may include computing devices, such as desktop computers, laptop computers, personal digital assistants ("PDAs"), tablet computers, smart phones, smart televisions (e.g., televisions connected to the Internet), set-top boxes, game consoles, security systems (including security cameras), vehicle on-board computers, network devices (e.g., routers, switches, modems), aerial vehicles, drones, or the like. The remote units <NUM> may communicate directly with one or more of the network units <NUM> via UL communication signals. The remote units <NUM> may also communicate directly with one or more of the other remote units <NUM>.

In one embodiment, a remote unit <NUM> may establish a first plurality of network connections for direct communication with a mobile communication network and a second plurality of network connections for direct vehicle-to-everything communication with other remote units <NUM> over a plurality of radio access types. In certain embodiments, the remote unit <NUM> may receive a request to transmit a vehicle-to-everything communication. In various embodiments, the remote unit <NUM> may determine whether the vehicle-to-everything communication is to be transmitted via a direct communication with a mobile communication network or a direct vehicle-to-everything communication with other remote units <NUM>. In some embodiments, the remote unit <NUM> may determine a radio access type of the plurality of radio access types for transmitting the vehicle-to-everything communication via a direct vehicle-to-everything communication. In certain embodiments, the remote unit <NUM> may select a cell of a plurality of cells that supports vehicle-to-everything resource management for the vehicle-to-everything communication via a direct vehicle-to-everything communication and the radio access type. In various embodiments, the remote unit <NUM> may request resources via the cell for transmitting the vehicle-to-everything communication via a direct vehicle-to-everything communication using the radio access type. Accordingly, the remote unit <NUM> may be used for V2X communication over multiple radio access types.

In various embodiments, a remote unit <NUM> may transmit information indicating a vehicle-to-everything capability of the remote unit <NUM>. In various embodiments, the remote unit <NUM> may receive a response to the information indicating the vehicle-to-everything capability of the remote unit <NUM>. In such embodiments, the response indicates whether the remote unit <NUM> is authorized to use the vehicle-to-everything capability. Accordingly, the remote unit <NUM> may be used for V2X communication over multiple radio access types.

In certain embodiments, a network unit <NUM> may receive information indicating a vehicle-to-everything capability of a remote unit <NUM>. In various embodiments, the network unit <NUM> may transmit a response to the information indicating the vehicle-to-everything capability of the remote unit <NUM>. In such embodiments, the response indicates whether the remote unit <NUM> is authorized to use the vehicle-to-everything capability. Accordingly, the network unit <NUM> may be used for V2X communication over multiple radio access types.

In one embodiment, a remote unit <NUM> may configure a remote unit with information indicating a plurality of mobile networks and a radio access type of a plurality of radio access types for direct vehicle-to-everything communication corresponding to each mobile network of the plurality of mobile networks. In various embodiments, the remote unit <NUM> may support a plurality of vehicle-to-everything applications. In such embodiments, each vehicle-to-everything application of the plurality of vehicle-to-everything applications communicates via a direct vehicle-to-everything communication using a corresponding radio access type of the plurality of radio access types. Accordingly, the remote unit <NUM> may be used for V2X communication over multiple radio access types.

<FIG> depicts one embodiment of an apparatus <NUM> that may be used for V2X communication over multiple radio access types. The apparatus <NUM> includes one embodiment of the remote unit <NUM>. Furthermore, the remote unit <NUM> may include a processor <NUM>, a memory <NUM>, an input device <NUM>, a display <NUM>, a transmitter <NUM>, and a receiver <NUM>. In some embodiments, the input device <NUM> and the display <NUM> are combined into a single device, such as a touchscreen. In certain embodiments, the remote unit <NUM> may not include any input device <NUM> and/or display <NUM>. In various embodiments, the remote unit <NUM> may include one or more of the processor <NUM>, the memory <NUM>, the transmitter <NUM>, and the receiver <NUM>, and may not include the input device <NUM> and/or the display <NUM>.

In various embodiments, the processor <NUM> may: establish a first plurality of network connections for direct communication with a mobile communication network and a second plurality of network connections for direct vehicle-to-everything communication with other remote units over a plurality of radio access types; receive a request to transmit a vehicle-to-everything communication; determine whether the vehicle-to-everything communication is to be transmitted via a direct communication with a mobile communication network or a direct vehicle-to-everything communication with other remote units <NUM>; determine a radio access type of the plurality of radio access types for transmitting the vehicle-to-everything communication via a direct vehicle-to-everything communication; select a cell of a plurality of cells that supports vehicle-to-everything resource management for the vehicle-to-everything communication via a direct vehicle-to-everything communication and the radio access type; and request resources via the cell for transmitting the vehicle-to-everything communication via a direct vehicle-to-everything communication using the radio access type.

In certain embodiments, the processor <NUM> may: configure the apparatus <NUM> with information indicating a plurality of mobile networks and a radio access type of a plurality of radio access types for direct vehicle-to-everything communication corresponding to each mobile network of the plurality of mobile networks; and support a plurality of vehicle-to-everything applications, wherein each vehicle-to-everything application of the plurality of vehicle-to-everything applications communicates via a direct vehicle-to-everything communication using a corresponding radio access type of the plurality of radio access types.

The transmitter <NUM> is used to provide UL communication signals to the network unit <NUM> and the receiver <NUM> is used to receive DL communication signals from the network unit <NUM>, as described herein. In certain embodiments, the transmitter <NUM> transmits information indicating a vehicle-to-everything capability of the apparatus <NUM>. In some embodiments, the receiver <NUM> receives a response to the information indicating the vehicle-to-everything capability of the apparatus <NUM>. In such embodiments, the response indicates whether the apparatus <NUM> is authorized to use the vehicle-to-everything capability.

<FIG> depicts one embodiment of an apparatus <NUM> that may be used for V2X communication over multiple radio access types. The apparatus <NUM> includes one embodiment of the network unit <NUM>. Furthermore, the network unit <NUM> may include a processor <NUM>, a memory <NUM>, an input device <NUM>, a display <NUM>, a transmitter <NUM>, and a receiver <NUM>. As may be appreciated, the processor <NUM>, the memory <NUM>, the input device <NUM>, the display <NUM>, the transmitter <NUM>, and the receiver <NUM> may be substantially similar to the processor <NUM>, the memory <NUM>, the input device <NUM>, the display <NUM>, the transmitter <NUM>, and the receiver <NUM> of the remote unit <NUM>, respectively.

In some embodiments, the receiver <NUM> receives information indicating a vehicle-to-everything capability of a remote unit <NUM>. In some embodiments, the transmitter <NUM> transmits a response to the information indicating the vehicle-to-everything capability of the remote unit <NUM>. In such embodiments, the response indicates whether the remote unit <NUM> is authorized to use the vehicle-to-everything capability.

Although only one transmitter <NUM> and one receiver <NUM> are illustrated, the network unit <NUM> may have any suitable number of transmitters <NUM> and receivers <NUM>.

In some embodiments, if a UE is to send a V2X message over a PC5 interface, the UE may determine whether a cell supports certain carrier frequencies for V2X communications. In such embodiments, if the cell does not support the carrier frequencies the UE may have to search for a cell that supports the carrier frequencies. The search may take into account a list of PLMNs that the UE is enabled to use for PC5 communications. In certain embodiments, a UE searching for a cell to support carrier frequencies for V2X communication may first look for the cell in its own PLMN and, if the UE is not successful, the UE may look in cells of equivalent PLMNs until a cell is found that supports V2X communications. In such embodiments, if the UE is outside coverage of 3GPP specified RATs (e.g., LTE and NR cells are unavailable) on a sidelink V2X frequency, then the UE may perform sidelink communication in another manner, such as according to SL-V2X-Preconfiguration.

In various embodiments, a <NUM> capable UE may support both EPS V2X communications (e.g., such as for safety services) and <NUM> V2X enhanced services (e.g., such as for vehicle platooning). In some embodiments, if <NUM> V2X capable UEs need to communicate with EPS V2X capable UEs, the UEs may use E-UTRA over Uu to send a V2X communication over legacy PC5 (e.g., E-UTRA).

As may be appreciated, a UE may have a number of services that require <NUM> radio access technology and such services will not be available if a <NUM> V2X capable UE uses E-UTRA and EPC due to communicating a V2X message over E-UTRA PC5. As described herein, a UE may be able to determine a best cell to camp in to support V2X communications over PC5 over both E-UTRA and NR without interrupting other V2X services. Furthermore, as described herein a UE may identify how to transmit eV2X messages either based on an enhanced E-UTRA radio or based on a NR radio.

In certain embodiments, during registration in an EPS, a UE may include in an initial attach request an indication that the UE is V2X capable. Moreover, an MME may check with an HSS to determine whether the UE is authorized to use V2X services and may provide an indication to an eNB that indicates whether the UE is authorized to use V2X. Based on this indication the eNB may identify whether the UE is enabled to use a scheduled mode of operation in a cell.

In various embodiments, such as in <NUM>, a UE may support both E-UTRA PC5 and NR PC5. Furthermore, in some embodiments, the UE may support a version of E-UTRA that is enhanced (e.g., enhanced E-UTRA), such as with higher data rates than standard E-UTRA. In certain embodiments, an NG-RAN node (e.g., eNB, gNB) may support scheduling resources for PC5 messages sent via NR, E-UTRA, and/or an enhanced E-UTRA. Accordingly, an NG-RAN node may indicate whether a UE is authorized to use E-UTRA PC5 and/or NR PC5 in a cell.

In some embodiments, a UE may use a single RAT and/or system (e.g., EPS or 5GS) over a Uu reference point (e.g., macro cell with a single RAT), and a RAN node may be able to configure the UE for multiple PC5 types of communication (e.g., E-UTRA PC5 and/or NR PC5). As may be appreciated, a UE may use a dual connectivity feature (e.g., a secondary cell operating in the same or in a different RAT than a master cell) together with PC5 communication.

In various embodiments, a V2X capable UE may provide its V2X capabilities during an initial registration and/or mobility registration procedure with a 5GS. For example, a UE may include information indicating that V2X is supported and/or the UE may provide an explicit indication of V2X services that the UE supports (e.g., safety V2X services using E-UTRA PC5, enhanced V2X services using NR PC5, etc.). In certain embodiments, a registration request message may be authorized by a network function (e.g., UDM, PCF, AUSF, or another network function) that may determine (e.g., check) whether a UE is authorized to use V2X services and may provide an indication indicating whether the UE is authorized to use PC5 communications over E-UTRA PC5 and/or NR PC5. In such embodiments, the network function may provide the indication to an AMF to indicate which PC5 types the UE is allowed to use. Moreover, the AMF may then provide information to an NG-RAN to indicate whether the UE is authorized to use V2X services over PC5 and may provide information indicating the RATs supported.

<FIG> is a schematic block diagram illustrating one embodiment of communications <NUM> including a registration procedure with V2X authorization. The communications <NUM> include messages transmitted between a UE <NUM> (e.g., V2X UE), a RAN <NUM> (e.g., NG-RAN), an AMF <NUM>, an AUSF <NUM>, and a UDM <NUM>. Each communication described herein may include one or more messages.

In certain embodiments, in a first communication <NUM> transmitted from the UE <NUM> to the RAN <NUM>, the UE <NUM> may transmit an initial registration request that includes an indication that the UE <NUM> is V2X capable. In some embodiments, as part of the first communication <NUM>, the UE <NUM> may include a generic indication (e.g., a single bit) or the UE <NUM> may be more explicit and indicate that the UE <NUM> supports basic (e.g., EPS based) and/or enhanced (e.g., <NUM> based) V2X capabilities.

In various embodiments, in a second communication <NUM> transmitted from the RAN <NUM> to the AMF <NUM>, the RAN <NUM> may transmit information that indicates AN parameters and/or information from the initial registration request received by the RAN <NUM> from the UE <NUM>.

In some embodiments, authentication and/or authorization messages <NUM> may be transmitted between the UE <NUM>, the RAN <NUM>, the AMF <NUM>, and/or the AUSF <NUM> to perform authentication and/or authorization of the UE <NUM>.

In certain embodiments, UDM selection <NUM> is performed by the AMF <NUM>.

In various embodiments, in a third communication <NUM> transmitted from the AMF <NUM> to the UDM <NUM>, the AMF <NUM> may forward the V2X capability of the UE <NUM> to the UDM <NUM>, such as within a Nudm_service request message.

In some embodiments, in a fourth communication <NUM> transmitted from the UDM <NUM> to the AMF <NUM>, the UDM <NUM>, based on subscription information, may provide an indication to the AMF <NUM> that the UE <NUM> is authorized to use E-UTRA PC5 and/or NR PC5. As part of the fourth communication <NUM>, the UDM <NUM> may also provide an indication that the UE <NUM> is enhanced E-UTRA capable. In certain embodiments, the AMF <NUM> may store information about the authorization of the UE <NUM> to use E-UTRA PC5 and/or NR PC5 in the UE's <NUM> context. In various embodiments, the AMF <NUM> may forward information about the authorization of the UE <NUM> together with the UE's <NUM> context to other AMFs or MMEs. In some embodiments, the AMF <NUM> may process and/or store information about the authorization of the UE <NUM> to facilitate signaling the information within the UE <NUM> context (e.g., RAN <NUM>) to the RAN <NUM> (e.g., NG-RAN node).

In certain embodiments, in a fifth communication <NUM> transmitted from the AMF <NUM> to the RAN <NUM>, the AMF <NUM> may send the indication about the authorization to use E-UTRA PC5 and/or NR PC5 to the RAN <NUM>. The indication may be within the UE's <NUM> RAN context encapsulated in a message as part of various parameters. In various embodiments, the AMF <NUM> may send the indication about the authorization to use E-UTRA PC5 and/or NR PC5 during each transition from a CM-idle state to a CM-connected state.

In some embodiments, the RAN <NUM> stores <NUM> (e.g., in the UE <NUM> context) information indicating whether the UE <NUM> is authorized to support EPS services, NR V2X services, E-UTRA PC5, and/or NR PC5.

In certain embodiments, in a sixth communication <NUM> transmitted from the RAN <NUM> to the UE <NUM>, the RAN <NUM> may transmit a registration accept message to the UE <NUM>.

As may be appreciated, while the communications <NUM> through <NUM> are described for registration with a 5GS, similar communications may be used for registration with an EPS.

In various embodiments, after the UE <NUM> receives the sixth communication <NUM>, the UE <NUM> may proceed to subscribe to V2X services from a V2X control function and/or may receive authorization to use PC5 in a PLMN.

In some embodiments, authorization information may include the following (either provided by a V2X control function and/or preconfigured at the UE <NUM>): <NUM>) An authorization policy: authorization to perform PC5 communication with a list of PLMNs for which the UE <NUM> is served by an E-UTRAN; and/or a list of geographical areas in which the UE <NUM> is authorized to perform PC5 communications at times that the UE <NUM> is not served by E-UTRA; <NUM>) Radio configuration parameters at times during which the UE <NUM> is not served by E-UTRAN: includes the radio parameters with geographical areas and an indication of whether they are "operator managed" or "non-operator managed" (e.g., the UE <NUM> may use the radio parameters to perform V2X communications over PC5 reference point at times in which the UE <NUM> is "not served by E-UTRAN" only if the UE <NUM> can reliably locate itself in a corresponding geographical area, otherwise, the UE <NUM> is not authorized to transmit); <NUM>) Policy parameters: mapping of destination layer <NUM> IDs (e.g., in a PC5 message) to V2X application IDs; mapping of per prose packet priority and packet delay budget; and/or mapping of V2X application IDs to V2X frequencies with geographical areas.

In certain embodiments, because a <NUM> UE <NUM> may support dual PC5 capability (e.g., both E-UTRA PC5 and NR PC5 simultaneously), the UE <NUM> may require configuration information to be aware of which PLMNs the UE <NUM> is allowed to perform PC5 communications over E-UTRA or NR. This configuration information may be needed by the UE <NUM> if served by the RAN <NUM> and also if not served by the RAN <NUM>. In various embodiments, the UE <NUM> may be configured with a list of PLMNs that the UE <NUM> is authorized to perform PC5 communications over E-UTRA, enhanced E-UTRA, and/or NR. In some embodiments, if not served by the RAN <NUM>, the UE <NUM> may be configured with a list of geographical areas that the UE <NUM> is authorized to perform PC5 communications over NR and/or E-UTRA.

In various embodiments, the UE <NUM> may be provided with information indicating times during which a V2X application triggers to send a message over PC5. In such embodiments, the UE <NUM> may need to identify if V2X messages need to be sent over E-UTRA PC5, enhanced E-UTRA PC5, or NR PC5. Such embodiments may include configuring the UE <NUM> with a mapping between V2X application IDs and PC5 RATs. In some embodiments, a V2X application ID may map to one or more PC5 RATs.

In some embodiments, a V2X application may indicate a priority of a V2X message to a V2X layer in the UE <NUM>. In such embodiments, based on the priority requested, the UE <NUM> may determine whether the V2X message will be sent over E-UTRA or NR RAT based on priority requirements. As may be appreciated, information used to determine whether the V2X message will be sent over E-UTRA or NR RAT may be configured at the UE <NUM> (e.g., the UE <NUM> may be configured by a network with a mapping of a priority to a selected PC5 RAT (e.g., E-UTRA or NR).

As described herein, the UE <NUM> may include the following configuration parameters: a list of PLMNs in which the UE <NUM> is authorized to perform E-UTRA, enhanced E-UTRA, and/or NR over PC5; a list of geographical areas in which the UE <NUM> is authorized to perform E-UTRA, enhanced E-UTRA, and/or NR over PC5; a mapping of V2X application IDs to PC5 RATs; and/or a mapping of a priority requested by a V2X application to one or more PC5 RATs. The configuration parameters may be configured in the UE <NUM> using NAS protocol messages, using RRC protocol messages, and/or using other protocols carried over user plane IP protocols.

In certain embodiments, the UE <NUM> may be configured with authorization to perform E-UTRA or NR and a gNB and/or eNB may decide dynamically whether enhanced E-UTRA may be used to transmit a V2X message. In one example, a cell may be configured with information that indicates that for a specific carrier frequency enhanced E-UTRA may be used. In such an example, the cell may dynamically decide whether a V2X message can be transmitted using enhanced E-UTRA PC5. In such embodiments, this type of configuration may be supported if a cell can detect that UEs in its vicinity are enhanced E-UTRA PC5 capable (e.g., based on information from the UDM <NUM>).

In various embodiments, the UE <NUM> may be configured so that for specific application IDs the UE <NUM> is E-UTRA PC5 authorized, and/or enhanced E-UTRA PC5 may be used in specific geographical locations. In such embodiments, if the UE <NUM> is triggered to transmit a V2X message for the specific application IDs, the UE <NUM> checks its geographical location to determine whether E-UTRA or enhanced E-UTRA is to be used.

In some embodiments, the UE <NUM> may be configured so that for a specific application ID, E-UTRA is authorized. In such embodiments, if the UE <NUM> is enhanced E-UTRA capable and if the UE <NUM> starts a message exchange (e.g., for unicast communications), the UE <NUM> may indicate that it is enhanced E-UTRA capable and may decide to use enhanced E-UTRA to convey a PC5 message.

In certain embodiments, the RAN <NUM> may not be able to know and/or gather enough information for the UE's <NUM> transmission configuration for a certain PC5 RAT. In such embodiments, the RAN <NUM> may know (e.g., by network configuration) which other RAN node to query to learn the PC5 configuration information. In some embodiments, a RAN node may broadcast or announce that it supports all types of PC5 communication. Moreover, some PC5 RATs may determine other RAN nodes' supported communications without a query to the other RAN nodes and for other PC5 RATs the PC5 RATs may need to query other RAN nodes to determine the other RAN nodes; supported communications. For example, a gNB may be able to configure the UE <NUM> for NR PC5 transmission, but may not be able to determine the E-UTRA PC5 or enhance E-UTRA PC5 configuration by itself. However, the gNB may know which particular eNB to query to obtain such E-UTRA PC5 or enhance E-UTRA PC5 configuration. Moreover, the gNB may announce support of E-UTRA PC5, enhance E-UTRA PC5, and NR PC5 communication.

<FIG> is a schematic block diagram illustrating one embodiment of a system <NUM> for sending a PC5 message over multiple RATs in an autonomous mode. The system <NUM> includes a UE <NUM>. The UE <NUM> may be substantially similar to the UE <NUM> and/or the remote unit <NUM> as described herein. Moreover, the UE <NUM> includes a V2X client <NUM> and has a V2X configuration <NUM> (V2X config). The V2X configuration <NUM> may include an E-UTRA PC5 radio configuration, an NR PC5 radio configuration, a list of application IDs for E-UTRA PC5, and/or a list of application IDS for NR PC5.

The UE <NUM> also includes a first V2X application <NUM> (first V2X app) and a second V2X application <NUM> (second V2X app). The UE <NUM> may be configured for E-UTRA PC5 <NUM> and/or NR PC5 <NUM>. As illustrated, the system <NUM> also includes a V2X control function <NUM>. In various embodiments, the V2X control function <NUM> may transmit information <NUM> indicating the V2X configuration <NUM>.

In various embodiments, while the UE <NUM> is in an autonomous mode of operation, the UE <NUM> may determine a radio configuration for V2X services based on configuration policies of the V2X configuration <NUM>. In one embodiment, the UE <NUM> determines the radio parameters to use based on a geographical area. In some embodiments, if the radio configuration indicates both NR PC5 and E-UTRA PC5, the UE <NUM> uses both radio parameters to listen for PC5 messages.

In certain embodiments, while the UE <NUM> is in an autonomous mode of operation and a V2X application requests to transmit a PC5 message, the UE <NUM> may determine whether the V2X message is to be sent over NR PC5 or E-UTRA PC5 based on the configuration received from the V2X control function <NUM>. For example, while a V2X application may send a PC5 message over a V2X layer the UE <NUM> may determine based on a V2X application ID that the PC5 message must be sent over E-UTRA PC5 based on radio configuration parameters.

<FIG> is a schematic block diagram illustrating one embodiment of a system <NUM> for sending a PC5 message over multiple RATs in a scheduled mode. The system <NUM> includes the UE <NUM> and the V2X control function <NUM> which are substantially the same as the UE <NUM> and the V2X control function <NUM> of system <NUM>. The system <NUM> also includes a first cell <NUM> (e.g., cell <NUM>, cell having a first PLMN ID - ID = <NUM>, cell supporting NR PC5 radio frequencies), a second cell <NUM> (e.g., cell <NUM>, cell having a PLMN ID - ID = <NUM>, cell supporting E-UTRA PC5 radio frequencies), and a third cell <NUM> (e.g., cell <NUM>, cell having a second PLMN ID = ID = <NUM>, cell supporting NR PC5 and E-UTRA PC5 radio frequencies).

In some embodiments, the UE <NUM> may be camped out on the first cell <NUM>. Moreover, in various embodiments, the V2X control function <NUM> may transmit information <NUM> indicating the V2X configuration <NUM>. In one embodiment, the V2X configuration <NUM> may indicate that the first V2X application <NUM> has an ID = <NUM> and that the first V2X application <NUM> is configured for NR PC5. Moreover, in such an embodiment, the V2X configuration <NUM> may indicate that the second V2X application <NUM> has an ID = <NUM> and that the second V2X application <NUM> is configured for E-UTRA PC5. In certain embodiments, the UE <NUM> may determine that the second V2X application <NUM> requires E-UTRA PC5 and the UE <NUM> may be aware that the first V2X application <NUM> requires NR PC5. The first cell <NUM> may not support E-UTRA PC5 so the UE <NUM> may search for a cell supporting E-UTRA PC5. The second cell <NUM> may support E-UTRA PC5, but only E-UTRA PC5 is supported over Uu while the third cell <NUM> supports E-UTRA PC5 and NR PC5 over Uu. Accordingly, the UE <NUM> may select <NUM> the third cell <NUM> to transmit a V2X message of the second V2X application <NUM> because the third cell <NUM> also supports PC5 communications for the first V2X application <NUM>.

In various embodiments, while in a scheduled mode of operation, if the UE <NUM> intends to use radio resources for V2X communication over PC5 the UE <NUM> may act as described in one or more of the following embodiments.

In certain embodiments, if the UE <NUM> is in an RRC_IDLE state: if a V2X application triggers the V2X layer to send a PC5 message over PC5, the UE <NUM> determines based on a V2X app ID to PC5 RAT whether the PC5 message is sent over E-UTRA or NR; the UE <NUM> then checks whether the serving cell has the radio resources available to support E-UTRA and/or NR PC5 (e.g., by checking the SIB information); if performing a cell search the UE <NUM> checks whether there are existing V2X communications that require NR and/or E-UTRA over PC5. For example, if there are existing applications that use NR and E-UTRA PC5, the UE <NUM> may search for a cell that supports both. If only E-UTRA PC5 is active, then the UE <NUM> may give priority to an E-UTRA cell. If only NR PC5 is active, then the UE <NUM> may give priority to an NR cell, and so forth.

In some embodiments, if a cell supports requested radio resources, the UE <NUM> may enter an RRC_CONNECTED state and request resource allocation to send a PC5 message. In various embodiments, if a cell does not support requested radio resources, the UE <NUM> may search for a cell in an existing PLMN that is operating the requested (e.g., provisioned) radio resources.

In certain embodiments, if the UE <NUM> does not find a cell in a registered PLMN, the UE <NUM> may check a cell in an equivalent PLMN in which authorization for V2X communications over a PC5 reference point is allowed. In some embodiments, if the UE <NUM> finds a cell in which authorization for V2X communications over a PC5 reference point is allowed but the UE <NUM> is not in the registered PLMN or a PLMN equivalent to the registered PLMN, and that cell belongs to a PLMN authorized for V2X communications over PC5 reference point and provides radio resources for V2X service, then the UE <NUM> may perform PLMN selection triggered by V2X communications over PC5 reference point as defined in TS <NUM>.

In various embodiments, if the UE <NUM> finds a cell in which authorization for V2X communications over a PC5 reference point is allowed but the cell is not in a PLMN authorized for V2X communications over the PC5 reference point, the UE <NUM> may not use V2X communications over the PC5 reference point.

In certain embodiments, if the UE <NUM> does not find any suitable cell in any PLMN, then the UE <NUM> may consider itself not served by NG-RAN and use radio resources provisioned in a UE or a UICC. If no such provision exists in the ME or the UICC or the provision does not authorize V2X communications over a PC5 reference point, then the UE <NUM> is not authorized to transmit.

In some embodiments, the UE <NUM> may have existing V2X sessions active an over PC5 (e.g., NR PC5) and a V2X application ID may require to send a PC5 message over another PC5 interface (e.g., over E-UTRA PC5), but there may be no cell in the vicinity that supports both NR PC5 and E-UTRA PC5. In such embodiments, the UE <NUM> may have to drop the existing NR PC5 sessions in order to attach to a cell supporting E-UTRA PC5. However, if there are NR PC5 services that require constant communication, dropping the existing NR PC5 sessions may interrupt such services. Accordingly, the UE <NUM> may determine whether a V2X service is allowed to preempt other services.

In various embodiments, the UE <NUM> may receive configuration information with a list of V2X application IDs that may be preempted if a new V2X application requires a service that is not supported by the serving cell and/or PLMN. The list may also include information with V2X application IDs for which preemption is not allowed. In such embodiments, if a V2X application ID requests to send a PC5 message that is not supported in a current cell, the UE <NUM> may check whether the existing V2X application can be preempted.

In certain embodiments, a V2X application may indicate that a PC5 message is for an emergency (e.g., a car broadcasting an emergency braking alert). In such embodiments, the UE <NUM> may immediately preempt all other V2X services and search for a cell that supports a carrier frequency for the emergency. In one embodiment, the UE <NUM> may be configured with a specific V2X application ID that is mapped to an emergency PC5 message.

In some embodiments, the UE <NUM> may request a RAN node for a different PC5 RAT and a network (e.g., the RAN node and/or a core network) may initiate either idle mode mobility (e.g., RRC release with a redirection indication) or connected mode mobility to a RAN node that supports a PC5 RAT requested. For this purpose, the RAN node, at a location on which the UE <NUM> is currently camping, may announce to the UE <NUM> that multiple types of PC5 RATs are supported even though that RAN node will not support all PC5 RATs. In such embodiments, the RAN node may not support all the PC5 RAT types but may be configured with other RAN nodes in the vicinity of this node that support the requested PC5 RAT. Such a network-based solution may be referred to as a fallback for V2X service(s) over PC5 interface.

In various embodiments, if the UE <NUM> is in an RRC_IDLE mode, the UE <NUM> may request resources for PC5 transmission from a RAN by entering an RRC_CONNECTED state. In certain embodiments, if the RAN node does not support a requested PC5 RAT, the RAN node may send an RRC release message including a redirect indication that contains a list of target cells that support the requested PC5 RAT. In such embodiments, the UE <NUM> may carry an idle mode mobility procedure to attach to a new cell and request resources for PC5 transmission.

In certain embodiments, if the UE <NUM> is in an ECM and/or RRC CONNECTED mode, a RAN node may initiate a handover by sending a handover request towards an MME and/or an AMF. In some embodiments, in a handover request, a RAN node may include an indication for a PC5 RAT requested. In various embodiments, an MME and/or an AMF may identify a target RAN node that supports requested PC5 and may initiate a handover command towards a RAN node that supports the requested PC5 RAT. In certain embodiments, a source RAN node may include, in a handover required message, a target cell ID that supports a requested PC5 RAT.

In some embodiments, if the UE <NUM> is in an RRC_CONNECTED mode and a source RAN node is configured target RAN nodes supporting certain PC5 RATs, the source RAN node may initiate a handover by sending a handover request towards a target RAN node (e.g., via an X2 or an Xn interface).

As may be appreciated, V2X applications may tolerate a small delay before a radio transmission is possible (e.g., <NUM> -<NUM> delay). Such a delay may result from a mobility procedure (e.g., idle mode or connected mode mobility). In certain embodiments, a RAN node may announce to the UE <NUM> which of supported PC5 RATs are associated with a certain small delay. In such embodiments, the UE <NUM> may be able to assess whether an application request for transmission over a different PC5 RAT <NUM>) has a higher priority (e.g., to pre-empt current PC5 RAT) and/or <NUM>) the application can tolerate a certain small delay for cell change. In some embodiments, an autonomous (e.g., UE-based) change of cell performed by the UE <NUM> may have a larger delay than a network-based solution because the UE <NUM> may need to scan and tune to cells supporting a different PC5 RAT.

<FIG> is a flow chart diagram illustrating one embodiment of a method <NUM> for a UE selecting a cell while the UE is camped in a <NUM> cell. The method <NUM> includes a UE camped <NUM> on a <NUM> cell. The method <NUM> includes determining <NUM> whether a V2X application or an eV2X application is triggered. If an eV2X application is triggered, the method <NUM> may determine <NUM> whether the <NUM> cell provides resources for eV2X communication. If the <NUM> cell provides resources for eV2X communication, the method <NUM> may perform <NUM><NUM> eV2X TX-RX. If the <NUM> cell does not provide resources for eV2X communication, the method <NUM> may determine <NUM> whether there are other <NUM> frequencies available for supporting eV2X. If there are other <NUM> frequencies available, <NUM> eV2X TX-RX may be performed on another <NUM> frequency.

If a V2X application is triggered, the method <NUM> may determine <NUM> whether the <NUM> cell provides resources for V2X communication over <NUM> resources. If the <NUM> cell provides resources for V2X communication over <NUM> resources, the method <NUM> may perform <NUM><NUM> V2X TX-RX. If the <NUM> cell does not provide resources for V2X communication over <NUM> resources, the method <NUM> may determine <NUM> whether other <NUM> frequencies supporting V2X communications are available. If other <NUM> frequencies supporting V2X communications are available, the method <NUM> may reselect <NUM> another <NUM> frequency and the method <NUM> may return to determining <NUM> whether the <NUM> cell provides resources for V2X communication over <NUM> resources. If other <NUM> frequencies supporting V2X communications are not available, the method <NUM> may search <NUM> for a <NUM> cell that supports V2X, and the method <NUM> may end.

<FIG> is a flow chart diagram illustrating another embodiment of a method <NUM> for a UE selecting a cell while the UE is camped in a <NUM> cell. The method <NUM> includes a UE camped <NUM> on a <NUM> cell. The method <NUM> includes determining <NUM> whether a V2X application or an eV2X application is triggered. If an eV2X application is triggered, the method <NUM> may determine <NUM> whether the <NUM> cell provides resources for eV2X communication. If the <NUM> cell provides resources for eV2X communication, the method <NUM> may perform <NUM><NUM> eV2X TX-RX. If the <NUM> cell does not provide resources for eV2X communication, the method <NUM> may determine <NUM> whether there are other <NUM> frequencies available for supporting eV2X.

If there are other <NUM> frequencies available for supporting eV2X, the method <NUM> may determine <NUM> whether the UE runs other V2X services. If the UE does not run other V2X services, the method <NUM> may perform <NUM> V2X transmission over a new cell. If the UE does run other V2X services, the method <NUM> may determine <NUM> whether the other V2X services are supported at a new cell. If the other V2X services are supported at the new cell, the method <NUM> may perform <NUM> V2X transmission over the new cell. If the other V2X services are not supported at the new cell, the method <NUM> may determine <NUM> whether the other V2X services can be preempted. If the other V2X services can be preempted, the method <NUM> may perform <NUM> V2X transmission over the new cell. If the other V2X services cannot be preempted, the method <NUM> may search <NUM> for a new cell and return to determining <NUM> whether there are other <NUM> frequencies available for supporting eV2X.

If a V2X application is triggered, the method <NUM> may determine <NUM> whether the <NUM> cell provides resources for V2X communication over <NUM> resources. If the <NUM> cell provides resources for V2X communication over <NUM> resources, the method <NUM> may determine <NUM> whether the UE runs other V2X services. The method <NUM> may then proceed through steps <NUM> through <NUM> as discussed herein. If the method <NUM> searches <NUM> for a new cell, the method <NUM> may end.

If the <NUM> cell does not provide resources for V2X communication over <NUM> resources, the method <NUM> may determine <NUM> whether other <NUM> frequencies supporting V2X communications are available. If other <NUM> frequencies supporting V2X communications are available, the method <NUM> may reselect <NUM> another <NUM> frequency and the method <NUM> may return to determining <NUM> whether the <NUM> cell provides resources for V2X communication over <NUM> resources. If other <NUM> frequencies supporting V2X communications are not available, the method <NUM> may search <NUM> for a <NUM> cell that supports V2X, and the method <NUM> may end.

<FIG> is a flow chart diagram illustrating one embodiment of a method <NUM> for a UE selecting a cell while the UE is camped in a <NUM> cell. The method <NUM> includes a UE camped <NUM> on a <NUM> cell. The method <NUM> includes determining <NUM> whether a V2X application or an eV2X application is triggered. If an eV2X application is triggered, the method <NUM> may determine <NUM> whether the <NUM> cell supports eV2X frequencies. If the <NUM> cell does not support eV2X frequencies, the method <NUM> may search <NUM> for a new cell. If the <NUM> cell does support V2X frequencies, the method <NUM> may determine <NUM> whether the UE has other V2X services. If the UE has other V2X services, the method <NUM> may determine <NUM> whether the other V2X services are supported at a new cell. If the other V2X services are supported at the new cell, the method <NUM> may perform <NUM> eV2X TX-RX. If the other V2X services are not supported at the new cell, the method <NUM> may determine <NUM> whether the other V2X services can be preempted. If the other V2X services can be preempted, the method <NUM> may perform <NUM> eV2X TX-RX. If the other V2X services cannot be preempted, the method <NUM> may search <NUM> for a new cell.

If a V2X application is triggered, the method <NUM> may determine <NUM> whether the <NUM> cell provides resources for V2X communication over <NUM> resources. If the <NUM> cell provides resources for V2X communication over <NUM> resources, the method <NUM> may perform <NUM> V2X TX-RX. If the <NUM> cell does not provide resources for V2X communication over <NUM> resources, the method <NUM> may determine <NUM> whether other <NUM> frequencies supporting V2X communications are available. If other <NUM> frequencies supporting V2X communications are available, the method <NUM> may reselect <NUM> another <NUM> frequency and the method <NUM> may return to determining <NUM> whether the <NUM> cell provides resources for V2X communication over <NUM> resources. If other <NUM> frequencies supporting V2X communications are not available, the method <NUM> may search <NUM> for a <NUM> cell that supports V2X, and the method <NUM> may end.

<FIG> is a flow chart diagram illustrating one embodiment of a method <NUM> for V2X communication over multiple radio access types. In some embodiments, the method <NUM> is performed by an apparatus, such as the remote unit <NUM>. In certain embodiments, the method <NUM> may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

The method <NUM> may include establishing <NUM>, via a remote unit <NUM>, a first plurality of network connections for direct communication with a mobile communication network and a second plurality of network connections for direct vehicle-to-everything communication with other remote units over a plurality of radio access types. In certain embodiments, the method <NUM> includes receiving <NUM> a request to transmit a vehicle-to-everything communication. In various embodiments, the method <NUM> includes determining <NUM> whether the vehicle-to-everything communication is to be transmitted via a direct communication with a mobile communication network or a direct vehicle-to-everything communication with other remote units <NUM>. In some embodiments, the method <NUM> includes determining <NUM> a radio access type of the plurality of radio access types for transmitting the vehicle-to-everything communication via a direct vehicle-to-everything communication. In certain embodiments, the method <NUM> includes selecting <NUM> a cell of a plurality of cells that supports vehicle-to-everything resource management for the vehicle-to-everything communication via a direct vehicle-to-everything communication and the radio access type. In various embodiments, the method <NUM> includes requesting <NUM> resources via the cell for transmitting the vehicle-to-everything communication via a direct vehicle-to-everything communication using the radio access type.

In certain embodiments, the plurality of radio access types comprises evolved universal terrestrial radio access, new radio, or a combination thereof. In some embodiments, the method <NUM> further comprises supporting a plurality of vehicle-to-everything applications, wherein each vehicle-to-everything application of the plurality of vehicle-to-everything applications uses a corresponding network connection of the second plurality of network connections for direct vehicle-to-everything communication with other remote units <NUM> over a corresponding radio access type of the plurality of radio access types.

In various embodiments, each vehicle-to-everything application of the plurality of vehicle-to-everything applications has a vehicle-to-everything application identifier. In one embodiment, the method <NUM> further comprises determining the radio access type for transmitting a vehicle-to-everything communication via direct vehicle-to-eveiything communication based on a mapping of the vehicle-to-everything application identifier corresponding to a vehicle-to-everything application of the plurality of vehicle-to-everything applications to a specific radio access type.

In certain embodiments, the method <NUM> further comprises determining the preemption of a first vehicle-to-everything application of the plurality of vehicle-to-everything applications based on a mapping of the vehicle-to-everything application identifier corresponding to the first vehicle-to-everything application to a preemption flag. In some embodiments, the method <NUM> further comprises determining the cell that supports vehicle-to-everything resource management based on a vehicle-to-everything carrier frequency of the first vehicle-to-everything application of the plurality of vehicle-to-everything applications.

In various embodiments, the method <NUM> further comprises determining whether the cell supports vehicle-to-everything resource management based on a vehicle-to-everything carrier frequency of a second vehicle-to-everything application of the plurality of vehicle-to-everything applications. In one embodiment, the method <NUM> further comprises determining that a second vehicle-to-everything application of the plurality of vehicle-to-everything applications cannot be preempted and, in response to the cell not supporting vehicle-to-everything resource management based on the vehicle-to-everything carrier frequency of the second vehicle-to-everything application of the plurality of vehicle-to-everything applications, selecting a different cell of the plurality of cells that supports vehicle-to-everything resource management and the carrier frequency of the second vehicle-to-everything application.

<FIG> is a flow chart diagram illustrating another embodiment of a method <NUM> for V2X communication over multiple radio access types. In some embodiments, the method <NUM> is performed by an apparatus, such as the remote unit <NUM>. In certain embodiments, the method <NUM> may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

The method <NUM> may include transmitting <NUM>, from a remote unit <NUM>, information indicating a vehicle-to-everything capability of the remote unit <NUM>. In various embodiments, the method <NUM> includes receiving <NUM> a response to the information indicating the vehicle-to-everything capability of the remote unit <NUM>. In such embodiments, the response indicates whether the remote unit <NUM> is authorized to use the vehicle-to-everything capability.

In certain embodiments, the information indicating the vehicle-to-everything capability of the remote unit <NUM> is transmitted during a registration procedure. In some embodiments, the information indicating the vehicle-to-everything capability of the remote unit <NUM> indicates whether vehicle-to-everything communication is supported. In various embodiments, the information indicating the vehicle-to-everything capability of the remote unit <NUM> indicates which vehicle-to-everything services are supported by the remote unit <NUM>, and the vehicle-to-everything services comprise evolved universal terrestrial radio access, new radio, or a combination thereof.

In certain embodiments, a unified data management authorizes the remote unit <NUM> to use the vehicle-to-everything capability. In some embodiments, the unified data management indicates to an access and mobility management function which radio access types that the remote unit <NUM> is enabled to use.

In various embodiments, the radio access types comprise evolved universal terrestrial radio access and new radio. In one embodiment, the access and mobility management function indicates to a radio access network authorization to carry out resource management for direct vehicle-to-everything communication for the remote unit <NUM> for a new radio access type, an evolved universal terrestrial radio access type, or a combination thereof.

<FIG> is a flow chart diagram illustrating a further embodiment of a method <NUM> for V2X communication over multiple radio access types. In some embodiments, the method <NUM> is performed by an apparatus, such as the network unit <NUM>. In certain embodiments, the method <NUM> may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

The method <NUM> may include receiving <NUM> information indicating a vehicle-to-everything capability of a remote unit <NUM>. In various embodiments, the method <NUM> includes transmitting <NUM> a response to the information indicating the vehicle-to-everything capability of the remote unit <NUM>. In such embodiments, the response indicates whether the remote unit <NUM> is authorized to use the vehicle-to-everything capability.

In certain embodiments, the information indicating the vehicle-to-everything capability of the remote unit <NUM> is transmitted during a registration procedure. In some embodiments, the information indicating the vehicle-to-everything capability of the remote unit <NUM> indicates whether vehicle-to-everything communication is supported. In various embodiments, the information indicating the vehicle-to-everything capability of the remote unit indicates which vehicle-to-everything services are supported by the remote unit <NUM>, and the vehicle-to-everything services comprise evolved universal terrestrial radio access, new radio, or a combination thereof.

<FIG> is a flow chart diagram illustrating yet another embodiment of a method <NUM> for V2X communication over multiple radio access types. In some embodiments, the method <NUM> is performed by an apparatus, such as the remote unit <NUM>. In certain embodiments, the method <NUM> may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

The method <NUM> may include configuring <NUM> a remote unit <NUM> with information indicating a plurality of mobile networks and a radio access type of a plurality of radio access types for direct vehicle-to-everything communication corresponding to each mobile network of the plurality of mobile networks. In various embodiments, the method <NUM> includes supporting <NUM> a plurality of vehicle-to-everything applications. In such embodiments, each vehicle-to-everything application of the plurality of vehicle-to-everything applications communicates via a direct vehicle-to-everything communication using a corresponding radio access type of the plurality of radio access types.

In certain embodiments, the plurality of radio access types comprises evolved universal terrestrial radio access, enhanced evolved universal terrestrial radio access, new radio, or some combination thereof. In some embodiments, the method <NUM> further comprises configuring the remote unit <NUM> with information indicating geographic areas for communication, wherein each geographic area of the geographic areas has a corresponding radio access type of the plurality of radio access types. In various embodiments, the method <NUM> further comprises receiving a trigger, from a vehicle-to-everything application of the plurality of vehicle-to-everything applications, to send a message via a vehicle-to-everything communication.

In one embodiment, the method <NUM> further comprises selecting to send a message via a direct vehicle-to-everything communication and determining a radio access type of the plurality of radio access types for transmitting the message via the direct vehicle-to-everything communication. In certain embodiments, in an autonomous mode, the remote unit <NUM> determines the message radio access type based on configuration information received from a vehicle-to-everything control function. In some embodiments, the message comprises a priority.

In various embodiments, the method <NUM> further comprises determining a transmission radio access type of the plurality of radio access types for transmitting the message based on the priority. In one embodiment, the method <NUM> further comprises configuring the remote unit <NUM> with a mapping between the priority and at least one radio access type of the plurality of radio access types. In certain embodiments, the transmission radio access type of the plurality of radio access types for transmitting the message is determined based on the mapping.

In some embodiments, the method <NUM> further comprises configuring the remote unit <NUM> with a mapping between application identifiers corresponding to the plurality of vehicle-to-everything applications and at least one radio access type of the plurality of radio access types.

In one embodiment, a method comprises: establishing, via a remote unit, a first plurality of network connections for direct communication with a mobile communication network and a second plurality of network connections for direct vehicle-to-everything communication with other remote units over a plurality of radio access types; receiving a request to transmit a vehicle-to-everything communication; determining whether the vehicle-to-everything communication is to be transmitted via a direct communication with a mobile communication network or a direct vehicle-to-everything communication with other remote units; determining a radio access type of the plurality of radio access types for transmitting the vehicle-to-everything communication via a direct vehicle-to-everything communication; selecting a cell of a plurality of cells that supports vehicle-to-everything resource management for the vehicle-to-everything communication via a direct vehicle-to-everything communication and the radio access type; and requesting resources via the cell for transmitting the vehicle-to-everything communication via a direct vehicle-to-everything communication using the radio access type.

In certain embodiments, the plurality of radio access types comprises evolved universal terrestrial radio access, new radio, or a combination thereof.

In some embodiments, the method further comprises supporting a plurality of vehicle-to-everything applications, wherein each vehicle-to-everything application of the plurality of vehicle-to-everything applications uses a corresponding network connection of the second plurality of network connections for direct vehicle-to-everything communication with other remote units over a corresponding radio access type of the plurality of radio access types.

In various embodiments, each vehicle-to-everything application of the plurality of vehicle-to-everything applications has a vehicle-to-everything application identifier.

In one embodiment, the method further comprises determining the radio access type for transmitting a vehicle-to-everything communication via direct vehicle-to-everything communication based on a mapping of the vehicle-to-everything application identifier corresponding to a vehicle-to-everything application of the plurality of vehicle-to-everything applications to a specific radio access type.

In certain embodiments, the method further comprises determining the preemption of a first vehicle-to-everything application of the plurality of vehicle-to-everything applications based on a mapping of the vehicle-to-everything application identifier corresponding to the first vehicle-to-everything application to a preemption flag.

In some embodiments, the method further comprises determining the cell that supports vehicle-to-everything resource management based on a vehicle-to-everything carrier frequency of the first vehicle-to-everything application of the plurality of vehicle-to-everything applications.

In various embodiments, the method further comprises determining whether the cell supports vehicle-to-everything resource management based on a vehicle-to-everything carrier frequency of a second vehicle-to-everything application of the plurality of vehicle-to-everything applications.

In one embodiment, the method further comprises determining that a second vehicle-to-everything application of the plurality of vehicle-to-everything applications cannot be preempted and, in response to the cell not supporting vehicle-to-everything resource management based on the vehicle-to-everything carrier frequency of the second vehicle-to-everything application of the plurality of vehicle-to-everything applications, selecting a different cell of the plurality of cells that supports vehicle-to-everything resource management and the carrier frequency of the second vehicle-to-everything application.

In one embodiment, an apparatus comprises: a processor that: establishes a first plurality of network connections for direct communication with a mobile communication network and a second plurality of network connections for direct vehicle-to-everything communication with other remote units over a plurality of radio access types; receives a request to transmit a vehicle-to-everything communication; determines whether the vehicle-to-everything communication is to be transmitted via a direct communication with a mobile communication network or a direct vehicle-to-everything communication with other remote units; determines a radio access type of the plurality of radio access types for transmitting the vehicle-to-everything communication via a direct vehicle-to-everything communication; selects a cell of a plurality of cells that supports vehicle-to-everything resource management for the vehicle-to-everything communication via a direct vehicle-to-everything communication and the radio access type; and requests resources via the cell for transmitting the vehicle-to-everything communication via a direct vehicle-to-everything communication using the radio access type.

In some embodiments, the processor supports a plurality of vehicle-to-everything applications, and each vehicle-to-everything application of the plurality of vehicle-to-everything applications uses a corresponding network connection of the second plurality of network connections for direct vehicle-to-everything communication with other remote units over a corresponding radio access type of the plurality of radio access types.

In one embodiment, the processor determines the radio access type for transmitting a vehicle-to-everything communication via direct vehicle-to-eveiything communication based on a mapping of the vehicle-to-everything application identifier corresponding to a vehicle-to-everything application of the plurality of vehicle-to-everything applications to a specific radio access type.

In certain embodiments, the processor determines the preemption of a first vehicle-to-everything application of the plurality of vehicle-to-everything applications based on a mapping of the vehicle-to-everything application identifier corresponding to the first vehicle-to-everything application to a preemption flag.

In some embodiments, the processor determines the cell that supports vehicle-to-everything resource management based on a vehicle-to-everything carrier frequency of the first vehicle-to-everything application of the plurality of vehicle-to-everything applications.

In various embodiments, the processor determines whether the cell supports vehicle-to-everything resource management based on a vehicle-to-everything carrier frequency of a second vehicle-to-everything application of the plurality of vehicle-to-everything applications.

In one embodiment, the processor determines that a second vehicle-to-everything application of the plurality of vehicle-to-everything applications cannot be preempted and, in response to the cell not supporting vehicle-to-everything resource management based on the vehicle-to-everything carrier frequency of the second vehicle-to-everything application of the plurality of vehicle-to-everything applications, selects a different cell of the plurality of cells that supports vehicle-to-everything resource management and the carrier frequency of the second vehicle-to-everything application.

In one embodiment, a method comprises: transmitting, from a remote unit, information indicating a vehicle-to-everything capability of the remote unit; and receiving a response to the information indicating the vehicle-to-everything capability of the remote unit, wherein the response indicates whether the remote unit is authorized to use the vehicle-to-everything capability.

In certain embodiments, the information indicating the vehicle-to-everything capability of the remote unit is transmitted during a registration procedure.

In some embodiments, the information indicating the vehicle-to-everything capability of the remote unit indicates whether vehicle-to-everything communication is supported.

In various embodiments, the information indicating the vehicle-to-everything capability of the remote unit indicates which vehicle-to-everything services are supported by the remote unit, and the vehicle-to-everything services comprise evolved universal terrestrial radio access, new radio, or a combination thereof.

In certain embodiments, a unified data management authorizes the remote unit to use the vehicle-to-everything capability.

In some embodiments, the unified data management indicates to an access and mobility management function which radio access types that the remote unit is enabled to use.

In various embodiments, the radio access types comprise evolved universal terrestrial radio access, new radio, or a combination thereof.

In one embodiment, the access and mobility management function indicates to a radio access network authorization to carry out resource management for direct vehicle-to-everything communication for the remote unit for a new radio access type, an evolved universal terrestrial radio access type, or a combination thereof.

In one embodiment, an apparatus comprises: a transmitter that transmits information indicating a vehicle-to-everything capability of the apparatus; and a receiver that receives a response to the information indicating the vehicle-to-everything capability of the apparatus, wherein the response indicates whether the apparatus is authorized to use the vehicle-to-everything capability.

In certain embodiments, the information indicating the vehicle-to-everything capability of the apparatus is transmitted during a registration procedure.

In some embodiments, the information indicating the vehicle-to-everything capability of the apparatus indicates whether vehicle-to-everything communication is supported.

In various embodiments, the information indicating the vehicle-to-everything capability of the apparatus indicates which vehicle-to-everything services are supported by the apparatus, and the vehicle-to-everything services comprise evolved universal terrestrial radio access, new radio, or a combination thereof.

In certain embodiments, a unified data management authorizes the apparatus to use the vehicle-to-everything capability.

In some embodiments, the unified data management indicates to an access and mobility management function which radio access types that the apparatus is enabled to use.

In one embodiment, the access and mobility management function indicates to a radio access network authorization to carry out resource management for direct vehicle-to-everything communication for the apparatus for a new radio access type, an evolved universal terrestrial radio access type, or a combination thereof.

In one embodiment, a method comprises: receiving information indicating a vehicle-to-everything capability of a remote unit; and transmitting a response to the information indicating the vehicle-to-everything capability of the remote unit, wherein the response indicates whether the remote unit is authorized to use the vehicle-to-everything capability.

In one embodiment, an apparatus comprises: a receiver that receives information indicating a vehicle-to-everything capability of a remote unit; and a transmitter that transmits a response to the information indicating the vehicle-to-everything capability of the remote unit, wherein the response indicates whether the remote unit is authorized to use the vehicle-to-everything capability.

In one embodiment, a method comprises: configuring a remote unit with information indicating a plurality of mobile networks and a radio access type of a plurality of radio access types for direct vehicle-to-everything communication corresponding to each mobile network of the plurality of mobile networks; and supporting a plurality of vehicle-to-everything applications, wherein each vehicle-to-everything application of the plurality of vehicle-to-everything applications communicates via a direct vehicle-to-everything communication using a corresponding radio access type of the plurality of radio access types.

In certain embodiments, the plurality of radio access types comprises evolved universal terrestrial radio access, enhanced evolved universal terrestrial radio access, new radio, or some combination thereof.

In some embodiments, the method further comprises configuring the remote unit with information indicating geographic areas for communication, wherein each geographic area of the geographic areas has a corresponding radio access type of the plurality of radio access types.

In various embodiments, the method further comprises receiving a trigger, from a vehicle-to-everything application of the plurality of vehicle-to-everything applications, to send a message via a vehicle-to-everything communication.

In one embodiment, the method further comprises selecting to send a message via a direct vehicle-to-everything communication and determining a radio access type of the plurality of radio access types for transmitting the message via the direct vehicle-to-everything communication.

In certain embodiments, in an autonomous mode, the remote unit determines the message radio access type based on configuration information received from a vehicle-to-everything control function.

In some embodiments, the message comprises a priority.

In various embodiments, the method further comprises determining a transmission radio access type of the plurality of radio access types for transmitting the message based on the priority.

In one embodiment, the method further comprises configuring the remote unit with a mapping between the priority and at least one radio access type of the plurality of radio access types.

In certain embodiments, the transmission radio access type of the plurality of radio access types for transmitting the message is determined based on the mapping.

In some embodiments, the method further comprises configuring the remote unit with a mapping between application identifiers corresponding to the plurality of vehicle-to-everything applications and at least one radio access type of the plurality of radio access types.

In one embodiment, an apparatus comprises: a processor that: configures the apparatus with information indicating a plurality of mobile networks and a radio access type of a plurality of radio access types for direct vehicle-to-everything communication corresponding to each mobile network of the plurality of mobile networks; and supports a plurality of vehicle-to-everything applications, wherein each vehicle-to-everything application of the plurality of vehicle-to-everything applications communicates via a direct vehicle-to-everything communication using a corresponding radio access type of the plurality of radio access types.

In some embodiments, the processor configures the apparatus with information indicating geographic areas for communication, and each geographic area of the geographic areas has a corresponding radio access type of the plurality of radio access types.

In various embodiments, the apparatus further comprises a receiver that receives a trigger, from a vehicle-to-everything application of the plurality of vehicle-to-everything applications, to send a message via a vehicle-to-everything communication.

In one embodiment, the processor selects to send a message via a direct vehicle-to-everything communication and determines a radio access type of the plurality of radio access types for transmitting the message via the direct vehicle-to-everything communication.

In certain embodiments, in an autonomous mode, the processor determines the message radio access type based on configuration information received from a vehicle-to-everything control function.

In various embodiments, the processor determines a transmission radio access type of the plurality of radio access types for transmitting the message based on the priority.

In one embodiment, the processor configures the apparatus with a mapping between the priority and at least one radio access type of the plurality of radio access types.

In some embodiments, the processor configures the apparatus with a mapping between application identifiers corresponding to the plurality of vehicle-to-everything applications and at least one radio access type of the plurality of radio access types.

Claim 1:
A method performed by a user equipment, UE, (<NUM>), the method comprising:
establishing (<NUM>) a first plurality of network connections for direct communication with a mobile communication network and a second plurality of network connections for direct vehicle-to-everything, V2X, communication with other UEs (<NUM>), both the first plurality of network connections and the second plurality of network connections being over a plurality of radio access types, wherein the plurality of radio access types comprises evolved universal terrestrial radio access, EUTRA, and new radio, NR, and wherein the UE (<NUM>) supports both the first plurality of network connections and the second plurality of network connections simultaneously;
receiving (<NUM>) a request to transmit a V2X communication;
determining (<NUM>) whether the V2X communication is to be transmitted via a direct communication with a mobile communication network using the first plurality of network connections or a direct V2X communication with other UEs (<NUM>) using the second plurality of network connections; and
in the event that the V2X communication is to be transmitted via the direct V2X communication using the second plurality of network connections:
determining (<NUM>) a radio access type of the plurality of radio access types for transmitting the V2X communication via the direct V2X communication using the second plurality of network connection;
selecting (<NUM>) a cell of a plurality of cells that supports V2X resource management for the V2X communication via the direct V2X communication using the second plurality of network connection and the radio access type; and
requesting (<NUM>) resources via the cell for transmitting the V2X communication via the direct V2X communication using the second plurality of network connection and using the radio access type.