Context-specific alerts for user equipment

Abstract

Methods and apparatus for context-specific alerts for autonomous and non-autonomous vehicles. The apparatus obtains a capability indication of the UE indicating that the UE is paired with the vehicle. The apparatus generates a vehicle-specific signal based on the capability indication indicating that the UE is paired with the vehicle. The apparatus outputs the vehicle-specific signals to the UE. The vehicle includes an autonomous vehicle, wherein the capability indication further indicates that an autonomous mode of the autonomous vehicle is activated or deactivated. Data within the vehicle-specific signals is customized according to a pairing combination of the UE and the vehicle.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. patent application serial number 17 / 933,762, filed on September 20, 2022, entitled “CONTEXT SPECIFIC ALERTS FOR USER EQUIPMENTS,” which is expressly incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure relates generally to communication systems, and more particularly to configuration for context-specific alerts for user equipment (UE). Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of 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.

[0005] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. 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). Certain aspects of 5G NR may be based on 4G Long Term Evolution (LTE) standards. It is necessary to further improve 5G NR technology. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0006] A simplified summary of one or more aspects is presented below to provide a basic understanding of these aspects. This summary is not an extensive review of all contemplated aspects. This summary neither identifies the key or important elements of all aspects, nor describes 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 presented later.

[0007] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a device at a network node. The apparatus may be a processor and / or a modem at a network node or the network node itself. The apparatus obtains a capability indication of a user equipment (UE), the capability indication indicating that the UE is paired with a vehicle. The apparatus generates vehicle-specific signals based on the capability indication indicating that the UE is paired with the vehicle. The apparatus outputs the vehicle-specific signals to the UE.

[0008] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be a device at a UE. The apparatus may be a processor and / or a modem at the UE or the UE itself. The apparatus sends a capability indication of the UE to a network entity, the capability indication indicating that the UE is paired with a vehicle. The apparatus receives a vehicle-specific signal from the network entity based on the capability indication indicating that the UE is paired with the vehicle.

[0009] To achieve the aforementioned and related purposes, one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail some exemplary features of one or more aspects. However, these features indicate only some of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0011] Figure 2A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0012] Figure 2B is a diagram illustrating an example of DL channels within a subframe according to various aspects of the present disclosure.

[0013] Figure 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0014] Figure 2D is a diagram illustrating an example of UL channels within a subframe according to various aspects of the present disclosure.

[0015] Figure 3 is a diagram illustrating an example of a base station and a user equipment (UE) in an access network.

[0016] Figure 4 is a diagram illustrating an example of autonomous vehicles and non-autonomous vehicles accessing a network.

[0017] Figure 5is a diagram illustrating an example of autonomous vehicles and non-autonomous vehicles accessing a network.

[0018] Figure 6 It is a call flow diagram of the signaling between the UE and the base station.

[0019] Figure 7 is a flow chart of a wireless communication method.

[0020] Figure 8 is a diagram illustrating an example of a hardware implementation for an example network entity.

[0021] Fig. 9 is a flow chart of a wireless communication method.

[0022] Fig.10 is a flow chart of a wireless communication method.

[0023] Fig.11 are diagrams illustrating examples of hardware implementations for example apparatuses and / or network entities. DETAILED DESCRIPTION

[0024] The development of vehicle autonomous driving capabilities is an ongoing worldwide effort across industry and academia. Autonomous vehicles can be configured to enable operation with closer vehicle spacing and reduced reaction times. With advances in processing power, autonomous vehicles may be able to ingest and process large amounts of data to assess the environment and enable inter-vehicle maneuver coordination. The development of vehicle-based sensor sharing and cloud-based sensor sharing may allow detection and dissemination of other vehicles, vulnerable road users (e.g., pedestrians, cyclists), or road features.

[0025] Human drivers and autonomous vehicles may operate with different characteristics, including reaction time to detected vehicles, road users, or road conditions, and how close they may operate to other vehicles and road features. In a mixed environment of both autonomous and non-autonomous vehicles, the propagation of sensor sharing data and maneuver requests may be tailored to the capabilities of the receiving vehicle, whether that vehicle is an autonomous vehicle activating / deactivating autonomous mode or a non-autonomous vehicle.

[0026] Various aspects presented herein provide a configuration for context-specific alerts for autonomous vehicles and non-autonomous vehicles. For example, various aspects presented herein may identify a set of standard or over-the-air signaling for a network entity to provide vehicle-specific sensor shared data (e.g., vehicle road users, non-vehicle road users, or road conditions) to an autonomous vehicle that has autonomous functionality enabled, an autonomous vehicle that has autonomous functionality disabled, or a non-autonomous vehicle.

[0027] The specific embodiments described below in conjunction with the accompanying drawings are descriptions of various configurations and do not represent the only configurations in which the concepts described herein can be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, these concepts can be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0028] Several aspects of telecommunication systems are presented with reference to various apparatus and methods. These apparatus and methods are 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.

[0029] As an example, an element, or any part of an element, or any combination of elements can be implemented as a "processing system", which includes 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 the present disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, 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, or any combination thereof.

[0030] Thus, in one or more example aspects, specific implementations and / or use cases, the described functionality may be implemented in hardware, software, or any combination thereof. If implemented in software, the functionality may be stored or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. Storage media may be any available media that can be accessed by a computer. As an example, 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, combinations of these types of computer-readable media, 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.

[0031] Although various aspects, specific implementations and / or use cases are described in this application by the illustration of some examples, additional or different aspects, specific implementations and use cases may be generated in many different arrangements and scenarios. The various aspects, specific implementations and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, various aspects, specific implementations and / or use cases can be generated via integrated chip specific implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchase equipment, medical devices, devices that enable artificial intelligence (AI), etc.). Although some examples may or may not be specifically for use cases or applications, the described examples may have a wide range of applicability. Various aspects, specific implementations and / or use cases may be in the range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the range of aggregated, distributed or original equipment manufacturer (OEM) devices or systems in conjunction with one or more technologies herein. In some actual settings, the equipment combined with the various aspects and features described may also include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.) The techniques described herein can be practiced in a wide variety of devices of various sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc.

[0032] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or components in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or network equipment (such as a base station (BS)), or one or more units (or one or more components) performing base station functionality can be implemented in an aggregated or decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0033] A converged base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack that is physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of the CU, DU, and RU may be implemented as a virtual unit, for example, via a virtual central unit, a virtual distributed unit, a virtual radio unit, or some combination thereof.

[0034] Base station operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configuration such as that initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Various units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0035] Figure 1 1 is a diagram 100 illustrating an example of a wireless communication system and an access network. The illustrated wireless communication system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs 110 that may communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more disaggregated base station units, such as a near real-time (near RT) RAN intelligent controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a service management and orchestration (SMO) framework 105, or both. The CU 110 may communicate with one or more DUs 130 via corresponding midhaul links, such as an F1 interface. The DU 130 may communicate with one or more RUs 140 via corresponding fronthaul links. The RU 140 may communicate with corresponding UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

[0036] Each of the units (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO framework 105) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interfaces of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive signals or send signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive and / or send signals to one or more of the other units via a wireless transmission medium.

[0037] In some aspects, CU 110 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface that is configured to communicate signals with other control functions hosted by CU 110. CU 110 may be configured to handle user plane functionality (i.e., central unit-user plane (CU-UP)), control plane functionality (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 110 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 110 may be implemented to communicate with DU 130 for network control and signaling.

[0038] DU 130 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 140. In some aspects, DU 130 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least in part according to a functional split such as those defined by 3GPP. In some aspects, DU 130 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

[0039] The lower layer functionality may be implemented by one or more RUs 140. In some deployments, the RUs 140 controlled by the DUs 130 may correspond to logical nodes that host RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on functional splitting (such as lower layer functional splitting). In such an architecture, the RUs 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RUs 140 may be controlled by the corresponding DUs 130. In some scenarios, this configuration may enable the DUs 130 and CUs 110 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).

[0040] The SMO framework 105 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 105 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 105 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 190) to perform network element lifecycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 110, DU 130, RU 140, and near-RT RIC 125. In some specific implementations, the SMO framework 105 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 111) via the O1 interface. Additionally, in some specific implementations, the SMO framework 105 may communicate directly with one or more RUs 140 via the O1 interface. The SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of the SMO framework 105 .

