Communication for a vehicle security system

Abstract

This disclosure provides systems, methods, and devices for wireless communication that support a secure system. In a first aspect, a method of wireless communication includes receiving first information of a first mobile entity from the first mobile entity. The method also includes sending the group configuration information to the first mobile entity. The group configuration information is generated based on the map information and indicates a group including the first mobile entity and the second mobile entity. The method also includes sending alert information to the group. Other aspects and features are also claimed and described.

Description

[0001] Cross-references to related applications

[0002] This application claims the benefit of U.S. Patent Application No. 18 / 335,307, filed June 15, 2023, entitled “COMMUNICATION FOR VEHICLESAFETY SYSTEM,” the entire contents of which are expressly incorporated herein by reference. Technical Field

[0003] This disclosure relates generally to wireless communication systems, and more specifically to safety systems, such as safety systems associated with vehicles and utilizing map data. Some features can be implemented and provide improved entity tracking, improved and more relevant safety alerts, reduced communication overhead, improved power efficiency, reduced intersection accidents, scalability, or combinations thereof. Background Technology

[0004] Wireless communication networks are widely deployed to provide various communication services such as voice, video, packet data, message sending and receiving, and broadcasting. These wireless networks can be multiple access networks capable of supporting multiple users by sharing available network resources. Such networks can be multiple access networks that support communication for multiple users by sharing available network resources.

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

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

[0007] As the demand for mobile broadband access continues to grow, the likelihood of network interference and congestion is also increasing, with more UEs accessing long-range wireless communication networks and more short-range wireless systems being deployed in communities. Research and development are continuously advancing wireless technologies to not only meet the growing demand for mobile broadband access but also to enhance and improve the user experience of mobile communications.

[0008] Vehicle-to-everything (V2X) technology enables the sharing of information from a vehicle to another device or entity that may affect that vehicle, and vice versa. V2X technology is associated with vehicular communication systems 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 and non-limiting examples. V2X technology can utilize cellular-based or wireless LAN-based communication. In some specific implementations, the messaging and communication used for V2X technology are within the application and use the underlying radio as the conduit (communication path).

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

[0010] Furthermore, even if such messages are received, the VRU may still be at risk of injury or potential collision with other vehicles in certain situations (such as at intersections) due to driver distraction or impairment, VRU distraction (e.g., a VRU at an intersection might be looking at a smartphone or watch / wearable device while walking, jogging, or cycling), or a combination thereof. A VRU safety system can be configured to receive a BSM from each of multiple vehicles approaching an intersection and determine a potential collision with the VRU based on that BSM. However, receiving BSMs from multiple vehicles increases communication overhead and provides the VRU safety system with multiple BSMs to process. In such cases, the VRU safety system may experience increased latency associated with receiving and processing BSMs. Summary of the Invention

[0011] The following summary outlines some aspects of this disclosure to provide a basic understanding of the techniques discussed. This summary is not an exhaustive overview of all the intended features of this disclosure, nor is it intended to identify key or essential elements of all aspects of this disclosure, nor to define the scope of any or all aspects of this disclosure. The sole purpose of this summary is to present, in a general form, some concepts of one or more aspects of this disclosure as a prelude to the more detailed description that follows.

[0012] In one aspect of this disclosure, a method for wireless communication is performed by a server. The method includes receiving first information from a first mobile entity. The method also includes sending group configuration information to the first mobile entity. The group configuration information is generated based on map information and indicates a group including the first mobile entity and a second mobile entity. The method further includes sending alarm information to the group.

[0013] In an additional aspect of this 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 information from a first mobile entity. The at least one processor is further configured to send group configuration information to the first mobile entity. The group configuration information is generated based on map information and indicates a group including the first mobile entity and a second mobile entity. The at least one processor is also configured to send alarm information to the group.

[0014] In an additional aspect of this disclosure, an apparatus includes components for receiving first information about a first mobile entity. The apparatus also includes components for sending group configuration information to the first mobile entity. The group configuration information is generated based on map information and indicates a group including the first mobile entity and a second mobile entity. The apparatus further includes components for sending alarm information to the group.

[0015] In an additional aspect of this 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 information from a first mobile entity. The operations also include sending group configuration information to the first mobile entity. The group configuration information is generated based on map information and indicates a group including the first mobile entity and a second mobile entity. The operations further include sending alarm information to the group.

[0016] In an additional aspect of this disclosure, an apparatus includes a communication interface configured to receive first information from a first mobile entity. The communication interface is further configured to send group configuration information to the first mobile entity. The group configuration information is generated based on map information and indicates a group including the first mobile entity and a second mobile entity. The apparatus also includes at least one processor coupled to a memory storing processor-readable code. The at least one processor is configured to execute the processor-readable code to generate alarm information for the group.

[0017] In one aspect of this disclosure, a method for wireless communication is performed by a server. The method includes receiving an indicator from a first mobile entity, the indicator indicating location accuracy information associated with a location estimate of the first mobile entity based on signals received from a non-ground entity. The method also includes sending alarm information to one or more mobile entities. The alarm information is associated with a potential collision between an object and the one or more mobile entities, and the potential collision is determined based on the indicator.

[0018] In an additional aspect of this 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 an indicator from a first moving entity, the indicator indicating location accuracy information associated with a location estimate of the first moving entity based on signals received from a non-ground entity. The at least one processor is further configured to send alarm information to one or more moving entities. The alarm information is associated with a potential collision between an object and the one or more moving entities, and the potential collision is determined based on the indicator.

[0019] In an additional aspect of this disclosure, an apparatus includes components for receiving an indicator from a first moving entity, the indicator indicating location accuracy information associated with a location estimate of the first moving entity based on signals received from a non-ground entity. The apparatus also includes components for sending alarm information to one or more moving entities. The alarm information is associated with a potential collision between an object and the one or more moving entities, and the potential collision is determined based on the indicator.

[0020] In an additional aspect of this 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 an indicator from a first moving entity, the indicator indicating location accuracy information associated with a location estimate of the first moving entity based on signals received from a non-ground entity. The operations also include sending alarm information to one or more moving entities. The alarm information is associated with a potential collision between an object and the one or more moving entities, and the potential collision is determined based on the indicator.

[0021] In an additional aspect of this disclosure, an apparatus includes a communication interface configured to receive an indicator from a first moving entity, the indicator indicating location accuracy information associated with a location estimate of the first moving entity based on signals received from a non-ground entity. The apparatus also includes at least one processor coupled to a memory storing processor-readable code. The at least one processor is configured to execute the processor-readable code to generate alarm information for one or more moving entities. The alarm information is associated with a potential collision between an object and the one or more moving entities, and the potential collision is determined based on the indicator.

[0022] In one aspect of this disclosure, a method for wireless communication performed by a mobile entity includes sending first information about the mobile entity to a server. The method also includes receiving group configuration information from the server. The group configuration information is based on map information and indicates a group that includes the mobile entity and another mobile entity. The method further includes communicating with the other mobile entity in the group based on the group configuration information.

[0023] In an additional aspect of this disclosure, a mobile entity includes a memory storing processor-readable code; and at least one processor coupled to the memory. The at least one processor is configured to execute the processor-readable code to send first information about the mobile entity to a server. The at least one processor is further configured to execute the processor-readable code to receive group configuration information from the server. The group configuration information is based on map information and indicates a group including the mobile entity and another mobile entity. The at least one processor is also configured to execute the processor-readable code to communicate with the other mobile entity in the group based on the group configuration information.

[0024] In an additional aspect of this disclosure, an apparatus includes components for sending first information about the mobile entity to a server. The apparatus also includes components for receiving group configuration information from the server. The group configuration information is based on map information and indicates a group that includes the mobile entity and another mobile entity. The apparatus further includes components for communicating with the other mobile entity in the group based on the group configuration information.

[0025] In an additional aspect of this disclosure, a non-transitory computer-readable medium stores instructions that, when executed by a processor, cause the processor to perform operations. The operations include sending first information about the mobile entity to a server. The operations also include receiving group configuration information from the server. The group configuration information is based on map information and indicates a group that includes the mobile entity and another mobile entity. The operations further include communicating with the other mobile entity in the group based on the group configuration information.

[0026] In an additional aspect of this disclosure, an apparatus includes at least one processor coupled to a memory storing processor-readable code. The at least one processor is configured to execute the processor-readable code to generate first information about the mobile entity. The apparatus also includes a communication interface configured to send the first information about the mobile entity to a server and receive group configuration information from the server. The group configuration information is based on map information and indicates a group including the mobile entity and another mobile entity. The communication interface is further configured to communicate with the other mobile entity in the group based on the group configuration information.

[0027] In one aspect of this disclosure, a method for wireless communication performed by a mobile entity includes receiving signals from a non-terrestrial entity. The method further includes transmitting an indicator indicating location accuracy information associated with a location estimate of the mobile entity. The location estimate of the mobile entity is based on the received signals.

[0028] In an additional aspect of this disclosure, a mobile entity includes a memory storing processor-readable code; and at least one processor coupled to the memory. The at least one processor is configured to execute the processor-readable code to cause the at least one processor to receive signals from a non-ground entity. The at least one processor is further configured to execute the processor-readable code to cause the at least one processor to send an indicator indicating location accuracy information associated with a location estimate of the mobile entity. The location estimate of the mobile entity is based on the received signals.

[0029] In an additional aspect of this disclosure, an apparatus includes components for receiving signals from a non-ground entity. The apparatus also includes components for transmitting an indicator indicating position accuracy information associated with a position estimate of the moving entity. The position estimate of the moving entity is based on the received signals.

[0030] In an additional aspect of this 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 signals from a non-ground entity. The operations also include sending an indicator indicating location accuracy information associated with a location estimate of the mobile entity. The location estimate of the mobile entity is based on the received signals.

[0031] In an additional aspect of this disclosure, an apparatus includes a communication interface configured to receive signals from a non-ground entity. The apparatus also includes at least one processor coupled to a memory storing processor-readable code. The at least one processor is configured to execute the processor-readable code to generate an indicator indicating location accuracy information associated with a location estimate of the moving entity. The location estimate of the moving entity is based on the received signals.

[0032] The features and technical advantages of the examples according to this disclosure have been summarized rather extensively above in order to better understand the detailed description below. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily used as the basis for modifying or designing other structures for achieving the same purpose as this 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 manner of operation) and their associated advantages will be better understood from the following description when considered in conjunction with the accompanying drawings. Each figure in the drawings is provided for illustrative and descriptive purposes and not as a definition of limitation of the claims.

[0033] While aspects and implementations are described herein by way of example, those skilled in the art will understand that additional implementations and use cases may arise in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, aspects and / or the use of devices that can be implemented via integrated chip implementations and other non-modular component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchasing devices, medical devices, AI-enabled devices, etc.). While some examples may or may not specifically point to use cases or applications, the applicability of various types of the described innovations is evident. The scope of implementations ranges from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more aspects of the described innovations. In some practical contexts, devices incorporating the described aspects and features may also necessarily include additional components and features for implementing and practicing the claimed and described aspects. For example, the transmission and reception of wireless signals necessarily involve multiple components (e.g., hardware components, including antennas, radio frequency (RF) chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.) for analog and digital purposes. The innovations described herein are intended to be implemented in a variety of devices, chip-level components, systems, distributed arrangements, end-user equipment, etc., with different sizes, shapes, and constructions. Attached Figure Description

[0034] A further understanding of the nature and advantages of this disclosure can be achieved by referring to the following figures. In the figures, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numeral and a second numeral for differentiation between similar components. If only the first reference numeral is used in the specification, the description applies to any one of the similar components having the same first reference numeral, regardless of the second reference numeral.

[0035] Figure 1 It is a block diagram illustrating details of an example wireless communication system based on one or more aspects.

[0036] Figure 2 This is a block diagram illustrating examples of base stations and user equipment (UEs) based on one or more aspects.

[0037] Figure 3 A diagram illustrating an example decomposed base station architecture based on one or more aspects is shown.

[0038] Figure 4This is a block diagram illustrating an example wireless communication system that supports a security system based on one or more aspects.

[0039] Figure 5 This is a diagram illustrating an example of a scenario based on a precision factor of one or more aspects.

[0040] Figure 6 It is a ladder diagram illustrating an example of the operation of a security system based on one or more aspects.

[0041] Figure 7 This is a flowchart illustrating an example process for supporting a security system based on one or more aspects.

[0042] Figure 8 This is a flowchart illustrating an example process for supporting a security system based on one or more aspects.

[0043] Figure 9 This is a flowchart illustrating an example process for supporting a security system based on one or more aspects.

[0044] Figure 10 This is a flowchart illustrating an example process for supporting a security system based on one or more aspects.

[0045] Figure 11 It is a perspective view of a motor vehicle with a driver monitoring system based on one or more aspects.

[0046] Figure 12 It is a block diagram of an example server that supports a security system based on one or more aspects.

[0047] Figure 13 It is a block diagram of an example network entity that supports a security system based on one or more aspects.

[0048] The same reference numerals and names in different figures denote the same elements. Detailed Implementation

[0049] 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 this disclosure. Rather, the detailed description includes specific details for providing a thorough understanding of the subject matter of the invention. It will be apparent to those skilled in the art that these specific details are not necessary in every situation, and in some cases, well-known structures and components are shown in block diagram form for clarity of presentation.

[0050] This disclosure provides systems, apparatus, methods, and computer-readable media that support safety systems. For example, this disclosure describes servers such as vehicle-to-cloud servers configured to receive safety messages for groups of mobile entities and, based on the safety messages, detect potential collisions associated with at least one mobile entity in the group. For illustration, the server may be configured to select a group of one or more mobile entities (such as one or more vehicles). The selection of this configuration may be based on map information such as population density (e.g., rural, semi-rural, urban, suburban, or city center), traffic density (e.g., frequent congestion, infrequent congestion, light, moderate, heavy, traffic jams, emergency, severe, heavy, moderate, or slight) or combinations thereof. For example, in rural or semi-urban areas, the configuration may instruct a vehicle to be designated as the group leader and configured to perform safety message transmission on behalf of the group. As another example, in urban areas, the configuration may instruct different mobile entities in the group to send safety messages for the group in a pattern or scheme (e.g., sequence). Based on one or more security messages received from the group, the server can determine the entry time of the group into an area such as an intersection (e.g., a geofenced area), the departure time of the group from the area, or a combination thereof. Based on determining that the group is within the area, the server can generate an alert indicating a potential collision between at least one mobile entity in the group and an object such as a pedestrian. The server can send an alert message to the group based on this potential collision. For example, the server can send the alert message to one mobile entity in the group, multiple mobile entities in the group, or to each mobile entity included in the group. In some implementations, such as when the group is in a semi-rural area, the server can be configured to divide the group into multiple subgroups based on map information. Alternatively, such as when multiple groups are in a rural area, the server can be configured to combine the multiple groups into a combined group based on the map information. In some implementations, mobile entities can receive signals from satellite vehicles, and location accuracy information associated with the location estimate of the mobile entity can be determined based on the received signals. The mobile entity can send indicators of location accuracy information, such as a precision factor (DOP) scalar, to the server.

[0051] 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, this disclosure provides techniques for supporting safety systems. For example, the described techniques provide for configuring a group of one or more vehicles to send safety information (e.g., group information) for that group, such as safety messages representing or applicable to that group. By configuring the group to send one or more safety messages representing or applicable to that group, overhead can be reduced. Additionally or alternatively, one or more safety messages representing or applicable to that group can reduce redundant messages (e.g., indicating speed or heading) from the vehicles in that group. Additionally or alternatively, one or more safety messages representing or applicable to that group can enable a server to identify potential collisions associated with that group (such as potential collisions with at least one moving entity in the group) without receiving safety messages from at least one moving entity in the group. Thus, configuring the group and receiving one or more safety messages for that group can minimize over-the-air transmission without compromising safety. Additionally, this technique can provide reduced overhead communication, improved entity tracking, improved and more relevant safety alerts, improved power efficiency, reduction of intersection accidents, or a combination thereof.

