Vehicle-to-pedestrian system based on sidelink

Abstract

Methods, systems, and devices for wireless communications are described. A user equipment (UE) (e.g., a P‑UE) carried by a pedestrian may receive control signaling indicating a resource allocation for a sidelink channel for pedestrian-to-vehicle communications. The P‑UE may send a message including an identifier of the P‑UE within the resource allocation for the sidelink channel based on movement data of the PUE being classified as pedestrian movement. The P‑UE may monitor the sidelink channel for a collision warning message including the identifier of the P‑UE from a vehicle UE based on sending the message. If the P‑UE receives a collision warning message including its identifier, the P‑UE may present an alert based on receiving the collision warning message.

Description

[0001] Cross-references

[0002] This patent application claims the benefit of U.S. Provisional Patent Application Serial No. 62 / 865,791, filed on June 24, 2019, by BALASUBRAMANIAN et al., entitled “SIDELINKBASED VEHICLE-TO-PEDESTRIAN SYSTEM”; and U.S. Patent Application Serial No. 16 / 908,495, filed on June 22, 2020, by BALASUBRAMANIAN et al., entitled “SIDELINK BASED VEHICLE-TO-PEDESTRIAN SYSTEM”; each of which is assigned to the assignee of this patent application. Technical Field

[0003] The following relates generally to wireless communications, and more particularly to a sidelink-based vehicle-to-pedestrian (V2P) system. Background Art

[0004] Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcasting, etc. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth generation (4G) systems such as long term evolution (LTE) systems, advanced LTE (LTE-A) systems, or LTE-A Pro systems, and fifth generation (5G) systems that may be referred to as new radio (NR) systems. These systems may employ techniques such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), or discrete Fourier transform extended orthogonal frequency division multiple access (DFT-S-OFDM). A wireless multiple access communication system may include multiple base stations or network access nodes, each of which simultaneously supports communication of multiple communication devices, which may be referred to as user equipment (UE) in addition.

[0005] Some wireless communication systems may support direct communication between multiple communication devices. Examples of direct communication may include, but are not limited to, device-to-device (D2D) communication, vehicle-based communication (also referred to as V2P network), vehicle-to-everything (V2X) network, vehicle-to-vehicle (V2V) network, cellular V2X (C-V2X) network, etc. As the demand for communication efficiency increases, some wireless communication systems may not be able to provide satisfactory power management, and thus improved technology is desired. Summary of the invention

[0006] The described technology relates to improved methods, systems, devices and apparatus for supporting sidelink-based vehicle-to-pedestrian (V2P) systems. Generally, the described technology provides for presenting a warning of a predicted collision with a vehicle to a pedestrian. The wireless communication system described herein can support direct communication (such as V2P wireless communication) between multiple communication devices or user equipment (UE). In a V2P wireless communication system, device-to-device communication can occur between a vehicle (also referred to as a V-UE) and a UE carried by a pedestrian (also referred to as a P-UE). Some V2P wireless communication systems can support a sidelink channel (such as via a PC5 interface) for V-UE and P-UE to exchange V2P and P2V messages.

