1. Patent Search
  2. Details

EXTENDED DISCONTINUOUS RECEIVE (eDRX) CYCLES

20190158311 ยท 2019-05-23

    Inventors

    Cpc classification

    International classification

    Abstract

    A core network node (e.g., Serving GPRS Support Node), a radio access network node (e.g., Base Station Subsystem) and various methods are described herein for implementing longer paging cycles (e.g., Extended Discontinuous Receive (eDRX) cycles) for wireless devices in a wireless communication network.

    Claims

    1. A core network (CN) node configured to interact with a radio access network (RAN) node and a wireless device, the CN node comprising: a processor; and, a memory that stores processor-executable instructions, wherein the processor interfaces with the memory to execute the processor-executable instructions, whereby the CN node is operable to: register the wireless device; receive an Internet Protocol (IP) packet destined for the wireless device; buffer the IP packet for a predetermined time; calculate a next occurrence of a nominal paging group for the wireless device; transmit a page request associated with the wireless device to the RAN node, wherein the page request is transmitted before the next occurrence of the nominal paging group for the wireless device; receive a page response from the RAN node; and upon receipt of the page response, transmit the IP packet to the RAN node for delivery to the wireless device.

    2. The CN node of claim 1, wherein the CN node is operable to register the wireless device upon receiving a Routing Area Update (RAU) request from the wireless device, wherein the RAU request comprises an International Mobile Subscriber Identity (IMSI), an extended Discontinuous Receive Cycle (eDRX) cycle, and an estimated coverage class of the wireless device.

    3. The CN node of claim 1, wherein the CN node is operable to perform the register operation by using system information received from the RAN node, wherein the system information indicates for each of one or more cells managed by the RAN node whether an extended Discontinuous Receive Cycle (eDRX) cycle is supported.

    4. The CN node of claim 1, wherein each of one or more cells managed by the RAN node supports a set of extended Discontinuous Receive Cycle (eDRX) cycle lengths and each member of the set of eDRX cycle lengths occurs an integral number of times within a Time Division Multiple Access (TDMA) frame number (FN) space.

    5. The CN node of claim 1, wherein the CN node is further operable to perform the calculate operation by utilizing (1) an International Mobile Subscriber Identity (IMSI), an extended Discontinuous Receive Cycle (eDRX) cycle, and an estimated coverage class associated with the wireless device; and (2) Time Division Multiple Access (TDMA) frame number (FN) information received from the RAN node indicating ongoing TDMA frame transmissions within an overall TDMA FN space for each of one or more cells managed by the RAN node.

    6. The CN node of claim 1, wherein the page request comprises at least an indication of an extended Discontinuous Receive Cycle (eDRX) cycle, and an estimated coverage class of the wireless device.

    7. A method in a core network (CN) node configured to interact with a radio access network (RAN) node and a wireless device, the method comprising: registering the wireless device; receiving an Internet Protocol (IP) packet destined for the wireless device; buffering the IP packet for a predetermined time; calculating a next occurrence of a nominal paging group for the wireless device; transmitting a page request associated with the wireless device to the RAN node, wherein the page request is transmitted before the next occurrence of the nominal paging group for the wireless device; receiving a page response from the RAN node; and upon receipt of the page response, transmitting the IP packet to the RAN node for delivery to the wireless device.

    8. The method of claim 7, wherein the registering step further comprises receiving a Routing Area Update (RAU) request from the wireless device, wherein the RAU request comprises an International Mobile Subscriber Identity (IMSI), an extended Discontinuous Receive Cycle (eDRX) cycle, and an estimated coverage class of the wireless device.

    9. The method of claim 7, wherein the registering step further comprises using system information received from the RAN node, wherein the system information indicates for each of one or more cells managed by the RAN node whether an extended Discontinuous Receive Cycle (eDRX) cycle is supported.

    10. The method of claim 7, wherein each of one or more cells managed by the RAN node supports a set of extended Discontinuous Receive Cycle (eDRX) cycle lengths and each member of the set of eDRX cycle lengths occurs an integral number of times within a Time Division Multiple Access (TDMA) frame number (FN) space.

    11. The method of claim 7, wherein the calculating step further comprises utilizing (1) an International Mobile Subscriber Identity (IMSI), an extended Discontinuous Receive Cycle (eDRX) cycle, and an estimated coverage class associated with the wireless device; and (2) Time Division Multiple Access (TDMA) frame number (FN) information received from the RAN node indicating ongoing TDMA frame transmissions within an overall TDMA FN space for each of one or more cells managed by the RAN node.

    12. The method of claim 7, wherein the page request comprises at least an indication of an extended Discontinuous Receive Cycle (eDRX) cycle, and an estimated coverage class of the wireless device.

    13. A radio access network (RAN) node configured to manage one or more cells and further configured to interact with a wireless device and a core network (CN) node, the RAN node comprising: a processor; and, a memory that stores processor-executable instructions, wherein the processor interfaces with the memory to execute the processor-executable instructions, whereby the radio access network node is operable to: transmit, to the CN node, a registration request associated with the wireless device; receive, from the CN node, a first page request associated with the wireless device, wherein the first page request is received before a next occurrence of a nominal paging group for the wireless device; and, calculate the next occurrence of the nominal paging group for the wireless device using information in the first page request.

    14. The RAN node of claim 13, wherein the RAN node is further operable to: transmit, to the wireless device, a second page request at the calculated next occurrence of the nominal paging group for the wireless device; receive, from the wireless device, a first page response; transmit, to the CN node, a second page response; receive, from the CN node, an Internet Protocol (IP) packet for the wireless device; and, transmit the IP packet to the wireless device.

    15. The RAN node of claim 13, wherein the registration request is a Routing Area Update (RAU) request which comprises an International Mobile Subscriber Identity (IMSI), an extended Discontinuous Receive Cycle (eDRX) cycle, and an estimated coverage class of the wireless device.

    16. The RAN node of claim 13, wherein the RAN node prior to receiving the first page request is operable to transmit, to the CN node, Time Division Multiple Access (TDMA) frame number (FN) information associated with ongoing TDMA frame transmissions within an overall TDMA FN space for the one or more managed cells.

    17. The RAN node of claim 13, wherein the RAN node is further operable to transmit, to the CN node, system information that indicates for each of the one or more managed cells whether an extended Discontinuous Receive Cycle (eDRX) cycle is supported.

    18. The RAN node of claim 13, wherein each of the one or more managed cells supports a set of extended Discontinuous Receive Cycle (eDRX) cycle lengths and each member of the set of eDRX cycle lengths occurs an integral number of times within a Time Division Multiple Access (TDMA) frame number (FN) space.

    19. The RAN node of claim 13, wherein the first page request comprises at least an indication of an extended Discontinuous Receive Cycle (eDRX) cycle, and an estimated coverage class of the wireless device.

    20. A method in a radio access network (RAN) node configured to manage one or more cells and further configured to interact with a wireless device and a core network (CN) node, the method comprising: transmitting, to the CN node, a registration request associated with the wireless device; receiving, from the CN node, a first page request associated with the wireless device, wherein the first page request is received before a next occurrence of a nominal paging group for the wireless device; and, calculating the next occurrence of the nominal paging group for the wireless device using information in the first page request.

    21. The method of claim 20, further comprising: transmitting, to the wireless device, a second page request at the calculated next occurrence of the nominal paging group for the wireless device; receiving, from the wireless device, a first page response; transmitting, to the CN node, a second page response; receiving, from the CN node, an Internet Protocol (IP) packet for the wireless device; and, transmitting the IP packet to the wireless device.

    22. The method of claim 20, wherein the registration request is a Routing Area Update (RAU) request which comprises an International Mobile Subscriber Identity (IMSI), an extended Discontinuous Receive Cycle (eDRX) cycle, and an estimated coverage class of the wireless device.

    23. The method of claim 20, further comprising, prior to receiving the first page request, transmitting , to the CN node, Time Division Multiple Access (TDMA) frame number (FN) information associated with ongoing TDMA frame transmissions within an overall TDMA FN space for the one or more managed cells.

    24. The method of claim 20, further comprising transmitting, to the CN node, system information that indicates for each of the one or more managed cells whether an extended Discontinuous Receive Cycle (eDRX) cycle is supported.

    25. The method of claim 20, wherein each of the one or more managed cells supports a set of extended Discontinuous Receive Cycle (eDRX) cycle lengths and each member of the set of eDRX cycle lengths occurs an integral number of times within a Time Division Multiple Access (TDMA) frame number (FN) space.

    26. The method of claim 20, wherein the first page request comprises at least an indication of an extended Discontinuous Receive Cycle (eDRX) cycle, and an estimated coverage class of the wireless device.

    Description

    BRIEF DESCRIPTION OF THE DRAWINGS

    [0054] A more complete understanding of the present disclosure may be obtained by reference to the following detailed description when taken in conjunction with the accompanying drawings:

    [0055] FIG. 1 (PRIOR ART) is a graph that illustrates simulated details about the battery lifetime of a wireless device for different triggering intervals when implementing the PSM functionality and the eDRX functionality;

    [0056] FIG. 2 is a diagram of an exemplary wireless communication network which includes a CN node and multiple RAN nodes which are configured in accordance with an embodiment of the present disclosure;

    [0057] FIG. 3 is a flowchart of a method implemented in the CN node in accordance with an embodiment of the present disclosure;

    [0058] FIG. 4 is a block diagram illustrating an exemplary structure of the CN node configured in accordance with an embodiment of the present disclosure;

    [0059] FIG. 5 is a flowchart of a method implemented in the RAN node in accordance with an embodiment of the present disclosure; and,

    [0060] FIG. 6 is a block diagram illustrating an exemplary structure of the RAN node configured in accordance with an embodiment of the present disclosure.

    DETAILED DESCRIPTION

    [0061] A discussion is provided first herein to describe an exemplary wireless communication network that includes a CN node (e.g., SGSN) and multiple RAN nodes (e.g., BSSs) which are configured to interact with multiple wireless devices (e.g., MTC devices) in accordance with the present disclosure (illustrated in FIG. 2). Then, a discussion is provided about several technical features (e.g., working assumptions) where one or more of these technical features can be implemented by the CN node and the RAN node as a basis to help address the aforementioned problems associated with the prior art and realize a complete solution for implementing the eDRX functionality. Finally, a discussion is provided to explain the functionalities-configurations of the CN node (e.g., SGSN) and the RAN node (e.g., BSS) in accordance with the present disclosure (illustrated in FIGS. 3-6).

    Exemplary Wireless Communication Network 200

    [0062] Referring to FIG. 2, there is illustrated an exemplary wireless communication network 200 in accordance with the present disclosure. The wireless communication network 200 includes a core network 206 (which comprises a CN node 207) and multiple RAN nodes 202.sub.1 and 202.sub.2 (only two shown) which interface with multiple wireless devices 204.sub.1, 204.sub.2, 204.sub.3 . . . 204.sub.n. The wireless communication network 200 also includes many well-known components, but for clarity, only the components needed to describe the features of the present disclosure are described herein. Further, the wireless communication network 200 is described herein as being a GSM/EGPRS wireless communication network 200 which is also known as an EDGE wireless communication network 200. However, those skilled in the art will readily appreciate that the techniques of the present disclosure which are applied to the GSM/EGPRS wireless communication network 200 are generally applicable to other types of wireless communication systems, including, for example, WCDMA, LTE, and WiMAX systems.

    [0063] The wireless communication network 200 includes the RAN nodes 202.sub.1 and 202.sub.2 (only two shown) which provide network access to the wireless devices 204.sub.1, 204.sub.2, 204.sub.3 . . . 204.sub.n. In this example, the RAN node 202.sub.1 is providing network access to wireless device 204.sub.1 while the RAN node 202.sub.2 is providing network access to wireless devices 204.sub.2, 204.sub.3 . . . 204.sub.n. The RAN nodes 202.sub.1 and 202.sub.2 are connected to the core network 206 (e.g., EGPRS core network 206) and, in particular, to the CN node 207. The core network 206 is connected to an external packet data network (PDN) 208, such as the Internet, and a server 210 (only one shown). The wireless devices 204.sub.1, 204.sub.2, 204.sub.3 . . . 204.sub.n may communicate with one or more servers 210 (only one shown) connected to the core network 206 and/or the PDN 208.

    [0064] The wireless devices 204.sub.1, 204.sub.2, 204.sub.3 . . . 204.sub.n may refer generally to an end terminal (user) that attaches to the wireless communication network 200, and may refer to either a MTC device (e.g., a smart meter) or a non-MTC device. Further, the term wireless device is generally intended to be synonymous with the term mobile device, mobile station (MS). User Equipment, or UE, as that term is used by 3GPP, and includes standalone wireless devices, such as terminals, cell phones, smart phones, tablets, and wireless-equipped personal digital assistants, as well as wireless cards or modules that are designed for attachment to or insertion into another electronic device, such as a personal computer, electrical meter, etc.

    [0065] Likewise, unless the context clearly indicates otherwise, the term RAN node 202.sub.1 and 202.sub.2 is used herein in the most general sense to refer to a base station, a wireless access node, or a wireless access point in a wireless communication network 200, and may refer to RAN nodes 202.sub.1 and 202.sub.2 that are controlled by a physically distinct radio network controller as well as to more autonomous access points, such as the so-called evolved Node Bs (eNodeBs) in Long-Term Evolution (LTE) networks.

    [0066] Each wireless device 204.sub.1, 204.sub.2, 204.sub.3 . . . 204.sub.n may include a transceiver circuit 210.sub.1, 210.sub.2, 210.sub.3 . . . 210.sub.n for communicating with the RAN nodes 202.sub.1 and 202.sub.2, and a processing circuit 212.sub.1, 212.sub.2, 212.sub.3 . . . 212.sub.n for processing signals transmitted from and received by the transceiver circuit 210.sub.1, 110.sub.2, 210.sub.3 . . . 210.sub.n and for controlling the operation of the corresponding wireless device 204.sub.1, 204.sub.2, 204.sub.3 . . . 204.sub.n. The transceiver circuit 210.sub.1, 210.sub.2, 210.sub.3 . . . 210.sub.n may include a transmitter 214.sub.1, 214.sub.2, 214.sub.3 . . . 214.sub.n and a receiver 216.sub.1, 216.sub.2, 216.sub.3 . . . 216.sub.n, which may operate according to any standard, e.g., the GSM/EDGE standard. The processing circuit 212.sub.1, 212.sub.2, 212.sub.3 . . . 212.sub.n may include a processor 218.sub.1, 218.sub.2, 218.sub.3 . . . 218.sub.n and a memory 220.sub.1, 220.sub.2, 220.sub.3 . . . 220.sub.n for storing program code for controlling the operation of the corresponding wireless device 204.sub.1, 204.sub.2, 204.sub.3 . . . 204.sub.n. The program code may include code for performing the procedures as described hereinafter (e.g., implementing paging cycles in a cellular network, generating a Routing Area Update request including an indication of an eDRX cycle length and a coverage class associated with the device, and performing a registration process including transmitting the Routing Area Update request).

    [0067] Each RAN node 202.sub.1 and 202.sub.2 may include a transceiver circuit 222.sub.1 and 222.sub.2 for communicating with wireless devices 204.sub.1, 204.sub.2, 204.sub.3 . . . 204.sub.n, a processing circuit 224.sub.1 and 224.sub.2 for processing signals transmitted from and received by the transceiver circuit 222.sub.1 and 222.sub.2 and for controlling the operation of the corresponding RAN node 202.sub.1 and 202.sub.2, and a network interface 226.sub.1 and 226.sub.2 for communicating with the core network 206. The transceiver circuit 222.sub.1 and 222.sub.2 may include a transmitter 228.sub.1 and 228.sub.2 and a receiver 230.sub.1 and 230.sub.2, which may operate according to any standard, e.g., the GSM/EDGE standard. The processing circuit 224.sub.1 and 224.sub.2 may include a processor 232.sub.1 and 232.sub.2, and a memory 234.sub.1 and 234.sub.2 for storing program code for controlling the operation of the corresponding RAN node 202.sub.1 and 202.sub.2. The program code may include code for performing the procedures as described hereinafter (e.g., transmitting a RAU request associated with a wireless device to a CN node, receiving a page request from the CN node for the wireless device, using information in the page request to calculate the next occurrence of the nominal paging group for the wireless device, and transmitting system information to the CN node regarding the one or more managed cells, wherein the system information for each of the one or more managed cells indicates: (1) whether an eDiscontinuous Receive Cycle (eDRX) cycle is supported; and (2) a maximum eDRX cycle length supported within a set of eDRX cycle lengths).

    [0068] The CN node 207 (e.g., SGSN 207, Mobility Management Entity (MME) 207) may include a transceiver circuit 236 for communicating with the RAN nodes 202.sub.1 and 202.sub.2, a processing circuit 238 for processing signals transmitted from and received by the transceiver circuit 236 and for controlling the operation of the CN node 207, and a network interface 240 for communicating with the RAN nodes 202.sub.1 and 202.sub.2. The transceiver circuit 236 may include a transmitter 242 and a receiver 244, which may operate according to any standard, e.g., the GSM/EDGE standard. The processing circuit 238 may include a processor 246 and a memory 248 for storing program code for controlling the operation of the CN node 207. The program code may include code for performing the procedures as described hereinafter (e.g., receiving a packet for delivery to a wireless device, buffering the packet, receiving/maintaining BSS specific TDMA FN information, receiving system information indicating support for eDRX and a maximum supported eDRX cycle length, determining a paging area, an eDRX cycle length, and a coverage class associated with the wireless device, determining a nominal paging group for the device using an IMSI, the eDRX cycle length, and the coverage class associated with the wireless device, maintaining a counter, transmitting a paging request including the counter value, the IMSI, the eDRX cycle length, and the coverage class associated with the wireless device before the next occurrence of the nominal paging group for the wireless device, incrementing the counter upon determining failure to receive a page response, resetting the counter upon receipt of a page response, and forwarding the buffered packet for delivery to the wireless device).

    Complete Solution for Implementing eDRX

    [0069] As discussed in the Background Section, the traditional SGSN (traditional CN node) upon receiving an IP packet (e.g., containing a trigger) for delivery to a target wireless device that is making use of eDRX will respond by immediately sending a corresponding paging request to a BSS (traditional RAN node). When this occurs, there is the possibility that the next paging based instance of reachability for the target wireless device may occur well beyond the point in time when the BSS receives the paging request. This can be problematic considering that (a) the BSS may be limited in how long the BSS can buffer the paging request while waiting for the next paging opportunity for the target wireless device operating in eDRX mode, and (b) the SGSN may consider the paging request to have failed or the target wireless device to be unreachable if the SGSN does not receive a corresponding page response from the BSS within a relatively short time frame. These problems and other problems are addressed by the present disclosure as discussed hereinafter.

    [0070] As a first step towards realizing a complete solution for eDRX, a basic technical feature can be adopted whereby the SGSN 207 (CN node 207) will have the ability to buffer a downlink IP packet 305 intended for a target wireless device 204.sub.3 (for example) for an extended time period (e.g., up to 1 hour). This leaves open the challenge of how the SGSN 207 can now determine an appropriate time for taking further steps towards delivering the buffered IP packet 305 to the target wireless device 204.sub.3. This challenge can be met as described hereinafter.

    [0071] Technical Feature 1: An SGSN 207 will have the ability to buffer a downlink IP packet 305 for an extended time period prior to delivering the buffered IP packet 305 to the target wireless device 204.sub.3.

    [0072] Synchronization and TDMA FN Information

    [0073] In practice, it can be expected that all cells 321.sub.1, 321.sub.2 . . . 321.sub.n (for example) managed by any given BSS 202.sub.2 (for example) will be synchronized from a TDMA FN perspective to a high degree, such that the transmission of TDMA FN sequences transmitted over the radio interface of these cells 321.sub.1, 321.sub.2 . . . 321.sub.n will at most differ by about, for example, a few milliseconds. As part of Gb interface management procedures, wherein the Gb interface connects the BSS 202.sub.2 (RAN node 202.sub.2) to the SGSN 207 (CN node 207) in the GPRS core network 206, knowledge of BSS specific TDMA FN information 307 can be conveyed from the BSS 202.sub.2 to the SGSN 207, thereby providing the SGSN 207 with near real time knowledge (e.g., accurate within a few milliseconds) of ongoing TDMA frame transmissions within the overall TDMA FN space for each cell 321.sub.1, 321.sub.2 . . . 321.sub.n managed by any given BSS 202.sub.2. This near real time knowledge of ongoing TDMA frame transmissions combined with knowledge of the International Mobile Subscriber Identity (IMSI), eDRX cycle, and coverage class associated with a target wireless device 204.sub.3 (for example) allows the SGSN 207 to calculate the next occurrence of the nominal paging group for the target wireless device 204.sub.3. In this regard, see the 3GPP TSG-GERAN Meeting #63 Tdoc GP-140605, entitled GSM Evolution for cellular IoT-PCH Overview dated Aug. 25-29, 2014, which discusses an IMSI based hashing algorithm that takes into account the eDRX cycle length and coverage class of a target wireless device to determine the nominal paging group for the target wireless device (the entire contents of this document are hereby incorporated herein by reference for all purposes).

    [0074] Technical Feature 2: The frame structure in all cells 321.sub.1, 321.sub.2 . . . 321.sub.n served by a BSS 202.sub.2 belonging to any given vendor will be aligned, for example, on about a 5 or 10 milliseconds level.

    [0075] Technical Feature 3: The Gb interface management procedures will be enhanced to support the transmission of BSS specific TDMA FN information 307 from the BSS 202.sub.2 to the SGSN 207, which may then be maintained by the SGSN 207 indefinitely.

    [0076] Technical Feature 4: The SGSN 207 uses the IMSI, eDRX cycle, and coverage class of a target wireless device 204.sub.3 (for example) and the TDMA FN information 307 to determine the ongoing occurrences of the nominal paging group for that target wireless device 204.sub.3 (for example) within the context of each BSS 202.sub.2 managing cells 321.sub.1, 321.sub.2 . . . 321.sub.n in the corresponding paging area.

    [0077] eDRX in GERAN

    [0078] The Technical Features 1-4 or any combination thereof listed above could be used as a basis for further developing a full solution for eDRX for GERAN (i.e., eDRX for Study of Power Saving for MTC Devices (uPoD) and GSM Evolution based Cellular Internet of Things (CIoT)) as described below.

    [0079] Selecting an eDRX Cycle

    [0080] A cell 321.sub.1, 321.sub.2 . . . 321.sub.n that supports eDRX shall support a set of eDRX cycle lengths subject to the requirement that each member of the set shall occur an integral number of times within the full TDMA FN space. This set of eDRX cycle lengths, an example of which is shown in TABLE 1, shall be common to all GERAN cells 321.sub.1, 321.sub.2 . . . 321.sub.n that support eDRX, since it is based on parsing the GERAN TDMA FN space.

    TABLE-US-00001 TABLE 1 Set of eDRX Cycle Lengths Target Extended DRX Extended Number of 51-MFs Extended DRX Cycle Value DRX Cycle per Extended DRX Cycle Cycles per TDMA (EXTENDED_DRX) Length (EXTENDED_DRX_MFRMS) FN Space 0 ~30 seconds 128 416 1 ~60 seconds 256 208 2 ~2 minutes 512 104 3 ~4 minutes 1024 52 4 ~6.5 minutes 1664 32 5 ~8 minutes 2048 26 6 ~13 minutes 3328 16 7 ~16 minutes 4096 13 8 ~26 minutes 6656 8 9 ~52 minutes 13312 4 Note 1: 53248 51-multiframes (MFs) occur with the TDMA FN space (i.e., 2715648 TDMA frames). Note 2: All remaining EXTENDED_DRX values may be reserved.

    [0081] If the maximum amount of time that any given SGSN 207 implementation supports buffering a downlink IP packet 305 before sending the IP packet 305 to the BSS 202.sub.2 is X minutes, then each cell 321.sub.1, 321.sub.2 . . . 321.sub.n in a RAI managed by that SGSN 207 should indicate a maximum eDRX cycle length that does not exceed X minutes. As such, a cell 321.sub.1, 321.sub.2 . . . 321.sub.n that sends system information 303 indicating that the cell 321.sub.1, 321.sub.2 . . . 321.sub.n supports eDRX shall therefore also indicate the maximum eDRX cycle length supported within the set. To accomplish this: [0082] The Routing Area Update (RAU) Request 301 shall be modified to include an indication of the eDRX cycle length selected (e.g., as desired or requested) by the wireless device 204.sub.3 (for example) and the estimated coverage class of the wireless device 204.sub.3. [0083] After the wireless device 204.sub.3 (for example) registers (e.g., performs a RAU), the serving SGSN 207 knows the wireless device's (a) paging area, (b) an eDRX cycle length (e.g., a requested or desired eDRX cycle length as indicated by the EXTENDED_DRX value of TABLE 1 included in the RAU Request 301), (c) estimated coverage class (e.g., also included in the RAU Request 301); and (d) the wireless device's IMSI (e.g., also included in the RAU Request 301). Therefore, the serving SGSN 207 knows how to determine the ongoing occurrences of the wireless device's nominal paging group for each BSS 202.sub.2 (for example) that is managing cell(s) 321.sub.1, 321.sub.2 . . . 321.sub.n in the corresponding paging area.

    [0084] Technical Feature 5: Each member of the set of eDRX cycle lengths supported in a cell 321.sub.1, 321.sub.2 . . . 321.sub.n occurs an integral number of times within the TDMA FN space, where the set of possible eDRX cycle lengths shall be common to all GERAN cells 321.sub.1, 321.sub.2 . . . 321.sub.n that support eDRX.

    [0085] Technical Feature 6: System Information 303 shall indicate if eDRX is supported in a cell 321.sub.1, 321.sub.2 . . . 321.sub.n and the maximum eDRX cycle length of the set allowed in the serving cell 321.sub.1, 321.sub.2 . . . 321.sub.n (see TABLE 1). Further, the indicated maximum eDRX cycle length shall not exceed the maximum time period that the corresponding SGSN 207 can buffer a downlink IP packet 305.

    [0086] Technical Feature 7: The RAU Request 301 shall be modified to include an indication of the eDRX cycle length selected (e.g., as desired or requested) by a wireless device 204.sub.3 (for example) and the wireless device's estimated downlink coverage class.

    [0087] Managing Downlink IP Packets

    [0088] When the SGSN 207 first determines that the SGSN 207 has downlink IP payload 305 for delivery to a given wireless device 204.sub.3 (for example) and the corresponding wireless device's ready-timer is not running, the SGSN 207 calculates the next occurrence of the wireless device's nominal paging group using the IMSI, the eDRX cycle, and the coverage class of the wireless device 204.sub.3 along with the TDMA FN information 307 that the SGSN 207 has for each BSS 202.sub.2 (for example) managing one or more cells 321.sub.1, 321.sub.2 . . . 321.sub.n (for example) in the corresponding paging area. [0089] The SGSN 207 sends a paging request 309 to each BSS 202.sub.2 (one shown in this example) in the paging area shortly before the next occurrence of the wireless device's nominal paging group in the cells 321.sub.1, 321.sub.2 . . . 321.sub.n managed by the BSS 202.sub.2 (one shown in this example) [0090] Each paging request 309 comprises information (e.g., eDRX cycle length, coverage class, and IMSI of the wireless device 204.sub.3) that allows the BSS 202.sub.2 (for example) to determine the next occurrence of the wireless device's nominal paging group. [0091] Upon receiving a paging response 311 from a BSS 202.sub.2 (for example), the SGSN 207 forwards the available IP packet 305 to that BSS 202.sub.2 for delivery to the target wireless device 204.sub.3.

    [0092] Technical Feature 8: Paging requests 309 transmitted from the SGSN 207 to the BSS 202.sub.2 (one shown in this example) shall include an indication of the eDRX cycle length and the estimated coverage class identified by the target wireless device 204.sub.3 (for example) in its last registration (e.g., RAU Request 301).

    [0093] Technical Feature 9: Upon receiving a downlink IP packet 305, the SGSN 207 assumes that the SGSN 207 can buffer the IP packet 305 for an extended time period (e.g., up to 1 hour) with no concern for potential impacts of this buffering on the application server 210 (for example) from which the SGSN 207 received the IP packet 305.

    [0094] Technical Feature 10: The SGSN 207 maintains a running counter that is incremented each time the SGSN 207 fails to receive a page response 311 (associated with a paging request 309 for a specific IP packet 305) from a wireless device 204.sub.3 (for example) and is reset each time the SGSN 207 successfully receives a page response 311, where the value of this running counter is included in each paging request 309 that the SGSN 207 sends to the BSS 202.sub.2 for the corresponding wireless device 204.sub.3 (for example).

    [0095] It is proposed that the Technical Features 1-10 or any combination thereof listed above can be used as the basis for supporting eDRX within GERAN (i.e., eDRX for both uPoD and GSM Evolution based CIoT).

    Basic Functionalities-Configurations of CN node 207 and RAN Node 202.sub.2

    [0096] Referring to FIG. 3, there is a flowchart of a method 300 implemented in the CN node 207 (e.g., SGSN 207) in accordance with an embodiment of the present disclosure. At step 302, the CN node 207 registers a wireless device 204.sub.3 (for example) such that the wireless device 204.sub.3 can receive or transmit IP packets to or from another device such as the application server 210. In one embodiment, the CN node 207 registers the wireless device 204.sub.3 upon receiving a RAU request 301 which comprises an IMSI, an eDRX cycle (e.g., a requested or desired eDRX cycle), and an estimated coverage class of the wireless device 204.sub.3 (see technical feature 7) (see also FIG. 2). If desired, the CN node 207 may perform the register step 302 using the information in the received RAU request 301 and using system information 303 that was previously received from the RAN node 202.sub.2 that manages one or more cells 321.sub.1, 321.sub.2 . . . 321.sub.n in the paging area of the wireless device 204.sub.3. The system information 303 indicates for each of the one or more managed cells 321.sub.1, 321.sub.2 . . . 321.sub.n the following: (1) whether an eDRX cycle is supported; and (2) a maximum eDRX cycle length supported within a set of eDRX cycle lengths (see technical feature 6). For instance, the CN node 207 can use the system information 303 to: (a) ensure that the RAU request 301 for eDRX is accepted only if the corresponding cell(s) 321.sub.1, 321.sub.2 . . . 321.sub.n actually supports eDRX and (b) ensure that the eDRX cycle length requested within the RAU request 301 does not exceed the maximum eDRX cycle length actually supported by the cell(s) 321.sub.1, 321.sub.2 . . . 321.sub.n. Further, each of the one or more managed cells 321.sub.1, 321.sub.2 . . . 321.sub.n can support a set of eDRX cycle lengths and each member of the set of eDRX cycle lengths occurs an integral number of times within a TDMA FN space (technical feature 5 and TABLE 1). In addition, each of the one or more managed cells 321.sub.1, 321.sub.2 . . . 321.sub.n can be synchronized from the TDMA FN perspective to be aligned at about a 5 or 10 milliseconds level (technical feature 2).

    [0097] At step 304, the CN node 207 receives an IP packet 305 from an application server 210 (for example) that is destined for the wireless device 204.sub.3. At step 306, the CN node 207 buffers the IP packet 305 for a predetermined time (e.g., up to one hour) (see technical features 1 and 9). If the system information 303 described above with the registering step 302 is used then the system information 303 could be configured such that the indicated maximum eDRX cycle length for each managed cell 321.sub.1, 321.sub.2 . . . 321.sub.n would not exceed the predetermined time (e.g., up to one hour) that the IP packet 305 is permitted to be buffered by the CN node 207 after the receipt of the IP packet 305 (technical feature 6).

    [0098] At step 308, the CN node 207 calculates a next occurrence of a nominal paging group for the wireless device 204.sub.3. In one example, the CN node 207 performs the calculating step 308 by utilizing (1) an IMSI, an eDRX cycle (e.g., a requested or desired eDRX cycle), and an estimated coverage class associated with the wireless device 204.sub.3 (this information is obtained from the RAU request 301), and (2) TDMA FN information 307 which is received from the RAN node 202.sub.2 and indicates ongoing TDMA frame transmissions within an overall TDMA FN space for each of one or more cells 321.sub.1, 321.sub.2 . . . 321.sub.n which are managed by the RAN node 202.sub.2 (technical features 3 and 4). For example, the CN node 207 can use the IMSI, the eDRX cycle, and the estimated coverage class of the wireless device 204.sub.3 along with the TDMA FN information 307 to calculate the next occurrence of the nominal paging group for the wireless device 204.sub.3 as follows: [0099] The nominal paging group of the wireless device 204.sub.3 occurs once every eDRX cycle. [0100] Assuming the wireless device 204.sub.3 is using coverage class 1 on the downlink then its nominal paging group occurs if the PCH block number=NOMINAL PAGING_GROUP (0 . . .N1)=mod (IMSI, N). [0101] N=number of paging groups on one CCCH within a given eDRX cycle=(number of paging blocks per 51-multiframe of the CCCH)*(Number of 51-MF per negotiated eDRX Cycle=EXTENDED_DRX_MFRMS). [0102] The specific set of PCH blocks comprising the nominal paging group is determined by the actual downlink coverage class of the device 204.sub.3 but will always include the PCH block identified using coverage class 1.

    [0103] The use of the TDMA FN information 307 in this calculation is important because it allows the CN node 207 to determine when the next instance or occurrence of the nominal paging group will occur in the time domain for the wireless device 204.sub.3.

    [0104] At step 310, the CN node 207 transmits a page request 309 associated with the wireless device 204.sub.3 to the RAN node 202.sub.2, wherein the page request 309 is transmitted before, for example at a predetermined or determinable time (e.g., 5 seconds) before, the next occurrence of the nominal paging group for the wireless device 204.sub.3. In one example, the page request 309 comprises an indication of an eDRX cycle (e.g., a requested or desired eDRX cycle), the IMSI and an estimated coverage class of the wireless device 204.sub.3 (this information is obtained from the RAU request 301) (technical feature 8). If desired, the page request 309 can also comprise a value of a running counter that is incremented by the CN node 207 each time a page response (associated with a page request for a specific IP packet) is not received from the wireless device 204.sub.3 and is reset each time a page response (associated with a page request) is received from the wireless device 204.sub.3 (technical feature 10).

    [0105] At step 312, the CN node 207 receives a page response 311 from the RAN node 202.sub.2. Upon receiving the page response 311, the CN node 207 at step 314 transmits the IP packet 305 to the RAN node 202.sub.2 for delivery to the wireless device 204.sub.3. An advantage of the CN node 207 implementing the method 300 is that by deferring the transmission of the page request 309 according to the CN node 207's knowledge of when the next nominal paging group occurs for the wireless device 204.sub.3 the CN node 207 will have a realistic expectation of receiving a corresponding page response 311 from wireless device 204.sub.3 shortly after transmitting the page request 309. This is beneficial since it avoids the page request timeout scenario that would otherwise commonly occur if the CN node 207 were to use legacy procedures. In this regard, when the traditional CN node transmits the page request associated with the wireless device to the RAN node without taking into account the eDRX cycle of the wireless device (i.e., the probability of the traditional CN node transmitting a page request shortly before the occurrence of the next nominal paging group for the wireless device without explicitly taking into account the wireless device's eDRX cycle is low). The penalty incurred by the traditional CN node experiencing the page request timeout scenario is that the traditional CN node may re-attempt paging (using an even greater set of cells for the paging re-attempt), thereby wasting processing power, and wasting signaling capacity on the data link to each RAN node to which it transmits either the initial page request or a re-attempted page request and potentially falsely concluding that the wireless device is unreachable (due to a lack of page response). In addition, without knowing the coverage class of the wireless device the traditional CN node would not be able to indicate the coverage class information in the page request sent to the RAN node and the RAN node would therefore not be able to determine the set of PCH blocks to use for transmitting the page request over the radio interface to the wireless device.

    [0106] Referring to FIG. 4, there is a block diagram illustrating structures of an exemplary CN node 207 (for example) configured in accordance with an embodiment of the present disclosure. In one embodiment, the CN node 207 may comprise a register module 402, a first receive module 404, a buffer module 406, a calculate module 408, a first transmit module 410, a second receive module 412, and a second transmit module 414. The register module 402 is configured to register a wireless device 204.sub.3 (for example) such that the wireless device 204.sub.3 can receive or transmit IP packets to or from another device such as the application server 210 (for example). In one embodiment, the register module 402 is configured to register the wireless device 204.sub.3 upon receiving a RAU request 301 which comprises an IMSI, an eDRX cycle (e.g., a requested or desired eDRX cycle), and an estimated coverage class of the wireless device 204.sub.3 (see technical feature 7). If desired, the register module 402 may register the wireless device 104.sub.3 using the information in the received RAU request 301 and by using system information 303 that was previously received from the RAN node 202.sub.2 that manages one or more cells 321.sub.1, 321.sub.2 . . . 321.sub.n in the paging area of the wireless device 204.sub.3. The system information 303 indicates for each of the one or more managed cells 321.sub.1, 321.sub.2 . . . 321.sub.n the following: (1) whether an eDRX cycle is supported; and (2) a maximum eDRX cycle length supported within a set of eDRX cycle lengths (see technical feature 6). For instance, the register module 402 can use the system information 303 to: (a) ensure that the RAU request 301 for eDRX is accepted only if the corresponding cell(s) 321.sub.1, 321.sub.2 . . . 321.sub.n actually supports eDRX and (b) ensure that the eDRX cycle length requested within the RAU Request 301 does not exceed the maximum eDRX cycle length actually supported by the cell(s) 321.sub.1, 321.sub.2 . . . 321.sub.n. Further, each of the one or more managed cells 321.sub.1, 321.sub.2 . . . 321.sub.n can support a set of eDRX cycle lengths and each member of the set of eDRX cycle lengths occurs an integral number of times within a TDMA FN space (technical feature 5 and TABLE 1). In addition, each of the one or more managed cells 321.sub.1, 321.sub.2 . . . 321.sub.n can be synchronized from the TDMA FN perspective to be aligned at about a 5 or 10 milliseconds level (technical feature 2). The first receive module 404 is configured to receive an IP packet 305 from an application server 210 (for example) that is destined for the wireless device 204.sub.3. The buffer module 406 is configured to buffer the IP packet 305 for a predetermined time (e.g., up to one hour) (see technical features 1 and 9). If the system information 303 described above with the registering step 302 is used then the system information 303 could be configured such that the indicated maximum eDRX cycle length for each managed cell 321.sub.1, 321.sub.2 . . . 321.sub.n would not exceed the predetermined time (e.g., up to one hour) that the IP packet 305 is permitted to be buffered by the CN node 207 after the receipt of the IP packet 305 (technical feature 6).

    [0107] The calculate module 408 is configured to calculate a next occurrence of a nominal paging group for the wireless device 204.sub.3. In one example, the calculate module 408 can perform the calculating operation by utilizing (1) an IMSI, an eDRX cycle (e.g., a requested or desired eDRX cycle), and an estimated coverage class associated with the wireless device 204.sub.3 (this information is obtained from the RAU request 301), and (2) TDMA FN information 307 which is received from the RAN node 202.sub.2 and indicates ongoing TDMA frame transmissions within an overall TDMA FN space for each of one or more cells 321.sub.1, 321.sub.2 . . . 321.sub.n which are managed by the RAN node 202.sub.2 (technical features 3 and 4). For example, the CN node 207 can use the IMSI, the eDRX cycle, and the estimated coverage class of the wireless device 204.sub.3 along with the TDMA FN information 307 to calculate the next occurrence of the nominal paging group for the wireless device 204.sub.3 as follows: [0108] The nominal paging group of the wireless device 204.sub.3 occurs once every eDRX cycle. [0109] Assuming the wireless device 204.sub.3 is using coverage class 1 on the downlink then its nominal paging group occurs if the PCH block number=NOMINAL PAGING_GROUP (0 . . . N1)=mod (IMSI, N). [0110] N=number of paging groups on one CCCH within a given eDRX cycle=(number of paging blocks per 51-multiframe of the CCCH)*(Number of 51-MF per negotiated eDRX Cycle=EXTENDED_DRX_MFRMS). [0111] The specific set of PCH blocks comprising the nominal paging group is determined by the actual downlink coverage class of the device 204.sub.3 but will always include the PCH block identified using coverage class 1.

    [0112] The use of the TDMA FN information 307 is important because it allows the CN node 207 to determine when the next instance or occurrence of the nominal paging group will occur in the time domain for the wireless device 204.sub.3.

    [0113] The first transmit module 410 is configured to transmit a page request 309 associated with the wireless device 204.sub.3 to the RAN node 202.sub.2, wherein the page request 309 is transmitted before, for example at a predetermined or determinable time (e.g., 5 seconds) before, the next occurrence of the nominal paging group for the wireless device 204.sub.3. In one example, the page request 309 comprises an indication of an eDRX cycle (e.g., a requested or desired eDRX cycle), the IMSI and an estimated coverage class of the wireless device 204.sub.3 (this information is obtained from the RAU request 301) (technical feature 8). If desired, the page request 309 can also comprise a value of a running counter that is incremented by the CN node 207 each time a page response (associated with a page request for a specific IP packet) is not received from the wireless device 204.sub.3 and is reset each time a page response (associated with a page request) is received from the wireless device 204.sub.3 (technical feature 10).

    [0114] The second receive module 412 is configured to receive a page response 311 from the RAN node 202.sub.2. The second transmit module 414 upon receipt of the page response 311 is configured to transmit the IP packet 305 to the RAN node 202.sub.2 for delivery to the wireless device 204.sub.3.

    [0115] As those skilled in the art will appreciate, the above-described modules 402, 404, 406, 408, 410, 412 and 414 of the CN node 207 (e.g., SGSN 207) may be implemented separately as suitable dedicated circuits. Further, the modules 402, 404, 406, 408, 410, 412 and 414 can also be implemented using any number of dedicated circuits through functional combination or separation. In some embodiments, the modules 402, 404, 406, 408, 410, 412 and 414 may be even combined in a single application specific integrated circuit (ASIC). As an alternative software-based implementation, the CN node 207 (e.g., SGSN 207) may comprise a memory 248, a processor 246 (including but not limited to a microprocessor, a microcontroller or a Digital Signal Processor (DSP), etc.) and a transceiver 236. The memory 248 stores machine-readable program code executable by the processor 246 to cause the CN node 207 (e.g., SGSN 207) to perform the steps of the above-described method 300.

    [0116] Referring to FIG. 5, there is a flowchart of a method 500 implemented in a RAN node 202.sub.2 (for example) in accordance with an embodiment of the present disclosure. At step 502, the RAN node 202.sub.2 transmits a registration request 301 associated with the wireless device 204.sub.3 (for example) to the CN node 207. In one embodiment, the registration request 301 is a RAU request which comprises an IMSI, an eDRX cycle (e.g., a requested or desired eDRX cycle), and an estimated coverage class of the wireless device 204.sub.3 (see technical feature 7). If desired, the RAN node 202.sub.2 at step 504 (which may occur before step 502) can transmit system information 303 to the CN node 207, where the system information 303 indicates for each of one or more cells 321.sub.1, 321.sub.2 . . . 321.sub.n managed by the RAN node 202.sub.2 the following: (1) whether an eDRX cycle is supported; and (2) a maximum eDRX cycle length supported within a set of eDRX cycle lengths (see technical feature 6) (see FIG. 3's step 302 for discussion on how the CN node 207 can use the RAU request 301 and the system information 303 (if any) to register the wireless device 204.sub.3). In one embodiment, each of the one or more managed cells 321.sub.1, 321.sub.2 . . . 321.sub.n can support a set of eDRX cycle lengths and each member of the set of eDRX cycle lengths occurs an integral number of times within a TDMA FN space (technical feature 5 and TABLE 1). In addition, each of the one or more managed cells 321.sub.1, 321.sub.2 . . . 321.sub.n can be synchronized from the TDMA FN perspective to be aligned at about a 5 or 10 milliseconds level (technical feature 2).

    [0117] At step 506 (which may occur before step 502), the RAN node 202.sub.2 can transmit TDMA FN information 307 to the CN node 207. The TDMA FN information 307 indicates ongoing TDMA frame transmissions within an overall TDMA FN space for the one or more managed cells 321.sub.1, 321.sub.2 . . . 321.sub.n (technical feature 3) (see FIG. 3's step 308 for discussion on how the CN node 207 can use the TDMA FN information 307 (if transmitted) to calculate the next occurrence of the nominal paging group for the wireless device 204.sub.3).

    [0118] At step 508, the RAN node 202.sub.2 receives a page request 309 associated with the wireless device 204.sub.3 from the CN node 207. The page request 309 is received before, for example at a predetermined or determinable time (e.g., 5 seconds) before, the next occurrence of the nominal paging group for the wireless device 204.sub.3.

    [0119] At step 510, the RAN node 202.sub.2 calculates the next occurrence of the nominal paging group for the wireless device 204.sub.3 using information within the page request 309. In one example, the page request 309 comprises an indication of an eDRX cycle (e.g., a requested or desired eDRX cycle), the IMSI and an estimated coverage class of the wireless device 204.sub.3 (technical feature 8). If desired, the page request 309 can also comprise a value of a running counter that is maintained and incremented by the CN node 207 each time a page response (associated with a corresponding page request for a specific IP packet) is not received from the wireless device 204.sub.3 and is reset each time a page response (associated with a corresponding page request) is received from the wireless device 204.sub.3 (technical feature 10). For example, the RAN node 202.sub.2 can use the IMSI, the eDRX cycle, and the estimated coverage class of the wireless device 204.sub.3 to calculate the next occurrence of the nominal paging group for the wireless device 204.sub.3 as follows: [0120] The nominal paging group of the wireless device 204.sub.3 occurs once every eDRX cycle. [0121] Assuming the wireless device 204.sub.3 is using coverage class 1 on the downlink then its nominal paging group occurs if the PCH block number=NOMINAL PAGING_GROUP (0 . . . N1)=mod (IMSI, N). [0122] N=number of paging groups on one CCCH within a given eDRX cycle=(number of paging blocks per 51-multiframe of the CCCH)*(Number of 51-MF per negotiated eDRX Cycle=EXTENDED_DRX_MFRMS). [0123] The specific set of PCH blocks comprising the nominal paging group is determined by the actual downlink coverage class of the device 204.sub.3 but will always include the PCH block identified using coverage class 1. [0124] The RAN node 202.sub.2 inherently has knowledge of the TDMA FN information associated with the one or more cells 321.sub.1, 321.sub.2 . . . 321.sub.n that it manages which it uses to determine when the next instance of the nominal paging group will occur in the time domain for the target wireless device 204.sub.3.

    [0125] At step 512, the RAN node 202.sub.2 transmits a second page request 313 to the wireless device 204.sub.3 at the next occurrence of the nominal paging group for the wireless device 204.sub.3. The first page request 309 and the second page request 311 are two different messages where the first page request 309 that is received by the RAN node 202.sub.2 from the CN node 207 triggers the RAN node 202.sub.2 to send a radio interface version of the page request 309 which is also called a page request but this radio interface version page request 313 can include paging information for multiple wireless devices 204.sub.2 etc. . . .

    [0126] At step 514, the RAN node 202.sub.2 receives a first page response 315 from the wireless device 204.sub.3. At step 516, the RAN node 202.sub.2 transmits a second page response 311 to the CN node 207. The page response 315 that is transmitted from the wireless device 204.sub.3 to the RAN node 202.sub.2 logically triggers the RAN node 202.sub.2 to send the page response 311 to the CN node 207. These two page responses 311 and 315 could be the same message (e.g., a short Logical Link Control (LLC) PDU) for GERAN or they could be two different messages for other radio access technologies.

    [0127] At step 518, the RAN node 202.sub.2 receives an IP packet 305 destined for the wireless device 204.sub.3 from the CN node 207. At step 520, the RAN node 202.sub.2 transmits the IP packet 305 to the wireless device 204.sub.3. The other RAN nodes 202.sub.1 (for example) can also be configured in a similar manner to perform method 500. An advantage of the RAN node 202.sub.2 implementing the method 500 is that it allows the RAN node 202.sub.2 to precisely determine the set of PCH blocks comprising the next instance of the nominal paging group (i.e., the next instance of the reachability of the wireless device 204.sub.3) to use for transmitting the second page request 313 to the wireless device 204.sub.3 over the radio interface, thereby allowing the wireless device 204.sub.3 to be reachable using a minimum amount of power. In contrast, without the ability to precisely determine the next instance of device reachability the RAN node 202.sub.2 will have to use other paging solutions, none of which will be as power efficient (from a wireless device perspective) as method 500 since all other solutions will necessarily require the wireless device to read more than one instance of its nominal paging group per eDRX cycle to support reachability.

    [0128] Referring to FIG. 6, there is a block diagram illustrating structures of an exemplary RAN node 202.sub.2 (for example) configured in accordance with an embodiment of the present disclosure. In one embodiment, the RAN node 202.sub.2 may comprise a first transmit module 602, a second transmit module 604, a third transmit module 606, a first receive module 608, a calculate module 610, a fourth transmit module 612, a second receive module 614, a fifth transmit module 616, a third receive module 618, and a sixth transmit module 620. The first transmit module 602 is configured to transmit a registration request 301 associated with the wireless device 204.sub.3 (for example) to the CN node 207. In one embodiment, the registration request 301 is a RAU request which comprises an IMSI, an eDRX cycle (e.g., a requested or desired eDRX cycle), and an estimated coverage class of the wireless device 204.sub.3 (see technical feature 7). If desired, the second transmit module 604 can be configured to transmit system information 303 (which may occur before transmission of registration request 301) to the CN node 207. The system information 303 indicates for each of one or more cells 321.sub.1, 321.sub.2 . . . 321.sub.n managed by the RAN node 202.sub.2 the following: (1) whether an eDRX cycle is supported; and (2) a maximum eDRX cycle length supported within of a set of eDRX cycle lengths (see technical feature 6) (see FIG. 3's step 302 for discussion on how the CN node 207 can use the RAU request 301 and the system information 303 (if any) to register the wireless device 204.sub.3). In one embodiment, each of the one or more managed cells 321.sub.1, 321.sub.2 . . . 321.sub.n can support a set of eDRX cycle lengths and each member of the set of eDRX cycle lengths occurs an integral number of times within a TDMA FN space (technical feature 5). In addition, each of the one or more managed cells 321.sub.1, 321.sub.2 . . . 321.sub.n can be synchronized from the TDMA FN perspective to be aligned at about a 5 or 10 milliseconds level (technical feature 2).

    [0129] The third transmit module 606 is configured to transmit TDMA FN information 307 to the CN node 207 (note: the third transmit module 606 may transmit the TDMA FN information 307 before the first transmit module 602 transmits the registration request 301). The TDMA FN information 307 indicates ongoing TDMA frame transmissions within an overall TDMA FN space for the one or more managed cells 321.sub.1, 321.sub.2 . . . 321.sub.n (technical feature 3) (see FIG. 3's step 308 for discussion on how the CN node 207 can use the TDMA FN information 307 (if transmitted) to calculate the next occurrence of the nominal paging group for the wireless device 204.sub.3).

    [0130] The first receive module 608 is configured to receive a page request 309 associated with the wireless device 204.sub.3 from the CN node 207. The page request 309 is received before, for example at a predetermined or determinable time (e.g., 5 seconds) before, the next occurrence of the nominal paging group for the wireless device 204.sub.3.

    [0131] The calculate module 610 is configured to calculate the next occurrence of the nominal paging group for the wireless device 204.sub.3 using information within the page request 309. In one example, the page request 309 comprises an indication of the IMSI, an eDRX cycle (e.g., a requested or desired eDRX cycle), the IMSI, and an estimated coverage class of the wireless device 204.sub.3 (technical feature 8). If desired, the page request 309 can also comprise a value of a running counter that is maintained and incremented by the CN node 207 each time a page response (associated with a corresponding page request for a specific IP packet) is not received from the wireless device 204.sub.3 and is reset each time a page response (associated with a corresponding page request) is received from the wireless device 204.sub.3 (technical feature 10). For example, the RAN node 202.sub.2 can use the IMSI, the eDRX cycle, the estimated coverage class of the wireless device 204.sub.3 to calculate the next occurrence of the nominal paging group for the wireless device 204.sub.3 as follows: [0132] The nominal paging group of the wireless device 204.sub.3 occurs once every eDRX cycle. [0133] Assuming the wireless device 204.sub.3 is using coverage class 1 on the downlink then its nominal paging group occurs if the PCH block number=NOMINAL PAGING_GROUP (0 . . . N1)=mod (IMSI, N). [0134] N=number of paging groups on one CCCH within a given eDRX cycle=(number of paging blocks per 51-multiframe of the CCCH)*(Number of 51-MF per negotiated eDRX Cycle=EXTENDED_DRX_MFRMS). [0135] The specific set of PCH blocks comprising the nominal paging group is determined by the actual downlink coverage class of the device 204.sub.3 but will always include the PCH block identified using coverage class 1. [0136] The RAN node 202.sub.2 inherently has knowledge of the TDMA FN information associated with the one or more cells 321.sub.1, 321.sub.2 . . . 321.sub.n that it manages which it uses to determine when the next instance of the nominal paging group will occur in the time domain for the target wireless device 204.sub.3.

    [0137] The fourth transmit module 612 is configured to transmit a second page request 313 to the wireless device 204.sub.3 at the calculated next occurrence of the nominal paging group for the wireless device 204.sub.3. The first page request 309 and the second page request 311 are two different messages where the first page request 309 that is received by the RAN node 202.sub.2 from the CN node 207 triggers the RAN node 202.sub.2 to send a radio interface version of the page request 309 which is also called a page request but this radio interface version page request 313 can include paging information for multiple wireless devices 204.sub.2 etc. . . .

    [0138] The second receive module 614 is configured to receive a first page response 315 from the wireless device 204.sub.3. The fifth transmit module 616 is configured to transmit a second page response 311 to the CN node 207. The page response 315 that is transmitted from the wireless device 204.sub.3 to the RAN node 202.sub.2 logically triggers the RAN node 202.sub.2 to send the page response 311 to the CN node 207. These two page responses 311 and 315 could be the same message (e.g., a short LLC PDU) for GERAN or they could be two different messages for other radio access technologies.

    [0139] The third receive module 618 is configured to receive an IP packet 305 destined for the wireless device 204.sub.3 from the CN node 207. The sixth transmit module 620 is configured to transmit the IP packet 305 to the wireless device 204.sub.3. The other RAN nodes 202.sub.1 (for example) can also be configured in a similar manner. An advantage of the RAN node 202.sub.2 being configured in this manner is that it allows the RAN node 202.sub.2 to precisely determine the set of PCH blocks comprising the next instance of the nominal paging group (i.e., the next instance of the reachability of the wireless device 204.sub.3) to use for transmitting the second page request 313 to the wireless device 204.sub.3 over the radio interface, thereby allowing the wireless device 204.sub.3 to be reachable using a minimum amount of power. In contrast, without the ability to precisely determine the next instance of device reachability the RAN node 202.sub.2 will have to use other paging solutions, none of which will be as power efficient (from a wireless device perspective) as method 500 since all other solutions will necessarily require the wireless device to read more than one instance of its nominal paging group per eDRX cycle to support reachability.

    [0140] As those skilled in the art will appreciate, the above-described modules 602, 604, 606, 608, 610, 612, 614, 616, 618, and 620 of the RAN node 202.sub.2 (e.g., BSS 202.sub.2) may be implemented separately as suitable dedicated circuits. Further, the modules 602, 604, 606, 608, 610, 612, 614, 616, 618, and 620 can also be implemented using any number of dedicated circuits through functional combination or separation. In some embodiments, the modules 602, 604, 606, 608, 610, 612, 614, 616, 618, and 620 may be even combined in a single application specific integrated circuit (ASIC). As an alternative software-based implementation, the RAN node 202.sub.2 (e.g., BSS 202.sub.2) may comprise a memory 234.sub.2, a processor 232.sub.2 (including but not limited to a microprocessor, a microcontroller or a Digital Signal Processor (DSP), etc.) and a transceiver 222.sub.2. The memory 234.sub.2 stores machine-readable program code executable by the processor 232.sub.2 to cause the RAN node 202.sub.2 (e.g., BSS 202.sub.2) to perform the steps of the above-described method 500.

    [0141] Those skilled in the art will appreciate that the use of the term exemplary is used herein to mean illustrative, or serving as an example, and is not intended to imply that a particular embodiment is preferred over another or that a particular feature is essential. Likewise, the terms first and second, and similar terms, are used simply to distinguish one particular instance of an item or feature from another, and do not indicate a particular order or arrangement, unless the context clearly indicates otherwise. Further, the term step, as used herein, is meant to be synonymous with operation or action. Any description herein of a sequence of steps does not imply that these operations must be carried out in a particular order, or even that these operations are carried out in any order at all, unless the context or the details of the described operation clearly indicates otherwise.

    [0142] Of course, the present disclosure may be carried out in other specific ways than those herein set forth without departing from the scope and essential characteristics of the invention. One or more of the specific processes discussed above may be carried out in a cellular phone or other communications transceiver comprising one or more appropriately configured processing circuits, which may in some embodiments be embodied in one or more application-specific integrated circuits (ASICs). In some embodiments, these processing circuits may comprise one or more microprocessors, microcontrollers, and/or digital signal processors programmed with appropriate software and/or firmware to carry out one or more of the operations described above, or variants thereof. In some embodiments, these processing circuits may comprise customized hardware to carry out one or more of the functions described above. The present embodiments are, therefore, to be considered in all respects as illustrative and not restrictive.

    [0143] Although multiple embodiments of the present disclosure have been illustrated in the accompanying Drawings and described in the foregoing Detailed Description, it should be understood that the invention is not limited to the disclosed embodiments, but instead is also capable of numerous rearrangements, modifications and substitutions without departing from the present disclosure that as has been set forth and defined within the following claims.