Map aware security system

Abstract

This disclosure provides systems, methods, and devices for wireless communication that support sensed charging subscriptions. In a first aspect, a method of wireless communication includes receiving first location information associated with a first mobile entity. The method also includes sending an alert based on the first location information and path information configured to model a plurality of paths associated with the intersection zone. The plurality of paths includes a curved first path. The path information defines a plurality of line segments to model the first path. Other aspects and features are also claimed and described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. patent application Ser. No. 18 / 165,526, filed on February 7, 2023, entitled “MAP AWARE SAFETY SYSTEM,” which is expressly incorporated herein by reference in its entirety. Technical Field

[0003] Aspects of the present disclosure generally relate to wireless communication systems, and more particularly to safety systems, such as safety systems utilizing map data. Some features may enable and provide improved entity tracking, improved and more relevant safety alerts, improved power efficiency, reduction of intersection accidents, or a combination thereof. Background Art

[0004] Wireless communication networks are widely deployed to provide various communication services such as voice, video, packet data, messaging, broadcast, etc. These wireless networks may be multiple-access networks capable of supporting communication for multiple users by sharing the available network resources.

[0005] A wireless communication network may include several components. These components may include wireless communication devices, such as base stations (or Node Bs) that may support communication for multiple user equipment (UEs). UEs may communicate with base stations via downlinks and uplinks. A downlink (or forward link) refers to the communication link from a base station to a UE, and an uplink (or reverse link) refers to the communication link from a UE to a base station.

[0006] A base station may transmit data and control information to a UE on the downlink, or receive data and control information from a UE on the uplink. On the downlink, transmissions from a base station may encounter interference caused by transmissions from neighboring base stations or other wireless radio frequency (RF) transmitters. On the uplink, transmissions from a UE may encounter interference from uplink transmissions from other UEs communicating with neighboring base stations or from other wireless RF transmitters. This interference may degrade performance on both the downlink and uplink.

[0007] As the demand for mobile broadband access continues to grow, the potential for interference and congested networks grows with more UEs accessing long-range wireless communication networks and more short-range wireless systems deployed in communities. Research and development continue to advance wireless technologies to not only meet the growing demand for mobile broadband access, but also to improve and enhance the user experience with mobile communications.

[0008] Vehicle-to-everything (V2X) enables the sharing of information from a vehicle to another device or entity that may affect the vehicle, and vice versa. V2X technology is associated with an in-vehicle communication system that may include one or more aspects or types of communication, such as vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-network (V2N), vehicle-to-pedestrian (V2P), vehicle-to-device (V2D), and vehicle-to-grid (V2G), as illustrative, non-limiting examples. V2X technology can utilize cellular-based communications or wireless local area network communications. In some implementations, messages and communications for V2X technology are in the application and use the underlying radio as the conduit (communication path).

[0009] V2X-capable vehicles periodically broadcast their current status using application-layer messages, such as Basic Safety Messages (BSMs) or Collaborative Awareness Messages (CAMs), which are nominally sent every 100 milliseconds (ms). These transmissions constitute V2X basic safety capabilities and include at least vehicle identity, location, and motion status. Beyond basic safety, standards bodies such as the Society of Automotive Engineers (SAE), the European Telecommunications Standards Institute (ETSI)-European Telecommunications Standards (ETS), and the China Standards Association, China Society of Automotive Engineers (CSAE), are developing application-layer standards for advanced features, including sensor sharing (such as broadcasting detected vehicles or objects) and collaborative driving (such as sharing and negotiating intended maneuvers). In a V2P system, such messages can be detected by one or more UEs and used to alert vulnerable road users (VRUs), such as pedestrians, cyclists, and other micro-mobility users (e.g., e-scooters, Segways, etc.), of the presence of one or more vehicles. Compared to road vehicles (such as cars, trucks, or other vehicles that include an alternator), UEs typically include storage devices, such as batteries, that may be sensitive to power consumption. Frequent or continuous monitoring of V2X application layer messages may result in unacceptable power consumption (battery drain) for the UE.

[0010] Additionally, even if such messages are implemented, the VRU may still be at risk of injury or potential collision with a vehicle in certain situations (such as at an intersection) due to driver distraction or impairment, VRU distraction (e.g., a VRU at an intersection may be looking at a smartphone or watch / wearable device while walking, jogging, or cycling), or a combination thereof. Summary of the Invention

[0011] The following summarizes some aspects of the present disclosure to provide a basic understanding of the technology discussed. This summary is not an exhaustive overview of all anticipated features of the present disclosure and is neither intended to identify key or important elements of all aspects of the present disclosure nor to delineate the scope of any or all aspects of the present disclosure. The sole purpose of this summary is to provide some concepts of one or more aspects of the present disclosure in a summarized form as a prelude to the more detailed description that will be presented later.

[0012] In one aspect of the present disclosure, a method for wireless communication is performed by a server. The method includes receiving first location information associated with a first mobile entity. The method also includes sending an alert based on the first location information and path information configured to model multiple paths associated with an intersection area. The multiple paths include a curved first path. The path information defines multiple line segments to model the first path.

[0013] In an additional aspect of the present disclosure, an apparatus includes at least one processor and a memory coupled to the at least one processor. The at least one processor is configured to receive first location information associated with a first mobile entity. The at least one processor is further configured to send an alert based on the first location information and path information configured to model multiple paths associated with an intersection zone. The multiple paths include a curved first path. The path information defines multiple line segments to model the first path.

[0014] In an additional aspect of the present disclosure, an apparatus includes means for receiving first location information associated with a first mobile entity. The apparatus also includes means for sending an alert based on the first location information and path information configured to model multiple paths associated with an intersection zone. The multiple paths include a curved first path. The path information defines multiple line segments to model the first path.

[0015] In an additional aspect of the present disclosure, a non-transitory computer-readable medium stores instructions that, when executed by a processor, cause the processor to perform operations. The operations include receiving first location information associated with a first mobile entity. The operations also include sending an alert based on the first location information and path information configured to model multiple paths associated with an intersection zone. The multiple paths include a curved first path. The path information defines multiple line segments to model the first path.

[0016] The features and technical advantages of the examples according to the present disclosure have been outlined quite broadly above so that the detailed description below may be better understood. Additional features and advantages will be described below. The concepts and specific examples disclosed may be readily utilized as a basis for modifying or designing other structures for achieving the same purposes of the present disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein (both their organization and method of operation) and the associated advantages will be better understood from the following description when considered in conjunction with the accompanying drawings. Each of the figures in the drawings is provided for the purpose of illustration and description and not as a definition of limitations to the claims.

[0017] Although various aspects and specific implementations are described in this application by way of illustration of some examples, it will be understood by those skilled in the art that additional specific implementations and use cases may be generated in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, aspects and / or uses may be generated via integrated chip specific implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, devices that enable artificial intelligence (AI), etc.). Although some examples may or may not specifically point to use cases or applications, the applicability of a wide range of described innovations may occur. The scope of specific implementations may range from chip-level or module components to non-module, non-chip-level specific implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems in conjunction with one or more aspects of the described innovations. In some practical environments, the devices in conjunction with the described various aspects and features may also necessarily include additional components and features for implementing and practicing the various aspects claimed and described. For example, the transmission and reception of wireless signals necessarily include multiple components for analog and digital purposes (e.g., hardware components including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The innovations described herein are intended to be practiced in a variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc., having different sizes, shapes, and configurations. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] A further understanding of the nature and advantages of the present disclosure may be achieved by referring to the following drawings. In the drawings, similar components or features may have the same reference number. In addition, various components of the same type may be distinguished by following the reference number with a dash and a second reference number to distinguish between similar components. If only the first reference number is used in the specification, the description applies to any of the similar components having the same first reference number, regardless of the second reference number.

[0019] Figure 1 is a block diagram illustrating details of an example wireless communication system in accordance with one or more aspects.

[0020] Figure 2 is a block diagram illustrating an example of a base station and a user equipment (UE) according to one or more aspects.

[0021] Figure 3 A diagram illustrating an example decomposed base station architecture in accordance with one or more aspects is shown.

[0022] Figure 4 is a block diagram illustrating an example wireless communication system supporting a security system in accordance with one or more aspects.

[0023] Figure 5 is a diagram illustrating an example of a map supporting a safety system according to one or more aspects.

[0024] Figure 6 is a table illustrating an example data structure for a path model supporting a safety system according to one or more aspects.

[0025] Figure 7 is a diagram illustrating another example of a map supporting a safety system according to one or more aspects.

[0026] Figure 8 is a diagram illustrating another example of a map supporting a safety system according to one or more aspects.

[0027] Figure 9 is an illustration of an example of a timing diagram for two entities supporting a security system according to one or more aspects.

[0028] Figure 10 is a flow diagram illustrating an example process for supporting a security system in accordance with one or more aspects.

[0029] Figure 11 is a flow diagram illustrating an example process for supporting a security system in accordance with one or more aspects.

[0030] Figure 12 is a block diagram of an example server supporting a security system according to one or more aspects.

[0031] Figure 13 is a block diagram of example network entities supporting a security system according to one or more aspects.

[0032] Like reference numbers and designations in the various drawings indicate like elements. DETAILED DESCRIPTION

[0033] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to limit the scope of the present disclosure. Instead, the detailed description includes specific details to provide a thorough understanding of the subject matter of the present invention. It will be apparent to those skilled in the art that these specific details are not required in every case, and in some instances, well-known structures and components are shown in block diagram form for clarity of presentation.

[0034] The present disclosure provides systems, devices, methods, and computer-readable media that support safety systems. For example, the present disclosure describes a server, such as a car-to-cloud server, configured to determine the likelihood of a collision between two entities (such as a user equipment (UE) and a vehicle) at an intersection. To enable the server to determine the likelihood of a collision, the server may store a plurality of path models associated with the intersection and configured to model the paths of the entities toward the intersection. One or more of the path models may include a piecewise linearization of a corresponding path leading to or entering the intersection. At least one path model may model a curved path. Each path model may define a set of line segments of the path model, and include at least one line segment in the set of line segments of the path model having an endpoint positioned in an intersection zone. Additionally or alternatively, each path model may include a data structure stored in association with a map. For example, the data structure of the path model may be stored as metadata associated with an intersection zone of a map. In some implementations, for a path model that defines one or more line segments, the data structure may define or indicate that, for each line segment in the set of line segments of the path model, the path model defines a segment identifier (ID) of the line segment, a first endpoint of the line segment, a second endpoint of the line segment, an azimuth of the line segment, a segment length of the line segment, or a combination thereof. In some implementations, the server may receive first location information of a first entity, select a first path model for the first entity, and use the first path model to estimate a first time period during which the first entity is predicted to be in an intersection zone. Additionally, the server may receive second location information of a second entity, select a second path model for the second entity, and use the second path model to estimate a second time period during which the second entity is predicted to be in an intersection zone. Based on the first time period and the second time period, the server may generate an alert based on determining that the first entity and the second entity are predicted to be in the intersection zone at the same time.

[0035] Specific implementations of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages or benefits. In some aspects, the present disclosure provides techniques for supporting safety systems. For example, when at least one of two entities is traveling along a curved path toward an intersection, the described techniques provide an alert message based on a possible collision at the intersection between the two entities. By providing piecewise linearization to model the curved path, a path model can be selected and used to effectively estimate the entity's progress toward the intersection even in the presence of high measurement noise. The techniques further provide data structures for defining one or more path models, such that the one or more path models can be stored in association with map data. For example, data structures associated with intersections included in the map data can be stored as metadata as part of the map data. Additionally, the techniques can provide improved entity tracking, improved and more relevant safety alerts, improved power efficiency, a reduction in intersection accidents, or a combination thereof.

[0036] The present disclosure as a whole relates to providing or participating in authorized shared access between two or more wireless devices in one or more wireless communication systems (also referred to as wireless communication networks). In various specific implementations, the techniques and apparatuses may be used for wireless communication networks, such as code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks, single carrier FDMA (SC-FDMA) networks, LTE networks, GSM networks, fifth generation (5G) or new radio (NR) networks (sometimes referred to as "5G NR" networks, systems or devices), and other communication networks. As described herein, the terms "network" and "system" can be used interchangeably.

[0037] A CDMA network may implement, for example, a radio technology such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includes Wideband CDMA (W-CDMA) and Low Chip Rate (LCR). CDMA2000 covers IS-2000, IS-95, and IS-856 standards.

[0038] For example, a TDMA network may implement a radio technology such as Global System for Mobile Communications (GSM). The Third Generation Partnership Project (3GPP) defined the standard for the GSM EDGE (Enhanced Data Rates for GSM Evolution) Radio Access Network (RAN), also known as GERAN. GERAN is the radio component of GSM / EDGE, along with the network connecting base stations (e.g., Ater and Abis interfaces) and base station controllers (A interfaces, etc.). The radio access network represents the component of a GSM network through which phone calls and packet data are routed from the public switched telephone network (PSTN) and the internet to subscriber handsets (also known as user terminals or user equipment (UE)), and vice versa. A mobile phone operator's network may include one or more GERANs, which, in the case of a UMTS / GSM network, may be coupled to a UTRAN. Additionally, an operator's network may include one or more LTE networks, or one or more other networks. Various network types may utilize different radio access technologies (RATs) and RANs.

[0039] OFDMA networks can implement radio technologies such as Evolved UTRA (E-UTRA), Institute of Electrical and Electronics Engineers (IEEE) 802.11, IEEE 802.16, IEEE 802.20, flash-OFDM, etc. UTRA, E-UTRA, and GSM are part of the Universal Mobile Telecommunications System (UMTS). Specifically, Long Term Evolution (LTE) is a version of UMTS that uses E-UTRA. UTRA, E-UTRA, GSM, UMTS, and LTE are described in documents provided by an organization called the "3rd Generation Partnership Project" (3GPP), and cdma2000 is described in documents from an organization called the "3rd Generation Partnership Project 2" (3GPP2). These various radio technologies and standards are either known or under development. For example, 3GPP is a collaboration between a group of telecommunications associations to define globally applicable third generation (3G) mobile phone specifications. 3GPP LTE is a 3GPP initiative aimed at improving the UMTS mobile phone standard. 3GPP can define specifications for next-generation mobile networks, mobile systems, and mobile devices. This disclosure may describe certain aspects with reference to LTE, 4G, or 5G NR technologies; however, the description is not intended to be limited to a particular technology or application, and one or more aspects described with reference to one technology may be understood to be applicable to another technology. Additionally, one or more aspects of this disclosure may relate to shared access to wireless spectrum between networks using different radio access technologies or radio air interfaces.

