UMTS RNC ATM Transmission Feature Guide

RNC ATM Transmission (V4)
Feature Guide

Version
V1.00
Date
2014/01/2
Author
Zhao
Zesheng
Reviewer
Fan Pei
Notes
First Edition
2014 ZTE Corporation. All rights reserved.

ZTE CONFIDENTIAL: This document contains proprietary information of ZTE and is not to be disclosed or used
without the prior written permission of ZTE.
Due to update and improvement of ZTE products and technologies, information in this document is subjected to
change without notice.
ZTE Confidential Proprietary
RNC ATM Transmission

(V4)
TABLE OF CONTENTS
Feature Attribute ............................................................................................... 6
2
2.1
2.1.1
2.1.2
2.1.3
2.1.4
2.1.5
2.1.6
2.1.7
2.2
2.3
Overview ............................................................................................................ 6
Feature Introduction ............................................................................................. 6
ZWF22-02-001 ATM Transmission Stack............................................................. 6
ATM Transmission Interfaces............................................................................... 7
ZWF22-02-002 PVC Cross Connection ............................................................... 8
ZWF22-02-003 Dynamic AAL2 Connections ........................................................ 8
ZWF22-02-004 Permanent AAL5 Connections .................................................... 8
ZWF22-02-005 AAL2 Quality of Service separation ............................................. 9
ZWF22-02-006 ATM Link Redundancy ................................................................ 9
License Control .................................................................................................... 9
Correlation with Other Features ......................................................................... 10
3
3.1
3.1.1
3.1.2
3.2
3.2.1
3.2.2
3.2.3
3.2.4
3.2.5
3.2.6
3.3
3.4
3.4.1
3.4.2
3.4.3
3.4.4
3.4.5
3.4.6
3.5
3.5.1
3.6
3.6.1
3.6.2
3.6.3
Technical Description ..................................................................................... 10

ATM Transmission stack .................................................................................... 10
Overview ............................................................................................................ 10
ATM Protocol ..................................................................................................... 14
ATM Transmission Interfaces............................................................................. 23
Implementation of ATM Protocol in RNC ............................................................ 23
Inverse Multiplexing for ATM (IMA) .................................................................... 24
ATM over E1 ...................................................................................................... 35
ATM over T1 ...................................................................................................... 37
ATM over Optical STM-1/OC-3 .......................................................................... 39
ATM over Channelized STM-1/OC-3.................................................................. 44
PVC Cross Connection ...................................................................................... 51
Dynamic AAL2 Connections .............................................................................. 53
Setup Procedure ................................................................................................ 54
Modification Procedure ...................................................................................... 54
Release Procedure ............................................................................................ 55
CID Allocation Policy .......................................................................................... 55
Interconnection with AAL2 Switching Device ...................................................... 56
ALCAP protocol version ..................................................................................... 58
Permanent AAL5 Connections ........................................................................... 58
IP over ATM ....................................................................................................... 60
AAL2 Quality of Service separation .................................................................... 61
Service Category ............................................................................................... 62
Traffic Types ...................................................................................................... 63
Effective Bandwidth of PVC ............................................................................... 64
3.6.4
3.7
Configuration Policy ........................................................................................... 66

ATM Link Redundancy ....................................................................................... 66
4
4.1
4.2
4.3
4.5
4.6
4.7
Parameters....................................................................................................... 67
ZWF22-02-001 ATM Transmission stack Configuration Parameters .................. 67
ZWF22-02-008 Inverse Multiplexing over ATM, IMA Configuration Parameters . 79
ZWF22-02-051 ATM over E1 & ZWF22-02-052 ATM over T1 Configuration
Parameters ........................................................................................................ 83
ZWF22-02-054 ATM over Optical STM-1/OC-3 & ZWF22-02-055 ATM over
Channelized &STM-1/OC-3 Configuration Parameters ...................................... 84
ZWF22-02-003 Dynamic AAL2 Connections Configuration Parameters............. 98
ZWF22-02-004 Permanent AAL5 Connections Configuration Parameters ....... 100
ZWF22-02-006 ATM Link Redundancy Configuration Parameters ................... 101
5
5.1
5.2
Related Counters and Alarms ...................................................................... 103

Related Counters ............................................................................................. 103
Related Alarms ................................................................................................ 105
Abbreviation .................................................................................................. 107
Reference Document..................................................................................... 108
4.4

(V4)
FIGURES
Figure 3-1 ATM protocol stack on Iu-CS interface ..............................................................11
Figure 3-2 ATM protocol stack on Iu-PS interface ..............................................................12
Figure 3-3 ATM protocol stack on Iur interface...................................................................13
Figure 3-4 ATM protocol stack on Iub interface ..................................................................14
Figure 3-5 ATM cell header format.....................................................................................15
Figure 3-6 ATM protocol model ..........................................................................................16
Figure 3-7 Data transmission among layers .......................................................................17
Figure 3-8 Internal architecture of ATM Interface Processor ..............................................23
Figure 3-9 Reference model of IMA sublayer in the ATM protocol hierarchy ......................25
Figure 3-10 Inverse multiplexing and de-multiplexing of ATM cells in IMA group ...............26
Figure 3-11 Multi-link IMA cell transmission .......................................................................26
Figure 3-12 ICP cell format ................................................................................................28
Figure 3-13 IMA frame synchronization mechanism...........................................................30
Figure 3-14 IMA handling of RNC ATM processing board ..................................................34
Figure 3-15 STM-N frame format .......................................................................................40
Figure 3-16 STM-N multiplexing mapping structure ...........................................................43
Figure 3-17 ATM Process Board processing structure .......................................................43
Figure 3-18 E1-to-STM-1 multiplexing process ..................................................................47
Figure 3-19 T1-to-STM-1 multiplexing process ..................................................................48
Figure 3-20 Typical networking ..........................................................................................50
Figure 3-21 ATM over Channelized STM-1/OC-3 implementation......................................50
Figure 3-22 PVC cross connection networking...................................................................51
Figure 3-23 VP/VC switching .............................................................................................52
Figure 3-24 Typical IUR relay Networking ..........................................................................56
Figure 3-25 SAAL protocol stack........................................................................................59
TABLES
Table 2-1 Interfaces applicable to ATM transmission .......................................................... 7
Table 2-2 License Control List ............................................................................................ 9
Table 3-1 Payload type ......................................................................................................15
Table 3-2 Functions of various layers and their respective sub layers ................................17
Table 3-3 Services and related parameters .......................................................................21
Table 3-4 Features of various ATM services ......................................................................22
Table 4-1 Parameters List ..................................................................................................67
Table 4-6 Parameters List ................................................................................................100
Table 4-7 Parameters List ................................................................................................101
Table 5-1 Counter List .....................................................................................................103
Table 5-2 Alarm List .........................................................................................................105

(V4)
Feature Attribute
RNC Version: [ZXUR 9000 RNC (V4.13.10.15)]
Attribute: [Optional]
Related Network Element:
NE Name
Related or Not
MS/UE
BTS/Node B
BSC/RNC
iTC
MSC
MGW
SGSN
GGSN
HLR
Special Requirements
: Related, -: Irrelative
Overview
2.1
Feature Introduction
2.1.1
ZWF22-02-001 ATM Transmission Stack

Asynchronous Transfer Mode (ATM) is a cell-oriented switching and multiplexing
technology that utilizes fixed length packets to carry different types of traffic.
Asynchronous means data sent from each user is not necessarily periodic.
Combining the advantages of circuit switching and packet switching, ATM is capable of
carrying several types of information media and communication services with guaranteed
QoS in a single network.
ATM is adopted as the main protocol for interfaces between UTRAN NEs in 3GPP. ZTE
UMTS supports complete ATM protocol stack on all of the Iub interface, lur interface,
Iu-CS interface and Iu-PS interface.
2.1.2
ATM Transmission Interfaces

As one of the basic transfer modes stipulated in 3GPP R99 and R4 on the RAN, ATM
can be based on various types of physical transmission media. The external ATM
transmission interfaces supported by the RNC include E1, T1 and SDH (STM-1, STM-4
and CSTM-1). E1 and T1 interfaces are used in scenarios with low bandwidth
requirement, for example, NEs are directly connected through lub or lur interfaces.
CSTM-1 is used to implement multiplexing and convergence of several E1/T1 low-speed
links in STM-1 signals. For ATM transmission interfaces, CSTM-1 is basically equal to
E1/T1 interface and primarily used for Iub and Iur interfaces. ATM over STM-1 interface
is used in scenarios with high bandwidth requirement, for example, Iu-CS, and Iu-PS
interfaces. The following Table lists various interfaces applicable to ATM transmission:
Table 2-1
Interfaces applicable to ATM transmission
Feature Name
Applicable Interface
ZWF22-02-008 Inverse
Multiplexing over ATM,
Iub, Iur, Iu-CS, Iu-PS
Iub and Iur interfaces are

commonly used.

commonly used.

commonly used.
Iur, Iu-CS and Iu-PS interfaces

are commonly used.

commonly used.
IMA
ZWF22-02-051 ATM
over E1
ZWF22-02-052 ATM
over T1
ZWF22-02-054 ATM
over Optical
STM-1/OC-3
ZWF22-02-055 ATM
over Channelized
STM-1/OC-3
Remarks

(V4)
2.1.3
ZWF22-02-002 PVC Cross Connection

In scenarios over an ATM network, the RNC needs to terminate and handle cell stream in
Iub, Iur and Iu interface carried on ATM cells as the termination node in the ATM network.
Apart from that, ZTE UMTS RNC can also work as an ATM switch to perform
VC-/VP-granularity switching and forwarding of accessed cell stream and implement
PVC cross connection.
2.1.4
ZWF22-02-003 Dynamic AAL2 Connections

User data is transmitted through AAL2 in the ATM structure on lub, lur and Iu-CS
interfaces and in this case, a control mechanism needs to be established. The ITU-T
Q.2630.1-compliant Access Link Control Application Protocol (ALCAP) provides various
dynamic management functions for AAL2 connection. The basic function of the ALCAP is
to set up and release AAL2 connection between two signaling points, and perform
necessary maintenance and management of path resources of micro cells in the
signaling system. The ALCAP-controlled AAL2 connections will be used as the transport
bearers for the control plane and user plane of the Radio Network Layer (RNL). The
ALCAP may dynamically establish, modify and release these transport bearers.
When there are multiple connections of IU or IUR on the RNC, the point-to-point
connection mode between NEs leads to complicated topology and poor sharing of
transmission resources. RNC keeps AAL2 connections with adjacent NEs via ATM AAL2
switch gateway to reduce the number of physical links between NEs and enhance
sharing of transmission resources. The AAL2 switch gateway can either be an
independently deployed ATM switching device or built in the existing adjacent NEs.
2.1.5
ZWF22-02-004 Permanent AAL5 Connections

According to 3GPP, Iu/Iur and lub interfaces carry their respective control plane signaling
through SAAL-NNI and SAAL-UNI links. The SAAL is divided into a Service Specific part
and a Common Part (CP) by the AAL5 protocol. The access layer of SSCS relates to
services and consists of the Service Specific Coordination Function (SSCF) and the
Service Specific Connection Oriented Protocol (SSCOP). IP over ATM traffic carried on
AAL5 link involves two scenarios for RAN transmission, one is to carry O&M traffic for
Node B in Iub interface, the other is to carry Iu PS data stream.
2.1.6
ZWF22-02-005 AAL2 Quality of Service separation

ZTE UMTS can select varied AAL2 PVC types on lub, lur and Iu-CS interfaces based on
the QoS features of various services to adapt to services with different QoS levels. It can
assign different priorities to services even if they are carried on the same AAL2 PVC. The
scheduling priorities vary with services with different priorities and those with high priority
will be scheduled first to ensure priority transmission of real-time data or time-sensitive
data and assign bandwidth to unstable data services as much as possible.
2.1.7
ZWF22-02-006 ATM Link Redundancy

ZTE UMTS offers several redundancy schemes for both physical and logical ATM link
layers to avoid service failure due to one physical access link fault as well as lub interface
signaling link failure, thus enhancing system reliability and stability.
2.2
License Control
Table 2-2
License Control List
Feature ID
Feature Name
License
Configured
Sales
Control Item
NE
Unit
ZWF22-02-001
ATM Transmission stack
N/A
N/A
N/A
ZWF22-02-002
PVC Cross Connection
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
Dynamic
ZWF22-02-003
Connections
Permanent
ZWF22-02-004
AAL2
AAL5
Connections
AAL2 Quality of Service
ZWF22-02-005
separation
ZWF22-02-006
ATM Link Redundancy

Inverse Multiplexing over
ZWF22-02-008
ATM, IMA
ZWF22-02-051
ATM over E1
N/A
N/A
N/A
ZWF22-02-052
ATM over T1
N/A
N/A
N/A

(V4)
ZWF22-02-054
ATM over Optical

STM-1/OC-3
ZWF22-02-055
N/A
N/A
N/A
N/A
N/A
N/A
ATM over
Channelized
STM-1/OC-3
2.3
Correlation with Other Features

1. Required Features
None
2. Mutually Exclusive Features
None
3. Affected Features
None
Technical Description
3.1
ATM Transmission stack
3.1.1
Overview
According to 3GPP specifications, the ATM protocol stacks on various interfaces are
respectively shown in the following figures. ZTE UMTS is completely 3GPP-compliant.
10
Figure 3-1
Radio
Network
Layer
Radio
Network
Layer
ATM protocol stack on Iu-CS interface
Control Plane
User Plane
RANAP
Iu UP
Transport Network
User Plane
Transport Network
Control Plane
Transport Network
User Plane
Q.2630.1/2
SCCP
Q.2150.1
MTP3B
MTP3B
SSCF-NNI
SSCF-NNI
SSCOP
SSCOP
AAL5
AAL5
AAL2
ATM
ATM
ATM
Physical Layer
11

(V4)
Figure 3-2
Radio
Network
Layer
Radio
Network
Layer
ATM protocol stack on Iu-PS interface
Control Plane
User Plane
RANAP
Iu UP
Transport Network
User Plane
Transport Network
Control Plane
Transport Network
User Plane
SCCP
MTP3B
GTP-U
SSCF-NNI
UDP
SSCOP
IP
AAL5
AAL5
ATM
ATM
Physical Layer
12
Figure 3-3
Radio
Network
Layer
Radio
Network
Layer
ATM protocol stack on Iur interface
Control Plane
User Plane
RNSAP
Iur FP
Transport Network
User Plane
Transport Network
Control Plane
Transport Network
User Plane
Q.2630.1/2
SCCP
Q.2150.1
MTP3B
MTP3B
SSCF-NNI
SSCF-NNI
SSCOP
SSCOP
AAL5
AAL5
AAL2
ATM
ATM
ATM
Physical Layer
13

(V4)
Figure 3-4
Radio
Network
Layer
Radio
Network
Layer
ATM protocol stack on Iub interface
Control Plane
User Plane
NBAP
Iub FP
Transport Network
User Plane
Transport Network
Control Plane
Transport Network
User Plane
Q.2630.1/2
Q.2150.2
SSCF-UNI
SSCF-UNI
SSCOP
SSCOP
AAL5
AAL5
AAL2
ATM
ATM
ATM
Physical Layer
3.1.2
ATM Protocol
The ATM protocol combines the advantages of both circuit switching and packet
switching. ATM protocol has both the feature of circuit switching to support real-time
services, transparent transmission of data, without complicated data handling inside the
network, end-to-end communication protocol; and has the characteristics of packet
switching, such as variable bit rate services, statistical TDM for services transmitted on
links.
3.1.2.1
ATM cell header format

The figure shows the ATM cell header format:
14
Figure 3-5
ATM cell header format
GFC
VPI
VPI
VPI
VCI
VPI
VCI
VCI
VCI
VCI
PTI
CLP
HEC
PAYLOAD
(a) UNI Cell header
VCI
PTI
CL
P
HEC
PAYLOAD
(b) NNI Cell header
An ATM cell header is composed of the following:
Table 3-1
GFC
VPI
Payload type
Generic Flow Control (GFC): 4 bits. It is only used for UNI interface, and is
set to its default value 0000. In the future it may be used for flow control.
Virtual Path Identifier (VPI): 12 bits for NNI and 8 bits for UNI.
Virtual Channel Identifier (VCI): 16 bits. It identifies virtual channels on a
VCI
virtual path. In conjunction with the VPI, the VCI identifies a virtual
connection.
PTI
Payload Type Indicator (PTI): 3 bits. It is used to indicate cell type.

Cell Loss Priority (CLP): One bit. Indicates whether the cell should be
CLP
discarded if it encounters extreme congestion as it moves through the

