Override of the default base station discontinuous reception cycle for individual user equipment

Abstract

Aspects of the present disclosure relate to: a UE sending a request for a discontinuous reception (DRX) cycle for a first duration; receiving an indication that a DRX cycle having a second duration has been assigned to the UE by a core network component; receiving a system information block (SIB) from a base station, the SIB including: a default paging cycle; and an indication regarding support for overriding the default; entering an inactive state in which a transceiver of the UE is in a low power state; and, when the UE is in the inactive state, causing the transceiver to periodically enter a higher power state based on the second duration to monitor its paging channel. Other aspects, embodiments, and features are also claimed and described.

Description

[0001] Cross - Reference to Related Applications

[0002] This application claims the benefit of priority from non - provisional patent application No. 17 / 022,870, filed on September 16, 2020, with the United States Patent and Trademark Office, which claims the benefit of priority and the benefit of the filing date of provisional patent application No. 63 / 026,541, filed on May 18, 2020, with the United States Patent and Trademark Office. The entire contents of the above - mentioned applications are incorporated herein by reference as if set forth in full and for all applicable purposes. Technical Field

[0003] Generally speaking, the techniques described below relate to wireless communication systems, and more specifically, the techniques described below relate to changing the discontinuous reception (DRX) cycle for an individual user equipment. Various embodiments may provide and implement techniques for overriding the default base - station discontinuous reception cycle for an individual user equipment. Background Art

[0004] As the demand for mobile broadband access continues to increase, research and development continue to advance wireless communication technologies, not only to meet the growing demand for mobile broadband access, but also to promote and enhance the user experience of mobile communication. Summary of the Invention

[0005] A brief overview of one or more aspects of the present disclosure is given below in order to provide a basic understanding of these aspects. This overview is not an exhaustive overview of all the expected features of the present disclosure and is not intended to identify the key or important elements of all aspects of the present disclosure, nor to delineate the scope of any or all aspects of the present disclosure. Its sole purpose is to present some concepts of one or more aspects of the present disclosure in a simplified form as a prelude to the more detailed description that is given later.

[0006] In one example, a method of wireless communication at a user equipment is disclosed. In a more specific example, the method includes: sending, by the user equipment, a request for a discontinuous reception (DRX) cycle interval for a first duration; receiving, by the user equipment, an indication that a DRX cycle interval having a second duration has been assigned to the user equipment by a core - network component; receiving, by the user equipment, a system information block (SIB) from a base station, the SIB including: a default paging cycle; and an indication of support for overriding the default paging cycle; entering, by the user equipment, an inactive state in which the transceiver of the user equipment is in a low - power state; and when the user equipment is in the inactive state and based on the indication of the base - station support for overriding the default paging cycle, causing the transceiver to periodically enter a higher - power state at a period based on the second duration to monitor its paging channel.

[0007] In another example, a wireless communication device is disclosed. In a more specific example, the wireless communication device includes: a transceiver; a memory; and a processor communicatively coupled to the transceiver and the memory, the processor being configured to: send a request for a discontinuous reception (DRX) cycle interval of a first duration; receive an indication that a DRX cycle interval of a second duration has been assigned to the wireless communication device by a core network component; receive a system information block (SIB) from a base station, the SIB including: a default paging cycle; and an indication of support for overriding the default paging cycle; enter an inactive state in which the transceiver is in a low power state; and when the wireless communication device is in the inactive state and based on the indication of support for overriding the default paging cycle by the base station, cause the transceiver to periodically enter a higher power state at a period based on the second duration to monitor its paging channel.

[0008] In another more specific example, the wireless communication device includes: a unit for sending a request for a discontinuous reception (DRX) cycle interval of a first duration; a unit for receiving an indication that a DRX cycle interval of a second duration has been assigned to the user equipment by a core network component; a unit for receiving a system information block (SIB) from a base station, the SIB including: a default paging cycle; and an indication of support for overriding the default paging cycle; a unit for entering an inactive state in which the transceiver of the user equipment is in a low power state; and a unit for, when the wireless communication device is in the inactive state and based on the indication of support for overriding the default paging cycle by the base station, causing the transceiver to periodically enter a higher power state at a period based on the second duration to monitor its paging channel.

[0009] In another example, a non-transitory processor-readable storage medium storing a processor-executable program is disclosed. In a more specific example, the processor-executable program is for causing a processing circuit to perform the following operations: send a request for a discontinuous reception (DRX) cycle interval of a first duration; receive an indication that a DRX cycle interval of a second duration has been assigned to the user equipment by a core network component; receive a system information block (SIB) from a base station, the SIB including: a default paging cycle; and an indication of support for overriding the default paging cycle; cause a user equipment associated with the processing circuit to enter an inactive state in which a transceiver operatively coupled to the processing circuit is in a low power state; and when the user equipment wireless communication device is in the inactive state and based on the indication of support for overriding the default paging cycle by the base station, cause the transceiver to periodically enter a higher power state at a period based on the second duration to monitor its paging channel.

[0010] In another example, a method for wireless communication at a core network component is disclosed. In a more specific example, the method includes: receiving, from a user equipment, a request for a discontinuous reception (DRX) cycle interval for a first duration; assigning, to the user equipment, a DRX cycle interval having a second duration; sending, to the user equipment, an indication that the DRX cycle interval having the second duration has been assigned to the user equipment; and sending, to a base station in a registration area where the user equipment is located, a paging message, the paging message including: an indication that the DRX cycle interval having the second duration has been assigned to the user equipment; and an indication that allows overriding of a default paging cycle of the base station.

[0011] In another example, a core network component is disclosed. In a more specific example, the core network component includes: a transceiver; a memory; and a processor communicatively coupled to the transceiver and the memory, the processor being configured to: receive, from a user equipment, a request for a discontinuous reception (DRX) cycle interval for a first duration; assign, to the user equipment, a DRX cycle interval having a second duration; send, to the user equipment, an indication that the DRX cycle interval having the second duration has been assigned to the user equipment; and send, to a base station in a registration area where the user equipment is located, a paging message, the paging message including: an indication that the DRX cycle interval having the second duration has been assigned to the user equipment; and an indication that allows overriding of a default paging cycle of the base station.

[0012] In another more specific example, a core network component includes: a unit for receiving, from a user equipment, a request for a discontinuous reception (DRX) cycle interval for a first duration; a unit for assigning, to the user equipment, a DRX cycle interval having a second duration; a unit for sending, to the user equipment, an indication that the DRX cycle interval having the second duration has been assigned to the user equipment; and a unit for sending, to a base station in a registration area where the user equipment is located, a paging message, the paging message including: an indication that the DRX cycle interval having the second duration has been assigned to the user equipment; and an indication that allows overriding of a default paging cycle of the base station.

[0013] In another example, a non-transitory processor-readable storage medium storing a processor-executable program is disclosed. In a more specific example, the processor-executable program is for causing a processing circuit to perform the following operations: receiving, from a user equipment, a request for a discontinuous reception (DRX) cycle interval for a first duration; assigning, to the user equipment, a DRX cycle interval having a second duration; sending, to the user equipment, an indication that a DRX cycle interval having the second duration has been assigned to the user equipment; and sending, to a base station in a registration area where the user equipment is located, a paging message, the paging message including: an indication that a DRX cycle interval having the second duration has been assigned to the user equipment; and an indication that allows overriding of a default paging cycle of the base station.

[0014] In another example, a method for wireless communication at a base station is disclosed. The method includes: broadcasting, by the base station, a system information block (SIB), the SIB including: a default paging cycle; and an indication that supports overriding of the default paging cycle; receiving, from a core network component, a paging message, the paging message including: an indication that a DRX cycle interval having a second duration has been assigned to a user equipment; and an indication that allows overriding of the default paging cycle of the base station; and paging, based on the indication that allows overriding of the default paging cycle, the user equipment periodically at a period based on the second duration.

[0015] In another example, a scheduling entity is disclosed. In a more specific example, the scheduling entity includes: a transceiver; a network interface; a memory; and a processor communicatively coupled to the transceiver and the memory, the processor being configured to: use the transceiver to broadcast a system information block (SIB), the SIB including: a default paging cycle; and an indication that supports overriding of the default paging cycle; use the network interface to receive, from a core network component, a paging message, the paging message including: an indication that a DRX cycle interval having a second duration has been assigned to a user equipment; and an indication that allows overriding of the default paging cycle of the base station; and use the transceiver and based on the indication that allows overriding of the default paging cycle, to page the user equipment periodically at a period based on the second duration.

[0016] In another more specific example, the scheduling entity includes: a unit for broadcasting a system information block (SIB), the SIB including: a default paging cycle; and an indication that supports overriding of the default paging cycle; a unit for receiving, from a core network component, a paging message, the paging message including: an indication that a DRX cycle interval having a second duration has been assigned to a user equipment; and an indication that allows overriding of the default paging cycle of the base station; and a unit for paging the user equipment periodically at a period based on the second duration.

[0017] In another example, a non-transitory processor-readable storage medium storing a processor-executable program is disclosed. In a more specific example, the processor-executable program is for causing a processing circuit to perform the following operations: using a transceiver to broadcast a system information block (SIB), the SIB including: a default paging cycle; and an indication of support for overriding the default paging cycle; using a network interface to receive a paging message from a core network component, the paging message including: an indication that a discontinuous reception (DRX) cycle interval having a second duration has been assigned to a user equipment; and an indication of permission to override the default paging cycle of a base station; and using the transceiver and based on the indication of permission to override the default paging cycle, to periodically page the user equipment at a period based on the second duration.

[0018] After reviewing the following detailed description, these and other aspects of the present invention will become more fully understood. After reviewing the following description of specific exemplary embodiments in conjunction with the accompanying drawings, other aspects, features, and embodiments will become apparent to those of ordinary skill in the art. Although the following may discuss features with respect to certain embodiments and drawings, all embodiments may include one or more of the advantageous features discussed herein. In other words, although one or more embodiments may be discussed as having certain advantageous features, one or more of such features may also be used in accordance with the various embodiments discussed herein. In a similar manner, although the following may discuss exemplary embodiments as device, system, or method embodiments, it should be understood that such exemplary embodiments may be implemented in various devices, systems, and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1 is a schematic diagram of a wireless communication system in accordance with some aspects of the disclosed subject matter.

[0020] Figure 2 is a conceptual diagram of an example of a radio access network in accordance with some aspects of the disclosed subject matter.

[0021] Figure 3 is a conceptual diagram of logical connections between parts of a wireless communication system in accordance with some aspects of the disclosed subject matter.

[0022] Figure 4 is a block diagram conceptually illustrating an example of a hardware implementation for a scheduling entity in accordance with some aspects of the disclosed subject matter.

[0023] Figure 5 is a block diagram conceptually illustrating an example of a hardware implementation for a scheduled entity in accordance with some aspects of the disclosed subject matter.

[0024] Figure 6 is a block diagram conceptually showing an example of a hardware implementation for an access and mobility management function node according to some aspects of the disclosed subject matter.

[0025] Figure 7 is a signaling diagram showing exemplary signaling for scheduling a discontinuous reception cycle for a scheduled entity between a core network, a scheduling entity, and the scheduled entity within a wireless communication system according to some aspects of the disclosed subject matter.

[0026] Figure 8 is a flowchart showing an exemplary process for a scheduled entity to determine a discontinuous reception cycle to utilize with a scheduling entity in a registration area according to some aspects of the disclosed subject matter.

[0027] Figure 9 is a flowchart showing an exemplary process for a scheduling entity to determine a discontinuous reception cycle to use for sending a paging message intended for a specific scheduled entity according to some aspects of the disclosed subject matter.

[0028] Figure 10 is a flowchart showing an exemplary process for an access and mobility management function node to select a discontinuous reception cycle for a specific scheduled entity and override a default discontinuous reception cycle of a scheduling entity in a registration area according to some aspects of the disclosed subject matter. Detailed Description

[0029] The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be implemented. For the purpose of providing a thorough understanding of the various concepts, the detailed description includes specific details. It will be apparent, however, to one of ordinary skill in the art that these concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0030] While aspects and embodiments are described herein by way of illustration of some examples, those skilled in the art will understand that additional implementations and use cases may arise in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, packaging arrangements. For example, the embodiments and / or uses may be implemented via integrated chip embodiments and other non-module component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial devices, retail / purchase devices, medical devices, artificial intelligence-enabled devices, etc.). Although some examples may or may not be specific to a use case or application, a wide classification of applicability of the described innovations may occur. Implementations can range from chip-level or modular components to non-modular, non-chip-level implementations and further to aggregated, distributed, or OEM devices or systems incorporating one or more aspects of the described innovations. In some practical settings, devices incorporating the described aspects and features may also necessarily include additional components and features for the implementation and practice of the claimed and described embodiments. For example, the transmission and reception of wireless signals necessarily includes multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The innovations described herein are intended to be implementable in a variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc. having different sizes, shapes, and configurations.