[0040] 5G networks are expected to have diverse deployments, diverse spectrum, and diverse services and devices that can be implemented using a unified air interface based on OFDM. To achieve these goals, in addition to developing new radio technologies for 5GNR networks, further enhancements to LTE and LTE-A are also being considered. 5GNR will be able to scale to provide coverage (1) to massive Internet of Things (IoT), with ultra-high density (e.g., about 1M nodes / km) 2 (1) ultra-low complexity (e.g., about 10s of bits / sec), ultra-low power consumption (e.g., about 10+ years of battery life), and deep coverage with the ability to reach challenging locations; (2) includes mission-critical control with strong security to protect sensitive personal, financial, or classified information, ultra-high reliability (e.g., about 99.9999% reliability), ultra-low latency (e.g., about 1 millisecond (ms)), and users with a wide range of mobility or lack of mobility; and (3) provides services with enhanced mobile broadband (including very high capacity (e.g., about 10Tbps / km 2 ), coverage of very high data rates (e.g., multi-Gbps rates, 100+Mbps user experience rates), and deep perception with advanced discovery and optimization).

[0041] Devices, networks, and systems may be configured to communicate via one or more portions of the electromagnetic spectrum. The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5GNR, 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). Frequencies between FR1 and FR2 are typically referred to as mid-band frequencies. Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as the "below 6 GHz" band in various documents and articles. Similar naming issues sometimes arise for FR2, which is often (interchangeably) referred to as the "millimeter wave" (mmWave) band in documents and articles, although it is different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "mmWave" band by the International Telecommunication Union (ITU).

[0042] In view of the above aspects, unless otherwise specifically stated, it should be understood that the term "sub-6 GHz" and the like, if used herein, can broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. Furthermore, unless otherwise specifically stated, it should be understood that the term "mmWave" and the like, if used herein, can broadly refer to frequencies that may include mid-band frequencies, may be within FR2, or may be within the EHF band.

[0043] 5G NR devices, networks, and systems can be implemented using optimized OFDM-based waveform features. These features may include scalable numerologies and transmit time intervals (TTIs); a common, flexible framework for efficiently multiplexing services and features using dynamic, low-latency time division duplex (TDD) or frequency division duplex (FDD) designs; and advanced wireless technologies such as massive multiple-input, multiple-output (MIMO), robust mmWave transmission, advanced channel coding, and device-centric mobility. The scalability of numerologies and subcarrier spacing in 5G NR efficiently addresses the operation of various services across different spectrums and deployments. For example, in various outdoor and macro coverage deployments with less than 3 GHz FDD or TDD implementations, subcarrier spacing may occur as 15 kHz, for example, over bandwidths of 1 MHz, 5 MHz, 10 MHz, or 20 MHz. For various other outdoor and small cell coverage deployments with TDD greater than 3 GHz, subcarrier spacing may occur as 30 kHz over 80 MHz / 100 MHz bandwidths. For various other indoor broadband implementations, using TDD in the unlicensed portion of the 5 GHz band, the subcarrier spacing may occur at 60 kHz over a 160 MHz bandwidth. Finally, for various deployments transmitting over mmWave components using TDD at 28 GHz, the subcarrier spacing may occur at 120 kHz over a 500 MHz bandwidth.

[0044] 5G NR's scalable parameter set facilitates scalable TTIs for diverse latency and quality of service (QoS) requirements. For example, shorter TTIs can be used for low latency and high reliability, while longer TTIs can be used for higher spectral efficiency. Efficient multiplexing of long and short TTIs allows transmission to start on symbol boundaries. 5G NR also anticipates a self-contained integrated subframe design, where uplink or downlink scheduling information, data, and acknowledgments are located in the same subframe. The self-contained integrated subframe supports communications in unlicensed or contention-based shared spectrum, and adaptive uplink or downlink can be flexibly configured on a per-cell basis to dynamically switch between uplink and downlink to meet current traffic needs.

[0045] For clarity, certain aspects of the devices and techniques may be described below with reference to example 5G NR implementations or in a 5G-centric manner, and 5G terminology may be used as illustrative examples in portions of the description below; however, the description is not intended to be limited to 5G applications.

[0046] Furthermore, it should be understood that in operation, a wireless communication network adapted according to the concepts herein can operate using any combination of licensed or unlicensed spectrum, depending on load and availability. Therefore, it will be apparent to one of ordinary skill in the art that the systems, devices, and methods described herein can be applied to other communication systems and applications beyond the specific examples provided.

[0047] Although various aspects and specific implementations are described in this application by way of illustration of some examples, it will be understood by those skilled in the art that additional specific implementations and use cases may be generated in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, specific implementations or uses may be implemented via integrated chip specific implementations or other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail equipment or purchasing equipment, medical equipment, AI-enabled devices, etc.). Although some examples may or may not specifically point to use cases or applications, the applicability of a wide range of described innovations may occur. The scope of specific implementations may range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems comprising one or more described aspects. In some practical environments, the devices in combination with the various aspects and features described may also necessarily include additional components and features for implementing and practicing the various aspects claimed and described. It is intended that the innovations described herein may be implemented in a wide variety of embodiments of different sizes, shapes, and configurations, including both large and small devices, chip-level components, multi-component systems (e.g., radio frequency (RF) chains, communication interfaces, processors), distributed arrangements, end-user devices, etc.

[0048] Figure 1 1 is a block diagram illustrating details of an example wireless communication system according to one or more aspects. The wireless communication system may include a wireless network 100. The wireless network 100 may, for example, include a 5G wireless network. As will be appreciated by those skilled in the art, Figure 1 Components appearing in are likely to have related corresponding components in other network arrangements, including, for example, cellular-style network arrangements as well as non-cellular-style network arrangements (e.g., device-to-device or peer-to-peer or ad hoc network arrangements, etc.).

[0049] Figure 1The illustrated wireless network 100 includes a number of base stations 105 and other network entities. A base station can be a station that communicates with a UE and can also be referred to as an evolved Node B (eNB), a next-generation eNB (gNB), an access point, etc. Each base station 105 can provide communication coverage for a specific geographic area. In 3GPP, the term "cell" can refer to a specific geographic coverage area of ​​a base station or a base station subsystem serving that coverage area, depending on the context in which the term is used. In specific implementations of the wireless network 100 herein, the base stations 105 can be associated with the same operator or different operators (e.g., the wireless network 100 can include multiple operator wireless networks). In addition, in specific implementations of the wireless network 100 herein, the base stations 105 can provide wireless communications using one or more of the same frequencies as neighboring cells (e.g., one or more frequency bands in a licensed spectrum, an unlicensed spectrum, or a combination thereof). In some examples, an individual base station 105 or UE 115 can be operated by more than one network operating entity. In some other examples, each base station 105 and UE 115 can be operated by a single network operating entity.

[0050] A base station may provide communication coverage for a macro cell or a small cell (e.g., a pico cell or femto cell) or other type of cell. A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs that have a service subscription with a network provider. A small cell (such as a pico cell) will generally cover a relatively small geographic area and may allow unrestricted access by UEs that have a service subscription with a network provider. A small cell (such as a femto cell) will generally also cover a relatively small geographic area (e.g., a home) and, in addition to unrestricted access, may also provide restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs of users in a home, etc.). A base station for a macro cell may be referred to as a macro base station. A base station for a small cell may be referred to as a small cell base station, a pico base station, a femto base station, or a home base station. In Figure 1 In the example shown, base stations 105d and 105e are conventional macro base stations, while base stations 105a-105c are macro base stations implemented using one of 3D, full-dimensional (FD), or massive MIMO. Base stations 105a-105c utilize their higher-dimensional MIMO capabilities to employ 3D beamforming in elevation and azimuth beamforming to increase coverage and capacity. Base station 105f is a small cell base station, which can be a home node or a portable access point. The base station can support one or more (e.g., two, three, four, etc.) cells.

[0051] Wireless network 100 may support synchronous or asynchronous operation. For synchronous operation, base stations may have similar frame timing, and transmissions from different base stations may be approximately aligned in time. For asynchronous operation, base stations may have different frame timing, and transmissions from different base stations may not be aligned in time. In some cases, the network may be enabled or configured to handle dynamic switching between synchronous and asynchronous operation.

[0052] UEs 115 are dispersed throughout the wireless network 100, and each UE may be stationary or mobile. It should be understood that although mobile devices are generally referred to as UEs in the standards and specifications promulgated by 3GPP, such devices may additionally or otherwise be referred to by those skilled in the art as mobile stations (MSs), subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals (ATs), mobile terminals, wireless terminals, remote terminals, handsets, terminals, user agents, mobile clients, clients, gaming devices, augmented reality devices, vehicle components, vehicle devices, or vehicle modules, or some other suitable terminology. In this document, a "mobile" device or UE does not necessarily have the ability to move and may be stationary. Some non-limiting examples of mobile devices, for example, may include one or more implementations of UE 115, including mobile phones, cellular phones, smartphones, Session Initiation Protocol (SIP) phones, wireless local loop (WLL) stations, laptops, personal computers (PCs), notebooks, netbooks, smartbooks, tablets, and personal digital assistants (PDAs). The mobile device may additionally be an IoT or "Internet of Everything" (IoE) device, such as a car or other transportation vehicle, a satellite radio, a global positioning system (GPS) device, a global navigation satellite system (GNSS) device, a logistics controller, a drone, a multi-rotor helicopter, a quadcopter, smart energy or security equipment, solar panels or solar arrays, urban lighting, tap water or other infrastructure; industrial automation and enterprise equipment; consumer and wearable devices, such as glasses, wearable cameras, smart watches, health or fitness trackers, mammalian implantable devices, gesture tracking devices, medical devices, digital audio players (e.g., MP3 players), cameras, game consoles, etc.; and digital home or smart home devices, such as home audio, video and multimedia devices, appliances, sensors, vending machines, smart lighting, home security systems, smart meters, etc. In one aspect, the UE may be a device that includes a universal integrated circuit card (UICC). In another aspect, the UE may be a device that does not include a UICC. In some aspects, a UE that does not include a UICC may also be referred to as an IoE device. Figure 1The UEs 115a to 115d of the specific implementation illustrated in FIG are examples of mobile smartphone-type devices accessing the wireless network 100. A UE may also be a machine specifically configured to implement connected communications, including machine type communications (MTC), enhanced MTC (eMTC), narrowband IoT (NB-IoT), and the like. Figure 1 UEs 115e to 115k illustrated in FIG. 1 are examples of various machines configured for communication that access wireless network 100 .

[0053] A mobile device, such as UE 115, may be able to communicate with any type of base station, whether macro, pico, femto, relay, etc. Figure 1 In the figure, the communication links (represented as lightning balls) indicate wireless transmissions between a UE and a serving base station (which is a base station designated to serve the UE on the downlink or uplink), or desired transmissions between base stations, as well as backhaul transmissions between base stations. A UE may operate as a base station or other network node in some scenarios. Backhaul communications between base stations of wireless network 100 may be performed using wired or wireless communication links.

[0054] In operation, at wireless network 100, base stations 105a-105c use 3D beamforming and coordinated spatial techniques (e.g., coordinated multipoint (CoMP) or multi-connectivity) to serve UEs 115a and 115b. Macro base station 105d performs backhaul communications with base stations 105a-105c and small cells (base station 105f). Macro base station 105d also transmits multicast services that are subscribed to and received by UEs 115c and 115d. Such multicast services may include mobile TV or streaming video, or may include other services for providing community information, such as weather emergencies or alerts, such as Amber Alerts or Gray Alerts.

[0055] The wireless network 100 of the embodiment supports mission-critical communications with ultra-reliable and redundant links for mission-critical devices such as UE 115e, which is a drone. The redundant communication links with UE 115e include links from macro base station 105d and macro base station 105e, as well as small cell base station 105f. Other machine-type devices, such as UE 115f (thermometer), UE 115g (smart meter), and UE 115h (wearable device), can communicate directly with base stations such as small cell base station 105f and macro base station 105e via the wireless network 100, or in a multi-hop configuration by communicating with another user device that relays its information to the network, such as UE 115f communicating temperature measurement information to smart meter UE 115g, which then reports it to the network via small cell base station 105f. The wireless network 100 may also provide additional network efficiency (e.g., in a vehicle-to-vehicle (V2V) mesh network between UEs 115i-115k communicating with the macro base station 105e) through dynamic, low-latency TDD communications or low-latency FDD communications. Additionally, the V2V mesh network may include or correspond to a vehicle-to-everything (V2X) network between the UEs 115i-115k and one or more other devices, such as the UEs 115x, 115y.

[0056] The base stations 105 can communicate with the core network 130 and with each other. For example, the base stations 105 can interface with the core network 130 via a backhaul link 132 (e.g., via S1, N2, N3, or other interfaces). The base stations 105 can communicate with each other directly (e.g., directly between the base stations 105) or indirectly (e.g., via the core network 130) via the backhaul link (e.g., via X2, Xn, or other interfaces).

[0057] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC), which may include at least one mobility management entity (MME), at least one serving gateway (S-GW), and at least one packet data network (PDN) gateway (P-GW). The MME may manage non-access stratum (e.g., control plane) functions such as mobility, authentication, and bearer management for UEs 115 served by base stations 105 associated with the EPC. User IP packets may be delivered through the S-GW, which itself may be connected to the P-GW. The P-GW may provide IP address allocation and other functions. The P-GW may be connected to network operator IP services. The operator IP services may include access to the Internet, an intranet, an IP multimedia subsystem (IMS), or packet switched (PS) streaming services.

