Driver-specified object tracking

Abstract

A first user equipment (UE) may obtain a command from a driver of a vehicle that includes an indication of a driver-specified direction (DSD). The first UE may adjust a priority of objects detected within a sensor area of a set of sensors based on the indication of the DSD. To adjust the direction of the set of sensors, the first UE may transmit a signal to a second UE that includes at least one of the indication of the DSD or a second indication of the sensor area. The first UE may transmit the signal using a V2X communication link with the second UE. The first UE may receive a set of sensor results associated with the sensor area from the second UE. The first UE may output a sensor report based on the received set of sensor results.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. non-provisional patent application serial number 18 / 151,129, entitled “DRIVER-SPECIFIED OBJECT TRACKING,” filed on January 6, 2023, 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 systems for sensing objects surrounding a vehicle. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasts. 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 continued mobile broadband evolution promulgated by the 3rd 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. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. These improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the Invention

[0006] The following presents a simplified summary of one or more aspects in order to provide a basic understanding of these aspects. This summary is not an extensive overview of all contemplated aspects. This summary does not identify key or critical elements of all aspects, nor does it delineate 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 the more detailed description that will be presented later.

[0007] In one aspect of the present disclosure, a method, computer-readable medium, and apparatus are provided. The apparatus may include user equipment (UE). The apparatus may obtain a command from a driver of a vehicle including an indication of a driver-specified direction (DSD). The apparatus may adjust the priority of objects detected within a sensor area of a sensor set based on the indication of the DSD.

[0008] To achieve the foregoing and related ends, one or more aspects may 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 illustrative features of one or more aspects. However, these features are indicative of only some of the various ways in which the principles of the various aspects may be employed. BRIEF DESCRIPTION OF THE DRAWINGS

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

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

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

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

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

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

[0015] Figure 4 is a diagram illustrating example aspects of a sidelink slot structure.

[0016] Figure 5 is a diagram illustrating example aspects of sidelink communications between devices in accordance with various aspects presented herein.

[0017] Figure 6 is a diagram illustrating an example of resource reservation for sidelink communication.

[0018] Figure 7 are diagrams illustrating example aspects of a UE having sensors that may be configured to sense objects surrounding the UE.

[0019] Figure 8Ais a diagram illustrating example aspects of a UE that obtains an indication of driver-specified directions (DSD) from a driver of a vehicle.

[0020] Figure 8B is a diagram illustrating example aspects of a UE monitoring objects within a sensor area.

[0021] Figure 9A is a diagram illustrating an example of a UE configured to indicate a sensor area.

[0022] Figure 9B is a diagram illustrating an example of a UE display configured to indicate a sensor area.

[0023] Figure 10 is a connection flow diagram of a UE configured to sense an object within a sensor area of multiple UEs.

[0024] Figure 11 is a flow chart of a method of wireless communication.

[0025] Figure 12 is another flow chart of a method of wireless communication.

[0026] Figure 13 is a flow chart of a method of wireless communication.

[0027] Figure 14 are diagrams illustrating examples of hardware implementations for example apparatuses and / or network entities. DETAILED DESCRIPTION

[0028] The detailed description set forth below in conjunction with the accompanying drawings is a description of various configurations and does not represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details to provide a thorough understanding of the various concepts. However, these concepts may 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.

[0029] Several aspects of telecommunication systems are presented with reference to various apparatuses and methods. These apparatuses 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 can be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0030] 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. The example of a processor includes a microprocessor, a microcontroller, a graphics processing unit (GPU), a central processing unit (CPU), an application processor, a digital signal processor (DSP), a reduced instruction set computing (RISC) processor, a system on a chip (SoC), a baseband processor, a field programmable gate array (FPGA), a programmable logic device (PLD), a state machine, a gated logic component, a discrete hardware circuit and other suitable hardware configured to perform various functionalities described throughout this 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 an instruction, an instruction set, a code, a code segment, a program code, a program, a subroutine, a software component, an application, a software application, a software package, a routine, a subroutine, an object, an executable file, a thread of execution, a process, a function or any combination thereof.

[0031] Thus, in one or more example aspects, specific implementations and / or use cases, the functionality described 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. A storage medium may be any available medium that can be accessed by a computer. For 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.

[0032] Although various aspects, specific implementations and / or use cases are described in this application by way of illustration of some examples, additional or different aspects, specific implementations and / or use cases may be produced in many different arrangements and scenarios. The various aspects, specific implementations and / or use cases described herein may be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, various aspects, specific implementations and / or use cases may be produced via integrated chip implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, 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 within the scope of chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the scope of aggregation, distribution or original equipment manufacturer (OEM) equipment or systems in conjunction with one or more technologies herein. In some actual settings, the equipment in conjunction 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 both 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, including chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, and the like.

[0033] The deployment of a communication system (such as a 5G NR system) can be arranged in a variety of ways with various components or parts. 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) that perform base station functions can be implemented in a converged 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) can be implemented as a converged base station (also known as a standalone BS or a monolithic BS) or a decomposed base station.

[0034] 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 across 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, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0035] 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 (a 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)). Disaggregation 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.

[0036] Figure 1 FIG1 is a diagram 100 illustrating an example of a wireless communication system and 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, which 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 the 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.

[0037] 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 transmit 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 transmit 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 transmit signals to one or more of the other units via a wireless transmission medium.

[0038] In some aspects, the 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 the CU 110. The 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, the 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, the CU 110 may be implemented to communicate with the DU 130 for network control and signaling.

[0039] The 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, the DU 130 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more higher physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) based at least in part on a functional split, such as those defined by 3GPP. In some aspects, the DU 130 may also host one or more lower PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU 130 or with control functions hosted by the CU 110.

[0040] Lower layer functionality may be implemented by one or more RUs 140. In some deployments, a RU 140 controlled by a DU 130 may correspond to a logical node that hosts RF processing functionality or low PHY layer functionality (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 a functional split, such as a lower layer functional split. In such an architecture, the RU 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 and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration may enable the DU 130 and CU 110 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

[0041] The SMO framework 105 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 105 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operations and maintenance interface (such as the O1 interface). For virtualized network elements, the SMO framework 105 can be configured to interact with a cloud computing platform (such as 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 the O2 interface). Such virtualized network elements may include, but are not limited to, the CU 110, DU 130, RU 140, and near-RT RIC 125. In some implementations, the SMO framework 105 can communicate with hardware aspects of the 4G RAN (such as the Open eNB (O-eNB) 111) via the O1 interface. Additionally, in some implementations, the SMO framework 105 can 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 .

[0042] The non-RT RIC 115 may be configured to include logic that enables 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 in communication with the near-RT RIC 125 (e.g., via an A1 interface). The near-RT RIC 125 may be configured to include logic that enables near-real-time control and optimization of RAN elements and resources through data collection and actions over an interface (e.g., 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.

[0043] In some implementations, to generate AI / ML models 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 non-network data sources or from network functions 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 in performance and employ AI / ML models to perform corrective actions through the SMO framework 105 (such as via reconfiguration of O1) or by creating RAN management policies (such as A1 policies).

[0044] At least one of the CU 110, DU 130, and RU 140 may be referred to as a base station 102. Thus, the base station 102 may include one or more of the CU 110, DU 130, and RU 140 (each component is indicated by a dotted line to indicate that each component may or may not be included in the base station 102). 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 that includes 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 called a closed subscriber group (CSG). The communication link between the RU 140 and the UE 104 may include uplink (UL) (also known as reverse link) transmissions from the UE 104 to the RU 140 and / or downlink (DL) (also known as forward link) transmissions from the RU 140 to the UE 104. The communication link may utilize multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link may be over one or more carriers. The base station 102 / UE 104 may utilize spectrum of up to Y MHz (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, etc.) bandwidth for each carrier allocated in a carrier aggregation for a total of up to Yx MHz (x component carriers) for transmission in each direction. 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). The component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

[0045] Some UEs 104 may communicate with each other using device-to-device (D2D) communication links 158. The D2D communication links 158 may use DL / UL wireless wide area network (WWAN) spectrum. The D2D communication links 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). D2D communication may be accomplished through various 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.

[0046] Some examples of sidelink communications may include vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I) (e.g., from a vehicle-based communication device to a road infrastructure node such as a roadside unit (RSU)), vehicle-to-network (V2N) (e.g., from a vehicle-based communication device to one or more network nodes such as a base station), vehicle-to-pedestrian (V2P), cellular vehicle-to-everything (C-V2X), and / or combinations thereof, and / or vehicle-based communication devices communicating with other devices, which may be collectively referred to as vehicle-to-everything (V2X) communications. Sidelink communications may be based on V2X or other D2D communications, such as proximity services (ProSe), etc. In addition to UEs, sidelink communications may also be sent and received by other transmitting and receiving devices, such as roadside units (RSUs) 107, etc. Sidelink communications may be exchanged using a PC5 interface, such as in conjunction with Figure 4 Although the examples in Figure 4 The following description of an example slot structure may provide examples for sidelink communications related to 5G NR, but the concepts described herein may be applicable to other similar areas such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0047] 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 the 5 GHz unlicensed spectrum. When communicating in the unlicensed spectrum, the UE 104 / AP 150 may perform a clear channel assessment (CCA) to determine whether the channel is available before communicating.

