2G 3G and LTE Co-transmission(eRAN7.0_01).pdf

eRAN

2G/3G and LTE Co-transmissionFeature Parameter Description

Issue 01

Date 2014-04-26

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2015. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior writtenconsent 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. NoticeThe purchased products, services and features are stipulated by the contract made between Huawei and thecustomer. All or part of the products, services and features described in this document may not be within thepurchase 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 representationsof any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but all statements, information, andrecommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Issue 01 (2014-04-26) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

i

http://www.huawei.com

mailto:[email protected]

Contents

1 About This Document..................................................................................................................11.1 Scope..............................................................................................................................................................................11.2 Intended Audience..........................................................................................................................................................11.3 Change History...............................................................................................................................................................11.4 Differences Between eNodeB Types..............................................................................................................................2

2 Overview.........................................................................................................................................32.1 Definition........................................................................................................................................................................32.2 Benefits...........................................................................................................................................................................32.3 Architecture....................................................................................................................................................................3

3 Feature Component.......................................................................................................................53.1 Overview........................................................................................................................................................................53.2 Co-transmission with a Convergence Device.................................................................................................................63.3 Co-transmission Without a Convergence Device...........................................................................................................7

4 Related Features...........................................................................................................................104.1 Features Related to LOFD-003002 2G/3G and LTE Co-transmission........................................................................10

5 Network Impact...........................................................................................................................115.1 LOFD-003002 2G/3G and LTE Co-transmission........................................................................................................11

6 Other Impacts...............................................................................................................................126.1 LOFD-003002 2G/3G and LTE Co-transmission........................................................................................................126.1.1 NEs............................................................................................................................................................................126.1.2 Hardware...................................................................................................................................................................126.1.3 Inter-NE Interfaces....................................................................................................................................................126.1.4 Operation and Maintenance.......................................................................................................................................12

7 Engineering Guidelines.............................................................................................................137.1 When to Use LOFD-003002 2G/3G and LTE Co-transmission..................................................................................147.2 Required Information...................................................................................................................................................147.3 Planning........................................................................................................................................................................147.4 Deployment..................................................................................................................................................................147.4.1 Process.......................................................................................................................................................................147.4.2 Requirements.............................................................................................................................................................14

eRAN2G/3G and LTE Co-transmission Feature ParameterDescription Contents


ii

7.4.3 Data Preparation........................................................................................................................................................157.4.4 Precautions.................................................................................................................................................................237.4.5 Hardware Adjustment................................................................................................................................................247.4.6 Initial Configuration..................................................................................................................................................247.4.7 Activation Observation..............................................................................................................................................287.4.8 Reconfiguration.........................................................................................................................................................287.4.9 Deactivation...............................................................................................................................................................287.5 Performance Monitoring...............................................................................................................................................287.6 Parameter Optimization................................................................................................................................................287.7 Troubleshooting............................................................................................................................................................28

8 Parameters.....................................................................................................................................29

9 Counters........................................................................................................................................30

10 Glossary.......................................................................................................................................31

11 Reference Documents...............................................................................................................32

eRAN2G/3G and LTE Co-transmission Feature ParameterDescription Contents


iii

1 About This Document

1.1 ScopeThis document describes the LOFD-003002 2G/3G and LTE Co-transmission feature includingimplementation principles, feature dependencies, network impact, and engineering guidelines.The eNodeB servers as a convergence node for the co-transmission.

This document applies to the following types of eNodeBs.

eNodeB Type Model

Macro 3900 series eNodeB

LampSite DBS3900

Any managed objects (MOs), parameters, alarms, or counters described herein correspond tothe software release delivered with this document. Any future updates will be described in theproduct documentation delivered with future software releases.

This document applies only to LTE FDD. Any "LTE" in this document refers to LTE FDD, and"eNodeB" refers to LTE FDD eNodeB.

1.2 Intended AudienceThis document is intended for personnel who:

l Need to understand the features described herein

l Work with Huawei products

1.3 Change HistoryThis section provides information about the changes in different document versions. There aretwo types of changes, which are defined as follows:

eRAN2G/3G and LTE Co-transmission Feature ParameterDescription 1 About This Document


1

l Feature changeChanges in features and parameters of a specified version as well as the affected entities.

l Editorial changeChanges in wording or addition of information and any related parameters affected byeditorial changes. Editorial change does not specify the affected entities.

eRAN7.0 01 (2014-04-26)This is the first official release.This issue does not include any changes.

eRAN7.0 Draft A (2014-01-20)This document is created for eRAN7.0.

1.4 Differences Between eNodeB TypesThe features described in this document are implemented in the same way on macro andLampSite eNodeBs.

eRAN2G/3G and LTE Co-transmission Feature ParameterDescription 1 About This Document


2

2 Overview

