Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 25.402  Word version:  16.0.0

Top   Top   None   None   Next
1…   4…

 

1  ScopeWord‑p. 6

The present document constitutes the stage 2 specification of different synchronisation mechanisms in UTRAN and on Uu.

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]
TS 25.401: "UTRAN overall description".
[2]
TS 25.423: "UTRAN Iur interface Radio Network Subsystem Application Part (RNSAP) signalling".
[3]
TS 25.433: "UTRAN Iub interface Node B Application Part (NBAP) signalling".
[4]
TS 25.435: "UTRAN Iub interface user plane protocols for Common Transport Channel data streams".
[5]
TS 25.427: "UTRAN Iub/Iur Interface user plane protocol for DCH data streams".
[6]
TIA/EIA 422 B: "Electrical characteristics of balanced voltage digital interface circuits".
[7]
TS 25.411: "UTRAN Iu interface layer 1".
[8]
TS 25.421: "UTRAN Iur interface layer 1".
[9]
TS 25.431: "UTRAN Iub interface layer 1".
[10]
TS 25.104: "Base Station (BS) radio transmission and reception (FDD)".
[11]  Void.
[12]
TS 25.223: "Spreading and modulation (TDD)".
[13]
TS 25.215: "Physical layer; Measurements (FDD)".
[14]
TS 25.225: "Physical layer; Measurements (TDD)".
[15]
TS 25.123: "Requirements for support of radio resource management (TDD)".
[16]
TS 25.224: "Physical layer procedures (TDD)".
[17]
TS 25.105: "Base Station (BS) radio transmission and reception (TDD)".
[18]
ITU T Recommendation G.811 (1997-09): "Timing Characteristics of Primary Reference Clocks".
[19]
ITU T Recommendation G.812 (1998-06): "Timing Requirements of Slave Clocks suitable for use as Node Clocks in Synchronization Network".
[20]
ITU T Recommendation G.813 (1996-08): "Timing Characteristics of SDH equipment slave clocks (SEC)".
[21]
ETSI EN 300 462-4-1(1998-03): "Transmission and Multiplexing (TM); Generic requirements for synchronization networks; Part 4-1: Timing characteristics of slave clocks suitable for synchronization supply to Synchronous Digital Hierarchy (SDH) and Plesiochronous Digital Hierarchy (PDH) equipment".
[22]
ETSI EN 300 462-5-1 (1996-09): "Transmission and Multiplexing (TM); Generic requirements for synchronization networks; Part 5-1: Timing characteristics of slave clocks suitable for operation in Synchronous Digital Hierarchy (SDH) equipment".
[23]
ETSI EN 300 462-7-1 (2001-04): "Transmission and Multiplexing (TM); Generic requirements for synchronization networks; Part 7-1: Timing characteristics of slave clocks suitable for synchronisation supply to equipment in local node applications".
[24]
TS 25.212: "Multiplexing and channel coding (FDD)".
[25]
TS 25.222: "Multiplexing and channel coding (TDD)".
[26]
TS 25.321: "Medium Access Control (MAC) protocol specification".
[27]
TS 25.415: "UTRAN Iu interface user plane protocols".
Up

3  Definitions, symbols and abbreviationsWord‑p. 7

3.1  Definitions

Network Synchronisation:
generic concept that depicts the way of distributing a common frequency to all elements in a network
Reference Timing Signal:
timing signal of specified performance that can be used as a timing source for a slave clock
Holdover mode:
operating condition of a clock which has lost its controlling reference input and is using stored data, acquired while in locked operation (that is while controlled by an external input reference), to control its output. The stored data are used to control phase and frequency variations, allowing the locked condition to be reproduced within specifications.
Up

3.2  Symbols

No special symbols are defined in this document.

3.3  Abbreviations

For the purposes of the present document, the following abbreviations apply:
ACK
(time alignment) acknowledgement
BFN
Node B Frame Number (counter)
CFN
Connection Frame Number (counter)
CH
Channel
CN
Core Network
CPICH
Common Pilot Channel
CRNC
Controlling RNC
DL
Down Link
DCH
Dedicated Channel
DOFFFDD
FDD Default DPCH Offset value
DOFFTDD
TDD Default DPCH Offset value
DPCH
Dedicated Physical Channel
DPCCH
Dedicated Physical Control Channel
DRNC
Drift RNC
DSCH
Downlink Shared Channel
FACH
Forward Access Channel
FDD
Frequency Division Duplex
F-DPCH
Fractional DPCH
GPS
Global Positioning System
HO
Handover
IMB
Integrated Mobile Broadcast
LTOA
Latest Time of Arrival
L1
Layer 1
L2
Layer 2
MAC
Medium Access Control
MBMS
Multimedia Broadcast Multicast Service
MBSFN
Multicast/Broadcast over a Single Frequency Network
MCCH
MBMS point-to-multipoint Control Channel
MFN
Multicast Frame Number (counter)
MTCH
MBMS point-to-multipoint Traffic Channel
NACK
(time alignment) negative acknowledgement
PCCPCH
Primary Common Control Physical Channel
PCH
Paging Channel
PDU
Packet Data Unit
PTP
Point-to-Point
PTM
Point-to-Multipoint
PUSCH
Physical Uplink Shared Channel
RAB
Radio Access Bearer
RACH
Random Access Channel
RAN
Radio Access Network
RFN
RNC Frame Number (counter)
RL
Radio Link
RNC
Radio Network Controller
RNS
Radio Network Subsystem
RRC
Radio Resource Control
SAP
Service Access Point
SCH
Synchronisation Channel
SFN
Cell System Frame Number (counter)
SRNC
Serving RNC
SRNS
Serving RNS
TBS
Transport Block Set
TDD
Time Division Duplex
TOA
Time Of Arrival
TOAWE
Time Of Arrival Window Endpoint
TOAWS
Time Of Arrival Window Startpoint
TTI
Time Transmission Interval
UE
User Equipment
UL
Up Link
UMTS
Universal Mobile Telecommunications System
USCH
Uplink Shared CHannel
UTRAN
UMTS Terrestrial Radio Access Network
Up

3.4  Specification Notations |R7|Word‑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 3.84Mcps TDD, 7.68Mcps 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 3.84Mcps TDD, 7.68Mcps TDD and 1.28Mcps 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.
[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.
[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 3.84Mcps TDD, 7.68Mcps 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.
[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.
[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.
Procedure
When referring to an elementary 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. Radio Link Setup procedure.
Message
When referring to a message in the specification, the MESSAGE NAME is written with all letters in upper case characters followed by the word "message", e.g. RADIO LINK SETUP REQUEST message.
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. Transport Format Set IE.
Value of an IE
When referring to the value of an information element (IE) in the specification, the "Value" is enclosed by quotation marks, e.g. "Abstract Syntax Error (Reject)".
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.
Up

Up   Top   ToC