WO2017173158A1

WO2017173158A1 - Radio access network (ran)-originated paging messaging

Info

Publication number: WO2017173158A1
Application number: PCT/US2017/025164
Authority: WO
Inventors: Richard Burbidge; Sudeep Palat; Alexandre Stojanovski; Sangeetha Bangolae; Marta MARTINEZ TARRADELL; Mo-Han Fong; Youn Hyoung Heo
Original assignee: Intel IP Corporation
Priority date: 2016-04-01
Filing date: 2017-03-30
Publication date: 2017-10-05
Also published as: HK1258369A1; CN108702732B; CN108702732A

Abstract

Technology for a base station is disclosed. The base station can determine radio access network (RAN)-based UE paging parameters for configuration of a UE when the UE is in a suspended state. UE context information for the UE can be stored in a memory of the base station when the UE is in the suspended state. The base station can encode the RAN-based UE paging parameters for transmission to the UE directly or via a core network (CN) node. The base station can generate a RAN-originated paging message for the UE when downlink data is received at the base station for the UE. The base station can encode the RAN-originated paging message for transmission to the UE. The RAN-originated paging message can be transmitted from the base station and received at the UE in accordance with the RAN-based UE paging parameters.

Description

RADIO ACCESS NETWORK (RAN)-ORIGINATED

PAGING MESSAGING

BACKGROUND

[0001] Wireless mobile communication technology uses various standards and protocols to transmit data between a node (e.g., a transmission station) and a wireless device (e.g., a mobile device). Some wireless devices communicate using orthogonal frequency-division multiple access (OFDMA) in a downlink (DL) transmission and single carrier frequency division multiple access (SC-FDMA) in uplink (UL). Standards and protocols that use orthogonal frequency-division multiplexing (OFDM) for signal transmission include the third generation partnership project (3 GPP) long term evolution (LTE) Release 8, 9, 10, 11, 12 and 13, the Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard (e.g., 802.16e, 802.16m), which is commonly known to industry groups as WiMAX (Worldwide interoperability for Microwave Access), and the IEEE 802.11 standard, which is commonly known to industry groups as WiFi.

[0002] In 3GPP radio access network (RAN) LTE systems (e.g., Release 13 and earlier), the node can be a combination of Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node Bs (also commonly denoted as evolved Node Bs, enhanced Node Bs, eNodeBs, or eNBs) and Radio Network Controllers (RNCs), which communicates with the wireless device, known as a user equipment (UE). The downlink (DL) transmission can be a communication from the node (e.g., eNodeB) to the wireless device (e.g., UE), and the uplink (UL) transmission can be a communication from the wireless device to the node.

BRIEF DESCRIPTION OF THE DRAWINGS

[0003] Features and advantages of the disclosure will be apparent from the detailed description which follows, taken in conjunction with the accompanying drawings, which together illustrate, by way of example, features of the disclosure; and, wherein:

[0004] FIG. 1 illustrates a wireless communication system in accordance with an example; [0005] FIG. 2 illustrates signaling between an eNodeB and a user equipment (UE) for paging in accordance with an example;

[0006] FIG. 3 is a flowchart illustrating operations for performing paging between an eNodeB and a user equipment (UE) in accordance with an example;

[0007] FIG. 4 depicts functionality of a base station operable to provide paging messages to a user equipment (UE) in accordance with an example;

[0008] FIG. 5 depicts functionality of a user equipment (UE) operable to decode paging messages received from a base station in accordance with an example;

[0009] FIG. 6 depicts a flowchart of a machine readable storage medium having instructions embodied thereon for providing paging messages from a node to a user equipment (UE) in accordance with an example;

[0010] FIG. 7 illustrates an architecture of a wireless network in accordance with an example;

[0011] FIG. 8 illustrates a diagram of a wireless device (e.g., UE) in accordance with an example;

[0012] FIG. 9 illustrates interfaces of baseband circuitry in accordance with an example; and

[0013] FIG. 10 illustrates a diagram of a wireless device (e.g., UE) in accordance with an example.

[0014] Reference will now be made to the exemplary embodiments illustrated, and specific language will be used herein to describe the same. It will nevertheless be understood that no limitation of the scope of the technology is thereby intended.

DETAILED DESCRIPTION

[0015] Before the present technology is disclosed and described, it is to be understood that this technology is not limited to the particular structures, process actions, or materials disclosed herein, but is extended to equivalents thereof as would be recognized by those ordinarily skilled in the relevant arts. It should also be understood that terminology employed herein is used for the purpose of describing particular examples only and is not intended to be limiting. The same reference numerals in different drawings represent the same element. Numbers provided in flow charts and processes are provided for clarity in illustrating actions and operations and do not necessarily indicate a particular order or sequence.

EXAMPLE EMBODIMENTS

[0016] An initial overview of technology embodiments is provided below and then specific technology embodiments are described in further detail later. This initial summary is intended to aid readers in understanding the technology more quickly but is not intended to identify key features or essential features of the technology nor is it intended to limit the scope of the claimed subject matter.

[0017] FIG. 1 illustrates an exemplary wireless communication system 100. The wireless communication system 100 can be an LTE wireless communication system. The wireless communication system 100 can include mobility management entities (MMEs) / serving gateways (S-GWs) 102, 104. The wireless communication system can include eNodeBs 106, 108, 110 in an E-UTRAN 112. The MMEs / S-GWs 102, 104 can each be connected to the eNodeBs 106, 108, 110 over an SI interface. Each of the eNodeBs 106, 108, 110 can be connected to each other over an X2 interface. The eNodeBs 106, 108, 110 can be connected to one or more user equipment (UE) 114 over an Uu interface.

[0018] In one configuration, the wireless communication system 100 can support fifth generation (5G/) new radio (NR) capabilities. In this configuration, the MMEs / S-GWs 102, 104 can be referred to as next generation-control plane / user plane gateways (NG- CP/UPGW), the eNodeBs 106, 108, 110 can be referred to as enhanced LTE (eLTE) eNBs or gNBs. The eLTE eNBs or gNBs can be connected to each other over an Xn interface.

[0019] In one configuration, the wireless communication system 100 can support a reduced bandwidth or narrowband, new radio access technologies/networks (RAT/RAN) and/or new core networks (CN).

[0020] In one configuration, in LTE, the UE 114 can be in a radio resource control (RRC) connected state or an RRC idle state. In the RRC connected state, the UE 114 and an eNodeB 106 have a UE context that stores a current RAN configuration for the UE 114, which can be used for communication between the UE 114 and the eNodeB 106 (or network). In one example, when the UE 114 has no data to send, the UE 114 can be moved to the RRC idle state and the UE context in the eNodeB 106 can be released. Upon the transition to the RRC idle state and the release of the UE context, the UE 114 may not communicate with the eNodeB 106 (or network).

[0021] In one example, when the UE 114 is in the RRC idle state and there is data to be exchanged between the UE 114 and the eNodeB 106 (or network), the UE 114 can transition to the RRC connected state in order to exchange the data. During this connection establishment process, the UE context (with a current RAN configuration for the UE 114) can be established in the eNodeB 106 and the UE 114. The establishment of the UE context in the eNodeB 106 and the UE 114 can involve a relatively large amount of signaling (in terms of number of messages and number of bytes that are exchanged between the UE 114 and the eNodeB 106).

[0022] In previous solutions, when the UE 114 is in the RRC idle state (i.e., the UE context is not maintained in the UE 114 and the eNodeB 106, but the UE context is stored in an MME and S-GW), the UE 114 can update the network on its location each time the UE 114 crosses a geographical area (or tracking area). For example, the UE 114 can inform the MME when the UE 114 enters a tracking area 2 (TA2). When there is downlink data to be delivered from the network to the UE 114, the data can first be passed from the S-GW to the MME, and the MME can subsequently page the UE 114. Since the eNodeBs do not have any knowledge about the UE 114 (i.e., no knowledge of the UE context) and the MME only has knowledge of the UE 114 at a tracking area granularity, the MME can send a paging message to all eNodeBs in that particular tracking area. In other words, in previous solutions, the paging for the UE 114 can be initiated by the MME. The paging message is a broadcast message that can be listened to by a plurality of UEs, and the paging message can have one or more UE identifiers for a particular UE 114 for which the paging message is applicable. When the UE 114 detects its own UE identifier in the broadcasted paging message, the UE 114 can determine that it's been paged and the UE 114 can transition from the RRC idle mode to the RRC connected mode in order to retrieve the downlink data. In previous solutions, the paging of the UE 114 that is initiated by the MME can involve an undue amount of signaling between the MME, S-GW, eNodeBs and UEs.

[0023] In one example, the UE identifier (ID) in the paging message can be used to wake up a specific UE (e.g., UE 114). In LTE systems, several identifiers can be associated with the UE 114. For example, LTE systems can use protocol layer transparency, so each protocol layer can provide its own UE identifier. One example of a RAN-based ID is a cell radio network temporary identifier (C-RNTI), and one example of a CN (NAS)-based ID is a System Architecture Evolution (SAE) temporary mobile subscriber identity (S- TMSI).

[0024] In an alternative example, the UE 114 can transition to the RRC connected state using a reduced signaling load, which can be achieved by storing a last used UE context (with a last used RAN configuration for the UE 114) in the eNodeB 106 and the UE 114 even when the UE 114 is in the RRC ide mode. Therefore, when the UE 114 transitions from the RRC idle mode to the RRC connected mode, the UE 114 can simply revive the stored last used UE context in the eNodeB 106 and the UE 114. This resumption (or revival) of the stored last used UE context can involve a reduced amount of signaling, thereby reducing the number of messages and the number of bytes that are exchanged between the UE 114 and the eNodeB 106.

