WO2018090335A1 - 一种缓存数据请求方法及相关设备 - Google Patents

一种缓存数据请求方法及相关设备 Download PDF

Info

Publication number
WO2018090335A1
WO2018090335A1 PCT/CN2016/106446 CN2016106446W WO2018090335A1 WO 2018090335 A1 WO2018090335 A1 WO 2018090335A1 CN 2016106446 W CN2016106446 W CN 2016106446W WO 2018090335 A1 WO2018090335 A1 WO 2018090335A1
Authority
WO
WIPO (PCT)
Prior art keywords
target
local cache
service data
data
cache device
Prior art date
Application number
PCT/CN2016/106446
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 EP16921782.5A priority Critical patent/EP3534590B1/en
Priority to PCT/CN2016/106446 priority patent/WO2018090335A1/zh
Priority to CN201680086229.9A priority patent/CN109196843B/zh
Publication of WO2018090335A1 publication Critical patent/WO2018090335A1/zh
Priority to US16/412,821 priority patent/US11252251B2/en

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/56Provisioning of proxy services
    • H04L67/568Storing data temporarily at an intermediate stage, e.g. caching
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/2866Architectures; Arrangements
    • H04L67/289Intermediate processing functionally located close to the data consumer application, e.g. in same machine, in same home or in same sub-network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/56Provisioning of proxy services
    • H04L67/561Adding application-functional data or data for application control, e.g. adding metadata
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/56Provisioning of proxy services
    • H04L67/562Brokering proxy services
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/56Provisioning of proxy services
    • H04L67/568Storing data temporarily at an intermediate stage, e.g. caching
    • H04L67/5681Pre-fetching or pre-delivering data based on network characteristics
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W28/00Network traffic management; Network resource management
    • H04W28/02Traffic management, e.g. flow control or congestion control
    • H04W28/10Flow control between communication endpoints
    • H04W28/14Flow control between communication endpoints using intermediate storage
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/14Direct-mode setup
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W88/00Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08Access point devices
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W88/00Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/18Service support devices; Network management devices

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a cache data request method and related device.
  • the current common caching method is through the CDN (Content Delivery Network).
  • the content distribution network is responsible for connecting the servers and users at both ends of the entire bandwidth service chain to publish the content of the website to the edge of the network closest to the user. Enable users to get the required content nearby, ease the congestion of the Internet network, and improve the response speed of users visiting the website.
  • the CDN is deployed on the backbone network, and the user equipment needs to pass through the wireless network and the core network before reaching the backbone network, and the link transmission overhead and transmission delay between the wireless network and the core network are large.
  • the deployment of the CDN network is expensive, and it is required to deploy distributed storage, load balancing, network request redirection, and content management. If the CDN is deployed to other networks, the cost is high and the investment cost is high.
  • the present invention provides a cache data request method and related device, which can reduce network transmission overhead and transmission delay while alleviating network congestion, and improve the response speed of the data request device after requesting data.
  • a first aspect of the present invention provides a method of requesting a cached data. After the data requesting device detects the first request message for the target data server, determining, according to the local cache device list sent by the base station in advance, determining a target local cache device for buffering the target data server service data, and then the data requesting device is established. a network connection with the target local cache device, and sending the number of services for the target data server to the target local cache device through the network connection Upon request.
  • the data requesting device can directly request the target service data from the target local cache device, thereby avoiding the result of requesting data from the target data server.
  • the transmission overhead is wasted and the transmission delay is large, thereby improving the response speed of the data requesting device after requesting data, thereby improving the user experience.
  • the data requesting device after the data requesting device establishes a network connection with the target local cache device, when detecting that the target address is the first service data request of the target data server Sending a second service data request to the target local cache device, where the first service data request and the second service data request both carry a target service data identifier, where the second service data request is used to indicate the target local cache
  • the device sends the cached target service data to the data requesting device when detecting that the target service data corresponding to the target service data identifier is cached.
  • the first request message includes a target service data identifier, and is used to request the target service data corresponding to the target service data identifier.
  • the data requesting device After the data requesting device establishes a network connection with the target local cache device, the data requesting device sends a second service data request to the target local cache device, where the second service data request carries the target service data.
  • the second service data request is used to indicate that the target local cache device sends the cached target service data to the data request device when detecting that the target service data corresponding to the target service data identifier is cached.
  • the local cache device list includes an identifier of the at least one local cache device And determining, by the data requesting device, the first identifier that is consistent with the identifier of the local cache device in the local cache device list, where the cache content authorization list includes the target data server authorization cache.
  • the identifier of the at least one local cache device if the first identifier is present, determining that the local cache device corresponding to the first identifier is the target local cache device.
  • the data requesting device determines whether the pre-acquired cache content authorization list exists in the local cache device list The first identifier of the at least one local cache device is consistent with the identifier And receiving the cache content authorization list sent by the target data server.
  • the local cache device includes a base station to which the data request device belongs or/and is connected to the base station At least one first cache device.
  • the data requesting device sends the second request message to a base station to which the data requesting device belongs, where the second request message carries routing information, the routing message The second request message is used to indicate that the base station establishes a connection between the data requesting device and the target local cache device.
  • the routing information includes an identifier of the target local cache device or an index value of the target local cache device.
  • the data requesting device is the user
  • the device home gateway receives the first service data request that the target address sent by the user equipment is the address of the target data server.
  • a second aspect of the present invention provides another method of caching data requests. Sending, by the base station, a local cache device list to a data requesting device managed by the base station, where the local cache device list includes an identifier of at least one local cache device, where the local cache device list is used by the data requesting device to determine an authorization cache Target local cache device for target data server business data.
  • the data requesting device can directly request the target service data from the local cache device with a relatively short distance, thereby avoiding requesting data from the target data server.
  • the transmission overhead is wasted and the transmission delay is large, the response speed of the data requesting device after requesting the data is improved, and the user experience is improved.
  • the base station receives a second request message sent by the data requesting device, where the second request message carries routing information, where the routing message is used to indicate a target local cache.
  • the device the base station establishes a connection between the data requesting device and the target local cache device according to the second request message.
  • the base station establishes a transmission bearer between the base station and the data requesting device or/and between the base station and the target local cache device, where the transport bearer is used to transmit the data requesting device and Target local cache data between devices.
  • the base station receives a second service data request for the target local cache device that is sent after the data request device establishes a network connection with the target local cache device,
  • the second service data request carries the target service data identifier, and when it is determined that the target local cache device has cached the target service data corresponding to the target service data identifier, the base station sends the cached to the data requesting device.
  • Target business data carries the target service data identifier
  • the base station sends the second service data request to the target local cache device, and receives the After detecting the cached target service data that is sent when the target service data is cached, the target local cache device sends the cached target service data to the data request device.
  • the base station after receiving the network connection between the data requesting device and the target local cache device, sends the network connection After determining the second service data request for the target local cache device, when it is determined that the target local cache device does not cache the target service data, sending a third service data request to the target data server, where the third service data request is carried And the third service data request is used to instruct the target data server to send the target service data to the data requesting device.
  • the base station sends the second service data request to the target local cache device, where the second The service data request is used to indicate that the target local cache device sends uncached information for the target service data to the base station when detecting that the target service data is not cached, and the base station receives the target local cache.
  • the uncached information sent by the device for the target service data determines that the target local cache device does not cache the target service data.
  • a third aspect of the present invention provides a data requesting device.
  • the device includes a processor, a memory, and a communication interface.
  • the processor is coupled to the memory and communication interface, for example, the processor can be coupled to the memory and communication interface via a bus.
  • the communication interface is used to communicate with devices such as base stations. Memory For storing local cache device lists, etc.
  • the processor is configured to perform some or all of the processes of the first aspect.
  • a fourth aspect of the present invention provides another data requesting device, including:
  • a processing module configured to detect a first request message for the target data server; determining, according to the local cache device list sent by the base station in advance, a target local cache device for buffering the target data server service data; establishing and a network connection between the target local cache devices;
  • a sending module configured to send, by the network connection, a service data request for the target data server to the target local cache device.
  • the data requesting device can directly request the target service data from the target local cache device, thereby avoiding the result of requesting data from the target data server.
  • the transmission overhead is wasted and the transmission delay is large, thereby improving the response speed of the data requesting device after requesting data, thereby improving the user experience.
  • the processing module is further configured to: detect that the target address is a first service data request of the target data server, where the first service data request carries a target service data identifier;
  • the sending module is further configured to: send a second service data request to the target local cache device, where the second service data request carries the target service data identifier, and the second service data request is used to indicate the target
  • the local cache device sends the cached target service data to the data request device when detecting that the target service data corresponding to the target service data identifier is cached;
  • the device further includes:
  • a receiving module configured to receive the target service data sent by the target local cache device.
  • the first request message includes a target service data identifier, and is used to request target service data corresponding to the target service data identifier;
  • the sending module is further configured to: send a second service data request to the target local cache device, where the second service data request carries the target service data identifier, and the second service data request is used to indicate the target
  • the local cache device sends the cached target service data to the data request device when detecting that the target service data corresponding to the target service data identifier is cached;
  • the device further includes:
  • a receiving module configured to receive the target service data sent by the target local cache device.
  • the local cache device list includes an identifier of the at least one local cache device
  • the processing module is used to:
  • the local cache device corresponding to the first identifier is determined to be the target local cache device.
  • the receiving module is further configured to:
  • the local cache device includes a base station to which the data request device belongs or/and a connection with the base station At least one first cache device.
  • the processing module is configured to:
  • the base station And sending, by the base station to which the data requesting device belongs, the second request message, where the second request message carries routing information, where the routing message is used to indicate a target local cache device, and the second request message is used to indicate the
  • the base station establishes a connection or bearer of the data requesting device and the target local cache device.
  • the routing information includes an identifier of the target local cache device or an index value of the target local cache device.
  • the processing module is used to:
  • a fifth aspect of the present invention provides another data requesting device, the device comprising a processor, a transmitter, and a receiver.
  • the data requesting device implements some or all of the methods of the first aspect through the above modules.
  • a sixth aspect of the present invention provides a base station.
  • the base station includes a processor, a memory, and a communication interface.
  • the processor is coupled to the memory and communication interface, for example, the processor can be coupled to the memory and communication interface via a bus.
  • the communication interface is used to communicate with devices such as data requesting devices.
  • the memory is used to store a list of local cache devices and the like.
  • the processor is configured to perform some or all of the processes of the second aspect.
  • a seventh aspect of the present invention provides another base station, including:
  • a processing module configured to obtain a local cache device list, where the local cache device list includes an identifier of at least one local cache device;
  • a sending module configured to send, to the data requesting device managed by the base station, the local cache device list, where the local cache device list is used by the data requesting device to determine a target locality for caching the target data server service data Cache device.
  • the base station further includes:
  • a receiving module configured to receive a second request message sent by the data requesting device, where the second request message carries routing information, where the routing message is used to indicate a target local cache device;
  • the processing module is further configured to: establish a connection or bearer of the data requesting device and the target local cache device according to the second request message.
  • the processing module is configured to:
  • the base station further includes:
  • a receiving module configured to receive a second service data request for the target local cache device that is sent after the network request is established between the data requesting device and the target local cache device, where the second service data request carries the target service data identifier ;
  • the processing module is further configured to: when it is determined that the target local cache device has cached target service data corresponding to the target service data identifier, send the cached target service data to the data request device.
  • the processing module is configured to:
  • the processing module is further configured to:
  • the base station When it is determined that the target local cache device does not cache the target service data, the base station sends a third service data request to the target data server, where the third service data request carries the target service data identifier, the third The service data request is used to instruct the target data server to send the target service data to the data requesting device.
  • the processing module is used to:
  • An eighth aspect of the present invention provides another base station including a processor, a transmitter, and a receiver.
  • the base station implements some or all of the methods of the second aspect through the above modules.
  • 1a is a system architecture diagram of a communication system according to an embodiment of the present invention.
  • 1b is a system architecture diagram of another communication system according to an embodiment of the present invention.
  • 1c is a system architecture diagram of another communication system according to an embodiment of the present invention.
  • FIG. 2a is a schematic flowchart of a method for requesting cache data according to an embodiment of the present invention
  • 2b is a schematic flowchart of another method for requesting cache data according to an embodiment of the present invention.
  • FIG. 3 is a schematic flowchart of another method for requesting cache data according to an embodiment of the present invention.
  • FIG. 3b is a schematic flowchart of another method for requesting cache data according to an embodiment of the present disclosure
  • FIG. 4 is a schematic structural diagram of a data requesting device according to an embodiment of the present invention.
  • FIG. 5 is a schematic structural diagram of another data requesting device 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 another data requesting device according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic structural diagram of another base station according to an embodiment of the present invention.
  • the base station in the embodiment of the present invention includes an evolved base station (eNB) in an LTE (Long-Term Evolution, LTE) system, or a network device in a future communication system, such as a network device in the 5G (such as controller).
  • eNB evolved base station
  • LTE Long-Term Evolution
  • 5G 5th Generation
  • controller a network device in the 5G
  • the data requesting device in the embodiment of the present invention may be referred to as a user equipment (UE, User Equipment) or a modem modem module, including a mobile phone (English: cellphone), a smart phone (English: smart phone), and a computer. (English: computer), tablet (English: tablet computer), mobile Internet device (English: mobile Internet device, MID) and wearable devices, etc., which can access the network through the base station.
  • the data requesting device may refer to a Customer Premise Equipment (CPE), and the CPE may serve as a home gateway for providing customers such as a home or a business. Integrated access to broadband, IPTV, VOIP and other services.
  • CPE Customer Premise Equipment
  • the CPE can be connected to the home user equipment (UE) through a wireless connection such as Wifi, and then establish a connection with the base station through a wireless access method such as LTE or WCDMA (Wideband Code Division Multiple Access), thereby completing the home user equipment through the CPE.
  • UE home user equipment
  • Wifi wireless connection
  • LTE Long Term Evolution
  • WCDMA Wideband Code Division Multiple Access
  • the local cache device (LC) in the embodiment of the present invention may be an independent cache server connected to the base station through a local gateway (LGW, Local Gateway).
  • LGW local gateway
  • the local caching device may be part of the base station itself, such as one of the base stations.
  • the data server in the embodiment of the present invention may be a third-party server (Over The Top Server) that provides an application service to the UE through the Internet, or may be an operator's content providing server (Content Provide Server).
  • Third-party server (Over The Top Server) that provides an application service to the UE through the Internet
  • Content Provide Server an operator's content providing server
  • the embodiments of the present invention are applicable to various communication systems, such as an LTE system, a wireless broadband to the home (WTTx, Wireless To The x) system, a fifth generation communication system (5G), and a device to device (D2D) communication system. Wait.
  • LTE Long Term Evolution
  • WTTx Wireless To The x
  • 5G fifth generation communication system
  • D2D device to device
  • Figure 1a is a system architecture diagram of a communication system according to an embodiment of the present invention, including a user equipment 110a, a base station 120a, and at least one local cache device 131a, 132a, and 133a, wherein the base station 120a can pass through a local gateway 140a (LGW, Local Gateway) ) is connected to local cache devices 131a, 132a and 133a.
  • a base station 120a can be connected to a plurality of local cache devices (131a, 132a, and 133a), that is, when the different service data requested by the user equipment 110a is respectively in the local cache device 131a.
  • the user equipment 110a can send corresponding service data requests to the local cache devices 131a, 132a, and 133a through the base station 120a.
  • FIG. 1b is a system architecture diagram of another communication system according to an embodiment of the present invention, including a user equipment 110b, a local cache device 130b, and at least one base station 121b, 122b, and 123b, wherein the base stations (121b, 122b, and 123b) can pass
  • the local gateway 140b is connected to the local cache device 130b.
  • a plurality of base stations (121b, 122b, and 123b) may be connected to a local cache device 130b, that is, when the user equipment 110b requests a certain cached service in the local cache device 130b.
  • the same service data can be obtained from the same local cache device 130b through 121b, 122b and 123b, respectively, so that the service can be avoided when the base station is switched.
  • the local cache device in FIG. 1a and FIG. 1b may also be part of the base station itself, and then need to be connected to the local cache device through the local gateway, and the user equipment only needs service data. Just send it to the base station.
  • FIG. 1c is a system architecture diagram of another communication system according to an embodiment of the present invention, including a user equipment 110c, a home gateway CPE 120c, and The base station 130c and the local cache device 140c, wherein the base station 130c can be connected to the local cache device 140c through the local gateway 150c.
  • the user equipment 110c may request the home gateway CPE 120c for some service data buffered in the local cache device 130c, and the home gateway CPE 120c sends the corresponding service data to the local cache device 130c through the base station 120c. request.
  • the base station in the implementation scenario of the WTTx can be connected to multiple local cache devices, and multiple base stations can also be connected to the same local cache device.
  • the local cache device may be part of the base station itself, and the local gateway CPE only needs to send the service data request to the base station.
  • FIG. 2a is a schematic flowchart of a method for requesting a cached data according to an embodiment of the present invention.
  • the method is directed to an implementation scenario in which a data requesting device is a user equipment UE.
  • a user device such as a smart phone, is installed with a target application or client that can trigger a request to be sent to the target data server, and the user device or the modem module can perform cross-layer communication with the target application or client.
  • FIG. 2b is a schematic flowchart of another method for requesting a cached data according to an embodiment of the present invention.
  • the method is directed to an implementation scenario in which a data requesting device is a home gateway CPE.
  • the embodiment of the present invention is directed to a scenario in which the base station itself is not used as a local cache device, and only a plurality of independent local cache devices are connected.
  • the scenes shown in FIG. 2a and FIG. 2b differ only in steps S202 and S205, and thus are collectively described in this embodiment.
  • the method includes:
  • Step S201 The base station sends a local cache device list to the data requesting device managed by the base station.
  • the local cache device list includes an identifier of at least one local cache device, wherein the local cache device may be a separate cache device connected to the base station, or may be part of the base station itself.
  • the identifier of the local cache device refers to an identifier that can uniquely identify the local cache device. For example, the IP address of the local cache device (Internet Protocol), port number, etc. Both can be used as the identifier of the local cache device. Further, the index value corresponding to the identifier may be carried, and the data requesting device may be a user equipment or a home gateway CPE.
  • the base station is not connected to other independent local cache devices, and only the base station itself acts as a local cache device, and the content in the local cache device list is the IP address or/and port number of the base station itself;
  • the base station itself is not used as a local cache device, but a plurality of independent local cache devices are connected, and the content of the local cache device list is the IP address or/and port of at least one local cache device connected by the base station.
  • the base station itself acts as a local cache device, and at the same time, at least one independent local cache device is also connected, and the content in the local cache device list is the base station itself and at least one local cache connected to the base station.
  • the IP address or / and port number of the device is not connected to other independent local cache devices, and only the base station itself acts as a local cache device, and the content in the local cache device list is the IP address or/and port number of the base station itself;
  • the base station itself is not used as a local cache device, but a plurality of independent local cache
  • the embodiment of the present invention is directed to a scenario in which the base station itself is not used as a local cache device, but a plurality of independent local cache devices are connected, that is, the target local cache device mentioned later in the embodiment of the present invention is the first cache connected to the base station. device.
  • the base station may send the configured or saved local cache device list to the data requesting device in advance.
  • the local cache device list may be sent to the data requesting device by using different message bearers.
  • the local cache device list may be carried by RRC (Radio Resource Control) dedicated signaling or a system message of the base station.
  • the user uses an application of the user equipment to trigger a query to the DNS (Domain Name System) server for the address of the target data server, and establishes a TCP (Transmission Control Protocol) to the target data server. Control Protocol) connection, the connection at this time is the TCP connection between the application and the target server.
  • TCP Transmission Control Protocol
  • the user equipment before or after the CPE receives the local cache device list sent by the base station, the user equipment establishes a TCP connection with the target data server through the CPE.
  • the message sent by the TCP connection establishment process in the above two implementation scenarios needs to be transmitted through the bearer between the data requesting device and the base station and the base station and the core network gateway.
  • the process of establishing the TCP connection can trigger the process of establishing the relevant bearer, and the subsequent data.
  • the data passed between the requesting device and the target data server can be passed through the corresponding established bearer.
  • Step S202 the data requesting device detects the first request message for the target data server.
  • the first request message may be a connection that is made when a connection to the target data server is required in advance.
  • the established request may also be a service data request issued when requesting certain business data from the target data server.
  • the data requesting device can determine whether it is for the target data server by detecting whether the target address of the first request message is the IP address and/or port number of the target data server.
  • the target application in the data requesting device can communicate with the data requesting device through cross-layer communication, so that the data requesting device detects the first request message for the target data server.
  • the TCP connection between the target application and the target data server is triggered, so that the establishment corresponding to the base station to which the data requesting device belongs is connected to the target data server.
  • the SGW Serving Gateway
  • RAB Radio Access Bearer
  • a radio bearer that triggers an air interface is established between the base station and the data requesting device. Used for data transfer between the data request device and the target data server.
  • the target application or the user equipment may receive a list of local cache devices sent by the base station in the relevant data packet when establishing a connection to the target data server, or receive a list of local cache devices received from the base station by the data requesting device.
  • a determination is made as to whether a connection is established to the target local cache device based on comparison with the received cache content authorization list. Steps S201 and S202 do not particularly limit the execution order.
  • the data requesting device is a user equipment, and when the target application triggers the first request message, the data requesting device may directly detect.
  • step S202 may be specifically:
  • the data requesting device receives the first request message sent by the user equipment for the target data server.
  • the data requesting device is a home gateway CPE
  • the home gateway CPE is connected to the user equipment by using wifi
  • the user equipment sends the first request message to the data requesting device after detecting the first request message.
  • a request message is a home gateway CPE
  • Step S203 The data requesting device determines, according to the local cache device list sent by the base station in advance, whether there is a target local cache device that authorizes the service data of the cache target data server in the local cache device list. If there is a target local cache device, steps S204 to S215 are performed; Otherwise, steps S216 to S218 are performed.
  • the local cache device that is authorized to cache the service data of the target data server refers to a local cache device that has the service data permission of the cache target data server.
  • the data request device may obtain the cached content authorization list in advance, which may include the local cache device identifier information, that is, An identifier containing at least one local cache device for indicating a local cache device available to the target data server being accessed. Matching the identifier of the at least one local cache device in the local cache device list with the identifier of the at least one local cache device in the local cache device identifier information, and the local cache device corresponding to the matched identifier is the target local cache device.
  • the identifier of the local cache device may be an IP address and/or a port number, which may be used to address the relevant local cache device.
  • the cache content authorization list may further include source user equipment identification information or/and Uniform Resource Locator (URL).
  • the source user equipment identification information may be a device identifier of the user equipment, and is used to verify whether the user equipment has the right to obtain the cache in the local cache device.
  • the uniform resource locator URL information is used to indicate that the service data corresponding to a certain URL in the target data server has been locally cached, and may be combined with the local cache device identification information to indicate a URL corresponding to the service data cached in a local cache device.
  • the source user equipment identifier information may be an IP address and/or a port number or a MAC (Media Access Control) address of the source user equipment or the terminal, and may be used to address the related source user equipment or terminal.
  • the data requesting device may determine whether the first identifier corresponding to the identifier of the local cache device in the local cache device list exists in the cache content authorization list, and if the first identifier exists, determine the local cache device corresponding to the first identifier. That is, the target local cache device; if there is no first identifier, it means that at least one local cache device connected to the base station does not have the right to cache the service data of the target data server, that is, there is no target local cache device.
  • Table 1 be the cache content authorization list
  • Table 2 be the local cache device list. After comparing Table 1 and Table 2, it can be determined that the consistent IP address in the two tables is 112.111.154.224, so the IP address is 112.111.154.224.
  • the local cache device is the target local cache device.
  • Table 2 List of local cache devices (example)
  • the cache content authorization list may not only indicate at least one local cache device that authorizes the service data of the cache target data server, but also may be accurate to indicate that the authorized cache target data server is The service data corresponding to all URLs cached by a local cache device.
  • the first request message itself carries the target service data identifier, where the target service data identifier can refer to the URL, and the data requesting device can obtain at least one local cache device that authorizes the cache URL by caching the content authorization list.
  • the identifier matches the acquired identifier of the at least one local cache device with the identifier of the at least one local cache device in the local cache device list to determine the target local cache device.
  • Table 3 is a cache content authorization list
  • Table 2 is a local cache device list
  • the target service data identifier of the first service data request is URL3
  • two local cache devices with IP addresses of 148.16.12.12 and 207.211.135.210 can be determined. If the target service data corresponding to the URL 3 is authorized to be cached, it is further determined whether the IP address in the IP address in Table 2 is the same as the IP address of the local cache device of the authorized cache URL 3 of Table 3. It can be seen that the IP address is The local cache device of 207.211.135.210 is the target local cache device.
  • the cache content authorization list may be sent to the target application or the user equipment when the target application or the user equipment establishes a TCP connection with the target data server, and the data request device and the target application may be Obtaining a cached content authorization list across layers, or the data requesting device parses the data packets sent to the target application or user equipment; or may be a public land mobile network (PLMN, Public Land Mobile Network when the data requesting device performs network registration)
  • PLMN Public Land Mobile Network
  • the data requesting device determines that there are multiple target local cache devices, one may be selected according to a pre-configured priority, or one according to a certain operation rule.
  • Step S204 the data requesting device establishes a network connection with the target local cache device, and the network connection is used to send a service data request for the target data server to the target local cache device and further perform data transfer.
  • the TCP connection can be established with the target local cache device, that is, the data transmission channel between the target local cache device and the data request device is established, so that the data request device can be made
  • the service data request may be directly sent to the target local cache device. Further, the target local cache device may also send the requested service data to the data requesting device.
  • the data requesting device sends the first to the base station to which the data requesting device belongs.
  • a request message which may be a request to establish a connection with a target local cache device.
  • the second request message carries routing information, where the routing message is used to indicate the target local cache device, so that the base station establishes a connection between the data requesting device and the target local cache device.
  • the routing information may include an identifier of the target local cache device or an index value of the target local cache device.
  • a cache transmission resource bearer that is, an S1 connection
  • a local gateway LGW
  • the LGW has a certain MME (Mobile Management Entity Mobility Management Entity) function, which can establish the establishment of the control plane connection and the assignment of the user plane bearer.
  • MME Mobile Management Entity Mobility Management Entity
  • the base station may still establish a control plane connection with the MME, but an indication is added in the corresponding message to indicate that the user plane bearer is established with the LGW, and the MME performs the RAB (Radio Access Bearer). Assigning, and establishing a user plane transmission channel of the base station and the LGW, for carrying the data requesting device to send a data request to the target local cache device.
  • the second request message may be included in an RRC (Radio Resource Control) message, where the carrying indication information informs the base station to send a user plane connection request to the target local cache device, triggering the base station and the target local cache.
  • the related bearer is established between the devices.
  • the base station determines that the target terminal of the request is the target local cache device by using the target address of the second request message, and triggers the establishment of the S1 connection between the base station and the target local cache device.
  • the establishment of the S1 connection triggers the establishment of the RAB of the target local cache device and the base station, and opens the channel for transmitting the service data.
  • the air interface (base station and data requesting device) bearer setup is also included, or the air interface bearer established when establishing the connection with the target data server can be used to transmit the data sent to the target local cache device.
  • bearer RB Radio Bear
  • different RBs correspond to different TCPs, and the logical channel number (LCH ID) or the packet data convergence protocol identifier (Packet) may be used.
  • LCH ID logical channel number
  • Packet packet data convergence protocol identifier
  • PDCP ID Data Convergence Protocol ID
  • RB ID bearer identification
  • flow identifier to distinguish data of different TCP connections.
  • step S202 the target application or the user equipment has previously established a TCP connection with the corresponding target data server, that is, the base station has previously established with the SGW.
  • An S1 connection and / or bearer Then, at this time, the base station establishes an S1 connection and/or bearer with the LGW and the SGW, respectively, for respectively carrying data requests between the data requesting device and the target local cache device, and between the data requesting device and the target data server. Data request.
  • the base station may remove the bearer between the SGW and the SGW, and maintain only the bearer between the base station and the LGW; in another possible implementation scenario After the base station establishes a bearer with the LGW, the base station can simultaneously maintain the bearer between the base station and the SGW and the bearer between the base station and the LGW.
  • the target application installed in the data requesting device or the user equipment in the WTTx scenario can directly establish a TCP connection with the target local cache device. That is, the TCP connection may be between the target application installed in the data requesting device or the user device and the target local cache device.
  • the air interface (base station and data requesting device) bearer establishment is not triggered. That is to say, the data requesting device and the base station use the original air interface to transmit the bearer, but there is an S1 connection and/or bearer between the base station and the LGW and the SGW, respectively.
  • Step S205 the data requesting device detects the first service data request that the target address is the address of the target data server.
  • the first service data request may be triggered by the user performing some operations on the application in the data requesting device, or may be triggered when some applications in the data requesting device detect that the data needs to be updated.
  • the first service data request carries the target service data identifier, and is used to indicate the target service data requested by the data requesting device.
  • the target service data identifier may be a uniform resource locator of the target service data.
  • the data requesting device is a user equipment, and when the application triggers the first service data request, the data requesting device may directly detect. For example, when the user clicks on the B video in the A application, the data requesting device can detect the first service data request, where the target address of the first service data request is the address of the data server corresponding to the A application, and the B video is carried. The corresponding URL.
  • step S205 may be specifically:
  • the data requesting device receives the destination address sent by the user equipment as the address of the target data server. First business data request.
  • the data requesting device is a home gateway CPE
  • the home gateway CPE is connected to the user equipment through the wifi
  • the user equipment sends the first to the CPE after detecting the first service data request.
  • Business data request is a home gateway CPE
  • the data requesting device when the first request message sent by the data requesting device is the first service data request that includes the target service data identifier, the data requesting device directly performs step S206 after performing step S204.
  • Step S206 the data requesting device sends a second service data request to the base station.
  • the data requesting device modifies the target address in the first service data to the address of the target local cache device, thereby generating a second service data request, where the second service data request still carries the target service data identifier to indicate that the requested data is the target service. data.
  • the data requesting device may directly designate the wireless bearer channel according to the first service.
  • the second service data request generated by the data request is transmitted through the radio bearer channel between the data requesting device and the target local cache device that are pre-established in step S204, that is, the base station does not need to view the route of the second service data request at this time.
  • the information directly forwards the second service data request to the designated radio bearer established between the target and the local cache device.
  • the data requesting device may add an indication to the second service data request sent to the base station that the second service data request is routed to the target local cache device, where the indication may be the target local The IP address or index value of the cache device.
  • the base station may determine that the second service data request is sent to the target local cache device by acquiring the indication or the target address of the second service data request, so as to reach the target local cache device by using the pre-established radio bearer with the target local cache device. Send a second service data request.
  • the base station does not have the deep packet detection technology. Therefore, when the data request device is the user equipment, the application layer data needs to be transmitted to the modem module after the cross-layer communication with the target application. The data requesting device then transmits a second service data request for the modem module to the base station.
  • the base station has a deep packet detection technology, and the target application in the data requesting device can directly transmit the second service data request generated by the application layer. To the base station.
  • Step S207 The base station sends the second service data request to the target local cache device.
  • Step S208 The target local cache device detects whether the target service data corresponding to the target service data identifier is cached. If the cached target service data is detected, steps S209 to S210 are performed; otherwise, steps S211 to S212 or steps S213 to S215 are performed.
  • the target local cache device may detect, according to the target service data identifier carried in the device, whether the target service data corresponding to the target service data identifier is cached in the device. It can be understood that, in step S203, it is determined that the target local cache device is a local cache device that is authorized to cache the service data of the target data server, but the target local cache device may only cache part of the service data of the target data server or may not be fully cached. Any business data of the target data server, so the target local cache device needs to further detect whether the target service data is cached in this step.
  • Step S209 the target local cache device sends the cached target service data to the base station.
  • the response message (HTTP Response) may be sent to the base station, where the source IP address may be filled in as the target data server (or the data request device receives the IP address including the target local cache device).
  • the source IP address needs to be modified to the target data server address, and then the target service data is sent to the data requesting device through the established bearer.
  • Step S210 The base station sends the cached target service data to the data requesting device.
  • the base station may send the related data to the data requesting device. For example, if the data requesting device requests data of the B video, then the B video data sent by the base station can now be received.
  • Step S211 the target local cache device sends a third service data request to the target data server.
  • a TCP connection may be established with the target data server, and then a third service data request is sent to the target data server, where the target service data identifier is carried.
  • the source address of the third service data request may be a target local cache device or a data request device, which is not specifically limited herein.
  • the target local cache device may send a message to the data requesting device, requesting the number of teardown The TCP connection of the requesting device to the target local cache device is requested.
  • Step S212 the target data server sends the target service data to the data requesting device.
  • the target data server After receiving the third service data request, the target data server sends a response message to the target cache server, and then acquires the target service data and transmits the data to the data request device.
  • steps S211-S212 may also be steps S213-S215:
  • Step S213 the target local cache device sends uncached information for the target service data to the base station.
  • the uncached information for the target service data may be sent to the base station, where the cache information may be carried by the communication signaling, and used to indicate to the base station that the target local cache device does not cache the target service. data.
  • Step S214 The base station sends a third service data request to the target data server according to the uncached information.
  • the base station may send a fourth service data request to the target data server, where the third service data request carries the target service data identifier.
  • step S215 the target data server sends the target service data to the data requesting device.
  • the target data server After receiving the third service data request, the target data server sends a response message to the base station, and then acquires the target service data and transmits the data to the data requesting device.
  • Step S216 the data requesting device sends a first service data request to the base station.
  • the data requesting device sends a first service data request to the base station after determining that there is no target local cache device that authorizes the service data of the cache target data server.
  • Step S217 the base station sends a first service data request to the target data server.
  • the base station may determine to send the first service data request to the target data server according to the target address of the first service data request.
  • the target data server After receiving the first service data request, acquires the target service data and transmits the data to the data requesting device.
  • the data requesting device of the foregoing embodiment needs to resend the target service data. Give the user device.
  • the data requesting device determines to authorize the cache of the target data server service data according to the local cache device list sent by the base station in advance.
  • the target local cache device establishes a network connection with the target local cache device, so that the data request device can directly request the target service data from the local cache device with a relatively short distance, thereby avoiding the transmission caused when requesting data from the target data server.
  • the overhead is wasted and the transmission delay is large, thereby improving the response speed of the data requesting device after requesting data, thereby improving the user experience.
  • FIG. 3a is a schematic flowchart of another method for requesting cached data according to an embodiment of the present invention.
  • the method is directed to an implementation scenario in which a data requesting device is a user equipment UE.
  • the embodiment of the present invention is directed to a scenario in which the base station itself acts as a local cache device.
  • the scenes shown in FIG. 3a and FIG. 3b differ only in steps S302 and S305, and thus are collectively described in this embodiment.
  • Step S301 The base station sends a local cache device list to the data requesting device managed by the base station.
  • the base station is not connected to other independent local cache devices, and only the base station itself acts as a local cache device, and the content in the local cache device list is the IP address or/and port number of the base station itself.
  • Step S302 the data requesting device detects the first request message for the target data server.
  • step S301 the execution order is not limited between step S301 and step S302.
  • Step S303 The data requesting device determines, according to the local cache device list sent by the base station in advance, whether there is a target local cache device that authorizes the service data of the cache target data server in the local cache device list. If there is a target local cache device, steps S304 to S310 are performed; otherwise, steps S311 to S313 are performed.
  • the content in the local cache device list is the IP address or/and the port number of the base station itself, and the data requesting device only needs to determine whether the base station is the target local cache device that authorizes the service data of the cache target data server. Just fine. For specific implementation methods, reference may be made to step S203.
  • Step S304 the data requesting device establishes a network connection with the base station, and the network connection is used to send a service data request for the target data server to the target local cache device and further perform data transfer.
  • the TCP connection may be established with the base station, that is, the data transmission channel between the base station and the data requesting device is established, so that the data requesting device can receive the target data server.
  • the service data request may be directly sent to the base station. Further, the base station may send the requested service data to the data requesting device.
  • the data requesting device sends a second request message to the base station to which the data requesting device belongs, and the second request message may be a request for establishing a connection with the target local cache device.
  • the second request message carries the routing information, where the routing message is used to indicate the target local cache device, so that the base station establishes a connection between the data requesting device and the base station itself, thereby triggering the bearer establishment of the air interface (base station and data requesting device), or can be used.
  • the air interface bearer established when connecting with the target data server is previously established to transmit data transmitted to the base station.
  • RB Radio Bear
  • LCH ID logical channel number
  • Packet packet data convergence protocol identifier
  • PDCP ID Data Convergence Protocol ID
  • RB ID bearer identification
  • flow identifier to distinguish data of different TCP connections.
  • Step S305 the data requesting device detects the first service data request that the target address is the address of the target data server.
  • step S305 may be specifically:
  • the data requesting device receives the first service data request that the target address sent by the user equipment is the address of the target data server. As shown in Figure 3b.
  • Step S306 the data requesting device sends a second service data request to the base station.
  • the data requesting device may modify the target address in the first service data to the address of the base station, thereby generating a second service data request, and the second service data.
  • the request still carries the target service data identifier to indicate that the requested data is the target service data.
  • the second service data request includes routing information, and the routing information requested by the base station according to the second service data And determining that the target terminal of the second service data request is a base station.
  • the data requesting device may directly designate the wireless bearer channel according to the first service.
  • the second service data request generated by the data request is transmitted through the radio bearer channel between the data requesting device and the base station that is pre-established in step S304, that is, the base station does not need to view the routing information of the second service data request at this time.
  • the data requesting device may add an indication to the second service data request sent to the base station that the second service data request is routed to the target local cache device, where the indication may be the target local The IP address or index value of the cache device.
  • the base station may determine that the second service data request is sent to the target local cache device of the base station itself by obtaining the indication or parsing the target address of the second service data request.
  • Step S307 The base station detects whether the target local cache device caches the target service data corresponding to the target service data identifier. If the cached target service data is detected, step S308 is performed; otherwise, steps S309 to S310 are performed.
  • the base station may detect, according to the target service data identifier carried in the second service data request, whether the target service data corresponding to the target service data identifier is cached in the target local cache device of the base station.
  • Step S308 the base station sends the cached target service data to the data requesting device.
  • Step S309 the base station sends a third service data request to the target data server.
  • the base station may send a third service data request to the target data server, where the target service data identifier is carried.
  • the source address of the third service data request may be a base station or a data request device, which is not specifically limited herein.
  • Step S310 the target data server sends the target service data to the data requesting device.
  • Step S311 the data requesting device sends a first service data request to the base station.
  • Step S312 the base station sends a first service data request to the target data server.
  • Step S313 the target data server sends the target service data to the data requesting device.
  • the data requesting device of the foregoing embodiment needs to target after receiving the target service data from the base station or the target data server.
  • the service data is then sent to the user equipment.
  • the data requesting device after the data requesting device detects the first request message for the target data server, determining, according to the local cache device list sent by the base station, the authorization to cache the target data server service data.
  • the target local cache device establishes a network connection with the base station, so that the data requesting device can directly request the target service data from the base station, thereby avoiding waste of transmission overhead and large transmission delay caused when requesting data from the target data server. , thereby improving the response speed after the data request device requests the data, thereby improving the user experience.
  • the method for obtaining the cache data can be implemented in combination with the method flow in the above two embodiments.
  • FIG. 4 is a schematic structural diagram of a data requesting device according to an embodiment of the present invention. As shown in Figure 4, the device includes:
  • the processing module 410 is configured to detect a first request message for the target data server, and determine, according to the local cache device list sent by the base station in advance, a target local cache device for buffering the target data server service data; a network connection between the target local cache devices;
  • the sending module 420 is configured to send, by using the network connection, a service data request for the target data server to the target local cache device.
  • the processing module 410 is further configured to: detect that the target address is a first service data request of the target data server, where the first service data request carries a target service data identifier;
  • the sending module 420 is further configured to: send a second service data request to the target local cache device, where the second service data request carries the target service data identifier, where the second service data request is used to indicate the The target local cache device sends the cached target service data to the data request device when detecting that the target service data corresponding to the target service data identifier is cached;
  • the device further includes:
  • the receiving module 430 is configured to receive the target service number sent by the target local cache device according to.
  • the first request message includes a target service data identifier, and is used to request target service data corresponding to the target service data identifier;
  • the sending module 420 is further configured to: send a second service data request to the target local cache device, where the second service data request carries the target service data identifier, where the second service data request is used to indicate the The target local cache device sends the cached target service data to the data request device when detecting that the target service data corresponding to the target service data identifier is cached;
  • the device further includes:
  • the receiving module 430 is configured to receive the target service data sent by the target local cache device.
  • the local cache device list includes an identifier of at least one local cache device
  • the processing module 410 is configured to:
  • the local cache device corresponding to the first identifier is determined to be the target local cache device.
  • the receiving module 430 is further configured to:
  • the local cache device includes a base station to which the data request device belongs or/and at least one first cache device connected to the base station.
  • processing module 410 is configured to:
  • the base station And sending, by the base station to which the data requesting device belongs, the second request message, where the second request message carries routing information, where the routing message is used to indicate a target local cache device, and the second request message is used to indicate the
  • the base station establishes a connection between the data requesting device and the target local cache device.
  • the routing information includes an identifier of the target local cache device or an index value of the target local cache device.
  • processing module 410 is configured to:
  • the data requesting device determines, according to the local cache device list sent by the base station in advance, the target of authorizing the cache of the target data server service data.
  • the local cache device establishes a network connection with the target local cache device, so that the data requesting device can directly request the target service data from the local cache device with a relatively short distance, thereby avoiding waste of transmission overhead caused by requesting data from the target data server. And a large transmission delay, thereby improving the response speed after the data request device requests the data, thereby improving the user experience.
  • FIG. 5 is a schematic structural diagram of another data requesting device according to an embodiment of the present invention.
  • the device includes a processor 51, a memory 52, and a communication interface 53.
  • the processor 51 is connected to the memory 52 and the communication interface 53, for example, the processor 51 can be connected to the memory 52 and the communication interface 53 via a bus.
  • the processor 51 is configured to support the data requesting device to perform the corresponding function in the above method.
  • the processor 51 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 52 memory is used to store a list of local cache devices, program code, and the like.
  • the memory 52 may include a volatile memory (English: volatile memory), such as random access memory (English: random access memory, abbreviation: RAM); the memory 52 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 52 may also include a combination of the above types of memories.
  • the communication interface 53 is for communicating with the base station to transmit and receive messages involved in the above method.
  • the processor 51 can invoke the program code to perform the following operations:
  • Detecting a first request message for the target data server determining, according to the local cache device list sent by the base station in advance, a target local cache device for buffering the target data server service data; establishing a target local cache device with the target An inter-network connection, and a service data request for the target data server is sent to the target local cache device through the network connection.
  • the method is further configured to:
  • the first service data request carries the target service data identifier
  • the second service data request is sent to the target local cache device by using the communication interface 53
  • the second service data request carries the target service data identifier
  • the second service data request is used to indicate that the target local cache device requests the data request device when detecting the target service data corresponding to the cached target service data identifier Sending the cached target service data; receiving the target service data sent by the target local cache device through the communication interface 53.
  • the first request message includes a target service data identifier, and is used to request target service data corresponding to the target service data identifier;
  • the processor 51 After the processor 51 establishes a network connection with the target local cache device, it is further used to:
  • the cached target service data is sent to the data request device; and the target service data sent by the target local cache device is received through the communication interface 53.
  • the local cache device list includes an identifier of at least one local cache device
  • the processor 51 determines, according to the pre-acquired local cache device list, a target local cache device that is authorized to cache the target data server service data, specifically for:
  • the processor 51 before determining, by the processor 51, that the pre-acquired cache content authorization list has a first identifier that is consistent with the identifier of the at least one local cache device in the local cache device list, the processor is further configured to:
  • the cached content authorization list sent by the target data server is received through the communication interface 53.
  • the local cache device includes a base station to which the data request device belongs or/and at least one first cache device connected to the base station.
  • the processor 51 when the processor 51 establishes a network connection with the target local cache device, specifically:
  • the second request message Sending, by the communication interface 53, the second request message to the base station to which the data requesting device belongs, the second request message carrying routing information, the routing message is used to indicate a target local cache device, and the second request message is used by And instructing the base station to establish a connection between the data requesting device and the target local cache device.
  • the routing information includes an identifier of the target local cache device or an index value of the target local cache device.
  • the processor 51 when the processor 51 detects that the target address is the first service data request of the target data server, the processor 51 is specifically configured to:
  • the first service data request that the target address sent by the user equipment is the address of the target data server is received through the communication interface 53.
  • 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 processing module 610 is configured to obtain a local cache device list, where the local cache device list includes an identifier of the at least one local cache device.
  • a sending module 620 configured to send, to the data requesting device managed by the base station, the local cache device list, where the local cache device list is used by the data requesting device to determine a target for caching the target data server service data Local cache device.
  • the base station further includes:
  • the receiving module 630 is configured to receive a second request message sent by the data requesting device, where the second request message carries routing information, where the routing message is used to indicate a target local cache device;
  • the processing module 610 is further configured to: establish a connection between the data requesting device and the target local cache device according to the second request message.
  • processing module 610 is configured to:
  • the base station further includes:
  • the receiving module 630 is configured to receive a second service data request for the target local cache device that is sent after the network request is established between the data requesting device and the target local cache device, where the second service data request carries the target service data.
  • the processing module 610 is further configured to: when it is determined that the target local cache device has cached target service data corresponding to the target service data identifier, send the cached target service data to the data request device.
  • processing module 610 is configured to:
  • processing module 610 is further configured to:
  • the base station When it is determined that the target local cache device does not cache the target service data, the base station sends a third service data request to the target data server, where the third service data request carries the target service data identifier, the third The service data request is used to instruct the target data server to send the target service data to the data requesting device.
  • processing module 610 is configured to:
  • the data requesting device determines, according to the local cache device list sent by the base station in advance, the target of authorizing the cache of the target data server service data.
  • the local cache device establishes a network connection with the target local cache device, so that the data requesting device can directly request the target service data from the local cache device with a relatively short distance, thereby avoiding waste of transmission overhead caused by requesting data from the target data server. And a large transmission delay, thereby improving the response speed after the data request device requests the data, thereby 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 in performing the corresponding functions of the above methods.
  • 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 a list of local cache devices, program code, and the like.
  • 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)
  • ROM read-only memory
  • flash memory English: flash memory
  • hard disk English: hard disk drive, abbreviation: HDD
  • SSD solid state drive
  • memory 72 may also include a combination of the above types of memory.
  • the communication interface 73 is for communicating with the data requesting device or/and the target local cache device to send and receive messages involved in the above method.
  • the processor 71 can invoke the program code to perform the following operations:
  • a local cache device list to a data requesting device managed by the base station, the local cache device list including an identifier of at least one local cache device, the local cache device list being used by the data request device to determine authorization A target local cache device that caches the target data server service data.
  • the processor 71 is further configured to:
  • the processor 71 establishes the connection between the data requesting device and the target local cache device according to the second request message, specifically:
  • the processor 71 is further configured to:
  • a second service data request for the target local cache device that is sent after the network request is established between the data requesting device and the target local cache device, where the second service data request carries the target service data identifier;
  • the cached target service data is sent to the data request device through the communication interface 73.
  • the processor 71 determines that the target local cache device has cached the target service data requested by the target service data request, and sends the cached target service data to the data request device by using the communication interface 73, Specifically used for:
  • the processor is further configured to:
  • the target local cache device When it is determined that the target local cache device does not cache the target service data, send a third service data request to the target data server by using the communication interface 73, where the third service data request carries the target service data identifier, where the The three service data request is used to instruct the target data server to send the target service data to the data requesting device.
  • the processor 71 determines that the target local cache device does not cache the target service data
  • the processor is specifically configured to:
  • FIG. 8 is a schematic structural diagram of another data requesting device according to an embodiment of the present invention. As shown in Figure 8, the device includes:
  • the processor 810 is configured to detect a first request message for the target data server, and determine, according to the local cache device list sent by the base station in advance, a target local cache device for buffering the target data server service data; a network connection between the target local cache devices;
  • the transmitter 820 is configured to send, by using the network connection, a service data request for the target data server to the target local cache device.
  • the processor 810 is further configured to: detect that the target address is a first service data request of the target data server, where the first service data request carries a target service data identifier;
  • the transmitter 820 is further configured to: send a second service data request to the target local cache device, where the second service data request carries the target service data identifier, the second service data The request is used to indicate that the target local cache device sends the cached target service data to the data request device when detecting that the target service data corresponding to the target service data identifier is cached;
  • the device further includes:
  • the receiver 830 is configured to receive the target service data sent by the target local cache device.
  • the first request message includes a target service data identifier, and is used to request target service data corresponding to the target service data identifier;
  • the transmitter 820 is further configured to: send a second service data request to the target local cache device, where the second service data request carries the target service data identifier, where the second service data request is used to indicate the
  • the target local cache device sends the cached target service data to the data request device when detecting that the target service data corresponding to the target service data identifier is cached;
  • the device further includes:
  • the receiver 830 is configured to receive the target service data sent by the target local cache device.
  • the local cache device list includes an identifier of at least one local cache device
  • the processor 810 is configured to:
  • the local cache device corresponding to the first identifier is determined to be the target local cache device.
  • the receiver 830 is further configured to:
  • the local cache device includes a base station to which the data request device belongs or/and at least one first cache device connected to the base station.
  • the processor 810 is configured to:
  • the base station And sending, by the base station to which the data requesting device belongs, the second request message, where the second request message carries routing information, where the routing message is used to indicate a target local cache device, and the second request message is used to indicate the
  • the base station establishes a connection between the data requesting device and the target local cache device.
  • the routing information includes an identifier of the target local cache device or a target local cache setting.
  • the index value of the backup is a value of the backup.
  • the processor 810 is configured to:
  • the data requesting device determines, according to the local cache device list sent by the base station in advance, the target of authorizing the cache of the target data server service data.
  • the local cache device establishes a network connection with the target local cache device, so that the data requesting device can directly request the target service data from the local cache device with a relatively short distance, thereby avoiding waste of transmission overhead caused by requesting data from the target data server. And a large transmission delay, thereby improving the response speed after the data request device requests the data, thereby improving the user experience.
  • FIG. 9 is a schematic structural diagram of another base station according to an embodiment of the present invention. As shown in FIG. 9, the base station includes:
  • the processor 910 is configured to obtain a local cache device list, where the local cache device list includes an identifier of the at least one local cache device.
  • a transmitter 920 configured to send, to a data requesting device managed by the base station, the local cache device list, where the local cache device list is used by the data requesting device to determine a target for caching the target data server service data Local cache device.
  • the base station further includes:
  • a receiver 930 configured to receive a second request message sent by the data requesting device, where the second request message carries routing information, where the routing message is used to indicate a target local cache device;
  • the processor 910 is further configured to: establish, according to the second request message, a connection or a bearer of the data requesting device and the target local cache device.
  • the processor 910 is configured to:
  • the base station further includes:
  • the receiver 930 is configured to receive a second service data request for the target local cache device that is sent after the data requesting device establishes a network connection with the target local cache device, where the second service data request carries the target service data.
  • the processor 910 is further configured to: when it is determined that the target local cache device has cached the target service data corresponding to the target service data identifier, send the cached target service data to the data request device.
  • the processor 910 is configured to:
  • processor 910 is further configured to:
  • the base station When it is determined that the target local cache device does not cache the target service data, the base station sends a third service data request to the target data server, where the third service data request carries the target service data identifier, the third The service data request is used to instruct the target data server to send the target service data to the data requesting device.
  • the processor 910 is configured to:
  • the data requesting device determines, according to the local cache device list sent by the base station in advance, the target of authorizing the cache of the target data server service data.
  • the local cache device establishes a network connection with the target local cache device, so that the data requesting device can directly request the target service data from the local cache device with a relatively short distance, thereby avoiding waste of transmission overhead caused by requesting data from the target data server. And a large transmission delay, thereby improving the response speed after the data request device requests the data, thereby improving the user experience.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

