real time trigger feat 1433

8/14/2019 real time trigger feat 1433

http://slidepdf.com/reader/full/real-time-trigger-feat-1433 1/30

DN01170933 © Nokia Corporation 1 (30)

Issue 3-2 en Nokia Proprietary and Confidential

FEATURE 1433Terminal Management Support



FEATURE 1433 Terminal Management Support

2 (30) © Nokia Corporation DN01170933

Nokia Proprietary and Confidential Issue3-2en

The information in this documentation is subject to change without notice and describes onlythe product defined in the introduction of this documentation. This documentation is intendedfor the use of Nokia's customers only for the purposes of the agreement under which thedocumentation is submitted, and no part of it may be reproduced or transmitted in any form ormeans without the prior written permission of Nokia. The documentation has been prepared tobe used by professional and properly trained personnel, and the customer assumes fullresponsibility when using it. Nokia welcomes customer comments as part of the process ofcontinuous 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 cannot be considered bindingbut shall be defined in the agreement made between Nokia and the customer. However, Nokiahas made all reasonable efforts to ensure that the instructions contained in the documentationare adequate and free of material errors and omissions. Nokia will, if necessary, explain issueswhich may not be covered by the documentation.

Nokia's liability for any errors in the documentation is limited to the documentary correction oferrors. NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THISDOCUMENTATION OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL(INCLUDING MONETARY LOSSES), that might arise from the use of this documentation orthe information in it.

This documentation and the product it describes are considered protected by copyrightaccording to the applicable laws.

NOKIA logo is a registered trademark of Nokia Corporation.

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

Copyright © Nokia Corporation 2005. All rights reserved.





Contents

Contents 3

List of tables 4

List of figures 5

1 Introduction 7

2 Benefits for the operator 9

3 Description of the feature 113.1 Requirements for using the feature 113.1.1 Software 11

3.1.2 Hardware 113.1.3 Products 113.2 Functionality 123.2.1 General 123.2.2 Additional information 143.2.3 Files 163.2.4 Parameters 173.2.5 Statistics 183.2.6 Charging 183.3 Capacity 183.4 Restrictions 183.5 Related and interworking features 193.6 Compliance 19

4 Interfaces 214.1 Operator interfaces 214.1.1 MMLs 214.1.2 Alarms 234.2 Subscriber interfaces 234.3 External interfaces 23

5 Main changes in the feature 25

References 27

Glossary 29






List of tables

Table 1. Trigger SM parameters 13





List of figures

Figure 1. Trigger TP-User-Data field 14

Figure 2. Network elements involved in batch file sending functionality 23

Figure 3. Network elements involved in Real Time functionality 23








Introduction



1 Introduction

The configuration of the mobile equipment, for which the Nokia TerminalManagement Server (NTMS) can provide additional services, consists of twostages:

1. Identifying the mobile equipment that needs configuration update andsupports automatic configuration.

2. Sending the new settings to the mobile equipment, for example in a ShortMessage Service (SMS) or Wireless Application Protocol (WAP) Pushmessage.

This feature provides support for the first stage by gathering and sending thesubscriber-mobile terminal associations to the NTMS. This enables the NTMS toselect and configure the relevant mobile stations automatically, that is, in such away that the subscriber or the operator does not have to enter the data into theequipment manually.

The MSC/VLR provides two interfaces towards the NTMS: the batch file and real

time triggers. In the batch file writing functionality, the VisitorLocation Register(VLR) collects the subscriber and terminal associations to binary files, which theNTMS can download later through File Transfer Protocol (FTP). The gatheringprocess of data takes place once a day at a configurable time. The NTMS getsinformation about the creation time by using the time stamp in the file header.

In the real time trigger functionality, as soon as the Visited Mobile servicesSwitching Centre (VMSC) detects an event, it sends a trigger to the NTMS. Thesetriggers are sent in SMS, since the NTMS has a direct connection to the ShortMessage Service Centre (SMSC).

The VMSC sends a trigger immediately in the following cases:

• when an International Mobile Equipment Identity (IMEI) change isdetected

• when a roamer arrives from a foreign country

• when a subscriber makes an inter-VLR location update and the previouslocation of the user is one of the configured LAIs






