Application layer security message with geofencing information

Abstract

Techniques for wireless communication are disclosed. In one aspect, a user equipment (UE) may transmit device-to-device (D2D) communication. The D2D communication may include an application layer message and the application layer message includes one or more data elements related to a geofence of the UE. In one aspect, a user equipment (UE) may receive device-to-device (D2D) communication. The D2D communication may include an application layer message and the application layer message may include one or more data elements related to a geofence of the UE.

Description

[0001] Priority Claim

[0002] This patent application claims priority to U.S. Non - Provisional Application No. 16 / 752,567, entitled "APPLICATION LAYER SAFETY MESSAGE WITH GEO - FENCE INFORMATION", filed on January 24, 2020, which is assigned to the assignee of this application and is hereby incorporated by reference in its entirety.

[0003] Background

[0004] Aspects described herein generally relate to wireless communication systems, and more particularly to determining proximity to a geofence and optionally invoking an action based on that proximity. In some aspects, the geofence may be determined based on information received in device - to - device communication including application layer messages.

[0005] Wireless communication systems have evolved through several generations, including first - generation analog wireless telephone service (1G), second - generation (2G) digital wireless telephone service (including transitional 2.5G and 2.75G networks), third - generation (3G) high - speed data wireless service with Internet capabilities, and fourth - generation (4G) services (e.g., Long Term Evolution (LTE) or WiMax). There are many different types of wireless communication systems in use currently, including cellular and Personal Communication Service (PCS) systems. Examples of known cellular systems include cellular analog Advanced Mobile Phone System (AMPS), and digital cellular systems based on Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Global System for Mobile access (GSM) TDMA variants, etc.

[0006] The fifth - generation (5G) mobile standard (also known as New Radio (NR)) requires higher data transfer speeds, a larger number of connections, better coverage, and other improvements. According to the Next Generation Mobile Networks Alliance, the 5G standard is designed to provide, for example, a data rate of tens of megabits per second to each of thousands of users, and a data rate of 1 gigabit per second to dozens of employees on an office floor. Support for hundreds of thousands of simultaneous connections should be provided to support large - scale sensor deployments. Thus, the spectral efficiency of 5G mobile communication should be significantly improved compared to current 4G standards. In addition, signaling efficiency should be improved and latency should be greatly reduced compared to current standards.

[0007] Existing wireless risk warning systems require always-on broadcasts and application layer message processing, resulting in increased power consumption and additional RF congestion. Risk warnings can be related to vehicle entities and non-vehicle entities. For example, from June 2017 to June 2018, there were 1.33 million collisions between vehicles and deer, caribou, moose, or reindeer in the United States. For example, deer-vehicle collisions alone result in approximately 200 deaths and $1.1 billion in property damage per year, and an additional $3 billion is spent by state and federal governments, insurance companies, and drivers to reduce and manage animal-vehicle collisions.

[0008] Leveraging the increased data rate, reduced latency, and speed-plus-distance-sensitive physical layer (PHY) and media access control layer (MAC) (PHY-MAC) of 5G, vehicle-to-everything (V2X) communication technology is being implemented to support various driving applications, such as wireless communication between vehicles, between vehicles and roadside infrastructure, between vehicles and pedestrians, and so on. Accordingly, it would be beneficial to implement a collision prevention system using V2X communication technology to reduce property and life losses.

[0009] Overview

[0010] This overview identifies some example aspects of the features and is not an exclusive or exhaustive description of the disclosed subject matter. Whether a feature or an aspect is included in this overview or omitted from this overview is not intended to indicate the relative importance of these features. Additional features and aspects are described, and these additional features and aspects will become apparent to those skilled in the art upon reading the following detailed description and viewing the drawings that form a part of the detailed description.

[0011] According to various aspects disclosed herein, at least one aspect includes a method for wireless communication at a first user equipment (UE), the method comprising: receiving device-to-device (D2D) communication including an application layer message from a second user equipment (UE), wherein the application layer message includes one or more data elements related to a geofence of the second UE.

[0012] According to various aspects disclosed herein, at least one aspect includes a method for wireless communication at a user equipment (UE), the method comprising: transmitting device-to-device (D2D) communication, wherein the D2D communication includes an application layer message and wherein the application layer message includes one or more data elements related to a geofence of the UE.

[0013] According to various aspects disclosed herein, at least one aspect includes a first user equipment (UE) that includes: a transceiver; at least one processor coupled to a memory and the transceiver, the at least one processor cooperating with the transceiver and configured to: receive device-to-device (D2D) communication including an application layer message from a second user equipment (UE), wherein the application layer message includes one or more data elements related to a geofence of the second UE.

[0014] According to various aspects disclosed herein, at least one aspect includes a user equipment (UE) that includes: a transceiver; at least one processor coupled to a memory and the transceiver, the at least one processor cooperating with the transceiver and configured to: transmit device-to-device (D2D) communication, wherein the D2D communication includes an application layer message and wherein the application layer message includes one or more data elements related to a geofence of the UE.

[0015] Based on the figures and the detailed description, other objectives and advantages associated with the aspects disclosed herein will be apparent to those skilled in the art. Brief Description of the Drawings

[0017] The accompanying drawings are provided to assist in describing one or more examples of aspects of the disclosed subject matter and are provided only for purposes of illustration of the examples and not limitation thereof:

[0018] Figure 1 An exemplary wireless communication system in accordance with one or more aspects of the present disclosure is illustrated.

[0019] Figure 2A and Figure 2B An example wireless network structure in accordance with various aspects is illustrated.

[0020] Figure 3 An example of a wireless communication device in a wireless communication system in accordance with aspects of the present disclosure is illustrated.

[0021] Figure 4 An example of communication between UEs in accordance with aspects of the present disclosure is illustrated.

[0022] Figure 5 An example communication flow between UEs in accordance with aspects of the present disclosure is illustrated.

[0023] Figure 6 An example interaction between different layers at a transmitting device and a receiving device in accordance with aspects of the present disclosure is illustrated.

[0024] Figure 7 An example interaction between different layers at a transmitting device and a receiving device in accordance with aspects of the present disclosure is illustrated.

[0025] Figure 8 It is a block diagram illustrating various components of an exemplary UE according to at least one aspect of the present disclosure.

[0026] Figure 9 An exemplary proximity device represented as a series of interrelated functional modules according to one aspect of the present disclosure is illustrated.

[0027] Figure 10 Data elements used in D2D messaging according to aspects of the present disclosure are illustrated.

[0028] Figure 11 New messages used in D2D messaging according to aspects of the present disclosure are illustrated.

[0029] Figure 12 Example signaling between two UEs according to aspects of the present disclosure is illustrated.

[0030] Figure 13 Example signaling between two UEs according to aspects of the present disclosure is illustrated.

[0031] Figure 14 Example signaling between two UEs according to aspects of the present disclosure is illustrated.

[0032] Figure 15 An example flowchart of at least one method according to one aspect of the present disclosure is illustrated.

[0033] Figure 16A An example flowchart of at least one method according to one aspect of the present disclosure is illustrated.

[0034] Figure 16B An example flowchart of at least one method according to one aspect of the present disclosure is illustrated.

[0035] Figure 17 An example device represented as a series of interrelated functional modules according to one aspect of the present disclosure is illustrated.

[0036] Detailed description

[0037] Techniques are disclosed for establishing a moving geofence using 5G NR D2D communication as a UE (e.g., a UE installed in a vehicle, a UE installed in an animal (e.g., a tag), a pedestrian UE, etc.) moves. For example, C-V2X communication enables one-to-one (device-to-device) and one-to-many infrastructureless communication as well as infrastructure-mediated communication. The moving geofence can be established by exposing 5G NR embedded controls from the physical layer (PHY) and / or the media access control layer (MAC) (also referred to herein as PHY-MAC embedded controls) to the application layer. This allows for reducing device power consumption by diverting the 5G NR PHY-MAC control message mechanism to enable or disable application layer message processing. Specifically, when no geofence violation is detected, messages can be blocked from going to the application layer, thereby preventing unnecessary message processing at the application layer.

[0038] These and other aspects of the subject matter are provided in the following description of specific examples of the disclosed subject matter and the related drawings. Alternative designs may be made without departing from the scope of the disclosed subject matter. Additionally, well-known elements will not be described in detail or will be omitted so as not to obscure relevant details.

[0039] The term "exemplary" is used herein to mean "serving as an example, instance, or illustration". Any aspect described herein as "exemplary" is not necessarily to be construed as superior or better than other aspects. Likewise, the term "aspect" does not require that all aspects include the discussed feature, advantage, or mode of operation.

[0040] The terms used herein are only descriptive of particular aspects and should not be construed as limiting any aspect disclosed herein. As used herein, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. Those skilled in the art will further understand that the terms "comprises", "has", "includes", and / or "contains", when used herein, specify the presence of the stated feature, integer, step, operation, element, and / or component, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0041] In addition, aspects may be described in terms of sequences of actions performed by elements of, for example, a computing device. Those skilled in the art will recognize that the various actions described herein can be performed by special-purpose circuitry (e.g., an application-specific integrated circuit (ASIC)), by program instructions being executed by one or more processors, or by a combination of the two. Additionally, the sequences of actions described herein can be considered to be fully implemented within any form of non-transitory computer-readable medium storing a corresponding set of computer instructions that, when executed, will cause the associated processor to perform the functionality described herein. Thus, the various aspects described herein can be implemented in several different forms, all of which are contemplated as falling within the scope of the claimed subject matter. Additionally, for each aspect described herein, a corresponding form of any such aspect can be described herein as, for example, "logic configured to perform the described actions" and / or other structural components configured to perform the described actions.

[0042] As used herein, the terms "UE", "vehicle UE (V-UE)", on-board unit (OBU), and "base station" are not intended to be dedicated to or otherwise limited to any particular radio access technology (RAT) unless otherwise specified. In general, a user equipment will be referred to herein as a UE, and thus a UE can be any wireless communication device (e.g., a vehicle on-board computer, a vehicle navigation device, a mobile phone, a router, a tablet computer, a laptop computer, a tracking device, an Internet of Things (IoT) device, etc.) used by a user to communicate over a wireless communication network. A UE can be mobile or can be stationary (e.g., at certain times) and can communicate with a radio access network (RAN). As used herein, the term "UE" can be referred to interchangeably as an "access terminal" or "AT", "client device", "wireless device", "subscriber device", "subscriber terminal", "subscriber station", "user terminal" or UT, "mobile terminal", "mobile station", or variants thereof. A V-UE or OBU can be any wireless communication device within a vehicle, such as a navigation system, an alarm system, a head-up display (HUD), etc. Alternatively, a V-UE can be a portable wireless communication device (e.g., a cellular phone, a tablet computer, etc.) belonging to a driver of a vehicle or a passenger in the vehicle. The term "V-UE" can refer to a wireless communication device in a vehicle or the vehicle itself, depending on the context. In general, a UE can communicate with a core network via a RAN, and through the core network, a UE can connect to an external network (such as the Internet) and to other UEs. Of course, other mechanisms for connecting to the core network and / or the Internet are also possible for a UE, such as via a wired access network, a WiFi network (e.g., based on IEEE 802.11, etc.).

[0043] A base station may operate according to one of several RATs when communicating with a UE, depending on the network in which the base station is deployed, and may alternatively be referred to as an access point (AP), network node, B node, evolved B node (eNB), general B node (gB node, gNB), etc. Additionally, in some systems, the base station may provide only an edge node signaling function, while in other systems, the base station may provide additional control and / or network management functions.

[0044] A UE can be implemented by any of several types of devices, including but not limited to a printed circuit (PC) card, compact flash device, external or internal modem, wireless or wired telephone, smartphone, tablet, tracking device, asset tag, etc. The communication link by which the UE can send signals to the RAN is referred to as an uplink channel (e.g., reverse traffic channel, reverse control channel, access channel, etc.). The communication link by which the RAN can send signals to the UE is referred to as a downlink or forward link channel (e.g., paging channel, control channel, broadcast channel, forward traffic channel, etc.). As used herein, the term traffic channel (TCH) can refer to an uplink / reverse traffic channel or a downlink / forward traffic channel.

[0045] Figure 1 An exemplary wireless communication system 100 in accordance with one or more aspects is illustrated. The wireless communication system 100 (which may also be referred to as a wireless wide area network (WWAN)) may include various base stations 102 and various UEs 104. The base stations 102 may include macro cells (high-power cellular base stations) and / or small cells (low-power cellular base stations). Macro cells may include evolved B nodes (eNBs) (where the wireless communication system 100 corresponds to an LTE network), gB nodes (gNBs) (where the wireless communication system 100 corresponds to a 5G network), and / or combinations thereof, and small cells may include femtocells, picocells, microcells, etc.

