ETSI TS 125 427 V11.0.0 (2012-11)

Universal Mobile Telecommunications System (UMTS); UTRAN Iub/Iur interface user plane protocol for DCH data streams (3GPP TS 25.427 version 11.0.0 Release 11)

RTS/TSGR-0325427vb00

General Information

• Status: Published
• Publication Date: 15-Nov-2012
• Technical Committee: 3GPP RAN 3 - lub specification, lur specification, lu specification and UTRAN & O&M
• Current Stage: 12 - Completion
• Due Date: 17-Oct-2012
• Completion Date: 16-Nov-2012

Standards Content (Sample)

Technical Specification
Universal Mobile Telecommunications System (UMTS);
UTRAN Iub/Iur interface user plane protocol
for DCH data streams
(3GPP TS 25.427 version 11.0.0 Release 11)

3GPP TS 25.427 version 11.0.0 Release 11 1 ETSI TS 125 427 V11.0.0 (2012-11)

Reference
RTS/TSGR-0325427vb00
Keywords
UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.

© European Telecommunications Standards Institute 2012.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
3GPP TS 25.427 version 11.0.0 Release 11 2 ETSI TS 125 427 V11.0.0 (2012-11)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://ipr.etsi.org).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).
The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or
GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables.
The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under
http://webapp.etsi.org/key/queryform.asp.
ETSI
3GPP TS 25.427 version 11.0.0 Release 11 3 ETSI TS 125 427 V11.0.0 (2012-11)
Contents
Intellectual Property Rights . 2
Foreword . 2
Foreword . 6
1 Scope . 7
2 References . 7
3 Definitions and abbreviations . 7
3.1 Definitions . 7
3.2 Abbreviations . 8
3.3 Specification Notations . 8
4 General aspects . 9
4.1 DCH and E-DCH FP services . 10
4.2 Services expected from the Data Transport Network layer . 10
4.3 Protocol Version . 10
5 DCH Frame Protocol procedures . 11
5.1 Data Transfer . 11
5.1.0 General . 11
5.1.1 Uplink for DCH . 11
5.1.1a Uplink for E-DCH . 11
5.1.2 Downlink . 12
5.2 Timing Adjustment. 13
5.3 DCH Synchronisation . 14
5.4 Outer Loop PC Information Transfer [FDD, 1.28 Mcps TDD] . 14
5.5 Node Synchronisation . 14
5.6 Rx Timing Deviation Measurement [3.84 Mcps and 7.68 Mcps TDD] . 15
5.7 DSCH TFCI Signalling [FDD] . 15
5.8 Radio Interface Parameter Update [FDD] . 15
5.9 Timing Advance [3.84 Mcps and 7.68 Mcps TDD] . 16
5.10 General . 16
5.10.1 Transport bearer replacement . 16
5.10.2 Transport channel addition . 17
5.11 Generation of subframe number . 17
5.12 Generation of number of HARQ retransmissions . 17
5.13 Indication of HARQ failure . 18
5.14 TNL Congestion Indication . 19
6 Frame structure and coding . 19
6.1 General . 19
6.1.1 General principles for the coding . 20
6.2 Data frames . 20
6.2.1 Introduction. 20
6.2.2 UL DATA FRAME . 21
6.2.2.1 UL DATA FRAME FOR DCH . 21
6.2.2.2 UL DATA FRAME FOR E-DCH TYPE 1 . 23
6.2.2.3 UL DATA FRAME FOR E-DCH TYPE 2 . 24
6.2.3 DL DATA FRAME . 26
6.2.4 Coding of information elements in data frames . 28
6.2.4.1 Header CRC . 28
6.2.4.2 Frame Type (FT) . 28
6.2.4.3 Connection Frame Number (CFN) . 28
6.2.4.4 Transport Format Indicator (TFI) . 28
6.2.4.5 Quality Estimate (QE) . 28
6.2.4.6 Transport Block (TB) . 29
6.2.4.7 CRC indicator (CRCI). 29
ETSI
3GPP TS 25.427 version 11.0.0 Release 11 4 ETSI TS 125 427 V11.0.0 (2012-11)
6.2.4.8 Payload CRC . 29
6.2.4.9 Spare Extension . 29
6.2.4.10 Subframe Number . 29
6.2.4.11 Number of HARQ Retransmissions, NHR . 30
6.2.4.12 Number of Subframes . 30
6.2.4.13 Number of MAC-es PDUs . 30
6.2.4.14 Data Description Indicator, DDI . 30
6.2.4.15 Number of MAC-d PDUs, N. 30
6.2.4.16 FSN – Frame Sequence Number . 30
6.2.4.17 Number of MAC-is PDUs . 31
6.2.4.18 User Buffer size . 31
6.2.4.19 Number of MAC-is SDU in frame . 31
6.2.4.20 MAC-is PDU descriptor . 31
6.2.4.21 UL Multiplexing Information (UL Mux Info)[FDD] . 31
6.2.4.22 UL CLTD Removal (CLTD-R)[FDD] . 31
6.3 Control frames . 32
6.3.1 Introduction. 32
6.3.2 Header structure of the control frames . 32
6.3.2.1 Frame CRC . 32
6.3.2.2 Frame Type (FT) . 32
6.3.2.3 Control Frame Type . 32
6.3.3 Payload structure and information elements . 33
6.3.3.1 TIMING ADJUSTMENT . 33
6.3.3.1.1 Payload structure . 33
6.3.3.1.2 CFN . 33
6.3.3.1.3 Time of Arrival (ToA) . 33
6.3.3.1.4 Spare Extension . 34
6.3.3.2 DL SYNCHRONISATION . 34
6.3.3.2.1 Payload structure . 34
6.3.3.2.2 CFN . 34
6.3.3.2.3 Spare Extension . 34
6.3.3.3 UL SYNCHRONISATION . 34
6.3.3.3.1 Payload structure . 34
6.3.3.3.2 CFN . 35
6.3.3.3.3 Time of Arrival (ToA) . 35
6.3.3.3.4 Spare Extension . 35
6.3.3.4 OUTER LOOP POWER CONTROL [FDD, 1.28Mcps TDD] . 35
6.3.3.4.1 Payload structure . 35
6.3.3.4.2 SIR Target . 36
6.3.3.4.3 Spare Extension . 36
6.3.3.4.4 UL Mux Info . 36
6.3.3.5 DL NODE SYNCHRONISATION . 36
6.3.3.5.1 Payload structure . 36
6.3.3.5.2 T1 . 36
6.3.3.5.3 Spare Extension . 37
6.3.3.6 UL NODE SYNCHRONISATION . 37
6.3.3.6.1 Payload structure . 37
6.3.3.6.2 T1 . 37
6.3.3.6.3 T2 . 38
6.3.3.6.4 T3 . 38
6.3.3.6.5 Spare Extension . 38
6.3.3.7 RX TIMING DEVIATION [3.84 Mcps and 7.68Mcps TDD] . 38
6.3.3.7.1 Payload structure . 38
6.3.3.7.2 Rx Timing Deviation [3.84 Mcps TDD] . 39
6.3.3.7.2A Rx Timing Deviation [7.68 Mcps TDD] . 39
6.3.3.7.2B E-RUCCH Flag . 39
6.3.3.7.3 Spare Extension . 39
6.3.3.7.4 CFN . 39
6.3.3.7.5 New IE Flags . 39
6.3.3.8 DSCH TFCI SIGNALLING [FDD] . 40
6.3.3.8.1 Payload structure . 40
6.3.3.8.2 TFCI (field 2) . 40
ETSI
3GPP TS 25.427 version 11.0.0 Release 11 5 ETSI TS 125 427 V11.0.0 (2012-11)
6.3.3.8.3 Spare Extension . 40
6.3.3.8.4 CFN . 40
6.3.3.9 RADIO INTERFACE PARAMETER UPDATE [FDD] . 40
6.3.3.9.1 Payload structure . 40
6.3.3.9.2 Radio Interface Parameter Update flags . 41
6.3.3.9.3 TPC Power Offset (TPC PO) . 42
6.3.3.9.4 Spare Extension . 42
6.3.3.9.4A CFN . 42
6.3.3.9.5 DPC Mode . 42
6.3.3.9.6 TFCI Power Offset (TFCI PO) . 42
6.3.3.9.7 TFCI Power Offset for primary cell (TFCI PO_primary) . 42
6.3.3.9.8 Multiple RL Sets Indicator . 42
6.3.3.9.9 Maximum UE TX Power . 42
6.3.3.10 TIMING ADVANCE [3.84Mcps and 7.68 Mcps TDD] . 43
6.3.3.10.1 Payload structure . 43
6.3.3.10.2 CFN . 44
6.3.3.10.3 TA [3.84 Mcps] . 44
6.3.3.10.3A TA [7.68 Mcps] . 44
6.3.3.10.4 Spare Extension . 44
6.3.3.10.5 New IE Flags [7.68Mcps TDD] . 44
6.3.3.11 TNL CONGESTION INDICATION . 44
6.3.3.11.1 Payload structure . 44
6.3.3.11.2 Congestion Status . 45
6.3.3.11.3 Spare Extension . 45
7 Handling of Unknown, Unforeseen and Erroneous Protocol Data . 45
7.1 General . 45
7.2 Error detection . 45
7.2.1 CRC Calculation . 45
7.2.1.1 Relation between input and output of the Cyclic Redundancy Check . 46
Annex A (informative): Change history . 47
History . 49

