US20060068796A1 - Retrieving jurisdiction information from home location register - Google Patents
Retrieving jurisdiction information from home location register Download PDFInfo
- Publication number
- US20060068796A1 US20060068796A1 US10/955,063 US95506304A US2006068796A1 US 20060068796 A1 US20060068796 A1 US 20060068796A1 US 95506304 A US95506304 A US 95506304A US 2006068796 A1 US2006068796 A1 US 2006068796A1
- Authority
- US
- United States
- Prior art keywords
- wireless
- call
- computer
- subscriber
- switching center
- 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.)
- Abandoned
Links
Images
Classifications
-
- 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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/26—Network addressing or numbering for mobility support
- H04W8/28—Number portability ; Network address portability
Definitions
- the invention relates generally to wireless communications system and more particularly to a method and apparatus by which calls redirected from a mobile phone number to another number can be billed based on the service provider and the distance over which the forwarded call portion would have traveled if it had been placed by the non-roaming mobile telephone.
- Wireless communication has become nearly ubiquitous and competition between service providers often induces subscribers to switch to carriers that a subscriber believes or perceives to be providing a better “deal.”
- an adverse consequence of changing carriers has been the forfeiture of a wireless phone number.
- service providers have been compelled to offer number portability by which a subscriber of one service provider can terminate his service and carry or “port” the number given to him by one service provider to another service provider. This is possible as long as the number remains in the same relative geographic location (i.e., the number remains within the original rate center.) It is even possible to port a wireline number to a wireless service provider. In the future, number portability will provide the ability to port a phone number from one disparate geographic location to another.
- a wireless subscriber who obtains a wireless phone number from a service provider could have his mobile phone number “ported” to a new wireless service provider. If the subscriber uses his wireless phone to forward calls to another location, the calls that were made to the subscriber's phone, would need to be routed by the subscriber's new service provider to the forwarded destination number. If the forwarding phone's number were used to determine the service provider from which to exact payment for the call forwarding, using just the phone numbers it would appear that a call originated from the mobile customer's old service provider's network.
- charges for so-called long-distance calls and charges for so-called “toll” calls are enhanced over the charges imposed by carriers for “local” calls.
- the determination and hence the charge for a call is primarily determined by the geographic distance between the location of the calling phone and the phone being called.
- the gateway doesn't have the 6 digit code to identify the location of the switch from which the call would have originated if the forwarding phone had placed the call itself from its home service area.
- the intent of this invention is to provide a method by which a gateway switch can obtain data sufficient to identify the service provider and location of the switch, or geographic division thereof, from which a redirected call would have originated had the call originated from the mobile subscriber's home service area.
- the invention in one implementation encompasses a home location register data base, embodied as a processor coupled to a wireless communications network through any appropriate prior art network interface.
- a data storage device such as one or more hard disk drives that is operatively coupled to the processor stores wireless subscriber information.
- Computer-readable signal-bearing media coupled to the processor enable the processor to receive inquiries from communications network switches that are also coupled to the home location register data base.
- the processor executes a method, which includes sending subscriber information to network switches.
- a network switch receives a call that is to be routed to a wireless telephone
- the network switch first queries the home location register data base about the wireless telephone. If the wireless telephone has been set up to forward its calls to another number, the home location register data base sends a response to the inquiring network switch, informing it of the number to which the call should be forwarded, and, the identity of a switch in the wireless network from which the wireless telephone should be charged for placing a call to the number to which its calls are to be forwarded.
- FIG. 1 is a representation of one implementation of a wireless network that comprises a home location register data base that communicates with mobile switching centers in a wireless network and a gateway mobile switching center;
- FIG. 2 is a representation of one exemplary part of the switches embodied in FIG. 1 as the mobile switching centers and the gateway mobile switching center;
- FIG. 3 is a flow chart showing steps of a method practiced by the gateway mobile switching center shown in FIG. 1 ;
- FIG. 4 is a flow chart showing steps of a method practiced by the home location register data base shown in FIG. 1 .
- a wireless communication network 10 comprises a central gateway mobile switching center 12 , a home location register data base 14 and at least two mobile switching centers 16 and 18 , each of which is a mobile switching center for a wireless service provider (not shown) that provide wireless communications services to the wireless telephones 20 of service subscribers throughout a geographic area 22 .
- the gateway mobile switching center 12 and both of the mobile switching centers 16 and 18 are linked to the home location register data base 14 via appropriately-capable data links 15 ′ and 17 ′ over which call routing and other information pertinent to the network 10 can be carried.
- the call 26 When a call 26 is placed to a wireless subscriber's telephone 20 from outside the network 10 , the call 26 is eventually routed to the central gateway mobile switching center 12 (e.g., through the public switched telephone network or PSTN). At least one function of the gateway mobile switching center 12 is to route the call 26 to a mobile switching center 16 or 18 from which a wireless communications link can be established with the wireless subscriber's telephone 20 .
- the central gateway mobile switching center 12 when a call 26 to be routed to a wireless subscriber's telephone 20 is received by the central gateway mobile switching center 12 , the central gateway mobile switching center 12 sends a data message 15 that is a query to the home location register data base 14 for information about the telephone 20 and the service provided to the subscriber's telephone 20 by the wireless service provider.
- the form of the query message 15 sent to the home location register data base 14 is not critical. Existing protocols, such as those compliant with ANSI-41 standard as well as others that are known to those of skill in the art, can be used.
- the home location register data base 14 functions as data storage device that preferably stores several pieces of information about each wireless subscriber of a wireless service provider.
- the home location register data base 14 stores the electronic serial number or ESN and the mobile identification number or MIN of each subscriber's phone 20 , including the digits of the wireless telephone's number.
- the home location register data base 14 also stores information that identifies the communication services provided to a subscriber's phone by the service provider, such as whether a phone is entitled to services such as call forwarding and if so, a number or numbers to which a call 26 to a phone 20 is to be routed if the subscriber has activated call forwarding.
- the home location register data base 14 can also store the identity a mobile switching center or geographic coverage area thereof, into which the mobile telephone's number was ported into, by the service provider at the subscriber's request.
- the “identity” of a mobile switching center into which a number is ported can be in the form of a six digit area code and office code (commonly known to those of ordinary skill as the jurisdiction information parameter or “JIP”) that is unique to the geographic location assigned to the mobile subscriber's home service area. That mobile switching center is herein considered to be the “home” mobile switching center for that subscriber.
- information stored in the home location register data base 14 includes at least one number to which a call 26 to a wireless subscriber's telephone 20 number is to be forwarded but also includes the identity of the mobile switching center, or a geographic division thereof, having “jurisdiction” for the wireless subscriber number to which a call 26 was placed.
- the home location register data base 14 stores the identity of a mobile switching center 16 of a wireless communications service provider, to which a call 26 to the wireless subscriber number is to be routed, when a call to the non-roaming wireless subscriber is not to be forwarded to a second number.
- the home location register data base 14 when the home location register data base 14 receives the query message 15 that requests information from the gateway mobile switching center 12 , the home location register data base 14 returns a responsive message 17 to the gateway mobile switching center 12 that includes, among other things, information as to how and where to route the call 26 so that it will be forwarded as specified by the subscriber. If a subscriber has activated call forwarding, the home location register data base 14 provides to the gateway mobile switching center 12 , the phone number to which the calls for the subscriber are to be forwarded, but it also returns to the gateway mobile switching center 12 , information that identifies the mobile switching center 16 or 18 , or geographic division thereof, that the call 26 would have been routed to but for the subscriber's request to forward his calls to another number.
- the gateway mobile switching center 12 When the gateway mobile switching center 12 receives a telephone number (or wireless number) to which a call 26 is to be forwarded from the home location register data base 14 , the gateway mobile switching center 12 can thereafter proceed to forward the call 26 directly to a switching system 28 in the PSTN to which the call 26 needs to be routed to deliver the call 26 to the subscriber's destination number.
- the call By determining from the home location register data base 14 that a call 26 to a mobile telephone 20 is to be routed to a particular number, and by obtaining the identity of the mobile switching center, or geographic division thereof, 16 or 18 that would have otherwise received the call 26 and which then would have forwarded the call 26 , the call can be more quickly routed to its destination but an appropriate service charge can be levied on the subscriber by determining the path that the call 26 would have been forwarded over, if the call would have originated from the subscriber's wireless telephone 20 .
- the location of where a forwarded call would have been originated from, if it were placed by the wireless subscriber's phone 20 , i.e., the mobile switching center 16 or 18 having “jurisdiction” of the mobile phone 20 can be determined a number of ways.
- the mobile switching center having jurisdiction of a mobile telephone number can be identified by the digits of a location routing number assigned to the mobile switching center 16 or 18 .
- the first six digits of a location routing number can identify where a call should have originated from and how a call forwarded from, should be billed.
- the home location register data base 14 stores the first six digits of a non-ported telephone number assigned to the switch to identify the jurisdiction of the switch into which the mobile telephone number of the calls of which are forwarded to another number was ported.
- the home location register data base 14 stores data that identifies communication services provided to the wireless subscriber by the subscriber's service provider, including information that specifies whether the wireless subscriber is provided with call forwarding service.
- Messages sent to the home location register data base 14 from the gateway mobile switching center that include requests for subscriber information, can be compliant with ANSI-41 or compliant with messages used in a “3GPP” signaling environment.
- switching systems used in wireless communications networks and switching systems used in the PSTN employ a stored-program computer to control one or more matrices by which calls can be routed from a source on a switch input port to a destination on a switch output port.
- the term “computer” should be considered to be equivalent to and include, one or more switching systems or switch matrices as they are sometimes called.
- the home location register data base register 14 it too is comprised of a computer but also a data storage device, such as one or more hard disk drives, one or more CD-ROM drives and/or semiconductor memory from which information about the systems coupled to it can be quickly recovered and sent into the network 10 to which it is coupled and by which messages to the various computers/switches can be sent.
- a data storage device such as one or more hard disk drives, one or more CD-ROM drives and/or semiconductor memory from which information about the systems coupled to it can be quickly recovered and sent into the network 10 to which it is coupled and by which messages to the various computers/switches can be sent.
- computers are comprised of a central processing unit or CPU that executes program instructions. Accordingly, each of the switching systems/computers disclosed above is comprised of at least one processor that executes instructions that are stored in a program memory to which the processors are operatively coupled.
- FIG. 2 shows an example of a CPU 200 is coupled to memory 202 embodied in well known devices such as RAM, ROM, EEPROM and Flash memory, which can store instructions for the CPU.
- FIG. 2 also shows the CPU coupled to a hard disk storage 204 device and to a network interface 206 through which the CPU can communicate with the data network.
- Computers, memory, storage devices and network interfaces are well-known in the art and a further presentation of them herein is omitted for brevity.
- FIG. 3 An illustrative description of exemplary operation of the network of FIG. 1 is presented, for explanatory purposes in the flow charts of FIGS. 3 and 4 .
- the steps of FIG. 3 are performed by the gateway mobile switching center 12 whereas the steps of FIG. 4 are performed by the home location register data base 14 .
- step 302 shows the receipt of a signaling message by, or at, the gateway mobile switching center 12 .
- the signaling message can be an SS7 signaling message but regardless of its format, it can be considered to be a message by which a call is being directed to a mobile telephone 20 within the wireless communications network 10 for which the gateway mobile switching center 12 receives incoming calls.
- step 304 after having received the pertinent call data, the gateway mobile switching center 12 sends a different message to the home location register data base 14 by which the gateway mobile switching center 12 requests information on the mobile telephone to which the call just received is to be routed.
- the gateway mobile switching center 12 receives data from the home location register data base 14 that tells the gateway mobile switching center 12 several things but in particular, a number to which a call to the telephone 20 is to be forwarded instead.
- the home location register data base 14 provides in its responsive message 17 , the identity and/or location of the mobile switching center that the call to the mobile telephone would have been routed to by the gateway mobile switching center 12 , if the subscriber had not directed his calls to be forwarded. In so doing, the home location register data base 14 identifies to the gateway mobile switching center 12 , the identity and location of a geographic area or location from which the forwarded call 26 should be billed.
- step 308 the call to the wireless telephone 20 is routed by the gateway mobile switching center 12 to another switching system 28 , that is the next switch to which the call 26 needs to be routed in order to route the call to the destination number.
- FIG. 4 depicts steps performed by the home location register data base 14 , which also is comprised of a computer, program memory and a storage device. Like the gateway mobile switching center 12 and the mobile switching centers 16 and 18 , the home location register data base 14 is coupled to the network 10 .
- the home location register data base 14 receives data on the subscribers within a wireless communications network and the services that are to be provided to them.
- the home location register data base 14 stores information on whether a particular phone number should be provided with call forwarding and if so, records information that indicates when calls are to be forwarded and a number to which the calls are to be routed.
- the data that is received for storage within the home location register data base 14 can originate from a variety of sources, at least one of which is the operator of the wireless communications network at the time that a telephone/number is put into service.
- the home location register data base 14 also stores information on mobile phone numbers that are “ported” in to a wireless service provider network 10 by a customer of another service provider who wishes to transport his mobile phone number to the service provider for network 10 .
- the home location register data base 14 register receives from the gateway mobile switching system 12 , a message that is an inquiry, requesting information on a mobile telephone number/subscriber to which a call that arrived at the gateway 12 , should be routed.
- the requested information is located by the home location register data base 14 processor/computer from its associated data storage devices and sent to the gateway mobile switching center 12 for processing the call according to the instructions and information received from the home location register data base 14 .
- the gateway mobile switching center 12 can forward the call 26 to another switch 28 , with the call forwarding information and call origination data from the home location register data base 14 so that the call can be properly routed and billed by service providers along the way.
- mobile telephone number portability can be provided and services such as automatic call forwarding properly billed by retrieving the identity and location of a switching system that would have been required to route a call to a number to which calls to a mobile phone number are to be routed.
- automatic call forwarding properly billed by retrieving the identity and location of a switching system that would have been required to route a call to a number to which calls to a mobile phone number are to be routed.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephonic Communication Services (AREA)
Abstract
Calls to a wireless telephone number that are to be redirected by a gateway switch to another number can be properly billed, even if the wireless telephone number is ported to another service provider by billing the wireless telephone number subscriber for the charge that would have been incurred by placing a call to the forwarded number from the mobile telephone located in its home service area.
Description
- The invention relates generally to wireless communications system and more particularly to a method and apparatus by which calls redirected from a mobile phone number to another number can be billed based on the service provider and the distance over which the forwarded call portion would have traveled if it had been placed by the non-roaming mobile telephone.
- Wireless communication has become nearly ubiquitous and competition between service providers often induces subscribers to switch to carriers that a subscriber believes or perceives to be providing a better “deal.” Until recently, an adverse consequence of changing carriers has been the forfeiture of a wireless phone number. Recently, service providers have been compelled to offer number portability by which a subscriber of one service provider can terminate his service and carry or “port” the number given to him by one service provider to another service provider. This is possible as long as the number remains in the same relative geographic location (i.e., the number remains within the original rate center.) It is even possible to port a wireline number to a wireless service provider. In the future, number portability will provide the ability to port a phone number from one disparate geographic location to another.
- Such number portability has led to at least one problem for carriers.
- Heretofore, it was possible to identify a switch from which a call originated and hence the service provider of the switch from whence a call originated, simply by the first few digits of a phone number. The identity of a service provider responsible for collecting revenue from a customer for a call could be determined by the number from which the call originated.
- With the advent of service provider number portability, a wireless subscriber who obtains a wireless phone number from a service provider could have his mobile phone number “ported” to a new wireless service provider. If the subscriber uses his wireless phone to forward calls to another location, the calls that were made to the subscriber's phone, would need to be routed by the subscriber's new service provider to the forwarded destination number. If the forwarding phone's number were used to determine the service provider from which to exact payment for the call forwarding, using just the phone numbers it would appear that a call originated from the mobile customer's old service provider's network.
- As is well-known, charges for so-called long-distance calls and charges for so-called “toll” calls are enhanced over the charges imposed by carriers for “local” calls. As is also known, the determination and hence the charge for a call is primarily determined by the geographic distance between the location of the calling phone and the phone being called.
- Heretofore, it was possible to identify a switch that a call originated from and hence the geographic location of where a call originated from, simply by the first few digits of a phone number. The charge to exact from a customer for a call could be determined by comparing the number being called to the number from which the call originated and calculating or deriving the distance and systems through which the call would have been carried.
- With the advent of number portability, in prior art, carriers have begun to identify the originating location of a call by means of a the 6 digit area code and office code of a location routing number assigned to the originating switch since the mobile number no longer identifies the originating switch or service provider. In the case of redirecting a call from a gateway switch, the gateway doesn't have the 6 digit code to identify the location of the switch from which the call would have originated if the forwarding phone had placed the call itself from its home service area. The intent of this invention is to provide a method by which a gateway switch can obtain data sufficient to identify the service provider and location of the switch, or geographic division thereof, from which a redirected call would have originated had the call originated from the mobile subscriber's home service area.
- In order to more properly bill for call forwarding services provided to mobile phone subscribers who have ported their phone numbers from one service provider to another, there exists a need for tracking the service provider and the location of the mobile phone switching system, or a geographic division thereof, from which a mobile phone number that forwarded a call, would have originated the call if the forwarding phone had placed the forwarded call itself from its home service area.
- The invention in one implementation encompasses a home location register data base, embodied as a processor coupled to a wireless communications network through any appropriate prior art network interface. A data storage device, such as one or more hard disk drives that is operatively coupled to the processor stores wireless subscriber information. Computer-readable signal-bearing media coupled to the processor enable the processor to receive inquiries from communications network switches that are also coupled to the home location register data base.
- The processor executes a method, which includes sending subscriber information to network switches. When a network switch receives a call that is to be routed to a wireless telephone, the network switch first queries the home location register data base about the wireless telephone. If the wireless telephone has been set up to forward its calls to another number, the home location register data base sends a response to the inquiring network switch, informing it of the number to which the call should be forwarded, and, the identity of a switch in the wireless network from which the wireless telephone should be charged for placing a call to the number to which its calls are to be forwarded.
- Features of exemplary implementations of the invention will become apparent from the description, the claims, and the accompanying drawings in which:
-
FIG. 1 is a representation of one implementation of a wireless network that comprises a home location register data base that communicates with mobile switching centers in a wireless network and a gateway mobile switching center; -
FIG. 2 is a representation of one exemplary part of the switches embodied inFIG. 1 as the mobile switching centers and the gateway mobile switching center; -
FIG. 3 is a flow chart showing steps of a method practiced by the gateway mobile switching center shown inFIG. 1 ; and -
FIG. 4 is a flow chart showing steps of a method practiced by the home location register data base shown inFIG. 1 . - Turning to
FIG. 1 , awireless communication network 10 comprises a central gatewaymobile switching center 12, a home locationregister data base 14 and at least twomobile switching centers wireless telephones 20 of service subscribers throughout ageographic area 22. As shown inFIG. 1 , the gatewaymobile switching center 12 and both of themobile switching centers register data base 14 via appropriately-capable data links 15′ and 17′ over which call routing and other information pertinent to thenetwork 10 can be carried. - When a
call 26 is placed to a wireless subscriber'stelephone 20 from outside thenetwork 10, thecall 26 is eventually routed to the central gateway mobile switching center 12 (e.g., through the public switched telephone network or PSTN). At least one function of the gatewaymobile switching center 12 is to route thecall 26 to amobile switching center telephone 20. - In the preferred embodiment, when a
call 26 to be routed to a wireless subscriber'stelephone 20 is received by the central gatewaymobile switching center 12, the central gatewaymobile switching center 12 sends adata message 15 that is a query to the home locationregister data base 14 for information about thetelephone 20 and the service provided to the subscriber'stelephone 20 by the wireless service provider. The form of thequery message 15 sent to the home locationregister data base 14 is not critical. Existing protocols, such as those compliant with ANSI-41 standard as well as others that are known to those of skill in the art, can be used. The home locationregister data base 14 functions as data storage device that preferably stores several pieces of information about each wireless subscriber of a wireless service provider. Among other things, the home locationregister data base 14 stores the electronic serial number or ESN and the mobile identification number or MIN of each subscriber'sphone 20, including the digits of the wireless telephone's number. The home locationregister data base 14 also stores information that identifies the communication services provided to a subscriber's phone by the service provider, such as whether a phone is entitled to services such as call forwarding and if so, a number or numbers to which acall 26 to aphone 20 is to be routed if the subscriber has activated call forwarding. - The home location
register data base 14 can also store the identity a mobile switching center or geographic coverage area thereof, into which the mobile telephone's number was ported into, by the service provider at the subscriber's request. The “identity” of a mobile switching center into which a number is ported can be in the form of a six digit area code and office code (commonly known to those of ordinary skill as the jurisdiction information parameter or “JIP”) that is unique to the geographic location assigned to the mobile subscriber's home service area. That mobile switching center is herein considered to be the “home” mobile switching center for that subscriber. - In the prior art, when a mobile telephone subscriber activated call forwarding, calls to the
mobile telephone 20 from outside the service provider's network needed to be routed to a particular mobile switching center, (16 or 18 for example) having jurisdiction for the particular mobile telephone number. (The prior art method of routing the call to a mobile switching center is shown inFIG. 1 as the broken line between the gatewaymobile switching center 16 that is identified byreference numeral 26′) Thereafter, the mobile switching center for themobile phone 20 being called, would have forwarded the call on to anotherswitching system 28 in the PSTN, that would have routed thecall 26′ to the number to which the subscriber forwarded his calls. Routing a call to a mobile switching center having jurisdiction for a particular mobile phone number is not economically advantageous. - In the preferred embodiment, information stored in the home location
register data base 14 includes at least one number to which acall 26 to a wireless subscriber'stelephone 20 number is to be forwarded but also includes the identity of the mobile switching center, or a geographic division thereof, having “jurisdiction” for the wireless subscriber number to which acall 26 was placed. In other words, the home locationregister data base 14 stores the identity of amobile switching center 16 of a wireless communications service provider, to which acall 26 to the wireless subscriber number is to be routed, when a call to the non-roaming wireless subscriber is not to be forwarded to a second number. - Still referring to
FIG. 1 , when the home locationregister data base 14 receives thequery message 15 that requests information from the gatewaymobile switching center 12, the home locationregister data base 14 returns aresponsive message 17 to the gatewaymobile switching center 12 that includes, among other things, information as to how and where to route thecall 26 so that it will be forwarded as specified by the subscriber. If a subscriber has activated call forwarding, the home locationregister data base 14 provides to the gatewaymobile switching center 12, the phone number to which the calls for the subscriber are to be forwarded, but it also returns to the gatewaymobile switching center 12, information that identifies themobile switching center call 26 would have been routed to but for the subscriber's request to forward his calls to another number. - When the gateway
mobile switching center 12 receives a telephone number (or wireless number) to which acall 26 is to be forwarded from the home locationregister data base 14, the gatewaymobile switching center 12 can thereafter proceed to forward thecall 26 directly to aswitching system 28 in the PSTN to which thecall 26 needs to be routed to deliver thecall 26 to the subscriber's destination number. By determining from the home locationregister data base 14 that acall 26 to amobile telephone 20 is to be routed to a particular number, and by obtaining the identity of the mobile switching center, or geographic division thereof, 16 or 18 that would have otherwise received thecall 26 and which then would have forwarded thecall 26, the call can be more quickly routed to its destination but an appropriate service charge can be levied on the subscriber by determining the path that thecall 26 would have been forwarded over, if the call would have originated from the subscriber'swireless telephone 20. - The location of where a forwarded call would have been originated from, if it were placed by the wireless subscriber's
phone 20, i.e., themobile switching center mobile phone 20, can be determined a number of ways. In a preferred embodiment, the mobile switching center having jurisdiction of a mobile telephone number can be identified by the digits of a location routing number assigned to themobile switching center register data base 14 stores the first six digits of a non-ported telephone number assigned to the switch to identify the jurisdiction of the switch into which the mobile telephone number of the calls of which are forwarded to another number was ported. - Other information stored in the home location
register data base 14 includes the electronic serial number and the mobile identification number for a wireless subscriber's telephone. As set forth above, the home locationregister data base 14 stores data that identifies communication services provided to the wireless subscriber by the subscriber's service provider, including information that specifies whether the wireless subscriber is provided with call forwarding service. - In the preferred embodiment, signaling messages between the gateway
mobile switching center 12, the home locationdata base register 14 and mobile switching centers 16 and 18 and between any network-external switch 28 to which calls are sent using well-known SS7 messages. Messages sent to the home locationregister data base 14 from the gateway mobile switching center that include requests for subscriber information, can be compliant with ANSI-41 or compliant with messages used in a “3GPP” signaling environment. - As is well-known, switching systems used in wireless communications networks and switching systems used in the PSTN employ a stored-program computer to control one or more matrices by which calls can be routed from a source on a switch input port to a destination on a switch output port. As used herein, the term “computer” should be considered to be equivalent to and include, one or more switching systems or switch matrices as they are sometimes called.
- With respect to the home location register
data base register 14, it too is comprised of a computer but also a data storage device, such as one or more hard disk drives, one or more CD-ROM drives and/or semiconductor memory from which information about the systems coupled to it can be quickly recovered and sent into thenetwork 10 to which it is coupled and by which messages to the various computers/switches can be sent. - As is well known, computers are comprised of a central processing unit or CPU that executes program instructions. Accordingly, each of the switching systems/computers disclosed above is comprised of at least one processor that executes instructions that are stored in a program memory to which the processors are operatively coupled.
-
FIG. 2 shows an example of aCPU 200 is coupled tomemory 202 embodied in well known devices such as RAM, ROM, EEPROM and Flash memory, which can store instructions for the CPU.FIG. 2 also shows the CPU coupled to ahard disk storage 204 device and to anetwork interface 206 through which the CPU can communicate with the data network. Computers, memory, storage devices and network interfaces are well-known in the art and a further presentation of them herein is omitted for brevity. - An illustrative description of exemplary operation of the network of
FIG. 1 is presented, for explanatory purposes in the flow charts ofFIGS. 3 and 4 . The steps ofFIG. 3 are performed by the gatewaymobile switching center 12 whereas the steps ofFIG. 4 are performed by the home locationregister data base 14. - In
FIG. 3 , step 302 shows the receipt of a signaling message by, or at, the gatewaymobile switching center 12. The signaling message can be an SS7 signaling message but regardless of its format, it can be considered to be a message by which a call is being directed to amobile telephone 20 within thewireless communications network 10 for which the gatewaymobile switching center 12 receives incoming calls. - In
step 304, after having received the pertinent call data, the gatewaymobile switching center 12 sends a different message to the home locationregister data base 14 by which the gatewaymobile switching center 12 requests information on the mobile telephone to which the call just received is to be routed. - In
step 306, the gatewaymobile switching center 12 receives data from the home locationregister data base 14 that tells the gatewaymobile switching center 12 several things but in particular, a number to which a call to thetelephone 20 is to be forwarded instead. Importantly, the home locationregister data base 14 provides in itsresponsive message 17, the identity and/or location of the mobile switching center that the call to the mobile telephone would have been routed to by the gatewaymobile switching center 12, if the subscriber had not directed his calls to be forwarded. In so doing, the home locationregister data base 14 identifies to the gatewaymobile switching center 12, the identity and location of a geographic area or location from which the forwardedcall 26 should be billed. - In
step 308, the call to thewireless telephone 20 is routed by the gatewaymobile switching center 12 to anotherswitching system 28, that is the next switch to which thecall 26 needs to be routed in order to route the call to the destination number. Data received by the gatewaymobile switching center 12 from the home locationregister data base 14 that identifies the mobile switching center that would have forwarded the call if the gateway mobile switching center had not done so, is also forwarded to thenext switch 28 so that upon completion of the forwarded call, the subscriber who forwarded the call from his mobile phone number can be billed for the call-forwarding service that was provided, i.e., for the distance over which the call had to be carried and the networks through which the call had to be routed. -
FIG. 4 depicts steps performed by the home locationregister data base 14, which also is comprised of a computer, program memory and a storage device. Like the gatewaymobile switching center 12 and the mobile switching centers 16 and 18, the home locationregister data base 14 is coupled to thenetwork 10. - In
step 402, the home locationregister data base 14 receives data on the subscribers within a wireless communications network and the services that are to be provided to them. As an example, the home locationregister data base 14 stores information on whether a particular phone number should be provided with call forwarding and if so, records information that indicates when calls are to be forwarded and a number to which the calls are to be routed. The data that is received for storage within the home locationregister data base 14 can originate from a variety of sources, at least one of which is the operator of the wireless communications network at the time that a telephone/number is put into service. - The home location
register data base 14 also stores information on mobile phone numbers that are “ported” in to a wirelessservice provider network 10 by a customer of another service provider who wishes to transport his mobile phone number to the service provider fornetwork 10. In such a case, a number that originated from a pool of numbers of a service provider and to which a mobile switching center would have been assigned, is mapped or associated to another-mobile switching center, possibly located in a different geographic region. - In
step 404, the home locationregister data base 14 register receives from the gatewaymobile switching system 12, a message that is an inquiry, requesting information on a mobile telephone number/subscriber to which a call that arrived at thegateway 12, should be routed. - In
step 406, the requested information is located by the home locationregister data base 14 processor/computer from its associated data storage devices and sent to the gatewaymobile switching center 12 for processing the call according to the instructions and information received from the home locationregister data base 14. Once the gatewaymobile switching center 12 receives the home location register data baseresponsive message 17, the gatewaymobile switching center 12 can forward thecall 26 to anotherswitch 28, with the call forwarding information and call origination data from the home locationregister data base 14 so that the call can be properly routed and billed by service providers along the way. - In light of the foregoing, it should be apparent to those of ordinary skill that by using the invention disclosed and claimed herein that mobile telephone number portability can be provided and services such as automatic call forwarding properly billed by retrieving the identity and location of a switching system that would have been required to route a call to a number to which calls to a mobile phone number are to be routed. By routing such a call from a gateway mobile switching center that received it, around the mobile switching center that would normally accept calls for the wireless telephone, unnecessary call processing overhead is avoided and forwarded calls can be properly billed.
- The system and methods described above are examples. There may be many variations to the examples described above without departing from the spirit of the invention. For instance, the steps may be performed in a differing order, or steps may be added, deleted, or modified. In addition, there are many types of call redirection, of which immediate call forwarding is only one. The method of redirecting the call to another telephone number is independent of this invention. Examples of other types of call redirection to which this invention applies are call forwarding no page response, call forwarding busy line, call forwarding no answer, intelligent network based call redirection, late call forwarding, redirection to voice mail, selective call forwarding, etc.
- Although exemplary implementations of the invention have been depicted and described in detail herein, it will be apparent to those skilled in the relevant art that various modifications, additions, substitutions, and the like can be made without departing from the spirit of the invention and these are therefore considered to be within the scope of the invention as defined in the following claims.
Claims (20)
1. In wireless communications network that provides wireless communications services, a method of redirecting a call placed to a wireless subscriber's number, to a second number, comprising the steps of:
storing information in a first computer that is coupled to the wireless communications network, the stored information including:
at least one second number to which a call to the wireless subscriber number is to be redirected by a switching center for the wireless subscriber number; and
the identity of the mobile switching center, or geographic division thereof, of the first service provider, to which a call to the wireless subscriber number is to be routed when a call to the non-roaming wireless subscriber is not to be redirected to a second number.
2. The method of claim 1 , wherein the step of storing information includes the step of:
storing in the first computer, the identity of a mobile switching center, or a geographic division thereof, in a wireless communication network that has jurisdiction over a geographic coverage area for the wireless subscriber number.
3. The method of claim 1 , wherein the step of storing information includes the step of:
storing the identity of the mobile switching center or geographic division thereof, for the home service area of a mobile, in a storage device that is operatively coupled to the first computer.
4. The wireless communication network of claim 1 , wherein the step of:
storing information includes steps for storing at least one of:
a. an electronic serial number for a wireless subscriber's telephone;
b. a mobile identification number for a wireless subscriber's telephone;
c. services provided to the wireless subscriber by the subscriber's service provider;
d. information that specifies whether the wireless subscriber is provided with call redirecting service;
e. the identity of a mobile switching center, or geographic division thereof, to which calls to the wireless subscriber's number are to be routed by switching systems that are coupled to the switching network.
5. The method of claim 1 wherein the step of storing information in a first computer includes steps of storing in a home location register data base for a switching network, the area code and office code of a switching system, or geographic division thereof, where a call to the wireless subscriber, is to be redirected from.
6. In a wireless communication network, a method of routing a wireless telephone call to a wireless subscriber, comprising the steps of:
storing, in a first computer that is coupled to the communications network, information that identifies at least some services provided to the wireless subscriber by a wireless service provider;
receiving, by the first computer, a first message, the first message including a request for information about the wireless subscriber;
sending, by the first computer, a second message that is a response to the first message that identifies:
a number to which a call to the wireless subscriber is to be redirected; and
subscriber jurisdiction information for the wireless subscriber.
7. The method of claim 6 wherein the step of receiving, by a first computer, a first message, includes the step of receiving said first message from a second computer that is also coupled to the wireless network.
8. The method of claim 6 wherein the step of sending, by the first computer, a second message, includes the step of sending the second message to a second computer that is coupled to the wireless network, said second message identifying a third computer to which a call to the wireless subscriber is to be routed when calls to the wireless subscriber are not to be redirected.
9. The method of claim 6 , wherein the step of storing includes the step of:
storing in the first computer, the identity of a mobile switching center, or geographic division thereof, that has jurisdiction over a geographic coverage area for the wireless subscriber number.
10. The method of claim 6 , wherein the step of storing information includes the step of storing: the identity of the mobile switching center or geographic division thereof, for the home service area of a mobile, in a storage device that is operatively coupled to the first computer, from which a call is to be redirected.
11. The method of claim 6 , wherein the step of storing information includes steps for storing at least one of:
a. an electronic serial number for a wireless subscriber's telephone;
b. a mobile identification number for a wireless subscriber's telephone;
c. services provided to the wireless subscriber by the subscriber's service provider;
d. information that specifies whether the wireless subscriber is provided with call redirecting service;
e. the identity of a mobile switching center, or geographic division thereof, to which calls to the wireless subscriber's number, are to be routed by switching systems that are coupled to the switching network.
12. The method of claim 6 , wherein the step of receiving a first message includes the step of receiving a message that is in the SS7 signaling format.
13. A method of redirecting a call that is placed to a wireless telephone number, to another number, comprising the steps of:
sending a first message by a first computer to a second computer, the first message requesting from the second computer, information about the wireless telephone number;
receiving, by the first computer, a response to the first message that identifies at least, a telephone number to which calls that are placed to the wireless telephone number are to be redirected by a third computer; and
said first computer routing the call placed to the wireless telephone number, to a fourth computer.
14. The method of claim 13 , wherein the step of receiving by the first computer, a response to the first message includes receiving information that also includes at least one of:
a. an identifier for the third computer;
b. the identity of the mobile switching center or geographic division thereof, that has jurisdiction for the mobile;;
c. an electronic serial number of the wireless telephone number; and
d. communications services provided to the wireless telephone number.
15. The method of claim 13 , further comprising the step of:
a. redirecting the call and jurisdiction information received in the response from the second computer to the fourth computer.
16. The method of claim 13 , wherein the step of receiving by the first computer, a response to the first message includes the step of receiving information about the wireless telephone number from a home location register database.
17. A home location register data base system of a wireless communications network comprising:
a processor, operatively coupled to a wireless communications network;
a data storage device, operatively coupled to the processor;
one or more computer-readable signal-bearing media coupled to the processor, the computer-readable signal-bearing media storing program instructions, which when executed enable the processor to:
store information in the data storage device that includes:
at least one second number to which a call to a wireless subscriber number is to be redirected by a switching center for the wireless subscriber number; and
the identity of a mobile switching center, or geographic division thereof, of a wireless communications service provider, to which a call to the wireless subscriber number is to be routed when a call to the non-roaming wireless subscriber is not to be redirected to a second number;
the one or more computer-readable signal-bearing media also storing instructions, which when executed, enable the processor to receive a message from a switching system coupled to the wireless communications network, said message requesting from the processor, at least some of the information stored in the data storage device.
18. The home location register data base system of claim 17 , wherein the one or more computer-readable signal-bearing media further store program instructions, which when executed enable the processor to store additional information in the data storage device that includes at least one of:
a. data that specifies whether call redirecting is provided to a wireless subscriber number;
b. the electronic serial number of a wireless subscriber's telephone; and
c. the identity of the mobile switching center or geographic division thereof, having jurisdiction over the mobile.
19. A gateway mobile switching system of a first wireless communications network comprising:
a processor, operatively coupled to the first wireless communications network;
one or more computer-readable signal-bearing media coupled to the processor, the computer-readable signal-bearing media storing program instructions, which when executed enable the processor to:
receive from a first switch, signaling information for a call that is destined for a mobile telephone number that corresponds to a second mobile switching center within a wireless communications network;
retrieve by a first (gateway) mobile switching center from a data base coupled to the first wireless communications network, data that determines whether the processor is to route the call for the mobile telephone number to a second mobile switching center within the wireless communications network, or redirect the call to a second number through a second switch that is coupled to the wireless communications network; and
retrieve from the data base, information from which the identity of the second mobile switching center, or geographic division thereof, can be determined.
20. The gateway mobile switching system of claim 19 , further including one or more computer-readable signal-bearing media coupled to the processor storing program instructions, which when executed cause the gateway mobile switching system to route the call to the mobile telephone number to a second number through the second switch.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/955,063 US20060068796A1 (en) | 2004-09-30 | 2004-09-30 | Retrieving jurisdiction information from home location register |
US12/655,884 US7953388B2 (en) | 2004-09-30 | 2010-01-07 | Retrieving jurisdiction information from home location register |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/955,063 US20060068796A1 (en) | 2004-09-30 | 2004-09-30 | Retrieving jurisdiction information from home location register |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/655,884 Division US7953388B2 (en) | 2004-09-30 | 2010-01-07 | Retrieving jurisdiction information from home location register |
Publications (1)
Publication Number | Publication Date |
---|---|
US20060068796A1 true US20060068796A1 (en) | 2006-03-30 |
Family
ID=36099911
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/955,063 Abandoned US20060068796A1 (en) | 2004-09-30 | 2004-09-30 | Retrieving jurisdiction information from home location register |
US12/655,884 Expired - Fee Related US7953388B2 (en) | 2004-09-30 | 2010-01-07 | Retrieving jurisdiction information from home location register |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/655,884 Expired - Fee Related US7953388B2 (en) | 2004-09-30 | 2010-01-07 | Retrieving jurisdiction information from home location register |
Country Status (1)
Country | Link |
---|---|
US (2) | US20060068796A1 (en) |
Cited By (54)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100197267A1 (en) * | 2009-01-28 | 2010-08-05 | Headwater Partners I Llc | Device group partitions and settlement platform |
US8547872B2 (en) | 2009-01-28 | 2013-10-01 | Headwater Partners I Llc | Verifiable and accurate service usage monitoring for intermediate networking devices |
US8589541B2 (en) | 2009-01-28 | 2013-11-19 | Headwater Partners I Llc | Device-assisted services for protecting network capacity |
US8606911B2 (en) | 2009-03-02 | 2013-12-10 | Headwater Partners I Llc | Flow tagging for service policy implementation |
US8626115B2 (en) | 2009-01-28 | 2014-01-07 | Headwater Partners I Llc | Wireless network service interfaces |
US8630630B2 (en) | 2009-01-28 | 2014-01-14 | Headwater Partners I Llc | Enhanced roaming services and converged carrier networks with device assisted services and a proxy |
US8634805B2 (en) | 2009-01-28 | 2014-01-21 | Headwater Partners I Llc | Device assisted CDR creation aggregation, mediation and billing |
US8635335B2 (en) | 2009-01-28 | 2014-01-21 | Headwater Partners I Llc | System and method for wireless network offloading |
US8634821B2 (en) | 2009-01-28 | 2014-01-21 | Headwater Partners I Llc | Device assisted services install |
US8725123B2 (en) | 2008-06-05 | 2014-05-13 | Headwater Partners I Llc | Communications device with secure data path processing agents |
US8745220B2 (en) | 2009-01-28 | 2014-06-03 | Headwater Partners I Llc | System and method for providing user notifications |
US8793758B2 (en) | 2009-01-28 | 2014-07-29 | Headwater Partners I Llc | Security, fraud detection, and fraud mitigation in device-assisted services systems |
US8832777B2 (en) | 2009-03-02 | 2014-09-09 | Headwater Partners I Llc | Adapting network policies based on device service processor configuration |
US8868455B2 (en) | 2009-01-28 | 2014-10-21 | Headwater Partners I Llc | Adaptive ambient services |
US8893009B2 (en) | 2009-01-28 | 2014-11-18 | Headwater Partners I Llc | End user device that secures an association of application to service policy with an application certificate check |
US8898293B2 (en) | 2009-01-28 | 2014-11-25 | Headwater Partners I Llc | Service offer set publishing to device agent with on-device service selection |
US8924543B2 (en) | 2009-01-28 | 2014-12-30 | Headwater Partners I Llc | Service design center for device assisted services |
US8924469B2 (en) | 2008-06-05 | 2014-12-30 | Headwater Partners I Llc | Enterprise access control and accounting allocation for access networks |
US9094311B2 (en) | 2009-01-28 | 2015-07-28 | Headwater Partners I, Llc | Techniques for attribution of mobile device data traffic to initiating end-user application |
US9154826B2 (en) | 2011-04-06 | 2015-10-06 | Headwater Partners Ii Llc | Distributing content and service launch objects to mobile devices |
US9198042B2 (en) | 2009-01-28 | 2015-11-24 | Headwater Partners I Llc | Security techniques for device assisted services |
US9247450B2 (en) | 2009-01-28 | 2016-01-26 | Headwater Partners I Llc | Quality of service for device assisted services |
US9253663B2 (en) | 2009-01-28 | 2016-02-02 | Headwater Partners I Llc | Controlling mobile device communications on a roaming network based on device state |
US9351193B2 (en) | 2009-01-28 | 2016-05-24 | Headwater Partners I Llc | Intermediate networking devices |
US9392462B2 (en) | 2009-01-28 | 2016-07-12 | Headwater Partners I Llc | Mobile end-user device with agent limiting wireless data communication for specified background applications based on a stored policy |
US9557889B2 (en) | 2009-01-28 | 2017-01-31 | Headwater Partners I Llc | Service plan design, user interfaces, application programming interfaces, and device management |
US9565707B2 (en) | 2009-01-28 | 2017-02-07 | Headwater Partners I Llc | Wireless end-user device with wireless data attribution to multiple personas |
US9572019B2 (en) | 2009-01-28 | 2017-02-14 | Headwater Partners LLC | Service selection set published to device agent with on-device service selection |
US9578182B2 (en) | 2009-01-28 | 2017-02-21 | Headwater Partners I Llc | Mobile device and service management |
US9647918B2 (en) | 2009-01-28 | 2017-05-09 | Headwater Research Llc | Mobile device and method attributing media services network usage to requesting application |
US9706061B2 (en) | 2009-01-28 | 2017-07-11 | Headwater Partners I Llc | Service design center for device assisted services |
US9755842B2 (en) | 2009-01-28 | 2017-09-05 | Headwater Research Llc | Managing service user discovery and service launch object placement on a device |
US9858559B2 (en) | 2009-01-28 | 2018-01-02 | Headwater Research Llc | Network service plan design |
US9954975B2 (en) | 2009-01-28 | 2018-04-24 | Headwater Research Llc | Enhanced curfew and protection associated with a device group |
US9955332B2 (en) | 2009-01-28 | 2018-04-24 | Headwater Research Llc | Method for child wireless device activation to subscriber account of a master wireless device |
US9980146B2 (en) | 2009-01-28 | 2018-05-22 | Headwater Research Llc | Communications device with secure data path processing agents |
US10057775B2 (en) | 2009-01-28 | 2018-08-21 | Headwater Research Llc | Virtualized policy and charging system |
US10064055B2 (en) | 2009-01-28 | 2018-08-28 | Headwater Research Llc | Security, fraud detection, and fraud mitigation in device-assisted services systems |
US10171995B2 (en) | 2013-03-14 | 2019-01-01 | Headwater Research Llc | Automated credential porting for mobile devices |
US10200541B2 (en) | 2009-01-28 | 2019-02-05 | Headwater Research Llc | Wireless end-user device with divided user space/kernel space traffic policy system |
US10237757B2 (en) | 2009-01-28 | 2019-03-19 | Headwater Research Llc | System and method for wireless network offloading |
US10248996B2 (en) | 2009-01-28 | 2019-04-02 | Headwater Research Llc | Method for operating a wireless end-user device mobile payment agent |
US10264138B2 (en) | 2009-01-28 | 2019-04-16 | Headwater Research Llc | Mobile device and service management |
US10326800B2 (en) | 2009-01-28 | 2019-06-18 | Headwater Research Llc | Wireless network service interfaces |
US10492102B2 (en) | 2009-01-28 | 2019-11-26 | Headwater Research Llc | Intermediate networking devices |
US10715342B2 (en) | 2009-01-28 | 2020-07-14 | Headwater Research Llc | Managing service user discovery and service launch object placement on a device |
US10779177B2 (en) | 2009-01-28 | 2020-09-15 | Headwater Research Llc | Device group partitions and settlement platform |
US10783581B2 (en) | 2009-01-28 | 2020-09-22 | Headwater Research Llc | Wireless end-user device providing ambient or sponsored services |
US10798252B2 (en) | 2009-01-28 | 2020-10-06 | Headwater Research Llc | System and method for providing user notifications |
US10841839B2 (en) | 2009-01-28 | 2020-11-17 | Headwater Research Llc | Security, fraud detection, and fraud mitigation in device-assisted services systems |
US11218854B2 (en) | 2009-01-28 | 2022-01-04 | Headwater Research Llc | Service plan design, user interfaces, application programming interfaces, and device management |
US11412366B2 (en) | 2009-01-28 | 2022-08-09 | Headwater Research Llc | Enhanced roaming services and converged carrier networks with device assisted services and a proxy |
US11973804B2 (en) | 2009-01-28 | 2024-04-30 | Headwater Research Llc | Network service plan design |
US11985155B2 (en) | 2009-01-28 | 2024-05-14 | Headwater Research Llc | Communications device with secure data path processing agents |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11349986B2 (en) | 2020-10-27 | 2022-05-31 | T-Mobile Usa, Inc. | Customization of call forwarding or voicemail greetings based on location of wireless device |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5504804A (en) * | 1994-01-19 | 1996-04-02 | Telefonaktiebolaget Lm Ericsson | Providing individual subscriber services in a cellular mobile communications network |
US5771275A (en) * | 1996-12-17 | 1998-06-23 | Telefonaktiebolaget Lm Ericsson | Use of ISDN to provide wireless office environment connection to the public land mobile network |
US5854982A (en) * | 1995-08-21 | 1998-12-29 | Motorola, Inc. | Communication system architecture and method of routing therefor |
US6370390B1 (en) * | 1997-04-03 | 2002-04-09 | Nokia Telecommunications Oy | Delivery of short messages in a packet radio network |
US20020167906A1 (en) * | 2001-03-19 | 2002-11-14 | La Porta Thomas F. | Multiple-protocol home location register and method of use |
US6978134B1 (en) * | 1998-12-21 | 2005-12-20 | Nokia Corporation | Call routing |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
BR0111535A (en) * | 2000-06-09 | 2003-09-16 | Cellular Roaming Alliance Pty | Method and apparatus for enabling a mobile station from a home network to operate on a visited network |
-
2004
- 2004-09-30 US US10/955,063 patent/US20060068796A1/en not_active Abandoned
-
2010
- 2010-01-07 US US12/655,884 patent/US7953388B2/en not_active Expired - Fee Related
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5504804A (en) * | 1994-01-19 | 1996-04-02 | Telefonaktiebolaget Lm Ericsson | Providing individual subscriber services in a cellular mobile communications network |
US5854982A (en) * | 1995-08-21 | 1998-12-29 | Motorola, Inc. | Communication system architecture and method of routing therefor |
US5771275A (en) * | 1996-12-17 | 1998-06-23 | Telefonaktiebolaget Lm Ericsson | Use of ISDN to provide wireless office environment connection to the public land mobile network |
US6370390B1 (en) * | 1997-04-03 | 2002-04-09 | Nokia Telecommunications Oy | Delivery of short messages in a packet radio network |
US6978134B1 (en) * | 1998-12-21 | 2005-12-20 | Nokia Corporation | Call routing |
US20020167906A1 (en) * | 2001-03-19 | 2002-11-14 | La Porta Thomas F. | Multiple-protocol home location register and method of use |
Cited By (202)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8725123B2 (en) | 2008-06-05 | 2014-05-13 | Headwater Partners I Llc | Communications device with secure data path processing agents |
US8924469B2 (en) | 2008-06-05 | 2014-12-30 | Headwater Partners I Llc | Enterprise access control and accounting allocation for access networks |
US9591474B2 (en) | 2009-01-28 | 2017-03-07 | Headwater Partners I Llc | Adapting network policies based on device service processor configuration |
US8635678B2 (en) | 2009-01-28 | 2014-01-21 | Headwater Partners I Llc | Automated device provisioning and activation |
US8548428B2 (en) | 2009-01-28 | 2013-10-01 | Headwater Partners I Llc | Device group partitions and settlement platform |
US8570908B2 (en) | 2009-01-28 | 2013-10-29 | Headwater Partners I Llc | Automated device provisioning and activation |
US8583781B2 (en) | 2009-01-28 | 2013-11-12 | Headwater Partners I Llc | Simplified service network architecture |
US8588110B2 (en) | 2009-01-28 | 2013-11-19 | Headwater Partners I Llc | Verifiable device assisted service usage billing with integrated accounting, mediation accounting, and multi-account |
US8589541B2 (en) | 2009-01-28 | 2013-11-19 | Headwater Partners I Llc | Device-assisted services for protecting network capacity |
US8626115B2 (en) | 2009-01-28 | 2014-01-07 | Headwater Partners I Llc | Wireless network service interfaces |
US8630611B2 (en) | 2009-01-28 | 2014-01-14 | Headwater Partners I Llc | Automated device provisioning and activation |
US8631102B2 (en) | 2009-01-28 | 2014-01-14 | Headwater Partners I Llc | Automated device provisioning and activation |
US8630617B2 (en) | 2009-01-28 | 2014-01-14 | Headwater Partners I Llc | Device group partitions and settlement platform |
US8630630B2 (en) | 2009-01-28 | 2014-01-14 | Headwater Partners I Llc | Enhanced roaming services and converged carrier networks with device assisted services and a proxy |
US8630192B2 (en) | 2009-01-28 | 2014-01-14 | Headwater Partners I Llc | Verifiable and accurate service usage monitoring for intermediate networking devices |
US9609544B2 (en) | 2009-01-28 | 2017-03-28 | Headwater Research Llc | Device-assisted services for protecting network capacity |
US8634805B2 (en) | 2009-01-28 | 2014-01-21 | Headwater Partners I Llc | Device assisted CDR creation aggregation, mediation and billing |
US8635335B2 (en) | 2009-01-28 | 2014-01-21 | Headwater Partners I Llc | System and method for wireless network offloading |
US8634821B2 (en) | 2009-01-28 | 2014-01-21 | Headwater Partners I Llc | Device assisted services install |
US8640198B2 (en) | 2009-01-28 | 2014-01-28 | Headwater Partners I Llc | Automated device provisioning and activation |
US8639935B2 (en) | 2009-01-28 | 2014-01-28 | Headwater Partners I Llc | Automated device provisioning and activation |
US8639811B2 (en) | 2009-01-28 | 2014-01-28 | Headwater Partners I Llc | Automated device provisioning and activation |
US8666364B2 (en) | 2009-01-28 | 2014-03-04 | Headwater Partners I Llc | Verifiable device assisted service usage billing with integrated accounting, mediation accounting, and multi-account |
US8667571B2 (en) | 2009-01-28 | 2014-03-04 | Headwater Partners I Llc | Automated device provisioning and activation |
US8675507B2 (en) | 2009-01-28 | 2014-03-18 | Headwater Partners I Llc | Service profile management with user preference, adaptive policy, network neutrality and user privacy for intermediate networking devices |
US8688099B2 (en) | 2009-01-28 | 2014-04-01 | Headwater Partners I Llc | Open development system for access service providers |
US8695073B2 (en) | 2009-01-28 | 2014-04-08 | Headwater Partners I Llc | Automated device provisioning and activation |
US8713630B2 (en) | 2009-01-28 | 2014-04-29 | Headwater Partners I Llc | Verifiable service policy implementation for intermediate networking devices |
US8724554B2 (en) | 2009-01-28 | 2014-05-13 | Headwater Partners I Llc | Open transaction central billing system |
US8737957B2 (en) | 2009-01-28 | 2014-05-27 | Headwater Partners I Llc | Automated device provisioning and activation |
US8745220B2 (en) | 2009-01-28 | 2014-06-03 | Headwater Partners I Llc | System and method for providing user notifications |
US8745191B2 (en) | 2009-01-28 | 2014-06-03 | Headwater Partners I Llc | System and method for providing user notifications |
US8788661B2 (en) | 2009-01-28 | 2014-07-22 | Headwater Partners I Llc | Device assisted CDR creation, aggregation, mediation and billing |
US8793758B2 (en) | 2009-01-28 | 2014-07-29 | Headwater Partners I Llc | Security, fraud detection, and fraud mitigation in device-assisted services systems |
US8797908B2 (en) | 2009-01-28 | 2014-08-05 | Headwater Partners I Llc | Automated device provisioning and activation |
US8799451B2 (en) | 2009-01-28 | 2014-08-05 | Headwater Partners I Llc | Verifiable service policy implementation for intermediate networking devices |
US8839387B2 (en) | 2009-01-28 | 2014-09-16 | Headwater Partners I Llc | Roaming services network and overlay networks |
US8839388B2 (en) | 2009-01-28 | 2014-09-16 | Headwater Partners I Llc | Automated device provisioning and activation |
US8868455B2 (en) | 2009-01-28 | 2014-10-21 | Headwater Partners I Llc | Adaptive ambient services |
US8886162B2 (en) | 2009-01-28 | 2014-11-11 | Headwater Partners I Llc | Restricting end-user device communications over a wireless access network associated with a cost |
US8893009B2 (en) | 2009-01-28 | 2014-11-18 | Headwater Partners I Llc | End user device that secures an association of application to service policy with an application certificate check |
US8898293B2 (en) | 2009-01-28 | 2014-11-25 | Headwater Partners I Llc | Service offer set publishing to device agent with on-device service selection |
US8897743B2 (en) | 2009-01-28 | 2014-11-25 | Headwater Partners I Llc | Verifiable device assisted service usage billing with integrated accounting, mediation accounting, and multi-account |
US8898079B2 (en) | 2009-01-28 | 2014-11-25 | Headwater Partners I Llc | Network based ambient services |
US8897744B2 (en) | 2009-01-28 | 2014-11-25 | Headwater Partners I Llc | Device assisted ambient services |
US8903452B2 (en) | 2009-01-28 | 2014-12-02 | Headwater Partners I Llc | Device assisted ambient services |
US8924549B2 (en) | 2009-01-28 | 2014-12-30 | Headwater Partners I Llc | Network based ambient services |
US8924543B2 (en) | 2009-01-28 | 2014-12-30 | Headwater Partners I Llc | Service design center for device assisted services |
US8948025B2 (en) | 2009-01-28 | 2015-02-03 | Headwater Partners I Llc | Remotely configurable device agent for packet routing |
US9014026B2 (en) | 2009-01-28 | 2015-04-21 | Headwater Partners I Llc | Network based service profile management with user preference, adaptive policy, network neutrality, and user privacy |
US9026079B2 (en) | 2009-01-28 | 2015-05-05 | Headwater Partners I Llc | Wireless network service interfaces |
US9037127B2 (en) | 2009-01-28 | 2015-05-19 | Headwater Partners I Llc | Device agent for remote user configuration of wireless network access |
US9094311B2 (en) | 2009-01-28 | 2015-07-28 | Headwater Partners I, Llc | Techniques for attribution of mobile device data traffic to initiating end-user application |
US9137701B2 (en) | 2009-01-28 | 2015-09-15 | Headwater Partners I Llc | Wireless end-user device with differentiated network access for background and foreground device applications |
US9137739B2 (en) | 2009-01-28 | 2015-09-15 | Headwater Partners I Llc | Network based service policy implementation with network neutrality and user privacy |
US9143976B2 (en) | 2009-01-28 | 2015-09-22 | Headwater Partners I Llc | Wireless end-user device with differentiated network access and access status for background and foreground device applications |
US12101434B2 (en) | 2009-01-28 | 2024-09-24 | Headwater Research Llc | Device assisted CDR creation, aggregation, mediation and billing |
US11985155B2 (en) | 2009-01-28 | 2024-05-14 | Headwater Research Llc | Communications device with secure data path processing agents |
US11973804B2 (en) | 2009-01-28 | 2024-04-30 | Headwater Research Llc | Network service plan design |
US9154428B2 (en) | 2009-01-28 | 2015-10-06 | Headwater Partners I Llc | Wireless end-user device with differentiated network access selectively applied to different applications |
US9173104B2 (en) | 2009-01-28 | 2015-10-27 | Headwater Partners I Llc | Mobile device with device agents to detect a disallowed access to a requested mobile data service and guide a multi-carrier selection and activation sequence |
US9179308B2 (en) | 2009-01-28 | 2015-11-03 | Headwater Partners I Llc | Network tools for analysis, design, testing, and production of services |
US9179359B2 (en) | 2009-01-28 | 2015-11-03 | Headwater Partners I Llc | Wireless end-user device with differentiated network access status for different device applications |
US9179316B2 (en) | 2009-01-28 | 2015-11-03 | Headwater Partners I Llc | Mobile device with user controls and policy agent to control application access to device location data |
US9179315B2 (en) | 2009-01-28 | 2015-11-03 | Headwater Partners I Llc | Mobile device with data service monitoring, categorization, and display for different applications and networks |
US9198075B2 (en) | 2009-01-28 | 2015-11-24 | Headwater Partners I Llc | Wireless end-user device with differential traffic control policy list applicable to one of several wireless modems |
US9198117B2 (en) | 2009-01-28 | 2015-11-24 | Headwater Partners I Llc | Network system with common secure wireless message service serving multiple applications on multiple wireless devices |
US9198042B2 (en) | 2009-01-28 | 2015-11-24 | Headwater Partners I Llc | Security techniques for device assisted services |
US9198076B2 (en) | 2009-01-28 | 2015-11-24 | Headwater Partners I Llc | Wireless end-user device with power-control-state-based wireless network access policy for background applications |
US9198074B2 (en) | 2009-01-28 | 2015-11-24 | Headwater Partners I Llc | Wireless end-user device with differential traffic control policy list and applying foreground classification to roaming wireless data service |
US9204282B2 (en) | 2009-01-28 | 2015-12-01 | Headwater Partners I Llc | Enhanced roaming services and converged carrier networks with device assisted services and a proxy |
US9204374B2 (en) | 2009-01-28 | 2015-12-01 | Headwater Partners I Llc | Multicarrier over-the-air cellular network activation server |
US9215613B2 (en) | 2009-01-28 | 2015-12-15 | Headwater Partners I Llc | Wireless end-user device with differential traffic control policy list having limited user control |
US9215159B2 (en) | 2009-01-28 | 2015-12-15 | Headwater Partners I Llc | Data usage monitoring for media data services used by applications |
US9220027B1 (en) | 2009-01-28 | 2015-12-22 | Headwater Partners I Llc | Wireless end-user device with policy-based controls for WWAN network usage and modem state changes requested by specific applications |
US9225797B2 (en) | 2009-01-28 | 2015-12-29 | Headwater Partners I Llc | System for providing an adaptive wireless ambient service to a mobile device |
US9232403B2 (en) | 2009-01-28 | 2016-01-05 | Headwater Partners I Llc | Mobile device with common secure wireless message service serving multiple applications |
US9247450B2 (en) | 2009-01-28 | 2016-01-26 | Headwater Partners I Llc | Quality of service for device assisted services |
US9253663B2 (en) | 2009-01-28 | 2016-02-02 | Headwater Partners I Llc | Controlling mobile device communications on a roaming network based on device state |
US9258735B2 (en) | 2009-01-28 | 2016-02-09 | Headwater Partners I Llc | Device-assisted services for protecting network capacity |
US9271184B2 (en) | 2009-01-28 | 2016-02-23 | Headwater Partners I Llc | Wireless end-user device with per-application data limit and traffic control policy list limiting background application traffic |
US9270559B2 (en) | 2009-01-28 | 2016-02-23 | Headwater Partners I Llc | Service policy implementation for an end-user device having a control application or a proxy agent for routing an application traffic flow |
US9277433B2 (en) | 2009-01-28 | 2016-03-01 | Headwater Partners I Llc | Wireless end-user device with policy-based aggregation of network activity requested by applications |
US9277445B2 (en) | 2009-01-28 | 2016-03-01 | Headwater Partners I Llc | Wireless end-user device with differential traffic control policy list and applying foreground classification to wireless data service |
US9319913B2 (en) | 2009-01-28 | 2016-04-19 | Headwater Partners I Llc | Wireless end-user device with secure network-provided differential traffic control policy list |
US9351193B2 (en) | 2009-01-28 | 2016-05-24 | Headwater Partners I Llc | Intermediate networking devices |
US9386121B2 (en) | 2009-01-28 | 2016-07-05 | Headwater Partners I Llc | Method for providing an adaptive wireless ambient service to a mobile device |
US9386165B2 (en) | 2009-01-28 | 2016-07-05 | Headwater Partners I Llc | System and method for providing user notifications |
US9392462B2 (en) | 2009-01-28 | 2016-07-12 | Headwater Partners I Llc | Mobile end-user device with agent limiting wireless data communication for specified background applications based on a stored policy |
US9491564B1 (en) | 2009-01-28 | 2016-11-08 | Headwater Partners I Llc | Mobile device and method with secure network messaging for authorized components |
US9491199B2 (en) | 2009-01-28 | 2016-11-08 | Headwater Partners I Llc | Security, fraud detection, and fraud mitigation in device-assisted services systems |
US9521578B2 (en) | 2009-01-28 | 2016-12-13 | Headwater Partners I Llc | Wireless end-user device with application program interface to allow applications to access application-specific aspects of a wireless network access policy |
US9532261B2 (en) | 2009-01-28 | 2016-12-27 | Headwater Partners I Llc | System and method for wireless network offloading |
US9532161B2 (en) | 2009-01-28 | 2016-12-27 | Headwater Partners I Llc | Wireless device with application data flow tagging and network stack-implemented network access policy |
US9544397B2 (en) | 2009-01-28 | 2017-01-10 | Headwater Partners I Llc | Proxy server for providing an adaptive wireless ambient service to a mobile device |
US9557889B2 (en) | 2009-01-28 | 2017-01-31 | Headwater Partners I Llc | Service plan design, user interfaces, application programming interfaces, and device management |
US9565543B2 (en) | 2009-01-28 | 2017-02-07 | Headwater Partners I Llc | Device group partitions and settlement platform |
US9565707B2 (en) | 2009-01-28 | 2017-02-07 | Headwater Partners I Llc | Wireless end-user device with wireless data attribution to multiple personas |
US9572019B2 (en) | 2009-01-28 | 2017-02-14 | Headwater Partners LLC | Service selection set published to device agent with on-device service selection |
US9578182B2 (en) | 2009-01-28 | 2017-02-21 | Headwater Partners I Llc | Mobile device and service management |
US11219074B2 (en) | 2009-01-28 | 2022-01-04 | Headwater Research Llc | Enterprise access control and accounting allocation for access networks |
US8547872B2 (en) | 2009-01-28 | 2013-10-01 | Headwater Partners I Llc | Verifiable and accurate service usage monitoring for intermediate networking devices |
US11477246B2 (en) | 2009-01-28 | 2022-10-18 | Headwater Research Llc | Network service plan design |
US9615192B2 (en) | 2009-01-28 | 2017-04-04 | Headwater Research Llc | Message link server with plural message delivery triggers |
US9641957B2 (en) | 2009-01-28 | 2017-05-02 | Headwater Research Llc | Automated device provisioning and activation |
US9647918B2 (en) | 2009-01-28 | 2017-05-09 | Headwater Research Llc | Mobile device and method attributing media services network usage to requesting application |
US9674731B2 (en) | 2009-01-28 | 2017-06-06 | Headwater Research Llc | Wireless device applying different background data traffic policies to different device applications |
US9705771B2 (en) | 2009-01-28 | 2017-07-11 | Headwater Partners I Llc | Attribution of mobile device data traffic to end-user application based on socket flows |
US9706061B2 (en) | 2009-01-28 | 2017-07-11 | Headwater Partners I Llc | Service design center for device assisted services |
US9749899B2 (en) | 2009-01-28 | 2017-08-29 | Headwater Research Llc | Wireless end-user device with network traffic API to indicate unavailability of roaming wireless connection to background applications |
US9749898B2 (en) | 2009-01-28 | 2017-08-29 | Headwater Research Llc | Wireless end-user device with differential traffic control policy list applicable to one of several wireless modems |
US9755842B2 (en) | 2009-01-28 | 2017-09-05 | Headwater Research Llc | Managing service user discovery and service launch object placement on a device |
US9769207B2 (en) | 2009-01-28 | 2017-09-19 | Headwater Research Llc | Wireless network service interfaces |
US9819808B2 (en) | 2009-01-28 | 2017-11-14 | Headwater Research Llc | Hierarchical service policies for creating service usage data records for a wireless end-user device |
US9858559B2 (en) | 2009-01-28 | 2018-01-02 | Headwater Research Llc | Network service plan design |
US9866642B2 (en) | 2009-01-28 | 2018-01-09 | Headwater Research Llc | Wireless end-user device with wireless modem power state control policy for background applications |
US9942796B2 (en) | 2009-01-28 | 2018-04-10 | Headwater Research Llc | Quality of service for device assisted services |
US9954975B2 (en) | 2009-01-28 | 2018-04-24 | Headwater Research Llc | Enhanced curfew and protection associated with a device group |
US9955332B2 (en) | 2009-01-28 | 2018-04-24 | Headwater Research Llc | Method for child wireless device activation to subscriber account of a master wireless device |
US9973930B2 (en) | 2009-01-28 | 2018-05-15 | Headwater Research Llc | End user device that secures an association of application to service policy with an application certificate check |
US9980146B2 (en) | 2009-01-28 | 2018-05-22 | Headwater Research Llc | Communications device with secure data path processing agents |
US10028144B2 (en) | 2009-01-28 | 2018-07-17 | Headwater Research Llc | Security techniques for device assisted services |
US10057141B2 (en) | 2009-01-28 | 2018-08-21 | Headwater Research Llc | Proxy system and method for adaptive ambient services |
US10057775B2 (en) | 2009-01-28 | 2018-08-21 | Headwater Research Llc | Virtualized policy and charging system |
US10064033B2 (en) | 2009-01-28 | 2018-08-28 | Headwater Research Llc | Device group partitions and settlement platform |
US10064055B2 (en) | 2009-01-28 | 2018-08-28 | Headwater Research Llc | Security, fraud detection, and fraud mitigation in device-assisted services systems |
US10070305B2 (en) | 2009-01-28 | 2018-09-04 | Headwater Research Llc | Device assisted services install |
US10080250B2 (en) | 2009-01-28 | 2018-09-18 | Headwater Research Llc | Enterprise access control and accounting allocation for access networks |
US10165447B2 (en) | 2009-01-28 | 2018-12-25 | Headwater Research Llc | Network service plan design |
US10171988B2 (en) | 2009-01-28 | 2019-01-01 | Headwater Research Llc | Adapting network policies based on device service processor configuration |
US10171990B2 (en) | 2009-01-28 | 2019-01-01 | Headwater Research Llc | Service selection set publishing to device agent with on-device service selection |
US10171681B2 (en) | 2009-01-28 | 2019-01-01 | Headwater Research Llc | Service design center for device assisted services |
US11968234B2 (en) | 2009-01-28 | 2024-04-23 | Headwater Research Llc | Wireless network service interfaces |
US10200541B2 (en) | 2009-01-28 | 2019-02-05 | Headwater Research Llc | Wireless end-user device with divided user space/kernel space traffic policy system |
US10237757B2 (en) | 2009-01-28 | 2019-03-19 | Headwater Research Llc | System and method for wireless network offloading |
US10237146B2 (en) | 2009-01-28 | 2019-03-19 | Headwater Research Llc | Adaptive ambient services |
US10237773B2 (en) | 2009-01-28 | 2019-03-19 | Headwater Research Llc | Device-assisted services for protecting network capacity |
US10248996B2 (en) | 2009-01-28 | 2019-04-02 | Headwater Research Llc | Method for operating a wireless end-user device mobile payment agent |
US10264138B2 (en) | 2009-01-28 | 2019-04-16 | Headwater Research Llc | Mobile device and service management |
US10321320B2 (en) | 2009-01-28 | 2019-06-11 | Headwater Research Llc | Wireless network buffered message system |
US10320990B2 (en) | 2009-01-28 | 2019-06-11 | Headwater Research Llc | Device assisted CDR creation, aggregation, mediation and billing |
US10326675B2 (en) | 2009-01-28 | 2019-06-18 | Headwater Research Llc | Flow tagging for service policy implementation |
US10326800B2 (en) | 2009-01-28 | 2019-06-18 | Headwater Research Llc | Wireless network service interfaces |
US10462627B2 (en) | 2009-01-28 | 2019-10-29 | Headwater Research Llc | Service plan design, user interfaces, application programming interfaces, and device management |
US10492102B2 (en) | 2009-01-28 | 2019-11-26 | Headwater Research Llc | Intermediate networking devices |
US10536983B2 (en) | 2009-01-28 | 2020-01-14 | Headwater Research Llc | Enterprise access control and accounting allocation for access networks |
US10582375B2 (en) | 2009-01-28 | 2020-03-03 | Headwater Research Llc | Device assisted services install |
US10681179B2 (en) | 2009-01-28 | 2020-06-09 | Headwater Research Llc | Enhanced curfew and protection associated with a device group |
US10694385B2 (en) | 2009-01-28 | 2020-06-23 | Headwater Research Llc | Security techniques for device assisted services |
US10715342B2 (en) | 2009-01-28 | 2020-07-14 | Headwater Research Llc | Managing service user discovery and service launch object placement on a device |
US10716006B2 (en) | 2009-01-28 | 2020-07-14 | Headwater Research Llc | End user device that secures an association of application to service policy with an application certificate check |
US10749700B2 (en) | 2009-01-28 | 2020-08-18 | Headwater Research Llc | Device-assisted services for protecting network capacity |
US10771980B2 (en) | 2009-01-28 | 2020-09-08 | Headwater Research Llc | Communications device with secure data path processing agents |
US10779177B2 (en) | 2009-01-28 | 2020-09-15 | Headwater Research Llc | Device group partitions and settlement platform |
US10783581B2 (en) | 2009-01-28 | 2020-09-22 | Headwater Research Llc | Wireless end-user device providing ambient or sponsored services |
US10791471B2 (en) | 2009-01-28 | 2020-09-29 | Headwater Research Llc | System and method for wireless network offloading |
US10798254B2 (en) | 2009-01-28 | 2020-10-06 | Headwater Research Llc | Service design center for device assisted services |
US10798558B2 (en) | 2009-01-28 | 2020-10-06 | Headwater Research Llc | Adapting network policies based on device service processor configuration |
US10798252B2 (en) | 2009-01-28 | 2020-10-06 | Headwater Research Llc | System and method for providing user notifications |
US10803518B2 (en) | 2009-01-28 | 2020-10-13 | Headwater Research Llc | Virtualized policy and charging system |
US11966464B2 (en) | 2009-01-28 | 2024-04-23 | Headwater Research Llc | Security techniques for device assisted services |
US10834577B2 (en) | 2009-01-28 | 2020-11-10 | Headwater Research Llc | Service offer set publishing to device agent with on-device service selection |
US10841839B2 (en) | 2009-01-28 | 2020-11-17 | Headwater Research Llc | Security, fraud detection, and fraud mitigation in device-assisted services systems |
US10848330B2 (en) | 2009-01-28 | 2020-11-24 | Headwater Research Llc | Device-assisted services for protecting network capacity |
US10855559B2 (en) | 2009-01-28 | 2020-12-01 | Headwater Research Llc | Adaptive ambient services |
US10869199B2 (en) | 2009-01-28 | 2020-12-15 | Headwater Research Llc | Network service plan design |
US10985977B2 (en) | 2009-01-28 | 2021-04-20 | Headwater Research Llc | Quality of service for device assisted services |
US11039020B2 (en) | 2009-01-28 | 2021-06-15 | Headwater Research Llc | Mobile device and service management |
US11096055B2 (en) | 2009-01-28 | 2021-08-17 | Headwater Research Llc | Automated device provisioning and activation |
US11134102B2 (en) | 2009-01-28 | 2021-09-28 | Headwater Research Llc | Verifiable device assisted service usage monitoring with reporting, synchronization, and notification |
US11190545B2 (en) | 2009-01-28 | 2021-11-30 | Headwater Research Llc | Wireless network service interfaces |
US11190645B2 (en) | 2009-01-28 | 2021-11-30 | Headwater Research Llc | Device assisted CDR creation, aggregation, mediation and billing |
US11190427B2 (en) | 2009-01-28 | 2021-11-30 | Headwater Research Llc | Flow tagging for service policy implementation |
US11218854B2 (en) | 2009-01-28 | 2022-01-04 | Headwater Research Llc | Service plan design, user interfaces, application programming interfaces, and device management |
US20100197267A1 (en) * | 2009-01-28 | 2010-08-05 | Headwater Partners I Llc | Device group partitions and settlement platform |
US11228617B2 (en) | 2009-01-28 | 2022-01-18 | Headwater Research Llc | Automated device provisioning and activation |
US11337059B2 (en) | 2009-01-28 | 2022-05-17 | Headwater Research Llc | Device assisted services install |
US11363496B2 (en) | 2009-01-28 | 2022-06-14 | Headwater Research Llc | Intermediate networking devices |
US11405224B2 (en) | 2009-01-28 | 2022-08-02 | Headwater Research Llc | Device-assisted services for protecting network capacity |
US11405429B2 (en) | 2009-01-28 | 2022-08-02 | Headwater Research Llc | Security techniques for device assisted services |
US11412366B2 (en) | 2009-01-28 | 2022-08-09 | Headwater Research Llc | Enhanced roaming services and converged carrier networks with device assisted services and a proxy |
US11425580B2 (en) | 2009-01-28 | 2022-08-23 | Headwater Research Llc | System and method for wireless network offloading |
US9609459B2 (en) | 2009-01-28 | 2017-03-28 | Headwater Research Llc | Network tools for analysis, design, testing, and production of services |
US11494837B2 (en) | 2009-01-28 | 2022-11-08 | Headwater Research Llc | Virtualized policy and charging system |
US11516301B2 (en) | 2009-01-28 | 2022-11-29 | Headwater Research Llc | Enhanced curfew and protection associated with a device group |
US11533642B2 (en) | 2009-01-28 | 2022-12-20 | Headwater Research Llc | Device group partitions and settlement platform |
US11538106B2 (en) | 2009-01-28 | 2022-12-27 | Headwater Research Llc | Wireless end-user device providing ambient or sponsored services |
US11563592B2 (en) | 2009-01-28 | 2023-01-24 | Headwater Research Llc | Managing service user discovery and service launch object placement on a device |
US11570309B2 (en) | 2009-01-28 | 2023-01-31 | Headwater Research Llc | Service design center for device assisted services |
US11582593B2 (en) | 2009-01-28 | 2023-02-14 | Head Water Research Llc | Adapting network policies based on device service processor configuration |
US11589216B2 (en) | 2009-01-28 | 2023-02-21 | Headwater Research Llc | Service selection set publishing to device agent with on-device service selection |
US11665592B2 (en) | 2009-01-28 | 2023-05-30 | Headwater Research Llc | Security, fraud detection, and fraud mitigation in device-assisted services systems |
US11665186B2 (en) | 2009-01-28 | 2023-05-30 | Headwater Research Llc | Communications device with secure data path processing agents |
US11923995B2 (en) | 2009-01-28 | 2024-03-05 | Headwater Research Llc | Device-assisted services for protecting network capacity |
US11750477B2 (en) | 2009-01-28 | 2023-09-05 | Headwater Research Llc | Adaptive ambient services |
US11757943B2 (en) | 2009-01-28 | 2023-09-12 | Headwater Research Llc | Automated device provisioning and activation |
US8832777B2 (en) | 2009-03-02 | 2014-09-09 | Headwater Partners I Llc | Adapting network policies based on device service processor configuration |
US8606911B2 (en) | 2009-03-02 | 2013-12-10 | Headwater Partners I Llc | Flow tagging for service policy implementation |
US9154826B2 (en) | 2011-04-06 | 2015-10-06 | Headwater Partners Ii Llc | Distributing content and service launch objects to mobile devices |
US11743717B2 (en) | 2013-03-14 | 2023-08-29 | Headwater Research Llc | Automated credential porting for mobile devices |
US10834583B2 (en) | 2013-03-14 | 2020-11-10 | Headwater Research Llc | Automated credential porting for mobile devices |
US10171995B2 (en) | 2013-03-14 | 2019-01-01 | Headwater Research Llc | Automated credential porting for mobile devices |
Also Published As
Publication number | Publication date |
---|---|
US7953388B2 (en) | 2011-05-31 |
US20100112977A1 (en) | 2010-05-06 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7953388B2 (en) | Retrieving jurisdiction information from home location register | |
US6356756B1 (en) | Method and system for routing calls to a wireless telecommunications services platform | |
US6700972B1 (en) | System and method for processing and collecting data from a call directed to a call center | |
US7454197B2 (en) | System and method for routing a call to a landline communication unit or a wireless communication unit | |
CN1498029B (en) | Emergency call-back method | |
CA2143146C (en) | System for routing calls to mobile subscribers | |
US7853002B2 (en) | Number portability service in a telecommunication system | |
US7894814B2 (en) | Integrated wireless/wireline registration | |
US8983050B2 (en) | Handling of forwarded calls | |
CN101341764A (en) | Service of intelligent network | |
US8548152B2 (en) | System and method for handling toll free number telephone calls | |
US6633755B1 (en) | Method and nodes for routing a call in a mobile telecommunication network | |
US20080064409A1 (en) | Wireless direct routing system | |
US6944445B2 (en) | Homezone call forwarding service method | |
AU4352397A (en) | Using number portability database to solve call tromboning | |
EP1832126B1 (en) | Methods and apparatus to perform wireless peering in communication systems | |
US20050249343A1 (en) | Method for conveniently adding contact information to a network-based address book | |
US7107047B2 (en) | Employment of established telephone number of mobile device supported by serving mobile switching center to connect a call to the mobile device | |
US7903799B1 (en) | Method and apparatus for providing a communications service feature for a communication through a network | |
US20100075646A1 (en) | Method for terminating to a mobile network a call directed to a fixed network number | |
KR20020021235A (en) | Information Search Method Between Network Element In Wireless Intelligent Network | |
CN101835291A (en) | The intelligent network service |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: LUCENT TECHNOLOGIES INC., NEW JERSEY Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:MILLEN, STEPHANIE L.;VAN LEEUWEN, MARTIN H.;REEL/FRAME:015862/0621 Effective date: 20040930 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO PAY ISSUE FEE |