Paging Techniques for Balancing Power Savings and Public Alerting System Monitoring

Abstract

Aspects of the present disclosure relate to a UE and a network device for wireless communication. The UE sends an indication of the ability to receive PWS signals and / or an indication of the latency requirement for receiving PWS signals to the network device. The UE receives a configured DRX cycle value associated with the indication and a paging signal corresponding to the PWS signal associated with the configured DRX cycle value from the network device. The network device determines whether the UE is capable of receiving PWS signals and whether the UE expects to receive the PWS signals within a duration. The network device configures the DRX cycle value based on the determination and sends the configured DRX cycle value and a paging signal corresponding to the PWS signal based on the configured DRX cycle value to the UE. Other aspects, features, and embodiments are also claimed and described.

Description

[0001] Cross - reference to related applications

[0002] This application claims the benefit and priority of Provisional Application No. 62 / 842,492, filed on May 2, 2019, Provisional Application No. 62 / 847,169, filed on May 13, 2019, and Non - Provisional Application No. 16 / 862,175, filed on Apr. 29, 2020, with the United States Patent and Trademark Office, the entire contents of which are incorporated herein by reference as if fully set forth below and for all applicable purposes. Technical Field

[0003] The techniques discussed below generally relate to wireless communication systems and, in particular, to paging techniques. Embodiments may provide and implement techniques for extending paging cycles for power savings of communication devices and paging techniques for balancing power savings and public - warning - system (PWS) signal monitoring.

[0004] Introduction

[0005] The ability of a user equipment (UE) to monitor paging (i.e., paging monitoring) enables various operations to be performed at the UE. For example, paging monitoring allows the UE to learn of updates to system information (e.g., neighbor configuration, cell configuration, etc.), receive calls (e.g., mobile - terminated calls), and receive public - warning - system (PWS) signals (e.g., tsunami, earthquake, and / or Amber alerts). Notably, PWS signals may be life - critical, and thus, the UE may prefer to receive such signals as soon as possible.

[0006] According to current 3GPP specifications (3GPP TS 38.304 v15.3.0), the UE monitors paging in each discontinuous - reception cycle (DRX cycle). However, depending on the periodicity of the DRX cycle used, the UE may wake up too frequently (e.g., with short periodicity) to monitor paging. This may cause the UE to unnecessarily consume a large amount of power but may also increase the chance for the UE to receive life - critical PWS signals. Alternatively, based on the DRX cycle used, the UE may wake up less frequently (e.g., with long periodicity) to monitor paging. This may cause the UE to consume less power but may also cause the UE to miss paging signals including life - critical PWS signals, which is undesirable.

[0007] Brief Overview of Some Examples

[0008] A brief overview of one or more aspects of the present disclosure is presented below to provide a basic understanding of these aspects. This overview is not an exhaustive survey of all contemplated features of the present disclosure, and is neither intended to identify key or critical elements of all aspects of the present disclosure nor to attempt to define 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 follows.

[0009] Aspects of the present disclosure relate to user equipment (UE) and network devices for wireless communication. The UE transmits an indication of at least one of the ability to receive a Public Warning System (PWS) signal or a latency requirement for receiving the PWS signal to the network device. The UE receives a configured discontinuous reception (DRX) cycle value associated with the indication from the network device, and further receives a paging signal corresponding to the PWS signal associated with the configured DRX cycle value from the network device. The network device determines whether the UE is capable of receiving the PWS signal and whether the UE expects to receive the PWS signal within a duration. The network device configures the DRX cycle value based on the determination and transmits the configured DRX cycle value to the UE and the radio access network (RAN). The network device further transmits a paging signal corresponding to the PWS signal associated with the configured DRX cycle value to the UE. The disclosed aspects include various method, system, device, and apparatus embodiments.

[0010] In one example, a method for wireless communication at a user equipment (UE) is disclosed. The method includes: transmitting an indication of at least one of the ability to receive a Public Warning System (PWS) signal or a latency requirement specifying whether the UE expects to receive the PWS signal within a duration to a network device, receiving a configured discontinuous reception (DRX) cycle value associated with the indication from the network device, receiving a paging signal corresponding to the PWS signal associated with the configured DRX cycle value from the network device, and receiving the PWS signal from the network device. If the paging signal includes a sequence number or index of the PWS signal corresponding to the paging signal, the method may further include: determining whether to receive the PWS signal based on the sequence number or index included in the paging signal, waking up to receive the PWS signal if it is determined based on the sequence number or index to receive the PWS signal, and suppressing waking up for receiving the PWS signal if it is determined based on the sequence number or index not to receive the PWS signal.

[0011] In another example, a user equipment (UE) for wireless communication is disclosed. The UE includes at least one processor, a transceiver communicatively coupled to the at least one processor, and a memory communicatively coupled to the at least one processor. The at least one processor and the memory are configured to: send an indication to a network device indicating at least one of the ability to receive a Public Warning System (PWS) signal or a latency requirement specifying whether the UE expects to receive a PWS signal within a duration, receive a configured discontinuous reception (DRX) cycle value associated with the indication from the network device, receive a paging signal corresponding to the PWS signal associated with the configured DRX cycle value from the network device, and receive the PWS signal from the network device. If the paging signal includes a sequence number or index of the PWS signal corresponding to the paging signal, the at least one processor and the memory may be further configured to determine whether to receive the PWS signal based on the sequence number or index included in the paging signal, wake up to receive the PWS signal if it is determined based on the sequence number or index to receive the PWS signal, and suppress waking up for receiving the PWS signal if it is determined based on the sequence number or index not to receive the PWS signal.

[0012] Various method, system, device, and apparatus embodiments may further include additional features. For example, the UE may determine at least one of the ability to receive a PWS signal or a latency requirement based on at least one of the area where the UE is located or the UE's knowledge of an event that will prompt the transmission of a PWS signal. In another example, the indication requests a configured DRX cycle value from the network device, and the indication is sent via a non-access stratum (NAS) registration procedure or a capability update procedure.

[0013] In some examples, the UE may receive the paging signal by: determining that the UE is located in an area at risk of an event that will prompt the transmission of a PWS signal, updating the configured DRX cycle value with a historical configured DRX cycle value associated with the area, and receiving the paging signal from the network device based on the updated DRX cycle value. In another example, the UE may receive the paging signal by: determining that the UE is located in an area at risk of an event that will prompt the transmission of a PWS signal, and when the UE is able to receive the PWS signal and the latency requirement specifies that the UE expects to receive the PWS signal within a duration, receiving the paging signal based on the minimum of the configured DRX cycle value, the default DRX cycle value, and the radio access network (RAN)-configured DRX cycle value.

[0014] In some examples, if the UE is unable to receive the PWS signal or the latency requirement specifies that the UE does not expect to receive the PWS signal within a duration, the received configured DRX cycle value indicates to the UE that it is not allowed to receive the paging signal based on the minimum of the configured DRX cycle value, the default DRX cycle value, and the DRX cycle value configured by the radio access network (RAN), and that it is to receive the paging signal based on the configured DRX cycle value. In another example, the UE may receive the paging signal by deriving a paging repetition pattern over the durations of N configured DRX cycle values, where N is an integer greater than or equal to 1, selectively waking up to receive the paging signal based on the derived paging repetition pattern, and storing the derived paging repetition pattern in a database.

[0015] In some examples, the paging signal includes a sequence number or index of the PWS signal corresponding to the paging signal. Thus, the UE may further be configured to determine whether to receive the PWS signal based on the sequence number or index included in the paging signal, wake up to receive the PWS signal if it is determined to receive the PWS signal based on the sequence number or index, and suppress waking up to receive the PWS signal if it is determined not to receive the PWS signal based on the sequence number or index.

[0016] In one example, a method for wireless communication at a network device is disclosed. The method includes determining whether a user equipment (UE) is able to receive a public warning system (PWS) signal and whether the UE expects to receive the PWS signal within a duration, configuring a discontinuous reception (DRX) cycle value based on the determination, sending the configured DRX cycle value to the UE and the radio access network (RAN), sending a paging signal corresponding to the PWS signal to the UE based on the configured DRX cycle value, and sending the PWS signal to the UE.

[0017] In another example, a network device for wireless communication is disclosed. The network device includes at least one processor, a transceiver communicatively coupled to the at least one processor, and a memory communicatively coupled to the at least one processor. The at least one processor and the memory are configured to determine whether a user equipment (UE) is able to receive a public warning system (PWS) signal and whether the UE expects to receive the PWS signal within a duration, configure a discontinuous reception (DRX) cycle value based on the determination, send the configured DRX cycle value to the UE and the radio access network (RAN), send a paging signal corresponding to the PWS signal to the UE based on the configured DRX cycle value, and send the PWS signal to the UE.

[0018] Embodiments of various methods, systems, devices, and apparatuses may also include additional features. For example, if a UE is capable of receiving a PWS signal and desires to receive the PWS signal within a duration, the configured DRX cycle value is the first DRX cycle value and the transmission of the configured DRX cycle value indicates to the UE that the UE is allowed to receive the paging signal based on the minimum of the first DRX cycle value, the default DRX cycle value, and the DRX cycle value configured by the RAN. In another example, if the UE is not capable of receiving the PWS signal or does not desire to receive the PWS signal within the duration, the configured DRX cycle value is the second DRX cycle value and the transmission of the configured DRX cycle value indicates to the UE that the UE is not allowed to receive the paging signal based on the minimum of the second DRX cycle value, the default DRX cycle value, and the DRX cycle value configured by the RAN, and that the UE is to receive the paging signal based on the second DRX cycle value.

[0019] In some examples, the network device may determine whether the UE is capable of receiving the PWS signal by receiving an indication of PWS capability or non-PWS capability from the UE. In another example, the network device may determine whether the UE desires to receive the PWS signal within the duration by receiving a latency requirement via the received indication. In a further example, the indication requests a configured DRX cycle value from the network device, and the indication is received via a non-access stratum (NAS) registration procedure or a capability update procedure.

[0020] In some examples, the network device may determine whether the UE is capable of receiving the PWS signal by determining that the UE monitors paging according to an established paging duration, and may transmit the paging signal by transmitting the paging signal to the UE within a paging duration that is at least as long as the established paging duration. In another example, the paging signal includes a sequence number or index of the PWS signal corresponding to the paging signal.

[0021] These and other aspects of the present invention will be more fully understood after reading the following detailed description. After reading the following description of specific exemplary embodiments in conjunction with the accompanying drawings, other aspects, features, and embodiments will be apparent to those of ordinary skill in the art. Although the features may be discussed below 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 such features may be used in accordance with the various embodiments discussed herein. In a similar manner, although the exemplary embodiments may be discussed below as device, system, or method embodiments, it should be appreciated that such exemplary embodiments may be implemented in various devices, systems, and methods. Brief Description of the Drawings

[0023] Figure 1is a schematic illustration of a wireless communication system according to some aspects.

[0024] Figure 2 is a conceptual illustration of an example of a radio access network according to some aspects.

[0025] Figure 3 is a block diagram illustrating a wireless communication system supporting multiple-input multiple-output (MIMO) communication according to some aspects.

[0026] Figure 4 is a schematic illustration of the organization of radio resources in an air interface utilizing orthogonal frequency division multiplexing (OFDM) according to some aspects.

[0027] Figure 5 is a flowchart illustrating an example UE-specific paging cycle negotiation according to some aspects of the present disclosure.

[0028] Figure 6 is a flowchart illustrating an example UE-specific paging cycle negotiation for a UE in the RRC_INACTIVE state according to some aspects of the present disclosure.

[0029] Figure 7 is a table illustrating an example encoding of DRX cycle values at the non-access stratum (NAS) according to some aspects of the present disclosure.

[0030] Figure 8 is a block diagram conceptually illustrating an example of the hardware implementation of a network device according to some aspects of the present disclosure.

[0031] Figure 9 is a flowchart illustrating an exemplary process for wireless communication at a network device according to some aspects of the present disclosure.

[0032] Figure 10 is a block diagram conceptually illustrating an example of the hardware implementation of a UE according to some aspects of the present disclosure.

