Traffic operation and dispatch based on RSU

By introducing a manipulation coordinator into the vehicle, using the direct communication link and the sensor information of the RSU to coordinate the vehicle manipulation, the problems of unsafe transportation manipulation and high hardware demand in the prior art are solved, and safe and economical Self-driving.

CN113170294BActive Publication Date: 2024-11-05QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN201980079310.8
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2019-11-11
Filing Date
2019-11-12
Publication Date
2024-11-05
Estimated Expiration
2039-11-12

AI Technical Summary

Technical Problem

The prior art is difficult to ensure safe and effective vehicle manipulation in V2X, V2V and D2D communication between vehicles, especially in scenarios such as intersections, incomplete sensor information and distributed autonomous driving logic may lead to insufficient manipulation state. Stable, and each car requires expensive hardware support.

Method used

Centralized scheduler-based vehicle manipulation coordination through direct communication links between user equipment (UE) and manipulation coordinator (such as roadside units, RSU), requesting and receiving manipulation dispatch services, using the RSU, combined with The sensor information of the RSU and the report information of the UE determine the manipulation command.

Benefits of technology

The operation logic of transportation tools is simplified, the autonomous logic conflict between OEMs of different vehicles is avoided, the hardware requirements of each vehicle are reduced, safe and efficient transportation tools are realized, and the cost of achieving autonomous driving is reduced.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113170294B_ABST
    Figure CN113170294B_ABST
Patent Text Reader

Abstract

The present disclosure provides a centralized, scheduler-based handling for UEs that transmit and receive data to and from a maneuvering coordinator based on V2X communications. Once a UE knows the maneuvering coordinator, the UE can send a request for maneuvering operation scheduling to the maneuvering coordinator. The maneuvering coordinator then schedules and coordinates the operations of the UE.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Application No. 62 / 776,950, filed on December 7, 2018, entitled “RSU BASED VEHICLE MANEUVERSCHEDULING,” and U.S. Patent Application No. 16 / 679,973, filed on November 11, 2019, entitled “RSU BASED VEHICLE MANEUVER SCHEDULING,” both of which are expressly incorporated herein by reference in their entirety.

[0003] background Technical Field

[0005] The present disclosure relates generally to communication systems, and more particularly to vehicle-to-vehicle (V2V), vehicle-to-everything (V2X), or other device-to-device (D2D) communications.

[0006] introduction

[0007] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, and broadcast. Typical wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources. Examples of such multiple access technologies include 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.

[0008] These multiple access technologies have been adopted in various telecommunication standards to provide common protocols that enable different wireless devices to communicate at city, country, region, and even global levels. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5GNR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Various aspects of wireless communication may include direct communication between devices, such as in V2X, V2V, and / or other D2D communications. There is a need to further improve V2X, V2V, and / or other D2D technologies. These improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies.

[0009] Overview

[0010] A brief summary of one or more aspects is given below to provide a basic understanding of such aspects. This summary is not an exhaustive overview of all conceived aspects, and is neither intended to identify the key or critical elements of all aspects nor to define the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to a more detailed description that will be presented later.

[0011] In one aspect of the present disclosure, a method, computer-readable medium, and device for wireless communication at a user equipment (UE) are provided. The device wirelessly requests a service for maneuvering scheduling of a vehicle from the maneuvering coordinator via a direct communication link between the UE and the maneuvering coordinator. The device wirelessly receives maneuvering information from the maneuvering coordinator via the direct communication link. The device then applies the maneuvering information.

[0012] In another aspect of the present disclosure, a method, computer-readable medium, and device for wireless communication at a maneuvering coordinator are provided. The device wirelessly receives a request for a service for maneuvering scheduling of a vehicle from at least one UE via a direct communication link between each of at least one UE and the maneuvering coordinator. The device determines maneuvering information for the at least one UE based on the request. The device wirelessly transmits the maneuvering information to the at least one UE via the direct communication link.

[0013] To achieve the foregoing and related ends, the one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and drawings set forth in detail certain illustrative features of the one or more aspects. However, these features are merely indicative of several of the various ways in which the principles of the various aspects may be employed, and this description is intended to cover all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.

[0016] Figure 2 Various example aspects of a sidelink slot structure are illustrated.

[0017] Figure 3 is a diagram illustrating an example of a first device and a second device involved in wireless communication based on, for example, V2V, V2X, and / or device-to-device communication.

[0018] Figure 4 is a diagram illustrating an example of wireless communication between devices at an intersection based on V2X / V2V / D2D communication according to one aspect of the present disclosure.

[0019] Figure 5 is a diagram illustrating an example of wireless communication between devices at an intersection based on V2X / V2V / D2D communication according to another aspect of the present disclosure.

[0020] Figure 6 is a diagram of an example communication flow between a steering coordinator and UEs within range of the steering coordinator according to one aspect of the present disclosure.

[0021] Figure 7 is a diagram of an example communication flow between a steering coordinator and UEs within range of the steering coordinator according to another aspect of the present disclosure.

[0022] Fig. 8A and 8B is a flow chart of a wireless communication method at a UE.

[0023] Fig. 9 is a conceptual data flow diagram illustrating the flow of data between different devices / components in an example apparatus.

[0024] Fig.10 is a diagram illustrating an example of a hardware implementation for an apparatus employing a processing system.

[0025] Fig.11A and 11B is a flow chart of a wireless communication method at a steering coordinator.

[0026] Fig.12 is a conceptual data flow diagram illustrating the flow of data between different devices / components in an example apparatus.

[0027] Fig.13 is a diagram illustrating an example of a hardware implementation for an apparatus employing a processing system.

[0028] Detailed Description

[0029] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be practiced. This detailed description includes specific details to provide a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid diluting such concepts.

[0030] Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0031] As an example, an element, or any part of an element, or any combination of elements may be implemented as a "processing system" including one or more processors. Examples of processors include: microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gating logic, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout this disclosure. One or more processors in a processing system may execute software. Software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether it is described in software, firmware, middleware, microcode, hardware description languages, or other terms.

[0032] Accordingly, in one or more example embodiments, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, each function may be stored or encoded on a computer-readable medium as one or more instructions or codes. Computer-readable media include computer storage media. Storage media may be any available medium that can be accessed by a computer. As an example and not limitation, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, a combination of computer-readable media of the above types, or any other medium that can be used to store computer-executable code in the form of instructions or data structures that can be accessed by a computer.

[0033] Figure 1 1 is a diagram illustrating an example of a wireless communication system and access network 100. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes a base station 102, a UE 104, an evolved packet core (EPC) 160, and a core network (e.g., 5GC) 190. The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). A macro cell includes a base station. A small cell includes a femto cell, a pico cell, and a micro cell.

[0034] Base stations 102 configured for 4G LTE (collectively referred to as Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with EPC 160 via a backhaul link 132 (e.g., an S1 interface). Base stations 102 configured for NR (collectively referred to as Next Generation RAN (NG-RAN)) may interface with core network 190 via a backhaul link 184. Base stations 102 may perform one or more of the following functions, among other functions: delivery of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, positioning, and delivery of alert messages. Base stations 102 may communicate with each other directly or indirectly (eg, through EPC 160 or core network 190) over backhaul links 134 (eg, X2 interfaces). Backhaul links 134 may be wired or wireless.

[0035] Base stations 102 may communicate wirelessly with UE 104. Each base station 102 may provide communication coverage for a corresponding geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, a small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of one or more macro base stations 102. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved B node (eNB) (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG). A communication link 120 between a base station 102 and a UE 104 may include an uplink (UL) (also referred to as a reverse link) transmission from the UE 104 to the base station 102 and / or a downlink (DL) (also referred to as a forward link) transmission from the base station 102 to the UE 104. The communication link 120 may use multiple input multiple output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. These communication links may be through one or more carriers. The base station 102 / UE 104 may use spectrum of up to Y MHz (e.g., 5, 10, 15, 20, 100, 400 MHz, etc.) bandwidth for each carrier allocated in a carrier aggregation for a total of up to Yx MHz (x component carriers) for transmission in each direction. The carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to UL). The component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

[0036] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). The D2D communication may be through a variety of wireless D2D communication systems, such as, for example, FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi based on the IEEE 802.11 standard, LTE, or NR.

[0037] The wireless communication system may further include a Wi-Fi access point (AP) 150 communicating with a Wi-Fi station (STA) 152 in the 5 GHz unlicensed spectrum via a communication link 154. When communicating in the unlicensed spectrum, the STA 152 / AP 150 may perform a clear channel assessment (CCA) prior to communication to determine whether the channel is available.

[0038] The small cell 102' may operate in a licensed and / or unlicensed spectrum. When operating in an unlicensed spectrum, the small cell 102' may employ NR and use the same 5 GHz unlicensed spectrum as used by the Wi-Fi AP 150. The small cell 102' employing NR in the unlicensed spectrum may boost the coverage of the access network and / or increase the capacity of the access network.

[0039] Whether it is a small cell 102' or a large cell (e.g., a macro base station), the base station 102 may include an eNB, a gB node (gNB), or other types of base stations. Some base stations 180 (such as gNBs) may operate in traditional sub-6 GHz spectrum, millimeter wave (mmW) frequencies, and / or near mmW frequencies to communicate with UE 104. When the gNB operates in mmW or near mmW frequencies, the gNB may be referred to as a mmW base station. Extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 mm and 10 mm. The radio waves in this band may be referred to as millimeter waves. Near mmW can be extended down to 3 GHz frequencies with a wavelength of 100 mm. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, which is also referred to as centimeter waves. Communications using mmW / near mmW radio frequency bands have extremely high path loss and short range. A mmW base station (eg, base station 180 ) may utilize beamforming 182 with UE 104 to compensate for extremely high path loss and short range.

[0040] Devices can use beamforming to transmit and receive communications. For example, Figure 1It is illustrated that the base station 180 may transmit beamformed signals to the UE 104 in one or more transmission directions 182'. UE 104 may receive beamformed signals from base station 180 in one or more receive directions 182″. UE 104 may also transmit beamformed signals to base station 180 in one or more transmit directions. Base station 180 may receive beamformed signals from UE 104 in one or more receive directions. Base station 180 / UE 104 may perform beam training to determine the best receive direction and transmit direction for each of base station 180 / UE 104. The transmit direction and receive direction of base station 180 may be the same or different. The transmit direction and receive direction of UE 104 may be the same or different. Although the beamformed signals are illustrated between UE 104 and base station 102 / 180, various aspects of beamforming may be similarly applied by UE 104 or RSU 107 to communicate with other UEs 104 or RSUs 107, such as for communications based on V2X, V2V, or D2D.

[0041] The EPC 160 may include a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, a multimedia broadcast multicast service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and a packet data network (PDN) gateway 172. The MME 162 may be in communication with a home subscriber server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. In general, the MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are delivered through the serving gateway 166, which itself is connected to the PDN gateway 172. The PDN gateway 172 provides UE IP address allocation and other functions. The PDN gateway 172 and the BM-SC 170 are connected to IP services 176. The IP services 176 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, and / or other IP services. The BM-SC 170 may provide functionality for MBMS user service provisioning and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS transmissions, may be used to authorize and initiate MBMS bearer services within a public land mobile network (PLMN), and may be used to schedule MBMS transmissions. The MBMS gateway 168 may be used to distribute MBMS traffic to base stations 102 belonging to a multicast broadcast single frequency network (MBSFN) area that broadcasts a specific service, and may be responsible for session management (start / stop) and for collecting eMBMS-related charging information.

[0042] The core network 190 may include an access and mobility management function (AMF) 192, other AMFs 193, a session management function (SMF) 194, and a user plane function (UPF) 195. The AMF 192 may be in communication with a unified data management (UDM) 196. The AMF 192 is a control node that handles signaling between the UE 104 and the core network 190. In general, the AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are delivered through the UPF 195. The UPF 195 provides UE IP address allocation and other functions. The UPF 195 is connected to an IP service 197. The IP service 197 may include the Internet, an intranet, an IP multimedia subsystem (IMS), a PS streaming service, and / or other IP services.

[0043] A base station may also be referred to as a gNB, a Node B, an evolved Node B (eNB), an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmission reception point (TRP), or some other suitable term. The base station 102 provides an access point to the EPC 160 or the core network 190 for the UE 104. Examples of UE 104 include a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a tablet device, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a health care device, an implant, a sensor / actuator, a display, or any other similar functional device. Some UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, ovens, vehicles, heart monitors, etc.). UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology.

[0044] Some wireless communication networks may include vehicle-based communication devices that may communicate and / or communicate with other devices from vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I) (e.g., from a vehicle-based communication device to a road infrastructure node, such as a roadside unit (RSU)), vehicle-to-network (V2N) (e.g., from a vehicle-based communication device to one or more network nodes, such as a base station), and / or combinations thereof, which may be collectively referred to as vehicle-to-everything (V2X) communications. Again, referring to Figure 1In some aspects, a UE 104 (e.g., a transmitting vehicle user equipment (VUE) or other UE) may be configured to transmit messages directly to another UE 104. The communication may be based on V2V / V2X / V2I or other D2D communications, such as Proximity Services (ProSe), etc. V2V, V2X, V2I and / or D2D-based communications may also be transmitted and received by other transmitting and receiving devices, such as a roadside unit (RSU) 107, etc. Aspects of the communication may be based on PC5 or sidelink communications, for example, as combined with Figure 2 Although the following description may provide information about V2X / D2D communications in conjunction with 5GNR, the concepts described herein may be applicable to other similar areas such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0045] Refer again Figure 1 In certain aspects, a UE 104 may include a manipulation request component 198 configured to send a request for a manipulation operation schedule to a manipulation coordinator (e.g., a component, function, or service hosted by an RSU 107 or other device). A manipulation coordinator (e.g., an RSU 107) may include a manipulation coordination component 199 configured to receive a manipulation request from at least one UE 104, determine coordinated manipulation information for the at least one UE, and transmit a manipulation command to the at least one requesting UE.

