WiMAX Network Parameter Planning and Configuration

INTERNAL

WiMAX Network Parameter Planning and Configuration

1
Important Contents: 1. 2. 3. 4. 5.

Overview

Currently, many network planning parameters are found incorrect or missed during the check on parameters for all sites in the world. Many parameters with unclear definitions or indefinite configuration methods are also found. After the parameters are sorted out, the PN planning and configuration instruction is thereby provided for all WiMAX sites in the world.

Reuse of UL permbase must be planned in non 1/3 networking. The permbase and PRBSID must be configured separately for DL STC Zone to generate different scrambles and differentiate co-frequency sector signals. Reuse of the CDMAGROUPSTART parameter (start position of UL ranging code) should be planned in 1/3 networking. The IDCELL and segment ID of the first DL zone are not configured separately. Code is automatically obtained from Preamble Index. The permbase and PRBSID are shared by DP zone (in the case of beam forming) and non DP zone. It is unnecessary to plan the permbase and PRBSID of the DP zone separately. In the 5 MHz networking, reuse of the UL permbase is planned in the value range of 0 to 15. The preamble planning involved in this document is updated in the APUS V1.7.3. When the correctness of inputs is ensured, the planning results should comply with the planning principles.

6. 7.

2013-7-9

Huawei Technologies Proprietary

WiMAX Network Parameter Planning and Configuration

INTERNAL

Preamble Planning Principle and Method

2.1 Preamble Planning Principle

Currently, a total of 96 preambles numbered from 0 to 95 are used for planning. A one-to-one correspondence exists between preambles and IDCELL/segment ID. The value of IDCELL ranges from 0 to 31, and the value of Segment ID ranges from 0 to 2. The key of preamble planning is the IDCELL planning.

Principle: The 96 geographically nearby co-frequency carriers are treated as a cluster (the shape of the cluster should be close to a square). The 96 preambles are allocated on the principle of IDCELL reuse in the longest distance. The preambles are allocated and reused for different clusters in the same manner, thus ensuring the maximum distance between sectors with the same frequency and the same preamble.

2.2 Preamble Planning Method

Use the APUS to plan the preambles. The planning results include the planning of IDCELL and segment ID. Note: The APUS involves the reuse of IDCELL and segment ID in the longest distance, laying a foundation for subsequent UL preamble planning.

2013-7-9

Huawei Technologies Proprietary

WiMAX Network Parameter Planning and Configuration

INTERNAL

Planning and Configuration of Permbase and PRBSID

In WiMAX networks, the generation of UL and DL scrambles is related to permbase and PRBSID. DL zones include PUSC Zone, STC PUSC, PUSC all Zone, STC PUSC all Zone, PUSC DP Zone, STC PUSC DP, PUSC all DP Zone, and STC PUSC all DP Zone. Each zone has independent scrambles. The scrambles of the first zone are determined by IDCELL and segment ID, without having to configure the permbase and PRBSID. For other zones, the preamble and PRBSID need to be configured, but the preamble and PRBSID of DP zones are combined with those of non DP zones. The enabling of beam forming does not involve the modification of permbase and PRBSID. UL zones include only PUSC Zone and PUSC all Zone but do not include STC and DP zones. Therefore, the generation of UL scrambles is related only to DL IDCELL, and there is no UL PRBSID. The UL permbase should still be configured for UL sub-carrier mapping and UL ranging code generation.

3.1 Permbase and PRBSID Planning Principles

The permbase has 32 values like IDCELL, and the PRBSID has three values like the segment ID. After combination, a total of 96 scrambles can be generated. The planning principle of these scrambles is the same as that of preamble index. To simplify the planning, assign the value of IDCELL directly to the permbase of DL zones. The PRBSID is equal to MOD(segment ID + 1,3). The value of PRBSID complies with the protocol specification after ICIC is enabled, thus achieving backward compatibility with ICIC. The UL preamble planning mainly concerns the UL sub-carrier mapping to reduce the interferences caused by co-frequency sectors. In the 1/3 networking, the UL permbases should be consistent in the whole network, thus ensuring that no interferences exist between cofrequency and inter-segment sectors. In With All networking, permbase is reused in cofrequency sectors. For planning simplicity, the value of UL permbase is the same as the value of DL IDCELL in with All networking. (Note: When the APUS is used to plan preambles, the planning results already concerns the reuse of IDCELL between co-frequency sectors.)

2013-7-9

Huawei Technologies Proprietary

WiMAX NWP Parameter Planning and Configuration

