Zwf22!02!051 Atm Over E1

Feature Deployment and Testing Guide
ATM Over E1
Feature ID: ZWF22-02-051
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 2012-8-3 First eition
Serial Number: SJ-20120802112720-127
Publishing Date: 2012-08-03(R1.0)
SJ-20120802112720-127|2012-08-03(R1.0) ZTE Proprietary and Confidential

Contents
Chapter 1 Functional Description ............................................................. 1-1
Chapter 2 Preparations .............................................................................. 2-1
Chapter 3 Data configuration .................................................................... 3-1
Chapter 4 Testing ....................................................................................... 4-1
4.1 Test Purpose...................................................................................................... 4-1
4.2 Steps for Test..................................................................................................... 4-1
4.3 Expected Results ............................................................................................... 4-2
Chapter 5 Counter List............................................................................... 5-1

II

Chapter 1
Functional Description
E1 physical interface complies with ITU-T G.703 standards. The allowed jitter of the
physical interface complies with ITU-T G.823 standards. The structure of the frame which
is transferred over the E1 interface complies with the ITU-T G.704 standards. E1 has 32
timeslots numbered 0 to 31. Where, the timeslot 0 is used to carry the synchronization
information and the timeslot 16 for carrying the control signals (also transferring the
information signals if necessary). If the out-of-band common channel signaling (CCS) is
adopted, the timeslot 16 cannot transfer the signaling. Other timeslots can carry the data.
For the IMA protocol, ZTE RAN equipment uses the rest 30 timeslots to transfer the data,
and an E1 supports the physical bandwidth of 1920 kbps. For TC (UMI) mode, ZTE can
maximize the number of timeslot for data transmission to 31, and maximize the physical
bandwidth of an E1 to 1984 kbps.
1-1

Feature Deployment and Testing Guide Feature ID: ZWF22-02-051
This page intentionally left blank.
1-2

Chapter 2
Preparations
License
None
Hardware Requirement
Hardware Requirement is shown inTable 2-1.
Table 2-1 Hardware Requirement
NE Requirement
RNC DTA board
NodeB SA board
Software Requirement
Software Requirement is shown inTable 2-2.
Table 2-2 Software Requirement
NE Involved Version Requirement
UE YES UMTS FDD Number: 2

Category: Any
Release : R99
NodeB YES V4.11.10.14 ZTE equipment
RNC YES V3.11.10.11 ZTE equipment
MSCS NO ZTE equipment
MGW NO ZTE equipment
SGSN NO ZTE equipment
GGSN NO
HLR NO
Topology
Topology is shown inFigure 2-1.
2-1

Figure 2-1 Topology
2-2

Chapter 3
Data configuration
SGSN/GGSN - ZTE
None
MSC/MGW - ZTE
None
HLR ZTE
None
RNC
1. Create a NODEB office
Path: View > Configuration Management > RNC Managed Element > RNC
Ground Resource Management > Transmission Configuration > Network
Element Information > Create
Figure 3-1 Great the NODEB office
2. Set NODEB global parameter of the office
Element Information > Create > Basic Configuration
l NE office Id: 160(This ID must be unique for one RNC)
l MNC: 460(This is mobile network code)
l MCC: 15 (This is mobile country code)
l Net Element ID: 160(This is nodeb ID)
3-1

Figure 3-2 NODEB Basic configurations
3. Configuration the bear type of IUB.

Element Information > Create > Node B office2
l Config for Bear Type of Service in IUB: ATM (we will modify to ATM + IP type if
the IP bear configuration already successful)
l Config for Bear type of common Channel in IUB: ATM
l Config for Bear Type of NBAP in IUB: ATM
Figure 3-3 NODEB bear type
4. Configuration the ATM address and AAL2 signal protocol.

Element Information > Node B XXX > ATM office configuration
l Support Q.2630.2: NO
l ATM address of adjacent office (Decimal):160.160.160(Integration parameter
must the same with Node B)
3-2

Chapter 3 Data configuration
Figure 3-4 ATM configuration parameters
5. IMA parameter configuration

