18
Feature 1682: Paging Enhance- ment DN0560794 Issue 5-0-1

Paging Enhancement

Embed Size (px)

DESCRIPTION

Paging Enhancement

Citation preview

Page 1: Paging Enhancement

Feature 1682: Paging Enhance-

ment

DN0560794

Issue 5-0-1

Page 2: Paging Enhancement

2 DN0560794Issue 5-0-1

Feature 1682: Paging Enhancement

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia Siemens Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Siemens Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation.

The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given "as is" and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTA-TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-RECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2010/12/14. All rights reserved

f Important Notice on Product Safety Elevated voltages are inevitably present at specific points in this electrical equipment. Some of the parts may also have elevated operating temperatures.

Non-observance of these conditions and the safety instructions can result in personal injury or in property damage.

Therefore, only trained and qualified personnel may install and maintain the system.

The system complies with the standard EN 60950 / IEC 60950. All equipment connected has to comply with the applicable safety standards.

The same text in German:

Wichtiger Hinweis zur Produktsicherheit

In elektrischen Anlagen stehen zwangsläufig bestimmte Teile der Geräte unter Span-nung. Einige Teile können auch eine hohe Betriebstemperatur aufweisen.

Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Körperverlet-zungen und Sachschäden führen.

Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die Anlagen installiert und wartet.

Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene Geräte müssen die zutreffenden Sicherheitsbestimmungen erfüllen.

Page 3: Paging Enhancement

DN0560794Issue 5-0-1

3

Feature 1682: Paging Enhancement

Id:0900d805807cc448

Table of ContentsThis document has 18 pages.

1 Feature description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.2 Benefits for the operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.3 Requirements for using the feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.3.1 Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.3.2 Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.3.3 Products. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.4 Functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.4.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.4.1.1 Location information retrieval before repaging with IMSI. . . . . . . . . . . . . 61.4.1.2 Hypo-LAC paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.4.1.3 Prevention of paging on certain areas . . . . . . . . . . . . . . . . . . . . . . . . . . 121.4.1.4 Selective paging based on call type . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.4.1.5 Intelligent Selective Paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.4.2 Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.4.3 Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.4.4 Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151.4.5 Charging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151.5 Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151.6 Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151.7 Related and interworking features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161.8 Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161.9 Operator interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161.9.1 MMLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161.9.2 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171.10 Subscriber interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171.11 External interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2 Main changes in Feature 1682: Paging Enhancement . . . . . . . . . . . . . 182.1 Changes in the feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182.2 Changes in the document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Page 4: Paging Enhancement

4 DN0560794Issue 5-0-1

Feature 1682: Paging Enhancement

Id:0900d805807cc448

List of FiguresFigure 1 Information flow in paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Figure 2 Hypo-LAC paging compared to LAC paging. . . . . . . . . . . . . . . . . . . . . . . 9Figure 3 Use case 1- Deactive hypo-LAC paging and deactive enhanced hypo-LAC

paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Figure 4 Use case 2- Active hypo-LAC paging and deactive enhanced hypo-LAC

paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Figure 5 Use case 3- Deactive hypo-LAC paging and active enhanced hypo-LAC

paging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Figure 6 Use case 4- Active hypo-LAC paging and active enhanced hypo-LAC pag-

ing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Page 5: Paging Enhancement

DN0560794Issue 5-0-1

5

Feature 1682: Paging Enhancement Feature description

Id:0900d805807cc446

1 Feature description

1.1 IntroductionFeature 1682: Paging Enhancement introduces improvements to the paging procedure. The enhancement functionalities are optional and can be configured with the respective FIFILE/PRFILE parameters after the activation of the respective sales items.

The Location information retrieval before repaging with IMSI functionality improves the VLR level paging retry procedure as it enables the retrieval of the recent location area information before the repetition of the paging request.

The paging retry mechanism consists of two levels. On the one hand, the Visitor Location Register (VLR) requests the paging first with the Temporary Mobile Subscriber Identity (TMSI) and when there is no response, it can request the paging with the sub-scriber's International Mobile Subscriber Identity (IMSI). On the other hand, the Mobile Services Switching Centre (MSC) can repeat the paging over the A/Iu interface several times with the actual TMSI or IMSI content.

