Paging for network-based user equipment (UE)-to-UE communications

Abstract

The present disclosure provides systems, methods, and devices for wireless communications that support paging for network-based user equipment (UE)-to-UE communications. In a first aspect, a method of wireless communication performed at a network entity includes identifying a UE-to-UE paging request condition originating from a source UE. The method also includes identifying one or more other network entities within the paging area relative to the location of the source UE. The method also includes sending one or more paging messages to the one or more other network entities according to the UE-to-UE paging request condition. Other aspects and features are also claimed and described.

Description

Cross-references to related applications

[0001] This application claims the benefit of U.S. Patent Application No. 18 / 463,098, filed September 7, 2023, entitled “PAGING FOR NETWORK-BASED USEREQUIPMENT (UE)-TO-UE COMMUNICATION,” which is expressly incorporated herein by reference in its entirety. Technical Field

[0002] This disclosure relates generally to wireless communication systems, and more specifically to paging for network-based user equipment (UE) to UE communication. Several features enable and provide improved communication, including efficient resource utilization for enabling UE to UE paging and message sending / receiving. Background Technology

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

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

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

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

[0007] Autonomous and semi-autonomous vehicles represent a growing area of ​​research and interest in wireless communications. Many vehicles are equipped with onboard units (OBUs) that provide wireless communication capabilities. As an example, an OBU integrated into a vehicle can support wireless communication between the vehicle and a wireless network (e.g., a cellular network) via uplink and downlink air interfaces (also known as Uu interfaces). This type of communication supports the vehicle's connectivity functions, such as receiving driving directions, relaying sensor inputs, sending and receiving text messages, and making voice calls. Additionally, research has begun using OBUs to provide direct vehicle-to-vehicle communication via a sidelink interface (also known as the PC5 interface). However, such direct vehicle-to-vehicle communication is typically short-range and may not be robust enough to convey desired information between vehicles or other UEs that are not close enough to the original vehicle (or UE). In such implementations, conventional network-based communication can be used, but this may not be designed to serve the specific requirements and context of vehicle-to-UE communication or other UE-to-UE communication. Summary of the Invention

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

[0009] In one aspect of this disclosure, a method for performing wireless communication at a network entity is disclosed. The method includes identifying a UE-UE paging request condition originating from a source user equipment (UE). The method also includes identifying one or more other network entities within a paging area relative to the location of the source UE. The method further includes sending one or more paging messages to the one or more other network entities based on the UE-UE paging request condition.

[0010] In an additional aspect of this disclosure, an apparatus for wireless communication at a network entity includes a processing system comprising one or more processors and one or more memories coupled to the processors. The processing system is configured to cause the network entity to identify UE-to-UE paging request conditions originating from a source UE. The processing system is also configured to cause the network entity to identify one or more other network entities within a paging area relating to the location of the source UE. The processing system is further configured to cause the network entity to send one or more paging messages to the one or more other network entities based on the UE-to-UE paging request conditions.

[0011] In an additional aspect of this disclosure, an apparatus for wireless communication at a network entity includes components for identifying UE-UE paging request conditions originating from a source UE. The apparatus also includes components for identifying one or more other network entities within a paging area related to the location of the source UE. Furthermore, the apparatus includes components for sending one or more paging messages to the one or more other network entities based on the UE-UE paging request conditions.

[0012] In an additional aspect of this disclosure, a non-transitory computer-readable medium stores instructions that, when executed by a processor, cause the processor to perform operations for wireless communication at a network entity. The operations include identifying a UE-to-UE paging request condition originating from a source UE. The operations also include identifying one or more other network entities within a paging area relative to the location of the source UE. These operations further include sending one or more paging messages to the one or more other network entities based on the UE-to-UE paging request condition.

[0013] The features and technical advantages of the examples according to this disclosure have been summarized rather broadly above in order to better understand the detailed description below. Additional features and advantages will be described below. The disclosed concepts and specific examples can be readily used as the basis for modifying or designing other structures for achieving the same purpose of this disclosure. Such equivalent constructions do not depart from the scope of the appended claims. The characteristics of the concepts disclosed herein (both their organization and operation) and their associated advantages will be better understood from the following description when considered in conjunction with the accompanying drawings. Each figure in the drawings is provided for illustrative and descriptive purposes and not as a definition of limitation of the claims.

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

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

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

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

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

[0019] Figure 4This is a block diagram illustrating an example wireless communication system that supports paging for network-based UE-to-UE communication based on one or more aspects.

[0020] Figure 5A This is a block diagram illustrating an example of a wireless communication system for paging used in network-based vehicle-to-everything (V2X) communication, supported by one or more aspects.

[0021] Figure 5B This is a block diagram illustrating another example of a paging wireless communication system that supports one or more aspects for network-based V2X communication.

[0022] Figure 5C This is a block diagram illustrating another example of a paging wireless communication system that supports one or more aspects for network-based V2X communication.

[0023] Figure 6 This is a flowchart illustrating an example process for paging in network-based UE-to-UE communication, supported by one or more aspects.

[0024] Figure 7 It is a block diagram of an example network entity for paging in network-based UE-to-UE communication, based on one or more aspects of support.

[0025] The same reference numerals and names in the various figures indicate the same elements. Detailed Implementation

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

[0027] This disclosure provides systems, apparatus, methods, and computer-readable media that support paging for network-based User Equipment (UE) to UE communications. For example, this disclosure describes techniques that enable servers or other network entities implementing Access and Mobility Management (AMF) functionality to provide network-based or assisted UE-to-UE paging and messaging to various proximity-based communication applications at various UEs, such as Vehicle-to-Everything (V2X) communication applications. For illustration, a network entity may identify UE-to-UE paging conditions originating from a source UE, such as by receiving a UE-to-UE paging request from the source UE, the location of the receiving source UE, and the paging range, or using other methods further described herein. In response to identifying UE-to-UE paging conditions, the network entity may determine the location of the source UE and the paging range associated with the source UE. For example, the network entity may receive location information from the source UE or infer the location of the source UE based on signaling from a base station (or other network entity) serving the source UE. As another example, the network entity may receive the paging range from the source UE or an application server supporting a proximity-based communication application, or by accessing a configuration file associated with the source UE. Network entities can determine a paging area based on the location and paging range of the source UE, such as, as a non-limiting example, a circular area centered on the location of the source UE with a radius equal to the paging range. When identifying the paging area, the network entity can identify one or more other network entities (e.g., base stations, roadside units (RSUs), etc.) serving cells or tracking areas intersecting with the paging area. The network entity can then send one or more paging messages to the identified other network entities for delivery to other UEs served by those entities. Paging messages can be addressed to a specific UE, a UE group (e.g., a group of UEs sharing a group ID), any UE performing a specific application (e.g., a V2X application), UEs in an application group (e.g., UEs sharing a V2X group ID), or the paging message can be broadcast to all UEs within the service area of ​​other network entities. In this way, the network can help support proximity-based communication between UEs, particularly those that may not support direct UE-to-UE communication via sidelinks.

[0028] Specific implementations of the subject matter described herein can be implemented to achieve one or more of the following potential advantages or benefits. These advantages improve proximity-based vehicle UE applications by providing paging capabilities in vehicle UE applications involving wireless communication with poorly defined or undefined communication systems having different operating ranges. The paging capabilities described herein differ from the transmission of conventional network-based (e.g., Uu) paging messages. In some aspects, this disclosure provides techniques for supporting paging for network-based UE-UE communication. The described techniques provide a framework for wireless networks (such as 5G New Radio (NR) networks) to support proximity-based UE-UE communication without requiring the UE to be configured for direct UE-UE communication via a sidelink. For example, network entities can be configured to identify UE-UE paging conditions and identify other network entities (e.g., base stations) to receive paging messages for forwarding to UEs within their service area. The process of identifying network entities and UEs within a paging area and providing paging messages to these devices enables wireless networks to simulate and support proximity-based UE-UE communication in addition to conventional network-based communication. For example, UE-UE paging can be supported not only between UE pairs or groups of UEs (as in network-based paging), but also for UE-UE paging of UEs performing specific applications or an unidentified number of UEs located within a specific geographic area (e.g., within the paging range of the source UE). The improved proximity-based UE-UE communication disclosed herein is provided in a way that efficiently utilizes network resources, particularly by delivering paging messages to base stations and associated UEs within a specific identified paging area, rather than to all base stations and UEs in the network. In some aspects, the disclosed techniques provide V2X paging, distinct from conventional Uu paging, according to some examples of these examples, by implementing a dedicated P-RNTI different from the fixed P-RNTI used for addressing Uu paging, and this dedicated P-RNTI can be configured or broadcast by the network. As another example, the paging timing for proximity-based UE-to-UE paging (such as V2X paging) may differ from that of Uu paging. For instance, the paging timing may be determined based on a V2X-related ID (e.g., Layer 2 destination ID, V2X application ID, etc.) rather than the target UE ID as in Uu paging. The disadvantages of Uu paging mentioned herein are merely representative and are included to highlight the problems the inventors have identified and sought to improve upon in existing devices. Aspects of the device described below address some or all of these disadvantages, as well as other disadvantages known in the art. The improved device aspects described herein may offer additional benefits beyond those described above and can be used in applications other than those described above.

[0029] This disclosure relates throughout to providing or participating in licensed shared access between two or more wireless devices in one or more wireless communication systems (also known as wireless communication networks). In various specific implementations, technologies and apparatus can be used in wireless communication networks such as Code Division Multiple Access (CDMA) networks, Time Division Multiple Access (TDMA) networks, Frequency Division Multiple Access (FDMA) networks, Orthogonal FDMA (OFDMA) networks, Single Carrier FDMA (SC-FDMA) networks, LTE networks, GSM networks, fifth-generation (5G) or new radio (NR) networks (sometimes referred to as “5G NR” networks, systems, or devices), and other communication networks. As described herein, the terms “network” and “system” are used interchangeably.

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

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

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

