WO2018161244A1

WO2018161244A1 - Paging offset negotiation

Info

Publication number: WO2018161244A1
Application number: PCT/CN2017/075856
Authority: WO
Inventors: Jiming Guo; Reza Shahidi; Arvind Santhanam; Xuepan GUAN; Kiran Patil; Bhupesh Umatt; Yongsheng Shi; Xipeng Zhu
Original assignee: Qualcomm Incorporated
Priority date: 2017-03-07
Filing date: 2017-03-07
Publication date: 2018-09-13

Abstract

Methods, systems, and devices for wireless communication are described. A wireless device may identify a collision of a first DRX wakeup occasion of a first radio access technology (RAT) and a second DRX wakeup occasion of a second RAT within a discontinuous reception (DRX) interval. The wireless device may identify an offset change for a DRX wakeup occasion of at least one RAT based on the collision. In some cases, the wireless device may transmit a paging offset change request message to a network node, such as a base station or core network node, based on the identified offset change. The wireless device may receive, from the network node, a paging offset acceptance message in response to the paging offset change request message indicating a timing offset for changing the first DRX wakeup occasion or the second DRX wakeup occasion. In some cases, the wireless device may receive an indication from the network node to change a wakeup occasion.

Description

PAGING OFFSET NEGOTIATION

BACKGROUND

The following relates generally to wireless communication, and more specifically to paging offset negotiation.

Wireless communications systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcast, and so on. These systems may be capable of supporting communication with multiple users by sharing the available system resources (e.g., time, frequency, and power) . Examples of such multiple-access systems include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, and orthogonal frequency division multiple access (OFDMA) systems, (e.g., a Long Term Evolution (LTE) system, or a New Radio (NR) system) . A wireless multiple-access communications system may include a number of base stations or access network nodes, each simultaneously supporting communication for multiple communication devices, which may be otherwise known as user equipment (UE) .

When a base station has information to transmit to a UE, the base station may transmit a paging message to prompt the UE to enter a connected state in order to receive the information. In some cases, a UE may have the capability of supporting multiple radio access technologies (RATs) , and may be referred to as a concurrent RAT (CRAT) UE. Each of the multiple RATs supported by the UE may be associated with a different paging occasion or wakeup time during a reception time interval. In some instances, the UE may need to wake up for a paging occasion for each of the multiple RATs. In such circumstances, the wakeup occasion and related interval to monitor paging for one RAT may overlap with the wakeup occasion and related interval of another RAT. Due to limited receive capabilities of the UE or the interference between paging signal transmitted for each of the RATs—among other factors—the UE may be unable to successfully monitor and receive information for each RAT and thus, paging performance for a CRAT UE may be adversely impacted.

SUMMARY

The described techniques relate to improved methods, systems, devices, or apparatuses that support paging offset negotiation. A wireless device such as a user equipment (UE) may support multiple radio access technologies (RATs) and may operate in a discontinuous reception (DRX) mode to conserve power. In the DRX mode, the UE may periodically wakeup during a DRX cycle to monitor one or more channels to determine whether information for the wireless device is available for transmission or reception. Each RAT may be associated with a different wakeup occasion and in some cases, the wakeup occasions for two RATs may collide. In such instances, the UE may communicate with a base station or another network node of the wireless communications system to determine an appropriate offset for adjusting one of the wakeup occasions to avoid collisions between wakeup occasions. Such communications may involve the UE transmitting paging offset change request messages to a base station or another network node and receiving an acceptance of the offset change.

In some examples, the UE or another network node may determine an appropriate offset for adjusting one or more of the wakeup occasions subject to collisions. For instance, the UE or network node may identify or determine a timing offset for the UE based on an international mobile subscriber identity (IMSI) of the UE. The UE may transmit a paging offset change request message via a radio resource control (RRC) channel or a media access control (MAC) control element (CE) . In some cases, the UE may transmit a non-access stratum (NAS) message directly to a core network node in order to perform paging offset negotiation. Such techniques may allow for a UE to adjust one or more wakeup occasions for different RATs in order to avoid collisions between the wakeup occasions when operating in a DRX mode.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example of a system for wireless communication that supports paging offset negotiation in accordance with aspects of the present disclosure.

FIG. 2 illustrates an example of a wireless communications system that supports paging offset negotiation in accordance with aspects of the present disclosure.

FIGs. 3A and 3B illustrate examples of discontinuous reception (DRX) cycles that supports paging offset negotiation in accordance with aspects of the present disclosure.

FIGs. 4 through 9 illustrate example process flows that supports paging offset negotiation in accordance with aspects of the present disclosure.

FIGs. 10 through 12 show block diagrams of a device that supports paging offset negotiation in accordance with aspects of the present disclosure.

FIG. 13 illustrates a block diagram of a system including a UE that supports paging offset negotiation in accordance with aspects of the present disclosure.

FIGs. 14 through 16 show block diagrams of a device that supports paging offset negotiation in accordance with aspects of the present disclosure.

FIG. 17 illustrates a block diagram of a system including a base station that supports paging offset negotiation in accordance with aspects of the present disclosure.

FIGs. 18 through 19 illustrate methods for paging offset negotiation in accordance with aspects of the present disclosure.

DETAILED DESCRIPTION

In wireless communication systems, a base station may signal to a user equipment (UE) that paging information is available in a channel for the UE by sending a page or a paging message during a subframe, which may be referred to as a paging occasion for the UE. In some cases, a UE may operate in a discontinuous reception mode (DRX) to conserve battery life. In such cases, the UE may need to wake-up from a specific idle DRX occasion (e.g., based on a particular active/idle configuration) to monitor pages. In some cases, a concurrent radio access technology (CRAT) UE may share receiving and transmitting resources for simultaneous active/idle activity related to a plurality of RATs. Furthermore, the UE may need to wake up at a plurality of specific idle DRX occasions based on a wakeup occasion and related interval for each of the plurality of RATs. In some cases, the idle DRX wakeup occasions of two or more RATs may collide or overlap. In some cases, due to limited receiving capabilities of a UE, for example, the UE may only be capable of monitoring pages of one RAT at a given instance and be unable to monitor pages of another RAT—leading to ineffective or diminished paging performance by the UE with respect to the multiple RATs.

In some cases, following discovery of one or more previous or anticipated collisions of wakeup paging occasions for two or more RATs, a UE may adjust a wakeup page occasion offset of at least one of the RATs through interacting or negotiating with one or more elements of the network, such as a base station, a mobility management entity (MME) , or a core network entity.

Aspects of the disclosure are initially described in the context of a wireless communications system. Aspects are then described with respect to DRX cycle diagrams and process flows. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to paging offset negotiation.

FIG. 1 illustrates an example of a wireless communications system 100 in accordance with various aspects of the present disclosure. The wireless communications system 100 includes base stations 105, UEs 115, and a core network 130. In some examples, the wireless communications system 100 may be a Long Term Evolution (LTE) , LTE-Advanced (LTE-A) network, or a New Radio (NR) network. In some cases, wireless communications system 100 may support enhanced broadband communications, ultra-reliable (i.e., mission critical) communications, low latency communications, and communications with low-cost and low-complexity devices.

Base stations 105 may wirelessly communicate with UEs 115 via one or more base station antennas. Each base station 105 may provide communication coverage for a respective geographic coverage area 110. Communication links 125 shown in wireless communications system 100 may include uplink transmissions from a UE 115 to a base station 105, or downlink transmissions, from a base station 105 to a UE 115. Control information and data may be multiplexed on an uplink channel or downlink according to various techniques. Control information and data may be multiplexed on a downlink channel, for example, using time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques. In some examples, the control information transmitted during a transmission time interval (TTI) of a downlink channel may be distributed between different control regions in a cascaded manner (e.g., between a common control region and one or more UE-specific control regions) .

UEs 115 may be dispersed throughout the wireless communications system 100, and each UE 115 may be stationary or mobile. A UE 115 may also be referred to as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communications device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. A UE 115 may also be a cellular phone, a personal digital assistant (PDA) , a wireless modem, a wireless communication device, a handheld device, a tablet computer, a laptop computer, a cordless phone, a personal electronic device, a handheld device, a personal computer, a wireless local loop (WLL) station, an Internet of Things (IoT) device, an Internet of Everything (IoE) device, a machine type communication (MTC) device, an appliance, an automobile, or the like.

In some cases, a UE 115 may also be able to communicate directly with other UEs (e.g., using a peer-to-peer (P2P) or device-to-device (D2D) protocol) . One or more of a group of UEs 115 utilizing D2D communications may be within the coverage area 110 of a cell. Other UEs 115 in such a group may be outside the coverage area 110 of a cell, or otherwise unable to receive transmissions from a base station 105. In some cases, groups of UEs 115 communicating via D2D communications may utilize a one-to-many (1: M) system in which each UE 115 transmits to every other UE 115 in the group. In some cases, a base station 105 facilitates the scheduling of resources for D2D communications. In other cases, D2D communications are carried out independent of a base station 105.

Some UEs 115, such as MTC or IoT devices, may be low cost or low complexity devices, and may provide for automated communication between machines, i.e., Machine-to-Machine (M2M) communication. M2M or MTC may refer to data communication technologies that allow devices to communicate with one another or a base station without human intervention. For example, M2M or MTC may refer to communications from devices that integrate sensors or meters to measure or capture information and relay that information to a central server or application program that can make use of the information or present the information to humans interacting with the program or application. Some UEs 115 may be designed to collect information or enable automated behavior of machines. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging.

In some cases, an MTC device may operate using half-duplex (one-way) communications at a reduced peak rate. MTC devices may also be configured to enter a power saving “deep sleep” mode when not engaging in active communications. In some cases, MTC or IoT devices may be designed to support mission critical functions and wireless communications system may be configured to provide ultra-reliable communications for these functions.

Base stations 105 may communicate with the core network 130 and with one another. For example, base stations 105 may interface with the core network 130 through backhaul links 132 (e.g., S1, etc. ) . Base stations 105 may communicate with one another over backhaul links 134 (e.g., X2, etc. ) either directly or indirectly (e.g., through core network 130) . Base stations 105 may perform radio configuration and scheduling for communication with UEs 115, or may operate under the control of a base station controller (not shown) . In some examples, base stations 105 may be macro cells, small cells, hot spots, or the like. Base stations 105 may also be referred to as evolved NodeBs (eNBs) 105.

A base station 105 may be connected by an S1 interface to the core network 130. The core network may be an evolved packet core (EPC) , which may include at least one mobility management entity (MME) , at least one serving gateway (S-GW) , and at least one Packet Data Network (PDN) gateway (P-GW) . The MME may be the control node that processes the signaling between the UE 115 and the EPC. All user Internet Protocol (IP) packets may be transferred through the S-GW, which itself may be connected to the P-GW. The P-GW may provide IP address allocation as well as other functions. The P-GW may be connected to the network operators IP services. The operators IP services may include the Internet, the Intranet, an IP Multimedia Subsystem (IMS) , and a Packet-Switched (PS) Streaming Service.

