Content for TS 25.433 Word version: 18.0.0

3.1 Definitions 3.2 Symbols 3.3 Abbreviations 4.1 Procedure Specification Principles 4.2 Forwards and Backwards Compatibility 4.3 Specification Notations 5.1 Parallel Transactions
...

1 Scope p. 26

The present document specifies the radio network layer signalling protocol called Node B Application Part (NBAP) specification to be used for Control Plane over Iub Interface.

2 References p. 26

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.426: "UTRAN Iur and Iub Interface Data Transport & Transport Signalling for DCH Data Streams".

[3]

CCITT Recommendation X.731 (1992-01): "Information Technology - Open Systems Interconnection - Systems Management: State Management function".

[4]

TS 25.215: "Physical layer; Measurements (FDD)".

[5]

TS 25.225: "Physical layer; Measurements (TDD)".

[6]

TS 25.430: "UTRAN Iub General Aspect and Principle".

[7]

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

[8]

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

[9]

TS 25.213: "Spreading and modulation (FDD)".

[10]

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

[11]

ITU T Recommendation X.691, (2002-07): "Information technology - ASN.1 encoding rules - Specification of Packed Encoding Rules (PER)".

[12]

ITU T Recommendation X.680, (2002-07): "Information Technology - Abstract Syntax Notation One (ASN.1):Specification of basic notation".

[13]

ITU T Recommendation X.681, (2002-07): "Information Technology - Abstract Syntax Notation One (ASN.1): Information object specification".

[14]

TS 25.104: "UTRA (BS) FDD; Radio Transmission and Reception".

[15]

TS 25.105: "UTRA (BS) TDD; Radio Transmission and Reception".

[16]

TS 25.427: "UTRAN Iur/Iub Interface User Plane Protocol for DCH Data Stream".

[17]

TS 25.402: "Synchronisation in UTRAN Stage2".

[18]

TS 25.331: "RRC Protocol Specification".

[19]

TS 25.221: "Physical channels and mapping of transport channels onto physical channels[TDD]".

[20]

TS 25.223: "Spreading and modulation (TDD)".

[21]

TS 25.224: "Physical Layer Procedures (TDD)".

[22]

TS 25.133: "Requirements for support of Radio Resource management (FDD)".

[23]

TS 25.123: "Requirements for support of Radio Resource management (TDD)".

[24]

TS 25.435: "UTRAN Iub Interface: User Plane Protocols for Common Transport Channel Data Streams".

[25]

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

[26]

TR 25.921: (version.7.0.0) "Guidelines and Principles for Protocol Description and Error Handling".

[27]

ICD-GPS-200: "Navstar GPS Space Segment/Navigation User Interface".

[28]

RTCM-SC104: "RTCM Recommended Standards for Differential GNSS Service (v.2.2)".

[29]

RFC 2460 (1998-12): "Internet Protocol, Version 6 (IPv6) Specification".

[30]

RFC 768 (1980-08): "User Datagram Protocol".

[31]

TS 25.434: "UTRAN Iub Interface Data Transport & Transport Signalling for Common Transport Channel Data Streams ".

[32]

TS 25.321: "MAC protocol specification".

[33]

TS 25.306: "UE Radio Access capabilities".

[34]

TS 25.222: "Multiplexing and Channel Coding (TDD)".

[35]

RFC 2474 (1998-12): "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers".

[36]

RFC 2475 (1998-12): "An Architecture for Differentiated Services".

[37]

TS 25.304: "User Equipment (UE) procedures in idle mode and procedures for cell reselection in connected mode".

[38]

TS 25.319: "Enhanced Uplink; Overall description; Stage 2".

[39]

Galileo OS Signal in Space ICD (OS SIS ICD), Issue 1.2. February 2014, European Union.

[40] Void.

[41]

RFC 3376 (2002-12): "Internet Group Management Protocol, Version 3".

[42]

RFC 3810 (2004-06): "Multicast Listener Discovery Version 2 (MLDv2) for IPv6".

[43]

IS-GPS-200, Revision D, Navstar GPS Space Segment/Navigation User Interfaces, March 7th, 2006.

[44]

IS-GPS-705, Navstar GPS Space Segment/User Segment L5 Interfaces, (2005-09-22).

[45]

IS-GPS-800, Navstar GPS Space Segment/User Segment L1C Interfaces, (2008-03-31).

[46]

Specification for the Wide Area Augmentation System (WAAS), US Department of Transportation, Federal Aviation Administration, DTFA01-96-C-00025, 2001.

[47]

IS-QZSS, Quasi Zenith Satellite System Navigation Service Interface Specifications for QZSS, Ver.1.0, (2008-06-17).

[48]