[0046] Base stations 102 can jointly form a RAN and interface with an evolved packet core (EPC) or a next-generation core (NGC) via a backhaul link. In addition to other functions, base stations 102 can also perform functions related to one or more of the transfer of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (such as handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, RAN sharing, multimedia broadcast multicast service (MBMS), subscriber and equipment tracking, RAN information management (RIM), paging, positioning, and delivery of alert messages. Base stations 102 can communicate with each other directly or indirectly (e.g., via the EPC / NGC) on the backhaul link 134, which can be wired or wireless.

[0047] Base stations 102 can communicate wirelessly with UEs 104. Each base station 102 can provide communication coverage for its respective geographic coverage area 110. In one aspect, although not shown in Figure 1 FIG., coverage area 110 can be divided into multiple cells (e.g., three) or sectors, each cell corresponding to a single antenna or antenna array of base station 102.

[0048] The term "cell" refers to a logical communication entity for communicating with a base station 102 (e.g., on a carrier frequency) and can be associated with an identifier to distinguish adjacent cells operating via the same or different carrier frequencies (e.g., physical cell identifier (PCID), enhanced cell identifier (E-CID), virtual cell identifier (VCID), etc.). In some examples, a carrier frequency can support multiple cells and can be configured with different cells according to different protocol types that can provide access for different types of devices (e.g., machine type communication (MTC), narrowband Internet of Things (NB-IoT), enhanced mobile broadband (eMBB), or others). In some cases, the term "cell" can refer to a portion (e.g., a sector) of the geographic coverage area 110 on which the logical entity operates. As used herein, depending on the context, the term "cell" or "sector" can correspond to one of the multiple cells of base station 102 or base station 102 itself.

[0049] Although adjacent macro cell geographical coverage areas 110 may partially overlap (e.g., in a handover region), some geographical coverage areas 110 may be substantially overlapped by a larger geographical coverage area 110. For example, a small cell base station 102' may have a coverage area 110' that substantially overlaps the coverage areas 110 of one or more macro cell base stations 102. A network including small cells and macro cells may be referred to as a heterogeneous network. The heterogeneous network may further include a home evolved Node B (HeNB) and / or a home gB node, which may serve a restricted group known as a closed subscriber group (CSG). A communication link 120 between a base station 102 and a UE 104 may include an uplink (UL) (also known as a reverse link) transmission from the UE 104 to the base station 102 and / or a downlink (DL) (also known as a forward link) transmission from the base station 102 to the UE 104. The communication link 120 may use MIMO antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. These communication links may be over one or more carriers. The allocation of carriers may be asymmetric with respect to the DL and UL (e.g., more or fewer carriers may be allocated to the DL compared to the UL).

[0050] The wireless communication system 100 may further include a wireless local area network (WLAN) access point (AP) 150 in communication with a WLAN station (STA) 152 via a communication link 154 in an unlicensed spectrum (e.g., 5 gigahertz (GHz)). When communicating in an unlicensed spectrum, the UE 152 (WLAN STA) and / or the WLAN AP 150 may perform a clear channel assessment (CCA) before communicating to determine whether the channel is available.

[0051] The small cell base station 102' may operate in a licensed and / or unlicensed spectrum. When operating in an unlicensed spectrum, the small cell base station 102' may employ LTE or 5G technology and use the same 5 GHz unlicensed spectrum as that used by the WLAN AP 150. The small cell base station 102' adopting LTE / 5G in an unlicensed spectrum may boost the coverage of the access network and / or increase the capacity of the access network. LTE in an unlicensed spectrum may be referred to as LTE unlicensed (LTE-U), licensed-assisted access (LAA), or MulteFire.

[0052] The wireless communication system 100 may further include a mmW base station 180 that may operate in mmW frequencies and / or near mmW frequencies to communicate with a UE 182. The extremely high frequency (EHF) is part of the RF in the electromagnetic spectrum. The EHF has a range of 30 GHz to 300 GHz and a wavelength between 1 millimeter and 10 millimeters. The radio waves in this frequency band may be referred to as millimeter waves. Near mmW may extend down to 3 GHz frequencies with a 100 millimeter wavelength. The super high frequency (SHF) band extends between 3 GHz and 30 GHz, which is also referred to as centimeter waves. Communication using the mmW / near mmW radio frequency band has high path loss and a relatively short range. The mmW base station 180 may utilize beamforming 184 with the UE 182 to compensate for the extremely high path loss and short range. Additionally, it will be appreciated that in an alternative configuration, one or more base stations 102 may also use mmW or near mmW and beamforming for transmission. Accordingly, it will be appreciated that the foregoing explanation is merely an example and should not be construed as limiting the various aspects disclosed herein.

[0053] The wireless communication system 100 may further include one or more UEs (such as UE 190) that are indirectly connected to one or more communication networks via one or more device-to-device (D2D) peer-to-peer (P2P) links. In Figure 1 an example, the UE 190 has a D2D P2P link 192 with a UE 104 connected to a base station 102 (e.g., the UE 190 may thereby indirectly obtain cellular connectivity), and a D2D P2P link 194 with a 'UE 152, WLAN STA connected to a WLAN AP 150 (the UE 190 may thereby indirectly obtain WLAN-based Internet connectivity). In one example, the D2D P2P links 192 - 194 may use any known D2D RAT (such as LTE direct (LTE-D), WiFi direct (WiFi-D), Bluetooth, etc.) to support.

[0054] Leveraging the increased data rate, reduced latency, and velocity-plus-distance-sensitive physical layer (PHY) and media access control layer (MAC) (PHY-MAC) of 5G, vehicle-to-everything (V2X) communication technology is being implemented to support intelligent transportation system (ITS) applications such as wireless communication between vehicles (vehicle-to-vehicle (V2V)), between a vehicle and roadside infrastructure (vehicle-to-infrastructure (V2I)), and between a vehicle and a pedestrian (vehicle-to-pedestrian (V2P)). The goal is to enable vehicles to sense their surrounding environment and communicate this information to other vehicles, infrastructure, and personal mobile devices. Such vehicle communication will enable safety, mobility, and environmental improvements not available with current technologies. As discussed above, aspects disclosed herein may use geofencing to reduce collisions.

[0055] Still referring to Figure 1 , the wireless communication system 100 may include a plurality of V-UEs 160 that may communicate with the base station 102 over a communication link 120 (e.g., using the Uu interface). The V-UEs 160 may also communicate directly with each other over a wireless sidelink 162, directly with a roadside access point 164 over a sidelink 166, or communicate with the UE 104 over a sidelink 168 using a peer-to-peer (P2P) / device-to-device (D2D) protocol (e.g., “PC5”, LTE V2X D2D interface) or ProSe. Sidelink communication may be used for D2D media sharing, V2V communication, V2X communication (e.g., cellular V2X (C-V2X) communication), emergency rescue applications, etc. One or more of the V-UEs 160 in a group of V-UEs 160 that utilize D2D communication may be within the geographical coverage area 110 of the base station 102. Other V-UEs 160 in such a group may be outside the geographical coverage area 110 of the base station 102 or may otherwise be unable to receive transmissions from the base station 102. In some cases, each group of V-UEs 160 that communicate via D2D communication may utilize a one-to-many (1:M) system where each V-UE 160 transmits to every other V-UE 160 in the group. In some cases, the base station 102 facilitates the scheduling of resources for D2D communication. In other cases, D2D communication is performed between the V-UEs 160 without involving the base station 102.

[0056] In one aspect, the V-UE 160 and Figure 1Any other UE described herein may have a component 170 that determines proximity to a geofence, also referred to herein as the geofence component 170. The geofence component 170 can be a hardware, software, or firmware component that, when executed, causes the V-UE 160 to perform the operations described herein. For example, the geofence component 170 can be a software module stored in the memory of the V-UE 160 and executable by a processor of the V-UE 160. As another example, the geofence component 170 can be a hardware circuit (e.g., ASIC, field programmable gate array (FPGA), etc.) within the V-UE 160. Although discussed herein in the context of collision prevention for purposes of illustration and explanation, it will be appreciated that the geofence / proximity-based functionality described herein can be used to perform other functionality.

[0057] In one aspect, the wireless sidelinks 162, 166, 168 may operate on a communication medium of interest, which may be shared with other vehicles and / or infrastructure access points and other communications between other RATs. The "medium" can include one or more frequency, time, and / or spatial communication resources associated with communication between one or more transmitter / receiver pairs (e.g., covering one or more channels across one or more carriers).

[0058] In one aspect, the wireless sidelinks 162, 166, 168 can be C-V2X links. First-generation C-V2X has been standardized in LTE, and the next-generation C-V2X is expected to be defined in 5G (also referred to as "New Radio" (NR) or "5G NR"). C-V2X is a cellular technology that also enables device-to-device communication. In the United States and Europe, C-V2X is expected to operate in the licensed ITS band in sub-6 GHz. Other bands may be allocated in other countries. Thus, as a specific example, the communication medium of interest utilized by the sidelinks 162, 166, 168 can correspond to at least a portion of the licensed ITS band in sub-6 GHz. However, the present disclosure is not limited to this band or cellular technology.

[0059] Other protocols for the wireless sidelinks 162, 166, 168 may include dedicated short range communication (DSRC) links. DSRC is a one-way or two-way short- to medium-range wireless communication protocol that uses the wireless access for vehicular environments (WAVE) protocol (also known as IEEE 802.11p) for V2V, V2I, and V2P communications. IEEE 802.11p is an approved amendment to the IEEE 802.11 standard and operates in the licensed ITS band at 5.9 GHz (5.85 - 5.925 GHz) in the United States. In Europe, IEEE 802.11p operates in the ITS G5A band (5.875 - 5.905 MHz). Other bands may be allocated in other countries. The V2V communications described above occur over a secure channel, which in the United States is typically a 10 MHz channel dedicated for security purposes. The remainder of the DSRC band (total bandwidth is 75 MHz) is intended for other services of interest to the driver, such as road rules, tolling, parking automation, etc. Thus, as a specific example, the medium of interest utilized by the sidelinks 162, 166, 168 may correspond to at least a portion of the unlicensed ITS band at 5.9 GHz.

[0060] Alternatively, the medium of interest may correspond to at least a portion of an unlicensed band shared among various RATs. Although different licensed bands have been reserved for certain communication systems (e.g., reserved by government entities such as the Federal Communications Commission (FCC) in the United States), these systems, particularly those employing small cell access points, have recently extended their operation into the unlicensed band, such as the unlicensed national information infrastructure (U-NII) bands used by wireless local area network (WLAN) technologies (most notably the IEEE 802.11x WLAN technologies generally known as "Wi-Fi"). Example systems of this type include different variants of code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal FDAM (OFDMA) systems, single carrier FDAM (SC-FDMA) systems, etc.

[0061] Communication between V-UEs 160 is referred to as V2V communication, communication between a V-UE 160 and one or more roadside access points 164 is referred to as V2I communication, and communication between a V-UE 160 and one or more P-UEs 104 is referred to as V2P communication. V2V communication between V-UEs 160 may include, for example, information about the location, speed, acceleration, heading direction, and other vehicle data of these V-UEs 160. V2I information received at a V-UE 160 from one or more roadside access points 164 may include, for example, road rules, parking automation information, etc. V2P communication between a V-UE 160 and a P-UE 104 may include information about, for example, the location, speed, acceleration, and heading direction of the V-UE 160 and the location, speed (e.g., in the case where the P-UE 104 is a bicycle), and heading direction of the P-UE 104. It will be appreciated that terms such as V-UE 160 and P-UE 104 are used herein for ease of explanation and not to limit specific applications, device types, etc. It will be appreciated that these devices, as well as other devices recited herein, may also be referred to using the general term UE, which applies to any user equipment device recited herein.

[0062] Figure 2A An example wireless network architecture 200 in accordance with one or more aspects is illustrated. For example, a Next Generation Core (NGC) 210 may be functionally regarded as a control plane function 214 (e.g., UE registration, authentication, network access, gateway selection, etc.) and a user plane function 212 (e.g., UE gateway function, access to a data network, IP routing, etc.), which operate cooperatively to form a core network. A user plane interface (NG-U) 213 and a control plane interface (NG-C) 215 connect one or more gNBs 222 to the NGC 210, and more specifically to the control plane function 214 and the user plane function 212. In an additional configuration, one or more eNBs 224 may also be connected to the NGC 210 via the NG-C 215 to the control plane function 214 and the NG-U 213 to the user plane function 212. Additionally, the (e)NBs 224 may communicate directly with the (g)NBs 222 via a backhaul connection 223. Accordingly, in some configurations, the new RAN 220 may have only one or more gNBs 222, while other configurations include one or more of eNB 224 and gNB 222. The (g)NBs 222 or the (e)NBs 224 may communicate with one or more UEs 240 (e.g., Figure 1 any UE depicted in, such as UE 104, UE 152, UE 160, UE 182, UE 190, etc.). In one aspect, two UEs 240 may communicate with each other on a wireless unicast sidelink 242, which may correspond toFigure 1 the radio side link 162 in

[0063] Another optional aspect may include a Location Management Function (LMF) 230 that communicates with the NGC 210 to provide location assistance for the UE 240. The LMF 230 uses information from the UE 240 and / or the new RAN 220 to determine the current location of the UE 240 and provide the current location of the UE 240 upon request. The LMF 230 may be implemented as multiple structurally separate servers, or alternatively may each correspond to a single server. Although Figure 2A the LMF 230 is illustrated as separate from the NGC 210 and the new RAN 220, the LMF 230 may instead be integrated into one or more components of the NGC 210 or the new RAN 220.

[0064] Figure 2B An example wireless network architecture 250 is illustrated in accordance with one or more aspects. For example, an Evolved Packet Core (EPC) 260 may be functionally viewed as a control plane function (i.e., a Mobility Management Entity (MME) 264) and a user plane function (i.e., a Packet Data Network Gateway / Service Gateway (P / SGW) 262), which operate in concert to form the core network. An S1 control plane interface (S1-MME) 265 and an S1 user plane interface (S1-U) 263 connect one or more eNBs 224 to the EPC 260, and more specifically to the MME 264 and the P / SGW 262, respectively.

[0065] In an additional configuration, one or more gNBs 222 may also be connected to the EPC 260 via the S1-MME 265 to the MME 264 and the S1-U 263 to the P / SGW 262. Additionally, the (s)eNBs 224 may communicate directly with one or more gNBs 222 via a backhaul connection 223, whether or not there is direct connectivity of the gNBs to the EPC 260. Accordingly, in some configurations, the new RAN 220 may have only the (s)gNBs 222, while other configurations include both the (s)eNBs 224 and the (s)gNBs 222. The (s)gNBs 222 or the (s)eNBs 224 may communicate with one or more UEs 240 (e.g., Figure 1 any of the UEs depicted in Figure 1 such as UE 104, UE 182, UE 190, etc.). In one aspect, two UEs 240 may communicate with each other on a radio side link 242, which may correspond to

[0066] Another optional aspect may include a location server 270 that may be in communication with the EPC 260 to provide location assistance for the UE(s) 240. In one aspect, the location server 270 may be an evolved serving mobile location center (E-SMLC), a secure user plane location (SUPL) location platform (SLP), a gateway mobile location center (GMLC), etc. The location server 270 may be implemented as multiple structurally separate servers, or alternatively may each correspond to a single server. The location server 270 may be configured to support one or more location services for the UE(s) 240, and the UE(s) 240 can be connected to the location server 270 via the core network, the EPC 260, and / or via the Internet (not illustrated).

[0067] Figure 3 FIG. 300 is a block diagram of a first wireless communication device 310 in communication with a second wireless communication device 350 via V2V / C-V2X / V2X / D2D communication (e.g., via a sidelink). The device 350 may include a UE that communicates with another device 350 via V2V / C-V2X / V2X / D2D communication (e.g., via a sidelink). The first wireless communication device 310 may include a UE that communicates with another UE (e.g., device 350) via a sidelink. In addition to the other components illustrated in Figure 3 the device 310 and 350 may each include a message component 391, 393 and / or a determination component 392, 394 within the geofencing component 170 or a message component 391, 393 and / or a determination component 392, 394 that functionally cooperates with the geofencing component 170. The message components 391, 393 may be configured to generate a message that has a first indication of a geographic region associated with the message, the geographic region being at least partially based on the geographic location of the device 310, 350 transmitting the message. The determination components 392, 394 may be configured to determine whether the receiving device 310, 350 is within a threshold range of the transmitting device 310, 350 and / or whether to send feedback for the message based on the first indication of the geographic region associated with the message and the geographic location of the receiving device 310, 350. Packets may be provided to a controller / processor 375 that implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a media access control (MAC) layer.

[0068] The transmit (TX) processor 316 and the receive (RX) processor 370 implement the layer 1 functionality associated with various signal processing functions. Layer 1, which includes the physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) encoding / decoding of the transport channels, interleaving, rate matching, mapping to physical channels, modulation / demodulation of the physical channels, and MIMO antenna processing. The TX processor 316 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The encoded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to OFDM subcarriers, multiplexed with reference signals (e.g., pilots) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a stream of time-domain OFDM symbols. The OFDM stream is space precoded to generate multiple spatial streams. Channel estimates from the channel estimator 374 may be used to determine the encoding and modulation schemes and for spatial processing. The channel estimates may be derived from reference signals transmitted by the device 350 and / or channel state feedback. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX modulates an RF carrier with the corresponding spatial stream for transmission.

