WO2020069287A1

WO2020069287A1 - Radio access technology (rat) selection for nr v2x

Info

Publication number: WO2020069287A1
Application number: PCT/US2019/053412
Authority: WO
Inventors: Ansab ALI; Keyongin JEONG; Sangeetha L. Bangolae; Youn Hyoung Heo
Original assignee: Intel Corp
Current assignee: Intel Corp
Priority date: 2018-09-27
Filing date: 2019-09-27
Publication date: 2020-04-02
Anticipated expiration: 2021-03-27
Also published as: CN112997512B; CN112997512A

Abstract

An apparatus of a next generation NodeB (gNB) comprises one or more baseband processors to decode a transmission profile (Tx) message including bits that define a mapping of a transmission (Tx) profile to a corresponding vehicle-to-everything (V2X) service, and to select a Long Term Evolution (LTE) radio access technology (RAT) or a New Radio (NR) RAT to deliver a packet to a user equipment (UE) using V2X services based on the mapping. The gNB can include a memory to store the mapping.

Description

RADIO ACCESS TECHNOLOGY (RAT) SELECTION FOR NR V2X

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] The present application claims the benefit of US Provisional

Application No. 62/737,501 (AB5637-Z) filed Sep. 27, 2018. Said Application No. 62/737,501 is hereby incorporated herein by reference in its entirety.

BACKGROUND

[0002] As the use of both new radio (NR) and Long Term Evolution (LTE) becomes prevalent and widespread and new use cases of advanced vehicle-to-vehicle communication are identified, techniques for choosing between different Radio Access Technologies (RATs) for vehicle-to-everything (V2X) transmission can be contemplated. To this end, solutions for choosing the appropriate RAT considering variety of input factors and develop mechanisms to incorporate such factors to allow for flexible and efficient sidelink operation can be considered.

[0003] With the evolution of NR and its applicability to different modes of communication such as V2X, a unique scenario arises because of the presence of multiple connectivity technologies and standards. For instance, at the current point of time, the use of Long Term Evolution (LTE) is widespread throughout the world, and the LTE standard continues to evolve. At the same time, Fifth Generation (5G) based standards such as NR are beginning to be deployed as they mature. So, it is very feasible that network devices and user equipment (UE) devices which can connect to and utilize both LTE and NR based will be introduced into the market. What is more, such devices would continue to exist for an extended period of time as the rollout of NR to replace LTE completely is not an overnight process. So, to harness the full benefit of reliable and extended connectivity offered by legacy (LTE) standards as well as the technological edge offered by 5G standards, devices which can utilize multiple Radio Access Technologies (RATs) are going to be deployed in abundance.

[0004] This gives rise to an interesting question where the decision to choose a particular RAT for transmission becomes very important. For the case of vehicular communication, this is especially critical since for road safety applications, the differences in features offered by different RATs go a long way in determining which RAT should be chosen. In addition, with more advanced use cases being developed for V2X applications, this gives rise to a wide variety of technical requirements which need to be met by the selected RAT. A typical vehicular UE (V-UE) is also expected to be much more mobile than a non V-UE and thus this choice needs to be made more frequently.

DESCRIPTION OF THE DRAWING FIGURES

[0005] Claimed subject matter is particularly pointed out and distinctly claimed in the concluding portion of the specification. However, such subject matter may be understood by reference to the following detailed description when read with the accompanying drawings in which:

[0006] FIG. 1 is a diagram of radio access technology (RAT) selection for new radio (NR) vehicle-to-everything (V2X) in accordance with one or more embodiments.

[0007] FIG. 2 illustrates an architecture of a system of a network in accordance with some embodiments.

[0008] FIG. 3 illustrates example components of a device in accordance with some embodiments.

[0009] FIG. 4 illustrates example interfaces of baseband circuitry in accordance with some embodiments.

[00010] It will be appreciated that for simplicity and/or clarity of illustration, elements illustrated in the figures have not necessarily been drawn to scale. For example, the dimensions of some of the elements may be exaggerated relative to other elements for clarity. Further, if considered appropriate, reference numerals have been repeated among the figures to indicate corresponding and/or analogous elements.

DETAILED DESCRIPTION

[00011] In the following detailed description, numerous specific details are set forth to provide a thorough understanding of claimed subject matter. It will, however, be understood by those skilled in the art that claimed subject matter may be practiced without these specific details. In other instances, well-known methods, procedures, components and/or circuits have not been described in detail.

