Content for TS 25.435 Word version: 16.0.0

3.1 Definitions 3.2 Abbreviations 3.3 Specification Notations 4.1 Common Transport Channel Data Stream User Plane Protocol Services 4.2 Services expected from the Data Transport Network layer 4.3 Protocol Version
...

1 Scope Word‑p. 8

The present document provides a description of the UTRAN RNC-Node B (Iub) interface user plane protocols for Common 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] Void

[2]

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

[3]

TS 25.302: "Services provided by the Physical Layer".

[4]

TS 25.221: "Physical channels and mapping of transport channels to physical channels (TDD)".

[5]

TS 25.211: "Physical channels and mapping of transport channels onto physical channels (FDD)".

[6]

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

[7] Void

[8]

TS 25.331: "Radio Ressource Control (RRC) protocol specification".

[9]

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

[10]

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

[11]

TS 25.401: "UTRAN overall description".

[12]

TS 25.306: "UE Radio Access capabilities".

[13]

TS 25.427: "UTRAN Iub/Iur interface user plane protocol for DCH data streams".

[14]

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

3 Definitions and abbreviations

3.1 Definitions

For the purposes of the present document, the terms and definitions in TS 25.401 and the following apply:

Transport Connection:

service provided by the transport layer and used by Frame Protocol for the delivery of FP PDU

3.2 Abbreviations Word‑p. 9

For the purposes of the present document, the following abbreviations apply:

CFN

Connection Frame Number

CRC

Cyclic Redundancy Checksum

CRCI

CRC Indicator

DCH

Dedicated Transport Channel

Downlink

DRT

Delay Reference Time

DSCH

Downlink Shared Channel

E-DCH

Enhanced Dedicated Transport Channel

Frame Protocol

FSN

Frame Sequence Number

Frame Type

HSDPA

High Speed Downlink Packet Access

HS-DSCH

High Speed Downlink Shared Channel

MFN

Multicast Frame Number

Power Control

PDSCH

Physical Downlink Shared Channel

PUSCH

Physical Uplink Shared Channel

Quality Estimate

Transport Block

TBS

Transport Block Set

TFI

Transport Format Indicator

TNL

Transport Network Layer

ToA

Time of Arrival

ToAWE

Time of Arrival Window Endpoint

ToAWS

Time of Arrival Window Startpoint

TTI

Transmission Time Interval

Uplink

USCH

Uplink Shared Channel

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.68Mcps 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.68Mcps 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 1.28Mcps 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. Node Synchronisation 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. TIMING ADJUSTMENT control frae.

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. Frame Type 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.7 or 6.3.3 enclosed by quotation marks, e.g. "0" or "255".

4 General aspects Word‑p. 10

4.1 Common Transport Channel Data Stream User Plane Protocol Services

Common transport channel provides the following services:

Transport of TBS between the Node B and the CRNC for common transport channels.
Support of transport channel synchronisation mechanism.
Support of Node Synchronisation mechanism.

4.2 Services expected from the Data Transport Network layer

The following services are expected from the transport layer:

Delivery of Frame Protocol PDUs.

In sequence delivery is not required. However, frequent out-of-sequence delivery may impact the performance and should be avoided.

4.3 Protocol Version Word‑p. 11

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