Call Delay Optimization

R1.0

Call Delay Optimization

Internal Use Only

LEGAL INFORMATION
By accepting this certain document of ZTE CORPORATION you agree to the following terms. If you do not agree to the following terms, please notice that you are not allowed to use this document. Copyright 2014 ZTE CORPORATION. Any rights not expressly granted herein are reserved. This document contains proprietary information of ZTE CORPORATION. Any reproduction, transfer, distribution, use or disclosure of this document or any portion of this document, in any form by any means, without the prior written consent of ZTE CORPORATION is prohibited. and are registered trademarks of ZTE CORPORATION. ZTEs company name, logo and product names referenced herein are either trademarks or registered trademarks of ZTE CORPORATION. Other product and company names mentioned herein may be trademarks or trade names of their respective owners. Without the prior written consent of ZTE CORPORATION or the third party owner thereof, anyones access to this document should not be construed as granting, by implication, estopped or otherwise, any license or right to use any marks appearing in the document. The design of this product complies with requirements of environmental protection and personal security. This product shall be stored, used or discarded in accordance with product manual, relevant contract or laws and regulations in relevant country (countries). This document is provided as is and as available. Information contained in this document is subject to continuous update without further notice due to improvement and update of ZTE CORPORATIONs products and technologies.

ZTE CORPORATION
Address: NO. 55 Hi-tech Road South ShenZhen P.R.China 518057 http://support.zte.com.cn [email protected]

Website: Email:

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

Call Delay Optimization

Internal Use Only

Revision History
Product Version Document Version R1.0 Serial Number Reason for Revision First published

Author
Date 2011-12-07 Document Version R1.0 Prepared by Wang Xiaohui Reviewed by Zheng Hao Approved by Wang Zhenhai

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

II

Call Delay Optimization

Internal Use Only

Intended audience:

GSM network optimization engineers

Proposal: Before reading this document, you had better have the following knowledge and skills.
SEQ 1 2 3 Null Knowledge and skills Null Reference material

Follow-up document: After reading this document, you may need the following information.
SEQ 1 2 Null Reference material Null Information

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

III

Call Delay Optimization

Internal Use Only

About This Document

Summary
Chapter 1 2 GSM Call Delay Definition GSM Call Delay Analysis Description Introduces the call delay definition. Introduces the origination and termination signaling flow related to the call delay and analyze the factors affecting the call delay. Describes the measures of call delay optimization.

3 GSM Call Delay Optimization Scheme

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

IV

Call Delay Optimization

Internal Use Only

TABLE OF CONTENTS
1 2 2.1 2.1.1 2.1.2 2.2 2.3 3 3.1 3.1.1 3.1.2 3.2 3.2.1 3.2.2 3.2.3 3.3 3.3.1 3.3.2 3.3.3 3.3.4 3.4 3.4.1 3.4.2 3.4.3 3.4.4 GSM Call Delay Definition ........................................................................... 1 GSM Call Delay Analysis ............................................................................. 1 GSM Call Flow .............................................................................................. 1 Origination Signaling Flow ............................................................................. 1 Termination Signaling Flow ............................................................................ 2 Comparison of Call Delays of Different Service Models ................................... 3 Comparison of Time Delays of All the GSM Sites............................................ 4 GSM Call Delay Optimization Scheme ........................................................ 6 Call Flow Optimization ................................................................................... 6 Simplest Call Flow ......................................................................................... 6 Influence on Delay of Optional Processes....................................................... 6 CN Assignment Flow Optimization ................................................................. 9 Early Assignment Flow .................................................................................. 9 Late Assignment Flow (The Function Against Missing Call not Being Enabled) ..................................................................................................... 11 Late Assignment Flow (The Function Against Missing Call Being Enabled) .... 13 Parameter Optimization ............................................................................... 15 Number of Paging Multi-Frames................................................................... 15 Number of Reserved AGCH Blocks .............................................................. 17 Interval Between Two Paging Times of the CN ............................................. 17 Assignment Queuing ................................................................................... 18 System Version Optimization ....................................................................... 18 Optimization of Immediate Assignment Flow................................................. 18 Optimization of Connection Flow at the Abis Interface ................................... 19 BSC Packing Delay Optimization ................................................................. 21 BTS Packing Delay Optimization .................................................................. 22

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

Call Delay Optimization

Internal Use Only

FIGURES
Figure 1-1 The Signaling Flow Related to Call Delay .........................................................1 Figure 2-1 Figure 2-3 Origination Signaling Flow ................................................................................1 Call Delays of Different Termination Objects .....................................................4 Figure 2-2 Termination Signaling Flow ..............................................................................2 Figure 3-1 Paging Responding Time ............................................................................... 15 Figure 3-2 Paging Success Rate ..................................................................................... 16 Figure 3-3 Paging Success Rate Min Value Per Day ....................................................... 16 Figure 3-4 Flow of Two-Paging Mechanism ..................................................................... 17 Figure 3-5 Flow of Assignment Queuing .......................................................................... 18 Figure 3-6 Immediate Assignment Flow Before Optimization ............................................ 18 Figure 3-7 Immediate Assignment Flow After Optimization............................................... 19 The Figure 3-8 Figure 3-9 Connection Flow at the Abis Interface Before Optimization ....................... 19 Connection Flow at the Abis Interface After Optimization ................................. 20

Figure 3-10 BSC Packing Principle ................................................................................. 21