[00012] In the following description and/or claims, the terms coupled and/or connected, along with their derivatives, may be used. In particular embodiments, connected may be used to indicate that two or more elements are in direct physical and/or electrical contact with each other. Coupled may mean that two or more elements are in direct physical and/or electrical contact. However, coupled may also mean that two or more elements may not be in direct contact with each other, but yet may still cooperate and/or interact with each other. For example, "coupled" may mean that two or more elements do not contact each other but are indirectly joined together via another element or intermediate elements. Finally, the terms "on," "overlying," and "over" may be used in the following description and claims. "On," "overlying," and "over" may be used to indicate that two or more elements are in direct physical contact with each other. It should be noted, however, that "over" may also mean that two or more elements are not in direct contact with each other. For example, "over" may mean that one element is above another element but not contact each other and may have another element or elements in between the two elements. Furthermore, the term“and/or” may mean“and”, it may mean“or”, it may mean “exclusive-or”, it may mean“one”, it may mean“some, but not all”, it may mean “neither”, and/or it may mean“both”, although the scope of claimed subject matter is not limited in this respect. In the following description and/or claims, the terms "comprise" and "include," along with their derivatives, may be used and are intended as synonyms for each other.

[00013] Referring now to FIG. 1, a diagram of radio access technology (RAT) selection for new radio (NR) vehicle-to-everything (V2X) in accordance with one or more embodiments will be discussed. As shown in the arrangement 100 of FIG. 1, a first user equipment (UE 1) 110 can communicate with the accesses stratum (AS) layer 126 using a Long Term Evolution (LTE) RAT 114 or using an NR RAT 116 to connect with a 5G core (5GC) 118. A V2X application can run on a V2X server 120 at the V2X/upper layers 128. When connected to LTE RAT 114, the first UE (UE 1) 110 can connect with a second UE (UE 2) 112 over an LTE V2X sidelink interface 122. When connected to 5G RAT 116, the first UE 110 can connect with the second UE 112 over an NR V2X sidelink interface 124. As discussed herein, the relevant factors that can determine the selection of an appropriate Third Generation Partnership Project (3 GPP) RAT, what role each network (NW) layer plays in this decision and how such selection is actually performed by the vehicular user equipment (V-UE). It should be noted that although Long Term Evolution (LTE) and New Radio (NR) RATs are provided as examples herein, many of the principles also can be applicable to non-3GPP technologies, and the scope of the claimed subject matter is not limited in this respect.

[00014] In one or more embodiments, there are a number of different factors that come into play when considering the choice of RAT for sidelink transmission. These factors can range from V2X application type, for example road safety versus non safety related requirements including Quality of Service (QoS) parameters, expected range of communication and V2X application preference, RAT coverage and availability, operator policy, expected UE capabilities in the immediate vicinity, and so on. Such factors and the role the factors play are discussed, below.

[00015] In some example, V2X application type can be an important factor to consider. In 3GPP, V2X applications are broadly divided into two broad categories: road safety related applications, for example autonomous driving or platooning, and non-safety related applications, for example infotainment. Additionally, the applications can be split in terms of distinct use cases, each with an associated set of technical requirements. It is these sets of QoS and expected range requirements that can directly determine the decision by the V2X layer to choose a particular RAT. For instance, for a vehicle involved in a platoon, the reliability requirement is much higher than a vehicle only interested in acquiring sensor data such as for a digital map update. At the same time, the data rate requirements for the above two can be different as well. This complex mixture of varying requirements means that the choice of one RAT versus another is not always straight-forward. To this end, in one embodiment the RAT selection decision can be left to the V2X upper layer, at least when considering the above factors. In this way, the lower, access stratum (AS) layers at the UE are not concerned with the requirements needed by a particular application, especially if the chosen RAT is not expected to change across shorter time scale. In addition, the V2X application might have a preference for a specific RAT to be chosen even when the QoS requirements dictate otherwise, for example public safety related applications. In any case, the V2X layer can have autonomy to choose and indicate the relevant RAT to the lower layer for V2X transmission.

[00016] In another embodiment, in addition to the V2X service and/or application, another facet of RAT selection can involve the actual RAT coverage and availability for the given UE. It is quite possible that the V2X/upper layer 128 chooses a particular RAT for V2X transmission, but the AS layer determines that the current channel conditions for transmission, for example sidelink resource usage, is such that the required QoS for the V2X application cannot be guaranteed. Assuming that the sidelink resources are shared in this case, it potentially can be detrimental to use that particular RAT for transmission since it might impact transmissions from other V-UEs in the vicinity. Therefore, identifying and indicating the current RAT resource availability to the upper layers can be implemented to assist in the decision. In addition, the UE may be in coverage of one RAT but not the other and might be able to request dedicated resources for transmission in the former RAT to better meet the QoS requirements for the V2X application.

[00017] In another embodiment, operator policy can be a factor to proper V2X operation. It is expected that the UE’s decision to choose a particular RAT for transmission is conditioned on proper provisioning and authorization by the network, which is again left up to the upper layers to determine.