Feature 1433: Terminal Management Support supports the International MobileEquipment Identity Software Version (IMEISV) in batch file and real timetriggering.

This feature also provides pre-filtering possibilities, which decrease the amountof triggers sent to the NTMS. The filtering criteria include the following:

• Roaming status or IMSI range

They can be used to send information to the NTSM only about roaming orhome subscribers, or if this granularity is not enough, filtering can be doneon IMSI range basis as well.

• Mobile equipment phase

It can be used to send information to the NTMS only about equipmentswith certain minimum capabilities (like at least phase2 or phase3

terminals).

• Detected event

It can be used to define which events have to be reported to the NTMS(IMEI change, inter-PLMN location update, or new visitor with specialprevious location).

The VMSC sends both the common MSISDN and the own MSISDN to theNTMS, which provides the NTMS the knowledge that this is a multi-SIM user,and that it can be reached through an SMS with own MSISDN.



Benefits for the operator



2 Benefits for the operator

Feature 1433: Terminal Management Support is essential for the efficientfunctioning of the Nokia Terminal Management Server (NTMS) 1.0 and NokiaTerminal Management Server 2.0.

The feature provides support for the NTMS in the following functions:

• configuring new subscribers and new mobile equipment in the network

• detecting foreign subscribers who have arrived in the home network

• detecting roaming subscribers who have come home from a foreigncountry

The Real Time (RT) functionality makes it possible to detect these eventsimmediately when they take place.

This feature enables the operator to increase the profit, since it allows theautomatic configuration of new mobile equipments in the network and ensures

the subscribers' easier access to new services.

This feature also supports the provisioning of multi-SIM subscribers by sendingboth the own and common MSISDN to the NTMS.

With this feature it is possible to send the subscriber's data of HPLMN1 only tothe NTMS of HPLMN1 if the operator controls twohome networks with differentNTMSs for each network.

When the operator uses both the batch file creation and real time triggering, thelatest data is shown by using the time stamp.








Description of the feature



3 Description of the feature

3.1 Requirements for using the feature

3.1.1 Software

This feature has no special requirements for software.

3.1.2 Hardware

Requirements for the Batch file sending functionality

• The feature requires 32 MB free disk space on the Operation andMaintenance Unit (OMU) disk for the I-series Mobile Services SwitchingCentre (MSCi), (containing eight VLRUs).

• The feature requires 20 MB free disk space on the OMU disk for the MSC(containing five VLRUs).

• If the feature is used in a subrack MSC, a COCEN card is required.

3.1.3 Products

The feature is implemented for both i-series MSC/VLRs and subrack MSC/VLRs.






3.2 Functionality

3.2.1 General

Batch file transfer

The VLR generates one file per one VLRU, which contains the subscribers' ownMSISDN, IMEI, International Mobile Subscriber Identifier (IMSI), and commonMSISDN (if available) numbers. Only those subscribers' data is included in thefile who have valid IMEI number. Furthermore, the VLR can filter the data basedon the subscribers' home PLMN.

During the process of data gathering for the NTMS, the VLR scans through thesubscriber database the same way as in the VLR cleaning procedure. You can setthe accurate start time for the data gathering procedure using the MXM command.

The default time is midnight. At least a 60-minute interval is required between thestart of the VLR cleaning and the data gathering process, regardless of whichprocedure takes place first.

The files are stored on the OMU disk. The NTMS can download the files usingFTP.

After that the NTMS filters the downloaded data. It ignores the irrelevant dataentries (for example, those own MSISDN, IMEI, IMSI, and common MSISDNnumbers that belong to older-generation mobile stations that cannot use theservices provided by the NTMS), and carries out further processing of therelevant data in order to configure the appropriate (new) mobile equipment.

After that the NTMS sends the automatic configuration data, for example, theWAP gateway or the multimedia gateway address, and the user profile, such as,calendar or bookmarks, to the Mobile Subscriber (MS).

New flexible file structure is introduced that contains the file header informationand the data in the record structure.

Real Time triggering

When the VMSCreceives a location update or an access request from a subscriberand IMEI checking is switched on, the VMSC gets the subscriber's IMEI number.After a successful outcome of the transaction, the VLR checks the Real Time

