Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a first network entity may establish a first user equipment (UE) identifier (ID) associated with pre-paging. The first network entity may transmit, with information associated with the first UE ID, a request associated with paging to a second network entity. Numerous other aspects are described.

INTRODUCTION

Aspects of the present disclosure generally relate to wireless communication and to techniques and apparatuses for pre-paging.

SUMMARY

Some aspects described herein relate to a method of wireless communication performed at a first network entity. The method may include establishing a first user equipment (UE) identifier (ID) associated with pre-paging. The method may include transmitting, with information associated with the first UE ID, a request associated with paging to a second network entity.

Some aspects described herein relate to a method of wireless communication performed at a UE. The method may include establishing a first UE ID associated with pre-paging. The method may include monitoring for the first UE ID in a pre-paging message.

Some aspects described herein relate to a method of wireless communication performed at a first network entity. The method may include receiving a pre-paging configuration with a first UE ID. The method may include generating a mapping between the pre-paging configuration and a second UE ID associated with the first UE ID. The method may include transmitting a request associated with paging with the second UE ID and the pre-paging configuration.

Some aspects described herein relate to a method of wireless communication performed at a second network entity. The method may include receiving, with information associated with a first UE ID, a request associated with paging from a first network entity. The method may include transmitting a pre-paging message to a UE associated with the first UE ID.

Some aspects described herein relate to an apparatus for wireless communication at a first network entity. The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to cause the first network entity to establish a first UE ID associated with pre-paging. The one or more processors may be configured to cause the first network entity to transmit, with information associated with the first UE ID, a request associated with paging to a second network entity.

Some aspects described herein relate to an apparatus for wireless communication at a UE. The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to cause the UE to establish a first UE ID associated with pre-paging. The one or more processors may be configured to cause the UE to monitor for the first UE ID in a pre-paging message.

Some aspects described herein relate to an apparatus for wireless communication at a first network entity. The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to cause the first network entity to receive a pre-paging configuration with a first UE ID. The one or more processors may be configured to cause the first network entity to generate a mapping between the pre-paging configuration and a second UE ID associated with the first UE ID. The one or more processors may be configured to cause the first network entity to transmit a request associated with paging with the second UE ID and the pre-paging configuration.

Some aspects described herein relate to an apparatus for wireless communication at a second network entity. The apparatus may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to cause the second network entity to receive, with information associated with a first UE ID, a request associated with paging from a first network entity. The one or more processors may be configured to cause the second network entity to transmit a pre-paging message to a UE associated with the first UE ID.

Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a first network entity. The set of instructions, when executed by one or more processors of the first network entity, may cause the first network entity to establish a first UE ID associated with pre-paging. The set of instructions, when executed by one or more processors of the first network entity, may cause the first network entity to transmit, with information associated with the first UE ID, a request associated with paging to a second network entity.

Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to establish a first UE ID associated with pre-paging. The set of instructions, when executed by one or more processors of the UE, may cause the UE to monitor for the first UE ID in a pre-paging message.

Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a first network entity. The set of instructions, when executed by one or more processors of the first network entity, may cause the first network entity to receive a pre-paging configuration with a first UE ID. The set of instructions, when executed by one or more processors of the first network entity, may cause the first network entity to generate a mapping between the pre-paging configuration and a second UE ID associated with the first UE ID. The set of instructions, when executed by one or more processors of the first network entity, may cause the first network entity to transmit a request associated with paging with the second UE ID and the pre-paging configuration.

Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a second network entity. The set of instructions, when executed by one or more processors of the second network entity, may cause the second network entity to receive, with information associated with a first UE ID, a request associated with paging from a first network entity. The set of instructions, when executed by one or more processors of the second network entity, may cause the second network entity to transmit a pre-paging message to a UE associated with the first UE ID.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for establishing a first UE ID associated with pre-paging. The apparatus may include means for transmitting, with information associated with the first UE ID, a request associated with paging to another apparatus.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for establishing a first UE ID associated with pre-paging. The apparatus may include means for monitoring for the first UE ID in a pre-paging message.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a pre-paging configuration with a first UE ID. The apparatus may include means for generating a mapping between the pre-paging configuration and a second UE ID associated with the first UE ID. The apparatus may include means for transmitting a request associated with paging with the second UE ID and the pre-paging configuration.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving, with information associated with a first UE ID, a request associated with paging from another apparatus. The apparatus may include means for transmitting a pre-paging message to a UE associated with the first UE ID.

DETAILED DESCRIPTION

Various aspects relate generally to wireless communication and more particularly to paging user equipments (UEs). Some aspects more specifically relate to paging of a UE by a radio access network (RAN) network entity. The UE may enter an idle state, and the RAN network entity may page the UE. Paging may include the RAN network entity sending a paging message to the UE to indicate that the UE is to enter a connected state.

The paging by the RAN network entity may be controlled by a core network. The core network may include, for example, an access and mobility management function (AMF), which may be a network entity in the core network that acts as a termination point for signaling and/or mobility management with respect to the UE. The AMF may request the RAN network entity to page the UE. The RAN network entity may then page the UE to indicate that the UE can connect to the RAN network entity. More specifically, the RAN network entity may first transmit a physical downlink control channel (PDCCH) message to the UE. The PDCCH message may include a paging radio network temporary identifier (P-RNTI) identifying the UE and allocating resources for a paging message. The RAN network entity may then transmit the paging message to the UE on a physical downlink shared channel (PDSCH) in the allocated resource. The UE may set up a connection with the RAN network entity (including a bearer) based on receiving the paging message and performing a random access channel (RACH) procedure with the RAN network entity.

Only upon successful completion of bearer setup with the RAN network entity does the user interface of the UE notify the user about an incoming message, such as an incoming call (via ringing, vibration, notification). In certain scenarios, when paging and the RACH is successful, a subsequent physical uplink shared channel (PUSCH) message may fail if a downlink link budget is insufficient (too much power loss on the link). In other scenarios, even when paging is successful, the RACH may fail due to weak signals on an uplink because of poor or deep coverage. In certain examples, the paging message may not be received if the link is weak (e.g., if the smartphone is in a pocket or in a backpack).

To address these issues, in some examples, the RAN network entity may perform pre-paging, in which the RAN network entity transmits a pre-paging message. This pre-paging message may include information identifying a UE and indicating that the UE is to connect to the RAN network entity and/or perform an action in preparation for paging. For example, the pre-paging message may enable the UE, which may have an insufficient link budget, to alert the user on a display interface of the UE to move the UE to a better location, to improve a link to the RAN network entity. The RAN network entity may repeat the paging after a period of time. For example, in some aspects, rather than simply determining that paging has failed if no response to the paging is received from the UE, the RAN network entity may transmit a pre-paging message to the UE on a pre-paging channel. Pre-paging may include transmitting a pre-paging message ahead of a paging message or in preparation for paging. The UE may receive the pre-paging message and alert the user of the UE to move to a better location. The RAN network entity may repeat the paging after a specified amount of time or expect another monitoring occasion (MO) session for paging. By using a pre-paging message, the paging may ultimately be successful.

However, in one scenario, a paging UE identifier (ID) assigned by the RAN network entity (48 bits) may be too long in length for use on a pre-paging channel that the UE is to monitor for pre-paging. In another scenario, the AMF may maintain a UE context for the UE that includes information (e.g., identities, parameters, capabilities) for a logical connection of the UE. The UE may enter a radio resource control (RRC) idle state (e.g., go to sleep, exit coverage). If the UE enters the RRC idle state, the RAN network entity may clear the UE context. Accordingly, the RAN network entity may not be able to use the paging UE ID at a future time since the paging UE ID may correspond to the UE context at the RAN, which is cleared once the UE moves to an RRC idle state. Furthermore, since the RAN clears the UE context, the RAN may not be able to store any code (e.g., temporary UE ID) assigned to the UE for pre-paging monitoring. Without storing pre-paging information for a paging UE ID, the RAN network entity may have to allocate pre-paging resources and assign a code to the UE again when the UE is to be paged. This increases latency and consumes signaling resources.

According to various aspects described herein, the AMF may establish a new UE ID, such as a pre-paging UE ID for monitoring pre-paging. The AMF and the UE may establish the pre-paging UE ID, which, in one example, may be derived from a paging UE ID (e.g., fifth generation (5G) serving temporary mobile subscriber identity (S-TMSI)). In some aspects, the pre-paging UE ID may be shorter in length than a paging UE ID. The paging UE ID may be too long in length for use in a pre-paging message and/or on a pre-paging channel, and the pre-paging UE ID may be short enough in length to be used in a pre-paging message and/or on a pre-paging channel. The AMF may request that the RAN network entity pre-page the UE with the pre-paging UE ID. The RAN network entity may transmit a pre-paging message with the pre-paging UE ID to the UE. The UE may respond to the pre-paging message based at least in part on the pre-paging UE ID. In some aspects, the UE may derive the pre-paging UE ID with information included in a paging message. In this way, a UE may respond to a pre-paging message even if the UE is not in good coverage, because the UE is more likely to receive and respond to the pre-paging message (e.g., smaller than the pre-paging message or on a pre-paging channel). The RAN network entity may avoid having to resend a pre-paging resource allocation for the UE. As a result, pre-paging may be successful. Also, latency may be reduced and signaling resources may be conserved because paging messages are not wasted.

In some aspects, the AMF may store UE-specific pre-paging resources, such as a pre-paging configuration. The pre-paging configuration may indicate pre-paging resources and a temporary UE ID (e.g., code such as a radio network temporary identifier (RNTI)) assigned to the UE for monitoring across multiple cells/group IDs and codes). For example, the AMF may maintain a database of the codes assigned to a UE. The AMF may generate a mapping between a pre-paging configuration (e.g., including an assigned code) and a UE paging identity for the UE (paging UE ID). The AMF may transmit a paging request to the RAN network entity with the pre-paging configuration and the paging UE ID. The RAN network entity may transmit a pre-paging message using the pre-paging configuration (including the temporary UE ID). The UE may monitor for pre-paging with the temporary UE ID and receive the pre-paging message. In this way, the AMF may indicate the temporary UE ID assigned to the UE (in the pre-paging configuration) when the AMF transmits the paging request to the RAN network entity. By maintaining a mapping of the pre-paging configuration and the paging UE ID assigned to the UE, the RAN network entity may avoid having to resend a pre-paging resource allocation. As a result, paging may be successful. Latency may be reduced and signaling resources may be conserved if paging messages do not fail.