Landscapes

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

Abstract

本发明实施例提供了一种缓存数据获取方法。数据请求设备检测到针对目标数据服务器的第一请求消息后,根据预先接收到基站发送的本地缓存设备列表,确定用于缓存所述目标数据服务器业务数据的目标本地缓存设备,之后数据请求设备建立与所述目标本地缓存设备之间的网络连接,并通过所述网络连接向所述目标本地缓存设备发送针对所述目标数据服务器的业务数据请求。通过将目标数据服务器的数据缓存至基站侧的本地缓存设备中,使数据请求设备可以直接向目标本缓存设备请求目标业务数据,避免了向目标数据服务器请求数据时造成的传输开销浪费以及较大的传输时延,从而提高数据请求设备请求数据后的响应速度。

Description

一种缓存数据请求方法及相关设备 技术领域
本发明涉及通信技术领域,尤其涉及一种缓存数据请求方法及相关设备。
背景技术
随着智能终端的日渐普及以及移动设备的大规模增长,移动数据流量呈现持续的爆发式增长。巨大的网络流量爆发式增长,极易造成网络拥塞、数据冗余传输与用户体验差等问题。为了缓解由于内容和流量的爆炸式增长造成的网络基础设施压力过大的问题,本地缓存或者称之为内容下沉得到了学术界和产业界的高度关注。
当前比较常见的缓存方式是通过CDN(Content Delivery Network,内容分发网络),内容分发网络负责将位于整个带宽服务链两端的服务器和用户联系起来,将网站的内容发布到最接近用户的网络边缘,使用户可以就近获取所需的内容,缓解互联网网络拥塞状况,提高用户访问网站的响应速度。但是,CDN现部署于骨干网,用户设备需要经过无线网以及核心网之后才到达骨干网,而无线网与核心网之间的链路传输开销和传输时延较大。另外,CDN网络的部署花费较大,需要部署分布式存储、负载均衡、网络请求重定向、内容管理等要件,如果将CDN部署到其他网络开销较大、投资花费较高。
发明内容
本发明提供了一种缓存数据请求方法及相关设备,可以在缓解网络拥塞的同时降低数据传输开销和传输时延,提高数据请求设备请求数据后的响应速度。
本发明第一方面提供了一种缓存数据请求方法。数据请求设备检测到针对目标数据服务器的第一请求消息后,根据预先接收到基站发送的本地缓存设备列表,确定用于缓存所述目标数据服务器业务数据的目标本地缓存设备,之后数据请求设备建立与所述目标本地缓存设备之间的网络连接,并通过所述网络连接向所述目标本地缓存设备发送针对所述目标数据服务器的业务数 据请求。
在本技术方案中,通过将目标数据服务器的数据缓存至基站侧的本地缓存设备中,使数据请求设备可以直接向目标本缓存设备请求目标业务数据,避免了向目标数据服务器请求数据时造成的传输开销浪费以及较大的传输时延,从而提高数据请求设备请求数据后的响应速度,提升了用户体验。
在第一方面的第一种可能的实现方式中,数据请求设备建立与所述目标本地缓存设备之间的网络连接之后,在检测到目标地址为所述目标数据服务器的第一业务数据请求时,向所述目标本地缓存设备发送第二业务数据请求,其中,第一业务数据请求与第二业务数据请求都携带目标业务数据标识,所述第二业务数据请求用于指示所述目标本地缓存设备在检测到已缓存所述目标业务数据标识对应的目标业务数据时向数据请求设备发送缓存的所述目标业务数据。
在第一方面的第二种可能的实现方式中,第一请求消息包括目标业务数据标识,用于请求所述目标业务数据标识对应的目标业务数据。那么,数据请求设备建立与所述目标本地缓存设备之间的网络连接之后,数据请求设备向所述目标本地缓存设备发送第二业务数据请求,所述第二业务数据请求携带所述目标业务数据标识,所述第二业务数据请求用于指示所述目标本地缓存设备在检测到已缓存所述目标业务数据标识对应的目标业务数据时向数据请求设备发送缓存的所述目标业务数据。
结合第一方面以及第一方面的第一种或第二种中任一可能的实现方式,在第一方面的第三种可能的实现方式中,本地缓存设备列表包括至少一个本地缓存设备的标识,数据请求设备判断预先获取到的缓存内容授权列表中是否存在与所述本地缓存设备列表中的本地缓存设备的标识一致的第一标识,其中,缓存内容授权列表包括所述目标数据服务器授权缓存的至少一个本地缓存设备的标识,若存在所述第一标识,则确定所述第一标识对应的本地缓存设备为所述目标本地缓存设备。
结合第一方面的第三种可能的实现方式,在第一方面的第四种可能的实现方式中,数据请求设备判断预先获取到的缓存内容授权列表中是否存在与所述本地缓存设备列表中的至少一个本地缓存设备的标识一致的第一标识之 前,接收所述目标数据服务器发送的所述缓存内容授权列表。
结合第一方面的第三种可能的实现方式,在第一方面的第五种可能的实现方式中,所述本地缓存设备包括所述数据请求设备所属的基站或/和与所述基站连接的至少一个第一缓存设备。
在第一方面的第六种可能的实现方式中,所述数据请求设备向所述数据请求设备所属的基站发送所述第二请求消息,所述第二请求消息携带路由信息,所述路由消息用于指示目标本地缓存设备,所述第二请求消息用于指示所述基站建立所述数据请求设备和所述目标本地缓存设备的连接。
结合第一方面的第六种可能的实现方式,在第一方面的第七种可能的实现方式中,所述路由信息包括目标本地缓存设备的标识或目标本地缓存设备的索引值。
结合第一方面或第一方面的第一种至第七种中任一可能的实现方式,在第一方面的第八种可能的实现方式中,在WTTx的场景中,数据请求设备为与用户设备家庭网关,数据请求设备接收用户设备发送的目标地址为目标数据服务器的地址的第一业务数据请求。
本发明第二方面提供了另一种缓存数据请求方法。基站向所述基站管理的数据请求设备发送本地缓存设备列表,所述本地缓存设备列表包括至少一个本地缓存设备的标识,所述本地缓存设备列表被所述数据请求设备用于确定授权缓存所述目标数据服务器业务数据的目标本地缓存设备。
在本技术方案中,通过将目标数据服务器的数据缓存至基站侧的本地缓存设备中,使数据请求设备可以直接向距离较近的本地缓存设备请求目标业务数据,避免了向目标数据服务器请求数据时造成的传输开销浪费以及较大的传输时延,从而提高数据请求设备请求数据后的响应速度,提升了用户体验。
在第二方面的第一种可能的实现方式中,所述基站接收所述数据请求设备发送的第二请求消息,所述第二请求消息携带路由信息,所述路由消息用于指示目标本地缓存设备,所述基站根据所述第二请求消息建立所述数据请求设备和所述目标本地缓存设备的连接。
结合第二方面的第一种可能的实现方式,在第二方面的第二种可能的实 现方式中,所述基站建立所述基站与所述数据请求设备之间或/和所述基站与所述目标本地缓存设备之间的传输承载,所述传输承载用于传输所述数据请求设备和目标本地缓存设备之间的数据。
在第二方面的第三种可能的实现方式中,所述基站接收所述数据请求设备与所述目标本地缓存设备之间建立网络连接后发送的针对目标本地缓存设备的第二业务数据请求,所述第二业务数据请求携带目标业务数据标识,当确定所述目标本地缓存设备已缓存所述目标业务数据标识对应的目标业务数据时,所述基站向所述数据请求设备发送缓存的所述目标业务数据。
结合第二方面的第三种可能的实现方式,在第二方面的第四种可能的实现方式中,所述基站向所述目标本地缓存设备发送所述第二业务数据请求,接收到所述目标本地缓存设备在检测到已缓存所述目标业务数据时发送的缓存的所述目标业务数据后,向所述数据请求设备发送缓存的所述目标业务数据。
结合第二方面的第三种可能的实现方式,在第二方面的第五种可能的实现方式中,所述基站接收所述数据请求设备与所述目标本地缓存设备之间建立网络连接后发送的针对目标本地缓存设备的第二业务数据请求之后,当确定所述目标本地缓存设备未缓存所述目标业务数据时,向目标数据服务器发送第三业务数据请求,所述第三业务数据请求携带所述目标业务数据标识,所述第三业务数据请求用于指示所述目标数据服务器向所述数据请求设备发送所述目标业务数据。
结合第二方面的第五种可能的实现方式,在第二方面的第六种可能的实现方式中,所述基站向所述目标本地缓存设备发送所述第二业务数据请求,所述第二业务数据请求用于指示所述目标本地缓存设备在检测到未缓存所述目标业务数据时,向所述基站发送针对所述目标业务数据的未缓存信息,所述基站接收到所述目标本地缓存设备发送的针对所述目标业务数据的未缓存信息则确定所述目标本地缓存设备未缓存所述目标业务数据。
本发明第三方面提供了一种数据请求设备。该设备包括处理器、存储器以及通信接口。处理器连接到存储器和通信接口,例如处理器可以通过总线连接到存储器和通信接口。通信接口用于与基站等设备进行通信。存储器用 于存储本地缓存设备列表等。处理器用于执行第一方面的部分或全部流程。
本发明第四方面提供了另一种数据请求设备,包括:
处理模块,用于检测到针对目标数据服务器的第一请求消息;根据预先接收到基站发送的本地缓存设备列表,确定用于缓存所述目标数据服务器业务数据的目标本地缓存设备;建立与所述目标本地缓存设备之间的网络连接;
发送模块,用于通过所述网络连接向所述目标本地缓存设备发送针对所述目标数据服务器的业务数据请求。
在本技术方案中,通过将目标数据服务器的数据缓存至基站侧的本地缓存设备中,使数据请求设备可以直接向目标本缓存设备请求目标业务数据,避免了向目标数据服务器请求数据时造成的传输开销浪费以及较大的传输时延,从而提高数据请求设备请求数据后的响应速度,提升了用户体验。
在第四方面的第一种可能的实现方式中,
所述处理模块还用于:检测到目标地址为所述目标数据服务器的第一业务数据请求,所述第一业务数据请求携带目标业务数据标识;
所述发送模块还用于:向所述目标本地缓存设备发送第二业务数据请求,所述第二业务数据请求携带所述目标业务数据标识,所述第二业务数据请求用于指示所述目标本地缓存设备在检测到已缓存所述目标业务数据标识对应的目标业务数据时向数据请求设备发送缓存的所述目标业务数据;
所述设备还包括:
接收模块,用于接收所述目标本地缓存设备发送的所述目标业务数据。
在第四方面的第二种可能的实现方式中,所述第一请求消息包括目标业务数据标识,用于请求所述目标业务数据标识对应的目标业务数据;
所述发送模块还用于:向所述目标本地缓存设备发送第二业务数据请求,所述第二业务数据请求携带所述目标业务数据标识,所述第二业务数据请求用于指示所述目标本地缓存设备在检测到已缓存所述目标业务数据标识对应的目标业务数据时向数据请求设备发送缓存的所述目标业务数据;
所述设备还包括:
接收模块,用于接收所述目标本地缓存设备发送的所述目标业务数据。
结合第四方面以及第四方面的第一种或第二种中任一可能的实现方式, 在第四方面的第三种可能的实现方式中,所述本地缓存设备列表包括至少一个本地缓存设备的标识;
所述处理模块用于:
判断预先获取到的缓存内容授权列表中是否存在与所述本地缓存设备列表中的本地缓存设备的标识一致的第一标识,所述缓存内容授权列表包括所述目标数据服务器授权缓存的至少一个本地缓存设备的标识;
若存在所述第一标识,则确定所述第一标识对应的本地缓存设备为所述目标本地缓存设备。
结合第四方面的第三种可能的实现方式,在第四方面的第四种可能的实现方式中,所述接收模块还用于:
接收所述目标数据服务器发送的所述缓存内容授权列表。
结合第四方面的第三种可能的实现方式,在第四方面的第五种可能的实现方式中,所述本地缓存设备包括所述数据请求设备所属的基站或/和与所述基站连接的至少一个第一缓存设备。
在第四方面的第六种可能的实现方式中,所述处理模块用于:
向所述数据请求设备所属的基站发送所述第二请求消息,所述第二请求消息携带路由信息,所述路由消息用于指示目标本地缓存设备,所述第二请求消息用于指示所述基站建立所述数据请求设备和所述目标本地缓存设备的连接或承载。
结合第四方面的第六种可能的实现方式,在第四方面的第七种可能的实现方式中,所述路由信息包括目标本地缓存设备的标识或目标本地缓存设备的索引值。
结合第四方面或第四方面的第一种至第七种中任一可能的实现方式,在第四方面的第八种可能的实现方式中,所述处理模块用于:
接收用户设备发送的目标地址为目标数据服务器的地址的第一业务数据请求。
本发明第五方面提供了另一种数据请求设备,该设备包括处理器、发送器以及接收器。数据请求设备通过上述模块实现第一方面的部分或全部方法。
本发明第六方面提供了一种基站。该基站包括处理器、存储器以及通信 接口。处理器连接到存储器和通信接口,例如处理器可以通过总线连接到存储器和通信接口。通信接口用于与数据请求设备等设备进行通信。存储器用于存储本地缓存设备列表等。处理器用于执行第二方面的部分或全部流程。
本发明第七方面提供了另一种基站,包括:
处理模块,用于获取本地缓存设备列表,所述本地缓存设备列表包括至少一个本地缓存设备的标识;
发送模块,用于向所述基站管理的数据请求设备发送所述本地缓存设备列表,所述本地缓存设备列表被所述数据请求设备用于确定用于缓存所述目标数据服务器业务数据的目标本地缓存设备。
在第七方面的第一种可能的实现方式中,所述基站还包括:
接收模块,用于接收所述数据请求设备发送的第二请求消息,所述第二请求消息携带路由信息,所述路由消息用于指示目标本地缓存设备;
所述处理模块还用于:根据所述第二请求消息建立所述数据请求设备和所述目标本地缓存设备的连接或承载。
结合第七方面的第一种可能的实现方式,在第七方面的第二种可能的实现方式中,所述处理模块用于:
建立所述基站与所述数据请求设备之间或/和所述基站与所述目标本地缓存设备之间的传输承载,所述传输承载用于传输所述数据请求设备和目标本地缓存设备之间的数据。
在第七方面的第三种可能的实现方式中,所述基站还包括:
接收模块,用于接收所述数据请求设备与所述目标本地缓存设备之间建立网络连接后发送的针对目标本地缓存设备的第二业务数据请求,所述第二业务数据请求携带目标业务数据标识;
所述处理模块还用于:当确定所述目标本地缓存设备已缓存所述目标业务数据标识对应的目标业务数据时,向所述数据请求设备发送缓存的所述目标业务数据。
结合第七方面的第三种可能的实现方式,在第七方面的第四种可能的实现方式中,所述处理模块用于:
向所述目标本地缓存设备发送所述第二业务数据请求;
接收所述目标本地缓存设备在检测到已缓存所述目标业务数据时发送的缓存的所述目标业务数据;
向所述数据请求设备发送缓存的所述目标业务数据。
结合第七方面的第三种可能的实现方式,在第七方面的第五种可能的实现方式中,所述处理模块还用于:
当确定所述目标本地缓存设备未缓存所述目标业务数据时,所述基站向目标数据服务器发送第三业务数据请求,所述第三业务数据请求携带所述目标业务数据标识,所述第三业务数据请求用于指示所述目标数据服务器向所述数据请求设备发送所述目标业务数据。
结合第七方面的第五种可能的实现方式,在第七方面的第六种可能的实现方式中,所述处理模块用于:
向所述目标本地缓存设备发送所述第二业务数据请求,所述第二业务数据请求用于指示所述目标本地缓存设备在检测到未缓存所述目标业务数据时,向所述基站发送针对所述目标业务数据的未缓存信息;
接收所述目标本地缓存设备发送的针对所述目标业务数据的未缓存信息确定所述目标本地缓存设备未缓存所述目标业务数据。
本发明第八方面提供了另一种基站,该基站包括处理器、发送器以及接收器。基站通过上述模块实现第二方面的部分或全部方法。
附图说明
为了更清楚地说明本发明实施例中的技术方案,下面将对实施例中所需要使用的附图作简单地介绍,显而易见地,下面描述中的附图仅仅是本发明的一些实施例,对于本领域普通技术人员来讲,在不付出创造性劳动性的前提下,还可以根据这些附图获得其他的附图。
图1a是本发明实施例提供的一种通信系统的系统架构图;
图1b是本发明实施例提供的另一种通信系统的系统架构图;
图1c是本发明实施例提供的另一种通信系统的系统架构图;
图2a是本发明实施例提供的一种缓存数据请求方法的流程示意图;
图2b是本发明实施例提供的另一种缓存数据请求方法的流程示意图;
图3a是本发明实施例提供的另一种缓存数据请求方法的流程示意图;
图3b是本发明实施例提供的另一种缓存数据请求方法的流程示意图;
图4是本发明实施例提供的一种数据请求设备的结构示意图;
图5是本发明实施例提供的另一种数据请求设备的结构示意图;
图6是本发明实施例提供的一种基站的结构示意图;
图7是本发明实施例提供的另一种基站的结构示意图;
图8是本发明实施例提供的另一种数据请求设备的结构示意图;
图9是本发明实施例提供的另一种基站的结构示意图。
具体实施方式
下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚、完整地描述,显然,所描述的实施例仅仅是本发明一部分实施例,而不是全部的实施例。基于本发明中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。
在此部分,首先对本发明中各个实施例均涉及的一些基本概念进行说明。
本发明实施例中的基站包括LTE(长期演进,Long-Term Evolution,LTE)系统中的演进型基站(Evolutional Node B,eNB),或者未来通信系统中的网络设备,如5G中的网络设备(如控制器)。
本发明实施例中的数据请求设备,在一些实施场景中可以指用户设备(UE,User Equipment)或指调制解调器Modem模块,具体包括移动电话(英文:cellphone),智能手机(英文:smartphone),计算机(英文:computer),平板电脑(英文:tablet computer),移动互联网设备(英文:mobile Internet device,MID)和可穿戴设备等可以通过基站接入网络的设备。在适用于无线宽带到户(WTTx,Wireless To The x)的实施场景中,数据请求设备可以指客户终端设备(CPE,Customer Premise Equipment),CPE可以作为家庭网关,用于提供家庭或企业等客户的宽带、IPTV、VOIP等业务的综合接入。CPE可以与家庭用户设备(UE)通过Wifi等无线连接,再与基站通过LTE或者WCDMA(宽带码分多址,Wideband Code Division Multiple Access)等无线接入方式建立连接,从而完成家庭用户设备通过CPE接入网络,节省铺 设有线网络的费用。
本发明实施例中的本地缓存设备(LC,Local Cache),在一些实施场景中,可以指一个独立的缓存服务器,通过本地网关(LGW,Local Gateway)与基站连接。在另一些实施场景中,本地缓存设备可以是基站本身的一部分,例如可以是基站中的一个缓存设备。
本发明实施例中的数据服务器可以是通过互联网向UE提供应用服务的第三方服务器(Over The Top Server),也可以是运营商的内容提供服务器(Content Provide Server)等。
本发明实施例适用于多种通信系统,如LTE系统、无线宽带到户(WTTx,Wireless To The x)系统、第五代通信系统(5G)以及设备到设备(D2D,Device to Device)通信系统等。
图1a是本发明实施例提供的一种通信系统的系统架构图,包括用户设备110a,基站120a以及至少一个本地缓存设备131a、132a及133a,其中基站120a可以通过本地网关140a(LGW,Local Gateway)与本地缓存设备131a、132a及133a相连。在图1a所示的系统架构图中,一个基站120a可以和多个本地缓存设备(131a、132a及133a)连接,也就是说,当用户设备110a请求的不同的业务数据分别在本地缓存设备131a、132a及133a中对应存在本地缓存时,用户设备110a都可以通过基站120a分别向本地缓存设备131a、132a及133a发送相应的业务数据请求。
图1b是本发明实施例提供的另一种通信系统的系统架构图,包括用户设备110b,本地缓存设备130b以及至少一个基站121b、122b和123b,其中,基站(121b、122b和123b)可以通过本地网关140b与本地缓存设备130b相连。在图1b所示的系统架构图中,多个基站(121b、122b和123b)可以和一个本地缓存设备130b连接,也就是说,当用户设备110b请求某一缓存在本地缓存设备130b中的业务数据时,即使在基站121b、122b和123b之间移动时,仍然可以分别通过121b、122b和123b向同一个本地缓存设备130b获取请求的同一业务数据,这样可以避免切换基站时重建业务。
进一步的,图1a和图1b中的本地缓存设备也可以就是基站本身的一部分,则无需再通过本地网关与本地缓存设备相连,用户设备仅将业务数据请 求发送给基站即可。
本发明实施例的技术方案还适用于无线宽带到户WTTx的实施场景中,比如,图1c是本发明实施例提供的另一种通信系统的系统架构图,包括用户设备110c、家庭网关CPE120c以及基站130c以及本地缓存设备140c,其中,基站130c可以通过本地网关150c与本地缓存设备140c相连。在图1c所示的系统架构图中,用户设备110c可以向家庭网关CPE120c请求某一缓存在本地缓存设备130c中的业务数据,由家庭网关CPE120c通过基站120c向本地缓存设备130c发送相应的业务数据请求。
与图1a和图1b的系统架构相似的,WTTx的实施场景中的基站可以连接多个本地缓存设备,多个基站也可以连接同一个本地缓存设备。进一步的,本地缓存设备也可以就是基站本身的一部分,则无需再通过本地网关与本地缓存设备相连,家庭网关CPE仅将业务数据请求发送给基站即可。
请参阅图2a和图2b,图2a是本发明实施例提供的一种缓存数据请求方法的流程示意图,该方法流程针对的是数据请求设备为用户设备UE的实施场景。在该实施场景中,用户设备,例如智能手机中安装有可以触发向目标数据服务器发送请求的目标应用程序或客户端,用户设备或Modem模块可以与目标应用程序或客户端之间进行跨层通信。图2b是本发明实施例提供的另一种缓存数据请求方法的流程示意图,该方法流程针对的是数据请求设备为家庭网关CPE的实施场景。本发明实施例针对的是基站本身不作为本地缓存设备,仅连接了多个独立的本地缓存设备的情景。在本发明实施例中,图2a和图2b所示的场景仅在步骤S202和S205中有所区别,因此统一在该实施例中进行描述。
具体的,方法包括:
步骤S201,基站向基站管理的数据请求设备发送本地缓存设备列表。
本地缓存设备列表包括至少一个本地缓存设备的标识,其中本地缓存设备可以是与基站连接的独立的缓存设备,也可以是基站本身的一部分。本地缓存设备的标识则是指可以唯一的识别本地缓存设备的一种标识,例如,本地缓存设备的IP(Internet Protocol,网络之间互连的协议)地址、端口号等 都可以作为本地缓存设备的标识。进一步可以携带标识对应的索引值(index),数据请求设备可以是用户设备,也可以是家庭网关CPE。
在一种可能的情景中,基站未与其他独立的本地缓存设备连接,仅基站本身作为本地缓存设备,那么本地缓存设备列表中的内容即为基站本身的IP地址或/和端口号;在另一种可能的情景中,基站本身不作为本地缓存设备,但是连接了多个独立的本地缓存设备,那么本地缓存设备列表的内容即为基站连接的至少一个本地缓存设备的IP地址或/和端口号;在又一种可能的情景中,基站本身作为本地缓存设备,同时也连接了至少一个独立的本地缓存设备,那么本地缓存设备列表中的内容即为基站本身以及基站连接的至少一个本地缓存设备的IP地址或/和端口号。
本发明实施例针对的是基站本身不作为本地缓存设备,但是连接了多个独立的本地缓存设备的情景,即本发明实施例中后续提到的目标本地缓存设备为与基站相连的第一缓存设备。
在本发明实施例中,基站可以预先将配置或保存的本地缓存设备列表发送给数据请求设备,具体来说,该本地缓存设备列表可以通过不同的消息承载来发送给数据请求设备。例如,可以通过RRC(无线资源控制,Radio Resource Control)专用信令或者基站的系统消息来承载本地缓存设备列表。
在步骤S201之前或之后,用户使用用户设备的某一应用程序,触发其向DNS(Domain Name System,域名系统)服务器查询目标数据服务器的地址,并向目标数据服务器建立TCP(Transmission Control Protocol,传输控制协议)连接,此时的连接是该应用程序和目标服务器之间的TCP连接。在WTTx场景中,在CPE接收基站发送的本地缓存设备列表之前或之后,此时是用户设备通过CPE和目标数据服务器建立TCP连接。上述两种实施场景中的TCP连接建立过程所发送的消息都需要通过数据请求设备与基站以及基站和核心网网关之间的承载传输,TCP连接建立的过程可以触发相关承载建立的流程,后续数据请求设备和目标数据服务器之间传递的数据可以通过对应建立的承载来传递。
步骤S202,数据请求设备检测到针对目标数据服务器的第一请求消息。
第一请求消息可以是预先需要与目标数据服务器建立连接时发出的连接 建立的请求,也可以是向目标数据服务器请求某些业务数据时发出的业务数据请求。数据请求设备可以通过检测第一请求消息的目标地址是否为目标数据服务器的IP地址和/或端口号来确定是否是针对目标数据服务器的。
需要说明的是,这里数据请求设备中的目标应用程序可以通过跨层通信与数据请求设备进行通信,从而使数据请求设备检测到针对目标数据服务器的第一请求消息。
进一步的,当数据请求设备向目标数据服务器发送第一请求消息时,即触发该目标应用程序与目标数据服务器之间建立TCP连接,从而触发数据请求设备所属的基站对应的建立与目标数据服务器相连的SGW(Serving Gateway,服务网关)建立了一条S1连接,即基站与SGW之间建立对应的RAB(Radio Access Bearer,无线接入承载),基站与数据请求设备之间触发空口的无线承载建立,用于数据请求设备与目标数据服务器之间的数据传输。
此时目标应用程序或用户设备可以在向目标数据服务器建立连接时,可以接收基站在相关数据包中发送的本地缓存设备列表;或者接收数据请求设备发送的从基站接收的本地缓存设备列表。根据与收到的缓存内容授权列表比较,确定是否向目标本地缓存设备建立连接。步骤S201和步骤S202不特别限定执行顺序。
需要说明的是,如图2a,在一种可能的实施场景中,数据请求设备为用户设备,则当目标应用程序触发第一请求消息时,数据请求设备可以直接检测。
可选的,在WTTx场景下,步骤S202具体可以为:
数据请求设备接收用户设备发送的针对目标数据服务器的第一请求消息。
如图2b,在另一种适用于WTTx的实施场景中,数据请求设备为家庭网关CPE,家庭网关CPE通过wifi与用户设备相连,用户设备检测到第一请求消息之后向数据请求设备发送该第一请求消息。
步骤S203,数据请求设备根据预先接收到基站发送的本地缓存设备列表,判断本地缓存设备列表中是否存在授权缓存目标数据服务器的业务数据的目标本地缓存设备。若存在目标本地缓存设备,则执行步骤S204~S215; 否则,执行步骤S216~S218。
授权缓存目标数据服务器的业务数据的本地缓存设备是指具有缓存目标数据服务器的业务数据权限的本地缓存设备,数据请求设备可以预先获取到缓存内容授权列表,其中可以包含本地缓存设备标识信息,即包含至少一个本地缓存设备的标识,用于指示所访问的目标数据服务器可用的本地缓存设备。将本地缓存设备列表中的至少一个本地缓存设备的标识与本地缓存设备标识信息中至少一个本地缓存设备的标识进行匹配,匹配出的标识对应的本地缓存设备即为目标本地缓存设备。其中本地缓存设备的标识可以是IP地址和/或端口号,可用于寻址相关本地缓存设备。
进一步的,缓存内容授权列表还可以包括源用户设备标识信息或/和统一资源定位符信息(Uniform Resource Locator,URL)。源用户设备标识信息可以为用户设备的设备标识,用于验证用户设备是否有权获取本地缓存设备中的缓存。统一资源定位符URL信息用于指示目标数据服务器中某一URL对应的业务数据已进行本地缓存,可与本地缓存设备标识信息相结合来指示在某一本地缓存设备中缓存的业务数据对应的URL。其中源用户设备标识信息可以是源用户设备或终端的IP地址和/或端口号或MAC(Media Access Control,媒体访问控制)地址,可用于寻址相关源用户设备或终端。
具体实施中,数据请求设备可以判断缓存内容授权列表中是否存在与本地缓存设备列表中的本地缓存设备的标识一致的第一标识,若存在第一标识,则确定第一标识对应的本地缓存设备即为目标本地缓存设备;若不存在第一标识,则说明与基站相连的至少一个本地缓存设备中均不具备缓存目标数据服务器的业务数据的权限,即不存在目标本地缓存设备。
例如,设表1为缓存内容授权列表,表2为本地缓存设备列表,将表1和表2对比后可以确定,两个表中一致的IP地址为112.111.154.224,因此IP地址为112.111.154.224的本地缓存设备即为目标本地缓存设备。
Figure PCTCN2016106446-appb-000001
表1:缓存内容授权列表(示例)
Figure PCTCN2016106446-appb-000002
表2:本地缓存设备列表(示例)
当缓存内容授权列表包括统一资源定位符URL信息时,缓存内容授权列表中不仅可以指示授权缓存目标数据服务器的业务数据的至少一个本地缓存设备,还可以精确到指示授权缓存目标数据服务器中的某一个本地缓存设备缓存的所有URL对应的业务数据。在一些可能的实施场景中,第一请求消息本身携带目标业务数据标识,这里的目标业务数据标识就可以指URL,那么数据请求设备可以通过缓存内容授权列表获取授权缓存URL的至少一个本地缓存设备标识,将获取到的至少一个本地缓存设备的标识与本地缓存设备列表中的至少一个本地缓存设备的标识相匹配,确定目标本地缓存设备。
例如,设表3为缓存内容授权列表,表2为本地缓存设备列表,第一业务数据请求的目标业务数据标识为URL3,可以确定IP地址为148.16.12.12和207.211.135.210的两个本地缓存设备都授权缓存了URL3对应的目标业务数据,则进一步确定表2中的IP地址中是否存在与表3的授权缓存URL3的本地缓存设备的IP地址一致的IP地址,可以看出的,IP地址为207.211.135.210的本地缓存设备即为目标本地缓存设备。
Figure PCTCN2016106446-appb-000003
表3:缓存内容授权列表(示例)
需要说明的是,缓存内容授权列表可以是在目标应用程序或用户设备与目标数据服务器建立TCP连接时,目标数据服务器发送给目标应用程序或用户设备的,数据请求设备与目标应用程序之间可以跨层获取缓存内容授权列表,或者数据请求设备解析发送给目标应用程序或用户设备的数据包获得的;也可以是在数据请求设备进行网络注册时,公共陆地移动网络(PLMN,Public Land Mobile Network)根据数据请求设备注册情况发送给数据请求设备的,或是从目标应用程序中跨层传递的用户注册信息,这里不作具体限定。
进一步的,在数据请求设备确定得目标本地缓存设备存在多个时,可以根据预先配置的优先级选择一个,或根据一定的运算规则选择一个。
步骤S204,数据请求设备建立与目标本地缓存设备之间的网络连接,所述网络连接用于向所述目标本地缓存设备发送针对所述目标数据服务器的业务数据请求并进一步进行数据传递。
在数据请求设备确定所属基站侧存在目标本地缓存设备后,则可以与目标本地缓存设备建立TCP连接,即建立目标本地缓存设备与数据请求设备之间的数据传输通道,从而可以使数据请求设备在接收到针对目标数据服务器的业务数据请求时,直接向目标本地缓存设备发起业务数据请求即可。进一步的,也可以是目标本地缓存设备将请求的业务数据发送给数据请求设备。
在连接建立的过程中,数据请求设备向数据请求设备所属的基站发送第 二请求消息,该第二请求消息可以是用于与目标本地缓存设备建立连接的请求。其中,第二请求消息携带路由信息,该路由消息用于指示目标本地缓存设备,从而使基站建立数据请求设备和目标本地缓存设备的连接。具体的,路由信息可以包括目标本地缓存设备的标识或目标本地缓存设备的索引值(index)。
具体实施中,可以针对与目标本地缓存设备相连的本地网关(Local Gateway,LGW)建立缓存传输资源承载,即S1连接,可以通过Initial UE message(初始化UE消息)或其他S1消息建立连接,此时LGW具有一定的MME(Mobile Management Entity移动性管理实体)功能,可以进行控制面连接的建立和用户面承载的分配建立。在另一种实施方式中,可以是基站仍与MME建立控制面连接,但在对应的消息中增加指示说明用户面承载是与LGW建立的,由MME进行RAB(Radio Access Bearer,无线接入承载)指派,并建立基站和LGW的用户面传输通道,用于承载数据请求设备向目标本地缓存设备发送数据请求。
在建立相关承载的过程中,第二请求消息可以包含在RRC(无线资源控制,Radio Resource Control)消息,其中携带指示信息通知基站向目标本地缓存设备发送用户面连接请求,触发基站与目标本地缓存设备之间建立相关承载;也可以是基站通过第二请求消息的目标地址确定该请求的目标终端为目标本地缓存设备后,触发基站与目标本地缓存设备之间建立S1连接。这里,建立S1连接,触发建立目标本地缓存设备与基站的RAB,打通业务数据发送的通道。同时也包括空口(基站和数据请求设备)承载建立,或者可以使用之前建立与目标数据服务器连接时建立的空口承载来传递发送给目标本地缓存设备的数据。需要说明的是,对于空口的承载RB(Radio Bear,无线链路承载),不同的RB对应不同的TCP,其中可以通过逻辑信道号(logical channel ID,LCH ID)或分组数据汇聚协议标识(Packet Data Convergence Protocol ID,PDCP ID)或承载标识(RB ID)或者流标识来区分不同的TCP连接的数据。
进一步的,步骤S202中已经说明,目标应用程序或用户设备之前已经与对应的目标数据服务器建立了TCP连接,即基站之前已经与SGW建立了 一条S1连接和/或承载。那么此时,基站就是与LGW以及SGW之间分别建立一条S1连接和/或承载,用于分别承载数据请求设备与目标本地缓存设备之间的数据请求,以及数据请求设备与目标数据服务器之间的数据请求。需要说明的是,在一种可能的实施场景中,基站在与LGW建立了连接之后,可以拆除与SGW之间的承载,仅维护基站与LGW之间的承载;在另一种可能的实施场景中,基站在与LGW建立了承载之后,可以同时维护基站与SGW之间的承载以及基站与LGW之间的承载。
在一些实施场景中,当基站具备深度包检测技术(DPI,Deep Packet Inspection)时,数据请求设备中安装的目标应用程序或者WTTx场景中的用户设备可以直接与目标本地缓存设备建立TCP连接,也即该TCP连接可以是数据请求设备中安装的目标应用程序或者用户设备与目标本地缓存设备之间的。在该实施场景中,由于数据请求设备不感知该TCP连接建立过程,因此,不会触发空口(基站和数据请求设备)承载建立。也就是说,数据请求设备与基站之间使用原来的空口进行传输的承载,但是基站与LGW以及SGW之间分别存在一条S1连接和/或承载。
步骤S205,数据请求设备检测到目标地址为目标数据服务器的地址的第一业务数据请求。
第一业务数据请求可以是用户针对数据请求设备中的应用程序进行某些操作后触发生成的,也可以是数据请求设备中的某些应用程序检测到数据需要更新等情况时触发生成的。第一业务数据请求携带目标业务数据标识,用于指示数据请求设备请求的目标业务数据,例如,目标业务数据标识可以是目标业务数据的统一资源定位符。
需要说明的是,如图2a,在一种可能的实施场景中,数据请求设备为用户设备,则当应用程序触发第一业务数据请求时,数据请求设备可以直接检测。例如,当用户点击A应用程序中的B视频时,数据请求设备就可以检测到第一业务数据请求,其中第一业务数据请求的目标地址为A应用程序对应的数据服务器的地址,携带B视频对应的URL。
可选的,在WTTx场景下,步骤S205具体可以为:
数据请求设备接收用户设备发送的目标地址为目标数据服务器的地址的 第一业务数据请求。
如图2b,在另一种适用于WTTx的实施场景中,数据请求设备为家庭网关CPE,家庭网关CPE通过wifi与用户设备相连,用户设备检测到第一业务数据请求之后向CPE发送该第一业务数据请求。
可选的,当数据请求设备发送的第一请求消息就是包括目标业务数据标识的第一业务数据请求时,数据请求设备在执行完步骤S204后直接执行步骤S206。
步骤S206,数据请求设备向基站发送第二业务数据请求。
数据请求设备将第一业务数据中的目标地址修改为目标本地缓存设备的地址,从而生成第二业务数据请求,第二业务数据请求仍然携带目标业务数据标识,以指示所请求的数据为目标业务数据。
在一种可能的实施场景中,数据请求设备确定存在目标本地缓存设备后,再接收到针对目标数据服务器的第一业务数据请求时,可以通过指定无线承载通道的方式,直接将根据第一业务数据请求生成的第二业务数据请求通过步骤S204中预先建立的数据请求设备与目标本地缓存设备之间的无线承载通道进行传输,也就是说,基站此时无需再查看第二业务数据请求的路由信息,直接向指定的与目标本地缓存设备之间建立的无线承载转发第二业务数据请求即可。
在另一种可能的实施场景中,数据请求设备可以在发送给基站的第二业务数据请求中增加一个指示说明是第二业务数据请求是路由到目标本地缓存设备,其中指示说明可以是目标本地缓存设备的IP地址或者索引值等。基站通过获取指示说明或者解析第二业务数据请求的目标地址可以确定第二业务数据请求是发往目标本地缓存设备的,从而通过与目标本地缓存设备之间预先建立的无线承载向目标本地缓存设备发送第二业务数据请求。
需要说明的是,在一般的情况下,基站不具备深度包检测技术,因此在数据请求设备为用户设备时,需要将与目标应用程序跨层通信后将应用层数据传输给调制解调模块,然后数据请求设备将针对调制解调模块的第二业务数据请求传输给基站。在另一种情况下,基站具备深度包检测技术,则数据请求设备中的目标应用程序可以直接将应用层生成的第二业务数据请求传输 给基站。
步骤S207,基站向所述目标本地缓存设备发送所述第二业务数据请求。
步骤S208,目标本地缓存设备检测是否缓存了所述目标业务数据标识对应的目标业务数据。若检测到已缓存目标业务数据,则执行步骤S209~S210;否则,执行步骤S211~S212或步骤S213~S215。
目标本地缓存设备在接收到第二业务数据请求之后,可以根据其中携带的目标业务数据标识,检测设备中是否缓存了目标业务数据标识对应的目标业务数据。可以理解的,步骤S203中确定的是目标本地缓存设备是被授权缓存目标数据服务器的业务数据的本地缓存设备,但是目标本地缓存设备可能仅缓存了目标数据服务器的部分业务数据或者可能完全未缓存目标数据服务器的任何业务数据,因此目标本地缓存设备需要在本步骤中进一步检测是否缓存了目标业务数据。
步骤S209,目标本地缓存设备向基站发送缓存的目标业务数据。
当目标本地缓存设备确定缓存有目标业务数据后,可以向基站发送响应消息(HTTP Response),其中源IP地址可以填写为目标数据服务器(或者数据请求设备在收到包含目标本地缓存设备IP地址的数据包后,需要将源IP地址修改为目标数据服务器地址),之后通过建立的承载向数据请求设备发送该目标业务数据。
步骤S210,基站向数据请求设备发送缓存的所述目标业务数据。
基站接收到目标本地缓存设备发送的响应消息和/或目标业务数据后,就可以向数据请求设备发送相关数据。例如,如果数据请求设备请求的是B视频的数据,那么现在就可以接收到基站发送的B视频数据了。
步骤S211,目标本地缓存设备向目标数据服务器发送第三业务数据请求。
当目标本地缓存设备确定未缓存目标业务数据后,可以与目标数据服务器建立TCP连接,然后向目标数据服务器发送第三业务数据请求,其中携带目标业务数据标识。需要说明的是,这里的第三业务数据请求的源地址可以是目标本地缓存设备也可以是数据请求设备,这里不作具体限定。
可选的,目标本地缓存设备可以向数据请求设备发送消息,要求拆除数 据请求设备与目标本地缓存设备的TCP连接。
步骤S212,目标数据服务器向数据请求设备发送目标业务数据。
目标数据服务器在接收到第三业务数据请求后,向目标缓存服务器发送响应消息,之后则获取目标业务数据并传输给数据请求设备。
可选的,步骤S211~S212还可以为步骤S213~S215:
步骤S213,目标本地缓存设备向基站发送针对目标业务数据的未缓存信息。
当目标本地缓存设备确定未缓存目标业务数据后,可以向基站发送针对目标业务数据的未缓存信息,该为缓存信息可以通过通信信令承载,用于向基站说明目标本地缓存设备未缓存目标业务数据。
步骤S214,基站根据未缓存信息,向目标数据服务器发送第三业务数据请求。
基站接收到针对目标业务数据的未缓存信息后,可以向目标数据服务器发送第四业务数据请求,该第三业务数据请求中携带目标业务数据标识。
步骤S215,目标数据服务器向数据请求设备发送目标业务数据。
目标数据服务器在接收到第三业务数据请求后,向基站发送响应消息,之后则获取目标业务数据并传输给数据请求设备。
步骤S216,数据请求设备向基站发送第一业务数据请求。
数据请求设备在确定不存在授权缓存目标数据服务器的业务数据的目标本地缓存设备后,向基站发送第一业务数据请求。
步骤S217,基站向目标数据服务器发送第一业务数据请求。
基站根据第一业务数据请求的目标地址,可以确定向目标数据服务器发送第一业务数据请求。
步骤S218,目标数据服务器向数据请求设备发送目标业务数据。
目标数据服务器在接收到第一业务数据请求后,则获取目标业务数据并传输给数据请求设备。
需要说明的是,在图2b所示的WTTx场景中,上述实施例的数据请求设备在接收到来自基站、目标本地缓存设备或目标数据服务器的目标业务数据后,都需要将目标业务数据再发送给用户设备。
本图2a和2b所示的实施例中,数据请求设备检测到针对目标数据服务器的第一请求消息后,根据预先接收到基站发送的本地缓存设备列表,确定授权缓存所述目标数据服务器业务数据的目标本地缓存设备,建立与目标本地缓存设备之间的网络连接,从而使数据请求设备可以直接向距离较近的本地缓存设备请求目标业务数据,避免了向目标数据服务器请求数据时造成的传输开销浪费以及较大的传输时延,从而提高数据请求设备请求数据后的响应速度,提升了用户体验。
请参阅图3a和图3b,图3a是本发明实施例提供的另一种缓存数据请求方法的流程示意图,该方法流程针对的是数据请求设备为用户设备UE的实施场景;图3b是本发明实施例提供的另一种缓存数据请求方法的流程示意图,该方法流程针对的是数据请求设备为家庭网关CPE的实施场景。本发明实施例针对的是基站本身作为本地缓存设备的情景。在本发明实施例中,图3a和图3b所示的场景仅在步骤S302和S305中有所区别,因此统一在该实施例中进行描述。
步骤S301,基站向基站管理的数据请求设备发送本地缓存设备列表。
在该发明实施例中,基站未与其他独立的本地缓存设备连接,仅基站本身作为本地缓存设备,那么本地缓存设备列表中的内容即为基站本身的IP地址或/和端口号。
步骤S302,数据请求设备检测到针对目标数据服务器的第一请求消息。
需要说明的是,步骤S301和步骤S302之间不限定执行顺序。
步骤S303,数据请求设备根据预先接收到基站发送的本地缓存设备列表,判断本地缓存设备列表中是否存在授权缓存目标数据服务器的业务数据的目标本地缓存设备。若存在目标本地缓存设备,则执行步骤S304~S310;否则,执行步骤S311~S313。
在该发明实施例中,本地缓存设备列表中的内容即为基站本身的IP地址或/和端口号,则数据请求设备只需确定基站是否是授权缓存目标数据服务器的业务数据的目标本地缓存设备即可。具体的实施方法可以进一步参考步骤S203。
步骤S304,数据请求设备建立与基站之间的网络连接,所述网络连接用于向所述目标本地缓存设备发送针对所述目标数据服务器的业务数据请求并进一步进行数据传递。
在数据请求设备确定所属基站为目标本地缓存设备后,则可以与基站建立TCP连接,即建立基站与数据请求设备之间的数据传输通道,从而可以使数据请求设备在接收到针对目标数据服务器的业务数据请求时,直接向基站发起业务数据请求即可。进一步的,也可以是基站将请求的业务数据发送给数据请求设备。
在连接建立的过程中,数据请求设备向数据请求设备所属的基站发送第二请求消息,该第二请求消息可以是用于与目标本地缓存设备建立连接的请求。其中,第二请求消息携带路由信息,该路由消息用于指示目标本地缓存设备,从而使基站建立数据请求设备和基站本身的连接,进而触发空口(基站和数据请求设备)承载建立,或者可以使用之前建立与目标数据服务器连接时建立的空口承载来传递发送给基站的数据。需要说明的是,对于空口的承载RB(Radio Bear,无线链路承载),不同的RB对应不同的TCP,其中可以通过逻辑信道号(logical channel ID,LCH ID)或分组数据汇聚协议标识(Packet Data Convergence Protocol ID,PDCP ID)或承载标识(RB ID)或者流标识来区分不同的TCP连接的数据。
步骤S305,数据请求设备检测到目标地址为目标数据服务器的地址的第一业务数据请求。
可选的,在WTTx场景下,步骤S305具体可以为:
数据请求设备接收用户设备发送的目标地址为目标数据服务器的地址的第一业务数据请求。如图3b所示。
步骤S306,数据请求设备向基站发送第二业务数据请求。
数据请求设备在确定基站为授权缓存目标数据服务器的业务数据的目标本地缓存设备后,可以将第一业务数据中的目标地址修改为基站的地址,从而生成第二业务数据请求,第二业务数据请求仍然携带目标业务数据标识,以指示所请求的数据为目标业务数据。
第二业务数据请求包括路由信息,基站根据第二业务数据请求的路由信 息,可以确定该第二业务数据请求的目标终端是基站。
在一种可能的实施场景中,数据请求设备确定存在目标本地缓存设备后,再接收到针对目标数据服务器的第一业务数据请求时,可以通过指定无线承载通道的方式,直接将根据第一业务数据请求生成的第二业务数据请求通过步骤S304中预先建立的数据请求设备与基站之间的无线承载通道进行传输,也就是说,基站此时无需再查看第二业务数据请求的路由信息。
在另一种可能的实施场景中,数据请求设备可以在发送给基站的第二业务数据请求中增加一个指示说明是第二业务数据请求是路由到目标本地缓存设备,其中指示说明可以是目标本地缓存设备的IP地址或者索引值等。基站通过获取指示说明或者解析第二业务数据请求的目标地址可以确定第二业务数据请求是发往基站本身的目标本地缓存设备的。
步骤S307,基站检测目标本地缓存设备是否缓存了所述目标业务数据标识对应的目标业务数据。若检测到已缓存目标业务数据,则执行步骤S308;否则,执行步骤S309~S310。
基站在确定自身为目标本地缓存设备后,可以根据第二业务数据请求携带的目标业务数据标识,检测基站自身的目标本地缓存设备中是否缓存了目标业务数据标识对应的目标业务数据。
步骤S308,基站向数据请求设备发送缓存的目标业务数据。
步骤S309,基站向目标数据服务器发送第三业务数据请求。
当基站确定自身的目标本地缓存设备未缓存目标业务数据后,可以向目标数据服务器发送第三业务数据请求,其中携带目标业务数据标识。需要说明的是,这里的第三业务数据请求的源地址可以是基站也可以是数据请求设备,这里不作具体限定。
步骤S310,目标数据服务器向数据请求设备发送目标业务数据。
步骤S311,数据请求设备向基站发送第一业务数据请求。
步骤S312,基站向目标数据服务器发送第一业务数据请求。
步骤S313,目标数据服务器向数据请求设备发送目标业务数据。
需要说明的是,在图3b所示的WTTx场景中,上述实施例的数据请求设备在接收到来自基站或目标数据服务器的目标业务数据后,都需要将目标 业务数据再发送给用户设备。
本图3a和3b所示的实施例中,数据请求设备检测到针对目标数据服务器的第一请求消息后,根据预先接收到基站发送的本地缓存设备列表,确定授权缓存所述目标数据服务器业务数据的目标本地缓存设备,建立与基站之间的网络连接,从而使数据请求设备可以直接向基站请求目标业务数据,避免了向目标数据服务器请求数据时造成的传输开销浪费以及较大的传输时延,从而提高数据请求设备请求数据后的响应速度,提升了用户体验。
在基站本身作为本地缓存设备同时也连接了至少一个独立的本地缓存设备的情景中,缓存数据的获取方法可以结合上述两个实施例中的方法流程实施。
请参阅图4,图4是本发明实施例提供的一种数据请求设备的结构示意图。如图4所示,该设备包括:
处理模块410,用于检测到针对目标数据服务器的第一请求消息;根据预先接收到基站发送的本地缓存设备列表,确定用于缓存所述目标数据服务器业务数据的目标本地缓存设备;建立与所述目标本地缓存设备之间的网络连接;
发送模块420,用于通过所述网络连接向所述目标本地缓存设备发送针对所述目标数据服务器的业务数据请求。
可选的,
所述处理模块410还用于:检测到目标地址为所述目标数据服务器的第一业务数据请求,所述第一业务数据请求携带目标业务数据标识;
所述发送模块420还用于:向所述目标本地缓存设备发送第二业务数据请求,所述第二业务数据请求携带所述目标业务数据标识,所述第二业务数据请求用于指示所述目标本地缓存设备在检测到已缓存所述目标业务数据标识对应的目标业务数据时向数据请求设备发送缓存的所述目标业务数据;
所述设备还包括:
接收模块430,用于接收所述目标本地缓存设备发送的所述目标业务数 据。
可选的,所述第一请求消息包括目标业务数据标识,用于请求所述目标业务数据标识对应的目标业务数据;
所述发送模块420还用于:向所述目标本地缓存设备发送第二业务数据请求,所述第二业务数据请求携带所述目标业务数据标识,所述第二业务数据请求用于指示所述目标本地缓存设备在检测到已缓存所述目标业务数据标识对应的目标业务数据时向数据请求设备发送缓存的所述目标业务数据;
所述设备还包括:
接收模块430,用于接收所述目标本地缓存设备发送的所述目标业务数据。
可选的,所述本地缓存设备列表包括至少一个本地缓存设备的标识;
所述处理模块410用于:
判断预先获取到的缓存内容授权列表中是否存在与所述本地缓存设备列表中的本地缓存设备的标识一致的第一标识,所述缓存内容授权列表包括所述目标数据服务器授权缓存的至少一个本地缓存设备的标识;
若存在所述第一标识,则确定所述第一标识对应的本地缓存设备为所述目标本地缓存设备。
可选的,所述接收模块430还用于:
接收所述目标数据服务器发送的所述缓存内容授权列表。
可选的,所述本地缓存设备包括所述数据请求设备所属的基站或/和与所述基站连接的至少一个第一缓存设备。
可选的,所述处理模块410用于:
向所述数据请求设备所属的基站发送所述第二请求消息,所述第二请求消息携带路由信息,所述路由消息用于指示目标本地缓存设备,所述第二请求消息用于指示所述基站建立所述数据请求设备和所述目标本地缓存设备的连接。
可选的,所述路由信息包括目标本地缓存设备的标识或目标本地缓存设备的索引值。
可选的,所述处理模块410用于:
接收用户设备发送的目标地址为目标数据服务器的地址的第一业务数据请求。
在图4所示的实施例中,数据请求设备检测到针对目标数据服务器的第一请求消息后,根据预先接收到基站发送的本地缓存设备列表,确定授权缓存所述目标数据服务器业务数据的目标本地缓存设备,建立与目标本地缓存设备之间的网络连接,从而使数据请求设备可以直接向距离较近的本地缓存设备请求目标业务数据,避免了向目标数据服务器请求数据时造成的传输开销浪费以及较大的传输时延,从而提高数据请求设备请求数据后的响应速度,提升了用户体验。
请参阅图5,图5是本发明实施例提供的另一种数据请求设备的结构示意图。如图5所示,该设备包括处理器51、存储器52以及通信接口53。处理器51连接到存储器52和通信接口53,例如处理器51可以通过总线连接到存储器52和通信接口53。
处理器51被配置为支持所述数据请求设备执行上述方法中相应的功能。该处理器51可以是中央处理器(英文: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)或其任意组合。
存储器52存储器用于存储本地缓存设备列表以及程序代码等。存储器52可以包括易失性存储器(英文:volatile memory),例如随机存取存储器(英文:random access memory,缩写:RAM);存储器52也可以包括非易失性存储器(英文:non-volatile memory),例如只读存储器(英文:read-only memory,缩写:ROM),快闪存储器(英文:flash memory),硬盘(英文:hard disk drive,缩写:HDD)或固态硬盘(英文:solid-state drive,缩写:SSD);存储器52还可以包括上述种类的存储器的组合。
通信接口53用于与基站通信以收发上述方法中所涉及的消息。
处理器51可以调用所述程序代码以执行以下操作:
检测到针对目标数据服务器的第一请求消息;根据预先接收到基站发送的本地缓存设备列表,确定用于缓存所述目标数据服务器业务数据的目标本地缓存设备;建立与所述目标本地缓存设备之间的网络连接,并通过所述网络连接向所述目标本地缓存设备发送针对所述目标数据服务器的业务数据请求。
可选的,处理器51建立与所述目标本地缓存设备之间的网络连接之后,还用于:
检测到目标地址为所述目标数据服务器的第一业务数据请求,所述第一业务数据请求携带目标业务数据标识;通过通信接口53向所述目标本地缓存设备发送第二业务数据请求,所述第二业务数据请求携带所述目标业务数据标识,所述第二业务数据请求用于指示所述目标本地缓存设备在检测到已缓存所述目标业务数据标识对应的目标业务数据时向数据请求设备发送缓存的所述目标业务数据;通过通信接口53接收所述目标本地缓存设备发送的所述目标业务数据。
可选的,所述第一请求消息包括目标业务数据标识,用于请求所述目标业务数据标识对应的目标业务数据;
处理器51建立与所述目标本地缓存设备之间的网络连接之后,还用于:
通过通信接口53向所述目标本地缓存设备发送第二业务数据请求,所述第二业务数据请求携带所述目标业务数据标识,所述第二业务数据请求用于指示所述目标本地缓存设备在检测到已缓存所述目标业务数据标识对应的目标业务数据时向数据请求设备发送缓存的所述目标业务数据;通过通信接口53接收所述目标本地缓存设备发送的所述目标业务数据。
可选的,所述本地缓存设备列表包括至少一个本地缓存设备的标识;
处理器51根据预先获取到的本地缓存设备列表,确定授权缓存所述目标数据服务器业务数据的目标本地缓存设备时,具体用于:
判断预先获取到的缓存内容授权列表中是否存在与所述本地缓存设备列表中的本地缓存设备的标识一致的第一标识,所述缓存内容授权列表包括所 述目标数据服务器授权缓存的至少一个本地缓存设备的标识;若存在所述第一标识,则确定所述第一标识对应的本地缓存设备为所述目标本地缓存设备。
可选的,处理器51判断预先获取到的缓存内容授权列表中是否存在与所述本地缓存设备列表中的至少一个本地缓存设备的标识一致的第一标识之前,还用于:
通过通信接口53接收所述目标数据服务器发送的所述缓存内容授权列表。
可选的,所述本地缓存设备包括所述数据请求设备所属的基站或/和与所述基站连接的至少一个第一缓存设备。
可选的,处理器51建立与所述目标本地缓存设备之间的网络连接时,具体用于:
通过通信接口53向所述数据请求设备所属的基站发送所述第二请求消息,所述第二请求消息携带路由信息,所述路由消息用于指示目标本地缓存设备,所述第二请求消息用于指示所述基站建立所述数据请求设备和所述目标本地缓存设备的连接。
可选的,所述路由信息包括目标本地缓存设备的标识或目标本地缓存设备的索引值。
可选的,处理器51检测到目标地址为所述目标数据服务器的第一业务数据请求时,具体用于:
通过通信接口53接收用户设备发送的目标地址为目标数据服务器的地址的第一业务数据请求。
请参阅图6,图6是本发明实施例提供的一种基站的结构示意图。如图6所示,该基站包括:
处理模块610,用于获取本地缓存设备列表,所述本地缓存设备列表包括至少一个本地缓存设备的标识;
发送模块620,用于向所述基站管理的数据请求设备发送所述本地缓存设备列表,所述本地缓存设备列表被所述数据请求设备用于确定用于缓存所述目标数据服务器业务数据的目标本地缓存设备。
可选的,所述基站还包括:
接收模块630,用于接收所述数据请求设备发送的第二请求消息,所述第二请求消息携带路由信息,所述路由消息用于指示目标本地缓存设备;
所述处理模块610还用于:根据所述第二请求消息建立所述数据请求设备和所述目标本地缓存设备的连接。
可选的,所述处理模块610用于:
建立所述基站与所述数据请求设备之间或/和所述基站与所述目标本地缓存设备之间的传输承载,所述传输承载用于传输所述数据请求设备和目标本地缓存设备之间的数据。
可选的,所述基站还包括:
接收模块630,用于接收所述数据请求设备与所述目标本地缓存设备之间建立网络连接后发送的针对目标本地缓存设备的第二业务数据请求,所述第二业务数据请求携带目标业务数据标识;
所述处理模块610还用于:当确定所述目标本地缓存设备已缓存所述目标业务数据标识对应的目标业务数据时,向所述数据请求设备发送缓存的所述目标业务数据。
可选的,所述处理模块610用于:
向所述目标本地缓存设备发送所述第二业务数据请求;
接收所述目标本地缓存设备在检测到已缓存所述目标业务数据时发送的缓存的所述目标业务数据;
向所述数据请求设备发送缓存的所述目标业务数据。
可选的,所述处理模块610还用于:
当确定所述目标本地缓存设备未缓存所述目标业务数据时,所述基站向目标数据服务器发送第三业务数据请求,所述第三业务数据请求携带所述目标业务数据标识,所述第三业务数据请求用于指示所述目标数据服务器向所述数据请求设备发送所述目标业务数据。
可选的,所述处理模块610用于:
向所述目标本地缓存设备发送所述第二业务数据请求,所述第二业务数据请求用于指示所述目标本地缓存设备在检测到未缓存所述目标业务数据 时,向所述基站发送针对所述目标业务数据的未缓存信息;
接收所述目标本地缓存设备发送的针对所述目标业务数据的未缓存信息确定所述目标本地缓存设备未缓存所述目标业务数据。
在图6所示的实施例中,数据请求设备检测到针对目标数据服务器的第一请求消息后,根据预先接收到基站发送的本地缓存设备列表,确定授权缓存所述目标数据服务器业务数据的目标本地缓存设备,建立与目标本地缓存设备之间的网络连接,从而使数据请求设备可以直接向距离较近的本地缓存设备请求目标业务数据,避免了向目标数据服务器请求数据时造成的传输开销浪费以及较大的传输时延,从而提高数据请求设备请求数据后的响应速度,提升了用户体验。
请参阅图7,图7是本发明实施例提供的另一种基站的结构示意图。如图7所示,该基站包括处理器71、存储器72以及通信接口73。处理器71连接到存储器72和通信接口73,例如处理器71可以通过总线连接到存储器72和通信接口73。
处理器71被配置为支持所述基站执行上述方法中相应的功能。该处理器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存储器用于存储本地缓存设备列表以及程序代码等。存储器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向所述基站管理的数据请求设备发送本地缓存设备列表,所述本地缓存设备列表包括至少一个本地缓存设备的标识,所述本地缓存设备列表被所述数据请求设备用于确定授权缓存所述目标数据服务器业务数据的目标本地缓存设备。
可选的,处理器71还用于:
通过通信接口73接收所述数据请求设备发送的第二请求消息,所述第二请求消息携带路由信息,所述路由消息用于指示目标本地缓存设备;根据所述第二请求消息建立所述数据请求设备和所述目标本地缓存设备的连接。
可选的,处理器71根据所述第二请求消息建立所述数据请求设备和所述目标本地缓存设备的连接时,具体用于:
建立所述基站与所述数据请求设备之间或/和所述基站与所述目标本地缓存设备之间的传输承载,所述传输承载用于传输所述数据请求设备和目标本地缓存设备之间的数据。
可选的,处理器71还用于:
通过通信接口73接收所述数据请求设备与所述目标本地缓存设备之间建立网络连接后发送的针对目标本地缓存设备的第二业务数据请求,所述第二业务数据请求携带目标业务数据标识;当确定所述目标本地缓存设备已缓存所述目标业务数据标识对应的目标业务数据时,通过通信接口73向所述数据请求设备发送缓存的所述目标业务数据。
可选的,处理器71当确定所述目标本地缓存设备已缓存所述目标业务数据请求所请求的目标业务数据,通过通信接口73向所述数据请求设备发送缓存的所述目标业务数据时,具体用于:
通过通信接口73向所述目标本地缓存设备发送所述第二业务数据请求;通过通信接口73接收所述目标本地缓存设备在检测到已缓存所述目标业务数据时发送的缓存的所述目标业务数据;通过通信接口73向所述数据请求设 备发送缓存的所述目标业务数据。
可选的,处理器通过通信接口73接收所述数据请求设备与所述目标本地缓存设备之间建立网络连接后发送的针对目标本地缓存设备的第二业务数据请求之后,还用于:
当确定所述目标本地缓存设备未缓存所述目标业务数据时,通过通信接口73向目标数据服务器发送第三业务数据请求,所述第三业务数据请求携带所述目标业务数据标识,所述第三业务数据请求用于指示所述目标数据服务器向所述数据请求设备发送所述目标业务数据。
可选的,处理器71确定所述目标本地缓存设备未缓存所述目标业务数据时,具体用于:
通过通信接口73向所述目标本地缓存设备发送所述第二业务数据请求,所述第二业务数据请求用于指示所述目标本地缓存设备在检测到未缓存所述目标业务数据时,向所述基站发送针对所述目标业务数据的未缓存信息;
通过通信接口73接收所述目标本地缓存设备发送的针对所述目标业务数据的未缓存信息确定所述目标本地缓存设备未缓存所述目标业务数据。
请参阅图8,图8是本发明实施例提供的另一种数据请求设备的结构示意图。如图8所示,该设备包括:
处理器810,用于检测到针对目标数据服务器的第一请求消息;根据预先接收到基站发送的本地缓存设备列表,确定用于缓存所述目标数据服务器业务数据的目标本地缓存设备;建立与所述目标本地缓存设备之间的网络连接;
发送器820,用于通过所述网络连接向所述目标本地缓存设备发送针对所述目标数据服务器的业务数据请求。
可选的,
所述处理器810还用于:检测到目标地址为所述目标数据服务器的第一业务数据请求,所述第一业务数据请求携带目标业务数据标识;
所述发送器820还用于:向所述目标本地缓存设备发送第二业务数据请求,所述第二业务数据请求携带所述目标业务数据标识,所述第二业务数据 请求用于指示所述目标本地缓存设备在检测到已缓存所述目标业务数据标识对应的目标业务数据时向数据请求设备发送缓存的所述目标业务数据;
所述设备还包括:
接收器830,用于接收所述目标本地缓存设备发送的所述目标业务数据。
可选的,所述第一请求消息包括目标业务数据标识,用于请求所述目标业务数据标识对应的目标业务数据;
所述发送器820还用于:向所述目标本地缓存设备发送第二业务数据请求,所述第二业务数据请求携带所述目标业务数据标识,所述第二业务数据请求用于指示所述目标本地缓存设备在检测到已缓存所述目标业务数据标识对应的目标业务数据时向数据请求设备发送缓存的所述目标业务数据;
所述设备还包括:
接收器830,用于接收所述目标本地缓存设备发送的所述目标业务数据。
可选的,所述本地缓存设备列表包括至少一个本地缓存设备的标识;
所述处理器810用于:
判断预先获取到的缓存内容授权列表中是否存在与所述本地缓存设备列表中的本地缓存设备的标识一致的第一标识,所述缓存内容授权列表包括所述目标数据服务器授权缓存的至少一个本地缓存设备的标识;
若存在所述第一标识,则确定所述第一标识对应的本地缓存设备为所述目标本地缓存设备。
可选的,所述接收器830还用于:
接收所述目标数据服务器发送的所述缓存内容授权列表。
可选的,所述本地缓存设备包括所述数据请求设备所属的基站或/和与所述基站连接的至少一个第一缓存设备。
可选的,所述处理器810用于:
向所述数据请求设备所属的基站发送所述第二请求消息,所述第二请求消息携带路由信息,所述路由消息用于指示目标本地缓存设备,所述第二请求消息用于指示所述基站建立所述数据请求设备和所述目标本地缓存设备的连接。
可选的,所述路由信息包括目标本地缓存设备的标识或目标本地缓存设 备的索引值。
可选的,所述处理器810用于:
接收用户设备发送的目标地址为目标数据服务器的地址的第一业务数据请求。
在图8所示的实施例中,数据请求设备检测到针对目标数据服务器的第一请求消息后,根据预先接收到基站发送的本地缓存设备列表,确定授权缓存所述目标数据服务器业务数据的目标本地缓存设备,建立与目标本地缓存设备之间的网络连接,从而使数据请求设备可以直接向距离较近的本地缓存设备请求目标业务数据,避免了向目标数据服务器请求数据时造成的传输开销浪费以及较大的传输时延,从而提高数据请求设备请求数据后的响应速度,提升了用户体验。
请参阅图9,图9是本发明实施例提供的另一种基站的结构示意图。如图9所示,该基站包括:
处理器910,用于获取本地缓存设备列表,所述本地缓存设备列表包括至少一个本地缓存设备的标识;
发送器920,用于向所述基站管理的数据请求设备发送所述本地缓存设备列表,所述本地缓存设备列表被所述数据请求设备用于确定用于缓存所述目标数据服务器业务数据的目标本地缓存设备。
可选的,所述基站还包括:
接收器930,用于接收所述数据请求设备发送的第二请求消息,所述第二请求消息携带路由信息,所述路由消息用于指示目标本地缓存设备;
所述处理器910还用于:根据所述第二请求消息建立所述数据请求设备和所述目标本地缓存设备的连接或承载。
可选的,所述处理器910用于:
建立所述基站与所述数据请求设备之间或/和所述基站与所述目标本地缓存设备之间的传输承载,所述传输承载用于传输所述数据请求设备和目标本地缓存设备之间的数据。
可选的,所述基站还包括:
接收器930,用于接收所述数据请求设备与所述目标本地缓存设备之间建立网络连接后发送的针对目标本地缓存设备的第二业务数据请求,所述第二业务数据请求携带目标业务数据标识;
所述处理器910还用于:当确定所述目标本地缓存设备已缓存所述目标业务数据标识对应的目标业务数据时,向所述数据请求设备发送缓存的所述目标业务数据。
可选的,所述处理器910用于:
向所述目标本地缓存设备发送所述第二业务数据请求;
接收所述目标本地缓存设备在检测到已缓存所述目标业务数据时发送的缓存的所述目标业务数据;
向所述数据请求设备发送缓存的所述目标业务数据。
可选的,所述处理器910还用于:
当确定所述目标本地缓存设备未缓存所述目标业务数据时,所述基站向目标数据服务器发送第三业务数据请求,所述第三业务数据请求携带所述目标业务数据标识,所述第三业务数据请求用于指示所述目标数据服务器向所述数据请求设备发送所述目标业务数据。
可选的,所述处理器910用于:
向所述目标本地缓存设备发送所述第二业务数据请求,所述第二业务数据请求用于指示所述目标本地缓存设备在检测到未缓存所述目标业务数据时,向所述基站发送针对所述目标业务数据的未缓存信息;
接收所述目标本地缓存设备发送的针对所述目标业务数据的未缓存信息确定所述目标本地缓存设备未缓存所述目标业务数据。
在图9所示的实施例中,数据请求设备检测到针对目标数据服务器的第一请求消息后,根据预先接收到基站发送的本地缓存设备列表,确定授权缓存所述目标数据服务器业务数据的目标本地缓存设备,建立与目标本地缓存设备之间的网络连接,从而使数据请求设备可以直接向距离较近的本地缓存设备请求目标业务数据,避免了向目标数据服务器请求数据时造成的传输开销浪费以及较大的传输时延,从而提高数据请求设备请求数据后的响应速度,提升了用户体验。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程,是可以通过计算机程序来指令相关的硬件来完成,所述的程序可存储于一计算机可读取存储介质中,该程序在执行时,可包括如上述各方法的实施例的流程。其中,所述的存储介质可为磁碟、光盘、只读存储记忆体(Read-Only Memory,ROM)或随机存储记忆体(Random Access Memory,RAM)等。
以上所揭露的仅为本发明较佳实施例而已,当然不能以此来限定本发明之权利范围,因此依本发明权利要求所作的等同变化,仍属本发明所涵盖的范围。