Triggering criteria. Since these trigger short messages cause an additional load inthe MSC-SMSC interface, the operator can control which type of event to detectand which subscribers or equipments are relevant from the point of view of triggering.

The following table contains the types of event that can be chosen to be detected.






Note

The explanation of the parameters and events in the table are the following:

• Using the MS_CLASSMARK parameter, you can specify which type of mobile station must be detected.

• The HOME_VISITOR parameter makes it possible that only HOMEsubscribers, only VISITOR subscribers, or both of them are detected.

• The inter-PLMN location update event refers to a subscriber who has justcome home from a foreign country. National roamers are not detected.

• The New_visitor_with_special_previous_LAI_value eventindicates a new subscription in the network, but it can also be used after anunsuccessful location update.

With the configurable UTPFIL parameter, it is possible to set four different kindsof initial values (location area codes) for theNew_visitor_with_special_previous_LAI_value event.

The VMSC application reads the UTPFIL parameters, and if one of them is thesame as the Location Area Code (LAC) sent by the mobile station, the triggerfunctionality can be started. The Mobile Country Code (MCC) and MobileNetwork Code (MNC) of the previous LAI must match with the Home PLMN'sMCC and MNC.

If the detected event meets the filtering criteria, the VMSC generates a trigger

SM. The 'Trigger Short Message Transfer Protocol (SMTP)-User-Data' fieldcontains the subscriber's own MSISDN, IMEI or IMEISV, IMSI, and commonMSISDN number in ASCII characters. The following figure shows the structureof the user data.

Separate the numbers with spaces.

Table 1. Trigger SM parameters

Event detection Value(HEX)

Filtering criteria Activation statusby default

IMEI changes in the VMSC

database (IMEI)

01 Home/visitor subscriber

MS-classmark

Active

Inter PLMN location update of

a new visitor (PLMN)

02 Home/visitor subscriber

MS-classmark

Not active

New visitor with special

previous LAI value (NV LAI)

03 Home subscriber

MS-classmark

Not active






Note

Figure 1. Trigger TP-User-Data field

TP-User data is coded as 8 bit ASCII characters.

If the subscriber does not have a common MSISDN number, the Detected_eventis the last field in the TP-User-Data.

You have to configure the SMSC address and the SMSC application address(destination-B subscriber number) in the VMSC. Moreover, you have to define acommonly used A-MSISDN (TMSISDN) and A-IMSI (CIMSI) numbers as thesender of the created mobile-originated SM (A number).

The trigger MO-SM is sent towards a specific SMSC and SMSC applicationaddress. The NTMS receives it directly from the specific SMSC application. Asfor the remaining triggers, the NTMS gets them when it downloads the batch filesfrom the OMU disk as described above.

3.2.2 Additional information

IMSI filtering in Terminal Management Support

A new PLMN-specific parameter is introduced to filter and detect only thosesubscribers who belong to a selected proper Public Land Mobile Network (PLMN). The MSC generates trigger SMs and batch files towards the NTMS if the subscriber belongs to the PLMN that has 'TRIGGER SM TO NTMS =ALLOWED' in a PLMN-specific file. This functionality can be useful if there aremore 'home networks' inside your Circuit Switched (CS) core network.

If this functionality is active, the 'HOME_VISITOR' parameter has no effect.

MSC_36209956524_490523102400750_21601585458_PLMN_3620700000

Flag + MSISDN + IMEI(SV) + IMSI +Detected+COMMON MSISDN

event






Batch file transfer

• You have to set the IMEI-checking on at least for new visitors and for the'IMSI attach' in the home PLMN. This is essential from the functionalitypoint of view.

• The MSISDN-IMEI-IMSI list for NTMS file is not encoded on the OMUdisk. You have to use a secure internal network or ensure the security withan external function.

• If the VLR cleaning process and the data gathering for the NTMS takeplace on the same night, run the gathering process first.

• The COCEN card is required to download the MSISDN-IMEI-IMSI list forthe NTMS file through the TCP/IP link in the subrack MSC. The COCENcard can be configured with the WTP command.

