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"), Device-to-Device ("D2D"), 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> discloses a pedestrian user equipment (P-UE) which participates in P-UE related V2X communications comprises processor circuitry and a transmitter.

Methods for V2X communication over multiple radio access types are disclosed. Apparatuses and systems also perform the functions of the apparatus.

<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 support transmission of vehicle-to-everything messages over a first plurality of network connections for communication with a mobile communication network over a plurality radio access types 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 remote unit <NUM> may support a first plurality of vehicle-to-everything applications, wherein each vehicle-to-everything application of the first plurality of vehicle-to-everything applications uses the vehicle-to-everything messages transmitted via direct vehicle-to-everything communication over a radio access type of the plurality of radio access types and over a corresponding carrier frequency. In various embodiments, the remote unit <NUM> may support a second plurality of vehicle-to-everything applications, wherein each vehicle-to-everything application of the second plurality of vehicle-to-everything applications uses the vehicle-to-everything messages transmitted via the mobile communication network. In some embodiments, the remote unit <NUM> may receive a request from a vehicle-to-everything application of the first plurality of vehicle-to-everything applications or the second plurality of vehicle-to-everything applications to transmit a message via the direct vehicle-to-everything communication or via the mobile communication network. In certain embodiments, the remote unit <NUM> may determine a transmission radio access type and a transmission carrier frequency for transmitting the message over direct vehicle-to-everything communication. 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: support transmission of vehicle-to-everything messages over a first plurality of network connections for communication with a mobile communication network over a plurality radio access types and a second plurality of network connections for direct vehicle-to-everything communication with other remote units over a plurality of radio access types; support a first plurality of vehicle-to-everything applications, wherein each vehicle-to-everything application of the first plurality of vehicle-to-everything applications uses the vehicle-to-everything messages transmitted via direct vehicle-to-everything communication over a radio access type of the plurality of radio access types and over a corresponding carrier frequency; support a second plurality of vehicle-to-everything applications, wherein each vehicle-to-everything application of the second plurality of vehicle-to-everything applications uses the vehicle-to-everything messages transmitted via the mobile communication network; and determine a transmission radio access type and a transmission carrier frequency for transmitting the message over direct vehicle-to-everything communication.

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 some embodiments, the receiver <NUM> receives a request from a vehicle-to-everything application of the first plurality of vehicle-to-everything applications or the second plurality of vehicle-to-everything applications to transmit a message via the direct vehicle-to-everything communication or via the mobile communication network.

<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.

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>.

<FIG> is a schematic block diagram illustrating one embodiment of a system <NUM> for sending a V2X message in a scheduled mode of operation. The system <NUM> includes a UE <NUM>. The UE <NUM> may be substantially similar to 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 application ID to radio configuration, an application ID to TX profile mapping, and/or a TX profile (e.g., E-UTRA, enhanced E-UTRA, NR).

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> has an AS layer <NUM> in communication with the V2X client <NUM>. As illustrated, the system <NUM> also includes a V2X control function <NUM>.

In some embodiments, the second V2X application <NUM> sends a message <NUM> to the V2X client <NUM> (e.g., the V2X layer) including the application ID. In various embodiments, the V2X client <NUM> may check <NUM> the V2X configuration <NUM> for the application ID to identify the carrier frequency and TX profile required to transmit the message.

In certain embodiments, the V2X client <NUM> sends <NUM> the requirements for the operating carrier frequency and TX profile to the AS layer <NUM>. In some embodiments, the AS layer <NUM> checks <NUM> whether the current cell supports the operating carrier frequency for D2D communication for the second V2X application <NUM>. If the cell does not support the operating carrier frequency, the AS layer <NUM> performs a PLMN selection.

