High reliability communications for vehicle-to-everything (v2x) systems over sidelink and radio network link interfaces

Abstract

Certain aspects of the present disclosure provide techniques for wireless communications in vehicle-to-everything (V2X) systems. An example method generally includes receiving, by a serving network entity from a user equipment (UE), a request for information from a V2X application server, where the request includes an indication of a type of requested information and a location of the UE; identifying one or more parameters for transmitting the requested information to the UE via a transmitter UE; and transmitting, by the transmitter UE to the serving network entity, the requested information for transmission to the UE based on the identified parameters.

Description

Technical Field

[0001] Various aspects of this disclosure relate to wireless communication, and more specifically, to techniques for reliable communication within a vehicle-to-everything (V2X) system using both sidelink and network link interfaces. Background Technology

[0002] Wireless communication systems are widely deployed to provide a variety of telecommunications services, such as telephone, video, data, messaging, and broadcasting. These wireless communication systems can employ multiple access technologies that enable communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, etc.). Examples of such multiple access systems include, to name a few, 3GPP Long Term Evolution (LTE) systems, LTE-A Advanced systems, Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.

[0003] In some examples, a wireless multiple access communication system may include multiple base stations (BSs), each capable of simultaneously supporting communication with multiple communication devices, or user equipment (UEs). In LTE or LTE-A networks, a group of one or more base stations may define an eNodeB (eNB). In other examples (e.g., in next-generation, new radio (NR) or 5G networks), a wireless multiple access communication system may include multiple distributed units (DUs) (e.g., edge units (EUs), edge nodes (ENs), radio heads (RHs), smart radio heads (SRHs), transmit-receive points (TRPs), etc.) communicating with multiple central units (CUs) (e.g., central nodes (CNs), access node controllers (ANCs), etc.), wherein a group of one or more DUs communicating with the CUs may define access nodes (e.g., which may be referred to as BSs, 5G NBs, next-generation NodeBs (gNBs or gNodeBs), transmit-receive points (TRPs), etc.). A BS or DU may communicate with a group of UEs on downlink channels (e.g., for transmissions from the BS or DU to the UE) and uplink channels (e.g., for transmissions from the UE to the BS or DU).

[0004] These multiple access technologies have been adopted in various telecommunications standards to provide a common protocol enabling different wireless devices to communicate at the city, national, regional, and even global levels. NR (e.g., New Radio or 5G) is an example of an emerging telecommunications standard. NR is a set of enhancements to the LTE mobile standard issued by 3GPP. NR aims to better support mobile broadband internet access by improving spectrum efficiency, reducing costs, improving service, utilizing new spectrum, and using OFDMA with a cyclic prefix (CP) on both the downlink (DL) and uplink (UL) to better integrate with other open standards. To this end, NR supports beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.

[0005] Sidelink communication is communication from one UE to another. With the continued increase in demand for mobile broadband access, there is a need for further improvements to NR and LTE technologies, including improvements to sidelink communication. Preferably, these improvements should be applicable to other multiple access technologies and telecommunications standards that employ these technologies. Summary of the Invention

[0006] The systems, methods, and apparatus of this disclosure each have several aspects, and no single aspect is solely responsible for its desired properties. Without limiting the scope of this disclosure as set forth in the appended claims, some features will now be briefly discussed. After considering this discussion, and especially after reading the section entitled "Detailed Description," one will understand how the features of this disclosure provide advantages including improved communication between access points and stations in a wireless network.

[0007] Some aspects provide a method for wireless communication by a vehicle-to-everything (V2X) application server. This method typically includes receiving, via a serving network entity, an information request from a user equipment (UE) to a V2X application server, wherein the request includes an indication of the type of requested information and the location of the UE; identifying one or more parameters for transmitting the requested information to the UE via a transmitter UE; and, based on the identified parameters, transmitting the requested information to the serving network entity via the transmitter UE for transmission to the UE.

[0008] Some aspects provide a method for wireless communication by a receiver user equipment (UE) in a vehicle-to-everything (V2X) system. This method typically includes sending an information request from a V2X application server to a network entity, wherein the request includes an indication of the type of requested information and the location of the UE; and receiving the requested information from a transmitter UE.

[0009] Some aspects provide a method for wireless communication by a transmitter user equipment (UE) in a vehicle-to-everything (V2X) system. The method typically includes receiving from a network entity information requested by a UE connected to the transmitter UE, and one or more parameters for sending the request to the UE; and, based on the one or more parameters, sending the request information to the UE via a sidelink connection between the UE and the transmitter UE.

[0010] Various aspects of this disclosure provide components, apparatus, processors, and computer-readable media for performing the methods described herein.

[0011] To achieve the foregoing and related results, one or more aspects include the features fully described below and specifically pointed out in the claims. The following description and drawings illustrate certain illustrative features of one or more aspects in detail. However, these features only indicate a few of the various ways in which the principles of each aspect can be employed. Attached Figure Description

[0012] To gain a more detailed understanding of the foregoing features of this disclosure, a more specific description of the above brief overview can be provided by referring to various aspects (some of which are illustrated in the accompanying drawings). However, it should be noted that the drawings illustrate only certain typical aspects of this disclosure and should therefore not be considered as limiting its scope, as the description may allow for other equivalent aspects.

[0013] Figure 1 This is a block diagram conceptually illustrating an example telecommunications system according to certain aspects of this disclosure.

[0014] Figure 2 This is a block diagram illustrating an example logical architecture of a distributed radio access network (RAN) according to certain aspects of this disclosure.

[0015] Figure 3 This is a diagram illustrating an example physical architecture of a distributed RAN according to certain aspects of this disclosure.

[0016] Figure 4 This is a block diagram conceptually illustrating the design of an example base station (BS) and user equipment (UE) according to certain aspects of this disclosure.

[0017] Figure 5A and 5B An illustration of an example vehicle-to-everything (V2X) system according to some aspects of this disclosure is shown.

[0018] Figure 6 This disclosure illustrates communication between a vehicle-to-everything (V2X) application server, a roadside unit (RSU), and vehicles in a V2X system via side links and radio network links, according to certain aspects of this disclosure.

[0019] Figure 7 This illustrates the application of Quality of Service (QoS) rules to packets in vehicle-to-everything (V2X) communications in accordance with certain aspects of this disclosure.

[0020] Figure 8 Example operations are shown that, according to certain aspects of this disclosure, can be performed by a vehicle-to-everything (V2X) application server to communicate with a user equipment (UE) via a sidelink connection and a network link connection.

[0021] Figure 9 Example operations are shown that, according to certain aspects of this disclosure, can be performed by a receiver UE to process signals in a vehicle-to-everything (V2X) environment where communication is performed via sidelink and network link connections.

[0022] Figure 10 Example operations are shown that, according to certain aspects of this disclosure, can be performed by a transmitter UE to process signals in a vehicle-to-everything (V2X) environment where communication is performed via sidelink and network link connections.

[0023] Figure 11 An example architecture for communication in a vehicle-to-everything (V2X) environment, which is performed via sidelink and network link connections, is shown according to certain aspects of this disclosure.

[0024] Figure 12 A communication device is shown that may include various components configured to perform operations for use with the techniques disclosed herein in accordance with this disclosure.

[0025] Figure 13 A communication device is shown that may include various components configured to perform operations for use with the techniques disclosed herein in accordance with this disclosure.

[0026] Figure 14 A communication device is shown that may include various components configured to perform operations for use with the techniques disclosed herein in accordance with this disclosure.

[0027] For ease of understanding, the same reference numerals are used where possible to denote the same elements common in the figures. Elements disclosed in one aspect are intended to be usefully applied in other aspects without specific description. Detailed Implementation

