Negotiation of a PC5 rat for a V2X service

Embodiments of a User Equipment (UE) and methods of communication are generally described herein. The UE may be configurable to operate as an initiating UE for a vehicle-to-everything (V2X) application that includes PCS communication between the initiating UE and a receiving UE. The initiating UE may receive, from a base station, control signaling that indicates a default PCS radio access technology (RAT) for the V2X service. The default PCS RAT may be either a Long Term Evolution (LTE) PCS RAT or a New Radio (NR) PCS RAT. Based on the default PCS RAT and/or PCS RATs supported by the initiating UE, the initiating UE may select either the LTE PCS RAT or the NR PCS RAT. The selected PCS RAT may be proposed, in a negotiation with the receiving UE, for the V2X service.

TECHNICAL FIELD

BACKGROUND

Efficient use of the resources of a wireless network is important to provide bandwidth and acceptable response times to the users of the wireless network. However, often there are many devices trying to share the same resources and some devices may be limited by the communication protocol they use or by their hardware bandwidth. Moreover, wireless devices may need to operate with both newer protocols and with legacy device protocols.

DETAILED DESCRIPTION

FIG.1Ais a functional diagram of an example network in accordance with some embodiments.FIG.1Bis a functional diagram of another example network in accordance with some embodiments. In references herein, “FIG.1” may includeFIG.1AandFIG.1B. In some embodiments, the network100may be a Third Generation Partnership Project (3GPP) network. In some embodiments, the network150may be a 3GPP network, a new radio (NR) network and/or Fifth Generation (5G) network. Other networks may be used in some embodiments. In some embodiments, a network may include one or more of: one or more components shown inFIG.1A; one or more components shown inFIG.1B; and one or more additional components. Some embodiments may not necessarily include all components shown inFIG.1AandFIG.1B.

The network100may comprise a radio access network (RAN)101and the core network120(e.g., shown as an evolved packet core (EPC)) coupled together through an S1 interface115. For convenience and brevity sake, only a portion of the core network120, as well as the RAN101, is shown. In some embodiments, the RAN101may include one or more of: one or more components of an evolved universal terrestrial radio access network (E-UTRAN), one or more components of an NR network, and/or one or more other components.

The core network120may include a mobility management entity (MME)122, a serving gateway (serving GW)124, and packet data network gateway (PDN GW)126. In some embodiments, the networks100,150may include (and/or support) one or more Evolved Node-B's (eNBs)104and/or one or more Next Generation Node-B's (gNBs)105. The eNBs104and/or gNBs105may operate as base stations for communicating with User Equipment (UE)102. In some embodiments, one or more eNBs104may be configured to operate as gNBs105. Embodiments are not limited to the number of eNBs104shown inFIG.1Aor to the number of gNBs105shown inFIG.1B. Embodiments are also not limited to the connectivity of components shown inFIG.1A.

In some embodiments, one or more UEs102may communicate with each other. In some embodiments, such communication may be based on one or more of: PC5, vehicle-to-vehicle (V2V), vehicle-to-everything (V2X), sidelink, device-to-device (D2D) and/or other.

It should be noted that references herein to an eNB104or to a gNB105are not limiting. In some embodiments, one or more operations, methods and/or techniques (such as those described herein) may be practiced by a base station component (and/or other component), including but not limited to a gNB105, an eNB104, a serving cell, a transmit receive point (TRP) and/or other. In some embodiments, the base station component may be configured to operate in accordance with one or more of: a 3GPP LTE protocol/standard, an NR protocol/standard, a Fifth Generation (5G) protocol/standard; and/or other protocol/standard, although the scope of embodiments is not limited in this respect.

Descriptions herein of one or more operations, techniques and/or methods practiced by a component (such as the UE102, eNB104, gNB105and/or other) are not limiting. In some embodiments, one or more of those operations, techniques and/or methods may be practiced by another component.