The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. At least some of the network devices, such as base station 105 may include subcomponents such as an access network entity, which may be an example of an access node controller (ANC) . Each access network entity may communicate with a number of UEs 115 through a number of other access network transmission entities, each of which may be an example of a smart radio head, or a transmission/reception point (TRP) . In some configurations, various functions of each access network entity or base station 105 may be distributed across various network devices (e.g., radio heads and access network controllers) or consolidated into a single network device (e.g., a base station 105) .

Wireless communications system 100 may operate in an ultra-high frequency (UHF) frequency region using frequency bands from 700 MHz to 2600 MHz (2.6 GHz) , although some networks (e.g., a wireless local area network (WLAN) ) may use frequencies as high as 4 GHz. This region may also be known as the decimeter band, since the wavelengths range from approximately one decimeter to one meter in length. UHF waves may propagate mainly by line of sight, and may be blocked by buildings and environmental features. However, the waves may penetrate walls sufficiently to provide service to UEs 115 located indoors. Transmission of UHF waves is characterized by smaller antennas and shorter range (e.g., less than 100 km) compared to transmission using the smaller frequencies (and longer waves) of the high frequency (HF) or very high frequency (VHF) portion of the spectrum. In some cases, wireless communications system 100 may also utilize extremely high frequency (EHF) portions of the spectrum (e.g., from 30 GHz to 300 GHz) . This region may also be known as the millimeter band, since the wavelengths range from approximately one millimeter to one centimeter in length. Thus, EHF antennas may be even smaller and more closely spaced than UHF antennas. In some cases, this may facilitate use of antenna arrays within a UE 115 (e.g., for directional beamforming) . However, EHF transmissions may be subject to even greater atmospheric attenuation and shorter range than UHF transmissions.

Thus, wireless communications system 100 may support millimeter wave (mmW) communications between UEs 115 and base stations 105. Devices operating in mmW or EHF bands may have multiple antennas to allow beamforming. That is, a base station 105 may use multiple antennas or antenna arrays to conduct beamforming operations for directional communications with a UE 115. Beamforming (which may also be referred to as spatial filtering or directional transmission) is a signal processing technique that may be used at a transmitter (e.g., a base station 105) to shape and/or steer an overall antenna beam in the direction of a target receiver (e.g., a UE 115) . This may be achieved by combining elements in an antenna array in such a way that transmitted signals at particular angles experience constructive interference while others experience destructive interference.

Multiple-input multiple-output (MIMO) wireless systems use a transmission scheme between a transmitter (e.g., a base station 105) and a receiver (e.g., a UE 115) , where both transmitter and receiver are equipped with multiple antennas. Some portions of wireless communications system 100 may use beamforming. For example, base station 105 may have an antenna array with a number of rows and columns of antenna ports that the base station 105 may use for beamforming in its communication with UE 115. Signals may be transmitted multiple times in different directions (e.g., each transmission may be beamformed differently) . A mmW receiver (e.g., a UE 115) may try multiple beams (e.g., antenna subarrays) while receiving the synchronization signals.

In some cases, the antennas of a base station 105 or UE 115 may be located within one or more antenna arrays, which may support beamforming or MIMO operation. One or more base station antennas or antenna arrays may be collocated at an antenna assembly, such as an antenna tower. In some cases, antennas or antenna arrays associated with a base station 105 may be located in diverse geographic locations. A base station 105 may multiple use antennas or antenna arrays to conduct beamforming operations for directional communications with a UE 115.

In some cases, wireless communications system 100 may be a packet-based network that operate according to a layered protocol stack. In the user plane, communications at the bearer or Packet Data Convergence Protocol (PDCP) layer may be IP-based. A Radio Link Control (RLC) layer may in some cases perform packet segmentation and reassembly to communicate over logical channels. A Medium Access Control (MAC) layer may perform priority handling and multiplexing of logical channels into transport channels. The MAC layer may also use Hybrid ARQ (HARQ) to provide retransmission at the MAC layer to improve link efficiency. In the control plane, the Radio Resource Control (RRC) protocol layer may provide establishment, configuration, and maintenance of an RRC connection between a UE 115 and a network device 105-c, network device 105-b, or core network 130 supporting radio bearers for user plane data. At the Physical (PHY) layer, transport channels may be mapped to physical channels.

Wireless communications system 100 may support operation on multiple cells or carriers, a feature which may be referred to as carrier aggregation (CA) or multi-carrier operation. A carrier may also be referred to as a component carrier (CC) , a layer, a channel, etc. The terms “carrier, ” “component carrier, ” “cell, ” and “channel” may be used interchangeably herein. A UE 115 may be configured with multiple downlink CCs and one or more uplink CCs for carrier aggregation. Carrier aggregation may be used with both FDD and TDD component carriers.

In some cases, wireless communications system 100 may utilize enhanced component carriers (eCCs) . An eCC may be characterized by one or more features including: wider bandwidth, shorter symbol duration, shorter TTIs, and modified control channel configuration. In some cases, an eCC may be associated with a carrier aggregation configuration or a dual connectivity configuration (e.g., when multiple serving cells have a suboptimal or non-ideal backhaul link) . An eCC may also be configured for use in unlicensed spectrum or shared spectrum (where more than one operator is allowed to use the spectrum) . An eCC characterized by wide bandwidth may include one or more segments that may be utilized by UEs 115 that are not capable of monitoring the whole bandwidth or prefer to use a limited bandwidth (e.g., to conserve power) .

In some cases, an eCC may utilize a different symbol duration than other CCs, which may include use of a reduced symbol duration as compared with symbol durations of the other CCs. A shorter symbol duration may be associated with increased subcarrier spacing. A TTI in an eCC may consist of one or multiple symbols. In some cases, the TTI duration (that is, the number of symbols in a TTI) may be variable. In some cases, an eCC may utilize a different symbol duration than other CCs, which may include use of a reduced symbol duration as compared with symbol durations of the other CCs. A shorter symbol duration is associated with increased subcarrier spacing. A device, such as a UE 115 or base station 105, utilizing eCCs may transmit wideband signals (e.g., 20, 40, 60, 80 MHz, etc. ) at reduced symbol durations (e.g., 16.67 microseconds) . A TTI in eCC may consist of one or multiple symbols. In some cases, the TTI duration (that is, the number of symbols in a TTI) may be variable.

A shared radio frequency spectrum band may be utilized in an NR shared spectrum system. For example, an NR shared spectrum may utilize any combination of licensed, shared, and unlicensed spectrums, among others. The flexibility of eCC symbol duration and subcarrier spacing may allow for the use of eCC across multiple spectrums. In some examples, NR shared spectrum may increase spectrum utilization and spectral efficiency, specifically through dynamic vertical (e.g., across frequency) and horizontal (e.g., across time) sharing of resources.

In some cases, wireless communications system 100 may utilize both licensed and unlicensed radio frequency spectrum bands. For example, wireless communications system 100 may employ LTE License Assisted Access (LTE-LAA) or LTE Unlicensed (LTE U) radio access technology or NR technology in an unlicensed band such as the 5Ghz Industrial, Scientific, and Medical (ISM) band. When operating in unlicensed radio frequency spectrum bands, wireless devices such as base stations 105 and UEs 115 may employ listen-before-talk (LBT) procedures to ensure the channel is clear before transmitting data. In some cases, operations in unlicensed bands may be based on a CA configuration in conjunction with CCs operating in a licensed band. Operations in unlicensed spectrum may include downlink transmissions, uplink transmissions, or both. Duplexing in unlicensed spectrum may be based on frequency division duplexing (FDD) , time division duplexing (TDD) or a combination of both.

Wireless communications system 100 illustrates aspects of negotiating a paging occasion offset between a UE 115, a base station 105, core network 130 (e.g., a core network node) , or some combination. In some examples, a UE 115 may support a single RAT, while in other examples a UE 115 may be an example of a CRAT UE capable of supporting multiple RATs.

In some cases, the UE 115 may operate in a discontinuous reception mode (DRX) to conserve battery life. In such cases, the UE 115 may wake-up at a specific DRX occasion within a DRX interval (e.g., based on a particular paging configuration) to monitor for potential paging messages from a corresponding RAT. In some cases, the UE 115, which may be a CRAT UE, may share resources for simultaneous active/idle activity related to multiple RATs and each of the multiple RATs may be associated with one or more idle DRX wakeup occasions. In some cases, the idle DRX wakeup occasions of two or more RATs may collide or overlap and the UE 115 in wireless communications system 100 may only be capable of monitoring pages of one RAT (and not another RAT) during the wakeup occasion.

FIG. 2 illustrates an example of a wireless communications system 200 that supports paging offset negotiation in accordance with various aspects of the present disclosure. The wireless communications system 200 may include one or more UEs 115 (e.g., UE 115-a and UE 115-b) and a base station 105-a, which may be examples of the UE 115 and base station 105 described with reference to FIG. 1. As shown, UE 115-a may communicate with base station 105-a via communication link 125-a and UE 115-b may communicate with base station 105-a via communication link 125-b. Wireless communications system 200 also includes a core network node 130-a, which may be in communication with base station 105-a via backhaul link 132-a. Core network node 130-amay also be configured to communicate directly with UE 115-b via communication link 125-c.

Broadly, wireless communications system 200 illustrates aspects of different schemes for negotiating a paging occasion offset between base station 105-a and a UE 115, operating within a shared spectrum. In some examples, UE 115-a may support a single RAT, while UE 115-b may be an example of a CRAT UE capable of supporting multiple RATs.

In wireless communications system 200, base station 105-a may signal to a UE 115 that information is available by sending a page or a paging message during a particular subframe, which may be referred to as a paging occasion for the UE 115. In some cases, the UE 115 may operate in a discontinuous reception mode (DRX) to conserve battery life. In such cases, the UE 115 may need to wake-up at a specific DRX occasion (e.g., based on a particular paging configuration) to monitor for potential paging messages.

In some cases, the UE 115-b, which may be a CRAT UE, may share receiving and transmitting resources for simultaneous active/idle activity of multiple RATs and each of the multiple RATs may be associated with one or more idle DRX wakeup occasions. In some cases, the idle DRX wakeup occasions of two or more RATs may collide or overlap and the UE 115-b may only be capable of monitoring pages of one RAT during the wakeup occasion.

For example, a UE may have limited monitoring capabilities and may therefore only be capable of monitoring for paging occasion for a single RAT during a wakeup occasion. Thus, for a CRAT UE, such as UE 115-b, paging performance of the two or more RATs may be negatively impacted if the wakeup occasions for two or more RATs overlap, overlap, or otherwise collide. In some cases, following discovery of collision of a wakeup paging occasion between two or more RATs, the UE 115-b may negotiate a wakeup page occasion offset with one or more nodes of the network, such as the base station 105-a or core network node 130-a, which may be an MME.

