SGSN Pool

SGSN Pool
GBSS12.0
Feature Parameter Description
Issue 01
Date 2010-06-30
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2011. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
GSM BSS
SGSN Pool Contents
Contents
1 Introduction ................................................................................................................................1-1
1.1 Scope ............................................................................................................................................ 1-1
1.2 Intended Audience ........................................................................................................................ 1-1
1.3 Change History.............................................................................................................................. 1-1
2 Overview .....................................................................................................................................2-1
3 Technical Description ..............................................................................................................3-1
3.1 Routing of an MS to an SGSN ...................................................................................................... 3-1
3.2 SGSN Selection Based on Load Balancing Algorithm .................................................................. 3-2
3.3 Load Adjustment in an SGSN Pool ............................................................................................... 3-2
4 Parameters .................................................................................................................................4-1
5 Counters ......................................................................................................................................5-1
6 Glossary ......................................................................................................................................6-1
7 Reference Documents .............................................................................................................7-1
Huawei Proprietary and Confidential

Issue 01 (2010-06-30) ii
Copyright © Huawei Technologies Co., Ltd.
GSM BSS
SGSN Pool 1 Introduction
1 Introduction
1.1 Scope
This document describes routing of an MS to an SGSN, SGSN selection based on load balancing
algorithm, and load adjustment in an SGSN Pool in the SGSN Pool feature.
This section describes the feature GBFD-119701 SGSN Pool.
1.2 Intended Audience

It is assumed that users of this document are familiar with GPRS basics and have a working knowledge
of GPRS telecommunication.
This document is intended for:
 Personnel working on Huawei GPRS products or systems
 System operators who need a general understanding of this feature
1.3 Change History

The change history provides information on the changes in different document versions.
There are two types of changes, which are defined as follows:
 Feature change
Feature change refers to the change in the SGSN pool feature of a specific product version.
 Editorial change
Editorial change refers to the change in wording or the addition of the information that was not
described in the earlier version.
Document Issues
The document issues are as follows:
 01 (2010-06-30)
 Draft (2010-03-30)
01 (2010-06-30)
This is the first release of GBSS12.0.
Compared with issue Draft (2010-03-30) of GBSS12.0, issue 01 (2010-06-30) of GBSS12.0 incorporates
the changes described in the following table.
Change Type Change Description Parameter Change

Feature change None. None.
Editorial change Parameters are presented in the form of None.

Parameter ID instead of Parameter Name.

Issue 01 (2010-06-30) 1-1
GSM BSS
SGSN Pool 1 Introduction
Draft (2010-03-30)
This is the draft release of GBSS12.0.

Issue 01 (2010-06-30) 1-2
GSM BSS
SGSN Pool 2 Overview
2 Overview
SGSN Pool, also known as Gb Flex, enables multiple SGSNs to form a SGSN pool. A BSC belonging to
an SGSN pool area is connected to all SGSNs in the related SGSN pool. The resources and load are
shared by all the SGSNs in the pool, thus balancing the traffic load and reducing inter-SGSN handovers.
According to 3GPP 23.236-630, the functions of SGSN Pool are as follows:
 When more SGSN capacity is required, the SGSNs can be added without the replanning of the radio
network. Therefore, a lot of configuration efforts can be avoided.
 The SGSN Pool feature supports SGSN redundancy. If an SGSN in the SGSN pool is faulty, the
remaining SGSNs will keep serving the MSs located within the SGSN pool area. In a non-pooled case,
the complete SGSN service area is lost in case of an SGSN failure.
 An SGSN in the SGSN pool serves all the routing areas (RAs) in the SGSN pool area. This means that
no inter-SGSN RA update is needed, because an MS is registered in the same SGSN as long as it is
located within the SGSN pool area. This increases the QoS of GPRS for the end-user.
 The capacity dimensioning for an SGSN pool can be made according to the busy hour traffic of the
