Guide to CSOFTX3000 V100R006 Paging Strategy Optimization

Document

No.

Product

NameCSOFTX3000

Reader CSOFTX3000Product

VersionV100R006

Author

Core Network CDMA

Product Development

Department

Document

VersionV1.0

Guide to CSOFTX3000 V100R006

Paging Strategy Optimization

Prepared by Wang Xia Date 2007-11-19

Reviewed byLu Jinghui, Wang Qinyu,

Yan TianDate 2007-11-30

Tested by Date

Accepted by Date

Huawei Technologies Co., Ltd.

All Rights Reserved.

Guide to CSOFTX3000 V100R006 Paging Strategy OptimizationFor Internal Use Only

Revision Records

DateRevised

VersionDescription Author

2007-11-19 V1.00 Completed the initial draft. Wang Xia

2007-11-30 V1.01Revised according to review

suggestions.Wang Xia

2007-05-08 Huawei Technologies Proprietary Page ii of 21


Table of Contents

Chapter 1 Forewords...................................................................................................................... 2

1.1 Background......................................................................................................................... 2

1.1.1 Introduction...............................................................................................................2

1.1.2 Scenarios..................................................................................................................3

1.1.3 Present Service State and Huawei Service Feature.................................................3

1.2 Interworking with Other Network Elements.........................................................................3

1.3 Service Restriction..............................................................................................................3

Chapter 2 Overview........................................................................................................................ 3

2.1 Introduction......................................................................................................................... 3

2.1.1 Definition................................................................................................................... 3

2.1.2 Service Interaction....................................................................................................4

2.1.3 Benefits..................................................................................................................... 5

2.1.4 Requirements for Other Network Elements..............................................................5

2.2 Service Flow........................................................................................................................ 5

2.2.1 Paging Strategy Optimization...................................................................................5

2.2.2 IsPage Optimization..................................................................................................7

2.2.3 Paging Optimization for Whole Network...................................................................8

2.3 Service Implementation.....................................................................................................13

2.3.1 Principle.................................................................................................................. 13

2.3.2 Requirements.........................................................................................................14

2.3.3 License Application.................................................................................................14

2.3.4 Software Parameter................................................................................................14

2.4 Data Configuration............................................................................................................14

2.4.1 Configuration on the CSOFTX3000 Side................................................................14

2.4.2 Data Configuration on the UMG8900 Side.............................................................15

2.4.3 Data Configuration on the HLR Side.......................................................................15

2.4.4 Data Configuration on the BSC Side......................................................................15

2.5 Service Management........................................................................................................15

2.5.1 For Operators.........................................................................................................15

2.5.2 For Mobile Subscribers...........................................................................................15

2.6 Bill and Charging...............................................................................................................16

2.6.1 Principle.................................................................................................................. 16

2.6.2 Bill Generation........................................................................................................16

2.7 Troubleshooting................................................................................................................16

2007-05-08 Huawei Technologies Proprietary Page i of 21


2007-05-08 Huawei Technologies Proprietary Page ii of 21


Keywords: paging, paging strategy, paging interval

Abstract: This document is used to guide the optimization of the paging strategy.

Abbreviations:

Abbreviations Full Spelling

IsPage InterSystemPage

2007-05-08 Huawei Technologies Proprietary Page i of 21


Chapter 1 Forewords

1.1 Background

1.1.1 Introduction

The optimization includes the following aspects:

Paging strategy optimization

In Tibet and areas in countries outside China, a set of core network equipment covers

many areas, especially in the multi-area networking. The great geography difference

of those areas requires the customized configuration of paging parameter and paging

strategy based on each area. At present, the paging parameters of CSOFTX3000 and

most paging strategies are efficient globally and they are different only in the service

flow. This impacts the success paging ratio of the switch and increases the load of

paging channel. The global paging parameters and strategies are also

disadvantageous for the network optimization according to the actual condition.

Therefore, the paging strategies need be optimized, so that different areas can use

different paging strategies.

IsPage optimization

When a subscriber locates in the boundary of two MSCs, the InterSystemPage

(IsPage) may be triggered at the same time when the first paging is triggered. The

CSOFTX3000, however, does not support the IsPage in the first paging at present.

Therefore, it is necessary to optimize the paging strategy, so as to allow the IsPage in