2.1 DefinitionWith the 2G/3G and LTE Co-transmission feature, an eNodeB not only provides LTE services,but also functions as a hub to provide routing and Dynamic Host Configuration Protocol (DHCP)Relay functions to lower-level cascaded base stations (including GBTSs, eGBTSs, and NodeBs)and to transmit data transparently to the base station controllers.

2.2 BenefitsThe 2G/3G and LTE Co-transmission feature allows sharing physical ports and transmissionbandwidth between radio access networks and simplifies configuration and maintenanceoperations for transmission. This reduces capital expenditure (CAPEX) and operationalexpenditure (OPEX).

2.3 ArchitectureTable 2-1 describes a typical scenario for the 2G/3G and LTE Co-transmission feature.

Table 2-1 Typical scenario for the 2G/3G and LTE Co-transmission feature

CascadedBaseTransceiverStation

Networking

GBTS l The LMPT/UMPT of an eNodeB provides FE/GE ports to connect tothe BSC, MME, and S-GW and provides FE ports to connect to theGTMU of a GBTS.

l The UMPT of an eNodeB provides IP-over-FE/GE ports to connect tothe BSC, MME, and S-GW and provides IP-over-E1/T1 ports toconnect to the GTMU of a GBTS.

eRAN2G/3G and LTE Co-transmission Feature ParameterDescription 2 Overview


3

CascadedBaseTransceiverStation

Networking

eGBTS l The LMPT/UMPT of an eNodeB provides FE/GE ports to connect tothe BSC, MME, and S-GW and provides FE/GE ports to connect to theUMPT of an eGBTS.

l The UMPT of an eNodeB provides FE/GE ports to connect to the BSC,MME, and S-GW and provides IP-over-E1/T1 ports to connect to theUMPT of an eGBTS.

NodeB l The LMPT/UMPT of an eNodeB provides FE/GE ports to connect tothe RNC, MME, and S-GW and provides FE ports to connect to theWMPT of a NodeB.

l The LMPT/UMPT of an eNodeB provides FE/GE ports to connect tothe RNC, MME, S-GW, and the UMPT of a NodeB.

l The UMPT of an eNodeB provides FE/GE ports to connect to the RNC,MME, and S-GW and IP-over-E1/T1 ports to connect to the UMPT/WMPT of a NodeB.

NOTE

A scenario where an eNodeB uses IP-over-E1/T1 ports to connect to the BSC, RNC, MME, and S-GW israrely used on live networks and is not, therefore, described in this document. Such a scenario is uncommonbecause:

l The MME and S-GW generally do not support IP-over-E1/T1 ports.

l The eNodeB itself rarely uses IP-over-E1/T1 ports for transmission due to the low bandwidth providedby the E1/T1 links.

For details about the cascading between an eNodeB and CDMA/WiMAX base stations, see the cascadingbetween an eNodeB and GSM/UMTS base stations in this document.

eRAN2G/3G and LTE Co-transmission Feature ParameterDescription 2 Overview


4

3 Feature Component

3.1 OverviewThis section describes the LOFD-003002 2G/3G and LTE Co-transmission feature.

NOTE

The difference between the LOFD-003002 2G/3G and LTE Co-transmission feature and theMRFD-231501 IP-Based Multi-mode Co-Transmission on BS side(eNodeB) feature is that the eNodeBcascaded with single-mode base stations implement the former, whereas a multi-mode base station usingpanel-based or backplane-based interconnection implement the latter. For details about the MRFD-231501IP-Based Multi-mode Co-Transmission on BS side (eNodeB) feature, see Common Transmission FeatureParameter Description for SingleRAN.

With this feature, you can deploy eNodeBs in areas where Huawei base stations of other radioaccess technologies (RATs), including GBTSs, eGBTSs, and NodeBs, have been deployed.Using FE/GE ports and IP-over-E1/T1 ports, the eNodeBs can be cascaded with and share thetransmission resources of these base stations.

Figure 3-1 shows the co-transmission networking supported by an eNodeB.

eRAN2G/3G and LTE Co-transmission Feature ParameterDescription 3 Feature Component


5

Figure 3-1 Co-transmission networking

In 2G/3G and LTE co-transmission, an eNodeB, functioning as a convergence node, providesthe DHCP Relay function to the lower-level cascaded base stations. The eNodeB configuresroutes for transit data flows, based on shared transmission resources, to forward the data flows.In addition, users can configure the bandwidths of the specified resource groups to ensure thetransmission fairness between local data flows and transit data flows.

There are two scenarios for 2G/3G and LTE co-transmission:

l Co-transmission with a convergence devicel Co-transmission without a convergence device

3.2 Co-transmission with a Convergence DeviceIf a convergence device is used, data flows (for services, signaling, and O&M) of a GSM/UMTSbase station and an eNodeB converge at the device and are then transmitted over the IP network.Figure 3-2 shows co-transmission with a convergence device.



