WO1999004579A1 - System and method for achieving local number portability - Google Patents

System and method for achieving local number portability Download PDF

Info

Publication number
WO1999004579A1
WO1999004579A1 PCT/US1998/014368 US9814368W WO9904579A1 WO 1999004579 A1 WO1999004579 A1 WO 1999004579A1 US 9814368 W US9814368 W US 9814368W WO 9904579 A1 WO9904579 A1 WO 9904579A1
Authority
WO
WIPO (PCT)
Prior art keywords
customer
service
local
service provider
data
Prior art date
Application number
PCT/US1998/014368
Other languages
French (fr)
Inventor
Deborah L. Bauer
Ross Edward Button
Mike Cavanagh
Susan Jane Mcquigge Ernst
Kevin Germann
Ralph Holmes
Samuel S. Howlette
William Kayln
Steve Sauve
Francis C. Sommers
Original Assignee
Mci Communications Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Mci Communications Corporation filed Critical Mci Communications Corporation
Priority to AU83944/98A priority Critical patent/AU8394498A/en
Publication of WO1999004579A1 publication Critical patent/WO1999004579A1/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04QSELECTING
    • H04Q3/00Selecting arrangements
    • H04Q3/0016Arrangements providing connection between exchanges
    • H04Q3/0029Provisions for intelligent networking
    • H04Q3/005Personal communication services, e.g. provisions for portability of subscriber numbers
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/912Applications of a database
    • Y10S707/951Calendar or scheduling
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99931Database or file accessing
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99931Database or file accessing
    • Y10S707/99937Sorting
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99941Database schema or data structure
    • Y10S707/99944Object-oriented database structure
    • Y10S707/99945Object-oriented database structure processing
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99941Database schema or data structure
    • Y10S707/99948Application of database or data structure, e.g. distributed, multimedia, or image
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99951File or database maintenance
    • Y10S707/99952Coherency, e.g. same view to multiple users
    • Y10S707/99953Recoverability
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00Data processing: database and file management or data structures
    • Y10S707/99951File or database maintenance
    • Y10S707/99952Coherency, e.g. same view to multiple users
    • Y10S707/99955Archiving or backup