[0007] The V2P wireless communication system described herein can support effectively warning a P-UE of a predicted collision with a V-UE. For example, the P-UE can use various sensors of the P-UE to determine whether a carrying user is moving based on the pedestrian's mobility profile (e.g., walking, running, cycling, etc.). The P-UE can determine the pedestrian's mobility profile based on pedestrian characteristics that can be measured by sensors (such as the pedestrian's gait, speed, direction of movement, limb movement or swing, etc.). If the P-UE is traveling in one of these pedestrian mobility profiles, the P-UE can generate a message to be broadcast to nearby vehicles on a sidelink channel. The message generated by the P-UE may include an identifier of the P-UE, the location of the P-UE, an indicator of the pedestrian's intention (e.g., a trajectory), or any combination thereof.

[0008] A nearby V-UE may monitor messages from a P-UE. The V-UE may receive messages from the P-UE on a sidelink and determine whether the P-UE is predicted to collide with the V-UE. The collision prediction may be determined based on information included in a message sent by the P-UE, visual measurements, radar measurements, or any combination thereof. If the V-UE is predicted to be on a collision course with the P-UE, the V-UE may generate a collision warning message including an identifier of the P-UE at risk and send the collision warning message on a sidelink channel. The P-UE may receive the collision warning message on the sidelink channel and present an alert (e.g., on a display of the P-UE, via vibration, or using an audio prompt) if the collision warning message carries the identifier of the P-UE. The alert may notify a pedestrian of the predicted collision with the V-UE so that the pedestrian may take action to avoid the collision. If the collision warning message does not include an identifier of the P-UE, the P-UE may discard the collision warning message.

[0009] A method of wireless communication by a UE is described. The method may include: receiving control signaling indicating a resource allocation of a sidelink channel for pedestrian-to-vehicle communication; based on movement data of the UE being classified as pedestrian movement, sending a message including an identifier of the UE within the resource allocation of the sidelink channel; and based on sending the message, monitoring the sidelink channel for a collision warning message including the identifier of the UE from a vehicle UE.

[0010] An apparatus for wireless communication by a UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions are executable by the processor to cause the apparatus to: receive control signaling indicating resource allocation of a sidelink channel for pedestrian-to-vehicle communication; based on movement data of the UE being classified as pedestrian movement, send a message including an identifier of the UE within the resource allocation of the sidelink channel; and based on sending the message, monitor the sidelink channel for a collision warning message including the identifier of the UE from a vehicle UE.

[0011] Another apparatus for wireless communication by a UE is described. The apparatus may include components for: receiving control signaling indicating resource allocation of a sidelink channel for pedestrian-to-vehicle communication; based on movement data of the UE being classified as pedestrian movement, sending a message including an identifier of the UE within the resource allocation of the sidelink channel; and based on sending the message, monitoring the sidelink channel for a collision warning message including the identifier of the UE from a vehicle UE.

[0012] A non-transitory computer-readable medium storing code for wireless communication by a UE is described. The code may include instructions executable by a processor to: receive control signaling indicating resource allocation of a sidelink channel for pedestrian-to-vehicle communication; based on movement data of the UE being classified as pedestrian movement, send a message including an identifier of the UE within the resource allocation of the sidelink channel; and based on sending the message, monitor the sidelink channel for a collision warning message including the identifier of the UE from the vehicle UE.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending a message may include operations, features, components, or instructions for sending a message including location data of the UE, track data of the UE, or both.

[0014] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, monitoring the sideband channel may include operations, features, components, or instructions for monitoring a vehicle-to-pedestrian resource pool for a sidelink channel for a collision warning message.

[0015] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending a message may include operations, features, components, or instructions for sending a message including an identifier, which may be a pseudo-identifier of the UE.

[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending a message may include operations, features, components, or instructions for sending a message including a packet that includes a pseudo-identifier of a UE as a source identifier of the packet and a broadcast identifier as a destination identifier of the packet.

[0017] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a collision warning message including an identifier of a second UE that may be different from the UE, and discarding the collision warning message.

[0018] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a collision warning message including an identifier of the UE and presenting an alert based on receiving the collision warning message.

[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the alarm may be an audible alarm, a displayed alarm, or both.

[0020] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining that a second identifier included as a destination identifier in the collision warning message matches an identifier of the UE.

[0021] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for classifying the movement data as pedestrian movement based on the movement data corresponding to a pedestrian movement profile in a set of different movement profiles.

[0022] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include: at least one sensor for monitoring a UE and operations, features, components, or instructions for determining a movement parameter based on the monitoring, wherein movement data of the UE may be classified as pedestrian movement based on the movement parameter.

[0023] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the movement parameter may be a gait parameter, a speed parameter, a direction parameter, a limb movement parameter, or any combination thereof.

[0024] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending a message may include operations, features, components, or instructions for sending the message via a sidelink channel using a sidelink interface of the UE.

[0025] A method for wireless communication by a vehicle UE is described. The method may include: receiving control signaling indicating a resource allocation for a sidelink channel for vehicle-to-pedestrian communication; receiving a message including an identifier of a first UE and location data of the first UE within the resource allocation for the sidelink channel; and sending a collision warning message including the identifier of the first UE via the sidelink channel based on a predicted collision with the first UE using the location data.

[0026] An apparatus for wireless communication by a vehicle UE is described. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions are executable by the processor to cause the apparatus to: receive control signaling indicating a resource allocation for a sidelink channel for vehicle-to-pedestrian communication; receive a message including an identifier of a first UE and location data of the first UE within the resource allocation for the sidelink channel; and send a collision warning message including an identifier of the first UE via the sidelink channel based on a collision predicted with the first UE using the location data.

[0027] Another apparatus for wireless communication by a vehicle UE is described. The apparatus may include components for: receiving control signaling indicating a resource allocation for a sidelink channel for vehicle-to-pedestrian communication; receiving a message including an identifier of a first UE and location data of the first UE within the resource allocation for the sidelink channel; and sending a collision warning message including an identifier of the first UE via the sidelink channel based on a predicted collision with the first UE using the location data.

[0028] A non-transitory computer-readable medium storing code for wireless communication by a vehicle UE is described. The code may include instructions executable by a processor to: receive control signaling indicating a resource allocation for a sidelink channel for vehicle-to-pedestrian communication; receive a message including an identifier of a first UE and location data of the first UE within the resource allocation for the sidelink channel; and send a collision warning message including the identifier of the first UE via the sidelink channel based on a collision predicted with the first UE using the location data.

[0029] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving a message may include operations, features, components, or instructions for receiving a message including trajectory data of the first UE, wherein the collision may be predicted based on the trajectory data.

[0030] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving a message may include operations, features, components, or instructions for receiving a message including trajectory data of the first UE, movement data of the first UE, or both, wherein the collision may be predicted based on gait parameters, speed parameters, direction parameters, limb movement parameters, or any combination thereof.

[0031] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending the collision warning message may include operations, features, components, or instructions for sending the collision warning message including an identifier of the first UE as a destination identifier in the collision warning message.

[0032] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending a collision warning message may include operations, features, components, or instructions for sending the collision warning message via a sidelink channel using a sidelink interface of the vehicle UE.

[0033] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for changing a speed, a vehicle trajectory, or both of a vehicle including the vehicle UE based on a prediction.

[0034] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for generating an alert based on a prediction.

[0035] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a second message including an identifier of a second UE and location data of the second UE, predicting based on the second message that the vehicle UE may not be on a collision path with the second UE, and determining not to send a second collision warning message including an identifier of the second UE based on the prediction. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] Figure 1

[0013] An example of a system for wireless communications in accordance with aspects of the present disclosure is shown.

[0037] Figure 2 An example of a V2P wireless communication system according to aspects of the present disclosure is shown.

[0038] Figure 3 Examples of sidelink channel communications exchanges in accordance with aspects of the present disclosure are shown.

[0039] Figure 4 An example of a process flow according to aspects of the present disclosure is shown.

[0040] Figure 5 and Figure 6 A block diagram of a device according to aspects of the present disclosure is shown.

[0041] Figure 7 A block diagram of a communications manager in accordance with aspects of the present disclosure is shown.

[0042] Figure 8 A diagram of a system in accordance with aspects of the present disclosure is shown.

[0043] Figures 9 to 12 A flow chart illustrating a method according to aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0044] Some wireless communication systems may support direct communication between multiple communication devices, which may be further referred to as user equipment (UE). Examples of direct communication may include device-to-device (D2D) communication, which may include vehicle-based communication such as vehicle-to-pedestrian (V2P) wireless communication systems. In a V2P wireless communication system, D2D communication may occur between a vehicle (also referred to as a "V-UE") and a UE carried by a pedestrian (also referred to as a "P-UE"). Some wireless communication systems may support communication between vehicles and other devices. For example, some wireless communication systems may support vehicle-to-vehicle (V2V) communication, V2P communication, or vehicle-to-everything (V2X) communication. Direct communication between a V-UE and a P-UE may occur via a direct connection, which may be a sidelink connection (such as via a PC5 interface). Thus, the V-UE and the P-UE may exchange information via V2P messages and pedestrian-to-vehicle (P2V) messages using the PC5 interface.

[0045] Some vehicle-based wireless communication systems may have deficiencies in addressing road safety, and more specifically, in improving pedestrian safety via direct communication. In some examples, to address pedestrian safety, the P-UE may continuously monitor a sidelink (e.g., a PC5 interface) to obtain messages (e.g., warning messages) from the V-UE. However, continuous monitoring of the sidelink by the P-UE may result in increased power consumption, for example, due to the non-stop operation of the PC5 interface receiving circuit. Due to the limited resources of the P-UE (e.g., battery life), it may be challenging to improve pedestrian safety in a V2P wireless communication system while minimizing power consumption. Therefore, as the demand for communication efficiency and pedestrian safety improvements in V2P wireless communication systems increases, it may be desirable to improve the power management of the P-UE.

[0046] Described herein are techniques for effectively warning a P-UE of a predicted collision with a V-UE. The P-UE may determine whether a carrying user is moving based on the pedestrian's mobility profile. For example, the P-UE may use sensors on the device to determine whether the pedestrian is walking, running, riding a bicycle, etc., and when the pedestrian is near a road. The P-UE may determine the pedestrian's mobility profile based on pedestrian characteristics that may be measured by sensors, such as the pedestrian's gait, speed, direction of movement, limb movement or swing, etc. If the P-UE is traveling in one of these pedestrian mobility profiles, the P-UE may generate a message to be broadcast to nearby vehicles on a sidelink channel. The message generated by the P-UE may include an identifier of the P-UE, the location of the P-UE, an indicator of the pedestrian's intent (e.g., a trajectory), or any combination thereof. The intent indicator may convey the P-UE's mode of travel or the P-UE's mobility information, which may be based on sensor measurements.

[0047] A nearby V-UE may monitor messages from a P-UE. For example, a V-UE may receive messages from multiple P-UEs, and each message may contain a P-UE identifier, location, and intent. The V-UE may determine whether any of the P-UEs is predicted to collide with the V-UE. The collision prediction may be determined based on information included in the message, visual measurements, radar measurements, or any combination thereof. If the V-UE is on a collision course with the P-UE, the V-UE may generate a collision warning message that includes an identifier of the P-UE and may include an indication that the P-UE is predicted to collide with the V-UE. The V-UE may then send a collision warning message with an identifier of the P-UE of interest on a sidelink channel. The P-UE may receive the collision warning message on the sidelink channel and check whether the message includes an identifier of the P-UE. If the collision warning message is for the P-UE, the P-UE may present an alert (e.g., on a display of the P-UE, via vibration, or using an audio prompt). This may notify pedestrians of a predicted collision with the V-UE so that the pedestrians may take action to avoid the collision. If the collision warning message does not include the identifier of the P-UE, the P-UE may discard the collision warning message (eg, because the collision warning message may be intended for a different P-UE).

[0048] Aspects of the present disclosure are initially described in the context of a wireless communication system. Aspects of the present disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flow charts related to a sidelink-based V2P system.

[0049] Figure 1An example of a wireless communication system 100 supporting a sidelink-based V2P system according to aspects of the present disclosure is shown. The wireless communication system 100 may include a base station 105, a UE 115, and a core network 130. In some examples, the wireless communication system 100 may be a long term evolution (LTE) network, an advanced LTE (LTE-A) network, an LTE-A Pro network, or a new radio (NR) network. In some cases, the wireless communication system 100 may support enhanced broadband communications, ultra-reliable (e.g., mission-critical) communications, low-latency communications, communications with low-cost and low-complexity devices, or any combination thereof.

[0050] The base stations 105 may be dispersed throughout a geographic area to form the wireless communication system 100, and may be different forms of devices or devices with different capabilities. The base stations 105 and the UEs 115 may communicate wirelessly via one or more communication links 125. Each base station 105 may provide a coverage area 110 over which the UEs 115 and the base stations 105 may establish a communication link 125. The coverage area 110 may be an example of a geographic area over which the base stations 105 and the UEs 115 support communication of signals according to one or more radio access technologies.

[0051] The UEs 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary, mobile, or both at different times. The UEs 115 may be different forms of devices or devices with different capabilities. Figure 1 Some example UEs 115 are shown in FIG. 1. The UEs 115 described herein may be capable of communicating with various types of devices, such as Figure 1 Other UEs 115, base stations 105, and / or network equipment (eg, core network nodes, relay devices, integrated access and backhaul (IAB) nodes, or other network equipment) are shown.

[0052] The base stations 105 may communicate with the core network 130, or with each other, or both. For example, the base stations 105 may interface with the core network 130 via a backhaul link 120 (e.g., via S1, N2, N3, or other interface). The base stations 105 may communicate with each other directly (e.g., directly between the base stations 105) or indirectly (e.g., via the core network 130), or both, via the backhaul link 120 (e.g., via X2, Xn, or other interface). In some examples, the backhaul link 120 may be or include one or more wireless links.

[0053] The one or more base stations 105 described herein may include or may be referred to by those skilled in the art as a base station transceiver, a radio base station, an access point, a radio transceiver, a NodeB, an eNodeB (eNB), a next generation NodeB or a giga NodeB (any of which may be referred to as a gNB), a Home NodeB, a Home eNodeB, or other suitable terminology.

[0054] UE 115 may include or be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable terminology, where "device" may also be referred to as a unit, a station, a terminal, a client, and other examples. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, a machine type communication (MTC) device, etc., which may be implemented in various objects such as appliances, vehicles, meters, etc.

[0055] The UE 115 described herein may be capable of communicating with various types of devices, such as Figure 1 Other UEs 115 as well as base stations 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, relay base stations, etc. are shown, which may sometimes act as relays.

[0056] UE 115 and base station 105 can communicate with each other wirelessly via one or more communication links 125 on one or more carriers. The term "carrier" can refer to a set of radio spectrum resources with a defined physical layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of a radio frequency spectrum band (e.g., bandwidth portion (BWP)) that operates according to a physical layer channel of a given radio access technology (e.g., LTE, LTE-A, LTE-APro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling for coordinating operations for carriers, user data, or other signaling. The wireless communication system 100 may support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 may be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used with both frequency division duplex (FDD) and time division duplex (TDD) component carriers.

[0057] In some examples (e.g., in a carrier aggregation configuration), a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute Radio Frequency Channel Number (EARFCN)) and may be located according to a channel grid for discovery by a UE 115. A carrier may operate in a standalone mode, where initial acquisition and connection may be performed by a UE 115 via the carrier, or a carrier may operate in a non-standalone mode, where a different carrier (e.g., with the same or different radio access technology) is used to anchor the connection.

[0058] The communication link 125 shown in the wireless communication system 100 may include an uplink transmission from the UE 115 to the base station 105, or a downlink transmission from the base station 105 to the UE 115. A carrier may carry downlink or uplink communications (e.g., in FDD mode), or may be configured to carry both downlink and uplink communications (e.g., in TDD mode).

[0059] A carrier may be associated with a particular bandwidth of a radio frequency spectrum, and in some examples, the carrier bandwidth may be referred to as a "system bandwidth" of a carrier or wireless communication system 100. For example, a carrier bandwidth may be one of a plurality of predetermined bandwidths of a carrier for a particular radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz)). A device of the wireless communication system 100 (e.g., a base station 105 or a UE 115 or both) may have a hardware configuration that supports communication on a particular carrier bandwidth, or may be configured to support communication on one of a set of carrier bandwidths. In some examples, the wireless communication system 100 may include a base station 105 and / or a UE 115 that supports simultaneous communication via carriers associated with a plurality of carrier bandwidths. In some examples, each served UE 115 may be configured to operate on a portion (e.g., a subband, a BWP) or all of a carrier bandwidth.

[0060] The signal waveform transmitted on the carrier may be composed of multiple subcarriers (e.g., using multicarrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing MCM techniques, a resource element may be composed of a symbol period (e.g., the duration of a modulation symbol) and a subcarrier, where the symbol period and the subcarrier spacing are inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the codec rate of the modulation scheme, or both). Therefore, the more resource elements received by UE 115 and the higher the order of the modulation scheme, the higher the data rate of UE 115 may be. Wireless communication resources may refer to a combination of radio frequency spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial layers may also increase the data rate or data integrity of communications with UE 115.

