WO2018137149A1 - 一种内容请求方法及代理设备 - Google Patents

一种内容请求方法及代理设备 Download PDF

Info

Publication number
WO2018137149A1
WO2018137149A1 PCT/CN2017/072502 CN2017072502W WO2018137149A1 WO 2018137149 A1 WO2018137149 A1 WO 2018137149A1 CN 2017072502 W CN2017072502 W CN 2017072502W WO 2018137149 A1 WO2018137149 A1 WO 2018137149A1
Authority
WO
WIPO (PCT)
Prior art keywords
content
identifier
cache
proxy device
mec
Prior art date
Application number
PCT/CN2017/072502
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/072502 priority Critical patent/WO2018137149A1/zh
Publication of WO2018137149A1 publication Critical patent/WO2018137149A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications

Definitions

  • the embodiments of the present invention relate to the field of communications technologies, and in particular, to a content request method and a proxy device.
  • the core network of the wireless evolution network mainly includes a Mobility Management Entity (MME), a Serving Gateway (S-GW), and a packet data network gateway ( Packet Data Network Gateway (P-GW), which is responsible for network attached storage (NAS) signaling and NAS signaling encryption with user equipment, and assigns temporary identity to user equipment.
  • MME Mobility Management Entity
  • S-GW Serving Gateway
  • P-GW Packet Data Network Gateway
  • NAS network attached storage
  • P-GW Packet Data Network Gateway
  • select S-GW and P-GW/GGSN Gateway GPRS Support Node (GGSN); General Packet Radio Service (GPRS)
  • UMTS Universal Mobile Telecommunications System
  • SGSN Universal Mobile Telecommunications System
  • the S-GW is a mobility anchor for switching between Evolved Node Bs (eNodeBs) and provides lawful interception related functions.
  • the P-GW is an anchor point for user data transmission, and is responsible for user address allocation and policy. Control and billing rules are enforced and legally monitored.
  • the Home Subscriber Server (HSS) is used to store the subscription information of the user.
  • the Policy and Charging Rules Function (PCRF) provides policy and charging control rules.
  • the network element related to this application is P-GW, and other network elements are only for introduction.
  • a cache server in a mobile network is generally deployed behind the Gi interface of the GGSN or behind the SGi interface of the PGW to provide a cache service for users inside the gateway.
  • the user can directly obtain data directly from the cache server without obtaining content from the source server of the data.
  • the main problem with the above method is that the cache server is behind the GGSN or PGW, and the distance from the user terminal is relatively long, resulting in a large data transmission delay.
  • FIG. 2 it is a Mobile Edge Computing (MEC) cache scheme, in which a mobile network introduces a MEC network element, and its location is at the base station. Closer to the user's location with the GW. A bypassed Cache Server is deployed on the MEC (that is, a MEC Cache Server is connected to the MEC). Users can directly obtain content directly from the MEC Cache Server, which can further reduce the data transmission delay.
  • MEC Mobile Edge Computing
  • the main problem with this method is that because the MEC is located at a low level, the number of MECs will be large, so the MEC equipment cost cannot be too high, and the corresponding MEC Cache Server equipment cost cannot be too high, so each MEC Cache Server storage resources are limited, so you can't cache too much content, so many user content requests can't succeed (because there is no content), which leads to greatly reduced cache performance.
  • the prior art has a technical problem that the success rate of the terminal content request is low.
  • the embodiment of the present application provides a content request method and a proxy device, which are used to improve the success rate of a terminal content request.
  • an embodiment of the present application provides a content request method, including:
  • the proxy device receives a request message sent by the terminal, where the request message carries a content identifier
  • the proxy device After receiving the request message sent by the terminal, the proxy device obtains the identifier of the target cache device by using the content identifier, where the target cache device is a device that stores the requested content corresponding to the content identifier;
  • the proxy device sends the obtained request content to the terminal.
  • the proxy device receives the request message sent by the terminal, the request message carries the content identifier, and the identifier of the target cache device is obtained by using the content identifier, where the target cache device is a device that stores the requested content, and the proxy device is configured according to the target cache device. Identifying, obtaining the content of the request stored in the target cache device and transmitting the content to the terminal, so that the present application makes full use of the effect of the distributed cache, so that the content can be transmitted between the cache devices, when the proxy device itself does not find the content requested by the terminal The request content can be obtained from the target cache device storing the requested content, thereby greatly improving the success rate of the terminal content request and enhancing the effect of the cache.
  • the proxy device obtains the identifier of the target cache device by using the content identifier, including:
  • the proxy device queries the content index information of the content by using the content identifier to obtain the identifier of the target cache device;
  • the proxy device sends the content identifier to the cache controller, and receives an identifier of the target cache device obtained by the cache controller according to the content identifier.
  • the proxy device may store the content index message by itself, and thus may obtain the identifier of the target cache device by using the content index message stored by itself, or set a cache controller for managing the cache device in the system.
  • the proxy device can send a request message to the cache controller, and the cache controller returns the identifier of the target cache device to the proxy device.
  • the first way can reduce the hardware cost of the system; the second way uses centralized control, which can reduce the pressure of the proxy device.
  • the method further includes:
  • the proxy device fails to obtain the identifier of the target cache device by using the content identifier, requesting, by the source server, acquiring the requested content;
  • the proxy device sends the obtained request content to the terminal.
  • the proxy server when the proxy device fails to obtain the identifier of the target cache device by querying the content index information, the proxy server requests the source server to obtain the requested content, and ensures the success rate of the content requested by the terminal.
  • the proxy device fails to obtain the identifier of the target cache device by using the content identifier, the identifier of the source server is sent to the terminal And causing the terminal to request the source server to acquire the requested content according to the identifier of the source server.
  • the method further includes: the proxy device buffering the requested content.
  • the request content is also cached, so that the next time the terminal successfully requests the same request content to the proxy device, the success rate is improved.
  • the proxy device is a MEC cache server or a GW cache
  • the server the target cache device is a MEC cache server or a GW cache server.
  • the proxy device is integrated in the MEC or the GW.
  • the target cache device is integrated in the MEC or GW.
  • the cache controller is any one of the following:
  • a separate entity network element a control module integrated in the MEC, integrated in the GW, integrated in the proxy device or the target cache device.
  • the embodiment of the present application provides a proxy device, which can perform any content request method that implements the foregoing first aspect.
  • the proxy device includes a plurality of function modules, and is used to implement any one of the content request methods provided by the foregoing first aspect, so that the proxy device receives the request message sent by the terminal, and the request message carries the content identifier, and the request message carries the content identifier.
  • the content identifier acquires an identifier of the target cache device
  • the target cache device is a device that stores the requested content
  • the proxy device acquires the requested content stored in the target cache device according to the identifier of the target cache device, and sends the request content to the terminal, so that the application is sufficient
  • the content can be transferred between the cache devices.
  • the proxy device itself does not find the content requested by the terminal, the requested content can be obtained from the target cache device storing the requested content, and thus can be greatly Improve the success rate of the terminal content request, and enhance the effect of the cache.
  • the structure of the proxy device includes a processor and a transceiver configured to support the proxy device to perform the corresponding function in the content request method of the above first aspect.
  • the transceiver is configured to support communication between the proxy device and the terminal, and send information or instructions involved in the content request method to the terminal.
  • the proxy device can also include a memory for coupling with the processor that holds the program instructions and data necessary for the proxy device.
  • the embodiment of the present application provides a content request method, including:
  • the proxy device receives a request message sent by the terminal, where the request message carries a content identifier
  • the proxy device After receiving the request message sent by the terminal, the proxy device obtains the identifier of the target cache device by using the content identifier, where the target cache device is a device that stores the requested content corresponding to the content identifier;
  • the proxy device sends an identifier of the target cache device to the terminal.
  • the proxy device receives the request message sent by the terminal, and obtains the identifier of the target cache device by using the content identifier, where the target cache device is a device that stores the requested content, and the proxy device sends the identifier of the target cache device to the terminal. And causing the terminal to request the required request content from the target cache device. Therefore, the present application fully utilizes the effect of the distributed cache, and can greatly improve the success rate of the content request of the terminal, and enhance the effect of the cache.
  • the method further includes:
  • the proxy device fails to obtain the identifier of the target cache device by querying the content identifier, the identifier of the source server is sent to the terminal, so that the terminal requests the source server according to the identifier of the source server. Get the requested content.
  • the terminal when the proxy device fails to obtain the identifier of the target cache device by querying the content identifier, the terminal is notified to the source server to obtain the requested content, and the success rate of the content requested by the terminal is ensured.
  • the proxy device if the proxy device fails to obtain the identifier of the target cache device by using the content identifier, the proxy device requests the source server to obtain the requested content.
  • the proxy device sends the obtained request content to the terminal.
  • the proxy device is an MEC cache server or a GW cache server
  • the target cache device is an MEC cache server or a GW cache server.
  • the proxy device is integrated into the MEC Or GW, the target cache device is integrated in the MEC or GW.
  • the proxy device obtains the identifier of the target cache device by using the content identifier, including:
  • the proxy device queries the content index information of the content by using the content identifier to obtain the identifier of the target cache device;
  • the proxy device sends the content identifier to the cache controller, and receives an identifier of the target cache device obtained by the cache controller according to the content identifier.
  • the cache controller is any one of the following: a separate physical network element, integrated in the MEC, integrated in the GW, integrated in the proxy device, or the target cache device.
  • the embodiment of the present application provides a proxy device, which can perform any content request method that implements the foregoing third aspect.
  • the proxy device includes a plurality of functional modules, and is configured to implement any one of the content request methods provided by the foregoing third aspect, so that the proxy device receives the request message sent by the terminal, and obtains the target cache device by using the content identifier.
  • the target cache device is a device that stores the requested content, and the proxy device sends the identifier of the target cache device to the terminal, so that the terminal requests the requested content from the target cache device. Therefore, the present application fully utilizes the effect of the distributed cache, and can greatly improve the success rate of the content request of the terminal, and enhance the effect of the cache.
  • the structure of the proxy device includes a processor and a transceiver configured to support the proxy device to perform the corresponding function in the content request method of the above third aspect.
  • the transceiver is configured to support communication between the proxy device and the terminal, and send information or instructions involved in the content request method to the terminal.
  • the proxy device can also include a memory for coupling with the processor that holds the program instructions and data necessary for the proxy device.
  • the embodiment of the present application provides a computer storage medium for storing computer software instructions used by the proxy device provided in the foregoing second aspect, which includes a program designed to execute the foregoing first aspect.
  • the embodiment of the present application provides a computer storage medium for storing computer software instructions used by the proxy device provided in the foregoing fourth aspect, which includes a program designed to execute the foregoing third aspect.
  • the present application also provides a computer program product comprising instructions which, when run on a computer, cause the computer to perform the methods described in the above aspects.
  • FIG. 3 is a schematic diagram of a distributed cache application architecture according to an embodiment of the present application.
  • Embodiment 4 is a schematic diagram of a distributed cache application architecture provided by Embodiment 1 and Embodiment 2 of the present application;
  • FIG. 5 is a flowchart of a content request method according to Embodiment 1 of the present application.
  • FIG. 6 is a flowchart of a content request method according to Embodiment 2 of the present application.
  • FIG. 7 is a schematic diagram of a distributed cache application architecture provided by Embodiment 3 and Embodiment 4 of the present application;
  • FIG. 8 is a flowchart of a content request method according to Embodiment 3 of the present application.
  • FIG. 9 is a flowchart of a content request method according to Embodiment 4 of the present application.
  • FIG. 10 is a schematic diagram of a distributed cache application architecture provided by Embodiment 5 and Embodiment 6 of the present application;
  • FIG. 11 is a flowchart of a content request method according to Embodiment 5 of the present application.
  • FIG. 13 is a proxy device according to an embodiment of the present application.
  • FIG. 14 is a proxy device according to an embodiment of the present application.
  • FIG. 15 is a device provided by an embodiment of the present application.
  • the network elements involved in this application mainly include:
  • Terminal in the present application, for requesting acquisition of content from a proxy device or a source server and receiving the returned content;
  • the proxy device is configured to receive the request of the terminal, and provide the terminal with the content of the request or the location of the requested content.
  • the proxy device may be the MEC cache server or the GW cache server; or the proxy device may be integrated in the proxy device. MEC or GW.
  • the target cache device stores the content requested by the terminal, and is used to return the content requested by the terminal to the proxy device, or directly return the content requested by the terminal to the terminal.
  • the target cache device may be the MEC cache server or the GW.
  • the cache server; or the target cache device may also be integrated in the MEC or GW, wherein the GW may be a PGW, or may be an S-GW, a distributed gateway (D-GW), or a gateway of a 5G network. Specifically, there are no restrictions.
  • Cache Controller There is location information stored in the content, and location information of the content storage is provided in the present application. It should be noted that the cache controller may be a separate physical network element, or may be integrated in the MEC, or integrated in the GW, or integrated in the Cache Server (ie, the proxy device and the target cache device in the embodiment of the present application). .
  • FIG. 3 is a schematic diagram of a distributed cache application architecture provided by an embodiment of the present application.
  • the terminal sends a request message to the base station, and the base station forwards the request message to the MEC 1, and the MEC 1 forwards the request message to the MEC Cache Server 1.
  • the MEC Cache Server 1 is the proxy device (of course, if MEC Cache Server 1 is integrated in MEC 1, then MEC1 is the proxy device).
  • MEC Cache Server 1 When MEC Cache Server 1 stores the content requested by the terminal, the content requested by the terminal is Returned to the terminal; when the MEC Cache Server 1 does not store the content requested by the terminal, it goes to the cache controller (not shown in the figure, the cache controller may be integrated into the MEC 1, or integrated into the MEC Cache Server 1, or integrated in MEC 2, or integrated in MEC Cache Server 2, or integrated in GW 1, or integrated in GW Cache Server 1, or integrated in GW 2, or integrated in GW Cache Server 2, or a separate physical network element), cache The controller returns the location of the content requested by the terminal to the MEC Cache Server 1 (that is, returns the identifier of the target cache device, and the target cache device stores the terminal request Content, assume that the target device is a cache MEC Cache Server 2), MEC Cache Server 1 then acquires the content requested by the terminal to request MEC Cache Server 2, and sends the terminal.
  • the cache controller may be integrated into the MEC 1, or integrated into the MEC Cache Server 1,
  • the proxy device and the target cache device may both be GW Cache Server; or the proxy device is MEC Cache Server, the target cache device is the GW Cache Server; or the proxy device is the GW Cache Server, and the target cache device is the MEC Cache Server.
  • the above application architecture is based on a 4G network, but is not limited to a 4G network.
  • Any mobile network architecture is applicable to the present application, such as a General Packet Radio Service (GPRS) network, a 4.5G network, a 5G network, and the like.
  • GPRS General Packet Radio Service
  • All the cache nodes in the application architecture can transmit data to each other. Specifically, it can be a direct connection transmission. Data can also be an indirect connection to transfer data.
  • the proxy device is the MEC cache server
  • the target cache device is the MEC cache server
  • FIG. 4 is a schematic diagram of a distributed cache application architecture provided by an embodiment of the present application, where the MEC Cache Server 1 is a proxy device, and the MEC Cache Server 2 is a target cache device.
  • FIG. 5 is a flowchart of a content request method according to an embodiment of the present application.
  • the method shown in FIG. 5 corresponds to the architecture shown in FIG. 4, and includes the following steps:
  • Step 1 After the UE (terminal) establishes a connection with the MEC Cache Server 1 (proxy device), the UE sends a request message (Request message) to the MEC Cache Server 1.
  • the request message may carry a content identifier (ID) for indicating the content to be requested.
  • ID is specifically a content name, a Uniform Resource Identifier (URI), and the like. That is, in step 1, the terminal transmits the content ID to the Cache Controller.
  • URI Uniform Resource Identifier
  • the request message may specifically be a content request message.
  • the MEC Cache Server 1 can record the address information of the Source Server after receiving the data packet sent by the UE (the terminal) (for example, the data packet carries the IP address of the source server).
  • Step 2 When the MEC Cache Server 1 has the content requested by the UE, the content achivement message is returned to the UE, and the content requested by the UE is sent to the UE, and the process ends.
  • the MEC Cache Server 1 does not have the content requested by the UE in the above step 2, the following steps 3 to 7 are performed.
  • Step 3 The MEC Cache Server 1 sends a cache location request message to the Cache Controller.
  • the cache location request may carry the content ID for indicating the content to be requested.
  • the MEC Cache Server 1 sends the content ID to the Cache Controller.
  • Step 4 The Cache Controller returns a cache location response (cache location response) message to the MEC Cache Server 1, which carries the identifier of the target cache device (MEC Cache Server 2).
  • MEC Cache Server 2 carries the identifier of the target cache device (MEC Cache Server 2).
  • MEC Cache Server 2 carries the identifier of the target cache device (MEC Cache Server 2).
  • it may be a Location ID, where the Location ID is used to indicate where the content is located, ie, which cache server is included in the content.
  • it may be a server ID (server ID), or a location where the identifier content such as a server address (server address) is located, and the present application does not impose restrictions (the identification may also be mutually converted).
  • the Cache Controller When there is no cache of the content in the mobile network area under the jurisdiction (that is, the area covered by the Cache Controller), it may be named by a special identifier, for example, it may be *, #, or null, or may not carry any identifier. Ben Shen Please do not limit the format of the specific logo.
  • the Cache Controller returns the identifier of the target cache device to the MEC Cache Server 1.
  • the Cache Controller stores content index information indicating the storage location where each request content is located, for example, may be stored in the form of a database table, and an implementation is provided with reference to Table 1. the way.
  • different content ID forms can be mutually converted, for example, a URI is received, and a correspondence between a content name and a storage location ID is recorded in the database, and the cache controller can first receive the URI. Convert to the corresponding content name, and then look up the database according to the content name obtained after the conversion, and obtain the storage location ID corresponding to the content name. That is, the conversion between different forms of content IDs in this application does not affect the implementation of the present application.
  • the embodiment of the present application further provides an alternative implementation of the foregoing steps 3 and 4, that is, the proxy device stores the content index information in the solution in this application, and in this case, the MEC Cache Server 1 can pass its own The content index information is obtained by identifying the identifier of the MEC Cache Server 2.
  • the Cache Controller network element is removed, thereby reducing system hardware device overhead.
  • the Cache Controller network element is set, and the centralized device control mode can reduce the pressure of the proxy device.
  • Step 5 The MEC Cache Server 1 establishes a connection with the MEC Cache Server 2, and sends a request message to the MEC Cache Server 2, where the request message carries the content ID.
  • the MEC Cache Server 1 sends a content ID to the MEC Cache Server 2 for requesting the acquired content.
  • the MEC Cache Server 1 may directly send the content ID to the MEC Cache Server 2, or may forward the content ID to the MEC Cache Server 2 through the MEC 1 (as shown in the figure).
  • Step 6 The MEC Cache Server 2 sends a content achievement to the MEC Cache Server 1.
  • the MEC Cache Server 2 sends the content requested by the UE to the MEC Cache Server 1.
  • the MEC Cache Server 2 may directly send the content requested by the UE to the MEC Cache Server 1, or may forward the content requested by the UE through the MEC1.
  • Step 7 The MEC Cache Server 1 sends a content achievement to the UE, and the process ends.
  • the MEC Cache Server 1 transmits the content requested by the UE to the UE.
  • the Cache Controlle fails to provide the content (for example, the Cache Controlle sends a special identifier to the MEC Cache Server 1), the following steps 8 to 10 are performed.
  • Step 8 The MEC Cache Server 1 establishes a connection with the Source Server and sends a request message to the Source Server.
  • the MEC Cache Server 1 sends a request message (content ID) to the Source Server, requesting to acquire the content requested by the UE. Specifically, the MEC Cache Server 1 obtains the address information of the Source Server according to step 1.
  • the Source Server can be a server or a server group composed of multiple servers.
  • Step 9 The Source Server returns a content achievement to the MEC Cache Server 1.
  • the content achievement carries the content requested by the UE.
  • the Source Server returns the content requested by the UE to the MEC Cache Server 1.
  • Step 10 The MEC Cache Server 1 returns a content achievement to the UE.
  • the MEC Cache Server 1 returns the content requested by the UE to the UE.
  • the MEC Cache Server 1 may further store the content, so that the MEC Cache Server 1 can directly return the content from the MEC Cache Server 1 to the UE when receiving the request message of the content. .
  • the proxy server when the proxy device fails to obtain the identifier of the target cache device by using the content identifier, the proxy server requests the source server to obtain the requested content, and ensures the success rate of the content requested by the terminal.
  • the method may also be requested to obtain the content from the Source Server.
  • Step 8' the MEC Cache Server 1 sends the identity of the Source Server to the UE.
  • Step 9' the UE sends the content ID to the Source Server according to the identifier of the Source Server.
  • Step 10' the Source Server returns a content achievement to the UE, which carries the requested content.
  • the Source Serve returns the content requested by the UE to the UE.
  • the effect of the distributed cache is fully utilized, so that the content can be transferred between the storage devices.
  • the proxy device does not find the content requested by the terminal, the proxy device can obtain the content from the target cache device that stores the requested content. Requesting content, thus greatly improving the success rate of the content requested by the terminal, and enhancing the effect of storage.
  • FIG. 6 which is a flowchart of a content request method provided by an embodiment of the present application
  • the method shown in FIG. 6 corresponds to the architecture shown in FIG. 4
  • the process in FIG. 6 is similar to the process shown in FIG. 5 , and the difference is that : Steps 5 to 7, and steps 8 to 10.
  • Step 5 The MEC Cache Server 1 sends a Connection Relocation message to the UE.
  • the Connection Relocation sent by the MEC Cache Server 1 to the UE carries the identifier of the target cache device (MEC Cache Server 2), and the identifier of the target cache device is used to indicate the location of the content including the UE request (for example, MEC).
  • the MEC Cache Server 1 sends the identity of the target cache device to the UE.
  • the MEC Cache Server 1 may also record the correspondence between the MEC Cache Server 2 and the content of the request, so that when the content request is received again, the Connection Relocation message carrying the identifier of the target cache device may be directly sent to the UE.
  • Step 6 After establishing a connection with the MEC Cache Server 2, the UE sends a request message to the MEC Cache Server 2, where the request message carries the content ID.
  • the UE directly sends the content ID to the MEC Cache Server 2, requesting to acquire the content.
  • Step 7 The MEC Cache Server 2 sends a content achievement to the UE, and the process ends.
  • the MEC Cache Server 2 directly transmits the content requested by the UE to the UE.
  • the Cache Controller can send a special identifier to the MEC Cache Server 1, indicating that there is no content
  • the following steps 8 to 10 are performed.
  • Step 8 The MEC Cache Server 1 sends a Connection Relocation message to the UE.
  • Step 9 The UE establishes a connection with the Source Server and sends a request message to the Source Server.
  • the UE directly sends a request message to the Source Server requesting to acquire content.
  • Step 10 The Source Server returns a content achievement to the UE, and the process ends.
  • the second embodiment also provides an alternative method of the foregoing steps 8 to 10, specifically:
  • Step 8' the MEC Cache Server 1 establishes a connection with the Source Server and sends a request message to the Source Server.
  • the MEC Cache Server 1 sends a request message to the Source Server according to the address information of the Source Server, requesting to acquire the content requested by the UE.
  • the Source Server can be a server or a server group composed of multiple servers.
  • Step 9' the Source Server returns a content achievement to the MEC Cache Server 1.
  • the content achievement carries the content requested by the UE.
  • Step 10' MEC Cache Server 1 returns content achievement to the UE.
  • the MEC Cache Server 1 may further store the content, so that the MEC Cache Server 1 can directly return the content from the MEC Cache Server 1 to the UE when receiving the request message of the content. .
  • the MEC Cache Server 1 After the MEC Cache Server 1 obtains the identifier of the MEC Cache Server 2, the MEC Cache Server 1 requests the MEC Cache Server 2 to obtain the content, and sends the obtained content to the UE.
  • the MEC Cache Server 1 After the MEC Cache Server 1 obtains the identifier of the MEC Cache Server 2, the identifier of the MEC Cache Server 2 is carried in the connection redirection message and sent to the UE, and the UE requests the MEC Cache Server 2 to obtain the content.
  • the MEC Cache Server 1 when the Cache Controlle has no content, the MEC Cache Server 1 requests the source server to obtain the content, and sends the obtained content to the UE. In the second embodiment, when the Cache Controlle has no content, The MEC Cache Server 1 sends a connection redirection message to the UE, instructing the UE to directly request the content from the Source Server.
  • the second embodiment has the following beneficial effects: First, the terminal directly requests the server that stores the requested content (ie, the MEC Cache Server 2 or the Source Server) to obtain the content, which can reduce the pressure of the proxy device; second, the terminal can obtain the content. After the content, record the location of the server where the content is stored (for example, record as MEC Cache Server 2 or Source Server)
  • FIG. 7 is a schematic diagram of a distributed cache application architecture provided by an embodiment of the present disclosure, where GW Cache Server 1 is a proxy device, and GW Cache Server 2 is a target cache device.
  • FIG. 7 The difference between FIG. 7 and FIG. 4 is that the proxy device that the UE requests to acquire content is GW Cache Server 1, and the target cache device that stores the requested content is GW Cache Server 2.
  • FIG. 8 is a flowchart of a content request method provided by an embodiment of the present application, and the method shown in FIG. 8 corresponds to the architecture shown in FIG. 7.
  • the third embodiment shown in FIG. 8 is basically the same as the first embodiment shown in FIG. 5. The main difference is that the proxy device is replaced by the MEC Cache Server 1 as the GW Cache Server 1, and the MEC Cache Server 2 is replaced with GW Cache Server 2.
  • FIG. 7 is a schematic diagram of a distributed cache application architecture provided by an embodiment of the present disclosure, where GW Cache Server 1 is a proxy device, and GW Cache Server 2 is a target cache device.
  • FIG. 7 The difference between FIG. 7 and FIG. 4 is that the proxy device that the UE requests to acquire content is GW Cache Server 1, and the target cache device that stores the requested content is GW Cache Server 2.
  • FIG. 9 is a flowchart of a content request method provided by an embodiment of the present application, and the method shown in FIG. 9 corresponds to the architecture shown in FIG. 7.
  • the fourth embodiment shown in FIG. 9 is basically the same as the second embodiment shown in FIG. 6.
  • the main difference is that the proxy device is replaced by the MEC Cache Server 1 as the GW Cache Server 1, and the MEC Cache Server 2 is replaced with the GW. Cache Server 2.
  • FIG. 10 is a schematic diagram of a distributed cache application architecture provided by an embodiment of the present application, where the MEC Cache Server 1 is a proxy device, and the GW Cache Server 2 is a target cache device.
  • FIG. 10 The difference between FIG. 10 and FIG. 4 is that the proxy device that the UE requests to acquire content is the MEC Cache Server 1, and the target cache device that stores the requested content is the GW Cache Server 2.
  • FIG. 11 is a flowchart of a content request method according to an embodiment of the present application, and the method shown in FIG. 11 corresponds to the architecture shown in FIG. 10.
  • the fifth embodiment shown in FIG. 11 is basically the same as the first embodiment shown in FIG. 5.
  • the main difference is that the target cache device is replaced by the MEC Cache Server 2 as the GW Cache Server 2.
  • FIG. 10 is a schematic diagram of a distributed cache application architecture provided by an embodiment of the present application, where the MEC Cache Server 1 is a proxy device, and the GW Cache Server 2 is a target cache device.
  • FIG. 10 The difference between FIG. 10 and FIG. 4 is that the proxy device that the UE requests to acquire content is the MEC Cache Server 1, and the target cache device that stores the requested content is the GW Cache Server 2.
  • FIG. 12 is a flowchart of a content request method provided by an embodiment of the present application, and the method shown in FIG. 12 corresponds to the architecture shown in FIG.
  • the embodiment 6 shown in FIG. 12 is basically the same as the embodiment 2 shown in FIG. 6.
  • the main difference is that the target cache device is replaced by the MEC Cache Server 2 as the GW Cache Server 2.
  • the embodiment of the present application further provides a proxy device 1300.
  • the proxy device 1300 includes a transceiver unit 1301, a processing unit 1302, and a storage unit 1303.
  • the transceiver unit 1301 is configured to support a proxy device. 1300 and the foregoing embodiment 1, the third embodiment, the fifth embodiment, the terminal, the target cache device (for example Send and receive information between GW, GW Cache Server, MEC, MEC Cache Server, and source server.
  • the processing unit 1302 performs various communication related functions for the terminal, the target cache device, and the source server.
  • the processing unit 1302 of the proxy device is configured to perform the processes related to the MEC Cache Server 1 in FIG. 5 and FIG. 11 and/or other processes used in the techniques described in this application;
  • the processing unit 1302 of the proxy device is configured to perform the processing of the GW Cache Server 1 in FIG. 8 and/or other processes for the techniques described herein.
  • the storage unit 1303 is configured to store program codes and data of the proxy device.
  • the transceiver unit 1301 is configured to receive a request message sent by the terminal, where the request message carries a content identifier.
  • the processing unit 1302 is configured to: after receiving the request message sent by the terminal, obtain the identifier of the target cache device by using the content identifier, where the target cache device is a device that stores the requested content;
  • the transceiver unit 1301 is further configured to send the content identifier to the target cache device according to the identifier of the target cache device, request to acquire the requested content, and send the obtained request content to the terminal.
  • the processing unit 1302 is specifically configured to: query the content index information of the content by using the content identifier, and obtain the identifier of the target cache device; or
  • the query cache controller acquires the identifier of the target cache device.
  • the processing unit 1302 if the processing unit 1302 fails to obtain the identifier of the target cache device by using the content identifier, the processing unit 1302 is further configured to: request the source server to acquire the requested content;
  • the transceiver unit 1301 is further configured to: send the obtained request content to the terminal.
  • the processing unit 1302 is further configured to send the identifier of the source server to the terminal, so that the terminal is configured according to the source server.
  • the identifier requests the source server to acquire the requested content.
  • the proxy device is an MEC cache server or a GW cache server
  • the target cache device is an MEC cache server or a GW cache server.
  • the proxy device is integrated in the MEC or GW, and the target cache device is integrated in the MEC or GW.
  • the cache controller is any one of the following: a separate entity network element, an integrated MEC, an integrated GW, a control module integrated in the proxy device or the target cache device.
  • the embodiment of the present application further provides a proxy device 1400.
  • the proxy device 1400 includes a transceiver unit 1401, a processing unit 1402, and a storage unit 1403.
  • the transceiver unit 1401 is configured to support a proxy device.
  • the 1400 transmits and receives information between the terminal, the target cache device (for example, GW, GW Cache Server, MEC, MEC Cache Server) and the source server in the foregoing embodiment 2, the fourth embodiment, and the sixth embodiment.
  • the processing unit 1402 performs various communication related functions for the terminal, the target cache device, and the source server.
  • the processing unit 1402 of the proxy device is configured to perform the processes related to the MEC Cache Server 1 in FIG. 6 and FIG. 12 and/or other processes used in the techniques described in this application;
  • the processing unit 1402 of the proxy device is configured to perform the processing of the GW Cache Server 1 in FIG. 9 and/or other processes for the techniques described herein.
  • the storage unit 1403 is configured to store program codes and data of the proxy device.
  • the transceiver unit 1401 is configured to receive a request message sent by the terminal, where the request message carries a content identifier.
  • the processing unit 1402 is configured to: after receiving the request message sent by the terminal, acquire the identifier of the target cache device by using the content identifier, where the target cache device is a device that stores the requested content corresponding to the content identifier;
  • the transceiver unit 1401 is further configured to send the acquired identifier of the target cache device to the terminal.
  • the processing unit 1402 fails to obtain the identifier of the target cache device by using the content identifier, sending the identifier of the source server to the terminal, so that the terminal according to the identifier of the source server The source server requests to obtain the requested content.
  • processing unit 1402 is further configured to:
  • the transceiver unit 1401 is further configured to request the source server to acquire the requested content.
  • the transceiver unit 1401 is further configured to: send the obtained request content to the terminal.
  • the proxy device is an MEC cache server or a GW cache server
  • the target cache device is an MEC cache server or a GW cache server.
  • the proxy device is integrated in the MEC or GW, and the target cache device is integrated in the MEC or GW.
  • the embodiment of the present application further provides an apparatus 1500.
  • the apparatus 1500 includes: a processor 1501, a memory 1502, and a transceiver 1503.
  • the processor 1501, the memory 1502, and The transceivers 1503 are all connected by a bus 1504;
  • the memory 1502 is configured to store a computer execution instruction
  • the processor 1501 is configured to execute a computer execution instruction stored by the memory 1502.
  • the processor 1501 executes the computer-executed instructions stored in the memory 1502, such that the device 1500 performs the steps performed by the proxy device in the content request method provided by the embodiment of the present application, or The proxy device is caused to deploy the functional unit corresponding to the step.
  • the processor 1501 may include different types of processors 1501, or include the same type of processor 1501; the processor 1501 may be any one of the following: a central processing unit (CPU), an ARM processor, and a field. A device with computational processing capability, such as a Field Programmable Gate Array (FPGA) or a dedicated processor. In an optional implementation manner, the processor 1501 may also be integrated into a many-core processor.
  • processors 1501 may be any one of the following: a central processing unit (CPU), an ARM processor, and a field.
  • a device with computational processing capability such as a Field Programmable Gate Array (FPGA) or a dedicated processor.
  • FPGA Field Programmable Gate Array
  • the processor 1501 may also be integrated into a many-core processor.
  • the memory 1502 may be any one or any combination of the following: a random access memory (RAM), a read only memory (ROM), a non-volatile memory (non-volatile memory). , referred to as NVM), Solid State Drives (SSD), mechanical hard disks, disks, disk arrays and other storage media.
  • RAM random access memory
  • ROM read only memory
  • NVM non-volatile memory
  • SSD Solid State Drives
  • the transceiver 1503 is configured to perform data interaction between the device 1500 and other devices.
  • the proxy device may perform the method according to any one of the foregoing Embodiments 1 to 6 to implement a content request method.
  • the proxy device interacts with the terminal through the transceiver 1503.
  • the transceiver 1503 may be any one or any combination of the following: a network interface (such as an Ethernet interface), a wireless network card, and the like having a network access function.
  • the bus 1504 can include an address bus, a data bus, a control bus, etc., for ease of representation, Figure 9 shows the bus with a thick line.
  • the bus 1504 may be any one or any combination of the following: an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, and an extended industry standard structure ( Extended Industry Standard Architecture (EISA) bus and other devices for wired data transmission.
  • ISA Industry Standard Architecture
  • PCI Peripheral Component Interconnect
  • EISA Extended Industry Standard Architecture
  • the embodiment of the present application provides a computer readable storage medium.
  • the computer readable storage medium stores a computer execution instruction.
  • the processor of the proxy device executes the computer to execute the instruction, so that the proxy device performs the embodiment of the present application.
  • Embodiments of the present application provide a computer program product comprising computer executed instructions stored in a computer readable storage medium.
  • the processor of the proxy device can read the computer execution instructions from the computer readable storage medium; the processor executes the computer to execute the instructions, so that the proxy device performs the steps performed by the proxy device in the content request method provided by the embodiment of the present application, or The proxy device is caused to deploy the functional unit corresponding to the step.
  • the above embodiments it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof.
  • software it may be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions When the computer program instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present invention are generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transfer to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, digital subscriber line (DSL), or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer readable storage medium can be any available media that can be stored by a computer or a data storage device such as a server, data center, or the like that includes a plurality of available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)).
  • embodiments of the present application can be provided as a method, system, or computer program product.
  • the present application can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment in combination of software and hardware.
  • the application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Abstract