[0041] The non-RT RIC 115 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence (AI) / machine learning (ML) (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 125. The non-RT RIC 115 may be coupled to or communicate with the near-RT RIC 125 (such as via an A1 interface). The near-RT RIC 125 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 110, one or more DUs 130, or both, and the O-eNB with the near-RT RIC 125.

[0042] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 125, the non-RT RIC 115 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 125 and may be received from a non-network data source or from a network function at the SMO framework 105 or the non-RT RIC 115. In some examples, the non-RT RIC 115 or the near-RT RIC 125 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 115 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 105 (such as via reconfiguration of O1) or via the creation of RAN management policies (such as A1 policies).

[0043] At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Therefore, the base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component is indicated by a dotted line to indicate that each component may be included in the base station 102 or may not be included in the base station). The base station 102 provides an access point to the core network 120 for the UE 104. 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). Small cells include femto cells, pico cells, and micro cells. 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 Node B (eNB) (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to RU 140 and / or downlink (DL) (also known as forward link) transmission from RU 140 to UE 104. The communication link may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The communication link may be through one or more carriers. For each carrier allocated in a carrier aggregation of up to Yx MHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 may use a spectrum of up to Y MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.) bandwidth. These 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 for DL ​​compared to UL). 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).

[0044] 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 wireless wide area network (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, Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

[0045] The wireless communication system may also include a Wi-Fi AP 150 that communicates with a UE 104 (also referred to as a Wi-Fi station (STA)) via a communication link 154, for example, in a 5 GHz unlicensed spectrum, etc. When communicating in an unlicensed spectrum, the UE 104 / AP 150 may perform a clear channel assessment (CCA) to determine whether a channel is available prior to communication.

[0046] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as the "sub-6 GHz" band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0047] Frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Recent 5G NR research has identified the operating bands for these mid-band frequencies as frequency range designation FR3 (7.125GHz-24.25GHz). The bands falling within FR3 can inherit FR1 characteristics and / or FR2 characteristics, so the features of FR1 and / or FR2 can be effectively extended to mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operations to more than 52.6GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6GHz-71GHz), FR4 (71GHz-114.25GHz) and FR5 (114.25GHz-300GHz). Each of these higher frequency bands falls within the EHF band.

[0048] In view of the above, unless otherwise specified, if the term "6 GHz or less" is used herein, it may broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specified, if the term "millimeter wave" is used herein, it may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and / or FR5, or may be within the EHF band.

[0049] The base station 102 and the UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. The base station 102 may send a beamformed signal 182 to the UE 104 in one or more transmit directions. The UE 104 may receive the beamformed signal from the base station 102 in one or more receive directions. The UE 104 may also send a beamformed signal 184 to the base station 102 in one or more transmit directions. The base station 102 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 102 / UE 104 may perform beam training to determine the best receive direction and transmit direction for each of the base station 102 / UE 104. The transmit direction and receive direction of the base station 102 may be the same or different. The transmit direction and receive direction of the UE 104 may be the same or different.

[0050] The base station 102 may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a transceiver base station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), a network node, a network entity, a network equipment, a road side unit (RSU), or some other suitable term. The RSU may include a fixed PC5 / side link node that has network connectivity and is configured to communicate wirelessly with a mobile PC5 / side link UE (e.g., a vehicle). The vehicle communication path to the network entity may be via a cellular (e.g., Uu), for example, via a gNB, or may be via a PC5 / side link, via an RSU. The base station 102 may be implemented as an integrated access and backhaul (IAB) node, a relay node, a side link node, an aggregated (monolithic) base station with a baseband unit (BBU) (including a CU and a DU) and a RU, or as a decomposed base station including one or more of a CU, a DU, and / or a RU. A set of base stations, which may include decomposed base stations and / or aggregated base stations, may be referred to as a Next Generation (NG) RAN (NG-RAN).

[0051] The core network 120 may include an access and mobility management function (AMF) 161, a session management function (SMF) 162, a user plane function (UPF) 163, a unified data management (UDM) 164, one or more location servers 168, and other functional entities. AMF 161 is a control node that handles signaling between UE 104 and core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identity handling, access authorization, and subscription management. One or more location servers 168 are illustrated as including a gateway mobile location center (GMLC) 165 and a location management function (LMF) 166. However, in general, the one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the GMLC 165, LMF 166, position determination entity (PDE), serving mobile location center (SMLC), mobile positioning center (MPC), etc. GMLC 165 and LMF 166 support UE location services. GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. LMF 166 receives measurement and assistance information from NG-RAN and UE 104 via AMF 161 to calculate the location of UE 104. NG-RAN may determine the location of UE 104 using one or more positioning methods. Positioning UE 104 may involve signal measurements, position estimation, and optional speed calculation based on these measurements. Signal measurements may be performed by UE 104 and / or serving base station 102. The measured signals may be based on a satellite positioning system (SPS) 170 (e.g., one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / positioning systems), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., an atmospheric pressure sensor, a motion sensor), an NR enhanced cell ID (NR E-CID) method, NR signals (e.g., multi-round trip time (multi-RTT), DL angle of departure (DL-AoD), DL time difference of arrival (DL-TDOA), UL time difference of arrival (UL-TDOA), and UL angle of arrival (UL-AoA) positioning), and / or one or more of other systems / signals / sensors.

[0052] Examples of UE 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet computers, smart devices, wearable devices, vehicles (e.g., UEs included in autonomous vehicles or non-autonomous vehicles), electric meters, gas pumps, large or small kitchen appliances, healthcare equipment, implants, sensors / actuators, displays, or any other similarly functional devices. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as stations, mobile stations, subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, mobile phones, user agents, mobile clients, clients, or some other suitable terminology. In some scenarios, the term UE may also be applied to one or more supporting devices, such as in a device cluster arrangement. One or more of these devices may access the network collectively and / or individually.

[0053] See again Figure 1 In certain aspects, the UE 104 may include a capability component 198 configured to send a capability indication of the UE to a network entity, the capability indication indicating that the UE is paired with a vehicle; and receive a vehicle-specific signal from the network entity based on the capability indication indicating that the UE is paired with the vehicle.

[0054] See again Figure 1 In certain aspects, the base station 102 may include a signal component 199 configured to obtain a capability indication of the UE, the capability indication indicating that the UE is paired with the vehicle; generate a vehicle-specific signal based on the capability indication indicating that the UE is paired with the vehicle; and output the vehicle-specific signal to the UE.

[0055] Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar areas such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0056] Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B FIG230 is a diagram illustrating an example of DL channels within a 5G NR subframe. Figure 2C FIG250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2DFIG280 is a diagram illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD) (wherein for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated to either DL or UL), or may be time division duplex (TDD) (wherein for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated to both DL and UL). Figure 2A , Figure 2C In the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are full DL and full UL, respectively. Other slot formats 2-61 include a mix of DL, UL and flexible symbols. The UE is configured with the slot format through the received slot format indicator (SFI) (dynamically configured through DL control information (DCI) or semi-statically / statically configured through radio resource control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0057] FIG. 2A to FIG. 2D The frame structure is illustrated, and various aspects of the present disclosure may be applicable to other wireless communication technologies that 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 microslot, which may include 7, 4, or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For a normal CP, each time slot may include 14 symbols, and for an extended CP, each time slot may include 12 symbols. The symbol on the DL may be a CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbol. The symbol on the UL may be a CP-OFDM symbol (for high throughput scenarios) or a discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbol (also known as a single carrier frequency division multiple access (SC-FDMA) symbol) (for power-limited scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and parameter set. The parameter set defines the subcarrier spacing (SCS) and effectively defines the symbol length / duration, which is equal to 1 / SCS.

[0058]

[0059] For normal CP (14 symbols / slot), different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, parameter set 2 allows 4 slots per subframe. Thus, for normal CP and parameter set μ, there are 14 symbols / slot and 2 μ timeslots / subframe. The subcarrier spacing can be equal to 2 μ *15kHz, where μ is parameter set 0 to 4. Therefore, the subcarrier spacing for parameter set μ=0 is 15kHz, and the subcarrier spacing for parameter set μ=4 is 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 2A to FIG. 2D An example of a parameter set μ=2 with a normal CP of 14 symbols per slot and 4 slots per subframe is provided. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is about 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency-division multiplexed (see Figure 2B ). Each BWP may have a specific parameter set and CP (normal or extended).

[0060] A resource grid may be used to represent the frame structure. Each slot includes a resource block (RB) (also referred to as 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.

[0061] like Figure 2A As illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) (indicated as R for one particular configuration, but other DM-RS configurations are possible) and a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0062] Figure 2BExamples of various DL channels within a subframe of a frame are illustrated. A physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within a BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during a PDCCH monitoring opportunity on a CORESET, wherein the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identification. A secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the system frame number (SFN) and the number of RBs in the system bandwidth. The physical downlink shared channel (PDSCH) carries user data, broadcast system information not sent over the PBCH (such as the system information block (SIB)), and paging messages.

