WO2018090336A1 - 缓存数据获取方法、相关设备以及通信系统 - Google Patents

缓存数据获取方法、相关设备以及通信系统 Download PDF

Info

Publication number
WO2018090336A1
WO2018090336A1 PCT/CN2016/106447 CN2016106447W WO2018090336A1 WO 2018090336 A1 WO2018090336 A1 WO 2018090336A1 CN 2016106447 W CN2016106447 W CN 2016106447W WO 2018090336 A1 WO2018090336 A1 WO 2018090336A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
request
data packet
target data
cache
Prior art date
Application number
PCT/CN2016/106447
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/CN2016/106447 priority Critical patent/WO2018090336A1/zh
Priority to EP16921514.2A priority patent/EP3531745A4/en
Priority to CN201680090408.XA priority patent/CN109891929A/zh
Publication of WO2018090336A1 publication Critical patent/WO2018090336A1/zh
Priority to US16/413,881 priority patent/US20190274069A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/10—Flow control between communication endpoints
    • H04W28/14—Flow control between communication endpoints using intermediate storage
    • 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 invention relates to the field of wireless network technologies, and in particular, to a cache data acquisition method, related device, and system.
  • the more common caching method is to distribute the content of the source server to the edge of the network through the Content Delivery Network (CDN) deployed on the backbone network (English: Backbone Network), according to the network traffic and the connection of each node.
  • CDN Content Delivery Network
  • the comprehensive information such as the load status and the distance to the user and the response time redirects the user's data request to the service node closest to the user, so that the user can obtain the required data nearby, alleviate the congestion of the Internet network, and improve the user's access to the website. responding speed.
  • the CND is deployed only on the backbone network, and the data is pushed to the edge of the backbone network.
  • the backhaul cost of the wireless network to the core network link is large, so that the user terminal responds slowly when requesting cached data, thereby reducing the user experience.
  • the purpose of the present application is to provide a cache data acquisition method, which can avoid the overhead on the backhaul link of the wireless network to the core network, thereby improving the response speed of the user terminal requesting data and improving the user experience.
  • an embodiment of the present invention provides a method for acquiring cache data, including: receiving, by a base station, a request data packet sent by a user terminal, where the request data packet is used to request target data from a source server, and the base station according to the first data cache list, Determining whether the information of the request packet is related to the first data cache column The information in the table is matched.
  • the base station sends the target data stored in the cache device to the user terminal.
  • the cache device can It is a base station, a local gateway, a cache server connected to the base station through a local gateway, or a cache server independently deployed in the mobile network.
  • the request data packet after receiving the request data packet sent by the user terminal, the request data packet is used by the user terminal to request target data from the source server, and the base station determines, according to the first data cache list, whether the information of the request data packet is related to the first data.
  • the information in the cache list matches, and if so, the target data stored in the cache device is sent to the user terminal.
  • a cache device such as a base station, a local gateway, or a cache server
  • the overhead on the link thereby improving the response speed of the user terminal requesting data and improving the user experience.
  • the base station may further obtain, before determining, according to the first data cache list, whether the information of the request data packet matches the information in the first data cache list.
  • the first data cache list wherein the first data cache list includes at least one of an address of the server and an identifier of the data.
  • an implementation manner that the base station sends the target data to the user terminal may be: the base station sends the target data to the user by using the first bearer established by the base station and the cache device. Terminal; it can be understood that the cache device at this time includes a local gateway, a cache server connected to the base station through the local gateway, or a cache server independently deployed in the mobile network.
  • the data transmission between the base station and the cache device is carried by creating the first bearer, so that data transmission between the base station and the cache device and the source server is implemented, so that the user can directly obtain the target data from the cache device, which can avoid redundancy.
  • the transmission of the remaining data mitigates network congestion, shortens response delay, and improves user experience.
  • the method may further include: when the information of the request data packet does not match the information in the first data cache list, the base station may establish the base station and the source server. The second bearer transmits the target data to the user terminal.
  • the second bearer is used to carry data transmission between the base station and the source server, so that data transmission between the base station and the cache device and the source server is implemented, so that the user can set the buffer.
  • the original TCP Transmission Control Protocol
  • the original TCP Transmission Control Protocol
  • the base station may further determine whether the cache device has cached the target data, when the target data is cached. , the target data is sent to the user terminal.
  • the target data can be stored in a cache device (a base station, a local gateway, a cache server connected to the base station through a local gateway, or a cache server independently deployed in the mobile network).
  • the redundant data transmission can be avoided.
  • an implementation manner that the base station sends the target data to the user terminal may be: the base station encapsulates the target data into And responding to the data packet; the source address of the response data packet is a target address of the request data packet, and further, the response data packet is sent to the user terminal.
  • the base station replaces the request of the source server in response to the target data of the request packet, and prevents the user terminal from identifying the data packet when the source address of the response packet is inconsistent with the target address of the request packet.
  • the base station may further send the target server Sending the request packet, so that after the source server receives the request packet, the source server sends the target data to the user terminal.
  • the cache device base station, local gateway, or cache server
  • the TCP Transmission Control Protocol
  • the base station when the base station detects the target data that is sent by the source server to the user terminal, the base station may save the target data to the cache device (base station,
  • the local gateway or the cache server is configured to save the target data that can be cached by the cache device, avoiding repeatedly requesting the target data, and alleviating network congestion.
  • the base station may further generate a first request data packet, where the source address of the first request data packet The address of the cache device is used to request target data from the source server; and further, the first request data packet is sent to the source server, so that the source server sends the target data to the cache device after receiving the first request data packet.
  • a TCP (Transmission Control Protocol) data transmission channel between the base station and the source server is used to transmit data, and a TCP link is provided. Processing method to achieve the acquisition of target data.
  • TCP Transmission Control Protocol
  • the base station may receive the signaling message sent by the cache device, and And generating, according to the signaling message, a second request data packet, where the second request data packet is used to request target data from the source server, and further, sending the second request data packet to the source server, so that the source server receives the After the second request packet, the target data is returned. Further, the base station receives the target data returned by the source server, and sends the target data to the user terminal.
  • the cache device local gateway or cache server
  • the TCP Transmission Control Protocol
  • the base station may further save the target data to the cache device (local gateway or cache server).
  • the cache device can save the target data that can be cached, avoiding repeatedly requesting target data, and alleviating network congestion.
  • an implementation manner of the base station determining whether the target data is cached may be: the base station determining whether the cache device has cached the target data, where The cache device is a local gateway, a cache server connected to the base station through the local gateway, or a cache server independently deployed in the mobile network; correspondingly, when the cache device has cached the target data, the base station sends the target data to the user terminal.
  • the implementation may be: the base station sends a data request to the cache device, so that after the cache device receives the data request, The target data is sent to the user terminal.
  • the method may further include: the base station sending an address of the cache device to the user terminal.
  • the embodiment of the present invention further provides a method for acquiring a cache data, including: a cache device receiving a request data packet sent by a user terminal, where the request data packet is sent to a base station by a user terminal, for requesting target data;
  • a cache device receiving a request data packet sent by a user terminal, where the request data packet is sent to a base station by a user terminal, for requesting target data;
  • the base station determines that the information of the request data packet matches the information in the first data cache list or the target address of the request data packet is the address of the cache device
  • the base station requests the data.
  • the packet is sent to the cache device, at which time the cache device receives the request packet and sends the target data to the user terminal.
  • the cache device can be a base station, a local gateway, a cache server connected to the base station through a local gateway, or a cache server independently deployed in the mobile network.
  • the cache device receives the request data packet sent by the user terminal, where the request data packet is sent to the base station by the user terminal for requesting target data; when the base station receives the request data packet, and the base station determines the request data packet
  • the base station sends the request data packet to the cache device
  • the cache device sends the target data to the user.
  • the terminal sinks data of the source server to a cache device (base station, local gateway, a cache server connected to the base station through the local gateway, or a cache server independently deployed in the mobile network) deployed in the mobile network. Therefore, the user can directly obtain the target data from the cache device, thereby avoiding the overhead on the backhaul link of the wireless network to the core network, thereby improving the response speed of the user terminal requesting data and improving the user experience.
  • an implementation manner that the cache device sends the target data to the user terminal may be: the cache device determines whether the target data has been cached, when When the target data is cached, the target data is sent to the user terminal.
  • an implementation manner that the cache device sends the target data to the user terminal may be: the cache device encapsulates the target data into a response.
  • the data packet; the source address of the response data packet is the target address of the request data packet, and further, the response data packet is sent to the user terminal.
  • the cache device replaces the request of the source server to respond to the target data of the request data packet, and prevents the user terminal from identifying the data packet when the source address of the response data packet is inconsistent with the target address of the request data packet. At the same time, it avoids the transmission of redundant data, alleviates network congestion, shortens response delay, and improves user experience.
  • the method may further include: the cache device sends the request data packet to the source server, so that After receiving the request packet, the source server sends the target data to the user terminal.
  • the TCP Transmission Control Protocol
  • the method further includes: the cache device sending the first request data packet to the source server, so that after the source server receives the first request data packet, the source server returns the target data
  • the first request data packet is used to request the target data from the source server, and further, the cache device receives the target data returned from the source server, and sends the target data to the user terminal.
  • the cache device (the base station, the local gateway, the cache server connected to the base station through the local gateway, or the cache server independently deployed in the mobile network) does not cache the target data
  • the TCP between the cache device and the source server is used.
  • the data transmission channel transmits data, and provides a TCP link processing method to achieve target data acquisition.
  • the method further includes: the cache device sends a signaling message to the base station, so that the base station sends the source message to the source after receiving the signaling message.
  • the server sends a second request data packet, where the second request data packet is used to request target data from the source server; and further, the base station receives the target data returned from the source server, and sends the target data to the user terminal.
  • the cache device when the cache device (the local gateway, the cache server connected to the base station through the local gateway, or the cache server independently deployed in the mobile network) does not cache the target data, the TCP between the base station and the source server is used (Transmission Control) Protocol) Data transmission channel to transmit data, providing a TCP link processing method to achieve target data acquisition.
  • TCP Transmission Control
  • the embodiment of the present invention further provides a cache data obtaining method, including: a user terminal generates a third request data packet, where the third request data packet is used to request target data from a source server, and according to the second data cache. a list, determining whether the information of the third request packet matches the information in the second data cache list, and if yes, generating a fourth request packet, wherein the second data cache list includes at least one information, and the information and Corresponding relationship of the address of the cache device; the target address of the fourth request packet is the address of the cache device corresponding to the matched information; the fourth request packet is used to request the target data from the cache device, and further, the user terminal
  • the cache device sends a fourth request data packet, so that the cache device sends the target data to the user terminal after receiving the fourth request data packet. At this time, the user terminal receives the target data.
  • the cache device can be a base station, a local gateway, a cache server connected to the base station through a local gateway
  • the user terminal is configured with a second data cache list, where the second data cache list includes at least one information, and a correspondence between the information and an address of the cache device, when the user terminal receives the target data for requesting the source server.
  • the user terminal determines, according to the second data cache list, whether the information of the third request packet matches the information in the second data cache list, and if yes, the target data is cacheable by the cache device.
  • the user terminal modifies the target address of the third request packet to the address of the cache device corresponding to the matched information, generates a fourth request packet for requesting the target data from the cache device, and further sends the target request packet to the cache device.
  • Sending a fourth request data packet so that the cache device sends the target data to the user terminal after receiving the fourth request data packet, and at this time, the user terminal receives the target data, thereby implementing a cache closer to the user.
  • Obtain target data in devices such as base stations, local gateways, or cache servers, etc.), avoiding Net cost of the backhaul link to the core network, thereby improving the user terminal requests According to the response speed, enhance the user experience.
  • the user terminal may send the third request data packet, so that after receiving the third request data packet, the source server sends the third request data packet target data to the user terminal, and at this time, the user terminal receives the target data.
  • the data is transmitted by using a TCP (Transmission Control Protocol) data transmission channel between the user terminal and the source server, and a TCP link processing manner is provided to obtain target data.
  • TCP Transmission Control Protocol
  • the method before the user terminal determines whether the information of the third request data packet matches the information in the second data cache list, the method further includes: the user The terminal acquires a second data cache list, where the second data cache list includes at least one information, and a correspondence between the information and an address of the cache device, where the information includes an address of the server and/or an identifier of the data. .
  • the present invention provides a base station, including:
  • a receiving module configured to receive a request data packet sent by the user terminal, where the request data packet is used to request target data from the source server;
  • a processing module configured to determine, according to the pre-stored first data cache list, whether the information of the request data packet matches the information in the first data cache list
  • a sending module configured to send the target data to the user terminal when the information of the request data packet matches the information in the first data cache list.
  • the request data packet after receiving the request data packet sent by the user terminal, the request data packet is used by the user terminal to request target data from the source server, and the base station determines, according to the first data cache list, whether the information of the request data packet is related to the first data.
  • the information in the cache list matches, and if so, the target data stored in the cache device is sent to the user terminal.
  • a cache device such as a base station, a local gateway, or a cache server
  • the overhead on the link thereby improving the response speed of the user terminal requesting data and improving the user experience.
  • the processing module is further configured to: obtain a first data cache list, where the first data cache list includes at least one of the following information:
  • the sending module is further configured to:
  • the target data is sent to the user terminal by using the first bearer established by the base station and the cache device.
  • the sending module is further configured to:
  • the target data is sent to the user terminal by using a second bearer established by the base station and the source server.
  • the processing module is further configured to: determine whether the target data has been cached, and when the target data has been cached, trigger the sending module to send the target data to the user terminal.
  • the processing module is further configured to: encapsulate the target data into a response data packet; a source address of the response data packet is a target address of the request data packet;
  • the sending module is further configured to: send the response data packet to the user terminal.
  • the sending module is further configured to: when the target data is not cached, send the request data packet to the source server After the source server receives the request data packet, the source server sends the target data to the user terminal.
  • the processing module is further configured to: when the target data is not cached, generate a first request data packet, where a source address of the first request data packet is an address of a cache device, and is used to request target data from the source server ;
  • the sending module is further configured to: send the first request data packet to the source server, so that after the source server receives the first request data packet, send the target data to the Cache device.
  • the receiving module is further configured to: when the target data is not cached, receive a signaling message sent by the cache device;
  • the processing module is further configured to: generate a second request data packet according to the signaling message, where the second request data packet is used to request the target data from the source server;
  • the sending module is further configured to: send the second request data packet to the source server, so that the source server returns the target data after receiving the second request data packet;
  • the receiving module is further configured to: receive the target data returned by the source server;
  • the sending module is further configured to: send the target data to the user terminal.
  • the processing module is further configured to: determine whether the cache device includes the target data, where the cache device is a local gateway, the cache server connected to the base station by using the local gateway, or independently deployed on the cache server a cache server in the mobile network;
  • the sending module is further configured to: when the cache device has cached the target data, send a data request to the cache device, so that the cache device sends the target data after receiving the data request Send to the user terminal.
  • the sending module is further configured to: send an address of the cache device to the user terminal.
  • the embodiment of the present invention further provides a cache device, including:
  • a receiving module configured to receive a request data packet sent by the user terminal, where the request data packet is sent to the base station by the user terminal for requesting target data; when the base station receives the request data packet, When the base station determines that the information of the request data packet matches the information in the first data cache list or the target address of the request data packet is the address of the cache device, the base station sends the request data packet to the cache device. ;
  • a sending module configured to send the target data to the user terminal.
  • the cache device receives the request data packet sent by the user terminal, where the request data packet is sent to the base station by the user terminal for requesting target data; when the base station receives the request data packet, and the base station determines the request data packet Information matches the information in the first data cache list
  • the base station sends the request packet to the cache device, and the cache device sends the target data to the user terminal, by sinking the data of the source server to the deployment.
  • a cache device base station, local gateway, cache server connected to the base station through the local gateway or independently deployed in the cache server in the mobile network
  • the overhead of the wireless network to the backhaul link of the core network is avoided, thereby improving the response speed of the user terminal requesting data and improving the user experience.
  • the cache device further includes: a processing module, configured to determine that the target data is cached; and when the target data is cached, triggering the The sending module sends the target data to the user terminal.
  • the processing module is further configured to: encapsulate the target data into a response data packet; a source address of the response data packet is a target address of the request data packet;
  • the sending module is further configured to: send the response data packet to the user terminal.
  • the sending module is further configured to: when the base station determines information of the request data packet and the first data cache list When the information matches, and the target data is not cached, the request data packet is sent to the source server, so that after the source server receives the request data packet, the source server uses the target data. Send to the user terminal.
  • the sending module is further configured to: when the target data is not cached, send the first request data packet to the source server, so that after the source server receives the first request data packet, the source Returning, by the server, the target data, where the first request data packet is used to request the target data from the source server;
  • the receiving module is further configured to: receive the target data returned from the source server;
  • the sending module is further configured to: send the target data to the user terminal.
  • the sending module is further configured to: when the target data is not cached, send a signaling message to the base station, After the base station receives the signaling message, the base station sends a second request data packet to the source server, where the second request data packet is used by the base station to request the target server from the source server. Data; the base station receives the target data returned from the source server and transmits the target data to the user terminal.
  • the embodiment of the present invention further provides a user terminal, including:
  • a processing module configured to generate a third request data packet, where the third request data packet is used to request target data from the source server, and determine, according to the second data cache list, whether the information of the third request data packet is the second The information in the data cache list matches; the second data cache list includes at least one information, and a correspondence between the information and an address of the cache device;
  • the processing module is further configured to: when the information of the third request data packet matches the information in the second data cache list, generate a fourth request data packet, where a target address of the fourth request data packet is matched The address of the cache device corresponding to the information; the fourth request data packet is used to request the target data from the cache device;
  • a sending module configured to send the fourth request data packet to the cache device, so that the cache device sends the target data to the user terminal after receiving the fourth request data packet;
  • a receiving module configured to receive the target data.
  • the user terminal is configured with a second data cache list, where the second data cache list includes at least one information, and a correspondence between the information and an address of the cache device, when the user terminal receives the target data for requesting the source server.
  • the user terminal determines, according to the second data cache list, whether the information of the third request packet matches the information in the second data cache list, and if yes, the target data is cacheable by the cache device.
  • the user terminal modifies the target address of the third request packet to the address of the cache device corresponding to the matched information, generates a fourth request packet for requesting the target data from the cache device, and further sends the target request packet to the cache device.
  • Sending a fourth request data packet so that the cache device sends the target data to the user terminal after receiving the fourth request data packet, and at this time, the user terminal receives the target data, thereby implementing a cache closer to the user.
  • Obtain target data in devices such as base stations, local gateways, or cache servers, etc.), avoiding Net cost of the backhaul link to the core network, thereby improving the response speed of the user data requested by the terminal, enhance the user experience.
  • the sending module is further configured to: when the information of the third request data packet does not match the information in the second data cache list, send the third request data packet, so that the source server receives the After the third request data packet is described, the target data is sent to the user terminal;
  • the receiving module is further configured to: receive the target data.
  • the processing module is further configured to:
  • the second data cache list includes at least one information, and a correspondence between the information and an address of the cache device; wherein the information includes an address of the server and/or an identifier of the data .
  • the embodiment of the present invention further provides a base station, including:
  • a receiver configured to receive a request data packet sent by the user terminal, where the request data packet is used to request target data from the source server;
  • a processor configured to determine, according to the pre-stored first data cache list, whether the information of the request data packet matches the information in the first data cache list;
  • a transmitter configured to send the target data to the user terminal when the information of the request data packet matches the information in the first data cache list.
  • the processor is further configured to: obtain a first data cache list, where the first data cache list includes at least one of the following information:
  • the transmitter is further configured to:
  • the target data is sent to the user terminal by using the first bearer established by the base station and the cache device.
  • the transmitter is further configured to:
  • the target data is sent to the user terminal by using a second bearer established by the base station and the source server.
  • the processor is further configured to: determine whether the target data has been cached, and trigger the transmitter when the target data is cached Sending the target data to the user terminal.
  • the processor is further configured to: encapsulate the target data into response data a packet; a source address of the response packet is a target address of the request packet;
  • the transmitter is further configured to: send the response data packet to the user terminal.
  • the transmitter is further configured to: when the target data is not cached, send the request data packet to the source server After the source server receives the request data packet, the source server sends the target data to the user terminal.
  • the processor is further configured to: when the target data is not cached, generate a first request data packet, where the first The source address of the request packet is an address of the cache device, and is used to request target data from the source server;
  • the transmitter is further configured to: send the first request data packet to the source server, so that the source server sends the target data to the cache after receiving the first request data packet device.
  • the receiver is further configured to: when the target data is not cached, receive the signaling message sent by the cache device;
  • the processor is further configured to: generate, according to the signaling message, a second request data packet, where the second request data packet is used to request the target data from the source server;
  • the transmitter is further configured to: send the second request data packet to the source server, so that the source server returns the target data after receiving the second request data packet;
  • the receiver is further configured to: receive the target data returned by the source server;
  • the transmitter is further configured to: send the target data to the user terminal.
  • the processor is further configured to: determine whether the cache device includes the target data, where the cache device is local a gateway, the cache server connected to the base station by the local gateway, or a cache server independently deployed in a mobile network;
  • the transmitter is further configured to: when the cache device has cached the target data, to the The storage device sends a data request, so that the cache device sends the target data to the user terminal after receiving the data request.
  • the transmitter is further configured to: send an address of the cache device to the user terminal.
  • the embodiment of the present invention further provides a cache device, including:
  • a receiver configured to receive a request data packet sent by the user terminal, where the request data packet is sent to the base station by the user terminal for requesting target data; when the base station receives the request data packet, When the base station determines that the information of the request data packet matches the information in the first data cache list or the target address of the request data packet is the address of the cache device, the base station sends the request data packet to the cache device. ;
  • a transmitter configured to send the target data to the user terminal.
  • the cache device further includes:
  • a processor configured to determine that the target data has been cached; when the target data has been cached, triggering the transmitter to send the target data to the user terminal.
  • the processor is further configured to: encapsulate the target data into a response data packet;
  • the source address is the target address of the request packet;
  • the transmitter is further configured to: send the response data packet to the user terminal.
  • the transmitter is further configured to:
  • the base station determines that the information of the request data packet matches the information in the first data cache list, and does not cache the target data, sends the request data packet to the source server, so that the source After receiving the request packet, the server sends the target data to the user terminal.
  • the transmitter is further configured to: when the target data is not cached, send the first request data packet to the source server After the source server receives the first request data packet, the source server returns the target data, and the first request data packet is used to request the target data from the source server;
  • the receiver is further configured to: receive the target data returned from the source server;
  • the transmitter is further configured to: send the target data to the user terminal.
  • the transmitter is further configured to: when the target data is not cached, send a signaling message to the base station, so that After receiving the signaling message, the base station sends a second request data packet to the source server, where the second request data packet is used by the base station to request the target data from the source server.
  • the base station receives the target data returned from the source server and transmits the target data to the user terminal.
  • the ninth aspect, the embodiment of the present invention further provides a user terminal, including:
  • a processor configured to generate a third request data packet, the third request data packet is used to request target data from the source server, and determine, according to the second data cache list, whether the information of the third request data packet is the second The information in the data cache list matches; the second data cache list includes at least one information, and a correspondence between the information and an address of the cache device;
  • the processor is further configured to: when the information of the third request data packet matches the information in the second data cache list, generate a fourth request data packet, where a target address of the fourth request data packet is matched The address of the cache device corresponding to the information; the fourth request data packet is used to request the target data from the cache device;
  • a transmitter configured to send the fourth request data packet to the cache device, so that the cache device sends the target data to the user terminal after receiving the fourth request data packet;
  • a receiver for receiving the target data.
  • the transmitter is further configured to: when the information of the third request data packet does not match the information in the second data cache list, Determining a third request packet, so that the source server sends the target data to the user terminal after receiving the third request packet;
  • the receiver is further configured to: receive the target data.
  • the processor is further configured to:
  • the second data cache list includes at least one information, and a correspondence between the information and an address of the cache device; wherein the information includes an address of the server and/or an identifier of the data .
  • an embodiment of the present invention further provides a base station, including a processor, a memory, and a communication interface.
  • the processor is coupled to the memory and the communication interface, for example, the processor can be connected to the memory and the communication interface through a bus; the communication interface is configured to be deployed with the user terminal, the cache device (local gateway, a cache server connected to the base station through the local gateway, or independently A device such as a cache server in the mobile network communicates; a memory is used to store program code, target data, and a second data cache list of the cache data acquisition method described in the first aspect, and the processor is configured to call the program code in the memory. Perform some or all of the processes in the first aspect.
  • an embodiment of the present invention further provides a cache device, including a processor, a memory, and a communication interface.
  • the processor is coupled to the memory and the communication interface, for example, the processor can be coupled to the memory and the communication interface via a bus; the communication interface is configured to communicate with a device such as a user terminal, a source server, etc.; the memory is configured to store the cached data acquisition described in the second aspect The program code of the method and the target data; the processor is used to call the program code in the memory to perform part or all of the flow of the second aspect.
  • the cache device may be a base station, a local gateway, a cache server connected to the base station through a local gateway, or a cache server independently deployed in the mobile network.
  • an embodiment of the present invention further provides a user terminal, including a processor, a memory, and a communication interface.
  • the processor is coupled to the memory and the communication interface, for example, the processor can be coupled to the memory and the communication interface via a bus; the communication interface is configured to communicate with a device such as a cache device or a source server; and the memory is configured to store the cached data acquisition described in the third aspect
  • the program code of the method and the second data cache list, the processor is configured to call the program code in the memory, and perform part or all of the process of the third aspect, wherein the cache device may be a base station, a local gateway, and the base station is connected to the base station through the local gateway.
  • a cache server or a cache server that is deployed independently in a mobile network.
  • the embodiment of the present invention further provides a communication system, including: a user terminal, a base station, and a cache device;
  • the user terminal is configured to send a request data packet, where the request data packet is used to request target data from a source server;
  • the base station is configured to receive a request data packet sent by the user terminal, and determine, according to the first data cache list, whether the information of the request data packet matches the information in the first data cache list, and if yes, the target Data is sent to the user terminal;
  • the cache device is configured to store the target data.
  • the base station includes any one of the foregoing, the seventh aspect, or the tenth aspect, wherein the cache device includes any one of the foregoing fifth aspect, the eighth aspect, or the eleventh aspect. Cache device.
  • the embodiment of the present invention further provides a communication system, including: a user terminal and a cache device; wherein
  • the user terminal is configured to generate a third request data packet, where the third request data packet is used to request target data from the source server, and determine, according to the second data cache list, whether the information of the third request data packet is The information in the two data cache lists is matched, and if so, the fourth request data packet is generated, wherein the second data cache list includes at least one information, and a correspondence between the information and an address of the cache device;
  • the destination address of the four request data packet is the address of the cache device corresponding to the matched information; the fourth request data packet is used to request the target data from the cache device, and send the fourth request to the cache device data pack;
  • the cache device is configured to receive the fourth request data packet, and send the target data to a user terminal;
  • the user terminal is further configured to receive the target data.
  • the user terminal includes any of the user terminals described in the foregoing sixth aspect, the ninth aspect, or the twelfth aspect;
  • the cache device includes the foregoing fifth aspect, the fifth aspect, the first to the second implementation manner.
  • the fourth implementation manner of the fifth aspect, the fifth implementation manner of the fifth aspect, the eighth aspect, the first to the second implementation manner of the eighth aspect, the fourth implementation manner of the eighth aspect, and the fifth implementation manner of the eighth aspect A cache device according to any one of the first to the second implementations of the eleventh aspect, the fourth implementation manner of the eleventh aspect, or the fifth implementation manner of the eleventh aspect.
  • FIG. 1 is a schematic structural diagram of a communication system according to an embodiment of the present invention.
  • FIG. 2 is a schematic flowchart of a method for acquiring cache data according to an embodiment of the present invention
  • FIG. 3 is a schematic flowchart of a first manner in which a base station according to the present invention sends target data to a user terminal;
  • FIG. 4 is a schematic flowchart of a second manner in which a base station according to the present invention sends target data to a user terminal;
  • FIG. 5 is a schematic flowchart of another method for acquiring cache data according to an embodiment of the present disclosure
  • FIG. 6 is a schematic structural diagram of a base station according to an embodiment of the present disclosure.
  • FIG. 7 is a schematic structural diagram of another base station according to an embodiment of the present disclosure.
  • FIG. 8 is a schematic structural diagram of a cache device according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram of another cache device according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram of a user terminal according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic structural diagram of another user terminal according to an embodiment of the present disclosure.
  • FIG. 12 is a schematic structural diagram of still another base station according to an embodiment of the present disclosure.
  • FIG. 13 is a schematic structural diagram of still another cache device according to an embodiment of the present disclosure.
  • FIG. 14 is a schematic structural diagram of still another user terminal according to an embodiment of the present invention.
  • the cache data acquisition method described in the following embodiments may be applied to various communication systems, for example, Global System of Mobile Communication (GSM), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), General Packet Radio Service (GPRS), Long Term Evolution (LTE), and the like.
  • GSM Global System of Mobile Communication
  • CDMA Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • the user terminal may be a terminal having a communication function such as a smart phone (English: smart phone) or a tablet computer (English: tablet computer), which is not limited by the present invention.
  • the base station may be a base station (BTS, Base Transceiver Station) in GSM or CDMA, or may be a base station (NodeB) in WCDMA or an evolved base station (eNB or in LTE)
  • BTS Base Transceiver Station
  • NodeB base station
  • eNB evolved base station
  • the e-NodeB, evolutional Node B may also be, a future communication system, such as a network device (such as a controller) in the 5G, which is not limited by the present invention.
  • UE User equipment
  • mobile phone English: cellphone
  • smart phone English: smart phone
  • computer English: computer
  • tablet English: tablet computer
  • mobile Internet device English: mobile Internet devices, MIDs, and devices such as wearable devices that can access the network through base stations.
  • the cache device has a data cache function as a device or device for storing data of the source server, and the cache device is a base station, a local gateway (LGW), and a cache server connected to the base station through the local gateway. Or a cache server or the like that is independently deployed in a mobile network.
  • LGW local gateway
  • cache server or the like that is independently deployed in a mobile network.
  • the source server (English: Over The Top sever, also known as OTT Sever) provides a third-party server (Over The Top Server) that provides application services to user terminals via the Internet, or may be an operator's content provider (Content Provide Server).
  • the source server is used to release the target data in the embodiments of the present invention, and may also be used to configure the first data cache list in the base station according to the embodiment of the present invention or the second data in the user terminal according to the embodiment of the present invention. Cache list.
  • FIG. 1 is a schematic structural diagram of a communication system according to an embodiment of the present invention.
  • the communication system includes a user terminal 11, a base station 12, and a cache device.
  • the cache device of the present invention may be the base station 12 or the local gateway 13, or may be a cache server 14 connected to the base station 12 through the local gateway 13 or independently deployed on the The cache server 14 in the mobile network.
  • the cache server 14 in the mobile network.
  • the system may also include a PDN gateway (English: Public Data Network GateWay, also known as PDN GateWay, PGW for short) 15, a service gateway (English: Serving GateWay, SGW) 15, a source server 16, and the like.
  • a PDN gateway English: Public Data Network GateWay, also known as PDN GateWay, PGW for short
  • a service gateway English: Serving GateWay, SGW
  • FIG. 1 depicts a user terminal 11, a base station 12, a local gateway 13, a PGW/SGW 15, and a source server 16
  • the communication system may include a different number of user terminals 11, base stations 12, local gateways 13, and cache servers. 14.
  • the base station 11 can establish two bearers, namely, the S1 bearer, that is, the first bearer and the S2 bearer, that is, the second bearer, and the object carried by the S1 is the LGW, and the S1 bearer is used to carry the user terminal 11 and the local gateway 13 or the cache server 14 Data transmission; S2 carries the object SGW/PGW15, The S2 bearer is used to carry data transmission between the user terminal 11 and the source server 16.
  • the base station 11 establishes a one-to-one correspondence between the two radio bearers and the S1 bearer and the S2 bearer by creating two radio bearers respectively, which are bound to the S1 bearer and the S2 bearer.
  • FIG. 2 is a schematic flowchart of a method for acquiring cache data according to an embodiment of the present invention.
  • the cache data acquisition method includes the following steps:
  • Step S210 The user terminal sends a request data packet, where the request data packet is used to request target data from the source server.
  • the user terminal may send an uplink data packet to the source server through an application, such as a browser, a video software, a music software, or the like, requesting acquisition of the target data.
  • the request packet may include a source address, a target address, and an identifier of the target data.
  • the source address is the address of the user terminal, for example, the IP address of the user terminal (English: Internet Protocol Address), the MAC address of the user terminal (English: Media Access Control or Medium Access Control) address, and the destination address is the address of the source server.
  • the port number of the source server may be the IP address of the source server or the MAC address of the source server.
  • the identifier of the target data may be a Uniform Resource Locator (URL) of the target data.
  • the data packet is an Http Get request, and the user terminal requests the source server, for example, the first video website, to acquire target data, such as the first movie.
  • Step S220 The base station receives the request data packet sent by the user terminal, and determines, according to the first data cache list, whether the information of the request data packet matches the information in the first data cache list.
  • the base station is configured with a first data cache list, where the first data cache list includes at least one of the following information: an address of the server, an identifier of the data, and an address of the server is used to indicate a source of data that the base station can cache.
  • the address information of the source server may be an IP address and a port number of the server.
  • the first data cache list includes an IP address and a port number of the first video website, and the cache device (such as a base station, a local gateway, and a cache server)
  • the data of the first video website can be cached; the address of the server can also be the MAC address and port number of the server.
  • the IP address of the server can also be replaced with information that can correspond to the IP address of the server or the MAC address of the server, such as the name and domain name of the server.
  • the information may further include an identifier of the data, such as a URL, used to indicate the number of source servers that the base station can cache.
  • the first data cache list includes an IP address of the first video website and a URL of the first video, a URL of the second video, and a URL of the third video under the IP address of the first video website, then the cache device The first video, the second video, and the third video in the first video website may be cached, and the fourth video in the first video website may not be cached. It can be understood that the first data cache list may be actively pushed by the source server to the base station, or may be requested by the base station to obtain the source server, which is not limited by the present invention.
  • the first data cache list may be configured by the source server, or may be configured by the operator through the HPLMN (Home Public Land Mobile Network).
  • the base station may cache the plurality of data that meet the cache condition in the cache device in the base station according to the number of data requests.
  • the first data cache list may include the address of the source server that satisfies the plurality of data of the cache condition and/or Or the URL of multiple data that satisfies the cache condition. It can be set that the data whose request times are greater than the preset number of times, for example, 100 times, satisfies the cache condition.
  • the base station parses the request data packet, and determines, according to the first data cache list, whether the target address of the request data packet matches the address information in the first data cache list. If yes, the information of the request packet matches the information in the first data cache list. For example, when the first data cache list includes the address and port number of the server, the base station may determine whether the first data cache list is consistent with the target address of the request packet (ie, the address and port number of the source server) or The address and port number of the corresponding server. It can be understood that the MAC address of the server corresponds to the IP address of the unique server. If yes, the destination address of the request packet matches the address information in the first data cache list.
  • the base station may determine whether the destination address of the request packet exists in the first data cache list (ie, the address and port number of the source server). The domain name and port number of the corresponding server. If yes, the destination address of the request packet matches the address information in the first data cache list, otherwise it does not match.
  • step S220 further includes: determining, by the base station, whether there is an identifier of the data in the first data cache list that is consistent with the identifier of the target data, when the target address of the request packet Matching with the address information in the first data cache list, and the identifier of the data of the request data packet matches the information in the first data cache list when there is an identifier of the data in the first data cache list that is consistent with the identifier of the target data.
  • the cache device may cache the target data, and step S230 is performed; otherwise, the cache device may not cache the target data, and the base station may perform step S240, that is, the base station will perform
  • the request data packet is sent to the source server, so that the source server sends the target data to the user terminal after receiving the request data packet.
  • the cache device can be a base station, a local gateway, a cache server connected to the base station through the local gateway, or a cache server independently deployed in the mobile network.
  • Step S230 The base station sends the target data to the user terminal.
  • the base station sends the target data stored in the cache device to the user terminal, where the cache device may be the base station itself, or may be a local gateway, a cache server connected to the base station through the local gateway, or independently deployed on the mobile network. In the cache server, etc.
  • the cache device is a base station, and the base station may have a saved data list, where the saved data list may include at least one identifier of the saved data, such as a URL of the data.
  • the save data list includes the URL of the first movie and the URL of the second movie.
  • FIG. 3 is a schematic flowchart of a first manner in which a base station according to the present invention sends target data to a user terminal.
  • the first possible implementation manner of step S230 may specifically include:
  • Step S23101 The base station determines whether the target data has been cached.
  • the base station parses the URL of the target data included in the request packet, and determines whether the URL of the target data is included in the saved data list, and if yes, the target data is cached in the base station.
  • Step S23102 may be performed. Otherwise, it is explained that the target data is not buffered in the base station, step S23103 to step S23105 may be performed, or steps S23106 to S23109 may be performed.
  • Step S23102 The base station sends the target data to the user terminal.
  • the method of step S23102 may include: the base station encapsulates the target data into a response data packet; wherein, a source address of the response data packet is a target address of the request data packet; and the response data is further The packet is sent to the user terminal.
  • the steps S23105-S23110 are the first implementation manner of the base station sending the target data to the user terminal when the target data is not cached according to the embodiment of the present invention, including:
  • Step S23103 The base station sends the request data packet to the source server.
  • step S23103 may be performed.
  • Step S23104 The source server receives the request data packet.
  • Step S23105 The source server sends the target data to the user terminal.
  • the step S23105 may further include: when the base station detects the target data that is sent by the source server to the user terminal, the base station may save the target data to the cache device.
  • the second implementation manner of the base station sending the target data to the user terminal when the target data is not cached includes: the base station generates a first request data packet, where a source address of the first request data packet is an address of the cache device (for example, The IP address of the cache device, the MAC address of the cache device, etc., and the destination address is the address of the source server (for example, the IP address of the source server, the MAC address of the source server, etc.), and is used to request target data from the source server;
  • the base station sends the first request data packet to the source server, and after receiving the first request data packet, the source server sends the target data to the cache device, and the cache device sends the target data to the user terminal.
  • the steps S23106-S23110 are a third implementation manner in which the base station sends the target data to the user terminal when the target data is not cached according to the embodiment of the present invention, including:
  • Step S23106 the base station sends a second request data packet to the source server, where the second request data packet is used by the base station to request the target data from the source server, where the source address of the second request data packet is a base station Address, the destination address is the address of the source server.
  • step S23106 may be performed.
  • the source address of the second request data packet is an address of the base station (for example, a MAC address of the base station, a base station IP address, and the like)
  • the target address is a target address of the request data packet
  • the second request data packet includes an identifier of the target data.
  • Step S23107 The source server is receiving the second request data packet.
  • Step S23108 The source server returns the target data to the base station.
  • Step S23109 The base station receives the target data returned from the source server.
  • Step S23110 The base station sends the target data to the user terminal.
  • the base station may further save the target data.
  • Step S23111 The user terminal receives the target data.
  • the user terminal can receive the target data.
  • the cache device may be a local gateway, a cache server connected to the base station through the local gateway, or a cache server independently deployed in the mobile network, and a cache device (cache server or local gateway)
  • a cache device cache server or local gateway
  • the save data list includes the URL of the first movie and the URL of the second movie.
  • FIG. 4 is a schematic flowchart of a second manner in which a base station according to the present invention sends target data to a user terminal.
  • the second possible implementation manner of step S230 may specifically include:
  • Step S23201 The base station sends the request data packet to a cache device.
  • the base station may establish a first bearer with the cache device in advance for carrying data transmission between the user terminal and the cache device, and establish a second bearer with the source server for carrying between the user terminal and the source server. data transmission.
  • the first bearer established by the base station and the cache device may be controlled by a local gateway or a base station, or may be controlled by a Mobility Management Entity (MME) deployed in the mobile network.
  • MME Mobility Management Entity
  • Step S23202 The cache device receives the request data packet sent by the base station.
  • Step S23203 The cache device determines whether the target data has been cached.
  • the cache device may determine whether the identifier of the target data is included in the saved data list, and if yes, the cache device determines that the target data has been cached, and may perform step S23204; otherwise, perform step S23205 to step S23207, step S23208 to step S23212. Or step S23213 to step S23219.
  • Step S23204 The cache device sends the target data to the user terminal.
  • step S23204 may include: the cache device encapsulates the target data into a response data packet; a source address of the response data packet is a target address of the request data packet; and sending the response data packet To the user terminal.
  • the steps S23205-S23207 are the fourth implementation manner of the base station sending the target data to the user terminal when the target data is not cached according to the embodiment of the present invention, including:
  • Step S23205 The cache device sends the request data packet to the source server.
  • step S23205 may be performed.
  • Step S23206 The source server receives the request data packet.
  • Step S23207 The source server sends the target data to the user terminal.
  • the step S23207 may further include: when the base station detects the target data that is sent by the source server to the user terminal, the base station may send the target data to the cache device, and the cache device may receive and save the Target data and send the target data to the user terminal.
  • the steps S23208-S23212 are the fifth implementation manner of the base station sending the target data to the user terminal when the target data is not cached according to the embodiment of the present invention, including:
  • Step S23208 The cache device sends a first request data packet to the source server, where the first request data packet is used to request the target data from the source server.
  • the step may be performed.
  • the source address of the first request packet is an address of the cache device (for example, a MAC address of the cache device, an IP address of the cache device, and the like), and the target address is a target address of the request packet, and the first request data is
  • the package includes an identification of the target data.
  • Step S23209 The source server receives the first request data packet.
  • Step S23210 The source server sends the target data to the cache device.
  • Step S23211 The cache device receives the target data sent from the source server.
  • Step S23212 The cache device sends the target data to the user terminal.
  • the cache device may further save the target data.
  • the steps S23213-S23219 are the sixth implementation manner of the base station transmitting the target data to the user terminal when the target data is not cached according to the embodiment of the present invention, including:
  • Step S23213 The cache device sends a signaling message to the base station.
  • the cache device (such as a local gateway and a cache service connected to the base station through the local gateway) Or a cache server independently deployed in the mobile network) may generate a signaling message according to the data packet, the signaling message is used to instruct the base station to request target data from the source server, and receive the received data at the base station After the target data is described, the target data is sent to the user terminal.
  • the signaling message includes an address of the user terminal (such as a MAC address of the user terminal, an IP address of the user terminal, etc.), an identifier of the target data, and a target address of the request packet.
  • Step S23214 The base station is receiving the signaling message.
  • Step S23215 The base station sends a second request data packet to the source server, where the second request data packet is used to request the target data from the source server.
  • the base station may generate a second request data packet according to the signaling message, where the source address of the second request data packet is an address of the base station (for example, a MAC address of the base station, an IP address of the base station, etc.), and the target address is the request data.
  • the destination address of the package which is the address of the source server.
  • the second request packet includes an identification of the target data.
  • Step S23216 The source server receives the second request data packet.
  • Step S23217 The source server sends the target data to the base station.
  • Step S23218 The base station receives the target data returned from the source server
  • Step S23219 The base station sends the target data to the user terminal.
  • the step S23219 may further include: when the base station detects the target data that is sent by the source server to the user terminal, the base station may send the target data to the cache device, where the cache device may save the target data. .
  • Step S23220 The user terminal receives the target data.
  • step S23220 may be performed after step S23204, step S23207, step S23212 or step S23219.
  • Step S240 The base station sends the request data packet to the source server.
  • step S220 when the result of the determination in step S220 is YES, that is, the target address of the request packet does not match the address information in the first data cache list, the target data is data that the cache device cannot cache, and can be executed. Step S240 to step S260.
  • Step S250 The source server receives the request data packet.
  • Step S260 The source server sends the target data to the user terminal.
  • Step S270 The user terminal receives the target data.
  • the request data packet after receiving the request data packet sent by the user terminal, the request data packet is used by the user terminal to request target data from the source server, and the base station determines, according to the first data cache list, whether the information of the request data packet is the first The information in the data cache list matches, and if so, the target data stored in the cache device is sent to the user terminal.
  • a cache device such as a base station, a local gateway, or a cache server
  • the overhead on the link thereby improving the response speed of the user terminal requesting data and improving the user experience.
  • FIG. 5 is another schematic flowchart of a method for acquiring cache data according to an embodiment of the present invention.
  • the cache data acquisition method includes:
  • Step S510 The user terminal generates a third request data packet, where the third request data packet is used to request target data from the source server.
  • the user terminal may send an uplink data packet, that is, a third request data packet, to the source server through an application, such as a browser, a video software, a music software, or the like, requesting acquisition of the target data.
  • the third request data packet may be triggered by the user terminal after detecting the data acquisition operation for the identifier or the link of the target data in the application, or may be triggered when the application detects that the data needs to be updated.
  • the data acquisition operation may be a click operation, a double click operation, a drag operation, or the like for the identification or link of the target data.
  • the third request packet includes a source address, a target address, and an identifier of the target data.
  • the source address is the address of the user terminal, for example, the IP address and MAC address of the user terminal;
  • the target address is the address of the source server, for example, the IP address of the source server; and the identifier of the target data may be the URL of the target data.
  • the third request data packet is an Http Get request, and the user terminal requests the source server, for example, the first video website, to acquire target data, such as the first movie.
  • Step S520 The user terminal determines, according to the second data cache list, whether the information of the third request data packet matches the information in the second data cache list.
  • the user terminal may configure or acquire a second data cache list, where the second data cache list includes at least one information, and a correspondence between the information and an address of the cache device, where the information includes an address of the server and/or The identification of the data.
  • the address of the cache device may be the IP address and port number of the cache device, or the MAC address and port number of the cache device.
  • Server The address can be the IP address and port number of the source server, the MAC address and port number of the server, or the name, domain name, etc. of the server that can correspond to the IP address of the source server or the MAC address of the server.
  • the address of the server is used to indicate the source server from which the data that the base station can be cached.
  • the second data cache list includes the IP address of the first video website, and the base station can cache the data of the first video website.
  • the information may further include a URL of the data, used to indicate data in the source server that the base station can cache, for example, the second data cache list includes an IP address of the first video website and the first video website.
  • the URL of the first video, the URL of the first video, and the URL of the third video in the IP address the base station may cache the first video, the first video, and the third video in the first video website, but may not cache the first video.
  • the address and port number of the cache device are used to indicate the address information of the cache device to implement a TCP communication connection between the user terminal and the cache device.
  • the information included in the second data cache list has a corresponding relationship with the address of the cache device.
  • the IP address of the first video website corresponds to the IP address and port number of the first cache device
  • the IP address of the second video website corresponds to the second cache. IP address and port number of the device.
  • the multiple information may be corresponding to the address of the same cache device; the second data cache list is provided by the OTT service provider, and the address and port number of the cache device are provided by the operator, and the address of the cache device may be broadcasted by the base station. User terminal.
  • the user terminal determines, according to the second data cache list, whether the target address of the third request data packet matches the address information in the second data cache list, and if yes, the information of the third request data packet and the third The information in the second data cache list matches. For example, when the second data cache list includes the address and the port number of the server, the user terminal may determine whether the target address of the third request data packet exists in the second data cache list (ie, the address and port number of the source server).
  • the address or port number of the server that is consistent or corresponding, it can be understood that the MAC address of the server corresponds to the IP address of the unique server, and if so, the destination address of the third request packet and the address in the second data cache list
  • the information matches, otherwise it does not match; for example, when the second data cache list includes the domain name and port number of the server, the user terminal can determine whether there is a target address of the third request packet in the second data cache list (ie, The address and port number of the source server correspond to the domain name and port number of the server. If yes, the destination address of the request packet matches the address information in the first data cache list, otherwise it does not match.
  • step S520 further includes the user terminal determining the second data. Whether there is an identifier of the data in the cache list that is consistent with the identifier of the target data, when the target address of the third request packet matches the address information in the first data cache list, and the second data cache list exists and the target When the identification of the data is consistent with the identification of the data, the information of the third request packet matches the information in the first data cache list.
  • the target data is data that the cache device can cache, and step S530 may be performed to obtain the target data from the cache device; otherwise, The target data is not data that can be cached by the cache device, and steps S560 to S590 can be performed.
  • the user terminal may obtain the second data cache list, where the second data cache list includes at least one information, and a correspondence between the information and an address of the cache device;
  • the information includes the address of the server and/or the identity of the data.
  • the cache device can be a local gateway, a cache server connected to the base station through the local gateway, or a cache server independently deployed in the mobile network. It can be understood that the cache device in the embodiment of the present invention can be replaced by a base station, a local gateway, or a cache server.
  • Step S530 The user terminal generates a fourth request data packet, where a target address of the fourth request data packet is an address of a cache device corresponding to the matched information, and the fourth request data packet is used to request the cache device.
  • the target data is an address of a cache device corresponding to the matched information.
  • the user terminal may search, according to the correspondence between the information in the second data cache list and the address of the cache device, the cache device corresponding to the information (for example, the address of the server) that matches the target address of the third request packet.
  • the address, and further the address of the third request packet is modified to be the address of the cache device corresponding to the address of the matched server, and the fourth request packet is generated.
  • the source address of the fourth request data packet is an address of the user terminal, and the destination address is an address of the cache device corresponding to the matched information, and the fourth request data packet includes an identifier of the target data, and is used to request the target data from the cache device. .
  • Step S540 The user terminal sends the fourth request data packet to the cache device.
  • the user terminal sends a fourth request data packet to the cache device corresponding to the matched information.
  • Step S550 The cache device receives the fourth request data packet, and sends the target data to the user terminal.
  • the cache device may configure a save data list, and the save data list may include at least one identifier of the saved data, such as The URL of the data.
  • the save data list includes the URL of the first movie and the URL of the second movie.
  • the cache device may determine whether the target data is included in the saved data list, and if yes, the target data is cached in the cache device, and the cache device responds to the fourth request data packet, and is stored in the cache device. The target data corresponding to the identifier of the target data is sent to the user terminal. Otherwise, the target data is not cached in the cache device, and the cache device may request the source server to acquire the target data.
  • an implementation manner that the cache device may request the source server to obtain the target data may be: the cache device sends the first request data packet to the source server, where the first request data packet is used to the source server. Requesting the target data, the target address of the first request data packet is an address of the source server, the source address is an address of the cache device (such as a MAC address of the cache device, an IP address, and the like); the source server receives the first address Requesting a data packet, and in response to the first request data packet, returning the target data to the cache device; the cache device receiving the target data and transmitting the target data to the user terminal.
  • the cache device may further save the target data, and the corresponding relationship of the target data of the target data. It can be understood that the cache device can be a base station, a local gateway or a cache server.
  • the cache device may send a signaling message to the base station, where the signaling message is used. Instructing the base station to request target data from the source server, and after the base station receives the target data, sending the target data to the user terminal or to the cache device; a signaling message, generating a second request data packet according to the signaling message, and sending a second request data packet to the source server, where the second request data packet is used to request the target data from the source server; Receiving, by the source server, the second request data packet, and transmitting the target data to the base station in response to the second request data packet, the base station receiving the target data returned from the source server, and Sending the target data to the user terminal or the cache device. After the cache device receives the target data, the cache device may save the target data, and the corresponding relationship of the target data of the target data, and send the target data to the
  • the third request data packet may carry the source server address of the target data, so that the cache device can obtain the target address of the third request data packet, that is, the address of the source server, generate the first request data packet, and Signaling message.
  • the signaling message may carry the source server address of the target data and the identifier of the target data, so that the base station can generate the second request packet after obtaining the target address of the second request packet.
  • the cache device may also send a source address request to the user terminal to request the address of the source server of the target data, which is not limited by the present invention.
  • Step S560 The user terminal sends the third request data packet.
  • step S520 when the determination result of step S520 is NO, that is, when the address of the server in the second data cache list does not include the target address of the third request data packet, the user terminal may send the third request data packet to the source server.
  • Step S570 The source server receives the third request data packet.
  • Step S580 The source server sends the target data.
  • the source server after receiving the third request data packet sent by the user terminal, the source server sends the target data to the user terminal in response to the third request data packet.
  • Step S590 The user terminal receives the target data.
  • the user terminal is provided with a second data cache list, the second data cache list including at least one information, and a correspondence between the information and an address of the cache device, when the user terminal receives the After requesting the third request packet of the target data from the source server, the user terminal determines, according to the second data cache list, whether the information of the third request packet matches the information in the second data cache list, and if yes, indicates the target
  • the data is data that can be cached by the cache device, and the user terminal modifies the target address of the third request packet to the address of the cache device corresponding to the matched information, and generates a fourth request packet for requesting the target data from the cache device.
  • FIG. 6 is a schematic structural diagram of a base station according to an embodiment of the present invention, as shown in FIG. 6.
  • the base station includes:
  • the receiving module 610 is configured to receive a request data packet sent by the user terminal, where the request data packet is used to request target data from the source server.
  • the processing module 620 is configured to determine, according to the pre-stored first data cache list, whether the information of the request data packet matches the information in the first data cache list;
  • the sending module 630 is configured to send the target data to the user terminal when the information of the request data packet matches the information in the first data cache list.
  • the processing module 620 is further configured to: obtain a first data cache list, where the first data cache list includes at least one of the following information:
  • the sending module 630 is further configured to: when the information of the request data packet matches the information in the first data cache list, use the first bearer established with the cache device to target the target Data is sent to the user terminal.
  • the sending module 630 is further configured to: when the information of the request data packet does not match the information in the first data cache list, by using a second bearer established with the source server, The target data is sent to the user terminal.
  • the processing module 620 is further configured to: determine whether the target data has been cached, and when the target data has been cached, trigger the sending module to send the target data to the user terminal.
  • the processing module 620 is further configured to: encapsulate the target data into a response data packet; a source address of the response data packet is a target address of the request data packet;
  • the sending module 630 is further configured to: send the response data packet to the user terminal.
  • the sending module 630 is further configured to: when the target data is not cached, send the request data packet to the source server, so that after the source server receives the request data packet, the source server Sending the target data to the user terminal.
  • the processing module 620 is further configured to: when the target data is not cached, generate a first request data packet, where a source address of the first request data packet is an address of a cache device, The source server requests target data;
  • the sending module 630 is further configured to: send the first request data packet to the source server, After the source server receives the first request data packet, sending the target data to the cache device.
  • the receiving module 610 is further configured to: when the target data is not cached, receive a signaling message sent by the cache device;
  • the processing module 620 is further configured to: generate a second request data packet according to the signaling message, where the second request data packet is used to request the target data from the source server;
  • the sending module 630 is further configured to: send the second request data packet to the source server, so that the source server returns the target data after receiving the second request data packet;
  • the receiving module 610 is further configured to: receive the target data returned by the source server;
  • the sending module 630 is further configured to: send the target data to the user terminal.
  • the processing module 620 is further configured to: determine whether the cache device includes the target data, where the cache device is a local gateway, and the cache server connected to the base station by using the local gateway Or independently deployed to a cache server in the mobile network;
  • the sending module 630 is further configured to: when the cache device has cached the target data, send a data request to the cache device, so that the cache device, after receiving the data request, The data is sent to the user terminal.
  • the sending module 630 is further configured to: send an address of the cache device to the user terminal.
  • modules in the base station in the embodiments of the present invention may be specifically implemented according to the method in the method embodiment shown in FIG. 2, and the specific implementation process may refer to the method embodiment described in FIG. 2 above. The related description is not repeated here.
  • the request data packet after receiving the request data packet sent by the user terminal, the request data packet is used by the user terminal to request target data from the source server, and the base station determines, according to the first data cache list, the request data packet. Whether the information matches the information in the first data cache list, and if so, the target data stored in the cache device is transmitted to the user terminal.
  • a cache device such as a base station, a local gateway, or a cache server
  • the overhead on the link thereby improving the response speed of the user terminal requesting data and improving the user experience.
  • FIG. 7 is a schematic structural diagram of another base station according to an embodiment of the present invention.
  • the base station includes a processor 71, a memory 72, and a communication interface 73.
  • the processor 71 is coupled to a memory 72 and a communication interface 73, for example, the processor 71 can be coupled to the memory 72 and the communication interface 73 via a bus.
  • the processor 71 is configured to support the base station to perform a corresponding function in the cache data acquisition method illustrated in FIG. 2.
  • the processor 71 can be a central processing unit (CPU), a network processor (in English: network processor, NP), a hardware chip, or any combination thereof.
  • the hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof.
  • ASIC application-specific integrated circuit
  • PLD programmable logic device
  • the above PLD can be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), and a general array logic (GAL). Or any combination thereof.
  • the memory 72 is used to store target data, a first data cache list, program code, and the like in the cache data acquisition method shown in FIG. 2.
  • the memory 72 may include a volatile memory (English: volatile memory), such as a random access memory (English: random access memory, abbreviation: RAM); the memory 72 may also include a non-volatile memory (English: non-volatile memory) For example, read-only memory (English: read-only memory, abbreviation: ROM), flash memory (English: flash memory), hard disk (English: hard disk drive, abbreviation: HDD) or solid state drive (English: solid-state drive , abbreviation: SSD); the memory 72 may also include a combination of the above types of memory.
  • the communication interface 73 is configured to communicate with a device such as a user terminal, a local gateway, a cache server, or a source server to transmit and receive messages involved in the above method.
  • the processor 71 can invoke the program code to perform the following operations:
  • the request data packet is used to request target data from the source server;
  • the target data is transmitted to the user terminal through the communication interface 73.
  • the processor 71 is further configured to: before the processor 71 determines, according to the first data cache list, whether the information of the request data packet matches the information in the first data cache list, the processor 71 is further configured to:
  • the first data cache list includes at least one of the following information:
  • the sending the target data to the user terminal through the communication interface 73 includes: establishing, by using the cache device The first bearer transmits the target data to the user terminal through the communication interface 73.
  • the processor 71 is further configured to: when the information of the request data packet does not match the information in the first data cache list, pass the communication interface through the second bearer established with the source server 73 transmitting the target data to the user terminal.
  • the processor 71 before the processor 71 sends the target data to the user terminal through the communication interface 73, the processor 71 is further configured to:
  • the step of transmitting the target data to the user terminal via the communication interface 73 is performed.
  • the sending, by the processor 71, the target data to the user terminal by using the communication interface 73 includes:
  • a source address of the response data packet is a target address of the request data packet
  • the response data packet is transmitted to the user terminal via the communication interface 73.
  • the processor 71 is further configured to: when the target data is not cached, send the request data packet to the source server through the communication interface 73, so that the source server receives the request data. After the packet, the source server sends the target data to the user terminal.
  • the processor 71 is further configured to: when the target data is not cached, generate a first request data packet, where a source address of the first request data packet is an address of a cache device, and is used to send the source The server requests target data;
  • the processor 71 is further configured to: when the target data is not cached, receive the signaling message sent by the cache device through the communication interface 73;
  • the target data returned by the source server is received through the communication interface 73, and the target data is transmitted to the user terminal through the communication interface 73.
  • the processor 71 determines whether the target data has been cached, including:
  • the cache device Determining whether the cache device has cached the target data, where the cache device is a local gateway, a cache server connected to the base station through a local gateway, or a cache server independently deployed in the mobile network;
  • the sending the target data to the user terminal through the communication interface 73 includes: transmitting a data request to the cache device through the communication interface 73 to enable the cache After receiving the data request, the device sends the target data to the user terminal.
  • the processor 71 is further configured to: send, by using the communication interface 73, an address of the cache device to the user terminal.
  • FIG. 8 is a schematic structural diagram of a cache device according to an embodiment of the present invention. As shown in FIG. 8, the cache device includes:
  • the receiving module 810 is configured to receive a request data packet sent by the user terminal, where the request data packet is sent to the base station by the user terminal, for requesting target data, and when the base station receives the request data packet, When the base station determines that the information of the request data packet matches the information in the first data cache list or the target address of the request data packet is the address of the cache device, The base station sends the request data packet to the cache device;
  • the sending module 820 is configured to send the target data to the user terminal.
  • the request packet is the third request packet in the method embodiment described in FIG.
  • the cache device further includes: a processing module, configured to determine that the target data has been cached; and when the target data has been cached, triggering the sending module 820 to send the target data to the user terminal.
  • a processing module configured to determine that the target data has been cached; and when the target data has been cached, triggering the sending module 820 to send the target data to the user terminal.
  • the processing module is further configured to: encapsulate the target data into a response data packet; a source address of the response data packet is a target address of the request data packet;
  • the sending module 820 is further configured to: send the response data packet to the user terminal.
  • the sending module 820 is further configured to: when the base station determines that the information of the request data packet matches the information in the first data cache list, and does not cache the target data, to the source The server sends the request data packet, so that after the source server receives the request data packet, the source server sends the target data to the user terminal.
  • the sending module 820 is further configured to: when the target data is not cached, send the first request data packet to the source server, so that the source server receives the first request data packet. After the source server returns the target data, the first request data packet is used to request the target data from the source server;
  • the receiving module 810 is further configured to: receive the target data returned from the source server;
  • the sending module 820 is further configured to: send the target data to the user terminal.
  • the sending module 820 is further configured to: when the target data is not buffered, send a signaling message to the base station, so that after the base station receives the signaling message, the base station sends the The source server sends a second request data packet, where the second request data packet is used by the base station to request the target data from the source server; and the base station receives the target data returned from the source server, And transmitting the target data to the user terminal.
  • modules in the cache device in the embodiments of the present invention may be specifically implemented according to the method in the method embodiment shown in FIG. 2 or FIG. 5, and the specific implementation process may refer to FIG. 2 or FIG. The related description of the method embodiment is not described here.
  • the cache device receives the request packet sent by the user terminal, The request data packet is sent to the base station for the user terminal to request the target data; when the base station receives the request data packet, and the base station determines that the information of the request data packet matches the information in the first data cache list, or When the destination address of the request packet is the address of the cache device, the base station sends the request packet to the cache device, and the cache device sends the target data to the user terminal, by sinking the data of the source server to the mobile network.
  • a cache device (base station, local gateway, cache server connected to the base station through the local gateway or a cache server independently deployed in the mobile network), so that the user can directly obtain the target data from the cache device, thereby avoiding The overhead on the backhaul link of the wireless network to the core network, thereby improving the response speed of the user terminal requesting data and improving the user experience.
  • FIG. 9 is a schematic structural diagram of another cache device according to an embodiment of the present invention.
  • the cache device includes a processor 91, a memory 92, and a communication interface 93.
  • the processor 91 is connected to a memory 92 and a communication interface 93, for example, the processor 91 can be connected to the memory 92 and the communication interface 93 via a bus.
  • the processor 91 is configured to support the cache device to perform the corresponding function in the cache data acquisition method shown in FIG. 2 or FIG. 5.
  • the processor 91 can be a central processing unit (CPU), a network processor (in English), a hardware chip, or any combination thereof.
  • the hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof.
  • ASIC application-specific integrated circuit
  • PLD programmable logic device
  • the above PLD can be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), and a general array logic (GAL). Or any combination thereof.
  • the memory 92 is used to store target data, program code, and the like in the cache data acquisition method shown in FIG. 2 or FIG. 5.
  • the memory 92 may include a volatile memory (English: volatile memory), such as random access memory (English: random access memory, abbreviation: RAM); the memory 92 may also include non-volatile memory (English: non-volatile memory) For example, read-only memory (English: read-only memory, abbreviation: ROM), flash memory (English: flash memory), hard disk (English: hard disk drive, abbreviation: HDD) or solid state hard disk (English: Solid-state drive, abbreviated: SSD); the memory 92 may also include a combination of the above types of memory.
  • the communication interface 93 is for communicating with a user terminal, a source server, etc. to transmit and receive messages involved in the above method.
  • the processor 91 can invoke the program code to perform the following operations:
  • a request data packet sent by the user terminal where the request data packet is sent to the base station by the user terminal for requesting target data; when the base station receives the request data packet, and the base station When the information of the request data packet is matched with the information in the first data cache list or the target address of the request data packet is the address of the cache device, the base station sends the request data packet to the cache device;
  • the target data is transmitted to the user terminal through the communication interface 93.
  • the request packet is the third request packet in the method embodiment described in FIG.
  • the sending, by the processor 91, the target data to the user terminal by using the communication interface 93 includes:
  • the target data is transmitted to the user terminal via the communication interface 93.
  • the sending, by the processor 91, the target data to the user terminal by using the communication interface 93 includes:
  • a source address of the response data packet is a target address of the request data packet
  • the response data packet is transmitted to the user terminal via the communication interface 93.
  • the processor 91 is further configured to:
  • the request data packet is sent to the source server through the communication interface 93, so that after the source server receives the request data packet, the source server sends the target data to the user terminal.
  • the processor 91 is further configured to:
  • the communication interface 93 Sending, by the communication interface 93, the first request data packet to the source server, so that after the source server receives the first request data packet, the source server returns the target data, the first request data a packet for requesting the target data from the source server;
  • the target data returned from the source server is received through the communication interface 93, and the target data is transmitted to the user terminal.
  • the processor 91 is further configured to:
  • the base station sends a second request data packet to the source server, where the second request data packet And configured to request the target data from the source server; the base station receives the target data returned from the source server, and sends the target data to the user terminal.
  • FIG. 10 is a schematic structural diagram of a user terminal according to an embodiment of the present invention. As shown in FIG. 10, the user terminal 1000 includes:
  • the processing module 1010 is configured to generate a third request data packet, where the third request data packet is used to request target data from the source server, and determine, according to the second data cache list, whether the information of the third request data packet is The information in the two data cache lists is matched; the second data cache list includes at least one information, and a correspondence between the information and an address of the cache device;
  • the processing module 1010 is further configured to: when the information of the third request data packet matches the information in the second data cache list, generate a fourth request data packet, where a target address of the fourth request data packet is The address of the cache device corresponding to the matched information; the fourth request data packet is used to request the target data from the cache device;
  • the sending module 1020 is configured to send the fourth request data packet to the cache device, so that the cache device sends the target data to the user terminal after receiving the fourth request data packet;
  • the receiving module 1030 is configured to receive the target data.
  • the sending module 1020 is further configured to: when the information of the third request data packet does not match the information in the second data cache list, send the third request data packet, so that the source After receiving the third request data packet, the server sends the target data to the user terminal;
  • the receiving module 1030 is further configured to: receive the target data.
  • processing module 1010 is further configured to:
  • the second data cache list includes at least one information, and a correspondence between the information and an address of the cache device; wherein the information includes an address of the server and/or an identifier of the data .
  • modules in the user terminal in the embodiments of the present invention may be specifically implemented according to the method in the method embodiment shown in FIG. 5, and the specific implementation process may be implemented by referring to the method described in FIG. The related description of the example is not described here.
  • the user terminal is configured with a second data cache list, the second data cache list includes at least one information, and a correspondence between the information and an address of the cache device, when the user terminal After receiving the third request data packet for requesting the target data from the source server, the user terminal determines, according to the second data cache list, whether the information of the third request data packet matches the information in the second data cache list, and if The target data is data cacheable by the cache device, and the user terminal modifies the target address of the third request packet to the address of the cache device corresponding to the matched information, and generates a fourth request for requesting the target data from the cache device.
  • a cache device such as a base station, a local gateway, or a cache server
  • Obtaining the target data avoids the overhead of the backhaul link from the wireless network to the core network, thereby improving the response speed of the user terminal requesting data and improving the user experience.
  • FIG. 11 is a schematic structural diagram of another user terminal according to an embodiment of the present invention.
  • the user terminal includes a processor 111, a memory 112, and a communication interface 113.
  • the processor 111 is connected to the memory 112 and the communication interface 113, for example, the processor 111 can be connected to the memory 112 and the communication interface 113 via a bus.
  • the processor 111 is configured to support the user terminal to perform a corresponding function in the cache data acquisition method illustrated in FIG. 5.
  • the processor 111 can be a central processing unit (CPU), a network processor (English: network processor, NP), a hardware chip, or any combination thereof.
  • the above hardware chip may be an application specific integrated circuit (English: application-specific Integrated circuit (ASIC), programmable logic device (PLD) or a combination thereof.
  • the above PLD can be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), and a general array logic (GAL). Or any combination thereof.
  • the memory 112 is used to store a second data cache list and program code and the like in the cache data acquisition method shown in FIG. 5.
  • the memory 112 may include a volatile memory (English: volatile memory), such as random access memory (English: random access memory, abbreviation: RAM); the memory 112 may also include non-volatile memory (English: non-volatile memory) For example, read-only memory (English: read-only memory, abbreviation: ROM), flash memory (English: flash memory), hard disk (English: hard disk drive, abbreviation: HDD) or solid state drive (English: solid-state drive , abbreviation: SSD); the memory 112 may also include a combination of the above types of memory.
  • the communication interface 113 is configured to communicate with a base station, a local gateway, a cache server, or a source server to transmit and receive messages involved in the above method.
  • the processor 111 can invoke the program code to perform the following operations:
  • the third request data packet is used to request target data from the source server;
  • the second data cache list includes at least one information, and the information and the cache device Correspondence of addresses;
  • the fourth request data packet is used to request the target data from the cache device;
  • the target data is received through the communication interface 113.
  • the processor 111 is also used to execute:
  • the target data is received through the communication interface 113.
  • the processor 111 determines whether the information of the third request packet matches the information in the second data cache list, the processor 111 is further configured to:
  • the second data cache list includes at least one information, and a correspondence between the information and an address of the cache device; wherein the information includes an address of the server and/or Or the identification of the data.
  • FIG. 12 is a schematic structural diagram of still another base station according to an embodiment of the present invention. As shown in FIG. 12, the base station includes:
  • the receiver 1210 is configured to receive a request data packet sent by the user terminal, where the request data packet is used to request target data from the source server.
  • the processor 1220 is configured to determine, according to the pre-stored first data cache list, whether the information of the request data packet matches the information in the first data cache list.
  • the sender 1230 is configured to send the target data to the user terminal when the information of the request data packet matches the information in the first data cache list.
  • the processor 1220 is further configured to: obtain a first data cache list, where the first data cache list includes at least one of the following information:
  • the sender 1230 is further configured to: when the information of the request data packet matches the information in the first data cache list, the first bearer established by the base station and the cache device, Sending the target data to the user terminal;
  • the sender 1230 is further configured to: when the information of the request data packet does not match the information in the first data cache list, the second bearer established by the base station and the source server And transmitting the target data to the user terminal.
  • the processor 1220 is further configured to: determine whether the target data has been cached, and when the target data has been cached, trigger the transmitter to send the target data to the user terminal.
  • the processor 1220 is further configured to: encapsulate the target data into a response data packet; a source address of the response data packet is a target address of the request data packet;
  • the transmitter 1220 is further configured to: send the response data packet to the user terminal.
  • the sender 1230 is further configured to: when the target data is not cached, send the request data packet to the source server, so that after the source server receives the request data packet, The source server transmits the target data to the user terminal.
  • the processor 1220 is further configured to: when the target data is not cached, generate a first request data packet, where a source address of the first request data packet is an address of a cache device, The source server requests target data;
  • the transmitter 1230 is further configured to: send the first request data packet to the source server, so that the source server sends the target data to the after receiving the first request data packet. Cache device.
  • the receiver 1210 is further configured to: when the target data is not cached, receive a signaling message sent by the cache device;
  • the processor 1220 is further configured to: generate a second request data packet according to the signaling message, where the second request data packet is used to request the target data from the source server;
  • the transmitter 1230 is further configured to: send the second request data packet to the source server, so that the source server returns the target data after receiving the second request data packet;
  • the receiver 1210 is further configured to: receive the target data returned by the source server;
  • the transmitter 1230 is further configured to: send the target data to the user terminal.
  • the processor 1220 is further configured to: determine whether the cache device includes the target data, where the cache device is a local gateway, and the cache server connected to the base station by using the local gateway Or independently deployed to a cache server in the mobile network;
  • the transmitter 1230 is further configured to: when the cache device has cached the target data, send a data request to the cache device, so that the cache device, after receiving the data request, The data is sent to the user terminal.
  • the sender 1230 is further configured to: send an address of the cache device to the user terminal.
  • the functions of the receiver 1210, the processor 1220, and the transmitter 1230 in the base station in the embodiments of the present invention may be implemented according to the method in the method embodiment described in FIG. 2 above.
  • the specific implementation process refer to the related description of the method embodiment described in FIG. 2 above, and details are not described herein again.
  • FIG. 13 is a schematic structural diagram of still another cache device according to an embodiment of the present invention. As shown in FIG. 13, the cache device includes:
  • the receiver 1310 is configured to receive a request data packet sent by the user terminal, where the request data packet is sent to the base station by the user terminal, for requesting target data, and when the base station receives the request data packet, When the base station determines that the information of the request data packet matches the information in the first data cache list or the target address of the request data packet is the address of the cache device, the base station sends the request data packet to the cache. device;
  • the transmitter 1320 is configured to send the target data to the user terminal.
  • the request packet is the third request packet in the method embodiment described in FIG.
  • the cache device further includes:
  • a processor configured to determine that the target data has been cached; when the target data has been cached, triggering the transmitter to send the target data to the user terminal.
  • the processor is further configured to: encapsulate the target data into a response data packet; a source address of the response data packet is a target address of the request data packet;
  • the transmitter 1320 is further configured to: send the response data packet to the user terminal.
  • the transmitter 1320 is further configured to:
  • the base station determines that the information of the request data packet matches the information in the first data cache list, and does not cache the target data, sends the request data packet to the source server, so that the source After receiving the request packet, the server sends the target data to the user terminal.
  • the sender 1320 is further configured to: when the target data is not cached, send the first request data packet to the source server, so that the source server receives the first request data packet. After the source server returns the target data, the first request data packet is used to request the target data from the source server;
  • the receiver 1310 is further configured to: receive the target data returned from the source server;
  • the transmitter 1320 is further configured to: send the target data to the user terminal.
  • the transmitter 1320 is further configured to: when the target data is not buffered, send a signaling message to the base station, so that after the base station receives the signaling message, the base station sends The source server sends a second request data packet, where the second request data packet is used by the base station to request the target data from the source server; and the base station receives the target data returned from the source server, And transmitting the target data to the user terminal.
  • the functions of the receiver 1310, the transmitter 1320, and the processor in the cache device in the embodiments of the present invention may be specifically implemented according to the method in the foregoing method embodiment of FIG. 2 or FIG. 5, and the specific implementation process thereof Reference may be made to the related description of the method embodiment described in FIG. 2 or FIG. 5 above, and details are not described herein again.
  • FIG. 14 is a schematic structural diagram of another user terminal according to an embodiment of the present invention. As shown in FIG. 14, the user terminal includes:
  • the processor 1410 is configured to generate a third request data packet, where the third request data packet is used to request target data from the source server, and determine, according to the second data cache list, whether the information of the third request data packet is The information in the two data cache lists is matched; the second data cache list includes at least one information, and a correspondence between the information and an address of the cache device;
  • the processor 1410 is further configured to: when the information of the third request data packet matches the information in the second data cache list, generate a fourth request data packet, where the target address of the fourth request data packet is The address of the cache device corresponding to the matched information; the fourth request data packet is used to request the target data from the cache device;
  • the transmitter 1420 is configured to send the fourth request data packet to the cache device, so that the cache device sends the target data to the user terminal after receiving the fourth request data packet;
  • the receiver 1430 is configured to receive the target data.
  • the transmitter 1420 is further configured to: when the information of the third request data packet does not match the information in the second data cache list, send the third request data packet, so that the source After receiving the third request data packet, the server sends the target data to the user terminal;
  • the receiver 1430 is further configured to: receive the target data.
  • processor 1410 is further configured to:
  • the second data cache list includes at least one information, and a correspondence between the information and an address of the cache device; wherein the information includes an address of the server and/or an identifier of the data .
  • the functions of the processor 1410, the transmitter 1420, and the receiver 1430 in the user terminal in the embodiments of the present invention may be specifically implemented according to the method in the method embodiment described in FIG. 5 above, and the specific implementation process may be implemented. Refer to the related description of the method embodiment described in FIG. 5 above, and details are not described herein again.
  • the program may be stored in a computer readable storage medium, and the storage medium may include: Flash disk, Read-Only Memory (ROM), Random Access Memory (RAM), disk or optical disk.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明实施例提供了一种缓存数据获取方法、相关设备以及通信系统，该方法包括：接收用户终端发送的请求数据包；该请求数据包用于向源服务器请求目标数据；根据第一数据缓存列表，判断该请求数据包的信息是否与第一数据缓存列表中的信息相匹配，如果是，将所述目标数据发送至用户终端，本发明还提供了另一种缓存数据获取方法。本发明实施例通过将源服务器的数据下沉至距离用户较近的缓存设备(比如基站、本地网关或缓存服务器等)中，以便用户可以直接从缓存设备中获取目标数据，避免了无线网到核心网的回程链路上的开销，从而提高用户终端请求数据的响应速度，提升用户体验。

