ZWF22!02!001 ATM Transmission Stack - V3

Feature Deployment and Testing Guide
ATM Transmission stack_V3

Feature ID: ZWF22-02-001
Version: V3.11.10
ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright 2012 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided as is, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.
Revision History
Revision No. Revision Date Revision Reason
R1.0 20120806 First Edition
Serial Number: SJ-20120802112720-120
Publishing Date: 2012-08-06 (R1.0)
SJ-20120802112720-120|2012-08-06 (R1.0) ZTE Proprietary and Confidential

Chapter 1
Functional Description
The 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 from any user can be transmitted intermittently rather than
in a steady stream.
Combining the advantages of circuit and packet switching, ATM is capable of carrying
several types of information media and communication services with guaranteed QoS.
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, IuCS
interface and IuPS interface.
Overview
According to 3GPP, the ATM protocol stacks on various interfaces are respectively shown
in the following figures. ZTE UMTS is completely 3GPP-compliant.
1-1

Feature Deployment and Testing Guide Feature ID: ZWF22-02-001
Figure 1-1 ATM protocol stack on IuCS interface
1-2

Chapter 1 Functional Description
Figure 1-2 ATM protocol stack on IuPS interface
1-3

Figure 1-3 ATM protocol stack on Iur interface
1-4

Figure 1-4 ATM protocol stack on Iub interface
ATM Protocol
The ATM protocol combines the benefits of both circuit and packet switching. On the one
hand, it features Simple Handling of circuit switching, supports real-time transparent
transmission of service and data without complicated data handling and adopts end-to-end
communication protocol; on the other hand, it is characteristic of packet switching, for
example, it supports variable bit rate service, and adopts statistical TDM for services
transmitted on links.
1. ATM cell header format]
The figure shows the ATM cell header format:
1-5

Figure 1-5 ATM cell header format
ATM cell header is composed of the following:
Table 1-1 Payload type
GFC 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.
VPI Virtual Path Identifier (VPI): 12 bits for NNI and

8 bits for UNI.
VCI Virtual Channel Identifier (VCI): 16 bits. It iden-

tifies virtual channels on a virtual path. In con-
junction with the VPI, the VCI identifies a virtual
connection.
PTI Payload Type Indicator (PTI): 3 bits. It is used

to indicate cell type.
CLP Cell Loss Priority (CLP): One bit. Indicates

whether the cell should be discarded if it en-
counters 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.
HEC Header Error Control (HEC): 8 bits. It can be

used to correct the error of bit 1 in cell header.
The HEC is also used for cell delimitation. The
cell header position is identified through the rel-
evance between HEC and first 4 bytes of the
header.
1-6

2. Reference model
The ATM reference model contains a user plane, a control plane and a management
plane.
a. The user plane is used to transmit user information, including service-specific
protocol, data, voice and video information.
b. The control plane is used to implement call control and connection control. It
establishes, manages and releases calls and connections through signaling
handling.
c. 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 1-6 ATM protocol model
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.
1-7

Figure 1-7 Data transmission among layers
Protocol Control Information (PCI): PCI may contain header and tail.
The table lists the functions of all layers and their respective sub-layers:
Table 1-2 Functions of various layers and their respective sub-layers
High layer Function of high layer
1-8

AAL CS sub-layer Convergence: That

is, to transform ser-
vice data into CS data
units.
SAR sub-layer Segmentation and re-

assembly: To seg-
ment or reassemble
CS data based on
cells at this layer.
ATM layer GFC Cell header gen-

eration/extraction;
Cell VP/VC switching.
Cell multiplexing and

demultiplexing.
Physical Layer TC sub-layer Cell rate decoupling

HEC cell header
sequence genera-
tion/check Cell de-
limitation Transmis-
sion frame adaptation
Transmission frame
generation/recovery
PM sub-layer Bit timing Physical

media
The functions of all layers are described as follows:

l Physical Layer
The physical layer is the carrier of information stream. It contains the
Transmission Convergence (TC) sub-layer and Physical Media-Dependent
(PMD) sub-layer.
a. TC sub-layer
The TC sub-layer 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: ATM cell
demodulation (buffer) HEC generation Cell delimitation Transmission
frame adaptation Generation of transmission frame. The procedure for
extracting valid ATC layer cells from transmission frame: Transmission frame
receiving Transmission frame adaptation Cell delimitation HEC
verification ATM cell queuing. The main functions of TC sub-layer are cell
delimitation and HEC.
1-9

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.
b. PMD sub-layer
The PMD sub-layer implements its functions in accordance with ITU-T and
ATM F recommendation, and contains the following types of connections:
i. Connection based on direct cell transmission.
ii. Connection based on PDH network transmission.
iii. Connection based on SDH network transmission.
iv. Direct cell fiber transmission.
v. Universal Test & Operations PHY Interface for ATM (UTOPIA)
vi. OAM transmission interface
l 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 implements service transmission for the
AAL. 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 sub-layer interface
between the ATM layer and physical layer. The ATM layer at transmitting end
multiplexes cells with varied VCIs/VPIs and transmits them to the physical layer.
The ATM layer at receiving end identifies the VCIs/VPIs of cells from the physical
layer and transmits them to different modules 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. To implement VCC level continuity check, CC check
switch(CCCINFO0), CC check type (CCCINFO1), automatic CC check active and
de-active flag(CCCINFO34) and CC check direction(CCCINFO34)parameters
must be configured for VCC link.
l AAL
The AAL segments and assembles user information of high 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.
1-10

The AAL is used to enhance the capabilities of the ATM layer to meet the
demands of various specific 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 feature 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.
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 1-3 Services and related parameters
Service Class A Class B Class C Class D
Parameter
Source Required Not required.

and desti-
nation tim-
ing
Bit rate Constant Variable
Connec- Connection-oriented Connec-

tion Mode tionless
AAL type AAL 1 AAL 2 AAL 3 AAL 4
AAL 5
User ser- CBR Cir- VBR Motion picture, Connec- Connectionless data
vice exam- cuit emula- video and audio tion-ori- transmission
ples tion ented data
transmis-
sion
1-11

QoS QoS1 QoS2 QoS3 QoS4
Several bit rate-related concepts are described as follows:

Constant Bit Rate (CBR): Used to simulate 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,
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 speed response to senders. In the event of network congestion, senders
are requested to lower transmission rate. Suppose the senders observe these
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 give response
to 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 adding the minimum transmission bandwidth (frame
rate) service quality assurance. when the UBR + frames into the network, The
Frames which exceed the configuration parameters are tagged in accordance
with parameter control (UPC / NPC) in order to discard when network congestion,
when the UBR+ frames 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 IuPS services.
Table 1-4 Features of various ATM services
Feature CBR rt-VBR nrt-VBR ABR UBR UBR+
Bandwidth Yes Yes Yes Optional No Yes

guarantee
1-12

Feature CBR rt-VBR nrt-VBR ABR UBR UBR+
Applica- Yes Yes No No No No

ble to real-
time com-
munica-
tion
Applicable No No Yes Yes Yes Yes

to burst
communi-
cation
Any feed- No No No Yes No No

back on
conges-
tion
1-13

This page intentionally left blank.
1-14

Chapter 2
Preparations
License
None
Hardware Requirement
Hardware requirement is shown in Table 2-1.
Table 2-1 Hardware Requirement
NE Requirement
RNC APBE
NodeB None
Software Requirement
Software requirement i shown in Table 2-2.
Table 2-2 Software Requirement
NE Involved Version Requirement
UE YES - Number: 2
Category: Any
Release : Any
NodeB NO V4.11.10.14 -
RNC NO V3.11.10.11 ZTE equipment
MSCS YES - ZTE equipment
MGW YES - ZTE equipment
SGSN YES - ZTE equipment
GGSN NO - -
HLR NO - -
Topology
Topology is shown in Figure 2-1.
2-1

Figure 2-1 Topology
2-2

