Re: Enhance Fast Dormancy feature detailed document
3.1 Smart Phone Solution
3.1.1 WRFD-020500 Enhanced Fast Dormancy
Availability
This feature is available from RAN12.0.
Summary
This feature is concerned with the impact of Fast Dormancy to the RNC. To reduce the
signaling processing cost in the Fast Dormancy procedure, when receiving SCRI (signaling
connection release indication) message from UE or UE inactivity timer expires, RNC can
transfer UE state to CELL_FACH or through Cell_FACH to CELL/URA_PCH instead of
IDLE mode which is in legacy Fast Dormancy processing.
Benefits
This feature can reduce the signal processing cost of RNC in a network comprised of
intelligent UEs with FAST DORMANCY capable, thus avoid overflow of signaling
processing unit in RNC caused by Fast Dormancy.
Description
Some intelligent UEs support Fast dormancy function. To save the power, when there is no PS
data transfer, UE can send a SCRI message to require RNC release the RRC connection and
then periodically send heartbeat message to the core network, without implementation of this
feature, RNC will release the RRC connection, then each of the following heartbeat messages
will cause RRC connection setup, authentication, encryption and RAB setup procedures.
Comparing to normal PS call procedure, this Fast dormancy mechanism will greatly increase
the signaling processing cost of RNC and may cause overflow of signaling processing unit in
RNC.
With this feature, when receiving SCRI from UE or UE inactivity timer expires, RNC will
decided to transfer the state of the UE to CELL_FACH or through Cell_FACH to
CELL/URA_PCH instead of IDLE mode. When UE periodically sends heartbeat message,
RNC will reconfigure UE to CELL_FACH or CELL_DCH. The signaling procedure between
UE and RNC will be limited to only a few message exchanges because the RRC connection
RAN12.0 Optional Feature Description
Issue 1.5 (2010-06-10) Commercial in Confidence Page 199 of 391
keep existing, at least 40% signaling exchange can be reduced and RNC CPU resources can
be saved significantly while UE battery consumption is saved as much as that in IDLE mode.
When receiving SCRI message, if one of the following condition is met, RNC will look the
UE as FAST DORMANCY capable, initial this feature and transfer UE to CELL_FACH or
through Cell_FACH to CELL/URA_PCH state:
IMEI of the UE belongs to the range of IMEIs defined by operator configuration
RNC can get the IMEI of the UE by sending a “IDENTITY REQUEST” to UE and get UE
response;
Because the producer and model information are included in IMEI, operator can configure the
range of IMEIs with FAST DORMANCY function.
The cause value in SCRI message is "UE Requested PS Data session end."
When UE inactivity timer expires, if IMEI of the UE belongs to the range of IMEIs defined
by operator configuration, the UE will be transferred to CELL_FACH or through Cell_FACH
to CELL/URA_PCH state instead of IDLE state.
Pls be aware that when SCRI without cause value was sent and smart phone will be
transferred to CELL_FACH or through Cell_FACH to CELL/URA_PCH state which might
have the risk of incompatibility. In this case, we strongly suggest providing the feature
together with Huawei professional services.
Enhancement3.1 Smart Phone Solution
3.1.1 WRFD-020500 Enhanced Fast Dormancy
Availability
This feature is available from RAN12.0.
Summary
This feature is concerned with the impact of Fast Dormancy to the RNC. To reduce the
signaling processing cost in the Fast Dormancy procedure, when receiving SCRI (signaling
connection release indication) message from UE or UE inactivity timer expires, RNC can
transfer UE state to CELL_FACH or through Cell_FACH to CELL/URA_PCH instead of
IDLE mode which is in legacy Fast Dormancy processing.
Benefits
This feature can reduce the signal processing cost of RNC in a network comprised of
intelligent UEs with FAST DORMANCY capable, thus avoid overflow of signaling
processing unit in RNC caused by Fast Dormancy.
Description
Some intelligent UEs support Fast dormancy function. To save the power, when there is no PS
data transfer, UE can send a SCRI message to require RNC release the RRC connection and
then periodically send heartbeat message to the core network, without implementation of this
feature, RNC will release the RRC connection, then each of the following heartbeat messages
will cause RRC connection setup, authentication, encryption and RAB setup procedures.
Comparing to normal PS call procedure, this Fast dormancy mechanism will greatly increase
the signaling processing cost of RNC and may cause overflow of signaling processing unit in
RNC.
With this feature, when receiving SCRI from UE or UE inactivity timer expires, RNC will
decided to transfer the state of the UE to CELL_FACH or through Cell_FACH to
CELL/URA_PCH instead of IDLE mode. When UE periodically sends heartbeat message,
RNC will reconfigure UE to CELL_FACH or CELL_DCH. The signaling procedure between
UE and RNC will be limited to only a few message exchanges because the RRC connection
RAN12.0 Optional Feature Description
Issue 1.5 (2010-06-10) Commercial in Confidence Page 199 of 391
keep existing, at least 40% signaling exchange can be reduced and RNC CPU resources can
be saved significantly while UE battery consumption is saved as much as that in IDLE mode.
When receiving SCRI message, if one of the following condition is met, RNC will look the
UE as FAST DORMANCY capable, initial this feature and transfer UE to CELL_FACH or
through Cell_FACH to CELL/URA_PCH state:
IMEI of the UE belongs to the range of IMEIs defined by operator configuration
RNC can get the IMEI of the UE by sending a “IDENTITY REQUEST” to UE and get UE
response;
Because the producer and model information are included in IMEI, operator can configure the
range of IMEIs with FAST DORMANCY function.
The cause value in SCRI message is "UE Requested PS Data session end."
When UE inactivity timer expires, if IMEI of the UE belongs to the range of IMEIs defined
by operator configuration, the UE will be transferred to CELL_FACH or through Cell_FACH
to CELL/URA_PCH state instead of IDLE state.
Pls be aware that when SCRI without cause value was sent and smart phone will be
transferred to CELL_FACH or through Cell_FACH to CELL/URA_PCH state which might
have the risk of incompatibility. In this case, we strongly suggest providing the feature
together with Huawei professional services.
Enhancement
Bookmarks