02 - Call Setup

106
1 © 2005 Nokia Call Setup / Kittipong Thamapa Call Setup Call Setup

Transcript of 02 - Call Setup

Page 1: 02 - Call Setup

1 © 2005 Nokia Call Setup / Kittipong Thamapa

Call SetupCall Setup

Page 2: 02 - Call Setup

2 © 2005 Nokia Call Setup / Kittipong Thamapa

Call Setup

•RRC Connection Setup

•Transport Plan Setup

•Iu-CS Call Setup

•Iu-PS Call Setup

•HSDPA Call Setup

Page 3: 02 - Call Setup

3 © 2005 Nokia Call Setup / Kittipong Thamapa

Overview of Setting Up Call

Mobile Terminated Call (MTC)

ServiceRequest

Radio AccessBearer

Paging

Mobile Originated Call

RRCConnectio

n

Page 4: 02 - Call Setup

4 © 2005 Nokia Call Setup / Kittipong Thamapa

RRC Connection Setup

Page 5: 02 - Call Setup

5 © 2005 Nokia Call Setup / Kittipong Thamapa

Overview of Setting Up Call

Mobile Terminated Call (MTC)

ServiceRequest

Radio AccessBearer

Paging

Mobile Originated Call

RRCConnectio

n

Page 6: 02 - Call Setup

6 © 2005 Nokia Call Setup / Kittipong Thamapa

RRC Connection Setup UE Node-B RNC CN

RRC Connection Setup Request

RRC Connection Setup Complete

RRC Connection Setup

RRC RRC

RRCRRC

RRC RRC

NBAP Radio Link Setup

ALCAP Transport Bearer Setup

Page 7: 02 - Call Setup

7 © 2005 Nokia Call Setup / Kittipong Thamapa

RRC Connection Setup UE Node-B RNC CN

RRC Connection Setup Request ( CCCH on RACH)

Radio Link Setup Request NBAPNBAP

Radio Link Setup Response

NBAPNBAP

RRC Connection Setup Complete (DCCH on DCH)

RRC Connection Setup (CCCH on FACH)

Establish RequestALCAPALCAP

Establish ResponseALCAPALCAP

Layer 1 Synchronisation

NBAP Synchronisation

RRC RRC

RRCRRC

RRC RRC

Signalling Bearer

establishment

Page 8: 02 - Call Setup

8 © 2005 Nokia Call Setup / Kittipong Thamapa

RRC Connection Setup UE Node-B RNC CN

RRC Connection Setup Request (RACH)RRC RRC

SRNC

Admission Control

Select Transport Channel

Allocate RNTI

UE IEs

Measurement IEs

Initial UE identity

Establishment cause

Protocol errorindicator

Originating Conversational Call,

Originating Background Call,

Terminating Streaming Call,

Emergency Call,Inter-RAT cell reselection,

Registration,Detach,

Originating High Priority Signalling,

Call reestablishment,Terminating Low Priority

Signalling,

IMSI

TMSI & LAI

P-TMSI & RAI

IMEI

CHOICE

Page 9: 02 - Call Setup

9 © 2005 Nokia Call Setup / Kittipong Thamapa

RRC Connection Setup UE Node-B RNC CN

RRC Connection Setup Request (RACH)

Radio Link Setup Request

NBAPNBAP

RRC RRC

Message Discriminator

Message Type

Transaction ID

CRNC Communi-cation Context ID

DL DPCHInformation IEs

DL DPCHInformation IEs

DCH Information

DSCH Information

TFCI2 bearer information IEs

RL Information IEs

Transmission GapPattern Sequence

Information

Active PatternSequence Info

Page 10: 02 - Call Setup

10 © 2005 Nokia Call Setup / Kittipong Thamapa

RRC Connection Setup UE Node-B RNC CN

RRC Connection Setup Request (RACH)

Radio Link Setup Request

NBAPNBAP

Radio Link Setup Response

NBAPNBAP

RRC RRC

CRNC CommunicationContext ID

NodeB CommunicationContext ID

RadioLink Information List

RadioLink Information Item

DCH list RL Setup Response

Page 11: 02 - Call Setup

11 © 2005 Nokia Call Setup / Kittipong Thamapa

RRC Connection Setup UE Node-B RNC CN

RRC Connection Setup Request (RACH)

Radio Link Setup Request

NBAPNBAP

Radio Link Setup Response

NBAPNBAP

Establish RequestALCAPALCAP

Establish ResponseALCAPALCAP

RRC RRC

Start TX

Page 12: 02 - Call Setup

12 © 2005 Nokia Call Setup / Kittipong Thamapa

RRC Connection Setup UE Node-B RNC CN

RRC Connection Setup Request (RACH)

Radio Link Setup Request

NBAPNBAP

Radio Link Setup Response

NBAPNBAP

RRC Connection Setup (FACH)

Establish RequestALCAPALCAP

Establish ResponseALCAPALCAP

RRC RRC

RRC RRC

Page 13: 02 - Call Setup

13 © 2005 Nokia Call Setup / Kittipong Thamapa

RRC Connection Setup UE Node-B RNC CN

RRC Connection Setup (FACH)RRC RRC

UE IEs

RB IEs

TrCH IEs: UL/DL

PhyCH IEs: UL/DL

Initial UE ID

RRC Transaction ID

Activation Time

New U-RNTI

New C-RNTI

UTRAN DRX cycle length coefficient

RRC State Indicator

Capability updaterequirement

IMSI / TMSI and LAI / P-TMSI and RAI/ IMEI0..3

absolute CFN (0..255); default: now

CELL_DCH/CELL_FACH/CELL_PCH/URA_PCH

3..9

UE radio access FDD: TRUE/FALSEUE radio access TDD: TRUE/FALSEenumerated: GSM (optional)

RNC-ID , S-RNTI

(optional)

Signalling RBinformationto setup list

Signalling RBInformation

to setup RB identity

CHOICE RLC info type

RLC info

Same as RB

RB mapping info

Page 14: 02 - Call Setup

14 © 2005 Nokia Call Setup / Kittipong Thamapa

RRC Connection Setup UE Node-B RNC CN

RRC Connection Setup (FACH)RRC RRC

UE IEs

RB IEs

TrCH IEs: UL/DL

PhyCH IEs: UL/DL Added or ReconfiguredTrCH information list

UL/DL Transport channelinformation common forall transport channels

Added or ReconfiguredUL/DL TrCH information

optional:UARFCN uplink and downlinkdefault: operating band

Frequency Info

UL radio resources

DL radio resources

Page 15: 02 - Call Setup

15 © 2005 Nokia Call Setup / Kittipong Thamapa

RRC Connection Setup UE Node-B RNC CN

RRC Connection Setup Request (RACH)

Radio Link Setup Request

NBAPNBAP

Radio Link Setup Response

NBAPNBAP

RRC Connection Setup Complete (DCH)

RRC Connection Setup (FACH)

Establish RequestALCAPALCAP

Establish ResponseALCAPALCAP

RRC RRC

RRCRRC

RRC RRC

Layer 1 Synchronisation

NBAP Synchronisation

Page 16: 02 - Call Setup

16 © 2005 Nokia Call Setup / Kittipong Thamapa

RRC Connection Setup Complete UE Node-B RNC CN

RRC Connection Setup Complete (DCH)RRCRRC

• Release 99• Capabilities: PDCP, RLC, TrCH,

FDD RF, TDD RF, PhyCH, UE multi-mode/multi-RAT,security, UE positioning, measurement

0..3

1..maxCNdomains (4)

CS domain / PS domain

used to initialise the 20 MSBs of all hyperframe numbers

OP

UE IEs

Other IEs

RRC Transaction ID

START list

CN domainidentity

START

UE radio accesscapability

UE radio accesscapability extension

UE system specificcapability

Inter-RAT UEradio access

capability

1 to InterSysMessages (4)

GSM MS Classmark 2 /GSM MS Classmark 3

OP

Page 17: 02 - Call Setup

17 © 2005 Nokia Call Setup / Kittipong Thamapa

Transport Plane Setup

Page 18: 02 - Call Setup

18 © 2005 Nokia Call Setup / Kittipong Thamapa

Transport Plane Setup UE Node-B RNC CN

Establish RequestALCAPALCAP

Establish ResponseALCAPALCAP

Radio Link Setup Response

NBAPNBAP

Binding ID

Transport Layer Address

DAID-Dest. sign. assoc. ident

Path Identifier

Channel identifier (CID)

NSEA-Dest. NSAP serv. endpoint addr

Signalling association identifier

Binding ID

Page 19: 02 - Call Setup

19 © 2005 Nokia Call Setup / Kittipong Thamapa

AAL2UP without AAL2 Multiplexing

49 00123 020BTSID 0WAM0

123 021BTSID 0WAM1

Associate AAL2SIG terminate in same WAM

Transport Layer Address Format (A2EA)• Structure in RN 1.5 level is 49 + BTS ID + WAM serial number• Structure in RN 2.0 level is 49 + BTS ID + WAM physical

number + 0 49 + XXXXX + XXX

Page 20: 02 - Call Setup

20 © 2005 Nokia Call Setup / Kittipong Thamapa

AAL2UP with AAL2 Multiplexing

123 001BTSID 00AAL2SIG TPID

Page 21: 02 - Call Setup

21 © 2005 Nokia Call Setup / Kittipong Thamapa

AAL2UP without AAL2 Multiplexing

ZRII;

TREE= 1 ATYPE=N

DIGITS AL NBR RT CT SP NL RC DEST SDEST

4900123020 0 2 ROU NGC 0 0 APR 3 3

