Source: https://patents.google.com/patent/US8543667B2/en
Timestamp: 2019-05-22 23:17:32
Document Index: 621270683

Matched Legal Cases: ['art 600', 'art 600', 'art 600', 'art 700', 'art 700', 'art 700']

US8543667B2 - Policy-based content insertion - Google Patents
Policy-based content insertion Download PDF
US8543667B2
US8543667B2 US12/013,756 US1375608A US8543667B2 US 8543667 B2 US8543667 B2 US 8543667B2 US 1375608 A US1375608 A US 1375608A US 8543667 B2 US8543667 B2 US 8543667B2
US12/013,756
US20090182843A1 (en
2008-01-14 Application filed by Akamai Technologies Inc filed Critical Akamai Technologies Inc
2008-01-14 Priority to US12/013,756 priority Critical patent/US8543667B2/en
2008-01-29 Assigned to VERIVUE, INC. reassignment VERIVUE, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: HLUCHYJ, MICHAEL G., PAI, GANESH, REDDY, UMAMAHESWAR
2009-07-16 Publication of US20090182843A1 publication Critical patent/US20090182843A1/en
2013-09-24 Publication of US8543667B2 publication Critical patent/US8543667B2/en
Described are computer-based methods and apparatuses, including computer program products, for policy-based content insertion. A client device transmits to a content server a request for the delivery of content. The content server modifies the request based on an ingress policy. The content server transmits the modified request to a second server where the second server processes the request. The second server transmits a reply to the modified request to the content server. The reply includes a content insertion instruction. The content server transmits the content to the client device based on the content insertion instruction and/or one or more egress policies.
The present invention relates generally to computer-based methods and apparatuses, including computer program products, for policy-based content insertion.
The Internet has evolved from a network that provided for simple messaging, file transfer, and remote access to one of a full multimedia experience through the use of web servers and client browsers. Hyper Text Transfer Protocol (HTTP) is the preferred protocol used between a web server and client browser where a client issues HTTP requests (e.g., GET) and the web server responds with HTTP responses (e.g., 200 OK) containing optional data contents. The optional data contents are usually web pages such as Hypertext Markup Language (HTML) documents and linked objects (such as images and videos).
The use of linked objects within a web page makes for a flexible and dynamic conveyance of information. A web page served to a client from one web server may contain linked objects whereby the client browser automatically retrieves content from one or more other web servers to complete the web page. Also, a web server may redirect a client request via a redirect response (such as HTTP 300 Redirect) to another web server. In both cases, this provides a degree of scalability where content can be distributed among multiple web servers and then used in the composition of multiple and potentially different web pages.
The content delivered to a web client has changed from sending only HTML text to sending multimedia content such as sound, images, and/or video. Typically, multimedia content is much larger in size compared to HTML files. Also, the streaming rate and corresponding multimedia content file sizes have increased dramatically from early Internet video displayed in a small 160×120 window at 40 kb/s to 720×480 video streamed at 700 kb/s today going to high definition (HD) 1920×1080 video streamed at 5 Mb/s or greater. As the amount of content that needs to be delivered to support a client request increases, the web server typically needs the ability to read content faster from storage and provide the necessary high-speed protocol processing used to deliver the content to the client. As the number of clients requesting content from a web server increases, the ability to deliver content to each requesting client can be an issue. The situation is compounded by the diversity of requests, as now the web server has to have access to a large library of content to serve these requests. A large library also translates to complex management and layout of content in storage. With the proliferation of streaming video on the internet, not only the size and streaming rate of the content are significantly larger, the content typically must be delivered to the client at a steady rate. Any decrease in the transfer rate from the desired rate can cause interruptions in the client viewing experience, thereby decreasing the overall quality of the experience.
Scalability of web servers can be further achieved using proxy servers. Typically, a proxy server is a server that services the requests of clients by forwarding the requests to other servers. A forward proxy server sits in front of a client and forwards all request from the client to the designated servers. A forward proxy server is typically used in an enterprise to provide some degree of security and hiding of clients from external servers. Reverse proxy servers sit in front of a group of web servers and are often used to load balance client requests among the multiple servers in the group each capable of serving the request. A reverse proxy can be policy-based where current load, language, source address, and/or browser cookie, to name a few examples, are used to route a request to a specific server in the group. A reverse proxy server may also include functions such as security, encryption, compression, and caching of content as a means to off-load the processing work of a web server. In the case of caching, the proxy server is able to serve requests for which it has cached the requested content (typically static content), thus off-loading the request from the web server. Here, the client request is not delivered to the web server, but is handled entirely by the proxy server using its content cache. For functions such as security, encryption and compression, the proxy serves as a pre-processing stage for the client requests and a post-processing stage for the web server responses, where all content is still delivered from the web server.
FIG. 1 illustrates a web server and a web client known in the art. The web client issues an HTTP GET request to a web server, where the Uniform Resource Locator (URL) of the content being requested is a part of the GET request. The URL is used to deliver the GET request to the right application (e.g., database application, map application, etc.) on the web server. The application on the web server applies application logic to determine if the request is to be fulfilled and, if so, the application determines the content file, the bit rate, and any other associated attributes. The application then instructs the web server to stream the file to the client based on the determined attributes. The web server constructs a 200 OK response along with the content inserted at the end of the 200 OK message. The client uses the flow control provided by transmission control protocol (TCP) to pace the rate at which it consumes the content. The client displays the content to the end user at the encoded frame rate.
FIG. 2 illustrates a web server, a proxy server, and a web client known in the art. The proxy server can operate as a reverse proxy providing a content cache. The HTTP GET request from the client is analyzed by the proxy server to determine if the proxy server has a cached copy of the content and if so, the proxy server provides an immediate response to the web client without forwarding the request to the web server. If the proxy server does not have a cached copy of the content, then the proxy server forwards the HTTP GET request to the web server where the request is analyzed and an HTTP 200 OK response is generated for forwarding via the proxy server to the web client.
In other implementations of the proxy server, the proxy server can provide functions such as security, encryption, or compression. In these implementations, the proxy server provides a pre-processing stage for the client requests and a post-processing stage for the web server responses, where all content is delivered from the web server.
One aspect to policy-based content insertion is a method. The method includes receiving, at a content server, a content request. The method further includes modifying, at the content server, the content request based on one or more ingress policies. The method further includes transmitting the modified content request to a second server based on one or more routing policies. The method further includes receiving, at the content server, a reply to the modified content request from the second server. The reply includes a content insertion instruction.
Another aspect to policy-based content insertion is a computer program product. The computer program product is tangibly embodied in an information carrier. The computer program product includes instructions operable to cause a data processing apparatus to receive, at a content server, a content request and modify, at the content server, the content request based on one or more ingress policies. The computer program product further includes instructions operable to cause a data processing apparatus to transmit the modified content request to a second server based on one or more routing policies and receive, at the content server, a reply to the modified content request from the second server. The reply includes a content insertion instruction.
Another aspect to policy-based content insertion is a system. The system includes a content server. The content server includes a policy-based proxy module and a content insertion module. The policy-based proxy module is configured to receive a content request, modify the content request based on one or more ingress policies, and transmit the modified content request to a second server based on one or more routing policies. The content insertion module is configured to receive a reply to the modified content request from the second server. The reply includes a content insertion instruction.
Another aspect to policy-based content insertion is a system. The system includes a mean for content insertion. The means for content insertion include a means for receiving a content request and a means for modifying the content request based on one or more ingress policies. The means for content insertion further include a means for transmitting the modified content request to a second server based on one or more routing policies and a means for receiving a reply to the modified content request from the second server. The reply includes a content insertion instruction.
In other examples, any of the aspects above can include one or more of the following features. The content server transmits the content based on one or more egress policies. The one or more egress policies include content rate, content rate adjustment, network congestion, a client type, and/or an encryption requirement. Content located on the content server is associated with the content request based on the content insertion instruction.
In some examples, content located externally from the content server is associated with the content request based on the content insertion instruction. The content associated with the content insertion instruction is transmitted to a computing device associated with the content request. The content is transmitted at a first data rate associated with the content insertion instruction.
In other examples, the first data rate is changed to a second data rate based on network congestion, computing device performance, and/or content server performance. The content request is received employing a network connection. The content is transmitted employing the network connection. The network connection includes a network socket, a network session, a network port, and/or a network address.
In some examples, the transmission of the content employs an internet protocol (IP), a transmission control protocol (TCP), a hypertext transfer protocol (HTTP), a user datagram protocol (UDP), a real-time transport protocol (RTP), a real time messaging protocol (RTMP), a real time streaming protocol (RTSP), an interleaved RTSP, a session initiation protocol (SIP), and/or an IP television protocol.
In other examples, part or all of the content insertion instruction is removed from the reply. The modified reply and the content is transmitted employing a network connection associated with the content request. The modified reply is associated to the modified request based on the content insertion instruction and/or the network connection associated with the content request.
In some examples, the content is appended to the reply. The appended reply is transmitted employing a network connection associated with the content request. The content request includes an HTTP, RTMP, RTSP or SIP request. The modified content request includes a request for the content insertion instruction. The reply includes a corresponding HTTP, RTMP, RTSP or SIP response which includes the content insertion instruction.
In other examples, the content request is modified to insert one or more headers and/or attributes which request the content insertion instruction based on the one or more ingress policies. One or more headers and/or attributes associated with the content insertion instruction are removed from the reply.
In some examples, the one or more routing policies include routing information for content requests and/or application requests. The one or more ingress policies include entitlement information for a network connection associated with the content request, a user associated with the content request, a computing device associated with the content request, a time of day, a geographic location, and/or a service provider identity.
In other examples, the second server is selected from a plurality of second servers based on the one or more routing policies. The second server is an application server, a web server, a management server, a middleware server, a media server, a streaming server, and/or a web streaming server.
In some examples, the content request is modified to request the content insertion instruction associated with content based on the one or more ingress policies. The content insertion instruction includes a first data rate, a content location, an offset for streaming, a congestion management profile, and/or a content playlist.
In other examples, the congestion management profile instructs the content server to modify the rate of content transmission based on network congestion. The content playlist includes one or more advertisements. Each advertisement for the content playlist is dynamically selected by the content server and/or an external application server.
In some examples, the content insertion instruction includes a directive to insert content, a programming language directive, a markup language directive, and/or a scripting language directive. The content server includes a storage system and the content insertion module is further configured to associate content located on the storage system with the content request based on the content insertion instruction.
In other examples, the system includes an external storage system and the content insertion module is further configured to associate content located on the external storage system with the content request based on the content insertion instruction. The content insertion module is further configured to transmit the content associated with the content insertion instruction to a computing device associated with the content request.
In some examples, the content insertion module is further configured to remove part or all of the content insertion instruction from the reply and transmit the modified reply and the content employing a network connection associated with the content request.
In other examples, the content insertion module is further configured to append the content to the reply and transmit the appended reply employing a network connection associated with the content request.
The policy-based content insertion techniques described herein can provide one or more of the following advantages. An advantage is that the streaming of data separated from the processing of a request for the data enables the processing and the streaming to be scaled independently of the other. Another advantage is that the decoupling of the control and application processing from that of media delivery provides for efficient scalable media streaming.
FIG. 1 shows a web server and a web client known in the art.
FIG. 2 shows a web server, a proxy server, and a web client known in the art.
FIG. 3 depicts an exemplary system with a policy-based content insertion proxy.
FIG. 4 depicts another exemplary system with a policy-based content insertion proxy.
FIG. 5 depicts an exemplary content server.
FIGS. 6A-6B depict an exemplary flowchart illustrating applying policies to HTTP requests.
FIGS. 7A-7B depict an exemplary flowchart illustrating inserting content into a HTTP response.
In general overview, a user requests delivery of content (e.g., multimedia file, text file, binary file, etc.). The user's client (e.g., web browser, file browser, application on set top box, etc.) transmits the request (e.g., HTTP get request, file transfer protocol (FTP) get, a real time streaming protocol (RTSP) setup, etc.) to a content server (also referred to as a policy-based content insertion proxy (PCIP)). The content server modifies the request based on an ingress policy (e.g., user can receive content, network address can receive content, and the like). The content server transmits the modified request to a server (e.g., application server, web server, etc.). The server processes the modified request and transmits a reply to the modified request to the content server. The reply includes a content insertion instruction (e.g., content identification, data rate, etc.). The content server transmits the content to the user's client based on the content insertion instruction and/or one or more egress policies (e.g., burst the initial portion of the content at a high data rate to preload the client playout buffer, modify the content data rate based on network congestion, encrypt the content, and the like) at the content server.
The control plane processing can occur, for example, on general purpose computer servers supporting web services applications and/or other types of applications. The media plane, owning to its much greater bandwidth requirement as a result of serving high quality media streams, and therefore requiring a high bit rate, can stream media, for example, utilizing special purpose media streaming servers.
With the techniques described herein, the control plane and the media plane can utilize, for example, a single socket between a client browser and service which enables the transparent decoupling of the processing and media delivery from the client's perspective. The decoupling can preserve, for example, existing web server control and application compute platforms (e.g., hardware and/or software) and allow, for example, the introduction of new media streaming elements that integrate in a standards compliant way within the protocol framework (e.g., RTSP, HTTP, etc.). The media streaming can be, for example, off-loaded from a web and/or other application server allowing the use of special purpose media streaming components to achieve a high-performance, cost-effective solution for the delivery of high quality video. On the client side, the decoupling, typically, does not impose any changes regarding the request of the video stream. Moreover, on the server side, the decoupling can be integrated, for example, in a standards-compliant fashion with minimal impact to existing video streaming solutions. Such standards can include, for example, RFC 3550, available from the Internet Engineering Task Force (IETF) and RFC 2616, available from the IETF.
FIGS. 3-5 illustrate exemplary systems and servers that are part of the policy-based content insertion techniques. FIGS. 6-7 illustrate exemplary flowcharts of the processing of HTTP requests and responses, respectively, through the exemplary systems and servers of FIGS. 3-5. The exemplary systems and servers are illustrated through the use of the content server. Other variations and/or exemplary uses of the content server are described below.
Policy-Based Content Insertion
FIG. 3 depicts an exemplary system 300 with a policy-based content insertion proxy (PCIP) 320. The PCIP 320 (also referred to as a content server and/or a type of reverse proxy server) is located between the web client 330 and web server 310. In the system 300, all client requests for content are directed to the PCIP 320. The PCIP 320 is a proxy through which all messaging between the client 330 and server 310 passes. The PCIP 320 inserts content into the HTTP/TCP stream towards the client 330 at the appropriate time. The PCIP 320 can be, for example, a policy-driven, configurable HTTP server. The PCIP 320 advantageously provides the efficient decoupling of control and application plane processing from that of media delivery which increases the efficiency of the delivery of content to clients.
FIG. 3 illustrates policy-based content insertion in an exemplary HTTP request (in this example, GET) and reply (in this example, 200 OK). The exemplary content insertion is illustrated in the following seven steps (indicated by arrows on the system 300).
1. The client 330 sends an HTTP GET request to the PCIP 320. In some examples, the request is no different from the request the client 330 would have sent to the actual web server (in this example, 310). Advantageously, there is no change required on the client 330 since the request is sent through the PCIP 320 and the reply is sent back through the PCIP 320 (in this example, the same network connection is utilized for the communication between the client 330 and the PCIP 320).
2. The PCIP 320, on receipt of a GET request, analyzes the request and consults its configured policies (e.g., ingress policy, routing policy, etc.). The policy logic determines how the request should be handled. In this example, the policy logic in conjunction with provisioned data determines that the request needs to be proxied to an appropriate web server 310.
3. The PCIP 320 appends a header in the GET request. The new header, for example, requests the web server 310 to return back the name of the file that needs to be streamed, the offset from which to begin streaming, and/or the bit rate at which to stream. The PCIP 320 transmits the GET request, with this additional header, to the web server 310, which is responsible for handling the GET request as determined by the configured policies (e.g., the routing policies). The PCIP 320 does not interpret any of the other headers or content in the GET request.
4. The web server 310 processes the request and determines which file needs to be streamed, along with attributes like bit rate and offset into the file from where the streaming should start, based on one or more application policies. The web server 310 constructs the 200 OK message to send back to the client 330. The presence of the header inserted by the PCIP 320 causes the web server 310 to construct the 200 OK response but hold back on retrieving and inserting content into the 200 OK response.
5. Instead, the web server 310 inserts a header into the 200 OK response. The inserted header includes, for example, the name of the file, the offset from which to begin streaming and the bit rate at which to stream the content. The web server 310 transmits the 200 OK with the new header back to the PCIP 320.
6. The PCIP 320, on receipt of the 200 OK, extracts the header inserted by the web server 310. Using the information in the header and/or one or more egress policies configured in the PCIP 320, the PCIP 320 retrieves the content to be inserted into the 200 OK response from a storage system.
7. The PCIP 320 strips out the new header inserted by the web server 310 and forwards the 200 OK. The PCIP 320 appends the content at the end of the 200 OK response just as a prior art web server would have done. The client 330 receiving the response advantageously does not see any difference in the response which reduces the configuration needed for the efficient utilization of the system 300.
An additional advantage is that in the system 300, the PCIP 320 does not host the web application since the web application functionality is implemented by the web server 310, which allows for the PCIP 320 to be configured and optimized to stream content. Another advantage is that the PCIP 320 has a specialized function which is the high-performance delivery of streamed content and which off-loads this compute intensive function from the web server.
In some examples, the PCIP 320 is a content cache proxy, a transparent proxy, and/or a content insertion proxy based on the request/response being processed. In other examples, the client 330 processes the response and displays video. Any subsequent pause, rewind, and/or fast forward requests from the client 330 can be, for example, processed as described herein.
Although FIG. 3 illustrates the web client 330 and the web server 310, other types of clients and servers can communicate and be utilized with the PCIP 320. The other types of clients can include, for example, a file transfer protocol (FTP) client, a media client, a management console client, an application client, and/or any other type of computer client. The other types of servers can include, for example, an application server, a management server, a middleware server, a media server, a streaming server, a web streaming server, and/or any other type of computer server.
For example, a set top box (STB) with a media client 330 requests a video on demand through an IPTV network. The request (in this example, a TCP/IP request) is directed to the content server 320 (also referred to as a PCIP). The content server 320 processes the request as described above and transmits the modified request (in this example, a modified TCP/IP request) to the application server 310 (in this example, the application server at the cable headend). The application server 310 processes the modified request as described above and replies. The reply includes two content insertion instructions (in this example, content identification, content data rate). The content server 320 replies to the request with a stream of the requested content based on the content insertion instruction and transmits the reply. The offloading of the streaming of the content advantageously allows the application server 310 to process more requests while allowing the streaming to be done by a content server 320 that is designed to stream content.
Although FIG. 3 illustrates a single box for the web server 310, the system 300 can include, for example, a plurality of servers (e.g., web server 310 can represent a server farm or other group of servers logically and/or physically grouped together) which process the requests and/or reply to the request. The PCIP 320 can determine, for example, a server from the plurality of servers based on one or more routing policies. For example, the PCIP 320 receives an HTTP request for http://www.sometestdomain.net and has a routing policy that all HTTP requests for .sometestdomain.net domain are directed to a second web server. The PCIP 320 transmits the modified request (in this example, directed to http://www.sometestdomain.net) to the second web server. As another example, the PCIP 320 receives a FTP request for ftp://sometestdomain.net and has a routing policy that all FTP requests for .sometestdomain.net domain are directed to a third FTP server. The PCIP 320 transmits the modified request (in this example, directed to ftp://sometestdomain.net) to the third FTP server.
Although FIG. 3 illustrates a single web client 330, a plurality of clients (e.g., one thousand, ten thousand, one hundred thousand) can communicate with the PCIP 320. The PCIP 320 can process, for example, requests from, replies to, and/or streams to a plurality of clients nearly simultaneously. For example, the PCIP 320 nearly simultaneously streams a movie to an application client on a STB utilizing IPTV, modifies a HTTP request from a web client, and receives a reply from a FTP server.
Although FIG. 3 illustrates the web client 330, the PCIP 320, and the web server 310 connected to each other, the web client 330, the PCIP 320, and the web server 310 can be, for example, connected through one or more communication networks (e.g., internet, intranet, etc.), with other computing devices (e.g., routers) between them. The web client 330 and the PCIP 320 can be, for example, connected through a first communication network and the PCIP 320 and the 310 can be connected through a second communication network. In other examples, the web client 330, the PCIP 320, and the web server 310 are connected to the same communication network.
In some examples, the PCIP 320 receives requests and transmits replies utilizing the same network connection. The network connection can be, for example, a network socket, a network session, a network port, a network address, and/or any other type of network identification mechanism.
Typically, web servers (e.g., 310) and clients (e.g., 330) can communicate using HTTP sessions over TCP. For each unique connection/session between a client 310 and server 330, TCP abstracts the endpoint into what is typically referred to as a socket. Data written at one end of the socket from the client/server side emerges from the socket of the server/client in a reliable sequenced fashion. TCP processing uses checksum, re-transmission and/or other mechanisms to provide reliable transport. These TCP features require significant processing resources proportional to the streaming rate of the delivered content and add another scaling dimension to media delivery requirements beyond content retrieval from storage. Another advantage of the tight coupling of the control plane (e.g., web server 310) and data plane (e.g., PCIP 330) on a single communication endpoint (e.g., network socket) is that the processing resources required for the network communication can be offloaded to the data plane thereby enabling the control plane to more efficiently process requests.
FIG. 4 depicts another exemplary system 400 with the policy-based content insertion proxy 320. FIG. 4 illustrates sample HTTP messages 432, 434, 436, and 438 (in this example, GET and 200 OK messages) between the web client 330 and the PCIP 320 and between the PCIP 320 and the web server 310. These messages 432, 434, 436, and 438 illustrate a header insertion by the PCIP 320 in the inbound HTTP GET message before delivery to the web server 310, and a header deletion by the PCIP 320 in the inbound HTTP 200 OK message with content insertion before delivery to the web client 330.
The web client 330 transmits a HTTP GET message 432 which requests mediaID. The PCIP 320 modifies the HTTP GET message 434 based on one or more ingress policies. For example, an ingress policy can represent (e.g., in some computer-readable form) that the web client 330 can access the media and the domain xyz.com can access the media. The modified HTTP GET message 434 includes an identification (in this example, ck123), a request (in this example, file name, offset, and bit rate), and the forwarded address (in this example, webclient.xyz.com).
The web server 310 utilizes one or more application policies to determine the reply to the modified request 434. The web server 310 transmits a reply 436 to the modified request 434. The reply 436 includes content insertion instructions for the requested content (in this example, the identification, the file name, the offset, and the bit rate associated with the requested content). The PCIP 320 removes part or all of the content insertion instructions from the reply 436. The PCIP 320 uses the content insertion instruction to obtain the requested content and transmit the modified reply 438, which includes the requested content (in this example, video/mpeg2-ts), to the web client 330.
In some examples, the one or more ingress policies include entitlement information for a network connection associated with the content request (e.g., originating network, domain name, IP address, etc.), a user associated with the content request (e.g., anonymous user, registered user, guest user, etc.), a computing device associated with the content request (e.g., a personal digital assistant device, a personal computer device, a STB device, etc.), a time of day (e.g., set hours, night, day, etc.), a geographic location (e.g., New York, Southern United States, United States, North America, Asia, etc.), a service provider identity (e.g., certain cable provider, certain mobile telephone provider, etc.), and/or any other type of access control mechanisms associated with content.
FIG. 5 depicts the exemplary content server 320 in a system 500. The content server 320 includes a policy-based proxy module 522, a content insertion module 524, and a storage system 526. The system 500 can include, for example, an external storage system. The policy-based proxy module 522 receives requests from one or more clients (not shown) and modifies the requests based on one or more ingress policies. The policy-based proxy module 522 transmits the modified request to a server selected from one or more servers based on one or more routing policies.
The content insertion module 524 receives replies to the modified content requests from the one or more servers. The replies include content insertion instructions which enable the content insertion module 524 to obtain content and transmit that content to the client that requested the content. The content insertion module 524 associates the content insertion instructions (e.g., instructions include content file path, instructions include content unique identifier) with content to be obtained and provided to the requested client. The content can be, for example, located in the storage system 526 on the content server 320 and/or in the external storage system 528 (e.g., storage area network (SAN), network-attached storage (NAS), network file system (NFS) server, FTP server, HTTP server, etc.). The content insertion module 524 transmits the reply with the embedded content and/or the content to the client (i.e., the user's computing device) associated with the request. The content can be, for example, embedded into the reply (e.g., reply 438) and/or transmitted separately from the reply depending on the transmission protocol, the client type, and/or any other information associated with the content request.
FIGS. 6A-B depict an exemplary flowchart 600 illustrating applying policies to HTTP requests through the exemplary system 300 of FIG. 3. The flowchart 600 illustrates the PCIP 320 decision logic for an inbound HTTP GET request (e.g., 432) from the web client 330 to the PCIP 320 with the PCIP 320 providing the functions of a cache, transparent, or content insertion proxy depending on the request/response being processed.
The PCIP 320 accepts (610) an inbound HTTP GET request (e.g., 432) from the web client 330. The PCIP 320 parses (620) the HTTP GET request (e.g., 432) to determine the contents of the request. The PCIP 320 establishes (630) an inbound session with the web client 330. The PCIP 320 performs processing (640) to apply a lookup policy. This processing includes steps 642, 644, and 646. The PCIP 320 applies (642) a web client profile, a uniform resource identifier (URI) profile, and a URI destination list to determine if the web client 330, the client's network, and the destination can be accessed by the request. In this example, the web client profile, the URI profile, and the URI destination list are part of the ingress policies. A web client profile can be, for example, a computer-readable representation that a certain client can not receive content, all clients can receive content, etc. A uniform resource identifier (URI) profile can be, for example, a computer-readable representation that certain URIs can only be transmitted upon authentication, certain URIs can be transmitted to anyone, etc. A URI destination list can be, for example, a computer-readable representation that certain URIs can only receive G rated content, certain URIs must be authenticated, etc.
The PCIP 320 applies (644) routing policies and entitlement policies (e.g., user receives a high data rate, user receives low data rate, etc.) to determine which server to transmit the modified request to and how to modify the request. The PCIP 320 returns (646) a route list and server role (e.g., insertion proxy, cache, pass-through) based on the routing policies and the entitlement policies. The flowchart 600 continues (650) from FIG. 6A to FIG. 6B.
The PCIP 320 determines (660) if the role is insertion proxy. If the role is insertion proxy, then the PCIP 320 modifies (666) the request with header fields and/or other attributes (in this example, file name, offset, and bit rate) based on the ingress policies (in this example, the web client profile, the URI profile, and the URI destination list). The PCIP 320 transmits (668) the modified request (e.g., 434) to the server (e.g., web server 310) selected from the plurality of servers based on the routing policies. The PCIP 320 then waits (670) for a response from the web server 310.
If the role is not insertion proxy, then the PCIP 320 determines (662) if the role is cache. If the role is cache, then the PCIP 320 transmits (664) the requested content the same as an HTTP server (e.g., web server 310) would transmit the content. In other words, the PCIP 320 transmits the content without communicating with the web server 310.
If the role is not cache, then the PCIP 320 transmits (668) the request to the server based on the routing policies. The PCIP 320 then waits (670) for a response from the web server 310. The routing policies can include, for example, routing information for content requests (e.g., requests for movie content are directed to a fourth server, requests for mpeg content are directed to a fifth server, etc.), application requests (e.g., requests for billing are directed to a billing server, requests for authentication are directed to a authentication server, etc.), and/or any other type of routing information.
Although FIG. 3 illustrates a request from a web client 330 and FIG. 6 illustrates a HTTP request, the request can be from any type of computing device and/or can be in any protocol. In some examples, the request is received from the PCIP 320 (e.g., for storage of the content in a different location on the storage system), another computer server, a second PCIP, a second external storage system, and/or any other computing device. The request can include, for example, HTTP, real time messaging protocol (RTMP), real time streaming protocol (RTSP), session initiation protocol (SIP), and/or any other type of protocol that can be used to make such a request. As such, the reply includes a corresponding HTTP, RTMP, RTSP, SIP, and/or other protocol response which includes one or more content insertion instructions.
Content Insertion Instruction
In response to a request, the web server 310 can, for example, generate the one or more content insertion instructions based on one or more application policies (e.g., user has access to content, domain has access to content, domain has to pay for content, user has to pay for content, etc.). The one or more content insertion instructions can include a variety of different types of information that instruct a server on where and/or how to obtain and/or transmit requested content to the client making the request. The content insertion instructions can include, for example, a data rate (e.g., data rate=400 kb/s, data rate=10 Mb/s), a content location (e.g., file=MovieA3234, location=\dev\disk2\movies\AL4.m4a), an offset for streaming (e.g.: 4 minutes, 3 seconds, 2 frames; 20 minutes, 0 seconds, 4 frames; 24 frames, etc.), a congestion management profile (e.g.; stream at maximum rate until network capacity is above 60%; stream at minimum rate unless network capacity is below 30%; stream at maximum rate if TCP network throughput allows, stream at minimum rate otherwise), a content playlist (e.g., list of movies, list of television shows), and/or any other type of content instruction.
For example, the web server 310 generates the content insertion instructions of content location=\NYServer\Module0A\movie2342.mpg, the bitrate=3 Mb/s, and the offset=(9 minutes, 32 seconds, 5 frames). As another example, the web server 310 generates the content insertion instructions of content identifier=MovieA3234, the bitrate=400 kb/s, and encryption=public-key alpha.
In other examples, the web server 310 authenticates the user's login utilizing a backend authentication system (not shown). The user is classified as a high data rate client type (e.g., the user pays for the high data rate, the user is on a network that can receive a high data rate, etc.). As such, the web server 310 generates a content insertion instruction that the data rate is high (in this example, 10 Mb/s). In this example, the content insertion instruction is bitrate=10 Mb/s. In another example, the web server 310 determines that all replies and content to the testxyz.com domain are encrypted. As such, the web server 310 generates a content insertion instruction that the content is encrypted (e.g., data encryption standard (DES), public-key encryption, etc.). In this example, the content insertion instruction is encryption=DES.
In some examples, the web server 310 determines which content to stream and at what rate to a specific client based on the one or more application policies. The web server 310 can interface, for example, to databases and/or back office systems to determine how to handle each client request (e.g., authentication, billing, etc.) based on the one or more application polices. For example, the web server 310 communicates with a billing server (not shown) to bill the user's account for the requested movies. An another example, an application policy is that all requests for movies are authenticated through an authentication server (not shown) and then billed to a billing server (not shown). For example, another application policy is that requests for new television shows (e.g., within past 2 weeks, within past 5 days) are billed to a billing server only. An advantage to the streaming of content on the PCIP 320 is that standard compute servers (e.g., web server 310) are well suited to implement the application logic but do not perform well for delivering a large number of high bit rate content streams.
In other examples, the web server 310 includes application intelligence. For example, a web client 330 initiates a request to watch a video by sending a control plane payload in the HTTP request (GET) 432. This control plane payload is destined for a component on the web server 310 which has the application intelligence (e.g., Active Server Pages (.NET) and JavaServer Pages (JSP)) to interpret and understand the nature of the request. After applying the intelligence, the web server 310 transmits a reply 436 to the PCIP 320. The reply 436 enables the PCIP 320 to stream the content by first constructing a 200 OK HTTP envelope and then embedding the video stream behind the 200 OK header. The 200 OK message 438 (header and video stream) is written into the socket by the PCIP 320.
In some examples, the content insertion instruction includes a content playlist which includes one or more advertisements (e.g., dog food commercial, soap commercial). The PCIP 320 and/or an external application server (not shown) can dynamically select each advertisement for the content playlist. For example, the user requests Super Dog the movie and the external application server associates Super Dog the movie with a dog food commercial and a dog shampoo commercial. As such, the content playlist includes Super Dog the movie, the dog food commercial, and the dog shampoo commercial.
In other examples, the content insertion instruction includes a directive to insert content (e.g., insert=MovieA32, append=MovieB323), a programming language directive (e.g., #include=encryption, #region=USA), a markup language directive (e.g., X-Vv-id: ck123, X-Vv-Rsp: fileName=mediaUuid.ts), a scripting language directive (e.g., use language=English, use caption=Spanish), and/or any other type of directive.
As described above, the PCIP 320 obtains and transmits content based on the one or more content insertion instructions that are inserted into a response by the web server 310. FIG. 7 depicts an exemplary flowchart 700 illustrating inserting content into a HTTP response based on the one or more content insertion instructions using the exemplary system 300 of FIG. 3. The flowchart 700 illustrates the PCIP decision logic for an inbound HTTP 200 OK response from the web server 310 to the PCIP 320, with the PCIP 320 providing the functions of a transparent or content insertion proxy.
The PCIP 320 receives (710) a response (also referred to as a reply) from the web server 310. The PCIP 320 accepts (715) the inbound HTTP response (e.g., 436). The PCIP 320 parses (720) the HTTP response to determine the content insertion instructions (e.g., identifier, content location, data rate, directives, etc). The PCIP 320 locates (725) the inbound session based on the applicable content insertion instruction(s) (e.g., identifier, etc.), the network connection associated with the content request, and/or information associated with the HTTP response (e.g., client information, domain information, etc.). The flowchart 700 continues (730) from FIG. 7A to FIG. 7B.
The PCIP 320 determines (740) if the role is insertion proxy. If the role is not insertion proxy, then the PCIP 320 transmits (795) the HTTP response to the web client 330. If the role is insertion proxy, then the PCIP 320 locates (750) the applicable content instructions associated with obtaining and transmitting the requested content (e.g., content name, data rate). The PCIP 320 then retrieves (760) information about the content (e.g., the location on the storage system of the content, the location on an external storage system of the content, etc.), using, for example, a stored lookup table. The PCIP 320 removes (770) certain data from the headers (e.g., data rate=400 kb/s, offset=(1 hr, 10 min, 5 sec, 11 frames) and/or attributes (e.g., from=web server, port=80) that is not needed by the client (e.g., one or more of the content insertion instructions from the response). In some examples, PCIP removes (770) all headers that were inserted by server 310. The PCIP 320 locates (780) the content on the storage system and determines the offset of the content. The PCIP 320 streams (790) the content to the web client 330 at the requested bit rate. The PCIP 320 transmits (795) the modified HTTP response to the web client 330.
In some examples, the PCIP 320 transmits (795) the modified HTTP response to the web client 330 at a specified data rate based on the content insertion instruction (e.g., bitrate=500 kb/s, bitrate=10 Mb/s) and/or one or more egress policies. The PCIP 320 can change the specified data rate to a different data rate based on network congestion (e.g., transmission network above 90% capacity, data packets latency over 100 ms between PCIP 320 and web client 330, etc.), computing device performance (e.g., STB incoming processing above 95% capacity, cell phone storage above 75% capacity, etc.), content server performance (e.g., storage system above 90% storage capacity, content insertion module processing above 75% capacity, etc.), congestion management profile (e.g., reduce all data rates above 1 Mb/s when the network is above 75% capacity, reduce non-real time transmission data rates when the network is above 80% capacity) and/or any type of congestion and/or performance metric. The one or more egress policies include a content rate (e.g., transmissions to testdomain.net are at 1 Mb/s, transmission to testdomain.net should not exceed 2 Mb/s, etc.), a content rate adjustment (e.g., up all rates for certain domains by 500 kb/s, reduce all rates for certain domains by 100 kb/s, etc.), network congestion (e.g., transmission network above 90% capacity, data packets latency over 100 ms between PCIP 320 and web client 330, etc.), a client type (e.g., personal computer, cell phone, web browser, etc.), an encryption requirement (e.g., all transmissions to testdomain.net use DES, transmissions over 10 Mb/s do not use encryption, etc.), and/or any other type of egress rule.
Other Exemplary Uses
Although FIGS. 6A-6B and 7A-7B provide examples of a HTTP request and response, the PCIP 320 can be utilized for other applications that benefit from the off-loading of delivering high bit rate streams (e.g., IPTV, propriety streaming technology, etc.). The PCIP 320 can be utilized, for example, for Web streaming, IPTV, cable VOD applications, streaming large data files (software distribution), and/or other large data file streaming applications. For example, the request can be a SIP request and the reply can be a SIP reply. As another example, the request can be an IPTV request and the reply can be an IPTV reply. Another advantage is that technology which does not and/or cannot separate the processing of control plane and media delivery in a computing environment can utilize the PCIP 320 to implement a scalable streaming solution.
In some examples, Internet Protocol Television (IPTV) based Video-on-Demand (VOD) servers use the Real Time Streaming Protocol (RTSP) to stream content to clients. In this example the PCIP 320 acts as an Application Layer Gateway (ALG) which inserts headers and interprets headers embedded in the RTSP signaling. As described above in the web context, the PCIP 320 streams the content and the VOD processes requests.
In other examples, RTSP signaling is sometimes used in an interleaved mode to work around issues with firewalls. Interleaved-RTSP uses the same socket for delivering the control and media packets. As such, the PCIP 320 can be utilized to process the RTSP control packets and interleave the media content into the control response to the client (e.g., web client 330).
In some examples, the PCIP 320 streams content utilizing proprietary streaming technologies. The proprietary streaming technologies can include, Adobe Flash (available from Adobe System Incorporated of San Jose, Calif.), RealMedia (available from RealNetwork, Inc. of Seattle, Wash.), QuickTime (available from Apple, Inc. of Cupertino, Calif.), Windows Media (available from Microsoft Corporation, of Redmond, Wash.), and/or any other type of streaming technology.
The transmission of the content from the PCIP 320 to the client (e.g., web client 330) can employ, for example, an internet protocol (IP), a transmission control protocol (TCP), a hypertext transfer protocol (HTTP), a user datagram protocol (UDP), a real-time transport protocol (RTP), a real time messaging protocol (RTMP), a real time streaming protocol (RTSP), an interleaved RTSP, a session initiation protocol (SIP), an IP television protocol, and/or any other type of communication protocol.
In some examples, the PCIP 320 is distributed among a plurality of servers in a server farm. The server farm can be, for example, at one geographical location (e.g., a data center) or distributed among a plurality of geographical locations (e.g., multiple data centers).
Examples of communication networks include a packet-based network and/or a circuit-based network. Packet-based networks can include, for example, the Internet, a carrier internet protocol (IP) network (e.g., local area network (LAN), wide area network (WAN), campus area network (CAN), metropolitan area network (MAN), home area network (HAN)), a private IP network, an IP private branch exchange (IPBX), a wireless network (e.g., radio access network (RAN), 802.11 network, 802.16 network, general packet radio service (GPRS) network, HiperLAN), and/or other packet-based networks. Circuit-based networks can include, for example, the public switched telephone network (PSTN), a private branch exchange (PBX), a wireless network (e.g., RAN, bluetooth, code-division multiple access (CDMA) network, time division multiple access (TDMA) network, global system for mobile communications (GSM) network), and/or other circuit-based networks.
The client can be, for example, part of and/or implemented on a computing device. The computing device can include, for example, a computer, a computer with a browser device, a telephone, an IP phone, a mobile device (e.g., cellular phone, personal digital assistant (PDA) device, laptop computer, electronic mail device), and/or other communication devices. The browser device includes, for example, a computer (e.g., desktop computer, laptop computer) with a world wide web browser (e.g., Microsoft® Internet Explorer® available from Microsoft Corporation, Mozilla® Firefox available from Mozilla Corporation). The mobile computing device includes, for example, a personal digital assistant (PDA).
1. A method for content insertion, the method comprising:
receiving, at a content server, a content request from a requesting computing device;
modifying, at the content server, the content request by adding data to the content request, the data comprising one or more headers, attributes, or both, based on the content request;
transmitting, by the content server, the modified content request to a second server based on one or more routing policies; and
receiving, at the content server, a reply message responsive to the modified content request from the second server, the reply comprising a content insertion instruction comprising data indicative of content to transmit to the requesting computing device.
2. The method of claim 1, further comprising transmitting, by the content server, the requested content to a client that transmitted the content request.
3. The method of claim 2, wherein transmitting is based on one or more egress policies comprising content rate, content rate adjustment, network congestion, a client type, an encryption requirement, or any combination thereof.
4. The method of claim 1, further comprising associating content located on the content server with the content request based on the content insertion instruction.
5. The method of claim 1, further comprising associating content located externally from the content server with the content request based on the content insertion instruction.
6. The method of claim 1, further comprising transmitting the content associated with the content insertion instruction to a computing device associated with the content request.
7. The method of claim 6, wherein transmitting the content comprises transmitting the content at a first data rate associated with the content insertion instruction.
8. The method of claim 7, further comprising changing the first data rate to a second data rate based on network congestion, computing device performance, content server performance, or any combination thereof.
wherein receiving the content request comprises receiving the content request employing a network connection, and
wherein transmitting the content comprises transmitting the content employing the network connection.
10. The method of claim 9, wherein the network connection comprises a network socket, a network session, a network port, a network address, or any combination thereof.
11. The method of claim 6, wherein transmitting the content comprises transmitting the content employing an internet protocol (IP), a transmission control protocol (TCP), a hypertext transfer protocol (HTTP), a user datagram protocol (UDP), a real-time transport protocol (RTP), a real time messaging protocol (RTMP), a real time streaming protocol (RTSP), an interleaved RTSP, a session initiation protocol (SIP), an IP television protocol, or any combination thereof.
removing part or all of the content insertion instruction from the reply; and
transmitting the modified reply and the content employing a network connection associated with the content request.
13. The method of claim 12, further comprising associating the modified reply to the modified request based on the content insertion instruction, the network connection associated with the content request, or both.
appending the content to the reply to provide an appended reply; and
transmitting the appended reply employing a network connection associated with the content request.
15. The method of claim 1, wherein the content request comprises an HTTP, RTMP, RTSP or SIP request, the modified content request comprises a request for the content insertion instruction, and the reply comprises a corresponding HTTP, RTMP, RTSP or SIP response which comprises the content insertion instruction.
16. The method of claim 1, wherein the header data requests the content insertion instruction based on one or more ingress policies.
17. The method of claim 1, further comprising removing one or more headers, attributes, or both associated with the content insertion instruction from the reply.
18. The method of claim 1, wherein the one or more routing policies comprise routing information for content requests, application requests, or both.
19. The method of claim 16, wherein the one or more ingress policies comprise entitlement information for a network connection associated with the content request, a user associated with the content request, a computing device associated with the content request, a time of day, a geographic location, a service provider identity, or any combination thereof.
20. The method of claim 1, further comprising selecting the second server from a plurality of second servers based on the one or more routing policies.
21. The method of claim 1, wherein the second server is an application server, a web server, a management server, a middleware server, a media server, a streaming server, a web streaming server, or any combination thereof.
22. The method of claim 1, wherein modifying the content request comprises modifying the content request to request the content insertion instruction associated with content based on one or more ingress policies.
23. The method of claim 1, wherein the content insertion instruction comprises a first data rate, a content location, an offset for streaming, a congestion management profile, a content playlist, or any combination thereof.
24. The method of claim 23, wherein the congestion management profile instructs the content server to modify the rate of content transmission based on network congestion.
25. The method of claim 23, wherein the content playlist comprises one or more advertisements.
26. The method of claim 25, further comprising dynamically selecting each advertisement for the content playlist by the content server, an external application server, or both.
27. The method of claim 1, wherein the content insertion instruction comprises a directive to insert content, a programming language directive, a markup language directive, a scripting language directive, or any combination thereof.
28. A computer program product, tangibly embodied in a non-transitory computer readable storage medium, the computer program product including instructions being operable to cause a data processing apparatus to:
receive, at a content server, a content request from a requesting computing device;
modify, at the content server, the content request by adding data to the content request, the data comprising one or more headers, attributes, or both, based on the content request;
transmit, by the content server, the modified content request to a second server based on one or more routing policies; and
receive, at the content server, a reply message responsive to the modified content request from the second server, the reply comprising a content insertion instruction comprising data indicative of content to transmit to the requesting computing device.
29. A system for content insertion, the system comprising:
a proxy module configured to:
receive a content request from a requesting computing device;
modify the content request by adding data to the content request, the data comprising one or more headers, attributes, or both, based on the content request;
transmit the modified content request to a second server based on one or more routing policies; and
a content insertion module configured to receive a reply message responsive to the modified content request from the second server, the reply comprising a content insertion instruction comprising data indicative of content to transmit to the requesting computing device.
30. The system of claim 29, wherein the content server further comprising a storage system and wherein the content insertion module is further configured to associate content located on the storage system with the content request based on the content insertion instruction.
31. The system of claim 29, further comprising an external storage system and wherein the content insertion module is further configured to associate content located on the external storage system with the content request based on the content insertion instruction.
32. The system of claim 29, wherein the content insertion module is further configured to transmit the content associated with the content insertion instruction to a computing device associated with the content request.
33. The system of claim 29, wherein the content insertion module is further configured to:
remove part or all of the content insertion instruction from the reply; and
transmit the modified reply and the content employing a network connection associated with the content request.
34. The system of claim 29, wherein the content insertion module is further configured to:
append the content to the reply to provide an appended reply; and
transmit the appended reply employing a network connection associated with the content request.
35. A system for content insertion, the system comprising:
a means for content insertion comprising:
a means for receiving a content request from a requesting computing device;
a means for modifying the content request by adding data to the content request, the data comprising one or more headers, attributes, or both, based on the content request;
a means for transmitting the modified content request to a second server based on one or more routing policies; and
a means for receiving a reply message responsive to the modified content request from the second server, the reply comprising a content insertion instruction comprising data indicative of content to transmit to the requesting computing device.
US12/013,756 2008-01-14 2008-01-14 Policy-based content insertion Active 2028-02-28 US8543667B2 (en)
US12/013,756 US8543667B2 (en) 2008-01-14 2008-01-14 Policy-based content insertion
PCT/US2009/030495 WO2009091666A1 (en) 2008-01-14 2009-01-08 Policy-based content insertion
US13/857,451 US9544183B2 (en) 2008-01-14 2013-04-05 Methods and apparatus for providing content delivery instructions to a content server
US13/857,451 Continuation US9544183B2 (en) 2008-01-14 2013-04-05 Methods and apparatus for providing content delivery instructions to a content server
US20090182843A1 US20090182843A1 (en) 2009-07-16
US8543667B2 true US8543667B2 (en) 2013-09-24
ID=40551974
US12/013,756 Active 2028-02-28 US8543667B2 (en) 2008-01-14 2008-01-14 Policy-based content insertion
US13/857,451 Active 2029-01-23 US9544183B2 (en) 2008-01-14 2013-04-05 Methods and apparatus for providing content delivery instructions to a content server
US (2) US8543667B2 (en)
WO (1) WO2009091666A1 (en)
US20120011266A1 (en) * 2010-07-06 2012-01-12 General Instrument Corporation Method and apparatus for providing a real time streaming protocol session
US20120317613A1 (en) * 2011-06-09 2012-12-13 Eun Ah Kim Network apparatus based on content name and method for protecting content
US20160028785A1 (en) * 2014-07-24 2016-01-28 Combined Conditional Access Development and Support, LLC (CCAD, LLC) Message rate mixing for bandwidth management
US9418353B2 (en) 2010-12-20 2016-08-16 Akamai Technologies, Inc. Methods and systems for delivering content to differentiated client devices
JP4506856B2 (en) * 2008-03-10 2010-07-21 ソニー株式会社 Communication apparatus, and communication method
CN102047236A (en) * 2008-03-18 2011-05-04 法布里克斯电视有限公司 A controlled rate vod server
EP2382580A4 (en) * 2009-01-16 2013-06-12 Ericsson Telefon Ab L M Proxy server, control method thereof, content server, and control method thereof
US8892631B2 (en) * 2009-04-09 2014-11-18 International Business Machines Corporation System and method of optimizing digital media processing in a carrier grade web portal environment
US20100311393A1 (en) * 2009-06-08 2010-12-09 Castleman Mark Methods and apparatus for distributing, storing, and replaying directives within a network
US9258369B2 (en) * 2009-06-18 2016-02-09 At&T Intellectual Property I, L.P. System and method to provide a network-based service
US10263958B2 (en) * 2010-03-18 2019-04-16 Nominum, Inc. Internet mediation
JP5184606B2 (en) * 2010-11-01 2013-04-17 株式会社バッファロー Content transmission method, the destination storage and content transmission program
US8667183B1 (en) 2011-03-20 2014-03-04 Israel L'Heureux Server-side HTTP translator
US8949464B2 (en) * 2011-05-10 2015-02-03 Israel L'Heureux Client-side HTTP translator
US20170093759A1 (en) * 2015-09-29 2017-03-30 Fastly, Inc. Persistent edge state of end user devices at cache nodes
US9954816B2 (en) 2015-11-02 2018-04-24 Nominum, Inc. Delegation of content delivery to a local service
US20170331690A1 (en) * 2016-05-12 2017-11-16 Iboss, Inc. Applying network policies to devices based on their current access network
EP3435629A1 (en) * 2017-07-24 2019-01-30 Facebook, Inc. Transport of control data in proxy-based network communications
EP0772360A2 (en) 1995-10-30 1997-05-07 Sony Corporation Video data receiving apparatus, video data transmitting apparatus, and broadcasting system
EP1115252A2 (en) 2000-01-04 2001-07-11 Emc Corporation Seamless splicing of encoded MPEG video and audio
WO2002009425A1 (en) 2000-07-25 2002-01-31 Agilevision, L.L.C. Splicing compressed, local video segments into fixed time slots in a network feed
US20020065073A1 (en) * 2000-11-30 2002-05-30 Morihito Natani Extended-cell communication network and transmission apparatus
US6480539B1 (en) 1999-09-10 2002-11-12 Thomson Licensing S.A. Video encoding method and apparatus
US6566541B2 (en) * 1997-06-09 2003-05-20 Massachusetts Institute Of Technology Type 2 methionine aminopeptidase (MetAP2) inhibitors and uses thereof
US6567471B1 (en) 1997-07-25 2003-05-20 Sony Corporation System method and apparatus for seamlessly splicing data
US20050256873A1 (en) 2004-04-23 2005-11-17 Walker Gordon K Methods and apparatus for providing hierarchical content flow in a data network
EP1655963A2 (en) 1998-01-19 2006-05-10 Sony Corporation Compressed picture data editing apparatus and method
US20060104230A1 (en) * 2004-11-18 2006-05-18 Gidwani Sanjay M Wireless network having control plane segregation
US7107309B1 (en) 2002-07-03 2006-09-12 Sprint Spectrum L.P. Method and system for providing interstitial notice
US20070055984A1 (en) 2005-08-24 2007-03-08 C-Cor Incorporated Multi-tiered architecture for targeted ad insertion
US8141156B1 (en) * 2005-12-28 2012-03-20 At&T Intellectual Property Ii, L.P. Method and apparatus for mitigating routing misbehavior in a network
US7664864B2 (en) 1998-11-13 2010-02-16 Verisign, Inc. Meta content distribution network
AU1798502A (en) 2000-11-30 2002-06-11 Infocruiser Inc System and method for delivering dynamic content
KR100426399B1 (en) 2001-04-06 2004-04-08 니트젠테크놀러지스 주식회사 A method for providing contents delivery network service through wireless networks and a system therefor
DE10134821A1 (en) 2001-07-17 2003-02-06 Siemens Ag Device for separating dust from flue gases of combustion plants, preferably solid fuel combustion plants
US7467233B2 (en) 2002-07-30 2008-12-16 Akamai Technologies, Inc. Edge side components and application programming environment for building and delivering highly distributed heterogenous component-based web applications
KR100518270B1 (en) 2002-12-18 2005-10-04 엘지.필립스 엘시디 주식회사 Method of forming pattern using printing process
CA2517189A1 (en) 2003-03-17 2004-09-30 British Telecommunications Public Limited Company Web content adaption process and system
US20040243704A1 (en) 2003-04-14 2004-12-02 Alfredo Botelho System and method for determining the unique web users and calculating the reach, frequency and effective reach of user web access
EP1533970B1 (en) 2003-11-24 2006-08-16 Akamai Technologies, Inc. Method and system for secure content delivery
GB2430591B (en) 2005-09-23 2010-09-01 Scansafe Ltd Network communications
CN101242422B (en) 2007-02-06 2011-01-26 中国电信股份有限公司 Content distribution network system and method applicable to multi-service fusion
US8549157B2 (en) 2007-04-23 2013-10-01 Mcafee, Inc. Transparent secure socket layer
WO2009047784A2 (en) 2007-06-07 2009-04-16 Bhavin Turakhia Method and system for providing a predetermined service to a domain registrant by a tld registry
US8199916B2 (en) 2007-12-26 2012-06-12 International Business Machines Corporation Selectively loading security enforcement points with security association information
US20110119724A1 (en) 2008-07-07 2011-05-19 Telefonaktiebolaget Lm Ericsson (Publ) Proxy Functionality
KR101091980B1 (en) 2008-10-16 2011-12-08 에스케이플래닛 주식회사 System and method for content delivery using cache server and browser cache
US20110219109A1 (en) 2008-10-28 2011-09-08 Cotendo, Inc. System and method for sharing transparent proxy between isp and cdn
US8856322B2 (en) * 2008-12-19 2014-10-07 Openpeak Inc. Supervisory portal systems and methods of operation of same
JP4991903B2 (en) * 2010-04-26 2012-08-08 シャープ株式会社 MFP, authentication server, the MFP control system, program and recording medium
US20120096106A1 (en) 2010-06-18 2012-04-19 Akamai Technologies, Inc. Extending a content delivery network (CDN) into a mobile or wireline network
US8943215B2 (en) * 2010-12-21 2015-01-27 Microsoft Corporation Distributed smooth streaming utilizing dynamic manifests
US8559433B2 (en) * 2011-01-07 2013-10-15 Jeda Networks, Inc. Methods, systems and apparatus for the servicing of fibre channel fabric login frames
FR2973978A1 (en) 2011-04-08 2012-10-12 France Telecom Method of communication between the distribution networks of digital contents
TW201720194A (en) 2011-06-01 2017-06-01 Interdigital Patent Holdings Content delivery network interconnection (CDNI) mechanism
US9747592B2 (en) 2011-08-16 2017-08-29 Verizon Digital Media Services Inc. End-to-end content delivery network incorporating independently operated transparent caches and proxy caches
US9774616B2 (en) * 2012-06-26 2017-09-26 Oppleo Security, Inc. Threat evaluation system and method
FR2995487A1 (en) 2012-09-11 2014-03-14 France Telecom processing technique of a content distribution request
2008-01-14 US US12/013,756 patent/US8543667B2/en active Active
2009-01-08 WO PCT/US2009/030495 patent/WO2009091666A1/en active Application Filing
2013-04-05 US US13/857,451 patent/US9544183B2/en active Active
US20020080886A1 (en) * 2000-04-07 2002-06-27 Ptasinski Henry S. Method for selecting frame encoding parameters in a frame-based communications network
"Proxy Server," Wikipedia, Jan. 15, 2008, 7 pages.
"Reverse Proxy," Wikipedia, Jan. 3, 2008, 2 pages.
"Web cache," Wikipedia, Jan. 9, 2008, 2 pages.
Berners-Lee, T., et al., "Hypertext Transfer Protocol-HTTP/1.0," http://tools.ietf.org/html/rfc1945, May 1996, 57 pages.
Berners-Lee, T., et al., "Hypertext Transfer Protocol—HTTP/1.0," http://tools.ietf.org/html/rfc1945, May 1996, 57 pages.
Cerpa, A., et al., "NECP the Network Element Control Protocol," http://tools.ietf.org/html/draft-cerpa.necp-02, Feb. 22, 2000, 38 pages.
Cooper, I., et al. "Known HTTP Proxy/Caching Problems," http://tools.ietf.org/html/rfc3143, Jun. 2001, 30 pages.
Cooper, I., et al., "Internet Web Replication and Caching Taxonomy," http://tools,ietf.org/html/rfc3040, Jan. 2001, 30 pages.
Cooper, I., et al., "Known HTTP Proxy/Caching Problems," draft-cooper-wrec-known-prob-01.txt, http://tools.ietf.org/html/draft-cooper-wrec-known-prob-01, Apr. 12, 2001, 32 pages.
Field, R., et al. Hypertext Transfer Protocol-HTTP/1.1, http://tools.ietf.org/html/rfc2616, Jun. 1999, 165 pages.
Field, R., et al. Hypertext Transfer Protocol—HTTP/1.1, http://tools.ietf.org/html/rfc2616, Jun. 1999, 165 pages.
Hurst et al., "MPEG Splicing: Tutorial and Proposed SMPTE Standard," SMPTE Journal: pp. 1-14 (Nov. 1998).
International Search Report and Written Opinion for International Application No. PCT/US2009/030495, Date of Mailing May 4, 2009 (8 pages).
Kristol, David M., "HTTP Proxy State Management Mechanism," http://tools.ietf.org/html/draft-kristol-http-proxy-state-00, May 26, 1998, 9 pages.
P. Vixie, et al., "Hyper Text Caching Protocol (HTCP/0.0)," http://tools.ietf.org/html/rfc2756, Jan. 2000, 15 pages.
SCTE 35 (ITU-T J.181): Digital Program Insertin Cueing Message for Cable, pp. 1-37, 2004.
U.S. Appl. No. 12/015,490, Method and Apparatus for Dynamic Transmission Rate Adjustment to Support Seamless Splicing of Compressed Video Streams, pp. 1-38, filed Jan. 16, 2008.
Zhang et al., "Integrated Rate Control and Buffer Management for Scalable Video Streaming," Multimedia and Expo, 2007 IEEE International Conference on, IEEE, PI, Jul. 1, 2007, pp. 248-251, XP031123608.
Zhang et al., "Joint Rate Allocation and Buffer Management for Robust Transmission of VBR Video," 20080301, vol. 34, No. 3, Mar. 1, 2008, pates 337-343, XP02551681.
US9344429B2 (en) * 2011-06-09 2016-05-17 Samsung Electronics Co., Ltd. Network apparatus based on content name and method for protecting content
US9531778B2 (en) * 2014-07-24 2016-12-27 Combined Conditional Access Development And Support, Llc Message rate mixing for bandwidth management
US20130232210A1 (en) 2013-09-05
US20090182843A1 (en) 2009-07-16
US9544183B2 (en) 2017-01-10
WO2009091666A1 (en) 2009-07-23
US7017175B2 (en) 2006-03-21 Digital television application protocol for interactive television
CN103518351B (en) 2016-12-28 Use file delivery method ip broadcast streaming service distribution
US7653685B2 (en) 2010-01-26 Methods and apparatuses for transferring streaming multimedia data and various types of data associated therewith in a network environment
US9369516B2 (en) 2016-06-14 Deltacasting
AU2002237989B8 (en) 2002-08-19 A service gateway for interactive television
JP6279621B2 (en) 2018-02-14 Internet protocol (ip) multimedia subsystem (ims) based peer-to-peer (p2p) content delivery
US7447242B2 (en) 2008-11-04 Method for real time protocol media recording
CN102347952B (en) 2013-08-07 Interactive media session establishing system, method and device based on IP (Internet Protocol) multi-media sub-system
US20100106770A1 (en) 2010-04-29 Dynamically adaptive network-based data processing system and method
DK2695355T3 (en) 2019-04-01 Network Streaming video data using byte-range requests
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:HLUCHYJ, MICHAEL G.;PAI, GANESH;REDDY, UMAMAHESWAR;REEL/FRAME:020433/0351