6

Figure 3-2 Co-transmission with a convergence device

In this scenario, the convergence device provides the data convergence function. This does notaffect eNodeB operations; however, it does increase the OPEX and management workloadbecause an NE must be deployed.

NOTE

In this scenario, a router is generally used as the convergence device. The detailed functions of a router arenot described in this document.

3.3 Co-transmission Without a Convergence DeviceIf a convergence device is not used, GSM/UMTS base stations use IP-over-E1/T1 or IP-over-FE/GE ports to connect to an eNodeB. Data flows (for services, signaling, and O&M) from theGSM/UMTS base stations and those from the eNodeB converge at the eNodeB and are thentransmitted over the IP network. Figure 3-3 shows co-transmission without a convergencedevice.



7

Figure 3-3 Co-transmission without a convergence device

The eNodeB implements co-transmission based on multiple ports, IP routing, DHCP Relay andweighted round robin (WRR) scheduling.

Multiple PortsTo achieve co-transmission, the eNodeB must provide at least two E1/T1 or FE/GE physicalports. One port connects to a base station of another RAT and the other connects to the bearernetwork for IP transmission.

IP RoutingThe eNodeB, functioning as a convergence node, uses IP routing to forward uplink and downlinkdata flows of the lower-level cascaded base stations. By doing this, the eNodeB implements co-transmission in IP networking mode.

The eNodeB considers data flows of cascaded base stations as transit data flows and performsdifferentiated service scheduling based on the value of the Differentiated Services Code Point(DSCP). The eNodeB cannot identify the service types of transit data flows. The eNodeBfunctions as a router to forward the transit data flows based on their destination IP addresses.

DHCP RelayGenerally, a base station uses DHCP to obtain the IP address of packets, requiring that the DHCPclient (the base station) and DHCP server to be in the same broadcast domain.

In co-transmission mode, however, the cascaded GSM/UMTS base stations are not in the samebroadcast domain as the DHCP server. This requires that the eNodeB perform the DHCP Relayfunction to complete the layer-3 DHCP process for all cascaded base stations. The eNodeBconverts DHCP broadcast messages from the cascaded GSM/UMTS base stations into unicast



8

messages and then sends them to the DHCP server. After receiving a response from the DHCPserver, the eNodeB forwards the response to the GSM/UMTS base stations through the originalport.

The eNodeB configures the DHCP Relay function based on the parameters specified in theconfiguration file. If it must configure the DHCP function, the eNodeB obtains information aboutthe DHCP server. The DHCP Relay function can also be manually enabled and applies to allports on the eNodeB. Up to four DHCP servers can be configured for an eNodeB.

WRR SchedulingTo prevent GSM/UMTS transit data flows from affecting eNodeB data flows, the eNodeB usesdedicated transmission resource groups for the transit data flows. The eNodeB data flowsconsume resources in other groups. The WRR scheduling function helps to control the data flowsbetween the transmission resource groups to ensure scheduling fairness.

To perform scheduling for queues in a transmission resource group, the LMPT/UMPT usespriority queue (PQ) or WRR scheduling (non-PQ) so that each queue has a chance to bescheduled. Each queue is assigned a weighted value based on the bandwidth of each transmissionresource group. The weighted value specifies how much group bandwidth each queue can usefor transmission. This ensures the fairness between transmission resource groups, whilemaintaining the differentiation.



9

4 Related Features

4.1 Features Related to LOFD-003002 2G/3G and LTE Co-transmission

This section describes the dependency of the LOFD-0030002 2G/3G and LTE Co-transmissionfeature on other features.

Prerequisite FeaturesNone

Mutually Exclusive FeaturesNone

Impacted FeaturesNone

eRAN2G/3G and LTE Co-transmission Feature ParameterDescription 4 Related Features


10

5 Network Impact

5.1 LOFD-003002 2G/3G and LTE Co-transmissionThis section describes the network impact of the LOFD-003002 2G/3G and LTE Co-transmission feature.

System CapacityAfter you enable this feature, the eNodeB forwards the data flows of cascaded base stations. Theuplink and downlink traffic of the cascaded base stations occupies the transmission bandwidthand affects the forwarding performance of the eNodeB.

Network PerformanceAfter you enable this feature, services of the cascaded base stations will fail if the eNodeB isfaulty, being upgraded, or experiences transmission interruption.

eRAN2G/3G and LTE Co-transmission Feature ParameterDescription 5 Network Impact


11

6 Other Impacts

6.1 LOFD-003002 2G/3G and LTE Co-transmission

6.1.1 NEsNo impact.

6.1.2 HardwareNo impact.

6.1.3 Inter-NE InterfacesNo impact.

6.1.4 Operation and Maintenance

License

N/A