This feature enhances the VLR level paging retry. When the first paging with the TMSI fails as no response comes from the mobile station, the VLR retrieves the recent location area information from the database if the paging retry with IMSI is allowed, and sends a new paging request to the MSC with the updated location area information.

With the additional location information query, you can avoid the situation when the paging fails as the subscriber has already moved to a different location area in the same MSC/VLR.

With the Hypo-LAC paging functionality, 2G subscribers are first paged from the BSC under which they are recently located. The functionality is also supported in 3G: this is further referred to as Enhanced hypo-LAC paging functionality.

The Prevention of paging on certain area functionality allows the blocking mobile termi-nating calls and short messages in certain areas, such as metro stations. This increases security as it eliminates the possibility of activating explosives with the help of mobile phones. Blocking of calls and short messages is based on Location Area (LA).

With the Selective paging based on call type functionality, paging can be customized based on the call type.

The Intelligent Selective Paging (ISP) functionality is an enhancement of the 2G Hypo-LAC paging functionality. With ISP, paging is carried out in the neighboring cells which are located under the same BSC.

1.2 Benefits for the operatorThe Location information retrieval before repaging with IMSI functionality improves the VLR level paging retry procedure as it enables the retrieval of the recent location area information before the repetition of the paging request. With this additional location infor-mation query, you can avoid the situation when the paging fails as the subscriber has already moved to a different location area in the same MSC/VLR. Thus, you can increase the paging success rate.

With using the 2G Hypo-LAC paging and the 2G/3G equivalent Enhanced hypo-LAC paging functionalities which are effective, for example, during a festival event when the amount of traffic is high, a mobile subscriber is paged first from the BSC/RNC under

Page 6: Paging Enhancement

6 DN0560794Issue 5-0-1

Feature 1682: Paging Enhancement

Id:0900d805807cc446

Feature description

which the mobile subscriber has recently been located. The solutions provide optimized paging solution for respectively 2G and 3G networks, thus reducing the paging load for the BSCs/RNCs.

The Prevention of paging on certain area functionality increases security as it eliminates the possibility of activating explosives in certain areas with the help of mobile phones, as blocking of calls and short messages is based on LA.

The Selective paging based on call type functionality, that is the configuration of the number of repaging attempts based on call type, and the timer value setting for repaging attempts based on the call type, provides flexible paging scenarios and decreases paging load.

The Intelligent selective paging functionality offers similar benefits to those of hypo-LAC paging: paging is scoped to cells under the same BSC. The functionality is especially beneficial in lower mobility location areas.

The paging enhancements optimize the MSC/VLR paging parameters to increase the paging success rate. In general, it also decreases radio network overload. For more information on the overload mechanism, see Overload and Congestion Control (MSCi and MSC Server), Functional Description.

1.3 Requirements for using the feature

1.3.1 SoftwareThis feature has no special requirements for software.

This is a licensed functionality. A license needs to be purchased before using it.

1.3.2 HardwareThis feature has no special requirements for hardware.

1.3.3 ProductsThis feature functions in the Nokia Siemens Networks DX MSC, Compact DX MSC, MSC Server, and standalone MSS. The functionality is the same.

1.4 Functionality

1.4.1 General

1.4.1.1 Location information retrieval before repaging with IMSIThis feature enables you to retrieve the recent Location Area (LA) information before the paging request is repeated with the subscriber's IMSI. Thus, you can avoid the situation when the paging fails as the subscriber has already moved to another location area within the same MSC/VLR.

Figure Information flow in paging presents the information flow during paging.

Page 7: Paging Enhancement

DN0560794Issue 5-0-1

7

Feature 1682: Paging Enhancement Feature description

Id:0900d805807cc446

Figure 1 Information flow in paging

Information flow in paging is as following:

1. The paging request arrives from the Visited MSC (VMSC). The functionality is appli-cable for any mobile-terminated transactions, for example, calls, Short Message Service (SMS), Unstructured Supplementary Service Data (USSD), location ser-vices, and so on. The paging request first goes to the VLR as the location of the sub-scriber is stored there.

2. The VLR retrieves the actual location of the subscriber together with other relevant subscriber data from the database.

3. After retrieving the actual Location Area Identity (LAI), the VLR forwards the paging request to the A/Iu interface handler process of the VMSC. It performs the actual paging over the Base Station System Management Application Part (BSSMAP) or Radio Access Network Application Part (RANAP) protocol. The first paging request goes with the subscriber's TMSI.