In various embodiments, if a new V2X application requests to send a message over PC5, the UE <NUM> may select a different cell not supporting carrier frequencies of other V2X applications that are required to send messages over PC5. In certain embodiments, some V2X applications may transition to out of coverage operation, but this may affect the performance because scheduled mode operation may facilitate better resource management. In some embodiments, if a new V2X application requests to send a message over PC5, the UE <NUM> may select a cell that supports E-UTRA communications only. In such embodiments, V2X applications that are required to send message over Uu may be affected because E-UTRA may not support some QoS profiles or may not support URLLC communications, for example.

In one example, the UE <NUM> is served by E-UTRAN running one V2X application over PC5 (e.g., the first V2X application <NUM>) with radio resources provided by a serving cell. The UE <NUM> has also a V2X application (e.g., the second V2X application <NUM>) sending V2X messages via Uu. A new V2X application (e.g., a third V2X application) requests to send a message over PC5. The UE <NUM> detects that the serving cell does not support the carrier frequency required by the third V2X application. This results in the UE <NUM> potentially selecting a new cell interrupting services of the first V2X application <NUM> and the second V2X application <NUM> because the AS layer <NUM> does not have the visibility to identify the RAT type of frequency required by each active V2X application so the AS layer <NUM> will act based on an indication from the V2X layer.

In various embodiments, if a new V2X application (e.g., an application that was inactive) requests to send a message over PC5, the UE <NUM> may select a cell supporting the carrier frequency of the V2X service but may only support E-UTRA over Uu. In such embodiments, there may be V2X applications that are required to send message over NR Uu. Accordingly, if a cell is selected that support E-UTRA over Uu, the cell may not support some QoS profiles required by the V2X application.

In certain embodiments, configuration information corresponding to V2X applications may indicate whether the V2X applications are required to transmit V2X messages via Uu. In some embodiments, the UE <NUM> may receive additional configuration information indicating a required RAT type if transmitting a V2X message over Uu. In such embodiments, the UE <NUM> may use this configuration to determine whether the UE <NUM> needs to be on a cell supporting LTE-Uu or NR-Uu if a V2X message needs to be sent via a mobile communication network. In various embodiments, if the RAT preference configuration is present and the V2X application requests to send a V2X message via Uu and if the UE <NUM> determines that the cell supports the preferred RAT, then the UE <NUM> may send the V2X message. In certain embodiments, if the UE <NUM> determines that the cell does not support the preferred RAT, then the UE <NUM> does not send the V2X message.

In some embodiments, if there are multiple V2X applications active, the UE <NUM> needs additional configurations to identify if a new cell needs to be selected and which V2X applications must be supported in that cell. To support such an approach, two additional parameters may be included in the V2X configuration (e.g., a preemption flag and a priority of the V2X application).

An example configuration is as follows for a V2X configuration for V2X applications over Uu: V2X application ID to V2X application server address (e.g., Uu and/or RAT preference (LTE-Uu and/or NR-Uu), preemption indicator, priority).

