Feature Parameter Description: ATM Transport RAN12.0

ATM Transport RAN12.
Feature Parameter Description
Issue Date
01 2010-10-15
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2011. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied. The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute the warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China Website: Email: http://www.huawei.com support@huawei.com
WCDMA RAN ATM Transport
Contents
Contents
1 Introduction ................................................................................................................................1-1
1.1 Scope ............................................................................................................................................ 1-1 1.2 Intended Audience ........................................................................................................................ 1-1 1.3 Change History.............................................................................................................................. 1-1
2 Overview of ATM Transport ....................................................................................................2-1 3 Protocol Stacks .........................................................................................................................3-1

3.1 Iub Over ATM ................................................................................................................................ 3-1 3.1.1 Protocol Stack ....................................................................................................................... 3-1 3.1.2 Links on the Iub Interface ..................................................................................................... 3-2 3.1.3 OM IPoA Data Configuration on the Iub Interface ................................................................ 3-2 3.2 Iu-CS over ATM ............................................................................................................................. 3-3 3.2.1 Protocol Stack ....................................................................................................................... 3-3 3.2.2 Links on the Iu-CS Interface ................................................................................................. 3-4 3.2.3 Differences of the Iu-CS Interface Between R99 and R4/R5/R6/R7/R8 .............................. 3-4 3.3 Iu-PS over ATM ............................................................................................................................. 3-7 3.3.1 Protocol Stack ....................................................................................................................... 3-7 3.3.2 Links on the Iu-PS Interface ................................................................................................. 3-7 3.3.3 IPoA Data Configuration on the Iu-PS User Plane ............................................................... 3-8 3.4 Iur over ATM .................................................................................................................................. 3-9 3.4.1 Protocol Stack ....................................................................................................................... 3-9 3.4.2 Links on the Iur Interface .................................................................................................... 3-10 3.4.3 Configuration Principles for Static Relocation Routes over Iur........................................... 3-11 3.5 ATM Transport Modes ................................................................................................................. 3-12 3.5.1 UNI Mode ........................................................................................................................... 3-12 3.5.2 Fractional Mode .................................................................................................................. 3-13 3.5.3 Timeslot Cross Connection Mode ...................................................................................... 3-14 3.5.4 IMA Mode ........................................................................................................................... 3-16 3.6 PVC Parameters of the ATM Layer ............................................................................................. 3-17 3.6.1 VPI and VCI ........................................................................................................................ 3-17 3.6.2 Service Type ....................................................................................................................... 3-18 3.6.3 ATM Traffic Records ........................................................................................................... 3-19 3.7 AAL2 Path ................................................................................................................................... 3-20 3.8 MTP3/M3UA ................................................................................................................................ 3-21 3.8.1 MTP3 .................................................................................................................................. 3-21 3.8.2 Types of MTP3/M3UA DSPs .............................................................................................. 3-22 3.8.3 Signaling Route Mask and Signaling Link Mask ................................................................ 3-23 3.9 AAL5 Path ................................................................................................................................... 3-23 3.10 IPOA PVC.................................................................................................................................. 3-24 3.11 F5............................................................................................................................................... 3-24
Issue 01 (2010-10-15)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd
Contents
4 ATM Transmission Resources...............................................................................................4-1 5 ATM Transmission Resource Management .......................................................................5-1 6 Parameters .................................................................................................................................6-1 7 Counters ......................................................................................................................................7-1 8 Glossary ......................................................................................................................................8-1 9 Reference Documents .............................................................................................................9-1
Issue 01 (2010-10-15)
ii
1 Introduction
1 Introduction
1.1 Scope
This document merges the basic ATM transport principle. It describes protocol stacks, transmission resources, transmission resource management (TRM), and associated parameters.
1.2 Intended Audience

This document is intended for:

Personnel who are familiar with WCDMA basics Personnel who need to understand ATM transport Personnel who work with Huawei products
1.3 Change History

This section provides information on the changes in different document versions. There are two types of changes, which are defined as follows:

Feature change: refers to the change in the ATM transport feature. Editorial change: refers to the change in wording or the addition of the information that was not described in the earlier version.
Document Issues
The document issues are as follows:

01 (2010-10-15) Draft (2010-03-30)
01 (2010-10-15)
This is the document for the first commercial release of RAN12.0. Compared with issue Draft (2010-03-30) of RAN12.0, this issue optimizes the description.
Draft (2010-03-30)
This is the draft of the document for RAN12.0. This is a new document.
Issue 01 (2010-10-15)
1-1
2 Overview of ATM Transport
2 Overview of ATM Transport

Huawei radio access network (RAN) provides ATM-based Iub/Iu(Iu-CS and Iu-PS)/Iur interfaces and ATM TRM, such as admission control based on AAL2 path bandwidth; transmission resource mapping based on ATM QoS classes, and Iub overbooking.
Issue 01 (2010-10-15)
2-1
3 Protocol Stacks
3 Protocol Stacks
3.1 Iub Over ATM
3.1.1 Protocol Stack
Figure 3-1 shows the protocol stack for the ATM-based Iub interface. Figure 3-1 Protocol stack for the ATM-based Iub interface
The transport network layer of the Iub interface consists of the transport network layer user plane (area A), transport network layer control plane (area B), and transport network layer user plane (area C).

Areas A, B, and C share the physical layer and ATM layer. Therefore, all links in the three areas can be carried on common physical links. Links in areas A and B are carried on SAAL links. Based on the type of carried information, the upper layer of area A is classified into the NodeB Control Port (NCP) and the Communication Control Port (CCP). Only Q.AAL2 links are carried in area B.
In area C, the user plane data is carried on AAL2 paths. The bearer at the lower layer is the ATM PVC. Under the control of Q.AAL2, AAL2 connections can be dynamically set up or released for upper-layer services. Therefore, each AAL2 path must have its corresponding controlling Q.AAL2.
Issue 01 (2010-10-15)
3-1
3 Protocol Stacks
3.1.2 Links on the Iub Interface