4. The A/Iu interface process can resend the paging request. You can configure how many times you want it to be repeated. This can take couple of seconds based on the configuration, however, it is enough for the subscriber to accomplish a location update to a new area.

5. If there is no response from the mobile station, the VMSC-AIF sends a negative acknowledgement to the VLR.

Page 8: Paging Enhancement

8 DN0560794Issue 5-0-1

Feature 1682: Paging Enhancement

Id:0900d805807cc446

Feature description

6. The Paging Enhancement feature enables the VLR to retrieve again the subscriber data and location information from the database. This is performed only if the paging repetition with IMSI is allowed in the VLR parameters.

7. The VLR sends a new paging request to the AIF. In this case, the used identity is the subscriber's IMSI, and the paging is requested in the new location area.

8. The MSC sends the paging request to the radio network. You can configure how many times you want it to be repeated.

9. If the subscriber accepts the paging request, it sends the initial layer 3 message to the MSC.

10. The MSC forwards the access request to the VLR.11. The VLR performs the usual security procedures, for example, authentication,

security mode set-up, IMEI checking.12. After successful security checkings, the VLR acknowledges the access request

towards the mobile station.13. At the same time, the VLR answers the paging request to the VMSC.

If the second location retrieval is unsuccessful since, for example, the subscriber has already moved to a different VLR, the paging process stops and the call is cleared.

1.4.1.2 Hypo-LAC pagingThe Hypo-LAC paging functionality is supported in both 2G and 3G networks. The func-tionality can be activated for only 2G support. It can be also activated for 2G/3G net-works.

g 2G/3G support of the Hypo-LAC paging functionality is further referred to as Enhanced hypo-LAC paging functionality.

A Mobile Subscriber (MS) can be paged first from the BSC/RNC under which they have been recently located. This so-called hypo-LA is the minimum paging area. This paging method is correspondingly called hypo-LAC paging. If the hypo-LAC paging fails, a normal LAC paging is used. Hypo-LAC paging is very effective during, for example, a festival event when the amount of traffic is high.

Figure Hypo-LAC paging compared to LAC paging shows the difference between the hypo-LAC paging and the normal LAC paging.

Page 9: Paging Enhancement

DN0560794Issue 5-0-1

9

Feature 1682: Paging Enhancement Feature description

Id:0900d805807cc446

Figure 2 Hypo-LAC paging compared to LAC paging

The MSC/VLR finds out the recent BSC/RNC based on the Location Area Identity (LAI) and Cell Identity (CI) information of a paged MS, and starts paging with the TMSI only in this BSC/RNC. This hypo-LAC paging is repeated based on LA-specific parameters .

If the hypo-LAC paging with TMSI fails and the TMSI PAGE REPETITION VLR-specific parameter is set to USED, the MSC/VLR continues with a normal LAC paging with IMSI. This LAC paging is repeated based on LA-specific parameters .

The Enhanced hypo-LAC paging functionality allows the paging to be flexible: depend-ing on the activation status, paging can be versatile.

Use cases for 2G/3G common LACsUse case 1- Deactive hypo-LAC paging and deactive enhanced hypo-LAC pagingTMSI paging is sent to all the BSCs and all the RNCs of the LAC.

IMSI paging is sent to all the BSCs and all the RNCs of the LAC.

Page 10: Paging Enhancement

10 DN0560794Issue 5-0-1

Feature 1682: Paging Enhancement

Id:0900d805807cc446

Feature description

Figure 3 Use case 1- Deactive hypo-LAC paging and deactive enhanced hypo-LAC paging

Use case 2- Active hypo-LAC paging and deactive enhanced hypo-LAC pagingTMSI paging is sent to the most recently paged BSC (which is stored in the VLR data-base) and to all the RNCs of the LAC.

IMSI paging is executed in all the BSCs and all the RNCs of the LAC.

Figure 4 Use case 2- Active hypo-LAC paging and deactive enhanced hypo-LAC paging

Page 11: Paging Enhancement

DN0560794Issue 5-0-1

11

Feature 1682: Paging Enhancement Feature description

Id:0900d805807cc446

Use case 3- Deactive hypo-LAC paging and active enhanced hypo-LAC pagingTMSI paging is sent to all the BSCs and to the most recently paged RNC of the LAC (which is stored in the VLR database).

