WO2018064179A1 - V2x services in next generation cellular networks - Google Patents

Abstract

Devices and methods for vehicle-to-everything (V2X) communications are described. A V2X user equipment (V2X UE) can include processing circuitry arranged to configure a first transceiver of a plurality of transceivers to receive geo-location information from a plurality of mobile V2X communication nodes, via a first communication link in a first communication band. A sensing procedure is performed to determine a set of available candidate radio resources for transmission. A distance to the plurality of V2X communication nodes and a signal strength characteristic for each of the plurality of V2X communication nodes is determined based on the received geo-location information. A subset of V2X communication nodes is selected based on the determined distance being within a threshold distance and the determined signal strength characteristic for each of the plurality of V2X communication nodes being within a threshold signal strength.

Description

V2X SERVICES IN NEXT GENERATION CELLULAR

NETWORKS

PRIORITY CLAIM

[0001] This application claims the benefit of priority to United

States Provisional Patent Application Serial No. 62/402,518, filed

September 30, 2016, and entitled "ENABLING FUTURE V2X SERVICES IN NEXT GENERATION CELLULA NETWORKS," which provisional application is incorporated herein by reference in its entirety.

TECHNICAL FIELD

[0002] Aspects pertain to wireless communications. Some aspects relate to wireless networks including 3GPP (Third Generation Partnership Project) networks, 3 GPP LTE (Long Term Evolution) networks, 3 GPP LTE-A (LTE Advanced) networks, and fifth-generation (5G) networks including new radio (NR) networks. Other aspects are directed to enabling vehicle-to-everything (V2X) services in next generation cellular networks, such as 5G networks.

BACKGROUN D

[0003] The use of 3 GPP LTE systems (including both LTE and

LTE-A systems) has increased due to both an increase in the types of devices such as user equipments (UEs) using network resources as well as the amount of data and bandwidth being used by various applications, such as video streaming, operating on these UEs. For example, the growth of network use by Internet of Things (loT) UEs, which include machine type communication (MTC) devices such as sensors and may use machine-to- machine (M2M) communications, as well as the burgeoning V2X communications, has severely strained network resources and increased communication complexity. V2X communications of a variety of different applications from a user equipment (UE) are to coordinate with various technologies, as well as among potentially rapidly moving vehicles. [0004] Connected cars are becoming an important part of connected life of the users. With autonomous driving and loT on the horizon, V2X through the connectivity in the car, among vehicles, between vehicles and the infrastructure as well as sensors and the "things" surrounding the cars becomes more desirable. At the same time, meeting the stringent requirements of autonomous driving and seamless connectivity on the go for V2X applications as well as within the car and IoT applications remains challenging.

BRIEF DESCRIPTIO OF THE FIGURES

[0005] In the figures, which are not necessarily drawn to scale, like numerals may describe similar components in different views. Like numerals having different letter suffixes may represent different instances of similar components. The figures illustrate generally, by way of example, but not by way of limitation, various aspects discussed in the present document.

[0006] FIG. 1 A illustrates an architecture of a network in accordance with some embodiments.

[0007] FIG. IB is a simplified diagram of a next generation wireless network in accordance with some embodiments,

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

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

[0010] FIG. 4 is an illustration of a control plane protocol stack in accordance with some embodiments.

[0011] FIG. 5 is an illustration of a user plane protocol stack in accordance with some embodiments,

[0012] FIG. 6 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine- readable or computer-readable medium (e.g., a non-transitory machine- readable storage medium) and perform any one or more of the

methodologies discussed herein. [0013] FIG. 7 illustrates examples of multiple beam transmission in accordance with some embodiments.

[0014] FIG. 8 illustrates an exemplary V2X communication environment according to some aspects described herein.

[0015] FIG. 9 illustrates an exemplary depiction of a

communication network according to some aspects described herein.

[0016] FIG. 10 illustrates an exemplary V2X communication environment according to some aspects described herein.

[0017] FIG. 11 illustrates an exemplary internal configuration of a vehicular terminal device according to some aspects described herein.

[0018] FIG. 12 illustrates an exemplary internal configuration of a radio communication system of the vehicular terminal device of FIG. 11 according to some aspects described herein.

[0019] FIG. 13 illustrates exemplary transceivers using multiple radio communication technologies in the vehicular terminal device of FIG. 11 according to some aspects described herein.

[0020] FIG. 14 illustrates a terminal device configured for multi- band/multi-channel operation in multiple directions in accordance with some aspects.

[0021] FIG. 15 illustrates a terminal device configured for multi- band/multi-channel operation in accordance with some aspects.

[0022] FIG. 16 illustrates terminal devices using geo-location information for radio resource management, such as selection of radio resource for transmission/scheduling, in accordance with some aspects.

[0023] FIG. 17 illustrates terminal devices using geo-location information for radio layer relaying in accordance with some aspects.

[0024] FIG. 18 illustrates terminal devices using a combination of sensing-based radio resource selection and radio layer relaying in accordance with some aspects.

[0025] FIG. 19 illustrates terminal devices using network coding principles for V2V radio layer relaying in accordance with some aspects. [0026] FIG. 20 is a flow diagram illustrating example

functionalities for performing V2X communications in accordance with some aspects.

[0027] FIG. 21 illustrates a block diagram of a communication device such as an evolved Node-B (eNB), a new generation Node-B (gNB), or a user equipment (UE), in accordance with some aspects.

DETAILED DESCRIPTION

[0028] The following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of other embodiments.

Embodiments set forth in the claims encompass all available equivalents of those claims.

[0029] The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any aspect or design described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects or designs.

[0030] The words "plurality" and "multiple" in the description or the claims expressly refer to a quantity greater than one. The terms "group (of)," "set (of)," "collection (of)," "series (of)," "sequence (of)," "grouping (of)," etc., and the like in the description or in the claims refer to a quantity equal to or greater than one, i.e. one or more. Any term expressed in plural form that does not expressly state "plurality" or "multiple" likewise refers to a quantity equal to or greater than one. The terms "proper subset," "reduced subset," and "lesser subset" refer to a subset of a set that is not equal to the set, i.e. a subset of a set that contains less elements than the set.

[0031] As used herein, the term "software" includes any type of executable instruction or set of instructions, including embedded data in the software. Software may also encompass firmware. Software may create, delete or modify software, e.g., through a machine learning process. [0032] A "module" as used herein is understood to include any kind of functionality-implementing entity, which may include hardware-defined modules such as special-purpose hardware, software-defined modules such as a processor executing software or firmware, and mixed modules that include both hardware-defined and software-defined components, A module may thus be an analog circuit or component, digital circuit, mixed- signal circuit or component, logic circuit, processor, microprocessor, Central Processing Unit (CPU), application processor, Graphics Processing Unit (GPU), Digital Signal Processor (DSP), Field Programmable Gate Array (FPGA), integrated circuit, discrete circuit, Application Specific

Integrated Circuit (ASIC), etc., or any combination thereof. Any other kind of implementation of the respective functions which will be described below in further detail may also be understood as a "module". It is understood that any two (or more) of the modules detailed herein may be realized as a single module with substantially equivalent functionality, and conversely that any single module detailed herein may be realized as two (or more) separate modules with substantially equivalent functionality. Additionally, references to a "module" may refer to two or more modules that collectively form a single module.

[0033] The term "terminal device" utilized herein includes user-side devices (both mobile and immobile, such as a stand-alone UE or UE implemented as part of a vehicle, or UE placed within a vehicle) that may connect to a core network and various external networks via a radio access network. In some aspects, the term "terminal device" can include the vehicle that includes a UE or other smart device performing functionalities described herein. The term "network access node" or "network node" as utilized herein includes to a network-side device that provides a radio access network with which terminal devices may connect and exchange information with other networks through the network access node.

[0034] The term "base station" used in reference to an access node of a mobile communication network may be understood to include a macro base station (such as, for example, for cellular communications), micro/pico/femto base station, Node B, evolved Node-B (base station), new generation Node-B (gNB), Home base station, Remote Radio Head (RRH), relay point, access point (AP, such as, for example, for Wi-Fi, WLAN, WiGig, millimeter Wave (mmWave), etc. ) etc. As used herein, a "cell" in the setting of telecommunications may be understood to include an area (e.g., a public place) or space (e.g., multi-story building or airspace) served by a base station or access point. The base station may include mobile, e.g., installed in a vehicle, and the covered area or space may move accordingly. Accordingly, a cell may be covered by a set of co-located transmit and receive antennas, each of which also able to cover and serve a specific sector of the ceil. A base station or access point may serve one or more cells, where each cell is characterized by a distinct communication channel or standard (e.g., a base station offering 2G, 3G, LTE and 5G services). Macro-, micro-, femto-, pico-celis may have different cell sizes and ranges, and may be static or dynamic (e.g., a cell installed in a drone or balloon) or change its characteristic dynamically (for example, from macroceli to picocell, from static deployment to dynamic deployment, from omnidirectional to directional, from broadcast to narrowcast).

Communication channels may include narrowband or broadband.

Communication channels may also use carrier aggregation across radio communication technologies and standards, or flexibly adapt bandwidth to communication needs. In addition, terminal devices may include or act as base stations or access points or relays or other network access nodes.

[0035] The term "network" as utilized herein, for example, in reference to a communication network such as a mobile communication network, encompasses both an access section of a network (e.g., a radio access network (RAN) section) and a core section of a network (e.g., a core network section), but also, for an end-to-end system, encompasses mobile (including peer-to-peer, device to device, or machine to machine communications), access, backhaul, server, backbone and

gateway/interchange elements to other networks of the same or different type. The term "radio idle mode" or "radio idle state" used herein in reference to a mobile terminal refers to a radio control state in which the mobile terminal is not allocated at least one dedicated communication channel of a mobile communication network. The term "radio connected mode" or "radio connected state" used in reference to a mobile terminal refers to a radio control state in which the mobile terminal is allocated at least one dedicated uplink communication channel of a mobile

communication network. The uplink communication channel may be a physical channel or a virtual channel. Idle or connection mode may be connection-switched or packet-switched.

[0036] Unless explicitly specified, the term "transmit" encompasses both direct (point-to-point) and indirect transmission (via one or more intermediary points or nodes). Similarly, the term "receive" encompasses both direct and indirect reception. Furthermore, the terms "transmit," "receive," "communicate," and other similar terms encompass both physical transmission (e.g., the transmission of radio signals) and logical transmission (e.g., the transmission of logical data over a software-level connection). For example, a processor may transmit or receive data in the form of radio signals with another processor, where the physical transmission and reception is handled by radio-layer components such as RF transceivers and antennas, and the logical transmission and reception is performed by the processor. The term "communicate" encompasses one or both of transmitting and receiving, i.e. unidirectional or bidirectional communication in one or both of the incoming and outgoing directions. The term "calculate" encompasses both 'direct' calculations via a mathematical expression/formula/relationship and 'indirect' calculations via lookup or hash tables and other array indexing or searching operations, [0037] Several different vehicular radio communication

technologies, including short range radio communication technology (e.g., Dedicated Short Range Communications (DSRC)), cellular wide area radio communication technology (e.g., Long Term Evolution (LTE) Vehicle-to- Vehicle (V2V) and Vehicle-to-Everything (V2X)), and cellular narrowband radio communication technology may be used for communicating with and between vehicular terminal devices. These vehicular radio communication technologies target both autonomous driving use cases and delivery of standard mobile communications data, such as voice calls, text messages, and Internet and application data, to connected vehicles.

[0038] A short range radio communication technology may include e.g. a DSRC technology, a Bluetooth radio communication technology, an Ultra Wide Band (UWB) radio communication technology, a Wireless