Claims (48)

  1. 一种缓存数据请求方法,其特征在于,包括:
    数据请求设备检测到针对目标数据服务器的第一请求消息;
    所述数据请求设备根据预先接收到基站发送的本地缓存设备列表,确定用于缓存所述目标数据服务器业务数据的目标本地缓存设备;
    所述数据请求设备建立与所述目标本地缓存设备之间的网络连接,并通过所述网络连接向所述目标本地缓存设备发送针对所述目标数据服务器的业务数据请求。
  2. 如权利要求1所述的方法,其特征在于,所述数据请求设备建立与所述目标本地缓存设备之间的网络连接之后,所述方法还包括:
    所述数据请求设备检测到目标地址为所述目标数据服务器的第一业务数据请求,所述第一业务数据请求携带目标业务数据标识;
    所述数据请求设备向所述目标本地缓存设备发送第二业务数据请求,所述第二业务数据请求携带所述目标业务数据标识,所述第二业务数据请求用于指示所述目标本地缓存设备在检测到已缓存所述目标业务数据标识对应的目标业务数据时向数据请求设备发送缓存的所述目标业务数据;
    所述数据请求设备接收所述目标本地缓存设备发送的所述目标业务数据。
  3. 如权利要求1所述的方法,其特征在于,所述第一请求消息包括目标业务数据标识,用于请求所述目标业务数据标识对应的目标业务数据;
    所述数据请求设备建立与所述目标本地缓存设备之间的网络连接之后,所述方法还包括:
    所述数据请求设备向所述目标本地缓存设备发送第二业务数据请求,所述第二业务数据请求携带所述目标业务数据标识,所述第二业务数据请求用于指示所述目标本地缓存设备在检测到已缓存所述目标业务数据标识对应的 目标业务数据时向数据请求设备发送缓存的所述目标业务数据;
    所述数据请求设备接收所述目标本地缓存设备发送的所述目标业务数据。
  4. 如权利要求1-3所述的任一方法,其特征在于,所述本地缓存设备列表包括至少一个本地缓存设备的标识;
    所述数据请求设备根据预先获取到的本地缓存设备列表,确定用于缓存所述目标数据服务器业务数据的目标本地缓存设备包括:
    所述数据请求设备判断预先获取到的缓存内容授权列表中是否存在与所述本地缓存设备列表中的本地缓存设备的标识一致的第一标识,所述缓存内容授权列表包括所述目标数据服务器授权缓存的至少一个本地缓存设备的标识;
    若存在所述第一标识,则所述数据请求设备确定所述第一标识对应的本地缓存设备为所述目标本地缓存设备。
  5. 如权利要求4所述的方法,其特征在于,所述数据请求设备判断预先获取到的缓存内容授权列表中是否存在与所述本地缓存设备列表中的至少一个本地缓存设备的标识一致的第一标识之前,所述方法还包括:
    所述数据请求设备接收所述目标数据服务器发送的所述缓存内容授权列表。
  6. 如权利要求4所述的方法,其特征在于,所述本地缓存设备包括所述数据请求设备所属的基站或/和与所述基站连接的至少一个第一缓存设备。
  7. 如权利要求1所述的方法,其特征在于,所述数据请求设备建立与所述目标本地缓存设备之间的网络连接包括:
    所述数据请求设备向所述数据请求设备所属的基站发送所述第二请求消息,所述第二请求消息携带路由信息,所述路由消息用于指示目标本地缓存设备,所述第二请求消息用于指示所述基站建立所述数据请求设备和所述目 标本地缓存设备的连接。
  8. 如权利要求7所述的方法,其特征在于,所述路由信息包括目标本地缓存设备的标识或目标本地缓存设备的索引值。
  9. 如权利要求1-8所述的任一方法,其特征在于,所述数据请求设备检测到目标地址为所述目标数据服务器的第一业务数据请求包括:
    所述数据请求设备接收用户设备发送的目标地址为目标数据服务器的地址的第一业务数据请求。
  10. 一种缓存数据请求方法,其特征在于,包括:
    基站向所述基站管理的数据请求设备发送本地缓存设备列表,所述本地缓存设备列表包括至少一个本地缓存设备的标识,所述本地缓存设备列表被所述数据请求设备用于确定授权缓存所述目标数据服务器业务数据的目标本地缓存设备。
  11. 如权利要求10所述的方法,其特征在于,所述方法还包括:
    所述基站接收所述数据请求设备发送的第二请求消息,所述第二请求消息携带路由信息,所述路由消息用于指示目标本地缓存设备;
    所述基站根据所述第二请求消息建立所述数据请求设备和所述目标本地缓存设备的连接或承载。
  12. 如权利要求11所述的方法,其特征在于,所述根据所述第二请求消息建立所述数据请求设备和所述目标本地缓存设备的连接包括:
    所述基站建立所述基站与所述数据请求设备之间或/和所述基站与所述目标本地缓存设备之间的传输承载,所述传输承载用于传输所述数据请求设备和目标本地缓存设备之间的数据。
  13. 如权利要求10所述的方法,其特征在于,所述方法还包括:
    所述基站接收所述数据请求设备与所述目标本地缓存设备之间建立网络连接后发送的针对目标本地缓存设备的第二业务数据请求,所述第二业务数据请求携带目标业务数据标识;
    当确定所述目标本地缓存设备已缓存所述目标业务数据标识对应的目标业务数据时,所述基站向所述数据请求设备发送缓存的所述目标业务数据。
  14. 如权利要求13所述的方法,其特征在于,所述当确定所述目标本地缓存设备已缓存所述目标业务数据请求所请求的目标业务数据时,所述基站向所述数据请求设备发送缓存的所述目标业务数据,包括:
    所述基站向所述目标本地缓存设备发送所述第二业务数据请求;
    所述基站接收所述目标本地缓存设备在检测到已缓存所述目标业务数据时发送的缓存的所述目标业务数据;
    所述基站向所述数据请求设备发送缓存的所述目标业务数据。
  15. 如权利要求13所述的方法,其特征在于,所述基站接收所述数据请求设备与所述目标本地缓存设备之间建立网络连接后发送的针对目标本地缓存设备的第二业务数据请求之后,所述方法还包括:
    当确定所述目标本地缓存设备未缓存所述目标业务数据时,所述基站向目标数据服务器发送第三业务数据请求,所述第三业务数据请求携带所述目标业务数据标识,所述第三业务数据请求用于指示所述目标数据服务器向所述数据请求设备发送所述目标业务数据。
  16. 如权利要求15所述的方法,其特征在于,所述确定所述目标本地缓存设备未缓存所述目标业务数据包括:
    所述基站向所述目标本地缓存设备发送所述第二业务数据请求,所述第二业务数据请求用于指示所述目标本地缓存设备在检测到未缓存所述目标业务数据时,向所述基站发送针对所述目标业务数据的未缓存信息;
    所述基站接收所述目标本地缓存设备发送的针对所述目标业务数据的未缓存信息确定所述目标本地缓存设备未缓存所述目标业务数据。
  17. 一种数据请求设备,其特征在于,包括:
    处理模块,用于检测到针对目标数据服务器的第一请求消息;根据预先接收到基站发送的本地缓存设备列表,确定用于缓存所述目标数据服务器业务数据的目标本地缓存设备;建立与所述目标本地缓存设备之间的网络连接;
    发送模块,用于通过所述网络连接向所述目标本地缓存设备发送针对所述目标数据服务器的业务数据请求。
  18. 如权利要求17所述的设备,其特征在于,
    所述处理模块还用于:检测到目标地址为所述目标数据服务器的第一业务数据请求,所述第一业务数据请求携带目标业务数据标识;
    所述发送模块还用于:向所述目标本地缓存设备发送第二业务数据请求,所述第二业务数据请求携带所述目标业务数据标识,所述第二业务数据请求用于指示所述目标本地缓存设备在检测到已缓存所述目标业务数据标识对应的目标业务数据时向数据请求设备发送缓存的所述目标业务数据;
    所述设备还包括:
    接收模块,用于接收所述目标本地缓存设备发送的所述目标业务数据。
  19. 如权利要求17所述的设备,其特征在于,所述第一请求消息包括目标业务数据标识,用于请求所述目标业务数据标识对应的目标业务数据;
    所述发送模块还用于:向所述目标本地缓存设备发送第二业务数据请求,所述第二业务数据请求携带所述目标业务数据标识,所述第二业务数据请求用于指示所述目标本地缓存设备在检测到已缓存所述目标业务数据标识对应的目标业务数据时向数据请求设备发送缓存的所述目标业务数据;
    所述设备还包括:
    接收模块,用于接收所述目标本地缓存设备发送的所述目标业务数据。
  20. 如权利要求17-19所述的任一设备,其特征在于,所述本地缓存设备列表包括至少一个本地缓存设备的标识;
    所述处理模块用于:
    判断预先获取到的缓存内容授权列表中是否存在与所述本地缓存设备列表中的本地缓存设备的标识一致的第一标识,所述缓存内容授权列表包括所述目标数据服务器授权缓存的至少一个本地缓存设备的标识;
    若存在所述第一标识,则确定所述第一标识对应的本地缓存设备为所述目标本地缓存设备。
  21. 如权利要求20所述的设备,其特征在于,所述接收模块还用于:
    接收所述目标数据服务器发送的所述缓存内容授权列表。
  22. 如权利要求20所述的设备,其特征在于,所述本地缓存设备包括所述数据请求设备所属的基站或/和与所述基站连接的至少一个第一缓存设备。
  23. 如权利要求17所述的设备,其特征在于,所述处理模块用于:
    向所述数据请求设备所属的基站发送所述第二请求消息,所述第二请求消息携带路由信息,所述路由消息用于指示目标本地缓存设备,所述第二请求消息用于指示所述基站建立所述数据请求设备和所述目标本地缓存设备的连接或承载。
  24. 如权利要求23所述的设备,其特征在于,所述路由信息包括目标本地缓存设备的标识或目标本地缓存设备的索引值。
  25. 如权利要求17-24所述的任一设备,其特征在于,所述处理模块用于:
    接收用户设备发送的目标地址为目标数据服务器的地址的第一业务数据请求。
  26. 一种基站,其特征在于,包括:
    处理模块,用于获取本地缓存设备列表,所述本地缓存设备列表包括至 少一个本地缓存设备的标识;
    发送模块,用于向所述基站管理的数据请求设备发送所述本地缓存设备列表,所述本地缓存设备列表被所述数据请求设备用于确定用于缓存所述目标数据服务器业务数据的目标本地缓存设备。
  27. 如权利要求26所述的基站,其特征在于,所述基站还包括:
    接收模块,用于接收所述数据请求设备发送的第二请求消息,所述第二请求消息携带路由信息,所述路由消息用于指示目标本地缓存设备;
    所述处理模块还用于:根据所述第二请求消息建立所述数据请求设备和所述目标本地缓存设备的连接或承载。
  28. 如权利要求27所述的基站,其特征在于,所述处理模块用于:
    建立所述基站与所述数据请求设备之间或/和所述基站与所述目标本地缓存设备之间的传输承载,所述传输承载用于传输所述数据请求设备和目标本地缓存设备之间的数据。
  29. 如权利要求26所述的基站,其特征在于,所述基站还包括:
    接收模块,用于接收所述数据请求设备与所述目标本地缓存设备之间建立网络连接后发送的针对目标本地缓存设备的第二业务数据请求,所述第二业务数据请求携带目标业务数据标识;
    所述处理模块还用于:当确定所述目标本地缓存设备已缓存所述目标业务数据标识对应的目标业务数据时,向所述数据请求设备发送缓存的所述目标业务数据。
  30. 如权利要求29所述的基站,其特征在于,所述处理模块用于:
    向所述目标本地缓存设备发送所述第二业务数据请求;
    接收所述目标本地缓存设备在检测到已缓存所述目标业务数据时发送的缓存的所述目标业务数据;
    向所述数据请求设备发送缓存的所述目标业务数据。
  31. 如权利要求29所述的基站,其特征在于,所述处理模块还用于:
    当确定所述目标本地缓存设备未缓存所述目标业务数据时,所述基站向目标数据服务器发送第三业务数据请求,所述第三业务数据请求携带所述目标业务数据标识,所述第三业务数据请求用于指示所述目标数据服务器向所述数据请求设备发送所述目标业务数据。
  32. 如权利要求31所述的基站,其特征在于,所述处理模块用于:
    向所述目标本地缓存设备发送所述第二业务数据请求,所述第二业务数据请求用于指示所述目标本地缓存设备在检测到未缓存所述目标业务数据时,向所述基站发送针对所述目标业务数据的未缓存信息;
    接收所述目标本地缓存设备发送的针对所述目标业务数据的未缓存信息确定所述目标本地缓存设备未缓存所述目标业务数据。
  33. 一种数据请求设备,其特征在于,包括:
    处理器,用于检测到针对目标数据服务器的第一请求消息;根据预先接收到基站发送的本地缓存设备列表,确定用于缓存所述目标数据服务器业务数据的目标本地缓存设备;建立与所述目标本地缓存设备之间的网络连接;
    发送器,用于通过所述网络连接向所述目标本地缓存设备发送针对所述目标数据服务器的业务数据请求。
  34. 如权利要求33所述的设备,其特征在于,
    所述处理器还用于:检测到目标地址为所述目标数据服务器的第一业务数据请求,所述第一业务数据请求携带目标业务数据标识;
    所述发送器还用于:向所述目标本地缓存设备发送第二业务数据请求,所述第二业务数据请求携带所述目标业务数据标识,所述第二业务数据请求用于指示所述目标本地缓存设备在检测到已缓存所述目标业务数据标识对应的目标业务数据时向数据请求设备发送缓存的所述目标业务数据;
    所述设备还包括:
    接收器,用于接收所述目标本地缓存设备发送的所述目标业务数据。
  35. 如权利要求33所述的设备,其特征在于,所述第一请求消息包括目标业务数据标识,用于请求所述目标业务数据标识对应的目标业务数据;
    所述发送器还用于:向所述目标本地缓存设备发送第二业务数据请求,所述第二业务数据请求携带所述目标业务数据标识,所述第二业务数据请求用于指示所述目标本地缓存设备在检测到已缓存所述目标业务数据标识对应的目标业务数据时向数据请求设备发送缓存的所述目标业务数据;
    所述设备还包括:
    接收器,用于接收所述目标本地缓存设备发送的所述目标业务数据。
  36. 如权利要求33-35所述的任一设备,其特征在于,所述本地缓存设备列表包括至少一个本地缓存设备的标识;
    所述处理器用于:
    判断预先获取到的缓存内容授权列表中是否存在与所述本地缓存设备列表中的本地缓存设备的标识一致的第一标识,所述缓存内容授权列表包括所述目标数据服务器授权缓存的至少一个本地缓存设备的标识;
    若存在所述第一标识,则确定所述第一标识对应的本地缓存设备为所述目标本地缓存设备。
  37. 如权利要求36所述的设备,其特征在于,所述接收器还用于:
    接收所述目标数据服务器发送的所述缓存内容授权列表。
  38. 如权利要求36所述的设备,其特征在于,所述本地缓存设备包括所述数据请求设备所属的基站或/和与所述基站连接的至少一个第一缓存设备。
  39. 如权利要求33所述的设备,其特征在于,所述处理器用于:
    向所述数据请求设备所属的基站发送所述第二请求消息,所述第二请求消息携带路由信息,所述路由消息用于指示目标本地缓存设备,所述第二请 求消息用于指示所述基站建立所述数据请求设备和所述目标本地缓存设备的连接或承载。
  40. 如权利要求39所述的设备,其特征在于,所述路由信息包括目标本地缓存设备的标识或目标本地缓存设备的索引值。
  41. 如权利要求33-40所述的任一设备,其特征在于,所述处理器用于:
    接收用户设备发送的目标地址为目标数据服务器的地址的第一业务数据请求。
  42. 一种基站,其特征在于,包括:
    处理器,用于获取本地缓存设备列表,所述本地缓存设备列表包括至少一个本地缓存设备的标识;
    发送器,用于向所述基站管理的数据请求设备发送所述本地缓存设备列表,所述本地缓存设备列表被所述数据请求设备用于确定用于缓存所述目标数据服务器业务数据的目标本地缓存设备。
  43. 如权利要求42所述的基站,其特征在于,所述基站还包括:
    接收器,用于接收所述数据请求设备发送的第二请求消息,所述第二请求消息携带路由信息,所述路由消息用于指示目标本地缓存设备;
    所述处理器还用于:根据所述第二请求消息建立所述数据请求设备和所述目标本地缓存设备的连接或承载。
  44. 如权利要求43所述的基站,其特征在于,所述处理器用于:
    建立所述基站与所述数据请求设备之间或/和所述基站与所述目标本地缓存设备之间的传输承载,所述传输承载用于传输所述数据请求设备和目标本地缓存设备之间的数据。
  45. 如权利要求42所述的基站,其特征在于,所述基站还包括:
    接收器,用于接收所述数据请求设备与所述目标本地缓存设备之间建立网络连接后发送的针对目标本地缓存设备的第二业务数据请求,所述第二业务数据请求携带目标业务数据标识;
    所述处理器还用于:当确定所述目标本地缓存设备已缓存所述目标业务数据标识对应的目标业务数据时,向所述数据请求设备发送缓存的所述目标业务数据。
  46. 如权利要求45所述的基站,其特征在于,所述处理器用于:
    向所述目标本地缓存设备发送所述第二业务数据请求;
    接收所述目标本地缓存设备在检测到已缓存所述目标业务数据时发送的缓存的所述目标业务数据;
    向所述数据请求设备发送缓存的所述目标业务数据。
  47. 如权利要求45所述的基站,其特征在于,所述处理器还用于:
    当确定所述目标本地缓存设备未缓存所述目标业务数据时,所述基站向目标数据服务器发送第三业务数据请求,所述第三业务数据请求携带所述目标业务数据标识,所述第三业务数据请求用于指示所述目标数据服务器向所述数据请求设备发送所述目标业务数据。
  48. 如权利要求47所述的基站,其特征在于,所述处理器用于:
    向所述目标本地缓存设备发送所述第二业务数据请求,所述第二业务数据请求用于指示所述目标本地缓存设备在检测到未缓存所述目标业务数据时,向所述基站发送针对所述目标业务数据的未缓存信息;
    接收所述目标本地缓存设备发送的针对所述目标业务数据的未缓存信息确定所述目标本地缓存设备未缓存所述目标业务数据。