the first paging.

Paging optimization for whole network

After the multi-area networking is formed by migrating and integrating the original

network, the virtual MSCIDs are not distinguished in the whole network paging.

Instead, the paging message is sent to BSCs in all the MSCIDs. This is different with

that of the whole network paging before the migration and integration. At present, the

paging message can be sent to at most 10 BSCs at the same time. Therefore, the

BSC in the MSCID where the subscriber is located may be not included. The

preceding problem also exists in the multi-area networking (not formed by migrating

or integrating the original network), so the whole network paging need be optimized.

2007-05-08 Huawei Technologies Proprietary Page 2 of 21


1.1.2 Scenarios

The paging strategy optimization is applicable to all the markets, especially in the

scenario with execrable ratio resources and complex terrain. No special networking is

required.

1.1.3 Present Service State and Huawei Service Feature

None.

1.2 Interworking with Other Network Elements

An HLR is required for optimizing the whole network paging.

1.3 Service Restriction

None.

Chapter 2 Overview

2.1 Introduction

The base version of this document is CSOFTX3000 V100R006.

2.1.1 Definition

The optimization includes the following aspects:

Paging strategy optimization

In Tibet and areas in countries outside China, a set of core network equipment covers

many areas, especially in the multi-area networking. The great geography difference

of those areas requires the customized configuration of paging parameter and paging

strategy based on each area. At present, the paging parameters of CSOFTX3000 and

most paging strategies are efficient globally and they are different only in the service

flow. This impacts the success paging ratio of the switch and increases the load of

paging channel. The global paging parameters and strategies are also

disadvantageous for the network optimization based on the actual condition.



Therefore, the paging strategies need be optimized, so that different areas can use

different paging strategies.

IsPage optimization

When a subscriber locates in the boundary of two MSCs, the IsPage may be

triggered in the first paging. The CSOFTX3000, however, does not support the

IsPage in the first paging, so it is necessary to optimize the paging strategy, so as to

allow the IsPage in the first paging.

Paging optimization for entire network

After the multi-area networking is formed by migrating and integrating the original

network, the virtual MSCIDs are not distinguished in the whole network paging.

Instead, the paging message is sent to BSCs in all the MSCIDs. This is different with

that of the whole network paging before the migration and integration. At present, the

paging message can be sent to at most 10 BSCs at the same time. Therefore, the

BSC in the MSCID where the subscriber is located may be not included. The

preceding problem exists in the multi-area networking (not formed by migrating or

integrating the original network), so the whole network paging need be optimized. The

specific method is: trigger the whole network paging in a virtual MSC. If the paging

fails, trigger the whole network paging in an MSC.

2.1.2 Service Interaction

Figure 1-1 lists the interaction between the paging strategy optimization and other

services.

Figure 1-1 Interaction between the paging strategy optimization and other services

Service Interaction

Paging strategy

optimization

and extended

paging

In the extended paging, the paging strategy used is

consistent with that used before the extended paging is

triggered.

Paging strategy

optimization

and IsPage

incoming

paging

The default paging strategy is used in the IsPage incoming

paging.



Paging strategy

optimization

and early

paging

The default paging strategy is used in the early paging.

Paging strategy

optimization

and whole

network paging

The default paging strategy is used in the whole network

paging. The whole network paging in the extended paging,

however, adopts the paging strategy related to the location

area.

Paging strategy

optimization

and whole

network paging

flow

The default paging strategy is used in the flow of the whole

network paging.

IsPage

optimization

and whole

network paging

If the first paging is a whole network paging, the IsPage flow

is not triggered during the first paging.

Whole network

paging

optimization

and whole

network paging

flow

The procedure of whole network paging in a virtual MSCID is

also controlled by the whole network paging flow.

Optimization of

whole network

paging and

virtual MSCID

If the virtual MSCID function is not enabled or only an MSCID

is configured, the whole network paging in a virtual MSCID

acts as the whole network paging in an MSC.

2.1.3 Benefits

I. For Subscribers

The paging strategy optimization can improve the satisfaction of subscribers.

II. For Operators

The paging strategy optimization can improve the service quality and reduce the

network load, thus reduce the costs.



2.1.4 Requirements for Other Network Elements

An HLR is required for optimizing the whole network paging.