network. If the CLP bit equals 1, the cell should be discarded in preference
to cells with the CLP bit equal to 0.
Header Error Control (HEC): 8 bits. It can be used to correct the error of bit
HEC
1 in cell header. The HEC is also used for cell delimitation. The cell header
position is identified through the relevance between HEC and first 4 bytes of
the header.
15

(V4)
3.1.2.2
Reference model
The ATM reference model contains a user plane, a control plane and a management
plane.
1.
The user plane is used to transmit user information, including service-related

protocol, data, voice and video information.
2.
The control plane is used to implement call control and connection control. It
establishes, manages and releases calls and connections through signaling
handling.
3.
The management plane provides two functions: Layer management and plane
management. The plane management implements management functions for
the whole system and provides coordination function among all planes. Layer
management implements management functions for resources and parameters
in the protocol entity, and handles the Operation, Administration and
Maintenance (OAM) information stream related to specific layers.
The control plane and user plane are only differentiated in the service layer and AAL.
Figure 3-6
ATM protocol model
Management Plane
User Plane
Control Plane
Application
Application
AAL
SAAL
ATM
PHY
The ATM reference model is composed of such ATM layers as physical layer, ATM layer,
ATM Adaptation Layer (AAL) and higher layer, with data transmission among layers
shown in the following figure.
16
Figure 3-7
Data transmission among layers
AppInfo
AAL-PCI
AALSDU
AAL
48 Byte Info
CELL Header
48 Byte payload
ATM
53 Byte Cell
Physical Layer
53 Byte Cell
Bit Stream
Protocol Control Information (PCI): PCI may contain header and tail.
The table lists the functions of all layers and their respective sub layers:
Table 3-2
Functions of various layers and their respective sub layers
High layer
CS sublayer
Function of high layer

Convergence: That is, to transform service data into CS
data units.
AAL
SAR
Segmentation and reassembly: To segment or reassemble
sublayer
CS data based on cells at this layer.
17

(V4)
GFC Cell header generation/extraction;

ATM layer
Cell VP/VC switching.

Cell multiplexing and demultiplexing.
Cell rate decoupling HEC cell header sequence
Physical
TC sublayer
generation/check Cell delimitation Transmission frame

adaptation Transmission frame generation/recovery
Layer
PM sublayer
Bit timing Physical media
The functions of all layers are described as follows:

1.
Physical Layer
The physical layer is the carrier of information stream. It contains the Transmission
Convergence (TC) sublayer and Physical Media-Dependent (PMD) sublayer.
i.
TC sublayer
The TC sublayer encapsulates the ATM cells into the transmission frames being
used, or extracts valid ATM cells from them.
The procedure for encapsulating ATM layer cells into transmission frame is as
follows: ATM cell demodulation (buffer) HEC generation Cell delimitation
Transmission frame adaptation Generation of transmission frame.
The procedure for extracting valid ATM layer cells from transmission frame:
Transmission frame receiving Transmission frame adaptation Cell delimitation
HEC verification ATM cell queuing. The main functions of TC sublayer are cell
delimitation and HEC.
The cell rate decoupling is to interleave some idle cells to adapt the ATM layer cell
rate to the rate of transmission line.
The HEC and cell delimitation are implemented through the HEC. That is, to
perform CRC for every 32 bits. If they match subsequent 8 bits, a cell header is
found.
ii.
18
PMD sublayer
The PMD sublayer implements its functions in accordance with ITU-T and ATM
F recommendation, and contains the following types of connections:
2.
a)
Connection based on direct cell transmission.
b)
Connection based on PDH network transmission.
c)
Connection based on SDH network transmission.
d)
Direct cell fiber transmission.
e)
Universal Test & Operations PHY Interface for ATM (UTOPIA)
f)
OAM transmission interface
ATM layer
The ATM layer transmits ATM service data unit (48 bytes) and implements
communication with peer layer by using the cell (53 bytes) transport function
provided by the physical layer. It also provides transmission service for the AAL
layer. The ATM Service Data Unit (ATM-SDU) is an arbitrary data segment with
fixed length of 48 bytes and is the payload of an ATM cell.
The flow control is controlled by the GFC bit in the cell header.
The cell multiplexing/demultiplexing is implemented at the TC sublayer interface
between the ATM layer and physical layer. The ATM layer at the transmitting end
multiplexes cells with varied VCIs/VPIs and transmits them to the physical layer.
The ATM layer at the receiving end identifies the VCIs/VPIs of cells from the
physical layer and transmits them to different users for handling.
Cell header operation: Fill VCI/VPI and PTI on user side, and translate VCI/VPI in
network node.
The OAM function of ATM layer consists of F4 and F5 two levels. ZTE RNC support
F5 level Loop Back, continuity check, and fault management including RDI and AIS.
OAM
function
for
each
ATM
interface
board
is
controlled
by
switch
AtmOam.OamLock. To guarantee Loop Back diagnose could be carried, each ATM

interface board should be configured to one unique ATM location ID
19

(V4)
(AtmOam.LocationId1,
AtmOam.LocationId2,
AtmOam.LocationId3,
AtmOam.LocationId4) according to the ATM network plan. To implement VCC level

continuity
check,
(PvcTp.CcFlowType),
CC
check
automatic
switch(PvcTp.CcValid),
CC
check
active
CC
check
and
type
de-active
flag(PvcTp.CcSetFlag) and CC check direction(PvcTp.CcDirection)parameters

must be configured for VCC link.
3.
AAL
The AAL segments and assembles user information of the upper layer into cells,
absorbs cell delay jitter and cell loss and performs flow control and error control. The
network provides functions only up to the ATM layer. The AAL functions are
provided by users or network and external interfaces.
The AAL is used to enhance the capabilities of the ATM layer to meet the demands
of various services. These services may either be user services or functional
services required on the control and management planes. The services transported
at the ATM layer can be categorized into four types based on three basic
parameters: timing requirement between source and destination, bit rate
requirement and connection mode. Service types are Class A, Class B, Class C and
Class D.
Class A: Constant Bit Rate (CBR) services. ATM Adaptation Layer 1 (AAL1)
supports connection-oriented services with constant bit rate, for example, 64Kbit/s
voice service, constant bit rate non-compressed video communication and leased
circuits of private data network.
Class B: Variable Bit Rate (VBR) services. ATM Adaptation Layer 2 (AAL2) supports
connection-oriented services with variable bit rate, for example, compressed packet
voice communication and video transmission services. Such services have
transmission delay because the receiver needs to reassemble the original
non-compressed voice and video information.
Class C: Connection-Oriented data services: AAL3/4. Class C services include file
transfer and data network services, the connection of which is established before
data transmission. These services are of variable bit rate but without transmission
delay.
20
Class D: Connectionless data services, including datagram and data network

services. The connection will not be established prior to data transmission. AAL3/4
or AAL5 supports Class D services.
Table 3-3
Services and related parameters
Service
Parameter
Class A
Class B
Class C
Class D
Source and
destination
Required
Not required.
timing
Bit rate
Connection
Mode
Constant
Variable
Connection-oriented
Connectionless
AAL 3
AAL type
AAL 1
AAL 4
AAL 2
AAL 5
VBR Motion
User service
CBR Circuit picture,
Connection-oriented
examples
emulation
data transmission
video and
audio
QoS
QoS1
QoS2
QoS3
Connectionless
data
transmission
QoS4
Several bit rate-related concepts are described as follows:

Constant Bit Rate (CBR): Used to imitate copper wire or optical fiber. It involves no
error check, flow control or other types of handling. The CBR enables a smooth
transition from current telephone system into future B-ISDN system because
voice-class PCM paths, T1 circuits and other telephone systems all adopt
synchronous data transmission with CBR.
Variable Bit Rate (VBR): Classified into two sub-groups: Real-time-VBR (RT-VBR)
and Non-Real-time VBR (NRT-VBR). The RT-VBR is primarily used to describe
real-time services with variable data stream and strict requirements, for example,
interactive compressed video (such as videoconference). The NRT-VBR is used
where timing transmission is required, for example, e-mail, which allows for certain
extent of delay and change,
21

(V4)
Available Bit Rate (ABR): Designed for sporadic information transmission with given
bandwidth scope. The ABR is the only service type with which the network offers
bitrate response to senders. In the event of network congestion, senders are
requested to lower transmission rate. If the senders comply with these feedback
requests, the cell loss rate can be very low in ABR-capable communication. The
acting ABRs can be regarded as mobile passengers waiting in a queue: If there are
vacant seats (space), they are assigned to these seats without delay; otherwise,
they have to wait (unless some minimum bandwidth is available).
Unspecified Bit Rate (UBR): It does not make any commitment or handle the
congestion. The UBR is quite applicable to transmission of IP datagram. In the event
of congestion, UBR cells are discarded, but neither feedback nor request for
lowering transmission rate is transmitted to senders.
Unspecified Bit Rate Plus (UBR+): UBR+ is also known as GFR (Guaranteed Frame
Rate). UBR + is UBR added with minimum transmission bandwidth (frame rate)
service quality assurance. When the UBR + frames come into the network, the
frames which exceed the configuration parameters are tagged in accordance with
parameter control (UPC / NPC) in order to discard the frames during network
congestion, when the UBR+ frames come into the network, the rest of the frames
are sent through proper handling of scheduling and queue management, so UBR+
will simply and effectively provide the minimum bandwidth. But UBR + is only
applicable to AAL5 data services, that is, carrying Iub OMCB or Iu-PS services.
Table 3-4
Features of various ATM services
Feature
Bandwidth guarantee
Applicable to real-time
communication
Applicable to burst
communication
Any feedback on
congestion
22
CBR
rt-VBR
nrt-VBR
ABR
UBR
UBR+
Yes
Yes
Yes
Optional
No
Yes
Yes
Yes
No
No
No
No
No
No
Yes
Yes
Yes
Yes
No
No
No
Yes
No
No
3.2
ATM Transmission Interfaces
3.2.1
Implementation of ATM Protocol in RNC

The difference among various types of RNC-provided ATM Interface Processors (RAP)
only lies in the external PHY interface types (E1/T1 or SDH) while the internal
architecture of these ATM Interface Processors is the same, as shown in the following
figure.
Figure 3-8
Internal architecture of ATM Interface Processor
ATM Interface Processor

UTOPIA BUS
User
Plane
Port
PHY
PHY
PHY
Port
Port
Port
ATM Switch
AAL Network
processor
Control
Plane
The ATM handling function consists of three components: ATM PHY, ATM switching
module, and AAL network processor.
1.
ATM PHY
The ATM PHY implements ATM transmission access based on different physical
media. For ESDTA/EDTA, it offers multi-link ATM over E1/T1 access with the IMA
technology, or offers single E1/T1 TC (UNI) access; for EAPB, it offers ATM over
STM-1 access. The PHY port connects with the ATM SWITCH module through the
cell transmission bus (UTOPIA bus). In the transmitting direction, the PHY port
maps cells into physical frames and sends them on the transmission media; in the
receiving direction, it extracts cells from transmission media and sends them to the
ATM SWITCH module.
2.
ATM SWITCH
The ATM SWITCH module provides VP-/VC-granularity switching. It connects with
the ATM PHY and AAL network processor through different ATM ports (also known
23

(V4)
as ATM sub-unit). The VP/VC link based cell streams among different ATM ports
are interchangeable. Apart from the switching function, this module also implements
flow management and buffer management of VP/VC connections as well as ATM
OAM function.
3.
AAL NETWORK PROCESSOR

The AAL network processor implements AAL2 and AAL5 handling. In inbound
direction, the cell stream received at PHY port will be transmitted from ATM
SWITCH module to AAL network processor. The AAL network processor then
extracts signaling and user data carried in AAL2 and AAL5 frame, and transmits
them to the User Plane and Control Plane through the internal IP switching
platform.
In outbound direction, the signaling generated by the Control Plane is given the
AAL5 segmentation, and user data generated by User Plane is given the AAL2
segmentation in this module. Then the signaling and data are mapped into the cell
streams on VP/VC connection, sent to PHY port through the ATM SWITCH module
and finally to outbound NEs.
3.2.2
Inverse Multiplexing for ATM (IMA)

The Inverse Multiplexing for ATM (IMA) is the mainstream technical standard of ATM
over E1/T1. The conventional ATM over E1/T1 technology is bandwidth-inefficient
because one ATM physical port can only implement transmission based on one trunk
circuit. The IMA technology, however, expands the bandwidth of ATM paths by bundling
several low-speed links to protect the original investment of network operators.
The drafts of IMA specifications 1.0 and 1.1 were respectively proposed by the ATM
Forum in 1997 and 1999. ZTE UMTS IMA is compliant with the AF-PHY-0086.001
specification proposed by ATM Forum in 1999 and is backward compatible with all
features of IMA version 1.0 released in 1997.
Besides supporting the IMA technology, the RNC also enable ATM over E1/T1 through
TC (UNI) link, that is, ATM transmission is implemented only based on a single trunk
circuit instead of multi-link bundling and multiplexing. For specific protocol standards, see
ITUT- I.0321.
24
3.2.2.1
Position of IMA in ATM Protocol Stack

The IMA protocol module implements functions at the IMA sublayer. The IMA sublayer is
located between the TC sublayer and ATM layer. The IMA is a technology that reversely
multiplexes one ATM cell stream into multiple physical connections base on a cell to
transmit and multiplex cells transmitted on these connections into a single cell stream.
Role of IMA: When the user access network rate or the rate between two ATM NEs is
between two traditional multiplexing classes (for example, between E1 and E3), the IMA
multiplexes several low-rate connections into a high-rate logical connection. This high
rate is approximately equal to the summation of the low rates which composed of inverse
multiplexing.
Figure 3-9
Reference model of IMA sublayer in the ATM protocol hierarchy
User Plane Function
Layer Management
Plane
Management
ATM
Layer
ATM cell
reconstruction
ICP cell insert/pull
out
Physical IMA/TC
Cell rate decouple
Layer
Sublayer
IMA Frame Syn
Cell stuff
Error HEC cell
discard
IMA connection
ICP cell error
LIF/LODS/RDI-IMA fault
RDI-IMA alaram
Tx/Rx IMA link status
report
IMA group
configuration
Link Add/Delete
ATM cell rate
change
IMA group fault
report
IMA Statistic
Interface/TC layer
At the transmitting end, the cell streams received from the ATM layer are alternately
assigned in round robin manner to several links in the IMA group based on cell
granularity. In the receiving end, the cells received on different physical links are
reassembled into original cell streams based on cell granularity. The IMA sublayer is
transparent for the ATM layer at both ends of transmission.
25

(V4)
Figure 3-10
Inverse multiplexing and de-multiplexing of ATM cells in IMA group

Link0
I
M
A
G
R
P
Cell stream from

ATM layer
PHY
PHY
Link1
PHY
PHY
Link2
PHY
PHY
I
M
A
G
R
P
Cell stream to ATM

layer
As shown in the figure 3-10, in the transmitting direction, the ATM cells are distributed on
several PHY links in round robin mode, and in the receiving direction, the ATM cells are
reassembled into a unique cell stream based on IMA group. A group is actually a
pre-configured data channel containing several links. To ensure correct ATM cells are
assembled in a group, the IMA adopts two types of OAM cells, that is, filler cells and ICP
cells, to manage links and group.
Figure 3-11
Multi-link IMA cell transmission
IMA Frame 2
IMA Frame 1
...
ATM ATM
...
ICP2 ATM
...
ATM ATM ICP2
ATM
M-1
...
ICP2
2
M-1
ATM
...
ATM
...
IMA Frame 0
ATM
ICP1 ATM
2
M-1
ICP1 ATM ATM ATM ATM
...
ATM ICP1 ATM ATM
...
...
ATM
ICP0 ATM
ICP0
2
ATM ICP0 ATM
Link 0
Link 1
Link 2
Time
ICP1
3.2.2.2
Filler Cell
ATM
ATM Layer Cell
IMA Frame and Control Cells

1.
26
ICP Cell in Frame #1
IMA OAM cells
The IMA adopts two types of OAM cells: filler cells and ICP cells. For specific
formats of these cells, see Figure 3.12. The filler cells implement decoupling of
transmission cell rate between local and remote ends of ATM. If there are no ATM
layer cells to be sent between ICP cells within an IMA frame, the IMA transmitting
end will automatically insert filler cells on each link to maintain the expected cell rate
of the current IMA group; the IMA receiving end will verify and discard these filler
cells.
The ICP cells dedicated to carrying control and status monitoring information as
stipulated in the IMA protocol. The protocol entities at local and remote ends of the
IMA virtual link can only realize handshake and negotiation by transmitting and
receiving ICP cells. The ICP cells are indispensable for the enabling/disabling of
IMA groups, adding/deleting of IMA links, and synchronization, management and
detection of IMA frames in working state. The following figure shows the ICP cell
format:
27