[0046] Figure 2Example diagrams 200 and 210 are illustrated, which illustrate example time slot structures that can be used for wireless communication (e.g., for sidelink communication) between UE 104 and UE 104'. The time slot structure can be within a 5G / NR frame structure. Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar fields, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies. This is just an example, and other wireless communication technologies may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 equally sized subframes (1ms). Each subframe may include one or more time slots. A subframe may also include a mini-time slot, which may include 7, 4, or 2 symbols. Each time slot may include 7 or 14 symbols, depending on the time slot configuration. For time slot configuration 0, each time slot may include 14 symbols, and for time slot configuration 1, each time slot may include 7 symbols. Diagram 200 illustrates a single time slot transmission, which may correspond to a 0.5 ms transmission time interval (TTI), for example. Diagram 210 illustrates example 2 time slot aggregation, for example, aggregation of two 0.5 ms TTIs. Diagram 200 illustrates a single RB, while diagram 210 illustrates N RBs. In diagram 210, the 10 RBs used for control are merely an example. The number of RBs may be different.

[0047] A resource grid may be used to represent the frame structure. Each time slot may include a resource block (RB) (also called a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a number of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme. Figure 2 As illustrated in , some REs may include control information, for example, together with a demodulation RS (DMRS). Figure 2 It is also illustrated that the symbol(s) may include CSI-RS. Figure 2A symbol dedicated to DMRS or CSI-RS in indicates that the symbol includes DMRS or CSI-RS RE. Such a symbol may also include REs containing data. For example, if the number of ports of DMRS or CSI-RS is 1 and the comb-2 mode is used for DMRS / CSI-RS, half of the REs may include the RS, and the other half of the REs may include data. The CSI-RS resource may start at any symbol of the time slot and may occupy 1, 2, or 4 symbols, depending on the number of ports configured. The CSI-RS may be periodic, semi-persistent, or aperiodic (e.g., based on DCI triggering). For time / frequency tracking, the CSI-RS may be periodic or aperiodic. The CSI-RS may be transmitted in bursts of two or four symbols spread across one or two time slots. The control information may include sidelink control information (SCI). At least one symbol may be used for feedback, as described herein. The symbols before and / or after the feedback may be used to switch between data reception and feedback transmission. Although symbol 12 is illustrated as being used for data, it may instead be a gap symbol to enable turnaround for feedback in symbol 13. Another symbol (e.g., at the end of a slot) may be used as a gap. The gap enables the device to switch from operating as a transmitting device to preparing to operate as a receiving device (e.g., in a subsequent slot). As illustrated, data may be transmitted in the remaining REs. The data may include the data messages described herein. The location of any of the SCI, feedback, and LBT symbols may be the same as Figure 2 Different from the example illustrated in , multiple time slots can be grouped together. Figure 2 An example aggregation of two time slots is also illustrated. The number of time slots aggregated may also be greater than two. When time slots are aggregated, the symbols and / or gap symbols used for feedback may be different from the symbols and / or gap symbols used for feedback for a single time slot. Although feedback is not illustrated for this aggregation example, the symbol(s) in a multi-slot aggregation may also be allocated for feedback, as illustrated in the one time slot example.

[0048] Figure 3 3 is a block diagram of a first wireless communication device 310 in communication with a second wireless communication device 350, for example, via V2V / V2X / D2D communication. The device 310 may include a transmitting device that communicates with a receiving device (e.g., device 350) via V2V / V2X / D2D communication. The communication may be based on, for example, a side link. The device 310 may include a UE, an RSU, etc. The receiving device may include a UE, an RSU, etc. The packet may be provided to a controller / processor 375 that implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a media access control (MAC) layer.

[0049] The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection on the transport channel, forward error correction (FEC) encoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from channel estimator 374 may be used to determine coding and modulation schemes and for spatial processing. The channel estimates may be derived from a reference signal and / or channel condition feedback transmitted by device 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX may modulate an RF carrier with a corresponding spatial stream for transmission.

[0050] At the device 350, each receiver 354RX receives a signal through its respective antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for the device 350. If there are multiple spatial streams destined for the device 350, they can be combined into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then transforms the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, as well as the reference signal, are recovered and demodulated by determining the signal constellation point most likely transmitted by the device 310. These soft decisions can be based on the channel estimates calculated by the channel estimator 358. These soft decisions are then decoded and deinterleaved to recover the data and control signals originally transmitted on the physical channel by device 310. These data and control signals are then provided to controller / processor 359 which implements layer 3 and layer 2 functionality.

[0051] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer-readable medium. The controller / processor 359 may provide demultiplexing, packet reassembly, decryption, header decompression, and control signal processing between transport and logical channels. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0052] Similar to the functionality described in conjunction with transmissions performed by device 310, the controller / processor 359 may provide RRC layer functionality associated with system information (e.g., MIB, SIB) capture, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression, and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, resegmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0053] Channel estimates derived by a channel estimator 358 from a reference signal or feedback transmitted by the device 310 may be used by a TX processor 368 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354TX. Each transmitter 354TX may modulate an RF carrier with a corresponding spatial stream for transmission.

[0054] The transmission is processed at device 310 in a manner similar to that described in conjunction with the receiver functionality at device 350. Each receiver 318RX receives a signal through its respective antenna 320. Each receiver 318RX recovers the information modulated onto the RF carrier and provides the information to an RX processor 370.

[0055] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer readable medium. The controller / processor 375 provides demultiplexing, packet reassembly, decryption, header decompression, control signal processing between transport and logical channels. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0056] As an example, the device 350 may include a UE including a manipulation request component 398, the manipulation request component 398 being configured to send a request for a manipulation operation schedule to a manipulation coordinator (e.g., RSU 107). The device 310 may include a manipulation coordinator (e.g., RSU 107) including a manipulation coordination component 399, the manipulation coordination component 399 being configured to coordinate the manipulation of at least one UE and transmit the manipulation command to the requesting UE. As another example, the device 310 may include a UE, and the device 350 may include a manipulation coordinator. The TX processor 368, the RX processor 356, or the controller / processor 359 of the device 350, or at least one of the TX 316, the RX processor 370, or the controller / processor 375 may be configured to perform a combined Figure 1 The aspects described in 198 and 199.

[0057] Figure 4 An example 400 of wireless communication between devices based on V2X / V2V / D2D communication is illustrated. The communication may be based on a combination of Figure 2 The time slot structure of various aspects described. For example, a transmitting UE 402 (which may be associated with a vehicle or traveling in a vehicle) may transmit a transmission 414 (e.g., including a control channel and / or a corresponding data channel) that may be received by a receiving UE 404 (which may be traveling in a vehicle or associated with a vehicle). The control channel may include information for decoding the data channel and may also be used by the receiving device to avoid interference by suppressing transmission on occupied resources during data transmission. The number of TTIs and RBs that the data transmission will occupy may be indicated in a control message from the transmitting device. In addition to being able to operate as a receiving device, UEs 402 and 404 are each also able to operate as a transmitting device. Therefore, UE 404 is illustrated as transmitting a transmission 416. Transmissions 414 and 416 may be broadcast or multicast to nearby devices. For example, UE 402 may transmit communications intended to be received by other UEs within the range of UE 402.

[0058] UE 402, 404 may include a manipulation request component, similar to the combination of Figure 1 198 described.

[0059] UEs 402, 404 may be included in autonomous, semi-autonomous, or manually driven V2X-capable vehicles located at different parts of the intersection. Figure 4In example 400, UE 402 may be associated with or include an autonomous V2X-capable vehicle located on the north side of the intersection, and UE 404 may be associated with or include a semi-autonomous V2X-capable vehicle located on the south side of the intersection. As the two vehicles approach the center of the intersection, both UEs 402, 404 may transmit and receive data to and from each other in order to determine how to operate the vehicles to properly pass through the intersection. Communications between the vehicles may use a PC5 interface based on V2X communications, such as in conjunction with Figure 2 UE 402, 404 may share sensor information obtained at respective vehicles. The sensor information may provide additional information about the location and / or speed of other vehicles, the planned path of the vehicle, the intention of the vehicle, the physical capabilities of the vehicle, information based on detected objects or events by sensors, or based on input from other sensors.

[0060] However, for autonomous or semi-autonomous vehicles, vehicle operation at intersections or other locations can be challenging. Not all information can be detected by local sensors. For example, Figure 4 In example 400, other vehicles (e.g., vehicle 406) may not be capable of V2X communications. Figure 4 It is illustrated that a vehicle 406 without V2X capability is traveling on a road 432, which will intersect with a road 430, on which UEs 402 and 404 are traveling. Depending on the relative position of vehicle 406 relative to UEs 402 and 404, local sensors of vehicles associated with UEs 402 and 404 may not detect the presence of vehicle 406 when UEs 402 and 404 approach the intersection. Since vehicle 406 does not have V2X capability, vehicle 406 does not signal its presence and is unaware of the presence of vehicles associated with UEs 402 and 404 based on V2X communication. In addition, given the presence of mixed vehicles, some vehicles may not be equipped with sensors required for maneuvering operations. For example, high-performance sensors such as light detection and ranging (LiDAR) may be too expensive for use in many vehicles.

[0061] In addition, even with V2X-based sensor sharing, it may be difficult to ensure safe vehicle operation. For example, even with shared sensor information from multiple vehicles, it is not guaranteed that the combined sensor information is complete. For example, if the local sensor at the vehicle associated with UE 402 and 404 does not detect vehicle 406, the maneuvering information will still be incomplete despite the sharing of sensor information between UE 402 and 404. Moreover, the distributed autonomous driving logic may lead to an unstable state. For example, if a vehicle associated with UE 402 or UE 404 detects vehicle 406 and attempts to change its speed or direction, the change may cause a signaling storm to try to reach a distributed consensus between multiple vehicles with V2X capabilities. Changes in the planned speed and / or direction of the evasive vehicle can be propagated to nearby vehicles, causing these nearby vehicles to change their planned speed and / or direction. Nearby vehicles can then send their changed speed / direction to other vehicles, and so on. Additionally, powerful hardware will be required on each vehicle to support the handling of shared sensor information and the determination of vehicle manipulation based on such shared sensor information. Therefore, there is a need for improved operation of vehicles using V2X, V2V and / or other D2D communications. Aspects presented herein provide solutions to these problems through communication of UEs with a steering coordinator that provides centralized, dispatcher-based vehicle handling.

[0062] Figure 5 An example 500 of wireless communication between devices based on V2X / V2V / D2D communication including centralized, dispatcher-based vehicle maneuvering is illustrated. UE 502 may be similar to Figure 4 402 in the UE, and can directly transmit communications with other UEs (such as UE 504). Figure 4 In addition to the communication described between UE 402, 404, UE 502, 504 with V2X capability can also communicate with the steering coordinator. Figure 5 In the embodiment of the present invention, the maneuvering coordinator is illustrated as a roadside unit (RSU) 507, which is capable of receiving communications from multiple vehicles and providing coordinated vehicle maneuvering instructions. Thus, the RSU 507 can receive communications from the UE 502, 504 and / or transmit communications to the UE 502, 504. For example, the RSU 507 can communicate according to one or more V2X / V2V / D2D protocols and / or use corresponding frequency bands so that it can communicate with V2X / V2V / D2D enabled UEs. The RSU 507 may include a maneuvering coordination component, similar to the one in conjunction with the vehicle. Figure 1 199 of the description. Despite Figure 5The examples of use RSU to illustrate the example maneuvering coordinator, but other devices may also provide the maneuvering coordination capabilities described herein. Transmissions 514, 516, 518 may be broadcast or multicast to nearby devices. In other examples, at least one of 514, 516, or 518 may be unicast.

[0063] For example, UE 502, 504 may include vehicle user equipment (VUE). VUE may include an autonomous, semi-autonomous or manually driven vehicle with V2X capabilities. UE may be located at different parts of the intersection. For example, Figure 5 In example 500, UE 502 may be associated with or include an autonomous V2X-capable vehicle located on the north side of an intersection, and UE 504 may be associated with or include a semi-autonomous V2X-capable vehicle located on the south side of the intersection. When UE 502 and UE 504 approach the center of the intersection, at least one of UE 502, 504 may transmit data to RSU 507 and / or receive data from RSU 507 based on V2X communication to assist in maneuvering the vehicle through the intersection. This arrangement allows for centralized, dispatcher-based intersection handling via the RSU. Although this example is described in conjunction with an intersection, various aspects may be applied to various other locations, for example, including any of a highway entrance, a parking lot, a road entrance / exit, etc. The use of a centralized scheduling mechanism to coordinate the vehicle maneuvers of vehicles with V2X capabilities enables simplified operating logic to be used at the vehicle, because the vehicle can follow instructions from the RSU instead of determining its own maneuvers. The use of a centralized scheduling mechanism also avoids potential autonomous logic conflicts, such as potential logic conflicts between vehicles with different OEMs. The centralized scheduling mechanism reduces the need for advanced sensors on each vehicle. Such advanced sensors can be alternatively incorporated into the RSU that provides maneuvering coordination. The maneuvering coordinator (e.g., RSU) can be positioned in a manner that provides better road visualization, or can be connected to a plurality of different sensors on or around the road. For example, the sensor at the RSU can be located at a height above the vehicle passing by. The sensor can be located at a side of an intersection, an entrance / exit, a road, etc., a location that enables the vehicle to be identified on multiple roads. For example, RSU 507 can be able to detect vehicles on road 530 and road 532. In contrast, the vehicle is limited to traveling along the desired path. The simplification of logic requirements at the vehicle and the reduction of the need for advanced sensors at the vehicle reduce the cost of implementing autonomous vehicles (e.g., by using V2X assisted driving) and may also improve safety.

