Sie sind auf Seite 1von 57

MobileComm Professionals, Inc.

Your Partner for Wireless Engineering Solutions


2

Agenda

Cell Search
Channel Mapping
RACH Procedures
RRC Procedures
IP Address Allocation
3

Cell Search
System Acquisition(Initial Procedure)
4

System
Power On Cell Search Information Random User Data
and Selection Receive Access Tx/Rx

Initial Access Procedure

In LTE a terminal must perform some certain steps before it receives or transmits data.

After mobile switches on, it runs a low-level acquisition procedure so as to identify


nearby long term evolution (LTE) cells and discover how they are configured.

After these steps called initial access procedure the terminal is able to receive and
transmit its user data.
5

Steps In Cell Acquisition


Step Task Information Obtained
Symbol Timing
1 Receive PSS
Cell Identity within group
Frame timing
Physical cell identity
2 Receive SSS
Transmission mode
Cyclic prefix duration
Amplitude and phase reference for demodulation.
3 Start reception of RS
Power reference for channel quality estimation
Number of transmit antennas
Downlink bandwidth
4 Read MIB from PBCH
System frame number
PHICH configuration
5 Start reception of PCFICH Number of control symbols per sub frame

6 Read SIBs from PDSCH System information


Cell Search
6

Frequency Acquisition
UE search the center frequency by searching DC part
Decode BCH which occupies 62 subcarriers (6 RBs) at the center
frequency.
BCH tells the frequency information of the system (eg. System
Frequency Bandwidth)
Time Sync Process
UE decode Primary sync (PSS) with three different Primary Sync Sequence
and figure out which sequence is assigned for the cell and obtain the
primary time sync as well.
Apply the primary sync sequence (PSS) with the Secondary Sync code (SSS)
and figure out which sequence is assigned for the cell.
Synchronization Signals
7

Both the FDD and TDD versions of LTE broadcast Synchronization Signals in the
downlink direction:
Primary Synchronization Signal (PSS)
Secondary Synchronization Signal (SSS)
Synchronization Signals are broadcast within every 10 ms radio frame
The UE uses the Synchronization Signals to:
Achieve radio frame, sub-frame, slot and symbol synchronization in the
time domain
Identify the center of the channel bandwidth in the frequency domain
Deduce the Physical layer Cell Identity (PCI)
Detecting the Synchronization Signals is a prerequisite to measuring the cell
specific Reference Signals and decoding the Master Information Block (MIB) on
the Physical Broadcast Channel (PBCH)
P-SS
8

The PSS is used to:


Achieve sub-frame, slot and symbol synchronization in the time
domain
Identify the center of the channel bandwidth in the frequency domain
Deduce a pointer towards 1 of 3 Physical layer Cell Identities (PCI)
PCI are organized into 168 groups of 3 so the Primary
Synchronization Signal identifies the position of the PCI within the
group but does not identify the group itself
Frequency Synchronization PSS
9

3 different PSS sequences


corresponding to 3 different cell
Length 63 Zadoff-Chu Sequence IDs.
Zadoff Chu Sequences are They could be generated by using
based on CAZAC = Constant a different root sequence M for
ZCM(0) ZCM(1) ZCM(62) the Zadoff-Sequences
Amplitude Zero Auto-
Correlation sequences Five zeros Five zeros
0 0 0 0
Cell ID Root index (M)
OFDM Modulator 0 25
1 29
2 34
62 subcarriers (d.c. not included)

72 subcarriers (d.c. not included)


PSS structure in frequency domain -> only 62 subcarriers out of 72 used. This is because the length of
the Zadoff-Chu Sequence is 63 (d.c. not included)
3GPP TS 36.211
PSS Primary Synchronisation Signal
10

Time slot (0.5 ms) syncronization


PSS placed strategically at the beginning and middle of frame
Estimation is vendor specific (matched filtering)
Frame ambiguity of 0.5 ms

Find physical layer cell ID


1 out of 3 sequences sent on PSS
1 to 1 mapping with the physical cell ID (table specified by 3GPP*)
The cell ID group not known yet

UE
eNodeB
SSS Secondary Synchronisation Signal
11

Frame (10 ms) synchronization


2 different sequences depending on the cell group are sent: SSS0 and SSS1
By observing the combination of pairs SSS0 and SSS1 the UE can identify either the begining
or the middle of the frame
Example: the sequence SSS0-PSS is indicating the begining of the frame, SSS1-PSS the
middle of the frame

Find physical layer cell ID group


Sequences SSS0 and SSS1 are mapped with the cell id group 1..168 (table specified by 3GPP*)
The combination of SSS0 and SSS1 is giving the cell ID group
Frequency Synchronization SSS
12

a , b = two different 2 different SSS per cell:


cyclic shifts of a single SSS0 in subframe 0 and SSS1
Length-31 binary sequence in subframe 5.
length-31
binary sequence SSS0 and SSS1 have the same
a0 a1 a30 b0 b1 b30 structure but are shifted in frequency domain

The cyclic shift is


0 0 0 0
Dependent on the
Physical layer cell OFDM Modulator
ID group (1..168)
62 subcarriers (d.c. not included)
SSS0 in
subframe 0
SSS1 in
subframe 5
72 subcarriers (d.c. not included)
SSS structure in frequency domain
S-SS
13

The SSS is used to:


Achieve radio frame synchronization
Deduce a pointer towards 1 of 168 Physical layer Cell Identity (PCI) groups
Allows the PCI to be deduced when combined with the pointer from
the PSS
14

PSS and SSS


PSS and SSS Frame in Frequency and Time Domain for FDD Case
Frequency

6 RBs 72 subcarriers = 1.4 MHz


SSS

(minimum LTE Bandwidth)


PSS

Reference signals

Unused RE

5 ms repetition Time
period

10 ms Radio frame

One subframe (1 ms)


15

Find Cell

Group #0 Group #1 Group #2 Group


#167
PCI PCI PCI PCI501
PCI10 PCI2 PCI43 PCI5 PCI76 PCI8 PCI502 PCI503

PSS signal
3 different sequences called Physical-Layer Identities (0-2)
PCI: Primary and Secondary Synchronization

SSS signal
168 different sequences called Physical-Layer Cell-Identity groups (0-167)

168 Physical-Layer Cell-Identity groups with 3 Physical-Layer Identities per


group
168 x 3 = 504 Physical-Layer Cell Identities
16

Mapping
Timing Of Synchronization Signals -FDD
17

This example assumes the normal cyclic prefix because there are 7 symbols
within each time slot.
The extended cyclic prefix follows a similar pattern except there are only 6
symbols within the time slot (the SSS and PSS remain within the last two
symbols of the time slot)
Timing Of Synchronization Signals -TDD
18

The extended cyclic prefix follows a similar pattern except there are only 6 symbols
within the time slot (the SSS remains within the last symbol of time slots 1 and 11,
while the PSS remains within the third symbol of time slots 2 and 12)

In the case of TDD, the SSS and PSS are not in adjacent symbols.
PSS and SSS
19

PSS and SSS Frame in Frequency and Time Domain for FDD Case

SSS PSS

Frequency

6 RB

Subframe 0 Subframe 5

Time
20

Frequency Acquisition
(Time-slot & Frequency synchronisation
PSS Primary + Physical cell id (0,1,2) )
Synchronisation
Signal
(Frame synchronisation
SSS Secondary + Physical Cell id group (1..168) )
Synchronisation UE
eNodeB
Signal

Physical Cell Identities


21

Downlink Reference signals

For coherent demodulation terminal needs channel estimate for each subcarrier
Reference signals used for channel estimation
1) Too many signals reduce the DL capacity
2) Too less signals may be not be enough for channel estimation
3) Easy to be found by UEs

There are different type of reference signals

1. Cell specific DL reference signals


Every DL subframe
Across entire DL bandwidth
2. UE specific DL reference signals
Sent only on DL-SCH
Intended for individual UEs
22

PBCH Design Criteria

Detectable without the knowledge of system Bandwidth


mapped to the central 72 subcarriers
over 4 symbols
during second slot of each frame

Low system overhead & good coverage


Send minimum information only the MIB (Master Information Block)
SIBs (System Information Blocks) are sent on PDSCH

MIB (Master Information Block) content:


DL system Bandwidth
PHICH configuration (PHICH group number)
System frame number SFN
23

PBCH Mapping
Frequency
Slot 0 Slot 1

PSS

6 RBs= 72 Sub-carriers=1.4MHz
SSS
Reference Signal
Unused RE
PBCH

Time
PBCH Mapping
24

Slot 0 Slot 1

Frequency
6 RBs 72 subcarriers = 1.4 MHz
(minimum LTE Bandwidth)
SSS

PSS

Reference signals

Unused RE

PBCH

Time

First subframe (1 ms)


PBCH Repetition Pattern 25

one radio frame = 10 ms


72 subcarriers

Repetition Pattern of PBCH = 40 ms


26

PBCH Repetition Pattern


Carries the Master Information Block (MIB)
Includes indication of system bandwidth
Robust design for cell-wide coverage:
Low rate, QPSK, robust channel coding (1/3-rate tail-biting convolutional code with repetition),
40 ms TTI.

Repetition Pattern of PBCH = 40 ms


27

PCFICH And PHICH

One PHICH group


contains 8 PHICHs
28