[0061] One or more numerologies may be supported for a carrier, where the numerology may include subcarrier spacing (Δf) and cyclic prefix. A carrier may be divided into BWPs with the same or different numerologies. In some examples, a UE 115 may be configured with multiple BWPs. In some cases, a single BWP for a carrier is active at a given time, and communications by the UE 115 may be limited to the active BWP.

[0062] The time interval of the base station 105 or the UE 115 may be expressed as a multiple of a basic time unit, which may be, for example, T s =1 / (Δf max ·N f ) seconds sampling period, where Δf max It can represent the maximum supported subcarrier spacing, and N f The maximum supported discrete Fourier transform (DFT) size may be indicated. The time intervals of the communication resources may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0063] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some cases, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into multiple time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include multiple code element periods (e.g., depending on the length of the cyclic prefix preceding each code element period). In some wireless communication systems 100, a time slot may also be divided into multiple mini-slots containing one or more code elements. Excluding the cyclic prefix, each code element period may contain one or more (e.g., N f ) sampling period. The duration of a symbol period may depend on the subcarrier spacing or the operating frequency band.

[0064] A subframe, slot, mini-slot, or symbol may be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and may be referred to as a transmission time interval (TTI). In some cases, the TTI duration (e.g., the number of symbol periods in a TTI) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., in a burst of a shortened TTI (sTTI)).

[0065] Physical channels may be multiplexed on a carrier according to various techniques. For example, a physical control channel and a physical data channel may be multiplexed on a downlink carrier using a time division multiplexing (TDM) technique, a frequency division multiplexing (FDM) technique, or a hybrid TDM-FDM technique. A control region (e.g., a control resource set (CORESET)) of a physical control channel may be defined by a number of symbol periods and may extend across a system bandwidth of a carrier or a subset of that system bandwidth. One or more control regions (e.g., CORESETs) may be configured for a group of UEs 115. For example, a UE 115 may monitor or search a control region for control information according to one or more search space sets, and each search space set may include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level of a control channel candidate may refer to the number of control channel resources (e.g., control channel elements (CCEs)) associated with coded information of a control information format having a given payload size. A search space set may include a common search space set configured to send control information to multiple UEs 115 and a UE-specific search space set for sending control information to a specific UE 115.

[0066] Each base station 105 can provide communication coverage via one or more cells (e.g., macro cells, small cells, hot spots, or other types of cells, or various combinations thereof). The term "cell" may refer to a logical communication entity used to communicate with the base station 105 (e.g., via a carrier), and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or other identifier) ​​used to distinguish adjacent cells. In some examples, a cell may also refer to a geographic coverage area 110 or a portion of a geographic coverage area 110 (e.g., a sector) on which a logical communication entity operates. Depending on various factors such as the capabilities of the base station 105, the range of these cells may range from a smaller area (e.g., a structure, a subset of a structure) to a larger area. For example, a cell may be or include a building, a subset of a building, an external space between or overlapping a geographic coverage area 110, and the like.

[0067] A macro cell typically covers a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access to a UE 115 with a service subscription to a network provider that supports the macro cell. Compared to a macro cell, a small cell may be associated with a low-power base station 105, and the small cell may operate in the same or different (e.g., authorized, unauthorized) frequency band as the macro cell. A small cell may provide unrestricted access to a UE 115 with a service subscription to a network provider, or may provide restricted access to a UE 115 with an association to a small cell (e.g., a UE 115 in a closed user group (CSG), a UE 115 associated with a user in a home or office, etc.). A base station 105 may support one or more cells, and may also support communications on one or more cells using one or more component carriers.

[0068] In some examples, a carrier may support multiple cells, and different cells may be configured based on different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB), or other protocol types) that may provide access to different types of devices.

[0069] In some examples, base stations 105 may be mobile and, therefore, provide communication coverage for mobile geographic coverage areas 110. In some examples, different geographic coverage areas 110 associated with different technologies may overlap, but the different geographic coverage areas 110 may be supported by the same base station 105. In other examples, overlapping geographic coverage areas 110 associated with different technologies may be supported by different base stations 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of base stations 105 provide coverage for various geographic coverage areas 110 using the same or different radio access technologies.

[0070] The wireless communication system 100 may support synchronous or asynchronous operation. For synchronous operation, the base stations 105 may have similar frame timing, and transmissions from different base stations 105 may be approximately aligned in time. For asynchronous operation, the base stations 105 may have different frame timing, and in some examples, transmissions from different base stations 105 may not be aligned in time. The techniques described herein may be used for synchronous or asynchronous operation.

[0071] Some UEs 115, such as MTC or IoT devices, may be low-cost or low-complexity devices and may provide automatic communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC may refer to data communication technology that allows devices to communicate with each other or with a base station 105 without human intervention. In some examples, M2M communication or MTC may include communications from devices that are integrated with sensors or meters to measure or capture information and relay the information to a central server or application that utilizes the information or presents the information to a person interacting with the application. Some UEs 115 may be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based service charging.

[0072] Some UEs 115 may be configured to employ a reduced power consumption mode of operation, such as half-duplex communication (e.g., a mode supporting unidirectional communication via transmission or reception but not simultaneous transmission and reception). In some examples, half-duplex communication may be performed at a reduced peak rate. Other power saving techniques for UE 115 include entering a power saving deep sleep mode when not engaged in active communications, or operating on a limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some UEs 115 may be configured to operate using a narrowband protocol type associated with a predefined portion or range (e.g., a set of subcarriers or resource blocks (RBs)) within a carrier, within a guard band of a carrier, or outside a carrier.

[0073] The wireless communication system 100 can be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, the wireless communication system 100 can be configured to support ultra-reliable low-latency communication (URLLC) or mission-critical communication. UE 115 can be designed to support ultra-reliable, low-latency or critical functions (e.g., mission-critical functions). Ultra-reliable communication can include private communication or group communication, and can be supported by one or more mission-critical services (such as mission-critical push-to-talk (MCPTT), mission-critical video (MCVideo), or mission-critical data (MCData). Support for mission-critical functions can include prioritization of services, and mission-critical services can be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, mission-critical, and ultra-reliable low-latency are used interchangeably herein.

[0074] In some cases, UE 115 may also be able to communicate directly with other UE 115 via a device-to-device (D2D) communication link 135 (e.g., using a peer-to-peer (P2P) or D2D protocol). One or more UEs 115 utilizing D2D communication may be within a geographic coverage area 110 of a base station 105. Other UEs 115 in such a group may be outside the geographic coverage area 110 of a base station 105 or otherwise unable to receive transmissions from the base station 105. In some cases, groups of UEs 115 communicating via D2D communication may utilize a one-to-many (1:M) system in which each UE 115 transmits to each other UE 115 in the group. In some examples, base station 105 facilitates resource scheduling for D2D communication. In other cases, D2D communication is performed between UEs 115 without the involvement of base station 105.

[0075] In some systems, the D2D communication link 135 can be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, vehicles can communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these communications. Vehicles can signal information about traffic conditions, signal scheduling, weather, safety, emergency events, or any other information related to the V2X system. In some cases, vehicles in a V2X system can communicate with roadside infrastructure such as roadside units, or communicate with the network via one or more network nodes (e.g., base station 105) using vehicle-to-network (V2N) communication, or communicate with both. In some examples, UE 115 can be a P-UE 115 or a V-UE 115, or a combination thereof.

[0076] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), which may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), a user plane function (UPF)) for routing packets to an external network or interconnecting with an external network. The control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by a base station 105 associated with the core network 130. User IP packets may be transmitted through user plane entities, which may provide IP address allocation and other functions. The user plane entity may be connected to a network operator IP service 150. The operator IP service 150 may include access to the Internet, (one or more) intranets, an IP multimedia subsystem (IMS), or a packet-switched streaming service.

[0077] Some network devices, such as base stations 105, may include subcomponents such as access network entities 140, which may be examples of access node controllers (ANCs). Each access network entity 140 may communicate with UE 115 through multiple other access network transport entities 145, which may be referred to as radio heads, smart radio heads, or transmit / receive points (TRPs). Each access network transport entity 145 may include one or more antenna panels. In some configurations, the various functions of each access network entity 140 or base station 105 may be distributed across various network devices (e.g., radio heads and ANCs), or merged into a single network device (e.g., base station 105).

[0078] The wireless communication system 100 may operate using one or more frequency bands typically in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally, the region from 300 MHz to 3 GHz is referred to as the ultra-high frequency (UHF) region or decimeter band because the length of the wavelength ranges from about 1 decimeter to 1 meter. UHF waves may be blocked or redirected by buildings and environmental features, but these waves can penetrate structures sufficiently to allow macro cells to provide services to UEs 115 located indoors. Transmission of UHF waves may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers) compared to transmission of smaller frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0079] The wireless communication system 100 may also operate in the super high frequency (SHF) region (also known as the centimeter band) using a frequency band from 3 GHz to 30 GHz, or in the extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) (also known as the millimeter band). In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between the UE 115 and the base station 105, and the EHF antennas of each device may be smaller and more closely spaced than the UHF antennas. In some cases, this may facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may be subject to even greater atmospheric attenuation and a shorter range than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions using one or more different frequency regions, and the designated use of frequency bands across these frequency regions may vary by country or regulatory agency.

[0080] The wireless communication system 100 can utilize both the licensed video spectrum band and the unlicensed radio frequency spectrum band. For example, the wireless communication system 100 can adopt licensed assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed band such as the 5 GHz industrial, scientific, and medical (ISM) band. When operating in an unlicensed radio frequency spectrum band, devices such as base stations 105 and UEs 115 can use carrier sensing for collision detection and avoidance. In some cases, operations in unlicensed bands can be based on a combination of carrier aggregation configurations and component carriers operating in licensed bands (e.g., LAA). Operations in unlicensed spectrum can include downlink transmissions, uplink transmissions, P2P transmissions, D2D transmissions, and the like.