INTERNAL

In 5 MHz bandwidth networking, UL permbase has 17 values ranging from 0 to 16. Therefore, in 5 MHz bandwidth networking, 17 co-frequency sectors are used as a cluster to reuse the UL permbases. To reuse code, the APUS V1.7.3 treats 16 co-frequency sectors numbered from 0 to 15 as a cluster for planning.

For ICIC-enabled zones, the UL and DL permbases should be configured to the same, thus ensuring that no interferences caused by sub-carrier quadrature in adjacent sector edge bands. Currently, the ICIC function can be enabled only for V3R3 in the co-frequency FFR networking.

3.2 Permbase and PRBSID Configuration Methods

Note: There are 11 fields related to DL permbase and PRBSID and three fields related to UL permbase and PRBSID in Carrier zone info of MML commands, as listed in the following table. DL PUSC Zone PUSC ALL Zone STC PUSC Zone STC PUSC ALL Zone FUSC Zone BAND Zone UL PUSC Zone PUSC ALL Zone BAND Zone Permbase DLPUSCPERMBASE DLPUSCALLPERMBASE DLPUSCSTCPERMBASE DLPUSCALLSTCPERMBASE DLFUSCPERMBASE DLBANDPERMBASE Permbase
ULPUSCPERMBASE ULPUSCALLPERMBASE ULBANDPERMBASE

PRBSID None DLPUSCALLPRBSID DLPUSCSTCPRBSID DLPUSCALLSTCPRBSID DLFUSCPRBSID DLBANDPRBSID

DLPUSCPERMBASE is temporarily not concerned because the IDCELL value directly read from code is always invalid, and other zone fields should be determined according to the networking type. Because these fields are not used in the FUSC and band networking types, little concern is required temporarily. The following sections describe the configuration in different networking types.

WiMAX Network Parameter Planning and Configuration

INTERNAL

3.2.1 PUSC 1x3x1 Networking

PUSC 1/3 Networking DL PUSC PUSC ALL FUSC BAND UL PUSC PUSC ALL BAND PERMBASE Invalid (values are assigned automatically based on IDCELL) Invalid Invalid Invalid PERMBASE Identical on the whole network Invalid Invalid PRBSID Unavailable Invalid Invalid Invalid STCPERMBASE =IDCELL Invalid STCPRBSID =MOD(Seg ment+1,3) Invalid

MOD(SegmentID+1,3) means the remainder from a division of (segmentID+1) by 3. This is specified by the protocol after the ICIC function is enabled to implement backward compatibility. "Invalid" means that the value is not read no matter what value is set. The 5 MHz 1/3 networking is not supported.

3.2.2 PUSC with all Networking

PUSC with All Networking DL PUSC PUSC ALL FUSC PERMBASE Invalid Invalid (values are assigned automatically based on IDCELL) Invalid PRBSID STCPERMBASE STCPRBSID Invalid =MOD(Seg ment+1,3)

Unavailable Invalid Invalid Invalid Invalid Invalid

BAND Invalid UL PUSC PERMBASE Invalid =IDCELL in the case of 10 MHz networking; reuse permbases 0 to 15 or use the APUS to plan results in the case of 5 MHz networking

PUSC ALL

2013-7-9

Huawei Technologies Proprietary

WiMAX NWP Parameter Planning and Configuration

INTERNAL

BAND Invalid

MOD(SegmentID+1,3) means the remainder from a division of (segmentID+1) by 3. This is specified by the protocol after the ICIC function is enabled to implement backward compatibility. "Invalid" means that the value is not read no matter what value is set. In the UL with all networking, adjacent co-frequency carriers need to use different values of ULPUSCALLPERMBASE. The IDCELL planning of the APUS already concerns the reuse between adjacent co-frequency carriers. Therefore, ULPUSCALLPERMBASE can be assigned with the value of IDCELL easily and quickly. (Note: In the 10 MHz bandwidth networking, ULPERMBASE has 35 values, but it has only 32 values after it is assigned the values of IDCELL.) In the 5 MHz networking, permbase should be planned manually under the value range of 0 to 15 or by using the APUS V1.7.3.

3.2.3 Single-Frequency FFR Networking (Applicable to V3R2C03 and Later Versions)

Single-Frequency FFR Networking DL PERMBASE Invalid (values are assigned automatically based on IDCELL) =IDCELL Invalid Invalid PERMBASE Identical on the whole network Invalid Invalid PRBSID STCPERMBASE STCPRBSID

PUSC

Unavailable

=IDCELL

