US20010040958A1 - Extended number portability database services - Google Patents

Extended number portability database services Download PDF

Info

Publication number
US20010040958A1
US20010040958A1 US09/908,813 US90881301A US2001040958A1 US 20010040958 A1 US20010040958 A1 US 20010040958A1 US 90881301 A US90881301 A US 90881301A US 2001040958 A1 US2001040958 A1 US 2001040958A1
Authority
US
United States
Prior art keywords
domain
call
database
address
subscriber
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
Application number
US09/908,813
Inventor
Lila Madour
Shabnam Sultana
Original Assignee
Lila Madour
Shabnam Sultana
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to US09/221,165 priority Critical patent/US6266405B1/en
Application filed by Lila Madour, Shabnam Sultana filed Critical Lila Madour
Priority to US09/908,813 priority patent/US20010040958A1/en
Publication of US20010040958A1 publication Critical patent/US20010040958A1/en
Application status is Abandoned legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04QSELECTING
    • H04Q3/00Selecting arrangements
    • H04Q3/0016Arrangements providing connection between exchanges
    • H04Q3/0029Provisions for intelligent networking
    • H04Q3/005Personal communications services, e.g. provisions for portability of subscriber numbers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L29/00Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00
    • H04L29/02Communication control; Communication processing
    • H04L29/06Communication control; Communication processing characterised by a protocol
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L29/00Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00
    • H04L29/12Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 characterised by the data terminal
    • H04L29/12009Arrangements for addressing and naming in data networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L29/00Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00
    • H04L29/12Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 characterised by the data terminal
    • H04L29/12009Arrangements for addressing and naming in data networks
    • H04L29/12047Directories; name-to-address mapping
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements or network protocols for addressing or naming
    • H04L61/15Directories; Name-to-address mapping
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S379/00Telephonic communications
    • Y10S379/90Internet, e.g. Internet phone, webphone, internet-based telephony

Abstract

A system and method for providing portability of internet addressing maintains additional IP addressing information in number portability databases located throughout provider domains in a telecommunications network. This additional IP addressing information, in conjunction with additional Number Portability Request messaging information, permits portability of addresses across telecommunication and data communication networks in a transparent fashion.