Configuration Management

N/A

Performance Management

N/A

Fault management

N/A

eRAN2G/3G and LTE Co-transmission Feature ParameterDescription 6 Other Impacts


12

7 Engineering Guidelines

This chapter describes the engineering guidelines for 2G/3G and LTE Co-transmissiondeployment, including when to use the feature, requirements, deployment process, datapreparation, and initial configuration.

eRAN2G/3G and LTE Co-transmission Feature ParameterDescription 7 Engineering Guidelines


13

7.1 When to Use LOFD-003002 2G/3G and LTE Co-transmission

Co-transmission mainly involves the DHCP Relay function, routing and address planning forIP addresses of cascaded nodes, and transmission bandwidth planning for the eNodeB. IP-over-FE/GE transmission is recommended for 2G/3G and LTE co-transmission because, due to thelow bandwidth provided by the E1/T1 links, the eNodeB rarely uses IP-over E1/T1 transmission.This document provides engineering guidelines only for IP-over-FE/GE scenarios.

For information about the cascaded base station types and networking modes for 2G/3G andLTE co-transmission, see Table 2-1.

7.2 Required InformationUsers can deploy the 2G/3G and LTE Co-transmission feature when the common transmissionparameters have been configured. For details about the configurations of common transmissionparameters, see IP Transmission Feature Parameter Description.

7.3 Planning

RF PlanningN/A

Network PlanningN/A

Hardware PlanningN/A

7.4 Deployment

7.4.1 ProcessYou must configure the common transmission parameters before enabling the 2G/3G and LTECo-transmission feature. For details about how to configure these parameters, see IPTransmission Feature Parameter Description.

7.4.2 Requirements

Operating EnvironmentNone



14

Transmission NetworkingNone

LicenseThis feature requires the purchase and activation of a license. Table 7-1 lists the licenseinformation.

Table 7-1 License information for 2G/3G and LTE Co-transmission

Feature ID Feature Name LicenseControl Item

NE Sales Unit

LOFD-003002 2G/3G and LTECo-transmission

2G/3G and LTECo-transmission(FDD)

eNodeB per eNodeB

7.4.3 Data PreparationThis section describes the data that you need to collect for setting parameters. Required data isdata that you must collect for all scenarios. Collect scenario-specific data when necessary for aspecific feature deployment scenario.

There are three types of data sources:

l Network plan (negotiation required): parameter values planned by the operator andnegotiated with the EPC or peer transmission equipment

l Network plan (negotiation not required): parameter values planned and set by the operatorl User-defined: parameter values set by users

Prepare the following data before the deployment:

l The ETHPORT MO, which specifies the attribute of the Ethernet port for cascading onthe eNodeB. The key parameters in this MO are described in the following table.

Parameter Name

Parameter ID

Data Source Setting Notes

SubboardType

ETHPORT.SBT

Network plan(negotiation notrequired)

This parameter specifies the type of thesub-board on the board where theEthernet port is located.Set this parameter to BASE_BOARD(Base Board).



15

Parameter Name

Parameter ID


PortAttribute

ETHPORT.PA


This parameter specifies whether anEthernet port is an electrical port oroptical port.The port attribute of the physical portmust be consistent with that of the peerport. You are advised to set this parameterto AUTO(Automatic Detection).You can also set this parameter based onthe attribute of the physical port.NOTE

When the parameter is set to AUTO(Automatic Detection), it takes about 1minute to activate the port. If the electrical/optical attribute of peer port is modified, runthe RST ETHPORT command to reset thepeer port or the local Ethernet port.

MaximumTransmission Unit

ETHPORT.MTU

Network plan(negotiationrequired)

This parameter specifies the maximum IPpacket size (including the IP header) at theEthernet port.Set this parameter according to thetransport network plan.

Speed ETHPORT.SPEED


This parameter specifies the speed modeof the Ethernet port. This parameter mustbe set to the same value as that of the peerport.

Duplex ETHPORT.DUPLEX


This parameter specifies the duplex modeof the Ethernet port. This parameter mustbe set to the same value as that of the peerport.

l The DEVIP MO, which specifies the IP address of the port for cascading on the eNodeB.

The key parameters in this MO are described in the following table.

Parameter Name

Parameter ID


SubboardType

DEVIP.SBT


This parameter specifies the type of thesub-board on the board where a port islocated.Set this parameter to BASE_BOARD(Base Board).



16

Parameter Name

Parameter ID


IP Address DEVIP.IP Network plan(negotiation notrequired)

This parameter specifies the IP addressconfigured for a port. The IP address mustbe in the same network segment as thoseof the lower-level cascaded base stations.

Mask DEVIP.MASK


This parameter specifies the subnet maskof the device IP address configured on aport.The device IP address must be in the samenetwork segment as the port IP addressesof the cascaded base stations.