[0048] 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 (interchangeably) referred to 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 it is different from the extremely high frequency (EHF) band (30 GHz - 300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

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

[0050] With the above in mind, unless otherwise specified, if the term "sub-6 GHz" or the like 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. Furthermore, unless otherwise specified, if the term "millimeter wave" or the like 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.

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

[0052] The base station 102 may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit / receive point (TRP), a network node, a network entity, a network equipment, or some other suitable terminology. The base station 102 may be implemented as an integrated access and backhaul (IAB) node, a relay node, a sidelink node, a converged (monolithic) base station having a baseband unit (BBU) (including a CU and a DU) and a RU, or as a disaggregated base station including one or more of a CU, a DU, and / or a RU. A collection of base stations that may include disaggregated base stations and / or converged base stations may be referred to as a next generation (NG) RAN (NG-RAN).

[0053] 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. The AMF 161 is a control node that handles signaling between the UE 104 and the core network 120. The AMF 161 supports registration management, connection management, mobility management, and other functions. The SMF 162 supports session management and other functions. The UPF 163 supports packet routing, packet forwarding, and other functions. The UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identity handling, access authorization, and subscription management. The one or more location servers 168 are exemplified 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. The GMLC 165 and LMF 166 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. The LMF 166 receives measurements and assistance information from the NG-RAN and UE 104 via the AMF 161 to calculate the location of the UE 104. The NG-RAN may utilize one or more positioning methods to determine the location of the UE 104. Positioning the UE 104 may involve signal measurements, position estimates, and optionally velocity calculations based on these measurements. Signal measurements may be performed by the UE 104 and / or the base station 102 serving the UE 104. The measured signals may be based on one or more of 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 / location 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 other systems / signals / sensors.

[0054] Examples of UE 104 include cellular phones, smartphones, 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, tablets, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare devices, implants, sensors / actuators, displays, or any other similarly functional device. Some of UE 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart rate monitors, etc.). UE 104 may also be referred to as a station, mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology. In some scenarios, the term UE may also apply to one or more companion devices, such as in a device constellation arrangement. One or more of these devices may access the network collectively and / or individually.

[0055] Reference again Figure 1 In certain aspects, the UE 104 may have a DSD prioritization component 198 that may be configured to obtain driver specified directions (DSD) from a driver of a vehicle. The DSD prioritization component 198 may be configured to adjust the priority of objects detected within a sensor area of a sensor set based on an indication of DSD. Although the following description may focus on vehicle-to-everything (V2X) communications, the concepts described herein may be applicable to other similar areas, such as Internet of Things (IoT) communications. 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), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL, or may be time division duplex (TDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to both DL and UL. Figure 2A 、 Figure 2C In the example provided, the 5GNR 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 can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are all DL and all UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. The UE is configured with the slot format via the received slot format indicator (SFI) (dynamically configured via DL control information (DCI) or semi-statically / statically configured via radio resource control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0057] Figures 2A to 2D The frame structure is illustrated, and various aspects of the present disclosure are applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10ms) can be divided into 10 equally sized subframes (1ms). Each subframe may include one or more time slots. A subframe may also include a mini-time slot, which may include 7, 4, or 2 symbols. Each time slot may include 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 symbols on the DL may be CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbols. The symbols on the UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (for power-limited scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and the parameter set. The parameter set defines the subcarrier spacing (SCS) (see Table 1). Symbol length / duration can be scaled with 1 / SCS.

[0058]

[0059] Table 1: Parameter set, SCS and CP

[0060] 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 μ time slots / 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. Symbol length / duration is inversely related to subcarrier spacing. Figures 2A to 2D An example is provided for a normal CP with 14 symbols per slot and a parameter set μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 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).

[0061] A resource grid can be used to represent the frame structure. Each slot includes a resource block (RB) (also known as a physical RB (PRB)) that extends over 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0062] like Figure 2A As illustrated, some of the REs carry reference (pilot) signals (RS) for the UE. The RSs may include a demodulation RS (DM-RS) (indicated as R for a 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 RSs may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).

[0063] Figure 2BExamples of various DL channels within a subframe of a frame are illustrated. The 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 comprising six RE groups (REGs), each REG comprising 12 consecutive REs within an OFDM symbol of a RB. The PDCCH within a BWP may be referred to as a control resource set (CORESET). During a PDCCH monitoring opportunity on the 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), where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies across the channel bandwidth. The primary synchronization signal (PSS) may be within symbol 2 of a specific subframe of the frame. The PSS is used by the UE 104 to determine subframe / symbol timing and physical layer identity. The secondary synchronization signal (SSS) may be within symbol 4 of a specific subframe of the frame. The SSS is used by the UE to determine the physical layer cell identity group number and 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 known 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.

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

[0065] 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 a scheduling request, a channel quality indicator (CQI), a precoding matrix indicator (PMI), a rank indicator (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.

[0066] Figure 3 3 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 (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (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 transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0067] 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 transport channels, forward error correction (FEC) coding / decoding of transport channels, interleaving, rate matching, mapping onto physical channels, modulation / demodulation of physical channels, and MIMO antenna processing. The Tx processor 316 handles the mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK), quadrature phase-shift keying (QPSK), M-phase-shift keying (M-PSK), and M-quadrature amplitude modulation (M-QAM)). The coded and modulated symbols are then separated into parallel streams. Each stream is then mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then combined 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. The channel estimates may be derived from a reference signal and / or channel condition feedback transmitted 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 using a corresponding spatial stream for transmission.

[0068] At the UE 350, each receiver 354Rx receives a signal via 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 streams 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, as well as the reference signal, are recovered and demodulated by determining the most likely signal constellation point transmitted 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 a controller / processor 359, which implements layer 3 and layer 2 functionality.

[0069] 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 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 an ACK and / or NACK protocol to support HARQ operations.

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

[0071] The channel estimates derived by the channel estimator 358 from a reference signal or feedback sent by the base station 310 can 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 can be provided to different antennas 352 via separate transmitters 354Tx. Each transmitter 354Tx can modulate an RF carrier with a corresponding spatial stream for transmission.

[0072] 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 corresponding antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to an Rx processor 370.

[0073] 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 and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets. The controller / processor 375 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.

[0074] At least one of the Tx processor 368, the Rx processor 356, and the controller / processor 359 may be configured to perform Figure 1 Various aspects related to the DSD prioritization component 198.

[0075] Figure 4 Included are diagrams 400 and 410 illustrating example aspects of a slot structure that may be used for sidelink communications (e.g., between UE 104, RSU 107, etc.). In some examples, the slot structure may be within a 5G / NR frame structure. In other examples, the slot structure may be within an LTE frame structure. While 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. Figure 4 The example slot structure in FIG4 is only an example, and other sidelink communications may have different frame structures and / or different channels for sidelink communications. A frame (10 ms) may be divided into 10 equally sized subframes (1 ms). Each subframe may include one or more slots. A subframe may also include a mini-slot, which may include 7, 4, or 2 symbols. Each slot may include 7 or 14 symbols, depending on the slot configuration. For slot configuration 0, each slot may include 14 symbols, and for slot configuration 1, each slot may include 7 symbols. Diagram 400 illustrates a single resource block, which may correspond to a single slot transmission of, for example, a 0.5 ms transmit time interval (TTI). The physical sidelink control channel may be configured to occupy multiple physical resource blocks (PRBs), for example, 10, 12, 15, 20, or 25 PRBs. The PSCCH may be restricted to a single subchannel. The PSCCH duration may be configured to be, for example, 2 symbols or 3 symbols. A subchannel may include, for example, 10, 15, 20, 25, 50, 75, or 100 PRBs. Resources for sidelink transmissions may be selected from a resource pool comprising one or more subchannels. As a non-limiting example, a resource pool may include between 1 and 27 subchannels. A PSCCH size may be established for the resource pool, for example, to be between 10% and 100% of a subchannel within a duration of 2 or 3 symbols. Figure 4 Diagram 410 in Figure 4 illustrates an example in which the PSCCH occupies approximately 50% of a subchannel, as an example to illustrate the concept of the PSCCH occupying a portion of a subchannel. The physical sidelink shared channel (PSSCH) occupies at least one subchannel. In some examples, the PSCCH may include a first portion of sidelink control information (SCI), and the PSSCH may include a second portion of the SCI.