Description

缓存数据获取方法、相关设备以及通信系统 技术领域
本发明涉及无线网络技术领域，尤其涉及一种缓存数据获取方法、相关设备以及系统。
背景技术
随着智能终端(如智能手机等)的广泛应用，以及互联网技术的快速发展，移动数据流量呈现持续的爆发式增长，大量的数据流量使得运营商服务器以及网络基础设施压力过大，极易造成网络拥塞、数据冗余传输与用户体验差等问题。为了解决这一问题，缓存技术得到了学术界和产业界的高度关注。
目前，比较常见的缓存方式是通过部署于骨干网(英文：Backbone Network)的内容分发网络(Content Delivery Network，CDN)，将源服务器的内容分发到网络的边缘，根据网络流量和各节点的连接、负载状况以及到用户的距离和响应时间等综合信息将用户的数据请求重新导向离用户最近的服务节点上，使用户可就近取得所需的数据，缓解互联网网络拥塞状况，提高用户访问网站的响应速度。
然而，CND仅部署于骨干网，将数据推送到骨干网的边缘，对于无线网到核心网链路回程开销较大，使得用户终端在请求缓存数据时，响应速度较慢，降低用户体验。
发明内容
本申请的目的在于提供一种缓存数据获取方法，可以避免无线网到核心网的回程链路上的开销，从而提高用户终端请求数据的响应速度，提升用户体验。
第一方面，本发明实施例提供了一种缓存数据获取方法，包括：基站接收用户终端发送的请求数据包，该请求数据包用于向源服务器请求目标数据，基站根据第一数据缓存列表，判断请求数据包的信息是否与第一数据缓存列 表中的信息相匹配，其中，当该请求数据包的信息与第一数据缓存列表中的信息相匹配时，基站将存储于缓存设备的目标数据发送至用户终端，可以理解，该缓存设备可以是基站、本地网关、通过本地网关与基站相连的缓存服务器或者独立地部署于移动网络中的缓存服务器。
本技术方案，当接收用户终端发送的请求数据包后，该请求数据包用于用户终端向源服务器请求目标数据，基站根据第一数据缓存列表，判断该请求数据包的信息是否与第一数据缓存列表中的信息相匹配，如果是，则将存储于缓存设备中的目标数据发送至用户终端。通过将源服务器的数据下沉至距离用户较近的缓存设备(比如基站、本地网关或缓存服务器等)中，以便用户可以直接从缓存设备中获取目标数据，避免了无线网到核心网的回程链路上的开销，从而提高用户终端请求数据的响应速度，提升用户体验。
结合第一方面，在第一方面的第一种实现方式中，基站在根据第一数据缓存列表，判断请求数据包的信息是否与第一数据缓存列表中的信息相匹配之前，基站还可以获取第一数据缓存列表，其中，第一数据缓存列表中包含服务器的地址、数据的标识至少一个。
结合第一方面，在第一方面的第二种实现方式中，基站将目标数据发送至用户终端的一实施方式可以是：基站通过基站与缓存设备建立的第一承载，将目标数据发送至用户终端；可以理解，此时缓存设备包括本地网关、通过本地网关与基站相连的缓存服务器或者独立地部署于移动网络中的缓存服务器。
本技术方案，通过创建第一承载来承载基站与缓存设备之间的数据传输，实现基站与缓存设备以及源服务器之间是数据传输，以便用户可以直接从缓存设备中获取目标数据，可以避免冗余数据的传输，缓解网络堵塞，缩短响应时延，提高用户体验。
结合第一方面，在第一方面的第三种实现方式中，该方法还可以包括：当请求数据包的信息与第一数据缓存列表中的信息不匹配时，基站可以通过基站与源服务器建立的第二承载，将目标数据发送至用户终端。
本技术方案，通过创建第二承载来承载基站与源服务器之间的数据传输，实现基站与缓存设备以及源服务器之间是数据传输，以便用户可以在缓存设 备中无目标数据缓存时，通过原有的TCP(Transmission Control Protocol)数据传输通道来传输数据，实现目标数据的获取。
结合第一方面，在第一方面的第四种实现方式中，基站在将目标数据发送至用户终端之前，基站还可以判断是否缓存设备已缓存所述目标数据，当已缓存所述目标数据时，将目标数据发送至用户终端。可以理解，目标数据可以存储于缓存设备(基站、本地网关、通过本地网关与基站相连的缓存服务器或者独立地部署于移动网络中的缓存服务器)中。
本技术方案，通过将源服务器的数据下沉至距离用户较近的缓存设备(基站、本地网关或缓存服务器)中，以便用户可以直接从缓存设备中获取目标数据，可以避免冗余数据的传输，缓解网络堵塞，缩短响应时延，提高用户体验。
结合第一方面、第一方面的第一至四种实现方式，在第一方面的第五种实现方式中，基站将目标数据发送至用户终端的一实施方式可以是：基站将目标数据封装成响应数据包；该响应数据包的源地址为所述请求数据包的目标地址，进而，将所述响应数据包发送至用户终端。
本技术方案，基站代替源服务器响应请求数据包的目标数据的请求，避免用户终端在检测到响应数据包的源地址与该请求数据包的目标地址不一致时，用户终端不能识别该数据包。
结合第一方面第四种实现方式，在第一方面的第六种实现方式中，当缓存设备(基站、本地网关或缓存服务器)未缓存所述目标数据时，基站还可以向所述源服务器发送所述请求数据包，以使所述源服务器在接收到所述请求数据包后，所述源服务器将所述目标数据发送至用户终端。
本技术方案，当缓存设备(基站、本地网关或缓存服务器)未缓存目标数据时，仍然使用用户终端和源服务器之间的TCP(Transmission Control Protocol)数据传输通道来传输数据，提供一种TCP链路的处理方式。
结合第一方面第六种实现方式，在第一方面的第七种实现方式中，当基站检测到源服务器向用户终端发送的目标数据时，基站可以将该目标数据保存至缓存设备(基站、本地网关或缓存服务器)，实现对缓存设备对可以缓存的目标数据进行保存，避免重复请求目标数据，缓解网络拥塞。
结合第一方面第四种实现方式，在第一方面的第八种实现方式中，当未缓存所述目标数据时，基站还可以生成第一请求数据包，该第一请求数据包的源地址为缓存设备的地址，用于向源服务器请求目标数据；进而，向源服务器发送第一请求数据包，以使源服务器在接收到第一请求数据包后，将目标数据发送至所述缓存设备。
本技术方案，当缓存设备(基站、本地网关或缓存服务器)未缓存目标数据时，使用基站和源服务器之间的TCP(Transmission Control Protocol)数据传输通道来传输数据，提供一种TCP链路的处理方式，实现目标数据的获取。
结合第一方面第四种实现方式，在第一方面的第九种实现方式中，当缓存设备(本地网关或缓存服务器)未缓存目标数据时，基站可以接收缓存设备发送的信令消息，并根据该信令消息，生成第二请求数据包，该第二请求数据包用于向源服务器请求目标数据，进而，向所述源服务器发送该第二请求数据包，以使源服务器在接收到第二请求数据包后，返回所述目标数据，进一步地，基站接收源服务器返回的目标数据，并将该目标数据发送至用户终端。
本技术方案，当缓存设备(本地网关或缓存服务器)未缓存目标数据时，使用基站和源服务器之间的TCP(Transmission Control Protocol)数据传输通道来传输数据，提供一种TCP链路的处理方式，实现目标数据的获取。
结合第一方面第九种实现方式，在第一方面的第十种实现方式中，基站接收源服务器返回的目标数据之后，基站还可以将该目标数据保存至缓存设备(本地网关或缓存服务器)，实现对缓存设备对可以缓存的目标数据进行保存，避免重复请求目标数据，缓解网络拥塞。
结合第一方面第四种实现方式，在第一方面的第十一种实现方式中，基站判断是否已缓存目标数据的一实施方式可以是：基站判断缓存设备是否已缓存所述目标数据，其中，缓存设备为本地网关、通过本地网关与基站相连的缓存服务器或者独立地部署于移动网络中的缓存服务器；相应地，当缓存设备已缓存目标数据时，基站将目标数据发送至用户终端的一实施方式可以是：基站向缓存设备发送数据请求，以使该缓存设备在接收到数据请求后， 将目标数据发送至用户终端。
结合第一方面，在第一方面的第十二种实现方式中，该方法还可以包括：基站向所述用户终端发送缓存设备的地址。
第二方面，本发明实施例还提供了一种缓存数据获取方法，包括：缓存设备接收用户终端发送的请求数据包，其中，该请求数据包为用户终端发送给基站，用于请求目标数据；当基站接收到请求数据包时，且该基站判断请求数据包的信息与第一数据缓存列表中的信息相匹配时或该请求数据包的目标地址为缓存设备的地址时，基站将该请求数据包发送至缓存设备，此时缓存设备接收该请求数据包，并将目标数据发送至用户终端。可以理解，该缓存设备可以是基站、本地网关、通过本地网关与基站相连的缓存服务器或者独立地部署于移动网络中的缓存服务器。
本技术方案，缓存设备接收用户终端发送的请求数据包，其中，该请求数据包为用户终端发送给基站，用于请求目标数据；当基站接收到请求数据包时，且该基站判断请求数据包的信息与第一数据缓存列表中的信息相匹配时或该请求数据包的目标地址为缓存设备的地址时，基站将该请求数据包发送至缓存设备，此时缓存设备将目标数据发送至用户终端，通过将源服务器的数据下沉至部署于移动网络中距离用户较近的缓存设备(基站、本地网关、通过本地网关与基站相连的缓存服务器或者独立地部署于移动网络中的缓存服务器)中，以便用户可以直接从缓存设备中获取目标数据，避免了无线网到核心网的回程链路上的开销，从而提高用户终端请求数据的响应速度，提升用户体验。
结合第二方面，在第二方面的第一种实现方式中，缓存设备将所述目标数据发送至所述用户终端的一实施方式可以是：缓存设备判断是否已缓存所述目标数据，当已缓存所述目标数据时，将所述目标数据发送至所述用户终端。
结合第二方面或第二方面第一种实现方式，在第二方面的第二种实现方式中，缓存设备将目标数据发送至用户终端的一实施方式可以是：缓存设备将目标数据封装成响应数据包；该响应数据包的源地址为请求数据包的目标地址，进而，将该响应数据包发送至所述用户终端。
本技术方案，缓存设备代替源服务器响应请求数据包的目标数据的请求，避免用户终端在检测到响应数据包的源地址与该请求数据包的目标地址不一致时，用户终端不能识别该数据包，同时避免冗余数据的传输，缓解网络堵塞，缩短响应时延，提高用户体验。
结合第二方面第一种实现方式，在第二方面的第三种实现方式中，当所述基站判断所述请求数据包的信息与第一数据缓存列表中的信息相匹配，且缓存设备(本地网关、通过本地网关与基站相连的缓存服务器或者独立地部署于移动网络中的缓存服务器)未缓存目标数据时，该方法还可以包括：缓存设备向源服务器发送所述请求数据包，以使源服务器在接收到所述请求数据包后，源服务器将目标数据发送至用户终端。
本技术方案，当缓存设备中未缓存目标数据时，仍然使用用户终端和源服务器之间的TCP(Transmission Control Protocol)数据传输通道来传输数据，提供一种TCP链路的处理方式，实现目标数据的获取。
结合第二方面第一种实现方式，在第二方面的第四种实现方式中，当缓存设备(基站、本地网关、通过本地网关与基站相连的缓存服务器或者独立地部署于移动网络中的缓存服务器)未缓存目标数据时，该方法还包括：缓存设备向所述源服务器发送第一请求数据包，以使源服务器在接收到所述第一请求数据包后，源服务器返回所述目标数据，该第一请求数据包用于向所述源服务器请求所述目标数据，进而，缓存设备接收从源服务器返回的目标数据，并将目标数据发送至用户终端。
本技术方案，当缓存设备(基站、本地网关、通过本地网关与基站相连的缓存服务器或者独立地部署于移动网络中的缓存服务器)未缓存目标数据时，使用缓存设备和源服务器之间的TCP(Transmission Control Protocol)数据传输通道来传输数据，提供一种TCP链路的处理方式，实现目标数据的获取。
结合第二方面第一种实现方式，在第二方面的第五种实现方式中，当缓存设备(本地网关、通过本地网关与基站相连的缓存服务器或者独立地部署于移动网络中的缓存服务器)未缓存目标数据时，该方法还包括：缓存设备向所述基站发送信令消息，以使基站在接收到所述信令消息后，基站向源服 务器发送第二请求数据包，该第二请求数据包用于向所述源服务器请求目标数据；进而，基站接收从所述源服务器返回的目标数据，并将目标数据发送给用户终端。
本技术方案，当缓存设备(本地网关、通过本地网关与基站相连的缓存服务器或者独立地部署于移动网络中的缓存服务器)未缓存目标数据时，使用基站和源服务器之间的TCP(Transmission Control Protocol)数据传输通道来传输数据，提供一种TCP链路的处理方式，实现目标数据的获取。
第三方面，本发明实施例还提供了一种缓存数据获取方法，包括：用户终端生成第三请求数据包，该第三请求数据包用于向源服务器请求目标数据，并根据第二数据缓存列表，判断第三请求数据包的信息是否与第二数据缓存列表中的信息相匹配，如果是，则生成第四请求数据包，其中，第二数据缓存列表包括至少一个信息，以及该信息与缓存设备的地址的对应关系；第四请求数据包的目标地址为匹配的信息对应的缓存设备的地址；该第四请求数据包用于向所述缓存设备请求目标数据，进而，用户终端向所述缓存设备发送第四请求数据包，以使所述缓存设备在接收到第四请求数据包后，将目标数据发送至用户终端，此时，用户终端接收该目标数据。可以理解，该缓存设备可以是基站、本地网关、通过本地网关与基站相连的缓存服务器或者独立地部署于移动网络中的缓存服务器。
本技术方案，用户终端设置有第二数据缓存列表，该第二数据缓存列表包括至少一个信息，以及该信息与缓存设备的地址的对应关系，当用户终端接收到用于向源服务器请求目标数据的第三请求数据包后，用户终端根据第二数据缓存列表，判断第三请求数据包的信息是否与第二数据缓存列表中的信息相匹配，如果是，说明该目标数据为缓存设备可缓存的数据，用户终端将第三请求数据包的目标地址修改为匹配的信息对应的缓存设备的地址，生成用于向所述缓存设备请求目标数据的第四请求数据包，进而向所述缓存设备发送第四请求数据包，以使所述缓存设备在接收到第四请求数据包后，将目标数据发送至用户终端，此时，用户终端接收该目标数据，从而实现从距离用户较近的缓存设备(比如基站、本地网关或缓存服务器等)中获取目标数据，避免了无线网到核心网的回程链路的开销，从而提高用户终端请求数 据的响应速度，提升用户体验。
结合第三方面，在第三方面的第一种实现方式中，当所述第三请求数据包的信息与第二数据缓存列表中的信息不匹配时，则该目标数据为缓存设备不能缓存的数据，用户终端可以发送所述第三请求数据包，以使源服务器接收到所述第三请求数据包后，将第三请求数据包目标数据发送至用户终端，此时，用户终端接收该目标数据。
本技术方案，通过使用用户终端和源服务器之间的TCP(Transmission Control Protocol)数据传输通道来传输数据，提供一种TCP链路的处理方式，实现目标数据的获取。
结合第三方面，在第三方面的第一种实现方式中，用户终端在判断所述第三请求数据包的信息是否与第二数据缓存列表中的信息相匹配之前，该方法还包括：用户终端获取第二数据缓存列表，其中，该第二数据缓存列表中包括至少一个信息，以及所述信息与缓存设备的地址的对应关系；其中，所述信息包括服务器的地址和/或数据的标识。
第四方面，本发明提供了一种基站，包括：
接收模块，用于接收用户终端发送的请求数据包；所述请求数据包用于向源服务器请求目标数据；
处理模块，用于根据预存的第一数据缓存列表，判断所述请求数据包的信息是否与第一数据缓存列表中的信息相匹配；
发送模块，用于当所述请求数据包的信息与所述第一数据缓存列表中的信息相匹配时，将所述目标数据发送至所述用户终端。
本技术方案，当接收用户终端发送的请求数据包后，该请求数据包用于用户终端向源服务器请求目标数据，基站根据第一数据缓存列表，判断该请求数据包的信息是否与第一数据缓存列表中的信息相匹配，如果是，则将存储于缓存设备中的目标数据发送至用户终端。通过将源服务器的数据下沉至距离用户较近的缓存设备(比如基站、本地网关或缓存服务器等)中，以便用户可以直接从缓存设备中获取目标数据，避免了无线网到核心网的回程链路上的开销，从而提高用户终端请求数据的响应速度，提升用户体验。
结合第四方面，在第四方面的第一种实现方式中，
所述处理模块还用于：获取第一数据缓存列表，其中，所述第一数据缓存列表中包含以下信息中的至少一个：
服务器的地址、数据的标识。
结合第四方面，在第四方面的第二种实现方式中，所述发送模块还用于：
当所述请求数据包的信息与所述第一数据缓存列表中的信息相匹配时，通过所述基站与缓存设备建立的第一承载，将所述目标数据发送至所述用户终端。
结合第四方面，在第四方面的第三种实现方式中，所述发送模块还用于：
当所述请求数据包的信息与所述第一数据缓存列表中的信息不匹配时，通过所述基站与所述源服务器建立的第二承载，将所述目标数据发送至所述用户终端。
结合第四方面，在第四方面的第四种实现方式中，
所述处理模块还用于：判断是否已缓存所述目标数据，当已缓存所述目标数据时，触发所述发送模块将所述目标数据发送至所述用户终端。
结合第四方面或第四方面第一至四种实现方式中任一实现方式，在第四方面的第五种实现方式中，
所述处理模块还用于：将所述目标数据封装成响应数据包；所述响应数据包的源地址为所述请求数据包的目标地址；
所述发送模块还用于：将所述响应数据包发送至所述用户终端。
结合第四方面第四种实现方式，在第四方面的第六种实现方式中，所述发送模块还用于：当未缓存所述目标数据时，向所述源服务器发送所述请求数据包，以使所述源服务器在接收到所述请求数据包后，所述源服务器将所述目标数据发送至所述用户终端。
结合第四方面第四种实现方式，在第四方面的第七种实现方式中，
所述处理模块还用于：当未缓存所述目标数据时，生成第一请求数据包，所述第一请求数据包的源地址为缓存设备的地址，用于向所述源服务器请求目标数据；
所述发送模块还用于：向所述源服务器发送所述第一请求数据包，以使所述源服务器在接收到所述第一请求数据包后，将所述目标数据发送至所述 缓存设备。
结合第四方面第四种实现方式，在第四方面的第八种实现方式中，
所述接收模块还用于：当未缓存所述目标数据时，接收所述缓存设备发送的信令消息；
所述处理模块还用于：根据所述信令消息，生成第二请求数据包，所述第二请求数据包用于向所述源服务器请求所述目标数据；
所述发送模块还用于：向所述源服务器发送所述第二请求数据包，以使所述源服务器在接收到所述第二请求数据包后，返回所述目标数据；
所述接收模块还用于：接收所述源服务器返回的所述目标数据；
所述发送模块还用于：将所述目标数据发送至所述用户终端。
结合第四方面第四种实现方式，在第四方面的第九种实现方式中，
所述处理模块还用于：判断所述缓存设备是否包含所述目标数据，其中，所述缓存设备为本地网关、通过所述本地网关与所述基站相连的所述缓存服务器或者独立地部署于移动网络中的缓存服务器；
所述发送模块还用于：当所述缓存设备已缓存所述目标数据时，向所述缓存设备发送数据请求，以使所述缓存设备在接收到所述数据请求后，将所述目标数据发送至用户终端。
结合第四方面，在第四方面的第十种实现方式中，所述发送模块还用于：向所述用户终端发送缓存设备的地址。
第五方面，本发明实施例还提供了一种缓存设备，包括：
接收模块，用于接收用户终端发送的请求数据包；其中，所述请求数据包为用户终端发送给基站，用于请求目标数据；当所述基站接收到所述请求数据包时，且所述基站判断所述请求数据包的信息与第一数据缓存列表中的信息相匹配时或所述请求数据包的目标地址为缓存设备的地址时，所述基站将所述请求数据包发送至缓存设备；
发送模块，用于将所述目标数据发送至所述用户终端。
本技术方案，缓存设备接收用户终端发送的请求数据包，其中，该请求数据包为用户终端发送给基站，用于请求目标数据；当基站接收到请求数据包时，且该基站判断请求数据包的信息与第一数据缓存列表中的信息相匹配 时或该请求数据包的目标地址为缓存设备的地址时，基站将该请求数据包发送至缓存设备，此时缓存设备将目标数据发送至用户终端，通过将源服务器的数据下沉至部署于移动网络中距离用户较近的缓存设备(基站、本地网关、通过本地网关与基站相连的缓存服务器或者独立地部署于移动网络中的缓存服务器)中，以便用户可以直接从缓存设备中获取目标数据，避免了无线网到核心网的回程链路上的开销，从而提高用户终端请求数据的响应速度，提升用户体验。
结合第五方面，在第五方面的第一种实现方式中，所述缓存设备还包括：处理模块，用于判断是已缓存所述目标数据；当已缓存所述目标数据时，触发所述发送模块将所述目标数据发送至所述用户终端。
结合第五方面或第五方面第一种实现方式，在第五方面的第二种实现方式中，
所述处理模块还用于：将所述目标数据封装成响应数据包；所述响应数据包的源地址为所述请求数据包的目标地址；
所述发送模块还用于：将所述响应数据包发送至所述用户终端。
结合第五方面第一种实现方式，在第五方面的第三种实现方式中，所述发送模块还用于：当所述基站判断所述请求数据包的信息与第一数据缓存列表中的信息相匹配，且未缓存所述目标数据时，向所述源服务器发送所述请求数据包，以使所述源服务器在接收到所述请求数据包后，所述源服务器将所述目标数据发送至所述用户终端。
结合第五方面第一种实现方式，在第五方面的第四种实现方式中，
所述发送模块还用于，当未缓存所述目标数据时，向所述源服务器发送第一请求数据包，以使所述源服务器在接收到所述第一请求数据包后，所述源服务器返回所述目标数据，所述第一请求数据包用于向所述源服务器请求所述目标数据；
所述接收模块还用于：接收从所述源服务器返回的所述目标数据；
所述发送模块还用于：将所述目标数据发送至所述用户终端。
结合第五方面第一种实现方式，在第五方面的第五种实现方式中，所述发送模块还用于：当未缓存所述目标数据时，向所述基站发送信令消息，以 使所述基站在接收到所述信令消息后，所述基站向所述源服务器发送第二请求数据包，所述第二请求数据包用于所述基站向所述源服务器请求所述目标数据；所述基站接收从所述源服务器返回的所述目标数据，并将所述目标数据发送给所述用户终端。
第六方面，本发明实施例还提供了一种用户终端，包括：
处理模块，用于生成第三请求数据包；所述第三请求数据包用于向源服务器请求目标数据；以及根据第二数据缓存列表，判断所述第三请求数据包的信息是否与第二数据缓存列表中的信息相匹配；所述第二数据缓存列表包括至少一个信息，以及所述信息与缓存设备的地址的对应关系；
所述处理模块还用于：当所述第三请求数据包的信息与第二数据缓存列表中的信息相匹配时，生成第四请求数据包，所述第四请求数据包的目标地址为匹配的信息对应的缓存设备的地址；所述第四请求数据包用于向所述缓存设备请求所述目标数据；
发送模块，用于向所述缓存设备发送所述第四请求数据包，以使所述缓存设备在接收到所述第四请求数据包后，将所述目标数据发送至用户终端；
接收模块，用于接收所述目标数据。
本技术方案，用户终端设置有第二数据缓存列表，该第二数据缓存列表包括至少一个信息，以及该信息与缓存设备的地址的对应关系，当用户终端接收到用于向源服务器请求目标数据的第三请求数据包后，用户终端根据第二数据缓存列表，判断第三请求数据包的信息是否与第二数据缓存列表中的信息相匹配，如果是，说明该目标数据为缓存设备可缓存的数据，用户终端将第三请求数据包的目标地址修改为匹配的信息对应的缓存设备的地址，生成用于向所述缓存设备请求目标数据的第四请求数据包，进而向所述缓存设备发送第四请求数据包，以使所述缓存设备在接收到第四请求数据包后，将目标数据发送至用户终端，此时，用户终端接收该目标数据，从而实现从距离用户较近的缓存设备(比如基站、本地网关或缓存服务器等)中获取目标数据，避免了无线网到核心网的回程链路的开销，从而提高用户终端请求数据的响应速度，提升用户体验。
结合第六方面，在第六方面的第一种实现方式中，
所述发送模块还用于：当所述第三请求数据包的信息与第二数据缓存列表中的信息不匹配时，发送所述第三请求数据包，以使所述源服务器在接收到所述第三请求数据包后，将所述目标数据发送至所述用户终端；
所述接收模块还用于：接收所述目标数据。
结合第六方面，在第六方面的第二种实现方式中，所述处理模块还用于：
获取第二数据缓存列表，其中，所述第二数据缓存列表中包括至少一个信息，以及所述信息与缓存设备的地址的对应关系；其中，所述信息包括服务器的地址和/或数据的标识。
第七方面，本发明实施例还提供了一种基站，包括：
接收器，用于接收用户终端发送的请求数据包；所述请求数据包用于向源服务器请求目标数据；
处理器，用于根据预存的第一数据缓存列表，判断所述请求数据包的信息是否与第一数据缓存列表中的信息相匹配；
发送器，用于当所述请求数据包的信息与所述第一数据缓存列表中的信息相匹配时，将所述目标数据发送至所述用户终端。
结合第七方面，在第七方面的第一种实现方式中，所述处理器还用于：获取第一数据缓存列表，其中，所述第一数据缓存列表中包含以下信息中的至少一个：
服务器的地址、数据的标识。
结合第七方面，在第七方面的第二种实现方式中，所述发送器还用于：
当所述请求数据包的信息与所述第一数据缓存列表中的信息相匹配时，通过所述基站与缓存设备建立的第一承载，将所述目标数据发送至所述用户终端。
结合第七方面，在第七方面的第三种实现方式中，所述发送器还用于：
当所述请求数据包的信息与所述第一数据缓存列表中的信息不匹配时，通过所述基站与所述源服务器建立的第二承载，将所述目标数据发送至所述用户终端。
结合第七方面，在第七方面的第四种实现方式中，所述处理器还用于：判断是否已缓存所述目标数据，当已缓存所述目标数据时，触发所述发送器 将所述目标数据发送至所述用户终端。
结合第七方面或第七方面第一至四种实现方式中任一实现方式，在第七方面的第五种实现方式中，所述处理器还用于：将所述目标数据封装成响应数据包；所述响应数据包的源地址为所述请求数据包的目标地址；
所述发送器还用于：将所述响应数据包发送至所述用户终端。
结合第七方面第四种实现方式，在第七方面的第六种实现方式中，所述发送器还用于：当未缓存所述目标数据时，向所述源服务器发送所述请求数据包，以使所述源服务器在接收到所述请求数据包后，所述源服务器将所述目标数据发送至所述用户终端。
结合第七方面第四种实现方式，在第七方面的第七种实现方式中，所述处理器还用于：当未缓存所述目标数据时，生成第一请求数据包，所述第一请求数据包的源地址为缓存设备的地址，用于向所述源服务器请求目标数据；
所述发送器还用于：向所述源服务器发送所述第一请求数据包，以使所述源服务器在接收到所述第一请求数据包后，将所述目标数据发送至所述缓存设备。
结合第七方面第四种实现方式，在第七方面的第八种实现方式中，所述接收器还用于：当未缓存所述目标数据时，接收所述缓存设备发送的信令消息；
所述处理器还用于：根据所述信令消息，生成第二请求数据包，所述第二请求数据包用于向所述源服务器请求所述目标数据；
所述发送器还用于：向所述源服务器发送所述第二请求数据包，以使所述源服务器在接收到所述第二请求数据包后，返回所述目标数据；
所述接收器还用于：接收所述源服务器返回的所述目标数据；
所述发送器还用于：将所述目标数据发送至所述用户终端。
结合第七方面第四种实现方式，在第七方面的第九种实现方式中，所述处理器还用于：判断所述缓存设备是否包含所述目标数据，其中，所述缓存设备为本地网关、通过所述本地网关与所述基站相连的所述缓存服务器或者独立地部署于移动网络中的缓存服务器；
所述发送器还用于：当所述缓存设备已缓存所述目标数据时，向所述缓 存设备发送数据请求，以使所述缓存设备在接收到所述数据请求后，将所述目标数据发送至用户终端。
结合第七方面，在第七方面的第十种实现方式中，所述发送器还用于：向所述用户终端发送缓存设备的地址。
第八方面，本发明实施例还提供了一种缓存设备，包括：
接收器，用于接收用户终端发送的请求数据包；其中，所述请求数据包为用户终端发送给基站，用于请求目标数据；当所述基站接收到所述请求数据包时，且所述基站判断所述请求数据包的信息与第一数据缓存列表中的信息相匹配时或所述请求数据包的目标地址为缓存设备的地址时，所述基站将所述请求数据包发送至缓存设备；
发送器，用于将所述目标数据发送至所述用户终端。
结合第八方面，在第八方面的第一种实现方式中，所述缓存设备还包括：
处理器：用于判断是已缓存所述目标数据；当已缓存所述目标数据时，触发所述发送器将所述目标数据发送至所述用户终端。
结合第八方面或第八方面第一种实现方式，在第八方面的第二种实现方式中，所述处理器还用于：将所述目标数据封装成响应数据包；所述响应数据包的源地址为所述请求数据包的目标地址；
所述发送器还用于：将所述响应数据包发送至所述用户终端。
结合第八方面第一种实现方式，在第八方面的第三种实现方式中，所述发送器还用于：
当所述基站判断所述请求数据包的信息与第一数据缓存列表中的信息相匹配，且未缓存所述目标数据时，向所述源服务器发送所述请求数据包，以使所述源服务器在接收到所述请求数据包后，所述源服务器将所述目标数据发送至所述用户终端。
结合第八方面第一种实现方式，在第八方面的第四种实现方式中，所述发送器还用于，当未缓存所述目标数据时，向所述源服务器发送第一请求数据包，以使所述源服务器在接收到所述第一请求数据包后，所述源服务器返回所述目标数据，所述第一请求数据包用于向所述源服务器请求所述目标数据；
所述接收器还用于：接收从所述源服务器返回的所述目标数据；
所述发送器还用于：将所述目标数据发送至所述用户终端。
结合第八方面第一种实现方式，在第八方面的第五种实现方式中，所述发送器还用于：当未缓存所述目标数据时，向所述基站发送信令消息，以使所述基站在接收到所述信令消息后，所述基站向所述源服务器发送第二请求数据包，所述第二请求数据包用于所述基站向所述源服务器请求所述目标数据；所述基站接收从所述源服务器返回的所述目标数据，并将所述目标数据发送给所述用户终端。
第九方面，本发明实施例还提供了一种用户终端，包括：
处理器，用于生成第三请求数据包；所述第三请求数据包用于向源服务器请求目标数据；以及根据第二数据缓存列表，判断所述第三请求数据包的信息是否与第二数据缓存列表中的信息相匹配；所述第二数据缓存列表包括至少一个信息，以及所述信息与缓存设备的地址的对应关系；
所述处理器还用于：当所述第三请求数据包的信息与第二数据缓存列表中的信息相匹配时，生成第四请求数据包，所述第四请求数据包的目标地址为匹配的信息对应的缓存设备的地址；所述第四请求数据包用于向所述缓存设备请求所述目标数据；
发送器，用于向所述缓存设备发送所述第四请求数据包，以使所述缓存设备在接收到所述第四请求数据包后，将所述目标数据发送至用户终端；
接收器，用于接收所述目标数据。
结合第九方面，在第九方面的第一种实现方式中，所述发送器还用于：当所述第三请求数据包的信息与第二数据缓存列表中的信息不匹配时，发送所述第三请求数据包，以使所述源服务器在接收到所述第三请求数据包后，将所述目标数据发送至所述用户终端；
所述接收器还用于：接收所述目标数据。
结合第九方面，在第九方面的第二种实现方式中，所述处理器还用于：
获取第二数据缓存列表，其中，所述第二数据缓存列表中包括至少一个信息，以及所述信息与缓存设备的地址的对应关系；其中，所述信息包括服务器的地址和/或数据的标识。
第十方面，本发明实施例还提供了一种基站，包括处理器、存储器以及通信接口。处理器连接到存储器和通信接口，例如处理器可以通过总线连接到存储器和通信接口；通信接口用于与用户终端、缓存设备(本地网关、通过本地网关与基站相连的缓存服务器或者独立地部署于移动网络中的缓存服务器)等设备进行通信；存储器用于存储第一方面所述的缓存数据获取方法的程序代码、目标数据以及第二数据缓存列表等，处理器用于调用存储器中的程序代码，执行第一方面的部分或全部流程。
第十一方面，本发明实施例还提供了一种缓存设备，包括处理器、存储器以及通信接口。处理器连接到存储器和通信接口，例如处理器可以通过总线连接到存储器和通信接口；通信接口用于与用户终端、源服务器等设备进行通信；存储器用于存储第二方面所述的缓存数据获取方法的程序代码以及目标数据；处理器用于调用存储器中的程序代码，执行第二方面的部分或全部流程。该缓存设备可以是基站、本地网关、通过本地网关与基站相连的缓存服务器或者独立地部署于移动网络中的缓存服务器。
第十二方面，本发明实施例还提供了一种用户终端，包括处理器、存储器以及通信接口。处理器连接到存储器和通信接口，例如处理器可以通过总线连接到存储器和通信接口；通信接口用于与缓存设备或源服务器等设备进行通信；存储器用于存储第三方面所述的缓存数据获取方法的程序代码以及第二数据缓存列表，处理器用于调用存储器中的程序代码，执行第三方面的部分或全部流程，其中，该缓存设备可以是基站、本地网关、通过本地网关与基站相连的缓存服务器或者独立地部署于移动网络中的缓存服务器。
第十三方面，本发明实施例还提供了一种通信系统，包括：用户终端、基站以及缓存设备；其中，
所述用户终端用于发送请求数据包；所述请求数据包用于向源服务器请求目标数据；
所述基站用于接收用户终端发送的请求数据包，并根据第一数据缓存列表，判断所述请求数据包的信息是否与第一数据缓存列表中的信息相匹配，如果是，将所述目标数据发送至所述用户终端；
所述缓存设备用于存储所述目标数据。
可选地，所述基站包括上述第四方面、第七方面或第十方面所述的任一基站；所述缓存设备包括上述第五方面、第八方面或第十一方面所述的任一缓存设备。
第十四方面，本发明实施例还提供了一种通信系统，包括：用户终端、缓存设备；其中，
所述用户终端用于生成第三请求数据包；所述第三请求数据包用于向源服务器请求目标数据；并根据第二数据缓存列表，判断所述第三请求数据包的信息是否与第二数据缓存列表中的信息相匹配，如果是，生成第四请求数据包，其中，所述第二数据缓存列表包括至少一个信息，以及所述信息与缓存设备的地址的对应关系；所述第四请求数据包的目标地址为匹配的信息对应的缓存设备的地址；所述第四请求数据包用于向所述缓存设备请求所述目标数据，以及向所述缓存设备发送所述第四请求数据包；
所述缓存设备用于接收所述第四请求数据包，并将所述目标数据发送至用户终端；
所述用户终端还用于，接收所述目标数据。
可选地，所述用户终端包括上述第六方面、第九方面或第十二方面所述的任一用户终端；所述缓存设备包括上述第五方面、第五方面第一至二种实现方式、第五方面第四种实现方式、第五方面第五种实现方式、第八方面、第八方面第一至二种实现方式、第八方面第四种实现方式、第八方面第五种实现方式、第十一方面、第十一方面第一至二种实现方式、第十一方面第四种实现方式或第十一方面第五种实现方式所述任一的缓存设备。
附图说明
为了更清楚地说明本发明实施例中的技术方案，下面将对实施例中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其他的附图。
图1是本发明实施例提供的一种通信系统的架构示意图；
图2是本发明实施例提供的一种缓存数据获取方法的流程示意图；
图3是本发明提供的基站将目标数据发送至用户终端的第一种方式的流程示意图；
图4是本发明提供的基站将目标数据发送至用户终端的第二种方式的流程示意图；
图5是本发明实施例提供的一种缓存数据获取方法的另一流程示意图；
图6是本发明实施例提供的一种基站的结构示意图；
图7是本发明实施例提供的另一种基站的结构示意图；
图8是本发明实施例提供的一种缓存设备的结构示意图；
图9是本发明实施例提供的另一种缓存设备的结构示意图；
图10是本发明实施例提供的一种用户终端的结构示意图；
图11是本发明实施例提供的另一种用户终端的结构示意图；
图12是本发明实施例提供的又一种基站的结构示意图；
图13是本发明实施例提供的又一种缓存设备的结构示意图；
图14是本发明实施例提供的又一种用户终端的结构示意图。
具体实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
以下各实施例中所描述的缓存数据获取方法可以应用于各种通信系统，例如：全球移动通讯系统(GSM，Global System of Mobile communication)，码分多址(CDMA，Code Division Multiple Access)系统，宽带码分多址(WCDMA，Wideband Code Division Multiple Access Wireless)，通用分组无线业务(GPRS，General Packet Radio Service)，长期演进(LTE，Long Term Evolution)等。用户终端可以是智能手机(英文：smartphone)、平板电脑(英文：tablet computer)等具有通信功能的终端，本发明不作限定。
基站，可以是GSM或CDMA中的基站(BTS，Base Transceiver Station)，也可以是WCDMA中的基站(NodeB)或LTE中的演进型基站(eNB或 e-NodeB，evolutional Node B)，还可以是，未来通信系统，如5G中的网络设备(如控制器)，本发明不作限定。
用户终端(UE，User Equipment)，具体包括移动电话(英文：cellphone)，智能手机(英文：smartphone)，计算机(英文：computer)，平板电脑(英文：tablet computer)，移动互联网设备(英文：mobile Internet device，MID)和可穿戴设备等可以通过基站接入网络的设备。
缓存设备(Cache设备)为具有数据缓存功能是器件或设备，用于存储源服务器的数据，该缓存设备是基站、本地网关(英文：Local Gateway，LGW)、通过本地网关与基站相连的缓存服务器或者独立地部署于移动网络中的缓存服务器等。具体情况，可参见下述各个实施例的相关描述。
源服务器(英文：Over The Top sever，也称OTT Sever)通过互联网向用户终端提供应用服务的第三方服务器(Over The Top Server)，也可以是运营商的内容提供服务器(Content Provide Server)等，源服务器用于发布本发明各实施例中的目标数据，也可以用来配置本发明实施例所述的基站中的第一数据缓存列表或本发明实施例所述的用户终端中的第二数据缓存列表。
请参阅图1，图1是本发明实施例提供的一种通信系统的架构示意图。本发明各个实施例可以基于该的通信系统的来实施。该通信系统包括用户终端11，基站12以及缓存设备，本发明的缓存设备可以是基站12，也可是本地网关13，也可以是通过本地网关13与基站12连接的缓存服务器14或者独立地部署于移动网络中的缓存服务器14。具体情况，可参见下述各个实施例的相关描述。该系统还可以包括PDN网关(英文：Public Data Network GateWay，又称PDN GateWay，简称PGW)15、服务网关(英文：Serving GateWay，SGW)15、源服务器16等。尽管图1描绘了一个用户终端11、一个基站12、一个本地网关13、一个PGW/SGW15以及一个源服务器16，该通信系统可包括不同数目的用户终端11、基站12、本地网关13、缓存服务器14、PGW/SGW15以及源服务器16。
其中，基站11可以建立两个承载，分别是S1承载即第一承载和S2承载即第二承载，S1承载的对象为LGW，S1承载用于承载用户终端11与本地网关13或缓存服务器14之间的数据传输；S2承载的对象为SGW/PGW15， S2承载用于承载用户终端11与源服务器16之间的数据传输。基站11通过创建两个无线承载分别与S1承载和S2承载绑定，实现两个无线承载与S1承载、S2承载的一一对应。
请参阅图2，图2是本发明实施例提供的一种缓存数据获取方法的流程示意图。该缓存数据获取方法包括以下步骤：
步骤S210：用户终端发送请求数据包，所述请求数据包用于向源服务器请求目标数据。
具体地，用户终端可以通过应用程序，比如浏览器、视频软件、音乐软件等向源服务器发送上行数据包，请求获取目标数据。其中，该请求数据包可以包括源地址、目标地址以及目标数据的标识。其中，源地址为用户终端的地址，比如，用户终端的IP地址(英文：Internet Protocol Address)、用户终端的MAC(英文：Media Access Control或者Medium Access Control)地址等；目标地址为源服务器的地址、端口号，源服务器的地址可以是源服务器的IP地址或源服务器的MAC地址；目标数据的标识可以是目标数据的统一资源定位符(英文：Uniform Resource Locator，URL)。例如，该数据包为Http Get请求，用户终端向源服务器，比如，第一视频网站，请求获取目标数据，比如第一电影。
步骤S220：基站接收用户终端发送的所述请求数据包，并根据第一数据缓存列表，判断所述请求数据包的信息是否与第一数据缓存列表中的信息相匹配。
其中，基站配置了第一数据缓存列表，该第一数据缓存列表至少包括以下信息的中的至少一个：服务器的地址、数据的标识，该服务器的地址用于指示该基站可以缓存的数据所来源的源服务器的地址信息，可以是服务器的IP地址、端口号，例如，该第一数据缓存列表包括第一视频网站的IP地址和端口号，则缓存设备(比如基站、本地网关、缓存服务器)可以缓存第一视频网站的数据；服务器的地址还可以是可以服务器的MAC地址、端口号。其中，服务器的IP地址也可以替换为可以对应到该服务器的IP地址或服务器的MAC地址的信息，比如服务器的名称、域名等。可选地，该信息还可以包括数据的标识，比如URL，用于指示该基站可以缓存的源服务器中的数 据，例如，该第一数据缓存列表包括第一视频网站的IP地址以及该第一视频网站的IP地址下的第一视频的URL、第二视频的URL以及第三视频的URL，则缓存设备可以缓存第一视频网站中的第一视频、第二视频以及第三视频，而不能缓存第一视频网站中的第四视频。可以理解，该第一数据缓存列表可以是源服务器主动推送到基站的，也可以是基站向源服务器请求获取的，本发明不作限制。
可以理解，第一数据缓存列表可以由源服务器配置，也可以由运营商通过HPLMN(Home Public Land Mobile Network)配置。基站也可以根据数据请求次数，将满足缓存条件的多个数据的缓存在基站中的缓存设备中，此时，第一数据缓存列表可以包括满足缓存条件的多个数据的源服务器的地址和/或满足缓存条件的多个数据的URL。可以设定，请求次数大于预设次数比如100次的数据满足缓存条件。
具体地，基站接收到用户终端发送的请求数据包后，解析该请求数据包，并根据第一数据缓存列表，判断该请求数据包的目标地址是否与第一数据缓存列表中的地址信息相匹配，如果是，则请求数据包的信息与第一数据缓存列表中的信息相匹配。例如，当第一数据缓存列表包括服务器的地址、端口号时，基站可以判断第一数据缓存列表中是否存在与该请求数据包的目标地址(即，源服务器的地址、端口号)相一致或相对应的服务器的地址、端口号，可以理解，服务器的MAC地址对应唯一的服务器的IP地址，如果是，则该请求数据包的目标地址与第一数据缓存列表中的地址信息相匹配，否则不匹配；又例如，当第一数据缓存列表包括服务器的域名、端口号时，基站可以判断第一数据缓存列表中是否存在与请求数据包的目标地址(即，源服务器的地址、端口号)相对应的服务器的域名、端口号，如果是，则该请求数据包的目标地址与第一数据缓存列表中的地址信息相匹配，否则不匹配。当第一数据缓存列表包括服务器的地址、数据的标识时，步骤S220还包括基站判断第一数据缓存列表中是否存在与目标数据的标识相一致的数据的标识，当该请求数据包的目标地址与第一数据缓存列表中的地址信息相匹配，且第一数据缓存列表中存在与目标数据的标识相一致的数据的标识时，请求数据包的信息与第一数据缓存列表中的信息相匹配。当请求数据包的信息与 第一数据缓存列表中的信息相匹配时，则说明缓存设备可以缓存该目标数据，执行步骤S230；否则，则说明缓存设备不可以缓存该目标数据，此时基站可以执行步骤S240，即基站将所述请求数据包发送至源服务器，以使源服务器在接收到所述请求数据包后，将所述目标数据发送至所述用户终端。可以理解，该缓存设备可以是基站、本地网关、通过本地网关与基站相连的缓存服务器或者独立地部署于移动网络中的缓存服务器等。
步骤S230：所述基站将所述目标数据发送至所述用户终端。
具体地，基站将存储在缓存设备中的目标数据发送至用户终端，其中，该缓存设备可以是基站本身，也可以是本地网关、通过本地网关与基站相连的缓存服务器或者独立地部署于移动网络中的缓存服务器等。
在步骤S230的第一种可能的实现方式中，缓存设备为基站，基站可以有保存数据列表，该保存数据列表可以包括至少一个已保存数据的标识，比如数据的URL。例如，保存数据列表包括第一电影的URL以及第二电影的URL。
请参阅图3，图3是本发明提供的基站将目标数据发送至用户终端的第一种方式的流程示意图。步骤S230的第一种可能的实现方式具体可以包括：
步骤S23101：所述基站判断是否已缓存所述目标数据。
例如，基站在接收到请求数据包后，解析该请求数据包所包含的目标数据的URL，并判断保存数据列表中是否包含该目标数据的URL，如果是，则说明基站中已缓存目标数据，可以执行步骤S23102，否则，说明基站中没有缓存该目标数据，可以执行步骤S23103至步骤S23105，或执行步骤S23106至步骤S23109。
步骤S23102：所述基站将所述目标数据发送至所述用户终端。
可选地，步骤S23102一实施方式可以包括：基站将所述目标数据封装成响应数据包；其中，所述响应数据包的源地址为所述请求数据包的目标地址；再将所述响应数据包发送至所述用户终端。
请参阅图3中步骤S23103-S23105，步骤S23105-S23110是本发明实施例提供的当未缓存目标数据时基站向用户终端发送目标数据的第一种实施方式，包括：
步骤S23103：所述基站向所述源服务器发送所述请求数据包。
具体地，当缓存设备(基站、本地网关或缓存服务器)未缓存该目标数据时，可以执行步骤S23103。
步骤S23104：所述源服务器接收所述请求数据包。
步骤S23105：所述源服务器将所述目标数据发送至所述用户终端。
可选地，步骤S23105还可以包括：当基站检测到所述源服务器向所述用户终端发送的所述目标数据时，基站可以将目标数据保存至缓存设备。
可选地，当未缓存目标数据时基站向用户终端发送目标数据的第二种实施方式，包括：基站生成第一请求数据包，该第一请求数据包的源地址为缓存设备的地址(比如，缓存设备的IP地址、缓存设备的MAC地址等)，目标地址为源服务器的地址(比如，源服务器的IP地址、源服务器的MAC地址等)，用于向源服务器请求目标数据；进而，基站向源服务器发送第一请求数据包，源服务器在接收到第一请求数据包后，将目标数据发送至所述缓存设备，缓存设备再将该目标数据发送至用户终端。
请参阅图3中步骤S23106-S23110，步骤S23106-S23110是本发明实施例提供的当未缓存目标数据时基站向用户终端发送目标数据的第三种实施方式，包括：
步骤S23106：所述基站向所述源服务器发送第二请求数据包，所述第二请求数据包用于基站向所述源服务器请求所述目标数据，第二请求数据包的源地址是基站的地址，目标地址是源服务器的地址。
具体地，当缓存设备(基站)中未缓存该目标数据时，可以执行步骤S23106。该第二请求数据包的源地址为基站的地址(比如，基站的MAC地址、基站IP地址等)，目标地址为所述请求数据包的目标地址，该第二请求数据包包括目标数据的标识。
步骤S23107：所述源服务器在接收所述第二请求数据包。
步骤S23108：所述源服务器向所述基站返回所述目标数据。
步骤S23109：所述基站接收从所述源服务器返回的所述目标数据。
步骤S23110：所述基站将所述目标数据发送至所述用户终端。
可选地，步骤S23110之后，基站还可保存目标数据。
步骤S23111：所述用户终端接收所述目标数据。
具体地，步骤S23102之后、步骤S23105或步骤S23110之后，用户终端可以接收目标数据。
在步骤S230的第二种可能的实现方式中，缓存设备可以是本地网关、通过本地网关与基站相连的缓存服务器或者独立地部署于移动网络中的缓存服务器，缓存设备(缓存服务器或本地网关)中可以设有保存数据列表，该保存数据列表可以包括至少一个已缓存数据的标识，比如数据的URL，。例如，保存数据列表包括第一电影的URL以及第二电影的URL。
请参阅图4，图4是本发明提供的基站将目标数据发送至用户终端的第二种方式的流程示意图。步骤S230的第二种可能的实现方式具体可以包括：
步骤S23201：所述基站将所述请求数据包发送至缓存设备。
具体地，基站可以预先与所述缓存设备建立第一承载，用于承载用户终端与缓存设备之间的数据传输；以及与源服务器建立第二承载，用于承载用户终端与源服务器之间的数据传输。其中，基站与所述缓存设备建立的第一承载可以由本地网关或基站控制，也可以由移动网络中部署的移动性管理设备(英文Mobility Management Entity，MME)来控制。
步骤S23202：所述缓存设备接收基站发送的所述请求数据包。
步骤S23203：所述缓存设备判断是否已缓存所述目标数据。
具体地，缓存设备可以判断保存数据列表中是否包含目标数据的标识，如果是，则缓存设备判断已缓存所述目标数据，可以执行步骤S23204；否则执行步骤S23205至步骤S23207、步骤S23208至步骤S23212或步骤S23213至步骤S23219。
步骤S23204：所述缓存设备将所述目标数据发送至所述用户终端。
可选地，步骤S23204可以包括：所述缓存设备将所述目标数据封装成响应数据包；所述响应数据包的源地址为所述请求数据包的目标地址；在将所述响应数据包发送至所述用户终端。
请参阅图4中步骤S23205-S23207，步骤S23205-S23207是本发明实施例提供的当未缓存目标数据时基站向用户终端发送目标数据的第四种实施方式，包括：
步骤S23205：所述缓存设备向所述源服务器发送所述请求数据包。
具体地，当缓存设备的保存数据列表中不包含该目标数据的标识时，可以执行步骤S23205。
步骤S23206：所述源服务器接收所述请求数据包。
步骤S23207：所述源服务器将所述目标数据发送至所述用户终端。
可选地，步骤S23207还可以包括：当基站检测到所述源服务器向所述用户终端发送的所述目标数据时，基站可以向缓存设备发送所述目标数据，缓存设备可以接收并保存所述目标数据，并将该目标数据发送至用户终端。
请参阅图4中步骤S23208-S23212，步骤S23208-S23212是本发明实施例提供的当未缓存目标数据时基站向用户终端发送目标数据的第五种实施方式，包括：
步骤S23208：所述缓存设备向所述源服务器发送第一请求数据包，所述第一请求数据包用于向所述源服务器请求所述目标数据。
具体地，当缓存设备(基站、本地网关、通过本地网关与基站相连的缓存服务器或者独立地部署于移动网络中的缓存服务器)的保存数据列表中不包含该目标数据的标识时，可以执行步骤S23208。其中，该第一请求数据包的源地址为缓存设备的地址(比如，缓存设备的MAC地址、缓存设备的IP地址等)，目标地址为所述请求数据包的目标地址，该第一请求数据包包括目标数据的标识。
步骤S23209：所述源服务器接收所述第一请求数据包。
步骤S23210：所述源服务器将所述目标数据发送至所述缓存设备。
步骤S23211：所述缓存设备接收从所述源服务器发送的所述目标数据。
步骤S23212：所述缓存设备将所述目标数据发送至所述用户终端。
可选地，步骤S23210之后，缓存设备还可以保存目标数据。
请参阅图4中步骤S23213-S23219，步骤S23213-S23219是本发明实施例提供的当未缓存目标数据时基站向用户终端发送目标数据的第六种实施方式，包括：
步骤S23213：所述缓存设备向所述基站发送信令消息。
其中，缓存设备(比如本地网关、通过本地网关与基站相连的缓存服务 器或者独立地部署于移动网络中的缓存服务器)可以根据数据包生成信令消息，所述信令消息用于指示所述基站向所述源服务器请求目标数据，以及在所述基站接收到所述目标数据后，将所述目标数据发送至所述用户终端。所述信令消息包括用户终端的地址(比如用户终端的MAC地址、用户终端的IP地址等)、目标数据的标识以及请求数据包的目标地址。
步骤S23214：基站在接收所述信令消息。
步骤S23215：所述基站向所述源服务器发送第二请求数据包，所述第二请求数据包用于向所述源服务器请求所述目标数据。
其中，基站可以根据信令消息生成第二请求数据包，该第二请求数据包的源地址为基站的地址(比如，基站的MAC地址、基站的IP地址等)，目标地址为所述请求数据包的目标地址，即源服务器的地址。该第二请求数据包包括目标数据的标识。
步骤S23216：所述源服务器接收所述第二请求数据包。
步骤S23217：所述源服务器将所述目标数据发送至所述基站。
步骤S23218：所述基站接收从所述源服务器返回的所述目标数据，
步骤S23219：所述基站将所述目标数据发送给所述用户终端。
可选地，步骤S23219还可以包括：当基站检测到所述源服务器向所述用户终端发送的所述目标数据时，基站可以向缓存设备发送所述目标数据，缓存设备可以保存所述目标数据。
步骤S23220：所述用户终端接收所述目标数据。
具体地，步骤S23204、步骤S23207、步骤S23212或步骤S23219之后还可以执行步骤S23220。
步骤S240：所述基站将所述请求数据包发送至源服务器。
具体地，当步骤S220的判断结果为是时，即所述请求数据包的目标地址与第一数据缓存列表中的地址信息不匹配，则说明目标数据为缓存设备不可以缓存的数据，可以执行步骤S240至步骤S260。
步骤S250：所述源服务器接收所述请求数据包。
步骤S260：所述源服务器将所述目标数据发送至所述用户终端。
步骤S270：所述用户终端接收所述目标数据。
本发明实施例，当接收用户终端发送的请求数据包后，该请求数据包用于用户终端向源服务器请求目标数据，基站根据第一数据缓存列表，判断该请求数据包的信息是否与第一数据缓存列表中的信息相匹配，如果是，则将存储于缓存设备中的目标数据发送至用户终端。通过将源服务器的数据下沉至距离用户较近的缓存设备(比如基站、本地网关或缓存服务器等)中，以便用户可以直接从缓存设备中获取目标数据，避免了无线网到核心网的回程链路上的开销，从而提高用户终端请求数据的响应速度，提升用户体验。
请参阅图5，图5是本发明实施例提供的一种缓存数据获取方法的另一流程示意图。该缓存数据获取方法包括：
步骤S510：用户终端生成第三请求数据包，所述第三请求数据包用于向源服务器请求目标数据。
具体地，用户终端可以通过应用程序，比如浏览器、视频软件、音乐软件等向源服务器发送上行数据包，即第三请求数据包，请求获取目标数据。第三请求数据包可以是用户终端在检测到针对应用程序内的目标数据的标识或链接的数据获取操作后触发生成的，也可以是应用程序检测到数据需要更新等情况时触发生成的。该数据获取操作可以是针对目标数据的标识或链接的点击操作、双击操作、拖动操作等。该第三请求数据包包括源地址、目标地址以及目标数据的标识。其中，源地址为用户终端的地址，比如，用户终端的IP地址、MAC地址；目标地址为源服务器的地址，比如，源服务器的IP地址；目标数据的标识可以目标数据的URL。例如，该第三请求数据包为Http Get请求，用户终端向源服务器，比如，第一视频网站，请求获取目标数据，比如第一电影。
步骤S520：用户终端根据第二数据缓存列表，判断所述第三请求数据包的信息是否与第二数据缓存列表中的信息相匹配。
其中，用户终端可以配置或获取第二数据缓存列表，该第二数据缓存列表包括至少一个信息，以及所述信息与缓存设备的地址的对应关系；其中，所述信息包括服务器的地址和/或数据的标识。缓存设备的地址可以是缓存设备的IP地址、端口号，也可以是缓存设备的MAC地址、端口号。服务器的 地址可以是源服务器的IP地址、端口号，也可以是服务器的MAC地址、端口号，还可以是可以对应到该源服务器的IP地址或服务器的MAC地址的服务器的名称、域名等以及端口号，服务器的地址用于指示该基站可以缓存的数据所来源的源服务器，例如，该第二数据缓存列表包括第一视频网站的IP地址，则基站可以缓存第一视频网站的数据。可选地，该信息还可以包括数据的URL，用于指示该基站可以缓存的源服务器中的数据，例如，该第二数据缓存列表包括第一视频网站的IP地址以及该第一视频网站的IP地址下的第一视频的URL、第一视频的URL以及第三视频的URL，则基站可以缓存第一视频网站中的第一视频、第一视频以及第三视频，而不能缓存第一视频网站中的第四视频。缓存设备的地址和端口号用于指示缓存设备的地址信息，以实现用户终端与缓存设备的TCP通信连接。其中，第二数据缓存列表包括的信息与缓存设备的地址具有对应关系，比如第一视频网站的IP地址对应第一缓存设备的IP地址和端口号，第二视频网站的IP地址对应第二缓存设备的IP地址和端口号等。可以理解，多个信息可以对应同一缓存设备的地址；该第二数据缓存列表是OTT服务商提供的，缓存设备的地址和端口号则是运营商提供的，缓存设备的地址可以通过基站广播给用户终端。
具体地，用户终端根据第二数据缓存列表，判断所述第三请求数据包的目标地址是否与第二数据缓存列表中的地址信息相匹配，如果是，则第三请求数据包的信息与第二数据缓存列表中的信息相匹配。例如，当第二数据缓存列表包括服务器的地址、端口号时，用户终端可以判断第二数据缓存列表中是否存在与该第三请求数据包的目标地址(即，源服务器的地址、端口号)相一致或相对应的服务器的地址、端口号，可以理解，服务器的MAC地址对应唯一的服务器的IP地址，如果是，则该第三请求数据包的目标地址与第二数据缓存列表中的地址信息相匹配，否则不匹配；又例如，当第二数据缓存列表包括服务器的域名、端口号时，用户终端可以判断第二数据缓存列表中是否存在与第三请求数据包的目标地址(即，源服务器的地址、端口号)相对应的服务器的域名、端口号，如果是，则该请求数据包的目标地址与第一数据缓存列表中的地址信息相匹配，否则不匹配。当第二数据缓存列表包括服务器的地址、数据的标识时，步骤S520还包括用户终端判断第二数据 缓存列表中是否存在与目标数据的标识相一致的数据的标识，当该第三请求数据包的目标地址与第一数据缓存列表中的地址信息相匹配，且第二数据缓存列表中存在与目标数据的标识相一致的数据的标识时，第三请求数据包的信息与第一数据缓存列表中的信息相匹配。当第三请求数据包的信息与第二数据缓存列表中的信息相匹配时，则说明目标数据是缓存设备可以缓存的数据，可以执行步骤S530，从缓存设备中获取该目标数据；否则，则说明目标数据不是缓存设备可以缓存的数据，可以执行步骤S560至步骤S590。
可选地，步骤S520之前，用户终端可以获取第二数据缓存列表，其中，所述第二数据缓存列表中包括至少一个信息，以及所述信息与缓存设备的地址的对应关系；其中，所述信息包括服务器的地址和/或数据的标识。
可以理解，该缓存设备可以是本地网关、通过本地网关与基站相连的缓存服务器或者独立地部署于移动网络中的缓存服务器。可以理解，本发明实施例中缓存设备可以替换为基站、本地网关或缓存服务器。
步骤S530：所述用户终端生成第四请求数据包，所述第四请求数据包的目标地址为匹配的信息对应的缓存设备的地址；所述第四请求数据包用于向所述缓存设备请求所述目标数据。
具体地，用户终端可以根据第二数据缓存列表中信息与缓存设备的地址的对应关系，查找与该第三请求数据包的目标地址相匹配的信息(比如，服务器的地址)对应的缓存设备的地址，进而修改第三请求数据包的目标地址为相匹配的服务器的地址对应的缓存设备的地址，生成第四请求数据包。该第四请求数据包的源地址为用户终端的地址、目标地址为匹配的信息对应的缓存设备的地址，该第四请求数据包包括目标数据的标识，用于向所述缓存设备请求目标数据。
步骤S540：所述用户终端向所述缓存设备发送所述第四请求数据包。
具体地，用户终端向匹配的信息对应的缓存设备发送第四请求数据包。
步骤S550：所述缓存设备在接收所述第四请求数据包，并将所述目标数据发送至用户终端。
具体地，缓存设备(比如，基站、本地网关或缓存服务器等)可以配置保存数据列表，该保存数据列表可以包括至少一个已保存数据的标识，比如 数据的URL。例如，保存数据列表包括第一电影的URL以及第二电影的URL。当缓存设备接收到第四请求数据包后，解析该第四请求数据包的请求内容，即目标数据的标识，将目标数据的标识对应的目标数据发送至用户终端。
可选地，所述缓存设备可以判断保存数据列表中是否包含所述目标数据，如果是，则说明缓存设备中已缓存目标数据，缓存设备响应该第四请求数据包，将存储在缓存设备中所述目标数据的标识对应的所述目标数据发送至所述用户终端，否则，说明缓存设备中没有缓存该目标数据，缓存设备可以向源服务器请求获取目标数据。
可选地，缓存设备可以向源服务器请求获取目标数据的一种实现方式可以是：缓存设备向所述源服务器发送第一请求数据包，所述第一请求数据包用于向所述源服务器请求所述目标数据，该第一请求数据包的目标地址为源服务器的地址，源地址为缓存设备的地址(比如缓存设备的MAC地址、IP地址等)；所述源服务器接收所述第一请求数据包，并响应该第一请求数据包，向该缓存设备返回所述目标数据；缓存设备接收所述目标数据，并将所述目标数据发送至用户终端。可选地，缓存设备还可以保存该目标数据，以及目标数据的标识目标数据的对应关系。可以理解，该缓存设备可以是基站、本地网关或缓存服务器。
可选地，当缓存设备为本地网关或缓存服务器时，缓存设备可以向源服务器请求获取目标数据的另一种实现方式可以是：缓存设备可以向基站发送信令消息，所述信令消息用于指示所述基站向所述源服务器请求目标数据，以及在所述基站接收到所述目标数据后，将所述目标数据发送至所述用户终端或发送至所述缓存设备；基站接收所述信令消息，根据所述信令消息生成第二请求数据包，并向所述源服务器发送第二请求数据包，所述第二请求数据包用于向所述源服务器请求所述目标数据；所述源服务器接收所述第二请求数据包，并响应所述第二请求数据包将所述目标数据发送至所述基站，所述基站接收从所述源服务器返回的所述目标数据，并将所述目标数据发送给所述用户终端或所述缓存设备。当缓存设备接收到所述目标数据后，所述缓存设备可以保存该目标数据，以及目标数据的标识目标数据的对应关系，以及将所述目标数据发送至所述用户终端。
需要说明的是，第三请求数据包可以携带所述目标数据的源服务器地址，以使缓存设备可以获得第三请求数据包的目标地址，即源服务器的地址，生成第一请求数据包，以及信令消息。信令消息可以携带目标数据的源服务器地址以及目标数据的标识，以使基站在可以获得第二请求数据包的目标地址，生成第二请求数据包。缓存设备也可以向用户终端发送源地址请求，请求获取所述目标数据的源服务器的地址，本发明不作限定。
步骤S560：所述用户终端发送所述第三请求数据包。
具体地，当步骤S520的判断结果为否时，即第二数据缓存列表中的服务器的地址不包含第三请求数据包的目标地址时，用户终端可以向源服务器发送该第三请求数据包。
步骤S570：所述源服务器接收所述第三请求数据包。
步骤S580：所述源服务器发送所述目标数据。
具体地，该源服务器接收到用户终端发送的第三请求数据包后，响应该第三请求数据包，向用户终端发送目标数据。
步骤S590：所述用户终端接收所述目标数据。
在图5所示的实施例中，用户终端设置有第二数据缓存列表，该第二数据缓存列表包括至少一个信息，以及该信息与缓存设备的地址的对应关系，当用户终端接收到用于向源服务器请求目标数据的第三请求数据包后，用户终端根据第二数据缓存列表，判断第三请求数据包的信息是否与第二数据缓存列表中的信息相匹配，如果是，说明该目标数据为缓存设备可缓存的数据，用户终端将第三请求数据包的目标地址修改为匹配的信息对应的缓存设备的地址，生成用于向所述缓存设备请求目标数据的第四请求数据包，进而向所述缓存设备发送第四请求数据包，以使所述缓存设备在接收到第四请求数据包后，将目标数据发送至用户终端，此时，用户终端接收该目标数据，从而实现从距离用户较近的缓存设备(比如基站、本地网关或缓存服务器等)中获取目标数据，避免了无线网到核心网的回程链路的开销，从而提高用户终端请求数据的响应速度，提升用户体验。
请参阅图6，图6是本发明实施例提供的一种基站的结构示意图，如图6 所示，该基站包括：
接收模块610，用于接收用户终端发送的请求数据包；所述请求数据包用于向源服务器请求目标数据；
处理模块620，用于根据预存的第一数据缓存列表，判断所述请求数据包的信息是否与第一数据缓存列表中的信息相匹配；
发送模块630，用于当所述请求数据包的信息与所述第一数据缓存列表中的信息相匹配时，将所述目标数据发送至所述用户终端。
可选地，所述处理模块620还用于：获取第一数据缓存列表，其中，所述第一数据缓存列表中包含以下信息中的至少一个：
服务器的地址、数据的标识。
可选地，所述发送模块630还用于：当所述请求数据包的信息与所述第一数据缓存列表中的信息相匹配时，通过与缓存设备建立的第一承载，将所述目标数据发送至所述用户终端。
可选地，所述发送模块630还用于：当所述请求数据包的信息与所述第一数据缓存列表中的信息不匹配时，通过与所述源服务器建立的第二承载，将所述目标数据发送至所述用户终端。
可选地，所述处理模块620还用于：判断是否已缓存所述目标数据，当已缓存所述目标数据时，触发所述发送模块将所述目标数据发送至所述用户终端。
可选地，所述处理模块620还用于：将所述目标数据封装成响应数据包；所述响应数据包的源地址为所述请求数据包的目标地址；
所述发送模块630还用于：将所述响应数据包发送至所述用户终端。
所述发送模块630还用于：当未缓存所述目标数据时，向所述源服务器发送所述请求数据包，以使所述源服务器在接收到所述请求数据包后，所述源服务器将所述目标数据发送至所述用户终端。
可选地，所述处理模块620还用于：当未缓存所述目标数据时，生成第一请求数据包，所述第一请求数据包的源地址为缓存设备的地址，用于向所述源服务器请求目标数据；
所述发送模块630还用于：向所述源服务器发送所述第一请求数据包， 以使所述源服务器在接收到所述第一请求数据包后，将所述目标数据发送至所述缓存设备。
可选地，所述接收模块610还用于：当未缓存所述目标数据时，接收所述缓存设备发送的信令消息；
所述处理模块620还用于：根据所述信令消息，生成第二请求数据包，所述第二请求数据包用于向所述源服务器请求所述目标数据；
所述发送模块630还用于：向所述源服务器发送所述第二请求数据包，以使所述源服务器在接收到所述第二请求数据包后，返回所述目标数据；
所述接收模块610还用于：接收所述源服务器返回的所述目标数据；
所述发送模块630还用于：将所述目标数据发送至所述用户终端。
可选地，所述处理模块620还用于：判断所述缓存设备是否包含所述目标数据，其中，所述缓存设备为本地网关、通过所述本地网关与所述基站相连的所述缓存服务器或者独立地部署于移动网络中的缓存服务器；
所述发送模块630还用于：当所述缓存设备已缓存所述目标数据时，向所述缓存设备发送数据请求，以使所述缓存设备在接收到所述数据请求后，将所述目标数据发送至用户终端。
可选地，所述发送模块630还用于：向所述用户终端发送缓存设备的地址。
需要说明的是，本发明各实施例中的基站中各个模块的功能可根据上述图2所示的方法实施例中的方法具体实现，其具体实现过程可以参照上述图2所述的方法实施例的相关描述，此处不再赘述。
在图6所示的实施例中，当接收用户终端发送的请求数据包后，该请求数据包用于用户终端向源服务器请求目标数据，基站根据第一数据缓存列表，判断该请求数据包的信息是否与第一数据缓存列表中的信息相匹配，如果是，则将存储于缓存设备中的目标数据发送至用户终端。通过将源服务器的数据下沉至距离用户较近的缓存设备(比如基站、本地网关或缓存服务器等)中，以便用户可以直接从缓存设备中获取目标数据，避免了无线网到核心网的回程链路上的开销，从而提高用户终端请求数据的响应速度，提升用户体验。
请参阅图7，图7是本发明实施例提供的另一种基站的结构示意图。如图7所示，该基站包括处理器71、存储器72以及通信接口73。处理器71连接到存储器72和通信接口73，例如处理器71可以通过总线连接到存储器72和通信接口73。
处理器71被配置为支持所述基站执行图2所示的缓存数据获取方法中相应的功能。该处理器71可以是中央处理器(英文：central processing unit，CPU)，网络处理器(英文：network processor，NP)，硬件芯片或者其任意组合。上述硬件芯片可以是专用集成电路(英文：application-specific integrated circuit，ASIC)，可编程逻辑器件(英文：programmable logic device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(英文：complex programmable logic device，CPLD)，现场可编程逻辑门阵列(英文：field-programmable gate array，FPGA)，通用阵列逻辑(英文：generic array logic,GAL)或其任意组合。
存储器72存储器用于存储图2所示的缓存数据获取方法中的目标数据、第一数据缓存列表以及程序代码等。存储器72可以包括易失性存储器(英文：volatile memory)，例如随机存取存储器(英文：random access memory，缩写：RAM)；存储器72也可以包括非易失性存储器(英文：non-volatile memory)，例如只读存储器(英文：read-only memory，缩写：ROM)，快闪存储器(英文：flash memory)，硬盘(英文：hard disk drive，缩写：HDD)或固态硬盘(英文：solid-state drive，缩写：SSD)；存储器72还可以包括上述种类的存储器的组合。
通信接口73用于与用户终端、本地网关、缓存服务器或源服务器等设备进行通信以收发上述方法中所涉及的消息。
处理器71可以调用所述程序代码以执行以下操作：
通过通信接口73接收用户终端发送的请求数据包；所述请求数据包用于向源服务器请求目标数据；
根据第一数据缓存列表，判断所述请求数据包的信息是否与所述第一数据缓存列表中的信息相匹配；
当所述请求数据包的信息与所述第一数据缓存列表中的信息相匹配时， 通过通信接口73将所述目标数据发送至用户终端。
可选地，处理器71根据第一数据缓存列表，判断所述请求数据包的信息是否与所述第一数据缓存列表中的信息相匹配之前，所述处理器71还用于执行：
通过通信接口73获取第一数据缓存列表，其中，所述第一数据缓存列表中包含以下信息中的至少一个：
服务器的地址、数据的标识。
可选地，当所述请求数据包的信息与所述第一数据缓存列表中的信息相匹配时，所述通过通信接口73将所述目标数据发送至用户终端包括：通过与缓存设备建立的第一承载，通过通信接口73将所述目标数据发送至所述用户终端。
可选地，处理器71还用于执行：当所述请求数据包的信息与所述第一数据缓存列表中的信息不匹配时，通过与所述源服务器建立的第二承载，通过通信接口73将所述目标数据发送至所述用户终端。
可选地，处理器71通过通信接口73将所述目标数据发送至所述用户终端之前，处理器71还用于执行：
判断是否已缓存所述目标数据；
当已缓存所述目标数据时，则执行所述通过通信接口73将所述目标数据发送至用户终端的步骤。
可选地，处理器71通过通信接口73将所述目标数据发送至用户终端包括：
将所述目标数据封装成响应数据包；所述响应数据包的源地址为所述请求数据包的目标地址；
所述通过通信接口73将所述响应数据包发送至用户终端。
可选地，处理器71还用于执行：当未缓存所述目标数据时，通过通信接口73向所述源服务器发送所述请求数据包，以使所述源服务器在接收到所述请求数据包后，所述源服务器将所述目标数据发送至用户终端。
可选地，处理器71还用于执行：当未缓存所述目标数据时，生成第一请求数据包，所述第一请求数据包的源地址为缓存设备的地址，用于向所述源 服务器请求目标数据；
通过通信接口73向所述源服务器发送所述第一请求数据包，以使所述源服务器在接收到所述第一请求数据包后，将所述目标数据发送至所述缓存设备。
可选地，处理器71还用于执行：当未缓存所述目标数据时，通过通信接口73接收所述缓存设备发送的信令消息；
根据所述信令消息，生成第二请求数据包，所述第二请求数据包用于向所述源服务器请求所述目标数据；
通过通信接口73向所述源服务器发送所述第二请求数据包，以使所述源服务器在接收到所述第二请求数据包后，返回所述目标数据；
通过通信接口73接收所述源服务器返回的所述目标数据，并通过通信接口73将所述目标数据发送至用户终端。
可选地，处理器71判断是否已缓存所述目标数据包括：
判断缓存设备是否已缓存所述目标数据，其中，所述缓存设备为本地网关、通过本地网关与基站相连的缓存服务器或者独立地部署于移动网络中的缓存服务器；
当所述缓存设备已缓存所述目标数据时，所述通过通信接口73将所述目标数据发送至所述用户终端包括：通过通信接口73向所述缓存设备发送数据请求，以使所述缓存设备在接收到所述数据请求后，将所述目标数据发送至用户终端。
可选地，处理器71还用于执行：通过通信接口73向所述用户终端发送缓存设备的地址。
请参阅图8，图8是本发明实施例提供的一种缓存设备的结构示意图，如图8所示，该缓存设备包括：
接收模块810，用于接收用户终端发送的请求数据包；其中，所述请求数据包为用户终端发送给基站，用于请求目标数据；当所述基站接收到所述请求数据包时，且所述基站判断所述请求数据包的信息与第一数据缓存列表中的信息相匹配时或所述请求数据包的目标地址为缓存设备的地址时，所述 基站将所述请求数据包发送至缓存设备；
发送模块820，用于将所述目标数据发送至所述用户终端。
可以理解，当所述请求数据包的目标地址为缓存设备的地址时，所述请求数据包即为图5所述的方法实施例中第三请求数据包。
可选地，所述缓存设备还包括：处理模块，用于判断是已缓存所述目标数据；当已缓存所述目标数据时，触发所述发送模块820将所述目标数据发送至所述用户终端。
可选地，所述处理模块还用于：将所述目标数据封装成响应数据包；所述响应数据包的源地址为所述请求数据包的目标地址；
所述发送模块820还用于：将所述响应数据包发送至所述用户终端。
可选地，所述发送模块820还用于：当所述基站判断所述请求数据包的信息与第一数据缓存列表中的信息相匹配，且未缓存所述目标数据时，向所述源服务器发送所述请求数据包，以使所述源服务器在接收到所述请求数据包后，所述源服务器将所述目标数据发送至所述用户终端。
可选地，所述发送模块820还用于，当未缓存所述目标数据时，向所述源服务器发送第一请求数据包，以使所述源服务器在接收到所述第一请求数据包后，所述源服务器返回所述目标数据，所述第一请求数据包用于向所述源服务器请求所述目标数据；
所述接收模块810还用于：接收从所述源服务器返回的所述目标数据；
所述发送模块820还用于：将所述目标数据发送至所述用户终端。
可选地，所述发送模块820还用于：当未缓存所述目标数据时，向所述基站发送信令消息，以使所述基站在接收到所述信令消息后，所述基站向所述源服务器发送第二请求数据包，所述第二请求数据包用于所述基站向所述源服务器请求所述目标数据；所述基站接收从所述源服务器返回的所述目标数据，并将所述目标数据发送给所述用户终端。
需要说明的是，本发明各实施例中的缓存设备中各个模块的功能可根据上述图2或图5所示的方法实施例中的方法具体实现，其具体实现过程可以参照上述图2或图5所述的方法实施例的相关描述，此处不再赘述。
在图8所示的实施例中，缓存设备接收用户终端发送的请求数据包，其 中，该请求数据包为用户终端发送给基站，用于请求目标数据；当基站接收到请求数据包时，且该基站判断请求数据包的信息与第一数据缓存列表中的信息相匹配时或该请求数据包的目标地址为缓存设备的地址时，基站将该请求数据包发送至缓存设备，此时缓存设备将目标数据发送至用户终端，通过将源服务器的数据下沉至部署于移动网络中距离用户较近的缓存设备(基站、本地网关、通过本地网关与基站相连的缓存服务器或者独立地部署于移动网络中的缓存服务器)中，以便用户可以直接从缓存设备中获取目标数据，避免了无线网到核心网的回程链路上的开销，从而提高用户终端请求数据的响应速度，提升用户体验。
请参阅图9，图9是本发明实施例提供的另一种缓存设备的结构示意图。如图9所示，该缓存设备包括处理器91、存储器92以及通信接口93。处理器91连接到存储器92和通信接口93，例如处理器91可以通过总线连接到存储器92和通信接口93。
处理器91被配置为支持所述缓存设备执行图2或图5所示的缓存数据获取方法中相应的功能。该处理器91可以是中央处理器(英文：central processing unit，CPU)，网络处理器(英文：network processor，NP)，硬件芯片或者其任意组合。上述硬件芯片可以是专用集成电路(英文：application-specific integrated circuit，ASIC)，可编程逻辑器件(英文：programmable logic device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(英文：complex programmable logic device，CPLD)，现场可编程逻辑门阵列(英文：field-programmable gate array，FPGA)，通用阵列逻辑(英文：generic array logic,GAL)或其任意组合。
存储器92存储器用于存储图2或图5所示的缓存数据获取方法中的目标数据以及程序代码等。存储器92可以包括易失性存储器(英文：volatile memory)，例如随机存取存储器(英文：random access memory，缩写：RAM)；存储器92也可以包括非易失性存储器(英文：non-volatile memory)，例如只读存储器(英文：read-only memory，缩写：ROM)，快闪存储器(英文：flash memory)，硬盘(英文：hard disk drive，缩写：HDD)或固态硬盘(英文： solid-state drive，缩写：SSD)；存储器92还可以包括上述种类的存储器的组合。
通信接口93用于与用户终端、源服务器等进行通信以收发上述方法中所涉及的消息。
处理器91可以调用所述程序代码以执行以下操作：
通过通信接口93接收用户终端发送的请求数据包；其中，所述请求数据包为用户终端发送给基站，用于请求目标数据；当所述基站接收到所述请求数据包时，且所述基站判断所述请求数据包的信息与第一数据缓存列表中的信息相匹配时或所述请求数据包的目标地址为缓存设备的地址时，所述基站将所述请求数据包发送至缓存设备；
通过通信接口93将所述目标数据发送至所述用户终端。
可以理解，当所述请求数据包的目标地址为缓存设备的地址时，所述请求数据包即为图5所述的方法实施例中第三请求数据包。
可选地，处理器91通过通信接口93将所述目标数据发送至所述用户终端包括：
判断是否已缓存所述目标数据；
当已缓存所述目标数据时，通过通信接口93将所述目标数据发送至所述用户终端。
可选地，处理器91通过通信接口93将所述目标数据发送至所述用户终端包括：
将所述目标数据封装成响应数据包；所述响应数据包的源地址为所述请求数据包的目标地址；
通过通信接口93将所述响应数据包发送至所述用户终端。
可选地，当所述基站判断所述请求数据包的信息与第一数据缓存列表中的信息相匹配，且未缓存所述目标数据时，处理器91还用于执行：
通过通信接口93向所述源服务器发送所述请求数据包，以使所述源服务器在接收到所述请求数据包后，所述源服务器将所述目标数据发送至所述用户终端。
可选地，当未缓存所述目标数据时，处理器91还用于执行：
通过通信接口93向所述源服务器发送第一请求数据包，以使所述源服务器在接收到所述第一请求数据包后，所述源服务器返回所述目标数据，所述第一请求数据包用于向所述源服务器请求所述目标数据；
通过通信接口93接收从所述源服务器返回的所述目标数据，并将所述目标数据发送至所述用户终端。
可选地，当未缓存所述目标数据时，处理器91还用于执行：
通过通信接口93向所述基站发送信令消息，以使所述基站在接收到所述信令消息后，所述基站向所述源服务器发送第二请求数据包，所述第二请求数据包用于向所述源服务器请求所述目标数据；所述基站接收从所述源服务器返回的所述目标数据，并将所述目标数据发送给所述用户终端。
请参阅图10，图10是本发明实施例提供的一种用户终端的结构示意图，如图10所示，该用户终端1000包括：
处理模块1010，用于生成第三请求数据包；所述第三请求数据包用于向源服务器请求目标数据；以及根据第二数据缓存列表，判断所述第三请求数据包的信息是否与第二数据缓存列表中的信息相匹配；所述第二数据缓存列表包括至少一个信息，以及所述信息与缓存设备的地址的对应关系；
所述处理模块1010还用于：当所述第三请求数据包的信息与第二数据缓存列表中的信息相匹配时，生成第四请求数据包，所述第四请求数据包的目标地址为匹配的信息对应的缓存设备的地址；所述第四请求数据包用于向所述缓存设备请求所述目标数据；
发送模块1020，用于向所述缓存设备发送所述第四请求数据包，以使所述缓存设备在接收到所述第四请求数据包后，将所述目标数据发送至用户终端；
接收模块1030，用于接收所述目标数据。
可选地，所述发送模块1020还用于：当所述第三请求数据包的信息与第二数据缓存列表中的信息不匹配时，发送所述第三请求数据包，以使所述源服务器在接收到所述第三请求数据包后，将所述目标数据发送至所述用户终端；
所述接收模块1030还用于：接收所述目标数据。
可选地，所述处理模块1010还用于：
获取第二数据缓存列表，其中，所述第二数据缓存列表中包括至少一个信息，以及所述信息与缓存设备的地址的对应关系；其中，所述信息包括服务器的地址和/或数据的标识。
需要说明的是，本发明各实施例中的用户终端中各个模块的功能可根据上述图5所示的方法实施例中的方法具体实现，其具体实现过程可以参照上述图5所述的方法实施例的相关描述，此处不再赘述。
在图10所示的实施例中，本技术方案，用户终端设置有第二数据缓存列表，该第二数据缓存列表包括至少一个信息，以及该信息与缓存设备的地址的对应关系，当用户终端接收到用于向源服务器请求目标数据的第三请求数据包后，用户终端根据第二数据缓存列表，判断第三请求数据包的信息是否与第二数据缓存列表中的信息相匹配，如果是，说明该目标数据为缓存设备可缓存的数据，用户终端将第三请求数据包的目标地址修改为匹配的信息对应的缓存设备的地址，生成用于向所述缓存设备请求目标数据的第四请求数据包，进而向所述缓存设备发送第四请求数据包，以使所述缓存设备在接收到第四请求数据包后，将目标数据发送至用户终端，此时，用户终端接收该目标数据，从而实现从距离用户较近的缓存设备(比如基站、本地网关或缓存服务器等)中获取目标数据，避免了无线网到核心网的回程链路的开销，从而提高用户终端请求数据的响应速度，提升用户体验。
请参阅图11，图11是本发明实施例提供的另一种用户终端的结构示意图。如图11所示，该用户终端包括处理器111、存储器112以及通信接口113。处理器111连接到存储器112和通信接口113，例如处理器111可以通过总线连接到存储器112和通信接口113。
处理器111被配置为支持所述用户终端执行图5所示的缓存数据获取方法中相应的功能。该处理器111可以是中央处理器(英文：central processing unit，CPU)，网络处理器(英文：network processor，NP)，硬件芯片或者其任意组合。上述硬件芯片可以是专用集成电路(英文：application-specific  integrated circuit，ASIC)，可编程逻辑器件(英文：programmable logic device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(英文：complex programmable logic device，CPLD)，现场可编程逻辑门阵列(英文：field-programmable gate array，FPGA)，通用阵列逻辑(英文：generic array logic,GAL)或其任意组合。
存储器112存储器用于存储图5所示的缓存数据获取方法中的第二数据缓存列表以及程序代码等。存储器112可以包括易失性存储器(英文：volatile memory)，例如随机存取存储器(英文：random access memory，缩写：RAM)；存储器112也可以包括非易失性存储器(英文：non-volatile memory)，例如只读存储器(英文：read-only memory，缩写：ROM)，快闪存储器(英文：flash memory)，硬盘(英文：hard disk drive，缩写：HDD)或固态硬盘(英文：solid-state drive，缩写：SSD)；存储器112还可以包括上述种类的存储器的组合。
通信接口113用于与基站、本地网关、缓存服务器或源服务器进行通信以收发上述方法中所涉及的消息。
处理器111可以调用所述程序代码以执行以下操作：
生成第三请求数据包；所述第三请求数据包用于向源服务器请求目标数据；
根据第二数据缓存列表，判断所述第三请求数据包的信息是否与第二数据缓存列表中的信息相匹配；所述第二数据缓存列表包括至少一个信息，以及所述信息与缓存设备的地址的对应关系；
当所述第三请求数据包的信息与第二数据缓存列表中的信息相匹配时，生成第四请求数据包，所述第四请求数据包的目标地址为匹配的信息对应的缓存设备的地址；所述第四请求数据包用于向所述缓存设备请求所述目标数据；
通过通信接口113向所述缓存设备发送所述第四请求数据包，以使所述缓存设备在接收到所述第四请求数据包后，将所述目标数据发送至用户终端；
通过通信接口113接收所述目标数据。
可选地，当所述第三请求数据包的信息与第二数据缓存列表中的信息不 匹配时，处理器111还用于执行：
通过通信接口113发送所述第三请求数据包，以使所述源服务器在接收到所述第三请求数据包后，将所述目标数据发送至所述用户终端；
通过通信接口113接收所述目标数据。
可选地，处理器111判断所述第三请求数据包的信息是否与第二数据缓存列表中的信息相匹配之前，处理器111还用于执行：
通过通信接口113获取第二数据缓存列表，其中，所述第二数据缓存列表中包括至少一个信息，以及所述信息与缓存设备的地址的对应关系；其中，所述信息包括服务器的地址和/或数据的标识。
请参阅图12，图12是本发明实施例提供的又一种基站的结构示意图，如图12所示，该基站包括：
接收器1210，用于接收用户终端发送的请求数据包；所述请求数据包用于向源服务器请求目标数据；
处理器1220，用于根据预存的第一数据缓存列表，判断所述请求数据包的信息是否与第一数据缓存列表中的信息相匹配；
发送器1230，用于当所述请求数据包的信息与所述第一数据缓存列表中的信息相匹配时，将所述目标数据发送至所述用户终端。
可选地，所述处理器1220还用于：获取第一数据缓存列表，其中，所述第一数据缓存列表中包含以下信息中的至少一个：
服务器的地址、数据的标识。
可选地，所述发送器1230还用于：当所述请求数据包的信息与所述第一数据缓存列表中的信息相匹配时，通过所述基站与缓存设备建立的第一承载，将所述目标数据发送至所述用户终端；
可选地，所述发送器1230还用于：当所述请求数据包的信息与所述第一数据缓存列表中的信息不匹配时，通过所述基站与所述源服务器建立的第二承载，将所述目标数据发送至所述用户终端。
可选地，所述处理器1220还用于：判断是否已缓存所述目标数据，当已缓存所述目标数据时，触发所述发送器将所述目标数据发送至所述用户终端。
可选地，所述处理器1220还用于：将所述目标数据封装成响应数据包；所述响应数据包的源地址为所述请求数据包的目标地址；
所述发送器1220还用于：将所述响应数据包发送至所述用户终端。
可选地，所述发送器1230还用于：当未缓存所述目标数据时，向所述源服务器发送所述请求数据包，以使所述源服务器在接收到所述请求数据包后，所述源服务器将所述目标数据发送至所述用户终端。
可选地，所述处理器1220还用于：当未缓存所述目标数据时，生成第一请求数据包，所述第一请求数据包的源地址为缓存设备的地址，用于向所述源服务器请求目标数据；
所述发送器1230还用于：向所述源服务器发送所述第一请求数据包，以使所述源服务器在接收到所述第一请求数据包后，将所述目标数据发送至所述缓存设备。
可选地，所述接收器1210还用于：当未缓存所述目标数据时，接收所述缓存设备发送的信令消息；
所述处理器1220还用于：根据所述信令消息，生成第二请求数据包，所述第二请求数据包用于向所述源服务器请求所述目标数据；
所述发送器1230还用于：向所述源服务器发送所述第二请求数据包，以使所述源服务器在接收到所述第二请求数据包后，返回所述目标数据；
所述接收器1210还用于：接收所述源服务器返回的所述目标数据；
所述发送器1230还用于：将所述目标数据发送至所述用户终端。
可选地，所述处理器1220还用于：判断所述缓存设备是否包含所述目标数据，其中，所述缓存设备为本地网关、通过所述本地网关与所述基站相连的所述缓存服务器或者独立地部署于移动网络中的缓存服务器；
所述发送器1230还用于：当所述缓存设备已缓存所述目标数据时，向所述缓存设备发送数据请求，以使所述缓存设备在接收到所述数据请求后，将所述目标数据发送至用户终端。
可选地，所述发送器1230还用于：向所述用户终端发送缓存设备的地址。
需要说明的是，本发明各实施例中的基站中接收器1210、处理器1220、以及发送器1230的功能可根据上述图2所述的方法实施例中的方法具体实 现，其具体实现过程可以参照上述图2所述的方法实施例的相关描述，此处不再赘述。
请参阅图13，图13是本发明实施例提供的又一种缓存设备的结构示意图，如图13所示，该缓存设备包括：
接收器1310，用于接收用户终端发送的请求数据包；其中，所述请求数据包为用户终端发送给基站，用于请求目标数据；当所述基站接收到所述请求数据包时，且所述基站判断所述请求数据包的信息与第一数据缓存列表中的信息相匹配时或所述请求数据包的目标地址为缓存设备的地址时，所述基站将所述请求数据包发送至缓存设备；
发送器1320，用于将所述目标数据发送至所述用户终端。
可以理解，当所述请求数据包的目标地址为缓存设备的地址时，所述请求数据包即为图5所述的方法实施例中第三请求数据包。
可选地，所述缓存设备还包括：
处理器：用于判断是已缓存所述目标数据；当已缓存所述目标数据时，触发所述发送器将所述目标数据发送至所述用户终端。
可选地，所述处理器还用于：将所述目标数据封装成响应数据包；所述响应数据包的源地址为所述请求数据包的目标地址；
所述发送器1320还用于：将所述响应数据包发送至所述用户终端。
可选地，所述发送器1320还用于：
当所述基站判断所述请求数据包的信息与第一数据缓存列表中的信息相匹配，且未缓存所述目标数据时，向所述源服务器发送所述请求数据包，以使所述源服务器在接收到所述请求数据包后，所述源服务器将所述目标数据发送至所述用户终端。
可选地，所述发送器1320还用于，当未缓存所述目标数据时，向所述源服务器发送第一请求数据包，以使所述源服务器在接收到所述第一请求数据包后，所述源服务器返回所述目标数据，所述第一请求数据包用于向所述源服务器请求所述目标数据；
所述接收器1310还用于：接收从所述源服务器返回的所述目标数据；
所述发送器1320还用于：将所述目标数据发送至所述用户终端。
可选地，所述发送器1320还用于：当未缓存所述目标数据时，向所述基站发送信令消息，以使所述基站在接收到所述信令消息后，所述基站向所述源服务器发送第二请求数据包，所述第二请求数据包用于所述基站向所述源服务器请求所述目标数据；所述基站接收从所述源服务器返回的所述目标数据，并将所述目标数据发送给所述用户终端。
需要说明的是，本发明各实施例中的缓存设备中接收器1310、发送器1320以及处理器的功能可根据上述图2或图5所述方法实施例中的方法具体实现，其具体实现过程可以参照上述图2或图5所述的方法实施例的相关描述，此处不再赘述。
请参阅图14，图14是本发明实施例提供的又一种用户终端的结构示意图，如图14所示，该用户终端包括：
处理器1410，用于生成第三请求数据包；所述第三请求数据包用于向源服务器请求目标数据；以及根据第二数据缓存列表，判断所述第三请求数据包的信息是否与第二数据缓存列表中的信息相匹配；所述第二数据缓存列表包括至少一个信息，以及所述信息与缓存设备的地址的对应关系；
所述处理器1410还用于：当所述第三请求数据包的信息与第二数据缓存列表中的信息相匹配时，生成第四请求数据包，所述第四请求数据包的目标地址为匹配的信息对应的缓存设备的地址；所述第四请求数据包用于向所述缓存设备请求所述目标数据；
发送器1420，用于向所述缓存设备发送所述第四请求数据包，以使所述缓存设备在接收到所述第四请求数据包后，将所述目标数据发送至用户终端；
接收器1430，用于接收所述目标数据。
可选地，所述发送器1420还用于：当所述第三请求数据包的信息与第二数据缓存列表中的信息不匹配时，发送所述第三请求数据包，以使所述源服务器在接收到所述第三请求数据包后，将所述目标数据发送至所述用户终端；
所述接收器1430还用于：接收所述目标数据。
可选地，所述处理器1410还用于：
获取第二数据缓存列表，其中，所述第二数据缓存列表中包括至少一个信息，以及所述信息与缓存设备的地址的对应关系；其中，所述信息包括服务器的地址和/或数据的标识。
需要说明的是，本发明各实施例中的用户终端中处理器1410、发送器1420以及接收器1430的功能可根据上述图5所述的方法实施例中的方法具体实现，其具体实现过程可以参照上述图5所述的方法实施例的相关描述，此处不再赘述。
需要说明的是，对于前述的各个方法实施例，为了简单描述，故将其都表述为一系列的动作组合，但是本领域技术人员应该知悉，本发明并不受所描述的动作顺序的限制，因为依据本发明，某一些步骤可以采用其他顺序或者同时进行。其次，本领域技术人员也应该知悉，说明书中所描述的实施例均属于优选实施例，所涉及的动作和模块并不一定是本发明所必须的。
在上述实施例中，对各个实施例的描述都各有侧重，某个实施例中没有详细描述的部分，可以参见其他实施例的相关描述。
本领域普通技术人员可以理解上述实施例的各种方法中的全部或部分步骤是可以通过程序来指令相关的硬件来完成，该程序可以存储于一计算机可读存储介质中，存储介质可以包括：闪存盘、只读存储器(Read-Only Memory，ROM)、随机存取器(Random Access Memory，RAM)、磁盘或光盘等。
以上对本发明实施例所提供的内容下载方法及相关设备、系统进行了详细介绍，本文中应用了具体个例对本发明的原理及实施方式进行了阐述，以上实施例的说明只是用于帮助理解本发明的方法及其核心思想；同时，对于本领域的一般技术人员，依据本发明的思想，在具体实施方式及应用范围上均会有改变之处，综上所述，本说明书内容不应理解为对本发明的限制。

Claims (64)

  1. 一种缓存数据获取方法，其特征在于，包括：
    基站接收用户终端发送的请求数据包；所述请求数据包用于向源服务器请求目标数据；
    所述基站根据第一数据缓存列表，判断所述请求数据包的信息是否与所述第一数据缓存列表中的信息相匹配；
    当所述请求数据包的信息与所述第一数据缓存列表中的信息相匹配时，所述基站将所述目标数据发送至用户终端。
  2. 如权利要求1所述的方法，其特征在于，所述基站根据第一数据缓存列表，判断所述请求数据包的信息是否与所述第一数据缓存列表中的信息相匹配之前，所述方法还包括：
    所述基站获取第一数据缓存列表，其中，所述第一数据缓存列表中包含以下信息中的至少一个：
    服务器的地址、数据的标识。
  3. 如权利要求1所述的方法，其特征在于，所述基站将所述目标数据发送至用户终端包括：所述基站通过所述基站与缓存设备建立的第一承载，将所述目标数据发送至所述用户终端。
  4. 如权利要求1所述的方法，其特征在于，所述方法还包括：
    当所述请求数据包的信息与所述第一数据缓存列表中的信息不匹配时，所述基站通过所述基站与所述源服务器建立的第二承载，将所述目标数据发送至所述用户终端。
  5. 如权利要求1所述的方法，其特征在于，所述将所述目标数据发送至所述用户终端之前，所述方法还包括：
    所述基站判断是否已缓存所述目标数据；
    当已缓存所述目标数据时，则执行所述基站将所述目标数据发送至用户终端的步骤。
  6. 如权利要求1-5任一权利要求所述的方法，其特征在于，所述基站将所述目标数据发送至用户终端包括：
    所述基站将所述目标数据封装成响应数据包，所述响应数据包的源地址为所述请求数据包的目标地址；
    所述基站将所述响应数据包发送至用户终端。
  7. 如权利要求5所述的方法，其特征在于，当未缓存所述目标数据时，所述方法还包括：
    所述基站向所述源服务器发送所述请求数据包，以使所述源服务器在接收到所述请求数据包后，所述源服务器将所述目标数据发送至用户终端。
  8. 如权利要求5所述的方法，其特征在于，当未缓存所述目标数据时，所述方法还包括：
    所述基站生成第一请求数据包，所述第一请求数据包的源地址为缓存设备的地址，用于向所述源服务器请求目标数据；
    所述基站向所述源服务器发送所述第一请求数据包，以使所述源服务器在接收到所述第一请求数据包后，将所述目标数据发送至所述缓存设备。
  9. 如权利要求5所述的方法，其特征在于，当未缓存所述目标数据时，所述方法还包括：
    所述基站接收所述缓存设备发送的信令消息；
    所述基站根据所述信令消息，生成第二请求数据包，所述第二请求数据包用于向所述源服务器请求所述目标数据；
    所述基站向所述源服务器发送所述第二请求数据包，以使所述源服务器在接收到所述第二请求数据包后，返回所述目标数据；
    所述基站接收所述源服务器返回的所述目标数据，并将所述目标数据发 送至用户终端。
  10. 如权利要求5所述的方法，其特征在于，所述判断是否已缓存所述目标数据包括：
    所述基站判断缓存设备是否已缓存所述目标数据，其中，所述缓存设备为本地网关、通过本地网关与基站相连的缓存服务器或者独立地部署于移动网络中的缓存服务器；
    当所述缓存设备已缓存所述目标数据时，所述基站将所述目标数据发送至所述用户终端包括：
    所述基站向所述缓存设备发送数据请求，以使所述缓存设备在接收到所述数据请求后，将所述目标数据发送至用户终端。
  11. 权利要求1所述的方法，其特征在于，所述方法还包括：
    所述基站向所述用户终端发送缓存设备的地址。
  12. 一种缓存数据获取方法，其特征在于，包括：
    缓存设备接收用户终端发送的请求数据包；其中，所述请求数据包为用户终端发送给基站，用于请求目标数据；当所述基站接收到所述请求数据包时，且所述基站判断所述请求数据包的信息与第一数据缓存列表中的信息相匹配时或所述请求数据包的目标地址为缓存设备的地址时，所述基站将所述请求数据包发送至缓存设备；
    所述缓存设备将所述目标数据发送至所述用户终端。
  13. 如权利要求12所述的方法，其特征在于，所述缓存设备将所述目标数据发送至所述用户终端包括：
    所述缓存设备判断是否已缓存所述目标数据；
    当已缓存所述目标数据时，所述缓存设备将所述目标数据发送至所述用户终端。
  14. 如权利要求12或13所述的方法，其特征在于，所述缓存设备将所述目标数据发送至所述用户终端包括：
    所述缓存设备将所述目标数据封装成响应数据包，所述响应数据包的源地址为所述请求数据包的目标地址；
    所述缓存设备将所述响应数据包发送至所述用户终端。
  15. 如权利要求13所述的方法，其特征在于，当所述基站判断所述请求数据包的信息与第一数据缓存列表中的信息相匹配，且未缓存所述目标数据时，所述方法还包括：
    所述缓存设备向所述源服务器发送所述请求数据包，以使所述源服务器在接收到所述请求数据包后，所述源服务器将所述目标数据发送至所述用户终端。
  16. 如权利要求13所述的方法，其特征在于，当未缓存所述目标数据时，所述方法还包括：
    所述缓存设备向所述源服务器发送第一请求数据包，以使所述源服务器在接收到所述第一请求数据包后，所述源服务器返回所述目标数据，所述第一请求数据包用于向所述源服务器请求所述目标数据；
    所述缓存设备接收从所述源服务器返回的所述目标数据，并将所述目标数据发送至所述用户终端。
  17. 如权利要求13所述的方法，其特征在于，当未缓存所述目标数据时，所述方法还包括：
    所述缓存设备向所述基站发送信令消息，以使所述基站在接收到所述信令消息后，所述基站向所述源服务器发送第二请求数据包，所述第二请求数据包用于向所述源服务器请求所述目标数据，所述基站接收从所述源服务器返回的所述目标数据，并将所述目标数据发送给所述用户终端。
  18. 一种缓存数据获取方法，其特征在于，包括：
    用户终端生成第三请求数据包，所述第三请求数据包用于向源服务器请求目标数据；
    所述用户终端根据第二数据缓存列表，判断所述第三请求数据包的信息是否与第二数据缓存列表中的信息相匹配，所述第二数据缓存列表包括至少一个信息，以及所述信息与缓存设备的地址的对应关系；
    当所述第三请求数据包的信息与第二数据缓存列表中的信息相匹配时，所述用户终端生成第四请求数据包，所述第四请求数据包的目标地址为匹配的信息对应的缓存设备的地址，所述第四请求数据包用于向所述缓存设备请求所述目标数据；
    所述用户终端向所述缓存设备发送所述第四请求数据包，以使所述缓存设备在接收到所述第四请求数据包后，将所述目标数据发送至用户终端；
    所述用户终端接收所述目标数据。
  19. 如权利要求18所述的方法，其特征在于，当所述第三请求数据包的信息与第二数据缓存列表中的信息不匹配时，所述方法还包括：
    所述用户终端发送所述第三请求数据包，以使所述源服务器在接收到所述第三请求数据包后，将所述目标数据发送至所述用户终端；
    所述用户终端接收所述目标数据。
  20. 如权利要求18所述的方法，其特征在于，判断所述第三请求数据包的信息是否与第二数据缓存列表中的信息相匹配之前，所述方法还包括：
    所述用户终端获取第二数据缓存列表，其中，所述第二数据缓存列表中包括至少一个信息，以及所述信息与缓存设备的地址的对应关系；其中，所述信息包括服务器的地址和/或数据的标识。
  21. 一种基站，其特征在于，包括：
    接收模块，用于接收用户终端发送的请求数据包；所述请求数据包用于向源服务器请求目标数据；
    处理模块，用于根据预存的第一数据缓存列表，判断所述请求数据包的 信息是否与第一数据缓存列表中的信息相匹配；
    发送模块，用于当所述请求数据包的信息与所述第一数据缓存列表中的信息相匹配时，将所述目标数据发送至所述用户终端。
  22. 如权利要求21所述的基站，其特征在于，
    所述处理模块还用于：获取第一数据缓存列表，其中，所述第一数据缓存列表中包含以下信息中的至少一个：
    服务器的地址、数据的标识。
  23. 如权利要求21所述的基站，其特征在于，所述发送模块还用于：通过所述基站与缓存设备建立的第一承载，将所述目标数据发送至所述用户终端。
  24. 如权利要求21所述的基站，其特征在于，所述发送模块还用于：当所述请求数据包的信息与所述第一数据缓存列表中的信息不匹配时，通过所述基站与所述源服务器建立的第二承载，将所述目标数据发送至所述用户终端。
  25. 如权利要求21所述的基站，其特征在于，
    所述处理模块还用于：判断是否已缓存所述目标数据，当已缓存所述目标数据时，触发所述发送模块将所述目标数据发送至所述用户终端。
  26. 如权利要求21-25任一权利要求所述的基站，其特征在于，
    所述处理模块还用于：将所述目标数据封装成响应数据包；所述响应数据包的源地址为所述请求数据包的目标地址；
    所述发送模块还用于：将所述响应数据包发送至所述用户终端。
  27. 如权利要求25所述的基站，其特征在于，所述发送模块还用于：当未缓存所述目标数据时，向所述源服务器发送所述请求数据包，以使所述源 服务器在接收到所述请求数据包后，所述源服务器将所述目标数据发送至所述用户终端。
  28. 如权利要求25所述的基站，其特征在于，
    所述处理模块还用于：当未缓存所述目标数据时，生成第一请求数据包，所述第一请求数据包的源地址为缓存设备的地址，用于向所述源服务器请求目标数据；
    所述发送模块还用于：向所述源服务器发送所述第一请求数据包，以使所述源服务器在接收到所述第一请求数据包后，将所述目标数据发送至所述缓存设备。
  29. 如权利要求25所述的基站，其特征在于，
    所述接收模块还用于：当未缓存所述目标数据时，接收所述缓存设备发送的信令消息；
    所述处理模块还用于：根据所述信令消息，生成第二请求数据包，所述第二请求数据包用于向所述源服务器请求所述目标数据；
    所述发送模块还用于：向所述源服务器发送所述第二请求数据包，以使所述源服务器在接收到所述第二请求数据包后，返回所述目标数据；
    所述接收模块还用于：接收所述源服务器返回的所述目标数据；
    所述发送模块还用于：将所述目标数据发送至所述用户终端。
  30. 如权利要求25所述的基站，其特征在于，
    所述处理模块还用于：判断所述缓存设备是否包含所述目标数据，其中，所述缓存设备为本地网关、通过所述本地网关与所述基站相连的所述缓存服务器或者独立地部署于移动网络中的缓存服务器；
    所述发送模块还用于：当所述缓存设备已缓存所述目标数据时，向所述缓存设备发送数据请求，以使所述缓存设备在接收到所述数据请求后，将所述目标数据发送至用户终端。
  31. 如权利要求21所述的基站，其特征在于，
    所述发送模块还用于：向所述用户终端发送缓存设备的地址。
  32. 一种缓存设备，其特征在于，包括：
    接收模块，用于接收用户终端发送的请求数据包；其中，所述请求数据包为用户终端发送给基站，用于请求目标数据；当所述基站接收到所述请求数据包时，且所述基站判断所述请求数据包的信息与第一数据缓存列表中的信息相匹配时或所述请求数据包的目标地址为缓存设备的地址时，所述基站将所述请求数据包发送至缓存设备；
    发送模块，用于将所述目标数据发送至所述用户终端。
  33. 如权利要求32所述的缓存设备，其特征在于，所述缓存设备还包括：
    处理模块：用于判断是已缓存所述目标数据；当已缓存所述目标数据时，触发所述发送模块将所述目标数据发送至所述用户终端。
  34. 如权利要求32或33所述的缓存设备，其特征在于，
    所述处理模块还用于：将所述目标数据封装成响应数据包；所述响应数据包的源地址为所述请求数据包的目标地址；
    所述发送模块还用于：将所述响应数据包发送至所述用户终端。
  35. 如权利要求33所述的缓存设备，其特征在于，所述发送模块还用于：
    当所述基站判断所述请求数据包的信息与第一数据缓存列表中的信息相匹配，且未缓存所述目标数据时，向所述源服务器发送所述请求数据包，以使所述源服务器在接收到所述请求数据包后，所述源服务器将所述目标数据发送至所述用户终端。
  36. 如权利要求33所述的缓存设备，其特征在于，
    所述发送模块还用于，当未缓存所述目标数据时，向所述源服务器发送第一请求数据包，以使所述源服务器在接收到所述第一请求数据包后，所述 源服务器返回所述目标数据，所述第一请求数据包用于向所述源服务器请求所述目标数据；
    所述接收模块还用于：接收从所述源服务器返回的所述目标数据；
    所述发送模块还用于：将所述目标数据发送至所述用户终端。
  37. 如权利要求33所述的缓存设备，其特征在于，所述发送模块还用于：当未缓存所述目标数据时，向所述基站发送信令消息，以使所述基站在接收到所述信令消息后，所述基站向所述源服务器发送第二请求数据包，所述第二请求数据包用于所述基站向所述源服务器请求所述目标数据；所述基站接收从所述源服务器返回的所述目标数据，并将所述目标数据发送给所述用户终端。
  38. 一种用户终端，其特征在于，包括：
    处理模块，用于生成第三请求数据包；所述第三请求数据包用于向源服务器请求目标数据；以及根据第二数据缓存列表，判断所述第三请求数据包的信息是否与第二数据缓存列表中的信息相匹配；所述第二数据缓存列表包括至少一个信息，以及所述信息与缓存设备的地址的对应关系；
    所述处理模块还用于：当所述第三请求数据包的信息与第二数据缓存列表中的信息相匹配时，生成第四请求数据包，所述第四请求数据包的目标地址为匹配的信息对应的缓存设备的地址；所述第四请求数据包用于向所述缓存设备请求所述目标数据；
    发送模块，用于向所述缓存设备发送所述第四请求数据包，以使所述缓存设备在接收到所述第四请求数据包后，将所述目标数据发送至用户终端；
    接收模块，用于接收所述目标数据。
  39. 如权利要求38所述的用户终端，其特征在于，
    所述发送模块还用于：当所述第三请求数据包的信息与第二数据缓存列表中的信息不匹配时，发送所述第三请求数据包，以使所述源服务器在接收到所述第三请求数据包后，将所述目标数据发送至所述用户终端；
    所述接收模块还用于：接收所述目标数据。
  40. 如权利要求38所述的用户终端，其特征在于，所述处理模块还用于：
    获取第二数据缓存列表，其中，所述第二数据缓存列表中包括至少一个信息，以及所述信息与缓存设备的地址的对应关系；其中，所述信息包括服务器的地址和/或数据的标识。
  41. 一种基站，其特征在于，包括：
    接收器，用于接收用户终端发送的请求数据包；所述请求数据包用于向源服务器请求目标数据；
    处理器，用于根据预存的第一数据缓存列表，判断所述请求数据包的信息是否与第一数据缓存列表中的信息相匹配；
    发送器，用于当所述请求数据包的信息与所述第一数据缓存列表中的信息相匹配时，将所述目标数据发送至所述用户终端。
  42. 如权利要求41所述的基站，其特征在于，
    所述处理器还用于：获取第一数据缓存列表，其中，所述第一数据缓存列表中包含以下信息中的至少一个：
    服务器的地址、数据的标识。
  43. 如权利要求41所述的基站，其特征在于，所述发送器还用于：
    当所述请求数据包的信息与所述第一数据缓存列表中的信息相匹配时，通过所述基站与缓存设备建立的第一承载，将所述目标数据发送至所述用户终端。
  44. 如权利要求41所述的基站，其特征在于，所述发送器还用于：
    当所述请求数据包的信息与所述第一数据缓存列表中的信息不匹配时，通过所述基站与所述源服务器建立的第二承载，将所述目标数据发送至所述用户终端。
  45. 如权利要求41所述的基站，其特征在于，
    所述处理器还用于：判断是否已缓存所述目标数据，当已缓存所述目标数据时，触发所述发送器将所述目标数据发送至所述用户终端。
  46. 如权利要求41-45任一权利要求所述的基站，其特征在于，
    所述处理器还用于：将所述目标数据封装成响应数据包；所述响应数据包的源地址为所述请求数据包的目标地址；
    所述发送器还用于：将所述响应数据包发送至所述用户终端。
  47. 如权利要求45所述的基站，其特征在于，所述发送器还用于：当未缓存所述目标数据时，向所述源服务器发送所述请求数据包，以使所述源服务器在接收到所述请求数据包后，所述源服务器将所述目标数据发送至所述用户终端。
  48. 如权利要求45所述的基站，其特征在于，
    所述处理器还用于：当未缓存所述目标数据时，生成第一请求数据包，所述第一请求数据包的源地址为缓存设备的地址，用于向所述源服务器请求目标数据；
    所述发送器还用于：向所述源服务器发送所述第一请求数据包，以使所述源服务器在接收到所述第一请求数据包后，将所述目标数据发送至所述缓存设备。
  49. 如权利要求45所述的基站，其特征在于，
    所述接收器还用于：当未缓存所述目标数据时，接收所述缓存设备发送的信令消息；
    所述处理器还用于：根据所述信令消息，生成第二请求数据包，所述第二请求数据包用于向所述源服务器请求所述目标数据；
    所述发送器还用于：向所述源服务器发送所述第二请求数据包，以使所 述源服务器在接收到所述第二请求数据包后，返回所述目标数据；
    所述接收器还用于：接收所述源服务器返回的所述目标数据；
    所述发送器还用于：将所述目标数据发送至所述用户终端。
  50. 如权利要求45所述的基站，其特征在于，
    所述处理器还用于：判断所述缓存设备是否包含所述目标数据，其中，所述缓存设备为本地网关、通过所述本地网关与所述基站相连的所述缓存服务器或者独立地部署于移动网络中的缓存服务器；
    所述发送器还用于：当所述缓存设备已缓存所述目标数据时，向所述缓存设备发送数据请求，以使所述缓存设备在接收到所述数据请求后，将所述目标数据发送至用户终端。
  51. 如权利要求41所述的基站，其特征在于，
    所述发送器还用于：向所述用户终端发送缓存设备的地址。
  52. 一种缓存设备，其特征在于，包括：
    接收器，用于接收用户终端发送的请求数据包；其中，所述请求数据包为用户终端发送给基站，用于请求目标数据；当所述基站接收到所述请求数据包时，且所述基站判断所述请求数据包的信息与第一数据缓存列表中的信息相匹配时或所述请求数据包的目标地址为缓存设备的地址时，所述基站将所述请求数据包发送至缓存设备；
    发送器，用于将所述目标数据发送至所述用户终端。
  53. 如权利要求52所述的缓存设备，其特征在于，所述缓存设备还包括：
    处理器：用于判断是已缓存所述目标数据；当已缓存所述目标数据时，触发所述发送器将所述目标数据发送至所述用户终端。
  54. 如权利要求52或53所述的缓存设备，其特征在于，
    所述处理器还用于：将所述目标数据封装成响应数据包；所述响应数据 包的源地址为所述请求数据包的目标地址；
    所述发送器还用于：将所述响应数据包发送至所述用户终端。
  55. 如权利要求53所述的缓存设备，其特征在于，所述发送器还用于：
    当所述基站判断所述请求数据包的信息与第一数据缓存列表中的信息相匹配，且未缓存所述目标数据时，向所述源服务器发送所述请求数据包，以使所述源服务器在接收到所述请求数据包后，所述源服务器将所述目标数据发送至所述用户终端。
  56. 如权利要求53所述的缓存设备，其特征在于，
    所述发送器还用于，当未缓存所述目标数据时，向所述源服务器发送第一请求数据包，以使所述源服务器在接收到所述第一请求数据包后，所述源服务器返回所述目标数据，所述第一请求数据包用于向所述源服务器请求所述目标数据；
    所述接收器还用于：接收从所述源服务器返回的所述目标数据；
    所述发送器还用于：将所述目标数据发送至所述用户终端。
  57. 如权利要求53所述的缓存设备，其特征在于，所述发送器还用于：当未缓存所述目标数据时，向所述基站发送信令消息，以使所述基站在接收到所述信令消息后，所述基站向所述源服务器发送第二请求数据包，所述第二请求数据包用于所述基站向所述源服务器请求所述目标数据；所述基站接收从所述源服务器返回的所述目标数据，并将所述目标数据发送给所述用户终端。
  58. 一种用户终端，其特征在于，包括：
    处理器，用于生成第三请求数据包；所述第三请求数据包用于向源服务器请求目标数据；以及根据第二数据缓存列表，判断所述第三请求数据包的信息是否与第二数据缓存列表中的信息相匹配；所述第二数据缓存列表包括至少一个信息，以及所述信息与缓存设备的地址的对应关系；
    所述处理器还用于：当所述第三请求数据包的信息与第二数据缓存列表中的信息相匹配时，生成第四请求数据包，所述第四请求数据包的目标地址为匹配的信息对应的缓存设备的地址；所述第四请求数据包用于向所述缓存设备请求所述目标数据；
    发送器，用于向所述缓存设备发送所述第四请求数据包，以使所述缓存设备在接收到所述第四请求数据包后，将所述目标数据发送至用户终端；
    接收器，用于接收所述目标数据。
  59. 如权利要求58所述的用户终端，其特征在于，
    所述发送器还用于：当所述第三请求数据包的信息与第二数据缓存列表中的信息不匹配时，发送所述第三请求数据包，以使所述源服务器在接收到所述第三请求数据包后，将所述目标数据发送至所述用户终端；
    所述接收器还用于：接收所述目标数据。
  60. 如权利要求58所述的用户终端，其特征在于，所述处理器还用于：
    获取第二数据缓存列表，其中，所述第二数据缓存列表中包括至少一个信息，以及所述信息与缓存设备的地址的对应关系；其中，所述信息包括服务器的地址和/或数据的标识。
  61. 一种通信系统，其特征在于，包括：用户终端、基站以及缓存设备；其中，
    所述用户终端用于发送请求数据包；所述请求数据包用于向源服务器请求目标数据；
    所述基站用于接收用户终端发送的请求数据包，并根据第一数据缓存列表，判断所述请求数据包的信息是否与第一数据缓存列表中的信息相匹配，如果是，将所述目标数据发送至所述用户终端；
    所述缓存设备用于存储所述目标数据。
  62. 如权利要求61所述的通信系统，其特征在于，所述基站包括如权利 要求21-31或41-51所述的任一基站；所述缓存设备包括如权利要求32-37或52-57所述的任一缓存设备。
  63. 一种通信系统，其特征在于，包括：用户终端、缓存设备；其中，
    所述用户终端用于生成第三请求数据包；所述第三请求数据包用于向源服务器请求目标数据；并根据第二数据缓存列表，判断所述第三请求数据包的信息是否与第二数据缓存列表中的信息相匹配，如果是，生成第四请求数据包，其中，所述第二数据缓存列表包括至少一个信息，以及所述信息与缓存设备的地址的对应关系；所述第四请求数据包的目标地址为匹配的信息对应的缓存设备的地址；所述第四请求数据包用于向所述缓存设备请求所述目标数据，以及向所述缓存设备发送所述第四请求数据包；
    所述缓存设备用于接收所述第四请求数据包，并将所述目标数据发送至用户终端；
    所述用户终端还用于，接收所述目标数据。
  64. 如权利要求63所述的通信系统，其特征在于，所述用户终端包括如权利要求38-40或58-60所述的任一用户终端；所述缓存设备包括如权利要求32-34、36、37、52-54、56或57所述的任一缓存设备。
PCT/CN2016/106447 2016-11-18 2016-11-18 缓存数据获取方法、相关设备以及通信系统 WO2018090336A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
PCT/CN2016/106447 WO2018090336A1 (zh) 2016-11-18 2016-11-18 缓存数据获取方法、相关设备以及通信系统
EP16921514.2A EP3531745A4 (en) 2016-11-18 2016-11-18 ACQUISITION METHOD OF CACHE MEMORY DATA, DEVICE AND COMMUNICATION SYSTEM THEREOF
CN201680090408.XA CN109891929A (zh) 2016-11-18 2016-11-18 缓存数据获取方法、相关设备以及通信系统
US16/413,881 US20190274069A1 (en) 2016-11-18 2019-05-16 Cached-Data Obtaining Method, Related Device, And Communications System

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/106447 WO2018090336A1 (zh) 2016-11-18 2016-11-18 缓存数据获取方法、相关设备以及通信系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/413,881 Continuation US20190274069A1 (en) 2016-11-18 2019-05-16 Cached-Data Obtaining Method, Related Device, And Communications System

Publications (1)

Publication Number Publication Date
WO2018090336A1 true WO2018090336A1 (zh) 2018-05-24

Family

ID=62145190

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/106447 WO2018090336A1 (zh) 2016-11-18 2016-11-18 缓存数据获取方法、相关设备以及通信系统

Country Status (4)

Country Link
US (1) US20190274069A1 (zh)
EP (1) EP3531745A4 (zh)
CN (1) CN109891929A (zh)
WO (1) WO2018090336A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11252251B2 (en) 2016-11-18 2022-02-15 Huawei Technologies Co., Ltd. Cache data request method and related device
CN114926106A (zh) * 2022-03-16 2022-08-19 递易（上海）智能科技有限公司 一种智能柜格口状态动态更新方法、装置及电子设备

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112393734B (zh) * 2019-08-13 2023-05-23 上海博泰悦臻网络技术服务有限公司 导航方法、服务器及计算机可读存储介质
CN112954383B (zh) * 2021-03-02 2023-05-16 山东省计算中心（国家超级计算济南中心） 视频点播方法、视频点播代理服务器、基站及存储介质
CN114979283A (zh) * 2021-04-27 2022-08-30 中移互联网有限公司 数据获取方法、装置、电子设备及存储介质
US11553061B1 (en) * 2021-07-30 2023-01-10 At&T Intellectual Property I, L.P. Hyperlocal edge cache
CN114615237B (zh) * 2022-03-22 2024-03-29 阿里巴巴（中国）有限公司 流媒体通信方法、系统、设备及存储介质
CN114974605A (zh) * 2022-05-24 2022-08-30 山东浪潮智慧医疗科技有限公司 一种高并发场景下查询多条核酸报告的办法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014019516A1 (zh) * 2012-08-02 2014-02-06 华为技术有限公司 一种报文转发的方法和设备
CN104507124A (zh) * 2014-12-24 2015-04-08 中国科学院声学研究所 一种基站缓存的管理方法及用户访问的处理方法
CN105357281A (zh) * 2015-10-19 2016-02-24 中国科学院信息工程研究所 一种移动接入网分布式内容缓存访问控制方法及系统
CN106028400A (zh) * 2016-06-30 2016-10-12 华为技术有限公司 一种缓存内容的方法和基站

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102868719B (zh) * 2012-06-29 2015-09-16 北京奇虎科技有限公司 一种基于缓存的网络访问方法和服务器
CN104812006B (zh) * 2014-01-24 2019-11-01 北京三星通信技术研究有限公司 基于缓存的数据传输方法及装置
CN106162756A (zh) * 2015-03-31 2016-11-23 北京三星通信技术研究有限公司 一种基于lte网络的业务数据缓存方法及设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014019516A1 (zh) * 2012-08-02 2014-02-06 华为技术有限公司 一种报文转发的方法和设备
CN104507124A (zh) * 2014-12-24 2015-04-08 中国科学院声学研究所 一种基站缓存的管理方法及用户访问的处理方法
CN105357281A (zh) * 2015-10-19 2016-02-24 中国科学院信息工程研究所 一种移动接入网分布式内容缓存访问控制方法及系统
CN106028400A (zh) * 2016-06-30 2016-10-12 华为技术有限公司 一种缓存内容的方法和基站

Non-Patent Citations (1)

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

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11252251B2 (en) 2016-11-18 2022-02-15 Huawei Technologies Co., Ltd. Cache data request method and related device
CN114926106A (zh) * 2022-03-16 2022-08-19 递易（上海）智能科技有限公司 一种智能柜格口状态动态更新方法、装置及电子设备
CN114926106B (zh) * 2022-03-16 2024-03-12 递易（上海）智能科技有限公司 一种智能柜格口状态动态更新方法、装置及电子设备

Also Published As

Publication number Publication date
US20190274069A1 (en) 2019-09-05
EP3531745A1 (en) 2019-08-28
EP3531745A4 (en) 2019-09-18
CN109891929A (zh) 2019-06-14

Similar Documents

Publication Publication Date Title
WO2018090336A1 (zh) 缓存数据获取方法、相关设备以及通信系统
US11979367B2 (en) Method and apparatus for local application server discovery in mobile edge computing
JP7287431B2 (ja) ユーザ装置、通信装置、及び通信方法
US10285022B2 (en) Method and apparatus for signal transmission and reception of HSS/MME in wireless communication system
KR101645106B1 (ko) 무선 통신 네트워크 내의 소규모 데이터 통신
US20150172436A1 (en) Application Service Platform with Access to Context Data of Remote Access Node
JP2020096359A (ja) セルラネットワークにおけるインターネットへの接続の確立
WO2021042398A1 (zh) 一种通信方法及装置、网络设备、终端设备
WO2018195907A1 (zh) 无线通信的方法、网络设备和终端设备
US11356294B2 (en) Packet processing method and device
WO2013152472A1 (zh) 通信方法与系统，以及接入网设备与应用服务器
EP3606005B1 (en) Redirection method, control plane network element, aggregation user plane network element, content server and terminal device
US9585052B2 (en) Determining a traffic bearer for data traffic between a terminal and a content data source of a content data network
WO2016191963A1 (zh) 一种建立承载的方法、用户设备及基站
JP2019536355A (ja) ノードタイプに基づくデータストリーミングの支援制御
WO2017084042A1 (zh) 一种业务流的传输方法及装置
US11252251B2 (en) Cache data request method and related device
WO2014183781A1 (en) Establishing a direct communication (t5 association)between a mobility management entity (mme) and a machine type communication interworking function (mtc-iwf)
TW202015440A (zh) 無線通訊的方法和設備
US10257802B2 (en) Binding registration method, data forwarding method, related device, and network system
WO2017193363A1 (zh) 业务数据流发送方法及装置
WO2019154048A1 (zh) NB-IoT网络的通信方法、装置及存储介质
CN110233815B (zh) 一种寻呼方法和装置
WO2015096008A1 (en) Method and network node for routing backhaul packets
US11032856B2 (en) Data transmission method and apparatus

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

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

Country of ref document: EP

Effective date: 20190523