whole SGSN pool area. This is in contrast to a non-pooled case where each SGSN has to be
dimensioned according to the busy hour traffic of the area served by the specific SGSN. As the busy
hour traffic may occur at different time for different SGSNs, more SGSN capacity may be needed in
total for the non-pooled case. Therefore, SGSN Pool helps to improve network capacity and save
capital expenditure (CAPEX).
An SGSN pool is defined as a group of SGSNs serving MSs in one SGSN pool area. A BSC belonging to
an SGSN pool area is connected to all SGSNs in the related SGSN pool. As shown in Figure 2-1,
SGSN1, SGSN2, and SGSN3 form SGSN Pool1, and BSC1, BSC2, and BSC5 form SGSN Pool Area1;
whereas, SGSN4, SGSN5, and SGSN6 form SGSN Pool2, and BSC2, BSC3, and BSC6 form SGSN
Pool Area2.

Issue 01 (2010-06-30) 2-1
GSM BSS
SGSN Pool 2 Overview
Figure 2-1 SGSN Pool networking topology
SGSN Pool1 SGSN Pool2
SGSN1 SGSN2 SGSN3 SGSN4 SGSN5 SGSN6
BSC1 BSC2 BSC3 BSC4
RA11, RA12 RA21, RA22 RA31, RA32 RA41, RA42
BSC5 BSC6
RA51, RA52 RA61, RA62
SGSN Pool Area1

SGSN Pool Area2
An SGSN pool area consists of one or more RAs. All the RAs served by one BSC must belong to the
same SGSN pool area. RA21 and RA22, as shown in Figure 2-1, belong to both SGSN Pool Area1 and
SGSN Pool Area2, that is, overlapping SGSN pool areas. All the SGSNs in an SGSN pool share the
responsibility of handling all the MSs in all the RAs of the SGSN pool area. One or more SGSNs in the
pool may in addition serve BSCs outside this SGSN pool area. As shown in Figure 2-1, SGSN6 serves
RA41 and RA42 of BSC4 that are not in the SGSN pool area.
SGSN Pool is enabled when the parameter SGSNPOOLALLOW is set to Yes. If the SGSN Pool feature
is enabled at the BSC, the P-TMSI reassignment function must be enabled at the SGSN.
Each MS can be registered in any SGSN within the SGSN pool. Once an MS is registered in an SGSN,
the SGSN assigns a 4-bit packet temporary mobile subscriber identity (P-TMSI) to the MS to uniquely
identify the MS within the SGSN pool area. The network resource identifier (NRI) of the SGSN is
contained in the P-TMSI. The MS converts the P-TMSI into the temporary logical link identifier (TLLI).
When the MS accesses the network, it informs the BSC of the TLLI (containing the NRI). Then, the MS is
routed to the correct SGSN by the BSC based on the NRI contained in the TLLI. The MS is served by the
same SGSN as long as it stays within the SGSN pool area. The key technology of the SGSN Pool
feature is the SGSN selection based on the load balancing algorithm.

Issue 01 (2010-06-30) 2-2
GSM BSS
SGSN Pool 3 Technical Description
3 Technical Description
3.1 Routing of an MS to an SGSN
Routing of an MS with a TLLI Containing the network resource identifier (NRI)
Figure 3-1 shows the structure of a P-TMSI or TLLI (containing the NRI). The P-TMSI is assigned to the
MS by the SGSN.
Figure 3-1 Position of the NRI in the TLLI
31 30 29 28 27 26 25 24 23 22 ... 16 15 14 ...... 1 0
CS/PS NRI field
The NRI field in a P-TMSI or TLLI is from bit 23 to bit 14. A maximum of 1024 NRIs can be defined by
setting the NRI length to the maximum length of 10 bits. If the NRI is less than 10 bits, the most
significant bit of the NRI is always stored in bit 23. For example, if the NRI length is set to 4, a maximum
of 16 NRIs can be defined in the pool. In this case, the NRI is defined by bits 20-23 of the TLLI.
The NRI length is specified by the parameter SGSNNRILEN. One NRI corresponds to only one SGSN in
an SGSN pool; therefore, the NRIs must be set in all SGSNs and BSCs related to the SGSN pool.
 One SGSN may correspond to multiple NRIs and must be assigned at least one NRI.
 The NRI length must be the same in all SGSNs and BSCs related to an SGSN pool.
 In case of overlapping SGSN pool areas, the NRI length must be the same in all SGSNs and BSCs
