Systems and methods for optimizing application data delivery over third party networks
Aspects of the present disclosure generally relate to systems and methods for managing and optimizing end-to-end communication sessions involving the delivery of application data (e.g., audio (voice) data, audio/video data, electronic file download data, etc.) over third party networks using an optimized communication system (OCS), as described herein. Embodiments of the disclosed system provide and maintain optimal quality (e.g., reduced delay, packet loss, jitter, etc.) of communication sessions. In one example, the system provides (a real-time or close to real-time) evaluation of the network conditions, e.g., which networks are congested, and other factors associated with geographically diverse and unpredictable routing infrastructure characteristics of the Internet.
1. In an optimized communication system (OCS) including operative connections through one or more networks to a plurality of communication nodes for enabling communication sessions via the one or more networks, a method for optimizing incoming communication sessions, comprising the steps of:
receiving an indication at a particular communication node of an incoming communication session, wherein the indication includes information identifying a sending node;
upon determination that the sending node is not an OCS-compliant node, retrieving a predetermined list of preferred communication nodes from a local communication node database, wherein the preferred communication nodes are included in the predetermined list at least partially based on a communication session type associated with each preferred communication node;
parsing the predetermined list of preferred communication nodes to determine whether the sending node is present in the predetermined list of preferred communication nodes; and
if the sending node is present in the predetermined list of preferred communication nodes, accepting the incoming communication session from the sending node.
2. The method of claim 1 , wherein the particular communication node is a provisioning server for storing and maintaining the predetermined list of preferred communication nodes.
3. The method of claim 1 , wherein the particular communication node is a statistics server for receiving and storing information associated with network conditions.
4. The method of claim 1 , wherein the indication includes parameters defining the incoming communication session.
5. The method of claim 1 , wherein the sending node comprises a source node that originated the incoming communication session.
6. The method of claim 1 , wherein the sending node comprises a relay node that did not originate the incoming communication session.
7. The method of claim 1 , wherein the OCS includes an OCS server module for performing various functionalities of the OCS.
8. The method of claim 7 , wherein the preferred communication nodes are managed by the OCS server module.
9. The method of claim 7 , wherein the preferred communication nodes are not managed by the OCS server module.
10. The method of claim 1 , wherein the preferred communication nodes are selected from the group comprising: route nodes, media proxy nodes, relay nodes, communication-type-defined nodes.
11. The method of claim 1 , wherein the predetermined list of preferred communication nodes is defined by one or more of the following: an OCS administrator, a local user of the particular communication node, automatically by the particular communication node, automatically by an OCS server module.
12. The method of claim 1 , wherein the particular communication node comprises a network edge device.
13. The method of claim 1 , wherein the step of parsing the predetermined list of preferred communication nodes to determine whether the sending node is present in the predetermined list of preferred communication nodes takes into account the communication session type associated with each node.
14. The method of claim 1 , wherein the step of parsing the predetermined list of preferred communication nodes to determine whether the sending node is present in the predetermined list of preferred communication nodes takes into account network characteristic information corresponding to the preferred communication nodes.
15. The method of claim 1 , wherein the communication session type is a particular class of communication traffic of one or more classes of communication traffic that can be routed by each of the possible communication nodes.
16. The method of claim 15 , wherein the communication session type comprises one or more of voice mail, interactive voice response (IVR), conference calling, voice-based sessions, video-based sessions, multimedia-based sessions, file download sessions, and email sessions.
17. In an optimized communication system (OCS) including operative connections through one or more networks to a plurality of communication nodes for enabling communication sessions via the one or more networks, a method for optimizing incoming communication sessions, comprising the steps of:
receiving an indication at a particular communication node of an incoming communication session, wherein the indication includes information identifying a sending node;
upon determination that the sending node is not an OCS-compliant node, retrieving a predetermined list of preferred communication nodes from a local communication node database;
parsing the predetermined list of preferred communication nodes to determine whether the sending node is present in the predetermined list of preferred communication nodes, wherein the preferred communication nodes are included in the predetermined list at least partially based on a communication session type associated with each preferred communication node;
if the sending node is not present in the predetermined list of preferred communication nodes, determining whether the incoming communication session has been attempted through all preferred communication nodes in the predetermined list of communication nodes; and
if the incoming communication session has not been attempted through all preferred communication nodes in the predetermined list of communication nodes, rejecting the incoming communication session,
whereby the incoming communication session is received at the particular communication node via a second sending node.
18. The method of claim 17 , wherein the particular communication node is a provisioning server for storing and maintaining the predetermined list of preferred communication nodes.
19. The method of claim 17 , wherein the particular communication node is a statistics server for receiving and storing information associated with network conditions.
20. The method of claim 17 , wherein the indication includes parameters defining the incoming communication session.
21. The method of claim 20 , wherein the parameters comprise a source indication field.
22. In an optimized communication system (OCS) including operative connections through one or more networks to a plurality of communication nodes for enabling communication sessions via the one or more networks and an OCS server module for performing various functionalities of the OCS, a method for optimizing incoming communication sessions, comprising the steps of:
receiving an indication at a particular communication node of an incoming communication session, wherein the indication includes information identifying a sending node;
upon determination that the sending node is not an OCS-compliant node, retrieving a predetermined list of preferred communication nodes from a local communication node database, wherein the preferred communication nodes are managed by the OCS server module;
parsing the predetermined list of preferred communication nodes to determine whether the sending node is present in the predetermined list of preferred communication nodes, wherein the preferred communication nodes are included in the predetermined list at least partially based on a communication session type associated with each preferred communication node; and
if the sending node is present in the predetermined list of preferred communication nodes, accepting the incoming communication session from the sending node.
23. The method of claim 22 , wherein the communication session type is a particular class of communication traffic of one or more classes of communication traffic that can be routed by each of the possible communication nodes.
24. The method of claim 23 , wherein the communication session type comprises one or more of voice mail, interactive voice response (IVR), conference calling, voice-based sessions, video-based sessions, multimedia-based sessions, file download sessions, and email sessions.