KR100956003B1 - System for providing repair management supporting number portability service - Google Patents

Abstract

The present invention relates to a technology for receiving a fault report from a subscriber and a fault management system for processing it to support a number portability service.

In order to realize this, the present invention provides a fault management system that supports a number portability service, comprising: a subscriber information table storing subscriber information; A remote server information table storing access information with another host; A number portability information table constructed on a network and storing number portability information for a number portability service subscriber; And check the subscriber information table according to the subscriber's telephone number (TN) failure report and notify the third party vendor if the subscriber has moved to a third party, or otherwise change the telephone number (TN) reported from the subscriber. It determines whether the telephone number (TO_TN) is the same, and if it is the same, and receives the failure report of the subscriber, if not the same includes a host for receiving the failure report based on the remote server information table and the number portability information table .

Description

System for providing repair management supporting number portability service

1 is a block diagram showing a failure management system for supporting the number portability service according to an embodiment of the present invention.

FIG. 2 is a detailed configuration diagram of the Greater China in FIG.

3 is an exemplary configuration diagram of the number portability information table 500 shown in FIG. 1.

4 is an exemplary configuration diagram of the remote server information table 122 shown in FIG. 2.

5 is an exemplary configuration diagram of a subscriber information table 123 shown in FIG.

6 is a flowchart for explaining a failure management method for supporting number portability service according to an embodiment of the present invention.

The present invention relates to a fault management system and method for supporting a number portability service, and more particularly, to a fault management system for supporting a number portability service for allowing a subscriber to use the same phone number regardless of a carrier change or a position change. It is about a method.                         

At present, in order to subscribe to the wired communication service, the service provider had to be classified and subscribed at the beginning, and in order to change the service provider to another service provider, the communication service provider was terminated and the new service provider was newly subscribed. We had to join the side newly.

When the subscriber changes the service provider through the above process, the telephone number of the subscriber is changed. However, if the subscriber changes his / her phone number, he / she has to inform those who knew his / her phone number of the newly changed phone number. It does not change the operator.

This problem occurs even when the subscriber requests a change of area. When the subscriber transfers from the C area to the D area and reports the communication to the service provider, the telephone number used in the C area is destroyed and the new number is changed in the D area. By assigning a telephone number, the subscriber's new telephone number enables the landline service to be used.

Even in this case, the inconvenience that the telephone number is changed from the subscriber's point of view occurs.

Such a "number portability service" has been proposed to alleviate the inconvenience of subscribers. According to the number portability service, even if the subscriber of the communication service changes the operator or the location (location), the existing phone number can be used as it is. By comparing the quality of service and the rate, it is possible to freely select a service provider, thereby improving user convenience.

According to the above number portability service, even if the subscriber changes the provider to the operator A from the operator B or the location of the subscriber from the C region to the D region, the number is not changed and the existing telephone number used by the subscriber is used as it is. To make it possible.

In this case, the subscriber can receive the call using the existing telephone number, but the existing telephone number corresponds to the virtual number, and the telecommunication service provider to which the number portability service subscriber is finally subscribed to the actual telephone number for the number portability service subscriber. The number portability service subscriber is managed by the actual telephone number.

On the other hand, since the current trouble management system handles troubleshooting related to the telephone number reported from the subscriber, if the number portability service subscriber reports a telephone failure using a virtual telephone number used by the subscriber, Since the reported phone number is not a real phone number, there is a problem that it is not possible to perform troubleshooting related to the actual broken phone number.

Accordingly, the present invention has been made to solve the above-mentioned conventional problems, and an object thereof is to enable a fault management system that receives a fault report from a subscriber and handles it, to support a number portability service.

A failure management system supporting the number portability service of the present invention for achieving the above object includes a subscriber information table storing subscriber information; A remote server information table storing access information with another host; A number portability information table constructed on a network and storing number portability information for a number portability service subscriber; And check the subscriber information table according to the subscriber's telephone number (TN) failure report and notify the third party vendor if the subscriber has moved to a third party, or otherwise change the telephone number (TN) reported from the subscriber. It determines whether the telephone number (TO_TN) is the same, and if it is the same, and receives the failure report of the subscriber, if not the same includes a host for receiving the failure report based on the remote server information table and the number portability information table .