In one example, the UE 115-b may negotiate a page occasion offset with a core network node 130-a via the base station 105-b. In some cases, the UE 115-b may transmit a page offset change request through a control signaling message (e.g., L3 message) , or any other uplink message. The base station 105-a may subsequently receive the page offset change request from the UE 115-b, and determine to forward the page offset change request to the core network node 130-a. In some examples, the base station 105-a may forward the page offset change request to the core network node 130-ausing an S1 Access Protocol (AP) message, or any other suitable backhaul message. Following reception of the S1AP message from the base station 105-a, the core network node 130-a may process the page offset change request, and forward an acceptance of the request and/or an offset value to the base station 105-a via backhaul link 132-a. The base station 105-a may then process the S1AP message received from the core network node 130-a, and subsequently transmit information pertaining to the page offset acceptance (which may include a corresponding offset value for one or more wakeup occasions associated with a given RAT) to the UE 115-b.

In another example, the UE 115-b may directly negotiate a page occasion offset with the core network node 130-a. For example, UE 115-b may communicate with the core network node 130-a through a control message such as a non-access stratum (NAS) message. In some cases, the NAS message may comprise a set of protocols in the Evolved Packet System, and may be used to convey non-radio signaling directly between the UE 115-b and the core network node 130-a.

In an example of a page occasion offset negotiation procedure between the UE 115-b and the core network node 130-a, the UE 115-b may send a NAS message comprising a tracking area update (TAU) with a page occasion offset request to the core network node 130-a. In some cases, the UE 115-b may transmit the NAS message to the core network node 130-a via the base station 105-a. In such instance, the base station 105-b may not process the NAS message prior to forwarding it to the core network node 130-a. Following reception of the NAS message with the page occasion offset request, the core network node 130-a may respond with a NAS message accepting the TAU from the UE 115-b, together with a page occasion offset value. In other examples, the core network node 130-a may indicate a different offset than the offset request in the page occasion offset request.

In some examples, the UE 115-b may perform page occasion offset negotiations via radio access network (RAN) signaling or paging, which may include a UMTS RAN (UTRAN) , Evolved UTRAN (E-UTRAN) , or any other RAN. In such cases, the UE 115-b and base station 105-a may be able to directly negotiate a page occasion offset with limited assistance from the core network node 130-a. In some cases, the page occasion offset negotiation may occur during a random access procedure between the UE 115-b and the base station 105-a. For example, the UE 115-b may transmit a Radio Resource Control (RRC) message or a Medium Access Control (MAC) Control Element (CE) with a page occasion offset request. In some cases, the base station 105-a may accept the page occasion offset, and inform the UE 115-b of acceptance through RRC or a MAC CE. Furthermore, the base station 105-a may transmit or forward an indication of the page occasion offset granted to the UE 115-b, to the core network node 130-a or any other RAN node.

The UE 115-b, the base station 105-a, and/or the core network node 130-a (collectively, the involved devices) may adopt various ways of indicating or conveying information of page occasion offset. In some examples, the offset information represents a relative offset value in certain time measures (e.g., in number of subframes, frames, or slots) between the new (e.g., the requested, desired, or negotiated) page occasion and the existing page occasion. Thus, in some implementations the involved devices may calculate page occasion based on, e.g., certain predetermined, static, or semi-static system parameters or configurations (such as, e.g., international mobile subscriber identity (IMSI) ) and adjust the calculation by the dynamically indicated offset value to derive the new page occasion. In some other examples, the offset information is embodied by a parameter used in the page occasion calculation. For example, the involved devices may signal the page occasion offset using a particular value of IMSI such that the calculated page occasion according to the IMSI value reflects the new page occasion based on the offset information. Furthermore, IMSI-based offset indication may lessen the impact to other devices not involved in the page offset negotiation because as an already recognized parameter the IMSI can pass through or be used by those other devices transparently.

FIGs. 3A and 3B illustrate example DRX cycles 301 and 302 that support paging offset negotiation in accordance with various aspects of the present disclosure. The DRX cycle 301 may include one or more DRX intervals 305 (e.g., DRX interval 305-a and DRX interval 305-b) , during which a receiving UE 115 may be configured to wake-up for a portion of the interval to receive pages or paging messages from a base station 105. In some cases, the base station 105 and the UE 115 may be examples of a base station 105-a and UE 115-b as described with reference to FIG. 2.

In some cases, the UE may share receiving and transmitting resources for simultaneous active/idle activity of a plurality of RATs (e.g., RAT 1 and RAT 2) supported by the UE. Furthermore, each of the plurality of RATs may need to wake up at a specific idle DRX occasion within the DRX interval (s) 305. In some cases, the idle DRX wakeup occasions of two or more RATs (e.g., RAT 1 and RAT 2) may collide or overlap by spanning over one or more DRX intervals 305, as shown by wake-up collision interval 310-a. Furthermore, due to limited receiving capabilities of the UE, for example, the UE may only be capable of monitoring pages of one RAT at a given instance, paging performance of RAT 1 and RAT 2 may be compromised. In some cases, following discovery of collision of a wakeup paging occasion between RAT 1 and RAT 2, the UE 115 may negotiate a wakeup page occasion offset with one or more entities of the network, such as the base station 105 or a core network entity 130.

FIG. 3B illustrates an example of a DRX cycle 302 that supports paging occasion offset negotiation in accordance with aspects of the present disclosure. The DRX cycle 302 may include DRX interval 305-c, during which a receiving UE 115 may be configured to wake-up for a portion of the interval to receive pages or paging messages from a base station 105. In some cases, the base station 105 and the UE 115 may be examples of a base station 105-a and UE 115-b as described with reference to FIG. 2.

In some cases, the UE may share receiving and transmitting resources for simultaneous active/idle activity of a plurality of RATs (e.g., RAT 1 and RAT 2) supported by the UE. Furthermore, each of the plurality of RATs may need to wake up at a specific idle DRX occasion within the DRX interval 305-c. In some cases, the idle DRX wakeup occasions of two or more RATs (e.g., RAT 1 and RAT 2) may overlap as shown by wake-up collision interval 310-b. Furthermore, due to limited receiving capabilities of the UE, for example, the UE may only be capable of monitoring pages of one RAT at a given instance, paging performance of RAT 1 and RAT 2 may be compromised. As further described with reference to FIGs. 4-9, in some cases, the UE 115 may negotiate a wakeup page occasion offset with one or more elements of the network, such as the base station 105 or a MME, following discovery of collision of a wakeup paging occasion between two or more RATs.

FIG. 4 illustrates an example of a process flow 400 that supports paging offset negotiation in accordance with various aspects of the present disclosure. The process illustrated by process flow 400 may be implemented by a UE 115-c, a base station 105-b, and a core network entity 130-b. The UE 115-c and base station 105-b may be examples of a UE 115 and base station 105 described with reference to FIGs. 1 and 2. In some examples, the process illustrated by flow diagram 400 may be implemented in a wireless system employing mmW communications.

In some cases, the UE 115-c, which may be a CRAT UE, may share receiving and transmitting resources for simultaneous active/idle activity of a plurality of RATs. Furthermore, each of the plurality of RATs may need to wake up at a specific idle DRX occasions. In some cases, the idle DRX wakeup occasions of two or more RATs may collide or overlap. In some other cases, due to limited receiving capabilities of the UE 115-c, for example, the UE 115-c may only be capable of monitoring pages of one RAT at a given instance. Thus, paging performance of the two or more RATs may be compromised. Following discovery of collision of a wakeup paging occasion between two or more RATs, the UE 115-c may negotiate a wakeup page occasion offset with the core network entity 130-b, via the base station 105-b.

At 405, the UE 115-b may transmit a page offset change request through a control signaling message (e.g., L3 message) , or any other uplink message. The base station 105-amay subsequently receive the page offset change request from the UE 115-b. At 410, the base station 105-b may process the page offset change request prior to deciding to forward the page offset change request to the core network entity 130-b.

At 415, the base station 105-b may forward the page offset change request through the use of a S1AP message, or another backhaul message to the core network entity 130-b. Following reception of the S1AP message from the base station 105-b, the core network entity 130-b may process the page offset change request at 420, and forward an acceptance of the request and/or an offset value to the base station 105-b at 425.

At 430, the base station 105-b may transmit information pertaining to the page offset acceptance and the corresponding offset value via a control signaling message (e.g., L3 message) to the UE 115-c.

FIG. 5 illustrates an example of a process flow 500 that supports paging offset negotiation in accordance with various aspects of the present disclosure. The process illustrated by process flow 500 may be implemented by a UE 115-d, a base station 105-c, and a core network entity 130-c. The UE 115-c and base station 105-b may be examples of a UE 115 and base station 105 described with reference to FIGs. 1, 2, and 4. The core network entity 130-c may be an example of the core network entity 130-b described with reference to FIG. 4. In some examples, the process illustrated by flow diagram 500 may be implemented in a wireless system employing mmW communications.

In some cases, following discovery of collision of a wakeup paging occasion between two or more RATs, the UE 115-d may negotiate a wakeup page occasion offset with the core network entity 130-c, for example, through the use of a higher level control message such as a NAS message.

At 505, the UE 115-d may send a NAS message comprising a TAU with a page occasion offset request to the core network entity 130-c. In some cases, the UE 115-d may transparently transmit the NAS message via the base station 105-c, such that the base station 105-c may not further process the NAS message prior to forwarding it to the core network entity 130-c.

Following reception of the NAS message, the core network entity 130-c may process the PO offset request, and determine a PO Offset value at 510. At 515, the core network entity 130-c may respond with a NAS message accepting the TAU from the UE 115-b together with the page occasion offset value.

FIG. 6 illustrates an example of a process flow 600 that supports paging offset negotiation in accordance with various aspects of the present disclosure. The process illustrated by process flow 600 may be implemented by a UE 115-e, a base station 105-d, and a core network entity 130-d. The UE 115-e and base station 105-d may be examples of a UE 115 and base station 105 described with reference to FIGs. 1, 2, 4, and 5. The core network entity 130-d may be an example of the core network entity 130-b and core network entity 130-c described with reference to FIGs. 4 and 5. In some examples, the process illustrated by flow diagram 600 may be implemented in a wireless system employing mmW communications.

At 605, the UE 115-e may initiate performing page occasion offset negotiations with the RAN. In some cases, the page occasion offset negotiation may occur during a random access procedure between the UE 115-e and the base station 105-d. For example, at 605, the UE 115-b may transmit a RRC message or a MAC control element with a page occasion offset request to the base station 105-d.

At 610, the base station 105-d may process and accept the page occasion offset request. Thus, in some cases, the UE 115-e and base station 105-d may be able to directly negotiate a page occasion offset with limited assistance from the core network entity 130-d.

At 615, the base station 105-d may inform the UE 115-e of the page occasion offset acceptance and the offset value, through RRC or a MAC CE.

At 620, the base station 105-d may transmit or forward an indication of the page occasion offset granted to the UE 115-e, to the core network entity 130-d.