[0064] Prior to communicating with the RSU, the UE 502, 504 may be made aware of or otherwise identified to the RSU. As an example, the UE may identify the RSU as a steering coordinator using a location-based configuration. The UE may receive pre-configuration information including the locations of various steering coordinators. When the UE determines that it has entered a location corresponding to the location of one of the steering coordinators, the UE may attempt to communicate with the steering coordinator. As an example, the UE 502, 504 may be configured by the network (e.g., via a user plane with a base station). For example, referring to Figure 5 , RSU 507 may be directly connected to network 520, and UE 502 and 504 may receive configuration of the location where the UE should use the service of the steering coordinator from network 520 via base station 522 through corresponding Uu interfaces. The network may provide location information about multiple steering coordinators, or may provide information identifying a specific steering coordinator. For example, when UE 502 and UE 504 approach an intersection where the RSU is located, network 520 may communicate the presence of RSU 507 as a steering coordinator to UE 502, 504 through their respective Uu interfaces.

[0065] On the other hand, a discovery-based configuration may be used to make the UE aware of the RSU. In the discovery-based configuration, UE 502 and UE 504 may listen to broadcasts or beacons from the RSU via the PC5 interface. Figure 5 In the example of , RSU 507 may periodically broadcast or transmit a beacon via transmission 518. When UE 502 and UE 504 approach an intersection and receive the beacon in transmission 518, the UE may identify the presence of the RSU as a maneuvering coordinator. The beacon may distinguish an RSU that is capable of maneuvering coordination from other RSUs that may not be capable of maneuvering coordination. In addition to identifying the maneuvering coordinator, the UE may also perform a security check to confirm that the maneuvering coordinator is authorized to perform maneuvering coordination. Such authorization may be based, for example, on checking a security certificate associated with a declaration message from the maneuvering coordinator.

[0066] Once the UE has identified the presence of a maneuvering coordinator, such as RSU 507, the UE may communicate with the maneuvering coordinator. The UE may send a request to the RSU for a maneuvering schedule, e.g., for crossing an intersection, entering a road, stopping, etc. In one aspect, the UE may send the request via unicast signaling over the PC5 interface. The request may include information about the UE's intended path and / or operation. A unicast link may be established between the UE and the RSU based on the communication from the UE. For example, referring to Figure 5UE 502 and / or UE 504 may request maneuvering scheduling services from RSU 507 through the PC5 interface by sending information about the intended path and / or operation of the vehicles (e.g., the first vehicle intends to go straight through the intersection, the second vehicle intends to turn left, etc.) using the unicast link established by each device.

[0067] The RSU then schedules the operation of the vehicle in the desired path. The RSU may schedule the vehicle based on communications received from multiple vehicles passing a location and / or based on sensor information that helps the RSU detect the presence, location, and / or speed of other vehicles. The sensor information may be sensor information obtained at the RSU and / or sensor information received in reports from the vehicle. In one aspect, the RSU may send instructions to the UE via PC5, for example, via unicast signaling, broadcast signaling, and / or multicast signaling. For example, in Figure 5 In the example of , the RSU may schedule UE 504 to slow down and / or stop before turning left until UE 502 completes the straight pass through the intersection. When the RSU transmits and receives data for coordinating maneuvering schedules, the scheduling logic may be processed remotely (e.g., using cloud computing) or locally (e.g., within the RSU itself).

[0068] The RSU can also use its sensors and reports transmitted from the UE to determine the scheduling. Figure 5 , vehicle 506 is a non-V2X capable device located on the east side of the intersection. Since vehicle 506 does not transmit and receive data based on V2X communication, the RSU includes one or more sensors (camera, radar, LiDAR, ultrasonic, etc.) to detect and predict the maneuvers of vehicle 506 as it approaches the center of the intersection.

[0069] In some examples, a request for a manipulation schedule to the RSU may be sent by an upper layer of the UE, such as an application layer or a middleware layer of the UE (e.g., a network layer or an access layer). The request may also be sent in a message, such as a basic safety message (e.g., BasicSafetyMessage or other names), or other message formats defined, for example, under the Society of Automotive Engineers (SAE), SAE China (C-SAE), China Communications Standards Association (CCSA), and / or Collaborative Intelligent Transport System (C-ITS). Similarly, data from the RSU for coordinating the manipulation schedule may be received by an upper layer of the UE (e.g., an application layer or a middleware layer of the UE). Data from the RSU may also be received in a message, such as a signal phase and timing / mapping message (e.g., SPaT / MAP or other names), or other message formats defined, for example, under SAE, C-SAE, CCSA, and / or C-ITS. In one example, the upper layers of the UE may receive a signature or other fields (e.g., a Provider Specific Service Identifier (PSID) or an Intelligent Transportation System Application Identifier (ITS-AID)) identifying a certificate associated with the dispatch operation application for the UE to perform security checks on the RSU. Other communications between the UE and the RSU (such as those described below with reference to Figure 6 and 7 Those described in the signaling sequence of ) can be performed by the upper layers of the UE.

[0070] Figure 6 An example communication flow 600 is illustrated between an RSU 604 operating as a maneuvering coordinator and UEs 606, 608 and vehicles 610 within range of the RSU 604. Although the maneuvering coordinator is illustrated as an RSU, other devices may also perform maneuvering coordination. The communication may be based on V2X, V2V, or other D2D-based direct communications between the RSU and the UE. In one aspect, Figure 6 Logo combination Figure 5 A signaling sequence for centralized, dispatcher-based intersection handling is described, wherein the UEs include a first V2X-capable UE 606 (e.g., which may be associated with a vehicle or may include a vehicle), a second V2X-capable UE 608 (e.g., which may be associated with a vehicle or may include a vehicle), and a non-V2X-capable vehicle 610.

[0071] In one aspect, the network 602 may optionally configure one or more V2X-capable UEs (e.g., UEs 606, 608) to use a coordinated scheduling pattern by transmitting a configuration 612. The network 602 may configure the UEs (e.g., UEs 606 and 608) to use the coordinated scheduling pattern when the UEs are within range of a particular location. Thus, the UEs 606 and 608 may identify a steering coordinator, such as RSU 604, based on the current location of the UE in combination with information from the configuration 612. For example, referring to Figure 6 , when the UE 608 enters the intersection where the RSU is located, the network 602 may configure the UE 608 to be scheduled using the RSU 604. The RSU 604 may be permanently installed or may include a mobile RSU. For example, the network 602 may be an EPC, and the RSU scheduling may be included in the V2X configuration transmitted from the V2X control function of the EPC. As another example, the network 602 may be another type of core network (e.g., a 5G-based core network), and the configuration 612 may be transmitted from the policy control function (PCF) of the core network through the control plane using non-access stratum (NAS) layer signaling. As another example, the configuration may be stored in a component of the UE (e.g., a subscriber identity module (SIM) or a universal SIM (USIM) card, or an embedded SIM (eSIM)), or in the UE itself.

[0072] Configuration 612 may also be sent from a V2X application server outside the EPC or core network. Figure 6 , the manufacturer of UE 606 may pre-configure the UE for V2X operation and RSU scheduling by running a V2X application server before the UE 606 enters a location such as an intersection. Figure 6 As illustrated in , in one aspect, the network 602 may not transmit the RSU scheduling configuration to the UE 606, but may transmit the RSU scheduling configuration to the UE 608.

[0073] In another aspect, the RSU 604 may optionally announce its presence and / or ability to perform scheduling of vehicle maneuvers to V2X-capable UEs. Figure 6 As illustrated, the RSU 604 may transmit an announcement (e.g., transmission 614 and / or 615). The RSU 604 may broadcast a transmission or beacon, for example, using a special system information block (SIB) or a periodic service announcement message, to monitor for V2X-capable UEs 606 and UEs 608 in an intersection within range of the RSU. When the UEs 606 and 608 receive the transmissions 614, 615, they may identify the presence of the RSU and / or the RSU's ability to manipulate scheduling.

[0074] The beacons or transmissions 614, 615 may include a high definition (HD) local map to assist the UEs 606 and 608 in providing information about their desired operations. For example, the HD local map may provide information about where the RSU 507 is located. Figure 5 Information of the illustrated intersection. Since the RSU can provide maneuvering schedules at locations other than intersections, the map can provide information about road entrances / exits, parking lots, etc.

[0075] In one aspect, when the UE becomes aware of the RSU by configuring 612 and / or announcing (e.g., transmissions 614, 615), the UE may confirm the RSU's authority to perform manipulation scheduling by performing a security check. The UE may perform a security check before requesting a scheduling service from the RSU. This security check can help ensure that the RSU is authorized to perform manipulation operation scheduling. For example, when UE 606 or UE 608 receives transmission 614 or 615 from RSU 604, the transmission may include a signature or other field (e.g., a specific provider service identifier (PSID) or an intelligent transportation system application identifier (ITS-AID)) identifying a certificate associated with a scheduling operation application, which the UE may use to confirm the presence and scheduling capabilities of the RSU.

[0076] After identifying the presence of a maneuver coordinator (e.g., RSU 604) and / or performing a security check, a V2X-capable UE 606, 608 may send a request 616 for a scheduled maneuver to the RSU. This message (e.g., request 616) requests service from the RSU and may include any of the following: the mechanical capabilities of the corresponding UE (e.g., vehicle type, braking distance), the planned path of the UE (e.g., based on an HD local map or navigation information of the UE), the location of the UE, or the speed of the UE. This scheduling request message may also include the necessary access stratum (AS) layer information to establish a unicast V2X link between the RSU and the UE, including, for example, the UE's layer 2 identifier (L2 ID), a transmission (Tx) profile, and a quality of service (QoS) level. The Tx profile may indicate how the UE may receive the RSU's maneuvering commands, as discussed in detail below.

[0077] For example, refer to Figure 6 , when UE 606 approaches the intersection where RSU 604 is located, UE 606 may send a request for a scheduled maneuver to RSU 604 to request service from RSU 604. The request may indicate the UE's vehicle type, braking distance and / or other mechanical capabilities, its planned path (e.g., going straight through the intersection or turning to a street leaving the intersection), and its location (e.g., north side of the intersection, which lane). The request may also include the UE's AS layer information for forming a unicast link with the RSU so that UE 606 can receive the RSU's maneuver command.

[0078] Other V2X-capable UEs may optionally announce their intention to maneuver to the RSU 618. For example, Figure 5 As illustrated in , UE 504 may approach an intersection where RSU 507 is located at approximately the same time as UE 502. However, UE 504 may not send a request for a scheduled maneuver to RSU 507, but may instead announce its intent to maneuver. Figure 6 As illustrated, around the time when the UE 606 sends a request 616 for a scheduled maneuver to the RSU 604, the UE 608 may announce its intention 618 for the maneuver (including its mechanical capabilities and planned path (e.g., the UE 608 is traveling at a certain speed and intends to turn left)), and the RSU 604 may monitor and receive the UE's announcement information (e.g., the intention of the maneuver 618). Alternatively, similar to the request 616, the UE 608 may also request RSU scheduling by sending a request for a scheduled maneuver to the RSU 604.

[0079] The RSU 604 may also optionally detect manipulation of a non-V2X capable UE using sensors such as illustrated at 620. Figure 5 As illustrated, vehicle 506 may be a non-V2X capable UE approaching an intersection where RSU 507 is located, and therefore may not send a request for a scheduled maneuver or announce an intent to maneuver to RSU 507. Figure 6 As shown, the RSU may detect the maneuvers (e.g., speed and path) of a vehicle 610 that does not have V2X capabilities using sensors equipped at the RSU and / or at the intersection and / or using reports or sensor information received from UEs (such as UEs 606, 608). Such sensors may include, for example, any of cameras, radars, LIDARs, road sensors, and / or traffic lights, etc. The RSU 604 may also use these sensors to collect information about the environment of the intersection.

[0080] As illustrated at 622, the RSU 604 may determine at least one maneuver for a nearby UE. The RSU 604 may provide information scheduling the maneuver for the UE to the UE. The RSU 604 may determine maneuvers for multiple UEs and may schedule the UEs to operate in a manner that enables all UEs to move in their desired paths in a coordinated manner. For example, referring to Figure 6, RSU 604 may determine a maneuver for UE 606 based on information collected from UE 606, 608 and vehicle 610, for example, UE 606 may go straight through the intersection after UE 608 turns left and before vehicle 610 turns right. The information collected by RSU 604 for scheduling maneuvers may be based on data received from UEs in V2X communications and local sensor readings. This information may also be based on remote traffic monitoring and control center commands.

[0081] After the RSU 604 determines the scheduled maneuver, the RSU 604 transmits a scheduled maneuver response 624 to the requesting UE 606 and / or 608. The scheduled maneuver response 624 may be transmitted using a unicast link between the UE and the RSU 604. Figure 6 As illustrated, the RSU 604 may send a scheduled maneuver response 624 to the UE 606, which includes a maneuver command notifying the UE 606 of its scheduled maneuver (e.g., the vehicle may proceed straight through the intersection after another vehicle turns left and before a third vehicle turns right). The maneuver command may list all necessary operations that the UE 606 will need to perform the maneuver, such as the duration of the determined UE speed and the time and / or location at which the UE 606 may turn or change lanes. For example, the scheduled maneuver response transmitted to the UE 606 may command the UE to slow down and / or stop before continuing through the intersection until the vehicle 2 completes the left turn.