[0028] This disclosure provides apparatus, methods, processing systems, and computer-readable media for reliable communication within a vehicle-to-everything (V2X) system using both sidelink and network link interfaces. Typically, a UE (e.g., a vehicle UE) may attempt to receive and decode requested information from a transmitter UE via a sidelink (e.g., PC5) connection. If the UE fails to successfully receive and decode the requested information from the transmitter UE, the UE may request information from a serving network entity via a network link (e.g., Uu) connection. By using both sidelink and network link connections to provide the requested information to the requesting UE, the reliability of communication in a V2X system can be improved.

[0029] The following description provides examples and is not intended to limit the scope, applicability, or examples set forth in the claims. Changes may be made to the function and arrangement of the elements discussed without departing from the scope of this disclosure. Various examples may be appropriately omitted, substituted, or added to various procedures or components. For example, a method may be performed in a different order than described, and various steps may be added, omitted, or combined. Furthermore, features described with respect to some examples may be combined in some other examples. For instance, any number of aspects set forth herein may be used to implement an apparatus or practice a method. Additionally, the scope of this disclosure is intended to cover apparatus or methods practiced using structures, functions, or structures and functions other than or different from the aspects set forth herein. It should be understood that any aspect of what is disclosed herein may be embodied by one or more elements of the claims. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects.

[0030] The technologies described in this article can be used in various wireless communication technologies, such as LTE, CDMA, TDMA, FDMA, OFDMA, SC-FDMA, and other networks. The terms "network" and "system" are often used interchangeably. CDMA networks can implement radio technologies such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includes Wideband CDMA (WCDMA) and other CDMA variants. cdma2000 covers the IS-2000, IS-95, and IS-856 standards. TDMA networks can implement radio technologies such as Global System for Mobile Communications (GSM). OFDMA networks can implement radio technologies such as NR (e.g., 5G RA), Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, etc. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS).

[0031] New Radio (NR) is an emerging wireless communication technology being developed in conjunction with the 5G Technology Forum (5GTF). 3GPP Long Term Evolution (LTE) and LTE-Advanced (LTE-A) are versions of UMTS using E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization called the 3rd Generation Partnership Project (3GPP). cdma2000 and UMB are described in documents from an organization called the 3rd Generation Partnership Project 2 (3GPP2). The technologies described herein can be used in the aforementioned wireless network and radio technologies, as well as other wireless network and radio technologies. For clarity, although terms commonly associated with 3G and / or 4G wireless technologies may be used to describe aspects herein, aspects of this disclosure can be applied to other generation-based communication systems, such as 5G and later technologies, including NR technology.

[0032] New radio (NR) access (e.g., 5G technology) can support a variety of wireless communication services, such as enhanced mobile broadband (eMBB) for wide bandwidth (e.g., 80 MHz or higher), millimeter wave (mmW) for high carrier frequencies (e.g., 25 GHz or higher), massive machine-type communication (mMTC) for non-backward-compatible MTC technologies, and / or mission-critical ultra-reliable low-latency communication (URLLC). These services may have latency and reliability requirements. These services may also have different transmission time intervals (TTIs) to meet their respective quality of service (QoS) requirements. Furthermore, these services may coexist in the same subframe.

[0033] Figure 1 An example wireless communication network 100 in which various aspects of this disclosure can be implemented is shown. For example, Figure 1 The UE120a can be a V2X (vehicle-to-vehicle) or V2V (vehicle-to-vehicle) UE, or include UEs configured to perform the following references. Figures 7-8 The described operation is a V2X or V2V UE for processing signals using a first radio access technology and a second radio access technology in an environment where a device supporting a first radio access technology and a dual-mode device supporting both the first and second radio access technologies coexist.

[0034] like Figure 1 As shown, the wireless communication network 100 may include multiple base stations (BSs) 110a-z (each also individually referred to herein as BS 110 or collectively as BS 110) and other network entities. In various aspects of this disclosure, a roadside service unit (RSU) may be considered a type of BS, and BS 110 may be referred to as an RSU. BS 110 may provide communication coverage for a specific geographic area, sometimes referred to as a "cell," and may be stationary or mobile depending on the location of the mobile BS 110. In some examples, BS 110 may be interconnected with each other and / or with one or more other BSs or network nodes (not shown) in the wireless communication network 100 via various types of backhaul interfaces, such as direct physical connections, wireless connections, virtual networks, etc., using any suitable delivery network. Figure 1 In the example shown, BS 110a, 110b, and 110c can be macro BSs for macro cells 102a, 102b, and 102c, respectively. BS 110x can be a pico BS for pico cell 102x. BS 110y and 110z can be femto BSs for femto cells 102y and 102z, respectively. A BS can support one or more cells. BS 110 communicates with user equipment (UEs) 120a-y (each also individually referred to herein as UE120 or collectively as UE120) in the wireless communication network 100. UEs 120 (e.g., 120x, 120y, etc.) can be distributed throughout the wireless communication network 100, and each UE 120 can be fixed or mobile.

[0035] The wireless communication network 100 may also include a relay station (e.g., relay station 110r), also referred to as a relay station, which receives data and / or other information transmissions from an upstream station (e.g., BS 110a or UE 120r) and transmits data and / or other information transmissions to a downstream station (e.g., UE 120 or BS 110), or relays transmissions between UEs 120 to facilitate communication between devices.

[0036] Network controller 130 can be coupled to a group of BSs 110 and can provide coordination and control for these BSs 110. Network controller 130 can communicate with BSs 110 via backhaul. BSs 110 can also communicate with each other directly or indirectly, for example, via wireless or wired backhaul.

[0037] UEs 120 (e.g., 120x, 120y, etc.) can be distributed throughout the wireless communication network 100, and each UE can be fixed or mobile. A UE can also be referred to as a mobile station, terminal, access terminal, subscriber unit, station, customer premises equipment (CPE), cellular phone, smartphone, personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, laptop computer, cordless phone, wireless local loop (WLL) station, tablet computer, camera, gaming device, netbook, smartbook, ultrabook, appliance, medical device or medical equipment, biosensor / device, wearable device (such as smartwatch, smart clothing, smart glasses, smart bracelet), smart jewelry (e.g., smart ring, smart bracelet, etc.), entertainment device (e.g., music device, video device, satellite radio, etc.), vehicle component or sensor, smart meter / sensor, industrial manufacturing equipment, GPS device, or any other suitable device configured to communicate via wireless or wired media. Some UEs can be considered machine-type communication (MTC) devices or evolved MTC (eMTC) devices. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., which can communicate with the BS, another device (e.g., a remote device), or other entities. For example, a wireless node can provide connectivity to or to a network (e.g., a wide area network such as the Internet or cellular networks) via wired or wireless communication links. Some UEs can be considered Internet of Things (IoT) devices; they can be narrowband IoT (NB-IoT) devices. In some embodiments, Figure 1 The UE shown can be a V2X UE or include those capable of performing the functions discussed below. Figure 7 or Figure 8 The UE vehicle is shown in the operation diagram.