[0076] A resource grid may be used to represent the frame structure. Each time slot may include a resource block (RB) (also known 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. Figure 4 As illustrated, some of the REs may include control information in the PSCCH and some may include a demodulation RS (DMRS).At least one symbol may be used for feedback. Figure 4 An example is illustrated with two symbols for a physical sidelink feedback channel (PSFCH) with adjacent gap symbols. Symbols before and / or after the feedback can be used to transition between reception of data and transmission of feedback. The gap enables the device to switch from operating as a transmitting device to preparing to operate as a receiving device, for example, in a subsequent time slot. As illustrated in the figure, data can be sent in the remaining REs. The data can include data messages as described herein. The location of any of the data, DMRS, SCI, feedback, gap symbols, and / or LBT symbols can be different from Figure 4 Illustrated example. In some aspects, multiple time slots can be aggregated together.

[0077] Figure 5 Diagram 500 illustrates side link communication between devices. The communication may be based on a combination of Figure 5The timeslot structure of the various aspects described. For example, UE 502 may send a sidelink transmission 514, for example, including a control channel (e.g., PSCCH) and / or a corresponding data channel (e.g., PSSCH), which may be received by UEs 504, 506, and 508. The control channel may include information for decoding the data channel (e.g., sidelink control information (SCI)), which includes reservation information, such as information about time and / or frequency resources reserved for data channel transmission. For example, the SCI may indicate the TTI and the number of RBs to be occupied by the data transmission. The SCI may also be used by the receiving device to avoid interference by avoiding transmission on reserved resources. In addition to sidelink reception, UEs 502, 504, 506, and 508 may each be capable of sidelink transmission. Therefore, UEs 504, 506, and 508 are illustrated as sending sidelink transmissions 513, 515, 516, and 520. The sidelink transmissions 513, 514, 515, 516, 520 may be unicast, broadcast, or multicast to nearby devices. For example, UE 504 may transmit sidelink transmissions 513, 515 intended for reception by other UEs within range 501 of UE 504, and UE 506 may transmit sidelink transmission 516. Additionally or alternatively, RSU 507 may receive communications from and / or transmit communications 518 to UEs 502, 504, 506, 508. One or more of UEs 502, 504, 506, 508 or RSU 507 may include, for example, a combination of Figure 1 The DSD prioritization component 198 is described.

[0078] Sidelink communication may be based on resource allocation mechanisms of different types or modes. In a first resource allocation mode (which may be referred to herein as "mode 1"), centralized resource allocation may be provided by a network entity. For example, the base station 102 may determine the resources used for sidelink communication and may allocate resources to different UEs 104 for sidelink transmission. In this first mode, the UE receives sidelink resource allocation from the base station 102. In a second resource allocation mode (which may be referred to herein as "mode 2"), distributed resource allocation may be provided. In mode 2, each UE may autonomously determine the resources used for sidelink transmission. In order to coordinate the selection of sidelink resources by each UE, each UE may use sensing technology to monitor the resource reservations of other sidelink UEs and may select resources for sidelink transmission from unreserved resources. A device communicating based on the sidelink may determine one or more radio resources used by other devices in the time domain and frequency domain in order to select transmission resources that avoid conflicts with other devices.

[0079] Sidelink transmissions and / or resource reservations may be periodic or aperiodic, where the UE may reserve resources for transmission in the current slot and up to two future slots (as discussed below).

[0080] Thus, in this second mode (e.g., Mode 2), each UE may autonomously select resources for sidelink transmission, e.g., without a central entity (such as a base station) indicating resources for the device. A first UE may reserve the selected resources to inform other UEs about the resources that the first UE intends to use for sidelink transmission.

[0081] In some examples, resource selection for sidelink communication can be based on a sensing mechanism. For example, before selecting resources for data transmission, the UE can first determine whether the resources have been reserved by other UEs.

[0082] For example, as part of the listening mechanism for resource allocation mode 2, the UE may determine (e.g., listen) whether the selected side link resource has been reserved by other UEs before selecting the side link resource for data transmission. If the UE determines that the side link resource has not been reserved by other UEs, the UE may use the selected side link resource for transmitting data, for example, in a PSSCH transmission. The UE may estimate or determine which radio resources (e.g., side link resources) may be in use and / or reserved by other UEs by detecting and decoding side link control information (SCI) sent by other UEs. The UE may use a sensing-based resource selection algorithm to estimate or determine which radio resources are in use and / or reserved by other UEs. The UE may receive an SCI from another UE, the SCI including reservation information based on a resource reservation field included in the SCI. The UE may continuously monitor (e.g., listen) and decode the SCI from the peer UE. The SCI may include reservation information, for example, indicating the time slots and RBs that a particular UE has selected for future transmission. The UE may exclude resources used and / or reserved by other UEs from the set of candidate resources used by the UE for sidelink transmission, and the UE may select / reserve resources for sidelink transmission from resources that are not used and therefore form the candidate resource set. The UE may continuously perform sensing on the SCI with resource reservations in order to maintain a set of candidate resources from which the UE may select one or more resources for sidelink transmission. Once the UE selects a candidate resource, the UE may send an SCI indicating its own reservation of resources for sidelink transmission. The number of resources reserved by the UE (e.g., subchannels per subframe) may depend on the size of the data to be sent by the UE. Although this example is described with respect to a UE receiving reservation information from another UE, the reservation information may also be received from an RSU or other device communicating based on a sidelink.

[0083] Figure 6 600 is an example showing reserved time resources and frequency resources for sidelink transmission. For example, the resources may be included in a sidelink resource pool. Resource allocation for each UE may be in units of one or more subchannels (e.g., subchannels SC 1 to SC 4) in the frequency domain and may be based on a time slot in the time domain. The UE may also use resources in the current time slot to perform an initial transmission and may reserve resources in future time slots for retransmission. In this example, UE1 and UE2 are reserving two different future time slots for retransmission. Resource reservation may be limited to a window of predefined time slots and subchannels, such as a window of 8 time slots multiplied by 4 subchannels as shown in example 600, which provides a total of 32 available resource blocks. This window may also be referred to as a resource selection window.

[0084] A first UE ("UE1") may reserve a subchannel (e.g., SC 1) in a current time slot (e.g., time slot 1) for its initial data transmission 602, and may reserve additional future time slots within the window for data retransmissions (e.g., 604 and 606). For example, UE1 may reserve subchannel SC 3 at time slot 3 and subchannel SC 2 at time slot 4 for future retransmissions, as shown in FIG. Figure 4 UE1 then sends information about which resources are being used and / or reserved by it to other UEs. UE1 can do this by including the reservation information in the reserved resources field of the SCI (eg, the first stage SCI).

[0085] Figure 6 1 and 2. The example shows that the second UE ("UE2") reserves resources in subchannels SC 3 and SC 4 at time slot 1 for data transmission 608, and reserves resources in subchannels SC 3 and SC 4 at time slot 4 for data transmission 610, and reserves resources in subchannels SC 1 and SC 2 at time slot 7 for data transmission 612. Figure 6 Similarly, UE2 may send resource usage and reservation information to other UEs, such as by using the reserved resource field in the SCI.

[0086] The third UE may select resources for transmitting its data taking into account resources reserved by other UEs within the resource selection window. The third UE may first decode the SCI within a time period to identify which resources are available (e.g., candidate resources). For example, the third UE may exclude resources reserved by UE1 and UE2 and may select other available subchannels and time slots from the candidate resources for its transmission and retransmission, which may be based on the number of adjacent subchannels into which the data to be transmitted (e.g., packet) can fit.

[0087] Although Figure 6It is illustrated that resources are reserved for initial transmission and two retransmissions, but the reservation may be used for initial transmission and a single transmission or only for initial transmission.

[0088] The UE may determine an associated signal measurement (such as RSRP) for each resource reservation received by another UE. The UE may consider the reserved resources available for use by the UE in transmissions for which the UE measures an RSRP below a threshold. The UE may perform signal / channel measurements on sidelink resources already reserved and / or used by other UEs, such as by measuring the RSRP of a message reserving sidelink resources (e.g., SCI). Based at least in part on the signal / channel measurements, the UE may consider using / reusing sidelink resources already reserved by other UEs. For example, if the measured RSRP reaches or exceeds a threshold, the UE may exclude the reserved resources from a candidate resource set, and if the measured RSRP of the message reserving the resources is below a threshold, the UE may consider the reserved resources available. When the message reserving resources has an RSRP below a threshold, the UE may include these resources in the candidate resource set and may use / reuse such reserved resources because the low RSRP indicates that the other UE is far away and reusing these resources is unlikely to cause interference to the UE. A higher RSRP indicates that the transmitting UE for which the resources were reserved is potentially closer to the UE, and if the UE selects the same resources, the transmitting UE may experience a higher level of interference.

[0089] For example, in a first step, the UE may determine a set of candidate resources (e.g., by monitoring SCIs from other UEs and removing from the set of candidate resources resources reserved by other UEs in signals for which the UE measures an RSRP above a threshold). In a second step, the UE may select N resources for transmission and / or retransmission of a TB. For example, the UE may randomly select N resources from the set of candidate resources determined in the first step. In a third step, for each transmission, the UE may reserve future time and frequency resources for the initial transmission and up to two retransmissions. The UE may reserve resources by sending an SCI indicating resource reservation. For example, in Figure 6 In the example of , the UE may send an SCI that reserves resources for data transmission 608 , 610 , and 612 .

[0090] Figure 7FIG700 is a diagram illustrating an example of a set of UEs (such as UEs 702, 704, and 706) configured to detect one or more of a set of objects (such as objects 710, 712, and 714). The UEs may be configured to communicate with each other via a D2D communication link (such as a sidelink or V2X). UEs 702, 704, and 706 may have a sensor set that can be used to sense objects outside a vehicle. UEs 702, 704, and 706 may have a sensor set that can be used to sense a driver inside a vehicle. The sensor set may include at least one of a light detection and ranging (LIDAR) sensor, a radio detection and ranging (RADAR) sensor, a sound navigation and ranging (SONAR) sensor, a thermal sensor, a microphone, or a camera. The sensor set of the UE may be configured to detect objects within a detection zone surrounding the UE. For example, UE 702 may have a detection zone within a detection direction 703, within which UE 702 may detect objects (such as object 710, object 712, or object 714). UE 704 may have a detection area within detection direction 705, within which UE 704 may detect an object (such as object 710, object 712, or object 714). UE 706 may have a detection area within detection direction 707, within which UE 706 may detect an object (such as object 710, object 712, or object 714).

[0091] The RSU 708 can coordinate communications between the UEs 702, 704, and 706. In one aspect, the UE 702 can communicate with the RSU 708 to determine UEs located around the UE 702. In another aspect, the UE 702 can communicate with the RSU 708 to request that the UE set detect an object within the sensor area. In another aspect, the UE 702 can communicate with the RSU 708 and can allow the RSU 708 to coordinate the UEs 702, 704, and 706 to detect an object within the sensor area.

[0092] Although diagram 700 shows UEs 702, 704, and 706 with detection directions 703, 705, and 707, respectively, each of the UEs may have more or fewer directions in which the sensor set can detect objects around the vehicle. More or fewer UEs may be configured to coordinate with each other to sense objects within one or more sensor areas.

[0093] Although the UE may be configured to detect one or more objects around the UE using a set of sensors, the UE may not prioritize objects in one portion of the detection area relative to objects in another portion of the detection area. For example, the UE 702 may be configured to detect objects within the detection area of the detection direction 703, but may not be configured to adjust the priority of objects detected within the sensor area of the detection area of the detection direction 703. In some aspects, the UE may be configured to adjust the priority of objects detected within the sensor area based on an indication of a driver specified direction (DSD).

[0094] The UE may obtain a command including an indication of DSD from the driver of the vehicle.The UE may then adjust the priority of objects detected within the sensor area of the sensor set based on the indication of DSD.

[0095] Figure 8AFIG800 illustrates an example aspect of a UE 802 configured to obtain an indication of a DSD 805 from a driver 804. The DSD 805 may be obtained via a wired or wireless connection. A driver monitoring system (DMS) may monitor the actions of the driver 804 to receive an indication of the DSD 805 from the driver 804. In one aspect, the DSD 805 may be obtained via a microphone sensor that receives a verbal command from the driver 804, such as the command, "OK, car, tell me if there are any bikes on the right." Receipt of the first two words, "OK, car," may trigger a processor to analyze the remainder of the audio message for the command. The utterance "tell me" may trigger the processor to respond with an audio response. The utterance "are there any bikes?" may narrow the object the processor is searching for to objects associated with bike sharing, and "on the right" may narrow the sensor area for the object to be searched for to an area designated by the system as "right," such as the area to the driver's right of the vehicle or the rightmost half of the vehicle's sensor range. The system can semantically interpret commands from a driver 804 associated with UE 802 in a variety of ways (such as spoken or typed commands). On the other hand, UE 802 may detect multiple objects in a detection direction 803. UE 802 may indicate the objects to driver 804 in any suitable manner, such as by displaying a video of the objects in detection direction 803 on a screen, or by highlighting an area of a head-up display (HUD) of a vehicle associated with UE 802. Driver 804 may enter the command "Monitor for objects between the house and the truck." Receiving the word "monitor" may trigger the processor to prioritize tracking objects within the indicated area and not track objects outside the indicated area. Receiving the word "object" may trigger the processor to analyze any identifiable objects within the indicated area, as opposed to analyzing objects associated with a bicycle fingerprint or a truck fingerprint. Receiving the phrase "between the house and the truck" may indicate that DSD 805 is bounded by the house object and any truck objects detected in any detection area in detection direction 803. On the other hand, the driver 804 may input a command “monitor the road between the house and the truck,” thereby triggering the UE 802 to monitor the object defined by the detected road object between the detected house object and the detected truck object. The UE 802 may be configured to identify objects within the sensor based on one or more object fingerprints associated with different types of objects used to describe DSD (such as buildings, garbage bins / hoppers, trees, or road edges) and different types of objects to be monitored (such as bicycles, cars, or trucks).

[0096] In one aspect, DSD 805 may be obtained via a camera sensor that may receive a gesture from driver 804, such as a gesture toward a portion of the car. The gesture may be, for example, a wave, a pointing gesture, or a tap. In one aspect, DSD 805 may be obtained via a camera, LIDAR, SONAR, or thermal sensor that detects the driver's 804 eye gaze or head orientation. In some aspects, a first sensor may detect the driver's 804 head orientation, and a second sensor may detect the driver's 804 eye gaze. UE 802 may first determine a first zone of the detection area based on the driver's 804 head orientation, and then determine sub-zones within the first zone based on the driver's 804 eye gaze.

[0097] UE 802 may have a detection direction 803 indicating an area around UE 802 that a sensor set of UE 802 may monitor around UE 802. UE 802 may use DSD 805 to select a sensor area 806 in detection direction 803. Sensor area 806 may correspond to a detection sub-direction 801 within detection direction 803. UE 802 may adjust the priority of objects detected within sensor area 806 based on DSD 805. For example, UE 802 may increase or decrease the priority of objects detected within detection sub-direction 801 of detection direction 803 based on sensor area 806. In some aspects, UE 802 may receive an indication of sensor area 806 based on DSD 805, and UE 802 may monitor sensor area 806 selected by driver 804 via the sensor set of UE 802. In some aspects, the UE 802 may receive an indication of a sensor area 806 based on the DSD 805, and the UE 802 may select an area that is larger than the sensor area 806, such as a modified sensor area 808. For example, the driver 804 of the UE 802 may indicate a sensor area 806 for monitoring, and the UE 802 may select a modified sensor area 808 for monitoring that is larger than the sensor area 806 selected by the driver 804 of the UE 802 by a factor (e.g., 10% larger, or 2 feet larger on each side) and may be centered on the sensor area 806 selected by the driver 804. The UE 802 may monitor the modified sensor area 806 using the set of sensors of the UE 802 based on the sensor area 808 indicated by the driver 804.

[0098] In some aspects, changing the priority of objects detected in a sub-direction or a designated sensor area can eliminate or isolate the area for monitoring. In one aspect, UE 802 can set the default priority of the object to be monitored in an area (such as all areas detected on detection direction 803) to zero. In response to driver 804 indicating DSD 805, UE 802 can increase the priority of the object to be monitored in all areas detected on detection sub-direction 801 to one. Except for the area on detection sub-direction 801 of the sensor set of UE 802, this can exclude all areas in detection direction 803 from being monitored. On the other hand, UE 802 can set the default priority of the object to be monitored in an area (such as all areas detected on detection direction 803) to one. In response to driver 804 indicating DSD 805, UE 802 can reduce the priority of the object to be monitored in all areas detected on detection sub-direction 801 to zero. This can exclude all areas in detection sub-direction 801 from being monitored in detection direction 803.

[0099] In some aspects, UE 802 may communicate with other UEs such as Figure 7 806) to detect and monitor objects within the sensor area 806 via the sensor set of the UE 802. In some aspects, the UE 802 may detect and monitor a portion of the sensor area 806, and other UEs communicating with the UE 802 may detect and monitor other non-overlapping portions of the sensor area 806. In other aspects, the UE 802 and other UEs (such as Figure 7 UE 702, 704 or 706 in can be configured to monitor overlapping portions of sensor area 806.

[0100] Figure 8BFIG850 is a diagram illustrating example aspects of a UE 802 configured to monitor for objects within a sensor area 806 or a modified sensor area 808 (“monitored sensor area”). In one aspect, the UE 802 may prioritize objects detected within the monitored sensor area based on the DSD 805. The UE 802 may detect the object 852 and report it to the driver 804, for example, via a speaker (e.g., the UE 802 may play a recording indicating that it detected a bicycle within the monitored sensor area) or via a display (e.g., the UE 802 may indicate the monitored sensor area in a display on the dashboard or a heads-up display (HUD) projected onto the car windshield and may highlight the object 852 within the monitored sensor area). The UE 802 may monitor the object 852 and report to the driver 804 when the state of the object 852 changes (e.g., if the speed of the object 852 changes, if the object 852 disappears from the monitored sensor area, or if a new object blocks a portion of the object 852 from view by the UE 802).

[0101] In some aspects, UE 802 may monitor object 852 in response to receiving a command from driver 804. UE 802 may monitor object 852 in conjunction with a collection of other UEs such as Figure 7 852 within the monitored sensor area. For example, in one aspect, the UE 802 may receive an audio command from a microphone sensor that records the sentence "OK, car, tell me if the bike starts moving." Receipt of the first two words, "OK, car," may trigger the processor to analyze the rest of the audio message for the command, the utterance "tell me" may trigger the processor to respond with an audio response, the utterance "if bike" may narrow the object the processor is looking for to objects associated with bike sharing, and the utterance "starts moving" may narrow the type of object state change to movement from a stationary state to a moving state.

[0102] In some aspects, UE 802 may detect multiple bicycles within the monitored sensor area. In response, UE 802 may prompt UE 802 for clarification. For example, UE 802 may transmit an audio signal to a speaker of UE 802 indicating the presence of multiple bicycles within sensor area 806, and may prompt driver 804 to select one of the multiple bicycles within the sensor area relative to driver 804 for monitoring. In response, driver 804 may output an indication of selection of one of the multiple bicycles, such as via an audio command such as "select the leftmost bicycle" received via a microphone sensor, via a typed command such as "select the largest bicycle" received via a keyboard, or via a touchscreen displaying an image of the monitored sensor area, indicating a representation of the bicycle to be monitored. The UE 802 may indicate in its query to the driver 804 the differences between the multiple objects monitored in the monitored sensor area, such as differences in position (e.g., left bicycle, middle bicycle, right bicycle), size (e.g., large bicycle, normal bicycle, small bicycle), or color (red bicycle, yellow bicycle, orange bicycle), which the driver 804 may use to select one of the objects in the monitored sensor area.

[0103] In some aspects, the UE 802 may fail to detect the object indicated by the driver 804 of the UE 802. For example, the driver 804 of the UE 802 may instruct the UE 802 to monitor the sensor area 806 for bicycles, and the UE 802 may fail to detect the bicycle in the monitored sensor area, for example, if there are no bicycles in the area, if an obstructing object is placed between the sensor set of the UE 802 and the object 852, or if data from the sensor set of the UE 802 may be corrupted. The UE 802 may indicate to the driver 804 of the UE 802 that the UE 802 was unable to detect the indicated object. In response, the driver 804 of the UE 802 may repeat the same instruction, or may provide alternative instructions that allow the UE 802 to detect the object (e.g., by indicating a smaller sensor area to monitor, or by providing a more accurate description of the object to be monitored).

[0104] Figure 9A9 is a diagram illustrating an example of a UE 902 configured to indicate a sensor area 906 to a driver 904 of the UE 902. For example, the UE 902 may receive an indication from the driver 904 to monitor the sensor area 906. The UE 902 may have multiple headlights that illuminate various areas around the UE 902, such as area 912, area 914, and area 916. In response to the UE 902 receiving an indication from the driver 904 to monitor the sensor area 906, the UE 902 may illuminate area 916 and may not illuminate area 912 or area 914, thereby indicating to the driver 904 that it will monitor the area illuminated by area 916.

[0105] The UE 902 may indicate to the driver 904 that it is seeking confirmation of the selection of the sensor area 906, for example, by playing a prompt message “Please confirm whether the illuminated area should be monitored” through the speaker of the UE 902. The UE 902 may then receive a signal from the driver 904, such as an audio signal “Confirm” for a confirmed area and “Not Confirmed” for an unconfirmed area, or a tactile signal that the driver 904 has pressed an “OK” button for a confirmed area and a “Cancel” button for an unconfirmed area.

[0106] Figure 9B 950 is a diagram illustrating an example of a UE 902 having a display 952 that can be used to display detection zones within the display 952. The display 952 can be a visual representation of the detection zone of the UE 902, such as a display of an optical camera or infrared camera that the UE 902 may have, of the zone surrounding the UE 902. The display 952 can indicate multiple objects, such as an object 956 and an object 958 surrounding the UE 902. The UE 902 can highlight a zone 954 of the display 952 to indicate to the driver 904 that the highlighted representation of the zone 954 has been selected as the zone to be monitored by the UE 902 and that the UE 902 desires confirmation as to whether to adjust the priority of objects within the representation of the zone 954. In response, the UE 902 can adjust the priority of the object 958 relative to the object 956, for example, by increasing or decreasing the priority of the change in state of the object 958 relative to the object 956.

[0107] Figure 10 1000 is a connection flow diagram of a UE 1002 configured to sense objects within a sensor area by cooperating with a collection of UEs 1004 .

[0108] At 1006, UE 1002 may obtain an indication of a DSD from the driver of the vehicle associated with UE 1002. For example, UE 1002 may use a DMS to monitor the driver of the vehicle associated with UE 1002. The DMS may obtain a command including an indication of a DSD from the driver of the vehicle associated with UE 1002. UE 1002 may fuse one or more inputs from the driver of the vehicle associated with UE 1002. For example, UE 1002 may fuse the driver's keywords, head direction, and / or gaze direction to infer the DSD and / or objects to be analyzed with respect to UE 1002. In some aspects, UE 1002 may fuse one or more inputs from the driver of the vehicle associated with UE 1002 with one or more inputs from a sensor set of the vehicle associated with UE 1002, such as fusing a selection of the leftmost bicycle with input from a sensor set that monitors a set of bicycles in a row from left to right from the perspective of the driver of the vehicle.

[0109] At 1008, the UE 1002 may determine a prioritized sensor area based on the DSD received from the driver of the vehicle associated with the UE 1002. The prioritized sensor area may be used to select a sub-area of the detection area of the sensor set of the UE 1002. In some aspects, the UE 1002 may confirm the prioritized sensor area with the driver, for example, by turning on a dedicated light surrounding the UE 1002 or by highlighting an area of a display of the UE 1002.

[0110] At 1010, the UE 1002 may adjust the priority of objects within the sensor area based on the prioritized sensor area. The UE 1002 may increase the priority of objects within the sensor area, or may decrease the priority of objects within the sensor area, or may select to monitor a change in state of objects within or outside the sensor area based on a command associated with an indication of DSD from a driver of a vehicle associated with the UE 1002.

[0111] UE 1002 may send an indication of a DSD or sensor area 1012 to a set of UEs 1004. The set of UEs 1004 may be a set of UEs 1004 that may have sensors capable of monitoring the sensor area indicated by the DSD of the driver of the vehicle associated with UE 1002.

[0112] At 1014, the set of UEs 1004 may determine prioritized sensor areas based on the indication of the DSD or sensor area 1012. The prioritized sensor areas determined by the set of UEs 1004 may be the same as or different from the prioritized sensor areas determined by UE 1002 at 1008, as the detection area of the set of UEs 1004 may be different from the detection area of UE 1002.

[0113] At 1016, the set of UEs 1004 may adjust the priority of objects within the sensor area based on the prioritized sensor area, similar to UE 1002 at 1010. The set of UEs 1004 may send the set of sensor results 1018 to UE 1002. UE 1002 may receive the set of sensor results 1018 from the set of UEs 1004.

[0114] At 1020, UE 1002 may generate a sensor report based on the set of sensor results 1018 and the prioritized sensor areas determined at 1008. For example, UE 1002 may determine the total coverage area of the sensor areas based on an indication of DSD from a driver of a vehicle associated with UE 1002 and the set of sensor results 1018. UE 1002 may then determine what type of condition to monitor for each of UE 1002 and the set of UEs 1004 based on the generated sensor reports. UE 1002 may send an indication 1022 of a sensor report set to the set of UEs 1004. The set of UEs 1004 may receive the indication 1022 of a sensor report set.

[0115] At 1024, UE 1002 may monitor objects within the prioritized sensor area based on the priority of the objects within the sensor area adjusted at 1010 or based on the sensor report generated at 1020. At 1026, the set of UEs 1004 may monitor objects within the set of prioritized sensor areas based on the adjusted priority of the objects within the sensor area indicated by the indication of the DSD or sensor area 1012 or the indication of the set of sensor reports 1022. The prioritized sensor areas monitored by UE 1002 may be different from, the same as, or overlap with the set of prioritized sensor areas monitored by the set of UEs 1004. The set of UEs 1004 may send a set of sensor results 1028 to UE 1002. UE 1002 may receive the set of sensor results 1028.

[0116] The UE 1002 may be configured to notify a driver associated with the UE 1002 based on the monitoring results at 1024 and based on the set of sensor results 1028 received from the set of UEs 1004. For example, the UE 1002 may notify the driver associated with the UE 1002 if a new object enters one of the prioritized sensor areas, if an object in one of the prioritized sensor areas is obstructed, or if the projected path of one of the objects in one of the prioritized sensor areas changes to a different projected path by a threshold amount (e.g., by more than half a meter, or by more than 10%).

[0117] Figure 11 1100 is a flow chart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104, UE 350, UE 502, UE 504, UE 506, UE 508, UE 702, UE 704, UE 706, UE 802, UE 902, UE 1002, UE 1004; RSU 107, RSU 507; device 1404). At 1102, the UE may obtain a command including an indication of DSD from a driver of a vehicle. For example, 1102 may be performed by Figure 10 The UE 1002 in the embodiment may obtain a command including an indication of DSD from the driver of the vehicle at 1006. In addition, 1102 may be performed by Figure 1 、 Figure 3 、 Figure 5 、 Figure 7 or Figure 14 Component 198 in is executed.