[0033] Figure 1 This is a block diagram illustrating details of an example wireless communication system according to one or more aspects. The wireless communication system may include a wireless network 100. Wireless network 100 may, for example, include a 5G wireless network. As those skilled in the art will recognize, Figure 1 The components appearing in this network are likely to have corresponding components in other network layouts (including, for example, cellular network layouts and non-cellular network layouts (e.g., device-to-device, peer-to-peer, or self-organizing network layouts)).

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

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

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

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

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

[0039] In operation, at wireless network 100, base stations 105a to 105c use 3D beamforming and cooperative spatial technologies such as Cooperative Multipoint (CoMP) or Multi-Connection to serve UEs 115a and 115b. Macro base station 105d performs backhaul communication with base stations 105a to 105c and the small cell (base station 105f). Macro base station 105d also transmits multicast services subscribed to and received by UEs 115c and 115d. Such multicast services may include mobile TV or streaming video, or may include other services for providing community information, such as weather emergencies or alerts, such as Amber Alerts or Grey Alerts.

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

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

[0042] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 may be an evolved packet core (EPC), which may include at least one Mobility Management Entity (MME), at least one Serving Gateway (S-GW), and at least one Packet Data Network (PDN) Gateway (P-GW). The MME manages non-access stratum (e.g., control plane) functions, such as mobility, authentication, and bearer management of UE 115 served by base station 105 associated with the EPC. User IP packets can be delivered via the S-GW, which itself can connect to the P-GW. The P-GW provides IP address allocation and other functions. The P-GW can connect to network operator IP services. These operator IP services may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched (PS) streaming services.

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

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

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

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

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

[0048] Controllers 240 and 280 can respectively direct operations at base station 105 and UE 115. Controller 240 or other processors and modules at base station 105 or controller 280 or other processors and modules at UE 115 can perform or direct the execution of various processes used in the techniques described herein, in order to perform or direct... Figure 6 Other processes executed or used in the techniques described herein. Memory 242 and 282 may store data and program code for base station 105 and UE 115, respectively. Scheduler 244 may schedule the UE to perform data transmission on the downlink or uplink.

[0049] In some cases, UE 115 and base station 105 may operate in a shared radio spectrum band, which may include licensed or unlicensed (e.g., contention-based) spectrum. In the unlicensed frequency portion of the shared radio spectrum band, UE 115 or base station 105 may conventionally perform a medium sensing procedure to compete for spectrum access. For example, UE 115 or base station 105 may perform a Listen-Before-Speak or Listen-Before-Transmit (LBT) procedure (such as Clear Channel Assessment (CCA)) before communication to determine if a shared channel is available. In some implementations, CCA may include an energy detection procedure to determine if any other active transmission is present. For example, the device may infer that a change in the Received Signal Strength Indicator (RSSI) of the power meter indicates that the channel is occupied. In particular, signal power concentrated in a certain bandwidth and exceeding a predetermined noise floor may indicate another radio transmitter. CCA may also include the detection of a specific sequence indicating channel usage. For example, another device may transmit a specific preamble before transmitting a data sequence. In some cases, the LBT process may include the radio node adjusting its own backoff window based on the amount of energy detected on the channel or the ACK / NACK feedback of packets it transmits (as a manifestation of a collision).

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

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

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

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

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

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

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

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

[0058] As described herein, a node (which may be referred to as a node, network node, network entity, or wireless node) may include, can be, or may include in (e.g., as a component of): a base station (e.g., any base station described herein), a Transmitter Receiver Point (TRP), a UE (e.g., any UE described herein), a network controller, apparatus, device, computing system, Integrated Access and Backhaul (IAB) node, Distributed Unit (DU), Central Unit (CU), Remote Unit (RU), core network, LFM, and / or another processing entity configured to perform any of the techniques described herein. For example, a network node may be a UE. As another example, a network node may be a base station or a network entity. As another example, a first network node may be configured to communicate with a second or third network node. In one aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a UE. In another aspect of this example, the first network node may be a UE, the second network node may be a base station, and the third network node may be a base station. In yet other aspects of this example, the first network node, the second network node, and the third network node may be different from these examples. Similarly, references to UE, base station, device, equipment, computing system, etc., may include disclosures of UE, base station, device, equipment, computing system, etc., as network nodes. For example, a disclosure of a UE being configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node. Consistent with this disclosure, once a particular example is extended according to this disclosure (e.g., a disclosure of a UE being configured to receive information from a base station also discloses that a first network node is configured to receive information from a second network node), a broader example of a narrower example may be interpreted in reverse, but in a broad, open-ended manner. In the above example where a UE is configured to receive information from a base station and a first network node is configured to receive information from a second network node, the first network node may refer to a first UE, a first base station, a first device, a first equipment, a first computing system, a first or more components, a first processing entity, etc., configured to receive information; and the second network node may refer to a second UE, a second base station, a second device, a second equipment, a second computing system, a second or more components, a second processing entity, etc.

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

[0060] Figure 4 This is a block diagram of an example wireless communication system 400 supporting paging for network-based UE-to-UE communication, based on one or more aspects. In some examples, the wireless communication system 400 may implement aspects of the wireless network 100. The wireless communication system 400 includes a UE 115, a second UE 430, an Nth UE 432, one or more base stations 434 (collectively referred to below as "base stations 434"), and a network entity 450. Although three UEs (e.g., UE 115, second UE 430, and Nth UE 432), one base station 434, and one network entity 450 are illustrated, in some other embodiments, the wireless communication system 400 may typically include fewer than or more than three UEs, multiple base stations 434, multiple network entities 450, or combinations thereof. In some embodiments, UEs 115, 430, and 432 may include vehicles, onboard units (OBUs), wireless telephones, tablets, computers, or other devices, any of which may be configured to perform one or more vehicle-to-everything (V2X) communications. Similarly, although referred to as a base station, the functionality of base station 434 can be performed by one or more roadside units (RSUs), one or more communication nodes, or one or more other types of network entities. Although many examples herein are described in the context of V2X communication, this disclosure is not limited thereto, and in other specific implementations, UEs 115, 430, and 432 may include other types of UEs, such as Internet of Things (IoT) devices, that benefit from network-based (e.g., network-assisted) UE-to-UE communication.

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

[0062] Memory 404 includes or is configured to store instructions 405, application 406, and optional location information 408 and paging range 410. Application 406 may include or correspond to an application that performs UE-to-UE paging and messaging, such as an autonomous driving application or other applications that support V2X communication. Application 406 may operate as a 3GPP-based 5G Access and Mobility Function (AMF) that supports the V2X communication described herein. Additional examples of AMF interactions during V2X communication are described in further detail below. In some other implementations, application 406 may be an IoT application or another type of application that supports UE-to-UE paging and messaging. Location information 408 may indicate the location of UE 115. For example, location information 408 may include or correspond to location coordinates, such as latitude and longitude coordinates, Global Positioning System (GPS) coordinates, Global Navigation Satellite System (GNSS) coordinates, or another type commonly referred to as “absolute” location or positioning information. Additionally or alternatively, location information 408 may indicate the relative position of UE 115, such as the location relative to network entity 450 (which may be an NG-RAN node within the paging area surrounding UE 115) and / or UEs 430 and 432, which may be determined by UE 115 by performing one or more positioning operations (e.g., based on the exchanged signal). Location information 408 is referred to as optional because in some implementations, UE 115 may determine location information 408 and provide it to network entity 450, while in some other implementations, other devices (such as base stations or application servers) may determine location information on behalf of UE 115 and provide it to network entity 450. Paging range 410 indicates the paging range (e.g., distance) from UE 115 that UE 115 intends to perform UE-to-UE message transmission. In a V2X-based example, the paging range 410 might be several miles, as UE 115 (e.g., a vehicle) might expect to be able to communicate with any other vehicle or UE within a specific mile radius of UE 115. The paging range 410 is referred to as optional because in some implementations, UE 115 stores the paging range 410 and provides it to network entity 450, while in other implementations, other devices (such as base stations or application servers) may store and provide the paging range 410 on behalf of UE 115, or the paging range 410 may be stored in a configuration file associated with UE 115 that is accessible to network entity 450.

[0063] Transmitter 416 is configured to transmit reference signals, control information, and data to one or more other devices, and receiver 418 is configured to receive reference signals, synchronization signals, control information, and data from one or more other devices. For example, transmitter 416 may transmit signaling, control information, and data to base station 105, and receiver 418 may receive signaling, control information, and data from the base station. In some implementations, transmitter 416 and receiver 418 may be integrated into one or more transceivers. Additionally or alternatively, transmitter 416 or receiver 418 may include or correspond to a reference signal. Figure 2 One or more components of the described UE115.

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

[0065] UEs 430 and 432 may include one or more components as described herein with reference to UE 115. The second UE 430 and the Nth UE 432 may be located within area 436 corresponding to the paging area (e.g., the physical area where UEs 430 and 432 reside), as further described herein. Although in Figure 4In this example, two UEs are exemplified as being included in region 436, but in other embodiments, region 436 may include a single UE or more than two UEs (e.g., N may be greater than or less than three). In some embodiments, UEs 115, 430, and 432 are UEs with 5G capability, UEs with 6G capability, or a combination thereof.

[0066] Network entity 450 may include various components (such as structural components, hardware components) for performing one or more of the functions described herein. For example, these components may include one or more processors 452 (hereinafter collectively referred to as “processor 452”), one or more memory devices 454 (hereinafter collectively referred to as “memory 454”), one or more transmitters 456 (hereinafter collectively referred to as “transmitter 456”), and one or more receivers 458 (hereinafter collectively referred to as “receiver 458”). In some embodiments, network entity 450 may include an interface (e.g., a communication interface) that includes transmitter 456, receiver 458, or a combination thereof. Processor 452 may be configured to execute instructions 460 stored in memory 454 to perform the operations described herein. In some embodiments, processor 452 includes or corresponds to one or more of receive processor 238, transmit processor 220, and controller 240, and memory 454 includes or corresponds to memory 242.

