140 TDD Procedures S-RNC Iur C-RNC Uu UE Node B Iub CN Iu 1. SYSTEM INFORMATION (BCCH) IDLE RRC CONNECTED 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) IDLE 5. Authentication and Security 2. RRC Connection Setup 10. RRC Connection Release Figure 5.41 UE Registration on CS Domain Steps 1–2 and 10 are the same as those in CS Registration case. The others are described below: 3 and 4. The UE sends a G MM (GPRS Mobility Management) message ‘Attach Request’ to the SRNC, which is relayed to the CN. 6. The Core Network sends an ATTACH ACCEPT (NAS) message to the S-RNC in RANAP DIRECT TRANSFER message. End-to-End Communication Procedures 141 S-RNC Iur C-RNC Uu UE Iub CN Iu 1. SYSTEM INFORMATION (BCCH) IDLE RRC CONNECTED 3. RRC: INITIAL DIRECT TRANSFER - DCCH/RACH (GM M: ATTACH REQUEST) 6. RANAP:DIRECT TRANSFER 7. RRC: DIRECT TRANSFER - DCCH/FACH 8. RRC: DIRECT TRANSFER - DCCH/RACH IDLE Node B (GMM: ATTACH ACCEPT) (GMM: ATTACH COMPLETE) (GMM: ATTACH COMPLETE) 9. RANAP: DIRECT TRANSFER (GMM: ATTACH REQUEST) 4. RANAP: INITIAL DIRECT TRANSFER (GMM: ATTACH ACCEPT) 2. RRC Connection Setup 10. RRC Connection Release 5. Authentication and Security Figure 5.42 UERegistrationonPSDomain 7. The S-RNC forwards the ATTACH ACCEPT (NAS) message to the UE in RRC DIRECT TRANSFER message. 8. UE sends an ATTACH COMPLETE (NAS) message to the S-RNC in RRC DIRECT TRANSFER message. 9. The S-RNC sends the ATTACH COMPLETE (NAS) message to the Core Network within 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 procedures are separately included in the same figure. S-RNC Iur C-RNC Uu UE Node B Iub CN Iu Perfrom authentication algorithmon USIM ALT : CS ALT : PS Perfrom authentication algorithmon USIM 2. RRC: DIRECT TRANSFER - DCCH/FACH (MM:AUTHENTICATION REQUEST) 3. RRC: DIRECT TRANSFER - DCCH/RACH (MM:AUTHENTICATION RESPONSE) 6. RRC: DIRECT TRANSFER - DCCH/FACH (GMM:AUTHENTICATION AND CIPHERING REQUEST) (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 UE successfully turns on the security algorithms Figure 5.43 Authentication and Security End-to-End Communication Procedures 143 Individual steps are described below. Steps 1–4 are applicable for CS domain, whereas Steps 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 of RANAP 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 an MM: AUTHENTICATION RESPONSE message again in the payload of RRC Direct Transfer 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 REQUEST message in the payload of RRC Direct Transfer message to UE 7. After executing the authentication algorithms on USIM, the UE responds with a GMM: AUTHENTICATION AND CIPHERING RESPONSE message again in the payload of RRC Direct Transfer message. 8. The S-RNC sends a GMM: AUTHENTICATION AND CIPHERING RESPONSE message 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. In this message the CN domain indicates to UTRAN that the transaction should be encrypted. This message indicates the selected security algorithms and delivers the integrity and encryption keys to UTRAN. 10. Based on the information received in the RANAP message, the S-RNC sends RRC Security Mode Command message to UE. In this message, the S-RNC commands the UE to start encryption with the corresponding keys and algorithms. 11. The UE indicates that it has successfully turned on the selected integrity protection algorithm 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 the RANAP 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 to the UE, and Connect procedure denotes the completion of a call connection through the external network (PSTN). 144 TDD Procedures 5.16.3.1 Call Setup Procedure Figure 5.44 illustrates the main steps involved for both UE-originated and UE- terminated calls. Individual steps are described below: Alternative: UE Terminating Transaction 1. The Core Network sends SETUP message to S-RNC in the RANAP Direct Transfer message to initiate a mobile terminated call establishment. 2. S-RNC sends RRC DIRECT TRANSFER message containing the SETUP message to UE. 3. UE responds with RRC DIRECT TRANSFER message containing CALL CONFIRMED to the S-RNC to confirm the incoming call request. 4. S-RNC forwards the CALL CONFIRMED message to the CN in RANAP DIRECT TRANSFER message. Alternative: UE Originating Transaction 5. UE sends SETUP message in RRC: DIRECT TRANSFER message to S-RNC to initiate a mobile originating call establishment. 6. S-RNC forwards the SETUP message in RANAP DIRECT TRANSFER message to Core Network. 7. The Core Network responds with CALL PROCEEDING message in RANAP DIRECT TRANSFER message to indicate that the requested call establishment information has been received. S-RNC Iur C-RNC Uu UE Node B Iub CN Iu ALT :UE Terminating Transaction ALT :UE Originating Transaction 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 (CC: SETUP) (CC: SETUP) 3. RRC: DIRECT TRANSFER - DCCH/RACH (CC: CALL CONFIRMED) (CC: SETUP) Figure 5.44 Call Control Setup Signaling Procedure End-to-End Communication Procedures 145 8. The S-RNC forwards the CALL PROCEEDING message in RRC DIRECT TRANS- FER message to UE. 5.16.3.2 Call Connect Procedure Figure 5.45 illustrates the main steps involved. In the UE terminated case, the call has arrived 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 remote party, and an Alert indication arrives at the CN. The following steps are captured in the Connect 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. S-RNC Iur C-RNC Uu UE NodeB Iub CN Iu ALT :UE Terminating Transaction ALT :UE Originating Transaction 5. RANAP DIRECT TRANSFER (CC: CONNECT ACKNOWLEDGE) 6. RRC: DIRECT TRANSFER - DCCH/DCH (CC: CONNECT ACKNOWLEDGE) 3. RRC: DIRECT TRANSFER - DCCH/DCH (CC: CONNECT) 4. RANAP DIRECT TRANSFER (CC: CONNECT) 11. RRC: DIRECT TRANSFER - DCCH/DCH (CC: CONNECT ACKNOWLEDGE) 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 DIRECT TRANSFER message. 5. Core Network sends CONNECT ACKNOWLEDGE message in RANAP DIRECT TRANSFER 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 DIRECT TRANSFER message. Alternative: UE Originating Transaction 7. Core Network sends Alerting message to the S-RNC in RANAP DIRECT TRANS- FER message to indicate that the called user (UE) alerting has been initiated. 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 TRANS- FER message. 11. UE sends CONNECT ACKNOWLEDGE message in RRC DIRECT TRANSFER message to the S-RNC to acknowledge the offered connection. 12. S-RNC forwards the CONNECT ACKNOWLEDGE message to CN in RANAP DIRECT 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 Context are shown below: Activate PDP Context Request Optional: For UE terminating transaction only 1. Core Network sends SM: REQUEST PDP CONTEXT ACTIVATION message in RANAP DIRECT TRANSFER message to initiate activation of the PDP context. 2. S-RNC forwards the SM: REQUEST PDP CONTEXT ACTIVATION message in RRC DIRECT TRANSFER message to the UE. For both UE-terminating and UE-originating transactions 3. UE sends SM: ACTIVATE PDP CONTEXT REQUEST message in RRC DIRECT TRANSFER message to S-RNC to request activation of a PDP context. 4. S-RNC forwards the SM: ACTIVATE PDP CONTEXT REQUEST message in RANAP DIRECT TRANSFER message to the Core Network. Activate PDP Context Accept 5. The Core Network sends ACTIVATE PDP CONTEXT ACCEPT in RANAP DIRECT TRANSFER message to the S-RNC to ac knowledge activation of a PDP context. 6. S-RNC forwards the ACTIVATE PDP CONTEXT ACCEPT to UE in RRC DIRECT TRANSFER message. End-to-End Communication Procedures 147 S-RNC Iur C-RNC Uu UE Node B Iub CN Iu OPT :UE Terminating Transaction 1. RANAP DIRECT TRANSFER (SM: REQUEST PDP CONTEXT ACTIVATION) 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 ses- sions. It includes the UE Authentication, Registration, Call/Session Setup, and Data Flow. The steps involved are: Optional: UE-Terminated Transaction 1. In case of UE-terminating transactions, the paging signaling procedure is invoked to page 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 Setup procedure is performed, the UE will be in RRC CONNECTED state waiting for the first RAB Setup. 3. In the Initial Direct transfer, the UE will provide the network with the reason for this transaction in the Service Request message. 4. Authentication and Security is performed between UE and network to authenticate the 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 CONNECTED state and RRC Connection Release will be invoked. 148 TDD Procedures S-RNC Iur C-RNC Uu UE Node B Iub CN Iu 2. RRC Connection Setup 1. Paging OPT: UE Terminating Transaction 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 8. CC Connect 5. CC Setup 10. RRC Connection Release IDLE 9. RAB Release Figure 5.47 CS Overall Procedure The complete procedure for PS is described below. Steps 1–4 and 11 are the same as those for the CS overall procedure. The others are now described: 5. The Activate PDP Context Request is performed to request establishment of a PDP context 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 a PDP context. 8. First Temp-DCH allocation is invoked. (Temp-DCH is a DCH/T allocated for a finite value for the duration parameter.) 9. Subsequent Temp-DCH allocation will be invoked. 10. PS-RAB Release procedure will be invoked. References 149 S-RNC Iur C-RNC Uu UE Node B Iub CN Iu 2. RRC Connection Setup 1. Paging OPT: UE Terminating Transaction 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 10. PS RAB Release Figure 5.48 PS Overall Procedure REFERENCES [1] 3GPP TS 25.224 v4.5.0, ‘3GPP; TSG RAN; Physical Layer Procedures (TDD) (Release 4)’, 2003-03. [2] 3GPP TS 25.304 v4.5.0, ‘3GPP; TSG RAN; UE Procedures in Idle Mode and Procedures for Cell Rese- lection in Connected Mode, (Release 4)’, 2002-06. [3] 3GPP TS 25.303 v4.5.0, ‘3GPP; TSG RAN; Interlayer Procedures in Connected Mode (Release 4)’, 2002- 06. [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. [...]... I, the MMSE-BLE estimate is given by: ˆ d = (AH A + σ 2 I )−1 AH r Just like the ZF-BLE, the MMSE-BLE requires a computationally expensive matrix inversion The dimensions of the matrix to be inverted are the same as for the ZF-BLE Fortunately, the matrix to be inverted has the same banded structure (after appropriate reordering of columns) as for the ZF-BLE Thus, efficient implementation based on the. .. filters are suitable for cases where signals can be separated by codes This is not the case for high capacity TDD systems, primarily because of the low spreading factors (SF ≤ 16) We therefore focus on SUD and MUD techniques There are a large number of MUD techniques that were derived and investigated in the literature These techniques vary in their performance and computational complexity The optimal data... is the number of codes and L is the total number of symbols affected by the transmission of a single symbol In the example above, L = 5 Assume that all codes have the same spreading factor, and denote by Ns the number of symbols per code The Cholesky decomposition of a banded matrix is also banded with the same bandwidth as the original matrix [5] We therefore can write the Cholesky factor G in the. .. which then arrive at the receiver with equal power The SIC-JD can be configured to perform JD on multi-codes associated with the same user, and cancel MAI between groups of multi-codes via SIC 6.3.10 Implementation and Performance The Table 6.2 illustrates the relative computational loads of the various MUD algorithms We now illustrate the performance of the various MUD algorithms in various channels The. .. of the transmit diversity is mandatory in the UE, multiple channel estimation must be supported also in the UE Hence, the channel estimation problem becomes similar for the uplink or the downlink, namely, that of estimating multiple channel responses To facilitate channel estimation, the TDD burst contains a known training sequence, namely, the midamble Each UE transmits a unique midamble; for the. .. general, among the estimated coefficients for each channel response, only a few correspond to actual multi-paths, the rest represent only the noise The post-processing can be done to provide a more accurate channel response by reducing the number of such noise-only terms, thereby improving the performance of the data detection For example, a simple post-processing may involve zeroing out the channel coefficients,... Architecture which may be either Viterbi decoding or turbo decoding, depending on the channelcoding scheme used in the transmitter The decoder also provides estimates of the channel bit error rate (BER) Note that SIR estimation is required for turbo decoding as well as for power control (except that it is performed on the CCTrCH, rather than each transport channel) Next the CRC is checked and the total number... the details of the Receiver Front End; in the figure, samples from dual-diversity antennas are shown as chips 1 and 2 • Physical Channel Processing: The physical channel processor separates the output of the Receiver front end into several data streams, each representing a coded composite transport channel (CCTrCH) In addition, it provides the TFCI and the TPC bits for each CCTrCH For each CCTrCH, the. .. G62 G63 G64 G65 G66 0 0 0 0 0 0 0 G73 G74 G75 G76 G 77 0 0 0 0 0 0 0 G84 G85 G86 G 87 G88 0 0 0 0 0 0 0 G95 G96 G 97 G98 G99 0 0 0 0 0 0 0 G10,6 G10 ,7 G10,8 G10,9 G10,10 0 0 0 0 0 0 0 G11 ,7 G11,8 G11,9 G11,10 G11,11 0 0 0 0 0 0 0 G12,8 G12,9 G12,10 G12,11 G12,12 (1)                          164 Receiver Signal Processing Our goal is to show that the Cholesky factor can be approximated... G65 G∗ 52 53 54 55 H R2 = G73 G∗ + G74 G∗ + G75 G∗ 53 54 55 H R3 = G84 G∗ + G85 G∗ 54 55 H R4 = G95 G∗ 55 Equations for the 6th block column: R0 = |G62 |2 + |G63 |2 + |G64 |2 + |G65 |2 + |G66 |2 H R1 = G73 G∗ + G74 G∗ + G75 G∗ + G76 G∗ 63 64 65 66 H R2 = G84 G∗ + G85 G∗ + G86 G∗ 64 65 66 H R3 = G95 G∗ + G96 G∗ 65 66 H R4 = G10,6 G∗ 66 and so on The key is to notice that all of these equations are satisfied . performed, the UE will be in RRC CONNECTED state waiting for the first RAB Setup. 3. In the Initial Direct transfer, the UE will provide the network with the reason for this transaction in the. 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 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 Channel