The MME122manages mobility aspects in access such as gateway selection and tracking area list management. The serving GW124terminates the interface toward the RAN101, and routes data packets between the RAN101and the core network120. In addition, it may be a local mobility anchor point for inter-eNB handovers and also may provide an anchor for inter-3GPP mobility. The serving GW124and the MME122may be implemented in one physical node or separate physical nodes.

In some embodiments, UEs102, the eNB104and/or gNB105may be configured to communicate Orthogonal Frequency Division Multiplexing (OFDM) communication signals over a multicarrier communication channel in accordance with an Orthogonal Frequency Division Multiple Access (OFDMA) communication technique.

In some embodiments, the network150may include one or more components configured to operate in accordance with one or more 3GPP standards, including but not limited to an NR standard. The network150shown inFIG.1Bmay include a next generation RAN (NG-RAN)155, which may include one or more gNBs105. In some embodiments, the network150may include the E-UTRAN160, which may include one or more eNBs. The E-UTRAN160may be similar to the RAN101described herein, although the scope of embodiments is not limited in this respect.

In some embodiments, the network150may include the MME165, which may be similar to the MME122described herein, although the scope of embodiments is not limited in this respect. In some embodiments, the network150may include the SGW170, which may be similar to the SGW124described herein, although the scope of embodiments is not limited in this respect.

Embodiments are not limited to the number or type of components shown inFIG.1B. Embodiments are also not limited to the connectivity of components shown inFIG.1B.

FIG.2illustrates a block diagram of an example machine in accordance with some embodiments. The machine200is an example machine upon which any one or more of the techniques and/or methodologies discussed herein may be performed. In alternative embodiments, the machine200may operate as a standalone device or may be connected (e.g., networked) to other machines. The machine200may be a UE102, eNB104, gNB105, access point (AP), station (STA), user, device, mobile device, base station, another device, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while only a single machine is illustrated, the term “machine” shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein, such as cloud computing, software as a service (SaaS), other computer cluster configurations.

Examples as described herein, may include, or may operate on, logic or a number of components, modules, or mechanisms.

The machine (e.g., computer system)200may include a hardware processor202(e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory204and a static memory206, some or all of which may communicate with each other via an interlink (e.g., bus)208. The machine200may further include one or more of210-228.

The storage device216may include a machine readable medium222on which is stored one or more sets of data structures or instructions224(e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions224may also reside, completely or at least partially, within the main memory204, within static memory206, or within the hardware processor202during execution thereof by the machine200. In an example, one or any combination of the hardware processor202, the main memory204, the static memory206, or the storage device216may constitute machine readable media. In some embodiments, the machine readable medium may be or may include a non-transitory computer-readable storage medium. In some embodiments, the machine readable medium may be or may include a computer-readable storage medium.

The instructions224may further be transmitted or received over a communications network226using a transmission medium via the network interface device220utilizing any one of a number of transfer protocols. In an example, the network interface device220may include a plurality of antennas to wirelessly communicate using at least one of single-input multiple-output (SIMO), multiple-input multiple-output (MIMO), or multiple-input single-output (MISO) techniques. In some examples, the network interface device220may wirelessly communicate using Multiple User MIMO techniques. The term “transmission medium” shall be taken to include any intangible medium that is capable of storing, encoding or carrying instructions for execution by the machine200, and includes digital or analog communications signals or other intangible medium to facilitate communication of such software.

FIG.3illustrates an exemplary communication circuitry according to some aspects. It should be noted that a device, such as a UE102, eNB104, gNB105, the machine200and/or other device may include one or more components of the communication circuitry300, in some aspects. The communication circuitry300may include protocol processing circuitry305, which may implement one or more of: medium access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), radio resource control (RRC) and non-access stratum (NAS) functions. The communication circuitry300may further include digital baseband circuitry310, which may implement one or more physical layer (PHY) functions. The communication circuitry300may further include transmit circuitry315, receive circuitry320and/or antenna array circuitry330. The communication circuitry300may further include radio frequency (RF) circuitry325. In an aspect of the disclosure, RF circuitry325may include multiple parallel RF chains for one or more of transmit or receive functions, each connected to one or more antennas of the antenna array330.

In some embodiments, processing circuitry may perform one or more operations described herein and/or other operation(s). In a non-limiting example, the processing circuitry may include one or more components such as the processor202, protocol processing circuitry305, digital baseband circuitry310, similar component(s) and/or other component(s).

In some embodiments, a transceiver may transmit one or more elements (including but not limited to those described herein) and/or receive one or more elements (including but not limited to those described herein). In a non-limiting example, the transceiver may include one or more components such as transmit circuitry315, receive circuitry320, radio frequency circuitry325, similar component(s) and/or other component(s).

Although the UE102, eNB104, gNB105, machine200and/or other device described herein may each be illustrated as having several separate functional elements, one or more of the functional elements may be combined and may be implemented by combinations of software-configured elements, such as processing elements including digital signal processors (DSPs), one or more microprocessors, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), radio-frequency integrated circuits (RFICs) and combinations of various hardware and logic circuitry for performing at least the functions described herein. In some embodiments, the functional elements may refer to one or more processes operating on one or more processing elements.

