System and method for testing a telephone data interface system

FIELD OF THE INVENTION
The present invention relates in general to the field of telecommunications and more specifically to a system and method for testing a telephone data interface system.
BACKGROUND OF THE INVENTION
Without limiting the invention, its background is described in connection with local telephone services and providers of such services. In general, the telecommunications industry has evolved into a highly competitive and sophisticated network of equipment manufacturers and service providers. Since the early 1980s, the industry has seen a shift from pure analog techniques over copper wire to digital techniques over optical fiber. Today, customers can choose from a large array of consumer telecommunications services including local and long distance calling, 800 and 900 calling accounts, TCP/IP (i.e. the "Internet") and others.
Typically, a telecommunications customer obtains access to such services by establishing an account with a service provider. The service provider, in turn, will assign to the customer a telephone number for inbound calls or provide the customer with a dial-up number for outbound calls. For example, the number can be the local telephone number where the customer can be reached such as a home or business. The number can also be the local dial-in to an automated system for a switched connection to a network element such as a domain server. Other examples include, but are not limited to, a customer's facsimile machine, cell phone number or voice mail.
At the same time industry deregulation has brought about the entry of multiple service providers within single geographic regions. In addition to competition, the number and variety of telecommunications services continues to increase. Typically, a category of service is tied to a single unique number so that any one customer may consume a host of numbers to accommodate a host of services. Thus, a common situation has evolved wherein a single customer will have a home number, an office number, a facsimile machine number, a cell phone number, an Internet account number and possibly others.
Today's service providers employ advanced information technology systems using sophisticated equipment such as routers, switches and digital cross-connects. At a minimum, the equipment must be configured to ensure calls reach their destination regardless of the service provider. While standards and communications protocols have been adopted by the industry, cooperation amongst service providers has been critical to implementing a reliable network. Today, a customer can place a clear noise free call from almost anywhere in the world.
The Public Switched Telephone Network ("PSTN") comprises the telecommunications backbone for most voice/data traffic in the world. For most local and long distance telephone calls a local telephone company acts as a local entry point to the PSTN. Typically, a Local Routing Number ("LRN") is used to route the call from a point of origination to a point of destination on the PSTN. This is true regardless of who is servicing the call at either point.
This infrastructure, however, does not always accommodate a change in the service needs of an end customer. For example, often a customer desires to switch service providers to take advantage of a more attractive rate plan. The problem lies in that the customer is not guaranteed to maintain the same local number even if the customer remains at the same location. Thus, until the present invention, there was no way to port a customer's number from one service provider to another within the same local region.
In short, as competition for communications services has grown so has the value attached to a customer's telephone number. At present, call routing is based on a number associated with the switch used to handle the local call. Moreover, service providers have not developed a means for reliable call routing when a switch from one provider to another is made. Until the present invention, the only solution was to assign a new telephone number not already in use by another customer.
While long distance carriers have enacted portability solutions on a regional or even national basis for certain classes of services, such as 800 and 900 accounts, the local portability problem has not, until the present invention, been squarely addressed. Moreover, prior art efforts at local number portability have not been widespread. For example, an industry task force was formed, pursuant to the Illinois Commerce Commission Order on Customers First Plan (Docket 94-0096 dated Apr. 7, 1995), to develop a permanent number portability solution for Illinois. While the task force made progress in defining the problem and resolving certain issues related to implementing local number portability, it did not resolve the problem on a nationwide basis. Nor did the commission establish the hardware and software interfaces required to implement a nationwide portability solution.
Thus, a need exists for a system and method of achieving local number portability on a nationwide basis. A system and method of sharing a single telephone number over different local exchange carriers would fill a void not presently addressed by the prior art.
SUMMARY OF THE INVENTION
The present invention provides a system and method for testing a telephone data interface system. The telephone data interface is tested by reading one or more data records, connecting to the telephone data interface system, connecting the telephone data interface system to a external system emulator, sending one or more messages using the one or more data records to the telephone data interface system, formatting the one or more data records into one or more formatted messages that are compatible with the external system emulator, sending the one or more formatted messages to the external system emulator, and processing the one or more formatted messages.
The present invention also provides a testing system comprising a test data source, a telephone data interface, an external system emulator, a first communications link connecting the test data source to the telephone data interface system, and a second communications link connecting the telephone data interface system to the external system emulator.
The present invention provides a hardware and software platform to effect the porting of local telephone numbers from one service provider to another. The systems and subsystems of the invention are designed to communicate with a Number Portability Administration Center and Service Management System ("NPAC/SMS") which receives and stores updated customer routing information and makes it available to participating service providers. The NPAC/SMS contains a record of all ported numbers and a history file of all transactions relating to the porting of a number.
The present invention provides a system for Local Number Portability ("LNP") that submits service orders changes to a NPAC/SMS. In this regard, a Service Order Administration ("SOA") Subsystem is provided as means of entering and submitting services order changes to the NPAC/SMS via an interface that supports the retrieval and update of subscription, service provider and network information. A graphical user interface or a message-based interface to a service provider's upstream systems is used for this purpose.
For a more complete understanding of the present invention, including its features and advantages, reference is now made to the following detailed description, taken in conjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is an overall process flow diagram for the method used to transfer a customer's port data from an old service provider to a new service provider according to one embodiment of the invention;
FIG. 2 is a high level block diagram for the interface between a Service Order Administration ("SOA"), an Interface Broadcast Agent ("IBA") and a regional number portability administration center according to one embodiment of the invention;
FIG. 3 is a block diagram of the SOA and IBA Subsystems and their interface to various business applications;
FIG. 4 is a block diagram of an alternative embodiment of the present invention with a National Network Management Center;
FIG. 5 is a block diagram of an SOA broken down into its component subsystems according to one embodiment;
FIG. 6 is a block diagram of the IBA broken down into its component subsystems according to one embodiment;
FIG. 7 is a block diagram of the IBAR broken down into its component subsystems according to one embodiment;
FIG. 8 is a block diagram of the SOA Engine broken down into its component subsystems according to one embodiment;
FIG. 9 is a block diagram of the NNMC GUI Subsystem according to one embodiment;
FIG. 10 is a block diagram of the Downstream Interface Subsystem and the Emulator Subsystem according to one embodiment;
FIG. 11 is a flow chart for the DDS Emulator Process;
FIGS. 12, 12A, 12B, 12C, 12D, 12E, 12F, 12G, 12H, 12I and 12J are flow charts for various processes in the NCS Emulator according to one embodiment;
FIGS. 13, 13A and 13B are flow charts for various processes in the MINA/SMS Emulator according to one embodiment; and
FIG. 14 is a flow chart for a ARIS Emulator according to one embodiment.

