Professional Documents
Culture Documents
Dokumen - Tips - Connection Management Feature Parameter Descriptioneran2001 PDF
Dokumen - Tips - Connection Management Feature Parameter Descriptioneran2001 PDF
Dokumen - Tips - Connection Management Feature Parameter Descriptioneran2001 PDF
Connection Management
Feature Parameter Description
Issue 01
Date 2010-07-30
and other Huawei trademarks are the property of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Contents
1 Introduction.................................................................................................................................1-1
1.1 Scope.............................................................................................................................................................1-1
1.2 Intended Audience.........................................................................................................................................1-1
1.3 Change History..............................................................................................................................................1-1
3 Related Concepts........................................................................................................................3-7
3.1 Tracking Area ................................................................................................................................................3-7
3.2 Access Stratum States....................................................................................................................................3-7
3.3 Non-Access Stratum States ...........................................................................................................................3-8
3.4 Call Types in the NAS...................................................................................................................................3-8
4 Random Access.........................................................................................................................4-10
4.1 Random Access Preambles..........................................................................................................................4-11
4.1.1 Overview............................................................................................................................................4-11
4.1.2 Preamble Sequence Generation and Classification ............................................................................4-11
4.2 Random Access Procedure ..........................................................................................................................4-12
4.2.1 Contention-Based RA Procedure .......................................................................................................4-13
4.2.2 Non-Contention-Based RA Procedure ...............................................................................................4-15
4.3 RA Backoff Control ....................................................................................................................................4-15
6 RB Management .......................................................................................................................6-24
6.1 SRB2 Establishment and Modification .......................................................................................................6-24
6.2 DRB Establishment and Modification ........................................................................................................6-25
6.3 DRB Release ...............................................................................................................................................6-26
7 Engineering Guidelines..........................................................................................................7-28
7.1 T302 ............................................................................................................................................................7-28
7.2 RA Configurations ......................................................................................................................................7-28
8 Parameters ...................................................................................................................................8-1
9 Counters .......................................................................................................................................9-1
10 Glossary ...................................................................................................................................10-2
10.1 Terms.........................................................................................................................................................10-2
10.2 Acronyms and Abbreviations ....................................................................................................................10-2
11 Reference Documents............................................................................................................11-4
1 Introduction
1.1 Scope
This document describes the management of the connections between the User Equipment
(UE), E-UTRAN NodeB (eNodeB), and Mobility Management Entity (MME). Connection
management is a series of processes in which dedicated connection between the UE and the
MME is established for certain UE service and the dedicated connection is released when the
service is complete.
This document also describes Random Access (RA), signaling connection management,
Radio Bearer (RB) management, and related engineering guidelines.
Document Issues
The document issue is as follows:
z 01 (2010-07-30)
z Draft (2010-05-20)
01 (2010-07-30)
Compared with draft (2010-05-20), issue 01 (2010-07-30) incorporates the changes described
in the following table.
Draft (2010-05-20)
Compared with issue 01 (2010-01-31) of eRAN1.1, draft (2010-05-20) of eRAN2.0
incorporates the changes described in the following table.
Feature change The configurable parameters related The following parameters are
to the connection management deleted:
algorithms are changed. z PreambInitRcvTargetPwr
z PwrRampingStep
The following parameter is
added:
z CellRadius
z PreambleFmt
z T302
z UeInactiveTimer
Editorial change None. None.
Connection management in the LTE system involves management of the connections between
the UE, eNodeB, and MME. The connection management is performed in both control plane
and user plane.
Figure 2-1 shows the functions involved in connection management. RA is triggered by a UE
when the UE needs to communicate with the network for purposes such as service request,
location update, and paging. After the RA procedure is complete, the connection between the
UE and the MME in the control plane is started. Connection in the control plane consists of
Radio Resource Control (RRC) signaling connection and dedicated S1 connection. RRC
signaling connection refers to signaling connection between the UE and the eNodeB on the
Uu interface, and dedicated S1 connection refers to the signaling connection between the
eNodeB and the MME. After the connection in the control plane is complete, the MME
causes the eNodeB to establish E-UTRAN Radio Access Bearer (E-RAB) in the case of
service request. Through RB management, the eNodeB establishes, modifies, and releases the
E-RAB.
NOTE
The security mode command procedure is not described in this document. For details about the related
information, see the Security Feature Parameter Description.
2.2 UE Connection
UE connection consists of signaling connection in the control plane and RB management.
Signaling connection in this document refers to the signaling connection before security
establishment. The connection involves RRC signaling connection and signaling connection
on the S1 interface. RRC connection establishment is Signaling Radio Bearer-1 (SRB1)
establishment. Signaling connection on the S1 interface is dedicated S1 connection.
RB management in this document refers to the E-RAB establishment procedure after security
establishment. The procedure involves Signaling Radio Bearer-2 (SRB2) establishment and
Data Radio Bearer (DRB) establishment.
In the LTE system, the services between a UE and a Packet Data Network (PDN)-Gateway
(GW) with the same QoS class are referred to as an Evolved Packet System (EPS) bearer. In
the EPS bearer, the section between the UE and the eNodeB is RB, and the section between
the eNodeB and the Serving Gateway (S-GW) is S1 bearer, as shown in Figure 2-2. RB and
S1 bearer are collectively referred to as E-RAB.
RB is classified into Signaling Radio Bearer (SRB) and DRB according to different bearing
contents.
A SRB bears signaling, which is in the control plane. According to different signaling, three
different SRBs can be defined as follows:
z Signaling Radio Bearer-0 (SRB0): bearing the RRC signaling prior to RRC connection
establishment. The SRB0 is transmitted over the Common Control Channel (CCCH)
through the Transparent Mode (TM) in the Radio Link Control (RLC) layer.
z SRB1: bearing the NAS signaling prior to SRB2 establishment and RRC signaling,
which may contain Non-Access Stratum (NAS) signaling messages. The SRB1 is
transmitted over the Dedicated Control Channel (DCCH) through the Acknowledged
Mode (AM) in the RLC layer.
z SRB2: bearing NAS signaling. The SRB2 is transmitted over the DCCH through the AM
in the RLC layer. The priority of the SRB2 is lower than that of the SRB1, and the SRB2
can be established only after the security is activated.
A DRB bears data in the user plane. A maximum of eight DRBs can be established between
the UE and the eNodeB according to different QoS classes.
Signaling connection release is triggered by the MME. The connection of the E-RAB bearing
services is released first, and then the dedicated S1 connection is released. The MME may
also release dedicated S1 connection to release all the S1 resources.
2.2.2 RB Management
RB management consists of the management of the SRB2 and DRB after security is
established, which involves the establishment and modification of the DRB and SRB2 and
also release of the DRB. The SRB2 cannot be released through RB management. Instead, the
SRB2 is released with the SRB1 during signaling connection release.
3 Related Concepts
Table 3-1 Relation between the cause for RRC connection establishment and call type
NAS Procedure Cause for RRC Connection Call Type
Establishment
After the request for the RRC connection establishment, the cause of which is not MO-data or
MO-signaling, is rejected, the UE must wait for some time before sending the request for the
RRC connection establishment again. The waiting time can be set through the T302 timer.
When the UE receives a rejection message for the RRC connection establishment request, the
timer starts. When the UE enters the RRC_CONNECTED mode or cell reselection is
performed, the timer stops.
4 Random Access
available for the preambles. The Physical Random Access Channel (PRACH) bears the
RACH. The PRACH has fixed time and frequency resources, which can be obtained from the
common channel configuration parameters in the System Information Block-2 (SIB2).
This chapter describes the basic features LBFD-002010 Random Access Procedure and
TDLBFD-002010 Random Access Procedure.
By reading prach-ConfigurationIndex in the SIB2, the UE knows the occurrence time of the
PRACH in each radio frame. The value of prach-ConfigurationIndex ranges from 0 to 63, and
each value contains cell bandwidth, percentage of the occupied uplink resources, number of
access times in a second, average access delay, and radio frame and subframe numbers in the
PRACH. prach-ConfigurationIndex indicates different contents for the FDD mode and TDD
mode. For details, see reference document [3]. The eNodeB automatically changes the value
of prach-ConfigurationIndex according to the load on the PRACH. This prevents UE
preamble conflicts caused by overload on the PRACH.
from 0 to 837. The number of digits for cyclic shifts is determined by the eNodeB according
to the cell type and cell radius. The logical index of the ZC sequence is cyclic. That is, the
logical index 0 is consecutive to 837. Each cell can be configured with 64 preamble sequences.
If 64 preambles cannot be generated from a single ZC sequence, additional preamble
sequences are obtained from the ZC sequences with the consecutive logical indexes until all
the 64 sequences are found. For details about the preamble sequences generated from cyclic
shifts of the ZC sequence, see reference document [3]. The logical index of the ZC sequence
and configured cyclic shift value are transmitted in the PRACH configurations in the SIB2.
Based on the contention-based RA and non-contention-based RA, a UE uses the random
preamble sequence or dedicated preamble sequence that is allocated by the eNodeB.
Therefore, the 64 preamble sequences are divided into: random preamble sequence group and
dedicated preamble sequence group. To reduce UE preamble conflicts, the random preamble
sequence groups are divided into preamble sequence group A and preamble sequence group
B.
The following counters are periodically collected for the dedicated preamble sequence:
z Maximum number of dedicated preamble sequences that are allocated to the UE in the
period
z Number of preamble sequences in the current dedicated preamble sequence group
Based on the counters, the eNodeB modifies the classification of the dedicated preamble
sequence group and random preamble sequence group. In addition, random preamble
sequences are evenly divided into group A and group B.
When the SI modification period arrives, the RACH-related parameters are updated in the
broadcast SI messages if the number of preamble sequences changes. The RACH-related
parameters consist of the number of random preamble sequences and proportion of random
preamble sequence group A.
Figure 4-1 shows the contention-based RA procedure. The procedure is divided into four steps:
UE transmitting an RA preamble, eNodeB transmitting an RA response, UE transmitting
uplink scheduled data, and eNodeB transmitting a contention resolution.
UE Transmitting an RA Preamble
The UE transmits an RA preamble over the PRACH. For details about the calculation of the
transmit power of a preamble PPRACH, see the Power Control Feature Parameter Description.
On the following PRACH that is allocated, the UE transmits a preamble with the transmit
power of PPRACH. The preamble usually carries information of six bits, in which five bits
indicate the Random Access Radio Network Temporary Identifier (RA-RNTI), and one bit
indicates the size of the uplink transport block msg3 in the scheduled data transmission.
Timing Alignment Information, Initial UL Grant, and Temporary C-RNTI. A message on the
DL-SCH can carry multiple RA responses to be transmitted to multiple UEs.
Once the preamble is transmitted, the UE monitors the Physical Dedicated Control Channel
(PDCCH) in the Transmission Time Interval (TTI) until it obtains the required RA response.
z If the received RA-Preamble Identifier is consistent with the identifier that the UE
previously sent, the UE infers that the response is successful. Then, the UE transmits
uplink scheduled data.
z If the UE does not receive a response within the TTI, or if all received RA responses
contain RA preamble identifiers that do not match the transmitted RA preamble, the UE
infers that the response reception fails. Then, the UE performs RA again if the number of
RA attempts is smaller than the maximum number of attempts. If the number of RA
attempts is not smaller, the RA procedure fails.
z In non-contention-based RA
The eNodeB records the current RACH overload counter. The initial backoff value is 0. When
the RACH is overloaded, the backoff value is increased by 1. The action continues if the
RACH is still overloaded. If the backoff value is equal to the maximum value and the RACH
is still overloaded, the PRACH configuration needs to be modified. That is, the number of
PRACHs is increased, and the backoff value is set to 0. When the RACH is underloaded, the
backoff value is decreased by 1. The action continues if the RACH is still underloaded. If the
backoff value is equal to the minimum value and the RACH is still underloaded, the PRACH
configuration needs to be modified. That is, the number of PRACHs is decreased, and the
backoff value is set to 0. If the RACH is neither overloaded nor underloaded, the backoff
value remains unchanged.
This chapter describes the basic features LBFD-002007 RRC Connection Management and
TDLBFD-002007 RRC Connection Management.
the RRC connection establishment, the UE can be configured to perform measurements. The
UE can perform handover only when the security mode is started.
Figure 5-2 shows the RRC connection establishment procedure.
2. The MME parses the NAS message contained in the Initial UE Message before obtaining
the cause for the connection establishment. Then, the MME handles the UE service
request based on the cause and allocates a dedicated S1APID to the UE.
3. The MME sends the eNodeB the Initial Context Setup Request message, which may
contain the common UE context and EPS bearer context.
4. After receiving the Initial Context Setup Request message, the eNodeB starts the UE
context establishment. At the same time, the eNodeB generates security keys for service
bearer and signaling based on the received security parameters.
NOTE
By comparing the eNodeB-supported algorithms with the UE-supported algorithms, the eNodeB selects
a security algorithm supported by both the eNodeB and the UE and then sends the algorithm to the UE
through the Security Mode Command message. This document does not describe the security procedure.
For details, see the Security Feature Parameter Description.
5. The eNodeB performs service admission decision and resource allocation.
6. The eNodeB instructs the UE to start integrity protection and encryption when sending
the UE the security keys through the Security Mode Command message. At the moment,
downlink encryption is started.
7. The eNodeB sends the UE the RRC Connection Reconfiguration message on which
encryption and integrity protection is performed. This is used for the establishment of the
SRB2 and DRB.
8. After receiving the Security Mode Command message from the eNodeB, the UE selects
an encryption algorithm provided by the eNodeB. After the security keys that are used
by both the service bearer and the signaling are successfully generated, the UE transmits
the Security Mode Complete message, which is not encrypted. After the eNodeB
receives the Security Mode Complete message, uplink encryption is started.
9. The UE establishes corresponding resources according to the RRC Connection
Reconfiguration message. After the resources are successfully established, the UE
responds to the eNodeB with an RRC Connection Reconfiguration Complete message.
10. The eNodeB sends the MME the feedback through the Initial Context Setup Response
message, which indicates that the bearer is successfully established.
The E-UTRAN integrates the security procedure and initial bearer establishment procedure,
which indicating that the security parameter and bearer establishment parameter are
transmitted together. The security procedure must be started by the eNodeB first. The service
bearer establishment procedure, however, can be started later before the security procedure is
complete. That is, the RRC Connection Reconfiguration message in 7 can be sent before the
UE responds with a Security Mode Complete message. Thus, the delay from the initial UE
access to the bearer establishment is significantly reduced.
3. Over the CCCH, the eNodeB sends the UE the RRC Connection Reestablishment
message, which contains the information of the allocated resources. After receiving the
RRC Connection Reestablishment message, the UE reconfigures radio resources
according to the instructions in the message and then starts encryption and integrity
protection.
4. The UE sends the eNodeB the RRC Connection Reestablishment Complete message.
2. The eNodeB releases transmission resources and triggers the release of the RRC
connection over the Uu interface.
3. The eNodeB sends the UE an RRC Connection Release message to release the resources
over the Uu interface. In this case, the eNodeB does not need to wait for the response
from the UE.
4. The eNodeB releases the radio resources in the system.
5. The eNodeB sends the MME the UE Context Release Complete message, indicating that
the resource release is complete.
6. After sending the UE Context Release Complete message, the eNodeB releases the
corresponding UE context. Thus, the UE is changed from RRC_CONNECTED mode to
RRC_IDLE mode.
To release all the S1 resources including the service bearer resources, the MME can release
the dedicated S1 connection.
The eNodeB monitors the UE for data transmission or reception when the timer set through
the UeInactiveTimer parameter does not expire. When the timer expires, the eNodeB sends
the MME the signaling link release request if the UE fails to receive or send data.
When the MME initiates load rebalancing, the relative capacity of the MME should be
reconfigured, and the result must be sent to the eNodeB. In this case, the eNodeB does not
select the MME for the RRC connection establishment. If the RRC connection is released due
to load rebalancing, the eNodeB redirects the UE to another cell in the LTE system or a cell in
another Radio Access Technology (RAT) system.
6 RB Management
RB management refers to the management of the SRB2 and DRB after the encryption and
integrity protection is complete. RB management involves the establishment and modification
of the SRB2 and DRB and also release of the DRB. The SRB2 is released with the SRB1
during signaling link release. For details about the signaling link release, see section 5.4
"Signaling Link Release".
In RB management, the interaction between the UE and the eNodeB is based on the RRC
reconfiguration procedure. Therefore, RB management does not require dedicated signaling.
RRC reconfiguration is used in scenarios such as establishment, modification, and release of
RBs and configuration and modification of handover measurement information. Different
Information Elements (IEs) are used to distinguish RRC reconfiguration messages in different
scenarios.
This chapter describes the basic features LBFD-002008 Radio Bearer Management and
TDLBFD-002008 Radio Bearer Management.
The DRB modification is triggered by the MME through the E-RAB Modify Request
message. Figure 6-3 shows the DRB modification procedure. According to the instructions in
the RRC Connection Reconfiguration message, the UE reconfigures the corresponding PDCP
entity, corresponding RLC entity, and DCCH.
7 Engineering Guidelines
7.1 T302
The T302 timer indicates the waiting time for resending the RRC connection establishment
request after the RRC connection establishment request initiated by the UE is rejected. The
cause of the RRC connection establishment request is neither MO-data nor MO-signaling.
The T302 can be set to a large value for a cell with heavy traffic or a small value for a cell
with light traffic.
If the T302 is set to a large value, the UE does not access the cell in a long period of time
after rejected, and therefore the user experience is affected. If the T302 is set to a small value,
the UE attempts to access the network repeatedly, resulting in heavy loads in the system.
7.2 RA Configurations
The RA algorithm switch consists of the preamble group adjustment switch, time resource
adjustment switch, non-contention-based RA switch for handover, non-contention-based RA
switch for synchronization, dedicated preamble multiplexing switch, and backoff control
switch. The switch is controlled by the RachAlgoSwitch parameter.
z Preamble group adjustment switch (RaGrpAdjSwitch): RaGrpAdjSwitch adaptively
adjusts the number of dedicated preamble sequences in the preamble sequence group of
the cell. If the switch is turned on, the algorithm dynamically adjusts the preamble
configurations according to the use of the preambles. If the switch is turned off, the
algorithm uses the initial configuration and does not perform dynamic adjustment. It is
recommended that the parameter is set to OFF.
z Time resource adjustment switch (RaTrAdjSwitch): RaTrAdjSwitch adaptively adjusts
the PRACH configurations based on the RA preamble sequence detection result. If the
switch is turned on, the algorithm dynamically adjusts the time resource configuration
according to the RACH load. If the switch is turned off, the algorithm uses the initial
configuration and does not perform dynamic adjustment. It is recommended that the
parameter is set to OFF.
8 Parameters
MO Parameter ID Description
CellAlgoSwit RachAlgoSwitch RaGrpAdjSwitch: Indicates the switch that is used to enable and
ch disable the group adjustment algorithm.
When this switch is set to ON, the algorithm dynamically adjusts
the preamble configuration based on the preamble usage.
When this switch is set to OFF, the algorithm uses the initial
configuration and does not perform dynamic adjustments.
RaTrAdjSwitch: Indicates the switch that is used to enable and
disable the time-domain resource adjustment algorithm.
When this switch is set to ON, the algorithm dynamically adjusts
the time-domain resource allocation based on the load on the
RACH. When this switch is set to OFF, the algorithm uses the
initial configuration and does not perform dynamic adjustments.
HoRaSwitch: Indicates the switch that is used to control the
random access mode applied during handovers.
When this switch is set to ON, the eNodeB instructs UEs to use the
non-contention-based random access mode during handovers.
When this switch is set to OFF, the eNodeB instructs UEs to use
the contention-based random access mode during handovers.
UnsyncRaSwitch: Indicates the switch that is used to control the
random access mode applied when UEs are out of synchronization
in the uplink. When this switch is set to ON, the eNodeB instructs
UEs to use the non-contention-based random access mode upon
DL data arrival in the case of out-of-synchronization.
When this switch is set to OFF, the eNodeB instructs the UE to use
the contention-based random access mode upon DL data arrival in
the case of out-of-synchronization.
MaksIdxSwitch: Indicates the switch that is used to control the
reuse of dedicated preambles between UEs.
When this switch is set to ON, the eNodeB enables reuse of
dedicated preambles between UEs based on the MaskIndex
parameter. When this switch is set to OFF, the eNodeB allocates
one dedicated preamble to only one user at a given time.
BackOffSwitch: Indicates the switch that is used to enable and
disable the backoff control algorithm. When this switch is set to
ON, the backoff control algorithm is enabled. When this switch is
set to OFF, the backoff control algorithm is disabled.
Cell RootSequenceIdx Indicates the logical root sequence index, which is used to derive
the preamble sequence. Each logical root sequence corresponds to
a physical root sequence. For the mapping between logical root
sequences and physical root sequences, see 3GPP TS 36.211.
Cell PreambleFmt Indicates the preamble format used in the cell. For details, see
3GPP TS 36.211.
Cell CellRadius Indicates the radius of the cell.
MO Parameter ID Description
RRCConnSta T302 Indicates the length of timer T302. It refers to the wait time for
teTimer retransmitting an RRCConnectionRequest message after the
previous request with a cause other than "MO-Data" and
"MO-Signalling" is rejected. This timer is started after the UE
receives the RRCConnectionReject message. This timer is stopped
when the UE enters the RRC_CONNECTED mode or performs
cell reselection.
RRCConnSta UeInactiveTimer Indicates the time threshold that specifies when an idle UE should
teTimer be disconnected from the network. The eNodeB monitors whether
UEs are receiving or sending data. When a UE has neither received
nor sent data for a duration exceeding this threshold, the eNodeB
releases the radio resources of the UE. When this parameter is set
to 0, the eNodeB does not monitor the data transmitting or
receiving state of the UE.
9 Counters
For details about the counters related to connection management, see the eNodeB
Performance Counter Reference.
10 Glossary
10.1 Terms
None.
11 Reference Documents