[0082] Figure 7 Another example communication flow 700 is illustrated between an RSU 704 operating as a maneuvering coordinator and UEs 706, 708 and vehicles 710 within range of the RSU 704. Although the maneuvering coordinator is illustrated as the RSU 704, other devices may also perform maneuvering coordination. The communication may be based on V2X, V2V, or other D2D-based direct communications between the RSU and the UE. In one aspect, Figure 7 Logo combination Figure 4 , 5 6, wherein the UE includes a V2X-capable UE 706 (e.g., which may be associated with or may include a vehicle), a V2X-capable UE 708 (e.g., which may be associated with or may include a vehicle), and a non-V2X-capable vehicle 710. Figure 6 Describes the communication with Figure 6 The same reference numerals are used to mark the same reference numerals.

[0083] although Figure 6UE 608 is illustrated as providing a declaration of its intended maneuver, but UE 708 may send a request 718 for a scheduled maneuver to RSU 704. This request may be similar to that described in reference to Figure 6 The request described in request 616 in . Therefore, in Figure 7 , multiple UEs send requests for maneuver scheduling to the RSU 704. For example, when the UE 706 approaches the intersection where the RSU 704 is located, the UE 706 may send a request 616 for a scheduled maneuver to the RSU 704 to request a service from the RSU 704, and when the UE 708 approaches the intersection where the RSU 704 is located, the UE 708 may also send a request 718 for a scheduled maneuver to the RSU 704 to request a service from the RSU 704.

[0084] In one aspect, each request 616, 718 may inform the RSU of the V2X transmission and reception capabilities of the corresponding UE, for example, via the transmission (Tx) profile of the corresponding UE. The Tx profile indicates how the corresponding UE can receive the steering commands of the RSU and may be different for different UEs. For example, the transmission profile may include information such as, but not limited to, the supported modulation schemes (e.g., 16QAM or 64QAM), supported radio access technologies (RATs) (e.g., LTE or 5G), supported communication interfaces (e.g., PC5), and supported multiple-input multiple-output (MIMO) operation modes (e.g., transmit diversity) of the UE. Therefore, in Figure 7 In example 700 of FIG. 700 , request 616 from UE 706 may include a Tx profile indicating that UE 706 is capable of receiving 64QAM modulated data over a PC5 interface in a new radio (NR) / 5G RAT, and request 718 from UE 708 may include a Tx profile indicating that UE 708 is capable of receiving only 16QAM modulated data over a PC5 interface in a LTE / 4G RAT. The request for scheduled manipulation may also include a reference to Figure 6 Other information described in request 616.

[0085] As combined Figure 6 As described, at 622 the RSU 704 may determine and schedule a maneuver for the requesting vehicle.

[0086] After the RSU 704 determines the scheduled maneuver, the RSU 704 transmits a scheduled maneuver response 724, 725 to one or more requesting UEs. Figure 7, the RSU 704 may broadcast the steering information to any requesting UE, for example, rather than sending the steering information directly to a specific UE in a unicast link. The RSU 704 may send a response 724 to the UE 706, the response 724 including the steering ID of the UE 706 and / or the transmission profile of the UE 706. The response 724 may be sent via a unicast link between the RSU 704 and the UE 706. Similarly, the RSU 704 may send a response 725 to the UE 708, the response 725 including the steering ID of the UE 708 and / or the transmission profile of the UE 708. Thus, the response(s) 724, 725 may not include a steering command, but may instead include information that enables each UE 706, 708 to identify the steering command from the broadcast / multicast transmission 726. The RSU 704 may balance the transmission / reception capabilities of all UEs requesting scheduling, and may send a response to inform each UE of the Tx profile and a steering identifier for the corresponding UE to receive a separate steering command. The Tx profile indicates to the UE the format that the RSU 704 will use for steering command transmission. The steering identifier allows the UE to identify a steering command intended for a specific UE among multiple steering commands broadcast / multicast from the RSU.

[0087] For example, Figure 7 As illustrated, the RSU 704 may send a scheduled steering response to the UE 706, thereby informing the UE of the Tx profile for steering command transmission based on the transmission / reception capabilities of the UE received in the request 616, and a unique steering ID for receiving the steering command in the transmission. Similarly, the RSU 704 may send a scheduled steering response to the UE 708, thereby informing the UE 708 of the Tx profile for steering command transmission based on the transmission / reception capabilities of the UE received in the request 718, and a unique steering identifier for receiving the steering command in the transmission.

[0088] At 726, RSU 704 may broadcast or multicast a steering command intended for at least one of the multiple UEs requesting steering scheduling. The broadcast may include an aggregation of multiple steering commands intended for multiple UEs requesting scheduling. Each steering command in the broadcast may include a corresponding identifier (i.e., Rx ID1, Rx ID2, etc.) corresponding to one of the steering identifiers provided to each UE in the response 724, 725. Therefore, UE 706 or 708 can look for its steering identifier in the broadcast / multicast from the RSU. When the UE identifies the assigned steering ID, the UE can determine that the associated steering command is intended for the UE. The steering command can be broadcast / groupcast / multicast using the Tx profile features announced to the UE in the response 724 / 725.

[0089] For example, Figure 7As illustrated, RSU 704 broadcasts a maneuver command to UE 706 and UE 708, the maneuver command including Rx ID1 and corresponding maneuver command 1, Rx ID2 and corresponding maneuver command 2. ID1 and ID2 correspond to the respective maneuver identifiers transmitted to UE 706 and UE 708 in responses 724, 725. ID 1 informs UE 706 that command 1 is for UE 706. ID 2 informs UE 708 that command 2 is for UE 708. For example, command 1 may indicate that UE 706 should go straight through an intersection, for example, at an indicated time, while command 2 may indicate that UE 708 should turn left at an intersection, for example, at an indicated time. Since the UEs know their respective maneuver identifiers and the Tx profiles used for broadcast transmissions from responses 724, 725, UE 706 and UE 708 can receive their scheduled maneuver commands from the RSU's message.

[0090] In one aspect, the RSU 704 may send steering commands in different channels or transmission formats. For example, as described above with reference to Figure 7 As described, the Tx profile for UE 706 may indicate that UE 706 is capable of receiving 64QAM modulated data through the PC5 interface in New Radio (NR) / 5G RAT, while the Tx profile for UE 708 may indicate that UE 708 is capable of receiving only 16QAM modulated data through the PC5 interface in LTE / 4G RAT. Therefore, RSU 704 may divide its steering command message and transmit it to each UE in different channels (LTE and NR) on the PC5 interface using different modulation schemes. In addition, even if each UE can receive the steering command message on the same channel, RSU 704 may still transmit it on different channels to increase data reliability.

[0091] Therefore, the RSU-based scheduling mechanism described above provides coordinated maneuvers for all V2X-capable vehicles adjacent to the RSU, thereby providing several advantages. For example, autonomous vehicles require simpler operating logic, which only needs to follow the instructions transmitted by the RSU. Therefore, potential autonomous logic conflicts from different vehicle original equipment manufacturers (OEMs) are avoided. In addition, since only the RSU needs to be equipped with sensors for coordinating intersection handling, each vehicle does not require advanced sensors for maneuvering operations. Each vehicle does not require expensive and complex hardware, only V2X assisted driving, and can therefore achieve autonomous driving at a lower cost.

[0092] Although the above examples relate to the use of an RSU-based scheduling mechanism for UEs at intersections, the present invention is not limited to use at intersections. For example, RSUs may be used at the entrance and exit of a highway to coordinate the maneuvers of UEs entering or exiting the highway. In addition, RSUs may be used in parking lots (e.g., outdoor parking lots, indoor parking garages) to manage the maneuvers of UEs entering and exiting the parking lots.

[0093] A fixed RSU can operate as a manipulation coordinator. Similarly, a mobile RSU can operate as a manipulation coordinator. For example, a mobile RSU can be a temporary command center vehicle for special or emergency situations (such as accident handling or special events). The mobile RSU can also be connected to a command center for remote, manually controlled operations. As another example, the manipulation coordinator can be another mobile device authorized to perform coordinated manipulation scheduling. For example, the manipulation coordinator may include a mobile terminal (e.g., UE) that can be connected to the network via Uu or a wide area network (WAN).

[0094] In a further example, the mobile RSU may also be authorized to perform scheduling for UE manipulation. For example, as described above with reference to a fixed RSU, the RSU may include a certificate (e.g., a specific PSID / ITS-AID) associated with the scheduling operation application that is transmitted to the UE. The US may then perform a security check on this certificate information before the UE requests service from the RSU.

[0095] The maneuvering coordinator may also include dispatching functionality at a different location than the fixed or mobile RSUs. When the RSUs transmit and receive data for coordinating maneuvering dispatching, the dispatching logic may be processed remotely (e.g., using cloud computing) or locally (e.g., within the RSUs themselves). In one aspect where the dispatching logic is processed remotely, the dispatching functionality may be located in the cloud, or remote from the actual site it manages (e.g., an intersection, a freight station, an automated parking garage, etc.). For example, referring to Figure 5 , the RSU scheduling function 540 may be an element within the network 520 that broadcasts the steering information to the UE 502 or 504 via the RSU 507 via the PC5 (V2X) interface. Figure 5 As illustrated, the RSU 507 may be directly connected to the scheduling function 540, or the RSU may be connected to the scheduling function 540 via the base station 522. Alternatively, the scheduling function of the RSU may be an element in the RSU itself.

[0096] The maneuvering coordinator may also include a dispatching function that allows for manual input. Fixed or mobile RSUs may be connected to a command center for remote, manually controlled operation, and the information collected by the RSUs for dispatching maneuvers may be based on remote traffic monitoring and control center commands. In one aspect, dispatching may be manually controlled by humans. In another aspect, the dispatching logic may be semi-automated or automated. The dispatching logic may also be executed remotely (e.g., using cloud computing) as previously described, or locally (e.g., within the RSU itself). For example, referring to Figure 5 , the dispatch function 540 of the RSU may be an element within the network 520 that is manually or semi-manually controlled by an operator to dispatch vehicle maneuvers.

