MXPA99011667A - Method and apparatus for processing requests and maintaining records in a telecommunications system - Google Patents

Abstract

A method and apparatus for supporting local number portability and service portability in a telephone network (100) are disclosed. Subscription and administrative service requests are processed by local service management systems (LSMSs) (140a, 140b) and records are maintained at service control points (SCPs) (145a, 145b). The subscription requests include create, modify, and delete request of records in the SCPs (145a, 145b). The administrative service requests include numbering plan area (NPA) split, mass change, and query and resend requests. The records at the SCPs (145a, 145b) are accessible by switches (115a, 115b) via respective service transfer points (STPs) (120a, 120b) to determine the network addresses of the switches (115a, 115b) handling services and calls corresponding to a particular telephone number.

Description

METHOD AND APPARATUS FOR PROCESSING PETITIONS AND KEEPING RECORDS IN A TELECOMMUNICATION SYSTEM Technical Field The present invention relates to telephone systems. More particularly, the invention relates to a method and apparatus for handling subscription and administrative requests in a local service management system, particularly for local number portability.

Prior Art In the existing telephone network, customers are assigned telephone numbers based on where the telephones are located or are geographically fixed. For example, each telephone number may contain numbers that represent (1) a three-digit number area plan code (NPA code) which uniquely identifies a defined geographic area in which the customer's telephone is located, (2) a three-digit final office code (NXX) that identifies a central office that handles calls within that geographic area, and then (3) a four-digit line number that uniquely represents the client within the head office.

REF .: 32104 An existing telephone network is conventionally constituted of a series of connected telephone switches, each of which is operated by a local telephone service provider and designed to handle calls for particular customers within a service area. Many calls require switches operated by different local telephone service providers to interact with each other to establish the necessary links. In those cases, the switch in the calling party tries to locate the switch of the called party having access to the database of network addresses indexed according to the code NPA and NXX. After receiving the address of the called party's switch network, the calling party switch establishes a link between the switches and transmits a request to the called party's switch to complete the call to the called party. This configuration does not suit the needs of the client, however. For example, the network does not conveniently support "local number portability," which means the ability for a customer to keep their phone number when changing local telephone service providers. In this way, it is often required to change telephone numbers when moving from one service area to another, creating an inconvenience. This configuration also does not allow a client to select different service providers to concurrently provide different services or features to that client. The increase in customer mobility and the demand for portability have led to the proposal to modify the existing telephone network to support local number portability. Such modifications may involve keeping in a detailed database, records containing information indicating, for example, what services are provided to a client and which service providers are selected to provide those services. Such detailed records, however, must be updated accurately and frequently, so that the switches can rely on those records to provide effective service to their customers, so there is a need to provide a mechanism to preserve such records. records within the existing telephone network.