The fault management method for supporting the number portability service of the present invention for achieving the above object, the mobility whether to check whether the subscriber moved to the third party using the subscriber information table according to the subscriber's telephone number (TN) failure report Confirmation step; Notifying the third party if the subscriber moves to the third party as a result of the checking; Determining whether the telephone number TN reported by the subscriber and the telephone number TO_TN are changed from the subscriber using the subscriber information table if the subscriber is not the subscriber who has moved to the third party as a result of the checking; Accepting the failure report of the subscriber if the determination result is the same; And a failure report receiving step of receiving a failure report based on the remote server information table and the number portability information table, if not identical.

Hereinafter, with reference to the accompanying drawings will be described an embodiment of the present invention in more detail.

In the fault management system supporting the number portability service according to an embodiment of the present invention, as shown in FIG. 1, a plurality of systems 100, 200, 300,... Are connected to each other through a dedicated network 400, System (100, 200, 300, ...) is configured to access the number portability information management server 500 through a dedicated network (400).

The plurality of systems communicate through a dedicated network 400 based on Transmission Control Protocol / Internet Protocol (TCP / IP).

As illustrated in FIG. 1, each system includes a customer center 110 receiving a failure report in response to a call sent from a subscriber through an automatic call distribution device (not shown), and a request of the customer center 110. Wide area China 120 for determining whether to register with the subscriber by collecting the actual telephone number according to the number portability, and passing the test command to the tester (131, ...), the exchange 141 according to the test command , ...) is provided with a tester (131 to 13N + 1) for performing a predetermined test, for example, a line test, and transmits the test results to the Greater China (120).

The number portability information table 500 of FIG. 1 is a database storing subscriber number information according to the number portability service. As shown in FIG. 3, a field TN_AREA and a current phone number are stored. Field (TN), field for storing current phone station code (OFFICE_ID), field for storing subscriber name (SUB_NAME), field for storing number portability type (NP_KIND), field for storing number portability service provider code (NP_BUSI_CD) , Field to store the station code before change for number portability service (FROM_OFFICE_ID), field to store area code before change for number portability service (FROM_TN_AREA), field to store the telephone number before change for number portability service (FROM_TN) ), A field for storing the station code after the change for the number portability service (TO_OFFICE_ID), and a field for storing the area code after the change for the number portability service (TO _TN_AREA) and a field (TO_TN) for storing a telephone number after a change to the number portability service.

The number portability type field is a field for classifying a number portability service for registered subscribers by classifying the number portability service into a code. For example, if the code is “1”, the service provider is changed from its own carrier to another carrier. "2" indicates that the service provider has been changed from another service provider to its own carrier, "3" has changed its position in the home service provider, and "4" has changed its service provider from another service provider to its own service provider. Defines the state where the position has changed.

In the database constructed in the number portability information table 500, a phone number (country code, area code, phone number) before a number portability service change is stored, and a phone number (counter code, area code, phone number after a number portability service change). ) Is stored.

As shown in FIG. 2, the wide area China 120 of FIG. 1 includes a host 121, a tester 13N + 1, a remote server information DB 122, and a subscriber information DB 123.

To describe the functions of each part in more detail, the host 121 in conjunction with the subscriber information DB (123), remote server information DB (122) when the subscriber inquiry request from the customer center 110, various kinds of telephone numbers reported by the subscriber The inquiry is made, and the tester 13N + 1 performs a test on the switch 141 + 1 based on the command of the host 121. Preferably, the tester 131,... Is connected to the host 121.

In addition, the remote server information table 122 is a database that provides the host 121 with information of a wide area China (host) located in another system, and the subscriber information table 123 is a series of subscribers managed by the system. The information is stored in the database, and the communication unit 124 provides an interface function so that the host 121 can communicate with a host configured in the Greater China (220, 320) of another system through the dedicated network 400 based on TCP / IP communication. To perform.

As shown in FIG. 4, the field structure of the remote server information table 122 includes a telephone area code field (TN_AREA), a telephone station number field (TN_PREFIX), a failure management system identifier field (OSS_ID), and a failure management system IP address field (OSS_IP_ADD. ), Trouble management system Uniform Resource Locator (URL) field (OSS_UNAME), trouble management system communication port field (OSS_PORT), telephone station identifier field (OFFICE_ID), central station identifier field (CENTER_OFFICE_ID), operation status flag field (FLAG), etc. As shown in FIG. 5, the field structure of the subscriber information table 123 includes a subscriber identifier field (SUB-ID), a telephone number field (TN), a number portability type field (NP_KIND), and a telephone number field before change (FROM_TN). ), And a telephone number field (TO_TN) after the change.