[0097] Fig. 8A and 8B 800 is a flowchart of a wireless communication method. The method may be performed by a UE (e.g., UE 104, 402, 404, 502, 504, 606, 608, 706, 708, 1250, 1260; device 310, 350; device 902 / 902'; processing system 1014, which may include a memory and which may be the entire UE or a component of the UE), which transmits and receives data from a steering coordinator. The method may be performed by a UE or a component of the UE, and the component of the UE may include an upper layer component of the UE. For example, the method may be performed by an application layer or a middleware layer of the UE. The steering coordinator may include a road side unit (RSU) (e.g., RSU107, 507, 604, 704, 950) or other device (e.g., device 310 or 350). The steering coordinator may include a mobile terminal. Dashed lines are used to illustrate optional aspects. The method allows a UE to receive coordinated maneuvers for V2X-capable vehicles in proximity to an RSU.

[0098] At 802, the UE receives a configuration for manipulating a scheduling mode from the network. For example, 802 may be received from Fig. 9 In operation according to one aspect, a location-based configuration may first be used to make a UE (e.g., a vehicle with V2X capabilities) aware of the RSU. In the location-based configuration, the UE 502, 504 may be configured by the network (e.g., via a user plane), for example, as in conjunction with Figure 5 520 and Figure 6 For example, referring to Figure 5, RSU 507 may be connected to network 520, and UE 502 and 504 may be connected to network 520 through corresponding Uu interfaces via base station 522. When a UE (e.g., 502 or 504) approaches an intersection where an RSU is located, network 520 may communicate the presence of RSU 507 to UE 502, 504 through their respective Uu interfaces.

[0099] For example, in LTE, the network may be an EPC, and RSU scheduling may be included in a V2X configuration transmitted from a V2X control function of the EPC. As another example, in 5G, the network may be a core network, and the RSU scheduling configuration may be transmitted from a policy control function (PCF) of the core network on a control plane. The configuration may be stored in a component of the UE (e.g., a SIM card), or in the UE itself.

[0100] At 804, the UE may identify the steering coordinator based on the configuration received from the network before requesting the service for steering scheduling. For example, 804 may be received from Fig. 9 The configuration is performed by the identification component 910 of the UE. The configuration configures the UE to use the steering scheduling mode based on the location of the UE. Figure 6 In one aspect of 612, the network 602 may optionally configure the V2X-capable UE for use of the RSU scheduling mode, such as in conjunction with Figure 5 and / or the position described in 6. For example, referring to Figure 6 , when UE 608 enters the location where the RSU is installed, network 602 may configure UE 608 to use RSU 604 scheduling.

[0101] At 806, the UE may identify the steering coordinator based on preconfigured location information about the steering coordinator and the location of the UE before requesting the service for steering scheduling. For example, 806 may be provided by Fig. 9 The RSU scheduling configuration can be sent from the V2X application server. For example, refer to Figure 6 , the manufacturer of UE 606 can preconfigure its UE to perform V2X operations and RSU scheduling at various locations.

[0102] At 808, the UE may receive a notification message from the control coordinator, such as in conjunction with Figure 5 and 6 For example, 808 may be provided by Fig. 9 For example, in one aspect, a discovery-based configuration may be used to make the UE aware of the RSU. In the discovery-based configuration, the UE 502 or 504 may listen to broadcasts or beacons from the RSU via the PC5 interface. Figure 5 In the example of , RSU 507 may periodically broadcast or transmit a beacon. When a UE 502 or 504 monitoring the transmission approaches an intersection, the UE receives the beacon and may identify the presence of the RSU.

[0103] The announcement transmission or beacon may include map information (e.g., a high definition (HD) local map or other local map) for use in steering scheduling between the UE and the steering coordinator. Figure 6 As shown, the beacon of RSU 604 transmitted to UE 606 and UE 608 may include an HD local map identifying information about the intersection at which the RSU is located.

[0104] At 810, the UE identifies the steering coordinator based on the announcement message before requesting the service for steering scheduling. For example, 810 may be from Fig. 9 The maneuvering coordinator may include an RSU. The maneuvering coordinator may include a scheduling function at a location different from the RSU. The maneuvering coordinator may include a scheduling function that implements user input (e.g., manual input). For example, the RSU may optionally announce its presence and ability to perform scheduling of vehicle maneuvers to a UE having V2X capabilities in transmission 614. The process is based on reference Figure 5 For example, Figure 6 As illustrated in , the RSU 604 announces or broadcasts a transmission or beacon to monitor for V2X-capable UEs 606 and UEs 608 in the intersection within range of the RSU. When the UEs 606, 608 receive the transmission, they are made aware of the RSU and its steering scheduling capabilities.

[0105] At 812, the UE may perform a security check to verify that the maneuver coordinator is authorized to schedule maneuvers before requesting the service for maneuver scheduling. For example, 812 may be performed by a Fig. 9 In one aspect, when the UE passes Figure 6 When the RSU is made aware of the configuration 612 and / or transmission 614 of the UE, the UE may confirm the presence of the RSU and perform a security check before requesting scheduling services from the RSU. This security check ensures that the RSU is authorized to perform the maneuvering operation scheduling. For example, when the UE 606 or UE 608 receives a beacon transmission from the RSU 604, the transmission may include a signature or other field identifying a certificate associated with the scheduling operation application (e.g., a provider-specific service identifier (PSID) or an intelligent transportation system application identifier (ITS-AID)), which the UE may use to confirm the presence and scheduling capabilities of the RSU.

[0106] At 814, the UE wirelessly requests a service for maneuvering scheduling of the vehicle from the maneuvering coordinator via a direct communication link between the UE and the maneuvering coordinator. Fig. 9 The direct communication link may be based on vehicle-to-everything (V2X) communication, and the vehicle may include, for example, one of an autonomous, semi-autonomous, or manually driven vehicle. The UE may request from the maneuvering coordinator a service for maneuvering scheduling for at least one of crossing an intersection, entering a road, leaving a road, parking, etc. For example, once the UE is made aware of the RSU, the UE may send a request for intersection operation scheduling to the RSU. In one aspect, the UE may send the request via unicast signaling over the PC5 interface. The request may include information about the UE's expected path or other operational information about the UE. A unicast link may be established between the UE and the RSU based on the request. For example, in combination with Figure 5 and Figure 6 As described, UE 502 or UE 504 may request service from RSU 507 via the PC5 interface using the unicast link established by each device with information about the intended path or operation of the device (eg, vehicle 1 intends to go straight, vehicle 2 intends to turn left, etc.).

[0107] At 816, the UE may wirelessly send at least one of the expected path of the UE, the mechanical capabilities of the UE, or the speed of the UE to the maneuvering coordinator via the direct communication link. For example, 816 may be sent from Fig. 9 Although illustrated as being separate from block 814, this information may also be included within block 814. For example, in conjunction with Figure 6 As described in request 616 of , one or more V2X-capable UEs may send a request for a scheduled maneuver to the RSU. This message requests service from the RSU and includes the mechanical capabilities of the UE (e.g., vehicle type, braking distance), the planned path of the UE (e.g., based on an HD local map or navigation information of the UE), and the location and / or speed of the UE, etc.

[0108] At 818, the UE may wirelessly send link information to the steering coordinator via a direct communication link to establish a unicast link. For example, 818 may be sent from Fig. 9 Although illustrated as being separate from block 814 and the information sent at 816, this link information may also be transmitted with the request sent at 814 and / or the information sent at 816. The steering information may then be received from the steering coordinator via the unicast link. The link information may include at least one of a layer 2 identifier (L2 ID), a transmission profile, a radio access technology (RAT) capability, or a quality of service profile. For example, referring to Figure 6, when UE 606 approaches the intersection where RSU 604 is located, the UE may send a request for a scheduled maneuver to the RSU to request service from the RSU. This scheduling request message includes the necessary access stratum (AS) layer information to establish a unicast V2X link between the RSU and the UE, including, for example, the UE's layer 2 identifier (L2 ID), transmission (Tx) profile, and quality of service (QoS) level.

[0109] In one aspect, the request from the UE may inform the RSU of the UE's V2X transmission and reception capabilities via the UE's transmission (Tx) profile. The Tx profile indicates how the UE may receive the RSU's steering commands and may be different for different UEs. For example, the transmission profile may include information such as, but not limited to, the UE's supported modulation schemes (e.g., 16QAM or 64QAM), supported radio access technologies (RATs) (e.g., LTE or 5G), supported communication interfaces (e.g., PC5), and supported multiple-input multiple-output (MIMO) operation modes (e.g., transmit diversity). Therefore, in Figure 7 In example 700 of , the request from UE 706 may include a Tx profile indicating that UE 706 is capable of receiving 64QAM modulated data over a PC5 interface in a new radio (NR) / 5G RAT, and the request from UE 708 may include a Tx profile indicating that UE 708 is capable of receiving only 16QAM modulated data over a PC5 interface in a LTE / 4G RAT. The request for scheduled manipulation may also include a reference to Figure 6 Other information described in request 616.

[0110] At 820, the UE may receive an identifier of the UE in a message from the steering coordinator before receiving the steering information. For example, 820 may be received by Fig. 9 The receiving component 904 of the embodiment can be executed. The manipulation information can be received from the manipulation coordinator via broadcast, multicast or groupcast using the identifier of the UE. For example, referring to Figure 7 In response 724, after the RSU determines the scheduled steering, the RSU may transmit a scheduled steering response to the requesting UE. The steering identifier allows the UE to receive its steering command from the transmission.

[0111] For example, Figure 7 As illustrated, RSU 704 may send a scheduled steering response to UE 706, notifying the UE of a unique steering identifier for receiving the UE's steering commands in transmission. Similarly, RSU 704 may send a scheduled steering response to UE 708, notifying the UE of a unique steering identifier for receiving the UE's steering commands in transmission.

[0112] At 822, the UE may receive a transmission profile in the message from the steering coordinator. For example, 822 may be received from Fig. 9 The receiving component 904 of the embodiment can be executed. The manipulation information can be received from the manipulation coordinator via broadcast, multicast or groupcast based on the transmission profile. For example, referring to Figure 7 After the RSU determines the scheduled steering, the RSU may transmit a scheduled steering response to the requesting UE 724. The Tx profile indicates to the UE the format that the RSU will use for steering command transmission.

[0113] For example, Figure 7 As illustrated, the RSU 704 may send a scheduled steering response to the UE 706 based on the transmission / reception capabilities of the UE received in the request 616, thereby informing the UE of the Tx profile for the steering command transmission. Similarly, the RSU 704 may send a scheduled steering response to the UE 708 based on the transmission / reception capabilities of the UE received in the request 718, thereby informing the UE of the Tx profile for the steering command transmission.

[0114] At 824, the UE wirelessly receives steering information from the steering coordinator via the direct communication link. For example, 824 may be received from Fig. 9 For example, referring to Figure 6 At 624, after the RSU determines the scheduled manipulation, the RSU transmits a scheduled manipulation response to one or more requesting UEs. Figure 6 As illustrated, the RSU 604 sends a scheduled maneuver response to the UE 606, which includes a maneuver command notifying the UE of its scheduled maneuver (e.g., vehicle 1 may proceed straight through the intersection after vehicle 2 turns left and before vehicle 3 turns right). The maneuver command may list all necessary operations that the UE will need to perform for the maneuver, such as the duration of the determined UE speed and the time and / or location at which the UE may turn or change lanes. For example, the scheduled maneuver response transmitted to the UE 606 may command the UE to slow down and / or stop before continuing through the intersection until vehicle 2 completes the left turn.

[0115] As another example, refer to Figure 7 At 726, the RSU may announce a grouping command to multiple UEs requesting scheduling. Figure 7As illustrated, RSU 704 broadcasts a maneuver command to UE 706 and UE 708, the maneuver command including Rx ID1, Command 1, Rx ID2, and Command 2. Rx ID1 and Rx ID2 correspond to respective maneuver identifiers transmitted to UE 706 and UE 708 in responses 724, 725. Command 1 and Command 2 correspond to respective maneuver commands that inform UE 706 and UE 708 of their scheduled maneuvers determined at 622. For example, Command 1 may instruct Vehicle 1 to go straight through the intersection, while Command 2 may instruct Vehicle 2 to turn left at the intersection.

[0116] Finally, at 826, the UE applies the manipulation information. For example, 826 may be provided by Fig. 9 The manipulation information component 918 is used to perform. For example, Figure 6 In the maneuver command received at 624, the UE can operate the vehicle based on the maneuver command received from the maneuver coordinator, for example, slowing down and / or stopping before going straight through the intersection until vehicle 2 completes the left turn and before vehicle 3 starts to turn right.

[0117] Fig. 9 is a conceptual data flow diagram 900 illustrating the data flow between different devices / components in an example apparatus 902. The device may be a UE or a component of a UE. Figure 5 and Figure 6 , the UE may include a UE with V2X capability (e.g., UE 104, 502, 504, 606, 608, 706, 708 or device 310, 350).

[0118] The device 902 includes a receiving component 904 that receives wireless communications (e.g., based on V2X, V2V, D2D, etc.). The receiving component can be configured to receive a configuration of a steering coordinator 950 for a steering scheduling mode from a network 906, and / or receive pre-configured location information about the steering coordinator from a V2X application server 908. The receiving component 904 also receives an announcement message from the steering coordinator (which may include an HD local map), a data transmission (which may include a certificate indicating that the steering coordinator is authorized to perform scheduling), a message from the steering coordinator via broadcast, multicast, or groupcast (i.e., a scheduled steering response) (which may include an identifier of the UE (i.e., a steering identifier) ​​and a transmission profile (Tx profile)), and steering information (e.g., a steering command).

[0119] The device 902 may include an identification component 910 that identifies the maneuvering coordinator 950 based on a configuration received from the network 906, based on pre-configured location information from the V2X application server 908 and the location of the UE, and / or based on an announcement message from the maneuvering coordinator 950. The device 902 may further include a verification component 912 that performs a security check, such as based on a certificate in a data transmission received from the maneuvering coordinator to verify that the maneuvering coordinator is authorized to schedule the maneuver.

[0120] The device 902 may include a request component 914, which wirelessly requests the service of the maneuvering scheduling of the vehicle to the maneuvering coordinator 950 through a direct communication link between the device / UE and the maneuvering coordinator. The device 902 further includes a transmission component 916, which wirelessly sends a request (i.e., a request for scheduled maneuvering) to the maneuvering coordinator through a direct communication link, and the request includes at least one of the expected path of the UE, the mechanical capability of the UE, or the speed or position of the UE. The transmission component 916 also wirelessly sends link information (e.g., AS layer information including a Tx profile) to the maneuvering coordinator 950 through a direct communication link to establish a unicast link. In addition, the device 902 includes a manipulation information component 918, which applies the manipulation information received from the manipulation coordinator.

[0121] The apparatus may include executing Fig. 8A and 8B The additional components of each box of the algorithm in the preceding flowchart. Thus, Fig. 8A and 8B Each block in the aforementioned flow chart may be performed by a component and the device may include one or more of those components. These components may be one or more hardware components specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0122] Fig.101 is a diagram 1000 illustrating an example of a hardware implementation of a device 902' employing a processing system 1014. The processing system 1014 may be implemented with a bus architecture generally represented by a bus 1024. Depending on the specific application and overall design constraints of the processing system 1014, the bus 1024 may include any number of interconnecting buses and bridges. The bus 1024 links together various circuits including one or more processors and / or hardware components (represented by the processor 1004, components 904, 910, 912, 914, 916, 918, and computer readable medium / memory 1006). The bus 1024 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further.

[0123] The processing system 1014 may be coupled to the transceiver 1010. The transceiver 1010 is coupled to one or more antennas 1020. The transceiver 1010 provides a means for communicating with various other devices over a transmission medium. The transceiver 1010 receives signals from the one or more antennas 1020, extracts information from the received signals, and provides the extracted information to the processing system 1014 (specifically, the receiving component 904). In addition, the transceiver 1010 receives information from the processing system 1014 (specifically, the transmitting component 916) and generates signals to be applied to the one or more antennas 1020 based on the received information. The processing system 1014 includes a processor 1004 coupled to a computer-readable medium / memory 1006. The processor 1004 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory 1006. The software, when executed by the processor 1004, causes the processing system 1014 to perform the various functions described above for any particular device. The computer-readable medium / memory 1006 may also be used to store data manipulated by the processor 1004 when executing software. The processing system 1014 further includes at least one of components 904, 910, 912, 914, 916, 918. These components may be software components running in the processor 1004, software components resident / stored in the computer-readable medium / memory 1006, one or more hardware components coupled to the processor 1004, or some combination thereof. The processing system 1014 may be a component of the device 310 or the device 350 and may include the memory 376, 360 and / or at least one of the following: the TX processors 316, 368, the RX processors 370, 356, and the controller / processor 375, 359. Alternatively, the processing system 1014 may be the entire UE (e.g., see Figure 3 device 310 or 350).

