IP Transmission Efficiency Improvement (SingleRAN - 01)

SingleRAN
IP Transmission Efficiency
Improvement Feature Parameter
Description
Issue 01
Date 2016-09-30
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2017. 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 a 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: support@huawei.com
Issue 01 (2016-09-30) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
SingleRAN
IP Transmission Efficiency Improvement Feature Parameter
Description Contents
Contents
1 About This Document.................................................................................................................. 1

1.1 Scope.............................................................................................................................................................................. 1
1.2 Intended Audience.......................................................................................................................................................... 1
1.3 Change History............................................................................................................................................................... 2
1.4 Differences Between Base Station Types....................................................................................................................... 2
2 Overview......................................................................................................................................... 4
3 Multiplexing................................................................................................................................... 5
3.1 Overview........................................................................................................................................................................ 5
3.2 Frame Protocol Multiplexing (for UMTS Only)............................................................................................................ 5
3.2.1 Introduction................................................................................................................................................................. 5
3.2.2 Technical Description.................................................................................................................................................. 6
3.2.2.1 Packet Format........................................................................................................................................................... 6
3.2.2.2 Principles.................................................................................................................................................................. 7
3.3 UDP Multiplexing (for GSM and UMTS Only)............................................................................................................ 8
3.3.1 Introduction................................................................................................................................................................. 8
3.3.2 Technical Description.................................................................................................................................................. 8
3.3.2.1 Packet Format........................................................................................................................................................... 8
3.3.2.2 Principles................................................................................................................................................................ 11
3.4 Abis Multiplexing and Ater Multiplexing (for GSM Only)......................................................................................... 11
3.4.1 Introduction................................................................................................................................................................11
3.4.2 Technical Description................................................................................................................................................ 12
3.5 PPP MUX..................................................................................................................................................................... 13
3.5.1 Introduction............................................................................................................................................................... 13
4 Header Compression...................................................................................................................16
4.1 Overview...................................................................................................................................................................... 16
4.2 IPHC............................................................................................................................................................................. 16
4.2.1 Introduction............................................................................................................................................................... 16
4.3 PPPHC.......................................................................................................................................................................... 19
4.3.1 Introduction............................................................................................................................................................... 19
Issue 01 (2016-09-30) Huawei Proprietary and Confidential ii

SingleRAN
4.3.2.1 PPP Frame Format..................................................................................................................................................19

4.3.2.2 ACFC......................................................................................................................................................................21
4.3.2.3 PFC......................................................................................................................................................................... 21
5 MLPPP/MC-PPP...........................................................................................................................22
5.1 Overview...................................................................................................................................................................... 22
5.2 Technical Description................................................................................................................................................... 22
5.2.1 MLPPP.......................................................................................................................................................................23
5.2.2 MC-PPP..................................................................................................................................................................... 24
6 Related Features...........................................................................................................................25
6.1 LBFD-00300401/TDLBFD-00300401 IP Header Compression................................................................................. 25
6.2 LBFD-003004 Compression & Multiplexing over E1/T1........................................................................................... 25
6.3 TDLBFD-003004 Compression & Multiplexing over E1/T1...................................................................................... 26
6.4 LBFD-00300402/TDLBFD-00300402 PPP MUX.......................................................................................................26
6.5 LBFD-00300403/TDLBFD-00300403 ML-PPP/MC-PPP.......................................................................................... 26
6.6 GBFD-118604 Abis MUX............................................................................................................................................27
6.7 GBFD-118612 Abis IPHC............................................................................................................................................27
6.8 GBFD-118610 UDP MUX for A Transmission........................................................................................................... 28
6.9 WRFD-050420 FP MUX for IP Transmission............................................................................................................. 28
6.10 WRFD-050412 UDP MUX for Iu-CS Transmission................................................................................................. 29
7 Network Impact........................................................................................................................... 30
7.1 LBFD-00300401/TDLBFD-00300401 IP Header Compression................................................................................. 30
7.2 LBFD-003004 Compression & Multiplexing over E1/T1/TDLBFD-003004 Compression & Multiplexing over
E1/T1.................................................................................................................................................................................. 30
7.3 LBFD-00300402/TDLBFD-003004 PPP MUX...........................................................................................................30
7.4 LBFD-00300403/TDLBFD-003004 ML-PPP/MC-PPP.............................................................................................. 31
7.5 GBFD-118604 Abis MUX............................................................................................................................................31
7.6 GBFD-118612 Abis IPHC............................................................................................................................................32
7.7 GBFD-118610 UDP MUX for A Transmission........................................................................................................... 32
7.8 WRFD-050420 FP MUX for IP Transmission............................................................................................................. 33
7.9 WRFD-050412 UDP MUX for Iu-CS Transmission................................................................................................... 34
8 Engineering Guidelines............................................................................................................. 35
8.1 FP MUX (for UMTS Only).......................................................................................................................................... 35
8.1.1 When to Use.............................................................................................................................................................. 35
8.1.2 Required Information................................................................................................................................................ 35
8.1.3 Planning..................................................................................................................................................................... 35
8.1.3.1 RF Planning............................................................................................................................................................ 35
8.1.3.2 Network Planning................................................................................................................................................... 35
8.1.3.3 Hardware Planning................................................................................................................................................. 35
8.1.4 Deployment............................................................................................................................................................... 36
8.1.4.1 Requirements.......................................................................................................................................................... 36
8.1.4.2 Data Preparation..................................................................................................................................................... 36
Issue 01 (2016-09-30) Huawei Proprietary and Confidential iii

SingleRAN
8.1.4.3 Activation............................................................................................................................................................... 37
8.1.4.3.1 Using MML Commands...................................................................................................................................... 37
8.1.4.3.2 MML Command Examples................................................................................................................................. 37
8.1.4.3.3 Using the CME.................................................................................................................................................... 37
8.1.4.4 Activation Observation...........................................................................................................................................38
8.1.4.5 Deactivation............................................................................................................................................................38
8.1.4.5.3 Using the CME.................................................................................................................................................... 38
8.1.5 Performance Monitoring............................................................................................................................................39
8.1.6 Parameter Optimization............................................................................................................................................. 39
8.1.7 Possible Issues........................................................................................................................................................... 39
8.2 UDP MUX (for GSM and UMTS Only)...................................................................................................................... 39
8.2.1 When to Use.............................................................................................................................................................. 40
8.2.3 Planning..................................................................................................................................................................... 40
8.2.3.1 RF Planning............................................................................................................................................................ 40
8.2.4 Deployment............................................................................................................................................................... 41
8.2.4.1 Requirements.......................................................................................................................................................... 41
8.2.4.3 Activation............................................................................................................................................................... 41
8.2.4.3.3 Using the CME.................................................................................................................................................... 42
8.2.4.5 Deactivation............................................................................................................................................................42
8.2.4.5.3 Using the CME.................................................................................................................................................... 43
8.2.7 Possible Issues........................................................................................................................................................... 44
8.3 Abis MUX (for GSM Only)......................................................................................................................................... 45
8.3.1 When to Use.............................................................................................................................................................. 45
8.3.3 Planning..................................................................................................................................................................... 45
8.3.3.1 RF Planning............................................................................................................................................................ 45
8.3.4 Deployment............................................................................................................................................................... 46
Issue 01 (2016-09-30) Huawei Proprietary and Confidential iv

SingleRAN
8.3.4.1 Requirements.......................................................................................................................................................... 46
8.3.4.3 Activation............................................................................................................................................................... 47
8.3.4.3.3 Using the CME.................................................................................................................................................... 48
8.3.4.5 Deactivation............................................................................................................................................................49
8.3.4.5.3 Using the CME.................................................................................................................................................... 49
8.3.7 Possible Issues........................................................................................................................................................... 51
8.4 PPP MUX..................................................................................................................................................................... 51
8.4.1 When to Use.............................................................................................................................................................. 51
8.4.3 Planning..................................................................................................................................................................... 51
8.4.3.1 RF Planning............................................................................................................................................................ 51
8.4.4 Deployment on the Base Station............................................................................................................................... 52
8.4.4.1 Requirements.......................................................................................................................................................... 52
8.4.4.3 Activation............................................................................................................................................................... 54
8.4.4.3.3 Using the CME.................................................................................................................................................... 55
8.4.4.5 Deactivation............................................................................................................................................................55
8.4.5 Deployment on the Base Station Controller.............................................................................................................. 55
8.4.5.1 Requirements.......................................................................................................................................................... 55
8.4.5.3 Activation............................................................................................................................................................... 58
8.4.5.3.3 Using the CME.................................................................................................................................................... 58
8.4.5.5 Deactivation............................................................................................................................................................58
8.4.8 Possible Issues........................................................................................................................................................... 59
Issue 01 (2016-09-30) Huawei Proprietary and Confidential v

SingleRAN
8.5 IPHC............................................................................................................................................................................. 59
8.5.1 When to Use.............................................................................................................................................................. 59
8.5.3 Planning..................................................................................................................................................................... 60
8.5.3.1 RF Planning............................................................................................................................................................ 60
8.5.4 Deployment on the eNodeB/NodeB/eGBTS............................................................................................................. 62
8.5.4.1 Requirements.......................................................................................................................................................... 62
8.5.4.3 Activation............................................................................................................................................................... 65
8.5.4.3.3 Using the CME.................................................................................................................................................... 66
8.5.4.5 Deactivation............................................................................................................................................................67
8.5.4.5.3 Using the CME.................................................................................................................................................... 67
8.5.5 Deployment on the GBTS......................................................................................................................................... 67
8.5.5.1 Requirements.......................................................................................................................................................... 67
8.5.5.3 Activation............................................................................................................................................................... 68
8.5.5.3.3 Using the CME.................................................................................................................................................... 69
8.5.5.5 Deactivation............................................................................................................................................................70
8.5.5.5.3 Using the CME.................................................................................................................................................... 70
8.5.6.1 Requirements.......................................................................................................................................................... 70
8.5.6.3 Activation............................................................................................................................................................... 73
8.5.6.3.3 Using the CME.................................................................................................................................................... 75
8.5.6.5 Deactivation............................................................................................................................................................75
Issue 01 (2016-09-30) Huawei Proprietary and Confidential vi

SingleRAN
8.5.6.5.3 Using the CME.................................................................................................................................................... 75

8.5.9 Possible Issues........................................................................................................................................................... 76
8.6 PPPHC.......................................................................................................................................................................... 78
8.6.1 When to Use.............................................................................................................................................................. 78
8.6.3 Planning..................................................................................................................................................................... 78
8.6.3.1 RF Planning............................................................................................................................................................ 78
8.6.4.1 Requirements.......................................................................................................................................................... 79
8.6.4.3 Activation............................................................................................................................................................... 81
8.6.4.3.3 Using the CME.................................................................................................................................................... 82
8.6.4.5 Deactivation............................................................................................................................................................83
8.6.5.1 Requirements.......................................................................................................................................................... 83
8.6.5.3 Activation............................................................................................................................................................... 85
8.6.5.3.3 Using the CME.................................................................................................................................................... 86
8.6.5.5 Deactivation............................................................................................................................................................86
8.6.6.1 Requirements.......................................................................................................................................................... 86
8.6.6.3 Activation............................................................................................................................................................... 89
8.6.6.3.3 Using the CME.................................................................................................................................................... 90
8.6.6.5 Deactivation............................................................................................................................................................90
8.6.9 Possible Issues........................................................................................................................................................... 91
8.7 MLPPP/MC-PPP.......................................................................................................................................................... 91
Issue 01 (2016-09-30) Huawei Proprietary and Confidential vii

SingleRAN
8.7.1 When to Use.............................................................................................................................................................. 91

8.7.3 Planning..................................................................................................................................................................... 91
8.7.3.1 RF Planning............................................................................................................................................................ 91
8.7.4.1 Requirements.......................................................................................................................................................... 92
8.7.4.3 Activation............................................................................................................................................................... 95
8.7.4.3.3 Using the CME.................................................................................................................................................... 95
8.7.4.5 Deactivation............................................................................................................................................................96
8.7.5.1 Requirements.......................................................................................................................................................... 96
8.7.5.3 Activation............................................................................................................................................................... 99
8.7.5.3.3 Using the CME.................................................................................................................................................... 99
8.7.5.5 Deactivation............................................................................................................................................................99
8.7.6.1 Requirements.......................................................................................................................................................... 99
8.7.6.2 Data Preparation................................................................................................................................................... 100
8.7.6.3 Activation............................................................................................................................................................. 102
8.7.6.3.1 Using MML Commands.................................................................................................................................... 103
8.7.6.3.2 MML Command Examples............................................................................................................................... 103
8.7.6.3.3 Using the CME.................................................................................................................................................. 103
8.7.6.4 Activation Observation.........................................................................................................................................103
8.7.6.5 Deactivation..........................................................................................................................................................103
8.7.7 Performance Monitoring..........................................................................................................................................103
8.7.8 Parameter Optimization........................................................................................................................................... 103
8.7.9 Possible Issues......................................................................................................................................................... 103
9 Parameters................................................................................................................................... 104
10 Counters.................................................................................................................................... 125
11 Glossary..................................................................................................................................... 126
12 Reference Documents............................................................................................................. 127
Issue 01 (2016-09-30) Huawei Proprietary and Confidential viii

SingleRAN
Description 1 About This Document
1 About This Document
1.1 Scope
This document describes transmission efficiency improvement mechanisms used in GSM,
UMTS, and LTE networks, including its technical principles, related features, network impact,
and engineering guidelines.
This document covers the following features:
l LBFD-003004 Compression & Multiplexing over E1/T1

l LBFD-00300401 IP Header Compression
l LBFD-00300402 PPP MUX
l LBFD-00300403 ML-PPP/MC-PPP
l TDLBFD-003004 Compression & Multiplexing over E1/T1
l TDLBFD-00300401 IP Header Compression
l TDLBFD-00300402 PPP MUX
l TDLBFD-00300403 ML-PPP/MC-PPP
l GBFD-118604 Abis MUX
l GBFD-118612 Abis IPHC
l GBFD-118610 UDP MUX for A Transmission
l WRFD-050420 FP MUX for IP Transmission
l WRFD-050412 UDP MUX for Iu-CS Transmission
For definitions of base stations described in this document, see section "Base Station
Products" in SRAN Networking and Evolution Overview Feature Parameter Description.
1.2 Intended Audience

This document is intended for personnel who:
l Need to understand the features described herein

l Work with Huawei products
Issue 01 (2016-09-30) Huawei Proprietary and Confidential 1

SingleRAN
1.3 Change History

This section provides information about the changes in different document versions. There are
two types of changes:
l Feature change
Changes in features of a specific product version
l Editorial change
Changes in wording or addition of information that was not described in the earlier
version
SRAN12.1 01 (2017-03-08)
This issue does not include any changes.
SRAN12.1 Draft A (2016-12-30)

Draft A (2016-12-30) of SRAN12.1 introduces the following changes to Issue 02
(2016-05-26) of SRAN11.1.
Change Change Description Parameter Change

Type
Feature Added support for IP transmission efficiency None

change improvement by FG2e boards of a BSC.
Added support for IP transmission efficiency None

improvement by LTE NB-IoT.
Editorial Revised the descriptions in this document. None

change
1.4 Differences Between Base Station Types

Feature Support by Macro, Micro, and LampSite Base Stations
Feature ID Feature Name Suppo Suppo Suppo
rted rted rted
by by by
Macro Micro Lamp
Base Base Site
Statio Statio Base
ns ns Statio
ns
LBFD-003004 Compression & Multiplexing over Yes No Yes

E1/T1

SingleRAN
Feature ID Feature Name Suppo Suppo Suppo

rted rted rted
by by by
Macro Micro Lamp
Base Base Site
Statio Statio Base
ns ns Statio
ns
TDLBFD-003004 Compression & Multiplexing over Yes No Yes

E1/T1
LBFD-00300401 IP Header Compression Yes No Yes
TDLBFD-00300401 IP Header Compression Yes No Yes
LBFD-00300402 PPP MUX Yes No Yes
TDLBFD-00300402 PPP MUX Yes No Yes
LBFD-00300403 ML-PPP/MC-PPP Yes No Yes
TDLBFD-00300403 ML-PPP/MC-PPP Yes No Yes
GBFD-118604 Abis MUX Yes No No
GBFD-118612 Abis IPHC Yes No No
GBFD-118610 UDP MUX for A Transmission Yes No No
WRFD-050420 FP MUX for IP Transmission Yes Yes Yes
WRFD-050412 UDP MUX for Iu-CS N/A N/A N/A

Transmission
Function Implementation in Macro, Micro, and LampSite Base Stations

Function Difference
Multiplexing Micro base stations do not support PPP MUX.
Header Micro base stations do not support IPHC or PPPHC.

compression
PPP extended Micro base stations do not support MLPPP or MC-PPP.

protocol

SingleRAN
Description 2 Overview
2 Overview
Transmission efficiency improvement is highly necessary in today's networks with ever-

increasing traffic volume to increase their transmission bandwidth usage. The IP transmission
bandwidth usage can be increased by using multiplexing and header compression
technologies that reduce the header overhead of packets.
Different mechanisms for improving IP transmission efficiency are provided based on the
characteristics of the protocols, as shown in Figure 2-1.
Figure 2-1 Mechanisms for improving IP transmission efficiency

SingleRAN
Description 3 Multiplexing
3 Multiplexing
3.1 Overview
Multiplexing reduces the header overhead of packets by multiplexing multiple packets into
one packet to improve transmission efficiency.
Multiplexing technologies include:
l FP MUX
l UDP MUX
l Abis MUX
l Ater MUX
l PPP MUX
Multiplexing may result in delay and jitter; therefore, multiplexing is not recommended when
bandwidth resources are sufficient.
3.2 Frame Protocol Multiplexing (for UMTS Only)
3.2.1 Introduction
Frame Protocol Multiplexing (FP MUX), corresponding to the WRFD-050420 FP MUX for
IP Transmission feature, encapsulates multiple FP PDUs into one FP MUX packet, reducing
the UDP/IP/L2/L1 header transmission overhead and resulting in improved transmission
efficiency. FP MUX is not an open standard.
FP MUX has the following characteristics:
l The implementation is simple. FP MUX requires the support of only the transmission
end and the reception end. The intermediate transport equipment does not need to
support FP MUX.
l FP MUX significantly improves the transmission efficiency but increases the
transmission delay.
FP MUX is applicable only to the user plane of the Iub interface that is based on IP
transmission. The BSC6900, BSC6910, and NodeB support this feature.

SingleRAN
The corresponding feature of FP MUX supported by Iub for UMTS is WRFD-050420 FP

MUX for IP Transmission.
3.2.2 Technical Description
3.2.2.1 Packet Format

Figure 3-1 shows the format of an IP packet where FP MUX is applied. A multiplexed IP
packet has the following characteristics:
l The FP PDUs in one FP MUX frame share the IP and UDP headers and therefore must
have the same source IP address, destination IP address, and DSCP.
l One FP MUX frame can carry the data of multiple users. The FP MUX header specifies
the size and owner of each FP PDU.
l The UDP header contains a fixed source UDP port number. The number indicates that
this packet is an FP MUX packet and therefore requires demultiplexing at the reception
end.
Figure 3-1 Format of an FP MUX IP packet
The fields in Figure 3-1 are described as follows:
l User Identifier: specifies the owner of an FP PDU.

l Length Indicator: specifies the size of an FP PDU.
l FP PDU: is the payload of an FP subframe.
FP MUX significantly improves the transmission efficiency. Take the speech service as an
example. The size of each speech packet is 41 bytes, and the total size of the IP and UDP
headers is 28 bytes. If FP MUX is not applied, the size of the IP packet is 69 bytes (28 bytes
+ 41 bytes). If FP MUX is applied, the transmission efficiency is improved because the ratio
of the UDP data size to the IP packet size increases from 60% to 70% or even to 90% when
the number of FP subframes in the FP MUX frame increases. The ratio equals (41 x n)
divided by [28 + (41 + 3) x n], where n is a natural number. However, when the size of the IP
packet increases, the transmission delay also increases.
The parameters related to FP MUX are as follows:

SingleRAN
l FP MUX switch: specifies whether to enable FP MUX.

l Max subframe length[byte]: specifies the maximum size of an FP subframe. If the size
of an FP subframe exceeds the value of this parameter, the FP subframe is not
multiplexed.
l Max frame length[byte]: specifies the maximum size of an FP MUX frame.
l Max delay time[ms]: specifies the maximum period of time that the system waits before
sending the multiplexed data. If the waiting time exceeds the value of this parameter, the
system immediately sends the multiplexed data to prevent a long delay.
NE FP MUX Max Max frame Max delay
switch subframe length time
length
RNC When SUBFRAMEL MAXFRAMEL FPTIMER

MUXTYPE is EN EN
set to FPMUX,
FP MUX is
enabled.
NodeB When SUBFRAMEL FRAMELEN TIMER (ADD

IPMUXSWITC EN (ADD (ADD IPPATH)
H is set to IPPATH) IPPATH)
ENABLE, FP
MUX is
enabled.
3.2.2.2 Principles
The prerequisites for enabling FP MUX are as follows:
l Both the RNC and the NodeB support FP MUX.

l The data related to FP MUX is configured on both the RNC and NodeB sides.
Figure 3-2 shows the working principle of FP MUX at the transmission end.
Figure 3-2 Buffering and multiplexing performed at the transmission end
The transmission end buffers the user data (FP PDUs) and encapsulates the data into FP MUX
frames according to specific multiplexing conditions. Then, the FP MUX frame is sent to the
UDP layer.
The multiplexing conditions are as follows:

SingleRAN
l If the size of an FP PDU exceeds Max subframe length, the FP PDU is not multiplexed
but directly sent to the UDP layer.
l If the size of an FP MUX frame reaches Max frame length, the FP MUX frame is sent
to the UDP layer without being multiplexed with more FP PDUs.
l If the value of the timer reaches Max delay time, the FP MUX frame is sent to the UDP
layer without being multiplexed with more FP PDUs.
After receiving the FP MUX frames in sequence, the reception end demultiplexes the frames
to obtain the original data and perform service processing.
3.3 UDP Multiplexing (for GSM and UMTS Only)
3.3.1 Introduction
UDP Multiplexing (UDP MUX) is a transport bearer multiplexing technology, which is
defined in 3GPP TR 29.814. It is also called RTP MUX. This technology enables multiple
RTP packets to be multiplexed in one UDP packet, reducing the overhead of the
UDP/IP/L2/L1 header and increasing the transmission efficiency.
UDP MUX has the following characteristics:
l The implementation is simple. UDP MUX requires support only at the transmission end
and the reception end. The intermediate transport equipment does not need to support
UDP MUX.
l UDP MUX significantly improves the transmission efficiency but increases the
transmission delay.
l UDP MUX is an open standard.
UDP MUX is applicable to the user plane of the A and Iu-CS interfaces that are based on IP
transmission. The BSC6900 and BSC6910 support UDP MUX.
UDP MUX applied to the A interface corresponds to the GBFD-118610 UDP MUX for A
Transmission feature.
UDP MUX applied to the Iu-CS interface corresponds to the WRFD-050412 UDP MUX for
Iu-CS Transmission feature.
3.3.2.1 Packet Format

UDP MUX has two multiplexing modes:
l Multiplexing mode 1: In this mode, the RTP header is multiplexed without being
compressed. The size of an RTP header is 12 bytes. 3.3.2.1 Packet Format shows the IP
packet format with the RTP header uncompressed.
l Multiplexing mode 2: In this mode, the RTP header is compressed and then multiplexed.
The field that remains unchanged during a call is removed from the RTP header, and
only the variable Sequence Number and Timestamp fields are reserved. The size of the
RTP header after compression is 3 bytes (UMTS) or 4 bytes (GSM). Figure 3-4 shows
the IP packet format with the RTP header compressed.