The links on the ATM-based Iub interface are of three types: SAAL link of User-Network Interface (UNI) type, AAL2 path, and IPoA PVC. The SAAL link of UNI type is used to carry NCP, CCP, and ALCAP, as shown in Figure 1-17. Figure 3-2 Links on the Iub interface
The RINT shown in Figure 1-17 refers to ATM interface boards UOIa/UOIc, AOUa/AOUc, and AEUa.
3.1.3 OM IPoA Data Configuration on the Iub Interface

On the ATM-based Iub interface, the IPoA PVC functions as the Operation and Maintenance (OM) channel.
OM IPoA PVC on the Iub Interface

Figure 3-3 shows the IPoA PVCs from the BSC6900 to NodeBs. Figure 3-3 IPoA PVCs from the BSC6900 to NodeBs
Issue 01 (2010-10-15)
3-2
3 Protocol Stacks
Network Segments
Each IPoA PVC travels through the following network segments before reaching the NodeB:

The 80.168.3.0 segment (with network mask of 255.0.0.0) between the OM board and the ATM interface board. This network segment is set before delivery of the BSC6900. The 12.13.1.0 segment (with network mask of 255.255.255.0) between the ATM interface board and the NodeBs. When setting this network segment, you need to take field conditions into consideration.
3.2 Iu-CS over ATM

Figure 3-4 shows the protocol stack for the Iu-CS interface. Figure 3-4 Protocol stack for the ATM-based Iu-CS interface
The transport network layer of the Iu-CS interface consists of the following areas:

Transport network layer user plane (area A) Transport network layer control plane (area B) Transport network layer user plane (area C)
Areas A, B, and C share the physical layer and ATM layer. Therefore, all links in the three areas can be carried on common physical links.
Issue 01 (2010-10-15)
3-3
3 Protocol Stacks
3.2.2 Links on the Iu-CS Interface

The Iu-CS links on the CN side are of two types: MTP3 link and AAL2 path. Figure 3-5 shows the links on the ATM-based Iu-CS interface. Figure 3-5 Links on the Iu-CS Interface
The RINT shown in Figure 1-28 refers to ATM interface boards of the BSC6900. The UOIa/UOIc board is recommended when ATM transport is applied to the Iu-CS interface.
3.2.3 Differences of the Iu-CS Interface Between R99 and R4/R5/R6/R7/R8

In the 3GPP R99, the MSC connects to the BSC6900 as one entity. In the 3GPP R4/R5/R6/R7/R8, the MSC connects to the BSC6900 after being split into two entities, namely, MSC server and MGW.
Iu-CS Interface Defined in the 3GPP R4/R5/R6/R7/R8

Figure 3-6 shows the Iu-CS interface in the 3GPP R4/R5/R6/R7/R8.
Issue 01 (2010-10-15)
3-4
3 Protocol Stacks
Figure 3-6 Iu-CS interface in the 3GPP R4/R5/R6/R7/R8
The network may require multiple MGWs depending on the traffic volume. In practice, the MSC server is often not directly connected to the BSC6900. Data is forwarded between the MSC server and the BSC6900 through the routes configured on the MGW. Figure 3-7 shows an example of the network structure on the Iu-CS interface in the 3GPP R4/R5/R6/R7/R8. Figure 3-7 Example of the network structure on the Iu-CS interface in the 3GPP R4/R5/R6/R7/R8
Issue 01 (2010-10-15)
3-5
3 Protocol Stacks
Functions of the MSC and of the MSC Server and MGW

Figure 3-8 Protocol stack for the ATM-based Iu-CS interface
As shown in Figure 3-8, the MSC in an R99 network implements the functions in areas A, B, and C of the protocol stack. The MSC server and MGW in an R4/R5/R6/R7/R8 network implement their functions as follows:

The MSC server implements the functions in area A. The MGW implements the functions in areas B and C.
Data Configuration on the BSC6900

In the 3GPP R99, the BSC6900 needs to be configured with only one type of Iu-CS signaling point, that is, the MSC. In the 3GPP R4/R5/R6/R7/R8, the BSC6900 needs to be configured with the following two types of Iu-CS signaling point:

MSC server (also called Iu-CS RANAP signaling point) MGW (also called Iu-CS ALCAP signaling point)
Table 3-1 describes the differences between signaling point configuration in R99 and that in R4/R5/R6/R7/R8. Table 3-1 Differences between signaling point configuration in R99 and that in R4/R5/R6/R7/R8 Item Type R4/R5/R6/R7/R8 Iu-CS RANAP signaling point and Iu-CS ALCAP signaling point R99 Iu-CS signaling point
Issue 01 (2010-10-15)
3-6
3 Protocol Stacks
Item Quantity
R4/R5/R6/R7/R8 More than one
R99 One
3.3 Iu-PS over ATM

Figure 3-9 shows the protocol stack for the Iu-PS interface. Figure 3-9 Protocol stack for the ATM-based Iu-PS interface
The transport network layer of the Iu-PS interface consists of the transport network layer user plane (area A) and the transport network layer user plane (area C). Areas A and C share the physical layer and ATM layer. Therefore, all links in the two areas can be carried on common physical links.
3.3.2 Links on the Iu-PS Interface

The Iu-PS links on the CN side are of two types: MTP3 link and IPoA PVC. Figure 3-10 shows the links on the ATM-based Iu-PS interface.
Issue 01 (2010-10-15)
3-7
3 Protocol Stacks
Figure 3-10 Links on the ATM-based Iu-PS interface
The RINT shown in Figure 3-10 refers to the UOIa/UOIc board.
3.3.3 IPoA Data Configuration on the Iu-PS User Plane

On the ATM-based Iu-PS interface, the IPoA PVC is implemented on the user plane.
IPoA PVC on the Iu-PS User Plane

Figure 3-11 shows the IPoA PVC on the Iu-PS user plane. Figure 3-11 IPoA PVC on the Iu-PS interface
Issue 01 (2010-10-15)
3-8
3 Protocol Stacks
IPoA Data on the Iu-PS User Plane

