PDCP Header Compression (RAN15.0 - 01) PDF

WCDMA RAN
PDCP Header Compression Feature

Parameter Description
Issue 01
Date 2013-04-28
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2015. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior 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: [email protected]
Issue 01 (2013-04-28) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
WCDMA RAN
PDCP Header Compression Feature Parameter Description Contents
Contents
1 About This Document..................................................................................................................1

1.1 Scope..............................................................................................................................................................................1
1.2 Intended Audience..........................................................................................................................................................1
1.3 Change History...............................................................................................................................................................1
1.4 Differences Between Base Station Types.......................................................................................................................2
2 Overview.........................................................................................................................................4
2.1 Introduction to PDCP Header Compression...................................................................................................................4
2.2 PDCP Header Compression algorithms.........................................................................................................................4
2.2.1 IPHC............................................................................................................................................................................4
2.2.2 RoHC...........................................................................................................................................................................5
3 Technical Description...................................................................................................................6
3.1 Overview of PDCP Header Compression Technology..................................................................................................6
3.2 PDCP System Structure..................................................................................................................................................7
3.2.1 UMTS Structure for the PS Domain............................................................................................................................7
3.2.2 User Plane of the Protocol Stack for the PS Domain..................................................................................................7
3.2.3 PDCP Structure in the Radio Interface Protocol Architecture....................................................................................8
3.3 Process of PDCP Header Compression..........................................................................................................................9
3.3.1 Process of IPHC...........................................................................................................................................................9
3.3.2 Process of RoHC.......................................................................................................................................................13
4 Engineering Guidelines.............................................................................................................22
4.1 WRFD-011500 PDCP Header Compression (RFC2507)............................................................................................22
4.1.1 Requirements.............................................................................................................................................................22
4.1.2 Data Preparation........................................................................................................................................................23
4.1.3 Activation (Using MML Commands).......................................................................................................................23
4.1.4 MML Command Examples.......................................................................................................................................23
4.1.5 Activation (Using the CME)......................................................................................................................................23
4.1.6 Activation Observation..............................................................................................................................................24
4.1.7 Deactivation (Using MML Commands)....................................................................................................................25
4.1.9 Deactivation (Using the CME)..................................................................................................................................25
4.2 PDCP Header Compression (RoHC)............................................................................................................................25
Issue 01 (2013-04-28) Huawei Proprietary and Confidential ii

WCDMA RAN
PDCP Header Compression Feature Parameter Description Contents
4.2.1 Requirements.............................................................................................................................................................26
4.2.2 Data Preparation........................................................................................................................................................26
4.2.3 Activation (Using MML Commands).......................................................................................................................26
4.2.5 Activation (Using the CME)......................................................................................................................................26
4.2.6 Activation Observation..............................................................................................................................................27
4.2.7 Feature Deactivation..................................................................................................................................................28
4.2.9 Deactivation (Using the CME)..................................................................................................................................28
5 Parameters.....................................................................................................................................30
6 Counters........................................................................................................................................58
7 Glossary.........................................................................................................................................59
8 Reference Documents.................................................................................................................60
Issue 01 (2013-04-28) Huawei Proprietary and Confidential iii

WCDMA RAN
PDCP Header Compression Feature Parameter Description 1 About This Document
1 About This Document
1.1 Scope
This document describes PDCP Header Compression, including its technical principles and
engineering guidelines.
This document covers the following features:
l WRFD-011500 PDCP Header Compression (RFC2507)

l WRFD-010617 VoIP over HSPA/HSPA+
This document applies to the following NE types.
NE Type NE Model
RNC BSC6900, BSC6910
NodeB Macro Not involved
Micro Not involved
LampSite Not involved
1.2 Intended Audience

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

l Work with Huawei products
1.3 Change History

This section provides information about the changes in different document versions. There are
two types of changes, which are defined as follows:
Issue 01 (2013-04-28) Huawei Proprietary and Confidential 1

WCDMA RAN
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
RAN15.0 01(2013-04-28)
This issue does not include any changes.
RAN15.0 Draft A (2013-01-30)

Compared with issue 01 (2012-07-20) of RAN14.0, Draft A (2013-01-30) of RAN15.0 includes
the following changes.
Change Type Change Description Parameter Change
Feature change None. None.
Editorial change Incorporated the None.

WRFD-011501 PDCP
Header Compression
(RoHC) into the
WRFD-010617 VoIP over
HSPA/HSPA+.
1.4 Differences Between Base Station Types

Feature Support by Macro, Micro, and LampSite Base Stations
Feature ID Descriptio Supported by Controller Supported Supported LampSite

n (Y/N/NA) by Macro by Micro
(Y/N/NA) (Y/N/NA)
BSC6900 BSC6910
WRFD-01 PDCP Y Y N/A N/A N/A

1500 Header
Compressi
on
(RFC2507
)
NOTE
Y indicates that a feature is supported; N indicates that a feature is not supported; NA indicates that an NE is
not involved, that is, a feature does not require the support of the NE.

WCDMA RAN
The features described in this document are implemented in the same way on macro, micro, and
LampSite base stations.

WCDMA RAN
PDCP Header Compression Feature Parameter Description 2 Overview
2 Overview
2.1 Introduction to PDCP Header Compression

Theoretically, all the equivalent entities (MAC\RLC\PDCP) that communicate with the UE in
the RNC operate on radio links. The radio spectrum resource is precious and has to be utilized
economically. However, in the RTP/UDP/IP (for example, IPv4) protocol structure of the
services that will be widely used in the future, such as streaming services and VoIP, only the
header fields occupy 40 bytes. Transmitting the header fields of the RTP/UDP/IP protocol
consumes a large amount of radio link resource. Therefore, the RNC needs to compress the
headers of RTP/UDP/IP packets. The PDCP (Packet Data Convergence Protocol) Header
Compression undertakes this function.
2.2 PDCP Header Compression algorithms

PDCP header compression has two types of algorithms:
l IPHC (IP Header Compression): It can apply to PS services.

l RoHC (Robust Header Compression): It can apply to VoIP services.
2.2.1 IPHC
The IP protocol, transport protocols like TCP or UDP, and optional application protocols are
described in the header of a packet. Data in a header serves long-distance transport over multiple
links or hops in the network.
The header includes the following data:
l Source IP address
l Destination IP address
l Port information
l Protocol ID
l Sequence number
l Error checking information

WCDMA RAN
PDCP Header Compression Feature Parameter Description 2 Overview
IPHC uses the concept of packet stream context. A context is a set of data which contain field
values and value change patterns in the packet header.
For each packet stream, the context is formed at the compressor and the decompressor. After
the context is established on both sides, the compressor can compress the packets.
Figure 2-1 shows the block diagram of IPHC.
Figure 2-1 Block diagram of IPHC
To initiate compression of the headers of a packet stream, a full header carrying a Context
Identifier (CID) is transmitted over the link.
The compressor and decompressor store most fields of this full header as context. The context
consists of the fields of the header whose values are constant and thus need not be sent over the
link at all, or whose values change little between consecutive headers so that PDCP header
compression uses fewer bits to send the difference from the previous value compared with
sending the absolute value.
2.2.2 RoHC
The IPHC schemes are suitable for radio links with strong link-level checksums but are not
robust enough to handle high Bit Error Rate (BER) and long Round Trip Time (RTT). Because
high BER and long RTT are common on 3G links, an efficient and robust compression scheme
is needed. In this regard, the RoHC scheme is developed.
RoHC is an extensible framework consisting of the following profiles:
l RoHC uncompressed (profile 0): provides a way to send packets without any compression.
l RoHC RTP (profile 1): compresses packets with IP/UDP/RTP protocol headers.
l RoHC UDP (profile 2): compresses packets with IP/UDP protocol headers.
l RoHC ESP (profile 3): compresses packets with IP/ESP protocol headers.
The RoHC scheme uses Window-based Least Significant Bit (W-LSB) encoding for the
compression of dynamic fields in the protocol headers. Due to its feedback mechanism, RoHC
is robust on radio links with high BER and long RTT. It can achieve compression to as small as
1 byte, and thus it is more efficient than other compression schemes. Even though RoHC is
complex compared with earlier schemes, RoHC is suitable for wireless networks, which use the
very expensive radio spectrum resource.

WCDMA RAN
PDCP Header Compression Feature Parameter Description 3 Technical Description
3 Technical Description
3.1 Overview of PDCP Header Compression Technology

PDCP is an important component of the radio interface protocols on the L2. PDCP provides the
following functions:
l Transfer of packet data

l Header compression and decompression of IP data streams
l Lossless SRNS relocation
The general process of PDCP header compression is as follows:
l The redundant protocol headers are compressed before being transmitted on a link.
l The packets are decompressed to their original status when they are received at the other
end of the link.
PDCP header compression is applied for the following purposes:
l Reducing header overhead

When TCP segments in bulk transfers over a medium-speed link are tunneled, header
compression decreases the header overhead for IPv6/TCP from 19.5% to less than 1%, and
for tunneled IPv4/TCP from 11.7% to less than 1%. PDCP header compression greatly
reduces header overhead.
In addition, for voice services, a packet with a huge amount of data comes with significant
delay. PDCP header compression can also reduce this header overhead to a large extent.
l Shortening response time
For very low-speed links, echoing of characters may take longer than 100-200 ms because
of the time required to transmit large headers. 100-200 ms is the maximum time, and people
can tolerate without feeling that the system is sluggish within the time.
PDCP header compression shortens response time and improves the echoing rate of
characters.
l Reducing packet loss rate
After PDCP header compression, fewer bits are transmitted per packet. Therefore, the
packet loss rate is lower for a given Bit Error Rate (BER).

WCDMA RAN
3.2 PDCP System Structure

This section describes the following aspects of PDCP system structure:
l UMTS structure for the PS domain
l User plane of the protocol stack for the PS domain
l PDCP structure in the radio interface protocol architecture
3.2.1 UMTS Structure for the PS Domain

Figure 3-1 shows the UMTS structure for the Packet Switched (PS) domain.
The header compression function is provided by the RNC. Packet data is transferred from the
Internet or other external networks to the RNC by the GGSN and SGSN through the GPRS
Tunnel Protocol (GTP). The RNC relays the packet data to the UE.
Figure 3-1 UMTS structure for the PS domain
3.2.2 User Plane of the Protocol Stack for the PS Domain

As shown in Figure 3-2, the user plane has a layered protocol structure. It transfers user data
through data transfer control procedures.
After receiving data from the PS domain through the GTP tunnel, the RNC processes the data
as follows:
1. Perform header compression.
2. Send the compressed data to the RLC module on the lower layer.
3. Process the data at lower layers and then send the data to the UE over the Uu interface.
After receiving the data, the UE processes the data as follows:
1. Process the data on the lower layers.
2. Send the data to the PDCP sublayer and decompress it.
3. Send the data to the application layer.
That is the process of downlink data transfer. The uplink data transfer is of the same principle.