[0025] In one example, the UE 114 can be considered as being suspended when the UE 114 is in the RRC idle state and the last used UE context is stored at the UE 114 and the eNodeB 106. In addition, a CN, e.g., an MME / S-GW 102 can be informed when the UE 114 is suspended, and bearers over an S l-U interface can be torn down or also be placed into a suspended state or inactive state (which is a different state as compared to an idle state or connected state). In another example, the suspended state of the UE 114 can be considered as part of the RRC connected state and the MME / S-GW 102 may not be informed when the UE 114 is in the suspended state.

[0026] In one example, when the UE is suspended, a MME-originated paging message can utilize a UE NAS identity, such as the S-TMSI. Alternatively, when the UE is suspended, a different UE ID (e.g., a Suspend UE ID) can be utilized to identify a node that stores the UE context as well as the UE context itself.

[0027] In one example, the UE 114 can utilize a discontinuous reception (DRX) mechanism for power saving when the UE 114 is in the RRC idle mode (or suspended mode). In some cases, the suspended mode can be part of an RRC connected mode. With DRX, the UE 114 can only wake up for a short period of time to monitor for a paging message and can be asleep for the remainder of a paging cycle. A period for which the UE 114 wakes up to monitor for the paging message can be referred to as a DRX cycle length parameter, which can be selected by the UE 114. The DRX cycle length parameter can effectively determine a delay to provide data to the UE 114. In previous solutions, the DRX cycle length parameter can be negotiated between the UE 114 and the MME using non access stratum (NAS) signaling when the UE 114 attaches to the network or when the UE 114 sends a tracking area update (TAU). Since the DRX cycle length parameter can be negotiated between the UE 114 and the MME, this parameter can be referred to as a core network (CN) DRX cycle length parameter. In addition, in previous solutions, the selection of the DRX cycle length parameter by the UE during attach/TAU does not allow the DRX cycle length parameter to be controlled based on current traffic constraints for the UE 114.

[0028] In one configuration, the UEs that monitors for paging messages can be in various states. For example, a "UE-1" or "UE in idle": can indicate a UE that is released to the RRC idle mode (RRC IDLE), as in legacy LTE. In this state, UE AS context is not stored by the UE or the RAN node, i.e., the UE is not suspended. In another example, a "UE-2" or "UE suspended" can indicate a UE that is suspended, e.g., as defined in 3GPP LTE

Release 13 as part of a new suspend/resume procedure for non-NB-IoT UEs. In this state, a UE can be released to the RRC idle mode, and the UE can store the UE AS context which is also stored in the eNodeB. In this state, the UE can use a DRX cycle based on legacy LTE (e.g., a minimum of a UE specific paging DRX cycle, indicated to the UE via NAS, and a cell specific paging DRX cycle) and paging for the UE can be triggered by the MME (CN node). In yet another example, a "UE-3" or "UE in light connected" or "UE in light state" or "UE suspended that are paged by RAN node" or "UE suspended with RAN DRX cycle" can indicate a UE that is suspended similarly to "UE-2" but the UE can be allocated with a different kind of DRX cycle and the paging message can be triggered by the RAN node, as described in further details below.

[0029] FIG. 2 illustrates exemplary signaling between an eNodeB 210 and a user equipment (UE) 220 for paging. The UE 220 can be in suspended state, and therefore, UE context information for the UE 220 can be stored in memory of the eNodeB 210 and the UE 220. The eNodeB 210 can determine radio access network (RAN)-based UE paging parameters for configuration of the UE 220 when the UE 220 is in the suspended state. RAN-based UE paging parameters can include a RAN discontinuous reception (DRX) cycle length paging parameter and a UE paging identifier (ID) (or simply UE ID). More specifically, the eNodeB 210 can receive a power saving preference message from the UE 220, and the eNodeB 210 can determine the RAN DRX cycle length paging parameter based on the power saving preference message. The eNodeB 210 can receive a message from the UE 220 that indicates quality of service (QoS) constraints for one or more data radio bearers (DRBs) established for the UE 220. In addition, the eNodeB 210 can receive QoS constraints and power saving information related to the UE 220 from a core network (CN) node, such as an MME. The eNodeB 210 can determine the RAN DRX cycle length paging parameter based on the QoS constraints for the one or more DRB established for the UE 220. In other words, based on the power saving preference message and/or the QoS constraints for the DRBs, the eNodeB 210 can determine the RAN DRX cycle length paging parameter, which is one of the RAN-based UE paging parameters for the UE 220.

[0030] In one example, the eNodeB 210 can send the RAN-based UE paging parameters (which can include the RAN DRX cycle length paging parameter and the UE paging ID) to the UE 220. The UE 220 can receive the RAN-based UE paging parameters, and the UE 220 can store the RAN-based UE paging parameters for subsequent usage.

[0031] In one example, the UE paging ID can be a RAN-based UE ID or a core network (CN) based UE ID. The RAN-based UE ID can include a cell radio network temporary identifier (C-RNTI), and the CN-based UE ID can include a non-access stratum (NAS) UE ID or a System Architecture Evolution (SAE) temporary mobile subscriber identity (S-TMSI).

[0032] In an alternative example, the eNodeB 210 can receive a message from the UE 220 that indicates QoS constraints for one or more DRBs established for the UE 220 or applications executed at the UE 220, and the eNodeB 210 can select different RAN DRX cycle length paging parameters for each DRB or application category based on the QoS constraints. The eNodeB 210 can send the RAN-based UE paging parameters (which can include the different RAN DRX cycle length paging parameters for each DRB or application category and the UE paging ID) to the UE 220.

[0033] In one example, at a later time (i.e., after the UE 220 is configured with the RAN- based UE paging parameters), the eNodeB 210 can receive downlink data for the UE 220. For example, the eNodeB 210 can receive the downlink data from an MME (not shown), and the downlink data can be for the UE 220. The eNodeB 210 can send a RAN- originated paging message to the UE 220 when the UE 220 is in the suspended state, which can indicate to the UE 220 that the eNodeB 210 is currently holding downlink data for the UE 220 (i.e., downlink data to be retrieved by the UE 220). The eNodeB 210 can directly send the RAN-originated paging message to the UE 220 (i.e., the paging message originates at the eNodeB 210 and not at another CN node, such as an MME). The UE 220 can receive the RAN-originated paging message in accordance with the RAN-based UE paging parameters that were previously received at the UE 220. For example, the UE 220 can monitor for the RAN-originated paging message in accordance with the DRX cycle length paging parameter included in the RAN-based UE paging parameters. The UE 220 can detect the RAN-originated paging message based on the UE paging ID. In addition, the UE 220 can initiate a transition to a radio resource control (RRC) connected state to retrieve the downlink data from the eNodeB 210 after receiving the RAN-originated paging message. Alternatively, the downlink data can be sent to the UE 220 in an inactive state without fully transitioning to the RRC connected state.

[0034] In an alternative configuration, the eNodeB 210 can receive a NAS UE ID from a CN node, such as an MME (not shown). The eNodeB 210 can receive NAS DRX paging parameters received from the CN node. The eNodeB 210 can store the NAS UE ID and the NAS DRX paging parameters along with UE RAN context for the UE 220. The eNodeB 210 can include the NAS UE ID and the NAS DRX paging parameters received from the CN node in the RAN-based UE paging parameters. The eNodeB 210 can send the RAN-based UE paging parameters (with the NAS UE ID and the NAS DRX paging parameters) to the UE 220.

[0035] In another alternative configuration, the eNodeB 210 can receive the power saving preference message and/or the QoS constraints for the DRBs established for the UE 220, and the eNodeB 210 can determine the RAN DRX cycle length paging parameter, which is one of the RAN-based UE paging parameters for the UE 220. In other words, the RAN- based UE paging parameters can be negotiated between the UE 220 and the eNodeB 210. The eNodeB 210 can send the RAN-based UE paging parameters to a CN node, such as an MME. The CN node can receive and store the RAN-based UE paging parameters, and the CN node can utilize the RAN-based UE paging parameters for subsequent paging messages from the CN node (i.e., CN-originated paging messages). In this configuration, the eNodeB 210 can send certain paging parameters to the CN node, and the CN node can originate the paging message using these paging parameters (and possibly other parameters)

[0036] In an alternative configuration, the eNodeB 210 can originate the paging message and send the RAN-originated paging message across a paging area. The paging area may be the same or different than a tracking area. Since the paging area can include multiple eNodeBs, the eNodeB 210 can send the RAN-originated paging message to other eNodeBs across X2 connections. In some cases, the X2 connections may not exist between al of the eNodeBs, and in this case, the eNodeB 210 can request the MME (which is connected to all of the eNodeBs in the paging area) to forward the RAN- originated paging message to all of the eNodeBs in the paging area.

[0037] In an alternative configuration, the CN node (e.g., MME) can consider the QoS constraints for the DRBs established for UE 220, and the CN node can determine a DRX cycle length paging parameter based on the QoS constraints. The CN node can provide the DRX cycle length paging parameter to the UE 220 directly over NAS signaling or RRC signaling.

[0038] In another configuration, when the eNodeB 210 pages the UE 220, the eNodeB 210 can use a different identifier for the UE 220 as compared to an identifier used by the MME for paging. However, there is a possibility that the UE 220 and the network can become out of sync, and in this case, the UE 220 can believe its idle whereas the network can believe that the UE 220 is light connected, or vice versa. Therefore, the UE 220 can monitor RAN-originated paging messages using both identifiers (e.g., a CN or NAS identifier and a RAN identifier), which can ensure that the UE 220 is able to detect a

RAN-originated paging message that is applicable to the UE 220. In other words, in order to mitigate a possible mismatch between a UE suspend state and an RRC idle state, the eNodeB 210 can send the RAN-originated paging message with the NAS UE ID and the NAS DRX cycle (in addition to the RAN-based UE ID and DRX cycle length parameter).