In various embodiments, the UE <NUM> may be configured with V2X applications over PC5 that operate only in scheduled mode operation if sending V2X messages over PC5. In certain embodiments, if there are multiple V2X application active, the UE <NUM> may need configuration information to determine which V2X application must be in the scheduled mode operation and its priority. In such embodiments, the V2X configuration may be as follows: V2X Application ID to Radio Frequency (e.g., operation mode (mode <NUM> and/or mode <NUM> supported - if an application supports mode <NUM> only, then the application will operate only if a cell supports the V2X application's carrier frequency, otherwise no V2X message may be transmitted), preemption indicator, priority).

In some embodiments, if a V2X application requests to send a V2X message (e.g., over Uu or over PC5) the UE <NUM> determines how to select a cell as follows: <NUM>) The UE <NUM> first determines whether the current cell the UE <NUM> has selected (is camped on) supports the operating carrier frequency (e.g., if the message is sent over PC5) or the RAT preference (e.g., if the message is sent over Uu) of the new V2X application. The V2X client <NUM> checks with the lower layers to determine whether the new V2X application requirements (e.g., carrier frequency or RAT preference) are supported in the serving cell; <NUM>) If the AS layer <NUM> reports that the current cell does not support the carrier frequency, the UE <NUM> (e.g., the V2X client <NUM>) may request that the AS layer <NUM> find a cell supporting the carrier frequency or RAT preference of the new V2X application and also the carrier frequency (e.g., for V2X messages over PC5) and/or RAT preference (e.g., for V2X messages over Uu) of the other active V2X applications. The V2X client <NUM> checks with the lower layers to determine whether there is such a cell that supports all active application requirements; and <NUM>) If the AS layer <NUM> reports that no such cell is found, the UE <NUM> (e.g., the V2X client <NUM>) needs to determine which active V2X applications need to be supported (e.g., because the UE <NUM> may have to select a new cell that could support all active V2X applications). The UE <NUM> (e.g., the V2X client <NUM>) checks the priority and the preemption configuration to determine the V2X applications that need to be supported by a cell. For example, the UE <NUM> may determine that a V2X application sending messages over Uu must be on a cell supporting NR or that a V2X application sending messages over PC5 must run on scheduled mode operation and must not be preempted. The UE <NUM> uses the priority configuration to select the highest priority application and decide which application cannot be supported by a cell (e.g., based on the preemption configuration). Once the UE <NUM> selects the V2X applications (e.g., based on the priority and preemption information), the UE <NUM> checks with the lower layers to determine whether there is a cell that supports the prioritized V2X applications. If there is such cell, the UE <NUM> selects the cell and transmits the V2X message accordingly. V2X application that are not supported in the new selected cell will operate as out of coverage.

For example, if the UE <NUM> receives a request from a third V2X application to send a V2X over PC5 and has an active application sending a V2X message over Uu and PC5, the UE <NUM> may be configured with the following: <NUM>) The first V2X application <NUM>: Priority: <NUM>; RAT preference: NR-Uu; and Preempt: No. <NUM>) The second V2X Application <NUM>: Priority: <NUM>; Carrier Frequency: Y; and Preempt: No. <NUM>) The third V2X Application: Priority: <NUM>; Carrier Frequency: X; and Preempt: Yes.

In such an example, the UE <NUM> may check whether the third V2X application can be supported in the current cell. If the third V2X application cannot be supported, the UE <NUM> (e.g., the V2X client <NUM>) checks with the AS layer <NUM> to determine whether there is a cell that supports all V2X application requirements. If there is no such cell, the V2X client <NUM> determines that the third V2X application has the lowest priority and can be preempted. Therefore, the UE <NUM> will request that the AS layer <NUM> selects a cell supporting NR-Uu and Carrier Frequency: Y.

<FIG> is a schematic block diagram illustrating one embodiment of a system <NUM> for a V2X client request to select a cell based on a V2X application priority and a preemption configuration. The system <NUM> includes the UE <NUM>. The UE <NUM> may be substantially similar to the UE <NUM> of <FIG> and/or the remote unit <NUM> as described herein. Moreover, the UE <NUM> includes the V2X client <NUM> and has the V2X configuration <NUM> (V2X config). The V2X configuration <NUM> may include: a radio configuration per application ID; an application ID to TX profile mapping; a TX profile (e.g., E-UTRA, enhanced E-UTRA, NR); a mapping of an application ID to V2X AS, RAT preference, a priority, and/or a preemption; and/or a mapping of an application ID to carrier frequency, a priority, and/or a preemption.

The UE <NUM> also includes the first V2X application <NUM> (first V2X app) and the second V2X application <NUM> (second V2X app). The UE <NUM> has the AS layer <NUM> in communication with the V2X client <NUM>. As illustrated, the system <NUM> also includes the V2X control function <NUM>.