IMSI paging is sent to all the BSCs and all the RNCs of the LAC.

Figure 5 Use case 3- Deactive hypo-LAC paging and active enhanced hypo-LAC paging

Use case 4- Active hypo-LAC paging and active enhanced hypo-LAC pagingTMSI paging is sent to the most recently paged BSC or to the most recently paged RNC.(which is stored in the VLR database).

IMSI paging is sent to all the BSCs and all the RNCs of the LAC.

Page 12: Paging Enhancement

12 DN0560794Issue 5-0-1

Feature 1682: Paging Enhancement

Id:0900d805807cc446

Feature description

Figure 6 Use case 4- Active hypo-LAC paging and active enhanced hypo-LAC paging

g The network configurations described in the use cases are not the recommended configurations by Nokia Siemens Networks.

1.4.1.3 Prevention of paging on certain areasWith this functionality, it is also possible to block mobile terminating calls and short messages in certain areas, for example, metro stations. This functionality increases security as, for example, it eliminates the possibility of activating explosives with the help of mobile stations. Blocking of calls and short messages is based on LA.

1.4.1.4 Selective paging based on call typeWith this functionality, it is possible to configure the number of repaging attempts and separate timer values (T1-T3) for repaging attempts as per the call type, for example, the call scenario.

The parameters can be configured for the following call scenarios:

• PSI (Provide Subscriber Information) • FSM (Forward SM) • PRN (Provide Roaming Number)

g PRN is the default setting.

1.4.1.5 Intelligent Selective PagingIntelligent Selective Paging (ISP) is an enhancement of the Hypo-LAC paging function-ality. Upon receiving the paging request, paging is carried out in the neighboring cells which are located under the same BSC.

The paging message towards the BSC includes:

Page 13: Paging Enhancement

DN0560794Issue 5-0-1

13

Feature 1682: Paging Enhancement Feature description

Id:0900d805807cc446

• Location area code (LAC) • Cell identifier (CI)

If intelligent selective paging is activated, the primary paging is performed in the coverage area of the recent cell. If this primary intelligent selective paging is not suc-cessful, that is, there is no response from the mobile station, the paging is continued as hypo-LAC paging: the LAC based (TMSI) repaging attempts are carried out as per the logic of the Hypo-LAC paging functionality.

g To allow intelligent selective paging, hypo-LAC paging must also be activated.

Every repaging attempt uses an expanding paging area. For example, with three repaging attempts, the paging scope is the following:

0. TMSI+Recent CI (ISP)

1. TMSI+Recent BSC (Hypo-LAC)

2. TMSI+Recent BSC (Hypo-LAC)

3. TMSI+Recent BSC (Hypo-LAC)

If TMSI paging fails and the TMSI PAGE REPETITION VLR-specific parameter is set to USED, the MSC/VLR attempts a standard LAC paging with IMSI.

1.4.2 FilesThere are no files directly visible to the operator.

1.4.3 ParametersThe following FIFILE parameters are related to this feature:

GET_LAI_BEF_PAGING_REP (002:1100)This FIFILE parameter controls the optionality of the Location information retrieval before repaging with IMSI functionality. The operator can activate or deactivate the func-tionality with the WOS and WOA MML commands.

The possible values are:

• ACTIVEThe optional feature is in use and active.

• DEACTIVEThe optional feature is in use but not active.

HYPO_LAC_USAGE (002:1191)This FIFILE parameter controls the optionality of the Hypo-LAC paging functionality. The operator can activate or deactivate the functionality with the WOS and WOA MML com-mands.

The possible values are:

ACTIVE The optional feature is in use and active.

DEACTIVE The optional feature is in use but not active.

DEDICATED_RNC_PAGING (002:1740)This FIFILE parameter controls the optionality of the Enhanced hypo-LAC paging func-tionality.

Page 14: Paging Enhancement

14 DN0560794Issue 5-0-1

Feature 1682: Paging Enhancement

Id:0900d805807cc446

Feature description

The possible values are:

ON The optional feature is in use and active.

OFF The optional feaure is in use but not active.

SELECTIVE_PAGING (002:1405)This FIFILE parameter controls the optionality of LAC-based selective paging parame-ters which allow or restrict TMSI repaging attempts. The number of repaging attempts and separate timer values for repaging attempts based on the call type are the configu-rable parameters.