[0124] In one configuration, the device 902 / 902' for wireless communication includes: a device for wirelessly requesting a service for maneuvering scheduling of a vehicle from the maneuvering coordinator through a direct communication link between the UE and the maneuvering coordinator; a device for wirelessly receiving maneuvering information from the maneuvering coordinator through the direct communication link; and a device for applying the maneuvering information. In another configuration, the device 902 / 902' for wireless communication includes: a device for receiving a configuration for a maneuvering scheduling mode from a network; and a device for identifying the maneuvering coordinator based on the configuration before requesting the service for maneuvering scheduling. In yet another configuration, the device 902 / 902' for wireless communication includes: a device for receiving a configuration for a maneuvering scheduling mode from a network; and a device for identifying the maneuvering coordinator based on the configuration before requesting the service for maneuvering scheduling. In yet another configuration, the device 902 / 902' for wireless communication includes: a device for identifying the maneuvering coordinator before requesting the service for maneuvering scheduling. For example, the maneuvering coordinator is identified based on preconfigured location information about the maneuvering coordinator and the current location of the UE. In yet another configuration, the apparatus 902 / 902' for wireless communication includes means for receiving an announce message from the steering coordinator; and means for identifying the steering coordinator based on the announce message before requesting the service for steering scheduling.

[0125] In an additional configuration, the device 902 / 902' for wireless communication includes: a device for performing a security check to verify that the manipulation coordinator is authorized to schedule the manipulation before requesting the service for manipulation scheduling. In another configuration, the device 902 / 902' for wireless communication includes: a device for wirelessly sending at least one of the expected path of the UE, the mechanical capabilities of the UE, or the speed of the UE to the manipulation coordinator via the direct communication link. In another configuration, the device 902 / 902' for wireless communication includes: a device for wirelessly sending link information to the manipulation coordinator via the direct communication link to establish a unicast link, and the manipulation information is received from the manipulation coordinator via the unicast link. In another configuration, the device 902 / 902' for wireless communication includes: a device for receiving an identifier of the UE in a message from the manipulation coordinator before receiving the manipulation information, and a device for receiving a transmission profile in the message from the manipulation coordinator. For example, the manipulation information is received from the manipulation coordinator via broadcast, multicast, or groupcast using the identifier of the UE and based on the transmission profile.

[0126] The aforementioned means may be one or more of the aforementioned components of the device 902 and / or the processing system 1014 of the device 902' configured to perform the functions recited by the aforementioned means. As previously described, the processing system 1014 may include the TX processors 316, 368, the RX processors 370, 356, and the controllers / processors 375, 359. Thus, in one configuration, the aforementioned means may be the TX processors 316, 368, the RX processors 370, 356, and the controllers / processors 375, 359 configured to perform the functions recited by the aforementioned means.

