Wideband tdd wcdma for the unpaired spectrum phần 7 pptx

The Core Network sends an ATTACH ACCEPT NAS message to the S-RNC inRANAP DIRECT TRANSFER message... The S-RNC sends an MM: AUTHENTICATION RESPONSE message in the payload of RANAP Direct

3 RRC: INITIAL DIRECT TRANSFER - DCCH/RACH

(MM: LOCATION UPDATING REQUEST)

4 RANAP:INITIAL DIRECT TRANSFER (MM: LOCATION UPDATING REQUEST)

6 RANAP: DIRECT TRANSFER (MM: LOCATION UPDATING ACCEPT)

7 RRC: DIRECT TRANSFER - DCCH/FACH (MM: LOCATION UPDATING ACCEPT)

8 RRC: DIRECT TRANSFER - DCCH/RACH (MM: TMSI REAL LOCATION COMPLETE)

9 RANAP:DIRECT TRANSFER (MM: TMSI REALLOCATION COMPLETE)

3 and 4 The UE sends a GMM (GPRS Mobility Management) message ‘AttachRequest’ to the SRNC, which is relayed to the CN

6 The Core Network sends an ATTACH ACCEPT (NAS) message to the S-RNC inRANAP DIRECT TRANSFER message

End-to-End Communication Procedures 141

7 RRC: DIRECT TRANSFER - DCCH/FACH

8 RRC: DIRECT TRANSFER - DCCH/RACH

5 Authentication and Security

Figure 5.42 UE Registration on PS Domain

7 The S-RNC forwards the ATTACH ACCEPT (NAS) message to the UE in RRCDIRECT TRANSFER message

8 UE sends an ATTACH COMPLETE (NAS) message to the S-RNC in RRC DIRECTTRANSFER message

9 The S-RNC sends the ATTACH COMPLETE (NAS) message to the Core Networkwithin the RANAP DIRECT TRANSFER message

142 TDD Procedures

5.16.2 Authentication and Security

Figure 5.43 shows how a CN authenticates the User and initiates the Ciphering (for data)and Integrity Protection (for signaling messages) processes The CS and PS proceduresare separately included in the same figure

(GMM:AUTHENTICATION AND CIPHERING RESPONSE)

7 RRC: DIRECT TRANSFER - DCCH/RACH

10 RRC :Security Mode Command - DCCH/FACH

11 RRC: Security Mode Complete - DCCH/RACH

1 RANAP DIRECT TRANSFER (MM:AUTHENTICATION REQUEST)

(MM:AUTHENTICATION RESPONSE)

4 RANAP DIRECT TRANSFER

5 RANAP DIRECT TRANSFER (GMM:AUTHENTICATION AND CIPHERING REQUEST)

8 RANAP DIRECT TRANSFER (GMM:AUTHENTICATION AND CIPHERING RESPONSE)

CN indicates to UTRAN the selected security algorithm and delivers the integrity and encyption key to UTRAN

9 RANAP Security Mode Command

12 RANAP Security Mode Complete

End-to-End Communication Procedures 143

Individual steps are described below Steps 1–4 are applicable for CS domain, whereasSteps 5–8 are for PS domain The remaining steps are common to both CS and PS:Alternative: for Circuit-Switched (CS) transactions

1 The CN sends a MM: AUTHENTICATION REQUEST message in the payload ofRANAP Direct Transfer message to the S-RNC

2 The S-RNC sends an MM: AUTHENTICATION REQUEST message in the payload

of RRC Direct Transfer message to UE

3 After executing the authentication algorithms on USIM the UE responds with anMM: AUTHENTICATION RESPONSE message again in the payload of RRC DirectTransfer message

4 The S-RNC sends an MM: AUTHENTICATION RESPONSE message in the payload

of RANAP Direct Transfer message to CN

Alternative: for Packet-Switched (PS) transactions

5 The CN sends a GMM: AUTHENTICATION AND CIPHERING REQUEST message

in the payload of RANAP Direct Transfer message to the S-RNC