[0063] like Figure 2C As illustrated, some of the REs carry DM-RS (indicated as R for a particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may send a DM-RS for a physical uplink control channel (PUCCH) and a DM-RS for a physical uplink shared channel (PUSCH). The PUSCH DM-RS may be sent in the first or first two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS may be sent in different configurations. The UE may send a sounding reference signal (SRS). The SRS may be sent in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the comb structures in the comb structure. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

[0064] Figure 2DExamples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicators (CQI), precoding matrix indicators (PMI), rank indicators (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACKs and / or negative ACKs (NACKs)). The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0065] Figure 3 375. The Controller / Processor 375 is a block diagram of a base station 310 in an access network communicating with a UE 350. In the DL, Internet Protocol (IP) packets may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with transfer of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation 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 transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0066] The transmit (TX) processor 316 and receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) coding / 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-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The coded and modulated symbols may then be separated 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 pre-coded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation schemes, as well as for spatial processing. Channel estimates may be derived from reference signals and / or channel condition feedback sent by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier for transmission using a corresponding spatial stream.

[0067] At the UE 350, each receiver 354Rx receives a signal through its corresponding 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 UE 350. If multiple spatial streams are destined for the UE 350, they can be combined into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then converts 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 and the reference signal are recovered and demodulated by determining the most likely signal constellation point sent by the base station 310. These soft decisions can be based on channel estimates calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by base station 310. The data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functionality.

[0068] 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. In the UL, the controller / processor 359 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 359 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0069] Similar to the functionality described in conjunction with DL transmissions performed by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, 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.

[0070] Channel estimates derived by the channel estimator 358 based on a reference signal or feedback sent by the base station 310 may be used by the 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.

[0071] UL transmissions are processed at the base station 310 in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318Rx receives a signal through its respective antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to the RX processor 370.

[0072] 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. In the UL, the controller / processor 375 provides demultiplexing between transport channels and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover IP packets. The controller / processor 375 is also responsible for error detection using ACK and / or NACK protocols to support HARQ operations.

[0073] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to combine Figure 1 The capability component 198 performs various aspects.

[0074] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to combine Figure 1 The signal component 199 performs various aspects.

[0075] The development of vehicle autonomous driving capabilities is an ongoing worldwide effort across industry and academia. Autonomous vehicles can be configured to enable operation with closer vehicle spacing and reduced reaction times. With advances in processing power, autonomous vehicles may be able to ingest and process large amounts of data to assess the environment and enable inter-vehicle maneuvering coordination. The development of vehicle-based sensor sharing and cloud-based sensor sharing may allow detection and dissemination of other vehicles, vulnerable road users (VRUs) (e.g., pedestrians, cyclists), or road features.

[0076] Human drivers and autonomous vehicles may operate with different characteristics, including reaction time to detected vehicles, road users, or road conditions, and how close they may operate to other vehicles and road features. In a mixed environment of both autonomous and non-autonomous vehicles, the propagation of sensor sharing data and maneuver requests may be customized based on the capabilities of the receiving vehicle, whether that vehicle is an autonomous vehicle activating / deactivating autonomous mode or a non-autonomous vehicle. Identifying standards and mechanisms for customizing data distribution to vehicles based on their AV capabilities may allow for successful deployment of autonomous vehicles.

[0077] Various aspects presented herein provide a configuration for scenario-specific alerts for autonomous vehicles and non-autonomous vehicles. For example, various aspects presented herein may identify a set of standard or over-the-air signaling for a network entity to provide vehicle-specific sensor shared data (e.g., vehicle road users, non-vehicle road users, or road conditions) to an autonomous vehicle that has autonomous functionality activated, an autonomous vehicle that has autonomous functionality deactivated, or a non-autonomous vehicle. At least one advantage of the present disclosure is that the vehicle-specific sensor shared data can be communicated over a cellular wireless network (e.g., Uu) or via sidelink communications at an application layer or lower layer (e.g., PC5).

[0078] Human-driven vehicles, autonomous vehicles can be distinguished by their intake of environmental data and the corresponding ability to react to environmental data (e.g., other road vehicles, VRUs or road hazards). Autonomous vehicles may be able to consume and process more data, including data beyond the field of view of human drivers. About reaction time, human reaction time can rely on human perception reaction time, which can be, for example, up to or longer than 2.5 seconds, and autonomous vehicles may be able to react in sub-second time. About data intake, autonomous vehicles can receive and / or process a large number of objects (e.g., vehicles, VRUs or road hazards) from other vehicles or from network propagation. However, human drivers can only react or consider these objects to objects in their visible surroundings (e.g., obstacles VRUs propagated via shared propagation of sensors from other vehicles or from the network) or objects perceived by human drivers. The field of view of human drivers or the ability to perceive objects vary from person to person, and can be substantially dissimilar between people. About the scope of data, human drivers are limited to the human driver field of view. The human field of view may be constrained by the direction the human is looking, as well as environmental conditions such as, but not limited to, lighting conditions (e.g., daytime versus nighttime), precipitation (e.g., snow, fog, hail, etc.), oncoming vehicles (e.g., headlight glare), or other (e.g., smoke). An autonomous vehicle or non-autonomous field of view may provide more coverage than the somewhat narrower human field of view, for example, by employing a variety of sensors to provide potentially up to a 360-degree field of view (e.g., deploying one or more cameras, one or more radars, one or more sonars, one or more laser-based sensors, etc.). Still further, some example vehicles may be capable of processing received data corresponding to one or more areas beyond the sensor field of view, and incorporating such data into a decision engine and a planned route of travel.

[0079] Figure 44 is a diagram illustrating an example of an autonomous vehicle and a non-autonomous vehicle in an access network. In the diagram, 400 includes an autonomous vehicle (AV) 402, an AV 404, and a non-AV 406. The AV 402 may start an autonomous mode. The AV 404 may deactivate the autonomous mode. The AV 402 may communicate with a network entity 408 and provide vehicle capabilities 412 via an application layer, PC5, or Uu, wherein the Uu may include an application layer message, an RRC message, or a lower layer signaling (e.g., MAC-CE), and the PC5 may include an application layer message, PC5-RRC, PC5 signaling, or a lower layer signaling (e.g., MAC-CE). The vehicle capabilities 412 may indicate the data processing capabilities of the AV 402 to the network when the autonomous mode is started. The AV 402 may receive an alert 414 customized for the AV 402 based on the vehicle capabilities 412. The AV 404 may communicate with the network entity 408 and provide vehicle capabilities 416 via an application layer, PC5, or Uu (e.g., signaling, MAC-CE). The vehicle capabilities 416 may indicate the data processing capabilities of the AV 404 to the network when the autonomous mode is released. The AV 404 may receive an alert 418 customized for the AV 404 based on the vehicle capabilities 416. The non-AV 406 may communicate with the network entity 408 and provide vehicle capabilities 420 via an application layer, PC5, or Uu (e.g., signaling, MAC-CE). The vehicle capabilities 420 may indicate the data processing capabilities of the non-AV 406 to the network. The non-AV 406 may receive an alert 422 customized for the non-AV 406 based on the vehicle capabilities 420.

[0080] The network entity 408 may receive environmental information 410 from the network related to weather, maps, road conditions, traffic, etc. The environmental information 410 may be collected from other vehicles or third-party sources, and the network entity 408 may be configured to issue vehicle-specific guidance to the AV (e.g., 402, 404) or non-AV 406.

[0081] Figure 5500 is a diagram illustrating an example of an autonomous vehicle and a non-autonomous vehicle in an access network. In some cases, a vehicle may relay an alert from the network to one or more other vehicles. For example, as shown in diagram 500, AV 502 may provide vehicle capabilities 512 to network 508, and network 508 may provide alerts 514 that may include environmental information 510 based on vehicle capabilities 512. In some cases, AV 502 may act as a relay source and relay alerts 514 to one or more vehicles. For example, AV 502 may relay alerts 514 to AV 504. AV 504 may activate or deactivate an autonomous mode. In the case where AV 504 activates an autonomous mode, AV 504 may utilize alerts 514. However, in some cases, not all vehicles have AV capabilities. For example, some vehicles may be non-AVs (e.g., 506). In such cases, the AV 502 may still relay the alert 516 to the non-AV 506, but the non-AV 506 may not be able to utilize the alert 516 or may only be able to utilize a portion of the alert 516. In some aspects, the AV 502 may customize the alerts (e.g., 514, 516) based on the type of vehicle (e.g., AV or non-AV activating / deactivating autonomous mode). The AV 502 may customize the alerts based on the type of vehicle based on capability indications received from one or more vehicles. In yet other cases, the AV 502 may modify the alerts (e.g., 514, 516) relayed to other vehicles (e.g., 504, 506) to provide a baseline alert that can be utilized by any vehicle.