It should be noted that in some embodiments, an apparatus of the UE102, eNB104, gNB105, machine200, and/or other device may include various components shown inFIGS.2-3and/or other components. Accordingly, techniques and operations described herein that are performed by a device may be performed by an apparatus of the device, in some embodiments.

In accordance with some embodiments, the UE102may be configurable to operate as an initiating UE102for a vehicle-to-everything (V2X) application that includes PC5 communication between the initiating UE102and a receiving UE102. The initiating UE102may receive, from a base station, control signaling that indicates a default PC5 radio access technology (RAT) for the V2X service. The default PC5 RAT may be either a Long Term Evolution (LTE) PC5 RAT or a New Radio (NR) PC5 RAT. The initiating UE102may select either the LTE PC5 RAT or the NR PC5 RAT to be proposed, in a negotiation with the receiving UE102, for the V2X service. The initiating UE102may, if the initiating UE102supports at least the default PC5 RAT, select the default PC5 RAT. The initiating UE102may, if the initiating UE102does not support the default PC5 RAT: of the LTE PC5 RAT and the NR PC5 RAT, select the PC5 RAT that is supported by the initiating UE102; and transmit, to the receiving UE102, a PC5 Radio Access Technology (RAT) request message to initiate the V2X service. The PC5 RAT request message may indicate the selected PC5 RAT. These embodiments are described in more detail below.

FIG.4illustrates the operation of a method of communication in accordance with some embodiments. Embodiments of the method400may include additional or even fewer operations or processes in comparison to what is illustrated inFIG.4. Embodiments of the method400are not necessarily limited to the chronological order that is shown inFIG.4.

In some embodiments, a UE102may perform one or more operations of the method400, but embodiments are not limited to performance of the method400and/or operations of it by the UE102. In some embodiments, a device and/or component (including but not limited to the UE102, gNB105and/or eNB104) may perform one or more operations that may be the same as, similar to, reciprocal to and/or related to an operation of the method400.

Discussion of various operations, techniques and/or concepts regarding one method described herein (such as the method400and/or other) may be applicable to other operations described herein and/or other methods described herein. One or more of the techniques, operations and/or methods described herein may be performed by a device other than an eNB104, gNB105, and UE102, including but not limited to a Wi-Fi access point (AP), station (STA) and/or other.

In some embodiments, an apparatus of a device (including but not limited to the UE102, eNB104, gNB105and/or other) may comprise memory that is configurable to store one or more elements, and the apparatus may use them for performance of one or more operations. The apparatus may include processing circuitry, which may perform one or more operations (including but not limited to operation(s) of the method400and/or other methods described herein). The processing circuitry may include a baseband processor. The baseband circuitry and/or the processing circuitry may perform one or more operations described herein. The apparatus may include a transceiver to transmit and/or receive one or more blocks, messages and/or other elements.