[0039] In one configuration, when a UE is suspended, a control plane node in the network can store UE RAN context along with a RAN DRX cycle length parameter (which may be different from a CN DRX cycle length parameter). The Sl-U bearers can be retained to a user plane node. The user plane node and the control plane node can be the same node or different nodes. These nodes can be the same as a last serving eNodeB for the UE, or these nodes can include previous eNodeBs that have served the UE, or these nodes can include a node that is serving as an anchor point for the UE storing the UE RAN context and terminating the Sl-U bearers associated with the user plane.

[0040] In one configuration, a RAN network can provide a RAN DRX cycle length parameter to the UE to be used when the UE is suspended. The RAN DRX cycle length parameter can be provided to the UE when the UE is RRC connected at a time prior to the UE being suspended, and the RAN DRX cycle length parameter can be applicable for one or more suspend/resume cycles. For example, the configured RAN DRX cycle length parameter can be applicable until cleared or reconfigured to a new value by the network. The RAN DRX cycle length parameter can be known to both the RAN network and the UE prior to paging messages being sent from the RAN network to the UE.

[0041] In one configuration, the RAN DRX cycle length parameter provided to the UE can take into consideration UE power saving constraints, a desired QoS for established data radio bearers (DRBs), etc. Each DRB can contain data from different TCP/IP flows (e.g., a voice session which utilizes an increased QoS can be associated with a certain DRB). For example, when a DRB bearer has a low delay constraint, the network can configure a short DRX cycle length parameter for the UE that causes the UE to wake up more frequently. On other hand, when a DRB bearer allows for a high delay, the network can configure a long DRX cycle length parameter for the UE that causes the UE to wake up less frequently. Therefore, the network can configure specific DRX cycle length parameters that satisfy particular DRB constraints for the UE. This dynamic configuration of the DRX cycle length parameters based on specific DRBs can be in contrast to static DRX cycle length parameters that are agnostic to the DRBs that are used. This dynamic configuration of the DRX cycle length parameters can be based on the QoS constraints for a particular DRB for a particular UE, which allows for more flexible DRX

configurations per UE. In another example, when the UE indicates a desire for increased/decreased power saving, the network can configure a longer/shorter DRX cycle length parameter for the UE to achieve the increased/decreased power saving, respectively.

[0042] In one example, the RAN DRX cycle length parameter can be a network configured value (any value) or chosen from a list such as/similar to long DRX cycle parameters defined for a connected mode DRX configuration that is already defined over a wide range. The RAN DRX cycle length parameter can be determined from/based on the connected DRX parameters. In an alternative example, a new default value can be broadcast by the network, although the QoS of individual UEs may not be taken into consideration in this example. In another altemative example, the RAN DRX cycle length parameter can be defined in a similar manner as the CN DRX cycle length parameter currently assigned by the CN node (e.g., MME), but the RAN DRX cycle length parameter can be assigned instead by the RAN node (e.g., eNodeB). In addition, the CN DRX cycle length parameter can be an input that the RAN node considers when determining the RAN DRX cycle length parameter.

[0043] In one example, when data arrives at an SI -U bearer termination network node (e.g., eNodeB), the network node can initiate a procedure to page the UE. The UE can be paged by the network node using the RAN DRX cycle length parameter that is applicable at that time.

[0044] In one configuration, in a legacy LTE paging mechanism, a CN node (e.g., MME) can negotiate a CN DRX cycle length parameter with the UE and the CN node can trigger the paging for the UE. In the legacy LTE paging mechanism, the UE can be a UE-1 or a UE-2. In contrast, for a novel RAN-based paging mechanism, a RAN node (e.g., eNodeB) can negotiate a RAN DRX cycle length parameter with the UE, and the RAN node can trigger the paging for the UE. In the novel RAN-based paging mechanism, the UE can be a UE-3. In the novel RAN-based paging mechanism, the RAN node can be an anchor for a paging decision, as opposed to the CN node, as in the legacy LTE paging mechanism. [0045] A RAN paging message can be defined in different manners independent of whether the CN node or the RAN node triggers the paging for the UE. For example, in one configuration, a same RAN paging message (e.g., RRC paging message) can be used to page UEs (e.g., UE-1, UE-2 or UE-3) when the paging originates at the CN node or the RAN node. The paging DRX cycle length parameter associated with these UEs can share certain commonality in order to allow the usage of the same RAN paging messages. The same RAN paging messages can include different paging UE IDs. In addition, the same RAN paging messages can utilize a same paging radio network temporary identifier (P- RNTI) or a new/different RNTI. In an alternative configuration, different RAN paging message (e.g., a RRC paging message and RRC light paging message) can be used to page UEs when the paging originates at the CN node or the RAN node. Here, a UE-3 can be paged with a different RRC message as compared to a UE-1 or UE-2. These two RAN paging messages (e.g., the RRC paging message and RRC light paging message) can be defined to be sent in same or different time and frequency resources. The different RAN paging messages can include different paging UE IDs. In addition, the different RAN paging messages can utilize a same P-RNTI or a new/different RNTI.

[0046] In one configuration, a UE paging ID (or simply UE ID) used in the RAN- originated paging message can be a RAN-based UE ID or a NAS UE ID. The RAN- based UE ID can be a C-RNTI or a Suspend UE ID or any other RAN ID pre-agreed or signaled between the UE and the RAN network. The NAS UE ID can include an S-

TMSI. To use the NAS UE ID, the MME can provide the UE NAS ID to the RAN node storing the UE RAN context over S 1 signaling between the MME and the RAN node. The UE RAN context and/or an S l-U bearer termination point can be transferred from one RAN node (e.g., eNodeB) to another RAN node when the UE is connected or suspended. The UE paging parameters, such as the DRX parameters and the UE paging ID can also be transferred to the new network node at that time.

[0047] In one example, paging that is initiated by the RAN node can be referred to as suspend-mode paging (localized paging) or RAN-originated paging, which can be differentiated from NAS-based paging that originates from the MME (core network). The RAN-originated paging message can encompass only an agreed UE paging ID, such as the Suspend UE ID, whereas in legacy LTE systems, a paging message can include multiple paging records each with a UE ID (e.g., S-TMSI or IMSI) and a circuit switched (CS) or packet switched (PS) domain indicator.

[0048] In one example, the UE paging ID (or simply UE ID) used in the RAN-originated paging message can be unique within a UE-specific area where the RAN-originated paging message is sent. For example, the area can be determined to be centered around a cell in which the UE was located when the UE moved to the suspended state. The area can be defined as a list of cells or a list of groups of cells. To ensure that the UE paging ID used in the RAN-originated paging message is unique within this area that is dynamically allocated, a UE paging ID that is guaranteed to be unique over a much larger area can be used. For example, the UE paging ID can include a network code field, e.g., referring to a cell that allocated the UE paging ID, and a UE specific field that refers to a specific UE within that cell. The network code field can be unique over a large area and perhaps even the whole network. To ensure that the UE specific portion is unique within that cell, the UE specific portion can refer to a time when the UE paging ID was allocated and/or the UE specific portion can refer to a time since a RAN node/cell that allocated the UE paging ID was restarted.

[0049] In one example, a paging occasion at which the UE checks a physical downlink control channel (PDCCH) for the P-RNTI can be calculated using a timer based on a configured DRX cycle length value. The timer can be from a system frame number (SFN) corresponding to a point in time at which the UE started a suspended mode, and the SFN can be used as a clock reference. Alternatively, the paging occasion at which the UE checks the PDCCH for the P-RNTI can be calculated using legacy calculations as a baseline, as per 3GPP LTE Release 13 36.304 idle mode procedures which allow for further randomness if desired. When a default paging cycle is not defined per RAN node, a configured value can be considered without finding a minimum of the two. In yet another alternative, the paging occasion at which the UE checks the PDCCH for the P- RNTI can be calculated using an absolute time reference based on a coordinated universal time (UTC) in a system information block 16 (SIB 16), and the absolute time reference can be utilized when a paging window is defined.

[0050] In one example, the UEs can overwrite rules of choosing a minimum (as explained above) or the UEs can use a different rule when defined by the 3 GPP LTE specification or when indicated by the network. For example, the network can indicate that the UE is to always use a UE-specific DRX cycle or to use a UE-specific DRX cycle when a certain threshold in comparison to the corresponding cell is met (which can aim to allow a usage of very large UE DRX cycles when permitted). This approach can be useful when the UEs uses an extended DRX in idle mode (i-eDRX) cycle or when the UE is provided with a maximum DRX cycle due to its power conditions, even when a default DRX cycle of the corresponding cell is smaller.

[0051] In one example, a new P-RNTI specific to this novel RAN-based paging mechanism can be defined with a new value. In another example, the RAN-originated paging message can be transferred using a legacy logical channel, such as a paging control channel (PCCH), and a transport channel, such as a paging channel (PCH), or corresponding new channels can be defined.

[0052] In one example, the novel RAN-based paging mechanism can be used with a DRX cycle and extended DRX cycle, as defined in 3GPP LTE Release 13. In another example, a UE-3 using the RAN-based paging DRX cycle may not use extended DRX in idle mode (I-eDRX). In yet another example, the I-eDRX can occur over the top or transparently to the RAN-based paging or RAN node.