related to the different SGSN pools.
The mapping relation between the NRI and CNID can be configured on the Web LMT.
If an MS accessing the network carries the TLLI containing the NRI, the BSC extracts the NRI from the
TLLI and routes the MS to an SGSN according to the mapping relation between the NRI and the SGSN.
 If the SGSN is in normal state, the BSC always routes the MS to the corresponding SGSN.
 If the SGSN is faulty, SGSNSTATUS is Prohibited, or the corresponding SGSN is unavailable, the
BSC routes the MS to a normal SGSN in the same SGSN pool based on the load balancing algorithm.
 If the null-NRI is contained in the TLLI, it indicates that the MS must be routed to another SGSN. In this
case, the BSC routes the MS to a normal SGSN in the same SGSN pool based on the load balancing
algorithm.
Routing of an MS With a TLLI Not Containing the NRI

 When an MS accesses the network for the first time, it generates a random TLLI and sends it to the
BSC. The TTLI does not contain the NRI. Then, the BSC routes the MS to an SGSN in normal state
according to the load balancing algorithm.
 When an MS belonging to one SGSN pool area accesses another SGSN pool area through the first
RA update, the BSC extracts the NRI from the TTLI. Since the NRI does not correspond to any SGSN
serving the new SGSN pool area, the BSC routes the MS to an SGSN in normal state according to the
load balancing algorithm.

Issue 01 (2010-06-30) 3-1
GSM BSS
An NRI used in one SGSN pool must not be reused in neighboring pools. For example, when an MS that
is registered in SGSN Pool Area1 of SGSN Pool1 accesses SGSN Pool Area2 of SGSN Pool2, the BSC
routes the MS to an SGSN serving SGSN Pool Area2 according to the NRI. If the NRI configuration of
the two SGSN pools is the same, the BSC routes the MS to the SGSN corresponding to the NRI in
SGSN Pool2. This may lead to overload in the SGSN and load imbalance in the SGSN Pool2.
3.2 SGSN Selection Based on Load Balancing Algorithm

SGSN Capacity
The capacity of the SGSN in each SGSN pool is specified by the parameter SGSNCAP set at the BSC.
Load Balancing Algorithm

The BSC calculates the load sharing ratio of each SGSN and the range of a random value V based on
the capacity and SGSNSTATUS of each SGSN. The value range of SGSNSTATUS is Normal, Unload,
and Prohibited. The load sharing ratio of the SGSNs in normal state is calculated.
Value V is calculated through the random number algorithm. The BSC calculates the load sharing ratio of
each SGSN in normal state according to the capacity of each SGSN. The load sharing ratio of each
SGSN indicates the proportion of the capacity of one SGSN to the capacity of all SGSNs in the pool. The
ratio is accurate to the third decimal place; therefore, the range of value V is from 0 to 999.
The BSC obtains value V through the random number algorithm and selects a serving SGSN based on
the mapping relation between value V and SGSN, to ensure the load balance in the SGSN pool.
Table 3-1 describes the mapping relation between value V and SGSN for an SGSN pool. Here, the
SGSN pool consists of SGSN1 with a capacity of 400 users, SGSN2 with a capacity of 300 users, and
SGSN3 with a capacity of 300 users.
Table 3-1 Mapping relation between value V and SGSN
Load
SGSN Capacity Sharing
SGSN ID (Number of Users) SGSN State Ratio Range of Value V
SGSN1 400 Normal 40.0% 000-399
SGSN2 300 Normal 30.0% 400-699
SGSN3 300 Normal 30.0% 700-999
For example, if value V is 404, the BSC selects SGSN2 as the serving node; if value V is 100, the BSC
selects SGSN1 as the serving node.
3.3 Load Adjustment in an SGSN Pool

