Real Time Trigger Feat 1433
This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA
Overview
Download & View Real Time Trigger Feat 1433 as PDF for free.
More details
- Words: 5,469
- Pages: 30
FEATURE 1433 Terminal Management Support
DN01170933 Issue 3-2 en
© Nokia Corporation Nokia Proprietary and Confidential
1 (30)
FEATURE 1433 Terminal Management Support
The information in this documentation 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's customers only for the purposes of the agreement under which the documentation is submitted, and no part of it may be reproduced or transmitted in any form or means without the prior written permission of Nokia. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia 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 cannot be considered binding but shall be defined in the agreement made between Nokia and the customer. However, Nokia has made all reasonable efforts to ensure that the instructions contained in the documentation are adequate and free of material errors and omissions. Nokia will, if necessary, explain issues which may not be covered by the documentation. Nokia's liability for any errors in the documentation is limited to the documentary correction of errors. NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDING MONETARY LOSSES), that might arise from the use of this documentation or the information in it. This documentation and the product it describes are considered protected by copyright according 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 respective companies, and they are mentioned for identification purposes only. Copyright © Nokia Corporation 2005. All rights reserved.
2 (30)
© Nokia Corporation Nokia Proprietary and Confidential
DN01170933 Issue 3-2 en
Contents Contents 3 List of tables 4 List of figures 5 1
Introduction 7
2
Benefits for the operator 9
3 3.1 3.1.1 3.1.2 3.1.3 3.2 3.2.1 3.2.2 3.2.3 3.2.4 3.2.5 3.2.6 3.3 3.4 3.5 3.6
Description of the feature 11 Requirements for using the feature 11 Software 11 Hardware 11 Products 11 Functionality 12 General 12 Additional information 14 Files 16 Parameters 17 Statistics 18 Charging 18 Capacity 18 Restrictions 18 Related and interworking features 19 Compliance 19
4 4.1 4.1.1 4.1.2 4.2 4.3
Interfaces 21 Operator interfaces 21 MMLs 21 Alarms 23 Subscriber interfaces 23 External interfaces 23
5
Main changes in the feature 25 References 27 Glossary 29
DN01170933 Issue 3-2 en
© Nokia Corporation Nokia Proprietary and Confidential
3 (30)
FEATURE 1433 Terminal Management Support
List of tables Table 1.
4 (30)
Trigger SM parameters
13
© Nokia Corporation Nokia Proprietary and Confidential
DN01170933 Issue 3-2 en
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
DN01170933 Issue 3-2 en
© Nokia Corporation Nokia Proprietary and Confidential
5 (30)
FEATURE 1433 Terminal Management Support
6 (30)
© Nokia Corporation Nokia Proprietary and Confidential
DN01170933 Issue 3-2 en
Introduction
1
Introduction The configuration of the mobile equipment, for which the Nokia Terminal Management Server (NTMS) can provide additional services, consists of two stages: 1.
Identifying the mobile equipment that needs configuration update and supports automatic configuration.
2.
Sending the new settings to the mobile equipment, for example in a Short Message Service (SMS) or Wireless Application Protocol (WAP) Push message.
This feature provides support for the first stage by gathering and sending the subscriber-mobile terminal associations to the NTMS. This enables the NTMS to select and configure the relevant mobile stations automatically, that is, in such a way that the subscriber or the operator does not have to enter the data into the equipment 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 the NTMS can download later through File Transfer Protocol (FTP). The gathering process of data takes place once a day at a configurable time. The NTMS gets information 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 services Switching Centre (VMSC) detects an event, it sends a trigger to the NTMS. These triggers are sent in SMS, since the NTMS has a direct connection to the Short Message Service Centre (SMSC). The VMSC sends a trigger immediately in the following cases:
DN01170933 Issue 3-2 en
•
when an International Mobile Equipment Identity (IMEI) change is detected
•
when a roamer arrives from a foreign country
•
when a subscriber makes an inter-VLR location update and the previous location of the user is one of the configured LAIs
© Nokia Corporation Nokia Proprietary and Confidential
7 (30)
FEATURE 1433 Terminal Management Support
Feature 1433: Terminal Management Support supports the International Mobile Equipment Identity Software Version (IMEISV) in batch file and real time triggering. This feature also provides pre-filtering possibilities, which decrease the amount of 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 or home subscribers, or if this granularity is not enough, filtering can be done on IMSI range basis as well.
•
Mobile equipment phase It can be used to send information to the NTMS only about equipments with 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 special previous location).
The VMSC sends both the common MSISDN and the own MSISDN to the NTMS, 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.
8 (30)
© Nokia Corporation Nokia Proprietary and Confidential
DN01170933 Issue 3-2 en
Benefits for the operator
2
Benefits for the operator Feature 1433: Terminal Management Support is essential for the efficient functioning of the Nokia Terminal Management Server (NTMS) 1.0 and Nokia Terminal 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 foreign country
The Real Time (RT) functionality makes it possible to detect these events immediately when they take place. This feature enables the operator to increase the profit, since it allows the automatic 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 sending both the own and common MSISDN to the NTMS. With this feature it is possible to send the subscriber's data of HPLMN1 only to the NTMS of HPLMN1 if the operator controls two home networks with different NTMSs for each network. When the operator uses both the batch file creation and real time triggering, the latest data is shown by using the time stamp.
DN01170933 Issue 3-2 en
© Nokia Corporation Nokia Proprietary and Confidential
9 (30)
FEATURE 1433 Terminal Management Support
10 (30)
© Nokia Corporation Nokia Proprietary and Confidential
DN01170933 Issue 3-2 en
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
3.1.3
•
The feature requires 32 MB free disk space on the Operation and Maintenance Unit (OMU) disk for the I-series Mobile Services Switching Centre (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.
Products The feature is implemented for both i-series MSC/VLRs and subrack MSC/VLRs.
DN01170933 Issue 3-2 en
© Nokia Corporation Nokia Proprietary and Confidential
11 (30)
FEATURE 1433 Terminal Management Support
3.2
Functionality
3.2.1
General Batch file transfer
The VLR generates one file per one VLRU, which contains the subscribers' own MSISDN, IMEI, International Mobile Subscriber Identifier (IMSI), and common MSISDN (if available) numbers. Only those subscribers' data is included in the file who have valid IMEI number. Furthermore, the VLR can filter the data based on the subscribers' home PLMN. During the process of data gathering for the NTMS, the VLR scans through the subscriber database the same way as in the VLR cleaning procedure. You can set the 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 the start of the VLR cleaning and the data gathering process, regardless of which procedure takes place first. The files are stored on the OMU disk. The NTMS can download the files using FTP. After that the NTMS filters the downloaded data. It ignores the irrelevant data entries (for example, those own MSISDN, IMEI, IMSI, and common MSISDN numbers that belong to older-generation mobile stations that cannot use the services provided by the NTMS), and carries out further processing of the relevant data in order to configure the appropriate (new) mobile equipment. After that the NTMS sends the automatic configuration data, for example, the WAP 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 information and the data in the record structure. Real Time triggering
When the VMSC receives a location update or an access request from a subscriber and 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 in the MSC-SMSC interface, the operator can control which type of event to detect and 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.
12 (30)
© Nokia Corporation Nokia Proprietary and Confidential
DN01170933 Issue 3-2 en
Description of the feature
Table 1.
Trigger SM parameters
Event detection
Value (HEX)
IMEI changes in the VMSC database (IMEI)
01
Inter PLMN location update of a new visitor (PLMN)
02
New visitor with special previous LAI value (NV LAI)
03
Filtering criteria
Activation status by default
Home/visitor subscriber
Active
MS-classmark Home/visitor subscriber
Not active
MS-classmark Home subscriber
Not active
MS-classmark
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 HOME subscribers, only VISITOR subscribers, or both of them are detected.
•
The inter-PLMN location update event refers to a subscriber who has just come home from a foreign country. National roamers are not detected.
•
The New_visitor_with_special_previous_LAI_value event indicates a new subscription in the network, but it can also be used after an unsuccessful location update.
With the configurable UTPFIL parameter, it is possible to set four different kinds of initial values (location area codes) for the New_visitor_with_special_previous_LAI_value event. The VMSC application reads the UTPFIL parameters, and if one of them is the same as the Location Area Code (LAC) sent by the mobile station, the trigger functionality can be started. The Mobile Country Code (MCC) and Mobile Network Code (MNC) of the previous LAI must match with the Home PLMN's MCC 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' field contains the subscriber's own MSISDN, IMEI or IMEISV, IMSI, and common MSISDN number in ASCII characters. The following figure shows the structure of the user data.
Note Separate the numbers with spaces.
DN01170933 Issue 3-2 en
© Nokia Corporation Nokia Proprietary and Confidential
13 (30)
FEATURE 1433 Terminal Management Support
MSC_36209956524_490523102400750_21601585458_PLMN_3620700000 Flag +
MSISDN
+
Figure 1.
IMEI(SV)
+
IMSI
+Detected+COMMON MSISDN event
Trigger TP-User-Data field
Note TP-User data is coded as 8 bit ASCII characters. If the subscriber does not have a common MSISDN number, the Detected_event is 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 a commonly used A-MSISDN (TMSISDN) and A-IMSI (CIMSI) numbers as the sender of the created mobile-originated SM (A number). The trigger MO-SM is sent towards a specific SMSC and SMSC application address. The NTMS receives it directly from the specific SMSC application. As for the remaining triggers, the NTMS gets them when it downloads the batch files from 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 those subscribers 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 are more 'home networks' inside your Circuit Switched (CS) core network. If this functionality is active, the 'HOME_VISITOR' parameter has no effect.
14 (30)
© Nokia Corporation Nokia Proprietary and Confidential
DN01170933 Issue 3-2 en
Description of the feature
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 functionality point of view.
•
The MSISDN-IMEI-IMSI list for NTMS file is not encoded on the OMU disk. You have to use a secure internal network or ensure the security with an external function.
•
If the VLR cleaning process and the data gathering for the NTMS take place on the same night, run the gathering process first.
•
The COCEN card is required to download the MSISDN-IMEI-IMSI list for the NTMS file through the TCP/IP link in the subrack MSC. The COCEN card can be configured with the WTP command.
•
For transfer through TCP/IP, the COCEN plug-in unit is necessary to build a connection in the subrack mechanism, or a CP6LX-S processor card is needed with built-in LAN interface.
•
If the Super-Charger feature is used, the VLR database contains active and passive subscriber data. The batch files produced for the NTMS include only the active subscribers' data. Even in this case the NTMS can receive the same subscriber's data from more VLRs, because the subscriber may be in an active state in more than one VLRs. The received data can also be conflicting. On the other hand, due to the on demand cleaning method, the VLR may remove the active subscriber before it produces the batch files.
Real Time triggering
DN01170933 Issue 3-2 en
•
If you set the MSC to send a trigger SM in the case of an inter-PLMN location update inside the same VMSC, the NTMS has to filter out the unnecessary inter-system location update triggers (from the UMTS towards the GSM).
•
The NTMS can notice the new equipment and the subscriber with maximum one day delay.
•
The RT triggering functionality does not generate a trigger SM when the user switches off the mobile station under VMSC1, then puts the SIM card to a new mobile station and switches ON the mobile station under VMSC2.
© Nokia Corporation Nokia Proprietary and Confidential
15 (30)
FEATURE 1433 Terminal Management Support
•
The Real Time triggering functionality does not generate two trigger SMs when two users change mobile stations. When user 1 makes the location update, a trigger SM is generated and it deletes the IMEI number from user 2 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 SM when a General Packet Radio Service (GPRS) subscriber makes a location update through the Serving GPRS Support Node (SGSN) since the IMEI number 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 need to send a special MO-SM. If the subscriber is a multi-SIM user, the same multiSIM common ISDN number is used in the network. With this feature, the MSC can recognise those self-provisioning MO-SMs that are sent to the NTMS based on the called subscriber number and thus the MSC does not exchange the subscriber's own MSISDN number to the multi-SIM common ISDN number. Skip SMS deny in NTMS SMS case
When the Feature 1545 and 1576 Sequential and Parallel Alerting is active, the operator can set the SMS-Deny flag in member level in order to ignore all the MTSMs that arrive with own MSISDN number and allow only MT-SMs send to the Group number. This is problematic when the application server wants to send MT-SM to the subscriber's own MSISDN number. To solve this problem the GMSC compares the address of the sender application received in the MT-SM to the PROVAC parameter in order to recognise those MTSMs. If so, the MSC sets the MEMBER INTERROGATION and CFUSMCFO flag in SRI_FOR_SM (Nokia propriatery extension) in order to inform the HLR about the SM coming from an application. When the HLR gets this indication it does not check the Deny Direct SM parameter and SM forwarding from the subscriber 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 MSISDN numbers are copied to the new MSISDN-IMEI-IMSI list for NTMS files. The files are located on the OMU disk in the ASWDIR/NTMS subdirectory. There are as many files as VLR units. Each VLRU creates its own MSISDNIMEI-IMSI list for the NTMS file. The file names are LMTMS0.LST, LMTMS1.LST, … , and LMTMS7.LST.
16 (30)
© Nokia Corporation Nokia Proprietary and Confidential
DN01170933 Issue 3-2 en
Description of the feature
The files are binary and contain records separated by '0xEE'. The records consist of 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 11 bytes) 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 is approximately 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 those subscribers' data who come from the selected PLMN. New flexible file structure is introduced that contains file header information and record elements. The new file structure contains the actual system time to solve cooperation 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 the
common MSISDN/CLI is provided to the NTMS or not. NTMS_SELF_PROV_SM_USED (031:0051) By using this parameter, the MSC sends the own MSISDN number in self-provisioning SMs towards the NTMS, even though the Multi-SIM feature is active and the subscriber is a multi-SIM user. NTMS_SKIP_SM_DENY (031:0055) This parameter can be used so the application-originated SM can be sent to own MSISDN number of the subscriber even if the SMS_DENY functionality is active in the HLR. When this parameter is active, the SMS forwarding is also overriden in the HLR. NTMS_FLEXIBLE_FILE (031:0053) The PRFILE parameter defines whether the new flexible file structure or the old file structure is used in the MSC/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 and
deactivation. NTMS_REAL_TIME_SM_ACTIV (031:0049) This parameter controls the activation and deactivation of the Real Time triggering part of the feature. NTMS_PLMN_SPEC_FILT (002:0942) The PLMN-specific filtering functionality can be controlled with this parameter.
DN01170933 Issue 3-2 en
© Nokia Corporation Nokia Proprietary and Confidential
17 (30)
FEATURE 1433 Terminal Management Support
3.2.5
Statistics Real Time triggers are reported as trigger SMs in the Field Reporting Service Measurement 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 Bus between 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/IP link, 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 international roamers, the number of Trigger SMs can increase significantly in the MSCs that serve 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
18 (30)
•
It is recommended to run the process of data gathering for the NTMS in low traffic hours.
•
For the MSCi, provide 23-MB disk space for the eight new files on the OMU 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 VLR cleaning 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 SMs can increase. If so, the load is not significant.
© Nokia Corporation Nokia Proprietary and Confidential
DN01170933 Issue 3-2 en
Description of the feature
Real Time triggering
•
3.5
After a VMSC restart, the amount of trigger SMs may also increase because of the previous unsuccessful location updates of the subscribers. Therefore, it is advised to switch off the New_visitor_with_special_previous_LAI_value parameter after a VMSC restart for at least one location update period.
Related and interworking features The file processing application was implemented in Nokia Terminal Management Server 1.0. The real time processing application was implemented in Nokia Terminal 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 be provided to the NTMS. For more information, see Feature 1541: Same CLI for Multiple Subscribers, Feature Description.
•
Super-Charger If the Super-Charger feature is used, the VLR database contains active and passive 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 the NTMS_SKIP_SM_DENY PRFILE parameter is set, the 'SMS deny flag'
function can be overwritten if the SMS comes from a special application (for example, NTMS). For more information, see Feature 1545 and 1576: Sequential and Parallel Alerting, Feature Description.
3.6
Compliance The feature is Nokia-specific. This feature is supported in 3G.
DN01170933 Issue 3-2 en
© Nokia Corporation Nokia Proprietary and Confidential
19 (30)
FEATURE 1433 Terminal Management Support
20 (30)
© Nokia Corporation Nokia Proprietary and Confidential
DN01170933 Issue 3-2 en
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
DN01170933 Issue 3-2 en
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 process that is designed to create the MSISDN-IMEI-IMSI list for the MTMS 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 process for the NTMS. It is recommended to run the data gathering process first, before the VLR cleaning process. Use the INTER PLMN LOCATION UPDATE (INPLU) parameter to set if the VMSC has to generate a trigger SM when a home subscriber comes back from a foreign country and when a foreign subscriber arrives in the network. Use the NEW VISITOR WITH SPECIAL PREVIOUS LAI VALUE (NVLAI) parameter to set if the VMSC has to generate a trigger SM when new subscribers first switch on their MS. If this functionality is activated, a trigger SM is also generated when subscribers move to a different VLR area and their previous LAI is one of the preconfigured values. The HOME VISITOR (RSTAT) parameter makes it possible that only HOME subscribers, only VISITOR subscribers, or both of the above are detected. Use the MS CLASSMARK (MSCLASS) parameter to set the minimum revision level (phase 1, phase 2, and so on) of the mobile stations to be detected.
© Nokia Corporation Nokia Proprietary and Confidential
21 (30)
FEATURE 1433 Terminal Management Support
MXO
MXP
MXN
Output VLR parameters Use this command to display the current values of VLRspecific parameters and to display the start time of the process of data gathering for the NTMS. Output PLMN parameters Use this command to display the current parameter values of one PLMN. Modify PLMN parameters. Use this command to modify PLMN parameters. With the TRIGNTMS parameter you can define whether the subscribers who belong to that PLMN have to be detected or not. Use the PLMN-SPECIFIC FILTERING parameter to send only those subscribers' data in Real Time Trigger SM who belong to a specific PLMN. Either PLMN-specific filtering is active, or the HOME/VISITOR parameter is active.
For further information, see VLR and PLMN Parameter Handling, MX Command Group. GSM Network and Network Element Specific Number Handling, WV Command Group
WVS
WVR
WVI
22 (30)
Create network and network element-specific number Use the SMSC ADDRESS FOR TRIGGER SM (TRIGSC) parameter to set the specific SMSC address for the trigger SM. Use the SMSC APPLICATION FOR TRIGGER SM (TRIGAC) parameter to set the specific SMSC application address (B number) for the trigger SM. Use the APPLICATION ADDRESS OF PROVISIONING (PROVAC) parameter to set the specific external application address 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. Delete network and network element-specific number Use the DELETE NETWORK AND MSC/HLR SPECIFIC NUMBER parameter to delete a specific SMSC address, SMSC application address, common MSISDN, common IMSI number from the real time triggers. Interrogate network and network element-specific number Use the INTERROGATE NETWORK AND MSC/HLR SPECIFIC NUMBER parameter to interrogate a specific SMSC address, SMSC application address, common MSISDN, common IMSI number of the real time triggers.
© Nokia Corporation Nokia Proprietary and Confidential
DN01170933 Issue 3-2 en
Interfaces
WVF
Modify network and network element-specific number Use the MODIFY NETWORK AND MSC/HLR SPECIFIC NUMBER 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 interfaces This feature only provides subscriber-specific information to the NTMS, which provides the subscribers.
4.3
External interfaces The feature affects the following interfaces of the MSC/VLR:
FTP
NTMS
MSC/VLR
LMTMS0.LST...LMTMS7.LST
Figure 2.
NTMS
Network elements involved in batch file sending functionality
SM
SMSC
Direct connection
Figure 3.
DN01170933 Issue 3-2 en
SM
IWMSC
SM
VMSC
Short Message generated
Network elements involved in Real Time functionality
© Nokia Corporation Nokia Proprietary and Confidential
23 (30)
FEATURE 1433 Terminal Management Support
24 (30)
© Nokia Corporation Nokia Proprietary and Confidential
DN01170933 Issue 3-2 en
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
DN01170933 Issue 3-2 en
•
Information on the batch files produced for the NTMS has been added.
•
Visitor subscriber has been removed as the filtering criteria for the 'new visitor 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.
© Nokia Corporation Nokia Proprietary and Confidential
25 (30)
FEATURE 1433 Terminal Management Support
26 (30)
© Nokia Corporation Nokia Proprietary and Confidential
DN01170933 Issue 3-2 en
References
DN01170933 Issue 3-2 en
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 Activation Manual
5.
Feature 1541: Same CLI for Multiple Subscribers, Feature Description
6.
Feature 1545 and 1576: Sequential and Parallel Alerting, Feature Description
7.
Feature 1627: Super-Charger, Feature Description
© Nokia Corporation Nokia Proprietary and Confidential
27 (30)
FEATURE 1433 Terminal Management Support
28 (30)
© Nokia Corporation Nokia Proprietary and Confidential
DN01170933 Issue 3-2 en
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
DN01170933 Issue 3-2 en
© Nokia Corporation Nokia Proprietary and Confidential
29 (30)
FEATURE 1433 Terminal Management Support
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
Terms Active or passive subscriber
A VLR that supports the Super-Charger feature considers the subscriber active until it receives a (SendIdentification or CancelLocation) notification that the subscriber has been moved to another VLR. The active status does not necessarily mean that the subscriber is roaming under this VLR and the HLR stores the address of this VLR. The same subscriber's status can be active in more than one VLRs. The passive status means that the subcriber is not roaming under the VLR, but its data is retained for later usage.
Previous LAI
The mobile station sends this number to the network when an access request is initiated.
Nokia Terminal External network element which provides automatic configuration of the mobile Management Server equipment and of the user capability information for the MMSC during multimedia sessions. Triggering
Indication to the Mobile Terminal Management Server to start the automatic configuration.
Trigger SM
Short message generated by the MSC after a successful event.
Common MSISDN/CLI
The number which is 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 the subscriber(s).
Own MSISDN
The number which belongs to the primary basic service and uniquely identifies the subscriber in the HLR. The HLR can optionally use this number towards the VLR/SGSN in the location update procedure.
Time stamp
It is information added to a record or other form of data showing the date and time it was processed and possibly the user.
30 (30)
© Nokia Corporation Nokia Proprietary and Confidential
DN01170933 Issue 3-2 en
DN01170933 Issue 3-2 en
© Nokia Corporation Nokia Proprietary and Confidential
1 (30)
FEATURE 1433 Terminal Management Support
The information in this documentation 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's customers only for the purposes of the agreement under which the documentation is submitted, and no part of it may be reproduced or transmitted in any form or means without the prior written permission of Nokia. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia 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 cannot be considered binding but shall be defined in the agreement made between Nokia and the customer. However, Nokia has made all reasonable efforts to ensure that the instructions contained in the documentation are adequate and free of material errors and omissions. Nokia will, if necessary, explain issues which may not be covered by the documentation. Nokia's liability for any errors in the documentation is limited to the documentary correction of errors. NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDING MONETARY LOSSES), that might arise from the use of this documentation or the information in it. This documentation and the product it describes are considered protected by copyright according 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 respective companies, and they are mentioned for identification purposes only. Copyright © Nokia Corporation 2005. All rights reserved.
2 (30)
© Nokia Corporation Nokia Proprietary and Confidential
DN01170933 Issue 3-2 en
Contents Contents 3 List of tables 4 List of figures 5 1
Introduction 7
2
Benefits for the operator 9
3 3.1 3.1.1 3.1.2 3.1.3 3.2 3.2.1 3.2.2 3.2.3 3.2.4 3.2.5 3.2.6 3.3 3.4 3.5 3.6
Description of the feature 11 Requirements for using the feature 11 Software 11 Hardware 11 Products 11 Functionality 12 General 12 Additional information 14 Files 16 Parameters 17 Statistics 18 Charging 18 Capacity 18 Restrictions 18 Related and interworking features 19 Compliance 19
4 4.1 4.1.1 4.1.2 4.2 4.3
Interfaces 21 Operator interfaces 21 MMLs 21 Alarms 23 Subscriber interfaces 23 External interfaces 23
5
Main changes in the feature 25 References 27 Glossary 29
DN01170933 Issue 3-2 en
© Nokia Corporation Nokia Proprietary and Confidential
3 (30)
FEATURE 1433 Terminal Management Support
List of tables Table 1.
4 (30)
Trigger SM parameters
13
© Nokia Corporation Nokia Proprietary and Confidential
DN01170933 Issue 3-2 en
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
DN01170933 Issue 3-2 en
© Nokia Corporation Nokia Proprietary and Confidential
5 (30)
FEATURE 1433 Terminal Management Support
6 (30)
© Nokia Corporation Nokia Proprietary and Confidential
DN01170933 Issue 3-2 en
Introduction
1
Introduction The configuration of the mobile equipment, for which the Nokia Terminal Management Server (NTMS) can provide additional services, consists of two stages: 1.
Identifying the mobile equipment that needs configuration update and supports automatic configuration.
2.
Sending the new settings to the mobile equipment, for example in a Short Message Service (SMS) or Wireless Application Protocol (WAP) Push message.
This feature provides support for the first stage by gathering and sending the subscriber-mobile terminal associations to the NTMS. This enables the NTMS to select and configure the relevant mobile stations automatically, that is, in such a way that the subscriber or the operator does not have to enter the data into the equipment 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 the NTMS can download later through File Transfer Protocol (FTP). The gathering process of data takes place once a day at a configurable time. The NTMS gets information 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 services Switching Centre (VMSC) detects an event, it sends a trigger to the NTMS. These triggers are sent in SMS, since the NTMS has a direct connection to the Short Message Service Centre (SMSC). The VMSC sends a trigger immediately in the following cases:
DN01170933 Issue 3-2 en
•
when an International Mobile Equipment Identity (IMEI) change is detected
•
when a roamer arrives from a foreign country
•
when a subscriber makes an inter-VLR location update and the previous location of the user is one of the configured LAIs
© Nokia Corporation Nokia Proprietary and Confidential
7 (30)
FEATURE 1433 Terminal Management Support
Feature 1433: Terminal Management Support supports the International Mobile Equipment Identity Software Version (IMEISV) in batch file and real time triggering. This feature also provides pre-filtering possibilities, which decrease the amount of 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 or home subscribers, or if this granularity is not enough, filtering can be done on IMSI range basis as well.
•
Mobile equipment phase It can be used to send information to the NTMS only about equipments with 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 special previous location).
The VMSC sends both the common MSISDN and the own MSISDN to the NTMS, 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.
8 (30)
© Nokia Corporation Nokia Proprietary and Confidential
DN01170933 Issue 3-2 en
Benefits for the operator
2
Benefits for the operator Feature 1433: Terminal Management Support is essential for the efficient functioning of the Nokia Terminal Management Server (NTMS) 1.0 and Nokia Terminal 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 foreign country
The Real Time (RT) functionality makes it possible to detect these events immediately when they take place. This feature enables the operator to increase the profit, since it allows the automatic 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 sending both the own and common MSISDN to the NTMS. With this feature it is possible to send the subscriber's data of HPLMN1 only to the NTMS of HPLMN1 if the operator controls two home networks with different NTMSs for each network. When the operator uses both the batch file creation and real time triggering, the latest data is shown by using the time stamp.
DN01170933 Issue 3-2 en
© Nokia Corporation Nokia Proprietary and Confidential
9 (30)
FEATURE 1433 Terminal Management Support
10 (30)
© Nokia Corporation Nokia Proprietary and Confidential
DN01170933 Issue 3-2 en
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
3.1.3
•
The feature requires 32 MB free disk space on the Operation and Maintenance Unit (OMU) disk for the I-series Mobile Services Switching Centre (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.
Products The feature is implemented for both i-series MSC/VLRs and subrack MSC/VLRs.
DN01170933 Issue 3-2 en
© Nokia Corporation Nokia Proprietary and Confidential
11 (30)
FEATURE 1433 Terminal Management Support
3.2
Functionality
3.2.1
General Batch file transfer
The VLR generates one file per one VLRU, which contains the subscribers' own MSISDN, IMEI, International Mobile Subscriber Identifier (IMSI), and common MSISDN (if available) numbers. Only those subscribers' data is included in the file who have valid IMEI number. Furthermore, the VLR can filter the data based on the subscribers' home PLMN. During the process of data gathering for the NTMS, the VLR scans through the subscriber database the same way as in the VLR cleaning procedure. You can set the 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 the start of the VLR cleaning and the data gathering process, regardless of which procedure takes place first. The files are stored on the OMU disk. The NTMS can download the files using FTP. After that the NTMS filters the downloaded data. It ignores the irrelevant data entries (for example, those own MSISDN, IMEI, IMSI, and common MSISDN numbers that belong to older-generation mobile stations that cannot use the services provided by the NTMS), and carries out further processing of the relevant data in order to configure the appropriate (new) mobile equipment. After that the NTMS sends the automatic configuration data, for example, the WAP 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 information and the data in the record structure. Real Time triggering
When the VMSC receives a location update or an access request from a subscriber and 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 in the MSC-SMSC interface, the operator can control which type of event to detect and 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.
12 (30)
© Nokia Corporation Nokia Proprietary and Confidential
DN01170933 Issue 3-2 en
Description of the feature
Table 1.
Trigger SM parameters
Event detection
Value (HEX)
IMEI changes in the VMSC database (IMEI)
01
Inter PLMN location update of a new visitor (PLMN)
02
New visitor with special previous LAI value (NV LAI)
03
Filtering criteria
Activation status by default
Home/visitor subscriber
Active
MS-classmark Home/visitor subscriber
Not active
MS-classmark Home subscriber
Not active
MS-classmark
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 HOME subscribers, only VISITOR subscribers, or both of them are detected.
•
The inter-PLMN location update event refers to a subscriber who has just come home from a foreign country. National roamers are not detected.
•
The New_visitor_with_special_previous_LAI_value event indicates a new subscription in the network, but it can also be used after an unsuccessful location update.
With the configurable UTPFIL parameter, it is possible to set four different kinds of initial values (location area codes) for the New_visitor_with_special_previous_LAI_value event. The VMSC application reads the UTPFIL parameters, and if one of them is the same as the Location Area Code (LAC) sent by the mobile station, the trigger functionality can be started. The Mobile Country Code (MCC) and Mobile Network Code (MNC) of the previous LAI must match with the Home PLMN's MCC 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' field contains the subscriber's own MSISDN, IMEI or IMEISV, IMSI, and common MSISDN number in ASCII characters. The following figure shows the structure of the user data.
Note Separate the numbers with spaces.
DN01170933 Issue 3-2 en
© Nokia Corporation Nokia Proprietary and Confidential
13 (30)
FEATURE 1433 Terminal Management Support
MSC_36209956524_490523102400750_21601585458_PLMN_3620700000 Flag +
MSISDN
+
Figure 1.
IMEI(SV)
+
IMSI
+Detected+COMMON MSISDN event
Trigger TP-User-Data field
Note TP-User data is coded as 8 bit ASCII characters. If the subscriber does not have a common MSISDN number, the Detected_event is 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 a commonly used A-MSISDN (TMSISDN) and A-IMSI (CIMSI) numbers as the sender of the created mobile-originated SM (A number). The trigger MO-SM is sent towards a specific SMSC and SMSC application address. The NTMS receives it directly from the specific SMSC application. As for the remaining triggers, the NTMS gets them when it downloads the batch files from 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 those subscribers 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 are more 'home networks' inside your Circuit Switched (CS) core network. If this functionality is active, the 'HOME_VISITOR' parameter has no effect.
14 (30)
© Nokia Corporation Nokia Proprietary and Confidential
DN01170933 Issue 3-2 en
Description of the feature
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 functionality point of view.
•
The MSISDN-IMEI-IMSI list for NTMS file is not encoded on the OMU disk. You have to use a secure internal network or ensure the security with an external function.
•
If the VLR cleaning process and the data gathering for the NTMS take place on the same night, run the gathering process first.
•
The COCEN card is required to download the MSISDN-IMEI-IMSI list for the NTMS file through the TCP/IP link in the subrack MSC. The COCEN card can be configured with the WTP command.
•
For transfer through TCP/IP, the COCEN plug-in unit is necessary to build a connection in the subrack mechanism, or a CP6LX-S processor card is needed with built-in LAN interface.
•
If the Super-Charger feature is used, the VLR database contains active and passive subscriber data. The batch files produced for the NTMS include only the active subscribers' data. Even in this case the NTMS can receive the same subscriber's data from more VLRs, because the subscriber may be in an active state in more than one VLRs. The received data can also be conflicting. On the other hand, due to the on demand cleaning method, the VLR may remove the active subscriber before it produces the batch files.
Real Time triggering
DN01170933 Issue 3-2 en
•
If you set the MSC to send a trigger SM in the case of an inter-PLMN location update inside the same VMSC, the NTMS has to filter out the unnecessary inter-system location update triggers (from the UMTS towards the GSM).
•
The NTMS can notice the new equipment and the subscriber with maximum one day delay.
•
The RT triggering functionality does not generate a trigger SM when the user switches off the mobile station under VMSC1, then puts the SIM card to a new mobile station and switches ON the mobile station under VMSC2.
© Nokia Corporation Nokia Proprietary and Confidential
15 (30)
FEATURE 1433 Terminal Management Support
•
The Real Time triggering functionality does not generate two trigger SMs when two users change mobile stations. When user 1 makes the location update, a trigger SM is generated and it deletes the IMEI number from user 2 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 SM when a General Packet Radio Service (GPRS) subscriber makes a location update through the Serving GPRS Support Node (SGSN) since the IMEI number 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 need to send a special MO-SM. If the subscriber is a multi-SIM user, the same multiSIM common ISDN number is used in the network. With this feature, the MSC can recognise those self-provisioning MO-SMs that are sent to the NTMS based on the called subscriber number and thus the MSC does not exchange the subscriber's own MSISDN number to the multi-SIM common ISDN number. Skip SMS deny in NTMS SMS case
When the Feature 1545 and 1576 Sequential and Parallel Alerting is active, the operator can set the SMS-Deny flag in member level in order to ignore all the MTSMs that arrive with own MSISDN number and allow only MT-SMs send to the Group number. This is problematic when the application server wants to send MT-SM to the subscriber's own MSISDN number. To solve this problem the GMSC compares the address of the sender application received in the MT-SM to the PROVAC parameter in order to recognise those MTSMs. If so, the MSC sets the MEMBER INTERROGATION and CFUSMCFO flag in SRI_FOR_SM (Nokia propriatery extension) in order to inform the HLR about the SM coming from an application. When the HLR gets this indication it does not check the Deny Direct SM parameter and SM forwarding from the subscriber 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 MSISDN numbers are copied to the new MSISDN-IMEI-IMSI list for NTMS files. The files are located on the OMU disk in the ASWDIR/NTMS subdirectory. There are as many files as VLR units. Each VLRU creates its own MSISDNIMEI-IMSI list for the NTMS file. The file names are LMTMS0.LST, LMTMS1.LST, … , and LMTMS7.LST.
16 (30)
© Nokia Corporation Nokia Proprietary and Confidential
DN01170933 Issue 3-2 en
Description of the feature
The files are binary and contain records separated by '0xEE'. The records consist of 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 11 bytes) 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 is approximately 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 those subscribers' data who come from the selected PLMN. New flexible file structure is introduced that contains file header information and record elements. The new file structure contains the actual system time to solve cooperation 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 the
common MSISDN/CLI is provided to the NTMS or not. NTMS_SELF_PROV_SM_USED (031:0051) By using this parameter, the MSC sends the own MSISDN number in self-provisioning SMs towards the NTMS, even though the Multi-SIM feature is active and the subscriber is a multi-SIM user. NTMS_SKIP_SM_DENY (031:0055) This parameter can be used so the application-originated SM can be sent to own MSISDN number of the subscriber even if the SMS_DENY functionality is active in the HLR. When this parameter is active, the SMS forwarding is also overriden in the HLR. NTMS_FLEXIBLE_FILE (031:0053) The PRFILE parameter defines whether the new flexible file structure or the old file structure is used in the MSC/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 and
deactivation. NTMS_REAL_TIME_SM_ACTIV (031:0049) This parameter controls the activation and deactivation of the Real Time triggering part of the feature. NTMS_PLMN_SPEC_FILT (002:0942) The PLMN-specific filtering functionality can be controlled with this parameter.
DN01170933 Issue 3-2 en
© Nokia Corporation Nokia Proprietary and Confidential
17 (30)
FEATURE 1433 Terminal Management Support
3.2.5
Statistics Real Time triggers are reported as trigger SMs in the Field Reporting Service Measurement 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 Bus between 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/IP link, 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 international roamers, the number of Trigger SMs can increase significantly in the MSCs that serve 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
18 (30)
•
It is recommended to run the process of data gathering for the NTMS in low traffic hours.
•
For the MSCi, provide 23-MB disk space for the eight new files on the OMU 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 VLR cleaning 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 SMs can increase. If so, the load is not significant.
© Nokia Corporation Nokia Proprietary and Confidential
DN01170933 Issue 3-2 en
Description of the feature
Real Time triggering
•
3.5
After a VMSC restart, the amount of trigger SMs may also increase because of the previous unsuccessful location updates of the subscribers. Therefore, it is advised to switch off the New_visitor_with_special_previous_LAI_value parameter after a VMSC restart for at least one location update period.
Related and interworking features The file processing application was implemented in Nokia Terminal Management Server 1.0. The real time processing application was implemented in Nokia Terminal 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 be provided to the NTMS. For more information, see Feature 1541: Same CLI for Multiple Subscribers, Feature Description.
•
Super-Charger If the Super-Charger feature is used, the VLR database contains active and passive 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 the NTMS_SKIP_SM_DENY PRFILE parameter is set, the 'SMS deny flag'
function can be overwritten if the SMS comes from a special application (for example, NTMS). For more information, see Feature 1545 and 1576: Sequential and Parallel Alerting, Feature Description.
3.6
Compliance The feature is Nokia-specific. This feature is supported in 3G.
DN01170933 Issue 3-2 en
© Nokia Corporation Nokia Proprietary and Confidential
19 (30)
FEATURE 1433 Terminal Management Support
20 (30)
© Nokia Corporation Nokia Proprietary and Confidential
DN01170933 Issue 3-2 en
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
DN01170933 Issue 3-2 en
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 process that is designed to create the MSISDN-IMEI-IMSI list for the MTMS 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 process for the NTMS. It is recommended to run the data gathering process first, before the VLR cleaning process. Use the INTER PLMN LOCATION UPDATE (INPLU) parameter to set if the VMSC has to generate a trigger SM when a home subscriber comes back from a foreign country and when a foreign subscriber arrives in the network. Use the NEW VISITOR WITH SPECIAL PREVIOUS LAI VALUE (NVLAI) parameter to set if the VMSC has to generate a trigger SM when new subscribers first switch on their MS. If this functionality is activated, a trigger SM is also generated when subscribers move to a different VLR area and their previous LAI is one of the preconfigured values. The HOME VISITOR (RSTAT) parameter makes it possible that only HOME subscribers, only VISITOR subscribers, or both of the above are detected. Use the MS CLASSMARK (MSCLASS) parameter to set the minimum revision level (phase 1, phase 2, and so on) of the mobile stations to be detected.
© Nokia Corporation Nokia Proprietary and Confidential
21 (30)
FEATURE 1433 Terminal Management Support
MXO
MXP
MXN
Output VLR parameters Use this command to display the current values of VLRspecific parameters and to display the start time of the process of data gathering for the NTMS. Output PLMN parameters Use this command to display the current parameter values of one PLMN. Modify PLMN parameters. Use this command to modify PLMN parameters. With the TRIGNTMS parameter you can define whether the subscribers who belong to that PLMN have to be detected or not. Use the PLMN-SPECIFIC FILTERING parameter to send only those subscribers' data in Real Time Trigger SM who belong to a specific PLMN. Either PLMN-specific filtering is active, or the HOME/VISITOR parameter is active.
For further information, see VLR and PLMN Parameter Handling, MX Command Group. GSM Network and Network Element Specific Number Handling, WV Command Group
WVS
WVR
WVI
22 (30)
Create network and network element-specific number Use the SMSC ADDRESS FOR TRIGGER SM (TRIGSC) parameter to set the specific SMSC address for the trigger SM. Use the SMSC APPLICATION FOR TRIGGER SM (TRIGAC) parameter to set the specific SMSC application address (B number) for the trigger SM. Use the APPLICATION ADDRESS OF PROVISIONING (PROVAC) parameter to set the specific external application address 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. Delete network and network element-specific number Use the DELETE NETWORK AND MSC/HLR SPECIFIC NUMBER parameter to delete a specific SMSC address, SMSC application address, common MSISDN, common IMSI number from the real time triggers. Interrogate network and network element-specific number Use the INTERROGATE NETWORK AND MSC/HLR SPECIFIC NUMBER parameter to interrogate a specific SMSC address, SMSC application address, common MSISDN, common IMSI number of the real time triggers.
© Nokia Corporation Nokia Proprietary and Confidential
DN01170933 Issue 3-2 en
Interfaces
WVF
Modify network and network element-specific number Use the MODIFY NETWORK AND MSC/HLR SPECIFIC NUMBER 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 interfaces This feature only provides subscriber-specific information to the NTMS, which provides the subscribers.
4.3
External interfaces The feature affects the following interfaces of the MSC/VLR:
FTP
NTMS
MSC/VLR
LMTMS0.LST...LMTMS7.LST
Figure 2.
NTMS
Network elements involved in batch file sending functionality
SM
SMSC
Direct connection
Figure 3.
DN01170933 Issue 3-2 en
SM
IWMSC
SM
VMSC
Short Message generated
Network elements involved in Real Time functionality
© Nokia Corporation Nokia Proprietary and Confidential
23 (30)
FEATURE 1433 Terminal Management Support
24 (30)
© Nokia Corporation Nokia Proprietary and Confidential
DN01170933 Issue 3-2 en
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
DN01170933 Issue 3-2 en
•
Information on the batch files produced for the NTMS has been added.
•
Visitor subscriber has been removed as the filtering criteria for the 'new visitor 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.
© Nokia Corporation Nokia Proprietary and Confidential
25 (30)
FEATURE 1433 Terminal Management Support
26 (30)
© Nokia Corporation Nokia Proprietary and Confidential
DN01170933 Issue 3-2 en
References
DN01170933 Issue 3-2 en
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 Activation Manual
5.
Feature 1541: Same CLI for Multiple Subscribers, Feature Description
6.
Feature 1545 and 1576: Sequential and Parallel Alerting, Feature Description
7.
Feature 1627: Super-Charger, Feature Description
© Nokia Corporation Nokia Proprietary and Confidential
27 (30)
FEATURE 1433 Terminal Management Support
28 (30)
© Nokia Corporation Nokia Proprietary and Confidential
DN01170933 Issue 3-2 en
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
DN01170933 Issue 3-2 en
© Nokia Corporation Nokia Proprietary and Confidential
29 (30)
FEATURE 1433 Terminal Management Support
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
Terms Active or passive subscriber
A VLR that supports the Super-Charger feature considers the subscriber active until it receives a (SendIdentification or CancelLocation) notification that the subscriber has been moved to another VLR. The active status does not necessarily mean that the subscriber is roaming under this VLR and the HLR stores the address of this VLR. The same subscriber's status can be active in more than one VLRs. The passive status means that the subcriber is not roaming under the VLR, but its data is retained for later usage.
Previous LAI
The mobile station sends this number to the network when an access request is initiated.
Nokia Terminal External network element which provides automatic configuration of the mobile Management Server equipment and of the user capability information for the MMSC during multimedia sessions. Triggering
Indication to the Mobile Terminal Management Server to start the automatic configuration.
Trigger SM
Short message generated by the MSC after a successful event.
Common MSISDN/CLI
The number which is 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 the subscriber(s).
Own MSISDN
The number which belongs to the primary basic service and uniquely identifies the subscriber in the HLR. The HLR can optionally use this number towards the VLR/SGSN in the location update procedure.
Time stamp
It is information added to a record or other form of data showing the date and time it was processed and possibly the user.
30 (30)
© Nokia Corporation Nokia Proprietary and Confidential
DN01170933 Issue 3-2 en
Related Documents
Real Time Trigger Feat 1433
November 2019 2
1433
November 2019 3
Real Time
July 2020 60
New Feat New Feat
December 2019 3
Trigger
November 2019 31