[0038] Some wireless networks (such as LTE) utilize Orthogonal Frequency Division Multiplexing (OFDM) on the downlink and Single-Carrier Frequency Division Multiplexing (SC-FDM) on the uplink. OFDM and SC-FDM divide the system bandwidth into multiple (K) orthogonal subcarriers, which are often referred to as tones, bins, etc. Each subcarrier can be modulated with data. Typically, modulation symbols are transmitted in the frequency domain using OFDM and in the time domain using SC-FDM. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the subcarrier spacing could be 15 kHz, and the minimum resource allocation (called a "resource block" (RB)) could be 12 subcarriers (or 180 kHz). Therefore, for system bandwidths of 1.25, 2.5, 5, 10, or 20 MHz, the nominal Fast Fourier Transform (FFT) size could be equal to 128, 256, 512, 1024, or 2048, respectively. System bandwidth can also be divided into subbands. For example, a subband can cover 1.08MHz (i.e., 6 resource blocks), and there can be 1, 2, 4, 8, or 16 subbands for system bandwidths of 1.25, 2.5, 5, 10, or 20MHz, respectively.

[0039] While the aspects of the examples described herein can be associated with LTE technology, the aspects of this disclosure can be applied to other wireless communication systems, such as NR. NR can use OFDM with CP on both the uplink and downlink, and includes support for half-duplex operation using TDD. Beamforming can be supported, and beam direction can be dynamically configured. MIMO transmission with pre-decoding can also be supported. MIMO configuration in DL can support up to 8 transmit antennas, multi-layer DL transmission of up to 8 streams, and up to 2 streams per UE. Multi-layer transmission of up to 2 streams per UE can be supported. Aggregation of multiple cells with up to 8 serving cells can be supported.

[0040] In some examples, access to the air interface can be scheduled. A scheduling entity (e.g., a BS) allocates resources for communication between some or all devices and apparatuses within its service area or cell. The scheduling entity can be responsible for scheduling, allocating, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communication, subordinate entities utilize the resources allocated by the scheduling entity. A base station is not the only entity that can be used as a scheduling entity. In some examples, a UE can be used as a scheduling entity and can schedule resources for one or more subordinate entities (e.g., one or more other UEs), and other UEs can utilize the resources scheduled by the UE for wireless communication. In some examples, a UE can be used as a scheduling entity in a point-to-point (P2P) network and / or a mesh network. In the mesh network example, in addition to communicating with a scheduling entity, UEs can also communicate directly with each other.

[0041] exist Figure 1 In the diagram, a solid line with a double arrowhead indicates a desired transmission between the UE and the serving BS, which is a BS designated to serve the UE on the downlink and / or uplink. A thin dashed line with a double arrowhead indicates interference transmission between the UE and the BS.

[0042] Figure 2 It shows that it can be used Figure 1 The example logical architecture of the distributed radio access network (RAN) 200 implemented in the wireless communication network 100 shown is illustrated. The 5G access node 206 may include an access node controller (ANC) 202. The ANC 202 may be the central unit (CU) of the distributed RAN 200. The backhaul interface to the next-generation core network (NG-CN) 204 may terminate at the ANC 202. The backhaul interface to the adjacent next-generation access node (NG-AN) 210 may terminate at the ANC 202. The ANC 202 may include one or more TRPs 208 (e.g., cell, BS, gNB, etc.).

[0043] TRP 208 can be a distributed unit (DU). TRP 208 can be connected to a single ANC (e.g., ANC 202) or more ANCs (not shown). For example, for RAN sharing, Radio as a Service (RaaS), and service-specific AND deployments, TRP 208 can be connected to more than one ANC. TRP 208 can each include one or more antenna ports. TRP 208 can be configured to serve the UE's services individually (e.g., dynamically selected) or jointly (e.g., jointly transmitted).

[0044] The logical architecture of this distributed RAN 200 can support fronthaul solutions across different deployment types. For example, the logical architecture can be based on transmit network capabilities (e.g., bandwidth, latency, and / or jitter).

[0045] The logical architecture of this distributed RAN 200 can share features and / or components with LTE. For example, the next-generation access node (NG-AN) 210 can support dual connectivity with NR and can share common fronthaul for LTE and NR.

[0046] The logical architecture of distributed RAN 200 enables cooperation between TRPs 208, for example, within a TRP and / or across TRPs via ANC 202. Inter-TRP interfaces can be omitted.

[0047] Logical functions can be dynamically distributed within the logical architecture of the distributed RAN 200. The Radio Resource Control (RRC) layer, Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, Medium Access Control (MAC) layer, and Physical (PHY) layer can be adaptably placed at the DU (e.g., TRP 208) or CU (e.g., ANC 202).

[0048] Figure 3 An example physical architecture of a distributed RAN 300 according to various aspects of this disclosure is shown. A centralized core network unit (C-CU) 302 can host core network functions. The C-CU 302 can be deployed centrally. Functions of the C-CU 302 may be offloaded (e.g., to Advanced Wireless Services (AWS)) to handle peak capacity.

[0049] The centralized RAN unit (C-RU) 304 can host one or more ANC functions. Optionally, the C-RU 304 can host core network functions locally. The C-RU 304 can be deployed in a distributed manner. The C-RU 304 can be located close to the network edge.

[0050] The DU 306 can host one or more TRPs (Edge Nodes (EN), Edge Units (EU), Radio Headers (RH), Smart Radio Headers (SRH), etc.). The DU can be located at the network edge with radio frequency (RF) capabilities.

[0051] Figure 4 The BS 110a and UE 120a shown are examples of various aspects of this disclosure that can be used to implement the present disclosure. Figure 1 Example components described herein. For example, antenna 452, processors 466, 458, 464 and / or controller / processor 480 of UE 120a, and / or antenna 434, processors 420, 430, 438 and / or controller / processor 440 of BS 110a can be used to perform the functions described herein. Figures 8-10 The various techniques and methods described.

[0052] In BS 110a, the transmit processor 420 can receive data from data source 412 and control information from controller / processor 440. This control information can be used for the Physical Broadcast Channel (PBCH), Physical Control Format Indicator Channel (PCFICH), Physical Hybrid ARQ Indicator Channel (PHICH), Physical Downlink Control Channel (PDCCH), Group Common PDCCH (GC PDCCH), etc. The data can be used for the Physical Downlink Shared Channel (PDSCH), etc. The processor 420 can process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. The processor 420 can also generate reference symbols, for example, for the Primary Synchronization Signal (PSS), Secondary Synchronization Signal (SSS), and Cell-Specific Reference Signal (CRS). The transmit (TX) Multiple-Input Multiple-Output (MIMO) processor 430 can perform spatial processing (e.g., pre-decoding) on ​​the data symbols, control symbols, and / or reference symbols (if applicable), and can provide an output symbol stream to modulators (MODs) 432a to 432t. Each modulator 432 can process its own output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator can further process (e.g., convert to analog, amplify, filter, and up-convert) the output sample stream to obtain a downlink signal. The downlink signal from modulators 432a to 432t can be transmitted via antennas 434a to 434t, respectively.

[0053] At UE 120a, antennas 452a to 452r can receive downlink signals from base station 110a and can provide the received signals to demodulators (DEMODs) in transceivers 454a to 454r respectively. Each demodulator 454 can adjust (e.g., filter, amplify, downconvert, and digitize) the received signal individually to obtain input samples. Each demodulator can further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. MIMO detector 456 can obtain the received symbols from all demodulators 454a to 454r, perform MIMO detection on the received symbols if applicable, and provide the detected symbols. Receiver processor 458 can process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for UE 120a to data sink 460, and provide decoding control information to controller / processor 480.