[0069] At the device 350, each receiver 354RX receives signals via its respective corresponding antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides the information to the receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement the layer 1 functionality associated with various signal processing functions. The RX processor 356 may perform spatial processing on the information to recover any spatial streams destined for the device 350. If there are multiple spatial streams destined for the device 350, they may be combined by the RX processor 356 into a single OFDM symbol stream. The RX processor 356 then uses a fast Fourier transform (FFT) to transform the OFDM symbol stream from the time domain to the frequency domain. The frequency-domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, as well as the reference signals, are recovered and demodulated by determining the signal constellation points that were most likely transmitted by the device 310. These soft decisions may be based on the channel estimates calculated by the channel estimator 358. These soft decisions are then decoded and deinterleaved to recover the original data and control signals transmitted by the device 310 on the physical channel. These data and control signals are then provided to the controller / processor 359 that implements layer 3 and layer 2 functionality.

[0070] The controller / processor 359 may be associated with a memory 360 that stores program code and data. The memory 360 may be referred to as a computer-readable medium. The controller / processor 359 may provide demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing. The controller / processor 359 is also responsible for error detection using the ACK and / or NACK protocols to support HARQ operations.

[0071] Similar to the functionality described in connection with transmissions performed by device 310, the controller / processor 359 may provide RRC layer functionality associated with system information (e.g., MIB, SIB) capture, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression, and security (ciphering, deciphering, integrity protection, integrity verification); RLC layer functionality associated with transfer of upper layer PDUs, error correction via ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction via HARQ, priority handling, and logical channel prioritization.

[0072] Channel estimates derived by the channel estimator 358 from reference signals or feedback transmitted by device 310 may be used by the TX processor 368 to select an appropriate coding and modulation scheme and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354TX. Each transmitter 354TX may modulate an RF carrier with a respective spatial stream for transmission.

[0073] Transmissions are processed at device 310 in a manner similar to that described in connection with the receiver functionality at device 350. Each receiver 318RX receives signals via its respective corresponding antenna 320. Each receiver 318RX recovers the information modulated onto the RF carrier and provides the information to the RX processor 370.

[0074] The controller / processor 375 may be associated with a memory 376 that stores program code and data. The memory 376 may be referred to as a computer-readable medium. The controller / processor 375 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing. The controller / processor 375 is also responsible for error detection using the ACK and / or NACK protocols to support HARQ operations.

[0075] Wireless communication may include multicast communication directly between UEs. As an example, multicast sidelink communication may be performed via the PC5 interface. Each UE may communicate using sidelink multicast, for example, based on V2X communication, V2V communication, or D2D communication. Multicast may involve transmissions from one UE intended to be decoded by UEs that are part of a service group. The service group may include one or more UEs. A group ID identifying the service group may be included in a message, for example, in the sidelink control information (SCI) of a multicast message and / or as part of the MAC layer destination address.

[0076] In PC5 multicast, the transmitting UE may ensure that all intended recipients in the service group and in the vicinity of the transmitting UE accurately receive the message. If an intended recipient in the service group in the vicinity of the transmitting UE does not accurately receive the message, the transmitting UE may retransmit the message to ensure accurate reception of the message.

[0077] To improve reliability, feedback may be sent back from each receiving UE in the service group. For example, if a particular UE in the service group does not correctly receive the message, the UE may indicate an error in receiving the message, e.g., a NACK, to the transmitting UE via sidelink transmission. In response to the NACK, the transmitting UE may retransmit the message.

[0078] Figure 4 An example of communication 400 between multiple UEs (e.g., based on C-V2X / V2X / V2V / D2D communication) is illustrated. UE 402 may be the transmitting UE for the service group multicast message 414. UEs 404, 406, and 408 may be associated with the service group. UE 404 may have correctly received message 414 and does not transmit a NACK. UE 406 may have experienced an error in receiving the message. Thus, UE 406 may transmit a NACK 416 to UE 402 indicating that the message was not accurately received. In response to NACK 416, the transmitting UE 402 may determine, e.g., at 424, to retransmit message 414. However, negative feedback, e.g., (a) NACK(s), may be received from a distant recipient outside the desired neighborhood of the transmitting UE 402. As Figure 4 illustrated, the UE may expect to reliably receive the message by UEs within range / area 401. A UE 408 outside the expected area 401 and not adjacent to UE 402 may receive at least a portion of the message and send a NACK 420 to UE 402. However, UE 408 may be at such a distance that even with a retransmission from UE 402, UE 408 will likely never correctly receive message 414. Additionally, based on service requirements, there may be no need for a UE (e.g., UE 408) at that distance to receive the message as the message becomes irrelevant.

[0079] Thus, a (plural) NACK can be received from a receiving UE that is associated with the service group but at such a distance that it would be ineffective to cause the transmitter to retransmit the message. Such ineffective retransmissions would degrade the overall system performance by inefficient use of radio resources and by unnecessary potential interference to other wireless communications. Although a group ID (e.g., a common destination ID) can be used in an ad hoc C-V2X / V2X / V2V / D2D environment to identify a multicast service group, it may be difficult to manage or establish a common group identifier that is known only to vehicles in the service group that are also in the vicinity of the transmitting UE due to the highly mobile nature of the transmitter and / or receiver.

[0080] Aspects are proposed to limit feedback from receivers (e.g., receiving UEs) outside an expected geographical area by providing information that enables a receiver to determine whether it is an intended receiver of a message. The receiver can then determine whether to send feedback based on whether the receiver is an intended receiver of the message. A transmitter device (e.g., 402) can indicate geographical area information in each multicast message, where the geographical area information indicates that receivers (e.g., 404, 406) within the indicated geographical area (e.g., 401) are expected to reliably receive the message and should send feedback to help improve the multicast. This can help receivers (e.g., UE 408) outside the expected area determine that they do not have to send feedback. Thus, the geographical area information helps limit feedback from receivers in the service group but not in the vicinity of the transmitter. Although the problems have been described using an illustration of C-V2X / V2X / V2V / D2D communication among UEs 402, 404, 406, 408, the concepts are equally applicable to base stations, RSUs, mobile UEs, vehicle UEs, etc. participating in PC5-based communication.

[0081] To reduce the overhead for encoding geographical area information in a message, the geographical area can be indicated using predefined divisions or regions. For example, the geographical area can be divided into a series of uniformly sized rectangular divisions. The geographical area can be limited or extendable to cover the entire earth's surface. However, the various aspects disclosed herein are not limited to these examples. The predefined division or region (e.g., division ID or region ID) can be encoded in the message. In one example, the division / region for which the message is intended to be reliably received can include a circular area centered at the location of the transmitting device (e.g., UE 402 or other transmitter participating in PC5 communication) and extending with a radius indicated to the receiving device. In another example, the predefined division can have a non-circular shape. For example, a block can be divided into a set of rectangular, hexagonal, or other shaped divisions, each division having a corresponding division ID. In yet another example, the predefined division can have a customized shape. For example, the predefined division can follow a road contour, driving direction, geographical feature shape, etc. In another example, hierarchical divisions can be arranged in different layers. Each layer can correspond to divisions of different sizes. For example, the first layer can correspond to a division having a radius of 50m, a width of 50m, etc. The second layer can correspond to a division having a radius of 100m, a width of 100m, etc. The third layer can correspond to a division having a radius of 500m, a width of 500m, etc. Thus, the transmitting device and the receiving device can identify the division / region for which the message is intended to be reliably received based on a combination of the layer ID and the division ID corresponding to the layer ID. In another example, the division partitioning can be preconfigured for the receiving device. For example, the division partitioning can be based on the global coordinates of the geographical location. Then, the transmitting device can select the corresponding division from the preconfigured division partitioning. The receiving device and the transmitting device can receive occasional updates for the preconfigured division partitioning.