Local Area Network radio communication technology (e.g. according to an IEEE 802. 1 1 (e.g. IEEE 802.11η) radio communication standard)), IrDA (Infrared Data Association), Z-Wave and ZigBee, HiperLAN/2 ((High Performance Radio LAN, an alternative ATM-like 5 GHz standardized technology), IEEE 802.1 la (5 GHz), IEEE 802, 1 Ig (2.4 GHz), IEEE 802. 1 In, IEEE 802.3 1VHT (VHT = Very High Throughput), e.g. IEEE 802.1 lac for VHT below 6GHz and IEEE 802.1 lad for VHT at 60 GHz, a Worldwide Interoperability for Microwave Access (WiMax) (e.g.

according to an IEEE 802.16 radio communication standard, e.g. WiMax fixed or WiMax mobile), WiPro, HiperMAN (High Performance Radio Metropolitan Area Network), IEEE 802, 16m Advanced Air Interface, WiGig (e.g., according to any IEEE 802.11 standard), millimeter Wave (mmW), centimeter Wave (cmW), and other similar radio communication technologies and the like.

[0039] A short range radio communication technology may, for example, include the following characteristics: the technology may be based on Carrier Sense Multiple Access (CSMA), the technology may be contention-based, e.g. usually no fully load channel possible; the technology may be rather inexpensive; no communication network provider is necessary for the spectrum; e.g. for DSRC: the add-on 802. 1 system may be implemented in most of the communication devices, e.g. in vehicles; the technology may be used to form an ad hoc network where there is no fixed communications infrastructure; the technology may provide a high data rate; the technology may in some cases not provide a redundancy frequency band; the technology may in some cases have latency as an issue, since the latency may be unpredictable; and the technology may in some cases have no central scheduler. [0040] A cellular wide area radio communication technology may include e.g. a Global System for Mobile Communications (GSM) radio communication technology, a General Packet Radio Service (GPRS) radio communication technology, an Enhanced Data Rates for GSM Evolution (EDGE) radio communication technology, or a Third Generation

Partnership Project (3 GPP) radio communication technology (e.g. UMTS (Universal Mobile Telecommunications System), FOMA (Freedom of Multimedia Access), 3 GPP LTE (long term Evolution), 3 GPP LTE

Advanced (long term Evolution Advanced)), CDMA2000 (Code division multiple access 2000), CDPD (Cellular Digital Packet Data), Mobitex, 3G (Third Generation), CSD (Circuit Switched Data), HSCSD (High-Speed Circuit-Switched Data), UMTS (3G) (Universal Mobile

Telecommunications System (Third Generation)), W-CDMA (UMTS) (Wideband Code Division Multiple Access (Universal Mobile

Telecommunications System)), HSPA (High Speed Packet Access), HSDPA (High-Speed Downlink Packet Access), HSUPA (High-Speed Uplink Packet Access), HSPA+ (High Speed Packet Access Pius), UMTS- TDD (Universal Mobile Telecommunications System - Time-Division Duplex), TD-CDMA (Time Division - Code Division Multiple Access), TD-CDMA (Time Division - Synchronous Code Division Multiple

Access), 3 GPP Rel. 8 (Pre-4G) (3rd Generation Partnership Project Release 8 (Pre-4th Generation)), UTRA (UMTS Terrestrial Radio Access), E- UTRA (Evolved UMTS Terrestrial Radio Access), LTE Advanced (4G) (long term Evolution Advanced (4th Generation)), cdmaOne (2G), CDMA2000 (3G) (Code division multiple access 2000 (Third generation)), EV-DO (Evolution-Data Optimized or Evolution-Data Only), AMPS (1 G) (Advanced Mobile Phone System (1st Generation)), TACS/ETACS (Total Access Communication System/Extended Total Access Communication System), D-AMPS (2G) (Digital AMPS (2nd Generation)), PTT (Push-to- talk), MTS (Mobile Telephone System), IMTS (Improved Mobile

Telephone System), AMTS (Advanced Mobile Telephone System), OLT (Norwegian for Offentiig Landmobil Telefoni, Public Land Mobile Telephony), MTD (Swedish abbreviation for Mobiltelefonisystem D, or Mobile telephony system D), Autotel/PALM (Public Automated Land Mobile), ARP (Finnish for Autoradiopuhelin, "car radio phone"), NMT (Nordic Mobile Telephony), Hicap (High capacity version of NTT (Nippon Telegraph and Telephone)), CDPD (Cellular Digital Packet Data), Mobitex, DataTAC, iDEN (Integrated Digital Enhanced Network), PDC (Personal Digital Cellular), CSD (Circuit Switched Data), PHS (Personal Handy- phone System), WiDEN (Wideband Integrated Digital Enhanced Network), iBurst, and Unlicensed Mobile Access (UMA, also referred to as also referred to as 3 GPP Generic Access Network, or GAN standard), and LTE- A (Long Term Evolution Advanced), LTE V2V, LTE V2X, 5G (e.g., millimeter Wave (mmWave), 3 GPP New Radio (NR)), next generation cellular standards like 6G, and other similar radio communication technologies. Cellular Wide Area radio communication technologies also include "small cells" of such technologies, such as microcells, femtocells, and picocelis. Cellular Wide Area radio communication technologies may be generally referred to herein as "cellular" communication technologies. Furthermore, as used herein the term GSM refers to both circuit- and packet-switched GSM, for example, including GPRS, EDGE, and any other related GSM technologies. Likewise, the term UMTS refers to both circuit- and packet-switched GSM, for example, including HSPA,

HSDPA/HSUPA, HSDPA+/HSUPA+, and any other related UMTS technologies. Further communication technologies include Line of sight (LiFi) communication technology. It is understood that exemplary scenarios detailed herein are demonstrative in nature, and accordingly may be similarly applied to various other mobile communication technologies, both existing and not yet formulated, particularly in cases where such mobile communication technologies share similar features as disclosed regarding the following examples.

[0041] Presence of multi-radios on one device, provide both opportunities and challenges. On one hand, configuration and management of devices— including for example provisioning and on-boarding— becomes more challenging especially in the vehicular networks where the environment is dynamic. On the other hand, by introducing mechanisms to allow different integrative or collocated radios to coexist and cooperate, better collective performance may be achieved, leading to a better user experience. In addition, connectivity coverage increase is expected for vehicles using multi-radio communications.

[0042] Techniques described herein are associated with new RAT design concepts to meet requirements of future vehicular services and communication systems. Enhanced vehicle-to-everything (eV2X) applications can be analyzed in the framework of the 3GPP NR design along with traditional enhanced mobile broadband (elviBB) and enhanced machine-type communications (eMTC) services. Due to ongoing transformation in the automotive industry towards a "connected car" vision and higher automation levels, new stringent requirements are imposed on V2X communication systems. The 3 GPP NR technology can be used to address the challenging V2X communication requirements to become a primary technology of choice for future vehicular services in a longer term, providing ubiquitous coverage and seamless access to network

infrastructure as well as reliable proximate connectivity capabilities.

[0043] V2X communications are characterized by unique technical challenges due to a number of deployment-specific factors, such as a high vehicle mobility/speed as wells as dynamic vehicle topology. The challenging radio environment of vehicular systems along with stringent V2X communication requirements may have specific implications on radio-layer design and thus detailed study and analysis of key eV2X technology components can be useful. Various eV2X technology components are described herein, which can be used to efficiently support eV2X services, focusing on sidelink eV2X radio-layer aspects.

[0044] FIG. 1 A illustrates an architecture of a network in accordance with some embodiments. The network 100 is shown to include a UE 102, which can be part of a terminal device (e.g., a vehicle) 101. The UE 102 is illustrated as a smartphone (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.

[0045] In some embodiments, any UE 102 can comprise an Internet of Things (loT) UE, which can comprise a network access layer designed for low-power loT 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.

[0046] The UE 102 may be configured to connect, e.g.,

communicatively couple, with a radio access network (RAN) 110 - the RAN 110 may be, for example, an Evolved Universal Mobile

Telecommunications System (UMTS) Terrestrial Radio Access Network ( ! ( I RAN ), a NextGen RAN (NG RAN), or some other type of RAN. The UE 102 utilizes a connection 103 (to RAN 1 10), which can include a physical communications interface or layer (discussed in further detail below); in this example, the connection 103 is 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-Taik (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,

[0047] In this embodiment, the UE 102 may further directly exchange communication data with another UE via a ProSe interface. The ProSe interface 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).

[0048] The UE 102 (and the vehicle 101) are shown to be configured to access an access point (AP) 106 via connection 107. The connection 107 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.1 protocol, wherein the AP 106 would comprise a wireless fidelity (WiFi®) router. In this example, the AP 106 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).

[0049] The RAN 1 10 can include one or more access nodes that enable the connections 103 and 104. 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 110 may include one or more RAN nodes for providing macroceils, e.g., macro RAN node 111, 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 macroceils), e.g., low power (LP) RAN node 1 2,

[0050] Any of the RAN nodes 1 1 1 and 12 can terminate the air interface protocol and can be the first point of contact for the UE 102. In some embodiments, any of the RAN nodes 1 1 1 and 12 can fulfill various logical functions for the RAN 1 10 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. In an example, any of the nodes 1 1 1 and/or 12 can be a new generation node-B (gNB), an evolved node-B (eNB) or another type of RAN node,

[0051] In accordance with some embodiments, the UE 102 can be configured to communicate using Orthogonal Frequency-Division Multiplexing (OFDM) communication signals with each other or with any of the RAN nodes 111 and 1 12 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.

[0052] In some embodiments, a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 1 1 1 and 112 to the UE 02, 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.

[0053] The physical downlink shared channel (PDSCH) may carry user data and higher-layer signaling to the UE 102. 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 UE 102 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 02 within a cell) may be performed at any of the RAN nodes 111 and 1 12 based on channel quality information fed back from the UE 102. The downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) the UE 102.

[0054] 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),

[0055] 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.

[0056] The RAN 1 0 is shown to be communicatively coupled to a core network (CN) 120 -via an SI interface 1 13. In embodiments, the CN 120 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN. In this embodiment the S I interface 113 is split into two parts: the SI -U interface 114, which carries traffic data between the RAN nodes 111 and 112 and the serving gateway (S-GW) 122, and the SI -mobility management entity (MME) interface 115, which is a signaling interface between the RAN nodes 11 1 and 1 12 and MMEs 121.

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

authentication, authorization, naming/addressing resolution, location dependencies, etc.

[0058] The S-GW 122 may terminate the SI interface 113 towards the RAN 110, and routes data packets between the RAN 110 and the CN 120. In addition, the S-GW 122 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.

[0059] The P-GW 123 may terminate an SGi interface toward a PDN. The P-GW 123 may route data packets between the EPC network 123 and external networks such as a network including the application server 130 (alternatively referred to as application function (AT)) via an Internet Protocol (IP) interface 125. Generally, the application server 130 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^r 123 is shown to be communicatively coupled to an application server 130 via an IP

communications interface 125. The application server 130 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 UE 102 via the CN 120.

[0060] The P-GW 123 may further be a node for policy

enforcement and charging data collection. Policy and Charging

Enforcement Function (PCRF) 126 is the policy and charging control element of the CN 120. 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 PCRF^'s 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 126 may be communicatively coupled to the application server 130 via the P-GW 123. The application server 130 may signal the PCRF 126 to indicate a new service flow and select the appropriate Quality of Service (QoS) and charging parameters. The PCRF 26 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 130.

[0061] In an example, any of the nodes 111 or 112 can be configured to communicate to the UE 102 (e.g., dynamically) an antenna panel selection and a receive (Rx) beam selection that should be used by the UE for data reception on a physical downlink shared channel (PDSCH) as well as for channel state information reference signal (CSI-RS) measurements and channel state information (CSI) calculation.

[0062] In an example, any of the nodes 11 1 or 112 can be configured to communicate to the UE 102 (e.g., dynamically) an antenna panel selection and a transmit (Tx) beam selection that should be used by the UE for data transmission on a physical uplink shared channel (PUSCH) as well as for sounding reference signal (SRS) transmission. [0063] FIG. IB is a simplified diagram of a next generation wireless network in accordance with some embodiments. The wireless network may be similar to that shown in FIG. 1 A but may contain components associated with a 5G network. The wireless network may contain, among other elements not shown, a RAN 1 10 coupled to the core network 120 (as well as to the Internet which can connect the core network 120 with other core networks 120). In some embodiments, the RAN 110 and the core network 120 may be a next generation (5G) 3 GPP RAN and 5G core network, respectively. The RAN 1 10 may include an upper layer of a new generation node-B (gNB) (also referred to as a new radio (NR.) base station (BS) (ULNRBS)) 140 and multiple lower layers of different gNBs (NR. BS (LLNRBS)) 111. The LLNRBS s 111 can be connected to the ULNRBS 140 via a Z interface. The Z interface can be open or proprietary. In some examples, the LLNRBS 111 can be referred to as a transmission-reception point (TRP). If the Z interface is proprietary, then the ULNRBS 140 and the LLNRBS 1 1 1 may be provided by the same vendor. The LLNRBS 11 1 can be connected by a Y interface, which may be equivalent to the LTE X2 interface. The ULNRBS 140 may be connected to the core network 120 through the S I interface 1 13.

[0064] As used herein, the term circuitry may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), or memory (shared, dedicated, or group) that executes one or more software or firmware programs, a combinational logic circuit, or other suitable hardware components that provide the described functionality. In some

embodiments, the circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules. In some embodiments, circuitry may include logic, at least partially operable in hardware. Embodiments described herein may be implemented into a system using any suitably configured hardware or software.

[0065] FIG. 2 illustrates example components of a device 200 in accordance with some embodiments. In some embodiments, the device 200 may include application circuitry 202, baseband circuitry 204, Radio Frequency (RF) circuitry 206, front-end module (FEM) circuitry 208, one or more antennas 2 0, and power management circuitry (PMC) 212 coupled together at least as shown. The components of the illustrated device 200 may be included in a terminal device (e.g., in a UE or another mobile device) or a RAN node. In some embodiments, the device 200 may include less elements (e.g., a RAN node may not utilize application circuitry 202, and instead include a processor/controller to process IP data received from an EPC). In some embodiments, the device 200 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-RA ) implementations).

[0066] The application circuitry 202 may include one or more application processors. For example, the application circuitry 202 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 200. In some embodiments, processors of application circuitry 202 may process IP data packets received from an EPC.

[0067] The baseband circuitry 204 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 204 may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RF circuitry 206 and to generate baseband signals for a transmit signal path of the RF circuitry 206. Baseband processing circuity 204 may interface with the application circuitry 202 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 206. For example, in some embodiments, the baseband circuitry 204 may include a third generation (3G) baseband processor 204 A, a fourth generation (4G) baseband processor 204B, a fifth generation (5G) baseband processor 204C, or other baseband processors) 204D 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 204 (e.g., one or more of baseband processors 204A-D) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 206. In other embodiments, some or all of the functionality of baseband processors 204 A-D may be included in modules stored in the memory 204G and executed via a Central Processing Unit (CPU) 204E. 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 204 may include Fast-Fourier Transform (FFT), preceding, or constellation mapping/demapping functionality. In some embodiments,

encoding/decoding circuitry of the baseband circuitry 204 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.

[0068] In some embodiments, the baseband circuitry 204 may include one or more audio digital signal processor(s) (DSP) 204F. The audio DSP(s) 204F 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 204 and the application circuitry 202 may be

implemented together such as, for example, on a system on a chip (SOC). |Ό069| In some embodiments, the baseband circuitry 204 may provide for communication compatible with one or more radio

technologies. For example, in some embodiments, the baseband circuitry 204 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 204 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

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

[0071] In some embodiments, the receive signal path of the RF circuitry 206 may include mixer circuitry 206 A, amplifier circuitry 206B and filter circuitry 206C. In some embodiments, the transmit signal path of the RF circuitry 206 may include filter circuitry 206C and mixer circuitry 206A. RF circuitry 206 may also include synthesizer circuitry 206D for synthesizing a frequency for use by the mixer circuitry 206 A of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 206 A of the receive signal path may be configured to down- convert RF signals received from the FEM circuitry 208 based on the synthesized frequency provided by synthesizer circuitry 206D. The amplifier circuitry 206B may be configured to amplify the down-converted signals and the filter circuitry 206C may be a low-pass filter (LPF) or bandpass 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 204 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 206 A of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.

[0072] In some embodiments, the mixer circuitry 206 A of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 206D to generate RF output signals for the FEM circuitry 208. The baseband signals may be provided by the baseband circuitry 204 and may be filtered by filter circuitry 206C.

[0073] In some embodiments, the mixer circuitry 206A of the receive signal path and the mixer circuitry 206A 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 206 A of the receive signal path and the mixer circuitry 206A 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 206A of the receive signal path and the mixer circuitry 206 A may be arranged for direct downconversion and direct upconversion, respectively. In some embodiments, the mixer circuitry 206A of the receive signal path and the mixer circuitry 206A of the transmit signal path may be configured for super-heterodyne operation.

[0074] 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 206 may include analog-to-digital converter (ADC) and digital-to- analog converter (DAC) circuitry and the baseband circuitry 204 may include a digital baseband interface to communicate with the RF circuitry 206.

[0075] 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.

[0076] In some embodiments, the synthesizer circuitry 206D 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 trequency synthesizers may be suitable. For example, synthesizer circuitry 206D may be a delta-si gma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

[0077] The synthesizer circuitry 206D may be configured to synthesize an output frequency for use by the mixer circuitry 206 A of the RF circuitry 206 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 206D may be a fractional N/ + 1 synthe sizer .

[0078] 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 204 or the applications processor 202 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 202.

[0079] Synthesizer circuitry 206D of the RF circuitry 206 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 (DP A). 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.

[0080] In some embodiments, synthesizer circuitry 206D 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 206 may include an IQ/polar converter.

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

[0082] In some embodiments, the FEM circuitry 208 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 206), The transmit signal path of the FEM circuitry 208 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 206), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 210). [0083] In some embodiments, the PMC 212 may manage power provided to the baseband circuitry 204, In particular, the PMC 212 may control power-source selection, voltage scaling, batteiy charging, or DC-to- DC conversion. The PMC 212 may often be included when the device 200 is capable of being powered by a battery, for example, when the device is included in a UE. The PMC 212 may increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.

[0084] While FIG. 2 shows the PMC 212 coupled only with the baseband circuitry 204. However, in other embodiments, the PMC 212 may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, application circuitry 202, RF circuitry 206, or FEM 208.

[0085] In some embodiments, the PMC 212 may control, or otherwise be part of, various power saving mechanisms of the device 200. For example, if the device 200 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 200 may power down for brief intervals of time and thus save power.

[0086] If there is no data traffic activity for an extended period of time, then the device 200 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 200 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 200 may not receive data in this state, in order to receive data, it must transition back to RRC Connected state.

[0087] 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,

[0088] Processors of the application circuitry 202 and processors of the baseband circuitry 204 may be used to execute elements of one or more instances of a protocol stack. For example, processors of the baseband circuitry 204, alone or in combination, may be used execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry 204 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.

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

[0090] The baseband circuitry 204 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface 312 (e.g., an interface to send/receive data to/from memory external to the baseband circuitry 204), an application circuitry interface 314 (e.g., an interface to send/receive data to/from the application circuitry 202 of FIG. 2), an RF circuitry interface 3 16 (e.g., an interface to send/receive data to/from RF circuitry 206 of FIG. 2), a wireless hardware connectivity interface 318 (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 320 (e.g., an interface to send/receive power or control signals to/from the PMC 212).

[0091] FIG. 4 is an illustration of a control plane protocol stack in accordance with some embodiments. In this embodiment, a control plane

400 is shown as a communications protocol stack between the UE 102, the RAN node 111 (or alternatively, the RAN node 1 12), and the MME 121.

[0092] The PHY layer 40 may transmit or receive information used by the MAC layer 402 over one or more air interfaces. The PHY layer

401 may further perform link adaptation or adaptive modulation and coding (AMC), power control, cell search (e.g., for initial synchronization and handover purposes), and other measurements used by higher layers, such as the RRC layer 405. The PHY layer 401 may still further perform error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, modulation/demodulation of physical channels, interleaving, rate matching, mapping onto physical channels, and Multiple Input Multiple Output (MIMO) antenna processing,

[0093] The MAC layer 402 may perform mapping between logical channels and transport channels, multiplexing of MAC service data units (SDUs) from one or more logical channels onto transport blocks (TB) to be delivered to PHY via transport channels, de-multiplexing MAC SDUs to one or more logical channels from transport blocks (TB) delivered from the PHY via transport channels, multiplexing MAC SDUs onto TBs, scheduling information reporting, error correction through hybrid automatic repeat request (HARQ), and logical channel prioritization.

[0094] The RLC layer 403 may operate in a plurality of modes of operation, including: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). The RLC layer 403 may execute transfer of upper layer protocol data units (PDUs), error correction through automatic repeat request (ARQ) for AM data transfers, and concatenation, segmentation and reassembly of RLC SDUs for UM and AM data transfers. The RLC layer 403 may also execute re-segmentation of RLC data PDUs for AM data transfers, reorder RLC data PDUs for UM and AM data transfers, detect duplicate data for UM and AM data transfers, discard RLC SDUs for UM and AM data transfers, detect protocol errors for AM data transfers, and perform RLC re-establishment.