本申请实施例涉及通信技术领域，尤其涉及一种内容请求方法及代理设备，用以提高终端内容请求的成功率，包括：代理设备接收终端发送的请求消息，通过查询缓存内容索引信息获取目标缓存设备的标识，所述目标缓存设备为存储所述请求内容的设备，代理设备根据目标缓存设备的标识，获取到目标缓存设备中存储的请求内容并发送至终端，从而，本申请充分利用分布式缓存的效果，使得内容能够在缓存设备之间传输，当代理设备自身没有查找到终端请求的内容时，可从存储有该请求内容的目标缓存设备中获取请求内容，因而能够极大提高终端内容请求的成功率，增强了缓存的效果。

Description

一种内容请求方法及代理设备 技术领域
本申请实施例涉及通信技术领域，尤其涉及一种内容请求方法及代理设备。
背景技术
如图1所示，为当前无线演进网络架构图，无线演进网络的核心网主要包含移动管理网元(Mobility Management Entity，MME)、服务网关(Serving Gateway，S-GW)、分组数据网络网关(Packet Data Network Gateway，P-GW)三个逻辑功能体，其中的MME负责与用户设备之间的网络附属存储(Network Attached Storage，NAS)信令和NAS信令加密，为用户设备分配临时身份标识，选择S-GW和P-GW/GGSN(网关GPRS支撑节点(Gateway GPRS Support Node，GGSN)；通用分组无线服务(General Packet Radio Service，GPRS))等核心网网元，提供漫游、跟踪、安全等功能，它对应于当前通用移动通信系统(Universal Mobile Telecommunications System，UMTS)系统内部服务GPRS支持节点(Serving GPRS Support Node，SGSN)的控制平面部分。S-GW是本地演进型Node B(Evolved Node B，eNodeB)之间切换的移动性锚点，并提供合法监听相关功能；P-GW是用户数据传输的锚点，则负责用户地址分配，策略控制和计费规则的执行和以及合法监听相关功能。服务器归属签约用户服务器(Home Subscriber Server，HSS)用于存储用户的签约信息。策略与计费规则功能单元(Policy and Charging Rules Function，PCRF)提供策略和计费控制规则。与本申请相关的网元为P-GW，其他网元仅作为介绍。
参照图1，现有技术中，移动网络中的缓存服务器(cache server)一般部署在GGSN的Gi接口后面或部署在PGW的SGi接口后面，为本网关内部的用户提供缓存服务。也就是说用户可以直接从cache server中直接获取数据，而不需要到数据的源服务器中获取内容。
上述方法存在的主要问题是：cache server在GGSN或PGW后面，离用户终端的距离比较远，导致数据传输时延较大。
为解决上述问题，现有技术中提出另一种缓存方案，如图2所示，为移动边缘计算(Mobile Edge Computing，MEC)缓存方案，其中，移动网络引入了MEC网元，其位置处于基站与GW之间，离用户的位置更近。在MEC上部署旁路的Cache Server(也就是在MEC上连接一个MEC Cache Server)，用户可以直接从MEC Cache Server中直接获取内容，这样可以进一步减短数据传输时延。
该方法存在的主要问题是：由于MEC的位置较低，因此MEC的数量就会很多，从而MEC的设备成本就不能太高，相应的MEC Cache Server设备成本也不能太高，所以每个MEC Cache Server存储资源就比较有限，无法缓存太多内容，这样用户的很多内容请求就无法成功(因为没有内容)，因而导致缓存效果大大降低了。
综上所述，现有技术存在终端内容请求成功率较低的技术问题。
发明内容
本申请实施例提供一种内容请求方法及代理设备，用以提高终端内容请求的成功率。
第一方面，本申请实施例提供一种内容请求方法，包括：
代理设备接收终端发送的请求消息，所述请求消息携带内容标识；
所述代理设备在接收到所述终端发送的请求消息后，通过所述内容标识获取目标缓存设备的标识，所述目标缓存设备为存储所述内容标识对应的请求内容的设备；
所述代理设备根据所述目标缓存设备的标识，向所述目标缓存设备发送所述内容标识，请求获取所述请求内容；
所述代理设备将获取的所述请求内容发送至所述终端。
上述申请实施例中，代理设备接收终端发送的请求消息，请求消息携带内容标识，通过内容标识获取目标缓存设备的标识，所述目标缓存设备为存储请求内容的设备，代理设备根据目标缓存设备的标识，获取到目标缓存设备中存储的请求内容并发送至终端，从而，本申请充分利用分布式缓存的效果，使得内容能够在缓存设备之间传输，当代理设备自身没有查找到终端请求的内容时，可从存储有该请求内容的目标缓存设备中获取请求内容，因而能够极大提高终端内容请求的成功率，增强了缓存的效果。
结合第一方面，在第一方面的第一种可能的实现方式中，所述代理设备通过所述内容标识获取目标缓存设备的标识，包括：
所述代理设备通过所述内容标识，查询自身的内容索引信息，获取所述目标缓存设备的标识；或者
所述代理设备向缓存控制器发送所述内容标识，并接收所述缓存控制器根据所述内容标识获得的所述目标缓存设备的标识。
上述申请实施例，代理设备可以是自身存储有内容索引消息，因而可通过自身存储的内容索引消息获取目标缓存设备的标识；或者是在系统中专门设置一个用于管理缓存设备的缓存控制器，从而代理设备可以向缓存控制器发送请求消息，由缓存控制器向代理设备返回目标缓存设备的标识。其中，第一种方式可减少系统硬件设备开销；第二种方式采用集中控制，可减少代理设备压力。
结合第一方面，在第一方面的第二种可能的实现方式中，所述方法还包括：
所述代理设备若通过所述内容标识获取目标缓存设备的标识失败，则向所述源服务器请求获取所述请求内容；
所述代理设备将获取的所述请求内容发送至所述终端。
上述申请实施例，当代理设备通过查询内容索引信息获取目标缓存设备的标识失败时，则向源服务器请求获取请求内容，保证了终端请求内容的成功率。
结合第一方面，在第一方面的第三种可能的实现方式中，所述代理设备若通过所述内容标识获取目标缓存设备的标识失败，则将所述源服务器的标识发送至所述终端，使所述终端根据所述源服务器的标识向所述源服务器请求获取所述请求内容。
在一种可能的设计中，所述代理设备向所述目标缓存设备请求获取所述请求内容之后，还包括：所述代理设备缓存所述请求内容。
上述申请实施例，代理设备向目标缓存设备获取到请求内容之后，还缓存请求内容，从而当终端下次向代理设备可成功请求到同样的请求内容，有利于提高成功率。
结合第一方面或第一方面的第一种可能的实现方式至第三种可能的实现方式，在第一方面的第四种可能的实现方式中，所述代理设备为MEC缓存服务器或GW缓存服务器，所述目标缓存设备为MEC缓存服务器或GW缓存服务器。
结合第一方面或第一方面的第一种可能的实现方式至第三种可能的实现方式，在第一方面的第五种可能的实现方式中，所述代理设备集成于MEC或GW，所述目标缓存设备集成于MEC或GW。
结合第一方面的第一种可能的实现方式，在第一方面的第六种可能的实现方式中，所述缓存控制器为下列任一种：
独立实体网元、集成于MEC、集成于GW、集成于所述代理设备或所述目标缓存设备的控制模块。
第二方面，本申请实施例提供一种代理设备，可以执行实现上述第一方面提供的任意一种内容请求方法。
在一种可能的设计中，该代理设备包括多个功能模块，用于实现上述第一方面提供的任意一种内容请求方法，使得代理设备接收终端发送的请求消息，请求消息携带内容标识，通过内容标识获取目标缓存设备的标识，所述目标缓存设备为存储请求内容的设备，代理设备根据目标缓存设备的标识，获取到目标缓存设备中存储的请求内容并发送至终端，从而，本申请充分利用分布式缓存的效果，使得内容能够在缓存设备之间传输，当代理设备自身没有查找到终端请求的内容时，可从存储有该请求内容的目标缓存设备中获取请求内容，因而能够极大提高终端内容请求的成功率，增强了缓存的效果。
在一种可能的设计中，代理设备的结构中包括处理器和收发器，所述处理器被配置为支持代理设备执行上述第一方面的内容请求方法中相应的功能。所述收发器用于支持代理设备与终端之间的通信，向终端发送上述内容请求方法中所涉及的信息或者指令。代理设备中还可以包括存储器，所述存储器用于与处理器耦合，其保存代理设备必要的程序指令和数据。
第三方面，本申请实施例提供一种内容请求方法，包括：
代理设备接收终端发送的请求消息，所述请求消息携带内容标识；
所述代理设备在接收到所述终端发送的请求消息后，通过所述内容标识获取目标缓存设备的标识，所述目标缓存设备为存储所述内容标识对应的请求内容的设备；
所述代理设备将所述目标缓存设备的标识发送至所述终端。
上述申请实施例中，代理设备接收终端发送的请求消息，通过内容标识获取目标缓存设备的标识，所述目标缓存设备为存储所述请求内容的设备，代理设备将目标缓存设备的标识发送至终端，使终端向该目标缓存设备请求需要的请求内容。从而，本申请充分利用分布式缓存的效果，能够极大提高终端内容请求的成功率，增强了缓存的效果。
结合第三方面，在第三方面的第一种可能的实现方式中，所述方法还包括：
所述代理设备若通过查询所述内容标识获取目标缓存设备的标识失败，则将所述源服务器的标识发送至所述终端，使所述终端根据所述源服务器的标识向所述源服务器请求获取所述请求内容。
上述申请实施例，当代理设备通过查询内容标识获取目标缓存设备的标识失败时，则通知终端向源服务器请求获取请求内容，保证了终端请求内容的成功率。
结合第三方面，在第三方面的第二种可能的实现方式中，所述代理设备若通过所述内容标识获取目标缓存设备的标识失败，则向所述源服务器请求获取所述请求内容；
所述代理设备将获取的所述请求内容发送至所述终端。
结合第三方面或第三方面的第一种可能的实现方式或第三方面的第二种可能的实现 方式，在第三方面的第三种可能的实现方式中，所述代理设备为MEC缓存服务器或GW缓存服务器，所述目标缓存设备为MEC缓存服务器或GW缓存服务器。
结合第三方面或第三方面的第一种可能的实现方式或第三方面的第二种可能的实现方式，在第三方面的第四种可能的实现方式中，所述代理设备集成于MEC或GW，所述目标缓存设备集成于MEC或GW。
结合第三方面，在第三方面的第五种可能的实现方式中，所述代理设备通过内容标识获取目标缓存设备的标识，包括：
所述代理设备通过所述内容标识，查询自身的内容索引信息，获取所述目标缓存设备的标识；或者
所述代理设备向缓存控制器发送所述内容标识，并接收所述缓存控制器根据所述内容标识获得的所述目标缓存设备的标识。
在一种可能的设计中，所述缓存控制器为下列任一种：独立实体网元、集成于MEC、集成于GW、集成于所述代理设备或所述目标缓存设备。
第四方面，本申请实施例提供一种代理设备，可以执行实现上述第三方面提供的任意一种内容请求方法。
在一种可能的设计中，该代理设备包括多个功能模块，用于实现上述第三方面提供的任意一种内容请求方法，使得代理设备接收终端发送的请求消息，通过内容标识获取目标缓存设备的标识，所述目标缓存设备为存储所述请求内容的设备，代理设备将目标缓存设备的标识发送至终端，使终端向该目标缓存设备请求需要的请求内容。从而，本申请充分利用分布式缓存的效果，能够极大提高终端内容请求的成功率，增强了缓存的效果。
在一种可能的设计中，代理设备的结构中包括处理器和收发器，所述处理器被配置为支持代理设备执行上述第三方面的内容请求方法中相应的功能。所述收发器用于支持代理设备与终端之间的通信，向终端发送上述内容请求方法中所涉及的信息或者指令。代理设备中还可以包括存储器，所述存储器用于与处理器耦合，其保存代理设备必要的程序指令和数据。
第五方面，本申请实施例提供了一种计算机存储介质，用于储存为上述第二方面提供的代理设备所用的计算机软件指令，其包含用于执行上述第一方面所设计的程序。
第六方面，本申请实施例提供了一种计算机存储介质，用于储存为上述第四方面提供的代理设备所用的计算机软件指令，其包含用于执行上述第三方面所设计的程序。
第七方面，本申请还提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
附图说明
为了更清楚地说明本申请实施例中的技术方案，下面将对实施例描述中所需要使用的附图作简要介绍。
图1为当前无线演进网络架构图；
图2为现有技术的MEC缓存方案；
图3为本申请实施例提供的分布式缓存应用架构图；
图4为本申请实施例一和实施例二提供的分布式缓存应用架构图；
图5为本申请实施例一提供的内容请求方法流程图；
图6为本申请实施例二提供的内容请求方法流程图；
图7为本申请实施例三和实施例四提供的分布式缓存应用架构图；
图8为本申请实施例三提供的内容请求方法流程图；
图9为本申请实施例四提供的内容请求方法流程图；
图10为本申请实施例五和实施例六提供的分布式缓存应用架构图；
图11为本申请实施例五提供的内容请求方法流程图；
图12为本申请实施例六提供的内容请求方法流程图；
图13为本申请实施例提供的代理设备；
图14为本申请实施例提供代理设备；
图15为本申请实施例提供的设备。
具体实施方式
为了使本申请的目的、技术方案和优点更加清楚，下面将结合附图及实施例对本申请作进一步地详细描述。
本申请涉及的网元主要有：
终端：在本申请中，用于向代理设备或源服务器请求获取内容并接收返回的内容；
代理设备：用于接收终端的请求，为终端提供请求的内容或请求的内容所在的位置，本申请实施例中，代理设备可以是MEC缓存服务器或GW缓存服务器；或者代理设备还可以是集成于MEC或GW。
目标缓存设备：存储有终端所请求的内容，用于向代理设备返回终端请求的内容，或直接向终端返回终端所请求的内容，本申请实施例中，目标缓存设备可以是MEC缓存服务器或GW缓存服务器；或者目标缓存设备还可以是集成于MEC或GW，其中，GW可以PGW，也可以是S-GW，分布式网关(Distributed Gate Way，D-GW)，还可以是5G网络的网关，具体不做限制。
缓存控制器(Cache Controller)：其中有内容存储的位置信息，在本申请中提供内容存储的位置信息。需要说明的是，该缓存控制器可能是一个单独的实体网元，也可以是集成于MEC，或者集成于GW，或者集成于Cache Server(即本申请实施例中的代理设备、目标缓存设备)。
参照图3，为本申请实施例提供的分布式缓存应用架构图，终端向基站发送请求消息，基站向MEC 1转发请求消息，MEC 1转发请求消息至MEC Cache Server 1，该图中，MEC Cache Server 1即为代理设备(当然，如果MEC Cache Server 1是集成于MEC 1中，则MEC1则为代理设备)，当MEC Cache Server 1中存储有终端所请求的内容，则将终端所请求的内容返回给终端；当MEC Cache Server 1未存储终端所请求的内容，则向缓存控制器(图中未示出，缓存控制器可以是集成于MEC 1，或集成于MEC Cache Server 1，或集成于MEC 2，或集成于MEC Cache Server 2，或集成于GW 1，或集成于GW Cache Server 1，或集成于GW 2，或集成于GW Cache Server 2，或是一个单独的实体网元)，缓存控制器向MEC Cache Server 1返回终端所请求的内容所在的位置(即返回目标缓存设备的标识，目标缓存设备中存储有终端所请求的内容，假设目标缓存设备为MEC Cache Server 2)，然后MEC Cache Server 1向MEC Cache Server 2请求获取终端请求的内容，并发送给终端。
当然，代理设备和目标缓存设备也可以均是GW Cache Server；或者代理设备是MEC  Cache Server，目标缓存设备是GW Cache Server；或者代理设备是GW Cache Server，目标缓存设备是MEC Cache Server。
上述应用架构是以4G网络为例，但不限于4G网络，任何移动网络架构均适用本申请，如是通用分组无线服务(General Packet Radio Service，GPRS)网络，4.5G网络，5G网络等。
上述应用架构中的所有缓存节点(如图中所示的MEC Cache Server 1、MEC Cache Server 2、GW Cache Server 1、GW Cache Server 2)之间可以相互传输数据，具体地，可以是直接连接传输数据，还可以是间接连接传输数据。
下面根据代理设备、目标缓存设备的类型，分多个实施例进行具体说明。
实施例一
该实施例中，代理设备为MEC缓存服务器、目标缓存设备为MEC缓存服务器。
参照图4，为本申请实施例提供的分布式缓存应用架构图，其中，MEC Cache Server 1为代理设备，MEC Cache Server 2为目标缓存设备。
参照图5，为本申请实施例提供的内容请求方法流程图，图5所示的方法对应于图4所示的架构，包括以下步骤：
步骤1、UE(终端)与MEC Cache Server 1(代理设备)建立连接后，UE向MEC Cache Server 1发送request message(请求消息)。
其中，request message可以携带内容标识(ID)，用于指示要请求的内容。例如，具体是内容名称(content name)，或者统一资源标识符(Uniform Resource Identifier，URI)等等。即，步骤1中终端向Cache Controller发送内容ID。
可选的，request message(请求消息)具体可以是content request message(内容请求消息)。
可选的，MEC Cache Server 1(代理设备)在接收到UE(终端)发送的数据包后(例如数据包携带Source server的IP地址)，可以记录Source Server的地址信息。
步骤2、当MEC Cache Server 1拥有UE所请求的内容时，则向UE返回content achivement消息，将UE请求的内容发送给UE，流程结束。
若上述步骤2中，MEC Cache Server 1没有UE所请求的内容时，则执行下述步骤3～步骤7。
步骤3、MEC Cache Server 1向Cache Controller(缓存控制器)发送cache location request(缓存位置请求)消息。其中，cache location request可以携带有该内容ID，用于指示要请求的内容。
即，MEC Cache Server 1向Cache Controller发送内容ID。
步骤4、Cache Controller向MEC Cache Server 1返回cache location response(缓存位置响应)消息，其中携带有目标缓存设备(MEC Cache Server 2)的标识。例如可以是位置标识(Location ID)，这里的Location ID用于表示内容所处的位置，即在哪台缓存服务器中包含该内容。具体还可以是Server ID(服务器ID)，也可以是Server address(服务器地址)等标识内容所处的位置，本申请不做限制(标识的不同也可以进行相互转化)。当所辖移动网络区域内(即Cache Controller所覆盖的区域)没有该内容的缓存时，可以通过一个特殊标识来指名，例如可以是*，#，或者null等形式，也可以不携带任何标识，本申 请不限制具体标识的格式。
即，Cache Controller向MEC Cache Server 1返回目标缓存设备的标识。
在该步骤4中，具体地，Cache Controller中存储有内容索引信息，该索引信息指示每种请求内容所在的存储位置，例如可以是通过数据库表格的形式存储，参照表1，给出一种实现方式。
内容ID 存储位置ID
内容ID 1 MEC Cache Server 1、MEC Cache Server 3
内容ID 2 MEC Cache Server 1、MEC Cache Server 5
…… ……
表1
在此，不同内容ID形式之间是可以相互转化的，例如收到的是URI，而数据库中记录的是content name与存储位置ID之间的对应关系，则cache controller可以首先将接收到的URI转换为相对应的content name，然后根据转换后得到的content name去查找数据库，得到对该content name相对应的存储位置ID。即本申请中，不同形式的内容ID之间的转化不影响本申请的实现。
此外，本申请实施例还给出上述步骤3和步骤4的一种替代实现方案，即本申请方案中代理设备中自身存储有内容索引信息，在此种情形下，MEC Cache Server 1可通过自身的内容索引信息，获取MEC Cache Server 2的标识。
该实现方式，取消了Cache Controller网元，因而可减少系统硬件设备开销。而上述步骤3和步骤4的实现方式中，设置有Cache Controller网元，由于采用集中控制的方式，因而可减少代理设备压力。
步骤5、MEC Cache Server 1与MEC Cache Server 2建立连接，并向MEC Cache Server2发送request message，其中，request message中携带有内容ID。
即，MEC Cache Server 1向MEC Cache Server 2发送内容ID，用于请求获取的内容。
该步骤中，MEC Cache Server 1可以是直接向MEC Cache Server 2发送该内容ID，也可以是通过MEC 1向MEC Cache Server 2转发该内容ID(如图中所示)
步骤6、MEC Cache Server 2向MEC Cache Server 1发送content achievement。
即，MEC Cache Server 2将UE请求的内容发送给MEC Cache Server 1。这里，MEC Cache Server 2可以是直接向MEC Cache Server 1发送UE请求的内容，也可以是通过MEC1转发UE请求的内容。
步骤7、MEC Cache Server 1向UE发送content achievement，流程结束。
即，MEC Cache Server 1将UE请求的内容发送给UE。
当然，若上述步骤4中，Cache Controlle无法提供所述内容(例如Cache Controlle发送一个特殊标识给MEC Cache Server 1)，则执行下述步骤8～步骤10。
步骤8、MEC Cache Server 1与Source Server(源服务器)建立连接，并向Source Server发送request message。
即，MEC Cache Server 1向Source Server发送请求消息(内容ID)，请求获取UE请求获取的内容。具体的，MEC Cache Server 1根据步骤1获得Source Server的地址信息， 其中，Source Server可以是一台服务器，也可以是由多台服务器构成的服务器群。
步骤9、Source Server向MEC Cache Server 1返回content achievement。
其中，content achievement中携带有UE所请求的内容。
即，Source Serve向MEC Cache Server 1返回UE所请求的内容。
步骤10、MEC Cache Server 1向UE返回content achievement。
即，MEC Cache Server 1向UE返回UE所请求的内容。
在该步骤的之前或之后，还可以包括：MEC Cache Server 1存储该内容，如此，MEC Cache Server 1下次再接收到该内容的请求消息时，就能直接从MEC Cache Server 1返回内容给UE。
上述步骤8～步骤10，当代理设备通过内容标识获取目标缓存设备的标识失败时，则向源服务器请求获取请求内容，保证了终端请求内容的成功率。
作为上述步骤8～步骤10的一种替代方法，本申请，当Cache Controlle无法提供UE请求的内容时，还可以通过下述方法实现向Source Server请求获取内容。
步骤8’、MEC Cache Server 1将Source Server的标识发送至UE。
步骤9’、UE根据Source Server的标识向Source Server发送内容ID。
步骤10’、Source Server向UE返回content achievement，其中携带有请求的内容。
即，Source Serve向UE返回UE所请求的内容。
上述申请实施例一，充分利用分布式缓存的效果，使得内容能够在存储设备之间传输，当代理设备自身没有查找到终端请求的内容时，可从存储有该请求内容的目标缓存设备中获取请求内容，因而能够极大提高终端请求内容的成功率，增强了存储的效果。
实施例二
如图6所示，为本申请实施例提供的内容请求方法流程图，图6所示的方法对应于图4所示的架构，图6流程与图5所示的流程类似，区别之处在于：步骤5～步骤7，以及步骤8～步骤10。
步骤5、MEC Cache Server 1向UE发送Connection Relocation(连接重定向)消息。
该步骤中，MEC Cache Server 1向UE发送的Connection Relocation中携带有目标缓存设备(MEC Cache Server 2)的标识，该目标缓存设备的标识用以指示包含有UE请求的内容所在位置(例如为MEC Cache Server 2的位置标识)。
即，MEC Cache Server 1向UE发送目标缓存设备的标识。
并且，MEC Cache Server 1还可以将MEC Cache Server 2与该请求的内容的对应关系记录下来，以便再次接收到该内容请求时，可直接向UE发送携带有目标缓存设备的标识的Connection Relocation消息。
步骤6、UE与MEC Cache Server 2建立连接后，向MEC Cache Server 2发送request message，request message中携带有内容ID。
即由UE直接向MEC Cache Server 2发送内容ID，请求获取内容。
步骤7、MEC Cache Server 2向UE发送content achievement，流程结束。
即，MEC Cache Server 2将UE请求的内容直接发送给UE。
当然，若图6所示的步骤4中，Cache Controlle没有内容(例如Cache Controller可以发送一个特殊标识给MEC Cache Server 1，表示没有内容)，则执行下述步骤8～步骤10。
步骤8、MEC Cache Server 1向UE发送Connection Relocation(连接重定向)消息。
步骤9、UE与Source Server建立连接，并向Source Server发送request message。
即，UE直接向Source Server发送请求消息，请求获取内容。
步骤10、Source Server向UE返回content achievement，流程结束。
当然，与实施例一相同的是，实施例二也提供上述步骤8～步骤10的一种替代方法，具体为：
步骤8’、MEC Cache Server 1与Source Server建立连接，并向Source Server发送request message。
即，MEC Cache Server 1根据Source Server的地址信息向Source Server发送请求消息，请求获取UE请求获取的内容。其中，Source Server可以是一台服务器，也可以是由多台服务器构成的服务器群。
步骤9’、Source Server向MEC Cache Server 1返回content achievement。
其中，content achievement中携带有UE所请求的内容。
步骤10’、MEC Cache Server 1向UE返回content achievement。
在该步骤的之前或之后，还可以包括：MEC Cache Server 1存储该内容，如此，MEC Cache Server 1下次再接收到该内容的请求消息时，就能直接从MEC Cache Server 1返回内容给UE。
上述申请实施例二，与上述申请实施例一的主要区别在于：
第一，实施例一中，当MEC Cache Server 1获取到MEC Cache Server 2的标识后，MEC Cache Server 1向MEC Cache Server 2请求获取内容，并将获取的内容发送给UE；而实施例二中，当MEC Cache Server 1获取到MEC Cache Server 2的标识后，将MEC Cache Server2的标识携带于连接重定向消息中发送给UE，由UE向MEC Cache Server 2请求获取内容。
第二，实施例一中，当Cache Controlle没有内容时，由MEC Cache Server 1向Source Server请求获取内容，并将获取到的内容发送给UE；实施例二中，当Cache Controlle没有内容时，由MEC Cache Server 1向UE发送连接重定向消息，指示UE直接向Source Server请求获取内容。
该实施例二有益效果如下：第一，由终端直接向存储有请求内容的服务器(即MEC Cache Server 2或Source Server)请求获取内容，可减轻代理设备的压力；第二，终端可在获取到内容后，记录存储有该内容的服务器的位置(例如记录为MEC Cache Server 2或Source Server)
实施例三
参照图7，为本申请实施例提供的分布式缓存应用架构图，其中，GW Cache Server 1为代理设备，GW Cache Server 2为目标缓存设备。
图7与图4的区别在于：UE请求获取内容的代理设备是GW Cache Server 1，而存储有请求内容的目标缓存设备是GW Cache Server 2。
参照图8，为本申请实施例提供的内容请求方法流程图，图8所示的方法对应于图7所示的架构。
图8所示的实施例三与图5所示的实施例一基本相同，主要区别是将其中的代理设备由MEC Cache Server 1替换为GW Cache Server 1，将其中的MEC Cache Server 2替换为 GW Cache Server 2。
具体可参照上述说明，此处不再赘述。
实施例四
参照图7，为本申请实施例提供的分布式缓存应用架构图，其中，GW Cache Server 1为代理设备，GW Cache Server 2为目标缓存设备。
图7与图4的区别在于：UE请求获取内容的代理设备是GW Cache Server 1，而存储有请求内容的目标缓存设备是GW Cache Server 2。
参照图9，为本申请实施例提供的内容请求方法流程图，图9所示的方法对应于图7所示的架构。
图9所示的实施例四与图6所示的实施例二基本相同，主要区别是将其中的代理设备由MEC Cache Server 1替换为GW Cache Server 1，将其中的MEC Cache Server 2替换为GW Cache Server 2。
具体可参照上述说明，此处不再赘述。
实施例五
参照图10，为本申请实施例提供的分布式缓存应用架构图，其中，MEC Cache Server1为代理设备，GW Cache Server 2为目标缓存设备。
图10与图4的区别在于：UE请求获取内容的代理设备是MEC Cache Server 1，而存储有请求内容的目标缓存设备是GW Cache Server 2。
参照图11，为本申请实施例提供的内容请求方法流程图，图11所示的方法对应于图10所示的架构。
图11所示的实施例五与图5所示的实施例一基本相同，主要区别是将其中的目标缓存设备由MEC Cache Server 2替换为GW Cache Server 2。
具体可参照上述说明，此处不再赘述。
实施例六
参照图10，为本申请实施例提供的分布式缓存应用架构图，其中，MEC Cache Server1为代理设备，GW Cache Server 2为目标缓存设备。
图10与图4的区别在于：UE请求获取内容的代理设备是MEC Cache Server 1，而存储有请求内容的目标缓存设备是GW Cache Server 2。
参照图12，为本申请实施例提供的内容请求方法流程图，图12所示的方法对应于图10所示的架构。
图12所示的实施例六与图6所示的实施例二基本相同，主要区别是将其中的目标缓存设备由MEC Cache Server 2替换为GW Cache Server 2。
具体可参照上述说明，此处不再赘述。
基于相同的发明构思，本申请实施例还提供一种代理设备1300，如图13所示，该代理设备1300包括收发单元1301、处理单元1302和存储单元1303，该收发单元1301用于支持代理设备1300与上述实施例一、实施例三、实施例五中终端、目标缓存设备(例如 为GW、GW Cache Server、MEC、MEC Cache Server)及源服务器之间收发信息。该处理单元1302执行各种用于与终端、目标缓存设备及源服务器的通信相关功能。
以代理设备为MEC Cache Server 1为例，则代理设备的处理单元1302用于执行图5、图11中涉及MEC Cache Server 1的处理过程和/或用于本申请所描述的技术的其他过程；以代理设备为GW Cache Server 1为例，则代理设备的处理单元1302用于执行图8中涉及GW Cache Server 1的处理过程和/或用于本申请所描述的技术的其他过程。
存储单元1303用于存储代理设备的程序代码和数据。
收发单元1301，用于接收终端发送的请求消息，所述请求消息携带内容标识；
处理单元1302，用于在接收到所述终端发送的请求消息后，通过所述内容标识获取目标缓存设备的标识，所述目标缓存设备为存储所述请求内容的设备；
所述收发单元1301，还用于根据所述目标缓存设备的标识，向所述目标缓存设备发送所述内容标识，请求获取所述请求内容，以及将获取的请求内容发送至所述终端。
可选地，所述处理单元1302，具体用于：通过所述内容标识，查询自身的内容索引信息，获取所述目标缓存设备的标识；或者
通过所述内容标识，查询缓存控制器获取所述目标缓存设备的标识。
可选地，若所述处理单元1302通过所述内容标识获取目标缓存设备的标识失败，则所述处理单元1302，还用于：向所述源服务器请求获取所述请求内容；
所述收发单元1301还用于：将获取的所述请求内容发送至所述终端。
可选地，若通过所述内容标识获取目标缓存设备的标识失败，则所述处理单元1302还用于将所述源服务器的标识发送至所述终端，使所述终端根据所述源服务器的标识向所述源服务器请求获取所述请求内容。
可选地，所述代理设备为MEC缓存服务器或GW缓存服务器，所述目标缓存设备为MEC缓存服务器或GW缓存服务器。
可选地，所述代理设备集成于MEC或GW，所述目标缓存设备集成于MEC或GW。
可选地，所述缓存控制器为下列任一种：独立实体网元、集成于MEC、集成于GW、集成于所述代理设备或所述目标缓存设备的控制模块。
基于相同的申请构思，本申请实施例还提供一种代理设备1400，如图14所示，该代理设备1400包括收发单元1401、处理单元1402和存储单元1403，该收发单元1401用于支持代理设备1400与上述实施例二、实施例四、实施例六中终端、目标缓存设备(例如为GW、GW Cache Server、MEC、MEC Cache Server)及源服务器之间收发信息。该处理单元1402执行各种用于与终端、目标缓存设备及源服务器的通信相关功能。
以代理设备为MEC Cache Server 1为例，则代理设备的处理单元1402用于执行图6、图12中涉及MEC Cache Server 1的处理过程和/或用于本申请所描述的技术的其他过程；以代理设备为GW Cache Server 1为例，则代理设备的处理单元1402用于执行图9中涉及GW Cache Server 1的处理过程和/或用于本申请所描述的技术的其他过程。
存储单元1403用于存储代理设备的程序代码和数据。
收发单元1401，用于接收终端发送的请求消息，所述请求消息携带内容标识；
处理单元1402，用于在接收到所述终端发送的请求消息后，通过所述内容标识获取所述目标缓存设备的标识，所述目标缓存设备为存储所述内容标识对应的请求内容的设备；
所述收发单元1401，还用于将获取的所述目标缓存设备的标识发送至所述终端。
可选地，若所述处理单元1402通过所述内容标识获取目标缓存设备的标识失败，则将所述源服务器的标识发送至所述终端，使所述终端根据所述源服务器的标识向所述源服务器请求获取所述请求内容。
可选地，所述处理单元1402还用于：
若通过所述内容标识获取目标缓存设备的标识失败，则所述收发单元1401还用于向所述源服务器请求获取所述请求内容；
所述收发单元1401，还用于：将获取的所述请求内容发送至所述终端。
可选地，所述代理设备为MEC缓存服务器或GW缓存服务器，所述目标缓存设备为MEC缓存服务器或GW缓存服务器。
可选地，所述代理设备集成于MEC或GW，所述目标缓存设备集成于MEC或GW。
基于相同的发明构思，本申请实施例还提供一种设备1500，如图15所示，包括：设备1500包括处理器1501、存储器1502和收发器1503；所述处理器1501、所述存储器1502和所述收发器1503均通过总线1504连接；
所述存储器1502，用于存储计算机执行指令；
所述处理器1501，用于执行所述存储器1502存储的计算机执行指令；
如果所述设备1500为代理设备，所述处理器1501执行所述存储器1502存储的计算机执行指令，使得所述设备1500执行本申请实施例提供的上述内容请求方法中由代理设备执行的步骤，或者使得代理设备部署与该步骤对应的功能单元。
处理器1501，可以包括不同类型的处理器1501，或者包括相同类型的处理器1501；处理器1501可以是以下的任一种：中央处理器(Central Processing Unit，简称CPU)、ARM处理器、现场可编程门阵列(Field Programmable Gate Array，简称FPGA)、专用处理器等具有计算处理能力的器件。一种可选实施方式，所述处理器1501还可以集成为众核处理器。
存储器1502可以是以下的任一种或任一种组合：随机存取存储器(Random Access Memory，简称RAM)、只读存储器(read only memory，简称ROM)、非易失性存储器(non-volatile memory，简称NVM)、固态硬盘(Solid State Drives，简称SSD)、机械硬盘、磁盘、磁盘整列等存储介质。
收发器1503用于设备1500与其他设备进行数据交互；例如，如果设备1500为代理设备，待代理设备可以执行上述实施例一～实施例六中任一所述的方法，实现内容请求方法，该代理设备通过收发器1503与终端进行数据交互。收发器1503可以是以下的任一种或任一种组合：网络接口(例如以太网接口)、无线网卡等具有网络接入功能的器件。
该总线1504可以包括地址总线、数据总线、控制总线等，为便于表示，图9用一条粗线表示该总线。总线1504可以是以下的任一种或任一种组合：工业标准体系结构(Industry Standard Architecture，简称ISA)总线、外设组件互连标准(Peripheral Component Interconnect，简称PCI)总线、扩展工业标准结构(Extended Industry Standard Architecture，简称EISA)总线等有线数据传输的器件。
本申请实施例提供一种计算机可读存储介质，计算机可读存储介质中存储有计算机执行指令；代理设备的处理器执行该计算机执行指令，使得代理设备执行本申请实施例提 供的上述内容请求方法中由代理设备执行的步骤，或者使得代理设备部署与该步骤对应的功能单元。
本申请实施例提供一种计算机程序产品，该计算机程序产品包括计算机执行指令，该计算机执行指令存储在计算机可读存储介质中。代理设备的处理器可以从计算机可读存储介质读取该计算机执行指令；处理器执行该计算机执行指令，使得代理设备执行本申请实施例提供的上述内容请求方法中由代理设备执行的步骤，或者使得代理设备部署与该步骤对应的功能单元。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本发明实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存储的任何可用介质或者是包含一个多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质(例如，软盘、硬盘、磁带)、光介质(例如，DVD)或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。
本领域内的技术人员应明白，本申请的实施例可提供为方法、系统、或计算机程序产品。因此，本申请可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本申请可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本申请是参照根据本申请实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。