[0118] At 1104, the UE may adjust the priority of objects detected within the sensor area of the sensor set based on the indication of DSD. For example, 1104 may be performed by Figure 10 1002 in the UE, at 1010, the UE may adjust the priority of the objects detected in the sensor area of the sensor set based on the indication of DSD. In addition, 1104 may be performed by Figure 1 、 Figure 3 、 Figure 5 、 Figure 7 or Figure 14 Component 198 in is executed.

[0119] Figure 121200 is a flow chart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104, UE 350, UE 502, UE 504, UE 506, UE 508, UE 702, UE 704, UE 706, UE 802, UE 902, UE 1002, UE 1004; RSU 107, RSU 507; device 1404). At 1202, the UE may obtain a command including an indication of DSD from a driver of a vehicle. For example, 1202 may be performed by Figure 10 The UE 1002 in the embodiment may obtain a command including an indication of DSD from the driver of the vehicle at 1006. In addition, 1202 may be performed by Figure 1 、 Figure 3 、 Figure 5 、 Figure 7 or Figure 14 Component 198 in is executed.

[0120] At 1204, the UE may adjust the priority of objects detected within the sensor area of the sensor set based on the indication of DSD. For example, 1204 may be performed by Figure 10 1002 in the UE, at 1010, the UE may adjust the priority of the objects detected in the sensor area of the sensor set based on the indication of DSD. In addition, 1204 may be performed by Figure 1 、 Figure 3 、 Figure 5 、 Figure 7 or Figure 14 Component 198 in is executed.