In some aspects, a first network entity (e.g., a network node110, a core network node115) may include a communication manager160. As described in more detail elsewhere herein, the communication manager160may establish a first UE ID associated with pre-paging. The communication manager160may transmit, with information associated with the first UE ID, a request associated with paging to a second network entity.

In some aspects, the communication manager160may receive a pre-paging configuration with a first UE ID. The communication manager160may generate a mapping between the pre-paging configuration and a second UE ID associated with the first UE ID. The communication manager160may transmit a request associated with paging with the second UE ID and the pre-paging configuration. Additionally, or alternatively, the communication manager160may perform one or more other operations described herein.

In some aspects, a UE120(e.g., a UE120) may include a communication manager140. As described in more detail elsewhere herein, the communication manager140may establish a first UE ID associated with pre-paging. The communication manager140may monitor for the first UE ID in a pre-paging message. Additionally, or alternatively, the communication manager140may perform one or more other operations described herein.

In some aspects, a second network entity (e.g., a network node110) may include a communication manager150. As described in more detail elsewhere herein, the communication manager150may receive, with information associated with a first UE ID, a request associated with paging from a first network entity. The communication manager150may transmit a pre-paging message to a UE associated with the first UE ID. Additionally, or alternatively, the communication manager150may perform one or more other operations described herein.

FIG.2is a diagram illustrating an example200of a network node110or core network node115in communication with a UE120in a wireless network100, in accordance with the present disclosure. The network node110may be equipped with a set of antennas234athrough234t, such as T antennas (T≥1). The UE120may be equipped with a set of antennas252athrough252r, such as R antennas (R≥1). The network node110of example200includes one or more radio frequency components, such as antennas234and a modem232. In some examples, a network node110may include an interface, a communication component, or another component that facilitates communication with the UE120or another network node. Some network nodes110may not include radio frequency components that facilitate direct communication with the UE120, such as one or more CUs, or one or more DUs.

In some aspects, a first network entity (e.g., a network node110, core network node115) includes means for establishing a first UE ID associated with pre-paging; and/or means for transmitting, with information associated with the first UE ID, a request associated with paging to a second network entity. In some aspects, the means for the first network entity to perform operations described herein may include, for example, one or more of communication manager150, transmit processor220, TX MIMO processor230, modem232, antenna234, MIMO detector236, receive processor238, controller/processor240, memory242, or scheduler246.

In some aspects, the first network entity includes means for receiving a pre-paging configuration with a first UE ID; means for generating a mapping between the pre-paging configuration and a second UE ID associated with the first UE ID; and/or means for transmitting a request associated with paging with the second UE ID and the pre-paging configuration.

In some aspects, a UE (e.g., a UE120) includes means for establishing a first UE ID associated with pre-paging; and/or means for monitoring for the first UE ID in a pre-paging message. The means for the UE to perform operations described herein may include, for example, one or more of communication manager140, antenna252, modem254, MIMO detector256, receive processor258, transmit processor264, TX MIMO processor266, controller/processor280, or memory282.

In some aspects, a second network entity (e.g., a network node110) includes means for receiving, with information associated with a first UE ID, a request associated with paging from a first network entity; and/or means for transmitting a pre-paging message to a UE associated with the first UE ID. In some aspects, the means for the second network entity to perform operations described herein may include, for example, one or more of communication manager150, transmit processor220, TX MIMO processor230, modem232, antenna234, MIMO detector236, receive processor238, controller/processor240, memory242, or scheduler246.

FIG.4is a diagram of an example400of a core network405, in accordance with the present disclosure. As shown inFIG.4, example400may include a UE120, a wireless network100, and a core network405. Devices and/or networks of example400may interconnect via wired connections, wireless connections, or a combination thereof.

The wireless network100may support, for example, a cellular RAT. The network100may include one or more network nodes, such as base stations (e.g., base transceiver stations, radio base stations, node Bs, eNodeBs (eNBs), gNodeBs (gNBs), base station subsystems, cellular sites, cellular towers, access points, TRPs, radio access nodes, macrocell base stations, microcell base stations, picocell base stations, femtocell base stations, or similar types of devices) and other network nodes that can support wireless communication for the UE120. The network100may transfer traffic between the UE120(e.g., using a cellular RAT), one or more network nodes (e.g., using a wireless interface or a backhaul interface, such as a wired backhaul interface), and/or the core network405. The wireless network100may provide one or more cells that cover geographic areas.

In some aspects, the wireless network100may perform scheduling and/or resource management for the UE120covered by the network100(e.g., the UE120covered by a cell provided by the wireless communication network100). In some aspects, the wireless network100may be controlled or coordinated by a network controller (e.g., network controller130ofFIG.1), which may perform load balancing and/or network-level configuration, among other examples. As described above in connection withFIG.1, the network controller may communicate with the network100via a wireless or wireline backhaul. In some aspects, the wireless network100may include a network controller, a self-organizing network (SON) module or component, or a similar module or component. Accordingly, the wireless network100may perform network control, scheduling, and/or network management functions (e.g., for uplink, downlink, and/or sidelink communications of the UE120covered by the network100).

In some aspects, the core network405may include an example functional architecture in which systems and/or methods described herein may be implemented. For example, the core network405may include an example architecture of a 5G next generation (NG) core network included in a 5G wireless telecommunications system. Although the example architecture of the core network405shown inFIG.4may be an example of a service-based architecture, in some aspects, the core network405may be implemented as a reference-point architecture and/or a 4G core network, among other examples.

As shown inFIG.4, the core network405may include a number of functional elements. The functional elements may include, for example, a network slice selection function (NSSF)410, a network exposure function (NEF)415, an authentication server function (AUSF)420, a unified data management (UDM) component425, a policy control function (PCF)430, an application function (AF)435, an AMF440, a session management function (SMF)445, and/or a user plane function (UPF)450, among other examples. These functional elements may be communicatively connected via a message bus455. Each of the functional elements shown inFIG.4may be implemented on one or more devices associated with a wireless telecommunications system. In some implementations, one or more of the functional elements may be implemented on physical devices, such as an access point, a base station, and/or a gateway, among other examples. In some implementations, one or more of the functional elements may be implemented on a computing device of a cloud computing environment.

The NSSF410may include one or more devices that select network slice instances for the UE120. Network slicing is a network architecture model in which logically distinct network slices operate using common network infrastructure. For example, several network slices may operate as isolated end-to-end networks customized to satisfy different target service standards for different types of applications executed, at least in part, by the UE120and/or communications to and from the UE120. Network slicing may efficiently provide communications for different types of services with different service standards.

The NSSF410may determine a set of network slice policies to be applied at the wireless network100. For example, the NSSF410may apply one or more UE route selection policy (URSP) rules. In some aspects, the NSSF410may select a network slice based on a mapping of a data network name (DNN) field included in a route selection description (RSD) to the DNN field included in a traffic descriptor selected by the UE120. By providing network slicing, the NSSF410allows an operator to deploy multiple substantially independent end-to-end networks potentially with the same infrastructure. In some implementations, each slice may be customized for different services.

The NEF415may include one or more devices that support exposure of capabilities and/or events in the wireless telecommunications system to help other entities in the wireless telecommunications system discover network services. The AUSF420may include one or more devices that act as an authentication server and support the process of authenticating the UE120in the wireless telecommunications system.

The UDM425may include one or more devices that store user data and profiles in the wireless telecommunications system. In some aspects, the UDM425may be used for fixed access and/or mobile access, among other examples, in the core network405.

The PCF430may include one or more devices that provide a policy framework that incorporates network slicing, roaming, packet processing, and/or mobility management, among other examples. In some aspects, the PCF430may include one or more URSP rules used by the NSSF410to select network slice instances for the UE120.

The AF435may include one or more devices that support application influence on traffic routing, access to the NEF415, and/or policy control, among other examples. The AMF440may include one or more devices that act as a termination point for non-access stratum (NAS) signaling and/or mobility management, among other examples. In some aspects, the AMF440may request the NSSF410to select network slice instances for the UE120, e.g., at least partially in response to a request for data service from the UE120.

The SMF445may include one or more devices that support the establishment, modification, and release of communication sessions in the wireless telecommunications system. For example, the SMF445may configure traffic steering policies at the UPF450and/or enforce user equipment internet protocol (IP) address allocation and policies, among other examples. In some aspects, the SMF445may provision the network slice instances selected by the NSSF410for the UE120.

The UPF450may include one or more devices that serve as an anchor point for intraRAT and/or interRAT mobility. In some aspects, the UPF450may apply rules to packets, such as rules pertaining to packet routing, traffic reporting, and/or handling user plane QoS, among other examples.

The message bus455may be a logical and/or physical communication structure for communication among the functional elements. Accordingly, the message bus455may permit communication between two or more functional elements, whether logically (e.g., using one or more application programming interfaces (APIs), among other examples) and/or physically (e.g., using one or more wired and/or wireless connections).

FIG.5is a diagram illustrating an example500associated with a paging signal flow, in accordance with the present disclosure. As shown inFIG.5, a UE510(e.g., UE120) and a network node at a RAN520(e.g., network node110) may communicate with one another in a wireless network (e.g., wireless network100). The RAN520may communicate with an AMF530(e.g., AMF440). The AMF530may communicate with an SMF540(e.g., SMF445). The SMF540may communicate with a UPF550(e.g., UPF450).

A core network may control the paging of a UE by a RAN. For example, the AMF of the core network may request paging by the RAN. For example, an access and AMF of the core network may request paging by the RAN. A network node of the RAN may then page the UE to indicate that the UE can set up a connection. More specifically, the network node may transmit a PDCCH message that uses a P-RNTI and that allocates resources for a paging message. The network node may transmit the paging message on a PDSCH in the allocated resource. The UE may set up a connection with the network node (including a bearer) based on receiving the paging message and performing a RACH procedure.

Example500shows paging signaling that is initiated by the core network. As shown by reference number552, the UPF550may receive downlink data. As shown by reference number554, the UPF550may notify the SMF540of the data. As shown by reference number556, the SMF540may provide an acknowledgment (ACK) of the data notification. As shown by reference number558, the UPF550may transmit the downlink data to the SMF540.