FIG. 7 illustrates an example of a process flow 700 that supports paging offset negotiation in accordance with various aspects of the present disclosure. The process illustrated by process flow 700 may be implemented by a UE 115-f, a base station 105-e, and a core network entity 130-e. The UE 115-f, base station 105-e, and core network entity 130-e may be examples of a UE 115 and base station 105 described with reference to FIGs. 4, 5, and 6. In some examples, the process illustrated by flow diagram 700 may be implemented in a wireless system employing mmW communications.

At 705, the core network entity 130-e may trigger a page occasion offset procedure. In some cases, the core network entity 130-e may indicate to the base station 105-e a page occasion offset value to be used by the UE 115-f for controlling its paging wakeup occasions for one or more RATs. In some cases, the core network entity 130-e may utilize a S1AP message to page the base station 105-e, and indicate the page occasion offset value. As previously described, the S1AP message may provide control plane signaling between the core network entity 130-e and the base station 105-e.

At 710, the base station 105-e may process the page occasion offset received from the core network entity 130-e, and determine an offset value amongst other timing parameters for the UE 115-f.

At 715, the base station 105-a may then forward or transmit an over-the-air (OTA) RRC page with an indication of the page occasion offset value and/or a timing page occasion to the UE 115-f.

FIG. 8 illustrates an example of a process flow 800 that supports paging offset negotiation in accordance with various aspects of the present disclosure. The process illustrated by process flow 800 may be implemented by a UE 115-g, base stations 105-f and 105-g, and a core network entity 130-f. The UE 115-g, base station 105-g, and core network entity 130-f may be examples of a UE 115, base station 105, and core network entity 130-f described with reference to FIGs. 4, 5, and 6. In some examples, the process illustrated by flow diagram 800 may be implemented in a wireless system employing mmW communications.

At 805, one or more network elements such as the base station 105-f, or base station 105-g, or core network entity 130-f, or a combination thereof may initiate negotiation of a paging procedure with the UE 115-g, prior to completing a random access procedure.

At 810, the core network entity 130-f may provide a UE context setup or modification, such as a page occasion offset to the base station 105-f. In some cases, one or more functions of the core network entity 130-f may also be performed by the base station 105-f. For example, in some cases, page occasion offset negotiations may be initiated by the base station 105-f. In such cases, the base station 105-f may also be referred to as anchor base station 105-f.

Following reception of one or more UE context setup or modification instructions, the anchor base station 105-f may proceed to configure the UE 115-g to a lightly connected state, at 815.

At 820, the anchor base station may receive incoming data, signaling, or a combination thereof for the UE 115-g. In some cases, the incoming data or signaling may be received from the base station 105-g.

At 825, the anchor base station 105-f may trigger a paging message in a RAN paging area, the RAN paging area comprising one or more other base stations 105, including the base station 105-g. In some cases, the base station 105-g in the RAN paging area may receive the paging message.

At 830, the base station 105-g may process the paging message from the anchor base station 105-f to extract a paging occasion offset and/or a timing paging occasion.

At 835, the base station 105-g may transmit an OTA RRC page with the page occasion offset and/or the timing paging occasion to the UE 105-g.

In some cases, the anchor base station 105-f may have a certain degree of autonomy in determining a page occasion offset value, or timing paging occasion, or a combination thereof, for the UE 115-g. In such cases, the anchor base station 105-f may not receive a paging occasion offset from the core network entity 130-f, and may proceed to conduct the paging procedure as described above.

FIG. 9 illustrates an example of a process flow 900 that supports paging offset negotiation in accordance with various aspects of the present disclosure. The process illustrated by process flow 900 may be implemented by a UE 115-h, and a network node 905. The UE 115-g may be an example of a UE 115 described with reference to FIGs. 1 and 2. The network node 905 may be an example of a base station 105, a core network entity, or a MME. In some examples, the process illustrated by flow diagram 900 may be implemented in a wireless system employing mmW communications.

At 910, the UE 115-h may identify a collision of a first DRX interval of a first RAT and a second DRX interval of a second RAT.

At 915, the UE 115-h may identify a DRX interval offset change for the first DRX interval of the first RAT based at least in part on the collision.

At 920, the UE 115-h may transmit a paging offset change request message to the network node 905, based at least in part on the DRX interval offset change identified at 915. In some cases, the paging offset change request message may be a first L3 message comprising an indication of a request to change a timing offset value for the first DRX interval. In some other cases, the paging offset change request message may be a NAS message comprising a TAU. Furthermore, in some cases, the paging offset change request message may be transmitted prior to completion of a random access procedure. In such cases, the paging offset change request message may be a RRC message or a MAC CE. In some cases, the requested timing offset value may be based at least in part on an international mobile subscriber identity (IMSI) associated with the UE 115-h.

Following reception of the paging offset change request message, the network node 905 may further process the paging offset change request at 925. In some cases, the network node 905 may respond with a paging offset acceptance message. Furthermore, in some cases, the paging offset acceptance message may be a second L3 message comprising an indication of an acceptance to the paging offset change request, or a NAS message comprising a TAU acceptance. In some cases, the paging offset acceptance message may also comprise an indication of acceptance of the timing offset value request at 920. In some other cases, the paging offset acceptance message may comprise an indication of a new timing offset value.

At 935, the UE 115-h may adjust the first DRX interval of the first RAT based at least in part on the paging offset acceptance message. In some cases, the UE 115-h may also transmit a RRC response or a MAC response CE, following receiving the paging offset acceptance message.

FIG. 10 shows a block diagram 1000 of a wireless device 1005 that supports paging offset negotiation in accordance with aspects of the present disclosure. Wireless device 1005 may be an example of aspects of a UE 115 as described with reference to FIG. 1. Wireless device 1005 may include receiver 1010, UE paging manager 1015, and transmitter 1020. Wireless device 1005 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .

Receiver 1010 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to paging offset negotiation, etc. ) . Information may be passed on to other components of the device. The receiver 1010 may be an example of aspects of the transceiver 1335 described with reference to FIG. 13. The receiver 1010 may utilize a single antenna or a set of antennas.

UE paging manager 1015 may be an example of aspects of the UE paging manager 1315 described with reference to FIG. 13.

UE paging manager 1015 and/or at least some of its various sub-components may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions of the UE paging manager 1015 and/or at least some of its various sub-components may be executed by a general-purpose processor, a digital signal processor (DSP) , an application-specific integrated circuit (ASIC) , an field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in the present disclosure.

The UE paging manager 1015 and/or at least some of its various sub-components may be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations by one or more physical devices. In some examples, UE paging manager 1015 and/or at least some of its various sub-components may be a separate and distinct component in accordance with various aspects of the present disclosure. In other examples, UE paging manager 1015 and/or at least some of its various sub-components may be combined with one or more other hardware components, including but not limited to an I/O component, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof in accordance with various aspects of the present disclosure.

UE paging manager 1015 may identify, within a DRX interval, a collision of a first DRX wakeup occasion of a first RAT and a second DRX wakeup occasion of a second RAT, identify an offset change for a DRX wakeup occasion of the first RAT based on the collision, transmit, to a network node, a paging offset change request message based on the offset change, and receive, from the network node, a paging offset acceptance message in response to the paging offset change request message.

Transmitter 1020 may transmit signals generated by other components of the device. In some examples, the transmitter 1020 may be collocated with a receiver 1010 in a transceiver module. For example, the transmitter 1020 may be an example of aspects of the transceiver 1335 described with reference to FIG. 13. The transmitter 1020 may utilize a single antenna or a set of antennas.

FIG. 11 shows a block diagram 1100 of a wireless device 1105 that supports paging offset negotiation in accordance with aspects of the present disclosure. Wireless device 1105 may be an example of aspects of a wireless device 1005 or a UE 115 as described with reference to FIGs. 1 and 10. Wireless device 1105 may include receiver 1110, UE paging manager 1115, and transmitter 1120. Wireless device 1105 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .

Receiver 1110 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to paging offset negotiation, etc. ) . Information may be passed on to other components of the device. The receiver 1110 may be an example of aspects of the transceiver 1335 described with reference to FIG. 13. The receiver 1110 may utilize a single antenna or a set of antennas.

UE paging manager 1115 may be an example of aspects of the UE paging manager 1315 described with reference to FIG. 13. UE paging manager 1115 may also include collision component 1125, offset component 1130, message transmitter 1135, and message receiver 1140.

Collision component 1125 may identify, within a DRX interval, a collision of a first DRX wakeup occasion of a first RAT and a second DRX wakeup occasion of a second RAT. In some cases, identifying the collision of the first DRX wakeup occasion and the second DRX wakeup occasion includes: identifying a previous overlap of the first DRX wakeup occasion and the second DRX wakeup occasion.

Offset component 1130 may identify an offset change for a DRX wakeup occasion of the first RAT based on the collision.

Message transmitter 1135 may transmit, to a network node, a paging offset change request message based on the offset change. In some cases, the paging offset change request message includes a requested timing offset value. In some cases, the requested timing offset value is calculated based on an IMSI associated with a UE. In some cases, the network node includes a base station. In some cases, the network node includes a core network entity.

Message receiver 1140 may receive, from the network node, a paging offset acceptance message in response to the paging offset change request message. In some cases, the paging offset acceptance message includes an indication of acceptance of the requested timing offset value. In some cases, the paging offset acceptance message includes a new timing offset value that is different from the requested timing offset value.

Transmitter 1120 may transmit signals generated by other components of the device. In some examples, the transmitter 1120 may be collocated with a receiver 1110 in a transceiver module. For example, the transmitter 1120 may be an example of aspects of the transceiver 1335 described with reference to FIG. 13. The transmitter 1120 may utilize a single antenna or a set of antennas.

FIG. 12 shows a block diagram 1200 of a UE paging manager 1215 that supports paging offset negotiation in accordance with aspects of the present disclosure. The UE paging manager 1215 may be an example of aspects of a UE paging manager 1015, a UE paging manager 1115, or a UE paging manager 1315 described with reference to FIGs. 10, 11, and 13. The UE paging manager 1215 may include collision component 1220, offset component 1225, message transmitter 1230, message receiver 1235, wakeup component 1240, L3 component 1245, NAS component 1250, and control component 1255. Each of these modules may communicate, directly or indirectly, with one another (e.g., via one or more buses) .

Collision component 1220 may identify, within a DRX interval, a collision of a first DRX wakeup occasion of a first RAT and a second DRX wakeup occasion of a second RAT. In some cases, identifying the collision of the first DRX wakeup occasion and the second DRX wakeup occasion includes: identifying a previous overlap of the first DRX wakeup occasion and the second DRX wakeup occasion.

Offset component 1225 may identify an offset change for a DRX wakeup occasion of the first RAT based on the collision.

Message transmitter 1230 may transmit, to a network node, a paging offset change request message based on the offset change. In some cases, the paging offset change request message includes a requested timing offset value. In some cases, the requested timing offset value is calculated based on an IMSI associated with a UE. In some cases, the network node includes a base station. In some cases, the network node includes a core network entity.