[0058] In some implementations, the core network 130 includes or is coupled to a location management function (LMF) 131, which is an entity in the 5G core network (5GC) that supports various functionalities, such as managing support for different location services for one or more UEs. For example, the LMF 131 may include one or more servers, such as multiple distributed servers. The base station 105 may forward location messages to the LMF 131 and may communicate with the LMF via the NR Positioning Protocol A (NRPPa). The LMF 131 is configured to control positioning parameters of the UE 115, and the LMF 131 may provide information to the base station 105 and the UE 115 so that actions can be taken at the UE 115. In some implementations, the UE 115 and the base station 105 are configured to communicate with the LMF 131 via an access and mobility management function (AMF).

[0059] Figure 2 is a block diagram illustrating an example of a base station 105 and a UE 115 according to one or more aspects. The base station 105 and the UE 115 may be Figure 1 For the restricted association scenario (as mentioned above), the base station 105 can be any one of the base stations in the UE and one of the UEs. Figure 1 The small cell base station 105f in the base station 105f, and the UE 115 may be a UE 115c or 115d operating in the service area of ​​the base station 105f, which will be included in the list of accessible UEs of the small cell base station 105f in order to access the small cell base station 105f. The base station 105 may also be some other type of base station. Figure 2 As shown in FIG, the base station 105 may be equipped with antennas 234a through 234t, and the UE 115 may be equipped with antennas 252a through 252r for facilitating wireless communication.

[0060] At the base station 105, the transmit processor 220 may receive data from the data source 212 and control information from the controller 240 (such as a processor). The control information may be for the physical broadcast channel (PBCH), the physical control format indicator channel (PCFICH), the physical hybrid ARQ (automatic repeat request) indicator channel (PHICH), the physical downlink control channel (PDCCH), the enhanced physical downlink control channel (EPDCCH), the MTC physical downlink control channel (MPDCCH), etc. The data may be for the physical downlink shared channel (PDSCH), etc. In addition, the transmit processor 220 may process (e.g., encode and symbol map) the data and control information separately to obtain data symbols and control symbols. The transmit processor 220 may also generate reference symbols, such as for the primary synchronization signal (PSS) and the secondary synchronization signal (SSS), as well as cell-specific reference signals. The transmit (TX) MIMO processor 230 may perform spatial processing (e.g., precoding) on ​​the data symbols, control symbols, or reference symbols, if applicable, and may provide output symbol streams to modulators (MODs) 232a through 232t. For example, the spatial processing performed on the data symbols, control symbols, or reference symbols may include precoding. Each modulator 232 may process a corresponding output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Additionally or alternatively, each modulator 232 may process the output sample stream (e.g., by analog-converting, amplifying, filtering, and frequency upconverting it) to obtain a downlink signal. The downlink signals from modulators 232a through 232t may be transmitted via antennas 234a through 234t, respectively.

[0061] At UE 115, antennas 252a through 252r may receive downlink signals from base station 105 and may provide received signals to demodulators (DEMODs) 254a through 254r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) a corresponding received signal to obtain input samples. Each demodulator 254 may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 256 may obtain received symbols from demodulators 254a through 254r, perform MIMO detection on the received symbols (if applicable), and provide detected symbols. A receive processor 258 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for UE 115 to a data sink 260, and provide decoded control information to a controller 280, such as a processor.

[0062] On the uplink, at the UE 115, a transmit processor 264 may receive and process data from a data source 262 (e.g., for a physical uplink shared channel (PUSCH)) and control information from a controller 280 (e.g., for a physical uplink control channel (PUCCH)). Additionally, the transmit processor 264 may generate reference symbols for reference signals. The symbols from the transmit processor 264 may be pre-decoded by a TX MIMO processor 266 (if applicable), further processed by modulators 254a through 254r (e.g., for SC-FDM, etc.), and transmitted to the base station 105. At the base station 105, the uplink signal from the UE 115 may be received by the antenna 234, processed by the demodulator 232, detected by the MIMO detector 236 (if applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 115. Receive processor 238 may provide the decoded data to a data sink 239 and the decoded control information to controller 240 .

[0063] The controller 240 and the controller 280 may direct the operation at the base station 105 and the UE 115, respectively. The controller 240 or other processors and modules at the base station 105 or the controller 280 or other processors and modules at the UE 115 may perform or direct the execution of various processes for the techniques described herein, such as performing or directing Figures 1 to 13 Other processes illustrated or described with reference to these figures may be performed or used for the techniques described herein. Memory 242 and memory 282 may store data and program codes for base station 105 and UE 115, respectively. Scheduler 244 may schedule UEs for data transmission on the downlink or uplink.

[0064] In some cases, the UE 115 and the base station 105 may operate in a shared radio spectrum band that may include licensed or unlicensed (e.g., contention-based) spectrum. In the unlicensed frequency portion of the shared radio spectrum band, the UE 115 or the base station 105 may conventionally perform a medium sensing process to compete for access to the spectrum. For example, the UE 115 or the base station 105 may perform a listen-before-talk or listen-before-transmit (LBT) process (such as a clear channel assessment (CCA)) before communicating to determine whether the shared channel is available. In some implementations, the CCA may include an energy detection process to determine whether there are any other active transmissions. For example, the device may infer that a change in the received signal strength indicator (RSSI) of the power meter indicates that the channel is occupied. In particular, a signal power concentrated in a certain bandwidth and exceeding a predetermined noise floor may indicate another wireless transmitter. CCA may also include detection of a specific sequence that indicates the use of the channel. For example, another device may transmit a specific preamble before transmitting a data sequence. In some cases, the LBT process may include the wireless node adjusting its own backoff window based on the amount of energy detected on the channel or acknowledgement / negative acknowledgement (ACK / NACK) feedback for its own transmitted packets (as an indication of a collision).

[0065] Figure 3 A diagram illustrating an example decomposed base station 300 architecture is shown. The decomposed base station 300 architecture may include one or more central units (CUs) 310, which may communicate directly with a core network 320 via a backhaul link, or indirectly through one or more decomposed base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 325 via an E2 link, or a non-real-time (non-RT) RIC 315 associated with a service management and orchestration (SMO) framework 305, or both. The core network 320 may include or correspond to the core network 130. The CUs 310 may communicate with one or more distributed units (DUs) 330 via corresponding midhaul links, such as an F1 interface. The DUs 330 may communicate with one or more radio units (RUs) 340 via corresponding fronthaul links. The RUs 340 may communicate with corresponding UEs 115 via one or more radio frequency (RF) access links. In some implementations, a UE 115 may be served simultaneously by multiple RUs 340.

[0066] Each of the units (i.e., CU 310, DU 330, RU 340, and near-RT RIC 325, non-RT RIC 315, and SMO framework 305) may include one or more interfaces or be coupled to one or more interfaces that are configured to receive or transmit signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units, or an associated processor or controller that provides instructions to the communication interface of these units, may be configured to communicate with one or more of the other units via the transmission medium. For example, these units may include a wired interface that is configured to receive signals or transmit signals to one or more of the other units via a wired transmission medium. In addition, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as a radio frequency (RF) transceiver) that is configured to receive signals or transmit signals to one or more of the other units via a wireless transmission medium, or both.

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

[0068] The DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 340. In some aspects, the DU 330 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more higher physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) based at least in part on a functional split, such as those defined by the 3rd Generation Partnership Project (3GPP). In some aspects, the DU 330 may also host one or more lower PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by the DU 330 or with control functions hosted by the CU 310.

[0069] Lower layer functionality may be implemented by one or more RUs 340. In some deployments, a RU 340 controlled by a DU 330 may correspond to a logical node that hosts RF processing functionality or low PHY layer functionality (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 340 may be implemented to handle over-the-air (OTA) communications with one or more UEs 115. In some implementations, both real-time and non-real-time aspects of control and user plane communications with the RU 340 may be controlled by the corresponding DU 330. In some scenarios, this configuration may enable the implementation of the DU 330 and CU 310 in a cloud-based RAN architecture (such as a vRAN architecture).

[0070] The SMO framework 305 can be configured to support RAN deployment and provisioning of both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 305 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via an operations and maintenance interface (such as the O1 interface). For virtualized network elements, the SMO framework 305 can be configured to interact with a cloud computing platform (such as Open Cloud (O-Cloud) 390) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as the O2 interface). Such virtualized network elements can include, but are not limited to, CU 310, DU 330, RU 340, and near-RT RIC 325. In some implementations, the SMO framework 305 can communicate with hardware aspects of the 4G RAN (such as Open eNB (O-eNB) 311) via the O1 interface. Additionally, in some implementations, the SMO framework 305 can communicate directly with one or more RUs 340 via the O1 interface. The SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of the SMO framework 305 .

[0071] The non-RT RIC 315 can be configured to include logic that enables non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 325. The non-RT RIC 315 can be coupled to or in communication with the near-RT RIC 325 (e.g., via an A1 interface). The near-RT RIC 325 can be configured to include logic that enables near-real-time control and optimization of RAN elements and resources through data collection and actions over an interface (e.g., via an E2 interface) that connects one or more CUs 310, one or more DUs 330, or both, and the O-eNB with the near-RT RIC 325.

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

[0073] As described herein, a node (which may be referred to as a node, network node, network entity, or wireless node) may include, may be, or may be included in (e.g., as a component of) a base station (e.g., any base station described herein), a transmit / receive point (TRP), a UE (e.g., any UE described herein), a network controller, an apparatus, a device, a computing system, an integrated access and backhaul (IAB) node, a distributed unit (DU), a central unit (CU), a remote unit (RU), a core network, an LFM, a server, and / or another processing entity configured to perform any of the techniques described herein. For example, the network node may be a UE. In another example, the network node may be a base station or a network entity. In another example, a first network node may be configured to communicate with a second network node or a third network node. In one aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a UE. In another aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a base station. In yet other aspects of this example, the first network node, the second network node, and the third network node may be different from these examples. Similarly, references to a UE, a base station, an apparatus, a device, a computing system, etc., may include disclosure of the UE, base station, apparatus, device, or computing system, etc., as a network node. For example, a disclosure that a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node. Consistent with the present disclosure, once a specific example is expanded upon according to the present disclosure (e.g., a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node), a broader example of the narrower example may be interpreted inversely, but in a broad, open-ended manner. In the above example where a UE is configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node, the first network node may refer to a first UE, a first base station, a first apparatus, a first device, a first computing system, a first one or more components, a first processing entity, etc., configured to receive information; and the second network node may refer to a second UE, a second base station, a second apparatus, a second device, a second computing system, a second one or more components, a second processing entity, etc.

[0074] As described herein, different terms may be used in various aspects to describe the communication of information (e.g., any information, signal, etc.). Disclosure of one communication term includes disclosure of the other communication terms. For example, a first network node may be described as being configured to send information to a second network node. In this example and consistent with the present disclosure, disclosure that the first network node is configured to send information to the second network node includes disclosure that the first network node is configured to provide, transmit, output, communicate, or send information to the second network node. Similarly, in this example and consistent with the present disclosure, disclosure that the first network node is configured to send information to the second network node includes disclosure that the second network node is configured to receive, obtain, or decode information provided, transmitted, output, communicated, or sent by the first network node.

[0075] Figure 4 is a block diagram of an example wireless communication system 400 that supports a safety system according to one or more aspects. In some examples, the wireless communication system 400 can implement aspects of the wireless network 100. Additionally or alternatively, the wireless communication system 400 can include or correspond to a vulnerable road user (VRU) alert system. The wireless communication system 400 includes a UE 115, a vehicle 450, a network entity 405, and a server 480. In some implementations, the vehicle 450 can include or correspond to a Figure 1 UEs 115i, 115j, 115k. In some implementations, the network entity 405 and the server 480 may be individually or collectively referred to as a network, a network device, or a network system (e.g., a security system). Although one UE 115, one vehicle 450, one network entity 405, and one server 480 are illustrated, in some other implementations, the wireless communication system 400 may generally include multiple UEs 115, multiple vehicles 450, multiple network entities 405, multiple servers 480, or a combination thereof.

[0076] In some implementations, the wireless communication system 400 includes a V2X wireless communication system. V2X is a communication system in which information is transmitted between a vehicle and other entities within a wireless communication network that provides V2X services. V2X services may include services for vehicle-to-vehicle (V2V), vehicle-to-pedestrian (V2P), vehicle-to-infrastructure (V2I), and vehicle-to-network (V2N). One or more V2X standards are intended to develop or support advanced driver assistance systems (ADAS) that assist drivers in making critical decisions such as lane changes, speed changes, overtaking speeds, etc. Low-latency communication can be used in V2X and is therefore suitable for precise positioning. For example, assistance from V2X can be used to enhance positioning techniques such as time of arrival (TOA), time difference of arrival (TDOA), or observed time difference of arrival (OTDOA) or any other cellular positioning technology.

[0077] Generally speaking, there can be at least two operating modes for V2X services, as defined in 3rd Generation Partnership Project (3GPP) TS 23.285. One operating mode uses direct wireless communication between V2X entities when they are within range of each other. The other operating mode uses network-based wireless communication between the entities. These two operating modes can be combined, or other operating modes can be used if desired.

[0078] The wireless communication of the V2X wireless communication system can be through the Proximity-based Services (ProSe) Direct Communication (PC5) reference point as defined in 3GPP TS23.303, and can use wireless communication according to the Institute of Electrical and Electronics Engineers (IEEE) 1609, Wireless Access in Vehicular Environments (WAVE), Intelligent Transportation Systems (ITS) and IEEE 802.11p, on the 5.9 GHz ITS band or other wireless connections directly between entities.

[0079] In some implementations, the wireless communication system 400 is associated with a geographic area 476. The geographic area 476 can include one or more roads, each of which includes at least one intersection 478. The intersection 478 can be any type of intersection, such as a T-intersection, a +-intersection, a Y-intersection, a roundabout, or other types of intersections. In addition, the one or more roads can be associated with multiple paths, each of which leads to or enters the intersection 478. For example, one or more paths can be configured for vehicle traffic, pedestrian traffic, or a combination thereof. The one or more roads or one or more paths can be linear, non-linear, curved, or a combination thereof. For illustration, as illustrative and non-limiting examples, one or more paths can be associated with a road, a car lane, a bus lane, a bicycle lane, a sidewalk, or a combination thereof.