[0067] Memory 454 includes or is configured to store instructions 460, source UE location 462, paging area 464, identified network entity 466, and optional map data 468 and UE profile 469. Source UE location 462 indicates the location of the source UE from which the identified UE-to-UE paging condition originates. Paging area 464 indicates the area to which a paging message is to be transmitted based on the identified UE-to-UE paging condition, and may correspond to area 436. Paging area 464 may be determined based on source UE location 462 and paging range 410, as further described below. Identified network entity 466 indicates one or more network entities located within paging area 464. Map data 468 includes one or more area maps that include the locations of UEs to be received by UE-to-UE paging within paging area 464 (e.g., area 436). The map may indicate the location of other features, such as roads, geographical features, structures, objects, regional divisions (e.g., rooms, properties, towns, cities, states, countries, etc.), network entities within the wireless communication system 400, other features, or combinations thereof. The UE profile 469 may include one or more UE profiles indicating information associated with applications supported at various UEs that support UE-to-UE paging, such as whether UE-to-UE paging is supported, the associated paging range, other information, or combinations thereof.

[0068] Transmitter 456 is configured to transmit reference signals, synchronization signals, control information, and data to one or more other devices, and receiver 458 is configured to receive reference signals, control information, and data from one or more other devices. For example, transmitter 456 may transmit signaling, control information, and data to UE 115, and receiver 458 may receive signaling, control information, and data from the UE. In some implementations, transmitter 456 and receiver 458 may be integrated into one or more transceivers. Additionally or alternatively, transmitter 456 or receiver 458 may include or correspond to a reference signal. Figure 2 One or more components of the described base station 105.

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

[0070] Base station 434 may include network entity 450 as referenced herein or Figures 1 to 3 The base station 105 describes one or more components. The base station 434 may be located within an area 436 corresponding to the paging area (e.g., the physical area where UEs 430 and 432 reside), as further described herein. For example, the base station 434 may support one or more cells where UEs 430 and 432 reside. Although in Figure 4While illustrated as a single unit, base station 434 may include two or more base stations. In some implementations, base station 434 is a 5G-enabled base station, a 6G-enabled base station, or a combination thereof.

[0071] In some implementations, the wireless communication system 400 implements a 5G NR network. For example, the wireless communication system 400 may include multiple 5G-capable UEs 115, 430, and 432, as well as multiple 5G-capable network entities 450 and base stations 434, such as UEs, base stations, servers, etc., configured to operate according to 5G NR network protocols such as those defined by 3GPP. In some other implementations, the wireless communication system 400 implements a 6G network.

[0072] During the operation of the wireless communication system 400, network entity 450 may identify UE-to-UE paging request conditions originating from a source UE (such as UE 115). UE-to-UE paging conditions may indicate that application 406, executing at UE 115, intends to perform proximity-based UE-to-UE measurements, such as by actively requesting paging message reception or providing actual UE message reception, while one or more other conditions indicating a paging request for message reception also exist. For example, UE-to-UE paging request conditions may be associated with application 406, executing at UE 115 and similarly at UEs 430 and 432. In some specific implementations, application 406 is related to vehicle performance, such as navigation applications, autonomous driving applications, pedestrian safety applications, or another type of application that implements and supports wireless communication to and from vehicles, such as vehicle-to-vehicle (V2V) communication or vehicle-to-everything (V2X) communication. Thus, UE-to-UE paging request conditions may be V2X paging conditions or V2V paging conditions. V2X communication can be primarily proximity-based. For example, a key use case for V2X is enhanced situational awareness, and therefore, only nearby vehicles are likely relevant to most V2X communications. Furthermore, different V2X communication applications may have different range requirements. For instance, a Cooperative Awareness Message (CAM) might have a range requirement of 300 meters, while a highway traffic congestion warning might have a range requirement of 1000 meters. Additionally, sidelink-based V2X communication features distance-based reliability (such as distance-based negative acknowledgment (NACK)) and utilizes transmit adaptation (e.g., modulation and decoding scheme (MCS) selection, different repetition counts, etc.) to meet varying range and other service requirements. To support network-based V2X communication, paging may be required, including paging one or more V2X-capable UEs, as further described herein, to receive V2X transmissions or join V2X groups or sessions in the downlink (DL).

[0073] In some aspects, the UE may have specific interactions with the AMF, and those interactions can be supported by multi-access edge computing (MEC) deployments or generic edge servers in the network. For example, an MEC deployment may communicate requests or commands to parts of the network, such as the AMF and / or the UE. In some aspects, an MEC deployment may specify use case scenarios, and the AMF may translate these use cases into specific V2X paging parameters. For example, an MEC deployment or other edge server may receive information from a UE (such as a V2X source UE), such as desired range requirements, and based on this, the MEC deployment or other edge server may determine the paging area and control NG-RAN nodes accordingly. In another example, an MEC deployment or other edge server may determine the paging area based on known characteristics or network conditions of the V2X source UE, the location of other UEs, etc. Use cases based on those parameters and corresponding paging areas can be determined, and NG-RAN nodes can be controlled according to the paging areas. The MEC deployment or edge server may communicate with NG-RAN nodes via the AMF (such as via the UPF and SMF). MEC deployments or edge servers may additionally or alternatively transmit paging requests to individual V2X source UEs or other UEs, such as via AMF relay paging requests, which specify the source UE ID (e.g., V2X Layer 2 source ID), destination UE ID (e.g., 5G-S-TMSI), V2X Layer 2 destination ID, V2X application ID, and / or V2X group ID. The use cases determined by the MEC deployment or edge server in these respects may be based on any information available at the source or destination UE in the following examples.

[0074] V2X paging can differ from typical network-based paging, such as the fact that V2X paging does not have a specific destination UE and the paging area used for V2X paging is physically limited. Therefore, the range-based tracking and UE-to-UE paging and message sending / receiving described herein are well-suited to support network-based V2X communication. In other specific implementations, application 406 could be an IoT application performing proximity-based UE-to-UE paging and message sending / receiving. These examples are not limiting, and in other specific implementations, application 406 could be any type of application performing proximity-based UE-to-UE communication.

[0075] UE-to-UE paging conditions can be actively indicated by UE 115 (e.g., the source UE), passively indicated by UE 115, or enabled by the network (e.g., at network entity 450). In a specific implementation of actively indicating UE-to-UE paging conditions, application 406 is configured to cause UE 115 to generate a UE-to-UE paging request 470 and send that UE-to-UE paging request to network entity 450. Network entity 450 can identify UE-to-UE paging conditions by receiving a UE-to-UE paging request 470 with UE 115 as the source UE. The UE-to-UE paging request 470 can indicate a request to perform paging for an upcoming message from UE 115. For example, the UE-to-UE paging request 470 can indicate a destination UE, destination UE group, destination application, or broadcast indicator as the expected target for paging and the upcoming message. In some implementations, similar to other network-based paging and messaging schemes, a UE-to-UE paging request 470 may include a device identifier (ID) or other identifier of the destination UE (such as the second UE 430) or a group ID corresponding to a destination UE group (such as the group including the Nth UE 432). In other implementations, a UE-to-UE paging request 470 may include an application ID indicating an application (e.g., application 406) performed by the destination UE, or an application group ID indicating a UE group within the context of that application. In other examples, a UE-to-UE paging request 470 may include a broadcast indicator indicating that an upcoming message will be broadcast to all UEs within a specific range of UE 115. Additionally or alternatively, a UE-to-UE paging request 470 may include information for determining the recipient of the paging or messaging (as further described below), location information associated with UE 115 (e.g., the source UE), paging range 410, or both.

[0076] In a specific implementation of passively instructing UE-to-UE paging conditions, UE 115 may provide information for determining the paging recipient, and such information may be identified as a UE-to-UE paging condition by network entity 450. For example, network entity 450 may receive location information associated with UE 115 (e.g., the source UE), paging range 410, or both, and receipt of either or both of such information may be interpreted by network entity 450 as a request for proximity-based UE-to-UE paging of UE 115. This information may be received directly from UE 115, or from one or more other network entities (such as base station 434) serving the cell where UE 115 resides, or from an application server associated with application 406. In a specific implementation where network-enabled UE-to-UE paging conditions are implemented, network entity 450 may identify the paging condition in response to receiving a general paging request or message to be sent to another UE, based on information stored in a configuration file associated with that UE (such as the configuration file associated with application 406). For example, to determine whether a UE-to-UE paging condition has been identified when network entity 450 receives a paging request originating from UE 115, network entity 450 may access UE profile 469 to determine whether UE 115 or an application running at UE 115 requests proximity-based UE-to-UE paging and messaging. For example, UE profile 469 may include or correspond to a V2X Quality of Service (QoS) profile associated with application 406. In some implementations, if UE profile 469 indicates that UE 115 requests proximity-based UE-to-UE paging and messaging, UE profile 469 may also indicate a paging range 410, so that UE 115 does not need to report the paging range 410 to network entity 450.

[0077] In response to identifying paging conditions, network entity 450 may identify one or more other network entities within a paging area associated with the location of the source UE. For example, network entity 450 may determine a source UE location 462 (e.g., the location of UE 115) and a paging range 410 (e.g., the maximum range within which UE 115 is configured to transmit UE-to-UE messages), and network entity 450 may determine a paging area 464 based on the source UE location 462 and the paging range 410. As an example, paging area 464 may be a circle centered on the location of UE 115 with a radius equal to that of paging range 410. In other implementations, paging area 464 may have a different shape or may be defined in different ways, such as a rectangle or semicircle facing one direction toward UE 115, representing the area where UE 115 is configured to perform UE-to-UE communication.