[0052] This disclosure relates throughout to providing or participating in licensed 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, technologies and apparatus can be used in 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, and fifth-generation (5G) or new radio (NR) networks (sometimes referred to as "5G"). NR (Network, System, or Device) and other communication networks. As described herein, the terms “network” and “system” are used interchangeably.

[0053] For example, CDMA networks can implement radio technologies such as Universal Terrestrial Radio Access (UTRA) and CDMA2000. UTRA includes Wideband CDMA (W-CDMA) and Low Chip Rate (LCR). CDMA2000 covers the IS-2000, IS-95, and IS-856 standards.

[0054] For example, TDMA networks can implement radio technologies such as the Global System for Mobile Communications (GSM). The 3rd Generation Partnership Project (3GPP) defines the standard for the GSM EDGE (Enhanced Data Rate GSM Evolution) Radio Access Network (RAN) (also known as GERAN). GERAN is the radio component of the network connecting GSM / EDGE base stations (e.g., Ater and Abis interfaces) and base station controllers (A interface, etc.). The radio access network represents a component of the GSM network through which telephone 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 (UEs)) and from subscriber handsets to the PSTN and the Internet. A mobile phone operator's network may include one or more GERANs, which may be coupled with UTRAN in the case of UMTS / GSM networks. Additionally, the operator's network may also include one or more LTE networks, or one or more other networks. Different network types may use different radio access technologies (RATs) and RANs.

[0055] OFDMA networks can implement radio technologies such as Evolved UTRA (E-UTRA), IEEE 802.11, IEEE 802.16, IEEE 802.20, and flash-OFDM. UTRA, E-UTRA, and GSM are part of the Universal Mobile Telecommunications System (UMTS). Specifically, Long Term Evolution (LTE) is a UMTS version using 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 3rd Generation Partnership Project 2 (3GPP2). These various radio technologies and standards are known or under development. For example, 3GPP is a collaboration among telecommunications associations aimed at defining globally applicable third-generation (3G) mobile phone specifications. 3GPP LTE is a 3GPP initiative aimed at improving the UMTS mobile phone standard. 3GPP defines specifications for next-generation mobile networks, mobile systems, and mobile devices. This disclosure may refer to LTE, 4G, or 5G NR technologies to describe certain aspects; however, this 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 radio spectrum between networks using different radio access technologies or radio air interfaces.

[0056] 5G networks are expected to have diverse deployments, diverse spectrum, and diverse services and devices available using a unified OFDM-based air interface. To achieve these goals, in addition to developing new radio technologies for 5G NR networks, further enhancements to LTE and LTE-A are also considered. 5G NR will be able to scale to provide coverage (1) to massive Internet of Things (IoT) with ultra-high density (e.g., approximately 1 M nodes / km). 2 (1) Ultra-low complexity (e.g., approximately 10 s bits / sec), ultra-low power consumption (e.g., approximately 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., approximately 99.9999% reliability), ultra-low latency (e.g., approximately 1 millisecond (ms)), and users with a wide range of mobility or lack of mobility; and (3) Provides enhanced mobile broadband (including extremely high capacity (e.g., approximately 10 Tbps / km)). 2 Coverage with extremely high data rates (e.g., multi-Gbps rates, 100+Mbps user experience rates) and deep awareness with advanced discovery and optimization.

[0057] Devices, networks, and systems can 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 5G NR, two initial operating bands have been designated as frequency ranges FR1 (410MHz-7.125GHz) and FR2 (24.25GHz-52.6GHz). The frequencies between FR1 and FR2 are generally referred to as mid-band frequencies. Although a portion of FR1 is greater than 6GHz, in various documents and articles, FR1 is often (interchangeably) referred to as the “sub-6GHz” band. A similar naming issue sometimes arises for FR2, which in documents and articles is often (interchangeably) referred to as the “millimeter wave” (mmWave) band, although this is different from the extremely high frequency (EHF) band (30GHz-300GHz) designated as “mmWave” by the International Telecommunication Union (ITU).

[0058] In light of the above, unless otherwise specifically stated, it should be understood that when the term "below 6 GHz" is used herein, it can broadly refer to frequencies less than 6 GHz, within FR1, or including intermediate frequency band frequencies. Furthermore, unless otherwise specifically stated, it should be understood that when used herein, the term "mmWave" can broadly refer to frequencies that can include intermediate frequency band frequencies, within FR2, or within the EHF band.

[0059] 5G NR devices, networks, and systems can be implemented using optimized OFDM-based waveform characteristics. These characteristics may include scalable parameter sets and transmission time intervals (TTIs); a general, flexible framework for efficiently multiplexing services and features using dynamic, low-latency Time Division Duplex (TDD) or Frequency Division Duplex (FDD) designs; and advanced radio technologies such as massive MIMO, robust mmWave transmission, advanced channel decoding, and device-centric mobility. The scalability of parameter sets 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 implementing FDD or TDD below 3 GHz, subcarrier spacing may occur at 15 kHz, exceeding bandwidths such as 1 MHz, 5 MHz, 10 MHz, and 20 MHz. For other various outdoor and small cell coverage deployments with TDD above 3 GHz, subcarrier spacing may occur at 30 kHz over an 80 MHz / 100 MHz bandwidth. For various other indoor broadband implementations using TDD on the unlicensed portion of the 5 GHz band, subcarrier spacing may occur at 60 kHz over a 160 MHz bandwidth. Finally, for various deployments transmitting via mmWave components under 28 GHz TDD, subcarrier spacing may occur at 120 kHz over a 500 MHz bandwidth.

[0060] 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 spectrum efficiency. Efficient multiplexing of long and short TTIs allows transmission to begin at symbol boundaries. 5G NR also anticipates self-contained integrated subframe designs, where uplink or downlink scheduling information, data, and acknowledgments reside in the same subframe. Self-contained integrated subframes support communication in unlicensed or contention-based shared spectrum, with adaptive uplink or downlink that can be flexibly configured on a per-cell basis to dynamically switch between uplink and downlink to meet current service demands.

[0061] For clarity, certain aspects of the apparatus and technology 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 the sections described below; however, this description is not intended to be limited to 5G applications.

[0062] Furthermore, it should be understood that, in operation, wireless communication networks adapted according to the concepts herein may operate using any combination of licensed or unlicensed spectrum, depending on load and availability. Therefore, it will be apparent to those skilled in the art that the systems, apparatuses, and methods described herein can be applied to other communication systems and applications besides the specific examples provided.

[0063] While aspects and implementations are described herein by way of example, those skilled in the art will understand that additional implementations and use cases may arise in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and package arrangements. For example, implementations or uses may be achieved via integrated chip implementations or other devices based on non-modular components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail or purchasing devices, medical devices, AI-enabled devices, etc.). While some examples may or may not specifically point to use cases or applications, the applicability of various types of the described innovations is evident. The scope of implementations can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the described aspects. In some practical contexts, devices incorporating the described aspects and features may also necessarily include additional components and features for implementing and practicing the claimed and described aspects. The innovations described herein are expected to be implemented in a wide variety of specific implementations of different sizes, shapes and constructions, including both large and small devices, chip-level components, multi-component systems (e.g., radio frequency (RF) chains, communication interfaces, processors), distributed deployments, end-user equipment, etc.

[0064] Figure 1 This 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. Wireless network 100 may, for example, include a 5G wireless network. As those skilled in the art will recognize, Figure 1 The components appearing in this network are likely to have corresponding components in other network layouts (including, for example, cellular network layouts and non-cellular network layouts (e.g., device-to-device, peer-to-peer, or self-organizing network layouts)).

[0065] Figure 1The illustrated wireless network 100 includes a plurality of base stations 105 and other network entities. A base station may be a station communicating with a UE and may also be referred to as an evolved Node B (eNB), a next-generation eNB (gNB), and an access point, etc. Each base station 105 may provide communication coverage for a specific geographic area. In 3GPP, the term "cell" may 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 the specific implementation of the wireless network 100 herein, base stations 105 may be associated with the same operator or different operators (e.g., the wireless network 100 may include multiple operator wireless networks). Additionally, in the specific implementation of the wireless network 100 herein, base stations 105 may use one or more frequencies (e.g., one or more bands of licensed spectrum, unlicensed spectrum, or combinations thereof) from the same frequencies as neighboring cells to provide wireless communication. In some examples, a single base station 105 or UE 115 may be operated by more than one network operating entity. In some other examples, each base station 105 and UE 115 may be operated by a single network operating entity.

[0066] Base stations can provide communication coverage for macro cells, small cells (such as pico cells or femto cells), or other types of cells. Macro cells typically cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access by UEs with service subscriptions to a network provider. Small cells (such as pico cells) typically cover a relatively small geographic area and allow unrestricted access by UEs with service subscriptions to a network provider. Small cells (such as femto cells) also typically cover a relatively small geographic area (e.g., a home) and, in addition to unrestricted access, 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, pico base station, femto base station, or home base station. Figure 1 In the example shown, base stations 105d and 105e are conventional macro base stations, while base stations 105a to 105c are macro base stations implemented using one of 3D, full-dimensional (FD), or massive MIMO. Base stations 105a to 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 stations can support one or more (e.g., two, three, and four cells, etc.) cells.

[0067] Wireless Network 100 can support synchronous or asynchronous operation. For synchronous operation, base stations can have similar frame timings, and transmissions from different base stations can be roughly aligned in time. For asynchronous operation, base stations can have different frame timings, and transmissions from different base stations may not be aligned in time. In some scenarios, the network can be enabled or configured to handle dynamic switching between synchronous and asynchronous operations.

[0068] UE 115 is distributed 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 standards and specifications issued by 3GPP, such devices may additionally or otherwise be referred to by those skilled in the art as mobile station (MS), subscriber station, mobile unit, subscriber unit, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile subscriber station, access terminal (AT), mobile terminal, radio terminal, remote terminal, handphone, terminal, user agent, mobile client, client, gaming device, augmented reality device, vehicle component, vehicle equipment or vehicle module, or some other suitable term. 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 include specific implementations that may include one or more UEs 115, including mobile phones, cellular phones (phones), smartphones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, laptop computers, personal computers (PCs), notebooks, netbooks, smartbooks, tablet devices, and personal digital assistants (PDAs). Mobile devices may additionally be IoT or “Internet of Everything” (IoE) devices, such as automobiles or other transportation vehicles, satellite radios, Global Positioning System (GPS) devices, Global Navigation Satellite System (GNSS) devices, logistics controllers, drones, multi-rotor helicopters, quadcopter helicopters, smart energy or security devices, solar panels or solar arrays, urban lighting, water supply or other infrastructure; industrial automation and enterprise equipment; consumer and wearable devices, such as glasses, wearable cameras, smartwatches, health or fitness trackers, mammalian implantable devices, posture 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 equipment, appliances, sensors, vending machines, smart lighting, home security systems, smart meters, etc. In one aspect, a UE may be a device that includes a Universal Integrated Circuit Card (UICC). In another aspect, a 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 illustrated UEs 115a to 115d are examples of mobile smartphone-type devices accessing the wireless network 100. The UE can also be a machine specifically configured for connected communications, including machine-type communications (MTC), enhanced MTC (eMTC), and narrowband IoT (NB-IoT). Figure 1 The illustrated UEs 115e to 115k are examples of various machines configured for communication that access the wireless network 100.

[0069] Mobile devices (such as UE 115) can communicate with any type of base station (whether macro base station, pico base station, femto base station, or relay station). In FI105rG.1, a communication link (represented by a lightning bolt) indicates radio transmissions between the UE and a serving base station (which is designated to serve the UE on the downlink or uplink), or expected transmissions between base stations, and backhaul transmissions between base stations. The UE can operate as a base station or other network node in some scenarios. Backhaul communication between base stations of the wireless network 100 can be performed using wired or wireless communication links.

[0070] In operation, at wireless network 100, base stations 105a to 105c use 3D beamforming and cooperative spatial technologies such as Cooperative Multipoint (CoMP) or Multi-Connection to serve UEs 115a and 115b. Macro base station 105d performs backhaul communication with base stations 105a to 105c and the small cell (base station 105f). Macro base station 105d also transmits multicast services 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 Grey Alerts.

[0071] The wireless network 100 specifically implements mission-critical communication with ultra-reliable and redundant links for mission-critical devices such as the UE 115e used as unmanned aerial vehicles. Redundant communication links with the UE 115e include links from macro base stations 105d and 105e, as well as small cell base station 105f. Other machine-type devices, such as the UE 115f (thermometer), UE 115g (smart meter), and UE 115h (wearable device), can communicate directly with base stations such as the 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 relaying its information to the network. For example, the UE 115f transmits temperature measurement information to the smart meter UE 115g, which then reports it to the network via the small cell base station 105f. Wireless network 100 can also provide additional network efficiency through dynamic, low-latency TDD or low-latency FDD communication, such as in vehicle-to-vehicle (V2V) mesh networks between UEs 115i to 115k communicating with macro base station 105e. Additionally, the V2V mesh network can include or correspond to a vehicle-to-everything (V2X) network between UEs 115i-115k and one or more other devices, such as UEs 115x, 115y.

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

[0073] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. 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 manages non-access stratum (e.g., control plane) functions, such as mobility, authentication, and bearer management of UE 115 served by base station 105 associated with the EPC. User IP packets can be delivered via the S-GW, which itself can connect to the P-GW. The P-GW provides IP address allocation and other functions. The P-GW can connect to network operator IP services. These operator IP services may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched (PS) streaming services.

[0074] In some implementations, the core network 130 includes or is coupled to management functions such as Location Management Function (LMF) 131, Sensing Management Function (SnMF), or Access and Mobility Management Function (AMF) that are entities in the 5G core network (5GC) that support various functionalities, such as managing support for different location services for one or more UEs. The SnMF can be configured to manage support for sensing operations of one or more sensing operations or sensing services for one or more devices, such as one or more UEs 115, one or more base stations 105, one or more TRPs, or combinations thereof. For example, the SnMF may include one or more servers, such as multiple distributed servers. Base station 105 may forward sensing messages to the SnMF and may communicate with the SnMF via NR Location Protocol A (NRPPa). The SnMF is configured to control sensing parameters of UE 115, and the SnMF may provide information to base station 105 and UE 115 enabling actions to be taken at UE 115, base station 105, or another device. LMF 131 may include one or more servers, such as multiple distributed servers. Base station 105 can forward location messages to LMF 131 and can communicate with LMF 131 via NR Positioning Protocol A (NRPPa). LMF 131 is configured to control the positioning parameters of UE 115, and LMF 131 can provide information to base station 105 and UE 115, enabling actions to be taken at UE 115. In some implementations, UE 115 and base station 105 are configured to communicate with LMF 131 via AMF.

[0075] Figure 2 This 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 can be... Figure 1 This refers to any one of the base stations and one of the UEs in the system. For restricted association scenarios (as mentioned above), base station 105 can be... Figure 1 The base station 105 is a small cell base station, and UE 115 can be UE 115c or 115d operating within the service area of ​​base station 105f. UE 115 will be included in the list of accessible UEs of small cell base station 105f in order to access it. Base station 105 can also be some other type of base station. For example... Figure 2 As shown, base station 105 may be equipped with antennas 234a to 234t, and UE 115 may be equipped with antennas 252a to 252r for facilitating wireless communication.

[0076] At base station 105, transmitting processor 220 can receive data from data source 212 and control information from controller 240 (such as a processor). The control information may be for physical broadcast channel (PBCH), physical control format indicator channel (PCFICH), physical hybrid ARQ (automatic repeat request) indicator channel (PHICH), physical downlink control channel (PDCCH), enhanced physical downlink control channel (EPDCCH), MTC physical downlink control channel (MPDCCH), etc. The data may be for physical downlink shared channel (PDSCH), etc. Additionally, transmitting processor 220 can process (e.g., encoding and symbol mapping) the data and control information separately to obtain data symbols and control symbols. Transmitting processor 220 can also generate, for example, reference symbols for primary synchronization signal (PSS) and secondary synchronization signal (SSS), as well as cell-specific reference signals. The transmit (TX) MIMO processor 230 can perform spatial processing (e.g., pre-decoding, where applicable) on data symbols, control symbols, or reference symbols, and can provide an output symbol stream to modulators (MODs) 232a to 232t. For example, spatial processing performed on data symbols, control symbols, or reference symbols may include pre-decoding. Each modulator 232 can (e.g., for OFDM, etc.) process its respective output symbol stream to obtain an output sample stream. Additionally or alternatively, each modulator 232 can process the output sample stream (e.g., perform analog-to-analog conversion, amplification, filtering, and up-conversion) to obtain a downlink signal. The downlink signal from modulators 232a to 232t can be transmitted via antennas 234a to 234t, respectively.

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