Table 3-2 describes the IPoA data to be configured on the user plane of the ATM-based Iu-PS interface. Table 3-2 IPoA data on the user plane of the ATM-based Iu-PS interface Item Description
Local IP address of the IPoA PVC (IPADDR) Device IP address on the ATM interface board of the BSC6900 Peer IP address of the IPoA PVC (PEERIPADDR) IP address of the gateway on the SGSN side
PVC between the interface board carrying the IPoA data and the gateway on the SGSN side Route between the interface board carrying If the IP address of the interface board carrying the IPoA the IPoA data and the network segment of data and the IP address of the peer SGSN are located on the peer SGSN different subnets, routes to the destination IP address need to be configured at the BSC6900. DSTIP is the IP address of the SGSN, and NEXTHOP is the IP address of the gateway on the SGSN side.
On the Iu-PS interface, the SGSN must be configured with routes to the network segment to which the IP address of the BSC6900 interface board belongs. The next hop is the gateway on the BSC6900 side. Otherwise, PS services cannot be provided.
3.4 Iur over ATM

Figure 3-12 shows the protocol stack for the Iur interface.
Issue 01 (2010-10-15)
3-9
3 Protocol Stacks
Figure 3-12 Protocol stack for the ATM-based Iur interface
The transport network layer of the ATM-based Iur interface consists of the following areas:

Transport network layer user plane (area A) Transport network layer control plane (area B) Transport network layer user plane (area C)
3.4.2 Links on the Iur Interface

The Iur links on the CN side are of two types: MTP3 link and AAL2 path. Figure 3-13 shows the links on the ATM-based Iur interface.
Issue 01 (2010-10-15)
3-10
3 Protocol Stacks
Figure 3-13 Links on the Iur interface
3.4.3 Configuration Principles for Static Relocation Routes over Iur

The IP routes on the Iur interface are used to forward the PS data during Serving Radio Network Subsystem (SRNS) relocation. During the SRNS relocation, the PS data is transferred from the local BSC6900 to the SGSN and then to the neighboring BSC6900. Therefore, the prerequisites for configuring IP routes on the Iur interface are that the IP paths between the local BSC6900 and the SGSN, between the neighboring BSC6900 and the SGSN, and between the serving BSC6900 and the drift BSC6900 are configured. Figure 3-14 shows the configuration of IP routes on the Iur interface. The IP routes configured in multiple subsystems are similar.
Issue 01 (2010-10-15)
3-11
3 Protocol Stacks
Figure 3-14 IP route configuration on the Iur interface
The RINT shown in Figure 3-14 refers to IP interface boards PEUa, POUa/POUc, UOIa (UOIa_IP), FG2a/FG2c, and GOUa/GOUc.
3.5 ATM Transport Modes

ATM transport has four modes: UNI, fractional, timeslot cross connection, and IMA.
3.5.1 UNI Mode

The UNI mode is a transport mode at the Transmission Convergence (TC) sublayer of the physical layer. In UNI mode, an ATM cell is directly carried on an E1/T1 frame and the bits of the ATM cell are sequentially mapped to the valid timeslots on the E1/T1 frame. Figure 3-15 shows the mapping between the ATM cell and the E1 timeslots in UNI mode. The 53 bytes of the ATM cell are sequentially carried on E1 timeslots. Each E1 frame provides 31 timeslots (with slot 0 unavailable) for carrying the ATM cell.
Issue 01 (2010-10-15)
3-12
3 Protocol Stacks
Figure 3-15 Mapping between the ATM cell and the E1 timeslots in UNI mode
3.5.2 Fractional Mode

Fractional mode (WRFD-050302 Fractional ATM Function on Iub Interface) is applicable to the Transmission Convergence (TC) sublayer of the physical layer. This section describes the principles and functions of fractional ATM, introduces the two implementation modes (that is, fractional IMA and fractional ATM), and provides the principles for configuring fractional IMA links and fractional ATM links.
Principles of Fractional ATM

In the case of fractional ATM, multiple timeslots out of the 32 timeslots on an E1 (or 24 timeslots on a T1) are used to transmit an ATM cell. At the transmission end, an ATM cell is mapped to multiple timeslots among the 31 timeslots on an E1 (or 24 timeslots on a T1). At the reception end, the ATM cell is restored from the associated timeslots on the E1/T1. Figure 1-3 shows the fractional ATM mode. An E1 frame has timeslots numbered from 0 to 31. All the timeslots except timeslot 0 are available for service data transmission. A T1 frame has timeslots numbered from 1 to 24. All the timeslots are available for service data transmission. The timeslots to which the ATM cell is not mapped can transmit other data. Figure 3-16 Fractional ATM mode
Issue 01 (2010-10-15)
3-13
3 Protocol Stacks
If multiple E1/T1 trunks exist between the transmission end and the reception end and work in IMA mode, such an IMA mode is called fractional IMA. In fractional IMA mode, an IMA group contains multiple fractional ATM links.
Function of Fractional ATM

After the fractional ATM function is enabled, the ATM cells of a 3G network can be transmitted over an existing 2G network, as shown in Figure 3-17. Figure 3-17 Fractional ATM function
Two Modes of the Fractional ATM Function

There are two implementation modes of the fractional ATM function on the Iub interface:
Fractional ATM In fractional ATM mode, multiple idle timeslots can be used for transmission. The fractional ATM mode is applicable only to the AEUa/AOUc board.
Fractional IMA In fractional IMA mode, multiple fractional IMA links are logically gathered into a group with each fractional IMA link occupying the same number of idle timeslots.
The fractional IMA mode is applicable only to the AEUa/AOUc board.
3.5.3 Timeslot Cross Connection Mode

The timeslot cross connection function implements cross connections between timeslots on two E1/T1s at the physical medium (PM) sublayer of the physical layer. This section describes the principles and functions of timeslot cross connection.
Issue 01 (2010-10-15)
3-14
3 Protocol Stacks
Principles of Timeslot Cross Connection