[0095] The PDCP layer 404 may execute header compression and decompression of IP data, maintain PDCP Sequence Numbers (SNs), perform in-sequence delivery of upper layer PDUs at re-establishment of lower layers, eliminate duplicates of lower layer SDUs at re-establishment of lower layers for radio bearers mapped on RLC AM, cipher and decipher control plane data, perform integrity protection and integrity verification of control plane data, control timer-based discard of data, and perform security operations (e.g., ciphering, deciphering, integrity protection, integrity verification, etc.).

[0096] The main services and functions of the RRC layer 405 may include broadcast of system information (e.g., included in Master

Information Blocks (MIBs) or System Information Blocks (SIBs) related to the non-access stratum (NAS)), broadcast of system information related to the access stratum (AS), paging, establishment, maintenance and release of an RRC connection between the UE and E-UTRAN (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), establishment, configuration, maintenance and release of point to point Radio Bearers, security functions including key management, inter radio access technology (RAT) mobility, and

measurement configuration for UE measurement reporting. Said MIBs and SIBs may comprise one or more information elements (IEs), which may each comprise individual data fields or data structures.

[0097] The UE 102 and the RAN node 11 1 may utilize a Uu interface (e.g., an LTE-Uu interface) to exchange control plane data via a protocol stack comprising the PHY layer 401, the MAC layer 402, the RLC layer 403, the PDCP layer 404, and the RRC layer 405.

[0098] The non-access stratum (NAS) protocols 406 form the highest stratum of the control plane between the UE 102 and the MME 121. The NAS protocols 406 support the mobility of the UE 102 and the session management procedures to establish and maintain IP connectivity between the UE 102 and the P-GW 123. [0099] The S I Application Protocol (Sl-AP) layer 415 may support the functions of the S I interface and comprise Elementary Procedures (EPs). An EP is a unit of interaction between the RAN node 111 and the CN 120. The S l-AP layer services may comprise two groups: UE- associated services and non UE-associated services. These services perform functions including, but not limited to: E-UTRAN Radio Access Bearer (E-RAB) management, UE capability indication, mobility, NAS signaling transport, RAN Information Management (RIM), and

configuration transfer.

[00100] The Stream Control Transmission Protocol (SCTP) layer (alternatively referred to as the SCTP/IP layer) 414 may ensure reliable delivery of signaling messages between the RAN node 111 and the MME 121 based, in part, on the IP protocol, supported by the IP layer 413. The L2 layer 412 and the LI layer 41 1 may refer to communication links (e.g., wired or wireless) used by the RAN node and the MME to exchange information.

[00101] The RAN node 111 and the MME 121 may utilize an S -

MME interface to exchange control plane data via a protocol stack comprising the LI layer 411, the L2 layer 412, the IP layer 413, the SCTP layer 414, and the S 1 -AP layer 415.

[00102] FIG. 5 is an illustration of a user plane protocol stack in accordance with some embodiments. In this embodiment, a user plane 500 is shown as a communications protocol stack between the UE 102 (or alternatively, the UE 102), the RAN node 11 1 (or alternatively, the RAN node 112), the S-GW 122, and the P-GW 123. The user plane 500 may utilize at least some of the same protocol layers as the control plane 400. For example, the UE 102 and the RAN node 111 may utilize a Uu interface (e.g., an LTE-Uu interface) to exchange user plane data via a protocol stack comprising the PHY layer 401 , the MAC layer 402, the RLC layer 403, and the PDCP layer 404.

[00103] The General Packet Radio Service (GPRS) Tunneling

Protocol for the user plane (GTP-U) layer 504 may be used for carrying user data within the GPRS core network and between the radio access network and the core network. The user data transported can he packets in any of IPv4, IPv6, or PPP formats, for example. The UDP and IP security (UDP/IP) layer 503 may provide checksums for data integrity, port numbers for addressing different functions at the source and destination, and encryption and authentication on the selected data flows. The RAN node 111 and the S-GW 122 may utilize an Sl-U interface to exchange user plane data via a protocol stack comprising the LI layer 41 1, the L2 layer 412, the UDP/IP layer 503, and the GTP-U layer 504. The S-GW 122 and the P-GW 123 may utilize an S5/S8a interface to exchange user plane data via a protocol stack comprising the LI layer 411, the L2 layer 412, the UDP/IP layer 503, and the GTP-U layer 504. As discussed above with respect to FIG. 4, NAS protocols support the mobility of the UE 102 and the session management procedures to establish and maintain IP

connectivity between the UE 102 and the P-GW 123.

[00104] FIG. 6 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine- readable or computer-readable medium (e.g., a non-transitory machine- readable storage medium) and perform any one or more of the

methodologies discussed herein. Specifically, FIG. 6 shows a

diagrammatic representation of hardware resources 600 including one or more processors (or processor cores) 610, one or more memory/storage devices 620, and one or more communication resources 630, each of which may be communicatively coupled via a bus 640. For embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 602 may be executed to provide an execution environment for one or more network slices/sub- slices to utilize the hardware resources 600

[00105] The processors 610 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) such as a baseband processor, an application specific integrated circuit (ASIC), a radio-frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, a processor 612 and a processor 614, [00106] The memory/storage devices 620 may include main memory, disk storage, or any suitable combination thereof. The

memory/ storage devices 620 may include, but are not limited to any type of volatile or non-volatile memory such as dynamic random access memory (DRAM), static random-access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc.

[00107] The communication resources 630 may include

interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices 604 or one or more databases 606 via a network 608. For example, the communication resources 630 may include wired communication components (e.g., for coupling via a Universal Serial Bus (USB)), cellular communication components, NFC components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components.