Global Navigation Satellite System GLONASS Interface Control Document, Version 5, 2002.

[49]

TS 25.308: "High Speed Downlink Packet Access (HSDPA); Overall description; Stage 2"

[50]

TS 36.133: "Requirements for support of radio resource management".

[51]

BDS-SIS-ICD-2.0: "BeiDou Navigation Satellite System Signal In Space Interface Control Document Open Service Signal (Version 1.0)", December 2013.

[52]

TS 25.300: "Universal Terrestrial Radio Access Network (UTRAN); General description; Stage 2".

3 Definitions, Symbols and Abbreviations p. 28

3.1 Definitions p. 28

For the purposes of the present document, the following terms and definitions apply.

CRNC Communication Context:

The CRNC Communication Context contains the necessary information for the CRNC for communication with a specific UE. The CRNC Communication Context is identified by the CRNC Communication Context ID.

Elementary Procedure:

The NBAP protocol consists of Elementary Procedures (EPs). An Elementary Procedure is a unit of interaction between the CRNC and the Node B.

An EP consists of an initiating message and possibly a response message.

Two kinds of EPs are used:

Class 1: Elementary Procedures with response (success or failure).
Class 2: Elementary Procedures without response.

For Class 1 EPs, the types of responses can be as follows:

Successful

A signalling message explicitly indicates that the elementary procedure has been successfully completed with the receipt of the response.

Unsuccessful

A signalling message explicitly indicates that the EP failed.

Class 2 EPs are considered always successful.

Node B Communication Context:

The Node B Communication Context contains the necessary information for the Node B for communication with a specific UE. The Node B Communication Context is created by the Radio Link Setup procedure and deleted by the Radio Link Deletion procedure when deleting the last Radio Link within the Node B Communication Context. The Node B Communication Context is identified by the Node B Communication Context ID.

Prepared Reconfiguration:

A Prepared Reconfiguration exists when the Synchronised Radio Link Reconfiguration Preparation procedure has been completed successfully. The Prepared Reconfiguration does not exist anymore only after either of the procedures Synchronised Radio Link Reconfiguration Commit or Synchronised Radio Link Reconfiguration Cancellation has been completed. In particular, the Prepared Reconfiguration still exists if the object (e.g. Radio Link) concerned by the Synchronised Radio Link Reconfiguration (e.g. in the case of an HS-DSCH Setup) is removed, but the Node B Communication Context still exists.

3.2 Symbols p. 28

Void.

3.3 Abbreviations p. 29

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

A-GPS

Assisted GPS

AICH

Acquisition Indicator Channel

ALCAP

Access Link Control Application Part

ASN.1

Abstract Syntax Notation One

BCCH

Broadcast Control Channel

BDS

BeiDou Navigation Satellite System

CCPCH

Common Control Physical Channel

CFN

Connection Frame Number

CLTD

Closed Loop Transmit Diversity

Compressed Mode

CPICH

Common Pilot Channel

CRNC

Controlling Radio Network Controller

DBDS

Differential BDS

DCH

Dedicated Channel

DGANSS

Differential GANSS

DGPS

Differential GPS

Downlink

DPCCH

Dedicated Physical Control Channel

DPCH

Dedicated Physical Channel

DPDCH

Dedicated Physical Data Channel

DSCH

Downlink Shared Channel

E-AGCH

E-DCH Absolute Grant Channel

E-DCH

Enhanced UL DCH

EGNOS

European Geostationary Navigation Overlay Service

E-HICH

E-DCH HARQ Acknowledgement Indicator Channel

E-PUCH

Enhanced Uplink Physical Channel (TDD only)

E-RNTI

E-DCH RNTI

E-RUCCH

E-DCH Random Access Uplink Control Channel (TDD only)

E-TFCI

E-DCH Transport Format Combination Indicator

E-UCCH

E-DCH Uplink Control Channel (TDD only)

FACH

Forward Access Channel

FDD

Frequency Division Duplex

F-DPCH

Fractional DPCH

Frame Protocol

FPACH

Fast Physical Access Channel (TDD only)

F-TPICH

Fractional Transmitted Precoding Indicator Channel

GAGAN

GPS Aided Geo Augmented Navigation

GANSS

Galileo and Additional Navigation Satellite Systems

GLONASS

GLObal'naya NAvigatsionnaya Sputnikovaya Sistema (Engl.: Global Navigation Satellite System)

GNSS

Global Navigation Satellite System

GPS

Global Positioning System

HSDPA

High Speed Downlink Packet Access

HS-DSCH

High Speed Downlink Shared Channel

HS-PDSCH

High Speed Physical Downlink Shared Channel

HS-SCCH

High Speed Shared Control Channel

HS-SICH

High Speed Shared Information Channel

ICD