Description

    BACKGROUND
  • Applicants' invention relates generally to number portability in telecommunications systems and, more particularly, to techniques for providing number portability towards Internet service providers. [0001]
  • Number portability in telecommunication systems typically permits end users (i.e., mobile subscribers) to retain the same telephone numbers whenever the end users change from one telecommunication service provider/operator domain to another telecommunication service provider/operator domain. Without number portability, service providers will be unable to accommodate the relocation of a mobile subscriber from one service provider to another without changing the subscriber's directory telephone number. [0002]
  • Changing a directory telephone number in the event of relocation of a subscriber occasions expense and effort for both the subscriber and the telecommunications provider. For the provider, it is an expensive process to administer the changes of directory telephone numbers when a subscriber relocates from one area to another. The administration required by the provider includes both efforts to define available new numbers in the new location and to update the existing directory. The relocated subscriber also incurs expense in providing notice of the new directory number to potential callers (friends and business contacts). If such notice is not provided or retained by the potential callers, calls may not be placed to the relocated subscriber. Loss of calls to a relocated subscriber can result in loss of social or business opportunity. Thus, number portability is advantageous in that it permits relocated mobile subscribers, who have changed service providers, to receive calls that otherwise might be directed to the wrong service provider and therefore would be lost. [0003]
  • For an understanding of number portability, a conventional telecommunications network [0004] 10 is shown in FIG. 1 and is described below. Network 10 includes a set of service provider domains 20A-20C and 20F. Three of the domains (particularly domains 20A-20C) are mobile telecommunications domains serving mobile stations; domain 20F serves fixed stations. In the illustrated network, domain 20F can be of a network type such as a public switched network (PSTN) or integrated services digital network (ISDN), for example. At least some of the areas served by domains 20 can be, and likely are, geographically coextensive. Some of the domains 20 may also be served by differing service providers, e.g., different telecommunications operating companies.
  • Fixed station domain [0005] 20F includes at least one local exchange 22F. Local exchange 22F is connected to a plurality of fixed subscriber stations, only one of which (subscriber 24) is shown in FIG. 1. Local exchange 22F is connected either directly or ultimately (e.g., via transit exchanges) to a gateway exchange or gateway node 26F. Gateway node 26F is connected to a database 30F. Database 30F is, in turn, connected (e.g., for updating and maintenance purpose) to a service management system 32F.
  • Mobile telecommunications domains [0006] 20A-20C each have respective gateway nodes 26A-26C, each of which takes the form of gateway mobile services switching center (GMSC) and accordingly are respectively referred to as GMSCs 26A-26C.
  • Each gateway node GMSC [0007] 26 serves as an interface to external domains 20 for one or more mobile services switching centers (MSCs) 40 which belong to the domain.
  • Although any given domain likely has a plurality of MSCs [0008] 20, only a single MSC 40 is shown in domains 20 for purposes of illustration. Each GMSC 26 is connected to the MSCs 40 in its domain; MSCs 40 in the same domain may also be connected. Each MSC 40 in FIG. 1 is connected to serve at least one and preferably a plurality of base station controllers (BSCs) 50. For example, MSC 40A serves base station controllers 50A-1 through 50A-m; MSC 40B(1) serves base station controllers 50B(1)-1 through 50B(1)-m. It should be understood that, typically, differing MSCs 40 serve a differing number of base station controllers 50 The use of BSCs 50, shown in the Figures, is for purposes of illustration. It will be recognized that each MSC 40 can directly serve the BSs 60 without any intermediary BSCs 50 in some mobile systems (e.g., TDMA according to IS-136).
  • Each base station controller [0009] 50 is connected to one or more base transceiver stations (BS) 60A-1 through 60A-1(q). The number of base transceiver stations (BS) 60 per base station controller 50 can vary.
  • Each base transceiver stations (BS) [0010] 60 transmits and receives radio frequency communications to and from a plurality of mobile subscribers (MS) 70 in the geographical areas served by the respective BS 60. For sake of simplicity and illustration, only one mobile station 70 is shown in FIG. 1, although it should be understood that each domain 20 serves hundreds if not thousands of unillustrated mobile stations. The particular mobile station 70 depicted in FIG. 1 is shown as being served by base transceiver station (BS) 60A-m(q).
  • Mobile telecommunications domains [0011] 20A-20C each include respective databases 30A-30C. Databases 30A-30C are connected to and maintained by service management systems 32A-32C, respectively. Service management systems 32A-32C are connected to and supervised by a master management system 32M.
  • Databases [0012] 30 are subscriber location servers which are augmented with additional intelligence and are known as mobile subscriber number portability databases. Databases 30 include information which facilitates number portability for many types of subscribers in their respective domains, including mobile subscribers.
  • As will become more apparent below, the mobile telecommunications domains [0013] 20A-20C described above comprise a mobile subscriber number portability domain. In the number portability domain, mobile subscribers can change service providers, e.g., change from one of the domains to another, e.g., change from domain 20A to domain 20C, and still maintain their “directory” number. FIG. 2 shows the circumstance where mobile subscriber 71 has changed service providers. In particular, as depicted in FIG. 2, mobile subscriber 71 has changed his subscription from the provider which operates domain 20C to the provider which operates domain 20B. In fact, at the time shown in FIG. 2, mobile subscriber 71 is served by MSC 40B(1).
  • Upon the change of subscription as depicted in FIG. 2, deletion of the subscriber (owning mobile station [0014] 71) from MSC 40C was communicated to service management system (SMS) 32C, which advised master service management system (SMS) 32M. SMS 32M subsequently communicated the deletion of the subscriber to all SMSs 32, including SMSs 32A, 32B, and 32F, which in turn updated respective databases 30A, 30B, 32F, accordingly. Then, when the subscriber joined the service provider which operates domain 20B, SMS 32C advised master SMS 32M of the enlistment. SMS 32M subsequently advised all SMSs 32 of the enlistment in domain 20B of the subscriber, including SMSs 32A, 32C, 32F, which in turn updated respective databases 30A, 30C, and 30F, accordingly. Therefore, in accordance with the above process, the subscriber of mobile station 71 is able to retain the same directory number upon changing service providers from domain 20C to domain 20B.
  • FIG. 2 further shows placement of a call from mobile subscriber [0015] 70 in domain 20A to mobile subscriber 71 which has changed from service provider 20C to service provider 20B. The originating MSC 40A receives the mobile subscriber call via BS 60A-m(q) and BSC 50A-m. Then, in accordance with conventional techniques, MSC 40A initiates a number portability request message (Action 3-1; FIG. 2), such as, for example, the Number Portability Request Invoke message utilized in ANSI41, to number portability database 30A. However, in view of the previous updating of database 30A to reflect the mobile subscriber 71 changing service providers (as discussed above), the parameter returned by database 30A at action 3-2 includes the address of the new GMSC 26B, not the address of the old GMSC 26C. Thus, at 3-2, number portability database 30A initiates a number portability return message, such as, for example, the Number Portability Request Return Result (npreq) utilized in ANSI41, to the originating MSC 40A. This return message includes a local portability routing number (LRN) to GMSC 26B. Thus, MSC 40A can then connect the originating call from mobile subscriber 70 to GMSC 26B, and thereby to MSC40B(1), BSC 50B(1)-1, BS 60B(1)-1(a), and finally to called mobile subscriber 71. Therefore, mobile subscriber 70 is able to call mobile subscriber 71, which has changed service providers from 20C to 20B, using the same directory number.
  • Thus, as described above, a call-originating domain accesses a mobile subscriber number portability database to obtain the address of the gateway node of the telecommunications domain which currently serves a called mobile subscriber. Use of the Number Portability database will therefore advantageously permit a mobile subscriber in a telecommunications system to retain the same directory number whenever the subscriber changes from one service provider/operator domain to another service provider/operator domain. [0016]
  • Conventionally, however, the above described number portability database is usable only for telecommunication service providers and does not provide portability towards Internet service providers. Applying conventional number portability techniques to the portability of Internet addressing would be advantageous since both current and proposed (Ipv6) Internet addressing systems are provider-based and therefore, whenever a subscriber changes providers, the subscriber's domain name changes as well as the subscriber's IP address. Therefore it would be desirable to extend application of the number portability database to permit a subscriber to change from one Internet access provider to another access provider without changing the subscriber's Internet IP address and/or domain name. Additionally, number portability can be applied to the internet service provider itself. Thus, if an internet service provider's IP address changes, then number portability can permit continued access by subscribers and/or other data communication network. Extending application of the conventional number portability database to Internet service providers therefore advantageously permits a cohesive integration between telecommunication and data communication networks. This integration would permit telecommunication network operators and data communications providers (e.g., internet service providers) to improve service to their subscribers by providing access between the two in a transparent fashion (i.e., telecom to datacom or datacom to telecom). Extending application of the conventional number portability database to internet service providers additionally permits number portability between data communications providers (i.e., datacom to datacom). [0017]
  • SUMMARY
  • These desirable characteristics and others are provided by the following exemplary embodiments of the invention. [0018]
  • According to one exemplary embodiment of the invention a method of routing calls through a communications network is provided. The method of this exemplary embodiment comprises the steps of: a) initiating a call from a first subscriber in a call-originating domain to a second subscriber in a data communications domain; b) transmitting a first message from a first node in said call-originating domain to a database in said call-originating domain; c) locating a current data communication network node parameter in said database, wherein said network node parameter is associated with said second subscriber; d) transmitting a second message that includes said located data communication network node parameter from said database to said first node; e) routing said call from said first node to a data communications address indicated by said located data communication network node parameter; and f) updating said database when said second subscriber changes membership from a first communication network provider to a data communication network provider. [0019]
  • According to a second exemplary embodiment of the invention a system for routing calls through a communications network is provided. The system of this exemplary embodiment comprises: means for initiating a call from a first subscriber in a call-originating domain to a second subscriber in a data communications domain; means for transmitting a first message from a first node in said call-originating domain to a database in said call-originating domain; means for locating a current data communication network node parameter in said database, wherein said network node parameter is associated with said second subscriber; means for transmitting a second message that includes said located data communication network node parameter from said database to said first node; means for routing said call from said first node to a data communications address indicated by said located data communication network node parameter; and means for updating said database when said second subscriber changes membership from a first communication network provider to a data communication network provider. [0020]
  • According to a third exemplary embodiment of the invention a method of routing calls through a communications network, the communications network having a set of domains, at least one of the domains in said set of domains being a data communications domain, is provided. The method of this exemplary embodiment comprises the steps of: accessing, in a call-originating domain included in the set of domains, a database to obtain an address of a node of the data communications domain which currently serves a called subscriber; and including the address of the data communications domain which currently serves said called subscriber as a parameter in a routing message for routing a call from the call-originating domain to said node of said data communications domain. [0021]
  • According to a fourth exemplary embodiment of the invention a system for routing calls through a communications network, the communications network having a set of domains, at least one of the domains in said set of domains being a data communications domain, is provided. The system of this exemplary embodiment comprises: means for accessing, in a call-originating domain included in the set of domains, a database to obtain an address of a node of the data communications domain which currently serves a called subscriber; and means for including the address of the data communications domain which currently serves said called subscriber as a parameter in a routing message for routing a call from the call-originating domain to said node of said data communications domain.[0022]
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • The objects and advantages of the invention will be understood by reading the following detailed description in conjunction with the drawings in which: [0023]
  • FIG. 1 is a diagram of a conventional telecommunications network that implements number portability; [0024]
  • FIG. 2 is a diagram of a call from a first mobile subscriber to a second mobile subscriber that has changed service providers in a telecommunications network; [0025]
  • FIG. 3 is a diagram of message parameters of exemplary embodiments of the invention that are included in the Number Portability Request Invoke message; [0026]
  • FIG. 4 is a diagram of message parameters of exemplary embodiments of the invention that are included in the Number Portability Request Return Result message; [0027]
  • FIG. 5 is a flow diagram of exemplary embodiments of the invention; and [0028]
  • FIG. 6 is a diagram illustrating the messaging between system components in accordance with exemplary embodiments of the invention.[0029]
  • DETAILED DESCRIPTION
  • To provide portability of addresses across telecommunication and data communication networks, exemplary embodiments of the invention extend the conventional number portability principles, described in the Background section above, to include Internet addresses as well as the E.164 type of addresses currently returned as the local number portability routing digits. To account for Internet addressing, exemplary embodiments of the invention modify the conventional number portability request invoke messages (e.g., ANSI41 NPREQ) and the number portability request return result messages (e.g., ANSI41 npreq) to include additional information. For request invoke messages, this additional information will include a new parameter, “Transaction Capability,” that indicates whether Internet addressing is supported. For return result messages, the additional information will include a new optional routing address parameter, “Routing IP Address,” that will permit routing of the call on the IP network towards the ported Internet service provider (e.g., voice over IP), and a new “Ported Gateway Capabilities” parameter that specifies the protocol capabilities of the ported gateway. [0030]
  • FIG. 3 illustrates modification of the conventional Number Portability Request Invoke message [0031] 100 in accordance with exemplary embodiments of the invention. As discussed above, “Transaction Capability” flag 101 is added to the message 100 to indicate whether the originating mobile switching center/end user terminal/network node is capable of initiating Internet calls to a destination IP address. If the flag 101 is “set,” then the capability of supporting Internet addressing is indicated. Conversely, if the flag is “cleared,” then Internet addressing is not supported.
  • FIG. 4 illustrates modification of the conventional Number Portability Request Return Result message in accordance with further exemplary embodiments of the invention. In these further exemplary embodiments, a “Routing IP Address” parameter [0032] 103 is added to the Return Result message 102. This “Routing IP Address” parameter is composed of sub-elements including Parameter ID 104, Parameter Length 105, Address Type 106, and IP Address 107. The Parameter ID 104 is an identifier or tag that specifies the type of information included in the message, the Parameter Length 105 specifies the length of the “Routing IP Address” parameter, the Address Type 106 specifies the type of IP address (e.g., Ipv4, Ipv6, ATM, etc.) contained in the “Routing IP Address” parameter, and the IP Address 107 specifies the IP address to which the called subscriber is ported.
  • In addition to the “Routing IP Address,” the protocol capabilities of the ported gateway will be included in a new “Ported Gateway Capabilities” parameter [0033] 130. This parameter will specify the protocol capabilities of the ported gateway including options such as SIP, H.323, L2TP tunneling (IETF), PPP (point to point protocol, IETF), or ATM UNI.
  • It is noted that, though FIGS. 3 and 4 illustrate the additional parameters of exemplary embodiments as being appended to the end of the conventional Request Invoke and Return Result messages, one skilled in the art will recognize that these additional parameters could be located at any appropriate location within the messages. [0034]
  • In further exemplary embodiments of the invention, the conventional Number Portability database ([0035] 30 in FIG. 2) can also be modified to support a new entry for IP addresses. Additionally, a “Name Address” entry could also be added to the NPDB. This “Name Address” entry could be used for performing conversion to an IP address before the NPDB answers a number portability request message. This conversion could be performed, for example, by querying a directory name server. For example, if the ported address is a text address (e-mail, URL, etc.), the NPDB would query a directory name server to request the IP address corresponding to the text address. This IP address can then be returned via the Return Result message (102 and 103 of FIG. 4).
  • A flow diagram of the operation of the exemplary embodiments discussed above is shown in FIG. 5. When a communication is initiated [0036] 110, the switching center/end user terminal/network node (117, FIG. 6) will initiate 111 a Number Portability Request message (118, FIG. 6) to the NPDB (30, FIG. 6) which will include the “Transaction Capability” parameter. The NPDB then determines 112 whether the “Transaction Capability” parameter indicates that the MSC/end user terminal/network node is capable of initiating Internet calls to a destination IP address. If internet addressing is not supported, meaning that the originating domain is not able to set-up an internet call to the ported internet service provider, the NPDB will return 113 an LRN in E.164 format that is the address of the closest gateway to the ported internet service provider (ISP) capable of performing protocol conversion. If, however, Internet addressing is supported, the NPDB further analyzes the ported address to determine whether the ported address is a text address 114. If the ported address is a text address, then the NPDB queries a directory name server to request the IP address which corresponds to the text address.
  • The NPDB then returns [0037] 115 the IP address to which the called subscriber is ported to the originating MSC/end user terminal/network node via the “Routing IP Address” parameter (119, FIG. 6). The NPDB additionally returns 120 the available protocol options of the ported gateway via the “Ported Gateway Capabilities” parameter. The originating domain (i.e., the mobile switching center, end user terminal, or network node), then selects 122 one of the options specified in the parameter for initiating 123 the call towards the ported domain (or the new service provider).
  • Thus, as described above, exemplary embodiments of the invention extend the number portability principle, implemented in existing telecommunication networks, to support IP address portability between telecommunication service providers and data communication service providers or between data communication service providers and other data communication service providers. One skilled in the art will additionally recognize that a number of standard protocols could be used to support the enhancements of the exemplary embodiments of the invention described above with only minor modifications. For telecommunications domains, these protocols could include, e.g., ANSI41, GSM MAP, and ISUP (ISDN user part). For data communications domains these protocols could include, e.g., SIP and H.323. [0038]
  • Although a number of embodiments are described herein for purposes of illustration, these embodiments are not meant to be limiting. Those skilled in the art will recognize modifications that can be made in the illustrated embodiments. Such modifications are meant to be covered by the spirit and scope of the appended claims. [0039]

