Common Transmission(RAN13.0 01)

Common Transmission SRAN6.0

Feature Parameter Description

Issue 01

Date 2011-03-30

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: http://www.huawei.com

Email: [email protected]

http://www.huawei.com/

mailto:[email protected]

SingleRAN

Common Transmission Contents

Issue 01 (2011-03-30) Huawei Proprietary and Confidential

Copyright © Huawei Technologies Co., Ltd

i

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 Co-Transmission ............................................................................................... 2-1

2.1 Definition ....................................................................................................................................... 2-1

2.2 Benefits ......................................................................................................................................... 2-1

2.3 Application Scenarios .................................................................................................................... 2-1

2.3.1 GU Co-Transmission on the MBSC Side .............................................................................. 2-1

2.3.2 GL/UL/GU Co-Transmission on the Base Station Side ........................................................ 2-2

3 GU Co-Transmission ................................................................................................................ 3-1

3.1 GU Co-Transmission Types .......................................................................................................... 3-1

3.2 Co-Transmission for the Iub and Abis Interfaces .......................................................................... 3-1

3.2.1 Network Topologies .............................................................................................................. 3-1

3.2.2 Iub/Abis Co-Transmission Protocol Stack ............................................................................ 3-7

3.2.3 Configurations and Capabilities ............................................................................................ 3-7

3.3 Co-Transmission for the Iu-CS and A Interfaces ........................................................................... 3-9

3.3.1 Network Topologies .............................................................................................................. 3-9

3.3.2 Iu-CS/A Co-Transmission Protocol Stack ........................................................................... 3-10

3.3.3 Configurations and Capabilities .......................................................................................... 3-11

3.4 Co-Transmission for the Iu-PS and Gb Interfaces ...................................................................... 3-12

3.4.1 Network Topologies ............................................................................................................ 3-12

3.4.2 Iu-PS/Gb Co-Transmission Protocol Stack ........................................................................ 3-12

3.4.3 Configurations and Capabilities .......................................................................................... 3-13

4 GL Co-Transmission ................................................................................................................ 4-1

4.1 IP-Based GL Co-Transmission Through FE Ports Interconnection .............................................. 4-1

4.2 Route Backup Through FE Ports Interconnection ........................................................................ 4-2

5 UL Co-Transmission ................................................................................................................ 5-1

5.1 IP-Based Co-Transmission Through FE Ports Interconnection .................................................... 5-1

5.2 Route Backup Through FE Ports Interconnection ........................................................................ 5-2

5.3 Hybrid Transmission Through FE Ports Interconnection .............................................................. 5-4

6 Engineering Guidelines ........................................................................................................... 6-1

6.1 Configuration Guidelines for Co-Transmissoin on the Base Station Controller Side .................... 6-1

6.2 Configuration Guidelines for Co-Transmissoin on the Base Station Side ..................................... 6-1

6.2.1 Overview ............................................................................................................................... 6-1

6.2.2 Configuring Routes to Forward IP Packets .......................................................................... 6-1

6.2.3 Configuring Standard ARP Proxy and Routes to Forward IP Packets ................................. 6-2

SingleRAN

Common Transmission Contents



ii

7 Parameters ................................................................................................................................. 7-1

8 Counters ...................................................................................................................................... 8-1

9 Glossary ...................................................................................................................................... 9-1

10 Reference Documents ......................................................................................................... 10-1

SingleRAN

Common Transmission 1 Introduction



1-1

1 Introduction

1.1 Scope

This document provides a common transmission (co-transmission) solution, including GSM and UMTS (GU) co-transmission on the base station controller/base station side, GSM and LTE (GL) co-transmission on the base station side, and UMTS and LTE (UL) co-transmission on the base station side.

For details about the description of GU common transmission resource management, see the Transmission Resource

Management Feature Parameter Description.

For details about the description of IP transmission in the GSM and UMTS, see the IP BSS Feature Parameter Description of the GBSS and the IP RAN Feature Parameter Description of the UMTS respectively.

1.2 Intended Audience

This document is intended for:

Personnel who are familiar with GSM, WCDMA, and LTE basics

Personnel who need to understand the co-transmission feature

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 co-transmission 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 (2011-03-30)

Draft A (2010-12-30)

01 (2011-03-30)

This is the document for the first commercial release of SRAN6.0.

Compared with issue Draft A (2010-12-30) of SRAN6.0, this issue optimizes the description.

Draft A (2010-12-30)

This is the draft of the document for SRAN6.0.

Compared with issue 01 (2010-10-15) of SRAN5.0, this issue optimizes the description.

Transmission%20Resource%20Management.htm


IP%20RAN.htm

SingleRAN

Common Transmission 2 Overview of Co-Transmission



2-1

2 Overview of Co-Transmission

2.1 Definition

Co-transmission mentioned in this document refers to the IP-based co-transmission for GU, GL, and UL. That is, IP transmission ports and IP transport networks are shared in GU, GL, and UL co-transmission scenarios to achieve the sharing of transmission resources.

2.2 Benefits

Co-transmission reduces the capital expenditure (CAPEX) and operational expenditure (OPEX) and simplifies the transmission maintenance in the following ways:

