Method and system for implementing integrated voice over internet protocol in a cloud-based network

• US 9,699,222 B2
• Filed: 07/13/2015
• Issued: 07/04/2017
• Est. Priority Date: 02/15/2010
• Status: Expired due to Fees

• Current Assignee: ZTE Corporation
• Original Assignee: ZTE Corporation
• Inventors: Khasnabish, Bhumip
• Primary Examiner(s): Harper, Kevin C
• Application Number:
  US14/797,938
• Publication Number:
  US 20150358367A1
• Time in Patent Office: 722 Days
• CPC Class Codes: F03D 7/06 the wind motors having rotation axis substantially perpendicular to the air flow entering the rotor
• CPC Class Codes: H04L 65/1016 IP multimedia subsystem [IMS]
• CPC Class Codes: H04L 65/1045 Proxies, e.g. for session initiation protocol [SIP]
• CPC Class Codes: H04L 65/1053 IP private branch exchange [PBX] functionality entities or arrangements circuit switched PBXs H04M3/00
• CPC Class Codes: H04L 65/1056 Multi-site
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/80 Responding to QoS

Abstract

A system for implementing VoIP over a cloud-based network includes a first edge proxy server operatively connected to a plurality of target proxy servers to receive resource information from one or more of the target proxy servers. Each target proxy server is associated with the cloud-based network. A first endpoint is operatively connected to the first edge proxy server and is configured for voice communications with a second endpoint. The voice communications are facilitated by the first edge proxy server using the received resource information.

Claims

1. A system for communicating over a cloud-based network between first and second endpoints, the system comprising:

an ingress edge proxy server of an ingress cloud operatively coupled to the first endpoint;

a first target proxy server of a middle cloud in a different administrative domain than the ingress cloud, the first target proxy server configured to receive information from resources under its control as identified first target resources, and operatively coupled to the ingress edge proxy server via a first intercloud interface;

an egress edge proxy server of an egress cloud in a different administrative domain than the ingress cloud and the middle cloud, the egress proxy server operatively coupled to the first target proxy server via a second intercloud interface, and operatively coupled to the second endpoint; and

a second target proxy server in one of the ingress, the middle, or the egress cloud and operatively coupled to one of the ingress or egress edge proxy servers and configured to receive information from resources under its control as identified second target resources;

wherein;

the edge proxy servers are configured to receive the information of the identified first and second target resources from the first and second target proxy servers respectively;

the edge proxy servers include middleware that identifies, allocates, and keeps track of the best identified first and second target resources for a plurality of services; and

the edge proxy servers download at respective predetermined intervals information of the tracked resources'"'"' characteristics to the first and second endpoints including at least the tracked resources'"'"' availability and loading condition; and

in the event an endpoint is decoupled from its edge proxy server and subsequently recoupled to an edge proxy server, the recoupling edge proxy server updates the recoupled endpoint with updated tracked resources information; and

the intercloud interfaces facilitate exchanges of the identified resource information and resource availability and loading information to and from the clouds to which they are attached; and

security, policy, and load balancing functions of the target proxy servers in the different administrative domains are managed by the middleware across the inter-cloud interfaces.

2. The system of claim 1, wherein the communication comprises a voice over IP (VoIP) communication.

3. The system of claim 1, wherein the at least one of the edge proxy servers establishes the route based on at least one parameter of the resource information.

4. The system of claim 2, wherein the identified cloud-based network resources are monitored by at least one of the first and second edge proxy servers to update its resource information.

5. The system of claim 4, wherein the updated resource information is used by one of the edge proxy servers to modify the route.

6. The system of claim 5, wherein the first and second edge proxy servers are both configured to independently monitor network resources for the communication, update its respective resource information, and modify at least one of the route and the resources allocated based on at least one parameter of its updated resource information.

7. The system of claim 4, wherein the first and second edge proxy servers each comprise middleware, wherein the middleware uses the information received from the target proxy servers to keep track of the best target proxy servers to use to obtain the resources needed for the communication and the route for the communication, and regularly downloads information about those target proxy servers to the first and second endpoints of the system, including at least the target proxy servers'"'"' availability and loading condition.

8. The system of claim 4, wherein in the event one of the endpoints decouples from its edge proxy server and subsequently recouples to its edge proxy server, its edge proxy server updates that endpoint'"'"'s target proxy server information.

9. A method for communicating over a cloud-based network (cloud) between first and second endpoints, comprising:

operatively coupling an ingress edge proxy server of an ingress cloud to the first endpoint;

operatively coupling a target proxy server of a middle cloud to the ingress edge proxy server via a first intercloud interface, and operatively coupling the target proxy server to an egress edge proxy server of an egress cloud via a second intercloud interface; and

operatively coupling the egress edge proxy server to the second endpoint;

wherein;

the edge proxy servers include middleware that identifies and keeps track of the best server for a desired service, and downloads at predetermined intervals information of the tracked server'"'"'s characteristics to the first and second endpoints including at least the tracked server'"'"'s availability and loading condition;

in the event an endpoint is decoupled from its edge server and subsequently recoupled to its respective ingress or egress cloud via the same or a different edge server, the recoupling edge proxy server provides the recoupled endpoint with updated tracked server information;

the intercloud interfaces facilitate exchanges of resources and respective resource availability information to or from ones of the clouds to which they are respectively attached; and

at least two of the ingress cloud, the middle cloud, and the egress cloud are in different administrative domains, and security, policy, and load balancing functions of the servers in the different administrative domains are managed by the middleware across the inter-cloud interfaces.

10. The method of claim 9, wherein the communication comprises a voice over IP (VoIP) communication.

11. The method of claim 9, wherein at least one of the edge proxy servers establishes the route using at least one parameter of the resource information it has received.

12. The method of claim 9, wherein the resources allocated for the communication between the first and second endpoints are monitored by at least one of the first and second edge proxy servers to update its resource information.

13. The method of claim 12, wherein the updated resource information is used by one of the edge proxy servers to modify the route.

14. The method of claim 13, wherein the first and second edge proxy servers are both configured to independently monitor network resources for the communication, and update its respective resource information, and modify at least one of the route and the resources allocated based on at least one parameter of its updated resource information.

15. The method of claim 9, wherein the first and second edge proxy servers each comprise middleware that uses the information received from the target proxy servers to keep track of the best target proxy servers to use to obtain the resources needed for the communication and the route for the communication, and regularly downloads information about those target proxy servers to the first and second endpoints of the system, including at least their the target proxy servers'"'"' availability and loading condition.

16. The method of claim 9, wherein in the event one of the endpoints decouples from its edge proxy server and subsequently recouples to its edge proxy server, its edge proxy server updates that endpoint'"'"'s target proxy server information.