[0080] In some implementations, the UE 115, the network entity 405, and the vehicle 450 may be located within the geographic area 476. Although each of the UE 115, the network entity 405, and the vehicle 450 is described and illustrated as being located within the geographic area 476, in other implementations, one or more of the UE 115, the network entity 405, or the vehicle 450 may be located outside the geographic area 476. Additionally or alternatively, the UE 115 or the vehicle 450 may be traveling toward or located within the intersection 478. In some implementations, the UE 115, the vehicle 450, or both are mobile devices. The network entity 405 may include a base station (such as the base station 105), an access point, a roadside unit, another UE or vehicle, or a portion of a core network (such as the core network 130). The network entity 405 may be stationary or mobile. The server 480 may include a server, a base station 105, the core network 130, or other devices or systems. For example, the server 480 includes a car-to-cloud (C2C) server. In some implementations, the server 480 includes the LMF 131.

[0081] In some implementations, the UE 115, the vehicle 450, or both are configured to communicate with the network entity 405 using a sidelink (SL) link / interface (e.g., using sidelink communication) or a Uu link / interface (e.g., using Uu communication). The server 480 can communicate with (e.g., be communicatively coupled to) the UE, the vehicle 450, or the network entity 405 via a cellular network. The server 480 can be configured to be aware of the situational awareness (e.g., location, heading angle, speed, etc.) of the UE 115 or the vehicle 450 based on information such as vehicle / VRU, based on basic safety message (BSM) messages (for the vehicle 450), and based on pedestrian safety message (PSM) messages (for the UE 115). Additionally or alternatively, as an illustrative, non-limiting example, server 480 may be aware of a map of geographic area 476 or a map associated with the geographic area, such as a map indicating the nature of local intersections (e.g., 478), stop signs, traffic lights, or other information in the geographic area.

[0082] UE 115 may include a device such as a mobile device or a vehicle. In some specific implementations, UE 115 is a device corresponding to a VRU. UE 115 may include various components (such as structural components, hardware components) for performing one or more functions described herein. For example, these components may include one or more processors 402 (hereinafter collectively referred to as "processors 402") and one or more memory devices 404 (hereinafter collectively referred to as "memory 404"). In some specific implementations, UE 115 may include an interface (e.g., a communication interface) that includes a transmitter 416, a receiver 418, or a combination thereof. The processor 402 may be configured to execute instructions 407 stored in the memory 404 to perform the operations described herein. In some specific implementations, the processor 402 includes or corresponds to one or more of the receive processor 258, the transmit processor 264, and the controller 280, and the memory 404 includes or corresponds to the memory 282.

[0083] Memory 404 includes or is configured to store instructions 407 and information 406. Information 406 may include capability information, location information, travel information, or a combination thereof. As illustrative, non-limiting examples, information 406 may include or indicate location or position (e.g., latitude, longitude, elevation, etc.), position accuracy, heading angle, speed, velocity, altitude, device status, path history, predicted path, planned plan, ID, time, steering wheel angle, acceleration, yaw rate, braking system status, device or vehicle size (e.g., length, width, height, weight, etc.), event flags, or a combination thereof.

[0084] The UE 115 includes one or more transmitters 416 (hereinafter collectively referred to as "transmitters 416") and one or more receivers 418 (hereinafter collectively referred to as "receivers 418"). The transmitter 416 is configured to transmit reference signals, control information, and data to one or more other devices, and the receiver 418 is configured to receive reference signals, synchronization signals, control information, and data from one or more other devices. For example, the transmitter 416 may transmit signaling, control information, and data to the base station 105, the network entity 405, the vehicle 450, or another UE 115, and the receiver 418 may receive signaling, control information, and data from the base station, the network entity, the vehicle, or the other UE. In some implementations, the transmitter 416 and the receiver 418 may be integrated into one or more transceivers. Additionally or alternatively, the transmitter 416 or the receiver 418 may include or correspond to a reference signal. Figure 2 One or more components of the UE 115 are described.

[0085] In some implementations, the UE 115 may include one or more antenna arrays. The one or more antenna arrays may be coupled to the transmitter 416, the receiver 418, or the communication interface. The antenna array may include multiple antenna elements configured to perform wireless communications with other devices (such as with the base station 105). In some implementations, the antenna array may be configured to perform wireless communications using different beams (also referred to as antenna beams). The beams may include a TX beam and an RX beam. For illustration, the antenna array may include multiple independent sets (or subsets) of antenna elements (or multiple independent antenna arrays), and each set of antenna elements of the antenna array may be configured to communicate using a different corresponding beam, which may have a different corresponding direction than the other beams. For example, a first set of antenna elements of the antenna array may be configured to communicate via a first beam having a first direction, and a second set of antenna elements of the antenna array may be configured to communicate via a second beam having a second direction. In other implementations, the antenna array may be configured to communicate via more than two beams. Alternatively, one or more sets of antenna elements of the antenna array may be configured to concurrently generate multiple beams, for example, using multiple RF chains of the UE 115. Each separate set (or subset) of antenna elements may include multiple antenna elements, such as two antenna elements, four antenna elements, ten antenna elements, twenty antenna elements, or any other number greater than two. Although described as an antenna array, in other implementations, the antenna array may include or correspond to multiple antenna panels, and each antenna panel may be configured to communicate using a different corresponding beam.

[0086] UE 115 may include one or more components as described herein with reference to UE 115. In some implementations, UE 115 is a 5G-capable UE, a 6G-capable UE, or a combination thereof.

[0087] Vehicle 450 may include a device such as a mobile device or a vehicle. For example, vehicle 450 may include or correspond to Figure 1 UE 115i, 115j, 115k. The vehicle 450 may include various components (such as structural components, hardware components) for performing one or more functions described herein. For example, these components may include one or more processors 442 (hereinafter collectively referred to as "processor 442") and one or more memory devices 444 (hereinafter collectively referred to as "memory 444"). The processor 442 and the memory 444 may include or correspond to the processor 402 and the memory 404, respectively. In some specific implementations, the vehicle 450 may include an interface (e.g., a communication interface) that includes a transmitter 446, a receiver 448, or a combination thereof. The transmitter 446 and the receiver 448 may include or correspond to the transmitter 416 and the receiver 418, respectively. The processor 442 may be configured to execute instructions 452 stored in the memory 444 to perform the operations described herein. In some specific implementations, the processor 442 includes or corresponds to one or more of the receive processor 258, the transmit processor 264, and the controller 280, and the memory 444 includes or corresponds to the memory 282.

[0088] Memory 444 includes or is configured to store instructions 452 and information 454. Instructions 452 may include or correspond to instructions 407. Information 454 may include or correspond to information 406. Information 454 may include capability information, location information, travel information, or a combination thereof. As illustrative, non-limiting examples, information 406 may include or indicate location or position (e.g., latitude, longitude, elevation, etc.), position accuracy (e.g., horizontal estimated position error (HEPE)), heading angle, speed, velocity, altitude, device status, path history, predicted path, planned route, ID, time, steering wheel angle, acceleration, yaw rate, braking system status, device or vehicle size (e.g., length, width, height, weight, etc.), event flags, or a combination thereof.

[0089] The vehicle 450 includes one or more transmitters 446 (hereinafter collectively referred to as "transmitters 446") and one or more receivers 448 (hereinafter collectively referred to as "receivers 448"). The transmitter 446 is configured to transmit reference signals, control information, and data to one or more other devices, and the receiver 448 is configured to receive reference signals, synchronization signals, control information, and data from one or more other devices. For example, the transmitter 446 may transmit signaling, control information, and data to the base station 105, the network entity 405, another vehicle 450, or the UE 115, and the receiver 448 may receive signaling, control information, and data from the base station, the network entity, the other vehicle, or the UE. In some implementations, the transmitter 446 and the receiver 448 may be integrated into one or more transceivers. Additionally or alternatively, the transmitter 446 or the receiver 448 may include or correspond to a reference signal. Figure 2 One or more components of the UE 115 are described.

[0090] In some implementations, the vehicle 450 may include one or more antenna arrays. The one or more antenna arrays may be coupled to the transmitter 446, the receiver 448, or the communication interface. The antenna array may include multiple antenna elements configured to perform wireless communications with other devices (such as with the base station 105). In some implementations, the antenna array may be configured to perform wireless communications using different beams (also referred to as antenna beams). The beams may include a TX beam and an RX beam. For example, the antenna array may include multiple independent sets (or subsets) of antenna elements (or multiple independent antenna arrays), and each set of antenna elements of the antenna array may be configured to communicate using a different corresponding beam, which may have a different corresponding direction than the other beams. For example, a first set of antenna elements of the antenna array may be configured to communicate via a first beam having a first direction, and a second set of antenna elements of the antenna array may be configured to communicate via a second beam having a second direction. In other implementations, the antenna array may be configured to communicate via more than two beams. Alternatively, one or more sets of antenna elements of the antenna array may be configured to concurrently generate multiple beams, for example, using multiple RF chains of the vehicle 450. Each separate set (or subset) of antenna elements may include multiple antenna elements, such as two antenna elements, four antenna elements, ten antenna elements, twenty antenna elements, or any other number greater than two. Although described as an antenna array, in other implementations, the antenna array may include or correspond to multiple antenna panels, and each antenna panel may be configured to communicate using a different corresponding beam.

[0091] The vehicle 450 can include one or more components as described herein with reference to the UE 115. In some implementations, the vehicle 450 is a 5G-capable vehicle, a 6G-capable vehicle, or a combination thereof.

[0092] The network entity 405 may include a device such as a base station, a roadside unit, a node, or another UE. The network entity 405 may be a mobile device or a stationary device. The network entity 405 may include various components (such as structural components, hardware components) for performing one or more functions described herein. For example, these components may include one or more processors 422 (hereinafter collectively referred to as "processor 422") and one or more memory devices 424 (hereinafter collectively referred to as "memory 424"). In some specific implementations, the network entity 405 may include an interface (e.g., a communication interface) that includes a transmitter 426, a receiver 428, or a combination thereof. The processor 422 may be configured to execute instructions 430 stored in the memory 424 to perform the operations described herein. In some specific implementations, the processor 422 includes or corresponds to one or more of the receive processor 238, the transmit processor 220, and the controller 240, and the memory 424 includes or corresponds to the memory 242.

[0093] Memory 424 includes or is configured to store instructions 430 and information 434. Information 434 may include or correspond to information 406 or 454. For example, network entity 405 may be configured to receive UE information 490 including or indicative of information 406 from UE 115. As another example, network entity 405 may be configured to receive vehicle information 492 including or indicative of information 454 from vehicle 450.

[0094] The network entity 405 includes one or more transmitters 426 (hereinafter collectively referred to as "transmitters 426") and one or more receivers 428 (hereinafter collectively referred to as "receivers 428"). The transmitter 426 is configured to transmit reference signals, control information, and data to one or more other devices, and the receiver 428 is configured to receive reference signals, synchronization signals, control information, and data from one or more other devices. For example, the transmitter 426 may transmit signaling, control information, and data to the base station 105, the UE 115, the vehicle 450, another network entity 405, or the server 480, and the receiver 428 may receive signaling, control information, and data from the base station, the UE, the vehicle, the another network entity, or the server. In some implementations, the transmitter 426 and the receiver 428 may be integrated into one or more transceivers. Additionally or alternatively, the transmitter 426 or the receiver 428 may include or correspond to a reference signal. Figure 2 One or more components of base station 105 are described.

[0095] In some implementations, the network entity 405 may include one or more antenna arrays. The one or more antenna arrays may be coupled to the transmitter 426, the receiver 428, or the communication interface. The antenna array may include multiple antenna elements configured to perform wireless communications with other devices (such as with the UE 115 or the base station 105). In some implementations, the antenna array may be configured to perform wireless communications using different beams (also referred to as antenna beams). The beams may include a TX beam and an RX beam. For example, the antenna array may include multiple independent sets (or subsets) of antenna elements (or multiple independent antenna arrays), and each set of antenna elements of the antenna array may be configured to communicate using a different corresponding beam, which may have a different corresponding direction than the other beams. For example, a first set of antenna elements of the antenna array may be configured to communicate via a first beam having a first direction, and a second set of antenna elements of the antenna array may be configured to communicate via a second beam having a second direction. In other implementations, the antenna array may be configured to communicate via more than two beams. Alternatively, one or more sets of antenna elements of the antenna array may be configured to concurrently generate multiple beams, for example using multiple RF chains of the network entity 405. Each separate set (or subset) of antenna elements may include multiple antenna elements, such as two antenna elements, four antenna elements, ten antenna elements, twenty antenna elements, or any other number greater than two. Although described as an antenna array, in other implementations, the antenna array may include or correspond to multiple antenna panels, and each antenna panel may be configured to communicate using a different corresponding beam.

[0096] The network entity 405 may include one or more components as described herein with reference to the UE 115 or the base station 105. In some implementations, the network entity 405 is a 5G-capable network entity, a 6G-capable network entity, or a combination thereof.

[0097] The server 480 may include various components (such as structural components, hardware components) for performing one or more functions described herein. For example, these components may include one or more processors 482 (hereinafter collectively referred to as "processors 482"), one or more memory devices 484 (hereinafter collectively referred to as "memory 484"), and one or more communication devices 475 (hereinafter collectively referred to as "communication devices 475"). In some specific implementations, the server 480 may include an interface (e.g., a communication interface) that includes the communication device 475. The processor 482 may be configured to execute instructions 486 stored in the memory 484 to perform the operations described herein. In some specific implementations, the processor 482 includes or corresponds to one or more of the receive processor 238, the transmit processor 220, and the controller 240, and the memory 484 includes or corresponds to the memory 242.

[0098] The memory 384 includes or is configured to store instructions 486 , map data 488 , intersection information 499 , path information 497 , travel information 494 , and one or more thresholds 496 (hereinafter collectively referred to as “thresholds 496 ”).

[0099] Map data 488 may include or indicate aspects or features of geographic area 476. As illustrative, non-limiting examples, map data 488 may include or indicate roads, intersections, traffic control devices, geographic features, hazards, or a combination thereof. In some implementations, map data 488 may include intersection information 499, path information 497, or a combination thereof. For example, map data 488 may include an intersection (e.g., 478) and may include metadata associated with the intersection. The metadata may include intersection information 499, path information 497, or a combination thereof. Although described as being included in server 480, in other implementations, map data 488 may be stored in a database remote from server 480 or accessible to the server.