Chapter 3
Data configuration
SGSN/GGSN-ZTE
Parameters should configure as planned.
MSC/MGW-ZTE
Parameters should configure as planned.
HLR-ZTE
None
RNC
1. APBE Board Configuration
Reference ZWF22-02-054 ATM over Optical STM-1 Local Office Configuration
2. Path Group Configuration

First Create two Path Group ID: 52 for IUCS, 54 for IU PS,
Take example with Path Group ID 52 Created as below:
l Path Group ID: Depends on the real situation now it is 52
l Path Group Bear Type: ATM
l Forward Band width of Path Group(Unit:kbps): negotiate with Core Network
now it is 100000
l Backward Band width of Path Group(Unit:kbps): negotiate with Core Network
now it is 100000
l Mobile Country Code: negotiate with Core Network now it is 460
l Mobile Network Code: negotiate with Core Network now it is 25
l Ritio of occupied private bandwidth of Path Group by Operator: Depends on the
real situation now it is 0
3-1

Path: View->Configuration Management->RNC Managed Element->Ground

Resource Management Information->Transport Configuration-> Path Group
Configuration -> Path Group -> Add Path Group ->xxx
3. Local Office Configuration
l Mobile Country Code: negotiate with Core Networknow it is 460
l Mobile Network Code: negotiate with Core Networknow it is 25
l MNC BCD Code Length: negotiate with Core Networknow it is 2
l Net Element ID: negotiate with Core Networknow it is 21

Resource Management Information->Transport Configuration-> Network Element
Information-> Local Network Element Information configuration-> xxx
l 14-bit signaling code: negotiate with Core Networknow it is useless

l 24-bit signaling code: negotiate with Core Networknow it is 31-31-31
3-2

Chapter 3 Data configuration

Resource Management Information->Transport Configuration->Network Element
Information->RNC:0->Local Office Signaling Point Configuration ->14-bit/24-bit
signaling code.
l ATM Address Coding: negotiate with Core Networknow it is NSAP
l ATM Address of Adjacent Office(Decimal): negotiate with Core Networknow it
is 021-021-021

Information->RNC:0-> ATM Adjacent Office configuration->xxx
3-3

After finished Configuration Signalling Link Configuration in CN Office, Singalling

Link Route for MGW and SGSN should be added as below

Information->RNC:0-> Signalling Link Route->Add->XXX
4. IUCS Office Configuration
Firstly add MGW Office

l NE Type: depends on Core Network networkingnow it is MGW
l Net Element ID: 5000
3-4


Information ->Right Click->Create->CN Office- >Basic Configuration-> xxx
l Config for Bear Type of Service in IU: ATM

Information ->Right Click->Create->CN Office->CN Office-2> xxx
l Whether Default Office: No

l ATM Address Coding Plan: negotiate with Core Networknow it is NSAP
l Connection relationship with local signaling point: depends on Core Network
networkingnow it is Direct connecting
l UNI side or NNI side: negotiate with Core Networknow it is NNI
l ATM Address of Adjacent Office(Decimal): negotiate with Core Networknow it
is 220.220.220
l Whether Support Q.2630.2 Protocol or not: negotiate with Core Networknow it
is Do not Support Q.2630.2 Protocol
3-5


Information >CN Office->MGW:xxx->ATM Office Configuration > xxx
l TrPath ID: 52
l Path Group ID: 52 which has been created above
l Tx bandwidth(Unit:kbps): negotiate with Core Networknow it is 100000
l Rx bandwidth(Unit:kbps): negotiate with Core Networknow it is 100000
3-6


Resource Management Information->Transport Configuration->Network
Element Information >CN Office->MGW:xxx->Path Configuration >Add-> Path
Configuration-> xxx
l The Services Net Type: negotiate with Core Networknow it is Network2
l MGW Encode Type of Signaling Point: negotiate with Core Networknow it is
24-bit signaling point
l MGW Signaling Point Code: negotiate with Core Networknow it is 4-52-1
l Sub-Service Field: negotiate with Core Networknow it is National signaling code
l Domain type of adjacent office: Adjacent office signaling in SCN domain
l Signalling point type of adjacent office: Signaling transfer/end point
l Protocol type: negotiate with Core Networknow it is China
3-7