Port Type DEVIP.PT


This parameter specifies the type of thephysical port.l If the eNodeB uses the E1/T1 port to

connect to the transport network, setthis parameter to PPP(PPP Link) orMPGRP(Multi-link PPP Group).

l If the eNodeB uses the Ethernet portto connect to the transport network, setthis parameter to ETH(EthernetPort) or ETHTRK(EthernetTrunk).

l In cascading scenarios, set thisparameter to the IP address of thephysical port.

l The IPRT MO, which specifies a route from the co-transmission port on the eNodeB to

the port of a lower-level cascaded base station. If the cascaded base station is a GBTS or aNodeB, routes to the BSC or to the RNC and M2000 must be set, respectively. The keyparameters in this MO are described in the following table.

Parameter Name

Parameter ID


RouteIndex

IPRT.RTIDX


This parameter specifies the route indexof an IP route.

Destination IP

IPRT.DSTIP


l You are advised not to set both ofthese parameters to 0.0.0.0.

l In cascading scenarios, a route to theRNC or BSC must be set. Thedestination IP address is the service IPaddress of the RNC or BSC.



17

Parameter Name

Parameter ID


Mask IPRT.DSTMASK


l In cascading scenarios, a route to thelogical IP address of the cascaded basestation must be set. The destination IPaddress is the logical IP address of thecascaded base station.

SubboardType

IPRT.SBT Network plan(negotiation notrequired)

This parameter specifies the type of sub-board on the board where the IP route isestablished.Set this parameter to BASE_BOARD(Base Board).

RouteType

IPRT.RTTYPE


This parameter specifies the type of route.l If the eNodeB uses the Ethernet port

to connect to the transport network, setthis parameter to NEXTHOP(NextHop).

l If the eNodeB uses the E1 port toconnect to the transport network, setthis parameter to IF(Exit Interface).

Port Type IPRT.IFT Network plan(negotiation notrequired)

This parameter specifies the type of aport.If the eNodeB uses the E1 port to connectto the transport network, set thisparameter to PPP(PPP Link) orMPGRP(Multi-link PPP Group).

Next HopIP

IPRT.NEXTHOP


This parameter specifies the IP address ofthe next hop.l This parameter is valid only when the

IPRT.RTTYPE parameter is set toNEXTHOP(Next Hop).

l Set this parameter to the IP address ofthe gateway on the transport networkto which the eNodeB is connected.



18

Parameter Name

Parameter ID


Priority IPRT.PREF


This parameter specifies the priority ofthe route.If a backup IP route is required, thisparameter is required to specify thepriorities of the active and backup routes.The route with a higher priority is selectedas the active route. A smaller valueindicates a higher priority.The eNodeB does not support route-levelload balancing. Therefore, routes to thesame destination network segment musthave different priorities.

l (Optional) The DHCPRELAYSWITCH MO, which specifies whether to turn on the

DHCP Relay switch on the eNodeB. This switch is turned on only when plug-and-play(PnP) is used to deploy the base stations cascaded to the eNodeB. The key parameter inthis MO is described in the following table.

Parameter Name

Parameter ID


DHCPRelaySwitch

DHCPRELAYSWITCH.ES

Transportplanning(internalplanning)

This parameter specifies whether to turnon the DHCP Relay switch.Set this parameter to ENABLE(Enable).

l (Optional) The DHCPSVRIP MO, which specifies the IP address of the DHCP server for

the cascaded base stations. The key parameter in this MO is described in the followingtable.

ParameterName

Parameter ID


DHCPServer IPAddress

DHCPSVRIP.DHCPSVRIP

Transportplanning(internalplanning)

This parameter specifies the IP address ofthe DHCP server.l If the cascaded base station is a

NodeB, set this parameter to the IPaddress of the M2000 or RNC.

l If the cascaded base station is a GBTS,set this parameter to the IP address ofthe BSC.

l (Optional) The RSCGRP MO, which specifies dedicated transmission resource groups for

services of the cascaded base stations. The eNodeB data flows use different transmissionresource groups with data flows of the cascaded base stations. The key parameters in thisMO are described in the following table.



19

Parameter Name

Parameter ID


TransmissionResourceGroup ID

RSCGRP.RSCGRPID


Set this parameter based on the networkplan.You are advised to set differenttransmission resource groups for dataflows of the cascaded base stations andthe eNodeB.Add transmission resource group ID onlyif you need to measure the performancecounters.

SubboardType

RSCGRP.SBT


This parameter specifies the type of sub-board on the board where the IP route isestablished.Set this parameter to BASE_BOARD(Base Board).

BearingPort Type

RSCGRP.PT


This parameter specifies the type of a portwhere a transmission resource group iscarried.Set this parameter according to the typeof the physical port connecting the MMEand S-GW.

TxBandwidth