[0053] In one example, the RAN-based paging DRX range can be the same as a legacy LTE 2.56sec. In another example, the RAN-based paging DRX range can be increased, e.g., up to 5.12 or 10.24 sec, but a similar paging DRX operation can be utilized, e.g., a paging frame (PF) can be found with one or multiple paging occasions (PO) every certain time (TRAN-basedDRx). In yet another example, the RAN-based paging DRX can operate similar to previously described, but a different node (e.g., the MME or application server) can indicate to the RAN node every time that the UE become available/reachable for RAN-based paging. When the indication is provided by the MME, then this approach can allow a same operation of I-eDRX. In a further example, the RAN-based paging DRX can operate similar to previously described, but an additional mechanism can be defined in the RAN node to track or trigger every time that the UE become available/reachable for the RAN-based paging. This approach can effectively involve moving the I-eDRX mechanism or a portion of the I-eDRX mechanism to the RAN node.

[0054] In one example, when I-eDRX is used, this functionality can be allowed, negotiated/configured and controlled by different nodes. For example, with a CN centric operation, a CN node (e.g., MME) can negotiate, configure and/or control usage of the I- eDRX. The RAN node can determine when the UE is reachable during the active periods (PF/PO) of the RAN-based DRX cycle. In some cases, a paging window time (PTW) can also be indicated to the RAN node. In another example, with a split operation between the CN and RAN nodes, the CN node (e.g., MME) can control a portion of the I-eDRX operation (e.g., allow and negotiate/configure its usage) and a remaining portion can be handled by the RAN node (e.g., an actual control of I-eDRX operations can be handled by the RAN node). For example, the CN node can negotiate the usage/parameters for the I- eDRX cycle and PTW, but the RAN node can later control when the UE becomes reachable with the RAN-based DRX cycle and a period of time (e.g., a PTW time) before the UE enters again in an extended inactive period configured by the I-eDRX cycle. In yet another example, in a RAN centric operation, the RAN node (e.g., eNodeB) can negotiate, configure and control usage of the I-eDRX.

[0055] In one example, the extended DRX operation can be changed for a UE-3 in order to simplify operation considering that the paging is RAN-based. Therefore, a UE within an I-eDRX cycle may not be reached for multiple DRX cycles (which are currently defined as short based on DRX cycles). Instead, a length of the RAN based DRX cycle can be extended as the UE only wakes up for one PF.

[0056] In one configuration, multiple RAN DRX parameters can be utilized per UE. A UE can have associated different DRX cycle parameters per bearer or application. For example, the UE can be configured to use a minimum DRX cycle parameter 'x', and each bearer or category of applications or category of pagings can have associated different paging DRX cycle parameters, e.g., "x", "n*x" or "m*x", where n,m are integers and "x" is the minimum value of the DRX cycle parameter. The ability to have different DRX cycle parameters per bearer of application or application category can reduce a number of times in which the UE wakes up for mobile terminated (MT) traffic, while guaranteeing different MT reachability delays. As an example, when bearer 1 is to be paged with DRX cycle 'x' but bearer 2 can be paged using DRX cycle 'η*χ', the UE can check a paging frame (PF) and/or paging occasion (PO) every 'x' seconds, and the network (e.g., RAN or CN node) can send the paging message to the UE in a reduced amount of time (every 'x' sec) or in an increased amount of time (every "n*x") depending on whether the paging message was received on bearer 1 or 2. This approach can be useful for UEs that take an increased amount of time when transitioning into RRC connected mode or UEs that consume an increased amount of power (e.g., due to poor location) when transitioning into RRC connected mode.

[0057] FIG. 3 is an exemplary flowchart illustrating operations for performing paging between an eNodeB and a user equipment (UE). The eNodeB can determine radio access network (RAN)-based paging parameters for the UE, as in block 302. The eNodeB can determine the RAN-based paging parameters for the UE based on quality of service (QoS) constraints of data radio bearers (DRBs) of the UE, a UE power saving preference, etc. The RAN-based paging parameters can include a C-RNTI, a S-TMSI, a Suspend UE ID or a new specific UE IE. The eNodeB can configure the UE with the RAN-based paging parameters, as in block 304. For example, the eNodeB can send the RAN-based paging parameters to the UE. The eNodeB can send a RAN originated paging message to the UE, as in block 306. The RAN originated paging message can utilize the RAN-based paging parameters and/or core network (CN)-based paging parameters. The eNodeB can send the RAN originated paging message to the UE using the pre-negotiated RAN-based paging parameters, as in block 308. The UE can receive the RAN originated paging message from the eNodeB using the pre-negotiated RAN-based paging parameters, as in block 310.

[0058] In one example, the signaling of the RAN-based paging parameters and the RAN originated paging message can be performed in 3GPP LTE systems that utilize suspend/resume mechanisms. Alternatively, the signaling of the RAN-based paging parameters and the RAN originated paging message can be performed in other RANs that support a power efficient state, such as a 5G New Radio (NR) system.

[0059] In one configuration, a user equipment (UE) can use radio access network (RAN)- assigned paging parameters in order to receive paging messages from a RAN (e.g., eNodeB). The RAN-assigned paging parameters can include a paging discontinuous reception (DRX) parameter and/or a paging UE identifier (ID). The paging UE ID can be a C-RNTI, a S-TMSI, a Suspend UE ID or a new specific UE ID. The RAN-assigned paging parameters can be a combination of RAN-assigned parameters and CN-assigned parameters. The UE can receive the RAN-assigned paging parameters from the RAN (e.g., eNodeB) and store the RAN-assigned paging parameters at the UE, and the UE can later use the RAN-assigned paging parameters in order to receive the paging messages from the RAN (e.g., eNodeB). The paging messages received at the UE can originate in the RAN or CN. The UE can calculate a paging occasion subframe using a simple system frame number (SFN) based timer reference, or alternatively, using an absolute time reference based on a coordinated universal time (UTC) in a system information block 16 (SIB 16). The UE can receive a paging message that includes the paging UE ID corresponding to the UE, and the paging UE ID can be unique within a given

geographical area. In addition, the UE can provide a power saving preference to the RAN (e.g., eNodeB), and the power saving preference can assist in determining a RAN DRX setting for the UE.

[0060] In one configuration, a network node (e.g., a RAN node or CN node) can assign paging parameters to a UE, and the paging parameters can be used for subsequent paging messages. The paging parameters can include a paging DRX parameter and/or a paging UE ID. The network node can utilize quality of service (QoS) constraints of bearers and/or power saving constraints from the UE when determining the paging parameters, such as the paging DRX parameter.

[0061] In one configuration, a RAN node (e.g., eNodeB) can receive a UE NAS ID and/or a NAS DRX from a CN node for storage with a UE RAN context, and the RAN node can use the UE NAS ID and/or NAS DRX for subsequent paging messages. The RAN node can originate a paging message and send the paging message using a combination of RAN-based parameters and CN-based parameters. The RAN node can use NAS paging parameters for RAN-originated paging to handle UEs that may have been in an RRC idle state when the RAN node believes the UEs were in a suspended state. In addition, the RAN node can allocate a unique UE ID that includes a part field referring to a time the unique UE ID was allocated or when a network node was restarted.

[0062] In one configuration, a CN node (e.g., MME) can receive paging parameters for a UE from a RAN node. The CN node can store the paging parameters and utilize the paging parameters for subsequent paging messages that originate at the CN node.

[0063] Another example provides functionality 400 of a base station operable to provide paging messages to a user equipment (UE), as shown in FIG. 4. The base station can comprise memory and one or more processors. The one or more processors can be configured to determine, at the base station, radio access network (RAN)-based UE paging parameters for configuration of a UE when the UE is in a suspended state, wherein UE context information for the UE is stored in the memory of the base station when the UE is in the suspended state, as in block 410. The one or more processors can be configured to encode, at the base station, the RAN-based UE paging parameters for transmission to the UE, as in block 420. The one or more processors can be configured to generate, at the base station, a RAN-originated paging message for the UE when downlink data is received at the base station for the UE, as in block 430. The one or more processors can be configured to encode, at the base station, the RAN-originated paging message for transmission to the UE, wherein the RAN-originated paging message is transmitted from the base station and received at the UE in accordance with the RAN- based UE paging parameters, as in block 440.

[0064] Another example provides functionality 500 of a user equipment (UE) operable to decode paging messages received from a base station, as shown in FIG. 5. The UE can comprise one or more processors. The one or more processors can be configured to decode, at the UE, radio access network (RAN)-based UE paging parameters received from the base station, wherein the RAN-based UE paging parameters include a RAN discontinuous reception (DRX) cycle length paging parameter of the base station and a UE paging identifier (ID), as in block 510. The one or more processors can be configured to decode, at the UE, a RAN-originated paging message received from the base station when the UE is in a suspended state, wherein the RAN-originated paging message is received at the UE when downlink data for the UE is stored at the base station and in accordance with the RAN-based UE paging parameters, as in block 520. The one or more processors can be configured to initiate, at the UE, a radio resource control (RRC) connected state to retrieve the downlink data from the base station after receiving the RAN-originated paging message, as in block 530. In addition, the UE can comprise memory interfaced with the one or more processors, and the memory can be configured to store the RAN-based UE paging parameters received from the base station.

[0065] Another example provides at least one machine readable storage medium having instructions 600 embodied thereon for providing paging messages from a node to a user equipment (UE), as shown in FIG. 6. The instructions can be executed on a machine, where the instructions are included on at least one computer readable medium or at least one non-transitory machine readable storage medium. The instructions when executed by one or more processors perform: determining, at the node, radio access network (RAN)- based UE paging parameters for configuration of a UE, as in block 610. The instructions when executed by one or more processors perform: encoding, at the node, the RAN-based UE paging parameters for transmission to the UE, as in block 620. The instructions when executed by one or more processors perform: generating, at the node, a RAN-originated paging message for the UE when downlink data is received for the UE, as in block 630. The instructions when executed by one or more processors perform: encoding, at the node, the RAN-originated paging message for transmission to the UE, wherein the RAN- originated paging message is transmitted from the node and received at the UE in accordance with the RAN-based UE paging parameters, as in block 640.