• For transfer through TCP/IP, the COCEN plug-in unit is necessary to builda connection in the subrack mechanism, or a CP6LX-S processor card isneeded with built-in LAN interface.

• If the Super-Charger feature isused, the VLR database contains active andpassive subscriber data. The batch files produced for the NTMS includeonly the active subscribers' data. Even in this case the NTMS can receivethe same subscriber's data from more VLRs, because the subscriber may bein an active state in more than one VLRs. The received data can also beconflicting. On the other hand, due to the on demand cleaning method, theVLR may remove the active subscriber before it produces the batch files.


• If you set the MSC to send a trigger SM in the case of an inter-PLMNlocation update inside the same VMSC, the NTMS has to filter out theunnecessary inter-system location update triggers (from the UMTStowards the GSM).

• The NTMS can notice the new equipment and the subscriber withmaximum one day delay.

• The RT triggering functionality does not generate a trigger SM when theuser switches off the mobile station under VMSC1, then puts the SIM cardto a new mobile station and switches ON the mobile station under VMSC2.






• The Real Time triggering functionality does not generate two trigger SMswhen two users change mobile stations. When user 1 makes the locationupdate, a trigger SM is generated and it deletes the IMEI number from user2 record in the VMSC. When User2 makes the location update, a trigger

SM is not generated, because the previous IMEI number has been deleted.

• The Real Time triggering functionality does not generate a trigger SMwhen a General Packet Radio Service (GPRS) subscriber makes a locationupdate through the Serving GPRS Support Node (SGSN) since the IMEInumber is not transferred automatically from the SGSN to the MSC/VLR.This requires an optional feature.

Override Common MSISDN in NTMS MO-SM case

When subscribers make a self-provisioning to update some information, such as,firmware, GPRS, WAP, MMS, and so on, in their mobile equipments, they needto send a special MO-SM. If the subscriber is a multi-SIM user, the same multi-

SIM common ISDN number is used in the network.

With this feature, the MSC can recognise those self-provisioning MO-SMs thatare sent to the NTMS based on the called subscriber number and thus the MSCdoes not exchange the subscriber's own MSISDN number to the multi-SIMcommon ISDN number.

Skip SMS deny in NTMS SMS case

When the Feature 1545 and 1576 Sequential and Parallel Alerting is active, theoperator can set the SMS-Deny flag in member level in order to ignore all the MT-SMs that arrive with own MSISDN number and allow only MT-SMs send to theGroup number. This is problematic when the application server wants to sendMT-SM to the subscriber's own MSISDN number.

To solve this problem the GMSC compares the address of the sender applicationreceived in the MT-SM to the PROVAC parameter in order to recognise those MT-SMs. If so, the MSC sets the MEMBER INTERROGATION and CFUSMCFOflag in SRI_FOR_SM (Nokia propriatery extension) in order to inform the HLRabout the SM coming from an application. When the HLR gets this indication itdoes not check the Deny Direct SM parameter and SM forwarding from thesubscriber data and allows the MT-SM delivery to the own subscriber number.

3.2.3 Files

The active home subscriber's own MSISDN, IMEI, IMSI, and common MSISDNnumbers are copied to the new MSISDN-IMEI-IMSI list for NTMS files. Thefiles are located on the OMU disk in the ASWDIR/NTMS subdirectory.

There are as many files as VLR units. Each VLRU creates its own MSISDN-IMEI-IMSI list for the NTMS file. The file names are LMTMS0.LST,LMTMS1.LST, … , and LMTMS7.LST.






The files are binary and contain records separated by '0xEE'. The records consistof the own MSISDN (represented in 11 bytes), the IMEI (represented in 8 bytes),the IMSI (represented in 9 bytes), and the common MSISDN (represented in 11bytes) numbers in this order. If the subscriber does not have a common MSISDN

number, the last field in the record is the IMSI number.

One record length is 40 bytes including the separator. The maximum file size isapproximately 4 MB. These files do not have headers.

The NTMS can download the content of the files through the TCP/IP connection,using FTP.

If the PLMN-specific filtering functionality is active, the files contain only thosesubscribers' data who come from the selected PLMN.

