Method and apparatus for accessing communication data relevant to a target entity identified by a number string

• US 7,012,916 B2
• Filed: 01/18/2002
• Issued: 03/14/2006
• Est. Priority Date: 02/20/1996
• Status: Expired due to Term

• Current Assignee: Comcast IP Holdings I LLC (Comcast Corporation)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Seaborne, Andrew Franklin, Bouthors, Nicolas, Low, Colin
• Primary Examiner(s): Luther, William A.
• Application Number:
  US10/052,285
• Publication Number:
  US 20020167940A1
• Time in Patent Office: 1,516 Days
• Field of Search: 370/352, 370/389, 370/353, 370/380, 370/392, 370/396, 370/401, 370/404, 370/427, 370/435, 370/450, 370/465, 370/485, 379/88.17, 379/90.01, 379/93.01, 379/93.05, 379/93.09, 379/100.15, 379/100.16, 379/230, 379/221.01, 379/221.09, 379/221.08, 379/221.06, 379/87.17, 379/900, 379/220.01, 707/10, 707/201, 709/200, 709/201, 709/217, 709/219
• US Class Current: 370/352
• CPC Class Codes: H04L 12/2856 Access arrangements, e.g. Internet access asynchronous transfer mode networks H04L12/5601; broadband local area networks H04L12/2801; optical access or distribution networks H04Q11/0067; access to open networks H04L12/5691; digital subscriber line end-user equipment and bit-level processing of data on a PSTN-based network H04M11/00; home network gateways H04L12/2834; wireless access networks H04W
• CPC Class Codes: H04L 12/2867 Physical combinations
• CPC Class Codes: H04L 2101/30 Types of network names
• CPC Class Codes: H04L 2101/38 Telephone uniform resource identifier [URI]
• CPC Class Codes: H04L 61/10 of different types
• CPC Class Codes: H04L 61/30 Managing network names, e.g. use of aliases or nicknames name-to-address mapping H04L61/45
• CPC Class Codes: H04L 61/301 Name conversion
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 61/4557 Directories for hybrid networks, e.g. including telephone numbers
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 69/16 Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: H04M 2201/60 Medium conversion
• CPC Class Codes: H04M 2203/1041 Televoting
• CPC Class Codes: H04M 3/42 Systems providing special services or facilities to subscribers specially adapted for wireless communication networks H04W4/00
• CPC Class Codes: H04M 3/42161 via computer interface
• CPC Class Codes: H04M 3/42229 Personal communication services, i.e. services related to one subscriber independent of his terminal and/or location diverting calls from one subscriber to another subscriber, i.e. two different subscriptions H04M3/54; selecting arrangements in intelligent networks H04Q3/005
• CPC Class Codes: H04M 3/4228 in networks
• CPC Class Codes: H04M 3/428 : Arrangements for placing incoming calls on hold
• CPC Class Codes: H04M 3/48 : Arrangements for recalling a calling subscriber when the wanted subscriber ceases to be busy
• CPC Class Codes: H04M 3/4938 : comprising a voice browser which renders and interprets, e.g. VoiceXML
• CPC Class Codes: H04M 3/5191 : interacting with the Internet
• CPC Class Codes: H04M 3/523 : with call distribution or queueing
• CPC Class Codes: H04M 3/533 : Voice mail systems
• CPC Class Codes: H04M 3/54 : Arrangements for diverting calls for one subscriber to another predetermined subscriber based on the calling party profile H04M3/42059; based on location H04M3/42348; based on presence H04M3/42365; to voice mail H04M3/53308
• CPC Class Codes: H04M 7/0009 : where voice calls remain entirely in the telephone network
• CPC Class Codes: H04M 7/003 : Click to dial services
• CPC Class Codes: H04M 7/006 : Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP) , including next generation networks with a packet-switched transport layer H04L65/00 takes precedence; aspects not specific to the type of network H04M3/00; special services in those networks H04M3/42
• CPC Class Codes: H04M 7/12 : for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal
• CPC Class Codes: H04M 7/126 : Interworking of session control protocols
• CPC Class Codes: H04M 7/128 : Details of addressing, directories or routing tables
• CPC Class Codes: H04Q 2213/13097 : Numbering, addressing
• CPC Class Codes: H04Q 2213/13102 : Common translator
• CPC Class Codes: H04Q 2213/13106 : Microprocessor, CPU
• CPC Class Codes: H04Q 2213/13109 : Initializing, personal profile
• CPC Class Codes: H04Q 2213/13141 : Hunting for free outlet, circuit or channel
• CPC Class Codes: H04Q 2213/13175 : Graphical user interface [GUI], WWW interface, visual indication
• CPC Class Codes: H04Q 2213/13176 : Common channel signaling, CCS7
• CPC Class Codes: H04Q 2213/13204 : Protocols
• CPC Class Codes: H04Q 2213/13209 : ISDN
• CPC Class Codes: H04Q 2213/13282 : Call forward, follow-me, call diversion
• CPC Class Codes: H04Q 2213/13298 : Local loop systems, access network
• CPC Class Codes: H04Q 2213/13332 : Broadband, CATV, dynamic bandwidth allocation
• CPC Class Codes: H04Q 2213/13345 : Intelligent networks, SCP
• CPC Class Codes: H04Q 2213/13349 : Network management
• CPC Class Codes: H04Q 2213/13389 : LAN, internet
• CPC Class Codes: H04Q 2213/13405 : Dual frequency signaling, DTMF
• CPC Class Codes: H04Q 2213/13504 : client/server architectures
• CPC Class Codes: H04Q 2213/13526 : resource management
• CPC Class Codes: H04Q 2213/13527 : protocols - X.25, TCAP etc.
• CPC Class Codes: H04Q 2213/13528 : SCP architecture
• CPC Class Codes: H04Q 2213/13534 : Internet - WWW, HTML, browsers etc.
• CPC Class Codes: H04Q 2213/13546 : Intelligent Peripheral
• CPC Class Codes: H04Q 3/0029 : Provisions for intelligent networking
• CPC Class Codes: H04Q 3/005 : Personal communication services, e.g. provisions for portability of subscriber numbers
• CPC Class Codes: Y10S 379/90 : Internet, e.g. Internet phone, webphone, internet-based telephony

