V300R002C02
Issue 01
Date 2009-03-20
Website: http://www.huawei.com
Email: support@huawei.com
and other Huawei trademarks are the property of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
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 the statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Contents
2 Multi-Antenna Feature..............................................................................................................2-1
2.1 Overview of the Multi-Antenna Feature.........................................................................................................2-2
2.2 Availability of the Multi-Antenna Feature......................................................................................................2-4
2.3 Functions of the Multi-Antenna Feature.........................................................................................................2-5
2.3.1 Key Multi-Antenna Technologies..........................................................................................................2-5
2.3.2 Strategy of Multi-Antenna Applications................................................................................................2-9
2.4 Implementation of the Multi-Antenna Feature................................................................................................2-9
2.4.1 Activating the Multi-Antenna Feature...................................................................................................2-9
2.4.2 Deactivating the Multi-Antenna Feature..............................................................................................2-14
2.5 Maintenance of the Multi-Antenna Feature..................................................................................................2-15
2.6 Reference Information of the Multi-Antenna Feature...................................................................................2-16
5 QoS Feature.................................................................................................................................5-1
5.1 Overview of the QoS Feature..........................................................................................................................5-2
5.2 Availability of the QoS Feature......................................................................................................................5-3
5.3 Description of the QoS Feature.......................................................................................................................5-4
5.3.1 QoS Network Model..............................................................................................................................5-5
5.3.2 QoS Mechanism and Parameters............................................................................................................5-5
5.3.3 QoS Transmission Control...................................................................................................................5-10
5.4 Implementation of the QoS Feature..............................................................................................................5-11
5.4.1 Activation of the QoS Feature..............................................................................................................5-11
5.4.2 Deactivation of the QoS Feature..........................................................................................................5-14
5.5 Maintenance Information of the QoS Feature...............................................................................................5-14
5.6 Reference Information of the QoS Feature...................................................................................................5-15
6 Handover Feature.......................................................................................................................6-1
6.1 Overview of the Handover Feature.................................................................................................................6-2
6.2 Availability of the Handover Feature..............................................................................................................6-3
6.3 Description of the Handover Feature..............................................................................................................6-3
6.4 Implementation of the Handover Feature........................................................................................................6-5
6.4.1 Activating the Handover Feature...........................................................................................................6-5
6.4.2 Deactivating the Handover Feature........................................................................................................6-8
6.5 Maintenance Information of the Handover Feature........................................................................................6-8
6.6 Reference Information of the Handover Feature.............................................................................................6-9
8 FFR Feature..................................................................................................................................8-1
8.1 Overview of the FFR Feature..........................................................................................................................8-2
8.2 Availability of the FFR Feature......................................................................................................................8-3
8.3 Description of the FFR Feature.......................................................................................................................8-3
8.4 Implementation of the FFR Feature................................................................................................................8-6
8.4.1 Activating the FFR Feature....................................................................................................................8-6
8.4.2 Deactivating the FFR Feature................................................................................................................8-7
8.5 Maintenance Information of the FFR Feature.................................................................................................8-7
8.6 Reference Information of the FFR Feature.....................................................................................................8-7
Figures
Tables
Overview
This document describes the features of the DBS3900 WiMAX in terms of their definitions,
principles, service flows, and implementation.
Product Versions
The following table lists the product versions related to this document.
Intended Audience
This document is intended for:
Change History
Version Description
Organization
1 HARQ Feature
This describes the Hybrid Automatic Repeat Request (HARQ), which is a technology that uses
both Forward Error Correction (FEC) and Automatic Repeat Request (ARQ) to improve the
communications reliability.
2 Multi-Antenna Feature
This describes the functions, application strategies, and engineering of the multi-antenna
technologies that the Huawei WiMAX products adopt.
3 Power Control and AMC Feature
Power control and AMC algorithms are core algorithms of WiMAX. The MS and BS cooperate
over the R1 interface to achieve power control and AMC.
4 Idle Mode Feature
This describes the basic concepts, functions, and implementation method of the idle mode
feature.
5 QoS Feature
The WiMAX BS can provide users with five different Quality of Service (QoS) levels. Users
need to choose the desired QoS level when subscribing to services.
6 Handover Feature
This describes the handover feature of the WiMAX BS. The WiMAX BS supports hard
handovers, including intra-BS handovers and inter-BS handovers.
7 Automatic Discovery Feature
This describes the automatic discovery feature, which is the application of DHCP in the WiMAX
system.
8 FFR Feature
FFR is an enhanced function of the WiMAX system.
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
General Conventions
The general conventions that may be found in this document are defined as follows.
Convention Description
Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention Description
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention Description
Keyboard Operations
The keyboard operations that may be found in this document are defined as follows.
Format Description
Key Press the key. For example, press Enter and press Tab.
Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+Alt
+A means the three keys should be pressed concurrently.
Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means
the two keys should be pressed in turn.
Mouse Operations
The mouse operations that may be found in this document are defined as follows.
Action Description
Click Select and release the primary mouse button without moving
the pointer.
Drag Press and hold the primary mouse button and move the
pointer to a certain position.
1 HARQ Feature
This describes the Hybrid Automatic Repeat Request (HARQ), which is a technology that uses
both Forward Error Correction (FEC) and Automatic Repeat Request (ARQ) to improve the
communications reliability.
Definition
HARQ is a PHY/MAC-layer technology that uses both hybrid ARQ and forward error correction
(FEC).
After HARQ is enabled, the transmitter decides whether to retransmit a data packet according
to the received ACK or NACK message from the receiver. If data retransmission is required,
the receiver combines the data packet with the previously received packet and then retransmits
the data packet for error correction decoding.
Through data retransmission, the receiver can obtain the time diversity gain, coding gain, and
power gain to enhance the decoding performance and spectrum efficiency and intensify coverage
effect.
Purpose
Featuring the advantages of both FEC and ARQ, HARQ is aimed at improving quality and
reliability in signal transmission. In an adverse radio environment, HARQ can reduce the
impaction of channel fading and interference fluctuation, thereby achieving high system gains,
lowering the BER, and improving data transmission performance.
Specification
The Huawei specifications of the HARQ feature are described as follows:
l The UL HARQ delay and DL HARQ delay can be four frames.
l A maximum of 16 HARQ channels can be allocated to each DL subscriber and each UL
subscriber. The supported highest HARQ capability set is HARQ set 3.
l A DL single-subscriber frame supports a maximum of four subbursts, and an UL single-
subscriber frame supports a maximum of three subbursts.
Influence
l HARQ improves spectrum efficiency and enhances coverage.
l The data retransmission and combination during HARQ increase transmission delay to a
small extent.
l Relation between the HARQ feature and other features:
– The HARQ feature is related to power control and AMC feature. HARQ and AMC are
used together to combat the fading of radio channels and time-variable interference.
AMC provides rough and slow adaptive control within a large dynamic range. HARQ
provides precise and fast adaptive control within a small dynamic range.
– The HARQ feature is related to the QoS feature. During service establishment, the BS
decides whether HARQ is enabled for a connection according to the service flow
parameter for QoS feature.
Term
Term Definition
Stop-and-wait The transmitter processes another data block only after the previously
mechanism transmitted data block is correctly received.
Retransmission For an incorrect data block, the transmitter retransmits the check bits
first. If error occurs again, the transmitter retransmits the entire data
block.
Incremental The data transmitted by the sending send for the first time contains
Redundancy system information and some redundancy information. The
retransmitted data, however, does not contain system information bit
except new redundancy information. After the receiver receives an error
packet, it does not discard the error packet but combines the error packet
with the retransmitted redundancy information and then decodes the
combined information.
BS Base Station
CC Chase Combining
IR Incremental Redundancy
MS Mobile Station
Abbreviations
and Acronyms Full Spelling
SS Subscriber Station
√ √ - - - √
NOTE
In Table 1-1, √ is used to mark network elements that are involved in the HARQ feature, and - is used to
mark network elements that are not involved in the HARQ feature.
Supporting Versions
Table 1-2 lists the versions that support the HARQ feature.
License Support
This feature does not require the license support.
feature that uses Convolutional Turbo Code (CTC) coding and need not support the IR-HARQ
feature. Hence, this document describes mainly the functions and working principles of the CC-
HARQ feature.
The CC-HARQ feature involves the processing for network access and service establishment in
the signaling plane, processing for the UL and DL HARQ in the user plane, HARQ allocation
management, and buffer management.
1.3.1 Fundamental Principles of the HARQ
The HARQ feature defined by IEEE 802.16 standard is applied to air interface links of the base
station and mobile station (MS). In fact, it is a Stop-and-Wait (SAW) hybrid ARQ solution.
1.3.2 HARQ Types
In the IEEE 802.16 standard, two types of HARQs are defined: CC-HARQ and IR-HARQ.
1.3.3 HARQ Processing in the Signaling Plane
HARQ processing in the signaling plane involves the initial network entry of the MS, handover,
idle-mode network reentry, location update, and service flow establishment.
1.3.4 HARQ Processing in the User Plane
The BS performs HARQ processing in the user plane on the PHY layer and MAC layer.
1.3.5 HARQ Allocation Algorithm and Buffer Management
1.3.6 Power Control and AMC Processing for HARQ Connections
After a transmitter sends a packet to the receiver, it sends the next packet only when it receives
the ACK message from the receiver. If the transmitter fails to receive the ACK message, it
retransmits the packet that fails to be received, as shown in Figure 1-1.
Both the UL and DL over the R1 interface of the WiMAX network support the HARQ. DL
HARQ: After a base station (BS) sends a HARQ data packet, the MS responds with the ACK
or NACK message based on whether the correct data packet is received. UL HARQ: After an
MS sends an HARQ data packet, the BS decides whether to retransmit according whether the
UL decoding is correct.
HARQ enables selective retransmission of error data to decrease the impact of error codes over
the channel on services. Figure 1-1 shows how HARQ is implemented at the base station side
(the HARQ implementation at the MS side is similar).
When the CC-HARQ is adopted and data retransmission is required, the transmitter uses the
same modulation and coding (MC) mode to retransmit the burst. After the receiver receives the
data, it combines the data with its previously received one to raise the Signal Noise Ratio (SNR)
before decoding, hence, increasing the probability of correct decoding.
When the IR-HARQ is adopt and data retransmission is required, the transmitter can use different
MC mode and can add redundancy information different from previous one to the error
correction (EC) block for data retransmission. After the receiver receives the data, it combines
the data with its previously received one to raise the SNR or adds redundancy information to
the decoding code, hence, increasing the probability of correct decoding. The IR-HARQ feature
performance is slightly better than the CC-HARQ feature performance but requires higher
hardware capability.
According to the WiMAX Forum Mobile System Profile Release 1.0, the base station must
support the CC-HARQ feature that uses Convolutional Turbo Code (CTC) coding and need not
support the IR-HARQ feature.
(1) On the M2000 or Web LMT, configure the OFDMA support capability parameter of
the BS. This parameter indicates the HARQ support capability of the BS. The HARQ
related OFDMA support capability parameters are:
l Demodulation Mode: The BIT#4 (the fifth bit from the least significant bit to the
most significant bit) set to 1 is one of the prerequisites for enabling the HARQ.
When the BIT#4 is set to 0, HARQ is disabled.
l Modulation Mode: The BIT#5 (the sixth bit from the least significant bit to the
most significant bit) set to 1 is one of the prerequisites for enabling the HARQ.
When the BIT#5 is set to 0, HARQ is disabled.
l Uplink Control Support: HARQ retransmission requires the UL ACK channel
to transmit the DL ACK or NACK message. The BIT#2 (the third bit from the
least significant bit to the most significant bit) set to 1 indicates supporting the UL
ACK channel and enabling the HARQ. When the BIT#2 is set to 0, HARQ is
disabled.
(2) During sector carrier establishment, the BS decides whether to enable the HARQ
function according to the HARQ capability parameters and records the decision for
the sector. The result is used during the network entry negotiation of the MS.
2. SBC processing procedure during the initial network entry of the MS
During the initial network entry of the MS, whether the BS supports the HARQ function
is negotiated through the SS basic capability (SBC) processing procedure. The SBC
processing procedure is described as follows:
(1) The MS initiates the SBC processing procedure to negotiate whether to support the
HARQ function by sending a message to the BS.
(2) The BS negotiates with the MS on whether to support the HARQ parameters HARQ
Buffer Capability, Number of UL/DL HARQ Channels, and Maximum Number
Of Bursts Per Frame Capability In HARQ according to the HARQ Chase indicator
bit in parameters Modulation Mode and Demodulation Mode. Through negotiation,
the BS decides whether to enable HARQ for a connection, the number of HARQ
channels to be used, and whether to enable the PDU SN subheader in MAC Header
and Extended Subhead Support.
l HARQ Buffer Capability: The value of this parameter indicates the maximum
size of buffer that a sub-burst can occupy. The value of this parameter impacts the
transmission rate of the MS that enables the HARQ function.
l Number of UL/DL HARQ Channels: The value of this parameter needs to be
negotiated between the BS and the MS and set to the smallest value supported by
the BS and the MS. The value of this parameter and the value of HARQ Buffer
Capability together determine the peak rate of the MS that enables the HARQ.
l Maximum Number Of Bursts Per Frame Capability In HARQ: The value of
this parameter indicates the maximum number of bursts in each frame supported
by the HARQ. The value of this parameter impacts the number of MSs that a frame
can process synchronously.
(3) The BS saves the negotiation result. The DSA processing procedure during service
establishment is started.
3. DSA processing procedure during service establishment
During the service establishment, whether the BS supports the HARQ function is negotiated
through the Dynamic Service Addition (DSA) procedure. The DSA processing procedure
is described as follows:
(1) The BS decides whether to enable HARQ according to MS service flow QoS
parameters, negotiated Number of UL/DL HARQ Channels and HARQ Buffer
Capability supported by the MS during SBC processing procedure, and service flow
delay threshold of the BS.
(2) The BS saves related negotiation parameters and sets up the HARQ connection
according to the negotiation parameters.
The HARQ processing in the user plane is classified into DL processing in the user plane and
UL processing in the user plane.
1. HARQ DL processing in the user plane
As shown in Figure 1-3, the BS packs, fragments, and then assembles the data packets
from the classifier into a subburst, adds the CRC16 code, performs coding and modulation,
and then sends the subburst to the MS.
After an HARQ ACK Delay for DL Burst, the MS responds with an ACK or NACK
message through the ACK channel. The BS demodulates the message on the ACK channel,
and then performs HARQ allocation according to the demodulation result.
HARQ ACK Delay for DL Burst: It indicates the time an MS takes to responds with an
ACK or NACK message after receiving a sub-burst. The value of this parameter impacts
data transmission performance and system overhead over the air interface.
The BS uses the HARQ ACK Delay for DL Burst parameter in the UCD message to define
how soon an MS responds with an ACK or NACK message after receiving a DL sub-burst.
The BS performs fast ACK channel demodulation for the ACK or NACK message received
from the MS, performs HARQ allocation according to the demodulation result and
retransmission times, and decides whether to empty the buffer corresponding to the DL HARQ
subchannel.
Context
The HARQ parameter configuration at the BS side is as follows:
NOTE
Before performing the HARQ parameter configuration at the BS side, ensure that the sector carrier is in
deactivate state. Step 2 to step 6 of the following configuration steps are not in a particular sequence.
Procedure
Step 1 Run MOD CARRIERBLOCKFLAG to deactivate the sector carrier.
For example,
MOD CARRIERBLOCKFLAG: SECTORID=0, CARRIERID=0, BLOCKFLAG=Blocked;
Step 2 Run MOD OFDMACAPABILITY to enable the HARQ UL/DL modulation mode,
demodulation mode, MAP capability, and UL ACK channel support. Modulation mode enabled
(BIT#4 set to 1) and demodulation mode enabled (BIT#5 set to 1) are the prerequisites for
enabling the HARQ.
For example,
MOD OFDMACAPABILITY: SECTORID=0, CARRIERID=0, DEMODULATION=37, MODULATION=20,
ULCTRLSUPP=4, OFDMAMAPCAP=6;
Step 3 Run MOD MACCAPABILITY to enable the BS to support the PDU SN extended subheader,
to set the BS-supported HARQ buffer size (5140 bits are recommended), and to set the HARQ-
supported maximum number of subbursts (65 is recommended) in a frame.
For example,
MOD MACCAPABILITY: SECTORID=0, CARRIERID=0, HEADERTYPESUPP=327647, EXTCAP=1,
HARQCHASEBUFCAP=5140, MAXBURINHARQ=65;
Step 4 Run MOD ULCHANPARA and MOD DLCHANPARA to configure the UL/DL HARQ
maximum retransmission times and HARQ DL ACK delay.。
For example,
MOD ULCHANPARA: SECTORID=0, CARRIERID=0, HARQDELAYFORDLBURST=1, ULHARQMAXRETRAN=4;
MOD DLCHANPARA: SECTORID=0, CARRIERID=0, DLMAXHARQRETRAN=4;
Step 5 Run MOD RRMSOFT to enable the service flow priority threshold and service flow delay
threshold at the BS side. HARQ can be enabled for the service flow only when the previous two
thresholds are smaller than those thresholds in the QoS parameters set for the MS.
For example,
MOD RRMSOFT: PARANO=21, VALUE=0;
MOD RRMSOFT: PARANO=22, VALUE=8;
Step 6 Run MOD RRMSOFT to configure the UL public-area mode of the BS. The UL public-area
supports five modes (mode 0 to mode 4). Where, mode 3 does not support UL HARQ ACK
channels. Therefore, to enable the HARQ, do not configure mode 3.
For example,
MOD RRMSOFT: PARANO=5, VALUE=4;
----End
Procedure
Run MOD OFDMACAPABILITY to set demodulation mode parameter BIT#5 and
modulation mode BIT#4 to 0 to deactivate the HARQ feature.
For example,
MOD OFDMACAPABILITY: SECTORID=0, CARRIERID=0,
DEMODULATION=5,MODULATION=4,ULCTRLSUPP=2,OFDMAMAPCAP=6;
----End
Related Parameters
Table 1-3, Table 1-4, Table 1-5, Table 1-6, Table 1-7, Table 1-8 and Table 1-9 list the
parameters related to the HARQ feature.
Parameter Meaning
SECTORID Sector ID
CARRIERID Carrier ID
Parameter Meaning
SECTORID Sector ID
CARRIERID Carrier ID
Parameter Meaning
SECTORID Sector ID
CARRIERID Carrier ID
SECTORID Sector ID
CARRIERID Carrier ID
SECTORID Sector ID
CARRIERID Carrier ID
SECTORID Sector ID
CARRIERID Carrier ID
2 Multi-Antenna Feature
This describes the functions, application strategies, and engineering of the multi-antenna
technologies that the Huawei WiMAX products adopt.
Definition
The IEEE 802.16e system supports multiple multi-antenna technologies, including downlink
transmitter diversity (such as Matrix A and CDD), space division multiplexing (such as Matrix
B), and uplink multi-antenna receiver (MRC), and uplink collaborative MIMO (collaborate
spatial multiplex: CSM).
l If the BS uses two transmit antennas, two-antenna Matrix A or Matrix B transmission can
be adopted. For common channels like the Preamble, two-antenna CDD transmission can
be adopted.
l If the BS uses four transmit antennas, Matrix A+CDD or Matrix B+CDD transmission can
be adopted. For common channels like the Preamble, four-antenna CDD transmission can
be adopted.
l If the terminal supports demodulation under Matrix A or Matrix B, the BS transmits signals
to the terminal in these two MIMO modes.
Purpose
The multi-antenna technology can help significantly increase the system capacity or expand the
coverage so that the spectrum resources can be fully used or the number of sites can be reduced.
With this technology, the customers can reduce the CAPEX for the WiMAX market and protect
their investment, thus bringing better service experience to their subscribers.
Specifications
System peak throughput:
l Under the configuration of 4T4R, the peak downlink throughput in each sector carrier is
45 Mbit/s. Conditions: 10 MHz bandwidth, PUSC/all sc, and 35:12 subframe ratio.
l Under the configuration of 4T4R, the peak uplink throughput in each sector carrier is 10
Mbit/s. Conditions: 10 MHz bandwidth, PUSC/all sc, and 26:21 subframe ratio.
Impact
Multi-antenna technologies do not affect each other. When used together with other features,
the multi-antenna feature has the following impact on the system.
Two-antenna Matrix A and two-antenna Matrix B:
l On the signaling system: The system must support the MAP format of MIMO.
l On Zone management: The system must support the allocation and management of the STC
Zone.
Four-antenna Matrix A + CDD and four-antenna Matrix B + CDD:
l On the signaling system: The system must support the MAP format of MIMO.
l On Zone management: The system must support the allocation and management of the STC
Zone.
Term
Term Definition
Space-time Space-time coding (STC) is a signal coding technology that can be used
coding to obtain enhanced data transmission rates. It combines the space
transmitted signals and time transmitted signals. In essence, it is a two-
dimension (space dimension and time dimension) processing method. In
a new-generation communication system, space diversity achieved
through multiple transmit and receive antennas raises the system
capacity and information rate. Meanwhile, different signals are
transmitted in different timeslots by the same antenna, and therefore
receive diversity can be implemented at the receiver. In this way,
diversity and coding gains are obtained to achieve high-speed
transmission. This technology is used in 3G communication systems to
increase spectrum utilization.
m*n The uplink or downlink links have m transmit antennas and n receive
antennas.
MS Mobile Station
SS Subscriber Station
BS Base Station
Table 2-1 Requirements of the multi-antenna feature for the network elements
ASN AAA DHCP
SS/MS BS -GW Server Server M2000
√ √ - - - √
NOTE
In Table 2-1, √ is used to mark network elements that must meet specific requirements, and - is used to
mark network elements that do not have to meet specific requirements.
Supporting Versions
Table 2-2 lists the versions that support the multi-antenna feature.
License Support
To use this feature, you need to apply for a license that supports it.
Downlink MIMO
Downlink MIMO is a multi-antenna open-loop technology in which multiple antennas are used
to transmit signals without knowing downlink channel condition. The WiMAX system profile
defines that the major downlink MIMO technologies are Matrix A and Matrix B, which features
vertical coding.
In Matrix A, the two links of transmitted signals are content-related. Under the impact (reflection
and refraction) of physical space environment, a transmitted signal is dispersed into multiple
signals with different phases. In optimum conditions, two receiving signals may be combined
into one signal with the power doubled. In this way, the receiving diversity can increase by 3
dB to enhance the system coverage. Figure 2-1 shows the transmit matrix of Matrix A.
In the scenario of Matrix A transmission, the recommended number of receive antennas at the
receiver side is two or more. Although only one antenna can also demodulate data, such
configuration is not recommended because the performance is poor.
Matrix B: Different streams are transmitted through two antennas over the same time and
frequency resources. Figure 2-2 shows the transmit matrix of Matrix B.
In the scenario of Matrix B transmission, the receiver must be equipped with two or more receive
antennas to demodulate data because it must separate the two streams using the same resources.
Matrix B cannot provide diversity gain. Instead, it brings space multiplexing diversity because
two streams use the same time and frequency resources. The performance of Matrix B can be
ensured when the signal-to-noise ratio is high and the channels of the two channels of the two
streams must be uncorrelated.
The system can perform self-adaptive switching between Matrix A and Matrix B through the
adaptive MIMO switching (AMS) algorithm, which helps maximize the spectrum gain.
Downlink CDD
CDD is implemented through the transmission of data duplicate with different delays through
different antennas. This technology can provide diversity gain and improve performance. The
IEEE 802.16e standard specifies that the downlink preambles and the first downlink zone cannot
use STC coding. However, the CDD can be used to improve the demodulation performance of
the common channel, thus improving the coverage of common channels. With the CDD
technology, the power gain can be obtained from multi-antenna transmission. In the scenario of
channel fading, this technology can even bring a small amount of diversity gain. In the scenario
of LOS, no diversity gain can be obtained.
1. The Preamble and data on common channels are transmitted in CDD mode. Figure 2-4
shows the transmission mode.
2. Transmission mode of traffic channel. On the traffic channel, the four-antenna MIMO +
CDD transmission mode is Matrix A+CDD/Matrix B+CDD self-adaptive switching.
l Figure 2-5 shows the mapping between the Matrix A + CDD baseband data and antenna.
l Figure 2-6 shows the mapping between the Matrix B + CDD baseband data and antenna.
1. Uplink diversity receiving. Uplink receive diversity is the most commonly used multi-
antenna technology. The BTS performs coherent combination for the signals received by
multiple antennas. In this way, array gains and four-way receiver diversity are obtained.
The receive algorithm is maximum ratio combining (MRC). In MRC, coherent combination
is performed for the signals received by multiple antennas. Through MRC, array gains and
diversity gains can be obtained.
2. Uplink CSM. In uplink CSM, the terminals of two transmit-only antennas are fixed to the
same time or frequency resources. The BS uses multiple antennas to receive signals, thus
distinguishing between subscribers and improving uplink capacity. Figure 2-7 shows
principle of uplink CSM.
With the MIMO License, the BS uses MIMO transmission by default regardless of the multi-
antenna transmission configuration.
l If the SS does not support MIMO or the downlink transmission is on a non-STC Zone,
CDD is used. The system reserve a Zone dedicated for this transmission mode. The SSs in
this Zone automatically use CDD mode to transmit data.
l If the MS supports Matrix A and Matrix B, the system determines to MIMO mode to be
used according to the channel environment. The switching between Matrix A and Matrix
B is performed automatically.
Prerequisite
l The M2000 has issued the License to the NE.
l The basic configurations related to sector carriers have been implemented.
Context
l You can set the parameters through the background maintenance tool Web LMT or the
M2000.
l The parameters used in steps 2–6 and step 8 can be changed only during the deactivation
of sector carriers. The changes take effect after the sector carriers are activated again.
Procedure
Step 1 Query and set the License information.
1. Run the LST CARRIERLICENSEINFO command to query the information about the
License of a carrier.
Example:
LST CARRIERLICENSEINFO: SECTORID=0, CARRIERID=0;
Step 2 Query and set the numbers of transmit antennas and receive antennas of a BS.
1. Run the LST SECTOR command to query the numbers of the transmit antennas and
receive antennas of a sector.
Example:
LST SECTOR: SECTORID=0;
2. Run the MOD SECTOR command to set the numbers of the transmit antennas and receive
antennas of a sector.
Example:
MOD SECTOR: SECTORID=0, TXANTNUM=4, RXANTNUM=4;
NOTE
2. Run the MOD CARRIERBASICINFO command to set the antenna mode of a sector
carrier.
Example:
MOD CARRIERBASICINFO: SECTORID=0, CARRIERID=0, ANTBITMAP=2;
NOTE
The value range of ANTBITMAP is 0–2. 0 means using the antennas A and B of a 4T4R RRU to set
up a 2T2R configuration. 1 means using the antennas C and D of a 4T4R RRU to set up a 2T2R
configuration. 2 means using the antennas A, B, C, and D of a 4T4R RRU to set up a 4T4R
configuration.
NOTE
Software parameter 47 is the iCSD switch. 0 means disable, and 1 means enable.
2. Run the MOD OFDMACAPABILITY command to set the BS's capability in MIMO
negotiation.
Example:
MOD OFDMACAPABILITY: SECTORID=0, CARRIERID=0, DEMODULATIONMIMOSUPP=3,
MODULATIONMIMOSUPP=64;
Table 2-3 Downlink PUSC 1/3 + PUSC 1/3 STC Zone, uplink PUSC 1/3
Sector Parameter Setting
Table 2-4 Downlink PUSC with All + PUSC with All STC zone, uplink PUSC with All
Sector Parameter Setting
Table 2-5 Down link PUSC 1/3 + PUSC 1/3 STC Zone + PUSC with All + PUSC with All
STC Zone, uplink PUSC 1/3 + PUSC with All
Sector Parameter Setting
Table 2-6 Downlink PUSC 1/3 + PUSC 1/3 STC Zone + PUSC with All + PUSC with All
STC Zone, uplink PUSC with All
NOTE
l The 5 MHz bandwidth supports the subframe ratios of 35:12, 32:15, 29:18, and 26:21 and
supports only the configuration of all subcarriers (downlink PUSC with ALL + PUSC with All
STC zone, uplink PUSC with All). Configuration method: Three sectors use the same parameter
setting, and the values of SECTORID and DLSEGMENTNO must be set according to the actual
conditions.
l The 7 MHz bandwidth supports the subframe ratio of 21:12. Table 2-3 and Table 2-4 list the
configuration method of subcarriers.
Step 7 Query and set the MIMO and the AMS switches.
1. Run the LST RRMSWITCH command to query the MIMO switch of a sector carrier.
Example:
LST RRMSWITCH: SECTORID=0, CARRIERID=0;
2. Run the MOD RRMSWITCH command to set the MIMO switch of a sector carrier.
Example:
MOD RRMSWITCH: SECTORID=0, CARRIERID=0, DLAMCSWITCH=ON, DLMIMOSWITCH=ON,
DLAMSSWITCH=ON, MIMOBAMCSWITCH=ON;
Step 8 Activate the uplink CSM function. To activate the uplink CSM function, run MOD
RRMSWITCH to set Switch of uplink CSM to ON.
Example:
----End
Procedure
Step 1 To deactivate the downlink MIMO feature, run MOD RRMSWITCH to set Switch of
downlink MIMO to OFF. To deactivate the Matrix A and Matrix B adaptive function, set
Switch of the AMS algorithm on the downlink to OFF.
Example:
MOD RRMSWITCH: SECTORID=0, CARRIERID=0, DLMIMOSWITCH=OFF, DLAMSSWITCH=OFF;
Step 2 To deactivate the uplink CSM function, run MOD RRMSWITCH to set Switch of uplink
CSM to OFF.
NOTE
If the command does not take effect, deactivate the sector carrier, and then activate it again.
Example:
MOD RRMSWITCH: SECTORID=0, CARRIERID=0, ULCSMSWITCH=OFF;
----End
Related Parameters
Table 2-9, Table 2-10, Table 2-11, and Table 2-12 list the parameters related to the multi-
carrier feature.
SECTORID Sector ID
SECTORID Sector ID
CARRIERID Carrier ID
SECTORID Sector ID
CARRIERID Carrier ID
Power control and AMC algorithms are core algorithms of WiMAX. The MS and BS cooperate
over the R1 interface to achieve power control and AMC.
Definition
Power control is a process in which the MS or BS uses certain rules to adjust and control the
transmit power according to the change in the channel condition and the power of the received
signal. In the WiMAX system, power control is implemented mainly to control the transmit
power of the MS.
In AMC, an appropriate MCS is chosen according to the channel quality and system capacity.
Purpose
The purpose of power control is to control the transmit power of the MS, thereby ensuring the
data transmission quality in various radio environments.
In AMC, an appropriate MCS is chosen according to the channel quality and system capacity.
In this way, data transmission efficiency is maximized, and a high rate is achieved.
Power control and AMC can be used together to raise the system average throughput and
transmission quality. When the system capability is limited, the primary goal is to lower the PER
to the target value and minimize reverse interference.
Specifications
This feature supports uplink closed-loop power control, uplink open-loop power control, uplink
AMC, and downlink AMC.
l 64QAMCC2/3
l 64QAMCC3/4
l QPSKCTC1/2
l QPSKCTC3/4
l 16QAMCTC1/2
l 16QAMCTC3/4
l 64QAMCTC1/2
l 64QAMCTC2/3
l 64QAMCTC3/4
l 64QAMCTC5/6
NOTE
Impact
None.
Terms
Term Definition
BS Base Station
MS Mobile Station
Table 3-1 Network elements involved in the power control and AMC feature
AAA DHCP
SS/MS BS ASN-GW Server Server M2000
√ √ - - - √
NOTE
In Table 3-1, √ is used to mark the network elements involved in this feature, and - is used to mark the
network elements not involved in this feature.
Supporting Versions
Table 3-2 lists the versions that support the power control and AMC feature.
Table 3-2 Versions that support the power control and AMC feature
Product Version
BS DBS3900 V300R002C02
License Support
This feature is not subject to license restrictions.
Power Control
By control mode, power control is classified into closed-loop power control and open-loop power
control. Closed-loop power control is further classified into inner-loop power control and outer-
loop power control.
l Closed-loop power control
The BS measures the signal quality on the uplink and sends power control instructions to
the MS.
NOTE
You can run the MOD ULAMCTHRESH command to configure the values of Cinr Target Value for all
the MSs under a carrier. For details, see Step 2.
NOTE
l Different service scheduling types (UGS, eRTPS, RTPS, NRTPS, and BE services) have different
values of Per Target Value.
l You can run the MOD ULPERTHRESH command to configure the values of PER Target Value for
all the MSs under a carrier. For details, see Step 2.
The thresholds are adjusts by steps. The adjustments are accumulated. CINR threshold currently
used for inner-loop power control and AMC = Initial values of Cinr Target Value for all the
MSs under a carrier/Cinr Low Threshold/Cinr Up Threshold + accumulated adjusted value
l If the measured value of the PER is greater than Per Target Value, the Cinr Target
Value, Cinr Low Threshold, or Cinr Up Threshold is too low, and the BS automatically
raises Cinr Target Value, Cinr Low Threshold, or Cinr Up Threshold for the MS.
l If the measured value of the PER is smaller than Per Target Value, the Cinr Target
Value, Cinr Low Threshold, or Cinr Up Threshold is too high, and the BS automatically
lowers Cinr Target Value, Cinr Low Threshold, or Cinr Up Threshold for the MS.
This process is outer-loop power control.
The MS adjusts its transmit power according to the quality of the downlink signal. Open-loop
power control is fast and causes low overheads over the air interface. The drawback of open-
loop power control is low precision.
The uplink power control mode can shift between closed-loop power control and open-loop
power control. Closed-loop power control is precise. This type of power control, however, is
slow and causes high overheads over the air interface. Open-loop power control is fast and causes
low overheads over the air interface. This type of power control, however, is not precise.
A shift between the uplink power control modes is originated by the BS or MS. When the shift
is originated by the BS, the BS sends the PMC-RSP message to the MS, and the MS responds
with the PMC-REQ message acknowledging the receipt of the shift instruction. When the power
control mode shifts from closed-loop power control to open-loop power control, the MS can
start transmitting data on the uplink only if it has received both the PMC-RSP and UL noise and
interference level IE messages from the BS.
AMC
Uplink AMC
The basic principle of uplink AMC is that the BS instructs the MS to use a low-level MCS when
the measured CINR is below the Cinr Low Threshold for the FEC. The BS instructs the MS
to use a high-level MCS when the measured CINR is above Cinr Up Threshold for the FEC.
NOTE
You can run the MOD ULAMCTHRESH command to configure the values of Cinr Lower Threshold
and Cinr Upper Threshold for all the MSs under a carrier. For details, see Step 2.
Generally, uplink inner-loop power control is used together with AMC. In this way, power
control is implemented to adjust the actual CINR, and MCS is adjusted so that the uplink CINR
of the MS stays in the required range. Uplink inner-loop power control and uplink AMC are
implemented at the same time. When the uplink signal is poor, the MCS is lowered or the transmit
power of the MS is raised to ensure correct signal demodulation on the uplink. When the uplink
signal becomes good, the MCS is raised or the transmit power of the MS is lowered to ensure
correct signal demodulation on the uplink.
Downlink AMC
Closed-loop power control is used together with the mode of the MS requesting the MCS. The
MS reports the downlink CINR, and the BS decides the downlink MCS. If the value of the
parameter DownLink MS AMC Switch is set to ON, the system prefers and uses the downlink
MCS reported by the MS if possible. If the MS does not report the MCS, the BS determines the
downlink MCS. If the value of the parameter DownLink MS AMC Switch is set to OFF, the
BS decides the downlink MCS.
NOTE
You can run the MOD RRMSWITCH command to configure the value of the parameter DownLink MS
AMC Switch. For details, see .
You can run the MOD DLAMCTHRESH command to configure the values of Cinr Lower Threshold
and Cinr Upper Threshold for all the MSs under a carrier. For details, see Step 2.
Procedure
l Activate uplink inner-loop power control
1. To activate uplink inner-loop power control, run the MOD RRMSWITCH command,
with the value of the parameter UpLink Inner Loop Power Control Switch
(ULINNERLOOPPOWERSWITCH) set to NEWPCALG.
l Activate uplink outer-loop power control.
1. To activate uplink outer-loop power control, run the MOD RRMSWITCH command,
with the value of the parameter UpLink Outer Loop Power Control Switch
(ULOUTERLOOPPOWERSWITCH) set to ON.
2. If necessary, run the MOD ULPERTHRESH command to change the target PER
value and maximum adjustment step of each service. Generally, the default value is
recommended.
For example, the target PER and maximum adjustment step of the BE service are
BePer Target Value (BEPERTARGET) and BePer Maximum Adjust Step
(BEMAXADJSTEP) respectively.
l Activate uplink open-loop power control.
1. Run the MOD RRMSWITCH command to set the value of the parameter UpLink
Power Control Change MS Switch (ULPOWERCTRLMODEMSSWITCH) to
ON. After the value is set in this way, the BS starts open-loop power control if the MS
sends an open-loop power control request and the BS responds with a message
indicating that the power control mode is successfully changed.
By default, the BS starts closed-loop power control.
l Activate uplink AMC.
1. To activate uplink AMC, run the MOD RRMSWITCH command, with the value of
the parameter UpLink AMC Switch (ULAMCSWITCH) set to ON.
2. If necessary, run the MOD ULAMCTHRESH command to modify the initial values
of the parameters Cinr Target Value (CINRTARGET), Cinr Up Threshold
(CINRUPTHRE), Cinr Low Threshold (CINRLOWTHRE), and Maximum
Adjust Step(MAXADJUSTSTEP) for all the MSs under a carrier. Generally, the
default value is recommended.
l Activate downlink AMC.
1. To activate downlink AMC, run the MOD RRMSWITCH command, with the value
of the parameter DownLink AMC Switch (DLAMCSWITCH) set to ON.
2. If necessary, run the MOD DLAMCTHRESH command to modify the initial values
of the parameters Cinr Target Value (CINRTARGET), Cinr Up Threshold
(CINRUPTHRE), Cinr Low Threshold (CINRLOWTHRE), and Maximum
Adjust Step(MAXADJUSTSTEP) for all the MSs under a carrier. Generally, the
default value is recommended.
----End
Procedure
l Deactivate uplink inner-loop power control.
1. To deactivate uplink inner-loop power control, run the MOD RRMSWITCH
command, with the value of the parameter UpLink Inner Loop Power Control
Switch (ULINNERLOOPPOWERSWITCH) set to OFF.
l Deactivate uplink AMC.
1. To deactivate uplink AMC, run the MOD RRMSWITCH command, with the value
of the parameter UpLink AMC Switch (ULAMCSWITCH) set to OFF.
l Deactivate uplink outer-loop power control.
1. To deactivate uplink outer-loop power control, run the MOD RRMSWITCH
command, with the value of the parameter UpLink Outer Loop Power Control
Switch (ULOUTERLOOPPOWERSWITCH) set to OFF.
l Deactivate uplink open-loop power control.
1. Run the MOD RRMSWITCH command to set the value of the parameter UpLink
Power Control Change MS Switch (ULPOWERCTRLMODEMSSWITCH) to
OFF. After the value is set in this way, the BS does not support the power control
mode change, which is initiated by the MS.
l Deactivate downlink AMC.
1. To deactivate downlink AMC, run the MOD RRMSWITCH command, with the
value of the parameter DownLink AMC Switch (DLAMCSWITCH) set to OFF.
----End
Related Parameters
Table 3-3, Table 3-4, and Table 3-5 list the parameters related to the power control and AMC
feature.
This describes the basic concepts, functions, and implementation method of the idle mode
feature.
Definition
Idle mode allows an MS to move within a paging group (PG) composed by multiple BSs without
registration at a specific BS. After an MS enters idle mode, the MS periodically receives DL
broadcast messages. The BS deletes all the link information of the MS, and the ASN-GW retains
only the connection information of the MS on the paging controller (PC).
Purpose
When the SS/MS in idle mode roams to another cell, no handover process is triggered, thus
saving air interface resources and reducing the power of the SS/MS.
The idle mode feature also saves resources that may be wasted during handover of an SS/MS to
another BS when the SS/MS roams across a border of a BS. If the SS/MS is in idle mode, the
BS releases the resources reserved for the SS/MS, thus maximizing the use of the resources.
Network Model
Figure 4-1 shows the network model of the idle mode feature.
The BS incorporates a paging agent (PA), and the ASN-GW incorporates a paging controller
(PC)/location registration (LR).
A PG is a logical group composed by multiple BSs. A BS can belong to multiple PGs.
The PA interfaces with the SS/MS on the R1 interface and with the PC on the R6 interface.
Specifications
A BS supports three PGs.
Impacts
The idle mode feature saves air interface resources and network resources and improves the
capacity of a network.
Terms
Term Definition
Paging Group A logical group composed by multiple BSs. In the coverage of a PG, an
SS/MS can be periodically paged by a BS for location update or network
re-entry without establishment of an air interface link to the BS. A PG
is generally managed and deployed by the network management system
and is identified with a PG ID.
Paging Controller A function entity that implements the idle mode feature. The PC stores
the status and operation parameters of SSs/MSs in idle mode and controls
the paging operations of SSs/MSs in idle mode. PCs can be categorized
into two types: anchor PC and relay PC.
Paging Offset Paging frame offset. It is used together with a paging cycle to determine
the number of frames of a paging message. An SS/MS synchronizes its
paging cycle with the BS to receive broadcast messages that instruct the
SS/MS to exit idle mode or to perform location update.
Location A functional entity that stores the status and operation data of SSs/MSs
Registration in idle mode.
Location Update A process initiated when an SS/MS detects changes in the paging group
or the SS/MS is powered off.
Term Definition
BS Base Station
PA Paging Agent
PG Paging Group
PC Paging Controller
LR Location Registration
LU Location Update
Network Element
The idle mode feature requires the joint work of the SS/MS, BS, and ASN-GW. Table 4-1 lists
the network elements involved in the idle mode feature.
√ √ √ √ √ -
NOTE
In Table 4-1, √ indicates network elements that are involved in the idle mode feature, and - indicates
network elements that are not involved.
Version
Table 4-2 lists the versions that support the idle mode feature.
License
A license is not required for the idle mode feature.
1. The SS/MS sends a DREG-REQ message to the BS to request for idle mode entry.
l If the UL or DL data related to the SS/MS exists, the BS performs 2 .
l If the UL or DL data related to the SS/MS does not exist, the BS performs 4.
2. The BS sends a DREG-CMD message to the SS/MS to notify the SS/MS of later request
for idle mode entry after the REQ-duration expires.
3. After the REQ-duration expires, the SS/MS sends a DREG-REQ message to the BS to
request for idle mode entry.
4. The BS sends an IM_Entry_State_Change_Req message to the ASN-GW.
5. The ASN-GW returns an IM_Entry_State_Change_Rsp message to the BS.
6. The BS sends a DREG-CMD message to the SS/MS.
7. The BS sends an IM_Entry_State_Change_Ack message to the ASN-GW to indicate the
SS/MS idle mode entry.
8. The SS/MS exits the network, and the resources are released.
1. When the BS detects that the SS/MS needs to enter idle mode, the BS sends an
IM_Entry_State_Change_Req message to the ASN-GW.
2. The ASN-GW sends an IM_Entry_State_Change_Rsp message to the BS.
3. The BS sends a DREG-CMD message to the SS/MS.
4. The SS/MS sends a DREG-REQ message and enters idle mode.
5. The BS sends an IM_Entry_State_Change_Ack message to the ASN-GW to indicate the
SS/MS idle mode entry.
6. The SS/MS exits the network, and the resources are released.
4.3.2 Paging
This describes the paging process initiated by the ASN-GW.
Paging is a process in which a broadcast message is sent to notify an SS/MS in idle mode of
location update or network re-entry when the location information of the SS/MS needs to be
updated or data related to the SS/MS is present on the ASN-GW.
Paging Process
Figure 4-4 shows the paging process.
1. The ASN-GW sends a Paging_Announce message to all BSs in the PG where the SS/MS
resides.
l If Paging Cause contained in the Paging_Announce message is 0x01, SS/MS location
update is required.
l If Paging Cause contained in the Paging_Announce message is 0x02, SS/MS network
re-entry from idle mode is required.
2. The paged BS sends an MOB_PAG-ADV message to the SS/MS.
3. Based on Action Code contained in the MOB_PAG-ADV message, the SS/MS determines
whether to perform location update or to re-enter the network from idle mode.
l If Action Code is 0b01, the SS/MS performs location update.
l If Action Code is 0b10, the SS/MS re-enters the network from idle mode.
Location update can be classified into secure location update and insecure location update.
l If a valid secure context exists between the SS/MS and the BS, that is, the BS receives a
valid authentication key, secure location update is initiated. After the secure location update
is complete, the SS/MS remains in idle mode.
l If a valid secure context does not exist between the SS/MS and the BS, that is, the BS does
not receive a valid authentication key, insecure location update is initiated. Insecure
location update is actually a location update failure. After the insecure location update is
complete, the SS/MS re-enters the network from idle mode.
NOTE
If the location update is initiated by the ASN-GW, the process starts from 1.
If the location update is initiated by the SS/MS, the process starts from 5.
1. The ASN-GW sends a Paging_Announce message to all BSs in the PG where the SS/MS
resides.
2. The paged BS sends an MOB_PAG-ADV message to the SS/MS.
3. The SS/MS sends ranging codes at an assigned ranging region to the BS.
4. The BS sends an RNG-RSP message to the SS/MS.
l If Raging Status contained in the RNG-RSP message is continue, the process returns
to 3.
l If Raging Status contained in the RNG-RSP message is success, the process goes to
5.
5. The SS/MS sends an RNG-REQ message to the BS for location update.
6. The BS sends an LU-Req message to the ASN-GW to request for the SS/MS location
update.
7. The ASN-GW sends an LU-Rsp message to the BS to acknowledge the SS/MS location
update.
8. The BS sends an RNG_RSP message to the SS/MS to indicate successful location update
after the BS verifies the RNG_REQ message.
9. The BS sends an LU-Cnf message to the ASN-GW to indicate successful location update.
NOTE
If the location update is initiated by the ASN-GW, the process starts from 1.
If the location update is initiated by the SS/MS, the process starts from 5.
1. The ASN-GW sends a Paging_Announce message to all BSs in the PG where the SS/MS
resides.
2. The paged BS sends an MOB_PAG-ADV message to the SS/MS.
3. The SS/MS sends ranging codes at an assigned ranging region to the BS.
4. The BS sends an RNG-RSP message to the SS/MS.
l If Raging Status contained in the RNG-RSP message is continue, the process returns
to 3.
l If Raging Status contained in the RNG-RSP message is success, the process goes to
5.
5. The SS/MS sends an RNG-REQ message to the BS for location update.
6. The BS sends an LU-Req message to the ASN-GW to request for the SS/MS location
update.
7. The ASN-GW sends an LU_Rsp message to the BS.
8. The BS sends an RNG_RSP message to the SS/MS to indicate a location update failure if
any of the following conditions is met:
l The ASN-GW sends the LU-Rsp message to reject the SS/MS location update.
l The LU_Rsp message does not contain the SS/MS-related context.
l The BS fails to verify the RNG_REQ message.
9. The BS sends an LU-Cnf message to the ASN-GW to indicate location update failure.
10. The SS/MS re-enters the network from idle mode.
When the SS/MS enters idle mode, the BS starts a management resource holding timer for the
SS/MS. Depending on whether the timer expires, the SS/MS has different processes of network
re-entry from idle mode.
l The UL data is present on the SS/MS side, or the user of the SS/MS wants to re-enter the
network.
l The DL data related to the SS/MS is present on the ASN-GW side, and the paging controller
pages the BS in the PG and instructs the BS to broadcast a paging message for SS/MS
network re-entry from idle mode.
NOTE
If the SS/MS idle mode exiting is initiated by the ASN-GW, the idle mode exiting process starts from 1.
If the SS/MS idle mode exiting is initiated by the SS/MS, the idle mode exiting process starts from 5.
1. The ASN-GW sends a Paging_Announce message to all BSs in the PG where the SS/MS
resides.
2. The paged BS sends an MOB_PAG-ADV message to the SS/MS to instruct the SS/MS to
re-enter the network from idle mode.
3. The SS/MS sends ranging codes at an assigned ranging region to the BS.
4. The BS sends an RNG-RSP message to the SS/MS.
l If Raging Status contained in the RNG-RSP message is continue, the process returns
to 3.
l If Raging Status contained in the RNG-RSP message is success, the process goes to
5.
5. The SS/MS sends an RNG-REQ message to the BS for network re-entry from idle mode.
6. The BS sends an IM_Exit_State_Change_Req message to the ASN-GW after the BS detects
that the management resource holding timer expires.
7. The ASN-GW sends an IM_Exit_State_Change_Rsp message to the BS.
8. The BS sends an RNG-RSP message to the SS/MS after the BS verifies the validity of the
SS/MS.
9. The BS sends a Path_Reg_Req message to the ASN-GW for establishment of data links.
10. The ASN-GW sends a Path_Reg_Rsp message to the BS.
NOTE
If the SS/MS idle mode exiting is initiated by the ASN-GW, the idle mode exiting procedure starts from 1.
If the SS/MS idle mode exiting is initiated by the SS/MS, the idle mode exiting procedure starts from 5.
1. The ASN-GW sends a Paging_Announce message to all BSs in the PG where the SS/MS
resides.
2. After the BS receives the Paging Announce message, the BS sends an MOB_PAG-ADV
message to the SS/MS to instruct the SS/MS to re-enter the network from idle mode.
3. The SS/MS sends ranging codes at an assigned ranging region to the BS.
4. The BS sends an RNG-RSP message to the SS/MS.
l If Raging Status contained in the RNG-RSP message is continue, the process returns
to 3.
l If Raging Status contained in the RNG-RSP message is success, the process goes to
5.
5. The SS/MS sends an RNG-REQ message to the BS for network re-entry from idle mode.
6. The BS sends a RNG_RSP message to the SS/MS after the BS detects that the management
resource holding timer does not expire.
Procedure
Step 1 Run the DSP CARRIERSTATUS command to query the status of carriers.
l If carriers are unblocked, run the MOD CARRIERBLOCKFLAG command to block the
carriers.
l If carriers are blocked, go to Step 2.
NOTE
Step 4 Run the ADD PAGINGINF command to add a PG for the BS.
----End
Procedure
Step 1 Run the DSP CARRIERSTATUS command to query the status of carriers.
l If carriers are unblocked, run the MOD CARRIERBLOCKFLAG command to block the
carriers.
l If carriers are blocked, go to Step 2.
NOTE
----End
Related Parameters
Table 4-3 and Table 4-4 list the parameters related to the idle mode feature.
Parameter Description
SECTORID Sector ID
CARRIERID Carrier ID
Parameter Description
CarrierID Carrier ID
SectorID Sector ID
PagingGroupID PG ID
PagingControllerID PC ID
Parameter Description
Table 4-5 Performance measurement items related to the idle mode feature
Item Description
Idle entry success times See Successful Idle Entries Triggered by the MS.
triggered by MS
Idle entry success times See Successful Idle Entries Triggered by the BS.
triggered by BS
Idle entry rejected times by See Idle Entry Rejected Times by MS Times.
MS times
Location update times due See Location Update Times Due to Power Off.
to power off
Re-entry network success See Re-Entry Network Success Times From Idle.
times from idle
5 QoS Feature
The WiMAX BS can provide users with five different Quality of Service (QoS) levels. Users
need to choose the desired QoS level when subscribing to services.
Purpose
QoS is used to guarantee the end-to-end service quality. When the network is congested, QoS
guarantees reliable data transmission of important services and ensures efficient use of network
resources.
QoS offers operators with effective control over the use of network resources. With QoS, the
network supports existing and emerging multimedia services and applications. At the same time,
the network can distinguish between services and provide corresponding quality guarantee. In
this way, multiple services such as voice, video, and data can be converged on the same network.
With QoS, operators can divide users into detailed groups and provide user-specific
differentiated and value-added services.
Specifications
The IEEE 802.16e standard defines five service flow QoS sheduling types, that is, the UGS,
ertPS rtPS, nrtPS, and BE.
Impact
None.
Term
Term Definition
Latency Latency refers to the time it takes for the original data to go through a
series of processing steps such as coding, to be transmitted through the
channel, to arrive at the receiver, and to be decoded.
Term Definition
Packet loss rate Because of the limited buffer size of network switching equipment and
the interfering signals on the transmission links, packets may get lost on
the transmission links. The packet loss rate is the ratio of the number of
lost packets to the number of transmitted packets. The packet loss rate
is an important yardstick for measuring the quality of communication
links.
MS Mobile Station
SS Subscriber Station
BS Base Station
BE Best effort
√ √ √ √ - -
NOTE
Supporting Versions
Table 5-2 lists the versions that support the QoS feature.
License Restriction
This feature is not subject to license restrictions.
Upon subscription, the QoS profile is configured for subscribers through the Web Management
Access System (WMAS) of the AAA or the LMT of the ASN-GW. When a subscriber accesses
the network, the QoS profile is delivered to the WiMAX DBS3900 along with the pre-
provisioned service flow established. The DBS3900 is responsible for service flow management
and QoS scheduling.
See 5.3.3 QoS Transmission Control for the differentiated service, admission control, and load
control functions in Figure 5-1.
QoS Parameters
In the WiMAX system, QoS parameters are defined to describe scheduling rules for service
flows over the air interface. Each type of scheduling service is configured with a set of QoS
parameters: delay, tolerant jitter, and bandwidth. Each type of scheduling service matches with
a QoS parameter set.
UGS
The UGS is designed to support real-time uplink service flows that transmit fixed-size packets
on a periodic basis.
The BS assigns fixed bandwidth to the preceding service flows on a real-time and periodic basis.
In this way, the overheads consumed by requests from the SSs are reduced, and the real-time
requirements of the service flows are met. Therefore, in a UGS service flow, data is sent through
the bandwidth granted periodically by the BS, and the SS does not request bandwidth from the
BS.
The QoS parameters of the UGS are as follows:
l Maximum Sustained Traffic Rate (Maximum sustained rate, ADD QOSTEMP)
This parameter indicates the average peak rate of data service flows. On the uplink, the SS
ensures that the average rate of the service flows does not exceed the value of this parameter.
On the downlink, the BS limits the rate at the entry of the network. The value range of this
parameter is subject to restrictions due to the transmission capabilities of the air interface
and R6 interface. In addition, the value range of this parameter is related to the uplink and
downlink transmission capabilities of the SS. If the value of this parameter is too large or
too small, calculation is performed during the actual process of establishing the service
flow according to the resource management algorithm, and the calculation result determines
whether the service flow can be successfully established. Based on the current capabilities
of the SS and actual service requirements, the recommended value of this parameter is
between 256 kbit/s and 8 Mbit/s. Operators can provide services of different rates, for
example, 512 kbit/s, 1 Mbit/s, and 2 Mbit/s.
l Request/Transmission Policy (Transmission policy, ADD QOSTEMP)
This parameter is used to configure the attributes of service flows. In the latest IEEE 802.16e
R2D7, this parameter can indicate the following policies:
When the value of SDU flag is set to fixed, this parameter must be set. The size of the SDU
cannot exceed 254 bytes.
rtPS
The real-time polling service (rtPS) is designed to support real-time uplink service flows that
transmit variable-size packets on a periodic basis, such as MPEG video.
In the rtPS, the BS offers real-time, periodic, and unicast request opportunities, which enable
the service flow to inform the BS of its variable requirements for bandwidth on a periodic basis
so that the BS can grant variable burst bandwidth on a periodic basis for the service flow to
transmit variable-size packets. The rtPS requires more request overheads than the UGS but
supports variable grant sizes for optimum data transport efficiency.
The QoS parameters of the rtPS are as follows:
l Minimum Reserved Traffic Rate (Minimum guaranteed rate, ADD QOSTEMP)
This parameter indicates the minimum data rate reserved by the service flow. The BS offers
the bandwidth required by the minimum data rate reserved by the service flow. If the
bandwidth required by the service flow is less than the reserved bandwidth, the BS can use
the remaining part of the reserved bandwidth for other purposes.
l Request/Transmission Policy (Transmission policy, ADD QOSTEMP)
l Maximum Latency (Maximum latency, ADD QOSTEMP)
l SDUFLG (SDU flag, ADD QOSTEMP)
l SDUSZ (SDU size, ADD QOSTEMP)
l MAXLEN (Maximum burst length, ADD QOSTEMP)
Burst transmission is a type of intermittent data transmission mode. In burst transmission,
data generated at a low rate is buffered by the transmitter. When the buffered data is enough
to form a data group, the data is transmitted at a rate tens of times the rate at which the data
is generated. The receiver buffers the received data and forwards the data to users at normal
rates. The maximum burst length is determined according to the buffering capabilities and
maximum continuous service rate. Within a proper range, an increase in the buffers raises
the transmission rate.
ertPS
The extended real-time polling service (ertPS) is designed to support real-time service flows
that generate variable-size packets on a periodic basis, such as VoIP with silence suppression.
The ertPS is a scheduling mechanism that is built on the benefits of both the UGS and the rtPS.
The BS offers unicast grants in an unsolicited manner like in UGS, thus reducing the delay of
requests for bandwidth. Whereas UGS allocations are fixed in size, ertPS allocations are
dynamic. The BS can provide periodic uplink bandwidth allocations that can be used for
requesting bandwidth and data transmission. By default, the sizes of allocations correspond to
the current value of Maximum Sustained Traffic Rate of the service flow. The SS may request
a change in the size of the uplink allocation by using the Extended Piggyback Request field
of the grant management subheaders or the BR field of the MAC signaling headers or by sending
a codeword over the channel quality indicator channel (CQICH). The BS does not change the
size of uplink allocations until it receives another request for bandwidth change from the SS.
The QoS parameters of the ertPS are as follows:
l Maximum Sustained Traffic Rate (Maximum sustained rate, ADD QOSTEMP)
l Minimum Reserved Traffic Rate (Minimum guaranteed rate, ADD QOSTEMP)
This parameter indicates the minimum data rate reserved by the service flow. The BS offers
the bandwidth required by the minimum data rate reserved by the service flow. In the ertPS,
the reserved traffic rate is generally configured to be identical to the maximum sustained
traffic rate. On the downlink, bandwidth is allocated according to the data amount but
cannot exceed the maximum sustained traffic rate. On the uplink, the maximum sustained
traffic rate is always allocated. If the remaining bandwidth of the BS is below the maximum
sustained traffic rate when a service flow is established, the service flow cannot be
successfully established.
l Request/Transmission Policy (Transmission policy, ADD QOSTEMP)
l Maximum Latency (Maximum latency, ADD QOSTEMP)
l Tolerated Jitter (Maximum tolerant variation time, ADD QOSTEMP)
l SDUFLG (SDU flag, ADD QOSTEMP)
l SDUSZ (SDU size, ADD QOSTEMP)
l MAXLEN (Maximum burst length, ADD QOSTEMP)
nrtPS
The non-real-time polling service (nrtPS) is designed to support non-real-time uplink service
flows that transmit variable-size packets on a non-periodic basis, such as high-bandwidth FTP
service flows.
The BS offers unicast polls on a regular but not necessarily periodic basis, which ensures that
the service flow receives request opportunities even during network congestion. The service
flow can also send requests for bandwidth in a manner of competition.
The QoS parameters of the nrtPS are as follows:
l Minimum Reserved Traffic Rate (Minimum guaranteed rate, ADD QOSTEMP)
If the bandwidth required by the service flow is less than the reserved bandwidth, the BS
can use the remaining part of the reserved bandwidth for other purposes.
l Maximum Sustained Traffic Rate (Maximum sustained rate, ADD QOSTEMP)
l Request/Transmission Policy (Transmission policy, ADD QOSTEMP)
l SDUFLG (SDU flag, ADD QOSTEMP)
l SDUSZ (SDU size, ADD QOSTEMP)
l MAXLEN (Maximum burst length, ADD QOSTEMP)
BE
The best-effort (BE) service is designed to offer best-effort transmission and has the lowest
priority.
A BE service flow can use transmission opportunities offered by unicast polls or send bandwidth
requests in a manner of competition. The chance of the BE service flow using opportunities
offered by unicast polls depends on the load on the network. If the load on the network is light,
the BE service flow may probably have transmission opportunities. If the load on the network
is heavy, the chance of transmission opportunities is slim or even none. Therefore, when
transmitting BE service flows, the SS cannot relay on transmission opportunities offered by
unicast polls. The network provides no QoS guarantee for BE service flows.
The QoS parameters of the BE service are as follows:
l Maximum Sustained Traffic Rate (Maximum sustained rate, ADD QOSTEMP)
In addition, the BE service has another parameter that indicates the transmission attribute of the
service flow, that is, Traffic Priority (Flow priority, ADD FLOW).
This parameter defines the priority of the transmission. The bigger the parameter is, the higher
the priority is. For example, two service flows having the same QoS parameters except the
priority, so the service flow with a higher priority has lower latency and higher buffering
preference. If some other QoS parameters of the two service flows have different values, the
priority determined by these parameters is preferably considered.
For the detailed attributes and value ranges of the previous parameters, see
#wimax-9-73_table1.
The QoS transmission control mechanism defines the mapping relation between the transmission
bearer priorities and the WiMAX R6 interface transmission resource configuration and traffic.
It addresses many problems, for example, how to guarantee the service QoS, bandwidth utility
rate, and user fairness in the scenarios such as fixed transmission bandwidth, dynamically
changing bandwidth, branching transmission, and load balance. The QoS transmission control
involves the transmission differentiated service, transmission admission control, and
transmission overload control.
Differentiated transmission services use two types of rules. One is based on the priority indicator
in TOS field of the IP header; the other is the DSCP value in TOS. Currently, only the latter rule
is supported.
Procedure
l Run MML commands on the ASN-GW or the AAA to activate the QoS feature for the R1
interface. The procedure for running MML commands on the ASN-GW to activate the QoS
feature for the R1 interface is as follows:
Data collection
NOTE
The IP path is configured at a specific logical port, the IP address of the BS is the IP address of the
port, and the IP address of the gateway is the physical or logical IP address of the gateway.
3. Run the SET DIFPRI command to configure the priorities of differentiated services.
NOTE
l Configuring the priorities of differentiated services refers to specifying the DSCP priorities of
services. If this step is not performed, the system uses the default DSCP priorities for services.
l The BS needs to be restarted for the configuration of differentiated services to take effect.
For example, to configure the priorities of differential services (the priority rule is
DSCP, the signaling priority is 48, the VLAN priority for signaling is 6, the OAM
priority is 32, the OAM VLAN priority is 3, the OAMFTP priority is 1, the OMFTP
VLAN priority is 0), run the following command:
SET DIFPRI: PRIRULE=DSCP, SIGPRI=48, SIGVLANPRI=6, OAMPRI=32,
OAMVLANPRI=4, OAMFTPPRI=1, OAMFTPVLANPRI=0, DT1PRI=46, DT1VLANPRI =6
For example, you need to configure transmission admission control. The uplink and
downlink admission thresholds of high-priority subscribers (handover subscribers)
are 85%, and the uplink and downlink admission thresholds of new subscribers are
75%. That is, when the system load is lower than 75%, all subscribers are admitted.
When the system load is higher than 75% and lower than 85%, only the high-priority
subscribers are admitted. When the system load is higher than 85%, all subscribers
are not admitted. The value of USERDATATYPE5GBR is the fixed bandwidth that
is reserved for non-real-time services such as BE services. To make the preceding
configurations, run the following command:
SET TACALG: TRMULCACSWITCH=ON, TRMDLCACSWITCH=ON, TRMULVIPUSERCACTH=85,
TRMULUSERCACTH=85, TRMDLVIPUSERCACTH=75, TRMDLUSERCACTH=75,
USERDATATYPE5GBR=100, USERDATATYPE1ACTFACTOR=100,
USERDATATYPE2ACTFACTOR=100, USERDATATYPE3ACTFACTOR=100,
USERDATATYPE4ACTFACTOR=100, USERDATATYPE5ACTFACTOR=100;
For example, to configure the OLC algorithm (the UL OLC algorithm switch is OFF,
the DL OLC algorithm switch is ON, the UL OLC trigger threshold is 100, the UL
OLC release threshold is 0, the DL OLC trigger threshold is 100, the DL OLC release
threshold is 0, OLC time trigger is 0, the OLC action period is 100, the OLC release
bearer No. is 0), run the following command:
SET TOLCALG: TRMULOLCSWITCH=OFF, TRMDLOLCSWITCH=ON, TRMULOLCTRIGTH=100,
TRMULO
LCRELTH=0, TRMDLOLCTRIGTH=100, TRMDLOLCRELTH=0, TRMOLCTIMETRG=0,
TRMOLCACTIONPRD
=100, TRMOLCRELBEARERNUM=0;
----End
Related Parameters
For the detailed information of the QoS parameters, see the documents delivered with the
WASN9770 packet service gateway.
6 Handover Feature
This describes the handover feature of the WiMAX BS. The WiMAX BS supports hard
handovers, including intra-BS handovers and inter-BS handovers.
Definition
When the MS moves from one cell to another, the signal strength of the source cell becomes
weak whereas that of the target cell becomes strong, because of reasons such as distance. To
obtain better signal quality and ensure service continuity, the MS switches to the target cell. This
process is known as a handover, which is a major function enabling mobility management in
wireless communications.
The Huawei WiMAX BS supports handovers between the same frequency points of different
sectors. Intra-frequency handovers can be initiated by the MS or BS.
The Huawei WiMAX BS supports handovers between different frequency points of the same
sector or different sectors. Inter-frequency handovers can be initiated by the MS or BS.
Purpose
The purpose of handovers is to provide better service quality and ensure service continuity.
When the radio channels change or the BS is overloaded, the BS requires the terminal to initiate
a handover so that the terminal obtains better signal quality or service continuity. The MS itself
can also initiate handovers.
Specifications
None.
Impact
Improper network planning may cause frequent handovers, which affect subscriber services.
Terms
Term Definition
R6 interface This is the interface between the BS and the GW.It supports signaling
exchange between the BS and the GW and the setup of R6 tunnel to carry
the traffic of the MS.
Hard handover A hard handover is a handover in which the terminal is disconnected from
the source cell before a connection is established between the terminal and
the target cell.
MS Mobile Station
BS Base Station
√ √ √ - - √
NOTE
In Table 6-1, √ is used to mark the network elements involved in this feature, and - is used to mark the
network elements not involved in this feature.
Supporting Versions
Table 6-2 lists the versions that support the handover feature.
Product Version
License Support
This feature is subject to license restrictions.
Handover Processes
An entire handover consists of the following processes:
1. Handover preparation
2. Handover triggering
3. Network reentry
MS-Initiated Handover
Handover Preparation
1. The MS obtains the information of the neighboring BSs.
2. The serving BS sends the broadcast message MOB_NBR_ADV, which carries the
information of the neighboring BSs, to the MS.
3. The MS obtains the information of neighboring BSs through scanning.
4. The MS receives the broadcast message MOB_NBR-ADV from the BS, scans the signals
of the neighboring cells, obtains the downlink information, and issues a neighboring cell
scanning report. According to quality comparison, the MS selects a proper target cell for
the handover.
Handover Triggering
The MS can initiate a handover request according to the trigger configured by the BS. The
message carries the list of target BSs, and the MS can identify the measured values of the target
BSs according to the indicator bits.
Network Reentry
Network reentry refers to the process in which the MS enters the network again through the
target BS after sending the MOB_HO-IND message to the source BS. Different from the initial
network entry process, the network reentry process involves optimization. The target BS
implements optimization according to the MS information obtained from the source BS. The
target BS sends the optimization instruction to the MS through the RNG RSP message, and then
the MS performs network reentry optimization according to the optimization instruction. The
optimization of the process expedites network reentry and reduces the handover delay.
BS-Initiated Handover
Handover Preparation
In a scanning handover initiated by the BS, the BS detects that specific conditions are met and
then sends a scanning response to the MS. The response message carries a recommended list of
target BSs. After receiving the scanning response, the MS starts a scanning process and sends
the scanning report to the BS. After receiving the scanning report, the BS checks whether the
conditions for an outgoing handover are met. If the conditions are met, the BS sends a handover
request to the MS, which triggers a handover. Currently, the BS supports scanning triggered by
the following three conditions:
l When the BS detects that the uplink CINR of the MS is below the value of
SCANCINRBADTHRESH, a scanning process is triggered.
l When the BS detects that the PER of the MS is below the value of
SCANPERRBADTHRESH, a scanning process is triggered.
l When the BS detects that the load on a BS is above the value of LOADOUTTHRESH, a
scanning process is triggered by an MS that is heavily loaded. The scanning process is
stopped when any of the following conditions is met:
– The load on the BS is below the value of LOADOUTSTOPTHRESH.
The preceding three conditions can be used as the same time. In this case, the BS triggers a
handover process using the method whose condition is met first. A new handover process is not
triggered before the current handover process is complete.
Handover Triggering
A scanning handover process is triggered if the thresholds are properly set, scanning handovers
are enabled, and conditions are met. See detailed steps on how to perform proper configurations.
Network Reentry
Network reentry refers to the process in which the MS enters the network again through the
target BS after sending the MOB_MSHO-IND message to the source BS. Different from the
initial network entry process, the network reentry process involves optimization. The target BS
implements optimization according to the MS information obtained from the source BS. The
target BS sends the optimization instruction to the MS through the RNG RSP message, and then
the MS performs network reentry optimization according to the optimization instruction. The
optimization of the process expedites network reentry and reduces the handover delay.
Prerequisite
The licenses are activated.
NOTE
For details on how to upload, distribute, and query licenses for the DBS3900 WiMAX, see the M2000
Online Help.
Procedure
l Activate MS-initiated handovers.
1. On the M2000 client or Web LMT, run the MOD MACCAPABILITY command,
with the value of the parameter Support for mobility (MOBFEATURESUPP) set
to 1, which indicates that the BS supports handovers.
Check the value of bit 0 of the parameter Support for mobility
(MOBFEATURESUPP). If the value of the bit is 1, the handover feature is supported.
If the value of the bit is 0, the handover feature is not supported.
NOTE
The value range of the parameter Support for mobility (MOBFEATURESUPP) is 0–7.
l Bit 0: Mobility (HO) support
l Bit 1: Sleep mode support
l Bit 2: Idle mode support
If the value of the parameter Support for mobility (MOBFEATURESUPP) is 7, the BS
supports the handover, sleep mode, and idle mode.
2. Configure sector carriers on the M2000 client or Web LMT.
Run the DSP CARRIERSTATUS command to query the status of source sector
carriers and target sector carriers.
NOTE
The coverage environment required by handovers can be guaranteed only when the source
sector carrier and target sector carrier are active and available. In addition, the MS must be able
to enter the network through the configured sector carriers successfully.
3. Run the LST NBR command to query the configured neighboring cells.
For example, you need to query the neighboring relations, the BSID of the central BS
is 0000-2E00-6400, and the BSID of the neighboring BS is 0000-2F00-7000. Run the
following command: LST NBR: CBSID="0000-2E00-6400",
NBRBSID="0000-2f00-7000";
4. Run the ADD NBR command to add the neighboring cell relations.
For example, to add the neighboring cell relation between the central BS with BSID
0000-2E00-6400 and the neighboring BS with BSID 0000-2F00-7000, run the
following command: ADD NBR: CBSID="0000-2E00-6400",
NBRBSID="0000-2F00-7000";
5. Run the LST TRIGGER command to query the trigger information.
For example, to query the information of trigger 0 of carrier 0 under sector 0, run the
following command: LST TRIGGER:SECTORID = 0,CARRIERID =
0,TRIGGERID = 0;
6. Run the ADD TRIGGER command to configure the trigger information.
For example, to add the trigger information in a case where the sector number is 0,
the carrier number is 0, the trigger type is 1, the trigger function is 1, the trigger action
is 1, the trigger value is 1, and the trigger interval is 1, run the following command:
ADD TRIGGER: SECTORID=0, CARRIERID=0, TRIGGERID=1,
TRIGGERTYPE=1, TRIGGERFU NCTION=1, TRIGGERACTION=1,
TRIGGERVALUE=1, TRIGGERAVERDURATION=1;
l Activate BS-initiated handovers.
To activate BS-initiated handovers, you need to perform the preceding six steps and then
perform the step that follow.
1. Run the LST HOPARA command to query the handover parameters of the BS.
For example, you need to query the handover parameters of a BS, the sector ID is 0,
and the carrier ID is 0. Run the following command:
LST HOPARA:
NOTE
l When the value of the parameter DIFFREQHOSWITCH is set to ON and the frequency
point of the target BS detected by the MS belongs to an inter-frequency neighboring cell,
handover decision is performed according to the value of the parameter
HODIFFREQTHRESH, and an intra-frequency handover is initiated.
l When the value of the parameter DIFFREQHOSWITCH is set to OFF, an inter-frequency
handover is not initiated even if the MS detects an inter-frequency neighboring cell.
l If the MS detects an intra-frequency neighboring cell, an inter-frequency handover is not
performed, regardless of the value of the parameter DIFFREQHOSWITCH.
2. Run the MOD HOPARA command, with the value of the parameters
ULCINRHOSWITCH, ULPERHOSWITCH, LOADHOSWITCH, and
DIFFREQHOSWITCH set to ON.
For example, you need to modify the handover parameters of a BS, the sector ID is 0,
and the carrier ID is 0. Run the following command:
----End
Procedure
Step 1 On the M2000 client or Web LMT, run the MOD MACCAPABILITY command, with the
value of the parameter Support for mobility (MOBFEATURESUPP) set to 0, which indicates
that the BS does not support handovers.
Step 2 Run the RMV NBR command to remove the neighboring cell relations so that the MS cannot
find target neighboring cells for handovers.
For example, you need to remove the neighboring cell relations, the central BSID is
0000-2E00-6400, and the BSID of the neighboring cell is 0000-2F00-7000. Run the following
command:CBSID="0000-2E00-6400", NBRBSID="0000-2F00-7000";
Step 3 Run the MOD HOPARA command, with the value of the parameters
ULCINRHOSWITCH, ULPERHOSWITCH, LOADHOSWITCH, and
DIFFREQHOSWITCH set to OFF.
----End
Related Parameters
Table 6-3, Table 6-4, and Table 6-5 list the parameters related to the handover feature.
Parameter Meaning
Parameter Meaning
SECTORID Sector ID
CARRIERID Carrier ID
This describes the automatic discovery feature, which is the application of DHCP in the WiMAX
system.
Definition
Automatic discovery is a function that automatically assigns OM IP addresses to the BSs through
the DHCP function and establishes OMLs between the M2000 and the BSs so that the BSs are
automatically managed by the M2000 in a centralized manner.
Purpose
The automatic discovery feature effectively simplifies local maintenance of the BSs. With this
feature, local software commissioning is not necessary during site deployment.
After the BS is powered on, the DHCP server automatically assigns the BS the parameters
required for the establishment of the OML. Then, the OML between the M2000 and the BS is
automatically established. All the software commissioning work on the BS can be performed
on the management center in a centralized manner. In this way, the maintenance cost is lowered.
Specifications
None.
Impact
l The automatic discovery feature is mainly used during site deployment. If automatic
discovery fails during site deployment, local software commissioning must be performed.
In this case, remote centralized configuration is not possible.
l The automatic discovery feature does not interfere with the daily operation of the system.
l The information about the OML established through the automatic discovery feature is not
saved to the data configuration file. Therefore, engineers need to use MML commands on
the M2000 to manually configure the OML information of the network element for future
use and maintenance.
l If the OML parameters need to be configured manually, the DHCP function must be
disabled first, and the parameter configuration must be consistent with that on the DHCP
server. Otherwise, the DHCP function modifies the manually configured parameter values
in the case of intermittent interruptions of the OML, and the OML may malfunction.
Terms
Term Definition
OML Link between the BS and the M2000 for operation and maintenance
BS Base Station
MS Mobile Station
SS Subscriber Station
- √ - - √
NOTE
In Table 7-1, √ is used to mark network elements that are involved in this feature, and - is used to mark
network elements that are not involved in this feature.
Supporting Versions
Table 7-2 lists the versions that support the automatic discovery feature.
License Support
This feature is not subject to license restrictions.
Principle Description
The automatic discovery feature is achieved through the DHCP server configured on the M2000.
The DHCP server configured on the M2000 server is responsible for allocating IP addresses for
the BSs. This server is different from the DHCP server that is responsible for allocating IP
addresses for the terminals. The DHCP server is responsible for assigning BSs configuration
parameters related to the operation and maintenance links (OMLs), for example, OM IP
addresses. After a BS configures its own OM transmission parameters, it can establish an OML
to communicate with the M2000. Meanwhile, with the cooperation of the DHCP server, the BS
and M2000 can interact to achieve mutual discovery. In this way, the M2000 manages the BSs
in a centralized manner.
This feature enables the following functions:
l After a BS is powered on, it automatically obtains the OML parameters through the DHCP
protocol to establish the OML.
l The M2000 automatically discovers and manages network elements.
Application Scenarios
Generally, the BSs are converged on the bearer network and connected to the ASN-GW and
M2000.
When the M2000 and the BS are configured in the same network segment, the DHCP broadcast
messages from the BS can be sent to the DHCP server on the M2000 directly through the IP
bearer network.
When the M2000 and the BS are not configured in the same network segment, the DHCP relay
service needs to be configured on the layer 3 switching device that is configured on the IP bearer
network and closest to the BS. The broadcast messages are sent to the DHCP server on the
M2000 through the layer 3 switching network.
After a BS is powered on, it requests its own OM transmission parameters from the DHCP server
on the M2000 through the DHCP protocol. These parameters are used to establish the OML
between the BS and the M2000. In order for the DHCP broadcast packets from the BS to be sent
over the IP bearer network and received by the M2000, the DHCP relay service needs to be
configured on the layer 3 switching equipment closest to the BS on the bearer network so that
the broadcast packets from the BS are converted to unicast packets and sent to the DHCP server
on the M2000 through the layer 3 switching network. The detailed configuration is related to
the network segment information of the subnetwork served by the relay server and the IP address
of the destination DHCP server. For details on the configuration commands and procedure, see
the manuals of the specific equipment.
Principle
The automatic discovery feature is used mainly during site deployment. The user needs to plan
the OM transmission parameters of the BSs. After each BS is powered on at the site, it
automatically establishes an OML between itself and the M2000. In this way, the maintenance
personnel can perform centralized maintenance for the BSs on the M2000. The principle of this
feature is as follows:
1. The user plans OM transmission parameters for each BS on the network according to the
actual situations of the bearer network and the details of network planning. Table 7-3 lists
the OM transmission parameters.
2. The user types the information in the parameter table on the DHCP server on the M2000.
The parameter table can take the form of an Excel worksheet, which can be imported to
the DHCP server. At this time, the DHCP already can provide services. This Excel template
can be obtained from the DHCP server configuration tool. The user only needs to export
the worksheet from the tool.
3. The user installs the hardware and powers on the BS.
NOTE
If the ESN of the BS cannot be determined, the user needs to report the ESN and physical location
to the personnel at the network management center and ask them to record the ESN on the DHCP
server.
4. By interacting with the DHCP server, the BS obtains its own OM transmission parameters.
5. The BS validates the OM transmission parameters that it obtains.
6. The M2000 automatically creates the BS in the topology view and establishes an OM
management link between itself and the BS.
7. The user manages the BS in remote mode and performs software commissioning through
the M2000.
The parameters listed in Table 1 are crucial to the establishment of the OML. If parameter
planning is incorrect, the network management center may fail to manage the BS. In this case,
the configurations of the DHCP server on the M2000 and of the topology on the M2000 need
to be modified so that the BS can be managed through the network management center in remote
mode. Some parameters, mainly the OM IP address of the BWA, listed in Table 1 need to be
modified.
If the DHCP switch is set to ON, the BS originates a DHCP request to reconnect to the M2000
after detecting that it is disconnected from the M2000 for a period of time. The OML parameters
obtained through the DHCP protocol are not written into the configuration data of the BS and
therefore not permanently saved after the BS is powered off. If the OML parameters need to be
written into the configuration data after automatic discovery is performed, you need to run
associated MML commands to configure OML parameters the same as those planned on the
DHCP server. Otherwise, the BS automatically uses the parameters saved in the configuration
data and may break away from the management of the M2000.
Prerequisite
l The M2000 works properly, and the M2000 client is functional.
l The DHCP server assigning IP addresses for the BSs is already deployed, and the DHCP
software is already installed. The DHCP server can be deployed on the same computer as
the M2000.
l The DHCP relay service is available on the layer 3 switch that is closest to the BS among
all the layer 3 switches between the BS and the M2000, and the relay parameters are
configured. After the configuration, DHCP broadcast messages from the BSs can reach the
M2000, and response messages from the M2000 can be received by the BSs.
Data Preparation
When configuring the BS data through the WCS, you need to create NEs on the M2000 topology.
Fill the planned NE information in the DHCP Parameter Template, and then create NEs in
batches through the DHCP tool.
NOTE
Procedure
Step 1 Copy the filled DHCP parameter template to a folder under a path of the M2000 client.
Step 2 On the iManager M2000 Mobile Element Management System, choose Configuration >
DHCP Configuration Tool. The DHCP Configuration Tool interface is displayed, as shown
in Figure 7-1.
If the login fails, the system displays the following message Server may be not running. System
will be exit!. In this case, log in to the M2000 server as the superuser in Telnet mode, and then
run the start_dhcpserver command to start the DHCP service.
If the system displays the following message DHCPServer start succeed!, you can
infer that the DHCP service is started successfully.
Step 3 In the DHCP Configuration Tool interface, click , select the DHCP parameter template,
and then import the DHCP parameters to the DHCP server.
Click the DBS3900 Wimax tab to view the imported data.
Step 4 On the iManager M2000 Mobile Element Management System, choose Topology > Main
Topology to view the Main Topology tab page.
Step 5 On the Main Topology tab page, select the ASN-GW to be connected to the NE, right-click the
ASN-GW, and then select Search BTS from the shortcut menu.
All the NEs imported by the DHCP tool are displayed on the Main Topology tab page. Creating
NEs is complete.
----End
Procedure
Run the SET DHCPFUNC command, with the value of the parameter STRFLG set to
DISABLE.
CAUTION
If this command is successfully run, the BS does not automatically originate DHCP requests. In
this case, if the manually configured OM IP address is faulty, the network management center
cannot manage the BS. Therefore, you should be cautious about running this command.
----End
Related Parameters
Table 7-4 lists the parameters related to the automatic discovery feature.
Parameter Meaning
By default, the DHCP function is enabled for the BS. Unless necessary, do not disable the DHCP
function of a BS by using this command.
8 FFR Feature
Definition
FFR is an enhanced function of the WiMAX system. With this function, one frequency point
can have PUSC zones and PUSC with all SC zones on the uplink or downlink. The BS instructs
the MS to switch between different zones according to the signal quality.
Purpose
The FFR networking mode is a hybrid networking mode. In this mode, all the BSs uses the same
frequency point. At the borders of cells, only some of the sub-carriers are used to guarantee
coverage. In areas where the signal quality is good, all the sub-carriers are used to guarantee
efficient use of frequency spectrum resources.
Specifications
None.
Impact
None.
Terms
Term Definition
Zone A zone comprises a group of OFDMA symbols that uses the same
substitution formula. The PUSC zone is an example.
Zone switching In FFR networking mode, the BS instructs the MS to switch between
partial use of sub-carriers and use of all sub-carriers according to the
signal quality.
BS Base Station
√ √ - - -
NOTE
In Table 8-1, √ is used to mark network elements that are involved in this feature, and - is used to mark
network elements that are not involved in this feature.
Supporting Versions
Table 8-2 lists the versions that support the FFR feature.
Product Version
License Support
This feature is not subject to license restrictions.
The WiMAX BTS supports networking modes such as PUSC(1,1,3), PUSC with all SC(1,3,3),
and FFR(1,1,3). In FFR networking mode, the zone switching function is used to ensure that the
MS can switch between different zones. In this way, co-channel interference is avoided.
Networking Modes
PUSC with all SC(1,3,3) Networking Mode
In PUSC with all SC(1,3,3) networking mode, the three sectors of a BTS use different frequency
points, and each sector uses the PUSC with all SC method on the uplink and downlink. This
networking mode is applicable to operators that have sufficient frequency resources. In this
mode, co-channel interference between BTSs is avoided, and the throughput of each sector and
the entire network is guaranteed.
In FFR(1,1,3) networking mode, the entire network uses one frequency point. Areas far from
the BTS uses the PUSC substitution mode, and each of the three sectors of a BTS use one-third
of the sub-channels at the same frequency point, as shown by the blue area in Figure 8-3. Zones
close to the BTS uses the PUSC with all SC substitution mode, and the three sectors of the BTS
uses all the sub-channels at a frequency point.
The FFR(1,1,3) networking mode is superior to the PUSC(1,1,3) networking mode in that the
former can both guarantee coverage at borders and improve the throughput of the entire BTS.
The FFR(1,1,3) networking mode requires a precise and fast zone switching algorithm. The BTS
switches the MS to a proper zone according to the uplink and downlink conditions of the MS.
Zone Switching
Zone Switching Process
1. In FFR networking mode, the MS enters the PUSC zone by default after entering the
network. If the PUSC zone resources are not sufficient, the MS enters the PUSC with all
SC zone.
2. When the MS is in the PUSC zone, it reports the CINR of the downlink PUSC zone in real
time. After receiving the CINR from the MS, the BS decides whether the CINR exceeds
the zone switching measurement threshold. If the CINR exceeds the zone switching
measurement threshold, the BS requires the MS to measure the CINR of the PUSC with
all SC zone. If the average CINR of all the sub-channels in a period of time exceeds the
threshold for switching from one-third of the sub-carriers to all the sub-carriers, the BS
switches the MS from the 1/3-sub-carrier zone to the all-sub-carrier zone.
3. When the MS is in the PUSC with all SC zone, it reports the CINRs of all the downlink
sub-carriers in real time. After receiving the CINRs reported by the MS, the BS decides
whether they exceed the threshold for switching from all the sub-carriers to one-third of
the sub-carriers. If they exceed the threshold for switching from all the sub-carriers to one-
third of the sub-carriers, the BS switches the MS from the all-sub-carrier zone to the 1/3-
sub-carrier zone.
Settings of Parameters Related to Zone Switching
1. You can run the MOD CARRIERZONEINFO command to set the zone type.
MOD CARRIERZONEINFO: SECTORID=0, CARRIERID=0, DLZONENUM=2, DLZONEIND=9,
DL2NDSTARTSYMBOL=21, DL2NDZONESCHNUM=30, ULZONENUM=2, ULZONEIND=5,
UL2NDSTARTSYMBOL=15, UL2NDZONESCHNUM=35;
2. You can run the MOD CARRIERBASICINFO command to configure the basic
information of the carriers.
MOD CARRIERBASICINFO: SECTORID=0, CARRIERID=0, DLSEGMENTNO =0,
DLBITMAP="00000003", ULBITMAP="000000000000000FFF";
3. You can run the MOD FFRPARA command to configure the measurement threshold.
MOD FFRPARA: SECTORID=0, CARRIERID=0, PUSCTOALLMEATH=18;
4. You can run the MOD FFRPARA command to configure the switching threshold.
MOD FFRPARA: SECTORID=0, CARRIERID=0, PUSCTOALLSWITCHTH=20,
ALLTOPUSCSWITCHTH=16;
Procedure
This is an inherent feature of the system, and activation is not required.
----End
Procedure
This is an inherent feature of the system, and deactivation is not possible.
----End
Related Parameters
Table 8-3 lists the parameters related to the FFR feature.
Parameter Meaning
SECTORID Sector ID
CARRIERID Carrier ID