Figure 3-18 shows an example of timeslot cross connection. The timeslot cross connection device cross-connects the timeslots on one E1/T1 to the timeslots on the other E1/T1. In the example shown in the following figure, the device cross-connects slots 2 and 3 on one E1/T1 to slots 4 and 8 on another E1/T1 respectively. Figure 3-18 Example of timeslot cross connection
Function of Timeslot Cross Connection

The AEUa board supports timeslot cross connection. Through the configured timeslot cross connection, the E1 data in TS A of the source port is transmitted to TS B of the target port. Thus, the timeslot cross connection helps provide a transparent data transmission channel for the 2G equipment or NodeB monitoring equipment. Figure 3-19 shows implementation of timeslot cross connection. Figure 3-19 Implementation of timeslot cross connection
Issue 01 (2010-10-15)
3-15
3 Protocol Stacks
Neither the source timeslot nor the target timeslot of a timeslot cross connection can be used by other applications, such as fractional ATM, IMA, and UNI.
If an E1 link is configured with a timeslot cross connection, the E1 link cannot carry any IMA or UNI link. The other timeslots on this E1 link can carry fractional ATM or fractional IMA links.
3.5.4 IMA Mode

IMA mode (WRFD-050304 IMA Transmission for E1T1 or Channelized STM-1/OC-3 on Iub Interface) is applicable to the Transmission Convergence (TC) sublayer of the physical layer. The IMA function is implemented by the IMA group, which is composed of either IMA links or fractional IMA links. This section describes the principles, clock modes, and characteristics of IMA mode.
Principles of IMA Mode

Figure 3-20 shows the principles of the IMA mode based on the assumption that each IMA group contains three E1/T1 links.

At the transmission end, the IMA group receives the ATM cell stream from the ATM layer and distributes the cells among the E1/T1 links. At the reception end, the IMA group reassembles the cells to restore the original ATM cell stream, and then transfers the cell stream to the ATM layer.
The physical layer provides high-speed transport channels for ATM cells from the perspective of the ATM layer. Figure 3-20 Principles of the IMA mode
In IMA mode, ATM cells, IMA Control Protocol (ICP) cells, and filler cells form an IMA frame to implement necessary controlling functions. The length of an IMA frame, m, is defined during the setup of an IMA group. Figure 3-26 shows an IMA frame. The mapping between the ATM cell and the physical link (that is, the E1/T1 link) is similar to that in UNI mode.
Issue 01 (2010-10-15)
3-16
3 Protocol Stacks
Figure 3-21 IMA frame
Clock Modes
The clock mode of an IMA group is defined from the perspective of an IMA group rather than a single link. The IMA group has two clock modes:

Common Transmit Clock (CTC): In CTC clock mode, all links in an IMA group share one clock source. The clock source may be extracted from the same external clock or from a link. Independent Transmit Clock (ITC): In ITC mode, the clocks used by the links within an IMA group are derived from at least two clock sources. The loopback clock mode is a special case of the ITC mode.
Characteristics
The IMA mode has the following characteristics:

The clock modes at the two ends of the IMA group must be identical. All E1/T1s within an IMA group are simultaneously scrambled or none of them is scrambled. In other words, the states of the scrambling switches at both ends of E1/T1s must be identical. All IMA links within an IMA group must be of the same type, either common IMA link or fractional IMA link.
If an IMA group is made up of fractional IMA links, the quantity of timeslots carrying each fractional IMA link must be identical.
3.6 PVC Parameters of the ATM Layer

For configuring the IPoA PVCs, AAL2 paths, SAAL links, or VPCLCX links, the PVC parameters need to be set.
3.6.1 VPI and VCI

The main characteristics of the ATM technology are multiplexing, switching, and transmitting of ATM cells. All these operations are performed over Virtual Channels (VCs). A VC and a Virtual Path (VP) are identified by Virtual Channel Identifier (VCI) and Virtual Path Identifier (VPI) respectively. Figure 3-22 shows the relation between VC and VP.
A VC is identified by a VCI. It is a logical connection between ATM nodes and is the channel for transmitting ATM cells between two or more nodes. The VC is used for the data transmission between mobile terminals, between networks, or between mobile terminal and network.
Issue 01 (2010-10-15)
3-17
3 Protocol Stacks
A VP is a group of VCs at a given reference point. The VCs in the group have the same VPI.
Figure 3-22 Relation between VC and VP
3.6.2 Service Type

The ATM services are of five types (WRFD-05030107 CBR, rt-VBR, nrt-VBR, UBR ATM QoS Classes, WRFD-050305 UBR+ ATM QoS Class): Constant Bit Rate (CBR), Real-Time Variable Bit Rate (RT-VBR), Non-Real-Time Variable Bit Rate (NRT-VBR), Unspecified Bit Rate (UBR), and UBR_PLUS (UBR+). Table 3-3 describes the types of service. Table 3-3 Types of service Type of Service CBR RT-VBR NRT-VBR UBR Description No error check, flow control, or other processing Rate of a service with variable-rate data streams and strict real-time requirements, for example, interactive compressed video (video telephony). Rate of a service that is applicable to timing transmission. A service of this type, for example, e-mail, is relatively insensitive to delivery time or delay. Rate of a service with no commitment to transmission and no feedback on congestion. This type of service is ideal for the transmission of IP datagrams. In congestion, UBR cells are discarded, and no feedback or request for slowing down the data rate is delivered to the transmission end. UBR+ is an enhancement of UBR with minimum desired cell rate (MDCR) indication. UBR+ is the most suitable for Iub OAM channel. The MCR of UBR+ ensures the connectivity of OAM connection in the case of Iub transmission resource congestion, and the best effort service of UBR+ uses the transmission bandwidth completely.
UBR+
Table 3-4 describes the characteristics of different ATM services. Table 3-4 Characteristics of different ATM services Characteristic Bandwidth guarantee Applicability to real-time communication CBR Yes Yes RT-VBR Yes Yes NRT-VBR Yes No UBR No No UBR+ Yes No
Issue 01 (2010-10-15)
3-18
3 Protocol Stacks
Characteristic Applicability to bursts of communication Feedback on congestion
CBR No No
RT-VBR No No
NRT-VBR Yes No
UBR Yes No
UBR+ No No
The ATM service type is also called ATM QoS class. The CBR, RT-VBR, NRT-VBR, or UBR ATM QoS classes can be configured for AAL2 path, and the UBR+ ATM QoS class is generally used for Iub OAM connection. The service types carried on the AAL2 paths can be determined by running the ADD ATMTRF command, and then the mapping between the service types and the transmission resources for the adjacent node can be configured by running the ADD TRMMAP command.
3.6.3 ATM Traffic Records