4900123040 0 3 ROU NGC 0 0 APR 6 5

4900123060 0 4 ROU NGC 0 0 APR 8 6

TREE= 2 ATYPE=N

DIGITS AL NBR RT CT SP NL RC DEST SDEST

456618190111 0 100 ROU NGC 0 0 APR 10 4

COMMAND EXECUTED

Page 22: 02 - Call Setup

22 © 2005 Nokia Call Setup / Kittipong Thamapa

Binding ID

Binding Identifier (Binding ID) is used to initialise the linkage between ALCAP and Application Part (RANAP, RNSAP, NBAP) identifiers.

Binding Identifier can be used both in Radio Network Control plane Application Part protocols and in Transport Network Control Plane's ALCAP protocol.

Binding ID binds the Radio and Transport Network Control plane identifiers together.

Page 23: 02 - Call Setup

23 © 2005 Nokia Call Setup / Kittipong Thamapa

Binding ID

AP-1

ALCAP-1

AP-1

ALCAP-1

AP-1

ALCAP-1

AP-2

ALCAP-2

AP-2

ALCAP-2

AP-2

ALCAP-1

Step 1

Step 2

Step 3

Radio Network Control Plane Setup (Response)

ALCAP Establish request

Node1 Transport Address Binding ID

Node1 Transport Address Binding ID

Node 1

Transport

address

Binding ID

Page 24: 02 - Call Setup

24 © 2005 Nokia Call Setup / Kittipong Thamapa

AAL type 2 connection establishment

Page 25: 02 - Call Setup

25 © 2005 Nokia Call Setup / Kittipong Thamapa

Explanation of parameters

•Cause (CAU)• Gives the reason of an operational error

• Describes the reason for the release of connection

• Indicates the reason why connection could not established

•Connection element identifier (CEID)• It consists of AAL type 2 path identifier and Channel identifier (CID).

• AAL type 2 path identifier has field size of 4 octets. A value of ‘0’ in all octets indicates “Null”.

• Channel identifier has field size of 1 octet. It can have value in the range of 8 to 255. A value of ‘0’ indicates “Null”.

•AAL type 2 service endpoint address (A2EA)• It carries end point address of the destination.

• It can have E.164 or NSAP format.

Page 26: 02 - Call Setup

26 © 2005 Nokia Call Setup / Kittipong Thamapa

Example of RRC Connection and Transport Setup

Page 27: 02 - Call Setup

27 © 2005 Nokia Call Setup / Kittipong Thamapa

RRC Connection Setup UE Node-B RNC CN

RRC Connection Setup Request (RACH)

Radio Link Setup Request

NBAPNBAP

Radio Link Setup Response

NBAPNBAP

RRC Connection Setup Complete (DCH)

RRC Connection Setup (FACH)

Establish RequestALCAPALCAP

Establish ResponseALCAPALCAP

Layer 1 Synchronisation

NBAP Synchronisation

RRC RRC

RRCRRC

RRC RRC

Page 28: 02 - Call Setup

28 © 2005 Nokia Call Setup / Kittipong Thamapa

Radio Link Setup Response RADIO LINK SETUP RESPONSE

NBAP-PDU

successfulOutcome

- procedureCode: 9

- criticality: reject

- messageDiscriminator: common

successfulOutcome

RadioLinkSetupResponse

protocolIEs

- id: 43

- criticality: ignore

CRNC-CommunicationContextID: 1033

- id: 73

- criticality: ignore

NodeB-CommunicationContextID: 160010

- id: 111

- criticality: ignore

RadioLinkInformationList-RL-SetupRsp

- id: 101

- criticality: ignore

RadioLinkInformationItem-RL-SetupRsp

- rL-ID: 1

- diversityIndication: mdc-is-done-at-rnc

dCH-Information-RL-SetupRsp

- id: 52

- criticality: ignore

DCH-List-RL-SetupRsp

DCH-List-Item-RL-SetupRsp

- dCH-ID: 24

- bindingID: '00000003'H

transportLayerAddress

- non-extended:'4900123020FFFFFFFFFFFFFFFFFFFFFFFFFFFFFF'H

- id: 142

- criticality: ignore

TrafficTP-ID: 1

Transport Layer Address Format (A2EA)

• Structure in RN 1.5 level is 49 + BTS ID + WAM serial number

• Structure in RN 2.0 level is 49 + BTS ID + WAM physical number + 0

49 + XXXXX + XXX

Binding ID

Page 29: 02 - Call Setup

29 © 2005 Nokia Call Setup / Kittipong Thamapa

Establish Request message DAID-Dest. sign. assoc. ident.: 00 00 00 00

- Message's Compatibility: 00h

Pass-on not possible:

- Do not send notification

- Pass on message or parameter

General action:

- Do not send notification

- Pass on message or parameter

CEID-Connection element ident.

- Parameter's Compatibility: 00h

Pass-on not possible:

- Do not send notification

- Pass on message or parameter

General action:

- Do not send notification

- Pass on message or parameter

Parameter length: 5 (05h)

- Path identifier: 1001 (3E9h)

- Channel identifier: 12 (Ch)

NSEA-Dest. NSAP serv. endpoint addr.

- Parameter's Compatibility: 10h

Pass-on not possible:

- Do not send notification

- Discard parameter

General action:

- Do not send notification

- Pass on message or parameter

Parameter length: 20 (14h)

- Address: 49 00 12 30 20 FF FF FF FF

FF FF FF FF FF FF FF FF FF FF FF

LC-Link Charactreristics

- Parameter's Compatibility: 00h

Pass-on not possible:

- Do not send notification

- Pass on message or parameter

General action:

- Do not send notification

- Pass on message or parameter

Parameter length: 12 (0Ch)

- Maximum forward CPS-SDU bit rate: 312 (138h)

- Maximum backwards CPS-SDU bit rate: 334 (14Eh)

- Average forward CPS-SDU bit rate: 300 (12Ch)

- Average backwards CPS-SDU bit rate: 325 (145h)

- Maximum forward CPS-SDU size: 24 (18h)

- Maximum backwards CPS-SDU size: 26 (1Ah)

- Average forward CPS-SDU size: 24 (18h)

- Average backwards CPS-SDU size: 26 (1Ah)

OSAID-Orig. sign. assoc. ident.

- Parameter's Compatibility: 00h

Pass-on not possible:

- Do not send notification

- Pass on message or parameter

General action:

- Do not send notification

- Pass on message or parameter

Parameter length: 4 (04h)

- Signalling association identifier: 45 10 1A 00

SUGR-Served user gen. reference

- Parameter's Compatibility: 00h

Pass-on not possible:

- Do not send notification

- Pass on message or parameter

General action:

- Do not send notification

- Pass on message or parameter

Parameter length: 4 (04h)

- Field: 00 00 00 03

Binding ID

QoS rate & SDU

CID

Page 30: 02 - Call Setup

30 © 2005 Nokia Call Setup / Kittipong Thamapa

Establish Confirm message

DAID-Dest. sign. assoc. ident.: 45 10 1A 00

- Message's Compatibility: 00h

Pass-on not possible:

- Do not send notification

- Pass on message or parameter

General action:

- Do not send notification

- Pass on message or parameter

OSAID-Orig. sign. assoc. ident.

- Parameter's Compatibility: 00h

Pass-on not possible:

- Do not send notification

- Pass on message or parameter

General action:

- Do not send notification

- Pass on message or parameter

Parameter length: 4 (04h)

- Signalling association identifier: 00 00 00 09

Page 31: 02 - Call Setup

31 © 2005 Nokia Call Setup / Kittipong Thamapa

Iu-CS Call Setup

Page 32: 02 - Call Setup

32 © 2005 Nokia Call Setup / Kittipong Thamapa

Overview of Setting Up Call

Mobile Terminated Call (MTC)

ServiceRequest

Radio AccessBearer

Paging

Mobile Originated Call

RRCConnectio

n

Page 33: 02 - Call Setup

33 © 2005 Nokia Call Setup / Kittipong Thamapa

Iu-CS Call Setup (CM Service Request) UE RNC MGW

RRC Connection Setup

Initial Direct Transfer

CM Service RequestRRC RRC

Initial UE Message

CM Service RequestRANAPRANAP

Initial UE Message

CM Service AcceptRANAPRANAP

BSSAP’

Initial Direct Transfer

CM Service AcceptRRC RRC

Node-B

Rel’99

Page 34: 02 - Call Setup

34 © 2005 Nokia Call Setup / Kittipong Thamapa

Iu-CS Call Setup (CM Service Request) UE RNC

RRC Connection Setup & CM Service Request

Common IDRANAPRANAP

Direct Transfer

( Call Proceeding)

RANAPRANAP

BSSAP’

Downlink Direct Transfer (Call Proceeding)RRC RRC

Common ID

Uplink Direct Transfer (Set up)RRC RRC

MGW

Direct Transfer (Setup)RANAPRANAP

BSSAP’CC: Set up

BSSAP’

CC: Call Proceedi

ng

Node-B

Security Mode Command

Page 35: 02 - Call Setup

35 © 2005 Nokia Call Setup / Kittipong Thamapa

Overview of Setting Up Call

Mobile Terminated Call (MTC)

ServiceRequest

Radio AccessBearer

Paging

Mobile Originated Call

RRCConnectio

n

Page 36: 02 - Call Setup

36 © 2005 Nokia Call Setup / Kittipong Thamapa

Iu-CS Call Setup (RAB Setup) UE Node-B RNC

RRC Connection Setup & CM Service Request & Call Setup

RAB Assignment RequestRANAPRANAP

RAB Assignment ResponseRANAPRANAP