[0031] The various concepts presented throughout this disclosure can be implemented in a wide variety of telecommunications systems, network architectures, and communication standards.

[0032] Figure 1 is a schematic diagram of a wireless communication system 100 in accordance with some aspects of the disclosed subject matter and is described as a non-limiting illustrative example. In some aspects, the wireless communication system 100 can include three interacting domains: a core network 102, a radio access network (RAN) 104, and a user equipment (UE) 106. In some aspects, with the aid of the wireless communication system 100, the UE 106 can be implemented to perform data communication with an external data network 110 (such as, but not limited to, the Internet).

[0033] In some aspects, RAN 104 may implement any suitable wireless communication technology or combination of technologies to provide radio access to UE 106. For example, RAN 104 may operate according to the 3rd Generation Partnership Project (3GPP) New Radio (NR) specifications, which are sometimes referred to as 5G NR or simply 5G. As another example, RAN 104 may operate based on a hybrid of 5G NR and the evolved Universal Terrestrial Radio Access Network (eUTRAN) standard, which is sometimes referred to as LTE. 3GPP refers to this hybrid RAN as the Next Generation RAN or NG-RAN. Of course, many other examples may be utilized in conjunction with the subject matter disclosed herein without departing from the scope of the present disclosure.

[0034] As shown in the example of Figure 1 , RAN 104 includes various base stations 108. Broadly speaking, a base station may be used to implement a network element in a radio access network that is responsible for radio transmission and reception to or from a UE (such as UE 106) in one or more cells. In different technologies, standards, and / or contexts, various terms have been used to refer to the network element acting as a base station. For example, those skilled in the art may also use terms to refer to a base station to refer to a network element that connects one or more UE devices to one or more parts of the core network 102, such as a base transceiver station (BTS), radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), access point (AP), Node B (NB), evolved Node B (eNB), gNode B (gNB), or some other suitable term.

[0035] In some aspects, as Figure 1 shown, RAN 104 may support wireless communication for multiple mobile devices. In 3GPP standards, a mobile device may be referred to as a user equipment (UE), but those skilled in the art may also use various terms to refer to a mobile device to refer to a network element that provides a user with access to one or more network services, such as a mobile station (MS), user station, mobile unit, user unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile user station, access terminal (AT), mobile terminal, wireless terminal, remote terminal, cell phone, terminal, user agent, mobile client, client, or some other suitable term. Generally, a UE may be a device (e.g., a mobile device) that provides a user with access to network services.

[0036] Within this document, a "mobile" device does not necessarily need to have the ability to move and can be stationary. The term mobile device or mobile equipment broadly refers to a wide variety of devices and technologies. A UE may include multiple hardware structural components, the size, shape, and arrangement of which are convenient for communication; such components may include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc. that are electrically coupled to each other. For example, some non-limiting examples of mobile devices include mobile phones, cellular (cell) phones, smartphones, Session Initiation Protocol (SIP) phones, laptop computers, personal computers (PCs), notebooks, netbooks, smartbooks, tablet devices, personal digital assistants (PDAs), and various embedded systems (e.g., corresponding to the "Internet of Things" (IoT)). Additionally, a mobile device can be an automobile or other transportation vehicle, a remote sensor or actuator, a robot or robotic device, a satellite radio unit, a Global Positioning System (GPS) device, an object tracking device, a drone, a multi-wing aircraft, a quadcopter, a remote control device, a consumer device, and / or a wearable device (such as glasses, a wearable camera, a virtual reality device, a smartwatch, a health and / or fitness tracker, a digital audio player (e.g., an MP3 player), a camera, a game console, etc.). Additionally, a mobile device can be a digital home device or a smart home device, such as a home audio device, a home video device, and / or a home multimedia device, an appliance, a vending machine, smart lighting, a home security system, a smart meter, etc. Additionally, a mobile device can be a smart energy device, a security device, a solar panel and / or a solar array, a municipal infrastructure device for controlling electricity (e.g., a smart grid), a municipal infrastructure device for controlling lighting, a municipal infrastructure device for controlling water, etc.; industrial automation and enterprise equipment; a logistics controller; agricultural equipment; military defense equipment, vehicles, airplanes, ships, weapons, etc. Further, a mobile device can provide connected medical or telemedicine support (e.g., telehealthcare). A telemedicine device can include a telemedicine monitoring device and a telemedicine management device, and its communication can be given priority processing or priority access relative to other types of information (e.g., in terms of priority access for the transmission of critical service data, and / or in terms of the relevant QoS for the transmission of critical service data).

[0037] In some aspects, in Figure 1The wireless communication between the RAN 104 and the UE 106 shown can be described as utilizing an air interface. Transmissions from a base station (e.g., base station 108) to one or more UEs (e.g., UE 106) over the air interface can be referred to as downlink (DL) transmissions. According to some aspects of the disclosed subject matter, the term downlink can refer to point-to-multipoint transmissions originating at a scheduling entity (e.g., base station 108). For example, downlinks can be implemented using one or more broadcast channel multiplexing techniques. In some aspects, transmissions from a UE (e.g., UE 106) to a base station (e.g., base station 108) can be referred to as uplink (UL) transmissions. According to some aspects of the disclosed subject matter, the term uplink can refer to point-to-point transmissions originating at a scheduled entity (e.g., UE 106).

[0038] In some aspects, access to the air interface can be scheduled, where a scheduling entity (e.g., a base station of the RAN 104, such as base station 108) allocates resources for communication among some or all of the devices and apparatuses within its service area or cell. For example, as described below in connection with Figure 9 and Figure 10 the scheduling entity can be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities. In such an example, for a scheduled communication, the scheduled entity (e.g., UE 106) can use the resources allocated by the scheduling entity (e.g., base station 108).

[0039] In some aspects, base station 108 is not the only entity that can act as a scheduling entity. For example, in some instances, a UE can act as a scheduling entity, scheduling resources for one or more scheduled entities (e.g., one or more other UEs).

[0040] As Figure 1 shown, in some aspects, a scheduling entity (e.g., base station 108) can broadcast downlink traffic 112 to one or more scheduled entities (e.g., UE 106). Broadly speaking, in some aspects, a scheduling entity (e.g., base station 108) can act as a node or device responsible for scheduling traffic in a wireless communication network, including downlink traffic 112 and in some examples uplink traffic 116 from one or more scheduled entities (e.g., UE 106) to the scheduling entity (e.g., base station 108). Additionally, a scheduled entity (e.g., UE 106) can act as a node or device that receives downlink control information 114 (which can include, but is not limited to, scheduling information (e.g., grants), synchronization or timing information, and / or other control information) from another entity in the wireless communication network, such as the scheduling entity (e.g., base station 108).

[0041] Typically, in some aspects, base station 108 may include a backhaul interface for communication with the backhaul portion 120 of the wireless communication system. In some aspects, backhaul 120 may provide a link between a particular base station and core network 102. Additionally, in some examples, the backhaul network (e.g., including backhaul 120) may provide interconnection between various base stations 108. Various types of backhaul interfaces may be employed, such as direct physical connections, virtual networks, and / or any other suitable connections using any appropriate transport network.

[0042] In some aspects, core network 102 may be part of wireless communication system 100 and may be independent of the radio access technology used in RAN 104. In some aspects, core network 102 may be configured according to 5G standards (e.g., 5GC). Additionally or alternatively, in some aspects, core network 102 may be configured according to 4G evolved packet core (EPC) or any other suitable standard or configuration.

[0043] In some aspects, UE 106 may be connected to multiple base stations 108 simultaneously and / or may be connected to a single base station 108 using multiple component carriers (e.g., at different frequencies) to increase the bandwidth available for communication to and / or from UE 106.

[0044] Figure 2 is a conceptual diagram of an example of radio access network 200 according to some aspects of the disclosed subject matter and is described as a non-limiting illustrative example. In some aspects, RAN 200 may be an implementation of RAN 104 described above in Figure 1 and shown in Figure 1 In some aspects, the geographical area covered by RAN 200 may be divided into cellular regions (cells), and user equipment (UE) may uniquely identify these cellular regions (cells) based on an identifier broadcast from an access point or base station. Figure 2 Macro cells 202, 204, and 206 and small cell 208 are shown, each of which may include one or more sectors (not shown). For example, a sector may be defined as a sub-region of a cell, and all sectors within a cell may be served by the same base station. Radio links within a sector may be identified by a single logical identifier belonging to that sector. In a cell divided into multiple sectors, multiple sectors within the cell may be formed by multiple sets of antennas, where each antenna is responsible for communication with UEs in a portion of the cell.

[0045] In Figure 2In [the figure], two base stations 210 and 212 are shown in cells 202 and 204; and a third base station 214 is shown controlling a remote radio head (RRH) 216 in cell 206. That is, a base station may have an integrated antenna or may be connected to an antenna or RRH via a feeder cable. In the example shown, cells 202, 204, and 206 may be referred to as macro cells since base stations 210, 212, and 214 support cells with relatively large sizes. Additionally, a base station 218 is shown in a small cell 208 (which may be referred to as, for example, a micro cell, a pico cell, a femto cell, a home base station, a home Node B, a home eNode B, etc.), and small cell 208 may overlap with one or more macro cells. In Figure 2 the example shown, cell 208 may be referred to as a small cell since base station 218 supports a cell with a relatively small size. In some aspects, the cell size may be determined based on system design and component constraints.

[0046] It should be understood that radio access network 200 may include any number of radio base stations and cells. Additionally, relay nodes may be deployed to extend the size or coverage area of a given cell. Further, base stations 210, 212, 214, 218 may provide a wireless access point to the core network for any number of mobile devices. In some examples, base stations 210, 212, 214, and / or 218 may be a specific implementation of base station 108 described above in conjunction with Figure 1 and shown in Figure 1 the figure.

[0047] Figure 2 Also included is a quadcopter 220 (which is sometimes referred to as a drone), and quadcopter 220 may be configured to function as a base station. That is, in some examples, a cell may not necessarily be stationary, and the geographical area of a cell may move according to the position of a mobile base station such as quadcopter 220.

[0048] Within RAN 200, a cell may include UEs that may communicate with one or more sectors of each cell. Additionally, each of base stations 210, 212, 214, 218, and 220 may be configured to provide access to core network 102 for all UEs in the respective cell (e.g., as described above in conjunction with Figure 1The access points described). For example, UEs 222 and 224 can communicate with base station 210, UEs 226 and 228 can communicate with base station 212, UEs 230 and 232 can communicate with base station 214 via RRH 216, UE 234 can communicate with base station 218, and UE 236 can communicate with mobile base station 220. In some examples, UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240, and / or 242 can be specific implementations of UE 106 described above in conjunction with Figure 1 described and shown in Figure 1 FIG.

[0049] In some examples, a mobile network node (e.g., quadcopter 220) can be configured to act as a UE. For example, quadcopter 220 can operate within cell 202 by communicating with base station 210.

[0050] In some aspects, sidelink signals can be used between UEs without relying on scheduling or control information from a base station. For example, two or more UEs (e.g., UEs 226 and 228) can use peer-to-peer (P2P) or sidelink signals to communicate with each other without relaying the communication through a base station (e.g., base station 212). In another example, UE 238 is shown communicating with UEs 240 and 242. In such an example, UE 238 can act as a scheduling entity or a primary sidelink device, and UEs 240 and 242 can act as scheduled entities or non-primary (e.g., secondary) sidelink devices. In yet another example, a UE can act as a scheduling entity in a device-to-device (D2D), peer-to-peer (P2P), or vehicle-to-vehicle (V2V) network and / or in a mesh network. In the mesh network example, UEs 240 and 242 can optionally communicate directly with each other in addition to communicating with a scheduling entity (e.g., UE 238). Thus, in a wireless communication system with scheduled access to time-frequency resources and having a cellular configuration, P2P configuration, and / or mesh configuration, a scheduling entity and one or more scheduled entities can utilize the scheduled resources to communicate.