[00108] Instructions 650 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 610 to perform any one or more of the methodologies discussed herein. The instructions 650 may reside, completely or partially, within at least one of the processors 610 (e.g., within the processor's cache memory), the memory/ storage devices 620, or any suitable combination thereof Furthermore, any portion of the instructions 650 may be transferred to the hardware resources 600 from any combination of the peripheral devices 604 or the databases 606. Accordingly, the memory of processors 610, the memory/storage devices 620, the peripheral devices 604, and the databases 606 are examples of computer-readable and machine-readable media.

[00109] FIG. 7 illustrates examples of multiple beam transmission in accordance with some embodiments. Although the example scenarios 700 and 750 depicted in FIG. 7 may illustrate some aspects of techniques disclosed herein, it will be understood that embodiments are not limited by example scenarios 700 and 750, Embodiments are not limited to the number or type of components shown in FIG. 7 and are also not limited to the number or arrangement of transmitted beams shown in FIG. 7.

[00110] In example scenario 700, the eNB 1 1 1 may transmit a signal on multiple beams 705-720, any or all of which may be received at the UE 102. It should be noted that the number of beams or transmission angles as shown are not limiting. As the beams 705-720 may be directional, transmitted energy from the beams 705-720 may be concentrated in the direction shown. Therefore, the UE 102 may not necessarily receive a significant amount of energy from beams 705 and 710 in some cases, due to the relative location of the UE 102.

[00111] UE 102 may receive a significant amount of energy from the beams 715 and 720 as shown. As an example, the beams 705-720 may be transmitted using different reference signals, and the UE 102 may determine channel-state information (CSI) feedback or other information for beams 715 and 720. In some embodiments, each of beams 705-720 are configured as CSI reference signals (CSI-RS). In related embodiments, the CSI-RS signal is a part of the discovery reference signaling (DRS) configuration. The DRS configuration may serve to inform the UE 102 about the physical resources (e.g., subframes, subcarriers) on which the CSI-RS signal will be found. In related embodiments, the UE 102 is further informed about any scrambling sequences that are to be applied for CSI-RS.

[00112] In an example, up to 2 MIMO layers may be transmitted within each beam by using different polarizations. More than 2 MIMO layers may be transmitted by using multiple beams. In an example, the UE is configured to discover the available beams and report those discovered beams to the eNB prior to the MIMO data transmissions using suitable reporting messaging. Based on the reporting messaging, the eNB 104 may determine suitable beam directions for the MIMO layers to be used for data communications with the UE 102. In various embodiments, there may be up to 2, 4, 8, 16, 32, or more MIMO layers, depending on the number of MIMO layers that are supported by the eNB 111 and UE 102. In a given scenario, the number of MIMO layers that may actually be used will depend on the quality of the signaling received at the UE 102, and the availability of reflected beams arriving at diverse angles at the UE 102 such that the UE 102 may discriminate the data carried on the separate beams. In an example, the e B 11 1 can communicate control signal messaging (e.g., downlink control information, or DCI) with an antenna panel selection and a beam index selection for the UE to use when receiving data (e.g., via PDSCH) or transmitting data (e.g., via PUSCH).

[00113] In the example scenario 750, the UE 102 may determine angles or other information (such as CSI feedback/report, including beam index, precoder, channel-quality indicator (CQI) or other) for the beams 765 and 770. The UE 102 may also determine such information when received at other angles, such as the illustrated beams 775 and 780. The beams 775 and 780 are demarcated using a dotted line configuration to indicate that they may not necessarily be transmitted at those angles, but that the UE 102 may determine the beam directions of beams 775 and 780 using such techniques as receive beam-forming, as receive directions. This situation may occur, for example, when a transmitted beam reflects from an object in the vicinity of the UE 102, and arrives at the UE 102 according to its reflected, rather than incident, angle.

[00114] In an example, antenna switching in an LTE communication system supports spatial diversity schemes at the UE. The antenna switching can be applied at the UE transmitter (i.e. for uplink

communications) and/or at the UE receiver (i.e. for downlink

communication). In the antenna switching in the receiving mode, the UE does not process the signals received by all receiving antennas. Instead, the UE can dynamically use the antenna subset that have optimal instantaneous link conditions to the eNB transmitter, and only processes the signals received by those antennas. This technique can enable the receiver to employ smaller number of transceiver units (TXRUs) or radio frequency (RF) chains. Similarly, in transmit antenna switching, the UE transmitter employs smaller number of TXRUs or RF chains than the available number of antennas. For example, for typical uplink implementation of LTE, the UE can be equipped with two antenna elements for the receiving mode (i.e., for downlink communications) and only one antenna element in

transmitting mode (i.e., for uplink communications). The smaller number of transmit (TX) antenna elements is used to reduce the hardware cost and achieve greater energy efficiency at the UEs. Different number of the transmit and receive antennas in this case makes the antenna switching in the uplink an attractive technology to support diversity schemes in a cost efficient manner.

[00115] In an example, LTE uplink transmissions can use antenna switching, which is supported by 1-bit feedback from the eNB to indicate to the UE the selected antenna to use for transmitting data. The data can be transmitted on the Physical Uplink Shared Channel (PUSCH). The feedback can be communicated by the eNB in the uplink scheduling grant communicated on a control channel. For the SRS transmissions in the uplink, the antenna switching can be supported by specifying the antenna order that should be used for the SRS transmission in a given OFDM symbol. Conventionally, antenna switching for the DL is not supported in LTE.

[00116] In some aspects, evolved V2X (or eV2X) communication use cases can target assisted or autonomous driving applications, including but not limited to vehicle platooning (limited or fully automated), collective perception of environment, remote driving, and autonomous driving (limited or fully automated). The evolved V2X use cases can be associated with requirements on different V2X communication types including V2V, V2I and V2N, where a vehicle communicates with other vehicles, Road Side Units (UE-or gNB-type RSUs), or a server residing in a network, respectively. In some aspects, the end-to-end communication latency can vary in the range from 5 to 30 ms (with typical values below 10ms), and associated reliability can vary in the range from 90% to 99.999%. In terms of traffic type, eV2X systems can support periodic and event triggered transmissions with packet size from 300 bytes to 6500 bytes. In some aspects, the eV2X communications data rate can vary from a few 0.5-2 Mbps to 1 Gbps, where throughput of 10-60 Mbps can be considered as a typical values in case of video sharing for autonomous platooning and driving. In some aspects, target communication ranges can vary from 80m to 1000m, where larger ranges can be characterized by lower reliability and latency requirements (e.g., 3ms/200m/99.999%, 10ms/500m/99.99%, and 50ms/1000m/99%). In this regard, R-based V2X communication can be configured to support solutions that can provide low latency, high reliability, long range, and various data rates (from low to high). Beside traditional communication requirements, many of eV2X applications can be configured with high precision positioning capabilities that are essential for autonomous driving applications.

[00117] FIG. 8 illustrates an exemplary V2X communication environment according to some aspects described herein. Referring to FIG. 8, the V2X communication environment 800 may include various V2X enabled devices, such as vehicular terminal devices (e.g., vehicles) 808 and 810, a roadside unit (RSU) 806, a V2X enabled base station or an evolved Node-B (base station) 804, and a V2X enabled infrastructure 802. Each of the V2X enabled devices within the V2X communication environment 800 may include a plurality of radios, where each radio may be configured to operate in one or more of a plurality of wired or wireless radio access technologies, RATs. Example RATs include a dedicated short-range communication (DSRC) radio communication technology, a wireless access vehicular environment (WAVE) radio communication technology, a Bluetooth radio communication technology, an IEEE 802.1 1 radio communication technology, an LTE radio communication technology, and a 5G radio communication technology (e.g., communications in a mm Wave band of frequencies 30-300 GHz and/or cm Wave bands in frequencies below 30 GHz).

[00118] In some aspects, V2X deployments within the V2X communication environment 800 may use multiple RATs operating on different bands (e.g., licensed, un-licensed, light licensed and high frequency bands) to improve V2X wireless connectivity. Furthermore, V2X communication infrastructure within the V2X environment 800 may be deployed with different tiers of cells comprising traditional macro-cells, small cells deployed on RSUs (e.g., RSU 806) as well as allow for direct vehicle-to-vehicle communication (e.g., communication between vehicles 808 and 810 using multiple hops). In this regard, communications within the V2X environment 800 may for example include V2N (Vehicle-to- Network) communications, V2I (Vehicle-to-Infrastructure)

communications, V2V (Vehicle-to- Vehicle) communications, and V2P (Vehicle-to-Pedestrians) communications. In some aspects, multiple V2X communication links, such as communication links 812, may be exploited to improve the connectivity performance of the V2X environment 800. The communication links 812 in FIG. 8 are illustrated only as examples and other links may also be used in the V2X communication environment.

Each of the links 812 between any two or more of the V2X enabled devices in FIG. 8 can include multi-links, using the same or different RATs of multiple available RATs.

[00119] In some aspects, terminal devices 808 and 810 within the V2X communication environment 800 can be configured for high speed V2V communication, at high carrier frequencies (e.g. 5.9 GHz in low band communications, and 63 GHz in high band communications respectively). In some aspects, the subcarrier spacing can be optimized to make NR. eV2X design more robust to Doppler effects and synchronization errors. In some aspects, for LTE V2V communication at 5.9GHz, the frequency offset caused by Doppler effects and synchronization errors may be up to 7.4 kHz. In order to reduce V2V system sensitivity to the inter-carrier interference (ICI) effects and improve demodulation performance, increased subcarrier spacing and reduced symbol durations can be considered. In some aspects, for eV2X communications below 6 GHz

(e.g., 5.9 GHz), the 30 and 60 kHz subcarrier spacing can be used. In some aspects, for eV2X communications above 6 GHz (e.g., 63 GHz), the subcarrier spacing can be scaled up accordingly (e.g., 240 and 480 kHz subcarrier spacing can be used).

[00120] FIG. 9 illustrates an exemplary depiction of a

communication network 900 according to some aspects described herein. As shown in FIG. 9, communication network 900 may be an end-to-end network spanning from radio access network 902 to backbone networks 932 and 942. Backbone networks 932 and 942 may be realized as predominantly wireline networks. Network access nodes 920 to 926 may include a radio access network and may wirelessiy transmit and receive data with terminal devices 904 to 916 to provide radio access connections to terminal devices 904 to 916. Terminal devices 904 to 916 may utilize the radio access connections provided by radio access network 902 to exchange data on end-to-end communication connections with servers in backbone networks 932 and 942. The radio access connections between terminal devices 904 to 916 and network access nodes 920 to 926 may be implemented according to one or more RATs, where each terminal device may transmit and receive data with a corresponding network access node according to the protocols of a particular RAT that governs the radio access connection. In some aspects, one or more of terminal devices 904 to 916 may utilize licensed spectrum or unlicensed spectrum for the radio access connections. In some aspects, one or more of terminal devices 904 to 916 may directly communicate with one another according to any of a variety of different device-to-device (D2D) communication protocols.

[00121] As shown in FIG. 9, in some aspects terminal devices such as terminal devices 906 to 910 may rely on a forwarding link provided by terminal device 904, where terminal device 904 may act as a gateway or relay between terminal devices 906 to 910 and network access node 920. In some aspects, terminal devices 906 to 910 may be configured according to a mesh or multi-hop network and may communicate with terminal device 904 via one or more other terminal devices and using one or more multi- link connections using one or more of multiple RATs (multi-RAT). The configuration of terminal devices, e.g., a mesh or multi-hop configuration, may change dynamically e.g., according to terminal or user requirements, the current radio or network environment, the availability or performance of applications and sendees, or the cost of communications or access.

[00122] In some aspects, terminal devices such as terminal device 916 may utilize relay node 918 to transmit or receive data with network access node 926, where relay node 918 may perform relay transmission between terminal devices 916 and network access node 926, e.g., with a simple repeating scheme or a more complex processing and forwarding scheme. The relay may also be a realized as a series of relays, or use opportunistic relaying, where a best or approximately best relay or series of relays at a given moment in time or time interval is used,

[00123] In some aspects, network access nodes, such as network access node 924 and 926, may interface with core network 930, which may provide routing, control, and management functions that govern both radio access connections and core network and backhaul connections. As shown in FIG. 9, core network 930 may interface with backbone network 942, and may perform network gateway functions to manage the transfer of data between network access nodes 924 and 926 and the various servers of backbone network 942. In some aspects, network access nodes 924 and 926 may be directly connected with each other via a direct interface, which may be wired or wireless. In some aspects, network access nodes such as network access nodes 920 may interface directly with backbone network 932. In some aspects, network access nodes such as network access node 922 may interface with backbone network 932 via router 928.

[00124] Backbone networks 932 and 942 may contain various different Internet and external servers in servers 934 to 938 and 944 to 948. Terminal devices 904 to 916 may transmit and receive data with servers 934 to 938 and 944 to 948 on logical software-level connections that rely- on the radio access network and other intermediate interfaces for lower layer transport. Terminal devices 904 to 916 may therefore utilize communication network 900 as an end-to-end network to transmit and receive data, which may include internet and application data in addition to other types of user-plane data. In some aspects backbone networks 932 and 942 may interface via gateways 940 and 950, which may be connected at interchange 952.

[00125] Some of terminal devices 904 to 916 may be mobile de vices such as smartphones, tablet PCs, and the like. Other terminal devices may be static devices such as devices integrated in a V2X communication environment. By way of example, some terminal devices may be integrated in a traffic light or a traffic sign or in a street post, and the like. Some terminal devices may be integrated in a vehicle. Some of the terminal devices 904 to 916 may be low power consumption devices, some of the terminal devices may provide a minimum QoS, and some may provide the capability to communicate using multi-links on different RATs and so forth.

[00126] FIG. 10 illustrates an exemplary V2X communication environment 1000 according to some aspects described herein. More specifically, FIG. 10 shows an exemplary excerpt of a plurality of roads 1022, 1024, and 1026, A plurality of vehicles such as vehicles 1028--- 1040 may drive or stand on or aside of roads 1022- 1026. Terminal devices having various mobile radio capabilities may be integrated in vehicles 028-1040. The terminal devices may be configured to support different RATs, such as one or more Short Range radio communication technologies or one or more Cellular Wide Area radio communication technologies or one or more cellular wideband radio communication technologies as described herein (e.g., communications at frequencies below 6 GHz (such as 5.9 GHz) and communications at frequencies above 6 GHz (such as 63 GHz)). Moreover, infrastructure objects such as a V2X enabled base station or an evolved Node-B (base station) 1002, a V2X enabled infrastructure 1016, traffic lights 1018, 1020, road side units (RSU) 1004- 1014, road posts, traffic signs, and the like may be provided and may be configured to support the different RATs using multi-radio, multi-link connectivity as described herein.

[00127] Terminal devices having various mobile radio capabilities may be integrated in traffic infrastructure objects 1002-1020. These terminal devices may be configured to support different RATs, such as one or more Short Range radio communication technologies or one or more Cellular Wide Area radio communication technologies or one or more cellular narrowband radio communication technologies as described herein. An arbitrary number of base stations (e.g., 11 and 112) or Wireless Access Points may also be provided to be part of one or more different RATs which may be of the same or of different radio communication network providers. [00128] More and more vehicles (e.g., vehicles 1028-1040) may he connected to the Internet and to each other via one or more communication links (e.g., multiple mm Wave and/or cmWave communication links). Furthermore, the vehicles 1028-1040 may advance toward higher automation thereof, which results in various demands with respect to terminal devices, e.g. with respect to power consumption, interoperability, coexistence, device access, synchronization of various terminal devices. In order to deal with increasingly complex road situations, in accordance with some aspects automated vehicles may rely not only on their own sensors, but also on information detected or transmitted by other vehicles or infrastructure components. Therefore, the vehicles may cooperate with each other and it may he desired that the information transmitted between various vehicles and infrastructure components reach its respective destination reliably within an exceedingly short timeframe. In this regard, multi-radio, multi-link communications using one or more RATs may take place between communication nodes (e.g., infrastructure components 1002-1020 and vehicles 1028-1040) within the V2X communication environment 1000 to improve V2X connectivity performance across several metrics, such as reliability, latency, data rate, and so forth.

[00129] As will be described in more detail below, multi-link connectivity in the V2X communication network 1000 may be based on using communication links operating on the same or different frequency bands, as well as on different RATs or the same RAT. Example V2X communication technologies, which may be included in the RATs include DSRC, LTE-based communications (e.g., LTE MBMS, LTE SC-PTM, LTE ProSe, LTE V2X, and LTE-Uu communications), WLAN (802.1 1- based protocols and standards), LWA, LAA, Multefire, 5G NR (New- Radio), legacy communication standards (e.g., 2G/3G standards), and so forth. The communication scenarios identified herein may according to some aspects allow for mixing of one or more RATs on communication links between vehicles or other V2X enabled nodes (e.g., 1002-1020), depending on the capability of infrastructure and vehicular devices. [00130] In some aspects, a device may identify communication links to neighboring devices of high importance, based on various factors, such as proximity, message content, or any other context information (e.g., map application data pertaining to a vehicular environment). The device may then detect when a link is not reliable and provide mechanisms to improve reliability for important links. In some aspects, the device may maintain a list— or other appropriate data staicture such as a tree, dictionary, array, matrix, etc.— of links, associated with one or more neighboring devices within a certain range, in storage or in a central location of a list of hypothetical receivers within range of that device. The list may be updated periodically or when a new neighboring device is detected within range of the device. In some aspects, the device may utilize the list and various other methods to improve the quality or reliability of a communication link, for example a communication link to a neighboring device. In an aspect, the device may receive the list from another source, such as a central directory or other devices.

[00131] FIG. 11 illustrates an exemplary internal configuration of a vehicular terminal device 1100 according to some aspects described herein. Referring to FIG. 11, vehicular terminal device 1 00 may include a steering and movement system 1 125, a radio communication system 1 121 , and an antenna system 1123. The internal components of vehicular terminal device 1 100 may be arranged or enclosed within a vehicular housing, such as an automobile body, plane or helicopter fuselage, boat hull, or similar type of vehicular body dependent on the type of vehicle that vehicul ar terminal device 1100 is. As an example, FIG. 1 1 illustrates the vehicular terminal device 1100 as a vehicle (which may be an example of vehicles such as vehicles 1028-1040 in FIG. 10) including a vehicle body 1102, tires 1104- 1106, different types of lamps such as headlamps 1108-11 10, front shield 1 1 12, one or more side windows 1 1 14, rear window 1116, exterior rearview mirror 1118, and the like.

[00132] Vehicular terminal device 1 100 may further include one or more radio terminal devices (e.g., UEs) 1 120-1122, which may form the radio communication system 1121. The radio communication system 1121 may be configured to implement one or more different RATs.

Furthermore, a plurality of sensors 1124, 1126, 1 128, 1130, 1 132, 1134, 1136, and 1138 may be installed in the vehicular terminal device 1100.

[00133] Examples of sensors 1 124 to 1 138 may include one or more of the following sensors (it is to be noted that any other type of sensor may be provided and not all of the following sensors need to be provided): a distance sensor (e.g. a radar sensor), such as distance sensor 324; a camera, such as camera 326; a water/rain sensor, such as rain sensor 328; a tire sensor (e.g., an air pressure sensor), such as tire sensors 330-332; an airbag sensor such as airbag sensor 334; an exhaust gas sensor, such as exhaust gas sensor 336; and a temperature sensor, such as temperature sensor 338. Furthermore, one or more controllers or actuators may be provided in the vehicular terminal device 1100, such as a speed controller, an air condition controller, a brake controller, an airbag trigger controller, and so forth.

[00134] In some aspects, one or more processors 1 140 (e.g., hardware processors, processing circuitry, microprocessors, central processing units (CPUs), etc.) may be provided and may be

communicatively coupled to some or all of the sensors 1 124-1138 and to the radio communication system 1121 as well as to some or all of the controllers or actuators. The coupling may be wired, wireless or optical. In an example, the one or more processors 1 140 may be part of the radio communication system 1 121.

[00135] Thus, by way of example, sensors 1 24 to 1 138 may be configured to detect respective physical quantity and to generate a corresponding quantity value representing the detected physical quantity and may forward the same to processor 1140, which may be configured to process the quantity values received from the plurality of sensors 1124- 1138 and may supply the processing results to the terminal devices 1 120- 1 122. The terminal devices 1 120-1122 may be configured to generate and transmit radio messages to other terminal devices or base stations, for example. Furthermore, terminal devices 1120-1 122 may be configured to receive and decode radio messages from other terminal devices or base stations, for example, and to forward respective instructions to the one or more processors 1140. The one or more processors 1140 may he configured to generate respective control signals or messages and to transmit the same to the controllers or actuators. An exemplary structure of the radio communication system 1 121 (which includes the terminal devices 120 and 1122) is illustrated in FIG. 12 and FIG. 13.

[00136] In order to help ensure that both incoming and outgoing data is received and transmitted properly with a selected network access node or other terminal device, e.g., according to a wireless standard or a proprietary standard, or a mix thereof, a terminal device may also receive control information that provides control information or parameters. The control parameters may include, for example, time and frequency scheduling information, coding/modulation schemes, power control information, paging information, retransmission information, connection/mobility information, or other such information that defines how and when data is to be transmitted and received. Terminal devices may then use the control parameters to control data transmission and reception with the network access node or other terminal device, thus enabling the terminal device to successfully exchange user and other data traffic with the network access node or other terminal device over the wireless connection. The network access node may interface with an underlying communication network (e.g., a core network) that may provide a terminal device with data including voice, multimedia (e.g., audio/video/image), internet or other web-browsing data, etc., or provide access to other applications and services, e.g., using cloud technologies.

[00137] A terminal device may be configured to operate on at least one RAT of a plurality of RATs. A terminal device configured to operate on a plurality of R ATs (e.g., the first and second R ATs) may be configured in accordance with the wireless protocols of both the first and second RATs and optionally in addition in accordance with a wireless protocol of a third RAT (and likewise for operation on additional RATs). For example, LTE network access nodes (e.g., base stations) may transmit discovery and control information in a different format (including the type/contents of information, modulation and coding scheme, data rates, etc.) with different time and frequency scheduling (including periodicity, center frequency, bandwidth, duration, etc.) than Wi-Fi network access nodes (e.g., WLAN APs). Consequently, a terminal device designed for both LTE and Wi-Fi operation may operate according to the specific LTE protocols in order to properly receive LTE discovery and control information, and may also operate according to the specific Wi-Fi protocols in order to properly receive Wi-Fi discovery and control information. Terminal devices configured to operate on other radio access networks, such as UMTS, GSM, Bluetooth, 5G, and others, may likewise be configured to transmit and receive radio signals according to the corresponding individual access protocols. In some aspects, terminal devices may have dedicated hardware or software component corresponding to each supported RAT.

[00138] In some aspects, the steering and movement system 1125 may include components of vehicular terminal device 1 100 related to steering and movement of the vehicular terminal device. In aspects where vehicular terminal device 1 100 is an automobile, the steering and movement system 1125 may include wheels and axles, an engine, a transmission, brakes, a steering wheel, associated electrical circuitry and wiring, and any other components used in the driving of an automobile. In aspects where the vehicular terminal device 1100 is an aerial vehicle, the steering and movement system 1125 may include one or more of rotors, propellers, jet engines, wings, rudders or wing flaps, air brakes, a yoke or cyclic, associated electrical circuitry and wiring, and any other components used in the flying of an aerial vehicle. In aspects where the vehicular terminal device 1 100 is an aquatic or sub-aquatic vehicle, the steering and movement system 1125 may include any one or more of rudders, engines, propellers, a steering wheel, associated electrical circuitry and wiring, and any other components used in the steering or movement of an aquatic vehicle. In some aspects, the steering and movement system 1 125 may also include autonomous driving functionality, and accordingly may also include a central processor configured to perform autonomous driving computations and decisions and an array of sensors for movement and obstacle sensing. The autonomous driving components of the steering and movement system 1125 may also interface with the radio communication system 1121 to facilitate communication with other nearby vehicular terminal devices or central networking components that perform decisions and computations for autonomous driving,

[00139] The radio communication system 1121 and the antenna system 1 123 may be configured to perform one or more radio

communication functionalities of the vehicular terminal device 1100, which may include transmitting and receiving communications with a radio communication network or transmitting and receiving communications directly with other vehicular terminal devices and other communication devices. For example, the radio communication system 1121 and the antenna system 1123 may be configured to transmit and receive communications with one or more network access nodes, such as, in the demonstrative context of D SRC and LTE V2V/V2X, RSUs and evolved Node-Bs (base stations). In some aspects, the communication system 1121 may include a plurality of radios (e.g., with a plurality of transceivers), which may be configured to communicate simultaneously using one or more RATs (e.g., simultaneous communication using multiple links, e.g., on one or more mmWave and/or cmWave bands) and one or more antenna arrays (or sub-arrays or a single multi -array antenna, such as a MIMO antenna array).

[00140] FIG. 12 illustrates an exemplary internal configuration of a radio communication system of the vehicular terminal device of FIG. 11 according to some aspects described herein. Referring to FIG. 12, the radio communication system 1121 may include a radio frequency (RF) transceiver 1202, a digital signal processor (DSP) 1204, and a controller 1206.

[00141] Although not explicitly shown in FIG. 12, in some aspects, the radio communication system 1 121 may further include one or more additional hardware or software components (such as

processors/microprocessors, controllers/microcontrollers, other specialty or generic hardware/processors/circuits, etc.), peripheral device(s), memory, power supply, external device interface(s), subscriber identity module(s) (SIMs), user input/output devices (display(s), keypad(s), touchscreen(s), speaker(s), external button(s), camera(s), microphone(s), etc.), or other related components.

[00142] The controller 1206 may comprise suitable circuitry, logic, interfaces or code and may be configured to execute upper-layer protocol stack functions. The DSP 1204 may comprise suitable circuitry, logic, interfaces or code and may be configured to perform physical layer (PHY) processing. The RF transceiver 1202 may be configured to perform RF processing and amplification related to transmission and reception of wireless RF signals via the antenna system 1123.

[00143] The antenna system 1 123 may include a single antenna or an antenna array with multiple antennas. The antenna system 1123 may additionally include analog antenna combination or beamforming circuitry. In the receive (RX) path, the RF transceiver 1202 may be configured to receive analog RF signals from the antenna system 1123, and perform analog and digital RF front-end processing on the analog RF signals to produce digital baseband samples (e.g., In-Phase/Quadrature (IQ) samples) to provide to the DSP 1204. In some aspects, the RF transceiver 1202 may include analog and digital reception components, such as amplifiers (e.g., a Low Noise Amplifiers (LNAs)), filters, RF demodulators (e.g., RF IQ demodulators)), and analog-to-digital converters (ADCs), which the RF transceiver 1202 may utilize to convert the received RF signals to digital baseband samples.