6 The S-RNC sends a GMM: AUTHENTICATION AND CIPHERING REQUESTmessage in the payload of RRC Direct Transfer message to UE

7 After executing the authentication algorithms on USIM, the UE responds with aGMM: AUTHENTICATION AND CIPHERING RESPONSE message again in thepayload of RRC Direct Transfer message

8 The S-RNC sends a GMM: AUTHENTICATION AND CIPHERING RESPONSEmessage in the payload of RANAP Direct Transfer message to CN

For both Circuit-Switched (CS) and Packet-Switched (PS) transactions

9 The CN sends a RANAP SECURITY MODE COMMAND message to S-RNC Inthis message the CN domain indicates to UTRAN that the transaction should beencrypted This message indicates the selected security algorithms and delivers theintegrity and encryption keys to UTRAN

10 Based on the information received in the RANAP message, the S-RNC sends RRCSecurity Mode Command message to UE In this message, the S-RNC commandsthe UE to start encryption with the corresponding keys and algorithms

11 The UE indicates that it has successfully turned on the selected integrity protectionalgorithm and encryption algorithm by sending RRC SECURITY MODE COM-PLETE MESSAGE

12 The S-RNC informs the CN domain about the procedure completion by sending theRANAP SECURITY MODE COMPLETE message

5.16.3 CS Call Control Procedures

Call Control procedures can be classified as either UE originated or UE terminated.Furthermore, they can also be classified as Setup procedures or Connect procedures,where Setup procedure denotes the UE requesting a call, or a call being delivered tothe UE, and Connect procedure denotes the completion of a call connection through theexternal network (PSTN)

144 TDD Procedures

5.16.3.1 Call Setup Procedure

Figure 5.44 illustrates the main steps involved for both originated and terminated calls

UE-Individual steps are described below:

Alternative: UE Terminating Transaction

1 The Core Network sends SETUP message to S-RNC in the RANAP Direct Transfermessage to initiate a mobile terminated call establishment

2 S-RNC sends RRC DIRECT TRANSFER message containing the SETUP message

to UE

CONFIRMED to the S-RNC to confirm the incoming call request

4 S-RNC forwards the CALL CONFIRMED message to the CN in RANAP DIRECTTRANSFER message

Alternative: UE Originating Transaction

5 UE sends SETUP message in RRC: DIRECT TRANSFER message to S-RNC toinitiate a mobile originating call establishment

6 S-RNC forwards the SETUP message in RANAP DIRECT TRANSFER message toCore Network

7 The Core Network responds with CALL PROCEEDING message in RANAP DIRECTTRANSFER message to indicate that the requested call establishment information hasbeen received

1 RANAP DIRECT TRANSFER

4 RANAP DIRECT TRANSFER (CC: CALL CONFIRMED)

5 RRC: DIRECT TRANSFER - DCCH/RACH

6 RANAP DIRECT TRANSFER (CC: SETUP)

7 RANAP DIRECT TRANSFER (CC: CALL PROCEEDING)

8 RRC: DIRECT TRANSFER - DCCH/FACH (CC: CALL PROCEEDING)

2 RRC: DIRECT TRANSFER - DCCH/FACH

End-to-End Communication Procedures 145

8 The S-RNC forwards the CALL PROCEEDING message in RRC DIRECT FER message to UE

TRANS-5.16.3.2 Call Connect Procedure

Figure 5.45 illustrates the main steps involved In the UE terminated case, the call hasarrived at the UE and the Connect procedure describes the steps taken by the UE sub-sequently Similarly, in the UE terminated case, the call has been placed to the remoteparty, and an Alert indication arrives at the CN The following steps are captured in theConnect procedure:

Alternative: UE Terminating Transaction

1 UE sends Alerting message in RRC: DIRECT TRANSFER message to the S-RNC

to indicate that the called user (UE) alerting has been initiated

2 S-RNC forwards the ALERTING message in RANAP DIRECT TRANSFER message

to the Core Network

12 RANAP DIRECT TRANSFER (CC: CONNECT ACKNOWLEDGE)

9 RANAP DIRECT TRANSFER (CC: CONNECT)