[0081] The base station 105 or UE 115 may be equipped with multiple antennas, which may be used to employ technologies such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communications, or beamforming. The antennas of the base station 105 or UE 115 may be located in one or more antenna arrays or antenna panels that may support MIMO operations, or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at antenna accessories such as antenna towers. In some cases, the antennas or antenna arrays associated with the base station 105 may be located in different geographical locations. The base station 105 may have an antenna array with multiple rows and columns of antenna ports, which the base station 105 may use to support beamforming for communications with the UE 115. Similarly, the UE 115 may have one or more antenna arrays that may support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support radio frequency beamforming for signals sent via the antenna ports.

[0082] The base station 105 or UE 115 can use MIMO communication to exploit multipath signal propagation and increase spectral efficiency by sending or receiving multiple signals via different spatial layers. This technology may be referred to as spatial multiplexing. Multiple signals may be sent, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry bits associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO technology includes single-user MIMO (SU-MIMO) in which multiple spatial layers are sent to the same receiving device and multi-user MIMO (MU-MIMO) in which multiple spatial layers are sent to multiple devices.

[0083] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting device or a receiving device (e.g., a base station 105 or a UE 115) to shape or steer an antenna beam (e.g., a transmit beam or a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming can be achieved by combining signals communicated via antenna elements of an antenna array so that some signals propagating at a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to signals communicated via antenna elements can include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to signals carried via antenna elements associated with the device. Adjustments associated with each antenna element can be defined by a set of beamforming weights associated with a particular orientation (e.g., relative to the antenna array of the transmitting device or the receiving device, or relative to some other orientation).

[0084] The base station 105 or the UE 115 may use beam scanning techniques as part of a beamforming operation. For example, the base station 105 may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communications with the UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be sent multiple times by the base station 105 in different directions. For example, the base station 105 may send signals based on different sets of beamforming weights associated with different transmission directions. Transmissions in different beam directions may be used (e.g., by a transmitting device such as the base station 105, or a receiving device such as the UE 115) to identify the beam direction for subsequent transmission and / or reception by the base station 105.

[0085] Some signals, such as data signals associated with a particular receiving device, may be sent by base station 105 in a single beam direction (e.g., a direction associated with a receiving device, such as UE 115). In some examples, the beam direction associated with transmissions along the single beam direction may be determined based on signals sent in different beam directions. For example, UE 115 may receive one or more of the signals sent by base station 105 in different directions, and UE 115 may report to base station 105 an indication of the signal it received having the highest signal quality or other acceptable signal quality.

[0086] In some cases, transmissions by a device (e.g., a base station 105 or a UE 115) may be performed using multiple beam directions, and the device may generate a combined beam for transmission (e.g., from the base station 105 to the UE 115) using a combination of digital precoding or radio frequency beamforming. The UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured number of beams across the system bandwidth or one or more subbands. The base station 105 may send reference signals (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)) that may be precoded or unprecoded. The UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook). Although these techniques are described with reference to signals sent by base station 105 in one or more directions, UE 115 may employ similar techniques to send signals multiple times in different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE 115), or to send signals in a single direction (e.g., to send data to a receiving device).

[0087] When receiving various signals such as synchronization signals, reference signals, beam selection signals, or other control signals from the base station 105, a receiving device (e.g., UE 115) can try multiple reception configurations (e.g., directional listening). For example, the receiving device can try multiple reception directions by receiving via different antenna subarrays, processing received signals according to different antenna subarrays, receiving according to different reception beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or processing received signals according to different reception beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which can be referred to as "listening" according to different reception configurations or reception directions. In some examples, the receiving device can receive along a single beam direction using a single reception configuration (e.g., when receiving a data signal). The single reception configuration can be aligned on a beam direction determined based on listening according to different reception configuration directions (e.g., a beam direction with the highest signal strength, the highest signal-to-noise ratio (SNR), or other acceptable signal quality determined based on listening according to multiple beam directions).

[0088] The wireless communication system 100 can be a packet-based network that operates according to a layered protocol stack. In the user plane, the communication at the bearer or packet data convergence protocol (PDCP) layer can be IP-based. The radio link control (RLC) layer can perform packet segmentation and reorganization to communicate on a logical channel. The medium access control (MAC) layer can perform priority processing and multiplexing of logical channels to transport channels. The MAC layer can also use error detection technology, error correction technology, or both to support retransmission at the MAC layer to improve link efficiency. In the control plane, the radio resource control (RRC) protocol layer can provide the establishment, configuration, and maintenance of the RRC connection (which supports the radio bearer of user plane data) between the UE 115 and the base station 105 or the core network 130. At the physical layer, the transport channel can be mapped to the physical channel.

[0089] UE 115 and base station 105 can support retransmission of data to increase the possibility of successfully receiving data. Hybrid automatic repeat request (HARQ) feedback is a technology that increases the possibility of correctly receiving data through communication link 125. HARQ can include a combination of error detection (e.g., using cyclic redundancy check (CRC)), forward error correction (FEC) and retransmission (e.g., automatic repeat request (ARQ)). HARQ can improve the throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some cases, the device can support simultaneous slot HARQ feedback, where the device can provide HARQ feedback for data received in the previous symbol in the slot in a specific time slot. In other cases, the device can provide HARQ feedback in subsequent time slots or according to some other time interval.