Load Adjustment When an SGSN Is Added to or Removed from the SGSN Pool
When a new SGSN is added to the SGSN pool, the BSC automatically adjusts the load sharing ratio of
each SGSN. For example, SGSN4 with a capacity of 300 users is added to the SGSN pool. Compared

Issue 01 (2010-06-30) 3-2
GSM BSS
with the original mapping relation between value V and SGSN shown in Table 3-1 in 3.2 SGSN Selection
Based on Load Balancing Algorithm, the mapping relation is renewed, as shown in Table 3-2.
Table 3-2 Mapping relation between value V and SGSN when SGSN4 is added
Load
SGSN1 400 Normal 30.8% 000-307
SGSN2 300 Normal 23.1% 308-538
SGSN3 300 Normal 23.1% 539-769
SGSN4 300 Normal 23.0% 770-999
Load sharing ratio of the last SGSN = 1 - sum of load sharing ratio of each remaining SGSN
When an SGSN is removed from the SGSN pool, the BSC also automatically adjusts the load sharing
ratio of each remaining SGSN. If SGSN3 in Table 3-2 is removed from the SGSN pool, the mapping
relation between value V and SGSN is renewed, as shown in Table 3-3.
Table 3-3 Mapping relation between value V and SGSN when SGSN3 is removed
Load
SGSN1 400 Normal 40.0% 000-399
SGSN2 300 Normal 30.0% 400-699
SGSN4 300 Normal 30.0% 700-999
Load Adjustment When the SGSN Capacity Is Changed

When all the SGSNs stay in the SGSN pool and are in normal state, the BSC automatically adjusts the
load sharing ratio of each SGSN if the capacity of one or more SGSNs is changed.
If the capacity of SGSN2 in Table 3-1 in 3.2 SGSN Selection Based on Load Balancing Algorithm is
changed from 300 to 400, the mapping relation between value V and SGSN is renewed, as shown in
Table 3-4.
Table 3-4 Mapping relation between value V and SGSN when the capacity of an SGSN is changed
Load
SGSN1 400 Normal 36.4% 000-363
SGSN2 400 Normal 36.4% 364-727
SGSN3 300 Normal 27.2% 728-999

Issue 01 (2010-06-30) 3-3
GSM BSS
The range of value V is changed from 400-699 in Table 3-3 to 364-727 in Table 3-4.
Load Adjustment When an SGSN Is Faulty

When an SGSN is faulty, the BSC adjusts the load sharing ratio of each normal SGSN and routes the
MSs registered in the faulty SGSN to a normal SGSN in the pool.
If SGSN2 in Table 3-4 is faulty, the mapping relation between value V and SGSN is renewed, as shown
in Table 3-5.
Table 3-5 Mapping relation between value V and SGSN when SGSN2 is faulty
Load
SGSN1 400 Normal 57.1% 000-570
SGSN2 400 Faulty 0 --
SGSN3 300 Normal 42.9% 571-999
Load Adjustment When an SGSN Is Unloaded

If SGSNSTATUS of an SGSN in the pool is set to Unload, the BSC adjusts the load sharing ratio of each
normal SGSN and routes the MSs registered in the unloaded SGSN to a normal SGSN in the pool. For
example, if SGSN2 in the SGSN pool consisting of SGSN1, SGSN2, and SGSN3 is faulty, the MSs
registered in SGSN2 are routed to SGSN1 or SGSN3. In this case, the NRI contained in the P-TMSI is
changed. The changed NRI in the P-TMSI corresponds to SGSN1 or SGSN3; therefore, the BSC does
not route the MSs back to SGSN2 even if SGSN2 resumes to normal state. This may lead to overload in
SGSN1 or SGSN3 and imbalance in the SGSN pool. In this case, SGSNSTATUS of SGSN1 or SGSN 3
should be set to Unload.
If SGSNSTATUS of SGSN1 in Table 3-4 is set to Unload, the mapping relation between value V and
SGSN is renewed, as shown in Table 3-6.
Table 3-6 Mapping relation between value V and SGSN when SGSN1 is unloaded
Load
SGSN1 300 Unloaded 0 --
SGSN2 400 Normal 57.1% 000-570
SGSN3 300 Normal 42.9% 571-999
After SGSNSTATUS of SGSN1 is set to Unload, the MSs registered in SGSN1 are reassigned P-TMSIs.
 If an MS sends a request for the PS service, the P-TMSI is reassigned as follows:
1. Before the connection is established, SGSN1 assigns the MS P-TMSI1 in which NRI is NULL_NRI
and routing area identity (RAI) is Non-broadcast RAI.
2. The MS initiates RA update immediately on receiving the non-broadcast RAI.

Issue 01 (2010-06-30) 3-4
GSM BSS
3. The BSC extracts the null-NRI from TLLI1 and routes the MS to a normal SGSN according to the load
balancing algorithm.
4. The SGSN reassigns a P-TMSI to the MS.
 When an MS remains standby for a long time, the P-TMSI is reassigned as follows:
1. In the periodic RA update, the MS sends TLLI1 to the BSC. Then, the BSC routes the MS to SGSN1.
2. SGSN1 assigns P-TMSI2 containing the null-NRI and sends the non-broadcast RAI to the MS.
3. The MS immediately initiates RA update on receiving the non-broadcast RAI.
4. When SGSNSTATUS of SGSN1 is Unload and null-NRI is contained in TLLI2, the BSC routes the
MS to a normal SGSN according to the load balancing algorithm.
5. The SGSN reassigns a P-TMSI to the MS.
 After an MS is powered off for a long time, it immediately initiates RA update when it is powered on. In
this case, the P-TMSI is reassigned according to the status of SGSN1.
− If
SGSNSTATUS of SGSN1 is Unload, the MS is reassigned a P-TMSI. The reassignment procedure
is the same as that for an MS being standby for a long time.
− If
SGSNSTATUS of SGSN1 is Normal, SGSN1 continues to serve the MS and the MS is not
reassigned a P-TMSI.
After the load is balanced in the SGSN pool, the SGSNSTATUS of SGSN1 must be set to Normal.
Otherwise, subsequent MSs cannot be registered in SGSN1.

Issue 01 (2010-06-30) 3-5
GSM BSS
SGSN Pool 4 Parameters
4 Parameters
Table 4-1 Parameter description
Parameter ID NE MML Command Description
SGSNPOOLALLOW BSC6900 MOD Meaning: Whether to enable the SGSN

GCNOPERATOR(Optional) pool function. With SGSN pool, a
ADD BSC6900 is connected to multiple
GCNOPERATOR(Optional) SGSNs in the pool, and load balancing
and resource sharing between these
SGSNs are allowed. In this manner, the
PS services are processed by the
SGSNs in the SGSN pool in the most
efficient way. This reduces inter-MSC
handovers and node redundancy
backup.
GUI Value Range: NO(No), YES(Yes)

Actual Value Range: NO, YES
Unit: None
Default Value: NO
SGSNNRILEN BSC6900 MOD Meaning: Length of the NRI(Network
GCNOPERATOR(Optional) Resource Identifier) or NULL-NRI. The
ADD length determines the maximum value
GCNOPERATOR(Mandatory) of the NRI and NULL-NRI.
GUI Value Range: 1~10

Actual Value Range: 1~10
Unit: None
Default Value: 1
NRI BSC6900 ADD Meaning: Identifies the mapping relation
NRISGSNMAP(Mandatory) from the NRI to the SGSN uniquely with
RMV the operator name
NRISGSNMAP(Mandatory)
Unit: None
Default Value: None
CNID BSC6900 ADD Meaning: Uniquely identifies a node of
NRISGSNMAP(Mandatory) SGSN, with the specified operator
name

Unit: None
Default Value: None

Issue 01 (2010-06-30) 4-1
GSM BSS
SGSN Pool 4 Parameters
Parameter ID NE MML Command Description
CNID BSC6900 ADD NSE(Mandatory) Meaning: Uniquely identifies a node of

MOD NSE(Optional) SGSN, with the specified operator
name