Claims (24)

  1. 一种内容请求方法，其特征在于，包括：
    代理设备接收终端发送的请求消息，所述请求消息携带内容标识；
    所述代理设备在接收到所述终端发送的请求消息后，通过所述内容标识获取目标缓存设备的标识，所述目标缓存设备为存储所述内容标识对应的请求内容的设备；
    所述代理设备根据所述目标缓存设备的标识，向所述目标缓存设备发送所述内容标识，请求获取所述请求内容；
    所述代理设备将获取的所述请求内容发送至所述终端。
  2. 根据权利要求1所述的方法，其特征在于，所述代理设备通过所述内容标识获取目标缓存设备的标识，包括：
    所述代理设备通过所述内容标识，查询自身的内容索引信息，获取所述目标缓存设备的标识；或者
    所述代理设备向缓存控制器发送所述内容标识，并接收所述缓存控制器根据所述内容标识获得的所述目标缓存设备的标识。
  3. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述代理设备若通过所述内容标识获取目标缓存设备的标识失败，则向所述源服务器请求获取所述请求内容；
    所述代理设备将获取的所述请求内容发送至所述终端。
  4. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    所述代理设备若通过所述内容标识获取目标缓存设备的标识失败，则将所述源服务器的标识发送至所述终端，使所述终端根据所述源服务器的标识向所述源服务器请求获取所述请求内容。
  5. 根据权利要求1至4任一所述的方法，其特征在于，所述代理设备为移动边缘计算MEC缓存服务器或网关GW缓存服务器，所述目标缓存设备为MEC缓存服务器或GW缓存服务器。
  6. 根据权利要求1至4任一所述的方法，其特征在于，所述代理设备集成于MEC或GW，所述目标缓存设备集成于MEC或GW。
  7. 根据权利要求2所述的方法，其特征在于，所述缓存控制器为下列任一种：
    独立实体网元、集成于MEC、集成于GW、集成于所述代理设备或所述目标缓存设备的控制模块。
  8. 一种内容请求方法，其特征在于，包括：
    代理设备接收终端发送的请求消息，所述请求消息携带内容标识；
    所述代理设备在接收到所述终端发送的请求消息后，通过所述内容标识获取目标缓存设备的标识，所述目标缓存设备为存储所述内容标识对应的请求内容的设备；
    所述代理设备将所述目标缓存设备的标识发送至所述终端。
  9. 根据权利要求8所述的方法，其特征在于，所述方法还包括：
    所述代理设备若通过查询所述内容标识获取目标缓存设备的标识失败，则将所述源服务器的标识发送至所述终端，使所述终端根据所述源服务器的标识向所述源服务器请求获取所述请求内容。
  10. 根据权利要求8所述的方法，其特征在于，所述方法还包括：
    所述代理设备若通过所述内容标识获取目标缓存设备的标识失败，则向所述源服务器请求获取所述请求内容；
    所述代理设备将获取的所述请求内容发送至所述终端。
  11. 根据权利要求8至10任一所述的方法，其特征在于，所述代理设备为MEC缓存服务器或GW缓存服务器，所述目标缓存设备为MEC缓存服务器或GW缓存服务器。
  12. 根据权利要求8至10任一所述的方法，其特征在于，所述代理设备集成于MEC或GW，所述目标缓存设备集成于MEC或GW。
  13. 一种代理设备，其特征在于，包括：
    收发器，用于接收终端发送的请求消息，所述请求消息携带内容标识；
    处理器，用于在接收到所述终端发送的请求消息后，通过所述内容标识获取目标缓存设备的标识，所述目标缓存设备为存储所述请求内容的设备；
    所述收发器，还用于根据所述目标缓存设备的标识，向所述目标缓存设备发送所述内容标识，请求获取所述请求内容，以及将获取的请求内容发送至所述终端。
  14. 根据权利要求13所述的代理设备，其特征在于，所述处理器，具体用于：
    通过所述内容标识，查询自身的内容索引信息，获取所述目标缓存设备的标识；或者
    通过所述内容标识，查询缓存控制器获取所述目标缓存设备的标识。
  15. 根据权利要求13所述的代理设备，其特征在于，若所述处理器通过所述内容标识获取目标缓存设备的标识失败，
    则所述处理器，还用于向所述源服务器请求获取所述请求内容；
    所述收发器还用于：将获取的所述请求内容发送至所述终端。
  16. 根据权利要求13所述的代理设备，其特征在于，若通过所述内容标识获取目标缓存设备的标识失败，
    则所述收发器，还用于将所述源服务器的标识发送至所述终端，使所述终端根据所述源服务器的标识向所述源服务器请求获取所述请求内容。
  17. 根据权利要求13至16任一所述的代理设备，其特征在于，所述代理设备为MEC缓存服务器或GW缓存服务器，所述目标缓存设备为MEC缓存服务器或GW缓存服务器。
  18. 根据权利要求13至16任一所述的代理设备，其特征在于，所述代理设备集成于MEC或GW，所述目标缓存设备集成于MEC或GW。
  19. 根据权利要求14所述的代理设备，其特征在于，所述缓存控制器为下列任一种：
    独立实体网元、集成于MEC、集成于GW、集成于所述代理设备或所述目标缓存设备的控制模块。
  20. 一种代理设备，其特征在于，包括：
    收发器，用于接收终端发送的请求消息，所述请求消息携带内容标识；
    处理器，用于在接收到所述终端发送的请求消息后，通过所述内容标识获取所述目标缓存设备的标识，所述目标缓存设备为存储所述内容标识对应的请求内容的设备；
    所述收发器，还用于将获取的所述目标缓存设备的标识发送至所述终端。
  21. 根据权利要求20所述的代理设备，其特征在于，若所述处理器通过所述内容标识获取目标缓存设备的标识失败，
    则所述收发器还用于：将所述源服务器的标识发送至所述终端，使所述终端根据所述 源服务器的标识向所述源服务器请求获取所述请求内容。
  22. 根据权利要求19所述的代理设备，其特征在于：若通过所述内容标识获取目标缓存设备的标识失败，
    所述处理器，还用于：则向所述源服务器请求获取所述请求内容；
    所述收发器，还用于：将获取的所述请求内容发送至所述终端。
  23. 根据权利要求20至22任一所述的代理设备，其特征在于，所述代理设备为MEC缓存服务器或GW缓存服务器，所述目标缓存设备为MEC缓存服务器或GW缓存服务器。
  24. 根据权利要求20至22任一所述的代理设备，其特征在于，所述代理设备集成于MEC或GW，所述目标缓存设备集成于MEC或GW。