New flexible file structure is introduced that contains file header information andrecord elements. The new file structure contains the actual system time to solvecooperation problem between real time triggering and batch file creation.

3.2.4 Parameters

The following PRFILE parameters are related to this feature:

COMMON_MSISDN_SENT (002:0867) This parameter determines whether thecommon MSISDN/CLI is provided to the NTMS or not.

NTMS_SELF_PROV_SM_USED (031:0051) By using this parameter, the MSCsends the own MSISDN number in self-provisioning SMstowards the NTMS, even though the Multi-SIM feature isactive and the subscriber is a multi-SIM user.

NTMS_SKIP_SM_DENY (031:0055) This parameter can be used so theapplication-originated SM can be sent to own MSISDNnumber of the subscriber even if the SMS_DENYfunctionality is active in the HLR. When this parameter isactive, the SMS forwarding is also overriden in the HLR.

NTMS_FLEXIBLE_FILE (031:0053) ThePRFILEparameterdefines whether thenew flexible file structure or the old file structure is used in theMSC/HLR.

IMEISV_TO_NTMS (031:0054) This parameter determines whether the IMEISV(16 digits) or the IMEI (15 digits) is sent to the NTMS.

The following FIFILE parameters are related to this feature:

MTMS_DATA (002:0714) This parameter controls the feature activation anddeactivation.

NTMS_REAL_TIME_SM_ACTIV (031:0049) This parameter controls theactivation and deactivation of the Real Time triggering part of the feature.

NTMS_PLMN_SPEC_FILT (002:0942) The PLMN-specific filteringfunctionality can be controlled with this parameter.






3.2.5 Statistics

Real Time triggers are reported as trigger SMs in the Field Reporting ServiceMeasurement and as ordinary MO-SMs in SMS Measurement in the IWMSC.

3.2.6 Charging

No charging data record is generated in trigger SMs.

3.3 Capacity

The creation of batch files may cause an overload problem in the Message Busbetween the VLRU and the OMU. For this reason, it is very important to run the

data gathering process at night when the VLR and Message Bus load is lower.

Every night, maximum 23 MB of data (eight VLRUs) can go through the TCP/IPlink, between the MSCi/VLR and the NTMS.

For the subrack MSC, the maximum amount of data is 11 MB (five VLRUs).

Since in the Real Time functionality the MSC/VLR also detects internationalroamers, the number of Trigger SMs can increase significantly in the MSCs thatserve an airport or a border area.

If the SMSC capacity is lower than the MSCi, use the MO-SMS limiter (mainly

in TCP/IP connection) to avoid the SMSC being overloaded.

3.4 Restrictions

Batch file transfer

• It is recommended to run the process of data gathering for the NTMS in lowtraffic hours.

• For the MSCi, provide 23-MB disk space for the eight new files on theOMU Winchester Data Unit (WDU).

• The required space for the subrack MSC is 11 MB.

• At least a 60-minute interval is required between the start of the VLRcleaning and the start of the data gathering process for the NTMS.

• If you use the 'Previous LAI is special value' detection and the network contains restricted areas for a lot of subscribers, the amount of trigger SMscan increase. If so, the load is not significant.







• After a VMSC restart, the amount of trigger SMs may also increasebecause of the previous unsuccessful location updates of the subscribers.Therefore, it is advised to switch off theNew_visitor_with_special_previous_LAI_value parameterafter a VMSC restart for at least one location update period.

3.5 Related and interworking features

Thefile processing application was implemented in Nokia Terminal ManagementServer 1.0. The real time processing application was implemented in NokiaTerminal Management Server 2.0. For more information, see Nokia Terminal

Management Server Product Description.

This feature has the following interworking functionalities:

• Same CLI for Multiple Subscribers

With the help of this feature both common and own MSISDN can beprovided to the NTMS.

For more information, see Feature 1541: Same CLI for MultipleSubscribers, Feature Description.

• Super-Charger

If the Super-Charger feature is used, the VLR database contains active andpassive subscriber data.

For more information, see Feature 1627: Super-Charger, Feature Description.

• Sequential and Parallel Alerting

If the Sequential and Parallel Alerting feature is active and theNTMS_SKIP_SM_DENYPRFILE parameter is set, the 'SMS deny flag'function can be overwritten if the SMS comes from a special application(for example, NTMS).