[0078] On the uplink, at UE 115, the transmitting processor 264 can receive and process data from data source 262 (e.g., for the Physical Uplink Shared Channel (PUSCH)) and control information from controller 280 (e.g., for the Physical Uplink Control Channel (PUCCH)). Additionally, the transmitting processor 264 can also generate reference symbols for reference signals. Symbols from the transmitting processor 264 can be pre-decoded by the TX MIMO processor 266 when needed, further processed by modulators 254a to 254r (e.g., for SC-FDM, etc.), and transmitted to base station 105. At base station 105, the uplink signal from UE 115 can be received by antenna 234, processed by demodulator 232, detected by MIMO detector 236 when needed, and further processed by receiving processor 238 to obtain the decoded data and control information transmitted by UE 115. The receiver processor 238 can provide the decoded data to the data sink 239 and the decoded control information to the controller 240.

[0079] Controllers 240 and 280 can respectively direct operations at base station 105 and UE 115. Controller 240 or other processors and modules at base station 105 or controller 280 or other processors and modules at UE 115 can perform or direct the execution of various processes used in the techniques described herein, such as performing or directing... Figures 7 to 10 The examples or references Figures 7 to 10 The described execution or other processes used in the techniques described herein. Memory 242 and 282 may store data and program code for base station 105 and UE 115, respectively. Scheduler 244 may schedule the UE to perform downlink or uplink data transmission.

[0080] In some cases, UE 115 and base station 105 may operate in a shared radio spectrum band, which may include licensed or unlicensed (e.g., contention-based) spectrum. In the unlicensed frequency portion of the shared radio spectrum band, UE 115 or base station 105 may conventionally perform a medium sensing procedure to compete for spectrum access. For example, UE 115 or base station 105 may perform a Listen-Before-Speak or Listen-Before-Transmit (LBT) procedure (such as Clear Channel Assessment (CCA)) before communication to determine if a shared channel is available. In some implementations, CCA may include an energy detection procedure to determine if any other active transmission is present. 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, signal power concentrated in a certain bandwidth and exceeding a predetermined noise floor may indicate another radio transmitter. CCA may also include the detection of a specific sequence indicating channel usage. 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 on acknowledgment / negative acknowledgment (ACK / NACK) feedback for packets it transmits (as a manifestation of a collision).

[0081] Figure 3 A diagram illustrating an example of a 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 the core network 320 via a backhaul link, or indirectly with the core network 320 via 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 a core network 130. CUs 310 may communicate with one or more distributed units (DUs) 330 via corresponding midhaul links (such as F1 interfaces). DUs 330 may communicate with one or more radio units (RUs) 340 via corresponding fronthaul links. 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.

[0082] Each of the units (i.e., CU 310, DU 330, RU 340, and near-RT RIC 325, non-RT RIC 315, and SMO frame 305) may include or be coupled to one or more interfaces configured to receive or transmit signals, data, or information (collectively, signals) via wired or wireless transmission media. Each of the units, or an associated processor or controller providing instructions to the communication interfaces of these units, may be configured to communicate with one or more other units via transmission media. For example, these units may include wired interfaces configured to receive signals or transmit signals to one or more other units via wired transmission media. Additionally, these units may include wireless interfaces that may include receivers, transmitters, or transceivers (such as radio frequency (RF) transceivers) configured to receive signals or transmit signals to one or more other units, or both, via wireless transmission media.

[0083] In some aspects, the CU 310 can host one or more higher-level control functions. Such control functions may include Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Serving Data Adaptation Protocol (SDAP), etc. Each control function can be implemented using an interface configured to signal to other control functions hosted by the CU 310. The CU 310 can be configured to handle user plane functionality (i.e., Central Unit-User Plane (CU-UP)), control plane functionality (i.e., Central Unit-Control Plane (CU-CP)), or a combination thereof. In some implementations, the CU 310 can be logically divided into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 310 can be implemented to communicate with the DU 330 for network control and signaling as needed.

[0084] DU 330 may correspond to a logical unit comprising one or more base station functions for controlling the operation of one or more RU 340s. In some aspects, DU 330 may host one or more of the Radio Link Control (RLC) layer, the Media Access Control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.), depending at least in part on the functional breakdown, such as those defined by the 3rd Generation Partnership Project (3GPP). In some aspects, DU 330 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface configured to communicate signals with other layers (and modules) hosted by DU 330 or with control functions hosted by CU310.

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

[0086] 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, SMO framework 305 can be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, 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 may include, but are not limited to, CU 310, DU 330, RU 340, and near-RT RIC 325. In some implementations, SMO framework 305 can communicate with the hardware aspects of the 4G RAN (such as Open eNB (O-eNB) 311) via the O1 interface. Additionally, in some implementations, SMO framework 305 can communicate directly with one or more RU 340s via the O1 interface. SMO framework 305 may also include a non-RT RIC 315 configured to support the functionality of SMO framework 305.

[0087] The non-RT RIC 315 can be configured to include logical functions enabling non-real-time control and optimization of RAN elements and resources, including artificial intelligence / machine learning (AI / ML) workflows for model training and updates, or policy-based guidance for applications / features in the near-RT RIC 325. The non-RT RIC 315 can be coupled to or communicate with the near-RT RIC 325, such as via an A1 interface. The near-RT RIC 325 can be configured to include logical functions enabling near real-time control and optimization of RAN elements and resources via an interface, such as via an E2 interface, through data collection and action, connecting one or more CU 310s, one or more DU 330s, or both, and O-eNBs to the near-RT RIC 325.

[0088] In some implementations, to generate AI / ML models to be deployed in the near-RT RIC 325, the non-RT RIC 315 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 325 and can be received from non-network data sources or network functions at the SMO framework 305 or the non-RT RIC 315. In some examples, the non-RT RIC 315 or near-RT RIC 325 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 315 may monitor long-term trends and patterns of performance and use AI / ML models to perform corrective actions via the SMO framework 305 (such as reconfiguration via O1) or by creating RAN management policies (such as A1 policies).

