B - 01 - TDD LTE Signaling Procedures

TDD-LTE Signaling Procedures
TDD Products Support Department

Content
 Cell Search
 Random Access
 Power-on Attach/Detach
 UE-Initiated Service Request Procedure
 Paging Procedure
 TAU Procedure
 Handover Procedure
 Dedicated Bearer Procedure
Cell Search
 Check PSCH to acquire a 5ms clock and a Check PSCH to acquire
a 5 ms clock and the
specific cell ID. specific ID of a cell in a
cell group.
 Check SSCH to acquire a radio frame
clock and a cell ID group. Check SSCH to acquire
a radio frame clock and
 Frame synchronization is achieved through a cell ID group.
the preceding two steps, and then the RS

location is acquired. Carry out channel Check downlink
reference signals to
estimate by checking the RS. acquire the BCH

antenna configuration.
 Read PBCH for acquiring other system Read BCH to acquire

information, including dl-Bandwidth in MIB other cell information
and systemFrameNumber (SFN) in MIB, to

achieve frame synchronization with a cell.
Content
 Cell Search
 Random Access
 UE Initiated Service Request Procedure
 TAU Procedure
Random Access Trigger Conditions
Scenario 1: Initial
access and shift
from RRC IDLE to
Connected
Scenario 3: Scenario 2:
Redirected to a new Reestablishment
cell after handoff upon radio link
setup failure
Random access
scenario
Scenario 4:
Downlink data Scenario 5: Uplink
arrives when uplink data arrives when
data is out-of- uplink data is out-of-
synchronization synchronization
Classification of Random Access Procedures
 Contention-based random access:

 A User Equipment (UE) chooses a random preamble from the broadcast preamble
group.
 Use Preamble Group A/B
 The contention occurs when two UEs try to use the same preamble.
The fourth step is
 Applicable to all random access scenarios.
used to resolve
 Non-contention-based random access: conflicts
 The preambles used by UEs are assigned by eNodeB.
 Random access is completed in three steps.
 Only applicable to scenarios 3 and 4.
 Non-contention-based random access: No need to

resolve conflicts
Random Access Procedure
UE eNB
 Comparison between two random
access procedures
0 RA Preamble assignment
UE eNB
Random Access Preamble 1

1 Random Access Preamble
Random Access Response 2 2 Random Access Response
3 Scheduled Transmission
Contention Resolution 4
Purpose of Random Access
 Request an initial access;
 Shift from idle to connecting state;
 Support handover between eNodeBs;
 Obtain/resume uplink synchronization;
 Request UE ID from the eNodeB;
 Send an uplink resource request to the eNodeB;
Set up a radio
Obtain/ resume
link between
uplink
the UE and the
synchronization
eNodeB
s
Preamble Format
 Random access preamble
CP Sequence
TCP TSEQ
4 is used only for frame structure type 2

TDD Random Access Configuration
 PRACH Configuration
Random Access Preamble Time-frequency Mapping
 A
Random Access Preamble Time-frequency Mapping
 The quadruple ( f , t , t , t ) specifies the time-frequency position of
RA
( 0)
RA
(1)
RA
( 2)
RA
random access resources.

 f indicates the frequency-domain index within a specified time
RA
domain.
 t  0,1,2 indicates whether random access resources are allocated in
0
RA
each radio frame, in even number of frames only or in odd number

of frames only.
 t  0,1 indicates whether to assign the random access resources in
(1)
RA
first half of the frame or the last half of the frame.

 t indicates the subframe number from which you start to allocate
2
RA
random access resources. The subframes are numbered from 0,

and indicate all uplink subframes between two consecutive UL/DL
switchover points.
0 1 2 0 1 2
D S U U U D S U U U
Downlink Special Uplink

D S U
subframe subframe subframe
PRACH Resources Frequency Domain Location
Calculation
 Leading format 0-3
 RA  f RA 
n PRB offset  6  2 , if f RA mod 2  0
RA
n PRB   
 N RB  f RA 
UL
 6  n PRB
RA
offset  6  , otherwise
  2 
 UL
N RB indicates the total number of available PRBs in the
uplink.
 RA
n
PRB indicates the first RB number allocated to the
related PRACH resources.
 RA
n That is, the parameter prach-FrequencyOffset. It
PRB offset
indicates the frequency offset of the PRACH resource,

and can be considered as the number of the first RB
used to assign PRACH resources.
PRACH Time-frequency Allocation Example
Take UL/DL configuration 1 as an example