WCDMA RAN
Figure 3-2 User plane of the protocol stack for the PS domain
3.2.3 PDCP Structure in the Radio Interface Protocol Architecture

Figure 3-3 shows the PDCP structure in the radio interface protocol architecture.
Figure 3-3 PDCP structure in the radio interface protocol architecture
The PDCP entities are located in the PDCP sublayer. Every PDCP entity uses none, one, or
several different header compression protocols.
Every PS domain Radio Access Bearer (RAB) is associated with one Radio Bearer (RB), which
in turn is associated with one PDCP entity. A PDCP entity is mapped to either one acknowledged
mode (AM) RLC entity or one or two unacknowledged mode (UM) or transparent mode (TM)
RLC entities. The RLC entities depend on the RB characteristic (unidirectional or bidirectional)
and RLC mode.

WCDMA RAN
3.3 Process of PDCP Header Compression
3.3.1 Process of IPHC

The process of IP Header Compression (IPHC) involves the following algorithms:
l Compressible chain of sub-headers judgment algorithm

l Packet stream judgment algorithm
l Twice algorithm for TCP packet streams
l Header request algorithm for TCP packet streams
l Compression slow-start algorithm for non-TCP packet streams
l Periodic header refresh algorithm for non-TCP packet streams
Figure 3-4 shows the process of IPHC.

WCDMA RAN
Figure 3-4 Process of IPHC
Compressible Chain of Sub-headers Judgment Algorithm

This section gives rules on how the compressible chain of sub-headers is compressed.
A compressible sub-header can be one of the following headers:
l An IPv6 basic header

l An IPv6 extension header
l A TCP header

WCDMA RAN
l A UDP header
l An IPv4 header
The compressible chain of sub-headers extends from the beginning of the header.
l Up to but not including the first header that is not an IPv4 header, an IPv6 basic or extension
header, a TCP header, or a UDP header.
l Up to and including the first TCP header, UDP header, fragment header, Encapsulating
Security Payload (ESP) header, or IPv4 header for a fragment.
Whichever gives a shorter chain.
For example, both rules fit a chain of sub-headers that contains a fragment header and ends at a
tunneled IPX packet. Since the second rule gives a shorter chain, the compressible chain of sub-
headers ends at the fragment header.
The part of the header that is stored as context and compressed is the longest initial sequence of
entire sub-headers that is not larger than maximum control header size which is fixed to 18 bytes.
Packet Stream Judgment Algorithm

To achieve the best compression rates, packets should be grouped together so that the packets
in the same packet stream have similar headers.
The compressor uses whatever criterion it finds appropriate to group packets into packet streams.
To determine which packet stream a packet belongs to, a compressor may proceed as follows:
1. Check the compressible chain of sub-headers.

2. Check the contents of an upper layer protocol header.
3. Check whether the defining fields of the compressible chain of sub-headers are changed or
not.
NOTE
l If too many fields are used for identification, performance might suffer because more CIDs will be
used and the wrong CIDs might be reused when new flows need CIDs.
l If too few fields are used for identification, performance might suffer because there are too frequent
changes to the context.
The CID spaces for TCP and non-TCP are separate. Therefore, a TCP CID and a non-TCP CID
never identify the same context even if they have the same value. This doubles the available
CID space when the same number of bits is used for the CIDs.
Max CID value for TCP connections defines the maximum CID value for TCP connections, and
it is fixed to 15.
Max CID value for non-TCP connections defines the maximum CID value for non-TCP
connections, and it is fixed to 15.
Twice Algorithm for TCP Packet Streams

In this algorithm, the decompressor computes a checksum to check whether its context has been
updated properly or not.

WCDMA RAN
If the checksum fails, the error is assumed to be caused by a lost segment that did not update the
context properly. If the lost segment contained the same delta as the current, the delta of the
current segment is then added to the context again.
The decompressor computes the checksum again.
l If this repair is successful, the decompressor continues to deliver packets.

l If this repair fails, the delta is applied once more. That is, the delta is added and the checksum
is computed again.
Analysis of traces of diverse TCP bulk transfers shows that applying the delta of the current
segment one or two times repairs the context for 83% to 99% of all single-segment losses in the
data stream.
For the acknowledgment stream, the success rate is lower because of the delayed
acknowledgment mechanism of TCP. The Twice mechanism repairs the context for 53% to 99%
of the losses in the acknowledgment stream.
Header Request Algorithm for TCP Packet Streams

When the Twice algorithm fails, another recovery mechanism, called Header Request, is
available for repairing the context at the decompressor.
When failing to repair the context after a loss, the decompressor requests a full header from the
compressor. This is possible only when bidirectional links are used, because the decompressor
must communicate with its compressor. The decompressor sends a context state message to the
compressor to indicate that one or more contexts are invalid.
Compression Slow-Start Algorithm for Non-TCP Packet Streams

To allow the decompressor to recover quickly from loss of a full header that has changed the
context, full headers are sent periodically with an exponentially increasing period after a change
in the context, as shown in Figure 3-5. This technique avoids an exchange of messages between
compressor and decompressor. Such exchanges can be costly for wireless mobiles, because more
power is consumed by the transmitter and delay can be introduced by switching between
transmitter and receiver.
Figure 3-5 Exponentially increasing period after a change
Figure 3-5 shows how packets are sent after a change in the context. The compressor keeps a
variable F_PERIOD for each non-TCP packet stream. The variable keeps track of how many
compressed headers are sent between full headers. When the headers of a non-TCP packet stream
change so that its context changes, a full header is sent and F_PERIOD is set to 1. After
F_PERIOD compressed headers are sent, a full header is sent. F_PERIOD is doubled each time
a full header is sent during compression slow-start.

WCDMA RAN
Periodic Header Refresh Algorithm for Non-TCP Packet Streams

To avoid losing too many packets if a receiver loses its context, there is an upper limit to the
number of compressed headers in a non-TCP packet stream. The maximum number of
compressed non-TCP headers is 256. These compressed headers might be sent between header
refreshes. If a packet is to be sent and the maximum number of compressed non-TCP headers
have been sent after the last full header was sent for this packet stream, a full header must be
sent.
To avoid long durations of disconnection for low data rate packet streams, there is also an upper
limit, the maximum time for sending compressed headers which is fixed to 5s, on the time
between full headers in a non-TCP packet stream. If a packet is to be sent and more than
maximum time for sending compressed headers seconds have passed after the last full header
was sent for this packet stream, a full header must be sent.
3.3.2 Process of RoHC

This section describes the modes and states used in the process of Robust Header Compression
(RoHC).
The features of RoHC supported by the RNC are as follows:
l All profiles: 0 (uncompressed), 1 (RTP), 2 (UDP), and 3 (ESP)
l Compression of both IPv4 and IPv6 headers
l All states and modes
l All RoHC packet types, including all extensions: 0, 1, 2, and 3
l Local repair mechanisms
l List compression
l All encoding methods except timer-based compression of RTP timestamp
The profiles supported by the RNC are defined by the profile number, profile 1 instance, profile
2 instance, profile 3 instance, and profile 4 instance factors. The values of them are described
as follows.
Factor Value Remarks
Profile number 4 -
Profile 1 instance 0 No Compress
Profile 2 instance 1 RTP
Profile 3 instance 2 UDP
Profile 4 instance 3 ESP
RoHC can be characterized as an interaction between two state machines, one compressor
machine and one decompressor machine. The compressor and the decompressor have three states
each, which in many ways are related to each other even if the meanings of the states are different
from the two parties. Both machines start in the lowest compression state and transit gradually
to higher states.

WCDMA RAN
Compressor States of RoHC

Figure 3-6 shows the compression process of RoHC.
Figure 3-6 Compression process of RoHC
After getting a chain of sub-headers, the compressor creates a CID or finds a proper CID. The
CID is equal to or less than the value of downlink maximum CID which is fixed to 3. On the
decompressor side, CID is restricted by uplink maximum CID which is fixed to 3.
The RoHC compressor operates in the following three states:
l Initialization and Refresh (IR)

WCDMA RAN
l First Order (FO)

l Second Order (SO)
Figure 3-7 shows the basic principle of the compressor states of RoHC.
Figure 3-7 Compressor states of RoHC
The compressor always starts in IR state. In this state, it sends uncompressed packets to establish
the context on the decompressor side. After it gains the confidence that the decompressor has
the context information, the compressor moves to higher states of operation, either through FO
state to SO state or directly to SO state. The compressor dynamically changes its states depending
on link conditions and error conditions as observed and reported by the decompressor.
NOTE
The detailed state transitions of the compressor vary with the mode of RoHC. For detailed information,
see Modes of RoHC.
Decompressor States of RoHC

Figure 3-8 shows the decompression process of RoHC.

WCDMA RAN
Figure 3-8 Decompression process of RoHC
The RoHC decompressor operates in the following three states:
l No Context
l Static Context
l Full Context
Figure 3-9 shows the decompressor states of RoHC.

WCDMA RAN
Figure 3-9 Decompressor states of RoHC
The decompressor starts in No Context state, as it has no context information available at the
beginning of a packet flow. The successful decompression of an IR packet (containing both static
and dynamic information) sent from the compressor creates the context information on the
decompressor side. Then, the decompressor can move to the Full Context state when it has
received both static and dynamic information.
When in Full Context state, the decompressor moves to lower states only upon repeated failures.
When moving to a lower state, it moves to the Static Context state and then hopefully can move
back to the Full Context state by restoring the context through successful decompression of FO
packets. If it fails to decompress FO packets, it moves to the No Context state. In this case, the
compressor needs to send IR packets to restore the context at the decompressor.
Modes of RoHC
The RoHC framework defines the following three modes of operation:
l Unidirectional Mode (U-mode)

l Bidirectional Optimistic Mode (O-mode)
l Bidirectional Reliable Mode (R-mode)
The reliability of these working modes and overheads used for transmitting feedback are
different.
The initial operating mode of the compressor must be U-Mode, and then gradually transits to
O-Mode or R-Mode. The mode can be changed from any one to the other two, as shown in
Figure 3-10.

WCDMA RAN
Figure 3-10 The transitions of operation modes
In the current version, only the mode transitions between U-mode and O-mode are supported.
The three modes of operation are described as follows:
l U-mode
In U-mode, packets are sent in only one direction, that is, from the compressor to the
decompressor. In the case that a return path or feedback channel is unavailable, RoHC can
still be used.
The compressor uses the optimistic approach, that is, sending enough information to
reconstruct the context and to maintain the integrity of the decompressor context. The
context updating information is sent periodically to ensure context synchronization. A
periodic timeout mechanism is used for the compressor to transit to lower states and send
FO and IR state packets. Figure 3-11 shows the state transitions of the compressor in U-
mode.