In the above, the configuration has been described with reference to the system 100 for convenience of explanation, but the other systems 200, 300,... Also have the same structure as the system 100, and the wide area of the systems 200, 300,... Concentrating stations 220 and 320 are also constructed in the same structure as shown in FIG.

Hereinafter, a method of providing number portability service according to an embodiment of the present invention will be described in detail with reference to the flowchart shown in FIG. 6.

When a Public Switched Telephone Network (PSTN) or Asymmetric Digital Subscriber Line (ADSL) subscriber receives a failure report for a specific phone number, the customer center 110 calls the telephone number in the Greater China 120. Request for registration confirmation (S2).

The host 121 of the Greater China 120 checks the registration of the subscriber of the telephone number by inquiring the telephone number (TN) in the subscriber information table 123 (S4).

As a result of the check, if the telephone number exists in the subscriber information table 123 (YES in S6), the host 121 determines the type of number portability of the subscriber by querying the NP_KIND field of the subscriber information table 123. If the type number portability is " 1 " (Yes in S8), the subscriber determines that the subscriber has moved to another operator and notifies the customer center 110 that the subscriber has moved to the other operator and ends. S10).

Further, if the number portability type is "NULL" instead of "1, 2, 3, 4" as a result of the determination at the host 121, the subscriber does not register the number portability service, so the subscriber's telephone number (TN) Receive a failure report for) and ends (S14).

However, unlike the case described above, if the number portability type is "2, 3, 4" as a result of the determination in the host 121 (Yes in S12), it is checked whether the subscriber's telephone number is the last destination number (S16). Here, the determination as to whether the subscriber's telephone number is the last destination is determined by comparing the TN field value of the subscriber information table 123 and the TO_TN field value, and the TN field value and the TO-TN field of the subscriber information table 123. If the values match (Yes in S16), since the telephone number reported from the subscriber corresponds to the telephone number after the change, a failure report is received and terminated for the telephone number reported from the subscriber (S14).

However, if the TN field value and the TO_TN field value in the subscriber information table 123 do not match each other (No in S16), since the telephone number reported from the subscriber does not match the telephone number after the change, the subscriber information table ( Set the pre-change phone number stored in the FROM_TN field of 123) as the pre-call number, and set the post-change telephone number stored in the TO_TN field of the subscriber information table 123 as the report telephone number (TN) (S18). The remote information is retrieved from the remote server information table 122 based on the number (S20).

If remote information (IP address, URL, communication port, etc. of the host of the system managing the phone number) is retrieved from the remote server information table 122 (Yes in S22), the IP of the remote server is retrieved. After binding to the host using the address and port information (S24), the process proceeds to step S4 described above.

As a result of the determination in step S22, if the remote information about the telephone number after the change is not retrieved from the remote server information table 122 (No in S28), the host 121 transmits the number portability information table (through the communication unit 124). Inquiring (500) (S26), it is determined whether the number portability information exists (S28). For reference, if the remote information about the telephone number after the change in the remote server information table 122 is not retrieved, a failure report using a phone number registered to a third-party company by a subscriber moved from a third-party company is an example. Can be.

If the telephone number is not found in the number portability information table 500 (No in S28), the host 121 notifies the customer center 111 of the unregistered subscriber (S30). If the telephone number is retrieved from the number portability information table 500 (No in S28), the telephone number stored in the TO_TN field of the number portability information table 500 is set as the reported telephone number, and then the process proceeds to step S4. The following process is performed by inquiring from the subscriber information table 123 based on the number.

For reference, when the number portability information does not exist in the number portability information table 500 as a result of the determination in step S28 (No in S28), the phone number reported from the subscriber is not registered in the own business. For example, the case is not registered with the business operator.

If the number portability information exists in the number portability information table 500 as a result of the determination in step S28 (YES in S28), the telephone number reported by the subscriber is not registered to the own business operator, For example, if registered.

