WO2014002612A1 - Webコンテンツの配信装置 - Google Patents
Webコンテンツの配信装置 Download PDFInfo
- Publication number
- WO2014002612A1 WO2014002612A1 PCT/JP2013/062758 JP2013062758W WO2014002612A1 WO 2014002612 A1 WO2014002612 A1 WO 2014002612A1 JP 2013062758 W JP2013062758 W JP 2013062758W WO 2014002612 A1 WO2014002612 A1 WO 2014002612A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- content
- client
- web
- sub
- domain
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/957—Browsing optimisation, e.g. caching or content distillation
- G06F16/9574—Browsing optimisation, e.g. caching or content distillation of access to content, e.g. by caching
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/231—Content storage operation, e.g. caching movies for short term storage, replicating data over plural servers, prioritizing data for deletion
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/41—Structure of client; Structure of client peripherals
- H04N21/4104—Peripherals receiving signals from specially adapted client devices
- H04N21/4126—The peripheral being portable, e.g. PDAs or mobile phones
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/41—Structure of client; Structure of client peripherals
- H04N21/4104—Peripherals receiving signals from specially adapted client devices
- H04N21/4126—The peripheral being portable, e.g. PDAs or mobile phones
- H04N21/41265—The peripheral being portable, e.g. PDAs or mobile phones having a remote control device for bidirectional communication between the remote control device and client device
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
- H04N21/438—Interfacing the downstream path of the transmission network originating from a server, e.g. retrieving MPEG packets from an IP network
- H04N21/4381—Recovering the multiplex stream from a specific network, e.g. recovering MPEG packets from ATM cells
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
- H04N21/438—Interfacing the downstream path of the transmission network originating from a server, e.g. retrieving MPEG packets from an IP network
- H04N21/4383—Accessing a communication channel
- H04N21/4384—Accessing a communication channel involving operations to reduce the access time, e.g. fast-tuning for reducing channel switching latency
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
- H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
- H04N21/44—Processing of video elementary streams, e.g. splicing a video clip retrieved from local storage with an incoming video stream, rendering scenes according to MPEG-4 scene graphs
- H04N21/44016—Processing of video elementary streams, e.g. splicing a video clip retrieved from local storage with an incoming video stream, rendering scenes according to MPEG-4 scene graphs involving splicing one content stream with another content stream, e.g. for substituting a video clip
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client
- H04N21/61—Network physical structure; Signal processing
- H04N21/6106—Network physical structure; Signal processing specially adapted to the downstream path of the transmission network
- H04N21/6125—Network physical structure; Signal processing specially adapted to the downstream path of the transmission network involving transmission via Internet
Definitions
- the present invention relates to a Web content distribution apparatus, and is particularly suitable for distributing a multi-domain Web page in which content data constituting a Web page is distributed and arranged on a plurality of Web servers together with the html file.
- the present invention relates to a distribution device.
- Non-patent documents 1, 2 and 3 disclose techniques for speeding up the distribution of Web contents.
- Non-Patent Document 1 discloses a technique in which a server holds a TCP connection with a client for a certain period, thereby delivering a plurality of Web contents over a TCP connection once established. This eliminates the need to establish and disconnect a TCP connection for each content data, thereby realizing high-speed web content distribution.
- Non-Patent Document 2 describes the speed of Web content delivery in existing HTTP by requiring integration of TCP connections, push delivery from servers, multiplexing of requests, deletion of redundant headers, and compression of communication data. SPDY that improves the performance is disclosed. At this time, by implementing SPDY in the session layer that operates HTTP, high-speed Web content distribution can be realized without modifying the existing TCP, SSL, and HTTP.
- Non-Patent Document 3 a reverse proxy called an edge server is provided on a network, content data necessary for distribution of Web content and the like is held as a cache, and instead of a server that holds original content data, an edge server Discloses a technique for communicating with a client. As a result, the RTT is shortened compared to the case where communication is performed by the original server / client, and the Web content delivery speed is increased.
- the client first sends an html file from the Web server. To get.
- this html file the domain of the Web server in which each content data output to the Web page is distributed is described as a link destination.
- the client accesses each domain, acquires each content data, and combines them to reproduce the Web page. Therefore, the client cannot proceed to the next processing unless the acquisition of the html file is completed.
- Non-Patent Documents 1 and 3 the server does not support so-called server push distribution in which content is distributed to the client, so the client must access all the web servers and request content distribution. I had to.
- the number of sessions established simultaneously with the server is not limited, and content stored on the same Web server as the html file requested by the client Server push delivery is possible.
- requests from clients are required for content stored in other Web servers in different domains. Therefore, as schematically shown in FIG. 9, if the distribution target is a multi-domain web page, the client not only accesses the web server WS1 to acquire the html file, but also about other content data. However, they had to access and acquire the Web servers WS1, WS2, WS3 ... by themselves.
- An object of the present invention is to solve the above-described problems of the prior art and provide a Web content distribution apparatus capable of distributing a multi-domain Web page at high speed in response to a request from a client.
- the present invention caches a multi-domain web page including links to a plurality of contents in different domains, and delivers the web content in an alternative manner in response to a request from a client.
- This distribution apparatus is characterized in that it has the following configuration.
- a main content acquisition unit that acquires main content in which a domain linked to at least one sub-content included in a Web page is described; a sub-content acquisition unit that accesses the linked domain and acquires each sub content; Storage means for associating and caching the main and sub contents, and distribution means for distributing the main content and sub contents cached for the web page requested by the client.
- the html file of a web page in a multi-domain configuration and related content data are acquired from a plurality of web servers, cached in advance on a cache server, and managed in the same domain.
- the client can easily acquire not only the html file but also the content data by server push distribution simply by accessing the server.
- FIG. 1 is a block diagram showing a network configuration of a Web content distribution system according to an embodiment of the present invention. It is the figure which showed an example of the web page of a multi domain structure. It is the figure which showed the delivery method of the content which concerns on one Embodiment of this invention. It is the flowchart which showed the cache method of the web page content by the acceleration server. It is the flowchart which showed the delivery method of the web page by an acceleration server. It is the sequence flow which showed the delivery method of the Web page by the acceleration server. It is the sequence flow which showed the other delivery method of the web page by an acceleration server. It is a functional block diagram of an acceleration server. It is the figure which expressed typically the delivery method of the Web page by SPDY.
- FIG. 1 is a block diagram showing a network configuration of a Web content distribution system according to an embodiment of the present invention, in which html files (main content) and content data (sub-contents) are distributed for a multi-domain Web page.
- Multiple deployed web server WSs acceleration server AS that performs proxy server (alternate delivery) function between each web server WS and client, and html files and content data from the acceleration server AS
- the main configuration is a client that acquires and reproduces a desired Web page.
- a different domain is assigned to each Web server WS.
- the Web page to be distributed is composed of the html file A and three content data B, C, and D output to the page of the html file A as shown in FIG. Yes.
- the acceleration server AS and each Web server WS are connected by an appropriate connection such as an HTTP connection or an SPDY connection, and the client and the acceleration server AS are Connected by SPDY connection that can deliver server push.
- the html file A and the content data B are held in the Web server WS1 in the domain DN1
- the content data C and D are held in the Web server WS2 in the domain DN2.
- the domain DN3 is assigned to the acceleration server AS.
- the acceleration server AS caches each data of the web page from each web server WS
- the client accesses the acceleration server AS to store each cached data.
- the procedure to acquire is demonstrated.
- FIG. 4 is a flowchart showing an operation in which the acceleration server AS caches each data of the Web page from each Web server WS.
- the content A (html) is accessed by accessing the domain DN1 of the Web server WS1.
- File A) is obtained.
- the domain of each content data B, C, D is determined based on the link destination domain of each content data B, C, D described in the html file.
- the domain of content data B is determined as DN1
- the domains of content data C and D are determined as DN2.
- step S13 content data B, C, and D are acquired from the Web servers WS1 and WS2 by accessing the domains DN1 and DN2, respectively.
- step S14 the html file A and the content data B, C, D are edited as necessary.
- the link destination domains of the respective content data B, C, and D described in the html file A are all domains to which the request message is transmitted. Rewritten to DN1. If the file names of the content data B, C, and D are duplicated, they are rewritten to different file names so as not to duplicate.
- the acquired html file A and content data B, C, D are associated with each other and cached.
- FIG. 5 is a flowchart showing an operation in which the acceleration server AS delivers a Web page in response to a request from the client
- FIG. 6 is a sequence flow thereof.
- step S31 When the request message of the web page (html file A) is transmitted from the client to the acceleration server AS at time t1, the request message is received at step S31 by the acceleration server AS, and at time t2, the request message is received. A response message is returned.
- step S32 it is determined whether or not the requested html file A is held as cache information. If held, the process proceeds to step S33, and the html file A is read out and distributed to the client at time t3.
- step S34 it is determined whether or not there is content data related to the html file A.
- step S35 it is determined whether or not server push distribution of the content data B, C, D is possible.
- the multiple pushed request messages regarding the three content data B, C, and D are transmitted from the acceleration server AS to the client.
- step S36 it is determined that server push delivery is possible.
- step S36 the three cached content data B, C, and D are read, and distribution to the client is started at time t6.
- step S37 it is determined whether or not the distribution of all content data has been completed, and the process returns to step S34 to continue the related content distribution until completion. Thereafter, when the distribution of all the content data is completed, the process ends.
- step S32 if it is determined in step S32 that the requested web page is not cached, the cache processing described with reference to FIG. 4 is executed, and the cached html file A and each content data B, C and D are delivered to the client.
- the three content data B, C, and D are simultaneously delivered from the acceleration server AS to the client.
- the present invention is not limited to this, and for example, Web If it is known that the priority and importance of the content data B held in the server WS1 are higher than the priority and importance of the content data C and D held in the web server WS2, as shown in FIG.
- the content data B is first distributed first, and then the remaining content data C and D are distributed. May be distributed in the order according to the priority.
- only content data B having a high priority may be distributed and content data C and D having a low priority may not be distributed according to the congestion status of the network.
- FIG. 8 is a functional block diagram of the acceleration server AS, and illustrations of components unnecessary for the description of the present invention are omitted here.
- the main content acquisition unit 101 acquires the html file A of the Web page from the Web server on the network.
- the domain of the Web server is given separately.
- the domain analysis unit 102 determines the domain of each sub-content based on the link destination domain of each sub-content B, C, and D described in the html file.
- the sub-content acquisition unit 103 accesses the domains and acquires content data B, C, and D from each Web server.
- the acquired html file A and each content data B, C, D are cached in the storage unit 2 in association with each other as a content group constituting the Web page.
- the content editing unit 3 edits the link destination of each content so that the client can acquire the html file A and each content data B, C, D of the Web page from the same domain. That is, for each sub-content whose link destination is described in the html file A acquired by the main content acquisition unit 101, the domain editing unit 301 writes a description about the link destination domain from the original domain. Rewrite to sent domain DN1.
- the file name editing unit 302 refers to the file names of the content data B, C, and D acquired by the sub content acquisition unit 103, and sets the file name of the sub content with the duplicate file name to another file name that does not overlap. Rewrite.
- the storage unit 2 caches the html file A and the content data B, C, and D whose link destination domain and file name have been edited.
- the request reception unit 4 receives a Web page distribution request from a client.
- the request analysis unit 5 identifies the html file A and the sub contents B, C, and D necessary for the delivery of the Web page.
- the cache determination unit 6 determines whether or not the html file A and the sub contents B, C, and D are cached in the storage unit 2. Request the contents acquisition unit 1 to cache the contents B, C, and D.
- the content acquisition unit 1 executes the cache processing in response to the request.
- the main content distribution unit 701 reads the html file A cached in the storage unit 2 and distributes it to the client.
- the push determination unit 702 determines whether or not the client can support server push distribution. If the client supports server push distribution, the sub-content distribution unit 703 distributes the content data B, C, and D to the client. Otherwise, the sub-content distribution unit 703 distributes in response to a request from the client. To do.
- the html file and each content data are cached in advance in the same domain acceleration server AS, so the SPDY between the client and the acceleration server AS.
- the client simply sends a request message for the html file to the acceleration server AS so that not only the html file but also the remaining content data can be automatically acquired by server push delivery.
- the client Compared to the case where the client first acquires only the html file and identifies the domain of each content data, and then accesses each domain to acquire the remaining content data, as in the prior art, High-speed distribution becomes possible.
Abstract
Description
前記htmlファイルAおよびコンテンツデータBは、ドメインDN1のWebサーバWS1に保持され、コンテンツデータC,Dは、ドメインDN2のWebサーバWS2に保持されている。アクセラレションサーバASにはドメインDN3が割り当てられている。
ファイル名編集部302は、前記サブコンテンツ取得部103により取得されたコンテンツデータB,C,Dのファイル名を参照し、ファイル名が重複するサブコンテンツのファイル名を、重複しない他のファイル名に書き替える。前記記憶部2には、リンク先のドメインやファイル名が編集済みのhtmlファイルAおよびコンテンツデータB,C,Dがキャッシュされる。
Claims (8)
- 所在するドメインの異なる複数のコンテンツへのリンクを含むマルチドメイン構成のWebページを予めキャッシュし、クライアントからの要求に応答して代替配信するWebコンテンツの配信装置において、
Webページに含まれる少なくとも一つのサブコンテンツのリンク先のドメインが記述されたメインコンテンツを取得するメインコンテンツ取得手段と、
前記リンク先の各ドメインにアクセスして各サブコンテンツを取得するサブコンテンツ取得手段と、
前記メインおよびサブの各コンテンツを対応付けてキャッシュする記憶手段と、
クライアントからリクエストされたWebページに関してキャッシュされているメインコンテンツおよび各サブコンテンツを配信する配信手段とを具備したことを特徴とするWebコンテンツの配信装置。 - 前記メインコンテンツおよび各サブコンテンツを編集するコンテンツ編集手段を具備したことを特徴とする請求項1に記載のWebコンテンツの配信装置。
- 前記コンテンツ編集手段は、メインコンテンツに記述されている各サブコンテンツへのリンク先のドメインを当該メインコンテンツと同一のドメインに書き替えることを特徴とする請求項2に記載のWebコンテンツの配信装置。
- 前記コンテンツ編集手段は、ファイル名が重複するサブコンテンツのファイル名を、重複しない他のファイル名に書き替えることを特徴とする請求項2または3に記載のWebコンテンツの配信装置。
- クライアントから要求されたWebページに対応したメインおよびサブの各コンテンツが前記記憶手段にキャッシュされていないと、当該メインおよびサブの各コンテンツを各ドメインから取得して前記記憶手段にキャッシュした後、前記クライアントへ配信することを特徴とする請求項1ないし4のいずれかに記載のWebコンテンツの配信装置。
- 前記メインコンテンツがhtmlファイルであり、前記各サブコンテンツが、当該htmlファイルのページに出力されるコンテンツデータであることを特徴とする請求項1ないし5のいずれかに記載のWebコンテンツの配信装置。
- 前記クライアントとSPDYで通信し、前記サブコンテンツがサーバPushによりクライアントへ配信されることを特徴とする請求項1ないし6のいずれかに記載のWebコンテンツの配信装置。
- 前記各サブコンテンツに優先度が設定され、前記サーバPushによる配信対象または配信順序が、当該優先度に応じて選択されることを特徴とする請求項7に記載のWebコンテンツの配信装置。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
KR1020157002248A KR101663120B1 (ko) | 2012-06-29 | 2013-05-02 | Web 컨텐츠의 전송 장치 |
US14/411,609 US10127328B2 (en) | 2012-06-29 | 2013-05-02 | Distribution device for web content |
CN201380033272.5A CN104412263B (zh) | 2012-06-29 | 2013-05-02 | Web内容的发布装置 |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2012146859A JP5918642B2 (ja) | 2012-06-29 | 2012-06-29 | Webコンテンツの配信装置 |
JP2012-146859 | 2012-06-29 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2014002612A1 true WO2014002612A1 (ja) | 2014-01-03 |
Family
ID=49782786
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2013/062758 WO2014002612A1 (ja) | 2012-06-29 | 2013-05-02 | Webコンテンツの配信装置 |
Country Status (5)
Country | Link |
---|---|
US (1) | US10127328B2 (ja) |
JP (1) | JP5918642B2 (ja) |
KR (1) | KR101663120B1 (ja) |
CN (1) | CN104412263B (ja) |
WO (1) | WO2014002612A1 (ja) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2014157224A1 (ja) * | 2013-03-29 | 2014-10-02 | Kddi株式会社 | Webコンテンツの配信装置 |
WO2014157223A1 (ja) * | 2013-03-29 | 2014-10-02 | Kddi株式会社 | Webコンテンツの配信装置 |
WO2014157222A1 (ja) * | 2013-03-29 | 2014-10-02 | Kddi株式会社 | Webコンテンツの配信装置 |
WO2014157221A1 (ja) * | 2013-03-29 | 2014-10-02 | Kddi株式会社 | Webコンテンツの配信装置 |
Families Citing this family (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP6089363B2 (ja) * | 2013-02-04 | 2017-03-08 | 株式会社ウェブサービス・ディベロップメント | ネットワーク通信システム、サーバプッシュ通信制御サーバ、クライアント端末、サーバプッシュ通信制御方法、情報処理方法、およびプログラム |
US8924850B1 (en) * | 2013-11-21 | 2014-12-30 | Google Inc. | Speeding up document loading |
WO2015147354A1 (ko) * | 2014-03-27 | 2015-10-01 | 엘지전자 주식회사 | Spdy에 기초한 웹 가속 방법 및 이를 위한 spdy 프록시 |
US9992263B2 (en) * | 2014-10-10 | 2018-06-05 | Pulse Secure, Llc | Predictive prioritized server push of resources |
JP6489838B2 (ja) | 2015-01-15 | 2019-03-27 | キヤノン株式会社 | 送信装置、送信方法、及びプログラム |
JP6483636B2 (ja) * | 2016-03-28 | 2019-03-13 | Kddi株式会社 | Webコンテンツ配信方法 |
US10785286B2 (en) | 2016-05-05 | 2020-09-22 | International Business Machines Corporation | Proactive content push for enhancing real-time service delivery via cloud |
US10574723B2 (en) * | 2016-11-30 | 2020-02-25 | Nutanix, Inc. | Web services communication management |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2001265641A (ja) * | 2000-03-20 | 2001-09-28 | Nec Corp | ウェブコンテントの知的フェッチと配送のためのシステムと方法 |
JP2009217836A (ja) * | 2000-02-07 | 2009-09-24 | Netli Inc | ウェブ・コンテンツの高性能配信の方法 |
JP2010102509A (ja) * | 2008-10-23 | 2010-05-06 | Ntt Docomo Inc | データ中継装置及びデータ中継方法 |
Family Cites Families (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7953820B2 (en) * | 2002-09-11 | 2011-05-31 | Hughes Network Systems, Llc | Method and system for providing enhanced performance of web browsing |
US7565423B1 (en) * | 2004-06-30 | 2009-07-21 | Google Inc. | System and method of accessing a document efficiently through multi-tier web caching |
US7685255B2 (en) * | 2006-04-24 | 2010-03-23 | Blue Coat Systems, Inc. | System and method for prefetching uncacheable embedded objects |
CN101242422B (zh) * | 2007-02-06 | 2011-01-26 | 中国电信股份有限公司 | 适应多业务融合的内容分发网络系统和方法 |
US8812651B1 (en) * | 2007-02-15 | 2014-08-19 | Google Inc. | Systems and methods for client cache awareness |
US7941609B2 (en) * | 2007-02-23 | 2011-05-10 | Microsoft Corporation | HTTP acceleration by prediction and pre-fetching |
CN100484069C (zh) | 2007-05-21 | 2009-04-29 | 华为技术有限公司 | 一种文件数据分发方法及相关设备 |
US8321568B2 (en) | 2008-03-31 | 2012-11-27 | Amazon Technologies, Inc. | Content management |
US8495719B2 (en) * | 2008-10-02 | 2013-07-23 | International Business Machines Corporation | Cross-domain access prevention |
AU2010328326B2 (en) * | 2009-12-07 | 2016-12-01 | Robert Buffone | System and method for website performance optimization and internet traffic processing |
US8964757B2 (en) * | 2009-12-18 | 2015-02-24 | Qualcomm Incorporated | HTTP optimization, multi-homing, mobility and priority |
EP2583189B1 (en) * | 2010-06-18 | 2018-09-19 | Akamai Technologies, Inc. | Extending a content delivery network (cdn) into a mobile or wireline network |
-
2012
- 2012-06-29 JP JP2012146859A patent/JP5918642B2/ja not_active Expired - Fee Related
-
2013
- 2013-05-02 KR KR1020157002248A patent/KR101663120B1/ko active IP Right Grant
- 2013-05-02 US US14/411,609 patent/US10127328B2/en active Active
- 2013-05-02 WO PCT/JP2013/062758 patent/WO2014002612A1/ja active Application Filing
- 2013-05-02 CN CN201380033272.5A patent/CN104412263B/zh active Active
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2009217836A (ja) * | 2000-02-07 | 2009-09-24 | Netli Inc | ウェブ・コンテンツの高性能配信の方法 |
JP2001265641A (ja) * | 2000-03-20 | 2001-09-28 | Nec Corp | ウェブコンテントの知的フェッチと配送のためのシステムと方法 |
JP2010102509A (ja) * | 2008-10-23 | 2010-05-06 | Ntt Docomo Inc | データ中継装置及びデータ中継方法 |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2014157224A1 (ja) * | 2013-03-29 | 2014-10-02 | Kddi株式会社 | Webコンテンツの配信装置 |
WO2014157223A1 (ja) * | 2013-03-29 | 2014-10-02 | Kddi株式会社 | Webコンテンツの配信装置 |
WO2014157222A1 (ja) * | 2013-03-29 | 2014-10-02 | Kddi株式会社 | Webコンテンツの配信装置 |
WO2014157221A1 (ja) * | 2013-03-29 | 2014-10-02 | Kddi株式会社 | Webコンテンツの配信装置 |
Also Published As
Publication number | Publication date |
---|---|
CN104412263A (zh) | 2015-03-11 |
US10127328B2 (en) | 2018-11-13 |
CN104412263B (zh) | 2018-06-12 |
KR20150044429A (ko) | 2015-04-24 |
JP5918642B2 (ja) | 2016-05-18 |
KR101663120B1 (ko) | 2016-10-06 |
US20150161284A1 (en) | 2015-06-11 |
JP2014010622A (ja) | 2014-01-20 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
JP5918642B2 (ja) | Webコンテンツの配信装置 | |
CN101635737B (zh) | 下载方法、系统、p2p服务器、客户端 | |
US8171161B2 (en) | Static and dynamic content delivery | |
JP6278531B2 (ja) | ハイブリッドhttp及びudpコンテンツ配信 | |
US10904307B2 (en) | Distributed management of live stream storage | |
CN102629938B (zh) | 对网络视频加载进行视频加速的方法和系统 | |
US20100332589A1 (en) | Integrated static and dynamic content delivery | |
JP2006079606A5 (ja) | ||
EP2853074B1 (en) | Methods for optimizing service of content requests and devices thereof | |
CN101406060A (zh) | 应用对等(p2p)内容分发网络延时下载视频服务 | |
US20130144994A1 (en) | Content Delivery Network and Method for Content Delivery | |
WO2018044520A1 (en) | Anycast manifest retrieval, unicast content retrieval | |
CN1614931A (zh) | 基于ip网络数字媒体传送方法 | |
JP5614530B2 (ja) | 情報通信システム、ノード装置、情報処理方法、及び情報処理プログラム | |
EP2351254B1 (en) | Method and apparatus for receiving data by using peer-to-peer portal server | |
US9386056B1 (en) | System, method and computer readable medium for providing media stream fragments | |
JP6081846B2 (ja) | Webコンテンツの配信装置 | |
JP6081847B2 (ja) | Webコンテンツの配信装置 | |
JP6054799B2 (ja) | Webコンテンツの配信装置 | |
JP6081845B2 (ja) | Webコンテンツの配信装置 | |
JP6086838B2 (ja) | Webコンテンツ配信装置 | |
KR101091982B1 (ko) | 캐시서버와 브라우저캐시를 이용한 컨텐츠 캐싱방법 및 그 캐시서버 | |
Nekrasov et al. | Distributed load balancing for the adaptive video streaming using CDN with ring system of server consolidation by circulant topology | |
JP5338774B2 (ja) | 配信システム、情報処理装置、情報処理プログラム、及びコンテンツ投入方法 | |
Czyrnek et al. | PlatonTV: A Scientific High Definition Content Delivery Platform |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 13810854 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 14411609 Country of ref document: US |
|
ENP | Entry into the national phase |
Ref document number: 20157002248 Country of ref document: KR Kind code of ref document: A |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 13810854 Country of ref document: EP Kind code of ref document: A1 |