CONFIDENTIAL Important Concepts and Its Relationship Dai Mi PD NB SW2

CONFIDENTIAL

Important Concepts and Its Relationship

Dai MiPD NB SW2

PD NB SW2 Page 2 CONFIDENTIALCONFIDENTIAL

UTRAN framework an protocols Basic concepts

UE related concepts UTRAN related concepts Radio resource concepts

Mappings of L1 resource Mappings of Internal IDs

Content


UTRAN Framework

RNS

RNC

RNS

RNC

Core Network

Node B Node B Node B Node B

Iu Iu

Iur

Iub IubIub Iub


RNC Control Plan Protocols

Node B

RNC

CN

UE RNC

RANAP

NBAP

RNSAPRRC

NBAP :Node B Application PartRANAP:Radio Access Network Appication PartRNSAP:Radio Network Subsystem Application PartRRC :Radio Resource Control


UU Interface Protocol structure

L3co

ntr

ol

contr

ol

contr

ol

contr

ol

LogicalChannels

TransportChannels

C-plane signalling U-plane information

PHY

L2/MAC

L1

RLC

DCNtGC

L2/RLC

MAC

RLCRLC

RLCRLC

RLCRLC

RLC

Duplication avoidance

UuS boundary

BMC L2/BMC

control

PDCPPDCP L2/PDCP

DCNtGC

RadioBearers

RRC


Iub interface protocol structure

Node BApplication Part

(NBAP)

AAL Type 2

ALCAP

TransportLayer

Physical Layer

RadioNetworkLayer

Radio NetworkControl Plane

TransportNetwork

Control Plane

DC

H FP

RA

CH

FP

ATM

DSC

H FP

AAL Type 5

User Plane

SSCF-UNI

SSCOP

AAL Type 5

SSCF-UNI

SSCOP

Q.2630.1

Q.2150.2

FA

CH

FP

PC

H FP

USC

H FP

CP

CH

FP


Iu Interface –CS domain protocol structure

Q.2150.1

Q.2630.1

RANAP Iu UP ProtocolLayer

TransportNetwork

Layer

Physical Layer

TransportUser

NetworkPlane

Control Plane User Plane

TransportUser

NetworkPlane

Transport NetworkControl Plane

RadioNetwork

Layer

ATM

SSCOP

AAL5

SSCOP

SSCF-NNI

AAL2AAL5

MTP3bMTP3b

SCCP

SSCF-NNI


Iu Interface-PS domain protocol structure

SSCF-NNI

SSCOP

AAL5

IP

SCTP

SCCP

SSCF-NNI

MTP3-BM3UA

RANAPIu UP Protocol

Layer

TransportNetwork

Layer

Physical Layer

TransportUser

NetworkPlane

Control Plane User Plane

TransportUser

NetworkPlane

Transport NetworkControl Plane

RadioNetwork

Layer

ATM

AAL5

IP

UDP

GTP-U

Physical Layer

ATM


Peer to peer layer protocols

RLC

RRC

L1

MM / SM / SMS

RRC

MAC

ATM

RANAP

AAL5

Relay

ATM

AAL5

3G SGSN RNS MS

Iu-Ps Uu

RLC SCCP

Signalling Bearer

MAC

L1

Signalling Bearer

RANAP

SCCP

MM / SM / SMS

gaohongmei


S-RNTI allocated for all UEs having a RRC connection

allocated by the SRNC

unique within the SRNC.

reallocated always when the SRNC for the RRC connection is changed and deallocated when the RRC connection is released.

U-RNTI U-RNTI = SRNC id + S-RNTI

Identifies the UE within UTRAN having a RRC connection

used as a UE identifier in cell update, URA update, RRC connection reestablishment and (UTRAN originated) paging messages and associated responses on the radio interface.

S-RNTI within the U-RNTI is used by the CRNC to route the received uplink messages towards the SRNC.

UE related concepts-UE Identifiers


C-RNTI allocated by a CRNC for a UE

unique within one cell controlled by the allocating CRNC

can be reallocated when a UE accesses a new cell with the cell update procedure.

• used as a UE identifier in all other DCCH/DTCH common channel messages on the radio interface.

DSCH-RNTI allocated by CRNC when a DSCH channel is configured

unique within the cell carrying the DSCH.

Usage of UE identifiers