Abstract

Service resource items (49) for use in call setup in a telephone system are held on servers (58) that are connected to a computer network which is logically distinct from the telephone system infrastructure; this computer network may, for example, make use of the Internet. Each service resource item (49) is locatable on the network at a corresponding URI and is associated with a particular telephone number. A mapping is provided between telephone numbers and the URIs of associated service resource items. When it is desired to access a service resource item (49) associated with a particular telephone number, this mapping is used to retrieve the corresponding URI (step 55) which is then used to access the desired service resource item (56, 57, 59).

Claims

1. A method of accessing communication data relevant to a target entity identified by a number string, said method comprising:

storing in the domain name system (DNS) of the Internet records each associated with a corresponding domain name and holding an URI for locating communications data associated with the domain name, each said domain name being related to a respective number string from which it can be derived by a process including parsing at least a substantial portion of the number string into at least a part of said domain name;

applying said process to the said number string identifying the target entity whereby to form the related domain name;

supplying the domain name formed to the DNS to retrieve the URI held in the corresponding record; and

using the URI retrieved to access said communication data.

2. A method according to claim 1, wherein the URI held in at least one said record is an URL including an access scheme and host address.

3. A method according to claim 2, wherein said host address is a domain name.

4. A method according to claim 1, wherein each said number string is in telephone-number form.

5. A method according to claim 1, wherein the communications data is a communications endpoint address for the target entity.

6. A method of accessing a target entity over a telephone network, in which communications data in the form of a telephone number for the target entity is accessed according to the method of claim 1, this telephone number then being used to call the target entity over the telephone network.

7. A method according to claim 1, wherein the URI held in at least one said records is the URI for said communications data itself.

8. A method according to claim 1, wherein the URI held in at least one said records is of functionality that has access to multiple items of communications data, and wherein using the URI retrieved to access said communication data involves using the URI to access said functionality and supply it with an indicator of the desired item of communications data, this data then being returned by the functionality.

9. A method according to claim 8, wherein the indicator is incorporated into said URI and supplied in this form to said functionality.

10. A method according to claim 8, wherein the indicator is supplied to said functionality as a separate element to said URI.

11. A method according to claim 8, wherein the URI held in at least one said records is an URL including an access scheme and host address for accessing said functionality.

12. A method according to claim 8, wherein each said number string is in telephone-number form.

13. A method according to claim 8, wherein the communications data is a communications endpoint address for the target entity.

14. A method of accessing a target entity over a telephone network, in which communications data in the form of a telephone number for the target entity is accessed according to the method of claim 7, this telephone number then being used to call the target entity over the telephone network.