[0100] Intersection information 499 can be associated with one or more intersections, such as intersection 478. For example, intersection information 499 can include or indicate information defining or characterizing an intersection zone associated with intersection 478. The intersection zone can be defined as the same or a different size or shape than intersection 478. In some implementations, as illustrative and non-limiting examples, intersection information 499 can indicate or define the size, shape, origin, length, roadway, traffic control device, geographic feature, hazard, or a combination thereof for intersection 478, an intersection zone associated with intersection 478, or both.

[0101] Path information 497 includes or indicates one or more paths associated with an intersection zone (such as an intersection zone associated with intersection 478). In some implementations, at least one of the one or more paths is a curved path, such as a nonlinear path. Each of the one or more paths can have an endpoint located or positioned within intersection 478 or an intersection zone associated with intersection 478. Additionally or alternatively, path information 497 can include one or more path models, wherein each of the one or more path models is configured to model a different path. For example, path information 497 can include or indicate a first path 481 (e.g., a first path model) and a second path 485 (e.g., a second path model). The first path model of first path 481 can define a first set of line segments (such as a plurality of line segments) to model first path 481, and a first line segment in the first set of line segments includes a first endpoint located at a first location within intersection 478 or an intersection zone associated with intersection 478. The second path model of second path 485 may define a second set of line segments to model second path 485, and a second line segment in the second set of line segments may include a second endpoint located at a second location in intersection 478 or an intersection zone associated with intersection 478. The first location and the second location may be the same location or different locations. For example, the first location and the second location may both be the origin of intersection 478 or the intersection zone associated with intersection 478.

[0102] Each path model of the path information 497 can be configured to model a different path in the one or more paths. For example, each path model can include a data structure defining a set of segments (such as a set of one or more segments) of the path model. For example, the first path 481 includes segment information 483 indicating or defining a set of one or more segments of the first path 481. Figure 6 An example of a data structure for a path model is further described. Additionally or alternatively, each path model can include at least one line segment in the path model's line segment set having an endpoint located in intersection 478 or an intersection region of intersection 478. In some implementations, for each line segment in the path model's line segment set, each path model defines a segment identifier (ID) of the line segment, a first endpoint of the line segment, a second endpoint of the line segment, an azimuth of the line segment, a segment length of the line segment, or a combination thereof.

[0103] Travel information 494 may include or indicate travel or location information for UE 115, vehicle 450, or a combination thereof. For example, travel information 494 may include or indicate information 406, 434, or 454, UE information 490, or vehicle information 492. Additionally or alternatively, travel information 494 may include or indicate a first entity 487 (such as UE 115) and a second entity 491 (such as vehicle 450). First entity 487 may include or indicate information 406 or UE information 490 associated with UE 115. Second entity 491 may include or indicate information 454 or vehicle information 492 associated with vehicle 450. In some implementations, travel information 494 may include or indicate a path, path model, or line segment associated with or assigned to an entity. For example, first entity 487 may include or indicate path 489, which is assigned to first entity 487 (e.g., UE 115) to model the first entity's path. For illustration, the path 489 may include or correspond to the first path 481 (eg, the first path model) or the second path 485 (eg, the second path model).

[0104] Threshold 496 may include or indicate one or more values, one or more ranges, or a combination thereof. Threshold 496 may be associated with time, duration, heading angle, distance, or a combination thereof.

[0105] In some implementations, the wireless communication system 400 implements a 5G NR network. For example, the wireless communication system 400 may include a plurality of 5G-capable UEs 115, a plurality of 5G-capable vehicles 450, a plurality of 5G-capable network entities 405, and a plurality of 5G-capable base stations 105, such as UEs and base stations configured to operate according to a 5G NR network protocol, such as that defined by 3GPP. In some other implementations, the wireless communication system 400 implements a 6G network.

[0106] In some implementations, server 480 is configured to generate or use a piecewise linearization of a curved or straight path leading to intersection 478. The piecewise linearization may include or correspond to a path model, such as first path 481 (e.g., first path model). Note that the generation or use of the path model may be map-aware, such that the path model is generated based on, associated with, or included in map data 488. To generate the path model, server 480 may be configured to linearize the curved path into one or more smaller linear segments. For example, server 480 may divide the path into multiple segments to approximate the expected heading angle of an entity to be constant within a segment. Server 480 may store segment details of the path as a data structure that can be used to determine which path an entity (e.g., UE 115 or vehicle 450) is on. The data structure may include or indicate relationships between the multiple segments, such that the multiple segments can model abrupt changes in heading angle from one segment to the next. The segment details may include or correspond to segment information 483.

[0107] refer to Figure 5 , Figure 5 488 is a diagram illustrating an example of a map supporting a safety system according to one or more aspects. The map may include or correspond to map data 488.

[0108] The map includes one or more roads, such as road 502. The map also indicates an intersection region 578, such as the intersection region associated with intersection 478. Intersection region 578 includes an origin at location 510.

[0109] The map also indicates a path model 520 (e.g., a first path model) for a curved path. The path model may include or correspond to the first path 481. The path model 520 may model the curved path as three piecewise linear segments, such as a first segment (seg-1) 531, a second segment (seg-2) 532, and a third segment (seg-3) 533. The first segment (seg-1) 531, the second segment (seg-2) 532, and the third segment (seg-3) 533 may include or correspond to the segment information 483. The first segment (seg-1) 531 may extend between the origin (at position 510) and position 522. The second segment (seg-2) 532 may extend between position 522 and position 524. The third segment (seg-3) 533 may extend between position 524 and position 526. Note that the first segment (seg-1) 531, the second segment (seg-2) 532, and the third segment (seg-3) 533 approximate the path of travel that could be taken by an entity traveling from location 526 to the origin (at location 510) through the curved path.

[0110] Return Reference Figure 4 , the server 480 may generate a data structure including or indicating a path model (such as path model 520). For example, the server 480 may perform map-aware modeling of one or more segments of the path. In some implementations, the server 480 may determine the endpoints (or origins) and lengths of each segment of the path. For illustration, let t ij ,X ij =(x ij ,y ij ) are the length and coordinates of segment-j of path-i respectively. The coordinates of the first segment in the path are taken as the origin (i.e., In some implementations, the origin is a location included in the intersection zone or a location identified as the origin of the intersection zone. The coordinates of segment-j (j>1) of path-i can be expressed as:

[0111]

[0112] where α ij Denotes the azimuth (heading angle) of segment-j of path-i away from the origin. Once the length of each segment in the path is determined (or obtained from a map), the coordinates of the segment of the path can be obtained based on the path model.

[0113] refer to Figure 6 , Figure 6 is a table illustrating an example data structure 600 for supporting a path model for a safety system according to one or more aspects. The data structure 600 may include or correspond to the path information 497 , the first path 481 , the segment information 483 , or the second path 485 , or the map data 488 .

[0114] The data structure 600 includes a plurality of entries, each of which corresponds to a segment. Each entry includes a segment number, an origin, an azimuth, and a segment length. Note that the data structure 600 includes a notation for segment-j of path-i, which denotes the segment number as Seg-ij, the origin position as X, and the segment length as X. ij , denote the azimuth angle as α ij And denote the segment length as t ij .

[0115] Return Reference Figure 4, intersection information 499, path information 497, or a combination thereof may be included in map data 488 or stored as part of the map data. In some such implementations, the origin of intersection 478 (or intersection area) may be designated as origin O. For example, origin O may include or correspond to location 510. The origin of intersection 478 may be the geometric center of intersection 478 or intersection area or another point. In some implementations, multiple paths may meet or intersect at origin O. For example, all paths associated with intersection 478 or intersection area may meet at origin O. In other implementations, one path or no paths meet or are located at origin O. In some such implementations, each path model may include or indicate a corresponding location included in or intersecting intersection 478 or intersection area.

[0116] In some implementations, intersection information 499, path information 497, or a combination thereof can be included in or stored as part of map data 488 as metadata associated with intersection 478. In some implementations, the metadata can include or indicate a data structure, such as data structure 600, for each path that intersects intersection 478 or the intersection zone. Additionally or alternatively, the metadata can include or indicate the origin O of intersection 478, one or more traffic control devices (e.g., a stop sign, speed bump, etc., present at each path-i near the origin of intersection 478), or a combination thereof.

[0117] refer to Figure 7 , Figure 7 is a diagram illustrating another example of a map supporting a safety system according to one or more aspects. Figure 7 The map may include or correspond to map data 488. Additionally or alternatively, Figure 7 The map may include or correspond to Figure 5 Map.

[0118] and Figure 5 Compared to the map, Figure 7 The map of shows additional modeling paths, for example, additional path models in addition to the first path model 520. For example, Figure 7The map includes a second path model 721, a third path model 722, a fourth path model 740, and a fifth path model 760. Each of the second path model 721 and the third path model 722 includes two segments. Note that the origin of each of the second path model 721 and the third path model 722 is different from the location 510, such as the origin of the intersection area 578. For illustration, the third path model 722 includes an endpoint at the location 723. The fourth path model 740 includes two segments and has an endpoint at the location 510. The fifth path model 760 includes a single segment with an endpoint at the location 510. Each of the first path model 520, the second path model 721, the third path model 722, the fourth path model 740, and the fifth path model 760 can be represented or defined based on a data structure, such as the data structure 600.

[0119] Reference again Figure 4 , the server 480 can be configured to identify an intersection 478 or intersection zone based on the intersection for an entity such as a UE 115 or a vehicle 450. For example, in some implementations, the server 480 can identify the intersection closest to the entity. For example, the intersection 478 or the intersection information 499 can include or indicate an origin associated with the intersection 478. j ) represents the intersection origin I j (e.g., 478), and the location of the entity (e.g., 115 or 450) is represented as V, the server 480 may determine the number of nodes from V to O (I j ) of the intersection k with the minimum distance. That is, k = arg min j d(V,O(I j )), where d() is an appropriate distance measure. In some implementations, the closest intersection can be the closest intersection in the direction of travel of the entity or within a threshold range of the direction of travel of the entity. In some other implementations, the server 480 can determine the intersection k using situational awareness information obtained from the entity (such as a camera, radar) or other equipment of the entity. For illustration, the entity can be closest to or at a first intersection, and the situational awareness information can indicate that there are no other entities or no other entities are adjacent to the first intersection. In some such cases, the server 480 can identify a second intersection, such as the next intersection in the direction of travel of the entity. The server 480 can determine the path associated with the entity based on the second intersection.

[0120] In some implementations, the server 480 is configured to identify paths associated with an entity (e.g., a UE 115 or a vehicle 450). For illustration, the server 480 may assign the entity to a path model based on location or travel information associated with the entity, and use the assigned path model to estimate or predict one or more locations of the entity. For example, based on the location of entity E (e.g., a noise location), the paths and segments to which entity E belongs (or is assigned) may be obtained by minimizing the vertical distance between entity E and all modeled paths associated with intersection k. In some implementations, the vertical distance may be a distance in a direction perpendicular to the heading angle of entity E. The server 480 may select the path model to be assigned to entity E as the path model having the smallest vertical distance to entity E. For example, referring to Figure 8 , Figure 8 is a diagram illustrating another example of a map supporting a safety system according to one or more aspects.

[0121] Figure 8 The map may include or correspond to map data 488. Additionally or alternatively, Figure 8 The map may include or correspond to Figure 5 Map or Figure 7 Map of . Figure 7 Compared to the map, Figure 8 The map includes entities, such as a first entity 881 , a second entity 882 , and a third entity 883 .

[0122] First entity 881 is assigned to first path model 520. For illustration, server 480 may determine a direction of travel or heading angle (indicated by arrow 891) of first entity 881. Server 480 may determine (in a direction perpendicular to the heading angle indicated by arrow 891) the distance from the first entity to each path modeled by a path model associated with intersection zone 578. Based on the perpendicular distances, server 480 may determine that a path, segment, or both of first path model 520 is closest to first entity 881 and may assign first path model 520 to first entity 881. Additionally, server 480 may determine that second entity 882 is included in intersection zone 578 and may forgo or refrain from identifying a path model to be assigned to second entity 882. Server 480 may determine that third entity 883 is closest to fourth path model 740.

[0123] Based on the server 480 assigning the first entity 881 to the first path model, the server 480 can estimate the distance from the first entity 881 to the intersection zone 578 or the amount of time it will take for the first entity 881 to reach the intersection zone 578. For example, the server 480 can use the shortest distance (directly or perpendicular to the direction of travel of the first entity) to determine a location on a segment of the first path model 520. The server 480 can use the determined location on the segment of the first path model 520 to estimate the distance from the first entity 881 to the intersection zone 578 or the amount of time it will take for the first entity 881 to reach the intersection zone 578.

[0124] In some implementations, the server 480 can compare the heading angles of entities, such as the first entity 881, to confirm the identified path pattern. For illustration, β is the heading angle of the first entity 881, and α ij is the azimuth of segment-j of path-i that crosses into intersection zone 578 (or the azimuth plus 180 degrees), where β, α ij Each is a positive angle. Based on the above, if |α ij -β|≤THR1, in the case of a threshold value (eg, 496), the server 480 may determine that the first entity 488 is in the segment-j of the path-i (of the first path model 520). However, if |α ij −β|>THR2, the server 480 may determine that the first entity 480 is not heading toward the intersection area 578 .

[0125] In some implementations, if an entity is within an intersection 478 or an intersection zone 578, the server 480 may not consider the heading angle of the entity (such as the second entity 882). When an entity is positioned within an intersection 478 or an intersection zone 578, the entity is susceptible to colliding with another entity that may enter the intersection 478 or the intersection zone 578 or be present in the intersection or the intersection zone. In some such cases, the server 480 may estimate the amount of time that the entity will remain in the intersection 478 or the intersection zone 578. For example, the server 480 may estimate the amount of time as the amount of time that the entity leaves the farthest point (of the intersection 478 or the intersection zone 578) from the entity. As another example, the server 480 may estimate the amount of time as the amount of time it takes for the entity to traverse the longest linear distance of the intersection 478 or the intersection zone 578.