[0082] Figure 6 600 is a call flow diagram of signaling between a UE 602 and a base station 604. The base station 604 may be configured to provide at least one cell. The UE 602 may be configured to communicate with the base station 604. For example, in Figure 1 In the context of , base station 604 may correspond to base station 102 and. In addition, UE 602 may correspond to at least UE 104. In another example, in Figure 3 In the context of , base station 604 may correspond to base station 310 and UE 602 may correspond to UE 350.

[0083] At 606, UE 602 may send a capability indication of the UE to base station 604. Base station 604 may receive a capability indication of the UE from UE 602. The capability indication may indicate that UE 602 is paired with a vehicle. The term "pairing" as used herein is used to indicate that the UE is communicatively coupled to the vehicle so that the UE and the vehicle can communicate with each other. The UE and the vehicle may be communicatively coupled (e.g., paired) via a wired or wireless connection. In addition, unless otherwise specified, such terms as used herein and / or in the claims are not necessarily intended to be limited to only one specific communication protocol or system. The vehicle may include an autonomous vehicle or a non-autonomous vehicle. In some cases, the capability indication may indicate that the UE is paired with an autonomous vehicle or a non-autonomous vehicle. In some aspects, the capability indication may indicate that the autonomous mode of the autonomous vehicle is activated or released. In some aspects, the capability indication may be included in wireless communication. In such aspects, the vehicle-specific signal may be included in at least one of an application layer message, an RRC message, or a physical layer message. In some aspects, the capability indication may be included in short-range wireless communication. For example, the capability indication may be included within a short-range wireless device-to-device communication protocol, such as sidelink, WiFi, or dedicated short-range communication (DSRC). The vehicle-specific signal may be included within at least one of an application layer message, an RRC message, or a physical layer message.

[0084] At 608, the base station 604 may generate a vehicle-specific signal based on a capability indication indicating that the UE 602 is paired with the vehicle. In some aspects, the data within the vehicle-specific signal may be customized for the UE paired with the vehicle. For example, the data within the vehicle-specific signal may be customized for the paired combination of the UE and the vehicle. In some aspects, the vehicle may include an autonomous vehicle so that an autonomous mode of the autonomous vehicle is activated. The autonomous vehicle may have one or more autonomous modes, wherein the one or more autonomous modes have different levels of autonomous operation. For example, according to a system developed by the Society of Automotive Engineers (SAE) International (e.g., SAE J3016), autonomy in a vehicle may be classified into six levels. The SAE levels may be classified as Level 0 - No Automation, the human driver does everything; Level 1 - Hands on the wheel / Shared control, where the automated system may sometimes assist the human driver in performing some parts of the driving task; Level 2 - Hands free, where the automated system may actually perform some parts of the driving task, while the human continues to monitor the driving environment and perform the rest of the driving task; Level 3 - Eyes free, where the automated system may actually perform some parts of the driving task and monitor the driving environment in some cases, but the human driver must be ready to take back control when the automated system requests it; Level 4 - Attention free, where the automated system may perform the driving task to monitor the driving environment, and the human does not need to take back control, but the automated system may only operate in certain environments and under certain conditions; and Level 5 - Steering wheel optional, where the automated system may perform all driving tasks under all conditions where the human driver may perform all driving tasks. In some cases, some of the data may correspond to one or more other vehicles, one or more road users, one or more road conditions, one or more traffic conditions, one or more sensor fields of view, one or more depths, one or more ranges, etc., or some combination thereof. In some aspects, where the vehicle includes a non-autonomous vehicle, at least a portion of the data may include at least information associated with the proximity of the non-autonomous vehicle for a UE paired with the non-autonomous vehicle. In some aspects, where the vehicle includes an autonomous vehicle, at least a portion of the data may include at least information associated with the proximity of the autonomous vehicle for a UE paired with an autonomous vehicle for use by the autonomous vehicle when the autonomous mode of the autonomous vehicle is released. In some aspects, the proximity of the non-autonomous vehicle for a UE paired with a non-autonomous vehicle or the proximity of the autonomous vehicle for a UE paired with an autonomous vehicle may correspond to all or part of the estimated field of view of the operator of the non-autonomous vehicle, the autonomous vehicle, or both. In some aspects, the operator of the autonomous vehicle may include a remotely located operator capable of affecting at least some operation of the autonomous vehicle. In yet other aspects, the operator of the non-autonomous vehicle or the autonomous vehicle may include a driver or other operator located within the vehicle.In some aspects, where the vehicle comprises a non-autonomous vehicle, the data within the vehicle-specific signal may be based at least in part on an indication of an estimated or expected reaction time of an operator of the vehicle. In some aspects, where the vehicle comprises an autonomous vehicle, the data within the vehicle-specific signal may be based at least in part on an expected data processing capability of the autonomous vehicle, an estimated or expected reaction time of an operator of the autonomous vehicle, or both.

[0085] At 610, the base station 604 may output a vehicle-specific signal. The base station 604 may output (e.g., generate, transmit, etc.) a vehicle-specific signal to the UE 602. The UE 602 may be paired with a vehicle. The UE 602 may receive the vehicle-specific signal from the base station 604 or possibly from another network entity. The transmission of the vehicle-specific signal may include one or more application layer messages, one or more radio resource control (RRC) messages, or one or more physical layer messages. In some aspects, the vehicle-specific signal may include a content-specific alert. The content-specific alert may be intended to be used by the paired UE alone, by the UE and the vehicle in a distributed manner, by the UE and by the vehicle in a separate manner, or may be delivered by the UE to the vehicle for processing by the vehicle. For example, a paired UE may receive a content-specific alert intended to be sent to another UE so that only the paired UE utilizes the content-specific alert. In another example, the UE may receive a scenario-specific alert including map information, wherein the UE may utilize the map information to plot a route, and the vehicle may utilize the map information to know the upcoming road conditions, so that the UE and the vehicle utilize the content-specific alert in a distributed manner. In another example, the UE may receive a context-specific alert including a traffic condition, which may be used by the UE to calculate a new route based on the traffic condition, and the vehicle may utilize the context-specific alert to activate / deactivate an operating mode of the vehicle in response to the context-specific alert, such that the UE and the vehicle utilize the context-specific alert for different purposes. In another example, the UE may receive a context-specific alert including an indication of a nearby upcoming obstacle, such that the UE communicates the context-specific alert for processing by the vehicle.

[0086] At 612, UE 602 may send a second vehicle-specific signal to one or more UEs (not shown) via sidelink communication. In some aspects, each of the one or more UEs (not shown) may be paired with a corresponding autonomous vehicle or a corresponding non-autonomous vehicle, wherein UE 602 and one or more UEs (not shown) may be within a UE group or may be within a threshold proximity to each other. In some aspects, a vehicle-specific signal may be sent by UE 602 to one or more UEs. The vehicle-specific signal may be sent via broadcast, multicast, or unicast. In some aspects, the second vehicle-specific signal may be processed to correspond to the vehicle capabilities of one or more UEs based on a vehicle-specific signal received by a first UE (e.g., UE 602) from a network entity. In some aspects, the second vehicle-specific signal may include at least a portion of a vehicle-specific signal received by the first UE from a network entity.

[0087] Figure 7 700 is a flow chart of a wireless communication method. The method may be performed by a base station (eg, base station 102; network entity 802). One or more of the illustrated operations may be omitted, swapped, or performed simultaneously. The method may provide vehicle-specific sensor sharing data to an autonomous vehicle or a non-autonomous vehicle.

[0088] At 702, the network entity may obtain a capability indication of the UE. For example, 702 may be performed by the signal component 199 of the network entity 802. The capability indication may indicate that the UE is paired with a vehicle. The vehicle may include an autonomous vehicle or a non-autonomous vehicle. In some cases, the capability indication may indicate that the UE is paired with an autonomous vehicle or a non-autonomous vehicle. In some aspects, the capability indication may indicate that the autonomous mode of the autonomous vehicle is activated or released. In some aspects, the capability indication may be included in the wireless communication. The wireless communication including the capability indication may be received via the transceiver of the network entity. In some aspects, the capability indication may be included in the short-range wireless communication. For example, the capability indication may be included in a short-range wireless device-to-device communication protocol (e.g., side link, WiFi, or DSRC). The vehicle-specific signal may be included in at least one of an application layer message, an RRC message, or a physical layer message.