[0121] At 1206, the UE may obtain a signal from the driver of the vehicle to monitor the sensor area. For example, 1206 may be performed by Figure 10 1002 in the embodiment, the UE may obtain a signal from the driver of the vehicle to monitor the sensor area at 1010. In addition, 1206 may be performed by Figure 1 、 Figure 3 、 Figure 5 、 Figure 7 or Figure 14 Component 198 in is executed.

[0122] At 1208, the UE may obtain an indication of DSD from the driver of the vehicle. For example, 1208 may be Figure 10 1002 in the embodiment, at 1010, the UE may obtain an indication of DSD from the driver of the vehicle. In addition, 1208 may be performed by Figure 1 、 Figure 3 、 Figure 5 、 Figure 7 or Figure 14 Component 198 in is executed.

[0123] At 1210, the UE may calculate the sensor area based on the indication of the DSD. For example, 1210 may be calculated by Figure 10 1002 in the UE, at 1010, the UE may calculate the sensor area based on the indication of DSD. In addition, 1210 may be performed by Figure 1 、 Figure 3 、 Figure 5 、 Figure 7 or Figure 14 Component 198 in is executed.

[0124] At 1212, the UE may obtain a signal via at least one of an audio user interface or a touch user interface. For example, 1212 may be performed by Figure 10 1002 in the UE, at 1010, the UE may obtain a signal via at least one of an audio user interface or a touch user interface. In addition, 1212 may be performed by Figure 1 、 Figure 3 、 Figure 5 、 Figure 7 or Figure 14 Component 198 in is executed.

[0125] At 1214, the UE may monitor the direction the driver's head is facing to identify the zone. For example, 1214 may be performed by Figure 10 In the UE 1002, at 1010, the UE can monitor the direction in which the driver's head is facing to identify the zone. In addition, 1214 can be performed by Figure 1 、 Figure 3 、 Figure 5 、 Figure 7 or Figure 14 Component 198 in is executed.

[0126] At 1216, the UE may monitor the gaze direction of the driver of the vehicle to identify the sensor area within the identified area. For example, 1216 may be performed by Figure 10 1002 in the UE, at 1010, the UE may monitor the gaze direction of the driver of the vehicle to identify the sensor area within the identified area. In addition, 1216 may be performed by Figure 1 、 Figure 3 、 Figure 5 、 Figure 7 or Figure 14 Component 198 in is executed.

[0127] At 1218, the UE may monitor the gaze direction of the driver of the vehicle. For example, 1218 may be performed by Figure 10 In the embodiment of the present invention, the UE 1002 may monitor the direction of the driver's gaze of the vehicle at 1010. In addition, 1218 may be performed by Figure 1 、 Figure 3 、 Figure 5 、 Figure 7 or Figure 14 Component 198 in is executed.

[0128] At 1220, the UE may monitor a gesture made by the driver of the vehicle. For example, 1220 may be performed by Figure 10 1002 in the embodiment, the UE may monitor a gesture made by a driver of a vehicle at 1010. In addition, 1220 may be performed by Figure 1 、 Figure 3 、 Figure 5 、 Figure 7 or Figure 14 Component 198 in is executed.

[0129] At 1222, the UE may record the audio sound emitted by the driver of the vehicle. For example, 1222 may be Figure 10 1002 in the UE, at 1010, the UE may record the audio sound emitted by the driver of the vehicle. In addition, 1222 may be performed by Figure 1 、 Figure 3 、 Figure 5 、 Figure 7 or Figure 14 Component 198 in is executed.