[0126] Return Reference Figure 4In some implementations, if the HEPE associated with an entity is greater than or equal to a threshold, server 480 may not assign the entity to a path model or a segment of a path model. The HEPE of the entity may include or correspond to information 406, 434, or 454, UE information 490, or vehicle information 492. The threshold may include or correspond to threshold 496.

[0127] In some specific implementations, server 480 is configured to determine or calculate the collision possibility associated with two entities or between two entities. For example, server 480 can determine the collision possibility associated with intersection 478 or the intersection zone (e.g., 578) of intersection 478. For illustration, server 480 can estimate or predict that a first entity (e.g., UE 115) is predicted to be in a time period (e.g., duration) in the intersection zone, the entry time when the first entity enters the intersection zone, the departure time when the first entity leaves the intersection zone, or a combination thereof. Additionally or alternatively, server 480 can estimate or predict that a second entity (e.g., vehicle 450) is predicted to be in a time period (e.g., duration) in the intersection zone, the entry time when the second entity enters the intersection zone, the departure time when the second entity leaves the intersection zone, or a combination thereof. Based on the duration that the first entity and the second entity are predicted to be in the intersection zone at the same time, server 480 can generate or send an alert message, such as alert message 493. In some implementations, server 480 can determine an overlap time, such as a predicted amount of time that two entities are estimated to be in the intersection zone at the same time. Server 480 can generate or send an alert message 493 based on determining that the overlap time is greater than or equal to a threshold (e.g., 496).

[0128] refer to Figure 9 , Figure 9 is a diagram of an example of a timing diagram for two entities supporting a safety system according to one or more aspects. For example, the two entities may include UE 115 and vehicle 450. Figure 9 Four examples are included, such as a first example 910, a second example 920, a third example 930, and a fourth example 940. Each of the examples 910-940 is associated with a predicted likelihood of collision.

[0129] For example, the server 480 is configured to calculate or predict the Where T v1 is the predicted entry time of vehicle 450 at the intersection zone (eg, 578 ), and T v2 is the predicted departure time of the vehicle 450 at the intersection area. As another example, the server 480 is configured to calculate or predict [T b1 ,Tb2 ], where T b1 is the predicted entry time of UE 115 at the intersection zone (e.g., 578), and T b2 is the predicted departure time of UE 115 at the intersection zone. Server 480 may determine the predicted time overlap T between vehicle 450 and UE 115 o The server 480 may be configured to overlap the predicted time T based on the o Greater than or equal to a threshold value (eg, 496) to generate or send an alert message 493.

[0130] refer to Figure 4 , an example of operation of wireless communication system 400 includes UE 115 and vehicle 450 in geographic area 476. UE 115 sends UE information 490. UE information 490 can be received by network entity 405 or server 440. In some implementations, network entity 405 receives UE information 490 and sends UE information 490 to server 480.

[0131] Server 480 receives UE information 490 and stores UE information 490 at travel information 494. For example, server 480 may store UE information 490 at first entity 487. Server 480 may access map data 488 and use map data 488 to identify intersection information 499 based on UE information 490. For example, server 480 may identify an intersection zone associated with intersection 478, which server 480 determines UE 115 is traveling toward. Based on the intersection information and UE information 490, server 480 may identify a path model to assign to UE 115. For example, server 480 may identify a first path 481 (e.g., a first path model) assigned to UE 115 and indicated by path 489. Using the first path model, server 480 may estimate or predict a first time period (e.g., duration) during which UE 115 is predicted to be in the intersection zone, a first entry time for UE 115 to enter the intersection zone, a first exit time for UE 115 to exit the intersection zone, or a combination thereof.

[0132] The vehicle 450 sends the vehicle information 492. The vehicle information 492 can be received by the network entity 405 or the server 440. In some implementations, the network entity 405 receives the vehicle information 492 and sends the vehicle information 492 to the server 480.

[0133] Server 480 receives vehicle information 492 and stores it at travel information 494. For example, server 480 may store vehicle information 492 at second entity 491. Server 480 may access map data 488 and, using map data 488 and based on vehicle information 492, identify intersection information 499. For example, server 480 may identify an intersection zone associated with intersection 478, which server 480 determines vehicle 450 is traveling toward. Based on the intersection information and vehicle information 492, server 480 may identify a path model to assign to vehicle 450. For example, server 480 may identify a second path 485 (e.g., a second path model) assigned to vehicle 450. Using the second path model, the server 480 can estimate or predict a second time period (e.g., duration) that the vehicle information 492 is predicted to be in the intersection zone, a second entry time that the vehicle information 492 enters the intersection zone, a second exit time that the vehicle information 492 exits the intersection zone, or a combination thereof.

[0134] The server 480 can determine or calculate a collision probability associated with or between the UE 115 and the vehicle 450. For example, the server 480 can estimate or predict a collision probability time period (e.g., duration) during which both the UE 115 and the vehicle 450 are predicted to be in the intersection zone. Based on the collision probability time period (e.g., duration of the collision probability time period), the server 480 can generate or send an alert message, such as the alert message 493. In some implementations, the server 480 can generate or send the alert message 493 based on determining that the overlap time is greater than or equal to a threshold (e.g., 496), based on a change characteristic received from the UE 115 or the vehicle 450, or a combination thereof.

[0135] As reference Figure 4As described, the present disclosure provides techniques for supporting sensing billing subscriptions. The described techniques provide processes, information, and signaling for generating an alert message 493 based on a possible collision at an intersection between two entities (e.g., a UE 115 and a vehicle 450) when at least one of the two entities travels along a curved path toward an intersection 478. By providing piecewise linearization to model the curved path, a path model (e.g., path information 497 or first path 481) can be selected and used to effectively estimate the entity's travel toward the intersection 478 even in the presence of high measurement noise. The techniques further provide a data structure (e.g., 600) for defining one or more path models, such that the one or more path models can be stored in association with map data 488. For example, a data structure associated with an intersection 478 included or identified in the map data 488 can be stored as metadata as part of the map data 488. Additionally, the techniques can provide improved entity tracking, improved and more relevant safety alerts, improved power efficiency, a reduction in intersection accidents, or a combination thereof.