[00144] In the transmit (TX) path, the RF transceiver 1202 may be configured to receive digital baseband samples from the DSP 1204, and to perform analog and digital RF front-end processing on the digital baseband samples to produce analog RF signals to provide to antenna system 1123 for wireless transmission. In some aspects, the RF transceiver 1202 may include analog and digital transmission components, such as amplifiers (e.g., Power Amplifiers (PAs), filters, RF modulators (e.g., RF IQ modulators), and digital-to-analog converters (DACs) to mix the digital baseband samples received from a baseband modem, which the RF transceiver 1202 may use to generate the analog RF signals for wireless transmission by the antenna system 1 23.

[00145] The DSP 1204 may be configured to perform physical layer

(PHY) transmission and reception processing to, in the transmit path, prepare outgoing transmit data provided by controller 1206 for transmission via RF transceiver 1202, and, in the receive path, to prepare incoming received data provided by the RF transceiver 1202 for processing by the controller 1206. The DSP 1204 may be configured to perform one or more of error detection, forward error correction encoding/decoding, channel coding and interleaving, channel modulation/demodulation, physical channel mapping, radio measurement and search, frequency and time synchronization, antenna diversity processing, power control and weighting, rate matching/de-matching, retransmission processing, interference cancelation, and any other physical layer processing functions.

[00146] The DSP 1204 may include one or more processors configured to retrieve and execute program code that defines control and processing logic for physical layer processing operations. In some aspects, the DSP 1204 may be configured to execute processing functions with software via the execution of executable instructions. In some aspects, the DSP 1204 may include one or more dedicated hardware circuits (e.g., ASICs, FPGAs, and other hardware) that are digitally configured to specifically execute processing functions, where the one or more processors of the DSP 1204 may offload certain processing tasks to these dedicated hardware circuits, which may be referred to as hardware accelerators. Exemplary hardware accelerators may include Fast Fourier Transform

(FFT) circuits and encoder/decoder circuits. In some aspects, the processor and hardware accelerator components of the DSP 1204 may be realized as a coupled integrated circuit.

[00147] While the DSP 1204 may be configured to perform lower- layer physical processing functions, the controller 1206 may be configured to perform upper-layer protocol stack functions. The controller 1206 may include one or more processors configured to retrieve and execute program code that defines the upper-layer protocol stack logic for one or more radio communication technologies, which may include Data Link Layer/Layer 2 and Network Layer/Layer 3 functions. In an example, the upper layer protocol stack may include a V2X convergence function associated with functionalities performed by one or more radios within the RF transceiver 1202 or a V2X convergence function layer that is common to one or more of the radios within the RF transceiver 1202. In some aspects, the DSP 1204 or the controller 1206 may perform one or more of the functions performed by the processor 1 140 (FIG. 11).

[00148] The controller 1206 may be configured to perform both user-plane and control-plane functions to facilitate the transfer of application layer data to and from the radio communication system 1121 according to the specific protocols of one or more supported radio communication technologies. User-plane functions may include header compression and encapsulation, security, error checking and correction, channel multiplexing, scheduling and priority, while the control-plane functions may include setup and maintenance of radio bearers. The program code retrieved and executed by the controller 1206 may include executable instructions that define the logic of such functions,

[00149] In some aspects, the controller 1206 may be

communicatively coupled to an application processor, which may be configured to handle the layers above the protocol stack, including the transport and application layers. The application processor may be configured to act as a source for some outgoing data transmitted by the radio communication system 1 121, and a sink for some incoming data received by the radio communication system 1 121 . In the transmit path, the controller 1206 may be configured to receive and process outgoing data provided by the application processor according to the layer-specific functions of the protocol stack, and provide the resulting data to the DSP 1204. The DSP 1204 may be configured to perform physical layer processing on the received data to produce digital baseband samples, which the DSP may provide to the RF transceiver 1202. The RF transceiver 1202 may be configured to process the digital baseband samples to convert the digital baseband samples to analog RF signals, which the RF transceiver 1202 may wirelessly transmit via the antenna system 1123. In the receive path, the RF transceiver 1202 may be configured to receive analog RF signals from the antenna system 1 123 and process the analog RF^' signal to obtain digital baseband samples. The RF transceiver 1202 may be configured to provide the digital baseband samples to the DSP 1204, which may perform physical layer processing on the digital baseband samples. The DSP 1204 may then provide the resulting data to the controller 1206, which may process the data according to the layer-specific functions of the protocol stack and provide the resulting incoming data to the application processor.

[00150] In some aspects, the radio communication system 1 121 may be configured to transmit and receive data according to multiple radio communication technologies and/or multiple communication bands.

Accordingly, in some aspects, one or more of the antenna system 1123, the RF transceiver 1202, the DSP 1204, and the controller 1206 may include separate components or instances dedicated to different radio

communication technologies or unified components that are shared between different radio communication technologies.

[00151] In some aspects, the RF transceiver 1202 may include separate RF circuitry sections dedicated to different respective radio communication technologies or multiple bands of the same radio technology, or RF circuitry sections shared between multiple radio communication technologies. In some aspects, the separate RF circuitry sections dedicated to different radio communication technologies may be interfaced to each other via a common V2X convergence layer or via separate V2X convergence functions associated with each RF circuitry section.

[00152] In some aspects, the antenna system 1123 may include separate antennas dedicated to different respective radio communication technologies, or antennas shared between multiple radio communication technologies, or separate antennas dedicated to different communication bands of the same radio technology. Accordingly, while the antenna system 1 123, the RF transceiver 1202, the DSP 1204, and the controller 206 are shown as individual components in FIG. 2, in some aspects the antenna system 1 123, the RF transceiver 1202, the DSP 1204, or the controller 1206 may encompass separate components dedicated to different radio communication technologies.

[00153] FIG. 13 illustrates exemplary transceivers using multiple radio communication technologies in the vehicular terminal device of FIG. 1 1 according to some aspects described herein. Referring to FIG. 13, the RF transceiver 1302 may include an RF transceiver 1302 A for a first radio communication technology, an RF transceiver 1302B for a second radio communication technology, and an RF transceiver 1302C for a third radio communication technology. In some aspects, the transceivers 1302A- 1302C can be configured to communicate in multiple bands of the same radio access technology (e.g., mmWave and cmWave communication bands). Similarly, the DSP 1304 may include a DSP 1304A for the first radio communication technology, a DSP 1304B for the second radio communication technology, and a DSP 1304C for the third radio communication technology. Similarly, the controller 1306 may include a controller 1306 A for the first radio communication technology, a controller 1306B for the second radio communication technology, and a controller 1306C for the third radio communication technology.

[00154] In some aspects, the radio communication technologies may, for example, include a dedicated short-range communication (DSRC) radio communication technology, a wireless access vehicular environment (WAVE) radio communication technology, a Bluetooth radio

communication technology, an IEEE 802, 1 radio communication technology (e.g., Wi-Fi), an LTE radio communication technology, and a 5G radio communication technology.

[00155] The RF transceiver 1302 A, the DSP 1304A, and the controller 1306 A may form a communication arrangement (e.g., the hardware and software components dedicated to a particular radio communication technology) for the first radio communication technology (or first communication band). The RF transceiver 1302B, the DSP 1304B, and the controller 1306B may form a communication arrangement for the sseeccoonndd rraaddiioo ccoommmmuunniiccaattiioonn tteecchhnnoollooggyy ((oorr aa sseeccoonndd ccoommmmuunniiccaattiioonn bbaanndd)).. TThhee R RFF ttrraannsscceeiivveerr 11330022CC,, tthhee DDSSPP 11330044CC,, aanndd tthhee c coonnttrroolllleerr 11330066CC mmaayy ffoorrmm aa ccoommmmuunniiccaattiioonn aarrrraannggeemmeenntt ffoorr tthhee tthhiirrdd rraaddiioo ccoommmmuunniiccaattiioonn tteecchhnnoollooggyy ((oorr aa tthhiirrdd ccoommmmuunniiccaattiioonn bbaanndd)).. WWhhiillee 55 ddeeppiicctteedd aass bbeeiinngg llooggiiccaallllyy sseeppaarraattee iinn FFIIGG.. 1133,, aannyy ccoommppoonneennttss ooff tthhee ccoommmmuunniiccaattiioonn aarrrraannggeemmeennttss mmaayy bbee iinntteeggrraatteedd iinnttoo aa ccoommmmoonn

ccoommppoonneenntt..

[[0000115566]] WWiitthh ccoonnttiinnuueedd rreeffeerreennccee ttoo FFIIGG.. 1144--FFIIGG.. 2244,, oonnee oorr mmoorree ooff tthhee rreeffeerreenncceedd hhaannddhheelldd ddeevviicceess ((ee..gg..,, U UEEss)),, vveehhiiccuullaarr ddeevviicceess oorr ootthheerr

1100 VV22XX--eennaabblleedd ddeevviicceess ((ee..gg..,, RRSSUUss)) mmaayy bbee ccoonnffiigguurreedd ssiimmiillaarrllyy ttoo tthhee

vveehhiiccuullaarr tteerrmmiinnaall ddeevviiccee 11 110000 aass sshhoowwnn aanndd ddeessccrriibbeedd iinn rreeffeerreennccee ttoo FFIIGG.. 1 11 -- FFIIGG.. 1133 oorr aannyy ooff tthhee FFIIGGSS.. 11--1100.. DDeevviicceess iilllluussttrraatteedd oorr ddeessccrriibbeedd iinn rreeffeerreennccee ttoo FFIIGGSS.. 1144--2244 mmaayy bbee ccoonnfifigguurreedd ttoo ttrraannssmmiitt aanndd rreecceeiivvee rraaddiioo ssiiggnnaallss uussiinngg oonnee oorr mmoorree ccoommmmuunniiccaattiioonn lliinnkkss aassssoocciiaatteedd wwiitthh aatt lleeaasstt oonnee

1155 RRAATT ooff mmuullttiippllee RRAATTss,, aanndd rreepprreesseennttiinngg ccoommmmuunniiccaattiioonn ddaattaa aaccccoorrddiinngg ttoo oonnee oorr mmoorree vveehhiiccuullaarr rraaddiioo ccoommmmuunniiccaattiioonn tteecchhnnoollooggiieess,, ssuucchh aass DDSSRRCC,, WWAAVVEE,, BBlluueettooootthh,, WWii--FFii,, LLTTEE,, aanndd//oorr 55GG..

[[0000115577]] FFIIGG.. 1144 iilllluussttrraatteess aa tteerrmmiinnaall

band/multi-channel operation in multiple directions in accordance with 20 some aspects. Referring to FIG. 14, there is illustrated a terminal device 1402 (e.g., a vehicle). The terminal device 1402 may be configured for multi-band multi-channel operation. For example, the terminal device 1402 can include multiple transceivers coupled to an antenna array, where each transceiver can be configured to operate in one or more bands of a radio 25 access technology in a communication band spectrum 1410 (e.g., from 3 GHz to 300 GHz). In some aspects, a first transceiver 1412 can be configured to operate in a first communication band 1408, and a second transceiver 1414 can be configured to operate in a second communication band 1404. In some aspects, a third transceiver 1416 can be configured to 30 operate in a third communication band 1406. In some aspects, the first communication band 1408 can be a communication band below 6 GHz, and the second and third communication bands 1404 and 1406 can include a communication band above 6 GHz (e.g., 63 GHz). In some aspects, the second and third transceivers can be located at different locations within the terminal device so that directional communication using multiple communication links above 6 GHz can be achieved.

[00158] In some aspects, the communication at the first

communication band 1408 (e.g., below 6 GHz, such as 5.9 GHz) can use 10-20 MHz or above (e.g. up to 100 MHz) bandwidth. In some aspects, the communication at the second and third communication bands 1404 and 1406 (e.g., above 6 GHz, such as 63 GHz) can use can use bandwidth of approximately 1 GHz or other bandwidths (e.g. 400, 500, 1000, 2000 MHz). In this regard, since communications using transceivers 1414 and 1416 use highly directional high data rates communications, such transceivers can be disposed at different locations within the terminal device (e.g. as seen in FIG. 14 or at other locations, such as on top of a rooftop, at bumper level, at side mirrors, etc.).

[00159] In some aspects, emerging eV2X services can utilize cooperative message exchange to reliably share large amount of data at ultra-low latency. The reliable eV2X communication should be supported for various communication ranges and ensure efficient resource utilization to operate in dense scenarios. The following design concepts can be used for NR eV2X systems,

[00160] The synchronized multi-band/multi-channel operation can further increase eV2X NR system reliability. The communication links at high carrier frequencies may not be reliable due to channel blockage or obstruction and can suffer from the reduced communication range. At high carrier frequency, the reliable connection may often be possible only with rear and front vehicles. From eV2X service perspective, it is often desirable to communicate with other vehicles in the same lane. The relaying solution can serve this purpose, however it may cause additional protocol latency and may not be efficient at high bands especially for transmission of the short control messages. The alternative way to extend coverage is to utilize communication at low band (e.g., below 6GHz, such as 5.9 GHz), which is less sensitive to propagation path obstruction. The broadcast transmissions in low band can be also used for control plane signaling to assist communication at high carrier frequency. For instance, the geo-location information update among vehicles may be done at low carrier frequency and applied for connection establishment at the high band. In this regard, the benefits of dual band communications can be considered for NR eV2X system design. In some aspects, geo-location information of the source and destination nodes can be used to tune antenna beams so that they can point directly towards each other and establish high data rate reliable links at, e.g., higher band communications (e.g., communication links above 6 GHz, such as 63 GHz).

[00161] FIG. 15 illustrates a terminal device configured for multi- band/multi-channel operation in accordance with some aspects. Referring to FIG. 15, there is illustrated a terminal device 1502 (e.g., a vehicle). The terminal device 1502 may be configured for multi-band multi-channel operation. For example, the terminal device 1502 can include multiple transceivers coupled to an antenna array, where each transceiver can be configured to operate in one or more bands of a radio access technology (e.g., 5G radio access technology). In some aspects, a first transceiver can be configured to operate in a first communication band 1502 for communication with another terminal device 506 (e.g., eNB), which can be a low data rate communication band (e.g., below 6 GHz, such as 5.9 GHz). In some aspects, a second transceiver can be configured to operate in a second communication band 1504, which can be a high data rate communication band (e.g., above 6 GHz, such as 63 GHz).

[00162] In some aspects, more robust control PHY can be used for operation at high carrier frequencies. However, this approach can be associated with reduced spectral efficiency given that multiple repetitions may be needed to overcome the propagation loss due to lack of directional antenna gains.

[00163] In some aspects, synchronized multi-band multi-channel operation can be configured at low and high frequency bands using one or more of the following techniques. In some aspects, the terminal device 1500 can be configured for multi-band multi-channel eV2X NR

communication on sidelink (e.g. transceivers supporting dual band sidelink communication at 5.9 GHz and 63 GHz with another terminal device). In some aspects, the terminal device 1500 can be configured to use low band communications (e.g., at 5.9 GHz) as a control plane to assist radio layer communications in a high band communication link. In some aspects, the terminal device 1500 can be configured to use multi-band multi-channel operation to discover neighboring terminal devices (e.g., neighboring vehicles). For example, directionality of one or more high data rate communication links (e.g., above 6 GHz) can be used to discover devices in the vicinity of the terminal device 1500.

[00164] In some aspects, the terminal device 1500 can be configured to exchange geo-location information between communication nodes using sidelink communication on a low data rate communication link or a high data rate communication link. In some aspects, the terminal device 1500 can be configured to exchange control signaling information for radio resource management, where the radio resources can include time, frequency or spatial (beam) or code (signal) or polarization resources for control or data signaling. In some aspects, the terminal device 1500 can be configured to perform multi-antenna array beamforming at the TX and/or RX sides of the source and destination vehicle by utilizing geo-location information of the TX and RX antennas operating at high band, and sidelink communication at low band to assist beamforming in high band. In some aspects, the terminal device 1500 can be configured for multichannel operation at low bands for load balancing.

[00165] FIG. 16 illustrates terminal devices using geo-location information for radio resource management, such as selection of radio resource for transmission/scheduling, in accordance with some aspects. Referring to FIG. 16, there is illustrated a communication environment 1600, which includes terminal devices (e.g., vehicles) 1606, 1608, 1610, and 1612. In some aspects, communication resources can be divided between the terminal devices in a frequency division multiplexing scheme 1602, where each terminal device can communicate on a specific frequency band. In some aspects, communication resources can be divided between the terminal devices in a time division multiplexing scheme 1604, where each terminal device can communicate within a frequency range at a given time. In some aspects, a combination of time and frequency division multiplexing can be used as another option of operation and using communication resources.

[00166] In some aspects, one or more of the terminal devices 1606 -

1612 can be configured for utilization of vehicle geo-location information. Autonomous driving applications can be used for exchanging geo-location information between the terminal devices, such as kinematic, telemetry and/or sensor information among vehicles (e.g., vehicle speed vector information indicating vehicle speed and travel direction, as well as vehicle current location). From radio-layer perspective, the geo-location information can be used for radio-resource management to improve reliability of sidelink-based V2X communication (e.g., as seen in FIG. 16). Under sufficient amount of spectrum resources, the spatial reuse principle can provide reliable V2V communication across large communication ranges (if spatial isolation range is sufficient). In some aspects of LTE V2V design, the geo-location information can be used to determine subset of time-frequency resources (associated with certain geographical area) available for selection at the transmitting vehicle. For NR eV2X design, when the transmitting vehicle selects resource for transmission, the vehicle may also utilize geo-location information of neighboring vehicles, competing for resources. In addition, the availability of more precise geo- location information can be used to assist in radio-resource management and provide spatial isolation for broadcast / groupcast / unicast V2X communication.

[00167] In some aspects, one or more of the terminal devices 1606 -

1612 can be configured to use geo-location information in connection with one or more of the following techniques. In some aspects, vehicle geo- location information can be used to improve reliability of NR. eV2X sidelink communications. In some aspects, the geo-location information of neighboring vehicles can be used for radio-resource selection and management including resource scheduling. For example, geolocation information exchanged using low data rate communication links (e.g., communication links at frequencies below 6 GHz) can be used to assess the density of the communication environment. Additionally, vehicle velocity vector information can be used to improve sensing and radio-resource selection by sharing subset of resources by vehicles moving in the same direction. For example and in reference to FIG. 16, terminal devices 1606 can determine that terminal device 1608 is traveling in the same direction, and spectral resources can be divided between terminal devices 1606 and 1608 based on such common direction of travel. In some aspects, a terminal device (or an eNB) can execute spectrum control functionalities and can apportion or allocate spectrum to individual terminal devices based on device density of the communication environment 1600.

[00168] In some aspects, vehicle geo-location information as exchanged using one or more low data rate communication links (e.g., one or more communication links at frequencies below 6 GHz, such as 5.9 GHz) can be used for spatial beam (or antenna port) or demodulation reference signal selection, and to improve communication on one or more high data rate communication links. In some aspects, vehicle geo-location information can be used for advanced relaying techniques and intelligent message forwarding (e.g., as seen in reference to FIG. 17).

[00169] FIG. 17 illustrates terminal devices using geo-location information for radio layer relaying in accordance with some aspects. Referring to FIG. 17, there is illustrated a communication environment 1700 with communications taking place between terminal devices 1702 - 1710.

[00170] In some aspects, autonomous radio-layer relaying solutions can be used to improve V2V communication performance. For example, relaying techniques within the communication environment 1700 can be used to provide extended coverage range, which can address link budget challenges in multiple eV2X scenarios. In some aspects, spectrum sensing based and/or geo-location based transmission schemes can be used in connection with radio-layer relaying techniques to provide extended V2V communication range and higher reliability even in communication scenarios with present interference. In some aspects, the utilization of vehicle geo-location information can be used to enable intelligent radio- layer relaying protocols, that can perform multi-hop forwarding of vehicle messages taking into account geo-location information of the source vehicles (e.g. geographical distance or radio distance between source and relay node).

[00171] Referring to FIG. 17, terminal device 1702 can be a relaying device. In one aspect, terminal device 1708 can be the transmitting device and terminal device 1706 can be the receiving device. Terminal device 1702 can use low data communication links with terminal devices 1706 and 1708 to exchange geo-location information and determine distances between the three devices. Based on the distance, e.g. between device 1706 and 1708, relaying device 1702 can determine that no relaying of data (e.g. data communicated on one or more high data rate communication links, such as links at frequencies above 6 GHz) is necessary. In some aspects, when terminal devices are located within a certain distance from the relaying terminal device 1 702, terminal devices can be considered within a "no relaying" zone, as indicated in FIG. 17.

[00172] In some aspects, terminal device 1710 can be the transmitting device, and terminal device 1704 can be the receiving device. Based on geo-location information exchanged between the relaying device 1702 and the terminal devices 1704 and 1710 using one or more low data rate communication links, the ruling device 1702 can determine that relaying of data communicated on one or more high data rate

communication links from terminal device 1710 is necessary (when terminal devices 1704 and 1710 are located outside a predetermined range from the relaying device 1702, terminal devices 1704 and 1710 can be considered located within a "relaying region" as indicated in FIG. 17).

[00173] FIG. 18 illustrates terminal devices using a combination of sensing-based radio resource selection and radio layer relaying in accordance with some aspects. In some aspects, radio-layer relaying can be combined with sensing-based radio-resource selection. For example, a terminal device can use a sensing procedure to select a set of resources for broadcast transmissions, and use part of the selected resources for transmission of its own packet, while another part of the selected resources can be used for forwarding packets (or sub-packet) received from other terminal devices (or linear combination of packets from one or more other terminal devices). In some aspects, at each packet forwarding hop, optimal radio resource can be selected and, therefore, data packets can be more reliably propagated to larger distances. In some aspects, terminal devices can be configured to perform sensing of the resource grid of available resources, receive a plurality of packets, and retransmit only the packets (or sub-packets) that have not been retransmitted by other vehicles.

[00174] Referring to FIG. 18, there is illustrated a resource grid 1800 which can be a representation of spectrum (e.g., time, frequency, frame, etc.) that is available for communication using low data rate (e.g. at frequencies below 6 GHz) and/or high data rate communication links (e.g. at frequencies above 6 GHz). Terminal devices 1802 - 1810 can perform sensing to detect available communication resources associated with the resource grid 1800, In some aspects, a terminal device can receive a first data communication using a first type of communication link (e.g. a low data rate communication link), and transmit a second data communication (or relay the first data communication) using another communication link of the first type or a second type (e.g., a high data rate communication link). In some aspects, a terminal device can be configured to

simultaneously receive a first data communication on a first communication link while transmitting a second data communication on a second communication link.

[00175] A first terminal device 1802 can use a first resource Rl to transmit a data message to terminal device 1804. Terminal device 1804 can be configured to receive the transmission from terminal device 1802 using spectral resource Rl, while transmitting its own transmission using second available resource R2. Terminal device 1802 can receive the data transmission from terminal device 1804 using available resource R2, and then relay the received transmission from terminal device 1804 to another terminal device using a third available resource R3. In this regard, terminal device 1804 can be configured to transmit a data communication on a second available resource R2 to terminal device 1802, while terminal device 1802 can be configured to forward the received communication from device 1804 or communication from another device (or a combination of its own communication and communication received from another device), onto a third terminal device using the third available

communication resource R3.

[00176] FIG. 19 illustrates terminal devices using network coding principles for V2V radio layer relaying in accordance with some aspects. In some aspects, the reliability and radio-resource utilization efficiency of V2V communication can be further improved if network coding principles are applied at V2V radio-layers for broadcast communication. More specifically, a relaying terminal device (or node) can forward a

combination of received packets or sub-packets, so that terminal devices can dispatch/relay the data packets that have not been successfully received yet, by utilizing packets that were already successfully received. Referring to FIG. 19, the communication environment 1900 can include a plurality of terminal devices 1902 - 1910, with terminal device 1906 being a relaying device. More specifically, terminal device 1906 can receive a data message S I from terminal device 1902, and a data message asked two from terminal device 1910. Terminal device 1906 can then apply a network coding function (e.g., a logical function such as XOR, a linear combination function, or another type of function) to generate a combined message S3. The combined message S3 can then be relayed to one or more of the remaining terminal devices 1902, 1904, 1908, and 1910. In this regard, a single combined message can be used by individual terminal devices to decode packets or sub-packets of data transmissions from other terminal devices. The above techniques and principles can be applied not only to shared channel transmissions (e.g., physical sideiink shared channel, or PSSCH transmissions), but can also be applicable to control channel transmissions (e.g., physical sideiink control channel, or PSCCH, transmissions). The later (PSCCH transmissions) can be utilized to reduce hidden node problem in sensing and resource selection procedures used for data transmissions. [00177] In some aspects, network coding and relaying can be applied jointly with geo-location information, so that packets received from opposite sides of the relaying node 1906 can be propagated more efficiently. For example, geolocation information can be exchanged using a low data rate communication link, while the combined message can be communicated using a high data rate communication link.

[00178] In some aspects, different schemes of advanced radio layer relaying can benefit V2V communication performance and thus can be a design component for 3 GPP NR-V2X design.

[00179] In some aspects, the following multi-hop radio-layer relaying in low and/or high frequency bands can be used in a V2X communication environment. More specifically, the following radio-layer relaying techniques can be used to improve reliability, radio-resource utilization and increase V2V communication range in noise and

interference limited scenarios. In some aspects, geo-location information communicated on low data rate links can be used for multi-hop radio-layer relaying based on relative geographical or radio distance between the source vehicle and the relay vehicle. In some aspects, combination of multi-hop radio-layer relaying with sensing based principle can be used for selecting an optimal radio resource for transmission (e.g., utilizing the spectral resource associated with minimal interference or noise energy). In some aspects, combination of multi-hop radio-layer relaying can be used with sensing-based resource selection, exchange of geo-location information, and network coding principles for generating a combined message for subsequent relaying and communication. In some aspects, sensing-based radio-resource selection can be used for data forwarding with increased reliability.

[00180] In some aspects, various multi-antenna technologies can be used in eV2X communications. The system design options can based on distributed antenna systems when directional antennas or multi-antenna arrays are deployed in multiple locations within a terminal device (e.g., at least in front and rear sides of a vehicle), which can provide additional degree of spatial filtering and thus improve reliability of V2V links against interference as well as increase link budget. In some aspects, vehicle distributed antenna systems (VDAS) can operate independently in terms of baseband processing or can be under the control of common baseband processing unit. Multi-antenna technologies can be useful at high carrier frequency bands (e.g. at frequencies above 6 GHz, such as 63 GHz), where high data rate communication links can be established between neighboring terminal devices. The multi-antenna technology can also benefit V2V communications at lower frequency bands (e.g., low data rate

communication bands at frequencies below 6 GHz) by increasing spectrum efficiency of V2V communication links.

[00181] A challenges for multi-antenna technology at high carrier frequencies can include TX-RX beam tuning to establish reliable communication link between a transmitter and a receiver. The TX-RX beam tuning can be a challenging procedure, especially in instances when communication with multiple vehicles needs to be supported (e.g., broadcast communication). The TX and RX beam sweeping across multiple terminal devices (e.g., vehicles) may impose significant overhead on overall system performance especially if broadcast type of

communication is considered. In some aspects, in order to reduce system overhead on beam training, the geo-location information of the TX and RX antennas can be used to assist physical link establishment. In some instances when coordinates of both TX and RX antenna arrays are available, the beam adjustment can be based on geo-location information. This possibility can be especially useful for communication with RSUs, so that vehicle TX and RX beams can be autonomously adjusted based on the travel distance between the RSU and the transmitting vehicle. The geo- location information can be also used for antenna selection/ switching.

[00182] In some aspects, in order to increase data rate on vehicle links, the multi-layer communication can be analyzed. Although it may be not always be feasible to use multiple spatial layers due to line-of-sight (LOS) propagation channel between vehicles, it may still be possible to utilize polarization to deliver multiple streams or utilize multiple spatial layers for communication with different vehicles. [00183] In some aspects, multi-antenna technologies and distributed antenna systems can be used in a V2X communication environment. More specifically, multi-antenna technologies and vehicle distributed antenna systems can include multi-layer V2V communications, full duplex communications with simultaneous transmit and receive functions from antennas installed in front and rear sides of the vehicle, beamforming to reduce system overhead for establishment of directional unicast

communication links between vehicles or between vehicle and RSUs/g Bs, and so forth.

[00184] In some aspects, advanced receiver techniques can be used for eV2X communications. The V2V communication in UE-autonomous or gNB-controlled mode can be limited by co-channel interference due to multiple channel access nature, hidden node problems, or due to dense V2V deployment scenarios. In order to improve V2V system performance in such environments, successive interference cancellation (SIC) receivers can be used in connection with blind retransmission techniques. In some aspects, receivers utilizing joint detection of several vehicles- muti-user detection (MUD) using the same radio-resource can be used to improve reliability of V2V communications. The SIC receivers can be applied in combination with multiple retransmissions of the same message by the source or relaying nodes. In some aspects, the following advanced receiver techniques with multiple blind retransmissions can be used in connection with the V2X communications: advanced SIC receivers utilizing joint demodulation of multiple sources at the same radio resource; joint detection of multiple transmitters or successive interference cancellation receivers in combination with blind HARQ retransmissions; and multiple access schemes in combination with sensing-based resource selection or geo- location based transmission schemes.

[00185] In some aspects, V2X communication techniques disclosed herein can use broadcast, groupcast, and/or unicast communication links using a low data rate and/or high data rate communications. One of the examples of groupcast eV2X communication is platooning, which assumes message exchange among platoon members (i.e., a set of vehicles moving in the same direction). From higher layer perspective, platoon application may be configured so that a lead vehicle controls platoon operation, including radio resource control, communications spectrum detection, spectrum assignment, spectrum reassignment, and so forth (i.e., localized radio-resource management by a lead vehicle for reliable groupcast V2V communications). In some aspects, communication flow control and spectrum resources can be pre-scheduled, which may be based on radio resource management by one of the members in the platoon group of terminal devices.

[00186] A Half-duplex and in-band emission problems are other challenges for eV2X communications in a UE autonomous mode. In some aspects, system level solutions such as re-transmissions and relaying, can be used to reduce the half-duplex issues. However, considering that half- duplex probability is optimally low in order to meet reliability criteria, the TDM centric resource allocation option may be a more preferable for eV2X communication at short range requiring high reliability. The TDM centric resource allocation (e.g., 1604) can also reduce the in-band emission problem. For instance under 20 ms latency target, the amount of time resources may be rather limited at low band, e.g., 80 or 160 resources assuming 60 kHz subcarrier spacing and scaled sub frame or slot based communication respectively. In this case, to reduce half-duplex probability, multiple time resources can be used by a transmitter in order to ensure that probability of foil overlap is below reliability target.

[00187] In some aspects, two types of RSUs can be considered in V2X communications - UE-type RSUs and eNB type RSUs. The UE-type RSU can be used as an application layer logical entity,

[00188] In some aspects, eV2X positioning can be considered during

V2X communications. One of the eV2X system requirement is to ensure accurate vehicle positioning, which can be beyond the accuracy of GNSS- based positioning. In some aspects, 3 GPP systems can support relative lateral position accuracy of at least 0.1 m and relative longitudinal position accuracy of less than 0.5 m for UEs supporting V2X applications in proximity. Since these positioning requirements can be challenging, new system level solutions may be used to achieve these targets. Considering the GNSS or differential GNSS solution as a baseline it may be further possible to improve positioning by utilizing cooperative sidelink based measurements. In some aspects, cooperative positioning approaches can be used, by utilizing sidelink radio-layer measurements to estimate distance between proximate vehicles based on time of flight measurements. In this regard, improvement of GNSS based geo-location capabilities can be achieved in a V2X communication system by applying cooperative localization techniques for more precise vehicle positioning.

[00189] In some aspects, in order to overcome compatibility and interoperability issues which could arise with simultaneous deployments of both NR and LTE technologies and in order to simplify the further transition to eV2X technology, the common design of the sidelink air interface for both NR and LTE systems can be developed for V2V communication, so that it can be used under LTE and NR networks.

[00190] FIG. 20 is a flow diagram illustrating example

functionalities for performing V2X communications in accordance with some aspects. Referring to FIG. 20, the example method 2000 may start at 2002, when geo-location information from a plurality of mobile V2X communication nodes can be decoded. For example and in reference to FIG. 17, terminal device 1702 can receive geo-location information from other terminal devices such as 1704, 1706, 1708, and 1710. The geo- location information can be received via a first transceiver of a plurality of transceivers using a first communication band. For example and in reference to FIG. 14, a first transceiver 1412 can be used to receive the geo- location information using communication links 1408, which can be a communication link at a frequency below or around 6 GHz.

[00191] At 2004, direction of travel for the plurality of mobile V2X communication nodes can be determined based on the velocity vector information. At 2006, a subset of the plurality of mobile V2X

communication nodes that are moving in a same direction as the V2X UE can be determined based on the direction of travel. For example and in reference to FIG. 16, terminal device 1606 can receive velocity vector information from terminal devices 1608, 1612, and 1610, and can determine that terminal device 1608 is traveling in the same direction. At 2008, a resource configuration message can be encoded for transmission by a second transceiver of the plurality of transceivers to the subset of mobile V2X communication nodes, using a second communication band. For example, transceiver 1414 or 4016 within the terminal device 1402 can be used for transmission of the resource configuration message. In some aspects, the resource configuration message can indicate resource scheduling for transmission using the second communication band (e.g., a communication band at a frequency above 6 GHz).

[00192] FIG. 21 illustrates a block diagram of a communication device such as an eNB, a gNB, or a UE, in accordance with some aspects. In alternative aspects, the communication device 2100 may operate as a standalone device or may be connected (e.g., networked) to other communication devices. In a networked deployment, the communication device 2100 may operate in the capacity of a server communication device, a client communication device, or both in server-client network

environments. In an example, the communication device 2100 may act as a peer communication device in peer-to-peer (P2P) (or other distributed) network environment. The communication device 2100 may be a UE, eNB, PC, a tablet PC, a STB, a PDA, a mobile telephone, a smart phone, a web appliance, a network router, switch or bridge, or any communication device capable of executing instructions (sequential or otherwise) that specify actions to be taken by that communication device. Further, while only a single communication device is illustrated, the term "communication device" shall also be taken to include any collection of communication devices 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.

[00193] Examples, as described herein, may include, or may operate on, logic or a number of components, modules, or mechanisms. Modules are tangible entities (e.g., hardware) capable of performing specified operations and may be configured or arranged in a certain manner. In an example, circuits may be arranged (e.g., internally or with respect to external entities such as other circuits) in a specified manner as a module. In an example, the whole or part of one or more computer systems (e.g., a standalone, client or server computer system) or one or more hardware processors may be configured by firmware or software (e.g., instructions, an application portion, or an application) as a module that operates to perform specified operations. In an example, the software may reside on a communication device readable medium. In an example, the software, when executed bv the underlying hardware of the module, causes the hardware to perform the specified operations.

[00194] Accordingly, the term "module" is understood to encompass a tangible entity, be that an entity that is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., transitorily) configured (e.g., programmed) to operate in a specified manner or to perform part or all of any operation described herein. Considering examples in which modules are temporarily configured, each of the modules need not be instantiated at any one moment in time. For example, where the modules comprise a general-purpose hardware processor configured using software, the general-purpose hardware processor may be configured as respective different modules at different times. Software may accordingly configure a hardware processor, for example, to constitute a particular module at one instance of time and to constitute a different module at a different instance of time.