In certain embodiments, the first V2X application <NUM> is active and sends <NUM> V2X messages to the V2X client <NUM> via Uu. In some embodiments, the second V2X application <NUM> sends <NUM> a request to the V2X client <NUM> to transmit a message via PC5. In various embodiments, the V2X client <NUM> may check the V2X configuration <NUM> for the application ID to identify the carrier frequency and TX profile required to transmit the message. The V2X client <NUM> may determine that the second V2X application <NUM> cannot be supported by the current cell. Moreover, the V2X client <NUM> (e.g., V2X layer) may determine that there is a V2X application sending V2X messages over Uu, determine that NR over Uu is required, and that the V2X application must not be preempted. Accordingly, the V2X client <NUM> sends <NUM> the cell preferences to the AS layer <NUM> indicating that the new cell must support the carrier frequency of the second V2X application <NUM> and must also support NR-Uu.

In some embodiments, the AS layer <NUM> checks <NUM> whether the current cell supports the operating carrier frequency for the second V2X application <NUM> and NR-Uu. If the AS layer <NUM> does not find another cell, the UE <NUM> may send the V2X message over PC5 as out-of-coverage.

<FIG> is a flow chart diagram illustrating one embodiment of a method for selection of a cell to support multiple V2X applications. The method <NUM> includes a V2X application being triggered <NUM>. The method <NUM> determines <NUM> whether the V2X application is to use PC5 or Uu. If the V2X application is to use PC5, the method <NUM> may determine <NUM> whether the <NUM> cell provides resources for V2X communication. If the <NUM> cell provides resources for V2X communication, the method <NUM> may send <NUM> the V2X message, and the method <NUM> may end. If the <NUM> cell does not provide resources for V2X communication, the method <NUM> may determine <NUM> whether there are other V2X applications active.

If there are other V2X application active, the method <NUM> may determine <NUM> whether there is any cell that supports all active V2X applications. If there is a cell that supports all active V2X applications, the method <NUM> may send <NUM> the V2X message, and the method <NUM> may end. If there is no cell that supports all active V2X applications, the method <NUM> may determine <NUM> V2X applications that require a cell based on priority and preemption and may identify the corresponding cell. If a corresponding cell is identified, the method <NUM> may send <NUM> the V2X message, and the method <NUM> may end.

If the V2X application is to use Uu, the method <NUM> may determine <NUM> whether the <NUM> cell supports a RAT preference. If the <NUM> cell supports the RAT preference, the method <NUM> may send <NUM> the V2X message, and the method <NUM> may end. If the <NUM> cell does not support the RAT preference, the method <NUM> may determine <NUM> whether there are other V2X applications active.

In various embodiments, the UE <NUM> (e.g., the V2X client <NUM>) sends to lower layers (e.g., the AS layer <NUM>) a list of prioritized cell selection procedures. For example, if the UE <NUM> determines that a new V2X application cannot be supported in the current cell, the V2X client <NUM> constructs a list of V2X applications in priority order according to their priority status and checks their V2X application requirements. The V2X client <NUM> then sends to the AS layer <NUM> a list of prioritized cell selection procedures. The AS layer <NUM> selects a cell according to the list in priority order.

In such embodiments, the V2X client <NUM> may evaluate the priority of each active V2X application and send a prioritized list of cell selection to the AS layer <NUM>, such as the following cell selection: Priority <NUM>: Support NR-Uu and Carrier Frequency: Y and Carrier Frequency: X; Priority <NUM>: Support NR-Uu and Carrier Frequency: Y; and Priority <NUM>: Support NR-Uu.

Moreover, in such embodiments, the AS layer <NUM> may go through the list of priority to select a cell. Based on the cell selected the UE <NUM> may configure the V2X application as in-coverage if supported by the new cell selected and out of coverage if not supported by the new cell.

In certain embodiments, if each cell support only one V2X application carrier frequency, the V2X client <NUM> may construct a list of V2X applications in priority order and send to the AS layer <NUM> a list of carrier frequencies in priority order. In such embodiments, the cell selection list may be as follows: Priority <NUM>: Support NR-Uu an Carrier Frequency Y; and Priority <NUM>: Support NR-Uu and Carrier Frequency X.