Ground Resource Management > Transmission Configuration > IMA Group
Configuration > IMA Group Configuration
l Unit No.:5(this is DAT boards slot number in resource shelf)
l IMA Group: 1(automatic create by OMM)
l UTOPIA physics address: 14(This is ATM transmission port number)
l TC/IMA Model: IMA Model (the same with NODEB configuration)
Figure 3-5 IMA Group configuration parameters
6. E1 Link configuration
Ground Resource Management > Transmission Configuration > IMA Group
Configuration > IMA Link configuration
l Unit No: 5(the same with IMA group configuration)

l IMA Group: 1(refer to IMA Group Set ID)
l DT unit NO.:5(this is DAT boards slot number in resource shelf)
l DT subunit NO.:9(which port in DTA board)
3-3

l Scrambling code type in link direction: Cell payload scrambling (unscrambling)

l E1/T1 index: E1 (integration parameter the same with NODEB parameter)
Figure 3-6 IMA configuration parameters
7. PVC configuration
Element Information > Node B XXX > PVC configuration
l PVC ID: 1(PVC identifier)
l Unit No: 5(the physics board slot number)
l ATM port NO :(The same with UTOPIA physics address)
l CVPI: 1(Integration parameter the same with NODEB parameter)
l CVCI: 40(Integration parameter the same with NODEB parameter)
l PVC Config-1->Service Type: CBR (Constant Bit Rate (CBR), Real-time-VBR
(RT-VBR), Non-Real-time VBR (NRT-VBR), Available Bit Rate (ABR), Unspecified
Bit Rate (UBR), Unspecified Bit Rate Plus (UBR+))
Figure 3-7 PVC configuration parameters
3-4

8. Path Group configuration

Ground Resource Management > Transmission Configuration > Path Group
configuration
l Path Group ID: 1601
l Path Group Bear Type: ATM
l unit: 5((the physics board slot number))
l port: 14(IMA Group UTOPIA physics address)
l Forward band width of path group bps as the unit (kbps):1530(Depends on how
many E1 to be configured, one E1 band width is 1920bps)
l Backward band width of path group bps as the unit (kbps):1530(Depends on how
many E1 to be configured, one E1 band width is 1920bps)
l MCC/MNC: 460/15 (Mobile country code/Mobile network code)
Figure 3-8 Path group configuration parameters
9. Path configuration
Element Information > Node B XXX > Path configuration
l Path Group ID: 1601(refer to path group parameter configuration)

l Mobile country code: 460
l Mobile network code: 15
l Length of Destination IP address:NA (this path group using ATM bear so the IP
address is NA)
l Tx bandwidth (kbps):15360(Depends on how many E1s to be configured, every
E1 band width is 1920bps)
l Rx bandwidth (kbps): 15360(Depends on how many E1s to be configured, every
E1 band width is 1920bps)
3-5

Figure 3-9 Path configuration parameters
10. Signaling link configuration

Element Information > Node B XXX > Path configuration
PVC ID: 1 (refer to the PVC configuration parameter)
Application protocol: NBAP (if the PVC will use bear NCP or CCP that select NBAP;
if the PVC will use bear ALCAP that select ALCAP).
Figure 3-10 signaling link configuration parameters
11. AAL2 Path configuration

Element Information > Node B XXX > AAl2 Path configuration
l AAL2 Path ID: 1 (integration parameter the same of the Node B side)
l PVC ID: 4(Refer to the PVC configuration parameter)
l AAL2 Path Type: stringent class _AND_ tolerant class (This parameter indicates
a request for an AAL type 2 path with a specified Quality of Service)
3-6

l Service Type: MIX(RT prefer bear SRB and real time service;NRT1 prefer bear
R99 non-real time;NRT2 prefer bear HSUPA non-real time service;NRT3 prefer
bear HSDPA non-real time service; MIX bear all service type)
l Owner identifier: Location office (If select location office it allocates CID values
from CID value 8 upwards; If select adjacent office it allocation CID values from
CID value 255 downwards)
Figure 3-11 AAL2 path configuration parameters
12. NODEB port configuration

Element Information > Node B XXX > NODEB port configuration
l Port type: NCP (NCP (NodeB Control Port)/CCP (Communication Control Port))
l Signaling Link1:1(refer to Signaling link configuration parameter)
l Config the Bear Type of NBAP LINK1 in IUB: ATM (select bear type of this LINK)
Figure 3-12 NODEB port configuration parameters
3-7