[0054] On the uplink, at UE 120a, the transmitting processor 464 can receive and process data from data source 462 (e.g., for the Physical Uplink Shared Channel (PUSCH)) and control information from the controller / processor 480 (e.g., for the Physical Uplink Control Channel (PUCCH)). The transmitting processor 464 can also generate reference symbols for reference signals (e.g., for Sounding Reference Signals (SRS)). Symbols from the transmitting processor 464 can be pre-decoded (if applicable) by the TX MIMO processor 466, then further processed by demodulators in transceivers 454a to 454r (e.g., SC-FDM, etc.), and transmitted to base station 110a. At BS 110a, the uplink signal from UE 120a can be received by antenna 434, processed by modulator 432, detected by MIMO detector 436 (if applicable), and further processed by receiving processor 438 to obtain the signal from the UE. The 120a transmits decoded data and control information. The receiver processor 438 can provide the decoded data to the data sink 439 and the decoded control information to the controller / processor 440.

[0055] Controllers / processors 440 and 480 can respectively direct operations at BS 110a and UE 120a. Processor 440 and / or other processors and modules at BS 110a can perform or direct the execution of processes used in the techniques described herein. For example, as Figure 4 As shown, the controller / processor 440 of BS 110a has a V2X communication module 441, which can be configured to receive requests for information from the UE and send the requested information to the transmitter UE and / or the requesting UE. Figure 4 As shown, according to various aspects described herein, the controller / processor 480 of UE 120a has a V2X communication module 481, which can be configured to receive requested information from a V2X application server via one or more sidelink connections or network link connections. Although shown at controller / processor 480 and controller / processor 440, other components of UE 120a and BS 110a can be used to perform the operations described herein. Memory 442 and 482 can store data and program code for BS 110a and UE 120a, respectively. Scheduler 444 can schedule data transmissions for the UE on the downlink and / or uplink.

[0056] In some cases, two or more subordinate entities (e.g., UEs) can communicate with each other using sidelink signaling. Real-world applications of such sidelink communication may include public safety, proximity services, UE-to-network relay, vehicle-to-vehicle (V2V) communication, Internet of Things (IoE) communication, IoT communication, mission-critical meshes, and / or various other suitable applications. Typically, sidelink signaling can refer to a signal transmitted from one subordinate entity (e.g., UE1) to another subordinate entity (e.g., UE2) without relaying the communication through a scheduling entity (e.g., UE or BS), even if the scheduling entity is available for scheduling and / or control purposes. In some examples, licensed spectrum can be used to transmit sidelink signals (unlike wireless local area networks (WLANs) which typically use unlicensed spectrum).

[0057] Figure 5A and 5B Illustrations of example vehicle-to-everything (V2X) systems according to some aspects of this disclosure are shown. For example, Figure 5A and 5B The vehicle shown can communicate via a sidelink channel and can perform sidelink CSI reporting as described herein.

[0058] Figure 5A and 5B The V2X system provided in China offers two complementary transmission modes. Figure 5A The first transmission mode, illustrated by example, involves direct communication (e.g., also known as sidelink communication) between participants who are adjacent to each other in the local area. Through... Figure 5B The example shown in the second transmission mode involves network communication over a network, which can be implemented via a Uu interface (e.g., a wireless communication interface between the radio access network (RAN) and the UE).

[0059] refer to Figure 5A A V2X system 500 (e.g., including vehicle-to-vehicle (V2V) communication) is shown as having two vehicles 502 and 504. A first transmission mode allows direct communication between different participants in a given geographic location. As shown, the vehicles may have a wireless communication link 506 with a person (i.e., vehicle-to-person (V2P), e.g., via a UE) through a PC5 interface. Communication between vehicles 502 and 504 can also occur through a PC5 interface 508. Similarly, communication can occur from vehicle 502 to other road components (e.g., roadside service unit 510), such as traffic signals or signs (i.e., vehicle-to-infrastructure (V2I)) via a PC5 interface 512. Figure 5AEach communication link shown enables bidirectional communication between components, thus each component can act as both a transmitter and receiver of information. The V2X system 500 can be a self-managing system implemented without assistance from network entities. Because no network service interruption occurs during handover operations of mobile vehicles, the self-managing system can improve spectrum efficiency, reduce costs, and increase reliability. The V2X system can be configured to operate in licensed or unlicensed spectrum, allowing any vehicle equipped with the system to access public frequencies and share information. This coordinated / universal spectrum operation allows for safe and reliable operation.

[0060] Figure 5B A V2X system 550 is shown for communication between vehicles 552 and 554 via network entity 556. This network communication can occur through discrete nodes, such as base stations (e.g., eNBs or gNBs), which send and receive information to and from vehicles 552 and 554 (e.g., relaying information between vehicles 552 and 554). For example, network communication via vehicle-to-network (V2N) links 558 and 510 can be used for long-distance communication between vehicles, such as for transmitting the presence of a car accident a distance ahead along a road or highway. Nodes can send other types of communication to vehicles, such as traffic flow conditions, road hazard warnings, environmental / weather reports, and service station availability. Such data can be obtained from cloud-based shared services.

[0061] In some cases, two or more subordinate entities (e.g., UEs) can communicate with each other using sidelink signals. As mentioned above, V2V and V2X communications are examples of communications that can be transmitted via sidelinks. When a UE transmits sidelink communication on a sub-channel of a frequency band, the UE typically cannot receive another communication in the band (e.g., another sidelink communication from another UE). Other applications of sidelink communication can include public safety or service announcement communications, communications for proximity services, communications for UE-to-network relay, device-to-device (D2D) communications, Internet of Things (IoE) communications, Internet of Things (IoT) communications, mission-critical mesh communications, and other suitable applications. Typically, a sidelink can refer to a direct link between one subordinate entity (e.g., UE1) and another subordinate entity (e.g., UE2). Thus, even if the scheduling entity is available for scheduling or control purposes, the sidelink can be used to transmit and receive communications (also referred to herein as “sidelink signals”) without relaying them through the scheduling entity (e.g., BS). In some examples, licensed spectrum can be used to transmit sidelink signals (unlike wireless LANs that typically use unlicensed spectrum).

[0062] Various sidelink channels can be used for sidelink communication, including the Physical Sidelink Discovery Channel (PSDCH), Physical Sidelink Control Channel (PSCCH), Physical Sidelink Shared Channel (PSSCH), and Physical Sidelink Feedback Channel (PSFCH). The PSDCH can carry a discovery expression that enables near-end devices to discover each other. The PSCCH can carry control signaling, such as sidelink resource configurations and other parameters for data transmission, and the PSSCH can carry data transmission.

[0063] Regarding PSSCH operations, the UE performs transmission or reception within a time slot on the carrier. For a given period of time slot, transmission resources for sidelink transmission are typically reserved or allocated on a sub-channel of the frequency band. For the UE, the NR sidelink supports a scenario where all symbols in the time slot are available for sidelink transmission, and another scenario where only a subset of consecutive symbols in the time slot are available for sidelink transmission.

[0064] Example of high-reliability communication in a vehicle-to-everything (V2X) system using sidelinks and network links.

[0065] This disclosure provides apparatus, methods, processing systems, and computer-readable media for reliable communication in a vehicle-to-everything (V2X) system by communicating with a UE (e.g., a vehicle) in a V2X system using sidelinks and network links.

[0066] Vehicle-to-everything (V2X) services enable a variety of vehicle-based communication systems. For example, V2X services can be implemented as vehicle-to-vehicle (V2V), vehicle-to-pedestrian (V2P), vehicle-to-infrastructure (V2I), and vehicle-to-network (V2N) services. Typically, V2X services can utilize one or both sidelink (PC5) and network link (Uu) communication links, depending on the specific details of each service. In some examples, V2N services can leverage existing network infrastructure to allow services such as map downloads, software downloads, and updates to be performed between the vehicle UE and the V2X application server via a cellular network. Furthermore, V2N services operating on cellular networks over large communication areas can coexist with V2V, V2P, and V2I services, which use sidelink connections for communication over short distances.