[00018] In a further embodiment, the expected UE capabilities in the immediate vicinity can be a factor for RAT selection. Since V2X communication is inherently based on different V-UEs in local vicinity of each other being able to communicate effectively, the different use cases are also reliant on this behavior. For instance, in case of vehicle platooning, it is expected that a given vehicle in a platoon can not only communicate with the platoon leader and other vehicles in the platoon, but also other vehicles in the vicinity which are not part of the platoon. In order to do so, the appropriate RAT should be chosen since it cannot be ensured that all or even most of the vehicles have the capability to monitor both RATs simultaneously. Thus, the V2X/upper layer 128 can take this into account, for example by monitoring the various sidelink transmissions over a period of time, to determine which RAT should be used to form the platoon.

[00019] In yet another embodiment, the access stratum (AS) layer can have a role in RAT selection. As discussed above, the AS layer 126 is expected to be mostly agnostic when it comes to RAT selection. This is also in line with some of the behavior in legacy LTE across different releases, for example Release 14 versus Release 15, where owing to non-backward compatible transmission schemes at the physical layer, the upper layer was involved in a transmission profile mechanism selection to assist the AS layer 126 in choosing a particular transmission format. Therefore, while the reasons for doing so are somewhat different, this behavior can be generalized and extended to RAT selection as well.

[00020] It should be noted, however, that the legacy behavior simply revolved around choosing between transmission formats for the same RAT. In contrast, for 5G NR applications, the decision to choose across different RATs involves more scrutiny. Specifically, since the carrier frequencies associated to the different RATs are dissimilar, the resource pools allocated for the two RATs are expected to have different and uncorrelated resource usage. When the V2X/upper layer 128 chooses a particular RAT for transmission, it should be aware of the current resource usage on both RATs, which can for instance be indicated by constant bit rate (CBR) like metrics as defined for LTE. This issue can be addressed in different ways as discussed below.

[00021] In a first example, the V2X layer does not take the resource utilization or congestion of the RATs into account and simply indicates to the AS layer 126 to select one particular RAT. In this case, the UE would be forced to follow the indication and may either transmit anyway, leading to further congestion, or be forced to skip transmissions due to CBR restrictions in place, leading to a degradation in quality for the particular application.

[00022] In a second example, the V2X layer is informed of the resource usage of the RATs and takes those into account when making the decision. This can be done by internal UE implementation for instance by indicating the average resource usage or CBR over specific set of resources for each RAT. Since it the job of the AS layer 126 to select specific resources for transmission, however, it can be somewhat convoluted that the AS layer 126 first indicates availability of potential resources to the upper layer, which might change once the AS layer 126 actually receives the packet for transmission.

[00023] In a third example, the V2X layer can include additional information alongside the packet passed down to the AS layer 126 which can serve the purpose of assisting the AS layer 126 to determine if the channel conditions are suitable for this RAT or whether the transmission needs to switch to a different RAT or whether the transmission has to use a specific RAT. For instance, a flag can indicate if the AS layer 126 can consider the CBR or an equivalent metric for NR to determine which RAT can be chosen for transmission. This can be based on some configured or preconfigured criteria, such as a list of ProSe per packet priority-CBR (PPPP-CBR) range values which already exists in LTE specifications and which determines if the RAT is indeed suitable for transmission of this packet. An example of this is in Table 1 below, which depicts the mapping of packet priority to CBR to be used by AS layer 126. This mapping can also include a recommended RAT to be utilized for the specific QoS.

Table 1: Sample configuration for RAT selection at the AS layer

[00024] In some embodiments, a RAT selection procedure can take into account a transmission (Tx) profile. In the current LTE standard, Release 15, the concept of a Tx profile is captured as a pre-configuration parameter as follows.

SL-V2X-TxProfileList-r 15 ::= SEQUENCE (SIZE (1..256)) OF SL-V2X-

TxProfile-rl5

SL-V2X-TxProfile-r 15 ::= ENUMERATED {

rell4, rell5, spare6, spare5, spare4, spare3, spare2, spare 1, ...}

[00025] The two options of Release 14 and Release 15 indicate the transmission scheme to be used for transmission of the V2X packet. The upper layer indicates a pointer to which particular profile should be used alongside each packet. This approach can be extended to the case of indicating the RAT type to be used for transmission by utilizing the spare values. In this case, the V2X/upper layer 128 simply defines the mapping of Tx profiles to specific V2X service, based on the factors discussed above, and indicates the pointer to the identified TX profile for each packet. The preconfiguration can also include the additional information in Table 1 above to be used by the AS layer 126. Specifically, the relevant QoS for each packet mapped to the channel and/or resource usage by utilizing the table format. Then, for each packet passed to the AS layer 126, in addition to containing the relevant QoS information and the Tx profile information, also indicates whether the AS layer 126 is allowed to switch to a different RAT in case the current QoS-resource usage mapping (CBR-PPPP) does not allow the use of the current RAT for Y2X transmission.