15. A method of accessing communication data relevant to a target entity identified by a number string, said method comprising:

storing in the domain name system (DNS) of the Internet records each associated with a corresponding domain name and holding an at least part-formed URL, including access scheme and host name, of an item of communications data, each said domain name being related to a respective number string from which it can be derived by a process including parsing at least a substantial portion of the number string into at least a part of said domain name;

applying said process to the said number string identifying the target entity whereby to form the related domain name;

supplying the domain name formed to the DNS to retrieve the at least part-formed URL held in the corresponding record; and

using the at least part-formed URL retrieved to access said communication data.

16. A method according to claim 15, wherein the URL retrieved is only part-formed and using the at least part-formed URL retrieved to access said communication data involves completing the URL by adding a path element serving to distinguish the desired item of communication data from other items held on the same host.

17. A method according to claim 15, wherein each said number string is in telephone-number form.

18. A method according to claim 15, wherein the communications data is a communications endpoint address for the target entity.

19. A method of accessing a target entity over a telephone network, in which communications data in the form of a telephone number for the target entity is accessed according to the method of claim 15, this telephone number then being used to call the target entity over the telephone network.

20. A method of discovering communications endpoint address data for contacting a target entity identified by a number string, said method comprising:

storing in the domain name system (DNS) of the Internet records each associated with a corresponding domain name and holding an URL of a resource that has access to multiple items of communications endpoint address data, each said domain name being related to a respective number string from which it can be derived by a process including parsing at least a substantial portion of the number string into at least a part of said domain name, the number strings being in telephone-number form;

applying said process to the said number string identifying the target entity whereby to form the related domain name;

supplying the domain name formed in step (b) to the DNS to retrieve the URL held in the corresponding record; and

using the URL to access the corresponding said resource and supply it with an indicator of the desired item of communications endpoint address data, this data then being returned by the resource.

21. A method of accessing communication data relevant to a target entity identified by a number string, said method comprising:

storing in a DNS-type database system, records each associated with a corresponding domain name and holding an URI for locating communications data associated with the domain name, each said domain name being related to a respective number string from which it can be derived by a process including parsing at least a substantial portion of the number string into at least a part of said domain name;

applying said process to the said number string identifying the target entity whereby to form the related domain name;

supplying the domain name formed to the DNS-type database system to retrieve the URI held in the corresponding record; and

using the URI retrieved to access said communication data.

22. A method according to claim 21, wherein the URI held in at least one said records is an URL including an access scheme and host address for accessing said communications data.

23. A method according to claim 21, wherein each said number string is in telephone-number form.

24. A method according to claim 21, wherein the communications data is a communications endpoint address for the target entity.

25. A method according to claim 21, wherein the URI held in at least one said record is of functionality that has access to multiple items of communications data, and wherein using the URI retrieved to access said communication data involves using the URI to access said functionality and supply it with an indicator of the desired item of communications data which is then returned by the functionality.

26. A method of accessing communications data for contacting a target entity, said method comprising:

forming, from a number string identifying the target entity, a domain name by a process including parsing at least a substantial portion of the number string into at least a part of said domain name;

supplying the domain name formed to the domain name system of the Internet and receiving back from the domain name system a resource record including an URI for locating communications data associated with the domain name; and

using the URI received back to access said communication data.

27. A method according to claim 26, wherein the URI received back is an URL including an access scheme and host address for accessing said communications data.

28. A method according to claim 26, wherein said number string is a telephone number.

29. A method according to claim 26, wherein the communications data is a communications endpoint address for the target entity.

30. A method of accessing a target entity over a telephone network, in which communications data in the form of a telephone number for the target entity is accessed according to the method of claim 26, this telephone number then being used to call the target entity over the telephone network.

31. A method according to claim 26, wherein the URI received back is the URI of said communications data itself.

32. A method according to claim 26, wherein the URI received back is of functionality that has access to multiple items of communications data, and wherein using the URI received back to access said communication data involves using the URI to access said functionality and supply it with an indicator of the desired item of communications data which is then returned by the functionality.

33. A method according to claim 32, wherein the indicator is incorporated into said URI and supplied in this form to said functionality.

34. A method according to claim 32, wherein the indicator is supplied to said functionality as a separate element to said URI.

35. A method according to claim 32, wherein the URI received back is an URL including an access scheme and host address for accessing said functionality.