Interface Control Document

IMB

Integrated Mobile Broadcast

Internet Protocol

IPDL

Idle Periods in the DownLink

ISCP

Interference Signal Code Power

Layer 1

Layer 2

MBMS

Multimedia Broadcast Multicast Service

MBSFN

MBMS over a Single Frequency Network

MFN

Multicast Frame Number

MIB

Master Information Block

MICH

MBMS Notification Indicator Channel

MIMO

Multiple Input Multiple Output

MSAS

Multi-functional Satellite Augmentation System

NAICS

Network Assisted Interference Cancellation and Suppression

NBAP

Node B Application Part

MBMS Notification Indicator

O&M

Operation and Maintenance

PCCPCH

Primary Common Control Physical Channel

PCH

Paging Channel

PDSCH

Physical Downlink Shared Channel

PICH

Paging Indication Channel

PLCCH

Physical Layer Common Control Channel

PUSCH

Physical Uplink Shared Channel

QZSS

Quasi-Zenith Satellite System

RACH

Random Access Channel

Radio Link

RLS

Radio Link Set

RNC

Radio Network Controller

RRC

Radio Resource Control

Scheduling Block

SBAS

Satellite Based Augmentation System

SCCPCH

Secondary Common Control Physical Channel

SCH

Synchronisation Channel

SCTD

Space Code Transmit Diversity

S-DPCCH

Secondary Dedicated Physical Control Channel

SIB

System Information Block

SRNC

Serving Radio Network Controller

STTD

Space Time Transmit Diversity

TDD

Time Division Duplex

TFC

Transport Format Combination

TFCI

Transport Format Combination Indicator

TFCS

Transport Format Combination Set

TFS

Transport Format Set

TPC

Transmit Power Control

TSTD

Time Switched Transmit Diversity

UARFCN

UTRA Absolute Radio Frequency Channel Number

UDP

User Datagram Protocol

User Equipment

Uplink

UMTS

Universal Mobile Telecommunications System

USCH

Uplink Shared Channel

UTC

Universal Coordinated Time

UTRA

Universal Terrestrial Radio Access

UTRAN

Universal Terrestrial Radio Access Network

WAAS

Wide Area Augmentation System

4 General p. 30

4.1 Procedure Specification Principles p. 30

The principle for specifying the procedure logic is to specify the functional behaviour of the Node B exactly and completely. The CRNC functional behaviour is left unspecified. The Reset procedure is an exception from this principle.

The following specification principles have been applied for the procedure text in subclause 8:

The procedure text discriminates between:
1. Functionality which "shall" be executed
  The procedure text indicates that the receiving node "shall" perform a certain function Y under a certain condition. If the receiving node supports procedure X but cannot perform functionality Y requested in the REQUEST message of a Class 1 EP, the receiving node shall respond with the message used to report unsuccessful outcome for this procedure, containing an appropriate cause value.
2. Functionality which "shall, if supported" be executed
  The procedure text indicates that the receiving node "shall, if supported," perform a certain function Y under a certain condition. If the receiving node supports procedure X, but does not support functionality Y, the receiving node shall proceed with the execution of the EP, possibly informing the requesting node about the not supported functionality.
Any required inclusion of an optional IE in a response message is explicitly indicated in the procedure text. If the procedure text does not explicitly indicate that an optional IE shall be included in a response message, the optional IE shall not be included. For requirements on including Criticality Diagnostics IE, see section 10. For examples on how to use the Criticality Diagnostics IE, see Annex C.

4.2 Forwards and Backwards Compatibility p. 31

The forwards and backwards compatibility of the protocol is assured by a mechanism in which all current and future messages, and IEs or groups of related IEs, include Id and criticality fields that are coded in a standard format that will not be changed in the future. These parts can always be decoded regardless of the standard version.

4.3 Specification Notations p. 31

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

[3.84Mcps TDD IMB -…]

This tagging of a word indicates that the word preceding the tag "[3.84Mcps TDD IMB]" applies only to 3.84Mcps TDD IMB. This tagging of a heading indicates that the heading preceding the tag "[3.84Mcps TDD IMB]" and the section following the heading applies only to 3.84Mcps TDD IMB.

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.

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 written as it is specified in subclause 9.2 enclosed by quotation marks, e.g. "Abstract Syntax Error (Reject)".

5 NBAP Services p. 32

5.1 Parallel Transactions p. 32

Unless explicitly indicated in the procedure description, at any instance in time one protocol peer shall have a maximum of one ongoing dedicated NBAP procedure related to a certain Node B Communication Context.

6 Services Expected from Signalling Transport p. 32

NBAP requires an assured in-sequence delivery service from the signalling bearer, and notification if the assured in-sequence delivery service is no longer available.