[0033] Figure 11 is a flowchart illustrating an exemplary process for wireless communication at a UE according to some aspects of the present disclosure.

[0034] Detailed Description

[0035] 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 practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of various concepts. However, it will be apparent to those skilled 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.

[0036] While aspects and embodiments are described herein by way of illustration of some examples, those skilled in the art will appreciate that additional implementations and use cases can 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, embodiments and / or uses can be generated via integrated chip embodiments and other non-module component-based devices (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / shopping devices, medical devices, AI-enabled devices, etc.). While some examples may or may not be specific to particular use cases or applications, a wide applicability of the described innovations can occur. The scope of implementations can range from chip-level or module components to non-module, 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 environments, devices incorporating the described aspects and features may also necessarily include additional components and features for implementing and practicing the claimed and described embodiments. For example, the transmission and reception of wireless signals necessarily includes several 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 practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, end-user devices, etc. of various sizes, shapes, and constitutions.

[0037] Aspects of the present disclosure provide and implement techniques for extending paging cycles for power saving in communication devices. Other aspects also provide and implement paging techniques for balancing power saving and public warning system (PWS) signal monitoring.

[0038] The various concepts presented throughout this disclosure can be implemented across a wide variety of telecommunications systems, network architectures, and communication standards. Now referring to Figure 1 , by way of illustrative example and not limitation, various aspects of the present disclosure are illustrated with reference to wireless communication system 100. Wireless communication system 100 includes three interacting domains: core network 102, radio access network (RAN) 104, and user equipment (UE) 106. Via wireless communication system 100, UE 106 can be enabled to perform data communication with an external data network 110 (such as but not limited to the Internet).

[0039] The RAN 104 can implement any suitable one or more wireless communication technologies to provide radio access to the UE 106. As an example, the RAN 104 can operate according to the New Radio (NR) specification of the 3rd Generation Partnership Project (3GPP), which is commonly referred to as 5G. As another example, the RAN 104 can operate under a hybrid of 5G NR and the evolved Universal Terrestrial Radio Access Network (eUTRAN) standard, which is commonly referred to as LTE. 3GPP refers to this hybrid RAN as the next-generation RAN, or NG-RAN. Of course, many other examples can be utilized within the scope of this disclosure.

[0040] As illustrated, the RAN 104 includes a plurality of base stations 108. Broadly speaking, a base station is a network element in a radio access network that is responsible for radio transmission and reception to or from a UE in one or more cells. In different technologies, standards, or contexts, a base station may be differently referred to by those skilled in the art 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), g Node B (gNB), or some other suitable term.

[0041] The radio access network 104 is further illustrated as supporting wireless communication for a plurality of mobile devices. A mobile device may be referred to as a user equipment (UE) in the 3GPP standard, but may also be referred to by those skilled in the art as a mobile station (MS), subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal (AT), mobile terminal, wireless terminal, remote terminal, handset, terminal, user agent, mobile client, client, or some other suitable term. A UE may be a device (e.g., a mobile device) that provides a user with access to network services.

[0042] 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 refers generically to a wide variety of devices and technologies. A UE may include several hardware structural components sized, shaped, and arranged to facilitate communication; such components may include antennas, antenna arrays, RF chains, amplifiers, one or more processors, etc., electrically coupled to each other. For example, some non-limiting examples of mobile devices include mobile equipment, cellular (cell) phones, smart phones, Session Initiation Protocol (SIP) phones, laptop devices, personal computers (PCs), notebooks, netbooks, smartbooks, tablet devices, personal digital assistants (PDAs), and a wide variety of embedded systems, such as those 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, a Global Positioning System (GPS) device, an object tracking device, a drone, a multi-axis aircraft, a quadcopter, a remote control device, a consumer and / or wearable device (such as glasses), a wearable camera, a virtual reality device, a smart watch, a health or fitness tracker, a digital audio player (e.g., an MP3 player), a camera, a game console, etc. A mobile device can also be a digital home or smart home device, such as a home audio, video, and / or multimedia device, an appliance, a vending machine, a smart lighting device, a home security system, a smart meter, etc. A mobile device can also be a smart energy device, a security device, a solar panel or solar array, a municipal infrastructure device (e.g., a smart grid) that controls electricity, lighting, water, etc., an industrial automation and / or enterprise device, a logistics controller, an agricultural device, etc. Further, a mobile device can provide connected healthcare or telemedicine support, such as remote healthcare. Telehealth devices can include telehealth monitoring devices and telehealth regulatory devices, and their communication can be prioritized or given preferential access over other types of information, for example, in the form of prioritized access for critical service data transmission and / or associated QoS for critical service data transmission.

[0043] Wireless communication between the RAN 104 and the UE 106 can be described as utilizing an air interface. Transmissions on the air interface from a base station (e.g., base station 108) to one or more UEs (e.g., UE 106) can be referred to as downlink (DL) transmissions. According to certain aspects of the present disclosure, the term downlink may refer to a point-to-multipoint transmission originating at a scheduling entity (described further below; e.g., base station 108). Another way to describe this scenario can be to use the term broadcast channel multiplexing. 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 further aspects of the present disclosure, the term uplink may refer to a point-to-point transmission originating at a scheduled entity (described further below; e.g., UE 106).

[0044] In some examples, access to the air interface can be scheduled, where a scheduling entity (e.g., base station 108) allocates resources for communication among some or all of the devices and equipment within its service area or cell. Within the present disclosure, as discussed further below, the scheduling entity can be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more scheduled entities. That is, for scheduled communication, the UE 106 (which can be a scheduled entity) can utilize the resources allocated by the scheduling entity 108.

[0045] The base station 108 is not the only entity that can act as a scheduling entity. That is, in some examples, a UE can act as a scheduling entity to schedule resources for one or more scheduled entities (e.g., one or more other UEs).

[0046] As Figure 1 illustrated, the scheduling entity 108 can broadcast downlink traffic 112 to one or more scheduled entities 106. Broadly speaking, the scheduling entity 108 is a node or device responsible for scheduling traffic in a wireless communication network (including downlink traffic 112 and in some examples also including uplink traffic 116 from one or more scheduled entities 106 to the scheduling entity 108). On the other hand, the scheduled entity 106 is a node or device that receives downlink control information 114 (including but not limited to scheduling information (e.g., grants), synchronization or timing information), or other control information from another entity in the wireless communication network, such as the scheduling entity 108.

[0047] Generally, the base station 108 can include a backhaul interface for communicating with the backhaul portion 120 of the wireless communication system. The backhaul 120 can provide a link between the base station 108 and the core network 102. Additionally, in some examples, the backhaul network can provide interconnection between the respective base stations 108. Various types of backhaul interfaces can be employed, such as direct physical connections using any suitable transport network, virtual networks, and the like.

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

[0049] Now referring to Figure 2 , by way of example and not limitation, a schematic illustration of a RAN 200 is provided. In some examples, the RAN 200 can be the same as the RAN 104 described above and illustrated in Figure 1 . The geographical area covered by the RAN 200 can be divided into cellular regions (cells) that can be uniquely identified by a user equipment (UE) 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 illustrated, each of which can include one or more sectors (not shown). A sector is a sub-region of a cell. All sectors within a cell are served by the same base station. The radio link within a sector can be identified by a single logical identifier belonging to that sector. In a cell divided into sectors, multiple sectors within the cell can be formed by an antenna group, where each antenna is responsible for communicating with UEs in a part of the cell.

[0050] In Figure 2 , two base stations 210 and 212 are shown in cells 202 and 204; and a third base station 214 is shown as controlling a remote radio head (RRH) 216 in cell 206. That is, a base station can have an integrated antenna, or can be connected to an antenna or RRH by a feeder cable. In the illustrated example, cells 202, 204, and 126 can be referred to as macro cells because base stations 210, 212, and 214 support cells with large sizes. Additionally, a base station 218 is shown in small cell 208 (e.g., micro cell, pico cell, femto cell, home base station, home Node B, home evolved Node B, etc.), and the small cell 208 can overlap with one or more macro cells. In this example, cell 208 can be referred to as a small cell because base station 218 supports a cell with a relatively small size. Cell sizing can be done according to system design and component constraints.

[0051] It should be understood that the radio access network 200 may include any number of radio base stations and cells. In addition, relay nodes may be deployed to extend the size or coverage area of a given cell. Base stations 210, 212, 214, 218 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 the same as the base station / scheduling entity 108 described above and illustrated in Figure 1 as explained in

[0052] Figure 2 Further included is a quadcopter or drone 220, which may be configured to act as a base station. That is, in some examples, a cell may not have to be stationary, and the geographical area of a cell may move according to the location of a mobile base station such as quadcopter 220.

[0053] Within the RAN 200, a cell may include UEs that may communicate with one or more sectors of each cell. In addition, each of base stations 210, 212, 214, 218, and 220 may be configured to provide an access point to the core network 102 (see Figure 1 ) for all UEs in the corresponding cell. For example, UEs 222 and 224 may communicate with base station 210; UEs 226 and 228 may communicate with base station 212; UEs 230 and 232 may communicate with base station 214 via RRH 216; UE 234 may communicate with base station 218; and UE 236 may communicate with mobile base station 220. In some examples, UEs 222, 224, 226, 228, 230, 232, 234, 236, 238, 240, and / or 242 may be the same as the UE / scheduled entity 106 described above and illustrated in Figure 1 as explained in

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

[0055] In a further aspect of the RAN 200, sidelink signals may 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) may communicate with each other using peer-to-peer (P2P) or sidelink signals 227 without relaying the communication through a base station (e.g., base station 212). In a further example, UE 238 is illustrated as communicating with UEs 240 and 242. Here, UE 238 may act as a scheduling entity or a primary sidelink device, and UEs 240 and 242 may act as scheduled entities or non-primary (e.g., secondary) sidelink devices. In yet another example, a UE may act as a scheduling entity in a device-to-device (D2D), peer-to-peer (P2P), or vehicle-to-vehicle (V2V) network, and / or a mesh network. In the mesh network example, UEs 240 and 242 may optionally communicate directly with each other in addition to communicating with the scheduling entity 238. Thus, in a wireless communication system having scheduled access to time-frequency resources and having a cellular configuration, P2P configuration, or mesh configuration, a scheduling entity and one or more scheduled entities may utilize the scheduled resources to communicate.

[0056] In the radio access network 200, the ability of a UE to communicate while moving independently of its location is referred to as mobility. The various physical channels between the UE and the radio access network are generally established, maintained, and released under the control of an access and mobility management function (AMF, not illustrated, Figure 1 which is part of the core network 102). In some scenarios, the AMF may include a security context management function (SCMF). The SCMF may manage the security context for both the control plane and user plane functionality, in whole or in part, as well as perform the security anchor function (SEAF) for authentication.

[0057] In various aspects of the present disclosure, the radio access network 200 can utilize DL-based mobility or UL-based mobility to achieve mobility and handover (i.e., the connection of a UE is transferred from one radio channel to another radio channel). In a network configured for DL-based mobility, during a call with a scheduling entity, or at any other time, the UE can monitor various parameters of the signal from its serving cell and various parameters of neighboring cells. Depending on the quality of these parameters, the UE can maintain communication with one or more neighboring cells. During this time, if the UE moves from one cell to another cell, or if the signal quality from a neighboring cell exceeds the signal quality from the serving cell for a given amount of time, the UE can perform a handover or switch from the serving cell to the neighboring (target) cell. For example, the UE 224 (illustrated as a vehicle, but any suitable form of UE can be used) can move from the geographical area corresponding to its serving cell 202 to the geographical area corresponding to the neighbor cell 206. When the signal strength or quality from the neighbor cell 206 exceeds the signal strength or quality of its serving cell 202 for a given amount of time, the UE 224 can transmit a report message indicating this condition to its serving base station 210. In response, the UE 224 can receive a handover command, and the UE can undergo a handover to cell 206.