[0067] Figure 6An example of communication between a Vehicle-to-Everything (V2X) application server, a Roadside Unit (RSU), and vehicles in a V2X system via sidelink and radio network link connections is illustrated. In this example, a UE can communicate with other UEs via a sidelink or radio network link connection (e.g., via a PC5 connection or a Uu connection) to send and receive V2X messages. UEs within the gNodeB coverage area can send requests for specific V2X services via a network link connection between the UE (e.g., the vehicle) and the gNodeB, and can send the requested information via both the network link and sidelink interfaces. To efficiently utilize the spectrum, UE-type Roadside Units (RSUs) can have both sidelink (PC5) and network link (Uu) connections. These RSUs are thus able to forward received packets from the V2X application server to the UEs within range via the sidelink connection between the RSU and the UEs within range.

[0068] Figure 7 This diagram illustrates the application of Quality of Service (QoS) parameters to V2X communications according to certain embodiments. As shown, V2X packets received at a transmitter UE (e.g., an RSU with a Uu connection to a gNodeB and a PC5 connection to a requesting UE) can be passed through the V2X layer, and PC5 QoS rules can be applied to the V2X packets. In a PC5 (sidelink) QoS flow, the V2X packets and QoS flow ID can be passed to the Serving Data Adaptation Protocol (SDAP) layer to generate a service layer radio bearer, and then passed through successive higher layers of the network stack to be sent to the requesting UE. QoS parameters applicable to the packets can be indicated at the application layer and can include parameters applied per flow or per packet. Parameters applied per flow can include, for example, resource type (Guaranteed Bit Rate (GBR), Critical Delay GBR, non-GBR), priority, packet delay budget, packet error rate, average window (e.g., for GBR and Critical Delay GBR resources), maximum data burst size (e.g., for Critical Delay GBR resources), etc. Parameters applied per packet can include range parameters that identify the minimum distance required to satisfy the QoS parameters. For example, distance can be defined in meters from the RSU and can be omnidirectional.

[0069] While these QoS parameters can allow for some improvements in communication reliability in V2X systems, omnidirectional QoS parameters and omnidirectional transmission of data from the transmitting UE (e.g., RSU) can be inefficient for many reasons. For example, packets may be available to UEs traveling in a specific direction. Omnidirectional transmission of these packets (e.g., in a broadcast transmission along all directions that the RSU can transmit on) can be wasteful of resources because the data in these packets may only be available to a subset of UEs connected to the RSU via sidelink connections. Furthermore, while QoS parameters can define the quality of service for various transmissions, there may be situations where the transmitting UE (1) cannot meet the QoS requirements for transmission, and (2) cannot ultimately ensure that the receiving UE can successfully receive and decode the requested data.

[0070] To enhance the robustness and reliability of communication in V2X systems, the embodiments described herein allow devices in a V2X system to use orientation parameters and communicate by switching between a sidelink (PC5) and a network link (Uu) connection in the event of a sidelink transmission failure. As discussed in further detail below, the V2X application server can indicate the range and direction (customized transmission shape) to the UE vehicle and / or RSU based on specific types of V2X packets and / or geographic information. The range parameter can be an optional parameter and, in some embodiments, can be used for multicast transmission. For content-sharing scenarios, the V2X application server can identify a specific RSU to be used when transmitting data to a requesting UE via a sidelink connection. This range can be defined based on the location of the RSU transmitting the specific packet and the receiver UE, according to the direction or customized shape, which can improve resource utilization by allowing transmissions to be performed in other directions. Furthermore, after an RSU or transmitter experiences multiple consecutive failures to transmit data to a receiver UE, the gNB can transmit packets to the receiver UE via a network link connection to ensure that data is provided to each requesting UE.

[0071] Figure 8 An example operation 800 according to an embodiment described herein is illustrated. This example operation 800 can be performed by a V2X application server for reliable communication within a vehicle-to-everything (V2X) system using sidelink and network link connections. As shown, operation 800 begins at block 802, where the V2X application server receives an information request from a user equipment (UE) through a serving network entity. This request typically includes the type of information requested and an indication of the UE's location.

[0072] At box 804, the V2X application server identifies one or more parameters used to send a request to the UE via the transmitter UE.

[0073] At box 806, the V2X application server sends the requested information for transmission to the UE to the serving network entity through the transmitter UE, based on the identified parameters.

[0074] Figure 9 An example operation 900 according to an embodiment described herein is illustrated. This example operation 900 can be performed by a user equipment (UE) for reliable communication within a vehicle-to-everything (V2X) system using sidelink and network link connections. As shown, operation 900 can begin at block 902, where the UE sends an information request from a V2X application server to a network entity. This request typically includes the type of information requested and an indication of the UE's location.

[0075] At box 904, the UE receives the requested information from the transmitter UE.

[0076] Figure 10 An example operation 1000 according to an embodiment described herein is illustrated. This example operation 1000 can be performed by a transmitter UE (e.g., RSU) for reliable communication within a vehicular network (V2X) system using sidelink and network link connections. As shown, operation 1000 can begin at block 1002, where the transmitter UE receives from a network entity information requested by a UE connected to the transmitter UE, along with one or more parameters for sending the request to the UE.

[0077] At box 1004, the transmitter UE sends a requested message to the UE via a sidelink connection between the UE and the transmitter UE based on one or more parameters.

[0078] In some embodiments, the V2X application server can notify a specific transmitter UE (e.g., RSU) to provide service to a UE that has requested data from the V2X application server. In operating modes where both sidelink and network link connections can be used to serve the UE, the application server can receive V2X requests via a Uu connection between the UE and the serving network entity (e.g., the serving gNodeB). The V2X application server can determine the target area and the size of the area to which packet transmission for the requested data will be directed (e.g., within what range should packets be sent from a specific RSU to a specific UE). As discussed, when requesting data from the V2X application server, the UE can identify the type of data requested from the V2X application server (e.g., map data, software updates, etc.) and the UE's current location (e.g., relative to the serving cell, latitude / longitude information determined by a satellite positioning system (SPS) such as NAVSTAR GPS, GALILEO, etc.). Because the application server can know the location of the requesting UE and the RSU in the V2X environment, the application server can identify the optimal RSU for serving the requesting UE. The RSU can be selected based on the range and location of the UE and RSU, so that the nearest RSU is selected to forward data to the UE.

[0079] In some embodiments, the range defined for the transmitter UE does not need to be circular. Depending on the type of requested data and / or the location of the transmitter UE and the requesting UE, the range can be defined based on the direction from the transmitter UE. For example, an elliptical communication area can be used to enhance high-priority services or direct data transmissions to a receiver in a specific direction from the transmitter UE. In some embodiments, the range parameter can be used for both unicast and multicast transmissions. For example, the transmitter UE can identify the importance of a particular UE's transmission in a specific direction and apply various QoS parameters to services in that specific direction to improve the reliability of communication with the requesting UE. In some embodiments, transmission can be omnidirectional if the V2X server does not identify the direction.