WCDMA RAN
Figure 3-11 State diagram for U-mode
Compared with other modes of operation, U-mode results in lower compression gain. The
compressor can move to other modes of operation if it receives a feedback packet from the
decompressor. As the decompressor can estimate link conditions and knows the availability of
the feedback channel, it may choose to move to other modes of operation.
l O-mode
In O-Mode, the decompressor can send feedback in the form of requests for error recovery
(negative acknowledgements, NACKs) or indication of successful context update
(acknowledgements, ACKs). Figure 3-12 shows state transitions of the compressor in
optimistic mode upon receiving feedback packets from the decompressor and using the
optimistic approach.

WCDMA RAN
Figure 3-12 State diagram for O-mode
The compressor moves to higher states by using the optimistic approach or after receiving ACKs
from the decompressor.
The decompressor sends ACKs for IR packets. For other context updating packets, it sends ACKs
optionally. To recover from repeated failures, it sends NACKs or static NACKs (depending on
its state).
l R-mode
In R-mode, the feedback channel is used often to avoid packet loss caused by context
invalidation. R-mode uses the secure reference principle rather than the optimistic approach
as in other modes. Figure 3-13 shows the state transitions of the compressor in R-mode.
Figure 3-13 State diagram for R-mode

WCDMA RAN
R-mode improves the robustness against packet loss and bit errors. Compared with O-mode, R-
mode has a very low probability of context invalidation but may result in a larger number of
damaged headers being delivered when the context is invalidated.
Confidence of the compressor depends on acknowledgements from the decompressor for every
context updating packet. However, not every packet in R-mode updates the context. According
to the secure reference principle, the compressor should send the context updating packets
periodically and repeat until acknowledgement is received from the decompressor.

WCDMA RAN
PDCP Header Compression Feature Parameter Description 4 Engineering Guidelines
4 Engineering Guidelines
4.1 WRFD-011500 PDCP Header Compression (RFC2507)
4.1.1 Requirements
l Dependencies on Hardware
The UE supports this feature.
l Dependencies on Other Features
This feature does not depend on other features.
l License
For details about how to activate the license, see License Management Feature Parameter
Description.
Table 4-1 BSC6900&BSC6910
Feature Feature License License Supporte License Sal

ID Name Control Item in d NE Allocatio es
Item ID the DSP Type n for Un
LICUSA Multiple it
GE Operator
Comman s
d Output
WRFD-01 PDCP LQW1PD PDCP BSC6900 Method 2 per

1500 Header CPHO01R Header BSC6910 Mb
Compressi ES Compressi ps
on on
(RFC2507 (RFC2507
) ) (per
Mbps)

WCDMA RAN
If RAN Sharing or MOCN is enabled, the licensed value is allocated among the primary
and secondary operators according to the value of the "License Allocation for Multiple
Operators parameter".
Method 2: it is recommended that the license allocation proportion of a feature be consistent
with that of the capacity license item "PS throughput only-kbps". The licensed values can
be set by running the SET LICENSE command. If the FeatureResAssignMode parameter
in this command is set to AutoAssign, the licensed values are automatically allocated
among the primary and secondary operators. If the FeatureResAssignMode parameter in
this command is set to ManualAssign, you also need to specify the related license
parameters to implement manual license allocation.
4.1.2 Data Preparation

None.
4.1.3 Activation (Using MML Commands)

Run the RNC MML command SET UCORRMALGOSWITCH to select the
CFG_PDCP_RFC2507_HC_SWITCH check box under the Channel configuration strategy
switch parameter.
4.1.4 MML Command Examples

//Activating PDCP Header Compression (RFC2507).
SET UCORRMALGOSWITCH: CfgSwitch=CFG_PDCP_RFC2507_HC_SWITCH-1;
4.1.5 Activation (Using the CME)

NOTE
When configuring the Service Awareness-based QoS Management feature 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 on the CME.
Set parameters on the CME according to the operation sequence in Table 4-2. For instructions
on how to perform the CME single configuration, see CME Single Configuration Operation
Guide.
Step 2 (Optional) Modify objects in batches on the CME. (CME batch modification center)
----End
To modify objects, such as RNCs, NodeBs, cells, and external UMTS cells, in batches, click
on the CME to start the batch modification wizard. For instructions on how to perform a
batch modification through the CME batch modification center, press F1 while running the
wizard to obtain online help.

WCDMA RAN
Table 4-2 Configuring the parameter on the CME
SN MO NE Parameter Name Paramete Configura

r ID ble in CME
Batch
Modificati
on Center
1 UCORRMAL RNC Channel CfgSwitch Yes

GOSWITCH Configuration (BSC6900
Strategy Switch ,BSC6910
)
4.1.6 Activation Observation

1. On the LMT, click Trace > UMTS Service, and double-click Uu Interface Trace to
display the Uu Interface Trace window.
2. Set Cell config, Uu Message Type, and Save File, and then click Submit.
3. Enable the UE to establish PS BE services.
4. Check the IE rb-InformationSetupList of the RB Setup message in the traced data:
l If this message contains the IE headerCompressionInfoList, as shown in Figure 4-1,
this feature has been activated.
l If this message does not contain the IE headerCompressionInfoList, this feature has
not been activated.
Figure 4-1 rb-InformationSetupList message

WCDMA RAN
4.1.7 Deactivation (Using MML Commands)

Run the RNC MML command SET UCORRMALGOSWITCH to clear the
CFG_PDCP_RFC2507_HC_SWITCH check box under the Channel configuration strategy
switch parameter.

//Deactivating PDCP Header Compression (RFC2507).
SET UCORRMALGOSWITCH: CfgSwitch=CFG_PDCP_RFC2507_HC_SWITCH-0;
4.1.9 Deactivation (Using the CME)

NOTE
When configuring the HSUPA Adaptive Transmission feature on the CME, perform a single configuration
first, and then perform a batch modification if required.
Step 1 Configure a single object (such as a cell) on the CME.

Set parameters on the CME according to the operation sequence described in Table 4-3. For
instructions on how to perform the CME single configuration, see CME Single Configuration
Operation Guide
----End
To modify objects in batches, click on the CME to start the batch modification wizard. For
instructions on how to perform a batch modification through the CME batch modification center,
press F1 while running the wizard to obtain online help.SET UCORRMALGOSWITCH to clear
the CFG_PDCP_RFC2507_HC_SWITCH check box under the Channel configuration
strategy switch parameter.
Table 4-3 Configuring the parameters on the CME
SN Managed NE Parameter Parameter ID Configurable

Object (MO) Name in CME Batch
Modification
Center

GOSWITCH Configurati (BSC6900,BSC6910
on Strategy )
Switch
4.2 PDCP Header Compression (RoHC)

WCDMA RAN
4.2.1 Requirements
l Dependencies on Hardware
The UE supports this feature.
l Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
4.2.2 Data Preparation

None.
4.2.3 Activation (Using MML Commands)

1. Run the RNC MML command SET UCORRMALGOSWITCH. In this step, select the
CFG_PDCP_RFC3095_HC_SWITCH check box under the parameter Channel
configuration strategy switch. Select the following parameters in the Compatibility
Switch list box:
l CMP_RAB_5_CFG_ROHC_SWITCH

//Activating PDCP Header Compression (RoHC) SET UCORRMALGOSWITCH:
CfgSwitch=CFG_PDCP_RFC3095_HC_SWITCH-1,
CmpSwitch=CMP_RAB_5_CFG_ROHC_SWITCH-1&CMP_RAB_6_CFG_ROHC_SWITC
H-1&CMP_RAB_7_CFG_ROHC_SWITCH-1&CMP_RAB_8_CFG_ROHC_SWITCH-1&C
MP_RAB_9_CFG_ROHC_SWITCH-1;
4.2.5 Activation (Using the CME)

NOTE
When configuring the Service Awareness-based QoS Management feature on the CME, perform a single
configuration first, and then perform a batch modification if required.
Step 1 Configure a single object on the CME.

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

WCDMA RAN
To modify objects, such as RNCs, NodeBs, cells, and external UMTS cells, in batches, click
on the CME to start the batch modification wizard. For instructions on how to perform a
batch modification through the CME batch modification center, press F1 while running the
wizard to obtain online help.

r ID ble in CME
Batch
Modificati
on Center

)
Compatibility Switch CmpSwitc Yes

h
(BSC6900
,BSC6910
)
4.2.6 Activation Observation

1. On the LMT, click Trace > UMTS Service, and double-click Uu Interface Trace to
display the Uu Interface Trace window.
2. Set Cell config, Uu Message Type, and Save File, and then click Submit.
3. Enable the UE to establish VoIP services.
4. Check the IE rb-InformationSetupList of the RB Setup message in the traced data:
l If this message contains the IE headerCompressionInfoList, as shown in Figure 4-2,
this feature has been activated.
l If this message does not contain the IE headerCompressionInfoList, this feature has
not been activated.

WCDMA RAN
Figure 4-2 rb-InformationSetupList message
4.2.7 Feature Deactivation

Run the RNC MML command SET UCORRMALGOSWITCH (CME single configuration:
UMTS Radio Global Configuration Express > Connection_Oriented RRM Switch
Configuration > Connection Oriented Algorithm Switches; CME batch modification center:
Modifying RNC Parameters in Batches). In this step, deselect the
CFG_PDCP_RFC3095_HC_SWITCH check box under the parameter Channel
configuration strategy switch. Disable the following switches in the Compatibility Switch
list box:

//Deactivating PDCP Header Compression (RoHC) SET UCORRMALGOSWITCH:
CfgSwitch=CFG_PDCP_RFC3095_HC_SWITCH-0,
CmpSwitch=CMP_RAB_5_CFG_ROHC_SWITCH-0&CMP_RAB_6_CFG_ROHC_SWITC
H-0&CMP_RAB_7_CFG_ROHC_SWITCH-0&CMP_RAB_8_CFG_ROHC_SWITCH-0&C
MP_RAB_9_CFG_ROHC_SWITCH-0;
4.2.9 Deactivation (Using the CME)

NOTE
When configuring the HSUPA Adaptive Transmission feature on the CME, perform a single configuration
first, and then perform a batch modification if required.

WCDMA RAN
Step 1 Configure a single object (such as a cell) on the CME.
Set parameters on the CME according to the operation sequence described in Table 4-5. For
instructions on how to perform the CME single configuration, see CME Single Configuration
Operation Guide
----End
To modify objects in batches, click on the CME to start the batch modification wizard. For
instructions on how to perform a batch modification through the CME batch modification center,
press F1 while running the wizard to obtain online help.SET UCORRMALGOSWITCH to clear
the CFG_PDCP_RFC2507_HC_SWITCH check box under the Channel configuration
strategy switch parameter.

r ID ble in CME
Batch
Modificati
on Center

)
Compatibility Switch CmpSwitc Yes

h
(BSC6900
,BSC6910
)