(V4)
Figure 3-12
28
ICP cell format
In the OMCR, the ICP version No. of a local IMA group can be configured through
the parameter ImaGroup.ImaVersion and this parameter will be sent to a remote
IMA group through the OAM Label field in the ICP cell.
2.
IMA frame
All physical links (for example, T1/E1) in the same multiplexing and inverse
multiplexing set constitute an IMA group. The IMA protocol divides ATM cell stream
into several segments of consecutive frames on each link in the IMA group.
An IMA frame consists of M consecutive cells that appear on each link. Every IMA
frame contains one ICP cell (its position in the frame is consistent with the offset
field in the ICP cell). Note that one IMA frame spans all N links instead of one link in
current IMA group, as shown in Figure 3 11. The IMA frame can be 32, 64, 128 and
256 cells long. The specific length of IMA frame is negotiated between local and
remote ends when the IMA group is initiated and it remains unchanged in working
state. The IFSN field of the ICP cell in an IMA frame describes the sequence
number of the IMA frame, which increments from 0 to M-1.
Related features of the IMA frame can be configured through the following
parameters in the OMCR:
ImaGroup.TXFRAMLGTH: IMA frame length in transmitting direction.
3.
IMA frame synchronization

The IMA frame synchronization is a process of delimiting ATM cell sequence from
received physical signal and restoring it to an IMA frame. The synchronization is
judged by monitoring whether the ICP cell in the IMA frame is missing or has an
error. The following figure shows the status transition of IMA frame synchronization.
29

(V4)
Figure 3-13
IMA frame synchronization mechanism
The status transition from loss-of-synchronization to synchronization involves the

following three important parameters:
value: Refers to the number of continuous invalid ICP cells. It is the threshold for IMA
frame to transit from synchronization status into IMA Hunt status.
value: Refers to the number of continuous valid ICP cells. It is the threshold for IMA
frame to transit from pre-synchronization status into IMA synchronization status.
value: Refers to the number of continuous errored ICP cells. It is one of the thresholds
for IMA frame to transit from synchronization status into IMA HUNT status.
4.
Operational mode of IMA group

Each end of the IMA group can either be the transmitting or receiving end, and their
working mode can either be identical or different. Therefore, the IMA group may
work in the following four different modes:
i.
30
Symmetric configuration and operation.
This is the default working mode of the IMA group, and must be supported. In such a
mode, the protocol parameters configured on the transmitting and receiving ends of
IMA group must be identical and ATM cells can only be transmitted when both ends
are ACTIVE.
ii.
Symmetric configuration and asymmetric operation
This mode is optional, requiring completely identical configurations on both transmitting

and receiving ends, but allowing only one of them, that is, transmitting or receiving
only.
iii.
Asymmetric configurations and operation
This mode is also optional, requiring neither identical configurations nor identical working
status on both ends.
The operational mode features of the IMA group can be configured through the
following parameters in the OMCR:
ImaGroup.NESYMETRY: Operational mode of local IMA group.
5.
Clock mode and SICP cell of IMA group

The IMA protocol allows each physical LINK in the IMA group to adopt an
Independent Transmit Clock (ITC) or a Common Transmit Clock (CTC) during cell
transmission. The clocks of all links in the IMA group are not synchronized in the ITC
mode, which may result in frame delay. Therefore, to avoid the overflow or
exhaustion of the transmit buffer area, ICP filler cells must be added in the IMA
frame. The ICP filler cells are also required in the CTC mode for decoupling of
transmission rate and expected value.
The continuous SICP cells containing identical LSI field in the same IMA frame can
be used to implement ICP filler cell mechanism. The number of SICP cells on each
link should be less than 1/5M. The receiving end may handle either of the two
continuous SICP cells in the IMA frame and discard the other and exclude it from
polling receiving scope.
31

(V4)
The clock mode features of the IMA group can be configured through the following
parameter in the OMCR:
ImaGroup.NeTxClkMd: Transmit clock mode of IMA group.
6.
Calculation of IMA Data Cell Rate (IDCR)

The IMA Data Cell Rate (IDCR) refers to the actual ATM cell rate that can be
achieved by the ATM layer above the IMA sublayer. The IDCR is nominally a
constant for an IMA group in ACTIVE state, that is, equal to the summation of
transmission rates of all links, but the transmission rates of IMA group are calculated
through the selected Transmit clock Reference Link (TRL). The transmission rates
involve TX and RX, but in both directions, different TRLs can be selected for IDCR
calculation. The IDCR is expressed as follows:
IDCR = Non TRLCR (M-1)/M (2048/2049)
Where, Non refers to the number of Links in ACTIVE state; TRLCR refers to the
actual cell rate measured on the TRL; (M-1)/M takes into account the feature that
each IMA frame contains one ICP cell; 2048/2049 means one SICP cell needs to be
inserted in every 2048 cells on the TRL.
7.
Selection and use of IMA TRL

At the Start-Up stage of an IMA group, the peer ends of the IMA connection select
their respective TX TRL, inform each other of the TX TRL through ICP cell and use
them as the RX TRL at the peer end. In CTC mode, the IMA transmitter inserts one
SICP cell at an interval of every 2048 cells on each link. In ITC mode, the IMA
inserts one SICP cell at an interval of every 2048 cells on each TRL and fills or
compensates cells on other links with TRL as reference.
The IMA receiving end eliminates the Cell Delay Variable (CDV) on different links,
takes 0 (no ATM cell currently) or one ATM cell from IMA receiving buffer area and
sends it to the ATM layer once the TICK value expires.
8.
32
Differential delay among IMA LINKs
The differential delay among IMA links means the IMA frames on different physical
links
are
not
completely
synchronized.
The
transmitter
may
tolerate
loss-of-synchronization to a certain extent, as stipulated in IMA protocol. Specifically

speaking, the loss-of-synchronization should not exceed 2.5 times the cell time of
lower layer physical links. The receiver must compensate the differential delay by
using the internal buffer area. If the physical link is DS1/E1, the upper limit of
differential delay compensation is 25 milliseconds.
The differential delay among IMA LINKs can be configured through the parameter
ImaGroup.DiffDelayMax in the OMCR.
9.
Redundancy protection among IMA links

One IMA group may contain multiple links and the failure of some links may not
affect the available status of the IMA group as long as the status of links with
quantity not less than the minimum threshold is ACTIVE. For the ATM layer, the
failure of some links may slightly lower the bandwidth of related ATM ports.
The features related to the number of links in the IMA group can be configured
through the following parameters in the OMCR:
ImaGroup.MinRxLks: The minimum number of RX links in ACTIVE state to keep the
IMA group in UP state.
ImaGroup.MinTxLks: The minimum number of TX links in ACTIVE state to keep the
IMA group in UP state.
According to the IMA protocol, asymmetric simplex is theoretically feasible for the
IMA group, so the number of links in the TX and RX directions may be different and
separately configured. But in practice, the IMA transmission is two-way, so the same
configuration is generally adopted for the number of TX and RX links.
3.2.2.3
IMA handling of RNC ATM interface board

The ATM PHY handling module refers to the IMA handling module on the Digital Trunk
ATM process board of RNC. The digital trunk processing boards currently supported
include the EDTA (E1/T1 interface) and ESDTA (CSTM-1 optical interface).
33

(V4)
The mapping relation between logical links in the IMA group and digital trunk lines can be
flexibly configured. When configuring the IMA group, you may map several links in the
same group into different physical links. Such a configuration ensures there are still
available links in the IMA group in the event of failure of some trunk lines. The parameter
triplet (ImaLink.SeqInChip, ImaChip.ImaChipSeq and ImaGroup.GroupSeq) solely
identifies one IMA/TC LINK, and binary group (Unit.UnitSeq, LogicalE1.LogicalE1Seq) /
(Unit.UnitSeq, LogicalT1.LogicalT1Seq) solely identifies one trunk link. When configuring
IMA/TC LINK, you can determine the mapping relation between them by selecting
related trunk link parameters.
Figure 3-14
IMA handling of RNC ATM processing board
32E1/T1
Digital Trunk Processing
board
IMA Interface Board

PHY
UTOPIA BUS
Port
IMA/TC
HW switch
IMA/TC
IMA/TC
Port
Port
Port
ATM Switch
User
Plane
AAL Network
processor
Control
Plane
Digital Trunk Processing

board(CSTM-1 interface)
1 CSTM-1
The IMA handling module also implements non-IMA TC (UNI) handling.

The chip resource sequence number of the IMA group is subject to the parameter
ImaChip.ImaChipSeq in the OMCR.
34
3.2.3
ATM over E1
E1 physical interface conforms to ITU-T G.703, and the jitter allowed by E1 physical
interface conforms to ITU-T G.823.
1.
Rate
2048 kbit/s 102.4 bit/s ( 50 ppm)

2.
Impedance
Coaxial pair: 75 ohm; symmetrical pair: 120 ohm.

3.
Timeslot
E1 contains 32 timeslots sequentially numbered from 0 to 31. Timeslot 0 is used to carry

clock synchronization information, and timeslot 16 is used to carry control signal. If the
outband Common Channel Signaling (CCS) is adopted, timeslot 16 is not used for
signaling transmission but to carry information signal, with the remaining timeslots used
to carry data. ZTE RNC adopts 30 timeslots for data transmission. The physical
bandwidth supported by one E1 is 1920kbps.
4.
Frame format
The format of frames transmitted over E1 interface conforms to ITU-T G.704. E1

supports three frame formats: basic frame (that is, multiframe without CRC-4), multiframe
(that is, multiframe with CRC-4) and forced multiframe.
The forced multiframe is a self-defined type with the frame format same as that of
multiframe. Forced multiframe and multiframe are differentiated as follows:
1.
If the format is set to forced multiframe, an alarm will be generated in the event
of multiframe loss (that is, basic frame from peer end is received) during
interconnection with peer end.
1.
If the format is set to multiframe, no alarm will be generated in the event of

multiframe loss during interconnection with peer end.
5.
Coding format
35

(V4)
HDB3.
6.
ATM over E1 protocol stack
ATM over E1 includes the following two bearer modes:

i.
IMA
One ATM path may carry several E1 links based on the multi-link bundling technology
(IMA). For related specifications, see AF-PHY-0086.001
ii.
TC(UNI)
The IMA protocol is not used at the TC layer of the ATM protocol stack, and one ATM
path can only carry a single E1 link. For related specifications, see ITUT- I.0321.
For specific technical features of ATM over E1, see Inverse Multiplexing for ATM and
IMA. This chapter only focuses on the physical interface features of E1.
7.
Implementation in RNC
EDTA supports the access of 32 E1 links; ESDTA supports the access of 252 CSTM-1
E1 links or 336 CSTM-1 T1 links. The EDTA/ESDTA processes the PCM carrier signal,
terminates the E1 physical frame of external trunk link. For details, see Inverse
Multiplexing for ATM and IMA.
The E1-capable features can be customized by configuring the units and subunits in
relation to the EDTA/ESDTA in the OMCR, with related features described as follows:
Field
Value (Unit)
Bit0: E1/T1 lines
WIRETYPE
adopt short haul.

Bit1: E1/T1 lines
adopt long haul.
Bit0: 75 ohm
(E1)/100 ohm
IMPEDANCE
(T1) Bit1: 120

ohm (E1)/110
ohm (T1)
36
Meaning
This field
configures the
short haul or
long haul of the
trunk lines.
Remarks
The short haul
connection is
supported by
default.
This field
75 ohm (E1)/100
configures the
ohm (T1) is
impedance of
supported by
the trunk lines.
default.
0: Multiframe
1: Dual-frame
CRC4MODE
(that is, basic

frame).
4: Forced
This field
configures the
working mode of
None
CRC4 and frame

format of E1 link.
multiframe
3.2.4
ATM over T1
T1 physical interface conforms to ITU-T G.703, and the jitter allowed by T1 physical
interface conforms to ITU-T G.824.
1.
Rate
1544 kbit/s 50 bits/s ( 32 ppm)

2.
Impedance
Symmetrical pair: 100 ohm.

3.
Timeslot
T1 contains 24 timeslots sequentially numbered from 0 to 23. All 24 timeslots can be

used to carry data. The synchronization is implemented through the synchronization BIT
of each frame, and there is no separate synchronization timeslot. The physical
bandwidth supported by one T1 is 1536kbps.
4.
Frame format
The format of frames transmitted over T1 interface conforms to ITU-T G.704. T1

supports the following frame formats:
1.
The Extended Super Frame (ESF) format without CRC6.
2.
ESF format with CRC6.
3.
Super Frame (SF) format.
4.
4-Frame Multiframe (F4) format.
37

(V4)
5.
SLC-96 (72-Frame Multiframe) format.
For the ESF format, see AT&T Pub 62411. For the SF format, see AT&T Pub 54016.
5.
Coding formats
T1 supports such coding formats for Bipolar with eight-Zero Substitution (B8ZS),
Alternate Mark Inversion (AMI) (56K) and AMI (64K).
6.
ATM over T1 protocol stack
ATM over T1 includes the following two bearer modes:

7.
IMA
One ATM path may carry several T1 links based on the multi-link bundling technology
(IMA). For related specifications, see AF-PHY-0086.001
8.
TC(UNI)
The IMA protocol is not used at the TC layer of the ATM protocol stack, and one ATM
path can only carry a single T1 link. For related specifications, see ITUT- I.0321.
For specific technical features of ATM over T1, see Inverse Multiplexing for ATM, IMA.
This chapter only focuses on the physical interface features of T1.
9.
The RNC provides the EDTA and supports the access of 32 T1 links. The EDTA
processes the PCM carrier signal, terminates the T1 physical frame of external trunk link.
The T1-capable features can be customized by configuring the units and subunits in
relation to the EDTA in the OMCR, with related features described as follows:
Field
WIRETYPE
38
Value (Unit)
Meaning
Remarks
Bit0: E1/T1
This field
lines adopt
configures the The short haul
short haul.
short haul or
connection is
Bit1: E1/T1
long haul of
supported by
lines adopt
the trunk
default.
long haul.
lines.
IMPEDANCE
CRC4MODE
Bit0: 75 ohm
This field
(E1)/100 ohm
configures the
(T1) Bit1: 120
impedance of
ohm (E1)/110
the trunk
ohm (T1)
lines.
0: Multiframe
This field
1: Dual-frame
configures the
(that is, basic
working mode
frame).
of CRC4 and
4: Forced
frame format
multiframe
of T1 link.
75 ohm (E1)/100
ohm (T1) is
supported by
default.
None.
0: B8ZS
coding format
of T1.
1: AMI coding
CODINGFORMAT
format of T1
(56K)
This field
configures the
coding format
None
of T1.
2: AMI coding
format of T1
(64K)
3.2.5
ATM over Optical STM-1/OC-3
3.2.5.1
Physical interface
STM-1 is one of the basic rate standards in SDH/SONET specifications set forth by the
International Telegraph and Telephone Consultative Committee (CCITT). The physical
interface features of the optical STM-1 module of ZTE UMTS are as follows:
Rate: 155.520Mb/s4.6ppm
Standard: ITU-T G.957/G.958.
Media type: ITU-T G.652/G.653 single-mode fiber.
Operating wavelength: 1310 nm.
Sensitivity: better than -31 dB.
39

(V4)
Interface: S-1.1
Non-trunk transmission distance: 15 Km.
3.2.5.2
STM-N physical frame format

The SDH features a set of standardized information hierarchy. The basic signal
transmission hierarchy is the Synchronous Transport Module-1 (STM-1), which can be
multiplexed by multiples of 4 into high-rate digital signal series through byte interleaving.
The basic method is shown in the following table.
Level
STM-1
Rate (Mbit/s)
155.520
STM-4
622.080
STM-16
2488..320
STM-64
9953.280
The STM-Ns in the same level feature identical rate and frame format to facilitate
tributary synchronous multiplexing, DXC, add/drop and switching, and direct add/drop of
low-speed tributary signals into and from high-speed ones. In view of the above feature,
the ITU-T defines that the STM-N is an octet-based rectangle-block frame structure.
Figure 3-15
STM-N frame format
Information payload stores various information blocks transmitted by STM-N.

Path overhead refers to the overhead bytes used to monitor the transmission
performance of low-rate signals.
Section overhead refers to the mandatory bytes used for network operation,
management and maintenance to ensure normal and flexible transmission of information
payload.
40
Section overhead includes regenerator section overhead (RSOH) and multiplex section
overhead (MSOH).
3.2.5.3
SDH overhead byes

