KR100325694B1 - Local number portability audit management process in local service management system - Google Patents

Abstract

The present invention provides a local service for number portability that resolves subscriber data inconsistency between a local service management system (LSMS) and a service control point (SCP) after exchanging number porting data between service providers. Its purpose is to provide a method for auditing data in a management system.

According to the present invention, a data auditing method in a local service management system for number portability, the method comprising: a first step in which a subscriber data audit function reads subscriber data of an audit target from an SCP database and creates and stores a data list; A second step in which the subscriber data audit function reads relevant subscriber data from an LSMS database and compares it with a list of subscriber data created from the SCP database to determine whether there is a mismatch; And a third step of confirming the inconsistency of the subscriber data so that the subscriber data audit function updates the subscriber data of the SCP database according to whether the administrator requests a resolution. A data audit method is provided.

Description

Data auditing method in local service management system for number portability {Local number portability audit management process in local service management system}

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method for managing number porting data between telecommunication carriers, and in particular, after exchanging number porting data between service providers, a local service management system (LSMS) and a service control system (SCP). The present invention relates to a data auditing method in a local service management system for number portability that resolves subscriber data inconsistency.

With the emergence of new telephone companies, the provision of number portability will become a necessary service in the future. Management of shared number portability data occupies an increasingly important position for reliable service execution.

The problem of number porting data matching in the service provider is an important factor that affects the service availability and reliability of the service provider and is an important part directly related to the market competition problem of the service provider.

Number portability (NP) is a capability of a network that allows a user to change a service provider, a location, a service type, and the like without changing a conventional telephone number.

With this number portability, subscribers can eliminate the personal expenses incurred by the number shift, benefit from the use of new services and lower rates due to service competition, and for new operators, they can easily enter the local telephone business and compete. You can be provided with a foundation to do this.

In order to provide the number portability, the subscriber data related to the number transfer must be shared between each service provider, and the subscriber data needs to be generated, deleted, or changed when the number is moved.

Accordingly, there are largely a centralized management method and a distributed management method for managing number portability data between operators.

The distributed management method is a method of exchanging number porting data between service providers of each service provider. When multiple service providers exist, they are connected in a full mesh form and data management becomes complicated when a new service provider is generated.

Centralized management uses the TMN interface, the standard for telecommunications network management, and is a way for third-party independent number portability data management agencies to drive disagreement coordination or number management policies between operators.

Therefore, providing a standardized interface, downloading number portability data to each service provider, and handling data inconsistency among service providers belong to the function of the central service management system.

However, international standardization has not yet been made to resolve the inconsistency of the number-mobile subscriber data between the local service management system (LSMS) and service control system (SCP) in the service provider.

The present invention has been made to solve the above problems of the prior art, and under the centralized management structure by investigating the inconsistency of the subscriber data that may occur in the service provider after data processing activities related to the number transfer between operators and accurate Its purpose is to provide a data auditing method in a local service management system for portability to minimize the waste of unnecessary resources caused by unused data.

1 is a structure of number portability management to which the present invention is applied.

2 is a detailed configuration diagram of the LSMS and SCP of FIG.

3 is a flow chart of information transmission and reception for auditing data between LSMS and SCP according to the present invention.

4 is a subscriber data audit processing flow diagram in accordance with the present invention.

Explanation of symbols on the main parts of the drawings

100: MSMS (Master Service Management System)

101: LSMS (Local Service Management System)

102: Subscription Administration System

103: SCP (Service Control Point)

201: LSMS agent 202: subscriber data audit function

203: management coordinator unit 204: subscriber data management function unit

205: graphical user interface function

206: LSMS Database

207: SCP Agent 208: SCP Database

209: service logic execution environment 210: service logic

According to the present invention for achieving the above object, is connected to the LSMS (Local Service Management System) database and the LSMS database that stores subscriber data, routing data, Global Title Translation (GTT) data, etc. necessary for number transfer LSMS, which acts as an administrator for managing number porting data, including subscriber data audit function which performs data audit function, and creation, deletion, retrieval, change, etc. of subscriber data, routing data, etc. A method for auditing data in a local service management system for number portability, including an SCP including an SCP database storing information used for service processing and a SCP (Service Control Point) agent receiving and processing a management command of a subscriber. Subscriber data with audit function with data audit function A first step of reading the data from the SCP database and creating and storing a data list; A second step in which the subscriber data audit function reads relevant subscriber data from an LSMS database and compares it with a list of subscriber data created from the SCP database to determine whether there is a mismatch; And a third step of confirming the inconsistency of the subscriber data so that the subscriber data audit function updates the subscriber data of the SCP database according to whether the administrator requests a resolution. A data audit method is provided.

In the following, with reference to the accompanying drawings, a preferred embodiment according to the present invention will be described in detail.

1 is a diagram illustrating a number portability management structure to which the present invention is applied, and a description of each system constituting the service management structure is as follows.

The master service management system (MSMS) 100 is a system for providing data required for providing number portability capability between operators to a local service management system (LSMS) 101 connected through a CMIP protocol.