[0090] The wireless communication system 100 may support effectively warning a pedestrian-carrying UE 115 (e.g., a P-UE) about a predicted collision with a vehicle (e.g., a vehicle that may include certain aspects of the UE 115 or V-UE). For example, the P-UE may use various sensors of the device to determine whether the pedestrian is moving according to a certain mobility profile (such as walking, running, or cycling). The P-UE may determine the pedestrian mobility profile based on pedestrian characteristics that may be measured by sensors (such as the pedestrian's gait, speed, direction of movement, limb movement or swing, etc.). If the P-UE is traveling in one of these pedestrian mobility profiles, the P-UE may generate a message to be broadcast to nearby vehicles on a sidelink channel, which may be an example of a D2D communication link 135 between a V-UE and the P-UE. The message generated by the P-UE may include an identifier of the P-UE, the location of the P-UE, an indicator of the pedestrian's intent, or any combination thereof.

[0091] A nearby V-UE may monitor messages from a P-UE. The V-UE may receive a message from the P-UE on a sidelink and determine whether the P-UE is predicted to collide with the V-UE. The collision prediction may be determined based on information included in the message, visual measurements, radar measurements, or any combination thereof. If the V-UE is on a collision course with the P-UE, the V-UE generates a collision warning message using an identifier of the P-UE and sends the collision warning message on a sidelink channel. The P-UE may receive the collision warning message on the sidelink channel and present an alert (e.g., on a display of the P-UE, via vibration, or using an audio prompt) if the collision warning message carries an identifier of the P-UE. The alert may notify a pedestrian of the predicted collision with the V-UE so that the pedestrian may take action to avoid the collision. If the collision warning message does not include an identifier of the P-UE, the P-UE may discard the collision warning message.

[0092] Figure 2 An example of a V2P wireless communication system 200 supporting a sidelink-based V2P system according to aspects of the present disclosure is shown. In some examples, the V2P wireless communication system 200 can implement aspects of the wireless communication system 100. The V2P wireless communication system 200 can include multiple UEs 115, which can be reference Figure 1 Examples of corresponding devices described. For example, UE 115-a can be a V-UE, and each of UE 115-b, UE 115-c, and UE 115-d can be an example of a P-UE (e.g., a UE 115 carried by a pedestrian). In some examples, the V2P wireless communication system 200 can implement aspects of the wireless communication system 100. For example, the UE 115 in the V2P wireless communication system 200 can address road safety, and more specifically, improve pedestrian safety through direct communication between UEs 115 in the V2P wireless communication system 200 by exchanging information (e.g., V2P messages 205 and P2V messages 210) via the PC5 interface 215.

[0093] In some examples, in order to experience these advantages (e.g., road safety, pedestrian safety), the UE 115 in the V2P wireless communication system 200 can support improvements in UE 115 power usage (e.g., minimizing power consumption) and other advantages. In order for the UE 115 to experience advantages such as power improvements, the UE 115 in some examples can implement techniques that provide improved PC5 power operation for the UE 115. For example, a P-UE (e.g., UE 115-b, UE 115-c, UE 115-d) can broadcast messages on the PC5 interface 215 (e.g., a sidelink channel), which can be received at a V-UE (e.g., UE 115-a) as part of a vehicle-pedestrian collision prediction technique. The P-UE message can include the movement data of the P-UE, the location of the P-UE, and an identifier of the P-UE. The V-UE can receive the P-UE message and determine whether the P-UE and the V-UE are predicted to collide. If the P-UE and V-UE are predicted to collide, the V-UE may send a collision warning message to the P-UE, which may prompt an alarm at the P-UE. This gives the pedestrian a warning so that the pedestrian can avoid colliding with the V-UE. Figure 3An exemplary sidelink channel communication exchange for vehicle-to-pedestrian collision detection and prevention is further described in more detail. In some cases, a vehicle-to-pedestrian resource pool for a sidelink channel may be configured for sending one or more collision warning messages by a V-UE, and a P-UE may monitor the vehicle-to-pedestrian resource pool for collision warning messages. For example, base station 105 may configure a vehicle-to-pedestrian resource pool for use by a V-UE and one or more P-UEs. Similarly, base station 105 may configure a pedestrian-to-vehicle resource pool for pedestrians to send their identity, location, intent, and sensor information to a vehicle.

[0094] Figure 3 An example of a sidelink channel communication exchange 300 supporting a sidelink-based V2P system in accordance with aspects of the present disclosure is shown. In some examples, the sidelink channel communication exchange 300 can implement aspects of the wireless communication system 100.

[0095] In general, the sidelink channel communication exchange 300 describes communication between a pedestrian device 305 and a vehicle 310 on a sidelink between the pedestrian device 305 and the vehicle 310. The pedestrian device 305 may be as described in reference Figure 2 115. In some cases, pedestrian device 305 may refer to a device (such as UE 115) owned, operated, or carried by a pedestrian (e.g., a user), or in close proximity to a pedestrian (e.g., a user). For example, pedestrian device 305 may refer to a UE 115 or mobile device held by a person, in a person's pocket or backpack, etc. Vehicle 310 may refer to an autonomous or self-driving vehicle, a human-operated vehicle, or a vehicle that includes aspects of both. For example, vehicle 310 may include a UE 115 as described above. Figure 2 Various aspects of the UE 115-a or V-UE 115 described.

[0096] The sidelink channel may be configured for direct or indirect communication between the pedestrian device 305 and the vehicle 310. For example, in some cases, signaling may be communicated directly between the pedestrian device 305 and the vehicle 310. Additionally or alternatively, signaling may be communicated between the pedestrian device 305 and the vehicle 310 via a relay point such as the base station 105. The sidelink channel may be as described in reference to Figure 2 An example of the PC5 interface 215 is shown.

[0097] In some cases, the pedestrian device 305 can be configured with a resource allocation for a sidelink channel for pedestrian-to-vehicle communications. For example, the pedestrian device 305 can be configured with a resource allocation so that the pedestrian device 305 can power the sidelink communication component during the resource allocation and, in some cases, reduce the power to the sidelink communication component between resource allocations. Configuring the sidelink resources can improve power conservation at the pedestrian device 305 because the pedestrian device may not have to maintain power to the sidelink circuit to monitor for sidelink messages with warnings. Instead, the pedestrian device can power the sidelink circuit for the sidelink resource allocation.

[0098] The pedestrian device 305 and the vehicle 310 may each store an application 315. In some cases, the application 315 may run as a background process in each device. In some examples, the application 315 may generate packets that are sent between devices. For example, the application 315-a at the pedestrian device 305 may include a pedestrian classification component 320 and a pseudo identifier (ID) generation component 325. At 330, the application 315-a may prompt the pedestrian device 305 to send a P-UE packet 350 via a sidelink channel. The P-UE packet 350 may include, for example, an identifier of the pedestrian device 305, a location 360 of the pedestrian device 305, an indicator 365 (e.g., a track) of the pedestrian's intent, or any combination thereof.

[0099] In some examples, the P-UE packet 350 may include a pseudo ID 355 of the pedestrian device 305 instead of an actual identifier of the pedestrian device 305. The pseudo ID may be an identifier generated by the P-UE 115 instead of an identifier assigned to the P-UE 115 by the base station 105, the wireless communication system 100, a manufacturer, etc. In some examples, using the pseudo ID 355 may be more secure for the pedestrian device 305 than using an actual identifier (e.g., RNTI, etc.). Additionally or alternatively, the P-UE packet 350 may include or be based on an actual identifier of the pedestrian device 305. The pseudo ID 355 may be generated by a pseudo ID generation component 325 of the application 315-a.

[0100] Position 360 may indicate the location of pedestrian device 305. For example, position 360 may be a global positioning system (GPS) value (e.g., GPS coordinates) or some other global navigation satellite system (GNSS) positioning information. In some cases, position 360 may be indicated as a relative position or based on proximity.

[0101] The intention indicator 365 of the pedestrian device 305 can be determined based on one or more sensors of the pedestrian device 305. For example, the pedestrian device 305 can use different sensors to determine the characteristics of the pedestrian's movement, such as the pedestrian's gait, speed, direction of movement, limb movement (e.g., limb swing), etc. The pedestrian device 305 can then parameterize these characteristics and sensor readings into the intention of the pedestrian device 305. For example, based on the pedestrian's limb movement, speed, and gait, the pedestrian device 305 can determine that the pedestrian is running. In addition, based on the pedestrian's direction of movement, the pedestrian device 305 can determine its trajectory, such as, for example, the pedestrian is running towards the street or towards a vehicle (e.g., vehicle 310).

[0102] Pedestrian device 305 may broadcast P-UE packets 350, which may be received by nearby vehicles. In some cases, the broadcast may be periodic. For example, the broadcast may be unconditionally periodic, or the broadcast may be specified to be sent when the UE is operating in a pedestrian mode (such as walking, biking, running, etc.). Alternatively, in some examples, pedestrian device 305 may detect an event that triggers the generation of P-UE packets 350, the broadcast, or both.

[0103] For example, the triggering event may be based on a change in the pedestrian's cadence or gait, a pedestrian approaching an intersection or street, a pedestrian approaching a vehicle, etc. The pedestrian device 305 may determine the pedestrian's travel pattern and determine whether the pedestrian is performing any modes of interest. For example, walking, running, or bicycling may be possible modes of interest. In some cases, driving a vehicle or being a passenger in a vehicle may not be considered a mode of interest because vehicle-to-vehicle communications may implement their own collision detection processes.

[0104] If the pedestrian device 305 is executing any mode of interest, the application 315-a (e.g., by the pseudo ID generation component 325) can assign a pseudo ID 355 to the P-UE. The application 315-a can then create a P-UE packet 350 that includes the pseudo ID 355 as the source ID of the packet and a destination ID indicating that the P-UE packet 350 is broadcast (e.g., and does not have a specific, intended destination or receiving device). The application 315-a can also include other content in the P-UE packet 350, such as a location 360 (e.g., GPS or GNSS coordinates) and an intent indicator 365 (e.g., trajectory data) to convey the determined pedestrian intent.

[0105] Once the application 315-a generates the P-UE packet 350, the application packet at the pedestrian device 305 may be provided to the V2X layer 380 at the pedestrian device 305. For example, the P-UE packet 350 may be provided to the V2X layer 380-a. The V2X layer 380-a may process the P-UE packet 350 and pass it to the protocol stack 385 of the pedestrian device 305 for processing. After the protocol stack 385-a processes the P-UE packet 350, the packet may be sent in a broadcast transmission on the sidelink channel.

[0106] Vehicles in the vicinity of pedestrian device 305 may receive broadcasted P-UE packet 350. For example, vehicle 310 may receive P-UE packet 350 from pedestrian device 305, which includes pseudo ID 355, location 360, and intent indicator 365. In some examples, vehicle 310 may receive application packets from each of a plurality of pedestrian devices, where each application packet may include a corresponding pseudo ID, location, and intent indicator.

[0107] The vehicle 310 may determine whether the pedestrian device 305 is on a collision course with the vehicle 310. For example, the vehicle 310 may determine whether the pedestrian device 305 and the vehicle 310 are on a collision course based on the location 360 and the intent indicator 365 in the P-UE packet 350. In some cases, the vehicle 310 may run a collision detection algorithm based on the trajectory of the vehicle 310 and the trajectory of the pedestrian device 305. In some cases, the vehicle 310 may determine whether there is a possibility of a collision based on visual measurements, radar measurements, etc. For example, using sensors on the vehicle 310, the vehicle 310 may obtain a more accurate reading of the location of the pedestrian or pedestrian device 305, which the vehicle 310 may use to estimate the possibility of a collision. The vehicle 310 may similarly perform collision detection for any other pedestrian device from which the vehicle 310 receives a P-UE packet.

[0108] If the vehicle 310 determines that the vehicle 310 and the pedestrian device 305 are on a collision course, the vehicle 310 may generate a pedestrian warning at 345. The vehicle 310 may determine the source of the pseudo ID 355 of the P-UE to be paged and generate a V-UE packet 370, which includes the pseudo ID 355 of the pedestrian device 305 and a warning indicator 375. In some cases, the pseudo ID 355 may be a destination ID of the V-UE packet 370. In some cases, the V-UE packet 370 may include an identifier of the vehicle 310 (such as a pseudo V-UE identifier). The warning indicator 375 may include a warning sign that a collision may occur between the vehicle 310 and the pedestrian device 305.

[0109] The vehicle 310 may send a V-UE packet 370 to the V2X layer 380-b, which may process the packet. The V-UE packet 370 may then be sent to the protocol stack 385-b, where it is processed and sent to the pedestrian device 305 via the sidelink channel. In some cases, the V-UE packet 370 may be broadcast, and in some cases, the V-UE packet 370 may be sent directionally to the pedestrian device 305.

[0110] The pedestrian device 305 may receive the V-UE packet 370 from the vehicle 310. For example, a lower layer at the pedestrian device 305 may receive the V-UE packet 370 and forward the packet to a higher layer. The application layer at the pedestrian device 305 may check whether the packet is intended for the pedestrian device 305, for example, by comparing the pseudo ID 355 in the destination field of the V-UE packet 370 with the pseudo ID of the pedestrian device 305. If the packet is not intended for the pedestrian device 305 (e.g., the pseudo ID 355 in the destination field of the V-UE packet 370 does not match the pseudo ID of the pedestrian device 305), the application 315-a may discard the packet. If the packet is intended for the pedestrian device 305 (e.g., the pseudo ID 355 in the destination field of the V-UE packet 370 matches the pseudo ID of the pedestrian device 305), the application 315-a and the pedestrian device 305 may respond to the collision warning message.

[0111] For example, pedestrian warning device 340 can trigger an alarm that can notify the user about a possible collision. For example, the alarm can cause vibration, noise, visual prompts, etc. at pedestrian device 305. In some cases, the alarm may be similar to a public warning message. The user of pedestrian device 305 can observe the alarm and take actions to avoid the collision route. In some cases, vehicle 310 can also take actions to avoid the collision route. For example, vehicle 310 can adjust its speed or trajectory to avoid colliding with pedestrian device 305.

[0112] In some cases, collision detection may be performed at the vehicle 310 rather than the pedestrian device 305 to preserve battery life at the pedestrian device 305. For example, the vehicle 310 may typically have a longer battery life (e.g., due to the use of an alternator, a larger battery, etc.). Frequent monitoring and calculation of collision detections in a V2P system or a general V2X system may result in significant battery drain. Therefore, the majority of the collision detection process may be performed at the vehicle 310 rather than draining the battery of the pedestrian device 305, which is more limited. This may result in a relatively substantial increase in battery life at the pedestrian device 305 while still providing safety features for the user of the pedestrian device 305.

[0113] Figure 4 An example of a process flow 400 for supporting a sidelink-based V2P system according to aspects of the present disclosure is shown. In some examples, the process flow 400 can implement aspects of the wireless communication system 100. The process flow 400 can include a UE 115-e and a UE 115-f. The UE 115-e can be a pedestrian UE or a pedestrian device (such as a UE 115-f). Figure 2 115 - b, UE 115 - c, and UE 115 - d) described above. UE 115 - f may be a vehicle UE (such as a vehicle UE described above). Figure 2 An example of UE 115-a) is described.