Message receiver 1235 may receive, from the network node, a paging offset acceptance message in response to the paging offset change request message. In some cases, the paging offset acceptance message includes an indication of acceptance of the requested timing offset value. In some cases, the paging offset acceptance message includes a new timing offset value that is different from the requested timing offset value.

Wakeup component 1240 may adjust the first DRX wakeup occasion of the first RAT based on the paging offset acceptance message.

L3 component 1245 may transmit or receive L3 messages. In some cases, transmitting the paging offset change request message includes: transmitting a first L3 message including an indication of a request to change a timing offset value for the first DRX wakeup occasion. In some cases, receiving the paging offset acceptance message includes: receiving a second L3 message including an indication of an acceptance of the request to change the timing offset value. In some cases, at least one of the paging offset change request message and the paging offset acceptance message includes an IMSI associated with a UE.

NAS component 1250 may transmit or receive NAS messages. In some cases, transmitting the paging offset change request message includes: transmitting a NAS message including a TAU. In some cases, receiving the paging offset acceptance message includes: receiving a NAS response message including a TAU acceptance and a timing offset value for the first DRX wakeup occasion.

Control component 1255 may transmit or receive control information. In some cases, transmitting the paging offset change request message includes: transmitting an RRC message or a MAC control element that indicates a paging occasion offset request. In some cases, receiving the paging offset acceptance message includes: transmitting a RRC response message or a MAC response control element in response to the paging occasion offset request.

FIG. 13 shows a diagram of a system 1300 including a device 1305 that supports paging offset negotiation in accordance with aspects of the present disclosure. Device 1305 may be an example of or include the components of wireless device 1005, wireless device 1105, or a UE 115 as described above, e.g., with reference to FIGs. 1, 10 and 11. Device 1305 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including UE paging manager 1315, processor 1320, memory 1325, software 1330, transceiver 1335, antenna 1340, and I/O controller 1345. These components may be in electronic communication via one or more busses (e.g., bus 1310) . Device 1305 may communicate wirelessly with one or more base stations 105.

Processor 1320 may include an intelligent hardware device, (e.g., a general-purpose processor, a DSP, a central processing unit (CPU) , a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) . In some cases, processor 1320 may be configured to operate a memory array using a memory controller. In other cases, a memory controller may be integrated into processor 1320. Processor 1320 may be configured to execute computer-readable instructions stored in a memory to perform various functions (e.g., functions or tasks supporting paging offset negotiation) .

Memory 1325 may include random access memory (RAM) and read only memory (ROM) . The memory 1325 may store computer-readable, computer-executable software 1330 including instructions that, when executed, cause the processor to perform various functions described herein. In some cases, the memory 1325 may contain, among other things, a basic input/output system (BIOS) which may control basic hardware and/or software operation such as the interaction with peripheral components or devices.

Software 1330 may include code to implement aspects of the present disclosure, including code to support paging offset negotiation. Software 1330 may be stored in a non-transitory computer-readable medium such as system memory or other memory. In some cases, the software 1330 may not be directly executable by the processor but may cause a computer (e.g., when compiled and executed) to perform functions described herein.

Transceiver 1335 may communicate bi-directionally, via one or more antennas, wired, or wireless links as described above. For example, the transceiver 1335 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 1335 may also include a modem to modulate the packets and provide the modulated packets to the antennas for transmission, and to demodulate packets received from the antennas.

In some cases, the wireless device may include a single antenna 1340. However, in some cases the device may have more than one antenna 1340, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.

I/O controller 1345 may manage input and output signals for device 1305. I/O controller 1345 may also manage peripherals not integrated into device 1305. In some cases, I/O controller 1345 may represent a physical connection or port to an external peripheral. In some cases, I/O controller 1345 may utilize an operating system such as

or another known operating system. In other cases, I/O controller 1345 may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device. In some cases, I/O controller 1345 may be implemented as part of a processor. In some cases, a user may interact with device 1305 via I/O controller 1345 or via hardware components controlled by I/O controller 1345.

FIG. 14 shows a block diagram 1400 of a wireless device 1405 that supports paging offset negotiation in accordance with aspects of the present disclosure. Wireless device 1405 may be an example of aspects of a base station 105 as described with reference to FIG. 1. Wireless device 1405 may include receiver 1410, base station paging manager 1415, and transmitter 1420. Wireless device 1405 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .

Receiver 1410 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to paging offset negotiation, etc. ) . Information may be passed on to other components of the device. The receiver 1410 may be an example of aspects of the transceiver 1735 described with reference to FIG. 17. The receiver 1410 may utilize a single antenna or a set of antennas.

Base station paging manager 1415 may be an example of aspects of the base station paging manager 1715 described with reference to FIG. 17. Base station paging manager 1415 and/or at least some of its various sub-components may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions of the base station paging manager 1415 and/or at least some of its various sub-components may be executed by a general-purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in the present disclosure.

The base station paging manager 1415 and/or at least some of its various sub-components may be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations by one or more physical devices. In some examples, base station paging manager 1415 and/or at least some of its various sub-components may be a separate and distinct component in accordance with various aspects of the present disclosure. In other examples, base station paging manager 1415 and/or at least some of its various sub-components may be combined with one or more other hardware components, including but not limited to an I/O component, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof in accordance with various aspects of the present disclosure.

Base station paging manager 1415 may identify, within a DRX interval, a DRX offset change for a first DRX wakeup occasion of a first RAT associated with a UE, the DRX offset change being based on a collision of the first DRX wakeup occasion of the first RAT and a second DRX wakeup occasion of a second RAT. In some cases, base station paging manager 1415 may receive, from a network node, a paging offset change message based on the DRX offset change, and transmit, to the UE, a paging offset message in response to the paging offset change message.

Transmitter 1420 may transmit signals generated by other components of the device. In some examples, the transmitter 1420 may be collocated with a receiver 1410 in a transceiver module. For example, the transmitter 1420 may be an example of aspects of the transceiver 1735 described with reference to FIG. 17. The transmitter 1420 may utilize a single antenna or a set of antennas.

FIG. 15 shows a block diagram 1500 of a wireless device 1505 that supports paging offset negotiation in accordance with aspects of the present disclosure. Wireless device 1505 may be an example of aspects of a wireless device 1405 or a base station 105 as described with reference to FIGs. 1 and 14. Wireless device 1505 may include receiver 1510, base station paging manager 1515, and transmitter 1520. Wireless device 1505 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses) .

Receiver 1510 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to paging offset negotiation, etc. ) . Information may be passed on to other components of the device. The receiver 1510 may be an example of aspects of the transceiver 1735 described with reference to FIG. 17. The receiver 1510 may utilize a single antenna or a set of antennas.

Base station paging manager 1515 may be an example of aspects of the base station paging manager 1715 described with reference to FIG. 17. Base station paging manager 1515 may also include change component 1525, message receiver 1530, and message transmitter 1535.

Change component 1525 may identify, within a DRX interval, a DRX offset change for a first DRX wakeup occasion of a first RAT associated with a UE, the DRX offset change being based on a collision of the first DRX wakeup occasion of the first RAT and a second DRX wakeup occasion of a second RAT.

Message receiver 1530 may receive, from a network node, a paging offset change message based on the DRX offset change. In some cases, the network node includes the UE. In some cases, the network node includes a core network entity.

Message transmitter 1535 may transmit, to the UE, a paging offset message in response to the paging offset change message. In some cases, the paging offset message includes a timing offset value for the first DRX wakeup occasion.

Transmitter 1520 may transmit signals generated by other components of the device. In some examples, the transmitter 1520 may be collocated with a receiver 1510 in a transceiver module. For example, the transmitter 1520 may be an example of aspects of the transceiver 1735 described with reference to FIG. 17. The transmitter 1520 may utilize a single antenna or a set of antennas.

FIG. 16 shows a block diagram 1600 of a base station paging manager 1615 that supports paging offset negotiation in accordance with aspects of the present disclosure. The base station paging manager 1615 may be an example of aspects of a base station paging manager 1715 described with reference to FIGs. 14, 15, and 17. The base station paging manager 1615 may include change component 1620, message receiver 1625, message transmitter 1630, L3 component 1635, S1AP component 1640, control component 1645, configuration component 1650, RAN component 1655, and timing component 1660. Each of these modules may communicate, directly or indirectly, with one another (e.g., via one or more buses) .

Change component 1620 may identify, within a DRX interval, a DRX offset change for a first DRX wakeup occasion of a first RAT associated with a UE, the DRX offset change being based on a collision of the first DRX wakeup occasion of the first RAT and a second DRX wakeup occasion of a second RAT.

Message receiver 1625 may receive, from a network node, a paging offset change message based on the DRX offset change. In some cases, the network node includes the UE. In some cases, the network node includes a core network entity.

Message transmitter 1630 may transmit, to the UE, a paging offset message in response to the paging offset change message. In some cases, the paging offset message includes a timing offset value for the first DRX wakeup occasion.

L3 component 1635 may transmit or receive L3 messages. In some cases, identifying the DRX offset change includes: receiving, from the UE, an L3 message including a paging offset change request message including an indication of a request to change a timing offset value for the first DRX wakeup occasion. In some cases, transmitting the paging offset message includes: transmitting, to the UE, a second L3 message that indicates the timing offset value based on the indication of the acceptance of the request to change the timing offset value.

S1AP component 1640 may transmit, to a core network entity, an S1AP message based on the indication of the request to change the timing offset value. In some cases, receiving the paging offset change message includes: receiving, from the core network entity, an S1AP response message including an indication of an acceptance of the request to change the timing offset value.

Control component 1645 may transmit or receive control information. In some cases, transmitting the paging offset message includes: transmitting an RRC message or a MAC control element that indicates a paging occasion offset. In some cases, identifying the DRX offset change includes: receiving an RRC message or a MAC control element that indicates a paging occasion offset request. In some cases, identifying the DRX offset change includes: receiving, from a core network entity, a UE-specific control message indicating a timing offset for the first DRX wakeup occasion.

Configuration component 1650 may configure the UE in an idle state based on the UE-specific control message.

RAN component 1655 may transmit, to a second base station, a RAN paging message indicating the timing offset, where transmitting the paging offset message is based on the RAN paging message and receive, from the base station, incoming data for the UE, where transmitting the RAN paging message is based on the incoming data.

Timing component 1660 may calculate the timing offset value based on an IMSI associated with the UE.

FIG. 17 shows a diagram of a system 1700 including a device 1705 that supports paging offset negotiation in accordance with aspects of the present disclosure. Device 1705 may be an example of or include the components of base station 105 as described above, e.g., with reference to FIG. 1. Device 1705 may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including base station paging manager 1715, processor 1720, memory 1725, software 1730, transceiver 1735, antenna 1740, network communications manager 1745, and base station communications manager 1750. These components may be in electronic communication via one or more busses (e.g., bus 1710) . Device 1705 may communicate wirelessly with one or more UEs 115.