[0078] In some implementations, UE 115 (e.g., the source UE) may report location information 408, paging range 410, or both to network entity 450. For example, network entity 450 may receive a report message including location information 408, and network entity 450 may determine the source UE's location 462 based on location information 408. In some implementations, the report message includes or corresponds to a Radio Resource Control (RRC) message, and the report message may be received directly from UE 115 or from a serving base station (or other network entity) associated with UE 115. Alternatively, an application server (such as a V2X application server) associated with application 406 may provide a report message including location information 408, paging range 410, or both to network entity 450. In some other implementations, location information 408 may be provided in other message transmissions from UE 115, and network entity 450 may extract location information 408 from such non-report message transmissions. As an example, network entity 450 may receive one or more user data packets originating from UE 115 and including location information 408. These user data packets may be addressed to other UEs, such as UE 430 or 432. Network entity 450 may extract the location information 408 from the received user data packets and use the extracted location information to determine the source UE location 462. This extraction of location information 408 is possible in specific implementations where application 406 and network entity 450 are associated with the same entity, enabling network entity 450 to decode and extract information, or if the user data packets are not encoded at a higher layer or not encrypted in a manner that network entity 450 cannot decode or decrypt. In such implementations, user data packets may be forwarded over the network to an application server, and the application server may extract the location information 408 and report it to network entity 450, thereby protecting the privacy and security of application data.

[0079] In some other implementations, network entity 450 may determine or infer the location of UE 115 based on the location of other devices. For example, network entity 450 may determine the source UE location 462 based on the location of a base station serving UE 115 or other network entities. One technique for identifying which base station serves UE 115 is to have the network entity identify the base station providing the UE-to-UE paging request 470 (if such request is not directly from UE 115). Alternatively, when UE 115 is attached to a cell served by a base station, UE 115 may transmit a cell attachment message to network entity 450. The cell attachment message may indicate the cell identifier (ID) of the cell to which UE 115 is attached, and network entity 450 may identify the base station associated with that cell to determine the source UE location 462 based on the location of the identified base station (or the indicated cell). Alternatively, when UE 115 is associated with a base station, the base station may transmit an association message to network entity 450. The association message may indicate the base station associated with UE 115, such as by including the base station ID and the ID of UE 115. Upon receiving the association message, network entity 450 may determine the source UE location 462 based on the location of the identified base station (or other network entity). Alternatively, network entity 450 may receive one or more user data packets indicating the UE identifier (ID) of UE 115 and the network entity ID of the serving base station, and network entity 450 may extract these IDs and determine the source UE location 462 based on the location of the identified base station. As described above, this extraction is only possible in implementations where the user data packets are not encoded at a higher level or are not encrypted in a manner that network entity 450 cannot decode or decrypt. In such implementations, user data packets can be forwarded over the network to an application server, and the application server can extract these IDs and provide them to network entity 450, thereby protecting the privacy and security of application data.

[0080] Similar to location information 408, paging range 410 may be provided to network entity 450 or otherwise determined by the network entity to enable the determination of paging area 464. In some embodiments described above, UE-to-UE paging request 470 includes paging range 410. Alternatively, network entity 450 may receive configuration message 478 originating from UE 115 (e.g., the source UE) and indicating paging range 410. In some embodiments, configuration message 478 may be received from UE 115 (or from another network entity, such as a base station, that forwards configuration message 478 to network entity 450). In some other embodiments, configuration message 478 may be received from an application server associated with application 406. In other embodiments, network entity 450 may access UE profile 469 to determine paging range 410 associated with UE 115 based on identifying UE-to-UE paging conditions.

[0081] After identifying paging area 464, network entity 450 may identify one or more cells or tracking areas intersecting with paging area 464 to identify the base station (or other network entity) to provide paging signals to UEs within range. For example, map data 468 or other data accessible to network entity 450 may indicate the geographic location of a cell or other tracking area served by a base station within wireless communication system 400, and network entity 450 may identify the base station (or other network entity) associated with a cell or other tracking area intersecting (e.g., overlapping) with paging area 464. As a specific example, base station 434 may serve cells intersecting with or overlapping with area 436 (e.g., the geographic area represented by paging area 464), and therefore the identified network entity 466 includes base station 434. Base station 434 may serve UEs 430 and 432, etc.

[0082] In some implementations, identifying the paging area 464 can be a multi-step process, including identifying possible areas and identifying the paging area 464, and refining the paging area 464 into overlaps or intersections with possible areas. In some examples, network entity 450 may determine possible areas based on map data 468, UE information associated with UE 115, application information associated with application 406, or a combination thereof. For example, and in the context of V2X communication, some types of messages may only be sent to UEs in front of the moving vehicle (e.g., in the direction the vehicle is traveling), and in such implementations, possible areas may include areas in front of UE 115 but not behind UE 115. Therefore, the intersection of this possible area (e.g., in front of UE 115) and a circular paging area centered on the location of UE 115 may be an approximate semicircle centered on UE 115 and extending in front of and to the sides of UE 115. Similarly, some messages may only be sent behind the vehicle, and therefore, paging area 464 can be refined to remove portions in front of UE 115. Other examples include areas based on location or geographic features, such as narrowing the paging area to only cover cells that cover a road if only one road is located within the original paging area. Other examples are possible, such as areas where UEs are not permitted to pass through or enter, areas with geographic features that prevent UE passage, etc. In these examples, the identified network entity 466 (e.g., base station 434) includes only network entities located in both the initial paging area and the determined “possible areas.” In some other implementations, instead of network entity 450 identifying the possible areas to refine paging area 464, the application server associated with application 406 determines the possible areas and provides them to network entity 450. See below for reference. Figure 5B and Figure 5CAdditional details describing the operation of this application server.

[0083] After identifying the identified network entity 466, network entity 450 may send one or more paging messages 472 (hereinafter collectively referred to as "paging messages 472") to the identified network entity 466 according to the UE-to-UE paging request conditions. Figure 4 In the example shown, network entity 466, representing base station 434 located in region 436, transmits paging message 472 to base station 434 for delivery to UEs 430 and 432 within the associated serving cell. Paging message 472 may include a source UE identifier (ID), a source application ID, or both, to indicate the source of the paging. Additionally or alternatively, paging message 472 may include a destination UE ID, a destination group ID, or a destination application ID to indicate the destination UE to which paging message 472 is to be received. Alternatively, paging message 472 is designated as a broadcast message to be broadcast by base station 434. In some embodiments, paging message 472 is designated as being transmitted by base station 434 via the paging control channel (PCCH). In some other embodiments, paging message 472 is designated as being transmitted by base station 434 via the physical downlink control channel (PDCCH) as downlink control information (DCI). Additionally or alternatively, paging message 472 may be communicated in a manner different from other network-based non-UE to UE paging. For example, paging message 472 may include a first Paging-Radio Network Temporary Identifier (P-RNTI), which is different from the second P-RNTI associated with non-UE to UE paging. As another example, paging message 472 may be transmitted via a channel with a different frequency or at a different time period compared to paging messages used for non-UE to UE paging, which may be configured by network entity 450 or another component of wireless communication system 400.

[0084] After transmitting paging message 472 to base station 434 serving UEs 430 and 432, network entity 450 may receive UE-to-UE message 474 from UE 115. UE-to-UE message 474 is a message to be transmitted to the paged UE. In response to receiving UE-to-UE message 474, network entity 450 may forward UE-to-UE message 474 as DL message 476 to base station 434 (e.g., another network entity) for transmission to UEs 430 and 432.

[0085] For reference Figure 4As described, this disclosure provides techniques for supporting paging for network-based UE-UE communication. The described techniques provide a framework for a wireless communication system 400 to support proximity-based UE-UE communication without requiring UEs to be configured for direct UE-UE communication via sidelinks. For example, network entity 450 may be configured to identify UE-UE paging conditions originating from UE 115 (e.g., UE 115 is the source UE) and to identify other network entities (e.g., base stations) to receive paging messages for forwarding to UEs 430 and 432 within their service area. For example, network entity 450 may determine a paging area 464 corresponding to area 436, and network entity 450 may identify one or more base stations (e.g., other network entities) serving cells or other coverage areas intersecting with area 436. This process of identifying network entities and UEs within paging area 464 and providing paging messages 472 to such devices enables the wireless communication system 400 to simulate and support proximity-based UE-UE communication in addition to conventional network-based communication. For example, it can support not only UE-to-UE paging between UE pairs or UE groups (such as in network-based paging), but also UE-to-UE paging for UEs performing a specific application (e.g., application 406) or for an unidentified number of UEs located within a specific geographical area (e.g., within the paging range 410 of UE 115). The improved proximity-based UE-to-UE communication described above is provided in a way that efficiently utilizes network resources, particularly by delivering paging messages 472 to base stations and associated UEs within a specific identified paging area, rather than to all base stations and UEs in the network.

[0086] Figures 5A to 5C This is a block diagram of an example wireless communication system 500 supporting paging for network-based V2X communication, based on one or more aspects. The wireless communication system 500 includes UEs 115 and 502-508, base stations 510-516, one or more management servers (referred to herein as "management server 520"), and an application server 530. Base station 510 serves the cell where UE 115 is located, base station 512 serves the cells where UEs 502 and 504 are located, base station 514 serves the cell where UE 506 is located, and base station 516 serves the cell where UE 508 is located. Although in Figures 5A to 5C The diagram shows five UEs and four base stations, but in other specific implementations, the wireless communication system 500 may include fewer or more than five UEs, fewer or more than four base stations, or combinations thereof. Although UEs 115 and 502-508 are... Figures 5A to 5CWhile UEs 115 and 502-508 are exemplified as vehicles and described herein in the context of V2X communication, in other implementations, UEs 115 and 502-508 may be other types of UEs (such as smartphones carried by pedestrians) or other types of UEs (such as IoT devices) that support proximity-based UE-to-UE communication. Additionally or alternatively, although described as base stations 510-516, in other implementations, one or more of base stations 510-516 may be other types of network entities, such as access points, RSUs, servers, communication nodes, etc.