BSSAP’

Radio Bearer SetupRRC RRC

Assignment

Request

Radio Bearer Setup completeRRC RRC

MGW

Establish Request/Confirm ALCAPALCAP

Radio Link Reconfiguration PrepareNBAPNBAP

Radio Link Reconfiguration CommitNBAPNBAP

Radio Link Reconfiguration ReadyNBAPNBAP

Establish Request/Confirm ALCAPALCAP

Page 37: 02 - Call Setup

37 © 2005 Nokia Call Setup / Kittipong Thamapa

Iu-PS Call set up

Page 38: 02 - Call Setup

38 © 2005 Nokia Call Setup / Kittipong Thamapa

Iu-CS VS Iu-PS Call Setup

RRC

ServiceReq

Security Mode Command

Attach

Page 39: 02 - Call Setup

39 © 2005 Nokia Call Setup / Kittipong Thamapa

RAB Establishment Iu-CS VS Iu-PS

For non-real time services, the radio access bearer is created without immediately reserving radio resources

RAB

Iu-CS Iu-PS

PDP Context Activation

Page 40: 02 - Call Setup

40 © 2005 Nokia Call Setup / Kittipong Thamapa

GPRS Attach

UEATTACH REQUEST ( )

(Identification Procedure)

Authentication and Ciphering Procedure

ATTACH ACCEPT ( )

e.g. new TMSIor P-TMSI

ATTACH COMPLETE ( )

3G-SGSN

Page 41: 02 - Call Setup

41 © 2005 Nokia Call Setup / Kittipong Thamapa

Initial Direct Transfer

UE RNC MSC

RRC Connection Setup

Initial Direct Transfer

CM Service RequestRRC RRC

Node-B

UE RNC SGSN Node-B

Initial Direct Transfer

Attach Request GMMRRC RRC

Initial UE Message

CM Service RequestRANAPRANAP

Initial UE Message

Attach Request GMMRANAPRANAP

RRC Connection Setup

Page 42: 02 - Call Setup

42 © 2005 Nokia Call Setup / Kittipong Thamapa

Iu-PS Attach (1/2) UE RNC

RRC Connection Setup

GMM : Identity RequestRANAPRANAP

Identity Request (GMM)RRC RRC

SGSN Node-B

Initial Direct Transfer

Attach Request GMMRRC RRC

Initial UE Message

Attach Request GMMRANAPRANAP

Identity Response (GMM)RRC RRC

RANAPRANAPGMM: Identity Response

Page 43: 02 - Call Setup

43 © 2005 Nokia Call Setup / Kittipong Thamapa

Iu-PS Attach (2/2) UE RNC

RRC Connection Setup

GMM: Authentication & Ciphering Request RANAPRANAP

GMM: Authentication & Ciphering RequestRRC RRC

SGSN Node-B

RRC RRC

RANAPRANAP

GMM: Authentication & Ciphering Response

GMM: Authentication & Ciphering Response

GMM: Attach Accept RANAPRANAP

GMM: Attach AcceptRRC RRC

RRC RRC

RANAPRANAP

GMM: Attach Complete

GMM: Attach Complete

Security Mode Command

Common ID RANAPRANAP

Page 44: 02 - Call Setup

44 © 2005 Nokia Call Setup / Kittipong Thamapa

RAB Assignment Iu-CS VS Iu-PS Iu-PS RAB-ASSIGNMENT REQUEST

RANAP-PDU

initiatingMessage

- procedureCode: 0

- criticality: reject

initiatingMessage

RAB-AssignmentRequest

protocolIEs

- id: 54

- criticality: ignore

RAB-SetupOrModifyList

- id: 53

- firstCriticality: reject

firstValue

- rAB-ID: '00000101'B

rAB-Parameters

- trafficClass: background

- rAB-AsymmetryIndicator: symmetric-bidirectional

maxBitrate

- MaxBitrate: 128000

- deliveryOrder: delivery-order-not-requested

- maxSDU-Size: 12016

sDU-Parameters

residualBitErrorRatio

- mantissa: 1

- exponent: 5

Iu-CS RAB-ASSIGNMENT REQUEST

RANAP-PDU

initiatingMessage

- procedureCode: 0

- criticality: reject

initiatingMessage

RAB-AssignmentRequest

protocolIEs

- id: 54

- criticality: ignore

RAB-SetupOrModifyList

- id: 53

- firstCriticality: reject

firstValue

- rAB-ID: '00000001'B

rAB-Parameters

- trafficClass: conversational

- rAB-AsymmetryIndicator: symmetric-bidirectional

maxBitrate

- MaxBitrate: 12200

guaranteedBitRate

- GuaranteedBitrate: 4750

- deliveryOrder: delivery-order-requested

- maxSDU-Size: 244

sDU-Parameters

sDU-ErrorRatio

- mantissa: 7

- exponent: 3

Bit rate

Page 45: 02 - Call Setup

45 © 2005 Nokia Call Setup / Kittipong Thamapa

RAB Assignment Iu-CS VS Iu-PS Iu-PS residualBitErrorRatio

- mantissa: 1

- exponent: 5

- deliveryOfErroneousSDU: no-error-detection-consideration

allocationOrRetentionPriority

- priorityLevel: 2

- pre-emptionCapability: shall-not-trigger-pre-emption

- pre-emptionVulnerability: pre-emptable

- queuingAllowed: queueing-not-allowed

- relocationRequirement: none

Iu-CS residualBitErrorRatio

- mantissa: 1

- exponent: 6

- deliveryOfErroneousSDU: yes

sDU-FormatInformationParameters

- subflowSDU-Size: 81

: :

residualBitErrorRatio

- mantissa: 1

- exponent: 3

- deliveryOfErroneousSDU: no-error-detection-consideration

sDU-FormatInformationParameters

- subflowSDU-Size: 103

: :

residualBitErrorRatio

- mantissa: 5

- exponent: 3

- deliveryOfErroneousSDU: no-error-detection-consideration

sDU-FormatInformationParameters

- subflowSDU-Size: 60

: :

- transferDelay: 80

- sourceStatisticsDescriptor: speech

Page 46: 02 - Call Setup

46 © 2005 Nokia Call Setup / Kittipong Thamapa

RAB Assignment Iu-CS VS Iu-PS

Iu-PS userPlaneInformation

- userPlaneMode: transparent-mode

- uP-ModeVersions: '0000000000000001'B

transportLayerInformation

- transportLayerAddress: '00001010001110100001010100000101'B

iuTransportAssociation

- gTP-TEI: '3C000000'H

- service-Handover: handover-to-GSM-should-not-be-performed

- secondCriticality: ignore

secondValue

pDP-TypeInformation

- PDP-Type: ipv4

- PDP-Type: ipv4

- dataVolumeReportingIndication: do-not-report

Iu-CS

userPlaneInformation

- userPlaneMode: support-mode-for-predefined-SDU-sizes

- uP-ModeVersions: '0000000000000001'B

transportLayerInformation

- transportLayerAddress:

'0100010100000000000000000000000000000000000001100100001000010 110001011110000000000000000000000000000000000000000000000000

000000000000000000000000000000000000000'B

iuTransportAssociation

- bindingID: '01025550'H

- secondCriticality: ignore

secondValue

Page 47: 02 - Call Setup

47 © 2005 Nokia Call Setup / Kittipong Thamapa

Radio Bearer Setup

UE Initiated PDP Context Activation

UE

3G-SGSN

GGSNACTIVATE PDP CONTEXT REQUEST ( )

ACTIVATE PDP CONTEXT ACCEPT ( )

CREATE PDP CONTEXT REQUEST

CREATE PDP CONTEXT RESPONSE

UPDATE PDP CONTEXT REQUEST

UPDATE PDP CONTEXT RESPONSE

Page 48: 02 - Call Setup

48 © 2005 Nokia Call Setup / Kittipong Thamapa

PDP Context Activation

Protocol discriminator

Requested QoS

Requested LLC SAPI

Transaction indicator

Activate PDP contextrequest message ID

Requested PDP address

Access Point Name OP

Requested NSAPI

Protocol configurationoptions OP

1010: GPRS session management messages

01000001: Activate PDP context request

• Delay class• Reliability class• Precedence class• Mean and peak

throughput class• Maximum UL/DL bit rate• Transfer delay• Guaranteed UL/DL bit

rate• Residual BER• Delivery order• etc.

UE 3G-SGSN

ACTIVATE PDP CONTEXT REQUEST ( )

Page 49: 02 - Call Setup

49 © 2005 Nokia Call Setup / Kittipong Thamapa

PDP Context Activation

Protocol discriminator

Negotiated QoS

Negotiated LLC SAPI

Transaction indicator

Activate PDP contextrequest message ID

PDP address

Packet Flow Identifier

OPProtocol configuration

options

OP

Radio priority

Spare half octet

OP

1010: GPRS session management messages

01000010: Activate PDP context accept

Not required in UMTS, but transmitted tosupport UMTS – GPRS cell reselection

UE 3G-SGSN

ACTIVATE PDP CONTEXT ACCEPT ( )

Page 50: 02 - Call Setup

50 © 2005 Nokia Call Setup / Kittipong Thamapa

Encryption off and Encryption on

Page 51: 02 - Call Setup

51 © 2005 Nokia Call Setup / Kittipong Thamapa

Encryption off Encryption on

User Data can not be decoded

Page 52: 02 - Call Setup

52 © 2005 Nokia Call Setup / Kittipong Thamapa

Encryption off Encryption on

Page 53: 02 - Call Setup

53 © 2005 Nokia Call Setup / Kittipong Thamapa

Link of Signalling Messages