Claims (20)

What is claimed is:
1. A method of routing calls through a communications network comprising the steps of:
a) initiating a call from a first subscriber in a call-originating domain to a second subscriber in a data communications domain;
b) transmitting a first message from a first node in said call-originating domain to a database in said call-originating domain;
c) locating a current data communication network node parameter in said database, wherein said network node parameter is associated with said second subscriber;
d) transmitting a second message that includes said located data communication network node parameter from said database to said first node;
e) routing said call from said first node to a data communications address indicated by said located data communication network node parameter; and
f) updating said database when said second subscriber changes membership from a first communication network provider to a data communication network provider.
2. The method of
claim 1
, wherein step c) further comprises the substep of:
i) converting said located data communication network node parameter to a data communications address using a naming address database.
3. The method of
claim 1
, wherein the network node parameter is an IP address.
4. The method of
claim 2
, wherein the data communications address is an IP address.
5. The method of
claim 1
, wherein said first message includes a first parameter that indicates whether said first node supports data communication network addressing.
6. A system for routing calls through a communications network comprising:
means for initiating a call from a first subscriber in a call-originating domain to a second subscriber in a data communications domain;
means for transmitting a first message from a first node in said call-originating domain to a database in said call-originating domain;
means for locating a current data communication network node parameter in said database, wherein said network node parameter is associated with said second subscriber;
means for transmitting a second message that includes said located data communication network node parameter from said database to said first node;
means for routing said call from said first node to a data communications address indicated by said located data communication network node parameter; and
means for updating said database when said second subscriber changes membership from a first communication network provider to a data communication network provider.
7. The system of
claim 6
, wherein said means for locating a network node parameter further comprises:
means for converting said located data communication network node parameter to a data communications address using a naming address database.
8. The system of
claim 6
, wherein the network node parameter is an IP address.
9. The system of
claim 7
, wherein the data communications address is an IP address.
10. The system of
claim 6
, wherein said first message includes a first parameter that indicates whether said first node supports data communication network addressing.
11. A method of routing calls through a communications network, the communications network having a set of domains, at least one of the domains in said set of domains being a data communications domain, the method comprising the steps of:
accessing, in a call-originating domain included in the set of domains, a database to obtain an address of a node of the data communications domain which currently serves a called subscriber; and
including the address of the data communications domain which currently serves said called subscriber as a parameter in a routing message for routing a call from the call-originating domain to said node of said data communications domain.
12. The method of
claim 11
, further comprising the step of:
providing a first message to said database indicating whether said call-originating domain supports data communication network addressing.
13. The method of
claim 11
, wherein the address included as a parameter in the routing message is the IP address of the data communications domain which currently serves said called subscriber.
14. The method of
claim 11
, wherein the method further comprises the step of:
updating said database when said subscriber changes membership from a communications domain in said set of domains to a data communications domain whereby the address of the node of the data communications domain is associated in said database with said subscriber.
15. The method of
claim 11
, wherein said call-originating domain is a telecommunications domain.
16. A system for routing calls through a communications network, the communications network having a set of domains, at least one of the domains in said set of domains being a data communications domain, comprising:
means for accessing, in a call-originating domain included in the set of domains, a database to obtain an address of a node of the data communications domain which currently serves a called subscriber; and
means for including the address of the data communications domain which currently serves said called subscriber as a parameter in a routing message for routing a call from the call-originating domain to said node of said data communications domain.
17. The system of
claim 16
, further comprising:
means for providing a first message to said database indicating whether said call-originating domain supports data communication network addressing.
18. The system of
claim 16
, wherein the address included as a parameter in the routing message is the IP address of the data communications domain which currently serves said called subscriber.
19. The system of
claim 16
, wherein the system further comprises:
means for updating said database when said subscriber changes membership from a communications domain in said set of domains to a data communications domain whereby the address of the node of the data communications domain is associated in said database with said subscriber.
20. The system of
claim 16
, wherein said call-originating domain is a telecommunications domain.
US09/908,813 1998-12-28 2001-07-20 Extended number portability database services Abandoned US20010040958A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US09/221,165 US6266405B1 (en) 1998-12-28 1998-12-28 Extended number portability database services
US09/908,813 US20010040958A1 (en) 1998-12-28 2001-07-20 Extended number portability database services

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US09/908,813 US20010040958A1 (en) 1998-12-28 2001-07-20 Extended number portability database services
US10/082,139 US20020114440A1 (en) 1998-12-28 2002-02-26 Extended number portability database services

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US09/221,165 Continuation US6266405B1 (en) 1998-12-28 1998-12-28 Extended number portability database services

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US10/082,139 Continuation US20020114440A1 (en) 1998-12-28 2002-02-26 Extended number portability database services