[0089] At 704, the network entity may generate a vehicle-specific signal. For example, 704 may be performed by the signal component 199 of the network entity 802. The network entity may generate a vehicle-specific signal based on a capability indication indicating that the UE is paired with the vehicle. In some aspects, the data within the vehicle-specific signal may be customized for the UE paired with the vehicle. For example, the data within the vehicle-specific signal may be customized for the paired combination of the UE and the vehicle. In some aspects, the vehicle may include an autonomous vehicle so that the autonomous mode of the autonomous vehicle is activated. In such cases, some of the data may correspond to one or more other vehicles or otherwise known vehicles, one or more road users, one or more road conditions, one or more traffic conditions, one or more sensor fields of view, one or more depths, one or more ranges, etc., or some combination thereof. In some aspects, in response to the vehicle including a non-autonomous vehicle, at least a portion of the data may include at least information associated with the proximity of the non-autonomous vehicle for the UE paired with the non-autonomous vehicle. In some aspects, in response to the vehicle including an autonomous vehicle, at least a portion of the data may include at least information associated with the proximity of the autonomous vehicle for the UE paired with the autonomous vehicle for use by the autonomous vehicle when the autonomous mode of the autonomous vehicle is released. In some aspects, information about the proximity of a non-autonomous vehicle for a UE paired with a non-autonomous vehicle or the proximity of an autonomous vehicle for a UE paired with an autonomous vehicle may correspond to an estimated field of view of an operator of the vehicle. In some aspects, the operator of an autonomous vehicle may include a remotely located operator that can affect at least some operation of the autonomous vehicle. In yet other aspects, the operator of a non-autonomous vehicle or an autonomous vehicle may include a driver or other operator located within the vehicle. In some aspects, in response to the vehicle including a non-autonomous vehicle, the data within the vehicle-specific signal may be based at least in part on an indication of an estimated or expected reaction time of an operator of the non-autonomous vehicle. In some aspects, in response to the vehicle including an autonomous vehicle, the data within the vehicle-specific signal may be based at least in part on an indication of an estimated or expected reaction time of an operator of the non-autonomous vehicle. In some aspects, in response to the vehicle including an autonomous vehicle, the data within the vehicle-specific signal may be based at least in part on an expected data processing capability of the autonomous vehicle, an estimated or expected reaction time of an operator of the autonomous vehicle, or both.

[0090] At 706, the network entity may output a vehicle-specific signal. For example, 706 may be performed by the signal component 199 of the network entity 802. The network entity may output the vehicle-specific signal to the UE. The UE is paired with a vehicle (e.g., an autonomous vehicle or a non-autonomous vehicle). The transmission of the vehicle-specific signal may include one or more application layer messages, one or more RRC messages, or one or more physical layer messages. In some aspects, a processor associated with the signal component may be configured to output the vehicle-specific signal by initiating the transmission of the vehicle-specific signal via the transceiver.

[0091] Figure 8800 is a diagram illustrating an example of a hardware implementation for a network entity 802. The network entity 802 may be a BS, a component of a BS, or may implement BS functionality. The network entity 802 may include at least one of a CU 810, a DU 830, or a RU 840. For example, depending on the layer functionality handled by the component 199, the network entity 802 may include a CU 810; both a CU 810 and a DU 830; each of the CU 810, the DU 830, and the RU 840; the DU 830; both the DU 830 and the RU 840; or the RU 840. The CU 810 may include a CU processor 812. The CU processor 812 may include an on-chip memory 812'. In some aspects, the CU 810 may also include an additional memory module 814 and a communication interface 818. The CU 810 communicates with the DU 830 via a midhaul link, such as an F1 interface. DU 830 may include a DU processor 832. DU processor 832 may include on-chip memory 832'. In some aspects, DU830 may also include an additional memory module 834 and a communication interface 838. DU 830 communicates with RU 840 via a fronthaul link. RU 840 may include a RU processor 842. RU processor 842 may include on-chip memory 842'. In some aspects, RU840 may also include an additional memory module 844, one or more transceivers 846, an antenna 880, and a communication interface 848. RU840 communicates with UE 104. On-chip memory 812', 832', 842' and additional memory modules 814, 834, 844 may each be considered a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory. Each of processors 812, 832, 842 is responsible for general processing, including executing software stored on a computer-readable medium / memory. The software, when executed by a corresponding processor, causes the processor to perform the various functions described above.The computer-readable medium / memory may also be used to store data that is manipulated by the processor when executing the software.

[0092] As discussed above, component 199 is configured to obtain a capability indication of the UE, the capability indication indicating that the UE is paired with a vehicle; generate a vehicle-specific signal based on the capability indication indicating that the UE is paired with a vehicle; and output the vehicle-specific signal to the UE. Component 199 may be within one or more processors of one or more of CU 810, DU 830, and RU 840. Component 199 may be one or more hardware components that are specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to perform the stated process / algorithm, stored in a computer-readable medium so as to be implemented by one or more processors, or some combination of the above. Network entity 802 may include a variety of components configured for various functions. In one configuration, network entity 802 includes a component for obtaining a capability indication of the UE, the capability indication indicating that the UE is paired with a vehicle. The network entity includes a component for generating a vehicle-specific signal based on the capability indication indicating that the UE is paired with a vehicle. The network entity includes a component for outputting a vehicle-specific signal to the UE. The component may be a component 199 of network entity 802 configured to perform the function recorded by the component. As described above, the network entity 802 may include the TX processor 316, the RX processor 370, and the controller / processor 375. Thus, in one configuration, the components may be the TX processor 316, the RX processor 370, and / or the controller / processor 375 configured to perform the functions recited by the components.

[0093] Fig. 9 900 is a flow chart of a wireless communication method. The method may be performed by a UE (e.g., UE 104; device 1104). One or more of the illustrated operations may be omitted, swapped, or performed simultaneously. The method may be a UE receiving vehicle-specific sensor sharing data based on whether the UE is included in an autonomous vehicle or a non-autonomous vehicle.

[0094] At 902, the UE may send a capability indication of the UE. For example, 902 may be performed by the capability component 198 of the device 1104. The UE may send a capability indication of the UE to a network entity. The capability indication may indicate that the UE is paired with a vehicle. The vehicle may include an autonomous vehicle or a non-autonomous vehicle. In some cases, the capability indication may indicate that the UE is paired with an autonomous vehicle or a non-autonomous vehicle. In some aspects, the capability indication may indicate that the autonomous mode of the autonomous vehicle is activated or released. In some aspects, the capability indication may be included in wireless communication. Wireless communication including the capability indication may be sent via the transceiver of the UE. In some aspects, the capability indication may be included in short-range wireless communication. For example, the capability indication may be included in a short-range wireless device-to-device communication protocol (e.g., side link, WiFi, or DSRC). The vehicle-specific signal may be included in at least one of an application layer message, an RRC message, or a physical layer message.

[0095] At 904, the UE may receive a vehicle-specific signal. For example, 904 may be performed by the capability component 198 of the device 1104. The UE may receive a vehicle-specific signal from a network entity. The vehicle-specific signal may be based on a capability indication indicating that the UE is paired with an autonomous vehicle or a non-autonomous vehicle. In some aspects, the data within the vehicle-specific signal may be customized according to the pairing combination of the UE and the vehicle. For example, the data within the vehicle-specific signal may be customized for a UE paired with an autonomous vehicle, or for a UE paired with a non-autonomous vehicle, or both. In the case where the vehicle includes an autonomous vehicle and the autonomous mode of the autonomous vehicle is activated, some of the data may correspond to one or more other vehicles, one or more road users, one or more road conditions, one or more traffic conditions, one or more sensor fields of view, one or more depths, one or more ranges, etc., or some combination thereof. In some aspects, in response to the vehicle including a non-autonomous vehicle, at least a portion of the data may include at least information associated with the proximity of a non-autonomous vehicle for a UE paired with a non-autonomous vehicle. In some aspects, in response to the vehicle comprising an autonomous vehicle, at least a portion of the data may include at least information associated with the proximity of the autonomous vehicle for a UE paired with the autonomous vehicle for use by the autonomous vehicle when the autonomous mode of the autonomous vehicle is released. In some aspects, the proximity of the non-autonomous vehicle for a UE paired with a non-autonomous vehicle or the proximity of the autonomous vehicle for a UE paired with an autonomous vehicle may correspond to the field of view of the operator of the vehicle. In some aspects, in response to the vehicle comprising a non-autonomous vehicle, the data within the vehicle-specific signal may be based at least in part on an estimated or expected reaction time of the operator of the non-autonomous vehicle. In some aspects, in response to the vehicle comprising an autonomous vehicle, the data within the vehicle-specific signal may be based at least in part on the expected data processing capabilities of the autonomous vehicle, the expected reaction time of the operator of the autonomous vehicle, or both. The reception of the vehicle-specific signal may include one or more application layer messages, one or more RRC messages, or one or more physical layer messages. In some aspects, a processor associated with the capability component may be configured to receive the vehicle-specific signal by initiating the reception of the vehicle-specific signal via a transceiver.

