In this section we show the relation between RRC and GMM states.
In order to simplify this table, we only consider the handset is only using data channels, so no voice nor SMS (circuit domain) is being used.
Table 2.1. RCC - GMM relation
| RCC State | GMM State (2G/3G) | Description |
|---|---|---|
| RCC State | GMM State (2G/3G) | Description |
| Cell_DCH | READY/PMM_CONNECTED |
The handset is transmitting or receiving data information using a dedicated channel or a HSPA shared channel. |
| Cell_FACH | READY/PMM_CONNECTED |
The handset had been transmitting or receiving data some seconds ago and due to inactivity had been moved to the Cell_FACH RCC state. Also it's possible that the handset is transmitting or receiving small amount of data like pings, keep-alives, cell updates,... |
| Cell_PCH/URA_PCH | READY/PMM_CONNECTED |
The handset had been in Cell_FACH some seconds ago and due to inactivity had been moved to this less resource consume state. However, the signaling channel is available and is able to change to a data transmission state like FACH or DCH with a little amount of signaling. |
| Cell_PCH/URA_PCH | STANDBY/PMM_IDLE |
The handset is not transmitting nor receiving any amount of data and also the signaling connection is closed. However the IP address is maintained by the network and associated to this handset. This is one of the most interesting states since the PDP context is not closed, the IP address is still valid and the handset is not consuming battery, network traffic,... As soon as the handset needs to reestablish the data channel the radio state will be changed to FACH or DCH. |
| RRC_IDLE | STANDBY/PMM_IDLE |
This state is the same as the previous one since the radio state is IDLE. |
| RRC_IDLE | IDLE/PMM_DETACHED |
The handset is not transmitting nor receiving anything and also it hasn't any PDP context established, so no IP address is available for this handset. Normally this state is after 24h of inactivity in the package domain. |