WCDMA RAN
PDCP Header Compression Feature Parameter Description 5 Parameters
5 Parameters
Table 5-1 Parameters
Parame NE MML Feature Feature Description

ter ID Comma ID Name
nd
CfgSwit BSC690 SET WRFD- DC- Meaning:

ch 0 UCORR 010699 HSDPA Channel configuration strategy switch group.
MALG WRFD- +MIMO
OSWIT 1.
010698 HSPA+ CFG_DC_MIMO_DYNAMIC_SELECT_SWITCH:
CH Uplink
WRFD- When this switch is turned on, the RNC determines
11.5Mbi whether to enable the DC-HSDPA or MIMO feature for
010652
t/s per a newly admitted user based on the cell load and the
WRFD- User number of HSDPA users.
010693
SRB 2. CFG_DL_BLIND_DETECTION_SWITCH: When
WRFD- over the switch is on, the DL blind transport format detection
010694 HSDPA function is used for single SRB and AMR+SRB bearers.
WRFD- DL Note that the UE is only required to support the blind
010697 64QAM transport format stipulated in 3GPP 25.212 section
WRFD- +MIMO 4.3.1.
010696 UL 3. CFG_EDPCCH_BOOSTING_SWITCH: When the
WRFD- 16QAM switch is on, Boosting can be configured for the HSUPA
151209 E- service.
DPCCH 4. CFG_FREE_USER_SWITCH: When this switch is
WRFD-
Boostin turned on, special handling for free access user is
150250
g enabled.
WRFD-
DC- 5. CFG_HSDPA_64QAM_SWITCH: When the switch
010101
HSDPA is on, 64QAM can be configured for the HSDPA
WRFD- service.
Macro-
010510
Micro 6. CFG_HSDPA_DCMIMO_SWITCH: When this
WRFD- DC- switch is turned on, DC+MIMO can be configured for
011500 HSDPA the HSDPA service.
WRFD- 3C- 7. CFG_HSDPA_DC_SWITCH: When the switch is
010686 HSDPA on, DC can be configured for the HSDPA service.

WCDMA RAN

nd
WRFD- 3GPP 8. CFG_HSDPA_MIMO_SWITCH: When the switch

010687 R9 is on, MIMO can be configured for the HSDPA service.
WRFD- Specific 9. CFG_HSDPA_MIMO_WITH_64QAM_SWITCH:
010684 ations When the switch is on and the switches for 64QAM and
WRFD- 3.4/6.8/1 MIMO are on, 64QAM+MIMO can be configured for
010683 3.6/27.2 the HSDPA service
Kbps 10. CFG_HSDPA_4C_MIMO_SWITCH: Whether the
WRFD-
RRC 4C-HSDPA+MIMO feature is allowed for HSDPA
0106150
Connect services. When this switch is turned on, the MC-
2
ion and HSDPA+MIMO (4C-HSDPA+MIMO and 3C-HSDPA
WRFD- Radio +MIMO) feature is allowed for HSDPA services.
0106150 Access
3 11. CFG_HSDPA_4C_SWITCH: Whether the 3C-
Bearer
HSDPA or 4C-HSDPA feature is allowed for HSDPA
WRFD- Establis
services. When this switch is turned on, the 3C-HSDPA
0106150 hment
or 4C-HSDPA feature is allowed for HSDPA services.
1 and
Release 12. CFG_HSDPA_DBMIMO_SWITCH: Whether the
WRFD- DB-HSDPA+MIMO feature is allowed for HSDPA
0106150 PDCP services. When this switch is turned on, the DB-HSDPA
4 Header +MIMO feature is allowed for HSDPA services.
WRFD- Compre
ssion 13. CFG_HSDPA_DB_SWITCH: Whether the DB-
170203 HSDPA feature is allowed for HSDPA services. When
(RFC25
WRFD- 07) this switch is turned on, the DB-HSDPA feature is
150207 allowed for HSDPA services.
CPC -
WRFD- 14. CFG_HSPA_DTX_DRX_SWITCH: When the
DTX /
150227 switch is on, DTX_DRX can be configured for the
DRX
WRFD- HSPA service.
CPC -
0206050 15. CFG_HSPA_HSSCCH_LESS_OP_SWITCH:
HS-
4 When the switch is on, HS-SCCH Less Operation can
SCCH
WRFD- be configured for the HSPA service.
less
150223 operatio 16. CFG_HSUPA_16QAM_SWITCH: When the
WRFD- n switch is on, 16QAM can be configured for the HSUPA
150209 service.
2x2
WRFD- MIMO 17. CFG_HSUPA_DC_SWITCH: When this switch is
010615 turned on, the DC-HSUPA function can be enabled for
Downlin HSUPA services.
WRFD- k
18. CFG_IMS_SUPPORT_SWITCH: When the switch
010617 64QAM
is on and the IMS license is activated, the RNC supports
WRFD- Combin IMS signaling.
020134 ation of
19.
One CS
CFG_LOSSLESS_DLRLC_PDUSIZECHG_SWITC
Service
H: Whether the UTRAN supports the function of
and Two
lossless RLC PDU size change. When this switch is
PS
turned on, downlink channel reconfiguration between
Services
the DCH and HS-DSCH does not cause RLC PDU size

WCDMA RAN

nd
Combin change which results in packet loss. This function takes

ation of effect only on the UEs enabled with this function. For
Three details about this function, see 3GPP TS 25.331.
PS 20. CFG_LOSSLESS_RELOC_CFG_SWITCH:
Services When the switch is on and the UE supports lossless
Combin relocation, the RNC configures lossless relocation for
ation of PDCP parameters if the requirements of RLC mode,
Two PS discard mode, and sequential submission are met. Then,
Services lossless relocation is used for the UE.
Combin 21. CFG_MULTI_RAB_SWITCH: When the switch is
ation of on, the RNC supports multi-RABs combinations such
One CS as 2CS, 2CS+1PS, 1CS+2PS, and 2PS.
Service 22.
and CFG_PDCP_IPV6_HEAD_COMPRESS_SWITCH:
Three When the switch is on and the PDCP Header
PS compression license is activated, the PDCP header
Services compression algorithm for IPv6 is used at the RNC.
Uplink 23. CFG_PDCP_RFC2507_HC_SWITCH: When the
Control switch is on and the PDCP Header compression license
Channel is activated, the PDCP RFC2507 header compression
OLPC algorithm is used for the RNC.
4C- 24. CFG_PDCP_RFC3095_HC_SWITCH: When the
HSDPA switch is on and the PDCP ROHC license is activated,
the PDCP RFC3095 header compression algorithm is
DB-
used for the RNC.
HSDPA
+MIMO 25. CFG_PTT_SWITCH: When this switch is on, the
RNC identifies the PTT user based on the QoS attributes
Lossless in the RAB assignment request message. Then, the PTT
SRNS users are subject to special processing.
Relocati
on 26. CFG_RAB_REL_RMV_HSPAPLUS_SWITCH:
When this switch is on and if an RAB release is
MC- performed, the RNC decides whether to fall back a
HSDPA certain HSPA(HSPA+) feature based on the
+MIMO requirement of remaining traffic carried by the UE. That
DB- is, if an HSPA+ feature is required by the previously
HSDPA released RAB connection but is not required in the
initial bearer policy of the remaining traffic, the RNC
Multiple
falls back the feature to save the transmission resources.
RAB
The HSPA+ features that support the fallback are
Package
MIMO, 64QAM, MIMO+64QAM, UL 16QAM, DC-
(PS
HSDPA, UL TTI 2ms, and DC-HSUPA.
RAB >=
2) 27. CFG_RCS_E_SWITCH: Indicates whether to
enable the RCS-e (Rich Communication Suit enhanced)
VoIP service that supports voice services carried in the CS
over domain and video services carried in the PS domain.

WCDMA RAN

nd
HSPA/ When this switch is turned off, the RCS-e service is
HSPA+ disabled. When this switch is turned on, the RCS-e
Push to service is enabled.
Talk 28.
CFG_FACH_AM_RLC_RETRANSMIT_PARA_SW
ITCH: Switch for configuring AM RLC retransmission
parameters for UEs in the CELL_FACH state. (1) When
this switch is turned on and the cell-level parameters in
the command "ADD UCELLFACHCONGCTRL" are
not set, the parameters "TimerPoll" and
"NoDiscardMaxDAT" parameters in the command
"SET UFACHCFGPARA" are used as AM RLC
retransmission parameters specific to PS services and
SRBs. (2) When this switch is turned on and the cell-
level parameters in the command "ADD
UCELLFACHCONGCTRL" are set, the parameters
"TimerPollForFachPsTRB" and "TimerPollFor-
FachSRB" in the command "ADD UCELLFACH-
CONGCTRL" are used as AM RLC retransmission
parameters specific to PS services and SRBs,
respectively. (3) When this switch is turned off, the
parameters "TimerPoll" and "NoDiscardMaxDAT" in
the command "ADD UTYPSRBRLC" are used as AM
RLC retransmission parameters specific to SRBs, and
the parameters "TimerPoll" and "NoDiscardMaxDAT"
in the command "ADD UTYPRABRLC" are used as
AM RLC retransmission parameters specific to PS
services.
29.
CFG_DCH_SRB_AM_RLC_RETRANS_PARA_SW
ITCH: Switch controlling the configuration mode of
AM RLC SDU retransmission parameters for UEs in
the CELL_DCH state. When this switch is turned on
and UEs in the CELL_DCH state, on the RNC, the
transmitting side of an AM RLC entity uses the values
of the "TimerPoll" and "NoDiscardMaxDAT"
parameters in the "ADD UTYPSRBDCHRNCRLC" or
"MOD UTYPSRBDCHRNCRLC" command for SDU
retransmission. When this switch is turned off or UEs
not in the CELL_DCH state, on the RNC, the
transmitting side uses the values of these parameters in
the "ADD UTYPSRBRLC" or "MOD UTYPSRBRLC"
command for SDU retransmission.
30. CFG_HSDPA_SFDC_SWITCH: Whether to
enable the SFDC HSDPA function for UEs processing
HSDPA services. When this switch is set to on, the

WCDMA RAN

nd
SFDC HSDPA function is enabled for UEs processing