The possible values are:

ACTIVE The optional feature is in use and active.

DEACTIVE The optional feature is in use but not active.

LAC_SMS_TMSI_REPA_RESTR (002:1406)This PRFILE parameter controls if TMSI repaging is restricted in the SMS call scenario.

The possible values are:

TRUE TMSI repaging is restricted in the SMS call scenario.

FALSE TMSI repaging is allowed in the SMS call scenario.

g This parameter is in use if FIFILE parameter SELECTIVE_PAGING is active.

LAC_PSI_TMSI_REPA_RESTR (002:1407)This PRFILE parameter controls if TMSI repaging is restricted in the Provide_Subscriber _Information (PSI) call scenario.

The possible values are:

TRUE TMSI repaging is restricted in the PSI call scenario.

FALSE TMSI repaging is allowed in the PSI call scenario.

g This parameter is in use if FIFILE parameter SELECTIVE_PAGING is active.

LAC_PRN_TMSI_REPA_RESTR (002:1408)This PRFILE parameter controls if TMSI repaging is restricted in Provide_Roaming_Number (PRN) call scenario.

The possible values are:

TRUE TMSI repaging is restricted in the PRN call scenario.

FALSE TMSI repaging is allowed in the PRN call scenario.

g This parameter is in use if FIFILE parameter SELECTIVE_PAGING is active.

INTELLIG_SELEC_PAGING (002:1474)This PRFILE parameter controls the optionality of the Intelligent selective paging func-tionality. It defines whether the intelligent selective paging is activated for a location area. The intelligent selective paging requires that the hypo-LAC paging is also acti-vated.

The possible values are:

ON The Intelligent Selective Paging function is in use and active.

OFF The Intelligent Selective Paging function is in use but not active.

Page 15: Paging Enhancement

DN0560794Issue 5-0-1

15

Feature 1682: Paging Enhancement Feature description

Id:0900d805807cc446

1.4.4 StatisticsThis functionality affects the ASCII reports.

Hypo-LAC paging attempts are reported like normal LAC paging attempts. In case of a faulty hypo-LAC paging it can give a slightly faulty information if a normal LAC paging with IMSI is not executed. Otherwise, there is no impact on the reports.

1.4.5 ChargingThis feature has no effects on charging.

1.5 CapacityThis feature has no effects on capacity.

1.6 RestrictionsLocation information retrieval before repaging with IMSIWhen the mobile subscriber has moved to a different MSC/VLR, the retrieval of location area information fails and the paging request is not repeated.

Hypo-LAC pagingThe Hypo-LAC paging functionality can be activated respectively for 2G or 2G/3G support.

Hypo-LAC paging functionality (2G)

The hypo-LAC paging is valid only in the BSCs, that is, in 2G side. There can be unnec-essary hypo-LAC paging attempts when a MS has moved from one hypo-LA to another hypo-LA inside the same LA, because location updating is not made in this case. The normal LAC paging with TMSI is not executed when the hypo-LAC paging is defined for this LAC.

Enhanced hypo-LAC paging functionality (2G/3G)

The functionality is not used with IMSI paging.

In case of common a 2G and 3G LAC deployed to the network, the MSS/VLR is not able to detect the radio access changes because the location update (LU) is carried out only when the LAC changes. The deployment of the common 2G and 3G LAC is not the rec-ommended configuration by Nokia Siemens Networks.

Prevention of paging on certain areasThere are no restrictions related to this functionality of the feature.

Selective paging based on call typeThe VLR controls repaging preventation for TMSI based on the call scenario. So the VLR can restrict repaging for TMSI according to the call scenario but not for IMSI.

Intelligent Selective PagingWith intelligent selective paging, hypo-LAC paging has to be active for the LAC before ISP can be activated.

Similarly to hypo-LAC paging, intelligent selective only uses TMSI.

Page 16: Paging Enhancement

16 DN0560794Issue 5-0-1

Feature 1682: Paging Enhancement

Id:0900d805807cc446

Feature description

The Intelligent selective paging functionality is only supported in 2G.

1.7 Related and interworking featuresThis feature has no related or interworking features.

1.8 ComplianceThis feature is fully compliant with the 3GPP technical specifications.

1.9 Operator interfaces

1.9.1 MMLs

