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

• US 20050141491A1
• Filed: 02/25/2005
• Published: 06/30/2005
• Est. Priority Date: 12/11/1995
• Status: Active Grant

• Current Assignee: Comcast IP Holdings I LLC (Comcast Corporation)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Seaborne, Andrew Franklin, Low, Colin, Bouthors, Nicolas
• Granted Patent: US 7,804,816 B2
• Time in Patent Office: Days
• 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 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-16. -16. (canceled)

17. A method of accessing a target entity identified by a number string, said method comprising:

(a) storing in the domain name system of the Internet, hereinafter the DNS, records each associated with a corresponding domain name and holding an URI of an entity 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;

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

(c) supplying the domain name formed in (b) to the DNS to retrieve the URI held in the corresponding said record, this URI being that of the target entity; and

(d) using the URI retrieved in (c) in accessing said target entity.

18. A method according to claim 17, wherein the said number string identifying the target entity is of telephone-number form.

19. A method according to claim 17, wherein the URI of the target entity comprises an access scheme and host address.

20. A method according to claim 17, wherein the target entity is an information entity which is accessed in (d) to retrieve information.

21. A method according to claim 17, wherein the target entity is a logging entity which is accessed in (d) to log information.

22. A method according to claim 17, wherein in (d) the URI of the target entity is resolved into a network address of the target entity.

23. A method of accessing a target entity identified by a number string, said method comprising:

(a) storing in a DNS-type database system records each associated with a corresponding domain name and holding an URI of an entity 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;

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

(c) supplying the domain name formed in (b) to the DNS-type database system to retrieve the URI held in the corresponding said record, this URI being that of the target entity; and

(d) using the URI retrieved in (c) in accessing said target entity.

24. A method according to claim 23, wherein the said number string identifying the target entity is of telephone-number form.

25. A method according to claim 23, wherein the URI of the target entity comprises an access scheme and host address.

26. A method according to claim 23, wherein the target entity is an information entity which is accessed in (d) to retrieve information.

27. A method according to claim 23, wherein the target entity is a logging entity which is accessed in (d) to log information.

28. A method according to claim 23, wherein in (d) the URI of the target entity is resolved into a network address of the target entity.

29. A method of accessing a target entity identified by a number string, said method comprising:

(a) forming, from said 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;

(b) supplying the domain name formed in (a) to the domain name system of the Internet and receiving back from the domain name system a resource record including an URI of the target entity; and

(c) using the URI received back in (b) to access said target entity.

30. A method according to claim 29, wherein the said number string identifying the target entity is of telephone-number form.

31. A method according to claim 29, wherein the URI of the target entity comprises an access scheme and host address.

32. A method according to claim 29, wherein the target entity is an information entity which is accessed in (c) to retrieve information.

33. A method according to claim 29, wherein the target entity is a logging entity which is accessed in (c) to log information.

34. A method according to claim 29, wherein in (c) the URI of the target entity is resolved into a network access of the target entity.

35. Apparatus for accessing a target entity identified by a number string, said apparatus comprising:

the domain name system of the Internet, hereinafter the DNS;

at least one server of the DNS being arranged to store records each associated with a corresponding domain name and holding an URI of an entity 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;

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

an URI-retrieval arrangement for supplying the domain name formed by the parsing arrangement to the DNS to retrieve the URI held in the corresponding said record, this URI being that of the target entity; and

an access arrangement arranged to use the URI retrieved by the URI-retrieval arrangement to access said target entity.

36. Apparatus according to claim 35, wherein the said number string identifying the target entity is of telephone-number form.

37. Apparatus according to claim 35, wherein the URI of the target entity comprises an access scheme and host address.

38. Apparatus according to claim 35, wherein the target entity is an information entity, the access arrangement being arranged to access the target entity to retrieve information.

39. Apparatus according to claim 35, wherein the target entity is a logging entity, the access arrangement being arranged to access the target entity to log information.

40. Apparatus for accessing a target entity identified by a number string, said apparatus comprising:

a DNS-type database system comprising at least one server arranged to store records each associated with a corresponding domain name and holding an URI of an entity 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;

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