The ATM traffic records are public resources, which can be used by the IPoA PVCs, AAL2 paths, SAAL links, and VPCLCX links. You need to add the traffic record at the BSC6900 based on the traffic model of the link on the Iub/Iu-CS/Iu-PS/Iur interface. The ATM traffic records can be configured by the ADD ATMTRF command.
Traffic Parameters
Traffic parameters refer to the parameters used by each PVC for flow control. Table 3-5 describes the ATM traffic parameters. Table 3-5 ATM traffic parameters Parameter ID TRFX ST Description Identifies a traffic record. Indicates the type of service carried over ATM. CBR and RT-VBR indicate real-time services, which are usually carried on the user planes of the Iur, Iub, and Iu-CS interfaces. NRT-VBR and UBR indicate non-real-time services, which are usually carried on the user plane of the Iu-PS interface. Indicates the unit of PCR, SCR, and MCR. Indicates the maximum rate of transmitting ATM cells. The value of PCR must be greater than that of SCR. Indicates the average rate of transmitting ATM cells over a long time. Indicates the minimum rate of transmitting ATM cells. Indicates the maximum number of continuous ATM cells. Generally, the value of MBS cannot be greater than PCR x CDVT. The value of CDVT can be set as large as possible within the permission of the delay and delay variation. Indicates the maximum tolerable variation in the unit of 0.1 s. Describes the usage of the ATM traffic record.
UT PCR SCR MCR MBS
CDVT REMARK
Issue 01 (2010-10-15)
3-19
3 Protocol Stacks
The traffic rate is indicated in the following ways:

PCR: applicable when ST is set to CBR and the traffic rate is a constant value. Combination of PCR and SCR: applicable when ST is set to RTVBR or NRTVBR. MCR: applicable when ST is set to UBR_PLUS.
ATM Traffic Record Configuration Principles

Table 3-6 provides suggestions for configuring service types during configuration of ATM traffic records for links. Table 3-6 Recommended service types for links Link NCP/CCP AAL2 path IPoA PVC (user plane) IPoA PVC (management plane) MTP3 link Type of Service (In Descending Order by Priority) RTVBR, NRTVBR, CBR RTVBR, NRTVBR, CBR, UBR UBR UBR_PLUS, RTVBR, NRTVBR, CBR, UBR RTVBR, NRTVBR, CBR
In practice, ATM traffic records should be negotiated between the local and the peer equipment. The ATM traffic parameters, such as PCR and SCR, should be configured depending on the traffic model in use. When configuring ATM traffic records for links, you need to consider the traffic on the interface boards of the BSC6900.
3.7 AAL2 Path

AAL2 Connections and AAL2 Path
The Q.AAL2 module is responsible for dynamically setting up and releasing AAL2 connections between the BSC6900 and the peer end. The peer end can be a NodeB, a CS CN node, or a neighboring BSC6900. An AAL2 path contains multiple AAl2 connections. The AAL2 paths can be configured for the Iub/Iu-CS/Iur interface (WRFD-05030104 Dynamic AAL2 Connections on Iub/IuCS/Iur Interface). Figure 3-23 shows the relation between an AAL2 path and AAL2 connections on the Iub interface. Figure 3-23 Relation between an AAL2 path and AAL2 connections
According to different traffic classes (conversational, streaming, interactive, and background), the following types of AAL2 path can be configured:
Issue 01 (2010-10-15)
3-20

3 Protocol Stacks
CBR RT-VBR NRT-VBR UBR
According to different types of service (R99, HSDPA, and HDUPA), the following types of AAL2 path can be configured:

R99 HSPA
The AAL2 path can be configured through the ADD AAL2PATH command. When an AAL2 path is configured, the TXTRFX and RXTRFX parameters need to be set. They determine the type of path. The TXTRFX and RXTRFX parameters record the ATM traffic, and they can be configured through the ADD ATMTRF command. For details, see section 3.6.3 "ATM Traffic Records". An AAL2 path is carried on a PVC. The parameters VPI and VCI are used to identify the PVCs. The PVC identifier and other PVC attributes must be negotiated between the BSC6900 and the peer end.
AAL2 Route
An AAL2 path may reach not the destination node but an adjacent node. In this case, AAL2 routes can be configured to reach the destination node. The AAL2 route to an ATM node can be configured through the ADD AAL2RT command. Figure 3-24 shows an example of the AAL2 route. Figure 3-24 Example of the AAL2 route
Even if the destination node and the adjacent node are the same, an AAL2 route needs to be configured. The AAL2 route cannot be configured for the adjacent node of the IUPS type.
3.8 MTP3/M3UA
3.8.1 MTP3
MTP3 links are contained in an MTP3 link set. MTP3 links are carried on the SAAL links of Network-to-Network Interface (NNI) type. You can run the command ADD MTP3LKS to specify an MTP3 link set, and then run the command ADD MTP3LNK to add the MTP3 links by using the parameter SIGLKSX.
MTP3 Links for Iu-CS Interface

The configuration of MTP3 links between the BSC6900 and the MSC server depends on the networking between the MSC server and the BSC6900:
Issue 01 (2010-10-15)
3-21
3 Protocol Stacks
If the MSC server is directly connected to the BSC6900, at least one MTP3 link is required for the MSC server (IUCS_RANAP signaling point). It is recommended that more than one MTP3 link be configured. If the MSC server is connected to the BSC6900 through the MGW, the MSC server (IUCS_RANAP signaling point) does not require any MTP3 link. If the MSC server is connected to the BSC6900 not only directly but also through the MGW, as shown in Figure 3-25, the MSC server (IUCS-RANAP) requires at least one MTP3 link. It is recommended that more than one MTP3 link be configured.
Figure 3-25 Example of connections between the MSC server and the BSC6900
MTP3 Links for Iu-PS Interface