[0136] Figure 10 is a flow chart illustrating an example process 1000 for supporting a security system according to one or more aspects. The operations of process 1000 may be performed by a server (such as core network 130, server 480, base station 105, or network entity 405, or as described above with reference to Figure 12 For example, the example operations of process 1000 may enable a server to support a security system.

[0137] At block 1002, a server receives first location information associated with a first mobile entity. For example, the first mobile entity may include or correspond to UE 115 or vehicle 450. The first location information may include or correspond to information 406, 434, or 454, travel information 494, UE information 490, or vehicle information 492.

[0138] At block 1004, the server sends an alert based on the first location information and path information configured to model multiple paths associated with the intersection area. The alert may include or correspond to alert message 493. The intersection may include or correspond to intersection 478, map data 488, or intersection information 499. The path information may include or correspond to path information 497, first path 481, second path 485, path models 520, 721, 722, or 740. The multiple paths may include a curved (e.g., nonlinear) first path. For example, the first path may include or correspond to path models 520, 721, 722, or 740. The path information defines multiple line segments to model the first path. For example, the line segments may include or correspond to segment information 483 or segments 531-533.

[0139] In some specific implementations, the server estimates a first time period based on the first location information and the path information, during which the first mobile entity is predicted to be in the intersection zone. Additionally or alternatively, the server may receive second location information associated with a second mobile entity. For example, the first mobile entity includes one of a vehicle and a UE associated with a pedestrian, and the second mobile entity includes the other of the vehicle and the UE. The server may estimate a second time period based on the second location information and the path information, during which the second mobile entity will be in the intersection zone. The server may be configured to generate an alert based on the overlap of the first time period with the second time period. This document at least refers to Figure 9 An example of overlapping is further described. In some implementations, the server receives an indicator of an alert characteristic from the first mobile entity. For example, the indicator may be included in the UE information 490 or the vehicle information. The alert characteristic may indicate the amount of time before the predicted time at which the first mobile entity is predicted to enter the intersection zone that the alert is transmitted. An alert (e.g., an alert message 493) may be sent to the first mobile entity based on the indicator.

[0140] In some implementations, the path information includes multiple path models. For example, the multiple path models may include or correspond to a first path 481 (eg, a first path model) and a second path 485 (eg, a second path model). Figure 6 Illustrative examples of data structures for path models are described. Each path model in a plurality of path models can be configured to model a different path in a plurality of paths. In some implementations, each path model in the plurality of path models defines a path model segment set and includes at least one segment in the path model segment set having an endpoint located in an intersection zone.

[0141] In some implementations, the plurality of path models include a first path model for a first path in the plurality of paths and a second path model for a second path in the plurality of paths. For example, the first path model may include or correspond to first path 481, and the second path model may include or correspond to second path 485. The first path model may define a plurality of line segments. Additionally or alternatively, a first line segment in the plurality of line segments or associated with the first path may include a first endpoint located at a first location in an intersection area. The second path model may include one or more line segments to model a second path. A second line segment in the one or more line segments may include a second endpoint located at a second location in the intersection area. In some implementations, the first location and the second location are the same location.

[0142] In some implementations, for each path model in the plurality of path models and for each line segment in the set of line segments of the path model, the path model defines a segment ID of the line segment, a first endpoint of the line segment, a second endpoint of the line segment, an azimuth of the line segment, a segment length of the line segment, or a combination thereof. For example, at least one path model of the multi-path model may have at least one path model as described herein with reference to Figure 6 The data structure described.

[0143] In some implementations, the server determines the direction of travel of the first mobile entity and the position of the first mobile entity based on the first location information. For example, the direction of travel may include or correspond to representative arrow 891. Additionally or alternatively, the server may determine the distance from the first mobile entity to the modeled paths of a plurality of path models. To determine the distance, for each path model in the plurality of path models, the server may determine (in a direction perpendicular to the direction of travel) the distance from the position of the first mobile entity to the modeled path of the path model. The server may select the first path model from the plurality of path models that has the shortest distance among the determined distances. In some implementations, the server may assign the first path model to the first mobile entity, for example, based on the first path with the shortest distance. Additionally or alternatively, the server may determine a line segment (associated with the shortest distance) of the selected first path model. In some implementations, the server may determine a difference based on the azimuth of the line segment and the heading angle of the first mobile entity. The server may perform a comparison based on the difference and a first threshold. The first threshold may include or correspond to threshold 496. In some implementations, the assigned first path model can include or correspond to path 489 (eg, a path ID of the first path model).For example, the server can assign the first path model to the first mobile entity based on the result of the comparison.

[0144] In some implementations, the server may estimate the time period during which the first mobile entity is predicted to be in the intersection zone based on the first path model assigned to the first mobile entity. Figure 3 The time period is determined as described. The time period may include or indicate an entry time at which the first mobile entity is predicted to enter the intersection zone, an exit time at which the first mobile entity is predicted to leave the intersection zone, a duration between entry and exit, or a combination thereof. The server may generate an alert based on determining that the first entity is predicted to be in the intersection zone at the same time as the second mobile entity. In some specific implementations, the server receives additional location information associated with the first mobile entity. For example, the additional location information may be received after the first location information. The server may determine that the first mobile entity is within the intersection zone based on the additional location information. The server may estimate the time at which the first mobile entity is predicted to leave the intersection zone based on the size of the intersection zone.

[0145] In some implementations, the server determines a horizontal estimated positioning error associated with the first mobile entity. The horizontal estimated positioning error may include or correspond to information 406, 434, or 545, UE information 490, vehicle information 492, or travel information 494. The server may perform a comparison based on the horizontal estimated positioning error and a second threshold. The second threshold may include or correspond to threshold 496. The first path model may be assigned to the first mobile entity based on the horizontal estimated positioning error being less than or equal to the second threshold.

[0146] In some embodiments, the server identifies intersection zone information associated with the intersection zone based on map data. For example, the intersection zone information may include or correspond to intersection information 499. In some embodiments, the server is configured to select the intersection zone (or intersection zone information) based on the first location information. For example, the intersection zone may be selected based on the distance between the first location associated with the first mobile entity and the second location associated with the intersection zone, the direction of travel of the first mobile entity, situational awareness information included in the first location information, or a combination thereof. The map data may include or correspond to map data 488. In some such embodiments, the server may access the map data. The intersection zone information may be stored as metadata of the map data. Additionally or alternatively, the intersection zone information may indicate an origin location associated with the intersection zone, one or more paths associated with the intersection zone, one or more traffic control devices associated with the intersection zone, path information, or a combination thereof.

[0147] Figure 11is a flow chart illustrating an example process 1100 for supporting a security system according to one or more aspects. The operations of process 1100 may be performed by a server (such as core network 130 or server 480, base station 105 or network entity 405, or as described above with reference to Figure 12 For example, the example operations of process 1100 may enable a server to support a security system.

[0148] At block 1102 , the server identifies an intersection based on map data. The map data may include or correspond to map data 488 . In some implementations, the server receives and stores the map data. The intersection may include or correspond to intersection 478 .

[0149] At block 1104, the server determines a path model for a path associated with the intersection. In some implementations, to determine the path model, the server identifies a path based on map data, such as a path leading to or entering intersection 478. For example, the server can use image or object recognition to identify or generate a path based on map data. In some implementations, as illustrative and non-limiting examples, the server can identify or generate a path based on roads, traffic markings (e.g., lane markings, crosswalks, bike lane markings, bus lane markings, etc.), sidewalks, curbs, or other features. Additionally or alternatively, the server can identify multiple paths.

[0150] Based on the identified path, the server can generate a path model for the path. The path model can include a data structure such as at least one of the data structures described herein. Figure 6 In some implementations, to generate a path model, the server determines whether a change in a heading angle of a path (e.g., an object traveling along the path) from endpoint to endpoint is greater than or equal to a threshold. If the change in heading angle is greater than or equal to the threshold, the server performs piecewise linearization of the path to generate a plurality of segments to model the path.

[0151] At block 1106, the server stores path information indicating the path model. For example, the server may store path information 497 including or indicating the first path 481 (e.g., the first path model). In some implementations, the path model or path information may be stored as metadata of the map data.

[0152] Figure 12 is a block diagram of an example server 1200 supporting a security system according to one or more aspects. The server 1200 may be configured to perform operations including reference Figure 10 and Figure 11In some implementations, the server 1200 includes the structure, hardware, and components shown and described with reference to the base station 105 or the core network 130. For example, the server 1200 may include a controller 240 to execute logic or computer instructions stored in a memory 242 and to control components of the server 1200 that provide features and functionality of the server 1200. The server 1200 transmits and receives signals via wireless radio components 1201a-t and antennas 234a-t under the control of the controller 240. The wireless radio components 1201a-t include the following: Figure 2 Various components and hardware are illustrated for base station 105 in FIG, including modulators and demodulators 232a-t, transmit processor 220, TX MIMO processor 230, MIMO detector 236, and receive processor 238.

[0153] As shown, the memory 242 may include map information 1202, tracking logic 1203, and communication logic 1204. The map information 1202 may include or correspond to map data 488, intersection information 499, or path information 497. The tracking logic 1203 may be configured to track or predict travel information (e.g., travel information). The communication logic 1204 may be configured to enable communication between the server 1200 and one or more other devices. The server 1200 may receive information from Figure 13 One or more UEs (e.g., UE 115), one or more base stations (e.g., base station 105), one or more network entities (e.g., network entity 405), or network entity 1300 receive signals or send signals to them.

[0154] Figure 13 is a block diagram of an example network entity 1300 supporting a security system according to one or more aspects. The network entity 1300 may be configured to perform a reference Figures 1 to 4 In some implementations, the network entity 1300 includes the structure, hardware, and components shown and described with reference to the UE 115, base station 105, vehicle 450, or network entity 405. For example, the network entity 1300 includes a controller 280 that operates to execute logic or computer instructions stored in a memory 282 and controls components of the UE 700 that provide features and functionality of the network entity 1300. The network entity 1300 transmits and receives signals via wireless radios 1301a-r and antennas 252a-r under the control of the controller 280. The wireless radios 1301a-r include various components and hardware, such as Figure 2As illustrated for UE 115, it includes modulators and demodulators 254a-r, a MIMO detector 256, a receive processor 258, a transmit processor 264, and a TX MIMO processor 266. As another example, the network entity 1300 may include or correspond to a base station, such as Figure 2 In such implementations, the wireless radios 1301a-t include various components and hardware (e.g., Figure 2 105), including modulators and demodulators 232a-t, a transmit processor 220, a TX MIMO processor 230, a MIMO detector 236, and a receive processor 238.

[0155] As shown, the memory 282 may include location information 1302 and communication logic 1303. The location information 1302 may include or correspond to information 406, 434, or 454, UE information 490, and vehicle information 492. The communication logic 1303 may be configured to implement communication between the network entity 1300 and one or more other devices. The network entity 1300 may be connected to the network entity 1300 from a plurality of locations. Figure 12 One or more UEs (e.g., UE 115), one or more base stations (e.g., 105), one or more network entities (e.g., network entity 405), core network 130, server 480 or server 1200 receive signals or send signals to them.

[0156] Please note that reference Figure 10 or Figure 11 One or more blocks (or operations) described herein may be combined with one or more blocks (or operations) described with reference to another figure. Figure 10 One or more boxes (or operations) of Figure 11 As another example, with Figure 10 or Figure 11 One or more boxes can be associated with the same Figures 1 to 4 One or more boxes (or operations) associated with the above. Figures 1 to 4 One or more of the operations described may be combined with reference to Figures 5 to 9 A combination of one or more of the operations described.

[0157] In one or more aspects, techniques for supporting a safety system may include additional aspects, such as any single aspect or any combination of aspects described below or in combination with one or more other processes or devices described elsewhere herein. In a first aspect, techniques for supporting a safety system may include receiving first location information associated with a first mobile entity. The techniques may also include sending an alert based on the first location information and path information configured to model multiple paths associated with an intersection zone. The multiple paths include a curved first path. The path information defines multiple line segments to model the first path. In some examples, the techniques of the first aspect may be implemented in a method or process. In some other examples, the techniques of the first aspect may be implemented in a wireless communication device (such as a network entity, which may include a server (e.g., a cloud server or other server), a component of a server, a base station, or a component of a base station). In some examples, the wireless communication device may include at least one processing unit or system (which may include an application processor, a modem, or other component) and at least one memory device coupled to the processing unit. The processing unit may be configured to perform the operations described herein with respect to the wireless communication device. In some examples, the memory device includes a non-transitory computer-readable medium having program code stored thereon, which, when executed by the processing unit, is configured to cause the wireless communication device to perform the operations described herein. Additionally or alternatively, the wireless communication device may include an interface (e.g., a wireless communication interface) comprising a transmitter, a receiver, or a combination thereof. Additionally or alternatively, the wireless communication device may include one or more components configured to perform the operations described herein.

[0158] In a second aspect, in combination with the first aspect, the technology further includes estimating a first time period during which the first mobile entity is predicted to be in the intersection zone based on the first position information and the path information.

[0159] In a third aspect, in combination with the second aspect, the technique further includes receiving second location information associated with a second mobile entity.

[0160] In a fourth aspect, in combination with the third aspect, the technology further includes estimating a second time period during which the second mobile entity will be in the intersection zone based on the second position information and the path information.

[0161] In a fifth aspect, in combination with the fourth aspect, the technology further includes generating an alert based on an overlap of the first time period and the second time period.

[0162] In a sixth aspect, in combination with one or more of the first to fifth aspects, the first mobile entity includes one of a vehicle or a UE associated with a pedestrian.

[0163] In a seventh aspect, in combination with the sixth aspect, the second mobile entity includes the other of a vehicle or a UE.

[0164] In an eighth aspect, in combination with one or more of the first to seventh aspects, the path information includes a plurality of path models.

[0165] In a ninth aspect, in combination with the eighth aspect, each path model of the plurality of path models is configured to model a different path of the plurality of paths.

[0166] In a tenth aspect, in combination with the eighth aspect or the ninth aspect, each of the plurality of path models defines a set of line segments of the path model.

[0167] In an eleventh aspect, in combination with the tenth aspect, each of the plurality of path models includes at least one line segment having an end point located in an intersection zone among the line segment sets of the path model.

[0168] In a twelfth aspect, in combination with one or more of the eighth to eleventh aspects, the plurality of path models includes a first path model of a first path, the first path model defining a plurality of line segments.

[0169] In a thirteenth aspect, in combination with the twelfth aspect, a first line segment of the plurality of line segments includes a first endpoint located at a first position in the intersection area.

[0170] In a fourteenth aspect, in combination with the thirteenth aspect, the plurality of path models include a second path model of a second path among the plurality of paths.

[0171] In a fifteenth aspect, in combination with the fourteenth aspect, the second path model includes one or more line segments to model the second path.

[0172] In a sixteenth aspect, in combination with the sixteenth aspect, a second line segment of the one or more line segments includes a second endpoint located at a second position in the intersection area.

[0173] In a seventeenth aspect, in combination with the sixteenth aspect, the first position and the second position are the same position.

[0174] In the eighteenth aspect, in combination with one or more of the eighth to seventeenth aspects, for each path model in the plurality of path models, for each line segment in the line segment set of the path model, the path model defines the segment ID of the line segment, the first endpoint of the line segment, the second endpoint of the line segment, the azimuth of the line segment, the segment length of the line segment, or a combination thereof.

[0175] In a nineteenth aspect, in combination with one or more of the eighth to eighteenth aspects, the technology further includes determining a direction of travel of the first mobile entity and a position of the first mobile entity based on the first position information.

[0176] In a twentieth aspect, in combination with the nineteenth aspect, the technology further comprises determining a distance from the first mobile entity to the modeled paths of the plurality of path models.

[0177] In a twenty-first aspect, in combination with the twentieth aspect, to determine the distance, the technology further includes determining, for each of a plurality of path models, a distance from the position of the first mobile entity to the modeled path of the path model in a direction perpendicular to the direction of travel.

[0178] In a twenty-second aspect, in combination with the twentieth aspect and the twenty-first aspect, the technology further includes selecting a first path model having the shortest distance among the determined distances among the plurality of path models.

[0179] In a twenty-third aspect, in combination with the twenty-second aspect, the technology further includes assigning a first path model to the first mobile entity.

[0180] In a twenty-fourth aspect, in combination with the twenty-third aspect, the technique further comprises estimating a time period during which the first mobile entity is predicted to be in the intersection zone based on a first path model assigned to the first mobile entity.

[0181] In a twenty-fifth aspect, in combination with the twenty-fourth aspect, the time period includes an entry time when the first mobile entity is predicted to enter the intersection zone and an exit time when the first mobile entity is predicted to exit the intersection zone.

[0182] In a twenty-sixth aspect, in combination with the twenty-fifth aspect, the technology further includes generating an alert based on determining that the first mobile entity is predicted to be in the intersection zone at the same time as the second mobile entity.

[0183] In a twenty-seventh aspect, in combination with one or more of aspects twenty-second to twenty-sixth, the technique further comprises determining a line segment of the selected first path model, the line segment being associated with the shortest distance.

[0184] In a twenty-eighth aspect, in combination with the twenty-seventh aspect, the technology further comprises determining a difference based on an azimuth angle of the line segment and a heading angle of the first mobile entity.

[0185] In a twenty-ninth aspect, in combination with the twenty-eighth aspect, the technology further comprises performing a comparison based on the difference and a first threshold.

[0186] In a thirtieth aspect, in combination with the twenty-ninth aspect, the technology further includes assigning a first path model to the first mobile entity based on a result of the comparing.

[0187] In a thirty-first aspect, in combination with the thirtieth aspect, the technology further includes determining a horizontal estimated positioning error associated with the first mobile entity.

[0188] In a thirty-second aspect, in combination with the thirty-first aspect, the technology further includes performing a comparison based on the horizontal estimated positioning error and a second threshold.

[0189] In a thirty-third aspect, in combination with the thirty-second aspect, the first path model is assigned to the first mobile entity based on a horizontal estimated positioning error being less than or equal to a second threshold.

[0190] In a thirty-fourth aspect, in combination with one or more of the first to thirty-third aspects, the technology further includes accessing map data.

[0191] In a thirty-fifth aspect, in combination with the thirty-fourth aspect, the technology further includes identifying intersection zone information associated with the intersection zone based on the map data.

[0192] In the thirty-sixth aspect, in combination with the thirty-fifth aspect, the intersection area information is stored as metadata of the map data and indicates an origin position associated with the intersection area, one or more paths associated with the intersection area, one or more traffic control devices associated with the intersection area, path information, or a combination thereof.

[0193] In a thirty-seventh aspect, in combination with the thirty-sixth aspect, the technology further includes selecting an intersection zone based on the first position information.

[0194] In a thirty-eighth aspect, in combination with the thirty-seventh aspect, the intersection zone is selected based on a distance between a first position associated with the first mobile entity and a second position associated with the intersection zone, a direction of travel of the first mobile entity, situational awareness information included in the first position information, or a combination thereof.

[0195] In a thirty-ninth aspect, in combination with one or more of the first to thirty-eighth aspects, the technology further includes receiving additional location information associated with the first mobile entity.

[0196] In a 40th aspect, in combination with the 39th aspect, the technology further includes determining that the first mobile entity is within the intersection zone based on the additional position information.

[0197] In a forty-first aspect, in combination with the fortieth aspect, the technology further includes estimating a time when the first mobile entity is predicted to leave the intersection zone based on a size of the intersection zone.

[0198] In a 42nd aspect, in combination with one or more of the first to 41st aspects, the technique further comprises receiving an indicator of the characteristic of the alert from the first mobile entity.

[0199] In a forty-third aspect, in combination with the forty-second aspect, the alert characteristic indicates an amount of time before a predicted time at which the alert is transmitted when the first mobile entity is predicted to enter the intersection zone.

[0200] In a forty-fourth aspect, in combination with the forty-second or forty-third aspect, the alert is sent to the first mobile entity based on the indicator.

[0201] It will be understood by those skilled in the art that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0202] This article is about Figures 1 to 13 The components, functional blocks and modules described include processors, electronic devices, hardware devices, electronic components, logic circuits, memories, software codes, firmware codes, etc., or any combination thereof. Software should be broadly interpreted to mean instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, processes, and / or functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. In addition, the features discussed herein may be implemented via dedicated processor circuits, via executable instructions, or a combination thereof.

[0203] It will be further understood by those skilled in the art that the various illustrative logic blocks, modules, circuits, and algorithmic steps described in conjunction with the disclosure herein may be implemented as electronic hardware, computer software, or a combination thereof. In order to clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been generally described above in terms of their functionality. Whether this functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the entire system. Those skilled in the art may implement the described functionality in different ways for each specific application, but such specific implementation decisions should not be interpreted as resulting in departure from the scope of this disclosure. It will also be readily appreciated that the order or combination of components, methods, or interactions described herein are merely examples, and that the components, methods, or interactions of various aspects of this disclosure may be combined or performed in a manner other than that illustrated and described herein.

[0204] The various illustrative logical components, logic blocks, modules, circuits, and algorithmic processes described in conjunction with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or a combination of both. The interchangeability of hardware and software has been generally described in terms of functionality and exemplified in the various illustrative components, blocks, modules, circuits, and processes described above. Whether such functionality is implemented in hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0205] The hardware and data processing apparatus for implementing the various illustrative logics, logic blocks, modules, and circuits described in conjunction with the various aspects disclosed herein may be implemented or executed using a general-purpose single-chip or multi-chip processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, or any conventional processor, controller, microcontroller, or state machine. In some implementations, a processor may be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in combination with a DSP core, or any other such configuration. In some implementations, particular processes and methods may be performed by circuits specific to a given function.

[0206] In one or more aspects, the functions described may be implemented in hardware, digital electronic circuitry, computer software, firmware, including the structures disclosed in this specification and their structural equivalents, or any combination thereof. Implementations of the subject matter described in this specification may also be implemented as one or more computer programs, i.e., one or more modules of computer program instructions encoded on computer storage media for execution by, or for controlling the operation of, data processing apparatus.