[0066] FIG. 7 illustrates an architecture of a wireless network with various components of the network in accordance with some embodiments. A system 700 is shown to include a user equipment (UE) 701 and a UE 702. The UEs 701 and 702 are illustrated as smartphones (i.e., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also comprise any mobile or non-mobile computing device, such as Personal Data Assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, or any computing device including a wireless

communications interface. In some embodiments, any of the UEs 701 and 702 can comprise an Internet of Things (IoT) UE, which can comprise a network access layer designed for low-power IoT applications utilizing short-lived UE connections. An IoT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for (machine initiated) exchanging data with an MTC server and/or device via a public land mobile network (PLMN), Proximity-Based Service (ProSe) or device-to-device (D2D) communication, sensor networks, or IoT networks. An IoT network describes interconnecting uniquely identifiable embedded computing devices (within the internet infrastructure) having short-lived connections, in addition to background applications (e.g., keep-alive messages, status updates, etc.) executed by the IoT UE.

[0067] The UEs 701 and 702 are configured to access a radio access network (RAN)— in this embodiment, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN) 710. The UEs 701 and 702 utilize connections 703 and 704, respectively, each of which comprises a physical

communications interface or layer (discussed in further detail below); in this example, the connections 703 and 704 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, and the like.

[0068] In this embodiment, the UEs 701 and 702 may further directly exchange communication data via a ProSe interface 705. The ProSe interface 705 may alternatively be referred to as a sidelink interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH).

[0069] The UE 702 is shown to be configured to access an access point (AP) 706 via connection 707. The connection 707 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 706 would comprise a wireless fidelity (WiFi) router. In this example, the AP 706 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).

[0070] The E-UTRAN 710 can include one or more access points that enable the connections 703 and 704. These access points can be referred to as access nodes, base stations (BSs), NodeBs, RAN nodes, RAN nodes, and so forth, and can comprise ground stations (i.e., terrestrial access points) or satellite access points providing coverage within a geographic area (i.e., a cell). The E-UTRAN 710 may include one or more RAN nodes 711 for providing macrocells and one or more RAN nodes 712 for providing femtocells or picocells (i.e., cells having smaller coverage areas, smaller user capacity, and/or higher bandwidth compared to macrocells).

[0071] Any of the RAN nodes 711 and 712 can terminate the air interface protocol and can be the first point of contact for the UEs 701 and 702. In some embodiments, any of the RAN nodes 711 and 712 can fulfill various logical functions for the E-UTRAN 710 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

[0072] In accordance with some embodiments, the UEs 701 and 702 can be configured to communicate using Orthogonal Frequency -Division Multiplexing (OFDM)

communication signals with each other or with any of the RAN nodes 711 and 712 over a multicarrier communication channel in accordance various communication techniques, such as an Orthogonal Frequency-Division Multiple Access (OFDMA) communication technique (e.g., for downlink communications) or a Single Carrier Frequency Division Multiple Access (SC-FDMA) communication technique (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. The OFDM signals can comprise a plurality of orthogonal subcarriers.

[0073] In some embodiments, a downlink resource grid can be used for downlink transmissions from any of the RAN nodes 711 and 712 to the UEs 701 and 702, while uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid, called a resource grid or time-frequency resource grid, which is the physical resource in the downlink in each slot. Such a time-frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation. Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to one slot in a radio frame. The smallest time-frequency unit in a resource grid is denoted as a resource element. Each resource grid comprises a number of resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block comprises a collection of resource elements; in the frequency domain, this represents the smallest quantity of resources that currently can be allocated. There are several different physical downlink channels that are conveyed using such resource blocks. [0074] The physical downlink shared channel (PDSCH) carries user data and higher-layer signaling to the UEs 701 and 702. The physical downlink control channel (PDCCH) carries information about the transport format and resource allocations related to the PDSCH channel, among other things. It also informs the UEs 701 and 702 about the transport format, resource allocation, and H-ARQ (Hybrid Automatic Repeat Request) information related to the uplink shared channel. Typically, downlink scheduling (assigning control and shared channel resource blocks to the UE 102 within a cell) is performed at any of the RAN nodes 711 and 712 based on channel quality information fed back from any of the UEs 701 and 702, and then the downlink resource assignment information is sent on the PDCCH used for (i.e., assigned to) each of the UEs 701 and 702.

[0075] The PDCCH uses control channel elements (CCEs) to convey the control information. Before being mapped to resource elements, the PDCCH complex-valued symbols are first organized into quadruplets, which are then permuted using a sub-block inter-leaver for rate matching. Each PDCCH is transmitted using one or more of these CCEs, where each CCE corresponds to nine sets of four physical resource elements known as resource element groups (REGs). Four Quadrature Phase Shift Keying (QPSK) symbols are mapped to each REG. The PDCCH can be transmitted using one or more CCEs, depending on the size of the downlink control information (DCI) and the channel condition. There can be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation level, L=l, 2, 4, or 8).

[0076] The E-UTRAN 710 is shown to be communicatively coupled to a core network— in this embodiment, an Evolved Packet Core (EPC) network 720 via an SI interface 713. In this embodiment the SI interface 713 is split into two parts: the S I -U interface 714, which carries traffic data between the RAN nodes 711 and 712 and the serving gateway (S-GW) 722, and the Sl-MME interface 715, which is a signaling interface between the RAN nodes 711 and 712 and the mobility management entities (MMEs) 721.

[0077] In this embodiment, the EPC network 720 comprises the MMEs 721, the S-GW 722, the Packet Data Network (PDN) Gateway (P-GW) 723, and a home subscriber server (HSS) 724. The MMEs 721 are similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN). The MMEs 721 manage mobility aspects in access such as gateway selection and tracking area list management. The HSS 724 comprises a database for network users, including subscription-related information to support the network entities' handling of

communication sessions. The EPC network 720 may comprise one or several HSSs 724, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc. For example, the HSS 724 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.

[0078] The S-GW 722 terminates the SI interface 713 towards the E-UTRAN 710, and routes data packets between the E-UTRAN 710 and the EPC network 720. In addition, the S-GW 722 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.

[0079] The P-GW 723 terminates an SGi interface toward a PDN. The P-GW 723 routes data packets between the EPC network 723 and external networks such as a network including the application server 730 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 725. Generally, the application server 730 is an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.). In this embodiment, the P-GW 723 is shown to be communicatively coupled to an application server 730 via an IP communications interface 725. The application server 730 can also be configured to support one or more communication services (e.g., Voice-over-Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 701 and 702 via the EPC network 720.

[0080] The P-GW 723 may further be a node for policy enforcement and charging data collection. Policy and Charging Enforcement Function (PCRF) 726 is the policy and charging control element of the EPC network 720. In a non-roaming scenario, there may be a single PCRF in the Home Public Land Mobile Network (HPLMN) associated with a User Equipment's (UE) Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with local breakout of traffic, there may be two PCRFs associated with a UE's IP-CAN session: a Home PCRF (H-PCRF) within a HPLMN and a Visited PCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). The PCRF 726 may be communicatively coupled to the application server 730 via the P-GW 723. The application server 730 may signal the PCRF 726 to indicate a new service flow and selecting the appropriate Quality of Service (QoS) and charging parameters. The PCRF 726 may provision this rule into a Policy and Charging Enforcement Function (PCEF) (not shown) with the appropriate traffic flow template (TFT) and QoS class of identifier (QCI), which commences the QoS and charging as specified by the application server.

[0081] FIG. 8 illustrates example components of a device in accordance with some embodiments. In some embodiments, the device 1500 may include application circuitry 802, baseband circuitry 804, Radio Frequency (RF) circuitry 806, front-end module (FEM) circuitry 808, and one or more antennas 810, coupled together at least as shown. The components of the illustrated device 1500 may be included a UE or a RAN node. In some embodiments, the device 1500 may include less elements (e.g., a RAN node may not utilize application circuitry 802, and instead include a processor/controller to process IP data received from an EPC). In some embodiments, the device 1500 may include additional elements such as, for example, memory /storage, display, camera, sensor, and/or input/output (I/O) interface. In other embodiments, the components described below may be included in more than one device (e.g., said circuitries may be separately included in more than one device for Cloud-RAN (C-RAN) implementations).

[0082] The application circuitry 802 may include one or more application processors. For example, the application circuitry 802 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors may be coupled with and/or may include memory /storage and may be configured to execute instructions stored in the memory /storage to enable various applications and/or operating systems to run on the system. In some embodiments, processors of application circuitry 802 may process IP data packets received from an EPC.

[0083] The baseband circuitry 804 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 804 may include one or more baseband processors and/or control logic to process baseband signals received from a receive signal path of the RF circuitry 806 and to generate baseband signals for a transmit signal path of the RF circuitry 806. Baseband processing circuity 804 may interface with the application circuitry 802 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 806. For example, in some embodiments, the baseband circuitry 804 may include a second generation (2G) baseband processor 804a, third generation (3G) baseband processor 804b, fourth generation (4G) baseband processor 804c, and/or other baseband processor(s) 804d for other existing generations, generations in development or to be developed in the future (e.g., fifth generation (5G), 6G, etc.). The baseband circuitry 804 (e.g., one or more of baseband processors 804a-d) may handle various radio control functions that

enable communication with one or more radio networks via the RF circuitry 806. In other embodiments, some or all of the functionality of baseband processors 804a-d may be included in modules stored in the memory 804g and executed via a Central Processing Unit (CPU) 804e. The radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc. In some embodiments, modulation/demodulation circuitry of the baseband circuitry 804 may include Fast-Fourier Transform (FFT), precoding, and/or constellation

mapping/demapping functionality. In some embodiments, encoding/decoding circuitry of the baseband circuitry 804 may include convolution, tail-biting convolution, turbo, Viterbi, and/or Low Density Parity Check (LDPC) encoder/decoder functionality.

Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.