TABLES
Table 2-1 Table 3-1 Table 3-2 Table 3-3 Table 3-4 Table 3-5 Table 3-6 Table 3-7 Table 3-8 Table 3-9 Table 3-10 Table 3-11 Table 3-12 Table 3-13 Intervals Between Signaling Points of Call Delay ................................................4 Simplest Origination Flow ..................................................................................6 Simplest Termination Flow ................................................................................6 Delay of Authentication Flow (1 s)......................................................................7 Delay of IMEI Query flow (0.7 s) ........................................................................7 Delay of Encryption Flow (0.7 s) ........................................................................7 Delay of Classmark Query Flow (0 s) .................................................................8 Influence on the Call Delay of Different Flows ....................................................8 Call Delays of These Assignment Flows ............................................................9 Early Assignment Flow ......................................................................................9 Late Assignment Flow (The Function Against Missing Call not Being Enabled) 11 Late Assignment Flow (The Function Against Missing Call Being Enabled) ..... 13 Test Effects Comparison ............................................................................... 21 Call Delay Test Comparision Result ............................................................... 22

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

VI

Call Delay Optimization

Internal Use Only

GSM Call Delay Definition

Call delay is used to evaluate the time from the call initiation to alerting. It is one of the KPIs reflecting the users perception. On the signaling point, the statistics of process from the originating MS sending the CHANNEL REQUEST message to receiving the ALERTING message is made, as shown in the following figure (the red arrow).

Figure 1-1 The Signaling Flow Related to Call Delay

The call delay relates to the origination and termination signaling flow, equipment type, assignment mode of the CN, and test method. The analysis and comparison of the factors affecting the call delay are demonstrated in the following contents.

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

Call Delay Optimization

Internal Use Only

2
2.1
2.1.1

GSM Call Delay Analysis

GSM Call Flow
Origination Signaling Flow
In the origination flow, the process from sending the CHANNEL REQUEST message to receiving the ALERTING message is relevant to the call delay. This process includes the origination SD assignment, classmark query, authentication, encryption, IMEI query, call establishment, and TCH channel assignment. During these processes, the four processes of classmark query, authentication, encryption, and IMEI query are optional.

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

Call Delay Optimization

Internal Use Only

Figure 2-1 Origination Signaling Flow

MS
CHANNEL REQ

BTS
CHANNEL RQD CHANNEL ACT CHANNEL ACT ACK IMM ASSIGNMENT CMD SABM UA

BSC

MSC

EST IND(CM SERVICE REQ)

CR CC

AUTHENTICATION REQUEST AUTHENTICATION RESPONSE CIPHER MODE CMD CIPHER MODE CMP IDENTITY REQUEST IDENTITY RESPONSE CLASSMARK REQUEST CLASSMARK UPDATE CM SERVICE ACCEPTED SETUP CALL PROCEEDING CHANNEL ACT CHANNEL ACT ACK ASSIGNMENT CMD SABM UA ASSIGNMENT CMP ASSIGNMENT CMP ALERTING CONNECT CONNECT ACK TALKING DISCONNECT RELEASE RELEASE CMP CHANNEL REL DISC UA DEACTIVE SACCH RELEASE INDICATION RF CHANNEL REL RF CHANNEL REL ACK CLEAR CMP RLSD RLSD CMP CLEAR CMD EST IND ASSIGNMENT REQ CIPHER MODE CMD

2.1.2

Termination Signaling Flow

After the origination SETUP message is received by the CN, the CN starts the termination paging. After the termination alerting, the MS receives the Alerting message. Therefore, the termination flow should be considered.

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

Call Delay Optimization

Internal Use Only

In the termination flow, the process from paging message to alerting is relevant to the call delay. This process includes the origination SD assignment, classmark query, authentication, encryption, IMEI query, call establishment, and TCH channel assignment. During these processes, the four processes of classmark query, authentication, encryption, and IMEI query are optional.

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

Call Delay Optimization

Internal Use Only

Figure 2-2 Termination Signaling Flow

MS
PAGING REQ CHANNEL REQ

BTS
PAGING CMD

BSC
PAGING

MSC

CHANNEL RQD CHANNEL ACT CHANNEL ACT ACK

IMM ASSIGNMENT CMD SABM UA EST IND(PAGING RESPONSE) CR CC AUTHENTICATION REQUEST AUTHENTICATION RESPONSE CIPHER MODE CMD CIPHER MODE CMP IDENTITY REQUEST IDENTITY RESPONSE CLASSMARK REQUEST CLASSMARK UPDATE CM SERVICE ACCEPTED SETUP CALL CONFIRMED CHANNEL ACT CHANNEL ACT ACK ASSIGNMENT CMD SABM UA ASSIGNMENT CMP ASSIGNMENT CMP ALERTING CONNECT CONNECT ACK TALKING DISCONNECT RELEASE RELEASE CMP CHANNEL REL DISC UA DEACTIVE SACCH RELEASE INDICATION RF CHANNEL REL RF CHANNEL REL ACK CLEAR CMP RLSD RLSD CMP CLEAR CMD EST IND ASSIGNMENT REQ CIPHER MODE CMD

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

Call Delay Optimization

Internal Use Only

2.2

Comparison of Call Delays of Different Service Models

In the actual test, because the handing methods for different termination objects of the CN are different, the call delays of different termination objects are different. In the following figure, the delays of mobile phone calling mobile phone, mobile phone calling the fixed-line telephone, and mobile phone calling the virtual number are described.

Figure 2-3 Call Delays of Different Termination Objects

2.3

Comparison of Time Delays of All the GSM Sites

The equipment in the existing network has the following three kinds of configuration. ZTE CN + iBSC + BTS V3 ZTE CN + BSC + BTS V3

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

Call Delay Optimization

Internal Use Only

ZTE CN + iBSC + SDR

The engineers make the dialing test in three kinds of configuration respectively and the intervals between the signaling points of call delay are shown in the following table.

Table 2-1

Intervals Between Signaling Points of Call Delay iBSC + SDR iBSC + B8018 BSC + B8018 0.0031 0.0235 0.0016 0.2966 0.0501 0.1845 0.4686 0.575 0.0438 2.9736 0.0232 0 0.4299 0.2046 0.2967 5.5748 0 0.66 0.0046 0.0363 0.0078 0.278 0.0891 0.1732 0.4862 0.0609 0.6155 0.1313 0.0546 0.0157 0.3188