As shown by reference number560, the SMF540may initiate a Namf communication N1 and N2 message transfer. The message transfer helps to identify a service-based interface for the AMF530. The message transfer may include details, such as a packet data protocol (PDU) session ID, N2 session management information (e.g., quality of service (QOS) profiles), core network N3 tunnel information, a single network slice selection assistance information (S-NSSAI) that identifies a slice, and a paging policy indicator that is used for identifying paging policies. As shown by reference number562, the AMF530may provide a message transfer response. As shown by reference number564, the AMF530may start a timer (e.g., T3513). Timer T3513 starts when a paging procedure is initiated and stops when the paging procedure ends (with the reception of a paging response). As shown by reference number566, the AMF530may transit a paging request to the RAN520(RAN520network entity).

As shown by reference number568, the RAN520(network entity of the RAN520) may transmit a PDCCH message with a paging radio network temporary identifier (P-RNTI) to the UE510. The P-RNTI may have a fixed value of “fffe”. As shown by reference number570, the RAN520may transmit an RRC message for paging on the PDSCH. As shown by reference number572, the UE510may transmit a random access (RA) preamble to the RAN520to initiate a RACH procedure for establishing a connection. as shown by reference number574, the RAN520may transmit a random access response as part of the RACH procedure. As shown by reference number576, the UE510may transmit an RRC connection request on the PUSCH to establish a connection. as shown by reference number578, the RAN520may transmit an RRC connection setup message on the PDSCH. As shown by reference number580, the UE510may transmit an RRC connection setup complete service request message on the PUSCH.

As shown by reference number582, the RAN520may transmit a next generation application protocol (NGAP) N2 message that indicates a service request for a connection. The AMF530may be supervising the paging procedure with the timer. If the AMF receives no response from the UE510to the paging request, the AMF530may apply further paging according to an applicable paging strategy. The AMF530may be counting paging requests while the timer is running. As shown by reference number584, the AMF530may stop the timer.

While this paging procedure may be successful when the UE510is in regular coverage of the RAN520, in some scenarios, the UE510may not be able to monitor paging if the UE510moves into deep coverage or further away from the RAN520where coverage is less reliable. For example, if the UE510has moved into less reliable coverage, there may be no steps570through580.

Only upon successful completion of bearer setup does the user interface of the UE510notify the user about an incoming call (via ringing, vibration, notification). This may not be satisfactory for mobile termination (MT) calls or sessions because, if paging and RACH is successful, but a subsequent PUSCH message fails. Even if paging is successful, assuming a downlink link budget is sufficient (not too much power loss on the link), the RACH will fail due to a weak uplink. In addition, the paging message may not be received if the link is weak (e.g., if the smartphone is in a pocket or in a backpack).

To address these issues, in some examples, the RAN520may perform pre-paging, in which the RAN520transmits a pre-paging message. This pre-paging message may include information identifying a UE and indicating that the UE is to connect to the RAN520and/or perform an action in preparation for paging. For example, the pre-paging message may enable the UE520, which may have an insufficient link budget, to alert the user on a display interface of the UE520to move the UE520to a better location, to improve a link to the RAN520. The RAN520may repeat the paging after a period of time. For example, in some aspects, rather than simply determining that paging has failed if no response to the paging is received from the UE, the RAN520may transmit a pre-paging message to the UE520on a pre-paging channel. Pre-paging may include transmitting a pre-paging message ahead of a paging message or in preparation for paging. The UE520may receive the pre-paging message and alert the user of the UE520to move to a better location. The RAN network entity may repeat the paging after a specified amount of time or expect another monitoring occasion (MO) session for paging. By using a pre-paging message, the paging may ultimately be successful.

In some examples, the UE510may indicate its capability to monitor pre-paging messages. The UE510may also indicate to the RAN520whether a pre-paging feature is turned on or off. The UE510may operate in a power-saving mode and may turn off the pre-paging feature. During any phase of an RRC-connected state, the RAN520may assign a temporary UE ID (e.g., temporary RNTI) for monitoring pre-paging PDCCH. In some aspects, the RAN520may use a new downlink control information (DCI) format reserved for pre-paging, which is scrambled by the RNTI. There may be a validity timer associated with the RNTI. The RAN520may clear the RNTI after the validity timer expires.

In some examples, there may by different ways of separating pre-paging resources, including ways of achieving time, frequency, and code domain orthogonality. For instance, pre-paging time and frequency resources may be group common, and UEs may be separated into multiple groups. The RAN520may signal each UE with a group ID and a unique RNTI (code). Each group may have non-overlapping time and frequency resources allocated for pre-paging.

In some examples, to enable the pre-paging configuration to be valid after cell reselection, the RAN520may configure a UE with pre-paging resources for a group of cells. If one of these cells is detected by the UE, the UE may be able to monitor pre-paging with the code assigned to the UE. The code assigned to the UE may be associated with the UE context.

The UE context may include information for a logical connection of the UE. The information may include a subscriber identify, an indication of whether the subscriber identity is unauthenticated, a 3GPP subscription identity, a globally unique temporary identifier, a mobile equipment identity, UE-specific discontinuous reception (DRX) parameters, mobility management network capabilities, event subscriptions, and/or other UE capabilities related to the 5G core network. The UE context may be maintained by the AMF530.

However, in one scenario, the paging UE ID that is used for paging (e.g., 5G S-TMSI) is 48 bits and may be too long in length for use on a pre-paging channel that the UE510is to monitor for pre-paging. In another scenario, since the RAN520clears the UE context after the UE510moves to an RRC idle state, the RAN520may not be able to use a paging UE ID at a future time since the paging UE ID may correspond to the UE context at the RAN520, which is cleared once the UE510moves to an RRC idle state. For example, the UE510may receive a signal but not respond to paging. Furthermore, since the RAN520clears the UE context, the RAN520may not be able to store the code or temporary UE ID assigned to the UE510for pre-paging monitoring. Without a pre-paging configuration stored information for the pre-paging resources, the RAN520may have to allocate pre-paging resources and assign a code to the UE510again when the UE510is to be paged. This increases latency and consumes signaling resources. That is, if the pre-paging resources are allocated by the RAN520during an RRC connected mode, this information needs to be stored at the core network since the UE context in RAN520is cleared once the UE510moves to an RRC idle state. Thereby, this information is lost for a future paging/pre-paging occasion.

According to various aspects described herein, the AMF may establish a new UE ID, such as a pre-paging UE ID for monitoring pre-paging. The AMF and the UE may establish (e.g., agree to) the pre-paging UE ID, which may be derived from a paging UE ID (e.g., 5G S-TMSI). The pre-paging UE ID may be shorter in length than a paging UE ID. The paging UE ID may be too long in length for use in a pre-paging message and/or on a pre-paging channel and the pre-paging UE ID may be short enough in length to be used in a pre-paging message and/or on a pre-paging channel. The AMF may request that the RAN network entity pre-page the UE with the pre-paging UE ID. The RAN network entity may transmit a pre-paging message with the pre-paging UE ID to the UE. The UE may respond to the pre-paging message based at least in part on the pre-paging UE ID. In some aspects, the UE may derive the pre-paging UE ID with information included in a paging message. In this way, a UE may respond to a pre-paging message even if the UE is not in good coverage. The network may avoid having to resend a pre-paging resource allocation for the UE. As a result, pre-paging may be successful. Also, latency may be reduced and signaling resources may be conserved because paging messages are not wasted.

FIG.6AandFIG.6Bare diagrams illustrating an example600of configuring pre-paging, in accordance with the present disclosure. Example600shows a UE610(e.g., UE120) and a RAN network entity620(e.g., network node110, referred to as “RAN620”) that may communicate with one another in a wireless network (e.g., wireless network100). The RAN620may communicate with AMF630(e.g., AMF440), which is located in a 5G core network (e.g., core network405).

As shown by reference number632inFIG.6A, the UE610may be registered with the AMF630over a NAS layer, which is a functional layer between the UE610and the core network. The UE610and the AMF630may establish a first UE ID, or a pre-paging UE ID used for monitoring pre-paging. As shown by reference number634, the UE610and the AMF630may establish the pre-paging UE ID. As shown by reference number636, the AMF630may derive the pre-paging UE ID from a second UE ID (e.g., 5G S-TMSI) or from geographical area information of a UE, a bit map, a masking function, a preconfigured function (e.g., configured by the network), or a predefined function (e.g., defined in a standard). A bitmap may include a second set of bits that are translated from a first set of bits for a UE ID. A mask may include a subset of the bits used for a UE ID. A function may include the addition of information, such as location information or an area code. For example, the pre-paging ID may include the X most significant bits of the 5G-S-TMSI plus an area code. The second UE ID may be a code that is shorter in length than the 5G S-TMSI. As part of establishing the pre-paging ID, as shown by reference number638, the AMF630may transmit the pre-paging UE ID to the UE610. The UE610may store the pre-paging UE ID for later pre-paging monitoring. As shown by reference number640, the UE610may transmit a registration complete message. The registration complete message may indicate that the UE610has accepted the pre-paging UE ID. In some aspects, the UE610may derive the pre-paging UE ID from the second UE ID (e.g., 5G S-TMSI) or from geographical area information of a UE, a bit map, a masking function, a preconfigured function (e.g., configured by the network), or a predefined function (e.g., defined in a standard).

The AMF630and the UE610may now be familiar with at least two UE IDs. A first UE ID may be the pre-paging UE ID642that is associated with pre-paging or specific to pre-paging (used for pre-paging and not paging). A first UE ID associated with pre-paging may mean that the first UE ID is the pre-paging UE ID, is to be used for pre-paging, or corresponds to pre-paging. The first UE ID may be a UE ID that is used for enhanced paging or paging for coverage enhancements. A second UE ID may be an original or legacy UE ID644, such as the 5G-TMSI. The UE610and the AMF630may establish the paging UE ID at UE registration. This may include the UE610sharing its paging UE ID or the AMF630assigning the paging UE ID. The paging UE ID (second UE ID) may be what has typically been transmitted with a paging request from the AMF630. A paging request may include a request for paging or a request that initiates paging. However, in example600, the pre-paging UE ID (first UE ID) may be what is transmitted in a pre-paging request. A pre-paging request may include a request for pre-paging or a request that initiates pre-paging.