Embodiments are not limited by references herein to transmission, reception and/or exchanging of elements such as frames, messages, requests, indicators, signals or other elements. In some embodiments, such an element may be generated, encoded or otherwise processed by processing circuitry for transmission by a transceiver or other component cases. In some embodiments, such an element may be received by a transceiver or other component, and may be decoded, detected or otherwise processed by processing circuitry. In some embodiments, the processing circuitry and the transceiver may be included in a same apparatus. In some embodiments, the transceiver may be separate from the apparatus that comprises the processing circuitry, in some embodiments.

One or more of the elements (such as messages, operations and/or other) described herein may be included in a 3GPP protocol, 3GPP LTE protocol, 4G protocol, 5G protocol, NR protocol and/or other protocol, but embodiments are not limited to usage of those elements. In some embodiments, other elements may be used, including other element(s) in a same standard/protocol, other element(s) in another standard/protocol and/or other. In addition, the scope of embodiments is not limited to usage of elements that are included in standards.

In some embodiments, the UE102, eNB104and/or gNB105may be arranged to operate in accordance with a 3GPP protocol, NR protocol, and/or other protocol.

In descriptions herein, references are made to performance of one or more operations of the method400(and/or other operations) by an initiating UE102or by a receiving UE102. It is understood that such references are not limiting. In some cases, such references may be used in the descriptions herein for clarity. In some embodiments, a device (including but not limited to a UE102, a UE102that operates as an initiating UE102, a UE102that operates as a receiving UE102, and/or other device) may perform one or more of the operations of the method400and/or other operations described herein. In some embodiments, a device (including but not limited to a UE102, a UE102that operates as an initiating UE102, a UE102that operates as a receiving UE102, and/or other device) may perform one or more operations that may be the same as, similar to, related to and/or reciprocal to one or more of the operations of the method400and/or other operations described herein.

In some embodiments, a UE102may be configurable to operate as an initiating UE102and may also be configurable to operate as a receiving UE102. Accordingly, the UE102may perform one or more operations from the perspective of an initiating UE102and may perform one or more operations from the perspective of a receiving UE102, in some embodiments. For instance, the UE102may initiate a first V2X service, and may transmit a first PC5 RAT request message (related to the first V2X service) to a first UE102. The UE102may also receive, for a second V2X service, a second PC5 RAT request message (related to the second V2X service) from a second UE102.

At operation405, the UE102may exchange control signaling with one or more components of a network. In some embodiments, the UE102may exchange at least a portion of the control signaling with an eNB104. In some embodiments, the UE102may exchange at least a portion of the control signaling with a gNB105. Embodiments are not limited to exchanging of the control signaling with these components (eNB104and/or gNB105), as the UE102may exchange at least a portion of the control signaling with one or more other components, in some embodiments.

At operation410, the UE102may exchange additional control signaling with another UE102. In some embodiments, operation410may be extended to multiple control messages and/or multiple UEs102. For instance, the initiating UE102may send a control message to each of multiple receiving UEs102, in some embodiments.

At operation415, the UE102may select a PC5 RAT for a V2X service. At operation420, the UE102may select a PC5 RAT to be proposed for the V2X service.

At operation425, the UE102may exchange a PC5 RAT request message. In some embodiments, the UE102may exchange the PC5 RAT request message with another UE102, although the scope of embodiments is not limited in this respect. In some embodiments, the initiating UE102may transmit a PC5 RAT request message to the receiving UE102. In some embodiments, the receiving UE102may receive a PC5 RAT request message from the initiating UE102. In some embodiments, operation425may be extended to multiple PC5 RAT request messages and/or multiple UEs102. For instance, the initiating UE102may send a PC5 RAT request message to each of multiple receiving UEs102, in some embodiments.

At operation430, the UE102may exchange a PC5 RAT response message. In some embodiments, the UE102may exchange the PC5 RAT response message with another UE102, although the scope of embodiments is not limited in this respect. In some embodiments, the initiating UE102may receive a PC5 RAT response message from the receiving UE102. In some embodiments, the receiving UE102may transmit a PC5 RAT response message to the initiating UE102. In some embodiments, operation430may be extended to multiple PC5 RAT response messages and/or multiple UEs102. For instance, the initiating UE102may receive a PC5 RAT response message from each of multiple receiving UEs102, in some embodiments.