=6
RA
n PRB offset
Classification of Preambles
 Non-dedicated random access preambles
 Group A
Preamble ID:0 to sizeOfRA-PreamblesGroupA – 1

 Group B
Preamble ID:sizeOfRA-PreamblesGroupA to
numberOfRA-Preambles – 1
 Dedicated random access preambles
 Dedicated random access preambles
 Group A/B related parameters
MSG1: Random Access Preamble (RA preamble)
 GROUP A/B selection

 The possible size of a to-be-sent Msg3 ﹥
messageSizeGroupA.
 pathloss<PCMAX – preambleInitialReceivedTargetPower –
deltaPreambleMsg3 – messagePowerOffsetGroupB
 Transmission Power
PREAMBLE_RECEIVED_TARGET_POWER =
preambleInitialReceivedTargetPower + DELTA_PREAMBLE +
(PREAMBLE_TRANSMISSION_COUNTER – 1) * powerRampingStep
PPRACH = min{PCMAX, PREAMBLE_RECEIVED_TARGET_POWER +
PL}_[dBm]
 Time-frequency resources
MSG2: Random Access Response (RAR)
 eNodeB side: MAC generates RAR and sends it
over the DL-SCH.
E T RAPID Oct 1
UL Grant ：
- Hopping flag – 1 bit
- Fixed size resource block assignment – 10 bits R Timing Advance Command Oct 1
- Truncated modulation and coding scheme – 4 bits Timing Advance
- TPC command for scheduled PUSCH – 3 bits Command
UL Grant Oct 2
- UL delay – 1 bit
- CQI request – 1 bit
UL Grant Oct 3
UL Grant Oct 4
Temporary C-RNTI Oct 5
Temporary C-RNTI Oct 6

MSG2: Random Access Response (RAR)
 UE side: Intercept RA-RNTI on the PDCCH and the RAR consistent
with the sent preamble ID in the RA response window.
 If the collision is caused by multiple UEs choosing the same signature
sequence in the same leading time-frequency resource, then each UE
will receive an RAR.
Window start: The subframe where preamble is sent + three
subframes.
Window size: ra-ResponseWindowSize subframe.
1ms RAR Window
... preamble ...
time
Example
 Which ones of the following five UEs will cause contention? Which
ones can be successfully admitted?
UE1: RA-RNTI = 15, PreambleID = 6

UE1 and UE2 receive the same MSG2;

UE3, UE4 and UE5: Each receives its own MSG2.
MSG3
 MSG3 Content:
1. Initial access: The RRC Connection Request message is transferred
on the CCCH. At least NAS UE ID is transferred, but no NAS message
is sent.
2. RRC Connection Re-establishment: The RRC Connection Re-
establishment Request message is transferred on the CCCH. No NAS
message is transferred.
3. Handover: The RRC Handover Confirm message is transferred on the
DCCH. The UE C-RNTI is transferred in this message.
4. Other cases: The UE C-RNTI at least must be transferred (uplink data
and downlink data).
 The UE C-RNTI is transferred on the UL-grant in MSG2.
 Start MAC contention resolution timer. Start intercepting
PDCCH until the timer expires or stops.
Example
UE1 and UE2 receive the same MSG2. Both UE1 and UE 2
send MSG3 on the same UL grant, and contention arises ;
UE3, UE4 and UE5: Each receives its own MSG2. They
each send MSG3 on their own UL grant, and no contention arises.
MSG4: Contention Resolution
 Contention resolution identity: A UE receives C-

RNTI on PDCCH, or UE contention resolution ID
on DL-SCH.
UE Contention Resolution Identity Oct 1

 MSG3 includes CCCH SDU (scenarios 1 and 2), and

receives PDCCH for Temp-CRNTI.
If the MAC PDU is successfully decoded, and the MAC PDU
contains a UE contention resolution ID MAC control element
and matches the CCCH SDU transmitted in Msg3:
UE side:

Stops the contention resolution timer, and considers the
contention resolution successful;

Sets the Temporary C-RNTI to the C-RNTI;

Discards the temporary C-RNTI;

Considers this random access procedure successfully completed.
 MSG3 contains C-RNTI (other scenarios): Receive

PDCCH for C-RNTI.
UE side: Stops the contention resolution timer.

