Recursive query for communications network data

• US 7,599,351 B2
• Filed: 03/15/2002
• Issued: 10/06/2009
• Est. Priority Date: 03/20/2001
• Status: Active Grant

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: Verizon Business Global LLC (Verizon Communications Inc.)
• Inventors: Gallant, John Kenneth, McMurry, Kathleen A.
• Primary Examiner(s): Patel; Jayanti K
• Assistant Examiner(s): Park; Jung
• Application Number:
  US10/099,097
• Publication Number:
  US 20020136206A1
• Time in Patent Office: 2,762 Days
• Field of Search: None
• US Class Current: 370/352
• CPC Class Codes: G06Q 20/102 Bill distribution or payments
• CPC Class Codes: G06Q 30/04 Billing or invoicing
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes
• CPC Class Codes: H04L 12/14 Charging , metering or billing arrangements for data wireline or wireless communications
• CPC Class Codes: H04L 12/1403 Architecture for metering, charging or billing
• CPC Class Codes: H04L 12/1446 inter-operator billing
• CPC Class Codes: H04L 41/00 Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
• CPC Class Codes: H04L 43/00 Arrangements for monitoring or testing data switching networks
• CPC Class Codes: H04L 43/06 Generation of reports
• CPC Class Codes: H04L 43/0817 by checking functioning
• CPC Class Codes: H04L 43/16 Threshold monitoring
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 47/125 by balancing the load, e.g. traffic engineering
• CPC Class Codes: H04L 47/19 at layers above the network layer network arrangements for networked applications for scheduling or organising the servicing of application requests H04L67/60
• CPC Class Codes: H04L 47/2408 for supporting different services, e.g. a differentiated services [DiffServ] type of service
• CPC Class Codes: H04L 47/2433 Allocation of priorities to traffic types
• CPC Class Codes: H04L 47/2441 relying on flow classification, e.g. using integrated services [IntServ]
• CPC Class Codes: H04L 61/00 Network arrangements, protocols or services for addressing or naming
• CPC Class Codes: H04L 61/4523 using lightweight directory access protocol [LDAP]
• CPC Class Codes: H04L 61/4535 using an address exchange platform which sets up a session between two nodes, e.g. rendezvous servers, session initiation protocols [SIP] registrars or H.323 gatekeepers
• CPC Class Codes: H04L 61/4557 : Directories for hybrid networks, e.g. including telephone numbers
• CPC Class Codes: H04L 63/0272 : Virtual private networks
• CPC Class Codes: H04L 63/102 : Entity profiles
• CPC Class Codes: H04L 63/1408 : by monitoring network traffic monitoring network traffic per se H04L43/00
• CPC Class Codes: H04L 63/1416 : Event detection, e.g. attack signature detection
• CPC Class Codes: H04L 63/1458 : Denial of Service
• CPC Class Codes: H04L 65/103 : in the network
• CPC Class Codes: H04L 65/104 : in the network
• CPC Class Codes: H04L 65/1043 : Gateway controllers, e.g. media gateway control protocol [MGCP] controllers
• CPC Class Codes: H04L 65/1069 : Session establishment or de-establishment
• CPC Class Codes: H04L 65/1094 : Inter-user-equipment sessions transfer or sharing
• CPC Class Codes: H04L 65/1096 : Supplementary features, e.g. call forwarding or call holding systems providing special services or facilities to telephony subscribers H04M3/42
• CPC Class Codes: H04L 65/1101 : Session protocols
• CPC Class Codes: H04L 65/1104 : Session initiation protocol [SIP]
• CPC Class Codes: H04L 65/401 : wherein the services involve a main real-time session and one or more additional parallel real-time or time sensitive sessions, e.g. white board sharing or spawning of a subconference
• CPC Class Codes: H04L 65/612 : for unicast
• CPC Class Codes: H04L 65/762 : at the source reformatting of additional data in video distribution servers H04N21/2355
• CPC Class Codes: H04L 67/06 : specially adapted for file transfer, e.g. file transfer protocol [FTP]
• CPC Class Codes: H04L 67/14 : Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/303 : Terminal profiles
• CPC Class Codes: H04L 67/306 : User profiles
• CPC Class Codes: H04L 67/34 : involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/51 : Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/52 : specially adapted for the location of the user terminal
• CPC Class Codes: H04L 67/563 : Data redirection of data network streams
• CPC Class Codes: H04L 67/61 : taking into account QoS or priority requirements
• CPC Class Codes: H04L 69/08 : Protocols for interworking; Protocol conversion
• CPC Class Codes: H04L 69/329 : in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 : Network security protocols
• CPC Class Codes: H04M 15/00 : Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
• CPC Class Codes: H04M 15/06 : Recording class or number of calling , i.e. A-party or called party , i.e. B-party
• CPC Class Codes: H04M 15/41 : Billing record details, i.e. parameters, identifiers, structure of call data record [CDR]
• CPC Class Codes: H04M 15/43 : Billing software details
• CPC Class Codes: H04M 15/44 : Augmented, consolidated or itemized billing statement or bill presentation
• CPC Class Codes: H04M 15/47 : Fraud detection or prevention means
• CPC Class Codes: H04M 15/49 : Connection to several service providers
• CPC Class Codes: H04M 15/51 : for resellers, retailers or service providers
• CPC Class Codes: H04M 15/52 : for operator independent billing system
• CPC Class Codes: H04M 15/53 : using mediation
• CPC Class Codes: H04M 15/55 : for hybrid networks
• CPC Class Codes: H04M 15/56 : for VoIP communications
• CPC Class Codes: H04M 15/58 : based on statistics of usage or network monitoring
• CPC Class Codes: H04M 15/63 : based on the content carried by the session initiation protocol [SIP] messages
• CPC Class Codes: H04M 15/745 : Customizing according to wishes of subscriber, e.g. friends or family
• CPC Class Codes: H04M 15/80 : Rating or billing plans; Tariff determination aspects
• CPC Class Codes: H04M 15/8207 : Time based data metric aspects, e.g. VoIP or circuit switched packet data
• CPC Class Codes: H04M 15/8214 : Data or packet based
• CPC Class Codes: H04M 15/8292 : Charging for signaling or unsuccessful connection
• CPC Class Codes: H04M 2207/203 : composed of PSTN and data network, e.g. the Internet
• CPC Class Codes: H04M 2215/0104 : Augmented, consolidated or itemised billing statement, e.g. additional billing information, bill presentation, layout, format, e-mail, fax, printout, itemised bill per service or per account, cumulative billing, consolidated billing
• CPC Class Codes: H04M 2215/0108 : Customization according to wishes of subscriber, e.g. customer preferences, friends and family, selecting services or billing options, Personal Communication Systems [PCS]
• CPC Class Codes: H04M 2215/0148 : Fraud detection or prevention means
• CPC Class Codes: H04M 2215/0152 : General billing plans, rate plans, e.g. charge rates, numbering plans, rate centers, customer accounts
• CPC Class Codes: H04M 2215/0164 : Billing record, e.g. Call Data Record [CDR], Toll Ticket[TT], Automatic Message Accounting [AMA], Call Line Identifier [CLI], details, i.e. parameters, identifiers, structure
• CPC Class Codes: H04M 2215/0168 : On line or real-time flexible customization or negotiation according to wishes of subscriber
• CPC Class Codes: H04M 2215/0172 : Mediation, i.e. device or program to reformat CDRS from one or more switches in order to adapt to one or more billing programs formats
• CPC Class Codes: H04M 2215/0176 : Billing arrangements using internet
• CPC Class Codes: H04M 2215/0188 : Network monitoring; statistics on usage on called/calling number
• CPC Class Codes: H04M 2215/2013 : Fixed data network, e.g. PDN, ATM, B-ISDN
• CPC Class Codes: H04M 2215/202 : VoIP; Packet switched telephony
• CPC Class Codes: H04M 2215/2046 : Hybrid network
• CPC Class Codes: H04M 2215/22 : Bandwidth or usage-sensitve billing
• CPC Class Codes: H04M 2215/44 : Charging/billing arrangements for connection made over different networks, e.g. wireless and PSTN, ISDN, etc.
• CPC Class Codes: H04M 2215/46 : Connection to several service providers
• CPC Class Codes: H04M 2215/54 : Resellers-retail or service providers billing, e.g. agreements with telephone service operator, activation, charging/recharging of accounts
• CPC Class Codes: H04M 2215/7813 : Time based data, e.g. VoIP or circuit switched packet data
• CPC Class Codes: H04M 2215/782 : Data or packet based
• CPC Class Codes: H04M 3/2218 : Call detail recording
• 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/46 : Arrangements for calling a number of substations in a predetermined sequence until an answer is obtained
• CPC Class Codes: H04M 3/465 : Arrangements for simultaneously calling a number of substations until an answer is obtained
• 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/0075 : Details of addressing, directories or routing tables
• CPC Class Codes: H04M 7/0078 : Security; Fraud detection; Fraud prevention
• CPC Class Codes: H04M 7/1205 : where the types of switching equipement comprises PSTN/ISDN equipment and switching equipment of networks other than PSTN/ISDN, e.g. Internet Protocol networks
• CPC Class Codes: H04M 7/128 : Details of addressing, directories or routing tables
• CPC Class Codes: H04Q 3/0029 : Provisions for intelligent networking
• CPC Class Codes: H04W 4/02 : Services making use of location information
• CPC Class Codes: H04W 4/029 : Location-based management or tracking services
• CPC Class Codes: H04W 4/20 : Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel

Abstract

An approach for providing telephony and other services over a data network is disclosed. A communications system includes a location server that generates a first subset from the set of all addresses relating to a called party. A proxy server obtains a first subset of addresses from the location server and attempts to establish a session with the called party based on the subset of addresses. In response to whether the first subset of addresses results in session establishment, the proxy server may then request a second subset from the location server. Context information provided by the location server with the first subset may be returned to the location server as part of the request for the second subset.

Claims

1. A method of establishing a communication session with at least one party coupled to a communication system, comprising:

from a location server, obtaining at least one first destination address related to communicating with the party;

providing, to the location server, context information relating to processing that occurs in the location server;

attempting to establish the session through the communication system using the first destination address; and

depending on whether the session is established using the first destination address, obtaining from the location server at least one second destination address related to communicating with the party and attempting to establish the session using the second destination address, wherein the second destination address differs from the first destination address, and, wherein the context information is obtained from the location server in conjunction with obtaining the first destination address, and the context information is provided to the location server in conjunction with obtaining the second destination address.

2. The method of claim 1 wherein the first destination address comprises a first communication system address associated with the party, and the second destination address comprises a second communication system address associated with the party.

3. The method of claim 1 wherein the context information comprises at least one of:

a nature-of-address indicator, a dial plan identifier, or a location identifier.