The sharing of transmission ports and transmission bandwidth is cost-effective.

The sharing of transmission networks simplifies the transmission configuration and maintenance.

2.3 Application Scenarios

2.3.1 GU Co-Transmission on the MBSC Side

Figure 2-1 Typical application scenarios of GU co-transmission

As shown in Figure 2-1, the GSM and UMTS networks that are deployed together share an MBSC. In this situation, co-transmission is achieved in the following ways:

On the core network (CN) side, the Iu-CS and A interfaces and the Iu-PS and Gb interfaces of the MBSC can share a common IP network when GSM and UMTS share the CN (that is, share the MSC server, MGW, and SGSN).

On the radio access network (RAN) side, the Iub and Abis interfaces can share a common IP network when a multi-mode base station (MBTS) is used or the GSM BTS and UMTS NodeB share an equipment room.

SingleRAN

Common Transmission 2 Overview of Co-Transmission



2-2

The MBSC mentioned in this document refers to Huawei GSM+UMTS dual-mode base station controller.

The MBTS mentioned in this document refers to Huawei multi-mode base station.

2.3.2 GL/UL/GU Co-Transmission on the Base Station Side

Figure 2-2 GL co-transmission by interconnecting FE ports on the base station side

As shown in Figure 2-2, in the scenario where the BTS and eNodeB are co-sited and share a common BBU or the MBTS and eNodeB are co-sited and share a common BBU, IP-based co-transmission can be achieved by interconnecting FE ports on the board panels on the base station side. This solution is the same for UL co-transmission, GU co-transmission, and GL co-transmission on the base station side.

In co-transmission scenarios where FE ports on the board panels are interconnected, if one mode providing the co-transmission port is reset, upgraded, or malfunctions, the services of the other mode are affected.

The sharing of a common BBU refers to the situation where the boards of two radio access technologies (RATs) are

installed in the same BBU.

This document takes the distributed base station (DBS) as an example to describe the co-transmission on the base station side. The co-transmission principle for macro base stations is the same as that for DBSs and thus is not described in this document.

SingleRAN

Common Transmission 3 GU Co-Transmission



3-1

3 GU Co-Transmission

3.1 GU Co-Transmission Types

The Huawei SingleRAN solution supports the following types of GU co-transmission:

IP-based GU co-transmission on the MBSC side (corresponding to the feature MRFD-211502 IP-Based BSC and RNC Co-Transmission on MBSC Side)

− IP-based co-transmission for the Iub and Abis interfaces on the MBSC side

− IP-based co-transmission for the Iu-CS and A interfaces

− IP-based co-transmission for the Iu-PS and Gb interfaces

GU co-transmission on the base station side

− IP-based co-transmission for the Iub and Abis interfaces on the MBTS side

− TDM-based co-transmission for the Iub and Abis interfaces on the base station side

The transmission resources to be shared are the physical ports and transport network.

3.2 Co-Transmission for the Iub and Abis Interfaces

The IP-based GU co-transmission differs from the IP transmission in the GSM or UMTS in terms of network topology and IP address configuration. The following sections describe the network topology, protocol stack, configurations, and capabilities of the co-transmission for the Iub and Abis interfaces.

3.2.1 Network Topologies

IP-Based Co-Transmission for the Iub and Abis Interfaces on the MBSC Side

When the MBSC operates in GU mode, the IP transport network and the physical port on the interface board of the MBSC can be shared by the Iub and Abis interfaces. Figure 3-1 and Figure 3-2 show the network topologies of the co-transmission based on FE/GE and E1/T1 over STM-1/OC-3 for the Iub and Abis interfaces. FE/GE is used, when possible.

When the co-transmission is implemented on the basis of the E1/T1 over STM-1/OC-3 mode, the data link layer uses the PPP/MLPPP protocol. The traffic flow of the BTS and that of the NodeB correspond to different PPP links or MLPPP groups. In the case of the GU MBTS, the traffic flow of the GSM network and that of the UMTS network share one PPP link or MLPPP group, and the traffic flow of the GSM network is distinguished from the traffic flow of the UMTS network by user datagram protocol (UDP) ports.

When the co-transmission is implemented on the basis of the FE/GE mode, the data link layer uses the Ethernet protocol.

The MBSC interface board identifies the GSM data and the UMTS data, and sends the data to the corresponding GSM/UMTS service processing board and signaling processing board.

SingleRAN




3-2

Figure 3-1 Iub/Abis co-transmission based on FE/GE on the MBSC side

Figure 3-2 Iub/Abis co-transmission based on E1/T1 over STM-1/OC-3 on the MBSC side

2G UP: processing board of the GSM user plane

2G CP: processing board of the GSM control plane

3G UP: processing board of the UMTS user plane

3G CP: processing board of the UMTS control plane

IP_GCUP: IP address of the GSM control/user plane

IP_UCP: IP address of the UMTS control plane

IP_UUP: IP address of the UMTS user plane

IP-Based Co-Transmission for the Iub and Abis Interfaces on the MBTS Side