used as a UE identifier for DTCH and DCCH in downlink when mapped onto DSCH transport channel.



TMSI ,P-TMSI TMSI allocated by VLRS and P-TMSI allocated by SGSNs

To support the subscriber identity confidentiality service



UE related concepts-UE state

Establish RRCConnection

Release RRCConnection

UTRA RRC Connected Mode

UTRA:Inter-RATHandover

GSM:Handover

Establish RRCConnection

Release RRCConnection

URA_PCH CELL_PCH GSMConnected

Mode

Establish RRConnection

Release RRConnection

Idle Mode

Camping on a UTRAN cell1 Camping on a GSM / GPRS cell1

GPRS Packet Idle Mode1

GPRSPacket

TransferMode

Initiation oftemporaryblock flow

Release oftemporaryblock flow

Cell reselection

CELL_DCH

out of service

in service

CELL_FACH

out of service

in service

out of service

in service



1.Idle Mode In idle mode, the UE shall perform a periodic search for higher priority PLMNs. The UE can initiate Location Area Update, Rout Area Update, CS Service, PS Service

and so on through initiating a RRC connection setup process. After a RRC connection setup process is successfully established, the UE will enter th

e UTRA RRC connect mode. When a RRC connection is released, the UE will enter the Idle Mode from UTRA RRC

connect mode.


2. RRC Connect Mode(CELL_DCH)The UE will enter the CELL_DCH state in the following conditions:

Change from IDLE to CELL_DCH by establishing RRC connection on dedicated channel. For example, A high traffic PS service(32kbps or above ) is established on CELL_DCH.

Change CELL_FACH to CELL_DCH because of RAB Setup or RAB Modify or DCCC.

DCCC(CELL_FACH to CELL_DCH) procedure is initiated by 4A measure report.



3. RRC Connect Mode(CELL_FACH)The UE will enter the CELL_FACH state in the following conditions:

Change from IDLE to CELL_FACH by establishing RRC connection on common channel. For example, a low traffic PS(8kbps) service is established on CELL_FACH.

Change CELL_DCH to CELL_FACH because of RAB release or RAB modify or DCCC.

DCCC(CELL_DCH to CELL_FACH) procedure is initiated by 4B measure report.

Change CELL_PCH or URA_PCH state to CELL_FACH through CELL UPDATE procedure.



4. RRC Connect Mode(CELL_PCH)The UE will enter the CELL_FACH state in the following conditions:

The UE enters the CELL_PCH state form CELL_FACH state by a cell update or a Radio Bearer reconfiguration process.

The UE enters the CELL_PCH state form CELL_DCH state by a Radio Bearer reconfiguration process.

In CELL_PCH state, RNC pages the UE in CELL area.



5. RRC Connect Mode(URA_PCH)

The UE enters the URA_PCH state form CELL_PCH state by a cell update procedure.

Note: When the UE sends out CELL UPDATE message, UE Changes from CELL_PCH to CELL_FACH, and after the cell update procedure complete the UE moves to URA_PCH state.

In URA_PCH state, RNC pages UE in URA area.



UTRAN related concepts

1.位置区（ Location Area） ,路由区（ Routing Area) , CELL, URA

MSC 管辖区：由若干位置区构成

SGSN 管辖区域：包含多个路由区，与 MSC 区无关

位置区（ LA ）：可由若干个小区组成，包含若干个路由区

路由区（ RA ）：由一个或多个小区构成，在位置区内统一编码

小区（ cell ）： UMTS 网络中最小的服务区域



位置区和路由区信息和不同实体之间有着不同的关系：

CN ：通过 LA/RA 信息识别和寻呼 UE ，在 IU 接口 Paging 消息中可以得到体现，通过和 UE 之间的直传消息（初始直传，上行直传）获得 UE 当前的 LA/RA 信息；

UTRAN ：可以准确获得 UE 当前所在小区的 LA/RA 信息，控制 UE当前的 LA/RA 信息在 UE 和 CN 两侧的更新；

UE ：在 RRC-IDLE 状态通过系统消息获取自己当前的 LA/RA 信息，在 RRC-CONNECT 状态通过和 UTRAN 之间和移动管理相关消息（主要是这些消息中的“ Cn Information” 信元）获取自己当前的LA/RA 信息，通过比较并最终决定是否发起位置区更新 / 路由区更新。