The central service management system 100 distributes or collectively adjusts the shared information required for the number porting service in the entire network to the local service management system (LSMS) 101 of each operator. In particular, it plays the role of mediation to accept routing information necessary for service provision and subscriber data of all service providers to maintain the integrity and synchronization of these information.

The Local Service Management System (LSMS) 101 downloads subscriber data, routing data, Global Title Translation (GTT) data, etc. required for number movement from the central service management system (MSMS) 100 and transmits the number portability within the service provider. NP) It transmits and manages application functions and data.

The service control system (SCP) 103 receives line-related data, non-line-related messages, and routing information necessary for the number portability call processing from the local service control system (LSMS) 101 connected through the CMIP protocol. (NP DB) and GTT database, and then handles routing of calls to non-routed numbers and routing of non-line related messages.

In addition, the service control system (SCP) 103 has a transaction function with a service switching point (SSP) and a number portability database necessary for providing the number portability capability. When the service control system (SCP) 103 receives a query from the SSP, it is included in the query. The network routing information corresponding to the called party's address is retrieved, and the call is forwarded by responding to the corresponding SSP.

In addition, the service control system (SCP) 103 receives a non-line related message from a signaling transfer point (STP), retrieves a signal point code corresponding to a destination address of the message, and re-converts it to the corresponding signal point. Root function.

The subscription administration system (SAS) 102 is a subscription management system that receives and processes a number shift and termination request from a subscriber. When using a two-stage routing scheme, transactions can occur with a Local Service Control System (LSMS) 101 connected by a proprietary protocol to provide location mobility within the same area code.

In this case, the SAS 102 requests the Local Service Management System (LSMS) 101 to change the network routing information of the moved subscriber and completes the call to the new destination exchange. Change its own network information.

FIG. 2 is a detailed configuration diagram of the LSMS and the SCP of FIG. 1, and the relationship between the LSMS and the SCP is a relationship between a manager and an agent mentioned in the TMN management.

As shown in the figure, there is an LSMS agent 201 corresponding to the manager role of the MSMS in the LSMS serving as the manager for managing the number movement data of the SCP. The LSMS agent 201 downloads subscriber data, routing data, global title translation (GTT) data, and the like necessary for number movement of the MSMS, and creates, deletes, retrieves, or changes information in the LSMS database 206. .

The manager application unit connected to the LSMS agent 201 and the LSMS database 206 includes a subscriber data audit function 202, a management coordinator 203, a subscriber data management function 204, and a network data management function.

There is also a graphical user interface function 205 coupled to the manager application.

Meanwhile, SCP agent 207 of SCP receives management commands such as creation, deletion, retrieval, and change of subscriber data, routing data, etc. related to number movement from LSMS, and is used by actual number transfer service logic 210 for service processing. It is responsible for creating, deleting, retrieving, and changing information in the SCP database 208.

That is, in response to a number porting data management request such as creating, deleting, or changing subscriber data of the MSMS, the LSMS agent 201 performs DB operations on the LSMS database 206 according to these requests and manages subscriber data in the manager application unit. Management applications such as section 204, network data management functions, etc., are reflected in the SCP database 208 in the SCP.

As described above, if there is more than one SCP in the provider, two or more databases related to number transfer exist. Although the request is reflected in SCP number porting database 208 through LSMS subscriber data management function 204 or network data management functions, communication problems between MSMS and LSMS, communication problem between LSMS and SCP, number porting database There is a possibility that data inconsistency may occur due to an operation problem or the like.

The subscriber data audit function unit 202 exists to solve such a number porting data mismatch problem.

Now, information transmission and reception flows corresponding to the subscriber auditing function of the present invention will be described with reference to FIGS. 3 and 4.

3 is a flow chart of information transmission and reception for auditing data between LSMS and SCP according to the present invention, and shows messages between LSMS database 206, subscriber data audit function 202, SCP agent 207, and SCP database 208. It is shown.

As shown in the figure, subscriber data audit function 202 instructs SCP agent 207 to obtain audit data via M-GET operation (301), which causes SCP agent 207 to send SCP database 208. Query the subscriber data DB (302), get the result (303), and respond to the M-GET request (304).

The subscriber data audit function 202 stores these data in a list (305), queries the LSMS database 206 for the same audit data (306) and receives the results (307).

Subscriber data audit function 202 checks for inconsistencies by performing a comparison of each data received from LSMS database 206 and SCP agent 207 (308). For the data inconsistency, the SCP agent 207 requests data change through the M-SET operation with the value in the LSMS database 206 (309).

The SCP agent 207 requests an update to the SCP database 208 (310), receives the result (311), constructs an M-SET response message and responds to the subscriber data audit function 202 (312). . Subscriber data audit function 202 configures information about the mismatch resolution result and reports the result to graphical user interface function 205 (313).

4 is a flowchart of a subscriber data audit process according to the present invention, wherein the subscriber data audit function unit 202 is configured to operate at a predetermined cycle when an administrator requests a service provider or when a management function is configured.