[0082] Figure 5 Illustrates an example communication flow 500 between a transmitting device 502 and a receiving device 504. The communication can be based on C-V2X / V2X / V2V / D2D communication, such as PC5 multicast, unicast, and / or broadcast communication. In some aspects, the communication can be based on other D2D direct communication, such as ProSe. Although Figure 5An example of communication between a transmitting device 502 interpreted as a UE and a receiving device 504 is described, but each concept can be equally applicable to base stations, RSUs, mobile UEs, vehicle UEs, etc. participating in PC5-based communication, C-V2X / V2X / V2V communication, or other direct D2D communication. As part of generating a service group message for transmission via, for example, C-V2X / V2X / V2V / D2D, the transmitting device 502 can determine a zone / area / range for which the message is intended to be reliably received by the receiving parties in the service group for that zone / area / range. This can provide a way for the transmitting device 502 to limit feedback to only the (receiving) parties within the expected zone / area / range. The transmitting device can determine its current geographical location at 503 and can use the current location to determine the area / zone / range in which the message is intended to be received and for which the transmitting device should receive HARQ feedback. For example, the transmitting device can identify a pre-configured zone in which the transmitting device is currently located. In another example, the zone can be centered on the transmitting device and have a selected radius. In another example, the transmitting device can define the zone in another way or otherwise select the area / range / zone.

[0083] As an example, the range can be selected based on, for example, quality of service (QoS) parameters associated with multicast. For example, the 5QI for different services can indicate QoS information such as resource type, priority level of communication, packet delay budget (PDB) indicating the amount of time a packet can be delayed, packet error rate (PER) indicating the limit on packet loss rate, average window, data burst volume parameter indicating the limit on the amount of data to be served within a period of time. Additionally, the application can indicate the range requirements for the traffic. For example, the range can be in the form of an absolute distance (e.g., 500 meters) or a relative level (e.g., long, medium, or short).

[0084] The transmitting device can indicate its current location and the surrounding range in the message. These can be indicated as a zone ID based on the geographical location of the transmitting device and the range of the surrounding zones. For example, the transmitting device can indicate the number or quantity N of adjacent surrounding zones in which the message is intended to be reliably received. If N = 1, the receiving device will need to be in the same zone as the transmitting device in order to be expected to reliably receive the message. If N = 2, the receiving devices in the same zone as the transmitting device and in the zones directly adjacent to the transmitting device zone will be expected to reliably receive the message. For example, if the zone is rectangular in shape, the devices expected to reliably receive the message should be in the same area as the transmitting device and in 8 adjacent zones. If the zone is hexagonal in shape, the devices expected to reliably receive the message should be in the same zone as the transmitting device and in 6 adjacent zones. N can be chosen as any number and is not limited to the examples provided herein.

[0085] Once the transmitting device determines the zone / area / range in which the message is intended to be reliably delivered and in which the recipient should send feedback, the transmitting device may generate the message. The message may include a control part and a data part. The control part may include, in the sidelink control information (SCI), an indication of the zone / area / range in which the message is intended to be reliably received. The SCI may also include group ID information corresponding to the service group for multicast. The group ID information may enable the message to be decoded by recipients associated with the service group and aware of the group ID. The group ID may be the same as the destination ID or may be different from the destination ID. The group ID may be provided by the application layer or middleware layer of the UE, or may be mapped by the V2X layer from the ID provided by the application layer. The group ID may correspond to a higher layer ID or an ID mapped from a higher layer ID, while the destination ID corresponds to a lower layer ID. The group ID may be mapped to the destination ID.

[0086] To further reduce the overhead of transmitting zone / area / range information in the message, the transmitting device may hash the group ID and the zone ID at 507 to generate a shortened ID, e.g., an information element (IE). The IE may then be embedded in the SCI of the message as part of generating the message at 509. After the generation at 509, the transmitting device 502 may transmit the message 511 together with the IE.

[0087] The receiving device 504 decodes at least a part of the message at 519 to determine an indication of the range / area / zone in which the message is intended to be reliably received, e.g., zone ID information. The receiving device may receive the control part of the message but may not correctly receive the data part of the message. Since the message is not correctly received, the receiving device 504 may need to determine whether to send HARQ feedback (e.g., NACK) to the transmitting device 502. The receiving device may determine at 521 whether to send a NACK based on the current position of the receiving device and based on the indication of the range / area / zone in which the message is intended to be reliably received included in the message. Thus, the receiving device may determine its current position at 517 and may determine to send a NACK when the receiving device 504 is within the indicated range / area / zone. For example, the receiving device may send a NACK when the receiving device is in the same zone as the transmitting device (e.g., when N = 1) or within the list of surrounding zones (when N>1). The surrounding zones may be based on the range / number / quantity indicated to the receiving device 504. In another example, the range / number / quantity of the surrounding zones may vary depending on the QoS of the multicast service. The QoS may be configured via RRC or via a higher layer.

[0088] The region / division / range indicated in message 511 may refer to at least one pre-configured division, which is pre-configured and stored at the receiving device. As illustrated at 513, the receiving device may receive an update to the pre-configured division(s) / region(s) / range(s). Although not illustrated, the transmitting device 502 may receive a similar update to the pre-configured division(s) / region(s) / range(s). A device may sometimes operate as a transmitting device and sometimes the same device may operate as a receiving device.

[0089] When an indication of a region and / or group ID is included in an IE, the receiving device 504 may monitor at least one IE in the SCI of any received message at 515. The IE that the receiving device monitors at 515 may be based on a predetermined hash of any group ID associated with the receiving UE for a multicast service hashed with the surrounding division ID. Since the receiving device may be mobile, the surrounding division ID may be updated based on the current location of the receiving device.

[0090] If the UE determines at 521 that the UE is within the region / division / range for the expected reliable reception of the message and the UE has not correctly received message 511, the UE may respond to the transmitting device 502 with a NACK 523. The UE may determine whether to send a NACK based on additional aspects (such as whether the receiver is associated with a service group corresponding to the group ID included in the message, etc.). In response to the NACK 523, the transmitting device 502 may retransmit the message 525 to ensure reliable reception of the message by the receiving device 504.

[0091] Figure 6 and 7 An example of the interaction of using division IDs between different layers at the transmitting device and the receiving device for C-V2X / V2X / V2V communication is illustrated. Although aspects are presented for a V2X example, the aspects may be applied to other direct D2D communications. In Figure 6In Example 600, the application layer 602, layer 3 for D2D communication (e.g., V2X layer) 604, and the access stratum (AS) layer 606 are for the transmitting device (e.g., 502). In one example, layer 3 may include the V2X layer. In other examples, aspects may be applied to other D2D direct communication, such as ProSe. The application layer 608, layer 3 for D2D communication (e.g., V2X layer) 610, and the AS layer 612 are for the receiving device (e.g., 504). At the transmitting device, the application layer may provide the group ID and the QoS profile of a particular service group to layer 3. The QoS profile may include an indication of the 5QI for the service group, the rate of the service group, and / or the range of the service group. The application layer 602 may also provide the data to be transmitted to the service group in a message (e.g., a multicast message) to layer 3. The data may be provided together with the corresponding group ID. The application layer may provide the provider service identifier (PSID) together with the data. Layer 3 may map the group ID received from the application layer to the destination L2ID (Dst.L2 ID) of the service group. Layer 3 may also store the QoS profile of the service group. If layer 3 does not provide the QoS profile to layer 3, layer 3 may use the PSID to determine the corresponding QoS profile, e.g., map the PSID to the QoS profile. Similarly, if the application layer does not provide the group ID to layer 3, the Dst.L2 ID determined by layer 3 may be based on the mapping of the PSID to the Dst.L2 ID. Such mapping information may be pre-configured on the UE, stored in the (U)SIM card, or provisioned from the network via a dynamic provisioning mechanism (e.g., Open Mobile Alliance (OMA) Device Management (DM) OMA-DM or UE policy delivery mechanism). The AS layer may receive the Dst.L2 ID, source L2 ID, QoS profile (e.g., including 5QI and / or range), and data of the service group from layer 3. The AS layer may determine whether to use the acknowledged mode (e.g., NACK mode) for multicast based on the 5QI from the QoS profile or a local policy. For example, if the 5QI indicates a requirement for high reliability (e.g., a very low PER value), the transmitting UE may choose to use acknowledgments to achieve such high reliability. In the NACK mode, the transmitting device may monitor the feedback (e.g., (a) NACK) to determine whether to retransmit the message. The AS layer 606 may also determine the zone ID to be used in the message. The zone ID may correspond to the zone in which the transmitting device is currently located. The AS layer 606 may also determine the range to be used in the message. The range may indicate an additional range around the transmitting device for which the transmitting device aims for the message to be reliably received, or the zone or list of zones in which the receiving device is located. The range may notify the receiver whether it should provide feedback. The transmitting device may then transmit a message including the SCI 614 and the data 616. The SCI may include information indicating the group ID or Dst.L2 ID, the zone ID determined by the AS, and / or the range determined by the AS.

[0092] At the receiving device, the application layer 608 provides the group ID of the service group associated with the receiving device to layer 610. Layer 610 determines the Dst.L2 ID based on the group ID, similar to the mapping performed by layer 604 of the transmitting device. The AS layer 612 at the receiving device determines its own zoning ID, such as the zoning in which the receiving device is currently located. When the receiving device receives a message including the SCI 614 and data 616, the receiving device determines whether to send feedback (e.g., NACK) in the case where the data part of the message is not correctly received. The receiving device can determine whether to send a NACK based on whether the Dst.L2 ID determined by layer 610 matches the Dst.L2 ID indicated in the SCI 614 of the message and / or based on whether the zoning ID of the receiving device determined by AS 612 matches the zoning ID indicated in the SCI 614 or falls within the range of the zoning ID indicated in the SCI 614. If the Dst.L2 ID matches and the zoning ID of the receiving device falls within the indicated range of the zoning ID of the transmitting device, the receiving device can provide a NACK, for example, in the case where the data part of the message is not received. If layer 610 at the receiving device does not provide the Dst.L2 ID to the AS layer 612, the receiving device can determine not to send a NACK. The SCI can carry different forms of information about the zoning ID, Dst.L2 ID, and range. For example, the zoning ID and Dst.L2 ID of the SCI can be hashed to reduce the overhead required to send the message. In this case, the SCI can adopt a format different from the format used for other V2X message transmissions (e.g., broadcast messages). Therefore, additional bits can be included in the SCI to distinguish the format of the message, for example, whether the message is broadcast, multicast, or unicast.

[0093] Figure 7 Example 700 in Figure 6 is similar to the example in Figure 6 The application layer 702 at the transmitting device and layer 3 (e.g., the V2X layer) 704 for D2D communication can operate similarly to the example in Figure 7In this case, the range may not be determined or indicated by the AS layer 706 at the transmitting device. Instead, the application layer 708 at the receiving device may provide the QoS profile of the service group to the layer 710 at the receiving device. The 5QI and range information may be provided from the layer 710 of the receiving device to the AS layer 712. The AS layer at the receiving device may then determine not only its own zoning ID based on the current location of the receiving device but also the range to be used when determining whether to send feedback. Thus, the SCI 714 sent from the transmitting device together with the data 716 may not include information indicating the range. The receiving device may determine whether to send feedback based on any combination of whether the Dst.L2 ID of the SCI matches the Dst.L2 ID determined by the layer 710, whether the zoning ID determined by the AS 712 is within the zoning ID indicated in the SCI 714 plus the range determined by the AS layer 712. Alternatively, the receiving device may determine the range based on its own zoning ID and verify whether the zoning ID indicated in the SCI 714 is within that range. For example, the receiving device may determine not to send a NACK if the zoning ID in the SCI 714 is not within the range of the receiving device's own zoning ID. As explained above, the SCI may include other information for supporting operations. For example, the SCI may include an indication of whether the message is a retransmitted message and the sequence number of the message. In this case, the receiving device may determine whether to send a NACK based on whether it has received the original transmission of the same message.

[0094] Figure 8 is a block diagram illustrating various components of an exemplary UE 800 in accordance with aspects of the present disclosure. In one aspect, the UE 800 may correspond to any of the UEs described herein, such as Figure 1 104, 152, 160, 182, 190 in Figure 2A and 2B UE 240 in Figure 3 or Figure 8 UEs 310, 350, etc. in Figure 8 For simplicity, the various features and functions illustrated in the block diagram of Figure 8 are connected together using a common bus, which is intended to represent that these various features and functions are operatively coupled together. Those skilled in the art will recognize that other connections, mechanisms, features, functions, etc. may be provided and adapted as needed to operatively couple and configure an actual UE. Additionally, it is recognized that one or more of the features or functions illustrated in the example of