[0058] In a network configured for UL-based mobility, the UL reference signal from each UE may be used by the network to select a serving cell for each UE. In some examples, base stations 210, 212, and 214 / 216 may broadcast unified synchronization signals (e.g., unified primary synchronization signal (PSS), unified secondary synchronization signal (SSS), and unified physical broadcast channel (PBCH)). UEs 222, 224, 226, 228, 230, and 232 may receive the unified synchronization signals, derive carrier frequency and slot timing from these synchronization signals, and transmit uplink pilots or reference signals in response to the derived timing. The uplink pilot signal transmitted by a UE (e.g., UE 224) may be received concurrently by two or more cells (e.g., base stations 210 and 214 / 216) within the radio access network 200. Each of these cells may measure the strength of the pilot signal, and the radio access network (e.g., one or more of base stations 210 and 214 / 216 and / or a central node within a core network) may determine a serving cell for UE 224. As UE 224 moves in radio access network 200, the network may continue to monitor uplink pilot signals transmitted by UE 224. When the signal strength or quality of the pilot signal measured by a neighboring cell exceeds the signal strength or quality measured by the serving cell, network 200 may handover UE 224 from the serving cell to the neighboring cell with or without notifying UE 224.

[0059] Although the synchronization signal transmitted by base stations 210, 212 and 214 / 216 may be uniform, the synchronization signal may not identify a specific cell, but may identify a zone including multiple cells operating on the same frequency and / or having the same timing. The use of zones in a 5G network or other next generation communication network may implement an uplink-based mobility framework and improve the efficiency of both the UE and the network. Efficiency may be achieved because the number of mobility messages that need to be exchanged between the UE and the network may be reduced.

[0060] In various implementations, the air interface in radio access network 200 may utilize licensed spectrum, unlicensed spectrum, or shared spectrum. Licensed spectrum generally provides exclusive use of a portion of the spectrum by a mobile network operator purchasing a license from a government regulatory agency. Unlicensed spectrum provides shared use of a portion of the spectrum without a government-granted license. Although some technical rules generally still need to be followed to access unlicensed spectrum, any operator or device can obtain access. Shared spectrum can fall between licensed and unlicensed spectrum, where technical rules or restrictions may be required to access the spectrum, but the spectrum may still be shared by multiple operators and / or multiple RATs. For example, the license holder of a portion of licensed spectrum may provide licensed shared access (LSA) to share the spectrum with other parties, e.g., with access obtained using conditions determined by a suitable license holder.

[0061] The air interface in radio access network 200 may utilize one or more duplexing algorithms. Duplexing refers to a point-to-point communication link where both endpoints can communicate with each other in two directions. Full duplex means that both endpoints can communicate with each other simultaneously. Half duplex means that only one endpoint can send information to the other endpoint at a time. In a wireless link, a full duplex channel generally relies on physical isolation of the transmitter and receiver, as well as suitable interference cancellation techniques. Full duplex emulation for a wireless link is typically achieved by utilizing frequency division duplexing (FDD) or time division duplexing (TDD). In FDD, transmissions in different directions operate at different carrier frequencies. In TDD, transmissions in different directions on a given channel are separated from each other using time division multiplexing. That is, at some times, the channel is dedicated to transmission in one direction, and at other times, the channel is dedicated to transmission in the other direction, where the direction can change very quickly, e.g., several times per time slot.

[0062] In some aspects of the present disclosure, the scheduling entity and / or the scheduled entity may be configured for beamforming and / or multiple-input multiple-output (MIMO) techniques. Figure 3 An example of a wireless communication system 300 supporting MIMO is illustrated. In a MIMO system, the transmitter 302 includes multiple transmit antennas 304 (e.g., N transmit antennas), and the receiver 306 includes multiple receive antennas 308 (e.g., M receive antennas). Thus, there are N×M signal paths 310 from the transmit antennas 304 to the receive antennas 308. Each of the transmitter 302 and the receiver 306 may be implemented, for example, in the scheduling entity 108, the scheduled entity 106, or any other suitable wireless communication device.

[0063] The use of such multi-antenna techniques enables a wireless communication system to utilize the spatial domain to support spatial multiplexing, beamforming, and transmit diversity. Spatial multiplexing can be used to simultaneously transmit different data streams (also referred to as layers) on the same time-frequency resources. These data streams can be transmitted to a single UE to increase the data rate or to multiple UEs to increase the overall system capacity, the latter being referred to as multi-user MIMO (MU-MIMO). This is achieved by spatially precoding each data stream (i.e., multiplying these data streams by different weights and phase shifts) and then transmitting each spatially precoded stream on the downlink via multiple transmit antennas. The spatially precoded data streams arrive at the UE(s) with different spatial signatures, which enable each UE to recover one or more data streams intended for that UE. On the uplink, each UE transmits a spatially precoded data stream, which enables the base station to identify the source of each spatially precoded data stream.

[0064] The number of data streams or layers corresponds to the transmission rank. In general, the rank of a MIMO system 300 is limited by the lower of the number of transmit or receive antennas 304 or 308. Additionally, the channel conditions at the UE and other considerations (such as the available resources at the base station) may also affect the transmission rank. For example, the rank assigned to a particular UE on the downlink (and thus, the number of data streams) can be determined based on a rank indicator (RI) transmitted from the UE to the base station. The RI can be determined based on the antenna configuration (e.g., the number of transmit and receive antennas) and the measured signal-to-interference-plus-noise ratio (SINR) on each receive antenna. The RI can indicate, for example, the number of layers that can be supported under the current channel conditions. The base station can use the RI along with resource information (e.g., the available resources and the amount of data to be scheduled for the UE) to assign a transmission rank to the UE.

[0065] In a time-division duplex (TDD) system, the UL and DL are reciprocal, where each uses different time slots of the same frequency bandwidth. Thus, in a TDD system, the base station can assign a rank for DL MIMO transmission based on UL SINR measurements (e.g., based on sounding reference signals (SRS) or other pilot signals transmitted from the UE). Based on the assigned rank, the base station can then transmit CSI-RS using a separate C-RS sequence for each layer to provide multi-layer channel estimation. Based on this CSI-RS, the UE can measure the channel quality across the layers and resource blocks and feedback CQI and RI values to the base station for use in updating the rank and assigning REs for future downlink transmissions.

[0066] In the simplest case, as Figure 3As shown, rank-2 spatial multiplexing transmission on the 2x2 MIMO antenna configuration will transmit one data stream from each transmit antenna 304. Each data stream arrives at each receive antenna 308 along a different signal path 310. The receiver 306 can then use the signals received from each receive antenna 308 to reconstruct these data streams.

[0067] To obtain a low block error rate (BLER) on transmissions over the radio access network 200 while still achieving a very high data rate, channel coding can be used. That is, wireless communication can generally utilize a suitable error-correcting block code. In a typical block code, an information message or sequence is split into code blocks (CBs), and an encoder (e.g., CODEC) at the transmitting device then mathematically adds redundancy to the information message. This redundancy in the encoded information message can be used to increase the reliability of the message, enabling any bit errors that may occur due to noise to be corrected.

[0068] Data coding can be implemented in a variety of ways. In earlier 5G NR specifications, user data was encoded using quasi-cyclic low-density parity-check (LDPC) with two different base graphs: one base graph was used for large code blocks and / or high code rates, and the other base graph was used for other cases. Polar coding based on nested sequences was used to encode control information and the physical broadcast channel (PBCH). For these channels, puncturing, shortening, and repetition were used for rate matching.

[0069] Aspects of the present disclosure can be implemented using any suitable channel code. Various implementations of the scheduling entity 108 and the scheduled entity 106 can include suitable hardware and capabilities (e.g., encoders, decoders, and / or CODECs) to perform wireless communication using one or more of these channel codes.

[0070] The air interface in radio access network 200 can utilize one or more multiplexing and multiple access algorithms to enable simultaneous communication of various devices. For example, the 5G NR specification utilizes orthogonal frequency division multiplexing (OFDM) with cyclic prefix (CP) to provide multiple access for UL transmissions from UEs 222 and 224 to base station 210, and multiplexing for DL transmissions from base station 210 to one or more UEs 222 and 224. Additionally, for UL transmissions, the 5G NR specification provides support for discrete Fourier transform spread OFDM (DFT-s-OFDM) with CP (also known as single carrier FDMA (SC-FDMA)). However, within the scope of the present disclosure, multiplexing and multiple access are not limited to the above schemes, and time division multiple access (TDMA), code division multiple access (CDMA), frequency division multiple access (FDMA), sparse code multiple access (SCMA), resource spreading multiple access (RSMA), or other suitable multiple access schemes can be utilized to provide. Furthermore, multiplexing of DL transmissions from base station 210 to UEs 222 and 224 can be provided using time division multiplexing (TDM), code division multiplexing (CDM), frequency division multiplexing (FDM), orthogonal frequency division multiplexing (OFDM), sparse code multiplexing (SCM), or other suitable multiplexing schemes.

[0071] Reference will be made to Figure 4 the OFDM waveform schematically illustrated in

[0072] to describe various aspects of the present disclosure. Those of ordinary skill in the art should understand that various aspects of the present disclosure can be applied in substantially the same manner as described herein to the DFT-s-OFDMA waveform. That is, although some examples of the present disclosure may focus on OFDM links for clarity, it should be understood that the same principles can also be applied to the DFT-s-OFDMA waveform and other waveforms. Figure 4 depicts an expanded view of an exemplary DL subframe 402, which shows an OFDM resource grid 404. However, as those skilled in the art will readily appreciate, the PHY transmission structure for any particular application may differ from the examples described herein depending on any number of factors. Here, time is in the horizontal direction in terms of OFDM symbols; and frequency is in the vertical direction in terms of subcarriers or tones.

[0073] The resource grid 404 can be used to schematically represent the time-frequency resources for a given antenna port. That is, in a MIMO implementation where multiple antenna ports are available, there can be a corresponding multiple resource grids 404 available for communication. The resource grid 404 is divided into multiple resource elements (REs) 406. An RE (which is 1 subcarrier × 1 symbol) is the smallest discrete part of the time-frequency grid and contains a single complex value representing data from a physical channel or signal. Depending on the modulation utilized in a particular implementation, each RE can represent one or more information bits. In some examples, an RE block can be referred to as a physical resource block (PRB) or more simply as a resource block (RB) 408, which contains any suitable number of contiguous subcarriers in the frequency domain. In one example, an RB can include 12 subcarriers, and this number is independent of the parameter set used. In some examples, depending on the parameter set, an RB can include any suitable number of contiguous OFDM symbols in the time domain. Within this disclosure, it is assumed that a single RB (such as RB 408) fully corresponds to a single communication direction (transmission or reception for a given device).

[0074] A UE generally utilizes only a subset of the resource grid 404. An RB can be the smallest resource unit that can be allocated to a UE. Thus, the more RBs are scheduled for a UE and the higher the modulation scheme selected for the air interface, the higher the data rate of that UE.

[0075] In this illustration, RB 408 is shown as occupying less than the entire bandwidth of subframe 402, with some subcarriers shown above and below RB 408. In a given implementation, subframe 402 can have a bandwidth corresponding to any number of one or more RBs 408. Additionally, in this illustration, RB 408 is shown as occupying less than the entire duration of subframe 402, but this is merely a possible example.

[0076] Each subframe 402 (e.g., a 1 ms subframe) can include one or more contiguous time slots. As an illustrative example, in the example shown in Figure 4 one subframe 402 includes four time slots 410. In some examples, a time slot can be defined according to a specified number of OFDM symbols with a given cyclic prefix (CP) length. For example, a time slot can include 7 or 14 OFDM symbols with a nominal CP. Additional examples can include mini time slots with a shorter duration (e.g., 1, 2, 4, or 7 OFDM symbols). In some cases, these mini time slots can occupy resources scheduled for ongoing time slot transmissions for the same or different UEs to transmit.

[0077] An expanded view of one of these time slots 410 illustrates that the time slot 410 includes a control region 412 and a data region 414. Generally, the control region 412 may carry control channels (e.g., PDCCH), while the data region 414 may carry data channels (e.g., PDSCH or PUSCH). Of course, a time slot may include all DL, all UL, or at least one DL portion and at least one UL portion. Figure 4 The simple structure illustrated in Figure 4 is merely exemplary in nature and different time slot structures may be utilized and may include one or more of each control region and data region.