[0084] In some embodiments, the baseband circuitry may include one or more audio digital signal processor(s) (DSP) 804f. The audio DSP(s) 804f may be include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments. Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments. In some embodiments, some or all of the constituent components of the baseband circuitry 804 and the application circuitry 802 may be implemented together such as, for example, on a system on a chip (SOC).

[0085] In some embodiments, the baseband circuitry 804 may provide for

communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 804 may support communication with an evolved universal terrestrial radio access network (EUTRAN) and/or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN). Embodiments in which the baseband circuitry 804 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

[0086] RF circuitry 806 may enable communication with wireless networks

using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 806 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry 806 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 808 and provide baseband signals to the baseband circuitry 804. RF circuitry 806 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 804 and provide RF output signals to the FEM circuitry 808 for transmission.

[0087] In some embodiments, the RF circuitry 806 may include a receive signal path and a transmit signal path. The receive signal path of the RF circuitry 806 may include mixer circuitry 806a, amplifier circuitry 806b and filter circuitry 806c. The transmit signal path of the RF circuitry 806 may include filter circuitry 806c and mixer circuitry 806a. RF circuitry 806 may also include synthesizer circuitry 806d for synthesizing a frequency for use by the mixer circuitry 806a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 806a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 808 based on the synthesized frequency provided by synthesizer circuitry 806d. The amplifier circuitry 806b may be configured to amplify the down-converted signals and the filter circuitry 806c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals may be provided to the baseband circuitry 804 for further processing. In some embodiments, the output baseband signals may be zero-frequency baseband signals. In some embodiments, mixer circuitry 806a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.

[0088] In some embodiments, the mixer circuitry 806a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 806d to generate RF output signals for the FEM circuitry 808. The baseband signals may be provided by the baseband circuitry 804 and may be filtered by filter circuitry 806c. The filter circuitry 806c may include a low-pass filter (LPF), although the scope of the embodiments is not limited in this respect.

[0089] In some embodiments, the mixer circuitry 806a of the receive signal path and the mixer circuitry 806a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and/or upconversion respectively. In some embodiments, the mixer circuitry 806a of the receive signal path and the mixer circuitry 806a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 806a of the receive signal path and the mixer circuitry 806a may be arranged for direct downconversion and/or direct upconversion, respectively. In some embodiments, the mixer circuitry 806a of the receive signal path and the mixer circuitry 806a of the transmit signal path may be configured for super-heterodyne operation.

[0090] In some embodiments, the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternate embodiments, the output baseband signals and the input baseband signals may be digital baseband signals. In these alternate embodiments, the RF circuitry 806 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 804 may include a digital baseband interface to communicate with the RF circuitry 806.

[0091] In some dual-mode embodiments, a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect. [0092] In some embodiments, the synthesizer circuitry 806d may be a fractional-N synthesizer or a fractional N/N+l synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable. For example, synthesizer circuitry 806d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

[0093] The synthesizer circuitry 806d may be configured to synthesize an output frequency for use by the mixer circuitry 806a of the RF circuitry 806 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 806d may be a fractional N/N+l synthesizer.

[0094] In some embodiments, frequency input may be provided by a voltage controlled oscillator (VCO). Divider control input may be provided by either the baseband circuitry 804 or the applications processor 802 depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the applications processor 802.

[0095] Synthesizer circuitry 806d of the RF circuitry 806 may include a divider, a delay- locked loop (DLL), a multiplexer and a phase accumulator. In some embodiments, the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by either N or N+l (e.g., based on a carry out) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop. In these embodiments, the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0096] In some embodiments, synthesizer circuitry 806d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some embodiments, the output frequency may be a LO frequency (fLO). In some embodiments, the RF circuitry 806 may include an IQ/polar converter.

[0097] FEM circuitry 808 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 810, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 806 for further processing. FEM circuitry 808 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 806 for transmission by one or more of the one or more antennas 810.

[0098] In some embodiments, the FEM circuitry 808 may include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry may include a low-noise amplifier (LNA) to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 806). The transmit signal path of the FEM circuitry 808 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 806), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 810.

[0099] In some embodiments, the device 1500 comprises a plurality of power saving mechanisms. If the device 1500 is in an RRC_Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device may power down for brief intervals of time and thus save power.

[00100] If there is no data traffic activity for an extended period of time, then the device 1500 may transition off to an RRC Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The device 1500 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again. The device cannot receive data in this state, in order to receive data, it must transition back to RRC Connected state.

[00101] An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.

[00102] Processors of the application circuitry 802 and processors of the baseband circuitry 804 may be used to execute elements of one or more instances of a protocol stack. For example, processors of the baseband circuitry 804, alone or in combination, may be used execute Layer 3, Layer 2, and/or Layer 1 functionality, while processors of the application circuitry 804 may utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers). As referred to herein, Layer 3 may comprise a radio resource control (RRC) layer, described in further detail below. As referred to herein, Layer 2 may comprise a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, described in further detail below. As referred to herein, Layer 1 may comprise a physical (PHY) layer of a UE/RAN node, described in further detail below.

[00103] FIG. 9 illustrates example interfaces of baseband circuitry in accordance with some embodiments. As discussed above, the baseband circuitry 804 of FIG. 8 may comprise processors 804a-804e and a memory 804g utilized by said processors. Each of the processors 804a-804e may include a memory interface, 904a-904e, respectively, to send/receive data to/from the memory 804g.

[00104] The baseband circuitry 804 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface 912 (e.g., an interface to send/receive data to/from memory external to the baseband circuitry 804), an application circuitry interface 914 (e.g., an interface to send/receive data to/from the application circuitry 802 of FIG. 8), an RF circuitry interface 916 (e.g., an interface to send/receive data to/from RF circuitry 806 of FIG. 8), and a wireless hardware connectivity interface 918 (e.g., an interface to send/receive data to/from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components).

[00105] FIG. 10 provides an example illustration of the wireless device, such as a user equipment (UE), a mobile station (MS), a mobile wireless device, a mobile

communication device, a tablet, a handset, or other type of wireless device. The wireless device can include one or more antennas configured to communicate with a node, macro node, low power node (LPN), or, transmission station, such as a base station (BS), an evolved Node B (eNB), a baseband processing unit (BBU), a remote radio head (RRH), a remote radio equipment (RRE), a relay station (RS), a radio equipment (RE), or other type of wireless wide area network (WWAN) access point. The wireless device can be configured to communicate using at least one wireless communication standard such as, but not limited to, 3 GPP LTE, WiMAX, High Speed Packet Access (HSPA), Bluetooth, and WiFi. The wireless device can communicate using separate antennas for each wireless communication standard or shared antennas for multiple wireless communication standards. The wireless device can communicate in a wireless local area network

(WLAN), a wireless personal area network (WPAN), and/or a WWAN. The wireless device can also comprise a wireless modem. The wireless modem can comprise, for example, a wireless radio transceiver and baseband circuitry (e.g., a baseband processor). The wireless modem can, in one example, modulate signals that the wireless device transmits via the one or more antennas and demodulate signals that the wireless device receives via the one or more antennas.

[00106] FIG. 10 also provides an illustration of a microphone and one or more speakers that can be used for audio input and output from the wireless device. The display screen can be a liquid crystal display (LCD) screen, or other type of display screen such as an organic light emitting diode (OLED) display. The display screen can be configured as a touch screen. The touch screen can use capacitive, resistive, or another type of touch screen technology. An application processor and a graphics processor can be coupled to internal memory to provide processing and display capabilities. A non-volatile memory port can also be used to provide data input/output options to a user. The non-volatile memory port can also be used to expand the memory capabilities of the wireless device. A keyboard can be integrated with the wireless device or wirelessly connected to the wireless device to provide additional user input. A virtual keyboard can also be provided using the touch screen.

Examples [00107] The following examples pertain to specific technology embodiments and point out specific features, elements, or actions that can be used or otherwise combined in achieving such embodiments.

[00108] Example 1 includes an apparatus of a base station operable to provide paging messages to a user equipment (UE), the base station comprising: one or more processors configured to: determine, at the base station, radio access network (RAN)-based UE paging parameters for configuration of a UE when the UE is in a suspended state, wherein UE context information for the UE is stored in the memory of the base station when the UE is in the suspended state; encode, at the base station, the RAN-based UE paging parameters for transmission to the UE; generate, at the base station, a RAN-originated paging message for the UE when downlink data is received at the base station for the UE; and encode, at the base station, the RAN-originated paging message for transmission to the UE directly or via a core network (CN) node, wherein the RAN-originated paging message is transmitted from the base station and received at the UE in accordance with the RAN-based UE paging parameters; and memory interfaced with the one or more processors, wherein the memory is configured to store the RAN-based UE paging parameters at the base station.

[00109] Example 2 includes the apparatus of Example 1, further comprising a transceiver configured to: transmit the RAN-based UE paging parameters to the UE; and transmit the RAN-originated paging message to the UE.

[00110] Example 3 includes the apparatus of any of Examples 1 to 2, wherein the RAN- based UE paging parameters include one or more of: a RAN discontinuous reception (DRX) cycle length paging parameter or a UE paging identifier (ID).

[00111] Example 4 includes the apparatus of any of Examples 1 to 3, wherein the UE paging ID is a RAN-based UE ID or a CN-based UE ID, wherein the RAN-based UE ID includes a cell radio network temporary identifier (C-RNTI), and the CN-based UE ID includes a non-access stratum (NAS) UE ID or a System Architecture Evolution (SAE) temporary mobile subscriber identity (S-TMSI).

[00112] Example 5 includes the apparatus of any of Examples 1 to 4, wherein the one or more processors are further configured to: decode a power saving preference message received from the UE; and determine the RAN DRX cycle length paging parameter based on the power saving preference message.

