WO2018188073A1 - 内容部署方法及分发控制器 - Google Patents

内容部署方法及分发控制器 Download PDF

Info

Publication number
WO2018188073A1
WO2018188073A1 PCT/CN2017/080573 CN2017080573W WO2018188073A1 WO 2018188073 A1 WO2018188073 A1 WO 2018188073A1 CN 2017080573 W CN2017080573 W CN 2017080573W WO 2018188073 A1 WO2018188073 A1 WO 2018188073A1
Authority
WO
WIPO (PCT)
Prior art keywords
cache
deployment
content
request
server
Prior art date
Application number
PCT/CN2017/080573
Other languages
English (en)
French (fr)
Inventor
谢人超
谢俊峰
诸华林
黄韬
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2017/080573 priority Critical patent/WO2018188073A1/zh
Priority to CN201780088618.XA priority patent/CN110431804B/zh
Priority to EP17905120.6A priority patent/EP3598697B1/en
Publication of WO2018188073A1 publication Critical patent/WO2018188073A1/zh
Priority to US16/600,157 priority patent/US11057489B2/en

Links

Images

Classifications

    • 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/01—Protocols
    • H04L67/06—Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • 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/01—Protocols
    • H04L67/131—Protocols for games, networked simulations or virtual reality
    • 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
    • H04L67/5681—Pre-fetching or pre-delivering data based on network characteristics
    • 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/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • H04L67/63—Routing a service request depending on the request content or context