Page 54: 02 - Call Setup

54 © 2005 Nokia Call Setup / Kittipong Thamapa

UE Node-B RNC CN

RRC Connection Setup Request

Radio Link Setup Request NBAPNBAP

Radio Link Setup Response

NBAPNBAP

RRC RRC

IMSIRNTI

RNC Communication Context ID

Node B Communication Context ID

RNC Communication Context ID

Transport Layer Address

Binding ID

Page 55: 02 - Call Setup

55 © 2005 Nokia Call Setup / Kittipong Thamapa

UE Node-B RNC CN

RRC Connection Setup Complete

RRC Connection Setup

Establish Request (ERQ)ALCAPALCAP

Establish Response (ECF)ALCAPALCAP

RRCRRC

RRC RRC

Transport Layer Address

Channel Identifier (CID)

OSAID Orig sign assoc idnet.

OSAID Orig sign assoc idnet.

DAID Dest sign assoc idnet.

IMSI

Data send on CID that allocate on ERQ

Page 56: 02 - Call Setup

56 © 2005 Nokia Call Setup / Kittipong Thamapa

HSDPA Call set up

Page 57: 02 - Call Setup

57 © 2005 Nokia Call Setup / Kittipong Thamapa

Physical Channels for One HSDPA UE

• Associated DPCH, Dedicated Physical Channel

• DPCH needed for each HSDPA UE.

• Signalling, uplink data.

• HS-PDSCH: High-Speed Physical Downlink Shared Channel

• Actual HSDPA data of HS-DSCH transport channel.

• 1-15 code channels.

• QPSK or 16QAM modulation.

• HS-SCCH: High-Speed Shared Control Channel

• Informs UE how to receive HS-PDSCH in the same TTI.

• HS-DPCCH: High-Speed Dedicated Physical Control Channel

• MAC-hs Ack/Nack information.

• Channel Quality Information.

UE

BTS

Ass

oci

ate

d

DPC

HA

ssoci

ate

d

DPC

H1-1

5 x

HS-

PD

SC

H

1-4

x H

S-S

CC

H

HS

-DPC

CH

Page 58: 02 - Call Setup

58 © 2005 Nokia Call Setup / Kittipong Thamapa

Transport to Phys. CH mapping Transport Channels

DCH

RACH

BCH

FACH

PCH

Physical Channels

Dedicated Physical Data Channel (DPDCH)

Dedicated Physical Control Channel (DPCCH)

Physical Random Access Channel (PRACH)

Common Pilot Channel (CPICH)

Primary Common Control Physical Channel (P - CCPCH)

Secondary Common Control Physical Channel (S - CCPCH)

Synchronisation Channel (SCH)

Acquisition Indicat or Channel (AICH)

Paging Indicator Channel (PICH)

HS-DSCH-related Shared Control Channel (HS-SCCH)

HS-DSCH High Speed Physical Downlink Shared Channel (HS-PDSCH)

Dedicated Physical Control Channel (uplink) for HS-DSCH (HS-DPCCH)

Page 59: 02 - Call Setup

59 © 2005 Nokia Call Setup / Kittipong Thamapa

HSDPA Layer 1 channels

Page 60: 02 - Call Setup

60 © 2005 Nokia Call Setup / Kittipong Thamapa

Dedicated Uplink Physical Channel ( Layer 1 )

• 5.2.1 Dedicated uplink physical channels

• There are three types of uplink dedicated physical channels, the uplink Dedicated Physical Data Channel (uplink DPDCH), the uplink Dedicated Physical Control Channel (uplink DPCCH ), and the uplink Dedicated Control Channel associated with HS-DSCH transmission (uplink HS-DPCCH ).

• The DPDCH, the DPCCH and the HS-DPCCH are I/Q code multiplexed.

• The uplink DPDCH is used to carry the DCH transport channel.

• The uplink DPCCH is used to carry control information generated at Layer 1. The Layer 1 control information consists of known pilot bits, transmit power-control (TPC) commands, feedback information (FBI), and transport-format combination indicator (TFCI).

Page 61: 02 - Call Setup

61 © 2005 Nokia Call Setup / Kittipong Thamapa

Uplink Physical Layer

I

j

cd,1

d

Sdpch,n

I+jQ

DPDCH1

Q

cd,3

d

DPDCH3

cd,5

d

DPDCH5

cd,2

d

DPDCH2

cd,4

d

cc

c

DPCCH

S

chs

HS-DPCCH (If Nmax-dpdch mod 2 = 1)

DPDCH4

chs

HS-DPCCH (If Nmax-dpdch mod 2 = 0)

hs

hs

cd,6

d

DPDCH6

Spreading for uplink DPCCH, DPDCHs and HS-DPCCH

Pilot Npilot bits

TPC NTPC bits

DataNdata bits

Slot #0 Slot #1 Slot #i Slot #14

Tslot = 2560 chips, 10 bits

1 radio frame: Tf = 10 ms

DPDCH

DPCCHFBI

NFBI bitsTFCI

NTFCI bits

Tslot = 2560 chips, Ndata = 10*2k bits (k=0..6)

Figure 1: Frame structure for uplink DPCCH

Subframe #0 Subframe # i Subframe #4

HARQ-ACK CQI

One radio frame T f = 10 ms

One HS-DPCCH subframe (2 ms)

2 T slot = 5120 chips T slot = 2560 chips

Figure 2A: Frame structure for uplink HS-DPCCH

Page 62: 02 - Call Setup

62 © 2005 Nokia Call Setup / Kittipong Thamapa

Transport /Physical Channels mapping (UL example)

Transport Block

Transport Block

TFI

TrCH x

Transport Block

Transport Block

TFI

TrCH y

TFCI Coding & Multiplexing

Physical Data Channel

Physical Control Channel

TB & Error Indication

TB & Error Indication

TFI TB & Error Indication

TB & Error Indication

TFI

TFCIdecoding

DeCoding & De-Multiplexing

Physical Data Channel

Physical Control Channel

Higher Layers UTRAN:MAC / FP

Physical Layer BTS L1

DPCCH DPDCH DPCCH DPDCH

Ue Side BS Side

Page 63: 02 - Call Setup

63 © 2005 Nokia Call Setup / Kittipong Thamapa

Downlink Physical Layer

• 5.3.2 Dedicated downlink physical channels

• There is only one type of downlink dedicated physical channel, the Downlink Dedicated Physical Channel (downlink DPCH).

• Within one downlink DPCH, dedicated data generated at Layer 2 and above, i.e. the dedicated transport channel (DCH), is transmitted in time-multiplex with control information generated at Layer 1 (known pilot bits, TPC commands, and an optional TFCI). The downlink DPCH can thus be seen as a time multiplex of a downlink DPDCH and a downlink DPCCH.

Page 64: 02 - Call Setup

64 © 2005 Nokia Call Setup / Kittipong Thamapa

Downlink Physical Channel

Different downlink Physical channels (point S in Figures 8)

G1

G2

GP

GS

S-SCH

P-SCH

(point T in Figure 11)

Figure 9: Combining of downlink physical channels

One radio frame, Tf = 10 ms

TPC NTPC bits

Slot #0 Slot #1 Slot #i Slot #14

Tslot = 2560 chips, 10*2k bits (k=0..7)

Data2Ndata2 bits

DPDCH

TFCI NTFCI bits

Pilot Npilot bits

Data1Ndata1 bits

DPDCH DPCCH DPCCH

Figure 9: Frame structure for downlink DPCH

Page 65: 02 - Call Setup

65 © 2005 Nokia Call Setup / Kittipong Thamapa

HS-SCCH

MAC Architecture

Handles high speed channels

Handles dedicated channels

HS-DSCH HS-DSCH

Associated Uplink Signalling

Associated Downlink Signalling

FACH RACH

DCCH DTCH DTCH

DSCH TDD only

MAC Control

Iur or local

MAC Control

DCH DCH

MAC-d

USCH TDD only

MAC-c/sh

CCCH CTCH BCCH SHCCH TDD only

PCCH

FACH PCH USCH TDD only

DSCH TDD only

Iub

MAC Control

MAC-hs

Configuration without MAC-c/sh

Configuration with MAC-c/sh

Configuration with MAC-c/sh

Handles common channels

HS-DPCCH

DPCH ( UL+DL rrc messages (DCCH) )

DPCH ( UL RLC+TCP-IP ack (DTCH) )

DPCH UL SF 16DPCH DL SF 256

Physical Layer

HS-DCCH UL SF 256HS-SCCH DL SF 128

BS RNC RNC

HS-PDSCH

HS-PDSCH DL

n° codes x SF 16

Page 66: 02 - Call Setup

66 © 2005 Nokia Call Setup / Kittipong Thamapa

HSDPA Protocol Architecture

• New MAC entity, MAC-hs (high-speed) added to the Node B

• Layers above, such as RLC, unchanged.

WCDMA L1

UE

Iub/Iur

SRNCNode B

Uu

MACRLC

NAS

HSDPA user plane

WCDMA L1

MAC-hs

TRANSPORT

FRAMEPROTOCOL

TRANSPORT

FRAMEPROTOCOL

MAC-dRLC

Iu

Page 67: 02 - Call Setup

67 © 2005 Nokia Call Setup / Kittipong Thamapa

Node B enhancements for HSDPATerminalsNode BRNC

PacketsScheduler

& Buffer

HARQ &

Coding

ACK/NACK & Feedback Decoding

Flow Control

R99 responsibilities:

• Physical layer operations

• No dymanic decision making

New Node B functions for HSDPA:• Sophisticated Scheduler:

•In order Delivery within priority queue