The SDH offers subdivided monitoring and management functions. Specifically, the
monitoring includes section monitoring and path monitoring. The section monitoring
includes regeneration section and multiplex section monitoring, and the path monitoring
includes higher order path and lower order path monitoring. These monitoring functions
are implemented through different overhead bytes.
1.
Section Overhead (SOH)
overhead (MSOH).
The Regeneration Section Trace Message J0 is contained in the RSOH and used to
repeatedly send the Section Access Point Identifier (SAPI) for the receiving end to retain
continuous connection with the designated transmitting end. The operator can detect and
clear faults at an early time through J0 byte to speed up network recovery. In the OMCR,
the J0 mode and Regeneration Section Trace Message in relation to J0 byte are
configurable through the parameters S155Port.J0Mode and S155Port.J0.
2.
Path Overhead (POH)
The payload of an STM-N frame contains the Path Overhead (POH) used to monitor
low-speed tributary signals.
The SOH implements section monitoring and the POH implements path monitoring. The
POH can be further classified into Higher-Order Path Overhead (HOPOH) and
Lower-Order Path Overhead (LOPOH).
The HOPOH monitors the paths of VC-4/VC-3 level.
The ATM over STM-1 necessitates the monitoring of VC-4 path. In the OMCR, you can
configure the J1 mode and the Higher-Order Path Trace Message of J1 through the
parameters Vc4Trail.J1Mode and Vc4Trail.J1 respectively.
41

(V4)
The Path signal label byte C2 is contained in HOPOH and used to indicate the
multiplexing structure and nature of information payload of VC frames, for example,
whether the path is loaded, the types of services carried and their mapping mode. The
C2 at transmitting and receiving ends must match. In the OMCR, the parameter
Vc4Trail.C2 is configurable and for ATM over STM-1 mode, C2 should be set to ATM
Mapping.
3.2.5.4
ATM over STM-1 multiplexing mapping

The following terms are used in the STM-N multiplexing structure:
Multiplexing Unit (MXU): The basic MXU of SDH contains several containers, including
(C-n), virtual containers (VC-n), tributary units (TU-n), tributary unit groups (TUG-n),
administration units (AU-n) and administration unit groups (AUG-n). n refers to the level
sequence number.
Container: Refers to the information structure unit used to carry service signals with
varied rates. Five standard containers, including C-11, C-12, C-2, C-3 and C-4, are
defined in G.709.
Virtual Container (VC): Refers to the information structure unit used to support SDH
path layer connection. The VC can be categorized into Lower Order Virtual Containers
(LOVC) and Higher Order Virtual Containers (HOVC). VC-4 and VC-3 in AU-3 are
HOVCs.
Tributary Unit (TU) and Tributary Unit Group (TUG): TU refers to the information
structure used to provide adaptation between lower order path and higher order path
layers. A TUG refers to one TU or a collection of several TUs that constantly occupy the
specified position(s) in higher order VC payload.
Administration Unit (AU) and Administration Unit Group (AUG): AU refers to the
information structure used to provide adaptation between lower order path and higher
order path layers. An AUG refers to one AU or a collection of several AUs that constantly
occupy the specified position(s) in STM-N payload.
The following figure shows the SDH multiplexing mapping structure:
42
Figure 3-16
STM-N multiplexing mapping structure
ATM over STM-1 implements insertion and dropping of ATM cell streams into or from
VC-4 in SDH frames.
3.2.5.5
The ATM Optical module on the EAPB board of RNC implements PHY functions, and
provides four optical interfaces corresponding to four STM-1-based transmission paths.
In the inbound direction, STM-1 frames are received by the ATM Optical module which
recovers the ATM cell streams carried in them. Then the ATM switch module switches
VP/VC connections to the ATM network processor. Next, The ATM network processor
then extracts the carried user and signaling data through AAL2/AAL5 processing, and
sends the payload data to the User plane processing Board or Control plane processing
Board through the internal media stream switching platform.
In the outbound direction, the processing is symmetric to that in the inbound direction.
Figure 3-17
PHY
ATM Process Board processing structure
ATM Process Board
UTOPIA BUS
Port
User plane
processing
Board
STM-1
STM-1
STM-1
STM-1
Port
Port
Port
Port
ATM Switch
AAL Network
processor
Control
plane
processing
Board
43

(V4)
The four ATM Optical modules correspond to the four ATM switching ports (ATM
sub-units) on the ATM switch module. The ATM sub-unit features in the OMCR can be
configured through parameters described in 3.2.1.3:
The following SDH optical path features of each optical interface should also be
configured in the OMCR:
Received signal failure (SF) alarm threshold: Corresponds to the parameter
S155Port.SF.
Received signal degradation (SD) alarm threshold: Corresponds to the parameter
S155Port.SD.
3.2.6
ATM over Channelized STM-1/OC-3
3.2.6.1
Physical interface
STM-1 is one of the basic rate standards in SDH/SONET specifications set forth by
CCITT. The physical interface features of the optical STM-1 module of ZTE UMTS are as
follows:
Rate: 155.520Mb/s4.6ppm
Standard: ITU-T G.957/G.958.
Media type: ITU-T G.652/G.653 single-mode fiber.
Operating wavelength: 1310nm
Sensitivity: Better than -31dB.
Interface S-1.1
Non-trunk transmission distance: 15Km.
3.2.6.2
STM-N physical frame format

For details, see ATM over Optical STM-1/OC-3.
44
3.2.6.3
SDH overhead byes

The SDH offers subdivided monitoring and management functions. Specifically, the
monitoring includes section monitoring and path monitoring. The section monitoring
includes regeneration section and multiplex section monitoring, and the path monitoring
includes higher order path and lower order path monitoring. These monitoring functions
are implemented through different overhead bytes.
1.
Section Overhead (SOH)
overhead (MSOH).
The Regeneration Section Trace Message J0 is contained in the RSOH and used to
repeatedly send the Section Access Point Identifier (SAPI) for the receiving end to retain
continuous connection with the designated transmitting end. J0 byte can be an arbitrary
character on the network of the same operator. However, J0 bytes at the transmitting
and receiving ends must match on the network border of two operators. The operator
can detect and clear faults at an early time through J0 byte to speed up network recovery.
In the OMCR, the J0 mode and Regeneration Section Trace Message in relation to J0
byte can be configured through the parameters S155Port.J0Mode and S155Port.J0.
2.
Path Overhead (POH)
The payload of an STM-N frame contains the Path Overhead (POH) used to monitor
low-speed tributary signals.
The SOH implements section monitoring and the POH implements path monitoring. The
POH can be further classified into the Higher-Order Path Overhead (HOPOH) and the
Lower-Order Path Overhead (LOPOH).
The HOPOH monitors the paths of VC-4/VC-3 level.
The ATM over CSTM-1 necessitates the monitoring of VC-4 path. In the OMCR, the J1
mode and the Higher-Order Path Trace Message of J1 can be configured through the
parameters Vc4Trail.J1Mode and Vc4Trail.J1 respectively.
45

(V4)
The Path signal label byte C2 is contained in HOPOH and used to indicate the
multiplexing structure and nature of information payload of VC frames, for example,
whether the path is loaded, what the types of services carried are and what their
mapping mode is. The C2 must match at transmitting and receiving ends. In the OMCR,
the parameter Vc4Trail.C2 can be configured; and for ATM over CSTM-1 mode, the
payload type of optical path need be set to TUG Mapping.
The LOPOH monitors the paths of VC-11/VC-12 level. In the OMCR, the J2 mode and
the Lower-Order Path Trace Message of J2 can be configured through the parameters
(Vc4Vc11Trail.J2MODE,Vc4Vc11Trail.J2),(Vc12Trail.J2MODE,Vc12Trail.J2),(Vc3Vc12
Trail.J2MODE,Vc3Vc12Trail.J2),(Vc11Trail.J2MODE,Vc11Trail.J2).
The Low Order Path signal label byte V5 is contained in LOPOH and used to indicate the
multiplexing structure and nature of information payload of VO frames, for example,
whether the path is loaded, what the types of services carried are and what their
mapping mode is. The C2 must match between the transmitting and receiving ends. In
the OMCR, the parameter Vc4Vc11Trail.V5,Vc12Trail.V5,Vc3Vc12Trail.V5,Vc11Trail.V5
can be configured. For the CSTM-1 mode, E1/T1 signals are carried in VC-11/VC-12, so
V5 is set to Asynchronous Mapping Signal by default.
3.2.6.4
STM-1 multiplexing mapping

The following terms are used in the STM-N multiplexing structure:
Multiplexing Unit (MXU): The basic MXU of SDH contains several containers, including
(C-n), virtual containers (VC-n), tributary units (TU-n), tributary unit groups (TUG-n),
administration units (AU-n) and administration unit groups (AUG-n). n refers to the level
sequence number.
Container: Refers to the information structure unit used to carry service signals with
varied rates. Five standard containers, including C-11, C-12, C-2, C and C-4, are defined
in G.709.
Virtual Container (VC): Refers to the information structure unit used to support SDH
path layer connection. The VC can be categorized into Lower Order Virtual Containers
(LOVC) and Higher Order Virtual Containers (HOVC). VC-4 and VC-3 in AU-3 are
HOVCs.
46
Tributary Unit (TU) and Tributary Unit Group (TUG): TU refers to the information
structure used to provide adaptation between lower order path and higher order path
layers. A TUG refers to one TU or a collection of several TUs that constantly occupy the
specified position(s) in higher order VC payload.
Administration Unit (AU) and Administration Unit Group (AUG): AU refers to the
information structure used to provide adaptation between lower order path and higher
order path layers. An AUG refers to one AU or a collection of several AUs that constantly
occupy the specified position(s) in STM-N payload.
3.2.6.5
E1-/T1-to-CSTM-1 multiplexing
The Channel Synchronous Transfer Mode-1 (CSTM-1) multiplexing is a technology that
multiplexes low-speed tributary signals (for example, 2Mb/s, 34Mb/s and 140Mb/s) into
SDH signals-STM-1 frames. The E1-based CSTM-1 multiplexing refers to the insertion
and dropping of STM-1/VC-12 signals, and T1-based CSTM-1 multiplexing refers to the
insertion and dropping of STM-1/VC11 signals.
The lines of multiplexing from an active payload to STM-N are not unique during SDH
multiplexing in ITUT-G.709 recommendation. Each STM-1 signal may multiplex 63 E1 or
84 T1 signals.
The following figure shows the E1-to-STM-1 multiplexing process:
Figure 3-18
E1-to-STM-1 multiplexing process
The following figure shows the T1-to-STM-1 multiplexing process:
47

(V4)
Figure 3-19
T1-to-STM-1 multiplexing process
In practice, the multiplex paths may vary among countries and regions. To ensure the
paths for inter-networking, an operator can select AU-3 or AU-4 multiplexing mode (The
AU-4 is adopted by the SONET in China, and here the default configuration is used) by
setting the parameter Board.SdhPortMuxMode in the OMC of RNC.
According to SDH multiplexing standard, each STM-1 signal may multiplex 63 T1 signals
(Semi-configuration), or 84 T1 signals (Full-configuration). Operator can select E1 or T1
interface
in
the
STM-1
signals,
T1
multiplex
mode
(Semi-configuration
or
Full-configuration) by setting the parameter Board.ExtPortType.
3.2.6.6
PCM sequencing mode in CSTM-1

The following are currently the two standards for tributary PCM sequencing (E1/T1 link
identifier):
1.
ITUT-G.707-based PCM sequencing:
The low-rate SDH signals are multiplexed into high-rate ones through byte interleaving in
the SDH.
For E1, 3 VC12s are multiplexed into TUG-2 frames through byte interleaving; 7 TUG-2
frames multiplexed into TUG-3 frames through byte interleaving; 3 TUG-3 frames
multiplexed into VC4 frames through byte interleaving.
For T1, 4 VC11s are multiplexed into TUG-2 frames through byte interleaving; 7 TUG-2
frames multiplexed into TUG-3 frames through byte interleaving; 3 TUG-3 frames
multiplexed into VC4 frames through byte interleaving.
48
2.
Tributary-based PCM sequencing:
For E1, tributary-based PCM sequencing means sequential numbering of VC12 services
in the same TUG-2, starting from the first TUG-2 of the first TUG-3.
For T1, tributary-based PCM sequencing means sequential numbering of VC11 services
in the same TUG-2, starting from the first TUG-2 of the first TUG-3.
In the OMCR of RNC, the PCM sequencing mode can be configured through the
parameter PcmMapType. If the positions of tributary signals are inconsistent in VC-4
during interconnection of equipment from different vendors, the service will be
unavailable after interconnection. Therefore, this parameter must be correctly
configured.
3.2.6.7
Analysis of application scenarios in UTRAN

The RNC can provide standard ATM over CSTM-1 transmission interface for lub, Iur,
Iu-PS and Iu-CS interfaces. The most typical application scenario of CSTM-1 is still lub
interface. Generally, Node B provides the E1/T1 interface with the twisted pair or coaxial
cable as medium. The E1/T1 signals are converted and converged into CSTM-1 signals
through the SDH bridge equipment before being sent to the RNC.
The following figure shows a typical networking example where the ZXONM E300
enables the conversion between E1 and CSTM-1 (E1).
49

(V4)
Figure 3-20
Typical networking
Node B
E
S
D
T
A
coaxial pair
Fiber
Optical transmiter and

receiver
Node B
RNC
With the CSTM-1 interface, the RNC products can distribute with a large number of
E1/T1 electrical interfaces, hence the higher interface integration. Furthermore, the
mature APS technology of the SDH will greatly enhance interface and line protection.
3.2.6.8
Figure 3-21
ATM over Channelized STM-1/OC-3 implementation
User plane
processing
Board
Digital Trunk
ATM process
board
CSTM-1
CSTM-1
Control plane
processing
Board
The following boards are involved:

1.
The optical digital trunk and IMA interface board: ESDTA. The ESDTA provides four
CSTM-1 optical interface and implements CSTM-1 access; implements add/drop of
low-speed trunk signals in the STM-1 frame; terminates the processing of trunk
50
frames at physical layer; ESDTA completes the processing of ATM over E1/T1 at
the same time.
3.3
PVC Cross Connection

When Node B connects to its Controlling RNC (CRNC) through the RNC in charge of
ATM convergence due to the lack of direct point-to-point ATM transmission path, the
convergence RNC needs to switch the IUB VP/VC service connections of Node B to its
CRNC.
Note that such a scenario completely differs from the SRNC-DRNC separation
mechanism in the WCDMA technology. In this scenario, the IUB cell streams of Node B
are forwarded to its CRNC through VC/VP switching, and the processing is
independently implemented at the ATM layer and completely transparent for RNLU and
RNLC upper layer applications.
Figure 3-22
PVC cross connection networking
VP/VC1
Node B
E1/SDH
VP/VC2
Switch
RNC
CRNC
The ATM Switch module on the ATM interface board of RNC can implement VP/VC
cross connection. It connects with different ATM PHY peripherals through the UTOPIA
bus. These ATM PHY peripherals correspond to the physical interface entities of
transmission cells such as IMA groups and optical modules. They connect with different
ATM ports of the ATM Switch module through UTOPIA bus, as shown in the following
figure. Apart from the above external ATM ports, each ATM Switch module also provides
an internal ATM port numbered 0. This port connects with the AAL network processor
51

(V4)
and switches the service data ended in local RNC over VP/VC connection. The following
description focuses on the features of the ATM Switch module.
Each port on the ATM Switch module may carry multiple VP/VC connections, and flexible
VP-/VC-granularity switching can be implemented for ATM connections among different
ports, as shown in the figure.
Figure 3-23
VP/VC switching
In the OMCR, the switching relation between VP- or VC-granularity ATM connections
among different ports can be flexibly configured. This version currently only supports
VC-granularity PVC switching among different ports.
The PVC connection includes the following two types at the RNC ATM layer:
1.
Terminated after intra-board switching.
2.
Forwarded to other RNC NEs after intra-board switching.

For PVC connections that need to be terminated by the local RNC, the first type
mentioned above must be configured and related PVC switching relation configuration:
(External Port, External VPI, and External VCI) (Port 0, Internal VPI, and Internal
VCI).
52
In the OMCR, the above switching relation is represented by a combination of

parameters:
(LogicalAtmPort.BoardPortSeq,
PvcTp.CVPI,
PvcTp.CVCI)
(LogicalAtmPort.BoardPortSeq, PvcTp.VPI , PvcTp.VCI).