[0095] UE 800 may include at least one transceiver 804 that is connected to one or more antennas 802 to communicate with other network nodes (such as other vehicles (e.g., one or more other V-UEs 160), infrastructure access points (e.g., one or more roadside access points 164), P-UEs (e.g., one or more P-UEs 140), base stations (e.g., base station 102), etc.) via at least one specified RAT (e.g., C-V2X or IEEE 802.11p) on the medium of interest utilized by the unicast sidelink 162. The transceiver 804 may be configured in various ways to transmit and encode signals (such as messages, indications, information, etc.) according to the specified RAT and vice versa to receive and decode signals (such as messages, indications, information, pilots, etc.). As used herein, a "transceiver" may include a transmitter circuit, a receiver circuit, or a combination thereof, but does not necessarily provide both transmission and reception functionality in all designs. For example, in designs where full communication is not necessary, a low-functional receiver circuit may be employed in some designs to reduce cost (e.g., simply providing a receiver chip or similar circuitry for low-level sniffing).

[0096] UE 800 may also include a satellite positioning service (SPS) receiver 806. The SPS receiver 806 may be connected to one or more antennas 802 for receiving satellite signals. The SPS receiver 806 may include any suitable hardware and / or software for receiving and processing SPS signals. The SPS receiver 806 requests information and operations from other systems when appropriate and performs the calculations necessary to determine the location of UE 800 using measurements obtained by any suitable SPS algorithm.

[0097] One or more sensors 808 may be coupled to the processor 810 to provide information related to the state and / or environment of UE 800, such as speed, heading (e.g., compass heading), headlight status, mileage fuel consumption, etc. As an example, the one or more sensors 808 may include a speedometer, a tachometer, an accelerometer (e.g., a microelectromechanical systems (MEMS) device), a gyroscope, a geomagnetic sensor (e.g., a compass), an altimeter (e.g., a barometric altimeter), etc.

[0098] The processor 810 may include one or more microprocessors, microcontrollers, ASICs, and / or digital signal processors that provide processing functionality as well as other computing and control functionality. The processor 810 may include any form of logic suitable for executing or causing the components of UE 800 to execute at least the techniques provided herein. In some aspects, the processor 810 may include: a modem processor to at least partially perform functions at the PHY layer and the MAC layer; and an application processor configured to at least partially perform functions at the application layer.

[0099] The processor 810 may also be coupled to a memory 814, which is used to store data and software instructions for performing the programmed functionality within the UE 800. The memory 814 may be on-board the processor 810 (e.g., within the same integrated circuit (IC) package), and / or the memory 814 may be external to the processor 810 and functionally coupled via a data bus.

[0100] The UE 800 may include a user interface 850, which provides any suitable interface system that allows a user to interact with the UE 800, such as a microphone / speaker 852, a keypad 854, and a display 856. The microphone / speaker 852 provides voice communication services for the UE 800. The keypad 854 includes any suitable buttons for user input to the UE 800. The display 856 includes any suitable display, such as, for example, a backlit liquid crystal display (LCD), and may further include a touchscreen display for additional user input modes.

[0101] In one aspect, the UE 800 may include a geofencing component 170 that is functionally coupled or integrated into the processor 810. The geofencing component 170 may be a hardware, software, or firmware component that, when executed, causes the UE 800 to perform the operations described herein. For example, the geofencing component 170 may be a software module stored in the memory 814 and executable by the processor 810. As another example, the geofencing component 170 may be a hardware circuit within the UE 800 (e.g., an ASIC, a field programmable gate array (FPGA), etc.). The functionality of the geofencing component 170 will be discussed in more detail below.

[0102] As discussed above, for example, a sector ID or a region ID can be encoded in a message to reduce overhead and allow for the determination of the range / distance between the transmitting UE and the receiving UE that may be associated with the message (e.g., based on the sector ID, layer ID, etc.). For example, the range information for a message can include a circular area centered at the transmitting device location or other transmitters participating in PC5 communication and extending a radius towards the receiving UE. Also as mentioned above, various alternative sectors can be defined, such as predefined sectors including non-circular shapes, each sector having a corresponding sector ID or following a road contour, driving direction, geographical feature shape, etc. Similarly, as discussed, hierarchical sectors can be organized in different layers, where each layer corresponds to a sector of a different size (e.g., 50m, 100m, etc.). Accordingly, the transmitting device and the receiving device can identify the sector / region that is the expected range of the message based on the layer ID and / or the sector ID. In a specific example, a first UE can transmit, together with a message, the expected range associated with the message (e.g., configured as a sector ID and / or range information). A second UE can receive this message and use the sector ID and / or range information to determine whether the second UE is within a threshold range for taking an action on the message. In various aspects discussed herein, this determination can be performed at the PHY-MAC layer to reduce power consumption. If the receiving UE is within the threshold range, the second UE can enable application layer processing of the message. For example, the sector ID / range information can be provided in the sidelink control information (SCI). Additionally, in some aspects, direction-based control (e.g., beamforming / beam steering) can be used to improve situational awareness and reduce RF congestion. It will be appreciated that if the first UE is moving, a dynamic geographical fence boundary can be generated around the first UE based on the range information associated with the message (e.g., sector ID, etc.). Accordingly, in addition to determining the sector / region / range for which reliable reception of the message is intended as discussed above, various aspects can determine whether to block or permit application layer processing of the message based on a range threshold.

[0103] Aspects disclosed herein include techniques for determining proximity to a geofence and invoking an action based on that proximity. An example action can be an action related to collision avoidance. Other actions can include, but are not limited to, visual, audible, tactile, or other warnings or commands indicating a change in motion state. As mentioned above, existing wireless risk warning systems require always-on broadcasts and application layer message processing, resulting in increased power consumption and additional RF congestion. Aspects of the present disclosure create a "mobile geofence" by exposing 5G NR PC5 PHY-MAC embedded controls to the application layer. Aspects of the present disclosure also reduce device power consumption by diverting the 5G NR PC5 PHY-MAC control message mechanism to enable or disable application layer message processing. For example, a zoning ID and / or range-based control (e.g., sidelink control information (SCI) range and / or zoning ID parameter). Additionally, direction-based control can be provided (e.g., beam steering to improve situational awareness and reduce RF congestion). Reduced power consumption can be obtained for battery-powered devices by prohibiting upper layer processing and message transmission. High message reliability within a configured threshold range can be achieved based on NR NACK-based reliability, as discussed above. Additionally, dynamic geofence boundaries can be generated around the PC5-device based on real-time proximity to pedestrians, cyclists, animals, etc. Furthermore, aspects of the present disclosure using PC5 provide a greater range than infrastructureless vehicle communications such as DSRC or IEEE 802.11p, which are also limited to broadcast operations.

[0104] In accordance with aspects disclosed herein, a proximity component can use two control message parameters (zoning ID and / or range information) to determine the range between UEs. In accordance with aspects, the zoning ID can be based on the current UE location within a defined zone (as discussed herein) and the range can be defined as a discrete number of zones or an absolute distance measurement. However, aspects disclosed herein are not limited to these examples. These two control message parameters can also be used at the PHY-MAC to control retransmissions to achieve high reliability. As mentioned above, the zoning ID and range information can be used to determine the range between UEs at the PHY-MAC level. This allows for a virtual moving geofence / dynamic geofence that follows the movement of the UE. In contrast, conventional architectures determine range / location at the application layer to provide power-consuming geofences. In some UE configurations, separate application processors may need to be activated to perform application layer processing, while PHY-MAC layer operations can be performed at the modem level to achieve even further power savings.

[0105] Conventionally, PHY-MAC control message parameters are not visible to the application layer. To provide various aspects of the present disclosure, additional functional modules are provided to enable or disable application layer message processing based on the range embedded in D2D / C-V2X communications (e.g., 5G NR PC5 communications) and optionally direction determination (based on sector ID and range information), as discussed above. As used herein, the terms D2D, C-V2X, and / or PC5 information may include one or more application layer messages, control messages, and / or information related to UE-to-UE range determination (e.g., sector ID, range, etc.). According to various aspects of the disclosure, D2D, C-V2X, and / or PC5 information may be transmitted within a message container using the unicast sidelink mechanism defined by the 3rd Generation Partnership Project (3GPP). Other aspects may use other 3GPP broadcast types (such as broadcast or multicast) to transmit D2D, C-V2X, and / or PC5 information. Similarly, the terms D2D, C-V2X, and / or PC5 communications may include one or more application layer messages, control messages / information related to UE-to-UE range determination (e.g., sector ID, range, etc.) transmitted over an air interface (e.g., the PC5 interface). For ease of illustration, the term PC5 communications will be used in the following examples, but it should be appreciated that the various aspects of the disclosure may generally be applied to D2D communications and devices.