At operation435, the UE102may exchange a PC5 RAT acknowledgement (ACK) message. In some embodiments, the UE102may exchange the PC5 RAT ACK message with another UE102, although the scope of embodiments is not limited in this respect. In some embodiments, the initiating UE102may transmit a PC5 RAT ACK message to the receiving UE102. In some embodiments, the receiving UE102may receive a PC5 RAT ACK message from the initiating UE102. In some embodiments, operation435may be extended to multiple PC5 RAT ACK messages and/or multiple UEs102. For instance, the initiating UE102may transmit a PC5 RAT ACK message to each of multiple receiving UEs102, in some embodiments.

At operation440, the UE102may exchange data message(s) as part of the V2X service. In some embodiments, the UE102may exchange the data message(s) with another UE102, although the scope of embodiments is not limited in this respect. The exchange of data message(s) may include transmission of data message(s) and/or reception of data message(s). In some embodiments, the initiating UE102may transmit data message(s) to the receiving UE102. In some embodiments, the initiating UE102may receive data message(s) from the receiving UE102. In some embodiments, the receiving UE102may transmit data message(s) to the initiating UE102. In some embodiments, the receiving UE102may receive data message(s) from the initiating UE102. In some embodiments, operation440may be extended to multiple data messages and/or multiple UEs102. For instance, the initiating UE102may transmit a data message to each of multiple receiving UEs102, in some embodiments.

Embodiments are not limited to usage of messages such as the PC5 RAT request message, PC5 RAT response message, PC5 RAT ACK message and/or other. In some embodiments, one or more other messages may be used in operations described herein (including, but not limited to, operations of the method400).

In some embodiments, the UE102may be configurable to operate as an initiating UE102for a V2X application. In some embodiments, the V2X application may include PC5 communication between the initiating UE102and one or more receiving UEs102. In some embodiments, the initiating UE102may receive, from a base station (such as the eNB104, gNB105and/or other), control signaling that indicates a default PC5 RAT for the V2X service. In some embodiments, a PC5 RAT described as part of the method400(such as the default PC5 RAT, proposed PC5 RAT, selected PC5 RAT and/or other PC5 RAT) may be either a Long Term Evolution (LTE) PC5 RAT or a New Radio (NR) PC5 RAT, although the scope of embodiments is not limited in this respect. One or more other PC5 RATs may be used, in some embodiments.

In some embodiments, the initiating UE102may select either the LTE PC5 RAT or the NR PC5 RAT to be proposed, in a negotiation with the receiving UE102, for the V2X service. In some embodiments, the initiating UE102may, if the initiating UE102supports at least the default PC5 RAT, select the default PC5 RAT. In some embodiments, the initiating UE102may, if the initiating UE102does not support the default PC5 RAT, perform one or more of: select (from the LTE PC5 RAT and the NR PC5 RAT) the PC5 RAT that is supported by the initiating UE102; transmit, to the receiving UE102, a PC5 RAT request message to initiate the V2X service; and/or other. In some embodiments, the PC5 RAT request message may indicate the selected PC5 RAT and/or other information.

In some embodiments, the initiating UE102may receive, from the receiving UE102, a PC5 RAT response message that indicates which PC5 RAT, of the LTE PC5 RAT and the NR PC5 RAT, was selected by the receiving UE102for the V2X service. In some embodiments, the initiating UE102may transmit, to the receiving UE102, a PC5 RAT acknowledgement (ACK) message to indicate reception of the PC5 RAT response message.

In some embodiments, the initiating UE102may transmit, to the receiving UE102, a data message for the V2X service. In some embodiments, the initiating UE102may encode the data message in accordance with the PC5 RAT indicated in the PC5 RAT response message.

In some embodiments, the initiating UE102may, if the initiating UE102supports the PC5 RAT indicated in the PC5 RAT response message: use the PC5 RAT indicated in the PC5 RAT response message as the PC5 RAT for the V2X service. In some embodiments, the initiating UE102may, if the initiating UE102does not support the PC5 RAT indicated in the PC5 RAT response message: transmit additional control signaling to the receiving UE102to indicate that the initiating UE102does not support the PC5 RAT indicated in the PC5 RAT response message.