PCT/CN2017/072502 2017-01-24 2017-01-24 一种内容请求方法及代理设备 WO2018137149A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/072502 WO2018137149A1 (zh) 2017-01-24 2017-01-24 一种内容请求方法及代理设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/072502 WO2018137149A1 (zh) 2017-01-24 2017-01-24 一种内容请求方法及代理设备

Publications (1)

Publication Number Publication Date
WO2018137149A1 true WO2018137149A1 (zh) 2018-08-02

Family

ID=62978459

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/072502 WO2018137149A1 (zh) 2017-01-24 2017-01-24 一种内容请求方法及代理设备

Country Status (1)

Country Link
WO (1) WO2018137149A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109995865A (zh) * 2019-04-03 2019-07-09 广东工业大学 一种基于移动边缘计算的数据信息的请求响应方法及装置
US11122106B2 (en) 2019-11-08 2021-09-14 Samsung Electronics Co., Ltd. Method and apparatus for providing web service using edge computing service

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1855825A (zh) * 2005-04-27 2006-11-01 株式会社日立制作所 计算机系统
CN101820434A (zh) * 2009-02-28 2010-09-01 华为技术有限公司 对等网络媒体传输方法、系统和对等节点
CN102833361A (zh) * 2011-06-15 2012-12-19 丛林网络公司 为资源请求终止连接和选择目标源装置
CN102833306A (zh) * 2011-06-15 2012-12-19 丛林网络公司 网络集成动态资源路由
CN102833148A (zh) * 2011-06-15 2012-12-19 丛林网络公司 资源请求及资源的路由代理
WO2013044987A1 (en) * 2011-09-28 2013-04-04 Telefonaktiebolaget L M Ericsson (Publ) Caching in mobile networks
CN103944994A (zh) * 2014-04-25 2014-07-23 中国联合网络通信集团有限公司 分布式资源获取方法及装置

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1855825A (zh) * 2005-04-27 2006-11-01 株式会社日立制作所 计算机系统
CN101820434A (zh) * 2009-02-28 2010-09-01 华为技术有限公司 对等网络媒体传输方法、系统和对等节点
CN102833361A (zh) * 2011-06-15 2012-12-19 丛林网络公司 为资源请求终止连接和选择目标源装置
CN102833306A (zh) * 2011-06-15 2012-12-19 丛林网络公司 网络集成动态资源路由
CN102833148A (zh) * 2011-06-15 2012-12-19 丛林网络公司 资源请求及资源的路由代理
WO2013044987A1 (en) * 2011-09-28 2013-04-04 Telefonaktiebolaget L M Ericsson (Publ) Caching in mobile networks
CN103944994A (zh) * 2014-04-25 2014-07-23 中国联合网络通信集团有限公司 分布式资源获取方法及装置

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109995865A (zh) * 2019-04-03 2019-07-09 广东工业大学 一种基于移动边缘计算的数据信息的请求响应方法及装置
US11122106B2 (en) 2019-11-08 2021-09-14 Samsung Electronics Co., Ltd. Method and apparatus for providing web service using edge computing service

