|Publication number||US7277421 B1|
|Application number||US 10/050,733|
|Publication date||2 Oct 2007|
|Filing date||16 Jan 2002|
|Priority date||16 Jan 2002|
|Publication number||050733, 10050733, US 7277421 B1, US 7277421B1, US-B1-7277421, US7277421 B1, US7277421B1|
|Inventors||Paul Barry Pershan|
|Original Assignee||Verizon Services Corp.|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (24), Non-Patent Citations (7), Referenced by (30), Classifications (14), Legal Events (4)|
|External Links: USPTO, USPTO Assignment, Espacenet|
The present invention is directed to communication systems, and more particularly, methods and apparatus for transitioning telephone services from the existing Public Switched Telephone Network (PTSN) to a Voice Over Internet Protocol (VOIP) telephone network.
The use of telephones for communications purposes is commonplace and often taken for granted. If someone wants to talk to another person on the other side of the country, he or she can pick up a telephone and dial the person's phone number. A ringing noise is heard and normally, the called party answers the phone. Presently, in most cases, the ensuing cross-country conversation is carried over the Public Switched Telephone Network (PSTN). The PSTN has been upgraded on a nearly continuous basis as advances in technology have made improvements possible. For example, fiber optic lines have replaced the use of copper lines in many parts of the PSTN. In addition, digital telephone switches have replaced older analog telephone switches.
While significant changes have been made to the PSTN over the years, to the end user, i.e., customer, these changes have been relatively transparent. In most cases, end users have been allowed to keep their existing telephone numbers and receive their existing telephone services despite network changes resulting from network upgrades. As known in the art, the PSTN uses a Time Division Multiplexing (TDM) based network.
Telephone service providers are currently confronting the possibility of a transition from the current TDM based network to IP packet based networks which are likely to carry voice calls in the future. Unless significant steps are made to smooth the transition to a telephone system based on VOIP, this transition represents a dramatic development that has the potential for presenting customers with noticeable changes in their telephone services, including telephone number changes.
As technology evolves once again and the prospect of moving from a Time Division Multiplexing (TDM) based network to a Voice over IP (VOIP) based network becomes more of a reality, several major issues arise.
From a technical standpoint, e.g., from a telephone switch deployment and operational perspective, there is the issue of how to move calls and users from the PSTN to the VOIP network and back, as may be required.
In addition to the issues of physical implementation, there is the practical issue of how to make the transition to a VOIP telephone system as transparent as possible to telephone users. For example, it is highly desirable that phone numbers should not change, and preferably the telephone services that a customer currently receives should continue to function. Maintaining existing phone numbers is particularly important to large companies who want to keep their phone numbers for business purposes. In addition, services such as call forwarding, call waiting, voice mail, etc. are used by many end users, and an interruption in these billable services would be an inconvenience, and may hurt the telephone company from both a customer satisfaction and revenue standpoint.
Companies, even more so than individuals, tend to be risk adverse when it comes to implementing new technology. For this reason, large companies who use multiple phone lines, will probably want to migrate to a VOIP network gradually, e.g., a few lines at a time. This is likely to be the case at least until the VOIP technology has been proven to be reliable. For example, if a company has 100 telephone lines it may only want to convert 25 of those lines into VOIP network telephone lines, in order to test the new technology without potentially losing all communications. In addition, before committing to switching lines to the VOIP telephone network, a company may want assurances that it will be able to switch the telephone lines back to the existing PSTN on short notice in the event that difficulties are encountered with the VOIP service.
A gradual transition of the type likely to occur presents hardware deployment challenges to telephone companies. Telephone companies may wish to provide VOIP telephone service for a small number of lines serviced by an existing switch, e.g., 25 lines out of a company's 100 lines, without having to make hardware upgrades to, or replace, the telephone switch which directly services the company's office. Given the cost of upgrading switches, it may only be justifiable from a cost standpoint, to upgrade an otherwise functional telephone switch, when a large number of subscribers or telephone lines serviced by the switch are ready to be transferred to VOIP service. Unfortunately, it is unlikely that a large number of users will agree to switch to a relatively new and somewhat unproven technology all at once.
In order to provide enhanced telephone services, many telephone companies now support, as part of the PSTN, Advanced Intelligent Network (AIN) functionality. AIN capabilities have made it easier to provide a wide array of previously unavailable telephone services. In an AIN system, telephone central offices each include one or more switches, each of which serves as a signal switching point (SSP).
Each SSP can detect one of a number of call processing events called AIN “triggers” or events. One such trigger is a Specific Digit String (SDS) trigger. This trigger is activated based on exact matches in the digits of a phone number, with a corresponding set of trigger digits. For example, if an SSP has an SDS six digit trigger set to 123-456, then any call passing through the switch directed to a phone number starting with 123-456 will activate that trigger. A local number portability (LNP) trigger is a type of trigger that will also be activated in response to a specific set of digits in a call matching a set of digits set as part of the LNP trigger.
When an AIN trigger is activated at an SSP because of the occurrence of a trigger event, the SSP suspends processing of the call that activated the trigger and generates a call processing message, e.g., a TCAP message, used to obtain call processing instructions from a service control point (SCP). The SSP forwards the call processing message, e.g., via a common channel interoffice signaling (CCIS) link utilizing the Signal System 7 (SS7) protocol, to a Service Control Point (SCP). The SCP determines the appropriate call processing instruction(s) to be sent from the switch based on software instructions and, in many cases, call specific information received from the switch. The call specific information may include, e.g., the calling party telephone number, the called party telephone number and one or more additional numbers or fields included in the call processing message received by the SCP which are available from a call transmitted in accordance with the SS7 standard.
The SCP may be implemented as an integrated service control point (ISCP). ISCPs normally include service creation logic and other functionality sometimes omitted from standard SCPs. If needed, the SCP can instruct the SSP at which the AIN trigger was activated to obtain and forward additional information, e.g., information relating to the call.
In response to a call processing message, the SCP accesses one or more stored call processing information or records (CPRs) to generate from the data received from the SSP one or more control messages. The call control messages are used to instruct the SSP on how to process the call that activated the AIN trigger. As part of a call control message, an ISCP can instruct the SSP to complete, e.g., forward the call, to a destination number provided by the SSP. Thus, an SCP can redirect a call in response to activation of an AIN trigger.
The SCP also has the ability to send the call to an outside resource, such as an intelligent peripheral using a send to outside resource (STOR) instruction. Intelligent peripherals are frequently coupled to SSPs to provide message announcement capabilities, voice recognition capabilities and other functionality which is not normally provided by the SSP.
In response to control messages, the SSP completes the phone call to which the control message relates as instructed by the control message.
In order to be allowed to compete in both he local and long distance telephone markets, some providers of local telephone service have had to open up the markets in which they provide local telephone service to competition. This often involves providing a mechanism by which a competitor's telephone switch can be used to provide local call routing and billing operations despite the fact that the customer's telephone line is not directly connected to the competitor's switch.
Some telephone service providers use AIN functionality and in particular, the AIN Local Number Portability (LNP), to enable a competitor's telephone switch to provide local telephone service despite the fact that the competitor's switch is not directly coupled to the end user's customer premise.
AIN LNP triggers are activated by calls originating from, or directed to a telephone number or portion thereof, are set at SSPs. Normally, the first six digits of telephone numbers that have been ported to another physical location activate the LNP trigger in an SSP.
Once an LNP trigger is activated at an SSP, the SSP pauses the call that activated the trigger, and sends a call processing message to an SCP. The SCP accesses a LNP database that includes information associating ported telephone numbers to Location Routing Numbers (LRNs). Each LRN normally corresponds to a telephone switch, e.g., a competitor's switch, which is responsible for servicing one or more ported calls. Accordingly, the LRN is the number that identifies the SSP to which the called telephone number is ported. While one LRN is associated with each ported telephone number, normally, several ported telephone numbers are associated with the same LRN.
In response to an LNP trigger being activated the SCP obtains from an LNP database the LRN corresponding to the ported number which activated the LNP trigger. The retrieved LRN is placed in the called party field, and the actual called telephone number is placed in a spare field of a call completion message sent by the SCP to the SSP. This call processing data is returned to the SSP, where call processing is resumed. The SSP looks in the called party field and routes the call to the SSP identified by the LRN in the called party field, i.e., the SSP to which the telephone number was ported.
When an SSP receives a call directed to its LRN it extracts the actual called party number from the spare field and then proceeds to process the call using the extracted called party number. In this manner, using the actual telephone number, the call is completed to the called party by the second, e.g., competitors, SSP. This is not correct.
From the above discussion, it is clear that AIN functionality has been used to provide a wide range of services such as call forwarding and call screening. It has even been used to support competition between local telephone service providers. The transition to VOIP is particularly challenging since such functionality may not fully exist in VOIP networks.
In view of the above discussion, it is apparent that there is a need for methods of effectively moving voice and/or data from a PSTN environment to and from a VOIP environment. It is desirable that these methods be transparent or relatively transparent to the end user, e.g., customers should be able to receive their current telephone services regardless of being moved to or from a VOIP environment. In addition, the method should allow for gradual transition from the PSTN to a VOIP network.
The present invention is directed to methods and apparatus for transitioning from use of the PSTN to VOIP networks to provide telephone service.
In accordance with the present invention, telephone customers are allowed to keep their existing PSTN telephone numbers but receive telephone service from the VOIP network, e.g., using an IP telephony device. Methods and apparatus of the present invention for allowing telephone numbers to be ported to a VOIP network, in a manner that is relatively transparent to the telephone service subscriber, rely on the use of one or more AIN triggers set in the PSTN to facilitate the porting of the telephone number to the VOIP network.
In accordance with one feature of the present invention, rather than upgrade each existing telephone switch in the PSTN to support a connection to the VOIP network, a few switches in the PSTN are upgraded to include links, e.g., trunks, to the VOIP network and the functionality required to communicate calls between the VOIP network and the PSTN. Alternatively and/or in conjunction with upgrading some switches, new switches are added to the PSTN with links to the VOIP network. Telephone switches in the PSTN with links to the VOIP network are called gateway switches.
In accordance with SS7, a call normally comprises a data portion and an audio, e.g., voice, portion. In the PSTN the data portion of a call is normally transmitted using out of band signaling. In the case of IP telephony, both the audio and data portions of a call are transmitted using IP packets.
In the case of an originating PSTN call, the originating switch normally adds the data portion of the call, i.e., call origination information such as calling party information, to the voice portion received from the calling party's telephony device, e.g., telephone. In the case of IP calls, the call originating from the calling party's telephony device may include both a data portion, e.g., calling party IP address and/or other identification information, and a voice portion, e.g., packetized speech. Additional data may be added to a call by switches or other network devices used to forward the call or, alternatively, the network device forwarding the call may modify the data portion of the call. The data portion of a call normally includes fields such as a calling party field, a called party field and an alternate billing field. The calling party field may include, e.g., the calling party's telephone number. The called party field may include, e.g., the called party's telephone number. The data portion of a call may also include originating switch information, etc. These fields provide call related information which can be used for call screening, forwarding, billing and other purposes. For this reason, these fields are sometimes called information fields. The voice portion of the call normally includes audio, e.g., speech, obtained from the calling and/or called party.
Telephone numbers may be ported from one switch to another. Telephone numbers are normally assigned to be serviced by particular end office switches in blocks based on their numerical value, e.g., the first six or more digits of the telephone number. Thus, each telephone number corresponds to a block of telephone numbers which has been assigned to be serviced by a switch. Ported telephone numbers are telephone numbers which are serviced by a switch which differs from the telephone switch responsible for servicing the block of telephone numbers to which the ported telephone number corresponds. The switch to which a telephone number is ported may be in either the PSTN or VOIP networks.
Calls originating in the PSTN that are directed to telephone numbers which have been ported to the VOIP network, are first routed to the PSTN telephone switch which served as the ported phone number's terminating switch prior to the number being ported to the VOIP network. An AIN trigger, e.g., an LNP trigger, is set at the PSTN telephone switch from which the telephone number was ported to the VOIP network. The AIN trigger is set to be activated by calls to one or more telephone numbers that have been ported to the VOIP network. A six digit LNP trigger may be used for this purpose. When the trigger is activated, at a switch from which a telephone number was ported, call processing is paused and an SCP is contacted to determine what call processing should be performed. The SCP compares the called number which activated the LNP trigger to a database of ported numbers. If the telephone number is not in the database because it was not ported to the VOIP network, the call is allowed to be completed in the normal manner. If the called number was ported to the VOIP network, a gateway telephone switch associated with the ported telephone number being called is identified from the LNP database accessed by the SCP. The SCP then instructs the switch where the call was paused to forward the call to the gateway switch assigned to handle the particular called telephone number.
Assuming the telephone service subscriber to whom the ported number corresponds, subscribes to one or more AIN telephone services, e.g., Centrex, call screening, or call forwarding services, an AIN trigger will be set at the gateway switch which will be activated by forwarded calls directed to the subscriber number. If such a trigger is encountered, on the called party's number, call processing will be paused and call processing instructions will be obtained from the SCP in the normal manner in which AIN processing is used to control a call. Thus, telephone service subscriber's whose telephone numbers have been ported to the VOIP network can continue to receive PSTN based AIN services on calls routed to the party via the PSTN.
Assuming that the SCP determines that the call should be completed to the ported telephone number, following activation of an AIN trigger at the gateway switch, the SCP will instruct the gateway switch to complete the call to the called number. This will involve completing the call to the IP telephony device to which the telephone number corresponds via the IP network. In response to the call completion message from the SCP, the IP gateway switch will perform the necessary operations to convert the SS7 call to IP packets and route the call, via the VOIP network, to the called party. Conventional SS7 information, e.g., calling party and called party information, may be included with the packetized information transmitted in the form of IP packets to the called party.
In accordance with one feature of the present invention, prior to instructing the gateway switch in the PSTN to complete the call to the called number using the VOIP network, the SCP queries a database maintained in the IP network for information corresponding to the called telephone number. In accordance with the invention, the database of IP telephone number information is accessed through the use of either session initiation protocol (SIP) and/or ENUM which are two competing protocols for obtaining information relating to a telephone number used by an IP device and/or IP telephone service subscriber. SIP is described in document RFC 2543 dated March 1999, titled “SIP: Session Initiation Protocol”, published by the Internet Society's Network Working Group. ENUM is described in document RFC 2916 dated September 2000, titled “E.164 number and DNS”, which is also published by the Internet Society's Network Working Group.
Information obtained from having the PSTN device, e.g., SCP, access the IP network based IP telephone information database is used in various embodiments to determine how to complete a call directed to an IP telephony device. For example, if the retrieved information indicates that calls directed to the called telephone number are to be forwarded to a telephone number serviced by the PSTN, the call will be completed to the indicated “forward to” telephone number without being routed through the VOIP network. In other cases, if the retrieved information indicates the called party is busy, unavailable, lacks the required bandwidth, or does not accept calls in the language in which the call is being supplied, the calling party will be notified of the inability to complete the call and the call will be terminated without routing to the VOIP network. The playing of such call termination notification messages to the calling party may be performed by an IP coupled to the IP gateway switch or coupled to another switch in the PSTN in response to instructions received by the gateway switch from the service control point.
Thus, in accordance with the present invention, the need to convert and transmit calls from the PSTN to the VOIP network is reduced or eliminated. This most frequently occurs in the case where data available from the IP network indicates that the call can not be completed to the called telephone number in the VOIP network.
Calls may be placed from IP telephone devices in the VOIP network, corresponding to ported telephone numbers, to PSTN telephone numbers. In accordance with the present invention, such calls will be routed from the VOIP network to the PSTN through a PSTN gateway switch that has the ability to convert between a packetized call format and an SS7 call format. In accordance with the present invention, prior to or at the gateway switch, called party information, e.g., the telephone number of the called party is placed in a spare information field associated with the telephone call and the calling party number is inserted in the called party field of the IP telephone call directed to a PSTN number.
At the gateway switch, AIN triggers, e.g., one or more SDS triggers, are set to be activated by calls from the VOIP network based on the telephone number included in the called party field. Upon activation of such a trigger, call processing is paused and a TCAP message is sent to the SCP to determine what call processing should be performed. Upon receiving such a message, the SCP compares the called party number to an information database listing VOIP numbers and numbers which were ported to the VOIP network from the PSTN.
For numbers which were ported from the VOIP network to the PSTN, the accessed database will indicate the PSTN telephone switch which is responsible for performing call billing operations for calls originating from the calling party. This telephone switch will normally be the telephone switch from which the calling party telephone number was ported to the VOIP network. The SCP will generate a call completion message with the actual called party telephone number serving as the called party number. This information is obtained by the SCP from the spare field, e.g., alternate billing field, into which it was inserted prior to being sent to the SCP. In addition, the SCP supplies billing information to the gateway switch which is transmitted to the switch which is to perform billing for calls originating from the called party whose number was ported to the VOIP domain. In this manner, customers can be billed from the same switch which provided their telephone service prior to their telephone number being ported to the VOIP network.
In response to the call completion message, the call from the VOIP network will be routed to the called party in the PSTN domain using normal PSTN routing procedures. However, as noted above, the calling party will be billed for the call by the switch which performed this operation prior to the calling party telephone number being ported to the VOIP domain.
In the above described manner, using existing AIN telephone switch capabilities, PSTN telephone numbers can be ported to the VOIP network. This can be done with the ported customers still receiving all or many of the telephone services, e.g., AIN based services, which they received prior to agreeing to have their telephone number and telephone service switched to the VOIP network. In addition, large customers can limit the transition to the VOIP network to a subset of the telephone numbers they use without fear of losing services or being unable to switch back to PSTN service if problems are encountered. Furthermore, from the telephone company perspective, one or more lines serviced by an existing PSTN switch without having to provide hardware upgrades at the PSTN switch from which the telephone number is being ported. Thus, upgrading of individual PSTN switches to include VOIP network connectivity can be delayed until the number of VOIP users justifies such an upgrade.
Additional features, embodiments and benefits of the invention will be apparent from the detailed description which follows.
The present invention is directed to methods and apparatus for migrating from the Public Switched Telephone Network (PSTN) to a Voice Over Internet Protocol (VOIP) network, while keeping the transition relatively transparent to end users. Various methods and apparatus of the invention are directed to allowing for a gradual transition of subscribers from the PSTN to VOIP environment, and to minimizing the need to upgrade and/or replace PSTN hardware, e.g., telephone switches, during the transition process.
The PSTN 102 comprises a plurality of telephone switches 116, 118, 120, coupled together as shown in
In addition to conventional switches 116, 118, 120 the PSTN 102 includes, a set of control and signaling connections 114 including one or more signal transfer points (STPs) 150. The connections 114 allow the various elements of the PSTN to exchange call control related messages and data.
The PSTN further includes one or more intelligent peripherals (IPs) 124, a service control point (SCP) 126 and an integrated service control point (ISCP) 128. Intelligent peripherals 124 are used to provide various services to callers including the playing of message prompts, speech recognition, and the collection of information, e.g., digits, from a caller in response to prompts. An SCP can instruct an SSP to connect a call to an IP and to have the IP play a message and/or collect information from the caller. Collected information may then be used to complete the call. SCP 126 and ISCP 128 serve the same general function in regard to responding to messages for call processing instructions. The ISCP includes an SCP in addition to various other components, e.g., AIN service setup and components. Accordingly, ISCPs provide greater functionality than SCPs. However, traditionally, SCPs 126 have been implemented with greater memory then ISCPs but this is not a requirement. The exemplary PSTN 102 includes SCPs 126 and ISCPs 128. However, the functions of these two elements could easily be combined into a single device 112. SCPs 126 because of their larger memory have often been used to provide LNP services. ISCPs 128, have been commonly used to provide a wide variety of Centrex services, call forwarding services, call screening services as well as other AIN based services.
For purposes of explaining the invention in later call flows, it will be assumed that SCP 126 is responsible for responding to messages resulting from activation of LNP triggers while ISCP 128 is responsible for responding to messages resulting from the activation of services to which individuals or corporate telephone users subscribe such as the aforementioned Centrex and call forwarding services.
In addition to the above discussed elements, the PSTN 102 includes an IP gateway switch 122. The IP gateway switch 122 couples the PSTN 102 to the VOIP network 104 and servers to interface between the PSTN and IP networks by performing any necessary signaling, packetization, and protocol conversions. IP gateway switch functionality can be incorporated into switches which also provide complete PSTN functionality. Such multiprotocol telephone switches may include links to both the PSTN 102 and VOIP network 104. Given the cost of telephone switches, it is desirable that the need to replace existing PSTN switches or to upgrade PSTN switches to include VOIP connection and functionality be limited until the demand for VOIP services at a given switch justifies the cost associated with such an upgrade. Thus, from a cost standpoint, during the initial transition to VOIP it is desirable to minimize the number of telephone switched required to have VOIP functionality and direct links to the VOIP network 104.
In accordance with one feature of the present invention, AIN LNP functionality is used to support the porting of telephone numbers from switches which do not have direct connections to the VOIP network to a switch, e.g., gateway switch 122, which does support VOIP functionality and has connections to the VOIP network 104. The switch to which the call is ported will then, in accordance with the present invention, service the call and perform billing operations as if the call were serviced by the switch from which the call was ported. In this manner, telephone customers can be provided with VOIP service from virtually any switch in the network without the need to replace or upgrade existing switches to interface directly with the VOIP network 104.
In accordance with the present invention, the SCP 126 includes a Local Number Portability (LNP) database 127 that includes a list of telephone numbers that have been ported from the PSTN 102 to a VOIP network 104, and the Local Routing Number (LRN) of the IP gateway switch assigned to service the particular ported number. LNP triggers are set on the ported lines at the switches 116, 118, 120 so that calls originating from the ported telephone lines or directed to the ported telephone lines will be re-routed via AIN LNP functionality to the assigned IP gateway switch.
The use of AIN LNP functionality to port VOIP calls to a non-local VOIP switch permits users to keep their existing telephone numbers while being ported from the PSTN to a VOIP network. The technique also allows users to continue to receive their existing PSTN based telephone services. In addition, from a cost standpoint has the significant advantage of allowing for a gradual transition from a PSTN to a VOIP network without requiring network wide hardware upgrades to the current switches.
The VOIP network 104, which is an IP based network, includes first and second soft switches 130, 154, first and second media/proxy servers 132, 156, an ENUM database 158. Soft switch 130 includes trunk call agent 136, and line call agent 138. VOIP network 104 may be implemented as part of the Internet, or as a part of a separate IP network which may or may not include links to the Internet. In the VOIP network 104, telephone calls comprise a stream of IP packets which may include call related data in addition to audio, e.g., voice, information. To complete a call in the IP network 104, IP packets are routed to from a calling party's IP telephony device, e.g., device 106, to the called party's IP telephony device, e.g., IP telephone 154.
Soft switches 130 include routing information and other control information associated with providing VOIP service, e.g., telephone service, to VOIP service customers, e.g., customers represented by VOIP telephone devices 106, 154. Depending on the implementation, the control and/or routing information and function may be implemented in the soft switch using one or more devices such as a trunk call agent 136 and a line call agent 138. The trunk call agent 136 includes control and routing information associated with various call trunks while the line call agent 138 includes routing and service information associated with individual user lines, e.g. telephones 106, for which soft switch 130 is responsible for, e.g., routing and billing functions. Media/proxy servers 132, 156 interact with the soft switches 130 and route IP telephone calls under direction of the soft switches 130, 152. Thus, IP calls and/or call related data are transmitted through these servers to their respective destinations. Soft switches 130, 152 provide calling and called information to the servers, then the servers determine routing and move the call to its ultimate destination, e.g., they determine the routing instructions for called numbers.
IP telephone calls can be routed under the direction of soft switches 130, 152 to the PSTN via the IP gateway switch 122 which interconnects the VOIP network 104 and PSTN 102. Similarly, soft switches can control the routing of calls received from the PSTN 102 via IP gateway switch 122 so that they are properly routed to an IP telephony device 106, 154. Thus, it is possible for calls to pass between the PSTN and IP domains with soft switches controlling call routing in the VOIP environment and PSTN switches controlling routing in the PSTN domain.
With regard to IP based telephony users, customer information may be stored in the VOIP network, e.g., at the soft switches 130 or in databases accessible to the soft switches 130 or via media/proxy servers 132, 156. Such information may include call screening information, call forwarding information, telephony device status information, customer name/address information and a wide variety of other types of information such as bandwidth capability. Such information can be useful in a wide variety of telephone call situations and, in many cases, can be used to determine whether a call directed to a VOIP telephone number can be successfully completed to the called number, will be redirected to another number (which may be a PSTN based telephone number) and/or if the call will not be able to be completed, e.g., because the called party's telephony device is not active or because the called party is unable to support the bandwidth required to accept the incoming call.
In accordance with various features of the present invention, as will be discussed below, prior to routing a call from the PSTN 102 to the VOIP network 104, information corresponding to a VOIP subscriber is accessed from the PSTN prior to the call being routed to the VOIP network 104. In this manner, the routing of calls from the PSTN to the VOIP network for calls which can not be completed, e.g., due to the called party's telephony device being inactive or because of called party call screening settings, is reduced or avoided. In addition, calls which would result in the call being redirected, e.g., forwarded, to a telephone number corresponding to the PSTN 102, can be routed in the PSTN domain without having to route the call to the VOIP network and then back to the PSTN 102 for call completion.
In accordance with the present invention, VOIP customer information may be accessed from the PSTN 102 in one of two ways. The first way of obtaining VOIP information involves the use of, Session Initiation Protocol, (SIP), to retrieve the desired information from the VOIP network 104. In the
The ENUM database can be used to facilitate users moving from location to location since such users can update the information in the ENUM database with a temporary IP address so that calls are directed to the user's current location at any given time.
In response to entry of a telephone number, the DNS returns information from an ENUM database. The ENUM database includes IP telephony information associated with a particular number. The telephone number associated information may include, e.g., IP address information to be used when routing IP calls to the entered telephone number, an E-mail address, and other information relating to or associated with the telephone number or service subscriber assigned to use the telephone number. Some of the information obtained using ENUM may be the same as, or similar to, information which could be obtained using SIP. However, SIP currently provides for a broader range of information to be stored and returned than does ENUM. Accordingly, while some embodiments involve the use of ENUM or SIP, other embodiments of the invention involve the use of both SIP and ENUM. In this manner, more information may be obtained than when only one of the two protocols is used to retrieve information associated with a telephone number.
The SIP and ENUM databases may include telephone number and other information corresponding to multiple parties, i.e., IP telephone device users.
A plurality of scenarios arises when migrating from a PSTN 102 to a VOIP network 104.
The top row in each of
While the IP gateway switch 122 is shown as an element of the PSTN domain, it is to be understood that this network element 122 bridges the two domains and therefore, arguable belongs at least in part, in each of the PSTN and VOIP domains.
In the figures, the term calling party is used to identify the device 110 (and thus party) from which an exemplary call originates. The originating SSP 116 is the exemplary local SSP to which the calling party's telephone line is connected. The LNP SCP 126 is the SCP which is used to respond to activation of LNP triggers and includes the LNP database 127. The Centrex (CTX) SSP 120 is the exemplary SSP which provides Centrex services to a telephone device coupled there to via a telephone line for which Centrex services are being provided. The term CTX line is used to indicate the device or line associated with a Centrex service subscriber which receives service from the CTX SSP 120. The term AIN ISCP 128 is used to identify the ISCP 128, which for purposes of explaining the invention, is used to provide AIN services, including e.g., call forwarding and AIN based Centrex services. Thus, for purposes of the examples discussed in
Solid arrows are used in
The exemplary call begins in step 202 with the calling party 110 dialing a phone number, e.g., 301-774-4244, corresponding to, e.g., the called party using IP telephone device 106. In step 204 the call initiated in step 202 is transmitted to originating switch 116 which is connected to the calling party's customer premises.
In step 206, an LNP trigger set using digits of the called party's telephone number as part of the telephone number porting process of the invention is activated and the call processing is paused. In step 208, a call processing message, e.g., a TCAP message, is sent to Service Control Point (SCP) 126 in order to obtain call processing instructions. In response to the call processing message received in response to activation of the LNP trigger, the SCP 126 retrieves the Local Routing Number (LRN) associated in the LNP database 127 with the called telephone number. This may be done by accessing the database 127 using the called telephone number as an index thereto.
In addition, in step 210 the SCP 126 generates a call control message, e.g., a TCAP response message with the retrieved LRN, e.g., 301-520-6607, of the IP gateway switch 122. This LRN is placed in the called party field and the original called party's telephone number, e.g., 301-774-4244, in a spare field of the call control message. In step 212, the call control message, which includes the LRN, is returned to the originating switch 116. In step 214, the originating switch receives the response message and resumes call processing. Then, in step 216, the switch 116 routes the call using the number in the called party field, which is now the LRN of the gateway switch 122.
In step 218, IP gateway switch 122 recognizes the incoming call as being directed to its own LRN number used for receiving LNP forwarded calls. In response to detecting the LRN in the called party field, the switch 122 retrieves the real called party number from the spare field and then proceeds to process the call using the real called party number. As a result of the use of the real called party number, in step 218, one or more AIN triggers set on the called party's line may be activated. This is because the called party may subscribe to one or more AIN services, e.g., call forwarding services. These AIN services may be identical to AIN services which the called party was receiving prior to having his/her telephone number and service ported to the VOIP network 104. In such a case, an AIN terminating attempt trigger (TAT) or other AIN trigger would be set on the called party's line at the IP gateway switch 122. The flow diagram of
As a result of activating the AIN trigger set on the called party's line, the IP gateway switch 122 pauses the call and generates a call processing message. In step 220, the switch 122 sends the call processing message to the ISCP 128 used to provide the called party with the AIN based services to which he or she subscribes. In response to the call processing message, in step 222 the ISCP 128 performs the functions associated with the AIN services to which the called party subscribes. This may include call screening and/or AIN based services such as call forwarding. As part of the call processing performed in step 222, the ISCP will access the appropriate CPR, e.g., the CPR corresponding to the called party and determine what further call processing, if any, should be performed. In this manner, the called party whose telephone number has been ported to the IP domain, can receive the same type of AIN services, e.g., call screening services, etc., as telephone service subscribers who have remained in the PSTN domain. In fact, if the called party was receiving AIN services prior to the number being ported to the VOIP domain, the called party can continue to receive those very same AIN services.
The exemplary call flow diagram of
In step 224, a call control message is returned to the IP gateway switch 122 which instructs the switch to complete the call to the called party number. In step 226, the IP gateway switch 122 determines that the called party number is in the VOIP domain and forwards the call to the soft switch 130, e.g., via a telephone trunk which connects the gateway switch 122 to the softswitch 130.
In step 230, the soft switch 130 looks at the called party number and proceeds to determine the IP address corresponding to the called party number to which the call should be routed. At this point the soft switch 130 can use a plurality of methods to determine the IP address to which the call is to be routed based on the called number 106. One method for determining the IP address is to consult proxy server functionality supported by media/proxy server 132.
In one embodiment of the present invention, the media/proxy servers include a database used for correlating phone numbers with IP addresses. In such embodiment in step 230 the trunk call agent 136 transmits a query to the proxy server functionality included in server 132 to determine the IP addressed to be used to route the call.
With the IP address of the called party determined, in step 232, the soft switch packetizes the call (voice and data portions) into IP packets with the necessary formatting and heading information added. In addition to packetizing the call, the soft switch instructs the proxy sever 132 to route the call using the called party's IP address. In step 236, the call, in the form of a plurality of IP packets, is directed to the called party's IP telephone 106 by the proxy server 132.
From the call flow of
In various embodiments, the LNP call forwarding feature of the present invention is used in conjunction with various other features such as the use of information obtained using SIP and/or ENUM in processing various calls placed from a telephone 110 located in the PSTN domain 204. Additional examples of call flows in which LNP forwarding is used in accordance with the invention are shown in
The use of SIP in conjunction with the LNP features of the present invention will now be explained by way of the example illustrated in
As in the
Referring to the example of
In accordance with the invention a call processing record (CPR) associated with the called party number (a VOIP number), includes instructions to use SIP to obtain called party information from the VOIP network 104. For purposes of explanation, a CPR including such SIP instructions will be called a SIP CPR.
In response to the SIP message, in step 326 the media/proxy server 132 accesses and/otherwise compiles information on the called party's 106 number and/or information relating to the VOIP network as part of a SIP response.
SIP information, e.g., instructions and/or other information, which can be returned to the ISCP 128 may include, 1) an instruction to route the call to a different number within the PSTN, 2) an instruction to route the call to a different number within the VOIP network 104, 3) call screening information, e.g., information indicating that the called party a) only accepts calls from specific identified callers, b) only accepts calls in specific languages, e.g., English or Spanish, c) only accepts calls that do not exceed a specific data rate. Thus, SIP information can include routing information, bandwidth information, security/screening information, etc. In addition, SIP allows for a host of other types of restrictions and/or information to be conveyed to the ISCP 128 and used in accordance with the invention for call processing and route determination purposes.
The routing information, which can be obtained through the use of SIP, may include call forwarding information set by the called party, e.g., as part of a call forwarding service. The ISCP 128 can redirect the call using forwarding telephone number or other routing information, if any, received from the server 132. Bandwidth availability information can be used to indicate how much bandwidth is available to the called party for purposes of the incoming call. If insufficient bandwidth is available, the ISCP 128 may, in accordance with the present invention, instruct the gateway switch 122 to terminate the call without transferring it to VOIP network 104 for delivery. Security information may include, e.g., call screening information. If a call is to be blocked because of call screening settings, the gateway switch may be instructed by the ISCP 128 to terminate the call without forwarding it to the VOIP network 104. In cases where a call is terminated without it being forwarded to the VOIP network, the ISCP may instruct the SSP 122 to send the call to an IP and for the IP to play the calling party a message indicating the reason the call can not, or is not, being completed.
In step 328, the server 132 returns information relating to the called party to the ISCP 128. The returned information sent to the ISCP 128 by the media/proxy server 132 gives the VOIP network 104 more information that can be used to control how calls will be routed and/or terminated than is available directly from the PSTN 102.
In step 332, the ISCP 128 instructs the gateway switch 122 to complete the call to the call forwarding telephone number corresponding to device 154. If the call forwarding number corresponds to a PSTN telephone number, the call will be completed without being transmitted to the VOIP network 104 despite the fact that the original called party number was a VOIP network telephone number.
In step 334 the IP gateway switch 122 receives and processes the call completion information provided by ISCP 128. In response to receiving the call completion information from the ISCP 128, in step 336 the gateway switch 122 routes the call to the VOIP network 104 for routing to the VOIP device 154. Thus, in step 336, the call is routed to the VOIP network 104, and more specifically to soft switch 152, e.g., through media/proxy server 132.
In step 338, soft switch 152 receives the call and uses one of a plurality of techniques to identify routing instructions, e.g., an IP address. Then in step 340 the soft switch 152 transmits a query to server 156, i.e., the server responsible for servicing calls to user device 154. Next, in step 342 the server 156 receives the query and determines the IP address that correlates with the called number. In step 344 the determined IP address is transmitted to the soft switch 152. Then in step 346 the soft switch 152 forwards the IP address to first media/proxy server 132. In step 350, the call is completed to end user device 154 to which the called party indicated calls were to be forwarded to.
As in the
In step 426, the IP gateway switch 122 receives the call completion message. Then in step 428 the IP routes the call using the call forwarding number supplied by the ISCP 128 resulting in the call being directed to CTX SSP 120 which serves as the terminating switch for the CTX line corresponding to device 108. In step 430, switch 120 receives the forward call and completes, in step 432, the connection to device 108 to which the call was forwarded.
Thus, in accordance with the present invention, a subscriber to an AIN service, e.g., an AIN based Centrex service, can continue to receive AIN based telephone services despite having been ported to the VOIP network 104.
As discussed above, ENUM is a protocol which, like SIP can be used to provide information relating to an VOIP telephone customer's capabilities, preferences, call forwarding settings, etc. In accordance some embodiments of the present invention ENUM is used as an alternative to, or in conjunction with, SIP as a way for a PSTN based device, e.g., ISCP 128, to obtain called party information from the VOIP network 104. In accordance with the present invention, the called party information obtained using ENUM may be used to make call routing and call completion information the same way that called party information obtained using SIP can be used.
Much like the Internet's Domain Naming System (DNS), where domain names such as www.yahoo.com are stored with correlating IP addresses. In accordance with ENUM, telephone numbers are stored in an ENUM database 158 with correlating IP addresses and related information, e.g., E-mail addresses, call forwarding information, etc. The ENUM database 158 may be incorporated into the existing Internet DNS.
In step 524 the ISCP 128 uses a Get_Data function to establish a communication link to the ENUM database 158 in an attempt to retrieve called party information from the VOIP network 104. In step 526 the ENUM database 158 is accessed and called party information, e.g., IP address, is retrieved using the called party's telephone number as an index into the ENUM database 158. In step 528, the called party information which is retrieved using ENUM may be the same as or similar to the above discussed information which could be retrieved using SIP. In the
The call is then completed to the telephony device 154 to which the called party directed incoming calls to be forwarded to by performing steps 332 through 350 in the same manner as discussed previously in regard to the
In the above described manner ENUM can be used in accordance with the present invention as an alternative to SIP to retrieve called party information from the VOIP network 104.
The pervious call flow examples have all addressed processing a call from the PSTN directed to a telephone number which has been ported to the VOIP network. Exemplary processing of a call from a VOIP telephony device to a PSTN telephone number will now be discussed with reference to
There is a greater variety of AIN triggers which can be activated based on the information included in the called party information field of a call then there are types of triggers that are responsive to information included in the calling party field of a call. Accordingly, it is often easier to design and implement AIN based services using triggers that are responsive to information in the called party field than it is to implement services based on information present in the calling party information field of a call.
In accordance with one feature of the present invention, calling party information is inserted into the called party information field of calls directed to the gateway switch 122 from the VOIP network 104. This allows the use of AIN triggers responsive to information in a call's called party information field, to be triggered by calling party information, e.g., the calling party's telephone number.
The insertion of calling party information into the called party field of a call may be performed by the softswitch used to forward the call to the gateway switch 122. To preserve the called party information, the soft switch, in accordance with the invention places the actual called party number into a spare field, e.g., an alternate billing information field of the call. As will be discussed below, a service control point or other network device can be used to recover the called party information after activation of an AIN trigger based on the information included in the called party field.
Rather than have the softswitch insert the called party information into the called party field of a call, the portion of the IP gateway switch 122 which is responsible for interfacing between the IP and PSTN networks 104, may place the calling party information in the called party field and the called party information in a spare field prior to the call being processed by the AIN trigger functionality included in the gateway switch 122.
Thus, in accordance with the invention, at the point AIN triggers may be triggered in the gateway switch 122 by calls from the VOIP network, the information included in the called party field will be the calling party ID, e.g., calling party's telephone number. Meanwhile the called party number will be included in a spare field such as an alternate billing field.
Furthermore, in accordance with the present invention, the ISCP 128 includes or can access a VOIP telephone number information database, e.g., a database including a list of VOIP telephone numbers from which calls may originate from the VOIP network 104. Billing to the calling party for such calls may be performed in accordance with the invention by the IP gateway switch 122 or a remote switch, e.g., switch 120. Billing is performed by the gateway switch 122 when the calling party number is local to the switch 122, e.g., corresponds to a PSTN line which was local to the gateway switch 122 before being converted to a VOIP number.
Billing is performed by a remote switch, e.g., Centrex switch 122, when the remote switch was responsible for serving as the terminating switch for the calling party telephone number prior to it being converted to an VOIP number. For VOIP telephone numbers which are to be billed by switches which are remote from the gateway switch 122, the VOIP telephone number information database includes information identifying the remote switch which is to perform the billing for calls from the listed VOIP number, and code which is to be included in an AMA slip ID to insure that correct billing to the called party number by the remote switch will occur. Each switch logs billing information including AMAslpID's which include the telephone number to be billed and the billing code which determines the billing to be performed. By transmitting AMAslpIDs from the gateway switch to the remote switch which previously serviced the calling party before the number was ported to the VOIP network 104, the calling party can be billed as if the transition to the VOIP network did not occur and/or by the same switch which previously performed the billing but at a different rate.
For purposes of the example, the calling party's telephone number is (301-774-4244) while the called party's telephone number is 301-774-5200. For purposes of the example, the terminating switch for the exemplary called party has been selected to be CTX switch 120. This same switch also served the calling party before the calling party's telephone number was ported to the VOIP domain. Accordingly, CTX switch 120 will be used to perform calling party billing operations in accordance with the invention.
Gateway switch 122 serves as the link between the VOIP soft switch 130 and the CTX SSP 120 through which the called party in the PSTN 102 can be reached by the calling party in the IP network 104.
In step 606 the call is received at soft switch 130. Next, in step 608, the soft switch 130 sends a query to media/proxy server 132 seeking routing instructions for called number 301-774-5200.
In step 610, the media/proxy server 132 locates the called party's number in its database and finds that the number is a PSTN number. Since the number being called is in the PSTN 102, the proxy server will information the softswitch 132 to route the call to the local STP for SS-7 routing.
In step 612, the media/proxy server sends the routing information back to the soft switch 130 informing it to route the call to a local Signal Transfer Point (STP) 150 for SS7 routing. The soft switch 130 receives the instructions in step 614 and, in step 616, contacts its local media/proxy server 132 which has SS-7 connectivity. Next, in step 618, the media/proxy server 132 uses SS7 messaging to contact the local PSTN STP 150. In step 620, the STP 150 verifies that the requested call can be completed, e.g., the STP 150 checks to see if the called line is busy or if a no answer condition exists. If either of these conditions is detected by the STP 150, the STP 150 will inform the media/proxy server 132, and the calling party would hear a busy signal or a no answer condition indication under the direction of server 132 or softswitch 130.
In response to receiving an indication that the called party is available, the call is routed, in step 622 to the IP gateway switch 122 through media/proxy server 132. As part of this routing, the called party number is placed in a spare information field, e.g., alternate billing field and the calling party number is inserted into the called party field. This swapping of data in call information fields may be performed by the softswitch 130, server 132, or at the IP gateway switch 122 prior to the call being subject to AIN trigger processing.
In accordance with the present invention, an AIN Public Office Dialing Plan Trigger (PODP), which is a type of specific digit string (SDS) trigger, is set to be activated at the IP gateway switch 122 based on calling party numbers which may correspond to the VOIP domain. Thus, calls from the VOIP domain, received by the IP gateway switch, will cause an AIN trigger to be activated. For purposes of the example, the activated SDS trigger may be a six digit trigger set so that calls from a number starting with 301-774 will activate the trigger. The use of a six digit AIN trigger allows a single trigger to be used at the switch 122 for numerous telephone numbers. While some of the telephone numbers which activate the trigger may not be VOIP originating calls, it is often easier to have the SCP distinguish between VOIP and non-VOIP calls rather then set thousands of separate triggers on trunk lines, e.g., one per 10 digit VOIP calling party number.
In step 624 the IP gateway switch 122 receives the call originating from VOIP phone 106, the Specific Digit String (SDS) trigger is activated and call processing is paused. Next, in step 626 the IP gateway switch 122 sends a call processing message to the ISCP 128 seeking call processing instructions.
In step 628, the ISCP 128 scans the ten-digit phone number in the calling party field of the received TCAP message, e.g., 301-774-4244, and compares it to the telephone numbers in the VOIP information database. If the scanned calling party number is not a number that was ported to the VOIP network or a number originating from the VOIP network, it will not be listed in the VOIP number information database 129 in such a case, a continue instruction is returned to the switch 122 and the call is routed normally. Thus, telephone numbers which have not been ported to the VOIP network but which activate the trigger set at the gateway switch 122 will be completed in a manner that does not significantly interfere with call processing and is transparent to the called and calling parties.
However, in the
However, in the
In step 630, a call control information, correcting billing and including the correct called number in the called number field, is sent back to the IP gateway switch 122. In step 532, the IP gateway switch 122 resumes the call, and looks in the called party field for the called party's number to be used for routing purposes. The IP gateway switch 122 finds the correct called party number 301-774-5200 which was placed in the called party field by the SCP, and routes the call to switch 120 in step 534.
In step 636, the call is received at switch 120, where it incurs a TAT trigger since the called party is a Centrex subscriber. Call processing is paused and in step 638, a call processing message is sent to the ISCP 128. If a CPR associated with the called number, included special routing or an active service, the call would be routed or processed in according with the CPR instructions. In the
In step 646 the call processing instructions are received from the ISCP and, in the call is completed to the telephony device by the SSP 120 in step 648.
Using the above described methods and apparatus of the present invention telephone users can gradually be moved from the PSTN 102 to VOIP network 104 in a relatively transparent manner. Significantly, in accordance with the invention large companies with multiple phone lines can be allowed convert a few lines at a time to the VOIP network without the need to make significant upgrades to the existing PSTN switches serving as terminating switches for the lines being moved to the VOIP network.
Numerous variations on the above described methods and apparatus are possible without departing from the scope of the invention.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US6226289 *||29 Sep 1997||1 May 2001||Bell Canada||Method and apparatus for dynamically routing calls in an intelligent network|
|US6301350 *||30 Jun 1995||9 Oct 2001||Qwest Communications International, Inc.||System and method for call handling|
|US6430176 *||6 Nov 1998||6 Aug 2002||Nortel Networks Limited||Multimedia channel management through PSTN signaling|
|US6493444 *||16 Mar 1999||10 Dec 2002||Bell Canada||Enhanced application telephone network|
|US6614781 *||20 Nov 1998||2 Sep 2003||Level 3 Communications, Inc.||Voice over data telecommunications network architecture|
|US6631186 *||21 Nov 2000||7 Oct 2003||Sbc Technology Resources, Inc.||System and method for implementing and accessing call forwarding services|
|US6636596 *||24 Sep 1999||21 Oct 2003||Worldcom, Inc.||Method of and system for providing intelligent network control services in IP telephony|
|US6678265 *||30 Dec 1999||13 Jan 2004||At&T Corp.||Local number portability database for on-net IP call|
|US6724876 *||2 Mar 2001||20 Apr 2004||Revd Networks, Inc.||Method and apparatus for effecting telecommunications service features using call control information extracted from a bearer channel in a telecommunications network|
|US6735209 *||29 Jul 1999||11 May 2004||Worldcom, Inc.||Address definition for IP telephony services|
|US6735621 *||15 Aug 2000||11 May 2004||Nortel Networks Limited||Method and apparatus for messaging between disparate networks|
|US6741585 *||5 May 2000||25 May 2004||Lucent Technologies Inc.||Interworking of addressing in an internetwork|
|US6771639 *||10 Apr 2000||3 Aug 2004||Nortel Networks Limited||Providing announcement information in requests to establish interactive call sessions|
|US6819667 *||5 Aug 1999||16 Nov 2004||Lucent Technologies Inc.||PSTN-internet notification services|
|US6839421 *||29 Oct 2001||4 Jan 2005||Telefonaktiebolaget Lm Ericsson (Publ)||Method and apparatus to carry out resolution of entity identifier in circuit-switched networks by using a domain name system|
|US6909708 *||18 Nov 1996||21 Jun 2005||Mci Communications Corporation||System, method and article of manufacture for a communication system architecture including video conferencing|
|US6917612 *||11 May 2001||12 Jul 2005||Telefonaktiebolaged L M Ericsson||System and method for address resolution in internet protocol (IP)-based networks|
|US6937563 *||8 Mar 2001||30 Aug 2005||Nortel Networks Limited||Homing and controlling IP telephones|
|US6937597 *||26 Feb 1999||30 Aug 2005||Lucent Technologies Inc.||Signaling method for internet telephony|
|US6937713 *||30 Dec 1999||30 Aug 2005||At&T Corp.||IP call forward profile|
|US7035260 *||27 Aug 2001||25 Apr 2006||At&T Corp.||Voice over IP service implementation for providing multimedia features|
|US7035384 *||18 May 2000||25 Apr 2006||Convergys Cmg Utah, Inc.||Call processing system with call screening|
|US7054325 *||5 Oct 2000||30 May 2006||Agilent Technologies, Inc.||Correlation of signalling messages|
|US20030099341 *||28 Nov 2001||29 May 2003||Bell Canada||Method and system for providing access to a voice mail system|
|1||"Protocol Action: SIP: Session Initiation Protocol to Proposed Standard", dated Feb. 2, 1999, downloaded from http://www.cs.columbia.edu/sip/proposed.txt on Jan. 8, 2002, pp. 1-2.|
|2||Carolyn Duffy Marsan, Network World Fusion, dated Sep. 26, 2000 "Telecordia, VeriSign to marry telephone, Net numbers", downloaded from http://www.nwfusion.com/news/2000/0926telecordia.html on Jan. 8, 2002, pp. 1-4.|
|3||Carolyn Duffy Marsan, Network World, dated Sep. 24, 2001, Buzz 2001: "The Enum phenomenon", downloaded from http://www.nwfusion.com/buzz2001/enum on Dec. 24, 2001, pp. 1-6.|
|4||ENUM, "Welcome to ENUM.ORG", downloaded from http://www.enum.org. on Jan. 8, 2002, pp. 1-2.|
|5||M. Handley et al., Network Working Group, Category: Standards Track, "SIP: Session Initiation Protocol", downloaded from ftp://ftp.isi.edu/in-notes/rfc2543.txt on Jan. 8, 2002, pp. 1-134.|
|6||P. Faltstrom, Cisco Systems Inc., dated Sep. 2000, Category: Standards Track, "E.164 number and DNS", downloaded from ftp://ftp.isi.edu/in-notes/rfc2916.txt on Dec. 24, 2001, pp. 1-9.|
|7||TeleDNS, "Welcome to the teleDNS Project", downloaded from http://www.enumworld.com on Jan. 8, 2002, pp. 1-2.|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US7512151 *||17 Apr 2001||31 Mar 2009||Nokia Corporation||Providing a network node with service reference information|
|US7558254 *||10 Aug 2004||7 Jul 2009||Alcatel-Lucent Usa Inc.||Method and apparatus for call routing via gateway brokering|
|US7583659 *||27 Jul 2004||1 Sep 2009||Hitachi Communication Technologies, Ltd.||Media gateway and automatic telephone call redirecting service system|
|US7801289 *||20 May 2005||21 Sep 2010||At&T Intellectual Property I, L.P.||Voice-over network (VoN)/voice-over internet protocol (VoIP) architect using advance intelligent network alternatives|
|US7903640||24 Jun 2008||8 Mar 2011||At&T Intellectual Property I, Lp||System and method for voice over internet protocol using a standard telephone system|
|US8094812 *||28 Sep 2007||10 Jan 2012||Juniper Networks, Inc.||Updating stored passwords|
|US8126017 *||13 May 2005||28 Feb 2012||At&T Intellectual Property Ii, L.P.||Method for address translation in telecommunication features|
|US8493997||4 Nov 2008||23 Jul 2013||Nokia Corporation||Providing a network node with service reference information|
|US8660113 *||31 Dec 2006||25 Feb 2014||At&T Intellectual Property Ii, L.P.||Method and apparatus for providing enhanced services local routing|
|US8730951||1 Jun 2012||20 May 2014||At&T Intellectual Property I, Lp||Apparatus and methods for origination of voice and messaging communication in a network|
|US8976784||29 Nov 2012||10 Mar 2015||At&T Intellectual Property I, Lp||Method and apparatus for provisioning a scalable communications network|
|US9001999||6 Dec 2011||7 Apr 2015||Pulse Secure, Llc||Updating stored passwords|
|US9015327||11 Jun 2012||21 Apr 2015||At&T Intellectual Property I, Lp||Apparatus and methods for flexible communicatons in a network|
|US9049209 *||8 May 2007||2 Jun 2015||At&T Intellectual Property I, L.P.||Methods and apparatus to route a communication session in an internet protocol (IP) multimedia subsystem (IMS) network|
|US9071468||11 Sep 2012||30 Jun 2015||At&T Intellectual Property I, Lp||Apparatus and methods for a scalable communications network|
|US9231986||7 Apr 2014||5 Jan 2016||At&T Intellectual Property I, Lp||Apparatus and methods for origination of voice and messaging communication in a network|
|US9246807||4 Feb 2014||26 Jan 2016||At&T Intellectual Property Ii, L.P.||Method and apparatus for providing enhanced services local routing|
|US9294591||20 Mar 2015||22 Mar 2016||AT&T Intellectual Property I, IP||Apparatus and methods for flexible communications in a network|
|US9401913||17 Mar 2015||26 Jul 2016||Pulse Secure, Llc||Updating stored passwords|
|US9509729||27 Nov 2015||29 Nov 2016||At&T Intellectual Property I, L.P.||Apparatus and methods for origination of voice and messaging communication in a network|
|US9577978||27 Jan 2015||21 Feb 2017||At&T Intellectual Property I, L.P.||Method and apparatus for provisioning a scalable communications network|
|US9647980||7 Jun 2012||9 May 2017||At&T Intellectual Property I, L.P.||Apparatus and methods for a scalable communications network|
|US20030086410 *||17 Apr 2001||8 May 2003||Jari Eikkula||Providing a network node with service reference information|
|US20050141528 *||27 Jul 2004||30 Jun 2005||Hitachi Communication Technologies, Ltd.||Media gateway and automatic telephone call redirecting service system|
|US20050182781 *||5 Jun 2003||18 Aug 2005||Bertrand Bouvet||System for consulting and/or updating dns servers and/or ldap directories|
|US20050232243 *||20 May 2005||20 Oct 2005||Maria Adamczyk||Voice-over Network (VoN)/voice-Over Internet Protocol (VoIP) architect using advance intelligent network alternatives|
|US20060034270 *||10 Aug 2004||16 Feb 2006||Oliver Haase||Method and apparatus for call routing via gateway brokering|
|US20080260139 *||24 Jun 2008||23 Oct 2008||At & T Delaware Intellectual Property, Inc.||System and Method for Voice Over Internet Protocol Using a Standard Telephone System|
|US20080281975 *||8 May 2007||13 Nov 2008||Chaoxin Charles Qiu||Methods and apparatus to route a communication session in an internet protocol (ip) multimedia subsystem (ims) network|
|US20090059904 *||4 Nov 2008||5 Mar 2009||Nokia Corporation||Providing a network node with service reference information|
|U.S. Classification||370/352, 370/400, 370/252, 370/395.2|
|Cooperative Classification||H04L65/104, H04M3/42297, H04L61/157, H04L29/1216, H04M7/128, H04M2207/12|
|European Classification||H04M3/42N5, H04M7/12H16, H04L29/06M2N2S4|
|16 Jan 2002||AS||Assignment|
Owner name: VERIZON SERVICES CORP, MARYLAND
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:PERSHAN, BARRY PAUL;REEL/FRAME:012507/0669
Effective date: 20020115
|2 Mar 2011||FPAY||Fee payment|
Year of fee payment: 4
|28 Jul 2014||AS||Assignment|
Owner name: VERIZON PATENT AND LICENSING INC., NEW JERSEY
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:VERIZON SERVICES CORP.;REEL/FRAME:033428/0605
Effective date: 20140409
|18 Mar 2015||FPAY||Fee payment|
Year of fee payment: 8