ETSI
3GPP TS 25.427 version 11.0.0 Release 11 6 ETSI TS 125 427 V11.0.0 (2012-11)
Foreword
rd
This Technical Specification (TS) has been produced by the 3 Generation Partnership Project (3GPP).
The contents of the present document are subject to continuing work within the TSG and may change following formal
TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an
identifying change of release date and an increase in version number as follows:
Version x.y.z
where:
x the first digit:
1 presented to TSG for information;
2 presented to TSG for approval;
3 or greater indicates TSG approved document under change control.
y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,
updates, etc.
z the third digit is incremented when editorial only changes have been incorporated in the document.
ETSI
3GPP TS 25.427 version 11.0.0 Release 11 7 ETSI TS 125 427 V11.0.0 (2012-11)
1 Scope
The present document shall provide a description of the UTRAN Iur and Iub interfaces user plane protocols for
Dedicated Transport Channel data streams as agreed within the TSG-RAN working group 3.
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including
a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same
Release as the present document.
[1] 3GPP TS 25.301: "Radio interface protocol architecture".
[2] 3GPP TS 25.401: "UTRAN overall description".
[3] 3GPP TS 25.302: "Services provided by the physical layer".
[4] 3GPP TS 25.433: "UTRAN Iub interface Node B Application Part (NBAP) signalling".
[5] 3GPP TS 25.402: "Synchronisation in UTRAN, Stage 2".
[6] 3GPP TS 25.423: "UTRAN Iur interface Radio Network Subsystem Application Part (RNSAP)
signalling".
[7] 3GPP TS 25.133: 'Requirements for support of radio resource management (FDD)'.
[8] 3GPP TS 25.123: 'Requirements for support of radio resource management (TDD)'.
[9] 3GPP TS 25.212: "Multiplexing and channel coding (FDD)".
[10] 3GPP TS 25.222: "Multiplexing and channel coding (TDD)".
[11] 3GPP TS 25.224: "Physical layer procedures (TDD)".
[12] 3GPP TS 25.214: "Physical layer procedures (FDD)".
[13] 3GPP TS 25.319: 'Enhanced uplink; Overall description; Stage 2'
[14] 3GPP TS 25.101: 'User Equipment (UE) radio transmission and reception (FDD)'
[15] 3GPP TS 25.331: 'Radio Resource Control (RRC); Protocol Specification'
[16] 3GPP TS 25.321: 'Medium Access Control (MAC) protocol specification'
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
Transport Bearer: service provided by the transport layer and used by frame protocol for the delivery of FP PDU
ETSI
3GPP TS 25.427 version 11.0.0 Release 11 8 ETSI TS 125 427 V11.0.0 (2012-11)
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
BER Bit Error Rate
CCTrCH Coded Composite Transport Channel
CFN Connection Frame Number
CRC Cyclic Redundancy Checksum
CRCI CRC Indicator
DCH Dedicated Transport Channel
DL Downlink
DPC Downlink Power Control
DRNC Drift RNC
DSCH Downlink Shared Channel
DTX Discontinuous Transmission
E-DCH Enhanced DCH
FP Frame Protocol
FT Frame Type
HARQ Hybrid ARQ
LTOA Latest Time of Arrival
PC Power Control
PDU Protocol Data Unit
PO Power Offset
QE Quality Estimate
RL Radio Link
SIR Signal-to-Interference Ratio
SRNC Serving RNC
TB Transport Block
TBS Transport Block Set
TFI Transport Format Indicator
TFCI Transport Format Combination Indicator
ToA Time of Arrival
ToAWE Time of Arrival Window Endpoint
ToAWS Time of Arrival Window Startpoint
TPC Transmit Power Control
TTI Transmission Time Interval
UE User Equipment
UL Uplink
3.3 Specification Notations
For the purposes of the present document, the following notations apply:
[FDD] This tagging of a word indicates that the word preceding the tag "[FDD]" applies only to FDD.
This tagging of a heading indicates that the heading preceding the tag "[FDD]" and the section
following the heading applies only to FDD.
[TDD] This tagging of a word indicates that the word preceding the tag "[TDD]" applies only to TDD,
including 7.68 Mcps TDD, 3.84Mcps TDD and 1.28Mcps TDD. This tagging of a heading
indicates that the heading preceding the tag "[TDD]" and the section following the heading applies
only to TDD, including 7.68Mcps TDD, 3.84Mcps TDD and 1.28Mcps TDD.
[7.68Mcps TDD] This tagging of a word indicates that the word preceding the tag "[7.68Mcps TDD]" applies only
to 7.68Mcps TDD. This tagging of a heading indicates that the heading preceding the tag
"[7.68Mcps TDD]" and the section following the heading applies only to 7.68Mcps TDD.
[3.84Mcps TDD] This tagging of a word indicates that the word preceding the tag "[3.84Mcps TDD]" applies only
to 3.84Mcps TDD. This tagging of a heading indicates that the heading preceding the tag
"[3.84Mcps TDD]" and the section following the heading applies only to 3.84Mcps TDD.
ETSI
3GPP TS 25.427 version 11.0.0 Release 11 9 ETSI TS 125 427 V11.0.0 (2012-11)
[1.28Mcps TDD] This tagging of a word indicates that the word preceding the tag "[1.28Mcps TDD]" applies only
to 1.28Mcps TDD. This tagging of a heading indicates that the heading preceding the tag
"[1.28Mcps TDD]" and the section following the heading applies only to 1.28Mcps TDD.
[FDD - …] This tagging indicates that the enclosed text following the "[FDD - " applies only to FDD.
Multiple sequential paragraphs applying only to FDD are enclosed separately to enable insertion of
TDD specific (or common) paragraphs between the FDD specific paragraphs.
[TDD - …] This tagging indicates that the enclosed text following the "[TDD - " applies only to TDD
including 7.68 Mcps TDD, 3.84Mcps TDD and 1.28Mcps TDD. Multiple sequential paragraphs
applying only to TDD are enclosed separately to enable insertion of FDD specific (or common)
paragraphs between the TDD specific paragraphs.
[7.68Mcps TDD - …] This tagging indicates that the enclosed text following the "[7.68Mcps TDD - " applies only
to 7.68Mcps TDD. Multiple sequential paragraphs applying only to 7.68Mcps TDD are enclosed
separately to enable insertion of FDD and TDD specific (or common) paragraphs between the
7.68Mcps TDD specific paragraphs.
[3.84Mcps TDD - …] This tagging indicates that the enclosed text following the "[3.84Mcps TDD - " applies only
to 3.84Mcps TDD. Multiple sequential paragraphs applying only to 3.84Mcps TDD are enclosed
separately to enable insertion of FDD and TDD specific (or common) paragraphs between the
3.84Mcps TDD specific paragraphs.
[1.28Mcps TDD - …] This tagging indicates that the enclosed text following the "[1.28Mcps TDD – " applies
only to 1.28Mcps TDD. Multiple sequential paragraphs applying only to 1.28Mcps TDD are
enclosed separately to enable insertion of FDD and TDD specific (or common) paragraphs
between the 1.28Mcps TDD specific paragraphs.
Procedure When referring to a procedure in the specification, the Procedure Name is written with the first
letters in each word in upper case characters followed by the word "procedure", e.g. Timing
Adjustment procedure.
Frame When referring to a control or data frame in the specification, the CONTROL/DATA FRAME
NAME is written with all letters in upper case characters followed by the words "control/data
frame", e.g. DL SYNCHRONISATION control frame.
IE When referring to an information element (IE) in the specification, the Information Element Name
is written with the first letters in each word in upper case characters and all letters in Italic font
followed by the abbreviation "IE", e.g. Connection Frame Number IE.
Value of an IE When referring to the value of an information element (IE) in the specification, the "Value" is
written as it is specified in subclause 6.2.4 or 6.3.3 enclosed by quotation marks, e.g. "0" or "255".
4 General aspects
The specification of Iub DCH and E-DCH data streams is also valid for Iur DCH and E-DCH data streams.
The complete configuration of the transport channel is selected by the SRNC and signalled to the Node B via the Iub
and Iur control plane protocols.
The parameters of a transport channel are described in TS 25.301 [1]. Transport channels are multiplexed on the
downlink by the Node B on radio physical channels, and de-multiplexed on the uplink from radio physical channels to
transport channels.
In Iur interface, every set of coordinated transport channels related to one UE context that is communicated over a set of
cells that are macro-diversity combined within Node B or DRNC, is carried on one transport bearer. This means that
there are as many transport bearers as set of coordinated transport channels and Iur DCH data ports for that
communication.
In Iub interface, every set of coordinated transport channels related to one UE context that is communicated over a set
of cells that are macro-diversity combined within Node B is carried on one transport bearer. This means that there are as
many transport bearers as set of coordinated transport channels and Iub DCH data ports for that communication.
ETSI
3GPP TS 25.427 version 11.0.0 Release 11 10 ETSI TS 125 427 V11.0.0 (2012-11)
Bi-directional transport bearers are used.
4.1 DCH and E-DCH FP services
DCH frame protocol provides the following services:
- Transport of TBS across Iub and Iur interface.
- Transport of outer loop power control information between the SRNC and the Node B.
- Support of transport channel synchronisation mechanism.
- Support of node synchronization mechanism.
- [3.84 Mcps TDD and 7.68 Mcps - Transfer of Rx timing deviation from the Node B to the SRNC.]
- Transfer of radio interface parameters from the SRNC to the Node B.
[FDD – E-DCH frame protocol provides the following services:
- Transport of MAC-es or MAC-is PDUs across Iub and Iur interface from Node B to SRNC.
- Transport of outer loop power control information between the SRNC and the Node B.
- Transfer of radio interface parameters from the SRNC to the Node B.
- Transport of network congestion indication from SRNC across Iub and Iur interface.
- Transport of hybrid ARQ information between SRNC and Node B.]
[TDD – E-DCH frame protocol provides the following services:
- Transport of MAC-es or MAC-is PDUs across Iub and Iur interface from Node B to SRNC.
- Transport of outer loop power control information between the SRNC and the Node B.
- Transport of network congestion indication from SRNC across Iub and Iur interface.
- Transport of hybrid ARQ information between SRNC and Node B.]
4.2 Services expected from the Data Transport Network layer
Following service is required from the transport layer:
- Delivery of FP PDU.
In sequence delivery is not required. However, frequent out-of-sequence delivery may impact the performance and
should be avoided.
4.3 Protocol Version
This revision of the specification specifies version 1 of the protocol.
ETSI
3GPP TS 25.427 version 11.0.0 Release 11 11 ETSI TS 125 427 V11.0.0 (2012-11)
5 DCH Frame Protocol procedures
5.1 Data Transfer
5.1.0 General
When there is some data to be transmitted, DCH data frames are transferred every transmission time interval from the
SRNC to the Node B for downlink transfer, and DCH/E-DCH data frames are transferred every transmission time
interval from Node B to the SRNC for uplink transfer. [FDD – For 2 ms Uu TTI and depending on configuration from
higher layers, the uplink E-DCH MAC-es or MAC-is PDU"s from one or more 2ms Uu TTI"s may be bundled into one
E-DCH Data Frame before being transferred at an interval of e.g. 10ms from the Node B to the SRNC.]
An optional error detection mechanism may be used to protect the data transfer if needed. At the transport channel setup
it shall be specified if the error detection on the user data is used.
5.1.1 Uplink for DCH
SRNC
Node B
UL DATA FRAME
Figure 1: Uplink Data Transfer procedure
Two modes can be used for the UL transmission: normal mode and silent mode. The mode is selected by the SRNC
when the transport bearer is setup and signalled to the Node B with the relevant control plane procedure.
- In normal mode, the Node B shall always send an UL DATA FRAME to the RNC for all the DCHs in a set of
coordinated DCHs regardless of the number of Transport Blocks of the DCHs.
- In silent mode and in case only one transport channel is transported on a transport bearer, the Node B shall not
send an UL DATA FRAME to the RNC when it has received a TFI indicating "number of TB equal to 0" for the
transport channel during a TTI.
- In silent mode and in case of coordinated DCHs, when the Node B receives a TFI indicating "number of TB
equal to 0" for all the DCHs in a set of coordinated DCHs, the Node B shall not send an UL DATA FRAME to
the RNC for this set of coordinated DCHs.
For any TTI in which the Node B Layer 1 generated at least one CPHY-Out-of-Sync-IND primitive, the Node B is not
required to send an UL DATA FRAME to the SRNC.
When Node B receives an invalid TFCI, no UL DATA FRAME shall be sent to the SRNC.
5.1.1a Uplink for E-DCH
SRNC
Node B
E-DCH
UL DATA FRAME
Figure 1a: Uplink Data Transfer procedure
ETSI
3GPP TS 25.427 version 11.0.0 Release 11 12 ETSI TS 125 427 V11.0.0 (2012-11)
When a MAC-e or MAC-i PDU is received, it is demultiplexed into MAC-d flows which are then each sent on separate
transport bearers to the RNC using the E-DCH UL DATA FRAME TYPE 1 (MAC-e) or TYPE 2 (MAC-i).
Only silent mode is used, i.e. E-DCH user-plane payload is transmitted using the E-DCH UL DATA FRAME only
when some payload has been successfully received.
[FDD – In case of Multi Cell E-DCH operation two transport bearer modes can be used for the E-DCH payload
transmission: separate Iub transport bearer mode and E-DCH UL flow multiplexing mode. The mode is selected by the
SRNC when the RL on secondary UL frequency is setup and signalled to the Node B with the relevant control plane
procedure.
- In separate Iub transport bearer mode, the Node B shall send each MAC-d flow received in cells of the different
UL frequencies (primary and secondary) on separate transport bearers, one per frequency, to the RNC using the
E-DCH UL DATA FRAME TYPE 2 (MAC-i).
- In E-DCH UL flow multiplexing mode, the Node B shall send the MAC-d flows received on all UL frequencies
(primary as well as secondary) on one transport bearer to the RNC using the E-DCH UL DATA FRAME TYPE
2 (MAC-i).]
[1.28Mcps TDD – In case of multiple carriers E-DCH operation two transport bearer modes can be used for the E-DCH
payload transmission: separate Iub transport bearer mode and E-DCH UL flow multiplexing mode. The mode is
selected by the SRNC when the RL is setup and signalled to the Node B with the relevant control plane procedure.
- In separate Iub transport bearer mode, the Node B shall send each MAC-d flow received in the different
frequencies on separate transport bearers, one per frequency, to the RNC using the E-DCH UL DATA FRAME
TYPE 2 (MAC-i).
- In E-DCH UL flow multiplexing mode, the Node B shall send one MAC-d flow received on all frequencies on
one transport bearer to the RNC using the E-DCH UL DATA FRAME TYPE 2 (MAC-i).]
5.1.2 Downlink
Node B SRNC
DL DATA FRAME
Figure 2: Downlink Data Transfer procedure
The Node B shall only consider a transport bearer synchronised after it has received at least one DL DATA FRAME on
this transport bearer before LTOA (TS 25.402 [5]).
The Node B shall consider the DL user plane of a certain RL synchronised once all transport bearers established to
carry DCH DL DATA FRAMEs included in the CCTrCH for this RL are considered as synchronised. Once
synchronised, the Node B shall assume the DL user plane for this Radio Link stays synchronised as long as the Radio
Link exists, even if transport bearers are added (see 5.10.2), replaced (see subclause 5.10.1), or removed. When a RL
established through the Radio Link Addition procedure (TS 25.433 [4] TS 25.423 [6]) is combined with a RL whose DL
user plane is considered as synchronised, the Node B shall consider the DL user plane of this newly established RL as
synchronised.
[FDD - The Node B shall transmit on the DL DPDCH(s) of a certain RL only when the DL user plane of this RL is
considered synchronised.]
[TDD – The Node B shall transmit special bursts on the DL DPCH as per TS 25.224 [11], until the DL user plane is
considered synchronised].
When the DL user plane is considered synchronised and the Node B does not receive a valid DL DATA FRAME in a
TTI, it assumes that there is no data to be transmitted in that TTI for this transport channel, and shall act as one of the
following cases:
ETSI
3GPP TS 25.427 version 11.0.0 Release 11 13 ETSI TS 125 427 V11.0.0 (2012-11)
- [TDD – If the Node B receives no valid DL DATA FRAMEs for any transport channel assigned to a UE it shall
assume DTX and transmit special bursts as per TS 25.224 [11]].
- If the Node B is aware of a TFI value corresponding to zero bits for this transport channel, this TFI is assumed.
If the TFS contains both a TFI corresponding to "TB length equal to 0 bits" and a TFI corresponding to "number
of TB equal to 0", the Node B shall assume the TFI corresponding to "number of TB equal to 0". When
combining the TFI's of the different transport channels, a valid TFCI might result and in this case data s
...