[0096] Fig.10 1000 is a flow chart of a wireless communication method. The method may be performed by a UE (e.g., UE 104; device 1104). One or more of the illustrated operations may be omitted, swapped, or performed simultaneously. The method may be a UE receiving vehicle-specific sensor sharing data based on whether the UE is included in an autonomous vehicle or a non-autonomous vehicle.

[0097] At 1002, the UE may send a capability indication of the UE. For example, 1002 may be performed by the capability component 198 of the device 1104. The UE may send a capability indication of the UE to a network entity. The capability indication may indicate that the UE is paired with a vehicle. The vehicle may include an autonomous vehicle or a non-autonomous vehicle. In some cases, the capability indication may indicate that the UE is paired with an autonomous vehicle or a non-autonomous vehicle. In some aspects, the capability indication may indicate that the autonomous mode of the autonomous vehicle is activated or released. In some aspects, the capability indication may be included in wireless communication. Wireless communication including the capability indication may be sent via the transceiver of the UE. In some aspects, the capability indication may be included in short-range wireless communication. For example, the capability indication may be included in a short-range wireless device-to-device communication protocol (e.g., side link, WiFi, or DSRC). The vehicle-specific signal may be included in at least one of an application layer message, an RRC message, or a physical layer message.

[0098] At 1004, the UE may receive a vehicle-specific signal. For example, 1004 may be performed by the capability component 198 of the device 1104. The UE may receive a vehicle-specific signal from a network entity. The vehicle-specific signal may be based on a capability indication indicating that the UE is paired with an autonomous vehicle or a non-autonomous vehicle. In some aspects, the data within the vehicle-specific signal may be customized according to the pairing combination of the UE and the vehicle. For example, the data within the vehicle-specific signal may be customized for a UE paired with an autonomous vehicle, or for a UE paired with a non-autonomous vehicle, or both. In the case where the vehicle includes an autonomous vehicle and the autonomous mode of the autonomous vehicle is activated, some of the data may correspond to one or more other vehicles, one or more road users, one or more road conditions, one or more traffic conditions, one or more sensor fields of view, one or more depths, one or more ranges, etc., or some combination thereof. In some aspects, in response to the vehicle including a non-autonomous vehicle, at least a portion of the data may include at least information associated with the proximity of a non-autonomous vehicle for a UE paired with a non-autonomous vehicle. In some aspects, in response to the vehicle comprising an autonomous vehicle, at least a portion of the data may include at least information associated with the proximity of the autonomous vehicle for a UE paired with the autonomous vehicle for use by the autonomous vehicle when the autonomous mode of the autonomous vehicle is released. In some aspects, the proximity of the non-autonomous vehicle for a UE paired with a non-autonomous vehicle or the proximity of the autonomous vehicle for a UE paired with an autonomous vehicle may correspond to the field of view of the operator of the vehicle. In some aspects, in response to the vehicle comprising a non-autonomous vehicle, the data within the vehicle-specific signal may be based at least in part on an estimated or expected reaction time of the operator of the non-autonomous vehicle. In some aspects, in response to the vehicle comprising an autonomous vehicle, the data within the vehicle-specific signal may be based at least in part on the expected data processing capabilities of the autonomous vehicle, the expected reaction time of the operator of the autonomous vehicle, or both. The reception of the vehicle-specific signal may include one or more application layer messages, one or more RRC messages, or one or more physical layer messages. In some aspects, a processor associated with the capability component may be configured to receive the vehicle-specific signal by initiating the reception of the vehicle-specific signal via a transceiver.

[0099] At 1006, the UE may send a second vehicle-specific signal to one or more UEs via sidelink communication. For example, 1006 may be performed by the capability component 198 of the device 1104. In some aspects, each of the one or more UEs may be paired with a corresponding autonomous vehicle or a corresponding non-autonomous vehicle. In some aspects, the vehicle-specific signal may be sent to one or more UEs via broadcast, multicast, or unicast. In some aspects, the second vehicle-specific signal may be processed to correspond to the vehicle capabilities of the one or more UEs based on the vehicle-specific signal received from the network entity. In some aspects, the second vehicle-specific signal may include at least a portion of the vehicle-specific signal received by the first UE from the network entity.

[0100] Fig.111100 is a diagram illustrating an example of a hardware implementation for an apparatus 1104. The apparatus 1104 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1104 may include a cellular baseband processor 1124 (also referred to as a modem) coupled to one or more transceivers 1122 (e.g., a cellular RF transceiver). The cellular baseband processor 1124 may include on-chip memory 1124'. In some aspects, the apparatus 1104 may also include one or more subscriber identity module (SIM) cards 1120 and an application processor 1106 coupled to a secure digital (SD) card 1108 and a screen 1110. The application processor 1106 may include on-chip memory 1106'. In some aspects, the device 1104 may also include a Bluetooth module 1112, a WLAN module 1114, an SPS module 1116 (e.g., a GNSS module), one or more sensor modules 1118 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor such as an inertial management unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-aided detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 1126, a power source 1130, and / or a camera 1132. The Bluetooth module 1112, the WLAN module 1114, and the SPS module 1116 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (RX)). The Bluetooth module 1112, the WLAN module 1114, and the SPS module 1116 may include their own dedicated antennas and / or communicate using antennas 1180. The cellular baseband processor 1124 communicates with the UE 104 and / or with the RU associated with the network entity 1102 through the transceiver 1122 via one or more antennas 1180. The cellular baseband processor 1124 and the application processor 1106 may each include a computer-readable medium / memory 1124', 1106', respectively. The additional memory module 1126 may also be considered as a computer-readable medium / memory. Each computer-readable medium / memory 1124', 1106', 1126 may be non-transitory. The cellular baseband processor 1124 and the application processor 1106 are each responsible for general processing, including executing software stored on a computer-readable medium / memory. The software enables the cellular baseband processor 1124 / application processor 1106 to perform the various functions described above when executed by the cellular baseband processor 1124 / application processor 1106. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 1124 / application processor 1106 when executing the software.The cellular baseband processor 1124 / application processor 1106 may be a component of the UE 350 and may include the memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, the device 1104 may be a processor chip (modem and / or application) and include only the cellular baseband processor 1124 and / or the application processor 1106, and in another configuration, the device 1104 may be the entire UE (e.g., see. Figure 3 350) and includes additional modules of device 1104.

[0101] As discussed above, component 198 is configured to send a capability indication of the UE to a network entity, the capability indication indicating that the UE is paired with a vehicle; and receive a vehicle-specific signal from the network entity based on the capability indication indicating that the UE is paired with a vehicle. Component 198 may be within the cellular baseband processor 1124, the application processor 1106, or both the cellular baseband processor 1124 and the application processor 1106. Component 198 may be one or more hardware components that are specifically configured to perform the stated process / algorithm, implemented by one or more processors configured to perform the stated process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination of the above. As shown, the device 1104 may include a variety of components configured for various functions. In one configuration, the device 1104 (and specifically the cellular baseband processor 1124 and / or the application processor 1106) includes a component for sending a capability indication of the UE to a network entity, the capability indication indicating that the UE is paired with a vehicle. The device includes a component for receiving a vehicle-specific signal based on the capability indication indicating that the UE is paired with a vehicle from a network entity. The apparatus also includes means for transmitting a second vehicle-specific signal to one or more UEs via sidelink communication. The means may be a component 198 of the apparatus 1104 configured to perform the functions recited by the means. As described above, the apparatus 1104 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Thus, in one configuration, the means may be a TX processor 368, an RX processor 356, and / or a controller / processor 359 configured to perform the functions recited by the means.