CHANNEL REQUIRED CHANNEL ACTIVATION CHAN ACTIV ACK IASS EIND CIPH MODE CMD CLASSM CHANGE CIPH MODE COMP SETUP CALL PROCEED CHANNEL ACTIVATION CHAN ACTIV ACK ASSIGNMENT CMD EIND ASSIGN COMPL ALERTING Average time of the originating call PAGING CMD CHANNEL REQUIRED CHANNEL ACTIVATION CHAN ACTIV ACK IMME ASSIGN PAGE RESPONSE CIPH MODE CMD CLASSM CHANGE CIPH MODE COMP SETUP CALL CONFIRMED CHANNEL ACTIVATION CHAN ACTIV ACK ASSIGNMENT CMD EIND IMME ASSIGN 0.000 0.024 0.000 0.262 0.024 0.193 0.488 0.471 0.025 3.317 0.026 0.000 0.571 0.104 0.313 5.818 0.000 1.238 0.001 0.026 0.000 0.288 0.030 0.204 0.470 0.031 0.678 0.139 0.023 0.001 0.620 0.000 0.109 0.000 0.340 0.051 0.184 0.471 0.473 0.042 3.986 0.116 0.000 0.380 0.099 0.172 6.423 0.101 1.429 0.001 0.105 0.000 0.370 0.048 0.187 0.466 0.050 0.896 0.236 0.095 0.000 0.428

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

Call Delay Optimization

Internal Use Only

iBSC + SDR ASSIGN COMPL ALERTING Average time of terminating call 0.163 0.179 4.091

iBSC + B8018 0.088 0.101 4.500

BSC + B8018 0.1936 0.3173 3.4429

The main differences of the three kinds of configuration are described as follows. Delay between the channel activation and activation response The delays of the B8018s in the SDR and BSC are similar and the delay of the B8018 in the iBSC is long. Paging responding time The paging response time of the B8010 in the BSC is the shortest and the paging response time of the B8018s in the SDR and iBSC is long. The causes of the differences are listed as follows. The signaling interaction delay of the B8018 in the iBSC is long, which is caused by the CMB forwarding the signaling. Because of using the IP mode, the signaling transmission is fast in the SDR. Because the signaling is transferred between the BSC and FUC and it is not forwarded by the CMB, the signaling transmission is fast in the BSC. Because the B8018 adopts the central paging mode in the iBSC and the signaling is forwarded by the CMB, the paging responding time is quite long. The SDR also adopts the central paging and the signaling is forwarded by CC. Before of the advantage of the IP transmission method, the paging responding time in the SDR is shorter than that of the B8018 in the iBSC.

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

Call Delay Optimization

Internal Use Only

3
3.1
3.1.1

GSM Call Delay Optimization Scheme

Call Flow Optimization
Simplest Call Flow
The call flow optimization means to delete the optional flows (Classmark query, authentication, encryption, and IMEI query) in the call initiation process. The simplest flow is shown as follows.

Table 3-1 Time 09:10.3 09:10.4 09:10.6 09:10.8 09:11.1 09:11.1 09:12.0 09:14.6 09:14.7 09:15.3

Simplest Origination Flow Direction UL UL DL UL DL UL DL DL UL DL Protocol MM RR RR RR MM CC CC RR RR CC Message The CM SERVICE REQUEST message The CHANNEL REQUEST message The IMMEDIATE ASSIGNMENT message The CLASSMARK CHANGE message The CM SERVICE ACCEPT message The SETUP message The CALL PROCEEDING message The ASSIGNMENT COMMAND message The ASSIGNMENT COMPLETE message The ALERTING message

Table 3-2 Time 09:12.2 09:12.8 09:13.0 09:13.0

Simplest Termination Flow Direction DL UL DL UL Protocol RR RR RR RR Message The PAGING REQUEST TYPE 1 message The CHANNEL REQUEST message The IMMEDIATE ASSIGNMENT message The PAGING RESPONSE message

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

Call Delay Optimization

Internal Use Only

Time 09:13.3 09:13.7 09:13.7 09:14.7 09:14.8 09:15.0

Direction UL DL UL DL UL UL

Protocol RR CC CC RR RR CC

Message The CLASSMARK CHANGE message The SETUP message The CALL CONFIRMED message The ASSIGNMENT COMMAND message The ASSIGNMENT COMPLETE message The ALERTING message

3.1.2

Influence on Delay of Optional Processes

The optional processes, including Classmark query, authentication, encryption, and IMEI query, are controlled at the CN. The delays of these processes in the CN statistics are accurate, as shown in the following tables.

Table 3-3 Time 14:53:10 14:53:11 14:55:23 14:55:24 14:57:35 14:57:36 14:59:48 14:59:49 15:02:00 15:02:01

Delay of Authentication Flow (1 s) Tracing Entity Type BSSAP BSSAP BSSAP BSSAP BSSAP BSSAP BSSAP BSSAP BSSAP BSSAP Message The AUTHENTICATION REQUEST message The AUTHENTICATION RESPONSE message The AUTHENTICATION REQUEST message The AUTHENTICATION RESPONSE message The AUTHENTICATION REQUEST message The AUTHENTICATION RESPONSE message The AUTHENTICATION REQUEST message The AUTHENTICATION RESPONSE message The AUTHENTICATION REQUEST message The AUTHENTICATION RESPONSE message Delay

00:01.0

00:01.0

00:01.0

00:01.0

00:01.0

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

10

Call Delay Optimization

Internal Use Only

Table 3-4 Time 09:46.4 09:47.2 09:49.9 09:50.6 10:25.2 10:26.0 11:00.7 11:01.3 13:18.6 13:19.3