[0078] Although not illustrated in Figure 4 Figure 4 , the individual REs 406 within an RB 408 may be scheduled to carry one or more physical channels, including control channels, shared channels, data channels, etc. Other REs 406 within the RB 408 may also carry pilots or reference signals. These pilots or reference signals are available for a receiving device to perform channel estimation on the corresponding channel, which may enable coherent demodulation / detection of control and / or data channels within the RB 408.

[0079] In a DL transmission, a transmitting device (e.g., the scheduling entity 108) may allocate one or more REs 406 (e.g., within the control region 412) to carry DL control information 114 to one or more scheduled entities 106, the DL control information 114 including one or more DL control channels that generally carry information from higher layers, such as a physical broadcast channel (PBCH), a physical downlink control channel (PDCCH), etc. Additionally, the DL REs may be allocated to carry DL physical signals, which generally do not carry information from higher layers. These DL physical signals may include a primary synchronization signal (PSS); a secondary synchronization signal (SSS); a demodulation reference signal (DM-RS); a phase-tracking reference signal (PT-RS); a channel state information reference signal (CSI-RS), etc.

[0080] The synchronization signals PSS and SSS (collectively referred to as SS) and in some examples also the PBCH may be transmitted in an SS block, which includes 4 consecutive OFDM symbols numbered in increasing order from 0 to 3 via a time index. In the frequency domain, the SS block may be spread over 240 contiguous subcarriers, where the subcarriers are numbered in increasing order from 0 to 239 via a frequency index. Of course, the present disclosure is not limited to this particular SS block configuration. Within the scope of the present disclosure, other non-limiting examples may utilize more or fewer than two synchronization signals; may include one or more supplementary channels in addition to the PBCH; may omit the PBCH; and / or may use non-consecutive symbols for the SS block.

[0081] The PDCCH may carry downlink control information (DCI) for one or more UEs in a cell. This may include, but is not limited to, power control commands for DL and UL transmissions, scheduling information, grants, and / or RE assignments.

[0082] In UL transmissions, a transmitting device (e.g., the scheduled entity 106) may utilize one or more REs 406 to carry UL control information (UCI) 118. The UCI may originate from a higher layer via one or more UL control channels such as the physical uplink control channel (PUCCH), the physical random access channel (PRACH), etc. to the scheduling entity 108. Additionally, each UL RE may carry a UL physical signal (which generally does not carry information from a higher layer), such as a demodulation reference signal (DM-RS), a phase-tracking reference signal (PT-RS), a sounding reference signal (SRS), etc. In some examples, the control information 118 may include a scheduling request (SR), i.e., a request to cause the scheduling entity 108 to schedule an uplink transmission. Here, in response to the SR transmitted on the control channel 118, the scheduling entity 108 may transmit downlink control information 114, which may schedule resources for an uplink packet transmission.

[0083] The UL control information may also include hybrid automatic repeat request (HARQ) feedback (such as an acknowledgement (ACK) or a negative acknowledgement (NACK)), channel state information (CSI), or any other suitable UL control information. HARQ is a technique well known to those of ordinary skill in the art, where for accuracy, any suitable integrity check mechanism (such as a checksum or a cyclic redundancy check (CRC)) may be utilized, for example, to verify the integrity of a packet transmission at the receiving side. If the integrity of the transmission is confirmed, an ACK may be transmitted, while if not, a NACK may be transmitted. In response to a NACK, the transmitting device may send a HARQ retransmission, which may enable chase combining, incremental redundancy, etc.

[0084] In addition to control information, one or more REs 406 (e.g., within the data region 414) may also be allocated for user data or traffic data. Such traffic may be carried on one or more traffic channels, such as for DL transmissions, it may be carried on the physical downlink shared channel (PDSCH); or for UL transmissions, it may be carried on the physical uplink shared channel (PUSCH).

[0085] To enable a UE to obtain initial access to a cell, the RAN may provide system information (SI) characterizing the cell. The minimum system information (MSI) and other system information (OSI) can be used to provide the system information. The MSI can be broadcast periodically on the cell to provide initial cell access and the most basic information required to obtain any OSI that can be broadcast periodically or sent on demand. In some examples, the MSI can be provided on two different downlink channels. For example, the PBCH can carry the master information block (MIB), while the PDSCH can carry system information block type 1 (SIB1). In the art, SIB1 may be referred to as the remaining minimum system information (RMSI).

[0086] The OSI can include any SI not broadcast in the MSI. In some examples, the PDSCH can carry multiple SIBs, not limited to SIB1 discussed above. Here, the OSI can be provided in these SIBs (such as SIB2 and above).

[0087] Described above and in Figure 1 and Figure 4 The channels or carriers illustrated are not necessarily all the channels or carriers that can be utilized between the scheduling entity 108 and the scheduled entity 106, and one of ordinary skill in the art will recognize that other channels or carriers, such as other traffic, control, and feedback channels, can be utilized in addition to those illustrated.

[0088] These physical channels are generally multiplexed and mapped to transport channels for handling by the media access control (MAC) layer. The transport channels carry information blocks, which are referred to as transport blocks (TBs). The transport block size (TBS) (which can correspond to the number of information bits) can be a controlled parameter based on the modulation and coding scheme (MCS) and the number of RBs in a given transmission.

[0089] Aspects of the present disclosure implement and provide techniques for extending the paging cycle for power saving of communication devices. Various types of communication devices, such as user equipment (UE) and network components (e.g., base stations), can utilize the various aspects to achieve power saving.

[0090] In one aspect, a UE-specific DRX cycle can be negotiated by the non-access stratum (NAS) during the registration procedure. The negotiated DRX cycle can be sent to the UE via the NAS registration acceptance message. The negotiated DRX cycle can be sent to the radio access network (RAN) via next generation (NG) paging for a UE in the RRC_idle state and via the UE context setup / modification message for a UE in the RRC_inactive state.

[0091] Figure 5FIG. 500 is a flowchart illustrating UE - specific paging cycle negotiation. At 508, UE 502 may initially receive a System Information Block type 1 message (SIB1) from gNB 504. The SIB1 may include a default paging cycle (default_Paging_Cycle). Thereafter, at 510, UE 502 may request a UE - specific DRX cycle by sending a registration request message (including the requested DRX cycle) to an Access and Mobility Management Function (AMF) entity 506. At 512, the AMF entity 506 may send a registration acceptance message (including the negotiated DRX cycle) to UE 502. At 514, the AMF entity 506 may then notify the gNB 504 of the negotiated DRX cycle via paging. Thus, at 516, the gNB 504 may continue to page the UE 502 according to the negotiated DRX cycle.

[0092] Figure 6 FIG. 600 is a flowchart illustrating UE - specific paging cycle negotiation for a UE in the RRC_Inactive state. At 610, UE 602 may initially receive a System Information Block type 1 message (SIB1) from gNB 604. The SIB1 may include a default paging cycle (default_Paging_Cycle). Thereafter, at 612, UE 602 may request a UE - specific DRX cycle by sending a registration request message (including the requested DRX cycle) to an Access and Mobility Management Function (AMF) entity 608. At 614, the AMF entity 608 may send a registration acceptance message (including the negotiated DRX cycle) to UE 602. At 616, the AMF entity 608 may then send Core Network (CN) assistance information (including the negotiated DRX cycle) to an anchor gNB 606. At 618, the anchor gNB 618 may send an RRC release message (including the negotiated DRX cycle) to UE 602. At 620, the anchor gNB 606 may then notify the gNB 604 of the negotiated DRX cycle via paging. Thus, at 622, the gNB 604 may continue to page the UE 602 according to the negotiated DRX cycle.

[0093] Figure 7Table 700 is an example encoding of DRX cycle values at the non-access stratum (NAS). As shown, the DRX cycle value can be encoded using bits 4 to 1 of octet 3 (e.g., bitstream {bit 4, bit 3, bit 2, bit 1}). For example, a bitstream with bit values {0, 0, 0, 0} can represent an unspecified DRX cycle value. A bitstream with bit values {0, 0, 0, 1} can represent a DRX cycle parameter T = 32, which is equivalent to 0.32 seconds. A bitstream with bit values {0, 0, 1, 0} can represent a DRX cycle parameter T = 64, which is equivalent to 0.64 seconds. A bitstream with bit values {0, 0, 1, 1} can represent a DRX cycle parameter T = 128, which is equivalent to 1.28 seconds. A bitstream with bit values {0, 1, 1, 0} can represent a DRX cycle parameter T = 256, which is equivalent to 2.56 seconds. A bitstream with bit values {1, 0, 0, 0} can represent a DRX cycle parameter T = 512, which is equivalent to 5.12 seconds. A bitstream with bit values {1, 0, 0, 1} can represent a DRX cycle parameter T = 1024, which is equivalent to 10.24 seconds. A bitstream with bit values other than those above for bits 4 to 1 of octet 3 can represent an unspecified DRX cycle value. Additionally, bits 8 to 5 of octet 3 can be considered spare bits and are encoded as zero.

[0094] It is noted that DRX cycle values greater than 2.56 seconds may not be supported by the NAS protocol. Thus, 5G NR interfaces (such as the NG, Xn, and F1 interfaces) may also not support DRX cycle values greater than 2.56 seconds. Accordingly, to extend the paging DRX cycle, it may be necessary to change the implementation of the NG, Xn, and F1 interfaces. For example, the UE-specific DRX cycle can be changed to extend to 5.12 seconds and / or 10.24 seconds. In another example, the paging cycle in the Xn and NG paging messages can be changed to extend to 5.12 seconds and / or 10.24 seconds.

[0095] In one aspect, when the UE-specific DRX cycle and the default paging cycle are inconsistent, the UE uses the smaller of the two DRX values. This prevents the UE from saving power based on the longer DRX cycle. However, when the longer UE-specific DRX cycle is specifically configured by the AMF, the UE will use the longer UE-specific DRX cycle for paging monitoring.

[0096] In one aspect, the DRX cycle parameter T can be determined as follows. The DRX cycle value T of the UE is determined by the shorter of the UE-specific DRX value (if configured by RRC or upper layers to be less than 512 (5.12 seconds)) and the default DRX value broadcast in the system information. The DRX cycle value T is the UE-specific DRX value if configured by RRC or upper layers to be 512 (5.12 seconds) or 1024 (10.24 seconds). If the UE-specific DRX value is not configured by RRC or upper layers, the DRX cycle value T is the default value.

[0097] In one aspect, when the UE-specific DRX cycle value is configured as 5.12 seconds or 10.24 seconds in the NAS registration procedure or RRC release, the UE uses this UE-specific DRX cycle value as the paging cycle to monitor paging. It is noted that this enhancement does not affect the paging occasion (PO) / paging frame (PF) calculation formula (LTE eDRX-style solution is not required) and thus does not have to be changed. In addition to UE-specific paging triggered by UE services, the RAN also sends non-UE-specific paging for the following: 1) Public Warning System (PWS) / Earthquake and Tsunami Warning System (ETWS), System Information Block (SIB) change, and (future) MCCH change. The PO / PF is shared by these two types of paging.

[0098] In one aspect, when using a longer paging cycle, the PWS / ETWS reception delay may increase. In addition, the AMF is aware of the UE type and performance requirements for PWS / ETWS. Accordingly, when determining / assigning the UE-specific DRX cycle value, the AMF can consider this information. The longer paging cycle can apply to both the RRC_idle state and the RRC_inactive state of the UE. Therefore, the RRC resume message can be extended for longer DRX cycle values. In a further aspect, for a UE in the RRC_inactive state, the RAN paging cycle (ran-PagingCycle) can be extended to 5.12 seconds and / or 10.24 seconds.

[0099] According to some aspects of the present disclosure, the ability of the UE to monitor paging (i.e., paging monitoring or paging surveillance) facilitates the execution of various UE operations. For example, paging monitoring allows the UE to learn about updates to system information (e.g., neighbor configuration, cell configuration, etc.), receive calls (e.g., mobile terminated calls), and receive Public Warning System (PWS) signals (e.g., tsunami, earthquake, and / or amber alerts). It is noted that PWS signals may be life-critical and thus the UE may prefer to receive such signals as soon as possible.