For PVC connections terminated by non-local RNC, the switching relation configuration:
(External Port 1, External VPI 1, External VCI 2) (External Port 2, External VPI 2,
External VCI 2).
In the OMCR, the above switching relation is represented by a combination of
parameters: (LogicalAtmPort.BoardPortSeq, PvcCross.Port2Vpi, PvcCross.Port2Vci)
(LogicalAtmPort.BoardPortSeq, PvcCross.Port1Vpi, PvcCross.Port1Vci).
The external VPI and external VCI are inter-NE interconnection parameters and must be
configured as planned. The internal VCI and VPI are internal equipment parameters and
may not be disclosed externally. The switching relation of a pair of PVC connections is
configured while configuring PVC. The switching relation is uniquely identified with the
parameter PvcTp.PvcSeq / PvcCross.PvcSeq in the OMCR.
The parameter Segment indicates VPC (VCC) node property: 2 means VPC or VCC End
Node and 3 means VPC or VCC Segment and End Node). The type of user service is
uniquely identified with the parameter PvcTp.PvcService: AAL5 signaling, AAL5 data,
AAL2 user data, OMCB. The type of ATM Interface is identified with the parameter
LogicalAtmPort.UniNniFlag: UNI or NNI. The parameter PvcTp.Iftype identified detailed
PVC interface: Iub, Iur, Iu-CS, Iu-PS and IuPC.
Generally, internal port (that is, port 0) is called low-end port, and external ports are
called high-end ports.
3.4
Dynamic AAL2 Connections

The Access Link Control Application Protocol (ALCAP) provides various dynamic
management functions for AAL2 connections, including dynamic setup, modification and
release of AAL2 connections.
Each
AAL2
connection
in
the
RNC
has
global
unique
No.
(Aal2PathTp.AAL2PATHSEQ).
53

(V4)
The AAL2 connection can either be the connection with CN or the connection with Node
B. Different management identifiers (Aal2PathTp.OWNER) must be selected for
connection with different NEs.
3.4.1
Setup Procedure
When a setup request is initiated by the local end, an AAL2 connection with sufficient
bandwidth will be selected based on the peer node ATM address of the configured AAL2
connection. Then one CID is selected based on the following CID allocation principle.
The bandwidth of existing AAL2 connection is subtracted from the bandwidth selected for
the ATM path, and the admission information is recorded into the CID table and instance
data area. If there are still some AAL2 paths with sufficient bandwidth when the
connection is set up for next identical peer node, one new path will be selected to
substitute the previous one. In this way, the AAL2 connections at the same end can
implement load sharing among different AAL2 paths. The ALCAP initiates an outgoing
setup procedure based on the requested CID. In the event of operation failure at the local
end of ALCAP or negotiation with peer end failed, the system will release the previously
requested CID and occupied bandwidth.
When the peer end voluntarily initiates a bearer setup request, The ALCAP receives the
ERQ message from peer end, and checks incoming CEID at the incoming interface,
calculates admission bandwidth based on office direction and path group ID and judges
whether access is possible. If access is confirmed, the ALCAP requests local office CID
resource for system to create an instance data area and sends an ECF message to the
peer end. The requested CID resource will be released in the event of insufficient
admission bandwidth or local office operation failure.
3.4.2
Modification Procedure
When the local end initiates a bearer modification request, the system will modify data in
the CID table and instance data area, and back up old data while saving new data. If the
service rate is modified, the ALCAP initiates outgoing modification procedure. Before the
ALCAP initiates outgoing modification procedure, the system will reserve bandwidth in
the CID table, and occupy the reserved bandwidth after interaction between ALCAP and
the peer end. In the event of operation failure at local end of ALCAP or negotiation with
54
the peer end failed, the system cancels parameter modification and records old
parameters in the data area again.
When the peer end voluntarily initiates a bearer modification request, the ALCAP
receives the MOD message from peer end, requests reserved bandwidth in the incoming
modification procedure. The subsystem on the control plane judges whether parameters
carried in the message need to be modified. If modification is allowed, the subsystem
occupies reserved bandwidth, and the ALCAP continues subsequent incoming
modification procedure and sends an MOA message to peer end. If modification is not
allowed at local end, the ALCAP will send an MOR to peer end.
3.4.3
Release Procedure
The local end voluntarily initiates a bearer release request, and the ALCAP initiates
outgoing release procedure based on the CID in the data area. The system then
releases occupied bandwidth and CID resources.
The peer end voluntarily initiates a bearer release request: Upon receiving a REL or RES
message from peer end, the ALCAP instructs upper layer users to initiate bearer release
and releases CID and bandwidth resources while requesting CEID in the incoming
release procedure.
3.4.4
CID Allocation Policy

According to Q.2630, the system allocates CIDs for AAL2 connections based on whether
local node has any AAL2 path. If the local node has one AAL2 path, the system allocates
8-255 to CID in an ascending order; otherwise it allocates them in a descending order.
The setup of AAL2 connection on lub and Iu-CS interfaces can only be initiated by the
RNC, and therefore CID allocation only occurs in the RNC. The system grants the RNC
to own all AAL2 paths connected with Node B or CN. The RNC allocates CIDs in an
ascending order, so the CID allocation conflict can be avoided on both ends of AAL
paths.
For lur interface, the role of SRNC may exchange between two RNCs, so which segment
of 8-255 is allocated for AAL2 paths is uncertain. ZTE RNC offers a solution that enables
flexible configuration through negotiation. If there is any local terminal, the system
55

(V4)
allocates CIDs in an ascending order; otherwise it allocates them in a descending order

so as to avoid CID allocation conflict.
After Q.2630 on the transmission control plane sets up AAL2 connections on lub, lur and
Iu-CS interfaces, ZTE equipment implements access connection control.
The CID resources may not be configured and they are dynamically managed by the
system based on calling status.
3.4.5
Interconnection with AAL2 Switching Device

ZTE RNC connects to a destination ATM office through a maximum of four ATM
gateways, which means the AAL2 link resources sharing between ZTE RNC and the
destination office is implemented through a maximum of four ATM gateways working in
load sharing mode. Figure 3.24 shows the typical IUR networking.
Figure 3-24
Typical IUR relay Networking
MGW 103
ZTE RNC
Mux
AAL2 SWITCH
NODE A
Other_RNC
MGW 104
AAL2 PATH for IUCS
AAL2 PATH for IUR
As shown in the figure 3-24, ZTE RNC connects with adjacent RNCs through several
ATM gateways (MGW in this example). ZTE RNC directly connects with each MGW. The
MGW is configured with STP (Signaling Transfer Point) function used for the RNSAP
signaling of the lur interface.
56
To implement AAL2 resource sharing between IU and IUR interfaces, the AAL2 static
routes must be configured for ZTE RNC to obtain the relay ATM office information
through the destination ATM office. In the above example, the destination node is
adjacent RNC, the relay node is MGW.
For Iu-CS interface traffic, when transport layer service instance is to be established in
outgoing direction, ZTE RNC would lookup AAL2 static route table first, to get the relay
node information for the destination node, the A2EA of relay node is used to find one
AAL2 path in its associated relay node while the A2EA of destination node is encoded in
ALCAP-ERQ message to inform the downstream AAL2 nodes for further relay.
For Iur interface traffic, when transport layer service instance is to be established in
outgoing direction, The adjacent RNCs ATM office information ID is used to lookup
AAL2 route table to match the relay node information, the A2EA of relay node is used to
find one AAL2 path in its associated relay node while the A2EA of destination node (for
some vendors DRNC, Destination A2EA would be changed to D-Node Bs A2EA ) is
encoded in ALCAP-ERQ message to inform the downstream AAL2 nodes for further
relay.
For one Destination ATM node, a maximum of 4 relay node could be configured in the
AAL2 route table; multiple relay nodes would be chosen in load sharing mode by default.
To perform bandwidth admission control, The AAL2 link resource would be allocated to
logical transmission paths associated with peer NEs (for details, see feature Transport
CAC). The AAL2 links connected with ZTE RNC and relay node are called shared AAL2
path. Shared AAL2 path must be allocated to the transmission path associated with relay
node,
and
the
attribute
(Aal2PathTp.IubUseFlag,
Aal2PathTp.IurUseFlag,
Aal2PathTp.IuCSUseFlag) should be designated to indicate whether to support Iub,

Iu-CS or Iur AAL2 relay.
Sharing AAL2 link must be referenced by transport paths of destination ATM office. In
the CAC procedure, bandwidth allocation and check is on the destination transport path
while CID allocation and check is on the relay transport path.
The parameter UIurLink.SptAal2Switch determines whether the adjacent RNC supports
AAL2 switch. If supported, the A2EA parameter in the ALCAP ERQ sent to the adjacent
57

(V4)
RNC will be set as the Node b address obtained from the adjacent RNC in the previous
message. The parameter is used when ZTE RNC connects with some special vendors.
3.4.6
ALCAP protocol version

When RNC and the peer office work together, AAL2 Signalling Protocol version should
be configured ITU-T Q2630.1 or
Aal2Ap.SptQ26302Flag.
ITU-T Q2630.2.
the configuration parameters is
Because the parameter should be consistent with the
opposite end, the services may be interrupted if one of the two peers cannot support
Q.2630.2.
This parameter does not support Q.2630.2 by default.
When RNC support ITU-T Q.2630.2, Path Type (PT) parameter will be contained in
ALCAP ERQ message, and modification of AAL type 2 connection resources is provided.
The Path Type parameter of AAL type 2 path (Aal2PathTp.Aal2PathClass) should be
consistent with the opposite end.
When RNC support ITU-T Q.2630.1, not support ITU-T Q.2630.2, Path Type parameter
will not be contained in ALCAP ERQ message, and modification of AAL type 2
connection resources is not provided.
3.5
Permanent AAL5 Connections

The SAAL signaling links carried on AAL5 connections involve two different types of
interfaces:
1)
The SAAL on lub interface contains SSCOP and SSCF-UNI to carry upper layer
NBAP and ALCAP signaling (UniSaalTp.APPTYPE).
2)
The SAAL on Iu/Iur interface contains SSCOP and SSCF-NNI, which carries
RNSAP and RANAP signaling through MTP3B and SCCP (NniSaalTp.APPTYPE)
as the SS7 link layer.
The Signaling ATM Adaptation Layer (SAAL) consists of the Common Part (CP) and
Service Special Convergence Sublayer (SSCS). The CP further consists of the Common
Part Convergence Sublayer (CPCS) and the Segmentation and Reassembly (SAR). To
accommodate the requirements of various types of upper layer information, the SSCS is
58
further divided into the Service Specific Co-ordination Function (SSCF) and the Service
Specific Connection Oriented Protocol (SSCOP) (as shown in the following figure).
Figure 3-25
SAAL protocol stack
NBAP
ALCAP
ALCAP
STC
SSCF-UNI( Q2130)
SCCP
MTP3b
SSCF-NNI( Q2140)
SSCS
SSCOP( Q2130)
CPCS
CP
LM
SAR
ATM
PHY
SSCS? ? ? ? ? ? ? ? ? ?
1.
SSCF-UNI
The SSCF-UNI is primarily responsible for coordinating the service functions between
upper layer users and SSCOP. It sets up or releases lower layer SSCOP signaling
connection based on upper layer service requirements, and forwards messages between
upper and lower layer modules to implement the translation between primitives and
signals.
2.
SSCF-NNI
The SSCF provides two functions on the NNI side:

i.
Coordination and interaction among LM, SSCOP and MTP3b of modules between
adjacent layers.
ii.
Maintenance and management of local and peer SSCF-NNI modules.

3.
SSCOP
The SSCOP implements point-to-point signaling link setup and release functions for
upper layer users. It provides two types of data transmission modes, acknowledged and
59

(V4)
unacknowledged, and adopts a reliable message transmission mechanism for signaling

data.
4.
LM
Located on the NNI interface, the Layer Management (LM) provides the following
functions:
i.
Link status management.
ii.
Link quality detection.
iii.
Processor overload/recovery detection.
iv.
Link location verification.
v.
NO CREDIT timeout monitoring.
vi.
Performance measurement.
vii.
Monitoring of the recovery interval of the last two SSCOP errors.

Each SAAL signaling link has a global unique No. (UniSaalTp.LinkSeq / Sl.SlSeq)
among ZTE RNC NEs and corresponds to the unique PvcTp.PvcSeq / PvcCross.PvcSeq.
The system initiates a link setup request for all signaling links on related PVCs based on
the user type
(UniSaalTp.APPTYPE / NniSaalTp.APPTYPE) configured in the OMCR.
Whether UNI or NNI mode is adopted is subject to the value of
(UniSaalTp.APPTYPE /
NniSaalTp.APPTYPE). The link setup parameters vary between the UNI and NNI. The
"CBR" must be selected for the ATM service type (Pvctp.ServiceCategory /
PvcCross.ServiceCategory) of AAL5 signaling links to ensure reliable transmission.

Each SAAL signaling link has a unique AAL5 object ID at Node B, and Node B will send
SSCOP connection setup request in the corresponding PVC. Service type of AAL5 PVC
is usually configured as CBR for reliable transmission of NBAP signaling.
3.5.1
IP over ATM
IP over ATM traffic carried on AAL5 link involves two scenarios for RAN transmission,
one is to carry O&M traffic for Node B in Iub interface, the other is to carry Iu PS data
60
stream, the implementation of IPOA in ZTE RNC and Node B is strictly compliant with
RFC 1577 Classical IP and ARP over ATM specification.
Logical IP interface corresponds to each ATM PHY port (IMA group, ATM over STM-1
port etc.) is the configuration object for IP over ATM transmission. IP address and subnet
mask can be configured on the above interfaces; hence static IP route can be deployed.
IPOA is a data link layer protocol in ISO reference model. User should firstly choose
AAL5 VCC link (PvcTp.PvcSeq / PvcCross.PvcSeq) under certain ATM PHY port, and
then mapping the link to the planned destination IP subnet (IpoAtmLink. DestIpAddr,
IpoAtmLink.DestIpAddrMaskLen).
For ATM over IU PS transmission, ZTE RNC support QOS based routing which means
to one destination IP subnet multi IPOA data link can be configured, different IPOA links
are used to carry traffic of different QOS type. For example, two IPOA link can be
deployed for the same IP subnet, one is based on RT-VBR traffic category and is used to
carry real time service, the other is based on UBR traffic category and is used to carry
Non-real time service, The parameter TOS is used to identify the COS value bound to a
dedicate IPOA link.
3.6
AAL2 Quality of Service separation

ZTE RNC supports real-time and non-real-time PVC configurations for AAL2. Upon the
setup of AAL2 connection, the session and stream services are mapped into real-time
AAL2 PVC, and interaction-class and background-class services are mapped into
non-real-time AAL2 PVC. In addition, the session and stream services are carried on the
PVC of real-time AAL2 assigned with different priority levels, and session services are
granted with high priority and the right of priority scheduling. Similarly, the interactionand background-class services also have different priority levels on non-real-time AAL2
PVCs.
When a service is set up, the system will accept or reject an AAL2 connection request
based on the status of network resources. For a given call, a communication connection
is allowed to set up only when the idle network resources meet the requested bandwidth
and specific indexes. Prior to the setup of a new connection, ensure the new connection
will not affect the QoS of existing connections on the network. The network resources
61

(V4)
requested by a new connection can only be obtained through negotiation with the CAC,
that is, the traffic protocol.
The system will implement PvcTp.Policing or PvcCross.Policing of the user traffic in
accordance with the traffic protocol during subsequent cell transmission upon service
setup, and check traffic based on user-requested QoS parameters. The QoS
requirements are subject to the acceptable statistical amount. The major indexes of QoS
include MaxCTD, p-to-p CDV and CLR or a combination of them based on the service
types. While meeting the QoS requirements, the scheduling mechanism will fulfill the
bandwidth committed in the distribution service agreement to ensure sufficient isolation
among connections so that the service features of one connection will not affect the
bandwidth and QoS requirements of other connections. Furthermore, the scheduler can
enable fair sharing for connections when there is any extra bandwidth.
3.6.1
Service Category
The ATM service categories (PvcTp.ServiceCategory / PvcCross.ServiceCategory) and
applicable applications include:
1.
Constant Bit Rate (CBR): The CBR enables constant transmission rate and has
strict requirements for the QoS requirements such as transmission delay,
transmission packet loss and transmission jitter. It is applicable to real-time services
or services necessitating constant bandwidth. The parameters in relation to CBR
mainly include the Peak Cell Rate (PCR) and Cell Delay Variation Tolerance
(CDVT).
2.
Variable Bit Rate (VBR): The VBR QoS provides a guarantee against transmission
delay
and
packet
loss,
and
mainly
applies
to
video
services
or
transmission-delay-sensitive services. The VBR can be further categorized into