When the MBTS operates in GU mode, the Iub and Abis interfaces can share the IP transport network and physical port through FE ports interconnection so that IP-based co-transmission is achieved. GU co-transmission on the base station side (corresponding to the feature MRFD-221501 IP-Based Multi-mode Co-Transmission on BS side(NodeB), or MRFD-211501 IP-Based Multi-mode Co-Transmission on BS side(GBTS)) can be based on IP over Ethernet or IP over E1/T1. For IP-based GU co-transmission on the BS side, only the UMTS can provide the co-transmission port.

SingleRAN




3-3

Figure 3-3 Iub/Abis co-transmission based on FE on the base station side

As shown in Figure 3-3, the main control board WMPT of UMTS provides an FE port (functioning as the common transmission port of GU) to connect to the transport network. GSM data and UMTS data in the base station achieve IP over Ethernet co-transmission through FE ports interconnection.

The FE ports can be interconnected in the following ways, as described in Table 3-1.

Table 3-1 FE ports interconnection

FE Ports Interconnection

The WMPT board and the GTMU board use the FE optical port to perform FE ports interconnection.

In this situation, the WMPT uses the FE electrical port to connect to the transport network.

The WMPT board and the GTMU board use the FE electrical port to perform FE ports interconnection.

In this situation, the WMPT uses the FE optical port to connect to the transport network.

In FE ports interconnection, the co-transmission is implemented on the Iub interface. The GSM data is switched to the WMPT board through the FE port on the GTMU board. The WMPT multiplexes the GSM data and UMTS data, and then transmits them to the shared transport network. Figure 3-4 and Figure 3-5 are shown as examples of network topologies of the distributed GU MBTS. The GU co-transmission network topologies of the macro base stations are similar to those of the DBSs.

The interface board of the GU MBTS identifies the GSM data and UMTS data, and sends the data to the corresponding GSM/UMTS baseband processing board and CPRI interface board.

SingleRAN




3-4

Figure 3-4 Iub/Abis co-transmission based on E1/T1 on the base station side

As shown in Figure 3-4, the WMPT provides an E1/T1 port (functioning as the common transmission port of GU) to connect to the transport network. GSM data and UMTS data in the base station achieve IP over E1/T1 co-transmission through FE ports interconnection. The UMTS WMPT uses MLPPP to bind E1 links and routes GSM data packets to the GTMU through the interconnected FE ports.

The base station controller shown in Figure 3-4 may be a BSC, an RNC, or an MBSC.

The UMTS UTRP can provide a GE port to connect to the transport network in GU co-transmission scenario.

The GBTS and NodeB can achieve route backup through FE ports interconnection. As shown in Figure 3-5, an active route passes through the transmission port of one RAT to the IP network, and a standby route passes through the transmission port of one RAT to that of another RAT through the interconnected FE ports and then to the IP network. In route backup mode, the bidirectional forwarding detection (BFD) function is used to detect the link status. In normal situations, the GBTS and NodeB connect to the IP network through the active routes. When the BFD function detects that the active route of the GBTS or NodeB becomes unavailable, the data flow of GSM or UMTS is switched to the standby route. After the active route is restored, the data flow is automatically switched back to the active route if the single-hop BFD mode is used; the data flow needs to be manually switched to the active route if the multi-hop BFD mode is used.

SingleRAN




3-5

Figure 3-5 Example of route backup for IP-based GU co-transmission (assuming that the UMTS transmission route is first unavailable and then restored)

The base station controller shown in Figure 3-5 may be a BSC, an RNC, or an MBSC.

Route backup is applicable only to IP over Ethernet.

Route backup is not applicable in a scenario where the UTRP provides a transmission port to connect to the transport network.

In route backup mode, the GTMUb and WMPT use the same type of port (an optical port or an electrical port) to connect to the transport network or to perform FE ports interconnection.

Route backup supports the BFD function. When the active route becomes unavailable, the quality of OM data flow, signaling data flow, and high-priority data flow is ensured.

In route backup mode, the IEEE1588 clock supports active/standby switchover in unicast mode but not in multicast mode.

TDM-Based Co-Transmission for the Iub and Abis Interfaces on the Base Station Side

This section describes/involves the feature "MRFD-221504 TDM-Based Multi-mode Co-Transmission via Backplane on BS side(NodeB)", or "MRFD-211504 TDM-Based Multi-mode Co-Transmission via Backplane on BS side(GBTS)".

TDM-based co-transmission for the Iub and Abis Interfaces on the base station side can be implemented through TDM over packet (TOP) method.

SingleRAN




3-6

The GSM and UMTS traffic can be multiplexed onto the same SDH/PDH network through the TDM timeslot cross-connect function. Through the fractional ATM or fractional IP function, the RNC and NodeB can map ATM cells or IP packets onto several E1 timeslots. TDM timeslots can be shared by the GU networks on the Abis and Iub interfaces respectively. Figure 3-6 shows the principle of TDM-based co-transmission.

Figure 3-6 Principle of TDM-based co-transmission

Figure 3-7 shows the TDM timeslots shared on the Iub interface. The UMTS data is transmitted on some E1 timeslots through the fractional ATM or fractional IP function, and then the GSM data is transmitted on the remaining E1 timeslots. In this solution, the UMTS equipment provides the timeslot cross-connect function.

Figure 3-7 TDM time slots shared on the Iub interface