Delay of IMEI Query flow (0.7 s) Tracing Entity Type BSSAP BSSAP BSSAP BSSAP BSSAP BSSAP BSSAP BSSAP BSSAP BSSAP Message The IDENTITY REQUEST message The IDENTITY RESPONSE message The IDENTITY REQUEST message The IDENTITY RESPONSE message The IDENTITY REQUEST message The IDENTITY RESPONSE message The IDENTITY REQUEST message The IDENTITY RESPONSE message The IDENTITY REQUEST message The IDENTITY RESPONSE message Delay

00:00.7

00:00.7

00:00.7

00:00.7

00:00.7

Table 3-5
Time

Delay of Encryption Flow (0.7 s)

Tracing Entity Type Message Delay

15:29.2 15:30.0 16:08.8 16:09.5 16:24.6 16:25.3 16:38.5 16:39.2 17:40.2 17:40.9

BSSAP BSSAP BSSAP BSSAP BSSAP BSSAP BSSAP BSSAP BSSAP BSSAP

The CIPHER MODE COMMAND message The CIPHER MODE COMPLETE message The CIPHER MODE COMMAND message The CIPHER MODE COMPLETE message The CIPHER MODE COMMAND message The CIPHER MODE COMPLETE message The CIPHER MODE COMMAND message The CIPHER MODE COMPLETE message The CIPHER MODE COMMAND message The CIPHER MODE

00:00.7

00:00.7

00:00.7

00:00.7

00:00.7

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

11

Call Delay Optimization

Internal Use Only

Time

Tracing Entity Type

Message

Delay

COMPLETE message Classmark query can be made at the same with authentication and IMEI query and its delay is quite short, 0 s.

Table 3-6

Delay of Classmark Query Flow (0 s)

Tracing Entity Type Message Delay

Time

14:53:10 14:53:10 14:53:15 14:53:15 14:55:23 14:55:23 14:55:27 14:55:27 14:57:40 14:57:40

BSSAP BSSAP BSSAP BSSAP BSSAP BSSAP BSSAP BSSAP BSSAP BSSAP

The CLASSMARK REQUEST message The CLASSMARK UPDATE message The CLASSMARK REQUEST message The CLASSMARK UPDATE message The CLASSMARK REQUEST message The CLASSMARK UPDATE message The CLASSMARK REQUEST message The CLASSMARK UPDATE message The CLASSMARK REQUEST message The CLASSMARK UPDATE message

00:00.0

00:00.0

00:00.0

00:00.0

00:00.0

Judging from the above comparison, the influence on the call delay of different flows is demonstrated in the following table.

Table 3-7 Flow

Influence on the Call Delay of Different Flows Corresponding Signaling Point Authentication Request -> Authentication Response Cipher Mode Command -> Cipher Mode Complete Identity Request -> Identity Response Classmark Enquiry -> Classmark Change 1.0 0.7 0.7 0.0 Delay (s)

Authentication Encryption IMEI query Classmark query

Judging from the above table, the authentication, encryption, and IMEI query flows affect the delay greatly. The specific value differs because of different equipment and

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

12

Call Delay Optimization

Internal Use Only

environments. The delays in the above table are the single-flow delays. If the flow is included in both the origination and termination, the affected delay will be two times of the affected delay of single flow. The IMEI query flow can be set to be periodical in the CN. This flow is not made for each call and it needs the support from the CN.

3.2

CN Assignment Flow Optimization

There are three kinds of common assignment flows: early assignment flow, late assignment flow (the function against missing call not being enabled), and late assignment flow (the function against missing call being enabled). The call delays of these assignment flows are shown in the following table.

Table 3-8

Call Delays of These Assignment Flows Early Assignment Flow 14:53:12 14:53:16 0:00:04 Late Assignment Flow (The Function Against Missing Call not Being Enabled) 16:09:13 16:09:17 0:00:04 Late Assignment Flow (The Function Against Missing Call Being Enabled) 23:49:15 23:49:20 0:00:05

Signaling point Setup Alerting Delay

The differences of the CN flows mainly lay between the setup and alerting. Therefore, the delays of different assignment flows of this process are compared. The delay of late assignment flow (the function against missing call being enabled) is 1 s longer than that of early assignment and late assignment (the function against missing call not being enabled).Therefore, from the aspect of delay reduction, it is suggested that the early assignment flow or late assignment flow (the function against missing call not being enabled) should be adopted.

3.2.1

Early Assignment Flow

The early assignment flow means that the originating call is assigned after the terminating paging is delivered. Compared with the late assignment flow (the function against missing call being enabled), the delay of early assignment flow is 1 s shorter.

Table 3-9 Time 14:53: 10 14:53: 10 14:53: 10

Early Assignment Flow Direction >TRC_MI_ FROM_A <TRC_MI_ TO_A <TRC_MI_ TO_A Message The CM_SERVICE_REQUEST message The CLASSMARK_REQUEST message The AUTHENTICATION_REQUES Remarks Receiving the first message from the radio side

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

13

Call Delay Optimization

Internal Use Only

Time 14:53: 10 14:53: 10 14:53: 11 14:53: 11 14:53: 12 14:53: 12 14:53: 12 14:53: 12 14:53: 12 14:53: 13 14:53: 13 14:53: 13 14:53: 12 14:53: 13 14:53: 12 14:53: 12 14:53: 12 14:53:

Direction >TRC_MI_ FROM_A >TRC_MI_ FROM_A >TRC_MI_ FROM_A <TRC_MI_ TO_A >TRC_MI_ FROM_A <TRC_MI_ TO_A <TRC_MI_ TO_C_D_ F <TRC_MI_ TO_C_D_ F <TRC_MI_ TO_C_D_ F >TRC_MI_ FROM_C_ D_F <TRC_MI_ TO_C_D_ F <TRC_MI_ TO_C_D_ F <TRC_MI_ TO_H248 >TRC_MI_ FROM_H2 48 >TRC_MI_ FROM_C_ D_F >TRC_MI_ FROM_C_ D_F >TRC_MI_ FROM_C_ D_F <TRC_MI_