An Iu-PS interface requires at least one MTP3 link. It is recommended that more than one MTP3 link be configured.
MTP3 Links for Iur Interface

The configuration of MTP3 links depends on the networking between the BSC6900 and the neighboring BSC6900:

If the BSC6900 is directly connected to the neighboring BSC6900, the Iur interface requires at least one MTP3 link. It is recommended that more than one MTP3 link be configured. If the BSC6900 is connected to the neighboring BSC6900 through a Signaling Transfer Point (STP), no MTP3 link is required.
It is recommended that the SAAL links of NNI type be evenly distributed to the SPU subsystems in the MPS/EPS so that the signaling exchange can be reduced between the SPU subsystems.
3.8.2 Types of MTP3/M3UA DSPs

The BSC6900 supports seven types of Destination Signaling Point (DSP): IUCS, IUCS_ALCAP, IUCS_RANAP, IUPS, IUR, STP, and AAL2SWITCH. DSPs of different types have different meanings. Table 3-7 describes the types of DSP.
Issue 01 (2010-10-15)
3-22
3 Protocol Stacks
Table 3-7 Types of DSP DSP Type IUCS IUCS_ALCAP IUCS_RANAP IUPS IUR STP AAL2SWITCH Description R99 MSC DSP. The IUCS DSP has the control plane functions of both radio network layer and transport network layer on the Iu-CS interface. R4 MGW DSP. The IUCS_ALCAP DSP has the control plane functions of the transport network layer on the Iu-CS interface. R4 MSC server DSP. The IUCS_RANAP DSP has the control plane functions of the radio network layer on the Iu-CS interface. Signaling point in the Iu-PS control plane Other BSC6900 signaling points Signaling transfer point AAL2 transfer point
3.8.3 Signaling Route Mask and Signaling Link Mask

The number (represented by n) of 1s in a signaling route mask determines the maximum number of routes (2n). For example, B0000 indicates that there is at most one route. B0001 or B1000 indicates that there are at most two routes. The number (represented by n) of 1s in a signaling link mask determines the maximum number of links (2n). For example, B0000 indicates that there is at most one link. B0001 or B1000 indicates that there are at most two links. The result of the logical AND operation on the signaling link mask and the signaling route mask must be 0, as shown in Figure 3-18. Figure 3-26 Relation between signaling link mask and signaling route mask
3.9 AAL5 Path

In ATM transport mode, AAL5 connections are used to carry the signaling on the Iub/Iur/Iu interface (WRFD-05030105 permanent AAL5 connections for control plane traffic). As defined in the 3GPP specifications, UNI-SAAL is used for control plane connections on the Iub interface, and NNI-SAAL is used for control plane connections on the Iur and Iu interfaces. The AAL5 connections for Iub/Iu-CS/Iur are set up by configuring the SAAL links. You can run the ADD SAALLNK command to configure the AAL5 connections on the Iub/Iur/Iu-CS interface. When an AAL5 connection is configured, the TXTRFX and RXTRFX parameters need to be
Issue 01 (2010-10-15)
3-23
3 Protocol Stacks
set. The TXTRFX and RXTRFX parameters record the ATM traffic, and they can be configured through the ADD ATMTRF command. An SAAL link is carried on an ATM PVC, the parameters CARRYVPI and CARRYVCI are used to identify the PVCs. The PVC identifier and other PVC attributes must be negotiated between the BSC6900 and the peer end. The signaling messages carried on the UNI-SAAL links are classified into NCP, CCP, and ALCAP, and the signaling messages carried on the NNI-SAAL links are MTP3, as described in Table 3-8. Table 3-8 Data carried on SAAL links Data Type NCP CCP ALCAP MTP3 Description The NCP carries common process messages of NBAP over the Iub interface. An Iub interface has only one NCP. A CCP carries dedicated process messages of NBAP over the Iub interface. An Iub interface may have multiple CCPs. The number of CCPs depends on network planning. ALCAP is also called Q.AAL2. Typically, an Iub interface has one ALCAP. MTP3 links are contained in an MTP3 link set. MTP3 links are carried on the SAAL links of Network-to-Network Interface (NNI) type.
3.10 IPOA PVC

IPOA is a technology in which IP packets are transmitted over the ATM transport network. Essentially, the ATM links over each interface are carried over PVCs. The IPoA PVCs on the Iub interface are used to transmit the OM information of a NodeB. In this case, the IPoA PVC is called the management plane IPoA PVC. The IPoA PVC on the Iu-PS interface is a PVC to the SGSN gateway. The IPOA PVC can be configured through the ADD IPOAPVC command. If the parameter PEERT is set to IUB, the IPOA link can only be used as an OM channel. The parameters CARRYVPI and CARRYVCI are used to identify the PVCs. When an IPOA PVC is configured, the TXTRFX and RXTRFX parameters need to be set. The TXTRFX and RXTRFX parameters record the ATM traffic, and they can be configured through the ADD ATMTRF command.
3.11 F5
Huawei supports operations on ATM OAM F5 end-to-end flows specified in ITU I.610 (WRFD-05030110 F5):
Fault management
AIS: RDI: CC:
alarm indication signal remote defect indication continuity check and loopback monitoring reporting
Performance management
Forward Backward
Activation and deactivation
Issue 01 (2010-10-15)
3-24
3 Protocol Stacks
The CC can be activated to monitor the end-to-end AAL2 path virtual connect link (VCL) and Iu-PS user plane VCL. When one VCL for AAL2 path or Iu-PS GTPU is loss of continuity (LOC), AIS, or RDI, this VCL is blocked. Then the service is established on other alternative VCLs to prevent the failure of the call. You can run the SET VCLLOP command to activate or deactivate the CC function. When the parameter LOPT is set to LOCAL_LOOP, and the LOP VCL command is executed, the CC function is activated. When the parameter LOPT is set to NO_LOOP, the CC function is deactivated. Huawei also supports proprietary delay detection function. When an NE receives a detection start command from the NMS, it starts detecting delay on the current AAL2 link or AAL5 link and periodically reports the delay to the NMS. The 8-byte reserved IE (LB IE) in the loopback message is used to store the message transmission time. When an NE receives the loopback message, it calculates the delay based on the time difference between transmission and reception.
Issue 01 (2010-10-15)
3-25
4 ATM Transmission Resources
4 ATM Transmission Resources