As shown by reference number646, the RAN620may transmit a pre-paging configuration. The pre-paging configuration may include information for monitoring pre-paging and for receiving pre-paging messages. The pre-paging configuration may indicate time domain resources, frequency domain resources, and/or code domain resources for monitoring pre-paging. The pre-paging configuration may include a a temporary UE ID (e.g., RNTI) or other information associated with scrambling a pre-paging message.

In some cases, the UE610may change state or move to less reliable coverage. As shown by reference number648, there may be an RLC or RRC release, which may result from a loss or ending of an RRC connected state. As shown by reference number650, the UE610may move to an RRC idle state. As shown by reference number652, the UE610may start monitoring for paging messages. As shown by reference number654, the UE610may move into deep coverage, which may include less reliable coverage. The location of the UE610may cause paging signaling to be unsuccessful. As shown by reference number656, the UE610may monitor for pre-paging messages that include the pre-paging ID. The pre-paging messages may be on a pre-paging channel and/or may be shorter messages such that the UE610may be more likely to receive and respond to a pre-paging message than a paging message.

Meanwhile, the UE context may be released. As shown by reference number658, the RAN620may transit a UE context release request. As shown by reference number660, the AMF630may transmit a UE context release command. As shown by reference number662, the UE context may be released at the RAN620.

Example600continues fromFIG.6AtoFIG.6B, where the UE610is monitoring for pre-paging messages that include the pre-paging UE ID, as shown by reference number652. The UE610may monitor a pre-paging channel that is the same or different than a paging channel. As shown by reference number664, the AMF630may transmit a request with information associated with the pre-paging ID. The information associated with the pre-paging UE ID may include the pre-paging UE ID, the paging UE ID, and/or information used to derive the pre-paging UE ID. Information used to derive the pre-paging UE ID may include a 5G S-TMSI (which may be the paging UE ID), geographical area information of a UE, a bit map, a masking function, a preconfigured function, or a predefined function.

The request with information associated with the pre-paging UE ID may include one of at least four options for initiating pre-paging. Pre-paging may be initiated with a pre-paging request by the AMF630or with a paging request by the AMF630. If the AMF630transmits a paging request, it may be up to the RAN620to determine whether to perform pre-paging rather than paging. In some aspects (option1), as shown by reference number666, the AMF630may transmit a pre-paging request with the pre-paging UE ID.

In some aspects (option2), as shown by reference number668, the AMF630may transmit a pre-paging request with the paging UE ID and information associated with deriving the pre-paging UE ID. As shown by reference number670, the RAN620may derive the pre-paging UE ID from the information associated with deriving the pre-paging UE ID.

In some aspects (option3), as shown by reference number672, the AMF630may transmit a paging request with the pre-paging UE ID. As shown by reference number674, the UE may determine to pre-page based at least in part on receiving the pre-paging UE ID with the regular paging request.

In some aspects (option4), as shown by reference number676, the AMF may transmit a paging request with information associated with deriving the pre-paging UE ID. As shown by reference number678, the RAN620may derive the pre-paging UE ID from the information. In option3or4, the paging request may include (or the information may include) an indication (e.g., flag) that the paging request is meant to be a pre-paging request.

As shown by reference number680, the RAN620may pre-page with the pre-paging UE ID. This may include transmitting a pre-paging message including the pre-paging UE ID on a pre-paging channel. The UE610, which is monitoring for a pre-paging message with the pre-paging UE ID, may detect that the pre-paging message is for the UE610. In some aspects, the pre-paging UE ID may be a code that is used to encode pre-paging resources (e.g., scrambling the DCI cyclic redundancy check (CRC) bits) instead of including the code in the paging PDSCH, as in the legacy operation.

In some aspects, the UE610may respond to the pre-paging message. The UE610may respond by alerting the user to move to better coverage, transmitting a response message, awaiting a paging message, or transmitting an RA preamble message.

In some aspects, the pre-paging UE ID may be or may include a geographic location-specific ID. The pre-paging UE ID may be valid in only certain geographic locations, such as in certain countries. The pre-paging UE ID will not work (UE will not respond) in invalid geographical locations (e.g., not registered in a country).

In some aspects, the AMF630may use a timer682that is associated with a pre-paging request. For example, in some aspects, the AMF630may first request paging in the legacy manner and start the timer682(e.g., timer T3513). The timer682may expire and the AMF630may transmit the pre-paging request based at least in part on the expiration of the timer682.

In some aspects, the timer682may be a pre-paging timer. The AMF630may start the timer682when the request is transmitted. When the timer682expires, the AMF630may transmit a new request. The AMF630may refrain from transmitting a request during the timer682. In some aspects, the AMF630may abandon paging for a while if the timer682expires. The AMF630may stop the timer682if a response to the request is received.

In some aspects, as shown by reference number684inFIG.6A, the UE610may transmit an indication of a UE capability to monitor pre-paging. For example, a UE paging information field may include a new flag for pre-paging. The AMF630may establish a pre-paging UE ID and transmit a pre-paging request based at least in part on the UE610having a UE capability to monitor pre-paging.

By establishing and using a pre-paging UE ID for the UE610, the AMF630may help the UE610to detect a pre-paging message without additional operations or resource allocations for pre-paging. This reduces latency and conserves signaling resources.

As indicated above,FIG.6AandFIG.6Bare provided as an example. Other examples may differ from what is described with regard toFIG.6AandFIG.6B.

FIG.7is a diagram illustrating an example700of configuring pre-paging, in accordance with the present disclosure.

In some aspects, the AMF may store UE-specific pre-paging resources (e.g., code or temporary UE ID, such as an RNTI) assigned to the UE for pre-paging resource monitoring across multiple cells/group IDs and codes). For example, the AMF may maintain a database of the codes or temporary UE IDs assigned to a UE. In some aspects, the AMF may generate a mapping between a pre-paging configuration (e.g., including an assigned code or temporary UE ID) and a UE paging identity for the UE (paging UE ID). The AMF may transmit a paging request with the pre-paging configuration and the paging UE ID to a RAN network entity. The RAN network entity may pre-page using the pre-paging configuration (with the temporary UE ID). The UE may monitor for pre-paging with the temporary UE ID and receive the pre-paging message. In this way, the AMF may indicate the code or temporary UE ID assigned to the UE (in the pre-paging configuration) when the AMF transmits the paging request to the RAN network entity. By maintaining a mapping assigned to the UE (e.g., in a database), the RAN network entity may avoid having to resend a pre-paging resource allocation. As a result, pre-paging will be successful. Latency may be reduced and signaling resources may be conserved if paging messages do not fail.

Example700shows an AMF that maintains a mapping of a pre-paging configuration to a UE for pre-paging. As shown by reference number702, the RAN620may transmit a pre-paging configuration that includes a temporary UE ID (e.g., RNTI established by the RAN620). The pre-paging configuration may include UE-specific pre-paging resources, such as a time domain resource, frequency domain resource, and/or a code domain resource. The code domain resource may include a code (e.g., the RNTI) assigned to the UE for pre-paging resource monitoring across multiple cells/group IDs and codes.

As shown by reference number704, the UE610may encounter an RLC or RRC release. As shown by reference number706, the UE610may move to an RRC idle state.

As shown by reference number708, the RAN620may transmit an NGAP pre-paging configuration setup message. This message may be part of an NGAP procedure, which involves communications between the RAN620and the AMF630to support UEs. NGAP procedures may be applicable to both 3GPP access and non-3GPP access. The setup message may include the pre-paging configuration. The message may be indexed with the UE610over an NG interface. The AMF630may link the temporary UE ID to a permanent UE ID, such as the paging UE ID. This temporary UE ID may be referred to as a first UE ID. The paging UE ID may be referred to as a second UE ID. The second UE ID may be associated with the first UE ID. That is, the second UE ID may correspond to or may be linked to the first UE ID.

The AMF630may maintain a table of paging UE IDs and pre-paging configurations. The paging UE ID may be a more permanent UE ID. As shown by reference number710, the AMF630and may generate a mapping between the paging UE ID (second UE ID) to one or more pre-paging configurations. A pre-paging configuration may indicate a time and frequency resource assignment for pre-paging and a temporary UE ID (first UE ID). The assignment and the temporary UE ID may only be valid for a certain amount of time. The assignment and the temporary UE ID may be associated with a setup time (when the temporary UE ID starts to be valid) and a validity duration (how long the temporary UE ID is valid). The AMF630may record the setup time and validity duration of the resource. After the validity duration, the AMF630may clear the temporary UE ID records.

For some reason, the UE context may be released. As shown by reference number712, the RAN620may transmit a UE context release request. As shown by reference number714, the UE610may enter deep coverage. As shown by reference number716, the UE610may monitor for pre-paging with a UE ID (e.g., temporary UE ID or first UE ID). In some aspects, the UE610may monitor for pre-paging with a paging UE ID (second UE ID). In some aspects, the UE610may monitor for pre-paging with a pre-paging UE ID that is specific to pre-paging and that was established at or near the time of UE registrations. The UE610may monitor for pre-paging messages on a pre-paging channel.

The AMF630may transmit a request associated with paging. The request may be a paging request with the paging UE ID. In some aspects, the request may include a paging request and a pre-paging request. For example, as shown by reference number718, the paging request may include a paging request with a pre-paging indication (e.g., pre-paging flag). The request may be an NGAP paging request message.

The RAN620may decide whether to use legacy paging or pre-paging to the UE610. The RAN620may decide to perform pre-paging. As shown by reference number720, the RAN620may begin pre-paging. The RAN may pre-page using the pre-paging configuration (with the temporary UE ID). This may include transmitting a pre-paging message with the temporary UE ID on a pre-paging channel. In some aspects, the pre-paging message may include the second UE ID (paging UE ID) or a pre-paging UE ID that was established between the UE610and the AMF630.

By maintaining pre-paging configurations for UEs, the AMF630does not have to reallocate paging resources after a UE context is cleared. This helps pre-paging to be successful and may reduce latency and conserve signaling resources.

FIG.8is a diagram illustrating an example800of configuring pre-paging, in accordance with the present disclosure.