[0089] As described herein, a node (which may be referred to as a node, network node, network entity, or wireless node) may include, can be, or may be included in (e.g., components of) the following: 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, apparatus, device, computing system, integrated access and backhaul (IAB) node, distributed unit (DU), central unit (CU), remote unit (RU), core network, location management function (LMF), sense management function (SnMF), server, and / or another processing entity configured to perform any of the techniques described herein. For example, a network node may be a UE. As another example, a network node may be a base station or a network entity. As yet another example, a first network node may be configured to communicate with a second or 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 other aspects of this example, the first network node, the second network node, and the third network node may differ from these examples. Similarly, references to UE, base station, device, equipment, computing system, etc., may include disclosures of UE, base station, device, equipment, computing system, etc., as network nodes. For example, a disclosure of a UE being 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 this disclosure, once a particular example is extended according to this disclosure (e.g., a disclosure of a UE being 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 a narrower example may be interpreted in reverse, but in a broad, open-ended manner. In the above example where a UE is configured to receive information from a base station and 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 device, a first equipment, a first computing system, a first 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 device, a second equipment, a second computing system, a second or more components, a second processing entity, etc.

[0090] As described herein, different terms may be used in various contexts to describe the transmission of information (e.g., any information, signal, etc.). Disclosure of one communication term includes disclosure of 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 this disclosure, disclosure that a first network node is configured to send information to a 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 this disclosure, disclosure that a first network node is configured to send information to a second network node includes disclosure that the second network node is configured to receive, obtain, or decode information provided, transmitted, output, communicate, or sent by the first network node.

[0091] Figure 4 This is a block diagram of an example wireless communication system 400 supporting a security system according to one or more aspects. In some examples, the wireless communication system 400 may implement aspects of a wireless network 100. Additionally or alternatively, the wireless communication system 400 may include or correspond to a vulnerable road user (VRU) alert system. The wireless communication system 400 includes a UE 115, a vehicle 450, a vehicle 451, a network entity 405, and a server 480. In some specific implementations, vehicle 450 or 451 may include or correspond to... Figure 1 UEs 115i, 115j, and 115k. It should be noted that vehicles 450 and 451 may also be referred to as mobile entities—for example, vehicle 450 is a first mobile entity, and vehicle 451 is a second mobile entity. In some implementations, network entity 405 and server 480 may be referred to individually or collectively as a network, network device, or network system (e.g., a security system). Although one UE 115, two vehicles 450 and 451, one network entity 405, and one server 480 are illustrated, in some other implementations, wireless communication system 400 may typically include multiple UEs 115, one or more vehicles 450 and 451, multiple network entities 405, multiple servers 480, or combinations thereof.

[0092] Although a UE 115 and a base station 105 are illustrated, in some other embodiments, the wireless communication system 400 may typically include multiple UEs 115, multiple base stations 105, or combinations thereof. In some embodiments, the UE 115 may be, as at least referred to herein, Figure 11Further described means of transportation. Additionally or alternatively, UE 115 may include or correspond to a device for a pedestrian (e.g., a VRU). For example, as an illustrative and non-limiting example, the device for the pedestrian may include or correspond to UE 115a, 115b, 115c, 115d, 114h, 115x, or 115y.

[0093] In some specific implementations, the wireless communication system 400 includes a V2X wireless communication system. V2X is a communication system in which information is exchanged 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 designed to develop or support advanced driver assistance systems (ADAS) that assist drivers in making critical decisions, such as lane changes, speed changes, and overtaking speeds. 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 technologies such as Time of Arrival (TOA), Time Difference of Arrival (TDOA), or Observed Time Difference of Arrival (OTDOA) or any other cellular positioning technology.

[0094] Generally, at least two operating modes can exist for V2X services, as defined in 3GPP TS 23.285. When V2X entities are within range of each other, one operating mode uses direct wireless communication between the V2X entities. 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 needed.

[0095] Wireless communication in V2X wireless communication systems can be achieved through proximity-based service (ProSe) direct communication (PC5) reference points as defined in 3GPP TS 23.303, and can also be achieved through other wireless connections between entities, such as those based on IEEE 1609, Wireless Access in Vehicular Environments (WAVE), Intelligent Transportation Systems (ITS), and IEEE 802.11p, on the 5.9 GHz ITS band.

[0096] In some implementations, the wireless communication system 400 is associated with a geographic area 476. Geographic area 476 may include one or more roads, each including at least one intersection 478. Intersection 478 can be any type of intersection, such as a T-junction, a plus-shaped intersection, a Y-junction, a roundabout, or other type of intersection. Additionally, one or more roads may be associated with multiple paths, each leading to or entering intersection 478. For example, one or more paths may be configured for vehicle traffic, pedestrian traffic, or a combination thereof. One or more roads or paths may be linear, non-linear, curved, or a combination thereof. For illustrative purposes, as a non-limiting example, one or more paths may be associated with roads, car lanes, bus lanes, bicycle lanes, sidewalks, or a combination thereof. In some implementations, intersection 478 may be associated with a geofenced portion of geographic area 476.

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

[0098] In some implementations, UE 115, vehicle 450, or vehicle 451 is configured to communicate with another of UE 115, vehicle 450, or vehicle 451 using a sidelink (SL) link / interface (e.g., using sidelink communication). Additionally or alternatively, UE 115, vehicle 450, vehicle 451, or a combination thereof is configured to communicate with network entity 405 using a sidelink (SL) link / interface (e.g., using sidelink communication) or a Uu link / interface (e.g., using Uu communication). Server 480 may communicate with (e.g., communicatively coupled to) the UE, vehicle 450, or network entity 405 via a cellular network. As an illustrative and non-limiting example, server 480 may be configured to know the contextual awareness (e.g., location, heading, speed, etc.) of UE 115 or vehicle 450 based on information (such as vehicle / VRU) such as Basic Security Message (BSM) messages (for vehicle 450), Personal Security Message (PSM) messages (for UE 115), Collective Awareness Message (CPM) messages, or combinations thereof. Additionally or alternatively, as an illustrative and non-limiting example, server 480 may know a map of geographic region 476 or a map associated with that geographic region, such as maps or other information indicating the nature of local intersections (e.g., 478), stop signs, traffic lights, etc., within the geographic region. For example, the map or map data associated with geographic region 476 may include or correspond to map information 488 as further described herein.

[0099] In some implementations, the BSM may include or indicate information such as location, motion, control status, size, events, or combinations thereof (e.g., BSM information). The location may include or indicate latitude, longitude, elevation, or location accuracy. The motion may include or indicate transmission settings, speed, heading, steering wheel angle, acceleration (e.g., longitudinal acceleration, lateral acceleration, vertical acceleration, yaw rate, or combinations thereof) or combinations thereof. As an illustrative, non-limiting example, the control status may include or indicate braking system status, such as braking or not braking. As an illustrative, non-limiting example, the size may include or indicate vehicle size, such as weight, length, width, height, maximum passenger capacity, or combinations thereof. As an illustrative, non-limiting example, the event may include or indicate hazard lights, stop line violation, ABS, traction control, stability control, hazardous materials, emergency response, emergency braking, light change, wiper change, tire blowout, vehicle breakdown, airbag deployment, or combinations thereof, or be associated with them. In some implementations, the CP may include or indicate information about detected objects, onboard sensors, or combinations thereof. CPM may include, correspond to, or be defined by the ETSI ITS Intelligent Transportation System (ITS) standard. As an illustrative and non-limiting example, the CPM may include or indicate an object ID, object description, local sensor perception, adjacent vehicle perception, RSU perception, or a combination thereof.

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

[0101] Memory 404 includes or is configured to store instructions 407 and information 406. Information 406 may include capability information, location information, travel information, or combinations thereof. As an illustrative and non-limiting example, information 406 may include or indicate location or orientation (e.g., latitude, longitude, elevation, etc.), positioning accuracy, heading angle, speed, rate, altitude, equipment status, path history, predicted path, planning, ID, time, steering wheel angle, acceleration, yaw rate, braking system status, equipment or vehicle size (e.g., length, width, height, weight, etc.), event flags, or combinations thereof.

[0102] 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"). Transmitters 416 are configured to transmit reference signals, control information, and data to one or more other devices, and receivers 418 are configured to receive reference signals, synchronization signals, control information, and data from one or more other devices. For example, transmitters 416 may transmit signaling, control information, and data to base station 105, network entity 405, vehicle 450, or another UE 115, and receivers 418 may receive signaling, control information, and data from the base station, the network entity, the vehicle, or the other UE. In some implementations, transmitters 416 and receivers 418 may be integrated into one or more transceivers. Additionally or alternatively, transmitters 416 or receivers 418 may include or correspond to reference signals. Figure 2 One or more components of the described UE 115.

[0103] In some embodiments, UE 115 may include one or more antenna arrays. One or more antenna arrays may be coupled to transmitter 416, receiver 418, or a communication interface. The antenna arrays may include multiple antenna elements configured to perform wireless communication with other devices, such as base station 105. In some embodiments, the antenna arrays may be configured to perform wireless communication 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 in the antenna array may be configured to communicate using a different corresponding beam, which may have a corresponding direction different from the other beams. For example, a first set of antenna elements in the antenna array may be configured to communicate via a first beam having a first direction, and a second set of antenna elements in the antenna array may be configured to communicate via a second beam having a second direction. In other embodiments, the antenna arrays may be configured to communicate via more than two beams. Alternatively, one or more sets of antenna elements in the antenna array may be configured to concurrently generate multiple beams, for example, using multiple RF chains of the UE 115. Each individual 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 of antenna elements greater than two. Although described as an antenna array, in other specific 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.

[0104] In some implementations, UE 115 includes a non-terrestrial signal sensor. For example, this non-terrestrial signal sensor may include one or more Global Navigation Satellite System (GNSS) sensors. GNSS may include or correspond to a satellite constellation that provides positioning, navigation, and timing (PNT) services on a global or regional basis. Additionally or alternatively, 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.

[0105] Vehicle 450 may include equipment such as mobile devices or vehicles. For example, vehicle 450 may include or correspond to Figure 1 UE 115i, 115j, 115k. In some specific implementations, vehicle 450 may include or correspond to as shown in reference . Figure 11 The described means of transport or as referenced Figure 13The network entity described herein. 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"), one or more memory devices 444 (hereinafter collectively referred to as "memory 444"), one or more transmitters 416 (hereinafter collectively referred to as "transmitter 416"), one or more receivers 481 (hereinafter collectively referred to as "receiver 418"), and one or more non-ground signal sensors 449 ("non-ground signal sensor 449"). Processor 442 and memory 444 may respectively include or correspond to processor 402 and memory 404. In some specific embodiments, vehicle 450 may include an interface (e.g., a communication interface) that includes transmitter 446, receiver 448, or a combination thereof. Transmitter 446 and receiver 448 may respectively include or correspond to transmitter 416 and receiver 418. Processor 442 may be configured to execute instructions 452 stored in memory 444 to perform the operations described herein. In some specific implementations, processor 442 includes or corresponds to one or more of receiving processor 258, transmitting processor 264 and controller 280, and memory 444 includes or corresponds to memory 282.

[0106] 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, position information, travel information, or combinations thereof. Additionally or alternatively, as an illustrative and non-limiting example, information 454 may include or indicate position (e.g., latitude, longitude, elevation, etc.), position accuracy (e.g., HEPE), factor of precision (DOP) or components thereof, heading, speed, rate, altitude, equipment status, path history, predicted path, planned path, ID, time, steering wheel angle, acceleration, yaw rate, braking system status, equipment or vehicle size (e.g., length, width, height, weight, etc.), event flags, or combinations thereof.

[0107] Transmitter 446 is configured to transmit reference signals, control information, and data to one or more other devices, and receiver 448 is configured to receive reference signals, synchronization signals, control information, and data from one or more other devices. For example, transmitter 446 may transmit signaling, control information, and data to base station 105, network entity 405, another vehicle 450, or UE 115, and 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, transmitter 446 and receiver 448 may be integrated into one or more transceivers. Additionally or alternatively, transmitter 446 or receiver 448 may include or correspond to a reference signal. Figure 2 One or more components of the described UE 115.

[0108] In some embodiments, vehicle 450 may include one or more antenna arrays. These antenna arrays may be coupled to transmitter 446, receiver 448, or a communication interface. The antenna arrays may include multiple antenna elements configured to perform wireless communication with other devices, such as base station 105. In some embodiments, the antenna arrays may be configured to perform wireless communication 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 in the antenna array may be configured to communicate using a different corresponding beam, which may have a corresponding direction different from the other beams. For example, a first set of antenna elements in the antenna array may be configured to communicate via a first beam having a first direction, and a second set of antenna elements in the antenna array may be configured to communicate via a second beam having a second direction. In other embodiments, the antenna arrays 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 individual 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 of antenna elements greater than two. Although described as an antenna array, in other specific embodiments, 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.

[0109] The non-terrestrial signal sensor 449 may include one or more Global Navigation Satellite System (GNSS) sensors. GNSS may include or correspond to a satellite constellation that provides positioning, navigation, and timing (PNT) services on a global or regional basis. In some specific implementations, the non-terrestrial signal sensor 449 may include or correspond to a transmitter 416, a receiver 418, or a combination thereof.

[0110] In some implementations, the non-ground signal sensor 449 is configured to perform measurements or generate reports, such as GNSS sensor position reports. For example, the non-ground signal sensor 449 may be configured to generate reports at regular intervals (such as 1 Hz (e.g., once per second)). Additionally or alternatively, each CNSS sensor measurement may include multiple interdependent Factor of Precision (DOP) scalars, ephemeris data associated with satellite launch vehicle calibration, or combinations thereof. In some implementations, the DOP scalar may include a horizontal DOP (2D-HDOP), a position DOP (3D-DOP), a vertical DOP (VDOP), a time DOP (TDOP), or combinations thereof. The 2D-HDOP may be associated with latitude, longitude, or a combination thereof, the 3D-HDOP may be referred to as a spherical DOP, the VDOP may be associated with altitude, and the TDOP may be associated with time.

[0111] Vehicle 451 may include or correspond to vehicle 450. For example, vehicle 451 may include one or more components as described in reference vehicle 450. Additionally or alternatively, vehicle 451 may be configured to perform one or more operations as described in reference vehicle 450. It should also be noted that vehicle 450 may be configured to also perform one or more operations as described in reference vehicle 451.

[0112] Vehicles 450 or 451 may include, as referenced herein, UE 115. Figure 11 means of transportation or Figure 13 The network entity describes one or more components. In some specific implementations, vehicle 450 or 451 is a 5G-enabled vehicle, a 6G-enabled vehicle, or a combination thereof.

[0113] Network entity 405 may include devices such as a base station, roadside unit, node, or another UE. Network entity 405 may be a mobile device or a stationary device. Network entity 405 may include various components (such as structural components, hardware components) for performing one or more of the 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 embodiments, network entity 405 may include an interface (e.g., a communication interface) including a transmitter 426, a receiver 428, or a combination thereof. Processor 422 may be configured to execute instructions 430 stored in memory 424 to perform the operations described herein. In some embodiments, processor 422 includes or corresponds to one or more of a receive processor 238, a transmit processor 220, and a controller 240, and memory 424 includes or corresponds to memory 242.

[0114] 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 vehicle information 490 or group information from vehicle 450, each of which may include or indicate information 406.

[0115] 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"). Transmitters 426 are configured to transmit reference signals, control information, and data to one or more other devices, and receivers 428 are configured to receive reference signals, synchronization signals, control information, and data from one or more other devices. For example, transmitters 426 may transmit signaling, control information, and data to base station 105, UE 115, vehicle 450, another network entity 405, or server 480, and receivers 428 may receive signaling, control information, and data from the base station, the UE, the vehicle, the other network entity, or the server. In some implementations, transmitters 426 and receivers 428 may be integrated into one or more transceivers. Additionally or alternatively, transmitters 426 or receivers 428 may include or correspond to reference signals. Figure 2 One or more components of the described base station 105.

[0116] In some embodiments, network entity 405 may include one or more antenna arrays. One or more antenna arrays may be coupled to transmitter 426, receiver 428, or a communication interface. The antenna arrays may include multiple antenna elements configured to perform wireless communication with other devices, such as UE 115 or base station 105. In some embodiments, the antenna arrays may be configured to perform wireless communication 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 in the antenna array may be configured to communicate using a different corresponding beam, which may have a corresponding direction different from the other beams. For example, a first set of antenna elements in the antenna array may be configured to communicate via a first beam having a first direction, and a second set of antenna elements in the antenna array may be configured to communicate via a second beam having a second direction. In other embodiments, the antenna arrays may be configured to communicate via more than two beams. Alternatively, one or more sets of antenna elements in the antenna array may be configured to concurrently generate multiple beams, for example, using multiple RF chains of network entity 405. Each individual 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 of antenna elements greater than two. Although described as an antenna array, in other specific embodiments, 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.

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

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

[0119] Memory 384 includes or is configured to store instructions 486, map information 488, intersection information 499, group information 494, accuracy information 495, alarm information 497, and one or more thresholds 477 (collectively referred to below as “thresholds 477”). Map information 488 may include or indicate aspects or features of geographic area 476. As an illustrative and non-limiting example, map information 488 may include or indicate roads, intersections, traffic control devices, geographic features, hazards, or combinations thereof. In some specific implementations, map information 488 may include intersection information 499. For example, map information 488 may include or indicate intersections (e.g., 478). Additionally or alternatively, map information 488 may include or indicate population density, traffic density, or combinations thereof. The population density may include or indicate a designation or type of area or region based on the concentration or distribution of population. As an illustrative and non-limiting example, the designation or type associated with population may include rural, semi-rural, urban, suburban, or city center. The traffic density may include or indicate a designation or type of traffic. As an illustrative and non-limiting example, the designation or type of traffic may include frequent congestion, infrequent congestion, light, moderate, heavy, traffic jam, emergency, severe, heavy, moderate, or minor. The designation or type of traffic may change over time.

[0120] In some implementations, map information 488 may include metadata associated with intersection 478, indicating population density, traffic density, or a combination thereof. For illustration, this metadata may include intersection information 499. Although described as being included in server 480, in other implementations, map information 488 may be stored remotely from server 480 or in a database accessible to that server.

[0121] Intersection information 499 may be associated with one or more intersections (such as intersection 478). For example, intersection information 499 may include or indicate information defining or characterizing an intersection area associated with intersection 478. An intersection area may be defined as the same or different in size or shape as intersection 478. In some implementations, as an illustrative and non-limiting example, intersection information 499 may indicate or define the size, shape, origin, length, road, traffic control equipment, geographic features, hazards, or combinations thereof for intersection 478, the intersection area associated with intersection 478, or both. In some implementations, intersection information 499 may include or define a geofenced area associated with an intersection (e.g., 478).

[0122] Group information 494 includes or indicates a group of one or more mobile entities (which may also be referred to as a queue of one or more mobile entities). For example, group information 494 may include a first group 487 and optionally a second group 496. Each group 487 or 496 may include or indicate at least one entity, such as a representative entity 489 of the first group 487. In some embodiments, group information 494 may include or indicate group configuration for the group (e.g., 491), vehicle information 490 for the entities of the group (e.g., 489), group information 492 for the group, or a combination thereof. In some embodiments, server 480 may be configured to combine multiple groups (e.g., 487 and 496) into a combined group. Additionally or alternatively, server 480 may be configured to divide a group (such as the first group 487) into two or more subgroups.

[0123] Accuracy information 495 includes or indicates the accuracy of the location of a moving entity (such as UE 115, vehicle 450, or vehicle 451). Alarm information 497 may include or indicate the probability of a collision between the moving entity and an object. For example, alarm information 497 may indicate a collision probability for vehicle 450, such as the probability of a collision between vehicle 450 and an object (e.g., UE 115).

[0124] Threshold 477 may include or indicate one or more values, one or more ranges, or combinations thereof. Threshold 477 may be associated with time, duration, heading, distance, or combinations thereof.

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

[0126] In some implementations, the wireless communication system 400 (e.g., server 480) is configured to group one or more mobile devices (such as one or more vehicles). For example, the one or more mobile devices may be grouped based on map information 488. The group may be configured to send one or more security messages for that group to server 480. For example, the group may send one or more security messages for that group to server 480 instead of each mobile device in the group sending one or more security messages for that mobile device to server 480.

[0127] In some implementations, server 480 receives safety messages, such as BSMs, from each of a plurality of vehicles. Therefore, server 480 knows the speed, position, heading, or combinations thereof for each of the plurality of vehicles. Server 480 may group one or more of the plurality of vehicles into groups. For example, this group may include or correspond to a first group 487. Server 480 may receive one or more safety messages for a group based on the group being configured. In some implementations, the one or more safety messages for the group may not include or indicate speed or heading, and server 480 may use the group's speed or heading information based on one or more BSMs received from the vehicles in the group prior to the formation of the group. In some other implementations, the one or more safety messages for the group may include the group's speed or heading or indicate that speed or heading to server 480 in a one-time or semi-static manner (e.g., updated every 5th message). Although described as speed or heading information, such information or parameters may be conveyed in a similar manner if other information or parameters are not expected to change significantly for the group over time.

[0128] In some implementations, server 480 may generate groups based on map information 488 (e.g., selecting one or more vehicles for that group). For example, server 480 may select one or more vehicles for that group and may generate configuration information (such as configuration 491) to send to at least one vehicle in that group. Server 480 may select or generate groups (e.g., configuration 491) based on map information 488 (e.g., map information 488 indicating whether the area associated with one or more vehicles is rural, semi-urban, or urban). Additionally or alternatively, server 480 may select or generate groups (e.g., configuration 491) based on population density, traffic density, or a combination thereof indicated by map information 488.

[0129] In some implementations, server 480 can be configured to group a vehicle that is designated as the group leader. The group leader can be the initial vehicle in the direction of travel, the last vehicle in the direction of travel, or another vehicle in the group besides the initial or last vehicle. The group leader can be configured to send one or more security messages to server 480. For example, the group leader can send one or more security messages on behalf of the group so that other vehicles in the group do not need to send security messages to server 480. In some such implementations, the designation of the group leader and the configuration of the group leader sending one or more security messages on behalf of the group (so that other vehicles in the group do not need to send security messages to server 480) can be performed based on map information 488 indicating whether the area associated with one or more vehicles is rural or semi-urban.

[0130] In some implementations, one or more safety messages sent by the group leader may include the group leader's BSM information and may not include the BSM information of another vehicle in the group. In some other implementations, one or more safety messages sent by the group leader may include information associated with another vehicle in the group. For example, one or more safety messages sent by the group leader may include safety information (e.g., BSM information) of another vehicle, CPM information from another vehicle, distance or location information associated with another vehicle, or a combination thereof. Additionally, the one or more safety messages may include the group leader's safety information. For illustration, the one or more safety messages sent by the group leader may include the group leader's BSM information and the BSM information of at least one other vehicle in the group besides the group leader.

[0131] In some implementations, server 480 may configure the group based on a pattern, such as a pre-configured pattern. For example, the pattern may include or instruct each vehicle in the group to be configured to send its BSM information in a cyclical manner (e.g., one after another). Alternatively, the pattern may include or instruct the initial and last vehicles in the group to alternately send their BSM information. In some such implementations, server 480 may or may not specify a group leader for the group. In some implementations, server 480 may select a pattern based on map information 488 indicating that the area associated with one or more vehicles is a city.

[0132] By configuring the group to send one or more safety messages for the group, the amount of OTA resources can be reduced compared to each vehicle in the group sending its own safety message. Additionally or alternatively, the one or more safety messages sent by the group may not negatively impact VRU security—for example, server 480 obtains sufficient information to identify potential collisions based on one or more messages from the group. Additionally, by configuring the group to send one or more safety messages for the group, wireless communication system 400 (e.g., server 480) does not need to perform collision probability calculations for each individual vehicle in the group. In other words, wireless communication system 400 (e.g., server 480) can perform collision probability calculations for the group, which achieves scaling of the collision probability calculation process.

[0133] In some implementations, wireless communication system 400 (e.g., server 480) is configured to determine the location or interaction of the group relative to intersection 478 or another geofenced area. For example, server 480 may determine that the group entered the intersection (e.g., entry time), that the group left the intersection 478 (e.g., departure time), or a combination thereof. For illustration, the server may determine entry or departure based on map information 488, intersection information 499, accuracy information, or a combination thereof. Server 480 may use the group's entry or departure to identify or determine potential collisions. To determine entry or departure, server 480 may use information included in or indicated by one or more safety messages for the group.

[0134] In some implementations, server 480 may use security information from a single member of the group to determine entry into or departure from the group. As an illustrative, non-limiting example, this security information may include speed, heading, distance or offset between two vehicles in the group, or a combination thereof. As an illustrative, non-limiting example, this security information may be based on or included in a security message received from the group leader (such as security information received once or semi-statically, e.g., speed or heading). As an illustrative example, server 480 may use the speed and heading reported by one vehicle in the group to determine the time of entry into intersection 478 (e.g., a geofenced area). Alternatively, server 480 may calculate the departure time based on speed, distance between two vehicles in the group (e.g., the initial vehicle and the last vehicle), the location of the reporting vehicle (e.g., the group leader), or a combination thereof. As an illustrative and non-limiting example, server 480 may determine the entry time of the group into a geofenced area (e.g., intersection 478) based on security information received from the group leader, who is the initial vehicle, and may calculate the departure time based on the length of the group and the relative speed of another vehicle (e.g., the last vehicle in the group) relative to the group leader.

[0135] In some implementations, server 480 may determine the time when the group enters intersection 478 (e.g., a geofenced area) based on a security message from the initial vehicle in the group. Alternatively, server 480 may determine the time when the group leaves intersection 478 (e.g., a geofenced area) based on a security message from the last vehicle in the group.

[0136] In some implementations, wireless communication system 400 (e.g., server 480) is configured to provide alerts, such as alert message 493, to the group. For example, server 480 may determine that one or more vehicles in the group have a collision probability. Additionally or alternatively, server 480 may determine that one or more vehicles in the group do not have a collision probability. In some implementations, server 480 may determine the existence of a collision probability (with another object within the area) based on the time the group enters an area (such as a geofenced area, e.g., intersection 478) or the time the group leaves the area.

[0137] In some implementations, server 480 may determine the collision probability of the group and may send an alert to at least one member of the group. For example, server 480 may send an alert to the group leader, who may then notify one or more other vehicles in the group of the collision probability. For illustration, the group leader may use sidelink communication to indicate the collision probability to at least one other vehicle. Alternatively, server 480 may send an alert to each vehicle in the group.

[0138] In some implementations, server 480 may send alerts to one or more vehicles with a collision probability. For example, server 480 may determine that the last vehicle in the group has a collision probability and may send an alert only to that last vehicle. Additionally or alternatively, server 480 may send alerts to at least one vehicle that may be affected by a speed update that may be performed by a vehicle with a location probability. For example, server 480 may determine that the penultimate vehicle has a collision probability and may send an alert to the last vehicle to notify that the penultimate vehicle has a collision probability and that there may be changes (e.g., a reduction in speed).

[0139] In some embodiments, the wireless communication system 400 (e.g., server 480) is configured to combine or divide groups. For example, server 480 may be configured to subdivide a group into multiple subgroups. Server 480 may subdivide the group based on map information 488. For example, server 480 may divide the group into multiple smaller groups (e.g., subgroups) based on map information 488 indicating that the area of ​​the group is semi-rural. In some embodiments, a subgroup may be designated as a group leader and may send security messages on behalf of multiple subgroups. In some other embodiments, two or more subgroups may send security messages to server 480 based on a pattern (e.g., a pattern indicated by server 480, such as cyclic, alternating, etc.). In some other embodiments, each subgroup may be designated as a group leader, and the group leader of that subgroup may send one or more security messages to server 480 on behalf of that subgroup. In some such implementations, dividing a group into multiple subgroups can increase the granularity of safety messages reported by each smaller group for safety purposes, without significantly increasing the total amount of safety message reports (e.g., without significantly increasing safety message overhead). Additionally or alternatively, dividing a group into multiple subgroups can take into account situations or circumstances where each vehicle in the group does not have the same, uniform, or substantially uniform speed or heading.

[0140] In some implementations, server 480 can be configured to combine multiple groups into a combined group. This combined group can be designated with a lead vehicle configured to send one or more security messages on behalf of the combined group. Server 480 can combine groups based on map information 488. For example, server 480 can combine groups based on map information 488 indicating that the area of ​​the group is rural, such as group 487 and group 496. In such rural scenarios, the probability of collisions is low, and combining the groups into a combined group reduces the amount of security messages sent.

[0141] In some implementations, one or more mobile entities may be configured to operate in conjunction with a positioning system such as GNSS. For example, the one or more mobile entities may include UE 115, vehicle 450, or vehicle 451. Each of the one or more mobile entities may include a non-terrestrial signal sensor, such as non-terrestrial signal sensor 449. The non-terrestrial signal sensor may be configured to perform measurements or generate reports, such as GNSS sensor position reports. For example, the non-terrestrial signal sensor may be configured to generate reports at regular intervals, such as 1 Hz (e.g., once per second). Additionally or alternatively, each GNSS sensor measurement may include multiple interdependent DOP scalars, ephemeris data associated with satellite vehicle calibration, or combinations thereof. In some implementations, the DOP scalar may include 2D-HDOP, 3D-DOP, VDOP, TDOP, or combinations thereof.

[0142] In some embodiments, a mobile entity, including a non-ground signal sensor, may be configured to provide or indicate one or more DOP scalars to another device or entity. Additionally or alternatively, the mobile entity may determine an accuracy level based on the one or more DOP scalars. For example, the mobile entity may determine whether the one or more DOP scalars are associated with a high or low accuracy level. In some embodiments, as an illustrative and non-limiting example, the mobile entity may determine the accuracy level based on 2D-HDOP, 3D-DOP, or a combination thereof.

[0143] refer to Figure 5 , Figure 5 This is a diagram illustrating an example of a scenario based on a precision factor of one or more aspects. For example, Figure 5 A first example 500 with low DOP (e.g., high accuracy level) and a second example 510 with high DOP (e.g., low accuracy level) are shown. Each of examples 500 and 510 includes a set of satellite launch vehicles 502 and vehicles 450. Each of the satellite launch vehicles 502 is configured to transmit signals received by non-ground signal sensors 449 of vehicles 450.

[0144] Referring to the first example 500, vehicle 450 receives signals from a dispersed group of satellite carriers 502, causing vehicle 450 to determine a low DOP. Referring to the second example 510, vehicle 450 receives signals from a more concentrated group of satellite carriers 502 compared to the first example. Therefore, vehicle 450 in the second example 510 determines a high DOP. As shown in the second example 510, the group of satellite carriers 502 is more tightly clustered compared to the group of satellite carriers 502 shown in the first example 500. However, this is for ease of explanation, and it should be noted that the group of satellite carriers 502 in the first example 500 may produce a high DOP relative to vehicle 450, such as in GNSS-damaged areas or urban test environments, where large HEPE (Horizontal Error Position Estimation) may exist due to satellite carrier signal obstruction and multipath. For illustration, in an urban environment where vehicle 450 is on a street adjacent to a tall building (e.g., a skyscraper), the tall building may block signals from one or more of the satellite vehicles 502 in the first example 500, causing the received signals to produce a high DOP.

[0145] Return to reference Figure 4 The mobile entity may generate an indicator indicating one or more DOP scalars determined by the mobile entity, an accuracy level determined by the mobile entity based on the one or more DOP scalars, or a combination thereof. The mobile entity may send the indicator to server 480. For example, the mobile entity may include the indicator in a message such as a safety message or a location message. This message may include or correspond to vehicle information 490, group information 492, or V2V communication 479. In some implementations, the mobile entity includes the indicator in a BSM or PSM sent to server 480.

[0146] Server 480 can be configured to determine accuracy information 495 based on a received indicator. In some implementations, server 480 may determine the accuracy (or error) of the location of the moving entity based on the indicator (e.g., accuracy level). Additionally or alternatively, server 480 may select an accuracy metric to determine the accuracy (or error) of the location of the moving entity. For example, server 480 may select an accuracy metric as HEPE based on historical location tracking, or use an accuracy level indicated by the received indicator. A high accuracy level (low HDOP / PDOP) indicated by the indicator may cause server 480 to determine that the location of the moving entity is accurate. Alternatively, a low accuracy level (high HDOP / PDOP) indicated by the indicator may cause server 480 to determine that the location of the moving entity is inaccurate. In some implementations, server 480 may use HEPE based on an indicator indicating a low accuracy level. Server 480 may generate alarm information 497 or alarm message 493. For example, server 480 can determine the probability of a collision with a moving entity based on its position, which is based on an accuracy metric.

[0147] In some implementations, examples of the operation of the wireless communication system 400 include vehicle 450 sending vehicle information 490 to server 480. Vehicle information 490 may include safety messages, such as the BSM of vehicle 450. In some implementations, vehicle information 490 may include an indicator indicating an accuracy level, such as an accuracy level determined by vehicle 450 based on one or more DOP scalars. Additionally or alternatively, vehicle 451 may send a safety message (e.g., 490) to server 480.

[0148] Server 480 may select one or more entities (e.g., 489) to be included in a group based on received vehicle information (e.g., 490). For example, server 480 may select vehicles 450 and 451 to be included in a first group 487. In some implementations, server 480 may select one or more vehicles or generate a group based on map information 488. Additionally or alternatively, server 480 may generate a configuration for the group (e.g., 491) based on map information 488. For example, server 480 may generate a group or configuration based on population density, traffic density, or a combination thereof indicated by map information 488.

[0149] Server 480 may send configuration 491 indicating the configuration for the group (e.g., 487). For example, server 480 may send configuration 491 to one or more vehicles included in the group.

[0150] Vehicle 450 can receive configuration 491, and after receiving configuration 491, can perform vehicle-to-vehicle communication with vehicle 450. For example, this vehicle-to-vehicle communication may include the transmission or reception of V2V communication 479. Vehicle-to-vehicle communication 479 may include one or more BSMs, vehicle information, configuration information, or combinations thereof. In some specific implementations, vehicle-to-vehicle communication 479 uses sidelink communication for exchange.

[0151] When vehicles 450 and 451 are configured as part of a group, vehicle 450 may send group information 492 to server 480. Group information 492 may include information used to represent the group.

[0152] Server 480 may receive group information 492 and determine, based on the group information, whether a potential collision exists within the area. This area may include or correspond to intersection 478, intersection information 499, a geofenced area, or a combination thereof. The potential collision may occur between at least one vehicle in the group and an object within the area (e.g., a pedestrian, another moving entity, UE 115, etc.). To determine whether a potential collision exists, server 480 determines the group's entry time into the area, the group's departure time from the area, the time period the group spent in the area, or a combination thereof. For example, server 480 may estimate the group's entry time into the area based on the group information. Similarly, server 480 may estimate the group's departure time from the area. Based on the determination of a potential collision, server 480 sends an alert message 493 to the group.

[0153] In some implementations, configuration 491 for the group (e.g., 487) is applicable until the group leaves the area (e.g., intersection 478). After the group leaves the area, server 480 can reconfigure one or more vehicles from the expired group into a new group.

[0154] For reference Figure 4As described, this disclosure provides techniques for supporting safety systems. The described techniques provide processes, information, and signaling for configuring one or more vehicles into a group for the purpose of generating safety information (e.g., group information 492) and reporting that safety information to server 480. For example, the group or vehicles in the group may report one or more safety messages (e.g., 492) representing or applicable to the group. One or more safety messages representing the group can reduce redundant messages (e.g., indicating speed or heading) from vehicles in the group. Configuring the group and receiving one or more safety messages for the group can minimize over-the-air transmissions without compromising safety. One or more safety messages for the group can enable server 480 to provide alerts to individual vehicles in the group without having to receive safety messages from that individual vehicle when it is configured as part of the group. Additionally, this technique can provide reduced overhead communication, efficient entity or group tracking, improved and more relevant safety alerts, improved power efficiency, reduction of intersection accidents, or a combination thereof.

[0155] Figure 6 This is a ladder diagram illustrating examples of the operation of a security system according to various aspects of this disclosure. For example... Figure 6 As shown, Figure 5 The ladder diagram wireless communication system 600 includes a server 480, a first vehicle 450, and a second vehicle 451. The wireless communication system 600 may include or correspond to... Figure 1 Wireless communication system or wireless communication system 400. Although Figure 6 Two vehicles 450 and 451 are depicted, but the wireless communication system 600 may include a single vehicle or more than two vehicles. Additionally, although network entities (e.g., 405) or UEs (e.g., 115) are not shown in the wireless communication system 600, in other embodiments, the wireless communication system 600 may include one or more network entities (e.g., 405), one or more UEs (e.g., 115), or a combination thereof. In some embodiments, one or more operations performed or described relative to server 480 may be performed by a controller (such as a centralized controller (e.g., core network 130 or management functions of the core network)).

[0156] During the operation of the wireless communication system 600, at 602, the first vehicle 450 sends first vehicle information to the server 480. This first vehicle information may include or correspond to vehicle information 490.

[0157] At point 602, the second vehicle 451 sends second vehicle information to server 480. This second vehicle information may include or correspond to vehicle information 490.

[0158] Server 480 may select multiple mobile entities to be included in a group. This group may include or correspond to a first group 487. Server 480 may select the multiple mobile entities based on the first information, the second information, the map information, or a combination thereof. The map information may include or correspond to a geographic region 476, an intersection 478, map information 488, and intersection information 499.

[0159] At 606, server 480 may send a configuration that includes or indicates group configuration information for the group. This configuration may include or correspond to configuration 491. Server 480 may send this configuration to one or more mobile entities included in the group. In some implementations, the group may include the first mobile entity and the second mobile entity.

[0160] At 608, the first mobile entity 450 and the second mobile entity 451 perform vehicle-to-vehicle communication. This vehicle-to-vehicle communication may include the transmission or reception of V2V communication 479. Additionally or alternatively, this vehicle-to-vehicle communication may include the exchange of one or more BSMs, vehicle information, configuration information, or combinations thereof. In some embodiments, this vehicle-to-vehicle communication includes sidelink communication.

[0161] At 610, the first mobile entity 450 transmits group information. For example, this group information may include or correspond to group information 492.

[0162] Server 480 receives the set of information and determines whether a potential collision exists within the area based on the set of information. The area may include or correspond to intersection 478, intersection information 499, a geofenced area, or a combination thereof. The potential collision may occur between at least one moving entity in the group and an object within the area (e.g., a pedestrian, another moving entity, etc.). To determine whether a potential collision exists, server 480 determines the entry time of the group into the area, the departure time of the group from the area, the time period of the group in the area, or a combination thereof. For example, server 480 may estimate the entry time of the group into the area based on the set of information. Similarly, server 480 may estimate the departure time of the group from the area.

[0163] At position 612, server 480 sends an alert message to the group. For example, this alert message may include or correspond to alert message 493. This alert information may be based on map information (e.g., 488 or 499). Server 480 may send this alert message to one or more vehicles in the group. Although Figure 6The illustration shows that server 480 sends the alarm message to both first vehicle 450 and second vehicle 451. However, in other implementations, server 480 may send the alarm message to first vehicle 450 instead of second vehicle 451, and vice versa.

[0164] refer to Figure 7 , Figure 7 This is a flowchart illustrating an example process 700 supporting a security system according to one or more aspects. The operation of process 700 may be performed by a server (such as core network 130 or server 480, base station 105 or network entity 405, or as referenced) Figure 12 The server described is used to execute this. For example, the example operation of process 700 enables the server to support a security system.

[0165] At box 702, the server receives first information about the first mobile entity. For example, the first mobile entity may include or correspond to vehicle 450. The first information may include or correspond to information 454 or vehicle information 490.

[0166] At box 704, the server sends group configuration information to the first mobile entity. For example, this group configuration information may include or correspond to configuration 491, group information 494, or a combination thereof. The group configuration information may be generated based on map information and may indicate a group that includes the first and second mobile entities. For example, the group may include vehicles 450 and 451. Additionally or alternatively, the group may be associated with a first group 487 of group information 494. The map information may include or correspond to geographic region 476, intersection 478, map information 488, intersection information 499, or a combination thereof. In some implementations, the group configuration information indicates what to use for or create a group. Additionally or alternatively, the group configuration information may indicate a communication scheme between the group and the server.

[0167] At box 706, the server sends an alarm message to the group. For example, this alarm message may include or correspond to alarm message 493 or alarm message 497.

[0168] In some implementations, the server receives second information about the second mobile entity. This second information may include or correspond to vehicle information 490. The server may select multiple mobile entities to be included in the group based on the first information, the second information, the map information, or a combination thereof.

[0169] Additionally or alternatively, the server may generate group configuration information indicating the plurality of mobile entities. For example, the group configuration information may be generated based on map information. For illustration, the map information may indicate population density, traffic density, or a combination thereof. Additionally or alternatively, the group configuration information may indicate that the first mobile entity is designated as the group leader. The group configuration information may also indicate the transmission scheme between one or more mobile entities in the group and the server. For example, the transmission scheme may indicate a cyclical pattern, an alternating pattern between a leading entity and a trailing entity, or another pattern or scheme for communication between the group and the server.

[0170] In some implementations, the server receives group information from the first mobile entity. For example, this group information may include or correspond to group information 492. The group information may include a first BSM of the first mobile entity, a portion of a second BSM of the second mobile entity, a CPM, or a combination thereof. Additionally or alternatively, the server may receive third information from the UE. The UE and the third information may include or correspond to UE 115 and information 406, respectively. In some implementations, the first information may include a first security message, the second information may include a second security message, and the group information may include a third security message associated with the group, or a combination thereof. Additionally or alternatively, the alarm information may be further generated based on the third information.

[0171] In some specific implementations, the server estimates the entry time of the group into the area based on the set of information. For example, the area may include or correspond to intersection 478 or intersection information 499. The area may be associated with map information. The map information may include or correspond to geographic region 476, map information 488, or a combination thereof. Additionally or alternatively, the server estimates the departure time of the group from the area. This departure time is estimated based on the first information, the second information, the map information, the set of information, the entry time, or a combination thereof.

[0172] In some implementations, the server identifies potential collisions within the area. A potential collision may occur between at least one mobile entity in the group and an object within the area. For example, the object may include UE 115 or a mobile device not included in the group. The server may generate the alert information based on the identified potential collisions. For example, the server may generate alert information 497. The server may send the alert information to the group leader, the at least one mobile entity, mobile entities in the group other than the group leader and the at least one mobile entity, or a combination thereof. For example, the server may send an alert message 493 that includes or indicates at least a portion of alert information 497.

[0173] In some implementations, the server determines a first subgroup and a second subgroup of the group based on the map information. In some such implementations, the group configuration information indicates the first subgroup and the second subgroup. Additionally, the first subgroup may include the first mobile entity (e.g., 450), and the second subgroup may include the second mobile entity (e.g., 451). The server may receive a first set of messages (e.g., 492) from the first mobile entity included in the first subgroup, and may receive a second set of messages (e.g., 492) from the second mobile entity.

[0174] In some implementations, the server uses the map information to determine which group of one or more mobile entities should be combined with the group to form a combined group. The server may send additional group configuration information indicating the combined group to the group. This additional group configuration information may include or correspond to configuration 491. The server may receive group information (e.g., 492) from at least one mobile entity in the combined group.

[0175] In some implementations, the server receives group information from the group. This group information (e.g., 492) may indicate location accuracy information based on DOP information and associated with location estimates of the first mobile entity based on signals received from non-ground entities. This accuracy information may include or correspond to accuracy information 495. The signal may be received by the first mobile entity using a non-ground signal sensor (such as non-ground signal sensor 440). The server may generate the alarm information based on this location accuracy information.

[0176] Figure 8 This is a flowchart illustrating an example process 800 supporting a security system according to one or more aspects. The operation of process 800 may be performed by a server (such as core network 130 or server 480, base station 105 or network entity 405, or as referenced) Figure 12 The server described is used to execute this. For example, the example operation of process 800 enables the server to support a security system.

[0177] At block 802, the server receives an indicator from a first mobile entity that indicates location accuracy information associated with a location estimate of the first mobile entity based on signals received from a non-ground entity. For example, the first mobile entity may include or correspond to UE 115, vehicle 450, or vehicle 451. The indicator may include or correspond to vehicle information 490, 406, or 454, or group information 492. In some embodiments, the server may receive a safety message including the indicator, such as a basic safety message or a pedestrian safety message. The safety message may include or correspond to vehicle information 490, 406, or 454, or group information 492. The location accuracy information may include or correspond to accuracy information 495. In some embodiments, the location accuracy information includes an accuracy level determined based on a DOP scalar indicated by GNSS sensor reports. The DOP scalar may include horizontal DOP, position DOP, or a combination thereof. Additionally or alternatively, the DOP scalar may be generated based on sensor measurements received from the non-ground entity. This non-ground entity may include or correspond to a satellite, such as a satellite included in GNSS.

[0178] At box 804, the server sends an alert message to one or more moving entities. For example, this alert message may include or correspond to alert message 497, alert message 493, or a combination thereof. The alert message may be associated with a potential collision between the object and the one or more moving entities. This potential collision may be determined based on the indicator. In some implementations, the server may generate the alert message based on map information. This map information may include or correspond to geographic region 476, map information 488, intersection information 499, or a combination thereof.

[0179] In some implementations, the server may select an accuracy value based on the indicator, which includes either a horizontally estimated position error based on historical tracking information or the position accuracy information itself. The server may then generate a position value (e.g., location) for the first moving entity based on this accuracy value. The server may then determine the potential collision based on this position value.

[0180] Figure 9 This is a flowchart illustrating an example process 900 supporting a security system according to one or more aspects. The operation of process 900 may be performed by a mobile entity (such as UE 115, vehicle 450 or 451) or as referenced... Figure 13 The network entity described is used to perform this action. For example, the example operation of process 900 enables the server to support a security system.

[0181] At box 902, the mobile entity sends its first information to the server. For example, the server may include or correspond to server 480. The first information may include or correspond to vehicle information 490, information 454, or a combination thereof.

[0182] At box 904, the mobile entity receives group configuration information from the server. For example, this group configuration information may include or correspond to configuration 491, group information 494, or a combination thereof. The group configuration information may be based on map information and may indicate a group that includes the mobile entity and another mobile entity. For example, the group may include vehicle 450 and vehicle 451. Additionally or alternatively, the group may be associated with a first group 487 of group information 494. In some embodiments, the group configuration information indicates that the mobile entity is designated as the group leader of the group. Additionally or alternatively, the group configuration information also indicates a transmission scheme between one or more mobile entities in the group and the server. For example, the transmission scheme may indicate a cyclical mode, an alternating mode between a leading entity and a trailing entity, or another mode or scheme for communication between the group and the server. Additionally or alternatively, the group configuration information may indicate that the group is associated with a combined group of multiple groups. For example, the group may be a combined group including multiple subgroups, or it may be a subgroup of a combined group.

[0183] The map information may include or correspond to geographic region 476, intersection 478, map information 488, intersection information 499, or a combination thereof. The map information may include or indicate population density, traffic density, or a combination thereof.

[0184] At box 906, the mobile entity communicates with another mobile entity in the group based on the group configuration information. For example, the other mobile entity may include vehicle 451. To communicate with the other mobile entity, the mobile entity and the other mobile entity may perform V2V communication (e.g., 494). In some implementations, the V2V communication may include or be associated with sidelink communication. For example, the mobile entity may establish a sidelink between itself and the other mobile entity and may communicate via that sidelink.

[0185] In some implementations, the mobile entity sends group information to the server. For example, the group information may include or correspond to group information 492. This group information may be associated with a group that includes the mobile entity and the other mobile entity.

[0186] In some implementations, the mobile entity receives alarm information from the server. For example, the alarm information may include or correspond to alarm information 497, alarm message 493, or a combination thereof. The alarm information may indicate a potential collision for the mobile entity, a potential collision for another mobile entity in the group, a potential change in the trajectory of that other mobile entity, or a combination thereof.

[0187] In some implementations, the mobile entity receives second information from the other mobile entity. This second information may include or correspond to V2V communication 479. Based on the second information from the other mobile entity, the mobile entity's third information, or a combination thereof, the mobile entity may generate a security message. For example, the security message may include or correspond to group information 492. The mobile entity may send the security message to the server.

[0188] In some implementations, the mobile entity may send group information, such as group information 492, to the server. In some such implementations, the group information may be associated with a group that includes the mobile entity and the other mobile entity. The group information may include a first BSM of the mobile entity, a portion of a second BSM of the other mobile entity, a CPM, or a combination thereof.

[0189] In some implementations, the mobile entity may receive signals from a non-ground entity. For example, the non-ground entity may include or correspond to a satellite, such as a satellite included in GNSS. The mobile entity may use a sensor (such as non-ground signal sensor 449) to receive the signal. The mobile entity may determine a position estimate based on the received signal and generate an indicator indicating position accuracy information associated with the position estimate. This accuracy information may include or correspond to accuracy information 495. The mobile entity may transmit the indicator. The indicator may be included in vehicle information 490 or group information 492.

[0190] Figure 10 This is a flowchart illustrating an example process 1000 supporting a security system according to one or more aspects. The operation of process 1000 may be performed by a mobile entity (such as UE 115, vehicle 450 or 451) or as referenced... Figure 13 The network entity described is used to perform this action. For example, the example operation of process 1000 enables the server to support a security system.

[0191] At box 1002, the moving entity receives a signal from a non-ground entity. This non-ground entity may include or correspond to a satellite, such as a satellite included in GNSS. The moving entity may use a sensor, such as non-ground signal sensor 449, to receive the signal.

[0192] In some embodiments, the mobile entity determines its position estimate based on the received signal. Additionally or alternatively, the mobile entity may generate an indicator indicating position accuracy information associated with the position estimate. In some embodiments, the mobile entity generates a sensor measurement including a DOP scalar based on the signal. As an illustrative, non-limiting example, the DOP scalar may include a horizontal DOP, a position DOP, or a combination thereof. Additionally or alternatively, the mobile entity may generate a GNSS sensor report indicating the DOP scalar. The mobile entity may determine an accuracy level based on the DOP scalar. In some such embodiments, the position accuracy information includes or indicates the determined accuracy level.

[0193] In some implementations, the mobile entity may generate a safety message, such as a basic safety message or a personal safety message, that includes indicators indicating the level of accuracy. For example, the safety message may include or correspond to vehicle information 490 or group information 492. Additionally, the mobile entity may send the safety message.

[0194] At box 1004, the mobile entity sends an indicator indicating location accuracy information associated with the mobile entity's location estimate. This indicator may include or correspond to vehicle information 490, information 406 or 454, or group information 492. The mobile entity's location estimate may be based on received signals. The location accuracy information may include or correspond to accuracy information 495.

[0195] In some implementations, the moving entity receives alarm information associated with a potential collision between the object and the moving entity. For example, the alarm information may include or correspond to alarm information 497, alarm message 493, or a combination thereof. The alarm information may be received from a server (such as server 480). Additionally or alternatively, the alarm information may be based on an indicator.

[0196] Figure 11 This is a perspective view of a motorized vehicle equipped with a driver monitoring system, based on one or more aspects. The vehicle 1100 may include, for example... Figure 1 The UE within the wireless network 100 shown or communicating with the UE. In some specific implementations, vehicle 1100 may include or correspond to UE 115i, 115j or 115k, vehicle 450 or vehicle 451.

[0197] Vehicle 1100 may include a forward-facing camera 1112 mounted inside the cabin for viewing through the windshield 1102. Vehicle 1100 may also include a cabin-facing camera 1114 mounted inside the cabin for the occupants of vehicle 1100, and particularly the driver of vehicle 1100. Although a set of mounting locations for cameras 1112 and 1114 has been shown for vehicle 1100, other mounting locations may also be used for cameras 1112 or 1114. For example, one or more cameras may be mounted on one of the driver's or passenger pillars 1126 or one of the driver's or passenger pillars 1128, such as near the top of pillars 1126 or 1128. Alternatively, one or more cameras may be mounted at the front of vehicle 1100, such as behind the radiator grille 1130 or integrated with the bumper 1132. As a further example, one or more cameras may be mounted as part of a driver or passenger side mirror assembly 1134.

[0198] Camera 1112 may be oriented such that its field of view captures the scene in front of vehicle 1100 in the direction in which vehicle 1100 is moving when in drive mode or forward. In some embodiments, an additional camera may be located at the rear of vehicle 1100 and oriented such that its field of view captures the scene behind vehicle 1100 in the direction in which vehicle 1100 is moving in the reverse direction. Although aspects of this disclosure may be described with reference to a “forward-facing” camera (refer to camera 1112), aspects of this disclosure may be similarly applied to a “rearward-facing” camera facing the reverse direction of vehicle 1100. Thus, the benefits obtained when the operator operates vehicle 1100 in the forward direction may be similarly obtained when the operator operates vehicle 1100 in the reverse direction.

[0199] Furthermore, although embodiments of this disclosure may be described with reference to a "forward-facing" camera (reference camera 1112), aspects of this disclosure can be similarly applied to input received from an array of cameras mounted around vehicle 1100 to provide a large field of view, which may be approximately 360 degrees parallel to the ground and / or approximately 360 degrees in a vertical direction approximately perpendicular to the ground. For example, additional cameras may be mounted around the exterior of vehicle 1100, such as mounted on or integrated into doors, mounted on or integrated into wheels, mounted on or integrated into bumpers, mounted on or integrated into hoods, and / or mounted on or integrated into the roof.

[0200] Camera 1114 can be oriented such that its field of view is configured to capture the scene within the cockpit of vehicle 1100 and include the user operator of vehicle 1100. In some embodiments, camera 1114 is configured to capture the face of the user operator of vehicle 1100 with sufficient detail to determine the user operator's gaze direction.

[0201] Each of cameras 1112 and 1114 may include one, two, or more image sensors, such as a first image sensor. When multiple image sensors are present, the first image sensor may have a larger field of view (FOV) than the second image sensor, or the first image sensor may have a different sensitivity or a different dynamic range than the second image sensor. In one example, the first image sensor may be a wide-angle image sensor, and the second image sensor may be a telephoto image sensor. In another example, the first sensor is configured to acquire an image through a first lens having a first optical axis, and the second sensor is configured to acquire an image through a second lens having a second optical axis different from the first optical axis. Additionally or alternatively, the first lens may have a first magnification, and the second lens may have a second magnification different from the first magnification. This configuration may occur in a camera module with a lens group, wherein multiple image sensors and associated lenses are located at offset positions within the camera module. Additional image sensors with larger, smaller, or the same field of view may be included.

[0202] Each image sensor may include components for capturing data representing a scene, such as image sensors (including charge-coupled devices (CCDs), Bayer filter sensors, infrared (IR) detectors, ultraviolet (UV) detectors, complementary metal-oxide-semiconductor (CMOS) sensors) and / or time-of-flight detectors. The device may also include components for focusing and / or converging light onto one or more of the image sensors (including simple lenses, compound lenses, spherical lenses, and aspherical lenses). These components may be controlled to capture a first image frame, a second image frame, and / or more image frames. The image frames may be processed to form a single output image frame (e.g., through a fusion operation), and the output image frame may be further processed according to the aspects described herein.

[0203] As used herein, an image sensor can refer to the image sensor itself and any specific other components coupled to the image sensor for generating image frames for processing by an image signal processor or other logic circuitry, or for storage in memory (whether short-term buffers or long-term non-volatile memory). For example, an image sensor can include other components of a camera, including shutters, buffers, or other readout circuitry for accessing the individual pixels of the image sensor. An image sensor can also refer to an analog front-end or other circuitry for converting analog signals into a digital representation of an image frame, which is provided to digital circuitry coupled to the image sensor.

[0204] Vehicle 1100 may include or otherwise couple to an image signal processor for processing image frames from one or more image sensors, such as a first image sensor, a second image sensor, and a depth sensor. Vehicle 1100 may also include or be coupled to a power source, such as a battery or alternator. Figure 2 One or more features, Figure 2 One or more additional features or components, or combinations thereof, not shown in the diagram.

[0205] Vehicle 1100 may include a sensor hub for docking with sensors to receive data about the movement of vehicle 1100, data about the environment surrounding vehicle 1100, or other non-camera sensor data. The sensor hub may include or be coupled to one or more sensors. One example non-camera sensor is a gyroscope, a device configured to measure rotation, orientation, or angular velocity to generate motion data. Another example non-camera sensor is an accelerometer, a device configured to measure acceleration, which can also be used to determine velocity and distance traveled by appropriately integrating the measured acceleration, and one or more of acceleration, velocity, and / or distance may be included in the generated motion data. In other examples, the non-camera sensor may be a Global Positioning System (GPS) receiver, a LiDAR system, a RADAR system, or other ranging system. For example, the sensor hub can be connected to a vehicle bus to transmit configuration commands and / or receive information from vehicle sensors such as distance (e.g., ranging) sensors or vehicle-to-vehicle (V2V) sensors (e.g., sensors for receiving information from nearby vehicles)).