2. Controlling RNC, Serving RNC, Drift RNC

Controlling RNC: The RNC that has the overall control of the logical

resources of its node B's. only one Controlling RNC for any Node B.

Serving RNC: The RNC that in charge of the radio connection

between a UE and the UTRAN There is one Serving RNS for each UE that has a

connection to UTRAN.

Drift RNC: The RNC that supports the SRNC with radio

resources when the connection between the UTRAN and the UE need to use its cell(s)

The role of an RNS (Serving or Drift) is on a per connection basis between a UE and the UTRAN.



3.Iub interface

NCP (NodeB Control Port): is for NBAP common procedure.

One Node B has one NCP

set up via proprietary O&M.

corresponding to one signaling bearer (SAAL) and one pair of vpi/vci

CCP (Communication Control Port): is for NBAP dedicated procedure and

One NodeB may have multiple CCPs

all the dedicated NBAP signaling should be transferred on one CCP

corresponding to one signaling bearer (SAAL) and one pair of vpi/vci



Node B communication context: one UE will be assigned one Node B communication context by Node B when

using dedicated channel on air interface. may include several RL Bond on one CCP

CRNC communication context: one UE will be assigned one CRNC communication context by RNC when using

dedicated channel on air interface.

Transaction ID: to denote an ongoing procedure belonging to NCP or one Node B communication

context.

NCP or each of Node B communication contexts could have different transaction ID for the same procedure

the procedure type and the transaction ID together what can denote an ongoing procedure.



Transport layer address one Node-B configured one transport layer address

All transport channel use this address in th response message.

Binding ID the map relation from transport bearer(aal2) to transport channel

allocated by Node-B during transport channel setup and inform RNC in response message.

ALCAP protocol can setup one all2 connected to one transport bearer.


Radio Resource Concepts

UTRAN Access Point A conceptual point within the UTRAN performing radio transmission and

reception

Radio Linka logical association between a single UE and a single UTRAN access point.

Its physical realization comprises one or more radio bearer transmissions.



RABThe service that the access stratum provides to the non-access stratum for

transferring of user data between User Equipment and CN.

RAB sub-flows A Radio Access Bearer can be realized by UTRAN through several su

b-flows

correspond to the NAS service data streams that have QoS characteristics

sub-flows of a RAB are established and released at the RAB establishment and release, respectively.

sub-flows of a RAB are submitted and delivered together at the RAB SAP.

sub-flows of a RAB are carried over the same Iu transport bearer.

sub-flows of a RAB are organised in a predefined manner at the SAP The organisation is imposed by the NAS as part of its co-ordination responsibility.



RBThe service provided by the layer2 for transfer of user data between UE

and Serving RNC.

RRC Connection point-to-point bi-directional connection between RRC peer entities on the

UE and the UTRAN sides, respectively

An UE has either zero or one RRC connection.


Mappings of L1 Resource- max user number, midamble and midamble shift

max_user_numbermidam

ble shift 2 4 6 8 10 12 14 16

0 48 16 7 0 4 2 120 1201 112 48 28 16 16 12 4 02 80 49 32 28 22 13 83 112 70 48 40 32 22 164 91 64 52 42 31 245 112 80 64 52 40 326 96 76 62 49 407 112 88 72 58 488 100 82 67 569 112 92 76 64

10 102 85 7211 112 94 8012 103 8813 112 9614 10415 112

M i d a m

b le


Mappings of L1 Resource- max user number, midamble and midamble shift

m (1) - c 8 (1)

m (2) - c 8 (2) m (1) - c 4 ( 1)

m (3) - c 4 (2)

m (5) - c 4 (3)

m (7) - c 4 (4)

m (1) - c 2 (1)

m (5) - c 2 (2)

m (1) - c 1 (1)

m (1) - c 16 (1)

m (1) - c 16 (2)*

m (2) - c 16 (3)

m (2) - c 16 (4)*

m (3) - c 8 (3)

m (4) - c 8 (4)

m (3) - c 16 (5)

m (3) - c 16 (6)*

m (4) - c 16 (7)

m (4) - c 16 (8)*

m (5) - c 8 (5)

m (6) - c 8 (6)

m (7) - c 8 (7)

m (8) - c 8 (8)

m (5) - c 16 (9)

m (5) - c 16 (10)*

m (6) - c 16 (11)