In some aspects, RAN620may split the pre-paging configuration into two parts. There may be a cell-specific part (first part) and a dedicated/UE-specific part (second part). As shown by reference number802, the RAN620may transmit the first part in system information (SI). As shown by reference number804, the UE610may enter an RRC connected state. As shown by reference number806, the RAN620may transmit the second part of the pre-paging configuration.

As shown by reference number808, the RAN620may transmit a NGAP pre-paging configuration setup message. This message may be part of an NGAP procedure, which involves communications between the RAN620and the AMF630to support UEs. The setup message may include the pre-paging configuration. The message may be indexed with the UE610over an NG interface. The AMF may map a temporary UE ID in the pre-paging configuration to a permanent UE ID, such as the UE paging identity (e.g., paging UE ID).

The AMF630may maintain a table of paging UE IDs and pre-paging configurations. A paging UE ID may be a more permanent UE ID. As shown by reference number810, the AMF630and may generate a mapping812between the paging UE ID (second UE ID) to one or more pre-paging configurations. The assignment and the temporary UE ID of the pre-paging configuration may only be valid for a certain amount of time. The assignment and the temporary UE ID may be associated with a setup time (when the temporary UE ID starts to be valid) and a validity duration (how long the temporary UE ID is valid). The AMF may record the setup time and validity duration of the resource. After the validity duration, the AMF may clear the temporary UE ID records.

As shown by reference number814, the UE610may encounter an RLC or RRC release. As shown by reference number816, the UE610may move to an RRC idle state. As shown by reference number818, the UE610may enter deep coverage. As shown by reference number820, the UE610may monitor for pre-paging with the temporary UE ID (first UE ID). In some aspects, the UE610may monitor for pre-paging with a paging UE ID (second UE ID). In some aspects, the UE610may monitor for pre-paging with a pre-paging UE ID that is specific to pre-paging and that was established at or near the time of UE registration. The UE610may monitor for pre-paging messages on a pre-paging channel. As shown by reference number822, the RAN620may transmit a UE context release request.

The AMF630may transmit a request associated with paging. The request may include a paging request and a pre-paging request. For example, as shown by reference number824, the paging request may include a paging request with a pre-paging indication (e.g., pre-paging flag).

As shown by reference number826, the RAN620may determine whether to use legacy paging or pre-paging to the UE610. As shown by reference number828, the RAN620may select the paging message, whether the paging message is a paging message or a pre-paging message. For example, the RAN620may decide to perform pre-paging (e.g., based on the pre-paging indication). The RAN620may select a pre-paging message. The RAN620may select a pre-paging message based at least in part on the pre-paging configuration. For example, the RAN620may select a pre-paging message that is appropriate for a resource allocation for the pre-paging message.

As shown by reference number830, the RAN620may begin pre-paging. This may include transmitting a pre-paging message on a pre-paging channel. The pre-paging message may include the temporary UE ID, the paging UE ID, or a pre-paging UE ID.

By having the RAN620decide to pre-page or page, the RAN620may have more flexibility in contacting the UE610. This reduces latency.

FIG.9is a diagram illustrating an example900of configuring pre-paging, in accordance with the present disclosure. Example900is similar to example800up through reference number820.

In some aspects, the AMF630may transmit a pre-paging request based at least in part on the expiration of a timer (e.g., timer T3513). For example, the AMF630may first request paging in the legacy manner. As shown by reference number902, the AMF630may start the timer. As shown by reference number904, the timer may expire. As shown by reference number906, the AMF630may transmit a pre-paging request based at least in part on the expiration of the timer. The pre-paging request may include UE-specific resource information. As shown by reference number908, the AMF630may start another timer (e.g., with a larger value). The RAN620may receive the request and pre-page the UE610on a pre-paging channel, as shown by reference number910.

By transmitting a pre-paging request based at least in part on a timer expiration of a paging request, the AMF630may give paging a change before pre-paging, but will start pre-paging right away. This reduces latency.

FIG.10is a diagram illustrating an example process1000performed, for example, at a first network entity or an apparatus of a first network entity, in accordance with the present disclosure. Example process1000is an example where the apparatus or the first network entity (e.g., network node110, core network node115, AMF630) performs operations associated with configuring pre-paging.

As shown inFIG.10, in some aspects, process1000may include establishing a first UE ID associated with pre-paging (block1010). For example, the first network entity (e.g., using communication manager160and/or pre-paging component1408, depicted inFIG.14) may establish a first UE ID associated with pre-paging, as described above.

As further shown inFIG.10, in some aspects, process1000may include transmitting, with information associated with the first UE ID, a request associated with paging to a second network entity (block1020). For example, the first network entity (e.g., using communication manager160and/or transmission component1404, depicted inFIG.14) may transmit, with information associated with the first UE ID, a request associated with paging to a second network entity, as described above.

In a first aspect, establishing the first UE ID includes transmitting the first UE ID, and receiving a registration complete message.

In a second aspect, alone or in combination with the first aspect, transmitting the request includes transmitting the request in response to receiving a UE context release message.

In a third aspect, alone or in combination with one or more of the first and second aspects, the information associated with the first UE ID includes the first UE ID, and the request is a pre-paging request.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the information associated with the first UE ID includes a second UE ID and information associated with deriving the first UE ID, and the request is a pre-paging request.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the information associated with the first UE ID includes the first UE ID, and the request is a paging request.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the information associated with the first UE ID includes information associated with deriving the first UE ID, and the request is a paging request.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, the information associated with deriving the first UE ID includes one or more of a second UE ID associated with the UE, a 5G S-TMSI, geographical area information of a UE, a bit map, a masking function, a preconfigured function, or a predefined function.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, process1000includes deriving the first UE ID from one or more of a second UE ID associated with the UE (e.g., paging UE ID or other identity associated with paging), a 5G S-TMSI associated with a UE, geographical area information of a UE, a bit map, a masking function, a preconfigured function, or a predefined function.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the first UE ID is shorter in length than the 5G S-TMSI.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, process1000includes maintaining a timer associated with pre-paging that starts based at least in part on the request, and transmitting a new request based at least in part on expiration of the timer.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, process1000includes receiving an indication of a UE capability to monitor pre-paging, and transmitting the request includes transmitting the request based at least in part on the UE capability.

FIG.11is a diagram illustrating an example process1100performed, for example, at a UE or an apparatus of a UE, in accordance with the present disclosure. Example process1100is an example where the apparatus or the UE (e.g., UE120, UE610) performs operations associated with configuring pre-paging.

As shown inFIG.11, in some aspects, process1100may include establishing a first UE ID associated with pre-paging (block1110). For example, the UE (e.g., using communication manager140and/or pre-paging component1708, depicted inFIG.17) may establish a first UE ID associated with pre-paging, as described above.

As further shown inFIG.11, in some aspects, process1100may include monitoring for the first UE ID in a pre-paging message (block1120). For example, the UE (e.g., using communication manager140and/or monitoring component1710, depicted inFIG.17) may monitor for the first UE ID in a pre-paging message, as described above.

In a first aspect, establishing the first UE ID includes receiving the first UE ID, and transmitting a registration complete message.

In a second aspect, alone or in combination with the first aspect, process1100includes transmitting an indication of a UE capability to monitor pre-paging.

FIG.12is a diagram illustrating an example process1200performed, for example, at a first network entity or an apparatus of a first network entity, in accordance with the present disclosure. Example process1200is an example where the apparatus or the first network entity (e.g., network node110, core network node115, AMF630) performs operations associated with configuring pre-paging.

As shown inFIG.12, in some aspects, process1200may include receiving a pre-paging configuration with a first UE ID (block1210). For example, the first network entity (e.g., using communication manager160and/or reception component1402, depicted inFIG.14) may receive a pre-paging configuration with a first UE ID, as described above.

As further shown inFIG.12, in some aspects, process1200may include generating a mapping between the pre-paging configuration and a second UE ID associated with the first UE ID (block1220). For example, the first network entity (e.g., using communication manager160and/or mapping component1410, depicted inFIG.14) may generate a mapping between the pre-paging configuration and a second UE ID associated with the first UE ID, as described above.

As further shown inFIG.12, in some aspects, process1200may include transmitting a request associated with paging with the second UE ID and the pre-paging configuration (block1230). For example, the first network entity (e.g., using communication manager160and/or transmission component1404, depicted inFIG.14) may transmit a request associated with paging with the second UE ID and the pre-paging configuration, as described above.

In a first aspect, the pre-paging configuration indicates a time and frequency resource assignment for pre-paging and a temporary UE ID as the first UE ID.

In a second aspect, alone or in combination with the first aspect, the time and frequency resource assignment and the temporary UE ID are associated with a setup time and a validity duration.

In a third aspect, alone or in combination with one or more of the first and second aspects, the request is a pre-paging request, and transmitting the request includes transmitting the request based at least in part on an expiration of a timer that starts after a paging request.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, transmitting the request includes transmitting the request in response to receiving a UE context release message.

FIG.13is a diagram illustrating an example process1300performed, for example, at a second network entity or an apparatus of a second network entity, in accordance with the present disclosure. Example process1300is an example where the apparatus or the second network entity (e.g., network node110, RAN network entity620) performs operations associated with configuring pre-paging.

As shown inFIG.13, in some aspects, process1300may include receiving, with information associated with a first UE ID, a request associated with paging from a first network entity (block1310). For example, the second network entity (e.g., using communication manager150and/or reception component2002, depicted inFIG.20) may receive, with information associated with a first UE ID, a request associated with paging from a first network entity, as described above.

As further shown inFIG.13, in some aspects, process1300may include transmitting a pre-paging message to a UE associated with the first UE ID (block1320). For example, the second network entity (e.g., using communication manager150and/or transmission component2004, depicted inFIG.20) may transmit a pre-paging message to a UE associated with the first UE ID, as described above.

In a first aspect, the information associated with the first UE ID includes the first UE ID, and the request is a pre-paging request.

In a second aspect, alone or in combination with the first aspect, the information associated with the first UE ID includes a second UE ID and information associated with deriving the first UE ID, and the request is a pre-paging request.