[0206] Figure 12 This is a block diagram of an example server 1200 that supports a security system based on one or more aspects. Server 1200 can be configured to perform operations, including references... Figures 1 to 4 , Figure 7 or Figure 8The description or reference Figure 7 or Figure 8 The process is described in the box. In some specific implementations, server 1200 includes the architecture, hardware, and components shown and described with reference to base station 105 or core network 130. For example, server 1200 may include controller 240 for executing logical or computer instructions stored in memory 242, as well as components that control server 1200 and provide the characteristics and functionality of server 1200. Under the control of controller 240, server 1200 transmits and receives signals via wireless radio components 1201a-t and antenna 234a-t. Wireless radio components 1201a-t include, for example, Figure 2 The various components and hardware illustrated for base station 105 include modulators and demodulators 232a-t, a transmit processor 220, a TX MIMO processor 230, a MIMO detector 236, and a receive processor 238. Although server 1200 is described as including wireless radio components 1201a-t and antennas 234a-t, in other specific embodiments, server 1200 may additionally or alternatively include interfaces, such as interfaces configured for wired communication.

[0207] As shown in the figure, memory 242 may include map information 1202, group information 1203, alarm logic 1204, and communication logic 1205. Map information 1202 may include or correspond to map information 488 or intersection information 499. Group information 1203 may include or correspond to configuration 491, group information 492, or group information 494. Alarm logic 1204 may be configured to generate alarm information 497 based on accuracy information 495, group information 494, threshold 477, map information 1202, or a combination thereof. Alarm logic 1204 may also be configured to generate alarm messages based on alarm information 497, such as alarm message 493. Communication logic 1205 may be configured to enable communication between server 1200 and one or more other devices. Server 1200 may receive data from 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... Figure 13 Network entity 1300 receives signals or sends signals to them.