[0130] At 1224, the UE may send a signal including at least one of an indication of the DSD or a second indication of the sensor area to the second UE. For example, 1224 may be performed by Figure 10 The UE 1002 in the embodiment may perform, at 1010, the UE may send a signal including at least one of an indication of the DSD or a second indication of the sensor area to the second UE. In addition, 1224 may be performed by Figure 1 、 Figure 3 、 Figure 5 、 Figure 7 or Figure 14 Component 198 in is executed.

[0131] At 1226, the UE may receive a set of sensor results associated with the sensor area from the second UE. For example, 1226 may be performed by Figure 10 1002 in the UE, at 1010, the UE may receive a sensor result set associated with the sensor area from a second UE. In addition, 1226 may be performed by Figure 1 、 Figure 3 、 Figure 5 、 Figure 7 or Figure 14 Component 198 in is executed.

[0132] At 1228, the UE may output a sensor report based on the received sensor result set. For example, 1228 may be performed by Figure 10 1002 in the UE, at 1010, the UE may output a sensor report based on the received sensor result set. In addition, 1228 may be performed by Figure 1 、 Figure 3 、 Figure 5 、 Figure 7 or Figure 14 Component 198 in is executed.

[0133] At 1230, the UE may use a vehicle-to-everything (V2X) communication link with a second UE to send a signal. For example, 1230 may be performed by Figure 10 1002 in the embodiment, at 1010, the UE may use a vehicle-to-everything (V2X) communication link with a second UE to send a signal. In addition, 1230 may be performed by Figure 1 、 Figure 3 、 Figure 5 、 Figure 7 or Figure 14 Component 198 in is executed.

[0134] Figure 13 1300 is a flow chart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104, UE 350, UE 502, UE 504, UE 506, UE 508, UE 702, UE 704, UE 706, UE 802, UE 902, UE 1002, UE 1004; RSU 107, RSU 507; device 1404). At 1302, the UE may obtain a command including an indication of DSD from a driver of a vehicle. For example, 1302 may be performed by Figure 10 The UE 1002 in the embodiment may obtain a command including an indication of DSD from the driver of the vehicle at 1006. In addition, 1302 may be performed by Figure 1 、 Figure 3 、 Figure 5 、 Figure 7 or Figure 14 Component 198 in is executed.

[0135] At 1304, the UE may adjust the priority of objects detected within the sensor area of the sensor set based on the indication of DSD. For example, 1304 may be performed by Figure 10 1002 in the UE, at 1010, the UE may adjust the priority of the objects detected in the sensor area of the sensor set based on the indication of DSD. In addition, 1304 may be performed by Figure 1 、 Figure 3 、 Figure 5 、 Figure 7 or Figure 14 Component 198 in is executed.

[0136] At 1306, the UE may obtain sensor data from the set of sensors adjusted to the sensor area. For example, 1306 may be performed by Figure 10 1002 in the UE, at 1010, the UE may obtain sensor data from a set of sensors adjusted to the sensor area. In addition, 1306 may be performed by Figure 1 、 Figure 3 、 Figure 5 、 Figure 7 or Figure 14 Component 198 in is executed.

[0137] At 1308, the UE may establish a status of the sensor area based on the obtained sensor data. For example, 1308 may be performed by Figure 10 1002 in the UE, at 1010, the UE may establish a state of the sensor area based on the obtained sensor data. In addition, 1308 may be performed by Figure 1 、 Figure 3 、 Figure 5 、 Figure 7 or Figure 14 Component 198 in is executed.

[0138] At 1310, the UE may monitor the obtained sensor data within a certain period of time in response to receiving the command. For example, 1310 may be performed by Figure 10 1002 in the UE, at 1010, the UE may monitor the obtained sensor data within a certain period of time in response to receiving the command. In addition, 1310 may be performed by Figure 1 、 Figure 3 、 Figure 5 、 Figure 7 or Figure 14 Component 198 in is executed.

[0139] At 1312, the UE may notify the driver of the vehicle of a change from the established state based on the obtained sensor data. For example, 1312 may be performed by Figure 10 1002 in the UE, at 1010, the UE may notify the driver of the vehicle of the change from the established state based on the obtained sensor data. In addition, 1312 may be performed by Figure 1 、 Figure 3 、 Figure 5 、 Figure 7 or Figure 14 Component 198 in is executed.

[0140] At 1314, the UE may indicate the sensor area to the driver of the vehicle. For example, 1314 may be Figure 101002 in the embodiment, the UE may indicate the sensor area to the driver of the vehicle at 1010. In addition, 1314 may be performed by Figure 1 、 Figure 3 、 Figure 5 、 Figure 7 or Figure 14 Component 198 in is executed.

[0141] At 1316, the UE may obtain confirmation of the sensor area from the driver of the vehicle in response to the indication of the sensor area. For example, 1316 may be performed by Figure 10 The UE 1002 in the embodiment of the present invention may perform, at 1010, the UE may obtain confirmation of the sensor area from the driver of the vehicle in response to the indication of the sensor area. In addition, 1316 may be performed by Figure 1 、 Figure 3 、 Figure 5 、 Figure 7 or Figure 14 Component 198 in is executed.

[0142] At 1318, the UE may adjust the priority of objects detected within the sensor area of the sensor set in response to receiving confirmation of the sensor area from the driver of the vehicle. For example, 1318 may be performed by Figure 10 1002 in the UE, at 1010, the UE may adjust the priority of the objects detected in the sensor area of the sensor set in response to receiving confirmation of the sensor area from the driver of the vehicle. In addition, 1318 may be performed by Figure 1 、 Figure 3 、 Figure 5 、 Figure 7 or Figure 14 Component 198 in is executed.

[0143] At 1320, the UE may indicate the sensor area to the driver of the vehicle using the vehicle's HUD. For example, 1320 may be Figure 10 The UE 1002 in FIG. 1002 may execute the sensor area to the driver of the vehicle using the HUD of the vehicle at 1010. In addition, 1320 may be performed by Figure 1 、 Figure 3 、 Figure 5 、 Figure 7 or Figure 14 Component 198 in is executed.

[0144] At 1322, the UE may indicate the sensor area to the driver of the vehicle on a screen of the vehicle. For example, 1322 may be Figure 10 The UE 1002 in the embodiment of the present invention may indicate the sensor area to the driver of the vehicle on the screen of the vehicle at 1010. In addition, 1322 may be performed by Figure 1 、 Figure 3 、 Figure 5 、 Figure 7 or Figure 14 Component 198 in is executed.

[0145] At 1324, the UE may indicate the sensor area to the driver of the vehicle using lights that illuminate the exterior of the vehicle. For example, 1324 may be Figure 10 1002 in the embodiment, the UE may indicate the sensor area to the driver of the vehicle using a light that illuminates the exterior of the vehicle. Figure 1 、 Figure 3 、 Figure 5 、 Figure 7 or Figure 14 Component 198 in is executed.

[0146] At 1326, the UE may identify a set of objects within the sensor area. For example, 1326 may be performed by Figure 10 1002 in the UE, at 1010, the UE may identify a set of objects within the sensor area. In addition, 1326 may be performed by Figure 1 、 Figure 3 、 Figure 5 、 Figure 7 or Figure 14 Component 198 in is executed.

[0147] At 1328, the UE may calculate the path / speed of each of the set of objects within the sensor area at a first time during the time period. For example, 1328 may be performed by Figure 10 1002 in the UE, at 1010, the UE may calculate the path / speed of each of the set of objects within the sensor area at a first time during the time period. In addition, 1328 may be performed by Figure 1 、 Figure 3 、 Figure 5 、 Figure 7 or Figure 14 Component 198 in is executed.

[0148] At 1330, the UE may recalculate the path / speed of each of the set of objects within the sensor area at a second time during the time period. For example, 1330 may be performed by Figure 10 1002 in the UE, at 1010, the UE may recalculate the path / speed of each of the set of objects within the sensor area at a second time during the time period. In addition, 1330 may be performed by Figure 1 、 Figure 3 、 Figure 5 、 Figure 7 or Figure 14 Component 198 in is executed.

[0149] Figure 1414 is a diagram illustrating an example of a hardware implementation for an apparatus 1404. The apparatus 1404 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1404 may include a cellular baseband processor 1424 (also referred to as a modem) coupled to one or more transceivers 1422 (e.g., a cellular RF transceiver). The cellular baseband processor 1424 may include on-chip memory 1424′. In some aspects, the apparatus 1404 may also include one or more subscriber identity module (SIM) cards 1420 and an application processor 1406 coupled to a secure digital (SD) card 1408 and a screen 1410. The application processor 1406 may include on-chip memory 1406′. In some aspects, the device 1404 may also include a Bluetooth module 1412, a WLAN module 1414, an SPS module 1416 (e.g., a GNSS module), one or more sensor modules 1418 (e.g., a barometric pressure sensor / altimeter; a motion sensor such as an inertial measurement 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, an audio sensor, a microphone, a thermal sensor, a driver monitoring system (DMS), a motion sensor, a camera, an eye movement sensor, and / or other technologies for positioning), an additional memory module 1426, a power source 1430, and / or a camera 1432. The Bluetooth module 1412, the WLAN module 1414, and the SPS module 1416 may include an on-chip transceiver (TRX) (or, in some cases, only a receiver (Rx)). The Bluetooth module 1412, WLAN module 1414, and SPS module 1416 may include their own dedicated antennas and / or utilize antenna 1480 for communication. The cellular baseband processor 1424 communicates with the UE 104 and / or RUs associated with the network entity 1402 via one or more antennas 1480 through the transceiver 1422. The cellular baseband processor 1424 and the application processor 1406 may each include computer-readable media / memory 1424', 1406', respectively. The additional memory module 1426 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 1424', 1406', 1426 may be non-transitory. The cellular baseband processor 1424 and the application processor 1406 are each responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the cellular baseband processor 1424 / application processor 1406, the software enables the cellular baseband processor 1424 / application processor 1406 to perform the various functions described above. The computer-readable medium / memory may also be used to store data that is manipulated by the cellular baseband processor 1424 / applications processor 1406 when executing software.The cellular baseband processor 1424 / application processor 1406 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 1404 may be a processor chip (modem and / or application) and include only the cellular baseband processor 1424 and / or the application processor 1406, while in another configuration, the device 1404 may be the entire UE (e.g., see. Figure 3 UE 350) and includes additional modules of device 1404.