an URI-retrieval arrangement for supplying the domain name formed by the parsing arrangement to the DNS-type database system to retrieve the URI held in the corresponding said record, this URI being that of the target entity; and

an access arrangement arranged to use the URI retrieved by the URI-retrieval arrangement to access said target entity.

41. Apparatus according to claim 40, wherein the said number string identifying the target entity is of telephone-number form.

42. Apparatus according to claim 40, wherein the URI of the target entity comprises an access scheme and host address.

43. Apparatus according to claim 40, wherein the target entity is an information entity, the access arrangement being arranged to access the target entity to retrieve information.

44. Apparatus according to claim 40, wherein the target entity is a logging entity, the access arrangement being arranged to access the target entity to log information.

45. Apparatus for accessing a target entity identified by a number string, said apparatus comprising:

a parsing arrangement arranged to form, from said 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;

an URI-retrieval arrangement for supplying the domain name formed in (a) to the domain name system of the Internet and for receiving back from the domain name system a resource record including an URI of the target entity; and

an access arrangement arranged to use the URI retrieved by the URI-retrieval arrangement to access said target entity.

46. Apparatus according to claim 45, wherein the said number string identifying the target entity is of telephone-number form.

47. Apparatus according to claim 45, wherein the URI of the target entity comprises an access scheme and host address.

48. Apparatus according to claim 45, wherein the target entity is an information entity, the access arrangement being arranged to access the target entity to retrieve information.

49. Apparatus according to claim 45, wherein the target entity is a logging entity, the access arrangement being arranged to access the target entity to log information.

50. Apparatus for accessing a target entity identified by a number string, said apparatus comprising:

a parsing arrangement arranged to form, from said 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;

an URI-retrieval arrangement for supplying the domain name formed in (a) to a DNS-type database system and for receiving back from that system a resource record including an URI of the target entity; and

an access arrangement arranged to use the URI retrieved by the URI-retrieval arrangement to access said target entity.

51. Apparatus according to claim 50, wherein the said number string identifying the target entity is of telephone-number form.

52. Apparatus according to claim 50, wherein the URI of the target entity comprises an access scheme and host address.

53. Apparatus according to claim 50, wherein the target entity is an information entity, the access arrangement being arranged to access the target entity to retrieve information.

54. Apparatus according to claim 50, wherein the target entity is a logging entity, the access arrangement being arranged to access the target entity to log information.

55. A computer program product for use in accessing a target entity identified by a number string, the computer program product when executing on computing equipment being arranged to condition the equipment to provide at least:

a parsing arrangement arranged to form, from said 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;

an URI-retrieval arrangement for supplying the domain name formed in (a) to the domain name system of the Internet and for receiving back from the domain name system a resource record including an URI of the target entity; and

an access arrangement arranged to use the URI retrieved by the URI-retrieval arrangement to access said target entity.

56. A computer program product according to claim 55, wherein the said number string identifying the target entity is of telephone-number form.

57. A computer program product according to claim 55, wherein the URI of the target entity comprises an access scheme and host address.

58. A computer program product according to claim 55, wherein the target entity is an information entity, the access arrangement being arranged to access the target entity to retrieve information.

59. A computer program product according to claim 55, wherein the target entity is a logging entity, the access arrangement being arranged to access the target entity to log information.

60. A computer program product for use in accessing a target entity identified by a number string, the computer program product when executing on computing equipment being arranged to condition the equipment to provide at least:

a parsing arrangement arranged to form, from said 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;

an URI-retrieval arrangement for supplying the domain name formed in (a) to a DNS-type database system and for receiving back from that system a resource record including an URI of the target entity; and

an access arrangement arranged to use the URI retrieved by the URI-retrieval arrangement to access said target entity.

61. A computer program product according to claim 60, wherein the said number string identifying the target entity is of telephone-number form.

62. A computer program product according to claim 60, wherein the URI of the target entity comprises an access scheme and host address.

63. A computer program product according to claim 60, wherein the target entity is an information entity, the access arrangement being arranged to access the target entity to retrieve information.

64. A computer program product according to claim 60, wherein the target entity is a logging entity, the access arrangement being arranged to access the target entity to log information.