Message T message The CLASSMARK_UPDATE message The CLASSMARK_UPDATE message The AUTHENTICATION_RESPON SE message The CM_SERVICE_ACCEPT message The SETUP message The CALL_PROCEEDING message The MAP_OPEN_REQ message The MAP_SEND_ROUTING_ INFORMATION_REQ message The MAP_DELIMITER_REQ message The MAP_PROVIDE_ROAMING_ NUMBER_IND message The MAP_PROVIDE_ROAMING_ NUMBER_RSP message The MAP_CLOSE_REQ message The ADD_REQ message The ADD_REPLY message The MAP_OPEN_CNF message The MAP_SEND_ROUTING_ INFORMATION_CNF message The MAP_CLOSE_IND message The Paging message

Remarks

Starting the internal flow

Terminating paging

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

14

Call Delay Optimization

Internal Use Only

Time 13 14:53: 12 14:53: 13 14:53: 15 14:53: 15 14:53: 15 14:53: 15 14:53: 16 14:53: 16 14:53: 15 14:53: 16 14:53: 15 14:53: 17 14:53: 17 14:53: 17 14:53: 16

Direction TO_A <TRC_MI_ TO_A >TRC_MI_ FROM_A >TRC_MI_ FROM_A <TRC_MI_ TO_A <TRC_MI_ TO_A >TRC_MI_ FROM_A >TRC_MI_ FROM_A >TRC_MI_ FROM_A <TRC_MI_ TO_H248 <TRC_MI_ TO_A >TRC_MI_ FROM_H2 48 <TRC_MI_ TO_H248 >TRC_MI_ FROM_A >TRC_MI_ FROM_A <TRC_MI_ TO_A

Message The ASSIGNMENT_REQUEST message The ASSIGNMENT_COMPLETE message The PAGING_RESPONSE message The CLASSMARK_REQUEST message The SETUP message The CLASSMARK_UPDATE message The CLASSMARK_UPDATE message The CALL_CONFIRMED message The ADD_REQ message The ASSIGNMENT_REQUEST message The ADD_REPLY message The ADD_REQ message The ASSIGNMENT_COMPLETE message The ALERT message The ALERT message

Remarks

Assigning the originating call after the terminating paging The assignment of originating call is completed.

Assigning the terminating call

The assignment of terminating call is completed.

Originating call alerting

3.2.2

Late Assignment Flow (The Function Against Missing Call not Being Enabled)
The late assignment flow adopted for the CN of ZTE is described as follows. In the TCH assignment stage, the origination and termination are made at almost at the same time. Compared with the late assignment flow (the function against missing call being enabled), the delay of the late assignment flow (the function against missing call not being enabled) is 1 s shorter.

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

15

Call Delay Optimization

Internal Use Only

Table 3-10 Late Assignment Flow (The Function Against Missing Call not Being Enabled) Time 16:09:12.1 7 16:09:12.1 8 16:09:12.1 8 16:09:12.4 1 16:09:13.1 1 16:09:13.1 2 16:09:13.1 2 16:09:13.1 2 16:09:13.1 2 16:09:13.3 0 16:09:13.3 0 16:09:13.3 0 16:09:13.3 0 16:09:13.3 0 16:09:13.4 3 16:09:13.4 3 16:09:13.4 3 16:09:13.4 3 16:09:13.4 3 16:09:14.6 Entity Type BSSAP Message The CM SERVICE REQUEST message The COMMON ID message The CM SERVICE ACCEPT message The CLASSMARK UPDATE message The SETUP message The MAP OPEN REQUEST message The CALL PROCEEDING message The SEND ROUTING INFO REQUEST message The MAP DELIMITER REQUEST message The MAP OPEN INDICATION message The MAP OPEN RESPONSE message The PROVIDE ROAM NUMBER REQUEST message The PROVIDE ROAM NUMBER RESPONSE message The MAP CLOSE REQUEST message The MAP OPEN CONFIRM message The SEND ROUTING INFO RESPONSE message The PAGING message The PAGING message The PAGING message The PAGE RESPONSE Directio n Receive Remarks Receiving the first message from the radio side

BSSAP BSSAP BSSAP BSSAP MSCMA P BSSAP MSCMA P MSCMA P VLRMAP VLRMAP VLRMAP

Send Send Receive Receive Send Send Send Send Receive Send Receive Starting the internal flow

VLRMAP VLRMAP MSCMA P MSCMA P BSSAP BSSAP BSSAP BSSAP

Send Send Receive Receive Send Send Send Receive Terminating paging

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

16

Call Delay Optimization

Internal Use Only

Time 6 16:09:14.6 7 16:09:14.6 7 16:09:14.9 0 16:09:15.6 0 16:09:15.6 1 16:09:15.6 7 16:09:15.6 7 16:09:15.6 8 16:09:15.7 2 16:09:15.7 2 16:09:16.3 0 16:09:16.4 4 16:09:16.5 6 16:09:16.5 6 16:09:16.6 2 16:09:16.6 2

Entity Type message BSSAP BSSAP BSSAP BSSAP H248 H248 BSSAP H248 H248 BSSAP BSSAP

Message

Directio n

Remarks

The COMMON ID message The SETUP message The CLASSMARK UPDATE message The CALL CONFIRMED message The EVT_H248S_ADD_REQ message The EVT_H248S_ADD_RPL message The ASSIGNMENT REQUEST message The EVT_H248S_ADD_REQ message The EVT_H248S_ADD_RPL message The ASSIGNMENT REQUEST message The ASSIGNMENT COMPLETE message The ASSIGNMENT COMPLETE message The ALERTING message The EVT_H248S_MODIFY_REQ message The EVT_H248S_MOD_RPL message The ALERTING message

Send Send Receive Receive Send Receive Send Send Receive Send Receive Assigning the originating call The assignment of terminating call is completed. The assignment of originating call is completed. Assigning the terminating call