[00113] Example 6 includes the apparatus of any of Examples 1 to 5, wherein the one or more processors are further configured to: decode a message received from the UE or the CN node that indicates quality of service (QoS) constraints for one or more data radio bearers (DRBs) established for the UE; and determine the RAN DRX cycle length paging parameter based on the QoS constraints for the one or more DRB established for the UE.

[00114] Example 7 includes the apparatus of any of Examples 1 to 6, wherein the one or more processors are further configured to: decode a message received from the UE that indicates quality of service (QoS) constraints for one or more data radio bearers (DRBs) established for the UE or applications executed at the UE; and select different RAN DRX cycle length paging parameters for each DRB or application category based on the QoS constraints.

[00115] Example 8 includes the apparatus of any of Examples 1 to 7, wherein the one or more processors are further configured to: decode a non-access stratum (NAS) UE ID received from the CN node; and decode NAS discontinuous reception (DRX) paging parameters received from the CN node, wherein the NAS UE ID and the NAS DRX paging parameters received from the CN node are included in the RAN-based UE paging parameters.

[00116] Example 9 includes an apparatus of a user equipment (UE) operable to decode paging messages received from a base station, the UE comprising: one or more processors configured to: decode, at the UE, radio access network (RAN)-based UE paging parameters received from the base station, wherein the RAN-based UE paging parameters includes one or more of a RAN discontinuous reception (DRX) cycle length paging parameter of the base station or a UE paging identifier (ID); decode, at the UE, a RAN- originated paging message received from the base station when the UE is in a suspended state or an idle state, wherein the RAN-originated paging message is received at the UE when downlink data for the UE is stored at the base station and in accordance with the RAN-based UE paging parameters; and initiate, at the UE, a radio resource control (RRC) connected state to retrieve the downlink data from the base station after receiving the RAN-originated paging message; and memory interfaced with the one or more processors, wherein the memory is configured to store the RAN-based UE paging parameters received from the base station.

[00117] Example 10 includes the apparatus of Example 9, further comprising a transceiver configured to: receive the RAN-based UE paging parameters from the base station;

receive the RAN-originated paging message from the base station in accordance with the RAN-based UE paging parameters; and receive the downlink data from the base station.

[00118] Example 11 includes the apparatus of any of Examples 9 to 10, wherein the memory is further configured to store UE context information for the UE when the UE is in the suspended state.

[00119] Example 12 includes the apparatus of any of Examples 9 to 11, wherein the UE paging ID is a RAN-based UE ID or a core network (CN) based UE ID, wherein the RAN-based UE ID includes a cell radio network temporary identifier (C-RNTI), and the CN -based UE ID includes a non-access stratum (NAS) UE ID or a System Architecture Evolution (SAE) temporary mobile subscriber identity (S-TMSI).

[00120] Example 13 includes the apparatus of any of Examples 9 to 12, wherein the one or more processors are further configured to encode a power saving preference message for transmission to the base station, wherein the power saving preference message enables the base station to configure the RAN DRX cycle length paging parameter.

[00121] Example 14 includes the apparatus of any of Examples 9 to 13, wherein the one or more processors are further configured to encode a message for transmission to the base station that indicates quality of service (QoS) constraints for one or more data radio bearers (DRBs) established for the UE, wherein the message containing the QoS constraints for the one or more DRBs enables the base station to configure the RAN DRX cycle length paging parameter.

[00122] Example 15 includes the apparatus of any of Examples 9 to 14, wherein the one or more processors are further configured to encode a message for transmission to the base station that indicates quality of service (QoS) constraints for one or more data radio bearers (DRBs) established for the UE or applications executed at the UE, wherein the message enables the base station to configure different RAN DRX cycle length paging parameters for each DRB or application category based on the QoS constraints [00123] Example 16 includes at least one machine readable storage medium having instructions embodied thereon for providing paging messages from a node to a user equipment (UE), the instructions when executed by one or more processors perform the following: determining, at the node, radio access network (RAN)-based UE paging parameters for configuration of a UE; encoding, at the node, the RAN-based UE paging parameters for transmission to the UE; generating, at the node, a RAN-originated paging message for the UE when downlink data is received for the UE; and encoding, at the node, the RAN-originated paging message for transmission to the UE directly or via a core network (CN) node, wherein the RAN-originated paging message is transmitted from the node and received at the UE in accordance with the RAN-based UE paging parameters.

[00124] Example 17 includes the at least one machine readable storage medium of Example 16, further comprising instructions when executed perform the following:

storing UE context information in memory of the node when the UE is in a suspended state.

[00125] Example 18 includes the at least one machine readable storage medium of any of Examples 16 to 17, wherein the UE paging ID is a RAN-based UE ID or a CN-based UE ID, wherein the RAN-based UE ID includes a cell radio network temporary identifier (C- RNTI), and the CN-based UE ID includes a non-access stratum (NAS) UE ID or a System Architecture Evolution (SAE) temporary mobile subscriber identity (S-TMSI).

[00126] Example 19 includes the at least one machine readable storage medium of any of Examples 16 to 18, wherein the RAN-based UE paging parameters includes one or more of: a RAN discontinuous reception (DRX) cycle length paging parameter or a UE paging identifier (ID).

[00127] Example 20 includes the at least one machine readable storage medium of any of Examples 16 to 19, further comprising instructions when executed perform the following: decoding a power saving preference message received from the UE; and determining the RAN DRX cycle length paging parameter based on the power saving preference message.

[00128] Example 21 includes the at least one machine readable storage medium of any of Examples 16 to 20, further comprising instructions when executed perform the following: decoding a message received from the UE that indicates quality of service (QoS) constraints for one or more data radio bearers (DRBs) established for the UE; and determining the RAN DRX cycle length paging parameter based on the QoS constraints for the one or more DRB established for the UE.

[00129] Example 22 includes the at least one machine readable storage medium of any of Examples 16 to 21, further comprising instructions when executed perform the following: decoding a message received from the UE that indicates quality of service (QoS) constraints for one or more data radio bearers (DRBs) established for the UE or applications executed at the UE; and selecting different RAN DRX cycle length paging parameters for each DRB or application category based on the QoS constraints.

[00130] Example 23 includes the at least one machine readable storage medium of any of Examples 16 to 22, further comprising instructions when executed perform the following: decoding a non-access stratum (NAS) UE ID received from the CN node; and decoding NAS discontinuous reception (DRX) paging parameters received from the CN node, wherein the NAS UE ID and the NAS DRX paging parameters received from the CN node are included in the RAN-based UE paging parameters.

[00131] Example 24 includes a node operable to provide paging messages to a user equipment (UE), the node comprising: means for determining, at the node, radio access network (RAN)-based UE paging parameters for configuration of a UE; means for encoding, at the node, the RAN-based UE paging parameters for transmission to the UE; means for generating, at the node, a RAN-originated paging message for the UE when downlink data is received for the UE; and means for encoding, at the node, the RAN- originated paging message for transmission to the UE directly or via a core network (CN) node, wherein the RAN-originated paging message is transmitted from the node and received at the UE in accordance with the RAN-based UE paging parameters.

[00132] Example 25 includes the node of Example 24, further comprising: means for storing UE context information in memory of the node when the UE is in a suspended state.

[00133] Example 26 includes the node of any of Examples 24 to 25, wherein the UE paging ID is a RAN-based UE ID or a CN-based UE ID, wherein the RAN-based UE ID includes a cell radio network temporary identifier (C-RNTI), and the CN-based UE ID includes a non-access stratum (NAS) UE ID or a System Architecture Evolution (SAE) temporary mobile subscriber identity (S-TMSI).

[00134] Example 27 includes the node of any of Examples 24 to 26, wherein the RAN- based UE paging parameters include a RAN discontinuous reception (DRX) cycle length paging parameter and a UE paging identifier (ID).

[00135] Example 28 includes the node of any of Examples 24 to 27, further comprising: means for decoding a power saving preference message received from the UE; and determining the RAN DRX cycle length paging parameter based on the power saving preference message.

[00136] Example 29 includes the node of any of Examples 24 to 28, further comprising: means for decoding a message received from the UE that indicates quality of service (QoS) constraints for one or more data radio bearers (DRBs) established for the UE; and determining the RAN DRX cycle length paging parameter based on the QoS constraints for the one or more DRB established for the UE.

[00137] Example 30 includes the node of any of Examples 24 to 29, further comprising: means for decoding a message received from the UE that indicates quality of service (QoS) constraints for one or more data radio bearers (DRBs) established for the UE or applications executed at the UE; and selecting different RAN DRX cycle length paging parameters for each DRB or application category based on the QoS constraints.

[00138] Example 31 includes the node of any of Examples 24 to 30, further comprising: means for decoding a non-access stratum (NAS) UE ID received from the CN node; and decoding NAS discontinuous reception (DRX) paging parameters received from the CN node, wherein the NAS UE ID and the NAS DRX paging parameters received from the CN node are included in the RAN-based UE paging parameters.

[00139] Various techniques, or certain aspects or portions thereof, may take the form of program code (i.e., instructions) embodied in tangible media, such as floppy diskettes, compact disc-read-only memory (CD-ROMs), hard drives, non-transitory computer readable storage medium, or any other machine-readable storage medium wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the various techniques. In the case of program code execution on programmable computers, the computing device may include a processor, a storage medium readable by the processor (including volatile and nonvolatile memory and/or storage elements), at least one input device, and at least one output device. The volatile and non-volatile memory and/or storage elements may be a random-access memory (RAM), erasable programmable read only memory (EPROM), flash drive, optical drive, magnetic hard drive, solid state drive, or other medium for storing electronic data. The node and wireless device may also include a transceiver module (i.e., transceiver), a counter module (i.e., counter), a processing module (i.e., processor), and/or a clock module (i.e., clock) or timer module (i.e., timer). In one example, selected components of the transceiver module can be located in a cloud radio access network (C-RAN). One or more programs that may implement or utilize the various techniques described herein may use an application programming interface (API), reusable controls, and the like. Such programs may be implemented in a high level procedural or object oriented programming language to communicate with a computer system. However, the program(s) may be implemented in assembly or machine language, if desired. In any case, the language may be a compiled or interpreted language, and combined with hardware implementations.