Figure 3-8 shows the TDM timeslots shared on the Abis interface. The GSM data is transmitted on some E1 timeslots, and then the UMTS data is transmitted on the remaining E1 timeslots through the fractional ATM or fractional IP function. In this solution, the GSM equipment provides the timeslot cross-connect function.

SingleRAN




3-7

Figure 3-8 TDM time slots shared on the Abis interface

In TDM-based co-transmission scenario, the requirement for reference clock of MBTS is as follows: if the UMTS NodeB shares E1/T1 transmission resources with GSM BTS, it is recommended that the E1/T1 clock source is configured at the GSM BTS, and the UMTS NodeB uses the E1/T1 clock source provided by the GSM BTS.

3.2.2 Iub/Abis Co-Transmission Protocol Stack

Figure 3-9 shows the protocol stack of the IP-based co-transmission for the Iub and Abis interfaces.

Figure 3-9 Protocol stack of the IP-based co-transmission for the Iub and Abis interfaces

As shown in Figure 3-9, the interface board shared by the Iub and Abis interfaces is responsible for protocol processing at the physical layer, data link layer, IP layer, and UDP layer. The protocols at other layers are processed on the processing boards of the UMTS/GSM control plane and user plane.

3.2.3 Configurations and Capabilities

Physical Layer

The following types of ports on interface boards of the MBSC support the IP-based co-transmission for the Iub and Abis interfaces:

GE optical port on the GOUa or GOUc board

SingleRAN




3-8

FE/GE electrical port on the FG2a or FG2c board

Channelized STM-1/OC-3 on the POUc board

The GE optical port provides high transmission bandwidth and supports long-distance transmission. Therefore, the GE optical port is recommended for configuration, when possible.

The following types of ports on interface boards of the GU MBTS support the IP-based co-transmission for the Iub and Abis interfaces:

FE optical/electrical port and E1/T1 port on the WMPT and UTRP (UMTS transmission units)

GE optical port on the UTRP (UMTS transmission unit)

E1/T1 port on the UTRP (UMTS transmission unit)

The UTRP has a limited bandwidth and does not facilitate GSM capacity expansion. Therefore, it is not recommended that the E1/T1 port of the UTRP functions as the common transmission port of GU.

In the IP-based GU co-transmission mode, the ports on the UMTS transmission unit are connected to the base station controller.

Data Link Layer

When FE/GE is used in co-transmission for the Iub and Abis interfaces, the Ethernet protocol is used at the data link layer. When E1/T1 over STM-1/OC-3 is used in co-transmission for the Iub and Abis interfaces, a PPP link or MLPPP group is used at the data link layer. A PPP link can be bound with one to thirty-one 64 kbit/s timeslots carried on only one E1/T1

A MLPPP link in the MLPPP group is bound with at least eight timeslots. In addition, the number of timeslots bound with each MLPPP link in the MLPPP group must be the same.

IP Addressing Principles

The IP addressing principles on the base station controller side are as follows:

Port IP address

The IP address can be PPP/MLPPP link IP address, Ethernet port IP address or device IP address. The Iub and Abis interfaces can share the same IP address. It is recommended that the Iub and Abis interfaces use different IP addresses.

Control plane IP address and user plane IP address on the Iub interface

On the Iub interface, the control plane IP address and user plane IP address can be the same or different.

Control plane IP address and user plane IP address on the Abis interface

On the Abis interface, the control plane IP address is the same as the user plane IP address.

The port IP address, control plane IP address, and user plane IP address can be the same on the Iub and Abis interfaces.

IP address of the OM channel

On the Iub interface,

− If the OM channel between the NodeB and the M2000 is established through the MBSC, the IP address of the OM channel is configured at the NodeB and M2000. The MBSC transmits only the OM packets between the M2000 and the NodeB.

− If the OM channel between the NodeB and the M2000 is not established through the MBSC, the IP address of the OM channel is configured at the NodeB and M2000. The MBSC does not transmit the OM packets between the M2000 and the NodeB.

SingleRAN




3-9

On the Abis interface, the IP address of the OM channel is configured in the MBSC and is the same as the control/user plane IP address.

The IP addressing principles on the base station side are as follows:

IP address on the Abis interface

The Abis interface needs to be configured with only one IP address.

On the Abis interface, the port IP address, control/user plane IP address, and IP address of the OM channel are the same.

IP address on the Iub interface

The Iub interface needs to be configured with three IP addresses.

On the Iub interface, the port IP address is the same as the control/user plane IP address. In addition, the OM channel is configured with one IP address and the FE interconnection port is configured with one IP address.

3.3 Co-Transmission for the Iu-CS and A Interfaces

IP-based GU co-transmission differs from the IP transmission in the GSM or UMTS in terms of network topology and IP address configuration. The following sections describe the network topology, protocol stack, configurations, and capabilities of the co-transmission for the Iu-CS and A interfaces.


When the MBSC operates in GU mode, the Iu-CS and A interfaces share the IP transport network and the physical port on the interface board of the MBSC. Figure 3-10 and Figure 3-11 show the network topologies of the co-transmission based on FE/GE and E1/T1 over STM-1/OC-3 for the Iu-CS and A interfaces. When possible, the FE/GE interface type is used.