[0080] After the V2X application server identifies the parameters used to send request data to the requesting UE, the V2X application server can provide these parameters to the identified transmitter UE (RSU) via a network link connection, such as... Figure 11 As shown. V2X application servers can communicate with the core network ( Figure 11The 5GC network shown provides direction and range parameters for V2X communication via a sidelink (PC5) connection. The Policy Control Function (PCF) in the core network can provide Access and Mobility Management Functions (AMF), and the AMF can provide the NG-RAN (network entity) with sidelink QoS parameters for V2X communication requesting data. The QoS parameters for V2X communication on the sidelink can be generated by an application server and sent via the network link connection to one or both of the requesting UE (e.g., vehicle UE) or the sending UE (e.g., UE type RSU), and can include the direction and range information as described above.

[0081] In some embodiments, as described above, V2X packets can be associated with customized range and direction indications. To indicate directional transmission, the application server can set an extended range indication in QoS parameters. The Media Access Control (MAC) entity of the transmitter UE (RSU) can select a HARQ feedback range based on this range to ensure that all receivers to which the packet is intended have correctly decoded the packet. The HARQ feedback range can be omnidirectional, elliptical, or customized based on the packet type and location information of the requesting UE and the sending UE. Range and direction indications, including those for data in packets to be forwarded to the requesting UE via a sidelink connection, can be applied on a per-QoS flow or per-packet basis, based on the indications in the V2X packets.

[0082] To enhance the reliability of communication in V2X systems, UEs within the HARQ feedback range identified in V2X packets can send ACK or NACK messages to the sending UE (RSU) based on whether each UE has successfully received and decoded the V2X packet. To ensure that each expected receiver has successfully received the V2X packet, the sending UE can forward HARQ ACK / NACK feedback to the serving gNodeB, and the serving gNodeB can determine whether to retransmit the packet to a specific UE via a network link (e.g., Uu) connection. For example, if the sending UE fails to successfully send V2X packets to the requesting UE a threshold number of times, the gNodeB can send V2X packets to the requesting UE via the Uu connection between the gNodeB and the requesting UE, thereby bypassing the sidelink connection between the requesting UE and the sending UE (which may be an unstable connection).

[0083] In some embodiments, the requesting UE may request the retransmission of V2X packets from the serving gNodeB. To do this, the requesting UE may send a negative acknowledgment (NACK) to the serving gNodeB, for example, via a network link (e.g., Uu) connection between the receiving UE and the serving gNodeB. In response, the gNodeB may directly send V2X packets to the requesting UE, thereby bypassing the sidelink connection between the requesting UE and the transmitting UE.

[0084] Upon receiving a NACK or other indication that the requesting UE has failed to receive V2X packets, various actions can be taken to retransmit V2X packets to the requesting UE. As discussed, in some embodiments, the gNodeB can transmit packets to the requesting UE via a network link connection. For example, when the coverage or range of the selected transmitter UE (e.g., RSU) is unsuitable for serving the requesting UE and no other transmitter UE is within the range of the requesting UE, the gNodeB can transmit packets to the requesting UE via a network link connection. In some embodiments, the application can select another transmitter UE to transmit V2X packets to the requesting UE. The transmitter UE can be selected based on, for example, the movement and location of the requesting UE.

[0085] Figure 12 A communication device 1200 is shown, which may include operations configured to perform the techniques disclosed herein, such as Figure 8 The operation shown herein includes various components (e.g., corresponding to component plus functional components). Communication device 1200 includes a processing system 1202 coupled to transceiver 1208. Transceiver 1208 is configured to transmit and receive signals, such as the various signals described herein, for communication device 1200 via antenna 1210. Processing system 1202 can be configured to enable communication device 1200 to perform processing functions, including processing signals received and / or to be transmitted by communication device 1200.

[0086] The processing system 1202 includes a processor 1204 coupled to a computer-readable medium / memory 1212 via a bus 1206. In some aspects, the computer-readable medium / memory 1212 is configured to store instructions (e.g., computer-executable code) that, when executed by the processor 1204, cause the processor 1204 to perform... Figure 8The operations shown may be other operations used to perform the various techniques discussed herein. In some aspects, the computer-readable medium / memory 1212 stores code 1214 for receiving an information request from a vehicle-to-everything (V2X) application server; code 1216 for identifying one or more parameters of information for sending a request to a UE via a transmitter UE; and code 1218 for information of the request sent to a UE via the transmitter UE. In some aspects, the processor 1204 has circuitry configured to implement the code stored in the computer-readable medium / memory 1212. The processor 1204 includes circuitry 1220 for receiving an information request from a vehicle-to-everything (V2X) application server; circuitry 1222 for identifying one or more parameters of information for sending a request to a UE via a transmitter UE; and circuitry 1224 for sending the request to a UE via the transmitter UE.

[0087] Figure 13 A communication device 1300 is shown, which may include operations configured to perform the techniques disclosed herein, such as Figure 9 The operation shown herein includes various components (e.g., corresponding to component plus functional components). Communication device 1300 includes a processing system 1302 coupled to transceiver 1308. Transceiver 1308 is configured to transmit and receive signals, such as the various signals described herein, for communication device 1300 via antenna 1310. Processing system 1302 can be configured to enable communication device 1300 to perform processing functions, including processing signals received and / or to be transmitted by communication device 1300.

[0088] The processing system 1302 includes a processor 1304 coupled to a computer-readable medium / memory 1312 via a bus 1306. In some aspects, the computer-readable medium / memory 1312 is configured to store instructions (e.g., computer-executable code) that, when executed by the processor 1304, cause the processor 1304 to perform... Figure 9 The operations shown may be other operations used to perform the various techniques discussed herein. In some aspects, the computer-readable medium / memory 1312 stores code 1314 for sending an information request from a vehicle-to-everything (V2X) application server; and code 1316 for receiving the requested information. In some aspects, the processor 1304 has circuitry configured to implement the code stored in the computer-readable medium / memory 1312. The processor 1304 includes circuitry 1318 for sending an information request from a vehicle-to-everything (V2X) application server; and circuitry 1320 for receiving the requested information.

[0089] Figure 14 A communication device 1400 is shown, which may include operations configured to perform the techniques disclosed herein, such as Figure 10 The operation shown herein includes various components (e.g., corresponding to component plus functional components). Communication device 1400 includes a processing system 1402 coupled to transceiver 1408. Transceiver 1408 is configured to transmit and receive signals, such as the various signals described herein, for communication device 1400 via antenna 1410. Processing system 1402 can be configured to enable communication device 1400 to perform processing functions, including processing signals received and / or to be transmitted by communication device 1400.

[0090] The processing system 1402 includes a processor 1404 coupled to a computer-readable medium / memory 1412 via a bus 1406. In some aspects, the computer-readable medium / memory 1412 is configured to store instructions (e.g., computer-executable code) that, when executed by the processor 1404, cause the processor 1404 to perform... Figure 10 The operations shown may be other operations used to perform the various techniques discussed herein. In some aspects, the computer-readable medium / memory 1412 stores code 1414 for receiving information from a UE connected to a transmitter UE and parameters for sending information to the UE; and code 1416 for sending the request information to the UE. In some aspects, the processor 1404 has circuitry configured to implement the code stored in the computer-readable medium / memory 1412. The processor 1404 includes circuitry 1418 for receiving information from a UE connected to a transmitter UE and parameters for sending information to the UE; and circuitry 1420 for sending the request information to the UE.

[0091] The methods disclosed herein include one or more steps or actions for implementing the methods. The method steps and / or actions may be interchanged without departing from the scope of the claims. In other words, unless a specific order of steps or actions is specified, the order and / or use of a particular step and / or action may be modified without departing from the scope of the claims.

[0092] As used herein, the phrase “at least one of” in a list of items refers to any combination of those items containing a single member. As an example, “at least one of: a, b, or c” is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other order of a, b, and c).

[0093] As used herein, the term "determining" encompasses a variety of actions. For example, "determining" can include calculation, operation, processing, derivation, investigation, searching (e.g., looking in a table, database, or other data structure), ascertaining, etc. Furthermore, "determining" can include receiving (e.g., receiving information), accessing (e.g., accessing data in memory), etc. Additionally, "determining" can include parsing, selecting, picking, building, etc.