4. The method of claim 1 further comprising obtaining, from the location server, context information relating to processing that occurs in the location server.

5. The method of claim 4 wherein the context information comprises at least one of:

a nature-of-address indicator, a dial plan identifier, or a location identifier.

6. The method of claim 1 wherein the location server uses the context information in the course of providing the second destination address.

7. The method of claim 1 wherein the context information comprises at least one of:

a nature-of-address indicator, a dial plan identifier, or a location identifier.

8. In a communication system comprising a location server, a method of establishing a communication session with at least one party coupled to the communication system, comprising the steps of:

submitting a first request to the location server for contact information associated with the party;

obtaining a first response from the location server responsive to the first request, the first response comprising at least one first set of one or more contacts associated with the party;

attempting to establish the session with the party using the first set of contacts;

responsive to whether the first set of contacts results in establishing the session, conditionally performing the steps of;

submitting at least one second request to the location server;

obtaining a second response from the location server responsive to the second request, the second response comprising at least one second set of one or more contacts for the party; and

attempting to establish the session with the party using the second set of contacts, wherein the second set of one or more contacts differs from the first set of one or more contacts.

9. The method of claim 8 wherein the second request relates to at least one contact provided in the first response.

10. The method of claim 8 wherein the second request is initiated in response to at least one contact in the first set of contacts in the first response.

11. The method of claim 8 wherein the second request is submitted conditionally upon the content of the first response.

12. The method of claim 11 wherein the first response comprises information relating to whether the second request should be submitted.

13. The method of claim 12 wherein at least one contact in the first response comprises information relating to whether the second request should be submitted.

14. The method of claim 8 further comprising providing to the location server context information relating to processing that occurs in the location server.

15. The method of claim 14 wherein the context information comprises at least one of:

a nature of address indicator, a dial plan identifier, or a location identifier.

16. The method of claim 14 wherein the location server uses the context information provided in conjunction with the second request in the course of preparing the second response.

17. The method of claim 8 further comprising obtaining from the location server context information relating to processing that occurs in the location server.

18. The method of claim 17 wherein the context information comprises at least one of:

a nature of address indicator, a dial plan identifier, or a location identifier.

19. The method of claim 17 wherein the location server uses the context information provided in conjunction with the second request in the course of preparing the second response.

20. The method of claim 8 wherein the context information is obtained from the location server in conjunction with the first response and the context information is provided to the location server in conjunction with the second request.

21. The method of claim 20 wherein the context information comprises at least one of:

a nature of address indicator, a dial plan identifier, or a location identifier.

22. The method of claim 20 wherein the location server uses the context information provided in conjunction with the second request in the course of preparing the second response.

23. A server for providing contact information about at least one party in a communications system comprising:

means for receiving a first request for contact information for the party;

means for determining a first contact set comprising zero or more contacts for the party;

means for outputting a first response, responsive to the first request, comprising the first contact set;