•Data Buffer management

•OVSF (orthogonal Variable Spread. Fact.) code management

•Packet scheduling

•Data Transfer on HS-DSCH

• Physical layer operations

•HARQ Retransmissions Handling

•Modulation selection

•Link adaptation

• Flow Control towards SRNC

Page 68: 02 - Call Setup

68 © 2005 Nokia Call Setup / Kittipong Thamapa

HS-DSCH code management

PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST [FDD]

NBAP-PDU

- messageDiscriminator: common

PhysicalSharedChannelReconfigurationRequestFDD

C-ID: 3

MaximumTransmissionPower: 378

HS-PDSCH-FDD-Code-Information

- extension flag: 0

- preamble: 10

- number-of-HS-PDSCH-codes: 5

- hS-PDSCH-Start-code-number: 11

PHYSICAL SHARED CHANNEL RECONFIGURATION REQUEST is sent by the RNC during the restart of the BS. It defines the Max power and Max number of codes SF 16 available for the HS-DSCH channel.

MAC hs is responsible for HS-PDSCH management. Codes selection is a dynamic procedure based on Ue – BS link quality.

RNC BS

at restart phase

Page 69: 02 - Call Setup

69 © 2005 Nokia Call Setup / Kittipong Thamapa

Retransmissions in HSDPA

Server RNC Node-B

UE

RLC retransmissions

TCP retransmissions

MAC-hs retransmissions

Page 70: 02 - Call Setup

70 © 2005 Nokia Call Setup / Kittipong Thamapa

Iub Flow Control messages ( 1/2 )

5.9 HS-DSCH Capacity Request

Node B CRNC

CAPACITY REQUEST

Figure 12B: HS-DSCH Capacity Request procedure

The HS-DSCH Capacity Request procedure provides means for the RNC to request HS-DSCH capacity to the BS , by indicating the user buffer size in the RNC for a given priority level (CmCH-PI).

The RNC is allowed to reissue the HS-DSCH Capacity Request if from the BS no CAPACITY ALLOCATION has been received within an appropriate time threshold.

Page 71: 02 - Call Setup

71 © 2005 Nokia Call Setup / Kittipong Thamapa

Iub Flow Control messages ( 2/2 )

5.10 HS-DSCH Capacity Allocation

D O C U M E N T T Y P E

T y p e U n i t O r D e p a r t m e n t H e r eT y p e Y o u r N a m e H e r e T y p e D a t e H e r e

N o d e B C R N C

C A P A C I T Y A L L O C A T I O N

HS-DSCH Capacity Allocation is generated either in response to a HS-DSCH Capacity Request or at any other time.

The flow control is mainly controlled by the Node-B sending capacity allocation messages. The Node-B does know the status of the buffers in the RNC by the capacity request and by every further data frame . So the Node B may use this message to modify the traffic flow at any time by indicating its capacity to deliver PDU.

Page 72: 02 - Call Setup

72 © 2005 Nokia Call Setup / Kittipong Thamapa

UE RRC status

Idlemode

Connected ModeCell DCH

URA PCH

Cell PCH

Cell FACH

These are the possible status for a UE in a UMTS network

IDLE MODE: “Stand by” mode. The UE is able to listen to BCH channel through the PCCPCH in order to receive the System Information. No RRC is available for the UE.

CELL DCH: one of the ”Connected Mode”. The UE is able to send and receive RRC messages DPDCH.

From Cell DCH for inactivity timer the UE can move to Cell FACH . Here it is able to use the DCCH and DTCH through the SCCPCH. This status allow the UE to save battery and resources. The UE can maintain low bit rate connection with the HTTP server.

From Cell FACH for inactivity timer the UE can move to Cell PCH. This status allow the UE to save battery. In fact here the UE listen to the PCH only.

URA PCH status is optional. It can be adopted in case is necessary to decrease the number of cell update performed by the UE when it move from one to another cell.

Page 73: 02 - Call Setup

73 © 2005 Nokia Call Setup / Kittipong Thamapa

HSDPA service

bit rate

time

option 1:

active set>1DCH

HSDPA

IDLE MODE

HS-DSCH Service Area

UE request PS connection after GPRS attach.Active set=1 allocate HS-DSCH

Page 74: 02 - Call Setup

74 © 2005 Nokia Call Setup / Kittipong Thamapa

Serving HS-DSCH Cell Change

HS-SCCH

HS-PDSCH

DPCH

DPCHServing HS-DSCH cell

Soft/softer handover is not supportedfor HS-SCCH/HS-PDSCH.

HS-DPCCH

UEs in SHO area are not allowed to get HSDPA traffic.

The UE having already HSDPA channel allocated that get in a SHO area , is allowed to change HS-DSCH cell only through the RT DCH.

HSDPA traffic can be started again only after the download traffic is completely stopped.

Page 75: 02 - Call Setup

75 © 2005 Nokia Call Setup / Kittipong Thamapa

HSDPA Mobility Handling with DCH Switching: RAN230

1/3

SHO RegionHS-DSCH Service Area

HS-DSCH Service Area

Data scheduled toUE. Active set=1 usercan be allocatedHS-DSCH. Active set>1implement mobility procedure and HO toDCH 0/0

Scheduled datacontinues todownload usingDCH X/Y. Scheduleddata ends DCHdropped. Newtraffic requestActive set=1 allocate HS-DSCH

UE is allocated DCH 0/0. A traffic request isreceived and DCHX/Y isallocated to supportdata transfer

time

bit rate bit rate

time

handover

option 1:

active set=1

handover

option 2:

active set>1

HSDPADCH

CELL

FACH

HSDPADCH

HSDPA

CELL

PCH

CELL

FACH

CELL

PCH

CELL

FACH

CELL

FACH

Page 76: 02 - Call Setup

76 © 2005 Nokia Call Setup / Kittipong Thamapa

SHO RegionHS-DSCH Service Area

HS-DSCH Service Area

Data scheduled toUE. Active set=1 canbe allocated HS-DSCH.Active set>1implement mobility procedure and HO toDCH 0/0

Allocate HS-DSCH

Cell_DCH 0/0

Traffic_request

Cell_DCH X/Y

low/no data rate

Cell_FACH/PCH

Traffic_request

Active Set =1

HSDPA Mobility Handling with DCH Switching: RAN230

2/3

Page 77: 02 - Call Setup

77 © 2005 Nokia Call Setup / Kittipong Thamapa

HSDPA Mobility Handling with DCH Switching: RAN230

• Separate parameters sets for HSDPA UE is implemented by including a HSDPA specific identifier in the WCEL parameters

• The following object classes can be defined for each cell

• Intra Frequency Measurement Control – FMCS

• Inter Frequency Measurement Control – FMCI

• Inter System Measurement Control – FMCG

• Intra Frequency Handover Path – HOPS

• Fallbacks from the HS-DSCH to the DCH can be followed up through counters

• CR727 when implemented will allow DCH to HSDPA switching without having to go to Cell_FACH state first.

3/3

Page 78: 02 - Call Setup

78 © 2005 Nokia Call Setup / Kittipong Thamapa

IDLE Mode – Cell DCH transaction UE RNC

IDLE MODE

SGSN Node-B

RRC Connection Request ( RACH )RRC RRC

RRC Connection Set Up ( FACH ) RRC RRC

RRC Connection Set Up Complete ( DCH ) RRC RRC

Radio Link Setup Response (C-NBAP )

NBAPNBAP

Radio Link Setup Request (C-NBAP ) NBAPNBAP

Establish Request (ALCAP)

ALCAPALCAP

Establish Confirm (ALCAP)

ALCAPALCAP

Cell DCH status

Page 79: 02 - Call Setup

79 © 2005 Nokia Call Setup / Kittipong Thamapa

Cell DCH – HS-DSCH transaction (1/2) UE RNC SGSN Node-B

RRC Direct Transfer: PDP context request RRC RRC

Radio Bearer Set UpRRC RRC

Radio Bearer Set Up CompleteRRC RRC

RANAP RANAP

PDP context request

RANAP RANAP

PDP context accept RRC Direct Transfer: PDP context accept RRC RRC

RRC RRCMeasurement Control

RRC RRCMeasurement Report

RRC Direct Transfer: Attach request RRC RRC RANAP RANAP

Attach request

RANAP RANAP

Attach accept RRC Direct Transfer: Attach accept RRC RRC

Authentic. &

Ciphering

RANAP RANAP

RAB assign. request

RANAP RANAP

RAB assign. response

Page 80: 02 - Call Setup

80 © 2005 Nokia Call Setup / Kittipong Thamapa

Cell DCH – HS-DSCH transaction (2/2) UE RNC SGSN Node-B

Radio Link Reconfiguration Ready

NBAPNBAP

Radio Link Reconfiguration Prepare NBAPNBAP

Establish RequestALCAPALCAP

Establish ConfirmALCAPALCAP

Radio Bearer Reconfiguration RRC RRC

RRC RRCRadio Bearer Reconfiguration Complete

Establish RequestALCAPALCAP

Establish ConfirmALCAPALCAP

NBAPNBAP Radio Reconfiguration Commit

HSDPA Traffic

Page 81: 02 - Call Setup

81 © 2005 Nokia Call Setup / Kittipong Thamapa

HS-DSCH – Cell PCH transaction (1/3) UE RNC SGSN Node-B

Release RequestALCAPALCAP

Release ConfirmALCAPALCAP

Radio Bearer Reconfiguration RRC RRC

RRC RRCRadio Bearer Reconfiguration Complete

Status change for inactivity timer

Cell FACH status

Radio Link Deletion Response

NBAPNBAP

