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

• US 9,112,880 B2
• Filed: 02/15/2011
• Issued: 08/18/2015
• Est. Priority Date: 02/15/2010
• Status: Active Grant

• Current Assignee: ZTE Corporation
• Original Assignee: ZTE Corporation
• Inventors: Khasnabish, Bhumip
• Primary Examiner(s): Harper, Kevin C
• Application Number:
  US13/577,021
• Publication Number:
  US 20130003537A1
• Time in Patent Office: 1,645 Days
• Field of Search: None
• US Class Current: 1/1
• 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 method for establishing a VoIP over a cloud-based network (iVoCS), said method comprising the steps of

establishing communication between an ingress iVoCs endpoint, an engress iVoCS endpoint, an ingress edge proxy server and an egress edge proxy server,

the ingress edge proxy server locates a target proxy server,

the ingress edge proxy server locates the egress edge proxy server by way of the target proxy server,

the ingress edge proxy server and the egress edge proxy server identify most feasible resources for one or more requested sessions and finalize a resource allocation,

the ingress edge proxy server and the egress edge proxy server identify and assign one or more resources in a middle cloud, and

the ingress edge proxy server and the egress edge proxy server communicate resource information on the resource allocation, the resources in the middle cloud, or both the resource allocation and the resources in the middle cloud, to the ingress iVoCS endpoint and the egress iVoCS endpoint.

2. The method of claim 1, further comprising:

identifying. by the first edge proxy server, network resources in the cloud-based network using the received resource information, wherein the first edge proxy server facilitates voice communication between the ingress iVoCS endpoint and the egress iVoCS endpoint using the identified network resources.

3. The method of claim 1, further comprising:

establishing voice communication between the ingress iVoCS endpoint and the engress iVoCs endpoint.

4. The method of claim 1, further comprising:

receiving, at the second edge proxy server, resource information; and

facilitating, by the second edge proxy server, voice communications, wherein the second edge proxy server is operatively connected to the second iVoCs endpoint.

5. The method of claim 4, further comprising:

identifying, by the first and second edge proxy servers, network resources for the voice communications.

6. The method of claim 1, further comprising monitoring a resource list.

7. The method of claim 1, further comprising relinquishing overloaded resources.