Data auditing is driven 401 by a system timer according to an administrator's request via graphical user interface function 205 or an audit period configured in subscriber data audit function 202.

First, the M-GET operation message of the CMIP protocol for the audited data is transmitted to the SCP agent 207 (402). The operation of the M-GET delivered at this time includes scoping or filtering information of the CMIP.

Upon receiving this message, SCP agent 207 responds to the M-GET operation by making a DB query. The response of the M-GET operation consists of one response message in the case of a single operation, and may be in the form of a linked reply in the case of scoping or filtering operations, but the simplification of the figure is simplified. To receive the M-GET response.

When the response is completed as described above (403), a list of subscriber data is stored (404), and the subscriber data corresponding to the list is queried (LS405). When reception of the query result is completed (406), it is compared with a previously received subscriber data list (407).

It is determined whether the data is inconsistent (408), and if there is no inconsistency, the result is transmitted (409) to the screen via the graphical user interface function unit 205 and ends.

If it is determined that there is a mismatch, a list of inconsistencies is displayed on the user screen through the graphical user interface function unit 205 (410), and the administrator checks whether or not to correct the mismatch (411). If there is no request for resolving inconsistency, exit.

If there is an administrator's request for resolving inconsistency, the MIP of MIP-SET operation of CMIP is transferred to change the data of the inconsistent SCP to the value of LSMS data (412). Here, the M-SET operation is transmitted in a confirmed mode.

SCP agent 207 receives the M-SET operation and changes and responds to the corresponding data in the number transfer database. If a response is received (413), the graphical user interface function 205 informs the administrator that the data has changed (414) and ends.

The present invention as described above is recorded on a computer-readable recording medium, and can be processed by a computer.

As described in detail above, the present invention prevents a malfunction of the number portability service by providing a solution and solution for data inconsistency that may occur between the LSMS and the SCP present in the provider in the centralized number portability management structure, thereby preventing unnecessary resources. It is effective to prevent waste.

The technical spirit of the present invention has been described above with reference to the accompanying drawings, but this is by way of example only and not by way of limitation to the present invention. In addition, it is obvious that any person with ordinary skill in the art may make various modifications and imitations without departing from the scope of the technical idea of the present invention.

Claims (7)

The number includes a local service management system (LSMS) database storing subscriber data, routing data, and global title translation (GTT) data necessary for number movement, and a subscriber data audit function connected to the LSMS database to perform a data audit function. LSMS serving as an administrator for managing mobile data, and It includes a SCP (Service Control Point) agent for receiving and processing management commands such as creation, deletion, retrieval, and change of subscriber data, routing data, etc., related to number movement of the LSMS, and an SCP database for storing information used for service processing. A method of auditing data in a local service management system for portability involving SCPs, If data auditing is configured by an administrator's request or the subscriber data auditing function and driven by a system timer according to an audit cycle, the subscriber data auditing function sends the SCP agent an M-GET operation message of the CMIP protocol for the audited data. A first step of delivering; The SCP agent, which has received the M-GET operation message in the first step, makes a subscriber database query to the SCP database and transmits the response to the subscriber data audit function, and the subscriber data audit function sends the received response to the subscriber. A second step of storing as a list of data; A third step in which the subscriber data audit function reads relevant subscriber data from the LSMS database and checks whether there is a mismatch by comparing with the subscriber data list stored in the second step; And A fourth step of updating the subscriber data of the SCP database by the subscriber data auditing function according to whether an administrator requests a resolution if the subscriber data is inconsistent; Data audit method in the local service management system for number portability, comprising a. delete The method of claim 1, The operation of the M-GET delivered to the SCP agent, A method for auditing data in a local service management system for number portability, which is a single operation or an operation including scoping or filtering information of a CMIP. The method of claim 1, The response of the M-GET operation from the SCP agent is Local service management system for number portability, characterized in that it consists of one response message in the case of a single operation, and a Linked Reply message in the case of scoping or filtering operations. How to audit data in The method of claim 1, The third step, Querying, by the subscriber data audit function, the LSMS database for subscriber data corresponding to the data list created from the SCP database; Comparing the query result with a list of subscriber data previously received from the SCP database when the query result is received; And And determining whether there is a mismatch between the subscriber data from the SCP database and the subscriber data from the LSMS database. The method of claim 1, The fourth step, Notifying the administrator of the result of the existence of the inconsistency data through the screen, and confirming whether or not the administrator will solve the inconsistency when the inconsistency data exists; Terminating if there is no inconsistency resolution request from the manager, and if an inconsistency resolution request is made by the manager, transmitting the M-SET operation message to change the data of the SCP that is inconsistent to the value of LSMS data by the subscriber data audit function; And When the SCP agent receives the M-SET operation and changes and responds to the corresponding data in the number movement database, the subscriber data audit function notifies the administrator that the data has been changed. How to audit data. The method of claim 6, The M-SET operation message is used to change the data of the SCP, which is inconsistent with the data auditing function, to the value of LSMS data. A method for auditing data in a local service management system for number portability, characterized in that transmitted in a confirmed mode.