real-time VBR (rt-VBR) and non-real-time VBR (nrt-VBR) based on the varied
requirements for transmission delay. Compared with rt-VBR, the nrt-VBR services
allow more transmission delay. The parameters in relation to VBR mainly include
the Peak Cell Rate (PCR), Sustainable Cell Rate (SCR), Maximum Burst Size (MBS)
and Cell Delay Variation Tolerance (CDVT).
62
3.
Available Bite Rate (ABR): The ABR QoS ensures the minimum transmission
bandwidth and applies to IP and LAN services. The ABR needs to provide flow
control at the ATM layer to avoid network congestion or overload. The parameters
in relation to ABR mainly include the Peak Cell Rate (PCR) and Minimum Cell Rate
(MCR).
4.
Unspecified Bit Rate (UBR): The UBR is also applicable to IP and LAN services but
without any QoS assurance. The parameter in relation to the UBR is the Peak Cell
Rate (PCR).
3.6.2
Traffic Types
RFC2514 provides 15 traffic types (PvcTp.TrafficType / PvcCross.TrafficType), among
which atmnoTrafficDescriptor (1), atmClpNoTaggingNoScr (3) and atmClptaggingNoScr
(4) are not recommended and they are marked in red in the following table. The following
table lists the corresponding relation between traffic types and the service categories of
PVC.
Service category and traffic type lookup table
Service
Traffic type
Para1
Para2
category
cbr
rtVbr
Para Para
3
atmClpNoTaggingNoScr
PCR0+1 PCR0
atmClpTaggingNoScr
PCR0+1 PCR0
atmNoClpNoScr
PCR0+1
atmClpTransparentNoScr
PCR0+1 CDVT
atmNoClpNoScrCdvt (12)
PCR0+1 CDVT
atmNoClpNoScr(2)
PCR0+1
atmClpNoTaggingNoScr(3)
PCR0+1 PCR0
atmClpTaggingNoScr(4)
PCR0+1 PCR0
atmClpNoTaggingScr(6)
PCR0+1 SCR0
MBS
atmClpNoTaggingScrCdvt(14)
PCR0+1 SCR0
MBS CDV
Para
5
ntrVbr
atmClpTaggingScr(7)
PCR0+1 SCR0
MBS
atmClpTaggingScrCdvt(15)
PCR0+1 SCR0
MBS CDV
63

(V4)
T
atmClpTransparentScr(10)
PCR0+1 SCR0+1
MBS CDV
T
atmNoClpScrCdvt(13)
PCR0+1 SCR0+1
MBS CDV
T
atmNoClpScr(5)
PCR0+1 SCR0+1
MBS
abr
atmClpNoTaggingMcr(8)
PCR0+1 CDVT
MCR
ubr
atmNoTrafficDescriptor(1)
atmNoClpNoScr(2)
PCR0+1
atmNoClpNoScrCdvt(12)
PCR0+1 CDVT
atmNoClpTaggingNoScr(11)
PCR0+1 CDVT
CLP: Cell Loss Priority.

PCR0+1: Peak Cell Rate of CLP=0+1 (Unit: Cell/Second)
PCR0: Peak Cell Rate of CLP=0 (Unit: Cell/Second)
CDVT: Cell Delay Variation Tolerance (Unit: one tenth microsecond)
SCR0: Sustainable Cell Rate of CLP=0 (Unit: Cell/Second)
SCR0+1: Sustainable Cell Rate of CLP=0+1 (Unit: Cell/Second)
MBS: Maximum Burst Size (Unit: Cell)
MCR: Minimum Cell Rate (Unit: Cell/Second)
3.6.3
Effective Bandwidth of PVC

The effective bandwidth of PVC needs to be calculated based on different service types.
E(X): Refers to the PVC effective bandwidth of service type X (Unit: bps).
1.
Effective bandwidth of CBR service type
The effective bandwidth of CBR service type can be obtained by multiplying 424 by the
traffic parameter 1, which basically means PCR0+1:
64
E(CBR) = (PCR0+1)424
2.
Effective bandwidth of VBR service type
The VBR includes such service types as RTVBR and NRTVBR, so the effective
bandwidth calculation is a bit complicated. The specific calculation methods are
described as follows:
If the CDVT value is contained in the traffic parameter, translate its unit from 1/10
microsecond into second:
CDVT = CDVT/10000000
If there is no SCR in the traffic parameters or there is an SCR but its value is 0, then:
E (VBR) = (PCR0 + 1) 424
If there is non-zero SCR but there is no MBS or CDVT and the sum of PCR and SCR is
less than 4, then:
E (VBR) = 0
If there is non-zero SCR but there is no MBS or CDVT and the sum of PCR and SCR is
not less than 4, then:
E (VBR) = [2*PCR*SCR/ (PCR+SCR)] 424
If there is non-zero SCR and MBS or CDTV, then:
E (VBR) = [PCR*MBS/ (PCR*CDVT+MBS)] 424
3.
Effective bandwidth of ABR service type
E (ABR) = MCR424
4.
Effective bandwidth of UBR service type
E (UBR) = 0
65

(V4)
3.6.4
Configuration Policy
See ZWF22-01-005 Transport CAC Feature Guide.
3.7
ATM Link Redundancy

The link redundancy mechanism of the RNC is adopted in both the physical and logical
link layers.
For the optical access mode at physical link layer, the RNC supports SDH/SONET
multi-path
protection
and
APS
protection
in
either
1+1
or
1:1
mode
(ApsGroup.BackUpMode). The duration required to activate standby link is less than 50

ms in the event of breakdown of the active link.
The APS module conforms to ITU-T G.841 standard, and implements optical interface
(board) protection switching through the two bytes (K1 and K2) carried in the frame
overhead. In either 1+1 or 1:1 protection switching, one protecting entity is specially used
for the protection of one working entity in the protection domain. On the working entity,
the service is transmitted to the destination of the protection domain for handling; on the
protecting entity, K1 and K2 bytes are transmitted for protection of the protection domain.
The Automatic Protection Switching (APS) is triggered in the event of failure of working
entity, the system determines the status of the bridge and selector, and switches to the
protecting entity for service transmission and reception.
The board supports a maximum of four protection groups (ApsGroup.GroupId). The
optical interface of the current board is the protecting optical interface or work optical
interface (S155Port.SetWportFlag) can be selected. The RNC supports both recovery
mode and non-recovery modes (ApsGroup.Revertive) as well as unidirectional and
bi-directional protection modes (ApsGroup.SwitchDirection).
For AAL2 links used to carry user plane data at the logical link layer, the load sharing
mechanism is adopted. In the event of failure of either of two AAL2 logical links, the RNC
will delete backup settings that pass this link, reset link resources through the resource
selection mechanism and select other working AAL2 paths. The restored AAL2 link will
be added into the backup resource.
66
For AAL5 links (PS service) used to carry user plane data at the logical link layer, the
RNC supports two redundancy mechanisms:
1.
Adopt load sharing as AAL2 connections.
2.
Support access of PS resources through IP rerouting.
For signaling links on Iu/Iur interface at logical link layer, the protection mechanism is
established on SS7. If some links are faulty, congested or unavailable, the SS7 will
perform rerouting.
Parameters
4.1
ZWF22-02-001 ATM Transmission stack

Configuration Parameters
Table 4-1
Paramete
r Name
PvcTp.Pv
cSeq
Parameters List
GUI Name
PVC No.
Parameter Description
This parameter specifies the

number of PVC.
Value
Range
Defaul
Unit
t
Value
1..12600 N/A N/A
Reco
mmen
ded
Value
N/A
67

(V4)

service type on PVC. It is used to
coordinate operations between
the PVC and upper-layer
services.
If this parameter is set to AAL5
signaling, AAL5 signaling
services are borne on the PVC.
PvcTp.Pv PVC Service
cService Type
0,1,2,4
N/A N/A
N/A
0..4095
N/A N/A
N/A
N/A N/A
N/A
data, AAL5 data services are

borne on the PVC.
user data, AAL2 user data
If this parameter is set to OMCB,
OMCB network management
PvcTp.CV VPI on High This parameter indicates the VPI

PI
End
of the high-end ATM port.
PvcTp.CV VCI on High This parameter indicates the VCI 32..6553

CI
68
End
This parameter indicates the

service type of a PVC in the
low-end to high-end direction. It
is used to provide different QoS
services to meet the
requirements of services for
delay, jitter and bandwidth
variation on the PVC. Options
include:
CBR: Constant Bit Rate, used in
the connections that require
static bandwidth during the
connection lifespan.
rtVBR: real-time Variable Bit
Rate, which means that the rate
at which the remote end sends
PvcTp.Se
rviceCate
gory
Service
Category
cells is variable.
nrtVBR: non-real-time Variable
0,1,2,4,5 N/A 0
N/A
0..15
N/A
Bit Rate, used to support

unexpected non-real-time
applications to guarantee a low
cell loss rate and an unlimited
delay. ABR: Available Bit Rate. A
traffic control mechanism is used
to control the rate at which the
source end sends cells based on
the feedback from the source
end.
UBR: Undefined Bit Rate.
Services of this type do not have
any QoS guarantee.
UBR+: Undefined Bit Rate+.
Services of this type are similar
to UBR, but this type provides
the lowest rate guarantee.
PvcTp.Tr
afficType

Traffic Type
description parameter of the
N/A N/A
high-end to low-end traffic.
69

(V4)
This parameter indicates whether

to enable the traffic policing
function on a PVC.
To ensure that the actual cell
traffic on a PVC meets the traffic
parameters configured for this
PVC and the transmitting and
PvcTp.Po Policing
licing
receiving of cells on other PVCs
Function Flag are not affected, the system can
0,1
N/A 0
N/A
2,3
N/A 3
N/A
enable the UPC function to

perform the corresponding
handling to the cells that do not
meet the configurations, for
example, mark the CLP in the
cell with a congestion flag, or
drop these cells.
node type of a PVC. It is used to
describe and identify the location
of the currently configured PVC
nodes in the ATM
communication network.
When the local-end device is
connected with the remote-end
PvcTp.Se
gment
VPC(VCC)
Node
Property
device through a PVC, multiple

ATM devices can be used for
PVC forwarding. To facilitate
OAM maintenance and fault
location, the connection between
the local-end device and the
remote-end device can be
divided into several segments.
This parameter only affects OAM
related functions of ATM, for
example, AIS, RDI, CC and
Loopback.
70
This parameter specifies the type

PvcTp.IfT
ype
Interface
of the port where a PVC is
Type of PVC operating. It is used to adapt the 1,2,3,4,6 N/A N/A

Beared
N/A
NE port where a PVC is

operating.
71

(V4)

high-end CC flag. It is used to
enable or disable the high-end
CC function of a PVC.
To enable the high-end CC
function of a PVC, this parameter
should be set to valid. In this
case, parameters including the
high-end cc type, high-end
activation flag and high-end CC
direction take effect.
Options include:
0-invalid
1-valid
If this parameter is set to 0, no
CC information is configured and
the front end does not parse the
follow-up bits.
Continue Check (CC) is used to
detect in real time the status of
the PVC link between two
PvcTp.Cc
Valid
communication nodes. The way

CC Valid Flag
it works is that the local-end
0,1
N/A N/A
N/A
device activates the CC cell

reception check function and
periodically checks whether it
can receive service cells or CC
cells from the remote-end device.
The remote-end device activates
the CC cell transmission function
and periodically sends CC cells.
If the local-end device cannot
receive any CC cells within a
certain period of time due to
transmission problems or the
deletion of the remote-end PVC,
the link is treated as
disconnected. To enable both the
local-end and remote-end
devices to detect and perceive
the status of the communication
link between them, both ends
should activate the CC cell
72
transmission function and the cell

reception check function.

high-end CC flow type. It is used
for in-segment CC check or
end-to-end CC check.
PvcTp.Cc CC Flow
FlowType Type
0,1
N/A 0
N/A
0,1
N/A 0
N/A

Options include:
Segment: If an in-segment CC
check is needed for an ATM
segment, this parameter is set to
Segment.
End-to-end: If a CC check is
needed on both ends of an ATM
connection, this parameter is set
to End-to-end.
PvcTp.Cc
SetFlag
CC Set Flag
high-end activation flag. It is used

to activate or deactivate the
high-end CC function of a PVC.
73

(V4)
This parameter specifies the CC

check direction on the high-end
port of a PVC, including
local-to-remote check,
remote-to-local check and
bidirectional check. In the CC
check, A refers to the local end
and B refers to the remote end.
When this parameter is set to
B->A or A<->B, the CC cell
transmission function on the
remote-end device of the PVC
must be activated. Otherwise,
PvcTp.Cc
Direction
the local-end PVC may become

CC Direction faulty because the CC check
0..3
N/A 0
N/A
times out.
Options include:
B->A: The CC check is
performed on the PVC receiving
direction.
Options include:
A->B: The CC check is
performed on the PVC sending
direction.
Options include:
A<->B: The CC check is
performed on both the PVC
sending and receiving directions.
PvcCross
.PvcSeq
74
PVC No.

number of PVC.
1..12600 N/A N/A
N/A

service type on PVC. It is used to
coordinate operations between
the PVC and upper-layer
services.
signaling, AAL5 signaling
PvcCross
.PvcServi
ce

PVC Service
Type
0,1,2,4
N/A N/A
N/A
0..4095
N/A N/A
N/A
0..65535 N/A N/A
N/A
0..4095
N/A N/A
N/A
0..65535 N/A N/A
N/A
data, AAL5 data services are

borne on the PVC.
user data, AAL2 user data
If this parameter is set to OMCB,
OMCB network management
PvcCross VPI on High This parameter indicates the VPI

.Port2Vpi End
PvcCross VCI on High This parameter indicates the VCI

.Port2Vci End

virtual path ID of the low-end
ATM port of a PVC.
PvcCross
.Port1Vpi
VPI
A PVC is selected according to

the ports, VPIs and VCIs during
ATM cell switching. This
parameter indicates the VPI of
the low-end ATM port.
virtual channel ID of the low-end
ATM port of a PVC.
PvcCross
.Port1Vci
VCI
A PVC is selected according to

the ports, VPIs and VCIs during
ATM cell switching. This
parameter indicates the VCI of
the low-end ATM port.
75

(V4)

service type of a PVC in the
low-end to high-end direction. It
is used to provide different QoS
services to meet the
requirements of services for
delay, jitter and bandwidth
variation on the PVC. Options
include:
CBR: Constant Bit Rate, used in
the connections that require
static bandwidth during the
connection lifespan.
rtVBR: real-time Variable Bit
Rate, which means that the rate
at which the remote end sends
PvcCross
.ServiceC
ategory
Service
Category
cells is variable.
nrtVBR: non-real-time Variable
0,1,2,4,5 N/A 0
N/A
0..15
N/A
Bit Rate, used to support

unexpected non-real-time
applications to guarantee a low
cell loss rate and an unlimited
delay. ABR: Available Bit Rate. A
traffic control mechanism is used
to control the rate at which the
source end sends cells based on
the feedback from the source
end.
UBR: Undefined Bit Rate.
Services of this type do not have
any QoS guarantee.
UBR+: Undefined Bit Rate+.
Services of this type are similar
to UBR, but this type provides
the lowest rate guarantee.
76
PvcCross
.TrafficTy Traffic Type
description parameter of the
pe
high-end to low-end traffic.
N/A N/A
This parameter indicates whether

to enable the traffic policing
function on a PVC.
To ensure that the actual cell
traffic on a PVC meets the traffic
parameters configured for this
PVC and the transmitting and
PvcCross Policing
receiving of cells on other PVCs
.Policing Function Flag are not affected, the system can
0,1
N/A 0
N/A
N/A 0
N/A
enable the UPC function to

perform the corresponding
handling to the cells that do not
meet the configurations, for
example, mark the CLP in the
cell with a congestion flag, or
drop these cells.
node type of a PVC. It is used to
describe and identify the location
of the currently configured PVC
nodes in the ATM
communication network.
PvcCross
.Segment
VPC(VCC)
Node
Property

This parameter only affects OAM
related functions of ATM, for
example, AIS, RDI, CC and
Loopback.
77

(V4)
This parameter identifies a UNI

interface. It is used to determine
whether the ATM port is located
at the UNI or NNI interface.
LogicalAt
According to the ATM protocol,
mPort.Uni UNI flag
the ATM information element of 0,1
NniFlag
the UNI interface contains the
N/A 0
N/A
N/A 1
N/A
0..65535 N/A 1
N/A
0..65535 N/A 1
N/A
0..65535 N/A 1
N/A
0..65535 N/A 1
N/A
1..244
N/A
GFC field and the flow control

mechanism, whereas the ATM
information element of the NNI
interface does not contain them.
AtmOam.
OamLock
Switch of
ATM
OAM Switch of ATM
OAM Function 0,1
Function
This parameter indicates the ID
of an ATM node. The ATM
AtmOam.
LocationI Location Id1 protocol defines a 128-bit ATM

d1
Location ID to identify a unique

