Definition
Paging is the broadcasting of paging messages within the tracking area (TA) where the terminal is registered, triggered by incoming calls or downlink data arriving in the network, to notify terminals in idle mode (RRC_IDLE) to establish an RRC connection. The MME/SGSN initiates paging to eNB via the S1/S11 interface. The eNB schedules the paging message on the PDSCH using PDCCH scrambled with P-RNTI, and the terminal listens to the paging channel according to the DRX cycle. The paging strategy (paging cycle, RRC state, eDRX) directly affects terminal power consumption and call setup delay.
Paging Process
Core Network Initiation
When downlink data arrives or a call comes in, the S-GW notifies the MME, which, based on the last registered TA List of the terminal, initiates a paging request to all eNBs within that TA carrying the IMSI or S-TMSI.
Air Interface Broadcast
At the paging occasion, the eNB indicates the paging message on the PDSCH using the PDCCH scrambled with P-RNTI. The terminal listens within the Paging Frame and Paging Occasion and, if it matches its own identifier, initiates RRC connection establishment.
DRX and eDRX
The terminal periodically listens according to the DRX cycle (such as 1.28s, 2.56s) to reduce power consumption. NB-IoT and others support eDRX (such as 40.96s, 10.24s), further saving power at the cost of increased paging delay.
IoT Paging Considerations
Most IoT devices are in a called scenario (downlink commands, OTA wake-up), and the paging success rate and latency affect the service experience. Long eDRX can reduce power consumption but requires the business to tolerate the corresponding delay; the TA planning in mobility strategy affects the paging range and signaling overhead.
IoT devices of SimtoLink, when in idle mode, need to be paged to receive downlink commands or OTA wake-ups. SimtoLink combines the business latency requirements in the solution design to choose an appropriate DRX/eDRX configuration: short DRX for scenarios requiring high real-time performance; long eDRX for scenarios like meters that can tolerate minute-level delays to extend battery life. When the SimtoLink platform initiates downlink commands, it considers paging delay and configures relevant timeout and retry strategies.
The Paging Occasion Has to Fall on a Subframe Where the Device Is Awake
Paging exists because an idle device has no dedicated channel. The network can only broadcast, inside the tracking area where the device registered, that there is downlink for it. From the list left by the last location update, the core sends the paging request to the base stations in those areas. On the paging frame and paging occasion, the base station points at the paging message with a control channel scrambled by the P-RNTI. The device plugs its own identity into a formula and works out which subframes to wake on. If its wake rhythm and the network’s send rhythm do not match, the message goes out while the device is asleep. After several misses the core treats the device as unreachable.
Connected mode does not need this broadcast. The base station already has the device’s scheduling identity, and downlink can go straight onto the shared channel. So a failed platform downlink should first ask whether the device was idle or connected. Only idle mode depends on the paging cycle. A failure in connected mode belongs to scheduling and bearers. 5G inactive mode can still be paged by the radio access network. That scope is not the same as 4G, where the core broadcasts by tracking area.
Pick the Cycle from the Wake Delay the Service Can Tolerate
The DRX cycle is the interval at which an idle device listens for paging. eDRX stretches that interval to tens of seconds or more. A longer cycle means the device radio turns on less often, the battery lasts longer, and one downlink from the platform waits about that cycle plus the random-access time. If the service must unlock, park, or throw a relay within a few seconds, an eDRX counted in minutes cannot be used. A meter that can be read within a quarter of an hour is the case that can lengthen the cycle.
The network, the SIM, and the module all have to accept the same cycle. Writing eDRX only into the module, when the network has not subscribed it or has not confirmed it in the attach accept, leaves the device waking on the default short cycle. The power saving never appears. An oversized tracking-area list means one page has to hit many cells and the signaling load rises. A list that is too small makes the device update its location often. Keep both separate from handover management: handover changes the cell in connected mode, paging finds a device in idle mode. If policy locks the device in connected mode and never releases it, every paging parameter is inert, and the device uses more power.
Broadcasting the Permanent Identity Over and Over
Paging should prefer a temporary identity. Using the IMSI on every page across the whole tracking area exposes the long-term identity on the air interface and lengthens the message. Another mistake is a platform that, after a timeout, sends again at sub-second intervals. The device is still inside a long eDRX sleep. Those requests stack into repeated pages in the core. They do not wake the device, and they occupy the paging channel. Align retries to the cycle, and after the first page fails read the unreachable cause. Do not resend immediately.
Paging failure is also easy to treat as a suspended SIM. Suspension or a deleted subscription is rejected at attach. When paging fails, the device can often still send uplink on its own. Compare whether uplink reports are still arriving, the time of the last location update, and the count of pages with no response. Uplink normal and downlink all timing out points first at the cycle and the list, not at swapping the antenna. If the list includes a base station that has already gone out of service, the message is sent into an empty cell and is also counted as no response.
The paging channel itself has a capacity. When the list is large and downlink commands bunch together, broadcast messages queue inside the cell or are discarded. A device that wakes on time still does not hear its own identity. Shortening the cycle does not help, because the failure is congestion on the sending side, not the device sleeping through the occasion. Shrink the paging scope or stagger the downlink times before talking about the power-saving cycle. A temporary identity that cannot be resolved and a device that is not in the list are different causes. The first is identity assignment. The second is the last location registration.