[00195] Communication device (e.g., UE) 2100 may include a hardware processor 2102 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 2104 and a static memory 2106, some or all of which may communicate with each other via an interlink (e.g., bus) 2108. The communication device 2100 may further include a display unit 21 10, an alphanumeric input device 2112 (e.g., a keyboard), and a user interface (UI) navigation device 21 14 (e.g., a mouse). In an example, the display unit 2110, input device 2112 and UI navigation device 2114 may be a touch screen display. The communication device 2100 may additionally include a storage device (e.g., drive unit) 2116, a signal generation device 2118 (e.g., a speaker), a network interface device 2120, and one or more sensors 2121, such as a global navigation satellite system (GNSS) sensor, compass, accelerometer, or other sensor. The communication device 2 00 may include an output controller 2128, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).

[00196] The storage device 2116 may include a communication device readable medium 2122 on which is stored one or more sets of data structures or instructions 2124 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions 2124 may also reside, completely or at least partially, within the main memory 2104, within static memory 2106, or within the hardware processor 2102 during execution thereof by the communication device 2100. In an example, one or any combination of the hardware processor 2102, the main memory 2104, the static memory 2106, or the storage device 21 16 may constitute communication device readable media.

[00197] While the communication device readable medium 2122 is illustrated as a single medium, the term "communication device readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions 2124.