[0114] At 405, UE 115-e and UE 115-f may establish a sidelink channel for V2P communication between the devices. For example, at 405-a, UE 115-e may receive control signaling indicating resource allocation for the sidelink channel for pedestrian-to-vehicle communication. At 405-b, UE 115-f may receive control signaling indicating resource allocation for V2P communication. In some cases, control signaling may be exchanged between UE 115-e and UE 115-f. Additionally or alternatively, the control signaling may come from another device (such as base station 105).

[0115] At 410, UE 115-e may monitor at least one sensor of UE 115-e. UE 115-e may determine movement parameters based on the monitoring. In some cases, the movement parameters may include gait parameters, speed parameters, direction parameters, limb movement parameters, or any combination thereof.

[0116] At 415, the UE 115-e may send a message including an identifier of the UE 115-e within the resource allocation of the sidelink channel based on the movement data of the UE 115-e being classified as pedestrian movement. The UE 115-e may classify the movement data as pedestrian movement based on the movement data corresponding to a pedestrian movement profile from a set of different movement profiles. For example, the pedestrian parameters determined at 410 may indicate that the pedestrian has a pedestrian movement profile corresponding to walking, bicycling, running, etc., as opposed to driving a car or riding as a passenger in a vehicle, which may be other examples of a movement profile.

[0117] UE 115-f may receive a message including an identifier of UE 115-e and location data of UE 115-e within a resource allocation for a sidelink channel. In some cases, UE 115-f may run a collision detection algorithm to predict whether UE 115-e and UE 115-f are on a path to collide or on a collision course. In some cases, the message may include trajectory data of UE 115-e, where a collision is predicted based on the trajectory data.

[0118] At 420, UE 115-e may monitor the sidelink channel for a collision warning message including an identifier of UE 115-e from the vehicle UE based on sending the message. At 425, UE 115-f may send a collision warning message including an identifier of UE 115-e via the sidelink channel based on a predicted collision with UE 115-e using the location data. In this example, UE 115-f may predict that UE 115-e and UE 115-f are on a path to collide, so UE 115-f may send a collision warning message with the identifier of UE 115-e.

[0119] At 430, UE 115-e may determine whether the collision warning message is for UE 115-e or for another device. For example, if UE 115-e receives a collision warning message (e.g., sent at 425) including an identifier of UE 115-e, UE 115-e may present an alarm based on receiving the collision warning message. The alarm may be, for example, an audible alarm, a display alarm (e.g., on a display of UE 115-e), or both. Alternatively, in some cases, UE 115-e may receive a collision warning message, and the collision warning message may include an identifier of another UE 115 different from UE 115-e. If the collision warning message includes an identifier of a different UE 115, UE 115-e may discard the collision warning message. In some cases, UE 115-f may implement some pedestrian avoidance techniques. For example, UE 115-f may change the speed of a vehicle including a vehicle UE, the trajectory of the vehicle, or both based on the prediction.

[0120] Figure 5 A block diagram 500 of a device 505 supporting a sidelink-based V2P system according to aspects of the present disclosure is shown. The device 505 may be an example of aspects of a UE 115 as described herein. The device 505 may include a receiver 510, a communication manager 515, and a transmitter 520. The device 505 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0121] The receiver 510 may receive information associated with various information channels (e.g., control channels, data channels, and information related to a sidelink-based V2P system, etc.), such as packets, user data, or control information. The information may be passed to other components of the device 505. The receiver 510 may be a reference Figure 8 Examples of aspects of the described transceiver 820. The receiver 510 may utilize a single antenna or a collection of antennas.

[0122] The communication manager 515 can receive control signaling indicating resource allocation of a sidelink channel for pedestrian-to-vehicle communication; based on the UE's movement data being classified as a pedestrian, send a message including an identifier of the UE within the resource allocation of the sidelink; and based on sending the message, monitor the sidelink channel for a collision warning message including the UE's identifier from the vehicle UE.

[0123] The communication manager 515 may also receive control signaling indicating resource allocation of a sidelink channel for V2P communication; receive a message including an identifier of a first UE and location data of the first UE within the resource allocation for the sidelink channel; and send a collision warning message including an identifier of the first UE via the sidelink channel based on a collision predicted with the first UE using the location data. The communication manager 515 may be an example of aspects of the communication manager 810 described herein.

[0124] The communication manager 515 or its subcomponents may be implemented in hardware, in code executed by a processor (e.g., software or firmware), or any combination thereof. If implemented in code executed by a processor, the functions of the communication manager 515 or its subcomponents may be performed by a general purpose processor, a DSP, an application specific integrated circuit (ASIC), an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in the present disclosure.

[0125] The communication manager 515 or its subcomponents can be physically located in a variety of locations, including being distributed so that portions of the functionality are implemented by one or more physical components at different physical locations. In some examples, according to various aspects of the present disclosure, the communication manager 515 or its subcomponents can be separate and distinct components. In some examples, according to various aspects of the present disclosure, the communication manager 515 or its subcomponents can be combined with one or more other hardware components, including but not limited to input / output (I / O) components, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof.

[0126] The actions performed by the communication manager 515 described herein may be implemented to achieve one or more potential advantages. An implementation may allow a pedestrian UE 115 to save power and increase battery life by having a vehicle (e.g., V-UE) perform a collision detection process instead of the pedestrian UE 115. Additionally or alternatively, the UE 115 may further reduce the time spent on monitoring collision detection messages by sending a P-UE message only when the UE 115 is detected to have a pedestrian movement profile. For example, when the UE 115 is determined to be a passenger in a vehicle or is operating a vehicle, the UE 115 may not send a message indicating a location, pedestrian intention, and identifier, so the UE 115 may only monitor the sidelink channel to obtain a V-UE message when the UE 115 is identified as having pedestrian movement. Therefore, these technologies may obtain power efficiency while providing road and pedestrian safety.

[0127] Transmitter 520 can transmit signals generated by other components of device 505. In some examples, transmitter 520 can be co-located with receiver 510 in a transceiver module. For example, transmitter 520 can be a reference Figure 8 Examples of aspects of the described transceiver 820. The transmitter 520 may utilize a single antenna or a collection of antennas.

[0128] Figure 6 A block diagram 600 of a device 605 supporting a sidelink-based V2P system according to aspects of the present disclosure is shown. The device 605 may be an example of aspects of the device 505 or UE 115 as described herein. The device 605 may include a receiver 610, a communication manager 615, and a transmitter 620. The device 605 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0129] The receiver 610 may receive information associated with various information channels (e.g., control channels, data channels, and information related to a sidelink-based V2P system, etc.), such as packets, user data, or control information. The information may be passed to other components of the device 605. The receiver 610 may be a reference Figure 8 Examples of aspects of the described transceiver 820. The receiver 610 may utilize a single antenna or a collection of antennas.

[0130] Communications manager 615 may be an example of aspects of communications manager 515 described herein. Communications manager 615 may include sidelink channel configuration component 620, identifier sending component 625, collision warning message monitoring component 630, sidelink channel configuration component 635, identifier receiving component 640, and collision warning message sending component 645. Communications manager 615 may be an example of aspects of communications manager 810 described herein.

[0131] The sidelink channel configuration component 620 can receive control signaling indicating resource allocation of a sidelink channel for pedestrian-to-vehicle communication. The identifier sending component 625 can send a message including an identifier of the UE within the resource allocation of the sidelink channel based on the movement data of the UE being classified as pedestrian movement. The collision warning message monitoring component 630 can monitor the sidelink channel for a collision warning message including the identifier of the UE from the vehicle UE based on sending the message.

[0132] The sidelink channel configuration component 635 can receive control signaling indicating resource allocation of a sidelink channel for V2P communication. The identifier receiving component 640 can receive a message including an identifier of the first UE and location data of the first UE within the resource allocation for the sidelink channel. The collision warning message sending component 645 can send a collision warning message including an identifier of the first UE via the sidelink channel based on a collision predicted with the first UE using the location data.

[0133] Transmitter 650 can transmit signals generated by other components of device 605. In some examples, transmitter 650 can be co-located with receiver 610 in a transceiver module. For example, transmitter 650 can be a reference Figure 8 Examples of aspects of the described transceiver 820. The transmitter 650 may utilize a single antenna or a collection of antennas.

[0134] In some cases, monitoring V-UE messages based on sending P-UE messages can support a processor of UE 115 (e.g., as described in reference Fig. 9 As described above, the control receiver 610, the transmitter 650 or the transceiver 920) effectively manages the V-UE message monitoring opportunity. For example, when the UE 115 has not yet sent a P-UE message, the processor of the UE 115 can turn off some components that monitor the sidelink channel. In addition to maintaining the battery life at the UE 115 due to spending less monitoring time, these techniques can also increase the life of the monitoring components.

[0135] Figure 7A block diagram 700 of a communication manager 705 supporting a sidelink-based V2P system according to aspects of the present disclosure is shown. The communication manager 705 can be an example of aspects of the communication manager 515, the communication manager 615, or the communication manager 810 described herein. The communication manager 705 can include a sidelink channel configuration component 710, an identifier transmission component 715, a collision warning message monitoring component 720, an alert presentation component 725, a pedestrian movement data component 730, a sidelink channel configuration component 735, an identifier reception component 740, a collision warning message transmission component 745, a vehicle adjustment component 750, and an alert generation component 755. Each of these modules can communicate with each other directly or indirectly (e.g., via one or more buses).

[0136] The sidelink channel configuration component 710 can receive control signaling indicating resource allocation of a sidelink channel for pedestrian-to-vehicle communication. The identifier sending component 715 can send a message including an identifier of the UE within the resource allocation of the sidelink channel based on the UE's movement data being classified as pedestrian movement. In some examples, the identifier sending component 715 can send a message including the UE's location data, the UE's trajectory data, or both. In some examples, the identifier sending component 715 can send a message including an identifier that is a pseudo-identifier of the UE.

[0137] In some examples, identifier sending component 715 can send a message including a packet including a pseudo identifier of the UE as a source identifier of the packet and a broadcast identifier as a destination identifier of the packet. In some examples, identifier sending component 715 can send the message via a sidelink channel using a sidelink interface of the UE.