HSDPA services. This switch is reserved for the MF-
HSDPA(multiflow HSDPA) function and cannot be
used in the current version.
31. CFG_HSDPA_DF3C_SWITCH: Whether to
enable the DF3C HSDPA function for UEs processing
DF3C HSDPA function is enabled for UEs processing
32. CFG_SRB_BICASTING_SWTICH: Whether to
validate the SRB bicasting function for SRBs carried
over HSDPA when the multiflow HSDPA function is
enabled. When this switch is set to on in a cell enabled
with the inter-NodeB multiflow function, SRB PDUs in
AM RLC mode are transmitted simultaneously in all
cells. When this switch is set to off, SRB PDUs in AM
RLC mode can only be transmitted in one cell. PDU is
short for packet data unit. AM is short for acknowledged
mode. UM is short for unacknowledged mode. TM is
short for transparent mode. SRB PDUs in UM or TM
RLC mode can only be transmitted in the primary
sector. This switch is reserved for the MF-HSDPA
(multiflow HSDPA) function and cannot be used in the
current version.
GUI Value Range:
CFG_DL_BLIND_DETECTION_SWITCH,
CFG_HSDPA_64QAM_SWITCH,
CFG_HSDPA_MIMO_SWITCH,
CFG_HSPA_DTX_DRX_SWITCH,
CFG_HSPA_HSSCCH_LESS_OP_SWITCH,
CFG_IMS_SUPPORT_SWITCH,
H, CFG_LOSSLESS_RELOC_CFG_SWITCH,
CFG_MULTI_RAB_SWITCH,
CFG_PDCP_IPV6_HEAD_COMPRESS_SWITCH,
CFG_PDCP_RFC2507_HC_SWITCH,
CFG_HSDPA_MIMO_WITH_64QAM_SWITCH,
CFG_HSDPA_DC_SWITCH,
CFG_HSUPA_16QAM_SWITCH,
CFG_RAB_REL_RMV_HSPAPLUS_SWITCH,
CFG_PTT_SWITCH,
CFG_EDPCCH_BOOSTING_SWITCH,
CFG_HSDPA_DCMIMO_SWITCH,

WCDMA RAN

nd
CFG_FREE_USER_SWITCH,
CFG_DC_MIMO_DYNAMIC_SELECT_SWITCH,
CFG_HSUPA_DC_SWITCH,
CFG_HSDPA_4C_MIMO_SWITCH,
CFG_HSDPA_4C_SWITCH,
CFG_HSDPA_DBMIMO_SWITCH,
CFG_HSDPA_DB_SWITCH,
CFG_RCS_E_SWITCH,
ITCH,
ITCH, CFG_HSDPA_SFDC_SWITCH,
CFG_HSDPA_DF3C_SWITCH,
CFG_SRB_BICASTING_SWTICH
Unit: None
Actual Value Range:
CFG_PTT_SWITCH,
CFG_RCS_E_SWITCH,
ITCH,

WCDMA RAN

nd
Default Value:
CFG_DC_MIMO_DYNAMIC_SELECT_SWITCH:
0,CFG_DL_BLIND_DETECTION_SWITCH:
1,CFG_EDPCCH_BOOSTING_SWITCH:
0,CFG_FREE_USER_SWITCH:
0,CFG_HSDPA_64QAM_SWITCH:
1,CFG_HSDPA_DCMIMO_SWITCH:
0,CFG_HSDPA_DC_SWITCH:
0,CFG_HSDPA_MIMO_SWITCH:
1,CFG_HSDPA_MIMO_WITH_64QAM_SWITCH:
0,CFG_HSDPA_4C_MIMO_SWITCH:
0,CFG_HSDPA_4C_SWITCH:
0,CFG_HSDPA_DBMIMO_SWITCH:
0,CFG_HSDPA_DB_SWITCH:
0,CFG_HSPA_DTX_DRX_SWITCH:
0,CFG_HSPA_HSSCCH_LESS_OP_SWITCH:
0,CFG_HSUPA_16QAM_SWITCH:
0,CFG_HSUPA_DC_SWITCH:
0,CFG_IMS_SUPPORT_SWITCH:
1,CFG_LOSSLESS_DLRLC_PDUSIZECHG_SWIT
CH:0,CFG_LOSSLESS_RELOC_CFG_SWITCH:
0,CFG_MULTI_RAB_SWITCH:
1,CFG_PDCP_IPV6_HEAD_COMPRESS_SWITCH:
0,CFG_PDCP_RFC2507_HC_SWITCH:
0,CFG_PTT_SWITCH:
0,CFG_RAB_REL_RMV_HSPAPLUS_SWITCH:
0,CFG_RCS_E_SWITCH:
0,CFG_FACH_AM_RLC_RETRANSMIT_PARA_S
WITCH:
0,CFG_DCH_SRB_AM_RLC_RETRANS_PARA_S
WITCH:0,CFG_HSDPA_SFDC_SWITCH:
0,CFG_HSDPA_DF3C_SWITCH:
0,CFG_SRB_BICASTING_SWTICH:0

WCDMA RAN

nd
CfgSwit BSC691 SET WRFD- DC- Meaning:

ch 0 UCORR 010699 HSDPA Channel configuration strategy switch group.
MALG WRFD- +MIMO
OSWIT 1.
010698 HSPA+ CFG_DC_MIMO_DYNAMIC_SELECT_SWITCH:
CH Uplink
WRFD- When this switch is turned on, the RNC determines
010652 11.5Mbi whether to enable the DC-HSDPA or MIMO feature for
t/s per a newly admitted user based on the cell load and the
WRFD- User
010693 number of HSDPA users.
SRB 2. CFG_DL_BLIND_DETECTION_SWITCH: When
WRFD- over
010694 the switch is on, the DL blind transport format detection
HSDPA function is used for single SRB and AMR+SRB bearers.
WRFD- Note that the UE is only required to support the blind
DL
010697 transport format stipulated in 3GPP 25.212 section
64QAM
WRFD- +MIMO 4.3.1.
010696 3. CFG_EDPCCH_BOOSTING_SWITCH: When the
UL
WRFD- 16QAM switch is on, Boosting can be configured for the HSUPA
151209 service.
E-
WRFD- DPCCH 4. CFG_FREE_USER_SWITCH: When this switch is
150250 Boostin turned on, special handling for free access user is
WRFD- g enabled.
010101 DC- 5. CFG_HSDPA_64QAM_SWITCH: When the switch
WRFD- HSDPA is on, 64QAM can be configured for the HSDPA
010510 service.
Macro-
WRFD- Micro 6. CFG_HSDPA_DCMIMO_SWITCH: When this
011500 DC- switch is turned on, DC+MIMO can be configured for
HSDPA the HSDPA service.
WRFD-
010686 3C- 7. CFG_HSDPA_DC_SWITCH: When the switch is
HSDPA on, DC can be configured for the HSDPA service.
WRFD-
010687 3GPP 8. CFG_HSDPA_MIMO_SWITCH: When the switch
R9 is on, MIMO can be configured for the HSDPA service.
WRFD-
010684 Specific 9. CFG_HSDPA_MIMO_WITH_64QAM_SWITCH:
ations When the switch is on and the switches for 64QAM and
WRFD- MIMO are on, 64QAM+MIMO can be configured for
010683 3.4/6.8/1
3.6/27.2 the HSDPA service
WRFD- Kbps 10. CFG_HSDPA_4C_MIMO_SWITCH: Whether the
0106150 RRC 4C-HSDPA+MIMO feature is allowed for HSDPA
2 Connect services. When this switch is turned on, the MC-
WRFD- ion and HSDPA+MIMO (4C-HSDPA+MIMO and 3C-HSDPA
0106150 Radio +MIMO) feature is allowed for HSDPA services.
3 Access 11. CFG_HSDPA_4C_SWITCH: Whether the 3C-
WRFD- Bearer HSDPA or 4C-HSDPA feature is allowed for HSDPA
0106150 Establis services. When this switch is turned on, the 3C-HSDPA
1 hment or 4C-HSDPA feature is allowed for HSDPA services.

WCDMA RAN

nd
WRFD- and 12. CFG_HSDPA_DBMIMO_SWITCH: Whether the

0106150 Release DB-HSDPA+MIMO feature is allowed for HSDPA
4 PDCP services. When this switch is turned on, the DB-HSDPA
WRFD- Header +MIMO feature is allowed for HSDPA services.
170203 Compre 13. CFG_HSDPA_DB_SWITCH: Whether the DB-
WRFD- ssion HSDPA feature is allowed for HSDPA services. When
150207 (RFC25 this switch is turned on, the DB-HSDPA feature is
07) allowed for HSDPA services.
WRFD-
150227 CPC - 14. CFG_HSPA_DTX_DRX_SWITCH: When the
DTX / switch is on, DTX_DRX can be configured for the
WRFD-
DRX HSPA service.
0206050
4 CPC - 15. CFG_HSPA_HSSCCH_LESS_OP_SWITCH:
HS- When the switch is on, HS-SCCH Less Operation can
WRFD-
SCCH be configured for the HSPA service.
150223
less 16. CFG_HSUPA_16QAM_SWITCH: When the
WRFD- operatio switch is on, 16QAM can be configured for the HSUPA
150209 n service.
WRFD- 2x2 17. CFG_HSUPA_DC_SWITCH: When this switch is
010615 MIMO turned on, the DC-HSUPA function can be enabled for
WRFD- Downlin HSUPA services.
010617 k 18. CFG_IMS_SUPPORT_SWITCH: When the switch
WRFD- 64QAM is on and the IMS license is activated, the RNC supports
020134 Combin IMS signaling.
ation of 19.
One CS CFG_LOSSLESS_DLRLC_PDUSIZECHG_SWITC
Service H: Whether the UTRAN supports the function of
and Two lossless RLC PDU size change. When this switch is
PS turned on, downlink channel reconfiguration between
Services the DCH and HS-DSCH does not cause RLC PDU size
Combin change which results in packet loss. This function takes
ation of effect only on the UEs enabled with this function. For
Three details about this function, see 3GPP TS 25.331.
PS 20. CFG_LOSSLESS_RELOC_CFG_SWITCH:
Services When the switch is on and the UE supports lossless
Combin relocation, the RNC configures lossless relocation for
ation of PDCP parameters if the requirements of RLC mode,
Two PS discard mode, and sequential submission are met. Then,
Services lossless relocation is used for the UE.
Combin 21. CFG_MULTI_RAB_SWITCH: When the switch is

ation of on, the RNC supports multi-RABs combinations such
One CS as 2CS, 2CS+1PS, 1CS+2PS, and 2PS.
Service 22.
and CFG_PDCP_IPV6_HEAD_COMPRESS_SWITCH:
Three When the switch is on and the PDCP Header

WCDMA RAN

nd
PS compression license is activated, the PDCP header