[0127] Fig.11A and 11B 1100 is a flowchart of a wireless communication method. The method may be performed by a steering coordinator (e.g., 107, 507, 604, 704, 950, device 1202 / 1202'; processing system 1314, which may include a memory and may be the entire steering coordinator or a component of the steering coordinator), which transmits and receives data from a UE (e.g., UE 104, 402, 404, 502, 504, 606, 608, 610, 706, 708, 710, 1250, 1260; or device 310, 350). The steering coordinator may include a roadside unit (RSU). The steering coordinator may include a scheduling function at a location different from the RSU. The steering coordinator may include a scheduling function that implements user input (e.g., manual input). Alternatively, the steering coordinator may include a mobile terminal. For example, referring to Figure 5 and 6 , the UE may include a V2X-capable UE 606 (e.g., UE 502 or a device associated with vehicle 1) or a V2X-capable UE 608 (e.g., UE 504 or a device associated with vehicle 2), and the maneuvering coordinator may include an RSU 507 / 604. Dashed lines are used to illustrate optional aspects. The method allows the RSU to coordinate maneuvers for V2X-capable vehicles adjacent to the RSU.

[0128] At 1102, the steering coordinator may transmit an announcement message (e.g., announcing the presence and / or capabilities of the steering coordinator). For example, 1102 may be transmitted from Fig.12 The RSU may be executed by the transmission component 1210 of the embodiment. The announcement message may be transmitted before receiving the request for the service for maneuver scheduling. The announcement message may include an indication of the maneuver scheduling capability. The announcement message may include security information indicating that the maneuver coordinator is authorized to schedule maneuvers. For example, the RSU may optionally send a message such as Figure 6 The announcement may also include a reference to the transmission 614 of the V2X-capable UE to announce its presence and / or ability to perform scheduling of vehicle maneuvers. Figure 5The discovery-based configuration described in the various aspects. For example, Figure 6 As illustrated in , an RSU 604 may announce or broadcast a transmission or beacon to monitor for V2X-capable UEs 606 or UEs 608 within range of the RSU. When the UEs 606, 608 receive the transmission, they may be made aware of the RSU and / or its steering scheduling capabilities.

[0129] In addition, in one aspect, when the UE passes Figure 6 When the configuration 612 and / or transmission 614 of the steering coordinator become aware of the RSU, they can confirm the presence of the RSU and perform a security check before requesting scheduling services from the RSU. This security check ensures that the RSU is authorized to perform the steering operation scheduling. Therefore, at 1102, the beacon transmission from the steering coordinator may include a signature or other field (e.g., a specific provider service identifier (PSID) or an intelligent transportation system application identifier (ITS-AID)) identifying the certificate associated with the scheduling operation application, which the UE can use to confirm the presence and scheduling capabilities of the steering coordinator.

[0130] At 1104, the maneuvering coordinator receives a request for a service for maneuvering scheduling of a vehicle from at least one UE. For example, 1104 may be received from Fig.12 , is executed by the receiving component 1204. The request can be wirelessly received via a direct communication link between each UE of at least one UE and the maneuvering coordinator (e.g., based on V2X communication). The vehicle(s) may include any of autonomous, semi-autonomous, or manually driven vehicles. The UE(s) may request from the maneuvering coordinator a service for maneuvering scheduling for at least one of crossing an intersection, entering a road, leaving a road, or parking. In one aspect, the maneuvering coordinator may receive a request from the UE via unicast signaling via a PC5 interface, which includes information about the expected path or operation of the UE, and a unicast link between the UE and the RSU is established. For example, referring to Figure 5 UE 502 and / or UE 504 may utilize the unicast link established by each device to utilize information about the intended path or operation of the device (e.g., vehicle 1 intends to go straight, vehicle 2 intends to turn left, etc.) to request service from RSU 507 through the PC5 interface.

[0131] At 1106, the maneuvering coordinator may wirelessly receive one or more of the expected path, mechanical capability, or speed from each UE requesting the service for maneuvering scheduling via the direct communication link. For example, 1106 may be received from Fig.12 For example, Figure 6The maneuver coordinator is illustrated as receiving request 616. This message may request service from the maneuver coordinator and may include the mechanical capabilities of the UE (vehicle type, braking distance), the planned path of the UE (e.g., based on a map provided by the maneuver coordinator or navigation information of the UE), and the location and / or speed of the UE.

[0132] At 1108, the manipulation coordinator may wirelessly receive link information from each of the at least one UE via the direct communication link. For example, 1108 may be received from Fig.12 The link information may include at least one of a layer 2 identifier (L2 ID), a transmission profile, a radio access technology (RAT) capability, and / or a quality of service profile. For example, referring to Figure 6 , when UE 606 (vehicle 1) approaches the intersection where RSU 604 is located, the maneuver coordinator (e.g., RSU 604) may receive a request for a scheduled maneuver requesting service from the UE. This scheduling request message may include necessary access stratum (AS) layer information to establish a unicast V2X link between the RSU and the UE, including, for example, the UE's layer 2 identifier (L2ID), transmission (Tx) profile, and quality of service (QoS) level.

[0133] In one aspect, each request from a UE may inform the RSU of the UE's V2X transmission and reception capabilities via the UE's transmission (Tx) profile. The Tx profile indicates how the UE may receive the RSU's steering commands and may be different for different UEs. For example, the transmission profile may include information such as, but not limited to, the UE's supported modulation schemes (e.g., 16QAM or 64QAM), supported radio access technologies (RATs) (e.g., LTE or 5G), supported communication interfaces (e.g., PC5), and supported multiple-input multiple-output (MIMO) operation modes (e.g., transmit diversity). Thus, in Figure 7 In example 700 of , the request of UE-1 may include a Tx profile indicating that UE 706 is capable of receiving 64QAM modulated data over the PC5 interface in New Radio (NR) / 5G RAT, while the request of UE-2 may include a Tx profile indicating that UE 708 is capable of receiving only 16QAM modulated data over the PC5 interface in LTE / 4G RAT. The request for scheduled manipulation may also include a reference to Figure 6 Other information described in request 616.

[0134] At 1110, the steering coordinator may establish a unicast link with each of the requesting UEs. For example, 1110 may be initiated by a Fig.12The establishment component 1206 is executed. The corresponding unicast link can be used to transmit the manipulation information to the UE. For example, refer to Figure 6 , when UE 606 (vehicle 1) approaches the intersection where RSU 604 is located and sends a request for a scheduled maneuver to the RSU to request service from the RSU, the request may include AS layer information of the UE for forming a unicast link with the RSU so that the RSU can use the established unicast link to send the maneuver command of the RSU.

[0135] At 1112, the manipulation coordinator may receive information from at least one sensor. For example, 1112 may be received from Fig.12 The control unit 1204 may be executed by the receiving component 1204 of the control unit. The control unit 1204 may then determine the control information based at least in part on the information received from the at least one sensor. In one aspect, the at least one sensor may include one or more of a camera, a radar, a road sensor, or a traffic light. For example, referring to Figure 6 At 620, the maneuvering coordinator may also optionally use sensors to detect maneuvers of UEs that do not have V2X capabilities. For example, Figure 5 As illustrated, the vehicle may not be V2X capable and therefore may not send a request for a scheduled maneuver or declare an intent to maneuver to the maneuver coordinator. Figure 6 As shown, the maneuvering coordinator can use sensors at and / or coupled to the maneuvering coordinator to detect the maneuvers (e.g., speed and path) of the vehicle 610 that does not have V2X capabilities. Such sensors can include, for example, cameras, radars, road sensors, and / or traffic lights. The maneuvering coordinator can also use these sensors to collect information about the surrounding environment.

[0136] At 1114, the steering coordinator determines steering information for the UE based on the request. For example, 1114 may be provided by a Fig.12 The determination component 1208 is executed. For example, Figure 6 At 622, the maneuver coordinator determines and schedules maneuvers for all known requesting vehicles accordingly. Figure 6 , RSU 604 may determine a maneuver for UE 606 based on information collected from UE 606, 608 and vehicle 610, for example, a timing at which UE 606 may go straight through an intersection after UE 608 turns left and before vehicle 610 turns right. The information collected by the RSU for scheduling maneuvers may be based on data received from the UE in V2X communications and local sensor readings. This information may also be based on remote traffic monitoring and control center commands.

[0137] In one aspect, the manipulation information may be based on information received from multiple UEs. For example, Figure 6 and Figure 7 An example is illustrated in which multiple V2X-capable UEs announce their intent to maneuver and / or request a scheduled maneuver to a maneuver coordinator. Figure 5 As illustrated in , UE 504 approaches an intersection where RSU 507 is located at approximately the same time as UE 502. However, UE 504 may not send a request for a scheduled maneuver to the RSU, but may instead announce its intent to maneuver. Figure 6 As illustrated, around the time when UE-1 606 sends a request for a scheduled maneuver to the RSU 604, UE-2 608 announces its intention for the maneuver, including its mechanical capabilities and planned path (e.g., UE 608 is traveling at a certain speed and intends to turn left), and the RSU 604 may monitor and receive the announcement information from UE 608. Alternatively, UE 608 may also request RSU scheduling by sending a request for a scheduled maneuver to the RSU according to request 616.

[0138] At 1116, the steering coordinator may transmit the identifier of the UE in the message before transmitting the steering information at 1120. For example, 1116 may be transmitted from Fig.12 In one aspect, at 1120, the steering information for the UE may be transmitted from the steering coordinator via broadcast, multicast, or groupcast using the UE's identifier. For example, referring to Figure 7 In response 724, after the steering coordinator determines the scheduled steering, the steering coordinator may transmit a scheduled steering response to one or more requesting UEs. In one aspect, the steering coordinator may balance the transmission / reception capabilities of all UEs requesting scheduling, and may send a response to notify each UE of the Tx profile and steering identifier so that the UE receives a separate steering command. The steering identifier allows the UE to receive its steering command from the transmission.

[0139] For example, Figure 7 As illustrated, RSU 704 may send a scheduled steering response to UE 706, notifying the UE of a unique steering identifier for receiving the UE's steering commands in transmission. Similarly, RSU 704 may send a scheduled steering response to UE 708, notifying the UE of a unique steering identifier for receiving the UE's steering commands in transmission.

[0140] At 1118, the manipulation coordinator may transmit the transmission profile in the message from the manipulation coordinator. For example, 1118 may be transmitted from Fig.12 In one aspect, the manipulation information may be transmitted from the manipulation coordinator via broadcast, multicast, or groupcast based on the transmission profile. For example, referring to Figure 7In response 724, after the steering coordinator determines the scheduled steering, the steering coordinator transmits a scheduled steering response to one or more requesting UEs. In one aspect, the steering coordinator can balance the transmission / reception capabilities of multiple UEs requesting scheduling, and can send a response to inform each UE of the Tx profile and steering identifier for the UE to receive a separate steering command. The Tx profile can indicate to the UE the format that the RSU will use for steering command transmission.

[0141] For example, Figure 7 As illustrated, the RSU 704 may send a scheduled steering response to the UE 706 based on the transmission / reception capabilities of the UE received in the request 616, thereby informing the UE of the Tx profile for the steering command transmission. Similarly, the RSU 704 may send a scheduled steering response to the UE 708 based on the transmission / reception capabilities of the UE received in the request 718, thereby informing the UE of the Tx profile for the steering command transmission.

[0142] Finally, at 1120, the steering coordinator may wirelessly transmit the steering information, such as that determined at 1114, to at least one UE via a direct communication link. For example, 1120 may be transmitted by a controller from Fig.12 For example, referring to the transmission component 1210 Figure 6 At 624, after the RSU determines the scheduled manipulation, the RSU transmits a scheduled manipulation response to one or more requesting UEs. Figure 6 As illustrated, the maneuver coordinator may send a scheduled maneuver response to the UE 606, which includes a maneuver command notifying the UE of its scheduled maneuver (e.g., vehicle 1 may go straight through the intersection after vehicle 2 turns left and before vehicle 3 turns right). The maneuver command may list all necessary operations that the UE will need to perform for the maneuver, such as the duration of the determined UE speed and the time and / or location at which the UE may turn or change lanes. For example, the scheduled maneuver response transmitted to the UE 606 may command the UE to slow down and / or stop before continuing through the intersection until vehicle 2 completes the left turn.

[0143] As another example, refer to Figure 7 The steering coordinator may announce the aggregate steering command to all UEs requesting scheduling. Figure 7As illustrated, a maneuver coordinator, such as RSU 704, may broadcast a maneuver command to UE 706 and UE 708, the maneuver command including Rx ID1, Command 1, Rx ID2, and Command 2. Rx ID1 and Rx ID2 correspond to respective maneuver identifiers transmitted to UE 706 and UE 708 in responses 724, 725. Command 1 and Command 2 correspond to respective maneuver commands that inform UE 706 and UE 708 of their scheduled maneuvers determined at 622. For example, Command 1 may indicate that vehicle 1 should go straight through an intersection, while Command 2 may indicate that vehicle 2 should turn left at an intersection.

[0144] In one aspect, the first manipulation information may be transmitted to the first UE using a first radio access technology (RAT), and the second manipulation information may be transmitted to the second UE using a second RAT. Figure 7 As described, the Tx profile for UE 706 may indicate that UE 706 is capable of receiving 64QAM modulated data through the PC5 interface in New Radio (NR) / 5G RAT, while the Tx profile for UE 708 may indicate that UE 708 is capable of receiving only 16QAM modulated data through the PC5 interface in LTE / 4G RAT. Therefore, the steering coordinator may divide its steering command message and transmit it to each UE in different channels (e.g., LTE and NR) on the PC5 interface using different modulation schemes. In addition, even if each UE can receive the steering command message on the same channel, the RSU may still transmit on different channels to increase data reliability.

[0145] Fig.12 is a conceptual data flow diagram 1200 illustrating the data flow between different devices / components in an example apparatus 1202. The apparatus may be a maneuvering coordinator or a component of a maneuvering coordinator (e.g., a roadside unit (RSU) or a mobile terminal) (e.g., 107, 310, 350, 507, 604, 704). For example, referring to Figure 5 and 6 , the steering coordinator may include the RSU 507 / 604. The steering coordinator may include a scheduling function at a location different from the RSU. The steering coordinator may include a scheduling function that implements user input (e.g., manual input).

[0146] The device 1202 includes a receiving component 1204 that receives communications from at least one UE, for example, based on V2X, V2V, and / or other D2D communications. The receiving component may be configured to wirelessly receive a request for a service for maneuvering scheduling of a vehicle (e.g., a request for a scheduled maneuver) from UE 1250, 1260 via a direct communication link between each of at least one UE 1250, 1260 and a maneuvering coordinator. The receiving component 1204 may wirelessly receive one or more of an expected path, mechanical capability, or speed from each UE requesting the service for maneuvering scheduling via the direct communication link. The receiving component 1204 further wirelessly receives link information (e.g., AS layer information including a Tx profile) from each of the at least one UE via the direct communication link. The receiving component 1204 additionally receives information from at least one sensor 1240, and the maneuvering information is based at least in part on the information received from the at least one sensor.

[0147] The device 1202 also includes an establishment component 1206 for establishing a unicast link with each of the at least one UE. The unicast link is used to transmit the manipulation information. The device 1202 also includes a determination component 1208 for determining the manipulation information (e.g., a manipulation command) for at least one UE 1250, 1260 based on the received request and sensor information. In addition, the device 1202 includes a transmission component 1210 that transmits a declaration message (e.g., a beacon) to the UE 1250, 1260 before receiving a request for a service for manipulation scheduling from the UE. The transmission component 1210 also transmits the identifier and transmission profile of the UE in the message before transmitting the manipulation information. The manipulation information for the UE is transmitted from the manipulation coordinator via broadcast, multicast, or groupcast using the identifier of the UE and based on the transmission profile. The transmission component 1210 wirelessly sends the manipulation information to at least one UE 1250, 1260 via the direct communication link.

[0148] The device 1202 further includes an announcement component 1212 configured to transmit an announcement message of the coordinator's presence / capabilities. The device 1202 also includes a security component 1214 that includes security information (e.g., certificates) in the announcement message. In addition, the device 1202 includes a command component 1216 that sends the manipulation information determined by the determination component 1208. In addition, the device 1202 includes sending Figure 7 A response component 1218 is involved in manipulating IDs and / or transmission profiles.

[0149] The apparatus may include executing Fig.11A and 11B The additional components of each box of the algorithm in the preceding flowchart. Thus, Fig.11A and 11BEach block in the aforementioned flow chart may be performed by a component and the device may include one or more of those components. These components may be one or more hardware components specifically configured to perform the process / algorithm, implemented by a processor configured to perform the process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.

[0150] Fig.13 1300 is a diagram illustrating an example of a hardware implementation of a device 1202' employing a processing system 1314. The processing system 1314 may be implemented with a bus architecture generally represented by a bus 1324. Depending on the specific application of the processing system 1314 and the overall design constraints, the bus 1324 may include any number of interconnecting buses and bridges. The bus 1324 links various circuits together, including one or more processors and / or hardware components (represented by the processor 1304, components 1204, 1206, 1208, 1210, 1212, 1214, 1216, 1218, and computer readable medium / memory 1306). The bus 1324 may also link various other circuits, such as timing sources, peripherals, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further.

[0151] The processing system 1314 may be coupled to the transceiver 1310. The transceiver 1310 is coupled to one or more antennas 1320. The transceiver 1310 provides a means for communicating with various other devices over a transmission medium. The transceiver 1310 receives signals from the one or more antennas 1320, extracts information from the received signals, and provides the extracted information to the processing system 1314 (specifically, the receiving component 1204). In addition, the transceiver 1310 receives information from the processing system 1314 (specifically, the transmitting component 1210) and generates signals to be applied to the one or more antennas 1320 based on the received information. The processing system 1314 includes a processor 1304 coupled to a computer-readable medium / memory 1306. The processor 1304 is responsible for general processing, including the execution of software stored on the computer-readable medium / memory 1306. The software, when executed by the processor 1304, causes the processing system 1314 to perform the various functions described above for any particular device. The computer-readable medium / memory 1306 may also be used to store data manipulated by the processor 1304 when executing software. The processing system 1314 further includes at least one of the components 1204, 1206, 1208, 1210, 1212, 1214, 1216, 1218. These components may be software components running in the processor 1304, software components resident / stored in the computer-readable medium / memory 1306, one or more hardware components coupled to the processor 1304, or some combination thereof. The processing system 1314 may be a component of the device 310 or the device 350 and may include the memory 376, 360 and / or at least one of the following: the TX processors 316, 368, the RX processors 370, 356, and the controller / processor 375, 359. Alternatively, the processing system 1314 may be the entire manipulation coordinator (e.g., see Figure 3 device 310 or 350).

[0152] In one configuration, the device 1202 / 1202' for wireless communication includes: a device for wirelessly receiving a request for a service for maneuvering scheduling of a vehicle from at least one UE via a direct communication link between each of the at least one UE and the maneuvering coordinator; a device for determining maneuvering information for the at least one UE based on the request; and a device for wirelessly transmitting the maneuvering information to the at least one UE via the direct communication link. In another configuration, the device 1202 / 1202' for wireless communication includes: a device for transmitting a declaration message before receiving the request for the service for maneuvering scheduling. In yet another configuration, the device 1202 / 1202' for wireless communication includes: a device for wirelessly receiving one or more of an expected path, mechanical capacity, or speed from each UE requesting the service for maneuvering scheduling via the direct communication link. In yet another configuration, the device 1202 / 1202' for wireless communication includes: a device for wirelessly receiving link information from each of the at least one UE via the direct communication link; and a device for establishing a unicast link with each of the at least one UE. In one aspect, the steering information is transmitted using a unicast link.

[0153] In an additional configuration, the device 1202 / 1202' for wireless communication includes: a device for receiving information from at least one sensor, wherein the manipulation information is at least partially based on the information received from the at least one sensor. In another configuration, the device 1202 / 1202' for wireless communication includes: a device for transmitting an identifier of the UE in a message before transmitting the manipulation information. In one aspect, the manipulation information for the UE is transmitted from the manipulation coordinator via broadcast, multicast, or groupcast using the identifier of the UE. In yet another configuration, the device 1202 / 1202' for wireless communication includes: a device for transmitting a transmission profile from the manipulation coordinator in the message. In one aspect, the manipulation information is received from the manipulation coordinator via broadcast, multicast, or groupcast based on the transmission profile.

[0154] The aforementioned means may be one or more of the aforementioned components of the device 1202 and / or the processing system 1314 of the device 1202' configured to perform the functions recited by the aforementioned means. As previously described, the processing system 1314 may include the TX processors 316, 368, the RX processors 370, 356, and the controllers / processors 375, 359. Thus, in one configuration, the aforementioned means may be the TX processors 316, 368, the RX processors 370, 356, and the controllers / processors 375, 359 configured to perform the functions recited by the aforementioned means.

[0155] Determining the maneuver of a vehicle is challenging for autonomous vehicles, especially at intersections. Not all traffic information can be detected by local sensors at the vehicle. Considering the presence of mixed vehicles with different communication capabilities, not all vehicles may be equipped with the sensors and communication components required to achieve coordinated maneuvering operations. Even if V2X-based sensors are shared between V2X-capable vehicles, it may be difficult to ensure safe driving operations. For example, even with multiple vehicles, there is no guarantee that sensor information is complete. Distributed autonomous driving logic may cause unstable maneuvering states at certain vehicles. Likewise, powerful hardware may be required at each vehicle to support the handling of such shared sensor information.

[0156] The present invention solves these challenges by providing centralized, scheduler-based steering coordination for UEs. The UE can transmit data to and receive data from a steering coordinator (e.g., a roadside unit) based on V2X communication. The UE may first identify the steering coordinator using a location-based configuration, a discovery-based configuration, or the like. Once the UE knows the steering coordinator, the UE sends a request for steering operation scheduling to the steering coordinator. The steering coordinator then schedules and coordinates the operations of the UE. The steering coordinator may also use its sensors and reports transmitted from the UE to determine the scheduling.

[0157] Therefore, the RSU-based scheduling mechanism described above provides coordinated maneuvering operations for all V2X-capable vehicles adjacent to the RSU, thereby providing several advantages. For example, autonomous vehicles require simpler operating logic, which only needs to follow the instructions transmitted by the RSU. In one aspect, the UE wirelessly requests the maneuvering coordinator for a service for maneuvering scheduling of vehicles through a direct communication link between the UE and the maneuvering coordinator; wirelessly receives maneuvering information from the maneuvering coordinator through the direct communication link; and applies the maneuvering information. On the other hand, the maneuvering coordinator wirelessly receives a request for a service for maneuvering scheduling of vehicles from at least one user equipment (UE) through a direct communication link between each UE in the maneuvering coordinator and the at least one UE; determines the maneuvering information for the at least one UE based on the request; and wirelessly transmits the maneuvering information to the at least one UE through the direct communication link. Therefore, potential autonomous logic conflicts from different vehicle original equipment manufacturers (OEMs) are avoided. In addition, since only the RSU needs to be equipped with sensors for coordinating intersection handling, each vehicle does not require advanced sensors for maneuvering operations. Each vehicle does not require expensive and complex hardware, but only requires V2X assisted driving, and can therefore achieve autonomous driving at a lower cost.

[0158] The following examples are merely illustrative and may be combined with aspects of other embodiments or teachings described herein without limitation.

[0159] Example 1 is a method for wireless communication at a user equipment (UE), comprising: wirelessly requesting a service for maneuvering scheduling of a vehicle from a maneuvering coordinator via a direct communication link between the UE and the maneuvering coordinator; wirelessly receiving maneuvering information from the maneuvering coordinator via the direct communication link; and applying the maneuvering information.

[0160] In Example 2, the method of Example 1 further includes: receiving a configuration for steering scheduling mode from a network; and identifying the steering coordinator based on the configuration before requesting the service for steering scheduling.

[0161] In Example 3, the method of Example 1 or 2 further includes: the configuration configuring the UE to use the steering scheduling mode based on the location of the UE.

[0162] In Example 4, the method of any one of Examples 1-3 further includes: identifying the steering coordinator before requesting the service for steering scheduling, wherein the steering coordinator is identified based on preconfigured location information about the steering coordinator and a current location of the UE.

[0163] In Example 5, the method of any one of Examples 1-4 further includes: receiving an announce message from the steering coordinator; and identifying the steering coordinator based on the announce message before requesting the service for steering scheduling.

[0164] In Example 6, the method of any one of Examples 1-5 further comprises: performing a security check to verify that the maneuver coordinator is authorized to schedule the maneuver before requesting the service for maneuver scheduling.

[0165] In Example 7, the method of any one of Examples 1-6 further includes wirelessly sending at least one of the expected path of the UE, the mechanical capabilities of the UE, or the speed of the UE to the maneuvering coordinator through the direct communication link.

[0166] In Example 8, the method of any one of Examples 1-7 further includes: wirelessly sending link information to the steering coordinator through the direct communication link to establish a unicast link, wherein the steering information is received from the steering coordinator via the unicast link.

[0167] In Example 9, the method of any one of Examples 1-8 further includes: the link information includes at least one of a layer 2 identifier (L2ID), a transmission profile, a radio access technology (RAT) capability, or a quality of service profile.

[0168] In Example 10, the method of any one of Examples 1-9 further includes: receiving an identifier of the UE in a message from the manipulation coordinator before receiving the manipulation information, wherein the manipulation information is received from the manipulation coordinator via broadcast, multicast, or groupcast using the identifier of the UE.

[0169] In Example 11, the method of any one of Examples 1-10 further includes: receiving a transmission profile in the message from the steering coordinator, wherein the steering information is received from the steering coordinator via the broadcast, the multicast, or the groupcast based on the transmission profile.

[0170] In Example 12, the method of any one of Examples 1-11 further includes: the UE requests, from the maneuver coordinator, a service for maneuver scheduling for at least one of crossing an intersection, entering a road, exiting a road, or parking.

[0171] Example 13 is a device comprising one or more processors and one or more memories in electronic communication with the one or more processors, the one or more memories storing instructions executable by the one or more processors to cause a system or device to implement a method as in any of Examples 1-12.

[0172] Example 14 is a system or apparatus comprising means for implementing a method as in any one of Examples 1-12 or implementing an apparatus as in any one of Examples 1-12.

[0173] Example 15 is a non-transitory computer-readable medium storing instructions executable by one or more processors, the instructions causing the one or more processors to implement the method as in any of Examples 1-12.

[0174] Example 16 is a method for wireless communication at a maneuvering coordinator, the method comprising: wirelessly receiving a request for a service for maneuvering scheduling of a vehicle from at least one user equipment (UE) via a direct communication link between each UE in the at least one UE and the maneuvering coordinator; determining maneuvering information for the at least one UE based on the request; and wirelessly transmitting the maneuvering information to the at least one UE via the direct communication link.

[0175] In Example 17, the method of Example 16 further comprises: transmitting an announce message before receiving the request for the service for manipulating scheduling.

[0176] In Example 18, the method of Example 16 or Example 17 further includes: the announcement message includes an indication of the manipulation scheduling capability.

[0177] In Example 19, the method of any one of Examples 16-18 further comprises: the announce message comprises security information indicating that the maneuver coordinator is authorized to schedule the maneuver.

[0178] In Example 20, the method of any one of Examples 16-19 further includes: wirelessly receiving, through the direct communication link, one or more of the expected path, mechanical capability, or speed from each UE requesting the service for steering scheduling.

[0179] In Example 21, the method of any one of Examples 16-20 further includes: wirelessly receiving link information from each of the at least one UE via the direct communication link; and establishing a unicast link with each of the at least one UE, wherein the manipulation information is transmitted using the unicast link.

[0180] In Example 22, the method of any one of Examples 16-21 further includes: the link information includes at least one of a layer 2 identifier (L2 ID), a transmission profile, a radio access technology (RAT) capability, or a quality of service profile.

[0181] In Example 23, the method of any one of Examples 16-22 further includes: the manipulation information is based on information received from multiple UEs.

[0182] In Example 24, the method of any one of Examples 16-23 further includes: receiving information from at least one sensor, wherein the manipulation information is based at least in part on the information received from the at least one sensor.

[0183] In Example 25, the method of any one of Examples 16-24 further includes: the at least one sensor includes one or more of a camera, a radar, a road sensor, or a traffic light.

[0184] In Example 26, the method of any one of Examples 16-25 further includes: transmitting an identifier of the UE in a message before transmitting the manipulation information, wherein the manipulation information for the UE is transmitted from the manipulation coordinator via broadcast, multicast, or groupcast using the identifier of the UE.

[0185] In Example 27, the method of any one of Examples 16-26 further includes transmitting a transmission profile in the message from the steering coordinator, wherein the steering information is received from the steering coordinator via the broadcast, the multicast, or the groupcast based on the transmission profile.

[0186] In Example 28, the method of any one of Examples 16-27 further includes: the first manipulation information is transmitted to the first UE using a first radio access technology (RAT), and the second manipulation information is transmitted to the second UE using a second RAT.

[0187] In Example 29, the method of any one of Examples 16-28 further includes requesting the service for maneuvering the maneuver includes a request for at least one of crossing an intersection, entering a road, exiting a road, or stopping.

[0188] Example 30 is a device comprising one or more processors and one or more memories in electronic communication with the one or more processors, the one or more memories storing instructions executable by the one or more processors to cause the system or device to implement a method as in any of Examples 16-29.

[0189] Example 31 is a system or apparatus comprising means for implementing a method as in any of Examples 16-29 or implementing an apparatus as in any of Examples 16-29.

[0190] Example 32 is a non-transitory computer-readable medium storing instructions executable by one or more processors, the instructions causing the one or more processors to implement a method as in any of Examples 16-29.

[0191] In Example 33, for all of Examples 1-32, the maneuvering coordinator includes a roadside unit (RSU) or a mobile terminal.

[0192] In Example 34, for all of Examples 1-33, the vehicle includes one of an autonomous, semi-autonomous, or manually driven vehicle.

[0193] In Example 35, for all of Examples 1-34, the direct communication link is based on vehicle-to-everything (V2X) communications.

[0194] It should be understood that the specific order or hierarchy of each box in the disclosed process / flowchart is an illustration of an exemplary approach. It should be understood that the specific order or hierarchy of each box in these process / flowcharts can be rearranged based on design preferences. In addition, some boxes can be combined or omitted. The attached method claims present the elements of various boxes in an exemplary order and are not meant to be limited to the specific order or hierarchy presented.

[0195] The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be easily understood by those skilled in the art, and the universal principles defined in this article can be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown in this article, but should be granted the full scope consistent with the claims in language, wherein the singular reference of the elements is not intended to represent "there is and only one", but "one or more", unless otherwise stated. The wording "exemplary" is used in this article to mean "used as an example, instance, or explanation". Any aspect described as "exemplary" herein does not have to be interpreted as being superior to or superior to other aspects. Unless otherwise stated, the term "some / certain" refers to one or more. Combinations such as "at least one of A, B or C", "one or more of A, B or C", "at least one of A, B and C", "one or more of A, B and C" and "A, B, C or any combination thereof" include any combination of A, B and / or C, and may include multiple A, multiple B or multiple C. Specifically, combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members of A, B, or C. All structural and functional equivalents of the elements of the various aspects described throughout this disclosure that are currently or hereafter known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is expressly recorded in the claims. The terms "module," "mechanism," "element," "device," and the like may not be a substitute for the term "means." Thus, no claim element should be interpreted as a means-plus-function unless the element is explicitly stated using the phrase "means for..."

Claims

1. A method for wireless communication at a user equipment (UE), comprising: wirelessly requesting a service for maneuver scheduling of a vehicle from the maneuver coordinator via a direct communication link between the UE and the maneuver coordinator; receiving an identifier of the UE in a message from the steering coordinator; receiving a transmission profile in said message from said manipulation coordinator; wirelessly receiving steering information from the steering coordinator through the direct communication link, wherein the steering information is received from the steering coordinator via broadcast, multicast, or groupcast using the identifier of the UE, and wherein the steering information is received from the steering coordinator via the broadcast, the multicast, or the groupcast based on the transmission profile; as well as The manipulation information is applied.

2. The method of claim 1, further comprising: receiving a configuration for manipulating a scheduling mode from a network; The manipulation coordinator is identified based on the configuration before requesting the service for manipulation scheduling.

3. The method of claim 2, wherein the configuring configures the UE to use the steering scheduling mode based on a location of the UE.

4. The method of claim 1, further comprising: The steering coordinator is identified before requesting the service for steering scheduling, wherein the steering coordinator is identified based on preconfigured location information about the steering coordinator and a current location of the UE.

5. The method of claim 1, further comprising: receiving an announce message from the manipulation coordinator; as well as The steering coordinator is identified based on the announce message before requesting the service for steering scheduling.

6. The method of claim 1, further comprising: A security check is performed before requesting the service for maneuver scheduling to verify that the maneuver coordinator is authorized to schedule a maneuver.

7. The method of claim 1, further comprising: At least one of an expected path of the UE, a mechanical capability of the UE, or a speed of the UE is wirelessly transmitted to the maneuvering coordinator over the direct communication link.

8. The method of claim 1, further comprising: Link information is wirelessly transmitted to the steering coordinator through the direct communication link to establish a unicast link, wherein the steering information is received from the steering coordinator via the unicast link.

9. The method of claim 8, wherein the link information comprises at least one of a layer 2 identifier (L2 ID), a transmission profile, a radio access technology (RAT) capability, or a quality of service profile.

10. The method of claim 1, wherein the direct communication link is based on vehicle-to-everything (V2X) communication.

11. The method of claim 1, wherein the maneuver coordinator comprises a road side unit (RSU).

12. The method of claim 11, wherein the steering coordinator comprises a scheduling function at a location different from the RSU.

13. The method of claim 11, wherein the manipulation coordinator includes a scheduling function that allows user input.

14. The method of claim 1, wherein the manipulation coordinator comprises a mobile terminal.

15. An apparatus for wireless communication, comprising: Memory; as well as at least one processor coupled to the memory and configured to: wirelessly requesting services for a maneuver schedule for a vehicle from the maneuver coordinator via a direct communication link between the device and the maneuver coordinator; receiving an identifier of the UE in a message from the steering coordinator; receiving a transmission profile in said message from said manipulation coordinator; wirelessly receiving steering information from the steering coordinator through the direct communication link, wherein the steering information is received from the steering coordinator via broadcast, multicast, or groupcast using the identifier of the UE, and wherein the steering information is received from the steering coordinator via the broadcast, the multicast, or the groupcast based on the transmission profile; as well as The manipulation information is applied. 16 . The apparatus of claim 15 , wherein the at least one processor is further configured to receive a configuration for a steering scheduling mode from a network and to identify the steering coordinator based on the configuration before requesting the service for steering scheduling.

17. A method for wireless communication at a steering coordinator, comprising: wirelessly receiving a request for a service for maneuver scheduling of a vehicle from each of at least one user equipment (UE) via a direct communication link between the at least one UE and the maneuver coordinator; Transmitting the UE identifier in the message; transmitting a transmission profile from the manipulation coordinator in the message; determining, based on the request, manipulation information for the at least one UE; as well as wirelessly transmitting the manipulation information to the at least one UE via the direct communication link, Wherein the manipulation information for the UE is transmitted from the manipulation coordinator via broadcast, multicast or groupcast using the identifier of the UE, and wherein the manipulation information is transmitted from the manipulation coordinator via the broadcast, the multicast or the groupcast based on the transmission profile.

18. The method of claim 17, further comprising: An announce message is transmitted prior to receiving the request for the service for manipulating a schedule.

19. The method of claim 18, wherein the announce message includes at least one of an indication of maneuver scheduling capabilities or security information indicating that the maneuver coordinator is authorized to schedule a maneuver.

20. The method of claim 17, further comprising: One or more of an expected path, mechanical capability, or speed is wirelessly received over the direct communication link from each UE requesting the service for steering scheduling.

21. The method of claim 17, further comprising: wirelessly receiving link information from each of the at least one UE via the direct communication link; as well as A unicast link is established with each of the at least one UE, wherein the manipulation information is transmitted using the unicast link.

22. The method of claim 21, wherein the link information comprises at least one of a layer 2 identifier (L2 ID), a transmission profile, a radio access technology (RAT) capability, or a quality of service profile.

23. The method of claim 17, wherein the manipulation information is based on information received from a plurality of UEs.

24. The method of claim 17, further comprising: Information is received from at least one sensor, wherein the manipulation information is based at least in part on the information received from the at least one sensor.

25. The method of claim 24, wherein the at least one sensor comprises one or more of a camera, a radar, a road sensor, or a traffic light.

26. The method of claim 17, wherein the first manipulation information is transmitted to the first UE using a first radio access technology (RAT), and the second manipulation information is transmitted to the second UE using a second RAT.

27. An apparatus for wireless communication, comprising: Memory; as well as at least one processor coupled to the memory and configured to: wirelessly receiving a request for a service for maneuver scheduling of a vehicle from at least one user equipment (UE) via a direct communication link between each of the UEs and a maneuver coordinator; Transmitting the UE identifier in the message; transmitting a transmission profile from the manipulation coordinator in the message; determining, based on the request, manipulation information for the at least one UE; as well as wirelessly transmitting the manipulation information to the at least one UE via the direct communication link, Wherein the manipulation information for the UE is transmitted from the manipulation coordinator via broadcast, multicast or groupcast using the identifier of the UE, and wherein the manipulation information is transmitted from the manipulation coordinator via the broadcast, the multicast or the groupcast based on the transmission profile.

28. The apparatus of claim 27, wherein the at least one processor is further configured to wirelessly receive, over the direct communication link, one or more of an expected path, a mechanical capability, or a speed from each UE requesting the service for manipulating scheduling.