[0087] Figure 5A An example is illustrated where a UE is configured to provide location information and paging range to the network. For example, UE 115 can report location information 540 to the network, UE 502 can report location information 542 to the network, UE 504 can report location information 544 to the network, UE 506 can report location information 546 to the network, and UE 508 can report location information 548 to the network. In some specific implementations, such as Figure 5A As shown, UE 115 and 502-508 generate location information 540-548 and transmit it to base stations 510-516, which then forward the location information 540-548 to management server 520. In some other embodiments, UE 115 and 502-508 generate location information 540-548 and transmit it directly to management server 520. Location information 540-548 may include positioning coordinates determined by a GPS or GNSS receiver, location information determined by a positioning operation performed by a device within the wireless communication system 500, other positioning or location information, or combinations thereof. Location information 540-548 may be transmitted via the control plane, such as via report message transmission. For example, UE 115 may transmit location information 540 as an RRC message to base station 510, and base station 510 may forward location information 540 to management server 520 via N2 signaling. As another example, UE 115 can directly transmit location information 540 to management server 520 via N1 signaling. Alternatively, location information 540-548 can be transmitted via the user plane and retrieved by management server 520, as shown in the reference. Figure 4As explained above, location information 540-548 may typically be included in a V2X application message, and management server 520 may be able to parse the V2X application message and extract location information 540. In some such implementations, different functionalities may be performed by different servers within management server 520, such that the User Plane Function (UPF) receives user plane messages and extracts location information 540-548, and transmits location information 540-548 to the Session Management Function (SMF) via N4 signaling, and the SMF transmits the location information to the Access and Mobility Management Function (AMF) via N11 signaling (all of which may be performed by management server 520, base stations 510-516, other network entities, or a combination thereof). The AMF, SMF, and UMF described above are the destination UE's AMF, SMF, and UMF, which may be located at the same or different servers as UE 115 (e.g., the source UE).

[0088] In addition to transmitting location information 540, UE 115 can also transmit paging range 541 to the network. In some specific implementations, such as Figure 5A As shown, UE 115 transmits paging range 541 to base station 510, and base station 510 forwards paging range 541 to management server 520. In some other implementations, UE 115 transmits paging range 541 directly to management server 520, or management server 520 is able to determine paging range 541, such as by accessing the UE profile associated with UE 115. Paging range 541 may be included in configuration messages from UE 115 or some other type of signaling.

[0089] To initiate a UE-to-UE paging request for an upcoming UE-to-UE message, UE 115 transmits a UE-to-UE paging request 590 to the network. In other words, a network entity (e.g., management server 520) may receive a UE-to-UE paging request 590 originating from UE 115 (e.g., the source UE). Figure 5A In the example shown, UE 115 transmits a UE-to-UE paging request 590 to base station 510, and base station 510 forwards the UE-to-UE paging request 590 to management server 520. Although location information 540, paging range 541, and UE-to-UE paging request 590 are shown as separate messages, in some other implementations, location information 540, paging range 541, or both may be included in the UE-to-UE paging request 590, as referenced above. Figure 4 As described above, a UE-to-UE paging request 590 can indicate a destination UE, destination UE group, destination application, destination application group, or broadcast indicator, as referenced above. Figure 4 As described.

[0090] After receiving a UE-to-UE paging request 590, the management server 520 can determine the paging area to be paging. For example, the paging area can be determined as a circular or other shaped area centered on the location of UE 115 and extending to the paging range 541, as referenced above. Figure 4 As described. In Figure 5A In this context, the paging area can cover area 501. To determine which devices should receive paging messages, management server 520 can determine which cells (or other tracking areas) intersect with area 501, and the base stations associated with those cells can be identified as targets for receiving paging messages. Figure 5A In the example shown, the cells associated with base stations 512-516 intersect with region 501, and therefore base stations 512-516 can be identified as destination network entities by management server 520. Although the paging area is described as being determined based on cells, in other specific implementations, the paging area may be determined based on other tracking areas, the location of network nodes, or other location-related information.

[0091] As described above, in some implementations, the paging area can be further refined by identifying the intersection between the initially determined paging area (e.g., based on paging range 541 and the location of UE 115) and possible areas determined based on other factors. For example, in area 501, if the cells associated with base stations 512 and 514 cover the same road traveled by UE 115, and base station 516 does not cover that road but covers other roads not connected to it, then the possible area may correspond to the road traveled by UE 115 (or the road connected to it). In this example, management server 520 can access map data including road layout to determine that the possible area does not intersect with the cell associated with base station 516, and therefore, the intersection of the possible area with the initial paging area results in base station 516 and the associated cell being excluded from the refined paging area. In other examples, other conditions or parameters besides road location can be similarly used to refine the initial paging area determination, such as the direction from which UE 115 will perform message transmission and reception, inaccessible areas within area 501, etc. Reducing the number of network entities transmitting paging messages reduces network overhead and network congestion associated with network-based UE-to-UE paging that supports proximity-based communication.

[0092] After identifying base stations or other network entities within the paging area, management server 520 may transmit paging message 592 to the identified base stations. For example, management server 520 may transmit paging message 592 to base stations 512 and 514 for delivery to UEs within their associated cells. For instance, base station 512 may transmit paging message 592 to UEs 502 and 504, and base station 514 may transmit paging message 592 to UE 506. Since base station 516 is excluded from the paging area because its associated cell does not intersect with a possible area (e.g., the road traveled by UE 115), management server 520 does not transmit paging message 592 to base station 516 for delivery to UE 508. Although described and illustrated as management server 520 transmitting paging message 592 to base stations 512-514, management server 520 may instead transmit control signaling to cause base stations 512-514 to send paging message 592 (i.e., the paging message is not transmitted between management server 520 and any base stations). As explained above, paging message 592 may be addressed to a single destination UE, a group of destination UEs, a destination application, a group of destination applications, or all UEs receiving the message (e.g., paging message 592 may be a broadcast message), as indicated by UE-to-UE paging request 590. In some implementations, paging message 592 may include additional information related to V2X communication or other types of proximity-based UE-to-UE communication, such as priority level, quality of service identifier (“5QI”), other parameters, or combinations thereof. Upon receiving paging message 592, UEs 502-506 may process paging message 592 to determine whether to monitor subsequent messages originating from UE 115.

[0093] The format and / or transmission of paging message 592 may differ from the transmission of typical network-based (e.g., Uu) paging messages. As an example, the DCI that schedules the PDSCH to carry paging message 592 may be addressed by a dedicated P-RNTI, which is different from the fixed P-RNTI used to address Uu paging, and the dedicated P-RNTI may be configured or broadcast by the network (e.g., by management server 520). As another example, the paging timing for proximity-based UE-to-UE paging (such as V2X paging) may differ from Uu paging; for example, the paging timing may be determined based on a V2X-related ID (e.g., Layer 2 destination ID, V2X application ID, etc.) rather than the target UE ID as in Uu paging. As described above, paging message 592 can be addressed in several different ways. In one example, paging message 592 may be source-destination specific (i.e., each paging message uses a pair of Layer 2 source IDs and Layer 2 destination IDs). In another example, paging message 592 can be destination- or application-specific (i.e., each paging message is for a single Layer 2 destination ID or a single V2X application ID). In yet another example, paging message 492 can be for more than one source-destination pair, more than one destination, or more than one V2X application. Configuration for such V2X or other proximity-based UE-to-UE paging can be provided by management server 520 (e.g., the network), and this configuration may include setting the time and frequency resource locations for paging transmission (e.g., paging frames), RNTI addressing, DCI scheduling of paging messages, etc. In some implementations, base stations 512-514 can transmit paging message 592 via PCCH. In some implementations, base stations 512-514 can transmit paging message 592 in the DCI via PDCCH. UEs 502-506 can determine whether paging message 592 is relevant based on information carried in paging message 592, such as a Layer 2 source ID, a Layer 2 destination ID, an application ID, or a combination thereof. If the UE determines that paging message 592 is relevant, the UE may continue with the next communication process, such as switching from sleep mode or low-energy mode (e.g., Connection Management Idle (CM Idle) mode) to active operation mode (e.g., CM Connection mode).

[0094] Figure 5B An example is illustrated where application server 530 is configured to provide information to the network to enable network-supported proximity-based UE-to-UE paging. Application server 530 is associated with applications that support proximity-based UE-to-UE paging and message passing (such as V2X applications). For example, application server 530 may be associated with... Figure 4This is related to application 406. To illustrate the operation of application server 530 in providing information, instead of UEs 115 and 502-508 reporting location information to the network (e.g., to management server 520), application server 530 can provide location information 550 associated with one or more of UEs 115 and 502-508. In some implementations, UEs 115 and 502-508 may report location information (such as higher-layer signaling that is not decryptable by management server 520) to application server 530, and application server 530 maintains a location database and updates management server 520 via the transmission of location information 550. Alternatively, location information may be included in user plane data passed from UEs 115 and 502-508 to application server 530, and application server 530 may extract various location data and transmit it as location information 550 to management server 520.