Publications (1)

Publication Number Publication Date
US20010040958A1 true US20010040958A1 (en) 2001-11-15

Family

ID=22826634

Family Applications (3)

Application Number Title Priority Date Filing Date
US09/221,165 Expired - Lifetime US6266405B1 (en) 1998-12-28 1998-12-28 Extended number portability database services
US09/908,813 Abandoned US20010040958A1 (en) 1998-12-28 2001-07-20 Extended number portability database services
US10/082,139 Abandoned US20020114440A1 (en) 1998-12-28 2002-02-26 Extended number portability database services

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US09/221,165 Expired - Lifetime US6266405B1 (en) 1998-12-28 1998-12-28 Extended number portability database services

Family Applications After (1)

Application Number Title Priority Date Filing Date
US10/082,139 Abandoned US20020114440A1 (en) 1998-12-28 2002-02-26 Extended number portability database services

Country Status (13)

Country Link
US (3) US6266405B1 (en)
EP (1) EP1142270B1 (en)
JP (1) JP4430239B2 (en)
CN (1) CN1247003C (en)
AR (1) AR022131A1 (en)
AT (1) AT305202T (en)
AU (1) AU2132800A (en)
BR (1) BR9916630B1 (en)
CA (1) CA2356679C (en)
DE (1) DE69927406T2 (en)
ES (1) ES2249056T3 (en)
NZ (1) NZ512314A (en)
WO (1) WO2000039981A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070005517A1 (en) * 2005-06-30 2007-01-04 Lucent Technologies Inc. Network support for submitting mail handling instructions to a postal service