In a third aspect, alone or in combination with one or more of the first and second aspects, the information associated with deriving the first UE ID includes one or more of a 5G S-TMSI, geographical area information of a UE, a bit map, a masking function, or a predefined function.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the information associated with the first UE ID includes the first UE ID, and the request is a paging request.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the information associated with the first UE ID includes information associated with deriving the first UE ID, where the request is a paging request, and process1300includes deriving the first UE ID based at least in part on the information associated with deriving the first UE ID.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, process1300includes selecting the pre-paging message.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, process1300includes transmitting a pre-paging configuration with the first UE ID to the first network entity, and receiving the request includes receiving the request with the pre-paging configuration.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the pre-paging configuration indicates a time and frequency resource assignment by the second network entity.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, receiving the request includes receiving the request in response to transmitting a UE context release message.

FIG.14is a diagram of an example apparatus1400for wireless communication, in accordance with the present disclosure. The apparatus1400may be a first network entity (e.g., network node110, core network node115, AMF630), or a first network entity may include the apparatus1400. In some aspects, the apparatus1400includes a reception component1402and a transmission component1404, which may be in communication with one another (for example, via one or more buses and/or one or more other components). As shown, the apparatus1400may communicate with another apparatus1406(such as a UE, a base station, or another wireless communication device) using the reception component1402and the transmission component1404. As further shown, the apparatus1400may include the communication manager160. The communication manager160may include a pre-paging component1408and/or a mapping component1410, among other examples.

The transmission component1404may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus1406. In some aspects, one or more other components of the apparatus1400may generate communications and may provide the generated communications to the transmission component1404for transmission to the apparatus1406. In some aspects, the transmission component1404may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus1406. In some aspects, the transmission component1404may include one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers/processors, one or more memories, or a combination thereof, of the first network entity described in connection withFIG.2. In some aspects, the transmission component1404may be co-located with the reception component1402in one or more transceivers.

In some aspects, the pre-paging component1408may establish a first UE ID associated with pre-paging. The transmission component1404may transmit, with information associated with the first UE ID, a request associated with paging to a second network entity.

The pre-paging component1408may derive the first UE ID from one or more of a paging UE ID, a 5G S-TMSI associated with a UE, geographical area information of a UE, a bit map, a masking function, a preconfigured function, a predefined function, and/or other UE identity information.

The pre-paging component1408may maintain a timer associated with pre-paging that starts based at least in part on the request. The transmission component1404may transmit a new request based at least in part on expiration of the timer.

The reception component1402may receive an indication of a UE capability to monitor pre-paging, and the transmission component1404may transmit the request based at least in part on the UE capability.

In some aspects, the reception component1402may receive a pre-paging configuration with a first UE ID. The mapping component1410may generate a mapping between the pre-paging configuration and a second UE ID associated with the first UE ID. The transmission component1404may transmit a request associated with paging with the second UE ID and the pre-paging configuration.

FIG.15is a diagram illustrating an example1500of a hardware implementation for an apparatus1505employing a processing system1510, in accordance with the present disclosure. The apparatus1505may be a first network entity or may be at (e.g., included in) a first network entity.

The processing system1510may be implemented with a bus architecture, represented generally by the bus1515. The bus1515may include any number of interconnecting buses and bridges depending on the specific application of the processing system1510and the overall design constraints. The bus1515links together various circuits including one or more processors and/or hardware components, represented by the processor (or processing circuitry)1520, the illustrated components, and the computer-readable medium/memory (or memory circuitry)1525. The processor1520may include multiple processors, such as processor1520a, memory1520b, and memory1520c. The memory1525may include multiple memories, such as memory1525a, memory1525b, and memory1525c. The bus1515may also link various other circuits, such as timing sources, peripherals, voltage regulators, and/or power management circuits.

The processing system1510may be coupled to one or more transceivers1530. A transceiver1530is coupled to one or more antennas1535. The transceiver1530provides a means for communicating with various other apparatuses over a transmission medium. The transceiver1530receives a signal from the one or more antennas1535, extracts information from the received signal, and provides the extracted information to the processing system1510, specifically the reception component1402. In addition, the transceiver1530receives information from the processing system1510, specifically the transmission component1404, and generates a signal to be applied to the one or more antennas1535based at least in part on the received information.

The processing system1510includes one or more processors1520coupled to a computer-readable medium/memory1525. A processor1520is responsible for general processing, including the execution of software stored on the computer-readable medium/memory1525. The software, when executed by the processor1520, causes the processing system1510to perform the various functions described herein for any particular apparatus. The computer-readable medium/memory1525may also be used for storing data that is manipulated by the processor1520when executing software. The processing system further includes at least one of the illustrated components. The components may be software modules running in the processor1520, resident/stored in the computer readable medium/memory1525, one or more hardware modules coupled to the processor1520, or some combination thereof.

In some aspects, the processing system1510may be a component of the network node110and may include one or more memories, such as the memory242, and/or may include one or more processors, such as at least one of the TX MIMO processor230, the RX processor238, and/or the controller/processor240. In some aspects, the apparatus1505for wireless communication includes means for establishing a first UE ID associated with pre-paging; and means for transmitting, with information associated with the first UE ID, a request associated with paging to a second network entity. In some aspects, the apparatus1505for wireless communication includes means receiving a pre-paging configuration with a first UE ID; means for generating a mapping between the pre-paging configuration and a second UE ID associated with the first UE ID; and means for transmitting a request associated with paging with the second UE ID and the pre-paging configuration. The aforementioned means may be one or more of the aforementioned components of the apparatus1400and/or the processing system1510of the apparatus1505configured to perform the functions recited by the aforementioned means. As described elsewhere herein, the processing system1510may include the TX MIMO processor230, the receive processor238, and/or the controller/processor240. In one configuration, the aforementioned means may be the TX MIMO processor230, the receive processor238, and/or the controller/processor240configured to perform the functions and/or operations recited herein.

FIG.15is provided as an example. Other examples may differ from what is described in connection withFIG.15.

FIG.16is a diagram illustrating an example1600of an implementation of code and circuitry for an apparatus1605, in accordance with the present disclosure. The circuitry may include processing circuitry and memory circuitry. The apparatus1605may be a first network entity, or a first network entity may include the apparatus1605.

As shown inFIG.16, the apparatus1605may include circuitry for establishing a first UE ID associated with pre-paging (circuitry1620). For example, the circuitry1620may enable the apparatus1605to establish a first UE ID associated with pre-paging.

As shown inFIG.16, the apparatus1605may include, stored in computer-readable medium1525, code for establishing a first UE ID associated with pre-paging (code1625). For example, the code1625, when executed by processor1520, may cause processor1520to cause transceiver1530to establish a first UE ID associated with pre-paging.

As shown inFIG.16, the apparatus1605may include circuitry for transmitting, with information associated with the first UE ID, a request associated with paging to a second network entity (circuitry1630). For example, the circuitry1630may enable the apparatus1605to transmit, with information associated with the first UE ID, a request associated with paging to a second network entity.

As shown inFIG.16, the apparatus1605may include, stored in computer-readable medium1525, code for transmitting, with information associated with the first UE ID, a request associated with paging to a second network entity (code1635). For example, the code1635, when executed by processor1520, may cause processor1520to cause transceiver1530to transmit, with information associated with the first UE ID, a request associated with paging to a second network entity.

As shown inFIG.16, the apparatus1605may include circuitry for receiving a pre-paging configuration with a first UE ID (circuitry1640). For example, the circuitry1640may enable the apparatus1605to receive a pre-paging configuration with a first UE ID.

As shown inFIG.16, the apparatus1605may include, stored in computer-readable medium1525, code for receiving a pre-paging configuration with a first UE ID (code1645). For example, the code1645, when executed by processor1520, may cause processor1520to cause transceiver1530to receive a pre-paging configuration with a first UE ID.

As shown inFIG.16, the apparatus1605may include circuitry for generating a mapping between the pre-paging configuration and a second UE ID associated with the first UE ID (circuitry1650). For example, the circuitry1650may enable the apparatus1605to generate a mapping between the pre-paging configuration and a second UE ID associated with the first UE ID.

As shown inFIG.16, the apparatus1605may include, stored in computer-readable medium1525, code for generating a mapping between the pre-paging configuration and a second UE ID associated with the first UE ID (code1655). For example, the code1655, when executed by processor1520, may cause processor1520generate a mapping between the pre-paging configuration and a second UE ID associated with the first UE ID.

As shown inFIG.16, the apparatus1605may include circuitry for transmitting a request associated with paging with the second UE ID and the pre-paging configuration (circuitry1660). For example, the circuitry1660may enable the apparatus1605to transmit a request associated with paging with the second UE ID and the pre-paging configuration.

As shown inFIG.16, the apparatus1605may include, stored in computer-readable medium1525, code for transmitting a request associated with paging with the second UE ID and the pre-paging configuration (code1665). For example, the code1665, when executed by processor1520, may cause processor1520to cause transceiver1530to transmit a request associated with paging with the second UE ID and the pre-paging configuration.

FIG.16is provided as an example. Other examples may differ from what is described in connection withFIG.16.

FIG.17is a diagram of an example apparatus1700for wireless communication, in accordance with the present disclosure. The apparatus1700may be a UE (e.g., UE120, UE610), or a UE may include the apparatus1700. In some aspects, the apparatus1700includes a reception component1702and a transmission component1704, which may be in communication with one another (for example, via one or more buses and/or one or more other components). As shown, the apparatus1700may communicate with another apparatus1706(such as a UE, a base station, or another wireless communication device) using the reception component1702and the transmission component1704. As further shown, the apparatus1700may include the communication manager140. The communication manager140may include a pre-paging component1708and/or a monitoring component1710, among other examples.

In some aspects, the apparatus1700may be configured to perform one or more operations described herein in connection withFIGS.1-9. Additionally, or alternatively, the apparatus1700may be configured to perform one or more processes described herein, such as process1100ofFIG.11. In some aspects, the apparatus1700and/or one or more components shown inFIG.17may include one or more components of the UE described in connection withFIG.2. Additionally, or alternatively, one or more components shown inFIG.17may be implemented within one or more components described in connection withFIG.2. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in one or more memories. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the functions or operations of the component.

The transmission component1704may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus1706. In some aspects, one or more other components of the apparatus1700may generate communications and may provide the generated communications to the transmission component1704for transmission to the apparatus1706. In some aspects, the transmission component1704may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus1706. In some aspects, the transmission component1704may include one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers/processors, one or more memories, or a combination thereof, of the UE described in connection withFIG.2. In some aspects, the transmission component1704may be co-located with the reception component1702in one or more transceivers.