[00026] This approach allows the maximum amount of flexibility to the V2X layer to choose if the current resource utilization for a given RAT needs to be taken into account. At the same time, the AS layer 126 is not directly involved in the decision and simply follows the mapping configured by the upper layers to choose the appropriate RAT. It should be noted that there can be different ways of accomplishing the same feature, for example by defining additional TX profile code points that indicate if AS layer 126 can switch to the other RAT if required by the mapping table. The fundamental principle still holds, for example by taking into account the resource utilization of an applicable RAT or RATs when determining the PC5 RAT for V2X transmission.

[00027] FIG. 2 illustrates an architecture of a system 200 of a network in accordance with some embodiments. The system 200 is shown to include a user equipment (UE) 201 and a UE 202. The UEs 201 and 202 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks) but may also comprise any mobile or non-mobile computing device, such as Personal Data Assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, or any computing device including a wireless communications interface.

[00028] In some embodiments, any of the UEs 201 and 202 can comprise an Internet of Things (IoT) UE, which can comprise a network access layer designed for low-power IoT applications utilizing short-lived UE connections. An IoT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity-Based Service (ProSe) or device-to- device (D2D) communication, sensor networks, or IoT networks. The M2M or MTC exchange of data may be a machine-initiated exchange of data. An IoT network describes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections. The IoT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the IoT network.

[00029] The UEs 201 and 202 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 210— the RAN 210 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN. The UEs 201 and 202 utilize connections 203 and 204, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 203 and 204 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3 GPP Long Term Evolution (LTE) protocol, a fifth generation (5G) protocol, a New Radio (NR) protocol, and the like.

[00030] In this embodiment, the UEs 201 and 202 may further directly exchange communication data via a ProSe interface 205. The ProSe interface 205 may alternatively be referred to as a sidelink interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH).

[00031] The UE 202 is shown to be configured to access an access point (AP) 206 via connection 207. The connection 207 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 206 would comprise a wireless fidelity (WiFi®) router. In this example, the AP 206 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).

[00032] The RAN 210 can include one or more access nodes that enable the connections 203 and 204. These access nodes (ANs) can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), next Generation NodeBs (gNB), RAN nodes, and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). The RAN 210 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 211, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node 212. [00033] Any of the RAN nodes 211 and 212 can terminate the air interface protocol and can be the first point of contact for the UEs 201 and 202. In some embodiments, any of the RAN nodes 211 and 212 can fulfill various logical functions for the RAN 210 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

[00034] In accordance with some embodiments, the UEs 201 and 202 can be configured to communicate using Orthogonal Frequency-Division Multiplexing (OFDM) communication signals with each other or with any of the RAN nodes 211 and 212 over a multicarrier communication channel in accordance various communication techniques, such as, but not limited to, an Orthogonal Frequency- Division Multiple Access (OFDMA) communication technique (e.g., for downlink communications) or a Single Carrier Frequency Division Multiple Access (SC- FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. The OFDM signals can comprise a plurality of orthogonal subcarriers.

[00035] In some embodiments, a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 211 and 212 to the UEs 201 and 202, while uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid, called a resource grid or time-frequency resource grid, which is the physical resource in the downlink in each slot. Such a time-frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation. Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to one slot in a radio frame. The smallest time-frequency unit in a resource grid is denoted as a resource element. Each resource grid comprises a number of resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block comprises a collection of resource elements; in the frequency domain, this may represent the smallest quantity of resources that currently can be allocated. There are several different physical downlink channels that are conveyed using such resource blocks.

[00036] The physical downlink shared channel (PDSCH) may carry user data and higher-layer signaling to the UEs 201 and 202. The physical downlink control channel (PDCCH) may carry information about the transport format and resource allocations related to the PDSCH channel, among other things. It may also inform the UEs 201 and 202 about the transport format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information related to the uplink shared channel. Typically, downlink scheduling (assigning control and shared channel resource blocks to the UE 102 within a cell) may be performed at any of the RAN nodes 211 and 212 based on channel quality information fed back from any of the UEs 201 and 202. The downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of the UEs 201 and 202.

[00037] The PDCCH may use control channel elements (CCEs) to convey the control information. Before being mapped to resource elements, the PDCCH complex-valued symbols may first be organized into quadruplets, which may then be permuted using a sub-block interleaver for rate matching. Each PDCCH may be transmitted using one or more of these CCEs, where each CCE may correspond to nine sets of four physical resource elements known as resource element groups (REGs). Four Quadrature Phase Shift Keying (QPSK) symbols may be mapped to each REG. The PDCCH can be transmitted using one or more CCEs, depending on the size of the downlink control information (DCI) and the channel condition. There can be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation level, L=l, 2, 4, or 8).