36. A method according to claim 32, wherein said number string is a telephone number.

37. A method according to claim 32, wherein the communications data is a communications endpoint address for the target entity.

38. A method of accessing a target entity over a telephone network, in which communications data in the form of a telephone number for the target entity is accessed according to the method of claim 32, this telephone number then being used to call the target entity over the telephone network.

39. A method of accessing communications data for contacting a target entity, said method comprising:

forming, from a number string identifying the target entity, a domain name by a process including parsing at least a substantial portion of the number string into at least a part of said domain name;

supplying the domain name formed to the domain name system of the Internet and receiving back from the domain name system a resource record including an at least part-formed URL, including access scheme and host name, of an item of communications data associated with the domain name; and

using the URL received back to access said communication data.

40. A method according to claim 39, wherein the URL received back is only part-formed and wherein using the URI received back to access said communications data involves completing the URL by adding a path element serving to distinguish the desired item of communication data from other items held on the same host.

41. A method according to claim 39, wherein said number string is a telephone number.

42. A method according to claim 39, wherein the communications data is a communications endpoint address for the target entity.

43. A method of accessing a target entity over a telephone network, in which communications data in the form of a telephone number for the target entity is accessed according to the method of claim 39, this telephone number then being used to call the target entity over the telephone network.

44. A method of discovering communications endpoint address data for contacting a target entity, said method comprising:

forming, from a number string identifying the target entity, a domain name by a process including parsing at least a substantial portion of the number string into at least a part of said domain name;

supplying the domain name formed to the domain name system of the Internet and receiving back from the domain name system a resource record including an URI of a resource that has access to multiple items of communications endpoint address data; and

using the URI received back to access corresponding said resource and supply it with an indicator of the desired item of communications endpoint address data, this data then being returned by the functionality.

45. A method of accessing communications data for contacting a target entity, said method comprising:

forming, from a number string identifying the target entity, a domain name by a process including parsing at least a substantial portion of the number string into at least a part of said domain name;

supplying the domain name formed to a DNS-type database system and receiving back a resource record including an URI for locating communications data associated with the domain name; and

using the URI received back to access said communications data.

46. A method according to claim 45, wherein the URI received back is an URL including an access scheme and host address for accessing said communications data.

47. A method according to claim 45, wherein each said number string is a telephone number.

48. A method according to claim 45, wherein the communications data is a communications endpoint address for the target entity.

49. A method according to claim 45, wherein the URI held in at least one said record is of functionality that has access to multiple items of communications data, and wherein using the URI received back to access said communications data involves using the URI to access said functionality and supply it with an indicator of the desired item of communications data which is then returned by the functionality.

50. A server of the domain name system of the Internet, the server holding at least one resource record that provides a mapping from a domain name to an URI for locating communications data associated with the domain name, at least a substantial portion of the domain name being in the form of a number string that has been parsed into plural domain-name labels.

51. A server according to claim 50, wherein said URI is an URL including an access scheme and host address for accessing said communications data.

52. A method according to claim 50, wherein the communications data is a communications endpoint address for the target entity.

53. A server according to claim 51, wherein said number string is at least a substantial portion of a telephone number.

54. A server according to claim 50, wherein said URI is of functionality that has access to multiple items of communications data.

55. A server of the domain name system of the Internet, the server holding at least one resource record that provides a mapping from a domain name to an at least part-formed URL, including access scheme and host name, of an item of communications data associated with the domain name, at least a substantial portion of the domain name being in the form of a number string that has been parsed into plural domain-name labels.

56. A server according to claim 55, wherein said number string is at least a substantial portion of a telephone number.

57. A server of the domain name system of the Internet, the server holding at least one resource record that provides a mapping from a domain name to an URL of a resource that has access to multiple items of communications data, at least a substantial portion of the domain name being in the form of a number string that has been parsed into plural domain-name labels.

58. A server according to claim 57, wherein said number string is at least a substantial portion of a telephone number.

59. A DNS-type distributed database system holding at least one resource record that provides a mapping from a domain name to an URI for locating communications data associated with the domain name, at least a substantial portion of the domain name being in the form of a number string that has been parsed into plural domain-name labels.

60. A system according to claim 59, wherein said URI is an URL including an access scheme and host address for accessing said communications data.

61. A system according to claim 59, wherein said number string is at least a substantial portion of a telephone number.

62. A system according to claim 59, wherein said URI is of functionality that has access to multiple items of communications data.