[0106] In Figure 9In this, a proximity component 900 is described, which may be functionally similar to the geofence component 170. It will be appreciated that the various modules described may communicate with each other in a two-way manner and may perform different functions in the transmission mode than in the reception mode. For example, in the application layer 910, a range threshold specification based on the application layer (e.g., corresponding to the geofence size in terms of the number of sectors, absolute distance, etc.) may be determined in the range specification module 916. Optionally, an orientation (including two or more dimensions) may be provided to focus the geofence on a specific vector / direction. The range threshold may then be provided to the PHY-MAC layer 920. In the transmission mode, the range threshold may be provided to the range module 922, which may then use this information to include it in the PC5 communication to identify the range for which the message is intended to be received (e.g., the number of sectors along with the device's current sector ID) (e.g., defining the geofence of the device). Optionally, the orientation information from the range specification module 916 may be provided to the direction module 926, which may then direct the RF signal of the PC5 communication (including the range information) in a specific direction (e.g., towards a known road, etc.). In the reception mode, optionally, the RX range threshold may be used in the threshold detection module 924 to determine whether the received message is within the RX threshold range, which may be different from the range received in the PC5 communication. This receiver-based range setting allows for an alternative range control separate from the Tx-based range control. Alternatively, the range threshold may be determined at the PHY-MAC layer 920 based on signal processing of the received communication (e.g., the determined reliability threshold) and / or based on the range included in the PC5 communication from the transmitting device. In some aspects, the range that defines the geographical area (e.g., sector ID and range) intended for the message in the PC5 communication may be used to define the range threshold. However, in other aspects, the range may not be provided in the PC5 communication, or the range may be replaced by the RX range threshold determined at the receiving UE. For example, the receiving UE may optionally define the RX range threshold to specify a minimum range for 2 adjacent sectors. Accordingly, if the range received in the PC5 communication message is less than 2, the RX range threshold may be used by the threshold detection module 924 to determine whether the range threshold is met.

[0107] Regardless of where the range threshold is specified (e.g., determined based on a received message, specified at the application layer, determined at the PHY-MAC layer, etc.), the threshold detection module 924 can be configured to determine whether the range between UEs / the range to the transmitting UE is within the threshold range (e.g., violates a geofence, proximity limit). For example, the range module 922 can determine information (such as the sector ID of the transmitting UE and / or range information (e.g., the number of adjacent sectors)) based on the PC5 communication received from the transmitting UE (e.g., in the SCI as discussed herein). This information can be used by the range module 922 to determine whether the receiving UE is within the threshold range. For example, it can be determined to be within the threshold range based on the range threshold (e.g., the range received in the PC5 communication), the sector ID of the transmitting UE, and the sector ID of the receiving UE (e.g., the sector ID of the receiving UE is within 2 adjacent sectors of the transmitting UE). Additionally, it will be appreciated that in some aspects, the threshold range value can be determined such that a proximity limit is violated when the determined range is greater than the threshold. Accordingly, in some configurations, the threshold range can be violated when the range between UEs is less than the threshold range value, while in other configurations, the threshold range can be violated when the range between UEs is greater than the threshold range value.

[0108] In contrast to conventional systems that use GPS positioning at the application layer, it will be appreciated that in various aspects disclosed herein, the UE - to - UE range can be determined at the PHY - MAC layer 920. For example, if the threshold detection module 924 determines that the UE - to - UE range is greater than the range threshold based on the geographical location (e.g., zoning ID) of the receiving UE (including the threshold detection module 624), subsequent application layer messages may not be passed to the application layer 910. Thus, the application layer 910 module will not be activated and reachability success rate savings can be achieved, as discussed herein. Blocking messages from reaching the application layer 910 reduces UE upper - layer processing (e.g., modules 912, 914, etc.) and reduces unnecessary message transmissions (e.g., attempts to respond to messages), thereby reducing UE power consumption. If the UE - to - UE range is not greater than the range threshold (e.g., within 2 adjacent zones), the application layer message may be passed to the application layer 910. For example, the application layer message may be passed to the application layer message processing module 912, and in some aspects, based on the content of the application layer message, the UE action module 914 may initiate specific actions based on these messages. In the case where the receiving UE is determined to be within the threshold range (e.g., within a geofence, within a proximity limit, within a number of adjacent zones, and / or within an absolute distance from the transmitting UE), application layer message elements may be provided to specify UE actions. For example, when the UE - to - UE range is not greater than the range threshold (e.g., the receiving UE is within the geofence of the transmitting UE), the receiving UE may perform one or more actions, such as initiating a warning (audio, tactile, and / or visual), initiating braking, steering, decelerating, and / or performing other actions to avoid a collision. In the following paragraphs regarding Figure 10 and 11 to provide examples of the various messages discussed herein.

[0109] As discussed above, the range threshold can be derived from the PC5 communication received from the originating / transmitting UE based on the zoning ID and range information of the originating UE. For example, the originating UE may provide its zoning ID and range information (e.g., 1 adjacent zone) to define the geographical area within which messages in the PC5 communication are intended to be received and optionally actions are to be taken. The receiving UE can then determine the originating UE zoning ID and range information (e.g., 1 adjacent zone) from the PC5 communication in the range module 922. The threshold detection module 924 can use this geographical area (e.g., originating party zoning ID and range information) to determine whether the current geographical location (e.g., the zoning ID of the receiving UE) is less than or equal to the range threshold (e.g., 1 adjacent zone). For example, if the receiving UE has the same zoning ID as the originating UE zoning ID or is located within 1 adjacent zoning ID of the originating UE zoning ID, the receiving UE is within the range threshold and application layer processing will be enabled, as discussed above.

[0110] In the replacement example, as discussed above, an optional RX range threshold may be established at the receiving UE (e.g., from the application layer 910). The originating UE may provide only the zoning ID in the PC5 communication (e.g., for some low-power / constrained devices), or the provided range may be overridden based on the receiving UE's own RX range threshold. If the receiving UE determines that the RX range threshold is 1 adjacent zone, the result will be the same as the example of the range information (1 adjacent zone) provided in the PC5 communication from the originating UE. Alternatively, if the receiving UE determines that the RX range threshold is 2 adjacent zones and is configured to override the range received in the PC5 communication, the application layer message provided in the PC5 communication from the originating UE will be processed with a greater UE-to-UE range (e.g., up to 2 adjacent zones instead of 1).

[0111] It will be appreciated that the determination of the UE-to-UE range may take any form discussed herein and is not limited to this specific zoning ID example. Additionally, it will be appreciated that the zoning ID and range information may represent any one of a variety of configurations, as discussed herein. For example, the zoning ID may be a circle around the originating / transmitting UE location with a given radius. Alternatively, the zoning ID may be a rectangle, and for example, 1 adjacent zone may include 8 additional zones each adjacent to each side and each corner of the rectangular zone defined by the zoning ID of the originating UE. Alternatively, the range may be defined as the absolute distance from the geographical location of the originating / transmitting UE (e.g., 100 meters). Accordingly, it will be appreciated that the foregoing examples are provided for illustrative purposes only, and specific examples should not be construed as limiting the various aspects disclosed herein.

[0112] According to some additional aspects, instead of a one-dimensional range, the range information may be two-dimensional or three-dimensional as determined by the direction module 296, which allows beam steering to focus the transmitted RF signal. The PHY-MAC layer 920 may optionally be configured to use the direction module 926 to enable beam steering to direct the RF beam energy to the situationally most relevant location (e.g., towards a known road, intersection, transmitting UE, away from obstacles, etc.). Focusing the RF signal / energy on a specific direction / vector can reduce unnecessary RF congestion, RF noise, and provide enhanced situational awareness.

[0113] The above has mainly discussed the functions of component 900 from the perspective of the recipient. As discussed above, various modules can be used in the transmission operation. For example, the first UE is configured to transmit messages in D2D communication (e.g., C-V2X, PC5, etc.). The message may include one or more data elements related to the geofence of the first UE. For example, the range specifying module 916 may specify the range to be associated with the message. The range specifying module 916 may also optionally determine the orientation of the first UE relative to a potential recipient UE (e.g., towards a road, intersection, railway line, away from an obstacle, etc.). The range module 922 may identify the current geographical location of the first UE, which may be converted into a zoning ID, and the range received from the range specifying module 916 may be included together with the zoning ID for transmission (e.g., included in the SCI for PC5 communication). The direction module 926 may optionally be used to direct the RF signal based on the orientation (e.g., through beamforming and / or beam steering) to focus the transmission energy in the direction of the potential recipient UE.

[0114] Figure 10Data elements that can be used to augment existing application layer standard messages or be part of new application layer messages are explained. Application layer messages can include those defined by industry and government organizations such as the Society of Automotive Engineers (SAE), the European Telecommunications Standards Institute - Intelligent Transport Systems (ETSI-ITS), or others. Examples of existing application layer messages suitable for encapsulating application layer data elements (DEs) include the SAE Personal Safety Message (PSM), which is defined in the SAE specification J2735, "Dedicated Short Range Communications (DSRC) Message Set Dictionary". For example, in accordance with various aspects disclosed herein, new application data elements related to proximity alert types, geofence alerts, and geofence movement instructions can be included in the PSM. The PSM is an example of an existing application layer message defined by the SAE. Another example is the Basic Safety Message (BSM), however, it should be noted that the data elements defined herein can also be easily included in other existing SAE application layer messages. It will also be appreciated that the new application data elements can alternatively be encapsulated in other messages of different standard groups (e.g., IEEE, 3GPP, etc.). Accordingly, the various aspects disclosed herein are not limited to the specific examples provided herein. According to some example aspects, the proximity alert type data element includes various entity types, including pedestrians, cyclists, animals, vehicles, and others. This data element can be used to warn a UE (e.g., a vehicle, a tag bearer, a pedestrian, etc.) of the presence of an entity within a distance threshold (e.g., warning a tag bearer of a vehicle or warning a vehicle of a tag bearer). The geofence alert data element includes various warning or action types, such as an audible alert, a tactile alert, and others. This data element can be used to directly warn of an action. The geofence movement instruction data element can include instructions for a UE (e.g., a vehicle, a tag bearer, etc.) to initiate movement in a direction defined by an angle value (e.g., J2735 DE_Anglevalue). It will be appreciated that these messages, data elements, and actions can assist in UE-to-UE range determination and proximity detection to a geofence and / or can be used for various functions such as collision avoidance.

[0115] Figure 11New application layer messages in accordance with aspects of the present disclosure are explained. For example, new messages (such as proximity alert messages) and their selected elements are provided as illustrated. The new messages may enable request and response interactions between various UEs (e.g., vehicles and device / tag bearers). A proximity alert message may have a message part that includes an originator parameter and a proximity alert component. The originator parameter content may include, for example, identity, statistical characteristics, dynamic characteristics, type: proximity alert request, and type: proximity alert response. The static characteristic identity may include a permanent ID identifier, such as a vehicle license plate number, VIN number, alphanumeric code identification number of a UE issued for an animal, an existing number or alphanumeric code of a UE associated with a pedestrian, cyclist, motorcycle, or other non-vehicle road user, or a number or alphanumeric code assigned to a UE specifically for proximity-based geofence detection. Other static characteristics may include vehicle type, vehicle size, color, or other descriptive attributes. The static characteristics of a cyclist, motorcycle, electric unicycle, moped, or user or other non-vehicle may include wheel size, physical size, color, number of permitted riders, or other static attributes. The dynamic characteristics may include attributes associated with the current motion state and permitted motion state of the UE or the device containing the UE. Vehicle dynamic characteristics may include position, speed, linear acceleration, attitude, angular velocity, where these five attributes are measured along three orthogonal axes. Additional vehicle dynamic parameters may include turning radius, braking distance. In accordance with various aspects disclosed herein, the proximity alert component may include data elements that include proximity alert type, geofence alert, and geofence motion instruction. The proximity alert type data element includes various entity types, including pedestrians, cyclists, animals, and others. This data element may be used to warn a UE (e.g., a vehicle, tag bearer) of the presence of an entity within a range threshold (e.g., warning a tag bearer of a vehicle or warning a vehicle of a tag bearer). The geofence alert data element includes various warning or action types, such as audible alerts, tactile alerts, and others. This data element may be used for direct warning actions. The geofence motion instruction data element may include an instruction to initiate movement (e.g., by a tag bearer) in a direction defined by an angle value (e.g., J2735 DE_Angle value). It will be appreciated that these messages, data elements, and actions may assist in range determination between UEs and proximity detection to a geofence and / or may be used for various functions such as collision avoidance.

[0116] Figure 12An exemplary signal flow between a first UE (UE1) 1230 (e.g., a transmitting UE) and a second UE (UE2) 1220 is illustrated. It will be appreciated that in various aspects, UE2 1220 and UE1 1230 can be a variety of devices, and the respective roles can change. For example, in one aspect, according to various aspects of the present disclosure, UE1 can be a vehicle and UE2 can be another device / tag bearer (e.g., another vehicle, pedestrian, cyclist, animal, livestock, construction equipment, agricultural equipment, etc.). It will be appreciated that UE2 1220 and UE1 1230 can be similar to any UE disclosed herein (e.g., Figure 1 UEs 104, 152, 160, 182, 190 in Figure 2A and 2B UE 240 depicted in Figure 3 and any one of UEs 310, 350 in

[0117] etc.). Figure 10 At 1202, D2D information (e.g., included in PC5 communication) is transmitted from UE2 1220 to UE1 1230. In some aspects, the PC5 communication can be or include an existing application layer message, such as PSM, which includes new data elements (see, e.g., Figure 10 data elements in Figure 10 ). Alternatively, the PC5 communication can include a new application layer message, which includes new data elements (see, e.g., Figure 10 data elements in Figure 10 ). Upon receiving the PC5 communication, at 1204, a determination is made as to whether UE2 1220 (the transmitting UE) is within a threshold range. As discussed above, this determination can be performed at the PHY-MAC and, in some aspects, can be performed without GPS assistance. If UE2 1220 is determined to be outside the threshold range, then at 1205, the PC5 communication (e.g., application layer message, data elements, etc.) is not provided to the application layer. If UE2 1220 is determined to be within the threshold range, then at 1206, the PC5 communication is provided to the application layer and / or application layer processing for the received PC5 communication is enabled. At 1208, optionally, high reliability transmission can be enabled by UE1 1230 for communication with UE2 1220. In some aspects, high reliability transmission can include the receiver (e.g., UE1 1230) being able to definitely negative acknowledge (NACK) known transmissions that were not correctly received or being configured to definitely acknowledge (ACK) received transmissions when the transmitter and receiver are close enough (as discussed above). At 1210, optionally, UE1 1230 can take action on new data elements (e.g., application layer messages) in the received D2D information. For example, a warning / alert can be activated, movement can be initiated, etc. However, it will be appreciated that in some aspects, no action may be taken directly on the message.

[0118] It will be appreciated that, among other things, in accordance with various aspects of the present disclosure, the message receiving UE (UE1) 1230 may be a vehicle, and the transmitting UE2 1220 may be a device / tag bearer (e.g., another vehicle, pedestrian, cyclist, animal, livestock, construction equipment, agricultural equipment, etc.). Additionally, D2D information is not limited to the PC5 communication and / or application layer message examples used above. Accordingly, it will be appreciated that the foregoing examples are provided merely for illustration, and specific examples should not be construed as limiting the various aspects disclosed herein.

[0119] Figure 13 An exemplary signal flow between a transmitting / originating UE2 1320 (e.g., a device / tag bearer) and a message receiving UE1 1330 (e.g., a vehicle) in accordance with aspects of the present disclosure is illustrated. It will be appreciated that in various aspects, UE1 1330 and UE2 1320 may be a variety of devices, and the various roles may change. For example, in one aspect, in accordance with various aspects of the present disclosure, UE2 1320 may be a vehicle and UE1 1330 may be another device / tag bearer (e.g., another vehicle, pedestrian, cyclist, animal, livestock, construction equipment, agricultural equipment, etc.). It will be appreciated that UE2 1320 and UE1 1330 may be similar to any UE disclosed herein (e.g., Figure 1 UE 104, 152, 160, 182, 190 in Figure 2A and 2B UE 240 depicted in Figure 3 any one of UE 310, 350 in

[0120] Figure 11 ​)。Upon receiving PC5 communication, at 1304, a determination is made as to whether UE2 1320 (the transmitting UE / transmitter) is within a threshold range. As discussed above, this determination is performed at PHY-MAC and in some aspects can be performed without GPS assistance. If UE2 1320 is determined to be outside the threshold range, then at 1305, the PC5 communication (e.g., new message, data element, etc.) is not provided to the application layer. If UE2 1320 is determined to be within the threshold range, then at 1306, the PC5 communication is provided to the application layer and / or the application layer is enabled to process the received PC5 communication. At 1308, optionally, high-reliability transmission is enabled by UE1 1330 for communication with UE2 1320. As discussed above, in some aspects, high-reliability transmission can include the receiver (e.g., UE1 1330) being able to affirmatively negative acknowledge (NACK) known transmissions that were not correctly received or being configured to affirmatively acknowledge (ACK) received transmissions when the transmitter and receiver are close enough. At 1310, optionally, UE1 1330 takes an action specified in the PC5 communication (e.g., proximity alert request). At 1312, a response (e.g., proximity alert response) is made to the PC5 communication (e.g., proximity alert request) from UE2 1320 in a transmission from UE1 1330 back to UE2 1320. In some aspects, the proximity alert response can contain similar elements such as alert type, geofence alert action, receiver location (optional), entity identifier (i.e., vehicle ID number, VIN, etc.), geofence movement instruction to be accepted or initiated.

[0121] It will be appreciated that D2D information is not limited to the PC5 communication, proximity alert request, and / or proximity alert response examples used above. Accordingly, it will be appreciated that the foregoing examples are provided for illustrative purposes only and that a particular example should not be construed as limiting the various aspects disclosed herein.

[0122] Figure 14 An exemplary signal flow between a first UE UE1 1420 (e.g., message receiving UE) and a second UE UE2 1430 (e.g., transmitting UE) in accordance with some aspects of the present disclosure is illustrated. For example, in one aspect, in accordance with various aspects of the present disclosure, UE1 1420 can be a vehicle and UE2 1430 can be another device / tag bearer (e.g., another vehicle, pedestrian, cyclist, animal, livestock, construction equipment, agricultural equipment, etc.). It will be appreciated that UE1 1420 and UE2 1430 can be similar to any UE disclosed herein (e.g., Figure 1 UE 104, 152, 160, 182, 190 in Figure 2A and 2BThe UE 240 depicted in Figure 3 any one of the UEs 310, 350 in

[0123] At 1401, the transmitting UE2 1430 may optionally direct the transmitted RF signal (as part of the D2D message / information transmitted from the UE2 1430 to the UE1 1420 at 1302 (e.g., PC5 communication such as discussed above)) towards the UE 1420. It will be appreciated that beamforming and / or beam steering can be used to direct the transmitted RF signal / RF transmission power towards the approximate location / direction of the UE1 1420. For example, even if the UE2 1430 does not know the specific location of the UE1 1420 (or even does not know if there is a UE1 1420), it may be able to direct the transmitted RF signal towards the location or direction where the UE may be located (e.g., roads, intersections, bike paths, hiking paths, railroad tracks, etc.). It will be appreciated that the optional RF steering aspect can reduce RF / channel congestion, improve transmission reliability, and reduce power consumption and other benefits. For example, if the UE2 1430 is a pedestrian in an urban environment, the initial beam steering can be based on the orientation and / or movement direction of the pedestrian and any roads or intersections in the orientation and / or movement direction of the pedestrian. The transmitted RF signal / RF transmission power will not be directed towards adjacent buildings, behind the pedestrian, etc. to reduce the power consumed by the device and improve reliable transmission by reducing the RF noise floor, which improves the performance of the transmitting device and other devices in the wireless communication network. Similarly, if the UE2 1430 is a tagged animal in a rural environment, the initial beam steering can be directed towards known roads, intersections, hiking paths, etc. based on the orientation and / or movement direction of the tagged animal. The transmitted RF signal / RF transmission power will not be directed towards areas outside the road, which can reduce the power consumed by the device.

[0124] Regardless of the transmission technology, upon receiving PC5 communication, at 1404, a determination is made as to whether UE1 1420 is within a threshold range. As discussed above, this determination can be performed at the PHY-MAC and, in some aspects, can be performed without GPS assistance. Additionally, in some aspects, it can be determined that UE2 is within the threshold range because this determination is based on the inter-UE range / distance between UE1 and UE2, as discussed above. If UE1 1420 is determined to be outside the threshold range, then at 1405, the PC5 communication (e.g., application layer message) is not provided to the application layer. If UE1 1420 is determined to be within the threshold range, then at 1406, the PC5 communication is provided to the application layer and, in some aspects, application layer processing is enabled to process the received PC5 communication. Optionally, at 1408, high-reliability transmission is enabled at UE1 1420 for communication with UE2 1430, as discussed in the foregoing disclosure. At 1410, optionally, UE1 1420 can adopt the actions specified in the PC5 communication (e.g., application layer message, proximity alert request, etc.). At 1411, optionally, UE1 1430 can direct an RF signal towards UE2 1430 in response to a D2D message / information received from UE2 1430 (e.g., PC5 communication, such as discussed above). For example, the D2D / PC5 communication from UE2 1430 (e.g., application layer message, proximity alert request, etc.) can include requests and responses, and a response (e.g., proximity alert response) can be made thereto in the transmission from UE1 1420 back to UE2 1430 at 1412.

[0125] It will be appreciated that in other aspects, in accordance with various aspects of the present disclosure, the message receiving UE UE1 1420 can be another device / tag bearer (e.g., another vehicle, pedestrian, cyclist, animal, livestock, construction equipment, agricultural equipment, etc.). Additionally, in some configurations, the beamforming / beam steering aspects discussed above can be used, while in other configurations, the beamforming / beam steering aspects discussed above may not be used. For example, regardless of whether there will be a response to the D2D information and / or the RF signal / beam steering used in the response (e.g., 1411), RF signal / beam steering 1401 can be used for the D2D information transmission 1402. Similarly, in some aspects, regardless of whether RF signal / beam steering is used in the transmission of the D2D information, RF signal / beam steering 1411 can be used for the response to the D2D information. Accordingly, it will be appreciated that the foregoing examples are provided for illustrative purposes only and that specific examples should not be construed as limiting the various aspects disclosed herein.

[0126] It will be appreciated from the foregoing that the various aspects discussed and disclosed herein include methods for determining proximity to a geofence for various applications (such as collision avoidance) and optionally invoking actions based on the proximity. Figure 15 A flowchart of a method 1500 in accordance with at least one aspect of the present disclosure is illustrated. The method 1500 may be performed by a first UE (e.g., similar to any UE disclosed herein (e.g., Figure 1 UE 104, 152, 160, 182, 190 in Figure 2A and 2B UE240 depicted in Figure 3Any one of the UEs 310, 350, etc. in )). At block 1502, a first UE (e.g., a vehicle, a tag bearer, a pedestrian, etc.) receives device-to-device (D2D) information from a second UE (e.g., a vehicle, a tag bearer, a pedestrian, etc.). At block 1504, the first UE may determine whether the first UE is within a threshold range from the second UE based on the D2D information (e.g., as mentioned above, this may be performed at the PHY-MAC layer). At block 1506, if the first UE is within the threshold range (i.e., "yes" in the flowchart), the first UE may enable application layer processing of the message in the D2D information (e.g., this may include existing application layer messages (e.g., SAE PSM) or new data elements included in new messages, as discussed above). At block 1516, if the first UE is not within the threshold range (i.e., the "no" path in the flowchart), the first UE may block the message from reaching the application layer (e.g., at the PHY-MAC, as discussed above). As discussed previously, this may allow significant power savings as the application layer processor and / or processing functions will not be initialized. At block 1508, if the first UE is within the threshold range, the first UE may optionally enable high reliability transmission. For example, as discussed above, to improve reliability, feedback may be sent back from the receiving UE (the first UE). For example, if the first UE does not correctly receive the D2D information (e.g., PC5 communication), the first UE may transmit a NACK (e.g., via PC5 communication) to indicate to the second UE that there is an error in receiving the message. In response to the NACK, the second UE may retransmit the message. Additionally, beamforming and / or beam steering may also be used to direct the RF signal / beam towards the second UE, as discussed above. At block 1510, the first UE may optionally perform one or more actions (e.g., alert, movement, etc., as discussed above) at the first UE based on one or more data elements of the message. It will be appreciated from the present disclosure that other methods and variations of the methods may be recognized and a detailed flowchart and / or discussion of each of them will not be provided. For example, in various aspects, a response to the received D2D information may be transmitted from the first UE to the second UE. The transmitted response may optionally use beamforming / beam steering to more precisely direct the RF transmission to the second UE, as discussed herein. Accordingly, aspects of the present disclosure should not be construed as limited to the illustrative examples provided.

[0127] It will be appreciated from the foregoing that various aspects discussed and disclosed herein include methods for transmitting application layer messages (e.g., personal safety messages), which may include the new data elements discussed herein related to the geographical fencing of the transmitting UE (e.g., see Figure 10 ) and / or new messages (e.g., see Figure 11 ). Figure 16AA flowchart of method 1610 is illustrated. Method 1610 for wireless communication is performed at a first user equipment (UE) 1601. At block 1602, the first UE receives device-to-device (D2D) communication from a second user equipment (UE), which includes an application layer message (an existing message such as PSM or a new message) including one or more data elements related to a geofence of the second UE. In various other aspects, the application layer message (an existing message such as PSM or a new message) may be included as a message including range information included in the D2D information for allowing determination of the geofence and geofence violation, as described in detail above. Similarly, the first UE and the second UE may be any of the various UEs disclosed herein. Accordingly, in accordance with the disclosure herein, it will be appreciated that other methods and variations of the methods may be recognized and a detailed flowchart and / or discussion of each of them will not be provided. Accordingly, aspects of the present disclosure should not be construed as limited to the illustrative examples provided.

[0128] Figure 16B A flowchart of method 1620 is illustrated. Method 1620 for wireless communication is performed at a user equipment (UE) 1621. At 1622, the UE transmits device-to-device (D2D) communication, where the D2D communication includes an application layer message (e.g., an existing message such as PSM with new data elements or a new message) and the application layer message includes one or more data elements related to a geofence of the UE. The method may optionally include determining, at 1624, the orientation of the UE relative to a potential receiving UE. It will be appreciated that the orientation / direction is towards one or more potential receiving UEs (e.g., towards a road, away from an obstacle, etc., as discussed above). The term potential receiving UE is used because the transmitting UE may not know if there are any UEs within the transmission range that can receive the transmission. The method may also optionally include, at 1626, directing the transmitted RF signal in the direction of the potential receiving UE based on the orientation. As discussed above, the directing of the RF signal may be performed by beamforming and / or beam steering to focus the RF signal / transmission power, which may reduce power consumption, improve situational awareness, and reduce RF congestion and other benefits, as discussed herein.

[0129] In various other aspects, the UE may determine the geographical location of the UE (e.g., zoning ID, area ID, etc.) and the range for the geofence, which may be used in the D2D information for determining the geofence and geofence violation, as described in detail above. Similarly, the UE and the potential receiving UE may be any of the various UEs disclosed herein. Accordingly, in accordance with the disclosure herein, it will be appreciated that other methods and variations of the methods may be recognized and a detailed flowchart and / or discussion of each of them will not be provided. Accordingly, aspects of the present disclosure should not be construed as limited to the illustrative examples provided.

[0130] The functionality of the various devices, components, methods, etc. disclosed herein can be implemented in a variety of ways consistent with the teachings herein. In some designs, the functionality of these modules can be implemented as one or more electrical components. In some designs, the functionality of these blocks can be implemented as a processing system including one or more processor components. In some designs, at least a portion of these modules' functionality can be implemented using, for example, one or more integrated circuits (e.g., AISC). As discussed herein, an integrated circuit can include a processor, software, other related components, or some combination thereof. Thus, the functionality of different modules can be implemented, for example, as different subsets of an integrated circuit, different subsets of a set of software modules, or a combination thereof. Moreover, it will be appreciated that a given subset (e.g., of an integrated circuit and / or a set of software modules) can provide at least a portion of the functionality of more than one module.

[0131] Figure 17 An example proximity-based geofencing device 1700 (which may be similar to geofencing component 170 and / or component 900) for implementing various aspects of the present disclosure is illustrated, which is represented as a series of interrelated functional modules. Device 1700 can correspond to any UE disclosed herein (e.g., Figure 1 UE 104, 152, 160, 182, 190 in Figure 2A and 2B UE 240 depicted in Figure 3either UE310, 350, etc. in ). In the illustrated example, the module 1702 for receiving D2D information (e.g., PC5 communication) from a second user equipment (UE) may correspond, at least in some aspects, to, for example, a communication device (e.g., transceiver 804 and / or a processing system (e.g., processor 810), etc.), as discussed herein. The module 1704 for determining whether a first UE is within a threshold range (the inter-UE range between the first UE and the second UE, as discussed above) based on the D2D information may correspond, at least in some aspects, to, for example, a communication device (e.g., transceiver 804 and / or a processing system (e.g., processor 810)) and, in some aspects, may be a function of the PHY-MAC layer of a modem processor (e.g., including functionality such as range module 922 and / or threshold detection module 924), as discussed herein. The module 1706 for implementing application layer processing of one or more data elements of the D2D information when the first UE is within the threshold range may correspond, at least in some aspects, to, for example, a processing device (e.g., processor 810, etc.) as discussed herein and, in some aspects, may correspond to an application layer processor (e.g., 910) that performs processing at the application layer. The module 1707 for blocking a message from reaching the application layer when the first UE is not within the threshold range may correspond, at least in some aspects, to, for example, a communication device (e.g., transceiver 804 and / or a processing system (e.g., processor 810)) and, in some aspects, may be a function of the PHY-MAC layer of a modem processor (e.g., threshold detection module 924), as discussed herein. The optional module 1708 for enabling high-reliability transmission when the first UE is within the threshold range from the second UE may correspond, at least in some aspects, to a communication device (e.g., transceiver 804 and / or a processing system (e.g., processor 810)). Another optional module 1710 for performing one or more actions at the first UE based on one or more data elements in a message may be, for example, a processing system (e.g., processor 810) or may be an application processor configured to perform functions at the application layer (e.g., 910, 914), as discussed herein. Another optional module 1711 for guiding the RF signal of a transmission may correspond, at least in some aspects, to a communication device (e.g., transceiver 804 and / or a processing system (e.g., processor 810)) and, in some aspects, may be a function of the PHY-MAC layer of a modem processor (e.g., direction module 926) and / or beamforming functionality, as discussed herein. It will be appreciated that, depending on the configuration, module 1711 may be used to direct the RF signal in an initial (originating) transmission towards an intended direction and / or to direct the RF signal towards the originating UE in response to a transmission from the originating UE, as discussed herein.

[0132] In addition, by Figure 9and 17 Each of the modules, components, and / or functions represented and other modules, components, and / or functions described herein may be implemented using any suitable means. Such means may also be implemented, at least in part, using the corresponding structures taught herein. For example, the components described above in connection with "module for..." may also correspond to the functionality of a similarly named "means for...". Thus, in some aspects, one or more of such means may be implemented using one or more processors, memories, integrated circuits, or other suitable structures taught herein, including implementation as algorithms. Those skilled in the art will recognize that algorithms in the present disclosure may be represented by the above functions, actions, etc. and sequences of actions that can be represented by pseudocode. For example, Figure 9 and 17 Each of the components, modules, and / or functions represented in may include code for performing the various functions, aspects, and actions disclosed herein.

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

[0134] In addition, those skilled in the art will appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the aspects disclosed herein may be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability of hardware and software, the various illustrative components, blocks, modules, circuits, and steps are described above in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

[0135] The various illustrative logical blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented or performed using a general purpose processor, a DSP, an 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 herein. A general purpose processor may be a microprocessor, but in the 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, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0136] The methods, sequences, and / or algorithms described in connection with the various aspects disclosed herein can be embodied directly in hardware, in software modules executed by a processor, or in a combination of both. The software modules can reside in random access memory (RAM), flash memory, read-only memory (ROM), erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such that the processor can read from and write to the storage medium. In an alternative, the storage medium can be integrated into the processor. The processor and the storage medium can reside in an ASIC. The ASIC can reside in a UE. In an alternative, the processor and the storage medium can reside in the UE as discrete components.

[0137] In one or more exemplary aspects, the described functionality can be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions can be stored on or transmitted via a computer-readable medium as one or more instructions or code. The computer-readable medium includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage medium can be any available medium that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. As used herein, disk and disc include compact disc (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 should also be included within the scope of computer-readable media.

[0138] Although the foregoing disclosure shows illustrative aspects of the present disclosure, it should be noted that various changes and modifications can be made therein without departing from the scope of the present disclosure as defined by the appended claims. The functions, steps, and / or acts in the method claims according to the aspects of the present disclosure described herein need not be performed in any particular order. Moreover, although the elements of the present disclosure may be described or claimed in the singular, the plural is also contemplated unless expressly stated to be limited to the singular.

Claims

1. A method for wireless communication at a first user equipment (UE), comprising: receiving device-to-device (D2D) communication including an application layer message from a second user equipment (UE), wherein the application layer message includes one or more data elements related to a geofence of the second UE; determining, based on the D2D information, whether the first UE is within the geofence of the second UE; and enabling application layer processing of the application layer message when the first UE is within the geofence of the second UE.

2. The method according to claim 1, further comprising: enabling high-reliability transmission at the first UE when the first UE is within the geofence of the second UE.

3. The method according to claim 1, further comprising: performing one or more actions at the first UE based on the one or more data elements of the application layer message.

4. The method according to claim 1, wherein the application layer message is a proximity alert message.

5. The method according to claim 4, wherein the proximity alert message enables request and response interaction between the first UE and the second UE.

6. The method according to claim 4, wherein the proximity alert message includes an originator parameter and a proximity alert component.

7. The method according to claim 6, wherein the originator parameter includes at least one of the following: identity, static characteristics, dynamic characteristics, type: proximity alert request, or type: proximity alert response.

8. The method according to claim 6, wherein the proximity alert component includes data elements, and the data elements include at least one of the following: proximity alert type data element, geofence alert data element, and geofence movement instruction data element.

9. The method according to claim 8, wherein the proximity alert type data element includes an entity type, and the entity type includes pedestrian, cyclist, animal, vehicle, or other.

10. The method according to claim 8, wherein the geofence alert data element includes a warning or an action, and the warning or the action includes an auditory alert, a tactile alert, or other alerts.

11. The method according to claim 8, wherein the geofence movement instruction data element includes an instruction to initiate movement.

12. The method according to claim 1, wherein the application layer message includes a response request.

13. The method according to claim 12, further comprising: transmitting a response to the second UE when the first UE is within the geofence of the second UE.

14. The method according to claim 1, wherein the one or more data elements are encapsulated in the application layer message.

15. The method according to claim 14, wherein the application layer message is a Society of Automotive Engineers (SAE) application layer message including at least one of a basic safety message (BSM) or a personal safety message (PSM).

16. The method according to claim 14, wherein the one or more encapsulated data elements include at least one of the following: a proximity alert type data element, a geofence alert data element, or a geofence movement instruction data element.

17. The method according to claim 16, wherein the proximity alert type data element includes an entity type, and the entity type includes a pedestrian, a cyclist, an animal, a vehicle, or others.

18. The method according to claim 16, wherein the geofence alert data element includes a warning or an action, and the warning or the action includes an auditory alert, a tactile alert, or other alerts.

19. The method according to claim 16, wherein the geofence movement instruction data element includes an instruction to initiate a movement.

20. A method for wireless communication at a user equipment (UE), comprising: transmitting device-to-device (D2D) communication, wherein the D2D communication includes an application layer message, wherein the application layer message includes one or more data elements related to a geofence of the UE, and receiving, in a case where a receiving UE is within the geofence of the UE, a response transmitted based on enabling application layer processing of the application layer message by the receiving UE.

21. The method according to claim 20, wherein the one or more data elements are encapsulated in the application layer message.

22. The method according to claim 20, wherein the application layer message is a Society of Automotive Engineers (SAE) application layer message including at least one of a basic safety message (BSM) or a personal safety message (PSM).

23. The method according to claim 21, wherein the one or more encapsulated data elements include at least one of the following: a proximity alert type data element, a geofence alert data element, or a geofence movement instruction data element.

24. The method according to claim 23, wherein the proximity alert type data element includes an entity type, and the entity type includes a pedestrian, a cyclist, an animal, a vehicle, or others.

25. The method according to claim 23, wherein the geofence alert data element includes a warning or an action, and the warning or the action includes an auditory alert, a tactile alert, or other alerts.

26. The method according to claim 23, wherein the geofence movement instruction data element includes an instruction to initiate a movement.

27. The method according to claim 20, wherein the application layer message is a proximity alert message.

28. The method according to claim 27, wherein the proximity alert message enables a request and response interaction between the UE and a potential receiving UE.

29. The method according to claim 27, wherein the proximity alert message includes an originator parameter and a proximity alert component.

30. The method according to claim 29, wherein the originator parameter includes at least one of the following: an identity, static characteristics, dynamic characteristics, type: proximity alert request, or type: proximity alert response.

31. The method according to claim 29, wherein the proximity alert component includes data elements, and the data elements include at least one of the following: proximity alert type data element, geofence alert data element, and geofence movement instruction data element.

32. The method according to claim 31, wherein the proximity alert type data element includes an entity type, and the entity type includes pedestrian, cyclist, animal, vehicle, or others.

33. The method according to claim 31, wherein the geofence alert data element includes a warning or an action, and the warning or the action includes an audible alert, a tactile alert, or other alerts.

34. The method according to claim 31, wherein the geofence movement instruction data element includes an instruction to initiate movement.

35. The method according to claim 20, further comprising: determining an orientation of the UE relative to a potential recipient UE.

36. The method according to claim 35, further comprising: guiding a radio frequency (RF) signal of a transmission of the D2D communication in a direction of the potential recipient UE based on the orientation.

37. The method according to claim 36, wherein guiding the RF signal is performed by beamforming and / or beam steering.

38. The method according to claim 36, wherein guiding the RF signal further includes at least one of the following: directing the RF signal in a direction of a known road, or directing the RF signal in a direction away from an obstacle.

39. The method according to claim 20, further comprising: determining a geographical location of the UE; and determining a range of the geofence of the UE.

40. A first user equipment (UE), comprising: a transceiver; and at least one processor coupled to a memory and the transceiver, the at least one processor cooperating with the transceiver and configured to: receive a device-to-device (D2D) communication including an application layer message from a second user equipment (UE), wherein the application layer message includes one or more data elements related to a geofence of the second UE; determine, based on the D2D information, whether the first UE is within the geofence of the second UE; and enable application layer processing of the application layer message when the first UE is within the geofence of the second UE.

41. The first UE according to claim 40, wherein the at least one processor is configured to: perform one or more actions at the first UE based on the one or more data elements of the application layer message.

42. The first UE according to claim 40, wherein the application layer message is a proximity alert message.

43. The first UE according to claim 42, wherein the proximity alert message includes originator parameters and a proximity alert component.

44. The first UE according to claim 43, wherein the proximity alert component includes data elements, and the data elements include at least one of the following: proximity alert type data element, geofence alert data element, and geofence movement instruction data element.

45. The first UE according to claim 44, wherein the proximity alert type data element includes an entity type, and the entity type includes pedestrian, cyclist, animal, vehicle, or others, wherein the geofence alert data element includes a warning or an action, and the warning or the action includes an auditory alert, a tactile alert, or other alerts, and wherein the geofence movement instruction data element includes an instruction to initiate a movement.

46. The first UE according to claim 40, wherein the one or more data elements are encapsulated in the application layer message.

47. The first UE according to claim 46, wherein the application layer message is a Society of Automotive Engineers (SAE) application layer message.

48. The first UE according to claim 46, wherein the one or more encapsulated data elements include at least one of the following: proximity alert type data element, geofence alert data element, or geofence movement instruction data element.

49. A user equipment (UE), comprising: a transceiver; and at least one processor coupled to a memory and the transceiver, the at least one processor cooperating with the transceiver and configured to: transmit device-to-device (D2D) communication, wherein the D2D communication includes an application layer message, wherein the application layer message includes one or more data elements related to a geofence of the UE; and receive, in a case where a receiving UE is within the geofence of the UE, a response transmitted based on enabling application layer processing of the application layer message by the receiving UE.

50. The UE according to claim 49, wherein the one or more data elements are encapsulated in the application layer message.

51. The UE according to claim 50, wherein the application layer message is a Society of Automotive Engineers (SAE) application layer message.

52. The UE according to claim 50, wherein the one or more encapsulated data elements include at least one of the following: proximity alert type data element, geofence alert data element, or geofence movement instruction data element.

53. The UE according to claim 49, wherein the application layer message is a proximity alert message.

54. The UE according to claim 53, wherein the proximity alert message includes originator parameters and a proximity alert component, and the proximity alert component includes data elements, and the data elements include at least one of the following: proximity alert type data element, geofence alert data element, and geofence movement instruction data element.

55. The UE according to claim 54, wherein the proximity alert type data element includes an entity type, the entity type including a pedestrian, a cyclist, an animal, a vehicle, or others, wherein the geofence alert data element includes a warning or an action, the warning or the action including an audible alert, a tactile alert, or other alerts, and wherein the geofence movement instruction data element includes an instruction to initiate movement.

56. The UE according to claim 49, wherein the at least one processor is further configured to: Determine an orientation of the UE relative to a potential recipient UE.

57. The UE according to claim 56, wherein the transceiver is configured to direct the RF signal among the transmissions in a direction of the potential recipient UE based on the orientation.

58. The UE according to claim 49, wherein the at least one processor is further configured to: Determine a geographical location of the UE; and Determine a range of the geofence of the UE.

Images