[00038] Some embodiments may use concepts for resource allocation for control channel information that are an extension of the above-described concepts. For example, some embodiments may utilize an enhanced physical downlink control channel (EPDCCH) that uses PDSCH resources for control information transmission. The EPDCCH may be transmitted using one or more enhanced the control channel elements (ECCEs). Similar to above, each ECCE may correspond to nine sets of four physical resource elements known as an enhanced resource element groups (EREGs). An ECCE may have other numbers of EREGs in some situations.

[00039] The RAN 210 is shown to be communicatively coupled to a core network (CN) 220— via an Sl interface 213. In embodiments, the CN 220 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN. In this embodiment the Sl interface 213 is split into two parts: the Sl-U interface 214, which carries traffic data between the RAN nodes 211 and 212 and the serving gateway (S-GW) 222, and the Sl -mobility management entity (MME) interface 215, which is a signaling interface between the RAN nodes 211 and 212 and MMEs 221.

[00040] In this embodiment, the CN 220 comprises the MMEs 221, the S-GW 222, the Packet Data Network (PDN) Gateway (P-GW) 223, and a home subscriber server (HSS) 224. The MMEs 221 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN). The MMEs 221 may manage mobility aspects in access such as gateway selection and tracking area list management. The HSS 224 may comprise a database for network users, including subscription-related information to support the network entities’ handling of communication sessions. The CN 220 may comprise one or several HSSs 224, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc. For example, the HSS 224 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.

[00041] The S-GW 222 may terminate the Sl interface 213 towards the RAN 210, and routes data packets between the RAN 210 and the CN 220. In addition, the S-GW 222 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3 GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.

[00042] The P-GW 223 may terminate an SGi interface toward a PDN. The P- GW 223 may route data packets between the EPC network 223 and external networks such as a network including the application server 230 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 225. Generally, the application server 230 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.). In this embodiment, the P-GW 223 is shown to be communicatively coupled to an application server 230 via an IP communications interface 225. The application server 230 can also be configured to support one or more communication services (e.g., Voice-over-Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 201 and 202 via the CN 220.

[00043] The P-GW 223 may further be a node for policy enforcement and charging data collection. Policy and Charging Enforcement Function (PCRF) 226 is the policy and charging control element of the CN 220. In a non-roaming scenario, there may be a single PCRF in the Home Public Land Mobile Network (HPLMN) associated with a UE’s Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with local breakout of traffic, there may be two PCRFs associated with a UE’s IP-CAN session: a Home PCRF (H-PCRF) within a HPLMN and a Visited PCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). The PCRF 226 may be communicatively coupled to the application server 230 via the P-GW 223. The application server 230 may signal the PCRF 226 to indicate a new service flow and select the appropriate Quality of Service (QoS) and charging parameters. The PCRF 226 may provision this rule into a Policy and Charging Enforcement Function (PCEF) (not shown) with the appropriate traffic flow template (TFT) and QoS class of identifier (QCI), which commences the QoS and charging as specified by the application server 230.

[00044] FIG. 3 illustrates example components of a device 300 in accordance with some embodiments. In some embodiments, the device 300 may include application circuitry 302, baseband circuitry 304, Radio Frequency (RF) circuitry 306, front-end module (FEM) circuitry 308, one or more antennas 310, and power management circuitry (PMC) 312 coupled together at least as shown. The components of the illustrated device 300 may be included in a UE or a RAN node. In some embodiments, the device 300 may include less elements (e.g., a RAN node may not utilize application circuitry 302, and instead include a processor/controller to process IP data received from an EPC). In some embodiments, the device 300 may include additional elements such as, for example, memory/storage, display, camera, sensor, or input/output (I/O) interface. In other embodiments, the components described below may be included in more than one device (e.g., said circuitries may be separately included in more than one device for Cloud-RAN (C-RAN) implementations) .

[00045] The application circuitry 302 may include one or more application processors. For example, the application circuitry 302 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors may be coupled with or may include memory/storage and may be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to run on the device 300. In some embodiments, processors of application circuitry 302 may process IP data packets received from an EPC.

[00046] The baseband circuitry 304 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 304 may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 306 and to generate baseband signals for a transmit signal path of the RF circuitry 306. Baseband processing circuity 304 may interface with the application circuitry 302 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 306. For example, in some embodiments, the baseband circuitry 304 may include a third generation (3G) baseband processor 304A, a fourth generation (4G) baseband processor 304B, a fifth generation (5G) baseband processor 304C, or other baseband processor(s) 304D for other existing generations, generations in development or to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.). The baseband circuitry 304 (e.g., one or more of baseband processors 304A-D) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 306. In other embodiments, some or all of the functionality of baseband processors 304A-D may be included in modules stored in the memory 304G and executed via a Central Processing Unit (CPU) 304E. The radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc. In some embodiments, modulation/demodulation circuitry of the baseband circuitry 304 may include Fast-Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality. In some embodiments, encoding/decoding circuitry of the baseband circuitry 304 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality. Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.

