Академический Документы
Профессиональный Документы
Культура Документы
The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia Siemens Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Siemens Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the process of continuous development and improvement of the documentation. The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given "as is" and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document. Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT. This documentation and the product it describes are considered protected by copyrights and other intellectual property rights according to the applicable laws. The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia Corporation. Siemens is a registered trademark of Siemens AG. Other product names mentioned in this document may be trademarks of their respective owners, and they are mentioned for identification purposes only. Copyright Nokia Siemens Networks 2009/11/4. All rights reserved
The same text in German: Wichtiger Hinweis zur Produktsicherheit In elektrischen Anlagen stehen zwangslufig bestimmte Teile der Gerte unter Spannung. Einige Teile knnen auch eine hohe Betriebstemperatur aufweisen. Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Krperverletzungen und Sachschden fhren. Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die Anlagen installiert und wartet. Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene Gerte mssen die zutreffenden Sicherheitsbestimmungen erfllen.
Table of Contents
This document has 40 pages. 1 2 2.1 2.2 2.3 2.4 2.4.1 2.4.2 2.4.3 2.4.4 2.4.5 2.4.6 2.4.7 2.4.8 2.5 2.6 2.6.1 2.6.2 2.6.3 2.6.4 2.6.5 2.7 2.7.1 2.7.2 2.7.3 2.7.4 2.7.5 2.7.6 2.7.7 2.7.8 2.8 2.8.1 2.8.2 2.8.3 3 3.1 3.2 3.3 3.4 3.5 3.6 Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Mobile Application Part (MAP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Network elements with MAP interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . Support protocol description of MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware requirements and software architecture of MAP . . . . . . . . . . . . MAP procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP location management procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP location service procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP operation and maintenance procedures. . . . . . . . . . . . . . . . . . . . . . . MAP call handling procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP supplementary service procedures . . . . . . . . . . . . . . . . . . . . . . . . . . MAP short message service procedures . . . . . . . . . . . . . . . . . . . . . . . . . . MAP security procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP subscriber information procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP signalling configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP general settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP overload control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP error counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SCCP return option for MAP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Number of authentication sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP operation timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Direction-specific MAP functionalities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multiple own network element addresses . . . . . . . . . . . . . . . . . . . . . . . . . . Prevention of MAP traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP version handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Direction-specific alarms related to MAP . . . . . . . . . . . . . . . . . . . . . . . . . . ANSI MAP - routing addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ANSI MAP - application context . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SMSC types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP traffic status information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP-related clear and event codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . MAP cyclic buffer for erroneous protocol messages. . . . . . . . . . . . . . . . . . MAP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Handling MAP statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting a fixed destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting a fixed destination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Starting counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Displaying counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Stopping counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Checking how MAP traffic is currently proceeding . . . . . . . . . . . . . . . . . . . 10 10 11 12 13 13 14 15 15 16 16 17 17 17 19 19 20 20 20 21 21 21 23 23 23 24 24 24 24 24 24 28 28 30 30 30 31 31 32 32
Id:0900d80580570e90
4 5 6 7 8 9
Defining the MAP version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Activating MAP error counters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Reading MAP cyclic buffer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 Modifying the own network element address . . . . . . . . . . . . . . . . . . . . . . . . 36 Denying MAP traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Configuring the default MAP parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Id:0900d80580570e90
List of Figures
Figure 1 Figure 2 Figure 3 The interfaces covered by MAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 MAP support protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 The MAP signalling configuration in the MSC and the HLR . . . . . . . . . 19
Id:0900d80580570e90
Id:0900d80580570e90
Summary of changes
1 Summary of changes
Changes made between issues 6-0 and 5-0 The company and product names have been changed according to the official Nokia Siemens Networks portfolio naming. Changes made between issues 5-0 and 4-2
Changes due to new features A new section about a new functionality SMSC types has been added to Chapter Direction-specific MAP functionalities due to the changes in the MultiCard SMS functionalities. Other changes As the description of the MAP statistics functionality has been changed and in order to clearly separate the following issues: general settings that affect the MAP protocol layer functionality direction-specific settings that affect the MAP protocol layer functionality other MAP related information which the operator can handle, but which does not affect the MAP protocol layer functionality MAP general settings Direction-specific MAP functionalities MAP traffic status information
Changes due to new features As an enhancement, the Multiple Own Network Element Addresses feature can be used to divide the HLR to multiple virtual HLRs by showing different Global Title (GT) numbers outside the HLR. This division is done on IMSI basis. You can create analyses for IMSI ranges to specify which HLR number is used with certain IMSIs. Thus, you can configure one HLR address for a certain subscriber area in the Nokia HLR. The following sections have been updated with these enhancements: Direction-specific MAP functionalities Modifying the own network element address
Changes due to new features No changes. Other changes Minor editorial corrections have been made.
Id:0900d80580570e6e
Summary of changes
Changes due to new features The following sections have been modified due to changes in the Multiple Own Network Element Addresses feature: Direction-specific MAP functionalities A new subsection has been added about the own network element address modification. Modifying the own network element address A new operating instruction section has been added.
The CAMEL Phase 2 Functional Subset in SSP feature has brought two new subscriber information procedures: AnyTimeInfoHandling SubscriberDataModificationNotification
Other changes The Figure Interfaces covered by MAP has been enhanced. Further details have been added to the Subsection MAP overload control. A new subsection has been written on MAP timers: MAP operation timers New operating instruction sections have been added: Configuring the default MAP parameters Denying MAP traffic
Interfaces using MAP protocol Figure The interfaces covered by the MAP modified: Ls and Lv interfaces removed, M interface added. Support protocol description of MAP SIGTRAN mentioned as a replacement of MTP. Software architecture of MAP Pairs: GMSC SGNS, MSC-A MSC-B, MSC-A MSC-B', and VLR gsmSCF have beed added to the list of MAP dialogues. Clear Codes related to MAP Clear Code '0410 GT ANALYSIS FAILED' added to the list of Clear Codes related to MAP. The MAP related clear and event codes have been moved to Chapter 2. Alarms related to MAP The list of alarms related to MAP has been removed from this document. It can be found in Failure Printouts. Changes made between issues 20 and 10
Id:0900d80580570e6e
Summary of changes
Introduction to Mobile Application Part References to MAP interfaces, which are not implemented in Nokia M11 were removed. New interface added (M interface for MM notification). New MAP procedures and a section on MAP Subscriber information procedures added. MAP general settings New heading. New section on Direction specific MAP functionalities added. Information on ANSI MAP routing addresses, SCCP return option for MAP and Authentication sets of MAP added.
Id:0900d80580570e6e
2.1
MAP is implemented as specified by ETSI and its successor 3GPP. Compatibility between different network elements provided by different vendors has been proven in a number of networks in inter-PLMN roaming cases and also in intra-PLMN cases, where Nokia Siemens Networks is one of the two or more equipment suppliers. Interfaces using MAP protocol The following interfaces are covered by MAP:
Figure 1
10
Id:0900d80580570e78
between the MSC and the HLR, for example, routing information inquiries for Mobile-Terminated (MT) calls between the VLR and the HLR, for example, location update, subscriber data management between two MSCs, for example, handovers, Mobile-Originated (MO) and Mobile-Terminated (MT) short messages between the MSC and the Equipment Identity Register (EIR), International Mobile Equipment Identity (IMEI) status checking between the two VLRs, International Mobile Subscriber Identity (IMSI), and authentication triplet retrievals from the previous VLR between the HLR and the GGSN, mobile terminated PDP context activation. This interface has not been implemented between the SMS-GMSC and the Serving GPRS Support Node (SGSN), for example General Packet Radio Service (GPRS) short messages between the EIR and the SGSN, GPRS IMEI checking between the HLR and the SGSN, for example, GPRS location update between the HLR and the gsmSCF, for example, Unstructured Supplementary Service Data (USSD) or any time handling of subscriber data between the MSC and the GSM Service Control Function (gsmSCF), supplementary service notification between the HLR and the Gateway Mobile Location Centre (GMLC), location services between the MSC and the GMLC, location services between the VLR and the gsmSCF, Mobility Management (MM) notification
2.2
Message Transfer Part (MTP) is the foundation on which SS7 is built. Signalling Connection Control Part (SCCP) enables the placement of signalling messages in the correct order at the distant end (connection-oriented network service) and signalling across multiple networks in the absence of a call (connectionless network service). MAP uses only the connectionless services of the following SCCP: Class 0 Class 1 Basic connectionless class Sequenced connectionless class
Transaction Capabilities Application Part (TCAP) handles the MAP transaction messages between different network elements. MAP uses the SCCP's services through TCAP.
Id:0900d80580570e78
11
The IETF Signalling Transmission (SIGTRAN) protocol stack (M3UA, SCTP, IP) can replace the MTP to transfer SS7 signalling over IP networks.
Figure 2
When one network element that has MAP operates with another network element, both elements have to have the above-mentioned protocol stack, that is, MAP, TCAP, SCCP, and MTP. A network element can also serve as an Signalling Transfer Point (STP) between other network elements when it only transmits signalling from one element to another. In this case, the STP can only have an MTP, or an MTP and an SCCP even if the other network elements also have MAP.
2.3
The MAP implementation contains network element dependent functions of the MAP interface. These functions are called MAP Application Service Elements (ASEs). Each MAP ASE is able to handle the user interface and the required dialogues. The MAP program of the MSC controls MAP dialogues between:
12
Id:0900d80580570e78
the pair of Visited MSC (VMSC) and Short Message Service Interworking MSC (SMS-IWMSC) the pair of VMSC and SMS Gateway MSC (SMS-GMSC) the pair of VMSC and gsmSCF the pair of VMSC and GMLC the pair of SMS-GMSC and HLR the pair of GMSC and HLR the pair of VMSC and EIR the pair of SMS-GMSC and SGSN the pair of SMS-IWMSC and SGSN the pair of anchor MSC (MSC-A) and MSC-B the pair of MSC-A and MSC-B' the pair of VLRs the pair of VLR and HLR the pair of VLR and Authentication Centre (AUC) the pair of VLR and gsmSCF the pair of HLR and VLR the pair of HLR and GMSC the pair of HLR and SMS-GMSC the pair of HLR and SGSN the pair of HLR and gsmSCF the pair of HLR and GMLC the pair of AUC and VLR the pair of EIR and VMSC the pair of EIR and SGSN
2.4
MAP procedures
A MAP procedure is a service offered by MAP. The procedure defines the operations that can be used in a given transaction. The procedures are described here only briefly, and the operations are not presented. For more information, see the MSC/VLR-HLR/EIR/MSC/VLR/GMLC/gsmSCF Mobile Application Part, Interface Specification and the HLR/EIR-MSC/VLR/SGSN/gsmSCF/GMLC Mobile Application Part, Interface Specification.
2.4.1
Id:0900d80580570e78
13
Location update The location update procedure is used to update location information held in the network. Location information is used to route incoming calls, packet data, short messages, and USSD to a roaming subscriber. The MAP_UPDATE_GPRS_LOCATION service is used by the SGSN to update the location information stored in the HLR. Location cancellation The purpose of the procedure is to delete the subscriber's record from the previous VLR after the subscriber has registered in a new VLR. The procedure can also be used if the subscriber's record has to be deleted for other operator-determined purposes, for example, withdrawal of subscription. This service is also used between the HLR and the SGSN to delete a subscriber record from the SGSN. The service can be invoked automatically when a Mobile Station (MS) moves from one SGSN area to another, to remove the subscriber record from the old SGSN, or by the HLR operator to enforce a location update from the SGSN to the HLR. Mobility management event reporting This procedure is used to notify the gsmSCF about a subscriber's change of location. The procedure is triggered by, for example, location update. MS purging An MS record is to be purged either because of an administrative action, or because the MS has been inactive for an extended period. After the purging, any request for routing information for a mobile-terminated call or a Mobile-Terminated Short Message (MTSM) is treated as if the MS is not reachable. This service is also used between the SGSN and the HLR to cause the HLR to mark its data for an MS, so that any request for routing information for a mobile-terminated short message or a network-requested PDP context activation is treated as if the MS is not reachable. Handover When an MS moves from one MSC area to another during a transaction, the handover procedure has to be performed in order to continue communication. For that purpose, the MSCs involved have to exchange data to initiate and then to realise the operation. Fault recovery After a fault in a location register, the fault recovery procedures ensure that subscriber data in the VLR or in the SGSN become consistent with the subscriber data stored in the HLR for the given MS. It also ensures that location information in the HLR, VLR, and SGSN shows accurately the current location of the MS. There are two fault recovery procedures: VLR restoration HLR restoration
2.4.2
14
Id:0900d80580570e78
between the GMLC and the HLR to retrieve routing information needed for routing a location service request to the servicing VMSC by the GMLC to request the location of a target MS from the VMSC by the VMSC to provide the location of a target MS to the GMLC when the request for location is either implicitly administered or made at some earlier time
2.4.3
Subscriber data management procedures Subscriber deletion In the subscriber deletion procedure, the subscriber data has to be removed from the VLR and the HLR. Subscriber data modification In the subscriber data modification procedure, subscriber data is modified in the HLR, and when necessary, also in the VLR or in the SGSN.
Subscriber identity procedure In the subscriber identity procedure, the IMSI of a subscriber is retrieved from the HLR.
2.4.4
Id:0900d80580570e78
15
2.4.5
2.4.6
16
Id:0900d80580570e78
2.4.7
2.4.8
2.5
Id:0900d80580570e78
17
sequence, MAP and all the underlying protocols have to be appropriately defined in the whole network area. SCCP routing plays a significant role in the GSM network configuration. In Figure The MAP signalling configuration in the MSC and the HLR, you can see that if you use routing on Subsystem Number (SSN), a more static definition has to be made in both the new network element and all the other elements where routing on SSN is defined towards the new element (all the SPC definitions and corresponding SSN definitions). If routing on Global Title (GT) is used in all cases (which is preferable), emphasis is on GT translation definitions. Although more analyses are needed when routing on GT is used, the resulting flexibility gives the network a much better upgrade ability. If routing is based on the GT, the actual routing happens at SCCP and MTP level. If the routing is based on SSN, it is performed only by the MTP. For more information on SCCP addressing, see SCCPaddressing (GT or SPC/SSN) in Common Channel Signalling (MTP, SCCP and TC).
18
Id:0900d80580570e78
Figure 3
For more information on configuration, see Introductionto MSC and HLR integration in MSC and HLR Integration.
2.6
2.6.1
Id:0900d80580570e78
19
For incoming dialogues, the default behaviour is that MAP uses the ticket service. The usage of the ticket service can be deactivated. If the ticket service is used, the overloading events are discarded as the default functionality. As a configurable option, MAP can also inform the requesting network element about the overload situation by sending a TC-ABORT back to the network. The decision as to which events may be discarded is based on the priorities of the application contexts. For incoming and outgoing dialogues, MAP protects its own unit from overload, when the number of unhandled dialogue initiations exceeds a predetermined threshold. For detailed information, see Section MAP interface in a CCSU of the MSC &VLR and MSC Server in Overload and Congestion Control ( MSC Server), Functional Description. For operating instructions, see Configuring the default MAP parameters.
2.6.2
2.6.3
2.6.4
20
Id:0900d80580570e78
By default, the returned amount of authentication sets is four. The maximum value with MAP version 1 is five. The maximum value with MAP version 2 is four. This is due to the limitations at the MTP level. If the response message is too long to fit in an MTP message, no information is delivered to the VLR/SGSN. The setting of these parameters has a meaning in the HLR affecting the SendAuthenticationInfo operation, and in the VLR affecting the SendIdentification operation. As to the SendIdentification operation between VLRs, maximum of three sets is sent in the response even if the configured value of the parameter is higher than three.
2.6.5
2.7
2.7.1
Id:0900d80580570e78
21
to the MSC/VLR. This means that the MSC/VLR has multiple own addresses and each partnering operator can associate its own MSC/VLR CgPA to its roaming subscribers. With this mechanism, SS7 signalling is routed from the roaming subscriber's core network back to the shared MSC/VLR through the correct core network. Thus, the SS7 signalling is routed correctly in core network sharing cases, and the SS7 signalling load is distributed evenly to the network sharing partners. Monitoring of signalling in core network sharing cases is easier as well, and the operator can make more flexible roaming agreements. The MAP protocol checks whether there is an address analysis for the Called Party Address (CdPA) and whether the result of that analysis is the new own network element address. The own address parameter is used on SCCP level and in some operations the new own network element addresses are also used as MAP message parameters. These operations are: UpdateLocation PurgeMS SubscriberLocationReport ProvideSubscriberInfo response AuthenticationFailureReport SendRoutingInfo NoteMM-Event
You can modify the value of the own network element address. The possible modification is based on the analysis of the SCCP level Called Party Address. As an enhancement, this feature can be used to divide the HLR to multiple virtual HLRs by showing different GT numbers outside the HLR. This division is done on IMSI basis. You can create an analysis for the IMSI (E.212) ranges to specify which HLR number is used with certain IMSIs. Based on the analysis, the analysis result can give a new HLR address. Thus, you can configure one HLR address for a certain subscriber area in the Nokia Siemens Networks DX HLR. If no analysis exists, the default number is used. The HLR address (in SCCP and in MAP level if the parameter exists) is changed in the following operations where a dialogue is initiated from the HLR: InsertSubscriberData DeleteSubscriberData CancelLocation ActivateTraceMode DeactivateTraceMode ProvideRoamingNumber ProvideSubscriberInfo UnstructuredSS-Request UnstructuredSS-Notify SS-InvocationNotification SetReportingState RemoteUserFree GetPassword AlertSC Reset In the HLR, you cannot configure the SCCP Calling Party Address for a message that contains Reset operation.
22
Id:0900d80580570e78
The MAP level HLR address is changed in the following result components of MAP operations: RestoreData result UpdateLocation result UpdateGPRSLocation result
The SCCP level address is changed in the first response message of the following network-initiated MAP dialogues: networkLocUpContext-v3, networkLocUp (v2,v1) infoRetrievalContext-v3,v2 gprsLocationUpdateContext-v3
2.7.2
2.7.3
2.7.4
MAP extensions
On the basis of the address analysis result, it is also determined whether the extensions for operations and their parameters are in use or not. The extensions are Nokia Siemens Networks-specific additions to MAP messages, and their use can be denied. The Nokia Siemens Networks-specific extension can only be used with Nokia Siemens Networks DX MSC/VLRs and HLRs. Usually, extensions sent by another vendor's network elements are not understood. They are ignored because their coding cannot be opened. However, if, for example, a foreign network sends extensions that are interpreted as extensions specific to the own PLMN and, therefore, may have unwanted effects, it can be helpful that all extensions sent from certain directions can be explicitly ignored. This applies also to the outgoing direction: the extensions are not sent.
g Do not deny the use of the extensions, because the denial can prevent the use of
Nokia Siemens Networks-specific applications and some operations.
Id:0900d80580570e78
23
2.7.5
2.7.6
2.7.7
2.7.8
SMSC types
The result of the address analysis can indicate an Short Message Service Centre (SMSC) type. This information is meaningful only when a SendRoutingInfoForSM or a ReportSM-DeliveryStatus operation (application context 20, shortMsgGatewayContext) is received from the network. The information about the SMSC type is forwarded by MAP to the HLR application, which uses the information in the business logic of the MultiSIM functionality.
2.8
2.8.1
24
Id:0900d80580570e78
Clear codes related to MAP Clear code 0005 B SUBSCRIBER BUSY Explanation 1. A subscriber is not able to receive an MobileTerminated Short Message (MT-SM) because the MS is busy receiving another MT-SM. 2. MAP sets the clear code if the BusySubscriber error is received from another network element and the error component does not contain any additional information. 0010 ABSENT SUBSCRIBER 0021 B-SUBSCRIBER BUSY, CCBS POSSIBLE The response received by the MSC/VLR is that an MS is not reachable. MAP sets the clear code if the BusySubscriber error is received from another network element with a CCBS-Possible indicator.
0022 B-SUBSCRIBER BUSY, CCBS NOT MAP sets the clear code if the BusySubscriber POSSIBLE error is received from another network element without a CCBS-Possible indicator. 0304 B-LINE OUT OF SERVICE MAP sets the clear code in the MSC/VLR when the incoming calls to a called subscriber have been barred by an operator. MAP sets the clear code in the MSC/VLR when a mobile subscriber has activated the supplementary service of incoming call barring. MAP sets the clear code in the MSC/VLR when data of a called MS cannot be found in the HLR. MAP sets the clear code in the MSC/VLR when the number of a called MS in the HLR has changed. 1. MAP sets the clear code in the MSC/VLR when the HLR has responded with a negative acknowledgement to the SendRoutingInfo operation with cause code CugReject without any additional information. 2. The SendRoutingInfo operation is rejected by MAP in the VLR because CUG information cannot be supported with the current MAP version. 0311 BEARER SERVICE NOT PROVISIONED The HLR has responded to the SendRoutingInfo operation that the bearer service is not provided. As a result, MAP sets the clear code in the MSC/VLR. The response received to an operation is that the teleservice is not provided.
Id:0900d80580570e78
25
Explanation MAP sets the clear code if the IllegalSubscriber error is received from another network element. The error is received from another network element.
0315 B SUBSCRIBER HAS CALL DIVER- The HLR has given a negative response to the SION BARRING SendRoutingInfo operation with cause code ForwardingViolation. 0319 ILLEGAL SUBSCRIBER STATION 031A INCOMING CALLS BARRED WITHIN THE CUG The error is received from another network element. The HLR has responded to the SendRoutingInfo operation that incoming calls have been barred within the CUG. As a result, MAP sets the clear code in the MSC/VLR.
031C SUBSCRIBER NOT A MEMBER OF The HLR has responded to the SendRoutingInfo THE CUG operation that a subscriber is not the member of CUG. As a result, MAP sets the clear code in the MSC/VLR. 031F REQUESTED BASIC SERVICE VIOLATES CUG CONSTRAINTS The HLR has responded to the SendRoutingInfo operation that the requested basic service violates CUG constrains. As a result, MAP sets the clear code in the MSC/VLR. The HLR has responded to the SendRoutingInfo operation that called party SS interaction violates within CUG. As a result, MAP sets the clear code in the MSC/VLR. Call control has sent the erroneous SendRoutingInfo request. As a result, MAP sets the clear code in the MSC/VLR. MAP sets the clear code when the attempt to start a MAP service has failed at a receiving end because of limited resources or congestion. MAP sets the clear code if the RoamingNotAllowed error is received from another network element. MAP sets the clear code if a notice that a message could not be delivered to a remote node is received from SCCP, and the notice contains a cause code indicating that address translation is missing. MAP sets the clear code if a CCSU is overloaded. The negative acknowledgement received to an operation from the other network element is FacilityNotSupported.
0320 CALLED PARTY SUPPLEMENTARY SERVICE INTERACTION VIOLATED WITHIN CUG 0405 ERRONEOUS REQUEST FROM CO-PROCESS 040C MAP CONGESTION
26
Id:0900d80580570e78
Explanation The negative acknowledgement received to an operation from another network element is SystemFailure. 1. MAP sets the clear code with an undefined reason. This cause is used as a default if none of the clear codes usually set by MAP is suitable. 2. The negative acknowledgement received to an operation from the other network element is DataMissing. 3. The negative acknowledgement received to an operation from another network element is UnexpectedDataValue. 4. An abort message has been received from the network. 5. A reject component has been received from the network. 6. There is a routing failure. A MAP message could not be routed to a destination network element. 7. TCAP resource limitation. 8. MAP has received an unexpected message from TCAP. 9. A MAP internal error. 10. No response has been received from the MSC. 11. No response has been received from the EIR. 12. No response has been received from the SCP.
MAP sets the clear code in the MSC/VLR when no response has been received from the HLR in the SendRoutingInfo operation. No response has been received from the VLR. An overload message has been received from the network.
Id:0900d80580570e78
27
Event codes related to MAP Event code 103E UNAUTHORIZED LCS CLIENT OR REQUEST Explanation 1. MAP sets the event code when it receives a negative acknowledgement from the GMLC with MAP error UnauthorizedRequestingNetwork. 2. MAP sets the event code when it receives a negative acknowledgement from the GMLC with MAP error UnknownOrUnreachableLCSClient.
2.8.2
2.8.3
MAP statistics
MAP statistics (MAP protocol measurement) is used to monitor the amount of incoming and outgoing MAP signalling messages. Gathered statistical information can be used, for example, in troubleshooting. Statistical data is gathered separately for different MAP interfaces. The interfaces are identified with the Subsystem Numbers (SSN) of the communicating MAP entities, for example, the HLR-VLR is identified as one interface. For every interface, there are 11 sets of counters. Each counter set is used for a different destination that is defined for using SPC or GT addresses. The destination addresses for up to 10 of the counter sets are manually configured by the operator. These 10 counter sets are used as fixed destinations, that is, a destination address can be given and then the counter set is reserved only for this specified destination. The 11th counter set is reserved for transactions which are to/from all other destinations, that means the destination address in the MAP signalling message is not one of the predefined ones.
28
Id:0900d80580570e78
The counter sets are divided into counters for dialogues (identified by the Application Context identifier), and for operations that are invoked during the dialogue (identified by the operation code). There are separate counters for incoming and outgoing MAP dialogues. This is necessary for making distinction between incoming and outgoing events in case of dialogues which are shown in the statistics between identical subsystems on both ends (for example, MSC-MSC or VLR-VLR). The following data is gathered for every dialogue (application context) and for the used dialogue version: total number of initiated dialogues total number of dialogues aborted by a local application total number of dialogues aborted by MAP layer at the own node total number of dialogues aborted by TC-P-Abort received from the network total number of dialogues aborted by TC-U-Abort received from the network total number of dialogues interrupted because of an operation timer expiration total number of dialogues interrupted because of an internal timer expiration total number of version fallbacks
One MAP dialogue contains one or more MAP operations. There are separate counters for incoming and outgoing MAP operations. This is needed because some operations are invoked between identical subsystems on both ends. The following data is gathered for every operation code and for the used dialogue version for the operation: total number of invoked operations total number of operations that resulted an error total number of operations that resulted an abort or reject total number of operations for which there was no response before an operation timer expiration
Id:0900d80580570e78
29
3.1
3.2
30
Id:0900d80580570e7b
Check the outcome (OXY) Display the destination list to check that the deleting process has been carried out successfully. Example Display the destination list containing all the fixed destinations from your MSC to the HLR. ZOXY:PROTOCOL=MAP:SNET=MSC:DNET=HLR;
3.3
Starting counters
Before you start The counters are started for only certain interfaces or for all interfaces (an interface is a combination of the own subsystem and the remote subsystem). If the counters are started for only certain interfaces, the measurement period is one hour and the counter report is stored to a file once an hour. If the counters are started for all interfaces, the measurement period is one day and the counter report is stored to a file every night, and also the cumulative counters for the day can be viewed with the OXL command. Steps 1 Display the measurement state (OXP) Example Display the MAP measurement state. ZOXP:PROTOCOL=MAP; 2 Start MAP meters if the measurement state is other than 'running' (OXS) Example Set the MAP meters for all interfaces to start on 15 August 2005 at noon. ZOXS:PROTOCOL=MAP:SDAY=20050815,STIME=1200;
3.4
Displaying counters
Before you start The counters are collected automatically from the signalling units to the centralized part once an hour on the full hour. After that the contents of the counters can be viewed either in the report file or with the OXL command. Steps 1 Display the MAP meters (OXL) Example Display general information on the MAP meters of signalling point code 76 that is located in NA0 common channel network and belongs to the HLR. ZOXL:PROTOCOL=MAP:SNET=MSC:DNET=HLR::CCNET=NA0,SPC=76::GEN;
Id:0900d80580570e7b
31
3.5
Stopping counters
Steps 1 Stop the MAP meters (OXE) Example Stop the MAP meters. ZOXE:PROTOCOL=MAP; The collecting of counter information from the distributed parts in each signalling unit is stopped and the counters are cleared in the distributed parts and in the centralized part.
3.6
32
Id:0900d80580570e7b
Id:0900d80580570e7e
33
34
Id:0900d80580570e81
Id:0900d80580570e84
35
36
Id:0900d80580570e87
Use the OPC MML command to create a network entity address analysis for determining the best MAP version, virtual MSC/VLR addresses, or virtual HLR addresses. The network entity address analysis for the virtual HLR address is only available in the HLR. Example (MSC/VLR) Create a network entity address analysis for the network entity with global title address 123456789, type of number NAT, and numbering plan E.164. ZOPC:TOA=GT:DIG=123456789,TON=NAT,NP=E164:RES=1,RESA=1; Example (HLR) Create a network entity address analysis for the network entity with global title address: 123456789, type of number: INT, and numbering plan: E.212. ZOPC:TOA=GT:DIG=123456789,TON=INT,NP=E212:RES=1,RESA=1;
Id:0900d80580570e87
37
38
Id:0900d80580570e8a
If the denial has to be created for several SMSCs, the OPC command is repeated for all the addresses. They should all point to the same result record.
Id:0900d80580570e8a
39
40
Id:0900d80580570e8d