[0100] According to the current 3GPP specifications, the UE monitors paging in each discontinuous reception cycle (DRX cycle). The DRX cycle can be the minimum value among the default paging cycle (defaultPagingCycle), the UE-specific DRX cycle, and the RAN paging cycle (ran-PagingCycle) (DRX cycle = min{defaultPagingCycle, UE-specific DRX cycle, ran-PagingCycle}). The UE-specific DRX cycle can be configured by the non-access stratum (NAS) (e.g., via the registration procedure or radio resource control (RRC) layer release) or a customer-configured value. The RAN paging cycle can be dedicated to the inactive state.

[0101] It is noted that, based on the DRX cycle used, the UE may wake up too frequently (e.g., with short periodicity) to monitor paging. This may cause the UE to unnecessarily consume a large amount of power, but may also increase the opportunity for the UE to receive life-critical PWS signals. Alternatively, based on the DRX cycle used, the UE may wake up less frequently (e.g., with long periodicity) to monitor paging. This may cause the UE to consume less power, but may also cause the UE to miss paging signals including life-critical PWS signals, which is not desirable. Accordingly, the present disclosure provides a novel approach for paging monitoring that balances power savings and PWS signal monitoring.

[0102] In one aspect, the network can configure different DRX cycles and establish rules for the UE to determine the DRX cycle based on the UE type. For example, for a UE capable of receiving PWS signals (i.e., a UE with PWS capability), the network can configure a normal (or relatively short) DRX cycle and allow the UE to monitor paging based on minimum value operation (e.g., monitor paging based on the minimum of the default paging cycle, the RAN paging cycle, and the configured DRX cycle). In another example, for a UE that cannot receive PWS signals (i.e., a UE without PWS capability), the network can configure a relatively long DRX cycle and instruct the UE to monitor paging associated only with the configured DRX cycle rather than minimum value operation.

[0103] In one aspect, the above network operations may involve modifying the 3GPP standard specifications. For example, the maximum paging cycle value can be extended / increased to a value greater than "rf256", i.e., 2.56 seconds. As shown, for example Figure 7 in the 3GPP standard specifications, the paging cycle value can be increased to 5.12 seconds and / or 10.24 seconds.

[0104] In a further aspect, the configuration of different DRX cycles can be affected by location-based information. The location-based information can include Earthquake and Tsunami Warning System (ETWS) information. ETWS information signals are transmitted during rare events such as earthquakes and tsunamis. In addition, certain regions of the world (e.g., Japan) may have a relatively high likelihood of experiencing such events compared to other regions based on typical crust movement patterns which change very slowly.

[0105] The location-based information can also include Cellular Message Alerting System (CMAS) information (e.g., Amber Alert). CMAS information can also depend on the region / carrier as some countries / regions may use such systems while others may not.

[0106] In one aspect, it may be desirable for the network to correctly configure the DRX cycle for "high-risk" regions (e.g., regions with a high probability of transmitting PWS / ETWS information signals). For example, the network can configure a relatively short paging monitoring cycle and / or allow the UE to receive paging based on the minimum paging cycle value among all DRX cycle lengths available to the UE. However, the following problems may still occur: 1) the network may inadvertently misconfigure a long DRX cycle and force the UE to apply that long DRX cycle; and / or 2) while in transit, the UE has not received an updated configuration of a shorter-length DRX cycle and is about to receive a PWS signal.

[0107] In one aspect, the UE can adapt / update its PWS capabilities based on location and the UE's own knowledge. The UE can update its capabilities between "having PWS capabilities" and "not having PWS capabilities" based on: 1) where the UE is located; and / or 2) whether the UE knows that a natural disaster (such as an earthquake or a tsunami) will occur in the near future (e.g., based on a forecast provided by a professional institution / authority). The UE can update its PWS capabilities by performing, for example, NAS registration / capability update procedures.

[0108] In another aspect, the UE can use historical configuration and location information to adapt / update the paging cycle. For example, the UE can store: 1) per-region paging cycle information of the historical configuration; and 2) a set of labeled high-risk regions (e.g., regions with a high probability of earthquakes, tsunamis, etc. or a high probability of transmitting PWS / ETWS information signals). Accordingly, when the UE travels to any high-risk region and the network has not correctly configured the DRX cycle to account for the high-risk region, the UE can choose to receive paging based on the paging cycle value determined by applying the local minimum operation (as described above) or directly applying the paging cycle value of the historical configuration which will have a relatively short length.

[0109] In one aspect, when the UE adapts / updates its PWS capabilities or paging cycle as described above, the UE may use the Public Land Mobile Network (PLMN), Mobile Country Code (MCC), and / or Global Positioning System (GPS) information to identify the area where the UE is located. This is useful when the UE travels across different countries and / or enters or exits high-risk areas.

[0110] According to some aspects of the present disclosure, the gNB may enable / disable the ability to configure / disable the DRX cycle value for the network (e.g., based on the UE's PWS capabilities). The gNB may also enable / disable the UE's ability to adapt / update its PWS capabilities and / or adapt / update its paging cycle. For example, the gNB may enable or disable via the SIB1 message. The gNB capabilities may also be signaled in the SIB1 message, but the gNB capabilities may be separate for inactive (RAN) versus idle (core network) paging. The gNB may notify the user of the enable / disable by sending a SIB update indication that instructs the user to read the SIB1 message. When the ability to configure / adapt / update the paging cycle based on the UE's PWS capabilities is disabled, the UE may start monitoring paging according to the legacy paging cycle (i.e., the minimum of the paging cycle specific to the UE and the default paging cycle).

[0111] In one aspect, the AMF is aware of the UEs camped in the tracking area. Thus, the AMF may notify all gNBs in the tracking area that there are UEs monitoring paging according to a longer cycle. Based on this information, the gNB may broadcast the alert message (PWS / ETWS signal) and SIB update for a longer duration. For example, if the gNB is aware of such UEs, when an earthquake or tsunami occurs, the gNB may send the PWS / ETWS signal for a longer amount of time to increase the probability of the UE receiving the signal.

[0112] In one aspect, configuring / adapting / updating the DRX cycle according to the PWS capabilities is enabled / disabled by the network based on UE support and traffic. Considerations include: 1) the slices supported / requested / allowed; 2) Internet of Things (IoT) devices versus regular UEs; 3) the mobility characteristics of the UE; and 4) other UE requests (e.g., battery savings).

[0113] For core network (CN) paging, when the CN initiates paging (for the entire tracking area), the AMF may notify the gNB of the UE's paging cycle. For RAN paging, when the RAN initiates paging, the anchor gNB may notify the other gNBs in the RAN paging area of the UE's paging cycle. The enable / disable may be performed via the NAS (e.g., registration procedure) and RRC (e.g., RNAU). In the latter case, the gNB notifies the AMF.

[0114] In a further aspect, if the UE-specific DRX cycle is longer than the broadcast control channel (BCCH) modification period, the UE may read a system information block message (e.g., SIB1) upon waking up to determine whether the system information has been updated. If there is any new system information in the system information block message, the UE will update it with the new information.

[0115] In one aspect, if there is no previous record, the UE may derive a paging repetition pattern over a period of time (T_derive). T_derive acts as a timer and may be a predefined and configurable value. For example, T_derive = X seconds. Alternatively, since the UE may require several (or a number of) DRX cycles to derive the paging repetition pattern, T_derive may be based on a number of DRX cycles. For example, T_derive = (N_DRX)*(DRX cycle length / value), where N_DRX is the number of DRX cycles the UE uses to derive the paging repetition pattern. During the period T_derive, the UE may wake up every DRX cycle and determine whether a paging signal is received. Thus, the UE will detect whether a paging signal is received in the first DRX cycle, the second DRX cycle, etc., up to the last DRX cycle before T_derive expires. After a specific number of DRX cycles (e.g., 20 DRX cycles), the UE will have enough information to derive the repetition pattern.

[0116] In one aspect, once the paging repetition pattern is derived, the UE may save power by selectively waking up (less frequently) to monitor for paging instead of waking up every DRX cycle. That is, the UE wakes up only within the DRX cycles in which the UE believes a paging signal will be received according to the paging repetition pattern. The derived paging repetition pattern may be recorded in a database and used for future reference, thus saving further power for the UE as the UE will not have to derive the pattern again.

[0117] In one aspect, the paging repetition pattern of a cell (and a particular network operator) can be saved / recorded / stored in a database in association with different types of information to assist the UE in locating the correct pattern. For example, the paging repetition pattern can be stored in association with cell location, cell identity, mobile country code (MCC), GPS information, network operator, network provider, and / or day / month / year time (since some PWS messages can depend on the season). The database can also store any known network repetition patterns that the UE may have obtained beforehand (e.g., by explicitly querying the network or network operator offline). Notably, if the UE previously knows the network repetition pattern, the UE can significantly reduce the amount of time required to derive the paging repetition pattern. For example, when the UE knows based on the stored network repetition pattern that the paging repetition pattern will repeat every X DRX cycles (e.g., 2 DRX cycles), and thus will only need to spend time determining the starting point of the pattern (e.g., whether the pattern starts in the first DRX cycle, the second DRX cycle, etc.), time is saved. The information stored in the database helps the UE uniquely detect where the UE will likely experience a particular paging repetition pattern when camped on a cell. The more information the UE can access, the more accurate the UE can evaluate what the paging repetition pattern will be from the database.

[0118] Generally, the network can divide the PWS message into multiple segments and send these segments to the UE. Additionally, the sequence number or index of the segments is embedded in the PWS signal itself. Therefore, the UE does not know the sequence number or index of the PWS signal until the PWS signal is decoded. Thus, if the PWS signal has a sequence number or index that the UE has already received or is not interested in receiving, the UE may not have to wake up to receive the PWS signal.

[0119] In one aspect, to avoid waking up the UE unnecessarily to receive unwanted PWS signals, the network can embed the sequence number or index of the PWS signal in the corresponding paging signal transmitted before the PWS signal. Accordingly, when the UE receives a paging signal in which the sequence number or index of the upcoming PWS signal is embedded, the UE can determine its interest in receiving the upcoming PWS signal based on the sequence number or index embedded in the paging signal. If the UE is interested in receiving the upcoming PWS signal based on the sequence number or index of the PWS signal embedded in the paging signal, the UE can wake up to receive the PWS signal. If the UE is not interested in receiving the upcoming PWS signal based on the sequence number or index of the PWS signal embedded in the paging signal, the UE can suppress waking up and forego receiving the PWS signal, which saves power.

[0120] Figure 8is a block diagram illustrating an example of a hardware implementation of a network device 800 employing a processing system 814. For example, the network device 800 can be a scheduling entity, a base station, a gNB, an AMF, or a combination of a gNB and an AMF as illustrated in any one or more of Figure 1 , 2 , 5, and / or 6. Figure 1 , 2 , 5 and / or 6.

[0121] The network device 800 can be implemented with a processing system 814 that includes one or more processors 804. Examples of processors 804 include a microprocessor, a microcontroller, a digital signal processor (DSP), a field programmable gate array (FPGA), a programmable logic device (PLD), 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, the network device 800 can be configured to perform any one or more of the functions described herein. That is, the processor 804 utilized in the network device 800 can be used to implement any one or more of the processes and procedures described below and illustrated in Figure 9 . Figure 9 .

[0122] In this example, the processing system 814 can be implemented with a bus architecture generally represented by bus 802. Depending on the specific application and overall design constraints of the processing system 814, bus 802 can include any number of interconnecting buses and bridges. Bus 802 communicatively couples various circuits including one or more processors (generally represented by processor 804), a memory 805, and a computer-readable medium (generally represented by computer-readable medium 806). Bus 802 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 further herein. A bus interface 808 provides an interface between bus 802 and a transceiver 810. The transceiver 810 provides a communication interface or means for communicating with various other devices over a transmission medium. Depending on the characteristics of the device, a user interface 812 (e.g., keypad, display, speaker, microphone, joystick) can also be provided. Of course, such a user interface 812 is optional and can be omitted in some examples such as a base station.

