Autonomous emergency steering path planner fusing DWA and a-star algorithms
The integration of A* and DWA algorithms in AES systems optimizes path planning to efficiently avoid obstacles and maintain lane alignment, enhancing the safety and reliability of autonomous vehicles.
Patent Information
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- QUALCOMM INC
- Filing Date
- 2024-10-29
- Publication Date
- 2026-05-07
AI Technical Summary
Existing autonomous emergency steering (AES) systems in advanced driver assistance systems (ADAS) and autonomous driving face challenges in optimizing path planning to effectively avoid obstacles while maintaining lane alignment, particularly when multiple obstacles are present.
The integration of the A-star (A*) algorithm with the dynamic window approach (DWA) algorithm enhances AES path planning by generating a global path considering obstacles and lane markers, using A* for long-term planning and DWA for local collision avoidance, balancing obstacle avoidance with lane marker alignment through a two-phase strategy.
This approach optimizes AES performance by providing a more accurate and efficient path that effectively avoids collisions and maintains lane alignment, improving the overall safety and reliability of autonomous vehicles.
Smart Images

Figure CN2024128031_07052026_PF_FP_ABST
Abstract
Description
AUTONOMOUS EMERGENCY STEERING PATH PLANNER FUSING DWA AND A-STAR ALGORITHMSTECHNICAL FIELD
[0001] The present disclosure relates generally to assisted / autonomous driving, and more particularly, to autonomous emergency steering (AES) systems associated with advanced driver assistance systems (ADAS) and / or assisted / autonomous driving.
[0002] INTRODUCTION
[0003] Wireless communication systems are widely deployed to provide various 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.
[0004] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a municipal, national, regional, and even global level. An example telecommunication standard is 5G New Radio (NR) . 5G NR is part of a continuous mobile broadband evolution promulgated by Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with 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. There exists a need for further improvements in 5G NR technology. These improvements may also be applicable to other multi-access technologies and the telecommunication standards that employ these technologies.
[0005] BRIEF SUMMARY
[0006] The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects. This summary neither identifies key or critical elements of all aspects nor delineates 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 is presented later.
[0007] In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus identifies there is a potential collision with a set of objects on a travelling path of the user equipment (UE) . The apparatus determines, based on identification of the potential collision with the set of objects, a first path that includes a set of nodes for avoiding the set of objects using a first algorithm. The apparatus determines, based on using at least one node in the set of nodes as a target, a second path for avoiding at least one object in the set of objects using a second algorithm. The apparatus outputs an indication to switch to the second path for avoiding the at least one object in the set of objects.
[0008] To the accomplishment of the foregoing and related ends, the one or more aspects may include the features hereinafter fully described and particularly pointed out in the claims. The following description and the drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of various aspects may be employed.BRIEF DESCRIPTION OF THE DRAWINGS
[0009] FIG. 1 is a diagram illustrating an example of a wireless communications system and an access network.
[0010] FIG. 2A is a diagram illustrating an example of a first frame, in accordance with various aspects of the present disclosure.
[0011] FIG. 2B is a diagram illustrating an example of downlink (DL) channels within a subframe, in accordance with various aspects of the present disclosure.
[0012] FIG. 2C is a diagram illustrating an example of a second frame, in accordance with various aspects of the present disclosure.
[0013] FIG. 2D is a diagram illustrating an example of uplink (UL) channels within a subframe, in accordance with various aspects of the present disclosure.
[0014] FIG. 3 is a diagram illustrating an example of a base station and user equipment (UE) in an access network.
[0015] FIG. 4 is a diagram illustrating an example of a vehicle performing road object detection using different types of sensors in accordance with various aspects of the present disclosure.
[0016] FIG. 5 is a diagram illustrating an example of an autonomous emergency steering (AES) system that is configured to use an A-star (A*) algorithm in accordance with various aspects of the present disclosure.
[0017] FIG. 6 is a diagram illustrating an example of a vehicle performing AES in accordance with various aspects of the present disclosure.
[0018] FIG. 7 is a diagram illustrating an example scenario of an AES path generated based on the A*algorithm encountering multiple obstacles in accordance with various aspects of the present disclosure.
[0019] FIG. 8 is a diagram illustrating an example of an AES system that fuses an A*algorithm and a dynamic window approach (DWA) algorithm in accordance with various aspects of the present disclosure.
[0020] FIG. 9 is a diagram illustrating an example of a UE selecting a global path based on an A*algorithm in accordance with various aspects of the present disclosure.
[0021] FIG. 10 is a diagram illustrating an example of creating nodes around obstacle (s) in accordance with various aspects of the present disclosure.
[0022] FIG. 11A is a diagram illustrating an example of a node connection route for an A*algorithm in accordance with various aspects of the present disclosure.
[0023] FIG. 11B is a diagram illustrating an example of a node connection route for a new A*algorithm in accordance with various aspects of the present disclosure.
[0024] FIG. 12 is a diagram illustrating an example of nodes creation based on a new A*algorithm in accordance with various aspects of the present disclosure.
[0025] FIG. 13 is a diagram illustrating an example DWA process / algorithm in accordance with various aspects of the present disclosure.
[0026] FIG. 14A is a diagram illustrating an example of the first phase (Phase 1) for the DWA algorithm in accordance with various aspects of the present disclosure.
[0027] FIG. 14B is a diagram illustrating an example of the second phase (Phase 2) for the DWA algorithm in accordance with various aspects of the present disclosure.
[0028] FIG. 15 is a diagram illustrating an example AES path generated based on a new A*algorithm in accordance with various aspects of the present disclosure.
[0029] FIG. 16 is a flowchart of a method of wireless communication.
[0030] FIG. 17 is a diagram illustrating an example of a hardware implementation for an example apparatus and / or network entity.DETAILED DESCRIPTION
[0031] Aspects presented herein may improve the overall performance of autonomous emergency steering (AES) for vehicles by enabling the AES to use different algorithms. For example, aspects presented herein may optimize the AES path planner by fusing the A-star (A*) algorithm and a dynamic window approach (DWA) algorithm. The A*algorithm may be used to generate a global path considering both obstacles and lane marker, and the DWA algorithm may be configured to use A*generated global node (s) as local target. Then, the cost function of the DWA algorithm may be used to balance avoid collision with obstacles and follow the nodes generated by the A*algorithm. In addition, the DWA algorithm may consider wheel angle rate as an input group, and use vehicle kinematic model to calculate predict path to get a path with best evaluation function. The DWA may also be configured to use a two-phase strategy to combine obstacle collision avoidance and keep heading of the vehicle the same with lane marker (e.g., to balance the obstacle avoidance and lane marker direction goal) . In other words, when several obstacles are in an ego path / lane, the A*algorithm may be implemented to provide a valid global path, and the DWA algorithm may be implemented to provide a more accurate path to avoid collision with obstacle.
[0032] The detailed description set forth below in connection with the drawings describes various configurations and does not represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts.
[0033] Several aspects of telecommunication systems are presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as “elements” ) . These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.
[0034] By way of example, an element, or any portion of an element, or any combination of elements may be implemented as a “processing system” that includes one or more processors. When multiple processors are implemented, the multiple processors may perform the functions individually or in combination. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs) , central processing units (CPUs) , application processors, digital signal processors (DSPs) , reduced instruction set computing (RISC) processors, systems on a chip (SoC) , baseband processors, field programmable gate arrays (FPGAs) , programmable logic devices (PLDs) , state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functionality described throughout this disclosure. One or more processors in the processing system may execute software. Software, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise, shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.
[0035] Accordingly, in one or more example aspects, implementations, and / or use cases, the functions described may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on or encoded as one or more instructions or code on a computer-readable medium. Computer-readable media includes computer storage media. Storage media may be any available media that can be accessed by a computer. By way of example, such computer-readable media can include a random-access memory (RAM) , a read-only memory (ROM) , an electrically erasable programmable ROM (EEPROM) , optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of the 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.
[0036] While aspects, implementations, and / or use cases are described in this application by illustration to some examples, additional or different aspects, implementations and / or use cases may come about in many different arrangements and scenarios. Aspects, implementations, and / or use cases described herein may be implemented across many differing platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, aspects, implementations, and / or use cases may come about via integrated chip implementations and other non-module-component based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, artificial intelligence (AI) -enabled devices, etc. ) . While some examples may or may not be specifically directed to use cases or applications, a wide assortment of applicability of described examples may occur. Aspects, implementations, and / or use cases may range a spectrum from chip-level or modular components to non-modular, non-chip-level implementations and further to aggregate, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more techniques herein. In some practical settings, devices incorporating described aspects and features may also include additional components and features for implementation and practice of claimed and described aspect. For example, transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes (e.g., hardware components including antenna, radio frequency (RF) -chains, power amplifiers, modulators, buffer, processor (s) , interleaver, adders / summers, etc. ) . Techniques described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc. of varying sizes, shapes, and constitution.
[0037] Deployment of communication systems, such as 5G NR systems, may be arranged in multiple manners with various components or constituent 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 a network equipment, such as a base station (BS) , or one or more units (or one or more components) performing base station functionality, may be implemented in an aggregated or disaggregated architecture. For example, a BS (such as a Node B (NB) , evolved NB (eNB) , NR BS, 5G NB, access point (AP) , a transmission reception point (TRP) , or a cell, etc. ) may be implemented as an aggregated base station (also known as a standalone BS or a monolithic BS) or a disaggregated base station.
[0038] An aggregated base station may be configured to utilize a radio protocol stack that is physically or logically integrated within a single RAN node. A disaggregated base station may be configured to utilize a protocol stack that is physically or logically distributed among 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 throughout one or multiple other RAN nodes. The DUs may be implemented to communicate with one or more RUs. Each of the CU, DU and RU can be implemented as virtual units, i.e., a virtual central unit (VCU) , a virtual distributed unit (VDU) , or a virtual radio unit.
[0039] Base station operation or network design may consider aggregation characteristics of base station functionality. For example, disaggregated base stations may be utilized in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (such as the network configuration sponsored 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 distributing functionality for at least one unit virtually, which can enable flexibility in network design. The various units of the disaggregated base station, or disaggregated RAN architecture, can be configured for wired or wireless communication with at least one other unit.
[0040] FIG. 1 is a diagram 100 illustrating an example of a wireless communications system and an access network. The illustrated wireless communications system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs 110 that can 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) . A CU 110 may communicate with one or more DUs 130 via respective midhaul links, such as an F1 interface. The DUs 130 may communicate with one or more RUs 140 via respective fronthaul links. The RUs 140 may communicate with respective UEs 104 via one or more radio frequency (RF) access links. In some implementations, the UE 104 may be simultaneously served by multiple RUs 140.
[0041] Each of the units, i.e., the CUs 110, the DUs 130, the RUs 140, as well as the Near-RT RICs 125, the Non-RT RICs 115, and the SMO Framework 105, may include one or more interfaces or be coupled to one or more interfaces configured to receive or to transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of the units, can be configured to communicate with one or more of the other units via the transmission medium. For example, the units can include a wired interface configured to receive or to transmit signals over a wired transmission medium to one or more of the other units. Additionally, the units can include a wireless interface, which may include a receiver, a transmitter, or a transceiver (such as an RF transceiver) , configured to receive or to transmit signals, or both, over a wireless transmission medium to one or more of the other units.
[0042] In some aspects, the CU 110 may host one or more higher layer control functions. Such control functions can include radio resource control (RRC) , packet data convergence protocol (PDCP) , service data adaptation protocol (SDAP) , or the like. Each control function can be implemented with an interface 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 implementations, the CU 110 can be logically split into one or more CU-UP units and one or more CU-CP units. The CU-UP unit can communicate bidirectionally with the CU-CP unit via an interface, such as an E1 interface when implemented in an O-RAN configuration. The CU 110 can be implemented to communicate with the DU 130, as necessary, for network control and signaling.
[0043] The DU 130 may correspond to a logical unit that includes one or more base station functions to control 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 high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation, demodulation, or the like) depending, at least in part, on a functional split, such as those defined by 3GPP. In some aspects, the DU 130 may further host one or more low PHY layers. Each layer (or module) can be implemented with an interface configured to communicate signals with other layers (and modules) hosted by the DU 130, or with the control functions hosted by the CU 110.
[0044] Lower-layer functionality can be implemented by one or more RUs 140. In some deployments, an RU 140, controlled by a DU 130, may correspond to a logical node that hosts RF processing functions, or low-PHY layer functions (such as performing fast Fourier transform (FFT) , inverse FFT (iFFT) , digital beamforming, physical random access channel (PRACH) extraction and filtering, or the like) , or both, based at least in part on the functional split, such as a lower layer functional split. In such an architecture, the RU (s) 140 can be implemented to handle over the air (OTA) communication with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control and user plane communication with the RU (s) 140 can be controlled by the corresponding DU 130. In some scenarios, this configuration can enable the DU (s) 130 and the CU 110 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.
[0045] The SMO Framework 105 may be configured to support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 105 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements that may be managed via an operations and maintenance interface (such as an O1 interface) . For virtualized network elements, the SMO Framework 105 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 190) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface) . Such virtualized network elements can include, but are not limited to, CUs 110, DUs 130, RUs 140 and Near-RT RICs 125. In some implementations, the SMO Framework 105 can communicate with a hardware aspect of a 4G RAN, such as an open eNB (O-eNB) 111, via an O1 interface. Additionally, in some implementations, the SMO Framework 105 can communicate directly with one or more RUs 140 via an O1 interface. The SMO Framework 105 also may include a Non-RT RIC 115 configured to support functionality of the SMO Framework 105.
[0046] The Non-RT RIC 115 may be configured to include a logical function 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 updates, or policy-based guidance of applications / features in the Near-RT RIC 125. The Non-RT RIC 115 may be coupled to or communicate with (such as via an A1 interface) the Near-RT RIC 125. The Near-RT RIC 125 may be configured to include a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions over an interface (such as via an E2 interface) connecting one or more CUs 110, one or more DUs 130, or both, as well as an O-eNB, with the Near-RT RIC 125.
[0047] 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 external servers. Such information may be utilized by the Near-RT RIC 125 and may be received at the SMO Framework 105 or the Non-RT RIC 115 from non-network data sources or from network functions. 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 for performance and employ AI / ML models to perform corrective actions through the SMO Framework 105 (such as reconfiguration via O1) or via creation of RAN management policies (such as A1 policies) .
[0048] At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Accordingly, a base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component indicated with dotted lines to signify 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 a UE 104. The base station 102 may include macrocells (high power cellular base station) and / or small cells (low power cellular base station) . The small cells include femtocells, picocells, and microcells. A network that includes both small cell and macrocells may be known as a heterogeneous network. A heterogeneous network may also include Home Evolved Node Bs (eNBs) (HeNBs) , which may provide service to a restricted group known as a closed subscriber group (CSG) . The communication links between the RUs 140 and the UEs 104 may include uplink (UL) (also referred to as reverse link) transmissions from a UE 104 to an RU 140 and / or downlink (DL) (also referred to as forward link) transmissions from an RU 140 to a UE 104. The communication links may use multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication links may be through one or more carriers. The base station 102 / UEs 104 may use spectrum up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) bandwidth per carrier allocated in a carrier aggregation of up to a total of Yx MHz (x component carriers) used for transmission in each direction. The carriers may or may not be adjacent to each other. Allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL) . The component carriers may include a primary component carrier and one or more secondary component carriers. A primary component carrier may be referred to as a primary cell (PCell) and a secondary component carrier may be referred to as a secondary cell (SCell) .
[0049] Certain UEs 104 may communicate with each other using device-to-device (D2D) communication link 158. The D2D communication link 158 may use the DL / UL wireless wide area network (WWAN) spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH) , a physical sidelink discovery channel (PSDCH) , a physical sidelink shared channel (PSSCH) , and a physical sidelink control channel (PSCCH) . D2D communication may be through a variety of wireless D2D communications systems, such as for example, BluetoothTM (Bluetooth is a trademark of the Bluetooth Special Interest Group (SIG) ) , Wi-FiTM (is a trademark of the Wi-Fi Alliance) based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.
[0050] The wireless communications system may further include a Wi-Fi AP 150 in communication with UEs 104 (also referred to as Wi-Fi stations (STAs) ) via communication link 154, e.g., in a 5 GHz unlicensed frequency spectrum or the like. When communicating in an unlicensed frequency spectrum, the UEs 104 / AP 150 may perform a clear channel assessment (CCA) prior to communicating in order to determine whether the channel is available.
[0051] The electromagnetic spectrum is often subdivided, based on frequency / wavelength, into various classes, bands, channels, etc. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz –7.125 GHz) and FR2 (24.25 GHz –52.6 GHz) . Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “sub-6 GHz” band in various documents and articles. A similar nomenclature issue sometimes occurs with regard to FR2, which is often referred to (interchangeably) as a “millimeter wave” band in documents and articles, despite being different from the extremely high frequency (EHF) band (30 GHz –300 GHz) which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band.
[0052] The frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Recent 5G NR studies have identified an operating band for these mid-band frequencies as frequency range designation FR3 (7.125 GHz –24.25 GHz) . Frequency bands falling within FR3 may inherit FR1 characteristics and / or FR2 characteristics, and thus may effectively extend features of FR1 and / or FR2 into mid-band frequencies. In addition, higher frequency bands are currently being explored to extend 5G NR operation beyond 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.
[0053] With the above aspects in mind, unless specifically stated otherwise, the term “sub-6 GHz” or the like if used herein may broadly represent frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Further, unless specifically stated otherwise, the term “millimeter wave” or the like if used herein may broadly represent frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and / or FR5, or may be within the EHF band.
[0054] The base station 102 and the UE 104 may each include a plurality of antennas, such as antenna elements, antenna panels, and / or antenna arrays to facilitate beamforming. The base station 102 may transmit a beamformed signal 182 to the UE 104 in one or more transmit directions. The UE 104 may receive the beamformed signal from the base station 102 in one or more receive directions. The UE 104 may also transmit a beamformed signal 184 to the base station 102 in one or more transmit directions. The base station 102 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 102 / UE 104 may perform beam training to determine the best receive and transmit directions for each of the base station 102 / UE 104. The transmit and receive directions for the base station 102 may or may not be the same. The transmit and receive directions for the UE 104 may or may not be the same.
[0055] The base station 102 may include and / or be referred to as a gNB, Node B, eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS) , an extended service set (ESS) , a TRP, network node, network entity, network equipment, or some other suitable terminology. The base station 102 can be implemented as an integrated access backhaul (IAB) node, a relay node, a sidelink node, an aggregated (monolithic) base station with a baseband unit (BBU) (including a CU and a DU) and an RU, or as a disaggregated base station including one or more of a CU, a DU, and / or an RU. The set of base stations, which may include disaggregated base stations and / or aggregated base stations, may be referred to as next generation (NG) RAN (NG-RAN) .
[0056] 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 the control node that processes the signaling between the UEs 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 identification handling, access authorization, and subscription management. The one or more location servers 168 are illustrated as including a Gateway Mobile Location Center (GMLC) 165 and a Location Management Function (LMF) 166. However, generally, 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, the LMF 166, a position determination entity (PDE) , a serving mobile location center (SMLC) , a mobile positioning center (MPC) , or the like. The GMLC 165 and the LMF 166 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) for accessing UE positioning information. The LMF 166 receives measurements and assistance information from the NG-RAN and the UE 104 via the AMF 161 to compute the position of the UE 104. The NG-RAN may utilize one or more positioning methods in order to determine the position of the UE 104. Positioning the UE 104 may involve signal measurements, a position estimate, and an optional velocity computation based on the measurements. The signal measurements may be made by the UE 104 and / or the base station 102 serving the UE 104. The signals measured 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) , global position system (GPS) , non-terrestrial network (NTN) , or other satellite position / location system) , LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS) , sensor-based information (e.g., barometric pressure sensor, motion sensor) , NR enhanced cell ID (NR E-CID) methods, 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.
[0057] Examples of UEs 104 include a cellular phone, a smart phone, a session initiation protocol (SIP) phone, a laptop, a personal digital assistant (PDA) , a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player) , a camera, a game console, a tablet, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, or any other similar functioning device. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meter, gas pump, toaster, vehicles, heart monitor, etc. ) . The UE 104 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. 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 collectively access the network and / or individually access the network.
[0058] Referring again to FIG. 1, in certain aspects, the UE 104 may have an AES component 198 that may be configured to identify there is a potential collision with a set of objects on a travelling path of the UE; determine, based on identification of the potential collision with the set of objects, a first path that includes a set of nodes for avoiding the set of objects using a first algorithm; determine, based on using at least one node in the set of nodes as a target, a second path for avoiding at least one object in the set of objects using a second algorithm; and output an indication to switch to the second path for avoiding the at least one object in the set of objects. In certain aspects, the base station 102 or the one or more location servers 168 may have an AES configuration component 199 that may be configured to provide AES related configurations to the UE 104.
[0059] FIG. 2A is a diagram 200 illustrating an example of a first subframe within a 5G NR frame structure. FIG. 2B is a diagram 230 illustrating an example of DL channels within a 5G NR subframe. FIG. 2C is a diagram 250 illustrating an example of a second subframe within a 5G NR frame structure. FIG. 2D is a diagram 280 illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplexed (FDD) in which for a particular set of subcarriers (carrier system bandwidth) , subframes within the set of subcarriers are dedicated for either DL or UL, or may be time division duplexed (TDD) in which for a particular set of subcarriers (carrier system bandwidth) , subframes within the set of subcarriers are dedicated for both DL and UL. In the examples provided by FIGs. 2A, 2C, the 5G NR frame structure is assumed to be TDD, with subframe 4 being configured with slot format 28 (with mostly DL) , where D is DL, U is UL, and F is flexible for use between DL / UL, and subframe 3 being configured with slot format 1 (with all UL) . While subframes 3, 4 are shown with slot formats 1, 28, respectively, any particular subframe may be configured with any of the various available slot formats 0-61. Slot formats 0, 1 are all DL, UL, respectively. Other slot formats 2-61 include a mix of DL, UL, and flexible symbols. UEs are configured with the slot format (dynamically through DL control information (DCI) , or semi-statically / statically through radio resource control (RRC) signaling) through a received slot format indicator (SFI) . Note that the description infra applies also to a 5G NR frame structure that is TDD.
[0060] FIGs. 2A-2D illustrate a frame structure, and the aspects of the present disclosure may be applicable to other wireless communication technologies, which may have a different frame structure and / or different channels. A frame (10 ms) may be divided into 10 equally sized subframes (1 ms) . Each subframe may include one or more time slots. Subframes may also include mini-slots, which may include 7, 4, or 2 symbols. Each slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is normal or extended. For normal CP, each slot may include 14 symbols, and for extended CP, each slot may include 12 symbols. The symbols on DL may be CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbols. The symbols on 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 a single stream transmission) . The number of slots within a subframe is based on the CP and the numerology. The numerology defines the subcarrier spacing (SCS) (see Table 1) . The symbol length / duration may scale with 1 / SCS.
[0061] Table 1: Numerology, SCS, and CP
[0062] For normal CP (14 symbols / slot) , different numerologies μ 0 to 4 allow for 1, 2, 4, 8, and 16 slots, respectively, per subframe. For extended CP, the numerology 2 allows for 4 slots per subframe. Accordingly, for normal CP and numerology μ, there are 14 symbols / slot and 2μ slots / subframe. The subcarrier spacing may be equal to 2μ* 15 kHz, where μ is the numerology 0 to 4. As such, the numerology μ=0 has a subcarrier spacing of 15 kHz and the numerology μ=4 has a subcarrier spacing of 240 kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIGs. 2A-2D provide an example of normal CP with 14 symbols per slot and numerology μ=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 set of frames, there may be one or more different bandwidth parts (BWPs) (see FIG. 2B) that are frequency division multiplexed. Each BWP may have a particular numerology and CP (normal or extended) .
[0063] A resource grid may be used to represent the frame structure. Each time slot includes a resource block (RB) (also referred to as physical RBs (PRBs) ) that extends 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.
[0064] As illustrated in FIG. 2A, some of the REs carry reference (pilot) signals (RS) for the UE.The RS may include demodulation RS (DM-RS) (indicated as R for one particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS) for channel estimation at the UE. The RS may also include beam measurement RS (BRS) , beam refinement RS (BRRS) , and phase tracking RS (PT-RS) .
[0065] FIG. 2B illustrates an example of various DL channels within a subframe of a frame. 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 including six RE groups (REGs) , each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within one BWP may be referred to as a control resource set (CORESET) . A UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., common search space, UE-specific search space) during PDCCH monitoring occasions on the CORESET, where the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at greater and / or lower frequencies across the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of particular subframes of a frame. The PSS is used by a UE 104 to determine subframe / symbol timing and a physical layer identity. A secondary synchronization signal (SSS) may be within symbol 4 of particular subframes of a frame. The SSS is used by a UE to determine a 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 a physical cell identifier (PCI) . Based on the PCI, the UE can determine the locations of the DM-RS. The physical broadcast channel (PBCH) , which carries a master information block (MIB) , may be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as SS block (SSB) ) . The MIB provides a number of RBs in the system bandwidth and a system frame number (SFN) . The physical downlink shared channel (PDSCH) carries user data, broadcast system information not transmitted through the PBCH such as system information blocks (SIBs) , and paging messages.
[0066] As illustrated in FIG. 2C, some of the REs carry DM-RS (indicated as R for one particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may transmit DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH) . The PUSCH DM-RS may be transmitted in the first one or two symbols of the PUSCH. The PUCCH DM-RS may be transmitted in different configurations depending on whether short or long PUCCHs are transmitted and depending on the particular PUCCH format used. The UE may transmit sounding reference signals (SRS) . The SRS may be transmitted in the last symbol of a subframe. The SRS may have a comb structure, and a UE may transmit SRS on one of the combs. The SRS may be used by a base station for channel quality estimation to enable frequency-dependent scheduling on the UL.
[0067] FIG. 2D illustrates an example of various UL channels within a subframe of a frame. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI) , such as scheduling requests, a channel quality indicator (CQI) , a precoding matrix indicator (PMI) , a rank indicator (RI) , and hybrid automatic repeat request (HARQ) acknowledgment (ACK) (HARQ-ACK) feedback (i.e., one or more HARQ ACK bits indicating one or more ACK and / or negative ACK (NACK) ) . The PUSCH carries data, and may additionally be used to carry a buffer status report (BSR) , a power headroom report (PHR) , and / or UCI.
[0068] FIG. 3 is a block diagram of a base station 310 in communication with a UE 350 in an access network. 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, SIBs) , 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 the transfer of upper layer packet data units (PDUs) , error correction through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs) , re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs) , demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.
[0069] The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1, which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding / decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation / demodulation of physical channels, and MIMO antenna processing. The TX processor 316 handles 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) , M-quadrature amplitude modulation (M-QAM) ) . The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate 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 with a respective spatial stream for transmission.
[0070] At the UE 350, each receiver 354Rx receives a signal through its respective antenna 352. Each receiver 354Rx recovers information modulated onto an RF carrier and provides the information to the 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 may 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 may be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then converts the OFDM symbol stream from the time-domain to the frequency domain using a Fast Fourier Transform (FFT) . The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, are recovered and demodulated by determining the most likely signal constellation points transmitted by the base station 310. These soft decisions may be based on channel estimates computed by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals that were originally transmitted by the base station 310 on the physical channel. The data and control signals are then provided to the controller / processor 359, which implements layer 3 and layer 2 functionality.
[0071] The controller / processor 359 can be associated with at least one memory 360 that stores program codes and data. The at least one 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, deciphering, 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.
[0072] Similar to the functionality described in connection with the DL transmission by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression / decompression, and security (ciphering, deciphering, integrity protection, integrity verification) ; RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.
[0073] Channel estimates derived by a channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antenna 352 via separate transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a respective spatial stream for transmission.
[0074] The UL transmission is processed at the base station 310 in a manner similar to that described in connection with the receiver function at the UE 350. Each receiver 318Rx receives a signal through its respective antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to a RX processor 370.
[0075] The controller / processor 375 can be associated with at least one memory 376 that stores program codes and data. The at least one 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, deciphering, header decompression, 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.
[0076] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform aspects in connection with the AES component 198 of FIG. 1.
[0077] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform aspects in connection with the AES configuration component 199 of FIG. 1.
[0078] In recent years, vehicle manufacturers have been developing vehicles with assisted driving and / or autonomous driving capabilities. Assisted driving, which may also be called advanced driver assistance systems (ADAS) , may refer to a set of technologies designed to enhance vehicle safety and improve the driving experience by providing assistance and automation to the driver. These technologies may use various sensor (s) , such as camera (s) , radar (s) , light detection and ranging (lidar (s) or lidar sensor (s) ) , etc., and other components to monitor a vehicle’s surroundings and assist the driver of the vehicle with certain driving tasks. For example, some features of assisted driving systems may include: (1) adaptive cruise control (ACC) (e.g., a system that automatically adjusts a vehicle’s speed to maintain a safe following distance from the vehicle ahead) , (2) lane-keeping assist (LKA) (e.g., a system that uses cameras to detect lane markings and helps keep the vehicle centered within the lane, and provides steering inputs to prevent unintentional lane departure) , (3) , autonomous emergency braking (AEB) (e.g., a system that detects potential collisions with obstacles or pedestrians and automatically apply the brakes to avoid or mitigate the impact) , (4) blind spot monitoring (BSM) (e.g., a system that uses sensors to detect vehicles in a driver’s blind spots and provides visual or audible alerts to avoid potential collisions during lane changes) , (5) parking assistance (e.g., a system that assists drivers in parking their vehicles by using camera (s) and sensor (s) to help with parallel parking or maneuvering into tight spaces) , and / or traffic sign recognition (e.g., camera (s) and image processing are used to recognize and display traffic signs such as speed limits, stop signs, and other road regulations on the vehicle’s dashboard) .
[0079] Autonomous driving (AD) , which may also be referred to as the autonomous driving system (ADS) , self-driving, and / or driverless technology, may refer to the ability of a vehicle to navigate and operate itself without specifying human intervention (e.g., travelling from one place to another place without a human controlling the vehicle) . The goal of the autonomous driving is to create vehicles that are capable of perceiving their surroundings, making decisions, and controlling their movements, all without the direct involvement of a human driver. To achieve or improve the autonomous driving, a vehicle may be specified to use a map (or map data) with detailed information, such as a high-definition (HD) map. An HD map may refer to a highly detailed and accurate digital map designed for use in autonomous driving and ADAS. In one example, HD maps may typically include one or more of: (1) geometric information (e.g., precise road geometry, including lane boundaries, curvature, slopes, and detailed 3D models of the surrounding environment) , (2) lane-level information (e.g., information about individual lanes on the road, such as lane width, lane type (e.g., driving, turning, or parking lanes) , and lane connectivity) , (3) road attributes (e.g., data on road features like traffic signs, signals, traffic lights, speed limits, and road markings) , (4) topology (e.g., information about the relationships between different roads, intersections, and connectivity patterns) , (5) static objects (e.g., locations and details of fixed objects along the road, such as buildings, traffic barriers, and poles) , (6) dynamic objects (e.g., real-time or frequently updated data about moving objects, like other vehicles, pedestrians, and cyclists) , and / or (7) localization and positioning: precise reference points and landmarks that help in accurate vehicle localization on the map, etc.
[0080] Note while some assisted / autonomous driving systems may demand the use of HD map data, there are also assisted / autonomous driving systems and information systems that may be configured not to use HD map data (e.g., due to costs) . For example, the Society of Automotive Engineers (SAE) has defined six levels of driving automation, from Level 0 (no automation) to Level 5 (full automation) . For Level 0 (no automation) , the human driver may be responsible for all aspects of driving, and the system may provide warnings or momentary assistance but does not take control of the vehicle. Example features for SAE Level 0 may include automatic emergency braking, blind spot warnings, and lane departure warnings, etc. As such, SAE Level 0 may not specify using HD map data. For Level 1 (driver assistance) , the vehicle may assist with either steering or acceleration / deceleration (but may not perform both simultaneously) . The human driver is still responsible for most driving tasks and may need to be ready to take over at any time. Example features for SAE Level 1 may include adaptive cruise control or lane-keeping assistance (e.g., lane centering) , etc. For Level 2 (partial automation) , the vehicle may control both steering and acceleration / deceleration under certain conditions, but the human driver is requested to remain engaged and monitor the driving environment at all times. Example features for SAE Level 2 may include ADAS, adaptive cruise control and lane-keeping assistance at the same time, etc. For Level 3 (conditional automation) , the vehicle may perform all driving tasks under specific conditions, and the human driver may not be specified to monitor the environment but may need to be ready to take over when requested by the system. Example features for SAE Level 3 may include traffic jam chauffeur, where the vehicle is capable of handling driving in traffic jams without driver intervention. For Level 4 (high automation) , the vehicle is capable of handling all driving tasks within certain conditions or environments (geofenced areas) . The system may operate without human intervention but may specify a human driver outside its operational domain. Example features for SAE Level 4 may include local driverless taxi and pedals / steering, etc. For Level 5 (full automation) , the vehicle is capable of performing all driving tasks under all conditions, and does not specify the human driver at any time. Example features for SAE Level 5 may include fully autonomous vehicles with no steering wheel or pedals. In summary, SAE Level 0 may be defined as features to provide warnings and assistance. ADAS is usually SAE Level 1 and 2, while AD is considered SAE level 3 to 5. Aspects presented herein (described below) may apply to all levels of SAE, including SAE Level 0 (e.g., for speed warning) . For purposes of the present disclosure, a system or information system that is used in associated with SAE Level 0 to Level 5 may collectively be referred to as a “vehicle system, ” which may encompass the assisted driving and the autonomous driving.
[0081] To enable a vehicle to be capable of providing assisted driving and / or autonomous driving, the vehicle may be configured to use various machine learning (ML) and / or neural network (NN) frameworks. An ML / NN framework may refer to a set of tools, libraries, and / or software components that are configured to provide a structured way to design, build, and deploy ML / NN models and applications. These frameworks may be able to simplify the process of developing ML / NN algorithms and applications by providing a foundation of pre-built functions, algorithms, and utilities. They may typically include features for data preprocessing, model training, evaluation, and / or deployment, etc. ML / NN frameworks may come in various programming languages, and they may be configured to cater to different types of machine learning tasks, including supervised learning, unsupervised learning, and / or reinforcement learning, etc. An ML / NN model may refer to a mathematical representation of a real-world process or problem, created using ML / NN algorithms and techniques. These ML / NN models may be configured to make predictions, classify data, and / or solve specific tasks based on patterns and relationships learned from input data. A deep learning framework may refer to a specialized software library or toolset that provides specified components and abstractions for building, training, and deploying deep neural networks. Deep learning frameworks may be designed to facilitate the development of complex neural network models, especially deep neural networks with multiple layers. These frameworks may offer a wide range of pre-implemented layers, optimizers, loss functions, and other components, making it easier for researchers and developers to work with deep learning models.
[0082] FIG. 4 is a diagram 400 illustrating an example of a vehicle performing road object detection using different types of sensors in accordance with various aspects of the present disclosure. In some implementations, a vehicle system may be configured to perform road object detections using multiple types of sensors (and also one or more ML / NN models) . For purposes of the present disclosure, a road object or a traffic participant may refer to an object that is related to roads and driving, and is typically / commonly used / considered by the vehicle system in providing assisted driving or performing autonomous driving. In some examples, the road object / traffic participant may also be referred to as a traffic-related object. For example, a road object / traffic participant may be another vehicle, a pedestrian, a cyclist / bicycle, an animal, a traffic cone, a traffic sign, a traffic light, traffic, a traffic lane, a traffic line, a vulnerable road user (VRU) , an object that is within a threshold distance of the vehicle, and / or any objects that may typically present on the roads (e.g., on the driving paths of vehicles) , etc. On the other hand, a non-road object or a non-traffic participant (which may also be referred to as a non-traffic related object) may refer to an object that is not related to roads and driving, and is typically / commonly not used / considered by the vehicle system in providing assisted driving or performing autonomous driving. For example, a non-road object / non-traffic participant may be an object that is not within a threshold distance of the vehicle (e.g., a house on the side of the road, a mountain that is far away) , an object that is not typically presented on a driving path / road (an airplane, a fire hydrant, a tree, etc. ) , a structure that is typically not traversed by vehicles (e.g., a pedestrian bridge) , etc. An ML / NN model may be trained to identify whether an object is a road object or a non-road object.
[0083] For example, as shown by the diagram 400, a vehicle or a vehicle system (collectively as a “UE 402” ) may be configured to use different types of sensors, such as a set of cameras 404 and / or a set of radars 406 for detecting road objects. For purposes of the present disclosure, the term “radar” may broadly refer to a device / component that is capable of detecting at least the presence and / or the distance of a physical object. Examples of radar may include an RF radar, a sonar, an ultrasonic sensor, a light detection and ranging (lidar) , etc. In some implementations, the UE 402 may also use different MN / NN models for identifying different types of road objects. For example, a first ML / NN model may be trained / used to detect and track polylines from sensor output (s) (e.g., images captured by the camera (s) of the vehicle, point clouds generated from radar (s) / lidar (s) , etc. ) , while a second ML / NN model may be trained / used to detect and track objects in a three-dimensional (3D) space (e.g., to perform 3D object detection (3DOD) tasks) . Then, the outputs of different types of sensors (e.g., from the set of cameras 404 and the set of radars 406) may be processed and used by the ADAS or the autonomous driving system (e.g., for assisted / autonomous driving) . A point cloud may refer to a discrete set of data points in space, where these points may represent a 3D shape or object. In some implementations, each point position may be associated with a set of Cartesian coordinates (X, Y, Z) . Point clouds may be produced by radar (s) / lidar (s) by detecting multiple points on the external surfaces of objects.
[0084] For purposes of the present disclosure and in the context of assisted / autonomous driving, a vehicle that is capable of performing autonomous driving and / or certain amount of assisted driving may be referred to as an “ego vehicle” or simply “ego. ” For example, an “ego lane” may refer to a lane in which an ego vehicle itself is currently driving. As such, the term “ego” in such context may refer to the vehicle itself, and the term “ego lane” may imply that it is the lane where the (ego) vehicle is actively maneuvering and making decisions. Depending on the context, the term “ego lane” may be used for differentiating the lane occupied by the ego / autonomous vehicle from other lanes on the road.
[0085] Autonomous emergency steering (AES) may refer to a technology (or part of an ADAS) designed to enhance vehicle safety by automatically steering a vehicle to avoid a collision. AES works in tandem with sensors like camera (s) and radar (s) to detect potential hazards, such as obstacles, pedestrians, or other vehicles, and intervenes by steering the vehicle away from danger when the driver does not react in time. Example features of AES may include: (1) collision avoidance (e.g., AES actively steers the vehicle to avoid an accident, especially in situations where braking alone may not prevent a collision) , (2) sensor integration (e.g., AES may rely on multiple sensors to monitor the surroundings and determine the best course of action in real-time) , (3) driver assistance (e.g., AES may be configured to activate when it determines the driver does not have sufficient time to react to avoid a potential collision, and (4) complementary to other systems (e.g., AES may work works with other systems such as autonomous emergency braking (AEB) , enhancing overall safety by combining braking and steering inputs when specified) . AES may typically be used to prevent lane departure accidents, mitigate the severity of side or rear-end collisions, and avoid obstacles in emergencies.
[0086] An A-star (A*) algorithm is a pathfinding and graph traversal algorithm that may be used in various applications, including autonomous systems like AES. For example, in the context of AES, the A*algorithm may be used for determining the optimal steering path to avoid collisions or hazards in real-time, such as computing the best route for the vehicle to take when it needs to autonomously steer to avoid an obstacle or hazard. The A*algorithm may use a combination of two values / factors, which may collectively be referred to as a cost function. The first value / factor is g (n) , which may correspond the cost to reach a particular state (or node) from the starting point, and the value / factor one is h (n) , which may correspond to a heuristic estimate of the cost from that state to the goal (the final point of safety or obstacle avoidance) . The A*algorithm may be configured to balance these two values / factors to decide the most efficient steering path, ensuring that the vehicle avoids the hazard in the least time or distance.
[0087] The A*algorithm may be suitable for real-time applications such as AES (e.g., systems that demand immediate decision making) as the A*algorithm is computationally efficient in finding the best path by reducing unnecessary exploration of non-optimal routes. Thus, A*algorithm may be well-suited for real-time obstacle avoidance in dynamic environments. The A*algorithm may also be adapted for dynamic obstacles, meaning if the system detects a moving object (like another car) , the path may be recalculated on the fly to maintain safety.
[0088] FIG. 5 is a diagram 500 illustrating an example of an AES system that is configured to use an A*algorithm in accordance with various aspects of the present disclosure. At 510, after the AES function is triggered / activated at a UE 502 (which may be used for collectively referring to a vehicle UE, an AES system, a vehicle equipped with AES, an ADAS with AES, an on-board diagnostic (OBD) system, and / or an AES algorithm, etc. ) , the UE 502 may be configured to obtain object and lane marker information using at least one camera and / or at least one radar (which may include at least one Lidar) . The object may refer to physical objects in proximity to the UE 502, such as other vehicles, pedestrians, roads, traffic signs, structures, etc. For example, the UE 502 may use a camera to obtain both the object information and the lane marker information, and the radar / lidar may be used for obtaining the object information as well, such as described in connection with FIG. 4. The UE 502 may also fuse the object information and the lane maker information (e.g., to ensure the consistency between the two information) . For purposes of the present disclosure, information detected by a camera may be referred to as the vision information, and information detected by a radar may be referred to as the radar information. Depending on the context, the camera (s) and / or the radar (s) may collectively be referred to as sensor (s) . As such, the fusion of the vision information and the radar information may be referred as the “fused sensor information” and / or “fusion information. ”
[0089] At 512, based on the object information and lane marker information (or the fused sensor information) , the UE 502 may derive a set of path constraints. Path constraint (s) may refer to limitation (s) and condition (s) that a vehicle (e.g., the UE 502) are configured to adhere / follow when planning and executing its path. These constraints may be designed to ensure the safe and efficient operation on the road. Example path constraints may include lane boundaries (e.g., a vehicle is specified to stay within designated lanes, respecting lane markings and boundaries) , road geometry (e.g., curves, intersections, and road edges that define the permissible path of the vehicle) , traffic rules (e.g., the vehicle may also be specified to obey speed limits, traffic signals, signs, and regulations, such as stopping at red lights or yielding to pedestrians) , and / or obstacles (e.g., the vehicle is specified to avoid collisions with other obstacles, such as other vehicles, pedestrians, cyclists, and road debris) , etc. Example road constraint parameters may include initial / current state of the UE 502 (e.g., initial / current position (x0) , initial / current velocity (v0) , initial / current acceleration (a0) , initial / current jerk (j0) , etc. ) and / or the target state in the future (for example 6 seconds later) (e.g., target future position (x_e) , target future velocity (v_e) , target future acceleration (a_e) , target future jerk (j_e) , etc. ) . v_e, a_e, and j_e may be set to zero (0) if the UE 502 is parallel with the lane center.
[0090] At 514, using the derived set of path constraints, the UE 502 may create an initial path, estimate an ego path (i.e., an ego lane) , or create an escape path (e.g., referring to a path that is used when the estimated ego path is out of the set of path constraints) .
[0091] At 516, while the UE 502 (or the vehicle associated with the UE 502) is moving, the UE 502 may check whether there is a (potential) collision with one or more movable and static objects (e.g., a vehicle stopping on the path of the UE 502) . If there is no (potential) collision with a movable and static object, the UE 502 does not create an emergency maneuver for the vehicle. In other words, the UE 502 does not trigger the AES to intervene with the driving of the vehicle.
[0092] On the other hand, if the UE 502 detects there is a (potential) collision with one or more movable and static objects (referring to as “obstacle (s) ” hereafter) , the UE 502 may be configured to create a maneuver for the vehicle (e.g., the UE 502 triggers the AES and intervenes with the driving of the vehicle as discussed above) . For example, if the UE 502 is configured to use the A*algorithm for the AES, at 518, the UE 502 may add node (s) around the obstacle (s) . For purposes of the present disclosure, nodes may refer to a set of points created around object (s) and / or lane marker (s) with a safety gap. A simple global path may be generated when nodes are linked with each other. Aspects presented herein may be configured to use nodes for generating an initial global path, and then optimizing the global path based on a DWA algorithm (where nodes also are used as a cost function of DWA, such as the path direction of the UE 502 is set to be towards a next node) (discussed below) .
[0093] At, 520, based on the nodes, the UE 502 may use the A*algorithm to find a path (e.g., an emergency path for avoiding collision with the obstacle (s) ) for maneuvering the vehicle. At 522, the UE 502 may use quintic polynomial to generate a trajectory between nodes. This may refer to the process of smoothing and optimizing the path found by the A*algorithm. While A*may be suitable for finding feasible, collision-free paths, it may typically generate paths that are a series of straight-line segments between nodes (waypoints) , which may result in sharp turns that are impractical for vehicles. Thus, the quintic polynomial trajectory generation may smooth the path between nodes by generating continuous and differentiable curves, accounting for the physical constraints of the vehicle (like position, velocity, and acceleration) . Then, the UE 502 may maneuver the vehicle based on the path to avoid collision with the obstacle (s) , or output the path to the entity / module / function / system that is responsible for performing the AES or steering for the vehicle.
[0094] FIG. 6 is a diagram 600 illustrating an example of a vehicle performing AES in accordance with various aspects of the present disclosure. As shown at 610, after the UE 502 detects there is a (potential) collision with an obstacle 602 (e.g., a movable and static object) on its (original) ego path, the UE 502 may add node (s) around the obstacle 602, use the A*algorithm to find an emergency path (aset of nodes) , and use the quintic polynomial to smooth the emergency path between the set of nodes. Then, the UE 502 may maneuver the vehicle based on the emergency path to avoid collision with the obstacle 602, or output the emergency path to the entity / module / function / system that is responsible for performing the AES or steering for the vehicle.
[0095] While the currently solution of using the A*algorithm search method and the (two segments) quintic polynomial (e.g., to obtain a smooth path generated around the obstacle) to avoid collision has been effective, this solution is typically just available for avoiding a single obstacle. For example, as shown by a diagram 700 of FIG. 7, when there are two obstacles (afirst obstacle and a second obstacle) that are in proximity to each other, the emergency path created by the A*algorithm may just be able to avoid the first obstacle, but not the second obstacle. This is mainly due to that the current solution does not have a local routine planner. As such, the node selected by the UE 502 may be simple, and may lead to an invalid path (e.g., a collision with obstacle (s) after the first obstacle) . In some scenarios, this may also let the AES abort frequently when the environment surrounding the vehicle is complicated (e.g., when the traffic is dense) . For example, the AES may abort when it is unable to find a valid path.
[0096] Aspects presented herein may improve the overall performance of AES for vehicles by enabling the AES to use different algorithms. For example, aspects presented herein may optimize the AES path planner by fusing the A*algorithm and a dynamic window approach (DWA) algorithm. The A*algorithm may be used to generate a global path considering both obstacles and lane marker, and the DWA algorithm may be configured to use A*generated global node (s) as local target. Then, the cost function of the DWA algorithm may be used to balance avoid collision with obstacles and follow the nodes generated by the A*algorithm. In addition, the DWA algorithm may consider wheel angle rate as an input group, and use vehicle kinematic model to calculate predict path to get a path with best evaluation function. The DWA may also be configured to use a two-phase strategy to combine obstacle collision avoidance and keep heading of the vehicle the same with lane marker (e.g., to balance the obstacle avoidance and lane marker direction goal) . In other words, when several obstacles are in an ego path / lane, the A*algorithm may be implemented to provide a valid global path, and the DWA algorithm may be implemented to provide a more accurate path to avoid collision with obstacle.
[0097] FIG. 8 is a diagram 800 illustrating an example of an AES system that fuses an A*algorithm and a DWA algorithm in accordance with various aspects of the present disclosure. Aspects presented herein may enable a UE to create nodes around obstacle (s) , and connect direction (s) of nodes using an A*algorithm. Then, the UE may use a DWA algorithm as a local planner, which considers the wheel angle rate difference (just lateral control is considered in this case) , and uses two phases to balance obstacle avoidance and lane marker direction goal. For ease of illustration, the A*algorithm that is fused with the DWA algorithm may be referred to as the “new A*algorithm. ”
[0098] At 810, after the AES function is triggered / activated at a UE 802 (which may be used for collectively referring to a vehicle UE, an AES system, a vehicle equipped with AES, an ADAS with AES, an OBD system, and / or an AES algorithm, etc. ) , the UE 802 may be configured to obtain object and lane marker information using at least one camera and / or at least one radar (which may include at least one Lidar) . The object may refer to physical objects in proximity to the UE 802, such as other vehicles, pedestrians, roads, traffic signs, etc. For example, the UE 802 may use a camera to obtain both the object information and the lane marker information, and the radar / lidar may be used for obtaining the object information as well, such as described in connection with FIG. 4. The UE 802 may also fuse the object information and the lane maker information (e.g., to ensure the consistency between the two information) .
[0099] At 812, based on the object information and lane marker information (or the fused sensor information) , the UE 802 may derive a set of path constraints, such as described in connection with 512 of FIG. 5.
[0100] At 814, while the UE 802 (or the vehicle associated with the UE 802) is moving, the UE 802 may check whether there is a (potential) collision with a set of obstacles (e.g., a set of movable and static objects such as a vehicle stopping on the path of the UE 802) . If there is no (potential) collision with at least one obstacle, the UE 802 may be refrained from performing an action. In other words, the UE 802 does not trigger the AES to intervene with the driving of the vehicle. On the other hand, if the UE 802 detects there is a (potential) collision with a set of obstacles, the UE 802 may be configured to create a maneuver for the vehicle (e.g., the UE 802 triggers the AES and intervenes with the driving of the vehicle as discussed above) .
[0101] In one aspect of the present disclosure, as shown at 816, based on the detection of a (potential) collision with a set of obstacles, the UE 802 may be configured to first estimate a path to avoid the set of obstacles based on the A*algorithm, such as described in connection with 518, 520, and 522 of FIG. 5. For purposes of illustration, this path may be referred to as a “global path, ” which may include a set of “global nodes. ” For example, at 818, the UE 802 may be configured to add nodes around the set of obstacles (e.g., assuming there are at least two obstacles: the first obstacle and the second obstacle) . Besides associating each node with the position, the velocity, and / or the acceleration of the UE 802 or the vehicle associated with the UE 802, the UE 802 may also add object ID information to each node, where different nodes may be assigned with different types according to different object classes (discussed below) . Then, at 820, the UE 802 may use the A*algorithm to find a global path, such as by connecting (neighbor) nodes associated with the set of obstacles as discussed in connection with FIG. 6.
[0102] At 822, after the UE 802 obtains the global path (that includes a set of global nodes) , the UE 802 may be configured to use a DWA algorithm (discussed below in details) to get a path based on considering both the global path and the collision avoidance. For purposes of illustration, this path may be referred to as a “local path. ” For example, at 824, the UE 802 may be configured to use one or more nodes from the A*algorithm (e.g., using one or more global nodes) as local target (s) . For example, a local target may be based on the information associated with a next / subsequent node, such as the direction, the position, etc. As nodes are created by safety margin with obstacle (s) , they could be used as a (good) target for the cost function of the DWA algorithm. At 826, the UE 802 may just consider its lateral direction to calculate dynamic windows for the DWA algorithm, and select different wheel angles or heading angle differences to calculate the local path according to the heading angle and its longitudinal speed. At 828, the UE 802 may select a local path (from multiple local paths associated with different wheel angles or heading angle differences) with best cost as the final local path, where the cost function of the DWA algorithm may considers both the minimum global path difference (e.g., a difference between a local path and a global path) and the obstacle distance (e.g., a distance between the obstacle and the vehicle when the vehicle is travelling on the local path) . Then, the UE 802 may output the selected local path, such as transmitting an indication of the selected local path to an AES system, or maneuvering the UE 802 (or the associated vehicle) to the selected local path to avoid the set of obstacles.
[0103] FIG. 9 is a diagram 900 illustrating an example of a UE selecting a global path based on the A*algorithm in accordance with various aspects of the present disclosure. As discussed in connection with FIG. 5, the A* (A-star) algorithm is a graph traversal algorithm and pathfinding algorithm that may be used to find the most optimal route from a starting point to a destination. For example, the A*algorithm may be used by a vehicle (e.g., the UE 802) for path planning (e.g., it helps the vehicle to determine the optimal path to follow, avoiding obstacles and minimizing travel time or distance) , navigation in complex environments (e.g., A*algorithm may guide a vehicle through complex urban areas, taking into account road structures, traffic, and other environmental factors, etc. ) , and dynamic adjustments (e.g., as conditions on the road change (like moving obstacles or traffic) , the A*algorithm may re-plan routes in real time to ensure efficient and safe navigation) .
[0104] In one example, the A*algorithm may work by maintaining a priority queue of nodes (potential paths) , and scoring them based on two key components: (1) g (x) : the actual cost of reaching the current node, and (2) h (x) : the heuristic estimate of the cost to reach the goal from the current node, typically based on the straight-line distance (e.g., a Euclidean distance) or other metrics. The total score for each node f (x) may be calculated based on f (x) = g (x) + h (x) , and the A*algorithm is aimed to minimize this value to find the optimal path.
[0105] As an illustration, at 902, the A*algorithm (or the UE 802 configured to use the A*algorithm) may be started with a set of nodes with a start node, where this set of nodes may be referred to as an “open set of nodes” or just an “open set. ” In other words, an open set may be a group that includes multiple / all possible “next / subsequent node (s) . ” When these possible next / subsequent node (s) are evaluated with the cost function, the possible next / subsequent node with the lowest score in the open set may be selected as the actual next / subsequent node to be used.
[0106] At 904, start from the start node, the A*algorithm may set the current node using a node in the open set that has a lowest final cost (denoted by f_score or f (x) ) , e.g., current node = the node in the open set having the lowest f_score value.
[0107] At 906, the A*algorithm may determine whether the current node is within an end zone, where the end zone may refer to a goal state or a final destination which the A*algorithm is trying to reach. If the current node within the end zone, then the search is done. However, if the current node is not within the end zone, at 908, the A*algorithm may remove the current node from the open set, and add this node to a closed set of nodes (which may be referred to as the “closed set” ) .
[0108] At 910, the A*algorithm may go through all the neighbor nodes, where the connection between nodes (e.g., from the current node to neighbor nodes) may be defined in a specific solution.
[0109] At 912, the A*algorithm may determine whether a neighbor node (or each of the neighbor nodes) is collision free path and valid spline. The “collision-free path” may refer to a route from the start point to the goal (end zone) that does not intersect with any obstacles in the environment, and the “valid spline” may refer to a continuous, smooth, and feasible curve that connects the points along the optimal path found by the A*algorithm.
[0110] At 914, if a neighbor node is collision free path and valid spline, the A*algorithm may add the neighbor node to the open set.
[0111] At 916, the A*algorithm may calculate a final cost (f_score) , which may be related to a jerk value of spline and collision with obstacle / lane (e.g., based on f (x) = g (x) +h(x) ) . Then, the A*algorithm may return to step 904 and repeat the process until the current node is within the end zone.
[0112] FIG. 10 is a diagram 1000 illustrating an example of creating nodes around obstacle (s) in accordance with various aspects of the present disclosure. As discussed in connection with 816 of FIGs. 8 and 9, the UE 802 may be configured to estimate a path to avoid the set of obstacles based on a (new) A*algorithm, which may include adding nodes around a set of obstacles. Aspects presented herein provide an example of how nodes are created.
[0113] At 1002, after detecting a set of obstacles, the UE 802 may create nodes around obstacle (s) , where each corner of an obstacle in the set of obstacles may be created with a node if it is within the ego lane (e.g., there may be a maximum of 4 nodes per obstacle) . Each node may be associated / assigned with a set of attributes, which may include time, lateral position, velocity (v) , jerk (k) , and / or object ID, etc. In the context of AES, jerk may refer to the rate of change of acceleration over time. It may be the derivative of acceleration with respect to time, and is measured in units of m / s3.
[0114] In addition, each node may be associated / assigned with a node type, such that different nodes may be defined for the maneuver generation. In one example, a first node type (Type 1) may be a standard node (e.g., with fixed position and velocity) , which may be placed on every obstacle / object to enable the UE 802 to create a path that is collision free from all obstacles / objects. A second node type (Type 2) may be an open node (e.g., with fixed position but free velocity) , which may be placed just on a threat that the initial path is colliding with. Depending on implementations, the UE 802 may be configured to assign a maximum of four open nodes (Type 2 nodes) , such as one in each corner of an obstacle, with a small margin. A start node (e.g., as shown by FIG. 5) may be an open node (Type 2 node) . A third node type may be an end node, which may be a free node in y, and may be fixed in time but lateral position and velocity within tolerances. For example, an end node may be fixed to the time at the end (e.g., configured to be 6 seconds) .
[0115] At 1004, based on the nodes created and their associated attributes, the UE 802 may apply the A*algorithm to connect the nodes. For example, as discussed in connection with FIG. 9, the UE 802 (or the A*algorithm) may iterate over the created nodes, calculate the heuristic cost for nodes, search neighbor nodes using multi-obstacle method (e.g., if a node’s time is ahead and is a different object, connect with the node, otherwise connect to the end node) , and calculate the true cost of the node. The UE 802 may repeat this process until the search is done (e.g., until the current node is within the end zone) .
[0116] FIG. 11A is a diagram 1100A illustrating an example of a node connection route for an A*algorithm (or a search algorithm) in accordance with various aspects of the present disclosure. Typically, an A*algorithm (in the context of AES) may be configured to start from a start node, and the start node may connect to other nodes except the end node. For example, as shown at 1102, the start node may be configured to connect to a neighbor node, which may be either a standard (Type 1) node or an open (Type 2) node as discussed in connection with FIG. 10. Then, as shown at 1104, the neighbor node may be configured to connect to the end node. As such, there may be three nodes in total (e.g., a start node, a neighbor (Type 1 / Type 2) node, and an end node) .
[0117] FIG. 11B is a diagram 1100B illustrating an example of a node connection route for a new A*algorithm (or a search algorithm) in accordance with various aspects of the present disclosure. For the (new) A*algorithm (in the context of AES) discussed in connection with FIGs. 8 to 10, the start node may also connect to other nodes except the end node. For example, as shown at 1106, the start node may be configured to connect to a neighbor node, which may be either a standard (Type 1) node or an open (Type 2) node as discussed in connection with FIG. 10. As shown at 1108, if the neighbor node is a standard (Type 1) node, the neighbor node may be connected to the end node. On the other hand, as shown at 1110, if the neighbor node is an open (Type 2) node, the neighbor node may be connected to the end node or node (s) with time ahead and with a different object ID (e.g., to account for a second obstacle that is associated with a different object ID than a first obstacle) .
[0118] FIG. 12 is a diagram 1200 illustrating an example of nodes creation based on the new A*algorithm in accordance with various aspects of the present disclosure. The UE 802 may detect a first obstacle 1202 and a second obstacle 1204 on the ego lane of the UE 802. As shown at 1210, the UE 802 may create two nodes around the first obstacle 1202 (e.g., at each corner of the first obstacle 1202 that is within the ego lane) . In addition, the UE 802 may associate each of these two nodes with a set of attributes, which may include an object ID (e.g., ID 1 for the first obstacle 1202) . Each node may be a standard (Type 1) node or an open (Type 2) node as discussed in connection with FIG. 10. Similarly, as shown at 1212, the UE 802 may create two nodes around the second obstacle 1204 (e.g., at each corner of the second obstacle 1204 that is within the ego lane) , and associate each of these two nodes with a set of attributes including the object ID (e.g., ID 2 for the second obstacle 1204) . As shown at 1214 (and discussed in connection with 1110 of FIG. 11B) , if a neighbor node is an open (Type 2) node, the neighbor node may be connected to node (s) with time ahead and with a different object ID (e.g., to account for a second obstacle that is associated with a different object ID than a first obstacle) instead of connected to an end node. Also, nodes of the obstacle (s) may be connected before the end node.
[0119] As discussed in connection with FIG. 8, aspects presented herein may use the A*algorithm for the global node selection process (e.g., for selecting the global path) , and then use the DWA algorithm to obtain a local path based on considering both the global path and the collision avoidance. For example, the DWA algorithm may use each node as a local target, which may provide a good performance to avoid collision with obstacle (s) , and avoid AES abort unexpected.
[0120] A dynamic window approach (DWA) algorithm may be capable of performing real-time obstacle avoidance and route planning for a vehicle by navigating the vehicle towards a goal while avoiding obstacles in dynamic environments by considering the motion constraints of the vehicle. Features / concepts of the DWA algorithm may include: (1) velocity space (e.g., DWA may evaluate possible velocities (both linear and angular) a vehicle may take within a given window of time, where this space may be constrained by the kinematic and dynamic limits of the vehicle (such as the maximum speed, acceleration, and deceleration, etc. ) ; (2) dynamic window (e.g., which may refer to a set of feasible velocities that the vehicle may achieve within a short time frame, considering both its current velocity and physical limits, and this window may be continuously updated as the vehicle moves; (3) trajectory simulation (e.g., for each velocity in the dynamic window, the DWA may simulate possible trajectories (paths) the vehicle may follow if it were to move at that velocity for a short period of time) ; (4) cost function (e.g., the DWA may evaluate each possible trajectory based on a cost function that typically takes into account a goal distance, an obstacle distance, a speed, and / or a heading alignment) ; and / or (5) optimal trajectory (e.g., based on the cost function, DWA may select a trajectory that best balances reaching the goal, avoiding obstacles, and staying within the dynamic constraints of the vehicle.
[0121] An AES path behavior may have two (2) phases during approach to one obstacle, where the DWA algorithm may be configured to have different strategies for the two phases. For a first phase (Phase 1) , the goal is to let the vehicle heading to a target node (e.g., node (s) created from the (new) A*algorithm, which may be referred to as the “A*node (s) ” ) , and avoiding collision with the obstacle. When the lateral position (e.g., the front tire position) of the vehicle is bigger than the lateral position of the obstacle, the DWA algorithm may switch to a second phase (Phase 2) . For the second phase, the goal is to let the lateral position of the vehicle to be the same with an A*node, and the lateral velocity to be zero 0 (or the heading angle to be parallel with the lane marker (s) ) .
[0122] FIG. 13 is a diagram 1300 illustrating an example DWA process / algorithm in accordance with various aspects of the present disclosure. As shown at 1302, the DWA algorithm (or the UE 802) may be configured to assume that the vehicle speed is constant, such that DWA algorithm may just focus on the lateral control of the vehicle. In addition, the wheel angle rate of the vehicle may be limited by a threshold, which may be based on the vehicle properties.
[0123] At 1304, the DWA algorithm may select different wheel angle rates as inputs, and use a vehicle bicycle model or a vehicle kinematic model to predict the path (e.g., the local path) associated with each wheel angle rate. A vehicle bicycle model or a bicycle model may refer to a simplified mathematical model that may be used to describe the kinematics and dynamics of a four-wheeled vehicle. For example, instead of modeling all four wheels, the vehicle may be represented as having two main wheels: one at the front and one at the rear. The front wheel may represent the combined effect of the two front wheels, particularly steering, and the rear wheel may represent the combined motion of the two rear wheels. The front wheel is responsible for steering the vehicle. Thus, when the front wheel turns, it alters the vehicle’s direction of travel, simulating how real vehicles steer by changing the orientation of their front wheels. In certain models, the rear wheel may be configured to be aligned with the vehicle’s longitudinal axis and responsible for propulsion. This may reflect how a real vehicle’s rear wheels follow the front wheels without steering. An examples kinematic mode of the vehicle may be represented based on:
[0124] where may represent the difference in X position of the vehicle, may represent the difference in Y position of the vehicle, V may represent the velocity of the vehicle, ψ may represent the heading angle of the vehicle, may represent the yaw rate or the heading angle difference, L may represent a circular movement radius, and δf may represent the front wheel angle of the vehicle. Based on the kinematic mode, the DWA algorithm may calculate the position (e.g., X, Y) of the vehicle at different time points.
[0125] At 1306, based on the calculated position of the vehicle (for each wheel angle rate) , the DWA algorithm may determine whether the front wheel position (e.g., the lateral position) of the vehicle passes the lateral position of the obstacle. In other words, the DWA algorithm may determine whether the front wheel position of the vehicle reaches outside of the obstacle.
[0126] As shown at 1308, if the front wheel position of the vehicle does not pass the lateral position of the obstacle, the DWA algorithm may be configured to apply / follow the first phase (Phase 1) , which may include using a first evaluation function (G) : G = a*(path end / final point heading angle –angle from the end point to a global path point heading) + b* (predict / DWA path to obstacle distance) , where a and b are factors.
[0127] As shown at 1310, if the front wheel position of the vehicle passes the lateral position of the obstacle, the DWA algorithm may be configured to apply / follow the second phase (Phase 2) , which may include using a second evaluation function (G) : G = a* (path end point heading –lane marker heading) + b* (DWA path to obstacle distance) + c* (DWA path to lane marker distance) + d* (lateral distance from end point to global node) , where a, b, c, and d are factors.
[0128] FIG. 14A is a diagram 1400A illustrating an example of the first phase (Phase 1) for the DWA algorithm in accordance with various aspects of the present disclosure. As shown at 1402, for the first phase (Phase 1) of the DWA algorithm, the goal of the DWA algorithm is to let the vehicle heading to a target node (e.g., an A*node) , and avoiding collision with the obstacle.
[0129] FIG. 14B is a diagram 1400B illustrating an example of the second phase (Phase 2) for the DWA algorithm in accordance with various aspects of the present disclosure. As shown at 1404, when the lateral position (e.g., the front tire position) of the vehicle is bigger than the lateral position of the obstacle, the DWA algorithm may switch to the second phase (Phase 2) . For the second phase, the goal is to let the lateral position of the vehicle to be the same with an A*node, the lateral velocity to be zero 0 (or the heading angle to be parallel with the lane marker (s) ) , and avoiding collision with the obstacle.
[0130] FIG. 15 is a diagram 1500 illustrating an example AES path generated based on the new A*algorithm in accordance with various aspects of the present disclosure. Based on fusing the A*algorithm with the DWA algorithm (e.g., using the A*algorithm for creating global path and the DWA algorithm for creating local path) , the UE 802 (e.g., the AES system) may enable the vehicle to avoid obstacles that are in proximity to each other. As shown at 1502, the emergency path created by the new A*algorithm may be able to avoid the first obstacle and the second obstacle. The new A*algorithm described herein also prevent the AES from aborting frequently when the environment surrounding the vehicle is complicated (e.g., when the traffic is dense) .
[0131] FIG. 16 is a flowchart 1600 of a method of wireless communication at a user equipment (UE) . The method may be performed by a UE (e.g., the UE 104, 402, 502, 802; the apparatus 1704) . The method may enable the UE to fuse an A*algorithm and a DWA algorithm for an AES system, thereby enabling the AES system to avoid multiple obstacles that are in proximity to each other with a higher precision and success rate.
[0132] At 1602, the UE may identify there is a potential collision with a set of objects on a travelling path of the UE, such as described in connection with FIG. 8. For example, at 810, after the AES function is triggered / activated at a UE 802 (which may be used for collectively referring to a vehicle UE, an AES system, a vehicle equipped with AES, an ADAS with AES, an OBD system, and / or an AES algorithm, etc. ) , the UE 802 may be configured to obtain object and lane marker information using at least one camera and / or at least one radar (which may include at least one Lidar) . At 812, based on the object information and lane marker information (or the fused sensor information) , the UE 802 may derive a set of path constraints. At 814, while the UE 802 (or the vehicle associated with the UE 802) is moving, the UE 802 may check whether there is a (potential) collision with a set of obstacles (e.g., a set of movable and static objects such as a vehicle stopping on the path of the UE 802) . If the UE 802 detects there is a (potential) collision with a set of obstacles, the UE 802 may be configured to create a maneuver for the vehicle. The identification of the potential collision may be performed by, e.g., the AES component 198, the camera 1732, the ECU 1734, the one or more sensors 1718, the transceiver (s) 1722, the cellular baseband processor (s) 1724, and / or the application processor (s) 1706 of the apparatus 1704 in FIG. 17.
[0133] At 1604, the UE may determine, based on identification of the potential collision with the set of objects, a first path that includes a set of nodes for avoiding the set of objects using a first algorithm, such as described in connection with FIGs. 8-10, 11A, and 11B. For example, as discussed in connection with 816 of FIG. 8, based on the detection of a (potential) collision with a set of obstacles, the UE 802 may be configured to first estimate a path to avoid the set of obstacles based on the A* algorithm. For example, at 818, the UE 802 may be configured to add nodes around the set of obstacles. Then, at 820, the UE 802 may use the A*algorithm to find a global path, such as by connecting (neighbor) nodes associated with the set of obstacles. The determination of the first path may be performed by, e.g., the AES component 198, the camera 1732, the ECU 1734, the one or more sensors 1718, the transceiver (s) 1722, the cellular baseband processor (s) 1724, and / or the application processor (s) 1706 of the apparatus 1704 in FIG. 17.
[0134] At 1606, the UE may determine, based on using at least one node in the set of nodes as a target, a second path for avoiding at least one object in the set of objects using a second algorithm, such as described in connection with FIGs. 8, 11A, 11B, 12, 13, 14A, and 14B. For example, as discussed in connection with 822 of FIG. 8, after the UE 802 obtains the global path (that includes a set of global nodes) , the UE 802 may be configured to use a DWA algorithm to get a path based on considering both the global path and the collision avoidance. For example, at 824, the UE 802 may be configured to use one or more nodes from the A*algorithm (e.g., using one or more global nodes) as local target. At 826, the UE 802 may just consider its lateral direction to calculate dynamic windows for the DWA algorithm, and select different wheel angles or heading angle differences to calculate the local path according to the heading angle and its longitudinal speed. At 828, the UE 802 may select a local path (from multiple local paths associated with different wheel angles or heading angle differences) with best cost as the final local path, where the cost function of the DWA algorithm may considers both the minimum global path difference (e.g., a difference between a local path and a global path) and the obstacle distance (e.g., a distance between the obstacle and the vehicle when the vehicle is travelling on the local path) . The determination of the second path may be performed by, e.g., the AES component 198, the camera 1732, the ECU 1734, the one or more sensors 1718, the transceiver (s) 1722, the cellular baseband processor (s) 1724, and / or the application processor (s) 1706 of the apparatus 1704 in FIG. 17.
[0135] At 1608, the UE may output an indication to switch to the second path for avoiding the at least one object in the set of objects, such as described in connection with FIG. 8. For example, at 830 of FIG. 8, the UE 802 may output the selected local path, such as transmitting an indication of the selected local path to an AES system, or maneuvering the UE 802 (or the associated vehicle) to the selected local path to avoid the set of obstacles. The output of the indication may be performed by, e.g., the AES component 198, the camera 1732, the ECU 1734, the one or more sensors 1718, the transceiver (s) 1722, the cellular baseband processor (s) 1724, and / or the application processor (s) 1706 of the apparatus 1704 in FIG. 17.
[0136] In one example, the first algorithm corresponds to an A-star (A*) algorithm and the second algorithm corresponds to a dynamic window approach (DWA) algorithm.
[0137] In another example, to determine the first path that includes the set of nodes for avoiding the set of objects using the first algorithm, the UE may be configured to identify one or more nodes around each object of the set of objects, determine a node type for each identified node, where the node type includes a standard node, an open node, or an end node, and connect multiple identified nodes based on their node types to obtain the set of nodes for the first path. In some implementations, each identified node is associated with a set of attributes that includes one or more of: a position of the UE at the node, a velocity of the UE at the node, an acceleration of the UE at the node, a jerk of the UE at the node, or an object identifier (ID) associated with a corresponding object, where the multiple identified nodes are connected based on their corresponding set of attributes.
[0138] In another example, to determine, based on using the at least one node in the set of nodes as the target, the second path for avoiding the at least one object in the set of objects using the second algorithm, the UE may be configured to use a second node in the set of nodes as the target when the UE is at a first node in the set of nodes, determine whether a lateral position of the UE is able to pass a lateral position of the at least one object, and generate the second path based on (1) a heading angle towards the at least one object and (2) a distance to the at least one object if the lateral position of the UE is able to pass the lateral position of the at least one object, or based on (1) the heading angle towards the at least one object, (2) a first distance to the at least one object, (3) a second distance to at least one lane marker, and (4) a lateral distance from a predicted end point to the second node if the lateral position of the UE is unable to pass the lateral position of the at least one object. In some implementations, the second node is subsequent to the first node in the set of nodes. In some implementations, the lateral position of the UE corresponds to a set of front wheel or tire positions of the UE.
[0139] In another example, the UE may obtain information related to the set of objects and lane marker from at least one camera or radar, where the identification of the potential collision with the set of objects is based on the obtained information.
[0140] In another example, the set of objects corresponds to a set of movable and static objects.
[0141] In another example, to determine the first path that includes the set of nodes for avoiding the set of objects using the first algorithm, the UE may be configured to calculate the first path that includes the set of nodes for avoiding the set of objects using the first algorithm.
[0142] In another example, to determining the second path for avoiding the at least one object in the set of objects using the second algorithm, the UE may be configured to calculate the second path for avoiding the at least one object in the set of objects using the second algorithm.
[0143] In another example, to output the indication to switch to the second path, the UE may be configured to at least one of: transmit an indication of the second path to an autonomous emergency steering (AES) system; or maneuver the UE to the second path.
[0144] FIG. 17 is a diagram 1700 illustrating an example of a hardware implementation for an apparatus 1704. The apparatus 1704 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 1704 may include at least one cellular baseband processor 1724 (also referred to as a modem) coupled to one or more transceivers 1722 (e.g., cellular RF transceiver) . The cellular baseband processor (s) 1724 may include at least one on-chip memory 1724'. In some aspects, the apparatus 1704 may further include one or more subscriber identity modules (SIM) cards 1720 and at least one application processor 1706 coupled to a secure digital (SD) card 1708 and a screen 1710. The application processor (s) 1706 may include on-chip memory 1706'. In some aspects, the apparatus 1704 may further include a Bluetooth module 1712, a WLAN module 1714, an ultrawide band (UWB) module 1738, an SPS module 1716 (e.g., GNSS module) , one or more sensors 1718 (e.g., barometric pressure sensor / altimeter; motion sensor such as inertial measurement unit (IMU) , gyroscope, and / or accelerometer (s) ; light detection and ranging (LIDAR) , radio assisted detection and ranging (RADAR) , sound navigation and ranging (SONAR) , magnetometer, audio and / or other technologies used for positioning) , additional memory modules 1726, a power supply 1730, a camera 1732, and / or an electronic control unit (ECU) 1734. The Bluetooth module 1712, the UWB module 1738, the WLAN module 1714, and the SPS module 1716 may include an on-chip transceiver (TRX) (or in some cases, just a receiver (RX) ) . The Bluetooth module 1712, the WLAN module 1714, and the SPS module 1716 may include their own dedicated antennas and / or utilize the antennas 1780 for communication. The cellular baseband processor (s) 1724 communicates through the transceiver (s) 1722 via one or more antennas 1780 with the UE 104 and / or with an RU associated with a network entity 1702. The cellular baseband processor (s) 1724 and the application processor (s) 1706 may each include a computer-readable medium / memory 1724', 1706', respectively. The additional memory modules 1726 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 1724', 1706', 1726 may be non-transitory. The cellular baseband processor (s) 1724 and the application processor (s) 1706 are each responsible for general processing, including the execution of software stored on the computer-readable medium / memory. The software, when executed by the cellular baseband processor (s) 1724 / application processor (s) 1706, causes the cellular baseband processor (s) 1724 / application processor (s) 1706 to perform the various functions described supra. The cellular baseband processor (s) 1724 and the application processor (s) 1706 are configured to perform the various functions described supra based at least in part of the information stored in the memory. That is, the cellular baseband processor (s) 1724 and the application processor (s) 1706 may be configured to perform a first subset of the various functions described supra without information stored in the memory and may be configured to perform a second subset of the various functions described supra based on the information stored in the memory. The computer-readable medium / memory may also be used for storing data that is manipulated by the cellular baseband processor (s) 1724 / application processor (s) 1706 when executing software. The cellular baseband processor (s) 1724 / application processor (s) 1706 may be a component of the UE 350 and may include the at least one 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 apparatus 1704 may be at least one processor chip (modem and / or application) and include just the cellular baseband processor (s) 1724 and / or the application processor (s) 1706, and in another configuration, the apparatus 1704 may be the entire UE (e.g., see UE 350 of FIG. 3) and include the additional modules of the apparatus 1704.
[0145] As discussed supra, the AES component 198 may be configured to identify there is a potential collision with a set of objects on a travelling path of the UE. The AES component 198 may also be configured to determine, based on identification of the potential collision with the set of objects, a first path that includes a set of nodes for avoiding the set of objects using a first algorithm. The AES component 198 may also be configured to determine, based on using at least one node in the set of nodes as a target, a second path for avoiding at least one object in the set of objects using a second algorithm. The AES component 198 may also be configured to output an indication to switch to the second path for avoiding the at least one object in the set of objects. The AES component 198 may be within the cellular baseband processor (s) 1724, the application processor (s) 1706, or both the cellular baseband processor (s) 1724 and the application processor (s) 1706. The AES component 198 may be one or more hardware components specifically configured to carry out the stated processes / algorithm, implemented by one or more processors configured to perform the stated processes / algorithm, stored within a computer-readable medium for implementation by one or more processors, or some combination thereof. When multiple processors are implemented, the multiple processors may perform the stated processes / algorithm individually or in combination. As shown, the apparatus 1704 may include a variety of components configured for various functions. In one configuration, the apparatus 1704, and in particular the cellular baseband processor (s) 1724 and / or the application processor (s) 1706, may include means for identifying there is a potential collision with a set of objects on a travelling path of the UE. The apparatus 1704 may further include means for determining, based on identification of the potential collision with the set of objects, a first path that includes a set of nodes for avoiding the set of objects using a first algorithm. The apparatus 1704 may further include means for determining, based on using at least one node in the set of nodes as a target, a second path for avoiding at least one object in the set of objects using a second algorithm. The apparatus 1704 may further include means for outputting an indication to switch to the second path for avoiding the at least one object in the set of objects.
[0146] In one configuration, the first algorithm corresponds to an A*algorithm and the second algorithm corresponds to a DWA algorithm.
[0147] In another configuration, the means for determining the first path that includes the set of nodes for avoiding the set of objects using the first algorithm may include configuring the apparatus 1704 to identify one or more nodes around each object of the set of objects, determine a node type for each identified node, where the node type includes a standard node, an open node, or an end node, and connect multiple identified nodes based on their node types to obtain the set of nodes for the first path. In some implementations, each identified node is associated with a set of attributes that includes one or more of: a position of the UE at the node, a velocity of the UE at the node, an acceleration of the UE at the node, a jerk of the UE at the node, or an object ID associated with a corresponding object, where the multiple identified nodes are connected based on their corresponding set of attributes.
[0148] In another configuration, the means for determining, based on using the at least one node in the set of nodes as the target, the second path for avoiding the at least one object in the set of objects using the second algorithm may include configuring the apparatus 1704 to use a second node in the set of nodes as the target when the UE is at a first node in the set of nodes, determine whether a lateral position of the UE is able to pass a lateral position of the at least one object, and generate the second path based on (1) a heading angle towards the at least one object and (2) a distance to the at least one object if the lateral position of the UE is able to pass the lateral position of the at least one object, or based on (1) the heading angle towards the at least one object, (2) a first distance to the at least one object, (3) a second distance to at least one lane marker, and (4) a lateral distance from a predicted end point to the second node if the lateral position of the UE is unable to pass the lateral position of the at least one object. In some implementations, the second node is subsequent to the first node in the set of nodes. In some implementations, the lateral position of the UE corresponds to a set of front wheel or tire positions of the UE.
[0149] In another configuration, the apparatus 1704 may include means for obtaining information related to the set of objects and lane marker from at least one camera or radar, where the identification of the potential collision with the set of objects is based on the obtained information.
[0150] In another configuration, the set of objects corresponds to a set of movable and static objects.
[0151] In another configuration, the means for determining the first path that includes the set of nodes for avoiding the set of objects using the first algorithm may include configuring the apparatus 1704 to calculate the first path that includes the set of nodes for avoiding the set of objects using the first algorithm.
[0152] In another configuration, the means for determining the second path for avoiding the at least one object in the set of objects using the second algorithm may include configuring the apparatus 1704 to calculate the second path for avoiding the at least one object in the set of objects using the second algorithm.
[0153] In another configuration, the means for outputting the indication to switch to the second path may include configuring the apparatus 1704 to at least one of: transmit an indication of the second path to an AES system; or maneuver the UE to the second path.
[0154] The means may be the AES component 198 of the apparatus 1704 configured to perform the functions recited by the means. As described supra, the apparatus 1704 may include the TX processor 368, the RX processor 356, and the controller / processor 359. As such, in one configuration, the means may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions recited by the means.
[0155] It is understood that the specific order or hierarchy of blocks in the processes / flowcharts disclosed is an illustration of example approaches. Based upon design preferences, it is understood that the specific order or hierarchy of blocks in the processes / flowcharts may be rearranged. Further, some blocks may be combined or omitted. The accompanying method claims present elements of the various blocks in a sample order, and are not limited to the specific order or hierarchy presented.
[0156] The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not limited to the aspects described herein, but are to be accorded the full scope consistent with the language claims. Reference to an element in the singular does not mean “one and only one” unless specifically so stated, but rather “one or more. ” Terms such as “if, ” “when, ” and “while” do not imply an immediate temporal relationship or reaction. That is, these phrases, e.g., “when, ” do not imply an immediate action in response to or during the occurrence of an action, but simply imply that if a condition is met then an action will occur, but without requiring a specific or immediate time constraint for the action to occur. The word “exemplary” is used herein to mean “serving as an example, instance, or illustration. ” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects. Unless specifically stated otherwise, 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, and may include multiples of A, multiples of B, or multiples of C. Specifically, combinations such as “at least one of A, B, or C, ” “one or more of A, B, or C, ” “at least one of A, B, and C, ” “one or more of A, B, and C, ” and “A, B, C, or any combination thereof” may be A only, B only, C only, A and B, A and C, B and C, or A and B and C, where any such combinations may contain one or more member or members of A, B, or C. Sets should be interpreted as a set of elements where the elements number one or more. Accordingly, for a set of X, X would include one or more elements. When at least one processor is configured to perform a set of functions, the at least one processor, individually or in any combination, is configured to perform the set of functions. Accordingly, each processor of the at least one processor may be configured to perform a particular subset of the set of functions, where the subset is the full set, a proper subset of the set, or an empty subset of the set. A processor may be referred to as processor circuitry. A memory / memory module may be referred to as memory circuitry. If a first apparatus receives data from or transmits data to a second apparatus, the data may be received / transmitted directly between the first and second apparatuses, or indirectly between the first and second apparatuses through a set of apparatuses. A device configured to “output” data or “provide” data, such as a transmission, signal, or message, may transmit the data, for example with a transceiver, or may send the data to a device that transmits the data. A device configured to “obtain” data, such as a transmission, signal, or message, may receive, for example with a transceiver, or may obtain the data from a device that receives the data. Information stored in a memory includes instructions and / or data. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are encompassed by the claims. Moreover, nothing disclosed herein is dedicated to the public regardless of whether such disclosure is explicitly recited in the claims. The words “module, ” “mechanism, ” “element, ” “device, ” and the like may not be a substitute for the word “means. ” As such, no claim element is to be construed as a means plus function unless the element is expressly recited using the phrase “means for. ”
[0157] As used herein, the phrase “based on” shall not be construed as a reference to a closed set of information, one or more conditions, one or more factors, or the like. In other words, the phrase “based on A” (where “A” may be information, a condition, a factor, or the like) shall be construed as “based at least on A” unless specifically recited differently.
[0158] The following aspects are illustrative only and may be combined with other aspects or teachings described herein, without limitation.
[0159] Aspect 1 is a method at a user equipment (UE) , comprising: identifying there is a potential collision with a set of objects on a travelling path of the UE; determining, based on identification of the potential collision with the set of objects, a first path that includes a set of nodes for avoiding the set of objects using a first algorithm; determining, based on using at least one node in the set of nodes as a target, a second path for avoiding at least one object in the set of objects using a second algorithm; and outputting an indication to switch to the second path for avoiding the at least one object in the set of objects.
[0160] Aspect 2 is the method of aspect 1, wherein the first algorithm corresponds to an A-star (A*) algorithm and the second algorithm corresponds to a dynamic window approach (DWA) algorithm.
[0161] Aspect 3 is the method of aspect 1 or aspect 2, wherein determining the first path that includes the set of nodes for avoiding the set of objects using the first algorithm comprises: identifying one or more nodes around each object of the set of objects; determining a node type for each identified node, wherein the node type includes a standard node, an open node, or an end node; and connecting multiple identified nodes based on their node types to obtain the set of nodes for the first path.
[0162] Aspect 4 is the method of any of aspects 1 to 3, wherein each identified node is associated with a set of attributes that includes one or more of: a position of the UE at the node, a velocity of the UE at the node, an acceleration of the UE at the node, a jerk of the UE at the node, or an object identifier (ID) associated with a corresponding object, wherein the multiple identified nodes are connected based on their corresponding set of attributes.
[0163] Aspect 5 is the method of any of aspects 1 to 4, wherein determining, based on using the at least one node in the set of nodes as the target, the second path for avoiding the at least one object in the set of objects using the second algorithm comprises: using a second node in the set of nodes as the target when the UE is at a first node in the set of nodes; determining whether a lateral position of the UE is able to pass a lateral position of the at least one object; and generating the second path based on (1) a heading angle towards the at least one object and (2) a distance to the at least one object if the lateral position of the UE is able to pass the lateral position of the at least one object, or based on (1) the heading angle towards the at least one object, (2) a first distance to the at least one object, (3) a second distance to at least one lane marker, and (4) a lateral distance from a predicted end point to the second node if the lateral position of the UE is unable to pass the lateral position of the at least one object.
[0164] Aspect 6 is the method of any of aspects 1 to 5, wherein the second node is subsequent to the first node in the set of nodes.
[0165] Aspect 7 is the method of any of aspects 1 to 6, wherein the lateral position of the UE corresponds to a set of front wheel or tire positions of the UE.
[0166] Aspect 8 is the method of any of aspects 1 to 7, further comprising: obtaining information related to the set of objects and lane marker from at least one camera or radar, wherein the identification of the potential collision with the set of objects is based on the obtained information.
[0167] Aspect 9 is the method of any of aspects 1 to 8, wherein the set of objects corresponds to a set of movable and static objects.
[0168] Aspect 10 is the method of any of aspects 1 to 9, wherein determining the first path that includes the set of nodes for avoiding the set of objects using the first algorithm comprises: calculating the first path that includes the set of nodes for avoiding the set of objects using the first algorithm.
[0169] Aspect 11 is the method of any of aspects 1 to 10, wherein determining the second path for avoiding the at least one object in the set of objects using the second algorithm comprises: calculating the second path for avoiding the at least one object in the set of objects using the second algorithm.
[0170] Aspect 12 is the method of any of aspects 1 to 11, wherein outputting the indication to switch to the second path comprises at least one of: transmitting an indication of the second path to an autonomous emergency steering (AES) system; or maneuvering the UE to the second path.
[0171] Aspect 13 is an apparatus at a user equipment (UE) , including: at least one memory; and at least one processor coupled to the at least one memory and, based at least in part on information stored in the at least one memory, the at least one processor, individually or in any combination, is configured to implement any of aspects 1 to 12.
[0172] Aspect 14 is the apparatus of aspect 13, further including at least one transceiver coupled to the at least one processor.
[0173] Aspect 15 is an apparatus at a user equipment (UE) , including means for implementing any of aspects 1 to 12.
[0174] Aspect 16 is a computer-readable medium (e.g., a non-transitory computer-readable medium) storing computer executable code, where the code when executed by a processor causes the processor to implement any of aspects 1 to 12.
Claims
1.An apparatus at a user equipment (UE) , comprising:at least one memory; andat least one processor coupled to the at least one memory, the at least one processor, individually or in any combination, is configured to:identify there is a potential collision with a set of objects on a travelling path of the UE;determine, based on identification of the potential collision with the set of objects, a first path that includes a set of nodes for avoiding the set of objects using a first algorithm;determine, based on using at least one node in the set of nodes as a target, a second path for avoiding at least one object in the set of objects using a second algorithm; andoutput an indication to switch to the second path for avoiding the at least one object in the set of objects.2.The apparatus of claim 1, wherein the first algorithm corresponds to an A-star (A*) algorithm and the second algorithm corresponds to a dynamic window approach (DWA) algorithm.3.The apparatus of claim 1, wherein to determine the first path that includes the set of nodes for avoiding the set of objects using the first algorithm, the at least one processor, individually or in any combination, is configured to:identify one or more nodes around each object of the set of objects;determine a node type for each identified node, wherein the node type includes a standard node, an open node, or an end node; andconnect multiple identified nodes based on their node types to obtain the set of nodes for the first path.4.The apparatus of claim 3, wherein each identified node is associated with a set of attributes that includes one or more of:a position of the UE at the node,a velocity of the UE at the node,an acceleration of the UE at the node,a jerk of the UE at the node, oran object identifier (ID) associated with a corresponding object, wherein the multiple identified nodes are connected based on their corresponding set of attributes.5.The apparatus of claim 1, wherein to determine, based on using the at least one node in the set of nodes as the target, the second path for avoiding the at least one object in the set of objects using the second algorithm, the at least one processor, individually or in any combination, is configured to:use a second node in the set of nodes as the target when the UE is at a first node in the set of nodes;determine whether a lateral position of the UE is able to pass a lateral position of the at least one object; andgenerate the second path based on (1) a heading angle towards the at least one object and (2) a distance to the at least one object if the lateral position of the UE is able to pass the lateral position of the at least one object, or based on (1) the heading angle towards the at least one object, (2) a first distance to the at least one object, (3) a second distance to at least one lane marker, and (4) a lateral distance from a predicted end point to the second node if the lateral position of the UE is unable to pass the lateral position of the at least one object.6.The apparatus of claim 5, wherein the second node is subsequent to the first node in the set of nodes.7.The apparatus of claim 5, wherein the lateral position of the UE corresponds to a set of front wheel or tire positions of the UE.8.The apparatus of claim 1, wherein the at least one processor, individually or in any combination, is further configured to:obtain information related to the set of objects and lane marker from at least one camera or radar, wherein the identification of the potential collision with the set of objects is based on the obtained information.9.The apparatus of claim 1, wherein the set of objects corresponds to a set of movable and static objects.10.The apparatus of claim 1, wherein to determine the first path that includes the set of nodes for avoiding the set of objects using the first algorithm, the at least one processor, individually or in any combination, is configured to: calculate the first path that includes the set of nodes for avoiding the set of objects using the first algorithm.11.The apparatus of claim 1, wherein to determine the second path for avoiding the at least one object in the set of objects using the second algorithm, the at least one processor, individually or in any combination, is configured to: calculate the second path for avoiding the at least one object in the set of objects using the second algorithm.12.The apparatus of claim 1, wherein to output the indication to switch to the second path, the at least one processor, individually or in any combination, is configured to at least one of:transmit an indication of the second path to an autonomous emergency steering (AES) system; ormaneuver the UE to the second path.13.A method at a user equipment (UE) , comprising:identifying there is a potential collision with a set of objects on a travelling path of the UE;determining, based on identification of the potential collision with the set of objects, a first path that includes a set of nodes for avoiding the set of objects using a first algorithm;determining, based on using at least one node in the set of nodes as a target, a second path for avoiding at least one object in the set of objects using a second algorithm; andoutputting an indication to switch to the second path for avoiding the at least one object in the set of objects.14.The method of claim 13, wherein the first algorithm corresponds to an A-star (A*) algorithm and the second algorithm corresponds to a dynamic window approach (DWA) algorithm.15.The method of claim 13, wherein determining the first path that includes the set of nodes for avoiding the set of objects using the first algorithm comprises:identifying one or more nodes around each object of the set of objects;determining a node type for each identified node, wherein the node type includes a standard node, an open node, or an end node; andconnecting multiple identified nodes based on their node types to obtain the set of nodes for the first path.16.The method of claim 13, wherein determining, based on using the at least one node in the set of nodes as the target, the second path for avoiding the at least one object in the set of objects using the second algorithm comprises:using a second node in the set of nodes as the target when the UE is at a first node in the set of nodes;determining whether a lateral position of the UE is able to pass a lateral position of the at least one object; andgenerating the second path based on (1) a heading angle towards the at least one object and (2) a distance to the at least one object if the lateral position of the UE is able to pass the lateral position of the at least one object, or based on (1) the heading angle towards the at least one object, (2) a first distance to the at least one object, (3) a second distance to at least one lane marker, and (4) a lateral distance from a predicted end point to the second node if the lateral position of the UE is unable to pass the lateral position of the at least one object.17.The method of claim 13, further comprising:obtaining information related to the set of objects and lane marker from at least one camera or radar, wherein the identification of the potential collision with the set of objects is based on the obtained information.18.The method of claim 13, wherein determining the first path that includes the set of nodes for avoiding the set of objects using the first algorithm comprises: calculating the first path that includes the set of nodes for avoiding the set of objects using the first algorithm, and wherein determining the second path for avoiding the at least one object in the set of objects using the second algorithm comprises: calculating the second path for avoiding the at least one object in the set of objects using the second algorithm.19.The method of claim 13, wherein outputting the indication to switch to the second path comprises at least one of:transmitting an indication of the second path to an autonomous emergency steering (AES) system; ormaneuvering the UE to the second path.20.A computer-readable medium storing computer executable code at a user equipment (UE) , the code when executed by at least one processor causes the at least one processor to:identify there is a potential collision with a set of objects on a travelling path of the UE;determine, based on identification of the potential collision with the set of objects, a first path that includes a set of nodes for avoiding the set of objects using a first algorithm;determine, based on using at least one node in the set of nodes as a target, a second path for avoiding at least one object in the set of objects using a second algorithm; andoutput an indication to switch to the second path for avoiding the at least one object in the set of objects.
Citation Information
Patent Citations
Unmanned ground vehicle path planning method based on improved dynamic window method
CN113156964A
Intelligent horizontal transportation system and method for full-automatic container loading and unloading wharf.
CN113486293A
Unmanned vehicle real-time global path planning method based on dynamic window of safe A* guide point
CN113608531A
DWA-based robot local path planning method and device in narrow environment and storage medium
CN115857504A
Robot path planning method based on fusion algorithm and related equipment
CN117433554A