10 RRC: DIRECT TRANSFER - DCCH/DCH

(CC: CONNECT)

1 RRC: DIRECT TRANSFER - DCCH/DCH (CC: ALERTING)

2 RANAP DIRECT TRANSFER (CC: ALERTING)

7 RANAP DIRECT TRANSFER (CC: ALERTING)

8 RRC: DIRECT TRANSFER - DCCH/DCH (CC: ALERTING)

Figure 5.45 Call Control Connect Signaling Procedure

146 TDD Procedures

3 UE sends CONNECT message in RRC DIRECT TRANSFER message to the S-RNC

to indicate call acceptance by UE

4 S-RNC forwards the CONNECT message to the Core Network in RANAP DIRECTTRANSFER message

5 Core Network sends CONNECT ACKNOWLEDGE message in RANAP DIRECTTRANSFER message to the S-RNC to indicate that the UE has been awarded the call

6 S-RNC forwards the CONNECT ACKNOWLEDGE message to UE in RRC DIRECTTRANSFER message

Alternative: UE Originating Transaction

7 Core Network sends Alerting message to the S-RNC in RANAP DIRECT FER message to indicate that the called user (UE) alerting has been initiated

TRANS-8 S-RNC forwards the ALERTING message in RRC DIRECT TRANSFER message

to the UE

9 Core Network sends CONNECT message in RANAP DIRECT TRANSFER message

to the S-RNC to indicate call acceptance by UE

10 S-RNC forwards the CONNECT message to the UE in RRC DIRECT FER message

TRANS-11 UE sends CONNECT ACKNOWLEDGE message in RRC DIRECT TRANSFERmessage to the S-RNC to acknowledge the offered connection

12 S-RNC forwards the CONNECT ACKNOWLEDGE message to CN in RANAPDIRECT TRANSFER message

5.16.4 PS Session Control Procedures

PS sessions are established by setting up a PDP Context between the UE and the GGSN

of the CN, see Figure 5.46 Procedures for Requesting and Accepting the PDP Contextare shown below:

Activate PDP Context Request

Optional: For UE terminating transaction only

1 Core Network sends SM: REQUEST PDP CONTEXT ACTIVATION message inRANAP DIRECT TRANSFER message to initiate activation of the PDP context

2 S-RNC forwards the SM: REQUEST PDP CONTEXT ACTIVATION message in RRCDIRECT TRANSFER message to the UE

For both UE-terminating and UE-originating transactions

3 UE sends SM: ACTIVATE PDP CONTEXT REQUEST message in RRC DIRECTTRANSFER message to S-RNC to request activation of a PDP context

4 S-RNC forwards the SM: ACTIVATE PDP CONTEXT REQUEST message in RANAPDIRECT TRANSFER message to the Core Network

Activate PDP Context Accept

5 The Core Network sends ACTIVATE PDP CONTEXT ACCEPT in RANAP DIRECTTRANSFER message to the S-RNC to acknowledge activation of a PDP context

6 S-RNC forwards the ACTIVATE PDP CONTEXT ACCEPT to UE in RRC DIRECTTRANSFER message

End-to-End Communication Procedures 147

2 RRC: DIRECT TRANSFER - DCCH/FACH (SM: REQUEST PDP CONTEXT ACTIVATION)

3 RRC: DIRECT TRANSFER - DCCH/RACH (SM: ACTIVATE PDP CONTEXT REQUEST)

4 RANAP DIRECT TRANSFER (SM: ACTIVATE PDP CONTEXT REQUEST)

5 RANAP DIRECT TRANSFER (SM: ACTIVATE PDP CONTEXT ACCEPT)

6 RRC: DIRECT TRANSFER - DCCH/FACH (SM: ACTIVATE PDP CONTEXT ACCEPT)

Figure 5.46 Activate PDP Context Signaling Procedure

5.16.5 CS Call and PS Session Data Procedures

Figures 5.47 and 5.48 show how a complete procedure looks like for CS Calls and PS sions It includes the UE Authentication, Registration, Call/Session Setup, and Data Flow.The steps involved are:

ses-Optional: UE-Terminated Transaction

1 In case of UE-terminating transactions, the paging signaling procedure is invoked topage the UE

2 RRC Connection Setup procedure is invoked to establish RRC connection between

UE and S-RNC for the incoming/outgoing call After the RRC Connection Setupprocedure is performed, the UE will be in RRC CONNECTED state waiting for thefirst RAB Setup

3 In the Initial Direct transfer, the UE will provide the network with the reason for thistransaction in the Service Request message

4 Authentication and Security is performed between UE and network to authenticatethe UE and to agree on the encryption if it is supported

5 Call Control (CC Setup) is performed to set up the call between UE and Core Network

6 The RAB setup procedure is performed

6a If the UE was in CELL-FACH, the UE now moves to the CELL-DCH state

7 CC Connect is performed between the CN and UE to complete the call setup

8 In case of Call the termination, the RAB Release procedure will be invoked

9 When all the RABs in the UE are released, the UE will be in RRC CONNECTEDstate and RRC Connection Release will be invoked

6 RAB Setup when UE is on CELL_FACH

7 RAB Setup when UE is on CELL_DCH

ALT: CELL_FACH

ALT: CELL_DCH

3 Initial Direct Transfer (Service Request)

4 Authentication and Security

RAB ESTABLISHED

RRC CONNECTED IDLE

Figure 5.47 CS Overall Procedure

The complete procedure for PS is described below Steps 1–4 and 11 are the same asthose for the CS overall procedure The others are now described:

5 The Activate PDP Context Request is performed to request establishment of a PDPcontext between the UE and the Core Network for a specific QoS

6 The PS-RAB Setup (UE is on CELL FACH) procedure is performed

7 The Activate PDP Context Accept is performed to acknowledge activation of aPDP context

8 First Temp-DCH allocation is invoked (Temp-DCH is a DCH/T allocated for a finitevalue for the duration parameter.)

9 Subsequent Temp-DCH allocation will be invoked

10 PS-RAB Release procedure will be invoked

6 PS RAB Setup when UE is admitted on CELL_FACH

3 Initial Direct Transfer (Service request)

4 Authentication and Security

11 RRC Connection Release

RAB ESTABLISHED

RRC CONNECTED IDLE

5 Activate PDP Context Request

7 Activate PDP Context Accept

IDLE

8 First Temp-DCH Allocation

9 Sub-Sequent Temp-DCH Allocation

[3] 3GPP TS 25.303 v4.5.0, ‘3GPP; TSG RAN; Interlayer Procedures in Connected Mode (Release 4)’, 06.

2002-[4] 3GPP TR 25.931 v4.4.0, ‘3GPP; TSG RAN; UTRAN Functions, Examples of Signaling Procedures (Release 4)’, 2002-06.

[5] 3GPP TS 25.331 v4.5.0, ‘3GPP; TSG RAN; Radio Resource Control (RRC); Protocol Specification (Release 4)’, 2002-06.

Receiver Signal Processing

The previous chapters have introduced the system overview, fundamentals of TDD, anddetails of the radio interface followed by procedures In this chapter, we will discuss anumber of technologies necessary to develop WTDD systems

The WTDD Radio Interface and Procedures specify how to establish radio connectionsand manage them Having done that, it is first of all necessary to discuss how the variousfeatures of the Radio Interface and Procedures are used to provide required Quality ofService to various user applications Subsequently, we will address a number of aspects

of efficient Management of the precious Radio Resources, with the central objective being

to provide adequate QoS to a large number of users over a variety of channel conditions.Then we consider a number of Receiver algorithms, such as Data Detection, ChannelEstimation, etc Finally, we show how these various technologies may be put together todevelop various network elements, namely UE, Node B and RNC

6.1 RECEIVER ARCHITECTURE

Figure 6.1 shows the overall architecture of a BS Receiver It is broken up into threeblocks, namely the Receiver Front End, Physical Channel Processing and Transport Chan-nel Processing:

• Receiver Front End: The receiver front end operates on the transmitted signal generated

