Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 25.425  Word version:  16.0.0

Top   Top   None   None   Next
1…   5… 
1 Scope  2 References  3 Definitions, symbols and abbreviations  3.1 Definitions  3.2 Symbols  3.3 Abbreviations  3.4 Specification Notations  4 General Aspects  4.1 Common Transport Channel Data Streams 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 shall provide a description of the UTRAN RNS-RNS (Iur) 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]  Void
[3]  Void
[4]  Void
[5]
TS 25.401: "UTRAN overall description".
[6]  Void
[7]
TS 25.321: "Medium Access Control (MAC) protocol specification".
[8]
TS 25.423: "UTRAN Iur Interface RNSAP Signalling".
[9]
TS 25.321: "Medium Access Control (MAC) protocol specification".
[10]
TS 25.224: "Physical layer procedures (TDD)".
Up

3  Definitions, symbols and abbreviations

3.1  Definitions

For the purposes of the present document, the terms and definitions in TS 25.401 and the following apply:
Common Transport Channel: it is defined as a transport channel that is shared by several users i.e. DSCH [TDD], USCH [TDD], RACH, FACH [FDD and 1.28Mcps TDD -, E-DCH for CELL_FACH and Idle] and HS-DSCH.
Transport Connection: service provided by the transport layer and used by Frame Protocol for the delivery of FP PDU

3.2  Symbols

No special symbols are defined in the present document.

3.3  Abbreviations  Word‑p. 9

For the purposes of the present document, the following abbreviations apply:
CFN
Connection Frame Number
CmCH
Common Transport Channel
C-RNC
Controlling Radio Network Controller
CRC
Cyclic Redundancy Checksum
DCH
Dedicated Transport Channel
DL
Downlink
D-RNTI
Drift RNTI
DRT
Delay Reference Time
DSCH
Downlink Shared Channel
E-DCH
Enhanced Dedicated Transport Channel
Extended S-RNTI
Extended Serving RNTI
FACH
Forward Access Channel
FP
Frame Protocol
FT
Frame Type
FSN
Frame Sequence Number
HSDPA
High Speed Downlink Packet Access
HS-DSCH
High Speed Downlink Shared Channel
RACH
Random Access Channel
RNC
Radio Network Controller
RNTI
Radio Network Temporary Identity
SRNC
Serving Radio Network Controller
S-RNTI
Serving RNTI
SSCS
Service Specific Convergence Sublayer
TB
Transport Block
TBS
Transport Block Set
TFI
Transport Format Indicator
TNL
Transport Network Layer
ToA
Time of Arrival
TTI
Transmission Time Interval
UE
User Equipment
UL
Uplink
U-RNTI
UTRAN RNTI
USCH
Uplink Shared Channel
Up

3.4  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 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. FACH Data Transfer 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. FACH FLOW CONTROL 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. Credits 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.5 or 6.3.3 enclosed by quotation marks, e.g. "0" or "255".
Up

4  General Aspects  Word‑p. 10

4.1  Common Transport Channel Data Streams User Plane Protocol Services

This subclause describes the services that the User Plane Protocols provide such as data transfer, flow control.

4.1.1  RACH Data Streams User Plane Protocol Services

RACH frame protocol provides the following services:
  • Transport of MAC-c/sh SDUs from the DRNC to the SRNC for RACH common transport channels.

4.1.2  FACH Data Streams User Plane Protocol Services  Word‑p. 11

FACH frame protocol provides the following services:
  • Transport of MAC-c/sh SDUs from the SRNC to the DRNC for FACH common transport channel.
  • Flow Control between MAC-d and MAC-c/sh.

4.1.3  USCH/DSCH Data Streams User Plane Protocol Services [TDD]

[TDD USCH]/DSCH frame protocol provides the following services:
  • Transport of MAC-c/sh SDUs between the SRNC and the DRNC for [TDD USCH] and DSCH common transport channels.
  • Flow Control between MAC-d and MAC-c/sh.

4.1.4  HS-DSCH Data Streams User Plane Protocol Services |R5|

HS-DSCH frame protocol provides the following services:
  • Transport of MAC-d flows between the SRNC and the DRNC for HS-DSCH common transport channels.
  • Flow Control between MAC-d and CRNC HS-DSCH Flow Control.

4.1.5  E-DCH for CELL_FACH and Idle Data Streams User Plane Protocol Services [FDD and 1.28Mcps TDD] |R8|

E-DCH for CELL_FACH and Idle frame protocol provides the following services:
  • Transport of MAC-is PDUs in Cell_FACH state between the DRNC and the SRNC for E-DCH common transport channels.

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

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

Up   Top   ToC