[0208] Figure 13 This is a block diagram of an example network entity 1300 that supports a security system based on one or more aspects. Network entity 1300 can be configured to perform reference... Figures 1 to 4 , Figure 9 or Figure 10 The description or reference Figure 9 or Figure 10The process is described in the box. In some specific implementations, network entity 1300 includes the structures, hardware, and components shown and described with reference to UE 115, base station 105, vehicle 450, vehicle 451, or network entity 405. For example, network entity 1300 includes a controller 280 that operates to execute logical or computer instructions stored in memory 282, and components that control network entity 1300 and provide the characteristics and functionality of network entity 1300. Under the control of controller 280, network entity 1300 transmits and receives signals via wireless radio components 1301a-r and antennas 252a-r. Wireless radio components 1301a-r include, for example, Figure 2 The various components and hardware exemplified for UE 115 include modulators and demodulators 254a-r, MIMO detector 256, receive processor 258, transmit processor 264, and TX MIMO processor 266. As another example, network entity 1300 may include or correspond to a base station, such as... Figure 2 Base station 105. In such a specific implementation, the wireless radio component 1301a-t includes various components and hardware (such as in...). Figure 2 (Example for base station 105) includes modulator and demodulator 232a-t, transmitter processor 220, TX MIMO processor 230, MIMO detector 236 and receiver processor 238.