[0102] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is merely an illustration of the exemplary method. It should be understood that the specific order or hierarchy of the blocks in the process / flowchart may be rearranged based on design preferences. Further, some blocks may be combined or omitted. The attached method claims present the elements of the various blocks in a sample order, but are not limited to the specific order or hierarchy presented.

[0103] The foregoing 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 apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not limited to the various aspects described herein, but should be given the full scope consistent with the language claims. Unless otherwise specified, reference to an element in the singular form does not mean "one and only one", but "one or more". Terms such as "if", "when" and "while" do not mean a direct temporal relationship or reaction. That is, these phrases, such as "when ......", do not mean an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply imply that if the conditions are met, the action will occur, but no specific or immediate time limit is required for the occurrence of the action. The word "exemplary" is used herein to mean "used as an example, instance, or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having advantages over other aspects. Unless otherwise specified, the term "some" 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, which 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 only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a set of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If the first device receives data from the second device or sends data to the second device, the data may be received / sent directly between the first device and the second device, or indirectly between the first device and the second device through a collection of devices. All structural and functional equivalents of the elements of the various aspects described throughout the present disclosure that are known or will later be known to a person of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims. Words such as "module", "mechanism", "element", "device", etc. cannot replace the word "component". Therefore, no claim element will be understood as a component plus function unless the element is explicitly stated using the phrase "component for..."

[0104] As used herein, the phrase "based on" should not be interpreted as referring to a closed set of information, one or more conditions, one or more factors, etc. In other words, the phrase "based on A" (where "A" can be information, a condition, a factor, etc.) should be interpreted as "based at least on A" unless specifically stated differently.

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

[0106] Aspect 1 is a method for performing wireless communication at a network entity, the method comprising: obtaining a capability indication of a UE, the capability indication indicating that the UE is paired with a vehicle; generating a vehicle-specific signal based on the capability indication indicating that the UE is paired with the vehicle; and outputting the vehicle-specific signal to the UE.

[0107] Aspect 2 is a method according to aspect 1, the method further comprising: the vehicle comprises an autonomous vehicle, and wherein the capability indication further indicates that an autonomous mode of the autonomous vehicle is activated or released.

[0108] Aspect 3 is a method according to any one of Aspects 1 and 2, the method further comprising: the data within the vehicle-specific signal is customized for the paired combination of the UE and the vehicle.

[0109] Aspect 4 is a method according to any one of Aspects 1 to 3, the method also including: the vehicle includes an autonomous vehicle and the autonomous mode of the autonomous vehicle is activated, and wherein the data corresponds to one or more other vehicles, one or more road users, one or more road conditions, one or more traffic conditions, one or more fields of view of sensors, one or more depths, one or more ranges, or some combination thereof.

[0110] Aspect 5 is a method according to any one of Aspects 1 to 4, the method further comprising: in response to the vehicle including a non-autonomous vehicle, the data at least includes information associated with the proximity of the non-autonomous vehicle of the UE for pairing with the non-autonomous vehicle, or in response to the vehicle including an autonomous vehicle, the data at least includes information associated with the proximity of the autonomous vehicle of the UE for pairing with the autonomous vehicle for use by the autonomous vehicle when the autonomous mode of the autonomous vehicle is released.

[0111] Aspect 6 is a method according to any one of Aspects 1 to 5, the method further comprising: the proximity of the non-autonomous vehicle of the UE for pairing with the non-autonomous vehicle or the proximity of the autonomous vehicle of the UE for pairing with the autonomous vehicle corresponds to an estimated field of view of an operator of the vehicle.

[0112] Aspect 7 is a method according to any one of Aspects 1 to 6, the method further comprising: in response to the vehicle comprising a non-autonomous vehicle, the data within the vehicle-specific signal is at least partially based on an expected reaction time of an operator of the non-autonomous vehicle, or in response to the vehicle comprising an autonomous vehicle, the data within the vehicle-specific signal is at least partially based on an expected data processing capability of the autonomous vehicle, an expected reaction time of the operator of the autonomous vehicle, or both.

[0113] Aspect 8 is a method according to any one of aspects 1 to 7, the method further comprising: the capability indication is included in a wireless communication received via a transceiver.

[0114] Aspect 9 is a method according to any one of Aspects 1 to 8, the method further comprising: the sending of the vehicle-specific signal includes one or more application layer messages, one or more RRC messages or one or more physical layer messages.

[0115] Aspect 10 is a method according to any one of Aspects 1 to 9, the method further comprising: the capability indication is included in the short-range wireless communication, wherein the vehicle-specific signal is included in at least one of an application layer message, an RRC message or a physical layer message.

[0116] Aspect 11 is a method according to any one of aspects 1 to 10, the method further comprising: the vehicle comprises an autonomous vehicle or a non-autonomous vehicle.

[0117] Aspect 12 is a method according to any one of aspects 1 to 11, the method further comprising: outputting the vehicle specific signal by initiating transmission of the vehicle specific signal via a transceiver.

[0118] Aspect 13 is an apparatus for wireless communication at a network entity, the apparatus comprising at least one processor coupled to a memory and at least one transceiver, the at least one processor being configured to implement any one of aspects 1 to 12.

[0119] Aspect 14 is an apparatus for wireless communication at a network entity, the apparatus comprising means for implementing any one of aspects 1 to 12.

[0120] Aspect 15 is a computer-readable medium storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 1 to 12.

[0121] Aspect 16 is a method for performing wireless communication at a UE, the method comprising: sending a capability indication of the UE to a network entity, the capability indication indicating that the UE is paired with a vehicle; and receiving a vehicle-specific signal from the network entity based on the capability indication indicating that the UE is paired with the vehicle.

[0122] Aspect 17 is a method according to aspect 16, the method further comprising: the vehicle comprises an autonomous vehicle, and wherein the capability indication further indicates that an autonomous mode of the autonomous vehicle is activated or released.

[0123] Aspect 18 is a method according to any one of aspects 16 and 17, the method further comprising: the data within the vehicle-specific signal is customized according to a paired combination of the UE and the vehicle.

[0124] Aspect 19 is a method according to any one of Aspects 16 to 18, the method further comprising: the vehicle comprises an autonomous vehicle and the autonomous mode of the autonomous vehicle is activated, and wherein the data corresponds to one or more other vehicles, one or more road users, one or more road conditions, one or more traffic conditions, one or more fields of view of sensors, one or more depths, one or more ranges, or some combination thereof.

[0125] Aspect 20 is a method according to any one of Aspects 16 to 19, the method further comprising: in response to the vehicle comprising a non-autonomous vehicle, the data at least comprising information associated with the proximity of the non-autonomous vehicle of the UE for pairing with the non-autonomous vehicle, or in response to the vehicle comprising an autonomous vehicle, the data at least comprising information associated with the proximity of the autonomous vehicle of the UE for pairing with the autonomous vehicle for use by the autonomous vehicle when the autonomous mode of the autonomous vehicle is released, wherein the proximity of the non-autonomous vehicle of the UE for pairing with the non-autonomous vehicle or the proximity of the autonomous vehicle of the UE for pairing with the autonomous vehicle corresponds to an estimated field of view of an operator of the vehicle.

[0126] Aspect 21 is a method according to any one of Aspects 16 to 20, the method further comprising: in response to the vehicle comprising a non-autonomous vehicle, the data within the vehicle-specific signal is at least partially based on an expected reaction time of an operator of the non-autonomous vehicle, or in response to the vehicle comprising an autonomous vehicle, the data within the vehicle-specific signal is at least partially based on an expected data processing capability of the autonomous vehicle, an expected reaction time of the operator of the autonomous vehicle, or both.

[0127] Aspect 22 is a method according to any one of aspects 16 to 21, the method further comprising: the capability indication is included in a wireless communication sent via a transceiver.

[0128] Aspect 23 is a method according to any one of Aspects 16 to 22, the method further comprising: the reception of the vehicle-specific signal includes one or more application layer messages, one or more RRC messages or one or more physical layer messages.

[0129] Aspect 24 is a method according to any one of Aspects 16 to 23, the method further comprising: the capability indication is included in the short-range wireless communication, wherein the vehicle-specific signal is included in at least one of an application layer message, an RRC message or a physical layer message.

[0130] Aspect 25 is a method according to any one of aspects 16 to 24, the method further comprising: the vehicle comprises an autonomous vehicle or a non-autonomous vehicle.

[0131] Aspect 26 is a method according to any one of aspects 16 to 25, the method further comprising: sending a second vehicle-specific signal to one or more UEs via sidelink communication.