2.2 Service Flow

This section describes the paging strategy optimization, IsPage optimization, and

paging optimization for the whole network. Also, this section introduces the service

flow related to each optimization service.

2.2.1 Paging Strategy Optimization

By default, the Paging Strategy Table and Paging Interval Table tables have only

one record separately. And the coverage of the records is global. The paging strategy

optimization allows different location areas to use different paging strategies and

multiple records can be configured in the Paging Strategy Table and Paging

Interval Table tables. In addition, the correlation between the location area and the

paging strategy is established in Location Area Cell Table.

The paging strategy optimization is available to all the services related to the paging,

including voice terminating call, data receive, mobile terminating short message

service, SSD update, OTAPA resource allocation, LBS location service, and PRC. In

this section, the normal paging of ordinary voice terminating call is taken as an

example.

2) During the incoming trunk call, when obtaining the BSC information required by

the paging, the MSC determines the paging strategy based on information of the

current location area of the subscriber. If there is no information about the

location area, the default paging strategy is used.

3) The preceding associated paging strategy is used in the subsequent sending of

paging message and control of paging procedure.



Note:

The preceding paging strategy contains information in Paging Strategy Table and

Paging Interval Table.

The preceding default paging strategy indicates the first record in Paging

Strategy Table and Paging Interval Table. The first record in the two tables

always exists and cannot be removed.

The default paging strategy is used in the whole network paging. The whole

network paging in the extended paging, however, adopts the paging strategy

related to the location area and the strategy is consistent with that used before the

extended paging is triggered.

In the extended paging (not the whole network paging), the paging strategy used

is consistent with that used before the extended paging is triggered.

The default paging strategy is used in the IsPage incoming paging. The LAC

location information contained in the IsPage request is the LAC information of

another office, so the relation with the paging strategy of local office cannot be

established. At present, the IsPage incoming paging is available only when the

subscriber does not exist, so the default paging strategy is used in the IsPage

incoming paging.

The parameters Early paging control mode, Reply function of receiving SMS,

Paging identification (IMSI is preferred or MIN is preferred), Paging scope on

feature services, Maximum whole network paging number per second are

only valid in the default paging strategy.

2.2.2 IsPage Optimization

I. IsPaging Optimization in Early Paging



The serving MSC receives the ROUTREQ message from the HLR.

If the default paging strategy denotes that the early paging need be triggered, the serving

MSC sends the Paging Request message to the BSC.

If InterSystemPage point with early paging in the paging strategy related to the

current location area is set to 0, the IsPage is triggered in the first paging. The

InterSystemPage message is sent to the border MSC.

Note:

Whether IsPage can be triggered in the first paging depends on the location area

information and data related to the IsPage outgoing paging.

If the first paging is a whole network paging generated when the subscriber does

not exists, the subscriber is deactivated, or there is no information about the

location area, the IsPage flow is not triggered. This is because the current location

area cannot be obtained or the obtained location area information is not exact.

II. IsPage Opimization in Normal Paging

HLR Serving MSC BSC

PagingRequest

ROUTREQ

Border MSC

InterSystemPage

a

e

d

c

broutreq(Dest digits)

Incoming call

a. The serving MSC receives a ROUTREG message from the HLR.

b. The serving MSC allocates the TLDN and sends it to the HLR.

c. The call is routed into the local office.

d. The serving MSC sends a Paging Request message to the BSC.

e. If InterSystemPage point with normal paging in the paging strategy related to the current

location area is set to 0, the IsPage is triggered in the first paging. The InterSystemPage message

is sent to the border MSC.



Note:

Whether IsPage can be triggered in the first paging depends on the location area

information and data related to the IsPage outgoing paging.

If the first paging is a whole network paging generated when the subscriber does

not exists, the subscriber is deactivated, or there is no information about the

location area, the IsPage flow is not triggered. This is because the current location

area cannot be obtained or the obtained location area information is not exact.

2.2.3 Paging Optimization for Whole Network

I. Optimization for Whole Network Paging Triggered Because Subscriber

Does not Exist, Subscriber Is Deactivated, or There Is No Information About

the Location Area

Figure Description

4) The serving MSC receives the ROUTREQ message from the HLR. (The serving

MSC contains two virtual MSCs; that is, MSCID1 and MSCID2. The following

descriptions are based on this precondition if there is no special instruction.) The