Radio Link Deletion RequestNBAPNBAP

Page 82: 02 - Call Setup

82 © 2005 Nokia Call Setup / Kittipong Thamapa

HS-DSCH – Cell PCH transaction (1/3) UE RNC SGSN Node-B

Release RequestALCAPALCAP

Release ConfirmALCAPALCAP

Release RequestALCAPALCAP

Release ConfirmALCAPALCAP

Physical Channel Reconfiguration ( FACH )RRC RRC

RRC RRCPhysical Channel Reconfiguration Complete ( RACH )

Cell PCH status

Page 83: 02 - Call Setup

83 © 2005 Nokia Call Setup / Kittipong Thamapa

Cell PCH – HS-DSCH transaction (1/3) UE RNC

Cell PCH status

Cell Update confirmRRC RRC

SGSN Node-B

Cell UpdateRRC RRC

UTRAN mobility information confirmRRC RRC

Measurement ReportRRC RRC

Radio Link Setup Request NBAPNBAP

Radio Link Setup Response

NBAPNBAP

Cell FACH status

Page 84: 02 - Call Setup

84 © 2005 Nokia Call Setup / Kittipong Thamapa

Cell PCH – HS-DSCH transaction (2/3) UE RNC SGSN Node-B

Establish ConfirmALCAPALCAP

Establish ConfirmALCAPALCAP

Establish ConfirmALCAPALCAP

Establish ConfirmALCAPALCAP

Establish RequestALCAPALCAP

Establish ConfirmALCAPALCAP

RRC Transport Channel

establishment

DPCH Transport Channel

establishment

HS-DSCH Transport Channel

establishment

Page 85: 02 - Call Setup

85 © 2005 Nokia Call Setup / Kittipong Thamapa

Cell PCH – HS-DSCH transaction (3/3) UE RNC

RRC RRC

SGSN Node-B

Radio Bearer ReconfigurationRRC RRC

Measurement ControlRRC RRC

Capacity AllocationHS-DSCHHS-DSCH

Radio Bearer Reconfiguration complete

HS-DSCHHS-DSCHCapacity Request

Cell DCH status

Page 86: 02 - Call Setup

86 © 2005 Nokia Call Setup / Kittipong Thamapa

CELL Update UE Node-B RNC CN

Cell Update (RACH)RRC RRC

SRNC

Admission Control

Select Transport Channel

RNTI

Measurement IEs

RNTI

Cell Update cause

Measurement Quantity

In dB CPICH_Ec/No

causes options:cell reselection,

periodical cell update, uplink data

transmission, paging response,

re-entered service area, radio link failure,

RLC unrecoverable error)

Cell Update confirm (FACH)RRC RRC

RRC state indicator

RLC re-establish indicatorRLC re-establish indicator

options:CELL_DCH, CELL_FACH, CELL_PCH, URA_PCH)

UE

RLC buffer Checking

Page 87: 02 - Call Setup

87 © 2005 Nokia Call Setup / Kittipong Thamapa

Cell Update MessageCELL UPDATE

UL-CCCH-Message

integrityCheckInfo

messageAuthenticationCode: '01011101001110001111100011101001'B

rrc-MessageSequenceNumber: 2

message

cellUpdate

u-RNTI

srnc-Identity: '000100110010'B

s-RNTI: '00000000010011010100'B

startList

STARTSingle

cn-DomainIdentity: cs-domain

start-Value: '00000000000000000010'B

STARTSingle

cn-DomainIdentity: ps-domain

start-Value: '00000000000000001000'B

am-RLC-ErrorIndicationRb2-3or4: FALSE

am-RLC-ErrorIndicationRb5orAbove: FALSE

cellUpdateCause: uplinkDataTransmission

rb-timer-indicator

t314-expired: TRUE

t315-expired: FALSE

measuredResultsOnRACH

currentCell

modeSpecificInfo

fdd

measurementQuantity

cpich-Ec-N0: 45

Page 88: 02 - Call Setup

88 © 2005 Nokia Call Setup / Kittipong Thamapa

Cell Update Confirm MessageCELL UPDATE CONFIRM [DCCH]

DL-DCCH-Message

integrityCheckInfo

messageAuthenticationCode: '11110111010101011110100011101101'B

rrc-MessageSequenceNumber: 2

message

cellUpdateConfirm

later-than-r3

rrc-TransactionIdentifier: 2

criticalExtensions

criticalExtensions

r5

cellUpdateConfirm-r5

new-C-RNTI: '0000000000000001'B

rrc-StateIndicator: cell-FACH

rlc-Re-establishIndicatorRb2-3or4: FALSE

rlc-Re-establishIndicatorRb5orAbove: FALSE

modeSpecificTransChInfo

fdd

modeSpecificPhysChInfo

fdd

Page 89: 02 - Call Setup

89 © 2005 Nokia Call Setup / Kittipong Thamapa

DCH Allocation UE Node-B RNC CN

Measurement Report (RACH)RRC RRC

SRNC

Admission Control

Collects Radio Ch

Parameters

Select Transport Ch IDs

In dB CPICH_Ec/No event: e4a

DPCH UL Scram. & Chan. code

Transport Ch DCH IDs

Measured Result

Measured Result on RACH

Traffic VolumeMeasured Result List

Event Result

Measurement Quantity

Radio Bearer Identity num.RLC Buffer Payload

Traffic VolumeEvent Identity

C-NBAPC-NBAPRadio Link Set up Request

Radio link ID & Cell ID

DPCH Power ctrl info

HS-DSCH MAC flow ctrl info

C-NBAPC-NBAPRadio Link Set up Response

Transport Layer Address

Binding ID

Transport Ch DCH IDs

Node-B

Radio Ch set up

AAL2 TP Selection

SRNC

Dig Analysis Route finding

ATM CAC

Path id & CID selection

Page 90: 02 - Call Setup

90 © 2005 Nokia Call Setup / Kittipong Thamapa

Measurement Report Message

MEASUREMENT REPORT

UL-DCCH-Message

integrityCheckInfo

messageAuthenticationCode: '11001011100111101...

rrc-MessageSequenceNumber: 6

message

measurementReport

measurementIdentity: 4

measuredResults

trafficVolumeMeasuredResultsList

TrafficVolumeMeasuredResults

rb-Identity: 1

rlc-BuffersPayload: pl0

TrafficVolumeMeasuredResults

rb-Identity: 2

rlc-BuffersPayload: pl0

TrafficVolumeMeasuredResults

rb-Identity: 3

rlc-BuffersPayload: pl0

TrafficVolumeMeasuredResults

rb-Identity: 4

rlc-BuffersPayload: pl0

TrafficVolumeMeasuredResults

rb-Identity: 5

rlc-BuffersPayload: pl512

measuredResultsOnRACH

currentCell

modeSpecificInfo

fdd

measurementQuantity

cpich-Ec-N0: 44

eventResults

trafficVolumeEventResults

ul-transportChannelCausingEvent

rachorcpch: NULL

trafficVolumeEventIdentity: e4a

Page 91: 02 - Call Setup

91 © 2005 Nokia Call Setup / Kittipong Thamapa

Radio Link Set up Request MessageRADIO LINK SETUP REQUEST [FDD]

NBAP-PDU

------

-messageDiscriminator: common

------

RadioLinkSetupRequestFDD

------

CRNC-CommunicationContextID: 1236

------

UL-DPCH-Information-RL-SetupRqstFDD

ul-ScramblingCode

- uL-ScramblingCodeNumber: 1000212

------

- minUL-ChannelisationCodeLength: v16

------

DL-DPCH-Information-RL-SetupRqstFDD

DCH-FDD-Information

DCH-FDD-InformationItem

- dCH-ID: 24

ul-TransportFormatSet

- nrOfTransportBlocks: 0

------

- nrOfTransportBlocks: 1

- transportBlockSize: 148

------

- transmissionTimeInterval: msec-40

------

dl-TransportFormatSet

------

- nrOfTransportBlocks: 1

- transportBlockSize: 148

mode

------

- transmissionTimeInterval: msec-40

------

DCH-FDD-InformationItem

------

- dCH-ID: 1

ul-TransportFormatSet

------

- nrOfTransportBlocks: 1

- transportBlockSize: 336

------

- nrOfTransportBlocks: 2

- transportBlockSize: 336

------

- nrOfTransportBlocks: 3

- transportBlockSize: 336

------

- nrOfTransportBlocks: 4

- transportBlockSize: 336

------

- transmissionTimeInterval: msec-20

------

dl-TransportFormatSet

dynamicParts

- nrOfTransportBlocks: 0

------

- transmissionTimeInterval: msec-10

------

RL-InformationList-RL-SetupRqstFDD

------

- rL-ID: 1

- c-ID: 3

------

- dl-ScramblingCode: 0

- fdd-DL-ChannelisationCodeNumber: 10

- initialDL-transmissionPower: -180

- maximumDL-power: -71

- minimumDL-power: -180

------

hSDSCH-MACdFlows-Information

------

Page 92: 02 - Call Setup

92 © 2005 Nokia Call Setup / Kittipong Thamapa

Radio Link Set up Response

RADIO LINK SETUP RESPONSE [FDD]

NBAP-PDU

------

- messageDiscriminator: common

------

RadioLinkSetupResponseFDD

------

CRNC-CommunicationContextID: 1236

------

NodeB-CommunicationContextID: 160001

------

RL-InformationResponseItem-RL-SetupRspFDD

------

- rL-ID: 1

- contents (in bits): 00001

- rL-Set-ID: 1

- contents (in bits): 00001

- received-total-wide-band-power: 69

------

dCH-InformationResponse