<FIG> is a schematic block diagram illustrating one embodiment of a system <NUM> for a V2X client sending a list of cell selection preferences in priority order based on a V2X application priority. The system <NUM> includes the UE <NUM>. The UE <NUM> may be substantially similar to the UE <NUM> of <FIG> and/or the remote unit <NUM> as described herein. Moreover, the UE <NUM> includes the V2X client <NUM> and has the V2X configuration <NUM> (V2X config). The V2X configuration <NUM> may include: a radio configuration per application ID; an application ID to TX profile mapping; a TX profile (e.g., E-UTRA, enhanced E-UTRA, NR); a mapping of an application ID to V2X AS, RAT preference, a priority, and/or a preemption; and/or a mapping of an application ID to carrier frequency, a priority, and/or a preemption.

In certain embodiments, the first V2X application <NUM> is active and sends <NUM> V2X messages to the V2X client <NUM> via Uu. In some embodiments, the second V2X application <NUM> sends <NUM> a request to the V2X client <NUM> to transmit a message via PC5. In various embodiments, the V2X client <NUM> may check the V2X configuration <NUM> for the application ID to identify the carrier frequency and TX profile required to transmit the message. The V2X client <NUM> may determine that the second V2X application <NUM> cannot be supported by the current cell. Moreover, the V2X client <NUM> (e.g., V2X layer) may construct a list of cell selection in priority order according to a V2X application priority and preemption configuration. The V2X client <NUM> transmits <NUM> the list of cell selection in priority order to the AS layer <NUM>.

In some embodiments, the AS layer <NUM> selects <NUM> a cell according to the priority order.

<FIG> is a flow chart diagram illustrating one embodiment of a method <NUM> for selection of a cell based on a V2X client sending a list of cell selection preferences in priority order. The method <NUM> includes a V2X application being triggered <NUM>. The method <NUM> determines <NUM> whether the V2X application is to use PC5 or Uu. If the V2X application is to use PC5, the method <NUM> may determine <NUM> whether the <NUM> cell provides resources for V2X communication. If the <NUM> cell provides resources for V2X communication, the method <NUM> may send <NUM> the V2X message, and the method <NUM> may end. If the <NUM> cell does not provide resources for V2X communication, the method <NUM> may determine <NUM> whether there are other V2X applications active.

If there are other V2X application active, the method <NUM> may construct <NUM> a list of prioritized V2X applications based on the priority and preemption configuration, then sends the list of cell selection preferences in priority order. If the list is constructed, the method <NUM> may determine <NUM> if there is a cell supporting the cell selection preferences. If there is a supporting cell, the method <NUM> may send <NUM> the V2X message, and the method <NUM> may end.

In some embodiments, if a V2X application requests to send a V2X message (e.g., over Uu or over PC5) the V2X client <NUM> requests from the AS layer <NUM> what each cell in the vicinity of the UE <NUM> supports. The V2X client <NUM> may request to report what V2X carrier frequencies are supported by cells of the registered PLMN or via any PLMN.

In certain embodiments, the AS layer <NUM> may provide the following information to the V2X client: cell ID; V2X carrier frequency (or frequencies) supported; NR-Uu and/or E-UTRA Uu support. The V2X client may use such information to determine: whether a new cell needs to be selected; and/or if all active V2X applications can be supported.

In various embodiments, the V2X client <NUM> uses the V2X application priority and preemption configuration to determine which V2X applications can be supported. Once the V2X client <NUM> decides on the V2X application, the V2X client <NUM> sends a request to the AS layer <NUM> to select one of the cell reported by the AS layer <NUM> that can support the selected V2X applications.

