Source: https://patents.google.com/patent/US9692710B2/en
Timestamp: 2019-04-21 08:53:49+00:00

Document:
2018-01-02 Assigned to SILICON VALLEY BANK, AS ADMINISTRATIVE AGENT reassignment SILICON VALLEY BANK, AS ADMINISTRATIVE AGENT SECURITY INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: GENBAND US LLC, SONUS NETWORKS, INC.
In a method and system for managing at least one media stream from a media source to a media destination, where the media stream passes through at least one network, providing a media manager for managing the media stream and the at least one network for performing at least one of the management functions bandwidth management, media hairpin detection, media path control, equal access or preventing media backhauling. In the media manager at least one of the media stream information types media routing, receive transport address, routed receive transport address, source network, destination network, media stream identifier, or bandwidth of the media stream is stored for a time period during which the media stream exists in the at least one network. The media manager uses at least one of the stored information types for performing at least one of the management functions.
This application is a continuation of U.S. patent application Ser. No. 11/314,119, filed Dec. 21, 2005, the disclosure of which is hereby incorporated by reference in its entirety.
The present application relates to media stream management on the internet.
When communicating media over the internet, five problems arise: bandwidth management; hairpinning; backhauling; media path control; and equal access. These problems will be discussed below, such as in the context of Voice-over-Internet-Protocol (VoIP). It should be understood of course that the present application relates to any type of media stream management on the internet.
By way of background, the “Open Systems Interconnection” protocol (OSI) comprises a seven layer model: application (layer 7); presentation (layer 6); session (layer 5); transport (layer 4); network (layer 3); data link (layer 2); and physical (layer 1).
For VoIP, so-called “user agents” (UA) operating at the application layer send and receive information packets by use of the Session Internet Protocol (SIP), SDP, H.323, MGCP, Megaco etc. SIP and SDP are by far the most commonly used protocol for VoIP based communications.
First, the problem of bandwidth management will be discussed. According to the low-level design scheme, information to be communicated is broken down into discrete packets of information, and these packets are directed from an originating endpoint to a destination endpoint. A higher level protocol is used to establish a connection between the endpoints. Accordingly, a virtual communications link is established and a long message is broken down into multiple packets and sent by the sender. The receiving end collects these packets and reassembles them into the original long message. However, the individual packets that comprise the message may travel over different routes to reach the endpoint, depending on network availability, loading, etc.
When transmitting e-mail, web pages, and data files or the like, it is generally not crucial that data be transmitted in real-time, i.e., delays in the data transmission are generally acceptable if the intervening network is heavily loaded. However, with respect to real-time interactive communications, such as VoIP and videoconferences, excessive delay can make the communication unworkable. Therefore, for such real-time interactive media communications, properly allocating and managing the bandwidth is important. Also, as discussed hereafter, the problems of hairpinning, equal access, and backhauling need to be managed.
Now the problems known as “hairpinning”, “bandwidth management” “media path control”, “equal access” and “backhauling” will be explained.
Hairpinning describes the situation where the caller and callee are in the same network.
Bandwidth management is a problem where a network has to manage how bandwidth is allocated for multimedia sessions based on policies for network topology or network users. Bandwidth management is necessary in order to provide guaranteed QoS (Quality of Service) to sessions and media streams which are admitted in the network and to prevent sessions from being established through the network where bandwidth is not available (using policy). Bandwidth may be tracked on single networks or between networks.
Media Path Control is a problem where in order to control the QoS provided to a session media or to route the media through incompatible networks, the media stream needs to be routed through specific network elements (generally called media gateways or MGs). Media path is controlled independently from the path session signaling takes, especially in VoIP where the two paths are setup using different protocols (e.g. SIP for signaling and SDP for media).
Equal access is a regulatory requirement which allows a subscriber to access long distance services by dialing a special code on his phone before dialing the intended recipient, thereby choosing a carrier of his choice. The user's service provider thus has to open up access to his physical infrastructure or service to third party long distance providers. For VoIP and other Internet based applications this may mean that the session signaling (that is, a signal to begin a call such as “INVITE”) and/or media stream must be routed to a third party long distance provider.
Media backhauling is a problem where media is upstreamed to the provider's core network where the service offered is controlled instead of being routed through a shorter path between the subscribers. The shorter path, which is preferred, is either a direct path between the subscribers of through local servers located close to the subscribers who do not have the service intelligence.
Session Border Controllers today integrating or coupling some forms of media management.
It is an object to improve media stream management on the internet in the problem areas of bandwidth, hairpinning, media path control, equal access, and/or backhauling.
In a method and system for managing at least one media stream from a media source to a media destination, where the media stream passes through at least one network, providing a media manager for managing the media stream and the at least one network and for performing at least one of a plurality of management functions, wherein the plurality of management functions include bandwidth management, media hairpin detection, media path control, equal access or preventing media backhauling. Storing in the media manager at least one of a plurality of media stream information types, wherein the plurality of media stream information types include media routing, receive transport address, routed receive transport address, source network, destination network, media stream identifier, or bandwidth of the media stream is stored for a time period during which the media stream exists in the at least one network. The media manager uses at least one of the stored information types for performing at least one of the management functions.
FIGS. 6A/6B show the six steps and the different types of information for the particular media stream present and which are stored in the media manager for the media path control and equal access management examples of FIG. 5 (in a media routing scenario).
For the purposes of promoting an understanding of the principles of the invention, reference will now be made to the preferred embodiment illustrated in the drawings and specific language will be used to describe the same. It will nevertheless be understood that no limitation of the scope of the invention is thereby intended, such alterations and further modifications in the illustrated device, and/or method, and such further applications of the principles of the invention as illustrated therein being contemplated as would normally occur now or in the future to one skilled in the art to which the invention relates.
does not work in an ASP/ISP model where the signaling proxy may be owned by the ASP and the L3 (layer 3) network is owned by an ISP.
FIG. 1 shows a media management system of the preferred embodiment where media stream management functions are used for a SIP call. It only shows INVITE request processing (known as call or session signaling) since all functions can be illustrated using that request as an example (an INVITE request is an invitation from a caller 13 (media destination 12) initiating a telephone call in VoIP to a callee 17 (media source 16). The processing for responses and other requests containing media information is identical.
A media manager MM may independently exist and connects to the other components shown (SIP proxy 11 (a server), and media gateways MG1, MG2) via standard or proprietary interfaces/protocols. The media manager MM may be bundled up with the SIP proxy 11 and/or MG (media gateway) elements MG1, MG2 (See FIG. 2) as well. FIG. 1 shows the information flow which illustrates the method used and the algorithm which is common to all deployment models.
In FIG. 1 the media manager MM holds the different types of media stream information (known as “information types” hereafter) for a particular media stream relating to the service being provided. For example, these information types are typically: 1) media routing information for the stream, denoted by MR, 2) destination transport addresses for the stream denoted by RX and NRX which contain an IP address and port pair, 3) source network SRC and destination network DEST information; and 4) bandwidth B/W information.
The AS is the Application Server which controls the service, and may be bundled within the SIP proxy 11 as shown in FIG. 1, but it need not be.
In a typical SIP call, the caller 13 (media destination 12) places the call on path 14 through the SIP proxy 11 to the application server AS along path 8, then back to the SIP proxy 11 along path 9, and then to the callee 17 (media source 16) along path 15. The SIP proxy 11 sends media stream update message (arrows 2 and 4) to the media manager MM to establish information types for a media stream in the media manager MM. Thus, the media manager MM can keep track of each media stream it knows in the networks it is managing, like the ISP Network 18. If the media stream is allowed by local policy and configuration on the media manager, it sends Media Stream OK message (arrows 3 and 5) to the SIP proxy 11. Otherwise, the Media Stream OK message is not sent (details not shown) and the SIP proxy 11 may decide the handling of the call at that point based on its own policy. At the end of the call, the SIP proxy 11 deletes the information types from the media manager MM (call termination is not shown). Details of the different stored media stream information types in the media manager MM are shown in FIGS. 3A/3B, 4A/4B, and 6A/6B.
The method of FIG. 1 is applicable to both of the scenarios where 1) a media stream is routed through an intermediate system as shown in FIG. 1 (i.e., the media gateways MG1, MG2); or 2) sent directly between the caller 13 and the callee 17, the example shown in FIG. 2.
FIG. 1 will now be described in greater detail.
First call signaling will be described. The caller 13 (media destination 12) initiates a SIP INVITE on the path 14 to the SIP proxy/SBC 11 in the ASP network 10. The SIP proxy 11 is linked by paths 8, 9 to the application server AS. The application server AS and the SIP proxy 11 send the SIP INVITE along path 15 to the callee 17 (media source 16).
Now media stream flow will be described. The ISP network shows media stream flow and includes the media manager MM and media gateway MG1 linked to the caller 13 via path 19, and media gateway MG2 linked to the callee 17 via path 20.
Dashed line 21 shows the MM/MG1 interface path in the ISP network 18. Dashed line 22 shows the MM/MG2 interface path in the ISP network 18. Dashed line 7 shows the MM/SBC interface path between the ISP network media manager MM and ASP network SIP proxy/SBC 11. All three of these dashed lines are illustrated in the legend key at 26.
Dashed line 23 shows the media stream path for the media stream (RTP/UDP) from media gateway MG1 to media gateway MG2. The legend key for this dashed line is indicated at 25.
Solid lines 14, 8, 9, and 15, relating to legend key 24, indicate the path for the session (also known as call) signaling SIP/H.323/Megaco/RTSP.
As shown in FIG. 1, the media manager MM performs one or more of the following management functions: bandwidth management; media hairpin detection; media path control; equal access management; and preventing media backhauling into the ASP network 10 used for session signaling.
FIG. 2 shows a SIP call flow to illustrate hairpin detection, bandwidth management, and media backhauling prevention. The information types which are stored in the media manager MM in FIG. 2 and the information types being sent to and from the media manager are shown in FIGS. 3A/3B and FIGS. 4A/4B.
In FIGS. 2, 3A/3B, and 4A/4B, a caller 13 places a call and the application server AS (where service is controlled) detects that a caller 13 is in the same network A (27) (which can be the ISP network in FIG. 1 but with media gateways) as the callee 17. The application server AS in network E (29), which is another ISP network, routes the call back into network A. At this point, the application server AS forwards the INVITE which is sent to the callee 17.
The caller 13 and callee 17 are assumed to be in the same network A as shown at 27.
The media manager MM and the media gateway MG are shown as a bundled system 6 in this example for simplicity. The interaction between the media manager MM and media gateway MG is not the subject of this preferred embodiment, but rather the subject of this preferred embodiment are the techniques used in the media manager MM which stores media stream information types to provide the indicated management functions.
In FIG. 2, the steps which occur during session signaling when the caller places the SIP INVITE call are indicated by circles 1-6. In step 1, caller 13 initiates the SIP INVITE call on path 14 to the SIP proxy 11. In step 2 the SIP proxy 11 may send the media stream update message 2 containing information types to the media manager in the bundled network 6 via path 7. The media manager then replies with the media stream OK message 3 if the media stream is allowed. In step 3 the SIP proxy sends the SIP INVITE on path 8 to the application server AS in network E (29), and the SIP INVITE then returns on path 9 to the SIP proxy 11 (step 4). In step 5, the media manager MM in bundled system 6 may send a media stream update message 4 to the media manager. The media manager then replies with media stream OK message 5 if the media stream is allowed. Thereafter in step 6 the SIP proxy 11 forwards the SIP INVITE on path 15 in step 6 to the callee 17.
FIGS. 3A/3B and 4A/4B will now be explained. In both figures, media routing for intra-network sessions is not required by the media manager MM policy configuration. FIGS. 3A/3B is the case where the media manager has been configured to route media for calls expected to be between networks A and E. FIGS. 4A/4B is the case where this is not required and shows the difference in stored information types on the media manager MM.
In step 1, only one media stream is shown on path 14 for simplicity (call INVITE) and the receive transport address (IP address and port) of this media stream are shown as information type RX under the SDP (session description protocol) designation.
In step 2 at path 7, the media stream update message 2 has information type MR (media routing) which contains information derived by executing media routing policy for the call expected at this point to be between networks A and E. The media manager MM expects to media route this call since MR(A,E) is “on”.
In FIGS. 3A/3B and 4A/4B, the information types required for hairpin detection are: source network (Src-Network); destination network (Dest-Network); media routing (MR); and destination transport address (IP address and port) (marked as Dest IP). A port represents an end point or “channel” for network communication. Different ports allow different applications on a same computer to utilize network resources without interfering with each other.
In FIGS. 3A/3B and 4A/4B, the information types required for bandwidth management are: bandwidth (B/W) calculated when processing the event; Dest IP (with port); MR; Src-Network; and Dest-Network. The bandwidth allocated to the media stream is stored as an information type corresponding to the media stream. The information for the source and destination network of the streams may also be maintained though they can be calculated using the former stored information values.
The method for computing bandwidth for the networks can be described as follows. For all media streams maintained, the bandwidth used for source and destination networks is aggregated as well as the bandwidth used between these networks. This may be an alternative to maintaining the network at runtime.
The information types required for backhaul prevention are: the Dest-IP (with port), MR; SRC Network; and Dest Network. The media manager MM thus maintains the information types of the media stream.
The media manager MM computes various information types for the media stream as well as other objects like source and destination network or intermediate networks which it is aware the media stream will pass through. Some examples of this computation are illustrated for network A. Note that all of the computations are actually derived from the information types maintained for the media stream itself, and it can be either stored or computed on demand based on the media manager MM's knowledge of the media streams.
The media manager MM uses information from the SIP proxy 11 to determine where the media stream is destined to go (based on transport address RX) and what the tentative source network is where it will be originated (based on Call-Dest-Network). This latter source network is where the SIP proxy thinks the media stream is destined to. The media routing MR information type for the call is determined using the source and destination information type media routing—MR(A, E)=on. This preferred embodiment focuses on the use of stored media stream information types maintained on a per media stream basis to implement the management functions.
Using the media stream information types, the media manager MM can compute the bandwidth used between various networks or for a single network. For example, the bandwidth between network A and network E is 1 Mbps since it is known that there is a single media stream which is expected to exist originating from network E and terminating on network A. Note that the computation can be done for any object as long as its relationship to the media stream is known. For example the information type bandwidth (BW) can also be computed for a transit network as long as the topology is known of how the transit network is located between networks A and E.
In summary, in step 2 the SIP proxy 11 sends a media stream update message 2 containing information types for the particular media stream to the media manager which are then stored by the media manager.
Steps 3 and 4 are executed by the SIP Proxy and Application server and simply result in the SIP message to be forwarded along the indicated paths.
In step 5, the SIP proxy sends the Media Stream Update message 4 to the media manager which contains the same information it sent earlier in Step 2 to the media manager. The media manager MM finds a “hit” in its run time cache/database of media streams it knows already exists in the network A. The hit is based on either the receive address RX (IP/port information) or the unique ID (FIGS. 4A/4B). When a hit is found, the media manager MM retrieves and updates the information types it created for the media stream in previous step 2. It now knows that the source network of the media stream is where the INVITE is destined to (which is network A itself) and re-applies the media routing policy. This is the hairpinning management scenario. The MM determines by applying the policy for media routing network A, MR(A, A) and determines that it is disabled. Since media routing is no longer necessary (directed by policy in the example), the media manager MM pushes the old media destination stored in the Dest-IP information type as NRX in the Media Stream OK message 5 to the SIP Proxy 11.
In step 5, the bandwidth for network A is also updated. It is now known that there are no expected media streams between the networks A and E, and there is a single media stream within network A. So B/W(A,E)=0 Mbps and B/W(A,A)=1 Mbps.
Since the SIP proxy 11 is able to push back the old media destination in the INVITE, media backhauling to the network C (or the application server or the SIP Proxy) is prevented. In this way, it is prevented unless necessary (e.g. for private to public network calls).
For the bandwidth management function, the media manager creates an aggregated bandwidth value for at least one network from values of the bandwidth information type of at least one media stream and all additional media streams passing through the at least one network. A new media stream is disallowed from setup in the at least one network if the aggregated bandwidth value exceeds an administratively provided bandwidth value in the media manager for the at least one network. The media source and the media destination may lie in the at least one network being managed.
Also for bandwidth management, a media stream may be passing through at least two networks; and the media manager creates an aggregated bandwidth value for the at least two networks from values of the bandwidth information type of the at least one media stream and all additional media streams passing through the at least two networks.
For the media hairpin detection function the media manager detects that values of the information types source network and destination network of at least one media stream are the same.
The media manager performs the backhauling prevention function by not routing a media stream in case a management determined policy of the media manager between media source network and media destination network does not require the media stream to be routed through a media gateway.
FIG. 5 shows a media routing scenario, and more specifically a solution for media path control and equal access. Steps 1-3 are the same as in FIGS. 2 and 3A/3B. The point where it differs is steps 4 and 5, as shown in FIGS. 6A/6B.
In step 4, the application server AS or the SIP proxy 11 may decide that in fact this call needs to pass through a provider selected by the user or administrator. If this information is decided by the application server AS, it is sent in the same INVITE back to the SIP proxy 11. The SIP proxy 11 may also invoke local policy to determine that the call needs to be sent through an interim network, as well (network I).
In step 5, the same as before in FIGS. 2, 3A/3B, and 4A/4B, there is a “hit” with the previous information types stored for the existing media stream. The SIP Proxy also sends the Media Stream Update message 4 for the interim network with the Call-Interim-Network=I information type. The existing information types are updated as well as the new information types created since there is more than one media stream. As shown in FIG. 5, the new network which is inserted in the middle of the call is the IXC network I labeled 40. The media manager MM in this example inserts two media gateways MG1 and MG2 into the media stream and updates the information types with the media stream OK message 5 for the individual media streams as indicated in step 5. These media gateways MG are selected based on the information provided by the SIP Proxy in the Call-interim-Network information type. The example shows two media gateways MG1 and MG2, but in reality there could be just one or more than two. These are connected by path 43 to each other and via paths 41 and 42 to caller 13 and callee 17, respectively. The information types are updated for stream 1 and the new information types are created for stream 2 as shown. Example computations for networks A and I are shown as well.
Like for FIGS. 3A/3B, FIGS. 6A/6B show the six steps and explain the stored information types of the media manager MM, but for the equal access example of FIG. 5 as explained above.
For the media path control function the media manager based on stored information types alters media source and media destination information type values of a media stream by altering values of at least some of the stored information types of the media stream and creating a new media stream with associated information types having new values, and sending the routed receive transport address of the new media stream to the media source.
For the equal access management function the media manager inserts at least one media gateway of a long distance carrier chosen by the media destination centrally of the at least one media stream. The media manager inserts the at least one media gateway, based on provisional information stored in said media manager, by altering a value of at least one of the information types of the media stream, and sending the routed receive transport address of the media stream to the media source.
The ISP Network and the ASP network are shown separated for the preferred embodiment only; they may, however, be administratively controlled by the same entity and the separation may either not exist or be purely logical where the ASP network represents the core of the same network and the ISP network represents the access of the same network.
a protocol used between the media gateway MG and the media manager MM could be anything.
This listing of some possible variations is not intended to limit the scope of this disclosure which is showing a preferred embodiment among many possible embodiments.
In the preferred embodiment, the media manager is not required to have the capabilities of managing all the indicated functions but may perform only one of the management functions indicated.
While a preferred embodiment has been illustrated and described in detail in the drawings and foregoing description, the same is to be considered as illustrative and not restrictive in character, it being understood that only the preferred embodiment has been shown and described and that all changes and modifications that come within the spirit of the invention both now or in the future are desired to be protected.
said media manager using at least one of said stored information types for performing at least one of said management functions.
2. The method of claim 1 wherein said bandwidth management function comprises the steps of: creating an aggregated bandwidth value for said at least one network from values of said bandwidth information type of said at least one media stream and all additional media streams passing through said at least one network.
3. The method of claim 2 wherein a new media stream is disallowed from setup in said at least one network if said aggregated bandwidth value exceeds an administratively provided bandwidth value in said media manager for said at least one network.
4. The method of claim 2 wherein the media source and the media destination lie in said at least one network being managed.
5. The method of claim 1 wherein for bandwidth management, said at least one media stream is passing through at least two networks; and said media manager creates an aggregated bandwidth value for said at least two networks from values of said bandwidth information type of said at least one media stream and all additional media streams passing through said at least two networks.
6. The method of claim 1 wherein for said media hairpin detection function said media manager detects that values of the information types source network and destination network of said at least one media stream are the same.
7. The method of claim 1 wherein for the media path control function said media manager based on stored information types alters the media source and media destination information type values of said at least one media stream by altering values of at least some of the stored information types of said at least one media stream and creating a new media stream with associated information types having new values, and sending the routed receive transport address of said new media stream to the media source.
8. The method of claim 1 wherein for the equal access management function said media manager inserts at least one media gateway of a long distance carrier chosen by said media destination centrally of said at least one media stream.
9. The method of claim 8 wherein said media manager inserts said at least one media gateway, based on provisional information stored in said media manager, by altering a value of at least one of the information types of said at least one media stream, and sending the routed receive transport address of said at least one media stream to said media source.
10. The method of claim 1 wherein said media manager performs said backhauling prevention function by not routing said media stream in case a management determined policy of said media manager between said media source network and said media destination network does not require the at least one media stream to be routed through a media gateway.
11. The method of claim 1 wherein said media manager is provided inside an SIP server.
12. The method of claim 1 wherein said media manager is provided inside a media gateway.
13. The method of claim 1 wherein said at least one network has at least one media gateway and said media manager controls said at least one media gateway.
14. The method of claim 1 wherein said media manager communicates with a session server which comprises an SIP proxy.
15. The method of claim 1 wherein the media stream comprises a voice-over internet protocol media stream.
16. The method of claim 1 wherein said at least one network has at least one media gateway and the media manager is bundled with the media gateway.
17. The method of claim 1 wherein said media manager communicates with a session server which comprises an SBC server.
18. The method of claim 1 wherein said at least one network comprises an ISP network with at least one media gateway and an RTP path.
19. The method of claim 1 wherein said at least one network has no media gateways and an RTP path between the media source and the media destination.
20. The method of claim 1 wherein during a signaling session, an invitation is sent from the media destination to the session server, then to the media manager, then to the application server, then from the application server back to the session server, then through the media manager to the session server, and then to the media source.
21. The method of claim 1 wherein a session server with which said media manager communicates is in an ASP network and said media manager is in an ISP network.
22. The method of claim 1 wherein a session server and said media manager in communication with said session server are in a common network.
23. The method of claim 22 wherein a media gateway is also provided in said common network with said media manager.
24. The method of claim 1 wherein a session server is provided in communication with said media manager, and said session server sends a media stream update message to said media manager, and said media manager responds with a media stream OK message depending upon how said media manager is managing at least one of said management functions.
26. The system of claim 25 wherein said bandwidth management function comprises: creating an aggregated bandwidth value for said at least one network from values of said bandwidth information type of said at least one media stream and all additional media streams passing through said at least one network.
27. The system of claim 26 wherein a new media stream is disallowed from setup in said at least one network if said aggregated bandwidth value exceeds an administratively provided bandwidth value in said media manager for said at least one network.
28. The system of claim 26 wherein the media source and the media destination lie in said at least one network being managed.
29. The system of claim 25 wherein for bandwidth management, said media stream is passing through at least two networks; and said media manager creates an aggregated bandwidth value for said at least two networks from values of said bandwidth information type of said at least one media stream and all additional media streams passing through said at least two networks.
30. The system of claim 25 wherein for said media hairpin detection function said media manager detects that values of the information types source network and destination network of said at least one media stream are the same.
31. The system of claim 25 wherein for the media path control function said media manager based on stored information types alters the media source and media destination information type values of said at least one media stream by altering values of at least some of the stored information types of said at least one media stream and creating a new media stream with associated information types having new values, and sending the routed receive transport address of said new media stream to the media source.
32. The system of claim 25 wherein for the equal access management function said media manager inserts at least one media gateway of a long distance carrier chosen by said media destination centrally of said at least one media stream.
33. The system of claim 32 wherein said media manager inserts said at least one media gateway, based on provisional information stored in said media manager, by altering a value of at least one of the information types of said media stream, and sending the routed receive transport address of said media stream to said media source.
34. The system of claim 25 wherein said media manager performs said backhauling prevention function by not routing said media at least one stream in case a management determined policy of said media manager between said media source network and said media destination network does not require the media stream to be routed through a media gateway.
using at least one of said media manager stored information types for performing at least one of said management functions.
36. The computer program product of claim 35 wherein said bandwidth management function comprises the steps of: creating an aggregated bandwidth value for said at least one network from values of said bandwidth information type of said at least one media stream and all additional media streams passing through said at least one network.
37. The computer program product of claim 36 wherein a new media stream is disallowed from setup in said at least one network if said aggregated bandwidth value exceeds an administratively provided bandwidth value in said media manager for said at least one network.
38. The computer program product of claim 36 wherein the media source and the media destination lie in said at least one network being managed.
39. The computer program product of claim 35 wherein for bandwidth management, said media stream is passing through at least two networks; and said media manager creates an aggregated bandwidth value for said at least two networks from values of said bandwidth information type of said at least one media stream and all additional media streams passing through said at least two networks.
40. The computer program product of claim 35 wherein for said media hairpin detection function said media manager detects that values of the information types source network and destination network of said at least one media stream are the same.
41. The computer program product of claim 35 wherein for the media path control function said media manager based on stored information types alters the media source and media destination information type values of said at least one media stream by altering values of at least some of the stored information types of said at least one media stream and creating a new media stream with associated information types having new values, and sending the routed receive transport address of said new media stream to the media source.
42. The computer program product of claim 35 wherein for the equal access management function said media manager inserts at least one media gateway of a long distance carrier chosen by said media destination centrally of said at least one media stream.
43. The computer program product of claim 42 wherein said media manager inserts said at least one media gateway, based on provisional information stored in said media manager, by altering a value of at least one of the information types of said at least one media stream, and sending the routed receive transport address of said media stream to said media source.
44. The computer program product of claim 35 wherein said media manager performs said backhauling prevention function by not routing said media stream in case a management determined policy of said media manager between said media source network and said media destination network does not require the media stream to be routed through a media gateway.
"Denial of Service-Understanding Attack Techniques," White Paper (Jun. 22, 2005).
"Kagoor Delivers New XpressPath Media Routing," Enterprise Networks and Servers, http://www.enterprisenetworksandservers.com/monthly/art.php/.800, p. 1 (Jul. 2004).
"Media Access Control (MAC) Bridges," IEEE 802.1D Standard for Local and Metropolitan Area Networks (Jun. 9, 2004).
"Packet Voice Over Broadband," Light Reading-Networking the Telecom Industry (Mar. 3, 2005).
"SDP: Session Description Protocol Overview (RFC 2327)," Javvin Network Management & Security (Downloaded from the Internet Aug. 15, 2005).
"Session Border Controller," YENRA, http://www.yenra.com/session-border-controller/, pp. 1-2 (Oct. 18, 2004).
"Session Control in IMS Architecture," Newport Networks, White Papers (Copyright 2002-2005).
"The E-Model, a Computational Model for use in Transmission Planning, " ITU-T, G.107, pp. 1-25 (Dec. 1998).
"Virtual Bridged Local Area Networks," IEEE Standards 802.1Q, pp. 1-327 (May 7, 2003).
"Denial of Service—Understanding Attack Techniques," White Paper (Jun. 22, 2005).
"Packet Voice Over Broadband," Light Reading—Networking the Telecom Industry (Mar. 3, 2005).
Acme Packet, Inc., "Session Admission control: Interactive communication SLAs over Skinny Pipes," 14 pages (2002).
Advisory Action Before the Filing of Appeal Brief and Examiner-Initiated interview Summary for U.S. Appl. No. 11/427,220 (Jun. 15, 2016).
Advisory Action for U.S. Appl. No. 11/427,220 (May 8, 2014).
Applicant-Initiated Interview Summary for U.S. Appl. No. 11/427,220 (Apr. 29, 2014).
Applicant-Initiated Interview Summary for U.S. Appl. No. 11/427,234 (Mar. 15, 2012).
Applicant-Initiated Interview Summary for U.S. Appl. No. 12/748,321 (Mar. 29, 2012).
Bond et al., "An Open Architecture for Next-Generation Telecommunication Services," ACM Transactions on Internet Technology, vol. 4, No. 1, pp. 83-123 (Feb. 2004).
Communication of European Publication Number and Information on the Application of Article 67(3) EPC for European Patent No. 1969788 (Aug. 20, 2008).
Communication pursuant to Article 94(3) EPC for Application No, 05 763 863.7 (Apr. 17, 2014).
Corrected Notice of Allowability for U.S. Appl. No. 11/427,234 (Jul. 16, 2012).
Crocker, D., "ARPA Internet Text Messages," RFC 822 (Aug. 13, 1982).
Decision to Grant a Patent for Japanese Patent Application No. 2007-549342 (Sep. 1, 2010).
Distributed Denial of Service Attacks, White Paper: Prolexic Technologies, Inc., Q4 (2004).
Extended European Search Report for European Application No. 06845686.2 (Mar. 6, 2014).
Final Office Action for U.S. Appl. No. 11/314,119 (Jul. 1, 2014).
Final Office Action for U.S. Appl. No. 11/427,200 (Nov. 20, 2009).
Final Office Action for U.S. Appl. No. 11/427,220 (Feb. 12, 2016).
Final Office Action for U.S. Appl. No. 11/427,220 (Feb. 28, 2014).
Final Office Action for U.S. Appl. No. 14/266,790 (Dec. 30, 2016).
Final Official Action for U.S. Appl. No. 11/026,746 (Jan. 4, 2011).
Final Official Action for U.S. Appl. No. 11/314,119 (Oct. 14, 2010).
Final Official Action for U.S. Appl. No. 11/427,171 (Dec. 22, 2010).
Final Official Action for U.S. Appl. No. 11/427,220 (Jan. 18, 2011).
Final Official Action for U.S. Appl. No. 11/427,234 (Jun. 15, 2011).
Final Official Action for U.S. Appl. No. 12/748,321 (Dec. 21, 2011).
First Examination Report for Indian Application No. 5066/DELNP/2007 (Jun. 19, 2015).
First Office Action for Chinese Application No. 200580048016.9 (Oct. 27, 2011).
Gallon et al., "Bandwidth Management in Next Generation Packet Networks," MSF Technical Report, MSF-TR-ARCH-005-FINAL, MultiService Forum (Aug. 2005).
Garcia-Martin et al., "Private Header (P-Header) Extensions to the Session Initiation Protocol (SIP) for the 3rd-Generation Partnership Project (3GPP)," RFC 3455, pp. 1-34 (Jan. 2003).
Handley et al., "SDP: Session Description Protocol," RFC 2327, pp. 1-40 (Apr. 1998).
Handley et al., "SIP: Session Initiation Protocol," RFC 2543, pp. 1-143 (Mar. 1999).
Hayes, "IP Based Multimedia Services Platform," Ericsson, 3GPP, ITU-T IMT-2000 and Beyond, Ottawa, Canada, 19 pages (May 28, 2002).
Intel, "Intel IXP2400 Network Processor Datasheet," Document No. 301164-011, pp. 1-126 (Feb. 2004).
International Search Report and Written Opinion for International Application No. PCT/US05/18870 (Oct. 31, 2005).
Interview Summary for U.S. Appl. No. 11/314,119 (Dec. 28, 2010).
Interview Summary for U.S. Appl. No. 11/427,171 (Apr. 13, 2011).
Interview Summary for U.S. Appl. No. 11/427,171 (Oct. 13, 2010).
Interview Summary for U.S. Appl. No. 11/427,200 (Jul. 14, 2008).
Interview Summary for U.S. Appl. No. 11/427,200 (Oct. 27, 2008).
Interview Summary for U.S. Appl. No. 11/427,220 (Apr. 27, 2011).
Interview Summary for U.S. Appl. No. 11/427,234 (Mar. 29, 2011).
Interview Summary for U.S. Appl. No. 12/748,321 (Sep. 6, 2011).
Le et al., "A Review of Mobility Support Paradigms for the Internet" (Jan. 2005).
Non-Final Office Action for U.S. Appl. No. 11/314,119 (Sep. 12, 2013).
Non-Final Office Action for U.S. Appl. No. 11/427,220 (Jul. 15, 2015).
Non-Final Office Action for U.S. Appl. No. 11/427,220 (Jul. 16, 2013).
Non-Final Office Action for U.S. Appl. No. 12/748,321 (Jul. 17, 2013).
Non-Final Office Action for U.S. Appl. No. 14/266,790 (Apr. 8, 2016).
Non-Final Official Action for U.S. App. No. 11/427,234 (Nov. 9, 2011).
Non-Final Official Action for U.S. Appl. No. 10/596,904 (May 11, 2011).
Non-Final Official Action for U.S. Appl. No. 11/026,746 (Jul. 9, 2010).
Non-Final Official Action for U.S. Appl. No. 11/026,746 (Jun. 17, 2011).
Non-Final Official Action for U.S. Appl. No. 11/314,119 (Apr. 1, 2010).
Non-Final Official Action for U.S. Appl. No. 11/427,171 (Jun. 21, 2010).
Non-Final Official Action for U.S. Appl. No. 11/427,171 (Jun. 9, 2010).
Non-Final Official Action for U.S. Appl. No. 11/427,220 (Jul. 7, 2010).
Non-Final Official Action for U.S. Appl. No. 11/427,234 (Oct. 18, 2010).
Non-Final Official Action for U.S. Appl. No. 12/748,321 (May 23, 2011).
Non-Final Rejection for U.S. Appl. No. 13/436,813 (Feb. 21, 2013).
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 11/026,746 (Dec. 12, 2011).
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 11/427,171 (May 23, 2013).
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 11/427,200 (Jun. 2, 2011).
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 11/427,234 (Apr. 23, 2012).
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 12/748,321 (Feb. 19, 2014).
Notice of Allowance and Fee(s) Due for U.S. Appl. No. 13/436,813 (Jan. 22, 2014).
Notice of Allowance for U.S. Appl. No. 11/314,119 (Jan. 5, 2015).
Notification of European publication number and information on the application of Article 67(3) EPC for European Application No. 05763863.7 (Aug. 16, 2007).
Notification of Second Office Action for Chinese Application No. 200580048016.9 (Sep. 3, 2012).
Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, or the Declaration for International Application No. PCT/US2006/048166 (Nov. 10, 2008).
Notification to Make Divisional Application for Chinese Application No. 200580048016 (Apr. 7, 2010).
Office Action for Japanese Patent Application No. 2007-549342 (May 13, 2010).
Office Action for U.S. Appl. No. 11/427,200 (Apr. 18, 2008).
Office Action for U.S. Appl. No. 11/427,200 (Feb. 6, 2009).
Office Action for U.S. Appl. No. 11/427,200 (Sep. 28, 2007).
Official Action for U.S. Appl. No. 11/026,746 (Dec. 23, 2009).
Restriction Requirement for U.S. Appl. No. 11/026,746 (Apr. 2, 2009).
Restriction Requirement for U.S. Appl. No. 11/026,746 (Sep. 2, 2009).
Rosenberg et al., "An Extension to the Session Initiation Protocol (SIP) for Symmetric Response Routing," RFC 3581, pp. 1-13 (Aug. 2003).
Rosenberg et al., "An Offer/Answer Model with the Session Description Protocol (SDP)," RFC 3264 (Jun. 2002).
Rosenberg et al., "Session Initiation Protocol (SIP): Locating SIP Servers," RFC 3263, pp. 1-16 (Jun. 2002).
Rosenberg et al., "SIP: Session Initiation Protocol," RFCc 3261, pp. 1-252 (Jun. 2002).
Rosenberg, "The Real Time Transport Protocol (RTP) Denial of Service (Dos) Attack and its Prevention," pp. 1-6 (Jun. 23, 2003).
Schulzrinne et al., "RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals," Network Work Group, RFC 2833 (May 2000).
Schulzrinne et al., "RTP: A Transport Protocol for Real-Time Application," Network Working Group, RFC 3550 (Jul. 2003).
Sisalem et al., "Denial of Service Attacks and SIP Infrastructure," 2003.
Supplementary European Search Report for European Application No. 05763863.7 (Feb. 16, 2012).
Walker et al., "Release 2 Architecture," MSF Release 2 Architecture, MSF-ARCH-002.00-FINAL, Multiservice Switching Forum (Jan. 4, 2005).

References: Application No. 2007
 Application No. 06845686
 Application No. 5066
 Application No. 200580048016
 Application No. 05763863
 Application No. 200580048016
 Application No. 200580048016
 Application No. 2007
 Application No. 05763863