=MOD(Segment+1, 3)

PUSC ALL FUSC BAND UL PUSC PUSC ALL BAND

=MOD(Segment +1,3) Invalid Invalid

=IDCELL

=MOD(Segment+1, 3)

MOD(SegmentID+1,3) means the remainder from a division of (segmentID+1) by 3. This is specified by the protocol after the ICIC function is enabled to implement backward compatibility. "Invalid" means that the value is not read no matter what value is set. The 5 MHz FFR networking is not supported.

WiMAX Network Parameter Planning and Configuration

INTERNAL

3.2.4 Multi-Frequency FFR Networking

Multi-Frequency FFR Networking DL PERMBASE PRBSID STCPERMBASE STCPRBSID

PUSC

Invalid (values are assigned automatically based on IDCELL)

=IDCELL

Unavailable

=IDCELL

=MOD(Segment+1,3)

PUSC ALL
FUSC BAND UL

=MOD(Segment+1,3)

=IDCELL

=MOD(Segment+1,3)

Invalid Invalid
PERMBASE

Invalid Invalid

PUSC PUSC ALL BAND

Invalid
=IDCELL

Invalid

MOD(SegmentID+1,3) means the remainder from a division of (segmentID+1) by 3. This is specified by the protocol after the ICIC function is enabled to implement backward compatibility. "Invalid" means that the value is not read no matter what value is set. In the UL with all networking, adjacent co-frequency carriers need to use different values of ULPUSCALLPERMBASE. The IDCELL planning of the APUS already concerns the reuse between adjacent co-frequency carriers. Therefore, ULPUSCALLPERMBASE can be assigned with the value of IDCELL easily and quickly. The 5 MHz FFR networking is not supported.

2013-7-9

Huawei Technologies Proprietary

WiMAX Network Parameter Planning and Configuration

INTERNAL

Ranging Code Planning

(Applicable to V3R3 and Earlier Versions)

The ranging code is a pseudo-random sequence that is 144 bits long. The protocol specifies the generation modes of ranging codes. The generated sequence is related only to the value of UL permbase, but the value of one permbase can generate 256 ranging codes. The ranging codes are classified into four types: IR, PR, BR, and HR. The current product supports a code set constituted by four ranging codes of each type. Therefore, a carrier requires only 16 ranging codes, and 256 codes can be allocated to 16 carriers. The ranging code planning mainly involves the values of CDMAGROUPSTART in CarrierBasicInfo of MML configuration. The 256 codes are grouped into 16 code sets, and the start position of each code set is 16n (n indicates an integer ranging from 0 to 15). The ranging code planning is to plan the start positions of these code sets.

4.1 Principles of Ranging Code Planning

In the UL 1/3 networking, because ULPERMBASE is the same, the generated 256 ranging codes must be reused between co-frequency carriers. The value of CDMAGROUPSTART is 16n (n indicates an integer ranging from 0 to 15), and there are totally 16 values. In With ALL networking, because the values of ULALLPERMBASE of adjacent cofrequency carriers are different, the ranging code sets generated by the adjacent carriers are different and do not interact even though the values of CMDAGROUPSTART are the same. To keep the consistency with the 1/3 networking, it is suggested to classify 16 co-frequency sectors into a cluster to reuse the ranging codes.

4.2 Methods for Ranging Code Planning

The ranging code planning methods are different in different networking types. See the following table.

2013-7-9

Huawei Technologies Proprietary

WiMAX NWP Parameter Planning and Configuration

INTERNAL

Networking Type PUSC networking 1x3x1

CDMAGROUPSTART Planning Method Sixteen carriers are classified into a cluster to reuse CDMAGROUPSTART. The value of CDMAGROUPSTART is 16n (n indicates an integer ranging from 0 to 15). The planning can be performed manually or automatically by using the APUS V1.7.3.

PUSC with networking Single-frequency FFR networking

all

There is no requirement on CDMAGROUPSTART planning when the correctness of ULALLPERMBASE planning is ensured. It is suggested to use the APUS V1.7.3 to perform automatic planning. Sixteen carriers are classified into a cluster to reuse CDMAGROUPSTART. The value of CDMAGROUPSTART is 16n (n indicates an integer ranging from 0 to 15). Note: Currently, the planning can be performed manually or automatically by using the APUS V1.7.3.

Multi-frequency FFR networking

There is no requirement on CDMAGROUPSTART planning when the correctness of ULALLPERMBASE planning is ensured. It is suggested to use the APUS V1.7.3 to perform automatic planning.