Description of the Invention To achieve these and other advantages and in accordance with the purpose of the invention, as described in the embodiments, and broadly, the invention includes a method and system for handling subscription and administrative requests in a system of local service administration. In one aspect of the invention, a method for handling a subscription request comprises receiving the subscription request in a local service administration system.; provide a customer record of a database; determine if a division of the area code of the numbering plan has occurred; send the subscription request to a service control point; and perform state management functions. In another aspect, a method for handling an NPA split request, in which a new NPA code and an old NPA code are assigned to an NPA to which a single NPA code was previously assigned, comprises access to a first set of NPAs. records that contain the old NPA code; generate a second set of records from the first set that contains the new NPA code; and delete the first set of records after the division of the NPA occurs. In yet another aspect, a method for handling a mass change request, comprises updating translations of records having an LRN designated in the mass change request, if the mass change request is for updating the mass; update translations of records that have a designated LNR in the mass change request and delete records that have the designated LNR, if the mass change request is to change mass records; and delete records that have an LRN designated in the mass change request, if the mass change request is for the mass change suppression. In yet another aspect, a method for handling a question and sending a request again comprises transmitting a question to at least one database in an LSMS and SCP; and send again a previously-subscribed subscription request, when a failure is determined with the transmission request previously transmitted. Both the foregoing general description and the following detailed description are exemplary and explanatory and are intended to provide a further explanation of the invention as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings are included to provide a better understanding of the invention and, together with the Detailed Description, serve to explain the principles of the invention. In the drawings: Figure 1 is a block diagram of a system consistent with the invention; Figure 2 is a block diagram of the local service management system 140 shown in Figure 1; Figure 3 shows a flow diagram representing a total process performed by the service manager program 148 consistent with the invention; Figure 4 shows a flowchart representing a process in which the service manager program 148 processes subscription requests received from the number portability management center; Figure 5 shows a flowchart representing a process in which the service manager program 148 processes a request to create; Figure 6 shows a flowchart representing a process in which the service manager program 148 processes a request to delete; Figure 7 shows a flowchart representing a process in which the service manager program 148 processes a request to modify; Figure 8 shows a flowchart representing a process in which s-service administrator program 148 processes administrative service requests; Figure 9 shows a flowchart representing a process in which the service manager program 148 processes a request to split an NPA; Figure 10 shows a flowchart representing a process in which the service manager program 148 processes a request to change the mass; and Figure 11 shows a flowchart representing a process in which the service manager program 148 processes a question and a request for forwarding.

BEST MODE FOR CARRYING OUT THE INVENTION Introduction In order to support the portability of the number and portability of local services in a telephone network, the method and apparatus of the invention handle subscription requests and administrative service in a local service management system to preserve records. at a service control point. Subscription requests include requests to create, modify, and delete records at the service control point. Requests for administrative services include dividing the NPA, change of the mass, and requests for investigation and resubmission. The registers at the service control point are accessible by switches via respective signal transfer points to determine the network addresses of the switches that handle the services and calls that correspond to a particular telephone number. The methods and apparatuses of the invention are described in relation to the accompanying drawings. Common reference numbers were used to designate similar components.

System Figure 1 shows one embodiment of the invention as system 100. As shown in Figure 1, system 100 includes telephones 100a, 100b, switches 115a, 115b, signal transfer points (STP) 120a, 120b , service order systems 125a, 125b, number portability manager center (NPAC) 130, local service management system (LSMS) 140a, 140b, and service control points 145a and 145b. The telephones 100a, 100b are connected to the switches 115a, 115b, respectively, which are linked to the STPs 120a, 120b, respectively, and the service order system 125a and 125b, respectively. The SCPs 145a, 145b are connected to the LSMS 140a, 140b, respectively, and the. STP 120a, 120b, respectively. The NPAC 130 is connected to the service order system 125a, 125b, and the LSMS 140a, 140b.

Telephones 1O0, switches 115 comprise conventional components used in a telephone network. The STP 120 comprises a signaling point that transfers signaling messages from one signaling link to another and preferably comprises a packet switch that transmits messages between the switches and other components of the network. The STP 120 also transmits messages between switches during the establishment and routing of a normal call. The Service Order System 125 handles the routing of service orders made by telephone customers 100 to NPAC 130. The NPAC 130 comprises an administrator of the third part of the regional LNP databases. The LSMS 140 processes requests from the NPAC 130 and preferably comprises a network database owned by the local service provider which contains information of the downloaded bearer number. The SCP comprises a transaction system based on a processor that provides a network interface to the services of the database. Figure 2 shows a block diagram of the LSMS 140 according to the invention. The LSMS 140 comprises the CMISE 142 gate, the application backrequest 144, the ReqAdmin Process 146, and the service management program (SMP) 148. Those elements are connected in series with the CMISE gate 142 that receives requests from the NPAC 130 and the service management program 148 coupled externally to the element manager of the network 200. In a preferred embodiment, the LSMS 140 comprises a programmed server which performs the functions described herein. The CMISE gateway 142 serves as an interface to receive requests in the CMISE format, validate data in the requests, and translate the requests into a format for the SMP 148. Such requests may include, for example, subscription requests to create, modify, or delete customer records stored in SCP 145. Application rollback 144 receives processed requests from gateway CMISE 142, validates requests, establishes a local subscriber record to be processed by SMP 148, and constructs the appropriate tables. The application backrequest 144 also schedules the requests to be processed with the ReqAdmin Process 146. The ReqAdmin Process 146 maintains the request program and initiates processing requests by the SMP 148. The SMP 148 processes the requests that are received from the ReqAdmin Process 146 in the manner described below in relation to Figures 3-11. After the processing of the requests, the SMP 148 transmits records to the network element manager 200 for storage in the SCP 145. The network element manager 200 validates the data in the registers and, if valid, stores the records in SCP 145.