The MBSC interface board identifies the GSM data and UMTS data, and sends the data to the corresponding GSM/UMTS service processing board and signaling processing board.

Figure 3-10 Iu-CS/A co-transmission based on FE/GE

SingleRAN




3-10

Figure 3-11 Iu-CS/A co-transmission based on E1/T1 over STM-1/OC-3

2G UP: processing board of the GSM user plane

2G CP:OPC_2G: originating signaling point of the GSM control plane


3G CP:OPC_3G: originating signaling point of the UMTS control plane

IP_GCP: GSM control plane IP address

IP_UCP: UMTS control plane IP address

IP_GUP: GSM user plane IP address

IP_UUP: UMTS user plane IP address

3.3.2 Iu-CS/A Co-Transmission Protocol Stack

Figure 3-12 shows the protocol stack of the IP-based co-transmission for the Iu-CS and A interfaces.

Figure 3-12 Protocol stack of the IP-based co-transmission for the Iu-CS and A interfaces

SingleRAN




3-11

As shown in Figure 3-12, the interface board shared by the Iu-CS and A interfaces is responsible for protocol processing at the physical layer, data link layer, IP layer, and UDP (UDP MUX) layer. The protocols at other layers are processed by the processing boards of the UMTS/GSM control plane and user plane.


Physical Layer

The following types of ports on interface boards of the MBSC support the IP-based co-transmission for the Iu-CS and A interfaces:

GE optical port on the GOUc board

FE/GE electrical port on the FG2c board

Channelized STM-1/OC-3 on the POUc board

The GE optical port provides high transmission bandwidth and supports long-distance transmission. As the traffic volume is high on the Iu-CS and A interfaces, the GE optical port is recommended for configuration, when possible.

Data Link Layer

When FE/GE is used in co-transmission for the Iub and Abis interfaces, the Ethernet protocol is used at the data link layer. When E1/T1 over STM-1/OC-3 is used in co-transmission for the Iub and Abis interfaces, a PPP link or an MLPPP group is used at the data link layer. A PPP link can be bound with one to thirty-one 64 kbit/s timeslots carried on only one E1/T1.

An MLPPP link in the MLPPP group is bound with at least eight timeslots on the MBSC side. In addition, the number of timeslots bound with each MLPPP link in the MLPPP group must be the same.


Port IP address

The IP address can be PPP/MLPPP link IP address, Ethernet port IP address or device IP address. The Iu-CS and A interfaces can share the same IP address. It is recommended that the Iu-CS and A interfaces use different IP addresses.

Control plane IP address

The Iu-CS and A interfaces share the same control plane IP address.

Generally, the SCTP link is dual-homed, that is, two control plane IP addresses are planned for one interface board. One IP address is used as the primary IP address and the other is used as the secondary IP address. The SCTP links on the Iu-CS and A interfaces share the two IP addresses. The SCTP port number is used to distinguish the signaling links on the Iu-CS and A interfaces.

User plane IP address

The Iu-CS and A interfaces use different user plane IP addresses.

The UDP MUX technique uses different Real-time Transfer Protocol (RTP) compression algorithms on the Iu-CS and A interfaces. Therefore, a separate user plane IP address must be planned on the Iu-CS interface and A interface, to distinguish the data flow on the Iu-CS interface from the data flow on the A interface.

On the Iu-CS interface, the port IP address, control plane IP address, and user plane IP address can be the same.

On the A interface, the port IP address, control plane IP address, and user plane IP address can be the same.

SingleRAN




3-12

Principles of Signaling Point Planning

A separate originating signaling point must be planned for the UMTS network and GSM network respectively. On the Iu-CS interface, the UMTS originating signaling point communicates with the CN through the RANAP signaling messages with respect to control plane signaling; on the A interface, the GSM originating signaling point communicates with the CN through the BSSMAP signaling messages with respect to control plane signaling.

The destination signaling point is planned on the CN. The UTMS and GSM can use the same or different destination signaling points.

3.4 Co-Transmission for the Iu-PS and Gb Interfaces

IP-based GU co-transmission differs from the IP transmission in the GSM or UMTS in terms of network topology and IP address configuration. The following sections describe the network topology, protocol stack, configurations, and capabilities of the co-transmission for the Iu-PS and Gb interfaces.


When the MBSC operates in GU mode, the Iu-PS and Gb interfaces share the IP transport network and the physical port on the interface board of the MBSC. The Gb interface does not support IP over E1; therefore, the co-transmission for the Iu-PS and Gb interfaces is based on only FE/GE. Figure 3-13 shows the network topology of the FE/GE-based co-transmission for the Iu-PS and Gb interfaces.

The MBSC interface board identifies the GSM data and UMTS data, and sends the data to the corresponding GSM/UMTS service processing board and signaling processing board.

Figure 3-13 FE/GE-based co-transmission for the Iu-PS and Gb interfaces

2G PCU: processing unit of the GSM user plane and control plane


3G CP:OPC_3G: originating signaling point of the UMTS control plane

IP_GCP: GSM control plane IP address

IP_UCP: UMTS control plane IP address

IP_GUP: GSM user plane IP address

IP_UUP: UMTS user plane IP address