SingleRAN
Figure 3-3 IP packet format with the RTP header uncompressed
Figure 3-4 IP packet format with the RTP header compressed
The following describes the fields of a UDP MUX packet.
l T: specifies whether the RTP header is compressed. Value 0 indicates that the RTP
header is not compressed, and value 1 indicates that the RTP header is compressed.
l Mux ID: is used in combination with the Source ID field to identify a user plane
connection. The value of this field is equal to the destination UDP port number of the
RTP packet divided by two.
l Length indicator: specifies the size of a multiplexed RTP packet, including the size of the
RTP header and payload. This field gives the information where the next multiplexed
RTP packet starts.
l R: reserved extension bit. This field is set to 0.
l Source ID: is used in combination with the Mux ID field to identify a user plane
connection. The value of this field is equal to the source UDP port number of the RTP
packet divided by two.
l Sequence Number: specifies the sequence number of an RTP packet.

SingleRAN
l Timestamp: specifies the time point when an RTP packet is sent.

l Payload Type: specifies the type of the payload.
UDP MUX packets have the following characteristics:
l The RTP packets in one UDP MUX packet share the IP and UDP headers and therefore
must have the same source IP address, destination IP address, and DSCP.
l A UDP MUX packet can carry the data of different users. The Multiplex header specifies
the size and owner of each RTP packet.
l The UDP header contains a fixed source UDP port number. The number indicates that
this packet is a UDP MUX packet and therefore requires demultiplexing at the reception
end.
As shown in Figure 3-3 and Figure 3-4, when k RTP packets are multiplexed into one UDP
packet, the IP packet overhead is reduced. When the RTP header is not compressed, an
overhead of (23 x k – 28) bytes is saved. When the RTP header is compressed, an overhead
of (32 x k – 28) bytes is saved. In addition, the total layer 2 and layer 1 header overhead
decreases with the reducing number of packets. Therefore, the multiplexing efficiency is
significantly improved. For detailed analysis, see 3GPP TR 29.814.
In non-transmission resource pool networking, the ADD IPMUX command is used to
configure the multiplexing function for data flows on the specified IP path.
In transmission resource pool networking, the ADD IPPOOLMUX command is used to
enable the multiplexing function for the specified adjacent node based on the specified
priority (PHB). This function enables multiplexing for data flows on the link between the
BSC and the corresponding adjacent node based on the specified priority.
The related parameters on the base station controller are as follows:
l The following three parameters need to be set to enable UDP MUX:

– IP MUX type (MUXTYPE): specifies whether UDP MUX is enabled on the base
station controller side when no transmission resource pools are configured. When
this parameter is set to UDPMUX, UDP MUX is enabled.
– MUX Type (MUXTYPE(BSC6910,BSC6900)): specifies whether UDP MUX is
enabled on the base station controller side when transmission resource pools are
configured. When this parameter is set to UDPMUX, UDP MUX is enabled.
– Sender UDP MUX mode (UDPMUXMODSEND(BSC6910,BSC6900)): specifies
the UDP MUX mode of the base station controller when it transmits data. The value
of this parameter can be NORTPCOMP or RTPCOMP. If this parameter is set to
NORTPCOMP, the base station controller supports UDP MUX with
uncompressed RTP headers when transmitting data. If this parameter is set to
RTPCOMP, the base station controller supports UDP MUX with compressed RTP
headers when transmitting data.
– Receive UDP MUX mode (UDPMUXMODRECV(BSC6910,BSC6900)):
specifies the UDP MUX mode of the base station controller when it receives data.
The value of this parameter can be NORTPCOMP or RTPCOMP. If this
parameter is set to NORTPCOMP, the base station controller supports UDP MUX
with uncompressed RTP headers when receiving data. If this parameter is set to
RTPCOMP, the base station controller supports UDP MUX with compressed RTP
headers when receiving data.
l Max subframe length [byte] (SUBFRAMELEN(BSC6910,BSC6900)): specifies the
maximum size of an RTP packet that can be multiplexed. If the size of an RTP packet

SingleRAN
exceeds the value of this parameter, the RTP packet is transmitted without being
multiplexed.
l Maximum frame length [byte] (MAXFRAMELEN(BSC6910,BSC6900)): specifies
the maximum size of a UDP MUX packet. If the size of a UDP MUX packet exceeds the
value of this parameter, the packet is transmitted without being added with more packets.
l Maximum delay time[ms] (FPTIMER(BSC6910,BSC6900)): specifies the maximum
period of time that the system waits before sending the multiplexed data. If the waiting
time exceeds the value of this parameter, the system immediately sends the multiplexed
data to prevent a long delay.
3.3.2.2 Principles
The prerequisites for enabling UDP MUX are as follows:
l Both the BSC/RNC and MGW support UDP MUX.
l The data related to UDP MUX is configured on both the BSC/RNC and MGW sides.
Figure 3-5 shows the working principle of UDP MUX at the transmission end.
Figure 3-5 Buffering and multiplexing performed at the transmission end
The transmission end buffers the user data and encapsulates multiple RTP packets into one
UDP MUX packet according to specific multiplexing conditions.
The multiplexing conditions are as follows:
l If the size of a UDP MUX packet reaches MAXFRAMELEN(BSC6910,BSC6900), the
UDP MUX packet is sent without being multiplexed with more RTP packets.
l If the value of the timer reaches FPTIMER(BSC6910,BSC6900), the UDP MUX packet
is sent without being multiplexed with more RTP packets.
After receiving the UDP MUX packets in sequence, the reception end demultiplexes the
packets to obtain the original data and perform service processing.
3.4 Abis Multiplexing and Ater Multiplexing (for GSM

Only)
3.4.1 Introduction
Abis MUX saves bandwidth by multiplexing packets. The BSC and BTS serve as transmit
and receive ends for each other. When Abis MUX is enabled, the transmit end multiplexes the
IP or User Datagram Protocol (UDP) packets that meet the multiplexing requirements.

SingleRAN
Multiple IP or UDP packets are multiplexed into one IP or UDP header at the transmit end
and demultiplexed at the receive end to recover the original data in the IP/UDP packets. This
improves transmission efficiency and saves transmission bandwidth.
The differences between Abis MUX and Ater MUX are as follows: Abis MUX applies to the
IP-based user plane for the Abis interface, whereas Ater MUX applies to the IP-based user
plane for the Ater interface. The BSC6910 does not support Ater MUX.
The corresponding feature of Ater MUX is GBFD-118604 Abis MUX.

This section describes the Ater MUX and Abis MUX (corresponding to the GBFD-118604
Abis MUX feature) mechanisms. The packet formats and working principles for Ater MUX
and Abis MUX are the same as those for FP MUX. For details, see section 3.2 Frame
Protocol Multiplexing (for UMTS Only).
When the BSC works in non-transmission resource pool networking mode and MUXTYPE is
set to ABISMUX, Abis MUX is enabled on the BSC. Other parameters are as follows:
l Maximum delay time[ms] (FPTIMER): specifies the maximum period of time that the
system waits before sending the multiplexed data. If the waiting time exceeds the value
of this parameter, the system immediately sends the multiplexed data to prevent a long
delay.
l IS QOSPATH (ISQOSPATH): specifies whether a path is a QoS path.
l Max frame length[byte] (MAXFRAMELEN): specifies the maximum size of an Abis
MUX frame.
l PHB (PHB): specifies the PHB type of the IPMUX to be enabled.
l Max subframe length[byte] (SUBFRAMELEN): specifies the maximum size of an
Abis subframe. If the size of an Abis subframe exceeds the value of this parameter, the
Abis subframe is not multiplexed.
When the BSC works in transmission resource pool networking mode and
MUXTYPE(BSC6910,BSC6900) is set to ABISMUX, Abis MUX is enabled on the BSC.
Other parameters are as follows:
l PHB (PHB(BSC6910,BSC6900)): specifies the PHB type of the IPMUX to be enabled.

l Max subframe length[byte] (SUBFRAMELEN(BSC6910,BSC6900)): specifies the
maximum size of an Abis subframe. If the size of an Abis subframe exceeds the value of
this parameter, the Abis subframe is not multiplexed.
l Maximum delay time[ms] (FPTIMER(BSC6910,BSC6900)): specifies the maximum
l Max frame length[byte] (MAXFRAMELEN(BSC6910,BSC6900)): specifies the
maximum size of an Abis MUX frame.
When IPMUXSWITCH is set to ENABLE, Abis MUX is enabled on the eGBTS. Other
parameters are as follows:
l Max Timer (TIMER): specifies the maximum period of time that the system waits
before sending the multiplexed data. If the waiting time exceeds the value of this
parameter, the system immediately sends the multiplexed data to prevent a long delay.

SingleRAN
l Max Frame Length (FRAMELEN): specifies the maximum size of an Abis MUX
frame.
l Max Subframe Length (SUBFRAMELEN): specifies the maximum size of an Abis
subframe. If the size of an Abis subframe exceeds the value of this parameter, the Abis
subframe is not multiplexed.
The Abis MUX parameters on the GBTS are as follows:
l Max Subframe Length (SUBFRAMETHRES(BSC6910,BSC6900)): specifies the
maximum size of an Abis subframe. If the size of an Abis subframe exceeds the value of
this parameter, the Abis subframe is not multiplexed.
l Maximum Frame Length (PKTLENTHRES(BSC6910,BSC6900)): specifies the
maximum size of an Abis MUX frame.
l Maximum Delay Time (TIMEOUT(BSC6910,BSC6900)): specifies the maximum
l Service Type (SRVTYPE(BSC6910,BSC6900)): specifies the type of service for which
multiplexing is performed. The service type can be CS speech service, CS data service,
PS high-priority service, and PS low-priority service.
The Ater MUX parameters on the BSC6900 are as follows:
l IP MUX Type (MUXTYPE): When this parameter is set to ATERMUX, Ater MUX is
enabled on the BSC6900.
3.5 PPP MUX

3.5.1 Introduction
PPP MUX corresponds to the following features:
l LBFD-00300402 PPP MUX
l TDLBFD-00300402 PPP MUX
PPP MUX is a technology through which multiple PPP payloads (also called PPP MUX
subframes) are encapsulated into a single PPP frame (also called a PPP MUX frame) to
reduce the overhead of each PPP subframe and improve the bandwidth usage on PPP links.
PPP MUX applies to scenarios where short packets such as speech and data are transmitted
over low-speed links. For long packets, PPP MUX does not improve the transmission
efficiency adequately and prolongs the transmission delay. Therefore, using PPP MUX to
transmit long packets is not recommended.
The PPP MUX frame format is defined in RFC3153. PPP MUX is supported by:
l GSM: the Ater interface of the BSC6900
l UMTS: the Iub, Iur, and Iu interfaces of the controller and the Iub interface of the NodeB
l LTE: the S1 and X2 interfaces of the eNodeB

By using PPP MUX, multiple PPP-encapsulated packets (or subframes), such as voice and
data packets, of small sizes on low-speed links can be sent in a single PPP multiframe,

SingleRAN
reducing the PPP overhead of each frame. The PPP MUX frame is a multiframe, in which
each multiplexed frame is called a subframe. Subframes in a PPP multiframe are separated by
field separators, which ensures the recovery of the PPP frames at the receive end.
Figure 3-6 shows the structure of a PPP Mux multiframe. Figure 3-7 shows the structure of a
subframe.
Figure 3-6 Structure of a PPP MUX frame
Figure 3-7 Structure of a PPP subframe
Each PPP MUX protocol data unit (PDU) consists of a 2-byte PPP MUX identifier (0X0059)
and multiple subframes. Each subframe consists of the following parts:
l The protocol field flag (PFF) indicates whether a PPP identifier is included in the
subframe.
l The length extension (LXT) bit indicates whether one or two bytes are contained in the
length field.
l The subframe length (LEN) indicates the number of bytes occupied by the PPP identifier
and information field of the subframe.
Compared with the original payload, each subframe is added with a 1-byte field indicating the
length and a protocol identifier (PID) field that exists only in the header subframe. The PID
field is shown in Figure 3-7. The PID field consists of zero to two bytes, indicating the
multiplexed protocol types.
Parameters related to PPP MUX are as follows:
l PPP MUX switch: specifies whether to enable PPP MUX.

l Maximum PPP MUX subframe size: specifies the maximum size of a PPP MUX
subframe. If the size of a PPP MUX subframe exceeds the value of this parameter, the
subframe is transmitted directly without being multiplexed.
l Maximum PPP MUX frame size: specifies the maximum size of a PPP MUX frame.
l PPP MUX frame timer: specifies the maximum waiting time for multiplexing. If the
waiting time exceeds the value of this parameter, the PPP MUX frame is transmitted
without adding more PPP MUX subframes.

SingleRAN
NE PPP MUX Maximum Maximum PPP MUX

Switch PPP MUX PPP MUX Frame Timer
Subframe Frame Size
Size
BSC6900 PPPMUX MAXSFLEN MAXMFLEN MUXTIME
BSC6910 PPPMUX MAXSFLEN MAXMFLEN MUXTIME
NodeB MUXCP MAXSFLEN MAXMFLEN MUXTIME
eNodeB MUXCP MAXSFLEN MAXMFLEN MUXTIME

SingleRAN
Description 4 Header Compression
4 Header Compression
4.1 Overview
Header compression is used in IP over E1/T1 mode to reduce the frame header load on PPP
links or MLPPP links so that transmission bandwidth usage increases. Header compression
requires point-to-point support from both the transmit and receive ends.
Header compression technologies include:
l IP Header Compression (IPHC)

l PPP Header Compression (PPPHC): Address and Control Field Compression (ACFC)
and Protocol Field Compression (PFC)
Compared with multiplexing, header compression is more suitable when the bit error rate
(BER) is high.
4.2 IPHC
4.2.1 Introduction
This section describes IPHC for transmission efficiency improvement, which corresponds to
the following features:
l LBFD-00300401 IP Header Compression

l TDLBFD-00300401 IP Header Compression
l GBFD-118612 Abis IPHC
As defined in RFC2507 and RFC3544, IPHC is a standard compression technology in IP over

E1 mode and is used to compress the IP, UDP, and RTP headers transmitted over PPP links.
IPHC deletes redundant information from the headers of IP or UDP packets that share the
same source and destination IP addresses as well as the same source and destination ports in
the UDP data flow. This improves transmission efficiency and saves IP transmission
resources.

SingleRAN

The IPHC working principles are as follows:
l Fixed fields in the IP, UDP, and RTP headers are only included in some packets, and
variable fields are represented in fewer bits.
l During PPP establishment, packets with complete headers are transmitted to establish the
header context at both ends. Subsequently, complete headers are retrieved from the
compressed header based on the header context and the variable fields.
The IPHC-related parameters specify whether header compression is supported by both ends
of a PPP or MLPPP link. That is, the two ends negotiate whether to compress the UDP, IP,
and RTP headers during link establishment.
IPHC removes redundant information in IP/UDP headers in UDP data flows to improve
transmission efficiency.
The user plane uses UDP/IP protocols. A typical data packet includes an 8-byte UDP header
and a 20-byte IP header. Figure 4-1 shows the frame structure of a UDP/IP packet. The UDP
header contains 4 fields, indicating the IP addresses of the source and destination UDP ports,
packet length, and packet checksum. The IP header contains 12 fields, indicating the source
and destination IP addresses and type of service (ToS).
Figure 4-1 Frame structure of a UDP/IP packet
All packets in the same data stream have the same source and destination IP addresses. Most
fields in each packet header have constant values during transmission. IPHC compresses these
constant fields. In this way, the transmit end can use a simplified header to replace a standard
header (the IP/UDP header shown in Figure 4-1, which has 16 fields and occupies 28 bytes).
Therefore, the header size is reduced by 80%.
An IP/UDP header for the GSM and UMTS is reduced from 28 bytes to 4 bytes, as shown in
Figure 4-2.

SingleRAN
Figure 4-2 IPHC working principle
An IP/UDP header for the LTE is reduced from 28 bytes to 5 bytes. The 5-byte compressed
header contains a context identifier (CID, 2 bytes), a generation field (1 byte), and an IP
identifier (2 bytes). The header is enough for uniquely identifying the data stream. The
receive end replaces the compressed header with the standard header before decompressing
the header.
Table 4-1 lists the parameters related to IPHC.
Table 4-1 IPHC parameters

NE Parameter Parameter Value Remarks
BSC/RNC IPHC(BSC6910,BS No_HC The BSC/RNC does

C6900) (PPP link) not support IPHC.
or
IPHC(BSC6910,BS UDP/IP_HC The BSC/RNC
C6900) (MLPPP supports IPHC for
group) UDP and IP packets.
RTP/UDP/IP_HC The BSC/RNC

supports IPHC for
UDP, RTP, and IP
packets.
GBTS IPHC(BSC6910,BS DISABLE The GBTS does not

C6900) (PPP link) support IPHC.
or
IPHC(BSC6910,BS ENABLE The GBTS supports
C6900) (MLPPP IPHC for UDP and
group) IP packets.
eGBTS/NodeB/ IPHC (PPP link) or DISABLE The NodeB/

eNodeB IPHC (MLPPP eNodeB/eGBTS
group) does not support
IPHC.

SingleRAN
NE Parameter Parameter Value Remarks
ENABLE The NodeB/

eNodeB/eGBTS
supports IPHC for
UDP and IP packets.
IPHCSUBOPT DISABLE Set this parameter to

(PPP link) or DISABLE(Disable)
IPHCSUBOPT if the peer device
(MLPPP group) does not support
negotiating about
the setting of this
parameter with the
local device.
ENABLE Set this parameter to

ENABLE(Enable)
if the peer device
supports negotiating
about the setting of
this parameter with
the local device.
IPHC increases bandwidth usage, depending on the payload size. A smaller payload value
will result in higher bandwidth usage.
4.3 PPPHC
4.3.1 Introduction
This section describes PPPHC for transmission efficiency improvement, which corresponds to
the following features:
l LBFD-003004 Compression & Multiplexing over E1/T1

l TDLBFD-003004 Compression & Multiplexing over E1/T1
PPPHC is used to compress PPP headers. The ACFC and PFC techniques can be used
together or separately. The specific techniques are negotiated during the Link Control
Protocol (LCP) phase.
4.3.2.1 PPP Frame Format

The PPP frame format is defined in IETF RFC1661, as shown in Figure 4-3.

SingleRAN
Figure 4-3 PPP frame format
The flag field (F) is 0x7E. The address field (A) and the control field (C) have fixed values of
0xFF and 0x03.
The fields of a PPP frame shown in Figure 4-3 are described as follows:
l Flag: specifies the start or end of a frame. This field for a PPP frame is set to a fixed
value.
l Address: specifies an address. This field is set to a fixed value.
l Control: specifies the control field. This field is set to a fixed value.
l Protocol: specifies the type of the protocol encapsulated by the information field. For
example, 0x0021 indicates that an IP packet is encapsulated.
l Information (also known as payload): contains the upper-layer protocol datagram
encapsulated by a PPP frame. The size of the information field varies and the maximum
size is specified by the maximum receive unit (MRU). The MRU is negotiable during the
PPP link establishment. If the MRU is not negotiated, the default size is 1500 bytes.
Different values of the Protocol field indicate different types of information fields, as
shown in Table 4-2.
l FCS: specifies the frame check sequence field.
Table 4-2 Mapping between the Protocol field value and information field type
Protocol Field Value Information Field Type
0x0021 IP packet
0xC021 LCP data
0x8021 Network Control Protocol (NCP) data
0xC023 Password Authentication Protocol (PAP)

data
0xC025 Link Quality Report (LQR) data
0xC223 Challenge Handshake Authentication

Protocol (CHAP) data

SingleRAN
4.3.2.2 ACFC
As defined in RFC1661, ACFC is used to compress the address and control fields in PPP and
MLPPP frames.
Since the address field (field A shown in Figure 4-3) and control field (field C shown in
Figure 4-3) in a PPP header have fixed values during transmission, these fields can be
compressed to conserve bandwidth. During link establishment, the transmit and receive ends
negotiate link attributes, including whether to use ACFC. During the LCP phase, the transmit
and receive ends negotiate whether to compress these fields based on the option "Address-
and-Control-Field-Compression" in control messages sent on PPP links. If both ends use
ACFC, the address and control fields are omitted in subsequent frames.
On the BSC/RNC, if ACFC(BSC6910,BSC6900) for PPP links and
ACFC(BSC6910,BSC6900) for MLPPP links are set to Enable, ACFC is supported. The two
ends then negotiate whether to use ACFC. If the parameters are set to Disable, ACFC is not
supported.
On the eNodeB/NodeB/eGBTS, the ACFC(N/A,GSM BSC6910,GSM BSC6900) parameter
specifies whether to activate ACFC for a PPP link. The ACFC(N/A,GSM BSC6910,GSM
BSC6900) parameter specifies whether to activate ACFC for an MLPPP link.
On the GBTS, the ACFC(N/A,GSM BSC6910,GSM BSC6900) parameter specifies whether
to activate ACFC for a PPP link. The ACFC(N/A,GSM BSC6910,GSM BSC6900) parameter
specifies whether to activate ACFC for an MLPPP link.
4.3.2.3 PFC
As defined in RFC1661, PFC is used to compress the protocol field in PPP and MLPPP
frames.
The size of the protocol field in a PPP or MLPPP frame header (the Protocol field shown in
Figure 4-3) is two bytes. This field specifies the type of the encapsulated protocol. For
example, 0x0021 indicates that an IP packet is encapsulated. Typically, packets at the network
layer, such as IP packets and compressed UDP/IP packets, have a protocol field value of less
than 0xFF. In this situation, the protocol field in each header can be compressed from 2 bytes
to 1 byte.
The least significant bit of the protocol field in a PPP or MLPPP frame specifies whether to
use PFC. Value 0 indicates that PFC is not used, and value 1 indicates that PFC is used.
On the BSC/RNC, if PFC(BSC6910,BSC6900) for PPP links and PFC(BSC6910,BSC6900)
for MLPPP links are set to Enable, PFC is supported. The two ends then negotiate whether to
use PFC. If the parameters are set to Disable, PFC is not supported.
On the eNodeB/NodeB/eGBTS, the PFC parameter specifies whether to activate PFC for a
PPP link. The PFC parameter specifies whether to activate PFC for an MLPPP link.
On the GBTS, the PFC(BSC6910,BSC6900) parameter specifies whether to activate PFC for
a PPP link. The PFC(BSC6910,BSC6900) parameter specifies whether to activate PFC for an
MLPPP link.

SingleRAN
Description 5 MLPPP/MC-PPP
5 MLPPP/MC-PPP
5.1 Overview
This section describes MLPPP/MC-PPP for transmission efficiency improvement, which
corresponds to the following features:
l LBFD-00300403 ML-PPP/MC-PPP
l TDLBFD-00300403 ML-PPP/MC-PPP
MLPPP (also called MP) is an extension of the PPP protocol. It is a data link layer protocol
that exists between the PPP layer and the network layer. MLPPP stands for Multi-Link Point-
to-Point Protocol.
MLPPP is used to combine multiple PPP links (also called MLPPP links) into one logical
link. MLPPP fragments upper-layer packets and then transmits the fragmented packets over
MLPPP links, increasing transmission efficiency.
MC-PPP is an extension of MLPPP. MC-PPP stands for Multi-Class Point-to-Point Protocol.

MC-PPP prioritizes packets and then fragments the packets in descending order of priority,
providing more service classes compared with MLPPP.
5.2 Technical Description

PPP defines the standard method of encapsulating the IP packets on point-to-point links. The
point-to-point links include the E1/T1 links and SDH links. E1/T1 ports use the PPP protocol
at the data link layer. The PPP protocol has two disadvantages:
l Each PPP link corresponds to only one E1 link. If multiple E1 links are used as transport
bearers, multiple PPP links must be configured. On a live network, the services with
heavy traffic require bandwidths of more than one E1 link.
l PPP frames are transmitted in sequence. As a result, high-priority frames may fail to be
transmitted because the network is congested with a large number of low-priority frames,
resulting in end-to-end performance deterioration.
To address the preceding problems, the MLPPP/MC-PPP technique is used to increase the
transport bandwidths, enhance transmission reliability, and ensure the transmission priority.