[00047] In some embodiments, the baseband circuitry 304 may include one or more audio digital signal processor(s) (DSP) 304F. The audio DSP(s) 304F may be include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments. Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments. In some embodiments, some or all of the constituent components of the baseband circuitry 304 and the application circuitry 302 may be implemented together such as, for example, on a system on a chip (SOC).

[00048] In some embodiments, the baseband circuitry 304 may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 304 may support communication with an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN). Embodiments in which the baseband circuitry 304 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

[00049] RF circuitry 306 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 306 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry 306 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 308 and provide baseband signals to the baseband circuitry 304. RF circuitry 306 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 304 and provide RF output signals to the FEM circuitry 308 for transmission.

[00050] In some embodiments, the receive signal path of the RF circuitry 306 may include mixer circuitry 306a, amplifier circuitry 306b and filter circuitry 306c. In some embodiments, the transmit signal path of the RF circuitry 306 may include filter circuitry 306c and mixer circuitry 306a. RF circuitry 306 may also include synthesizer circuitry 306d for synthesizing a frequency for use by the mixer circuitry 306a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 306a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 308 based on the synthesized frequency provided by synthesizer circuitry 306d. The amplifier circuitry 306b may be configured to amplify the down-converted signals and the filter circuitry 306c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals may be provided to the baseband circuitry 304 for further processing. In some embodiments, the output baseband signals may be zero- frequency baseband signals, although this is not a requirement. In some embodiments, mixer circuitry 306a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.

[00051] In some embodiments, the mixer circuitry 306a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 306d to generate RF output signals for the FEM circuitry 308. The baseband signals may be provided by the baseband circuitry 304 and may be filtered by filter circuitry 306c.

[00052] In some embodiments, the mixer circuitry 306a of the receive signal path and the mixer circuitry 306a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively. In some embodiments, the mixer circuitry 306a of the receive signal path and the mixer circuitry 306a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 306a of the receive signal path and the mixer circuitry 306a may be arranged for direct downconversion and direct upconversion, respectively. In some embodiments, the mixer circuitry 306a of the receive signal path and the mixer circuitry 306a of the transmit signal path may be configured for super-heterodyne operation.

[00053] In some embodiments, the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternate embodiments, the output baseband signals and the input baseband signals may be digital baseband signals. In these alternate embodiments, the RF circuitry 306 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 304 may include a digital baseband interface to communicate with the RF circuitry 306.

[00054] In some dual-mode embodiments, a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect. In some embodiments, the synthesizer circuitry 306d may be a fractional-N synthesizer or a fractional N/N+l synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable. For example, synthesizer circuitry 306d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

[00055] The synthesizer circuitry 306d may be configured to synthesize an output frequency for use by the mixer circuitry 306a of the RF circuitry 306 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 306d may be a fractional N/N+l synthesizer.

[00056] In some embodiments, frequency input may be provided by a voltage- controlled oscillator (VCO), although that is not a requirement. Divider control input may be provided by either the baseband circuitry 304 or the applications processor 302 depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the applications processor 302.

[00057] Synthesizer circuitry 306d of the RF circuitry 306 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator. In some embodiments, the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by either N or N+l (e.g., based on a carry out) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop. In these embodiments, the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[00058] In some embodiments, synthesizer circuitry 306d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some embodiments, the output frequency may be a LO frequency (fLO). In some embodiments, the RF circuitry 306 may include an IQ/polar converter.

[00059] FEM circuitry 308 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 310, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 306 for further processing. FEM circuitry 308 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 306 for transmission by one or more of the one or more antennas 310. ln various embodiments, the amplification through the transmit or receive signal paths may be done solely in the RF circuitry 306, solely in the FEM 308, or in both the RF circuitry 306 and the FEM 308.

[00060] ln some embodiments, the FEM circuitry 308 may include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry may include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 306). The transmit signal path of the FEM circuitry 308 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 306), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 310).

[00061] ln some embodiments, the PMC 312 may manage power provided to the baseband circuitry 304. ln particular, the PMC 312 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion. The PMC 312 may often be included when the device 300 is capable of being powered by a battery, for example, when the device is included in a UE. The PMC 312 may increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.

[00062] While F1G. 3 shows the PMC 312 coupled only with the baseband circuitry 304. However, in other embodiments, the PMC 3 12 may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry 302, RF circuitry 306, or FEM 308.