m (6) - c 16 (12)*

m (7) - c 16 (13)

m (7) - c 16 (14)*

m (8) - c 16 (15)

m (8) - c 16 (16)*

E.g. Association for K=8 Midambles


Mappings of L1 Resource- VRU and Spreading Code

SC, see FRS3002VRU SF16 SF8 SF4 SF2 SF1

15 30 14 6 2 0

14 29

13 28 13

12 27

11 26 12 5

10 25

9 24 11

8 23

7 22 10 4 1

6 21

5 20 9

4 19

3 18 8 3

2 17

1 16 7

0 15


Mappings of L1 Resource- VRU and VCN

VCN

VRU SF16 SF8 SF4 SF2 SF1

15 15 31 47 63 79

14 14 30 46 62 78

13 13 29 45 61 77

12 12 28 44 60 76

11 11 27 43 59 75

10 10 26 42 58 74

9 9 25 41 57 73

8 8 24 40 56 72

7 7 23 39 55 71

6 6 22 38 54 70

5 5 21 37 53 69

4 4 20 36 52 68

3 3 19 35 51 67

2 2 18 34 50 66

1 1 17 33 49 65

0 0 16 32 48 64


Mappings of L1 Resource- Window Length and Max Number of Users on TS

MaxNofUsersTS WL (SF16, SF8, SF4, SF2,SF1) WL_code (Used in messages to L1)

16 8 0

14 9 1

12 10 2

10 12 3

8 16 4

6 16 4

4 16 4

2 16 4

* WL(in chips) = MIN(16, 128 / MaxNofUsersTs)


Mappings of Internal IDs -ID used for P-CCPCH, FPACH and PICH

Common Physi calChannel ID 1

Common Physi calChannel ID p

Al l ocated by RNC Al l ocated by BIC

P-CCPCH, FPACH, PICH

DL UD Conn ID 1Logi cal User ID 1

DL UD Conn ID pLogi cal User ID p

RR Connecti onID 1

RR Connecti onID p

Al l ocated by NBAP


Mappings of Internal IDs -ID used for PRACH


Common Physi calChannel ID p

Al l ocated by RNC Al l ocated by BIC

PRACH

UL UD Conn ID 1Logi cal User ID 1

UL UD Conn ID pLogi cal User ID p

RR Connecti onID 1

RR Connecti onID p

Al l ocated by NBAP


Mappings of Internal IDs -ID used for S-CCPCH

S-CCPCH

Logi cal User ID 1

Logi cal User ID 2

Logi cal User ID q

DL UD ConnID k

Al l ocated by BIC

DL CCTrCH ID



Common Physi calChannel ID q

Al l ocated by RNC

RR Connecti onID 1

RR Connecti onID 2

RR Connecti onID q

Al l ocated by NBAP


Mappings of Internal IDs -ID used for Dedicated Service

Communi cati onContext ID 1

RL ID 1

RL ID 2

RL ID m

RR Connecti onID 1

RR Connecti onID 2

RR Connecti onID m

Communi cati onContext ID 2

RL ID 1

RL ID 2

RL ID n

RR Connecti onID m+1

RR Connecti onID m+2

RR Connecti onID m+n

UL CCTrCH ID 1DL CCTrCH ID 1UL CCTrCH ID 2DL CCTrCH ID 2

UL CCTrCH ID pDL CCTrCH ID p

UL UD Conn ID 1DL UD Conn ID 1

Logi cal User ID 1UL UD Conn ID 2DL UD Conn ID 2

Logi cal User ID 2

UL UD Conn ID pDL UD Conn ID p

Logi cal User ID p

Al l ocated by RNCAl l ocated by

NBAPAl l ocated by

RNCAl l ocated by BIC

UL CCTrCH ID 1DL CCTrCH ID 1

UL CCTrCH ID 2DL CCTrCH ID 2

UL CCTrCH ID qDL CCTrCH ID q

UL UD Conn ID p+1DL UD Conn ID p+1

Logi cal User ID p+1UL UD Conn ID p+2DL UD Conn ID p+2

Logi cal User ID p+2

UL UD Conn ID p+qDL UD Conn ID p+q

Logi cal User ID p+q

Dedi cated Servi ce


Q & A


Thank you!

Documents

CONFIDENTIAL Important Concepts and Its Relationship Dai Mi PD NB SW2