SMP Operation The SMP 148 handles subscription requests and administrative service requests in its maintenance or conservation of records stored in SCP 145. Figure 3 is a flow chart of a total process performed by SMP 148. After the assignment of initial values (step 310), the SMP 148 processes the subscription requests received from the NPAC (step 320) and processes the administrative service requests (step 330). After the SMP 148 processes those requests, the process ends (step 340). The processing of the subscription requests (step 320) is described in more detail in relation to Figures 4-7, and the processing of the administrative service requests (step 330) are described in connection with Figures 8-11. Subscription requests generally refer to requests in which customer records are created, modified or deleted. Figure 4 is a flow chart showing a preferred embodiment of how the SMP 148 processes subscription requests. After the processing of those subscription requests is initiated (step 400), the SMP 148 determines whether the subscription request is a request to create (step 410). If so, the SMP 148 processes the request as a subscription request (step 420), described in connection with Figure 5. If not, the SMP 148 determines whether the subscription request is a request to delete (step 430). If so, the SMP 148 processes the request as a request to delete (step 440), described in relation to Figure 6. If the request is a request to delete, the SMP 148 determines whether the request is a request to modify ( step 450). If so, the SMP 148 processes the request as a request to modify (step 460), described in connection with Figure 7. If the request is a request not to modify, the process ends (step 470). Figure 5 shows a flowchart representing a process in which the SMP 148 processes a request to create. To begin, initial values are assigned to a local database in the LSMS 140, after which a database record is retrieved (step 510). The SMP 148 determines whether a division or separation has occurred in the NPA (step 520). A division or separation of the NPA is where one or more NPA codes are assigned to a numbering plan area to which a single NPA code has previously been assigned. SMP 148 follows up on this determination for further use.