[0209] As shown in the figure, memory 282 may include information 1302 and communication logic 1303. Information 1302 may include or correspond to information 406, 434 or 454, vehicle information 490, configuration 491, group information 492 or combinations thereof. Communication logic 1303 may be configured to enable communication between network entity 1300 and one or more other devices. Network entity 1300 may be located from 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), one or more mobile entities (e.g., vehicle 450 or 451), core network 130, server 480 or Figure 12 Server 1200 receives signals or sends signals to them.

[0210] Note that this is for reference only. Figures 7 to 10 The described one or more boxes (or operations) may be combined with one or more boxes (or operations) described in another drawing with reference to the accompanying drawings. For example, Figure 7 One or more boxes (or operations) can be connected with Figure 8 A combination of one or more boxes (or operations). For example, Figure 7 One or more boxes can be connected with Figure 9 or Figure 10A combination of one or more boxes (or operations). For example, Figure 9 One or more boxes (or operations) can be connected with Figure 10 A combination of one or more boxes (or operations). For example, Figure 9 One or more boxes can be connected with Figure 7 or Figure 8 A combination of one or more boxes (or operations). For example, with... Figures 7 to 10 One or more associated boxes can be Figures 1 to 6 A combination of one or more associated boxes (or operations). Additionally or alternatively, refer to the above. Figures 1 to 4 One or more operations described can be compared with the reference Figure 5 or Figure 6 The described combination of one or more operations.

[0211] In one or more aspects, the technology used to support a security system may include additional aspects, such as any single aspect or any combination of aspects described below or in conjunction with one or more other processes or devices described elsewhere herein. In a first aspect, supporting a security system may include an apparatus configured to receive first information from a first mobile entity. The apparatus is further configured to send group configuration information to the first mobile entity. The group configuration information is generated based on map information and indicates a group including the first mobile entity and a second mobile entity. The apparatus is also configured to send alarm information to the group. Additionally, the apparatus may perform or operate according to one or more aspects described below. In some embodiments, the apparatus includes a device (such as a server) or a component of that device. In some embodiments, the apparatus may include at least one processor and memory coupled to the processor. The processor may be configured to perform the operations described herein with respect to the apparatus. In some other embodiments, the apparatus may include a non-transitory computer-readable medium having program code recorded thereon, and the program code may be executable by a computer to cause the computer to perform the operations described herein with reference to the apparatus. In some embodiments, the apparatus may include one or more components configured to perform the operations described herein. In some embodiments, the method of wireless communication may include one or more operations described herein with reference to the apparatus.

[0212] Secondly, in conjunction with the first aspect, the alert information is generated based on map information.

[0213] In a third aspect, in combination with one or more of the first or second aspects, the map information indicates population density, traffic density, or a combination thereof.

[0214] In the fourth aspect, in conjunction with one or more of the first to third aspects, the group configuration information indicates that the first mobile entity is designated as the group leader of the group.

[0215] In a fifth aspect, in conjunction with one or more of the first to fourth aspects, the device is further configured to receive second information from the second mobile entity.

[0216] In a sixth aspect, in conjunction with the fifth aspect, the device is further configured to select multiple mobile entities to be included in the group based on the first information, the second information, the map information, or a combination thereof.

[0217] In a seventh aspect, in conjunction with the sixth aspect, the device is further configured to generate the set of configuration information indicating the plurality of mobile entities.

[0218] In the eighth aspect, in conjunction with the seventh aspect, the device is further configured to receive group information from the first mobile entity.

[0219] In the ninth aspect, in conjunction with the eighth aspect, the device is further configured to receive third information from the UE.

[0220] In the tenth aspect, in conjunction with the ninth aspect, the first information includes a first security message, the second information includes a second security message, the group information includes a third security message associated with the group, and the alarm information is further generated based on the third information, or a combination thereof.

[0221] In the eleventh aspect, in conjunction with the seventh aspect, the device is further configured to receive group information from the first mobile entity.

[0222] In the twelfth aspect, in conjunction with the eleventh aspect, the set of information includes the first BSM of the first mobile entity, a portion of the second BSM of the second mobile entity, CPM, or a combination thereof.

[0223] In the thirteenth aspect, in conjunction with the twelfth aspect, the device is further configured to estimate the entry time of the group of entry areas based on the set of information, which is associated with the map information.

[0224] In the fourteenth aspect, in conjunction with the thirteenth aspect, the device is further configured to estimate the departure time of the group from the area, the departure time being estimated based on the first information, the second information, the map information, the group information, the entry time, or a combination thereof.

[0225] In the fifteenth aspect, in conjunction with one or more of the first to twelfth aspects, the device is further configured to determine a potential collision within a region. In some specific embodiments, the potential collision occurs between at least one moving entity in the group and an object within the region.

[0226] In the sixteenth aspect, in conjunction with the fifteenth aspect, the device is further configured to generate the alarm information based on the identified potential collision.

[0227] In the seventeenth aspect, in conjunction with the sixteenth aspect, the alarm information is sent to the group leader of the group, the at least one mobile entity, mobile entities in the group other than the group leader and the at least one mobile entity, or a combination thereof.

[0228] In the eighteenth aspect, in conjunction with one or more of the first to seventeenth aspects, the group configuration information indicates the transmission scheme of one or more mobile entities in the group with the device.

[0229] In the nineteenth aspect, in conjunction with one or more of the first to eighteenth aspects, the device is further configured to determine the first and second subgroups of the group based on the map information.

[0230] In the twentieth aspect, in conjunction with the nineteenth aspect, the group configuration information indicates the first subgroup and the second subgroup, the first subgroup including the first mobile entity and the second subgroup including the second mobile entity.

[0231] In the twentieth aspect, in conjunction with the twentieth aspect, the device is further configured to receive a first set of messages from the first mobile entity included in the first subgroup.

[0232] In the twentieth aspect, in conjunction with the twentieth aspect, the device is further configured to receive a second set of messages from the second mobile entity.

[0233] In the twenty-third aspect, in conjunction with one or more of the first to twenty-second aspects, the device is further configured to determine, based on the map information, to combine another group of one or more mobile entities with the group to form a combined group.

[0234] In the twentieth aspect, in conjunction with the twentieth aspect, the device is further configured to send additional group configuration information to the group, indicating the group's configuration.

[0235] In the twenty-fifth aspect, in conjunction with the twenty-fourth aspect, the device is further configured to receive group information from at least one mobile entity in the group.

[0236] In the twenty-sixth aspect, in conjunction with one or more of the first to twenty-fifth aspects, the device is further configured to receive group information from the group.

[0237] In the twenty-seventh aspect, in conjunction with the twenty-sixth aspect, this set of information indicates location accuracy information based on DOP information and location estimation associated with the first mobile entity based on signals received from non-ground entities.

[0238] In the twenty-eighth aspect, in conjunction with the twenty-seventh aspect, the device is further configured to generate the alarm information based on the location accuracy information.

[0239] In one or more aspects, the technology used to support the security system may include additional aspects, such as any single aspect or any combination of aspects described below or in conjunction with one or more other processes or devices described elsewhere herein. In a twenty-ninth aspect, supporting the security system may include an apparatus configured to send first information about the apparatus to a server. The apparatus is further configured to receive group configuration information from the server. The group configuration information is based on map information and indicates a group including the apparatus and another mobile entity. The apparatus is also configured to communicate with the other mobile entity in the group based on the group configuration information. Additionally, the apparatus may perform or operate according to one or more aspects described below. In some embodiments, the apparatus includes a wireless device (such as a mobile entity, UE, vehicle) or a component of the wireless device. In some embodiments, the apparatus may include at least one processor and memory coupled to the processor. The processor may be configured to perform the operations described herein with respect to the apparatus. In some other embodiments, the apparatus may include a non-transitory computer-readable medium having program code recorded thereon, and the program code may be executable by a computer to cause the computer to perform the operations described herein with reference to the apparatus. In some embodiments, the apparatus may include one or more components configured to perform the operations described herein. In some embodiments, a method of wireless communication may include one or more of the operations described herein with reference to the apparatus.

[0240] In the thirtieth aspect, in conjunction with the twenty-ninth aspect, the device is further configured to communicate via a side link established between the device and the other mobile entity.

[0241] In the thirty-first aspect, in conjunction with the thirtieth aspect, the device is further configured to send group information to the server, the group information being associated with the group including the device and the other mobile entity.

[0242] In aspect thirty-two, in conjunction with aspect thirty-one, the map information indicates population density, traffic density, or a combination thereof.

[0243] In aspect thirty-three, in conjunction with or in combination with aspect thirty-two, the group configuration information indicates that the device is designated as the group leader of the group.

[0244] In the thirty-fourth aspect, in conjunction with one or more of the twenty-ninth to thirty-fourth aspects, the device is further configured to receive alarm information from the server.

[0245] In the thirty-fifth aspect, in conjunction with the thirty-third aspect, the alarm information indicates a potential collision of the device, a potential collision of another moving entity in the group, a potential change in the course of the other moving entity, or a combination thereof.

[0246] In the thirty-sixth aspect, in conjunction with one or more of the twenty-ninth to thirty-fifth aspects, the device is further configured to receive second information from the other mobile entity.

[0247] In the thirty-seventh aspect, in conjunction with the thirty-sixth aspect, the device is further configured to generate a security message based on the second information, the device's third information, or a combination thereof.

[0248] In the thirty-eighth aspect, in conjunction with the thirty-seventh aspect, the device is further configured to send the security message to the server.

[0249] In the thirty-ninth aspect, in conjunction with the thirty-eighth aspect, the device is further configured to send group information to the server. In some specific implementations, the group information is associated with a group that includes the device and the other mobile entity.

[0250] In the fortieth aspect, in conjunction with the thirty-ninth aspect, the set of information includes the first BSM of the device, a portion of the second BSM of the other mobile entity, CPM; or a combination thereof.

[0251] In the forty-first aspect, in conjunction with one or more of aspects twenty-nine to forty-ten, the group configuration information indicates the transmission scheme of one or more mobile entities in the group with the server, the group being included in a combination of multiple groups, or a combination thereof.

[0252] In aspect 42, in conjunction with one or more of aspects 29 to 41, the device is further configured to receive signals from non-ground entities.

[0253] In aspect forty-three, in conjunction with aspect forty-two, the device is further configured to determine the position estimate of the device based on the received signal.

[0254] In the forty-fourth aspect, in conjunction with the forty-third aspect, the device is further configured to generate an indicator that indicates position accuracy information associated with the position estimate.

[0255] In aspect forty-fifth, in conjunction with aspect forty-fourth, the device is further configured to send the indicator.

[0256] In one or more aspects, the technology for supporting a security system may include additional aspects, such as any single aspect or any combination of aspects described below or in conjunction with one or more other processes or devices described elsewhere herein. In a forty-sixth aspect, supporting a security system may include an apparatus configured to receive signals from a non-ground entity. The apparatus is further configured to transmit an indicator indicating location accuracy information associated with a location estimate of the apparatus. The location estimate of the apparatus is based on the received signals. Additionally, the apparatus may perform or operate according to one or more aspects described below. In some embodiments, the apparatus includes a wireless device (such as a mobile entity, UE, vehicle) or a component of the wireless device. In some embodiments, the apparatus may include at least one processor and memory coupled to the processor. The processor may be configured to perform the operations described herein with respect to the apparatus. In some other embodiments, the apparatus may include a non-transitory computer-readable medium having program code recorded thereon, and the program code may be executable by a computer to cause the computer to perform the operations described herein with reference to the apparatus. In some embodiments, the apparatus may include one or more components configured to perform the operations described herein. In some specific implementations, the wireless communication method may include one or more operations described herein with reference to the apparatus.

[0257] In the forty-seventh aspect, in conjunction with the forty-sixth aspect, the device is further configured to receive alarm information associated with a potential collision between the object and the device.

[0258] In aspect forty-eight, in conjunction with aspect forty-seven, the alarm message is based on the indicator.

[0259] In aspect 49, in combination with one or more of aspects 46 to 48, the at least one processor is configured to execute processor-readable code to cause the at least one processor: the device is further configured to generate a GNSS sensor report indicating a DOP scalar.

[0260] In the fiftieth aspect, in conjunction with one or more of the forty-sixth to forty-eighth aspects, the device is further configured to generate sensor measurements including a DOP scalar.

[0261] In the fifty-first aspect, in conjunction with the fifty-second aspect, the DOP scalar includes horizontal DOP, positional DOP, or a combination thereof.

[0262] In aspect 52, in conjunction with aspect 51, the device is further configured to determine the position estimate of the device based on the received signal.

[0263] In aspect 53, in conjunction with aspect 52, the device is further configured to determine an accuracy level based on the DOP scalar, wherein the position accuracy information includes the determined accuracy level.

[0264] In aspect 54, in conjunction with aspect 53, the device is further configured to generate an indicator.

[0265] In aspect 55, in conjunction with aspect 54, the device is further configured to generate a security message including the indicator indicating the level of accuracy.

[0266] In aspect 56, in conjunction with aspect 55, the device is further configured to send the security message.

[0267] In aspect 57, in conjunction with aspect 56, the security message includes basic security messages or personal security messages.