Formore information, seeFeature 1545 and1576: Sequential andParallel Alerting, Feature Description.

3.6 Compliance

The feature is Nokia-specific. This feature is supported in 3G.








Interfaces



4 Interfaces

4.1 Operator interfaces

4.1.1 MMLs

The following MMLs are related to this feature:

VLR and PLMN Parameter Handling, MX Command Group

MXM Modify VLR parameters

Use this command to modify VLR-specific parameters.

Use the BATCH FILE CREATION START TIME (MTIM)parameter to set the start time of the data gathering processthat is designed to create the MSISDN-IMEI-IMSI list for theMTMS file on the OMU disk.

The default value is 00:00 (midnight).

At least a 60-minute interval is required between the start of the VLR cleaning and the start of the data gathering processfor the NTMS. It is recommended to run the data gatheringprocess first, before the VLR cleaning process.

Use the INTER PLMN LOCATION UPDATE (INPLU)parameter to set if the VMSC has to generate a trigger SMwhen a home subscriber comes back from a foreign countryand when a foreign subscriber arrives in the network.

Use the NEW VISITOR WITH SPECIAL PREVIOUS LAIVALUE (NVLAI) parameter to set if the VMSC has to generatea trigger SM when new subscribers first switch on their MS.If this functionality is activated, a trigger SM is also generatedwhen subscribers move to a different VLR area and theirprevious LAI is one of the preconfigured values.

The HOME VISITOR (RSTAT) parameter makes it possiblethat only HOME subscribers, only VISITOR subscribers, orboth of the above are detected.

Use the MS CLASSMARK (MSCLASS) parameter to set theminimum revision level (phase 1, phase 2, and so on) of themobile stations to be detected.






MXO Output VLR parameters

Use this command to display the current values of VLR-specific parameters and to display the start time of the processof data gathering for the NTMS.

MXP Output PLMN parametersUse this command to display the current parameter values of one PLMN.

MXN Modify PLMN parameters.

Use this command to modify PLMN parameters.

With the TRIGNTMS parameter you can define whether thesubscribers who belong to that PLMN have to be detected ornot.

Use the PLMN-SPECIFIC FILTERING parameter to sendonly those subscribers' data in Real Time Trigger SM whobelong to a specific PLMN. Either PLMN-specific filtering is

active, or the HOME/VISITOR parameter is active.

For further information, see VLR andPLMN Parameter Handling, MX Command Group.

GSM Network and Network Element Specific Number Handling, WVCommand Group

WVS Create network and network element-specific number

Use the SMSC ADDRESS FOR TRIGGER SM (TRIGSC)parameter to set the specific SMSC address for the triggerSM.

Use the SMSC APPLICATION FOR TRIGGER SM (TRIGAC)

parameter to set the specific SMSC application address (Bnumber) for the trigger SM.

Use the APPLICATION ADDRESS OF PROVISIONING(PROVAC) parameter to set the specific external applicationaddress for provisioning SM.

Use the COMMON MSISDN NUMBER FOR TRIGGER SM(TMSISDN) parameter to set the sender of the trigger SM.

Use the COMMON IMSI NUMBER FOR TRIGGER SM (CIMSI)parameter to set the sender of the trigger SM.

WVR Delete network and network element-specific number

Use the DELETE NETWORK AND MSC/HLR SPECIFICNUMBER parameter to delete a specific SMSC address, SMSC

application address, common MSISDN, common IMSInumber from the real time triggers.

WVI Interrogate network and network element-specific number

Use theINTERROGATE NETWORK AND MSC/HLR SPECIFICNUMBER parameter to interrogate a specific SMSC address,SMSC application address, common MSISDN, commonIMSI number of the real time triggers.



Interfaces



WVF Modify network and network element-specific number

Use the MODIFY NETWORK AND MSC/HLR SPECIFICNUMBER parameter to modify a specific SMSC address,SMSC application address, common MSISDN, common

IMSI number of the real time triggers.

For further information, see GSM Network and Network Element Specific Number Handling, WV Command Group.

4.1.2 Alarms