The pre-paging component1708may establish a first UE ID associated with pre-paging. The monitoring component1710may monitor for the first UE ID in a pre-paging message. The transmission component1704may transmit an indication of a UE capability to monitor pre-paging.

In some aspects, the pre-paging component1408may derive the first UE ID from one or more of a paging UE ID, a 5G S-TMSI associated with a UE, geographical area information of a UE, a bit map, a masking function, a preconfigured function, a predefined function, and/or other UE identity information.

FIG.18is a diagram illustrating an example1800of a hardware implementation for an apparatus1805employing a processing system1810, in accordance with the present disclosure. The apparatus1805may be a UE or may be at (e.g., included in) a UE.

The processing system1810may be implemented with a bus architecture, represented generally by the bus1815. The bus1815may include any number of interconnecting buses and bridges depending on the specific application of the processing system1810and the overall design constraints. The bus1815links together various circuits including one or more processors and/or hardware components, represented by the processor (or processing circuitry)1820, the illustrated components, and the computer-readable medium/memory (or memory circuitry)1825. The processor1820may include multiple processors, such as processor1820a, memory1820b, and memory1820c. The memory1825may include multiple memories, such as memory1825a, memory1825b, and memory1825c. The bus1815may also link various other circuits, such as timing sources, peripherals, voltage regulators, and/or power management circuits.

The processing system1810may be coupled to one or more transceivers1830. A transceiver1830is coupled to one or more antennas1835. The transceiver1830provides a means for communicating with various other apparatuses over a transmission medium. The transceiver1830receives a signal from the one or more antennas1835, extracts information from the received signal, and provides the extracted information to the processing system1810, specifically the reception component1702. In addition, the transceiver1830receives information from the processing system1810, specifically the transmission component1704, and generates a signal to be applied to the one or more antennas1835based at least in part on the received information.

The processing system1810includes one or more processors1820coupled to a computer-readable medium/memory1825. A processor1820is responsible for general processing, including the execution of software stored on the computer-readable medium/memory1825. The software, when executed by the processor1820, causes the processing system1810to perform the various functions described herein for any particular apparatus. The computer-readable medium/memory1825may also be used for storing data that is manipulated by the processor1820when executing software. The processing system further includes at least one of the illustrated components. The components may be software modules running in the processor1820, resident/stored in the computer readable medium/memory1825, one or more hardware modules coupled to the processor1820, or some combination thereof.

In some aspects, the processing system1810may be a component of the UE120and may include one or more memories, such as the memory282, and/or May include one or more processors, such as at least one of the TX MIMO processor266, the RX processor258, and/or the controller/processor280. In some aspects, the apparatus1805for wireless communication includes means for establishing a first UE ID associated with pre-paging; and means for monitoring for the first UE ID in a pre-paging message. The aforementioned means may be one or more of the aforementioned components of the apparatus1700and/or the processing system1810of the apparatus1805configured to perform the functions recited by the aforementioned means. As described elsewhere herein, the processing system1810may include the TX MIMO processor266, the RX processor258, and/or the controller/processor280. In one configuration, the aforementioned means may be the TX MIMO processor266, the RX processor258, and/or the controller/processor280configured to perform the functions and/or operations recited herein.

FIG.18is provided as an example. Other examples may differ from what is described in connection withFIG.18.

FIG.19is a diagram illustrating an example1900of an implementation of code and circuitry for an apparatus1905, in accordance with the present disclosure. The circuitry may include processing circuitry and memory circuitry. The apparatus1905may be a UE, or a UE may include the apparatus1905.

As shown inFIG.19, the apparatus1905may include circuitry for establishing a first UE ID associated with pre-paging (circuitry1920). For example, the circuitry1920may enable the apparatus1905to establish a first UE ID associated with pre-paging.

As shown inFIG.19, the apparatus1905may include, stored in computer-readable medium1825, code for establishing a first UE ID associated with pre-paging (code1925). For example, the code1925, when executed by processor1820, may cause processor1820to cause transceiver1830to establish a first UE ID associated with pre-paging.

As shown inFIG.19, the apparatus1905may include circuitry for monitoring for the first UE ID in a pre-paging message (circuitry1930). For example, the circuitry1930may enable the apparatus1905to monitor for the first UE ID in a pre-paging message.

As shown inFIG.19, the apparatus1905may include, stored in computer-readable medium1825, code for monitoring for the first UE ID in a pre-paging message (code1935). For example, the code1935, when executed by processor1820, may cause processor1820to cause transceiver1830to monitor for the first UE ID in a pre-paging message.

FIG.19is provided as an example. Other examples may differ from what is described in connection withFIG.19.

FIG.20is a diagram of an example apparatus2000for wireless communication, in accordance with the present disclosure. The apparatus2000may be a second network entity (e.g., network node110, RAN network entity620), or a second network entity may include the apparatus2000. In some aspects, the apparatus2000includes a reception component2002and a transmission component2004, which may be in communication with one another (for example, via one or more buses and/or one or more other components). As shown, the apparatus2000may communicate with another apparatus2006(such as a UE, a base station, or another wireless communication device) using the reception component2002and the transmission component2004. As further shown, the apparatus2000may include the communication manager150. The communication manager150may include a pre-paging component2008, among other examples.

In some aspects, the apparatus2000may be configured to perform one or more operations described herein in connection withFIGS.1-9. Additionally, or alternatively, the apparatus2000may be configured to perform one or more processes described herein, such as process1300ofFIG.13. In some aspects, the apparatus2000and/or one or more components shown inFIG.20may include one or more components of the second network entity described in connection withFIG.2. Additionally, or alternatively, one or more components shown inFIG.20may be implemented within one or more components described in connection withFIG.2. Additionally, or alternatively, one or more components of the set of components may be implemented at least in part as software stored in one or more memories. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the functions or operations of the component.

The reception component2002may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus2006. The reception component2002may provide received communications to one or more other components of the apparatus2000. In some aspects, the reception component2002may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples), and may provide the processed signals to the one or more other components of the apparatus2000. In some aspects, the reception component2002may include one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receive processors, one or more controllers/processors, one or more memories, or a combination thereof, of the second network entity described in connection withFIG.2.

The transmission component2004may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus2006. In some aspects, one or more other components of the apparatus2000may generate communications and may provide the generated communications to the transmission component2004for transmission to the apparatus2006. In some aspects, the transmission component2004may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples), and may transmit the processed signals to the apparatus2006. In some aspects, the transmission component2004may include one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers/processors, one or more memories, or a combination thereof, of the second network entity described in connection withFIG.2. In some aspects, the transmission component2004may be co-located with the reception component2002in one or more transceivers.

The reception component2002may receive, with information associated with a first UE ID, a request associated with paging from a first network entity. The transmission component2004may transmit a pre-paging message to a UE associated with the first UE ID.

The pre-paging component2008may select the pre-paging message. The transmission component2004may transmit a pre-paging configuration with the first UE ID to the first network entity, and wherein receiving the request includes receiving the request with the pre-paging configuration.

The number and arrangement of components shown inFIG.20are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown inFIG.20. Furthermore, two or more components shown inFIG.20may be implemented within a single component, or a single component shown inFIG.20may be implemented as multiple, distributed components. Additionally, or alternatively, a set of (one or more) components shown inFIG.20may perform one or more functions described as being performed by another set of components shown inFIG.20.

FIG.21is a diagram illustrating an example2100of a hardware implementation for an apparatus2105employing a processing system2110, in accordance with the present disclosure. The apparatus2105may be a second network entity or may be at (e.g., included in) a second network entity.

The processing system2110may be implemented with a bus architecture, represented generally by the bus2115. The bus2115may include any number of interconnecting buses and bridges depending on the specific application of the processing system2110and the overall design constraints. The bus2115links together various circuits including one or more processors and/or hardware components, represented by the processor (or processing circuitry)2120, the illustrated components, and the computer-readable medium/memory (or memory circuitry)2125. The processor2120may include multiple processors, such as processor2120a, memory2120b, and memory2120c. The memory2125may include multiple memories, such as memory2125a, memory2125b, and memory2125c. The bus2115may also link various other circuits, such as timing sources, peripherals, voltage regulators, and/or power management circuits.

The processing system2110may be coupled to one or more transceivers2130. A transceiver2130is coupled to one or more antennas2135. The transceiver2130provides a means for communicating with various other apparatuses over a transmission medium. The transceiver2130receives a signal from the one or more antennas2135, extracts information from the received signal, and provides the extracted information to the processing system2110, specifically the reception component2002. In addition, the transceiver2130receives information from the processing system2110, specifically the transmission component2004, and generates a signal to be applied to the one or more antennas2135based at least in part on the received information.

The processing system2110includes one or more processors2120coupled to a computer-readable medium/memory2125. A processor2120is responsible for general processing, including the execution of software stored on the computer-readable medium/memory2125. The software, when executed by the processor2120, causes the processing system2110to perform the various functions described herein for any particular apparatus. The computer-readable medium/memory2125may also be used for storing data that is manipulated by the processor2120when executing software. The processing system further includes at least one of the illustrated components. The components may be software modules running in the processor2120, resident/stored in the computer readable medium/memory2125, one or more hardware modules coupled to the processor2120, or some combination thereof.

In some aspects, the processing system2110may be a component of the network node110and may include one or more memories, such as the memory242, and/or may include one or more processors, such as at least one of the TX MIMO processor230, the RX processor238, and/or the controller/processor240. In some aspects, the apparatus2105for wireless communication includes means receiving, with information associated with a first UE ID, a request associated with paging from a first network entity; and means for transmitting a pre-paging message to a UE associated with the first UE ID. The aforementioned means may be one or more of the aforementioned components of the apparatus2000and/or the processing system2110of the apparatus2105configured to perform the functions recited by the aforementioned means. As described elsewhere herein, the processing system2110may include the TX MIMO processor230, the receive processor238, and/or the controller/processor240. In one configuration, the aforementioned means may be the TX MIMO processor230, the receive processor238, and/or the controller/processor240configured to perform the functions and/or operations recited herein.

FIG.21is provided as an example. Other examples may differ from what is described in connection withFIG.21.