------

- dCH-ID: 24

------

- bindingID: '00000009'H

------

49 00 00 10 20 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

------

- dCH-ID: 1

- bindingID: '00000004'H

------

49 00 00 10 20 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

------

hsDSCH-MACdFlow-Specific-InformationResp

------

- hsDSCHMacdFlow-Id: 0

-------

- bindingID: '00000006'H

------

49 00 00 10 20 FF FF FF FF FF FF FF FF FF FF FF FF FF FF

------

hsSCCH-Specific-Information-ResponseFDD

------

HSSCCH-Codes

------

- codeNumber: 4

------

Page 93: 02 - Call Setup

93 © 2005 Nokia Call Setup / Kittipong Thamapa

Establish Request ( 3 times ) UE Node-B RNC CN

e.g.

Establish RequestALCAPALCAP

Establish ConfirmALCAPALCAP

DAID-Dest. sig. assoc. identifier.

CEID-Connection element identifier

NSEA Dest NSAP service end point add.

CPS-SDU bit rate/size

OSAID-Origin. Sig. Assoc. identifier

SUGR-Served user gen. reference

Signalling association id that will generated in the BS .In the establish request is always 0.Connection element identifier contains PATH id & CID number selected by the RNC.AAL2 TP in the WAM of the BSParameter that define the Max. and Average bit rate/size of the CPS in forward & backwardsSignalling association id that will generated in the RNC .

The field of SUGR reports the binding ID generated in the BS and forwarded to the RNC through the Radio link set up Response .

DAID-Dest. sig. assoc. identifier.

OSAID-Origin. Sig. Assoc. identifier

Signalling association identifier generated in the BSSignalling association id that will generated in the RNC .

RNC & BS

Transport resources ready

to be used

RNC

Collects parameters to

configure the UE

Page 94: 02 - Call Setup

94 © 2005 Nokia Call Setup / Kittipong Thamapa

Establish Request MessageERQ - ESTABLISH REQUEST

DAID-Dest. sign. assoc. ident.: 00000000

- Message's Compatibility: 00h

Pass-on not possible:

- Do not send notification

- Pass on message or parameter

General action:

- Do not send notification

- Pass on message or parameter

CEID-Connection element ident.

- Parameter's Compatibility: 00h

Pass-on not possible:

- Do not send notification

- Pass on message or parameter

General action:

- Do not send notification

- Pass on message or parameter

Parameter length: 5 (05h)

- Path identifier: 1021 (3FDh)

- Channel identifier: 20 (14h)

NSEA-Dest. NSAP serv. endpoint addr.

-Parameter's Compatibility: 10h

Pass-on not possible:

- Do not send notification

- Discard parameter

General action:

- Do not send notification

- Pass on message or parameter

Parameter length: 20 (14h)

- Address: 4900001020....FFF

LC-Link Charactreristics

- Parameter's Compatibility: 00h

Pass-on not possible:

- Do not send notification

- Pass on message or parameter

General action:

- Do not send notification

- Pass on message or parameter

Parameter length: 12 (0Ch)

- Maximum forward CPS-SDU bit rate: 82 (52h)

- Maximum backwards CPS-SDU bit rate: 84 (54h)

- Average forward CPS-SDU bit rate: 23 (17h)

- Average backwards CPS-SDU bit rate: 25 (19h)

- Maximum forward CPS-SDU size: 24 (18h)

- Maximum backwards CPS-SDU size: 26 (1Ah)

- Average forward CPS-SDU size: 24 (18h)

- Average backwards CPS-SDU size: 26 (1Ah)

OSAID-Orig. sign. assoc. ident.

- Parameter's Compatibility: 00h

Pass-on not possible:

- Do not send notification

- Pass on message or parameter

General action:

- Do not send notification

- Pass on message or parameter

Parameter length: 4 (04h)

- Signalling association identifier: 44F29000

SUGR-Served user gen. reference

- Parameter's Compatibility: 00h

Pass-on not possible:

- Do not send notification

- Pass on message or parameter

General action:

- Do not send notification

- Pass on message or parameter

Parameter length: 4 (04h)

- Field: 00000009

Page 95: 02 - Call Setup

95 © 2005 Nokia Call Setup / Kittipong Thamapa

Establish Confirm Message

ECF - ESTABLISH CONFIRM

DAID-Dest. sign. assoc. ident.: 44F29000

- Message's Compatibility: 00h

Pass-on not possible:

- Do not send notification

- Pass on message or parameter

General action:

- Do not send notification

- Pass on message or parameter

OSAID-Orig. sign. assoc. ident.

- Parameter's Compatibility: 00h

Pass-on not possible:

- Do not send notification

- Pass on message or parameter

General action:

- Do not send notification

- Pass on message or parameter

Parameter length: 4 (04h)

- Signalling association identifier: 0000000E

Page 96: 02 - Call Setup

96 © 2005 Nokia Call Setup / Kittipong Thamapa

Establish Request MessageERQ - ESTABLISH REQUEST

DAID-Dest. sign. assoc. ident.: 00000000

- Message's Compatibility: 00h

Pass-on not possible:

- Do not send notification

- Pass on message or parameter

General action:

- Do not send notification

- Pass on message or parameter

CEID-Connection element ident.

- Parameter's Compatibility: 00h

Pass-on not possible:

- Do not send notification

- Pass on message or parameter

General action:

- Do not send notification

- Pass on message or parameter

Parameter length: 5 (05h)

- Path identifier: 1021 (3FDh)

- Channel identifier: 21 (15h)

NSEA-Dest. NSAP serv. endpoint addr.

-Parameter's Compatibility: 10h

Pass-on not possible:

- Do not send notification

- Discard parameter

General action:

- Do not send notification

- Pass on message or parameter

Parameter length: 20 (14h)

- Address: 4900001020FFFFFFFFFFFFFFFFFFFFFFFFFFFFFF

LC-Link Charactreristics

- Parameter's Compatibility: 00h

Pass-on not possible:

- Do not send notification

- Pass on message or parameter

General action:

- Do not send notification

- Pass on message or parameter

Parameter length: 12 (0Ch)

- Maximum forward CPS-SDU bit rate: 10 (Ah)

- Maximum backwards CPS-SDU bit rate: 1102 (44Eh)

- Average forward CPS-SDU bit rate: 2 (2h)

- Average backwards CPS-SDU bit rate: 1094 (446h)

- Maximum forward CPS-SDU size: 3 (3h)

- Maximum backwards CPS-SDU size: 45 (2Dh)

- Average forward CPS-SDU size: 1 (1h)

-Average backwards CPS-SDU size: 43 (2Bh)

OSAID-Orig. sign. assoc. ident.

---------

------

Parameter length: 4 (04h)

- Signalling association identifier: 44F29100

SUGR-Served user gen. reference

- Parameter's Compatibility: 00h

Pass-on not possible:

- Do not send notification

- Pass on message or parameter

General action:

- Do not send notification

- Pass on message or parameter

Parameter length: 4 (04h)

- Field: 00000004

SSISU-Ser. spec. info (SAR-unassured)

- Parameter's Compatibility: 00h

Pass-on not possible:

- Do not send notification

- Pass on message or parameter

General action:

- Do not send notification

- Pass on message or parameter

Parameter length: 7 (07h)

- Max length of SSAR-SDU forwards: 0 (0h)

- Max length of SSAR-SDU backwards: 175 (AFh)

- Transmission error detection disabled

Page 97: 02 - Call Setup

97 © 2005 Nokia Call Setup / Kittipong Thamapa

Establish Confirm

ECF - ESTABLISH CONFIRM

DAID-Dest. sign. assoc. ident.: 44F29100

- Message's Compatibility: 00h

Pass-on not possible:

- Do not send notification

- Pass on message or parameter

General action:

- Do not send notification

- Pass on message or parameter

OSAID-Orig. sign. assoc. ident.

- Parameter's Compatibility: 00h

Pass-on not possible:

- Do not send notification

- Pass on message or parameter

General action:

- Do not send notification

- Pass on message or parameter

Parameter length: 4 (04h)

- Signalling association identifier: 00000011

Page 98: 02 - Call Setup

98 © 2005 Nokia Call Setup / Kittipong Thamapa

Establish Request MessageERQ - ESTABLISH REQUEST

DAID-Dest. sign. assoc. ident.: 00000000

- Message's Compatibility: 00h

Pass-on not possible:

- Do not send notification

- Pass on message or parameter

General action:

- Do not send notification

- Pass on message or parameter

CEID-Connection element ident.

- Parameter's Compatibility: 00h

Pass-on not possible:

- Do not send notification

- Pass on message or parameter

General action:

- Do not send notification

- Pass on message or parameter

Parameter length: 5 (05h)

- Path identifier: 1021 (3FDh)

- Channel identifier: 22 (16h)

NSEA-Dest. NSAP serv. endpoint addr.

-Parameter's Compatibility: 10h

Pass-on not possible:

- Do not send notification

- Discard parameter

General action:

- Do not send notification

- Pass on message or parameter

Parameter length: 20 (14h)

- Address: 4900001020....FFFFFFFF

LC-Link Charactreristics

- Parameter's Compatibility: 00h

Pass-on not possible:

- Do not send notification

- Pass on message or parameter

General action:

- Do not send notification

- Pass on message or parameter

Parameter length: 12 (0Ch)

- Maximum forward CPS-SDU bit rate: 0 (0h)

- Maximum backwards CPS-SDU bit rate: 24 (18h)

- Average forward CPS-SDU bit rate: 0 (0h)

- Average backwards CPS-SDU bit rate: 2 (2h)