[0150] As discussed above, component 198 can be configured to obtain a Distance Detected (DSD) from the driver of the vehicle. Component 198 can be configured to adjust the priority of objects detected within the sensor area of the sensor set based on the indication of DSD. Component 198 can reside within cellular baseband processor 1424, application processor 1406, or both. Component 198 can be one or more hardware components specifically configured to perform the described processes / algorithms, implemented by one or more processors configured to perform the described processes / algorithms, stored on a computer-readable medium for implementation by one or more processors, or some combination thereof. As shown, device 1404 can include various components configured for various functions. In one configuration, device 1404 (and in particular cellular baseband processor 1424 and / or application processor 1406) can include components for obtaining a command including an indication of Distance Detected (DSD) from the driver of the vehicle. Device 1404 can include components for adjusting the priority of objects detected within the sensor area of the sensor set based on the indication of DSD. The sensor set may include at least one of a LIDAR sensor, a RADAR sensor, a SONAR sensor, a thermal sensor, a microphone, or a camera. Apparatus 1404 may include components for obtaining a command including an indication of DSD by monitoring a sensor area by obtaining a signal from the driver of the vehicle. Apparatus 1404 may include components for obtaining a command including an indication of DSD by obtaining an indication of DSD from the driver of the vehicle. Apparatus 1404 may include components for obtaining a command including an indication of DSD by calculating a sensor area based on the indication of DSD. Apparatus 1404 may include components for obtaining a signal from the driver of the vehicle by obtaining a signal via at least one of an audio user interface or a touch user interface. Apparatus 1404 may include components for obtaining an indication of DSD from the driver of the vehicle by monitoring the direction the driver's head is facing to identify a zone. Apparatus 1404 may include components for obtaining an indication of DSD from the driver of the vehicle by monitoring the direction the driver's head is facing to identify a sensor area within the identified zone. The apparatus 1404 may include means for obtaining an indication of DSD from the driver of the vehicle by monitoring the direction of the driver's gaze. The apparatus 1404 may include means for obtaining an indication of DSD from the driver of the vehicle by monitoring gestures made by the driver of the vehicle. The apparatus 1404 may include means for obtaining an indication of DSD from the driver of the vehicle by recording audio sounds emitted by the driver of the vehicle. The apparatus 1404 may include means for adjusting the orientation of the sensor set by sending a signal including at least one of an indication of DSD or a second indication of a sensor area to a second UE.Apparatus 1404 may include means for receiving a sensor result set associated with a sensor area from a second UE. Apparatus 1404 may include means for outputting a sensor report based on the received sensor result set. Apparatus 1404 may include means for transmitting a signal to the second UE by transmitting the signal using a V2X communication link with the second UE. Apparatus 1404 may include means for adjusting the priority of objects detected within a sensor area of the sensor set by indicating the sensor area to a driver of the vehicle. Apparatus 1404 may include means for adjusting the priority of objects detected within the sensor area of the sensor set by obtaining confirmation of the sensor area from the driver of the vehicle in response to the indication of the sensor area. Apparatus 1404 may include means for adjusting the priority of objects detected within the sensor area of the sensor set by adjusting the priority of objects detected within the sensor area of the sensor set in response to receiving confirmation of the sensor area from the driver of the vehicle. Apparatus 1404 may include means for indicating the sensor area to the driver of the vehicle using a head-up display (HUD) of the vehicle to indicate the sensor area to the driver of the vehicle. Device 1404 may include means for indicating the sensor area to the driver of the vehicle by indicating the sensor area to the driver of the vehicle on a screen of the vehicle. Device 1404 may also include means for indicating the sensor area to the driver of the vehicle by using lights that illuminate the exterior of the vehicle to indicate the sensor area to the driver of the vehicle. Device 1404 may include means for obtaining sensor data from a set of sensors tuned to the sensor area. Device 1404 may include means for establishing a state of the sensor area based on the obtained sensor data. Device 1404 may include means for monitoring the obtained sensor data over a certain period of time in response to receiving a command. Device 1404 may include means for notifying the driver of the vehicle of a change from the established state based on the obtained sensor data. The change in state may include a new object state in the sensor area associated with the established state. The change in state may include a new obstacle in the sensor area associated with the established state. The change in state may include an inability to sense a portion of the sensor area associated with the established state. Device 1404 may include means for monitoring the obtained sensor data over a certain period of time by identifying a set of objects within the sensor area. The apparatus 1404 may include means for monitoring the obtained sensor data during the time period by calculating a path for each of the set of objects within the sensor area at a first time during the time period. The apparatus 1404 may include means for monitoring the obtained sensor data during the time period by recalculating a path for each of the set of objects within the sensor area at a second time during the time period.The device 1404 may include components for monitoring acquired sensor data over a time period by identifying a set of objects within the sensor area. The device 1404 may include components for monitoring acquired sensor data over a time period by calculating a velocity of each of the set of objects within the sensor area at a first time during the time period. The device 1404 may include components for monitoring acquired sensor data over a time period by recalculating a velocity of each of the set of objects within the sensor area at a second time during the time period. This component may be a component 198 of the device 1404 configured to perform the functions recited by the component. As described above, the device 1404 may include a Tx processor 368, an Rx processor 356, and a controller / processor 359. Thus, in one configuration, these components may be the Tx processor 368, the Rx processor 356, and / or the controller / processor 359 configured to perform the functions recited by these components.

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

[0152] 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 can 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, references to elements in the singular form do not mean "one and only one", but "one or more". Terms such as "if", "when..." and "at..." do not imply a direct temporal relationship or reaction. That is, these phrases, such as "when...", do not mean 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 without the need for a specific or immediate time limit 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 As, multiple Bs, or multiple Cs. 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, B, and C, where any such combination may include 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 a first device receives data from or sends data to a 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 this disclosure that are known or later become 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 expressly recited in the claims. Words such as "module," "mechanism," "element," and "device" are not a substitute for the word "component." Therefore, no claim element will be understood to be part-plus-function unless the element is expressly recited using the phrase "component for..."

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

[0154] A device configured to "output" data (such as, transmit, signal, or message) may transmit the data via a wireless device (e.g., through a transceiver) or may transmit the data to the device that transmitted the data. A device configured to "obtain" data (such as, transmit, signal, or message) may receive the data via a wireless device (e.g., through a transceiver) or may obtain the data from the device that received the data.

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

[0156] Aspect 1 is a method of communicating at a UE, wherein the method may include obtaining a command from a driver of a vehicle including an indication of a Disturbance Detection (DSD). The method may include adjusting a priority of objects detected within a sensor area of a sensor set based on the indication of the DSD.

[0157] Aspect 2 is a method according to aspect 1, wherein the sensor set may include at least one of a LIDAR sensor, a RADAR sensor, a SONAR sensor, a thermal sensor, a microphone, or a camera.

[0158] Aspect 3 is a method according to any one of aspects 1 or 2, wherein obtaining the command including the indication of the DSD may include obtaining a signal from the driver of the vehicle to monitor the sensor area. Obtaining the command including the indication of the DSD may include obtaining the indication of the DSD from the driver of the vehicle. Obtaining the command including the indication of the DSD may include calculating the sensor area based on the indication of the DSD.

[0159] Aspect 4 is a method according to aspect 3, wherein obtaining the signal from the driver of the vehicle may include obtaining the signal via at least one of an audio user interface or a touch user interface.

[0160] Aspect 5 is a method according to any one of aspects 3 or 4, wherein obtaining the indication of the DSD from the driver of the vehicle may include monitoring the direction the driver's head is facing to identify a zone. Obtaining the indication of the DSD from the driver of the vehicle may include monitoring the direction the driver's gaze is looking to identify the sensor area within the identified zone.

[0161] Aspect 6 is a method according to any one of aspects 3 to 5, wherein obtaining the indication of the DSD from the driver of the vehicle may include monitoring the direction of the gaze of the driver of the vehicle. Obtaining the indication of the DSD from the driver of the vehicle may include monitoring gestures made by the driver of the vehicle. Obtaining the indication of the DSD from the driver of the vehicle may include recording audio sounds uttered by the driver of the vehicle.

[0162] Aspect 7 is a method according to any one of aspects 1 to 6, wherein adjusting the direction of the sensor set may include sending a signal including at least one of the indication of the DSD or a second indication of the sensor area to a second UE.

[0163] Aspect 8 is a method according to aspect 7, wherein the method may include receiving a sensor result set associated with the sensor area from the second UE. The method may include outputting a sensor report based on the received sensor result set.

[0164] Aspect 9 is a method according to any one of aspects 7 or 8, wherein sending the signal to the second UE may include sending the signal using a V2X communication link with the second UE.

[0165] Aspect 10 is a method according to any one of aspects 1 to 9, wherein adjusting the priority of objects detected within the sensor area of the sensor set may include indicating the sensor area to the driver of the vehicle. Adjusting the priority of objects detected within the sensor area of the sensor set may include obtaining confirmation of the sensor area from the driver of the vehicle in response to the indication of the sensor area. Adjusting the priority of objects detected within the sensor area of the sensor set may include adjusting the priority of objects detected within the sensor area of the sensor set in response to receiving the confirmation of the sensor area from the driver of the vehicle.

[0166] Aspect 11 is a method according to aspect 10, wherein indicating the sensor area to the driver of the vehicle may include indicating the sensor area to the driver of the vehicle using a head-up display (HUD) of the vehicle. Indicating the sensor area to the driver of the vehicle may include indicating the sensor area to the driver of the vehicle on a screen of the vehicle. Indicating the sensor area to the driver of the vehicle may include indicating the sensor area to the driver of the vehicle using lights that illuminate the exterior of the vehicle.