<FIG> is a schematic block diagram illustrating one embodiment of a system <NUM> for an AS layer providing assistance information to a V2X client for cell selection. The system <NUM> includes the UE <NUM>. The UE <NUM> may be substantially similar to the UE <NUM> of <FIG> and/or the remote unit <NUM> as described herein. Moreover, the UE <NUM> includes the V2X client <NUM> and has the V2X configuration <NUM> (V2X config). The V2X configuration <NUM> may include: a radio configuration per application ID; an application ID to TX profile mapping; a TX profile (e.g., E-UTRA, enhanced E-UTRA, NR); a mapping of an application ID to V2X AS, RAT preference, a priority, and/or a preemption; and/or a mapping of an application ID to carrier frequency, a priority, and/or a preemption.

In certain embodiments, the first V2X application <NUM> is active and sends <NUM> V2X messages to the V2X client <NUM> via Uu. In some embodiments, the second V2X application <NUM> sends <NUM> a request to the V2X client <NUM> to transmit a message via PC5. In various embodiments, the V2X client <NUM> may check the V2X configuration <NUM> for the application ID to identify the carrier frequency and TX profile required to transmit the message. The V2X client <NUM> may determine that the second V2X application <NUM> cannot be supported by the current cell. Moreover, the V2X client <NUM> (e.g., V2X layer) may construct a prioritized list of active V2X applications and request from the AS layer <NUM> a list of cell IDs that support the V2X carrier frequencies and/or RAT preferences of active V2X applications. Based on the list of cell IDs provided by the AS layer <NUM>, the V2X client <NUM> instructs <NUM> the AS layer <NUM> to select one of the cell IDs that supports active V2X applications.

In some embodiments, the AS layer <NUM> selects <NUM> a cell based on the V2X client <NUM> feedback.

In various embodiments, a decision to send a V2X message to the AS layer <NUM> for transmission may rely purely on the V2X application layer. In one embodiment, the V2X layer is configured by the V2X control function <NUM> with information that indicates the V2X application prioritization. Such prioritization may be used by the V2X layer to decide how to send V2X messages.

For example, if the UE <NUM> runs two V2X applications, the V2X control function may provide the following configuration: <NUM>) the first V2X application <NUM>: Priority <NUM>; Preemption: No. <NUM>) the second V2X application <NUM>: Priority <NUM>; Preemption: Yes.

In some embodiments, the V2X layer may use the configuration as follows: <NUM>) If the second V2X application <NUM> is active and the first V2X application <NUM> requires to send a V2X message, the V2X layer first checks whether the second V2X application <NUM> can be supported by the serving cell. If the V2X application cannot be supported, the V2X client checks the V2X configuration and identifies that the first V2X application <NUM> is of higher priority and that the second V2X application <NUM> can be preempted. The V2X layer decides to request resources for the first V2X application <NUM>. The second V2X application <NUM> will operate as out of coverage. <NUM>) If the first V2X application <NUM> is active and the second V2X application <NUM> requires to send a V2X message, the V2X layer asks the lower layer if the second V2X application <NUM> can be supported. If the second V2X application <NUM> cannot be supported, the V2X client <NUM> checks the V2X configuration and determines that the second V2X application <NUM> is of lower priority. The V2X client <NUM> decides not to request cell resources for the second V2X application <NUM>. In such a case, the second V2X application <NUM> will operate as out of coverage.

<FIG> is a schematic block diagram illustrating one embodiment of a system <NUM> for transmitting a V2X message if multiple V2X applications are active without impacting an AS layer. The system <NUM> includes the UE <NUM>. The UE <NUM> may be substantially similar to the UE <NUM> of <FIG> and/or the remote unit <NUM> as described herein. Moreover, the UE <NUM> includes the V2X client <NUM> and has the V2X configuration <NUM> (V2X config). The V2X configuration <NUM> may include: for an application with a first application ID (E-UTRA PC5 radio configuration, NR PC5 radio configuration, application ID to TX profile mapping, TX profile (E-UTRA, enhanced E-UTRA, NR), V2X application priority); and for an application with a second application ID (E-UTRA PC5 radio configuration, NR PC5 radio configuration, application ID to TX profile mapping, TX profile (E-UTRA, enhanced E-UTRA, NR), V2X application priority).