SingleRAN
5.2.1 MLPPP
Data Transmission Mechanism
MLPPP is used to combine multiple PPP links into one logical link. MLPPP fragments IP
packets and then transmits the fragmented packets over MLPPP links. In this manner, the
bandwidth and throughput are increased. Meanwhile, the transmission delay is reduced.
Figure 5-1 shows the MLPPP process: A large packet is fragmented into small packets, and
the small packets are transmitted on different physical links.
Figure 5-1 MLPPP process
Frame Format
The MLPPP frame format is defined in RFC1990. The MLPPP frame has two formats: with a
long sequence number and with a short sequence number, as shown in Figure 5-2 and Figure
5-3, respectively.
Figure 5-2 MLPPP frame format with a long sequence number

SingleRAN
Figure 5-3 MLPPP frame format with a short sequence number
The fields of the MLPPP frame header are described as follows:

l B: Beginning fragment bit (one bit). This field specifies whether an MLPPP frame is the
first fragment of a PPP frame.
l E: Ending fragment bit (one bit). This field specifies whether an MLPPP frame is the last
fragment of a PPP frame.
5.2.2 MC-PPP
MC-PPP (also called MC) is an extended protocol on the basis of MLPPP. MC-PPP stands for
Multi-Class Point-to-Point Protocol. By using the reserved bits in the MLPPP packets, MC-
PPP grants priorities to the packets transmitted at the link convergence layer. Therefore, the
packets with higher real-time requirements or higher priorities can be transmitted
preferentially, while other packets are suspended. For details about MC-PPP, see RFC2686.
The MLPPP technology divides a large packet into small packets and has each of the small
packets transmitted on different physical links. When different physical links have different
delays, the packets may be out of order. To ensure the correct sequence of packets, MLPPP
and MC-PPP provide sequence numbers for the disassembled packets (small packets).
MLPPP/MC-PPP provides long sequences and short sequences. Long sequences have a
maximum of 16 MC-PPP priorities. Short sequences have a maximum of four MC-PPP
priorities. Currently, the base station controller and base station support different numbers of
MC-PPP priorities as follows:
l If long sequences are used, 8 or 4 MC-PPP priorities are supported.
l If short sequences are used, 4 MC-PPP priorities are supported.

SingleRAN
Description 6 Related Features
6 Related Features
6.1 LBFD-00300401/TDLBFD-00300401 IP Header

Compression
Prerequisite Features
None
Mutually Exclusive Features

None
Impacted Features
None
6.2 LBFD-003004 Compression & Multiplexing over E1/T1

None

None
Impacted Features
None

SingleRAN
6.3 TDLBFD-003004 Compression & Multiplexing over

E1/T1
None

None
Impacted Features
None
6.4 LBFD-00300402/TDLBFD-00300402 PPP MUX

None

None
Impacted Features
None
6.5 LBFD-00300403/TDLBFD-00300403 ML-PPP/MC-PPP

Function Name Description
MLPPP MC-PPP must be used along with MLPPP, while

MLPPP can be used alone.

None
Impacted Features
None

SingleRAN
6.6 GBFD-118604 Abis MUX

Feature ID Feature Name Description
GBFD-118601 Abis over IP N/A
GBFD-118611 Abis IP over E1/T1 N/A

None
Impacted Features
GBFD-118605 IP QOS When this feature is used with

the Transmission Load
Adjustment Based on Actual
Traffic Measurement function
of the GBFD-118605 IP QOS
feature, the Abis transmission
efficiency increases
significantly.
6.7 GBFD-118612 Abis IPHC

GBFD-118611 Abis IP over E1/T1 N/A

None
Impacted Features
None

SingleRAN
6.8 GBFD-118610 UDP MUX for A Transmission

GBFD-118602 A over IP N/A
GBFD-118622 A IP over E1/T1 N/A

None
Impacted Features
None
6.9 WRFD-050420 FP MUX for IP Transmission

WRFD-050402 IP Transmission Introduction N/A

on Iub Interface

None
Impacted Features
WRFD-140208 Iub Transmission Resource l When FP MUX is used, an

Pool in RNC RNC pool supports only one
IP address. NodeBs are
interconnected to the RNC
using IP paths.
l When Transmission
Resource Pool in RNC is
used, an RNC pool supports
multiple IP addresses. This
enables traffic data to be

SingleRAN
WRFD-150243 Iub IP Transmission Based on transmitted on different

Dynamic Load Balance transmission paths to
implement load balancing.
However, FP MUX enables
traffic data to converge on
one transmission path and
multiplexes traffic packets of
the same type to one packet
for transmission, which
reduces the transmission
overhead. Therefore,
Transmission Resource Pool
in RNC and FP MUX cannot
be used concurrently.
6.10 WRFD-050412 UDP MUX for Iu-CS Transmission

WRFD-050409 IP Transmission Introduction N/A

on Iu Interface

None
Impacted Features
None

SingleRAN
Description 7 Network Impact
7 Network Impact
7.1 LBFD-00300401/TDLBFD-00300401 IP Header

Compression
System Capacity
No impact.
Network Performance
No impact.
7.2 LBFD-003004 Compression & Multiplexing over E1/T1/

TDLBFD-003004 Compression & Multiplexing over E1/T1
System Capacity
No impact.
Network Performance
No impact.
7.3 LBFD-00300402/TDLBFD-003004 PPP MUX

System Capacity
No impact.
Network Performance
No impact.

SingleRAN
7.4 LBFD-00300403/TDLBFD-003004 ML-PPP/MC-PPP

System Capacity
No impact.
Network Performance
No impact.
7.5 GBFD-118604 Abis MUX

System Capacity
No impact.
Network Performance
Abis MUX improves transmission efficiency on the Abis interface. Figure 7-1 shows the
frame format before and after Abis MUX is enabled, using enhanced full rate (EFR) speech
packets as an example.
Figure 7-1 Frame format before and after Abis MUX is enabled
Using EFR speech packets as an example, before Abis MUX is enabled, the sizes of the
Ethernet header, IP/UDP header, and payload for a frame are 14, 28, and 37 bytes,
respectively. Therefore, the size of a frame is 83 bytes and the total size of six frames is 498
bytes. After Abis MUX is enabled, six frames are multiplexed. The total size of these
multiplexed frames is 286 bytes, and the average size of each frame is 47.67 bytes. Therefore,
Abis MUX reduces the size of a frame by: (83-47.67)/83 = 42.56%

SingleRAN
Shorter original IP packets and more multiplexed frames lead to higher transmission
efficiency.
When transmission quality deteriorates, especially when there is a bit error, enabling Abis
MUX has a negative impact on speech quality; for example, the mean opinion score (MOS)
decreases. The impact can be minimized by reducing the value of the parameter related to
multiplexing duration or by reducing the size of the frames to be multiplexed. However, the
impact cannot be eliminated. Abis MUX is not recommended if the BER is higher than 10-6.
7.6 GBFD-118612 Abis IPHC

System Capacity
No impact.
Network Performance
Abis IPHC improves transmission efficiency on the Abis interface.
l Without Abis MUX, IPHC improves transmission efficiency on the Abis interface by
about 33%.
Using FR speech packets as an example, before Abis IPHC is enabled, the sizes of the
IP/UDP header and payload are 28 and 37 bytes, respectively. The size of a packet is 72
bytes. After Abis IPHC is enabled, the size of the IP/UDP header is reduced to 4 bytes
and therefore the size of an IP/UDP packet is reduced to 48 bytes.
Abis IPHC reduces the size of a packet by: (72 – 48)/72 = 33%
l With Abis MUX, IPHC further improves transmission efficiency on the Abis interface
by about 5%.
For example, the size of a packet is 447 bytes after 10 speech packets are multiplexed
using Abis MUX. After IPHC, the size of the packet is further reduced to 423 bytes.
Abis IPHC reduces the size of a packet by: (447 – 423)/447 = 5.4%
7.7 GBFD-118610 UDP MUX for A Transmission

System Capacity
No impact.
Network Performance
The UDP MUX for A Transmission feature improves transmission efficiency on the A
interface.
This feature supports two multiplexing modes:
l Multiplexing mode 1: In this mode, the RTP header is multiplexed without being
compressed.
l Multiplexing mode 2: In this mode, the RTP header is multiplexed and compressed.
More multiplexed frames lead to higher transmission efficiency.

SingleRAN
Figure 7-2 shows the frame format before and after this feature is enabled, using EFR speech
packets with the RTP header being compressed as an example.
Figure 7-2 Frame format before and after UDP MUX for A Transmission is enabled
As shown in the preceding figure, before this feature is enabled, the sizes of the Ethernet
header, IP/UDP header, RTP header, speech type field, and FCS for a frame are 14, 28, 12, 31,
and 4 bytes, respectively. Therefore, the size of a frame is 89 bytes and the total size of 10
frames is 890 bytes.
After this feature is enabled, 10 frames are multiplexed. The sizes of the Ethernet header,
IP/UDP header, multiplexed header, RTP header, speech type field, and FCS for a frame are
reduced to 14, 28, 5, 4, 31, and 4 bytes, respectively. The formula for calculating the total size
of these multiplexed frames is as follows: 14 bytes + 28 bytes + (5 bytes + 4 bytes + 31 bytes)
x 10 + 4 bytes = 446 bytes
After this feature is enabled, transmission efficiency increases from 34.83% to 69.50%.
l Transmission efficiency before the multiplexing: 31/89 = 34.83%

l Transmission efficiency after the multiplexing: 31/44.6 = 69.50%
When there is a bit error, enabling this feature has a negative impact on speech quality. The
impact can be minimized by reducing the value of the parameter related to multiplexing
duration or by reducing the size of the frames to be multiplexed. However, the impact cannot
be eliminated. This feature is not recommended if the BER is higher than 10-6.
7.8 WRFD-050420 FP MUX for IP Transmission

System Capacity
No impact.

SingleRAN
Network Performance
No impact.
7.9 WRFD-050412 UDP MUX for Iu-CS Transmission

System Capacity
No impact.
Network Performance
No impact.

SingleRAN
Description 8 Engineering Guidelines
8 Engineering Guidelines
8.1 FP MUX (for UMTS Only)

This section describes how to deploy the WRFD-050420 FP MUX for IP Transmission
feature in a newly deployed UMTS network. FP MUX is applicable only to the user plane of
the Iub interface that is based on IP transmission. FP MUX does not apply to the GSM or
LTE.
8.1.1 When to Use

It is recommended that FP MUX be activated in the following scenarios:
l The bandwidth of the bearer network is insufficient.
l The transmission performance of the bearer network is good. For the IP bearer network,
the packet loss rate is low; for the SDH/MSTP network, the bit error rate is low.
Since this feature may cause latency and jitter, it is not recommended that this feature be
activated if the bandwidth of the Iub interface is sufficient.
8.1.2 Required Information

None
8.1.3 Planning
8.1.3.1 RF Planning
N/A
8.1.3.2 Network Planning

The Iub interface is based on IP transmission.
8.1.3.3 Hardware Planning

RNC:

SingleRAN
l The FG2a/FG2c/FG2e/GOUa/GOUc/POUc of the BSC6900 supports this feature.

l The FG2c/FG2e/GOUc/EXOUa/EXOUb of the BSC6910 supports this feature.
NodeB:
l The UTRP/UTRPc/WMPT/WMPT of the BTS3900 supports this feature.
8.1.4 Deployment
8.1.4.1 Requirements
l Other features
This feature requires the WRFD-050402 IP Transmission Introduction on Iub Interface
feature.
l NEs
The receive end of IP packets support FP MUX.
l License
The license for the IP Transmission feature has been activated.
Feature ID Feature License NE Sales Unit

Name Control Item
WRFD-05042 FP MUX for FP MUX RNC Erl+Mbps

0 IP
Transmission
8.1.4.2 Data Preparation

Table 8-1 and Table 8-2 list the data to prepare before activating FP MUX.
Table 8-1 Data to prepare before activating FP MUX (RNC)
Parameter Parameter ID Setting Remarks

Name Notes
IP MUX Type MUXTYPE FPMUX MO: IPMUX (No

transmission resource
Max subframe SUBFRAMELEN 352 pools are configured.)/
length[byte] IPPOOLMUX
Maximum Frame MAXFRAMELEN 1031 (Transmission resource
Length[byte] pools are configured.)
These parameters are
Maximum Delay FPTIMER 2 configurable in CME
Time[ms] batch modification
center.

SingleRAN
Table 8-2 Data to prepare before activating FP MUX (NodeB)

Parameter Parameter ID Setting Remarks
Name Notes
IPMUX Switch IPMUXSWITCH ENABLE(E MO: IP Path

Flag nable) These parameters are
configurable in CME
Max Subframe SUBFRAMELEN 127
batch modification
Length
center.
Max Frame FRAMELEN 270
Length
Max Timer TIMER 1
8.1.4.3 Activation
8.1.4.3.1 Using MML Commands

Step 1 Run the RNC MML command ADD IPMUX (when no transmission resource pools are
configured) or ADD IPPOOLMUX (when transmission resource pools are configured) with
MUXTYPE set to FPMUX to activate FP MUX over the Iub interface.
NOTE
You do not need to configure the number of packets to be multiplexed after feature activation. This is
because the RNC selects appropriate subframes within the period specified by the Max Timer
parameter. Subframes that meet the following conditions will be combined into a packet:
l The sending of a subframe is within the time specified by the Max Timer parameter.
l The size of a subframe is less than the value of the Max Subframe Length parameter.
l The total size of the subframes plus 8 is less than or equal to the value of the Max Frame Length
parameter.
Step 2 In RAN15.0 or later versions, run the NodeB MML command ADD IPPATH or MOD
IPPATH to activate FP MUX over the Iub interface on the NodeB side. In versions earlier
than RAN15.0, run the NodeB MML command SET FPMUX to activate FP MUX over the
Iub interface on the NodeB side.
----End
8.1.4.3.2 MML Command Examples

//Activating FP MUX on the RNC side when no transmission resource pools are
configured.
ADD IPMUX: MUXTYPE=FPMUX, ANI=1, PATHID=1, ISQOSPATH=NO, SUBFRAMELEN=352,
MAXFRAMELEN=1031, FPTIMER=2;
//Activating FP MUX on the NodeB side
ADD IPPATH: PATHID=0, CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PT=PPP, PN=0,
JNRSCGRP=ENABLE, RSCGRPID=0, LOCALIP="192.168.11.110", PEERIP="192.168.22.220",
DSCP=20, IPMUXSWITCH=ENABLE, SUBFRAMELEN=128, FRAMELEN=512, TIMER=2;
8.1.4.3.3 Using the CME

This feature can be activated using the CME. This section uses the eNodeB as an example.
For detailed operations, see CME-based Feature Configuration or the CME online help
(press F1 in an active CME window).

SingleRAN
Configuration CME Online Help

Scenario
Configuring a CME Management > CME Guidelines > Getting Started with
single base station the CME > Introduction to Data Configuration Operations
Configure NodeBs CME Management > CME Guidelines > UMTS Application
in batches Management > NodeB Related Operations > Importing and
Exporting NodeB Data for Batch Configuration
8.1.4.4 Activation Observation

Step 1 Run the RNC MML command DSP IPMUX (when no transmission resource pools are
configured) or DSP IPPOOLMUX (when transmission resource pools are configured) to
query the status and performance of the IP packet multiplexing.
Step 2 For RAN15.0 or later, run the NodeB MML command DSP IPPATH to query whether the
value of the IPMUX Switch Flag parameter is Enable for a specified IP path. For versions
earlier than RAN15.0, run the NodeB MML command LST FPMUX to query whether the
value of the IPMUX Switch Flag is Enable for a specified IP path.
----End
8.1.4.5 Deactivation
Step 1 When no transmission resource pools are configured, run the RNC MML command RMV
IPMUX to deactivate the FP MUX for IP Transmission feature on the IP path of the RNC.
When transmission resource pools are configured, run the RNC MML command RMV
IPPOOLMUX to deactivate the FP MUX for IP Transmission feature on the adjacent node.
Step 2 Run the NodeB MML command MOD IPPATH to deactivate the FP MUX for IP
Transmission feature.
----End

//Deactivating FP MUX on the RNC side when no transmission resource pools are
configured
RMV IPMUX: IPMUXINDEX=1;
//Deactivating FP MUX on the RNC side when transmission resource pools are
configured
RMV IPPOOLMUX: IPPOOLMUXINDEX=1;
//Deactivating FP MUX on the NodeB side
MOD IPPATH: PATHID=1, SN=1, PATHTYPE=FIXED, IPMUXSWITCH=DISABLE;

On the CME, set parameters in the following table to deactivate FP MUX. For detailed
instructions, see 8.1.4.3.3 Using the CME.

SingleRAN
Table 8-3 Configuring parameters on the CME
Parameter Name Parameter ID Setting Notes
IP MUX Index IPMUXINDEX (No transmission Remove the

resource pools are configured.)/ corresponding MO
IPPOOLMUXINDEX (Transmission for this parameter.
resource pools are configured.)
IPMUX Switch Flag IPMUXSWITCH Set this parameter to

DISABLE(Disable).
8.1.5 Performance Monitoring