[00140] As used herein, the term "circuitry" may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor

(shared, dedicated, or group), and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. In some embodiments, the circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules. In some embodiments, circuitry may include logic, at least partially operable in hardware.

[00141] It should be understood that many of the functional units described in this specification have been labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom very-large-scale integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.

[00142] Modules may also be implemented in software for execution by various types of processors. An identified module of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions, which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module may not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module.

[00143] Indeed, a module of executable code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network. The modules may be passive or active, including agents operable to perform desired functions.

[00144] Reference throughout this specification to "an example" or "exemplary" means that a particular feature, structure, or characteristic described in connection with the example is included in at least one embodiment of the present technology. Thus, appearances of the phrases "in an example" or the word "exemplary" in various places throughout this specification are not necessarily all referring to the same embodiment.

[00145] As used herein, a plurality of items, structural elements, compositional elements, and/or materials may be presented in a common list for convenience. However, these lists should be construed as though each member of the list is individually identified as a separate and unique member. Thus, no individual member of such list should be construed as a de facto equivalent of any other member of the same list solely based on their presentation in a common group without indications to the contrary. In addition, various embodiments and example of the present technology may be referred to herein along with alternatives for the various components thereof. It is understood that such embodiments, examples, and alternatives are not to be construed as defacto equivalents of one another, but are to be considered as separate and autonomous representations of the present technology.

[00146] Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided, such as examples of layouts, distances, network examples, etc., to provide a thorough understanding of embodiments of the technology. One skilled in the relevant art will recognize, however, that the technology can be practiced without one or more of the specific details, or with other methods, components, layouts, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the technology.

[00147] While the forgoing examples are illustrative of the principles of the present technology in one or more particular applications, it will be apparent to those of ordinary skill in the art that numerous modifications in form, usage and details of implementation can be made without the exercise of inventive faculty, and without departing from the principles and concepts of the technology. Accordingly, it is not intended that the technology be limited, except as by the claims set forth below.

Claims

CLAIMS What is claimed is:

1. An apparatus of a base station operable to provide paging messages to a user equipment (UE), the base station comprising:

one or more processors configured to:

determine, at the base station, radio access network (RAN)-based UE paging parameters for configuration of a UE when the UE is in a suspended state, wherein UE context information for the UE is stored in the memory of the base station when the UE is in the suspended state; encode, at the base station, the RAN-based UE paging parameters for transmission to the UE;

generate, at the base station, a RAN-originated paging message for the UE when downlink data is received at the base station for the UE; and encode, at the base station, the RAN-originated paging message for transmission to the UE directly or via a core network (CN) node, wherein the RAN-originated paging message is transmitted from the base station and received at the UE in accordance with the RAN-based UE paging parameters; and

memory interfaced with the one or more processors, wherein the memory is configured to store the RAN-based UE paging parameters at the base station.

2. The apparatus of claim 1, further comprising a transceiver configured to:

transmit the RAN-based UE paging parameters to the UE; and transmit the RAN-originated paging message to the UE.

3. The apparatus of claim 1, wherein the RAN-based UE paging parameters include one or more of: a RAN discontinuous reception (DRX) cycle length paging parameter or a UE paging identifier (ID). The apparatus of claim 3, wherein the UE paging ID is a RAN-based UE ID or a CN-based UE ID, wherein the RAN-based UE ID includes a cell radio network temporary identifier (C-RNTI), and the CN-based UE ID includes a non-access stratum (NAS) UE ID or a System Architecture Evolution (SAE) temporary mobile subscriber identity (S-TMSI).

The apparatus of claim 3, wherein the one or more processors are further configured to:

decode a power saving preference message received from the UE; and determine the RAN DRX cycle length paging parameter based on the power saving preference message.

decode a message received from the UE or the CN node that indicates quality of service (QoS) constraints for one or more data radio bearers (DRBs) established for the UE; and

determine the RAN DRX cycle length paging parameter based on the QoS constraints for the one or more DRB established for the UE.

decode a message received from the UE that indicates quality of service (QoS) constraints for one or more data radio bearers (DRBs) established for the UE or applications executed at the UE; and

select different RAN DRX cycle length paging parameters for each DRB or application category based on the QoS constraints.

The apparatus of claim 1, wherein the one or more processors are further configured to:

decode a non-access stratum (NAS) UE ID received from the CN node; and decode NAS discontinuous reception (DRX) paging parameters received from the CN node,

wherein the NAS UE ID and the NAS DRX paging parameters received from the CN node are included in the RAN-based UE paging parameters.

An apparatus of a user equipment (UE) operable to decode paging messages received from a base station, the UE comprising:

one or more processors configured to:

decode, at the UE, radio access network (RAN)-based UE paging parameters received from the base station, wherein the RAN-based UE paging parameters includes one or more of a RAN discontinuous reception (DRX) cycle length paging parameter of the base station or a UE paging identifier (ID);

decode, at the UE, a RAN-originated paging message received from the base station when the UE is in a suspended state or an idle state, wherein the RAN-originated paging message is received at the UE when downlink data for the UE is stored at the base station and in accordance with the RAN-based UE paging parameters; and

initiate, at the UE, a radio resource control (RRC) connected state to retrieve the downlink data from the base station after receiving the RAN-originated paging message; and

memory interfaced with the one or more processors, wherein the memory is configured to store the RAN-based UE paging parameters received from the base station.

The apparatus of claim 9, further comprising a transceiver configured to: receive the RAN-based UE paging parameters from the base station; receive the RAN-originated paging message from the base station in accordance with the RAN-based UE paging parameters; and

receive the downlink data from the base station. The apparatus of claim 9, wherein the memory is further configured to store UE context information for the UE when the UE is in the suspended state.

The apparatus of claim 9, wherein the UE paging ID is a RAN-based UE ID or a core network (CN) based UE ID, wherein the RAN-based UE ID includes a cell radio network temporary identifier (C-RNTI), and the CN-based UE ID includes a non-access stratum (NAS) UE ID or a System Architecture Evolution (SAE) temporary mobile subscriber identity (S-TMSI).

The apparatus of any of claims 9 to 12, wherein the one or more processors are further configured to encode a power saving preference message for transmission to the base station, wherein the power saving preference message enables the base station to configure the RAN DRX cycle length paging parameter.

The apparatus of any of claims 9 to 12, wherein the one or more processors are further configured to encode a message for transmission to the base station that indicates quality of service (QoS) constraints for one or more data radio bearers (DRBs) established for the UE, wherein the message containing the QoS constraints for the one or more DRBs enables the base station to configure the RAN DRX cycle length paging parameter.

The apparatus of claim 9, wherein the one or more processors are further configured to encode a message for transmission to the base station that indicates quality of service (QoS) constraints for one or more data radio bearers (DRBs) established for the UE or applications executed at the UE, wherein the message enables the base station to configure different RAN DRX cycle length paging parameters for each DRB or application category based on the QoS constraints.

At least one machine readable storage medium having instructions embodied thereon for providing paging messages from a node to a user equipment (UE), the instructions when executed by one or more processors perform the following:

determining, at the node, radio access network (RAN)-based UE paging parameters for configuration of a UE;

encoding, at the node, the RAN-based UE paging parameters for transmission to the UE;

generating, at the node, a RAN-originated paging message for the UE when downlink data is received for the UE; and

encoding, at the node, the RAN-originated paging message for transmission to the UE directly or via a core network (CN) node, wherein the RAN-originated paging message is transmitted from the node and received at the UE in accordance with the RAN-based UE paging parameters.

The at least one machine readable storage medium of claim 16, further comprising instructions when executed perform the following: storing UE context information in memory of the node when the UE is in a suspended state.

The at least one machine readable storage medium of claim 16, wherein the UE paging ID is a RAN-based UE ID or a CN-based UE ID, wherein the RAN-based UE ID includes a cell radio network temporary identifier (C- RNTI), and the CN-based UE ID includes a non-access stratum (NAS) UE ID or a System Architecture Evolution (SAE) temporary mobile subscriber identity (S-TMSI).

The at least one machine readable storage medium of claim 16, wherein the RAN-based UE paging parameters includes one or more of: a RAN discontinuous reception (DRX) cycle length paging parameter or a UE paging identifier (ID).

The at least one machine readable storage medium of claim 19, further comprising instructions when executed perform the following: decoding a power saving preference message received from the UE; and determining the RAN DRX cycle length paging parameter based on the power saving preference message.

The at least one machine readable storage medium of claim 19, further comprising instructions when executed perform the following:

decoding a message received from the UE that indicates quality of service (QoS) constraints for one or more data radio bearers (DRBs) established for the UE; and

determining the RAN DRX cycle length paging parameter based on the QoS constraints for the one or more DRB established for the UE.

decoding a message received from the UE that indicates quality of service (QoS) constraints for one or more data radio bearers (DRBs) established for the UE or applications executed at the UE; and

selecting different RAN DRX cycle length paging parameters for each DRB or application category based on the QoS constraints.

The at least one machine readable storage medium of claim 16, further comprising instructions when executed perform the following:

decoding a non-access stratum (NAS) UE ID received from the CN node; and

decoding NAS discontinuous reception (DRX) paging parameters received from the CN node,