In some embodiments, the second V2X application <NUM> sends <NUM> a request to the V2X client <NUM> to transmit a message via V2X. The first V2X application <NUM> is already running a V2X service. In various embodiments, the V2X client <NUM> may check <NUM> the V2X configuration <NUM> for the second V2X application <NUM> to identify the carrier frequency and TX profile required to transmit the message. The V2X client <NUM> may determine that the second V2X application <NUM> cannot be supported by the current cell. Moreover, the V2X client <NUM> (e.g., V2X layer) may determine that there are active V2X applications of lower priority and decide to send the V2X message to the lower layers.

In some embodiments, the AS layer <NUM> selects <NUM> checks whether a current cell can support the requested parameters. If the AS layer <NUM> finds another cell that requires a different carrier frequency, the AS layer <NUM> may perform PLMN selection.

<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 supporting <NUM> transmission of vehicle-to-everything messages over a first plurality of network connections for communication with a mobile communication network over a plurality radio access types 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 supporting <NUM> a first plurality of vehicle-to-everything applications, wherein each vehicle-to-everything application of the first plurality of vehicle-to-everything applications uses the vehicle-to-everything messages transmitted via direct vehicle-to-everything communication over a radio access type of the plurality of radio access types and over a corresponding carrier frequency. In various embodiments, the method <NUM> includes supporting <NUM> a second plurality of vehicle-to-everything applications, wherein each vehicle-to-everything application of the second plurality of vehicle-to-everything applications uses the vehicle-to-everything messages transmitted via the mobile communication network. In some embodiments, the method <NUM> includes receiving <NUM> a request from a vehicle-to-everything application of the first plurality of vehicle-to-everything applications or the second plurality of vehicle-to-everything applications to transmit a message via the direct vehicle-to-everything communication or via the mobile communication network. In certain embodiments, the method <NUM> includes determining <NUM> a transmission radio access type and a transmission carrier frequency for transmitting the message over direct vehicle-to-everything communication.

In certain embodiments, the method <NUM> further comprises: selecting vehicle-to-everything applications of the first plurality of vehicle-to-everything applications or the second plurality of vehicle-to-everything applications that use direct vehicle-to-everything communication or the mobile communication network via a cell based on a priority and a preemption configuration; and selecting the cell that supports the selected vehicle-to-everything applications. In some embodiments, the priority corresponds to an application radio access type of the plurality of radio access types. In various embodiments, the priority corresponds to an application carrier frequency.

In one embodiment, the priority corresponds to an application radio access type of the plurality of radio access types and an application carrier frequency. In certain embodiments, the priority corresponds to an application radio access type of the plurality of radio access types and a plurality of application carrier frequencies. In some embodiments, the plurality of radio access types comprises evolved universal terrestrial radio access and new radio.

In various embodiments, determining the transmission radio access type and the transmission carrier frequency for transmitting the vehicle-to-everything message comprises identifying the transmission radio access type and the transmission carrier frequency based on a highest priority vehicle-to-everything application of the second plurality of vehicle-to-everything applications that includes a preferred radio access type of the plurality of radio access types.

In one embodiment, a method comprises: supporting transmission of vehicle-to-everything messages over a first plurality of network connections for communication with a mobile communication network over a plurality radio access types and a second plurality of network connections for direct vehicle-to-everything communication with other remote units over a plurality of radio access types; supporting a first plurality of vehicle-to-everything applications, wherein each vehicle-to-everything application of the first plurality of vehicle-to-everything applications uses the vehicle-to-everything messages transmitted via direct vehicle-to-everything communication over a radio access type of the plurality of radio access types and over a corresponding carrier frequency; supporting a second plurality of vehicle-to-everything applications, wherein each vehicle-to-everything application of the second plurality of vehicle-to-everything applications uses the vehicle-to-everything messages transmitted via the mobile communication network; receiving a request from a vehicle-to-everything application of the first plurality of vehicle-to-everything applications or the second plurality of vehicle-to-everything applications to transmit a message via the direct vehicle-to-everything communication or via the mobile communication network; and determining a transmission radio access type and a transmission carrier frequency for transmitting the message over direct vehicle-to-everything communication.