Services compression algorithm for IPv6 is used at the RNC.
Uplink 23. CFG_PDCP_RFC2507_HC_SWITCH: When the
Control switch is on and the PDCP Header compression license
Channel is activated, the PDCP RFC2507 header compression
OLPC algorithm is used for the RNC.
4C- 24. CFG_PDCP_RFC3095_HC_SWITCH: When the
HSDPA switch is on and the PDCP ROHC license is activated,
DB- the PDCP RFC3095 header compression algorithm is
HSDPA used for the RNC.
+MIMO 25. CFG_PTT_SWITCH: When this switch is on, the
Lossless RNC identifies the PTT user based on the QoS attributes
SRNS in the RAB assignment request message. Then, the PTT
Relocati users are subject to special processing.
on 26. CFG_RAB_REL_RMV_HSPAPLUS_SWITCH:
MC- When this switch is on and if an RAB release is
HSDPA performed, the RNC decides whether to fall back a
+MIMO certain HSPA(HSPA+) feature based on the
DB- requirement of remaining traffic carried by the UE. That
HSDPA is, if an HSPA+ feature is required by the previously
released RAB connection but is not required in the
Multiple initial bearer policy of the remaining traffic, the RNC
RAB falls back the feature to save the transmission resources.
Package The HSPA+ features that support the fallback are
(PS MIMO, 64QAM, MIMO+64QAM, UL 16QAM, DC-
RAB >= HSDPA, UL TTI 2ms, and DC-HSUPA.
2)
27. CFG_RCS_E_SWITCH: Indicates whether to
VoIP enable the RCS-e (Rich Communication Suit enhanced)
over service that supports voice services carried in the CS
HSPA/ domain and video services carried in the PS domain.
HSPA+ When this switch is turned off, the RCS-e service is
Push to disabled. When this switch is turned on, the RCS-e
Talk service is enabled.
28.
ITCH: Switch for configuring AM RLC retransmission
parameters for UEs in the CELL_FACH state. (1) When
this switch is turned on and the cell-level parameters in
the command "ADD UCELLFACHCONGCTRL" are
not set, the parameters "TimerPoll" and
"NoDiscardMaxDAT" parameters in the command
"SET UFACHCFGPARA" are used as AM RLC
retransmission parameters specific to PS services and
SRBs. (2) When this switch is turned on and the cell-
level parameters in the command "ADD

WCDMA RAN

nd
UCELLFACHCONGCTRL" are set, the parameters

"TimerPollForFachPsTRB" and "TimerPollFor-
FachSRB" in the command "ADD UCELLFACH-
CONGCTRL" are used as AM RLC retransmission
parameters specific to PS services and SRBs,
respectively. (3) When this switch is turned off, the
parameters "TimerPoll" and "NoDiscardMaxDAT" in
the command "ADD UTYPSRBRLC" are used as AM
RLC retransmission parameters specific to SRBs, and
the parameters "TimerPoll" and "NoDiscardMaxDAT"
in the command "ADD UTYPRABRLC" are used as
AM RLC retransmission parameters specific to PS
services.
29.
ITCH: Switch controlling the configuration mode of
AM RLC SDU retransmission parameters for UEs in
the CELL_DCH state. When this switch is turned on
and UEs in the CELL_DCH state, on the RNC, the
transmitting side of an AM RLC entity uses the values
of the "TimerPoll" and "NoDiscardMaxDAT"
parameters in the "ADD UTYPSRBDCHRNCRLC" or
"MOD UTYPSRBDCHRNCRLC" command for SDU
retransmission. When this switch is turned off or UEs
not in the CELL_DCH state, on the RNC, the
transmitting side uses the values of these parameters in
the "ADD UTYPSRBRLC" or "MOD UTYPSRBRLC"
command for SDU retransmission.
30. CFG_HSDPA_SFDC_SWITCH: Whether to
enable the SFDC HSDPA function for UEs processing
SFDC HSDPA function is enabled for UEs processing
31. CFG_HSDPA_DF3C_SWITCH: Whether to
enable the DF3C HSDPA function for UEs processing
DF3C HSDPA function is enabled for UEs processing
32. CFG_SRB_BICASTING_SWTICH: Whether to
validate the SRB bicasting function for SRBs carried
over HSDPA when the multiflow HSDPA function is
enabled. When this switch is set to on in a cell enabled

WCDMA RAN

nd
with the inter-NodeB multiflow function, SRB PDUs in

AM RLC mode are transmitted simultaneously in all
cells. When this switch is set to off, SRB PDUs in AM
RLC mode can only be transmitted in one cell. PDU is
short for packet data unit. AM is short for acknowledged
mode. UM is short for unacknowledged mode. TM is
short for transparent mode. SRB PDUs in UM or TM
RLC mode can only be transmitted in the primary
sector. This switch is reserved for the MF-HSDPA
(multiflow HSDPA) function and cannot be used in the
current version.
GUI Value Range:
CFG_PTT_SWITCH,
CFG_RCS_E_SWITCH,
ITCH,
Unit: None

WCDMA RAN

nd
Actual Value Range:

CFG_PTT_SWITCH,
CFG_RCS_E_SWITCH,
ITCH,
Default Value:
CFG_DC_MIMO_DYNAMIC_SELECT_SWITCH:
0,CFG_DL_BLIND_DETECTION_SWITCH:
1,CFG_EDPCCH_BOOSTING_SWITCH:
0,CFG_FREE_USER_SWITCH:
0,CFG_HSDPA_64QAM_SWITCH:
1,CFG_HSDPA_DCMIMO_SWITCH:
0,CFG_HSDPA_DC_SWITCH:
0,CFG_HSDPA_MIMO_SWITCH:
1,CFG_HSDPA_MIMO_WITH_64QAM_SWITCH:
0,CFG_HSDPA_4C_MIMO_SWITCH:
0,CFG_HSDPA_4C_SWITCH:

WCDMA RAN

nd
0,CFG_HSDPA_DBMIMO_SWITCH:
0,CFG_HSDPA_DB_SWITCH:
0,CFG_HSPA_DTX_DRX_SWITCH:
0,CFG_HSPA_HSSCCH_LESS_OP_SWITCH:
0,CFG_HSUPA_16QAM_SWITCH:
0,CFG_HSUPA_DC_SWITCH:
0,CFG_IMS_SUPPORT_SWITCH:
1,CFG_LOSSLESS_DLRLC_PDUSIZECHG_SWIT
CH:0,CFG_LOSSLESS_RELOC_CFG_SWITCH:
0,CFG_MULTI_RAB_SWITCH:
1,CFG_PDCP_IPV6_HEAD_COMPRESS_SWITCH:
0,CFG_PTT_SWITCH:
0,CFG_RAB_REL_RMV_HSPAPLUS_SWITCH:
0,CFG_RCS_E_SWITCH:
0,CFG_FACH_AM_RLC_RETRANSMIT_PARA_S
WITCH:
0,CFG_DCH_SRB_AM_RLC_RETRANS_PARA_S
WITCH:0,CFG_HSDPA_SFDC_SWITCH:
0,CFG_HSDPA_DF3C_SWITCH:
0,CFG_SRB_BICASTING_SWTICH:0

WCDMA RAN

nd
CmpSwi BSC690 SET WRFD- HSDPA Meaning:

tch 0 UCORR 0106100 Mobility 1.
MALG 6 Manage CMP_IU_IMS_PROC_AS_NORMAL_PS_SWITCH:
OSWIT WRFD- ment When the switch is on, the IMS signaling assigned by
CH 020203 Inter the CN undergoes compatibility processing as an
WRFD- RNC ordinary PS service. When the switch is not on, no
020202 Soft special processing is performed.
Handov 2.
WRFD-
er CMP_IU_QOS_ASYMMETRY_IND_COMPAT_S
150209
Intra WITCH: When the Iu QoS Negotiation function is
WRFD-
RNC active and the switch is on, IE RAB Asymmetry
150227
Soft Indicator is Symmetric bidirectional, The uplink and
WRFD- Handov downlink RNC negotiation rate is asymmetric, "RNC"
021200 er select the bigger rate as Iu QoS negotiation rate. When
WRFD- DB- the switch is OFF, "RNC" select the less rate as Iu QoS
150223 HSDPA negotiation rate.
WRFD- DB- 3.
010696 HSDPA CMP_IU_SYSHOIN_CMP_IUUP_FIXTO1_SWITC
WRFD- +MIMO H: When the switch is on, the IUUP version can be
010202 rolled back to R99 when complete configurations are
HCS applied during inter-RAT handover.
WRFD- (Hierarc
0106120 hical 4.
4 Cell CMP_IUR_H2D_FOR_LOWR5_NRNCCELL_SWIT
Structur CH: When the switch is on, H2D is performed before a
WRFD- neighboring RNC cell whose version is earlier than R5
140204 e)
is added to the active set; E2D is performed before a
WRFD- MC- neighboring RNC cell whose version is earlier than R6
150250 HSDPA is added to the active set. If the DRNC is of a version
+MIMO earlier than R5, DL services cannot be mapped on the
DC- HS-DSCH. If the DRNC is of a version earlier than R6,
HSDPA DL services cannot be mapped on the HS-EDCH.
UE State 5. CMP_IUR_SHO_DIVCTRL_SWITCH: When the
in switch is on, the diversity combination over the Iur
Connect interface is configured on the basis of that of the local
ed Mode RNC. When the switch is not on, the diversity
(CELL- combination over the Iur interface is configured on the
DCH, basis of services. The flag of diversity combination over
CELL- the Iur interface can be set to MUST (for BE services)
PCH, or MAY (for other services).
URA- 6. CMP_UU_ADJACENT_FREQ_CM_SWITCH:
PCH, Whether the RNC activates the compressed mode
CELL- before initiating an inter-frequency measurement on a
FACH) DC-HSDPA or DB-HSDPA UE. When this parameter
HSUPA is set to ON, the RNC initiates the inter-frequency
Mobility measurement without activating the compressed mode

WCDMA RAN

nd
Manage if both the UE and EARFCN support the non-

ment compressed inter-frequency measurement. When this
DC- parameter is set to OFF, the RNC activates the
HSUPA compressed mode before initiating the inter-frequency
measurement. This switch takes effect only in non-
3C- flexible DC cells and DB cells.
HSDPA
7.
CMP_UU_AMR_DRD_HHO_COMPAT_SWITCH:
This parameter specifies to enable AMR through DRD
two-step procedure function. When SRB is set up on
DCH, and "RNC" decides to setup the AMR through
DRD procedure, When the switch is enabled, "RNC"
will execute blind handover to the target cell, and then
setup the AMR RBs on the target cell, When the switch
is disabled, "RNC" will setup the AMR RBs on the
target cell directly.
8. CMP_UU_AMR_SID_MUST_CFG_SWITCH: For
narrowband AMR services, when the switch is on, the
SID frame is always configured; when the switch is not
on, the SID frame is configured on the basis of CN
assignment.
9. CMP_UU_FDPCH_COMPAT_SWITCH: When the
switch is OFF, if the information element that indicates
the F-DPCH capability of UE exists in the message
"RRC_CONNECT_REQ" or
"RRC_CONNECT_SETUP_CMP", the F-DPCH
capability depends on that indicator. In other case, it
means UE does not support F-DPCH. When the switch
is ON, if the information element that indicates the F-
DPCH capability of UE exists in the message
capability depends on that indicator. If that information
element does not exist, UE supports F-DPCH when all
the conditions meets: a) the version of UE is Release 6.
b) UE supports HS-PDSCH.
10. CMP_UU_IGNORE_UE_RLC_CAP_SWITCH:
When the switch is on, the RAB assignment request and
the subsequent RB setup procedure proceed if the RLC
AM capabilities of the UE fail to meet the minimum
RLC TX/RX window buffer requirement of the RAB to
be setup. When the switch is not on, the RAB
assignment request is rejected.
11.
CMP_UU_INTRA_FREQ_MC_BESTCELL_CIO_S
WITCH: When this switch is on, the cell individual