[00063] In some embodiments, the PMC 312 may control, or otherwise be part of, various power saving mechanisms of the device 300. For example, if the device 300 is in an RRC Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device 300 may power down for brief intervals of time and thus save power.

[00064] If there is no data traffic activity for an extended period of time, then the device 300 may transition off to an RRC_Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The device 300 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again. The device 300 may not receive data in this state, in order to receive data, it must transition back to RRC Connected state.

[00065] An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.

[00066] Processors of the application circuitry 302 and processors of the baseband circuitry 304 may be used to execute elements of one or more instances of a protocol stack. For example, processors of the baseband circuitry 304, alone or in combination, may be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry 304 may utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers). As referred to herein, Layer 3 may comprise a radio resource control (RRC) layer, described in further detail below. As referred to herein, Layer 2 may comprise a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, described in further detail below. As referred to herein, Layer 1 may comprise a physical (PHY) layer of a UE/RAN node, described in further detail below.

[00067] FIG. 4 illustrates example interfaces of baseband circuitry in accordance with some embodiments. As discussed above, the baseband circuitry 304 of FIG. 3 may comprise processors 304A-304E and a memory 304G utilized by said processors. Each of the processors 304A-304E may include a memory interface, 404A-404E, respectively, to send/receive data to/from the memory 304G.