Corresponding numerals in the drawings refer to corresponding parts unless otherwise indicated.
DETAILED DESCRIPTION OF THE INVENTION
Throughout the following description, the terms "interface", "line", "lines", "link", "communications link", "inbound link" and/or "outbound link" can mean a channel, signal pathway, data path, circuit, or other similar mechanism whether physical, virtual or logical, which can be used for the transfer and communication of data by system applications and programs, whether external or internal. The terms "outbound link" and "inbound link" can also mean "pipes" in the context of the Oracle database structure and associated protocols, or "sockets" in the context of the Unix operating system structure and associated protocols. Such conventions are well known to those skilled in the art.
Turning now to FIG. 1, a flow diagram of a telephone number porting process, denoted generally as 20, is shown. In general, the telephone number porting process 20, which achieves Local Number Portability ("LNP"), is used by a customer 22 to port or transfer his or her telephone number from an old service provider 24 to a new service provider 26. The customer 22 initiates the telephone number porting process 20 by submitting a port request to either the old service provider 24 as denoted by line 32, or the new service provider 26 as denoted by line 34, to arrange the port or transfer of the customer's telephone number from the old service provider 24 to the new service provider 26. Thereafter, the old service provider 24 and new service provider 26 arrange the port details for the customer's telephone number as denoted by line 36.
Once the new service provider 26 obtains the customer's port request, the new service provider 26 notifies a Number Portability Administration Center and Service Management System ("NPAC/SMS") 30, which maintains a centralized regional number database for all customers in a given region, of the pending port as denoted by line 38. Alternatively, the old service provider 24 can notify the NPAC/SMS 30 of the pending port as denoted by line 41.
When the NPAC/SMS 30 receives the notification it performs certain validation checks. If the NPAC/SMS 30 only received a notification from one of the involved service providers, either the old service provider 24 or the new service provider 26, will notify the service provider that failed to sent a notification that the NPAC/SMS 30 is expecting such a notification. If the NPAC/SMS 30 receives the missing notification and the notifications from the two service providers 24 and 26 indicate agreement, the NPAC/SMS 30 activates the port of the customer's telephone number when the new service provider due date is reached or the new service 26 provider sends and activation notice to the NPAC/SMS 30. The NPAC/SMS 30 activates the port of the customer's telephone number by sending the new port data to the old service provider 24 as denoted by line 40, the new service provider 26 as denoted by line 42, and all other service providers 28 as denoted by line 44. This ensures proper call routing to the customer because all the service providers in the region 24, 26, and 28 can update their networking equipment accordingly.
If during the validation process described above the old service provider 24 failed to respond, the NPAC/SMS 30 will log the failure to respond and allow the new service provider 26 to proceed with the port when the due date is reached. On the other hand, if it was the new service provider 26 that failed to respond, the NPAC/SMS 30 will log the failure to respond, cancel the notification and notify both service providers 24 and 26 of the cancellation. If there is any disagreement among any of the service providers 24, 26 or 28 as to who will provide the new service to the customer 22, the NPAC/SMS 30 will place the notification in a "conflict" state and notify the conflicting service providers 24, 26 or 28 of the conflict status. The conflicting service providers 24, 26 or 28 will determine who will serve the customer 22 using appropriate internal conflict resolution procedures. If the conflict is resolved, the NPAC/SMS 30 will remove the notification from the "conflict" once it is notified of the resolution and the process proceeds normally as described above. Alternatively, the new service provider 26 can cancel the port request.
The present invention incorporates significant advantages over the prior art in that it allows for the sending and receiving of porting data from regional databases, which are maintained at the NPAC/SMS 30, and provides a smooth transition from the old service provider 24 to the new service provider 26.
Turning now to FIG. 2, a block diagram of a system for achieving local number portability is shown and denoted generally as 46. The NPAC/SMS 30 is communicably linked to two functional subsystems, a Service Order Administration ("SOA") Subsystem 48 and an Interface Broadcast Agent ("IBA") Subsystem 50 via communication interfaces 52 and 54, respectively.
The SOA Subsystem 48 is the application responsible for sending the customer's port data from one service provider to another service provider. Likewise, the IBA Subsystem 50 is the application responsible for receiving, processing, storing and transmitting customer port data to the local networks. The SOA 48 and IBA 50 Subsystems work together with the NPAC/SMS 30 to send and receive customer porting data from regional call routing centers and data sources to more centralized information sources and applications. This configuration 46 provides a distributed architecture that allows the porting of data to the local applications and networking equipment maintained by service providers for appropriate call routing and processing.
The SOA Subsystem 48 is communicably linked to one or more local applications 56, which are maintained by the local service provider. Examples of the local applications 56 include, but are not limited to, residential and business lines for voice, data and fax communications. The local applications 56, in turn, are communicably linked and used by the customer Order Entry and Order Processing ("OE/OP") systems of other service providers 58, other Complex Local Exchange Carriers ("CLEC") 60, and other Local Exchange Carriers ("LEC") 62, depending on the existing network of service providers. The SOA Subsystem 48 acts as an intermediary between the local applications 56 and the NPAC/SMS 30, thus providing a smooth non-intrusive solution for local number portability.
Likewise, the IBA Subsystem 50 provides the interface between the regional NPAC/SMS 30 and a plurality of other network entry systems 64, 66 and 68. The specific functionality of the network entry systems 64, 66 and 68 may vary, but in general, they form a platform for receiving, storing, and routing customer port data. Examples of services that use the port data include local and long distances networks and 800 services.
For example, business applications 68 can comprise a database of records for all provider systems needing access to the customer porting data, such as the Automatic Number Identifier ("ANI") reference information system. The local network interfaces 66 can be an intelligent network architecture that supports routing queries during call processing. The network interface 64 can include the Metro Intelligent Network Architecture that forms a tie-in into available communications services. Such services may include an 800 or 900 service or other similar offerings that may require access to the port data through a regional toll switch network from the NPAC/SMS 30 for correct call servicing and routing.
Turning now to FIGS. 3 and 4, the interaction between the NPAC/SMS 30, the SOA Subsystem 48 and the IBA Subsystem 50 will be described. The Local Number Portability System of FIG. 3 is denoted generally as 70, whereas the Local Number Portability System of FIG. 4 is denoted generally as 92. Local Customer Order Entry and Order Processing ("OE/OP") Systems (collectively referred to as the "Front End") 78 send and receive LNP transactions or messages to and from a local SOA Engine 80. which is an interface that routes the LNP transactions or messages to their appropriate destinations, such as the Regional SOA Subsystems 72 located in various parts of the country. In the case of FIG. 4, the SOA Engine 80 also receives and sends LNP transactions or messages from and to a SOA Graphical User Interface ("GUI") 94, and routes database queries to the RIBA 76 and IBAR 86 Subsystems. Tne Regional SOA 72 and SOA Engine 80 Subsystems form the SOA Subsystem 48, which provides the means for submitting customer service order changes to the Regional NPAC/SMSs 74.
Each Regional SOA Subsystem 72 is connected to a corresponding Regional NPAC/SMS 74 by communication interface 82, and all of the Regional NPAC/SMSs 74 form the NPAC/SMS 30. Similarly, each Regional NPAC/SMS 74 is connected to a corresponding RIBA Subsystem 76 by communication interface 84. Communication interfaces 82 and 84 conform to recognized industry standards, such as the North American Council Functional Requirements Specifications and the current version of the "NPAC/SMS Interoperable Interface Specification" by Lockheed Martin IMS Corporation. Communication interface 82 utilizes a Common Management Interface Protocol ("CMIP") and communication interface 84 utilizes both CMIP and File Transfer Protocols ("FTP").
Preferably some method of access control is provided to manage security issues that arise from communications between the SOA 32 and RIBA 34 Subsystems and the NPAC/SMS 74. In one embodiment, an access control field is included in messages flowing between the SOA 32 and RIBA 34 Subsystems and the NPAC/SMS 74 and carries a digital signature. As is known by those skilled in the art, a digital signature is used for authentication purposes to guarantee the identity of the message sender. For example, the access control field can include the following information:
System ID: An identifier for the system that is using the interface. This is a key element in the authentication process. While it is passed in each Protocol Data Unit, it is only really important in the association establishment.
System Type: Identifies the kind of system that is connecting: SOA, IBA, SOA and IBA or NPAC.
User Id: An optional field that passes a user Id used mostly for logging.
List Id: This is an integer that identifies the list from which a key was chosen to create the signature.
Key Id: This is an integer that identifies which key from the 1000 keys in a list was used to generate a signature.
CMIP Departure Time: This is the time at which a message was sent.
Sequence Number: This is 32 bit unsigned integer that starts at 0 and is incremented until wrapping at the maximum value.
Signature: The signature field contains the MD5 hashed and encrypted System Id, the System Type, the User Id, the CMIP Departure Time, and Sequence Number without separators between those fields or other additional characters. Encryption is done using RSA encryption using the key from the key list specified. Validation of this field ensures data integrity and non-repudiation of data.
Association Functions: These are set of flags that are set when an association is established.
Recovery Mode: The recovery mode flag is used to recover after downtime.
The NPAC/SMS 30 then relays the port data in a predefined message format to the IBA Subsystem 50 through interfaces 84. Like the SOA Subsystem 48, the IBA Subsystem 50 comprises a plurality of Regional IBA Subsystems 76 that update a single IBAR Subsystem 86. As shown in FIG. 3, the IBAR Subsystem 86 is accessible by a plurality of downstream applications, such as business applications 88, and network provisioning and configuration systems 90. It should be understood, however, that any type of downstream system can be connected to the IBAR Subsystem 86 at the option of the service provider. In this way the porting data is distributed to existing network applications, such as long distance and local business, for proper call routing and processing. Similarly, FIG. 4 depicts the IBAR Subsystem 86 sending LNP data to four specific Request Processing Applications (88 and 90 of FIG. 3): an ANI Reference Information System ("ARIS") 96, Metro Intelligent Network Administration Service Management System ("MINA/SMS") 98, Network Control System ("NCS") 100 and Provisions Voice Network ("RTE7") 102.
Moreover, FIG. 4 depicts, several additional communication interfaces between the major subsystems of the LNP System 92: database access interface 104 between the Regional SOA 72 and RIBA 76 Subsystems; database access interface 106 between the RIBA 76 and SOA Engine 80 Subsystems; and database access interface 108 between the SOA Engine 80 and IBAR 86 Subsystem. A National Network Management Center ("NNMC") 110 is also shown.
The NNMC 110 is a stand-alone subsystem designed for basic querying of database information on the SOA 72 and IBAR 86 Subsystems. Accordingly, the NNMC 110 is connected through communication interfaces to the various databases in the LNP System 92: the SOA Engine Subsystem 80 through database access interface 114; the SOA Subsystem 72 through database access interface 116; and the IBAR Subsystem 86 through database access interface 118. An end-user can initiate a query using a NNMC GUI 112, which is connected to the NNMC 110. By entering a single telephone number and the database to query, either the SOA 126 (FIG. 5) or IBAR 172 (FIG. 7) Databases, an end-user can obtain such information as the LRN, effective date, service provider, action, status and telephone number range.
While FIGS. 3 and 4 depict the use of three (3) Regional SOA Subsystems 72, three (3) Regional NPAC/SMSs 74, and three (3) Regional IBA Subsystems 76, it is envisioned that each region providing local number portability, regardless of number, will have a corresponding SOA Subsystem 72, NPAC/SMS 74 and Regional IBA Subsystem 76. Moreover, while FIGS. 2, 3 and 4 illustrate various embodiments for achieving local number portability, it should be understood that other architectures may be similarly conceived and reduced to practice upon reference to this disclosure. It is anticipated therefore, that such other embodiments are well within the scope and spirit of the present invention. For example, FIGS. 5 through 8 disclose a detailed architectural design, in the form of block diagrarns, for various subsystems that may be used to achieve local number portability in a preferred embodiment of the present invention.
Turning now to FIG. 5, the SOA Subsystem 72 is shown broken down into its functional components. LNP transactions, also referred to as messages or requests, originating either from the SOA Engine Subsystem 80 or an SOA GUI 94 are received through stored procedures 120, such as those used in an Oracle database structure. The stored procedures 120 send the message through a single outbound link 122 to a SOA Message Handler 124. Note that throughput can be increased by running multiple instances of the SOA Message Handler 124, each instance receiving messages from the single outbound link 122.
The SOA Message Handler 124 organizes and processes the messages by tasks that are preferably broken down at an object level, e.g., Subscription Version, Audit, Service Provider and Network. Based on a message identifier, the SOA Message Handler 124 queries the SOA Database 126 to collect and assemble any additional information required by the NPAC/SMS 74. The SOA Message Handler 124 then sends the message to the CMIP Manager 128, which is a distributed systems generator that implements the interface between the SOA Subsystem 72 and the NPAC/SMS 74, and waits for a response from the CMIP Manager 128, such as success, failure or timeout. The CMIP Manager 128 then logs and sends the message to the NPAC/SMS 74.
When the CMIP Manager 128 receives a response from the NPAC/SMS 74, the response is routed to the SOA Message Handler 124, which processes any information received with the response and updates the SOA Database 81 when required. The SOA Message Handler 124 then sends the response through an inbound link 130 to the stored procedures 120 and out to the originating SOA Engine Subsystem 80 or SOA GUI 94. All output to the stored procedures 120 is done through separate inbound links 130, one for each SOA GUI 96.
The SOA Database 126 is used to store and maintain the current telephone number information for a customer. Table 1 below is domain field listing for an SOA Database 126 according to one embodiment:
TABLE 1__________________________________________________________________________Domain List for one Embodiment of the SOA Databse 126.Name Code Label Type__________________________________________________________________________BillingIdentifier BILLING.sub.-- ID Billing Identifier VARCHAR2(4)BooleanIndicator BOOL.sub.-- IND Boolean Indicator NUMBER(1)City CITY VARCHAR2(20)CLASS DPC CLASS.sub.-- DPC VARCHAR2(9)CLASS SSN CLASS.sub.-- SSN NUMBER(3)CNAM DPC CNAM.sub.-- DPC VARCHAR2(9)CNAM SSN SNAM.sub.-- SSN NUMBER(3)ContactType CONTACT.sub.-- TYP Contact Type VARCHAR2(2)Country COUNTRY VARCHAR2(20)EndUserLocationType END.sub.-- USER.sub.-- LOC.sub.-- TYPE VARCHAR2(2)EndUserLocationValue END.sub.-- USER.sub.-- LOC.sub.-- VALUE VARCHAR2(12)Identifier ID NUMBER(10)Identifier ID2 NUMBER(10)ISVM DPC ISVM.sub.-- DPC VARCHAR2(9)ISVM SSN ISVM.sub.-- SSN NUMBER(3)LIDB DPC LIDB.sub.-- DPC VARCHAR2(9)LIDB SSN LIDB.sub.-- SSN NUMBER(3)LNPtype LNP.sub.-- TYPE NUMBER(1)LRN LRN VARCHAR2(10)NPA NXX NPA.sub.-- NXX NPA-NXX VARCHAR2(6)NPA NXX NPA.sub.-- NXX2 NPA-NXX VARCHAR2(6)OperationAction OPER.sub.-- ACT Operation Action NUMBER(3)Postal Code PC Postal Code VARCHAR2(40)ServProvID SP.sub.-- ID VARCHAR2(4)ServProvID SP.sub.-- ID2 VARCHAR2(4)StateProvince STATE.sub.-- PROV State/Province VARCHAR2(2)Status STATUS Status Flag NUMBER(10)System Type SYSTEM.sub.-- TYPE NUMBER(1)TelephoneNumber TN Telephone Number VARCHAR2(10)Timestamp T2 DATETimestamp T DATETunableName TUNABLE.sub.-- NAME Tunable Name VARCHAR2(40)TunableValue TUNABLE.sub.-- VALUE Tunable Value VARCHAR2(40)UserIdentifier USER.sub.-- ID VARCHAR2(30)Zip ZIP VARCHAR2(9)__________________________________________________________________________
The Process Monitor creates separate instances, SOA Process Monitor 132 and RIBA Process Monitor 167, which are the parent processes for the SOA 72 and RIBA 76 Subsystems and watch over all of the standard applications or processes required to run the Subsystems 72, 76. The SOA Process Monitor 132 and RIBA Process Monitor 167 keep a table of all applications or processes spawned and operational information about each application, such as the exit status of each application. The SOA Process Monitor 132 does not, however, monitor the IBA Subscription Version Report 140 or the SOA Converter Process 142. The SOA Process Monitor 132 starts applications when they are required and is notified if an application terminates. If an application, which is intended to always be running terminates, such as the CMIP Manager 128 and Check Link 134. The SOA Process Monitor 132 will automatically restart the terminated application.
A Resynch Subscription Version Process 136 is coupled to the SOA Database 126 and it is used to synchronize the SOA Subsystem 72 after a period of downtime. The Resynch Subscription Version Process 136 is started after the CMIP Manager 128 binds to the NPAC/SMS 74. In operation, the Resvnch Subscription Version Process 136 requests from the NPAC/SMS 74, by way of the CMIP Manager 128, all subscription versions that have a modification time-stamp more recent than the last time the CMIP Manager 128 had an association with the NPAC/SMS 74. The Resynch Subscription Version Process 136 also sets a downtime flag in an audit database table to indicate that an audit was ongoing during a period of downtime.
The CMIP Manager 128 also receives notifications from the NPAC/SMS 74. These notification transactions are sent to an Unsolicited Event Handler 138 which, in turn, processes the transactions and updates the SOA Database 126 when necessary. The Unsolicited Events Message Handler 138 waits for a message to be sent from the CMIP Manager 128. When the Unsolicited Events Message Handler 138 receives a message from the CMIP Manager 128, the Unsolicited Events Message Handler 138 determines the type of message and performs the required actions for that message type. When the action is complete, the Unsolicited Events Message Handler 138 formats and sends a reply to the CMIP Manager 128, which translates the message into a CMIP event and sends the event to NPAC/SMS 74.
The IBA Subscription Version Report 140, which is monitored and controlled by the operator, is used to report discrepancies between the SOA Database 126 and the RIBA Database 144, which is located in the Regional Interface Broadcast Agent ("RIBA") Subsystem 76. The Check Link 134 monitors the physical connection between the SOA Subsystem 72 and NPAC/SMS 74 so that if the physical connection is broken, the Check Link 134 will reset the SOA Subsystem 72.
The SOA Converter Process 142 is a stand-alone process for NPA-NXX Split processing that performs a conversion of the telephone number value in the SOA Subscription Version table. Using tunable database links, the SOA Converter Process 142 accesses the NPA Split table in the IBAR Database 172 (FIG. 7) to determine the NPA-NXXs that are splitting, and their Permissive Dialing Periods ("PDPs"). At the start of a PDP, for a given NPA-NXX, the SOA Converter Process 142 performs a telephone number conversion. Each Subscription Version is retrieved from the SOA Database 126 to determine if the telephone number contains the old NPA-NXX. If so, the telephone number is modified to the new NPA-NXX. Other processes within the SOA Subsystem 72 continue processing during the conversion.
Turning to FIG. 6, the Regional Interface Broadcast Agent ("RIBA") Subsystem 76 is broken down into its functional components. In general, the RIBA Subsystem 76 provides the interface between the NPAC/SMS 74 and the Interface Broadcast Agent Repository ("IBAR") Subsystem 86. When the NPAC/SMS 74 sends a message to the RIBA Subsystem 76, it is received by the RIBA Agent 146, which validates and strips the message of protocol related information. The RIBA Agent 146 then determines where the message is addressed to and sends the data to the appropriate application.
Messages from the NPAC/SMS 74 that request operations to be performed on tables within the RIBA Database 144, such as SET, CREATE and DELETE, are sent to RIBA Message Handlers. FIG. 6 illustrates the use of four (4) RIBA Message Handlers, each handling CMIP messages for a specific object type and performing updating operations on tables within the RIBA Database 144: a Subscription Version Message Handler 148: a Network Message Handler 150; a LRN Message Handler 152; and a NPA-NXX Message Handler 154. When the appropriate RIBA Message Handler, either 148, 150, 152 or 154, accepts the message, the data is then extracted from the message and the operation is determined. An SQL statement is built for the action using the data values extracted from the message. The SQL statement is then performed, which updates the RIBA Database 144.
The FTP Network Download 162 and FTP Subscription Version Download 164 applications can update or restore the RIBA Database 144 and IBAR Database 172 from the NPAC/SMS 74 via FTP/TCPIP. These FTP applications 162 and 164, which are controlled by an operator, read the subscription version and service provider network information from the NPAC/SMS 74 via FTP/TCPIP to form a flat file and update the appropriate database tables with the new information. These activities should be appropriately logged.
Upon startup, the IBA Agent 146 uses the Database Query process 166 to read each data item (subscription version, service provider network, LRN, and NPA-NXX information) from the RIBA Database 144 and loads them into memory. These data items form the Managed Instance Tree ("MIT"), which is used by the RIBA Subsystem 76 as reference points to the stored data during its operation. Once the load has been completed, the RIBA Agent 146 binds to the NPAC/SMS 74 and sends a download and recovery complete transaction to desynchronize the RIBA Subsystem 76. When the bind has been successfully established, the RIBA Agent 146 requests that the NPAC/SMS 74 download all of the subscription, NPA-NXX and LRN data which was accumulated during the time that the IBA Agent 146 was not bound to the NPAC/SMS 74. Upon successful completion of the download, the RIBA Agent 146 informs the NPAC/SMS 74 that the download has been completed and normal processing resumes.
The RIBA Agent 146 also receives notification, recovery complete and action transactions, which are forwarded to the appropriate logging utilities: a Notification Logger 156; a Recovery Complete Logger 158: and an Action Logger 160. These logging utilities, 156, 158 and 160, perform actions that are common to the RIBA log and notification programs. These procedures are contained in a separate program file and linked with the log and notification programs. When changes are required in the utility functions, these changes only need to be made in one place and the programs recompiled. These utilities process and handle the transactions and update the RIBA Database 144.
In use, the NPAC/SMS 74 sends variable length create requests to the RIBA Agent 146 consisting of subscription data and a list of one or more telephone numbers for each subscription data element. The RIBA Agent 146 extracts the create request from the CMIP message and formats it into a structure suitable for use by the Action Logger 146 which, in turn, extracts the subscription version data from the structure. The Action Logger 146, which communicates directly with the RIBA Agent 146, is started by the Process Monitor 132 at the request of the RIBA Agent 146.
The Notification Logger 156 is used to log notifications received by the RIBA Agent 146. In this way, the NPAC-SMS Operational Information and Version New NPA-NXX notifications are logged. The RIBA Agent 146 receives these notifications from the NPAC/SMS 74, formats the information into a usable structure and forwards the structure to the Notification Logger 156 over a UNIX socket. The Notification Logger 156 is started by the Process Monitor 132 at the request of the RIBA Agent 146.
The Recovery Complete Logger 158 is used to log Recovery Complete Replies and Download Replies sent by the NPAC/SMS 74 to the RIBA Agent 146. The RIBA Agent 146 receives these actions from the NPAC/SMS 74, formats the information into a usable structure and forwards the structure to the Recovery Complete Logger 156 over a UNIX socket. The Recovery Complete Logger 156 is started by the Process Monitor 132 at the request of the RIBA Agent 146.
Table 2 is a domain field listing for an the IBA Database 144 according to one embodiment:
TABLE 2__________________________________________________________________________Domain field list for IBA Database.Name Code Label Type__________________________________________________________________________billingIdentifier BILLING.sub.-- ID Billing Identifier VARCHAR2(4)booleanIndicator BOOL.sub.-- IND Boolean Indicator NUMBER(1)city CITY VARCHAR2(20)CLASS DPC CLASS.sub.-- DPC VARCHAR2(9)CLASS SSN CLASS.sub.-- SSN NUMBER(3)CNAM DPC CNAM.sub.-- DPC VARCHAR2(9)CNAM SSN CNAM.sub.-- SSN NUMBER(3)contactType CONTACT.sub.-- TYPE Contact Type VARCHAR2(2)country COUNTRY VARCHAR2(20)endUserLocationType END.sub.-- USER.sub.-- LOC.sub.-- TYPE VARCHAR2(2)endUserLocationValue END.sub.-- USER.sub.-- LOC.sub.-- VALUE VARCHAR2(12)identifier ID NUMBER(10)ISVM DPC ISVM.sub.-- DPC VARCHAR2(9)ISVM SSN ISVM.sub.-- SSN NUMBER(3)LIDB DPC LIDB.sub.-- DPC VARCHAR2(9)LIDB SSN LIDB.sub.-- SSN NUMBER(3)LNPtype LNP.sub.-- TYPE NUMBER(1)LRN LRN VARCHAR2(10)NPA NXX NPA.sub.-- NXX NPA-NXX VARCHAR2(6)operationAction OPER.sub.-- ACT NUMBER(3)organizationId ORGNZ.sub.-- ID ID number of an VARCHAR(3) organization, client, NPAC, regional IBA.Postal Code PC Postal Code VARCHAR2(40)servProvID SP.sub.-- ID VARCHAR2(4)stateProvince STATE.sub.-- PROV State/Province VARCHAR2(2)status STATUS Status Flag NUMBER(10)systemType SYSTEM.sub.-- TYPE N1telephoneNumber TN Telephone Number VARCHAR2(10)timestamp T DATEtunableName TUNABLE.sub.-- NAME Tunable Name VARCHAR2(40)tunableValue TUNABLE.sub.-- VALUE Tunable Value VARCHAR2(40)userIdentifier USER.sub.-- ID VARCHAR2(30)zip ZIP VARCHAR2(40)__________________________________________________________________________
The RIBA Process Monitor 167, which was previously described in reference to the SOA Subsystem 72 (FIG. 5), watches over all of the standard applications or processes required to run the RIBA Subsystem 76. The RIBA Process Monitor 167 does not, however, monitor the FTP processes 162 and 164, or the RIBA Converter Process 170. The RIBA Process Monitor 167 starts applications when they are required and is notified if an application terminates. If an application, which is intended to always be running terminates, such as the RIBA Agent 146 and RIBA Check Link 168, the RIBA Process Monitor 167 will automatically restart the terminated application. The RIBA Check Link application 168 monitors the physical connection between the RIBA Subsystem 76 and NPAC/SMS 74. If the physical connection is broken, the RIBA Check Link 168 will reset the RIBA Subsystem 76.
The RIBA Converter Process 170 is a stand-alone process for NPA-NXX Split processing that performs a conversion of the telephone number value in the RIBA Subscription Version table. Using tunable database links, the RIBA Converter Process 170 accesses the NPA Split table in the IBAR Database 172 (FIG. 7) to determine the NPA-NXXs that are splitting, and their Permissive Dialing Periods ("PDPs"). At the start of a PDP, for a given NPA-NXX, the RIBA Converter Process 170 performs a telephone number conversion. Each telephone number record is retrieved from the RIBA Database 144 to determine if the telephone number contains the old NPA-NXX. If so, the telephone number is modified to the new NPA-NXX. Other processes within the RIBA Subsystem 76 are suspended for the duration of the conversion process.
Turning to FIG. 7, the Interface Broadcast Agent Repository ("IBAR") Subsystem is shown and denoted generally as 86. A particularly advantageous aspect of the present invention is that it provides interfaces from the IBAR Subsystem 86 to internal systems operated by the individual service providers. FIG. 7 illustrates four (4) proprietary downstream systems have been coupled to the IBAR Subsystem 86 for receiving data. The NCS 100 and RTE7 102 systems manage local number portability information in the long distance environment while the MINA/SMS 98 is configured to manage local number portability information on the local service network level. Also, the ARIS 96 collects local number portability ("LNP") information for distribution to service provider business systems 68 (FIG. 2) and 88 (FIG. 3).
As such, and according to one embodiment of the invention, the IBAR Subsystem 86 supports the following features:
A facility to consolidate LNP data from the RIBA Database 144 into the IBAR Database 172.
A data distribution application that manages distribution of data to the ARIS 96, MINA/SMS 98, and NCS 100 systems. This application will track the status of transactions to each of these systems.
An on-line interface to the NCS long distance support system 100 preferably using the DECmessageQ product from Digital Equipment Corp.
An on-line interface to the MINA/SMS system 98 preferably using Service Builder System Management Interface product from Northern Telecom.
An on-line interface to the ARIS system 96 preferably using the Registry Messaging product from MCI.
A batch interface to the RTE7 long distance support system 102 using FTP.
NPA-NXX Split Processing.
The IBAR Message Handler Subsystem 174 comprises the message handlers in the RIBA Subsystem 76 (FIG. 6). As previously described, the RIBA Agent 146 receives messages containing data from the NPAC/SMS 74 (FIG. 6). These messages are then directed to the proper message handlers: Subscription Version Message Handler 148, Network Message Handler 150, LRN Message Handler 152, and NPA-NXX Message Handler 154. These message handlers process the messages and data in block 176 (not explicitly shown in FIG. 6) and stores the data in the RIBA Database 144. The IBAR Message Handler Subsystem 174 also inserts the data into a feeder table which will be read by the IBA Queue Processing Subsystem 178.
The IBA Queue Processing Subsystem 178, which is responsible for sending all changes received by the RIBA Database 144 to the RIBA/IBAR Interface Subsystem 182, reads the data from the feeder table and tags each message with a tracking number before it is put into the Message Queue 180. As will be described below, the tracking number ensures that the messages are delivered in sequential order.
The RIBA/IBAR Interface Subsystem 182 is responsible for keeping the IBAR Database 172 up to date with the changes that are made in the RIBA Database 144. The RIBA/IBAR Interface Subsystem 182 includes a database update application 184 that reads and processes the messages from the Message Queue 180. During processing, the underlying message data is acquired and organized by tasks, which are broken down at the "object" level (i.e. Telephone Number, Audit, Service Provider, and Network). The database update application 184 then updates the appropriate database fields in the IBAR Database 172 with the "object" data and calls stored procedures 186 to populate dedicated links 188, 190 and 192 with the information stored in the IBAR Database 172.
To ensure that duplicate messages are not processed, the RIBA/IBAR Interface Subsystem 182 verifies that each message read from the Message Queue 180 is the next consecutively numbered message. The RIBA/IBAR Interface Subsystem 182 also provides the ability to track messages from any RIBA Subsystem 76 by recording all tracking numbers associated with each RIBA Subsystem 76 and its associated record in the IBAR Database 172.
At the end of a successful transaction, the RIBA/IBAR Interface Subsystem 182 sends a response to the Response Queue 181 for each message received from Message Queue 180 as to whether it was successfully applied, rejected due to validation errors, or needs to be resent to the Message Queue 180. The IBA Queue Processing Subsystem 178 reads the responses from the Response Queue 181, processes them, and makes the appropriate updates to the table. For example, if the tracking number is out of sequence, the RIBA/IBAR Interface Subsystem 182 issues a "resend" of the specific message and any messages that have been put into the Message Queue 180 after the specific message. If, however, the specific message cannot be found in the table, the IBA Queue Processing Subsystem 178 sends a "lost" message notification and the resend process continues.
Multiple instances of the RIBA/IBAR Interface Subsystem 182 can be run to accommodate various types of NPAC/SMS 74. This allows each NPAC/SMS 74 to have different information that is to be sent to the RIBA Subsystem 76 and then to the IBAR Subsystem 86. As a result, a version ID is used to identify the type of NPAC/SMS 74 reviewing a given region so that all information can be sent to one Message Queue 180.
As mentioned above, stored procedures 186 extract data from the IBAR Database 172 and write the data to the appropriate dedicated links 188, 190 and 192. Each downstream on-line Data Distribution Application has its own dedicated link (e.g., link 188 for ARIS 96 messages, link 190 for MINA/SMS 98 messages and link 192 for NCS 100 messages). Data from each dedicated link is then read by the appropriate dedicated Data Distribution Application (e.g., application 196 for ARIS 96 messages, application 198 for MINA/SMS 98 messages, and application 200 for NCS 100 messages).
These dedicated Data Distribution Applications, which are part of the Data Distribution Subsystem 194, then send the transactions to a second set of Message Queues, each dedicated Data Distribution Application having its own dedicated Message Queue (e.g., Message Queue 202 for ARIS 96 messages, Message Queue 204 for MINA/SMS 98 messages, and Message Queue 206 for NCS 100 messages). The Message Queues 202. 204 and 208 then send the transactions to the Downstream Interface Subsystem 208, which contains an interface for each application format (e.g., ARIS Request Processing Interface 210 for ARIS 96 messages, MINA/SMS Request Processing Interface 212 for MINA/SMS 98 messages, and NCS Request Processing Interface 214 for NCS 100 messages).
Once the message has been sent to the appropriate interface in the Downstream Interface Subsystem 208, the status of the record in the IBAR Database 172 will be changed to "Sending." In addition, the Message Queues 202, 204 and 206 are continuously monitored as transactions are added to them so that any errors can be found and an alarmed can be triggered. In the event of a message failure, or a process or system failure, or during system startup, a recovery process is started and the status of the records in the IBAR Database 172 are checked. During this recovery process, all records in the IBAR Database 172 having a status of "Sending" will be resent to the Downstream Interface Subsystem 208 in the same manner as previously described. Regular processing of messages from the IBAR Database 172 to the Downstream Interface Subsystem 208 will be held up until the recovery process is complete.
In the Downstream Interface Subsystem 208, a custom request processing application for each on-line interface to a network provider's external system will read the requests from a message and facilitate the transfer over the specific interface. They will format the data as required by the interface (e.g., Northern Telecom's Service Management Interface protocol requirements) and ensure that the data is delivered across the interface. Typically, the data is sent in a synchronous manner to the network provider's external system via an ASCII based TCP/IP socket interface. The network provider's external system is responsible for queuing the data to a serial communication port. The responses received from the network provider's external system can be sent in an asynchronous manner. Although the Downstream Interface Subsystem 208 as illustrated in FIG. 7 supports four proprietary interfaces, it should be understood that any interface can be supported depending on the external system used by the service provider.
The Downstream Interface Subsystem 208 uses various mechanisms that allow the IBAR Subsystem 86 to communicate with external systems. For example, the MINA/SMS Request Processing Interface 212 is implemented as a stream of data sent via a TCP/IP socket interface using SMI protocol. The NCS Request Processing Interface 214 is implemented using the ported telephone number and request Service Provider NPA-NXX data and is set up as a two-way dialog, i.e. data is sent to the NCS 100 and the NCS 100 replies after processing the data. The ARIS Request Processing Interface 210 is implemented using the ported telephone number data and uses MCI Registry or a similar communications protocol, which is a one-way dialog, i.e. data is sent to ARIS 96, but ARIS 96 does not return confirmation after processing the data. Unlike the other Request Processing Interfaces 210, 212 and 214, the RTE7 Batch Extract 216 consists of a regularly scheduled batch job that extracts the required transactions directly from the IBAR Database 172 and writes them to a disk file 218. The resulting disk file 218 is transmitted to RTE7 102 via TCP/IP using FTP.
Using the above described Request Processing Interfaces 210, 212 and 214, a user is able to access a menu from which the user can: connect or disconnect from the NCS Message Queue: logon or logoff the MINA/SMS session; or register or deregister from the ARIS registry. In response to the user's selection, the Service Configuration and Management Application 242 sends a signal to one of three Request Processing Interfaces 210, 212 or 214. For example, in the UNIX operating environment, two signals are used: SIGUSR1 and SIGUSR2. The SIGUSR1 signal is used for "connect", "logon" and "register" commands; whereas the SIGUSR2 signal is used for "disconnect", "logoff" and "deregister" commands.
An Emulator Subsystem 220 is communicably linked to the Downstream Interface Subsystem 208 and is used for testing and validating the Downstream Interface Subsystem 208. Communication between the Downstream Interface Subsystem 208 and Emulator Subsystem 220 is accomplished using different protocols for each individual program, such as: a DEC Message Queue for the DDS Emulator 222 and the NCS Emulator 228; a UNIX TCP/IP socket library for the MINA/SMS Emulator 226; and Registry for the ARIS Emulator 224.
The Utilities Subsystem 230 contains a set of utility functions and common procedures 232 that are used to speed up the development of UNIX and SQL programs. These functions have been developed specifically for use in the IBAR Subsystem 86 application environment and provide solutions to common problem requirements such as Oracle stored procedures 184, Message Queue access, FTP access, error handling, process signal control and any other software functions that may be best implemented as a utility.
An Audit Reconciliation Subsystem 234 provides service providers interfacing with the IBAR Subsystem 86 the ability to audit their databases against the IBAR Database 172. Some service providers may consider the IBAR Database 172 to be the database of record for LNP data. The Audit Reconciliation Subsystem 234 supports both regularly scheduled and on demand audit requests. The Audit Reconciliation Subsystem 234 will support requests for subsets of the data in the IBAR database 162 as well as complete database dumps. A system administrator can schedule these requests and will manually clean out any audit files that are no longer required. Specifically, the Audit Subsystem 236 extracts the audit data from the IBAR Database 172 and writes it to a disk file 238 that can be distributed using FTP.
The Process Monitor Subsvstem 240 provides the means to start and stop the IBAR applications and includes the Service Configuration and Management Application 242, which was previously described, and a Process Manager 244. The Service Configuration and Management Application 242 provides the means to stop and restart communications between each of the real time on-line interfaces found in the Distribution Interface Subsystem 208 and its downstream server counterpart operated by the service provider. The Process Manager 244 provides the means to stop and restart the RIBA/IBAR Interface Subsystem 182, the Data Distribution Subsystem 194 and the Downstream Interface Subsystem 208. Accordingly, the Process Monitor Subsystem 244 is started at system start-up and spawns the initial IBAR applications. The Process Monitor 244 also monitors each application process and will re-start any process that terminates abnormally. In other embodiments, the Process Monitor 244 can spawn more copies of the same systems upon request. The initial information is stored in a file and loaded by the Process Monitor 244 when it is started.
The NPA-NXX Split Subsystem 246 is responsible for processing NPA splits and includes several processes: NETCAP File Access Process 248; LERG 12 File Access Process 250; Administrator Process 252; Time Trigger Process 254; Mass Duplication Process 256; Add-to-Split Process 260; Unsplit Process 262; Relief Date Modification Process 264; LRN Cleanup Process 266; and Telephone Number Cleanup Process 268. These processes are described below.
The NETCAP File Access Process 248 determines when an NPA is going to split, what the new NPA-NXX is going to be, and at what date the split will occur. The NETCAP File Access Process 248 reads the NETCAP file and updates the NPA Split table in the IBAR Database 172 as appropriate. The NPA Split table in the IBAR Database 172 is where the status of each split is tracked and is used to provide the key input for driving NPA Split processing. The NETCAP file is the primary external data source of NPA Split information and is in a mainframe dataset format that must first be retrieved via FTP or some other mainframe-to-Unix utility. Although the NETCAP File Access Process 248 is preferably a regularly scheduled daily batch job, it can also be started manually by the system operator.
More specifically, the NETCAP File Access Process 248 first determines whether the NPA-NXX in the NETCAP file is portable by looking for the NPA-NXX in the IBAR Database 172. If the NPA-NXX does not exist in the IBAR Database 172, the NPA-NXX is bypassed. If on the other hand, the NPA-NXX does exist, the NPA-NXX is deemed to be portable and the RIBA Subsystem 76 associated the NPA-NXX is determined using the Action ID in the IBAR Database 172.
The NETCAP File Access Process 248 then determines the type of record to insert, modify or delete in the NPA Split table for the portable NPA-NXX. Existing NPA Split records having a status of "Completed" are deleted. A NPA Split record having an action of "Unsplit" may also be deleted prior to the Duplication Trigger Point. If the Relief Date for a NPA split record changes before the Mass Duplication Process 256 has been run, then only the NPA Split record's Relief Date is modified and the Relief Date Modification Process is not required.
The LERG12 File Access Process 250 reads the LERG 12 file and updates the LERG 12 table in the IBAR Database 172 as appropriate. The LERG 12 file is a mainframe dataset that is downloaded as a flat file for processing and is used as a secondary external data source of NPA Split information as it pertains to LRNs. The NPA-NXXs defined in the NETCAP data serve to identify both telephone numbers and LRNs affected by a split, as it is understood that LRNs contain valid NPA-NXXs. The LERG 12 data is used for confirmation that the LRNs identified as split-affected by the NETCAP data are valid split-affected LRNs according to the LERG. The LERG 12 File Access Process 250 is preferably a regularly scheduled monthly batch job.
The LERG12 File Access Process 250 checks for the existence of a LERG 12 flat-file. If one exists, the LERG 12 table, which is used for exception reporting, is purged so that the LERG 12 flat-file data can be re-inserted in the IBAR Database 172. This effectively replaces the old data in the LERG 12 table with the new data from the LERG 12 flat-file. The LERG 12 File Access Process 250 also has the ability to designate the LERG 12 flat-file via a command-line specified filename (optional), instead of using the default provided within the program.
The Administrator Process 252 produces exception reports based on information retrieved from the IBAR Database 172, the NETCAP file and the LERG 12 file. This process is executed on demand by a systems administrator or operator.
The Time Trigger Process 254 reads the NPA Split table in the IBAR Database 172 and processes each active record according to the Action and Status attributes and other tunable parameters, such as the Duplication Trigger Point. The Duplication Trigger Point is a tunable period of time prior to the start of Permissive Dialing Period. The Time Trigger Process 254 updates the NPA Split table as appropriate and starts the following processes: the Mass Duplication Process 256, the Add-to-Split Process 260, the Unsplit Process 262, the Relief Date Modification Process 264, the LRN Cleanup Process 266, and the Telephone Number Cleanup Process 268.
The Time Trigger Process 254 is also responsible for setting a suspend flag in the IBAR Database 172 that, as will be described below, suspends the RIBA/IBAR transaction flow prior to the running of the Mass Duplication Process 256, the Add-to-Split Process 260 and the Unsplit Process 262. This ensures that all existing IBAR transactions will be processed without interruption of the incoming flow and that none of the new incoming transactions will be inadvertently bypassed during split processing. Once the Mass Duplication Process 256, Add-to-Split Process 260 and Unsplit Process 262 are complete, the Time Trigger Process 254 resets the suspend flag.
The Time Trigger Process 254 runs continuously under the control of the Process Monitor 244. At a tunable period of time and after each pass through the NPA Split table, the Time Trigger Process 254 sleeps for a short time. There will be one instance of the Time Trigger Process 254 for each RIBA Subsystem 76 to facilitate processing of the NPA Split table. Each RIBA Subsystem 76 will process only the NPA-NXXs particular to the region serviced by the RIBA Subsystem 76 and the Regional NPAC/SMS 74. Each NPA Split record is processed in a synchronous mode such that, for each NPA Split record read, a process may or may not be executed depending on its conditions, and the process will be completed before the next NPA Split record is retrieved.
The Mass Duplication Process 256 reads the IBAR Database 172 and determines which records need to be duplicated for NPA Splits. Each current record that contains the affected NPA-NXX and an action of "Activate" or "Modify" is duplicated. The duplicated records are written to the IBAR Database 172 and then sent to MINA/SMS 98 by batch file and to the NCS 100 via Oracle pipes. The duplicated records are not sent to ARIS 96. The Mass Duplication Process 256 is started by the Time Trigger Process 254 when the Duplication Trigger Point is reached for a given NPA-NXX.
The NPA Split Duplication Process 258 within the RIBA/IBAR Interface Subsystem 182 is responsible for notifying the IBA Queue Processing Subsystem 178 to suspend the RIBA to IBAR transaction flow and for duplicating incoming transactions at the appropriate time. For NPA Split processing, the NPA Split Duplication Process 258 regularly examines the suspend flag in the IBAR Database 172 that is set by the Time Trigger Process 254. When the suspend flag is set, the NPA Split Duplication Process 258 notifies the IBA Queue Processing Subsystem 178 via the Response Queue 181, which then stops sending messages from the RIBA Database 144 to the Message Queue 180. The IBA Queue Processing Subsystem 178 periodically sends a message to the RIBA/IBAR Interface Subsystem 182 prompting the NPA Split Duplication Process 258 to check on the status of the suspend flag. Once the suspend flag has been reset by the Time Trigger Process 254, the NPA Split Duplication Process 258 notifies the IBA Queue Processing Subsystem 178 via the Response Queue 181 to resume sending messages.
For duplicating incoming transactions, the NPA Split Duplication Process 258 first completes regular processing of each transaction, including committing the record to the IBAR Database 172. The NPA Split Duplication Process 258 then compares each transaction against the NPA Split table in the IBAR Database 172 to determine whether the transaction is to be duplicated or not. A transaction is duplicated if the telephone number contains an affected NPA-NXX, the action is "Activate," "Modify" or "Disconnect" and the current processing time is between the Duplication Trigger Point and the Mandatory Dialing Date. Duplicated transactions are assigned an Action ID indicating that it is a duplicate and not an original transaction.
Transactions that are duplicated during the period from the Duplication Trigger Point to the Relief Date are sent only to MINA/SMS 98 and NCS 100 via existing mechanisms. Transactions that are duplicated during the period from the Relief Date to the Mandatory Dialing Date are sent to ARIS 96, MINA/SMS 98 and NCS 100 via existing mechanisms.
The Add-to-Split Process 260 performs the same role as the Mass Duplication Process 256 in reading the IBAR Database 172 and determining which records need to be duplicated for NPA Splits. This process, however, can be triggered by the Time Trigger Process 254 at any time that the Time Trigger Process 254 retrieves an NPA Split record indicating that an NPA-NXX requires Add-to-Split processing. An Add-to-Split can occur before and during the Permissive Dialing Period, with the same, or with different, start and end Permissive Dialing Period dates.
The records duplicated by the Add-to-Split Process 260 are written to the IBAR Database 172 and then sent to MINA/SMS 98 via the regular mechanism and not by batch file, as in the case of the Mass Duplication Process 256. These duplicated records are also sent to NCS 100, but are not sent to ARIS 96.
The Unsplit Process 262 reads the IBAR Database 172 and determines which telephone numbers require a "Duplicated Disconnect" transaction, due to a NPA-NXX Unsplit. A "Duplicate Disconnect" transaction is created for each telephone number that contains an NPA-NXX that has been unsplit, and any action other than "Disconnect" or "Duplicate-Disconnect." The "Duplicate Disconnect" transactions are sent to NCS 100 via the regular method, but are not sent to the ARIS 96 or the MINA/SMS 98. ARIS 96 performs Unsplit processing of its own and MINA/SMS 98 is informed of "Disconnect" telephone numbers via E-mail.
The Unsplit Process 262 can be triggered by the Time Trigger Process 254 at any time between the Duplication Trigger Point and the Mandatory Dialing Date, if the Mass Duplication Process 256 has been run. The Time Trigger Process 254 ensures that the RIBA/IBAR incoming transaction feed is suspended prior to the running of the Unsplit Process 262.
The Relief Date Modification Process 264 reads the IBAR Database 172 and determines which records need to be updated with a new Relief Date. Each record that contains an affected NPA-NXX is updated with the new Relief Date. These modifications are not sent to ARIS 96, MINA/SMS 98 or NCS 100. The Relief Date Modification Process 264 is triggered by the Time Trigger Process 254 at any time prior to Permissive Dialing Period if the Mass Duplication Process 256 has been run.
The LRN Cleanup Process 266 reads the IBAR Database 172 and determines which records require a modification to the LRN attribute. A "Modify" transaction is created for each record that contains an LRN with an old NPA-NXX, a telephone number not containing an old NPA-NXX, and any action other than "Disconnect" or "Duplicate Disconnect." The "Modify" transactions are sent to ARIS 96, MINA/SMS 98 and NCS 100 using the regular methods. The LRN Cleanup Process 266 is triggered by the Time Trigger Process 254 to run at the LRN Clean-up Trigger Point, which is a tunable number of hours prior to the Mandatory Dialing Date.
The Telephone Number Cleanup Process 268 reads the IBAR Database 172 and determines which records require a "Disconnect" transaction. A "Disconnect" transaction is created for each record that contains an old NPA-NXX and any action other than "Disconnect" or "Duplicate-Disconnect." The "Disconnect" transactions are sent to NCS 100 using the regular methods, but are not sent to ARIS 96 or MINA/SMS 98. The MINA/SMS 98 is informed of"Disconnect" telephone numbers via E-mail. The Telephone Number Cleanup Process 268 is triggered by the Time Trigger Process 254 at the telephone number Clean-up Trigger Point which is a tunable number of hours after the Mandatory Dialing Date.
Briefly referring back to FIGS. 3 and 4, the SOA Engine Subsystem 80 uses a message-based protocol to provide an interface between the Local Customer Order Entry/Order Processing ("OE/OP") Systems (collectively referred to as the "Front End") 78 and the SOA 32 and RIBA 34 Subsystems. Thus, the SOA Engine Subsystem 80 allows the Front End 78 to upload data, audit, query and otherwise communicate with the NPAC/SMS 74.
Now referring to FIG. 8, the SOA Engine Subsystem 80 will be described in detail. The Front End Emulator Subsystem 270 includes both client and server applications, which provide the interface between the SOA Engine Subsystem 80 and the Front End 78. The client applications handle requests from the Front End 78, whereas the server applications handle reply or responses to the Front End 78. More specifically and as illustrated in FIG. 8, the client applications may include a Subscription Version Request Service 272, a Notification Request Service 274, a LRN Request Service 276, a NPA-NXX Request Service 278, an Audit Request Service 280 and a Service Provider Request Service 282. The server applications may include a Query Reply Service 284 and an Action Reply Service 286.
Each client application 272, 274, 276, 278, 280 and 282 sends request messages from the Front End 78 to an Upstream Message Listener Subsystem 300 using the appropriate Registry protocols 288, 290, 292, 294, 296 and 298. Once a client application 272, 274, 276, 278, 280 or 282 sends a request message, that client application will wait for a reply message before sending another request message.
For each request message, the Upstream Message Listener Subsystem 300 determines the particular NPAC/SMS 74 to which the request message is to be delivered to and writes the request message to the SOA Engine Database 314 using a Subscription Version Request Listener 302, a Notification Request Listener 304, a LRN Request Listener 306, a NPA-NXX Request Listener 308, an Audit Request Listener 310 and a Service Provider Request Listener 312. The appropriate Listener 302, 304, 306, 308, 310 or 312 also sends a reply message back to Front End 78 through the appropriate client application 272, 274, 276, 278, 280 or 282. The reply message indicates only that the request message has been received and queued for transmission to the appropriate NPAC/SMS 74, and does not indicate that the request message has been sent to or processed by the NPAC/SMS 74.
The SOA Engine Database 314 contains a queuing table for each type of request message. The Upstream Message Handler Subsystem 316 polls these queuing tables using a Notification Message Handler 318, a Subscription Version Message Handler 320, a LRN Message Handler 322, a NPA-NXX Message Handler 324, an Audit Message Handler 326 and a Service Provider Message Handler 328 to retrieve the appropriate records and processes them accordingly. These Message Handlers will now be described in more detail.
The Notification Message Handler 318 polls the Notification table in the SOA Engine Database 314 to retrieve all records and determines the action to be performed on each retrieved record based on the record message type and status. If the record is a new request, the information needed to create the response message will be fetched from the SOA Database 126 or the corresponding database table will be updated. As was previously described in regard to FIG. 5, the new request message is processed by the SOA Subsystem 72, sent to and processed by the NPAC/SMS 74 and a response message is created and returned containing the result of the new request message. If the record is not a new request, an error response message will be created.
The appropriate response message is then sent to the Front End 78 via Registry 330 and Query Reply Service 284, or Registry 332 and Action Reply Service 286 where it is parsed, displayed on the console, and saved to a Log file. If the Front End 78 successfully receives the response message, a confirmation message is sent back to the Notification Message Handler 318. If the confirmation message is received, the Notification Message Handler 318 deletes the record from the Notification table in the SOA Engine Database 314. Otherwise, the result status of Notification table will be updated for the request. The Notification Message Handler 318 keeps running until all the records in the Notification table are processed. If there are no more records in the Notification table, the Notification Message Handler 318 sleeps for a certain time before it wakes up and begins to poll the Notification table again.
The Subscription Version Message Handler 320 polls the Subscription Version queuing table in the SOA Engine Database 314 to retrieve all records based on a telephone number range. The Subscription Version Message Handler 320 analyzes each retrieved record and determines the action to be performed based on the record message type and status. If the record is a new message the Subscription Version Message Handler 320 calls the appropriate stored procedure 120 (FIG. 5) in the SOA Database 126. As was previously described in regard to FIG. 5, the new request message is processed by the SOA Subsystem 72, sent to and processed by the NPAC/SMS 74 and a response message is created and returned containing the result of the new request message. Once a response is received from the stored procedure 120 (FIG. 5), it is evaluated and the return code is used to update the record status in the Subscription Version queuing table and a response message is created containing the message data and header. If the record is not a new message, a "resend" message will be reissued containing only the error message header. If the record is a new message, but has been queued longer than a configurable amount of time, it will be considered to have expired and the response message is created containing an error message header.
The appropriate response message is then sent to the Front End 78 via Registry 330 and Query Reply Service 284, or Registry 332 and Action Reply Service 286 where it is parsed, displayed on the console, and saved to a Log file. If the Front End 78 successfully receives the response message, a confirmation message is sent back to the Notification Message Handler 318. If the confirmation message is received, the Notification Message Handler 318 deletes the record from the Subscription Version queuing table in the SOA Engine Database 314.
The LRN Message Handler 322 polls the LRN queuing table in the SOA Engine Database 314 to retrieve all LRN Message records. The LRN Message Handler 322 analyzes each retrieved record and determines the action to be performed based on the record message type, status and received date. If the record is a new message, the LRN Message Handler 322 calls the appropriate stored procedure (FIG. 5) in the SOA Database 126. As was previously described in regard to FIG. 5, the new request message is processed by the SOA Subsvstem 72, sent to and processed by the NPAC/SMS 74 and a response message is created and returned containing the result of the new request message. Once a response is received from the stored procedure 120 (FIG. 5), it is evaluated and a response message will be created. If the record is not a new message, the date of the record is examined. If it is expired, it will be deleted from LRN queuing table. Otherwise, an error response message will be created.
The appropriate response message is then sent to the Front End 78 via Registry 330 and Query Reply Service 284, or Registry 332 and Action Reply Service 286 where it is parsed, displayed on the console, and saved to a Log file. If the Front End 78 successfully receives the response message, a confirmation message is sent back to the LRN Message Handler 322. If the LRN Message Handler 322 receives the confirmation message, the LRN Message Handler 322 deletes the record from the LRN Message queuing table in the SOA Engine Database 314. Otherwise, the result status of the LRN Message queuing table will be updated for the request.
The NPA-NXX Message Handler 324 polls the NPA-NXX queuing table in the SOA Engine Database 314 to retrieve all NPA-NXX Message records. The NPA-NXX Message Handler 324 analyzes each record retrieved and determines the action to be performed based on the message type, status, and received date. If the record is a new message, the NPA-NXX Message Handler 324 calls the appropriate stored procedure (FIG. 5) in the SOA Database 126. As was previously described in regard to FIG. 5, the new request message is processed by the SOA Subsystem 72, sent to and processed by the NPAC/SMS 74 and a response message is created and returned containing the result of the new request message. Once a response is received from the stored procedure 120 (FIG. 5), it is evaluated and a response message created. If the record is not a new message, the date of the record is examined and if it is expired, it will be deleted from NPA-NXX queuing table. Otherwise, an error response message is created.
The appropriate response message is then sent to the Front End 78 via Registry 330 and Query Reply Service 284, or Registry 332 and Action Reply Service 286 where it is parsed, displayed on the console, and saved to a Log file. If the Front End 78 successfully receives the response message, a confirmation message is sent back to the NPA-NXX Message Handler 324. If the NPA-NXX Message Handler 324 receives the confirmation message, the NPA-N Message Handler 324 deletes the record from the NPA-NXX queuing table in the SOA Engine Database 314. Otherwise, the result status of the NPA-NXX queuing table will be updated for the request.
The Audit Message Handler 326 polls the Audit queuing table in the SOA Engine Database 314 to retrieve all request records for processing. The Audit Message Handler 326 analyzes each record retrieved and determines the action to be performed based on the message type and status. If the record is a new message, the Audit Message Handler 326 calls the appropriate stored procedure (FIG. 5) in the SOA Database 126. As was previously described in regard to FIG. 5, the new request message is processed by the SOA Subsystem 72, sent to and processed by the NPAC/SMS 74 and a response message is created and returned containing the result of the new request message. Once a response is received from the stored procedure 120 (FIG. 5), it is evaluated and the return code is used to update the record status in the queuing table and a response message is created containing the header and the message data. If the record is not a new message, the response message is created containing an error message header. If the record is a new message, but has been queued longer than a configurable amount of time, it will be considered to have expired and the response message is created containing an error message header.
The appropriate response message is then sent to the Front End 78 via Registry 330 and Query Reply Service 284, or Registry 332 and Action Reply Service 286 where it is parsed, displayed on the console, and saved to a Log file. If the Front End 78 successfully receives the response message, a confirmation message is sent back to the Audit Message Handler 326. The Audit Message Handler 326 waits until the confirmation message is received in order to delete the record from the message queuing table in the SOA Engine Database 314.
The Service Provider Message Handler 328 polls the Service Provider queuing table in the SOA Engine Database 314 to retrieve all request records. The Service Provider Message Handler 328 analyzes each record retrieved and determines the action to be performed based on the message type and status. If the record is a new message, the Service Provider Message Handler 328 calls the appropriate stored procedure (FIG. 5) in the SOA Database 126. As was previously described in regard to FIG. 5, the new request message is processed by the SOA Subsystem 72, sent to and processed by the NPAC/SMS 74 and a response message is created and returned containing the result of the new request message. Once a response is received from the stored procedure 120 (FIG. 5), it is evaluated and the return code is used to update the record status in the queuing table and a response message is created containing the header and the message data. If the record is not a new message, the response message is created containing an error message header. If the record is a new message, but has been queued longer than a configurable amount of time, it will be considered to have expired and the response message is created containing an error message header.
The appropriate response message is then sent to the Front End 78 via Registry 330 and Query Reply Service 284, or Registry 332 and Action Reply Service 286 where it is parsed, displayed on the console, and saved to a Log file. If the Front End 78 successfully receives the response message, a confirmation message is sent back to the Service Provider Message Handler 328. The Service Provider Message Handler 328 waits until the confirmation message is received in order to delete the record from the message queuing table in the SOA Engine Database 314.
The SOA Engine Converter Process 334 is a stand-alone process that is started up as is needed. It accesses the NPA Split table in the IBAR Database 172, using tunable Oracle database links to determine the NPA-NXXs that are splitting and their Permissive Dialing Periods. At the start of a Permissive Dialing Period for a given NPA-NXX, the SOA Engine Converter Process 334 performs a telephone number conversion. Each telephone number record is retrieved from the SOA Engine Database 314 to determine if the telephone number contains the old NPA-NXX. If so, the telephone number is modified to the new NPA-NXX. Other processes within the SOA Engine Subsystem 80 continue processing during the conversion.
A Common Utility Function Subsystem 336 provides a set of utility functions that are available to speed development of UNIX and SQL programs. These utility functions, which include reading startup tunable parameters 338, are developed specifically for use in the SOA Engine Subsystem 80 application environment to provide solutions to common programming requirements, such as Oracle stored procedures.
Now referring to FIG. 9, the NNMC GUI Subsystem 112 will be described. The GUI Subsystem 112 connects to the SOA Databases 126 in the SOA Subsystems 72, the IBAR Database 172 in the IBAR Subsystem 86, the SOA Engine Database 314 in the SOA Engine Subsystem 80. Access to the SOA 126, IBAR 172 and SOA Engine 314 Databases is performed via database links, which are stored in the NNMC Database 340. A table within the NNMC Database 340 tracks the number of queries performed per day, per SOA Subsystem 72 and IBAR Subsystem 86. The number of queries is limited to a tunable daily maximum before the end-user is denied access. Based on the telephone number queried, the NNMC GUI 112 uses a telephone number to NPAC cross-reference table within the SOA Engine Database 314 to determine the correct SOA Database 126 to access.
Turning now to FIG. 10, the Emulator Subsystem 220 is depicted and will be described in detail. The Emulator Subsystem 220 comprises a NCS emulator 228, a MINA SIMS emulator 226, an ARIS emulator 224 and a DDS emulator 222. The emulators 222, 224, 226 and 228 are used for testing and validating the Downstream Interface Subsystem Request Processing applications 210, 212 and 214. Communication between the Downstream Interface Subsystem Request Processing applications 210, 212 or 214 and the Emulator Subsystem applications 224, 226 and 228 is accomplished via Message Queues 366, 364 and 362 respectively. The DDS emulator 222 is connected to each of the Downstream Interface Subsystem Request Processing applications 210, 212 and 214 via Message Queues 202, 204 and 206. Test data may be entered into the DDS Emulator 222 via user interface 360.
Turning now to both FIG. 10 and FIG. 11, the processing flow diagram for the DDS emulator 222 is illustrated and will be discussed. The DDS emulator 222 is designed to provide all Downstream Interface Subsystem Request Processing applications 210, 212 and 214 with test data. The test data may be entered in a file using a common text editor and computer 360. The file may then be sent to the respective Downstream Interface Subsystem Request Processing applications 210, 212, or 214 through Message Queues 202, 204 and 206. The targeted request processing application 210, 212, or 214 may then process the test data. Test messages are then sent to the ARIS, MINA/SMS and NCS emulators 224, 226 or 228, which respond to the messages. The DDS emulator process begins in block 400 and test data for the respective Downstream Interface Subsystem Request Processing application 210, 212 or 214 is read from a file in block 402. Communication using the targeted message queue 202, 204 or 206 is initiated in block 404. A test message is sent to the Downstream Interface Subsystem Request Processing application 224, 226 or 228, in block 406. Once the test message has been sent, the connection with the message queue 202, 204 or 206 is terminated in block 408 and processing ends in block 410.
Turning now to FIG. 12, the processing flow diagram for the NCS emulator 228 is illustrated and will be discussed. NCS emulator processing begins in block 500 and the write log parameter is retrieved in block 502. The write log parameter is a flag used to define when to write messages to a log file. If the write log parameter is defined as null, as determined in decision block 434, an error is logged in block 506 and processing ends in block 508. If, however, the write log parameter is not null, as determined in decision block 504 and the write log parameter is true, as determined in decision block 510, the log file is opened in block 512 and the process header is written in block 514. If, however, the write log parameter is not true, as determined in decision block 510, or the process header has been written in block 514, the NCS initialization process is called in block 516. The NCS initialization process 516 will be described below in reference to FIG. 12A. After the NCS initialization process 516 is complete, the NCS attach queue process is called in block 518. The NCS attach queue process 518 will be described below in reference to FIG. 12B. Next, the NCS open message process is called in block 520 and will be described in reference to FIG. 12C. If any of the processes 516, 518, or 520 fail, as determined in decision block 522, an error is logged in block 506 and processing ends in block 508.
If, however, a failure did not occur, as determined in decision block 522, the NCS message receive process is called in block 524. The NCS message receive process 524 will be described below in reference to FIG. 12D. If NCS message receive 524 returns a response of failure, as determined in decision block 526, the end header for the log file is logged out in block 528, the error is logged in block 506 and the process ends in block 508. If, however, a response of failure was not returned, as determined in decision block 526, the NCS message check process is called in block 530. The NCS message check 530 will be described below in reference to FIG. 12E. Next, the NCS assemble message process is called in block 532 and will be described below in reference to FIG. 12F. Next, the NCS add list process is called in block 534 and the NCS send message process is called in block 536. The NCS add list process 534 and the NCS send message process 536 will be described in reference to FIGS. 12G and 12H, respectively. If a response of successful is returned from the NCS message send process 538, decision block 540 determines if the write log parameter is set equal to true. If the write log parameter is set to true, the response message from the NCS emulator 228 to the NCS request processing 214 is logged out in block 542. If, however, the write log parameter is not set to true, as determined in decision block 540, or the response message has been logged out in block 542, processing returns to the NCS receive message process in block 524.
If, however, a successful response was not returned by the NCS send message process 536, as determined in decision block 538, and the response was failure, as determined in decision block 544, decision block 546 determines whether the write log parameter is set equal to true. If the write log parameter is set equal to true, the end header for the log file is logged out in block 548 and processing ends in block 508. If, however, a successful or failure response was not returned by the NCS send message process 536, as determined in decision blocks 538 and 544, decision block 550 determines whether a open failure response was returned by the NCS send message process 536. If an open failure response was not returned, processing returns to the NCS receive message process in block 524. If, however, a open failure response was returned, as determined in decision block 550, decision block 552 determines whether the write log parameter is set equal to true. If the write log parameter is set equal to true, the end header for the log file is logged out in block 554, an error is logged about the open target queue error in block 556 and processing ends in block 508. If, however, the write log parameter is not set equal to true, as determined in decision block 552, processing ends in block 508.
Turning now to FIG. 12A, the NCS initialization processing 446 will be described and begins processing in block 560. Memory is allocated to copy messages in block 562. If the return value indicates a status of "Null", as determined in decision block 564, a response of failure is returned in block 566. If, however, the return status is not defined as "NULL", as determined in decision block 564, memory is allocated to send messages in block 568. If the return status indicates a value of "Null", as determined in decision block 570, a response of failure is returned in block 566. If, however, a response of "Null" was not returned, as determined in decision block 570, memory is allocated to store messages in block 572. If the return value indicates a status of "Null", as determined in decision block 574, a response of failure is returned in block 566. If, however, a return status of "Null" was not returned, as determined in decision block 574, the rear pointer equal to the start node of the internal list is initialized in block 576. If the return response of the rear pointer indicates a value of "Null", as determined in decision block 578, a response of failure is returned in block 566. If, however, a return pointer does not indicate a return value of "Null", a response of successful is returned in block 580.
Turning now to FIG. 12B, the processing flow for the NCS attach queue process 518 begins processing in block 590. Environmental parameters, such as, the message queue bus identification, the message queue group and the message queue number, are retrieved in block 592. The environmental parameters allow the NCS emulator 228 to know which message queue to attach to in order to read and respond to messages. Message queue 206 is attached to the message queuing bus of a network environment in block 594. If the message queue 206 was successfully attached to the queuing bus, as determined in decision block 596, a response of successful is returned in block 598. If, however, the message queue 206 was not successfully attached to the message queue bus, as determined in decision block 596, the console is alerted in block 600 and a response of failure is returned in block 602.
Turning now to FIG. 12C, the processing flow for the NCS open message process 520 begins processing in block 610. Parameters for the targeted message queue are retrieved in block 612. The parameters may include parameters such as; the target queue number, the target queue group, target queue timeout, the target queue retry limit and the target queue max messages in queue. If all parameters are not retrieved, as determined in decision block 614, an error is logged in block 616 and a response of failure is returned in block 618. If, however, all parameters are retrieved, as determined in decision block 614, access to the targeted message queue is initialized in block 620. If access to the targeted queue was successfully initialized, as determined in decision block 622, a response of successful is returned in block 624. If, however, access to the targeted queue was not successfully initialized, a response of failure is returned in block 626.
Turning now to FIG. 12D, where a processing flow diagram for the NCS message receive 524 is illustrated and will be discussed. NCS message receive process begins in block 630. Messages in message queue 362 are received in block 632. If the message from the message queue 362 was not successfully received, as determined in decision block 634, a response of failure is returned in block 636. If, however, a failure did not occur receiving queue message, as determined in decision block 634, decision block 638 determines if the prefix screening format is a NPA-NXX transaction. If the prefix screening format is not a NPA-NXX transaction, decision block 640 determines if the specific digit screening format is a telephone number transaction. If the specific digit screening format is not a telephone number transaction, a response of failure is returned in block 636. If, however, the prefix screening format is a NPA-NXX transaction, as determined in decision block 638, the received message is copied into the appropriate receiving structure in block 642. Next, the buffer is freed of incoming messages in block 644. If the write log parameter is set equal to true, as determined in decision block 646, the received message is logged out of the log file in block 648 and a response of successful is returned in block 650. If, however, the write log parameter is not set equal to true, as determined in decision block 646, a response of successful is returned in block 650. If, however, the specific digit screening format is a telephone number transaction, as determined in decision block 640, the received message is copied into the appropriate receiving structure in block 652. Next, the buffer is freed of incoming messages in block 654. If the write log parameter is set equal to true, as determined in decision block 656, the received message is logged out of the log file in block 658 and a response of successful is returned in block 650. If, however, the write log parameter is not set equal to true, as determined in decision block 656, a response of successful is returned in block 650.
Turning now to FIG. 12E, where a processing flow diagram for the NCS check message process 530 is illustrated and will be discussed. The NCS check message process begins processing in block 660. If the transactions identification already exists, as determined in decision block 662, a response of "duplicate exists" is returned in block 664. If, however, the transaction identification does not already exists, the record identification is checked in block 666. If the record identification does not equal the predefined value for either a telephone transaction or a NPA-NXX transaction, a response of "record ID wrong" is returned in block 668. If, however, the record identification does equal a predefined value, as determined in decision block 666, the message size is checked in block 670. If the record size value is not the record size value defined by the numerically defined digit screening format or the prefix screening format, a response of "size wrong" is returned in block 672. If, however, the record size equals the predefined size, a response of "message all ok" is returned in block 674.
Turning now to FIG. 12F, where a processing flow diagram for the NCS assemble message 532 is illustrated and will be discussed. The NCS assemble message process inputs a response record from a file, which is used to emulate the NCS's action results. The record is assembled with a header to form a response message. NCS assemble message process begins processing in block 680. The values in the response message structure are initialized in block 682. If the status identification indicates message all ok, as determined in decision block 684, the status identification of the response message is set to successful in block 686. The error count of the response message is set equal to zero in block 688 and the array error identification values are set to message all ok in block 690. Processing then returns in block 692. If, however, the status identification of the response message does not equal message all ok, as determined in decision block 684, decision block 694 determines if the status identification of the response message equals message check random. If the status identification equals message check random, the status identification of the response message is set to error in block 696. The error count of the response message is set to one in block 698. The first position value of the array error identification is set to a random value that is obtained from the NCS error found process, which will be discussed below in reference to FIG. 12K, in block 700. Processing then returns in block 692. If, however, the status identification does not equal message random check, as determined in decision block 694, decision block 702 determines if the status identification is a fixed error. If the status identification does equal a fixed error, the status identification of the response message is set to failure in block 704. The error count is set equal to one in block 706 and the first position of the array error identification is set to the error identification function parameter found from the NCS error found process in block 708. Processing then returns in block 692. If, however, a fixed error did not occur, as determined in decision block 702, processing returns in block 692.
Turning now to FIG. 12G, the processing flow diagram for the NCS add list process 534 is illustrated and discussed. NCS add list process 534 begins processing in block 710. Decision block 712 determines if the number of elements from the linked list equals a predefined maximum number. If the number of elements equals the predefined maximum number, decision block 714 determines if the number of deleted elements from the linked list equals the predefined number of deleted nodes. If the number of deleted elements does not equal the predefined number of deleted nodes, as determined in decision block 714, the corresponding node from the linked list is deleted in block 716. Processing then returns to decision block 714 to determine if the number of deleted elements equals the predefined number of deleted nodes. If, however, the number of elements from the linked list does not equal the predefined maximum number, as determined in decision block 712, or the number of deleted elements from the linked list equals the predefined number of deleted nodes, as determined in decision block 714, decision block 718 determines if the response message pointer of the rear pointer is set equal to "Null". If the response message pointer is not set equal to "Null", the required memory buffer is allocated for the required response message as the next node of the rear pointer in block 720. The response message is copied into the allocated buffer in block 722. Next, the next node pointer of the rear node is set to "Null" in block 724 and the number of nodes in the linked list are returned in block 726. If, however, the response message pointer of the rear pointer is set equal to "Null", as determined in decision block 718, the required amount of buffer memory is allocated for the required response message in block 728. The response message is copied into the allocated buffer in block 730. The next node pointer of the rear node is set to "Null" in block 732. Next, the starting node pointer is set equal to the rear pointer in block 734 and the number of nodes in the linked list are returned in block 726.
Turning now to FIG. 12H, where a processing flow diagram for the NCS send message process 536 is illustrated and will be discussed. NCS send message process begins in block 740. The test message is sent to message queue 206 in block 742. If the test message was successfully sent to the message queue 206, as determined in decision block 744, a response of successful is returned in block 746. If, however, the test message was not successfully sent to the message queue 206 an error is logged in block 748 and a response of failure is returned in block 750.
Turning now to FIG. 121, where a processing flow diagram for the NCS signal handler is illustrated and begins the NCS signal handler process in block 760. NCS signal handler process catches the SIGTERM signal, or the Ctrl C signal, and exits the program after deallocating the memory buffers of the linked list. The response messages are removed from the linked list in block 762. Message queue 362 used to receive test messages is disconnected in block 764 and processing ends in block 766.
Turning now to FIG. 12J, where a processing flow diagram for the NCS error handler is illustrated and begins the NCS error found process in block 770. If the action code is forced applied, as determined in decision block 772, the seed of the random number is set equal to the dimension of the add error identification array in block 774. The index of the random error is determined in block 776. The return error identification is set equal to the value of the add error identification array at the random determined position in block 778 and the random error identification is returned in block 780. If, however, the action code is not forced applied, as determined in decision block 772. decision block 782 determines if the action code is delete. If the action code is delete, the seed of the random number is set equal to the dimension of the delete error identification array in block 784. The index of the random error is determined in block 786. The return error identification is set equal to the value of the deleted error identification array at the random determined position in block 788 and the random error identification is returned in block 780. If, however, the action code is not delete, as determined in decision block 782, the random error identification is returned in block 780.
Turning now to FIG. 13, where a processing flow diagram for the MINA/SMS emulator process 226 is illustrated and begins processing in block 800. The global variables are initialized in block 802. These variables may include the session authentication, key host IP address, and the process identification. A server socket is created and listened to on a known port number as defined by a environmental variable is created in block 804. A connection to a client session socket is made in block 806. The MINA/SMS emulator connect client process waits indefinitely for a client connection on the server socket and then creates a session socket for passing messages between the MINA/SMS emulator 226 and the MINA/SMS request processing 212. The MINA/SMS read message process is called in block 808 and will be discussed below in reference to FIG. 13A. If the MINA/SMS read message process returned a response of successful, as determined in decision block 810, the MINA/SMS process message process is called in block 812. The response message is then written to the client session socket in block 814. If the socket write was successful, as determined in decision block 816, processing returns to block 808 where another message is read. If, however, the socket read was not successful, as determined in decision block 810, or the socket write was not successful, as determined in decision block 816, the client session socket is closed in block 818. Decision block 820 determines if a system failure or shutdown occurred during processing. If a system failure or shutdown has not occurred, processing returns to block 806. If, however, a system failure or shutdown has occurred, the server socket is closed in block 822 and processing ends in block 824.
Turning now to FIG. 13A, where a processing flow diagram for the MINA/SMS read message process begins in block 830. The SMI request message header is read in block 832. If the read was not successful, as determined in decision block 834, a response of failure is returned in block 836. If, however, the read was successful, the data size from the previously read message header is extracted in block 838 and the data portion of the SMI request message is read in block 840. If the read was not successful, as determined in decision block 842, a response of failure is returned in block 836. If, however, the read was successful, a response of successful is returned in block 844.
Turning now to FIG. 13B, where a processing flow diagram for the MINA/SMS process messages process 812 begins processing in block 850. The request message header is parsed out and an appropriate response message header is created in block 852. If the request message sent is login, as determined in decision block 854, the login request message is parsed out and a login response message is created in block 856, and processing returns in block 858. If, however, the request message sent is not login, as determined in decision block 854, decision block 860 determines if the request message is logout. If the request message sent is logout, the logout request message is parsed out and a logout response message is created in block 862, and processing returns in block 858. If, however, the request message sent is not logout, as determined in decision block 860, decision block 864 determines if the request message is force logout. If the request message sent is force logout, the force logout request message is parsed out and a force logout response message is created in block 866, and processing returns in block 858. If, however, the request message sent is not force logout, as determined in decision block 864, decision block 868 determines if the request message is database query. If the request message sent is database query, the database query request message is parsed out and a database query response message is created in block 870, and processing returns in block 858. If, however, the request message sent is not database query, as determined in decision block 868, decision block 872 determines if the request message is provision. If the request message sent is provision, the provision request message is parsed out and a provision response message is created in block 874, and processing returns in block 858. If, however, the request message sent is not provision, as determined in decision block 872, decision block 876 determines if the request message is provision update. If the request message sent is provision update, the provision update request message is parsed out and a provision update response message is created in block 880, and processing returns in block 858. If, however, the request message sent is not provision update, as determined in decision block 876, processing returns in block 858.
Turning now to FIG. 14, where a processing flow diagram for the ARIS emulation process 224 is illustrated and begins processing in block 900. The registry parameters are setup in block 902. A registry connection is established by calling registry with a register verb in block 904. Registry is called to enable the ARIS emulator to receive a message from the application interface in block 906. While messages are being received, data is extracted from the received message structure and displayed on a monitor and written to a file in block 908. If there are more messages to receive, as determined in decision block 910, processing returns to block 906 to enable the ARIS emulator. If, however, no more messages exist, the connection with the registry is terminated in block 912 and processing end in block 914.
While this invention has been described in reference to illustrative embodiments, the description is not intended to be construed in a limiting sense. Various modifications and combinations of the illustrative embodiments as well as other embodiments of the invention will become apparent to persons skilled in the art upon reference or description. It is, therefore, intended that the appended claims encompass any such modifications or embodiments.

Number	Name	Date
5384822	Brown et al.	Jan 1995
5761272	Williams et al.	Jun 1998
5787147	Gundersen	Jul 1998
5809108	Thompson et al.	Sep 1998
5896440	Reed et al.	Apr 1999

System and method for testing a telephone data interface system

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

CPC

US Classifications

Field of Search

US

International Classifications

Abstract

Description

Claims

Parent Case Info

US Referenced Citations (5)

Continuations (1)