WCDMA RAN

nd
offset (CIO) of the best cell is always set to 0 in the

INTRA-FREQUENCY MEASUREMENT
CONTROL messages. Otherwise, the CIO information
of the best cell is not carried in the INTRA-
FREQUENCY MEASUREMENT CONTROL
messages.
12.
CMP_UU_IOS_CELL_SYNC_INFO_REPORT_SWI
TCH: When the switch is on, the cell synchronization
information traced by the IOS need to be reported during
the RRC measurement period.
13.
CMP_UU_SERV_CELL_CHG_WITH_ASU_SWIT
CH: When the switch is on, the active set update is in
the same procedure as the change of the serving cell.
When the switch is not on, the serving cell is changed
after the UE updates the active set and delivers
reconfiguration of physical channels. This switch is
applicable only to R6 or aboveUEs.
14.
CMP_UU_SERV_CELL_CHG_WITH_RB_MOD_S
WITCH: When the switch is on, channel transition is in
after the UE performs channel transition and delivers
reconfiguration of physical channels.
15.
CMP_UU_VOIP_UP_PROC_AS_NORMAL_PS_S
WITCH: By default, the switch is on. In this case, the
Alternative E-bit is not configured for L2.
16.
CMP_F2F_RLC_ONESIDE_REBUILD_SWITCH:
When the switch is set to ON, only uplink RLC or
downlink RLC can be re-established during the state
transition from CELL_FACH to CELL_FACH (F2F for
short).
17.
CMP_D2F_RLC_ONESIDE_REBUILD_SWITCH:
transition from CELL_DCH to CELL_FACH (D2F for
short).
18. CMP_RAB_5_CFG_ROHC_SWITCH: When the
switch is set to ON, the service with RAB ID 5 can be
configured with the Robust Header Compression

WCDMA RAN

nd
(ROHC) function. When the switch is set to OFF, the

service with RAB ID 5 cannot be configured with the
ROHC function.
configured with the ROHC function. When the switch
is set to OFF, the service with RAB ID 6 cannot be
configured with the ROHC function.
23. CMP_HSUPA_MACD_FLOW_MUL_SWITCH:
When the switch is set to ON, MAC-d flow can be
multiplexed without any restrictions. When the switch
is set to OFF, only MAC-d flows whose scheduling
priority is lower than that of the current MAC-d flow
can be multiplexed.
24. CMP_SMLC_RSLT_MODE_TYPE_SWITCH: If
the Client Type of a positioning request is Emergency
Services, PLMN Operator Services, PLMN Operator -
broadcast services, PLMN Operator - O&M, PLMN
Operator - anonymous statistics or PLMN Operator -
Target MS service support, the positioning result is
reported by using the Ellipsoid point with uncertainty
circle type. For other client types, the positioning result
is reported by using the Ellipsoid Arc type.
25.
CMP_F2P_PROCESS_OPTIMIZATION_SWITCH:
Switch for optimizing the procedure for the
CELL_FACH-to-CELL_PCH-or-URA_PCH state
transition. When this switch is set to on, F2P state
transition is performed through the physical channel
reconfiguration procedure.When this switch is set to off,

WCDMA RAN

nd
F2P state transition is performed through the RB

reconfiguration procedure.
26.
CMP_UU_SIB11_SIB12_WITH_1A1D_SWITCH:
Whether to carry parameters related to events 1A and
1D in system information block type 11 (SIB 11) and
SIB 12.If the switch of deferred measurement control
reading is turned on, the UE cannot promptly read
parameters related to events 1A and 1D for intra-
frequency neighboring cells from SIB 11 or SIB12. As
a result, the UE cannot perform soft handovers in
advance. The switch is set using DeferMcReadInd in the
ADD/MOD UCELLMEAS command.
GUI Value Range:
CMP_IU_IMS_PROC_AS_NORMAL_PS_SWITCH,
CMP_IU_SYSHOIN_CMP_IUUP_FIXTO1_SWITC
H,
CMP_IUR_H2D_FOR_LOWR5_NRNCCELL_SWIT
CH, CMP_IUR_SHO_DIVCTRL_SWITCH,
CMP_UU_AMR_SID_MUST_CFG_SWITCH,
CMP_UU_ADJACENT_FREQ_CM_SWITCH,
CMP_UU_IGNORE_UE_RLC_CAP_SWITCH,
CH,
WITCH,
WITCH, CMP_UU_FDPCH_COMPAT_SWITCH,
CMP_UU_AMR_DRD_HHO_COMPAT_SWITCH,
CMP_IU_QOS_ASYMMETRY_IND_COMPAT_S
WITCH,
CMP_F2P_PROCESS_OPTIMIZATION_SWITCH,
TCH,
WITCH,
CMP_UU_SIB11_SIB12_WITH_1A1D_SWITCH,
CMP_F2F_RLC_ONESIDE_REBUILD_SWITCH,
CMP_D2F_RLC_ONESIDE_REBUILD_SWITCH,
CMP_RAB_5_CFG_ROHC_SWITCH,
CMP_HSUPA_MACD_FLOW_MUL_SWITCH,
CMP_SMLC_RSLT_MODE_TYPE_SWITCH

WCDMA RAN

nd
Unit: None
Actual Value Range:
WITCH,
H,
CMP_UU_FDPCH_COMPAT_SWITCH,
WITCH,
TCH,
CH,
WITCH,
WITCH,
CMP_SMLC_RSLT_MODE_TYPE_SWITCH,
CMP_UU_SIB11_SIB12_WITH_1A1D_SWITCH
Default Value:
CMP_IU_IMS_PROC_AS_NORMAL_PS_SWITCH:
0,CMP_IU_QOS_ASYMMETRY_IND_COMPAT_S
WITCH:
0,CMP_IU_SYSHOIN_CMP_IUUP_FIXTO1_SWIT
CH:
0,CMP_IUR_H2D_FOR_LOWR5_NRNCCELL_SW
ITCH:0,CMP_IUR_SHO_DIVCTRL_SWITCH:
0,CMP_UU_ADJACENT_FREQ_CM_SWITCH:
0,CMP_UU_AMR_DRD_HHO_COMPAT_SWITCH
:1,CMP_UU_AMR_SID_MUST_CFG_SWITCH:

WCDMA RAN

nd
0,CMP_UU_FDPCH_COMPAT_SWITCH:
0,CMP_UU_IGNORE_UE_RLC_CAP_SWITCH:
1,CMP_UU_INTRA_FREQ_MC_BESTCELL_CIO_
SWITCH:
0,CMP_UU_IOS_CELL_SYNC_INFO_REPORT_S
WITCH:
0,CMP_UU_SERV_CELL_CHG_WITH_ASU_SWI
TCH:
0,CMP_UU_SERV_CELL_CHG_WITH_RB_MOD_
SWITCH:
1,CMP_UU_VOIP_UP_PROC_AS_NORMAL_PS_S
WITCH:
1,CMP_F2F_RLC_ONESIDE_REBUILD_SWITCH:
0,CMP_D2F_RLC_ONESIDE_REBUILD_SWITCH:
0,CMP_RAB_5_CFG_ROHC_SWITCH:
0,CMP_HSUPA_MACD_FLOW_MUL_SWITCH:
0,CMP_SMLC_RSLT_MODE_TYPE_SWITCH:
0,CMP_F2P_PROCESS_OPTIMIZATION_SWITCH
:0,CMP_UU_SIB11_SIB12_WITH_1A1D_SWITCH:
0

WCDMA RAN

nd
CmpSwi BSC691 SET WRFD- HSDPA Meaning:

tch 0 UCORR 0106100 Mobility 1.
MALG 6 Manage CMP_IU_IMS_PROC_AS_NORMAL_PS_SWITCH:
OSWIT WRFD- ment When the switch is on, the IMS signaling assigned by
CH 020203 Inter the CN undergoes compatibility processing as an
WRFD- RNC ordinary PS service. When the switch is not on, no
020202 Soft special processing is performed.
Handov 2.
WRFD-
er CMP_IU_QOS_ASYMMETRY_IND_COMPAT_S
150209
Intra WITCH: When the Iu QoS Negotiation function is
WRFD-
RNC active and the switch is on, IE RAB Asymmetry
150227
Soft Indicator is Symmetric bidirectional, The uplink and
WRFD- Handov downlink RNC negotiation rate is asymmetric, "RNC"
021200 er select the bigger rate as Iu QoS negotiation rate. When
WRFD- DB- the switch is OFF, "RNC" select the less rate as Iu QoS
150223 HSDPA negotiation rate.
WRFD- DB- 3.
010696 HSDPA CMP_IU_SYSHOIN_CMP_IUUP_FIXTO1_SWITC
WRFD- +MIMO H: When the switch is on, the IUUP version can be
010202 rolled back to R99 when complete configurations are
HCS applied during inter-RAT handover.
WRFD- (Hierarc
0106120 hical 4.
4 Cell CMP_IUR_H2D_FOR_LOWR5_NRNCCELL_SWIT
Structur CH: When the switch is on, H2D is performed before a
WRFD- neighboring RNC cell whose version is earlier than R5
140204 e)
is added to the active set; E2D is performed before a
WRFD- MC- neighboring RNC cell whose version is earlier than R6
150250 HSDPA is added to the active set. If the DRNC is of a version
+MIMO earlier than R5, DL services cannot be mapped on the
DC- HS-DSCH. If the DRNC is of a version earlier than R6,
HSDPA DL services cannot be mapped on the HS-EDCH.
UE State 5. CMP_IUR_SHO_DIVCTRL_SWITCH: When the
in switch is on, the diversity combination over the Iur
Connect interface is configured on the basis of that of the local
ed Mode RNC. When the switch is not on, the diversity
(CELL- combination over the Iur interface is configured on the
DCH, basis of services. The flag of diversity combination over
CELL- the Iur interface can be set to MUST (for BE services)
PCH, or MAY (for other services).
URA- 6. CMP_UU_ADJACENT_FREQ_CM_SWITCH:
PCH, Whether the RNC activates the compressed mode
CELL- before initiating an inter-frequency measurement on a
FACH) DC-HSDPA or DB-HSDPA UE. When this parameter
HSUPA is set to ON, the RNC initiates the inter-frequency
Mobility measurement without activating the compressed mode

WCDMA RAN

nd
Manage if both the UE and EARFCN support the non-