[0123] In some aspects of the present disclosure, the processor 804 can include a public warning system (PWS) capability determination circuitry 840 configured for various functions including, for example, determining whether a user equipment (UE) is capable of receiving a public warning system (PWS) signal and whether the UE desires to receive the PWS signal over a duration (a specific period of time). For example, the PWS capability determination circuitry 840 can be configured to implement the processes described below with reference to Figure 9 . Figure 9One or more of the described functions, including, for example, block 902. The processor 804 may also include DRX cycle configuration circuitry 842 configured for various functions, including, for example, configuring a discontinuous reception (DRX) cycle value based on the determination. For example, the DRX cycle configuration circuitry 842 may be configured to implement one or more of the functions described with respect to Figure 9 One or more of the described functions, including, for example, block 904. The processor 804 may also include DRX cycle communication circuitry 844 configured for various functions, including, for example, sending a configured DRX cycle value to the UE and the radio access network (RAN). For example, the DRX cycle communication circuitry 844 may be configured to implement one or more of the functions described with respect to Figure 9 One or more of the described functions, including, for example, block 906. The processor 804 may also include paging / PWS signal transmission circuitry 846 configured for various functions, including, for example, sending a paging signal corresponding to the PWS signal to the UE based on the configured DRX cycle value, and sending the PWS signal to the UE. For example, the paging / PWS signal transmission circuitry 846 may be configured to implement one or more of the functions described with respect to Figure 9 One or more of the described functions, including, for example, blocks 908 and 910.

[0124] The processor 804 is responsible for managing the bus 802 and general processing, including the execution of software stored on the computer-readable medium 806. When executed by the processor 804, the software causes the processing system 814 to perform the various functions described below for any particular device. The computer-readable medium 806 and the memory 805 may also be used to store data manipulated by the processor 804 when executing the software.

[0125] One or more processors 804 in the processing system may execute software. 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, executables, threads of execution, procedures, functions, etc., regardless of whether it is referred to in terms of software, firmware, middleware, microcode, hardware description language, or other terms. The software may reside on a computer-readable medium 806. The computer-readable medium 806 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 806 may reside within the processor system 814, outside the processing system 814, or be distributed across multiple entities including the processing system 814. The computer-readable medium 806 may be embodied in a computer program product. By way of example, the computer program product may include a computer-readable medium in a packaging material. Those skilled in the art will recognize how best to implement the described functionality presented throughout this disclosure depending on the particular application and the overall design constraints imposed on the overall system.

[0126] In one or more examples, the computer-readable storage medium 806 may include public warning system (PWS) capability determination instructions 850 configured for various functions, including for example determining whether a user equipment (UE) is capable of receiving a public warning system (PWS) signal and whether the UE desires to receive the PWS signal over a duration (a particular period of time). For example, the PWS capability determination instructions 850 may be configured to implement one or more of the functions described below with reference to Figure 9 including, for example, block 902. The computer-readable storage medium 806 may also include discontinuous reception (DRX) cycle configuration instructions 852 configured for various functions, including for example configuring a discontinuous reception (DRX) cycle value based on the determination. For example, the DRX cycle configuration instructions 852 may be configured to implement one or more of the functions described below with reference to Figure 9 including, for example, block 904. The computer-readable storage medium 806 may also include DRX cycle communication instructions 854 configured for various functions, including for example sending the configured DRX cycle value to the UE and a radio access network (RAN). For example, the DRX cycle communication instructions 854 may be configured to implement one or more of the functions described below with reference toFigure 9 One or more of the described functions, including, for example, block 906. The computer-readable storage medium 806 may also include paging / PWS signaling instructions 856 configured for various functions, including, for example, sending a paging signal corresponding to the PWS signal to the UE based on a configured DRX cycle value, and sending the PWS signal to the UE. For example, the paging / PWS signaling instructions 856 may be configured to implement the following regarding Figure 9 One or more of the described functions, including, for example, blocks 908 and 910.

[0127] Figure 9 Is a flowchart illustrating an exemplary process 900 for wireless communication at a network device in accordance with some aspects of the present disclosure. As described below, some or all of the illustrated features may be omitted in a particular implementation within the scope of the present disclosure, and some of the illustrated features may not be required to implement all embodiments. In some examples, process 900 may be performed by Figure 8 The network entity 800 illustrated in. In some examples, process 900 may be performed by any suitable equipment or device for performing the functions or algorithms described below.

[0128] At block 902, the network device may determine whether a user equipment (UE) is capable of receiving a public warning system (PWS) signal and whether the UE desires to receive the PWS signal over a duration (a particular time period). In one aspect, the determination may include receiving an indication of PWS capability or non-PWS capability from the UE. The determination may further include receiving a delay requirement via the received indication to determine whether the UE desires to receive the PWS signal over the duration. In a further aspect, the indication may request a configured discontinuous reception (DRX) cycle value (e.g., a UE-specific DRX cycle value) from the network device. Additionally, the indication may be received via a non-access stratum (NAS) registration procedure or a capability update procedure.

[0129] At block 904, the network device may configure a discontinuous reception (DRX) cycle value based on the determination. At block 906, the network device may send the configured DRX cycle value to the UE and the radio access network (RAN).

[0130] In one aspect, if the UE is capable of receiving the PWS signal and desires to receive the PWS signal over the duration, the configured DRX cycle value is a first DRX cycle value and the transmission of the configured DRX cycle value indicates to the UE that the UE is allowed to receive paging signals based on the minimum of the first DRX cycle value, a default DRX cycle value (default paging cycle), and a RAN-configured DRX cycle value (RAN paging cycle). In one aspect, the first DRX cycle value may be greater than or equal to 5.12 seconds (e.g., 5.12 seconds or 10.24 seconds).

[0131] In a further aspect, if the UE is unable to receive the PWS signal or does not expect to receive the PWS signal within the duration, the configured DRX cycle value is the second DRX cycle value. Additionally, the transmission of the configured DRX cycle value indicates to the UE that the UE: 1) is not allowed to receive paging signals based on the minimum of the second DRX cycle value, the default DRX cycle value, and the DRX cycle value configured by the RAN; and 2) is to receive paging signals based on the second DRX cycle value. In one aspect, the second DRX cycle value can be greater than or equal to 5.12 seconds (e.g., 5.12 seconds or 10.24 seconds).

[0132] At block 908, the network device may send a paging signal corresponding to the PWS signal to the UE based on the configured DRX cycle value. In one aspect, the network device may include the sequence number or index of the corresponding PWS signal in the paging signal. At block 910, the network may send the PWS signal to the UE.

[0133] In one aspect, when the network device determines whether the UE is able to receive the PWS signal (block 902), the network device may determine that the UE monitors paging according to the established paging duration. Accordingly, the network device may send a paging signal to the UE for a duration that is at least as long as the established paging duration (block 908).

[0134] Figure 9 The processes shown may include additional aspects, such as any single aspect or any combination of aspects described below and / or in connection with one or more other processes described elsewhere in this document.

[0135] In a first aspect, a network device may determine whether a user equipment (UE) is able to receive a public warning system (PWS) signal and whether the UE expects to receive the PWS signal within a duration. The network device may configure a discontinuous reception (DRX) cycle value based on the determination and send the configured DRX cycle value to the UE and the radio access network (RAN). The network device may further send a paging signal corresponding to the PWS signal to the UE based on the configured DRX cycle value.

[0136] In a second aspect, separately or in combination with the first aspect, if the UE is able to receive the PWS signal and expects to receive the PWS signal within the duration, the configured DRX cycle value is the first DRX cycle value and the transmission of the configured DRX cycle value indicates to the UE that the UE is allowed to receive paging signals based on the minimum of the first DRX cycle value, the default DRX cycle value, and the DRX cycle value configured by the RAN.

[0137] In a third aspect, either alone or in combination with one or more of the first and second aspects, if the UE is unable to receive the PWS signal or does not expect to receive the PWS signal within a duration, the configured DRX cycle value is the second DRX cycle value and the transmission of the configured DRX cycle value indicates to the UE that the UE is not allowed to receive paging signals based on the minimum of the second DRX cycle value, the default DRX cycle value, and the RAN-configured DRX cycle value, and that the paging signals are to be received based on the second DRX cycle value.

[0138] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, the network device may determine whether the UE is able to receive the PWS signal by receiving an indication of PWS capability or non-PWS capability from the UE, and may determine whether the UE expects to receive the PWS signal within a duration by receiving a latency requirement via the received indication.

[0139] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the indication requests the configured DRX cycle value from the network device, and the indication is received via a non-access stratum (NAS) registration procedure or a capability update procedure.

[0140] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the network device may determine whether the UE is able to receive the PWS signal by determining whether the UE monitors paging according to an established paging duration, and may transmit paging signals by transmitting paging signals to the UE within a paging duration that is at least as long as the established paging duration.

[0141] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the paging signal includes a sequence number or index of the PWS signal corresponding to the paging signal.

[0142] In one configuration, an apparatus 800 for wireless communication includes: means for determining whether a user equipment (UE) is able to receive a public warning system (PWS) signal and whether the UE expects to receive the PWS signal within a duration, means for configuring a discontinuous reception (DRX) cycle value based on the determination, means for transmitting the configured DRX cycle value to the UE and a radio access network (RAN), means for transmitting a paging signal corresponding to the PWS signal to the UE based on the configured DRX cycle value, and means for transmitting the PWS signal to the UE. In one aspect, the foregoing means may be the processor 804 shown in Figure 8 and is configured to perform the functions recited by the foregoing means. In another aspect, the foregoing means may be a circuit or any apparatus configured to perform the functions recited by the foregoing means.

[0143] Of course, in the above example, the circuitry included in the processor 804 is provided only as an example, and other devices for performing the functions may be included in aspects of the present disclosure, including but not limited to being stored in the computer-readable storage medium 806, or in any other suitable equipment or device described in any one of Figure 1 , 2 , 5, and / or 6 and utilizing instructions for processes and / or algorithms such as those described herein with respect to Figure 9 .

[0144] Figure 10 FIG. is a conceptual diagram illustrating an example of a hardware implementation of an exemplary UE 1000 employing a processing system 1014. According to various aspects of the present disclosure, an element, or any portion of an element, or any combination of elements can be implemented with a processing system 1014 that includes one or more processors 1004. For example, the UE 1000 can be a user equipment (UE) as illustrated in any one or more of Figure 1 , 2 , 5, and / or 6.

[0145] The processing system 1014 can be substantially the same as the processing system 814 illustrated in Figure 8 , including a bus interface 1008, a bus 1002, a memory 1005, a processor 1004, and a computer-readable medium 1006. In addition, the UE 1000 can include a user interface 1012 and a transceiver 1010 that are substantially similar to those user interfaces and transceivers described above in Figure 8 . That is, the processor 1004 utilized in the UE 1000 can be used to implement any one or more of the processes described below and illustrated in Figure 11 .

[0146] In some aspects of the present disclosure, the processor 1004 can include a public warning system (PWS) capability determination circuitry 1040 configured for various functions, including for example determining the ability to receive a PWS signal and / or specifying a delay requirement for whether the UE expects to receive the PWS signal within a duration (a specific time period), and sending an indication of the ability and / or the delay requirement to a network device. For example, the PWS capability determination circuitry 1040 can be configured to implement one or more functions described below with reference to Figure 11 , including for example blocks 1102 and 1104. The processor 1004 can also include a DRX cycle reception circuitry 1042 configured for various functions, including for example receiving a configured discontinuous reception (DRX) cycle associated with the indication from a network device. For example, the DRX cycle reception circuitry 1042 can be configured to implement the following with respect to Figure 11One or more of the described functions, including, for example, block 1106. The processor 1004 may also include paging signal receiving circuitry 1044 configured for various functions, including, for example, receiving a paging signal corresponding to the PWS signal from a network device (e.g., associated with a configured DRX cycle value). For example, the paging signal receiving circuitry 1044 may be configured to implement one or more of the functions described with respect to Figure 11 One or more of the described functions, including, for example, block 1108. The processor 1004 may also include PWS signal receiving circuitry 1046 configured for various functions, including, for example, receiving a PWS signal from a network device. Additionally, if the paging signal includes a sequence number or index of the PWS signal corresponding to the paging signal, the PWS signal receiving circuitry 1046 may also be configured to determine whether to receive the PWS signal based on the sequence number or index included in the paging signal, wake up to receive the PWS signal if it is determined to receive the PWS signal based on the sequence number or index, and suppress waking up to receive the PWS signal if it is determined not to receive the PWS signal based on the sequence number or index. For example, the PWS signal receiving circuitry 1046 may be configured to implement one or more of the functions described below with reference to Figure 11 One or more of the described functions, including, for example, blocks 1110, 1112, 1114, and 1116.