[0095] As a supplement to or alternative to transmitting location information 550, application server 530 may transmit paging range 552 to management server 520 to enable network-based UE-to-UE paging of UE 115. In some implementations, paging range 552 may be transmitted as part of a configuration message or a configuration setup process between application server 530 and management server 520. In some other implementations, application server 530 may receive a UE-to-UE paging request originating from UE 115, and application server 530 may transmit paging range 552 after selecting an appropriate paging range based on the type of communication requesting paging. For example, UE 115 may transmit a UE-to-UE paging request 590 to the network (similar to reference...). Figure 5A As described above, the UE-to-UE paging request 590 can be forwarded to both the management server 520 and the application server 530. The application server 530 can be configured to analyze the information in the UE-to-UE paging request 590 to determine the paging range 552 and provide that paging range to the management server 520. After the management server 520 receives and processes the UE-to-UE paging request 590 or otherwise identifies the UE-to-UE paging request, the management server 520 can determine the paging area based on the location information 550 and the paging range 552, and the management server 520 can initiate a paging message 592 sent by base stations 512-514 (e.g., network entities identified as being within the paging area), as referenced above. Figure 5A As described. In some specific implementations, possible areas (e.g., the roads UE 115 travels on and connects to) may be determined and identified by application server 530 and provided to management server 520 for refining the paging area, as referenced above. Figure 5A As described.

[0096] Figure 5CAn example is illustrated where the network determines location information based on message transmissions from the UE or an associated base station. In some specific implementations, instead of transmitting location information 540-548 to the network, UEs 115 and 502-508 may transmit other message transmissions indicating the associated base station, and the management server 520 may determine the location of UEs 115 and 502-508 based on the location of the associated base station. For example, UEs 115 and 502-508 may transmit cell attachment messages 560-568, indicating the cell ID of the cell to which UEs 115 and 502-508 are attached. Specifically, UE 115 may transmit cell attachment message 560 after completing the attachment process with base station 510; UEs 502 and 504 may transmit cell attachment messages 562 and 564 respectively after completing their respective attachment processes with base station 512; UE 506 may transmit cell attachment message 566 after completing the attachment process with base station 514; and UE 508 may transmit cell attachment message 568 after completing the attachment process with base station 516. Management server 520 may determine the serving base station associated with the cell where UEs 115 and 502-508 reside based on cell attachment messages 560-568. These cell attachment messages can be used to estimate the location of UEs 115 and 502-508. For example, UE 115 may transmit cell attachment message 560 including the cell ID associated with base station 510, and management server 520 may estimate the location of UE 115 based on the known locations of base station 510 and associated cells. As another example, UEs 502 and 504 may transmit cell attachment messages 562 and 564 respectively, each cell attachment message including a cell ID associated with base station 512, and management server 520 may estimate the location of UEs 502 and 504 based on the known location of base station 512 and the associated cell.

[0097] In some other implementations, management server 520 may determine the location of UEs 115 and 502-508 based on messages originating from base stations 510-518. For example, base station 510 may transmit association message 570 upon successful completion of the association process with UE 115, and association message 570 may indicate the cell ID or other ID associated with base station 510 and the UE ID associated with UE 115, thereby enabling management server 520 to determine that UE 115 is located within the cell or other tracking area associated with base station 510. Similarly, base station 512 may transmit association message 572 upon successful completion of the association process with UEs 502 and 504, base station 514 may transmit association message 574 upon successful completion of the association process with UE 506, and base station 516 may transmit association message 576 upon successful completion of the association process with UE 508. The management server 520 can estimate the location of UEs 115 and 502-508 based on the association messages 570-576, which can be used to identify which base stations should send paging messages to their associated UEs.

[0098] In some specific implementations, the paging area can be determined based on the paging range 541 received from UE 115, as referenced above. Figure 5A As described above. In some other specific implementations, this determination may be based on the paging range 552 received from the application server 530, as referenced above. Figure 5B As described above. Additionally or alternatively, the management server 520 may further refine the paging area based on information exported from map data or received from the application server 530. Although Figure 5C The example shown illustrates UE 115 transmitting a UE-to-UE paging request 590. However, in some other implementations, the management server 520 may identify UE-to-UE paging conditions based on more passive conditions, such as receiving location information associated with UE 115 and paging range 541 or paging range 552, as referenced above. Figure 4 As described.

[0099] Figure 6 This is a flowchart illustrating an example process 600 for paging in network-based UE-to-UE communication, supported by one or more aspects. The operation of process 600 can be performed by network entities (such as those mentioned above). Figures 1 to 3 The described base station 105, as mentioned above (reference). Figure 4 The described network entity 450, referenced above. Figures 5A to 5C The management server 520 described above (see reference above) Figures 5A to 5C The base stations described are 510, 512, 514, and 516, or as referenced above. Figure 7The network entity described is used to perform this operation. For example, the example operation of process 600 enables network entity 450 to support paging for network-based UE-to-UE communication.

[0100] In box 602, the network entity identifies the UE-to-UE paging request status originating from the source UE. For example, UE-to-UE paging request conditions may include or correspond to Figure 4 UE to UE paging request 470 or as mentioned above Figure 4 and Figures 5A to 5C Other identified conditions described, and the source UE may include or correspond to Figure 4 UE 115. In some specific implementations, UE-to-UE paging request conditions are associated with an application executed by the source UE (such as, specifically, the V2X application that generates the V2X paging conditions).

[0101] In box 604, the network entity identifies one or more other network entities within a paging area relative to the location of the source UE. For example, a paging area may include or correspond to Figure 4 The paging area 464, and one or more other network entities may include or correspond to serving the paging area 464. Figure 4 Network entities of UE 430 and 432.

[0102] At box 606, a network entity sends one or more paging messages to one or more other network entities based on UE-to-UE paging request conditions. For example, one or more paging messages may include or correspond to Figure 4 Paging message 472.

[0103] In some specific implementations, identifying the conditions for a UE-to-UE paging request includes receiving a UE-to-UE paging request originating from the source UE. For example, a UE-to-UE paging request may include or correspond to Figure 4 UE-to-UE paging request 470. In some such implementations, the UE-to-UE paging request indicates the location of the source UE, the paging range associated with the paging area, or both. Additionally or alternatively, the UE-to-UE paging request may indicate the destination UE, the destination UE group, the destination application, or a broadcast indicator.

[0104] In some specific implementations, identifying a UE-to-UE paging request includes receiving location information associated with the source UE, a paging range associated with the paging area, or both. For example, the location information may include or correspond to... Figure 4 Location information 408, and the paging range may include or correspond to Figure 4The paging range is 410. In some other implementations, identifying a UE-to-UE paging request includes receiving a paging request originating from a source UE and accessing a profile associated with the source UE to determine whether the source UE is associated with the UE-to-UE paging. For example, the profile may include or correspond to Figure 4 UE configuration file 469.

[0105] In some specific implementations, process 600 further includes receiving a report message that includes location information associated with the source UE, and identifying the location of the source UE based on the location information. For example, the report message may include or correspond to Figure 5A Location information 540. In some such implementations, the report message includes or corresponds to an RRC message received from a serving network entity associated with the source UE. Alternatively, the report message may include or correspond to an RRC message received from the source UE. Additionally or alternatively, the UE-to-UE paging request condition may be associated with an application executed by the source UE, and the report message may include or correspond to a message received from an application server associated with the application. For example, the report message may include or correspond to... Figure 5B Location information 550.

[0106] In some specific implementations, process 600 further includes receiving one or more user data packets originating from a source UE, extracting location information associated with the source UE from the one or more user data packets, and identifying the location of the source UE based on the location information. For example, network entity 450 may receive one or more user data packets originating from UE 115, and, based on (e.g., by network entity 450 or by...) Figures 5A to 5C The application server 530 extracts information from user data packets to determine the location of the source UE 462.

[0107] In some specific implementations, identifying UE-to-UE paging request conditions includes receiving UE-to-UE paging requests from different network entities. For example, a UE-to-UE paging request may include or correspond to... Figure 5A The UE to UE paging request 590. In such a specific implementation, process 600 may also include identifying the location of the source UE based on the location of different network entities. For example, the location of different network entities may include or correspond to Figure 5A The location of base station 510.

[0108] In some implementations, process 600 further includes receiving a cell attachment message associated with the source UE. The cell attachment message indicates the cell ID of the cell to which the source UE is attached. For example, the cell attachment message may include or correspond to... Figure 5CCell attachment message 560. In such embodiments, process 600 further includes identifying the serving network entity associated with the cell and identifying the location of the source UE based on the location of the serving network entity. In some embodiments, process 600 further includes receiving an association message associated with the source UE. The association message indicates the serving network entity to which the source UE is attached. For example, the association message may include or correspond to Figure 5C The associated message 570. In this specific implementation, process 600 also includes identifying the location of the source UE based on the location of the serving network entity.

[0109] In some implementations, process 600 further includes receiving one or more user data packets indicating the UE ID of the source UE and the network entity ID of the serving network entity of the source UE, and identifying the location of the source UE based on the location of the serving network entity. For example, network entity 450 may receive one or more user data packets originating from UE 115, and based on (e.g., by network entity 450 or by...) Figures 5A to 5C The application server 530 extracts the network entity ID from the user data packet to determine the source UE location 462.

[0110] In some implementations, process 600 also includes receiving a configuration message originating from the source UE. The configuration message indicates the paging range associated with the paging area. For example, the configuration message may include or correspond to... Figure 4 Configuration message 478. In such an implementation, process 600 further includes identifying a paging area based on the paging range and the location of the source UE. For example, the paging range may include or correspond to the paging range 410 carried by configuration message 478. In some other implementations, process 600 further includes receiving a configuration message from an application server associated with an application at the source UE. The configuration message indicates the paging range associated with the paging area. For example, the paging range includes or corresponds to Figure 5B The paging range is 552. In such a specific implementation, process 600 also includes identifying the paging area based on the paging range and the location of the source UE.

[0111] In some implementations, process 600 also includes identifying one or more tracking areas that intersect with the paging area. One or more other network entities are identified based on their location within these tracking areas. For example, they may be identified based on associated tracking areas that intersect with paging area 464 (e.g., geographic area 436). Figure 4 The network entity identified is 466.