[0051] In some aspects, the ability of a UE to communicate while moving (regardless of its location) (e.g., within radio access network 200) can be referred to as mobility. Generally, it can be in an access and mobility management function (AMF, not shown, which can be via the above in conjunction with Figure 1Under the control of the described core network 102, various physical channels between the UE and the radio access network are established, maintained, and released. The AMF may include a security context management function (SCMF) that manages security contexts for both control plane and user plane functionality, and a security anchor function (SEAF) that performs authentication.

[0052] In some aspects, the UE can enter an idle state (sometimes referred to as RRC_IDLE) or an inactive state (sometimes referred to as RRC_INACTICE), in which power consumption can be reduced by powering down one or more components (e.g., components of the receive chain) and periodically powering on the one or more components to determine whether a paging message has been directed to the UE. Typically, the UE can power on such components at a pre-determined frequency or period, which can be referred to as a discontinuous reception (DRX) cycle or an idle / inactive DRX (I-DRX). Typically, the UE can use its UE identification information (UE ID) to determine the paging frames and paging occasions (PF / PO) on which it may expect to receive paging messages. There are typically two parameters that can be used to control the DRX cycle for the UE to power on and check for paging messages: the RAN paging cycle (which can be cell-specific) and the DRX cycle that has been negotiated between the UE and the core network (e.g., with the AMF) during the registration process. As described below in conjunction with Figures 7 - 10 If the base station does not support the mechanism described herein for overriding the RAN paging cycle, the UE and the base station can use the RAN paging cycle or the DRX cycle assigned to the UE by the core network, whichever is shorter. Otherwise, if the base station does support the mechanism described herein for overriding the RAN paging cycle, the UE and the base station can use the DRX cycle assigned to the UE by the core network, even if the DRX cycle exceeds the duration of the default RAN paging cycle. Allowing the UE to use a DRX cycle longer than the RAN paging cycle may be advantageous in certain applications. For example, when the UE is in an inactive state (e.g., in a non-disturbance mode, in a mode where transmission and / or synchronous communication is not expected, etc.), the paging latency can be relaxed, and allowing the UE to use a longer DRX cycle can save power. In such an example, existing techniques for very long paging cycles (e.g., used by some Internet of Things devices) may not be suitable because the UE may need to maintain a certain level of connectivity (e.g., to receive emergency communications, receive permitted communications, perform mobility operations, etc.).

[0053] In some aspects, when the UE is in the idle or inactive state, paging can allow the network to reach the UE via paging messages that can be sent at DRX cycle intervals. Such paging messages can be used to notify UEs in the idle, inactive, and / or connected (e.g., active) states of system information changes and other indications, such as emergency alert messages (e.g., earthquake and tsunami alert system messages, commercial mobile alert system messages). The UE can monitor the paging channel for any core network-initiated paging message in the idle state at the DRX cycle, and can monitor the paging channel for any RAN-initiated paging message in the inactive state at the DRX cycle.

[0054] Figure 3 FIG. 4 is a conceptual diagram of logical connections between parts of a wireless communication system 300 according to some aspects of the disclosed subject matter and is described as a non-limiting illustrative example. In some aspects, the wireless communication system 300 can include three interacting domains: a core network (CN) that can include one or more access and mobility management function nodes (AMF) 302, a radio access network (RAN) 304, and a user equipment (UE) 306. In some aspects, the connection 310 can represent a logical interface between the UE 306 and the AMF 302, which can be referred to as the N1 interface. In some aspects, the connection 320 can represent a logical and / or network interface between the RAN 304 and the AMF 302, which can be referred to as the N2 interface. In some aspects, the connection 312 can represent an air interface between the UE 306 and the RAN 304 (e.g., one or more base stations within the RAN 304). In some aspects, the air interface 312 and the N2 interface 320 can be used as network interfaces over which a logical connection represented by the N1 interface 310 can be formed between the UE 306 and the AMF 302.

[0055] In some aspects, the N1 interface 310 can be used by the UE 306 and the AMF 302 to exchange non-access stratum (NAS) messages between the UE 306 and the AMF 302. For example, when the UE 306 attempts to access a new registration area, NAS messages can be used to send a registration request and receive a registration acceptance message indicating that the AMF 302 has accepted the registration of the UE 306 within the registration area.

[0056] In some aspects, the RAN 304 and the AMF 302 can use the N2 interface 320 to exchange control plane messages, such as messages related to the mobility of the UE (e.g., UE 306), messages related to changes in system information (e.g., sent via paging messages), and messages related to UE context management.

[0057] Figure 4is a block diagram conceptually showing an example of a hardware implementation for scheduling entity 400 according to some aspects of the disclosed subject matter and is described as a non-limiting illustrative example. For example, scheduling entity 400 can be a base station as shown in one or more of the diagrams in Figure 1 and / or Figure 2 . In another example, scheduling entity 400 can be a user equipment as shown in any one or more of the diagrams in Figure 1 and / or Figure 2 .

[0058] In some aspects, scheduling entity 400 can be implemented using a processing system 414 that includes one or more processors 404. Examples of processors 404 include a central processing unit (CPU), a microprocessor, a microcontroller, a digital signal processor (DSP), a field programmable gate array (FPGA), a programmable logic device (PLD), a graphics processing unit (GPU), a state machine, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described throughout this disclosure. In various examples, scheduling entity 400 can be configured to perform any one or more of the functions described herein. That is, the processor 404 as utilized in scheduling entity 400 can be used to implement any one or more of the processes or programs described below in connection with Figures 7 - 10 .

[0059] In this example, the processing system 414 can be implemented using a bus architecture typically represented by bus 402. Bus 402 can include any number of interconnecting buses and bridges, depending on the specific application of the processing system 414 and overall design constraints. Bus 402 communicatively couples various circuits including one or more processors (commonly represented by processor 404), memory 405, and a computer-readable medium (commonly represented by computer-readable medium 406). Bus 402 can also link various other circuits such as a timing source, peripherals, voltage regulators, and power management circuits, which are well known in the art and will not be described any further herein. Bus interface 408 can provide an interface between bus 402 and transceiver 410. Transceiver 410 can provide a wireless communication interface or unit for communicating with various other devices over a transmission medium. Additionally, in some aspects, bus interface 408 can provide an interface between bus 402 and network interface 416. Network interface 416 can provide a wired communication interface or unit for communicating with various other devices over a transmission medium. For example, network interface 416 can be used to establish an N2 interface that can be used to communicate with one or more parts of a core network (e.g., for communication with an access and mobility management function node (AMF)). Depending on the nature of the device, a user interface 412 (e.g., keypad, display, speaker, microphone, joystick) can also be provided. Of course, in some examples (such as a base station), such a user interface 412 can be omitted.

[0060] In some aspects of the disclosed subject matter, processor 404 can include a discontinuous reception (DRX) override determination circuit 440, which is configured for various functions including, for example, determining whether DRX override is authorized for a particular UE and / or determining the DRX cycle to be used for a particular UE. For example, DRX override determination circuit 440 can be configured to implement one or more of the functions described below in conjunction with Figure 9 the functions described in 906 to 912. Additionally, in some aspects, processor 404 can include a paging circuit 442, which is configured for various functions including, for example, sending a paging message intended for a particular UE. For example, paging circuit 442 can be configured to implement one or more of the functions described below in conjunction with Figure 9One or more of the described functions, such as those described in 910 and 912. Additionally, in some aspects, the processor 404 may include a system information broadcast circuit 444, which is configured for various functions (including, for example, broadcasting system information blocks (SIBs)), and the SIB may include information related to the default paging cycle of the serving cell and an indication of whether default DRX override is supported, etc. For example, the system information broadcast circuit 444 may be configured to implement one or more of the functions described below in conjunction with Figure 9 One or more of the described functions, such as those described in 902.

[0061] The processor 404 may manage the bus 402 and may perform general processing, including executing software stored on the computer-readable medium 406, which, when executed by the processor 404, causes the processing system 414 to perform the various functions described below for any particular device (e.g., in conjunction with Figures 7 - 10 ). In some aspects, the computer-readable medium 406 and the memory 405 may also be used to store data manipulated by the processor 404 when executing the software.

[0062] In one or more examples, the computer-readable storage medium 406 may include discontinuous reception (DRX) override determination software 452, which is configured for various functions (including, for example, determining whether DRX override is authorized for a particular UE and / or determining the DRX cycle to be used for a particular UE). For example, the DRX override determination software 452 may be configured to implement one or more of the functions described below in conjunction with Figure 9 One or more of the described functions, such as those described in conjunction with 906 to 912. Additionally, in some aspects, the computer-readable storage medium 406 may include paging software 454, which is configured for various functions (including, for example, sending paging messages intended for a particular UE). For example, the paging software 454 may be configured to implement one or more of the functions described below in conjunction with Figure 9 One or more of the described functions, such as those described in 910 and 912. Additionally, in some aspects, the computer-readable storage medium 406 may include system information broadcast software 456, which is configured for various functions (including, for example, broadcasting system information blocks (SIBs)), and the SIB may include information related to the default paging cycle of the serving cell and an indication of whether default DRX override is supported, etc. For example, the system information broadcast software 456 may be configured to implement one or more of the functions described below in conjunction with Figure 9 One or more of the described functions, such as those described in 902.

[0063] One or more processors 404 in the processing system may execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, processes, functions, etc. The software may be located on a computer-readable medium 406. The computer-readable medium 406 may be a non-transitory computer-readable medium. By way of example, non-transitory computer-readable media include magnetic storage devices (e.g., hard disks, floppy disks, magnetic tape), optical disks (e.g., compact disc (CD) or digital versatile disc (DVD)), smart cards, flash memory devices (e.g., cards, sticks, or key drives), random access memory (RAM), read only memory (ROM), programmable ROM (PROM), erasable PROM (EPROM), electrically erasable PROM (EEPROM), registers, removable disks, and any other suitable medium for storing software and / or instructions that can be accessed and read by a computer. The computer-readable medium 406 may be located within the processing system 414, outside the processing system 414, or distributed among multiple entities including the processing system 414. The computer-readable medium 406 may be embodied in a computer program product. By way of example, a computer program product may include a computer-readable medium with packaging material. Those skilled in the art will recognize how best to implement the described functionality throughout the present disclosure in accordance with a particular application and the overall design constraints imposed on the overall system.

[0064] In one or more examples, the computer-readable storage medium 406 may include DL scheduling software 1052, which is configured for various functions (including, for example, scheduling the start time of downlink transmissions with various time slots and the time length of data transmissions (e.g., using SLIV) to a scheduled entity (e.g., UE)). For example, the DL scheduling software 1052 may be configured to implement one or more of the functions described above with respect to Figure 9 the functions described, such as the functions described in connection with 908 and / or 912. Additionally, in some aspects, the computer-readable storage medium 1006 may include DI calculation software 1054, which is configured for various functions (including, for example, determining the symbol-based time length of additional DL interrupts required for a particular UE to perform an uplink transmission handover on a given frequency band associated with the scheduling entity 1000). For example, the DI calculation software 1054 may be configured to implement one or more of the functions described above in connection with Figure 9 the functions described, such as the functions described in connection with 912.

[0065] Figure 5 is a block diagram conceptually showing an example of a hardware implementation for a scheduled entity 500 according to some aspects of the disclosed subject matter and is described as a non - limiting illustrative example. For example, the scheduled entity 500 can be a user equipment (UE) as shown in any one or more of the diagrams in Figure 1 and / or Figure 2 According to some aspects of the present disclosure, an element, or any part of an element, or any combination of elements can be implemented using a processing system 514 that includes one or more processors 504.

[0066] In some aspects, the processing system 514 can be substantially the same as the processing system 414 shown in Figure 4 including a bus interface 508, a bus 502, a memory 505, a processor 504, and a computer - readable medium 506. Additionally, the scheduled entity 500 can include a user interface 512 and a transceiver 510, which are substantially similar to the user interface and transceiver described above in Figure 4 That is, the processor 504 as utilized in the scheduled entity 500 can be used to implement any one or more of the processes described below in connection with Figures 7 - 10 In some aspects of the present disclosure, the processor 504 can include a DRX registration circuit 540, which is configured for various functions (including, for example, requesting a DRX cycle from the AMF and determining the DRX cycle assigned to the UE by the AMF). For example, the DRX registration circuit 540 can be configured to implement one or more of the functions described below in connection with

[0067] For example, functions such as those described in connection with 804 and / or 806. Additionally, in some aspects, the processor 504 can include a DRX calculation circuit 542, which is configured for various functions (including, for example, determining the DRX cycle to be used with a particular base station). For example, the DRX calculation circuit 542 can be configured to implement one or more of the functions described below in connection with Figure 8 For example, functions such as those described in connection with 808 to 814. Additionally, in some aspects, the processor 504 can include a transceiver power control circuit 544, which is configured for various functions (including, for example, controlling the power state of the transceiver 510 between at least a low - power state (e.g., off state) and a higher - power state (e.g., on state)). For example, the transceiver power control circuit 544 can be configured to implement one or more of the functions described below in connection with Figure 8 In some aspects, the processor 504 can include a transceiver power control circuit 544, which is configured for various functions (including, for example, controlling the power state of the transceiver 510 between at least a low - power state (e.g., off state) and a higher - power state (e.g., on state)). For example, the transceiver power control circuit 544 can be configured to implement one or more of the functions described below in connection with Figure 8One or more of the described functions, such as the functions described in connection with 816. In a more specific example, the transceiver power control circuit 542 may be configured to control the operating state of the transceiver 510 when the UE is in the RRC_INACTIVE or RRC_IDLE state.

[0068] In one or more examples, the computer-readable storage medium 506 may include DRX registration software 552, which is configured for various functions (including, for example, requesting a DRX cycle from the AMF). For example, the DRX registration software 552 may be configured to implement one or more of the functions described below in connection with Figure 8 One or more of the described functions, such as the functions described in connection with 804 and / or 806. Additionally, in some aspects, the computer-readable storage medium 506 may include a DRX calculation circuit 554, which is configured for various functions (including, for example, determining a DRX cycle to use with a particular base station). For example, the DRX calculation circuit 554 may be configured to implement one or more of the functions described below in connection with Figure 8 One or more of the described functions, such as the functions described in connection with 808 to 816. Additionally, in some aspects, the computer-readable storage medium 506 may include transceiver power control software 556, which is configured for various functions (including, for example, controlling the power state of the transceiver 510 between at least a low power state (e.g., off state) and a higher power state (e.g., on state)). For example, the transceiver power control software 556 may be configured to implement one or more of the functions described below in connection with Figure 8 One or more of the described functions, such as the functions described in connection with 816. In a more specific example, the transceiver power control software 556 may be configured to control the operating state of the transceiver 510 when the UE is in the RRC_INACTIVE or RRC_IDLE state.

[0069] Figure 6 is a block diagram conceptually showing an example of a hardware implementation for an access and mobility management function node (AMF) 600 in accordance with some aspects of the disclosed subject matter and is described as a non-limiting illustrative example. For example, the AMF 600 may be a component of the core network shown in Figure 1 According to some aspects of the present disclosure, an element, or any part of an element, or any combination of elements may be implemented using a processing system 614 that includes one or more processors 604.

[0070] In some aspects, the processing system 614 may be associated with the one shown in Figure 4The processing system 414 shown is substantially the same and includes a bus interface 608, a bus 602, a memory 605, a processor 604, and a computer-readable medium 606. Additionally, the scheduled entity 600 may include a user interface 612 and a network interface 616, which are substantially similar to the user interface and network interface described above in Figure 4 That is, the processor 604 utilized in the AMF 600 can be used to implement any one or more of the processes described below in connection with Figures 7 - 10 For example, the network interface 616 can be used to establish an N2 interface that can be used to communicate with one or more parts of the RAN (e.g., for communication with a base station such as base station 108, base station 210, etc.).

[0071] In some aspects of the present disclosure, the processor 604 may include a DRX assignment circuit 640, which is configured for various functions (including, for example, assigning a DRX cycle for a UE in an inactive state or an idle state and determining whether to allow the UE to override the base station default paging cycle). For example, the DRX assignment circuit 640 can be configured to implement one or more of the functions described below in connection with Figure 10 For example, the functions described in connection with 1002 to 1010. Additionally, in some aspects, the processor 604 may include a paging circuit 642, which is configured for various functions (including, for example, sending a paging message to a base station when new data requiring paging of the UE is received), the paging message including the DRX cycle for the UE and an indication as to whether the UE is authorized to override the default base station paging cycle. For example, the paging circuit 642 can be configured to implement one or more of the functions described below in connection with Figure 10 For example, the functions described in connection with 1016 to 1020.

[0072] In one or more examples, the computer-readable storage medium 606 may include DRX assignment software 652, which is configured for various functions (including, for example, assigning a DRX cycle for a UE in an inactive state or an idle state and determining whether to allow the UE to override the base station default paging cycle). For example, the DRX assignment software 652 can be configured to implement the functions described below with respect to Figure 10One or more of the described functions, such as those described in connection with 1002 to 1010. Additionally, in some aspects, the computer-readable storage medium 606 may include paging software 654 configured for various functions (including, for example, sending a paging message to a base station when new data requiring paging of the UE is received), the paging message including a DRX cycle for the UE and an indication as to whether the UE is authorized to override the default base station paging cycle. For example, the paging software 652 may be configured to implement one or more of the functions described below in connection with Figure 10 One or more of the described functions, such as those described in connection with 1016 to 1020.

[0073] Figure 7 FIG. is a signaling diagram showing exemplary signaling between a core network 702, a scheduling entity 704, and a scheduled entity 706 within a wireless communication system 700 for scheduling a discontinuous reception (DRX) cycle for the scheduled entity, and is described as a non-limiting illustrative example. In some aspects, the wireless communication system 700 may correspond to, for example, the wireless communication system 100 described above in connection with Figure 1 and shown in Figure 1 In some aspects, the core network (CN) 702 may correspond to, for example, the core network 102, the AMF, and / or any other suitable component of the core network. In some aspects, the scheduling entity 704 may correspond to, for example, the base station (e.g., gNB or eNB) or other scheduling entity described above in connection with Figure 1 and / or Figure 2 In some aspects, the scheduled entity 706 may correspond to, for example, the UE or other scheduled node described above in connection with Figure 1 and / or Figure 2

[0074] ​At 708, when the scheduled entity 706 enters a new registration area, the scheduled entity 708 may perform a registration process. In some aspects, the registration process 708 may involve the scheduled entity 706 sending a registration request message to the CN 702 at 710. In some aspects, the registration request message may include any suitable information that the CN 702 can use to determine whether to accept the registration of the scheduled entity 706. Additionally, in some aspects, the scheduled entity 706 may include a requested discontinuous reception (DRX) cycle in the registration request message, and / or may include a request to override the default DRX cycle for the overriding scheduling entity (e.g., scheduling entity 704), which request may sometimes be referred to as a default DRX override request. In some aspects, the requested DRX cycle and / or the default DRX override request may be formatted in any suitable format. For example, the requested DRX cycle may be formatted as an integer representing a time interval (e.g., in milliseconds, frames, subframes, time slots, symbols, etc.) or a decimal number representing a time interval (e.g., in seconds). As another example, the requested DRX cycle may be formatted as an integer representing a multiplier for determining the DRX cycle by multiplying a base value by the multiplier. As yet another example, the default DRX override request may be formatted as a binary flag (e.g., 0 indicates that no request for default DRX override is being submitted, while 1 indicates that a default DRX override request is being submitted). As another example, the default DRX override request may be inferred based on the duration of the requested DRX cycle (e.g., a DRX that exceeds a threshold corresponding to the default RAN paging cycle may infer that a request for default DRX override is being submitted).

[0075] In some aspects, the registration process 708 may involve the CN 702 sending a registration acceptance message to the scheduled entity 706 at 712. In some aspects, the registration acceptance message may include the accepted DRX cycle that has been assigned to the scheduled entity 706 and an indication of whether the default DRX override request is accepted. In some aspects, the accepted DRX cycle may be the same as the requested DRX cycle, or may be different from the requested DRX cycle (e.g., longer or shorter). For example, in some aspects, if the default DRX override request is not accepted, the CN 702 may assign a DRX cycle that is no longer in duration than the default paging cycle as the accepted DRX cycle. As another example, in some aspects, the CN 702 may assign a DRX cycle that is slightly longer or shorter than the requested DRX cycle for various reasons (such as the availability of time slots corresponding to the requested DRX cycle) based on the subscription of the scheduled entity, local configuration, latency requirements for the public alert system, etc. In some aspects, the accepted DRX cycle and / or the default DRX override request may be formatted in any suitable format. For example, the accepted DRX cycle may be formatted as an integer representing a time interval (e.g., in milliseconds, frames, subframes, time slots, symbols, etc.), or a decimal number representing a time interval (e.g., in seconds). As yet another example, the default DRX override acceptance may be formatted as a binary flag (e.g., 0 indicates that the request for the default DRX override is not accepted, while 1 indicates that the default DRX override request is accepted). As another example, the acceptance of the default DRX override request may be inferred based on the duration of the accepted DRX cycle (e.g., a DRX that exceeds a threshold corresponding to the default RAN paging cycle may infer the acceptance of the request for the default DRX override).

[0076] At 714, a scheduling entity (e.g., scheduler 704 or another scheduling entity) triggers a handover and selects a new serving cell for the scheduled entity 706 (e.g., associated with the scheduling entity 704). The scheduled entity 706 may determine whether to use the accepted DRX cycle received from the CN 702 or the default paging cycle associated with the selected serving cell. It should be noted that this is only an example, and other components of the network may select a cell for the scheduled entity 706 and / or may trigger a connection to a new cell. For example, the scheduled entity 706 in the RRC_IDLE state may select a cell.

[0077] At 716, the scheduling entity 704 may send a System Information Block (SIB) that includes information related to the default paging cycle of the serving cell and an indication of whether default DRX override is supported. In some aspects, the scheduling entity 704 may send a default_Paging_Cycle value (e.g., as an integer, as a floating point number, etc.) and a default DRX override support value (e.g., as binary, where 0 corresponds to false and 1 corresponds to true). In some aspects, the SIB may be SIB1.

[0078] In some aspects, the scheduling entity 704 may broadcast the maximum DRX cycle supported by the scheduling entity 704. For example, the scheduling entity 704 may use a system information modification period to notify the scheduled entities that at least a portion of the system information is being modified. In such an example, if the scheduling entity 704 is modifying its system information (e.g., the information included in SIB1), the scheduling entity 704 may provide a notification of the upcoming change in the system information (e.g., via Downlink Control Information (DCI), such as a short message included in DCI transmitted on the Physical Downlink Control Channel (PDCCH)) during the system information modification period prior to the change in the system information. When the system information modification period during which the notification is sent has elapsed, the scheduling entity 704 may begin including the modified system information in one or more system information blocks (e.g., SIB1). In some aspects, the scheduling entity 704 may broadcast the maximum DRX cycle supported by the scheduling entity 704, which may be shorter than or equal to the system information modification period. Thus, the UE served by the scheduling entity 704 wakes up at least once during each system information modification period. In some aspects, the scheduling entity 704 may provide information indicating the boundaries of the system information modification period in the system information (e.g., in SIB1). In some aspects, the information indicating the boundaries of the system information modification period may define the length of the system information modification period in a radio frame.

[0079] In some aspects, in addition to or instead of the default DRX override support value, the scheduling entity 704 may also broadcast a maximum DRX cycle. For example, in addition to or instead of the default DRX override support value, the scheduling entity 704 may also broadcast a maximum DRX cycle. In a more specific example, if the scheduling entity 704 supports default DRX override, the scheduling entity 704 may broadcast the supported maximum DRX cycle. In such an example, if the UE receives a SIB (e.g., SIB1) that includes a maximum DRX cycle value, the UE may determine that default DRX override is supported. Otherwise, if the UE receives a SIB (e.g., SIB1) that does not include a maximum DRX cycle value, the UE may determine that default DRX override is not supported. Alternatively, the omission of the maximum DRX cycle may not indicate the non - support of default DRX override. For example, in some aspects, the scheduling entity 704 and / or the UE served by the scheduling entity 704 may infer the maximum DRX cycle supported by the scheduling entity 704 based on other system information broadcast by the scheduling entity 704. In such an example, the scheduling entity 704 and / or the UE served by the scheduling entity 704 may use the system information modification period duration to determine the maximum DRX cycle supported by the scheduling entity 704.

[0080] At 718, the scheduled entity 706 may use the accepted DRX cycle received in the registration acceptance message from the CN 702 based on the SIB received from the scheduling entity 704 indicating support for default DRX override.

[0081] In some aspects, the CN 702 may receive and / or generate new data 720 that needs to be transmitted to the scheduled entity 706, and at 722, the CN 702 may notify the scheduling entity 704 of the new data 720 (e.g., using an N2 paging message). In some aspects, the CN 702 may include information related to the DRX cycle assigned to the scheduled entity 706 with the new data 720 (e.g., by including the DRX cycle in the paging message). Additionally, in some aspects, the CN 702 may include an indication regarding the approval of default DRX override for the scheduled entity associated with the new data 720.

[0082] At 724, the scheduling entity 704 may send a paging message for the scheduled entity 706 at the paging frame and paging occasion based on the accepted DRX cycle in response to the paging message received from the CN 702.

[0083] At 726, a scheduling entity (e.g., scheduler 704 or another scheduling entity) triggers a handover and selects a new serving cell for the scheduled entity 706 (e.g., associated with the second scheduling entity 704-2) (e.g., due to a handover decision). The scheduled entity 706 may determine whether to use the accepted DRX cycle received from the CN 702 or the default paging cycle associated with the selected serving cell. As described above in connection with 714, this is merely an example, and other components of the network may select the cell for the scheduled entity 706 and / or may trigger a connection to a new cell. For example, the scheduled entity 706 in the RRC_IDLE state may select a cell.

[0084] At 728, the scheduling entity 704-2 may send an SIB (e.g., SIB1), which includes information related to the default paging cycle of the serving cell and an indication of non-support for default DRX override. In some aspects, the scheduling entity 704-2 may send a default_Paging_Cycle value (e.g., as an integer, as a floating point number, etc.), and may send a default DRX override support value (e.g., as binary, where 0 corresponds to false) or may omit the default DRX override support value indicating non-support for default DRX override. Alternatively, as described above in connection with 716, the omission of the maximum DRX cycle value by the scheduling entity 704-2 in the SIB broadcast may indicate non-support for default DRX override.

[0085] At 730, the scheduled entity 706 may use the shorter of the accepted DRX cycle and the default paging cycle received in the registration acceptance from the CN 702 based on the SIB received from the scheduling entity 704-2 indicating non-support for default DRX override.

[0086] In some aspects, the CN 702 may receive and / or generate new data 732 for the scheduled entity 706, and at 734, the CN 702 may notify the scheduling entity 704-2 of the new data 732 (e.g., using an N2 paging message). In some aspects, the CN 702 may include information related to the DRX cycle assigned to the scheduled entity 706 together with the new data 732 (e.g., by including the DRX cycle in the paging message). Additionally, in some aspects, the CN 702 may include an indication of approval for default DRX override for the scheduled entity associated with the new data 732.

[0087] At 736, the scheduling entity 704-2 may send a paging message for the scheduled entity 706 at a paging frame and paging occasion that is based on the shorter of the accepted DRX cycle and the default paging cycle received in the registration acceptance from the CN 702.

[0088] Figure 8 is a flowchart showing an exemplary process 800 for a scheduled entity to determine a discontinuous reception cycle to be utilized with a scheduling entity in a registration area according to some aspects of the disclosed subject matter, and is described as a non-limiting illustrative example. As described below, in certain implementations within the scope of the disclosed subject matter, some or all of the illustrated features may be omitted, and some of the illustrated features may not be required for the implementation of all embodiments. In some examples, process 800 may be performed (e.g., run) by the user equipment described above in connection with Figure 5 and / or the UE 106 described above in connection with Figure 1 In some examples, process 800 may be performed by any suitable device or unit for performing the functions or algorithms described below.

[0089] At 802, the UE may enter a new registration area in which the UE is required to register with the core network. In some aspects, the UE may enter a new registration area for various reasons, such as when moving between the coverage areas of different base stations, or when transitioning from a state in which connection is prohibited (e.g., a power-off state, a state in which the transmitter is powered off). The registration area may be defined by the network and may generally correspond to contiguous geographical areas, such as a large urban area, a county, etc. In some aspects, the UE may use any suitable technique or combination of techniques to determine that it has entered a new registration area. For example, the UE may receive a message including information indicating that a scheduling entity (e.g., base station 108, base station 210) is within a particular registration area. In a more specific example, the UE may receive a message explicitly indicating that it has entered a new registration area.

[0090] At 804, the UE may submit a registration request message (which may be a registration request message defined according to one or more 5G standards, such as 3GPP Technical Specification 23.501) to the core network (e.g., to the AMF), the registration request message including a request for a discontinuous reception (DRX) cycle that is longer than the default base station (BS) paging cycle. Additionally, in some aspects, the registration request message may include an explicit request to override the default DRX of the base station. For example, as described above in connection with Figure 7As described in 710, the UE may send a registration request message to the AMF. The registration request message includes the requested DRX cycle (in any suitable format) and, in some aspects, includes a default DRX override request. In some aspects, the UE may use the N1 interface to send such a request, which may be transmitted via the base station. In some aspects, the UE may use a transceiver (e.g., transceiver 510) to send the registration request message to send the request via any suitable communication network (e.g., via the RAN (such as RAN 104 or RAN 200), using one or more UL time slots, etc.) and / or any suitable channel (e.g., via the channel carrying the RRC message). In some aspects, the UE may use any suitable communication interface (such as transceiver 510) to send the registration request message.

[0091] At 806, the UE may receive a registration acceptance message (which may be a registration acceptance message defined according to one or more 5G standards, such as 3GPP Technical Specification 23.501). The registration acceptance message includes the accepted DRX cycle assigned to the UE by the core network (e.g., by the AMF). Additionally, in some aspects, the registration acceptance message may include an explicit indication that the override of the default DRX for the base station has been accepted. For example, as described above in connection with Figure 7 712, the UE may receive a registration acceptance message from the AMF. The registration acceptance message includes the accepted DRX cycle (in any suitable format) and, in some aspects, includes a default DRX override acceptance (if such a request has been accepted). In some aspects, such a message may be sent using the N1 interface and may be transmitted via the base station. In some aspects, the UE may receive the registration message by sampling and buffering the received radio signal on a specific channel and applying appropriate processing (such as energy detection, demodulation, decoding, etc.) to the buffered signal. In some aspects, the UE may use any suitable communication interface (such as a transceiver (e.g., transceiver 510)) to receive the registration acceptance message.

[0092] In some aspects, the accepted DRX cycle may be the same as, or different from, the requested DRX cycle. For example, as described above in connection with Figure 7 712, the accepted DRX may be longer or shorter than the accepted DRX and may exceed or may not exceed the default paging cycle used by many base stations. In some aspects, the accepted DRX cycle may exceed the default paging cycle used by many base stations, but the AMF may indicate that the default DRX override request is rejected. As described below, in such a case, the UE may use the default paging cycle for most base stations and may use the accepted DRX cycle for any base station with an unusually long default paging cycle.

[0093] At 808, the UE may receive a System Information Block (SIB) from the BS. The SIB includes a default paging cycle associated with the base station and an indication of whether the base station supports a DRX override feature for the default paging cycle (e.g., to use an accepted DRX cycle assigned to the UE that is longer than the default paging cycle). In some aspects, the UE may receive the SIB by: sampling and buffering a wireless signal received on a specific channel (e.g., via the Physical Downlink Shared Channel (PDSCH), Downlink Shared Channel (DL-SCH), and / or Broadcast Control Channel (BCCH)), and applying appropriate processing (such as energy detection, demodulation, decoding, etc.) to the buffered signal. In some aspects, the UE may use any suitable communication interface (such as a transceiver (e.g., transceiver 510)) to receive a registration acceptance message.

[0094] In some aspects, the presence of a specific default DRX override support value (e.g., binary 1) in the SIB may be an indication that the base station supports the DRX override feature for the default paging cycle. Additionally or alternatively, the presence of a (non-zero) maximum DRX cycle value in the SIB may be an indication that the base station supports the DRX override feature for the default paging cycle. Similarly, in some aspects, the presence of a specific default DRX override support value (e.g., binary 0) in the SIB and / or the presence of a zero maximum DRX cycle value in the SIB may be an indication that the base station does not support the DRX override feature for the default paging cycle. Alternatively, in some aspects, the absence of a default DRX override support value and the absence of any maximum DRX cycle value in the SIB may be an indication that the base station does not support the DRX override feature for the default paging cycle.

[0095] In some aspects, the UE may use any suitable technique or combination of techniques to determine whether the BS supports DRX override. For example, the UE may determine whether the BS supports DRX override based on whether the SIB received at 808 includes an indication that the base station supports the DRX override feature. In a more specific example, the UE may determine whether a bit in the SIB that indicates support or non-support for the DRX override feature is present or absent, and if present, determine whether the bit is true (e.g., binary 1) or false (e.g., binary 0). As described above, in such an example, if the bit in the SIB that indicates support or non-support for the DRX override feature is present and is true, the UE may determine that the base station supports the DRX override feature. Otherwise, if the bit is absent, or the bit is present and is false, the UE may determine that the base station does not support the DRX override feature.

[0096] As another more specific example, the UE may determine whether the BS supports DRX override based on whether a field in the SIB indicating the maximum DRX cycle supported by the base station is present or not. In such an example, if the field in the SIB indicating the maximum DRX cycle supported by the base station is present, the UE may determine that the base station supports the DRX override feature. Otherwise, if the field in the SIB indicating the maximum DRX cycle supported by the base station is not present, or if the value is zero, the UE may determine that the base station does not support the DRX override feature.

[0097] As another example, the UE may determine whether the BS supports DRX override based on whether a field in the SIB indicating the maximum DRX cycle supported by the base station is present or not and if present whether the value is non-zero. In such an example, if the field in the SIB indicating the maximum DRX cycle supported by the base station is present and non-zero, the UE may determine that the base station supports the DRX override feature. Otherwise, if the field in the SIB indicating the maximum DRX cycle supported by the base station is not present, or if the value is zero, the UE may determine that the base station does not support the DRX override feature.

[0098] At 810, if the UE determines that the BS supports DRX override (Yes at 810), the process 800 may move to 812. At 812, when the UE is connected to the BS, the UE may determine that the DRX cycle assigned by the core network (i.e., the accepted DRX included in the registration acceptance message received at 806) will be used to determine the paging interval (e.g., determine the paging frame and / or paging occasion for the UE), unless the base station limits the length of the DRX cycle to a shorter duration.

[0099] In some aspects, the UE can determine whether the maximum DRX cycle supported by the base station is restricted to a duration shorter than the DRX cycle assigned by the core network, and if so, can use the maximum DRX cycle supported by the base station (e.g., instead of the core network-assigned DRX cycle that is longer than the maximum DRX cycle supported by the base station). In some aspects, the UE can use any suitable information and / or any suitable technique to determine the maximum DRX cycle supported by the base station. For example, the SIB received from the base station can include an explicit indication of the maximum DRX cycle supported by the base station (e.g., in the maximum DRX cycle field). In such an example, the UE can compare the length of the maximum DRX cycle with the core network-assigned DRX cycle to determine which is shorter, and can use the shorter of the two DRX cycle durations. As another example, the SIB received from the base station can include an indication of the length of the system information modification period associated with the base station, and the explicit indication of the maximum DRX cycle supported by the base station can be omitted or may not be omitted. In such an example, the UE can compare the length of the system information modification period with the core network-assigned DRX cycle to determine which is shorter, and can use the shorter of the core network-assigned DRX cycle and a value based on the system information modification period (e.g., a value not greater than the system information modification time).

[0100] Otherwise, if the UE determines that the BS does not support DRX override ( "No" at 810), the process 800 can move to 814. At 814, when the UE is connected to the BS, the UE can determine that the shorter of the core network-assigned DRX cycle and the default paging cycle will be used to determine the paging interval (e.g., determine the paging frame and / or paging occasion of the UE).

[0101] At 816, the UE can wake up at a specific time (e.g., a specific paging frame and / or paging occasion) based on the paging interval selected at 812 or 814 to determine whether the base station (or another base station in the RAN notification area (RNA) where the UE is located) has sent a paging message. In some embodiments, the UE can use any suitable technique or combination of techniques to control the power of the transceiver to switch between a low-power state and a higher-power state. For example, the UE can control the state of the switch that connects the power source (e.g., the battery) to the transceiver between a closed state and an open state, where power is available to the transceiver in the closed state and power transmission to the transceiver is prohibited in the open state.

[0102] At 818, the UE may determine whether a handover to a new BS has been initiated. If the UE determines that a handover to a new BS (e.g., a new serving cell) has not been initiated ( "No" at 818), the process 800 may return to 816. Otherwise, if the UE determines that a handover to a new BS (e.g., a new serving cell) has been initiated ( "Yes" at 818), the process 800 may move to 820. It should be noted that the handover may be initiated for any suitable reason, such as due to the mobility of the UE between cells, due to load balancing by the network, etc. In some embodiments, the UE may use any suitable technique or combination of techniques to determine that a handover has been initiated. For example, the UE may receive a message from the RAN that includes an indication of a handover to a new BS and / or information that can be used to establish a connection with the new BS.

[0103] At 820, the UE may determine whether the UE has moved to a new registration area. If the UE has not moved to a new registration area ( "No" at 820), the process 800 may return to 808 to receive the SIB from the new BS. Otherwise, if the UE determines that it has moved to a new registration area ( "Yes"), the process 800 may end (e.g., a new instance of the process 800 may start). In some aspects, the UE may need to transition to the connected state (sometimes referred to as RRC_CONNECTED) when entering a new registration area in order to send a registration request. Alternatively, in some aspects, in a compatible network, the registration request may be sent while in the inactive state. In some aspects, the UE may use any suitable technique or combination of techniques (such as the techniques described above in connection with 802) to determine that it has entered a new registration area.

[0104] Figure 9 FIG. is a flowchart showing an exemplary process for a scheduling entity to determine a discontinuous reception cycle to be used for sending a paging message intended for a specific scheduled entity according to some aspects of the disclosed subject matter, and is described as a non-limiting illustrative example. As described below, in a particular implementation within the scope of the disclosed subject matter, some or all of the illustrated features may be omitted, and some of the illustrated features may not be required for the implementation of all embodiments. In some examples, the process 900 may be performed (e.g., run) by the base station described above in connection with Figure 4 and / or the base station 108 described above in connection with Figure 1 described. In some examples, the process 900 may be performed by any suitable device or unit for performing the functions or algorithms described below.

[0105] At 902, the base station may broadcast a System Information Block (SIB), which includes information related to the default paging cycle of the serving cell and an indication of whether default DRX override is supported. In some aspects, the SIB may be SIB1. It should be noted that a legacy base station that does not support default DRX override may not include an indication of not supporting default DRX override (e.g., because the base station is not configured with such an ability). Alternatively, in some examples, the base station may support default DRX override during some periods, while being unable to support default DRX override during other periods (e.g., periods during which the base station is experiencing high utilization). In some aspects, the base station may use any suitable technique or combination of techniques to broadcast the SIB. For example, the base station may use any suitable communication network (e.g., via a RAN (such as RAN 104 or RAN 200), using one or more DL time slots, etc.) to send the SIB. As another example, the base station may use any suitable one or more communication channels (e.g., Physical Downlink Shared Channel (PDSCH), Downlink Shared Channel (DL-SCH), and / or Broadcast Control Channel (BCCH)). In some aspects, the base station may use any suitable communication interface (such as a transceiver (e.g., transceiver 410)) to receive paging messages.

[0106] At 904, the base station may receive identification information of a User Equipment (UE) connected to the base station (e.g., when the base station is selected as a new serving cell, as described above in conjunction with Figure 7 714). In some aspects, the base station may receive the identification information from any suitable source (such as the UE, an AMF that manages handovers from a previous base station (and / or another core network component), or an AMF (and / or another core network component that sends a paging message intended for the UE)). For example, before the base station receives a paging message intended for the UE, the UE may not be connected to the base station (e.g., as described below in conjunction with 906). In some aspects, the identification information may be included in the context associated with the UE provided to the BS. In some aspects, the base station may use any suitable communication interface (such as the N2 interface (e.g., via network interface 416) and / or a transceiver (e.g., transceiver 410)) to receive the identification information of the UE.

[0107] At 906, the base station may receive a paging message from the core network (e.g., from the AMF), which includes data for the UE, an indication of the DRX cycle assigned to the UE, and an indication of whether default DRX override is approved for the UE. As described above in conjunction with Figure 7As described in 722, the DRX cycle and / or DRX override can be formatted in any suitable format. In some aspects, the base station can use any suitable communication interface (such as the N2 interface (e.g., via network interface 416) and / or transceiver (e.g., transceiver 410)) to receive paging messages.

[0108] At 908, the base station can determine whether the DRX cycle received at 906 is longer than the base station's default paging cycle. In some aspects, the base station can also determine whether default DRX override is approved for the UE. If the base station determines that the DRX cycle for the UE is longer than the base station's default paging cycle (and in some aspects, the default DRX override has been explicitly authorized) (yes at 908), then process 900 can move to 910. In some aspects, the base station can use any suitable technique or combination of techniques to determine whether the DRX cycle received at 906 is longer than the default paging cycle. For example, the base station can compare the two values to determine whether the DRX cycle received at 906 is longer than the default paging cycle.

[0109] At 910, if the DRX cycle assigned by the core network is permissible, the base station can use the DRX cycle assigned by the core network to the UE (i.e., the DRX cycle received in the paging message) to determine the timing (e.g., paging frame and / or paging occasion) for transmitting the paging message for the UE. In some aspects, the base station can determine whether the DRX cycle assigned by the core network is permissible based on the maximum DRX cycle supported by the base station. If the DRX cycle assigned by the core network is longer than the maximum DRX cycle supported by the base station, the base station can use the maximum DRX cycle supported by the base station to page the UE (e.g., instead of the DRX cycle assigned by the core network (which is longer than the maximum DRX cycle supported by the base station)). In some aspects, the base station can use any suitable information and / or any suitable technique to determine the maximum DRX cycle supported by the base station. For example, the base station can include an explicit indication of the maximum DRX cycle supported by the base station in the SIB. In a specific example, the base station can calculate the maximum DRX cycle supported by the base station (e.g., based on the system information modification period associated with the base station), and can include a value based on the calculated maximum DRX cycle in the SIB. Additionally or alternatively, the base station can receive the value of the maximum DRX cycle supported by the base station from another node (e.g., from a core network component), and can include the received value in the SIB. In such an example, the base station can compare the length of the maximum DRX cycle with the DRX cycle assigned by the core network to determine which is shorter, and can use the shorter of the two DRX cycle durations to page the UE.

[0110] As another example, the base station may include in the SIB an indication of the length of the system information modification period associated with the base station, and may omit or may not omit an explicit indication of the maximum DRX cycle supported by the base station. In such an example, the base station may compare the length of the system information modification period with the DRX cycle assigned by the core network to determine which is shorter, and may use the shorter of the DRX cycle assigned by the core network and a value based on the system information modification period (e.g., a value not greater than the system information modification period) to page the UE.

[0111] Otherwise, if the base station determines that the DRX cycle for the UE is less than or equal to the base station's default paging cycle (or, in some aspects, the default DRX override has not been explicitly authorized) (at 908, "No"), then process 900 may proceed to 912.

[0112] At 912, the base station may use the shorter of the DRX cycle assigned by the core network and the default paging cycle to determine the timing (e.g., paging frame and / or paging occasion) for transmitting a paging message for the UE. In some aspects, the base station may use any suitable technique or combination of techniques to transmit a paging message intended for the UE at 910 or 912. For example, the base station may use any suitable communication network (e.g., via a RAN (such as RAN 104 or RAN 200), using one or more DL time slots, etc.) to transmit the paging message as an RRC SIB. As another example, the base station may use any suitable one or more communication channels (e.g., Physical Downlink Shared Channel (PDSCH), Paging Channel (PCH), and / or Paging Control Channel (PCCH)). In some aspects, the base station may use any suitable communication interface (such as a transceiver (e.g., transceiver 410)) to transmit a paging message intended for the UE.

[0113] At 914, if the UE is still within the area served by the base station ("yes" at 914), the process 900 can return to 906, and the base station can receive another paging message from the core network. Otherwise, if the UE has left the area served by the base station (e.g., due to handover, mobility outside the RAN notification area, or for any other reason) ("no" at 914), the process 900 can end. It should be noted that regardless of whether the UE is within the area served by the base station, the base station continues to broadcast the SIB periodically at 902. However, to avoid making the figure too complex, this is not shown. In some aspects, the base station can use any suitable technique or combination of techniques to determine whether the UE has left the area served by the base station. For example, the base station can receive a notification indicating that the UE has left the RAN notification area (e.g., a message from the AMF indicating that the context associated with the UE will be released) from the access and mobility management function node (AMF). As another example, the base station can determine that the UE has left the area served by the base station based on the elapse of a predetermined time. In some aspects, 914 can be omitted (e.g., if the base station is located within the RAN notification area associated with the UE but does not have the UE context).

[0114] Figure 10 is a flowchart showing an exemplary process for an access and mobility management function node to select a discontinuous reception cycle for a specific scheduled entity and override the default discontinuous reception cycle of the scheduled entity in the registration area, and is described as a non - limiting illustrative example. As described below, in a particular implementation within the scope of the disclosed subject matter, some or all of the shown features can be omitted, and some of the shown features may not be required for the implementation of all embodiments. In some examples, the process 1000 can be performed (e.g., run) by the access and mobility management function node (AMF) described above in connection with Figure 6 and / or components of the core network 102 described above in connection with Figure 1 In some examples, the process 1000 can be performed by any suitable device or unit for performing the functions or algorithms described below.

[0115] At 1002, the AMF can receive a registration request message from a UE that is establishing a connection within a new registration area (which can be a registration request message defined according to one or more 5G standards such as 3GPP Technical Specification 23.501), and the registration request message includes a request for a discontinuous reception (DRX) cycle that is longer than the default base station (BS) paging cycle. Additionally, in some aspects, the registration request message can include an explicit request to override the default DRX cycle of the base station. For example, as described above in connection with Figure 7As described in 710, the registration request sent by the UE and received by the AMF may include the requested DRX cycle (in any suitable format) and in some aspects include a default DRX override request. In some aspects, such a request may be received using the N1 interface and may be transmitted via the base station. In some aspects, the AMF may receive the registration request message using any suitable communication interface (such as the N1 interface (e.g., via network interface 616)).

[0116] At 1004, the AMF may determine whether to allow a DRX cycle for the UE that is longer than the default paging cycle for one or more base stations in the registration area. In some aspects, the AMF may determine whether to allow a DRX cycle that exceeds the default paging interval (which may result in a DRX cycle that is shorter or longer than the default paging cycle) based on any suitable factors. In some aspects, the AMF may determine whether to allow a DRX cycle for the UE that is longer than the default paging cycle based on various factors (such as load balancing).

[0117] If the AMF determines to allow a DRX cycle that is longer than the default paging cycle (yes at 1006), the process 1000 may move to 1008. At 1008, the AMF may assign a DRX cycle to the UE that exceeds the default paging cycle of one or more base stations in the registration area. As described above in connection with Figure 7 712, the AMF may assign a DRX cycle that is slightly longer or slightly shorter than the DRX cycle requested at 1002 for various reasons (such as the availability of time slots corresponding to the requested DRX cycle, subscription based on the scheduled entity, local configuration, latency requirements for the public alert system).

[0118] At 1010, the AMF may notify the UE of the accepted DRX cycle and an indication that the request to override the default DRX cycle has been accepted. In some aspects, the AMF may notify the UE by sending a registration acceptance message (which may be a registration acceptance message defined according to one or more 5G standards such as 3GPP Technical Specification 23.501), the registration acceptance message including the accepted DRX cycle assigned to the UE by the core network (e.g., by the AMF). Additionally, in some aspects, the AMF may include an explicit indication in the registration acceptance message that the override of the default DRX for the base station has been accepted. For example, as described above in connection with Figure 7As described in 712, the AMF may send a registration acceptance message to the UE, which includes the accepted DRX cycle (in any suitable format) and in some aspects includes a default DRX override acceptance (if such a request is accepted). In some aspects, such a message may be sent using the N1 interface (e.g., via network interface 616) and may be transmitted via the base station communicating with the UE.

[0119] Otherwise, if the AMF determines that a DRX cycle longer than the default paging cycle is not allowed (at 1006, "No"), then process 1000 may move to 1012. At 1012, the AMF may assign a DRX cycle to the UE that is no longer than the default paging cycle of one or more base stations in the registration area.

[0120] At 1014, the AMF may notify the UE of the assigned DRX cycle and an indication that the request to override the default DRX cycle has not been accepted. In some aspects, the AMF may notify the UE by sending a registration acceptance message (which may be a registration acceptance message defined according to one or more 5G standards), which includes the assigned DRX cycle assigned to the UE by the core network (e.g., by the AMF). Additionally, in some aspects, the AMF may include an explicit indication in the registration acceptance message that the override of the default DRX of the base station has not been accepted. It should be noted that in some aspects, the AMF may assign a DRX cycle longer than the default paging cycle, but explicitly indicate that the override of the default DRX of the base station has not been accepted. In some aspects, such a message may be sent using the N1 interface (e.g., via network interface 616) and may be transmitted via the base station communicating with the UE.

[0121] At 1016, the AMF may determine whether there is any new data that requires paging the UE to transfer new data to the UE. In some aspects, the AMF may use any suitable technique or combination of techniques to determine whether there is any new data that requires paging. For example, if the AMF receives a new data notification and determines that the UE is not in a connected state (e.g., a state other than RRC_CONNECTED), then the AMF may instruct the RAN associated with the UE to page the UE with the new data. As another example, the AMF may use the technique described in Figure 7 720 above.

[0122] At 1018, if the AMF determines that there is new data for which the UE is to be paged (yes at 1018), then process 1000 may move to 1020. At 1020, the AMF may send a paging message to the base station (or base stations), the paging message including the new data for the UE and may include the DRX cycle that has been assigned to the UE and an indication that overriding of the default DRX has been authorized (if the request is accepted). As described above in connection with Figure 7 722, the AMF may send the paging message as an N2 message. In some aspects, the AMF may (e.g., via network interface 616) send the N2 message to all base stations within the current tracking area of the UE. For example, this may cause each of these base stations to page the UE, regardless of whether the UE is currently being served by a cell associated with the base station.

[0123] Otherwise, if the AMF determines that there is no new data for which the UE is to be paged (no at 1018), then process 1000 may move to 1022. At 1022, if the UE is still within the registered area (yes at 1022), then process 1000 may return to 1016. Otherwise, if the UE has left the registered area (no at 1022), then process 1000 may end.

[0124] Example 1: A method, apparatus, system, and non-transitory computer-readable medium for wireless communication, including: sending, by a user equipment, a request for a discontinuous reception (DRX) cycle interval for a first duration; receiving, by the user equipment, an indication that a DRX cycle interval having a second duration has been assigned to the user equipment by a core network component; receiving, by the user equipment, a system information block (SIB) from a base station, the SIB including: a default paging cycle; and an indication of support for overriding the default paging cycle; entering, by the user equipment, an inactive state in which a transceiver of the user equipment is in a low power state; and while the user equipment is in the inactive state and based on the indication of support by the base station for overriding the default paging cycle, causing the transceiver to periodically enter a higher power state at a frequency based on the second duration to monitor its paging channel.

[0125] Example 2: The method, apparatus, system, and non-transitory computer-readable medium according to Example 1, wherein the request is a registration request message, the registration request message including: the first duration as the requested DRX cycle interval; and a default DRX override request.

[0126] Example 3: The method, apparatus, system, and non-transitory computer-readable medium according to any one of Examples 1 to 2, wherein receiving the DRX cycle interval having the second duration includes receiving a registration acceptance message, the registration acceptance message including: the second duration; and a default DRX override acceptance.

[0127] Example 4: The method, apparatus, system, and non-transitory computer-readable medium according to any one of Examples 1 to 3, wherein the first duration and the second duration are the same.

[0128] Example 5: The method, apparatus, system, and non-transitory computer-readable medium according to any one of Examples 1 to 4, wherein the core network component is an access and mobility management function node (AMF).

[0129] Example 6: The method, apparatus, system, and non-transitory computer-readable medium according to any one of Examples 1 to 5, wherein sending the request for the DRX cycle interval having the first duration includes: sending the request for the DRX cycle interval having the first duration in response to entering a new registration area.

[0130] Example 7: The method, apparatus, system, and non-transitory computer-readable medium according to any one of Examples 1 to 6, wherein the SIB further includes information indicating a maximum DRX cycle duration supported by the base station, and the method, apparatus, system, and non-transitory computer-readable medium further includes: determining which of the second duration and the maximum DRX cycle duration supported by the base station is shorter; and setting a period based on the second duration by selecting the shorter of the second duration and the maximum DRX cycle duration supported by the base station.

[0131] Example 8: The method, apparatus, system, and non-transitory computer-readable medium according to any one of Examples 1 to 7, wherein the information indicating the maximum DRX cycle duration supported by the base station includes a maximum DRX cycle value provided via a maximum DRX cycle field.

[0132] Example 9: The method, apparatus, system, and non-transitory computer-readable medium according to any one of Examples 1 to 8, wherein the information indicating the maximum DRX cycle duration supported by the base station includes a system information modification period, and the method, apparatus, system, and non-transitory computer-readable medium further includes: determining the maximum DRX cycle duration supported by the base station based on the system information modification period.

[0133] Example 10: The method, apparatus, system, and non-transitory computer-readable medium according to any one of Examples 1 to 9 further include: receiving, by the user equipment, a second system information block (SIB) from a second base station, the second SIB including: a default paging cycle; and an indication of non-support for overriding the default paging cycle; and when the user equipment is in the inactive state and based on the indication of non-support for overriding the default paging cycle by the base station, causing the transceiver to periodically enter a higher power state at a period based on the default paging cycle to monitor its paging channel.

[0134] Example 11: The method, apparatus, system, and non-transitory computer-readable medium according to any one of Examples 1 to 10, wherein the indication of non-support for overriding the default paging cycle includes one or more of the following: a default DRX override value that is false; a maximum DRX cycle duration value that is zero; omission of the default DRX override value from the second SIB; or omission of the maximum DRX cycle duration value from the second SIB.

[0135] Example 12: The method, apparatus, system, and non-transitory computer-readable medium according to any one of Examples 1 to 11, wherein the indication of support for overriding the default paging cycle includes one or more of the following: a default DRX override value that is true; or a non-zero maximum DRX cycle duration value.

[0136] Example 13: The method, apparatus, system, and non-transitory computer-readable medium according to any one of Examples 1 to 12 further include: receiving, from a user equipment, a request for a discontinuous reception (DRX) cycle interval for a first duration; assigning, to the user equipment, a DRX cycle interval having a second duration; sending, to the user equipment, an indication that the DRX cycle interval having the second duration has been assigned to the user equipment; and sending, to a base station in a registration area where the user equipment is located, a paging message, the paging message including: an indication that the DRX cycle interval having the second duration has been assigned to the user equipment; and an indication of permission to override the default paging cycle of the base station.

[0137] Example 14: A method, apparatus, system, and non-transitory computer-readable medium for wireless communication, comprising: receiving, from a user equipment, a request for a discontinuous reception (DRX) cycle interval for a first duration; assigning, to the user equipment, a DRX cycle interval having a second duration; sending, to the user equipment, an indication that the DRX cycle interval having the second duration has been assigned to the user equipment; and sending a paging message to a base station in a registration area where the user equipment is located, the paging message comprising: an indication that the DRX cycle interval having the second duration has been assigned to the user equipment; and an indication that allows overriding of a default paging cycle of the base station.

[0138] Example 15: The method, apparatus, system, and non-transitory computer-readable medium according to any one of Examples 1 to 14, wherein the request is a registration request message, the registration request message comprising: the first duration as the requested DRX cycle interval; and a default DRX override request.

[0139] Example 16: The method, apparatus, system, and non-transitory computer-readable medium according to any one of Examples 1 to 15, wherein sending the DRX cycle interval having the second duration comprises sending a registration acceptance message, the registration acceptance message comprising: the second duration; and a default DRX override acceptance.

[0140] Example 17: The method, apparatus, system, and non-transitory computer-readable medium according to any one of Examples 1 to 16, wherein the first duration and the second duration are the same.

[0141] Example 18: The method, apparatus, system, and non-transitory computer-readable medium according to any one of Examples 1 to 17, wherein assigning the DRX cycle interval having the second duration is performed by an access and mobility management function node (AMF), and wherein the paging message is an N2 message sent from the AMF to the base station.

[0142] Example 19: The method, apparatus, system, and non-transitory computer-readable medium according to any one of Examples 1 to 18 further include: broadcasting, by a base station, a system information block (SIB), the SIB including: a default paging cycle; and an indication of support for overriding the default paging cycle; receiving, from a core network component, a paging message, the paging message including: an indication that a DRX cycle interval having the second duration has been assigned to the user equipment; and an indication of permission to override the default paging cycle of the base station; and paging the user equipment periodically based on the second duration based on the indication of permission to override the default paging cycle.

[0143] Example 20: A method, apparatus, system, and non-transitory computer-readable medium for wireless communication, including: broadcasting, by a base station, a system information block (SIB), the SIB including: a default paging cycle; and an indication of support for overriding the default paging cycle; receiving, from a core network component, a paging message, the paging message including: an indication that a DRX cycle interval having the second duration has been assigned to the user equipment; and an indication of permission to override the default paging cycle of the base station; and paging the user equipment periodically based on the second duration based on the indication of permission to override the default paging cycle.

[0144] Example 21: The method, apparatus, system, and non-transitory computer-readable medium according to any one of Examples 1 to 20, wherein the paging message is an N2 message sent from an access and mobility management function node AMF to the base station.

[0145] Example 22: The method, apparatus, system, and non-transitory computer-readable medium according to any one of Examples 1 to 21, the apparatus including: a unit for sending a request for a discontinuous reception (DRX) cycle interval for a first duration; a unit for receiving an indication that a DRX cycle interval having a second duration has been assigned to the user equipment by a core network component; a unit for receiving a system information block (SIB) from a base station, the SIB including: a default paging cycle; and an indication of support for overriding the default paging cycle; a unit for entering an inactive state in which a transceiver of the user equipment is in a low power state; and a unit for causing the transceiver to periodically enter a higher power state to monitor its paging channel based on the indication of support for overriding the default paging cycle of the base station when the wireless communication device is in the inactive state and based on the second duration.

[0146] Example 23: A system includes: a unit for sending a request for a discontinuous reception (DRX) cycle interval for a first duration; a unit for receiving an indication that a DRX cycle interval having a second duration has been assigned to the user equipment by a core network component; a unit for receiving a system information block (SIB) from a base station, the SIB including: a default paging cycle; and an indication of support for overriding the default paging cycle; a unit for entering an inactive state in which a transceiver of the user equipment is in a low power state; and a unit for causing the transceiver to periodically enter a higher power state to monitor its paging channel at a period based on the second duration when the wireless communication device is in the inactive state and based on the indication of support for overriding the default paging cycle by the base station.

[0147] Example 24: The method, apparatus, system, and non-transitory computer-readable medium according to any one of Examples 1 to 23, wherein the unit for sending the request for the DRX cycle interval for the first duration is responsive to entering a new registration area.

[0148] Example 25: The method, apparatus, system, and non-transitory computer-readable medium according to any one of Examples 1 to 24, wherein the system further includes: a unit for determining which of the second duration and the maximum DRX cycle duration supported by the base station is shorter; and a unit for setting the period based on the second duration by selecting the shorter of the second duration and the maximum DRX cycle duration supported by the base station.

[0149] Example 26: The method, apparatus, system, and non-transitory computer-readable medium according to any one of Examples 1 to 25, wherein the system further includes: a unit for receiving a second system information block (SIB) from a second base station, the second SIB including: a default paging cycle; and an indication of non-support for overriding the default paging cycle; and a unit for causing the transceiver to periodically enter a higher power state to monitor its paging channel at a period based on the default paging cycle when the wireless communication device is in the inactive state and based on the indication of non-support for overriding the default paging cycle by the base station.

[0150] Example 27: The method, apparatus, system, and non-transitory computer-readable medium according to any one of Examples 1 to 26, wherein the system further comprises: a unit for receiving a request for a discontinuous reception (DRX) cycle interval for a first duration from a user equipment; a unit for assigning a DRX cycle interval having a second duration to the user equipment; a unit for sending an indication to the user equipment that the DRX cycle interval having the second duration has been assigned to the user equipment; and a unit for sending a paging message to a base station in a registration area where the user equipment is located, the paging message comprising: an indication that the DRX cycle interval having the second duration has been assigned to the user equipment; and an indication that allows overriding of a default paging cycle of the base station.

[0151] Example 28: A system, comprising: a unit for receiving a request for a discontinuous reception (DRX) cycle interval for a first duration from a user equipment; a unit for assigning a DRX cycle interval having a second duration to the user equipment; a unit for sending an indication to the user equipment that the DRX cycle interval having the second duration has been assigned to the user equipment; and a unit for sending a paging message to a base station in a registration area where the user equipment is located, the paging message comprising: an indication that the DRX cycle interval having the second duration has been assigned to the user equipment; and an indication that allows overriding of a default paging cycle of the base station.

[0152] Example 29: The method, apparatus, system, and non-transitory computer-readable medium according to any one of Examples 1 to 28, wherein the system further comprises: a unit for broadcasting a system information block (SIB), the SIB comprising: a default paging cycle; and an indication that supports overriding of the default paging cycle; a unit for receiving a paging message from a core network component, the paging message comprising: an indication that the DRX cycle interval having the second duration has been assigned to the user equipment; and an indication that allows overriding of a default paging cycle of the base station; and a unit for periodically paging the user equipment at a period based on the second duration.

[0153] Example 30: A system includes: a unit for broadcasting a System Information Block (SIB), the SIB including: a default paging cycle; and an indication of support for overriding the default paging cycle; a unit for receiving a paging message from a core network component, the paging message including: an indication that a DRX cycle interval having the second duration has been assigned to the user equipment; and an indication of permission to override the default paging cycle of the base station; and a unit for paging the user equipment periodically at a period based on the second duration.

[0154] Example 31: A wireless communication device includes: a unit for sending a request for a discontinuous reception (DRX) cycle interval for a first duration; a unit for receiving an indication that a DRX cycle interval having a second duration has been assigned to the user equipment by a core network component; a unit for receiving a System Information Block (SIB) from a base station, the SIB including: a default paging cycle; and an indication of support for overriding the default paging cycle; a unit for entering an inactive state in which a transceiver of the user equipment is in a low power state; and a unit for causing the transceiver to enter a higher power state periodically at a period based on the second duration to monitor its paging channel when the wireless communication device is in the inactive state and based on the indication that the base station supports overriding the default paging cycle.

[0155] Example 32: The wireless communication device according to Example 31, wherein the unit for sending the request for the DRX cycle interval for the first duration is responsive to entering a new registration area.

[0156] Example 33: The wireless communication device according to any one of Examples 31 and 32, wherein the SIB further includes information indicating a maximum DRX cycle duration supported by the base station, and wherein the wireless communication device further includes: a unit for determining which of the second duration and the maximum DRX cycle duration supported by the base station is shorter; and a unit for setting the period based on the second duration by selecting the shorter of the second duration and the maximum DRX cycle duration supported by the base station.

[0157] Example 34: The wireless communication device according to any one of Examples 31 to 33 further includes: a unit for receiving a second system information block (SIB) from a second base station, the second SIB including: a default paging cycle; and an indication of non - support for overriding the default paging cycle; and a unit for causing the transceiver to periodically enter a higher power state to monitor its paging channel at a period based on the default paging cycle when the wireless communication device is in the inactive state and based on the indication of non - support for overriding the default paging cycle by the base station.

[0158] Example 35: A core network component includes: a unit for receiving a request for a discontinuous reception (DRX) cycle interval for a first duration from a user equipment; a unit for assigning a DRX cycle interval having a second duration to the user equipment; a unit for sending an indication to the user equipment that the DRX cycle interval having the second duration has been assigned to the user equipment; and a unit for sending a paging message to a base station in a registration area where the user equipment is located, the paging message including: an indication that the DRX cycle interval having the second duration has been assigned to the user equipment; and an indication of permission to override the default paging cycle of the base station.

[0159] Example 36: A scheduling entity includes: a unit for broadcasting a system information block (SIB), the SIB including: a default paging cycle; and an indication of support for overriding the default paging cycle; a unit for receiving a paging message from a core network component, the paging message including: an indication that the DRX cycle interval having the second duration has been assigned to the user equipment; and an indication of permission to override the default paging cycle of the base station; and a unit for paging the user equipment periodically at a period based on the second duration.

[0160] Example 37: The scheduling entity according to Example 36, wherein the SIB further includes information indicating a maximum DRX cycle duration supported by the base station, and wherein the scheduling entity further includes: a unit for determining which of the second duration and the maximum DRX cycle duration supported by the base station is shorter; and a unit for setting the period based on the second duration by selecting the shorter of the second duration and the maximum DRX cycle duration supported by the base station.

[0161] Example 38: A system includes one or more of the following: the wireless communication device according to any one of Examples 31 to 34, the core network component according to Example 35, and / or the scheduling entity according to any one of Examples 36 and 37.

[0162] Certain aspects of a wireless communication network have been presented with reference to exemplary implementations. As will be readily appreciated by those skilled in the art, the various aspects described throughout this disclosure may be extended to other telecommunication systems, network architectures, and communication standards.

[0163] By way of example, the various aspects may be implemented within other systems defined by 3GPP (e.g., Long Term Evolution (LTE), Evolved Packet System (EPS), Universal Mobile Telecommunications System (UMTS), and / or Global System for Mobile communications (GSM)). The various aspects may also be extended to systems defined by the Third Generation Partnership Project 2 (3GPP2), such as CDMA2000 and / or Evolution-Data Optimized (EV-DO). Other examples may be implemented within systems employing IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra Wide Band (UWB), Bluetooth, and / or other suitable systems. The actual telecommunication standard, network architecture, and / or communication standard employed will depend on the particular application and the overall design constraints imposed on the system.

[0164] In this disclosure, the term "exemplary" is used to mean "serving as an example, instance, or illustration". Any implementation or aspect described herein as "exemplary" is not necessarily to be construed as preferred or superior to other aspects of the disclosure. Similarly, the term "aspect" does not require that all aspects of the disclosure include the discussed feature, advantage, or mode of operation. The term "coupled" is used herein to refer to either a direct or an indirect coupling between two objects. For example, if object A physically contacts object B, and object B contacts object C, then objects A and C may still be considered to be coupled to each other, even if they do not directly physically contact each other. For example, a first object may be coupled to a second object even if the first object never directly physically contacts the second object. The terms "circuit" and "circuitry" are used broadly and are intended to include both hardware implementations of electronic devices and conductors (which, when connected and configured, perform the functions described herein, without limitation as to the type of electronic circuits) and software implementations of information and instructions (which, when executed by a processor, perform the functions described herein).

[0165] For Figures 1 - 10 one or more of the components, steps, features, and / or functions shown in Figures 1 - 10The apparatuses, devices, and / or components shown herein can be configured to perform one or more of the methods, features, or steps described herein. The novel algorithms described herein can also be implemented efficiently in software and / or embedded in hardware.

[0166] It is to be understood that the specific order or hierarchy of steps in the disclosed methods is an illustration of an exemplary process. It is to be understood that, based on design preferences, the specific order or hierarchy of steps in these methods can be rearranged. The appended method claims present the elements of the various steps in sample order and are not meant to be limited to the specific order or hierarchy presented, unless expressly recited herein.

[0167] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein can be applied to other aspects. Thus, the claims are not intended to be limited to the aspects shown herein, but are to be accorded the full scope consistent with the language of the claims, wherein the reference to an element in the singular is not intended to mean "one and only one" unless explicitly so stated, but rather "one or more." Unless otherwise expressly stated, the term "some" refers to one or more. A phrase referring to "at least one" of a list of items refers to any combination of those items, including a single member. For example, "at least one of the following: a, b, or c" is intended to cover: a; b; c; a and b; a and c; b and c; and a, b, and c. All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are known or will be known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public, whether or not such disclosure is expressly recited in the claims.

Claims

1. A method for wireless communication, comprising: When a user equipment enters a new registration area, the user equipment sends a registration request message, the registration request message including a request for an idle discontinuous reception (I-DRX) cycle interval for a first duration; The user equipment receives a registration acceptance message, the registration acceptance message including an indication that an I-DRX cycle interval having a second duration has been assigned to the user equipment by a core network component; When the user equipment enters a new serving cell, the user equipment receives a system information block (SIB) from a base station, the SIB including: A default I-DRX paging cycle; Information indicating a maximum I-DRX cycle duration supported by the base station, the information indicating the maximum I-DRX cycle duration supported by the base station including a system information modification period; and An indication of support for overriding the default I-DRX paging cycle; The user equipment determines the maximum I-DRX cycle duration supported by the base station based on the system information modification period; The user equipment determines which of the second duration or the maximum I-DRX cycle duration supported by the base station is shorter; The user equipment sets a period based on the second duration by selecting the shorter of the second duration or the maximum I-DRX cycle duration supported by the base station; The user equipment enters a radio resource control idle (RRC_IDLE) state, in which the transceiver of the user equipment is in a low power state; and When the user equipment is in the RRC_IDLE state and based on the indication of support for overriding the default I-DRX paging cycle by the base station, the transceiver periodically enters a higher power state at the period to monitor its paging channel.

2. The method according to claim 1, wherein, The registration request message further includes: The first duration as the requested I-DRX cycle interval; and A default I-DRX override request.

3. The method according to claim 1, wherein, The registration acceptance message further includes: The second duration; and A default I-DRX override acceptance.

4. The method according to claim 3, wherein, The first duration and the second duration are the same.

5. The method according to claim 1, wherein, The core network component is an access and mobility management function node (AMF).

6. The method according to claim 1, further comprising: The user equipment receives a second system information block (SIB) from a second base station, the second SIB including: A default I-DRX paging cycle associated with the second base station; and An indication of non-support for overriding the default I-DRX paging cycle associated with the second base station; and When the user equipment is in the RRC_IDLE state and based on an indication that the base station does not support overriding the default I-DRX paging cycle, cause the transceiver to periodically enter the higher power state at a period based on the default I-DRX paging cycle to monitor its paging channel.

7. The method according to claim 6, wherein, the indication of not supporting overriding the default I-DRX paging cycle associated with the second base station includes one or more of the following: a default I-DRX override value that is false; a maximum I-DRX cycle duration value that is zero; omission of the default I-DRX override value from the second SIB; or omission of the maximum I-DRX cycle duration value from the second SIB.

8. The method according to claim 1, wherein, the indication of supporting overriding the default I-DRX paging cycle includes one or more of the following: a default I-DRX override value that is true; or a non-zero maximum I-DRX cycle duration value.

9. A wireless communication device, comprising: a transceiver; a memory; and a processor communicatively coupled to the transceiver and the memory, the processor configured to: when the wireless communication device enters a new registration area, send a registration request message, the registration request message including a request for an idle discontinuous reception (I-DRX) cycle interval for a first duration; receive a registration acceptance message, the registration acceptance message including an indication that an I-DRX cycle interval having a second duration has been assigned to the wireless communication device by a core network component; when the wireless communication device enters a new serving cell, receive a system information block (SIB) from a base station, the SIB including: a default I-DRX paging cycle; information indicating a maximum I-DRX cycle duration supported by the base station, the information indicating the maximum I-DRX cycle duration supported by the base station including a system information modification period; and an indication of supporting overriding the default I-DRX paging cycle; determine the maximum I-DRX cycle duration supported by the base station based on the system information modification period; determine which of the second duration or the maximum I-DRX cycle duration supported by the base station is shorter; set a period based on the second duration by selecting the shorter of the second duration or the maximum I-DRX cycle duration supported by the base station; enter a radio resource control idle (RRC_IDLE) state, in which the transceiver is in a low power state; and when the wireless communication device is in the RRC_IDLE state and based on an indication that the base station supports overriding the default I-DRX paging cycle, cause the transceiver to periodically enter the higher power state at the period to monitor its paging channel.

10. The wireless communication device according to claim 9, wherein, the registration request message further includes: The first duration as the requested I-DRX cycle interval; and Default I-DRX override request.

11. The wireless communication device according to claim 9, wherein, The registration acceptance message further includes: The second duration; and Default I-DRX override acceptance.

12. The wireless communication device according to claim 11, wherein, The first duration and the second duration are the same.

13. The wireless communication device according to claim 9, wherein, The core network component is an access and mobility management function node (AMF).

14. The wireless communication device according to claim 9, wherein, The processor is further configured to: Receive a second system information block (SIB) from a second base station, the second SIB including: A default I-DRX paging cycle associated with the second base station; and An indication of non-support for overriding the default I-DRX paging cycle associated with the second base station; and When the wireless communication device is in the RRC_IDLE state and based on the indication of non-support for overriding the default I-DRX paging cycle by the base station, cause the transceiver to periodically enter the higher power state at a period based on the default I-DRX paging cycle to monitor its paging channel.

15. The wireless communication device according to claim 14, wherein, The indication of non-support for overriding the default I-DRX paging cycle associated with the second base station includes one or more of the following: A default I-DRX override value that is false; a maximum I-DRX cycle duration value that is zero; omission of the default I-DRX override value from the second SIB; or omission of the maximum I-DRX cycle duration value from the second SIB.

16. The wireless communication device according to claim 9, wherein, The indication of support for overriding the default I-DRX paging cycle includes one or more of the following: A default I-DRX override value that is true; or a non-zero maximum I-DRX cycle duration value.

Images