3.4.2 Iu-PS/Gb Co-Transmission Protocol Stack

Figure 3-14 shows the protocol stack of the IP-based co-transmission for the Iu-PS and Gb interfaces.

SingleRAN




3-13

Figure 3-14 Protocol stack of the IP-based co-transmission for the Iu-PS and Gb interfaces

As shown in Figure 3-14, the interface board shared by the Iu-PS and Gb interfaces is responsible for protocol processing at the physical layer, data link layer, IP layer, and UDP layer. The protocols at other layers are processed by the processing boards of the UMTS/GSM control plane and user plane.


Physical Layer

The following types of ports on interface boards of the MBSC support the IP-based co-transmission for the Iu-PS and Gb interfaces:

GE optical port on the GOUc board

FE/GE electrical port on the FG2c board

The GE optical port provides high transmission bandwidth and supports long-distance transmssion. As the traffic volume is high on the Iu-PS and Gb interfaces, the GE optical port is recommended for configuration, when possible.

Data Link Layer

When co-transmission is implemented on the Iu-PS and Gb interfaces, the Ethernet protocol is used at the data link layer.


Port IP address

The IP address can be PPP/MLPPP link IP address, Ethernet port IP address or device IP address. The Iu-PS and Gb interfaces can share the same IP address. It is recommended that the Iu-PS and Gb interfaces use different IP addresses.

Control plane IP address

Generally, the SCTP link on the Iu-PS interface is dual-homed, that is, two control plane IP addresses are planned for one interface board. One IP address is used as the primary IP address and the other is used as the secondary IP address.

There is no IP address assigned to the control plane on the Gb interface.

SingleRAN




3-14

User plane IP address

The Iu-PS and Gb interfaces use the same or different user plane IP addresses.

On the Iu-PS interface, the Tunnel End Point Identifier (TEID) is used for the user plane of GPRS Tunneling Protocol (GTP-U) layer, to identify users. The GTP-U uses the fixed UDP port 2152, and the UDPPN of the local Network Service Virtual Link (NSVL) of the Gb interface cannot use the UDP port number of the GTP-U.

On the Iu-PS interface, the port IP address, control plane IP address, and user plane IP address can be the same.

On the Gb interface, the port IP address can be the same as the user plane IP address.

Principles of Signaling Point Planning

Only one originating signaling point is planned for the UMTS. The Iu-CS and Iu-PS interfaces share the same originating signaling point. The control plane on the GSM Gb interface uses the inband signaling, and thus no signaling link or originating signaling point needs to be configured.

The destination signaling point of the Iu-PS interface is planned in the CN, and no destination signaling point needs to be planned for the Gb interface.

../RNCParaHtml/mbsc/m-para/nsvllocal_udppn.html

SingleRAN

Common Transmission 4 GL Co-Transmission



4-1

4 GL Co-Transmission

4.1 IP-Based GL Co-Transmission Through FE Ports Interconnection

GL co-transmission on the base station side (corresponding to the feature MRFD-211501 IP-Based Multi-mode Co-Transmission on BS side(GBTS)) can be based on IP over Ethernet or IP over E1/T1. For IP-based GL co-transmission on the BS side, only the LTE can provide the co-transmission port.

Figure 4-1 shows the IP-based GL co-transmission through FE ports interconnection in IP over Ethernet mode.

Figure 4-1 IP-based GL co-transmission through FE ports interconnection in IP over Ethernet mode

The base station controller shown in Figure 4-1 may be a BSC or an MBSC.

As shown in Figure 4-1, the main controlling board LMPT of LTE provides an FE/GE port (functioning as the common transmission port of GL) to connect to the transport network. GSM data and LTE data in the base station achieve IP over Ethernet co-transmission through FE ports interconnection.




The LMPT board and the GTMU board use the FE electrical port to perform FE ports interconnection.

In this situation, the LMPT uses the FE/GE electrical port or SFP optical port to connect to the transport network.

SingleRAN




4-2

Figure 4-2 shows the IP-based GL co-transmission through FE ports interconnection in IP over E1/T1 mode.

Figure 4-2 IP-based GL co-transmission through FE ports interconnection in IP over E1/T1 mode

As shown in Figure 4-2, the transmission board UTRP of LTE provides an E1/T1 port (functioning as the common transmission port of GL) to connect to the transport network. GSM data and LTE data in the base station achieve IP over E1/T1 co-transmission through FE ports interconnection. The LTE UTRP uses MLPPP to bind E1 links and routes GSM data packets to the GTMU through the interconnected FE ports.

The base station controller shown in Figure 4-2 may be a BSC or an MBSC.

The UTRP has a limited bandwidth and does not facilitate GSM capacity expansion. Therefore, it is not recommended that the E1/T1 port of the UTRP function as the common transmission port of GL.

4.2 Route Backup Through FE Ports Interconnection

The GBTS and eNodeB can achieve route backup through FE ports interconnection. As shown in Figure 4-3, an active route passes through the transmission port of one RAT to the IP network, and a standby route passes through the transmission port of one RAT to that of another RAT through the interconnected FE ports and then to the IP network. In route backup mode, the BFD function is used to detect the link status. In normal situations, the GBTS and eNodeB connect to the IP network through the active routes. When the BFD function detects that the active route of the GBTS or eNodeB becomes unavailable, the data flow of GSM or LTE is switched to the standby route. After the active route is restored, the data flow is automatically switched back to the active route if the single-hop BFD mode is used; the data flow needs to be manually switched to the active route if the multi-hop BFD mode is used.