PCT/CN2016/106446 2016-11-18 2016-11-18 一种缓存数据请求方法及相关设备 WO2018090335A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP16921782.5A EP3534590B1 (en) 2016-11-18 2016-11-18 Cache data requesting method and related device
PCT/CN2016/106446 WO2018090335A1 (zh) 2016-11-18 2016-11-18 一种缓存数据请求方法及相关设备
CN201680086229.9A CN109196843B (zh) 2016-11-18 2016-11-18 一种缓存数据请求方法及相关设备
US16/412,821 US11252251B2 (en) 2016-11-18 2019-05-15 Cache data request method and related device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/106446 WO2018090335A1 (zh) 2016-11-18 2016-11-18 一种缓存数据请求方法及相关设备

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/412,821 Continuation US11252251B2 (en) 2016-11-18 2019-05-15 Cache data request method and related device

Publications (1)

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

Family

ID=62145186

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/106446 WO2018090335A1 (zh) 2016-11-18 2016-11-18 一种缓存数据请求方法及相关设备

Country Status (4)

Country Link
US (1) US11252251B2 (zh)
EP (1) EP3534590B1 (zh)
CN (1) CN109196843B (zh)
WO (1) WO2018090335A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114979283A (zh) * 2021-04-27 2022-08-30 中移互联网有限公司 数据获取方法、装置、电子设备及存储介质

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112532673B (zh) * 2019-09-19 2023-12-05 北京京东振世信息技术有限公司 消息发送方法及装置、计算机可读存储介质、电子设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080086574A1 (en) * 2006-10-05 2008-04-10 Limelight Networks, Inc. Remote Domain Name Service
CN102143199A (zh) * 2010-10-19 2011-08-03 华为技术有限公司 获取内容的方法、节点及内容网络
US20140040346A1 (en) * 2012-07-31 2014-02-06 Apple Inc. Delivering content to electronic devices using local caching servers
CN103703747A (zh) * 2013-08-13 2014-04-02 华为技术有限公司 互联网内容存储方法和设备