PDCCH
PDCCH = Physical Downlink Control Channel
Used for
DL scheduling assignments
UL scheduling grants
Power control commands
One PDCCH carrier one message with a specific Downlink Control Information (DCI)
Multiple UE-s scheduled simultaneously -> Multiple PDCCH transmissions in a subframe
29

Size of the PDCCH Region

PDCCH region
1,2,3 OFDM symbols
in the beginning of the sub
frame

not allocated by PCFICH,


PHICH
PDSCH Physical Downlink Shared Channel
30

Contain the actual user data from DL-SCH

Use the available Resource Elements

eNodeB
Allocation is signalled by PDCCH UE

Also used for:

SIBs (System Information Block) of the system information


Paging
31

Physical Downlink Shared Channel


32

PDSCH Allocation
33

PUCCH
34

Uplink Reference Signals

Demodulation Reference Sounding Reference


Signals Signals

Associated with transmission of Not Associated with UL data


uplink data on PUSCH or PUCCH transmissions

Used for channel estimation for Used for estimation of the UL


coherent detection and channel quality to enable the
demodulation (both PUCCH and channel dependent scheduling
PUSCH)
35

RACH
36

Random Access Procedure


The random access procedure is characterized by
- Common procedure for FDD and TDD;
- One procedure irrespective of cell size;

The random access procedure is performed for the following five events:
- Initial access from RRC_IDLE
- RRC Connection Re-establishment procedure
- Handover
- DL Data arrival during RRC_CONNECTED requiring random access procedure
- UL data arrival during RRC_CONNECTED requiring random access procedure

The random access procedure takes two distinct forms:


- Contention based
- Non-contention based
37

Power Ramping
38

RACH Procedures

Non-contention Based
Contention Based
39

Scenario

How can multiple terminals perform


UE1 random access attempt at the same time
without collision?

UE2

Solution ?
eNodeB UE3

64 different orthogonal Preambles available in


each cell obtained by cyclic shift of a Zadoff-
Chu sequence
If however collision is happening (2 UEs using
the same preamble) -> contention resolution
process
40

Initial Access

1. PRACH Preamble sent to the eNodeB

2. Random Access response, ID of the


received preamble, C-RNTI is sent to UE
from eNodeB through PDSCH Physical
Downlink Shared Channel

3. RRC Connection request, C-RNTI, TMSI


is sent through PUSCH Physical Uplink
Shared Channel
eNodeB 4. ContentionResolution, C-RNTI & TMSI is UE
sent through PDSCH Physical Downlink
Shared Channel
41

RRC Connection
42

RRC Connection
The RRC states can further be characterised as follows:

-RRC_IDLE:
A UE specific DRX may be configured by upper layers.
UE controlled mobility;
The UE:
Monitors a Paging channel to detect incoming calls, system
information change, Notification,
Performs neighboring cell measurements and cell (re-)selection;
Acquires system information.
43

RRC Connection

RRC_CONNECTED
Transfer of unicast data to/from UE.
Network controlled mobility, i.e. handover and cell change order with
optional network assistance (NACC) to GERAN;
The UE:
Monitors a Paging channel and/ or System Information Block Type 1 contents
to detect system information change, notification,
Monitors control channels associated with the shared data channel to
determine if data is scheduled for it;
Provides channel quality and feedback information;
Performs neighbouring cell measurements and measurement reporting;
Acquires system information.
E-UTRAN Initial Attach 44

A UE/user needs to register with the network to receive services that require registration. This registration is
described as Network Attachment.
New MME Old MME/SGSN

1.Attach request
2.Attach request EIR

3.Identification request
3.Identification response
4.Identity request

4.Identity response
5a.Authentication/Security/ME identity
5b. ME identity check
6.Delete bearer request

6.Delete bearer response 6.PCRF interaction


7.Update location
8.Cancel location
8.Cancel location ACK
45

E-UTRAN Initial Attach


New MME Old MME/SGSN

10.Insert subscriber data


10.Insert subscriber data
11.Update location ACK

12.Create default bearer request


13.Create default bearer request
14.PCRF interaction
15.Create default bearer response

16.Create default bearer response First Downlink data

17.Attach accept

18.Radio bearer establishment request


19.Radio bearer establishment response
20 Attach complete

First Uplink Data


46

E-UTRAN Initial Attach


New Old MME/SGSN
MME

21.Updated Bearer request

22.Updated Bearer response

First downlink data

23.Update location request

24.Update location response


47

Detach
48

E-UTRAN Detach
The Detach procedure allows:
- the UE to inform the network that it does not want to access the EPS any longer, and
- the network to inform the UE that it does not have access to the EPS any longer.

The UE is detached either explicitly or implicitly:

- Explicit detach: The network or the UE explicitly requests detach and signal with each other.
- Implicit detach: The network detaches the UE, without notifying the UE. This is typically the case when
the network presumes that it is not able to communicate with the UE, e.g. due to radio conditions.

Three detach procedures are provided when the UE accesses the EPS through E-UTRAN. The first
detach procedure is UE-initiated detach procedure and other detach procedures are network-
initiated detach procedure:

- UE-Initiated Detach Procedure;


- MME-Initiated Detach Procedure;
- HSS-Initiated Detach Procedure.
49

UE-initiated Detach procedure

1.Detach request

2.Delete bearer
request
3.Delete bearer request

4.Delete bearer response

5.PCRF interaction
6.Delete bearer response
7.Detach accept

8.Signaling connection release


50

MME-Initiated Detach Procedure

1.Detach request

2.Delete bearer request

3. Delete bearer request


4.Delete bearer response
5.PCRF interaction

6.Delete bearer response


7.Detach accept

8.Signaling connection release


51

HSS-initiated Detach procedure

1. Cancel location
2. Detach request
3. Delete bearer request
4.Delete bearer request
5.Delete bearer response
6.PCRF interaction

7.Delete bearer response

8.Detach accept
9.Cancel location ACK
10.Signaling connection release
52

IP Address Allocation
Introduction
53

LTE networks are all IP networks. This means that they deliver all user
traffic in IP Packets, and provide users with always-on IP
connectivity.

When UE joins an LTE networks, a Packet Data(PDN) address(i.e. the


one that can be used in the PDN) is assigned to the UE for its
connection to the PDN, and a default bearer is established in the LTE
network(i.e. between UE and P-GW).
This default bearer remains connected(i.e. the IP address assigned to
the UE during the initial attach remains valid) until the UE is detached
from the LTE network.

A default bearer is established for each APN(Access Point Name)1 a


user has, and thus a unique IP address is assigned fro each APN. An IP
address can be an IPv4, IPv6 or IPv4/IPv6 type.
Dynamic IP Address allocation 54

UE Power On

1.Attach Request (PDN connectivity request)

IMSI, PDN Types=IPV4, PCO=DNS Server IPV4 2.Create Session Request


Address Request IMSI, PDN Types=IPV4, PDN 3.Create Session Request
4.Dynamic IP Address Allocation,
Address=0.0.0.0, PCO=DNS IMSI, PDN Types=IPV4, PDN UE IP=1.1.1.5
Server IPV4 Address Request Address=0.0.0.0, PCO=DNS
Server IPV4 Address Request Deliver DNS IP as well as UE IP

5.Create Session Response


PDN Types=IPV4, PDN Address=UE IP (1.1.1.5),
PCO=(Primary DNS IP, Secondary DNS IP)
6.Create Session Response
PDN Types=IPV4, PDN Address=UE IP (1.1.1.5),
7.Attach Accept(Activate default EPS Bearer Context Request PCO=(Primary DNS IP, Secondary DNS IP)

PDN Types=IPV4, PDN Address=UE IP (1.1.1.5),


PCO=(Primary DNS IP, Secondary DNS IP)
8 UE gets UE IP And DNS IP

EPS Default Bearer PDN Internet


IP Packet
Static IP Address allocation 55

UE Poweres On

1.Attach Request (PDN connectivity request)


2. Update Location Request
IMSI, PDN Types=IPV4, PCO=DNS Server IPV4
Address Request IMSI

3. Update Location Answer


IMSI, PDN Type=IPV4, PDN Address=Static UE IP(1.1.1.1)

4.Create Session Request


IMSI, PDN Type=IPV4, PDN Address=Static UE IP(1.1.1.1),
PCO=DNS Server IPV4 Address Request
5.Create Session Request
IMSI, PDN Type=IPV4, PDN Address=Static UE IP(1.1.1.1),
PCO=DNS Server IPV4 Address Request
Deliver DNS IP
6.Create Session Response
PDN Types=IPV4, PDN Address=Static UE IP (1.1.1.1),
7.Create Session Response PCO=(Primary DNS IP, Secondary DNS IP)
8.Attach Accept(Activate default EPS Bearer Context Request PDN Types=IPV4, PDN Address=Static UE IP (1.1.1.1),
PCO=(Primary DNS IP, Secondary DNS IP)
PDN Types=IPV4, PDN Address= Static UE IP (1.1.1.1),
PCO=(Primary DNS IP, Secondary DNS IP)
9 UE gets UE IP And DNS IP

EPS Default Bearer PDN Internet


IP Packet
Summary 56

Cell Search
Channel Mapping
RACH Procedures
RRC Procedures
IP Address Allocation
57

HAPPY LEARNING

MobileComm Professionals, Inc.


www.mcpsinc.com
www.mmentor.com

Das könnte Ihnen auch gefallen