[00068] The baseband circuitry 304 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface 412 (e.g., an interface to send/receive data to/from memory external to the baseband circuitry 304), an application circuitry interface 414 (e.g., an interface to send/receive data to/from the application circuitry 302 of FIG. 3), an RF circuitry interface 416 (e.g., an interface to send/receive data to/from RF circuitry 306 of FIG. 3), a wireless hardware connectivity interface 418 (e.g., an interface to send/receive data to/from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components), and a power management interface 420 (e.g., an interface to send/receive power or control signals to/from the PMC 312.

[00069] The following are example implementations of the subject matter described herein. In example one, an apparatus of a next generation NodeB (gNB) comprises one or more baseband processors to decode a transmission profile (Tx) message including bits that define a mapping of a transmission (Tx) profile to a corresponding vehicle-to-everything (V2X) service, and to select a Long Term Evolution (LTE) radio access technology (RAT) or a New Radio (NR) RAT to deliver a packet to a user equipment (UE) using V2X services based on the mapping, and a memory to store the mapping. In example two, the one or more baseband processors are to also select a suitable RAT based on a V2X application type for a V2X application providing the V2X services. In example three, the one or more baseband processors are to also select a suitable RAT based on RAT coverage and availability. In example four, the one or more baseband processors are to also select a suitable RAT based on operator policy, wherein the operator policy indicates if a particular UE can use a given RAT. In example five, the one or more baseband processors are to also select a suitable RAT based on a capability and interest of the UE and one or more additional UEs in the vicinity of the UE. In example six, the one or more baseband processors are to receive an indication from a V2X application indicating a suitable RAT based on a quality of service (QoS) requirement of the V2X application. In example seven, the one or more baseband processors are to select a suitable RAT based on an indication from a V2X layer. In example eight, the one or more baseband processors are to indicate a suitable RAT to a V2X layer before a V2X transmission. In example nine, the one or more baseband processors are to process information in conjunction with a V2X packet that indicates a suitable RAT. In example ten, the one or more baseband processors are to configure a mapping to select a given RAT for transmission based on channel or resource utilization over the given RAT. [00070] In example eleven, one or more machine readable media have instructions store thereon that, when executed by an apparatus of a next generation NodeB (gNB), result in decoding a transmission profile (Tx) message including bits that define a mapping of a transmission (Tx) profile to a corresponding vehicle-to- everything (V2X) service, and selecting a Long Term Evolution (LTE) radio access technology (RAT) or a New Radio (NR) RAT to deliver a packet to a user equipment (UE) using V2X services based on the mapping. In example twelve, the instructions, when executed, further result in selecting a suitable RAT based on a V2X application type for a V2X application providing the V2X services. In example thirteen, the instructions, when executed, further result in also selecting a suitable RAT based on RAT coverage and availability. In example fourteen, the instructions, when executed, further result in also selecting a suitable RAT based on operator policy, wherein the operator policy indicates if a particular UE can use a given RAT. In example fifteen, the instructions, when executed, further result in also selecting a suitable RAT based on a capability and interest of the UE and one or more additional UEs in the vicinity of the UE. In example sixteen, the instructions, when executed, further result in receiving an indication from a V2X application indicating a suitable RAT based on a quality of service (QoS) requirement of the V2X application. In example seventeen, the instructions, when executed, further result in selecting a suitable RAT based on an indication from a V2X layer. In example eighteen, the instructions, when executed, further result in indicating a suitable RAT to a V2X layer before a V2X transmission. In example nineteen, the instructions, when executed, further result in processing information in conjunction with a V2X packet that indicates a suitable RAT. In example twenty, the instructions, when executed, further result in configuring a mapping to select a given RAT for transmission based on channel or resource utilization over the given RAT.

[00071] Although the claimed subject matter has been described with a certain degree of particularity, it should be recognized that elements thereof may be altered by persons skilled in the art without departing from the spirit and/or scope of claimed subject matter. It is believed that the subject matter pertaining to radio access technology (RAT) selection for NR V2X and many of its attendant utilities will be understood by the forgoing description, and it will be apparent that various changes may be made in the form, construction and/or arrangement of the components thereof without departing from the scope and/or spirit of the claimed subject matter or without sacrificing all of its material advantages, the form herein before described being merely an explanatory embodiment thereof, and/or further without providing substantial change thereto. It is the intention of the claims to encompass and/or include such changes.

Claims

CLAIMS What is claimed is:

1. An apparatus of a next generation NodeB (gNB), comprising:

one or more baseband processors to decode a transmission profile (Tx) message including bits that define a mapping of a transmission (Tx) profile to a corresponding vehicle-to-everything (V2X) service, and to select a Long Term Evolution (LTE) radio access technology (RAT) or a New Radio (NR) RAT to deliver a packet to a user equipment (UE) using Y2X services based on the mapping; and a memory to store the mapping.

2. The apparatus of claim 1, wherein the one or more baseband processors are to also select a suitable RAT based on a V2X application type for a V2X application providing the V2X services.

3. The apparatus of any of claims 1-2, wherein the one or more baseband processors are to also select a suitable RAT based on RAT coverage and availability.

4. The apparatus of any of claims 1-3, wherein the one or more baseband processors are to also select a suitable RAT based on operator policy, wherein the operator policy indicates if a particular UE can use a given RAT.

5. The apparatus of any of claims 1-4, wherein the one or more baseband processors are to also select a suitable RAT based on a capability and interest of the UE and one or more additional UEs in the vicinity of the UE.

6. The apparatus of any of claims 1-5, wherein the one or more baseband processors are to receive an indication from a V2X application indicating a suitable RAT based on a quality of service (QoS) requirement of the V2X application.

7. The apparatus of claim 3, wherein the one or more baseband processors are to select a suitable RAT based on an indication from a V2X layer.

8. The apparatus of claim 3, wherein the one or more baseband processors are to indicate a suitable RAT to a V2X layer before a Y2X transmission.

9. The apparatus of claim 3, wherein the one or more baseband processors are to process information in conjunction with a V2X packet that indicates a suitable RAT.

10. The apparatus of claim 9, wherein the one or more baseband processors are to configure a mapping to select a given RAT for transmission based on channel or resource utilization over the given RAT.

11. One or more machine readable media having instructions store thereon that, when executed by an apparatus of a next generation NodeB (gNB), result in: decoding a transmission profile (Tx) message including bits that define a mapping of a transmission (Tx) profile to a corresponding vehicle-to-everything (V2X) service; and

selecting a Long Term Evolution (LTE) radio access technology (RAT) or a New Radio (NR) RAT to deliver a packet to a user equipment (UE) using V2X services based on the mapping.

12. The one or more machine readable media of claim 11, wherein the instructions, when executed, further result in selecting a suitable RAT based on a V2X application type for a V2X application providing the V2X services.

13. The one or more machine readable media of any of claims 11-12 wherein the instructions, when executed, further result in also selecting a suitable RAT based on RAT coverage and availability.

14. The one or more machine readable media of any of claims 11-13, wherein the instructions, when executed, further result in also selecting a suitable RAT based on operator policy, wherein the operator policy indicates if a particular UE can use a given RAT.

15. The one or more machine readable media of any of claims 11-14, wherein the instructions, when executed, further result in also selecting a suitable RAT based on a capability and interest of the UE and one or more additional UEs in the vicinity of the UE.

16. The one or more machine readable media of any of claims 11-15, wherein the instructions, when executed, further result in receiving an indication from a V2X application indicating a suitable RAT based on a quality of service (QoS) requirement of the V2X application.

17. The one or more machine readable media of claim 13, wherein the instructions, when executed, further result in selecting a suitable RAT based on an indication from a Y2X layer.

18. The one or more machine readable media of claim 13, wherein the instructions, when executed, further result in indicating a suitable RAT to a V2X layer before a V2X transmission.

19. The one or more machine readable media of claim 13, wherein the instructions, when executed, further result in processing information in conjunction with a V2X packet that indicates a suitable RAT.

20. The one or more machine readable media of claim 19, wherein the instructions, when executed, further result in configuring a mapping to select a given RAT for transmission based on channel or resource utilization over the given RAT.