Family Cites Families (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8369328B2 (en) * 2009-07-14 2013-02-05 Saguna Networks Ltd. System and method for efficient delivery of multi-unicast communication traffic
GB2486126B (en) * 2009-09-21 2014-01-08 Ericsson Telefon Ab L M Caching in mobile networks
US8843160B2 (en) * 2010-12-23 2014-09-23 International Business Machines Corporation Location based wireless tower caching
US8767728B2 (en) * 2011-03-01 2014-07-01 Telefonaktiebolaget Lm Ericsson (Publ) Tunnel gateway managed caching architecture
KR101899002B1 (ko) * 2011-03-23 2018-09-17 삼성전자 주식회사 무선 통신 시스템 및 그 무선 통신 시스템에서 컨텐츠 전송 방법
CN102904859B (zh) * 2011-07-26 2017-08-08 中兴通讯股份有限公司 保障流媒体业务服务质量的方法及系统
GB2494472A (en) * 2011-09-12 2013-03-13 Intellectual Ventures Holding 81 Llc Caching of content in a mobile communications network
CN103430516B (zh) * 2013-02-21 2017-02-22 华为技术有限公司 业务提供系统、方法、移动边缘应用服务器及支持节点
US9036635B2 (en) * 2013-03-12 2015-05-19 Motorola Solutions, Inc. Method and apparatus for propagating public safety multicast and broadcast services among public safety personnel
CN104125609B (zh) * 2013-04-28 2018-04-06 国际商业机器公司 家庭基站系统及其数据访问处理方法
US10085185B2 (en) * 2014-01-08 2018-09-25 Vodafone Ip Licensing Limited Telecommunications network with optimisation of content delivery
JP6432598B2 (ja) * 2014-04-30 2018-12-05 ソニー株式会社 クライアント装置、サーバ、記録媒体および情報処理方法
CN104092776A (zh) * 2014-07-25 2014-10-08 北京赛科世纪数码科技有限公司 一种信息存取方法和系统
CN104168317B (zh) * 2014-08-12 2018-01-19 华为技术有限公司 缓存内容命中方法和通信系统
CN105791392A (zh) * 2016-02-16 2016-07-20 中国科学院信息工程研究所 基于移动网络的边缘服务通信方法及系统
WO2018090336A1 (zh) 2016-11-18 2018-05-24 华为技术有限公司 缓存数据获取方法、相关设备以及通信系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080086574A1 (en) * 2006-10-05 2008-04-10 Limelight Networks, Inc. Remote Domain Name Service
CN102143199A (zh) * 2010-10-19 2011-08-03 华为技术有限公司 获取内容的方法、节点及内容网络
US20140040346A1 (en) * 2012-07-31 2014-02-06 Apple Inc. Delivering content to electronic devices using local caching servers
CN103703747A (zh) * 2013-08-13 2014-04-02 华为技术有限公司 互联网内容存储方法和设备

Non-Patent Citations (1)

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

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114979283A (zh) * 2021-04-27 2022-08-30 中移互联网有限公司 数据获取方法、装置、电子设备及存储介质

Also Published As

Publication number Publication date
EP3534590A4 (en) 2019-11-20
CN109196843A (zh) 2019-01-11
EP3534590B1 (en) 2022-09-28
CN109196843B (zh) 2021-07-09
US20190268434A1 (en) 2019-08-29
US11252251B2 (en) 2022-02-15
EP3534590A1 (en) 2019-09-04

Similar Documents

Publication Publication Date Title
WO2020207490A1 (en) System, apparatus and method to support data server selection
EP3429260B1 (en) Data transmission method and system
WO2021042398A1 (zh) 一种通信方法及装置、网络设备、终端设备
US9516625B2 (en) Methods and apparatuses for communicating content data to a communications terminal from a local data store
EP2690818B1 (en) Wireless communication system and method for transmitting content in wireless communication system
WO2018090336A1 (zh) 缓存数据获取方法、相关设备以及通信系统
US9585052B2 (en) Determining a traffic bearer for data traffic between a terminal and a content data source of a content data network
US20140310339A1 (en) Content delivery method and apparatus, and access network device
WO2019196000A1 (en) Methods and system for carrying out small data fast path communication
EP2756652A1 (en) Communications terminal and method
WO2019105286A1 (zh) 卫星网络通信方法、代理服务装置及网关
US11252251B2 (en) Cache data request method and related device
WO2012171315A1 (zh) 一种无线网络控制器分组域内容缓存系统及其实现方法
JP5726302B2 (ja) トポロジサーバを用いた、通信アーキテクチャにわたって分散されたノードのネットワークに対する秘密または保護されたアクセス
EP2903225B1 (en) Bit-rate control for access to content stored in local delivery devices of a content-delivery network
CN107343014B (zh) 基于内容分发网络的业务分流方法和远程网关
CN105682087B (zh) 业务路由方法及基站
US11240338B2 (en) Integrated content delivery of enhanced mobile gateway system
WO2023213215A1 (zh) 一种通信方法及装置
US20230025344A1 (en) Application Discovery Method, Apparatus, and System, and Computer Storage Medium
CN116915595A (zh) 一种业务处理方法和系统
GB2494470A (en) Caching of content in a mobile communications network
WO2015028057A1 (en) Packet processing in communications
CN117336791A (zh) 一种实现本地业务流量分流的方法、模块及系统
CN111417152A (zh) 一种数据的分流方法及装置、计算机可读存储介质

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16921782

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

Country of ref document: EP

Effective date: 20190528