VLR and PLMN Parameter Handling, MX Command GroupYou can use the commands of the MX command group to display and modify VLR-specific and PLMN-specific parameters. The purpose of these commands is to define the settings of the VLR and PLMN operations.

The following commands are relevant to this feature:

• MXM - MODIFY VLR PARAMETERSWith this command, you can modify the VLR-specific paging repetition parameters.

• MXO - OUTPUT VLR PARAMETERSWith this command, you can display the current values of the VLR-specific paging repetition parameters.

For more information, see VLR and PLMN Parameter Handling, MX Command Group.

Parameter Handling, WO Command GroupYou can use the commands of the WO command group to modify and output the param-eter values in the General Parameter File (PRFILE) and to activate or deactivate, and output the optional feature parameters in the Feature Information Control File (FIFILE).

The following command is relevant to this feature:

• WOA - ACTIVATE/DEACTIVATE OPTIONAL FEATUREUsing the WOA command of this command group you can activate and deactivate this functionality setting the HYPO_LAC_USAGE parameter.

For more information, see Parameter Handling, WO Command Group.

Location Area Handling, EL Command GroupYou can use the commands of the EL command group to define location areas where hypo-LAC paging is to be used with the HYPO-LAC PAGING parameter and to define the location areas where 3G paging is to be optimized. Call type based configuration of the number of repaging attempts and separate timer values for repaging attempts is set with this command group). The possible values of this parameter are OFF and ON. The default value is OFF. The PAGING PREVENTION parameter is added to this command group. This parameter turns off short messages and mobile terminating calls with ON/OFF values.

The parameters are included in the following commands.

Page 17: Paging Enhancement

DN0560794Issue 5-0-1

17

Feature 1682: Paging Enhancement Feature description

Id:0900d805807cc446

• ELC - CREATE LOCATION AREAThe parameters are visible in the output of this MML command.

• ELE - MODIFY LOCATION AREA PARAMETERS <OPTION>The parameters are modified by using this MML command.

• ELO - OUTPUT LOCATION AREA DATAThe parameter are visible in the output of this MML command.

• ELP - MODIFY REPAGING ATTEMPTSRepaging attemps and separate timer values for repaging attempts according to call type are configurable with this command.

For more information, see Location Area Handling, EL Command Group.

License and Feature Handling, W7 Command GroupYou can use the commands of the W7 command group to license and feature handling functions in the DX 200 and IPA2800-based network elements.

The following command is relevant to this feature:

• W7M - MODIFY FEATURE STATEUsing the W7M command of this command group you activate or inactivate a feature, or set the feature into a state in which it can be configured.

For more information, see License and Feature Handling, W7 Command Group.

1.9.2 AlarmsThere are no alarms related to this feature.

1.10 Subscriber interfacesThis feature has no subscriber interfaces.

1.11 External interfacesThis feature has no effects on the external interface of the MSC/HLRs.

Page 18: Paging Enhancement

18 DN0560794Issue 5-0-1

Feature 1682: Paging Enhancement

Id:0900d805807cc447

Main changes in Feature 1682: Paging Enhancement

2 Main changes in Feature 1682: Paging Enhancement

2.1 Changes in the featureThis feature is implemented in M13.4 with the following changes to on top of M12.

The Hypo-LAC paging functionality has been introduced. Difference between the hypo-LAC paging and the normal LAC paging has been modified. The Prevention of paging on certain areas functionality has been introduced.

The Selective paging based on call type functionality is an optional functionality intro-duced in M14.1.

The Enhanced hypo-LAC paging functionality has been introduced in M14.4 Top.

The Intelligent Selective Paging functionality has been introduced in M14.5 Top.

2.2 Changes in the documentChanges made between issues 5-0-1 and 5-0-0The document has been restructured and revised regarding the Hypo-LAC paging func-tionality.

Changes made between issues 5-0-0 and 4-0-0Sections Benefits for the operator, Functionality, Restrictions and Operator interfaces have been updated to incorporate information on the Selective paging based on call type and Intelligent Selective Paging functionalities.

Changes made between issues 4-0-0 and 3-0Sections Introduction, Benefits for the operator, Functionality, Restrictions and Operator interfaces have been updated to incorporate information on the Enhanced hypo-LAC paging functionality.

Changes made between issues 3-0 and 2-2The company and product names have been changed according to the official Nokia Siemens Networks portfolio naming.