[0094] The preceding description is provided to enable any person skilled in the art to practice the various aspects described herein. Various variations of these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but are to be given the full scope consistent with the language of the claims, wherein, unless expressly stated otherwise, elements referred to in the singular are not intended to mean “one and only one,” but rather “one or more.” Unless expressly stated otherwise, the term “some” means one or more. All structural and functional equivalents of elements throughout the various aspects described in this disclosure that are known or will be known hereafter by a person skilled in the art are expressly incorporated herein by reference and are intended to be covered by the claims. Moreover, regardless of whether the contents disclosed herein are expressly recited in the claims, they are not intended to be disclosed to the public. Pursuant to the provisions of 35 U.SC §112(f), no claim element is interpreted unless the element is expressly stated using the phrase “means for,” or, in the case of a method claim, using the phrase “step for.”

[0095] The various operations described above can be performed by any suitable component capable of performing the corresponding function. This component may include various hardware and / or multiple software components and / or multiple modules, including but not limited to circuits, application-specific integrated circuits (ASICs), or processors. Typically, where operations as shown in the figures are performed, those operations may have corresponding components plus functional components. For example, Figure 7-8 The various operations shown can be performed by Figure 4 The various processors shown (such as processors 466, 458, 464 and / or controller / processor 480 of UE120a) are used to perform the execution.

[0096] The various illustrative logic blocks, modules, and circuits disclosed herein can be implemented or executed using a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors integrated with a DSP core, or any other such configuration.

[0097] If implemented in hardware, the example hardware configuration could include a processing system in a wireless node. This processing system could be implemented using a bus architecture. The bus could include any number of interconnect buses and bridges, depending on the specific application and overall design constraints of the processing system. The bus could link together various circuits, including a processor, machine-readable media, and a bus interface. The bus interface could be used to connect network adapters, etc., to the processing system via the bus. The network adapter could be used to implement the signal processing functions of the PHY layer. In user terminal 120 (see...) Figure 1 In this case, a user interface (e.g., keyboard, display, mouse, joystick, etc.) can also be connected to the bus. This bus can also link various other circuits well known in the art, such as timing sources, peripherals, voltage regulators, power management circuits, etc., and therefore will not be described further. The processor can be implemented using one or more general-purpose and / or special-purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuits capable of executing software. Those skilled in the art will recognize how best to implement the described functionality for the processing system based on the specific application and the overall design constraints imposed on the system as a whole.

[0098] If implemented in software, the functionality can be stored on or transmitted via a computer-readable medium as one or more instructions or code. Software should be interpreted broadly as instructions, data, or any combination thereof, whether referring to software, firmware, middleware, microcode, hardware description languages, or others. Computer-readable media includes computer storage media and communication media, with communication media including any medium that facilitates the transfer of a computer program from one place to another. The processor may be responsible for managing the bus and general processing, including the execution of software modules stored on the machine-readable storage medium. The computer-readable storage medium may be coupled to the processor, allowing the processor to read information from and write information to the storage medium. Alternatively, the storage medium may be integrated with the processor. For example, the machine-readable medium may include a transmit line, a carrier wave modulated by data, and / or a computer-readable storage medium on which instructions separate from the wireless node are stored, all of which may be accessible by the processor via a bus interface. Alternatively or additionally, the machine-readable medium or any portion thereof may be integrated into the processor, such as in cases where it may have a cache and / or a general-purpose register file. Examples of machine-readable storage media may include, for example, RAM (random access memory), flash memory, ROM (read-only memory), PROM (programmable read-only memory), EPROM (erasable programmable read-only memory), EEPROM (electrically erasable programmable read-only memory), registers, disks, optical disks, hard disks, or any other suitable storage media, or any combination thereof. The machine-readable medium may be included in a computer program product.

[0099] A software module may include a single instruction or multiple instructions and may be distributed across several different code segments, different programs, and multiple storage media. The computer-readable medium may include multiple software modules. A software module includes instructions that, when executed by a device such as a processor, cause the processing system to perform various functions. The software module may include sending modules and receiving modules. Each software module may reside in a single storage device or be distributed across multiple storage devices. For example, when a trigger event occurs, a software module may be loaded from a hard disk drive into RAM. During the execution of a software module, the processor may load some instructions into a cache to improve access speed. One or more cache lines may then be loaded into a general-purpose register file for processor execution. When the functionality of a software module is mentioned below, it will be understood that this functionality is implemented by the processor when executing the instructions from that software module.

[0100] Furthermore, any connection is appropriately referred to as computer-readable medium. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared (IR), radio, and microwave, the definition of medium includes coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave. The disks and optical discs used herein include compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and... Optical discs, where magnetic disks typically copy data magnetically, copy data optically using lasers. Therefore, in some aspects, computer-readable media can include non-transitory computer-readable media (e.g., tangible media). Furthermore, in other aspects, computer-readable media can include transient computer-readable media (e.g., signals). Combinations of the above should also be included within the scope of computer-readable media.

[0101] Therefore, certain aspects may include a computer program product for performing the operations presented herein. For example, such a computer program product may include a computer-readable medium having instructions stored thereon (and / or encoded thereon) that can be executed by one or more processors to perform the operations described herein. For example, for performing the operations described herein and in… Figure 8-9 The instructions for the operation are described in the text.

[0102] Furthermore, it should be understood that modules and / or other suitable components for performing the methods and techniques described herein may be downloaded and / or otherwise obtained by the user terminal and / or base station where applicable. For example, such a device may be coupled to a server to facilitate the transfer of components for performing the methods described herein. Alternatively, the various methods described herein may be provided by storage components (e.g., RAM, ROM, physical storage media such as CDs or floppy disks, etc.), allowing the user terminal and / or base station to obtain the various methods by coupling or providing the storage components to the device. Furthermore, any other suitable techniques for providing the methods and techniques described herein to the device may be utilized.

[0103] It should be understood that the claims are not limited to the precise configuration and components described above. Various modifications, alterations, and variations may be made to the arrangement, operation, and details of the described methods and apparatus without departing from the scope of the claims.

Claims

1. A method for wireless communication by a V2X application server in a vehicle-to-everything (V2X) network, comprising: The Serving Network Entity receives a request for information from a V2X Application Server from a User Equipment (UE), wherein the request includes an indication of the type of information requested and the location of the UE. One or more parameters are identified for transmitting requested information to the UE via the transmitter UE, wherein the one or more parameters include a range parameter and a transmission direction parameter, the transmission direction parameter specifying the direction used by the transmitter UE when transmitting the requested information to the UE; and Based on the identified parameters, the transmitter (UE) sends the requested information for transmission to the serving network entity. The method further includes: sending the Quality of Service (QoS) parameters to the network entity for sending the requested information to the UE; The QoS parameters include the valid range of information from the transmitter UE for the requested information.

2. The method according to claim 1, wherein, The range parameter includes an extended range indication used by the transmitter UE to determine the valid range for transmitting the requested information.

3. The method according to claim 1, wherein, The transmission direction parameter identifies the shape of the transmission performed by the transmitter UE.

4. The method according to claim 1, further comprising: When it is determined that the transmitter UE has failed to successfully send the requested information to the UE, the network entity is configured to send the requested information to the UE via the Uu connection between the UE and the network entity.

5. The method according to claim 1, further comprising: Receive an indication that the UE failed to receive the requested information; The second transmitter UE is selected based on the location and movement information reported by the UE; as well as The second transmitter (UE) sends the requested information to the serving network entity for transmission to the UE.

6. The method according to claim 1, further comprising: The transmitter UE is selected based on the location of the UE and the location information of each of the plurality of transmitter UEs.

