Patent Grant
9060047
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.
Before discussing further the media communication problems of bandwidth, hairpinning, equal access, and backhauling, the following acronyms used hereafter are identified for convenience:
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.
In attempting to deal with the aforementioned and described media stream management problems of bandwidth, hairpinning, media path control, equal access, and/or backhauling, it has previously been known to provide at least the following types 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, including 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, the 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. 3A/3B show the six steps and the different types of information for the particular media stream present, which are stored in the media manager in
FIGS. 4A/4B show the six steps for a scenario where the media routing policy on the media manager MM for caller to external networks is different and this results in different information maintained by the media manager MM for some stages of INVITE processing (note that in the end, both FIGS. 4A/4B result in the same effect as FIGS. 3A/3B since the policy in the media manager MM for network A to network A calls is the same for the two cases);
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
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.
An overview of the management methods of the preferred embodiment, described hereafter in greater detail, is as follows:
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
In
The AS is the Application Server which controls the service, and may be bundled within the SIP proxy 11 as shown in
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
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
In
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
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 step 2 the media manager MM also sends the Media Stream OK message 3 to the SIP proxy if the media stream satisfies the local policy configuration on the media manager MM. For example, if the B/W(A,E) and B/W(A,A) are within configured limits on the media manager MM, the OK message 3 is sent. The Media Stream OK message 3 also contains the transport address NRX (See
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.
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
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
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 method of the preferred embodiment is equally applicable for any session layer protocols like SIP, H.323, RTSP, MGCP, Megaco carrying session layer media information in protocols like SDP, H.245 and new versions of SDP being developed at the IETF (Internet Engineering Task Force)
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.
Some of the variations, among many other possible variations, in the above preferred embodiment method are:
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.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4164193 | Smith | Aug 1979 | A |
| 5918020 | Blackard et al. | Jun 1999 | A |
| 6473793 | Dillon et al. | Oct 2002 | B1 |
| 6570855 | Kung et al. | May 2003 | B1 |
| 6600737 | Lai et al. | Jul 2003 | B1 |
| 6678359 | Gallick | Jan 2004 | B1 |
| 6738808 | Zellner et al. | May 2004 | B1 |
| 6775269 | Kaczmarczyk et al. | Aug 2004 | B1 |
| 6775280 | Ma et al. | Aug 2004 | B1 |
| 6798786 | Lo et al. | Sep 2004 | B1 |
| 6904017 | Meempat et al. | Jun 2005 | B1 |
| 6925461 | Byers | Aug 2005 | B2 |
| 6944678 | Lu et al. | Sep 2005 | B2 |
| 6980526 | Jang et al. | Dec 2005 | B2 |
| 7002973 | MeLampy et al. | Feb 2006 | B2 |
| 7028092 | MeLampy et al. | Apr 2006 | B2 |
| 7031311 | MeLampy et al. | Apr 2006 | B2 |
| 7072303 | MeLampy et al. | Jul 2006 | B2 |
| 7116767 | Yang et al. | Oct 2006 | B2 |
| 7133923 | MeLampy et al. | Nov 2006 | B2 |
| 7142532 | Penfield et al. | Nov 2006 | B2 |
| 7151781 | MeLampy et al. | Dec 2006 | B2 |
| 7180993 | Hamilton | Feb 2007 | B2 |
| 7193996 | Dobbins et al. | Mar 2007 | B2 |
| 7260060 | Abaye et al. | Aug 2007 | B1 |
| 7260085 | Dobbins et al. | Aug 2007 | B2 |
| 7277384 | Chan et al. | Oct 2007 | B1 |
| 7289489 | Kung et al. | Oct 2007 | B1 |
| 7411975 | Mohaban | Aug 2008 | B1 |
| 7457312 | Weiss et al. | Nov 2008 | B2 |
| 7512078 | Swain et al. | Mar 2009 | B2 |
| 7739395 | Parlamas et al. | Jun 2010 | B1 |
| 7974394 | Cao et al. | Jul 2011 | B1 |
| 8085758 | Ramachandran et al. | Dec 2011 | B2 |
| 8194640 | Ramachandran et al. | Jun 2012 | B2 |
| 8254265 | Ramachandran et al. | Aug 2012 | B2 |
| 8547962 | Ramachandran et al. | Oct 2013 | B2 |
| 8743870 | Ramachandran et al. | Jun 2014 | B2 |
| 8755371 | Ramachandran et al. | Jun 2014 | B2 |
| 20010050911 | Eastman | Dec 2001 | A1 |
| 20020062376 | Isoyama | May 2002 | A1 |
| 20020129236 | Nuutinen | Sep 2002 | A1 |
| 20020136206 | Gallant et al. | Sep 2002 | A1 |
| 20020181427 | Sparr et al. | Dec 2002 | A1 |
| 20030016627 | MeLampy et al. | Jan 2003 | A1 |
| 20030051130 | MeLampy et al. | Mar 2003 | A1 |
| 20030137942 | Ladegaard | Jul 2003 | A1 |
| 20030142681 | Chen et al. | Jul 2003 | A1 |
| 20030145077 | Khan et al. | Jul 2003 | A1 |
| 20030186702 | McConnell et al. | Oct 2003 | A1 |
| 20030206546 | Beyda | Nov 2003 | A1 |
| 20040005041 | Azami | Jan 2004 | A1 |
| 20040005892 | Mayer et al. | Jan 2004 | A1 |
| 20040009776 | Ishikawa et al. | Jan 2004 | A1 |
| 20040010514 | Agarwal et al. | Jan 2004 | A1 |
| 20040045030 | Reynolds et al. | Mar 2004 | A1 |
| 20040072593 | Robbins et al. | Apr 2004 | A1 |
| 20040086093 | Schranz | May 2004 | A1 |
| 20040152422 | Hoglund et al. | Aug 2004 | A1 |
| 20040156491 | Reding et al. | Aug 2004 | A1 |
| 20040196867 | Ejzak et al. | Oct 2004 | A1 |
| 20040224678 | Dahod et al. | Nov 2004 | A1 |
| 20040249927 | Pezutti | Dec 2004 | A1 |
| 20040266426 | Marsh et al. | Dec 2004 | A1 |
| 20050021804 | Hameleers et al. | Jan 2005 | A1 |
| 20050025123 | Mitsumori et al. | Feb 2005 | A1 |
| 20050041648 | Bharatia et al. | Feb 2005 | A1 |
| 20050052993 | Hanks et al. | Mar 2005 | A1 |
| 20050052996 | Houck et al. | Mar 2005 | A1 |
| 20050070230 | Das et al. | Mar 2005 | A1 |
| 20050074026 | Soncodi et al. | Apr 2005 | A1 |
| 20050078690 | DeLangis | Apr 2005 | A1 |
| 20050083895 | Pinault | Apr 2005 | A1 |
| 20050084088 | Hamilton | Apr 2005 | A1 |
| 20050089014 | Levin et al. | Apr 2005 | A1 |
| 20050108567 | D'Souza et al. | May 2005 | A1 |
| 20050111382 | Le et al. | May 2005 | A1 |
| 20050185657 | Karanassos | Aug 2005 | A1 |
| 20050207358 | Nishida et al. | Sep 2005 | A1 |
| 20060045095 | Dhar et al. | Mar 2006 | A1 |
| 20060067298 | Houck et al. | Mar 2006 | A1 |
| 20060083193 | Womack et al. | Apr 2006 | A1 |
| 20060093115 | Chen et al. | May 2006 | A1 |
| 20060098577 | MeLampy et al. | May 2006 | A1 |
| 20060117097 | Ogasawara et al. | Jun 2006 | A1 |
| 20060146792 | Ramachandran et al. | Jul 2006 | A1 |
| 20060159129 | Schmidt | Jul 2006 | A1 |
| 20060178130 | Makrygiannis | Aug 2006 | A1 |
| 20060218268 | Beck et al. | Sep 2006 | A1 |
| 20060239255 | Ramachandran et al. | Oct 2006 | A1 |
| 20060259958 | Jennings et al. | Nov 2006 | A1 |
| 20060285493 | Manuja et al. | Dec 2006 | A1 |
| 20060291447 | Siliquini et al. | Dec 2006 | A1 |
| 20060291450 | Ramachandran et al. | Dec 2006 | A1 |
| 20070019563 | Ramachandran et al. | Jan 2007 | A1 |
| 20070019625 | Ramachandran et al. | Jan 2007 | A1 |
| 20070036151 | Baeder | Feb 2007 | A1 |
| 20070076591 | Khan | Apr 2007 | A1 |
| 20070076594 | Khan et al. | Apr 2007 | A1 |
| 20070076603 | MeLampy et al. | Apr 2007 | A1 |
| 20070076710 | Khan | Apr 2007 | A1 |
| 20070076855 | MeLampy et al. | Apr 2007 | A1 |
| 20070104105 | MeLampy et al. | May 2007 | A1 |
| 20070116043 | MeLampy et al. | May 2007 | A1 |
| 20070156491 | Schuler et al. | Jul 2007 | A1 |
| 20070286158 | Cook | Dec 2007 | A1 |
| 20070291734 | Bhatia et al. | Dec 2007 | A1 |
| 20080086564 | Putman et al. | Apr 2008 | A1 |
| 20080239957 | Tokura et al. | Oct 2008 | A1 |
| 20100309906 | Ramachandran et al. | Dec 2010 | A1 |
| 20120189001 | Ramachandran et al. | Jul 2012 | A1 |
| 20140321453 | Ramachandran et al. | Oct 2014 | A1 |
| Number | Date | Country |
|---|---|---|
| 1556655 | Dec 2004 | CN |
| 1 263 242 | Dec 2002 | EP |
| WO 0249279 | Jun 2002 | WO |
| WO 0249315 | Jun 2002 | WO |
| WO 0249316 | Jun 2002 | WO |
| WO 02058349 | Jul 2002 | WO |
| WO 2006073481 | Jul 2006 | WO |
| Entry |
|---|
| IP Based Multimedia Services Platform—Stephen Hayes May 28, 2002. |
| Session Admission Control: Interactive Communication SLAs over Skinny pipes 2002. |
| 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). |
| 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/427,220 (Jul. 7, 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). |
| Office Action for Japanese Patent Application No. 2007-549342 (May 13, 2010). |
| Notification to Make Divisional Application for Chinese Application No. 200580048016 (Apr. 7, 2010). |
| Official Action for U.S. Appl. No. 11/026,746 (Dec. 23, 2009). |
| Final Office Action for U.S. Appl. No. 11/427,200 (Nov. 20, 2009). |
| Restriction Requirement for U.S. Appl. No. 11/026,746 (Sep. 2, 2009). |
| Restriction Requirement for U.S. Appl. No. 11/026,746 (Apr. 2, 2009). |
| Office Action for U.S. Appl. No. 11/427,200 (Feb. 6, 2009). |
| Interview Summary for U.S. Appl. No. 11/427,200 (Oct. 27, 2008). |
| Communication of European Publication No. And Information on the Application of Article 67(3) EPC for European Patent No. 1969788 (Aug. 20, 2008). |
| Interview Summary for U.S. Appl. No. 11/427,200 (Jul. 14, 2008). |
| Office Action for U.S. Appl. No. 11/427,200 (Apr. 18, 2008). |
| Office Action for U.S. Appl. No. 11/427,200 (Sep. 28, 2007). |
| International Search Report and Written Opinion for International Application No. PCT/US05/18870 (Oct. 31, 2005). |
| Gallon et al., “Bandwidth Management in Next Generation Packet Networks,” MSF Technical Report, MSF-TR-ARCH-005-FINAL, MultiService Forum (Aug. 2005). |
| “Denial of Service—Understanding Attack Techniques,” White Paper (Jun. 22, 2005). |
| “Packet Voice Over Broadband,” Light Reading—Networking the Telecom Industry (Mar. 3, 2005). |
| Walker et al., “Release 2 Architecture,” MSF Release 2 Architecture, MSF-ARCH-002.00-FINAL, Multiservice Switching Forum (Jan. 4, 2005). |
| Le et al., “A Review of Mobility Support Paradigms for the Internet” (Jan. 2005). |
| “Session Border Controller,” YENRA, http://www.yenra.com/session-border-controller/, pp. 1-2 (Oct. 18, 2004). |
| “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). |
| Intel, “Intel IXP2400 Network Processor Datasheet,” Document Number: 301164-011, pp. 1-126 (Feb. 2004). |
| Distributed Denial of Service Attacks, White Paper: Prolexic Technologies, Inc., Q4 (2004). |
| Rosenberg et al., “An Extension to the Session Initiation Protocol (SIP) for Symmetric Response Routing,” RFC 3581, pp. 1-13 (Aug. 2003). |
| Schulzrinne et al., “RTP: A Transport Protocol for Real-Time Application,” Network Working Group, RFC 3550 (Jul. 2003). |
| Rosenberg, “The Real Time Transport Protocol (RTP) Denial of Service (DOS) Attack and its Prevention,” pp. 1-6 (Jun. 23, 2003). |
| “Virtual Bridged Local Area Networks,” IEEE Standards 802.1Q, pp. 1-327 (May 7, 2003). |
| Garcia-Martin at 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). |
| Sisalem et al., “Denial of Service Attacks and SIP Infrastructure” (2003). |
| Rosenberg et al., “An Offer/Answer Model with the Session Description Protocol (SDP),” RFC 3264 (Jun. 2002). |
| Rosenberg et al., “SIP: Session Initiation Protocol,” RFC 3261, pp. 1-252 (Jun. 2002). |
| Rosenberg et al., “Session Initiation Protocol (SIP): Locating SIP Servers,” RFC 3263, pp. 1-16 (Jun. 2002). |
| “Session Control in IMS Architecture,” Newport Networks, White Papers (Copyright 2002-2005). |
| Schulzrinne at al., “RTP Payload for DTMF Digits, Telephony Tones and Telephony Signals,” Network Work Group, RFC 2833 (May 2000). |
| Handley at al., “SIP: Session Initiation Protocol,” RFC 2543, pp. 1-143 (Mar. 1999). |
| “The E-Model, a Computational Model for use in Transmission Planning,” ITU-T, (Dec. 1998). G.107, pp. 1-25. |
| Handley et al., “SDP: Session Description Protocol,” RFC 2327, pp. 1-40 (Apr. 1998). |
| Crocker, D., “ARPA Internet Text Messages,” RFC 822 (Aug. 13, 1982). Network. |
| “SDP: Session Description Protocol Overview (RFC 2327),” Javvin Network Management & Security(Downloaded from the Internet Aug. 15, 2005). |
| Interview Summary for U.S. Appl. No. 12/748,321 (Sep. 6, 2011). |
| Non-Final Official Action for U.S. Appl. No. 11/026,746 (Jun. 17, 2011). |
| Final Official Action for U.S. Appl. No. 11/427,234 (Jun. 15, 2011). |
| Notice of Allowance and Fee(s) Due for U.S. Appl. No. 11/427,200 (Jun. 2, 2011). |
| Non-Final Official Action for U.S. Appl. No. 12/748,321 (May 23, 2011). |
| Non-Final Official Action for U.S. Appl. No. 10/596,904 (May 11, 2011). |
| Interview Summary for U.S. Appl. No. 11/427,220 (Apr. 27, 2011). |
| Interview Summary for U.S. Appl. No. 11/427,171 (Apr. 13, 2011). |
| Interview Summary for U.S. Appl. No. 11/427,234 (Mar. 29, 2011). |
| Notification of European publication number and information on the application of Article 67(3) EPC for European Application No. 05763863.7 (Aug. 16, 2007). |
| Non-Final Rejection for U.S. Appl. No. 13/436,813 (Feb. 21, 2013). |
| Notification of Second Office Action for Chinese Application No. 200580048016.9 (Sep. 3, 2012). |
| Corrected Notice of Allowability for U.S. Appl. No. 11/427,234 (Jul. 16, 2012). |
| Notice of Allowance and Fee(s) Due for U.S. Appl. No. 11/427,234 (Apr. 23, 2012). |
| Applicant-Initiated Interview Summary for U.S. Appl. No. 12/748,321 (Mar. 29, 2012). |
| Final Official Action for U.S. Patent Application Final Official Action for U.S. Appl. No. 11/026,746 (Jan. 4, 2011). |
| Final Official Action for U.S. Appl. No. 11/427,171 ( Dec. 22, 2010). |
| Non-Final Official Action for U.S. Appl. No. 11/427,234 (Oct. 18, 2010). |
| Interview Summary for U.S. Appl. No. 11/427,171 (Oct. 13, 2010). |
| Decision to Grant a Patent for Japanese Patent Application No. 2007-549342 (Sep. 1, 2010). |
| Interview Summary for U.S. Patent Application U.S. Appl. No. 11/427,171 (Apr. 13, 2011). |
| Final Official Action for U.S. Appl. No. 11/427,220 (Jan. 18, 2011). |
| Applicant-Initiated Interview Summary for U.S. Appl. No. 11/427,234 (Mar. 15, 2012). |
| Supplementary European Search Report for European Application No. 05763863.7 (Feb. 16, 2012). |
| Final Official Action for U.S. Appl. No. 12/748,321 (Dec. 21, 2011). |
| Notice of Allowance and Fee(s) Due for U.S. Appl. No. 11/026,746 (Dec. 12, 2011). |
| Non-Final Official Action for U.S. Appl. No. 11/427,234 (Nov. 9, 2011). |
| First Office Action for Chinese Application No. 200580048016.9 (Oct. 27, 2011). |
| Notice of Allowance and Fee(s) Due for U.S. Appl. No. 13/436,813 (Jan. 22, 2014). |
| Non-Final Office Action for U.S. Appl. No. 12/748,321 (Jul. 17, 2013). |
| Non-Final Office Action for U.S. Appl. No. 11/427,220 (Jul. 16, 2013). |
| Notice of Allowance and Fee(s) Due for U.S. Appl. No. 11/427,171 (May 23, 2013). |
| 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). |
| Communication pursuant to Article 94(3) EPC for Application No. 05 763 863.7 (Apr. 17, 2014). |
| Extended European Search Report for European Application No. 06845686.2 (Mar. 6, 2014). |
| Final Office Action for U.S. Appl. No. 11/427,220 (Feb. 28, 2014). |
| Notice of Allowance and Fee(s) Due for U.S. Appl. No. 12/748,321 (Feb. 19, 2014). |
| 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). |
| Number | Date | Country | |
|---|---|---|---|
| 20070140223 A1 | Jun 2007 | US |