[0112] In some implementations, process 600 further includes identifying a possible location area based on map data, UE information associated with the source UE, application information associated with an application running at the source UE, or a combination thereof. One or more other network entities are located at the intersection of the paging area and the possible location area. For example, it can be based on... Figure 4 Map data 468 is used to identify possible location areas. In some other implementations, process 600 includes receiving a message from an application server associated with an application executed at the source UE. This message indicates the possible area location, and one or more other network entities are located at the intersection of the paging area and the possible location area. For example, it can be obtained from... Figure 5A Application server 530 with the -C option receives messages.

[0113] In some implementations, the one or more paging messages may include a source UE ID, a source application ID, or both. Additionally or alternatively, the one or more paging messages may include a destination UE ID, a destination group ID, or a destination application ID. Alternatively, the one or more paging messages may be designated as broadcast messages to one or more other network entities. Additionally or alternatively, the one or more paging messages may include a first P-RNTI that is different from a second P-RNTI associated with a non-UE to UE paging. Additionally or alternatively, the one or more paging messages may be designated as being transmitted by one or more other network entities via PCCH or PDCCH.

[0114] Figure 7 This is a block diagram of an example network entity 700 supporting paging for network-based UE-to-UE communication based on one or more aspects. Network entity 700 can be configured to perform operations, including referencing... Figure 6 The described process 600 is a block diagram. In some specific implementations, base station 800 includes reference... Figures 1 to 3 Base station 105 Figure 4 Network Entity 450 Figures 5A to 5C Management server 520 and / or Figures 5A to 5C The structures, hardware, and components shown and described for base stations 510, 512, 514, and 516. For example, network entity 700 may include controller 240, which operates to execute logical or computer instructions stored in memory 242, and components that control network entity 700 to provide the characteristics and functionality of network entity 700. Network entity 700 transmits and receives signals via wireless radio components 701a-t and antenna 234a-t under the control of controller 240. Wireless radio components 701a-t include various components and hardware (such as those in...). Figure 2(Example for base station 105) includes modulator and demodulator 232a-t, transmitter processor 220, TX MIMO processor 230, MIMO detector 236 and receiver processor 238.

[0115] As shown, memory 242 may include UE-to-UE paging information 702, paging area information 703, and communication logic 704. UE-to-UE paging information 702 may include or correspond to information indicating the following: the location of the source UE for the UE-to-UE paging request conditions, the paging range associated with the UE-to-UE paging, source parameters for the UE-to-UE paging message, destination parameters for the UE-to-UE paging message, or combinations thereof. Paging area information 703 may indicate a paging area determined based on the location of the source UE and the paging range, and may include or correspond to... Figure 4 The paging area is 464. Communication logic 704 can be configured to enable communication between network entity 700 and one or more other devices. Network entity 700 can communicate with one or more UEs (such as...). Figures 1 to 4 and Figures 5A to 5C UE 115 Figure 4 UE 430 and 432, Figures 5A to 5C UE 502-508) receives signals or sends signals to one or more UEs.

[0116] It should be noted that, for reference Figure 6 One or more boxes (or operations) described may be combined with one or more boxes (or operations) described in another figure referring to these figures. As another example, with... Figure 6 One or more associated boxes can be connected with and Figures 1 to 4 and Figures 5A to 5C A combination of one or more associated boxes (or operations). Additionally or alternatively, see above for reference. Figures 1 to 4 and Figures 5A to 5C One or more operations described can be compared with the reference Figure 7 The described combination of one or more operations.

[0117] In one or more aspects, techniques for supporting paging for network-based UE-UE communication may include additional aspects, such as any single aspect or any combination of aspects described below or in conjunction with one or more other processes or devices described elsewhere herein. In some aspects, an apparatus for wireless communication at a network entity may support paging for network-based UE-UE communication. In some embodiments, the apparatus includes or is integrated into a wireless device, such as a base station, server, or other network entity. In some embodiments, the apparatus may include a processing system comprising one or more processors and one or more memories coupled to the processors. The processing system may be configured to cause a network entity to perform the operations described herein with respect to the apparatus. In some other embodiments, the apparatus may include a non-transitory computer-readable medium storing instructions that, when executed by a processor, cause the processor to perform the operations described herein with reference to the apparatus. In some embodiments, the apparatus may include one or more components configured to perform the operations described herein. In some embodiments, methods for wireless communication at a network entity may include one or more operations described herein with reference to the apparatus.

[0118] Specific implementation examples are described in the following numbered clauses.

[0119] Clause 1: An apparatus for wireless communication at a network entity, the apparatus comprising a processing system including one or more processors and one or more memories coupled to the one or more processors. The processing system is configured to cause the network entity to identify a UE-to-UE paging request condition originating from a source UE. The processing system is further configured to cause the network entity to identify one or more other network entities within a paging area relating to the location of the source UE. The processing system is further configured to cause the entity to send one or more paging messages to the one or more other network entities based on the UE-to-UE paging request condition.

[0120] Clause 2: The apparatus according to Clause 1, wherein the processing system is configured to cause the network entity to identify the UE-to-UE paging request condition to receive a UE-to-UE paging request originating from the source UE.

[0121] Clause 3: The apparatus according to Clause 2, wherein the UE-to-UE paging request indicates the location of the source UE, the paging range associated with the paging area, or both.

[0122] Clause 4: The apparatus described in Clause 2, wherein the UE-to-UE paging request indicates a destination UE, a destination UE group, a destination application, or a broadcast indicator.

[0123] Clause 5: The apparatus according to Clause 1, wherein, in order to identify the UE-to-UE paging request conditions, the processing system is configured to cause the network entity to receive location information associated with the source UE, paging range associated with the paging area, or both.

[0124] Clause 6: The apparatus according to Clause 1, wherein, in order to identify the UE-to-UE paging request condition, the processing system is configured to cause the network entity to receive a paging request originating from the source UE and access a configuration file associated with the source UE to determine whether the source UE is associated with UE-to-UE paging.

[0125] Clause 7: The apparatus according to Clause 1, wherein the UE-to-UE paging request condition includes a V2X paging condition.

[0126] Clause 8: A method for wireless communication performed at a network entity, the method comprising: identifying a UE-to-UE paging request condition originating from a source UE, identifying one or more other network entities within a paging area associated with the location of the source UE, and sending one or more paging messages to the one or more other network entities in accordance with the UE-to-UE paging request condition.

[0127] Clause 9: The method according to Clause 8 further includes: receiving a report message including location information associated with the source UE, and identifying the location of the source UE based on the location information.

[0128] Clause 10: The method described in Clause 9, wherein the reporting message includes an RRC message received from a serving network entity associated with the source UE.

[0129] Clause 11: The method described in Clause 9, wherein the reporting message includes an RRC message received from the source UE.

[0130] Clause 12: The method according to Clause 9, wherein the UE-to-UE paging request condition is associated with an application executed by the source UE, and wherein the reporting message includes a message received from an application server associated with the application.

[0131] Clause 13: The method according to Clause 8 further comprises: receiving one or more user data packets originating from the source UE, extracting location information associated with the source UE from the one or more user data packets, and identifying the location of the source UE based on the location information.

[0132] Clause 14: The method according to Clause 8, wherein identifying the UE-to-UE paging request conditions includes receiving the UE-to-UE paging request from a different network entity, and wherein the method further includes identifying the location of the source UE based on the location of the different network entities.

[0133] Clause 15: The method according to Clause 8 further includes: receiving a cell attachment message associated with the source UE, the cell attachment message indicating the cell ID of the cell to which the source UE is attached; identifying a serving network entity associated with the cell; and identifying the location of the source UE based on the location of the serving network entity.

[0134] Clause 16: The method according to Clause 8 further includes: receiving an association message associated with the source UE, the association message indicating a serving network entity to which the source UE is attached; and identifying the location of the source UE based on the location of the serving network entity.

[0135] Clause 17: The method according to Clause 8 further comprises: receiving one or more user data packets, the one or more user data packets indicating the UE ID of the source UE and the network entity ID of the serving network entity of the source UE; and identifying the location of the source UE based on the location of the serving network entity.

[0136] Clause 18: The method according to Clause 8 further includes: receiving a configuration message from the source UE, the configuration message indicating a paging range associated with the paging area; and identifying the paging area based on the paging range and the location of the source UE.

[0137] Clause 19: The method according to Clause 8 further comprises: receiving a configuration message from an application server associated with an application at the source UE, the configuration message indicating a paging range associated with the paging area; and identifying the paging area based on the paging range and the location of the source UE.

[0138] Clause 20: An apparatus for wireless communication at a network entity, the apparatus comprising: components for identifying a UE-UE paging request condition originating from a source UE; components for identifying one or more other network entities within a paging area associated with the location of the source UE; and components for sending one or more paging messages to the one or more other network entities in accordance with the UE-UE paging request condition.

[0139] Clause 21: The apparatus according to Clause 20, wherein the one or more paging messages include a source UE ID, a source application ID, or both.

[0140] Clause 22: The apparatus according to Clause 21, wherein the one or more paging messages include a destination UEID, a destination group ID, or a destination application ID.

[0141] Clause 23: The apparatus according to Clause 21, wherein the one or more paging messages are designated as broadcast messages to the one or more other network entities.

[0142] Clause 24: The apparatus according to Clause 20, wherein the one or more paging messages include a first P-RNTI, the first P-RNTI being different from a second P-RNTI associated with a non-UE to UE paging.

[0143] Clause 25: The apparatus according to Clause 20, wherein the one or more paging messages are designated to be sent by the one or more other network entities via PCCH.

[0144] Clause 26: The apparatus according to Clause 20, wherein the one or more paging messages are designated to be sent by the one or more other network entities via PDCCH as DCI.