The SMP 148 then determines whether the request to create is a duplicate request (step 530). That is, if the same request has been received previously. If so, the SMP 148 processes the request to create a duplicate as a request to modify (step 540), in which case the processing continues as shown in Figure 7. If the SMP 148 determines that the request to create is a request to duplicate, process translations indicating the manner in which in telephone services, such as the 3-way call, voice mail, caller's ID, must be processed (step 550). Such translations may include network addresses for the service providers that provide those services and are preferably processed according to industry standards. The SMP 148 sends the create request to the network element manager 200 to request that the SCP 145 create a client register corresponding to the one that was accessed in the local database (step 560). The SMP 148 waits for the acknowledgment that the request to create was received properly. After receiving the acknowledgment (step 560), the SMP 148 performs state management functions (step 570) after which the process is completed (step 580). Such functions may include sending the request to create each SCP 145 where there is a plurality of SCP 145 connected to the SMP 148 and updating the local database to reflect the data stored in the SCP 148. Figure 6 shows a diagram of flow representing in which SMP 148 a request to delete is processed. This process contains several steps that are corresponding similar to that described in relation to Figure 5 for the processing of a request to create. To start, initial values are assigned to a local database in the LSMS 140, after which a record in the database is retrieved (step 600). The SMP 148 determines whether a division or separation of the NPA has occurred (step 610) and follows up on this determination for further use. The SMP 148 then processes translations that indicate the manner in which the telephone services are to be processed (step 620). The SMP 148 sends the request to suppress the element manager of the network 200 to request that the SCP 145 delete a client register (step 630) and awaits the acknowledgment that the request to delete was received properly. After receiving the acknowledgment (step 630), the SMP 148 performs state management functions (step 640) after which the process is completed (step 650). One of the state management functions is preferably to delete the client record from the local database in the LSMS 140. Figure 7 shows a flowchart representing a process in which the SMP 148 processes a request to modify. This process contains several steps that are correspondingly similar to those described in relation to Figures 5 and 6 for the processing of the create and delete requests. After starting the process, initial values are assigned to a local database in the LSMS 140, after which a database record is retrieved (step 700). The SMP 148 determines whether a division or separation of the NPA has occurred (step 710) and follows up on this determination for further use. The SMP 148 sends the request to suppress the element manager of the network 200 to request that the SCP 145 modify a client register previously stored in the SCP 145 (step 720) and awaits the acknowledgment that the request to modify was received properly. After receiving the acknowledgment (step 720), the SMP 148 performs state management functions (step 730) after which the process is completed (step 740). Administrative service requests generally refer to requests to maintain and update existing customer records as well as requests to further process previously made subscription requests. Figure 8 is a flow diagram showing a preferred embodiment of how the SMP 148 processes administrative service requests. After starting the process (step 800), the SMP 148 determines whether the administrative service request is a request to divide or separate the NPA (step 810). If so, the SMP 148 proceeds the request as a request for division or separation from the NPA (step 820) described in connection with Figure 9. If not, the SMP 148 determines whether the subscription request is a request for change of the dough (step 830). If so, the SMP 148 processes the request as a request to change the mass (step 840), described in relation to Figure 10. If the request is a request to change the mass, the SMP 148 determines whether the request it is a request for investigation and resubmission (step 850). If so, the SMP 148 processes the request as a request for investigation and resubmission (step 860), described in connection with Figure 11. If the request is a request for investigation and resubmission, the process ends (step 870). Figure 9 is a flowchart representing a process in which the service management program 148 processes a request to divide the NPA. As discussed below, a division of the NPA occurs where more than one NPA code is assigned to a numbering plan area to which a single NPA code had previously been assigned. This request is provided to update the NPA codes for the records stored in SCP 145. Before the division or separation of the NPA occurs, the SMP 148 makes a request to modify, as described in connection with Figure 7, to duplicate records with the old NPA code as new records and modify the NPA codes to reflect the new NPA code (step 910). In this way, two copies of those records are stored in SCP 145, one with the new NPA code and one with the old NPA code. After the division of the NPA occurs, the SMP 148 makes a deletion request, as described in connection with Figure 6 r to delete the records containing the old NPA code (step 920), after which the process (step 930). Figure 10 is a flowchart representing a process in which the service management program 148 processes a mass change request. In a preferred embodiment, there are three types of mass change requests: (1) update the mass on a given number of location routings (LRN); (2) move the mass of records from one SCP to another; and (3) suppress the mass of records of an SCP.

The SMP 148 determines if the request of the change of the mass is for the update of the mass in a given LRN (step 1010). If so, the SMP 148 updates the translations of each of the registers having the given LRN (step 1020) and then concludes the process (step 1070). If the request to change the mass is not to update the mass, SMP 148 determines whether the request to change the mass is to move the mass of records from one SCP to another, as designated by an NPA code and NXX (step 1030). If so, SCP 148 makes a request to create, as described in connection with Figure 5, to create in the destination SMP a copy of each record containing the designated NPA and NXX code and make a request to delete, as described in relation to Figure 6, for each record containing the designated NPA and NXX code located in the originating SCP (step 1040), and then the process is concluded (step 1070). If the request to change the mass is not to move the mass, the SMP 140 determines whether the request to change the mass is to request the deletion of an SCP record, as specified by an NPA and NXX code (step 1050). If so, the SMP 148 deletes the records with the designated NPA and NXX code of the SCP (step 1060). The process ends then (step 1070).