In some embodiments, the initiating UE102may use the PC5 RAT indicated in the PC5 RAT response message for the V2X service. In some embodiments, the initiating UE102may, if a second receiving UE102is to be included in the V2X service after the V2X service is initiated, and if the second receiving UE102does not support the PC5 RAT indicated in the PC5 RAT response message: transmit additional control signaling to re-negotiate the PC5 RAT to be used for the V2X service.

In some embodiments, the initiating UE102may encode the PC5 RAT request message to indicate one or more of: whether the initiating UE102supports the LTE PC5 RAT; whether the initiating UE102supports the NR PC5 RAT; and/or other information/parameters.

In some embodiments, the control signaling from the base station may include one or more parameters related to PC5 Transmit (TX) profiles for V2X services.

In some embodiments, the initiating UE102may encode the PC5 RAT request message to include an identifier of the V2X service. In some embodiments, the identifier may be an intelligent transport systems application identifier (ITS-AID), a provider service identifier (PSID) and/or other.

In some embodiments, the control signaling that indicates the default PC5 RAT for the V2X service may be received from: an eNB104of a Third Generation Partnership Project (3GPP) LTE network, a gNB105of an NR network, and/or other. Accordingly, the base station from which the control signaling is received may be an eNB104of a 3GPP LTE network, a gNB105of an NR network, and/or other, in some embodiments.

In some embodiments, the control signaling received from the base station may include the default PC5 RAT to enable a phased deployment of LTE PC5 communication and NR PC5 communication, wherein the default PC5 RAT is the LTE PC5 RAT during a first phase, wherein the default PC5 RAT is the NR PC5 RAT during a second phase that follows the first phase. For instance, a phased deployment may be used, wherein the default PC5 RAT is the LTE PC5 RAT during a first phase, wherein the default PC5 RAT is the NR PC5 RAT during a second phase that follows the first phase.

In some embodiments, the initiating UE102may receive, from a base station, control signaling that indicates a default PC5 RAT for the V2X service. In some embodiments, the default PC5 RAT may be either an LTE PC5 RAT or an NR PC5 RAT, although the scope of embodiments is not limited in this respect. In some embodiments, the initiating UE102may transmit, to the receiving UE102, first signaling that requests information related to PC5 RATs supported by the receiving UE102. In some embodiments, the initiating UE102may receive, from the receiving UE102, second signaling that indicates one or more PC5 RATs supported by the receiving UE102. In some embodiments, the initiating UE102may select either the LTE PC5 RAT or the NR PC5 RAT to be proposed, in a negotiation with the receiving UE102, for usage in the V2X service. In some embodiments, the selection may be based on one or more of: the default PC5 RAT, one or more PC5 RATs supported by the initiating UE102, the one or more PC5 RATs supported by the receiving UE102, and/or other.

In some embodiments, the initiating UE102may, if the initiating UE102and the receiving UE102support the default PC5 RAT, select the default PC5 RAT. In some embodiments, the initiating UE102may, if the initiating UE102does not support the default PC5 RAT or if the receiving UE102does not support the default PC5 RAT, and if one of the PC5 RATs (of the LTE PC5 RAT and the NR PC5 RAT) is supported by both the initiating UE102and the receiving UE102: select the PC5 RAT supported by both the initiating UE102and the receiving UE102. In some embodiments, the initiating UE102may transmit, to the receiving UE102as part of the negotiation, a PC5 RAT request message that proposes the selected PC5 RAT for usage in the V2X service. In some embodiments, the initiating UE102may receive, from the receiving UE102, a PC5 RAT response message that indicates whether the receiving UE102accepts the proposed PC5 RAT for usage in the V2X service. It is noted that transmission/reception of messages (such as the PC5 RAT request message, PC5 RAT response message, PC5 RAT ACK message and/or other) may be part of a negotiation in some embodiments, although the scope of embodiments is not limited in this respect.