information element ExtendMSCID or LAC contained in the message denotes

that the subscriber locates in the virtual MSCID1.

5) The serving MSC sends a Paging Request message to the BSC under MSCID1.

6) The serving MSC sends the Paging Request message to the BSC under

MSCID1 and BSC under MSCID2 at the same time.



Paging Optimization for Whole Network

After the serving MSC receives the ROUTREQ message, if the whole network paging

need be triggered (because the subscriber is deactivated, the subscriber is not

located in the MSC, or there is no information about the location area), proceed as

follows:

If Whole network paging of the default paging strategy in Paging Strategy

Table is set to Off, the flow is terminated.

If Whole network paging of the default paging strategy in Paging Strategy

Table is set to On, the configuration of Whole network paging scope in the

default paging strategy is judged.

If Whole network paging scope is set to Whole network paging scope

(MSCID), step b in the preceding figure is executed. That is, the serving MSC

sends the Paging Request message to the BSC under MSCID1. If the paging

fails, the flow is terminated.


(MSC), step c in the preceding figure is executed. That is, the serving MSC

sends the Paging Request message to the BSC under MSCID1 and BSC under

MSCID2 at the same time. If the paging fails, the flow is terminated.

If Whole network paging scope is set to Whole network paging scope (first

MSCID and then MSC), step b in the preceding figure is executed. That is, the

serving MSC sends the Paging Request message to the BSC under MSCID1. If

the paging fails, step c in the preceding figure is executed. That is, the serving

MSC sends the Paging Request message to the BSC under MSCID1 and BSC

under MSCID2 at the same time. If the paging fails, the flow is terminated.



Note:

At present, only the MSCID on the caller side and LAC of the callee contained in

the ROUTREQ message are descried in the protocol, while the MSCID on the

callee side is not required. Therefore, not the HLRs of all the suppliers support the

function of containing ExtendMSCID of the MSC where the callee is located in the

ROUTREQ message.

When the whole network paging is triggered, Whole network paging scope is set

to Whole network paging scope (MSCID) or Whole network paging

scope(first MSCID and then MSC), but the MSCID of the callee cannot be

obtained (for example, ExtendMSCID and LAC are not contained in the

ROUTREQ message from the HLR). To be compatible with the HLR and improve

the paging success ratio, the whole network paging in an MSC is directly

performed, regardless of the settings of Whole network paging scope.

If the ROUTREQ message from the HLR contains ExtendMSCID and LAC at the

same time, the priority of ExtendMSCID is higher than the MSCID information

obtained based on the LAC.

After the paging is responded, if the MSCID of the subscriber is inconsistent with

that before the paging, the call flow is terminated. Therefore, the whole network

paging in an MSC may be meaningless. The rule, however, remains in view of the

charging.

For the data called service and non-early-paging trunk incoming voice service, if

the whole network paging is triggered because there is no information of the

location area, the processing is consistent with the whole network paging in the

early paging procedure.

Whole network paging scope (MSCID) can be performed for at most one time.

Whole network paging scope (MSC) can be performed for at most one time. This

rule is also applied to the subsequent whole network paging.



II. Optimization for Whole Network Paging of Extended Paging Triggered Due

to Paging Failure

Figure Description

7) If the early paging or ordinary paging fails, the whole network paging of the

extended paging is triggered. (The parameter All MSC paging flag in the

adjacent location area cell tables is set to Yes.)


MSCID1.



Paging Procedure for Whole Network

If the early paging or ordinary paging fails, the whole network paging of the extended

paging is triggered. The configuration of the parameter All MSC paging flag in the

paging strategy related to the current flow is judged:



sends the Paging Request message to the BSC under MSCID1. If the paging














III. Optimization for Whole Network Paging Triggered Because There Is No

Information About the Location Area in Location Paging

Figure Description

10) The location paging triggers the whole network paging because there is no

information about the location area.


MSCID1.



Paging Procedure for Whole Network

In the location paging, if the whole network paging is triggered because there is no

information about the location area, the configuration of the parameter Whole

network paging scope in the default paging strategy will be judged:



sends the Paging Request message to the BSC under MSCID1.If the paging














Note:

The location paging is applied to the services such as SMS terminating call, SSD