Step 1 Run the RNC MML command DSP IPMUX (when no transmission resource pools are
query the status and performance of the IP packet multiplexing.
Step 2 Run the NodeB MML command DSP IPPATH to query the value of the IPMUX Switch
Flag parameter for a specified IP path.
----End
8.1.6 Parameter Optimization

Generally, the default parameter values are the optimized ones. In some cases, the value of the
SUBFRAMELEN parameter requires to be modified to control the size of the subframe. To
ensure that a specified frame can be multiplexed, set the SUBFRAMELEN parameter to a
value smaller than the size of the specified frame. To prevent a specified frame from being
multiplexed to reduce delay, set the SUBFRAMELEN parameter to a value larger than the
size of this frame.
If the size of the multiplexed frame is greater than the value of the MTU parameter, which can
be set by running the SET ETHPORT command, the multiplexed frame will be fragmented.
To avoid this, modify the value of the MAXFRAMELEN parameter.
The greater the value of the FPTIMER parameter, the higher the multiplexing rate and the
more obvious the delay and jitter.
8.1.7 Possible Issues

N/A
8.2 UDP MUX (for GSM and UMTS Only)

UDP MUX is applicable only to the user plane of the A and Iu-CS interfaces that are based on
IP transmission. This section describes how to deploy the GBFD-118610 UDP MUX for A
Transmission feature in a newly deployed GSM network and how to deploy the
WRFD-050412 UDP MUX for Iu-CS Transmission feature in a newly deployed UMTS
network. UDP MUX does not apply to the LTE.

SingleRAN
8.2.1 When to Use

Use UDP MUX in the following scenarios:
l The IP-based A interface and Iu-CS interface are connected through the bearer network,
of which the bandwidth is insufficient.
l The transmission performance of the bearer network is good. For the IP bearer network,
the packet loss rate is low; for the SDH/MSTP network, the BER is low.
UDP MUX is not recommended if the BER is higher than 10-6 or the transmission delay is
close to the threshold that the A/Iu-CS interface requires for the transmission network QoS.
Since UDP MUX may cause latency and jitter, it is not recommended that UDP MUX be
activated if the BSC/RNC and the CN equipment are located in the same equipment room.

Before you deploy the UDP MUX for A Transmission and UDP MUX for Iu-CS
Transmission features, collect the following information:
l Whether both the BSC/RNC and the CN support this feature

This feature is available only when both the BSC/RNC and the CN support:
– Negotiation about UDP multiplexing
– UDP multiplexing
– UDP multiplexing with the RTP header compressed
l Quality of the transmission network, for example, the BER and transmission delay
This feature is not recommended if the BER is higher than 10-6 or the transmission delay
is close to the threshold that the A interface requires for the transmission network QoS.
8.2.3 Planning
8.2.3.1 RF Planning
N/A

The A and Iu-CS interfaces are based on IP transmission.
Transmission bandwidth must be correctly planned.

Hardware planning for UDP MUX for A Transmission:
l IP over Ethernet
Interface boards configured on the BSC6900: FG2a/FG2c/FG2d/FG2e/GOUa/GOUc/
GOUd
Interface boards configured on the BSC6910: FG2c/FG2d/FG2e/GOUc/GOUd/EXOUa/
EXOUb

SingleRAN
l IP over E1/T1
Interface boards configured on the BSC6900: POUc/PEUa/PEUc
Hardware planning for UDP MUX for Iu-CS Transmission:
l IP over Ethernet
Interface boards configured on the BSC6900: FG2a/FG2c/FG2e/GOUa/GOUc
Interface boards configured on the BSC6910: FG2c/FG2e/GOUc/EXOUa/EXOUb
l IP over E1/T1
Interface board configured on the BSC6900: POUc
8.2.4 Deployment
l Other features
The UDP MUX for A Transmission feature requires GBFD-118602 A over IP and
GBFD-118622 A IP over E1/T1.
The UDP MUX for Iu-CS Transmission feature requires the WRFD-050409 IP
Transmission Introduction on Iu Interface feature.
l NEs
The CN supports UDP MUX.
l License
The licenses for the UDP MUX for A Transmission and UDP MUX for Iu-CS
Transmission features have been activated.
Feature ID Feature License NE Sales Unit
Name Control Item
GBFD-118610 UDP MUX for UDP MUX for BSC Erl

A A
Transmission Transmission
WRFD-05041 UDP MUX for UDP MUX for RNC Erl

2 Iu-CS Iu-CS
Transmission Transmission
l Other requirements
Static IP routing to the local BSC/RNC is configured on the peer device.
The RTCPSWITCH parameter is set to ON(Open) for the UDP MUX. For detailed
operations, see 8.2.4.3 Activation.

Table 8-1 lists the data to prepare before activating UDP MUX.
8.2.4.3 Activation

SingleRAN

l If no transmission resource pools are configured, run the BSC/RNC MML command
ADD IPMUX or MOD IPMUX to activate UDP MUX. Set the IP MUX Type
parameter to UDPMUX and set the following parameters based on the network plan:
Max subframe length[byte], Maximum Frame Length[byte], and Maximum Delay
Time[ms]. To activate UDP MUX for multiple links, run this command for each link
you want to activate.
l If transmission resource pools are configured, run the BSC/RNC MML command ADD
IPPOOLMUX or MOD IPPOOLMUX to activate UDP MUX. Set the IP MUX Type
parameter to UDPMUX and set the following parameters based on the network plan:
Max subframe length[byte], Maximum Frame Length[byte], and Maximum Delay
Time[ms]. To activate UDP MUX for multiple adjacent nodes, run this command for
multiple times.
NOTE
l If no transmission resource pools are configured, IP paths must be configured based on the network
plan. If transmission resource pools are configured, correct adjacent nodes must be configured based
on the network plan.
l The BSC/RNC assigns a default IPMUXINDEX value, but this parameter can also be set manually.
l The RTCP function is enabled. To enable the function for the UDP MUX for A Transmission
feature, run the ADD GCNNODE command or MOD GCNNODE command with RTCPSWITCH
parameter set to ON(Open). To enable the function for the UDP MUX for Iu-CS Transmission
feature, run the ADD UCNNODE command or MOD UCNNODE command with RTCPSwitch set
to ON.

//Activating UDP MUX when no transmission resource pools are configured
ADD IPMUX: MUXTYPE=UDPMUX, ANI=0, PATHID=0, ISQOSPATH=NO, SUBFRAMELEN=352,
MAXFRAMELEN=1031, FPTIMER=2, UDPMUXMODSEND=RTPCOMP, UDPMUXMODRECV=RTPCOMP,
IPMUXINDEX=0;
//Activating UDP MUX when transmission resource pools are configured
ADD IPPOOLMUX: MUXTYPE=UDPMUX, ANI=0, PHB=AF33, SUBFRAMELEN=352,
MAXFRAMELEN=1031, FPTIMER=2, UDPMUXMODSEND=RTPCOMP, UDPMUXMODRECV=RTPCOMP,
IPPOOLMUXINDEX=0;

Set parameters on the CME according to the operation sequence described in 8.2.4.2 Data
Preparation. For instructions on how to perform the CME single configuration, see CME
Single Configuration Operation Guide.

Run the BSC/RNC MML command DSP IPMUX (when no transmission resource pools are
query the statistics and status of the IP packet multiplexing. Check whether the feature has
been activated based on the values of the IPMUX Status, Number of Received MUX
Packets, and Number of Sent MUX Sub-frames parameters.

SingleRAN

Run the BSC/RNC MML command RMV IPMUX (when no transmission resource pools are
configured) or RMV IPPOOLMUX (when transmission resource pools are configured) to
deactivate UDP MUX.

//Deactivating UDP MUX when no transmission resource pools are configured
//Deactivating UDP MUX when transmission resource pools are configured

For instructions on how to perform the CME single configuration, see CME Single
Configuration Operation Guide. Set the parameter in the following table to deactivate UDP
MUX.
Table 8-4 Configuring the parameter on the CME
IP MUX Index IPMUXINDEX (No transmission Remove the MO

resource pools are configured.)/ corresponding to this
IPPOOLMUXINDEX (Transmission parameter.
resource pools are configured.)

Run the BSC/RNC MML command DSP IPMUX (when no transmission resource pools are
query the statistics and status of the IP packet multiplexing. Check the feature status based on
the values of the IPMUX Status, Number of Received MUX Packets, and Number of Sent
MUX Sub-frames parameters.
UDP MUX for Iu-CS Transmission

Generally, the default parameter values are the optimized ones. In some cases, the value of the
SUBFRAMELEN parameter requires to be modified to control the size of the subframe.
If the size of the multiplexed frame is greater than the value of the MTU parameter, which can
be set by running the SET ETHPORT command, the multiplexed frame will be fragmented.
To avoid this, modify the value of the MAXFRAMELEN parameter.
The greater the value of the FPTIMER parameter, the higher the frequency reuse coefficient
and the more obvious the delay and jitter.

SingleRAN
UDP MUX for A Transmission

l If the transmission quality of CS services is poor and the PS data rate is low, you can
infer that bit errors occur. In this situation, it is recommended that parameters listed in
Table 8-5 be set to smaller values, minimizing the impact of high BER.
l If the transmission quality of CS services is favorable and the PS data rate is low, you
can infer that transmission congestion occurs. It is recommended that parameters listed
in Table 8-5 be set to larger values, relieving transmission congestion.
NOTE
Transmission quality of CS services is indicated by the voice quality during calls.

Transmission quality of PS services is indicated by the PS data rate.
Table 8-5 Parameters to be adjusted
NE Parameter
BSC (No transmission resource pools are l FPTIMER

configured.) l MAXFRAMELEN
BSC (Transmission resource pools are l FPTIMER


If transmission bandwidth is not saved after UDP MUX is enabled, perform the following
operations:
Step 1 Observe the traffic volume.
During off-peak hours, few packets can be multiplexed and UDP MUX cannot save
transmission bandwidth. This is not a fault.
Step 2 Verify that SUBFRAMETHRES, TIMEOUT, and PKTLENTHRES are appropriately set to
ensure that packets can be multiplexed.
Step 3 Check the statistics and MUX status.

l In non-transmission pool networking mode, run the DSP IPMUX command to query the
statistics and IP MUX status.
– If IPMUX Status is Enable and the number of sent and received packets increases
after multiplexing, the IP MUX function is normal.
– If IPMUX Status is Enable and the number of sent and received packets does not
increase after multiplexing, check whether the IP MUX function is configured
correctly.
l In transmission pool networking mode, run the DSP IPPOOLMUX command to query
the statistics and value of IPMUX Status.
– If IPMUX Status is Enable and the number of sent and received packets increases
after multiplexing, the IP pool MUX function is normal.

SingleRAN
– If IPMUX Status is Enable and the number of sent and received packets does not
increase after multiplexing, check whether the IP pool MUX function is configured
correctly.
----End
8.3 Abis MUX (for GSM Only)

Abis MUX is applicable only to the user plane of the Abis interface that is based on IP
transmission. This section describes how to deploy the GBFD-118604 Abis MUX feature in a
newly deployed GSM network. Abis MUX does not apply to the UMTS or LTE.
8.3.1 When to Use

In an IP-based RAN backhaul network, Abis MUX is recommended if transmission
bandwidth resources are insufficient and transmission quality is favorable.

Before you deploy Abis MUX, collect information about the quality of the transmission
network, for example, the BER and transmission delay. Abis MUX is not recommended if the
BER is higher than 10-6 or the transmission delay is close to the threshold that the Abis
interface requires for the transmission network QoS.
8.3.3 Planning
8.3.3.1 RF Planning
N/A

The Abis interface is based on IP transmission.

l BSC
– If both the BSC and BTS use IP over E1/T1 transmission, the BSC must be
configured with the following boards:
The BSC6900 must be configured with the PEUa/PEUc/POUc board.
The BSC6910 must be configured with the POUc board.
– If the BTS uses IP over E1/T1 transmission, the BSC uses IP over Ethernet
transmission, and the BSC and BTS are connected using a router, the BSC must be
The BSC6900 must be configured with the FG2a/FG2c/FG2d/FG2e/GOUa/GOUc/
GOUd board.
The BSC6910 must be configured with the FG2c/FG2d/FG2e/GOUc/GOUd/
EXOUa/EXOUb board.
– If both the BSC and BTS use IP over E1/T1 transmission, the BSC must be

SingleRAN
The BSC6900 must be configured with the FG2a/FG2c/FG2d/FG2e/GOUa/GOUc/

GOUd board.
The BSC6910 must be configured with the FG2c/FG2d/FG2e/GOUc/GOUd/
EXOUa/EXOUb board.
l BTS
The BTS3006C and BTS3002E do not support this feature.
8.3.4 Deployment
Table 8-6 Deployment requirements
Aspect Requirement
BSC l If both the BSC and BTS use IP over

E1/T1 transmission, the BSC6900 must
be configured with the PEUa/PEUc/
POUc board. The BSC6910 must be
configured with the POUc board.
l If the BTS uses IP over E1/T1
transmission, the BSC uses IP over
Ethernet transmission, and the BSC and
BTS are connected using a router:
The BSC6900 must be configured with
the FG2a/FG2c/FG2d/FG2e/GOUa/
GOUc/GOUd board.
The BSC6910 must be configured with the
FG2c/FG2d/FG2e/GOUc/GOUd/EXOUa/
EXOUb board.
If both the BSC and BTS use IP over
Ethernet transmission, the BSC must be
FG2a/FG2c/FG2d/FG2e/GOUa/GOUc/
GOUd board.
FG2c/FG2d/FG2e/GOUc/GOUd/EXOUa/
EXOUb board.
BTS The BTS3006C and BTS3002E do not

support this feature.
GSM networking The Abis interface is based on IP

transmission.
MS None
MSC None

SingleRAN
Aspect Requirement
License The license controlling this feature has been

activated. For details on how to activate the
license, see License Management Feature
Parameter Description. For details about
license items, see License Control Item
Description.
Other requirements None

Table 8-1, Table 8-2, and Table 8-7 list the data to prepare before activating Abis MUX.
Table 8-7 Data to prepare before activating Abis MUX (GBTS)

Parameter Name Parameter ID Setting Notes Remarks
Service Type SRVTYPE(BSC690 Network plan MO:

0,BSC6910) BTSABISMUXFLO
W
Max Subframe SUBFRAMETHRE 352
These parameters are
Length S(BSC6910,BSC690
not configurable in
0)
CME batch
Maximum Frame PKTLENTHRES(B 1031 modification center.
Length SC6910,BSC6900)
Maximum Delay TIMEOUT(BSC691 2

Time 0,BSC6900)
Table 8-8 Data to prepare before activating Abis MUX (eGBTS)

Parameter Parameter ID Setting Notes Remarks
Name
IPMUX Switch IPMUXSWITCH ENABLE(Enable) MO: IP Path

Flag These parameters are
Path Type PATHTYPE FIXED(Fixed QoS) configurable in CME
batch modification
center.
8.3.4.3 Activation

l BSC

SingleRAN
– In transmission resource pool networking mode, run the ADD IPPOOLMUX

command on the BSC LMT to add an Abis MUX stream. In this step, set MUX
Type to ABISMUX, and set Adjacent node, PHB, and IP MUX Index to
appropriate values.
– In other networking modes, run the ADD IPMUX command on the BSC LMT to
add an Abis MUX stream. In this step, set IP MUX Type to ABISMUX, and set
Adjacent node ID, IP path ID, and IS QOSPATH to appropriate values.
NOTE
l The BSC can assign a value to IP MUX Index by default. You can also set this parameter based on
actual situations.
l If IS QOSPATH is set to YES(YES), set the PHB parameter to specify the per-hop behavior (PHB)
type for which Abis MUX is to be activated.
l GBTS
On the BSC LMT, run the ADD BTSABISMUXFLOW command with Service Type
set to an appropriate value to add an Abis MUX stream on the BTS side.
l eGBTS
– During initial configuration, run the ADD IPPATH command on the BTS LMT to
add an Abis MUX stream on the eGBTS side. In this step, set Path Type to
FIXED(Fixed QoS) and IPMUX Switch Flag to ENABLE(Enable).
– During data adjustment, run the MOD IPPATH command on the BTS LMT to add
an Abis MUX stream on the eGBTS side. In this step, set Path Type to
FIXED(Fixed QoS) and IPMUX Switch Flag to ENABLE(Enable).

//Activating Abis MUX
//BSC (No transmission resource pools are configured.)
ADD IPMUX: MUXTYPE=ABISMUX, ANI=0, PATHID=0, ISQOSPATH=NO, IPMUXINDEX=0;
//BSC (Transmission resource pools are configured.)
ADD IPPOOLMUX: MUXTYPE=ABISMUX, ANI=0, PHB=BE, IPPOOLMUXINDEX=0;
//GBTS
ADD BTSABISMUXFLOW: IDTYPE=BYID, BTSID=0, SRVTYPE=CSVOICE;
//eGBTS (during initial configuration)
ADD IPPATH: PATHID=0, SN=6, SBT=BASE_BOARD, PT=PPP, JNRSCGRP=DISABLE,
LOCALIP="192.168.11.110", PEERIP="192.168.22.220", PATHTYPE=FIXED, DSCP=20,
IPMUXSWITCH=ENABLE, SUBFRAMELEN=127, FRAMELEN=270, TIMER=1;
//eGBTS (during routine maintenance)
MOD IPPATH: PATHID=0, CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PT=PPP, PN=0,
IPMUXSWITCH=ENABLE;

NOTE
When configuring Abis MUX on the CME, perform a single configuration first, and then perform a
batch modification if required. Configure the parameters of a single object before a batch modification.
Perform a batch modification before logging out of the parameter setting interface.
Step 1 Configure a single object (such as a cell) on the CME.

Step 2 Modify objects in batches on the CME. (CME batch modification center)
To modify objects, such as BSCs, BTSs, GSM cells, TRXs, and GSM external cells, in
batches, click the icon on the CME configuration interface to start the batch modification

SingleRAN
wizard. For instructions on how to perform a batch modification through the CME batch
modification center, press F1 while running the wizard interface to obtain online help.
----End

l BSC and GBTS
– In transmission resource pool networking mode, run the DSP IPPOOLMUX
command on the BSC LMT to query the information about Abis MUX.
Expected result: The value of IPMUX Status is Enable.
– In other networking modes, run the DSP IPMUX command on the BSC LMT to
query the information about Abis MUX.
Expected result: The value of IPMUX Status is Enable.
l eGBTS
On the BTS LMT, run the DSP IPPATH command to query the information about Abis
MUX.
Expected result: The value of IPMUX Switch Flag is Enable.

l BSC
– In transmission resource pool networking mode, run the RMV IPPOOLMUX
command on the BSC LMT to delete the Abis MUX stream.
– In other networking modes, run the RMV IPMUX command on the BSC LMT to
delete the Abis MUX stream.
l GBTS
On the BSC LMT, run the RMV BTSABISMUXFLOW command to delete the Abis
MUX stream from the BTS side.
l eGBTS
On the BTS LMT, run the MOD IPPATH command with IPMUX Switch Flag set to
DISABLE(Disable) to delete the Abis MUX stream from the eGBTS side.

//Deactivating Abis MUX
//BSC (No transmission resource pools are configured.)
//BSC (Transmission resource pools are configured.)
//GBTS
RMV BTSABISMUXFLOW: IDTYPE=BYID, BTSID=0, SRVTYPE=CSVOICE;
//eGBTS
MOD IPPATH: PATHID=0, CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PT=PPP, PN=0,
IPMUXSWITCH=DISABLE;

On the CME, set parameters in the following table to deactivate Abis MUX. For detailed
instructions, see 8.3.4.3.3 Using the CME.

SingleRAN
Table 8-9 Configuring the parameters on the CME (BSC)
IP MUX Index IPMUXINDEX(BSC690 Remove the corresponding MO

0,BSC6910) for this parameter.
IP MUX Index IPPOOLMUXINDEX(B Remove the corresponding MO

SC6900,BSC6910) for this parameter.
Table 8-10 Configuring parameters on the CME (GBTS)
Service Type SRVTYPE(BSC6900,BS Remove the corresponding MO

C6910) for this parameter.
Table 8-11 Configuring the parameter on the CME (eGBTS)
IPMUX Switch Flag IPMUXSWITCH Set this parameter to

DISABLE(Disable).

None

l If transmission quality is poor, for example, if there is a bit error, set parameters listed in
Table 8-12 to small values to improve service quality.
l If transmission quality is good but transmission bandwidth resources are insufficient, set
parameters listed in Table 8-12 to large values to save transmission bandwidth.
NOTE
To monitor IP transmission quality, enable GBFD-118607 IP Performance Monitor.
Table 8-12 Parameters to be adjusted
NE Parameter
BSC (No transmission resource pools are l FPTIMER

BSC (Transmission resource pools are l FPTIMER(BSC6910,BSC6900)

configured.) l MAXFRAMELEN(BSC6910,BSC6900)

SingleRAN
NE Parameter
GBTS l TIMEOUT(BSC6910,BSC6900)
l PKTLENTHRES(BSC6910,BSC6900)
eGBTS l TIMER
l FRAMELEN

If transmission bandwidth is not saved after Abis MUX is enabled, perform the following
operations:
Step 1 Observe the traffic volume.

During off-peak hours, few packets can be multiplexed and Abis MUX cannot save
transmission bandwidth. This is not a fault.
Step 2 Modify the settings of SUBFRAMETHRES, TIMEOUT, and PKTLENTHRES to ensure
that packets can be multiplexed.
----End
8.4 PPP MUX

This section describes engineering guidelines for PPP MUX.
8.4.1 When to Use

PPP MUX is recommended if PPP headers are required to be multiplexed at the PPP/MLPPP
layer to increase transmission capacity.

None
8.4.3 Planning
8.4.3.1 RF Planning
None

IP over E1/T1 is applied to devices at the two ends where PPP MUX is used.

l LTE hardware planning
The eNodeB must be configured with the UMPT board.

SingleRAN
l GSM hardware planning

– To support PPP MUX for a PPP link, the BSC6900 must be configured with the
POUa/UOIa/POUc board.
– To support PPP MUX for an MLPPP group, the BSC6900 must be configured with
the POUa/POUc board.
l UMTS hardware planning
POUa/UOIa/POUc board, and the BSC6910 must be configured with the POUc
board.
the POUa/POUc board, and the BSC6910 must be configured with the POUc board.
– The BTS3900 must be configured with the UMPT/WMPT/UMPT+UTRP/WMPT
+UTRP.
8.4.4 Deployment on the Base Station
Transmission equipment connected to the eNodeB/NodeB supports E1/T1 ports along with
PPP MUX.

This section describes the parameters to prepare based on the network plan, which must be
negotiated with the peer CN or transmission equipment.
PPP MUX for a PPP Link
The following table describes the parameters that must be set in a PPPLNK MO to configure
PPP MUX for a PPP link. The cabinet number, subrack number, and slot number of the PPP
link must be the same as those of the board where the link is located. If a UMPT is used for
transmission, set the subboard type of the PPP link to BASE_BOARD(Base Board).
PPPMUX MUXCP Set this parameter to be

consistent with the setting of
the peer end.
Maximum Length of PPP MAXSFLEN These parameters are valid

Mux Subframe only if the
PPPLNK.MUXCP
Maximum Length of PPP MAXMFLEN parameter is set to
Muxframe ENABLE(Enable). Set this
PPP Muxframe MUXTIME parameter based on the
Combination Timeout network plan.
IP Header Compression IPHC Set this parameter based on

the network plan.

SingleRAN
Protocol Field Compression PFC Set this parameter based on

the network plan.
Address and Control Field ACFC Set this parameter based on

Compression the network plan.
PPP MUX for an MLPPP Group

The following table describes the parameters that must be set in an MPGRP MO to configure
PPP MUX for an MLPPP group. The cabinet number, subrack number, and slot number of the
MLPPP group must be the same as those of the board where the group is located. If a UMPT
is used for transmission, set the subboard type of the PPP link to BASE_BOARD(Base
Board).
PPPMUX MUXCP Set this parameter to be

the peer end.
PPP Mux Subframe Max MAXSFLEN These parameters are valid

Length only if the
MPGRP.MUXCP
Maximum Length of PPP MAXMFLEN parameter is set to
Muxframe ENABLE(Enable). Set this
PPP Muxframe MUXTIME parameter based on the
Combination Timeout network plan.
IP Header Compression IPHC Set this parameter based on

the network plan.
Multi-Class PPP MCPPP Set this parameter based on

the network plan.
MP/MC Header Option MHO These parameters are valid

only if the
MCPPP Class MCCLASS MPGRP.MCPPP parameter
is set to ENABLE(Enable).
Set this parameter based on
the network plan.
The following table describes the parameters that must be set in an MPLNK MO to configure
PPP MUX for an MLPPP link in an MLPPP group. Before adding an MLPPP link to a
specific MLPPP group, ensure that the MLPPP group has been configured. The cabinet
number, subrack number, and slot number of an E1/T1 port must be the same as those of the
board where the port is located. If a UMPT is used for transmission, set the subboard types of
the MLPPP link, MLPPP group, and E1/T1 port to BASE_BOARD(Base Board).

SingleRAN
Link No. PPPLNKN Each MLPPP link in an

MLPPP group must have a
unique link number.
MLPPP Group No. MPGRPN Each MLPPP group must

have a unique group
number.
Timeslot No. TSN Set this parameter based on

the network plan.
Maximum Receive Unit MRU Set this parameter based on

the network plan.
Protocol Field Compression PFC Set this parameter to be

the peer end.
Address and Control Field ACFC Set this parameter to be

Compression consistent with the setting of
the peer end.
Negotiation Time RESTARTTMR Retain the default value.
8.4.4.3 Activation

l PPP MUX for a PPP Link
Run the ADD PPPLNK command to configure PPP MUX for a PPP link.
l PPP MUX for an MLPPP Group
Step 1 Run the ADD MPGRP command to configure PPP MUX for an MLPPP group.
Step 2 Run the ADD MPLNK command to add an MLPPP link to the MLPPP group.
----End

ADD PPPLNK: CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PPPLNKN=0, PN=0, AUTH=NONAUTH,
TSN=TS1-1&TS2-1&TS3-1&TS4-1&TS5-1&TS6-1&TS7-1&TS8-1&TS9-1&TS10-1&TS11-1&TS12-1&TS1
3-1&TS14-1&TS15-1&TS16-1&TS17-1&TS18-1&TS19-1&TS20-1&TS21-1&TS22-1&TS23-1&TS24-1&T
S25-1&TS26-1&TS27-1&TS28-1&TS29-1&TS30-1&TS31-1, LOCALIP="192.168.20.3",
IPMASK="255.255.255.0", PEERIP="192.168.20.75", MUXCP=ENABLE;

ADD MPGRP: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, MPGRPN=0, AUTH=NONAUTH,
LOCALIP="192.168.20.3", IPMASK="255.255.255.0", PEERIP="192.168.20.75",
MUXCP=ENABLE, IPHC=ENABLE, MCPPP=ENABLE, MHO=LONG;
ADD MPLNK: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PPPLNKN=0, MPGRPN=0,
MPGRPSBT=BASE_BOARD, E1T1SRN=0, E1T1SN=7, E1T1SBT=BASE_BOARD, E1T1PN=0,

SingleRAN
S25-1&TS26-1&TS27-1&TS28-1&TS29-1&TS30-1&TS31-1;


Type
Single configuration CME Management > CME Guidelines > Getting Started with
the CME > Introduction to Data Configuration Operations
Batch eGBTS CME Management > CME Guidelines > GSM Application
configuration Management > Base Station Related Operations > Importing
and Exporting eGBTS Data for Batch Reconfiguration
Batch NodeB CME Management > CME Guidelines > UMTS Application
configuration Management > NodeB Related Operations > Importing and
Batch eNodeB CME Management > CME Guidelines > LTE Application
configuration Management > eNodeB Related Operations > Importing and
Exporting eNodeB Data for Batch Configuration

l PPP MUX for a PPP link
Run the DSP PPPLNK command, and then check the command output. If the value of Link
Status is UP(Up), PPP MUX for the PPP link has been activated.
l PPP MUX for an MLPPP group
Run the DSP MPGRP command, and then check the command output. If the value of
MLPPP Group Status is UP(Up), PPP MUX for the MLPPP group has been activated.
N/A
8.4.5 Deployment on the Base Station Controller
Transmission equipment connected to the BSC/RNC supports E1/T1 ports along with PPP
MUX.

SingleRAN

PPP MUX for a PPP Link
PPP MUX for a PPP link. The subrack number and slot number of the PPP link must be the
same as those of the board where the link is located.
PPP mux PPPMUX Set this parameter to be

consistent with the
setting of the peer end.
PPP mux max sub-frame MAXSFLEN These parameters are

length valid only if the
PPPLNK.PPPMUX
PPP mux max mux-frame MAXMFLEN parameter is set to
length ENABLE(Enable). Set
PPP mux framing out- MUXTIME this parameter based on
time[us] the network plan.
IP Header Compression IPHC Set this parameter

based on the network
plan.
Protocol field compress PFC Set this parameter

based on the network
plan.
Address and Control Field ACFC Set this parameter

Compress based on the network
plan.
PPP MUX for an MLPPP Group

PPP MUX for an MLPPP group. The subrack number and slot number of the MLPPP group
must be the same as those of the board where the group is located.
MP type MPTYPE Set this parameter based

MP/MC list head option MHF Set this parameter based


SingleRAN
MC PRI number MCCLASS These parameters are

valid only if the
MPGRP.MPTYPE
parameter is set to
MCPPP. Set this
parameter based on the
network plan.
PPP mux PPPMUX Set this parameter to

ENABLE(Enable).
This parameter value
must be consistent with
the setting of the peer
end.
PPP mux max sub-frame MAXSFLEN These parameters are

length valid only if the
PPPLNK.PPPMUX
PPP mux max mux-frame MAXMFLEN parameter is set to
PPP mux framing out- MUXTIME this parameter based on
Head compress IPHC Set this parameter based

Protocol field compress PFC Set this parameter based

Address and Control Field ACFC Set this parameter based

Compress on the network plan.
PPP MUX for an MLPPP link in an MLPPP group. Before adding an MLPPP link to a
specific MLPPP group, ensure that the MLPPP group has been configured. The subrack
number and slot number of an E1/T1 port must be the same as those of the board where the
port is located.
MP Group No. MPGRPN Each MLPPP group

must have a unique
group number.
PPP sub-link No. PPPLNKN Each MLPPP link in an

MLPPP group must
have a unique link
number.

SingleRAN
Bearing time slot TSBITMAP Set this parameter based

Sub-protocol negotiate out RESTARTTMR Retain the default value.

time[S]
Keep-alive timer length[S] KEEPALIVE Retain the default value.
CRC check mode FCSTYPE Retain the default value.
All parameters described in this section are not configurable in the CME batch modification
center.
8.4.5.3 Activation

See 8.4.4.3.1 Using MML Commands.

ADD PPPLNK: SRN=0, SN=21, BRDTYPE=POUc, PPPLNKN=0, DS1=0,
TSBITMAP=TS1-1&TS2-1&TS3-1&TS4-1&TS5-1&TS6-1&TS7-1&TS8-1&TS9-1&TS10-1&TS11-1&TS12-
1&TS13-1&TS14-1&TS15-1&TS16-1&TS17-1&TS18-1&TS19-1&TS20-1&TS21-1&TS22-1&TS23-1&TS2
4-1&TS25-1&TS26-1&TS27-1&TS28-1&TS29-1&TS30-1&TS31-1, BORROWDEVIP=NO,
LOCALIP="192.168.20.75", MASK="255.255.255.0", PEERIP="192.168.20.3",
PPPMUX=Enable, AUTHTYPE=NO_V, FLOWCTRLSWITCH=ON, ERRDETECTSW=OFF, OPSEPFLAG=OFF;

ADD MPGRP: SRN=0, SN=21, BRDTYPE=POUc, MPGRPN=0, MPTYPE=MCPPP, BORROWDEVIP=NO,
LOCALIP="192.168.20.75", MASK="255.255.255.0", PEERIP="192.168.20.3", MHF=LONG,
PPPMUX=Enable, FLOWCTRLSWITCH=ON, AUTHTYPE=NO_V, ERRDETECTSW=OFF,
ANTIERRFLAG=OFF, OPSEPFLAG=OFF;
ADD MPLNK: SRN=0, SN=21, BRDTYPE=POUc, MPGRPN=0, PPPLNKN=0, DS1=0,
TSBITMAP=TS1-1&TS2-1&TS3-1&TS4-1&TS5-1&TS6-1&TS7-1&TS8-1&TS9-1&TS10-1&TS11-1&TS12-
1&TS13-1&TS14-1&TS15-1&TS16-1&TS17-1&TS18-1&TS19-1&TS20-1&TS21-1&TS22-1&TS23-1&TS2
4-1&TS25-1&TS26-1&TS27-1&TS28-1&TS29-1&TS30-1&TS31-1;


See 8.4.4.4 Activation Observation.
N/A

SingleRAN

None

None

None
8.5 IPHC
This section describes engineering guidelines for IPHC.
8.5.1 When to Use

Before using IPHC, you must ensure that the base station is configured with the E1/T1 port.
IPHC is recommended if IP headers are required to be compressed to reduce transmission
overhead.
Abis IPHC applies to the following scenarios:
l In scenarios where E1 resources are insufficient, use the following functions or features
in a descending order of priority to save transmission resources: VAD, Abis MUX, Abis
IPHC, and local switching. If bandwidth requirements still cannot be met after VAD or
Abis MUX is used, use Abis IPHC.
NOTE
Use of the local switching function must be permitted by the operator because the function involves
lawful interception.
l High-BER scenarios, such as microwave transmission on BSCs in a desert. The
instantaneous BER may be larger than 1e-6 due to large temperature differences during a
day and a harsh environment. In these scenarios, it is recommended that IPHC be
enabled to improve transmission efficiency instead of Abis MUX. This is because Abis
MUX increases the datagram size, and therefore increases the packet loss rate. As a
result, speech quality deteriorates in high-BER scenarios. Unlike Abis MUX, IPHC
reduces datagram size, and therefore decreases the packet loss rate. As a result, speech
quality is improved.
l When TDM transmission is converted to IP over E1 transmission or IP over E1
transmission is deployed, the bandwidth is limited. In this scenario, it is recommended
that IPHC be enabled to improve transmission efficiency. Abis MUX can be enabled
together with IPHC and this further improves transmission efficiency by about 5%.
l In scenarios where BTSs are cascaded in IP over E1 mode and transmission bandwidth
between BTSs is limited, perform IPHC on the MP/PPP links between the BTSs.
Iub IPHC applies to the following scenarios:
l E1 resources are insufficient.
l High-BER scenarios, such as microwave transmission on RNCs in a desert. The
instantaneous BER may be larger than 1e-6 due to large temperature differences during a

SingleRAN
day and a harsh environment. In these scenarios, it is recommended that IPHC be

enabled to improve transmission efficiency instead of FP MUX. This is because FP
MUX increases the datagram size, and therefore increases the packet loss rate. As a
result, speech quality deteriorates in high-BER scenarios. Unlike FP MUX, IPHC
reduces datagram size, and therefore decreases the packet loss rate. As a result, speech
quality is improved.
l In scenarios where NodeBs are cascaded in IP over E1 mode and transmission
bandwidth between NodeBs is limited, perform IPHC on the MP/PPP links between the
NodeBs.

l If both the BSC and BTS use IP over E1/T1 transmission, the BSC and the BTS must
support the Abis IPHC feature.
l If the BTS uses IP over E1/T1 transmission, the BSC uses IP over Ethernet transmission,
and the BSC and BTS are connected using a router, the router and the BTS must support
the Abis IPHC feature.
NOTE
The BTS allows compression of non-TCP packets (UDP packets). It does not allow compression of TCP
and non-TCP packets simultaneously or compression of RTP packets. When the BTS is interconnected
to a router, the router allows compression of only non-TCP packets (UDP packets).
Collect information about the BTS traffic model and Abis link bandwidth to determine
whether to enable this feature based on the formula for calculating bandwidth. This is because
this feature is used only if bandwidth requirements still cannot be met after VAD or Abis
MUX is used.
8.5.3 Planning
8.5.3.1 RF Planning
None

IP over E1/T1 is applied to devices at the two ends where IPHC is used.
Transmission bandwidth must be correctly planned.
The Abis IPHC feature applies to the following networking scenarios:
l IP over E1 end-to-end scenario: The BTS negotiates IPHC parameters with the BSC.
IPHC is enabled on both the BTS and the BSC to perform bidirectional compression.
Figure 8-1 IP over E1 end-to-end scenario

SingleRAN
l IP over FE/GE transmission from the BSC to a router and IP over E1 transmission from
the router to the BTS: The BTS negotiates IPHC parameters with the router. The router
supports UDP datagram header compression implemented by IPHC. This saves
transmission resources between the BTS and the router.
Figure 8-2 Conversion from IP over E1 to IP over FE/GE
l BTS cascading in IP over E1 mode: Cascaded BTSs perform IPHC compression and
decompression on datagram flows and passerby datagram flows.
Figure 8-3 BTS cascading in IP over E1 mode
The UMTS networking scenarios are the same as GSM networking scenarios.

l LTE hardware planning
The eNodeB must be configured with the UMPT board. The LMPT board does not support
IPHC.
BSC:
– If both the BSC and BTS use IP over E1/T1 transmission, the BSC6900/BSC6910
must be configured with the POUc board.
NOTE
The PEU board on the BSC does not support the Abis IPHC feature.
– If the BTS uses IP over E1/T1 transmission, the BSC uses IP over Ethernet
transmission, and the BSC and BTS are connected using a router, the BSC6900
must be configured with the FG2a/FG2c/FG2d/FG2e/GOUa/GOUc/GOUd board
and the BSC6910 must be configured with the FG2c/FG2d/FG2e/GOUc/GOUd/
EXOUa/EXOUb board.
BTS:
– For the GBTS, the GTMUb or GTMUc board must be configured on 3900 series
base stations except the BTS3900B and BTS3900E.
– The DPTU board must be configured on the BTS3012 and BTS3012AE.
– The eGBTS must be configured with the UTRP/UMPT/GTMUb/GTMUc board.
The router must support IPHC.

SingleRAN

– RNC:
To support PPP MUX for a PPP link, the BSC6900 must be configured with the
PEUa/PEUc/POUa/UOIa/POUc board.
To support PPP MUX for an MLPPP group, the BSC6900 must be configured with
the PEUa/PEUc/POUa/POUc board.
– NodeB:
The BTS3900 must be configured with the UTRP, UMPT, and WMPT boards.
8.5.4 Deployment on the eNodeB/NodeB/eGBTS
Transmission equipment connected to the eNodeB/NodeB/eGBTS supports IP over E1/T1 and
IPHC.
The license controlling this feature has been activated. For details on how to activate the
license, see License Management Feature Parameter Description. For details about license
items, see License Control Item Description.
If the base station connects to a router in IP over E1 mode, the router must support IPHC.

IPHC for a PPP Link
IPHC for a PPP link. The cabinet number, subrack number, and slot number of the PPP link
must be the same as those of the board where the link is located. If a UMPT is used for
Link No. PPPLNK.PPPLNKN Each PPP link must have a unique

link number.
Port No. PPPLNK.PN Set this parameter based on the

actual connection and the peer
network device configuration.
Authentication Type PPPLNK.AUTH The setting of this parameter must

be consistent with that in the peer
network device.
User Name PPPLNK.UN These parameters are valid only if

the PPPLNK.AUTH parameter is
not set to NONAUTH(No
Authentication). The setting of
this parameter must be consistent

SingleRAN
Password PPPLNK.PWD with the peer network

configuration.
Time Slot No. PPPLNK.TSN The setting of this parameter must

network device.
Local IP PPPLNK.LOCALIP Set this parameter based on the

network plan.
Mask PPPLNK.IPMASK Set this parameter based on the

network plan.
Peer IP PPPLNK.PEERIP Set this parameter based on the

network plan.
PPPMUX PPPLNK.MUXCP The setting of this parameter must

network device.
IP Header PPPLNK.IPHC Set this parameter to ENABLE

Compression on local and peer ends.
IPHC SubOption PPPLNK.IPHCSUBOPT Set this parameter if the peer

device needs to negotiate about
the setting of this parameter with
the local device.
Maximum Receive PPPLNK.MRU Set this parameter based on the

Unit network plan.
Protocol Field PPPLNK.PFC The setting of this parameter must

Compression be consistent with that in the peer
network device.
Address and Control PPPLNK.ACFC The setting of this parameter must

Field Compression be consistent with that in the peer
network device.
IPHC for an MLPPP Group

IPHC for an MLPPP group. The cabinet number, subrack number, and slot number of the
MLPPP group must be the same as those of the board where the group is located. If a UMPT
is used for transmission, set the subboard type of the PPP link to BASE_BOARD(Base
Board).
Group No. MPGRP.MPGRPN Each MLPPP group must have a

unique group number.

SingleRAN
Authentication Type MPGRP.AUTH The setting of this parameter must

network device.
User Name MPGRP.UN These parameters are valid only if

the MPGRP.AUTH parameter is
Password MPGRP.PWD not set to NONAUTH(No
Authentication). The setting of
this parameter must be consistent
with that in the peer network
device.
Local IP MPGRP.LOCALIP Set this parameter based on the

network plan.
Mask MPGRP.IPMASK Set this parameter based on the

network plan.
Peer IP MPGRP.PEERIP Set this parameter based on the

network plan.
MLPPP Fragment MPGRP.FRAGSIZE Set this parameter based on the

Size network plan.
PPPMUX MPGRP.MUXCP The setting of this parameter must

network device.
IP Header MPGRP.IPHC The setting of this parameter must

Compression be consistent with that in the peer
network device.
IPHC SubOption MPGRP.IPHCSUBOPT Set this parameter if the peer

device needs to negotiate about
the setting of this parameter with
the local device.
Multi-Class PPP MPGRP.MCPPP The setting of this parameter must

network device.
IPHC for an MLPPP link in an MLPPP group. Before adding an MLPPP link to a specific
MLPPP group, ensure that the MLPPP group has been configured. The cabinet number,
subrack number, and slot number of an E1/T1 port must be the same as those of the board
where the port is located. If a UMPT is used for transmission, set the subboard types of the
MLPPP link, MLPPP group, and E1/T1 port to BASE_BOARD(Base Board).

SingleRAN
Link No. MPLNK.PPPLNKN Each MLPPP link in an MLPPP

group must have a unique link
number.
MLPPP Group No. MPLNK.MPGRPN Each MLPPP group must have a

unique group number.
Timeslot No. MPLNK.TSN Set this parameter based on the

network plan.
Maximum Receive MPLNK.MRU Set this parameter based on the

Unit network plan.
Protocol Field MPLNK.PFC Set this parameter to

Compression DISABLE(Disable), which must
be the same as that of the peer
end.
Address and Control MPLNK.ACFC Set this parameter to

Field Compression DISABLE(Disable), which must
be the same as that of the peer
end.
Negotiation Time MPLNK.RESTARTTMR Retain the default value.
8.5.4.3 Activation
For Newly Deployed Base Stations

l IPHC for a PPP link
Run the ADD PPPLNK command to configure IPHC for a PPP link.
l IPHC for an MLPPP group
Step 1 Run the ADD MPGRP command to configure IPHC for an MLPPP group.
----End
For Existing Base Stations
NOTICE
Setting the IPHC parameter in this step will cause the base station to re-initiate a negotiation
with the base station controller or router to establish a PPP link or an MLPPP group. The
negotiation may cause mute voices or interrupt data transmission for less than 3s.

SingleRAN
Run the MOD PPPLNK or MOD MPGRP command with IPHC set to ENABLE(Enable).
Set IPHCSUBOPT to ENABLE(Enable) if the peer device needs to negotiate about the
setting of this parameter with the local device.
For newly deployed base stations

S25-1&TS26-1&TS27-1&TS28-1&TS29-1&TS30-1&TS31-1, LOCALIP="192.168.20.3",
IPMASK="255.255.255.0", MUXCP=DISABLE, IPHC=ENABLE;

LOCALIP="10.10.10.10", IPMASK="255.255.255.0", MUXCP=DISABLE, IPHC=ENABLE,
MCPPP=ENABLE, MHO=LONG;
ADD MPLNK: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, PPPLNKN=0, MPGRPN=0, E1T1SRN=0,
E1T1SN=7, E1T1SBT=BASE_BOARD, E1T1PN=0,
S25-1&TS26-1&TS27-1&TS28-1&TS29-1&TS30-1&TS31-1;
For existing base stations

MOD PPPLNK: CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PPPLNKN=0, PN=0, IPHC=ENABLE;

MOD MPGRP: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, MPGRPN=0, IPHC=ENABLE;


Type

SingleRAN

Step 1 Check the activation status.
Run the DSP PPPLNK command, and then check the command output. If the value of
Link Status is UP(Up), IPHC has been activated.
MLPPP Group Status is UP(Up), IPHC has been activated.
Step 2 Observe the transmit flow during a call.

l If the BSC and the BTS are connected using PPP or MP links, monitor the transmit flow
by configuring Realtime Bandwidth. For details, see "Monitoring Transmission
Resources" in BSC6900 LMT User Guide or BSC6910 LMT User Guide.
l If the BSC and the BTS are connected using a router, obtain the transmit flow from the
transmission device.
Expected result: When the traffic volume is constant, the transmit flow when IPHC is set to
ENABLE(ENABLE) is less than the transmit flow when IPHC is set to
DISABLE(DISABLE).
----End

Run the MOD PPPLNK or MOD MPGRP command with IPHC set to
DISABLE(Disable).

MOD PPPLNK: CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PPPLNKN=0, PN=0, IPHC=DISABLE;

MOD MPGRP: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, MPGRPN=0, IPHC=DISABLE;

The method of using the CME to deactivate this feature is the similar to that of using the
CME to activate this feature. For details, see 8.5.4.3.3 Using the CME.
8.5.5 Deployment on the GBTS
l Transmission equipment connected to the GBTS supports IP over E1/T1 and IPHC.
l The license controlling this feature has been activated. For details on how to activate the
license, see License Management Feature Parameter Description. For details about
license items, see License Control Item Description.

SingleRAN
l If the base station connects to a router in IP over E1 mode, the router must support
IPHC.
Table 8-13 Data to prepare before activating Abis IPHC (GBTS) (related MOs:
BTSPPPLNK and BTSMPGRP)
Parameter Parameter ID Setting Notes

Name
IP Header BTSPPPLNK.IPHC(BSC6910,BSC6900) Set this parameter to

Compression ENABLE(Enable).
IP Header BTSMPGRP.IPHC(BSC6900,BSC6910) Set this parameter to

Compression ENABLE(Enable).
Table 8-14 Data to prepare before activating Abis IPHC (BSC) (related MO: PPPLNK or
MPGRP)
Parameter Parameter ID Setting Notes

Name
Head PPPLNK.IPHC(BSC6910,BSC6900) Set this parameter to UDP/

compress IP_HC(UDP/IP_HC).
Head MPGRP.IPHC(BSC6900,BSC6910) Set this parameter to UDP/

compress IP_HC(UDP/IP_HC).
center.
8.5.5.3 Activation
For Newly Deployed Base Stations

Run the ADD BTSPPPLNK command to configure IPHC for a PPP link.
Step 1 Run the ADD BTSMPGRP command to configure IPHC for an MLPPP group.
Step 2 Run the ADD BTSMPLNK command to add an MLPPP link to the MLPPP group.
----End

SingleRAN
For Existing Base Stations
NOTICE
Run the ADD BTSPPPLNK or ADD BTSMPGRP command with IPHC set to
ENABLE(Enable).
For newly deployed base stations

ADD BTSPPPLNK: IDTYPE=BYID, BTSID=200, PPPLNKN=0, PN=0, CN=0, SRN=0, SN=6,
TSBITMAP=TS1-1&TS2-1&TS3-1&TS4-1&TS5-1&TS6-1&TS7-1&TS8-1&TS9-1&TS10-1&TS11-1&T
S12-1&TS13-1&TS14-1&TS15-1&TS16-1&TS17-1&TS18-1&TS19-1&TS20-1&TS21-1&TS22-1&TS
23-1&TS24-1&TS25-1&TS26-1&TS27-1&TS28-1&TS29-1&TS30-1&TS31-1,
AUTHTYPE=NO_V, IPHC=ENABLE;

ADD BTSMPGRP: IDTYPE=BYID, BTSID=200, MPGRPN=0, CN=0, SRN=0, SN=6,
MPSWITCH=ENABLE, AUTHTYPE=NO_V, IPHC=ENABLE;
For existing base stations

MOD BTSPPPLNK: IDTYPE=BYID, BTSID=200, PPPLNKN=0, IPHC=ENABLE;

MOD BTSMPGRP: IDTYPE=BYID, BTSID=200, MPGRPN=0, IPHC=ENABLE;


Step 1 Run the BSC MML command DSP BTSPPPLNK or DSP BTSMPGRP, and then check the
command output.
Expected result: The value of IPHC Negotiation Result reported by the BTS is ENABLE.

SingleRAN
DISABLE(DISABLE).
----End

Run the MOD BTSPPPLNK or MOD BTSMPGRP command with IPHC set to
DISABLE(Disable).

MOD BTSPPPLNK: IDTYPE=BYID, BTSID=200, PPPLNKN=0, IPHC= DISABLE;

MOD BTSMPGRP: IDTYPE=BYID, BTSID=200, MPGRPN=0, IPHC= DISABLE;

Transmission equipment connected to the base station controller supports E1/T1 ports along
with IPHC.

IPHC for a PPP Link
IPHC for a PPP link. The subrack number and slot number of the PPP link must be the same
as those of the board where the link is located.
Link No. PPPLNK.PPPLNKN Each PPP link must have a

unique link number.
E1T1 port No. PPPLNK.DS1 Set this parameter based on the

actual connection and the peer
configuration.

SingleRAN
Bearing time slot PPPLNK.TSBITMAP Set this parameter to be

the peer end.
Borrow DevIP PPPLNK.BORROWDEVI Set this parameter based on the

P network plan.
Borrowed device IP PPPLNK. DEVIP This parameter is valid only if

address the
PPPLNK.BORROWDEVIP
parameter is not set to
YES(YES).
Local IP address PPPLNK.LOCALIP Set this parameter based on the

network plan.
Subnet mask PPPLNK. MASK Set this parameter based on the

network plan.
Peer IP address PPPLNK.PEERIP Set this parameter based on the

network plan.
Head compress PPPLNK.IPHC Set this parameter to UDP/

IP_HC(UDP/IP_HC) or
RTP/UDP/IP_HC(RTP/UDP/
IP_HC). This parameter value
must be consistent with the
setting of the peer end.
Protocol field compress PPPLNK.PFC Set this parameter to be

the peer end.
Address and Control Field PPPLNK.ACFC Set this parameter to be

Compress consistent with the setting of
the peer end.
PPP mux PPPLNK.PPPMUX Set this parameter to be

the peer end.
Validate protocol type PPPLNK.AUTHTYPE Set this parameter to be

the peer end.
Validate user name PPPLNK.AUTHNAME These parameters are valid

only if the
Validate password PPPLNK.AUTHPWD PPPLNK.AUTHNAME
Validate mode PPPLNK.AUTHMODE parameter is not set to
NO_V(NO_V). Set this
parameter to be consistent with
the setting of the peer end.

SingleRAN
IPHC for an MLPPP Group

IPHC for an MLPPP group. The subrack number and slot number of the MLPPP group must
be the same as those of the board where the group is located.
MP Group No. MPGRP.MPGRPN Set this parameter based on

the network plan.
MP type MPGRP.MPTYPE Set this parameter to be

the peer end.
Borrow DevIP MPGRP.BORROWDEVIP Set this parameter based on

the network plan.
Borrowed device IP MPGRP.DEVIP This parameter is valid only if

address the
MPGRP.BORROWDEVIP
YES(YES).
Local IP address MPGRP.LOCALIP Set this parameter based on

the network plan.
Subnet mask MPGRP.MASK Set this parameter based on

the network plan.
MP/MC list head option MPGRP.MHO Set this parameter based on

the network plan.
MC PRI number MPGRP.MCCLASS This parameter is valid only if

the MPGRP.MPTYPE
parameter is set to MCPPP.
Head compress MPGRP.IPHC Set this parameter to UDP/

IP_HC(UDP/IP_HC) or
RTP/UDP/
IP_HC(RTP/UDP/IP_HC).
This parameter value must be
the peer end.
Protocol field compress MPGRP.PFC Set this parameter to be

the peer end.
Address and Control Field MPGRP.ACFC Set this parameter based on

Compress the network plan. Set this
parameter to be consistent
with the setting of the peer
end.

SingleRAN
PPP mux MPGRP.PPPMUX Set this parameter to be

the peer end.
PPP mux max sub-frame MPGRP.MAXSFLEN These parameters are valid

length only if the MPGRP.PPPMUX
parameter is set to
PPP mux max mux-frame MPGRP.MAXMFLEN ENABLE(Enable). Set this
length parameter based on the
PPP mux framing out- MPGRP.MUXTIME network plan.
time[us]
IPHC for an MLPPP link in an MLPPP group. Before adding an MLPPP link to a specific
MLPPP group, ensure that the MLPPP group has been configured. The subrack number and
slot number of an E1/T1 port must be the same as those of the board where the port is located.
MP Group No. MPLNK.MPGRPN Each PPP link must have a

unique link number.
PPP sub-link No. MPLNK.PPPLNKN Each PPP link must have a

unique link number.
E1T1 port No. MPLNK.DS1 Set this parameter based on

the actual connection and the
peer configuration.
Bearing time slot MPLNK.TSBITMAP Set this parameter to be

the peer end.
CRC check mode MPLNK.FCSTYPE Set this parameter based on

the network plan.
center.
8.5.6.3 Activation
For Newly Deployed Base Station Controllers

Run the ADD PPPLNK command to configure IPHC for a PPP link.

SingleRAN
Step 1 Run the ADD MPGRP command to configure IPHC for an MLPPP group.
----End
NOTE
If the BSC works in IP over FE/GE mode:

l Enable the IPHC function for the routers and then for the BTSs.
l Do not enable the IPHC function for the BSC.
l Enable the routers to support the IPHC function only for UDP packet headers.
For Existing Base Station Controllers
NOTICE
Run the MOD PPPLNK or MOD MPGRP command with Subrack No. and Slot No. set to
the numbers of the subrack and slot where the POUc board is located and Head Compress be
set to UDP/IP_HC(UDP/IP_HC).
NOTE
If the BSC works in IP over FE/GE mode:

l Enable the IPHC function for the routers and then for the BTSs.
l Do not enable the IPHC function for the BSC.
l Enable the routers to support the IPHC function only for UDP packet headers.
For newly deployed base station controllers

23-1&TS24-1&TS25-1&TS26-1&TS27-1&TS28-1&TS29-1&TS30-1&TS31-1, BORROWDEVIP=NO,
LOCALIP="5.5.5.5", MASK="255.255.255.0", PEERIP="5.5.5.6", IPHC=RTP/UDP/
IP_HC, PPPMUX=Disable, AUTHTYPE=NO_V, FLOWCTRLSWITCH=ON, ERRDETECTSW=OFF,
OPSEPFLAG=OFF;

ADD MPGRP: SRN=0, SN=26, BRDTYPE=POUc, MPGRPN=0, MPTYPE=MCPPP,
BORROWDEVIP=NO, LOCALIP="9.9.9.99", MASK="255.255.255.0", PEERIP="9.9.9.98",
MHF=LONG, IPHC=UDP/IP_HC, PPPMUX=Disable, FLOWCTRLSWITCH=ON, AUTHTYPE=NO_V,
ERRDETECTSW=OFF, ANTIERRFLAG=OFF, OPSEPFLAG=OFF;

SingleRAN
For existing base station controllers

MOD PPPLNK: SRN=0, SN=26, BRDTYPE=POUc, PPPLNKN=0, IPHC=UDP/IP_HC;

MOD MPGRP: SRN=0, SN=26, BRDTYPE=POUc, MPGRPN=0, IPHC=UDP/IP_HC;


Step 1 Run the DSP PPPLNK or DSP MPGRP command, and then check the command output.
Expected result: The value of IPHC Negotiation Result reported by the BTS is ENABLE.

DISABLE(DISABLE).
----End

Run the MOD PPPLNK or MOD MPGRP command with Subrack No. and Slot No. set to
the numbers of subrack and slot where the POUc board is located and Head Compress be set
to No_HC(No_HC).

MOD PPPLNK: SRN=0, SN=26, BRDTYPE=POUc, PPPLNKN=0, IPHC=No_HC;

MOD MPGRP: SRN=0, SN=26, BRDTYPE=POUc, MPGRPN=0, IPHC=No_HC;

Set parameters on the CME according to the operation sequence described in Table 8-15. For
instructions on how to perform the CME single configuration, see CME Single
Configuration Operation Guide.

SingleRAN
Table 8-15 Configuring the parameters on the CME (BSC)

Parameter ID Parameter Setting Notes
Name
PPPLNK.IPHC(BSC6900,BSC6910) Head compress Set this parameter to

DISABLE(Disable).
MPGRP.IPHC(BSC6900,BSC6910) IP Header Set this parameter to

Compression DISABLE(Disable).

None

None

Abis IPHC is based on PPP. If Abis IPHC negotiation fails, link connectivity and performance
are not affected, but transmission bandwidth cannot be saved.
Possible faults may occur in the following scenarios:
Both the BSC and BTS Use IP over E1/T1 Transmission.
Figure 8-4 BSC and BTS using IP over E1/T1 transmission
l During PPP/MP initial negotiation, perform the following operations:
Step 1 On the BSC LMT, run the DSP PPPLNK or DSP MPGRP command to check whether the
IPHC negotiation is successful.
Expected result: The Code compress type value is non-TCP code. This indicates that the
negotiation is successful.
Step 2 For the GBTS, run the DSP BTSPPPLNK or DSP BTSMPGRP command on the BSC LMT
to check whether the IPHC negotiation is successful.
Expected result: The IPHC Negotiation Result value is Enabled. This indicates that the
negotiation is successful.
Step 3 For the eGBTS, run the DSP PPPLNK or DSP MPGRP command on the BTS LMT to
check whether the IPHC negotiation is successful.

SingleRAN
Expected result: The value of IPHC Negotiation Result is ENABLE(Enable). This indicates
that the negotiation is successful.
Step 4 On the BSC LMT, run the DSP PPPLNK or DSP MPGRP command to check whether the
IPHC negotiation parameters are configured correctly.
Expected result:
l Max CID for non-TCP Compression: negotiated value (default value: 767)
l Max quantity of code sent Continuous: 256
l Max space time of sending full head code: 1
l Size of max head which can be compressed: 28
If the negotiation fails, change the configuration on the BSC or the BTS to ensure that
the parameters are configured correctly. If the negotiation still fails, contact Huawei
technical support engineers.
----End
l After PPP/MP/IPHC negotiation, run the DSP PPPLNK or DSP MPGRP command on
the BSC LMT. In the command output, check the following information:
– Number of packets sent that were not compressed
– Number of IPv4/UDP compressed header packets which are compressed
successfully by sender
– Number of IPv4/UDP full header packets sent by sender
– Number of IPv6/UDP compressed header packets which are compressed
successfully by sender
– Number of IPv6/UDP full header packets sent by sender
– Number of IPv4/UDP full header packets which are decompressed successfully by
receiver
– Number of IPv4/UDP compressed header packets which are decompressed
successfully by receiver
– Number of IPv6/UDP full header packets which are decompressed successfully by
receiver
– Number of IPv6/UDP compressed header packets which are decompressed
successfully by receiver
If the preceding information is not measured, contact Huawei Customer Service
Center.
The BTS Uses IP over E1/T1 Transmission, the BSC Uses IP over Ethernet
Transmission, and the BSC and BTS Are Connected Using a Router.
Figure 8-5 The BTS using IP over E1/T1 transmission, the BSC using IP over Ethernet
transmission, and the BSC and BTS connected using a router

SingleRAN
l In the PPP or MP initial negotiation phase:

– For the GBTS, run the DSP BTSPPPLNK or DSP BTSMPGRP command on the
BSC LMT to check whether the IPHC negotiation is successful.
Expected result: The IPHC Negotiation Result value is Enabled. This indicates
that the negotiation is successful.
– For the eGBTS, run the DSP PPPLNK or DSP MPGRP command on the BTS
LMT to check whether the IPHC negotiation is successful.
Expected result: The value of IPHC Negotiation Result is ENABLE(Enable).
This indicates that the negotiation is successful.
If the negotiation fails, change the configuration on the BSC, BTS, or router to ensure that the
parameters are configured correctly. If the negotiation still fails, contact Huawei technical
support engineers.
8.6 PPPHC
This section describes engineering guidelines for PPPHC. PPPHC is used to compress PPP
headers. The ACFC and PFC techniques can be used together or separately.
8.6.1 When to Use

Before using PPPHC, you must ensure that the base station is configured with the E1/T1 port.
PPPHC is recommended if the address, control, and protocol fields in PPP headers are
required to be compressed to improve transmission efficiency.

None
8.6.3 Planning
8.6.3.1 RF Planning
None

IP over E1/T1 is applied to devices at the two ends where PPPHC is used.

l LTE hardware planning to enable LBFD-003004/TDLBFD-003004 Compression &
Multiplexing over E1/T1
The eNodeB must be configured with the UMPT board. The LMPT board does not
support PPPHC.
PEUa/PEUc/POUc board and the BSC6910 must be configured with the POUc
board.

SingleRAN
the PEUa/PEUc/POUc board and the BSC6910 must be configured with the POUc
board.
– The eGBTS must be configured with the UTRP/UMPT/GTMUb/GTMUc board.
– For the GBTS, the 3012 series base stations must be configured with the DPTU
board and the 3900 series base stations must be configured with the GTMUb or
GTMUc board.
PEUa/PEUc/POUa/UOIa/POUc board.
the PEUa/PEUc/POUa/POUc board.
– The NodeB must be configured with the UTRP, UMPT, and WMPT boards.
Transmission equipment connected to the eNodeB/NodeB/eGBTS supports E1/T1 ports along
with PPPHC.

PPPHC for a PPP Link
PPPHC for a PPP link. The cabinet number, subrack number, and slot number of the PPP link
must be the same as those of the board where the link is located. If a UMPT is used for
Link No. PPPLNK.PPPLNKN Each PPP link must have a

unique link number.
Port No. PPPLNK.PN Set this parameter based on

the actual connection and
the peer configuration.
Authentication Type PPPLNK.AUTH Set this parameter to be

the peer end.
User Name PPPLNK.UN These parameters are valid

only if the PPPLNK.AUTH
NONAUTH(No
Authentication). Set these

SingleRAN
Password PPPLNK.PWD parameters to be consistent

end.
Time Slot No. PPPLNK.TSN Set this parameter to be

the peer end.
Local IP PPPLNK.LOCALIP Set this parameter based on

the network plan.
Mask PPPLNK.IPMASK Set this parameter based on

the network plan.
Peer IP PPPLNK.PEERIP Set this parameter based on

the network plan.
PPPMUX PPPLNK.MUXCP Set this parameter to be

the peer end.
IP Header Compression PPPLNK.IPHC Set this parameter to be

the peer end.
Maximum Receive Unit PPPLNK.MRU Set this parameter based on

the network plan.
Protocol Field Compression PPPLNK.PFC Set this parameter to

ENABLE on local and peer
ends.
Address and Control Field PPPLNK.ACFC Set this parameter to

Compression ENABLE on local and peer
ends.
PPPHC for an MLPPP Group
For information about the parameters that must be set in an MPGRP MO to configure PPPHC
for an MLPPP group, see "IPHC for an MLPPP Group" in section 8.5 IPHC.
PPPHC for an MLPPP link in an MLPPP group. The cabinet number, subrack number, and
slot number of the MLPPP link must be the same as those of the board where the link is
located. If a UMPT is used for transmission, set the subboard type of the MLPPP link to
BASE_BOARD(Base Board).
Link No. MPLNK.PPPLNKN Each MLPPP link in an

unique link number.

SingleRAN
MLPPP Group Subboard MPLNK.MPGRPSBT Set this parameter to

Type E1_COVERBOARD(E1
Cover Board) or
BASE_BOARD(Base
Board) based on the actual
connection.
MLPPP Group No. MPLNK.MPGRPN Each MLPPP group must

have a unique group
number.
E1/T1 Subrack No. MPLNK.E1T1SRN Set these parameters based

on the actual connection.
E1/T1 Slot No. MPLNK.E1T1SN
E1/T1 Subboard Type MPLNK.E1T1SBT Set this parameter to

E1_COVERBOARD(E1
Cover Board) or
BASE_BOARD(Base
connection.
E1/T1 Port No. MPLNK.E1T1PN Set this parameter based on

Timeslot No. MPLNK.TSN Set this parameter to be

the peer end.
Maximum Receive Unit MPLNK.MRU Set this parameter based on

the network plan.
Protocol Field Compression MPLNK.PFC Set this parameter to

ends.
Address and Control Field MPLNK.ACFC Set this parameter to

Compression ENABLE on local and peer
ends.
8.6.4.3 Activation

l PPPHC for a PPP link
Run the ADD PPPLNK command to configure PPPHC for a PPP link.
l PPPHC for an MLPPP group
Step 1 Run the ADD MPGRP command to configure PPPHC for an MLPPP group.

SingleRAN
----End

TSN=TS1-1&TS2-1&TS3-1&TS4-1&TS5-1&TS6-1&TS7-1&TS8-1&TS9-1&TS10-1&TS11-1&TS12-1
&TS13-1&TS14-1&TS15-1&TS16-1&TS17-1&TS18-1&TS19-1&TS20-1&TS21-1&TS22-1&TS23-1&
TS24-1&TS25-1&TS26-1&TS27-1&TS28-1&TS29-1&TS30-1&TS31-1,
MUXCP=ENABLE, PFC=ENABLE, ACFC=ENABLE;

MUXCP=ENABLE, IPHC=ENABLE, MCPPP=ENABLE, MHO=LONG;
TSN=TS1-1&TS2-1&TS3-1&TS4-1&TS5-1&TS6-1&TS7-1&TS8-1&TS9-1&TS10-1&TS11-1&TS12-1
&TS13-1&TS14-1&TS15-1&TS16-1&TS17-1&TS18-1&TS19-1&TS20-1&TS21-1&TS22-1&TS23-1&
TS24-1&TS25-1&TS26-1&TS27-1&TS28-1&TS29-1&TS30-1&TS31-1, PFC=ENABLE,
ACFC=ENABLE;

Type

Status is UP(Up), PPPHC has been activated.
MLPPP Group Status is UP(Up), PPPHC has been activated.

SingleRAN
N/A
Transmission equipment connected to the GBTS supports E1/T1 ports along with PPPHC.

The following table describes the parameters that must be set in a BTSPPPLNK MO to
configure PPPHC for a PPP link. The cabinet number, subrack number, and slot number of
the PPP link must be the same as those of the board where the link is located.
PPP Link No. BTSPPPLNK.PPPLNKN Each PPP link must have a

unique link number.
Port No. BTSPPPLNK.PN Set this parameter based on

Bearing Time Slot BTSPPPLNK.TSBITMAP Set this parameter to be

the peer end.
Local IP Address BTSPPPLNK.LOCALIP Set this parameter based on

the network plan.
Subnet Mask BTSPPPLNK.MASK Set this parameter based on

the network plan.
Peer IP Address BTSPPPLNK.PEERIP Set this parameter based on

the network plan.
Support Protocol Field BTSPPPLNK.PFC Set this parameter to YES

Compress on local and peer ends.
Support Address and BTSPPPLNK.ACFC Set this parameter to YES

Control Field Compress on local and peer ends.
Max Receive Unit BTSPPPLNK.MRU Set this parameter based on

the network plan.
Validate Protocol Type BTSPPPLNK.AUTHTYPE Set this parameter to be

the peer end.

SingleRAN
Validate User Name BTSPPPLNK.AUTHNAM These parameters are valid

E only if the
BTSPPPLNK.AUTHTYPE
Validate Password BTSPPPLNK.AUTHPWD parameter is not set to
Validate Mode BTSPPPLNK.AUTHMOD NO_V(No Validate). Set
E this parameter to be
the peer end.
Restart Timer BTSPPPLNK.RSTIME Retain the default value.
IP Header Compression BTSPPPLNK.IPHC Set this parameter to be

the peer end.
The following table describes the parameters that must be set in a BTSMPGRP MO to
configure PPPHC for an MLPPP group. The cabinet number, subrack number, and slot
number of the MLPPP group must be the same as those of the board where the group is
located.
MLPPP Group No. BTSMPGRP.MPGRPN Set this parameter based on

the network plan.
Local IP Address BTSMPGRP.LOCALIP Set this parameter based on

the network plan.
Subnet Mask BTSMPGRP.MASK Set this parameter based on

the network plan.
Peer IP Address BTSMPGRP.PEERIP Set this parameter based on

the network plan.
MCPPP Switch BTSMPGRP.MPSWITCH Set this parameter to be

the peer end.
MP/MC List Head Option BTSMPGRP.MHF Set this parameter based on

the network plan.
MC PRI Number BTSMPGRP.MCCLASS These parameters are valid

only if the
BTSMPGRP.MPSWITCH
parameter is set to
ENABLE(Enable).
Validate Protocol Type BTSMPGRP.AUTHTYPE Set this parameter to be

the peer end.

SingleRAN
Support Protocol Field BTSMPGRP.PFC Set this parameter to YES

Compress on local and peer ends.
Support Address and BTSMPGRP.ACFC Set this parameter to YES

Control Field Compress on local and peer ends.
IP Header Compression BTSMPGRP.IPHC Set this parameter to be

the peer end.
The following table describes the parameters that must be set in a BTSMPLNK MO to
configure PPPHC for an MLPPP link in an MLPPP group. The cabinet number, subrack
number, and slot number of the MLPPP link must be the same as those of the board where the
link is located.
MLPPP Group No. BTSMPLNK.MPGRPN Each PPP link must have a

unique link number.
PPP Link No. BTSMPLNK.PPPLNKN Each PPP link must have a

unique link number.
Port No. BTSMPLNK.PN Set this parameter based on

Bearing Time Slot BTSMPLNK.TSBITMAP Set this parameter to be

the peer end.
Max Receive Unit BTSMPLNK.MRU Set this parameter based on

the network plan.
Restart Timer BTSMPLNK.RSTIME Retain the default value.
All parameters described in this section are not configurable in CME batch modification
center.
8.6.5.3 Activation

Run the ADD BTSPPPLNK command to configure PPPHC for a PPP link.

SingleRAN
Step 1 Run the ADD BTSMPGRP command to configure PPPHC for an MLPPP group.
----End

ADD BTSPPPLNK: IDTYPE=BYID, BTSID=0, PPPLNKN=0, PN=0, CN=0, SRN=0, SN=6,
23-1&TS24-1&TS25-1&TS26-1&TS27-1&TS28-1&TS29-1&TS30-1&TS31-1,
AUTHTYPE=NO_V;

MPSWITCH=ENABLE, MHF=LONG, AUTHTYPE=NO_V, PFC=YES, ACFC=YES, IPHC=ENABLE;
ADD BTSMPLNK: IDTYPE=BYNAME, BTSNAME="0", MPGRPN=0, PPPLNKN=0, PN=0, CN=0,
SRN=0, SN=7,
23-1&TS24-1&TS25-1&TS26-1&TS27-1&TS28-1&TS29-1&TS30-1&TS31-1;


Run the DSP BTSPPPLNK command, and then check the command output. If the value of
Link Status is UP(Up), PPPHC has been activated.
Run the DSP BTSMPGRP command, and then check the command output. If the value of
N/A
Transmission equipment connected to the base station controller supports E1/T1 ports along
with PPPHC.


SingleRAN

PPPHC for a PPP link. The subrack number and slot number of the PPP link must be the same
as those of the board where the link is located.
PPP link No. PPPLNK.PPPLNKN Each PPP link must have a

unique link number.
E1T1 port No. PPPLNK.DS1 Set this parameter based on

Bearing time slot PPPLNK.TSBITMAP Set this parameter to be

the peer end.
Borrow DevIP PPPLNK.BORROWDEVI Set this parameter based on

P the network plan.
Borrowed device IP address PPPLNK.DEVIP This parameter is valid only

if the
PPPLNK.BORROWDEVI
P parameter is not set to
YES(YES).
Local IP address PPPLNK.LOCALIP Set this parameter based on

the network plan.
Subnet mask PPPLNK. MASK Set this parameter based on

the network plan.
Peer IP address PPPLNK.PEERIP Set this parameter based on

the network plan.
Head compress PPPLNK.IPHC Set this parameter to be

the peer end.
Protocol field compress PPPLNK.PFC Set this parameter to

ends.
Address and Control Field PPPLNK.ACFC Set this parameter to

Compress ENABLE on local and peer
ends.
PPP mux PPPLNK.PPPMUX Set this parameter to be

the peer end.
Validate protocol type PPPLNK.AUTHTYPE Set this parameter to be

the peer end.

SingleRAN
Validate user name PPPLNK.AUTHNAME These parameters are valid

only if the
Validate password PPPLNK.AUTHPWD PPPLNK.AUTHTYPE
Validate mode PPPLNK.AUTHMODE parameter is not set to
NO_V(NO_V). Set this
parameter to be consistent
end.

PPPHC for an MLPPP group. The subrack number and slot number of the MLPPP group
must be the same as those of the board where the group is located.
MP Group No. MPGRP.MPGRPN Set this parameter based on

the network plan.
MP type MPGRP.MPTYPE Set this parameter to be

the peer end.
Borrow DevIP MPGRP.BORROWDEVIP Set this parameter based on

the network plan.
Borrowed device IP address MPGRP.DEVIP This parameter is valid only

if the
PPPLNK.BORROWDEVI
P parameter is not set to
YES(YES).
Local IP address MPGRP.LOCALIP Set this parameter based on

the network plan.
Subnet mask MPGRP.MASK Set this parameter based on

the network plan.

the network plan.
MC PRI number MPGRP.MCCLASS This parameter is valid only

if the MPGRP.MPTYPE
Head compress MPGRP.IPHC Set this parameter to be

the peer end.

SingleRAN
Protocol field compress MPGRP.PFC Set this parameter to

ends.
Address and Control Field MPGRP.ACFC Set this parameter to

Compress ENABLE on local and peer
ends.

the peer end.

length only if the
MPGRP.PPPMUX
PPP mux max mux-frame MPGRP.MAXMFLEN parameter is set to
PPP mux framing out- MPGRP.MUXTIME these parameters based on
PPPHC for an MLPPP link in an MLPPP group. The subrack number and slot number of the
MLPPP link must be the same as those of the board where the link is located.
MP Group No. MPLNK.MPGRPN Each PPP link must have a

unique link number.
PPP sub-link No. MPLNK.PPPLNKN Each PPP link must have a

unique link number.

Bearing time slot MPLNK.TSBITMAP Set this parameter to be

the peer end.
CRC check mode MPLNK.FCSTYPE Set this parameter based on

the network plan.
center.
8.6.6.3 Activation

SingleRAN

Run the ADD PPPLNK command to configure PPPHC for a PPP link.
Step 1 Run the ADD MPGRP command to configure PPPHC for an MLPPP group.
----End

23-1&TS24-1&TS25-1&TS26-1&TS27-1&TS28-1&TS29-1&TS30-1&TS31-1, BORROWDEVIP=NO,
PFC=Enable, ACFC=Enable, PPPMUX=Enable, AUTHTYPE=NO_V, FLOWCTRLSWITCH=ON,
ERRDETECTSW=OFF, OPSEPFLAG=OFF;

ADD MPGRP: SRN=0, SN=21, BRDTYPE=POUc, MPGRPN=0, MPTYPE=MLPPP,
BORROWDEVIP=NO, LOCALIP="192.168.20.75", MASK="255.255.255.0",
PEERIP="192.168.20.3", PFC=Enable, ACFC=Enable, PPPMUX=Enable,
FLOWCTRLSWITCH=ON, AUTHTYPE=NO_V, ERRDETECTSW=OFF, ANTIERRFLAG=OFF,
OPSEPFLAG=OFF;


Status is UP(Up), PPPHC has been activated.
N/A

None

SingleRAN

None

None
8.7 MLPPP/MC-PPP
This section describes engineering guidelines for MLPPP/MC-PPP.
8.7.1 When to Use

Before using MLPPP/MC-PPP, ensure that the base station and base station controller are
configured with the E1/T1 port.
MC-PPP is recommended if packet transmission efficiency is required to be improved and
more service classes are required.
MLPPP is recommended if the throughput is required to be increased and the transmission
delay is required to be reduced.

None
8.7.3 Planning
8.7.3.1 RF Planning
None

IP over E1/T1 is applied to devices at the two ends where MLPPP/MC-PPP is used.

l LTE hardware planning to enable LBFD-00300403/TDLBFD-00300403 MLPPP/
MCPPP
The eNodeB must be configured with the UMPT board. The LMPT board does not
support MLPPP.
– The BSC6900 must be configured with the PEUa/PEUc/POUc board.
– The BSC6910 must be configured with the POUc board.
– The eGBTS must be configured with the UTRP, UMPT, and GTMUb or GTMUc
boards.
– For the GBTS, the 3012 series base stations must be configured with the DPTU
board and the 3900 series base stations must be configured with the GTMUb or
GTMUc board.

SingleRAN

– The BSC6900 must be configured with the PEUa/PEUc/POUc board.
– The BTS3900 must be configured with the UTRP, UMPT, and WMPT boards.
Transmission equipment connected to the eNodeB, NodeB, or eGBTS supports IP over E1/T1
and MLPPP/MC-PPP.

MC-PPP
MLPPP/MCPPP for an MLPPP group. The cabinet number, subrack number, and slot number
of the MLPPP group must be the same as those of the board where the group is located. If a
UMPT is used for transmission, set the subboard type of the MLPPP group to
BASE_BOARD(Base Board).
PPPMUX MPGRP.MUXCP Set this parameter based on

the network plan.
PPP Mux Subframe Max MPGRP.MAXSFLEN These parameters are valid

Length only if the
MPGRP.MUXCP
PPP Muxframe Max Length MPGRP.MAXMFLEN parameter is set to
PPPMUX Combine Timeout MPGRP.MUXTIME ENABLE(Enable). Set this
network plan.
IP Header Compression MPGRP.IPHC Set this parameter to be

the peer end.
Multi-Class PPP MPGRP.MCPPP Set this parameter to

ends.
MP/MC Header Option MPGRP.MHO These parameters are valid

only if the
MCPPP Class MPGRP.MCCLASS MPGRP.MCPPP parameter
MLPPP/MC-PPP for an MLPPP link in an MLPPP group. Before adding an MLPPP link to a

SingleRAN
specific MLPPP group, ensure that the MLPPP group has been configured. The cabinet
number, subrack number, and slot number of an E1/T1 port must be the same as those of the
board where the port is located. If a UMPT is used for transmission, set the subboard types of
the MLPPP link, MLPPP group, and E1/T1 port to BASE_BOARD(Base Board).
Link No. MPLNK.PPPLNKN Each MLPPP link in an

unique link number.

have a unique group
number.
Timeslot No. MPLNK.TSN Set this parameter based on

the network plan.

the network plan.
Protocol Field Compression MPLNK.PFC Set this parameter to be

the peer end.
Address and Control Field MPLNK.ACFC Set this parameter to be

Compression consistent with the setting of
the peer end.
Negotiation Time MPLNK.RESTARTTMR Retain the default value.
MLPPP
Before deploying MLPPP, collect data for configuring an MLPPP group and an MLPPP link
in the MLPPP group.
The following table describes the parameter that must be set in an MPGRP MO to configure
MLPPP/MC-PPP for an MLPPP group. The cabinet number, subrack number, and slot
number of the MLPPP group must be the same as those of the board where the group is
located.
PPPMUX MPGRP.MUXCP Set this parameter to be

the peer end.
PPP Mux Subframe Max MPGRP.MAXSFLEN These parameters are valid

Length only if the
MPGRP.MUXCP
PPP Muxframe Max Length MPGRP.MAXMFLEN parameter is set to
PPPMUX Combine Timeout MPGRP.MUXTIME ENABLE(Enable). Set this
network plan.

SingleRAN
IP Header Compression MPGRP.IPHC Set this parameter based on

the network plan.
Multi-Class PPP MPGRP.MCPPP Set this parameter to be

the peer end.
MP/MC Header Option MPGRP.MHO These parameters are valid

only if the
MCPPP Class MPGRP.MCCLASS MPGRP.MCPPP parameter
MLPPP Link
MLPPP/MCPPP for an MLPPP link in an MLPPP group. The cabinet number, subrack
number, and slot number of the MLPPP link must be the same as those of the board where the
group is located. If a UMPT is used for transmission, set the subboard type of the MLPPP
group to BASE_BOARD(Base Board).
Link No. MPLNK.PPPLNKN Each PPP link must have a

unique link number.
MLPPP Group Subboard MPLNK.MPGRPSBT Set this parameter to

Type E1_COVERBOARD(E1
Cover Board) or
BASE_BOARD(Base
connection.

have a unique group
number.
E1/T1 Subrack No. MPLNK.E1T1SRN Set these parameters based

on the actual connection.
E1/T1 Slot No. MPLNK.E1T1SN
E1/T1 Subboard Type MPLNK.E1T1SBT Set this parameter to

E1_COVERBOARD(E1
Cover Board) or
BASE_BOARD(Base
connection.
E1/T1 Port No. MPLNK.E1T1PN Set this parameter based on


SingleRAN
Timeslot No. MPLNK.TSN Set this parameter to be

the peer end.

the network plan.
Protocol Field Compression MPLNK.PFC Set this parameter based on

the network plan.
Address and Control Field MPLNK.ACFC Set this parameter based on

Compression the network plan.
center.
8.7.4.3 Activation
Step 1 Run the ADD MPGRP command to configure MLPPP/MC-PPP for an MLPPP group.
----End

l MC-PPP
MUXCP=ENABLE, IPHC=ENABLE, MCPPP=ENABLE, MHO=LONG, MCCLASS=8;
S25-1&TS26-1&TS27-1&TS28-1&TS29-1&TS30-1&TS31-1, PFC=DISABLE, ACFC=DISABLE;
l MLPPP
MUXCP=ENABLE, IPHC=ENABLE, MCPPP=DISABLE;
S25-1&TS26-1&TS27-1&TS28-1&TS29-1&TS30-1&TS31-1, PFC=DISABLE, ACFC=DISABLE;


SingleRAN

Type

MLPPP Group Status is UP(Up), MLPPP/MC-PPP has been activated.
N/A
Transmission equipment connected to the GBTS supports IP over E1/T1 and MLPPP/MC-
PPP.

MC-PPP
configure MLPPP/MCPPP for an MLPPP group. The cabinet number, subrack number, and
slot number of the MLPPP group must be the same as those of the board where the group is
located.
MCPPP Switch BTSMPGRP.MPSWITCH Set this parameter to

ends.

SingleRAN

the network plan.

only if the
BTSMPGRP.MPSWITCH
parameter is set to
ENABLE(Enable).
Support Protocol Field BTSMPGRP.PFC Set this parameter to be

the peer end.
Support Address and BTSMPGRP.ACFC Set this parameter to be

Control Field Compress consistent with the setting of
the peer end.

the peer end.
configure MLPPP/MCPPP for an MLPPP link in an MLPPP group. Before adding an MLPPP
link to a specific MLPPP group, ensure that the MLPPP group has been configured. The
cabinet number, subrack number, and slot number of the MLPPP link must be the same as
those of the board where the link is located.
MLPPP Group No. BTSMPLNK.MPGRPN Each MLPPP group must

have a unique group
number.
PPP Link No. BTSMPLNK.PPPLNKN Each MLPPP link in an

unique link number.
Bearing Time Slot BTSMPLNK.TSBITMAP Set this parameter based on

the network plan.

the network plan.
MLPPP
in the MLPPP group.
configure MLPPP/MCPPP for an MLPPP group. The cabinet number, subrack number, and

SingleRAN
slot number of the MLPPP group must be the same as those of the board where the group is
located.
MCPPP Switch BTSMPGRP.MPSWITCH Set this parameter to

ends.

the network plan.

only if the
BTSMPGRP.MPSWITCH
parameter is set to
ENABLE(Enable).
Support Protocol Field BTSMPGRP.PFC Set this parameter to be

the peer end.
Support Address and BTSMPGRP.ACFC Set this parameter to be

Control Field Compress consistent with the setting of
the peer end.

the peer end.
configure MLPPP/MCPPP for an MLPPP link in an MLPPP group. The cabinet number,
subrack number, and slot number of the MLPPP link must be the same as those of the board
where the link is located.
MLPPP Group No. BTSMPLNK.MPGRPN Each MLPPP group must

have a unique group
number.
PPP Link No. BTSMPLNK.PPPLNKN Each MLPPP link in an

unique link number.
Bearing Time Slot BTSMPLNK.TSBITMAP Set this parameter based on

the network plan.

the network plan.

SingleRAN
center.
8.7.5.3 Activation

Step 1 Run the ADD BTSMPGRP command to configure MLPPP/MCPPP for an MLPPP group.
----End

l MC-PPP
MPSWITCH=ENABLE, AUTHTYPE=NO_V, IPHC=ENABLE;
ADD BTSMPLNK: IDTYPE=BYID, BTSID=0, MPGRPN=0, PPPLNKN=0, PN=0, CN=0, SRN=0,
SN=7,
l MLPPP
MPSWITCH=DISABLE, AUTHTYPE=NO_V, IPHC=ENABLE;
ADD BTSMPLNK: IDTYPE=BYID, BTSID=0, MPGRPN=0, PPPLNKN=0, PN=0, CN=0, SRN=0,
SN=7,


Run the DSP BTSMPGRP command, and then check the command output. If the value of
N/A
Transmission equipment connected to the base station controller supports IP over E1/T1 and
MLPPP/MC-PPP.

SingleRAN

MC-PPP
MLPPP/MCPPP for an MLPPP group. The subrack number and slot number of the MLPPP
group must be the same as those of the board where the group is located.
MP type MPGRP.MPTYPE Set this parameter to

MCPPP on local and peer
ends.

the network plan.

if the MPGRP.MPTYPE

the peer end.

the peer end.
Address and Control Field MPGRP.ACFC Set this parameter to be

the peer end.

the peer end.

length only if the
MPGRP.PPPMUX
length ENABLE(Enable). Set this
PPP mux framing out- MPGRP.MUXTIME parameter based on the
time[us] network plan.
MLPPP/MCPPP for an MLPPP link in an MLPPP group. Before adding an MLPPP link to a
specific MLPPP group, ensure that the MLPPP group has been configured. The subrack
number and slot number of an E1/T1 port must be the same as those of the board where the
port is located.

SingleRAN
MP Group No. MPLNK.MPGRPN Each MLPPP group must

have a unique group
number.
PPP sub-link No. MPLNK.PPPLNKN Each MLPPP link in an

unique link number.

the network plan.
Bearing time slot MPLNK.TSBITMAP Set this parameter based on

the network plan.
Sub-protocol negotiate out MPLNK.RESTARTTMR Retain the default value.

time[S]
Keep-alive timer length[S] MPLNK.KEEPALIVE Retain the default value.
CRC check mode MPLNK.FCSTYPE Retain the default value.
MLPPP
in the MLPPP group.
MLPPP/MCPPP for an MLPPP group. The subrack number and slot number of the MLPPP
group must be the same as those of the board where the group is located.
MP type MPGRP.MPTYPE Set this parameter to

MLPPP on local and peer
ends.

the network plan.

if the MPGRP.MPTYPE
parameter is set to MLPPP.

the peer end.

the peer end.

SingleRAN
Address and Control Field MPGRP.ACFC Set this parameter to be

the peer end.

the peer end.

length only if the
MPGRP.PPPMUX
length ENABLE(Enable). Set this
PPP mux framing out- MPGRP.MUXTIME parameter based on the
time[us] network plan.
MLPPP/MCPPP for an MLPPP link in an MLPPP group. The subrack number and slot
number of the MLPPP link must be the same as those of the board where the group is located.
MP Group No. MPLNK.MPGRPN Each MLPPP group must

have a unique group
number.
PPP sub-link No. MPLNK.PPPLNKN Each MLPPP link in an

unique link number.

the network plan.
Bearing time slot MPLNK.TSBITMAP Set this parameter based on

the network plan.
Sub-protocol negotiate out MPLNK.RESTARTTMR Retain the default value.

time[S]
Keep-alive timer length[S] MPLNK.KEEPALIVE Retain the default value.
CRC check mode MPLNK.FCSTYPE Retain the default value.
center.
8.7.6.3 Activation

SingleRAN
Step 1 Run the ADD MPGRP command to configure MLPPP/MC-PPP for an MLPPP group.
----End

l MC-PPP
ADD MPGRP: SRN=0, SN=21, BRDTYPE=POUc, MPGRPN=0, MPTYPE=MCPPP,
PEERIP="192.168.20.3", MHF=LONG, PPPMUX=Enable, FLOWCTRLSWITCH=ON,
AUTHTYPE=NO_V, ERRDETECTSW=OFF, ANTIERRFLAG=OFF, OPSEPFLAG=OFF;
l MLPPP
ADD MPGRP: SRN=0, SN=21, BRDTYPE=POUc, MPGRPN=0, MPTYPE=MLPPP,
PEERIP="192.168.20.3", PPPMUX=Enable, FLOWCTRLSWITCH=ON, AUTHTYPE=NO_V,
ERRDETECTSW=OFF, ANTIERRFLAG=OFF, OPSEPFLAG=OFF;


N/A

None

None

None

SingleRAN
Description 9 Parameters
9 Parameters
Table 9-1 Parameters

Parame NE MML Feature Feature Description
ter ID Comma ID Name
nd
MUXT BSC690 ADD GBFD-1 Abis Meaning: IP packet multiplexing type.

YPE 0 IPMUX 18604 MUX GUI Value Range: UDPMUX, ABISMUX,
MOD GBFD-1 UDP ATERMUX
IPMUX 18610 MUX Unit: None
for A
Transmi Actual Value Range: UDPMUX, ABISMUX,
ssion ATERMUX
Default Value: None

YPE 0 IPPOO 18604 MUX GUI Value Range: UDPMUX, ABISMUX
LMUX GBFD-1 UDP Unit: None
MOD 18610 MUX
IPPOO for A Actual Value Range: UDPMUX, ABISMUX
LMUX Transmi Default Value: None
ssion

YPE 0 IPPOO 18604 MUX GUI Value Range: UDPMUX
LMUX GBFD-1 UDP Unit: None
MOD 18610 MUX
IPPOO for A Actual Value Range: UDPMUX
ssion

SingleRAN

nd
UDPM BSC691 ADD GBFD-1 UDP Meaning: UDP multiplexing mode of the sending
UXMO 0 IPPOO 18610 MUX party. If the mode that does not support the function of
DSEND LMUX for A compressing the RTP header indicates that the sending
MOD Transmi party supports the UDP MUX RTP header but not the
IPPOO ssion function of compressing the RTP header. The mode
LMUX that supports the function of compressing the RTP
header indicates that the sending party supports both
the UDP MUX RTP header and the function of
compressing the RTP header.
GUI Value Range: NORTPCOMP, RTPCOMP
Unit: None
Actual Value Range: NORTPCOMP, RTPCOMP
Default Value: None
UDPM BSC690 ADD GBFD-1 Abis Meaning: UDP multiplexing mode of the sending
UXMO 0 IPMUX 18604 MUX party. If the mode that does not support the function of
DSEND MOD GBFD-1 UDP compressing the RTP header indicates that the sending
IPMUX 18610 MUX party supports the UDP MUX RTP header but not the
for A function of compressing the RTP header. The mode
Transmi that supports the function of compressing the RTP
ssion header indicates that the sending party supports both
the UDP MUX RTP header and the function of
compressing the RTP header.
Unit: None
Default Value: None
UDPM BSC691 ADD GBFD-1 UDP Meaning: UDP multiplexing mode of the receiving
UXMO 0 IPPOO 18610 MUX party. The mode that does not support the function of
DRECV LMUX for A compressing the RTP header indicates that the
MOD Transmi receiving party supports the UDP MUX RTP header
IPPOO ssion but not the function of compressing the RTP header.
LMUX The mode that supports the function of compressing
the RTP header indicates that the receiving party
supports both the UDP MUX RTP header and the
function of compressing the RTP header.
Unit: None
Default Value: None

SingleRAN

nd
UDPM BSC690 ADD GBFD-1 UDP Meaning: UDP multiplexing mode of the receiving
UXMO 0 IPMUX 18610 MUX party. The mode that does not support the function of
DRECV MOD for A compressing the RTP header indicates that the
IPMUX Transmi receiving party supports the UDP MUX RTP header
ssion but not the function of compressing the RTP header.
The mode that supports the function of compressing
the RTP header indicates that the receiving party
supports both the UDP MUX RTP header and the
function of compressing the RTP header.
Unit: None
Default Value: None
SUBFR BSC691 ADD GBFD-1 Abis Meaning: Maximum sub-frame length. This parameter
AMEL 0 IPPOO 18604 MUX indicates the maximum sub-frame length for
EN LMUX GBFD-1 UDP multiplexing. If the length of a sub-frame exceeds this
MOD 18610 MUX value, the sub-frame is not multiplexed.
IPPOO for A GUI Value Range: 16~1023
LMUX Transmi Unit: byte
ssion
Actual Value Range: 16~1023
Default Value: 352
SUBFR BSC690 ADD GBFD-1 Abis Meaning: Maximum sub-frame length. This parameter
AMEL 0 IPMUX 18604 MUX indicates the maximum sub-frame length for
EN MOD GBFD-1 UDP multiplexing. If the length of a sub-frame exceeds this
IPMUX 18610 MUX value, the sub-frame is not multiplexed.
for A GUI Value Range: 16~1023
Transmi Unit: byte
ssion
Default Value: 352
MAXF BSC691 ADD GBFD-1 Abis Meaning: Maximum multiplexing frame length.
RAME 0 IPPOO 18604 MUX GUI Value Range: 24~1031
LEN LMUX GBFD-1 UDP Unit: byte
MOD 18610 MUX
IPPOO for A Actual Value Range: 24~1031
LMUX Transmi Default Value: 1031
ssion

SingleRAN

nd
MAXF BSC690 ADD GBFD-1 Abis Meaning: Maximum multiplexing frame length
RAME 0 IPMUX 18604 MUX GUI Value Range: 24~1031
LEN MOD GBFD-1 UDP Unit: byte
IPMUX 18610 MUX
for A Actual Value Range: 24~1031
Transmi Default Value: 1031
ssion
FPTIM BSC691 ADD GBFD-1 Abis Meaning: This parameter specifies the maximum time
ER 0 IPPOO 18604 MUX that the system waits before sending the multiplexed
LMUX GBFD-1 UDP data. This parameter is used for the system to send the
MOD 18610 MUX multiplexed data. If the time for buffering the data
IPPOO for A exceeds this value, the system does not wait for the
LMUX Transmi multiplexing of other packets. In this way, the
ssion extended delay can be prevented.
GUI Value Range: 1~90
Unit: ms
Default Value: 2
ER 0 IPMUX 18604 MUX that the system waits before sending the multiplexed
MOD GBFD-1 UDP data. This parameter is used for the system to send the
IPMUX 18610 MUX multiplexed data. If the time for buffering the data
for A exceeds this value, the system does not wait for the
Transmi multiplexing of other packets. In this way, the
Unit: ms
Default Value: 2
ISQOS BSC690 ADD GBFD-1 Abis Meaning: This parameter specifies whether it is
PATH 0 IPMUX 18604 MUX QOSPATH, or not.
GBFD-1 UDP GUI Value Range: NO(NO), YES(YES)
18610 MUX Unit: None
for A
Transmi Actual Value Range: NO, YES
ssion Default Value: None

SingleRAN

nd
PHB BSC690 ADD GBFD-1 Abis Meaning: PHB type of the IPMUX to be enabled
0 IPMUX 18604 MUX GUI Value Range: BE(BE), AF11(AF11),
GBFD-1 UDP AF12(AF12), AF13(AF13), AF21(AF21),
18610 MUX AF22(AF22), AF23(AF23), AF31(AF31),
for A AF32(AF32), AF33(AF33), AF41(AF41),
Transmi AF42(AF42), AF43(AF43), EF(EF), CS1(CS1),
ssion CS2(CS2), CS3(CS3), CS4(CS4), CS5(CS5),
CS6(CS6), CS7(CS7)
Unit: None
Actual Value Range: BE, AF11, AF12, AF13, AF21,
AF22, AF23, AF31, AF32, AF33, AF41, AF42,
AF43, EF, CS1, CS2, CS3, CS4, CS5, CS6, CS7
Default Value: None
PHB BSC691 ADD GBFD-1 Abis Meaning: PHB type of the IPMUX to be enabled
0 IPPOO 18604 MUX GUI Value Range: BE(BE), AF11(AF11),
LMUX GBFD-1 UDP AF12(AF12), AF13(AF13), AF21(AF21),
18610 MUX AF22(AF22), AF23(AF23), AF31(AF31),
for A AF32(AF32), AF33(AF33), AF41(AF41),
Transmi AF42(AF42), AF43(AF43), EF(EF), CS1(CS1),
ssion CS2(CS2), CS3(CS3), CS4(CS4), CS5(CS5),
CS6(CS6), CS7(CS7)
Unit: None
Actual Value Range: BE, AF11, AF12, AF13, AF21,
AF22, AF23, AF31, AF32, AF33, AF41, AF42,
AF43, EF, CS1, CS2, CS3, CS4, CS5, CS6, CS7
Default Value: None
IPMUX BTS390 ADD WRFD- FP Meaning: Indicates whether the IPMUX function is
SWITC 0, IPPAT 050420 MUX enabled on IP paths. LTE currently does not support
H BTS390 H for IP this function.
0 GBFD-1 Transmi
MOD 18604 GUI Value Range: DISABLE(Disable),
WCDM IPPAT ssion ENABLE(Enable)
A, H
BTS390 Abis Unit: None
0 LTE DSP MUX Actual Value Range: DISABLE, ENABLE
IPPAT
H Default Value: DISABLE(Disable)
LST
IPPAT
H

SingleRAN

nd
TIMER BTS390 ADD WRFD- FP Meaning: Indicates the length of the IPMUX timer,
0, IPPAT 050420 MUX which defines the maximum buffer time for IPMUX
BTS390 H for IP packets. The LTE currently does not support the
0 GBFD-1 Transmi IPMUX function.
MOD 18604
WCDM IPPAT ssion GUI Value Range: 1~20
A, H
BTS390 Abis Unit: ms
0 LTE LST MUX
IPPAT
H Default Value: 1
FRAM BTS390 ADD WRFD- FP Meaning: Indicates the maximum multiframe length
ELEN 0, IPPAT 050420 MUX of IPMUX. The LTE currently does not support the
BTS390 H for IP IPMUX function.
0 GBFD-1 Transmi
MOD 18604 GUI Value Range: 100~1031
WCDM IPPAT ssion
A, Unit: byte
H Abis
BTS390 Actual Value Range: 100~1031
0 LTE LST MUX
IPPAT Default Value: 270
H
SUBFR BTS390 ADD WRFD- FP Meaning: Indicates the maximum subframe length of
AMEL 0, IPPAT 050420 MUX IPMUX. The LTE currently does not support the
EN BTS390 H for IP IPMUX function.
0 GBFD-1 Transmi
MOD 18604 GUI Value Range: 1~1023
WCDM IPPAT ssion
A, Unit: byte
H Abis
BTS390 Actual Value Range: 1~1023
0 LTE LST MUX
IPPAT Default Value: 127
H
SUBFR BSC691 ADD GBFD-1 Abis Meaning: Maximum sub-frame length. The data
AMET 0 BTSAB 18704 Indepen stream to be multiplexed on the same multiplexing
HRES ISMUX dent channel must be of the same type, and the length of
FLOW Transmi the packet before multiplexing cannot exceed the
MOD ssion maximum subframe length. If the length of a packet
BTSAB exceeds the maximum subframe length, the packet is
ISMUX transmitted without being multiplexed.
FLOW GUI Value Range: 16~1023
Unit: byte
Default Value: 352

SingleRAN

nd
SUBFR BSC690 ADD GBFD-1 Abis Meaning: Maximum sub-frame length. The data
AMET 0 BTSAB 18704 Indepen stream to be multiplexed on the same multiplexing
HRES ISMUX dent channel must be of the same type, and the length of
FLOW Transmi the packet before multiplexing cannot exceed the
MOD ssion maximum subframe length. If the length of a packet
BTSAB exceeds the maximum subframe length, the packet is
ISMUX transmitted without being multiplexed.
Unit: byte
Default Value: 352
PKTLE BSC691 ADD GBFD-1 Abis Meaning: Maximum multiplexing frame length. The
NTHRE 0 BTSAB 18704 Indepen length of the multiplexed packet must not exceed the
S ISMUX dent maximum multiplexing frame length. If the length of
FLOW Transmi the multiplexed packet exceeds the maximum
MOD ssion multiplexing frame length, the packet is transferred
BTSAB without being added with new subframes. The frame
ISMUX length refers to the payload, excluding the IP/UDP
FLOW header.
Unit: byte
Default Value: 1031
PKTLE BSC690 ADD GBFD-1 Abis Meaning: Maximum multiplexing frame length. The
NTHRE 0 BTSAB 18704 Indepen length of the multiplexed packet must not exceed the
S ISMUX dent maximum multiplexing frame length. If the length of
FLOW Transmi the multiplexed packet exceeds the maximum
MOD ssion multiplexing frame length, the packet is transferred
BTSAB without being added with new subframes. The frame
ISMUX length refers to the payload, excluding the IP/UDP
FLOW header.
Unit: byte
Default Value: 1031

SingleRAN

nd
TIMEO BSC691 ADD GBFD-1 Abis Meaning: Longest waiting time for multiplexing
UT 0 BTSAB 18704 Indepen When the multiplexed packet is no longer added with
ISMUX dent new data and the timer expires, the multiplexed packet
FLOW Transmi is transmitted directly. This parameter is determined
MOD ssion by the number of multiplexed packets. When the
BTSAB number of multiplexed packets increases, the value of
ISMUX this parameter increases.
Unit: ms
Default Value: 2
TIMEO BSC690 ADD GBFD-1 Abis Meaning: Longest waiting time for multiplexing
UT 0 BTSAB 18704 Indepen When the multiplexed packet is no longer added with
ISMUX dent new data and the timer expires, the multiplexed packet
FLOW Transmi is transmitted directly. This parameter is determined
MOD ssion by the number of multiplexed packets. When the
BTSAB number of multiplexed packets increases, the value of
ISMUX this parameter increases.
Unit: ms
Default Value: 2
SRVTY BSC691 ADD GBFD-1 IP QOS Meaning: Service type of the IP interface board. The
PE 0 BTSAB 18605 Abis service type can be CS speech, CS data, PS high
ISMUX GBFD-1 MUX priority, or PS low priority.
FLOW 18604 GUI Value Range: CSVOICE(CS Voice),
MOD CSDATA(CS Data), PSHIGHPRI(PS High PRI),
BTSAB PSLOWPRI(PS Low PRI)
ISMUX Unit: None
FLOW
Actual Value Range: CSVOICE, CSDATA,
RMV PSHIGHPRI, PSLOWPRI
BTSAB
ISMUX Default Value: None
FLOW

SingleRAN

nd
SRVTY BSC690 ADD GBFD-1 IP QOS Meaning: Service type of the IP interface board. The
PE 0 BTSAB 18605 Abis service type can be CS speech, CS data, PS high
ISMUX GBFD-1 MUX priority, or PS low priority.
FLOW 18604 GUI Value Range: CSVOICE(CS Voice),
MOD CSDATA(CS Data), PSHIGHPRI(PS High PRI),
BTSAB PSLOWPRI(PS Low PRI)
ISMUX Unit: None
FLOW
Actual Value Range: CSVOICE, CSDATA,
RMV PSHIGHPRI, PSLOWPRI
BTSAB
ISMUX Default Value: None
FLOW
IPHC BSC691 ADD GBFD-1 Abis IP Meaning: This parameter specifies whether to
0 PPPLN 18611 over compress the packet headers, or not.
K E1/T1 GUI Value Range: RTP/UDP/IP_HC(RTP/UDP/
MOD IP_HC), UDP/IP_HC(UDP/IP_HC), No_HC(No_HC)
PPPLN Unit: None
K
Actual Value Range: No_HC, UDP/IP_HC,
RTP/UDP/IP_HC
Default Value: UDP/IP_HC(UDP/IP_HC)
IPHC BSC690 ADD GBFD-1 Abis Meaning: This parameter specifies whether to
0 PPPLN 18612 IPHC compress the packet headers, or not.
K GUI Value Range: RTP/UDP/IP_HC(RTP/UDP/
PPPLN Unit: None
K
Actual Value Range: RTP/UDP/IP_HC, UDP/IP_HC,
No_HC
IPHC BSC691 ADD GBFD-1 Abis IP Meaning: This parameter specifies whether to
0 MPGR 18611 over compress the IP header of a MLPPP group, or not.
P E1/T1 GUI Value Range: RTP/UDP/IP_HC(RTP/UDP/
MPGR Unit: None
P
Actual Value Range: No_HC, UDP/IP_HC,
RTP/UDP/IP_HC

SingleRAN

nd
IPHC BSC690 ADD GBFD-1 Abis Meaning: This parameter specifies whether to
0 MPGR 18612 IPHC compress the IP header of a MLPPP group, or not.
P GUI Value Range: RTP/UDP/IP_HC(RTP/UDP/
MPGR Unit: None
P
Actual Value Range: RTP/UDP/IP_HC, UDP/IP_HC,
No_HC
IPHC BTS390 ADD WRFD- Fraction Meaning: Indicates whether to enable IP header
0, PPPLN 050411 al IP compression.
BTS390 K WRFD- Function GUI Value Range: DISABLE(Disable),
0 MOD 050402 on Iub ENABLE(Enable)
WCDM PPPLN Interface
A, LBFD-0 Unit: None
K IP
BTS390 03004 / Transmi Actual Value Range: DISABLE, ENABLE
0 LTE DSP TDLBF
PPPLN ssion Default Value: ENABLE(Enable)
D-00300 Introduc
K 4 tion on
LST LBFD-0 Iub
PPPLN 0300401 Interface
K /
TDLBF Compre
D-00300 ssion &
401 Multiple
xing
GBFD-1 over
18612 E1/T1
IP
Header
Compre
ssion
Abis
IPHC

SingleRAN

nd
IPHC BTS390 ADD WRFD- Fraction Meaning: Indicates whether to enable IP header
0, MPGR 050411 al IP compression.
BTS390 P Function GUI Value Range: DISABLE(Disable),
0 LBFD-0 on Iub
MOD 0300403 ENABLE(Enable)
WCDM MPGR Interface
A, / Unit: None
P TDLBF ML-
BTS390 Actual Value Range: DISABLE, ENABLE
0 LTE DSP D-00300 PPP/MC
MPGR 403 -PPP Default Value: ENABLE(Enable)
P LBFD-0 IP
LST 0300401 Header
MPGR / Compre
P TDLBF ssion
D-00300
401 Abis
IPHC
GBFD-1
18612
IPHCS BTS390 ADD WRFD- Fraction Meaning: Indicates whether to enable IPHC suboption
UBOPT 0, PPPLN 050411 al IP negotiation.
K IP
0 LTE LST TDLBF
PPPLN ssion Default Value: DISABLE(Disable)
D-00300 Introduc
K 4 tion on
LBFD-0 Iub
0300401 Interface
/
TDLBF Compre
D-00300 ssion &
401 Multiple
xing
GBFD-1 over
18612 E1/T1
IP
Header
Compre
ssion
Abis
IPHC

SingleRAN

nd
IPHCS BTS390 ADD WRFD- Fraction Meaning: Indicates whether to enable IPHC suboption
UBOPT 0, MPGR 050411 al IP negotiation.
BTS390 P Function GUI Value Range: DISABLE(Disable),
0 LBFD-0 on Iub
MOD 0300403 ENABLE(Enable)
WCDM MPGR Interface
A, / Unit: None
P TDLBF ML-
BTS390 Actual Value Range: DISABLE, ENABLE
0 LTE LST D-00300 PPP/MC
MPGR 403 -PPP Default Value: DISABLE(Disable)
P LBFD-0 IP
0300401 Header
/ Compre
TDLBF ssion
D-00300
401 Abis
IPHC
GBFD-1
18612
ACFC BSC691 ADD GBFD-1 Abis IP Meaning: This parameter specifies whether to
0 PPPLN 18611 over compress the address and control fields, or not. If this
K E1/T1 parameter is set to ENABLE, both ends negotiate
MOD whether to compress the address and control fields. If
PPPLN this parameter is set to DISABLE, the address and
K control fields are not compressed.
GUI Value Range: Disable(Disable), Enable(Enable)
Unit: None
Actual Value Range: Disable, Enable
Default Value: Enable(Enable)
0 PPPLN 18611 over compress the address and control fields, or not. If this
K E1/T1 parameter is set to ENABLE, both ends negotiate
PPPLN this parameter is set to DISABLE, the address and
K control fields are not compressed.
Unit: None

SingleRAN

nd
0 MPGR 18611 over compress the address and control fields, or not. If this
P E1/T1 parameter is set to ENABLE, both ends negotiate
MPGR this parameter is set to DISABLE, the address and
P control fields are not compressed.
Unit: None
0 MPGR 18611 over compress the address and control fields, or not. If this
P E1/T1 parameter is set to ENABLE, both ends negotiate
MPGR this parameter is set to DISABLE, the address and
P control fields are not compressed.
Unit: None
PFC BSC691 ADD GBFD-1 Abis IP Meaning: Compression flag of the PPP link protocol
0 PPPLN 18611 over domain
K E1/T1 GUI Value Range: Disable(Disable), Enable(Enable)
MOD Unit: None
PPPLN
K Actual Value Range: Disable, Enable
0 PPPLN 18611 over domain
K E1/T1 GUI Value Range: Disable(Disable), Enable(Enable)
MOD Unit: None
PPPLN
K Actual Value Range: Disable, Enable
0 MPGR 18611 over domain
P E1/T1 GUI Value Range: Disable(Disable), Enable(Enable)
MOD Unit: None
MPGR
P Actual Value Range: Disable, Enable

SingleRAN

nd
0 MPGR 18611 over domain
P E1/T1 GUI Value Range: Disable(Disable), Enable(Enable)
MOD Unit: None
MPGR
P Actual Value Range: Disable, Enable
PFC BTS390 ADD WRFD- Fraction Meaning: Indicates whether to enable protocol field
0, PPPLN 050411 al IP compression.
K IP
0 LTE DSP TDLBF
PPPLN ssion Default Value: ENABLE(Enable)
D-00300 Introduc
K 4 tion on
LST Iub
PPPLN GBFD-1
18611 Interface
K
Compre
ssion &
Multiple
xing
over
E1/T1
Abis IP
over
E1/T1
PFC BSC691 ADD GBFD-1 Abis IP Meaning: Whether to compress the protocol field of
0 BTSPP 18611 over the PPP link.
PLNK E1/T1 GUI Value Range: NO(No), YES(Yes)
MOD Unit: None
BTSPP
PLNK Actual Value Range: NO, YES
Default Value: YES(Yes)
0 BTSPP 18611 over the PPP link.
PLNK E1/T1 GUI Value Range: NO(No), YES(Yes)
MOD Unit: None
BTSPP
PLNK Actual Value Range: NO, YES

SingleRAN

nd
0 BTSMP 18611 over the PPP link.
GRP E1/T1 GUI Value Range: NO(No), YES(Yes)
MOD Unit: None
BTSMP
GRP Actual Value Range: NO, YES
0 BTSMP 18611 over the PPP link.
GRP E1/T1 GUI Value Range: NO(No), YES(Yes)
MOD Unit: None
BTSMP
GRP Actual Value Range: NO, YES
PATHT BTS390 ADD GBFD-1 Abis Meaning: Indicates the type of the IP path. FIXED
YPE 0, IPPAT 18601 over IP indicates that this IP path is used to carry the service
BTS390 H GBFD-1 Abis IP with specified Quality of Service (QoS), that is, with a
0 MOD 18611 over specified DSCP. ANY indicates that this IP path can
WCDM IPPAT E1/T1 be used to carry services of any QoS and hence is used
A, H to carry the service without a specified DSCP.
BTS390 GUI Value Range: FIXED(Fixed QoS), ANY(Any
0 LTE LST
IPPAT QoS)
H Unit: None
Actual Value Range: FIXED, ANY
Default Value: FIXED(Fixed QoS)
IPMUX BSC690 ADD GBFD-1 Abis Meaning: IP packet multiplex index.

INDEX 0 IPMUX 18604 MUX GUI Value Range: 0~12999
MOD GBFD-1 UDP Unit: None
IPMUX 18610 MUX
for A Actual Value Range: 0~12999
RMV
IPMUX Transmi Default Value: None
ssion
IPPOO BSC690 ADD GBFD-1 Abis Meaning: IP packet multiplex index.

LMUXI 0 IPPOO 18604 MUX GUI Value Range: 0~29999
NDEX LMUX GBFD-1 UDP Unit: None
MOD 18610 MUX
RMV ssion
IPPOO
LMUX

SingleRAN

nd
IPPOO BSC691 ADD GBFD-1 Abis Meaning: IP packet multiplex index

LMUXI 0 IPPOO 18604 MUX GUI Value Range: 0~29999
NDEX LMUX GBFD-1 UDP Unit: None
MOD 18610 MUX
RMV ssion
IPPOO
LMUX
ER 0 IPPOO 18604 MUX that the system waits before sending the multiplexed
LMUX GBFD-1 UDP data. This parameter is used for the system to send the
MOD 18610 MUX multiplexed data. If the time for buffering the data
IPPOO for A exceeds this value, the system does not wait for the
LMUX Transmi multiplexing of other packets. In this way, the
Unit: ms
Default Value: 2
MAXF BSC690 ADD GBFD-1 Abis Meaning: Maximum multiplexing frame length.
RAME 0 IPPOO 18604 MUX GUI Value Range: 24~1031
LEN LMUX GBFD-1 UDP Unit: byte
MOD 18610 MUX
LMUX Transmi Default Value: 1031
ssion
PPPMU BSC690 ADD GBFD-1 A IP Meaning: This parameter specifies whether to enable
X 0 PPPLN 18622 over the PPP frame multiplexing function, or not.If this
K GBFD-1 E1/T1 parameter is set to ENABLE, the PPP frame
MOD 18611 Abis IP multiplexing function is enabled. If this parameter is
PPPLN over set to DISABLE, the PPP frame multiplexing function
K E1/T1 is disabled.
Unit: None
Default Value: Disable(Disable)

SingleRAN

nd
MAXSF BSC690 ADD None None Meaning: Maximum PPPMUX sub-frame length. If
LEN 0 PPPLN the PPP frame length is larger than this value, the
K PPPMUX multiplexing is performed. The value of
MOD this parameter cannot be larger than the maximum
PPPLN multiplexed frame length wMuxMfl. To enable the
K PPPMUX, the number of sub-frames must be more
than or equal to 2. The following condition must be
met: wMuxMaxSfL <= ( wMuxMfl-8 )/2
Unit: byte
Default Value: 64
MAXM BSC690 ADD None None Meaning: The value of this parameter cannot be less
FLEN 0 PPPLN than the maximum PPPMUX sub-frame length
K (MUXMAXSFL). This parameter can be associated
MOD with the maximum segment length of the MP to
PPPLN control whether to segment the multiplexed MP. To
K enable the PPPMUX, the number of sub-frames must
be more than or equal to 2. The following condition
must be met: wMuxMaxSfL <= ( wMuxMfl-8 )/2.
Unit: byte
Default Value: 256
MUXTI BSC690 ADD GBFD-1 A IP Meaning: Maximum time waiting for multiplexing
ME 0 PPPLN 18622 over GUI Value Range: 1~1500
K GBFD-1 E1/T1
Unit: microsecond
MOD 18611 Abis IP
PPPLN over Actual Value Range: 1~1500
K E1/T1 Default Value: 1000

SingleRAN

nd
MPTYP BSC690 ADD GBFD-1 Abis IP Meaning: This parameter specifies the MP type,
E 0 MPGR 18611 over which can be MLPPP or MCPPP. MLPPP indicates
P E1/T1 that multiple PPP links are aggregated into an MP
MOD group. For details about MLPPP, see RFC1990
MPGR protocol. MCPPP indicates that a sender fragments the
P packets of various priorities into multiple classes of
fragments and allows to simultaneously send packets
of different priorities. For details about MCPPP, see
RFC2686 protocol.
GUI Value Range: MLPPP, MCPPP
Unit: None
Actual Value Range: MLPPP, MCPPP
Default Value: MCPPP
MHF BSC690 ADD GBFD-1 Abis IP Meaning: MLPPP/MCPPP sequence header option.
0 MPGR 18611 over GUI Value Range: LONG(LONG), SHORT(SHORT)
P E1/T1
Unit: None
MOD
MPGR Actual Value Range: LONG, SHORT
P Default Value: LONG(LONG)
MCCL BSC690 ADD GBFD-1 Abis IP Meaning: Number of MCPPP priorities. This
ASS 0 MPGR 18611 over parameter is valid when the MLPPP group type is
P E1/T1 MCPPP. Value 4(8) indicates that there are 4(8)
MOD priority classes.
MPGR GUI Value Range: 4;8
P Unit: None
Actual Value Range: 4, 8
Default Value: None
PPPMU BSC690 ADD GBFD-1 A IP Meaning: This parameter specifies whether to enable
X 0 MPGR 18622 over the PPP frame multiplexing function, or not.If this
P GBFD-1 E1/T1 parameter is set to ENABLE, the PPP frame
MOD 18611 Abis IP multiplexing function is enabled. If this parameter is
MPGR over set to DISABLE, the PPP frame multiplexing function
P E1/T1 is disabled.
Unit: None
Default Value: Disable(Disable)

SingleRAN

nd
MAXSF BSC690 ADD None None Meaning: Maximum length of the PPP multiplexing
LEN 0 MPGR frame.
P GUI Value Range: 1~746
MOD Unit: None
MPGR
P Actual Value Range: 1~746
Default Value: None
MAXM BSC690 ADD GBFD-1 A IP Meaning: Maximum length of the PPP multiplexing
FLEN 0 MPGR 18622 over frame.
P GBFD-1 E1/T1 GUI Value Range: 1~1500
MOD 18611 Abis IP Unit: None
MPGR over
P E1/T1 Actual Value Range: 1~1500
Default Value: None
MUXTI BSC690 ADD None None Meaning: Frame timeout duration of the PPP
ME 0 MPGR multiplexing group
P GUI Value Range: 1~1500
MOD Unit: microsecond
MPGR
P Actual Value Range: 1~1500
Default Value: None
MPGR BSC690 ADD GBFD-1 Abis IP Meaning: MLPPP group number.

PN 0 MPLN 18611 over GUI Value Range: 0~167
K E1/T1
Unit: None
Actual Value Range: 0~31(PEUa/PEUc),
0~167(POUc)
Default Value: None
PPPLN BSC690 ADD GBFD-1 Abis IP Meaning: PPP link number

KN 0 MPLN 18611 over GUI Value Range: 0~499
K E1/T1
Unit: None
MOD
MPLN Actual Value Range: 0~499
K Default Value: None
RMV
MPLN
K

SingleRAN

nd
TSBIT BSC690 ADD GBFD-1 Abis IP Meaning: Bearer E1/T1 port timeslot of MLPPP link.
MAP 0 MPLN 18611 over GUI Value Range: TS1(Time_slot_1),
K E1/T1 TS2(Time_slot_2), TS3(Time_slot_3),
MOD TS4(Time_slot_4), TS5(Time_slot_5),
MPLN TS6(Time_slot_6), TS7(Time_slot_7),
K TS8(Time_slot_8), TS9(Time_slot_9),
TS10(Time_slot_10), TS11(Time_slot_11),
TS30(Time_slot_30), TS31(Time_slot_31)
Unit: None
Actual Value Range: TS1, TS2, TS3, TS4, TS5, TS6,
TS7, TS8, TS9, TS10, TS11, TS12, TS13, TS14,
TS31
Default Value: None
RESTA BSC690 ADD GBFD-1 Abis IP Meaning: Duration of the PPP/MLPPP link restart
RTTM 0 MPLN 18611 over timer.
R K E1/T1 GUI Value Range: 2~5
MOD Unit: s
MPLN
K Actual Value Range: 2~5
Default Value: 3
KEEPA BSC690 ADD GBFD-1 Abis IP Meaning: Duration of the PPP/MLPPP link keep-alive
LIVE 0 MPLN 18611 over timer.
K E1/T1 GUI Value Range: 1~30
MOD Unit: s
MPLN
K Actual Value Range: 1~30
Default Value: 1

SingleRAN

nd
FCSTY BSC690 ADD GBFD-1 Abis IP Meaning: CRC verification mode of MLPPP link.
PE 0 MPLN 18611 over GUI Value Range: None(None), 16bit(16bit),
K E1/T1 32bit(32bit)
MOD Unit: None
MPLN
K Actual Value Range: None, 16bit, 32bit
Default Value: 16bit(16bit)
IPHC BSC691 ADD GBFD-1 Abis Meaning: Whether a PPP link is enabled with the
0 BTSPP 18612 IPHC function of IP header compression
PLNK GBFD-1 Ethernet GUI Value Range: DISABLE(DISABLE),
MOD 18630 OAM ENABLE(ENABLE)
BTSPP Unit: None
PLNK
Actual Value Range: DISABLE, ENABLE
Default Value: DISABLE(DISABLE)
0 BTSPP 18612 IPHC function of IP header compression
PLNK GBFD-1 Ethernet GUI Value Range: DISABLE(DISABLE),
BTSPP Unit: None
PLNK
0 BTSMP 18612 IPHC function of IP header compression
GRP GBFD-1 Ethernet GUI Value Range: DISABLE(DISABLE),
BTSMP Unit: None
GRP
0 BTSMP 18612 IPHC function of IP header compression
GRP GBFD-1 Ethernet GUI Value Range: DISABLE(DISABLE),
BTSMP Unit: None
GRP

SingleRAN
Description 10 Counters
10 Counters
There are no specific counters associated with this feature.

SingleRAN
Description 11 Glossary
11 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

SingleRAN
Description 12 Reference Documents
12 Reference Documents
RFC 2686, " The Multi-Class Extension to Multi-Link PPP"


IP Transmission Efficiency Improvement (SingleRAN - 01)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

IP Transmission Efficiency Improvement (SingleRAN - 01)

Uploaded by

Copyright:

Available Formats

SingleRAN

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 01 (2016-09-30) Huawei Proprietary and Confidential i

1 About This Document.................................................................................................................. 1

Issue 01 (2016-09-30) Huawei Proprietary and Confidential ii

4.3.2.1 PPP Frame Format..................................................................................................................................................19

Issue 01 (2016-09-30) Huawei Proprietary and Confidential iii

Issue 01 (2016-09-30) Huawei Proprietary and Confidential iv

Issue 01 (2016-09-30) Huawei Proprietary and Confidential v

Issue 01 (2016-09-30) Huawei Proprietary and Confidential vi

8.5.6.5.3 Using the CME.................................................................................................................................................... 75

Issue 01 (2016-09-30) Huawei Proprietary and Confidential vii

8.7.1 When to Use.............................................................................................................................................................. 91

Issue 01 (2016-09-30) Huawei Proprietary and Confidential viii

1 About This Document

This document covers the following features:

l LBFD-003004 Compression & Multiplexing over E1/T1

1.2 Intended Audience

l Need to understand the features described herein

Issue 01 (2016-09-30) Huawei Proprietary and Confidential 1

1.3 Change History

SRAN12.1 Draft A (2016-12-30)

Change Change Description Parameter Change

Feature Added support for IP transmission efficiency None

Added support for IP transmission efficiency None

Editorial Revised the descriptions in this document. None

1.4 Differences Between Base Station Types

LBFD-003004 Compression & Multiplexing over Yes No Yes

Issue 01 (2016-09-30) Huawei Proprietary and Confidential 2

Feature ID Feature Name Suppo Suppo Suppo

TDLBFD-003004 Compression & Multiplexing over Yes No Yes

LBFD-00300401 IP Header Compression Yes No Yes

TDLBFD-00300401 IP Header Compression Yes No Yes

LBFD-00300402 PPP MUX Yes No Yes

TDLBFD-00300402 PPP MUX Yes No Yes

LBFD-00300403 ML-PPP/MC-PPP Yes No Yes

TDLBFD-00300403 ML-PPP/MC-PPP Yes No Yes

GBFD-118604 Abis MUX Yes No No

GBFD-118612 Abis IPHC Yes No No

GBFD-118610 UDP MUX for A Transmission Yes No No

WRFD-050420 FP MUX for IP Transmission Yes Yes Yes

WRFD-050412 UDP MUX for Iu-CS N/A N/A N/A

Function Implementation in Macro, Micro, and LampSite Base Stations

Multiplexing Micro base stations do not support PPP MUX.

Header Micro base stations do not support IPHC or PPPHC.

PPP extended Micro base stations do not support MLPPP or MC-PPP.

Issue 01 (2016-09-30) Huawei Proprietary and Confidential 3

Transmission efficiency improvement is highly necessary in today's networks with ever-

Figure 2-1 Mechanisms for improving IP transmission efficiency

Issue 01 (2016-09-30) Huawei Proprietary and Confidential 4

3.2 Frame Protocol Multiplexing (for UMTS Only)

Issue 01 (2016-09-30) Huawei Proprietary and Confidential 5

The corresponding feature of FP MUX supported by Iub for UMTS is WRFD-050420 FP

3.2.2 Technical Description

3.2.2.1 Packet Format

Figure 3-1 Format of an FP MUX IP packet

The fields in Figure 3-1 are described as follows:

l User Identifier: specifies the owner of an FP PDU.

The parameters related to FP MUX are as follows:

Issue 01 (2016-09-30) Huawei Proprietary and Confidential 6

l FP MUX switch: specifies whether to enable FP MUX.