13. NODEB configuration information

Path: View > Configuration Management > RNC Managed Element > RNC Radio
Resource Management > NODEB configuration information
l NODEB NO.:160(refer to NODEB Net Element ID)
l NodeB type: General NODEB
Figure 3-13 NodeB configuration information
14. Cell global configuration information

Resource Management > UTRAN Cell > UTRAN Cell Global information
l Net Element ID: 11(Refer to RNC global ID)
l Cell Identity: 301
l Local Cell Identity: 301(integration parameter the same with NODEB
configuration)
l NODEB Number: 160(refer to NODEB Net Element ID)
l Location Area Code: 15(Integration parameter that was provided by core network)
l Routing Area Code: 15(Integration parameter that was provided by core network)
l MCC/MNC: 460/15(Integration parameter that was provided by core network)
Figure 3-14 Cell global configuration information-1
3-8

Figure 3-15 Cell global configuration information-2
15. Cell global configuration information

Resource Management > UTRAN Cell > Cell Setup parameters
l Frequency Band indicator: Band (this parameter come from operator)
l UUARFCN9687 (this parameter come from operator)
l DUARFCN10637 (this parameter come from operator)
l Cell Primary Scrambling Code: 301(this parameter come from operator)
Figure 3-16 Cell Setup Parameters
16. Confirm the transport Qos Profile Type

Element Information > Node B XXX > NodeB office > NodeB office 1 > Transport
Qos Profile Type
l Transport Qos Profile Type: According to ARP/THP/TC Config Transport Qos
3-9

Figure 3-17 Transport Qos Profile Type
17. Configuration the NODEB Basic Priority Transport Bearer index

Resource Management > Qos configuration Related to Network Element > Basic
Priority Bearer type index
l Basic Priority Transport Bearer type index: 2
Figure 3-18 Basic Priority Transport bearer type index
18. Configuration the NODEB Basic Priority Transport Bearer
Resource Management > Qos configuration > Basic Priority Transport Bearer
Type
3-10

NodeB
The NodeB data should be imported from configuration file. The following steps just show
the parameters scanned from LMT which are already imported to the SDR.
Figure 1-21 transmission configurations for ATM and IP.
1. Configure the transport network ID.
Figure 3-19 Transport network ID.
2. NODEBs ATM port Configuration.

l Physical Layer Port No.: 0
l Connection Object: 0 (0: RNC/BSC/CN, 1: SDR, 2: Third-party)
l Used E1 Board SubRack No. : 1
l Used E1 Board Slot No.: 13
l Used E1 Port ID: 0, 1,2,3,4,5,6,7.
3-11

Figure 3-20 ATM port configurations
3. ATM transmission configuration
Figure 3-21 ATM transmission configurations
4. AAL2 configuration
l PCV No.:1
l AAL2 Link ID: 1(integration parameter the same of the Path ID)
l VPI/VCI: 2/50(integration parameter the same of NODEB network configuration)
l Bandwidth: 14976(Same of NODEB network configuration parameter)
l Service Type: SRVC_CBR (integration parameter the same of NODEB network
configuration parameter)
Figure 3-22 AAL2 configurations information
5. SaalUNI configuration
l PVC No.:64501/64502/64503
3-12

l VPI/VCI: 1/40; 1/41; 1/42(integration parameter the same of NODEB network

configuration)
l Bandwidth: 128(Same of NODEB network configuration parameter)
l Service Type: SRVC_CBR (integration parameter the same of NODEB network
configuration parameter)
Figure 3-23 PVC configurations information
6. ALCAP configuration information

l PVC No.:64503
l ATM address: 160.160.160(Integration parameter same of NODEB network
configuration)
Figure 3-24 ALCAP configurations information
7. NODEB ID configuration
3-13

Figure 3-25 NODEB ID configurations information
8. IUB Link configuration
Figure 3-26 IUB Link configurations information
9. IUB Data Stream
Figure 3-27 IUB Data Steam information
10. NBAP D signaling configuration
3-14

Figure 3-28 NBAPDsgnaling configurations information
11. NBAP C Signaling configuration
Figure 3-29 NBAPCsgnaling configurations information
12. USecter
Figure 3-30 USecter configurations information
13. Local Cell Config