Definitions

  • TCP/IP i.e.
  • a telecommunications customer obtains access to such services by
  • the service provider in turn, will
  • the number can be the local
  • 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.
  • a network element such as a domain server.
  • Other examples include,
  • 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
  • a home number an office number, a facsimile machine number, a cell phone number,
  • the equipment must be configured to ensure calls reach their
  • PSTN Public Switched Telephone Network
  • LR Local Routing Number
  • a primary object of the present invention is to provide a hardware
  • NPAC/SMjS Network Management System
  • N AC/SMS contains a record of all ported numbers and a history file of all
  • Another object of the present invention is to provide a system for Local
  • LNP Number Portability
  • SOA Service Order Administration
  • service provider's upstream systems may be used for this purpose.
  • Another object of the present invention is to provide a facility for
  • the SOA is equipped with a host of functions for creating, canceling, acknowledging, modifying, retrieving, activating, disconnecting and removing subscription version information.
  • the SOA has an audit capability that
  • Still another object of the present invention is to provide the interface
  • the interface permits service
  • the information is accessible to all service
  • Another object of the present invention is to provide a system that interfaces
  • a new service provider can obtain authorization to port a customer using a standardized message format that notifies an old service provider
  • the NP AC/SMS performs certain validation checks, and attempts to
  • Yet another object of the present invention is to provide a means of
  • IBA Interface Broadcast Agent
  • the LBA subsystem is configured to automatically receive new network
  • the L A may also request data
  • the request can be based on time range, telephone
  • a service provider can also be any service provider.
  • the invention provides the software and hardware platforms for achieving
  • a central or regionalized database is used to keep track
  • Service providers interface with the database and obtain information at the
  • Disclosed, in one embodiment, is a system for maintaining a customer's local
  • the system uses a regional number portability subsystem
  • a service order application is communicably linked to the regional number portability subsystem and configured to send a porting
  • a local service management application is
  • management application supports the interface to the second service provider and
  • Figure 1 is an overall process flow diagram for the method used to transfer
  • Figure 2 is a high level block diagram for the interface between a Service
  • SOA Order Adrninistration
  • L A Interface Broadcast Agent
  • Figure 3 is a block diagram of the SOA and LBA subsystems and their
  • Figure 4 is a block diagram of an SOA broken down into its component
  • FIG. 5 is a block diagram of the LBA broken down into its component
  • FIG. 6 is a detailed block diagram of the Interface Broadcast Agent
  • Repository subsystem broken down into its component subsystems
  • FIG. 7 is a block diagram illustrating the Order Entry/ Order Processing interface subsystem according to one embodiment of the invention. Corresponding numerals in the drawings refer to corresponding parts unless
  • process 10 is shown.
  • process 10 is used by a
  • LNP Local Number Portability
  • link 13 link 15 represents the communications link
  • service provider 16 communicate via link 17 with each other in order to arrange a
  • NP AC/SMS Network Management System
  • an interface is W wO 9 v9 y / / 0 ⁇ 4 «57 / 9 PCT/US98/14368
  • a customer's port request is communicated to either the customer's old
  • FIG 2 a block diagram of a system for achieving local
  • FIG. 1 shows that the regional NP AC/SMS 18 is communicably linked to two functional sub-systems, a Service Order Administration (“SOA”) sub-system 32 and an Interface Broadcast Agent (“LBA”) sub-system 34 via communications links 33 and 35, respectively.
  • SOA Service Order Administration
  • LBA Interface Broadcast Agent
  • the SOA 32 is the responsible application that sends the customers port data
  • the LB 34 is the
  • the SOA 32 and LBA 34 work together with the NP AC/SMS 18 to send and receive
  • This configuration 30 provides a
  • the SOA 32 is communicably linked to one or more local
  • local apphcations 36 include, but are not limited, to local residential and
  • the local applications 36 are communicably linked and
  • the LBA 34 provides the interface between die regional NP AC/SMS 18 and a plurality of other network entry systems such as those shown in boxes 44,
  • business applications 48 can comprise a database of records for
  • network interfaces 46 can be an intelligent network architecture that supports routing
  • An example of a network interface 44 would include
  • Such services may include an 800 or 900 service or other
  • FIG. 4 a diagram illustrating the interaction between the SOA 32 and IBA 34
  • local level are represented at 62, which as shown is coupled to local SOA engine 58.
  • the SOA engine 58 feeds customer telephone information into the regional SO As
  • the SOA sub-system 32 comprises the regional SOAs
  • each region providing local number portability will have a
  • the LBA sub-system 34 comprises a plurality of regional LB As 56
  • the LBA repository 60 is accessible by a plurality
  • downstream applications such as business applications 64 and network
  • provisioning and configuration systems 66 It should be understood, however, that
  • any type of downstream system can be connected to the LBA repository 60 at the
  • the SOA subsystem 32 provides the means for submitting customer service order changes to the NP AC/SMS 18. Turning now to figure 4, the SOA 32 is shown
  • the stored procedures 82 place the transaction information into the outbound
  • the SMH 86 queries the SOA Database 81 for any
  • the SMG 98 also receives notifications from the NP AC/SMS 18.
  • RSP Resynch Subscription Version Process
  • the RSP 18 requests from the NP AC/SMS 18 all subscription
  • the RSP 88 also sets a downtime
  • the IBA Subscription Version Report ("ISVR") 92 is used to report
  • Link 96 monitors the physical connection between the SOA 32 and NP AC/SMS 18.
  • the Process Monitor 94 monitors the ISVreport 92.
  • the Process Monitor 94 monitors the ISVreport 92.
  • Process Monitor 94 is notified.
  • the Process Monitor 94 automatically restarts
  • the Process Monitor 94 is the parent process for
  • the Process Monitor 94 will watch over ail of
  • the SOA Message Handler 86 allows the GUI component ofthe SOA 32 to
  • SOA Message Handler 86 are run to allow for greater diroughput wherein each such
  • instance ofthe SOA Message Handler 86 receives requests from a single outbound
  • the SOA Message Handler 86 receives messages from the GUI via the GUI
  • outbound link 84 Messages are processed, data acquired and organized by tasks
  • Message Handler 84 is configured to collect and assemble the information required
  • messages are relaved to a DSET Distributed Systems
  • DSG DSG Generator
  • the UNIX sockets are used for the interface between d e LBA Agent 112 (See
  • the SOA subsystem 32 processes any data received with the
  • Unsolicited Events Message Handler 90 is used by die SOA subsystem
  • Message Handler 90 starts up by making a connection to the UNIX sockets and then
  • SOA Database 81 is used to store and maintain the current
  • Table 1 is domain field listing for an
  • SOA Database 81 according to one embodiment:
  • Table 1 Domain List for one Embodiment of the SOA Database 81.
  • RLBA 56 provides the
  • LBAR LBAR 110.
  • requests are formatted using a
  • CMLP Common Message Management Information Protocol
  • LMH Handlers 114, 122, 124, 126 or 128.
  • LMH Handlers 114, 122, 124, 126 or 128.
  • four (4) LMHs are used,
  • Each LMH 122, 124, 126 and 128 handles the CMLP requests which are
  • the LBA Agent 112 also receives
  • die LBA Agent 112 Upon startup, die LBA Agent 112 reads each data item (subscription version,
  • LRN LRN, NPA/NXX, etc.
  • MIT Managed Instance Tree
  • the LB Agent 112 binds to the NP AC/SMS 18. When the bind has been
  • the IBA Agent 112 requests that the NP AC/SMS 18
  • the LBA Agent 112 informs the NP AC/SMS
  • d e LBA Database 102 is updated from files using the
  • FTP File Transfer Protocol
  • applications 130 and 132 are controlled by an operator which involves the steps of
  • Table 2 is a domain field listing for an die LBA Database 102 according to
  • Monitor 134 is responsible for invoking applications when they are required and if
  • Recovery Complete Logger 118 or LBA Action Logger 120 Each of the logging applications 116, 118, 120 handle the transactions and update the LBA Database 102.
  • the IBA Database 102 can also be updated from flat files by the FTP
  • the Check Link application 136 monitors the physical connection between the
  • Process Monitor 134 is the parent process for both the SOA 32 and RLBA 56
  • LBA Message Handlers 122, 124, 126 and 128 are used to
  • the LMHs 122, 124, 126 and 128 also receive messages from the NP AC/SMS
  • NP AC/SMS 18 sends a message to the RLBA 56, it is received by die DSET DSG
  • Agent determines which ofthe four LMH applications (Service Provider 124, NAP-
  • the Network Download File Transfer Protocol 132 is used to restore the LBA Database 102 and LBAR 110 from the NP AC/SMS 18 via FTP/TCPLP.
  • die 110 provides a means for holding and distributing the data received from die NP AC/SMS 18 to all the various downstream systems maintained by die service W wOu 9 y 9 y /0 i ro4579y PCT/US98/14368
  • the Subscription Version Download File Transfer Protocol 130 may also be logged.
  • the Subscription Version Download File Transfer Protocol 130 may also be logged.
  • the activities from the download file transfer are performed using FTP/TCPIP.
  • the activities from the download file transfer are:
  • the NP AC/SMS 18 sends variable length create requests to the CMLP
  • Agent 112 consisting of subscription data and a list of one or more telephone
  • the CMLP Agent 112 extracts die create
  • LBA Action Logger 112 which, in turn, extracts the subscription version data from
  • the LBA Notification Logger 116 is used to log notifications received by the
  • the CMLP Agent 112 receives
  • the LBA Notification Logger 116 is started by the Process Monitor 134 at
  • the LBA Recovery Complete Logger 118 is used to log Recovery Complete
  • the IBA Agent 112 receives these actions from die NP AC/SMS 18, formats the
  • NCS ⁇ T Network Control System
  • RTE7 Radio Service
  • MLNA/SMS Network Adrmnistration Service Management System
  • ARIS ANT Reference Information System
  • LNP portability
  • d e LBAR 110 d e LBAR 110
  • a data distribution application that manages distribution of data to die
  • a database update application (the RII subsystem) reads the
  • a stored procedure extracts data from me LBAR 110 and
  • the Process Monitor 134 provides the means to start and stop the
  • LBA Queue Processor 150 is responsible for sending all the changes that die RLBA
  • the subsystem 56 receives from the NP AC/SMS 18 to the LBAR 110.
  • subsystem 150 is also responsible for ensuring all records of transactions on the
  • RIB A 56 are delivered to the BAR 110.
  • the IQP subsystem 150 processes records from a specific
  • the IQP The IQP
  • subsystem 150 will process all responses from the BAR system 110 and make the
  • the IQP subsystem 150 numbers each message
  • the BAR 110 verifies that the message read is d e next
  • die BAR 110 responds to each message sent as to
  • the R A to AR Interface (“RU") 154 is responsible for keeping the BAR 110 up to date with the changes that occur on the RBA 56.
  • the RE 154 receives messages from a RBA 56 via the Message Queue 152, interprets the messages and
  • RJJ 154 may be run to accommodate various types of NP AC/SMS 18 including the ones that are W wO w 9 y 9/ / 0 ⁇ 4 «579y PCT/US98/14368 operated by Lockheed-Martin and Perot.
  • RII 154 will call stored procedures 158 to
  • the RII 154 receives messages from the RBA
  • the Database 162 is
  • the RU 154 verifies each message received from die RBA 56, to ensure that
  • the RLI 154 also has the ability to receive messages from various types of
  • Each NP AC/SMS 18 may have different information that is to be
  • the RII 154 is mapped to set structures and sent through the message queue 152.
  • DDS Data Distribution Subsystem
  • NCS 174 multiple Data Distribution application formats are supported including NCS 174,
  • ARIS 176 and MLNA 178 one for each of die downstream interfaces.
  • data is retrieved from an Oracle pipe 160 and forwarded to an interface
  • the Downstream Interface Subsystem (“DIS) 180 is configured to provide the Downstream Interface Subsystem
  • NCS 188 NCS 188. It should be understood, however, that any interface may be supported
  • die DIS 180 allows the BAR 110 to communicate with external systems using die following mechanisms:
  • the MLNA/SMS interface 182 is implemented as a stream of data sent via a TCP/IP socket interface using SMI protocol.
  • NCS interface 188 is implemented using die ported telephone
  • the communication is set up as a
  • BAR 110 sends data to the NCS, and the NCS
  • the RTE7 interface 188 is implemented as a file of ASCII based data
  • this file is created
  • three (3) real time on-line interface applications are provided.
  • SCM Application
  • SIGUSRI SIGUSRI
  • SIGUSR2 SIGUSR2
  • the Audit/Reconciliation Subsystem (“AARS") 190 provides a downstream
  • the ARS 190 will support botii
  • a system configured to regularly scheduled and on demand audit requests.
  • a system configured to regularly scheduled and on demand audit requests.
  • Audit data can be extracted from die BAR database 162 and written to a disk
  • the ARS 190 will be described in detail below.
  • FIG. 6 also shows the use of a Process Monitor Subsystem ("PMS") 200
  • the PMS 200 is started at system start-up and spawns the
  • initial BAR apphcations including DDS 170, DIS 180 and RU 154 subsystems.
  • the initial information is stored in a file and loaded by the PMS
  • die SCM 202 is a part ofthe PMS 200 and provides die means to
  • die DIS 180 found in die DIS 180 and its downstream server counterpart operated by die service provider.
  • An Emulator Subsystem (“EMU") 210 is communicably linked to the DIS 180 and in the preferred embodiment supports four different emulators: the NCS 212,
  • the utilities subsystem 220 contains a set of utility functions that are
  • Graphical User Interface may be used to provide a human-machine interface
  • OE/OP Order Entry/Order Processing
  • a mechanized interface supporting uploading of data, audits/queries of the NP AC/SMS 18 and operational messaging is supplied.
  • Request 258, Audit 260 and Service Provider Request 262 services can comprise d e
  • Each request message received from die SOA 32 receives a reply back from
  • the Upstream Message Listener (“UML) 270 is responsible for receiving
  • SOA 32 front end messages to be delivered to an NP AC/SMS 18 and to write these
  • the UML 270 is also responsible for
  • Each record retrieved is analyzed to determine the
  • the response message will be sent to the OE Front End 250
  • the Upstream Message Handler LRN (“UMHLRN”) 316 polls the SOA
  • Manager LRN queuing table to retrieve all LRN Message records.
  • retrieved is analyzed to determine the action to be performed based on the message
  • the UMHLRN 316 calls die appropriate stored
  • die record is not a new message, the date of die record is examined. If it is not a new message, the date of die record is examined. If it is not a new message, the date of die record is examined. If it is not a new message, the date of die record is examined. If it is not a new message, the date of die record is examined. If it is not a new message, the date of die record is examined. If it is not a new message, the date of die record is examined. If it
  • UMHLM 316 receives a confirmation of a successful receipt of the message
  • UMHLRN 316 deletes the record from the message queuing table. Otherwise, the
  • the Upstream Message Handler NPA-NXX (“UMH NPA-NXX") 318 is used to poll the SOA Manager NPA-NXX queuing table to retrieve all NPA-NXX
  • Each record retrieved is analyzed to determine d e action to be
  • the date of die record is examined and if
  • response message is created.
  • the response message is sent to the front end 250 via
  • the Message Handler 318 deletes me record from
  • the Audit Message Handler 320 is used to poll the SOA Manager Audit
  • die record is a new message
  • the Message Handler 320 If die record is a new message, the Message Handler 320
  • a response message is created containing the header and die message data. If the record is not a new message, the response message is created containing
  • a Provide Message Handler Application 322 is also provided for polling the
  • SOA Manager Provider queuing table to retrieve all request records. Each record
  • die Service Provider 322 calls the appropriate
  • die return code is used to update the record status in die queuing table
  • the response message is sent to the front end 250 via Registry 285.
  • the service provider waits for a confirmation from the front end of a successful receipt of the message in order to delete the record from the message queuing table.
  • the Upstream Message Handler 310 also includes a Notification Message
  • Handler 312 that polls the SOA Manager Notification table to retrieve all records.
  • the action to be performed on each retrieved record will be determined based on the
  • die record is a new request, the information needed to create the response
  • Message Handler 310 keeps running until all the records in die SOA Manager
  • the Message Handler 310 sleeps for a certain time before it wakes
  • the Emulation Subsystem 250 includes an application called EMU Server
  • the EMU Server 264, 266 which emulates die SOA Front End server.
  • the EMU Server 264, 266 receives messages from the SOA message handlers direct from die service providers messaging and communication systems and the messages, in turn, are parsed, displayed on the console and saved to a Log file.
  • the EMU server application 264, 266 emulates the SOA Front End client by
  • the EMU client waits for a reply from the listener
  • a utilities subsystem 330 is provided and
  • an access control field is included in
  • SystemLD An identifier for the system mat is using d e interface. This is a key element in the audientication process. While it is passed in each Protocol Data
  • SystemType Identifies the kind of system that is connecting: SOA, BA,
  • Userld An optional field that passes a userld used mostly for logging.
  • Listld This is an integer that identifies die list from which a key was chosen
  • Keyld This is an integer that identifies which key from the 1000 keys in a
  • 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
  • the signature field contains die MD5 hashed and encrypted
  • Recovery Mode The recovery mode flag is used to recover after downtime. Definitions: When used, the terms "interface”, “line”, “lines”, “link”,
  • “communications link”, “inbound link” and or “outbound link” can mean a channel

Abstract

A system for maintaining a customer's telephone number when a switch from one service provider to a second provider is made interfaces with a regional customer number database to keep track of local numbers and the corresponding local service provider which services each number. Service providers interface with the database and obtain information at the telephone number level that permits individual providers to determine which carrier is providing service to which telephone number. A neutral third party maintains and administers the database allowing free access by any participating provider.

Description

SYSTEM AND METHOD FOR ACHIEVING LOCAL NUMBER PORTABILITY
TECHNICAL FIELD
The present invention relates in general to the field of telecommunications
and more specifically to a system and associated methods for keeping a customer's
telephone number when a switch is made from one telecommunications service
provider to another.
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 using fiber optic cabling. 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, as examples.
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 industry 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 ("LR ") 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. W wO 99/0u4«57 /9y PCT/US98/14368
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, different "LRNs" are
used among different service providers. 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 April 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
As such, a primary object of the present invention is to provide 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 Service
Management System ("NPAC/SMjS") which receives and stores updated customer
routing information and makes it available to participating service providers. The
N AC/SMS contains a record of all ported numbers and a history file of all
transactions relating to the porting of a number.
Another object of the present invention is to provide a system for Local
Number Portability ("LNP") that submits service orders changes to a NP AC/SMS.
In this regard, a Service Order Administration ("SOA") subsystem is provided as
means of entering and submitted services order changes to the NP AC/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 may be used for this purpose.
Another object of the present invention is to provide a facility for
administering the service provider subscription information relating to a particular
customer. In this regard, the SOA is equipped with a host of functions for creating, canceling, acknowledging, modifying, retrieving, activating, disconnecting and removing subscription version information. The SOA has an audit capability that
permits audits of a customer's porting activity based on a telephone number and
receives notifications from a NP AC/SMS to ensure that it is fully informed of
relevant events relating to a service provider's subscriptions.
Still another object of the present invention is to provide the interface
structures that permit service providers to read and update their own service provider
information within a NP AC/SMS. In this regard, the interface permits service
providers to update the information in their service provider profile as well as add
and delete their own network data. The information is accessible to all service
providers via a standard interface to assure correct call routing.
Another object of the present invention is to provide a system that interfaces
directly with existing telecommunication equipment operated by all service
providers. In this regard, a new service provider can obtain authorization to port a customer using a standardized message format that notifies an old service provider
according to processes internal to the old service provider. The messaging format
includes signal protocols that can be used by both the old and new service providers to sends update notifications to the NP AC/SMS using the SOA. Upon receipt of the
notifιcation(s), the NP AC/SMS performs certain validation checks, and attempts to
match a notification received from the new service provider with a concurring
notification that may be sent from the old service provider, permitting the two service providers to complete the port. Yet another object of the present invention is to provide a means of
downloading subscription and network data from a NP AC/SMS to the local service
provider's applications for correct call routing and network provisioning. In this
regard, an Interface Broadcast Agent ("IBA") subsystem is provided as a means of
interfacing a service provider's downstream systems with the NP AC/SMS. In one
embodiment, the LBA subsystem is configured to automatically receive new network
or subscription data or modifications to existing data. The L A may also request data
using a download request. The request can be based on time range, telephone
number, telephone number range or other indicator. A service provider can also
directly read the data from the NP AC/SMS .
The invention provides the software and hardware platforms for achieving
Local Number Portability. A central or regionalized database is used to keep track
of local numbers and the corresponding local service provider that services each
number. Service providers interface with the database and obtain information at the
telephone number level that permits individual providers to determine which carrier
is providing service to which telephone number. A neutral third party maintains and
administers the database allowing free access by any participating provider. Methods for transferring a customer's port data from an old service provider to a new service provider are also disclosed.
Disclosed, in one embodiment, is a system for maintaining a customer's local
telephone number when a switch is made from a first service provider to a second service provider. The system uses a regional number portability subsystem
containing a plurality of telephone number porting data defining how to route a call
from one service provider to another. A service order application is communicably linked to the regional number portability subsystem and configured to send a porting
request for a specific customer to the portability subsystem and service providers
interfaced to the subsystem. A local service management application is
communicably linked to the regional number portability subsystem via a second data
pathway and configured to receive the porting request. The local service
management application supports the interface to the second service provider and
delivers the porting request containing the new routing data for the customer
allowing the customer to maintain their existing telephone number once the switch
is made.
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.
W wOv 9y9y//0iw45a79y PCT US98/14368
BRIEF DESCRIPTION OF THE DRAWINGS
In the drawings:
Figure 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;
Figure 2 is a high level block diagram for the interface between a Service
Order Adrninistration ("SOA"), an Interface Broadcast Agent ("L A") and a regional
number portability administration center according to one embodiment of the
invention; Figure 3 is a block diagram of the SOA and LBA subsystems and their
interface to various business applications;
Figure 4 is a block diagram of an SOA broken down into its component
subsystems according to one embodiment;
Figure 5 is a block diagram of the LBA broken down into its component
subsystems according to one embodiment;
Figure 6 is a detailed block diagram of the Interface Broadcast Agent
Repository subsystem broken down into its component subsystems; and
Figure 7 is a block diagram illustrating the Order Entry/ Order Processing interface subsystem according to one embodiment of the invention. Corresponding numerals in the drawings refer to corresponding parts unless
otherwise indicated. DETAILED DESCRIPTION OF THE INVENTION
Turning now to Figure I, a flow diagram of a telephone number porting
process, denoted generally as 10, is shown. In general, process 10 is used by a
customer 12 to achieve Local Number Portability ("LNP") when switching from one
service provider 14 to another 16. As shown, a customer 12 initiates the process 10
by contacting either an old service provider 14 or a new service provider 16 to
arrange a transfer of the customer's porting data from the old service 14 to the new
service 16. The communications between the customer 12 and the old service
provider is indicated by link 13 while link 15 represents the communications link
with the new service provider 16. Thereafter, the old service provider 14 and new
service provider 16 communicate via link 17 with each other in order to arrange a
data port for the customer 12.
Once the new service provider 16 has obtained the customer's port data, the
provider 16 notifies the Number Portability Administration Center Service
Management System ("NP AC/SMS") 18 ofthe pending port prior to activation. The
interface between the new service provider 16 and the NP AC/SMS 18 is supported
by link 19. and conforms to recognized industry standards such as the "NP AC/SMS
Interoperable Interface Specification", version 1.0, by Lockheed Martin LMS Corporation, October, 1996. In general, the NP AC/SMS 18 maintains a centralized
regional number database for all customers in a given region and receives the port request from a new service provider 16.
According to the invention (see Figures 4 through 7), an interface is W wO 9 v9y//0υ4«57 /9 PCT/US98/14368
established between the NP AC/SMS 18 and the participating service providers permitting the transfer of the customer's port data.
A customer's port request is communicated to either the customer's old
service provider 14 or a new service provider 16 to the NP AC/SMS 18. After the
port request 19 has been received by the NP AC/SMS 18, the NP AC/SMS 18
communicates with the old service provider 14, the new service provider 16 and all
other service providers 20, via links 25, 23 and 21, respectively, to activate the port.
This permits a customer 12 to port his existing number from an old service provider
14 to a new service provider 16 while at the same time notifying all other service
providers 20 within that region that the port has been completed allowing proper call
routing.
With the knowledge that the customer's number has been ported from one
provider to another, all service providers 14, 16, and 20 can configure their
networking equipment for correct call routing within that region. The particular embodiment ofthe present invention incorporates significant advantages in that it
allows for the sending and receiving of porting data from regional databases (i.e.
maintained at the NP AC/SMS 18) providing for a smooth transition from an old
service provider 14 to a new service provider 16.
Turning now to figure 2, a block diagram of a system for achieving local
number portability is shown and denoted generally as 30. Specifically, figure 2
shows that the regional NP AC/SMS 18 is communicably linked to two functional sub-systems, a Service Order Administration ("SOA") sub-system 32 and an Interface Broadcast Agent ("LBA") sub-system 34 via communications links 33 and 35, respectively.
The SOA 32 is the responsible application that sends the customers port data
from one service provider to another service provider. Likewise, the LB 34 is the
responsible application for service management processes at the local network level.
The SOA 32 and LBA 34 work together with the NP AC/SMS 18 to send and receive
customer porting data from regional call routing centers and data sources to more
centralized information sources and applications. This configuration 30 provides a
distributed architecture which allows the porting of data to the local applications and
networking equipment maintained by service providers for appropriate call routing
and processing.
In one embodiment, the SOA 32 is communicably linked to one or more local
applications 36, which are maintained by the regional service provider. Examples
of the local apphcations 36 include, but are not limited, to local residential and
business lines for voice, data and fax communications as provided by the local service provider. The local applications 36, in turn, are communicably linked and
used by other service providers 38, other Complex Local Exchange Carriers
("CLEC") 40 and yet other Local Exchange Carriers ("LEC") 42 depending on the
existing network of service providers. It is the SOA 32 that acts as an intermediary between the local applications 36 and the regional NP AC/SMS 18 thus providing a smooth non-intrusive solution for local number portability.
Likewise, the LBA 34 provides the interface between die regional NP AC/SMS 18 and a plurality of other network entry systems such as those shown in boxes 44,
46 and 48. The specific functionality of the network entry systems 44, 46 and 48
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 48 can comprise a database of records for
all provider systems needing access to the customer porting data. An example well
known to those skilled in the art is the ANI reference information system. The local
network interfaces 46 can be an intelligent network architecture that supports routing
queries during call processing. An example of a network interface 44 would include
the Metro Intelligent Network Architecture tiαat 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 NP AC/SMS 18 for correct call servicing and routing. While figure 2 illustrates a single embodiment 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. Specifically figures 4 through 7 disclose detailed architectural designs, in the form of block diagrams, for various subsystems, including an SOA 32 and IBA 34, which may be used in a specific and preferred embodiment for achieving local number portability. Turning now to Figure 3, a diagram illustrating the interaction between the
NP AC/SMS 18, the SOA 32 and the IBA 34 sub-systems is shown and denoted
generally as 50. Customer Order Entries and Order Processing ("OE/OP") at the
local level are represented at 62, which as shown is coupled to local SOA engine 58.
The SOA engine 58 feeds customer telephone information into the regional SO As
54 located in various regions. The SOA sub-system 32 comprises the regional SOAs
54 and SOA engine 58. While the use of three (3) regional SOAs 54 in figure 3, it
is envisioned that each region providing local number portability will have a
corresponding SOA 54.
An interface between the SOA sub-system 32 and the NP AC/SMS 18
computer processing systems 52 is shown by lines 51. The SOA sub-system 32
sends the port data to systems 52 which, in turn, relay the port request in a predefined
message format to the LBA sub-system 34.
Likewise, the LBA sub-system 34 comprises a plurality of regional LB As 56
that update the LBA repository 60. The LBA repository 60 is accessible by a plurality
of downstream applications such as business applications 64 and network
provisioning and configuration systems 66. It should be understood, however, that
any type of downstream system can be connected to the LBA repository 60 at the
option ofthe 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.
The SOA subsystem 32 provides the means for submitting customer service order changes to the NP AC/SMS 18. Turning now to figure 4, the SOA 32 is shown
broken down into its functional components. LNP transactions originating either
from a GUT interface or the SOA Engine 80 are received through stored procedures
82. The stored procedures 82 place the transaction information into the outbound
link 84 and received by the SOA Message Handler ("SMH") 86 that reads and
processes the information. The SMH 86 queries the SOA Database 81 for any
required extra information and passes the transaction onto the SOA Manager
("SMG") 98, which sends the transaction to the NP AC/SMS 18 and waits for a
response. When the response is received from the NP AC/SMS 18, it is routed back
to the SMH 86, which then loads it into an inbound link 84 for the stored procedure
82.
The SMG 98 also receives notifications from the NP AC/SMS 18.
Notification transactions are passed onto the Unsolicited Event Handler ("UEH") 90
which, in rum, processes the transactions and updates die SOA database 81 when
necessary.
Also shown is a Resynch Subscription Version Process ("RSP") 88 coupled
to the SOA database 81 where it is used to synchronize die SOA subsystem 32 after
a period of downtime. After the SMG 98 binds to the NP AC/SMS 18, the RSP 88
is started. In operation, the RSP 18 requests from the NP AC/SMS 18 all subscription
versions that have a modification time-stamp more recent than the last time the SMG
98 had an association with the NP AC/SMS 18. The RSP 88 also sets a downtime
flag in an audit database tables to indicate that an audit was ongoing during a period of downtime.
The IBA Subscription Version Report ("ISVR") 92 is used to report
discrepancies between the SOA Database 81 and IBA Database 102. The Check
Link 96 monitors the physical connection between the SOA 32 and NP AC/SMS 18.
If the physical connection is broken, the Check Link 96 will reset the SOA subsystem
32.
All the processes within me SOA subsystem 32 (with the exception of die
ISVreport 92) are monitored by the Process Monitor 94. The Process Monitor 94
starts applications when they are required and if an application teπ inates, the
Process Monitor 94 is notified. The Process Monitor 94 automatically restarts
applications that are intended to always be running, like the SMG 98 and Check Link
96, if they terminate. The one exception is the ISVreport 92 which is operator
controlled and is not monitored by the Process Monitor 94.
In the preferred embodiment, the Process Monitor 94 is the parent process for
the SOA 32 and LBA 34 subsystems. The Process Monitor 94 will watch over ail of
the standard processes required to run me subsystems 32, 34 and keeps a table of all
applications spawned and operational information about each such application.
The SOA Message Handler 86 allows the GUI component ofthe SOA 32 to
communicate with the NP AC/SMS 18. In one embodiment, multiple instances of me
SOA Message Handler 86 are run to allow for greater diroughput wherein each such
instance ofthe SOA Message Handler 86 receives requests from a single outbound
link 84. Thus, all output to the stored procedures 82 is done through separate links, one for each GUI workstation.
The SOA Message Handler 86 receives messages from the GUI via the
outbound link 84. Messages are processed, data acquired and organized by tasks
which preferably are broken down at an object level (i.e. Subscription Version,
Audit, Service Provider, and Network). Based on a message identifier, the SOA
Message Handler 84 is configured to collect and assemble the information required
by the NPAC/ SMS 18.
In one embodiment, messages are relaved to a DSET Distributed Systems
Generator ("DSG") Manager through a UNIX sockets interface. The DSET DSG
Manager is used to implement the interface between die SOA 32 and the NP AC/SMS
18. The UNIX sockets are used for the interface between d e LBA Agent 112 (See
figure 5) and other LBA apphcations as well as the SOA Manager 98 and other SOA
applications.
All outgoing messages that go to the NP AC/SMS 18 are logged. The SOA
subsystem 32 then waits for a response (successful, failure or timeout) from the
DSET DSG Manager. The SOA subsystem 32 processes any data received with the
reply, updating the SOA database 81 where required, and relays die request result
back to the GUI application through one or inbound link(s) 83.
The Unsolicited Events Message Handler 90 is used by die SOA subsystem
32 to handle notification data received from NP AC/SMS 18. The Unsolicited Events
Message Handler 90 starts up by making a connection to the UNIX sockets and then
waiting for a message to be sent from the DSET DSG Manager. When a message is received by the Unsolicited Events Message Handler 90
from the DSET interface agent, the Unsolicited Events Message Handler 90
determines the type of message and performs the required actions for that message
type. When the action is complete the Unsolicited Events Message Handler 90
formats and sends a reply to the DSET DSG Manager which translates the message
info a CMLP event and sends the event to NP AC/SMS 18. The Unsolicited Events
Message Handler 90 resumes waiting for the next message to appear in the UNLX
socket.
As stated the SOA Database 81 is used to store and maintain the current
number information for a customer. Table 1 below is domain field listing for an
SOA Database 81 according to one embodiment:
Figure imgf000021_0001
Figure imgf000022_0001
Table 1: Domain List for one Embodiment of the SOA Database 81.
Turning to figure 5, the Regional Interface Broadcast Agent ("RLBA") 56 is
broken down into its component subsystems. In general, RLBA 56 provides the
interface between d e NP AC/SMS IS and the Interface Broadcast Agent Repository
("LBAR") 110. In the preferred embodiment, requests are formatted using a
Common Message Management Information Protocol ("CMLP") and once received
by the LBA Agent 112 and are then forwarded to any one of the LBA Message
Handlers ("LMH") 114, 122, 124, 126 or 128. Preferably, four (4) LMHs are used,
each handling CMLP requests for a specific object type: one for subscription versions
122, one for service provider networks 124, one for LRNs 126 and one for NPA-
NXXs 128. Each LMH 122, 124, 126 and 128 handles the CMLP requests which are
received and updates die LBA Database 102. The LBA Agent 112 also receives
notification, recovery complete and action transactions. These transactions are
forwarded to appropriate logging functions, which, in turn, process and handle the
transactions and update the LBA database 102.
Upon startup, die LBA Agent 112 reads each data item (subscription version,
LRN, NPA/NXX, etc.) from the RLBA database 102 and load them into memory .
These data items form the Managed Instance Tree ("MIT") used by me RLBA 56 as
reference points to the stored data during its operation. Once the reload has completed, the LB Agent 112 binds to the NP AC/SMS 18. When the bind has been
successfully established, the IBA Agent 112 requests that the NP AC/SMS 18
download all ofthe subscription, NPA-NXX and LRN data which was accumulated
during the time that die LBA Agent 112 was not bound to the NP AC/SMS 18. Upon
successful completion ofthe download, the LBA Agent 112 informs the NP AC/SMS
18 that the download has been completed and normal processing resumes.
In one embodiment, d e LBA Database 102 is updated from files using the
File Transfer Protocol ("FTP") as illustrated by blocks 130 and 132. The FTP
applications 130 and 132 are controlled by an operator which involves the steps of
reading the subscription version 130 and service provider network information 132
to form a file and update d e appropriate database tables with the new information.
Table 2 is a domain field listing for an die LBA Database 102 according to
one embodiment:
Figure imgf000023_0001
Figure imgf000024_0001
All of die applications wiϊhin the RLBA subsystem 56 (except die FTP
processes 130 and 132) are monitored by the Process Monitor 134. The Process
Monitor 134 is responsible for invoking applications when they are required and if
a process terminates the Process Monitor 134 is notified. Applications tiiat are
intended to always be running are automatically restarted by the Process Monitor 134
if they terminate.
Any transactions received by d e LBA Agent 112 are forwarded to the
appropriate logging applications such as he LBA Notification Logger 116, the LBA
Recovery Complete Logger 118 or LBA Action Logger 120. Each of the logging applications 116, 118, 120 handle the transactions and update the LBA Database 102.
The IBA Database 102 can also be updated from flat files by the FTP
Network Download 132 and FTP Subscription Version Download 130 applications.
The Check Link application 136 monitors the physical connection between the
RLBA 56 and NP AC/SMS 18. If the physical connection is broken, Check Link 136 will reset the RLBA subsystem 56.
All the processes within the RLBA subsystem 56 (with the exception ofthe FTP processes 130 and 132) are monitored by the Process Monitor 134. Thus, the
Process Monitor 134 is the parent process for both the SOA 32 and RLBA 56
subsystems and watches over all of the standard processes required to run each
system. The LBA Message Handlers ("LMH") 122, 124, 126 and 128 are used to
accept messages from NP AC/SMS 18 and to perform the required actions on these
messages.
The LMHs 122, 124, 126 and 128 also receive messages from the NP AC/SMS
18 requesting operations to be performed on the database tables ofthe LBA Database
102. Examples of these operations include SET, CREATE and DELETE. When e
NP AC/SMS 18 sends a message to the RLBA 56, it is received by die DSET DSG
Agent, validated and stripped of protocol related information. The DSET DSG
Agent determines which ofthe four LMH applications (Service Provider 124, NAP-
NXX 128, LRN 126 and Subscription Version 122) the message is addressed to and
sends the data to d e corresponding application process via a UNIX socket interface.
When the appropriate LMH (either 122, 124, 126 or 128) accepts the message, the
data is then extracted from the message and the operation is determined. An SQL
statement is built for the action with the data values extracted from die message and
the SQL statement is performed, updating the LBA Database 102.
The Network Download File Transfer Protocol 132 is used to restore the LBA Database 102 and LBAR 110 from the NP AC/SMS 18 via FTP/TCPLP. The LBAR
110 provides a means for holding and distributing the data received from die NP AC/SMS 18 to all the various downstream systems maintained by die service W wOu 9y9y/0iro4579y PCT/US98/14368
provider. In the preferred embodiment, all activities from the download file transfer
are logged. The Subscription Version Download File Transfer Protocol 130 may also
be used to restore the LBAR 110 and RLBA database 102 from the NP AC/SMS 18
using FTP/TCPIP. Preferably, the activities from the download file transfer are
logged.
In use, the NP AC/SMS 18 sends variable length create requests to the CMLP
Agent 112 consisting of subscription data and a list of one or more telephone
numbers for each subscription data element. The CMLP Agent 112 extracts die create
request from the CMLP message and formats it into a structure suitable for use by the
LBA Action Logger 112 which, in turn, extracts the subscription version data from
the structure.
The LBA Notification Logger 116 is used to log notifications received by the
CMLP Agent 112. In this way, the NPAC-SMS Operational Information and
VersionNew NPA-NXX notifications are logged. The CMLP Agent 112 receives
these notifications from the NP AC/SMS 18, formats the information into a usable
structure and forwards the structure to die LBA Notification Logger 116 over a UNTX
socket. The LBA Notification Logger 116 is started by the Process Monitor 134 at
the request ofthe CMIP Agent 112.
The LBA Recovery Complete Logger 118 is used to log Recovery Complete
Replies and Download Replies sent by the NP AC/SMS 18 to the LBA Agent 112.
The IBA Agent 112 receives these actions from die NP AC/SMS 18, formats the
information into a usable structure and forwards the structure to the IRA Recovery WOj 99/0u4«57 /9» PCT/US98/14368
Complete Logger 118 over a UNIX socket. The LBA Recovery Complete Logger
118 is started by the Process Monitor 134 at the request ofthe IBA Agent 112.
A particularly advantageous aspect ofthe present invention is mat it provides
interfaces from the Interface Broadcast Agent Repository 110 to internal systems
operated by the individual service provider. In one embodiment, four proprietary
downstream systems have been coupled to die LBAR 110 for receiving data. The
Network Control System ("NCSϊT) and RTE7 systems manage local number
portability information in the long distance environment while die Metro Intelligent
Network Adrmnistration Service Management System ("MLNA/SMS") is configured
to manage local number portability information on the local service network level.
Also, the ANT Reference Information System ("ARIS") collects local number
portability ("LNP") information for distribution to service provider business systems
44, 46 and 48.
As such, and according to one embodiment ofthe invention, d e LBAR 110
supports the following features:
A facility to consolidate LNP data from the RLBA Database 102 into
the BAR 110.
A data distribution application that manages distribution of data to die
ARIS, MTNA/SMS, and NCS 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
preferably using the DECmessageQ product from Digital Equipment W wO w 9 *9y//0u4«57 /9y PCT/US98/14368
Corp.
An on-line interface to the MLNA/SMS system preferably using
Service Builder System Management Interface product from Northern
Telecom.
- An on-line interface to the ARIS system preferably using die Registry
Messaging product from MCI.
A batch interface tcTthe RTE7 long distance support system using
FTP. A database update application (the RII subsystem) reads the
data from the message queue and performs the necessary database
updates in the LBAR 110.
In one embodiment, a stored procedure extracts data from me LBAR 110 and
writes e data to one of three links, each dedicated to one of die downstream on-line
interface applications. Data from each link is read by a dedicated data distribution
application (part ofthe DDS subsystem 170 shown in figure 6) which will in turn
broadcast it to dedicated message queues for die ARIS, MLNA/SMS and NCS request
processing applications.
The Process Monitor 134 provides the means to start and stop the
LBAR 110 and monitors each application or restarts any application which terminate
abnormally.
Turning to Figure 6, die subsystem for the Interface Broadcast Agent
Repository ("LBAR") is shown and denoted generally as 110. An LBA Queue Processor ("IQP") 150 is responsible for sending all the changes that die RLBA
subsystem 56 receives from the NP AC/SMS 18 to the LBAR 110. The IQP
subsystem 150 is also responsible for ensuring all records of transactions on the
RIB A 56 are delivered to the BAR 110.
In operation, the IQP subsystem 150 processes records from a specific
database table and puts die information into a message queue 152. The IQP
subsystem 150 will process all responses from the BAR system 110 and make the
appropriate updates to the table. The IQP subsystem 150 numbers each message
before it is put into the message queue 152 to ensure the messages are delivered in
sequential order. The BAR 110, in turn, verifies that the message read is d e next
consecutively numbered message from die RBA 56.
In one embodiment, die BAR 110 responds to each message sent as to
whedier it was successfully applied, rejected due to validation errors, or needs to be
resent. If the number is out of sequence then the BAR 110 issues a "resend" of die
specific message and any messages at have been put into the Message Queue 152 after that specific message. If die specific message requested for resend cannot be
found, a "lost" message notification is sent and the resend continues.
The R A to AR Interface ("RU") 154 is responsible for keeping the BAR 110 up to date with the changes that occur on the RBA 56. The RE 154 receives messages from a RBA 56 via the Message Queue 152, interprets the messages and
performs the appropriate database functions. Multiple instances of die RJJ 154 may be run to accommodate various types of NP AC/SMS 18 including the ones that are W wO w 9 y9//0υ4«579y PCT/US98/14368 operated by Lockheed-Martin and Perot. RII 154 will call stored procedures 158 to
perform the database transactions and to populate links 160 with the information
stored in the BAR Database 162.
In the preferred embodiment, the RII 154 receives messages from the RBA
56 via a specific message queue 152. Messages are processed, and die underlying
message data acquired and organized by tasks broken down at d e 'object' level (i.e.
Telephone Number, Audit, Service Provider, and Network). The Database 162 is
updated witii die 'object' data and at the end of a successful transaction, the RLI 154
will issue a confirmation message to the message queue 152.
The RU 154 verifies each message received from die RBA 56, to ensure that
no duplicate messages from die RBA 56 are processed. This is accomplished by
each RBA 56 tagging all messages with tracking numbers. The RLI 154 subsystem
records all tracking numbers associated witii a R A 56 and matches die record with
the tracking number in the BAR database 162. This provides die ability to track
messages from any RBA 56.
The RLI 154 also has the ability to receive messages from various types of
NP AC/SMS 18. Each NP AC/SMS 18 may have different information that is to be
sent to the RBA 56 and then the BAR 110. Since each NP AC/SMS 18 could have
different information to send and thus a version LD is used to identify the type of
NP AC/SMS 18 reviewing a given region. In the RBA 56, the information is
mapped to set structures and sent through the message queue 152. The RII 154
subsystem is able to recognize the type of structure that was populated by the RBA W vγOv, 9?9/04«57/9y PCT/US98/14368
56 and map the information to the appropriate database fields. The use ofthe version
ID allows for multiple NP AC/SMS 18, via the RIB A 56, to send all information to
one message queue 152.
Also shown is a Data Distribution Subsystem ("DDS") 170 which sends
transactions to a second message queue 172 for a downstream interface. Preferably,
multiple Data Distribution application formats are supported including NCS 174,
ARIS 176 and MLNA 178, one for each of die downstream interfaces. In one
embodiment, data is retrieved from an Oracle pipe 160 and forwarded to an interface
subsystem on the message queue 172. Once the message has been sent to the
downstream interface, the record in the BAR Database 162 will have its status
changed to "Sending" indicating tiiat the message has been sent to keep track ofthe
state ofthe transaction.
In one implementation, the Downstream Interface Subsystem ("DIS") 180
supports four proprietary interfaces: the MLNA SMS 182, ARIS 184, RTE7 186 and
NCS 188. It should be understood, however, that any interface may be supported
depending on the subsystem supported by die service provider. With me proprietary
interfaces, die DIS 180 allows the BAR 110 to communicate with external systems using die following mechanisms:
The MLNA/SMS interface 182 is implemented as a stream of data sent via a TCP/IP socket interface using SMI protocol.
The NCS interface 188 is implemented using die ported telephone
number and request Service Provider NPA-NXX data received from the Data Distribution Subsystem 170 from the message queue 172
and sent to the NCS. Preferably, the communication is set up as a
two-way dialog, i.e. BAR 110 sends data to the NCS, and the NCS
replies after processing the data.
- Ported telephone number data received from the Data Distribution
Subsystem 170 on message queue 172 and sent to ARIS 186 using
MCI Registry or a similar communications protocol.
The RTE7 interface 188 is implemented as a file of ASCII based data
sent via TCP/LP using FTP software Preferably, this file is created
on a regularly scheduled basis in batch mode.
In one embodiment, three (3) real time on-line interface applications are
found in e DIS 180 that support NCS 182, MTNA/SMS 184, and ARIS 188. A user
is able to access a menu from which he/she can select one ofthe following options:
1. - disconnect from NCS msgQ
2. - connect to NCS msgQ
3. - logoff MLNA/SMS session
4. - logon to MLNA/SMS session
5. - deregister from ARIS registry
6. - register with ARIS Registry
In response to a selection, the Service Configuration and Management
Application ("SCM") 202 will send a signal to one of tiiree DIS applications 182,
184 or 186. In die UNIX operating environment, two signals are used: SIGUSRI and SIGUSR2. The SIGUSRI signal is used for "connect" and "logon" commands with
the SIGUSR2 signal reserved for "disconnect" and "log off commands.
The Audit/Reconciliation Subsystem ("AARS") 190 provides a downstream
system for interfacing with the BAR 110 and provides the ability to compare service
provider databases against die BAR Database 162. The ARS 190 will support botii
regularly scheduled and on demand audit requests. In one embodiment, a system
administrator is given die ability tcfschedule regular audits and request on-demand
audits. Audit data can be extracted from die BAR database 162 and written to a disk
file 192 for transmission to a downstream system using FTP. The ARS 190 will
support requests for subsets ofthe data in die BAR database 162 as well as complete
database dumps.
Figure 6 also shows the use of a Process Monitor Subsystem ("PMS") 200
within the BAR 110. The PMS 200 is started at system start-up and spawns the
initial BAR apphcations including DDS 170, DIS 180 and RU 154 subsystems. In
other embodiments, more copies of the same systems can be spawned by die PMS
200 upon request. The initial information is stored in a file and loaded by the PMS
200 when it is started.
As shown, die SCM 202 is a part ofthe PMS 200 and provides die means to
stop and restart communications between each of the real time on-line interfaces
found in die DIS 180 and its downstream server counterpart operated by die service provider.
An Emulator Subsystem ("EMU") 210 is communicably linked to the DIS 180 and in the preferred embodiment supports four different emulators: the NCS 212,
MINA/SMS 214, ARIS 216 and DDS 218 emulators. The EMU 210 programs are
used for testing and validation of the DIS 180. In one embodiment, communication
between the DIS 180 and EMU 210 subsystem programs is accomplished using
different protocols for each individual program, as follows:
DDS Emulator DECmessageQ
NCS Emulator DECmessageQ
MTNA SMS Emulator UNLX TCP/IP socket library
ARIS Emulator Registry
The utilities subsystem 220 contains a set of utility functions that are
available to speed development of UNLX and SQL programs. These functions have
been developed specifically for use in the BAR 110 application environment and
provide solutions to common problem requirements such as Oracle stored procedures
158, message queue access, FTP access, error handling, process signal control and
any other software functions that may be best implemented as a utility.
As stated, the SOA 32 and B A 34 subsystems interface with the NP AC/SMS
18, such as ti at maintained by Lockheed Martin in Illinois. In this sequel, a
Graphical User Interface may be used to provide a human-machine interface
between e service provider Order Entry/Order Processing ("OE/OP") systems, such
as the one illustrated in figure 7, and the SOA 32 and EBA 34 subsystems.
In one embodiment, a mechanized interface supporting uploading of data, audits/queries of the NP AC/SMS 18 and operational messaging is supplied. Thus,
the Subscription Version 252, Notification 254, LRN Request 256, NPA-NXX
Request 258, Audit 260 and Service Provider Request 262 services can comprise d e
base set of messages for communications between OE/OP 250 and the SOA 32.
Each request message received from die SOA 32 receives a reply back from
the a Listener Application 270 indicating that die message has been received and
queued for transmission to the appropriate NP AC/SMS 18. This reply does not,
however, indicate tiiat the message has been sent to or processed by the NP AC/SMS
18. When the message has been sent to and processed by die NP AC/SMS 18, a
response message from die SOA 32 will be sent to OE/OP 62 containing die result
ofthe original request message returned by die NP AC/SMS 18.
The Upstream Message Listener ("UML") 270 is responsible for receiving
SOA 32 front end messages to be delivered to an NP AC/SMS 18 and to write these
requests to the SOA Manager Database 300. The UML 270 is also responsible for
determining the particular NP AC/SMS 18 to which each message is to be delivered.
The Upstream Message Handler Subscription Version ("UMHSVr) 314 will
poll the SOA Manager Subscription version queuing table to retrieve all records
based on telephone number range. Each record retrieved is analyzed to determine the
action to be performed based on the message type of the record and record status.
If the record is a new message the UMHSV 314 will call the appropriate
stored procedure. Once a response is received from the stored procedure, it is W wOυ 9 y9y/0υ44557 /9y PCT/US98/14368 evaluated and the return code is used to update the record status in the 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. The response message will be sent to the OE Front End 250
on Registry 288. The UMHSV 314, in turn, will wait for a confirmation from the
front end 250 of a successful receipt of he message in order to delete die record from
the message queuing table.
The Upstream Message Handler LRN ("UMHLRN") 316 polls the SOA
Manager LRN queuing table to retrieve all LRN Message records. Each record
retrieved is analyzed to determine the action to be performed based on the message
type, record status, and received date of d e record.
If the record is a new message, the UMHLRN 316 calls die appropriate stored
procedure. The returned value of die stored procedure will be evaluated and a
response message will be created.
If die record is not a new message, the date of die record is examined. If it
is expired, it will be deleted from LRN queuing table. Otherwise, a response
message will be created and sent to the SOA front end 250 via Registry 285. If the
UMHLM 316 receives a confirmation of a successful receipt of the message, the
UMHLRN 316 deletes the record from the message queuing table. Otherwise, the
result status of die queuing table will be updated for die request.
The Upstream Message Handler NPA-NXX ("UMH NPA-NXX") 318 is used to poll the SOA Manager NPA-NXX queuing table to retrieve all NPA-NXX
Message records. Each record retrieved is analyzed to determine d e action to be
performed based on the message type, record status, and received date ofthe record.
If die record is a new message, the UMH NPA-NXX 318 calls the appropriate stored
procedure. The returned value of the stored procedure will be evaluated and a
response message created.
If the record is not a new message, the date of die record is examined and if
it is expired, it will be deleted from NPA-NXX queuing table. Odierwise, an error
response message is created. The response message is sent to the front end 250 via
Registry 285. If he application received a confirmation of a successful receipt ofthe
message from the front end 250, the Message Handler 318 deletes me record from
the message queuing table. Odierwise, the result status ofthe queuing table will be
updated for the request.
The Audit Message Handler 320 is used to poll the SOA Manager Audit
queuing table to retrieve all request records for processing. Each record retrieved is
analyzed to determine the action to be performed based on the message type ofthe
record and record status. If die record is a new message, the Message Handler 320
calls d e appropriate stored procedure. Once a response is received from the stored
procedure, it is evaluated and the return code is used to update die record status in die
queuing table and a response message is created containing the header and die 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 is considered to be expired. The response
message is created containing an error message header. The response message will
be sent to the front end 250 via Registry 285. The process will wait for a
confirmation from die front end 250 of a successful receipt ofthe message in order
to delete die record from the message queuing table.
A Provide Message Handler Application 322 is also provided for polling the
SOA Manager Provider queuing table to retrieve all request records. Each record
retrieved is analyzed to determine the action to be performed based on die message
type of die record and record status.
If the record is a new message, die Service Provider 322 calls the appropriate
stored procedure. Once a response is received from die stored procedure, it is
evaluated and die return code is used to update the record status in die queuing table
and a response message is created cont-aining the header and d e 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 is considered to be expired. The response message
is created containing an error message header.
The response message is sent to the front end 250 via Registry 285. The service provider waits for a confirmation from the front end of a successful receipt of the message in order to delete the record from the message queuing table.
The Upstream Message Handler 310 also includes a Notification Message
Handler 312 that polls the SOA Manager Notification table to retrieve all records.
The action to be performed on each retrieved record will be determined based on the
message type and the status of the record.
If die record is a new request, the information needed to create the response
message will be fetched from the "SOA MGR Database 300 or the corresponding
database table will be updated.
If die record is not a new request, an error response message will be created
and sent to die front end 250 via Registry 285. If die process received a confirmation
of a successful receipt ofthe message from the front end 250, die Message Handler
310 deletes die record from die SOA Manager Notification table. Otherwise, the
result status of SOA Manager Notification table will be updated for die request. The
Message Handler 310 keeps running until all the records in die SOA Manager
Notification table are processed. If there is no more record in the SOA Manager
Notification table, the Message Handler 310 sleeps for a certain time before it wakes
up and begins to poll the SOA Manager Notification table again.
The Emulation Subsystem 250 includes an application called EMU Server
264 and 266 which emulates die SOA Front End server. The EMU Server 264, 266 receives messages from the SOA message handlers direct from die service providers messaging and communication systems and the messages, in turn, are parsed, displayed on the console and saved to a Log file.
The EMU server application 264, 266 emulates the SOA Front End client by
reading sample messages from a file and passing them onto the corresponding
listener using die Registry 285. The EMU client waits for a reply from the listener
before sending another message.
In the preferred embodiment, a utilities subsystem 330 is provided and
comprises a set of utility functions mat are available to speed development of UNLX
and SQL programs. These functions have been developed specifically for use in the
OE Interface application environment to provide solutions to common programming
requirements, such as Oracle stored procedures.
Preferably some method of access control is provided to manage security
issues that arise from communications between the BA 34/SOA 32 subsystems and
the NP AC/SMS 18. In one embodiment, an access control field is included in
messages flowing between the BA 34/SOA 32 subsystems and d e NP AC/SMS 18
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 die message
sender.
In one embodiment, messages flowing between the BA 34/SOA 32
subsystems and the NP AC/SMS 18 incorporate a variable called
"LnpAccessControl" for the access control field with the following information:
SystemLD: An identifier for the system mat is using d e interface. This is a key element in the audientication process. While it is passed in each Protocol Data
Unit, it is only really important in the association establishment.
SystemType: Identifies the kind of system that is connecting: SOA, BA,
SOA and A or NPAC. Userld: An optional field that passes a userld used mostly for logging.
Listld: This is an integer that identifies die list from which a key was chosen
to create the signature.
Keyld: 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 die MD5 hashed and encrypted
systemld, die system type, the userld, the cmipDepartureTime, and sequenceNumber
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. Definitions: When used, 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. The terms "outbound link" and "inbound link" have meaning in
the context of the Oracle database structure and associated protocols as "pipes"
which can be used for the transfer and communication of data from system
applications and programs, whether-extemal or internal. The terms "outbound link"
and "inbound link" also have meaning in the context of die Unix operating system
structure and associated protocols as "sockets" which can be used for the transfer and
communication of data from system apphcations and programs. Such conventions
are well known to those skilled in die art.
While tiiis 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 die illustrative embodiments as well as other embodiments of die invention will become apparent to persons skilled in d e
art upon reference or description. It is, tiierefore, intended mat the appended claims
encompass any such modifications or embodiments.

Claims

What is claimed is:
1. A system for maintaining a customer's local telephone number when a switch
is made from a first service provider to a second service provider, said system
comprising:
a regional number portability subsystem containing a plurality of telephone
number porting data defining how to route a call from said first service provider to
said second service provider;
a service order application communicably linked to said regional number
portability subsystem via a first data pathway and configured to send a porting
request for a specific customer; and
a local service management application communicably linked to said regional
number portability subsystem via a second data patiiway, said local service
management application configured to receive said porting request, said local service
management application supporting an interface to said second service provider for
delivering said porting request and providing new routing data about said specific
customer using the customer's existing telephone number.
2. The system for porting a customer's local telephone number according to
claim 1 wherein said service order application comprises:
means for receiving and processing customer orders for local telephone
service; a local service order database containing a plurality of current telephone
number and customer transaction information; and
a service order application engine forming a bridge between said means for
receiving and processing customer orders and said service order database, said
service order application engine configured to update said service order database witii
customer specific telephone number data.
3. The system for porting a customer's local telephone number according to
claim 2 further comprising a check link application which monitors the interface
between said service order application and said regional number portabihty
subsystem.
4. The system for porting a customer's local telephone number according to
claim 1 wherein said local service management application comprises:
a regional service database containing a plurality of current telephone number
and customer transaction information;
an interface agent application to said regional number portabihty subsystem,
said interface agent application configured to receive customer routing messages from said service order application;
means for handling said customer routing messages depending on die object type; and means for updating said regional service database.
5. The system for porting a customer's local telephone number according to
claim 4 further comprising a check link application which monitors d e interface
between said local service management application and said regional number
portability subsystem.
6. The system for porting a customer's local telephone number according to
claim 5 wherein said check link application is configured to reset said local service
management apphcation when said interface between said local service management
apphcation and said regional number portability subsystem is broken.
7. The system for porting a customer's local telephone number according to
claim 4 further comprising a plurality of transaction logging applications configured
to receive transaction requests, handle said requests and update said regional service database.
W wOυ 9v9/04w57/9y PCT US98/14368
8. An interface system for communicating telecommunications customer
porting requests from a local service provider to a number portability administration
center, said interface system comprising:
means for interfacing to local service provider business applications, said
means configured to accept transaction data from said business applications and
operably linked to at least one local order entry order processing terminal;
a transaction database cornrhunicably linked to said means for interfacing to
local service provider business applications, said transaction database containing a
plurality of customer telephone number data and a plurality of internally stored
transaction transfer applications that control the flow of data between said local
service provider and said number portabihty administration center;
a transaction message handling apphcation communicably linked to said
plurahty of internally stored applications for reading transaction data designated for
said number portability administration center; and
a managing application configured to receive said transaction data from said
transaction message handling application, said managing application communicably
linked to said number portability administration center.
9. The interface system according to claim 8 further comprising a
synchronization application coupled to botii said transaction database and said managing application and configured to re-synchronize said interface system after a predetermined period of downtime.
10. The interface system according to claim 9 further comprising an unsolicited
event handler application communicably linked to said managing application for
receiving notification transactions.
11. The interface system according to claim 8 further comprising:
a local service database containing a plurality of customer
telephone number data; and
a discrepancy reporting apphcation communicably linked to both said local
service database and said transaction database.
12. A method of porting a customer's telephone number among different
exchange carriers comprising the steps of:
requesting a change from a first service provider to a second service provider;
transmitting a customer's present telephone service information to a
repository containing a plurality of service provider and telephone customer data; and
porting said customer's present telephone service information from said
repository to said second service provider.
13. A system for porting a customer's telephone number among different
exchange carriers comprising:
a repository containing a plurahty of service provider and telephone customer
data;
means for requesting a change from a first service provider to a second
service provider;
means for transmitting a customer's present telephone service information to
said repostory, said means for transrm'tring communicably coupled to said repository
via a first link; and
means of porting said customer's present telephone service information from
said repository to said second service provider, said means of porting communicably
coupled to said repository via a second link.
PCT/US1998/014368 1997-07-21 1998-07-10 System and method for achieving local number portability WO1999004579A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU83944/98A AU8394498A (en) 1997-07-21 1998-07-10 System and method for achieving local number portability

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US08/897,906 US6366663B1 (en) 1997-07-21 1997-07-21 System for achieving local number portability
US08/897,906 1997-07-21

Publications (1)

Publication Number Publication Date
WO1999004579A1 true WO1999004579A1 (en) 1999-01-28

Family

ID=25408637

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US1998/014368 WO1999004579A1 (en) 1997-07-21 1998-07-10 System and method for achieving local number portability

Country Status (4)

Country Link
US (8) US6366663B1 (en)
AU (1) AU8394498A (en)
CA (1) CA2243386A1 (en)
WO (1) WO1999004579A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100325694B1 (en) * 1999-12-27 2002-02-25 오길록 Local number portability audit management process in local service management system

Families Citing this family (163)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH08123744A (en) * 1994-10-26 1996-05-17 Hitachi Ltd Work flow system
US6501950B1 (en) * 1996-03-14 2002-12-31 Bellsouth Intellectual Property Corporation Systems and methods for monitoring data signals on a communications network
US6104802A (en) 1997-02-10 2000-08-15 Genesys Telecommunications Laboratories, Inc. In-band signaling for routing
US7031442B1 (en) 1997-02-10 2006-04-18 Genesys Telecommunications Laboratories, Inc. Methods and apparatus for personal routing in computer-simulated telephony
KR100280045B1 (en) * 1997-05-02 2001-02-01 윤종용 Pigtailing method between optical waveguide device and optical fiber module
US6366663B1 (en) * 1997-07-21 2002-04-02 Mci Communications Corporation System for achieving local number portability
US6711611B2 (en) 1998-09-11 2004-03-23 Genesis Telecommunications Laboratories, Inc. Method and apparatus for data-linking a mobile knowledge worker to home communication-center infrastructure
US6985943B2 (en) 1998-09-11 2006-01-10 Genesys Telecommunications Laboratories, Inc. Method and apparatus for extended management of state and interaction of a remote knowledge worker from a contact center
USRE46528E1 (en) 1997-11-14 2017-08-29 Genesys Telecommunications Laboratories, Inc. Implementation of call-center outbound dialing capability at a telephony network level
US7907598B2 (en) 1998-02-17 2011-03-15 Genesys Telecommunication Laboratories, Inc. Method for implementing and executing communication center routing strategies represented in extensible markup language
US6298123B1 (en) 1998-03-26 2001-10-02 Bell Atlantic Network Services, Inc. Interconnect traffic tracking
US6351453B1 (en) 1998-03-26 2002-02-26 Bell Atlantic Network Services, Inc. Internet service provider (ISP) finder
US6411681B1 (en) 1998-03-26 2002-06-25 Bell Atlantic Network Services, Inc. Traffic track measurements for analysis of network troubles
US6282267B1 (en) 1998-03-26 2001-08-28 Bell Atlantic Network Services, Inc. Network planning traffic measurement program
US6385301B1 (en) * 1998-03-26 2002-05-07 Bell Atlantic Services Network, Inc. Data preparation for traffic track usage measurement
US6301336B1 (en) * 1998-03-26 2001-10-09 Mci Communications Corporation Method and apparatus for testing components in a communications system
DE19836560A1 (en) * 1998-08-12 2000-02-17 Siemens Ag Operability test method for switching centre
USRE46153E1 (en) 1998-09-11 2016-09-20 Genesys Telecommunications Laboratories, Inc. Method and apparatus enabling voice-based management of state and interaction of a remote knowledge worker in a contact center environment
US6922708B1 (en) * 1999-02-18 2005-07-26 Oracle International Corporation File system that supports transactions
US6560226B1 (en) * 1999-02-25 2003-05-06 Sprint Communications Company, L.P. System and method for caching ported number information
US7010110B2 (en) * 1999-03-31 2006-03-07 Walker Digital, Llc Method and apparatus for monitoring telephone status
US6195658B1 (en) * 1999-07-15 2001-02-27 Bell Atlantic Network Services, Incorporated Method and system for auditing a test database against a reference database
US6549916B1 (en) 1999-08-05 2003-04-15 Oracle Corporation Event notification system tied to a file system
US7280995B1 (en) 1999-08-05 2007-10-09 Oracle International Corporation On-the-fly format conversion
US7418435B1 (en) 1999-08-05 2008-08-26 Oracle International Corporation Multi-model access to data
US6438219B1 (en) 1999-08-31 2002-08-20 Worldcom, Inc. System, method and computer program product for achieving local number portability costing support
US6473503B1 (en) 1999-08-31 2002-10-29 Worldcom, Inc. System, method and computer program product for achieving local number portability network management support
US6473502B1 (en) 1999-08-31 2002-10-29 Worldcom, Inc. System, method and computer program product for achieving local number portability costing and network management support
US6970945B1 (en) * 1999-11-01 2005-11-29 Seebeyond Technology Corporation Systems and methods of message queuing
US6535599B1 (en) * 1999-11-08 2003-03-18 Sprint Communications Company, L.P. System and method for processing ported calls
US6480834B1 (en) * 1999-11-17 2002-11-12 Serena Software, Inc. Method and apparatus for serving files from a mainframe to one or more clients
US6529595B1 (en) * 1999-12-01 2003-03-04 Sprint Communications Company, L.P. Method and apparatus to process number portability data for a call
US7809382B2 (en) * 2000-04-11 2010-10-05 Telecommunication Systems, Inc. Short message distribution center
US8073477B2 (en) 2000-04-11 2011-12-06 Telecommunication Systems, Inc. Short message distribution center
EP1277145A4 (en) * 2000-02-16 2003-05-21 Bea Systems Inc Conversation management system for enterprise wide electronic collaboration
US7522911B2 (en) 2000-04-11 2009-04-21 Telecommunication Systems, Inc. Wireless chat automatic status tracking
US6732175B1 (en) 2000-04-13 2004-05-04 Intel Corporation Network apparatus for switching based on content of application data
US7146422B1 (en) * 2000-05-01 2006-12-05 Intel Corporation Method and apparatus for validating documents based on a validation template
US7185005B1 (en) 2000-05-12 2007-02-27 Oracle International Corporation Nested transactions in a file system
US7024394B1 (en) 2000-07-07 2006-04-04 International Business Machines Corporation System and method for protecting user logoff from web business transactions
US20020065947A1 (en) * 2000-07-13 2002-05-30 Clayton Wishoff Software application agent interface
US7216132B1 (en) * 2000-08-16 2007-05-08 Sparta Systems, Inc. System and method for automated process control
US6721732B2 (en) * 2000-10-02 2004-04-13 Scott S. Lawton Method and system for pre-filling search criteria into a form
US7058648B1 (en) 2000-12-01 2006-06-06 Oracle International Corporation Hierarchy-based secured document repository
US6819921B2 (en) * 2001-02-02 2004-11-16 Lucent Technologies Inc. Method of subscriber initiated porting of a wireless number for a mobile station
US6661888B2 (en) * 2001-02-23 2003-12-09 Open Support Systems, Llc Method for moving telecommunications customers onto a network
US20030033379A1 (en) * 2001-07-20 2003-02-13 Lemur Networks Intelligent central directory for soft configuration of IP services
US6658260B2 (en) 2001-09-05 2003-12-02 Telecommunication Systems, Inc. Inter-carrier short messaging service providing phone number only experience
US20030050922A1 (en) * 2001-09-13 2003-03-13 Sundeep Sanghavi System and method for obtaining dial-up access number
US7574501B2 (en) * 2001-09-25 2009-08-11 Siebel Systems, Inc. System and method for configuring and viewing audit trails in an information network
US7721193B2 (en) * 2001-10-18 2010-05-18 Bea Systems, Inc. System and method for implementing a schema object model in application integration
US7552222B2 (en) 2001-10-18 2009-06-23 Bea Systems, Inc. Single system user identity
US7206393B2 (en) * 2001-11-01 2007-04-17 Agilent Technologies, Inc. Apparatus and method for processing information from a telephone network
US7516447B2 (en) 2002-02-22 2009-04-07 Bea Systems, Inc. Methods and apparatus for building, customizing and using software abstractions of external entities
US7155438B2 (en) * 2002-05-01 2006-12-26 Bea Systems, Inc. High availability for event forwarding
US7257645B2 (en) * 2002-05-01 2007-08-14 Bea Systems, Inc. System and method for storing large messages
US7424717B2 (en) 2002-05-01 2008-09-09 Bea Systems, Inc. Systems and methods for business process plug-in development
US8135772B2 (en) 2002-05-01 2012-03-13 Oracle International Corporation Single servlets for B2B message routing
US7526519B2 (en) 2002-05-01 2009-04-28 Bea Systems, Inc. High availability application view deployment
US7222148B2 (en) 2002-05-02 2007-05-22 Bea Systems, Inc. System and method for providing highly available processing of asynchronous service requests
US7676538B2 (en) 2002-05-02 2010-03-09 Bea Systems, Inc. Systems and methods for application view transactions
US7350184B2 (en) 2002-05-02 2008-03-25 Bea Systems, Inc. System and method for enterprise application interactions
US7493628B2 (en) * 2002-05-02 2009-02-17 Bea Systems, Inc. Shared common connection factory
US7484224B2 (en) 2002-05-02 2009-01-27 Bae Systems, Inc. Adapter deployment without recycle
US7627631B2 (en) * 2002-05-02 2009-12-01 Bea Systems, Inc. Systems and methods for collaborative business plug-ins
US7246137B2 (en) * 2002-06-05 2007-07-17 Sap Aktiengesellschaft Collaborative audit framework
US20040068479A1 (en) * 2002-10-04 2004-04-08 International Business Machines Corporation Exploiting asynchronous access to database operations
WO2004036769A2 (en) * 2002-10-15 2004-04-29 Alcatel Wireless, Inc. Method and system for minimizing call setup delay for calls occurring in one or more wireless networks
US7460873B2 (en) 2003-02-07 2008-12-02 Sybase 365, Inc. Universal short code administration facility
US8019362B2 (en) 2003-02-07 2011-09-13 Sybase 365, Inc. Universal short code administration facility
US7672267B2 (en) * 2003-02-07 2010-03-02 Sybase 365, Inc. Intermediary network system and method for facilitating message exchange between wireless networks
US7154901B2 (en) * 2003-02-07 2006-12-26 Mobile 365, Inc. Intermediary network system and method for facilitating message exchange between wireless networks
US7340422B2 (en) 2003-02-10 2008-03-04 Asentinel Llc Systems and method for managing and processing of telecommunications invoices
US7293038B2 (en) 2003-02-25 2007-11-06 Bea Systems, Inc. Systems and methods for client-side filtering of subscribed messages
US7774697B2 (en) * 2003-02-25 2010-08-10 Bea Systems, Inc. System and method for structuring distributed applications
US7752599B2 (en) 2003-02-25 2010-07-06 Bea Systems Inc. Systems and methods extending an existing programming language with constructs
US7584474B2 (en) * 2003-02-25 2009-09-01 Bea Systems, Inc. Systems and methods for transaction chaining
US20050022164A1 (en) * 2003-02-25 2005-01-27 Bea Systems, Inc. Systems and methods utilizing a workflow definition language
US7299454B2 (en) * 2003-02-26 2007-11-20 Bea Systems, Inc. Method for multi-language debugging
US20050108682A1 (en) * 2003-02-26 2005-05-19 Bea Systems, Inc. Systems for type-independent source code editing
US7707564B2 (en) 2003-02-26 2010-04-27 Bea Systems, Inc. Systems and methods for creating network-based software services using source code annotations
US7539985B2 (en) * 2003-02-26 2009-05-26 Bea Systems, Inc. Systems and methods for dynamic component versioning
US7650276B2 (en) 2003-02-26 2010-01-19 Bea Systems, Inc. System and method for dynamic data binding in distributed applications
US20040230955A1 (en) * 2003-02-26 2004-11-18 Bea Systems, Inc. System for multi-language debugging
US7076772B2 (en) * 2003-02-26 2006-07-11 Bea Systems, Inc. System and method for multi-language extensible compiler framework
US8032860B2 (en) * 2003-02-26 2011-10-04 Oracle International Corporation Methods for type-independent source code editing
US20050044173A1 (en) * 2003-02-28 2005-02-24 Olander Daryl B. System and method for implementing business processes in a portal
US7444620B2 (en) 2003-02-28 2008-10-28 Bea Systems, Inc. Systems and methods for a common runtime container framework
US7636722B2 (en) 2003-02-28 2009-12-22 Bea Systems, Inc. System and method for describing application extensions in XML
US20040225995A1 (en) * 2003-02-28 2004-11-11 Kyle Marvin Reusable software controls
US7650592B2 (en) 2003-03-01 2010-01-19 Bea Systems, Inc. Systems and methods for multi-view debugging environment
US7013156B2 (en) 2003-03-13 2006-03-14 Mobile 365, Inc. Virtual network solution for SMS message exchange between GSM and ANSI (tia/eia 41) networks
US7272406B2 (en) * 2003-06-30 2007-09-18 Sybase 365, Inc. System and method for in-transit SMS language translation
US8229932B2 (en) 2003-09-04 2012-07-24 Oracle International Corporation Storing XML documents efficiently in an RDBMS
US20050086384A1 (en) * 2003-09-04 2005-04-21 Johannes Ernst System and method for replicating, integrating and synchronizing distributed information
US8694510B2 (en) * 2003-09-04 2014-04-08 Oracle International Corporation Indexing XML documents efficiently
US7760866B1 (en) * 2003-09-24 2010-07-20 Embarq Holdings Company, Llc System and method for auditing switch code routing instructions
US20050089151A1 (en) * 2003-10-24 2005-04-28 Han John M. Method and system for enabling and managing telephone number portability
US7181538B2 (en) * 2003-11-14 2007-02-20 Sybase 365, Inc. System and method for providing configurable, dynamic multimedia message service pre-transcoding
US7860498B2 (en) * 2003-12-01 2010-12-28 Sybase 365, Inc. System and method for virtual carrier addressing and routing for global short message service
US20050137838A1 (en) * 2003-12-18 2005-06-23 Medlyn Dayne H. Dial-up resource simulator
US7725545B2 (en) * 2004-02-20 2010-05-25 Sybase 365, Inc. Dual use counters for routing loops and spam detection
US7483707B2 (en) * 2004-03-02 2009-01-27 Sybase 365, Inc. Voting campaigns using universal voting card
US20050197885A1 (en) * 2004-03-02 2005-09-08 Derek Hung Kit Tam System and method for providing campaign management services
US7656885B2 (en) * 2004-03-12 2010-02-02 Sybase 365, Inc. Intermediary content gateway system and method
US7640211B2 (en) * 2004-03-12 2009-12-29 Sybase 365, Inc. System and method for billing augmentation
US6975711B2 (en) * 2004-04-07 2005-12-13 Sbc Knowledge Ventures, L.P. Method and system for forecasting telephony traffic trends using local number portability databases
US7930277B2 (en) * 2004-04-21 2011-04-19 Oracle International Corporation Cost-based optimizer for an XML data repository within a database
US20050262053A1 (en) * 2004-05-18 2005-11-24 Taiwan Semiconductor Manufacturing Co., Ltd. System and method for storing and accessing information via smart knowledge agents
US20070208946A1 (en) * 2004-07-06 2007-09-06 Oracle International Corporation High performance secure caching in the mid-tier
US7430284B2 (en) * 2004-08-19 2008-09-30 Sybase 365, Inc. Architecture and methods for inter-carrier Multi-Media Messaging
US7721287B2 (en) * 2004-08-31 2010-05-18 Sap Ag Organizing transmission of repository data
US7721288B2 (en) * 2004-08-31 2010-05-18 Sap Ag Organizing transmission of repository data
US7627547B2 (en) * 2004-11-29 2009-12-01 Oracle International Corporation Processing path-based database operations
US7921076B2 (en) 2004-12-15 2011-04-05 Oracle International Corporation Performing an action in response to a file system event
US8131766B2 (en) * 2004-12-15 2012-03-06 Oracle International Corporation Comprehensive framework to integrate business logic into a repository
US20100290365A1 (en) * 2004-12-22 2010-11-18 Kwong Andrew W Multi-level hosted inbound administration for a telephony system
US7398224B2 (en) * 2005-03-22 2008-07-08 Kim A. Cooper Performance motivation systems and methods for contact centers
US20070121603A1 (en) * 2005-09-30 2007-05-31 Clark Joseph E Iii Method and system for creating VoIP routing registry
US8073841B2 (en) * 2005-10-07 2011-12-06 Oracle International Corporation Optimizing correlated XML extracts
US7929683B1 (en) * 2005-10-07 2011-04-19 At&T Mobility Ii Llc Systems and methods for managing a numbering plan area split with LRN routed calls
US8356053B2 (en) * 2005-10-20 2013-01-15 Oracle International Corporation Managing relationships between resources stored within a repository
US8949455B2 (en) 2005-11-21 2015-02-03 Oracle International Corporation Path-caching mechanism to improve performance of path-related operations in a repository
US9008075B2 (en) 2005-12-22 2015-04-14 Genesys Telecommunications Laboratories, Inc. System and methods for improving interaction routing performance
US7738640B1 (en) 2005-12-28 2010-06-15 At&T Intellectual Property Ii, L.P. Methods for reconciling discrepancies in circuit information among various telecommunication network management systems
US7630325B1 (en) * 2005-12-28 2009-12-08 At&T Corp. Methods for reconciling trunk group identification information among various telecommunication network management systems
US7650367B2 (en) * 2006-01-13 2010-01-19 Tekelec Methods, systems, and computer program products for detecting and restoring missing or corrupted data in a distributed, scalable, redundant measurement platform database
US20070203909A1 (en) * 2006-02-28 2007-08-30 Tekelec Methods, systems, and computer program products for indexing, validating, recovering, and consolidating a database indexed by range-bound numeric data
US8584122B2 (en) 2006-03-31 2013-11-12 Ebay Inc. Batch scheduling
US20070245018A1 (en) * 2006-04-12 2007-10-18 International Business Machines Corporation Dynamic access control in a content-based publish/subscribe system with delivery guarantees
US7933392B1 (en) * 2006-05-31 2011-04-26 The Nielsen Company (Us), Llc Method and system for measuring market-share for an entire telecommunication market
US8572182B2 (en) * 2006-07-21 2013-10-29 Blackberry Limited Handling notifications in instant messaging systems
US8355485B2 (en) 2006-08-21 2013-01-15 Centurylink Intellectual Property Llc System and method for reporting telecommunications utilization and forecasting
US8433052B2 (en) 2006-08-21 2013-04-30 Centurylink Intellectual Property Llc System and method for requesting additional telephone numbering information for reporting
US8265257B2 (en) * 2006-08-21 2012-09-11 Centurylink Intellectual Property Llc System and method for determining telephone number blocks available for pooling donation
US8023628B2 (en) * 2006-08-21 2011-09-20 Embarq Holdings Company, Llc System and method for auditing a telephone number inventory of a telecommunications carrier
US8457630B2 (en) * 2006-08-25 2013-06-04 Research In Motion Limited System and method for transferring a device between mobile carriers
JP4961931B2 (en) * 2006-09-29 2012-06-27 富士通株式会社 Job execution scheduling program, job execution scheduling method, and job execution scheduling apparatus
US7797310B2 (en) * 2006-10-16 2010-09-14 Oracle International Corporation Technique to estimate the cost of streaming evaluation of XPaths
US9183321B2 (en) * 2006-10-16 2015-11-10 Oracle International Corporation Managing compound XML documents in a repository
US7827177B2 (en) * 2006-10-16 2010-11-02 Oracle International Corporation Managing compound XML documents in a repository
US20090003388A1 (en) * 2007-06-30 2009-01-01 Lucent Technologies, Inc. Method and apparatus for synchronizing ported number data
US8170190B2 (en) * 2007-12-20 2012-05-01 Verizon Patent And Licensing Inc. Method and system for managing telephone number allocation
US8244716B2 (en) * 2008-06-13 2012-08-14 Oracle International Corporation Data pattern for storing information, including associated version and audit information for use in data management
US7958112B2 (en) 2008-08-08 2011-06-07 Oracle International Corporation Interleaving query transformations for XML indexes
US8279852B2 (en) 2008-10-01 2012-10-02 The Nielsen Company (Us), Llc Method and system for measuring market share for voice over internet protocol carriers
US8837699B2 (en) 2008-10-01 2014-09-16 The Nielsen Company (Us), Llc Methods and apparatus to monitor subscriber activity
GB2476779B (en) * 2008-11-19 2011-12-21 Ericsson Telefon Ab L M Provisioning method and system
US20100150329A1 (en) * 2008-12-12 2010-06-17 Verizon Data Services Llc Distributed order processing
US8355495B2 (en) * 2009-02-25 2013-01-15 Telcordia Technologies, Inc. Multi vendor NPAC administration peering
US8369826B2 (en) 2009-03-18 2013-02-05 The Nielsen Company (Us), Llc Methods and apparatus to identify wireless subscriber activity status
US8908852B2 (en) * 2009-07-24 2014-12-09 Verizon Patent And Licensing Inc. System and method of providing local number portability
CA2714784A1 (en) * 2009-09-17 2011-03-17 Royal Canadian Mint/Monnaie Royale Canadienne Message storage and transfer system
US8688776B1 (en) * 2009-12-29 2014-04-01 The Directv Group, Inc. Emulation tool and method of using the same for a content distribution system
US20110208506A1 (en) * 2010-02-24 2011-08-25 Sling Media Inc. Systems and methods for emulating network-enabled media components
GB2478525A (en) * 2010-03-08 2011-09-14 Tyntec Ltd Memory device for providing message redirection data
US8929854B2 (en) 2011-10-27 2015-01-06 Telecommunication Systems, Inc. Emergency text messaging
US8948795B2 (en) 2012-05-08 2015-02-03 Sybase 365, Inc. System and method for dynamic spam detection
US8891750B2 (en) 2012-12-11 2014-11-18 Soundbite Communications, Inc. Identifying recycled telephone numbers
US8934480B2 (en) 2013-03-18 2015-01-13 Verizon Patent And Licensing Inc. Enriching traffic data in a telephone network
US9123076B2 (en) 2013-10-16 2015-09-01 Nasdaq OMX Group, Inc. Customizable macro-based order entry protocol and system
US10374868B2 (en) * 2015-10-29 2019-08-06 Pure Storage, Inc. Distributed command processing in a flash storage system
US10277735B2 (en) * 2017-03-10 2019-04-30 Neustar, Inc. Individual telephone number assignment

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0710042A2 (en) * 1994-10-26 1996-05-01 AT&T Corp. Means and method for providing local telephone number portability
US5625681A (en) * 1995-08-11 1997-04-29 Stratus Computer, Inc. Method and apparatus for telephone number portability

Family Cites Families (56)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4720850A (en) * 1986-03-14 1988-01-19 American Telephone And Telegraph Company At&T Bell Laboratories Communication system control arrangement
ATE155269T1 (en) 1989-08-14 1997-07-15 Centillion Data Systems Inc COST ACCOUNTING SYSTEM
US5640319A (en) * 1991-03-18 1997-06-17 Lucent Technologies Inc. Switch control methods and apparatus
US5625669A (en) * 1991-09-27 1997-04-29 Telemac Cellular Corporation Mobile phone with internal call accounting controls
US5218632A (en) 1991-10-16 1993-06-08 Telefonaktiebolaget L M Ericsson Flexible call detail recording system
US5333183A (en) 1992-03-13 1994-07-26 Moscom Corporation Universal MDR data record collection and reporting system
US5384822A (en) 1992-06-30 1995-01-24 At&T Corp. Computer controlled test facility for a telecommunication switch
US5802502A (en) * 1993-05-24 1998-09-01 British Telecommunications Public Limited Company System for selective communication connection based on transaction pricing signals
US5715303A (en) 1993-05-26 1998-02-03 U S West Communications, Inc. Method and system for configuring a telecommunication switch and identifying a record generated by same
US5835757A (en) 1994-03-30 1998-11-10 Siemens Telecom Networks Distributed database management system for servicing application requests in a telecommunications switching system
US5625816A (en) 1994-04-05 1997-04-29 Advanced Micro Devices, Inc. Method and system for generating product performance history
US5896440A (en) 1994-05-26 1999-04-20 Gte Service Corporation System and method for providing a unified communications link between divergent communication networks
US5832068A (en) 1994-06-01 1998-11-03 Davox Corporation Data processing system with real time priority updating of data records and dynamic record exclusion
US5546574A (en) 1994-06-30 1996-08-13 At&T Corporation Peer-to-peer data concurrence processes and apparatus
US5742905A (en) * 1994-09-19 1998-04-21 Bell Communications Research, Inc. Personal communications internetworking
SE515265C2 (en) 1994-10-17 2001-07-09 Ericsson Telefon Ab L M Systems and methods for processing signal data and communication systems comprising a signal data processing system
US5734977A (en) * 1994-11-10 1998-03-31 Telefonaktiebolaget Lm Ericsson Fraud detection in radio communications network
US5757895A (en) 1995-11-09 1998-05-26 Unisys Corporation Extracting and processing data derived from a common channel signalling network
US5774532A (en) 1995-04-21 1998-06-30 Mci Corporation Single network record construction
US5854834A (en) 1995-04-21 1998-12-29 Mci Communications Corporation Network information concentrator
US5717745A (en) 1995-04-24 1998-02-10 Mci Communications Corporation System and method of efficiently evaluating different messages by a server in a telecommunications environment
US5606600A (en) 1995-05-10 1997-02-25 Mci Communications Corporation Generalized statistics engine for telephone network employing a network information concentrator
CA2174796C (en) 1995-06-19 2000-04-18 James Patrick Dunn Method for automatic maintenance of a local number portability database
US5748724A (en) * 1995-06-30 1998-05-05 Siemens Stomberg-Carlson Method for transferring a subscriber to a new local service provider
US5887056A (en) * 1995-06-30 1999-03-23 Siemens Information And Communication Networks Method for routing telephone calls to subscribers of different service providers within a common numbering plan area
US5970131A (en) * 1995-06-30 1999-10-19 Siemens Information And Communication Networks, Inc. Method for providing location/geographic portability in a system having different service providers within a common numbering plan area
US5978464A (en) * 1995-06-30 1999-11-02 Siemens Information And Communications Networks, Inc. Method for updating a local switch internal database in system having different service providers within a common numbering plan area
US6115458A (en) * 1995-07-14 2000-09-05 American Express Travel Related Services Company, Inc. Method and apparatus for summaries of prepaid instrument transaction activity
US5703939A (en) 1995-07-27 1997-12-30 Lucent Technologies, Inc. Method for determining an optimum point for database queries during call delivery in a telecommunications network
US5566235A (en) 1995-10-05 1996-10-15 Bell Atlantic Network Services, Inc. Customer controlled service mediation management
US6445785B1 (en) * 1995-11-21 2002-09-03 Verizon Laboratories Inc. Methods and apparatus for local number portability in telecommunication systems
US5764745A (en) * 1995-12-15 1998-06-09 Gte Laboratories Incorporated Apparatus and method for local number portability using nongeographic subscriber numbers
US5787147A (en) 1995-12-21 1998-07-28 Ericsson Inc. Test message generator in a telecommunications network
US5765172A (en) 1996-01-23 1998-06-09 Dsc Communications Corporation System and method for verifying integrity of replicated databases
US5784443A (en) 1996-02-01 1998-07-21 Mci Corporation Integrated revenue domain for telecommunication networks
US5912962A (en) * 1996-02-06 1999-06-15 Northern Telecom Limited Method of porting for use with local number portability
US5734705A (en) 1996-03-29 1998-03-31 Xiox Corporation Intelligent configuration server for PBX
US5793861A (en) 1996-06-11 1998-08-11 Executone Information Systems, Inc. Transaction processing system and method
EP0827319A3 (en) * 1996-07-30 2000-05-17 Hewlett-Packard Company Global title translation in a telecommunications signalling network supporting number portability
US5823068A (en) * 1996-08-27 1998-10-20 Comair Rotron, Inc. Rotating system with reduced transference of vibration and acoustics and method for reducing same
US5861810C1 (en) * 1996-09-27 2001-02-27 Interactive Systems Llc System and method for providing crime victims updated informations and emergency alert notices
US5809108A (en) 1996-09-27 1998-09-15 Mci Communications Corporation Automated test call generation and execution system
US6134316A (en) 1996-10-18 2000-10-17 Telefonaktiebolaget Lm Ericsson Telecommunications network with relocateability of subscriber number
US5835497A (en) 1996-10-30 1998-11-10 Mci Communications Corporation Call record broadcast via an interface in a telecommunications network
US5761272A (en) 1996-11-26 1998-06-02 Mci Communications Corporation Method of and system for performing telecommunications stress testing
SE511357C2 (en) 1996-12-19 1999-09-20 Ericsson Telefon Ab L M Method and apparatus of a telecommunications network
US6122362A (en) 1996-12-24 2000-09-19 Evolving Systems, Inc. Systems and method for providing network element management functionality for managing and provisioning network elements associated with number portability
US6169793B1 (en) 1996-12-24 2001-01-02 Evolving Systems, Inc. Systems and methods for providing order and service mediation for telecommunications systems
US5930337A (en) * 1997-02-04 1999-07-27 Lucent Technologies Inc. Dynamic message-mailbox size variation
US5903632A (en) 1997-03-19 1999-05-11 Tmax Technologies Inc. Automated telephone directory
US5910981A (en) * 1997-03-26 1999-06-08 Lucent Technologies Inc. Automatic updating of a local database supporting local number portability
US6000031A (en) * 1997-05-01 1999-12-07 At&T Corp Method and system for collecting and authenticating updates to a network-based directory service
US5910983A (en) 1997-05-19 1999-06-08 Rockwell Semiconductor Systems, Inc. Apparatus and method for identifying records of overflowed ACD calls
US5901215A (en) 1997-05-20 1999-05-04 Rockwell Semiconductor Systems, Inc. Apparatus and method for identifying records of overflowed ACD calls
US5933489A (en) * 1997-06-30 1999-08-03 Telcordia Technologies, Inc. Method and apparatus for handling subscription and administrative requests in a local service management system
US6366663B1 (en) 1997-07-21 2002-04-02 Mci Communications Corporation System for achieving local number portability

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0710042A2 (en) * 1994-10-26 1996-05-01 AT&T Corp. Means and method for providing local telephone number portability
US5625681A (en) * 1995-08-11 1997-04-29 Stratus Computer, Inc. Method and apparatus for telephone number portability

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100325694B1 (en) * 1999-12-27 2002-02-25 오길록 Local number portability audit management process in local service management system

Also Published As

Publication number Publication date
US20040024765A1 (en) 2004-02-05
US6370548B1 (en) 2002-04-09
CA2243386A1 (en) 1999-01-21
US6047045A (en) 2000-04-04
US6411698B1 (en) 2002-06-25
US6067354A (en) 2000-05-23
US6415028B1 (en) 2002-07-02
US6366663B1 (en) 2002-04-02
AU8394498A (en) 1999-02-10
US6636868B1 (en) 2003-10-21
US7263533B2 (en) 2007-08-28

Similar Documents

Publication Publication Date Title
US6366663B1 (en) System for achieving local number portability
CA2276019C (en) Systems and methods for providing telecommunications services
US7024450B1 (en) Method and apparatus for deploying service modules among service nodes distributed in an intelligent network
AU760777B2 (en) Method and apparatus for deploying service modules among service nodes distributed in an intelligent network
US5610915A (en) System and method therefor of viewing call traffic of a telecommunications network
US5638431A (en) Calling card validation system and method therefor
US5706286A (en) SS7 gateway
US5825769A (en) System and method therefor of viewing in real time call traffic of a telecommunications network
US7266192B2 (en) Retrieval of data related to a call center
US6512824B1 (en) Proxy database for element management system of telephone switching network
US7912858B2 (en) Data synchronization method
US5963943A (en) System and method for storing and retrieving performance and topology information
WO1998028899A9 (en) Systems and methods for providing telecommunications services
JP2002521921A (en) Multi-protocol interface device at service control point
US5966713A (en) Method for determining the contents of a restoration log
KR100322671B1 (en) Ain ststem based on international specifications in wire or wireless communication networks
JPH07226797A (en) Communication system and communication service control method
KR100236925B1 (en) Method for processing paging requests of ips

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AL AM AT AU AZ BA BB BG BR BY CA CH CN CU CZ DE DK EE ES FI GB GE GH HU IL IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MD MG MK MN MW MX NO NZ PL PT RO RU SD SE SG SI SK SL TJ TM TR TT UA UG UZ VN YU ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW SD SZ UG ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

NENP Non-entry into the national phase

Ref country code: JP

Ref document number: 1999507542

Format of ref document f/p: F

NENP Non-entry into the national phase

Ref country code: CA

122 Ep: pct application non-entry in european phase