[0207] If implemented in software, the function may be stored as one or more instructions or codes on a computer-readable medium or sent via a computer-readable medium. The process of the method or algorithm disclosed herein may be implemented in a processor-executable software module that may reside on a computer-readable medium. Computer-readable media include both computer storage media and communication media, and the communication media include any media that can be implemented to transfer a computer program from one place to another. The storage medium can be any available medium that a computer can access. As an example and not limitation, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), CD-ROM or other optical disk storage devices, magnetic disk storage devices or other magnetic storage devices, or any other medium that can be used to store the required program code in the form of an instruction or data structure and can be accessed by a computer. In addition, any connection may be appropriately referred to as a computer-readable medium. Disks and optical disks as used herein include compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), floppy disks and blue-ray discs, wherein disks typically reproduce data magnetically, while optical discs reproduce data optically with lasers. The above combination should also be included within the scope of computer-readable media. Additionally, the operations of a method or algorithm may reside as a code and instruction set, or any combination of code and instruction sets, on a machine-readable medium or computer-readable medium, which may be incorporated into a computer program product.

[0208] Various modifications to the specific implementations described in this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other specific implementations without departing from the spirit or scope of this disclosure. Therefore, the claims are not intended to be limited to the specific implementations shown herein but are to be accorded the widest scope consistent with this disclosure, the principles and novel features disclosed herein.

[0209] Additionally, one of ordinary skill in the art will readily recognize that the terms "upper" and "lower" are sometimes used for ease of describing the drawings and indicate relative positions corresponding to the orientation of the drawings on a correctly oriented page and may not reflect the correct orientation of any device as implemented.

[0210] Certain features described in this specification in the context of separate implementations may also be implemented in combination in a single implementation. Conversely, various features described in the context of a single implementation may also be implemented in multiple implementations, either individually or in any suitable subcombination. Furthermore, while features may be described above as functioning in certain combinations and even initially claimed as such, one or more features from a claimed combination may in some cases be omitted from that combination, and a claimed combination may be directed to subcombinations or variations of subcombinations.

[0211] Similarly, although operations are depicted in a particular order in the accompanying drawings, this should not be understood as requiring such operations to be performed in the particular order shown or in a sequential order, or to perform all illustrated operations to achieve the desired result. In addition, the accompanying drawings may schematically depict one or more example processes in the form of flow charts. However, other operations not depicted may be incorporated into the schematically illustrated example processes. For example, one or more additional operations may be performed before, after, simultaneously with, or between any of the illustrated operations. In certain environments, multitasking and parallel processing are advantageous. In addition, the separation of various system components in the specific implementations described above should not be understood as requiring such separation in all specific implementations, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products. In addition, some other specific implementations also fall within the scope of the appended claims. In some cases, the actions recited in the claims can be performed in different orders and still achieve the desired result.

[0212] As used herein, including in the claims, the term "or" used in a list of two or more items means that any one of the listed items can be employed alone, or any combination of two or more of the listed items can be employed. For example, if a composition is described as containing component A, B, or C, the composition can include A alone; B alone; C alone; A and B combined; A and C combined; B and C combined; or A, B, and C combined. Furthermore, as used herein, including in the claims, "or" as used in a list of items beginning with "at least one of" indicates a separate list, so that, for example, a list of "at least one of A, B, or C" means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) or any combination of any of these. The term "substantially" is defined as largely, but not necessarily entirely, what is specified (and includes what is specified; for example, substantially 90 degrees includes 90 degrees, and substantially parallel includes parallel), as understood by one of ordinary skill in the art. In any disclosed embodiment, the term "substantially" may be replaced with "within [percentage] of" that specified, where percentages include 0.1%, 1%, 5%, or 10%.

[0213] The previous description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the spirit or scope of the disclosure. Therefore, the disclosure is not intended to be limited to the examples and designs described herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication performed by a server, the method comprising: receiving first location information associated with a first mobile entity; as well as An alert is sent based on the first location information and path information configured to model a plurality of paths associated with an intersection zone, the plurality of paths including a curved first path, and the path information defining a plurality of line segments to model the first path.

2. The method according to claim 1, further comprising: estimating a first time period based on the first position information and the path information, during which the first mobile entity is predicted to be in the intersection zone; receiving second location information associated with a second mobile entity; estimating a second time period, during which the second mobile entity will be in the intersection zone, based on the second position information and the path information; as well as generating the alert based on an overlap of the first time period and the second time period, and The first mobile entity includes one of a vehicle and a user equipment (UE) associated with a pedestrian, and the second mobile entity includes the other of the vehicle and the UE.

3. The method according to claim 1, wherein: The path information includes a plurality of path models; Each path model of the plurality of path models is configured to model a different path of the plurality of paths; and Each path model of the plurality of path models defines a line segment set of the path model and includes at least one line segment of the line segment set of the path model having an endpoint positioned in the intersection zone.

4. The method according to claim 3, wherein: The plurality of path models include: a first path model for the first path, the first path model defining the plurality of line segments, a first line segment of the plurality of line segments including a first endpoint located at a first position in the intersection zone; and a second path model of a second path of the plurality of paths, the second path model including one or more line segments to model the second path, a second line segment of the one or more line segments including a second endpoint located at a second position in the intersection area; and The first position and the second position are the same position.

5. The method of claim 3 , wherein for each path model in the plurality of path models: For each line segment in the set of line segments of the path model, the path model defines a segment identifier (ID) of the line segment, a first endpoint of the line segment, a second endpoint of the line segment, an orientation angle of the line segment, a segment length of the line segment, or a combination thereof.

6. The method according to claim 3, further comprising: determining a direction of travel of the first mobile entity and a position of the first mobile entity based on the first position information; Determining a distance from the first mobile entity to the modeled paths of the plurality of path models, wherein determining the distance comprises: for each path model of the plurality of path models, determining a distance from the position of the first mobile entity to a modeled path of the path model in a direction perpendicular to the direction of travel; as well as A first path model of the plurality of path models having the shortest distance among the determined distances is selected.

7. The method according to claim 6, further comprising: The first path model is assigned to the first mobile entity.

8. The method according to claim 6, further comprising: estimating, based on the first path model assigned to the first mobile entity, a time period during which the first mobile entity is predicted to be in the intersection zone, the time period comprising an entry time during which the first mobile entity is predicted to enter the intersection zone and an exit time during which the first mobile entity is predicted to exit the intersection zone; as well as The alert is generated based on a determination that a first mobile entity is predicted to be in the intersection zone at the same time as a second mobile entity.

9. The method according to claim 6, further comprising: determining a line segment of the selected first path model, the line segment being associated with the shortest distance; determining a disparity based on the azimuth of the line segment and the heading angle of the first mobile entity; performing a comparison based on the difference and a first threshold; as well as The first path model is assigned to the first mobile entity based on a result of the comparison.

10. The method according to claim 9, further comprising: determining a horizontal estimated positioning error associated with the first mobile entity; as well as A comparison is performed based on the horizontal estimated positioning error and a second threshold, wherein the first path model is assigned to the first mobile entity based on the horizontal estimated positioning error being less than or equal to the second threshold.

11. The method according to claim 1 , further comprising: Access map data; as well as identifying intersection zone information associated with the intersection zone based on the map data, and The intersection area information is stored as metadata of the map data and indicates an origin position associated with the intersection area, one or more paths associated with the intersection area, one or more traffic control devices associated with the intersection area, the path information, or a combination thereof.

12. The method according to claim 11, further comprising: The intersection zone is selected based on the first position information, and the intersection zone is selected based on a distance between a first position associated with the first mobile entity and a second position associated with the intersection zone, a direction of travel of the first mobile entity, situational awareness information included in the first position information, or a combination thereof.

13. The method according to claim 1, further comprising: receiving additional location information associated with the first mobile entity; determining, based on the additional location information, that the first mobile entity is within the intersection area; as well as A time at which the first mobile entity is predicted to leave the intersection zone is estimated based on a size of the intersection zone.

14. The method according to claim 1, further comprising: receiving an indicator of an alert characteristic from the first mobile entity, the alert characteristic indicating an amount of time before a predicted time at which the alert is transmitted at which the first mobile entity is predicted to enter the intersection zone, and Wherein the alert is sent to the first mobile entity based on the indicator.

15. A server, comprising: a memory storing processor-readable code; and at least one processor coupled to the memory, the at least one processor configured to execute the processor-readable code to cause the at least one processor to: receiving first location information associated with a first mobile entity; as well as An alert is sent based on the first location information and path information configured to model a plurality of paths associated with an intersection zone, the plurality of paths including a curved first path, and the path information defining a plurality of line segments to model the first path.

16. The server of claim 15, wherein the at least one processor is configured to execute the processor-readable code to cause the at least one processor to: identifying intersection zone information associated with the intersection zone based on map data, and The intersection area information is stored as metadata of the map data and indicates an origin position associated with the intersection area, one or more paths associated with the intersection area, one or more traffic control devices associated with the intersection area, the path information, or a combination thereof.

17. The server according to claim 15, wherein: The path information includes a plurality of path models; Each path model of the plurality of path models is configured to model a different path of the plurality of paths; and Each path model of the plurality of path models defines a line segment set of the path model and includes at least one line segment of the line segment set of the path model having an endpoint positioned in the intersection zone.

18. The server of claim 17, wherein for each path model in the plurality of path models: For each line segment in the set of line segments of the path model, the path model defines a segment identifier (ID) of the line segment, a first endpoint of the line segment, a second endpoint of the line segment, an orientation angle of the line segment, a segment length of the line segment, or a combination thereof.

19. The server of claim 17, wherein the at least one processor is configured to execute the processor-readable code to cause the at least one processor to: determining a direction of travel of the first mobile entity and a position of the first mobile entity based on the first position information; determining a distance from the first mobile entity to the modeled paths of the plurality of path models; as well as A first path model of the plurality of path models having the shortest distance among the determined distances is selected.

20. The server of claim 19, wherein the at least one processor is configured to execute the processor-readable code to cause the at least one processor to: determining a line segment of the selected first path model, the line segment being associated with the shortest distance; as well as determining a disparity based on the azimuth of the line segment and the heading angle of the first mobile entity; performing a comparison based on the difference and a threshold; as well as The first path model is assigned to the first mobile entity based on a result of the comparison.

21. The server of claim 20, wherein the at least one processor is configured to execute the processor-readable code to cause the at least one processor to: estimating a time period during which the first mobile entity is predicted to be in the intersection zone based on the first path model assigned to the first mobile entity, the time period including an entry time during which the first mobile entity is predicted to enter the intersection zone and an exit time during which the first mobile entity is predicted to exit the intersection zone; and The alert is generated based on a determination that a first mobile entity is predicted to be in the intersection zone at the same time as a second mobile entity.

22. A device comprising: means for receiving first location information associated with a first mobile entity; and Means for sending an alert based on the first position information and path information configured to model a plurality of paths associated with an intersection zone, the plurality of paths including a curved first path, and the path information defining a plurality of line segments to model the first path.

23. The apparatus of claim 22, wherein: The path information includes a plurality of path models; Each path model of the plurality of path models is configured to model a different path of the plurality of paths; and Each path model of the plurality of path models defines a line segment set of the path model and includes at least one line segment of the line segment set of the path model having an endpoint positioned in the intersection zone.

24. The apparatus according to claim 22, further comprising: means for identifying intersection zone information associated with the intersection zone based on map data, and The intersection area information is stored as metadata of the map data and indicates an origin position associated with the intersection area, one or more paths associated with the intersection area, one or more traffic control devices associated with the intersection area, the path information, or a combination thereof.

25. The apparatus according to claim 23, further comprising: means for determining a line segment of a first path model among the plurality of path models that is closest to the position of the first mobile entity; and Means for assigning the first path model to the first mobile entity based on determining that a difference between the azimuth angle of the line segment and the heading angle of the first mobile entity is less than or equal to a threshold.

26. The apparatus according to claim 25, further comprising: means for estimating, based on the first path model assigned to the first mobile entity, a time period during which the first mobile entity is predicted to be in the intersection zone, the time period comprising an entry time during which the first mobile entity is predicted to enter the intersection zone and an exit time during which the first mobile entity is predicted to exit the intersection zone; and Means for generating the alert based on determining that a first mobile entity is predicted to be in the intersection zone at the same time as a second mobile entity.

27. A non-transitory computer-readable medium storing instructions that, when executed by a processor, cause the processor to perform operations comprising: receiving first location information associated with a first mobile entity; and An alert is sent based on the first location information and path information configured to model a plurality of paths associated with an intersection zone, the plurality of paths including a curved first path, and the path information defining a plurality of line segments to model the first path.

28. The non-transitory computer readable medium of claim 27, wherein: The path information includes a plurality of path models; Each path model of the plurality of path models is configured to model a different path of the plurality of paths; and Each path model of the plurality of path models defines a set of line segments of the path model and includes at least one line segment of the set of line segments of the path model having an endpoint positioned in the intersection zone; and For each path model in the plurality of path models: For each line segment in the set of line segments of the path model, the path model defines a segment identifier (ID) of the line segment, a first endpoint of the line segment, a second endpoint of the line segment, an orientation angle of the line segment, a segment length of the line segment, or a combination thereof.

29. The non-transitory computer-readable medium of claim 27, wherein the instructions, when executed by the processor, cause the processor to perform operations further comprising: identifying intersection zone information associated with the intersection zone based on map data, and The intersection area information is stored as metadata of the map data and indicates an origin position associated with the intersection area, one or more paths associated with the intersection area, one or more traffic control devices associated with the intersection area, the path information, or a combination thereof.

30. The non-transitory computer-readable medium of claim 29, wherein the instructions, when executed by the processor, cause the processor to perform operations further comprising: estimating, based on a first path model assigned to the first mobile entity, a time period during which the first mobile entity is predicted to be in the intersection zone, the time period including an entry time during which the first mobile entity is predicted to enter the intersection zone and an exit time during which the first mobile entity is predicted to exit the intersection zone; and The alert is generated based on a determination that a first mobile entity is predicted to be in the intersection zone at the same time as a second mobile entity.

Images