Families Citing this family (61)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9286294B2 (en) 1992-12-09 2016-03-15 Comcast Ip Holdings I, Llc Video and digital multimedia aggregator content suggestion engine
US7168084B1 (en) 1992-12-09 2007-01-23 Sedna Patent Services, Llc Method and apparatus for targeting virtual objects
US6456603B1 (en) * 1999-01-21 2002-09-24 Telefonaktiebolaget L M Ericsson (Publ) Method of supporting communications mobility in a telecommunications system
JP2001094670A (en) * 1999-09-22 2001-04-06 Noboru Miura Telephone number revision guide system, server unit of this system, and computer-readable medium recording telephone number revision guide program
EP1959634A1 (en) 1999-09-28 2008-08-20 AT&T Corp. H.323 user, service and service provider mobility framework for the multimedia intelligent networking
US7346022B1 (en) * 1999-09-28 2008-03-18 At&T Corporation H.323 user, service and service provider mobility framework for the multimedia intelligent networking
DE19948458A1 (en) * 1999-10-08 2001-04-19 Alcatel Sa Server for supporting the establishment of telephone communications over an IP network
US7184418B1 (en) * 1999-10-22 2007-02-27 Telcordia Technologies, Inc. Method and system for host mobility management protocol
US6868416B2 (en) * 1999-12-03 2005-03-15 Korea Telecommunication Authority Internet addressing architecture and hierarchical routing method thereof
US6633635B2 (en) 1999-12-30 2003-10-14 At&T Corp. Multiple call waiting in a packetized communication system
US6937713B1 (en) 1999-12-30 2005-08-30 At&T Corp. IP call forward profile
US6775273B1 (en) 1999-12-30 2004-08-10 At&T Corp. Simplified IP service control
US6678265B1 (en) * 1999-12-30 2004-01-13 At&T Corp. Local number portability database for on-net IP call
US6816469B1 (en) 1999-12-30 2004-11-09 At&T Corp. IP conference call waiting
US6826173B1 (en) 1999-12-30 2004-11-30 At&T Corp. Enhanced subscriber IP alerting
US7180889B1 (en) 1999-12-30 2007-02-20 At&T Corp. Personal control of address assignment and greeting options for multiple BRG ports
US6690675B1 (en) 1999-12-30 2004-02-10 At&T Corp. User programmable fail-proof IP hotline/warm-line
US6671262B1 (en) 1999-12-30 2003-12-30 At&T Corp. Conference server for automatic x-way call port expansion feature
US6775267B1 (en) 1999-12-30 2004-08-10 At&T Corp Method for billing IP broadband subscribers
US6728239B1 (en) 1999-12-30 2004-04-27 At&T Corp. Scaleable network server for low cost PBX
US6680935B1 (en) 1999-12-30 2004-01-20 At&T Corp. Anonymous call rejection
US20020147845A1 (en) * 2001-03-06 2002-10-10 Juan-Antonio Sanchez-Herrero Flexible user distribution between user's serving entities
EP1278382B1 (en) * 2001-07-19 2007-02-14 Telefonaktiebolaget LM Ericsson (publ) Method and apparatus for solving number portability in origin
US7908628B2 (en) 2001-08-03 2011-03-15 Comcast Ip Holdings I, Llc Video and digital multimedia aggregator content coding and formatting
US7793326B2 (en) 2001-08-03 2010-09-07 Comcast Ip Holdings I, Llc Video and digital multimedia aggregator
ES2255682T3 (en) * 2002-06-28 2006-07-01 T-Mobile Deutschland Gmbh Procedure and device to treat short messages in case of call maintenance.
KR100805507B1 (en) * 2002-09-13 2008-02-20 엘지노텔 주식회사 System and Method for Mobile Number Portability Service
US7845749B2 (en) * 2002-11-13 2010-12-07 Sony Corporation Liquid-ejecting method and liquid-ejecting apparatus
US7417981B2 (en) * 2003-10-15 2008-08-26 Vonage Holdings Corp. Method and apparatus for enhanced Internet Telephony
US7860231B2 (en) * 2004-01-30 2010-12-28 Alcatel-Lucent Usa Inc. Porting a directory number for a duration of time
US7386111B2 (en) 2004-02-10 2008-06-10 Vonage Network Inc. Method and apparatus for placing a long distance call based on a virtual phone number
AT343303T (en) * 2004-05-11 2006-11-15 Cit Alcatel Network element and method for forming address information
US7940746B2 (en) 2004-08-24 2011-05-10 Comcast Cable Holdings, Llc Method and system for locating a voice over internet protocol (VoIP) device connected to a network
US20060210036A1 (en) * 2005-03-16 2006-09-21 Jeffrey Citron System for effecting a telephone call over a computer network without alphanumeric keypad operation
US8683044B2 (en) * 2005-03-16 2014-03-25 Vonage Network Llc Third party call control application program interface
US20060210040A1 (en) * 2005-03-16 2006-09-21 Jeffrey Citron Transfer identification software enabling electronic communication system
US20060233345A1 (en) * 2005-04-18 2006-10-19 Michael Frediani Automatic contact distributor with workflow system integration
MX2008006172A (en) * 2005-11-09 2008-10-09 Vonage Holdings Corp Method and system for customized caller identification.
US20070162421A1 (en) * 2006-01-12 2007-07-12 Sybase, Inc. Real-Time Messaging System for Bridging RDBMSs and Message Buses
US20070174395A1 (en) 2006-01-20 2007-07-26 Bostick James E Systems, methods, and media for communication with database client users
EP1985096A1 (en) * 2006-02-01 2008-10-29 Vonage Holdings Corp. Method and apparatus for communicating a status of a device in a packet-based communication network
AU2007217346B2 (en) 2006-02-27 2011-07-28 Vonage Holdings Corp. Automatic device configuration
US20070203909A1 (en) * 2006-02-28 2007-08-30 Tekelec Methods, systems, and computer program products for indexing, validating, recovering, and consolidating a database indexed by range-bound numeric data
US7933392B1 (en) 2006-05-31 2011-04-26 The Nielsen Company (Us), Llc Method and system for measuring market-share for an entire telecommunication market
US8804694B2 (en) * 2006-06-08 2014-08-12 At&T Intellectual Property Ii, L.P. Method and apparatus for invoking multimodal interaction in a VOIP call
US8184798B2 (en) * 2006-06-13 2012-05-22 Tekelec Methods, systems and computer program products for accessing number portability (NP) and E.164 number (ENUM) data using a common NP/ENUM data locator structure
US7761088B1 (en) 2006-07-14 2010-07-20 The Nielsen Company (U.S.), Llc Method and system for measuring market information for wireless telecommunication devices
KR100864824B1 (en) * 2006-09-22 2008-10-23 한국전자통신연구원 Apparatus and Method of processing number portability call among various telephone networks
CN1929629B (en) * 2006-09-27 2011-04-06 华为技术有限公司 Method, system for triggering intelligent business and signal processing device
US8254551B2 (en) 2006-12-07 2012-08-28 Tekelec, Inc. Methods, systems, and computer program products for providing quality of service using E.164 number mapping (ENUM) data in a communications network
US8917717B2 (en) * 2007-02-13 2014-12-23 Vonage Network Llc Method and system for multi-modal communications
US8538000B2 (en) 2007-08-10 2013-09-17 Tekelec, Inc. Methods, systems, and computer program products for performing message deposit transaction screening
US8594679B2 (en) 2008-03-07 2013-11-26 Tekelec Global, Inc. Methods, systems, and computer readable media for routing a message service message through a communications network
CN101547413B (en) 2008-03-25 2012-03-14 数码通电讯有限公司 Method and device for connecting calling from GSM mobile phone to IP phone
US8279852B2 (en) 2008-10-01 2012-10-02 The Nielsen Company (Us), Llc Method and system for measuring market share for voice over internet protocol carriers
US8837699B2 (en) 2008-10-01 2014-09-16 The Nielsen Company (Us), Llc Methods and apparatus to monitor subscriber activity
US9584959B2 (en) 2008-11-24 2017-02-28 Tekelec Global, Inc. Systems, methods, and computer readable media for location-sensitive called-party number translation in a telecommunications network
US8369826B2 (en) 2009-03-18 2013-02-05 The Nielsen Company (Us), Llc Methods and apparatus to identify wireless subscriber activity status
WO2010132436A2 (en) 2009-05-11 2010-11-18 Tekelec Methods, systems, and computer readable media for providing scalable number portability (np) home location register (hlr)
WO2011035050A2 (en) 2009-09-16 2011-03-24 Tekelec Methods, systems, and computer readable media for providing foreign routing address information to a telecommunications network gateway
US9635526B2 (en) 2013-03-15 2017-04-25 Tekelec, Inc. Methods, systems, and computer readable media for utilizing a diameter proxy agent to communicate short message service (SMS) messages

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3671488B2 (en) 1995-12-18 2005-07-13 ソニー株式会社 Call system and call method
US6463270B1 (en) 1996-01-26 2002-10-08 Telcordia Technologies, Inc. Method and apparatus supporting non-geographic telephone numbers
WO1997048050A1 (en) 1996-06-11 1997-12-18 Vdonet Corporation Ltd. Ip name resolution system
US6021126A (en) * 1996-06-26 2000-02-01 Bell Atlantic Network Services, Inc. Telecommunication number portability
BR9711952A (en) 1996-10-18 1999-08-24 Ericsson Telefon Ab L M telecommunications network {es and process route calls via-s of a telecommunications network {es

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070005517A1 (en) * 2005-06-30 2007-01-04 Lucent Technologies Inc. Network support for submitting mail handling instructions to a postal service

Also Published As

Publication number Publication date
AU2132800A (en) 2000-07-31
EP1142270A1 (en) 2001-10-10
CA2356679C (en) 2006-11-14
BR9916630A (en) 2001-10-16
WO2000039981A1 (en) 2000-07-06
AR022131A1 (en) 2002-09-04
AT305202T (en) 2005-10-15
NZ512314A (en) 2003-02-28
DE69927406T2 (en) 2006-07-06
JP2002534847A (en) 2002-10-15
DE69927406D1 (en) 2006-02-02
JP4430239B2 (en) 2010-03-10
BR9916630B1 (en) 2014-11-25
ES2249056T3 (en) 2006-03-16
EP1142270B1 (en) 2005-09-21
CN1376354A (en) 2002-10-23
US6266405B1 (en) 2001-07-24
CN1247003C (en) 2006-03-22
CA2356679A1 (en) 2000-07-06
US20020114440A1 (en) 2002-08-22

Similar Documents

Publication Publication Date Title
EP1727378B1 (en) Method and apparatus for defining and updating mobile services
US7656864B2 (en) Data network computing device call processing
CA2274821C (en) Providing location-based call forwarding within a mobile telecommunications network
US6845400B2 (en) Storing subscriber location indication at DNS, to enable location specific provision of internet content
EP1111945B1 (en) System and methods for global access to services for mobile telephone subscribers
ES2290312T3 (en) Method and appliance for resolving an entity identifier in an internet address that uses a dns server (domain name system).
US7027433B2 (en) Routing a call between different types of networks
AU752888B2 (en) Broadcasting messages to mobile stations within a geographic area
US5742598A (en) Network for efficiently locating resources and routing service requests received from individual node connections
CA2302482C (en) Network hub for interconnecting a wireless office environment with a public cellular telephone network
EP0985309B1 (en) Delivery of announcements to a user of a communications system when roaming in a network away from the user's home network
ES2270836T3 (en) Short message service support through a telephone network by package switching.
AU732643B2 (en) Rerouting an incoming call to a ported telecommunications terminal
US5884179A (en) Optimized routing of terminating calls within a mobile telecommunications network
US6845153B2 (en) Network independent party addressing using a unique identifier linked to network specific addresses
DE69834650T2 (en) Update of internet access point settings in a mobile radio system
JP4037456B2 (en) Routing address translation in telecommunications networks
US6693894B1 (en) Communications network and method for directly routing calls to mobile subscribers using an internet protocol network
EP0890287B1 (en) Routing an incoming call to a mobile station within a telecommunications network
US6658259B2 (en) Wireless network having a virtual HLR and method of operating the same
DE10020278B4 (en) A system for dynamically routing a short message sent from a sender using a mobile telephone
DE69932088T2 (en) Method and means for providing services in a telecommunications network
CN1977552B (en) System and method for virtual carrier addressing and routing for global short message service
CN1328915C (en) Method and apparatus for communicating data packet from external packet network to mobile radio station
JP3811064B2 (en) Authentication method and system

Legal Events

Date Code Title Description
STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO PAY ISSUE FEE