In certain embodiments, the method further comprises: selecting vehicle-to-everything applications of the first plurality of vehicle-to-everything applications or the second plurality of vehicle-to-everything applications that use direct vehicle-to-everything communication or the mobile communication network via a cell based on a priority and a preemption configuration; and selecting the cell that supports the selected vehicle-to-everything applications.

In some embodiments, the priority corresponds to an application radio access type of the plurality of radio access types.

In various embodiments, the priority corresponds to an application carrier frequency.

In one embodiment, the priority corresponds to an application radio access type of the plurality of radio access types and an application carrier frequency.

In certain embodiments, the priority corresponds to an application radio access type of the plurality of radio access types and a plurality of application carrier frequencies.

In some embodiments, the plurality of radio access types comprises evolved universal terrestrial radio access and new radio.

In one embodiment, an apparatus comprises: a processor that: supports transmission of vehicle-to-everything messages over a first plurality of network connections for communication with a mobile communication network over a plurality radio access types and a second plurality of network connections for direct vehicle-to-everything communication with other remote units over a plurality of radio access types; supports a first plurality of vehicle-to-everything applications, wherein each vehicle-to-everything application of the first plurality of vehicle-to-everything applications uses the vehicle-to-everything messages transmitted via direct vehicle-to-everything communication over a radio access type of the plurality of radio access types and over a corresponding carrier frequency; and supports a second plurality of vehicle-to-everything applications, wherein each vehicle-to-everything application of the second plurality of vehicle-to-everything applications uses the vehicle-to-everything messages transmitted via the mobile communication network; and a receiver that receives a request from a vehicle-to-everything application of the first plurality of vehicle-to-everything applications or the second plurality of vehicle-to-everything applications to transmit a message via the direct vehicle-to-everything communication or via the mobile communication network; wherein the processor determines a transmission radio access type and a transmission carrier frequency for transmitting the message over direct vehicle-to-everything communication.

In certain embodiments, the processor: selects vehicle-to-everything applications of the first plurality of vehicle-to-everything applications or the second plurality of vehicle-to-everything applications that use direct vehicle-to-everything communication or the mobile communication network via a cell based on a priority and a preemption configuration; and selects the cell that supports the selected vehicle-to-everything applications.

In various embodiments, the processor determining the transmission radio access type and the transmission carrier frequency for transmitting the vehicle-to-everything message comprises the processor identifying the transmission radio access type and the transmission carrier frequency based on a highest priority vehicle-to-everything application of the second plurality of vehicle-to-everything applications that includes a preferred radio access type of the plurality of radio access types.

Claim 1:
A method performed by a user equipment, UE, (<NUM>), the method comprising:
supporting (<NUM>) transmission of vehicle-to-everything, V2X, messages over a first plurality of network connections for communication with a mobile communication network over a plurality of radio access types and a second plurality of network connections for direct V2X communication with other UEs over a plurality of radio access types;
supporting (<NUM>) a first plurality of V2X applications, wherein each V2X application of the first plurality of V2X applications uses the V2X messages transmitted via direct V2X communication over a radio access type of the plurality of radio access types and over a corresponding carrier frequency;
supporting (<NUM>) a second plurality of V2X applications, wherein each V2X application of the second plurality of V2X applications uses the V2X messages transmitted via the mobile communication network;
receiving (<NUM>) a request from a specific V2X application of the first plurality of V2X applications to transmit a message via the direct V2X communication or from a specific V2X application of the second plurality of V2X applications to transmit a message via the mobile communication network;
selecting, based on a priority and a preemption configuration, V2X applications of the first plurality of V2X applications or the second plurality of V2X applications to support; and
selecting a cell that supports the selected V2X applications for transmission of the requested message.