Element Information >CN Office->MGW:xxx->Adjacent Office Signalling Point
Configuration>xxx
l PVC Service Type: negotiate with Core Network, AAL5 Signalling
l PVC Interface Type: negotiate with Core Network, IuCS
l Rack/Shelf/Slot: Depends on the real situationnow it is 1/1/4
l ATM Port Numer: Depends on the real situationnow it is 10
l CVPI: negotiate with Core Networknow it is 0
l CVCI: negotiate with Core Networknow it is 121
l The Service Type on low to high port direction: negotiate with Core Network
now it is CBR
l Low-end Peak Cell Rate for CLP=0+1(PCR0+1)(Unit:kbps): negotiate with Core
Networknow it is 2048
3-8


Information-> MGW:xxx-> PVC Configuration-> Add->xxx
l PVC Service Type: negotiate with Core Network, AAL2 User Data
l PVC Interface Type: negotiate with Core Network, IuCS
now it is CBR
3-9



Information-> MGW:xxx> PVC Configuration-> Add->xxx
l Application Protocol: negotiate with Core Network, now is MTP3B
3-10

l Attached Module: Depends on the real situationnow it is 4

Information-> MGW:xxx-> Signalling Link Configuration-> Add->xxx
l AAL2 Path ID: negotiate with Core Network, now is 1

l Service Type: negotiate with Core Network, now is Mix
l Attached ModuleDepends on the real situation now is 3
3-11


Information-> MGW:xxx-> AAL2 Path Configuration-> Add->xxx
l Attached Module: Depends on the real situation now is 4
l SLC: negotiate with Core Network, now is 0

Information-> MGW:xxx-> No 7 Link> Add->xxx
After Local office finished configuration Signalling Link Route for MGW, Office
Route should be added as below

Information-> MGW:xxx-> Office Route> Add->xxx
Then add MSCServer Office
l NE Type: depends on Core Network networkingnow it is MSCServer
3-12



Information ->Right Click->Create->CN Office- >Basic Configuration->xxx
3-13

l Config for Bear Type of Service in IU: ATM

Information ->Right Click->Create->CN Office->CN Office-2>xxx
l Whether Default Office: Yes

l ATM Address of Adjacent Office(Decimal): no need if IUCS connection as
RNC-MGW-MSC.
3-14


Information >CN Office->MSCServer:xxx->ATM Office Configuration > xxx
l MSCServer Encode Type of Signaling Point: negotiate with Core Networknow
it is 24-bit signaling point
l MSCServer Signaling Point Code: negotiate with Core Networknow it is 4-51-1
l Signalling point type of adjacent office: Signaling end point

3-15

Information >CN Office->MSCServer:xxx->Adjacent Office Signalling Point

Configuration> xxx
Make sure SCCP and RANAP should Added in Office Subsystem No as below

Information >CN Office->MSCServer:xxx-> Office Subsystem No > xxx
5. IUPS Office Configuration
Firstly add SGSN Office

l NE Type: depends on Core Network networkingnow it is SGSN
3-16


Information ->Right Click->Create->CN Office- >Basic Configuration->xxx
l Config for Bear Type of Service in IU: IP

l Whether Default Office: Ture
3-17


l ATM Address of Adjacent Office(Decimal): Default now is 00000000000
l Whether Support Q.2630.2 Protocol or not: Defaultnow it is Do not Support
Q.2630.2 Protocol
3-18


Information >CN Office->SGSN:xxx->ATM Office Configuration > xxx
l TrPath ID: 54
l Path Group ID: 54 which has been created above
l Destination IP address: negotiate with Core Networknow it is 200.54.0.0
l Tx bandwidth(Unit:kbps): negotiate with Core Networknow it is 100000
l Rx bandwidth(Unit:kbps): negotiate with Core Networknow it is 100000