[0145] Clause 27: A non-transitory computer-readable medium storing instructions that, when executed by a processor, cause the processor to perform operations for wireless communication at a network entity. The operations include identifying a UE-to-UE paging request condition originating from a source UE. The operations also include identifying one or more other network entities within a paging area relative to the location of the source UE. The operations further include sending one or more paging messages to the one or more other network entities based on the UE-to-UE paging request condition.

[0146] Clause 28: A non-transitory computer-readable medium as described in Clause 27, wherein said operation further includes identifying one or more tracking regions intersecting the paging region. The one or more other network entities are identified based on their location within said one or more tracking regions.

[0147] Clause 29: A non-transitory computer-readable medium as described in Clause 27, wherein the operation further includes identifying a possible location area based on map data, UE information associated with the source UE, application information associated with an application executed at the source UE, or a combination thereof. The one or more other network entities are located at the intersection of the paging area and the possible location area.

[0148] Clause 30: A non-transitory computer-readable medium as described in Clause 27, wherein said operation further includes receiving a message from an application server associated with an application executed at the source UE. The message indicates a possible regional location. The one or more other network entities are located at the intersection of the paging area and the possible location area.

[0149] Clause 31: A method of wireless communication performed at an MEC deployment or an edge server, the method comprising: determining a use case scenario by the edge server and translating the use case into specific V2X paging parameters, the specific V2X paging parameters being sent to a source UE.

[0150] Clause 32: The method according to Clause 31, wherein the edge server receives information about the desired range requirement, and the specific V2X paging parameters sent to the source UE are based on the desired range requirement.

[0151] Clause 33: The method of claim 31, wherein the V2X paging parameters are relayed to the source UE via the AMF.

[0152] Clause 34: The method of claim 31, wherein the V2X paging parameters determined by the edge server include one or more of the following: source UE ID (e.g., V2X Layer 2 source ID), destination UE ID (e.g., 5G-S-TMSI), V2X Layer 2 destination ID, V2X application ID, and / or V2X group ID.

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

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

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

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

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

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

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

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

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

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

[0163] Similarly, although operations are depicted in a specific order in the figures, this should not be construed as requiring such operations to be performed in the indicated specific order or sequential order, or to perform all illustrated operations to achieve the desired result. Furthermore, the figures may schematically depict one or more example processes in the form of flowcharts. However, other operations not depicted may be combined with the schematically illustrated example processes. For example, one or more additional operations may be performed before, after, simultaneously with, or between any illustrated operation. In some contexts, multitasking and parallel processing are advantageous. Moreover, the separation of the various system components in the embodiments described above should not be construed as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products. Additionally, some other embodiments also fall within the scope of the appended claims. In some cases, the actions recited in the claims may be performed in a different order and still achieve the desired result.

[0164] As used herein (including the claims), the term "or" in a list of two or more items means that any one of the listed items may be used alone, or any combination of two or more listed items may be used. For example, if a composition is described as containing component A, B, or C, the composition may contain A alone; B alone; C alone; a combination of A and B; a combination of A and C; a combination of B and C; or a combination of A, B, and C. Additionally, as used herein (including the claims), "or" in a list of items beginning with "at least one of" indicates a separate list, such that a list such as "at least one of A, B, or C" refers to A or B or C or AB or AC or BC or ABC (i.e., A and B and C) or any combination of any of these items. The term "substantially" is defined as substantially but not necessarily entirely what is specified (and includes what is specified; for example, substantially 90 degrees includes 90 degrees and substantially parallel includes parallel), as understood by one of ordinary skill in the art. In any disclosed specific implementation, the term “substantially” may be used in place of “[percentage]” for the specified content, where the percentage includes 0.1%, 1%, 5% or 10%.

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

Claims

1. An apparatus for wireless communication at a network entity, the apparatus comprising: a processing system including one or more processors and one or more memories coupled with the one or more processors, the processing system configured to cause the network entity to: identify a UE-to-UE paging request condition originating from a source user equipment (UE); identify one or more other network entities within a paging area relative to a location of the source UE; and transmit one or more paging messages to the one or more other network entities in accordance with the UE-to-UE paging request condition.

2. The apparatus of claim 1, wherein the processing system is configured to cause the network entity to receive a UE-to-UE paging request originating from the source UE based on the UE-to-UE paging request condition.

3. The apparatus of claim 2, wherein the UE-to-UE paging request indicates the location of the source UE, a paging range associated with the paging area, or both.

4. The apparatus of claim 2, wherein the UE-to-UE paging request indicates a destination UE, a group of destination UEs, a destination application, or a broadcast indicator.

5. The apparatus of claim 1, wherein to identify the UE-to-UE paging request condition, the processing system is configured to cause the network entity to receive location information associated with the source UE, a paging range associated with the paging area, or both.

6. The apparatus of claim 1, wherein to identify the UE-to-UE paging request condition, the processing system is configured to cause the network entity to: receive a paging request originating from the source UE; and access a profile associated with the source UE to determine whether the source UE is associated with UE-to-UE paging.

7. The apparatus of claim 1, wherein the UE-to-UE paging request condition comprises a vehicle-to-anything (V2X) paging condition.

8. A method of wireless communication performed at a network entity, the method comprising: identifying a UE-to-UE paging request condition originating from a source user equipment (UE); identifying one or more other network entities within a paging area relative to a location of the source UE; and transmitting one or more paging messages to the one or more other network entities in accordance with the UE-to-UE paging request condition.

9. The method of claim 8, the method further comprising: receiving a report message including location information associated with the source UE, wherein the one or more network entities are identified in accordance with the location of the source UE based on the location information received in the location message.

10. The method of claim 9, wherein the report message comprises a radio resource control (RRC) message received from a serving network entity associated with the source UE.

11. The method of claim 9, wherein the report message comprises a radio resource control (RRC) message received from the source UE.

12. The method of claim 9, wherein the UE-to-UE paging request condition is associated with an application executed by the source UE, and wherein the report message comprises a message received from an application server associated with the application.

13. The method of claim 8, the method further comprising: receiving one or more user data packets originating from the source UE; extracting location information associated with the source UE from the one or more user data packets; and identifying the location of the source UE from the location information.

14. The method of claim 8, wherein, identifying the UE-to-UE paging request condition comprises receiving a UE-to-UE paging request from a different network entity, and wherein the method further comprises: identifying the location of the source UE from a location of the different network entity.

15. The method of claim 8, the method further comprising: receiving a cell attach message associated with the source UE, the cell attach message indicating a cell identifier (ID) of a cell to which the source UE is attached, wherein a serving network entity associated with the cell is identified from the cell ID, and the location of the source UE is identified from a location of the serving network entity.

16. The method of claim 8, the method further comprising: receiving an association message associated with the source UE, the association message indicating a serving network entity to which the source UE is attached, wherein the location of the source UE is identified from a location of the serving network entity.

17. The method of claim 8, the method further comprising: receiving one or more user data packets, the one or more user data packets indicating a UE identifier (ID) of the source UE and a network entity ID of a serving network entity of the source UE, wherein the location of the source UE is identified from a location of the serving network entity.

18. The method of claim 8, the method further comprising: receiving a configuration message originating from the source UE, the configuration message indicating a paging range associated with the paging area, wherein the paging area is identified from the paging range and the location of the source UE.

19. The method of claim 8, the method further comprising: receiving a configuration message from an application server associated with an application at the source UE, the configuration message indicating a paging range associated with the paging area, wherein the paging area is identified from the paging range and the location of the source UE.

20. An apparatus for wireless communication at a network entity, the apparatus comprising: means for identifying a UE-to-UE paging request condition originating from a source user equipment (UE); means for identifying one or more other network entities within a paging area relative to a location of the source UE; and means for transmitting one or more paging messages to the one or more other network entities in accordance with the UE-to-UE paging request condition.

21. The apparatus of claim 20, wherein the one or more paging messages comprise a source UE identifier (ID), a source application ID, or both.

22. The apparatus of claim 21, wherein the one or more paging messages comprise a destination UE ID, a destination group ID, or a destination application ID.

23. The apparatus of claim 21, wherein the one or more paging messages are designated as broadcast messages to the one or more other network entities.

24. The apparatus of claim 20, wherein the one or more paging messages comprise a first paging-radio network temporary identifier (P-RNTI) that is different from a second P-RNTI associated with non-UE-to-UE paging.

25. The apparatus of claim 20, wherein the one or more paging messages are designated to be transmitted by the one or more other network entities via a paging control channel (PCCH).

26. The apparatus of claim 20, wherein the one or more paging messages are designated to be transmitted by the one or more other network entities via a physical downlink control channel (PDCCH) as downlink control information (DCI).

27. A non-transitory computer-readable medium storing instructions that, when executed by a processor, cause the processor to perform operations for wireless communication at a network entity, the operations comprising: identifying a UE-to-UE paging request condition originating from a source user equipment (UE); identifying one or more other network entities within a paging area relative to a location of the source UE; and transmitting one or more paging messages to the one or more other network entities in accordance with the UE-to-UE paging request condition.

28. The non-transitory computer-readable medium of claim 27, wherein the operations further comprise: identifying one or more tracking areas that intersect the paging area, wherein the one or more other network entities are identified in accordance with being located in the one or more tracking areas.

29. The non-transitory computer-readable medium of claim 27, wherein the operations further comprise: identifying a possible location area in accordance with map data, UE information associated with the source UE, application information associated with an application executing at the source UE, or a combination thereof, wherein the one or more other network entities are located in an intersection of the paging area and the possible location area.

30. The non-transitory computer-readable medium of claim 27, wherein the operations further comprise: receiving a message from an application server associated with an application executing at the source UE, the message indicating a possible area location, wherein the one or more other network entities are located in an intersection of the paging area and the possible location area. ​

Images