update, OTAPA resource allocation, LBS location service, and PRC.

When the whole network paging is triggered, Whole network paging scope is set

to Whole network paging scope (MSCID) or Whole network paging scope

(first MSCID and then MSC), but the MSCID of the callee cannot be obtained (for

example, ExtendMSCID and LAC are not contained in the ROUTREQ message

from the HLR). To be compatible with the HLR and improve the success ratio of

short message, the whole network paging in an MSC is directly performed,

regardless of the settings of Whole network paging scope.

The whole network paging of the location paging does not judge the parameter

Whole network paging in the default paging strategy. This is based on the

consideration for the forward compatibility. For example, the support for the

existent short message broadcast service.

2.3 Service Implementation

2.3.1 Principle

Multiple records can be configured in Paging Strategy Table and Paging Interval

Table. (At most 256 records can be configured for each table.) In Local Area Cell

Table, different location areas can refer to different paging strategies and paging

interval information; that is, the paging strategy and paging interval information can be

specific to each location area.

In Paging Strategy Table, InterSystemPage point with early paging is set to 0;

that is, the IsPage can be triggered in the first paging when the early paging function

is enabled.



In Paging Strategy Table, InterSystemPage point with normal paging is set to 0;

that is, the IsPage can be triggered in the first paging in a common paging event.

In Paging Strategy Table, define the scope of whole network paging. The values

contain Whole network paging scope (MSCID), Whole network paging scope

(MSC), and Whole network paging scope (first MSCID and then MSC); that is, the

scope of whole network paging is fractionalized based on the MSCID.

2.3.2 Requirements

None.

2.3.3 License Application

No License is required for the paging strategy optimization.

2.3.4 Software Parameter

No software parameter need be set for the paging strategy optimization.

2.4 Data Configuration

2.4.1 Configuration on the CSOFTX3000 Side

To optimize the paging strategy, configure the following tables at the CSOFTX3000

side:

I. Configuring the Data Tables

Paging Strategy Table: Run ADD PAGINGSTRA to add the paging strategy

information.

Paging Interval Table: Run ADD PAGEINTVL to add the paging interval

information.

Location Area Cell Table: Run ADD LAICGI or MOD LAICGI to refer to the

paging strategy information.

II. Configuration Examples

Adding the paging strategy information.

- Paging strategy name: outskirt

- Early paging: Use the early paging

- Paging optimization: Use the paging optimization function



- Whole network paging: On

- Whole network paging scope: first MSCID and then MSC

- Reply function of receiving SMS: Need wait the reply

- Location paging: Location paging

- Paging scope on feature services: Send paging by using LAC

- Paging identification: IMSI is preferred

- InterSystemPage point: 0

- Maximum whole network paging number per second: 50

ADD PAGINGSTRA: PGSTRANM="outskirt", EP=TRUE, PO=TRUE,

WNPO=VPMSCWP, WNP=ON, RFRSM=TRUE, LP=TRUE, PSFS=LAC,

PID=IMSI, IP=0, WNPT=50;

Adding the paging interval information.

- Paging interval name: outskirt

- Paging interval T1 (Second): 5



- Remain paging interval (Second): 3

ADD PAGEINTVL: PGINTVLNM="outskirt", PIT1=5, PIT2=4, PIT3=4, RPI=3;

Quoting the preceding new paging strategy.

- LAI/CGI: 460030001

- Virtual MSCe node name: LOCAL

- Paging strategy name: outskirt

- Paging interval name: outskirt

MOD LAICGI: CGI="460030001", MMN="LOCAL", PGSTRANM="outskirt",

PGINTVLNM="outskirt";

2.4.2 Data Configuration on the UMG8900 Side

No data configuration is required on the UMG8900 side.

2.4.3 Data Configuration on the HLR Side

No data configuration is required on the HLR side.

2.4.4 Data Configuration on the BSC Side

No data configuration is required on the BSC side.



2.5 Service Management

2.5.1 For Operators

Not involved.

2.5.2 For Mobile Subscribers

Not involved.

2.6 Bill and Charging

2.6.1 Principle

Not involved.

2.6.2 Bill Generation

Not involved.

2.7 Troubleshooting

None.


Documents

Guide to CSOFTX3000 V100R006 Paging Strategy Optimization