BSSAP BSSAP H248 H248 BSSAP

Receive Receive Send Receive Send

Originating call alerting

3.2.3

Late Assignment Flow (The Function Against Missing Call Being Enabled)
The late assignment flow (the function against missing call being enabled) means that the terminating call is assigned after the originating call is successfully assigned. Compared with the late assignment flow with the function against missing call not being enabled, the delay of this late assignment flow is 1 s longer.

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

17

Call Delay Optimization

Internal Use Only

Table 3-11 Time 23:49:14.1 7 23:49:14.1 8 23:49:14.1 8 23:49:14.4 1 23:49:15.1 1 23:49:15.1 2 23:49:15.1 2 23:49:15.1 2 23:49:15.1 2 23:49:15.5 4 23:49:15.5 4 23:49:15.5 5 23:49:15.5 6 23:49:15.5 8 23:49:15.5 8 23:49:15.5 8 23:49:15.5 8 23:49:15.8 3 23:49:15.8 3 23:49:15.8 3

Late Assignment Flow (The Function Against Missing Call Being Enabled) Entity Type BSSAP Message The CM SERVICE REQUEST message The COMMON ID message The CM SERVICE ACCEPT message The CLASSMARK UPDATE message The SETUP message The CAP OPEN REQUEST message The CALL PROCEEDING message The CAP INITIAL DP message The CAP DELIMITER REQUEST message The CAP OPEN CONFIRM message The CAP REQUEST REPORT BCSM EVENT message The CAP APPLY CHARGING message The CAP FURNISH CHARGING INFORMATION message The CAP CONTINUE message The MAP OPEN REQUEST message The SEND ROUTING INFO REQUEST message The MAP DELIMITER REQUEST message The MAP OPEN INDICATION message The MAP OPEN RESPONSE message The PROVIDE ROAM NUMBER REQUEST Directio n Receive Remarks Receiving the first message from the radio side

BSSAP BSSAP BSSAP BSSAP GSMSS F BSSAP GSMSS F GSMSS F GSMSS F GSMSS F GSMSS F GSMSS F GSMSS F MSCMA P MSCMA P MSCMA P VLRMAP VLRMAP VLRMAP

Send Send Receive Receive Send Send Send Send Receive Receive Receive Receive Receive Send Send Send Receive Send Receive Starting the internal flow

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

18

Call Delay Optimization

Internal Use Only

Time

Entity Type message

Message

Directio n

Remarks

23:49:15.8 3 23:49:15.8 3 23:49:16.0 0 23:49:16.0 0 23:49:16.0 2 23:49:16.0 2 23:49:16.0 2 23:49:17.3 8 23:49:17.3 9 23:49:17.3 9 23:49:17.6 6 23:49:18.6 1 23:49:18.6 3 23:49:18.7 0 23:49:18.7 1 23:49:18.8 0 23:49:18.8 0 23:49:19.4 9 23:49:19.4 9 23:49:20.1 7 23:49:20.3

VLRMAP VLRMAP MSCMA P MSCMA P BSSAP BSSAP BSSAP BSSAP BSSAP BSSAP BSSAP BSSAP H248 H248 H248 H248 BSSAP BSSAP BSSAP BSSAP BSSAP

The PROVIDE ROAM NUMBER RESPONSE message The MAP CLOSE REQUEST message The MAP OPEN CONFIRM message The SEND ROUTING INFO RESPONSE message The PAGING message The PAGING message The PAGING message The PAGE RESPONSE message The COMMON ID message The SETUP message The CLASSMARK UPDATE message The CALL CONFIRMED message The EVT_H248S_ADD_REQ message The EVT_H248S_ADD_RPL message The EVT_H248S_ADD_REQ message The EVT_H248S_ADD_RPL message The ASSIGNMENT REQUEST message The ASSIGNMENT COMPLETE message The ASSIGNMENT REQUEST message The ASSIGNMENT COMPLETE message The ALERTING message

Send Send Receive Receive Send Send Send Receive Send Send Receive Receive Send Receive Send Receive Send Receive Send Receive Receive Assigning the originating call The assignment of originating call is completed. Assigning the terminating call The assignment of terminating call is completed. Terminating paging

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

19

Call Delay Optimization

Internal Use Only

Time 1 23:49:20.3 2 23:49:20.3 9 23:49:20.3 9

Entity Type

Message

Directio n

Remarks

H248 H248 BSSAP

The EVT_H248S_MODIFY_REQ message The EVT_H248S_MOD_RPL message The ALERTING message

Send Receive Send Originating call alerting

3.3
3.3.1

Parameter Optimization
Number of Paging Multi-Frames
According to the GSM protocol, each mobile user (corresponding to each IMSI) belongs to one paging group. In each cell, every group corresponds to one sub paging channel. The MS calculates the paging group that it belongs to according to the IMSI and then calculates the location of the sub-paging channel of this paging group. In the actual network, the MS only 'listens" to the sub-paging channel that it belongs to and ignores the contents of other sub-paging channels. The number of the multi-frames of the paging channel means how many multi-frames are considered to be one loop of the sub-paging channel. Because the number of multi-frames is larger, the interval between the sub-paging channels is large. That is to say, the time from the paging being delivered by the CN to the MS receiving the paging is quite long. Therefore, the call delay can be reduced if the engineers set the number of paging multi-frames properly. The following figure shows one comparison test made in the experimental environment. Judging from this figure, the paging responding time differs. Generally speaking, the larger the number of the paging multi-frames is, the longer the paging responding time is.

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

20

Call Delay Optimization

Internal Use Only

Figure 3-1 Paging Responding Time

The default number of multi-frames of the network is 5. In some fields, such as the fields of Ericsson, the number is set to 2.Judging from the field test result, after the number of multi-frames is changed from 5 to 2, the average call time can be 0.6 s shorter. In the condition of the maximum CS paging traffic being 150000 each day, after the number of paging multi-frames is changed from 5 to 2, the paging success rate keeps stable.