Element Information >CN Office->SGSN:xxx->Path Configuration >Add-> Path
Configuration-> xxx
l SGSN Encode Type of Signaling Point: negotiate with Core Networknow it is
24-bit signaling point
l SGSN Signaling Point Code: negotiate with Core Networknow it is 4-54-1
l Signalling point type of adjacent office: Signaling transfer/end point
3-19


Element Information >CN Office->SGSN:xxx->Adjacent Office Signalling Point
Configuration> xxx
l PVC Service Type: negotiate with Core Network, AAL5 Signalling
l PVC Interface Type: negotiate with Core Network, IuPS
now it is CBR
3-20


Information-> SGSN:xxx-> PVC Configuration-> Add->xxx
l PVC Service Type: negotiate with Core Network, AAL5 Data

l PVC Interface Type: negotiate with Core Network, IuPS
3-21


now it is CBR

Information -> PVC Configuration-> Add->xxx
l Application Protocol: negotiate with Core Network, now is MTP3B

l Attached Module: Depends on the real situationnow it is 3
3-22


Information -> Signalling Link Configuration-> Add->xxx
l Attached Module: Depends on the real situation now is 3
l SLC: negotiate with Core Network, now is 0

Information-> SGSN:xxx-> No 7 Link> Add->xxx
After Local office finished configuration Signalling Link Route for SGSN, Office
Route should be added as below
3-23


Information-> SGSN:xxx-> Office Route> Add->xxx
Make sure SCCP and RANAP should Added In Office Subsystem No as below

Information >CN Office->SGSN:xxx-> Office Subsystem No > xxx
6. Other Configuration
l RNC DSP IP address: negotiate with Core Networknow it is 138.1.121.1
3-24


Resource Management Information->Transport Configuration -> IP Protocol
Configuration-> Interface Configuration-> Add >xxx.
3-25


Resource Management Information->Transport Configuration -> IP Protocol
Configuration-> Interface Configuration-> Configuration of Service IP Address
>xxx.
l PVC IDDepends on the real configurationnow it is 4
l Destination IP address: negotiate with Core Networknow it is 10.13.54.1
l Service Type: Depends on the real configurationnow it is 255

Resource Management Information->Transport Configuration->ATM and IP
Binding Relation- >Create-> ATM and IP Binding Relation -> xxx
l Static Route Prefixnegotiate with Core Networknow it is 200.54.0.0
l Next hop IP address: negotiate with Core Networknow it is 10.13.54.1

Resource Management Information->Transport Configuration->IP Protocol
Configuration >Static Route->Create->Static Route> xxx
3-26

NodeB
None
3-27

This page intentionally left blank.
3-28

Chapter 4
Test
Table of Contents
Test Puropose ............................................................................................................4-1
Steps for Test .............................................................................................................4-1
Expected Results .......................................................................................................4-4
4.1 Test Puropose

The purpose of this test case is to verify if the function of ATM Transmission stack is working
normally.
Related document:
ZTE UMTS ATM Transmission Feature Guide_V6.0_201110.docx
4.2 Steps for Test

Steps
1. Query all the PVC status of both IUCS and IUPS office with RNC
ManagedElement-Dynamic data management object.The PVC status is normal.
4-1

2. Query SSCOP Link status and SAAL link status of both IUCS and IUPS office, The
SSCOP link status is Not Congestion, the SAAL lm link status is In Service.
3. Query AAL2 Link status of both IUCS office with Dynamic data management object.
The Path status is unblock.
4. Query MTP3B Link status of both IUCS and IUPS office with Dynamic data
management object.The link status is Normal, the MTP3 link status in SMP and in
OMP is In Service status.
4-2

Chapter 4 Test
5. Query Adjacent Office status of both IUCS and IUPS office with Dynamic data
management object. The adjacent office status is Accessible.
6. WCDMA system is ready, UEs camp in Cell1. UE1 makes a voice call to UE2 in Cell1,
hold on for 30 seconds and then release the call.
7. UE1 activates a PS call in Cell1 and starts ftp downloading, hold on for 30 seconds
and then release the PS call.
4-3

End of Steps
4.3 Expected Results

All the links are working normally and all services can be established and released
normally.
4-4