[0147] In one or more examples, the computer-readable storage medium 1006 may include public warning system (PWS) capability determination instructions 1050 configured for various functions, including, for example, determining the ability to receive a PWS signal and / or specifying a delay requirement for indicating whether the UE expects to receive the PWS signal over a duration (a specific time period), and sending an indication of the ability and / or the delay requirement to a network device. For example, the PWS capability determination instructions 1050 may be configured to implement one or more of the functions described below with reference to Figure 11 One or more of the described functions, including, for example, blocks 1102 and 1104. The computer-readable storage medium 1006 may also include DRX cycle reception instructions 1052 configured for various functions, including, for example, receiving a configured discontinuous reception (DRX) cycle value associated with the indication from a network device. For example, the DRX cycle reception instructions 1052 may be configured to implement one or more of the functions described with respect to Figure 11 One or more of the described functions, including, for example, block 1106. The computer-readable storage medium 1006 may also include paging signal reception instructions 1054 configured for various functions, including, for example, receiving a paging signal corresponding to the PWS signal from a network device (e.g., associated with a configured DRX cycle value). For example, the paging signal reception instructions 1054 may be configured to implement one or more of the functions described with respect to Figure 11One or more of the described functions, including, for example, block 1108. The computer-readable storage medium 1006 may also include PWS signal reception instructions 1056 configured for various functions, including, for example, receiving a PWS signal from a network device. Additionally, if the paging signal includes a sequence number or index of the PWS signal corresponding to the paging signal, the PWS signal reception instructions 1056 may also be configured to determine whether to receive the PWS signal based on the sequence number or index included in the paging signal, wake up to receive the PWS signal if it is determined to receive the PWS signal based on the sequence number or index, and suppress waking up to receive the PWS signal if it is determined not to receive the PWS signal based on the sequence number or index. For example, the PWS signal reception instructions 1056 may be configured to implement one or more of the functions described below with reference to Figure 11 One or more of the described functions, including, for example, blocks 1110, 1112, 1114, and 1116.

[0148] Figure 11 is a flowchart illustrating an exemplary process 1100 for wireless communication at a user equipment (UE) in accordance with some aspects of the present disclosure. As described below, some or all of the illustrated features may be omitted in a particular implementation within the scope of the present disclosure, and some of the illustrated features may not be required to implement all embodiments. In some examples, process 1100 may be performed by Figure 10 the UE 1000 illustrated in. In some examples, process 1100 may be performed by any suitable equipment or device for performing the functions or algorithms described below.

[0149] At block 1102, the UE may determine the ability to receive a Public Warning System (PWS) signal and / or specify a delay requirement that indicates whether the UE expects to receive the PWS signal over a duration (a particular time period). In one aspect, the delay requirement signals whether the UE is configured (or not configured) to receive the PWS signal during a time window. In one aspect, the PWS ability and / or delay requirement may be determined based on the region in which the UE is located (e.g., a geographical region) and / or the UE's knowledge of an event that may prompt the transmission of a PWS signal (e.g., an earthquake, a tsunami, etc.). For example, the region may be determined using Public Land Mobile Network (PLMN), Mobile Country Code (MCC), and / or Global Positioning System (GPS) information.

[0150] At block 1104, the UE may send an indication to the network device indicating the ability to receive the PWS signal and / or the delay requirement. In one aspect, the indication may request a configured discontinuous reception (DRX) cycle value (e.g., a UE-specific DRX cycle value) from the network device. Additionally, the indication may be sent via a non-access stratum (NAS) registration procedure or a capability update procedure.

[0151] At block 1106, the UE may receive a configured discontinuous reception (DRX) cycle value associated with the indication from a network device. At block 1108, the UE may receive a paging signal corresponding to the PWS signal associated with the configured DRX cycle value from the network device.

[0152] In one aspect, to receive the paging signal, the UE may determine that the UE is located in an area at risk of an event that triggers PWS signal transmission (e.g., an area with a high probability of earthquake, tsunami, etc.), update the configured DRX cycle value with a historical configured DRX cycle value associated with the area, and receive the paging signal from the network device based on the updated DRX cycle value.

[0153] In another aspect, to receive the paging signal, the UE may determine that the UE is located in an area at risk of an event that triggers PWS signal transmission, and when the UE is able to receive the PWS signal and the latency requirement specifies that the UE expects to receive the PWS signal within a duration, receive the paging signal based on the minimum of the configured DRX cycle value, the default DRX cycle value (default paging cycle), and the radio access network (RAN)-configured DRX cycle value (RAN paging cycle). Here, the configured DRX cycle value may be greater than or equal to 5.12 seconds (e.g., 5.12 seconds or 10.24 seconds).

[0154] In a further aspect, to receive the paging signal, the UE may derive a paging repetition pattern over the duration of N configured DRX cycle values, where N is an integer greater than or equal to 1, selectively wake up to receive the paging signal based on the derived paging repetition pattern, and store the derived paging repetition pattern in a database.

[0155] In another aspect, if the UE cannot receive the PWS signal or the latency requirement specifies that the UE does not expect to receive the PWS signal within a duration, receiving the configured DRX cycle value indicates to the UE that: 1) it is not allowed to receive the paging signal based on the minimum of the configured DRX cycle value, the default DRX cycle value, and the RAN-configured DRX cycle value; and 2) it is to receive the paging signal based on the configured DRX cycle value. Here, the configured DRX cycle value may be greater than or equal to 5.12 seconds (e.g., 5.12 seconds or 10.24 seconds).

[0156] At block 1110, the UE may receive the PWS signal from the network device.

[0157] In one aspect, a paging signal (received at block 1108) may include a sequence number or index of a PWS signal corresponding to the paging signal. Accordingly, at block 1112, the UE may determine whether to receive the PWS signal based on the sequence number or index included in the paging signal. At block 1114, if it is determined based on the sequence number or index to receive the PWS signal, the UE may wake up to receive the PWS signal. At block 1116, if it is determined based on the sequence number or index not to receive the PWS signal, the UE may refrain from waking up to receive the PWS signal.

[0158] Figure 11 The processes shown may include additional aspects, such as any individual aspect or any combination of aspects described below and / or in connection with one or more other processes described elsewhere herein.

[0159] In a first aspect, the UE may send an indication to the network device indicating at least one of the ability to receive a Public Warning System (PWS) signal or a delay requirement specifying whether the UE expects to receive the PWS signal over a duration (e.g., the delay requirement signals that the UE is configured (or not configured) to receive the PWS signal during a time window). The UE may receive a configured discontinuous reception (DRX) cycle value associated with the indication from the network device. The UE may also receive a paging signal corresponding to the PWS signal associated with the configured DRX cycle value from the network device.

[0160] In a second aspect, either alone or in combination with the first aspect, the UE may determine at least one of the ability to receive the PWS signal or the delay requirement based on at least one of the area in which the UE is located or the UE's knowledge of an event that would prompt transmission of the PWS signal.

[0161] In a third aspect, either alone or in combination with one or more of the first and second aspects, the indication requests a configured DRX cycle value from the network device, and the indication is received via a non-access stratum (NAS) registration procedure or a capability update procedure.

[0162] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, the UE may receive the paging signal by determining that the UE is located in an area at risk of an event that would prompt transmission of the PWS signal, updating the configured DRX cycle value with a historical configured DRX cycle value associated with the area, and receiving the paging signal from the network device based on the updated DRX cycle value.

[0163] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the UE may receive the paging signal by determining that the UE is in a region at risk of an event where a PWS signal transmission occurs, and when the UE is able to receive the PWS signal and the latency requirement specifies that the UE expects to receive the PWS signal within a duration, receiving the paging signal based on the minimum of the configured DRX cycle value, the default DRX cycle value, and the radio access network (RAN)-configured DRX cycle value.

[0164] In a sixth aspect, either alone or in combination with one or more of the first to fifth aspects, if the UE is unable to receive the PWS signal or the latency requirement specifies that the UE does not expect to receive the PWS signal within a duration, receiving an indication from the configured DRX cycle value that the UE is not allowed to receive the paging signal based on the minimum of the configured DRX cycle value, the default DRX cycle value, and the radio access network (RAN)-configured DRX cycle value, and that the UE is to receive the paging signal based on the configured DRX cycle value.

[0165] In a seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the UE may receive the paging signal by deriving a paging repetition pattern over the durations of N configured DRX cycle values, where N is an integer greater than or equal to 1, selectively waking up to receive the paging signal based on the derived paging repetition pattern, and storing the derived paging repetition pattern in a database.

[0166] In an eighth aspect, either alone or in combination with one or more of the first to seventh aspects, when the paging signal includes a sequence number or index of the PWS signal corresponding to the paging signal, the UE may determine whether to receive the PWS signal based on the sequence number or index included in the paging signal, wake up to receive the PWS signal if it is determined based on the sequence number or index to receive the PWS signal, and suppress waking up for receiving the PWS signal if it is determined based on the sequence number or index not to receive the PWS signal.

[0167] In one configuration, an apparatus 1000 for wireless communication includes: means for determining the ability to receive a Public Warning System (PWS) signal and / or specifying a latency requirement for indicating whether the UE expects to receive the PWS signal over time; means for sending an indication of the ability to receive the PWS signal and / or the latency requirement to a network device; means for receiving a configured discontinuous reception (DRX) cycle value associated with the indication from the network device; means for receiving a paging signal corresponding to the PWS signal associated with the configured DRX cycle value from the network device; means for receiving the PWS signal from the network device; and if the paging signal includes a sequence number or index corresponding to the PWS signal of the paging signal, includes: means for determining whether to receive the PWS signal based on the sequence number or index included in the paging signal; means for waking up to receive the PWS signal if it is determined based on the sequence number or index that the PWS signal is to be received; and means for suppressing waking up to receive the PWS signal if it is determined based on the sequence number or index that the PWS signal is not to be received. In one aspect, the foregoing means may be the processor 1004 shown in Figure 10 and configured to perform the functions recited by the foregoing means. In another aspect, the foregoing means may be a circuit or any apparatus configured to perform the functions recited by the foregoing means.

[0168] Of course, in the above example, the circuitry included in the processor 1004 is provided by way of example only, and other means for performing the described functions may be included within aspects of the present disclosure, including but not limited to being stored in a computer-readable storage medium 1006, or in any other suitable apparatus or device described in Figure 1 、 2 、5 and / or 6 and utilizing instructions for processes and / or algorithms such as those described herein with respect to Figure 11 .

[0169] Several 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.

[0170] As an example, various aspects can be implemented within other systems defined by 3GPP, such as Long Term Evolution (LTE), Evolved Packet System (EPS), Universal Mobile Telecommunications System (UMTS), and / or Global System for Mobile Communications (GSM). Various aspects can 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 can be implemented within systems employing IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Ultra-Wideband (UWB), Bluetooth, and / or other suitable systems. The actual telecommunications standards, network architectures, and / or communication standards employed will depend on the specific application and the overall design constraints imposed on the system.

[0171] Within 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 superior or better than 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 can still be considered to be coupled to each other—even if they are not in direct physical contact with each other. For example, a first object can 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 and software implementations of information and instructions that, when connected and configured, enable the functions described in this disclosure without limitation as to the type of electronic circuit, and that, when executed by a processor, enable the functions described in this disclosure.