There are no alarms related to this feature.

4.2 Subscriber interfacesThis feature only provides subscriber-specific information to the NTMS, whichprovides the subscribers.

4.3 External interfaces

The feature affects the following interfaces of the MSC/VLR:

Figure 2. Network elements involved in batch file sending functionality

Figure 3. Network elements involved in Real Time functionality

FTP

LMTMS0.LST...LMTMS7.LST

MSC/VLRNTMS

SM

Direct connection

SMSC IWMSC VMSCSM SM

Short Messagegenerated

NTMS








Main changes in the feature



5 Main changes in the feature

This feature is implemented in M13, M13.1, and M13.2.

Changes between M13.2 and M13.1

• New flexible file structure is introduced.

• The IMEISV is supported in batch file and real time triggering.

Changes between M13.1 and M13

• Information on the batch files produced for the NTMS has been added.

• Visitor subscriber has been removed as the filtering criteria for the 'newvisitor with special previous LAI value' event.

• Values of detected events have been added.

• The required disk space for the MSC and MSCi has been corrected.










References

1. VLR and PLMN Parameter Handling, MX Command Group

2. GSM Network and Network Element Specific Number Handling, WV

Command Group

3. Nokia Terminal Management Server Product Description

4. Feature 854: File Transfer Protocol Over TCP/IP, Feature ActivationManual

5. Feature 1541: Same CLI for Multiple Subscribers, Feature Description

6. Feature 1545 and 1576: Sequential and Parallel Alerting, FeatureDescription

7. Feature 1627: Super-Charger, Feature Description










Glossary

Abbreviations

CLI Calling Line Identification

CS Circuit Switched

FTP File Transfer Protocol

GPRS General Packet Radio Service

HLR Home Location Register

HPLMN Home Public Land Mobile Network

IMEI International Mobile Equipment Identity

IMEISV International Mobile Equipment Identity Software Version

IMSI International Mobile Subscriber Identity

IWMSC Interworking Mobile Switching Centre

LAC Location Area Code

LAI Location Area Identity

LAN Local Area Network

MMSC Multimedia Messaging Service Centre

MO Mobile-Originated

MS Mobile Subscriber

MSC Subrack Mobile Services Switching Centre

MSCi I-series Mobile Services Switching Centre

MSISDN Mobile Subscriber ISDN number

NTMS Nokia Terminal Management Server

OMU Operation and Maintenance Unit

PLMN Public Land Mobile Network

SGSN Serving GPRS Support Node

SM Short Message




SMSC Short Message Service Centre

SMTP Short Message Trasnport Protocol

TCP/IP Transmission Control Protocol/Internet Protocol

UMTS Universal Mobile Telecommunication System

VLR Visitor Location Register

VLRU Visitor Location Register Computer Unit

VMSC Visited Mobile Services Switching Centre

WDU Winchester Data Unit

TermsActive or passivesubscriber

A VLR that supports the Super-Charger feature considers the subscriber activeuntil it receives a (SendIdentification or CancelLocation) notification that thesubscriber has been moved to another VLR. The active status does not necessarilymean that the subscriber is roaming under this VLR and the HLR stores theaddress of this VLR. The same subscriber's status can be active in more than oneVLRs.

The passive status means that the subcriber is not roaming under the VLR, but itsdata is retained for later usage.

Previous LAI The mobile station sends this number to the network when an access request is

initiated.

Nokia TerminalManagement Server

External network element which provides automatic configuration of the mobileequipment and of the user capability information for the MMSC duringmultimedia sessions.

Triggering Indication to the Mobile Terminal Management Server to start the automaticconfiguration.

Trigger SM Short message generated by the MSC after a successful event.

Common MSIS-DN/CLI

The number whichis commonly used by several subscribers (IMSIs). In the HLR,it is a normal attribute of the subscriber. In the VLR, it is used to identify thesubscriber(s).

Own MSISDN The number which belongs to the primary basic service and uniquely identifiesthe subscriber in the HLR. The HLR can optionally use this number towards theVLR/SGSN in the location update procedure.

Time stamp It is information added to a record or other form of data showing the date and timeit was processed and possibly the user.

Documents

real time trigger feat 1433