[00198] The term "communication device readable medium" may include any medium that is capable of storing, encoding, or carrying instructions for execution by the communication device 2100 and that cause the communication device 2100 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions. Non-limiting communication device readable medium examples may include solid-state memories, and optical and magnetic media. Specific examples of communication device readable media may include: non- volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; Random Access Memory (RAM); and CD-ROM and DVD-ROM disks. In some examples, communication device readable media may include non-transitory communication device readable media. In some examples, communication device readable media may include communication device readable media that is not a transitor propagating signal.

[00199] The instructions 2124 may further be transmitted or received over a communications network 2126 using a transmission medium via the network interface device 2120 utilizing any one of a number of transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc. ), Example communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks (e.g., cellular networks), Plain Old Telephone (POTS) networks, and wireless data networks (e.g., Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as Wi-Fi®, IEEE 802.16 family of standards known as WiMax©), IEEE 802.15.4 family of standards, a Long Term Evolution (LTE) family of standards, a Universal Mobile Telecommunications System (UMTS) family of standards, peer-to-peer (P2P) networks, among others. In an example, the network interface device 2120 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas to connect to the communications network 2126. In an example, the network interface device 2120 may include a plurality of antennas to wirelessly communicate using at least one of single-input multiple-output (SIMO), MIMO, or multiple-input single-output (MISO) techniques. In some examples, the network interface device 2120 may 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 communication device 2100, and includes digital or analog

communications signals or other intangible medium to facilitate

communication of such software,

[00200] Additional notes and examples:

[00201] Example 1 is an apparatus of vehicle-to-everything (V2X) user equipment (V2X UE), the apparatus comprising: processing circuitry arranged to: configure a first transceiver of a plurality of transceivers to receive geo-location information from a plurality of mobile V2X communication nodes, via a first communication link in a first

communication band, perform a sensing procedure to determine a set of available candidate radio resources for transmission, determine a distance to the plurality of V2X communication nodes and a signal strength characteristic for each of the plurality of V2X communication nodes, based on the received geo-location information; select a subset of V2X communication nodes from the plurality of V2X communication nodes based on the determined distance being within a threshold distance and the determined signal strength characteristic for each of the plurality of V2X communication nodes being within a threshold signal strength; and configure a second transceiver of the plurality of transceivers to

communicate a data message originating from a first V2X communication node of the subset of V2X communication nodes for relaying u sing a first subset of the available candidate radio resources for a second

communication link in a second communication band that is non- overlapping with the first communication band; and memory coupled to the processing circuitry and arranged to store the threshold distance and the threshold signal strength.

[00202] In Example 2, the subject matter of Example 1 includes, wherein the processing circuitry is arranged to: configure the second transceiver to communicate an original data message of the V2X UE using a second subset of the available candidate radio resources for the second communication link. [00203] In Example 3, the subject matter of Example 2 includes, wherein the processing circuitry is arranged to: configure the second transceiver to communicate a linear combination of the data message originating from the first V2X communication node and the original data message of the V2X LIE using one of the first subset and the second subset of the available candidate radio resources for the second communication link.

[00204] In Example 4, the subject matter of Examples 1-3 includes, wherein the processing circuitry is arranged to: determine a latency characteristic of the data message originating from the first V2X

communication node, and configure the second transceiver of the plurality of transceivers to communicate the data message when the latency characteristic is within a predetermined latency boundary.

[00205] In Example 5, the subject matter of Examples 2-4 includes, wherein the data message is for transmission to a second V2X

communication node of the subset of V2X communication nodes, and wherein the processing circuitry is arranged to: generate beamforming coefficients based on a portion of the geo-location information associated with the second V2X communication node; and configure the second transceiver to communicate the data message or the original data message to the second V2X communication node using an antenna array and based on the beamforming coefficients.

[00206] In Example 6, the subject matter of Examples 1-5 includes, wherein the first communication band is a centimeter wave (cmWave) communication band, and the second communication band is a millimeter wave (mmWave) communication band.

[00207] In Example 7, the subject matter of Examples 1-6 includes, wherein the first communication band is associated with a frequency below or around 6 GHz, and the second communication band is associated with a frequency above 6 GHz.

[00208] In Example 8, the subject matter of Examples 1-7 includes, an antenna array with a plurality of multiple-input-multiple-output (MIMO) antennas coupled to the plurality of transceivers. [00209] In Example 9, the subject matter of Example 8 includes, wherein: the first transceiver is configured to communicate with the plurality of V2X communication nodes using the first communication link and a first subset of the MIMO antennas; and the second transceiver is configured to communicate with the second V2X communication node using the second communication link and a second subset of the MIMO antennas.

[00210] In Example 10, the subject matter of Examples 1-9 includes, wherein the first communication link comprises control plane signaling for the second communication link, and the second communication link comprises one or both of user plane signaling and control plane signaling.

[00211] In Example 11, the subject matter of Examples 1-10 includes, wherein the V2X communication nodes comprise an evolved Node-B (eNB), a next generation Node-B (gNB), or a roadside unit (RSU).

[00212] In Example 12, the subject matter of Examples 1-1 1 includes, wherein the processing circuitry is arranged to: decode configuration messages from one or more of the plurality of mobile V2X communication nodes, the configuration message received via the first communication link and including radio resource management information.

[00213] In Example 13, the subject matter of Example 12 includes, wherein the processing circuitry is arranged to: configure the second transceiver to transmit the data message to a second V2X communication node of the subset of V2X communication nodes using time and frequency resources specified by the radio resource management information, the time and frequency resources including a set of physical resource blocks and slots/subframes,

[00214] In Example 14, the subject matter of Example 13 includes, wherein radio resource management information comprises: a descriptor of the time and frequency resources used for transmission of control and shared channel information, the shared channel information comprising data retransmissions; and a descriptor of at least one physical layer parameter used for transmission, the at least one physical layer parameter including a demodulation reference signal (DMRS) sequence, a beam index, a modulation and coding scheme (MSG) index, a precoder index, TX/RX antenna coordinates, and antenna orientation.

[00215] In Example 15, the subject matter of Examples 1-14 includes, wherein the geo-location information includes: velocity vector information; and current location information relative to a reference point or absolute information.

[00216] In Example 16, the subject matter of Example 1 5 includes, wherein the processing circuitry is arranged to: determine direction of travel for the plurality of mobile V2X communication nodes based on the velocity vector information; and determine based on the direction of travel, a subset of the plurality of mobile V2X communication nodes that are moving in a same direction as the V2X UE.

[00217] In Example 17, the subject matter of Example 16 includes, wherein the processing circuitry is arranged to: configure the second transceiver of the plurality of transceivers to communicate the data message to the second V2X communication node using time and frequency resources that are common with the subset of the plurality of mobile V2X communication nodes moving in the same direction.

[00218] In Example 18, the subject matter of Examples 1-17 includes, wherein the processing circuitry is arranged to: configure the first transceiver to receive configuration information from the plurality of mobile V2X communication nodes via the first communication link, the configuration information including node discovery information; and determine node density information for the plurality of mobile V2X communication nodes based on the node discovery information.

[00219] In Example 19, the subject matter of Example 18 includes, wherein the processing circuitry is arranged to: select a time and frequency resource for communicating the data message to a second V2X

communication node of the subset of V2X communication nodes based on the node density information.

[00220] In Example 20, the subject matter of Examples 1-19 includes, receiver circuitry configured to: perform joint detection of the multiple V2X communication nodes of the plurality of V2X

communication nodes, the multiple V2X communication nodes transmitting using a same subset of the available candidate radio resources for transmission; and receive the data message originating from the first V2X communication node based on the joint detection.

[00221] In Example 21, the subject matter of Example 20 includes, wherein the receiver circuitry comprises a successive interference cancellation (SIC) receiver,

[00222] Example 22 is an apparatus of vehicle-to-everything (V2X) user equipment (V2X UE), the apparatus comprising: processing circuitry arranged to: perform a sensing procedure to detect a set of available candidate radio resources for transmission; configure a first transceiver of a plurality of transceivers to receive geo-location information from a plurality of mobile V2X communication nodes, via a first communication link in a first communication band, and determine a distance to each of the V2X communication nodes; select a subset of V2X communication nodes from the plurality of V2X communication nodes based on the determined distance being within a first threshold distance; configure a second transceiver of the plurality of transceivers to receive a data message from a first mobile V2X communication node of the subset of V2X

communication nodes, using a second communication link in a second communication band that is non-overlapping with the first communication band and a first subset of the available candidate radio resources, the data message indicating a second mobile V2X communication node as a recipient; determine a distance between the first V2X communication and the second V2X communication node based on the received geo-location information; and configure the second transceiver to relay the data message to the second V2X communication node when the determined distance is above a second threshold distance, using the second communication link and a second subset of the available candidate resources; and memory coupled to the processing circuitry and arranged to store the first and second threshold distances.

[00223] In Example 23, the subject matter of Example 22 includes, wherein the processing circuitry is arranged to: encode a second data message for transmission to a third mobile V2X communication node of the plurality of mobile V2X communication nodes, using the second communication link and the first subset of the available candidate radio resources.

[00224] In Example 24, the subject matter of Examples 22-23 includes, wherein the processing circuitry is arranged to: decode a third data message received from a third mobile V2X communication node of the plurality of V2X mobile communication nodes, via the second

communication link; and generate a combined data message based on the data message and the third data message.