Figure 11 is a flowchart representing a process in which a service management program 148 processes a request for investigation and forwarding. Such a request can be initiated to verify a previously issued subscription request. For a research request, the SMP 148 consults the local LSMS database and the SCP based on a designated telephone number to access the information in the database (step 1110). For the resend request, the SMP 148 transmits a resend request according to a particular register (step 1120), after which the process ends (step 1130).

Conclusion It will be apparent to those skilled in the art that various modifications and variations may be made to the method and system of the present invention without departing from the spirit or scope of the invention. For example, the steps set forth in the processes of the invention can be carried out in any order, unless otherwise specified or required because the final step requires values generated by an initial step. The present invention covers the modifications and variations of this invention as long as they fall within the scope of the appended claims.

It is noted that in relation to this date, the best method known to the applicant to carry out the aforementioned invention, is that which is clear from the present description of the invention.

Claims (18)

CLAIMS Having described the invention as above, the content of the following claims is claimed as property:

1. A method for handling a subscription request to process records stored in a Service Control Point (SCP), characterized in that it comprises: receiving the subscription request in a Local Service Management System (LSMS); validate the data in the subscription request; translate the subscription request into a format comprised by the LSMS; recover a record from a local database within the LSMS; determine if a division of the area code of the numbering plan has occurred and follow up on the determination for later use; send the LSMS subscription request to an administrator of network elements to request that an SCP process a record corresponding to the record retrieved from the local database; wait for the acknowledgment that the subscription request sent to the network element manager was received properly; receive the acknowledgment of receipt; and perform state management functions.

The method according to claim 1, characterized in that the subscription request comprises a request to create record.

The method according to claim 1, characterized in that the subscription request comprises a request to suppress registration.

The method according to claim 1, characterized in that the subscription request comprises a request to modify the record.

5. The method of compliance with the claim 1, characterized in that it further comprises determining whether the received subscription request is the duplicate of a previously received subscription request; and if it is determined that the subscription request received is the duplicate, then the subscription request is processed as a request to modify the record.

6. The method of compliance with the claim 1, characterized in that it also comprises processing translations according to the received subscription request.

7. An apparatus for handling a subscription request for processing records stored at a Service Control Point (SCP), characterized in that it comprises: means for receiving the subscription request in a Local Service Management System (LSMS); means to validate the data in the subscription request; means for translating the subscription request into a format comprised by the LSMS; means for retrieving a record from a local database within the LSMS; means to determine if a division of the area code of the numbering plan has occurred and to track the determination for later use; means for sending the LSMS subscription request to an administrator of network elements to request that an SCP process a record corresponding to a record retrieved by the means for recovery; means for waiting for the acknowledgment that the subscription request sent to the network element manager was received properly; means to receive the acknowledgment of receipt; and means for performing state management functions.

The apparatus according to claim 7, characterized in that the subscription request comprises a request to create record.

9. The apparatus according to claim 7, characterized in that the subscription request comprises a request to suppress registration.

The apparatus according to claim 7, characterized in that the subscription request comprises a request to modify the record.

The apparatus according to claim 7, characterized in that it further comprises means determining whether the received subscription request is the duplicate of a previously received subscription request; and means for processing the subscription request as a modified registration request if it is determined that the received subscription request is a duplicate.

12. The apparatus according to claim 7, characterized in that it also comprises means for processing translations according to the received subscription request.