Figure 3-2 Paging Success Rate

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

21

Call Delay Optimization

Internal Use Only

Figure 3-3 Paging Success Rate Min Value Per Day

Paging Success Rate Min value per day

96.00%
94.00% 92.00% 90.00% 88.00% 86.00% 84.00% 82.00% 80.00% 78.00%

3.3.2

Number of Reserved AGCH Blocks

Number of reserved AGCH blocks means the blocks used for the AGCH in 51 multi-frames. After the CCCH structure is fixed, this parameter is actually used to allocate proportions occupied by the AGCH and PCH on the CCCH. The engineers can balance the AGCH and PCH bearing conditions through adjusting this parameter. Usually, the engineers can reduce the value of this parameter to shorten the paging responding time of the MS, with the prerequisite of no overloading on the AGCH. Right now, the preemption mechanism is adopted for the BTS. The messages needing to be delivered on the AGCH will preempt the PCH and be delivered. Therefore, it is suggested to set the number of the reserved AG blocks to be 0.

3.3.3

Interval Between Two Paging Times of the CN

The two paging mechanism is adopted for the CN. If the paging response is not received after N s of the first paging being delivered, the second paging will be delivered. The flow is shown in the following figure.

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

22

Call Delay Optimization

Internal Use Only

Figure 3-4 Flow of Two-Paging Mechanism

MS
PAGING REQ

BTS
PAGING CMD

BSC
PAGING

MSC

No Paging Response
PAGING PAGING CMD PAGING REQ

In the test, sometimes, the response appears after the second paging. Then one paging interval is added to the delay and the whole call delay is affected. Therefore, it is necessary to check whether the interval between the two paging times is reasonable. Usually, it is required that the interval should be longer than the maximum access attempting time at the radio side and it should be no longer than 6 s.

3.3.4

Assignment Queuing
During the cell congestion, if the function of allowing the assignment queuing is enabled, the MS will perform the queuing and wait for the TCH resource allocation. The flow is shown in the following figure.

Figure 3-5 Flow of Assignment Queuing

MS

BTS

BSC

MSC

ASSIGNMENT REQ

No radio resource, queuing

CHANNEL ACT CHANNEL ACT ACK ASSIGNMENT CMD SABM UA ASSIGNMENT CMP EST IND

ASSIGNMENT CMP

The waiting time of queuing is about 0 ~ 5 s. After the queuing is completed successfully, the call duration is much longer. Therefore, if the call that is abnormally long appears, it is necessary to check whether the assignment queuing exists in the assignment

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

23

Call Delay Optimization

Internal Use Only

measurement. If the queuing exists, it is suggested to increase the radio resources through capacity expansion and HR activating, so as to reduce the chance of queuing during the call.

3.4
3.4.1

System Version Optimization

Optimization of Immediate Assignment Flow
In the immediate assignment flow, the immediate assignment message can be sent at the time of sending the channel activation message to the BTS. For the immediate assignment process, the connection process at the Abis interface is unnecessary. The flow before the optimization is shown in the following figure.

Figure 3-6 Immediate Assignment Flow Before Optimization

Immediate Assignment Flow at the Abis Interface

MS
Channel Required

BTS
Channel Request Channel Activation

BSC

MSC

100ms
Imm Assign SABM UA Establish Indication Channel Active Ack Imm Assign

280ms

The flow after the optimization is shown in the following figure.

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

24

Call Delay Optimization

Internal Use Only

Figure 3-7 Immediate Assignment Flow After Optimization

Immediate Assignment Optimization Flow at the Abis Interface

MS BTS
Channel Required Channel Request Channel Activation Imm Assign Channel Active Ack SABM UA Establish Indication

BSC

MSC

Imm Assign

100ms 280ms

Judging from the above figure, if the assignment process at the Abis interface is to be optimized, make the optimization at the same time of the channel activation. Then the call delay will be 100 ms shorter. The above analysis is based on the condition of the Abis interface being the E1 transmission. If the Abis interface is IP transmission, the delay will not be compressed, because the message interaction process at the Abis interface is quite short in the IP mode (20 ms for a round). For the satellite site, the delay is much shorter and the SD assignment success rate can be enhanced. In iBSCV6.20.200fp10 and later versions, this function is realized. In iBSCV6.20.61, the OMC system control parameters can be modified directly.

3.4.2

Optimization of Connection Flow at the Abis Interface

For the BTS of iBSC + E1, it is necessary to make the Abis connection before the TCH activation.

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

25

Call Delay Optimization

Internal Use Only

The Figure 3-8

Connection Flow at the Abis Interface Before Optimization

Connection Flow at the Abis Interface

MS BTS BSC MSC

CMM Connection Command CMM Connection Response Channel Activation Channel Active Ack Assign Cmd

Assignment Request 90ms

100ms Assign Cmd SABM UA

320ms Establish Indication

Because the packing delay of the LAPD is quite long, the delay of the message exchange at the Abis interface is long. The interaction of one message needs the time longer than 70 ms. What is more, the connection at the Abis interface is not closely related to the channel activation, so it is unnecessary to make the two operations in a serial mode. What is more, the Abis connection is always successful. From the aspect of delay reduction, the two operations can be made at the same time. The delay at the Abis interface after the change is shown in the following figure.

Figure 3-9 Connection Flow at the Abis Interface After Optimization

Optimization of the Connection at the Abis Interface

MS BTS BSC MSC
Assignment Request CMM Connection Command Channel Activation

90ms100ms
Assign Cmd SABM UA Establish Indication CMM Connection Response Channel Active Ack Assign Cmd

320ms

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

26

Call Delay Optimization

Internal Use Only