[0138] The collision warning message monitoring component 720 can monitor the sidelink channel for a collision warning message including an identifier of the UE from the vehicle UE based on sending the message. In some examples, the collision warning message monitoring component 720 can monitor a V2P resource pool for the sidelink channel for a collision warning message.

[0139] In some examples, collision warning message monitoring component 720 can receive a collision warning message including an identifier of a second UE different from the UE. In some examples, collision warning message monitoring component 720 can discard the collision warning message.

[0140] The alert presentation component 725 may receive a collision warning message including an identifier of the UE. In some examples, the alert presentation component 725 may present an alert based on receiving the collision warning message. In some examples, the alert presentation component 725 may determine that a second identifier included as a destination identifier in the collision warning message matches the identifier of the UE. In some cases, the alert is an audible alert, a display alert, or both.

[0141] Pedestrian movement data component 730 can classify the movement data as pedestrian movement based on the movement data corresponding to a pedestrian movement profile in a set of different movement profiles. In some examples, pedestrian movement data component 730 can monitor at least one sensor of the UE.

[0142] In some examples, pedestrian movement data component 730 can determine movement parameters based on the monitoring, wherein the movement data of the UE is classified as pedestrian movement based on the movement parameters. In some cases, the movement parameters include gait parameters, speed parameters, direction parameters, limb movement parameters, or any combination thereof.

[0143] Sidelink channel configuring component 735 may receive control signaling indicating resource allocation for a sidelink channel for V2P communications.

[0144] Identifier receiving component 740 can receive a message including an identifier of a first UE and location data of the first UE within a resource allocation for a sidelink channel. In some cases, the message includes trajectory data of the first UE, wherein a collision is predicted based on the trajectory data.

[0145] In some examples, the identifier receiving component 740 can receive a message including trajectory data of the first UE, movement data of the first UE, or both, where a collision is predicted based on gait parameters, speed parameters, direction parameters, limb movement parameters, or any combination thereof.

[0146] In some examples, the identifier receiving component 740 may receive a second message including an identifier of the second UE and location data of the second UE. In some examples, the identifier receiving component 740 may predict that the vehicle UE is not on a collision path with the second UE based on the second message. In some examples, the identifier receiving component 740 may determine not to send a second collision warning message including an identifier of the second UE based on the prediction.

[0147] The collision warning message sending component 745 can send a collision warning message including an identifier of the first UE via a sidelink channel based on the collision predicted with the first UE using the position data. In some examples, the collision warning message sending component 745 can send the collision warning message including the identifier of the first UE as a destination identifier in the collision warning message. In some examples, the collision warning message sending component 745 can send the collision warning message via a sidelink channel using a sidelink interface of the UE.

[0148] The vehicle adjustment component 750 can change the speed of the vehicle including the vehicle UE, the trajectory of the vehicle, or both based on the prediction. The alert generation component 755 can generate an alert based on the prediction.

[0149] Figure 8 A diagram of a system 800 including a device 805 supporting a sidelink-based V2P system according to aspects of the present disclosure is shown. The device 805 may be an example of a device 505, a device 605, or a UE 115 as described herein or include a component of the device 505, a device 605, or a UE 115. The device 805 may include components for two-way voice and data communications, including components for sending and receiving communications, including a communication manager 810, an I / O controller 815, a transceiver 820, an antenna 825, a memory 830, and a processor 840. These components may communicate electronically via one or more buses (e.g., a bus 845).

[0150] The communication manager 810 may receive control signaling indicating resource allocation of a sidelink channel for pedestrian-to-vehicle communication; based on the UE's movement data being classified as pedestrian movement, send a message including an identifier of the UE within the resource allocation of the sidelink channel; and based on sending the message, monitor the sidelink channel for a collision warning message including the identifier of the UE from the vehicle UE. The communication manager 810 may also receive control signaling indicating resource allocation of a sidelink channel for V2P communication; receive a message including an identifier of a first UE and location data of the first UE within the resource allocation for the sidelink channel; and based on a collision with the first UE predicted using the location data, send a collision warning message including the identifier of the first UE via the sidelink channel.

[0151] I / O controller 815 can manage input and output signals for device 805. I / O controller 815 can also manage peripheral devices that are not integrated into device 805. In some cases, I / O controller 815 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 815 can utilize an operating system, such as Or another well-known operating system. In other cases, I / O controller 815 can represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, I / O controller 815 can be implemented as part of a processor. In some cases, a user can interact with device 805 via I / O controller 815 or via hardware components controlled by I / O controller 815.

[0152] As described above, the transceiver 820 can communicate bidirectionally via one or more antennas, wired or wireless links. For example, the transceiver 820 can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. The transceiver 820 can also include a modem to modulate packets and provide the modulated packets to an antenna for transmission, and demodulate packets received from an antenna.

[0153] In some cases, a wireless device may include a single antenna 825. However, in some cases, a device may have more than one antenna 825, which may be capable of sending or receiving multiple wireless transmissions concurrently.

[0154] The memory 830 may include RAM and ROM. The memory 830 may store computer-readable, computer-executable code 835 including instructions that, when executed, cause the processor to perform the various functions described herein. In some cases, the memory 830 may also contain, among other things, a BIOS that may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0155] Processor 840 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, processor 840 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into processor 840. Processor 840 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 830) to cause device 805 to perform various functions (e.g., functions or tasks of a V2P system based on a sidelink).

[0156] The code 835 may include instructions for implementing various aspects of the present disclosure, including instructions for supporting wireless communications. The code 835 may be stored in a non-transitory computer-readable medium such as a system memory or other type of memory. In some cases, the code 835 may not be directly executable by the processor 840, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein.

[0157] Fig. 9 A flow chart illustrating a method 900 for supporting a sidelink-based V2P system according to aspects of the present disclosure is shown. The operations of the method 900 may be implemented by a UE 115 or a component thereof as described herein. For example, the operations of the method 900 may be implemented by a UE 115 or a component thereof as described herein. Figures 5 to 8 The communication manager described in the embodiment of the present invention performs. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the functions described below.

[0158] At 905, the UE may receive control signaling indicating resource allocation for a sidelink channel for pedestrian-to-vehicle communication. The operations of 905 may be performed according to the methods described herein. In some examples, aspects of the operations of 905 may be performed as described in reference to Figures 5 to 8 The sidelink channel configuration component described is performed.

[0159] At 910, the UE may send a message including an identifier of the UE within a resource allocation of a sidelink channel based on the UE's movement data being classified as pedestrian movement. The operations of 910 may be performed according to the methods described herein. In some examples, aspects of the operations of 910 may be performed as described in reference to Figures 5 to 8 An identifier describing the component being sent.

[0160] At 915, the UE may monitor the sidelink channel based on sending the message to obtain a collision warning message from the vehicle UE including an identifier of the UE. The operation of 915 may be performed according to the method described herein. In some examples, various aspects of the operation of 915 may be performed as described in reference to Figures 5 to 8 Describes the collision warning message monitoring component implementation.

[0161] Fig.10 A flow chart illustrating a method 1000 for supporting a sidelink-based V2P system according to aspects of the present disclosure is shown. The operations of the method 1000 may be implemented by a UE 115 or a component thereof as described herein. In some examples, the operations of the method 1000 may be implemented by a UE 115 or a component thereof as described herein. Figures 5 to 8 The communication manager described in the embodiment of the present invention performs. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the functions described below.

[0162] At 1005, the UE may receive control signaling indicating resource allocation for a sidelink channel for pedestrian-to-vehicle communication. The operations of 1005 may be performed according to the methods described herein. In some examples, aspects of the operations of 1005 may be performed as described in reference to Figures 5 to 8The sidelink channel configuration component described is performed.

[0163] At 1010, the UE may send a message including an identifier of the UE within a resource allocation of a sidelink channel based on the UE's movement data being classified as pedestrian movement. The operations of 1010 may be performed according to the methods described herein. In some examples, aspects of the operations of 1010 may be performed as described in reference to Figures 5 to 8 An identifier describing the component being sent.

[0164] At 1015, the UE may monitor the sidelink channel based on sending the message to obtain a collision warning message from the vehicle UE including an identifier of the UE. The operation of 1015 may be performed according to the method described herein. In some examples, various aspects of the operation of 1015 may be performed as described in reference to Figures 5 to 8 Describes the collision warning message monitoring component implementation.

[0165] At 1020, the UE may receive a collision warning message including an identifier of the UE. The operations of 1020 may be performed according to the methods described herein. In some examples, aspects of the operations of 1020 may be performed as described in reference to Figures 5 to 8 Describes the implementation of the alert presentation component.

[0166] At 1025, the UE may present an alert based on receiving the collision warning message. The operations of 1025 may be performed according to the methods described herein. In some examples, aspects of the operations of 1025 may be performed as described in reference to Figures 5 to 8 Describes the implementation of the alert presentation component.

[0167] Fig.11 A flow chart illustrating a method 1100 for supporting a sidelink-based V2P system according to aspects of the present disclosure is shown. The operations of the method 1100 may be implemented by a UE 115 or a component thereof as described herein. For example, the operations of the method 1100 may be implemented by a UE 115 or a component thereof as described herein. Figures 5 to 8 The communication manager described in the embodiment of the present invention performs. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the functions described below.

[0168] At 1105, the UE may receive control signaling indicating resource allocation for a sidelink channel for V2P communication. The operations of 1105 may be performed according to the methods described herein. In some examples, aspects of the operations of 1105 may be performed as described in reference to Figures 5 to 8 The sidelink channel configuration component described is performed.

[0169] At 1110, the UE may receive a message including an identifier of the first UE and location data of the first UE within a resource allocation for a sidelink channel. The operations of 1110 may be performed according to the methods described herein. In some examples, aspects of the operations of 1110 may be performed as described in reference to Figures 5 to 8 An identifier describing the receiving component implementation.

[0170] At 1115, the UE may send a collision warning message including an identifier of the first UE via a sidelink channel based on the collision predicted with the first UE using the location data. The operations of 1115 may be performed according to the methods described herein. In some examples, aspects of the operations of 1115 may be performed as described in reference to Figures 5 to 8 Describes the collision warning message sending component implementation.