ATM transmission resources can be classified into physical resources, logical ports, resource groups, and paths. The transmission resources for Iub/Iu/Iur interfaces vary according to different networking. Huawei supports the following types of ATM transmission:

ATM over E1T1 on Iub interface (WRFD-05030101 ATM over E1T1 on Iub interface) ATM over channelized STM-1/OC-3 on Iub interface (WRFD-05030102 ATM over channelized STM-1/OC-3 on Iub interface) ATM over non-channelized STM-1/OC-3c on Iub/Iu/Iur interface (WRFD-05030103 ATM over non-channelized STM-1/OC-3c on Iub/Iu/Iur interface)
For details about the ATM transmission resources, see "Transmission Resources" in the Transmission Resource Management Feature Parameter Description.
Issue 01 (2010-10-15)
4-1
5 ATM Transmission Resource Management
5 ATM Transmission Resource Management

For ATM transport, Huawei provides the following transmission resource management:

Admission control (WRFD-05030106 Call Admission Based on Used AAL2 Path Bandwidth), which is used to allow more users to be admitted with the QoS guaranteed. Transmission resource mapping, in which the CBR, RT-VBR, NRT-VBR, and UBR ATM QoS classes are used to implement differentiated services. Iub overbooking (WRFD-050405 Overbooking on ATM Transmission, WRFD-050406 ATM QoS Introduction on Hub Node B (Overbooking on Hub Node B Transmission)), which is used to improve the usage efficiency on ATM transport scenario
For details about admission control, transmission resource mapping, and Iub overbooking, see the Transmission Resource Management Feature Parameter Description.
Issue 01 (2010-10-15)
5-1
6 Parameters
6 Parameters
The following describes the parameters related to ATM Transport feature. Table 6-1 Parameter description Parameter ID TXTRFX NE BSC6900 MML ADD VPCLCX(Mandatory) Description Meaning: Sending traffic index of the low end VPL/VCL GUI Value Range: 100~1999 Actual Value Range: 100~1999 Unit: None Default Value: None Meaning: Receiving traffic index of the low end VPL/VCL GUI Value Range: 100~1999 Actual Value Range: 100~1999 Unit: None Default Value: None Meaning: IPoA PVC peer type GUI Value Range: IUB, IUPS, OTHER Actual Value Range: IUB, IUPS, OTHER Unit: None Default Value: None Meaning: Peak rate of the ATM traffic GUI Value Range: 30~353207 Actual Value Range: 30~353207 Unit: None Default Value: None Meaning: Average rate of the ATM traffic GUI Value Range: 30~117924 Actual Value Range: 30~117924 Unit: None Default Value: None Meaning: Minimum guarantee rate of the ATM traffic GUI Value Range: 30~70754 Actual Value Range: 30~70754 Unit: None Default Value: None Meaning: Tolerable delay jitter GUI Value Range: 1024~212000 Actual Value Range: 1024~212000 Unit: 100ns Default Value: 1024
RXTRFX
BSC6900
ADD VPCLCX(Mandatory)
PEERT
BSC6900
ADD IPOAPVC(Mandatory)
PCR
BSC6900
ADD ATMTRF(Optional)
SCR
BSC6900
MCR
BSC6900
CDVT
BSC6900
Issue 01 (2010-10-15)
6-1
6 Parameters
Parameter ID MBS
NE BSC6900
MML ADD ATMTRF(Optional)
Description Meaning: Maximum burst size (MBS) GUI Value Range: 3~10000 Actual Value Range: 3~10000 Unit: byte Default Value: None Meaning: Rate unit GUI Value Range: CELL/S, KBIT/S Actual Value Range: CELL/S, KBIT/S Unit: None Default Value: None Meaning: TX traffic record index of the AAL2 Path on the out BSC6900 port (ATM layer PVC traffic). The traffic index is configured in the ATM traffic table (see "LST ATMTRF"). GUI Value Range: 100~1999 Actual Value Range: 100~1999 Unit: None Default Value: None Meaning: Sending traffic index GUI Value Range: 100~1999 Actual Value Range: 100~1999 Unit: None Default Value: None Meaning: TX traffic record index of the SAAL link GUI Value Range: 100~1999 Actual Value Range: 100~1999 Unit: None Default Value: None Meaning: RX traffic record index of the AAL2 Path on the out BSC6900 port (ATM layer PVC traffic). The traffic index is configured in the ATM traffic table (see "LST ATMTRF"). GUI Value Range: 100~1999 Actual Value Range: 100~1999 Unit: None Default Value: None Meaning: Receiving traffic index GUI Value Range: 100~1999 Actual Value Range: 100~1999 Unit: None Default Value: None
UT
BSC6900
TXTRFX
BSC6900
ADD AAL2PATH(Mandatory) MOD AAL2PATH(Optional)
TXTRFX
BSC6900
ADD IPOAPVC(Optional) MOD IPOAPVC(Optional)
TXTRFX
BSC6900
ADD SAALLNK(Mandatory) MOD SAALLNK(Optional)
RXTRFX
BSC6900
RXTRFX
BSC6900
Issue 01 (2010-10-15)
6-2
6 Parameters
Parameter ID RXTRFX
NE BSC6900
MML ADD SAALLNK(Mandatory) MOD SAALLNK(Optional)
Description Meaning: RX traffic record index of the SAAL link GUI Value Range: 100~1999 Actual Value Range: 100~1999 Unit: None Default Value: None Meaning: VPI of the AAL2 path out BSC6900 GUI Value Range: 0~4095 Actual Value Range: 0~4095 Unit: None Default Value: None Meaning: Uniquely identifies a signaling link set GUI Value Range: 0~186 Actual Value Range: 0~186 Unit: None Default Value: None Meaning: Uniquely identifies a signaling link set GUI Value Range: 0~186 Actual Value Range: 0~186 Unit: None Default Value: None Meaning: Uniquely identifies a signaling link set GUI Value Range: 0~186 Actual Value Range: 0~186 Unit: None Default Value: None Meaning: Uniquely identifies a signaling link set GUI Value Range: 0~186 Actual Value Range: 0~186 Unit: None Default Value: None Meaning: Uniquely identifies a signaling link set GUI Value Range: 0~186 Actual Value Range: 0~186 Unit: None Default Value: None Meaning: Uniquely identifies a signaling link set GUI Value Range: 0~186 Actual Value Range: 0~186 Unit: None Default Value: None
VPI
BSC6900
SIGLKSX
BSC6900
ADD M3LKS(Mandatory) MOD M3LKS(Mandatory) RMV M3LKS(Mandatory)
SIGLKSX
BSC6900
ADD M3LNK(Mandatory) MOD M3LNK(Mandatory) RMV M3LNK(Mandatory)
SIGLKSX
BSC6900
ADD M3RT(Mandatory) MOD M3RT(Mandatory) RMV M3RT(Mandatory)
SIGLKSX
BSC6900
ADD MTP3LKS(Mandatory) MOD MTP3LKS(Mandatory) RMV MTP3LKS(Mandatory)
SIGLKSX
BSC6900
ADD MTP3LNK(Mandatory) MOD MTP3LNK(Mandatory) RMV MTP3LNK(Mandatory)
SIGLKSX
BSC6900
ADD MTP3RT(Mandatory) MOD MTP3RT(Mandatory) RMV MTP3RT(Mandatory)
Issue 01 (2010-10-15)
6-3
6 Parameters
Parameter ID CARRYVPI
NE BSC6900
MML ADD IPOAPVC(Optional) MOD IPOAPVC(Optional)
Description Meaning: VPI value of the VCL of the bearer network GUI Value Range: 0~4095 Actual Value Range: 0~4095 Unit: None Default Value: None Meaning: VPI value of the SAAL out BSC6900 GUI Value Range: 0~4095 Actual Value Range: 0~4095 Unit: None Default Value: None Meaning: VCI value of the VCL of the bearer network GUI Value Range: 32~65535 Actual Value Range: 32~65535 Unit: None Default Value: None Meaning: VCI value of the SAAL out BSC6900 GUI Value Range: 32~65535 Actual Value Range: 32~65535 Unit: None Default Value: None Meaning: Local IP address GUI Value Range: None Actual Value Range: 0.0.0.0~255.255.255.255 Unit: None Default Value: None Meaning: Peer IP address GUI Value Range: None Actual Value Range: 0.0.0.0~255.255.255.255 Unit: None Default Value: None
CARRYVPI
BSC6900
CARRYVCI
BSC6900
CARRYVCI
BSC6900
IPADDR
BSC6900
ADD IPOAPVC(Mandatory) RMV IPOAPVC(Mandatory) MOD IPOAPVC(Mandatory)
PEERIPADDR
BSC6900
ADD IPOAPVC(Mandatory) RMV IPOAPVC(Mandatory) MOD IPOAPVC(Mandatory)
Issue 01 (2010-10-15)
6-4
7 Counters
7 Counters
There are no specific counters associated with this feature.
Issue 01 (2010-10-15)
7-1
8 Glossary
8 Glossary
For the acronyms, abbreviations, terms, and definitions, see the Glossary.
Issue 01 (2010-10-15)
8-1
9 Reference Documents
9 Reference Documents
[1] Transmission Resource Management Feature Parameter Description
Issue 01 (2010-10-15)
9-1