[0132] Aspect 27 is a method according to any one of aspects 16 to 26, the method further comprising: each UE of the one or more UEs is paired with a corresponding autonomous vehicle or a corresponding non-autonomous vehicle.

[0133] Aspect 28 is a method according to any one of aspects 16 to 27, the method further comprising: the vehicle-specific signal sent to the one or more UEs is sent via broadcast, groupcast or unicast.

[0134] Aspect 29 is a method according to any one of aspects 16 to 28, the method further comprising: the second vehicle-specific signal is processed to correspond to the vehicle capabilities of the one or more UEs based on the vehicle-specific signal received from the network entity.

[0135] Aspect 30 is a method according to any one of aspects 16 to 29, the method further comprising: the second vehicle-specific signal comprises the vehicle-specific signal received from the network entity.

[0136] Aspect 31 is a method according to any one of aspects 16 to 30, the method further comprising: receiving the vehicle specific signal by initiating reception of the vehicle specific signal via the transceiver.

[0137] Aspect 32 is an apparatus for wireless communication at a UE, the apparatus comprising: at least one processor, the at least one processor coupled to a memory and at least one transceiver, the at least one processor configured to implement any one of aspects 16 to 31.

[0138] Aspect 33 is an apparatus for wireless communication at a UE, the apparatus comprising: a component for implementing any one of aspects 16 to 31.

[0139] Aspect 34 is a computer-readable medium storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 16 to 31.

Claims

1. An apparatus for wireless communication at a network entity, the apparatus comprising: Memory; and at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor configured to: obtaining a capability indication of a user equipment (UE), the capability indication indicating that the UE is paired with a vehicle; generating a vehicle-specific signal based on the capability indication indicating pairing of the UE with the vehicle; as well as The vehicle specific signal is output to the UE.

2. The device according to claim 1, further comprising: A transceiver is coupled to the at least one processor, and wherein the at least one processor is configured to output the vehicle specific signal by initiating transmission of the vehicle specific signal via the transceiver.

3. The apparatus of claim 1, wherein the vehicle comprises an autonomous vehicle, and wherein the capability indication further indicates that an autonomous mode of the autonomous vehicle is activated or deactivated. 4 . The apparatus of claim 1 , wherein the data within the vehicle-specific signal is customized for a paired combination of the UE and the vehicle.

5. The apparatus of claim 4, wherein the vehicle comprises an autonomous vehicle and an autonomous mode of the autonomous vehicle is activated, and wherein the data corresponds to one or more other vehicles, one or more road users, one or more road conditions, one or more traffic conditions, one or more sensor fields of view, one or more depths, one or more ranges, or some combination thereof.

6. The device according to claim 4, wherein: i) in response to the vehicle comprising a non-autonomous vehicle, the data comprises at least information associated with a proximity of the non-autonomous vehicle for the UE to pair with the non-autonomous vehicle, or ii) in response to the vehicle comprising an autonomous vehicle, the data comprises at least information associated with a proximity of the autonomous vehicle for the UE paired with the autonomous vehicle for use by the autonomous vehicle when an autonomous mode of the autonomous vehicle is released.

7. The apparatus of claim 6, wherein the proximity of the non-autonomous vehicle for the UE to be paired with the non-autonomous vehicle or the proximity of the autonomous vehicle for the UE to be paired with the autonomous vehicle corresponds to a field of view of an operator of the vehicle.

8. The device according to claim 4, wherein: i) in response to said vehicle comprising a non-autonomous vehicle, said data within said vehicle-specific signal being based at least in part on an expected reaction time of an operator of said non-autonomous vehicle, or ii) in response to the vehicle comprising an autonomous vehicle, the data within the vehicle-specific signal is based at least in part on an expected data processing capability of the autonomous vehicle, an expected reaction time of an operator of the autonomous vehicle, or both.

9. The apparatus of claim 2, wherein the capability indication is included within a wireless communication received via the transceiver.

10. The apparatus of claim 9, wherein the transmission of the vehicle-specific signal comprises one or more application layer messages, one or more radio resource control (RRC) messages, or one or more physical layer messages.

11. The apparatus of claim 2, wherein the capability indication is included within a short-range wireless communication, wherein the vehicle-specific signal is included within at least one of an application layer message, a radio resource control (RRC) message, or a physical layer message.

12. The apparatus of claim 1, wherein the vehicle comprises an autonomous vehicle or a non-autonomous vehicle.

13. A method for wireless communication at a network entity, the method comprising: obtaining a capability indication of a user equipment (UE), the capability indication indicating that the UE is paired with a vehicle; generating a vehicle-specific signal based on the capability indication indicating pairing of the UE with the vehicle; as well as The vehicle specific signal is output to the UE.

14. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Memory; and at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor configured to: sending a capability indication of the UE to a network entity, the capability indication indicating that the UE is paired with a vehicle; and A vehicle-specific signal based on the capability indication indicating that the UE is paired with the vehicle is received from the network entity.

15. The device according to claim 14, further comprising: A transceiver is coupled to the at least one processor, and wherein the at least one processor is configured to receive the vehicle specific signal by initiating receipt of the vehicle specific signal via the transceiver.

16. The apparatus of claim 14, wherein the vehicle comprises an autonomous vehicle, and wherein the capability indication further indicates that an autonomous mode of the autonomous vehicle is activated or deactivated.

17. The apparatus of claim 14, wherein the data within the vehicle-specific signal is customized based on a paired combination of the UE and the vehicle.

18. The apparatus of claim 17, wherein the vehicle comprises an autonomous vehicle and an autonomous mode of the autonomous vehicle is activated, and wherein the data corresponds to one or more other vehicles, one or more road users, one or more road conditions, one or more traffic conditions, one or more fields of view of a sensor, one or more depths, one or more ranges, or some combination thereof.

19. The apparatus of claim 17, wherein: i) in response to the vehicle comprising a non-autonomous vehicle, the data comprises at least information associated with a proximity of the non-autonomous vehicle for the UE to pair with the non-autonomous vehicle, or ii) in response to the vehicle comprising an autonomous vehicle, the data comprising at least information associated with a proximity of the autonomous vehicle for the UE paired with the autonomous vehicle for use by the autonomous vehicle when an autonomous mode of the autonomous vehicle is released, Wherein the proximity of the non-autonomous vehicle for the UE to be paired with the non-autonomous vehicle or the proximity of the autonomous vehicle for the UE to be paired with the autonomous vehicle corresponds to a field of view of an operator of the vehicle.

20. The apparatus of claim 17, wherein: i) in response to said vehicle comprising a non-autonomous vehicle, said data within said vehicle-specific signal being based at least in part on an expected reaction time of an operator of said non-autonomous vehicle, or ii) in response to the vehicle comprising an autonomous vehicle, the data within the vehicle-specific signal is based at least in part on an expected data processing capability of the autonomous vehicle, an expected reaction time of an operator of the autonomous vehicle, or both.

21. The apparatus of claim 15, wherein the capability indication is included within a wireless communication sent via the transceiver.

22. The apparatus of claim 21, wherein the receiving of the vehicle-specific signal comprises one or more application layer messages, one or more radio resource control (RRC) messages, or one or more physical layer messages.

23. The apparatus of claim 15, wherein the capability indication is included within a short-range wireless communication, wherein the vehicle-specific signal is included within at least one of an application layer message, a radio resource control (RRC) message, or a physical layer message.

24. The apparatus of claim 14, wherein the vehicle comprises an autonomous vehicle or a non-autonomous vehicle.

25. The apparatus of claim 14, wherein the at least one processor is further configured to: A second vehicle-specific signal is sent to the one or more UEs via the sidelink communication.

26. The apparatus of claim 25, wherein each of the one or more UEs is paired with a corresponding autonomous vehicle or a corresponding non-autonomous vehicle.

27. The apparatus of claim 25, wherein the vehicle-specific signal sent to the one or more UEs is sent via broadcast, multicast, or unicast.

28. The apparatus of claim 25, wherein the second vehicle-specific signal is processed to correspond to vehicle capabilities of the one or more UEs based on the vehicle-specific signal received from the network entity.

29. The apparatus of claim 25, wherein the second vehicle-specific signal comprises the vehicle-specific signal received from the network entity.

30. A method of wireless communication at a user equipment (UE), the method comprising: sending a capability indication of the UE to a network entity, the capability indication indicating pairing of the UE with a vehicle; as well as A vehicle-specific signal based on the capability indication indicating that the UE is paired with the vehicle is received from the network entity.

Images