ATM node.
AtmOam.

d2

ATM node.
AtmOam.

d3

ATM node.
AtmOam.

d4

ATM node.
LogicalAt
mpPort.B
oardPortS
Local Port
Local Port
N/A N/A
eq
78
4.2
ZWF22-02-008 Inverse Multiplexing over ATM, IMA

Table 4-2
Parameters List
Reco
Paramete
r Name
GUI Name
Value
Range
Defaul mme
t
Unit
nded
Value Valu
e
This parameter indicates the unique

ImaLink.S Ima Link
ID of each IMA link in the IMA chip. It
184
N/A N/A
N/A
No. in the unit. The value configured 1..672
N/A N/A
N/A
No. in the unit. The value configured 1672 N/A N/A
N/A
eqInChip No. in Chip is set to uniquely identify an IMA link

in the IMA chip.
LogicalE1.
LogicalE1
Seq
LogicalT1.
LogicalT1
Seq
Logical E1
No
Logical T1
No
This parameter indicates the subunit

should be unique.
This parameter indicates the subunit
should be unique.
ImaLink.S
CRAMBL
ETYPE
Scramble
Type
scramble type. It is set to enhance

E1/T1 transmission reliability. It must 0,1,255 N/A 0
be consistent with that configured in

the peer end.
ImaChip.I
maChipSe
q
ImaGroup
.GROUPS
EQ
IMA Chip
No.
IMA Chip No.
IMA Group This parameter indicates the unique

No.
ID of the IMA group in the IMA chip.
14
N/A N/A
N/A
142
N/A N/A
N/A
12
N/A 2
N/A
This parameter indicates the IMA

ImaGroup
.ImaVersi
on
protocol version number of the local

IMA
OAM label. It is used to notify the
Version
remote IMA group of the

currently-supported IMA version
number during the negotiation.
79

(V4)
Reco
Paramete
r Name
GUI Name
Value
Range
Defaul mme
t
Unit
nded
Value Valu
e
The currently-supported IMA protocol

version numbers are as follows:
V1.0: IMA 1.0 is used.
V1.1: IMA 1.1 is used.
Near End
This parameter indicates the local
ImaGroup IMA Group transmitting clock of the IMA group. It

01
N/A 1
N/A
of active IMA links in the transmitting 1..32
N/A 1
NA
132
N/A 1
N/A
02
N/A 0
N/A
.NETXCL Transmit
is used to specify the clock for the
KMD
Clocking
IMA group, which must be consistent
Mode
with that of the remote IMA group.
Minimal
number of
active IMA
link in the
ImaGroup
.MINTXLK
S
transmit
direction
needed by
the IMA
group to
move to

minimum number of active
transmitting links. When the number
direction of the IMA group reaches
this parameter, the IMA group is in the
working state.
operational
state
Minimal
number of
active IMA
ImaGroup
.MINRXL
KS
link in the
receive
minimum number of active receiving
direction
links. When the number of active IMA
needed by links in the receiving direction of the

the IMA
IMA group reaches this parameter,
group to
the IMA group is in the working state.
move to
operational
state
80
ImaGroup Near End
.NESYME Group
symmetry of an IMA group at the local
Reco
Paramete
r Name
GUI Name
Value
Range
Defaul mme
t
Unit
nded
Value Valu
e
TRY
Symmetry end. The IMA protocol allows you to

Modes
configure symmetrical and

asymmetrical information element
transmission rates for virtual IMA
links.
At the local end, the symmetry types
of IMA groups include:
Symmetrical configuration and
symmetrical operation: The IMA
group must be configured with a
bidirectional IMA link. ATM
information elements can be
transmitted only when the IMA link is
a bidirectional link.
Symmetrical configuration and
asymmetrical operation: The IMA
group must be configured with a
bidirectional IMA link. The IMA group
allows ATM information elements to
be transmitted over a unidirectional
activated IMA link.
Asymmetrical configuration and
asymmetrical operation: The IMA
group can be configured with a
bidirectional or unidirectional IMA link.
The IMA group allows ATM
information elements to be
transmitted over a bidirectional or
unidirectional activated IMA link.
IMA Frame
ImaGroup Length in
.TXFRAM the
LGTH
Transmit
Direction
This parameter indicates the length of

a frame sent by the IMA group. It is
used to configure the number of ATM
information elements in an IMA frame
03
N/A 2
N/A
sent by the IMA group.

The length of an IMA frame can be
81

(V4)
Reco
Paramete
r Name
GUI Name
Value
Range
Defaul mme
t
Unit
nded
Value Valu
e
one of the following values:

M32: Frame length is 32, unit is cell
(Each IMA frame contains 32 ATM
information elements.)
M64: Frame length is 64, unit is cell
(Each IMA frame contains 64 ATM
information elements.)
M128: Frame length is 128, unit is
cell (Each IMA frame contains 128
ATM information elements.)
M256: Frame length is 256, unit is
cell (Each IMA frame contains 256
ATM information elements.)
maximum delay allowed by the IMA
group. It is used to configure the
maximum inter-link differential delay
ImaGroup Maximum
.DIFFDEL Delay for
AYMAX
IMA group
allowed by the IMA group. If the time

delay for receiving packets between 2520
the links in the IMA group exceeds the 0
Ms
25
N/A
maximum time delay, received

packets are discarded, and a LODS
alarm is raised. If the quality of a
transmission link is poor, this
parameter needs to be increased.
Unit.UnitS
eq
82
Unit No.
Unit Sequence Number
1..42
N/A N/A
N/A
4.3
ZWF22-02-051
ATM over E1 & ZWF22-02-052
ATM over T1 Configuration Parameters

Table 4-3
Parameters List
Reco
Paramete
r Name
GUI Name
Value
Range
Defaul mme
t
Unit
nded
Value Valu
e
This parameter specifies the type of a

port on a board. Options:
1: SDH-63E1, optical E1 port
2: SDH-63T1, optical half T1 port
Board.Ext
PortType
Port Type 3: SDH-84T1, optical full T1 port
08
N/A N/A
N/A
0,1,3
NA
NA
0,1,3
NA
NA
4: POS, optical POS port

5: ATM, optical ATM port
6: E1, electrical E1 port
7: T1, electrical T1 port
E1Port.Wir E1 long or
eType
short haul
E1Port.Im E1
pedance
This parameter indicates whether the

physical E1 cable used is a long or
short cable.
Impedance impedance of the physical E1 cable.

This parameter indicates the Cyclic
Redundancy Check (CRC) 4
operating mode of the E1 connected
to the port. The CRC is used to
improve the systems ability to detect
error codes. For the detailed definition
E1Port.CR E1 Frame
C4MODE Type
of the CRC, refer to G.704.
0,1,4,6 N/A 6
Multi-Frame: Multi-frame loss alarms

are not detected.
Multi-Frame with checked:
Multi-frame loss alarms are detected,
but the RAI is not inserted in the
feedback and the E1 is not blocked.
83

(V4)
Reco
Paramete
r Name
GUI Name
Value
Range
Defaul mme
t
Unit
nded
Value Valu
e
Forced Multi-Frame: Multi-frame loss

alarms are detected, and the RAI is
inserted in the feedback and the E1 is
blocked.
T1Port.Wir T1 long or
eType
short haul
T1Port.Im T1
pedance
dingForma
4.4
physical T1 cable used is a long or
T1 Coding This parameter indicates the T1

Format
0,1,3
N/A 0
N/A
0,3
N/A 0
N/A
0,1,2,7 N/A 7
N/A
short cable.
Impedance impedance of the physical T1 cable.
T1Port.Co
t
coding format.
ZWF22-02-054
ATM over Optical STM-1/OC-3 &
ZWF22-02-055
ATM over Channelized
&STM-1/OC-3 Configuration Parameters

Table 4-4
Parameters List
Reco
Parameter
Name
GUI Name
Value
Range
Defaul mme
t
Unit
nded
Value Valu
e

synchronization state. It
S155Port.S Synchronizati indicates the level of the clock
1
on Status
source contained in the signal

sent from the local-end port.
0,1,2,4,7,
8,10,11,1 N/A 0
N/A
2,14,15
Options include:
84
Reco
Parameter
Name
GUI Name
Value
Range
Defaul mme
t
Unit
nded
Value Valu
e
0: Quality unknown (Existing

Synchronization Network)
(Default)
1: Stratum 1 Traceable
2: ITU-T Rec.G.811
4: SSU-A
8: SSU-B
11: SETS
12: SONET minimum clock
traceable
14: Reserved for Network
Synchronization
15: Dont use for synchronization
alarm threshold of received
signal failure. When the bit error
rate of the signal received on the
optical port reaches the
S155Port.S Signal Fail
threshold set here, an SF alarm
is raised and the corresponding
Threshold
3,4
N/A 4
N/A
N/A 6
N/A
E1 is blocked. Options include:

3: 1e-3. The threshold of the
error bit rate is 1e-3 (0.0001)
4: 1e-4. The threshold of the
error bit rate is 1e-4 (0.0001)
alarm threshold of received
S155Port.S
D
Signal
signal degradation. When the bit
Degradation error rate of the signal received 59

Threshold
on the optical port reaches the

threshold set here, an SD alarm
is raised.
85

(V4)
Reco
Parameter
Name
GUI Name
Value
Range
Defaul mme
t
Unit
nded
Value Valu
e

mode of configuring the
regenerator section trace. It
works together with J0 to
determine the content of the
S155Port.J
0MODE
J0 Trail
regenerator section trace
Identifier Byte message. The regenerator

Mode
1,16
N/A 1
N/A
N/A
N/A 01
N/A
0,1,255
N/A 0
N/A
N/A 16
N/A
section trace message is used to

identify the signal on a port. It is
identified and matched on both
interconnection ends. An alarm
is raised when a mismatch
occurs.
value of the regenerator section
trace message. It works together
with J0 to determine the content
S155Port.J
0
J0 Trail
Identifier
Message
of the regenerator section trace

message. The regenerator
section trace message is used to
identify the signal on a port. It is
identified and matched on both
interconnection ends. An alarm
is raised when a mismatch
occurs.
This parameter specifies E1/T1
S155Port.P
cmMapTyp
e
sorting mode of SDH/SDONET.

PCM Map
Type
Options include:
0: ITUT-G.707 type
1: Tributary type
Sts1Trail.J1
MODE
High path trail mode of configuring the

identifier byte high-order path trace. It works 16,64
mode
together with J1 to determine the
content of the high-order path
86
Reco
Parameter
Name
GUI Name
Value
Range
Defaul mme
t
Unit
nded
Value Valu
e
trace message. The high-order

path trace message is used to
identify signal. It is identified and
matched on both interconnection
ends. An alarm is raised when a
mismatch occurs.
Options include:
16: 16 bytes mode (Default)
64: 64 bytes -mode
value of the high-order path
with J1Mode to determine the
High path trail content of the high-order path
Sts1Trail.J1 identifier
message
trace message. The high-order N/A
N/A 0x00
N/A
0,1,2,3
N/A 1
N/A
16,64
N/A 16
N/A

mismatch occurs.
high-order path signal flag.
Options include:
Sts1Trail.C High path

2
label
0: Unequipped or
supervisory-unequipped
1: Equipped-non-specific
(Default)
2: TUG structure
3: Locked TU-n
Vt15Trail.J2
MODE
Low path trail mode of configuring the

identifier byte low-order path trace. It works
mode

content of the low-order path
87

(V4)
Reco
Parameter
Name
GUI Name
Value
Range
Defaul mme
t
Unit
nded
Value Valu
e
trace message. The low-order

mismatch occurs.
Options include:
64: 64 bytes -mode
value of the low-order path trace
message. It works together with
J2Mode to determine the
Low path trail content of the low-order path
Vt15Trail.J2 identifier
message
N/A
N/A 0x00
N/A
0,1,2,4
N/A 2
N/A
16,64
N/A 16
N/A

mismatch occurs.
low-order path signal flag. It
indicates the payload type. For
more information, refer to G.707.
Vt15Trail.V Low path
Options include:
0: Unequipped or
label
2: Asynchronous (Default)
4: Byte synchronous
Vt2Trail.J2
MODE
88
Low path trail

identifier byte
mode

low-order path trace. It works
Reco
Parameter
Name
GUI Name
Value
Range
Defaul mme
t
Unit
nded
Value Valu
e

mismatch occurs.
Options include:
64: 64 bytes -mode
Vt2Trail.J2 identifier
message
N/A
N/A 0x00
N/A
0,1,2,4
N/A 2
N/A
16,64
N/A 16
N/A

mismatch occurs.
Vt2Trail.V5
Low path
Options include:
label
0: Unequipped or
4: Byte synchronous
Sts3Trail.J1
MODE
High path trail This parameter specifies the

identifier byte mode of configuring the
mode
high-order path trace. It works
89

(V4)
Reco
Parameter
Name
GUI Name
Value
Range
Defaul mme
t
Unit
nded
Value Valu
e

mismatch occurs.
Options include:
64: 64 bytes -mode
Sts3Trail.J1 identifier
message
N/A 0x00
N/A
N/A 1
N/A

mismatch occurs.
high-order path signal flag. For
Options include:
0: Unequipped or
Sts3Trail.C High path
0,1,19,22
,207
label
(Default)
2: TUG structure
3: Locked TU-n
19: ATM mapping
22: Mapping of HDLC/PPP [12],
90
Reco
Parameter
Name
GUI Name
Value
Range
Defaul mme
t
Unit
nded
Value Valu
e
[13] framed signal, see

G.707-10.3
207: POS
Vc3Trail.J1
MODE

High path trail path trace message is used to
identifier byte identify signal. It is identified and 16,64
mode
N/A 16
N/A
N/A 0x00
N/A
N/A 1
N/A

mismatch occurs.
Options include:
64: 64 bytes -mode
Vc3Trail.J1 identifier
message

mismatch occurs.
high-order path signal flag.
Vc3Trail.C2
High path
Options include:
label
0: Unequipped or
0,1,2,3
91

(V4)
Reco
Parameter
Name
GUI Name
Value
Range
Defaul mme
t
Unit
nded
Value Valu
e
(Default)
2: TUG structure
3: Locked TU-n
Low path trail path trace message is used to
Vc11Trail.J
2MODE
mode
N/A 16
N/A
N/A
N/A 0x00
N/A
0,1,2,4
N/A 2
N/A

mismatch occurs.
Options include:
64: 64 bytes -mode
Vc11Trail.J
2

identifier
message

mismatch occurs.
Vc11Trail.V Low path
label
Options include:
0: Unequipped or
92
Reco
Parameter
Name
GUI Name
Value
Range
Defaul mme
t
Unit
nded
Value Valu
e
4: Byte synchronous
Vc3Vc12Tr
ail.J2MODE
mode
N/A 16
N/A
N/A 0x00
N/A
N/A 2
N/A

mismatch occurs.
Options include:
64: 64 bytes -mode
Vc3Vc12Tr
ail.J2

identifier
message
N/A

mismatch occurs.
Vc3Vc12Tr Low path
ail.V5
label

indicates the payload type. For 0,1,2,4
Options include:
93

(V4)
Reco
Parameter
Name
GUI Name
Value
Range
Defaul mme
t
Unit
nded
Value Valu
e
0: Unequipped or
4: Byte synchronous
Vc4Trail.J1
MODE

High path trail path trace message is used to
mode
N/A 16
N/A
N/A 0x00
N/A
N/A 1
N/A

mismatch occurs.
Options include:
64: 64 bytes -mode
Vc4Trail.J1 identifier
message

mismatch occurs.
Vc4Trail.C2
High path
high-order path signal flag. For 0,1,2,3,1
label
more information, refer to G.707. 9,22,207

Options include:
94
Reco
Parameter
Name
GUI Name
Value
Range
Defaul mme
t
Unit
nded
Value Valu
e
0: Unequipped or
(Default)
2: TUG structure
3: Locked TU-n
19: ATM mapping
22: Mapping of HDLC/PPP [12],
[13] framed signal, see
G.707-10.3
207: POS
Vc12Trail.J
2MODE
mode
N/A 16
N/A
N/A 0x00
N/A

mismatch occurs.
Options include:
64: 64 bytes -mode
Low path trail J2Mode to determine the
Vc12Trail.J
identifier
N/A
2
message
95

(V4)
Reco
Parameter
Name
GUI Name
Value
Range
Defaul mme
t
Unit
nded
Value Valu
e

mismatch occurs.
Vc12Trail.V Low path
Options include:
0: Unequipped or
label
0,1,2,4
N/A 2
N/A
N/A 16
N/A
N/A 0x00
N/A
4: Byte synchronous
Vc4Vc11Tr
ail.J2MODE
mode
mismatch occurs.
Options include:
64: 64 bytes -mode
Vc4Vc11Tr
ail.J2
Low path trail

