Content for TS 25.427 Word version: 18.0.0

3.1 Definitions 3.2 Abbreviations 3.3 Specification Notations 4.1 DCH and E-DCH FP services 4.2 Services expected from the Data Transport Network layer 4.3 Protocol Version
...

1 Scope p. 7

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 p. 7

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]

TS 25.301: "Radio interface protocol architecture".

[2]

TS 25.401: "UTRAN overall description".

[3]

TS 25.302: "Services provided by the physical layer".

[4]

TS 25.433: "UTRAN Iub interface Node B Application Part (NBAP) signalling".

[5]

TS 25.402: "Synchronisation in UTRAN, Stage 2".

[6]

TS 25.423: "UTRAN Iur interface Radio Network Subsystem Application Part (RNSAP) signalling".

[7]

TS 25.133: "Requirements for support of radio resource management (FDD)".

[8]

TS 25.123: "Requirements for support of radio resource management (TDD)".

[9]

TS 25.212: "Multiplexing and channel coding (FDD)".

[10]

TS 25.222: "Multiplexing and channel coding (TDD)".

[11]

TS 25.224: "Physical layer procedures (TDD)".

[12]

TS 25.214: "Physical layer procedures (FDD)".

[13]

TS 25.319: "Enhanced uplink; Overall description; Stage 2"

[14]

TS 25.101: "User Equipment (UE) radio transmission and reception (FDD)"

[15]

TS 25.331: "Radio Resource Control (RRC); Protocol Specification"

[16]

TS 25.321: "Medium Access Control (MAC) protocol specification"

3 Definitions and abbreviations p. 7

3.1 Definitions p. 7

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

3.2 Abbreviations p. 8

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

Downlink

DPC

Downlink Power Control

DRNC

Drift RNC

DSCH

Downlink Shared Channel

DTX

Discontinuous Transmission

E-DCH

Enhanced DCH

Frame Protocol

Frame Type

HARQ

Hybrid ARQ

LTOA

Latest Time of Arrival

Power Control

PDU

Protocol Data Unit

Power Offset

Quality Estimate

Radio Link

SIR

Signal-to-Interference Ratio

SRNC

Serving RNC

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

User Equipment

Uplink

3.3 Specification Notations p. 8

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.

[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.

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 p. 9

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. 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.

Bi-directional transport bearers are used.

4.1 DCH and E-DCH FP services p. 10

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 p. 10

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 p. 10

This revision of the specification specifies version 1 of the protocol.