[00225] In Example 25, the subject matter of Example 24 includes, wherein the processing circuitry is arranged to: configure the second transceiver to relay the combined data message to at least the second V2X communication node when the determined distance is above the second threshold distance, using the second communication link and the second subset of the available candidate radio resources.

[00226] In Example 26, the subject matter of Examples 24-25 includes, wherein the processing circuitry is arranged to: apply one of a logical function or a linear combination function to the data message and the third data message to generate the combined message,

[00227] In Example 27, the subject matter of Examples 22-26 includes, wherein the first communication band is a centimeter wave

(cmWave) communication band, and the second communication band is a millimeter wave (mmWave) communication band,

[00228] In Example 28, the subject matter of Examples 22-27 includes, wherein the first communication band is associated with a frequency below or about 6 GHz, and the second communication band is associated with a frequency above 6 GHz,

[00229] In Example 29, the subject matter of Examples 22-28 includes, an antenna array with a plurality of multiple-input-multiple-output (ΜΪΜΌ) antennas coupled to the plurality of transceivers.

[00230] In Example 30, the subject matter of Example 29 includes, wherein the processing circuitry is arranged to: configure the first transceiver to communicate with the plurality of V2X communication nodes using the first communication link and a first subset of the MIMO antennas; and configure the second transceiver to communicate with the first and second V2X communication nodes using the second

communication link and a second subset of the MIMO antennas.

[00231] In Example 31, the subject matter of Examples 29-30 includes, wherein the processing circuitry is arranged to: configure the first transceiver to receive the geo-location information using a first subset of the MIMO antennas, while the second transceiver is transmitting the data message to the second V2X communication node using a second subset of the MIMO antennas.

[00232] Example 32 is a computer-readable storage medium that stores instructions for execution by one or more processors of a vehicle-to- everything (V2X) user equipment (V2X UE), the one or more processors to configure the V2X UE to: decode geo-location information from a plurality of mobile V2X communication nodes, the geo-location information received via a first transceiver of a plurality of transceivers using a first communication band, determine direction of travel for the plurality of mobile V2X communication nodes based on the velocity vector information; determine based on the direction of travel, a subset of the plurality of mobile V2X communication nodes that are moving in a same direction as the V2X UE; and encode a resource configuration message for transmission by a second transceiver of the plurality of transceivers to the subset of mobile V2X communication nodes, using a second

communication band, the resource configuration message indicating resource scheduling for transmission using the second communication band.

[00233] In Example 33, the subject matter of Example 32 includes, wherein the one or more processors further configure the V2X UE to: decode a first data message from a first mobile V2X communication node of the subset of V2X communication nodes, the first data message received by the second transceiver using a first time and frequency resource of the second communication band; and decode a second data message from a second mobile V2X communication node of the subset of V2X

communication nodes, the second data message received by the second transceiver using a second time and frequency resource of the second communication band. [00234] In Example 34, the subject matter of Example 33 includes, wherein the second transceiver is configured to receive the first data message and the second data message while operating in a time division multiplexing (TDM) scheme.

[00235] In Example 35, the subject matter of Examples 33-34 includes, wherein the one or more processors further configure the V2X UE to: communicate with the first mobile V2X communication node of the subset of V2X communication nodes to receive the first data message via a communication interface compatible with both the first communication band and the second communication band.

[00236] In Example 36, the subject matter of Examples 32-35 includes, wherein subcarrier spacing associated with the first time and frequency resource and the second time and frequency resource of the second communication band is allocated based on the TDM scheme.

[00237] In Example 37, the subject matter of Examples 32-36 includes, wherein the first and second time and frequency resources are indicated by the resource configuration message.

[00238] In Example 38, the subject matter of Examples 32-37 includes, wherein the one or more processors further configure the V2X UE to: determine secondary location information for the first and second mobile V2X communication nodes using time of flight information associated with the first and second data messages; and adjust the geo- iocation information associated with the first and second mobile V2X communication nodes based on the secondary location information.

[00239] In Example 39, the subject matter of Examples 32-38 includes, wherein the first communication band is a centimeter wave (cmWave) communication band, and the second communication band is a millimeter wave (mmWave) communication band.

[00240] In Example 40, the subject matter of Examples 32-39 includes, wherein the first communication band is associated with a frequency below 6 GHz, and the second communication band is associated with a frequency above 6 GHz.

[00241] Example 41 is an apparatus of a vehicle-to-everything

(V2X) user equipment (V2X UE), the apparatus comprising: means for decoding geo-location information from a plurality of mobile V2X communication nodes, the geo-iocation information received via a first transceiver of a plurality of transceivers using a first communication band; means for determining direction of travel for the plurality of mobile V2X communication nodes based on the velocity vector information; means for determining based on the direction of travel, a subset of the plurality of mobile V2X communication nodes that are moving in a same direction as the V2X UE; and means for encoding a resource configuration message for transmission by a second transceiver of the plurality of transceivers to the subset of mobile V2X communication nodes, using a second

communication band, the resource configuration message indicating resource scheduling for transmission using the second communication band.

[00242] In Example 42, the subject matter of Example 41 includes, means for decoding a first data message from a first mobile V2X communication node of the subset of V2X communication nodes, the first data message received by the second transceiver using a first time and frequency resource of the second communication band; and means for decoding a second data message from a second mobile V2X

communication node of the subset of V2X communication nodes, the second data message received by the second transceiver using a second time and frequency resource of the second communication band,

[00243] In Example 43, the subject matter of Example 42 includes, wherein the second transceiver is configured to receive the first data message and the second data message while operating in a time division multiplexing (TDM) scheme,

[00244] In Example 44, the subject matter of Examples 42-43 includes, means for communicating with the first mobile V2X

communication node of the subset of V2X communication nodes to receive the first data message via a communication interface compatible with both the first communication band and the second communication band.

[00245] In Example 45, the subject matter of Examples 41-44 includes, wherein subcarrier spacing associated with the first time and frequency resource and the second time and frequency resource of the second communication band is allocated based on the TDM scheme.

[00246] In Example 46, the subject matter of Examples 41-45 includes, wherein the first and second time and frequency resources are indicated by the resource configuration message.

[00247] In Example 47, the subject matter of Examples 41-46 includes, means for determining secondary location information for the first and second mobile V2X communication nodes using time of flight information associated with the first and second data messages; and means for adjusting the geo-location information associated with the first and second mobile V2X communication nodes based on the secondary location information.

[00248] In Example 48, the subject matter of Examples 41-47 includes, wherein the first communication band is a centimeter wave

(cm Wave) communication band, and the second communication band is a millimeter wave (mmWave) communication band.

[00249] In Example 49, the subject matter of Examples 41- 8 includes, wherein the first communication band is associated with a frequency below 6 GHz, and the second communication band is associated with a frequency above 6 GHz.

[00250] Example 50 is at least one machine-readable medium including instructions that, when executed by processing circuitry, cause the processing circuitry to perform operations to implement of any of Examples 1-49.

[00251] Example 51 is an apparatus comprising means to implement of any of Examples 1-49,

[00252] Example 52 is a system to implement of any of Examples 1-

49.

[00253] Example 53 is a method to implement of any of Examples 1-49.

[00254] Various modifications and changes may be made to aspects described herein without departing from the broader scope of the present disclosure. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. The accompanying drawings that form a part hereof show, by way of illustration, and not of limitation, specific embodiments in which the subject matter may be practiced. The embodiments illustrated are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other embodiments may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. This Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled.

[00255] Aspects and examples described herein may be referred to, individually and/or collectively, merely for convenience and without intending to voluntarily limit the scope of this application to any single aspect or inventive concept if more than one is in fact disclosed. Thus, although specific aspects have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific aspects shown. This disclosure is intended to cover any and all adaptations or variations of various aspects. Combinations of the above aspects, and other aspects not specifically described herein, will be apparent to those of skill in the art upon reviewing the above description.

[00256] The Abstract of the Disclosure is provided to allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it can be seen that various features are grouped together in a single aspect for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed aspects require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed aspect. Thus the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate aspect.

Claims

What is claimed is:

1. An apparatus of vehicle-to-everything (V2X) user equipment (V2X UE), the apparatus comprising:

processing circuitry arranged to:

configure a first transceiver of a plurality of transceivers to receive geo-location information from a plurality of mobile V2X communication nodes, via a first communication link in a first communication band;

perform a sensing procedure to determine a set of available candidate radio resources for transmission;

determine a distance to the plurality of V2X communication nodes and a signal strength characteristic for each of the plurality of V2X communication nodes, based on the received geo-location information;

select a subset of V2X communication nodes from the plurality of V2X communication nodes based on the determined distance being within a threshold distance and the determined signal strength characteristic for each of the plurality of V2X

communication nodes being within a threshold signal strength, and configure a second transceiver of the plurality of

transceivers to communicate a data message originating from a first V2X communication node of the subset of V2X communication nodes for relaying using a first subset of the available candidate radio resources for a second communication link in a second communication band that is non-overlapping with the first communication band; and

memory coupled to the processing circuitry and arranged to store the threshold distance and the threshold signal strength.

2. The apparatus of claim 1, wherein the processing circuitry is arranged to:

configure the second transceiver to communicate an original data message of the V2X UE using a second subset of the available candidate radio resources for the second communication link.

3. The apparatus of claim 2, wherein the processing circuitry is arranged to:

configure the second transceiver to communicate a linear combination of the data message originating from the first V2X

communication node and the original data message of the V2X UE using one of the first subset and the second subset of the available candidate radio resources for the second communication link. 4. The apparatus of any of claims 1-3, wherein the processing circuitry is arranged to:

determine a latency characteristic of the data message originating from the first V2X communication node; and

configure the second transceiver of the plurality of transceivers to communicate the data message when the latency characteristic is within a predetermined latency boundary.

5. The apparatus of claim 2, wherein the data message is for transmission to a second V2 X communication node of the subset of V2X communication nodes, and wherein the processing circuitry is arranged to: generate beamforming coeffi cients based on a portion of the geo- iocation information associated with the second V2X communication node; and

configure the second transceiver to communicate the data message or the original data message to the second V2X communication node using an antenna array and based on the beamforming coefficients. 6, The apparatus of any of claims 1-3, wherein the first

communication band is a centimeter wave (cmWave) communication band, and the second communication band is a millimeter wave (mmWave) communication band.

7, The apparatus of any of claim s 1-3, wherein the fi rst

communication band is associated with a frequency below or around 6 GHz, and the second communication band is associated with a frequency above 6 GHz,

8, The apparatus of any of claims 1-3, further comprising an antenna array with a plurality of multiple-input-multiple-output (MEMO) antennas coupled to the plurality of transceivers. 9, The apparatus of claim 8, wherein:

the first transceiver is configured to communicate with the plurality of V2X communication nodes using the first communication link and a first subset of the MIMO antennas, and

the second transceiver is configured to communicate with the second V2X communication node using the second communication link and a second subset of the MIMO antennas.

10. The apparatus of any of claims 1-3, wherein the first

communication link comprises control plane signaling for the second communication link, and the second communication link comprises one or both of user plane signaling and control plane signaling.

1 1. The apparatus of any of claims 1-3, wherein the V2X

communication nodes comprise an evolved Node-B (eNB), a next generation Node-B (gNB), or a roadside unit (RSU).

2. The apparatus of any of claims 1-3, wherein the processing circuitry is arranged to:

decode configuration messages from one or more of the plurality of mobile V2X communication nodes, the configuration message received via the first communication link and including radio resource management information,

13. The apparatus of claim 12, wherein the processing circuitry is arranged to:

configure the second transceiver to transmit the data message to a second V2X communication node of the subset of V2X communication nodes using time and frequency resources specified by the radio resource management information, the time and frequency resources including a set of physical resource blocks and slots/subframes.

14. The apparatus of claim 13, wherein radio resource management information comprises:

a descriptor of the time and frequency resources used for transmission of control and shared channel information, the shared channel information comprising data retransmissions, and

a descriptor of at least one physical layer parameter used for transmission, the at least one physical layer parameter including a demodulation reference signal (DMRS) sequence, a beam index, a modulation and coding scheme (MSC) index, a precoder index, TX/RX antenna coordinates, and antenna orientation. 5. The communication device of any of claims 1-3, wherein the geo- iocation information includes:

velocity vector information; and

current location information relative to a reference point or absolute information.

16. The apparatus of claim 15, wherein the processing circuitry is arranged to:

determine direction of travel for the plurality of mobile V2X communication nodes based on the velocity vector information; and

determine based on the direction of travel, a subset of the plurality of mobile V2X communication nodes that are moving in a same direction as the V2X UE.

17. The apparatus of claim 16, wherein the processing circuitry is arranged to:

configure the second transceiver of the plurality of transceivers to communicate the data message to the second V2X communication node using time and frequency resources that are common with the subset of the plurality of mobile V2X communication nodes moving in the same direction.

An apparatus of vehicle-to-everything (V2X) user equipment (V2X the apparatus comprising:

processing circuitry arranged to:

perform a sensing procedure to detect a set of available candidate radio resources for transmission;

configure a first transceiver of a plurality of transceivers to receive geo-iocation information from a plurality of mobile V2X communication nodes, via a first communication link in a first communication band, and determine a distance to each of the V2X communication nodes;

select a subset of V2X communication nodes from the plurality of V2X communication nodes based on the determined distance being within a first threshold distance;

configure a second transceiver of the plurality of transceivers to receive a data message from a first mobile V2X communication node of the subset of V2X communication nodes, using a second communication link in a second communication band that is non-overlapping with the first communication band and a first subset of the available candidate radio resources, the data message indicating a second mobile V2X communication node as a recipient;

determine a distance between the first V2X communication and the second V2X communication node based on the received geo-location information; and

configure the second transceiver to relay the data message to the second V2X communication node when the determined distance is above a second threshold distance, using the second

communication link and a second subset of the available candidate resources; and

memory coupled to the processing circuitry and arranged to store the first and second threshold distances,

19. The apparatus of claim 18, wherein the processing circuitry is arranged to:

encode a second data message for transmission to a third mobile V2X communication node of the plurality of mobile V2X communication nodes, using the second communication link and the first subset of the available candidate radio resources.

20. The apparatus of any of claims 18-19, wherein the processing circuitry is arranged to:

decode a third data message received from a third mobile V2X communication node of the plurality of V2X mobile communication nodes, via the second communication link; and

generate a combined data message based on the data message and the third data message.

21. The apparatus of claim 20, wherein the processing circuitry is arranged to:

configure the second transceiver to relay the combined data message to at least the second V2X communication node when the determined distance is above the second threshold distance, using the second communication link and the second subset of the available candidate radio resources.

22. The apparatus of claim 20, wherein the processing circuitry is arranged to:

apply one of a logical function or a linear combination function to the data message and the third data message to generate the combined message.

23. A computer-readable storage medium that stores instructions for execution by one or more processors of a vehicle-to-everything (V2X) user equipment (V2X UE), the one or more processors to configure the V2X UE to:

decode geo-location information from a plurality of mobile V2X communication nodes, the geo-location information received via a first transceiver of a plurality of transceivers using a first communication band; determine direction of travel for the plurality of mobile V2X communication nodes based on the velocity vector information;

determine based on the direction of travel, a subset of the plurality of mobile V2X communication nodes that are moving in a same direction as the V2X UE, and

encode a resource configuration message for transmission by a second transceiver of the plurality of transceivers to the subset of mobile V2X communication nodes, using a second communication band, the resource configuration message indicating resource scheduling for transmission using the second communication band.

24. The computer-readable storage medium of claim 23, wherein the one or more processors further configure the V2X UE to:

decode a first data message from a first mobile V2X communication node of the subset of V2X communication nodes, the first data message received by the second transceiver using a first time and frequency resource of the second communication band; and

decode a second data message from a second mobile V2X communication node of the subset of V2X communication nodes, the second data message received by the second transceiver using a second time and frequency resource of the second communication band.

25. The computer-readable storage medium of claim 24, wherein the second transceiver is configured to receive the first data message and the second data message while operating in a time division multiplexing (TDM) scheme.