identifier
message

N/A

96
Reco
Parameter
Name
GUI Name
Value
Range
Defaul mme
t
Unit
nded
Value Valu
e

mismatch occurs.
Vc4Vc11Tr Low path
Options include:
ail.V5
0: Unequipped or
label
0,1,2,4
N/A 2
N/A
06
N/A N/A
N/A
4: Byte synchronous
When the port type is set to an
optical port, this parameter
indicates the multiplex structure
Board.SdhP
ortMuxMod
e
Multiplex
of the port. Options:
structure of
1: SDH AU-4
the optical
2: SDH AU-3
port
3: SONET STS-1
4: SONET STS-3C
5: SDH AU-4-4C
6: SONET STS-12C
97

(V4)
4.5
ZWF22-02-003 Dynamic AAL2 Connections

Table 4-5
Parameters List
Defa Reco
Paramete
r Name
GUI Name
Value
Range
Uni ult mmen

t
Valu ded
e
Value
This parameter indicates the AAL2

path ID in the adjacent office. As the
Aal2PathT
p.Aal2Pat
hSeq
Path ID in
Office
local office is connected with multiple

adjacent offices through AAL2 paths,
this parameter is combined with ANI
1..42949
67295
N/A N/A N/A
to describe the different AAL2 path ID

in the local office.
path type.
Aal2PathT
p.Aal2Pat Path Type 1: Stringent Class

hClass
1,2,5
N/A 1
N/A
0,1
N/A 0
N/A
0,1
N/A N/A N/A
2: Tolerant Class
5: Stringent bi-level Class
In an AAL2 path, totally 247 channels
can be used, with value range 8-255.
When this parameter is configured to
the local office, the channel resources
are numbered from 8 in ascending
order. When this parameter is
Aal2PathT
p.Owner
configured to the adjacent office, the

Ownership channel resources are numbered
from 255 in descending order.
This parameter identifies the home
attribute of the AAL2 path. If the local
end of a link is configured to the local
office, the opposite end must be
configured to the adjacent office to
avoid resource conflicts.
Aal2PathT Whether
The parameter indicates whether the
p.IubUseF Supported AAL2 transmission path can be used
98
Defa Reco
Paramete
r Name
GUI Name
Value
Range
Uni ult mmen

t
Valu ded
e
lag
Iub
Value
by Iub Interface.
Interface
Aal2PathT
p.IuCSUs
eFlag
Whether
Supported
IuCS
Interface
Aal2PathT Whether

AAL2 transmission path can be used 0,1
by Iur Interface.
p.IurUseFl Supported AAL2 transmission path can be used 0,1

ag
al2ApSeq ID
office ID.
Whether
.UseFlag
protocol or 0: Q.2630.2
not supported
not
supported
Use Flag
1..1499
N/A N/A N/A
0,1
N/A 0
N/A
0,1
N/A 1
N/A
0,1
N/A 0
N/A
Aal2Ap.S supporting local office supports the Q.2630.2

ptQ26302 Q.2630.2 protocol.
Aal2Route
N/A N/A N/A
Iur Interface by IuCS Interface.
Aal2Ap.A NE Office
Flag
N/A N/A N/A
1: Q.2630.2
This parameter indicates whether to

use the ATM static route.
This parameter is a switch that
determines whether the peer-end
UIurLink.S
ptAal2Swi
tch
Whether
RNC can be used as an AAL2 switch.
AAL2
If the switch is turned on, the
Server or
peer-end RNC can receive and
not
forward ALCAP messages in which

the destination ATM address is not
the address of this RNC.
99

(V4)
4.6
ZWF22-02-004 Permanent AAL5 Connections

Table 4-6
Parameters List
Reco
Paramete
r Name
GUI Name
Value
Uni
Range
Defaul mme
t
nded
Value Valu
e
The global links at the UNI side

UniSaalTp
.LinkSeq
Signalling link No.
and NNI side in the local office

are numbered by using this
1..9000
N/A N/A
N/A
1..9000
N/A N/A
N/A
1..12600 N/A N/A
N/A
1..12600 N/A N/A
N/A
parameter.
global ID of the signalling link,
which identifies the unique
Sl.SlSeq
Signalling link
signalling link in the local office.
number
The signalling link refers to a

physical link that connects
each signalling link point and
transmits signalling messages.
PvcTp.Pv
cSeq
PvcCross.
PvcSeq
NniSaalTp
.AppType
UniSaalTp
.AppType
PVC No.
PVC No.

number of PVC.
number of PVC.
Application type
application type of broadband 3
N/A 3
N/A
N/A 1
N/A
N/A N/A
N/A
signalling links.
Application type
application type of broadband 1,2

signalling links.
This parameter indicates the IP
IpoAtmLin
k.DestIpA
ddr
Destination IP
Address
address of the remote

equipment. If the IPOA link is
NA
required to transfer IP packets

to a remote device, set this
100
Reco
Paramete
r Name
GUI Name
Value
Uni
Range
Defaul mme
t
nded
Value Valu
e
parameter to the IP address of

the remote device.
network segment of the remote
equipment. If the IPOA link is
IpoAtmLin
k.DestIpA
ddrMaskL
en
Destination IP
required to transfer IP packets
Address Mask
to a remote device in a
Length
specified network segment, set
0..32
N/A N/A
N/A
this parameter to the IP

address mask of the remote
device.
4.7
ZWF22-02-006 ATM Link Redundancy

Table 4-7
Parameters List
Reco
Paramete
r Name
GUI Name
Value
Uni
Range
Defaul mme
t
nded
Value Valu
e
ApsGroup
.GroupId

APS Group ID
number of an APS protection
1..8
N/A N/A
N/A
N/A 1
N/A
group.
This parameter indicates
whether to enable an optical
S155Port.
SetWport
Flag
Fiber Switch on
or off
port.
This parameter is used based on 0,1
Bit. Bit0 indicates the
enablement of the working port,
and Bit1 indicates the
101

(V4)
Reco
Paramete
r Name
GUI Name
Value
Uni
Range
Defaul mme
t
nded
Value Valu
e
enablement of the protection

port. Other Bits do not have a
practical use. Options include:
Bit0/1=0: optical port unused
Bit0/1=1: optical port is used
protection mode of a protection
group. Options:
1. Protection mode 1:N
(Currently, N is equal to 1.):
ApsGroup
.BackupM Protection Type
ode
Successful APS negotiation is
1..2
N/A 1
N/A
switchover is performed only in 1..2
N/A 2
N/A
N/A 1
N/A
required before switchover.

2. Protection mode 1+1:
Switchover is performed once a
fault is detected without waiting
for the completion of APS
negotiation.
protection direction. It indicates
the switchover mode of an
optical port. Options include:
1. Unidirectional switchover:
ApsGroup
.SwitchDir
ection
Protection
direction
When a receiving fault occurs,

the receiving direction.
2: Bidirectional switchover:
When a receiving fault occurs,
switchover is performed in both
the receiving and sending
directions.
After the working port is
ApsGroup
.Revertive
Revertible mode
switched over to the standby

port due to faults, if the fault is
1..2
troubleshot, the working port
102
Reco
Paramete
r Name
GUI Name
Value
Uni
Range
Defaul mme
t
nded
Value Valu
e
should be switched back to the

original port. This parameter
specifies the switchback mode.
Options include:
1: Revertive mode: After the
fault on the working port is
troubleshot for five minutes (The
period of time can be set in the
WTRTime field), the working
port is automatically switched
back to the original port. The
switchback does not need to be
triggered by the fault on the
protection port.
2: Non-revertive mode: After the
fault on the working port is
troubleshot, the working port is
not automatically switched back
to the original port, except when
a fault on the protection port is
detected or switchback is
performed manually.
Related Counters and Alarms
5.1
Related Counters
Table 5-1
Counter List
Counter ID
C380200011
Name
Unavailable seconds for IMA group state machine
103

(V4)
C380200012
The number of NE group failure reported
C380200013
The number of FE group failure reported
C380220003
The number of received ATM cells of High end Vcc
C380220004
The number of transmited ATM cells of High end Vcc
C380220013
The number of ATM cells received on high port when policy is

disabled
C380220014
The number of ATM cells received on high port when policy is

enabled
C380220015
The number of ATM cells discarded on high port because of

UPC or NPC
C380220016
The number of ATM cells with clp tag on high port because of
UPC or NPC
C380220017
The number of ATM CC cells received from high port
C380220018
The number of ATM AIS cells received from high port
C380220019
The number of ATM RDI cells received from high port
C380220020
The number of ATM cells discarded because of buffer

overflow on high port
104
C380230001
The number of ingress ATM cells
C380230002
The number of egress ATM cells
C380300001
number of CRC4 Block Error
C380300002
CRC4 Error Second
C380300003
CRC4 Severely Error Second
C380300004
CRC4 unavailable Second
C380300005
CRC4 available Second
C380300006
number of FAS Block Error
C380300007
FAS Error Second
C380300008
FAS Severely Error Second
C380300009
FAS unavailable Second
C380300010
FAS available Second
C380300011
number of EBIT Block Error
C380300012
EBIT Error Second
C380300013
EBIT Severely Error Second
C380300014
EBIT unavailable Second
5.2
C380300015
EBIT available Second
C380720001
Number of CRC6 background block error
C380720002
CRC6 errored second
C380720003
CRC6 severely errored second
C380720004
CRC6 unavailable second
C380720005
CRC6 available second
C380720006
Number of FAS bit error
C380720007
FAS errored second
C380720008
FAS severely errored second
C380720009
FAS unavailable second
C380720010
FAS available second
C380660004
Number of aal2 type atm cell received
C380660005
Number of CPS-PDU transmitted to CPS sublayer
C380660017
Number of CPS-PKT received with UUI error
C380670003
Number of SAR-PDU received
C380670004
Number of SAR-PDU received with AUU is 0
C380670005
Number of SAR-PDU received with AUU is 1
C380670010
Number of CPCS-PDU received with CRC error
C380670017
Number of CPCS-PDU dropped due to buffer overflow
Related Alarms
Table 5-2
Alarm List
Alarm Code
Alarm Name
199001026
Cell delineation do not synchronization about cell on E1/T1 link
199001792
SDH/SONET:Loss of signal
199001793
SDH/SONET:Loss of frame
199001794
SDH/SONET:Regenerator section trace mismatch/Section trace

mismatch
105

(V4)
199001795
SDH/SONET:MS alarm indication signal/Line alarm indication

signal
199001796
SDH/SONET:MS far-end reception failure/Line far-end reception

failure
199001797
SDH/SONET:Signal failure
199001798
SDH/SONET:Signal deterioration
199001799
SDH/SONET:Loss of AU pointer/Loss of path pointer
199001800
SDH/SONET:AU alarm indication signal/Path alarm indication

signal
199001801
SDH/SONET:HP trace mismatch/ Path trace mismatch
199001802
SDH/SONET:HP unequipped/Path unequipped
199001803
SDH/SONET:HP label mismatch/Path label mismatch
199001804
SDH/SONET:HP remote reception failure/Path remote reception

failure
199001805
SDH/SONET:Loss of multi-frame
199001806
SDH/SONET:Loss of TU pointer/Loss of virtual tributary pointer
199001807
SDH/SONET:Tributary unit alarm indication signal/Virtual

tributary alarm indication signal
199001808
SDH/SONET:LP remote defect indication/Virtual tributary remote

defect indication
199001809
SDH/SONET:LP remote failure indication/Virtual tributary remote

failure indication
106
199001810
SDH/SONET:LP trace mismatch/Virtual tributary trace mismatch
199001811
SDH/SONET:LP unequipped/Virtual tributary unequipped
199001812
SDH/SONET:LP label mismatch/Virtual tributary label mismatch
199001816
SDH/SONET:Severely B1 error code
199001817
199001818
199001819
SDH/SONET:Severely BIP-2 error code
199001820
SDH/SONET:MS remote error indication
199001821
SDH/SONET:HP remote error indication
199001826
SDH/SONET:LP remote error indication
199005773
High CRC error rate at E1/T1 bottom layer
199005774
High FAS error rate at E1/T1 bottom layer
199005775
High EBIT error rate at E1 bottom layer
199018944
The state of PVC link is faulty
199019223
Near-end IMA group fault
199019264
Fail to operate IMA group
199019008
Fail to configure the ATM port
199019207
Fail to config near-end IMA group
199019208
Fail to fix the time of near-end IMA group
199019264
Fail to operate IMA group
199019265
Fail to operate the link of the IMA group
199019712
APS channel mismatch
199019713
APS mode mismatch
199019715
APS channel between master and slave board gets errors
199019777
APS switchover happens
199041473
Fail to configure the ATM PVC
199041737
Near-end TC link fault
199041794
Fail to operate TC link
Abbreviation
Abbreviations
Full Characteristics
AAL2
ATM Adaptation Layer specification: Type 2
AAL5
ATM Adaptation Layer specification: Type 5
ATM
Asynchronous Transfer Mode
CAC
Connection Admission Control
CBR
Constant Bit Rate
CID
Cell ID
CS
Circuit Switched
IMA
Inverse Multiplexing for ATM
NBAP
Node B Application Part
107

(V4)
OMC-R
Operation and Maintenance for Radio
PCM
Pulse Code Modulation
PS
Packet Switched
QoS
Quality of Service
R99
Release 99
RAB
Radio Access Bearer
RAN
Radio Access Network
RLC
Radio Link Control
RNC
Radio Network Controller
rt-VBR
real-time Variable Bit Rate
SSCOP
Service
TC
Transmission Convergence
UBR
Unspecified Bit Rate
UBR+
Unspecified Bit Rate Plus
UNI
User-Network Interface
UTRAN
UMTS Terrestrial Radio Access Network
Specific
Connection Oriented Protocol
Reference Document
[1]ZXUR 9000 UMTS (V4.13.10.15) Radio Network Controller Radio Parameter
Reference
[2]ZXUR 9000 UMTS (V4.13.10.15) Radio Network Controller Ground Parameter
Reference
[3]ZXUR 9000 UMTS (V4.13.10.15) Radio Network Controller Performance Counter
Reference
108

UMTS RNC ATM Transmission Feature Guide

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

UMTS RNC ATM Transmission Feature Guide

Enviado por

Direitos autorais:

Formatos disponíveis

RNC ATM Transmission (V4)

RNC ATM Transmission (V4)

RNC ATM Transmission (V4)

2014 ZTE Corporation. All rights reserved.

ZTE Confidential Proprietary

RNC ATM Transmission

Feature Attribute ............................................................................................... 6

Technical Description ..................................................................................... 10

ZTE Confidential Proprietary

RNC ATM Transmission (V4)

Configuration Policy ........................................................................................... 66

Related Counters and Alarms ...................................................................... 103

Abbreviation .................................................................................................. 107

Reference Document..................................................................................... 108

ZTE Confidential Proprietary

RNC ATM Transmission

ZTE Confidential Proprietary

RNC ATM Transmission (V4)

ZTE Confidential Proprietary

RNC ATM Transmission

ZWF22-02-001 ATM Transmission Stack

ZTE Confidential Proprietary

RNC ATM Transmission (V4)

ATM Transmission Interfaces

Interfaces applicable to ATM transmission

Iub, Iur, Iu-CS, Iu-PS

Iub and Iur interfaces are

Iub, Iur, Iu-CS, Iu-PS

Iub and Iur interfaces are

Iub, Iur, Iu-CS, Iu-PS

Iub and Iur interfaces are

Iub, Iur, Iu-CS, Iu-PS

Iur, Iu-CS and Iu-PS interfaces

Iub, Iur, Iu-CS, Iu-PS

Iub and Iur interfaces are

ZTE Confidential Proprietary

RNC ATM Transmission

ZWF22-02-002 PVC Cross Connection

ZWF22-02-003 Dynamic AAL2 Connections

ZWF22-02-004 Permanent AAL5 Connections

ZTE Confidential Proprietary

RNC ATM Transmission (V4)

ZWF22-02-005 AAL2 Quality of Service separation

ZWF22-02-006 ATM Link Redundancy

License Control List

ATM Transmission stack

PVC Cross Connection

ATM Link Redundancy

ZTE Confidential Proprietary

RNC ATM Transmission

ATM over Optical

Correlation with Other Features

ATM Transmission stack

ZTE Confidential Proprietary

RNC ATM Transmission (V4)

ATM protocol stack on Iu-CS interface

ZTE Confidential Proprietary

RNC ATM Transmission

ATM protocol stack on Iu-PS interface

ZTE Confidential Proprietary

RNC ATM Transmission (V4)

ATM protocol stack on Iur interface

ZTE Confidential Proprietary

RNC ATM Transmission