SingleRAN




4-3

Figure 4-3 Example of route backup for IP-based GL co-transmission (assuming that the LTE transmission route is first unavailable and then restored)

SingleRAN




4-4



In route backup mode, the GTMUb and LMPT use the same type of port (an optical port or an electrical port) to connect to the transport network or to perform FE ports interconnection.



SingleRAN

Common Transmission 5 UL Co-Transmission



5-1

5 UL Co-Transmission

5.1 IP-Based Co-Transmission Through FE Ports Interconnection

UL co-transmission on the base station side (corresponding to the feature MRFD-221501 IP-Based Multi-mode Co-Transmission on BS side(NodeB)) can be based on IP over Ethernet or IP over E1/T1. For IP-based UL co-transmission on BS side, it is recommended that the LTE provide the co-transmission port.

Figure 5-1 shows the IP-based UL co-transmission through FE ports interconnection in IP over Ethernet mode.

Figure 5-1 IP-based UL co-transmission through FE ports interconnection in IP over Ethernet mode

The base station controller shown in Figure 5-1 may be an RNC or an MBSC.

As shown in Figure 5-1, the main controlling board LMPT of LTE provides an FE/GE port (functioning as the common transmission port of UL) to connect to the transport network. UMTS data and LTE data in the base station achieve IP over Ethernet co-transmission through FE ports interconnection.




The LMPT board and the WMPT board use the FE electrical port to perform FE ports interconnection.

In this situation, the LMPT uses the FE/GE electrical port or SFP optical to connect to the transport network.

SingleRAN




5-2

Figure 5-2 shows the IP-based UL co-transmission through FE ports interconnection in IP over E1/T1 mode.

Figure 5-2 IP-based UL co-transmission through FE ports interconnection in IP over E1/T1 mode

As shown in Figure 5-2, the transmission board UTRP of LTE provides an E1/T1 port (functioning as the common transmission port of UL) to connect to the transport network. UMTS data and LTE data in the base station achieve IP over E1/T1 co-transmission through FE ports interconnection. The LTE UTRP uses MLPPP to bind E1 links and routes UMTS data packets to the WMPT through the interconnected FE ports.

The base station controller shown in Figure 5-2 may be an RNC or an MBSC.

The UTRP has a limited bandwidth and does not facilitate UMTS capacity expansion. Therefore, it is not recommended that the E1/T1 port of the UTRP function as the common transmission port of UL.

5.2 Route Backup Through FE Ports Interconnection

The NodeB and eNodeB can achieve route backup through FE ports interconnection. As shown in Figure 5-3, an active route passes through the transmission port of one RAT to the IP network, and a standby route passes through the transmission port of one RAT to that of another RAT through the interconnected FE ports and then to the IP network. In route backup mode, the BFD function is used to detect the link status. In normal situations, the NodeB and eNodeB connect to the IP network through the active routes. When the BFD function detects that the active route of the NodeB or eNodeB becomes unavailable, the data flow of UMTS or LTE is switched to the standby route. After the active route is restored, the data flow is automatically switched back to the active route if the single-hop BFD mode is used; the data flow needs to be manually switched to the active route if the multi-hop BFD mode is used.

SingleRAN




5-3

Figure 5-3 Example of route backup for IP-based UL co-transmission (assuming that the UMTS transmission route is first unavailable and then restored)

SingleRAN




5-4



In route backup mode, the WMPT and LMPT use the same type of port (an optical port or an electrical port) to connect to the transport network or to perform FE ports interconnection.



5.3 Hybrid Transmission Through FE Ports Interconnection

The NodeB and eNodeB can achieve hybrid transmission through FE ports interconnection. To achieve this goal, UMTS must provide an E1/T1 port to carry high-QoS services (for example, CS services) and LTE must provide an FE/GE port to carry low-QoS services (for example, PS services). Hybrid transmission is not applicable in a scenario where both UMTS and LTE provide an FE/GE port.

The hybrid transmission of NodeB and eNodeB is classified into the following types:

Hybrid transmission performed on the UMTS data flow but not on the LTE data flow

Hybrid transmission performed on the LTE data flow but not on the UMTS data flow

Hybrid transmission performed on both the UMTS data flow and the LTE data flow

Figure 5-4 shows an example where hybrid transmission is performed on the UMTS data flow but not on the LTE data flow.

Figure 5-4 Example of hybrid transmission for IP-based UL co-transmission (assuming that hybrid transmission is performed on the UMTS data flow but not on the LTE data flow)

Hybrid transmission and route backup cannot be used simultaneously.

SingleRAN

Common Transmission 6 Engineering Guidelines



6-1

6 Engineering Guidelines

This chapter provides engineering guidelines for configuring the co-transmission feature.

6.1 Configuration Guidelines for Co-Transmissoin on the Base Station Controller Side

For the configuration guidelines for GU co-transmission on the base station controller side, see the SingleRAN Reconfiguration Guide.