In some embodiments, the UE102may be configurable to operate as a receiving UE102for a V2X application. In some embodiments, the V2X application may include PC5 communication between the receiving UE102and an initiating UE102. In some embodiments, the receiving UE102may receive, from the initiating UE102, control signaling that indicates one or more of: A) a proposed PC5 RAT for the V2X service, and B) one or more PC5 RATs supported by the initiating UE102; and/or other. In some embodiments, a PC5 RAT (such as the proposed PC5 RAT and/or supported PC5 RATs) may be either the LTE PC5 RAT or the NR PC5 RAT, although the scope of embodiments is not limited in this respect. In some embodiments, the receiving UE102may select either the LTE PC5 RAT or the NR PC5 RAT for the V2X service. In some embodiments, the receiving UE102may, if the receiving UE102supports the proposed PC5 RAT, select the proposed PC5 RAT. In some embodiments, the receiving UE102may, if the receiving UE102does not support the proposed PC5 RAT, and if at least one of the PC5 RATs (of the LTE PC5 RAT and the NR PC5 RAT) is supported by both the initiating UE102and the receiving UE102: select the PC5 RAT that is supported by both the initiating UE102and the receiving UE102.

In some embodiments, the receiving UE102may transmit, to the initiating UE102, a PC5 RAT response message that indicates the PC5 RAT selected by the receiving UE102for the V2X service.

In some embodiments, the receiving UE102may transmit, to the initiating UE102, a data message for the V2X service. In some embodiments, the receiving UE102may encode the data message in accordance with the PC5 RAT selected by the receiving UE102.

In some embodiments, the receiving UE102may, if the receiving UE102does not support the proposed PC5 RAT, and if the receiving UE102does not support any of the PC5 RATs supported by the initiating UE102: refrain from selection of the PC5 RAT for the V2X service; transmit, to the initiating UE102, a PC5 RAT response message that indicates that the receiving UE102did not select the PC5 RAT for the V2X service; and/or other.

It should be noted that descriptions herein may refer to sidelink communication, V2V communication, V2X communication, but the scope of embodiments is not limited in this respect. For instance, descriptions herein may refer to one or more techniques, operations, and/or methods that include sidelink communication, V2V communication, and/or V2X communication. It is understood that one or more of those techniques, operations, and/or methods may include one or more of: direct communication between mobile devices, device-to-device (D2D) communication, off-network communication, communication between two devices that may not necessarily include communication with a network, and/or other communication.

FIG.5illustrates an example scenario in accordance with some embodiments.FIG.6illustrates example messages that may be exchanged in accordance with some embodiments. It should be noted that the examples shown inFIGS.5-6may illustrate some or all of the concepts and techniques described herein in some cases, but embodiments are not limited by the examples. For instance, embodiments are not limited by the name, number, type, size, ordering, arrangement of elements (such as devices, operations, messages and/or other elements) shown inFIGS.5-6. Although some of the elements shown in the examples ofFIGS.5-6may be included in a 3GPP standard, NR standard, 5G standard and/or other standard, embodiments are not limited to usage of such elements that are included in standards.

In the scenario500, the UEs102may communicate over a PC5 interface (as indicated by510). In some embodiments, such communication may be in accordance with V2V, V2X, eV2X, sidelink, D2D, and/or other, although the scope of embodiments is not limited in this respect. In addition, one or more of the UEs102may exchange control signaling with one or more components of one or more networks (indicated by505inFIG.5). One or more of the techniques, operations and/or methods described herein may be performed in accordance with the scenario500and/or similar scenario, although the scope of embodiments is not limited in this respect.

InFIG.6, the UEs602,604may exchange messages (including but not limited to one or more of610,620,630). In a non-limiting example, the UE1 (indicated by602) may be an initiating UE102and the UE2 (indicated by604) may be a receiving UE102. Some embodiments may not necessarily include exchanging of all of the messages610,620,630. In some embodiments, one or more messages not shown inFIG.6may be exchanged between UE1602and UE2604.