RSCGRP.TXBW


This parameter specifies the uplinktransport admission bandwidth for atransmission resource group that carrieseNodeB data flows and TX trafficshaping bandwidth. This parameter isused in single-rate mode. Set thisparameter based on the network plan.

RxBandwidth

RSCGRP.RXBW


This parameter specifies the downlinktransport admission bandwidth for atransmission resource group that carrieseNodeB data flows and has no impact ontransit data flows. This parameter is usedin single-rate mode. Set this parameterbased on the network plan.

TxCommittedBurst Size

RSCGRP.TXCBS


This parameter specifies the TXcommitted burst size of a transmissionresource group.Set this parameter based on the networkplan. The value of RSCGRP.TXCBSmust be greater than or equal to that ofRSCGRP.TXBW for traffic shaping ofthe transmission resource group.



20

Parameter Name

Parameter ID


TXExcessiveBurst Size

RSCGRP.TXEBS


This parameter specifies the TXexcessive burst size of a transmissionresource group.Set this parameter based on the networkplan. You are advised to set thisparameter to two times that of the TXBandwidth value.

SchedulingWeight

RSCGRP.WEIGHT


This parameter specifies the schedulingweight of a transmission resource group.This parameter is used in calculating thebandwidth scheduled to a resource group,which helps achieve the user admissioncontrol.Set this parameter based on the networkplan in case of physical bandwidthrestriction. You are advised to retain thedefault value.

TXCommittedInformation Rate

RSCGRP.TXCIR


This parameter specifies the transmitcommitted information rate (CIR) of thetransmission resource group, which is aguarantee rate assigned by the operator.Set this parameter based on the networkplan. This parameter is used in double-rate mode. The parameter value is used asthe uplink transport admission bandwidthfor a transmission resource group thatcarries eNodeB data flows and TX trafficshaping bandwidth for eNodeB or transitdata flows.

RXCommittedInformation Rate

RSCGRP.RXCIR


This parameter specifies the receive CIRof the transmission resource group, whichis a guarantee rate assigned by theoperator. This parameter value is used asthe downlink transport admissionbandwidth for services that do not needflow control.Set this parameter based on the networkplan. This parameter is used in double-rate mode. The parameter value is used asthe downlink transport admissionbandwidth for a transmission resourcegroup that carries eNodeB data flows.



21

Parameter Name

Parameter ID


TX PeakInformation Rate

RSCGRP.TXPIR


This parameter specifies the peakinformation rate (PIR) of thetransmission resource group.Set this parameter based on the networkplan. This parameter is used in double-rate mode. The parameter value is used asthe uplink transport admission bandwidthfor a transmission resource group thatcarries eNodeB data flows and TX trafficshaping bandwidth for eNodeB or transitdata flows.

RX PeakInformation Rate

RSCGRP.RXPIR


This parameter specifies the receive PIRof the transmission resource group. Thisparameter value is used as the downlinktransport admission bandwidth for atransmission resource group.This parameter is used in double-ratemode. Set this parameter based on thenetwork plan.

TX PeakBurst Size

RSCGRP.TXPBS


This parameter specifies the size of thepeak burst transmitted from thetransmission resource group.Set this parameter based on the networkplan. The value of RSCGRP.TXPBSmust be greater than or equal to that ofRSCGRP.TXCBS. TheRSCGRP.TXPBS must be greater thanor equal to that of RSCGRP.TXPIR.

l (Optional) The IP2RSCGRP MO, which specifies a dedicated transmission resource group

for services of the cascaded base stations. This document does not describe how to specifya transmission resource group for local data flows. For detailed operations, see TransportResource Management Feature Parameter Description. The key parameters in this MOare described in the following table.

Parameter Name

Parameter ID


MappingIndex

IP2RSCGRP.MAPIDX

Network plan(negotiationnot required)

This parameter specifies the mappingbetween an IP address and thetransmission resource group. Thisparameter is used to specify the mappingtransmission resource group for transitdata flows.



22

Parameter Name

Parameter ID


TransmissionResourceGroup BearType

IP2RSCGRP.BEAR


This parameter specifies the bearer typeof a transmission resource group. Set thisparameter to IP(IP).

BearingPort Type

IP2RSCGRP.PT


This parameter specifies the type of a portwhere a transmission resource group iscarried. This parameter is used to specifythe type of an eNodeB port, throughwhich transit data flows are transmitted.

BearingPort No.

IP2RSCGRP.PN


This parameter specifies the number of aport where a transmission resource groupis carried. This parameter is used tospecify the number of an eNodeB port,through which transit data flows aretransmitted.

TransmissionResourceGroup ID

IP2RSCGRP.RSCGRPID


This parameter specifies the ID of atransmission resource group. Thisparameter is used to specify the ID of atransmission resource group for transitdata flows that are transmitted throughthe eNodeB.