7. The method according to claim 1, wherein, The one or more parameters are identified based on the type of information requested.

8. A method for wireless communication by a user equipment (UE), comprising: Send a request to a network entity for information from a V2X application server, wherein the request includes an indication of the type of information requested and the location of the UE; as well as The system receives requested information from the transmitter UE, wherein the requested information is sent by the vehicle-to-everything (V2X) application server based on one or more parameters identified for the requested information, the one or more parameters including a range parameter and a transmission direction parameter, the transmission direction parameter specifying the direction used by the transmitter UE when sending the requested information to the UE; The method further includes: receiving one or more Quality of Service (QoS) parameters from the transmitter; The one or more QoS parameters include a valid range of information from the transmitter UE for the requested information.

9. The method of claim 8, wherein the method further comprises: Based on the distance between the UE and the transmitter UE and the effective range of the requested information from the transmitter UE, it is determined that the UE is the intended recipient of the requested information; as well as Based on whether the requested information can be successfully decoded, a Hybrid Automatic Repeat Request (HARQ) with either Acknowledgment (ACK) or Negative Acknowledgment (NACK) is sent to the transmitter.

10. The method of claim 8, further comprising: The number of times the requested information is retransmitted from the transmitter UE; The number of times the requested information could not be successfully received reached the threshold. as well as Based on the threshold number of times the requested information has been unsuccessfully received, an indication is sent to the network entity that the transmitter UE has failed to send the requested information to the UE.

11. The method of claim 10, further comprising: The requested information is received from the network entity via the Uu connection between the UE and the network entity.

12. The method of claim 10, further comprising: Receive the requested information from the second network entity.

13. A method for wireless communication by a transmitter user equipment (UE), comprising: The network entity receives information requested by a UE connected to the transmitter UE, and one or more parameters for sending the requested information to the UE, wherein the one or more parameters include a range parameter and a transmission direction parameter, the transmission direction parameter specifying the direction used by the transmitter UE when sending the requested information to the UE; and Based on one or more parameters, the requested information is sent to the UE via a sidelink connection between the UE and the transmitter UE; The method further includes: sending one or more Quality of Service (QoS) parameters to the UE; The one or more QoS parameters include a valid range of information for the requested information.

14. The method according to claim 13, wherein, The range parameter includes an extended range indication used by the transmitter UE to determine the valid range for transmitting the requested information.

15. The method according to claim 13, wherein, The transmission direction parameter identifies the shape of the transmission performed by the transmitter UE.

16. The method of claim 13, further comprising: The UE receives a Hybrid Automatic Repeat Request (HARQ) feedback indicating whether the UE has successfully received the requested information.

17. The method according to claim 16, wherein, HARQ feedback is received from UEs within a specified distance of the transmitter UE.

18. The method of claim 16, further comprising: Based on receiving HARQ negative acknowledgment (NACK) feedback from the UE, the requested information is retransmitted to the UE.

19. The method of claim 18, further comprising: The HARQ NACK feedback is forwarded to the network entity.

20. The method of claim 18, further comprising: The number of times the UE failed to successfully receive the requested information reached a threshold was determined. as well as Send an instruction to the network entity to trigger the network entity to send the requested information directly to the UE via the Uu connection.

21. An apparatus for wireless communication via a V2X application server, comprising: The processor is configured as follows: The Serving Network Entity receives a request for information from a V2X Application Server from a User Equipment (UE), wherein the request includes an indication of the type of information requested and the location of the UE. One or more parameters are identified for transmitting requested information to the UE via the transmitter UE, wherein the one or more parameters include a range parameter and a transmission direction parameter, the transmission direction parameter specifying the direction used by the transmitter UE when transmitting the requested information to the UE; and Based on the identified parameters, the transmitter (UE) sends the requested information for transmission to the serving network entity. Send the Quality of Service (QoS) parameters to the network entity for sending the requested information to the UE; The QoS parameters include a valid range of information from the transmitter UE for the requested information; and Memory.

22. An apparatus for wireless communication by a user equipment (UE), comprising: The processor is configured as follows: Sending a request for information from a V2X application server to a network entity, wherein the request includes an indication of the type of information requested and the location of the UE; as well as The system receives requested information from the transmitter UE, wherein the requested information is sent by the vehicle-to-everything (V2X) application server based on one or more parameters identified for the requested information, the one or more parameters including a range parameter and a transmission direction parameter, the transmission direction parameter specifying the direction used by the transmitter UE when sending the requested information to the UE; Receive one or more Quality of Service (QoS) parameters from the transmitter; Wherein, the one or more QoS parameters include a valid range of information from the transmitter UE for the requested information; and Memory.

23. An apparatus for wireless communication by a transmitter user equipment (UE), comprising: The processor is configured as follows: The network entity receives information requested by a UE connected to the transmitter UE, and one or more parameters for sending the requested information to the UE, wherein the one or more parameters include a range parameter and a transmission direction parameter, the transmission direction parameter specifying the direction used by the transmitter UE when sending the requested information to the UE; and Based on one or more parameters, the requested information is sent to the UE via a sidelink connection between the UE and the transmitter UE; Send one or more Quality of Service (QoS) parameters to the UE; Wherein, the one or more QoS parameters include a valid range for the requested information; and Memory.

24. An apparatus for wireless communication via a V2X application server, comprising: A component for receiving a request for information from a V2X application server from a user equipment (UE) via a serving network entity, wherein the request includes an indication of the type of information requested and the location of the UE; A component for identifying one or more parameters for transmitting requested information to a UE via a transmitter UE, wherein the one or more parameters include a range parameter and a transmission direction parameter, the transmission direction parameter specifying the direction used by the transmitter UE when transmitting the requested information to the UE; and A component for sending, based on the identified parameters, the transmitter (UE) to the serving network entity the requested information to be sent to the UE; A component for sending Quality of Service (QoS) parameters to the network entity for sending requested information to the UE. The QoS parameters include the valid range of information from the transmitter UE for the requested information.

25. An apparatus for wireless communication by a user equipment (UE), comprising: A component for sending a request for information from a V2X application server to a network entity, wherein the request includes an indication of the type of information requested and the location of the UE; as well as A component for receiving requested information from a transmitter UE, wherein the requested information is sent by the vehicle-to-everything (V2X) application server based on one or more parameters identified for the requested information, the one or more parameters including a range parameter and a transmission direction parameter, the transmission direction parameter specifying the direction used by the transmitter UE when sending the requested information to the UE; Components for receiving one or more Quality of Service (QoS) parameters from the transmitter; The one or more QoS parameters include a valid range of information from the transmitter UE for the requested information.

26. An apparatus for wireless communication by a transmitter user equipment (UE), comprising: A component for receiving information requested by a UE connected to the transmitter UE from a network entity and one or more parameters for sending the requested information to the UE, wherein the one or more parameters include a range parameter and a transmission direction parameter, the transmission direction parameter specifying the direction used by the transmitter UE when sending the requested information to the UE; and A component for sending requested information to the UE via a sidelink connection between the UE and the transmitter UE based on one or more parameters; A component used to send one or more Quality of Service (QoS) parameters to the UE; The one or more QoS parameters include a valid range of information for the requested information.

27. A computer program product comprising computer-readable instructions, which, when executed by a processor, cause the processor to perform the method according to any one of claims 1-7.

28. A computer program product comprising computer-readable instructions, which, when executed by a processor, cause the processor to perform the method according to any one of claims 8-12.

29. A computer program product comprising computer-readable instructions, which, when executed by a processor, cause the processor to perform the method according to any one of claims 13-20.

Images