Unit: None
Default Value: None
CNID BSC6900 ADD Meaning: Uniquely identifies a node of
SGSNNODE(Mandatory) SGSN, with the specified operator
MOD name
SGSNNODE(Mandatory)
RMV GUI Value Range: 0~4095
SGSNNODE(Mandatory) Actual Value Range: 0~4095
Unit: None
Default Value: None
SGSNSTATUS BSC6900 ADD SGSNNODE(Optional) Meaning: Administrative state of the

MOD SGSNNODE(Optional) SGSN. The value "ALLOW" indicates
that the SGSN can handle the PS
services normally. The value
"UNISTALL" indicates that the SGSN
does not permit new PS services to
access the network and the ongoing PS
services are not affected. The value
"DENY" indicates that the SGSN denies
all PS services.
GUI Value Range:

UNISTALL(Uninstall), ALLOW(Allow),
DENY(Deny)
Actual Value Range: UNISTALL,
ALLOW, DENY
Unit: None
Default Value: ALLOW
SGSNCAP BSC6900 ADD SGSNNODE(Optional) Meaning: Available capacity of the
MOD SGSNNODE(Optional) SGSN

Unit: None
Default Value: 1800

Issue 01 (2010-06-30) 4-2
GSM BSS
SGSN Pool 5 Counters
5 Counters
For the counters, see the BSC6900 GSM Performance Counter Reference.

Issue 01 (2010-06-30) 5-1
GSM BSS
SGSN Pool 6 Glossary
6 Glossary
For the acronyms, abbreviations, terms, and definitions, see the Glossary.

Issue 01 (2010-06-30) 6-1
GSM BSS
SGSN Pool 7 Reference Documents
7 Reference Documents
[1] 3GPP TS 23.236: "Intra-domain connection of Radio Access Network (RAN) nodes to multiple
Core Network (CN) nodes "
[2] BSC6900 Feature List
[3] BSC6900 Optional Feature Description
[4] BSC6900 GSM Parameter Reference
[5] BSC6900 GSM MML Command Reference
[6] BSC6900 GSM Performance Counter Reference

Issue 01 (2010-06-30) 7-1

SGSN Pool

Uploaded by

Copyright:

Available Formats

You might also like

SGSN Pool

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SGSN Pool

Uploaded by

Copyright:

Available Formats

SGSN Pool

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential

1.2 Intended Audience

1.3 Change History

Change Type Change Description Parameter Change

Editorial change Parameters are presented in the form of None.

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

Figure 2-1 SGSN Pool networking topology

SGSN Pool1 SGSN Pool2

SGSN1 SGSN2 SGSN3 SGSN4 SGSN5 SGSN6

BSC1 BSC2 BSC3 BSC4

RA11, RA12 RA21, RA22 RA31, RA32 RA41, RA42

RA51, RA52 RA61, RA62

SGSN Pool Area1

Huawei Proprietary and Confidential

CS/PS NRI field

Routing of an MS With a TLLI Not Containing the NRI

Huawei Proprietary and Confidential

3.2 SGSN Selection Based on Load Balancing Algorithm

Load Balancing Algorithm

3.3 Load Adjustment in an SGSN Pool

Huawei Proprietary and Confidential

Load Adjustment When the SGSN Capacity Is Changed

Huawei Proprietary and Confidential

Load Adjustment When an SGSN Is Faulty

Load Adjustment When an SGSN Is Unloaded

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

SGSNPOOLALLOW BSC6900 MOD Meaning: Whether to enable the SGSN

GUI Value Range: NO(No), YES(Yes)

GUI Value Range: 1~10

GUI Value Range: 0~4095

Huawei Proprietary and Confidential

Parameter ID NE MML Command Description

CNID BSC6900 ADD NSE(Mandatory) Meaning: Uniquely identifies a node of

GUI Value Range: 0~4095

SGSNSTATUS BSC6900 ADD SGSNNODE(Optional) Meaning: Administrative state of the

GUI Value Range:

GUI Value Range: 0~65535

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

You might also like