- Maximum forward CPS-SDU size: 1 (1h)

- Maximum backwards CPS-SDU size: 6 (6h)

- Average forward CPS-SDU size: 1 (1h)

- Average backwards CPS-SDU size: 6 (6h)

OSAID-Orig. sign. assoc. ident.

- Parameter's Compatibility: 00h

Pass-on not possible:

- Do not send notification

- Pass on message or parameter

General action:

- Do not send notification

- Pass on message or parameter

Parameter length: 4 (04h)

- Signalling association identifier: 44F29200

SUGR-Served user gen. reference

- Parameter's Compatibility: 00h

Pass-on not possible:

- Do not send notification

- Pass on message or parameter

General action:

- Do not send notification

- Pass on message or parameter

Parameter length: 4 (04h)

- Field: 00000006

Page 99: 02 - Call Setup

99 © 2005 Nokia Call Setup / Kittipong Thamapa

Establish Confirm

ECF - ESTABLISH CONFIRM

DAID-Dest. sign. assoc. ident.: 44F29200

- Message's Compatibility: 00h

Pass-on not possible:

- Do not send notification

- Pass on message or parameter

General action:

- Do not send notification

- Pass on message or parameter

OSAID-Orig. sign. assoc. ident.

- Parameter's Compatibility: 00h

Pass-on not possible:

- Do not send notification

- Pass on message or parameter

General action:

- Do not send notification

- Pass on message or parameter

Parameter length: 4 (04h)

- Signalling association identifier: 0000000D

Page 100: 02 - Call Setup

100 © 2005 Nokia Call Setup / Kittipong Thamapa

CELL Update UE Node-B RNC CN

e.g.

Traffic Vol. Meas. Object List

Traffic Volume Report Quantity

UE state

Event ID & Reporting threshold

It defines the target DCH where to measure the traffic volume

It defines the type of quantity. In that case RLC buffer.

UE state: Cell DCH, Cell FACH....

Event type: e4a, e4b....& threshold for the RLC buffer in KB/s

Measurement Control (DPCH)RRC RRC

Capacity AllocationHS-DSCHHS-DSCH

HS-DSCHHS-DSCHCapacity Request

e.g.

CmCH-PI

Maximum MAC PDU Length

HS-DSCH credits

CmCH-PI

User Buffer Size Indicates the user’s buffer size (i.e. the amount of data in the buffer in the SRNC)

The Common Transport Channel Priority Indicator IE indicates the priority of the data frame

It indicates the number of MAC-d PDUs that the RNC is allowed to transmit for the MAC-d flow

Maximum MAC-d PDU length

Page 101: 02 - Call Setup

101 © 2005 Nokia Call Setup / Kittipong Thamapa

Measurement Control

MEASUREMENT CONTROL

DL-DCCH-Message

integrityCheckInfo

messageAuthenticationCode: '01000100110001010011011101101100'B

rrc-MessageSequenceNumber: 9

message

measurementControl

later-than-r3

rrc-TransactionIdentifier: 0

criticalExtensions

r4

measurementControl-r4

measurementIdentity: 2

measurementCommand

setup

trafficVolumeMeasurement

trafficVolumeMeasurementObjectList

UL-TrCH-Identity

dch: 1

trafficVolumeMeasQuantity

rlc-BufferPayload: NULL

trafficVolumeReportingQuantity

rlc-RB-BufferPayload: TRUE

rlc-RB-BufferPayloadAverage: FALSE

rlc-RB-BufferPayloadVariance: FALSE

measurementValidity

ue-State: cell-DCH

reportCriteria

trafficVolumeReportingCriteria

transChCriteriaList

TransChCriteria

ul-transportChannelID

dch: 1

eventSpecificParameters

TrafficVolumeEventParam

eventID: e4a

reportingThreshold: th1024

timeToTrigger: ttt0

pendingTimeAfterTrigger: ptat2

measurementReportingMode

measurementReportTransferMode: acknowledgedModeRLC

periodicalOrEventTrigger: eventTrigger

Page 102: 02 - Call Setup

102 © 2005 Nokia Call Setup / Kittipong Thamapa

Capacity Allocation / Request

HS-DSCH CAPACITY ALLOCATION

Control Frame CRC : 75 (4Bh)

Control Frame Type : 11 (0Bh)

CmCH-PI : 15 (Fh)

Maximum MAC-d PDU Length : 336 bit(s)

HS-DSCH Credits : 12 (00Ch)

HS-DSCH Interval : 10 ms

HS-DSCH Repetition Period : 0 (00h) (unlimited repetition period)

e.g. credits =12

HS-DSCH CAPACITY ALLOCATION

Control Frame CRC : 45 (2Dh)

Control Frame Type : 11 (0Bh)

CmCH-PI : 15 (Fh)

Maximum MAC-d PDU Length : 336 bit(s)

HS-DSCH Credits : 0 (000h) (stop transmission)

HS-DSCH Interval : 10 ms

HS-DSCH Repetition Period : 0 (00h) (unlimited repetition period)

e.g. credits =0

HS-DSCH CAPACITY REQUEST

Control Frame CRC : 50 (32h)

Control Frame Type : 10 (0Ah)

CmCH-PI : 15 (Fh)

User Buffer Size : 3108 (0C24h) octets

Page 103: 02 - Call Setup

103 © 2005 Nokia Call Setup / Kittipong Thamapa

CELL Update UE Node-B RNC CN

Radio Bearer Reconfiguration (FACH)RRC RRC

UE

Open Radio CH

Configure RBs & Log. CH

Radio Bearer Reconfiguration Complete (DPCH)RRC RRC

e.g.

RRC state indicator

RBs and associated Log.& Trans. Ch ID

UL & DL DPCH scramb. codes & SF

CPICH scramb. code info

Status for the UE. Options:Cell DCH, Cell FACH, Cell PCH, URA PCHRadio Bearer to configure, with the relative transport & logical ChannelDPCH UL & DL spreading factor, scramb. code & power informationPrimary CPICH scramb. code info

Cell DCH status

RNC

RNC starts traffic conn.

Page 104: 02 - Call Setup

104 © 2005 Nokia Call Setup / Kittipong Thamapa

Radio Bearer Reconfiguration (1/2)RADIO BEARER RECONFIGURATION [DCCH]

DL-DCCH-Message

------

rrc-StateIndicator: cell-DCH

------

rrc-TransactionIdentifier: 3

rb-Identity: 1

------

ul-UM-RLC-Mode

------

dl-UM-RLC-Mode-r5

------

ul-TransportChannelType

dch: 24

------

dl-TransportChannelType

dch: 24

------

ul-TransportChannelType

rach: NULL

------

dl-TransportChannelType

fach: NULL

-------

rb-Identity: 2

------

ul-AM-RLC-Mode

------

dl-AM-RLC-Mode-r5

------

ul-TransportChannelType

dch: 24

------

dl-TransportChannelType

dch: 24

------

ul-TransportChannelType

rach: NULL

------

dl-TransportChannelType

fach: NULL

------

rb-Identity: 3

------

ul-AM-RLC-Mode

------

dl-AM-RLC-Mode-r5

------

ul-TransportChannelType

dch: 24

dl-TransportChannelType

dch: 24

------

ul-TransportChannelType

rach: NULL

------

dl-TransportChannelType

fach: NULL

------

rb-Identity: 4

------

ul-AM-RLC-Mode

------

dl-AM-RLC-Mode-r5

------

ul-TransportChannelType

dch: 24

------

dl-TransportChannelType

dch: 24

------

ul-TransportChannelType

rach: NULL

------

dl-TransportChannelType

fach: NULL

------

Page 105: 02 - Call Setup

105 © 2005 Nokia Call Setup / Kittipong Thamapa

Radio Bearer Reconfiguration (2/2)rb-Identity: 5

------

ul-AM-RLC-Mode

------

dl-AM-RLC-Mode-r5

------

ul-TransportChannelType

dch: 1

------

dl-TransportChannelType

hsdsch: 0

ul-CommonTransChInfo

------

ul-AddReconfTransChInfoList

UL-AddReconfTransChInformation

ul-TransportChannelType: dch

transportChannelIdentity: 24

------

UL-AddReconfTransChInformation

ul-TransportChannelType: dch

transportChannelIdentity: 1

------

dl-CommonTransChInfo

------

dl-AddReconfTransChInfoList

DL-AddReconfTransChInformation-r5

dl-TransportChannelType

dch: 24

------

dch-QualityTarget

bler-QualityValue: -20

DL-AddReconfTransChInformation-r5

dl-TransportChannelType

hsdsch: NULL

------

dch-QualityTarget

bler-QualityValue: -20

ul-ChannelRequirement

ul-DPCH-Info

------

scramblingCode: 1000212

spreadingFactor: sf16

------

dl-HSPDSCH-Information

-------

HS-SCCH-Codes: 4

------

dl-CommonInformation

dl-DPCH-InfoCommon

------

sfd256: pb4

------

primaryCPICH-Info

primaryScramblingCode: 54

------

dl-DPCH-InfoPerRL

fdd

pCPICH-UsageForChannelEst: mayBeUsed

------

sf-AndCodeNumber

sf256: 10

------

Page 106: 02 - Call Setup

106 © 2005 Nokia Call Setup / Kittipong Thamapa

Radio Bearer Reconfiguration Complete

RADIO BEARER RECONFIGURATION COMPLETE

UL-DCCH-Message

integrityCheckInfo

messageAuthenticationCode: '10111011101100101110110100001011'B

rrc-MessageSequenceNumber: 7

message

radioBearerReconfigurationComplete

rrc-TransactionIdentifier: 3