Processor 1720 may include an intelligent hardware device, (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) . In some cases, processor 1720 may be configured to operate a memory array using a memory controller. In other cases, a memory controller may be integrated into processor 1720. Processor 1720 may be configured to execute computer-readable instructions stored in a memory to perform various functions (e.g., functions or tasks supporting paging offset negotiation) .

Memory 1725 may include RAM and ROM. The memory 1725 may store computer-readable, computer-executable software 1730 including instructions that, when executed, cause the processor to perform various functions described herein. In some cases, the memory 1725 may contain, among other things, a BIOS which may control basic hardware and/or software operation such as the interaction with peripheral components or devices.

Software 1730 may include code to implement aspects of the present disclosure, including code to support paging offset negotiation. Software 1730 may be stored in a non-transitory computer-readable medium such as system memory or other memory. In some cases, the software 1730 may not be directly executable by the processor but may cause a computer (e.g., when compiled and executed) to perform functions described herein.

Transceiver 1735 may communicate bi-directionally, via one or more antennas, wired, or wireless links as described above. For example, the transceiver 1735 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver 1735 may also include a modem to modulate the packets and provide the modulated packets to the antennas for transmission, and to demodulate packets received from the antennas.

In some cases, the wireless device may include a single antenna 1740. However, in some cases the device may have more than one antenna 1740, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.

Network communications manager 1745 may manage communications with the core network (e.g., via one or more wired backhaul links) . For example, the network communications manager 1745 may manage the transfer of data communications for client devices, such as one or more UEs 115.

Base station communications manager 1750 may manage communications with other base station 105, and may include a controller or scheduler for controlling communications with UEs 115 in cooperation with other base stations 105. For example, the base station communications manager 1750 may coordinate scheduling for transmissions to UEs 115 for various interference mitigation techniques such as beamforming or joint transmission. In some examples, base station communications manager 1750 may provide an X2 interface within an LTE/LTE-A wireless communication network technology to provide communication between base stations 105.

FIG. 18 shows a flowchart illustrating a method 1800 for paging offset negotiation in accordance with aspects of the present disclosure. The operations of method 1800 may be implemented by a UE 115 or its components as described herein. For example, the operations of method 1800 may be performed by a UE paging manager as described with reference to FIGs. 10 through 13. In some examples, a UE 115 may execute a set of codes to control the functional elements of the device to perform the functions described below. Additionally or alternatively, the UE 115 may perform aspects of the functions described below using special-purpose hardware.

At block 1805 the UE 115 may identify, within a DRX interval, a collision of a first DRX wakeup occasion of a first RAT and a second DRX wakeup occasion of a second RAT. The operations of block 1805 may be performed according to the methods described with reference to FIGs. 1 through 9. In certain examples, aspects of the operations of block 1805 may be performed by a collision component as described with reference to FIGs. 10 through 13.

At block 1810 the UE 115 may identify an offset change for a DRX wakeup occasion of the first RAT based at least in part on the collision. The operations of block 1810 may be performed according to the methods described with reference to FIGs. 1 through 9. In certain examples, aspects of the operations of block 1810 may be performed by a offset component as described with reference to FIGs. 10 through 13.

At block 1815 the UE 115 may transmit, to a network node, a paging offset change request message based at least in part on the offset change. The operations of block 1815 may be performed according to the methods described with reference to FIGs. 1 through 9. In certain examples, aspects of the operations of block 1815 may be performed by a message transmitter as described with reference to FIGs. 10 through 13.

At block 1820 the UE 115 may receive, from the network node, a paging offset acceptance message in response to the paging offset change request message. The operations of block 1820 may be performed according to the methods described with reference to FIGs. 1 through 9. In certain examples, aspects of the operations of block 1820 may be performed by a message receiver as described with reference to FIGs. 10 through 13.

FIG. 19 shows a flowchart illustrating a method 1900 for paging offset negotiation in accordance with aspects of the present disclosure. The operations of method 1900 may be implemented by a base station 105 or its components as described herein. For example, the operations of method 1900 may be performed by a base station paging manager as described with reference to FIGs. 14 through 17. In some examples, a base station 105 may execute a set of codes to control the functional elements of the device to perform the functions described below. Additionally or alternatively, the base station 105 may perform aspects of the functions described below using special-purpose hardware.

At block 1905 the base station 105 may identify, within a DRX interval, a DRX offset change for a first DRX wakeup occasion of a first RAT associated with UE, the DRX offset change being based at least in part on a collision of the first DRX wakeup occasion of the first RAT and a second DRX wakeup occasion of a second RAT. The operations of block 1905 may be performed according to the methods described with reference to FIGs. 1 through 9. In certain examples, aspects of the operations of block 1905 may be performed by a change component as described with reference to FIGs. 14 through 17.

At block 1910 the base station 105 may receive, from a network node, a paging offset change message based at least in part on the DRX offset change. The operations of block 1910 may be performed according to the methods described with reference to FIGs. 1 through 9. In certain examples, aspects of the operations of block 1910 may be performed by a message receiver as described with reference to FIGs. 14 through 17.

At block 1915 the base station 105 may transmit, to the UE, a paging offset message in response to the paging offset change message. The operations of block 1915 may be performed according to the methods described with reference to FIGs. 1 through 9. In certain examples, aspects of the operations of block 1915 may be performed by a message transmitter as described with reference to FIGs. 14 through 17.

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

Techniques described herein may be used for various wireless communications systems such as code division multiple access (CDMA) , time division multiple access (TDMA) , frequency division multiple access (FDMA) , orthogonal frequency division multiple access (OFDMA) , single carrier frequency division multiple access (SC-FDMA) , and other systems. The terms “system” and “network” are often used interchangeably. A code division multiple access (CDMA) system may implement a radio technology such as CDMA2000, Universal Terrestrial Radio Access (UTRA) , etc. CDMA2000 covers IS-2000, IS-95, and IS-856 standards. IS-2000 Releases may be commonly referred to as CDMA2000 1X, 1X, etc. IS-856 (TIA-856) is commonly referred to as CDMA2000 1xEV-DO, High Rate Packet Data (HRPD) , etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. A TDMA system may implement a radio technology such as Global System for Mobile Communications (GSM) .

An OFDMA system may implement a radio technology such as Ultra Mobile Broadband (UMB) , Evolved UTRA (E-UTRA) , Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20, Flash-OFDM, etc. UTRA and E-UTRA are part of Universal Mobile Telecommunications System (UMTS) . LTE and LTE-Aare releases of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, NR, and GSM are described in documents from the organization named “3rd Generation Partnership Project” (3GPP) . CDMA2000 and UMB are described in documents from an organization named “3rd Generation Partnership Project 2” (3GPP2) . The techniques described herein may be used for the systems and radio technologies mentioned above as well as other systems and radio technologies. While aspects of an LTE or an NR system may be described for purposes of example, and LTE or NR terminology may be used in much of the description, the techniques described herein are applicable beyond LTE or NR applications.

In LTE/LTE-A networks, including such networks described herein, the term evolved node B (eNB) may be generally used to describe the base stations. The wireless communications system or systems described herein may include a heterogeneous LTE/LTE-A or NR network in which different types of eNBs provide coverage for various geographical regions. For example, each eNB, next generation NodeB (gNB) , or base station may provide communication coverage for a macro cell, a small cell, or other types of cell. The term “cell” may be used to describe a base station, a carrier or component carrier associated with a base station, or a coverage area (e.g., sector, etc. ) of a carrier or base station, depending on context.

Base stations may include or may be referred to by those skilled in the art as a base transceiver station, a radio base station, an access point, a radio transceiver, a NodeB, eNodeB (eNB) , gNB, Home NodeB, a Home eNodeB, or some other suitable terminology. The geographic coverage area for a base station may be divided into sectors making up only a portion of the coverage area. The wireless communications system or systems described herein may include base stations of different types (e.g., macro or small cell base stations) . The UEs described herein may be able to communicate with various types of base stations and network equipment including macro eNBs, small cell eNBs, gNBs, relay base stations, and the like. There may be overlapping geographic coverage areas for different technologies.

A macro cell generally covers a relatively large geographic area (e.g., several kilometers in radius) and may allow unrestricted access by UEs with service subscriptions with the network provider. A small cell is a lower-powered base station, as compared with a macro cell, that may operate in the same or different (e.g., licensed, unlicensed, etc. ) frequency bands as macro cells. Small cells may include pico cells, femto cells, and micro cells according to various examples. A pico cell, for example, may cover a small geographic area and may allow unrestricted access by UEs with service subscriptions with the network provider. A femto cell may also cover a small geographic area (e.g., a home) and may provide restricted access by UEs having an association with the femto cell (e.g., UEs in a closed subscriber group (CSG) , UEs for users in the home, and the like) . An eNB for a macro cell may be referred to as a macro eNB. An eNB for a small cell may be referred to as a small cell eNB, a pico eNB, a femto eNB, or a home eNB. An eNB may support one or multiple (e.g., two, three, four, and the like) cells (e.g., component carriers) .

The wireless communications system or systems described herein may support synchronous or asynchronous operation. For synchronous operation, the base stations may have similar frame timing, and transmissions from different base stations may be approximately aligned in time. For asynchronous operation, the base stations may have different frame timing, and transmissions from different base stations may not be aligned in time. The techniques described herein may be used for either synchronous or asynchronous operations.

The downlink transmissions described herein may also be called forward link transmissions while the uplink transmissions may also be called reverse link transmissions. Each communication link described herein—including, for example,

wireless communications system

100 and 200 of FIGs. 1 and 2—may include one or more carriers, where each carrier may be a signal made up of multiple sub-carriers (e.g., waveform signals of different frequencies) .

The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that may be implemented or that are within the scope of the claims. The term “exemplary” used herein means “serving as an example, instance, or illustration, ” and not “preferred” or “advantageous over other examples. ” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.

In the appended figures, similar components or features may have the same reference label. Further, various components of the same type may be distinguished by following the reference label by a dash and a second label that distinguishes among the similar components. If just the first reference label is used in the specification, the description is applicable to any one of the similar components having the same first reference label irrespective of the second reference label.

Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

The various illustrative blocks and modules described in connection with the disclosure herein may be implemented or performed with a general-purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration) .

The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described above can be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations. Also, as used herein, including in the claims, “or” as used in a list of items (for example, a list of items prefaced by a phrase such as “at least one of” or “one or more of” ) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) . Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an exemplary step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. ”

Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, non-transitory computer-readable media may comprise RAM, ROM, electrically erasable programmable read only memory (EEPROM) , compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) , or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD) , floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

The description herein is provided to enable a person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein, but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.

Claims

A method for wireless communication, comprising:

identifying, within a discontinuous reception (DRX) interval, a collision of a first DRX wakeup occasion of a first radio access technology (RAT) and a second DRX wakeup occasion of a second RAT；