[0167] Aspect 12 is a method according to any one of aspects 1 to 11, wherein the method may include obtaining sensor data from the set of sensors assigned to the sensor area. The method may include establishing a state of the sensor area based on the obtained sensor data. The method may include monitoring the obtained sensor data for a certain period of time in response to receiving the command. The method may include notifying the driver of the vehicle of a change from the established state based on the obtained sensor data.

[0168] Aspect 13 is a method according to aspect 12, wherein the change in state may include a new object state in the sensor area associated with the established state. The change in state may include a new obstacle in the sensor area associated with the established state. The change in state may include an inability to sense a portion of the sensor area associated with the established state.

[0169] Aspect 14 is a method according to any one of aspects 12 or 13, wherein monitoring the acquired sensor data during the time period may include identifying a set of objects within the sensor area. Monitoring the acquired sensor data during the time period may include calculating a path for each of the set of objects within the sensor area at a first time during the time period. Monitoring the acquired sensor data during the time period may include recalculating the path for each of the set of objects within the sensor area at a second time during the time period.

[0170] Aspect 15 is a method according to any one of aspects 12 to 14, wherein monitoring the acquired sensor data during the time period may include identifying a set of objects within the sensor area. Monitoring the acquired sensor data during the time period may include calculating a speed of each of the set of objects within the sensor area at a first time during the time period. Monitoring the acquired sensor data during the time period may include recalculating the speed of each of the set of objects within the sensor area at a second time during the time period.

[0171] Aspect 16 is an apparatus for wireless communication, the apparatus comprising: a memory; and at least one processor, the at least one processor being coupled to the memory and configured to implement any one of aspects 1 to 15 based at least in part on information stored in the memory.

[0172] Aspect 17 is the apparatus of aspect 16, further comprising at least one of an antenna or a transceiver coupled to the at least one processor.

[0173] Aspect 18 is an apparatus for wireless communication, comprising means for implementing any one of aspects 1 to 15.

[0174] Aspect 19 is a computer-readable medium (eg, non-transitory 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 15.

Claims

1. An apparatus for communicating 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 information stored in the memory, configured to: obtaining a command from a driver of a vehicle including an indication of a driver-specified direction (DSD); and Prioritization of objects detected within a sensor area of a sensor set is adjusted based on the indication of the DSD.

2. The device of claim 1 , wherein the sensor set comprises at least one of a light detection and ranging (LIDAR) sensor, a radio detection and ranging (RADAR) sensor, a sound navigation and ranging (SONAR) sensor, a thermal sensor, a microphone, or a camera.

3. The device according to claim 1, wherein To obtain the command comprising the indication of the DSD, the at least one processor is configured to: obtaining a signal from the driver of the vehicle to monitor the sensor area; obtaining the indication of the DSD from the driver of the vehicle; and The sensor area is calculated based on the indication of the DSD.

4. The device according to claim 3, wherein In order to obtain the signal from the driver of the vehicle, the at least one processor is configured to: The signal is obtained via at least one of an audio user interface or a touch user interface.

5. The device according to claim 3, wherein To obtain the indication of the DSD from the driver of the vehicle, the at least one processor is configured to: monitoring the direction the driver's head is facing to identify a zone; as well as A gaze direction of the driver of the vehicle is monitored to identify the sensor area within the identified zone.

6. The device according to claim 3, wherein To obtain the indication of the DSD from the driver of the vehicle, the at least one processor is configured to: monitoring a gaze direction of the driver of the vehicle; monitoring gestures performed by the driver of the vehicle; or Audio sounds emanating from the driver of the vehicle are recorded.

7. The device according to claim 1, wherein To adjust the priority of objects detected within the sensor area, the at least one processor is configured to: A signal including at least one of the indication of the DSD or a second indication of the sensor area is sent to a second UE.

8. The apparatus of claim 7, wherein the at least one processor is further configured to: receiving, from the second UE, a set of sensor results associated with the sensor area; and A sensor report is output based on the received sensor result set.

9. The device according to claim 7, wherein To send the signal to the second UE, the at least one processor is configured to: The signal is sent using a vehicle-to-everything (V2X) communication link with the second UE.

10. The apparatus of claim 7, further comprising a transceiver coupled to the at least one processor, wherein To send the signal, the at least one processor is configured to: The signal including at least one of the indication of the DSD or the second indication of the sensor area is sent to the second UE via the transceiver.

11. The device according to claim 1, wherein To adjust the priority of objects detected within the sensor area of the sensor set, the at least one processor is configured to: indicating the sensor area to the driver of the vehicle; obtaining confirmation of the sensor area from the driver of the vehicle in response to the indication of the sensor area; as well as In response to obtaining the confirmation of the sensor area from the driver of the vehicle, the priority of objects detected within the sensor area of the sensor set is adjusted.

12. The device according to claim 11, wherein In order to indicate the sensor area to the driver of the vehicle, the at least one processor is configured to: indicating the sensor area to the driver of the vehicle using a heads-up display (HUD) of the vehicle; indicating the sensor area to the driver of the vehicle on a screen of the vehicle; or The sensor area is indicated to the driver of the vehicle using lights that illuminate the exterior of the vehicle.

13. The apparatus of claim 1 , wherein the at least one processor is further configured to: obtaining sensor data from the set of sensors aligned to the sensor area; establishing a state of the sensor region based on the obtained sensor data; In response to obtaining the command, monitoring the obtained sensor data for a certain period of time; as well as The driver of the vehicle is notified of a change from the established state based on the obtained sensor data.

14. The apparatus of claim 13, wherein the change in the state comprises at least one of: a new object state in the sensor area associated with the established state; a new obstacle in the sensor area associated with the established state; or Portions of the sensor area that are relevant to the established state cannot be sensed.

15. The device according to claim 13, wherein To monitor the obtained sensor data during the time period, the at least one processor is configured to: Identifying a set of objects within the sensor area; calculating a path for each of the set of objects within the sensor area at a first time during the time period; as well as The path of each of the set of objects within the sensor area is recalculated at a second time during the time period.

16. The device according to claim 13, wherein To monitor the obtained sensor data during the time period, the at least one processor is configured to: Identifying a set of objects within the sensor area; calculating a velocity of each of the set of objects within the sensor area at a first time during the time period; as well as The velocity of each of the set of objects within the sensor area is recalculated at a second time during the time period.

17. A method of communicating at a user equipment (UE), the method comprising: obtaining a command from a driver of a vehicle including an indication of a driver-specified direction (DSD); as well as Prioritization of objects detected within a sensor area of a sensor set is adjusted based on the indication of the DSD.

18. The method of claim 17, wherein the sensor set includes at least one of a light detection and ranging (LIDAR) sensor, a radio detection and ranging (RADAR) sensor, a sound navigation and ranging (SONAR) sensor, a thermal sensor, a microphone, or a camera.

19. The method of claim 17, wherein obtaining the command including the indication of the DSD comprises: obtaining a signal from the driver of the vehicle to monitor the sensor area; obtaining the indication of the DSD from the driver of the vehicle; as well as The sensor area is calculated based on the indication of the DSD.

20. The method of claim 19, wherein obtaining the signal from the driver of the vehicle comprises obtaining the signal via at least one of an audio user interface or a touch user interface.

21. The method of claim 19, wherein obtaining the indication of the DSD from the driver of the vehicle comprises: monitoring the direction the driver's head is facing to identify a zone; as well as A gaze direction of the driver of the vehicle is monitored to identify the sensor area within the identified zone.

22. The method of claim 19, wherein obtaining the indication of the DSD from the driver of the vehicle comprises at least one of: monitoring a gaze direction of the driver of the vehicle; monitoring gestures performed by the driver of the vehicle; or Audio sounds emanating from the driver of the vehicle are recorded.

23. The method of claim 17, wherein adjusting the priority of objects detected within the sensor area comprises: A signal including at least one of the indication of the DSD or a second indication of the sensor area is sent to a second UE.

24. The method according to claim 23, further comprising: receiving, from the second UE, a set of sensor results associated with the sensor area; as well as A sensor report is output based on the received sensor result set.

25. The method of claim 23, wherein sending the signal to the second UE comprises sending the signal using a vehicle-to-everything (V2X) communication link with the second UE.

26. The method of claim 25, wherein adjusting the priority of objects detected within the sensor area of the sensor set comprises: indicating the sensor area to the driver of the vehicle; obtaining confirmation of the sensor area from the driver of the vehicle in response to the indication of the sensor area; as well as In response to obtaining the confirmation of the sensor area from the driver of the vehicle, the priority of objects detected within the sensor area of the sensor set is adjusted.

27. The method of claim 25, wherein indicating the sensor area to the driver of the vehicle comprises at least one of: indicating the sensor area to the driver of the vehicle using a heads-up display (HUD) of the vehicle; indicating the sensor area to the driver of the vehicle on a screen of the vehicle; or The sensor area is indicated to the driver of the vehicle using lights that illuminate the exterior of the vehicle.

28. The method of claim 17, further comprising: obtaining sensor data from the set of sensors aligned to the sensor area; establishing a state of the sensor region based on the obtained sensor data; In response to obtaining the command, monitoring the obtained sensor data for a certain period of time; as well as The driver of the vehicle is notified of a change from the established state based on the obtained sensor data.

29. An apparatus for communicating at a user equipment (UE), the apparatus comprising: means for obtaining a command from a driver of a vehicle including an indication of a driver-specified direction (DSD); and Means for adjusting a priority of objects detected within a sensor area of a sensor set based on the indication of the DSD.

30. A computer-readable medium storing computer-executable code at a user equipment (UE) that, when executed by a processor, causes the processor to: obtaining a command from a driver of a vehicle including an indication of a driver-specified direction (DSD); and Prioritization of objects detected within a sensor area of a sensor set is adjusted based on the indication of the DSD.

Images