On the other hand, when a failure report is received from the subscriber in step S14, the host 121 transfers the order according to the failure process to a specific tester among the testers 131, ..., 13N, 13N + 1 to process the failure report. To be done.

According to the present invention as described above, by building an integrated subscriber network management system that accommodates the number portability service, even if the subscriber reports the failure to the existing number irrespective of the number portability service, it is possible to handle the fault management work smoothly do.

On the other hand, the present invention is not limited to the above-described embodiment, but can be modified and modified within the scope not departing from the gist of the present invention, such modifications and changes should be regarded as belonging to the following claims. will be.

Claims (9)

In the trouble management system supporting the number portability service, A subscriber information table storing subscriber information; A remote server information table storing access information with another host; A number portability information table constructed on a network and storing number portability information for a number portability service subscriber; And According to the subscriber's telephone number (TN) failure report, check the subscriber information table and notify the third-party vendor if the subscriber has moved to a third party, or otherwise change the telephone number (TN) and the telephone after the change Determine whether the number TO_TN is the same, and if it is the same, accept the failure report of the subscriber; otherwise, the host for receiving the failure report based on the remote server information table and the number portability information table. Problem management system that supports the number portability service, including. The method of claim 1, The host, And a number portability service that receives a fault report based on the remote server information table and the number portability information table when there is no information on the subscriber in the subscriber information table. The method of claim 2, The host, If the telephone number (TN) reported from the subscriber and the telephone number (TO_TN) after the change are not the same, if the remote information on the telephone number (TO_TN) after the change is found in the remote server information table, the remote server information exists. Binds to the host using IP address and port information, if it does not exist, search for the mobility information of the subscriber in the number portability information table and if it exists, breaks down based on the telephone number (TO_TN) after changing the number portability information table. A fault management system that supports number portability services that accept reports and notify you that you are an unregistered subscriber, if they do not exist. The method according to any one of claims 1 to 3, The subscriber information table, At least one of a subscriber identifier, a subscriber's telephone number (TN), a subscriber's number portability type (NP_KIND), a telephone number before the change according to the number portability service (FROM_TN), and a telephone number after the change according to the number portability service (TO_TN) Fault management system supporting number portability service. The method of claim 4, wherein The remote server information table, A trouble management system supporting a number portability service including at least one of a telephone area code, a telephone station number, a system identifier, a system IP address, a system URL, a system communication port, a telephone station identifier, a central station identifier, and an operation status flag. The method of claim 5, The number portability information table, Current area code, current phone number, current phone number, subscriber name, subscriber's number portability service registration type, number portability service provider code, number portability service change information (country code, area code, phone number), number portability service change After the information (station code, area code, telephone number, a trouble management system that supports a number portability service including at least one of. In the trouble management method that supports the number portability service, A mobility checking step of checking whether a subscriber has moved to a third party using a subscriber information table according to a subscriber's telephone number (TN) failure report; Notifying the third party if the subscriber moves to the third party as a result of the checking; Determining whether the telephone number TN reported by the subscriber and the telephone number TO_TN are changed from the subscriber using the subscriber information table if the subscriber is not the subscriber who has moved to the third party as a result of the checking; Accepting the failure report of the subscriber if the determination result is the same; And As a result of the determination, if it is not the same, the fault report accepting step of accepting the fault report based on the remote server information table and the number portability information table. Problem management method that supports the number portability service, including. The method of claim 7, wherein The mobility check step, If the information on the subscriber does not exist in the subscriber information table, receiving a failure report using the remote server information table and the number portability information table. 9. The method according to claim 7 or 8, The trouble report accepting step, A first inquiry step of retrieving remote information of the telephone number TO_TN after the change from the remote server information table if the telephone number TN reported from the subscriber is not the same as the telephone number TO_TN after the change; Binding to the corresponding host by using the IP address and port information of the remote server if the remote information about the telephone number TO_TN exists after the first inquiry result; A second inquiry step of querying the subscriber's mobility information in the number portability information table if there is no remote information on the changed telephone number TO_TN after the first inquiry result; Receiving a failure report based on a telephone number (TO_TN) after the change of the number portability information table if the mobility information of the subscriber exists as a result of the second inquiry; And Notifying that the subscriber is an unregistered subscriber if the mobility information of the subscriber does not exist as a result of the second inquiry Problem management method that supports the number portability service, including.

Images