Definitions

  • the present application relates to the field of communications, and in particular, to a content deployment method and a distribution controller.
  • a Content Delivery Network is a technology that is capable of distributing content (for example, content such as videos/web pages) from a location closer to the user.
  • content for example, content such as videos/web pages
  • the video server of Facebook a social networking service website
  • CDN technology can deploy video/web pages of Facebook's video server closer to users in China, for example, in a city in China (for example, Beijing), then Chinese users can go directly from the city. Obtaining these contents can not only reduce the transmission delay but also reduce the occupation of network bandwidth resources.
  • Embodiments of the present application provide a novel content deployment method and distribution controller capable of implementing content deployment under the control of a content provider.
  • a content deployment method comprising: a distribution controller receiving a content deployment request from an application server controller, the content deployment request including identification information of the requested content and address information of an application server storing the requested content; and distributing Controller to the first cache
  • the server sends a first deployment cache request, where the first deployment cache request includes identification information of the requested content and address information of the application server, and the first deployment cache request is used to request the first cache server to obtain the requested content from the application server and cache.
  • the content deployment request further includes deployment area information
  • the method further includes: the distribution controller determines the first cache server from the deployment area indicated by the deployment area information; and/or the content deployment request further includes the first cache server.
  • the identification information further includes the distribution controller determining the first cache server according to the identification information of the first cache server.
  • the method further includes: the distribution controller sending a second deployment cache request to the second cache server, where the second deployment cache request includes the identifier information of the first cache server and the identification information of the requested content, and the second deployment cache The request is for requesting the second cache server to acquire the requested content from the first cache server and cache.
  • the method further includes: the distribution controller determining segmentation identification information of the requested content; and the distribution controller separately transmitting a third deployment cache request to the at least two third cache servers, where the third deployment cache request includes A cache server identifier information and segmentation identifier information of the requested content, the third deployment cache request is used to request the third cache server to obtain the segmentation of the requested content from the first cache server and cache.
  • a second aspect provides a content deployment method, including: a distribution controller receiving a content deployment request from an application server controller, the content deployment request including identification information of the requested content and address information of the application server storing the requested content; and distribution control Determining segmentation identification information of the requested content; and the distribution controller separately transmitting the first deployment cache request to the at least two first cache servers, where the first deployment cache request includes address information of the application server and segmentation identification information of the requested content, The first deployment cache request is used to request the first cache server to obtain the segmentation of the requested content from the application server and cache.
  • the content deployment request further includes deployment area information
  • the method further includes: the distribution controller determines the first cache server from the deployment area indicated by the deployment area information; and/or the content deployment request further includes the first cache server.
  • the identification information further includes the distribution controller determining the first cache server according to the identification information of the first cache server.
  • a distribution controller comprising: a deployment request receiving unit configured to receive a content deployment request from an application server controller, the content deployment request including the request The identification information of the content and the address information of the application server storing the requested content; and the cache request sending unit configured to send the first deployment cache request to the first cache server, wherein the first deployment cache request includes the identification information of the requested content and The address information of the application server, the first deployment cache request is used to request the first cache server to obtain the requested content from the application server and cache.
  • the content deployment request further includes deployment area information
  • the cache request sending unit is further configured to determine the first cache server from the deployment area indicated by the deployment area information; and/or the content deployment request further includes the first cache server
  • the cache request sending unit is further configured to determine the first cache server according to the identifier information of the first cache server.
  • the cache request sending unit is further configured to send a second deployment cache request to the second cache server, where the second deployment cache request includes identifier information of the first cache server and identification information of the requested content, and the second deployment cache The request is for requesting the second cache server to acquire the requested content from the first cache server and cache.
  • the cache request sending unit is further configured to: determine segmentation identification information of the requested content; separately send a third deployment cache request to the at least two third cache servers, where the third deployment cache request includes the first cache server The identification information and the segmentation identification information of the requested content, the third deployment cache request is used to request the third cache server to acquire the segmentation of the requested content from the first cache server and cache.
  • a distribution controller comprising: a deployment request receiving unit configured to receive a content deployment request from an application server controller, the content deployment request including identification information of the requested content and an application server storing the requested content
  • the cache request sending unit is configured to: determine segmentation identification information of the requested content; respectively send the first deployment cache request to the at least two first cache servers, where the first deployment cache request includes address information of the application server and The segment identification information of the content is requested, and the first deployment cache request is used to request the first cache server to acquire the segmentation of the requested content from the application server and cache.
  • the content deployment request further includes deployment area information
  • the cache request sending unit is further configured to determine the first cache server from the deployment area indicated by the deployment area information; and/or the content deployment request further includes the first cache server
  • the cache request sending unit is further configured to determine the first cache server according to the identifier information of the first cache server.
  • a distribution controller comprising: a communication interface; a memory storing computer executable instructions; and a processor implementing any one of the first and second aspects described above when executing the computer executable instructions Content deployment method.
  • the distribution controller controls the first cache server to acquire and cache all or part of the requested content stored in the application server in response to the content deployment request from the application server controller, and thus the first cache server is a condition permitted by the content provider Cache its contents. That is, the content deployment method and the distribution controller according to the embodiments of the present application can implement content deployment under the control of the content provider.
  • Figure 1 shows a schematic diagram of a content distribution process in a conventional MCDN
  • FIG. 2 is a schematic diagram showing a system architecture of a content distribution system according to an embodiment of the present application
  • FIG. 3 shows a schematic block diagram of a distribution controller in accordance with an embodiment of the present application
  • FIG. 4 through 8 illustrate schematic diagrams of an example content distribution process in a content distribution system in accordance with an embodiment of the present application
  • FIG. 9 is a structural diagram showing an exemplary hardware architecture of a computing device capable of implementing a distribution controller and a content deployment method thereof according to an embodiment of the present application.
  • FIG. 1 shows a schematic diagram of a content distribution process in a conventional MCDN.
  • the content distribution process in the traditional MCDN includes: S102, the first terminal requests an item of content from the application server; S104, the application server returns the content to the first terminal; S106, the content is transmitted from the application server In the process of the first terminal, the cache server caches the content; S108, the second terminal requests the content from the cache server; S110, the cache server returns the content to the second terminal.
  • first terminal and the second terminal may be the same terminal or different terminals.
  • first terminal and the second terminal are distinguished, and it is intended to illustrate that as long as a terminal requests the content from the application server and the content has been cached by the cache server, then any subsequent terminal can obtain the above from the cache server. content.
  • the second terminal can acquire the content from a cache server that is located closer, without acquiring the content from a remote application server, thereby reducing transmission delay and saving network bandwidth resources. use.
  • the cache server caches the above content autonomously, which is likely to involve an infringement problem, that is, the content is cached without the permission of the content provider of the above content. May be infringing.
  • a novel content distribution system, a distribution controller for use in a content distribution system, and content implemented by a distribution controller are provided
  • the deployment method can jointly cooperate with the content provider and the network provider to complete the deployment of the content provider's content in the network provider's cache server, thereby avoiding the active cache of the content provider's content by the network provider's cache server. Infringement of the relevant legal rights of the content provider.
  • a content distribution system, a distribution controller for use in a content distribution system, and a content deployment method implemented by a distribution controller according to an embodiment of the present application will be described in detail below with reference to the accompanying drawings.
  • the content distribution system 200 includes an application server (Application Server, AS for short) 202, and an application server controller (Application).
  • Application Server Application Server
  • Application server controller Application
  • the application server 202 is configured to store content provided by the content provider; the application server controller 204 is configured to deploy to a certain item of content stored in the application server 202 (hereinafter referred to as content A for convenience of description)
  • content A for convenience of description
  • the content deployment request is sent to the distribution controller 206 when in one or more cache servers 208; the distribution controller 206 is configured to send to the one or more cache servers 208 in response to the content deployment request sent by the application server controller 204, respectively.
  • cache server 208 is configured to retrieve content A from application server 202 or other cache server in response to deployment cache request sent by distribution controller 206 All content or corresponding segments and cache the entire content or corresponding segment of the obtained content A.
  • the content provider has a legal interest in the content stored in the application server 202; the application server 202 and the application server controller 204 are located in the content provider; the distribution controller 206 and the cache server 208 are located in the network provider; the application server 202
  • the application server controller 204, the distribution controller 206, and the one or more cache servers 208 can deploy the entire content or corresponding segments of the content A stored in the application server 202 to one or more cache servers 208 by interacting with each other. in.
  • both the application server 202 and the application server controller 204 are controlled by the content provider, ie, what content is stored by the application server 202, whether the application server controller 204 sends a content deployment request to the distribution controller 206, and what is sent for The content deployment request for the content can be controlled by the content provider.
  • the application server 202 and the application server controller 204 may be deployed in the same physical device or may be separately deployed in different physical devices, and may be deployed in the same geographical location or separately deployed in different geographical locations.
  • Application server 202 and application server controller 204 are logical concepts rather than physical concepts.
  • the application server 202 may include one or more physical servers; the application server controller 204 may be a central controller that uniformly controls all physical servers serving as the application server 202, and may also include one that controls the application server 202, respectively. Or one or more distributed controllers of multiple physical servers.
  • the distribution controller 206 controls one or more cache controllers 208 to acquire and cache the entire contents of the content A stored in the application server 206 in response to the content deployment request of the application server controller 204. Or corresponding segments, such that the one or more cache controllers 208 cache the entire content or corresponding segments of its content A under the conditions of the content provider's permission.
  • the content distribution system according to an embodiment of the present application can be used for a scenario in which all content providers actively deploy content to a network provider.
  • the content distribution system according to an embodiment of the present application is not limited to the system architecture shown in FIG. 2, but covers various system architectures that operate in accordance with the above-described working principles.
  • the content distribution system according to an embodiment of the present application may implement a mobile network of 5G/6G network, Long Term Evolution (LTE) network, fixed network, MulteFire network, home base station network, non-3GPP (eg, WIFI) access, global In a mobile communication system (GSM) network, or a wideband code division multiple access (WCDMA) network.
  • application server controller 204 may send a content deployment request to distribution controller 206 (hereinafter referred to as content for convenience of description)
  • content deployment request Q may include the identification information of the content A and the address information of the application server 202.
  • the distribution controller 204 can determine one or more cache servers from the cache server to which the signal is connected, or send the deployment cache to the determined one or more cache servers, either randomly or according to its own selection rules for the cache server. request.
  • the application server controller 204 is in addition to the content deployment request Q.
  • the location information (ie, the deployment area information) of the deployment area L may be added to the content deployment request Q. That is, the content deployment request Q may include identification information of the content A, address information of the application server 202, and deployment area information.
  • the distribution controller 206 may determine one or more cache servers from the deployment area L indicated by the deployment area information, and send a deployment cache request to the determined one or more cache servers.
  • application server controller 204 is configured to cause content A stored in application server 202 to be deployed in one or more cache servers 208 (eg, cache servers 208-1 and 208-2) specified by the content provider.
  • cache servers 208 eg, cache servers 208-1 and 208-2
  • the identification information of the cache servers 208-1 and 208-2 may be added in the content deployment request Q. That is, the content deployment request Q may include identification information of the content A, address information of the application server 202, and identification information of the cache servers 208-1 and 208-2.
  • the distribution controller 206 does not need to select the cache server by itself, but can directly send the deployment cache request to the cache servers 208-1 and 208-2, respectively.
  • the identifier information of the content A may be a Uniform Resource Identifier (URI), a Uniform Resource Locator (URL), or other information identifying the content of the content A;
  • the information may be the administrative area identification information corresponding to the deployment area L, the geographical area identification information, or other information indicating the location of the deployment area L.
  • the address information of the application server 202 may be the Internet Protocol (IP) of the application server 202.
  • IP Internet Protocol
  • the address can also be other information indicating the address of the application server.
  • the identification information of the content A and the address information of the application server 202 may be information that is merged together.
  • the URL of the content A contains both the identification information of the content A and the address information of the application server 202.
  • FIG. 3 shows a schematic block diagram of a distribution controller in accordance with an embodiment of the present application.
  • a distribution controller used in a content distribution system according to an embodiment of the present application and a content deployment method implemented thereby will be described in detail below with reference to the accompanying drawings.
  • the distribution controller 206 includes a deployment request receiving unit 206-2 and a cache request transmitting unit 206-4, wherein: the deployment request receiving unit 206-2 is configured to receive control from an application server.
  • Content deployment request Q of device 204 wherein content deployment request Q includes identification information of content A and address information of application server 202;
  • cache request sending unit 206-4 is configured to one or more cache servers 208 (described below for Conveniently, the cache servers 208-m through 208-n, m and n are integers greater than 0, send deployment cache requests.
  • the distribution controller 206 can control the cache servers 208-m through 208-n to obtain the entire content or corresponding segments of the content A from the application server 202, respectively.
  • At least one of the cache servers 208-m to 208-n (eg, the cache server 208-j, j is an integer greater than 0) acquires the entire contents of the content A from the application server 202 and controls the cache servers 208-m to 208 The other cache servers in -n get the entire content or corresponding segments of content A from cache server 208-j.
  • the cache server 208-m through 208-n whether the cache server obtains content A from the application server 202 or other cache server, obtains the entire content of the content A, or the corresponding segment, and Which segment of the content A is obtained is determined by the cache request transmitting unit 206-4 and specified in the deployment cache request sent to the cache server.
  • the cache server that acquires the entire content of the content A or the corresponding segment from the application server 202 is referred to as a first cache server, and the cache server that acquires the entire content of the content A from the first cache server is referred to as a second.
  • the cache server is cached, and the cache server that obtains the corresponding segment of the content A from the first cache server is referred to as a third cache server.
  • the first, second, and third cache servers may have the same or different physical or logical structures, here only to distinguish between the entire content of the content A or the corresponding segmented cache server from different content sources.
  • the first, second, and third cache servers distinguish.
  • the cache request sending unit 206-4 may be based on the identification information of the content A and the application server 202.
  • the address information generates a first deployment cache request for the first cache server 208-j, and sends the first deployment cache request to the first cache server 208-j to cause the first cache server 208-j to identify information according to the content A.
  • the address information of the application server 202 acquires the entire content of the content A from the application server 202 and caches it.
  • the cache request transmitting unit 206-4 may be based on the identification information and segmentation of the content A.
  • the range information of the Aj generates the segment identification information of the segment Aj, and then generates a first deployment cache request for the first cache server 208-j based on the segment identification information of the segment Aj and the address information of the application server 202, and A cache server 208-j sends the first deployment cache request to cause the first cache server 208-j to obtain the segment Aj from the application server 202 based on the segment identification information of the segment Aj and the address information of the application server 202.
  • the cache request sending unit 206-4 may generate the second cache based on the identification information of the content A and the identification information of the first cache server 208-j.
  • the second deployment cache request of the server 208-i sends the second deployment cache request to the second cache server 208-i, so that the second cache server 208-i is based on the identification information of the content A and the first cache server 208-
  • the identification information of j acquires the entire content of the content A from the first cache server 208-j.
  • the cache request transmitting unit 206 -4 may generate segment identification information of the segment Ak based on the identification information of the content A and the range information of the segment Ak, and then generate the segmentation information based on the segment identification information of the segment Ak and the identification information of the first cache server 208-j.
  • the third cache request of the third cache server 208-k sends the third deployment cache request to the third cache server 208-k, so that the third cache server 208-k determines the segment identification information according to the segment Ak and the third The identification information of a cache server 208-j acquires the segment Ak from the first cache server 208-j.
  • the cache request generation unit 206-4 first determines one or more cache servers that are signally connected to the distribution controller 206 as a cache server. 208-m to 208-n.
  • the cache request transmitting unit 206-4 may determine the content distribution system randomly or according to the selection rule of the distribution controller 206 itself for the cache server.
  • the cache servers 208-m through 208-n in 200 are the cache servers in which content A will be deployed.
  • the cache request transmitting unit 206-4 may determine the content distribution system 200
  • the cache servers 208-m to 208-n in the deployment area L indicated by the deployment area information are the cache servers in which the content A is to be deployed.
  • the cache request generation unit 206-4 does not need to execute the cache server. The function is selected, and the cache server corresponding to the identification information of the cache server included in the content cache request Q is determined as the cache server of the content A.
  • the distribution controller 206 may further include a cache distribution recording unit 206-6 configured to record the distribution of the content A in the cache servers 208-m to 208-n.
  • the cache distribution recording unit 206-8 may record the identification information of the content A or the segment identification information and storage of the corresponding segment of the content A upon receiving the deployment cache completion response from the cache servers 208-m to 208-n. Correspondence between the identification information of the cache server of the content A or the corresponding segment of the content A.
  • the specific details of the content deployment method implemented by the distribution controller 206 are the same as the specific details of the corresponding functional modules in the distribution controller 206, and thus will not be described herein.
  • FIG. 4 through 8 illustrate schematic diagrams of an example content distribution process in a content distribution system in accordance with an embodiment of the present application.
  • an example content deployment process implemented in the content distribution system 200 includes:
  • the application server controller 204 sends a content deployment request for the content A to the distribution controller 206, where the content deployment request includes the content ID of the content A, the location area ID, and the application server 202.
  • Address information (AS address).
  • the distribution controller 206 selects a cache server (eg, cache servers 208-1 and 208-2) according to the location area ID.
  • a cache server eg, cache servers 208-1 and 208-2
  • S406-S412 is a content deployment process of the cache server 208-1, wherein: the distribution controller 206 sends a deployment cache request to the cache server 208-1 requesting the cache server 208-1 to acquire the entire content of the content A from the application server 202, the deployment The cache request includes a content ID and an AS address; the cache server 208-1 acquires all the contents of the content A from the application server 202 according to the content ID and the AS address, and returns the deployment cache completion to the distribution controller 206 after completing the buffering of the content A. response.
  • S414-S420 is a content deployment process of the cache server 208-2, similar to the content deployment process of the cache server 208-1 shown in S406-S412.
  • the distribution controller 206 After receiving the deployment cache completion response from the cache servers 208-1 and 208-2, the distribution controller 206 returns a content deployment completion response to the application server controller 204 and updates the cache distribution record stored by itself.
  • the content deployment process shown in FIG. 5 differs from the content deployment process shown in FIG. 4 in that the content deployment request sent by the application server controller 204 to the distribution controller 206 does not include a location area ID, and includes, in addition to the content ID, the AS. In addition to the address, the identification information (Cache Server ID) of the cache servers 208-1 and 208-2 is also included. That is, the application server controller 204 has specified the cache servers 208-1 and 208-2 in which the content A is to be deployed, so the distribution controller 206 does not need to select the cache server.
  • the other contents in FIG. 5 are the same as the corresponding contents in FIG. 4, and details are not described herein again.
  • the content deployment process shown in FIG. 6 differs from the content deployment process shown in FIG. 4 in that the distribution controller 206 sends a request cache server 208-2 to the cache server 208-2 to obtain from the cache server 208-1 instead of the application server 202.
  • the deployment cache request of content A (cache server 208-1 has completed the acquisition and caching of content A in S606-S612).
  • the identification information of the content A included in the deployment cache request transmitted by the distribution controller 206 in S614 is content ID 2 instead of the content ID.
  • the content ID and the content ID2 are identification information of the content A, but since they are generated by different network elements, their expressions may be different.
  • the URL is used as the identification information of the content A
  • the content ID and the content ID 2 are the identification information of the content A, they are not the same.
  • the other content in FIG. 6 is the same as the corresponding content in FIG. 5, and details are not described herein again.
  • the content deployment process shown in FIG. 7 differs from the content deployment process shown in FIG. 4 in that the distribution controller 206 segments the content A and controls the cache servers 208-1 and 208-2 to obtain the content A from the application server 202, respectively. Different segments and cached.
  • the distribution controller 206 controls the cache server 208-1 to acquire the first segment from the application server 202 (whose identification information is content ID1) and caches it, and controls the cache server 208-2 to acquire the second segment from the application server 202 (its The identification information is content ID2) and is cached.
  • the other content in FIG. 7 is the same as the corresponding content in FIG. 4, and details are not described herein again.
  • the content deployment process shown in FIG. 8 differs from the content deployment process shown in FIG. 4 in that a cache server 208-3 is added, the distribution controller 206 segments the content A, and the control cache server 208-1 acquires from the application server 202.
  • the entire contents of the content A are cached, and the cache servers 208-2 and 208-3 are controlled to acquire different segments of the content A from the cache server 208-1 and cache them.
  • the distribution controller 206 controls the cache server 208-2 to cache the first segment and control the cache service.
  • the server 208-3 caches the second segment, wherein the first segment and the second segment may be part of the content of the content A, or may be all parts of the content A.
  • the other content in FIG. 7 is the same as the corresponding content in FIG. 4, and details are not described herein again.
  • the various numbers in the above description for the cache server and its corresponding segments are only for the purpose of distinguishing these cache servers and their corresponding segments, and do not represent any restrictions on any logical or connection relationship.
  • the various step numbers in FIGS. 4 to 8 do not indicate that the steps must be performed in the order indicated by the number. In fact, the steps may be performed in other orders as long as the cache request can be deployed separately for the corresponding cache server. Requesting the content, returning the content, deploying the cache, and responding to these processes.
  • the various numbersing of other related network elements in the above description are only for the purpose of distinguishing these network elements, and do not represent any limitation to them.
  • the distribution controller used in the content distribution system, and the content deployment method implemented by the distribution controller the content provider's content is completed by the joint content provider and the network provider in the network
  • the deployment of the provider enables content deployment under the control of the content provider.
  • FIG. 9 is a block diagram showing an exemplary hardware architecture of a computing device capable of implementing a distribution controller in accordance with an embodiment of the present application.
  • computing device 900 includes an input interface 902, a processor 903, a memory 904, and an output interface 905.
  • the input interface 902, the processor 903, the memory 904, and the output interface 905 are connected to each other through a bus 910.
  • the input interface 902 and the output interface 905 may be separate interfaces or may belong to the same communication interface;
  • the memory includes but is not limited to a random access memory (RAM), and a read only memory (Read).
  • ROM Read Only Memory
  • EPROM Erasable Programmable Read Only Memory
  • CD-ROM Compact Disc Read-Only Memory
  • the processor may be one or more central processing units (CPUs).
  • CPUs central processing units
  • the processor is a CPU, the CPU may be a single-core CPU or a multi-core CPU.
  • the distribution controller 206 may also be implemented to include: a communication interface; a memory storing computer executable instructions; and a processor that, when executing the computer executable instructions, implements the distribution controller and its content deployment method described in connection with FIGS. 3 and 4.
  • the functional blocks shown in the block diagrams described above may be implemented as hardware, software, firmware, or a combination thereof.
  • hardware When implemented in hardware, it can be, for example, an electronic circuit, an application specific integrated circuit (ASIC), suitable firmware, plug-ins, function cards, and the like.
  • ASIC application specific integrated circuit
  • elements of the present application are programs or code segments that are used to perform the required tasks.
  • the program or code segments can be stored in a machine readable medium or transmitted over a transmission medium or communication link through a data signal carried in the carrier.
  • a "machine-readable medium” can include any medium that can store or transfer information.
  • machine-readable media examples include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, radio frequency (RF) links, and the like.
  • the code segments can be downloaded via a computer network such as the Internet, an intranet, and the like.
  • B corresponding to A means that B is associated with A, and B can be determined according to A.
  • determining B from A does not mean that B is only determined based on A, and that B can also be determined based on A and/or other information.
  • the disclosed systems, devices, and methods may be implemented in other manners.
  • the device embodiments described above are merely illustrative.
  • the division of the unit is only a logical function division.
  • there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
  • the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, or an electrical, mechanical or other form of connection.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the embodiments of the present application.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本申请实施例提供了一种内容部署方法及分发控制器。该内容部署方法包括：分发控制器接收来自应用服务器控制器的内容部署请求，内容部署请求包括请求内容的标识信息和存储请求内容的应用服务器的地址信息；以及分发控制器向第一缓存服务器发送第一部署缓存请求，其中，第一部署缓存请求包括请求内容的标识信息和应用服务器的地址信息，第一部署缓存请求用于请求第一缓存服务器从应用服务器获取请求内容并缓存。根据本申请实施例的内容部署方法及分发控制器能够实现在内容提供方的控制下的内容部署。

Description

内容部署方法及分发控制器 技术领域
本申请涉及通信领域，尤其涉及一种内容部署方法及分发控制器。
背景技术
随着智能手机的普及，移动数据流量呈现爆炸式增长。在这种情况下，如何利用缓存技术来降低骨干网和核心网中的流量、减少电信运营商在移动网络设备扩容方面的投资成为亟需解决的问题。因此，移动内容分发网络(Mobile Content Delivery Network，简称MCDN)应运而生。
内容分发网络(Content Delivery Network，简称CDN)是一种能够将内容(例如，视频/网页等内容)从离用户更近的位置分发给用户的技术。例如，社交网络服务网站“脸书”(Facebook)的视频服务器部署在美国，如果中国的用户要访问该视频服务器的视频内容，那么由于该视频内容离中国的用户非常远、需要在美国和中国之间进行传输，所以不但传输时延很长而且需要占用很多网络带宽资源。CDN技术可以将Facebook的视频服务器的视频/网页等内容都部署在离中国的用户更近的地方，例如，部署在中国的一个城市(例如，北京)，那么中国的用户就可以直接从这个城市获取这些内容，这样不仅可以使传输时延得到降低同时也可以减少网络带宽资源的占用。
发明内容
本申请的实施例提供了一种新颖的内容部署方法及分发控制器，能够实现在内容提供方的控制下的内容部署。
第一方面，提供了一种内容部署方法，包括：分发控制器接收来自应用服务器控制器的内容部署请求，内容部署请求包括请求内容的标识信息和存储请求内容的应用服务器的地址信息；以及分发控制器向第一缓存服 务器发送第一部署缓存请求，其中，第一部署缓存请求包括请求内容的标识信息和应用服务器的地址信息，第一部署缓存请求用于请求第一缓存服务器从应用服务器获取请求内容并缓存。
在一些实现方式中，内容部署请求还包括部署区域信息，上述方法还包括分发控制器从部署区域信息指示的部署区域中确定第一缓存服务器；和/或内容部署请求还包括第一缓存服务器的标识信息，上述方法还包括分发控制器根据第一缓存服务器的标识信息确定第一缓存服务器。
在一些实现方式中，上述方法还包括：分发控制器向第二缓存服务器发送第二部署缓存请求，第二部署缓存请求包括第一缓存服务器的标识信息和请求内容的标识信息，第二部署缓存请求用于请求第二缓存服务器从第一缓存服务器获取请求内容并缓存。
在一些实现方式中，上述方法还包括：分发控制器确定请求内容的分段标识信息；以及分发控制器向至少两个第三缓存服务器分别发送第三部署缓存请求，第三部署缓存请求包括第一缓存服务器的标识信息和请求内容的分段标识信息，第三部署缓存请求用于请求第三缓存服务器从第一缓存服务器获取请求内容的分段并缓存。
第二方面，提供了一种内容部署方法，包括：分发控制器接收来自应用服务器控制器的内容部署请求，内容部署请求包括请求内容的标识信息和存储请求内容的应用服务器的地址信息；分发控制器确定请求内容的分段标识信息；以及分发控制器向至少两个第一缓存服务器分别发送第一部署缓存请求，第一部署缓存请求包括应用服务器的地址信息和请求内容的分段标识信息，第一部署缓存请求用于请求第一缓存服务器从应用服务器获取请求内容的分段并缓存。
在一些实现方式中，内容部署请求还包括部署区域信息，上述方法还包括分发控制器从部署区域信息指示的部署区域中确定第一缓存服务器；和/或内容部署请求还包括第一缓存服务器的标识信息，上述方法还包括分发控制器根据第一缓存服务器的标识信息确定第一缓存服务器。
第三方面，提供了一种分发控制器，包括：部署请求接收单元，被配置为接收来自应用服务器控制器的内容部署请求，内容部署请求包括请求 内容的标识信息和存储请求内容的应用服务器的地址信息；以及缓存请求发送单元，被配置为向第一缓存服务器发送第一部署缓存请求，其中，第一部署缓存请求包括请求内容的标识信息和应用服务器的地址信息，第一部署缓存请求用于请求第一缓存服务器从应用服务器获取请求内容并缓存。
在一些实现方式中，内容部署请求还包括部署区域信息，缓存请求发送单元还被配置为从部署区域信息指示的部署区域中确定第一缓存服务器；和/或内容部署请求还包括第一缓存服务器的标识信息，缓存请求发送单元还被配置为根据第一缓存服务器的标识信息确定第一缓存服务器。
在一些实现方式中，缓存请求发送单元还被配置为向第二缓存服务器发送第二部署缓存请求，第二部署缓存请求包括第一缓存服务器的标识信息和请求内容的标识信息，第二部署缓存请求用于请求第二缓存服务器从第一缓存服务器获取请求内容并缓存。
在一些实现方式中，缓存请求发送单元还被配置为：确定请求内容的分段标识信息；向至少两个第三缓存服务器分别发送第三部署缓存请求，第三部署缓存请求包括第一缓存服务器的标识信息和请求内容的分段标识信息，第三部署缓存请求用于请求第三缓存服务器从第一缓存服务器获取请求内容的分段并缓存。
第四方面，提供了一种分发控制器，包括：部署请求接收单元，被配置为接收来自应用服务器控制器的内容部署请求，内容部署请求包括请求内容的标识信息和存储请求内容的应用服务器的地址信息；以及缓存请求发送单元，被配置为：确定请求内容的分段标识信息；向至少两个第一缓存服务器分别发送第一部署缓存请求，第一部署缓存请求包括应用服务器的地址信息和请求内容的分段标识信息，第一部署缓存请求用于请求第一缓存服务器从应用服务器获取请求内容的分段并缓存。
在一些实现方式中，内容部署请求还包括部署区域信息，缓存请求发送单元还被配置为从部署区域信息指示的部署区域中确定第一缓存服务器；和/或内容部署请求还包括第一缓存服务器的标识信息，缓存请求发送单元还被配置为根据第一缓存服务器的标识信息确定第一缓存服务器。
第五方面，提供了一种分发控制器，包括：通信接口；存储器，存储有计算机可执行指令；以及处理器，在执行计算机可执行指令时实现上述第一和第二方面中的任意一种内容部署方法。
这里，分发控制器响应于来自应用服务器控制器的内容部署请求而控制第一缓存服务器获取并缓存应用服务器中存储的请求内容的全部或部分，因此第一缓存服务器是在内容提供方许可的条件下对其内容进行缓存的。即，根据本申请实施例的内容部署方法及分发控制器能够实现在内容提供方的控制下的内容部署。
附图说明
图1示出了传统MCDN中的内容分发过程的示意图；
图2示出了根据本申请实施例的内容分发系统的系统架构的示意图；
图3示出了根据本申请实施例的分发控制器的示意框图；
图4至图8示出了根据本申请实施例的内容分发系统中的示例内容分发过程的示意图；以及
图9是示出能够实现根据本申请实施例的分发控制器及其内容部署方法的计算设备的示例性硬件架构的结构图。
具体实施方式
现在将参考附图更全面地描述示例实施方式。在图中，为了清晰，可能夸大了区域和层的厚度。在图中相同的附图标记表示相同或类似的结构，因而将省略它们的详细描述。
此外，所描述的特征、结构或特性可以以任何合适的方式结合在一个或更多实施例中。在下面的描述中，提供许多具体细节从而给出对本申请的实施例的充分理解。然而，本领域技术人员将意识到，可以实践本申请的技术方案而没有所述特定细节中的一个或更多，或者可以采用其它的方法、组元、材料等。在其它情况下，不详细示出或描述公知结构、材料或者操作以避免模糊本申请的主要技术创意。
需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互组合。下面将参考附图并结合实施例来详细说明本申请。
图1示出了传统MCDN中的内容分发过程的示意图。如图1所示，传统MCDN中的内容分发过程包括：S102，第一终端向应用服务器请求某项内容；S104，应用服务器向第一终端返回上述内容；S106，在上述内容被从应用服务器传输到第一终端的过程中，缓存服务器缓存上述内容；S108，第二终端向缓存服务器请求上述内容；S110，缓存服务器向第二终端返回上述内容。
需要说明的是，第一终端和第二终端可以是同一终端也可以是不同终端。这里为了清楚，对第一终端和第二终端进行了区分，旨在说明只要有终端从应用服务器请求过上述内容并且上述内容已经被缓存服务器缓存，那么后续无论哪个终端都可以从缓存服务器获取上述内容。
在图1所示的内容分发过程中，第二终端可以从位置更近的缓存服务器获取上述内容，而不用从遥远的应用服务器获取上述内容，因此降低了传输时延并且节省了网络带宽资源的使用。但是，如图1中的步骤S106所示，缓存服务器是自主缓存上述内容的，这很可能会涉及到侵权问题，也就是说在未经上述内容的内容提供方许可的情况下缓存上述内容是可能会侵权的。
鉴于图1所示的传统MCDN中的内容分发过程的一个或多个上述问题，提供了一种新颖的内容分发系统、用在内容分发系统中的分发控制器、及由分发控制器实现的内容部署方法，能够联合内容提供方和网络提供方共同完成内容提供方的内容在网络提供方的缓存服务器中的部署，从而能够避免由于网络提供方的缓存服务器对内容提供方的内容的主动缓存而造成的对于内容提供方的相关法律权益的侵害。
下面结合附图，详细描述根据本申请实施例的内容分发系统、用在内容分发系统中的分发控制器、以及由分发控制器实现的内容部署方法。
图2示出了根据本申请实施例的内容分发系统的系统架构的示意图。如图2所示，根据本申请实施例的内容分发系统200包括应用服务器(Application Server，简称AS)202、应用服务器控制器(Application  Server Controller，简称AS Controller)204、分发控制器(Delivery Controller)206、以及一个或多个缓存服务器(Cache Server)208(图中仅示出两个缓存服务器208-1和208-2作为示例)，其中：应用服务器202被配置为存储内容提供方提供的内容；应用服务器控制器204被配置为在期望将应用服务器202中存储的某项内容(下面为了描述方便，称为内容A)部署到一个或多个缓存服务器208中时，向分发控制器206发送内容部署请求；分发控制器206被配置为响应于应用服务器控制器204发送的内容部署请求，分别向一个或多个缓存服务器208发送在这些缓存服务器中部署内容A的全部内容或相应分段的部署缓存请求；缓存服务器208被配置为响应于分发控制器206发送的部署缓存请求，从应用服务器202或其他缓存服务器获取内容A的全部内容或相应分段并缓存所获取的内容A的全部内容或相应分段。
可选地，内容提供方对应用服务器202中存储的内容具有相关法律权益；应用服务器202和应用服务器控制器204位于内容提供方；分发控制器206和缓存服务器208位于网络提供方；应用服务器202、应用服务器控制器204、分发控制器206、以及一个或多个缓存服务器208可以通过相互交互，将应用服务器202中存储的内容A的全部内容或相应分段部署到一个或多个缓存服务器208中。
可选地，应用服务器202和应用服务器控制器204二者均由内容提供方控制，即应用服务器202存储哪些内容、应用服务器控制器204是否向分发控制器206发送内容部署请求、以及发送针对什么内容的内容部署请求都可以由内容提供方控制。应用服务器202和应用服务器控制器204可以被合并部署在同一物理设备中也可以被分别部署在不同物理设备中，可以被合并部署在同一地理位置也可以被分别部署在不同地理位置。应用服务器202和应用服务器控制器204是逻辑概念而不是物理概念。在实际实现中，应用服务器202可以包括一个或多个物理服务器；应用服务器控制器204可以是统一控制充当应用服务器202的所有物理服务器的中央控制器，也可以包括分别控制充当应用服务器202的一个或多个物理服务器的一个或多个分布式控制器。
在图2所示的内容分发系统中，分发控制器206响应于应用服务器控制器204的内容部署请求而控制一个或多个缓存控制器208获取并缓存应用服务器206中存储的内容A的全部内容或相应分段，因此该一个或多个缓存控制器208是在内容提供方许可的条件下对其内容A的全部内容或相应分段进行缓存的。
相关领域技术人员应该理解的是，根据本申请实施例的内容分发系统可用于所有内容提供方主动向网络提供方部署内容的场景。根据本申请实施例的内容分发系统并不限于图2所示的系统架构，而是覆盖了按照上述工作原理进行运转的各种系统架构。例如，根据本申请实施例的内容分发系统可以实现在5G/6G网络、长期演进(LTE)网络、固定网络、MulteFire网络、家庭基站网络、非3GPP(例如，WIFI)接入的移动网络、全球移动通讯系统(GSM)网络、或者宽带码分多址(WCDMA)网络中。
通常，为了使应用服务器202中存储的内容A被部署在一个或多个缓存服务器208中，应用服务器控制器204可以在发送给分发控制器206的内容部署请求(下面为了描述方便，称为内容部署请求Q)中添加内容A的标识信息和应用服务器202的地址信息。即，内容部署请求Q可以包括内容A的标识信息和应用服务器202的地址信息。此时，分发控制器204可以随机或者根据其自身针对缓存服务器的选择规则，从与其信号连接的缓存服务器中确定一个或多个缓存服务器，并向所确定的一个或多个缓存服务器发送部署缓存请求。
在一些场景中，为了使应用服务器202中存储的内容A被部署在内容提供方指定的部署区域(下面为了描述方便，称为部署区域L)中，应用服务器控制器204除了在内容部署请求Q中添加内容A的标识信息和应用服务器202的地址信息以外，还可以在内容部署请求Q中添加部署区域L的位置信息(即，部署区域信息)。即，内容部署请求Q可以包括内容A的标识信息、应用服务器202的地址信息、以及部署区域信息。此时，分发控制器206可以从部署区域信息所指示的部署区域L中确定一个或多个缓存服务器，并向所确定的一个或多个缓存服务器发送部署缓存请求。
在一些场景中，为了使应用服务器202中存储的内容A被部署在内容提供方指定的一个或多个缓存服务器208(例如，缓存服务器208-1和208-2)中，应用服务器控制器204除了在内容部署请求Q中添加内容A的标识信息和应用服务器202的地址信息以外，还可以在内容部署请求Q中添加缓存服务器208-1和208-2的标识信息。即，内容部署请求Q可以包括内容A的标识信息、应用服务器202的地址信息、以及缓存服务器208-1和208-2的标识信息。此时，分发控制器206无需自己选择缓存服务器，而可以直接分别向缓存服务器208-1和208-2发送部署缓存请求。
可选地，内容A的标识信息可以是内容A的统一资源标识符(Uniform Resource Identifier，简称URI)、统一资源定位符(Uniform Resource Locator，简称URL)、或者其他标识该内容的信息；部署区域信息可以是部署区域L所对应的行政区域标识信息、地理区域标识信息、或者其他表明部署区域L的位置的信息；应用服务器202的地址信息可以是应用服务器202的互联网协议(Internet Protocol，简称IP)地址，也可以是其他表明该应用服务器的地址的信息。在一些情况下，内容A的标识信息和应用服务器202的地址信息可以是合并在一起的信息。例如，内容A的URL同时包含有内容A的标识信息和应用服务器202的地址信息。
图3示出了根据本申请实施例的分发控制器的示意框图。下面结合附图，详细描述用在根据本申请实施例的内容分发系统中的分发控制器及由其实现的内容部署方法。
如图3所示，根据本申请实施例的分发控制器206包括部署请求接收单元206-2和缓存请求发送单元206-4，其中：部署请求接收单元206-2被配置为接收来自应用服务器控制器204的内容部署请求Q，其中，内容部署请求Q包括内容A的标识信息和应用服务器202的地址信息；缓存请求发送单元206-4被配置为向一个或多个缓存服务器208(下面为了描述方便，称为缓存服务器208-m至208-n，m和n是大于0的整数)发送部署缓存请求。
在一些场景中，分发控制器206可以控制缓存服务器208-m至208-n分别从应用服务器202获取内容A的全部内容或相应分段，也可以控制缓 存服务器208-m至208-n中的至少一个缓存服务器(例如，缓存服务器208-j，j是大于0的整数)从应用服务器202获取内容A的全部内容并控制缓存服务器208-m至208-n中的其他缓存服务器从缓存服务器208-j获取内容A的全部内容或相应分段。
在一些场景中，对于缓存服务器208-m至208-n中的每个缓存服务器，该缓存服务器是从应用服务器202还是其他缓存服务器获取内容A、获取内容A的全部内容还是相应分段、以及获取内容A的哪个分段都是由缓存请求发送单元206-4确定并在发送给该缓存服务器的部署缓存请求中指定。
下面，为了方便描述，将从应用服务器202获取内容A的全部内容或相应分段的缓存服务器称为第一缓存服务器，将从第一缓存服务器获取内容A的全部内容的缓存服务器称为第二缓存服务器，并将从第一缓存服务器获取内容A的相应分段的缓存服务器称为第三缓存服务器。应该明白的是，第一、第二、和第三缓存服务器可以具有相同或不同的物理或逻辑结构，这里仅为了区分从不同内容源获取内容A的全部内容或相应分段的缓存服务器而对第一、第二、和第三缓存服务器进行区分。
为了使缓存服务器208-m至208-n中的第一缓存服务器208-j从应用服务器202获取内容A的全部内容，缓存请求发送单元206-4可以基于内容A的标识信息和应用服务器202的地址信息生成针对第一缓存服务器208-j的第一部署缓存请求，并向第一缓存服务器208-j发送该第一部署缓存请求，以使第一缓存服务器208-j根据内容A的标识信息和应用服务器202的地址信息从应用服务器202获取内容A的全部内容并缓存。
为了使缓存服务器208-m至208-n中的第一缓存服务器208-j从应用服务器202获取内容A的相应分段A-j，缓存请求发送单元206-4可以基于内容A的标识信息和分段A-j的范围信息生成分段A-j的分段标识信息，然后基于分段A-j的分段标识信息和应用服务器202的地址信息生成针对第一缓存服务器208-j的第一部署缓存请求，并向第一缓存服务器208-j发送该第一部署缓存请求，以使第一缓存服务器208-j根据分段A-j的分段标识信息和应用服务器202的地址信息从应用服务器202获取分段A-j。
为了使缓存服务器208-m至208-n中的第二缓存服务器208-i(i是大 于0的整数)从第一缓存服务器208-j获取内容A的全部内容，缓存请求发送单元206-4可以基于内容A的标识信息和第一缓存服务器208-j的标识信息生成针对第二缓存服务器208-i的第二部署缓存请求，并向第二缓存服务器208-i发送该第二部署缓存请求，以使第二缓存服务器208-i根据内容A的标识信息和第一缓存服务器208-j的标识信息从第一缓存服务器208-j获取内容A的全部内容。
为了使缓存服务器208-m至208-n中的第三缓存服务器208-k(k是大于0的整数)从第一缓存服务器208-j获取内容A的相应分段A-k，缓存请求发送单元206-4可以基于内容A的标识信息和分段A-k的范围信息生成分段A-k的分段标识信息，然后基于分段A-k的分段标识信息和第一缓存服务器208-j的标识信息生成针对第三缓存服务器208-k的第三部署缓存请求，并向第三缓存服务器208-k发送该第三部署缓存请求，以使第三缓存服务器208-k根据分段A-k的分段标识信息和第一缓存服务器208-j的标识信息从第一缓存服务器208-j获取分段A-k。
可选地，缓存请求生成单元206-4在生成针对缓存服务器208-m至208-n的部署缓存请求的过程中，首先确定与分发控制器206信号连接的一个或多个缓存服务器作为缓存服务器208-m至208-n。在内容缓存请求Q仅包括内容A的标识信息和应用服务器202的地址信息的情况下，缓存请求发送单元206-4可以随机或者根据分发控制器206自身针对缓存服务器的选择规则，确定内容分发系统200中的缓存服务器208-m至208-n作为内容A将被部署在其中的缓存服务器。在内容缓存请求Q除了包括内容A的标识信息和应用服务器202的地址信息以外还包括由内容提供方指定的部署区域信息的情况下，缓存请求发送单元206-4可以确定内容分发系统200中的、处在部署区域信息所指示的部署区域L中的缓存服务器208-m至208-n作为内容A将被部署在其中的缓存服务器。在内容缓存请求Q除了包括内容A的标识信息和应用服务器202的地址信息以外还包括由内容提供方指定的缓存服务器的标识信息的情况下，缓存请求生成单元206-4无需执行对于缓存服务器的选择功能，而将内容缓存请求Q中包括的缓存服务器的标识信息所对应的缓存服务器确定为内容A的缓存服务器。
可选地，根据本申请实施例的分发控制器206还可以包括缓存分布记录单元206-6，被配置为记录内容A在缓存服务器208-m至208-n中的分布情况。例如，缓存分布记录单元206-8可以在接收到来自缓存服务器208-m至208-n的部署缓存完成响应时，记录内容A的标识信息或内容A的相应分段的分段标识信息与存储内容A或者内容A的相应分段的缓存服务器的标识信息之间的对应关系。
由分发控制器206实现的内容部署方法的具体细节与分发控制器206中相应功能模块的具体细节相同，因此这里不再赘述。
图4至图8示出了根据本申请实施例的内容分发系统中的示例内容分发过程的示意图。下面结合附图，详细描述这些内容分发过程。
如图4所示，根据本申请实施例的内容分发系统200中实现的示例内容部署过程包括：
S402，应用服务器控制器204向分发控制器206发送针对内容A的内容部署请求，其中该内容部署请求包括内容A的标识信息(content ID)、部署区域信息(location area ID)、以及应用服务器202的地址信息(AS address)。
S404，分发控制器206根据location area ID选择缓存服务器(例如，缓存服务器208-1和208-2)。
S406-S412是缓存服务器208-1的内容部署过程，其中：分发控制器206向缓存服务器208-1发送请求缓存服务器208-1从应用服务器202获取内容A的全部内容的部署缓存请求，该部署缓存请求包括content ID和AS address；缓存服务器208-1根据content ID和AS address从应用服务器202获取内容A的全部被容，并在完成对内容A的缓存后向分发控制器206返回部署缓存完成响应。
S414-S420是缓存服务器208-2的内容部署过程，与S406-S412示出的缓存服务器208-1的内容部署过程类似。
S422，分发控制器206在接收到来自缓存服务器208-1和208-2的部署缓存完成响应后，向应用服务器控制器204返回内容部署完成响应，并更新自身存储的缓存分布记录。
图5所示的内容部署过程与图4所示的内容部署过程的区别在于，应用服务器控制器204发送给分发控制器206的内容部署请求中不包括location area ID，并且除了包括content ID、AS address以外还包括缓存服务器208-1和208-2的标识信息(Cache Server ID)。即，应用服务器控制器204已经指定内容A将被部署在其中的缓存服务器208-1和208-2，因此分发控制器206无需选择缓存服务器。图5中的其他内容与图4中的相应内容相同，此处不再赘述。
图6所示的内容部署过程与图4所示的内容部署过程的区别在于，分发控制器206向缓存服务器208-2发送请求缓存服务器208-2从缓存服务器208-1而不是应用服务器202获取内容A的部署缓存请求(缓存服务器208-1已经在S606-S612中完成内容A的获取与缓存)。这里，分发控制器206在S614中发送的部署缓存请求中包括的内容A的标识信息是content ID 2，而不是content ID。这里，content ID和content ID2都是内容A的标识信息，但是由于是由不同网络元件生成的，所以它们的表现形式可能不同。比如，使用URL作为内容A的标识信息时，虽然content ID和content ID 2都是内容A的标识信息，但是它们并不相同。图6中的其他内容与图5中的相应内容相同，此处不再赘述。
图7所示的内容部署过程与图4所示的内容部署过程的区别在于，分发控制器206将内容A分段，并控制缓存服务器208-1和208-2分别从应用服务器202获取内容A的不同分段并缓存。这里，分发控制器206控制缓存服务器208-1从应用服务器202获取第一分段(其标识信息是content ID1)并缓存，并控制缓存服务器208-2从应用服务器202获取第二分段(其标识信息是content ID2)并缓存。图7中的其他内容与图4中的相应内容相同，此处不再赘述。
图8所示的内容部署过程与图4所示的内容部署过程的区别在于，增添了缓存服务器208-3，分发控制器206将内容A分段，控制缓存服务器208-1从应用服务器202获取内容A的全部内容并缓存，并控制缓存服务器208-2和208-3从缓存服务器208-1获取内容A的不同分段并缓存。这里，分发控制器206控制缓存服务器208-2缓存第一分段，并控制缓存服 务器208-3缓存第二分段，其中，第一分段和第二分段可以是内容A的一部分内容，也可以是内容A的全部部分。图7中的其他内容与图4中的相应内容相同，此处不再赘述。
需要说明的是，以上描述中针对缓存服务器及其所对应的分段的各种编号仅是出于区分这些缓存服务器及其对应的分段的目的，而不表示对任何逻辑或连接关系的限制。另外，图4至8中的各种步骤编号并不表示这些步骤必须按照编号指示的先后顺序执行，实际上，这些步骤可以按照其他顺序执行，只要能够分别针对相应的缓存服务器实现部署缓存请求、请求获取内容、返回内容、部署缓存完成响应这些处理即可。类似地，以上描述中对于其他相关网络元件的各种编号也仅是出于区分这些网络元件的目的，而不表示对它们的任何限制。
根据本申请实施例的内容分发系统、用在内容分发系统中的分发控制器、及由分发控制器实现的内容部署方法，通过联合内容提供方和网络提供方共同完成内容提供方的内容在网络提供方的部署，即能够实现在内容提供方的控制下的内容部署。
结合图1至图8描述的内容分发系统中的各个网络元件都可以由计算设备实现。例如，图9是示出能够实现根据本申请实施例的分发控制器的计算设备的示例性硬件架构的结构图。如图9所示，计算设备900包括输入接口902、处理器903、存储器904、输出接口905。其中，输入接口902、处理器903、存储器904、以及输出接口905通过总线910相互连接。
可选地，输入接口902和输出接口905可以是分离的两个接口，也可以属于同一通信接口；存储器包括但不限于是随机存取存储器(Random Access Memory，简称RAM)、只读存储器(Read-Only Memory，简称ROM)、可擦除可编程只读存储器(Erasable Programmable Read Only Memory，简称EPROM)、或便携式只读存储器(Compact Disc Read-Only Memory，简称CD-ROM)，用于相关指令及数据；处理器可以是一个或多个中央处理器(Central Processing Unit，简称CPU)，在处理器是一个CPU的情况下，该CPU可以是单核CPU，也可以是多核CPU。
也就是说，根据本申请实施例的分发控制器206也可以被实现为包括： 通信接口；存储有计算机可执行指令的存储器；及处理器，该处理器在执行计算机可执行指令时可以实现结合图3和图4描述的分发控制器及其内容部署方法。
需要明确的是，本申请并不局限于上文所描述并在图中示出的特定配置和处理。为了简明起见，这里省略了对已知方法的详细描述。在上述实施例中，描述和示出了若干具体的步骤作为示例。但是，本申请的方法过程并不限于所描述和示出的具体步骤，本领域的技术人员可以在领会本申请的精神后，作出各种改变、修改和添加，或者改变步骤之间的顺序。
以上所述的结构框图中所示的功能块可以实现为硬件、软件、固件或者它们的组合。当以硬件方式实现时，其可以例如是电子电路、专用集成电路(ASIC)、适当的固件、插件、功能卡等等。当以软件方式实现时，本申请的元素是被用于执行所需任务的程序或者代码段。程序或者代码段可以存储在机器可读介质中，或者通过载波中携带的数据信号在传输介质或者通信链路上传送。“机器可读介质”可以包括能够存储或传输信息的任何介质。机器可读介质的例子包括电子电路、半导体存储器设备、ROM、闪存、可擦除ROM(EROM)、软盘、CD-ROM、光盘、硬盘、光纤介质、射频(RF)链路，等等。代码段可以经由诸如因特网、内联网等的计算机网络被下载。
另外，本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
应理解，在本申请实施例中，“与A相应的B”表示B与A相关联，根据A可以确定B。但还应理解，根据A确定B并不意味着仅仅根据A确定B，还可以根据A和/或其它信息确定B。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、计算机软件或者二者的结合来实现，为了清楚地说明硬件和软件的可互换性，在上述说明中已经按照功能一般性地描述了各示例的组成及步骤。这些功能究竟以硬件还是软件 方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为了描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另外，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口、装置或单元的间接耦合或通信连接，也可以是电的，机械的或其它的形式连接。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本申请实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以是两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到各种等效的修改或替换，这些修改或替换都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以权利要求的保护范围为准。

Claims (17)

  1. 一种内容部署方法，包括：
    分发控制器接收来自应用服务器控制器的内容部署请求，所述内容部署请求包括请求内容的标识信息和存储所述请求内容的应用服务器的地址信息；以及
    所述分发控制器向第一缓存服务器发送第一部署缓存请求，其中，所述第一部署缓存请求包括所述请求内容的标识信息和所述应用服务器的地址信息，所述第一部署缓存请求用于请求所述第一缓存服务器从所述应用服务器获取所述请求内容并缓存。
  2. 如权利要求1所述的内容部署方法，其特征在于，所述内容部署请求还包括部署区域信息，所述方法还包括：
    所述分发控制器从所述部署区域信息指示的部署区域中，确定所述第一缓存服务器。
  3. 如权利要求1所述的内容部署方法，其特征在于，所述内容部署请求还包括所述第一缓存服务器的标识信息，所述方法还包括：
    所述分发控制器根据所述第一缓存服务器的标识信息，确定所述第一缓存服务器。
  4. 如权利要求1到3中任意一项所述的内容部署方法，其特征在于，所述方法还包括：
    所述分发控制器向第二缓存服务器发送第二部署缓存请求，所述第二部署缓存请求包括所述第一缓存服务器的标识信息和所述请求内容的标识信息，所述第二部署缓存请求用于请求所述第二缓存服务器从所述第一缓存服务器获取所述请求内容并缓存。
  5. 如权利要求1到3中任意一项所述的内容部署方法，其特征在于，所述方法还包括：
    所述分发控制器确定所述请求内容的分段标识信息；以及
    所述分发控制器向至少两个第三缓存服务器分别发送第三部署缓存请求，所述第三部署缓存请求包括所述第一缓存服务器的标识信息和所述请 求内容的分段标识信息，所述第三部署缓存请求用于请求所述第三缓存服务器从所述第一缓存服务器获取所述请求内容的分段并缓存。
  6. 一种内容部署方法，包括：
    分发控制器接收来自应用服务器控制器的内容部署请求，所述内容部署请求包括请求内容的标识信息和存储所述请求内容的应用服务器的地址信息；
    所述分发控制器确定所述请求内容的分段标识信息；以及
    所述分发控制器向至少两个第一缓存服务器分别发送第一部署缓存请求，所述第一部署缓存请求包括所述应用服务器的地址信息和所述请求内容的分段标识信息，所述第一部署缓存请求用于请求所述第一缓存服务器从所述应用服务器获取所述请求内容的分段并缓存。
  7. 如权利要求6所述的内容部署方法，其特征在于，所述内容部署请求还包括部署区域信息，所述方法还包括：
    所述分发控制器从所述部署区域信息指示的部署区域中，确定所述第一缓存服务器。
  8. 如权利要求6所述的内容部署方法，其特征在于，所述内容部署请求还包括所述第一缓存服务器的标识信息，所述方法还包括：
    所述分发控制器根据所述第一缓存服务器的标识信息，确定所述第一缓存服务器。
  9. 一种分发控制器，包括：
    部署请求接收单元，被配置为接收来自应用服务器控制器的内容部署请求，所述内容部署请求包括请求内容的标识信息和存储所述请求内容的应用服务器的地址信息；以及
    缓存请求发送单元，被配置为向第一缓存服务器发送第一部署缓存请求，其中，所述第一部署缓存请求包括所述请求内容的标识信息和所述应用服务器的地址信息，所述第一部署缓存请求用于请求所述第一缓存服务器从所述应用服务器获取所述请求内容并缓存。
  10. 如权利要求9所述的分发控制器，其特征在于，所述内容部署请求还包括部署区域信息，所述缓存请求发送单元还被配置为从所述部署区 域信息指示的部署区域中确定所述第一缓存服务器。
  11. 如权利要求9所述的分发控制器，其特征在于，所述内容部署请求还包括所述第一缓存服务器的标识信息，所述缓存请求发送单元还被配置为根据所述第一缓存服务器的标识信息确定所述第一缓存服务器。
  12. 如权利要求9到11中任意一项所述的分发控制器，其特征在于，所述缓存请求发送单元还被配置为向第二缓存服务器发送第二部署缓存请求，所述第二部署缓存请求包括所述第一缓存服务器的标识信息和所述请求内容的标识信息，所述第二部署缓存请求用于请求所述第二缓存服务器从所述第一缓存服务器获取所述请求内容并缓存。
  13. 如权利要求到11中任意一项所述的分发控制器，其特征在于，所述缓存请求发送单元还被配置为：
    确定所述请求内容的分段标识信息；
    向至少两个第三缓存服务器分别发送第三部署缓存请求，所述第三部署缓存请求包括所述第一缓存服务器的标识信息和所述请求内容的分段标识信息，所述第三部署缓存请求用于请求所述第三缓存服务器从所述第一缓存服务器获取所述请求内容的分段并缓存。
  14. 一种分发控制器，包括：
    部署请求接收单元，被配置为接收来自应用服务器控制器的内容部署请求，所述内容部署请求包括请求内容的标识信息和存储所述请求内容的应用服务器的地址信息；以及
    缓存请求发送单元，被配置为
    确定所述请求内容的分段标识信息；
    向至少两个第一缓存服务器分别发送第一部署缓存请求，所述第一部署缓存请求包括所述应用服务器的地址信息和所述请求内容的分段标识信息，所述第一部署缓存请求用于请求所述第一缓存服务器从所述应用服务器获取所述请求内容的分段并缓存。
  15. 如权利要求14所述的分发控制器，其特征在于，所述内容部署请求还包括部署区域信息，所述缓存请求发送单元还被配置为从所述部署区域信息指示的部署区域中确定所述第一缓存服务器。
  16. 如权利要求14所述的分发控制器，其特征在于，所述内容部署请求还包括所述第一缓存服务器的标识信息，所述缓存请求发送单元还被配置为根据所述第一缓存服务器的标识信息确定所述第一缓存服务器。
  17. 一种计算机可读存储介质，其上存储有计算机程序，其特征在于，该程序被处理器执行时，实现如权利要求1-8中任意一项所述方法中的操作。
PCT/CN2017/080573 2017-04-14 2017-04-14 内容部署方法及分发控制器 WO2018188073A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
PCT/CN2017/080573 WO2018188073A1 (zh) 2017-04-14 2017-04-14 内容部署方法及分发控制器
CN201780088618.XA CN110431804B (zh) 2017-04-14 2017-04-14 内容部署方法及分发控制器
EP17905120.6A EP3598697B1 (en) 2017-04-14 2017-04-14 Content deployment method and distribution controller
US16/600,157 US11057489B2 (en) 2017-04-14 2019-10-11 Content deployment method and delivery controller

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/080573 WO2018188073A1 (zh) 2017-04-14 2017-04-14 内容部署方法及分发控制器

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/600,157 Continuation US11057489B2 (en) 2017-04-14 2019-10-11 Content deployment method and delivery controller

Publications (1)

Publication Number Publication Date
WO2018188073A1 true WO2018188073A1 (zh) 2018-10-18

Family

ID=63792175

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/080573 WO2018188073A1 (zh) 2017-04-14 2017-04-14 内容部署方法及分发控制器

Country Status (4)

Country Link
US (1) US11057489B2 (zh)
EP (1) EP3598697B1 (zh)
CN (1) CN110431804B (zh)
WO (1) WO2018188073A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11706292B1 (en) * 2022-03-15 2023-07-18 Disney Enterprises, Inc. Local preference in anycast CDN routing

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090254638A1 (en) * 2008-04-08 2009-10-08 At&T Intellectual Property I, L.P. Topology Aware Content Delivery Network
US20100036954A1 (en) * 2008-08-06 2010-02-11 Edgecast Networks, Inc. Global load balancing on a content delivery network
CN103139236A (zh) * 2011-11-23 2013-06-05 华为技术有限公司 一种元数据的处理方法、装置及cdn互通系统
CN105187848A (zh) * 2015-08-18 2015-12-23 浪潮软件集团有限公司 一种内容分发网络系统及方法
CN105577822A (zh) * 2016-01-27 2016-05-11 北京国电通网络技术有限公司 基于cdn节点的缓存集中管理系统

Family Cites Families (52)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6976090B2 (en) * 2000-04-20 2005-12-13 Actona Technologies Ltd. Differentiated content and application delivery via internet
US6993508B1 (en) * 2000-12-29 2006-01-31 Novell, Inc. Method and mechanism for vending digital content
US7421411B2 (en) * 2001-07-06 2008-09-02 Nokia Corporation Digital rights management in a mobile communications environment
US20050021467A1 (en) * 2001-09-07 2005-01-27 Robert Franzdonk Distributed digital rights network (drn), and methods to access operate and implement the same
US7136922B2 (en) * 2002-10-15 2006-11-14 Akamai Technologies, Inc. Method and system for providing on-demand content delivery for an origin server
US7191332B1 (en) * 2003-05-20 2007-03-13 Sprint Communications Company L.P. Digital rights management for multicasting content distribution
US7711647B2 (en) * 2004-06-10 2010-05-04 Akamai Technologies, Inc. Digital rights management in a distributed network
US9654456B2 (en) * 2006-02-16 2017-05-16 Oracle International Corporation Service level digital rights management support in a multi-content aggregation and delivery system
US8520850B2 (en) * 2006-10-20 2013-08-27 Time Warner Cable Enterprises Llc Downloadable security and protection methods and apparatus
US8028090B2 (en) * 2008-11-17 2011-09-27 Amazon Technologies, Inc. Request routing utilizing client location information
US7921259B2 (en) * 2007-09-07 2011-04-05 Edgecast Networks, Inc. Content network global replacement policy
US8447831B1 (en) * 2008-03-31 2013-05-21 Amazon Technologies, Inc. Incentive driven content delivery
US20100088405A1 (en) * 2008-10-08 2010-04-08 Microsoft Corporation Determining Network Delay and CDN Deployment
US8688837B1 (en) * 2009-03-27 2014-04-01 Amazon Technologies, Inc. Dynamically translating resource identifiers for request routing using popularity information
US8756341B1 (en) * 2009-03-27 2014-06-17 Amazon Technologies, Inc. Request routing utilizing popularity information
US9137300B1 (en) * 2009-06-30 2015-09-15 Amazon Technologies, Inc. Opportunistic pipe switching
US9342661B2 (en) * 2010-03-02 2016-05-17 Time Warner Cable Enterprises Llc Apparatus and methods for rights-managed content and data delivery
CN102244644B (zh) * 2010-05-11 2015-03-11 华为技术有限公司 多媒体文件发布方法和装置
US9906838B2 (en) * 2010-07-12 2018-02-27 Time Warner Cable Enterprises Llc Apparatus and methods for content delivery and message exchange across multiple content delivery networks
US8468222B2 (en) * 2010-11-16 2013-06-18 Edgecast Networks, Inc. Discrete mapping for targeted caching
CN102075358B (zh) * 2010-12-31 2013-10-30 网宿科技股份有限公司 针对大规模服务器集群的内容分发和部署的系统和方法
US8291083B2 (en) * 2011-02-01 2012-10-16 Limelight Networks, Inc. Distributed landing pad and brick topology for content storage in content delivery networks
US20120284804A1 (en) * 2011-05-02 2012-11-08 Authentec, Inc. System and method for protecting digital contents with digital rights management (drm)
CN102868542B (zh) * 2011-07-04 2018-02-16 中兴通讯股份有限公司 一种服务分发网络中服务质量的控制方法及系统
CN102231749B (zh) * 2011-08-12 2013-12-11 乐视网信息技术（北京）股份有限公司 一种利用cdn网络传输直播流的系统和方法
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
EP2791819B1 (en) * 2011-12-14 2017-11-01 Level 3 Communications, LLC Content delivery network
US9294582B2 (en) * 2011-12-16 2016-03-22 Microsoft Technology Licensing, Llc Application-driven CDN pre-caching
US8904009B1 (en) * 2012-02-10 2014-12-02 Amazon Technologies, Inc. Dynamic content delivery
US8909736B1 (en) * 2012-07-12 2014-12-09 Juniper Networks, Inc. Content delivery network referral
US10095803B2 (en) * 2012-07-31 2018-10-09 Apple Inc. Delivering content to electronic devices using local caching servers
US8356074B1 (en) * 2012-08-09 2013-01-15 Limelight Networks, Inc. Inter point of presence split architecture
US8561102B1 (en) * 2012-08-16 2013-10-15 General Instrument Corporation Location specific video content retrieval enabling regional blackouts to be maintained
US20160198202A1 (en) * 2012-12-10 2016-07-07 Koninklijke Kpn N.V. Digital Rights Management for Segmented Content
US20140165209A1 (en) * 2012-12-11 2014-06-12 Verizon Patent And Licensing Inc. Digital content delivery platform for multiple retailers
US9628345B2 (en) * 2012-12-13 2017-04-18 Level 3 Communications, Llc Framework supporting content delivery with collector services network
JP6205765B2 (ja) * 2013-03-12 2017-10-04 沖電気工業株式会社 映像配信装置、映像配信プログラム、映像配信方法及び映像配信システム
US9509596B2 (en) * 2013-06-07 2016-11-29 Fasly, Inc. Domain name system bypass in user applications
US9906618B2 (en) * 2013-12-06 2018-02-27 Fastly Inc. Return path selection for content delivery
US9838497B2 (en) * 2014-02-19 2017-12-05 Level 3 Communications, Llc Content delivery network architecture with edge proxy
US9678998B2 (en) * 2014-02-28 2017-06-13 Cisco Technology, Inc. Content name resolution for information centric networking
CN104219329A (zh) * 2014-09-28 2014-12-17 浪潮软件集团有限公司 一种集群服务器中通过内容分发部署业务的方法
US20160134694A1 (en) * 2014-11-07 2016-05-12 Startapp, Inc. Content delivery network based network latency reduction apparatus, methods and systems
CN104834722B (zh) 2015-05-12 2018-03-02 网宿科技股份有限公司 基于cdn的内容管理系统
US10506262B2 (en) * 2015-12-29 2019-12-10 Telefonaktiebolaget Lm Ericsson (Publ) Method and system for optimized media delivery
WO2017117456A1 (en) * 2015-12-31 2017-07-06 Quixey, Inc. Geo-fence pre-caching systems and methods for providing location-variant results
US10839096B2 (en) * 2016-03-28 2020-11-17 International Business Machines Corporation Cryptographically provable zero-knowledge content distribution network
FR3050599B1 (fr) * 2016-04-20 2018-05-11 4T Sa Procede et dispositif permettant l'application d'un systeme de controle d'acces a la protection des flux video en mode direct.
CN105978936A (zh) * 2016-04-25 2016-09-28 乐视控股（北京）有限公司 Cdn服务器及其缓存数据的方法
US10162943B2 (en) * 2016-04-27 2018-12-25 Comcast Cable Communications, Llc Streamlined digital rights management
US10687115B2 (en) * 2016-06-01 2020-06-16 Time Warner Cable Enterprises Llc Cloud-based digital content recorder apparatus and methods
US10404649B2 (en) * 2016-09-30 2019-09-03 DISH Technologies L.L.C. Content delivery optimization using adaptive and dynamic DNS

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090254638A1 (en) * 2008-04-08 2009-10-08 At&T Intellectual Property I, L.P. Topology Aware Content Delivery Network
US20100036954A1 (en) * 2008-08-06 2010-02-11 Edgecast Networks, Inc. Global load balancing on a content delivery network
CN103139236A (zh) * 2011-11-23 2013-06-05 华为技术有限公司 一种元数据的处理方法、装置及cdn互通系统
CN105187848A (zh) * 2015-08-18 2015-12-23 浪潮软件集团有限公司 一种内容分发网络系统及方法
CN105577822A (zh) * 2016-01-27 2016-05-11 北京国电通网络技术有限公司 基于cdn节点的缓存集中管理系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3598697A4 *

Also Published As

Publication number Publication date
US11057489B2 (en) 2021-07-06
CN110431804A (zh) 2019-11-08
EP3598697B1 (en) 2022-01-19
US20200045128A1 (en) 2020-02-06
CN110431804B (zh) 2021-07-09
EP3598697A1 (en) 2020-01-22
EP3598697A4 (en) 2020-01-22

Similar Documents

Publication Publication Date Title
US10033818B2 (en) Using listen ranges to deliver content to electronic devices from local caching servers
US9871850B1 (en) Enhanced browsing using CDN routing capabilities
US8175584B2 (en) System and method to facilitate downloading data at a mobile wireless device
CN110650112B (zh) 一种通用鉴权方法、装置及云服务网络系统
US9386099B2 (en) Local caching device, system and method for providing content caching service
US20150088995A1 (en) Method and apparatus for sharing contents using information of group change in content oriented network environment
US20120014321A1 (en) Messaging activity feed
US20170155712A1 (en) Method and device for updating cache data
KR20220116425A (ko) 듀얼 ｓｉｍ 폰을 통한 데이터 캐시 매커니즘
WO2021204510A1 (en) Relocation of application context to edge data network
CN112825524B (zh) 网络服务节点的确定方法、装置和系统
US11521250B2 (en) Method and apparatus for providing digital product using user account synchronization
WO2018188073A1 (zh) 内容部署方法及分发控制器
CN109672756B (zh) 一种数据传输方法及相关装置、服务器和存储介质
CN109474591B (zh) 多系统间帐户共享方法、装置、电子设备及存储介质
CN113473247B (zh) 一种视频播放请求处理方法、装置、系统和电子设备
US20220350748A1 (en) Consistent hashing for communication devices
CN113055254B (zh) 一种地址配置方法、装置、接入服务器及存储介质
CN115004657B (zh) 寻址方法、寻址系统以及寻址装置
EP4086781A1 (en) Data reading method and terminal
CN103685367A (zh) 离线下载系统和方法
CN108769274B (zh) 一种对话式文件传输方法、装置和设备/终端/服务器
WO2014183171A1 (en) System for efficient mobile data distribution
KR101632068B1 (ko) 컨텐츠 고유 식별자를 이용하여 컨텐츠를 전송하기 위한 방법, 시스템 및 컴퓨터 판독 가능한 기록 매체
CN108574714B (zh) 互联网资源获取方法、装置及互联网缓存系统

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: 17905120

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2017905120

Country of ref document: EP

Effective date: 20191017