Similar Documents

Publication Publication Date Title
CN108696895B (zh) 资源获取方法、装置及系统
JP5885310B2 (ja) モバイル端末間のコンテンツ共有
US9390200B2 (en) Local caching device, system and method for providing content caching service
US20220103990A1 (en) Communication Method, Apparatus, and System
US11172460B2 (en) User location monitoring in mobile edge environment
WO2021057128A1 (zh) 一种基于nf的通信方法、设备及存储介质
WO2017114397A1 (zh) 一种实现心跳机制的方法、装置及系统
CN113037855B (zh) 一种多媒体访问系统、方法、装置、终端及介质
WO2019129300A1 (zh) 缓存决策方法及装置
WO2019024733A1 (zh) 无线接入点认证信息的查询方法与设备
WO2015021591A1 (zh) 互联网内容存储方法和设备
WO2018223964A1 (zh) 缓存数据控制方法及设备
TWI640214B (zh) 一種網路接入方法、相關設備和系統
WO2018214966A1 (zh) 终端控制方法以及使用该方法的网络单元和采集装置
WO2018137149A1 (zh) 一种内容请求方法及代理设备
WO2019057209A1 (zh) 本地内容的缓存方法、装置、存储介质及电子装置
US11330038B2 (en) Systems and methods for utilizing blockchain for securing browsing behavior information
WO2018176439A1 (zh) 地址获取方法、业务能力开放网元和移动边缘计算网元
JP6340076B2 (ja) 移動性管理方法、装置及びシステム
EP2999266B1 (en) Method, device and system for obtaining mobile network data resources
US20220345925A1 (en) Distribution of Consolidated Analytics Reports in a Wireless Core Network
WO2013083085A1 (zh) 数据获取方法及装置
WO2014036970A1 (zh) 应用触发方法及设备、系统
WO2016090927A1 (zh) 实现共享waln管理的方法、系统及wlan共享注册服务器
US20230137283A1 (en) Systems and methods to optimize registration and session establishment in a wireless network

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17894528

Country of ref document: EP

Kind code of ref document: A1