US8600364B2 - Systems and methods for terminating telephony communications to mobile telephony devices - Google Patents
Systems and methods for terminating telephony communications to mobile telephony devices Download PDFInfo
- Publication number
- US8600364B2 US8600364B2 US13/334,849 US201113334849A US8600364B2 US 8600364 B2 US8600364 B2 US 8600364B2 US 201113334849 A US201113334849 A US 201113334849A US 8600364 B2 US8600364 B2 US 8600364B2
- Authority
- US
- United States
- Prior art keywords
- mobile telephony
- mobile
- native
- telephony device
- telephony
- Prior art date
- Legal status (The legal status 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 status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W64/00—Locating users or terminals or network equipment for network management purposes, e.g. mobility management
- H04W64/003—Locating users or terminals or network equipment for network management purposes, e.g. mobility management locating network equipment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/16—Communication-related supplementary services, e.g. call-transfer or call-hold
Definitions
- the invention is related to systems and methods for terminating telephony communications to a mobile telephony device. More specifically, the invention relates to systems and methods for terminating telephony communications to a mobile telephony device that is roaming out of its native service area.
- Mobile telephony devices such as cellular telephones and mobile computing devices with cellular telephony capabilities, are typically provided with service from a cellular service provider.
- the cellular service provider typically only provides service to its customers within a defined geographical area, often only within a single country. The area served by the provider is considered the “native” service area for customers who receive cellular telephone service from the provider.
- the customer's cellular telephone may be capable of receiving cellular service from a second “non-native” cellular service provider that provides coverage in that location.
- the non-native cellular service provider is not the customer's regular service provider, the customer will be charged special “roaming” fees for receiving incoming communications and for sending outgoing communications from that location.
- the non-native cellular service provider charges the user's native cellular service provider for providing service to the customer's cellular telephone, and the native cellular service provider then passes those charges along to the customer as part of his regular monthly bill. This is true for telephone calls, text messages, and other forms of telephony communications.
- Roaming charges can be exorbitant compared to fees charged for telephony communications within the customer's native service area. International roaming charges are particularly expensive, as the rates negotiated between carriers for overseas call termination has been at a premium.
- FIG. 1 is a system level representation of elements that interact with each other to terminate telephony communications to mobile telephony devices;
- FIG. 2 is a schematic diagram of a controller that may be used to practice one or more embodiments of the present invention
- FIG. 3 is a block diagram illustrating elements of a mobile roaming connection unit embodying the invention.
- FIG. 4 is a diagram illustrating steps of a method embodying the invention for registering a mobile telephony device with a mobile roaming termination service
- FIG. 5 is a diagram illustrating steps of a method embodying the inventor for implementing call forwarding instructions as part of a method of terminating telephony communications to mobile telephony devices;
- FIG. 6 is a diagram illustrating steps of a method embodying the inventor for triggering the implementation of call forwarding instructions as part of a method of terminating telephony communications to mobile telephony devices;
- FIG. 7 is a diagram illustrating steps of a method embodying the inventor for terminating telephony communications to a mobile telephony device.
- FIG. 8 is a diagram illustrating steps of another method embodying the inventor for terminating telephony communications to a mobile telephony device.
- This term encompass traditional cellular telephones, as well as mobile telephony devices that include additional functionality, such as the ability to wirelessly communicate digital data.
- mobile computing devices that include communications capabilities provided by either or both of a cellular transceiver and a wireless digital data transceiver. Examples of such devices include the Apple iPhoneTM, mobile telephony devices running the AndroidTM operating system, the BlackberryTM and mobile telephones running the Symbian operating system.
- the following description also refers to terminating a telephony communication.
- This phrase refers to completing an incoming telephony communication, such as a voice or video telephone call, to a telephony device.
- This phrase also encompasses delivering text messages and other forms of text-based or video-based messaging to a telephony device.
- This phrase also encompasses other forms of communications that may be carried over a telephony network.
- call or “telephone call” is used in the following description for ease of reference, clarity and brevity. However, all of the systems and methods described below which involve handling, routing and terminating calls would also apply to systems and methods of handling, routing and terminating other forms of telephony-based communications. Thus, the terms call and telephone call are intended to include other forms of telephony-based communications.
- the invention provides a method, system and apparatus for terminating a telephony communication to a mobile telephony device that is roaming in such a way that roaming charges preferably are not incurred.
- the telephony communication is routed through an Internet Protocol (IP) telephony system which is capable of terminating the telephony communication to the mobile telephony device in ways that do not incur roaming charges.
- IP Internet Protocol
- the IP telephony system might deliberately cause the telephony communication to be terminated to the mobile telephony device through a non-native mobile telephony service provider. While this would result in the user incurring roaming charges, terminating the telephony communication in this fashion may be the only way to reach the user.
- telephony communications are effected over a packet-based data network.
- Signaling that is conducted in the packet-based data network is preferably executed using Session Initiation Protocol (SIP).
- SIP Session Initiation Protocol
- IP Internet Protocol
- VOIP Voice Over Internet Protocol
- the details and functionality of SIP can be found in the Internet Engineering Task Force (IETF) Request for Comments (RFC) Paper No. 3261 entitled, “SIP: Session Initiation Protocol” herein incorporated in its entirety by reference.
- SIP establishes and negotiates a session, including the modification or termination of a session. It uses a location-independent address system feature in which called parties can be reached based on a party's name. SIP supports name mapping and redirection, allowing users to initiate and receive communications from any location. Of course, while SIP is a preferred protocol for establishing communications over a data network, other signaling protocols could also be used to perform the invention.
- FIG. 1 depicts various elements that may be involved in terminating telephony communications to a mobile telephony device.
- the elements in FIG. 1 include a subscriber mobile telephony device 112 .
- the subscriber mobile telephony device 112 may have a native ability to handle voice over Internet protocol telephony communications sent via a data channel.
- an application running on the subscriber mobile telephony device 112 may provide the capability of handling voice over Internet protocol telephony communications sent via a data channel.
- Mobile telephony service provider A 114 is located in country 1 and provides telephony service to mobile telephony devices located in country 1 .
- Mobile telephony service provider A 114 could be, for example, a cellular telephone network.
- mobile telephony service provider A 114 is the native mobile telephony service provider that provides service to the subscriber mobile telephony device 112 .
- FIG. 1 also depicts a traditional publically switched telephone network (PSTN) 130 .
- PSTN publically switched telephone network
- An analog telephone 132 can utilize the PSTN 130 to place and receive calls.
- the analog telephone 132 could call the subscriber mobile telephony device 112 , and the call would be routed through the PSTN 130 , then through mobile telephony service provider B 140 to the subscriber mobile telephony device 112 .
- FIG. 1 also depicts a cellular telephone 110 that is provided with service by mobile telephony service provider A 114 .
- the cellular telephone 110 could call the subscriber mobile telephony device 112 through mobile telephony service provider B 140 .
- FIG. 1 further depicts an IP telephony device 111 that maintains a data connection to a packet network, such as the Internet 116 .
- the IP telephony device 111 is provided with telephony service by an IP telephony system 124 which is also connected to the Internet 116 . If the user of the IP telephony device 111 wishes to establish a call with the subscriber mobile telephony device 112 , the IP telephony device 111 sends a call setup request to the IP telephony system 124 via the Internet 116 .
- the IP telephony system 124 then routes the call through mobile telephony service provider B 140 to the subscriber mobile telephony device 112 .
- FIG. 1 also depicts that the IP telephony system 124 may use gateways 120 A, 120 B to communicate with the PSTN 130 , mobile telephony service provider A 114 , as well as other telephony service providers.
- FIG. 1 further depicts that mobile telephony service provider B 140 is located in country 2 and provides service to mobile telephony devices located in country 2 .
- Mobile telephony service provider B 140 could also be a cellular service provider.
- FIG. 1 illustrates that the subscriber mobile telephony device 112 is located in country 2 , and it is capable of wirelessly accessing the Internet 116 via a wireless interface 118 .
- the wireless interface 118 could be a wireless router operating under the WiFi or WiMax standards, or any other type of wireless interface device that is capable of communicating with the subscriber mobile telephony device 112 and the Internet 116 .
- the subscriber mobile telephony device 112 could establish a data link to the Internet, or to some other data network, in other ways.
- the subscriber mobile telephony device 112 could communicate through a wireless Local Area Network (LAN), a Wide Area Network (WAN) gateway, a hardwired Internet connection and the like.
- LAN Local Area Network
- WAN Wide Area Network
- the subscriber mobile telephony device 112 is capable of sending and receiving data communications through the wireless interface 118 , the subscriber mobile telephony device 112 is also capable of establishing a data channel through a mobile telephony service provider. The data channel would be separate from a channel used for audio communications. Thus, the subscriber mobile telephony device 112 is capable of sending and receiving data communications via two independent pathways.
- mobile telephony service provider A 114 located in country 1 , is the native service provider for the subscriber mobile telephony device 112 .
- the subscriber mobile telephony device 112 When located in country 2 , the subscriber mobile telephony device 112 only has access to mobile telephony service provider B 140 to send and receive telephony communications. This results in the subscriber incurring roaming charges.
- elements of the IP telephony system 124 are capable of terminating telephony communications to the subscriber mobile telephony device 112 via a data connection passing over the Internet 116 .
- the IP telephony system 124 may also be capable of terminating telephony communications to the subscriber mobile telephony device 112 via a data connection passing over a data channel provided by mobile telephony service provider B 140 . So long as the cost of obtaining that data connection is lower than the cost of receiving a telephone call via mobile telephony service provider B 140 over a mobile voice channel, this may be a preferred way of terminating the telephony communication to the subscriber mobile telephony device 112 .
- FIG. 2 illustrates elements of a computer processor 250 that can be used as part of the system operated by the IP telephony service provider 124 to accomplish various functions.
- the IP telephony service provider 124 could utilize multiple processors 250 located at various locations, along with their operating components and programming, each carrying out a specific or dedicated portion of the functions performed by the IP telephony service provider 124 .
- the processor 250 shown in FIG. 2 may be one of any form of a general purpose computer processor used in operating an IP based communication system.
- the processor 250 comprises a central processing unit (CPU) 252 , a memory 254 , and support circuits 256 for the CPU 252 .
- the processor 250 also includes provisions 258 / 260 for connecting the processor 250 to customer equipment via one or more access point, such as the packet network 116 , gateways 120 A, 1208 and a data channel provided by a cellular service provider, as well as possibly one or more input/output devices (not shown) for accessing the processor and/or performing ancillary or administrative functions related thereto.
- the provisions 258 / 260 are shown as separate bus structures in FIG. 2 ; however, they may alternately be a single bus structure without degrading or otherwise changing the intended operability of the processor 250 .
- processor 250 that assists in execution and is otherwise part of the subject invention is found within one or more of the mobile telephony devices.
- Such devices are sufficiently advanced beyond early generation cellular telephones that they contain processors capable of running operating systems developed by device manufactures, as well as third party applications that are downloaded and installed by users to performing a myriad of communications and non-communications oriented tasks.
- the memory 254 is coupled to the CPU 252 .
- the memory 254 or computer-readable medium, may be one or more of readily available memory such as random access memory (RAM), read only memory (ROM), floppy disk, hard disk, flash memory or any other form of digital storage, local or remote, and is preferably of non-volatile nature.
- the support circuits 256 are coupled to the CPU 252 for supporting the processor in a conventional manner. These circuits include cache, power supplies, clock circuits, input/output circuitry and subsystems, and the like.
- a software routine 262 when executed by the CPU 252 , causes the processor 250 to perform processes of the disclosed embodiments, and is generally stored in the memory 254 .
- the software routine 262 may also be stored and/or executed by a second CPU (not shown) that is remotely located from the hardware being controlled by the CPU 252 .
- the software routines could also be stored remotely from the CPU.
- the software could be resident on servers and memory devices that are located remotely from the CPU, but which are accessible to the CPU via a data network connection.
- the software routine 262 when executed by the CPU 252 , transforms the general purpose computer into a specific purpose computer that performs one or more functions of the IP telephony system 124 .
- the processes of the disclosed embodiments may be discussed as being implemented as a software routine, some of the method steps that are disclosed therein may be performed in hardware as well as by a processor running software. As such, the embodiments may be implemented in software as executed upon a computer system, in hardware as an application specific integrated circuit or other type of hardware implementation, or a combination of software and hardware.
- the software routine 262 of the disclosed embodiments is capable of being executed on any computer operating system, and is capable of being performed using any CPU architecture.
- the IP telephony system 124 includes a mobile roaming connection unit 300 , as illustrated in FIG. 3 .
- the mobile roaming connection unit 300 includes a registration unit 302 , a triggering unit 304 , a forwarding instruction unit 306 and a call termination unit 308 . These elements act together to register a mobile telephony device with a mobile roaming termination service provided by the IP telephony system 124 . These elements also act to determine when the service should be activated or deactivated, and to route telephony communications to registered mobile telephony devices when they are roaming out of their native service area. Whenever possible, the mobile roaming connection unit 300 terminates telephony communications to a roaming mobile telephony device in a manner that does not result in the user incurring roaming charges.
- the subscriber mobile telephony device 112 may deliberately choose to register itself with the mobile roaming connection unit 300 when it is within its native service area, and when a cellular channel to mobile telephony service provider A 114 is available. This might allow the subscriber mobile telephony device to receive incoming calls without using up minutes of a calling plan. In this instance, the subscriber might configure his subscriber device 112 such that whenever the subscriber device 112 detects the availability of a data network connection, such as a wireless router 118 connected to the Internet 116 , use of the system and methods described above are automatically initiated.
- a data network connection such as a wireless router 118 connected to the Internet 116
- the registration unit 302 will act to register individual mobile telephony devices with the mobile roaming termination service. Typically a subscriber will already have an existing account with the IP telephony system 124 . However, in some instances, a subscriber could register for the mobile roaming termination service as its only service from the IP telephony system 124 .
- FIG. 4 illustrates steps of a method of registering a mobile telephony device with the mobile roaming termination service.
- the registration unit 302 obtains the native telephone number associated with the subscriber mobile telephony device 112 .
- This native telephone number may have been assigned by mobile telephony service provider A 114 , or by some other mobile telephony service provider.
- the registration unit 300 then creates a new entry in a registration database for the subscriber mobile telephony device 112 that includes the native telephone number.
- the registration unit 302 obtains an identifier associated with the subscriber mobile telephony device 112 from mobile telephony service provider A 114 .
- the identifier is an international mobile subscriber identity (IMSI) number.
- IMSI international mobile subscriber identity
- the IMSI number is a unique identifier associated with all GSM and UMTS network mobile telephone users and conforms to the ITU E.212 numbering standard.
- the IMSI number is actually associated with the SIM card present in the subscriber mobile telephony device 112 , and it would be contained in a home location register that is maintained by mobile telephony service provider A 114 .
- the IMSI number is often required to be used in certain communications with a mobile telephony service provider when the mobile service provider is being asked to take certain actions with respect to a mobile telephony device.
- the registration unit 302 stores the IMSI number in the record established for the subscriber mobile telephony device 112 in the registration database.
- the mobile roaming connection unit 300 will have the information it requires to cause telephony communications directed to the regular native telephone number associated with the subscriber mobile telephony device 112 to be re-directed to the IP telephony system 124 .
- This is accomplished by instructing mobile telephony service provider A 114 to forward calls directed to the native telephone number associated with the subscriber mobile telephony device 112 to a new access number that is maintained by the IP telephony system 124 .
- call forwarding instructions have been implemented, all calls placed to the subscriber mobile telephony device 112 will instead be received by the IP telephony system 124 . In some embodiments, this would be accomplished using the RTP and SIP protocols.
- the IP telephony system 124 can then terminate the call to the subscriber mobile telephony device 112 in a fashion that will not incur roaming charges.
- FIG. 5 illustrates steps of a method that would be performed by the mobile roaming connection unit 300 to cause the implementation of call forwarding instructions.
- the method starts in step S 502 when the triggering unit 304 of the mobile roaming connection unit 300 decides that forwarding instructions should be issued.
- the triggering unit 304 determines that it is appropriate to implement call forwarding instructions in response to a variety of different conditions, as will be described in more detail below.
- the forwarding instruction unit 306 assigns a forwarding access telephone number.
- the forwarding access telephone number is stored in a registration database maintained by the IP telephony system 124 against the native telephone number and IMSI number of the subscriber mobile telephony device 112 .
- the forwarding instruction unit 306 issues call forwarding instructions to mobile telephony service provider A 114 to cause mobile telephony service provider A 114 to forward all calls made to the native telephone number of the subscriber mobile telephony device 112 to the assigned forwarding access number.
- the IMSI number for the subscriber mobile telephony device 112 must be used in the communications with mobile telephony service provider A 114 to cause the implementation of the call forwarding instructions.
- the forwarding access telephone number is controlled by the IP telephony system 124 .
- any calls made to the native telephone number of the subscriber mobile telephony device 112 are received by the IP telephony system 124 .
- the IP telephony system 124 consults the registration database to determine which subscriber mobile telephony device is associated with that forwarding access telephone number. In this fashion, the IP telephony system 124 knows which mobile telephony device the caller is trying to reach.
- the subscriber mobile telephony device 112 registers itself with the mobile roaming connection unit 300 via communications that pass over a data network. Those communications could be sent to the mobile roaming connection unit 300 over the Internet, via a wireless interface 118 . Those communications could also pass over a data channel of a cellular connection. Regardless, the subscriber mobile telephony device 112 would contact the mobile roaming connection unit 300 and provide information, such as an IP address and a port number, that allows the mobile roaming connection unit 300 to contact the subscriber mobile telephony device 112 and establish a voice over Internet protocol link with the subscriber mobile telephony device 112 . This information would also be stored in the registration database against the other information being maintained for the subscriber mobile telephony device 112 .
- the mobile roaming connection unit 300 can route incoming calls to the subscriber mobile telephony device 112 through a data network.
- the mobile roaming connection unit 300 establishes a VOIP call with the subscriber mobile telephony device 112 , and that call is then connected to the inbound call forwarded from mobile telephony service provider A 114 .
- the incoming call is routed through the data network, rather than through non-native mobile telephony service provider B 140 , no roaming charges will be incurred by the user.
- the user may have to pay to obtain access to the data network. But in many instances, the cost of accessing the data network will be lower than the cost of roaming charges that would otherwise be incurred.
- the subscriber mobile telephony device 112 uses a wireless access point, such as a WiFi router, to obtain access to the data network, the charges for such access would likely be far lower than the cost of roaming charges. Even when the subscriber mobile telephony device 112 uses a cellular data channel to obtain access to a data network, the user would likely incur lower charges for data access than the cost of typical roaming charges.
- this event may trigger the forwarding instruction unit 306 to issue call forwarding instructions to mobile telephony service provider A 114 .
- this event may trigger the forwarding instruction unit 306 to issue call forwarding instructions to mobile telephony service provider A 114 .
- a variety of other triggering events might also cause the forwarding instruction unit 306 to issue call forwarding instructions.
- the triggering events that cause the implementation or cancellation of call forwarding instructions could be customized for an individual user or for an individual subscriber mobile telephony device.
- FIG. 6 illustrates steps of a method that results in call forwarding instructions being issued.
- the method starts in step S 602 when the triggering unit 304 of the mobile roaming connection unit 300 obtains information about the location of the subscriber mobile telephony device 112 . This could be accomplished by having the triggering unit 304 interrogate the subscriber mobile telephony device 112 to obtain location information. Alternatively, an application running on the subscriber mobile telephony device 112 may periodically report the position of the device to the triggering unit 304 .
- step S 604 the triggering unit 304 compares the location of the subscriber mobile telephony device 112 to the known native service area of the device to determine if the subscriber mobile telephony device 112 has roamed out of its native service area. If the subscriber mobile telephony device 112 is roaming, then in step S 606 , the triggering unit issues forwarding instructions to mobile telephony service provider A 114 to have calls placed to the native telephone number of the subscriber mobile telephony device 112 forwarded to a forwarding access number, as described above. A similar process would be used to cancel call forwarding instructions when the triggering unit 304 determines that the subscriber mobile telephony device has returned to its native service area.
- the triggering unit 304 of the mobile roaming connection unit 300 may monitor the movements of the subscriber mobile telephony device 112 over an extended period of time. If an analysis of the movements of the subscriber mobile telephony device indicate that the device travels outside its native service area according to a regular pattern, such as every Monday morning, and/or that the device travels back into its native service area according to a regular pattern, such as every Friday evening, then this pattern information may be used to trigger the implementation and cancellation of call forwarding instructions. Rather than waiting for the actual location of the subscriber mobile telephony device to be obtained or reported, forwarding instructions may be automatically implemented and canceled based on the predicted movements of the device.
- a regular pattern such as every Monday morning
- a regular pattern such as every Friday evening
- the forwarding instruction unit 306 acts to automatically implement and cancel call forwarding instructions based on the occurrence of an event, or based on a prediction.
- an application running on the subscriber mobile telephony device may itself automatically cause the implementation and cancellation of call forwarding instructions if the application detects that the device has moved out of or back into the user's native calling area.
- the application may also automatically cause the implementation and cancellation of call forwarding instructions when the application detects that the subscriber mobile telephony device 112 does not have a cellular connection to its native mobile telephony service provider A 114 .
- the application may automatically cause the implementation and cancellation of call forwarding instructions when the application detects that a data network connection is available.
- the user might take direct actions to cause the implementation and cancellation of call forwarding instructions.
- an application running on the subscriber mobile telephony device may provide a user with the ability to manually cause the implementation and cancellation of call forwarding instructions.
- the application may be directly communicating with the mobile telephony service provider, or the application may communicate with the mobile roaming connection unit 300 to request that it cause the implementation or cancellation of call forwarding instructions. If the application is directly interacting with the mobile telephony service provider, the application may contact the mobile roaming connection unit 300 via a data network connection to obtain a forwarding access number. Such communications would also inform the mobile roaming connection unit 300 that calls received on the forwarding access number should be terminated to the subscriber mobile telephony device 112 .
- all incoming telephony communications are forwarded to the IP telephony system 124 at all times. This would require that a dedicated forwarding access number be assigned to the subscriber mobile telephony device 112 , and call forwarding instructions would always be active.
- the mobile roaming connection unit 300 Each time that a call is received on the forwarding access number, the mobile roaming connection unit 300 checks the connection status of the subscriber mobile telephony device 112 to determine what type of access the subscriber mobile telephony device 112 has. The call is then terminated to the subscriber mobile telephony device 112 in the most appropriate manner. This could mean sending the call through a cellular service provider in a normal manner, or setting up a VOIP telephone link via a data network. If more than one connection method is possible, preference rules would determine how the call is connected.
- the incoming telephony communication could be sent to voicemail, or to some type of interactive voice response system. Alternatively, the incoming telephony communication could be forwarded to another subscriber device or telephone number.
- FIG. 7 illustrates steps of a control method embodying the invention which terminates incoming telephony communications to a subscriber mobile telephony device 112 via the most appropriate path.
- This method would be executed by the mobile roaming connection unit 300 of an IP telephony system 124 after call forwarding instructions have been implemented.
- the subscriber mobile telephony device 112 is located in country 2 (see FIG. 1 ), and the subscriber mobile telephony device is capable of receiving incoming telephony communications from mobile telephony service provider B 140 .
- the method begins in step S 702 when an incoming telephony communication is received on a forwarding access number that has been assigned for the subscriber mobile telephony device 112 .
- the call termination unit 308 of the mobile roaming connection unit 300 checks to determine if the subscriber mobile telephony device 112 is registered and reachable via a data network connection. If the subscriber mobile telephony device 112 is registered, in step S 706 the call termination unit 308 checks to determine the quality of the data connection.
- step S 708 a VOIP call is established between the IP telephony system 124 and the subscriber mobile telephony device 112 over the data network.
- the received telephony communication is then terminated to the subscriber mobile telephony device 112 through the VOIP call.
- step S 710 a check is made to determine if the user has authorized calls to be terminated to the subscriber mobile telephony device 112 through non-native mobile telephony service provider B 140 . This will likely result in roaming charges. However, the user may choose to accept the roaming charges if there is no other way of receiving an incoming telephony communication. In this scenario, the mobile roaming connection unit 300 first checks to see if it is possible to terminate the call through alternate means. But if no other means are available, the call is ultimately terminated through the non-native mobile telephony service provider B 140 , after call forwarding has been canceled.
- the result of the decision reached in step S 710 could be conditioned on various things. For instance, the user may have instructed that all calls be terminated through non-native mobile telephony service provider B 140 if no other method of terminating the call exists. In other instances, the user might specify that calls should only be terminated through a non-native telephony service provider if the call will cost less than a threshold amount to complete. In still other instances, the user might specify that only calls originating from a particular set of telephone numbers should be completed through a non-native mobile telephony service provider. This would allow the user to specify that certain important people be put through, but that other calls are not.
- step S 710 If the decision in step S 710 is that the call should not be terminated through a non-native mobile telephony service provider, then in step S 718 the call is terminated in some other fashion. As discussed above, this could include sending the call to voicemail, playing a recording to the caller that the called party is unavailable, forwarding the call to an alternate telephone number, or terminating the call in some other fashion.
- step S 710 If the decision in step S 710 is to terminate the call to the subscriber mobile telephony device 112 through non-native mobile telephony service provider B 140 , in step S 712 the forwarding instruction unit 306 contacts mobile telephony service provider A 114 and cancels the call forwarding instructions. The call termination unit 308 then sends the call to the regular native telephone number of the subscriber mobile telephony device 112 in step S 714 . This will cause mobile telephony service provider A 114 to send the call on to mobile telephony service provider B 140 , which ultimately completes the call to the subscriber mobile telephony device 112 .
- the mobile roaming connection unit 300 is able to monitor the status of the call. Once the call is completed, the method proceeds to step S 716 , where the call forwarding instructions are re-implemented. This ensures that further calls directed to the subscriber mobile telephony device 112 will be forwarded to the IP telephony system 124 .
- step S 720 a check is made to determine if it is acceptable to terminate the communication through the non-native mobile telephony service provider B 140 . If the system determines that the call should not be terminated through non-native mobile telephony service provider B 140 , then in step S 728 the call would be terminated in some other fashion.
- step S 722 the forwarding instruction unit 306 contacts mobile telephony service provider A 114 and cancels the call forwarding instructions.
- the call termination unit 308 then sends the call to the regular native telephone number of the subscriber mobile telephony device 112 in step S 724 . This will cause mobile telephony service provider A 114 to send the call on to mobile telephony service provider B 140 , which ultimately completes the call to the subscriber mobile telephony device 112 .
- step S 726 the call forwarding instructions are re-implemented.
- FIG. 8 illustrates steps of another method embodying the invention. This method results in a telephony communication being terminated to a subscriber mobile telephony device 112 that is roaming. The call is completed through the non-native mobile telephony service provider B 140 . However, the call is completed in a fashion that will not result in roaming charges.
- the device When a mobile telephony device is located outside of its native calling area, the device will communicate with a non-native mobile telephony service provider. During an initial communication process, the non-native mobile telephony service provider will recognize that the mobile telephony device is a non-native device. As a result, the non-native mobile telephony service provider will assign a temporary local access telephone number the device. The temporary number is often known as a mobile subscriber roaming number (MSRN). The non-native mobile telephony service provider then communicates with the user's native mobile telephony service provider and informs the native mobile telephony service provider of the assigned local access telephone number. This can be accomplished using a MAP Update Location Message.
- MSRN mobile subscriber roaming number
- the native mobile telephony service provider stores the temporary local access telephone number in a home location register that it maintains.
- the native mobile telephony service provider can obtain the temporary local access telephone number using a MAP Provide Roaming Number message.
- the native mobile telephony service provider forwards the call to the temporary local access telephone number. This will route the call to the non-native mobile telephony service provider, which then completes the call to the subscriber's mobile telephony device.
- the local access number assigned to the subscriber mobile telephony device 112 by the non-native mobile telephony service provider B 140 is stored in the home location register of the native mobile telephony service provider A 114 , this information may be available to the IP telephony system 124 .
- the subscriber mobile telephony device 112 is roaming in country 2 , and mobile telephony service provider B 140 has assigned a local access number to the subscriber mobile telephony device 112 .
- the mobile roaming connection unit 300 has obtained the local access number from the native mobile telephony service provider 114 .
- forwarding instructions for the subscriber mobile telephony device have been implemented.
- step S 802 when an incoming telephony communication directed to the subscriber mobile telephony device 112 is received by the IP telephony system 124 .
- step S 804 a check is performed to determine if the subscriber mobile telephony device 112 is registered with the mobile roaming connection unit 300 and available over a data connection. If so, then in step S 806 the call is completed to the subscriber mobile telephony device 112 over the data connection.
- step S 810 a check is performed to determine if the mobile roaming connection unit 300 has the local access number assigned by the non-native mobile telephony service provider B 140 . If the local access number is available, in step S 812 the mobile roaming connection unit 300 routes the call over a data network to a gateway located in country 2 . The gateway in country 2 then contacts and hands the call off to the non-native mobile telephony service provider B 140 . The non-native mobile telephony service provider B 140 then completes the call to the subscriber mobile telephony device 112 .
- the IP telephony system 124 already has multiple agreements in place with mobile telephony service providers in multiple countries. Those agreements allow the IP telephony system 124 to route calls over a data network to gateways located in various countries. Those gateways can then hand calls off to the mobile telephony service providers in those countries.
- the call can be completed for a considerably lower cost than if the call was handled in a traditional manner, and roaming charges were incurred.
- the user would likely have to pay a small charge to terminate the call in this fashion. But the charge would be less than the cost of the roaming charges.
- step S 814 a check is made to determine if it is acceptable to terminate the communication in the traditional manner through the non-native mobile telephony service provider B 140 . If the system determines that the call should not be terminated through the non-native mobile telephony service provider B 140 , then in step S 822 the call would be terminated in some other fashion.
- step S 814 If the decision in step S 814 is to terminate the call to the subscriber mobile telephony device 112 in the traditional manner through the non-native mobile telephony service provider B 140 , then in step S 816 the forwarding instruction unit 306 contacts mobile telephony service provider A 114 and cancels the call forwarding instructions.
- the call termination unit 308 then sends the call to the regular native telephone number of the subscriber mobile telephony device 112 in step S 818 . This will cause mobile telephony service provider A 114 to send the call on to mobile telephony service provider B 140 , which ultimately completes the call to the subscriber mobile telephony device 112 .
- step S 820 Once the call is completed, the method proceeds to step S 820 , where the call forwarding instructions are re-implemented.
- an enhanced security option is made available. That is, once a communication request is passed to the IP telephony system 124 , call signaling and media connections between the IP telephony system 124 and the subscriber mobile telephony device 112 may be encrypted to provide a secure communication session.
- the encryption techniques that are used could be RSA encryption, as described in PKCS#1 v2.1: RSA Cryptography Standard, RSA Laboratories, dated June 14, 2002, or AES encryption as described in Advanced Encryption Standard (AES), Federal Information Processing Standards Publication 197, dated November 26, 2001, or the techniques described in Secure Socket Layer (now Transport Layer Security) Protocol, Version 1.2 as described in IETF RFC 5246, dated August 2008, all of which are incorporated herein by reference.
- a call forwarding number is assigned by the mobile roaming connection unit 300 when call forwarding instructions are being implemented. This would likely result in different forwarding access telephone numbers being used for the same device at different times.
- the forwarding access telephone number could be a dedicated telephone number that is used only for a particular mobile telephony device.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims (30)
Priority Applications (17)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/334,849 US8600364B2 (en) | 2011-12-22 | 2011-12-22 | Systems and methods for terminating telephony communications to mobile telephony devices |
US13/492,361 US8744422B2 (en) | 2011-12-22 | 2012-06-08 | Systems and methods for terminating telephony communications to mobile telephony devices |
US13/562,542 US8989721B2 (en) | 2011-12-22 | 2012-07-31 | Systems and methods for terminating telephony communications to mobile telephony devices |
US13/568,416 US9020477B2 (en) | 2011-12-22 | 2012-08-07 | Systems and methods for terminating telephony communications to mobile telephony devices |
US13/569,384 US8862109B2 (en) | 2011-12-22 | 2012-08-08 | Systems and methods for terminating telephony communications to mobile telephony devices via a non-native telephony service provider |
US13/597,485 US9002335B2 (en) | 2011-12-22 | 2012-08-29 | Systems and methods for terminating telephony communications to mobile telephony devices |
US13/597,916 US8693994B2 (en) | 2011-12-22 | 2012-08-29 | Systems and methods for terminating telephony communications to mobile telephony devices |
US13/597,396 US9020478B2 (en) | 2011-12-22 | 2012-08-29 | Systems and methods for terminating telephony communications to mobile telephony devices |
US13/649,847 US8958785B2 (en) | 2011-12-22 | 2012-10-11 | Systems and methods for terminating telephony communications to mobile telephony devices |
US13/669,009 US8934882B2 (en) | 2011-12-22 | 2012-11-05 | Systems and methods for terminating telephony communications to mobile telephony devices |
US13/668,826 US9491600B2 (en) | 2011-12-22 | 2012-11-05 | Systems and methods for terminating telephony communications to mobile telephony devices |
US13/671,162 US9002336B2 (en) | 2011-12-22 | 2012-11-07 | Systems and methods for terminating telephony communications to mobile telephony devices |
US13/671,006 US8571060B2 (en) | 2011-12-22 | 2012-11-07 | Systems and methods for terminating telephony communications to mobile telephony devices |
US13/673,043 US8855612B2 (en) | 2011-12-22 | 2012-11-09 | Systems and methods of terminating telephony communications to mobile telephony devices |
PCT/US2012/071248 WO2013096768A2 (en) | 2011-12-22 | 2012-12-21 | Systems and methods for terminating telephony communications to mobile telephony devices |
CA2873603A CA2873603A1 (en) | 2011-12-22 | 2012-12-21 | Systems and methods for terminating telephony communications to mobile telephony devices |
EP12812490.6A EP2865207A2 (en) | 2011-12-22 | 2012-12-21 | Methods, apparatuses and computer readable media for terminating telephony communications to mobile telephony devices making use of a mobile roaming termination service |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/334,849 US8600364B2 (en) | 2011-12-22 | 2011-12-22 | Systems and methods for terminating telephony communications to mobile telephony devices |
Related Child Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/492,361 Continuation-In-Part US8744422B2 (en) | 2011-12-22 | 2012-06-08 | Systems and methods for terminating telephony communications to mobile telephony devices |
US13/568,416 Continuation US9020477B2 (en) | 2011-12-22 | 2012-08-07 | Systems and methods for terminating telephony communications to mobile telephony devices |
Publications (2)
Publication Number | Publication Date |
---|---|
US20130165089A1 US20130165089A1 (en) | 2013-06-27 |
US8600364B2 true US8600364B2 (en) | 2013-12-03 |
Family
ID=48655030
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/334,849 Active US8600364B2 (en) | 2011-12-22 | 2011-12-22 | Systems and methods for terminating telephony communications to mobile telephony devices |
US13/568,416 Active US9020477B2 (en) | 2011-12-22 | 2012-08-07 | Systems and methods for terminating telephony communications to mobile telephony devices |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/568,416 Active US9020477B2 (en) | 2011-12-22 | 2012-08-07 | Systems and methods for terminating telephony communications to mobile telephony devices |
Country Status (1)
Country | Link |
---|---|
US (2) | US8600364B2 (en) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9491610B2 (en) | 2014-05-30 | 2016-11-08 | Vonage America Inc. | Method and apparatus for intra-network roaming for IP telephony network |
US9521112B2 (en) | 2013-09-16 | 2016-12-13 | Vonage America Inc. | Systems and methods of assigning and using virtual telephone numbers |
US9686668B2 (en) | 2014-05-30 | 2017-06-20 | Vonage America Inc. | Method and apparatus for intra-network roaming for IP telephony network |
US10009387B2 (en) | 2013-09-16 | 2018-06-26 | Vonage America Inc. | Systems and methods of assigning and using virtual telephone numbers |
Families Citing this family (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8600364B2 (en) | 2011-12-22 | 2013-12-03 | Vonage Network, Llc | Systems and methods for terminating telephony communications to mobile telephony devices |
US9002335B2 (en) | 2011-12-22 | 2015-04-07 | Guy Fighel | Systems and methods for terminating telephony communications to mobile telephony devices |
US8958785B2 (en) | 2011-12-22 | 2015-02-17 | Vonage Network, Llc | Systems and methods for terminating telephony communications to mobile telephony devices |
US9020478B2 (en) | 2011-12-22 | 2015-04-28 | Vonage Network, Llc | Systems and methods for terminating telephony communications to mobile telephony devices |
US8744422B2 (en) | 2011-12-22 | 2014-06-03 | Vonage Network, Llc. | Systems and methods for terminating telephony communications to mobile telephony devices |
US9002336B2 (en) | 2011-12-22 | 2015-04-07 | Vonage Network, Llc | Systems and methods for terminating telephony communications to mobile telephony devices |
US8855612B2 (en) | 2011-12-22 | 2014-10-07 | Vonage Network, Llc. | Systems and methods of terminating telephony communications to mobile telephony devices |
US9491600B2 (en) | 2011-12-22 | 2016-11-08 | Vonage America Inc. | Systems and methods for terminating telephony communications to mobile telephony devices |
US8934882B2 (en) | 2011-12-22 | 2015-01-13 | Vonage Network, Llc | Systems and methods for terminating telephony communications to mobile telephony devices |
US8989721B2 (en) | 2011-12-22 | 2015-03-24 | Vonage Network, Llc | Systems and methods for terminating telephony communications to mobile telephony devices |
CN103369499B (en) * | 2012-04-03 | 2018-03-09 | 富泰华工业(深圳)有限公司 | international roaming service activation system and method |
US20140029748A1 (en) * | 2012-07-30 | 2014-01-30 | Baruch Sterman | Systems and methods for preventing the examination of data packet contents |
US20150304829A1 (en) * | 2014-04-22 | 2015-10-22 | Vonage Network, Llc | Call forwarding verification |
Citations (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5745850A (en) * | 1994-10-24 | 1998-04-28 | Lucent Technologies, Inc. | Apparatus and method for mobile (e.g. cellular or wireless) telephone call handover and impersonation |
US20060264213A1 (en) | 2005-05-19 | 2006-11-23 | Lucent Technologies, Inc. | System for simultaneous registration of VoIP network for dual mode mobile telephone stations |
US20070015536A1 (en) | 2005-04-06 | 2007-01-18 | Qwest Communications International Inc. | Handset registration in a dual-mode environment |
US20070064682A1 (en) | 2005-09-16 | 2007-03-22 | Jennifer Adams | Methods and computer program products for managing a plurality of voice-over internet protocol phone lines in customer premises equipment |
US20070121580A1 (en) | 2005-10-03 | 2007-05-31 | Paolo Forte | Classification for media stream packets in a media gateway |
US20070167167A1 (en) | 2003-02-18 | 2007-07-19 | Roamware Inc. | Network-based system for rerouting phone calls from phone networks to VoIP clients for roamers and subscribers who do not answer |
US20070274485A1 (en) | 2006-05-09 | 2007-11-29 | Garrison William J | Network-independent ringback feature |
US20080039080A1 (en) * | 2006-08-09 | 2008-02-14 | Avaya Technology Llc | Enterprise mobility user |
US20080153480A1 (en) | 2005-02-23 | 2008-06-26 | Yue Jun Jiang | Integrated cellular VoIP for call rerouting |
US20080244148A1 (en) | 2007-04-02 | 2008-10-02 | Go2Call.Com, Inc. | VoIP Enabled Femtocell with a USB Transceiver Station |
US20110096771A1 (en) | 2007-11-29 | 2011-04-28 | Sami Saru | Voice over internet protocol (voip) systems, methods, network elements and applications |
Family Cites Families (28)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6088126A (en) | 1994-03-28 | 2000-07-11 | Siemens Information And Communication Networks, Inc. | Fax overflow loopback prevention |
US6571094B1 (en) | 1998-01-22 | 2003-05-27 | At&T Wireless Services, Inc. | Method and system for remote call forwarding of telephone calls from an IP connection |
US6285750B1 (en) | 1998-12-03 | 2001-09-04 | At&T Corp. | Method and apparatus for remotely controlling telephone call-forwarding |
US6615037B1 (en) | 1999-06-18 | 2003-09-02 | Nortel Networks Limited | Method apparatus and system for call forwarding when roaming from a first type network to a second type network in a communication system |
US20030003900A1 (en) | 2001-06-29 | 2003-01-02 | Goss Stephen C. | Proximity-based call forwarding |
US7460657B1 (en) | 2002-07-25 | 2008-12-02 | At&T Intellectual Property I, L.P. | Speed activation of pre-determined call-forwarding number |
US7116975B1 (en) | 2003-01-21 | 2006-10-03 | Cingular Wireless Ii, Llc | Systems and methods for automatic call forwarding in a wireless mobile station |
US7379436B2 (en) | 2004-02-23 | 2008-05-27 | Roamware Inc. | Integrated cellular VoIP for call rerouting |
US20040248563A1 (en) | 2003-06-09 | 2004-12-09 | Ayers John I. | Method and system for processing call-forward telephone numbers received for a subscriber |
US7551920B1 (en) | 2003-09-18 | 2009-06-23 | Sprint Spectrum L.P. | Signal strength-based call forwarding for wireless phones |
EP1759463A4 (en) | 2004-06-02 | 2011-12-28 | Mobilemax Inc | System for optimizing cellular telephone call placement with minimal user overhead |
US8837704B2 (en) | 2006-08-31 | 2014-09-16 | Microsoft Corporation | Client controlled dynamic call forwarding |
US8139753B2 (en) | 2006-11-20 | 2012-03-20 | Richard Pickering | Method and apparatus for handling a telephone call |
US8270958B2 (en) | 2007-06-20 | 2012-09-18 | Verizon Patent And Licensing Inc. | Apparatus, system and method for automated communication forwarding |
US9143617B2 (en) | 2008-11-20 | 2015-09-22 | Centurylink Intellectual Property Llc | System and method for providing a call forward indicator |
US9344866B2 (en) | 2009-12-11 | 2016-05-17 | Telefonaktiebolaget L M Ericsson (Publ) | Notifying roaming subscriber of missed call |
US8693994B2 (en) | 2011-12-22 | 2014-04-08 | Vonage Network, Llc | Systems and methods for terminating telephony communications to mobile telephony devices |
US9002335B2 (en) | 2011-12-22 | 2015-04-07 | Guy Fighel | Systems and methods for terminating telephony communications to mobile telephony devices |
US8600364B2 (en) | 2011-12-22 | 2013-12-03 | Vonage Network, Llc | Systems and methods for terminating telephony communications to mobile telephony devices |
US9491600B2 (en) | 2011-12-22 | 2016-11-08 | Vonage America Inc. | Systems and methods for terminating telephony communications to mobile telephony devices |
US8934882B2 (en) | 2011-12-22 | 2015-01-13 | Vonage Network, Llc | Systems and methods for terminating telephony communications to mobile telephony devices |
US9002336B2 (en) | 2011-12-22 | 2015-04-07 | Vonage Network, Llc | Systems and methods for terminating telephony communications to mobile telephony devices |
US8744422B2 (en) | 2011-12-22 | 2014-06-03 | Vonage Network, Llc. | Systems and methods for terminating telephony communications to mobile telephony devices |
US8855612B2 (en) | 2011-12-22 | 2014-10-07 | Vonage Network, Llc. | Systems and methods of terminating telephony communications to mobile telephony devices |
US8989721B2 (en) | 2011-12-22 | 2015-03-24 | Vonage Network, Llc | Systems and methods for terminating telephony communications to mobile telephony devices |
US8958785B2 (en) | 2011-12-22 | 2015-02-17 | Vonage Network, Llc | Systems and methods for terminating telephony communications to mobile telephony devices |
US9020478B2 (en) | 2011-12-22 | 2015-04-28 | Vonage Network, Llc | Systems and methods for terminating telephony communications to mobile telephony devices |
US8571060B2 (en) | 2011-12-22 | 2013-10-29 | Vonage Network, Llc | Systems and methods for terminating telephony communications to mobile telephony devices |
-
2011
- 2011-12-22 US US13/334,849 patent/US8600364B2/en active Active
-
2012
- 2012-08-07 US US13/568,416 patent/US9020477B2/en active Active
Patent Citations (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5745850A (en) * | 1994-10-24 | 1998-04-28 | Lucent Technologies, Inc. | Apparatus and method for mobile (e.g. cellular or wireless) telephone call handover and impersonation |
US20070167167A1 (en) | 2003-02-18 | 2007-07-19 | Roamware Inc. | Network-based system for rerouting phone calls from phone networks to VoIP clients for roamers and subscribers who do not answer |
US20080153480A1 (en) | 2005-02-23 | 2008-06-26 | Yue Jun Jiang | Integrated cellular VoIP for call rerouting |
US20070015536A1 (en) | 2005-04-06 | 2007-01-18 | Qwest Communications International Inc. | Handset registration in a dual-mode environment |
US20060264213A1 (en) | 2005-05-19 | 2006-11-23 | Lucent Technologies, Inc. | System for simultaneous registration of VoIP network for dual mode mobile telephone stations |
US20070064682A1 (en) | 2005-09-16 | 2007-03-22 | Jennifer Adams | Methods and computer program products for managing a plurality of voice-over internet protocol phone lines in customer premises equipment |
US20070121580A1 (en) | 2005-10-03 | 2007-05-31 | Paolo Forte | Classification for media stream packets in a media gateway |
US20070274485A1 (en) | 2006-05-09 | 2007-11-29 | Garrison William J | Network-independent ringback feature |
US20080039080A1 (en) * | 2006-08-09 | 2008-02-14 | Avaya Technology Llc | Enterprise mobility user |
US20080244148A1 (en) | 2007-04-02 | 2008-10-02 | Go2Call.Com, Inc. | VoIP Enabled Femtocell with a USB Transceiver Station |
US7990912B2 (en) | 2007-04-02 | 2011-08-02 | Go2Call.Com, Inc. | VoIP enabled femtocell with a USB transceiver station |
US20110096771A1 (en) | 2007-11-29 | 2011-04-28 | Sami Saru | Voice over internet protocol (voip) systems, methods, network elements and applications |
Non-Patent Citations (4)
Title |
---|
"3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Call Forwarding (CF) supplementary services; Stage 2 (Release 11)", 3GPP Standard; 3GPP TS 23.082, 3rd Generation Partnership Project (3GPP), Mobile Competence Centre; 650, Route Des Lucioles, F-06921 Sophia-Antipolis Cedex; France, vol. CT WG4, No. V11.0.0, Dec. 17, 2011, pp. 1-86, XP050554577, [retrieved on Dec. 17, 2011] paragraphs [0001]-[01.2]; figures 1.1, 1.11. |
Anonymous: "Easy Call Forwarding App" Android Forums, Dec. 2, 2010 pp. 1-4, XP055066320, Retrieved from the Internet: URL:http://androidforums.com/android-applications/7380-easy-call-forwarding-app.html [retrieved on Jun. 12, 2013] the whole document. |
Office Action issued in U.S. Appl. No. 12/987,559 on May 21, 2013. |
Partial Search Report issued PCT/US2012/071248 issued Jun. 24, 2013. |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9521112B2 (en) | 2013-09-16 | 2016-12-13 | Vonage America Inc. | Systems and methods of assigning and using virtual telephone numbers |
US10009387B2 (en) | 2013-09-16 | 2018-06-26 | Vonage America Inc. | Systems and methods of assigning and using virtual telephone numbers |
US9491610B2 (en) | 2014-05-30 | 2016-11-08 | Vonage America Inc. | Method and apparatus for intra-network roaming for IP telephony network |
US9686668B2 (en) | 2014-05-30 | 2017-06-20 | Vonage America Inc. | Method and apparatus for intra-network roaming for IP telephony network |
Also Published As
Publication number | Publication date |
---|---|
US20130165089A1 (en) | 2013-06-27 |
US9020477B2 (en) | 2015-04-28 |
US20130165092A1 (en) | 2013-06-27 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8600364B2 (en) | Systems and methods for terminating telephony communications to mobile telephony devices | |
US9002336B2 (en) | Systems and methods for terminating telephony communications to mobile telephony devices | |
US9491600B2 (en) | Systems and methods for terminating telephony communications to mobile telephony devices | |
US8571060B2 (en) | Systems and methods for terminating telephony communications to mobile telephony devices | |
US8862109B2 (en) | Systems and methods for terminating telephony communications to mobile telephony devices via a non-native telephony service provider | |
US8693994B2 (en) | Systems and methods for terminating telephony communications to mobile telephony devices | |
US8989721B2 (en) | Systems and methods for terminating telephony communications to mobile telephony devices | |
US9020478B2 (en) | Systems and methods for terminating telephony communications to mobile telephony devices | |
US8934882B2 (en) | Systems and methods for terminating telephony communications to mobile telephony devices | |
US8855612B2 (en) | Systems and methods of terminating telephony communications to mobile telephony devices | |
US9002335B2 (en) | Systems and methods for terminating telephony communications to mobile telephony devices | |
US8958785B2 (en) | Systems and methods for terminating telephony communications to mobile telephony devices | |
US11184479B2 (en) | Mobile roaming and authentication | |
EP3114876B1 (en) | Cell tower functionality with satellite access to allow a cell device to roam on a satellite network | |
US8265083B1 (en) | Systems and methods of providing communications services | |
US10498774B2 (en) | Systems and methods for improved E911 call handling | |
US9854102B2 (en) | Systems and methods of providing communications services | |
US9603115B2 (en) | Method and apparatus for cellular roaming charge bypass call completion | |
US20160066365A1 (en) | Systems and methods for terminating telephony communications to mobile telephony devices | |
US10973059B2 (en) | Systems and methods of providing communications services | |
US20130178237A1 (en) | SMS assisted Call Anchoring to Facilitate the Provision of Advanced Communications Services | |
US20130114590A1 (en) | Systems and methods of providing communications services | |
EP2865207A2 (en) | Methods, apparatuses and computer readable media for terminating telephony communications to mobile telephony devices making use of a mobile roaming termination service |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: VONAGE NETWORK, LLC, NEW JERSEY Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:FIGHEL, GUY;REEL/FRAME:027434/0454 Effective date: 20111221 |
|
AS | Assignment |
Owner name: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT, ILLINOIS Free format text: SECURITY AGREEMENT;ASSIGNOR:VONAGE NETWORK LLC;REEL/FRAME:028194/0597 Effective date: 20120510 Owner name: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT Free format text: SECURITY AGREEMENT;ASSIGNOR:VONAGE NETWORK LLC;REEL/FRAME:028194/0597 Effective date: 20120510 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT, ILLINOIS Free format text: SECURITY INTEREST;ASSIGNORS:VONAGE HOLDINGS CORP.;VONAGE NETWORK LLC;VONAGE BUSINESS SOLUTIONS INC.;AND OTHERS;REEL/FRAME:033545/0424 Effective date: 20140813 Owner name: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT Free format text: SECURITY INTEREST;ASSIGNORS:VONAGE HOLDINGS CORP.;VONAGE NETWORK LLC;VONAGE BUSINESS SOLUTIONS INC.;AND OTHERS;REEL/FRAME:033545/0424 Effective date: 20140813 |
|
AS | Assignment |
Owner name: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT, ILLINOIS Free format text: SECURITY INTEREST;ASSIGNORS:VONAGE HOLDINGS CORP.;VONAGE AMERICA INC.;VONAGE BUSINESS SOLUTIONS, INC.;AND OTHERS;REEL/FRAME:036205/0485 Effective date: 20150727 Owner name: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT Free format text: SECURITY INTEREST;ASSIGNORS:VONAGE HOLDINGS CORP.;VONAGE AMERICA INC.;VONAGE BUSINESS SOLUTIONS, INC.;AND OTHERS;REEL/FRAME:036205/0485 Effective date: 20150727 |
|
AS | Assignment |
Owner name: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE PATENT APPLICATION NUMBER 13966486 PREVIOUSLY RECORDED ON REEL 033545 FRAME 0424. ASSIGNOR(S) HEREBY CONFIRMS THE SECURITY INTEREST;ASSIGNORS:VONAGE HOLDINGS CORP.;VONAGE NETWORK LLC;VONAGE BUSINESS SOLUTIONS INC.;AND OTHERS;REEL/FRAME:037570/0203 Effective date: 20140813 Owner name: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT, ILLINOIS Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE PATENT APPLICATION NUMBER 13966486 PREVIOUSLY RECORDED ON REEL 033545 FRAME 0424. ASSIGNOR(S) HEREBY CONFIRMS THE SECURITY INTEREST;ASSIGNORS:VONAGE HOLDINGS CORP.;VONAGE NETWORK LLC;VONAGE BUSINESS SOLUTIONS INC.;AND OTHERS;REEL/FRAME:037570/0203 Effective date: 20140813 |
|
AS | Assignment |
Owner name: VONAGE AMERICA INC., NEW JERSEY Free format text: MERGER;ASSIGNOR:VONAGE NETWORK LLC;REEL/FRAME:037600/0456 Effective date: 20151223 |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
AS | Assignment |
Owner name: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT, ILLINOIS Free format text: SECURITY INTEREST;ASSIGNOR:VONAGE AMERICA INC.;REEL/FRAME:047502/0628 Effective date: 20181106 Owner name: JPMORGAN CHASE BANK, N.A., AS ADMINISTRATIVE AGENT Free format text: SECURITY INTEREST;ASSIGNOR:VONAGE AMERICA INC.;REEL/FRAME:047502/0628 Effective date: 20181106 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 8 |
|
AS | Assignment |
Owner name: VONAGE AMERICA LLC, NEW JERSEY Free format text: CHANGE OF NAME;ASSIGNOR:VONAGE AMERICA INC.;REEL/FRAME:060313/0292 Effective date: 20191226 |
|
AS | Assignment |
Owner name: TOKBOX, INC., NEW JERSEY Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:061002/0340 Effective date: 20220721 Owner name: NEXMO INC., NEW JERSEY Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:061002/0340 Effective date: 20220721 Owner name: VONAGE BUSINESS INC., NEW JERSEY Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:061002/0340 Effective date: 20220721 Owner name: VONAGE HOLDINGS CORP., NEW JERSEY Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:061002/0340 Effective date: 20220721 Owner name: VONAGE AMERICA INC., NEW JERSEY Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:061002/0340 Effective date: 20220721 |