6.2 Configuration Guidelines for Co-Transmissoin on the Base Station Side

To achieve IP-based co-transmission through FE ports interconnection, IP addresses must be planned and proper forwarding routes must be configured. This section describes how to plan IP addresses and how to configure forwarding routes. For details about how to configure co-transmission on the base station side, see the SingleRAN Reconfiguration Guide.

6.2.1 Overview

The IP addresses of UMTS NodeB and LTE eNodeB are classified into the OM IP address, service IP address, and port IP address. The service IP address and the port IP address can be the same. For the GSM GBTS, the OM IP address and the service IP address must be the same, and the port IP address and the OM/service IP address may not be the same.

The port IP addresses for the base stations of different RATs can be planned on the same network segment or on different network segments, based on the network mask of the base station controller. This chapter describes the guidelines for configuring the port IP addresses for the base stations of different RATs are on different network segments.

As the port IP addresses for the base stations of one RAT cannot be the same, IP packets can be forwarded through routes or standard address route protocol (ARP) proxy if the port IP addresses for the base stations of two RATs on different network segments. The following sections take IP-based GU co-transmission as an example to describe how to configure IP addresses and routes. The configuration method for GL and UL is similar to that for GU and is not described in this document.

6.2.2 Configuring Routes to Forward IP Packets

This section describes how to configure routes to forward IP packets, as shown in Figure 6-1.

SingleRAN




6-2

Figure 6-1 Route forwarding mode (GU IP addresses on different network segments)

In the downlink

− Configure a route on the base station controller side: GBTS IP address -> NodeB IP address (10.1.2.0 -> 10.1.1.2)

− Configure a route on the NodeB WMPT: GBTS IP address -> Interconnection port IP address. Note that you need not configure this route if the OM/service IP address of the GBTS and the interconnection port IP address are on the same network segment.

In the uplink

− Configure a route on the GBTS GTMU: Base station controller IP address -> Interconnection port IP address (10.1.1.0 -> 10.1.2.1)

− Configure a route on the NodeB WMPT: Base station controller IP address -> NodeB port IP address. Note that you need not configure this route if the NodeB port IP address and the base station controller IP address are on the same network segment.

The route 10.1.2.0 -> 10.1.2.2, 10.1.2.0 -> 10.1.2.1, 10.1.1.0 -> 10.1.1.2, 10.1.1.0 -> 10.1.1.1 is automatically configured by the system.

6.2.3 Configuring Standard ARP Proxy and Routes to Forward IP Packets

This section describes how to configure standard ARP proxy and routes to forward IP packets, as shown in Figure 6-2.

SingleRAN




6-3

Figure 6-2 ARP proxy mode (GU IP addresses on different network segments)

In the downlink

Configure the standard ARP proxy on the NodeB WMPT, and configure a forwarding route for GBTS packets: GBTS IP address -> Interconnection port IP address. Note that you need not configure this route if the OM/service IP address of the GBTS and the interconnection port IP address are on the same network segment.

In the uplink

− Configure a route on the GBTS GTMU: Base station controller IP address -> Interconnection port IP address (10.1.1.0 -> 10.1.2.1)

− Configure a route on the NodeB WMPT: Base station controller IP address -> NodeB port IP address. Note that you need not configure this route if the NodeB port IP address and the base station controller IP address are on the same network segment.

The route 10.1.2.0 -> 10.1.2.2, 10.1.2.0 -> 10.1.2.1, 10.1.1.0 -> 10.1.1.2, 10.1.0.0 -> 10.1.1.1 is automatically configured by the system.

SingleRAN

Common Transmission 7 Parameters



7-1

7 Parameters

Table 7-1 Parameter description

Parameter ID NE MML Command Description

UDPPN BSC6900 ADD NSVLLOCAL(Mandatory)

Meaning:UDP port number of the local NSVL. When "Subnet Protocol Type" of NSE is "Gb over IP" and "Subnetwork Configure Mode" is "Static", the setting of this parameter must be consistent with the setting at the SGSN side

GUI Value Range:1214~2001, 2005~3783, 3786~4783, 4785~65000

Actual Value Range:1214~2001, 2005~3783, 3786~4783, 4785~65000

Default Value:None

../RNCParaHtml/mbsc/m-para/nsvllocal_udppn.html

../RNCParaHtml/mbsc/m-mml/add-nsvllocal.html

../RNCParaHtml/mbsc/m-mml/add-nsvllocal.html

SingleRAN

Common Transmission 8 Counters



8-1

8 Counters

There are no specific counters associated with this feature.

SingleRAN

Common Transmission 9 Glossary



9-1

9 Glossary

For the acronyms, abbreviations, terms, and definitions, see the Glossary.

Glossary.htm

SingleRAN

Common Transmission 10 Reference Documents



10-1

10 Reference Documents

[1]. Transmission Resource Management Feature Parameter Description

[2]. SingleRAN Reconfiguration Guide

[3]. IP BSS Feature Parameter Description of the GBSS

[4]. IP RAN Feature Parameter Description of the UMTS


IP%20RAN.htm

Common Transmission(RAN13.0 01)

Documents

Transcript of Common Transmission(RAN13.0 01)