FIG.22is a diagram illustrating an example2200of an implementation of code and circuitry for an apparatus2205, in accordance with the present disclosure. The circuitry may include processing circuitry and memory circuitry. The apparatus2205may be a second network entity, or a second network entity may include the apparatus2205.

As shown inFIG.22, the apparatus2205may include circuitry for receiving, with information associated with a first UE ID, a request associated with paging from a first network entity (circuitry2220). For example, the circuitry2220may enable the apparatus2205to receive, with information associated with a first UE ID, a request associated with paging from a first network entity.

As shown inFIG.22, the apparatus2205may include, stored in computer-readable medium2125, code for receiving, with information associated with a first UE ID, a request associated with paging from a first network entity (code2225). For example, the code2225, when executed by processor2120, may cause processor2120to cause transceiver2130to receive, with information associated with a first UE ID, a request associated with paging from a first network entity.

As shown inFIG.22, the apparatus2205may include circuitry for transmitting a pre-paging message to a UE associated with the first UE ID (circuitry2230). For example, the circuitry2230may enable the apparatus2205to transmit a pre-paging message to a UE associated with the first UE ID.

As shown inFIG.22, the apparatus2205may include, stored in computer-readable medium2125, code for transmitting a pre-paging message to a UE associated with the first UE ID (code2235). For example, the code2235, when executed by processor2120, may cause processor2120to cause transceiver2130to transmit a pre-paging message to a UE associated with the first UE ID.

FIG.22is provided as an example. Other examples may differ from what is described in connection withFIG.22.

Aspect 1: A method of wireless communication performed at a first network entity, comprising: establishing a first user equipment (UE) identifier (ID) associated with pre-paging; and transmitting, with information associated with the first UE ID, a request associated with paging to a second network entity.

Aspect 2: The method of Aspect 1, wherein establishing the first UE ID includes: transmitting the first UE ID; and receiving a registration complete message.

Aspect 3: The method of any of Aspects 1-2, wherein transmitting the request includes transmitting the request in response to receiving a UE context release message.

Aspect 4: The method of any of Aspects 1-3, wherein the information associated with the first UE ID includes the first UE ID, and wherein the request is a pre-paging request.

Aspect 5: The method of any of Aspects 1-3, wherein the information associated with the first UE ID includes a second UE ID and information associated with deriving the first UE ID, and wherein the request is a pre-paging request.

Aspect 6: The method of any of Aspects 1-3, wherein the information associated with the first UE ID includes the first UE ID, and wherein the request is a paging request.

Aspect 7: The method of any of Aspects 1-3, wherein the information associated with the first UE ID includes information associated with deriving the first UE ID, and wherein the request is a paging request.

Aspect 8: The method of Aspect 7, wherein the information associated with deriving the first UE ID includes one or more of a 5G serving temporary mobile subscriber identity (S-TMSI), geographical area information of a UE, a bit map, a masking function, a preconfigured function, or a predefined function.

Aspect 9: The method of any of Aspects 1-8, further comprising deriving the first UE ID from one or more of a second UE ID associated with the UE, a 5G serving temporary mobile subscriber identity (S-TMSI) associated with a UE, geographical area information of a UE, a bit map, a masking function, a preconfigured function, or a predefined function.

Aspect 10: The method of Aspect 9, wherein the first UE ID is shorter in length than the 5G S-TMSI.

Aspect 11: The method of any of Aspects 1-10, further comprising: maintaining a timer associated with pre-paging that starts based at least in part on the request; and transmitting a new request based at least in part on expiration of the timer.

Aspect 12: The method of any of Aspects 1-11, further comprising receiving an indication of a UE capability to monitor pre-paging, and wherein transmitting the request includes transmitting the request based at least in part on the UE capability.

Aspect 13: A method of wireless communication performed at a user equipment (UE), comprising: establishing a first UE ID associated with pre-paging; and monitoring for the first UE ID in a pre-paging message.

Aspect 14: The method of Aspect 13, wherein establishing the first UE ID includes: receiving the first UE ID; and transmitting a registration complete message.

Aspect 15: The method of any of Aspects 13-14, further comprising transmitting an indication of a UE capability to monitor pre-paging.

Aspect 16: A method of wireless communication performed at a first network entity, comprising: receiving a pre-paging configuration with a first user equipment (UE) identifier (ID); generating a mapping between the pre-paging configuration and a second UE ID associated with the first UE ID; and transmitting a request associated with paging with the second UE ID and the pre-paging configuration.

Aspect 17: The method of Aspect 16, wherein the pre-paging configuration indicates a time and frequency resource assignment for pre-paging and a temporary UE ID as the first UE ID.

Aspect 18: The method of Aspect 17, wherein the time and frequency resource assignment and the temporary UE ID are associated with a setup time and a validity duration.

Aspect 19: The method of Aspect 16, wherein the pre-paging configuration indicates a time and frequency resource assignment for pre-paging.

Aspect 20: The method of Aspect 19, wherein the time and frequency resource assignment is associated with a setup time.

Aspect 21: The method of Aspect 19, wherein the time and frequency resource assignment is associated with a validity duration.

Aspect 22: The method of Aspect 16, wherein the pre-paging configuration indicates a temporary UE ID.

Aspect 23: The method of Aspect 22, wherein the temporary UE ID is associated with a setup time.

Aspect 24: The method of Aspect 22, wherein the temporary UE ID is associated with a validity duration.

Aspect 25: The method of any of Aspects 16-24, wherein the request is a pre-paging request, and wherein transmitting the request includes transmitting the request based at least in part on an expiration of a timer that starts after a paging request.

Aspect 26: The method of any of Aspects 16-25, wherein transmitting the request includes transmitting the request in response to receiving a UE context release message.

Aspect 27: A method of wireless communication performed at a second network entity, comprising: receiving, with information associated with a first user equipment (UE) identifier (ID), a request associated with paging from a first network entity; and transmitting a pre-paging message to a UE associated with the first UE ID.

Aspect 28: The method of Aspect 27, wherein the information associated with the first UE ID includes the first UE ID, and wherein the request is a pre-paging request.

Aspect 29: The method of Aspect 27, wherein the information associated with the first UE ID includes a second UE ID and information associated with deriving the first UE ID, and wherein the request is a pre-paging request.

Aspect 30: The method of Aspect 29, wherein the information associated with deriving the first UE ID includes one or more of a second UE ID associated with the UE, a 5G serving temporary mobile subscriber identity (S-TMSI), geographical area information of a UE, a bit map, a masking function, or a predefined function.

Aspect 31: The method of Aspect 27, wherein the information associated with the first UE ID includes the first UE ID, and wherein the request is a paging request.

Aspect 32: The method of Aspect 27, wherein the information associated with the first UE ID includes information associated with deriving the first UE ID, wherein the request is a paging request, and wherein the method includes deriving the first UE ID based at least in part on the information associated with deriving the first UE ID.

Aspect 33: The method of any of Aspects 27-32, further comprising selecting the pre-paging message.

Aspect 34: The method of any of Aspects 27-33, further comprising transmitting a pre-paging configuration with the first UE ID to the first network entity, and wherein receiving the request includes receiving the request with the pre-paging configuration.

Aspect 35: The method of Aspect 34, wherein the pre-paging configuration indicates a time and frequency resource assignment by the second network entity.

Aspect 36: The method of any of Aspects 27-35, wherein receiving the request includes receiving the request in response to transmitting a UE context release message.

Aspect 39: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method of one or more of Aspects 1-36.

Aspect 44: An apparatus for wireless communication at a first network entity, comprising: a processing system that includes processor circuitry and memory circuitry that stores code and is coupled with the processor circuitry, the processing system configured to cause the first network entity to perform the method of one or more of Aspects 1-12 and 16-26.

Aspect 45: An apparatus for wireless communication at a user equipment (UE), comprising: a processing system that includes processor circuitry and memory circuitry that stores code and is coupled with the processor circuitry, the processing system configured to cause the UE to perform the method of one or more of Aspects 13-15.

Aspect 46: An apparatus for wireless communication at a second network entity, comprising: a processing system that includes processor circuitry and memory circuitry that stores code and is coupled with the processor circuitry, the processing system configured to cause the second network entity to perform the method of one or more of Aspects 27-36.

Aspect 48: An apparatus for wireless communication at a first network entity, comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors configured to cause the first network entity to: establishing a first user equipment (UE) identifier (ID) associated with pre-paging; and transmitting, with information associated with the first UE ID, a request associated with paging to a second network entity.

Aspect 49: The apparatus of Aspect 48, wherein the one or more processors are configured, individually or collectively, to cause the first network entity to: establish a first user equipment (UE) identifier (ID) associated with pre-paging; and transmit, with information associated with the first UE ID, a request associated with paging to a second network entity.

Aspect 50: An apparatus for wireless communication at a user equipment (UE), comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors configured to cause the UE to: establishing a first UE ID associated with pre-paging; and monitoring for the first UE ID in a pre-paging message.

Aspect 51: The apparatus of Aspect 50, wherein the one or more processors are configured, individually or collectively, to cause the UE to: establish a first UE ID associated with pre-paging; and monitor for the first UE ID in a pre-paging message.

Aspect 52: An apparatus for wireless communication at a first network entity, comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors configured to cause the first network entity to: receive a pre-paging configuration with a first user equipment (UE) identifier (ID); generate a mapping between the pre-paging configuration and a second UE ID associated with the first UE ID; and transmit a request associated with paging with the second UE ID and the pre-paging configuration.

Aspect 53: The apparatus of Aspect 52, wherein the one or more processors are configured, individually or collectively, to cause the first network entity to: receive a pre-paging configuration with a first user equipment (UE) identifier (ID); generate a mapping between the pre-paging configuration and a second UE ID associated with the first UE ID; and transmit a request associated with paging with the second UE ID and the pre-paging configuration.

Aspect 54: An apparatus for wireless communication at a second network entity, comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors configured to cause the second network entity to: receive, with information associated with a first user equipment (UE) identifier (ID), a request associated with paging from a first network entity; and transmit a pre-paging message to a UE associated with the first UE ID.

Aspect 55: The apparatus of Aspect 54, wherein the one or more processors are configured, individually or collectively, to cause the second network entity to: receive, with information associated with a first user equipment (UE) identifier (ID), a request associated with paging from a first network entity; and transmit a pre-paging message to a UE associated with the first UE ID.