identifying an offset change for a DRX wakeup occasion of the first RAT based at least in part on the collision；

transmitting, to a network node, a paging offset change request message based at least in part on the offset change； and

receiving, from the network node, a paging offset acceptance message in response to the paging offset change request message.
The method of claim 1, further comprising:

adjusting the first DRX wakeup occasion of the first RAT based at least in part on the paging offset acceptance message.
The method of claim 1, wherein transmitting the paging offset change request message comprises:

transmitting a first layer 3 (L3) message comprising an indication of a request to change a timing offset value for the first DRX wakeup occasion.
The method of claim 3, wherein receiving the paging offset acceptance message comprises:

receiving a second L3 message comprising an indication of an acceptance of the request to change the timing offset value.
The method of claim 3, wherein:

at least one of the paging offset change request message and the paging offset acceptance message comprises an international mobile subscriber identity (IMSI) associated with a user equipment (UE) .
The method of claim 1, wherein transmitting the paging offset change request message comprises:

transmitting a non-access stratum (NAS) message comprising a tracking area update (TAU) .
The method of claim 6, wherein receiving the paging offset acceptance message comprises:

receiving a NAS response message comprising a TAU acceptance and a timing offset value for the first DRX wakeup occasion.
The method of claim 1, wherein transmitting the paging offset change request message comprises:

transmitting a radio resource control (RRC) message or a medium access control (MAC) control element that indicates a paging occasion offset request.
The method of claim 8, wherein receiving the paging offset acceptance message comprises:

transmitting a RRC response message or a MAC response control element in response to the paging occasion offset request.
The method of claim 1, wherein:

the paging offset change request message comprises a requested timing offset value.
The method of claim 10, wherein:

the paging offset acceptance message comprises an indication of acceptance of the requested timing offset value.
The method of claim 10, wherein:

the paging offset acceptance message comprises a new timing offset value that is different from the requested timing offset value.
The method of claim 10, wherein:

the requested timing offset value is calculated based at least in part on an international mobile subscriber identity (IMSI) associated with a user equipment (UE) .
The method of claim 1, wherein:

the network node comprises a base station.
The method of claim 1, wherein:

the network node comprises a core network entity.
The method of claim 1, wherein identifying the collision of the first DRX wakeup occasion and the second DRX wakeup occasion comprises:

identifying a previous overlap of the first DRX wakeup occasion and the second DRX wakeup occasion.
A method for wireless communication, comprising:

identifying, within a discontinuous reception (DRX) interval, a DRX offset change for a first DRX wakeup occasion of a first radio access technology (RAT) associated with a user equipment (UE) , the DRX offset change being based at least in part on a collision of the first DRX wakeup occasion of the first RAT and a second DRX wakeup occasion of a second RAT；

receiving, from a network node, a paging offset change message based at least in part on the DRX offset change； and

transmitting, to the UE, a paging offset message in response to the paging offset change message.
The method of claim 17, wherein identifying the DRX offset change comprises:

receiving, from the UE, a layer 3 (L3) message comprising a paging offset change request message comprising an indication of a request to change a timing offset value for the first DRX wakeup occasion.
The method of claim 18, further comprising:

transmitting, to a core network entity, an S1 Application Protocol (S1AP) message based at least in part on the indication of the request to change the timing offset value.
The method of claim 19, wherein receiving the paging offset change message comprises:

receiving, from the core network entity, an S1AP response message comprising an indication of an acceptance of the request to change the timing offset value.
The method of claim 20, wherein transmitting the paging offset message comprises:

transmitting, to the UE, a second L3 message that indicates the timing offset value based at least in part on the indication of the acceptance of the request to change the timing offset value.
The method of claim 17, wherein transmitting the paging offset message comprises:

transmitting a radio resource control (RRC) message or a medium access control (MAC) control element that indicates a paging occasion offset.
The method of claim 17, wherein identifying the DRX offset change comprises:

receiving a radio resource control (RRC) message or a medium access control (MAC) control element that indicates a paging occasion offset request.
The method of claim 17, wherein identifying the DRX offset change comprises:

receiving, from a core network entity, a UE-specific control message indicating a timing offset for the first DRX wakeup occasion.
The method of claim 24, further comprising:

configuring the UE in an idle state based at least in part on the UE-specific control message； and

transmitting, to a second base station, a radio access network (RAN) paging message indicating the timing offset, wherein transmitting the paging offset message is based at least in part on the RAN paging message.
The method of claim 25, further comprising:

receiving, from the base station, incoming data for the UE, wherein transmitting the RAN paging message is based at least in part on the incoming data.
The method of claim 17, wherein:

the paging offset message comprises a timing offset value for the first DRX wakeup occasion.
The method of claim 27, further comprising:

calculating the timing offset value based at least in part on an international mobile subscriber identity (IMSI) associated with the UE.
The method of claim 17, wherein:

the network node comprises the UE.
The method of claim 17, wherein:

the network node comprises a core network entity.
An apparatus for wireless communication, comprising:

means for identifying, within a discontinuous reception (DRX) interval, a collision of a first DRX wakeup occasion of a first radio access technology (RAT) and a second DRX wakeup occasion of a second RAT；

means for identifying an offset change for a DRX wakeup occasion of the first RAT based at least in part on the collision；

means for transmitting, to a network node, a paging offset change request message based at least in part on the offset change； and

means for receiving, from the network node, a paging offset acceptance message in response to the paging offset change request message.
The apparatus of claim 31, further comprising:

means for adjusting the first DRX wakeup occasion of the first RAT based at least in part on the paging offset acceptance message.
The apparatus of claim 31, wherein the means for transmitting the paging offset change request message comprises:

means for transmitting a first layer 3 (L3) message comprising an indication of a request to change a timing offset value for the first DRX wakeup occasion.
The apparatus of claim 33, wherein the means for receiving the paging offset acceptance message comprises:

means for receiving a second L3 message comprising an indication of an acceptance of the request to change the timing offset value.
The apparatus of claim 33, wherein:

at least one of the paging offset change request message and the paging offset acceptance message comprises an international mobile subscriber identity (IMSI) associated with a user equipment (UE) .
The apparatus of claim 31, wherein the means for transmitting the paging offset change request message comprises:

means for transmitting a non-access stratum (NAS) message comprising a tracking area update (TAU) .
The apparatus of claim 36, wherein the means for receiving the paging offset acceptance message comprises:

means for receiving a NAS response message comprising a TAU acceptance and a timing offset value for the first DRX wakeup occasion.
The apparatus of claim 31, wherein the means for transmitting the paging offset change request message comprises:

means for transmitting a radio resource control (RRC) message or a medium access control (MAC) control element that indicates a paging occasion offset request.
The apparatus of claim 38, wherein the means for receiving the paging offset acceptance message comprises:

means for transmitting a RRC response message or a MAC response control element in response to the paging occasion offset request.
The apparatus of claim 31, wherein:

the paging offset change request message comprises a requested timing offset value.
The apparatus of claim 40, wherein:

the paging offset acceptance message comprises an indication of acceptance of the requested timing offset value.
The apparatus of claim 40, wherein:

the paging offset acceptance message comprises a new timing offset value that is different from the requested timing offset value.
The apparatus of claim 40, wherein:

the requested timing offset value is calculated based at least in part on an international mobile subscriber identity (IMSI) associated with a user equipment (UE) .
The apparatus of claim 31, wherein:

the network node comprises a base station.
The apparatus of claim 31, wherein:

the network node comprises a core network entity.
The apparatus of claim 31, wherein the means for identifying the collision of the first DRX wakeup occasion and the second DRX wakeup occasion comprises:

means for identifying a previous overlap of the first DRX wakeup occasion and the second DRX wakeup occasion.
An apparatus for wireless communication, comprising:

means for identifying, within a discontinuous reception (DRX) interval, a DRX offset change for a first DRX wakeup occasion of a first radio access technology (RAT) associated with a user equipment (UE) , the DRX offset change being based at least in part on a collision of the first DRX wakeup occasion of the first RAT and a second DRX wakeup occasion of a second RAT；

means for receiving, from a network node, a paging offset change message based at least in part on the DRX offset change； and

means for transmitting, to the UE, a paging offset message in response to the paging offset change message.
The apparatus of claim 47, wherein the means for identifying the DRX offset change comprises:

means for receiving, from the UE, a layer 3 (L3) message comprising a paging offset change request message comprising an indication of a request to change a timing offset value for the first DRX wakeup occasion.
The apparatus of claim 48, further comprising:

means for transmitting, to a core network entity, an S1 Application Protocol (S1AP) message based at least in part on the indication of the request to change the timing offset value.
The apparatus of claim 49, wherein the means for receiving the paging offset change message comprises:

means for receiving, from the core network entity, an S1AP response message comprising an indication of an acceptance of the request to change the timing offset value.
The apparatus of claim 50, wherein the means for transmitting the paging offset message comprises:

means for transmitting, to the UE, a second L3 message that indicates the timing offset value based at least in part on the indication of the acceptance of the request to change the timing offset value.
The apparatus of claim 47, wherein the means for transmitting the paging offset message comprises:

means for transmitting a radio resource control (RRC) message or a medium access control (MAC) control element that indicates a paging occasion offset.
The apparatus of claim 47, wherein the means for identifying the DRX offset change comprises:

means for receiving a radio resource control (RRC) message or a medium access control (MAC) control element that indicates a paging occasion offset request.
The apparatus of claim 47, wherein the means for identifying the DRX offset change comprises:

means for receiving, from a core network entity, a UE-specific control message indicating a timing offset for the first DRX wakeup occasion.
The apparatus of claim 54, further comprising:

means for configuring the UE in an idle state based at least in part on the UE-specific control message； and

means for transmitting, to a second base station, a radio access network (RAN) paging message indicating the timing offset, wherein transmitting the paging offset message is based at least in part on the RAN paging message.
The apparatus of claim 55, further comprising:

means for receiving, from the base station, incoming data for the UE, wherein transmitting the RAN paging message is based at least in part on the incoming data.
The apparatus of claim 47, wherein:

the paging offset message comprises a timing offset value for the first DRX wakeup occasion.
The apparatus of claim 57, further comprising:

means for calculating the timing offset value based at least in part on an international mobile subscriber identity (IMSI) associated with the UE.
The apparatus of claim 47, wherein:

the network node comprises the UE.
The apparatus of claim 47, wherein:

the network node comprises a core network entity.
An apparatus for wireless communication, in a system comprising:

a processor；

memory in electronic communication with the processor； and

instructions stored in the memory and operable, when executed by the processor, to cause the apparatus to:

identify, within a discontinuous reception (DRX) interval, a collision of a first DRX wakeup occasion of a first radio access technology (RAT) and a second DRX wakeup occasion of a second RAT；

identify an offset change for a DRX wakeup occasion of the first RAT based at least in part on the collision；

transmit, to a network node, a paging offset change request message based at least in part on the offset change； and