means for receiving a second request, subsequent to the first request, for contact information for the party;

means for determining a second contact set comprising zero or more contacts for the party;

means for outputting a second response to the second request comprising the second contact set;

and wherein the second contact set differs from the first contact set.

24. The server of claim 23 wherein at least one of the first contact set and second contact set is a subset of all contacts for the party maintained by the location server.

25. The server of claim 23 wherein the second request relates to at least one contact provided in the first response.

26. The server of claim 23 wherein the second request is initiated in response to at least one contact in the contact set in the first response.

27. The server of claim 23 wherein the second request is submitted conditionally upon the content of the first response.

28. The server of claim 27 wherein the first response comprises information relating to whether the second request should be submitted.

29. The server of claim 23 further comprising means for providing, in conjunction with the first response, at least one indicator of whether the second request should be submitted.

30. The server of claim 23 wherein at least one contact in the first response comprises information relating to whether the second response should be submitted.

31. The server of claim 23 further comprising means for determining context information pertaining to the first request.

32. The server of claim 31 wherein the second request comprises the context information.

33. The server of claim 32 wherein the location server uses the context information provided in the second request in the course of preparing the second response.

34. The server of claim 31 wherein the context information comprises at least one of:

a nature of address indicator, a dial plan identifier, or a location identifier.

35. The server of claim 34 wherein the first response comprises the context information.

36. The server of claim 34 wherein the location server uses the context information provided in the second request in the course of preparing the second response.

37. The server of claim 34 wherein the context information comprises at least one of:

a nature of address indicator, a dial plan identifier, or a location identifier.

38. The server of claim 34 wherein the second request comprises the context information.

39. The server of claim 38 wherein the location server uses the context information provided in the second request in the course of preparing the second response.

40. The server of claim 38 wherein the context information comprises at least one of:

a nature of address indicator, a dial plan identifier, or a location identifier.

41. A proxy server for processing at least one request to establish a session with a party in a communications system comprising:

means for submitting to a location server a first request for contact information for the party;

means for receiving from the location server a first response to the first request, the first response comprising a first contact set;

means for determining from the first response whether a second request may be performed to obtain further contact information;

means for initiating the second request based upon the first response; and

means for submitting to the location server the second request.

42. The proxy server of claim 41 wherein at least one contact in the first response comprises information indicating the necessity of performing the second request.

43. The proxy server of claim 41 further comprising means for attempting to establish the session using at least one of the first contact set and the second contact set from the location server.

44. The proxy server of claim 41 wherein, depending upon the content of the first response, the proxy server dispatches the second request to itself.

45. The proxy server of claim 41 wherein the location server associates a finality indicator with at least one contact and the second request is conditionally submitted in response to a state of the finality indicator.

46. The proxy server of claim 41 further comprising:

means for receiving at least one context information from the location server in conjunction with the first response; and

means for providing the context information in conjunction with the second request.

47. The proxy server of claim 46 wherein the context information comprises at least one of:

a nature-of-address indicator, a dial plan identifier, or a location identifier.

48. A computer-readable storage medium having computer-executable instructions for performing a method for providing contact information for a party, the method comprising the steps of:

receiving a first request for contact information for the party;

determining a first contact set comprising zero or more contacts for the party;

outputting a first response to the first request comprising the first contact set;

receiving at least one second request, subsequent to the first request, for contact information for the party;

determining a second contact set comprising zero or more contacts for the party; and

outputting a second response to the second request comprising the second contact set;

wherein the second contact set may differ from the first contact set.

49. The computer-readable storage medium of claim 48 wherein the method further comprises the steps of:

determining context information related to the first request;

outputting the context information in conjunction with outputting the first response;

receiving the context information in conjunction with receiving the second request; and

applying the context information in determining the second contact set.

50. A computer-readable storage medium having computer-executable instructions for performing a method for obtaining contact information for a party, the method comprising the steps of:

submitting to a location server a first request for contact information for the party;

receiving from the location server a first response to the first request, the first response comprising a first contact set;

determining from the first response whether at least one second request should be performed to obtain further contact information;

initiating the second request based upon the first response;

receiving context information from the location server in conjunction with the first response; and

providing the context information to the location server in conjunction with the second request.

51. A method for providing contact information about at least one party in a communications system, the method comprising:

receiving a first request for contact information for the party;

determining a first contact set comprising zero or more contacts for the party;

outputting a first response, responsive to the first request, comprising the first contact set;

receiving a second request, subsequent to the first request, for contact information for the party;

determining a second contact set comprising zero or more contacts for the party;

outputting a second response to the second request comprising the second contact set, and wherein the second contact set differs from the first contact set.