[0268] In one or more aspects, the technology used to support the safety system may include additional aspects, such as any single aspect or any combination of aspects described below or in conjunction with one or more other processes or devices described elsewhere herein. In a fifty-eighth aspect, supporting the safety system may include an apparatus configured to receive an indicator from a first moving entity, the indicator indicating position accuracy information associated with a position estimate of the first moving entity based on signals received from a non-ground entity. The apparatus is further configured to send alarm information to one or more moving entities. The alarm information is associated with a potential collision between an object and the one or more moving entities. A potential collision is determined based on the indicator. Additionally, the apparatus may perform or operate according to one or more aspects described below. In some embodiments, the apparatus includes a device (such as a server) or a component of that device. In some embodiments, the apparatus may include at least one processor and memory coupled to the processor. The processor may be configured to perform the operations described herein with respect to the apparatus. In some other embodiments, the apparatus may include a non-transitory computer-readable medium having program code recorded thereon, and the program code may be executable by a computer to cause the computer to perform the operations described herein with reference to the apparatus. In some embodiments, the apparatus may include one or more components configured to perform the operations described herein. In some embodiments, the method of wireless communication may include one or more operations described herein with reference to the apparatus.

[0269] In aspect 59, in conjunction with aspect 58, the location accuracy information includes an accuracy level determined based on the DOP scalar indicated by GNSS sensor reports.

[0270] In the sixtieth aspect, in conjunction with the fifty-ninth aspect, the DOP scalar includes horizontal DOP, positional DOP, or a combination thereof.

[0271] In the sixty-first aspect, in conjunction with the sixtieth aspect, the DOP scalar is generated based on sensor measurements that are based on the signal received from the non-ground entity.

[0272] In aspect sixty-two, in conjunction with one or more of aspects fifty-eight to sixty-one, the device is further configured to select an accuracy value based on the indicator.

[0273] In aspect sixty-three, in conjunction with aspect sixty-two, the accuracy value includes the horizontally estimated position error based on historical tracking information or the position accuracy information.

[0274] In the sixty-fourth aspect, in conjunction with the sixty-second or sixty-third aspect, the device is further configured to generate the position value of the first moving entity based on the accuracy value.

[0275] In aspect sixty-five, in conjunction with aspect sixty-four, the device is further configured to determine the potential collision based on the position value.

[0276] In the sixty-sixth aspect, in conjunction with one or more of aspects fifty-eight to sixty-five, the device is further configured to receive a security message including the indicator.

[0277] In aspect sixty-seven, in conjunction with aspect sixty-six, the safety message includes a basic safety message or a pedestrian safety message.

[0278] In aspect sixty-eight, in combination with one or more of aspects fifty-eight to sixty-seven, the device is further configured to generate the alarm information based on map information.

[0279] Those skilled in the art will understand that information and signals can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0280] This article is relative to Figures 1 to 13 The components, functional blocks, and modules described include processors, electronic devices, hardware devices, electronic components, logic circuits, memory, software code, firmware code, and so on, or any combination thereof. Software should be interpreted broadly as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, and / or functions, regardless of whether it is referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. Furthermore, the features discussed herein can be implemented via dedicated processor circuitry, via executable instructions, or a combination thereof.

[0281] Those skilled in the art will further understand that the various exemplary logic blocks, modules, circuits, and algorithm steps described in conjunction with the disclosure herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability between hardware and software, various exemplary components, blocks, modules, circuits, and steps have been described above in general terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole. Those skilled in the art can implement the described functionality in different ways for each specific application, but such specific implementation decisions should not be construed as departing from the scope of this disclosure. Those skilled in the art will also readily recognize that the order or combination of components, methods, or interactions described herein is merely illustrative, and that components, methods, or interactions of various aspects of this disclosure can be combined or performed in ways other than those illustrated and described herein.

[0282] The various exemplary logics, logic blocks, modules, circuits, and algorithmic processes described in conjunction with the specific implementations disclosed herein can be implemented as electronic hardware, computer software, or a combination of both. The interchangeability of hardware and software has been broadly described in terms of functionality and illustrated in the aforementioned exemplary components, blocks, modules, circuits, and processes. Whether such functionality is implemented in hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0283] Hardware and data processing means for implementing the various exemplary logic, logic blocks, modules, and circuits described herein can be implemented or executed using a general-purpose single-chip or multi-chip processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor can be a microprocessor, or any conventional processor, controller, microcontroller, or state machine. In some embodiments, the processor may be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration. In some embodiments, specific processes and methods may be performed by circuitry specific to a given function.

[0284] In one or more aspects, the described functionality may be implemented in hardware, digital electronic circuits, computer software, firmware, including the structures disclosed in this specification and their structural equivalents or any combination thereof. Specific 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 a computer storage medium for execution by a data processing apparatus or for controlling the operation of a data processing apparatus.

[0285] If implemented in software, the functionality can be stored as one or more instructions or code on or transmitted through a computer-readable medium. The processes of the methods or algorithms disclosed herein can be implemented in a processor-executable software module that can reside on a computer-readable medium. Computer-readable media include both computer storage media and communication media, including any medium that can be implemented to transfer a computer program from one location to another. Storage media can be any available medium accessible to a computer. By way of 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 disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other medium capable of storing desired program code in the form of instructions or data structures and accessible to a computer. Additionally, any connection may be appropriately referred to as a computer-readable medium. As used herein, disks and optical discs include compact optical discs (CDs), laser discs, optical discs, digital versatile optical discs (DVDs), floppy disks, and Blu-ray discs, wherein disks typically magnetically reproduce data, while optical discs optically reproduce data using lasers. Combinations of the above should also be included within the scope of computer-readable media. Additionally, the operation of a method or algorithm may reside as a set of code and instructions or any combination of code and instructions on a machine-readable medium and a computer-readable medium that may be incorporated into a computer program product.

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

[0287] Additionally, those skilled in the art will readily recognize that the terms “upper” and “lower” are sometimes used to facilitate the description of the drawings and to indicate relative positions on a correctly oriented page corresponding to the orientation of the drawings, and may not reflect the correct orientation of any device as implemented.

[0288] Certain features described in this specification in the context of a single embodiment may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments. Furthermore, although features may be described above as operating in certain combinations and even originally claimed in this way, one or more features from the claimed combination may be removed from that combination in some cases, and the claimed combination may be for sub-combinations or variations thereof.

[0289] Similarly, although operations are depicted in a specific order in the accompanying drawings, this should not be construed as requiring such operations to be performed in the indicated specific order or sequential order, or to perform all illustrated operations to achieve the desired result. Furthermore, the drawings may schematically depict one or more example processes in the form of flowcharts. However, other operations not depicted may be combined with the schematically illustrated example processes. For example, one or more additional operations may be performed before, after, simultaneously with, or between any illustrated operation. In some contexts, multitasking and parallel processing are advantageous. Moreover, the separation of the various system components in the embodiments described above should not be construed as requiring such separation in all embodiments, 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. Additionally, some other embodiments also fall within the scope of the appended claims. In some cases, the actions recited in the claims may be performed in a different order and still achieve the desired result.

[0290] As used herein (including the claims), the term "or" in a list of two or more items means that any one of the listed items may be used alone, or any combination of two or more listed items may be used. For example, if a composition is described as containing component A, B, or C, the composition may contain A alone; B alone; C alone; a combination of A and B; a combination of A and C; a combination of B and C; or a combination of A, B, and C. Furthermore, as used herein (including the claims), "or" in a list of items beginning with "at least one of" indicates a separate list, such that a list such as "at least one of A, B, or C" refers to 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 items. The term "substantially" is defined as substantially 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 specific implementation, the term “substantially” may be used in place of “[percentage]” for the specified content, where the percentage includes 0.1%, 1%, 5% or 10%.

[0291] The prior description of this disclosure is provided to enable any person skilled in the art to make or use this disclosure. Various modifications to this 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 this disclosure. Therefore, this 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 server, the server comprising: Memory, the memory storing processor-readable code; and At least one processor, coupled to the memory, is configured to execute processor-readable code to enable the at least one processor to: Receive first information from the first mobile entity; Send group configuration information to the first mobile entity, the group configuration information being generated based on map information and indicating a group including the first mobile entity and the second mobile entity; as well as Send an alarm message to the group.

2. The server according to claim 1, wherein: The alarm information is generated based on the map information. The map information indicates population density, traffic density, or a combination thereof; The group configuration information indicates that the first mobile entity is designated as the group leader of the group; or Their combination.

3. The server of claim 1, wherein the at least one processor is configured to execute processor-readable code to cause the at least one processor to: Receive the second information of the second mobile entity from the second mobile entity; Based on the first information, the second information, the map information, or a combination thereof, select multiple mobile entities to be included in the group; and Generate the group configuration information that indicates the plurality of mobile entities.

4. The server of claim 3, wherein the at least one processor is configured to execute processor-readable code to cause the at least one processor to: Receive group information from the first mobile entity; and Receive third information from the user equipment (UE), and in: The first information includes a first security message; The second information includes a second security message; The group information includes a third security message associated with the group; The alarm information is further generated based on the third information; or Their combination.

5. The server according to claim 3, wherein: The at least one processor is configured to execute processor-readable code to cause the at least one processor to: receive group information from the first mobile entity; and The group information includes: The first basic security message (BSM) of the first mobile entity; The second mobile entity is part of the second BSM; Collective Perception Messages (CPM); or Their combination.

6. The server of claim 5, wherein the at least one processor is configured to execute processor-readable code to cause the at least one processor to: The entry time of the group into the region is estimated based on the group information, the region being associated with the map information; and Estimate the departure time of the group from the area, the departure time being estimated based on the first information, the second information, the map information, the group information, the entry time, or a combination thereof.

7. The server according to claim 1, wherein: The at least one processor is configured to execute processor-readable code to enable the at least one processor to: Identify potential collisions within a region, said potential collisions occurring between at least one moving entity in the group and an object within the region; and The alarm information is generated based on the identified potential collisions, and The alarm message was sent to: The group leader; The at least one moving entity; The group consists of mobile entities other than the group leader and the at least one mobile entity; or Their combination.

8. The server of claim 1, wherein the group configuration information indicates the transmission scheme of one or more mobile entities in the group with the server.

9. The server of claim 1, wherein the at least one processor is configured to execute processor-readable code to cause the at least one processor to: The first subgroup and the second subgroup of the group are determined based on the map information, wherein the group configuration information indicates the first subgroup and the second subgroup, the first subgroup includes the first mobile entity, and the second subgroup includes the second mobile entity; Receive a first set of messages from the first mobile entity included in the first subgroup; and Receive the second set of messages from the second mobile entity.

10. The server of claim 1, wherein the at least one processor is configured to execute processor-readable code to cause the at least one processor to: Based on the map information, determine to combine another group of one or more mobile entities with the group to form a combined group; Send additional group configuration information indicating the combined group to the group; and Receive group information from at least one mobile entity in the group.

11. The server of claim 1, wherein the at least one processor is configured to execute processor-readable code to cause the at least one processor to: Receive group information from the group, the group information indicating position accuracy information based on factor of precision (DOP) information and associated with position estimation of the first moving entity based on signals received from non-ground entities; and The alarm information is generated based on the location accuracy information.

12. A mobile entity, the mobile entity comprising: Memory, the memory storing processor-readable code; and At least one processor, coupled to the memory, is configured to execute processor-readable code to enable the at least one processor to: Send the first information of the mobile entity to the server; Receive group configuration information from the server, the group configuration information being based on map information and indicating a group that includes the mobile entity and another mobile entity; as well as To communicate with the other mobile entity in the group based on the group configuration information.

13. The mobile entity of claim 12, wherein the at least one processor is configured to execute processor-readable code to cause the at least one processor to: Communication is performed via a side link established between the mobile entity and the other mobile entity; and Send group information to the server, the group information being associated with the group including the mobile entity and the other mobile entity, and in: The map information indicates population density, traffic density, or a combination thereof; The group configuration information indicates that the mobile entity is designated as the group leader; or Their combination.

14. The mobile entity according to claim 12, wherein: The at least one processor is configured to execute processor-readable code to cause the at least one processor to: receive alarm information from the server; and The alarm message indicates: The potential collision of the moving entity; A potential collision with another moving entity in the group; The potential changes in the movement of the other moving entity; or Their combination.

15. The mobile entity of claim 12, wherein the at least one processor is configured to execute processor-readable code to cause the at least one processor to: Receive the second information of the other mobile entity from the other mobile entity; A security message is generated based on the second information, the third information of the mobile entity, or a combination thereof; and Send the security message to the server.

16. The mobile entity according to claim 15, wherein: The at least one processor is configured to execute processor-readable code to cause the at least one processor to: send group information to the server, the group information being associated with the group including the mobile entity and the other mobile entity; and The group information includes: The first basic security message (BSM) of the mobile entity; Part of the second BSM of the other mobile entity; Collective Perception Messages (CPM); or Their combination.

17. The mobile entity of claim 12, wherein the group configuration information indicates: The sending scheme of one or more mobile entities in the group and the server; The group is included in a combination of multiple groups; or Their combination.

18. The mobile entity of claim 12, wherein the at least one processor is configured to execute processor-readable code to cause the at least one processor to: Receiving signals from non-ground entities; The position estimate of the moving entity is determined based on the received signals; Generate an indicator that indicates the location accuracy information associated with the location estimate; as well as Send the indicated signal.

19. A mobile entity, the mobile entity comprising: Memory, the memory storing processor-readable code; and At least one processor, coupled to the memory, is configured to execute processor-readable code to enable the at least one processor to: Receiving signals from non-ground entities; as well as Send an indicator that indicates location accuracy information associated with the location estimate of the mobile entity, which is based on the received signal.

20. The mobile entity of claim 19, wherein the at least one processor is configured to execute processor-readable code to cause the at least one processor to: Receive alarm information associated with a potential collision between the object and the moving entity, and The alarm information is based on the indicator.

21. The mobile entity of claim 19, wherein the at least one processor is configured to execute processor-readable code to cause the at least one processor to: generate a Global Navigation Satellite System (GNSS) sensor report indicating a factor of precision (DOP) scalar.

22. The mobile entity of claim 19, wherein the at least one processor is configured to execute processor-readable code to cause the at least one processor to: generate a sensor measurement including a precision factor (DOP) scalar, the DOP scalar including horizontal DOP, position DOP, or a combination thereof.

23. The mobile entity of claim 22, wherein the at least one processor is configured to execute processor-readable code to cause the at least one processor to: The position estimate of the moving entity is determined based on the received signals; The accuracy level is determined based on the DOP scalar, wherein the location accuracy information includes the determined accuracy level. Generate indicator; Generate a security message including the indicator indicating the accuracy level; and Send the security message.

24. The mobile entity of claim 23, wherein the security message includes a basic security message or a personal security message.

25. A server, the server comprising: Memory, the memory storing processor-readable code; and At least one processor, coupled to the memory, is configured to execute processor-readable code to enable the at least one processor to: Receive an indicator from a first mobile entity, the indicator indicating location accuracy information associated with a location estimate of the first mobile entity based on signals received from a non-ground entity; as well as An alert message is sent to one or more moving entities, the alert message being associated with a potential collision between the object and the one or more moving entities, the potential collision being determined based on the indicator.

26. The server of claim 25, wherein the location accuracy information includes an accuracy level determined based on a precision factor (DOP) scalar indicated by a Global Navigation Satellite System (GNSS) sensor report.

27. The server according to claim 26, wherein: The DOP scalar includes horizontal DOP, positional DOP, or a combination thereof; The DOP scalar is generated based on sensor measurements, which are based on signals received from the non-ground entity; or Their combination.

28. The server of claim 25, wherein the at least one processor is configured to execute processor-readable code to cause the at least one processor to: An accuracy value is selected based on the indicator, the accuracy value including: Horizontal estimation of position error based on historical tracking information; or The location accuracy information; The position value of the first moving entity is generated based on the accuracy value; as well as The potential collision is determined based on the location value.

29. The server according to claim 25, wherein: The at least one processor is configured to execute processor-readable code to cause the at least one processor to: receive a security message including the indicator; and The safety messages include basic safety messages or pedestrian safety messages.

30. The server of claim 25, wherein the at least one processor is configured to execute processor-readable code to cause the at least one processor to generate the alarm information based on map information.

Images