Chapter 5
Counter List
None
5-1

ZWF22!02!001 ATM Transmission Stack - V3

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

ZWF22!02!001 ATM Transmission Stack - V3

Hochgeladen von

Copyright:

Verfügbare Formate

Feature Deployment and Testing Guide

ATM Transmission stack_V3

Revision No. Revision Date Revision Reason

R1.0 20120806 First Edition

Serial Number: SJ-20120802112720-120

Publishing Date: 2012-08-06 (R1.0)

SJ-20120802112720-120|2012-08-06 (R1.0) ZTE Proprietary and Confidential

SJ-20120802112720-120|2012-08-06 (R1.0) ZTE Proprietary and Confidential

Figure 1-1 ATM protocol stack on IuCS interface

SJ-20120802112720-120|2012-08-06 (R1.0) ZTE Proprietary and Confidential

Figure 1-2 ATM protocol stack on IuPS interface

SJ-20120802112720-120|2012-08-06 (R1.0) ZTE Proprietary and Confidential

Figure 1-3 ATM protocol stack on Iur interface

SJ-20120802112720-120|2012-08-06 (R1.0) ZTE Proprietary and Confidential

Figure 1-4 ATM protocol stack on Iub interface

The figure shows the ATM cell header format:

SJ-20120802112720-120|2012-08-06 (R1.0) ZTE Proprietary and Confidential

Figure 1-5 ATM cell header format

ATM cell header is composed of the following:

Table 1-1 Payload type

GFC Generic Flow Control (GFC): 4 bits. It is only

VPI Virtual Path Identifier (VPI): 12 bits for NNI and

VCI Virtual Channel Identifier (VCI): 16 bits. It iden-

PTI Payload Type Indicator (PTI): 3 bits. It is used

CLP Cell Loss Priority (CLP): One bit. Indicates

HEC Header Error Control (HEC): 8 bits. It can be

SJ-20120802112720-120|2012-08-06 (R1.0) ZTE Proprietary and Confidential

Figure 1-6 ATM protocol model

SJ-20120802112720-120|2012-08-06 (R1.0) ZTE Proprietary and Confidential

Figure 1-7 Data transmission among layers

Table 1-2 Functions of various layers and their respective sub-layers

High layer Function of high layer

SJ-20120802112720-120|2012-08-06 (R1.0) ZTE Proprietary and Confidential

AAL CS sub-layer Convergence: That

SAR sub-layer Segmentation and re-

ATM layer GFC Cell header gen-

Cell VP/VC switching.

Cell multiplexing and

Physical Layer TC sub-layer Cell rate decoupling

PM sub-layer Bit timing Physical

The functions of all layers are described as follows:

SJ-20120802112720-120|2012-08-06 (R1.0) ZTE Proprietary and Confidential

SJ-20120802112720-120|2012-08-06 (R1.0) ZTE Proprietary and Confidential

Table 1-3 Services and related parameters

Service Class A Class B Class C Class D

Source Required Not required.

Bit rate Constant Variable

Connec- Connection-oriented Connec-

AAL type AAL 1 AAL 2 AAL 3 AAL 4

SJ-20120802112720-120|2012-08-06 (R1.0) ZTE Proprietary and Confidential

QoS QoS1 QoS2 QoS3 QoS4

Several bit rate-related concepts are described as follows:

Table 1-4 Features of various ATM services

Feature CBR rt-VBR nrt-VBR ABR UBR UBR+

Bandwidth Yes Yes Yes Optional No Yes

SJ-20120802112720-120|2012-08-06 (R1.0) ZTE Proprietary and Confidential

Feature CBR rt-VBR nrt-VBR ABR UBR UBR+

Applica- Yes Yes No No No No

Applicable No No Yes Yes Yes Yes

Any feed- No No No Yes No No

SJ-20120802112720-120|2012-08-06 (R1.0) ZTE Proprietary and Confidential

This page intentionally left blank.

SJ-20120802112720-120|2012-08-06 (R1.0) ZTE Proprietary and Confidential