[0172] Figure 1-11 One or more of the components, steps, features, and / or functions illustrated therein can be rearranged and / or combined into a single component, step, feature, or function, or implemented in several components, steps, or functions. Additional elements, components, steps, and / or functions can also be added without departing from the novel features disclosed herein. Figure 1-11 The apparatus, devices, and / or components illustrated therein can be configured to perform one or more of the methods, features, or steps described herein. The novel algorithms described herein can also be efficiently implemented in software and / or embedded in hardware.

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

[0174] 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 general principles defined herein may 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 recitation of a singular element is not intended to mean "one and only one" - unless specifically so stated - but rather "one or more." The term "some / a" refers to one or more unless specifically stated otherwise. The phrase reciting "at least one of" a list of items refers to any combination of those items, including a single member. As an example, "at least one of 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. Elements of the various aspects described throughout this disclosure that are presently known or later come to be known to those of ordinary skill in the art as structural and functional equivalents are expressly incorporated herein by reference and are intended to be covered by the claims. Moreover, nothing disclosed herein is intended to be dedicated to the public, whether or not such disclosure is explicitly recited in the claims.

Claims

1. A method for wireless communication at a user equipment (UE), comprising: Sending an indication to a network device indicating at least one of the ability to receive a Public Warning System (PWS) signal or a delay requirement specifying whether the UE expects to receive the PWS signal within a duration; Receiving, from the network device, a configured discontinuous reception (DRX) cycle value associated with the indication; And Receiving, from the network device, a paging signal corresponding to the PWS signal associated with the configured DRX cycle value, wherein receiving the paging signal comprises: Determining that the UE is located in an area at risk of an event occurring that prompts transmission of the PWS signal; Updating the configured DRX cycle value with a historical configured DRX cycle value associated with the area; and Receiving the paging signal from the network device based on the updated DRX cycle value.

2. The method according to claim 1, further comprising determining at least one of the ability to receive the PWS signal or the delay requirement based on at least one of: The area in which the UE is located; or The UE's knowledge of whether an event will occur that prompts transmission of the PWS signal.

3. The method according to claim 1, wherein: The indication requests the configured DRX cycle value from the network device; and Sending the indication comprises sending via a non-access stratum (NAS) registration procedure or a capability update procedure.

4. The method according to claim 1, wherein if the UE cannot receive the PWS signal or the delay requirement specifies that the UE does not expect to receive the PWS signal within a duration, receiving the configured DRX cycle value indicates to the UE: Not being allowed to receive the paging signal based on the minimum of the configured DRX cycle value, a default DRX cycle value, and a radio access network (RAN)-configured DRX cycle value; and To receive the paging signal based on the configured DRX cycle value.

5. The method according to claim 1, wherein receiving the paging signal comprises: Deriving a paging repetition pattern over a duration of N configured DRX cycle values, where N is an integer greater than or equal to 1; Selectively waking up to receive the paging signal based on the derived paging repetition pattern; And Storing the derived paging repetition pattern in a database.

6. The method according to claim 1, wherein the paging signal includes a sequence number or index of the PWS signal corresponding to the paging signal, the method further comprising: Determining whether to receive the PWS signal based on the sequence number or index included in the paging signal; If it is determined based on the sequence number or index that the PWS signal is to be received, waking up to receive the PWS signal; And If it is determined based on the sequence number or index that the PWS signal is not to be received, suppressing waking up for receiving the PWS signal.

7. A user equipment (UE) for wireless communication, comprising: At least one processor; A transceiver communicatively coupled to the at least one processor; And A memory communicatively coupled to the at least one processor and the transceiver, wherein the transceiver is configured to: Send an indication to a network device indicating at least one of an ability to receive a Public Warning System (PWS) signal or a latency requirement specifying whether the UE expects to receive the PWS signal within a duration, Receive a configured discontinuous reception (DRX) cycle value associated with the indication from the network device, and Receive a paging signal corresponding to the PWS signal associated with the configured DRX cycle value from the network device, wherein the transceiver configured to receive the paging signal is further configured to: Determine that the UE is located in an area at risk of an event occurring that prompts transmission of the PWS signal; Update the configured DRX cycle value with a historical configured DRX cycle value associated with the area; And Receive the paging signal from the network device based on the updated DRX cycle value.

8. The UE of claim 7, wherein the transceiver is further configured to determine at least one of the ability to receive the PWS signal or the latency requirement based on at least one of: The area in which the UE is located; or The UE's knowledge of whether an event that prompts transmission of the PWS signal will occur.

9. The UE of claim 7, wherein: The indication requests the configured DRX cycle value from the network device; and The transceiver is configured to send the indication via a non-access stratum (NAS) registration procedure or a capability update procedure.

10. The UE of claim 7, wherein if the UE is unable to receive the PWS signal or the latency requirement specifies that the UE does not expect to receive the PWS signal within a duration, receiving the configured DRX cycle value indicates to the UE: Not to be allowed to receive the paging signal based on the minimum of the configured DRX cycle value, the default DRX cycle value, and the radio access network (RAN)-configured DRX cycle value; and To receive the paging signal based on the configured DRX cycle value.

11. The UE of claim 7, wherein the transceiver configured to receive the paging signal is further configured to: Derive a paging repetition pattern over a duration of N configured DRX cycle values, where N is an integer greater than or equal to 1; Selectively wake up to receive the paging signal based on the derived paging repetition pattern; And Store the derived paging repetition pattern in a database.

12. The UE of claim 7, wherein the paging signal includes a sequence number or index of the PWS signal corresponding to the paging signal, and the transceiver is further configured to: Determine whether to receive the PWS signal based on the sequence number or index included in the paging signal; If it is determined based on the sequence number or index that the PWS signal is to be received, wake up to receive the PWS signal; and If it is determined based on the sequence number or index that the PWS signal is not to be received, suppress waking up to receive the PWS signal.

13. A method for wireless communication at a network device, comprising: determining whether a user equipment (UE) is capable of receiving a public warning system (PWS) signal and whether the UE expects to receive the PWS signal within a duration; configuring a discontinuous reception (DRX) cycle value based on the determination; sending the configured DRX cycle value to the UE and a radio access network (RAN); configuring the UE to update the configured DRX cycle value with a historical configured DRX cycle value for a paging signal corresponding to the PWS signal when the UE is in an area that indicates a risk of transmission of the PWS signal; and sending, based on the configured DRX cycle value, a paging signal corresponding to the PWS signal to the UE.

14. The method according to claim 13, wherein if the UE is capable of receiving the PWS signal and expects to receive the PWS signal within the duration, then: the configured DRX cycle value is a first DRX cycle value; and sending the configured DRX cycle value indicates to the UE that the UE is allowed to receive the paging signal based on the minimum of the first DRX cycle value, a default DRX cycle value, and a DRX cycle value configured by the RAN.

15. The method according to claim 14, wherein if the UE is not capable of receiving the PWS signal or does not expect to receive the PWS signal within the duration, then: the configured DRX cycle value is a second DRX cycle value; and sending the configured DRX cycle value indicates to the UE that the UE: is not allowed to receive the paging signal based on the minimum of the second DRX cycle value, the default DRX cycle value, and the DRX cycle value configured by the RAN, and is to receive the paging signal based on the second DRX cycle value.

16. The method according to claim 13, wherein: determining whether the UE is capable of receiving the PWS signal includes receiving an indication of PWS capability or non-PWS capability from the UE; and determining whether the UE expects to receive the PWS signal within the duration includes receiving a delay requirement via the received indication.

17. The method according to claim 16, wherein: the indication requests the configured DRX cycle value from the network device; and the indication is received via a non-access stratum (NAS) registration procedure or a capability update procedure.

18. The method according to claim 13, wherein: determining whether the UE is capable of receiving the PWS signal includes determining whether the UE monitors paging according to an established paging duration; and sending the paging signal includes sending the paging signal to the UE for a paging duration that is at least as long as the established paging duration.

19. The method according to claim 17, wherein the paging signal includes a sequence number or index of the PWS signal corresponding to the paging signal.

20. A network device for wireless communication, comprising: at least one processor; a transceiver communicatively coupled to the at least one processor; and A memory communicatively coupled to the at least one processor and the transceiver, wherein the transceiver is configured to: Determine whether a user equipment (UE) is capable of receiving a Public Warning System (PWS) signal and whether the UE expects to receive the PWS signal within a duration; Configure a discontinuous reception (DRX) cycle value based on the determination; Send the configured DRX cycle value to the UE and a radio access network (RAN); Configure the UE to update the configured DRX cycle value with a historical configured DRX cycle value for a paging signal corresponding to the PWS signal when the UE is in an area that indicates a risk of transmission of the PWS signal; and Send a paging signal corresponding to the PWS signal to the UE based on the configured DRX cycle value.

21. The network device according to claim 20, wherein if the UE is capable of receiving the PWS signal and expects to receive the PWS signal within a duration, then: The configured DRX cycle value is a first DRX cycle value; and Sending the configured DRX cycle value indicates to the UE that the UE is allowed to receive the paging signal based on the minimum of the first DRX cycle value, a default DRX cycle value, and a DRX cycle value configured by the RAN.

22. The network device according to claim 21, wherein if the UE is not capable of receiving the PWS signal or does not expect to receive the PWS signal within a duration, then: The configured DRX cycle value is a second DRX cycle value; and Sending the configured DRX cycle value indicates to the UE that: The UE is not allowed to receive the paging signal based on the minimum of the second DRX cycle value, the default DRX cycle value, and the DRX cycle value configured by the RAN, and The UE is to receive the paging signal based on the second DRX cycle value.

23. The network device according to claim 20, wherein: The transceiver configured to determine whether the UE is capable of receiving the PWS signal is further configured to receive an indication of PWS capability or non-PWS capability from the UE; And The transceiver configured to determine whether the UE expects to receive the PWS signal within a duration is further configured to receive a delay requirement via the received indication.

24. The network device according to claim 23, wherein: The indication requests the configured DRX cycle value from the network device; and The indication is received via a non-access stratum (NAS) registration procedure or a capability update procedure.

25. The network device according to claim 20, wherein: The transceiver configured to determine whether the UE is capable of receiving the PWS signal is further configured to determine that the UE monitors paging according to an established paging duration; and The transceiver configured to send the paging signal is further configured to send the paging signal to the UE for at least as long as the established paging duration.

26. The network device according to claim 21, wherein the paging signal includes a sequence number or index of the PWS signal corresponding to the paging signal.

27. A method for wireless communication at a user equipment (UE), comprising: sending an indication to a network device indicating at least one of an ability to receive a public warning system (PWS) signal or a latency requirement specifying whether the UE expects to receive the PWS signal within a duration; receiving a configured discontinuous reception (DRX) cycle value associated with the indication from the network device; and receiving a paging signal corresponding to the PWS signal associated with the configured DRX cycle value from the network device, wherein receiving the paging signal includes: determining that the UE is located in an area at risk of an event occurring that triggers transmission of the PWS signal; and when the UE is capable of receiving the PWS signal and the latency requirement specifies that the UE expects to receive the PWS signal within a duration, receiving the paging signal based on the minimum of the configured DRX cycle value, a default DRX cycle value, and a radio access network (RAN)-configured DRX cycle value.

28. A user equipment (UE) for wireless communication, comprising: at least one processor; a transceiver communicatively coupled to the at least one processor; and a memory communicatively coupled to the at least one processor and the transceiver, wherein the transceiver is configured to: send an indication to a network device indicating at least one of an ability to receive a public warning system (PWS) signal or a latency requirement specifying whether the UE expects to receive the PWS signal within a duration, receive a configured discontinuous reception (DRX) cycle value associated with the indication from the network device, and receive a paging signal corresponding to the PWS signal associated with the configured DRX cycle value from the network device, wherein the transceiver configured to receive the paging signal is further configured to: determine that the UE is located in an area at risk of an event occurring that triggers transmission of the PWS signal; and when the UE is capable of receiving the PWS signal and the latency requirement specifies that the UE expects to receive the PWS signal within a duration, receive the paging signal based on the minimum of the configured DRX cycle value, a default DRX cycle value, and a radio access network (RAN)-configured DRX cycle value.

Images