Destination IP

IP2RSCGRP.DSTIP


This parameter specifies the destinationIP address of the data flow that is boundto a transmission resource group. Thisparameter is used to specify a destinationIP address for transit data flows.

Mask IP2RSCGRP.DSTMASK


This parameter specifies the subnet maskof the destination IP address of the dataflow that is bound to a transmissionresource group. This parameter is used tospecify a subnet mask of the destinationIP address for transit data flows.

7.4.4 PrecautionsIf a lower-level base station is a NodeB,l The destination IP address of the DHCP Relay route to the NodeB is the IP address of an

eNodeB port. If the eNodeB has multiple port IP addresses, the routes to all the ports mustbe set. You can set the destination IP address on the M2000.

l The next hop of the route from the NodeB to the RNC is the IP address of the eNodeB portconnected to the NodeB.

If a lower-level base station is a GBTS/eGBTS,



23

l The next hop of the route from the GBTS/eGBTS to the BSC is the IP address of the eNodeBport connected to the GBTS/eGBTS.

l The destination IP address of the DHCP Relay route to the GBTS is the IP address of aneNodeB port. If the eNodeB has multiple port IP addresses, the routes to all the ports mustbe set. You can set the destination IP address on the BSC.

l The destination IP address of the DHCP Relay route to the eGBTS is the IP address of aneNodeB port. If the eNodeB has multiple port IP addresses, the routes to all the ports mustbe set. You can set the destination IP address on the M2000.

7.4.5 Hardware AdjustmentN/A

7.4.6 Initial Configuration

Using the CME to Perform Batch Configuration for Newly Deployed eNodeBsEnter the values of the parameters listed in Table 7-2 in a summary data file, which also containsother data for the new eNodeBs to be deployed. Then, import the summary data file into theCME for batch configuration. For detailed instructions, see section "Creating eNodeBs inBatches" in the initial configuration guide for the eNodeB.

The summary data file may be a scenario-specific file provided by the CME or a customizedfile, depending on the following conditions:

l The MOs in Table 7-2 are contained in a scenario-specific summary data file. In thissituation, set the parameters in the MOs, and then verify and save the file.

l Some MOs in Table 7-2 are not contained in a scenario-specific summary data file. In thissituation, customize a summary data file to include the MOs before you can set theparameters.

l The template Basic Scenario: using for the scenario of vlan and without security, etc isused in non-security scenarios.

l The template Security Scenario: using for the Scenario of ACL, Pre-Shared key or RSADigital Certificate Signature, etc is used in security scenarios.

Table 7-2 Parameters related to 2G/3G and LTE Co-transmission

MO Sheet in theSummaryData File

MO Name Parameter Group Remarks

ETHPORT

Base StationTransportData

EthportAttribute

PortNo1, PortAttr1 -



24

MO Sheet in theSummaryData File

MO Name Parameter Group Remarks

DEVIP DevIPPattern DevIPPattern

CabinetNo,SubrackNo, SlotNo,SubboardType,PortType, PortNo, IP,Mask, Description

This sheetreferences the IPaddress informationabout S1 interface,X2 interface, OM, orclock channels in theBase StationTransport Datasheet.

IPRT IPRoutePattern

IPRoute CabinetNo,SubrackNo, SlotNo,SubboardType,PortType, PortNo,RouteType, DstIP,Mask, NextHopIP,RoutePriority,*Description Info

This sheetreferences theDestination IP1,DestinationMask1, and NextHop IP Address1 ofthe eNodeBparameter group inthe Base StationTransport Datasheet.

DHCPRELAYSWITCH

Common Data DHCPRELAYSWITCH

DHCP Relay Switch -

DHCPSVRIP

Common Data DHCPSVRIP

DHCP Server IPAddress

-

Using the CME to Perform Batch Configuration for Existing eNodeBsBatch reconfiguration using the CME is the recommended method to activate a feature onexisting eNodeBs. This method reconfigures all data, except neighbor relationships, for multipleeNodeBs in a single procedure. The procedure is as follows:

Step 1 After creating a planned data area, choose CME > Advanced > Customize Summary Data File(U2000 client mode), or choose Advanced > Customize Summary Data File (CME client mode),to customize a summary data file for batch reconfiguration.

NOTE

For context-sensitive help on a current task in the client, press F1.

Step 2 Choose CME > LTE Application > Export Data > Export Base Station Bulk ConfigurationData (U2000 client mode), or choose LTE Application > Export Data > Export Base StationBulk Configuration Data (CME client mode), to export the eNodeB data stored on the CME intothe customized summary data file.



25

Step 3 In the summary data file, set the parameters in the MOs listed in Table 7-2 and close the file.

Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk ConfigurationData (U2000 client mode), or choose LTE Application > Import Data > Import Base StationBulk Configuration Data (CME client mode), to import the summary data file into the CME,and then start the data verification.