by one or more UE transmitters The signal from each antenna is passed through thereceiver pulse-shaping filter, which is a truncated version of the root-raised cosine filter,

as described in a later Section of this chapter

• Each of the data streams is passed through the joint channel estimation block and apost-processing block There are several functionally equivalent implementations ofthe joint channel estimation procedure The Steiner algorithm [2] using the prime fac-tor DFT algorithm is a particularly suitable one Post-processing eliminates false orweak paths from the channel estimates The demodulator implements either a singleMulti User Detector or multiple RAKE receivers (synonymously referred to as detec-tors/demodulators) Among the MUD receivers, there are Zero Forcing Joint Detection(ZF-BLE) and MMSE Joint Detection (MMSE-BLE) Block Linear Equalizer tech-niques, whereas RAKE receiver is implemented using a traditional Matched Filter The

Wideband TDD: WCDMA for the Unpaired Spectrum P.R Chitrapu

 2004 John Wiley & Sons, Ltd ISBN: 0-470-86104-5

152 Receiver Signal Processing

Physical Channel Processing Transport Channel Processing

DCH 0 DCH N

USCH Front End Processing

RACH

other connections

• Physical Channel Segmentation

• Second Deinterleaving

• Physical Channel Demapping

joint Channel Resp 1 joint Channel Resp 2

est Noise Variance 1 est Noise Variance 2

soft Bits Out

Channel Estimation

Channel Estimation

Post Processing Post Processing Noise Estimation Noise Estimation

Rx Fir

Rx Fir

Timeslot

Rate

Figure 6.2 Receiver Front End Processing Details

output of the demodulator (joint detector) is a sequence of soft symbols Figure 6.2shows the details of the Receiver Front End; in the figure, samples from dual-diversityantennas are shown as chips 1 and 2

• Physical Channel Processing: The physical channel processor separates the output ofthe Receiver front end into several data streams, each representing a coded compositetransport channel (CCTrCH) In addition, it provides the TFCI and the TPC bits for eachCCTrCH For each CCTrCH, the second de-interleaving is performed (also referred to

as intra-frame interleaving), followed by bit descrambling The CCTrCH data stream

is now separated into its constituent transport channels These operations are inverses

to the operations defined in TS 25.222 [1] Figure 6.3 shows the details of the PhysicalChannel Processing

• Transport Channel Processing: The transport channel processing operates on the datacorresponding to a single transport channel It performs de-rate-matching (which isthe inverse operation of the rate-matching procedure) and 1st de-interleave block (alsoknown as interframe de-interleaving) This data is now decoded for channel decoding,

Receiver Architecture 153

Physical Channel Demapping

TPC0TFCI0

Physical Channel Demapping

TPCNTFCIN

other connections

Transport Channel De- Multiplexing

To Transport Channel Processing From Receiver Front End

Demodulator / Detector

Timeslot Rate Frame Rate

2nd Interleaving bit descrambling

Figure 6.3 Physical Channel Processing Details

Interleaving

De-Channel De-coding CRC Check

BER

BLER

SIR Estimate

Error Measurenment

• Noise Variance Estimation

• Blind Code Detection

Joint Detection MUD, RAKE, SUD

• ΑGC

• Rx Filter

• Freq and Timing

Sync.

Physical Channel Processing

Transport Channel Processing

DCH 0 DCH N BCH PCH FACH DSCH

Front End Processing

Figure 6.5 UE Receiver Architecture

which may be either Viterbi decoding or turbo decoding, depending on the coding scheme used in the transmitter The decoder also provides estimates of thechannel bit error rate (BER) Note that SIR estimation is required for turbo decoding

channel-as well channel-as for power control (except that it is performed on the CCTrCH, rather thaneach transport channel) Next the CRC is checked and the total number of block errorsare counted, based on which block error rate (BLER) is estimated The CRC errors areused in Uplink Outer Loop Power Control Figure 6.4 shows the details

From a signal processing point of view, the UE receiver is very similar to the BS receiver.One important difference is that the BS receiver processes multiple user signals unlike the