Considers the contention resolution successful.
Uses the original C-RNTI.
Discards the Temp-CRNTI when it expires.
Completes the random access procedure.
Example
UE1 and UE2 receive the same MSG2, and they both send
MSG3 on the same UL grant. Therefore, contention arises. Contention
resolution: Only one UE can have a successful access, or both UEs
fail to be admitted.
UE3, UE4 and UE5: They each receive their own MSG2, and send
MSG3 on their respective UL grant. All UEs are successfully admitted
as there is no contention.
Non-Contention-Based Random Access
 MSG0: In non-contention-based random access, the eNodeB assigns
a random access preamble to a UE through downlink dedicated
signaling.
 MSG1: Use a dedicated preamble.

 MSG2: The random access procedure ends once the the RAR is
received.
Content
 Cell Search
 Random Access
 TAU Procedure
Attachment Procedure
Perform cell selection
upon UE switch-on, and
receive system
information before the
Attach procedure
Including Attach Request, PDN connectivity request messages
(Including Messages)
8. Set up default
EPS bearer
(Including
(Including
(Including
(Including
20. Update
bearer
Detect User
inactivity
22. Update
bearer
NAS Signaling Connection Setup
Establish an RRC
Connection
Establish an S1
Connection
Attach Request
 RRCConnectionSetupComplete, and InitialUEMessage send the NAS
message Attach Request to EPC.
InitialContextSetupRequest
 This message is the initial context setup request sent to eNodeB from
the MME, requesting the eNodeB to establish a bearer resource. This
messages contains security context, and possibly other parameters
such as user radio capabilities and handover restriction lists.
 The security capability parameters of UE are sent to core network
through the attach request message, and then the core network
transmits the message to eNodeB.
UE Capability Enquiry
 The eNodeB will not send a UECapabilityEnquiry message to the UE if
initialContextSetupRequestMsg contains UE Radio Capability IE.
Otherwise, the eNodeB will send the UECapabilityEnquiry message to
the UE. After the UE reports the radio capability information, the eNodeB
will resend a UE Capability Info Indication message to the core network to
report UE radio capability information.
UECapability Enquiry
 The eNodeB will not send UECapabilityEnquiry to the UE if
initialContextSetupRequestMsg contains the UE Radio Capability IE.
Key System in LTE
 key system
USIM / AuC K
CK, IK
UE / HSS
KASME
UE / MME
KNASenc KNASint
KeNB / NH
UE / eNB
KUPenc KRRCint KRRCenc

Distribution of Authentication Data
 Auth authentication vector
 Quadruple: RAND, AUTN, XRES, and K ASME .
 3G: AV Quintuple: RAND, AUTN, XRES, CK, and

IK.
VLR/SGSN HE
Authentication data request
IMSI
Authentication data response

AV(1..n)
Authentication
 After receiving an Authentication Request message, a UE verifies the

freshness of the AUTN. The access network would be considered as
“trusted” if the authentication is passed.
ME/USIM MME
User authentication request (RAND, AUTN, KSIASME)
User authentication response (RES)
 USIM figures out RES.

 A UE responds with an Authentication Response message that
contains RES.
 The MME checks whether RES and XRES are consistent; if so, the UE
passes the authentication.
Security Mode Commands
 NAS layer security mode command

 Negotiate NAS algorithm between MME and UE.
 Calculate the NAS integrity protection key and encryption key
 AS layer security mode command

 Negotiate AS algorithm between eNodeB and UE.
 Calculate the NAS integrity protection key and encryption key

NAS Security Mode Commands
 According to the security capabilities reported by
the UE, the MME chooses the encryption and
integrity protection algorithms used by the NAS
layer.
 The MME sends an NAS security mode command
to the UE.
AS Security Mode Command
 eNodeB initiates AS layer security mode command procedure.
 Send Security Mode Command which is integrity protected. After that, start
downlink ciphering of RRC and user data.
 The UE performs integrity check.
NAS Information Delivery
 UL Information Transfer (UU)
 Uplink NAS Transport (S1)
 DL Information Transfer (UU)
 Downlink NAS Transport (S1)
Non-switch-off Detach Procedure: RRC_IDLE
UE eNB EPC
the EPS capability of

the UE is disabled
1. RA Preamble
2. RA Response
3. RRC Connection Request
4. RRC Connection Setup
5. RRCConnectionSetupComplete
(Including Detach Request)
6. Initial UE message
Clear all EPS
(Including Detach Request）
bearers and RB
resources
7. Security
Clear all EPS bearers

and TEID resources
of the UE
8. DOWNLINK NAS TRANSPORT

(Including Detach Accept)
9. DLInformationTransfer
(Including Detach Accept）
10. UE CONTEXT RELEASE

COMMAND
11. RRC Connection Release
12. UE CONTEXT RELEASE COMPLETE

Enter IDLE mode
again
Detach Procedures: RRC_CONNECTED
UE eNB EPC In non-switch-off detach
the EPS capability of
the UE is disabled
procedure, the UE receives a
Detach Accept response message
1. ULInformationTransfer
(Including Detach request Messages) from the MME and an RRC
Connection Release message from
2. UPLINK NAS TRANSPORT
the eNodeB.
Clear all EPS
bearers and RB （Including Detach request Messages）
resources
Clear all EPS bearers UE eNB EPC

and TEID resources
of the UE
UE switches off,
and initiates a
3. DOWNLINK NAS TRANSPORT Detach procedure
(Including Detach Accept Messages)
In IDLE mode, the UE initiates random access
and RRC connection setup procedures first
4. DLInformationTransfer
（Including Detach Accept Messages)
1. NAS: Detach Request（Switch off）
COMMAND
Clear all EPS Clear all EPS bearers
bearers and RB and TEID resources
6. RRC Connection Release resources of the UE
2. UE Context Release Command

COMPLETE
3. UE Context Release Complete
switch-off Detach Procedures
UE eNB EPC
UE switches off,
and initiates a
Detach procedure
In IDLE mode, the UE initiates random access

and RRC connection setup procedures first
1. NAS: Detach Request（Switch off）
Clear all EPS Clear all EPS bearers

bearers and RB and TEID resources
resources of the UE

Attach/Detach Tracking Signaling
NAS message
Set up RRC
connection
Set up S1
connection
NAS signaling connection
setup complete
DETACH procedure
Non-switch-off Detach Procedure
(RRC_CONNECTED)
Content
 Cell Search
 Random Access
 TAU Procedure
UE Initiated Service Request Procedure UE
If there is pending
data or signaling in
IDLE mode, the UE
eNB EPC
initiates a service
request procedure
1. RA Preamble
2. RA Response
In IDLE mode, a UE initiates a service 3. RRCConnectionRequest
request procedure to transfer service data.

4. RRCConnectionSetup
5. RRCConnectionSetupComplete
(containing Service Request message)
6. Initial UE message (containing
RRCConnectionSetupComplete, and Initial

Service Request message)
7. Authentication
UE Message contain Service Request. 8. S1-AP: Initial Context Setup Request
9. UECapabilityEnquiry
10. UECapabilityInformation
11. UE Capability Info Indication

12. SecurityModeCommand
13. SecurityModeComplete
14. RRCConnectionReconfiguration
15. RRCConnectionReconfigurationComplete
16. S1-AP: Initial Context Setup Response
First Uplink Data
Update bearer
First Downlink Data
Detect user
inactivity
17. UE Context Release Request (Cause)
Update bearer
19. RRC Connection Release

Content
 Cell Search
 Random Access
 TAU Procedure
Paging Procedure
UE eNB EPC UE eNB EPC
1. NAS: Paging (S_TMSI) 1. NAS: Paging (IMSI)

2. NAS: Paging (S_TMSI) 2. NAS: Paging (IMSI)
Same as steps 1 through 16 in the UE-initiated Service Request procedure Same as steps 1 through 19 in the UE-initiated Attach Request procedure
Content
 Cell Search
 Random Access
 TAU Procedure
TAU Procedure: Initiated in RRC_IDLE Mode
UE eNB EPC
The TAI in IDLE

mode is not on the
stored TAI list
1. RA Preamble
 In lDLE mode, if there is pending uplink data or 2. RA Response
uplink signaling (TAU-independent), the UE sets 3. RRCConnectionRequest
an “active” flag in TAU request message to 4. RRCConnectionSetup
request for the setup of user plane resources, 5. RRCConnectionSetupComplete

(containing TAU request)
and maintains the NAS signaling connection 6. Initial UE message

(containing TAU request)
after the TAU procedure ends. If the UE does not 7. Authentication/Security
set an “active” flag in the TAU request message,

8. Update UE context
between MMEs
the NAS signaling connection is released upon

9. Initial context setup request
(containing TAU Accept)
10. UECapabilityEnquiry
completion of the TAU procedure. 11. UECapabilityInformation
 The UE needs to respond with a TAU complete

12. UE Capability Info Indication
13. SecurityModeCommand
message if TAU accept is assigned a new GUTI. 14. SecurityModeComplete
Otherwise, the UE does not respond. 15. RRCConnectionReconfiguration

（containing TAU Accept）
17. Initial context setup response
（containing TAU Complete）

First Uplink Data
20. Update
First Downlink Data bearer
TAU Procedure: Initiated in RRC_CONNECTED
Mode
UE eNB EPC
TAU flow chart: The TAI in

CONNECTED mode
 Messages 1 to 2: UE transparently transmits the is not on the stored
TAI list
TAU request to EPC. 1. ULInformationTransfer (containing
TAU request)
 Message 3: The EPC updates UE context in the
MME. 2. UPLINK NAS TRANSPORT
（containing TAU request）
 Messages 4 to 5: EPC transmits TAU accept
message to eNodeB in a Downlink NAS Transport 3. Update UE context
message, and then to UE. between MMEs
 Messages 6 to 7: UE transparently transmits the 4. DOWNLINK NAS TRANSPORT

(containing TAU Accept)
TAU Complete message to EPC.
 NAS signaling connection will not be released 5. DLInformationTransfer
（containing TAU Accept）
upon completion of the procedure.
 UE needs to respond with a TAU complete 6. ULInformationTransfer
message if TAU accept is assigned a new GUTI.
Otherwise, the UE does not respond. 7. UPLINK NAS TRANSPORT
Content
 Cell Search
 Random Access
 TAU Procedure
LTE Handover Measurement Events
 Event A1: Serving becomes better than absolute threshold.
 Event A2: Serving becomes worse than absolute threshold.
 Event A3: Neighbor becomes amount of offset better than serving.
 Event A4: Neighbor becomes better than absolute threshold.
 Event A5: Serving becomes worse than absolute threshold 1, and neighbor
becomes better than another absolute threshold 2.
 Event B1: Neighbor becomes better than absolute threshold.
 Event B2: Serving becomes worse than absolute threshold 1 and neighbor
becomes better than another absolute threshold 2.
UE Source eNB Target eNB MME Serving Gateway
X2-Based HO 1. Measurement Control
packet data
0. Area Restriction Provided
packet data
UL allocation Legend
L3 signalling
2. Measurement Reports
L1/L2 signalling
3. HO decision
User Data
4. Handover Request
Handover Preparation
5. Admission Control
6. Handover Request Ack
DL allocation
RRC Conn. Reconf. incl.
7.
mobilityControlinformation
Detach from old cell
Deliver buffered and in transit
and
packets to target eNB
synchronize to new cell
Handover Execution
8. SN Status Transfer
Data Forwarding
Buffer packets from

Source eNB
9. Synchronisation
10. UL allocation + TA for UE
11. RRC Conn. Reconf. Complete
packet data
packet data
12. Path Switch Request
13. User Plane update
request
End Marker
14. Switch DL path
Handover Completion
packet data
End Marker
15.User Plane update
response
16.Path Switch Request Ack
17. UE Context Release
18. Release
Resources
S1-Based HO
S1
Source Target S1 S11 S5

UE MME S-GW PDN-GW
eNodeB eNodeB
Handover
decision
Preparation Phase
Handover Required
Handover Request
Radio Resource
allocation
Handover Request ACK(Handover Command)
Handover Command
Handover Command
Handover Confirm
Handover Notify
User Plane Update Request
Execution Phase
User Plane Update Response
UE Context Release Command
Radio Resource
Release
UE Context Release Complete

S1-Based HO
Measurement Setup
 After the RRC connection is set

up, the RRCConnection Setup
message is sent together with the
first RRCConnection
Reconfiguration message that
carries the UE context setup
message.
Measurement Report
Handover Required
 Source eNodeB initiates

the handover Required
Handover Request
 Initiate a handover request to the
target eNodeB
HandoverRequestACK
 Target eNodeB
initiates a handover
request to the MME.
RRCConnection Reconfiguration
 RRCConnection
Reconfiguration contains a
dedicated preamble. The RA
is a non-contention one.
Content
 Cell Search
 Random Access
 TAU Procedure
Dedicated Bearer Setup Procedure
UE eNB EPC
No matched
classifier in
This procedure can be initiated only by UE or MME Connected mode
rather than eNodeB in RRC_CONNECTED mode. (containing Bearer resource
allocation request)

（containing Bearer resource allocation request）
There are no steps 1 and 2 if the MME initiates this
3. Bearer
procedure. assignment
request
4. E-RAB SETUP/MODIFY REQUEST

(containing Activate/Modify dedicated
EPS bearer context request)
（containing Activate/Modify dedicated
EPS bearer context request）
7. E-RAB SETUP/MODIFY
RESPONSE
（containing Activate/Modify dedicated EPS bearer
context accept）

（containing Activate/Modify dedicated EPS bearer
context accept）
Uplink Data
10. Bearer
assignment
response
Downlink Data
Dedicated Bearer Modification Procedure UE eNB EPC
Modify a dedicated
EPS bearer in
Connected mode
This procedure can be only 1. ULInformationTransfer

(containing Bearer resource
initiated by UE and MME rather modification request)
than eNodeB in 2. UPLINK NAS TRANSPORT

（containing Bearer resource
RRC_CONNECTED mode.
modification request）
3. Bearer
modification
There are no steps 1 and 2 if the 4. E-RAB
SETUP/MODIFY/RELEASE
request
MME initiates this procedure. COMMAND

(containing
Activate/Modify/Deactivate EPS
bearer context request)
(containing Activate/Modify/Deactivate
EPS bearer context request)
7. E-RAB SETUP/MODIFY/RELEASE RESPONSE
(containing Activate/Modify/Deactivate
EPS bearer context accept)

(containing Activate/Modify/Deactivate EPS bearer
context accept)
10. Bearer
modification
response
Dedicated Bearer Release Procedure
UE eNB EPC
This procedure is initiated only in 1. Bearer

release request
the RRC_CONNECTED mode.
2. E-RAB RELEASE COMMAND
(containing Deactivate EPS bearer context request)
eNodeB releases
resources related
to this bearer
（containing Deactivate EPS bearer context request）
Release DRB and

EPS bearer
resources
5. E-RAB RELEASE RESPONSE
（containing Deactivate EPS bearer context accept）

（containing Deactivate EPS bearer context accept）
8. Bearer release
response

B - 01 - TDD LTE Signaling Procedures

Uploaded by

Copyright:

Available Formats

B - 01 - TDD LTE Signaling Procedures

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

B - 01 - TDD LTE Signaling Procedures

Uploaded by

Copyright:

Available Formats

TDD-LTE Signaling Procedures

TDD Products Support Department

the preceding two steps, and then the RS

estimate by checking the RS. acquire the BCH

 Read PBCH for acquiring other system Read BCH to acquire

and systemFrameNumber (SFN) in MIB, to

 Contention-based random access:

 Non-contention-based random access: No need to

Random Access Preamble 1

Random Access Response 2 2 Random Access Response

4 is used only for frame structure type 2

random access resources.

each radio frame, in even number of frames only or in odd number

first half of the frame or the last half of the frame.

random access resources. The subframes are numbered from 0,

Downlink Special Uplink

indicates the frequency offset of the PRACH resource,

Take UL/DL configuration 1 as an example

Preamble ID:0 to sizeOfRA-PreamblesGroupA – 1

 GROUP A/B selection

Temporary C-RNTI Oct 5

Temporary C-RNTI Oct 6

1ms RAR Window

... preamble ...

UE1: RA-RNTI = 15, PreambleID = 6

UE1 and UE2 receive the same MSG2;

 Contention resolution identity: A UE receives C-

UE Contention Resolution Identity Oct 1

UE Contention Resolution Identity Oct 2

UE Contention Resolution Identity Oct 3

UE Contention Resolution Identity Oct 4

UE Contention Resolution Identity Oct 5

UE Contention Resolution Identity Oct 6

 MSG3 includes CCCH SDU (scenarios 1 and 2), and

 MSG3 contains C-RNTI (other scenarios): Receive

UE side: Stops the contention resolution timer.

 MSG1: Use a dedicated preamble.

Including Attach Request, PDN connectivity request messages

KUPenc KRRCint KRRCenc

 3G: AV Quintuple: RAND, AUTN, XRES, CK, and

Authentication data response

 After receiving an Authentication Request message, a UE verifies the

User authentication request (RAND, AUTN, KSIASME)

User authentication response (RES)

 USIM figures out RES.

 NAS layer security mode command

 Calculate the NAS integrity protection key and encryption key

 AS layer security mode command

 Calculate the NAS integrity protection key and encryption key

the EPS capability of

3. RRC Connection Request

4. RRC Connection Setup

Clear all EPS bearers

8. DOWNLINK NAS TRANSPORT

10. UE CONTEXT RELEASE

11. RRC Connection Release

12. UE CONTEXT RELEASE COMPLETE

Clear all EPS bearers UE eNB EPC

2. UE Context Release Command