A method for handling a request for division or separation of the area code from the numbering plan for updating area codes of the numbering plan for records at a Service Control Point (SCP), characterized in that it comprises: receiving a request for administrative service in a Local Service Management System (LSMS); determine that the administrative service request is a request to divide the number plan area code, where it is requested that a new number plan area code be assigned and an old number plan area code assigned to an area of numbering plan to which he had previously been assigned a single number plan area code; duplicate a first set of records stored in an SCP containing the old number plan area code as a second set of new records; modify the second set of records to reflect the new number plan area code; determine that a division of the number plan area code has occurred; and delete the first set of records after division of the area code of the numbering plan occurs.

14. An apparatus for handling a request for division of the area code of the numbering plan to update the area codes of the numbering plan for the records stored in a Service Control Point (SCP), characterized in that it comprises: means for receiving an administrative service request in a Local Service Management System (LSMS); means for determining that the administrative service request is a request to divide the number plan area code, where it is requested that a new number plan area code be assigned and an old number plan area code to be assigned to a numbering plan area to which a single number plan area code was previously assigned; means for duplicating a first set of records stored in an SCP containing the old number plan area code as a second set of new records; means for modifying the second set of registers to reflect the new number plan area code; means for determining that a division of the numbering area area code has occurred; and means for suppressing the first set of records after division of the area code of the numbering plan occurs.

15. A method for handling a mass change request to process the records stored in a Service Control Point (SCP), characterized in that it comprises: receiving a request to change the mass in a Local Service Management System (LSMS); determine whether the mass change request is for an update of the mass at a given Location Routing Number (LRN); update translations of the records stored in an SCP having the given LRN, if it is determined that the request for the change of mass is to update the mass in the given LRN; determine whether the request to change the mass is to move the mass of records from an originating SCP to a destination SCP, as designated by an area code of the numbering plan and office code, if it is determined that the request to change the mass is not to update the mass; create in the destination SCP a copy of each record located in the originating SCP that contains the area code of the designated numbering plan and office code, if it is determined that the request to change the mass is to move the mass of records; determine whether the request to change the mass is to suppress the records of an SCP, as specified by a number plan area code and an office code, if it is determined that the request to change the mass is not is to move the mass of records; and delete the records containing the area code of the numbering plan and the office code specified from the SCP, if it is determined that the request for the change of mass is for suppression of records.

16. The method of compliance with the claim 15, characterized in that it also comprises determining whether the request to change the mass is to copy all the records of an SCP, as designated by an area code of the numbering plan and the office code, if it is determined that the change of the mass is not for the suppression of the mass of records; and copy the records containing the area code of the numbering plan and the specified office code of the originating SCP to the destination SCP, if 'it is determined that the request to change the mass is for copying records.

17. An apparatus for handling a mass change request for processing the records stored in a Service Control Point (SCP), characterized in that it comprises: means for receiving a request for change of mass in a Service Management System Local (LSMS); means for determining whether the mass change request is for a mass update at a given Location Routing Number (LRN); means for updating translations of the records stored in an SCP having the given LRN, if it is determined that the request to change the mass is to update the mass in the given LRN; means to determine whether the request to change the mass is to move the mass of records from an originating SCP to a destination SCP, as designated by an area code of the numbering plan and office code, if determines that the request for the change of mass is not to update the mass; means to create in the destination SCP a copy of each record located in the originating SCP containing the area code of the designated numbering plan and office code, if it is determined that the request to change the mass is to move the mass of records; means to determine whether the request to change the mass is to suppress the records of an SCP, as specified by a number plan area code and an office code, if it is determined that the change request of the mass is not to move the mass of records; and means for suppressing records containing the area code of the specified numbering plan and office code of the SCP, if it is determined that the request for change of mass is for record suppression.

18. The apparatus according to claim 17, further comprising means for determining whether the mass change request is for copying all the records of an SCP, as designated by an area code of the numbering plan and the office code, if it is determined that the change of the mass is not for the suppression of the mass of records; and means for copying the records containing the area code of the numbering plan and the specified office code from the originating SCP to the destination SCP, if it is determined that the mass change request is for copying records.