[0171] Fig.12 A flow chart illustrating a method 1200 for supporting a sidelink-based V2P system according to aspects of the present disclosure is shown. The operations of the method 1200 may be implemented by a UE 115 or a component thereof as described herein. For example, the operations of the method 1200 may be implemented by a UE 115 or a component thereof as described herein. Figures 5 to 8 The communication manager described in the embodiment of the present invention performs. In some examples, the UE may execute an instruction set to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform various aspects of the functions described below.

[0172] At 1205, the UE may receive control signaling indicating resource allocation for a sidelink channel for V2P communication. The operations of 1205 may be performed according to the methods described herein. In some examples, aspects of the operations of 1205 may be performed as described in reference to Figures 5 to 8 The sidelink channel configuration component described is performed.

[0173] At 1210, the UE may receive a message including an identifier of the first UE and location data of the first UE within a resource allocation for a sidelink channel. The operations of 1210 may be performed according to the methods described herein. In some examples, aspects of the operations of 1210 may be performed as described in reference to Figures 5 to 8 An identifier describing the receiving component implementation.

[0174] At 1215, the UE may send a collision warning message including an identifier of the first UE via a sidelink channel based on the collision predicted with the first UE using the location data. The operations of 1215 may be performed according to the methods described herein. In some examples, aspects of the operations of 1215 may be performed as described in reference to Figures 5 to 8 Describes the collision warning message sending component implementation.

[0175] At 1220, the UE may change the speed of the vehicle, the trajectory of the vehicle, or both, including the vehicle UE based on the prediction. The operations of 1220 may be performed according to the methods described herein. In some examples, aspects of the operations of 1220 may be performed as described in reference to Figures 5 to 8 The vehicle tuning components described are performed.

[0176] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified, and other implementations are possible. Furthermore, aspects from two or more methods may be combined.

[0177] Although aspects of LTE, LTE-A, LTE-APro, or NR systems may be described for purposes of example, and LTE, LTE-A, LTE-APro, or NR terminology may be used in much of the description, the techniques described herein may be applicable beyond LTE, LTE-A, LTE-APro, or NR networks. For example, the techniques described may be applicable to various other wireless communication systems, such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0178] The information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips referred to throughout the specification may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0179] The various illustrative blocks and modules described in conjunction with the disclosure herein may be implemented or executed with a general purpose processor, DSP, ASIC, CPU, 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 may be a microprocessor, but in an alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

[0180] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or sent via a computer-readable medium as one or more instructions or codes. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or a combination of any of these. Features that implement the functions may also be physically located in various locations, including being distributed so that portions of the functions are implemented in different physical locations.

[0181] Computer-readable media include both non-transitory computer storage media and communication media, and communication media include any media that facilitates the transfer of computer programs from one place to another.Non-transitory storage media can be any available media that can be accessed by a general or special computer.As an example and not limitation, non-transitory computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), flash memory, compact disc (CD) ROM or other optical disc storage, disk storage or other magnetic storage devices, or can be used to carry or store required program code components in the form of instructions or data structures and can be accessed by a general or special computer or a general or special processor.Any other non-transitory medium.Moreover, any connection is properly referred to as computer-readable media.For example, if software is sent from a website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technologies such as infrared, radio and microwaves, then coaxial cable, fiber optic cable, twisted pair, DSL or wireless technologies such as infrared, radio and microwaves are included in the definition of computer-readable media. As used herein, disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0182] As used herein, including in the claims, "or" used in a list of items (e.g., a list of items terminated by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, so that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Also, as used herein, the phrase "based on" should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."

[0183] In the drawings, similar components or features may have the same reference number. In addition, various components of the same type may be distinguished by following the reference number with a dash and a second reference that distinguishes between similar components. If only the first reference number is used in the specification, the specification applies to any of the similar components having the same first reference number, regardless of the second or other subsequent reference numbers.

[0184] The description set forth herein in conjunction with the accompanying drawings describes example configurations and does not represent all examples that may be implemented or within the scope of the claims. The term "example" as used herein means "used as an example, instance, or illustration," rather than "preferred" or "superior to other examples." For the purpose of providing an understanding of the described technology, the detailed description includes specific details. However, these technologies may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0185] The description herein is provided to enable those skilled in the art to make or use the present disclosure. Various modifications to the present 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 scope of the present disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but will be given the broadest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication by a user equipment (UE), comprising: receiving control signaling indicating resource allocation of a sidelink channel for pedestrian-to-vehicle communications; transmitting, within the resource allocation of the sidelink channel, a message including an identifier of the UE, wherein transmitting the message is classified as pedestrian movement based at least in part on movement data of the UE, and wherein transmitting the message includes transmitting the message including location data of the UE, an indicator of intent of the UE, or both; as well as Based at least in part on sending the message, the sidelink channel is monitored for a collision warning message from a vehicle UE that includes the identifier of the UE.

2. The method according to claim 1, wherein: Monitoring the sidelink channel comprises: A vehicle-to-pedestrian resource pool for the sidelink channel is monitored for the collision warning message.

3. The method according to claim 1, wherein: Sending the message includes: The message including the identifier is sent, the identifier being a pseudo identifier of the UE.

4. The method according to claim 1, wherein: Sending the message includes: The message is sent including a packet including the pseudo identifier of the UE as a source identifier of the packet and a broadcast identifier as a destination identifier of the packet.

5. The method according to claim 1, further comprising: receiving the collision warning message including an identifier of a second UE different from the UE; as well as The collision warning message is discarded.

6. The method according to claim 1, further comprising: receiving the collision warning message including the identifier of the UE; as well as An alert is presented based at least in part on receiving the collision warning message.

7. The method according to claim 6, wherein: The alarm is an audible alarm, a display alarm, or both.

8. The method according to claim 6, further comprising: It is determined that a second identifier included as a destination identifier in the collision warning message matches the identifier of the UE.

9. The method according to claim 1, further comprising: The movement data is classified as pedestrian movement based at least in part on the movement data corresponding to a pedestrian movement profile of a plurality of different movement profiles.

10. The method according to claim 1, further comprising: monitoring at least one sensor of the UE; as well as A movement parameter is determined based at least in part on the monitoring, wherein the movement data of the UE is classified as the pedestrian movement based at least in part on the movement parameter.

11. The method according to claim 10, wherein: The movement parameters are gait parameters, speed parameters, direction parameters, limb movement parameters or any combination thereof.

12. The method according to claim 1, wherein: Sending the message includes: The message is sent via the sidelink channel using a sidelink interface of the UE.

13. A method for wireless communication by a vehicle user equipment (UE), comprising: receiving control signaling indicating resource allocation of a sidelink channel for vehicle-to-pedestrian communications; receiving a message from a first UE within the resource allocation for the sidelink channel, the message including an identifier of the first UE and location data of the first UE, wherein receiving the message includes receiving the message including an indicator of intent of the first UE, wherein the collision is predicted based at least in part on the indicator of intent; and Based at least in part on a collision with the first UE predicted using the position data, sending a collision warning message including the identifier of the first UE via the sidelink channel.

14. The method according to claim 13, wherein: Receiving the message includes: The message is received including an indicator of intent of the first UE, movement data of the first UE, or both, wherein the collision is predicted based at least in part on a gait parameter, a speed parameter, a direction parameter, a limb movement parameter, or any combination thereof.

15. The method according to claim 13, wherein: Sending the collision warning message includes: The collision warning message is sent including the identifier of the first UE as a destination identifier in the collision warning message.

16. The method according to claim 13, wherein: Sending the collision warning message includes: The collision warning message is sent via the sidelink channel using the sidelink interface PC5 of the vehicle UE.

17. The method according to claim 13, further comprising: A speed of a vehicle including the vehicle UE, a trajectory of the vehicle, or both is changed based at least in part on the prediction.

18. The method according to claim 13, further comprising: An alert is generated based at least in part on the prediction.

19. The method according to claim 13, further comprising: receiving a second message including an identifier of a second UE and location data of the second UE; predicting that the vehicle UE is not on a collision course with the second UE based at least in part on the second message; as well as A determination is made based at least in part on the prediction not to send a second collision warning message including the identifier of the second UE.

20. An apparatus for wireless communication by a user equipment (UE), comprising: means for receiving control signaling indicating resource allocation of a sidelink channel for pedestrian-to-vehicle communications; means for transmitting, within the resource allocation of the sidelink channel, a message including an identifier of the UE based at least in part on movement data of the UE being classified as pedestrian movement, wherein transmitting the message is based at least in part on the movement data of the UE being classified as pedestrian movement, and wherein the means for transmitting the message further comprises means for transmitting the message including location data of the UE, an indicator of intent of the UE, or both; as well as Means for monitoring the sidelink channel for a collision warning message from a vehicle UE including the identifier of the UE based at least in part on sending the message.

21. The device according to claim 20, wherein: The means for monitoring the sidelink channel further comprises: Means for monitoring a vehicle-to-pedestrian resource pool for said sidelink channel for said collision warning message.

22. The device according to claim 20, wherein: The component for sending the message also includes: means for sending the message including the identifier, the identifier being a pseudo identifier of the UE.

23. The device according to claim 20, wherein: The component for sending the message also includes: Means for sending said message comprising a packet, said packet comprising a pseudo identifier of said UE as a source identifier of said packet and a broadcast identifier as a destination identifier of said packet.

24. The apparatus according to claim 20, further comprising: means for receiving the collision warning message comprising an identifier of a second UE different from the UE; as well as Means for discarding said collision warning message.

25. The apparatus of claim 20, further comprising: means for receiving the collision warning message comprising the identifier of the UE; as well as Means for presenting an alert based at least in part on receiving the collision warning message.

26. An apparatus for wireless communication by a vehicle user equipment (UE), comprising: means for receiving control signaling indicating resource allocation of a sidelink channel for vehicle-to-pedestrian communications; means for receiving, within the resource allocation for the sidelink channel, a message comprising an identifier of a first UE and location data of the first UE, wherein the means for receiving the message further comprises means for receiving the message comprising an indicator of intent of the first UE, wherein the collision is predicted based at least in part on the indicator of intent; as well as Means for sending, via the sidelink channel, a collision warning message including the identifier of the first UE based at least in part on a collision with the first UE predicted using the position data.

Images