All configuration information refer to the RNC config.
3-15

3-16

Chapter 4
Testing
Table of Contents
Test Purpose ..............................................................................................................4-1
Steps for Test .............................................................................................................4-1
Expected Results .......................................................................................................4-2
4.1 Test Purpose

The purpose of this test case is to verify the function of ATM over E1 is normal.
4.2 Steps for Test

1. Query IMA group status with OMM. The IMA group status is running.
2. Inhibit the IMA group.
3. The NodeB is out of service.
4-1

4. UE1 makes a voice call to UE2 in Cell1.
5. UE1 activates a PS call in Cell1 and starts data transferring.
4.3 Expected Results

All services can be established and released normally.
4-2

Chapter 5
Counter List
There is no any counter related to ATM over E1 feature.
5-1

Zwf22!02!051 Atm Over E1

Uploaded by

Copyright:

Available Formats

You might also like

Zwf22!02!051 Atm Over E1

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Zwf22!02!051 Atm Over E1

Uploaded by

Copyright:

Available Formats

Feature Deployment and Testing Guide

Revision No. Revision Date Revision Reason

R1.0 2012-8-3 First eition

Serial Number: SJ-20120802112720-127

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

SJ-20120802112720-127|2012-08-03(R1.0) ZTE Proprietary and Confidential

Chapter 5 Counter List............................................................................... 5-1

SJ-20120802112720-127|2012-08-03(R1.0) ZTE Proprietary and Confidential

SJ-20120802112720-127|2012-08-03(R1.0) ZTE Proprietary and Confidential

SJ-20120802112720-127|2012-08-03(R1.0) ZTE Proprietary and Confidential

This page intentionally left blank.

SJ-20120802112720-127|2012-08-03(R1.0) ZTE Proprietary and Confidential

Table 2-1 Hardware Requirement

RNC DTA board

Table 2-2 Software Requirement

NE Involved Version Requirement

UE YES UMTS FDD Number: 2

NodeB YES V4.11.10.14 ZTE equipment

RNC YES V3.11.10.11 ZTE equipment

MSCS NO ZTE equipment

MGW NO ZTE equipment

SGSN NO ZTE equipment

SJ-20120802112720-127|2012-08-03(R1.0) ZTE Proprietary and Confidential

Figure 2-1 Topology

SJ-20120802112720-127|2012-08-03(R1.0) ZTE Proprietary and Confidential

Figure 3-1 Great the NODEB office

2. Set NODEB global parameter of the office

SJ-20120802112720-127|2012-08-03(R1.0) ZTE Proprietary and Confidential

Figure 3-2 NODEB Basic configurations

3. Configuration the bear type of IUB.

Figure 3-3 NODEB bear type

4. Configuration the ATM address and AAL2 signal protocol.

SJ-20120802112720-127|2012-08-03(R1.0) ZTE Proprietary and Confidential

Figure 3-4 ATM configuration parameters

5. IMA parameter configuration

Figure 3-5 IMA Group configuration parameters

l Unit No: 5(the same with IMA group configuration)

SJ-20120802112720-127|2012-08-03(R1.0) ZTE Proprietary and Confidential

l Scrambling code type in link direction: Cell payload scrambling (unscrambling)

Figure 3-6 IMA configuration parameters

Figure 3-7 PVC configuration parameters

SJ-20120802112720-127|2012-08-03(R1.0) ZTE Proprietary and Confidential

8. Path Group configuration

Figure 3-8 Path group configuration parameters

l Path Group ID: 1601(refer to path group parameter configuration)

SJ-20120802112720-127|2012-08-03(R1.0) ZTE Proprietary and Confidential

Figure 3-9 Path configuration parameters

10. Signaling link configuration

Figure 3-10 signaling link configuration parameters

11. AAL2 Path configuration

SJ-20120802112720-127|2012-08-03(R1.0) ZTE Proprietary and Confidential

Figure 3-11 AAL2 path configuration parameters

12. NODEB port configuration

Figure 3-12 NODEB port configuration parameters

SJ-20120802112720-127|2012-08-03(R1.0) ZTE Proprietary and Confidential

13. NODEB configuration information

Figure 3-13 NodeB configuration information

14. Cell global configuration information