ment compressed inter-frequency measurement. When this
DC- parameter is set to OFF, the RNC activates the
HSUPA compressed mode before initiating the inter-frequency
measurement. This switch takes effect only in non-
3C- flexible DC cells and DB cells.
HSDPA
7.
CMP_UU_AMR_DRD_HHO_COMPAT_SWITCH:
This parameter specifies to enable AMR through DRD
two-step procedure function. When SRB is set up on
DCH, and "RNC" decides to setup the AMR through
DRD procedure, When the switch is enabled, "RNC"
will execute blind handover to the target cell, and then
setup the AMR RBs on the target cell, When the switch
is disabled, "RNC" will setup the AMR RBs on the
target cell directly.
8. CMP_UU_AMR_SID_MUST_CFG_SWITCH: For
narrowband AMR services, when the switch is on, the
SID frame is always configured; when the switch is not
on, the SID frame is configured on the basis of CN
assignment.
9. CMP_UU_FDPCH_COMPAT_SWITCH: When the
switch is OFF, if the information element that indicates
the F-DPCH capability of UE exists in the message
capability depends on that indicator. In other case, it
means UE does not support F-DPCH. When the switch
is ON, if the information element that indicates the F-
DPCH capability of UE exists in the message
capability depends on that indicator. If that information
element does not exist, UE supports F-DPCH when all
the conditions meets: a) the version of UE is Release 6.
b) UE supports HS-PDSCH.
10. CMP_UU_IGNORE_UE_RLC_CAP_SWITCH:
When the switch is on, the RAB assignment request and
the subsequent RB setup procedure proceed if the RLC
AM capabilities of the UE fail to meet the minimum
RLC TX/RX window buffer requirement of the RAB to
be setup. When the switch is not on, the RAB
assignment request is rejected.
11.
WITCH: When this switch is on, the cell individual

WCDMA RAN

nd
offset (CIO) of the best cell is always set to 0 in the

INTRA-FREQUENCY MEASUREMENT
CONTROL messages. Otherwise, the CIO information
of the best cell is not carried in the INTRA-
FREQUENCY MEASUREMENT CONTROL
messages.
12.
TCH: When the switch is on, the cell synchronization
information traced by the IOS need to be reported during
the RRC measurement period.
13.
CH: When the switch is on, the active set update is in
after the UE updates the active set and delivers
reconfiguration of physical channels. This switch is
applicable only to R6 or aboveUEs.
14.
WITCH: When the switch is on, channel transition is in
after the UE performs channel transition and delivers
reconfiguration of physical channels.
15.
WITCH: By default, the switch is on. In this case, the
Alternative E-bit is not configured for L2.
16.
CMP_F2F_RLC_ONESIDE_REBUILD_SWITCH:
transition from CELL_FACH to CELL_FACH (F2F for
short).
17.
CMP_D2F_RLC_ONESIDE_REBUILD_SWITCH:
transition from CELL_DCH to CELL_FACH (D2F for
short).
configured with the Robust Header Compression

WCDMA RAN

nd
(ROHC) function. When the switch is set to OFF, the

service with RAB ID 5 cannot be configured with the
ROHC function.
23. CMP_HSUPA_MACD_FLOW_MUL_SWITCH:
When the switch is set to ON, MAC-d flow can be
multiplexed without any restrictions. When the switch
is set to OFF, only MAC-d flows whose scheduling
priority is lower than that of the current MAC-d flow
can be multiplexed.
24. CMP_SMLC_RSLT_MODE_TYPE_SWITCH: If
the Client Type of a positioning request is Emergency
Services, PLMN Operator Services, PLMN Operator -
broadcast services, PLMN Operator - O&M, PLMN
Operator - anonymous statistics or PLMN Operator -
Target MS service support, the positioning result is
reported by using the Ellipsoid point with uncertainty
circle type. For other client types, the positioning result
is reported by using the Ellipsoid Arc type.
25.
CMP_F2P_PROCESS_OPTIMIZATION_SWITCH:
Switch for optimizing the procedure for the
CELL_FACH-to-CELL_PCH-or-URA_PCH state
transition. When this switch is set to on, F2P state
transition is performed through the physical channel
reconfiguration procedure.When this switch is set to off,

WCDMA RAN

nd
F2P state transition is performed through the RB

reconfiguration procedure.
26.
CMP_UU_SIB11_SIB12_WITH_1A1D_SWITCH:
Whether to carry parameters related to events 1A and
1D in system information block type 11 (SIB 11) and
SIB 12.If the switch of deferred measurement control
reading is turned on, the UE cannot promptly read
parameters related to events 1A and 1D for intra-
frequency neighboring cells from SIB 11 or SIB12. As
a result, the UE cannot perform soft handovers in
advance. The switch is set using DeferMcReadInd in the
ADD/MOD UCELLMEAS command.
GUI Value Range:
H,
CH,
WITCH,
WITCH, CMP_UU_FDPCH_COMPAT_SWITCH,
WITCH,
TCH,
WITCH,
CMP_UU_SIB11_SIB12_WITH_1A1D_SWITCH,
CMP_SMLC_RSLT_MODE_TYPE_SWITCH

WCDMA RAN

nd
Unit: None
Actual Value Range:
WITCH,
H,
CMP_UU_FDPCH_COMPAT_SWITCH,
WITCH,
TCH,
CH,
WITCH,
WITCH,
CMP_SMLC_RSLT_MODE_TYPE_SWITCH,
CMP_UU_SIB11_SIB12_WITH_1A1D_SWITCH
Default Value:
CMP_IU_IMS_PROC_AS_NORMAL_PS_SWITCH:
0,CMP_IU_QOS_ASYMMETRY_IND_COMPAT_S
WITCH:
0,CMP_IU_SYSHOIN_CMP_IUUP_FIXTO1_SWIT
CH:
0,CMP_IUR_H2D_FOR_LOWR5_NRNCCELL_SW
ITCH:0,CMP_IUR_SHO_DIVCTRL_SWITCH:
0,CMP_UU_ADJACENT_FREQ_CM_SWITCH:
0,CMP_UU_AMR_DRD_HHO_COMPAT_SWITCH
:1,CMP_UU_AMR_SID_MUST_CFG_SWITCH:

WCDMA RAN

nd
0,CMP_UU_FDPCH_COMPAT_SWITCH:
0,CMP_UU_IGNORE_UE_RLC_CAP_SWITCH:
1,CMP_UU_INTRA_FREQ_MC_BESTCELL_CIO_
SWITCH:
0,CMP_UU_IOS_CELL_SYNC_INFO_REPORT_S
WITCH:
0,CMP_UU_SERV_CELL_CHG_WITH_ASU_SWI
TCH:
0,CMP_UU_SERV_CELL_CHG_WITH_RB_MOD_
SWITCH:
1,CMP_UU_VOIP_UP_PROC_AS_NORMAL_PS_S
WITCH:
1,CMP_F2F_RLC_ONESIDE_REBUILD_SWITCH:
0,CMP_D2F_RLC_ONESIDE_REBUILD_SWITCH:
0,CMP_HSUPA_MACD_FLOW_MUL_SWITCH:
0,CMP_SMLC_RSLT_MODE_TYPE_SWITCH:
0,CMP_F2P_PROCESS_OPTIMIZATION_SWITCH
:0,CMP_UU_SIB11_SIB12_WITH_1A1D_SWITCH:
0

WCDMA RAN
PDCP Header Compression Feature Parameter Description 6 Counters
6 Counters
There are no specific counters associated with this feature.

WCDMA RAN
PDCP Header Compression Feature Parameter Description 7 Glossary
7 Glossary
For the acronyms, abbreviations, terms, and definitions, see the Glossary.

WCDMA RAN
PDCP Header Compression Feature Parameter Description 8 Reference Documents
8 Reference Documents
1. 3GPP TS 25.323, "Packet Data Convergence Protocol (PDCP) Specification"

2. RFC2507 "IP Header Compression"
3. RFC3095 "Robust Header Compression"


PDCP Header Compression (RAN15.0 - 01) PDF

Uploaded by

Document Informationclick to expand document information

Document Informationclick to expand document information

Copyright:

Available Formats

PDCP Header Compression (RAN15.0 - 01) PDF

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

PDCP Header Compression (RAN15.0 - 01) PDF

Uploaded by

Copyright:

Available Formats

WCDMA RAN

PDCP Header Compression Feature

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 01 (2013-04-28) Huawei Proprietary and Confidential i

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

Issue 01 (2013-04-28) Huawei Proprietary and Confidential ii

Issue 01 (2013-04-28) Huawei Proprietary and Confidential iii

1 About This Document

This document covers the following features:

l WRFD-011500 PDCP Header Compression (RFC2507)

This document applies to the following NE types.

RNC BSC6900, BSC6910

NodeB Macro Not involved

Micro Not involved

LampSite Not involved

1.2 Intended Audience

l Need to understand the features described herein

1.3 Change History

Issue 01 (2013-04-28) Huawei Proprietary and Confidential 1

RAN15.0 Draft A (2013-01-30)

Change Type Change Description Parameter Change

Feature change None. None.

Editorial change Incorporated the None.

1.4 Differences Between Base Station Types

Feature ID Descriptio Supported by Controller Supported Supported LampSite

WRFD-01 PDCP Y Y N/A N/A N/A

Issue 01 (2013-04-28) Huawei Proprietary and Confidential 2

Issue 01 (2013-04-28) Huawei Proprietary and Confidential 3

2.1 Introduction to PDCP Header Compression

2.2 PDCP Header Compression algorithms

l IPHC (IP Header Compression): It can apply to PS services.

The header includes the following data:

Issue 01 (2013-04-28) Huawei Proprietary and Confidential 4

Figure 2-1 shows the block diagram of IPHC.

Figure 2-1 Block diagram of IPHC

RoHC is an extensible framework consisting of the following profiles:

Issue 01 (2013-04-28) Huawei Proprietary and Confidential 5

3.1 Overview of PDCP Header Compression Technology

l Transfer of packet data

The general process of PDCP header compression is as follows:

PDCP header compression is applied for the following purposes:

l Reducing header overhead

Issue 01 (2013-04-28) Huawei Proprietary and Confidential 6

3.2 PDCP System Structure

3.2.1 UMTS Structure for the PS Domain

Figure 3-1 UMTS structure for the PS domain

3.2.2 User Plane of the Protocol Stack for the PS Domain

Issue 01 (2013-04-28) Huawei Proprietary and Confidential 7

3.2.3 PDCP Structure in the Radio Interface Protocol Architecture

Figure 3-3 PDCP structure in the radio interface protocol architecture

Issue 01 (2013-04-28) Huawei Proprietary and Confidential 8

3.3 Process of PDCP Header Compression

3.3.1 Process of IPHC

l Compressible chain of sub-headers judgment algorithm

Figure 3-4 shows the process of IPHC.