Step 5 After data verification is complete, choose CME > Planned Area > Export Incremental Scripts(U2000 client mode), or choose Area Management > Planned Area > Export IncrementalScripts (CME client mode), to export and activate the incremental scripts.

----End

Using the CME to Perform Single Configuration

On the CME, set the parameters listed in the "Data Preparation" section for a single eNodeB.The procedure is as follows:

Step 1 In the planned data area, click Base Station in the upper left corner of the configuration window.

Step 2 In area 1 shown in Figure 7-1, select the eNodeB to which the MOs belong.

Figure 7-1 MO search and configuration window

Step 3 On the Search tab page in area 2, enter an MO name, for example, CELL.

Step 4 In area 3, double-click the MO in the Object Name column. All the parameters in this MO aredisplayed in area 4.

Step 5 Set the parameters in area 4 or 5.



26

Step 6 Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or chooseArea Management > Planned Area > Export Incremental Scripts (CME client mode), to exportand activate the incremental scripts.

----End

Using MML Commands

Perform the following steps on the eNodeB:

Step 1 Run the SET ETHPORT command to set the attribute of the Ethernet port cascaded to theeNodeB.

Step 2 Run the ADD DEVIP command to set the device IP address of the Ethernet port cascaded tothe eNodeB. The IP addresses of the interconnected ports must be in the same network segment.

Step 3 Run the ADD IPRT command to add the routes from the eNodeB to the peer devices of thelower-level cascaded base stations.

l If the cascaded base station is a GBTS/eGBTS, the peer device is the BSC.

l If the cascaded base station is a NodeB, the peer devices are the RNC and M2000.

Step 4 (Optional) Run the SET DHCPRELAYSWITCH command to turn on the DHCP Relay switch.

Step 5 (Optional) Run the ADD DHCPSVRIP command to set the IP address of the DHCP server forthe cascaded base stations.

l If the cascaded base station is a GBTS/eGBTS, the DHCP server is the BSC.

l If the cascaded base station is a NodeB, the DHCP server is the RNC or M2000.

----End

MML Command Examples

To set the attribute of the Ethernet port cascaded to the eNodeB, run the following command:

SET ETHPORT: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PN=1, PA=FIBER, MTU=1500, SPEED=1000M, DUPLEX=FULL, ARPPROXY=ENABLE, FC=OPEN, FERAT=10, FERDT=10;

To set the device IP address of the Ethernet port cascaded to the eNodeB, run the followingcommand:

ADD DEVIP: SN=7, SBT=BASE_BOARD, PT=ETH, PN=1, IP="10.2.2.2", MASK="255.255.255.0";

To add the route from the eNodeB to the peer device of the lower-level cascaded base station(GBTS in this example), run the following command:

ADD IPRT: SN=7, SBT=BASE_BOARD, DSTIP="100.3.3.3", DSTMASK="255.255.255.0", RTTYPE=NEXTHOP, NEXTHOP="10.1.1.2", PREF=60;

To turn on the DHCP Relay switch on the eNodeB, run the following command:

SET DHCPRELAYSWITCH: ES=ENABLE;

To set the IP address of the DHCP server for the GBTS, run the following command:

ADD DHCPSVRIP: DHCPSVRIP="100.3.3.3";



27

7.4.7 Activation ObservationPerform the following steps on the eNodeB to check whether the transmission links from theeNodeB to the MME and S-GW are normal:

Step 1 Ping the IP addresses of the MME and S-GW on the eNodeB. If the ping operations succeed,the transmission links are normal.

Step 2 Ping the IP address of the NodeB on the RNC and the IP addresses of the GBTS and eGBTS onthe BSC. If the ping operations succeed, the feature has been enabled.

----End

7.4.8 ReconfigurationNone

7.4.9 DeactivationNone

7.5 Performance MonitoringNone

7.6 Parameter OptimizationN/A

7.7 TroubleshootingFor details about IP transmission fault location and troubleshooting, see eRAN TroubleshootingGuide.



28

8 Parameters

eRAN2G/3G and LTE Co-transmission Feature ParameterDescription 8 Parameters


29

9 Counters

eRAN2G/3G and LTE Co-transmission Feature ParameterDescription 9 Counters


30

10 Glossary

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

eRAN2G/3G and LTE Co-transmission Feature ParameterDescription 10 Glossary


31

11 Reference Documents

1. IP Transmission Feature Parameter Description2. Transport Resource Management Feature Parameter Description3. Common Transmission Feature Parameter Description

eRAN2G/3G and LTE Co-transmission Feature ParameterDescription 11 Reference Documents


32

Date post:	04-Dec-2015
Category:	Documents
Upload:	samuraial
View:	22 times
Download:	4 times