receive, from the network node, a paging offset acceptance message in response to the paging offset change request message.
The apparatus of claim 61, wherein the instructions are further executable by the processor to:

adjust the first DRX wakeup occasion of the first RAT based at least in part on the paging offset acceptance message.
The apparatus of claim 61, wherein the instructions are further executable by the processor to:

transmit a first layer 3 (L3) message comprising an indication of a request to change a timing offset value for the first DRX wakeup occasion.
The apparatus of claim 63, wherein the instructions are further executable by the processor to:

receive a second L3 message comprising an indication of an acceptance of the request to change the timing offset value.
The apparatus of claim 63, wherein:

at least one of the paging offset change request message and the paging offset acceptance message comprises an international mobile subscriber identity (IMSI) associated with a user equipment (UE) .
The apparatus of claim 61, wherein the instructions are further executable by the processor to:

transmit a non-access stratum (NAS) message comprising a tracking area update (TAU) .
The apparatus of claim 66, wherein the instructions are further executable by the processor to:

receive a NAS response message comprising a TAU acceptance and a timing offset value for the first DRX wakeup occasion.
The apparatus of claim 61, wherein the instructions are further executable by the processor to:

transmit a radio resource control (RRC) message or a medium access control (MAC) control element that indicates a paging occasion offset request.
The apparatus of claim 68, wherein the instructions are further executable by the processor to:

transmit a RRC response message or a MAC response control element in response to the paging occasion offset request.
The apparatus of claim 61, wherein:

the paging offset change request message comprises a requested timing offset value.
The apparatus of claim 70, wherein:

the paging offset acceptance message comprises an indication of acceptance of the requested timing offset value.
The apparatus of claim 70, wherein:

the paging offset acceptance message comprises a new timing offset value that is different from the requested timing offset value.
The apparatus of claim 70, wherein:

the requested timing offset value is calculated based at least in part on an international mobile subscriber identity (IMSI) associated with a user equipment (UE) .
The apparatus of claim 61, wherein:

the network node comprises a base station.
The apparatus of claim 61, wherein:

the network node comprises a core network entity.
The apparatus of claim 61, wherein the instructions are further executable by the processor to:

identify a previous overlap of the first DRX wakeup occasion and the second DRX wakeup occasion.
An apparatus for wireless communication, in a system comprising:

a processor；

memory in electronic communication with the processor； and

instructions stored in the memory and operable, when executed by the processor, to cause the apparatus to:

identify, within a discontinuous reception (DRX) interval, a DRX offset change for a first DRX wakeup occasion of a first radio access technology (RAT) associated with a user equipment (UE) , the DRX offset change being based at least in part on a collision of the first DRX wakeup occasion of the first RAT and a second DRX wakeup occasion of a second RAT；

receive, from a network node, a paging offset change message based at least in part on the DRX offset change； and

transmit, to the UE, a paging offset message in response to the paging offset change message.
The apparatus of claim 77, wherein the instructions are further executable by the processor to:

receive, from the UE, a layer 3 (L3) message comprising a paging offset change request message comprising an indication of a request to change a timing offset value for the first DRX wakeup occasion.
The apparatus of claim 78, wherein the instructions are further executable by the processor to:

transmit, to a core network entity, an S1 Application Protocol (S1AP) message based at least in part on the indication of the request to change the timing offset value.
The apparatus of claim 79, wherein the instructions are further executable by the processor to:

receive, from the core network entity, an S1AP response message comprising an indication of an acceptance of the request to change the timing offset value.
The apparatus of claim 80, wherein the instructions are further executable by the processor to:

transmit, to the UE, a second L3 message that indicates the timing offset value based at least in part on the indication of the acceptance of the request to change the timing offset value.
The apparatus of claim 77, wherein the instructions are further executable by the processor to:

transmit a radio resource control (RRC) message or a medium access control (MAC) control element that indicates a paging occasion offset.
The apparatus of claim 77, wherein the instructions are further executable by the processor to:

receive a radio resource control (RRC) message or a medium access control (MAC) control element that indicates a paging occasion offset request.
The apparatus of claim 77, wherein the instructions are further executable by the processor to:

receive, from a core network entity, a UE-specific control message indicating a timing offset for the first DRX wakeup occasion.
The apparatus of claim 84, wherein the instructions are further executable by the processor to:

configure the UE in an idle state based at least in part on the UE-specific control message； and

transmit, to a second base station, a radio access network (RAN) paging message indicating the timing offset, wherein transmitting the paging offset message is based at least in part on the RAN paging message.
The apparatus of claim 85, wherein the instructions are further executable by the processor to:

receive, from the base station, incoming data for the UE, wherein transmitting the RAN paging message is based at least in part on the incoming data.
The apparatus of claim 77, wherein:

the paging offset message comprises a timing offset value for the first DRX wakeup occasion.
The apparatus of claim 87, wherein the instructions are further executable by the processor to:

calculate the timing offset value based at least in part on an international mobile subscriber identity (IMSI) associated with the UE.
The apparatus of claim 77, wherein:

the network node comprises the UE.
The apparatus of claim 77, wherein:

the network node comprises a core network entity.
A non-transitory computer readable medium storing code for wireless communication, the code comprising instructions executable by a processor to:

identify, within a discontinuous reception (DRX) interval, a collision of a first DRX wakeup occasion of a first radio access technology (RAT) and a second DRX wakeup occasion of a second RAT；

identify an offset change for a DRX wakeup occasion of the first RAT based at least in part on the collision；

transmit, to a network node, a paging offset change request message based at least in part on the offset change； and

receive, from the network node, a paging offset acceptance message in response to the paging offset change request message.
The non-transitory computer-readable medium of claim 91, wherein the instructions are further executable by the processor to:

adjust the first DRX wakeup occasion of the first RAT based at least in part on the paging offset acceptance message.
The non-transitory computer-readable medium of claim 91, wherein the instructions are further executable by the processor to:

transmit a first layer 3 (L3) message comprising an indication of a request to change a timing offset value for the first DRX wakeup occasion.
The non-transitory computer-readable medium of claim 93, wherein the instructions are further executable by the processor to:

receive a second L3 message comprising an indication of an acceptance of the request to change the timing offset value.
The non-transitory computer-readable medium of claim 93, wherein:

at least one of the paging offset change request message and the paging offset acceptance message comprises an international mobile subscriber identity (IMSI) associated with a user equipment (UE) .
The non-transitory computer-readable medium of claim 91, wherein the instructions are further executable by the processor to:

transmit a non-access stratum (NAS) message comprising a tracking area update (TAU) .
The non-transitory computer-readable medium of claim 96, wherein the instructions are further executable by the processor to:

receive a NAS response message comprising a TAU acceptance and a timing offset value for the first DRX wakeup occasion.
The non-transitory computer-readable medium of claim 91, wherein the instructions are further executable by the processor to:

transmit a radio resource control (RRC) message or a medium access control (MAC) control element that indicates a paging occasion offset request.
The non-transitory computer-readable medium of claim 98, wherein the instructions are further executable by the processor to:

transmit a RRC response message or a MAC response control element in response to the paging occasion offset request.
The non-transitory computer-readable medium of claim 91, wherein:

the paging offset change request message comprises a requested timing offset value.
The non-transitory computer-readable medium of claim 100, wherein:

the paging offset acceptance message comprises an indication of acceptance of the requested timing offset value.
The non-transitory computer-readable medium of claim 100, wherein:

the paging offset acceptance message comprises a new timing offset value that is different from the requested timing offset value.
The non-transitory computer-readable medium of claim 100, wherein:

the requested timing offset value is calculated based at least in part on an international mobile subscriber identity (IMSI) associated with a user equipment (UE) .
The non-transitory computer-readable medium of claim 91, wherein:

the network node comprises a base station.
The non-transitory computer-readable medium of claim 91, wherein:

the network node comprises a core network entity.
The non-transitory computer-readable medium of claim 91, wherein the instructions are further executable by the processor to:

identify a previous overlap of the first DRX wakeup occasion and the second DRX wakeup occasion.
A non-transitory computer readable medium storing code for wireless communication, the code comprising instructions executable by a processor to:

identify, within a discontinuous reception (DRX) interval, a DRX offset change for a first DRX wakeup occasion of a first radio access technology (RAT) associated with a user equipment (UE) , the DRX offset change being based at least in part on a collision of the first DRX wakeup occasion of the first RAT and a second DRX wakeup occasion of a second RAT；

receive, from a network node, a paging offset change message based at least in part on the DRX offset change； and

transmit, to the UE, a paging offset message in response to the paging offset change message.
The non-transitory computer-readable medium of claim 107, wherein the instructions are further executable by the processor to:

receive, from the UE, a layer 3 (L3) message comprising a paging offset change request message comprising an indication of a request to change a timing offset value for the first DRX wakeup occasion.
The non-transitory computer-readable medium of claim 108, wherein the instructions are further executable by the processor to:

transmit, to a core network entity, an S1 Application Protocol (S1AP) message based at least in part on the indication of the request to change the timing offset value.
The non-transitory computer-readable medium of claim 109, wherein the instructions are further executable by the processor to:

receive, from the core network entity, an S1AP response message comprising an indication of an acceptance of the request to change the timing offset value.
The non-transitory computer-readable medium of claim 110, wherein the instructions are further executable by the processor to:

transmit, to the UE, a second L3 message that indicates the timing offset value based at least in part on the indication of the acceptance of the request to change the timing offset value.
The non-transitory computer-readable medium of claim 107, wherein the instructions are further executable by the processor to:

transmit a radio resource control (RRC) message or a medium access control (MAC) control element that indicates a paging occasion offset.
The non-transitory computer-readable medium of claim 107, wherein the instructions are further executable by the processor to:

receive a radio resource control (RRC) message or a medium access control (MAC) control element that indicates a paging occasion offset request.
The non-transitory computer-readable medium of claim 107, wherein the instructions are further executable by the processor to:

receive, from a core network entity, a UE-specific control message indicating a timing offset for the first DRX wakeup occasion.
The non-transitory computer-readable medium of claim 114, wherein the instructions are further executable by the processor to:

configure the UE in an idle state based at least in part on the UE-specific control message； and

transmit, to a second base station, a radio access network (RAN) paging message indicating the timing offset, wherein transmitting the paging offset message is based at least in part on the RAN paging message.
The non-transitory computer-readable medium of claim 115, wherein the instructions are further executable by the processor to:

receive, from the base station, incoming data for the UE, wherein transmitting the RAN paging message is based at least in part on the incoming data.
The non-transitory computer-readable medium of claim 107, wherein:

the paging offset message comprises a timing offset value for the first DRX wakeup occasion.
The non-transitory computer-readable medium of claim 117, wherein the instructions are further executable by the processor to:

calculate the timing offset value based at least in part on an international mobile subscriber identity (IMSI) associated with the UE.
The non-transitory computer-readable medium of claim 107, wherein:

the network node comprises the UE.
The non-transitory computer-readable medium of claim 107, wherein:

the network node comprises a core network entity.