Judging from the above figure, if the assignment process at the Abis interface is to be optimized, make the optimization at the same time of the channel activation. Then the call delay will be 90 ms shorter. The above analysis is based on the condition of the Abis interface being the E1 transmission. If the Abis interface is IP transmission, the delay will not be compressed, because the message interaction process at the Abis interface is quite short in the IP mode (One round is 20 ms at most.). In iBSCV6.20.61 and later versions, this function is realized. If the V2 BTS exists, the version later than iBSCV6.20.614cp006 is needed. In iBSCV6.20.61, the OMC system control parameters can be modified directly. The comparison of the test effects before and after the two flows of immediate assignment and connection are enabled at the same time.

Table 3-12

Test Effects Comparison After the Switch Is Turned on CM Service Request 08:00:38.500 08:04:10.700 08:07:43.735 08:11:15.783 08:14:47.643 08:18:20.731 08:21:52.871 08:25:25.658 08:28:57.818 08:32:30.686 08:36:03.678 08:39:35.638 08:43:08.738 08:46:43.711 08:50:16.761 08:53:48.693 Alerting 08:00:42.680 08:04:15.304 08:07:48.168 08:11:19.831 08:14:52.202 08:18:24.943 08:21:57.711 08:25:30.223 08:29:03.126 08:32:35.338 08:36:07.998 08:39:40.366 08:43:15.790 08:46:49.170 08:50:20.422 08:53:53.086 Delay 00:04.2 00:04.6 00:04.4 00:04.0 00:04.6 00:04.2 00:04.8 00:04.6 00:05.3 00:04.7 00:04.3 00:04.7 00:07.1 00:05.5 00:03.7 00:04.4 00:04.7

Before the Switch Is Turned on CM Service Request 09:01:21.613 09:04:55.921 09:08:27.596 09:15:39.663 09:19:12.598 09:22:45.706 09:26:17.658 09:29:50.721 09:33:23.613 09:36:56.657 09:40:30.720 09:44:03.788 09:47:35.668 09:51:07.671 09:54:40.679 09:58:13.907 Average Delay Alerting 09:01:27.392 09:04:59.968 09:08:32.620 09:15:44.714 09:19:17.526 09:22:50.030 09:26:22.597 09:29:55.529 09:33:28.428 09:37:02.812 09:40:35.771 09:44:08.099 09:47:39.827 09:51:12.423 09:54:45.834 09:58:18.709 Delay 00:05.8 00:04.0 00:05.0 00:05.1 00:04.9 00:04.3 00:04.9 00:04.8 00:04.8 00:06.2 00:05.1 00:04.3 00:04.2 00:04.8 00:05.2 00:04.8 00:04.9

Judging from the above table, the average delay is 200 ms shorter.

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

27

Call Delay Optimization

Internal Use Only

3.4.3

BSC Packing Delay Optimization

According to the communication overhead feature of the signaling transmission on the control plane of iBSC and the 20-bite payload mode of common signaling, the overhead of the IP head is large, which affects the throughput capability and capacity handling of the CMP control plane greatly. Therefore, it is necessary to pack the signaling of the Abis control plan, so as to reduce the impact of the overhead of the IP head. According to the maximum bite number (260 bites) of the LAPD frame, the packing threshold is set to be 255 bites and the packing delay is also set. The principle is shown in the following figure.

Figure 3-10 BSC Packing Principle

Message Message head Packing message Signaling or paging message Message Message body

body head Making packing before the delay

Message Head Message length

Protocol identifier

Message Message Type Length

Message Message

Packing message body

Head

body

Maximum bite number of packing: 255 Ethernet Sending the message during the delay

The O&M messages should not be packed. The signaling messages and packing messages are packed with the unit being rack. The SPB board creates independent buffer areas for different racks and the organized data packages on the CMP will be put into different buffer areas according to different targets. The paging messages are sent only to the main rack of the BTS and the main rack CMM sends the paging messages to the BCCH carriers of the racks. Because the LAPD packing will make the call delay longer, the engineers optimize the LAPD packing delay in iBSCV6.20.200fp005, so as to shorten the delay. The delay of the signaling packing is changed to 10 ms to 30 ms and the delay of the paging packing is changed to 50 ms to 30 ms. The engineers make the statistics of the traffic in the sending direction of each site for every 2 s. If the traffic is lower than 2 KB/s, the signaling and paging messages will not be packed. If the traffic is higher than 2 KB/s, the signaling and paging messages will be packed. The LAPD packing delay optimization can reduce the call delay for about 200 ms.

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

28

Call Delay Optimization

Internal Use Only

3.4.4

BTS Packing Delay Optimization

There are three kinds of LAPD UL signaling: OAM message, measurement report, and signaling message. The OAM messages are sent in the non-packing mode and have a low priority; the measurement reports and signaling messages are sent in the packing mode and the priority level of the signaling message is higher than that of the measurement report. One sending buffer queue is created for the measurement reports and signaling messages. The request data sent by the Abis interface of upper level is put in the buffer queue and the packing is made in the queue. Then the engineers use the regular scanning task to put the packing data of the buffer queue in the corresponding priority queue. The signaling message is put in the high-priority level sending queue and the measurement report message is put in the low-priority level sending queue. The packing mode is not used for the UL OAM messages and the UL OAM messages are not put in the buffer queue but are directly put in the low-level priority sending queue and sent with the measurement report messages. Some changes of the packing flow are made in the BTS version (BTSV6.20.243n), so as to shorten the call delay. The test environments include V3 8018 site, iBSC, and AMR. The call delay test comparison result is shown in the following table.

Table 3-13

Call Delay Test Comparision Result Originating Call to 10010 (ms) Originating Call to the MS (ms) 6564.03 6704.92 140.89

The LAPD packing switch being turned on The LAPD packing switch being turned off Delay at the Um interface being reduced

3434.59 3522.26 87.67

ZTE Confidential Proprietary

2014 ZTE CORPORATION. All rights reserved.

29