Feature Parameter Description: ATM Transport RAN12.0

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

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

Feature Parameter Description: ATM Transport RAN12.0

Hochgeladen von

Copyright:

Verfügbare Formate

ATM Transport RAN12.

Feature Parameter Description

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2011. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

WCDMA RAN ATM Transport

2 Overview of ATM Transport ....................................................................................................2-1 3 Protocol Stacks .........................................................................................................................3-1

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN ATM Transport

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN ATM Transport

1.2 Intended Audience

1.3 Change History

01 (2010-10-15) Draft (2010-03-30)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN ATM Transport

2 Overview of ATM Transport

2 Overview of ATM Transport

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN ATM Transport

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN ATM Transport

3.1.2 Links on the Iub Interface

3.1.3 OM IPoA Data Configuration on the Iub Interface

OM IPoA PVC on the Iub Interface

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN ATM Transport

3.2 Iu-CS over ATM

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN ATM Transport

3.2.2 Links on the Iu-CS Interface

3.2.3 Differences of the Iu-CS Interface Between R99 and R4/R5/R6/R7/R8

Iu-CS Interface Defined in the 3GPP R4/R5/R6/R7/R8

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN ATM Transport

Figure 3-6 Iu-CS interface in the 3GPP R4/R5/R6/R7/R8

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN ATM Transport

Functions of the MSC and of the MSC Server and MGW

Data Configuration on the BSC6900

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN ATM Transport

R4/R5/R6/R7/R8 More than one

3.3 Iu-PS over ATM

3.3.2 Links on the Iu-PS Interface

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN ATM Transport

Figure 3-10 Links on the ATM-based Iu-PS interface

The RINT shown in Figure 3-10 refers to the UOIa/UOIc board.

3.3.3 IPoA Data Configuration on the Iu-PS User Plane

IPoA PVC on the Iu-PS User Plane

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN ATM Transport

IPoA Data on the Iu-PS User Plane

3.4 Iur over ATM

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN ATM Transport

Figure 3-12 Protocol stack for the ATM-based Iur interface

3.4.2 Links on the Iur Interface

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN ATM Transport