WO2017097027A1 - 基于因特网内容适配协议的数据处理方法、装置和系统 - Google Patents

基于因特网内容适配协议的数据处理方法、装置和系统 Download PDF

Info

Publication number
WO2017097027A1
WO2017097027A1 PCT/CN2016/101587 CN2016101587W WO2017097027A1 WO 2017097027 A1 WO2017097027 A1 WO 2017097027A1 CN 2016101587 W CN2016101587 W CN 2016101587W WO 2017097027 A1 WO2017097027 A1 WO 2017097027A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
cache
response
icap
request
Prior art date
Application number
PCT/CN2016/101587
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 中兴通讯股份有限公司
Publication of WO2017097027A1 publication Critical patent/WO2017097027A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services

Definitions

  • the embodiments of the present invention relate to the field of communications, and in particular, to a data processing method, apparatus, and system based on an Internet content adaptation protocol.
  • ICAP Internet Content Adaptation Protocol
  • the purpose of the Internet Content Adaptation Protocol is to enable Web content devices to interoperate, share data and control information, enabling users to implement certain services on separate devices and optimize the functions performed.
  • ICAP is a lightweight HTTP (HyperText Transfer Protocol)-based remote procedure call protocol.
  • the device can transfer HTTP-based content to the ICAP server for content operations.
  • the ICAP server load may increase in processing time, and the ICAP request and response message may stay longer in the network, both of which may occur. Lead to the slow delivery of ICAP business services.
  • a data processing method based on an Internet content adaptation protocol comprising:
  • the service data is saved in a local cache according to the cache data response description field.
  • the step of transmitting a data cache request to an ICAP server Previously it also included:
  • the option query request including a client cache data support field, such that the ICAP server returns an option query response according to the client cache data support field, the option query response including server cache data Capability field.
  • the data cache request is a customized data cache request message or a request message multiplexed with an ICAP protocol
  • the cache response is a customized cache response message or a response message multiplexed with an ICAP protocol
  • the data The cache request is the same as the message type of the cache response.
  • the cache data description field includes a service data request record number field and a service data index field
  • the cache data response description field includes a service data response record number field
  • the cache data response description field further includes a service data end flag field
  • the step of saving the service data in the local cache according to the cache data response description field further includes:
  • the service data end flag field is a continuation data cache, the data cache request is continued to be sent to the ICAP server.
  • the method further includes:
  • the local cache is searched for the service data matched by the ICAP service query request and used directly.
  • a data processing apparatus based on an Internet content adaptation protocol comprising:
  • a data cache request sending module configured to send a data cache request to an Internet content adaptation protocol ICAP server, where the data cache request includes a cache data description field, so that the ICAP server returns a corresponding cache response according to the data cache request,
  • the cache response includes a cache data response description field and service data;
  • the cache module is configured to save the service data in a local cache according to the cache data response description field.
  • the data processing method and apparatus based on the Internet content adaptation protocol, by sending a data cache request to an Internet content adaptation protocol ICAP server, the data cache request includes a cache data description field, so that the ICAP server returns a corresponding cache response according to the data cache request.
  • the cache response includes a cached data response description field and service data, and the service data is saved in the local cache according to the cache data response description field. Since the service data in the local cache has been pre-stored, it can be cached locally when there is an ICAP service query. Find matching business data, if there is a match, it can be used directly, which speeds up the acquisition of business data and improves the speed of business response.
  • a data processing method based on an Internet content adaptation protocol comprising:
  • the business data is saved in a local cache.
  • the method before the step of receiving the data cache request sent by the ICAP client, the method further includes:
  • the option query request includes a client cache data support field, and returning an option query response according to the client cache data support field, where the option query response includes a server cache data capability field.
  • the data cache request is a customized data cache request message or a request message multiplexed with an ICAP protocol
  • the cache response is a customized cache response message or a response message multiplexed with an ICAP protocol
  • the data The cache request is the same as the message type of the cache response.
  • the cache data description field includes a service data request record number field and a service data index field
  • the cache data response description field includes a service data response record number field
  • the cache data response description field further includes a service data knot.
  • the bundle flag field the method further comprising:
  • the service data end flag field is the continuation data cache, otherwise the service data end flag field is the end data cache.
  • a data processing apparatus based on an Internet content adaptation protocol comprising:
  • a receiving module configured to receive a data cache request sent by an Internet Content Adaptation Protocol ICAP client, where the data cache request includes a cache data description field;
  • the response module is configured to obtain corresponding service data according to the data cache request, and return a corresponding cache response, where the cache response includes a cache data response description field and the service data, so that the ICAP client is configured according to the cache
  • the data response description field saves the business data in a local cache.
  • the data processing method and device based on the Internet content adaptation protocol receive a data cache request sent by an Internet Content Adaptation Protocol ICAP client, where the data cache request includes a cache data description field, and the corresponding service data is obtained according to the data cache request, and returned.
  • the cache response includes a cache data response description field and the service data, so that the ICAP client saves the service data in the local cache according to the cached data response description field, and the service data in the local cache is used for the ICAP client
  • the ICAP service query is performed, the service is preferentially searched and used, and the service data to be cached is returned according to the data cache request sent by the ICAP client, so that the ICAP client caches the received service data for the ICAP service query.
  • Priority search and use because the ICAP server has pre-stored the business data to the ICAP client in advance, if there is a match, it can be used directly, which speeds up the acquisition of business data and improves the speed of business response.
  • a data processing system based on an Internet content adaptation protocol comprising:
  • An ICAP client configured to send a data cache request to an Internet Content Adaptation Protocol ICAP server, the data cache request including a cache data description field;
  • the ICAP server is configured to receive a data cache request sent by the ICAP client, obtain corresponding service data according to the data cache request, and return a corresponding cache response, where the cache The response includes a cache data response description field and the service data;
  • the ICAP client is further configured to save the service data in a local cache according to the cached data response description field.
  • a computer storage medium is further provided, and the computer storage medium may store an execution instruction for executing the data processing method based on the Internet content adaptation protocol in the foregoing embodiment.
  • the ICAP server can return the corresponding service data to be cached according to the data cache request sent by the ICAP client, so that the ICAP The client caches the received service data and uses it for priority search and use when the ICAP service is queried. Since the ICAP server has previously sent the service data to the ICAP client for pre-storage, if there is a match, it can be used directly, which speeds up. The speed of acquisition of business data increases the speed of business response.
  • FIG. 1 is an application environment diagram of a data processing method based on an Internet content adaptation protocol in an embodiment
  • FIG. 2 is a flow chart of a data processing method based on an Internet content adaptation protocol in an embodiment
  • FIG. 3 is a flow chart of a data processing method based on an Internet content adaptation protocol in another embodiment
  • FIG. 4 is a flow chart of another data processing method based on an Internet content adaptation protocol in an embodiment
  • FIG. 5 is a structural block diagram of a data processing apparatus based on an Internet content adaptation protocol in an embodiment
  • FIG. 6 is a data processing apparatus based on an Internet content adaptation protocol in another embodiment. Structure diagram
  • FIG. 7 is a structural block diagram of a data processing apparatus based on an Internet content adaptation protocol in still another embodiment
  • FIG. 8 is a structural block diagram of another data processing apparatus based on an Internet content adaptation protocol in an embodiment
  • FIG. 9 is a structural block diagram of another data processing apparatus based on an Internet content adaptation protocol in another embodiment.
  • FIG. 10 is a structural block diagram of a data processing system based on an Internet content adaptation protocol in an embodiment.
  • FIG. 1 is an application environment diagram of a data processing method based on an Internet content adaptation protocol in an embodiment.
  • the application environment includes an ICAP client 110 and an ICAP server 120, wherein the ICAP client 110 and the ICAP server 120 communicate over a network.
  • the ICAP client 110 is a PC that supports the ICAP protocol software, and is a carrier-class network node device that implements the ICAP protocol, but is not limited thereto.
  • the ICAP client 110 obtains related resources for business processing by transmitting a related request message to the ICAP server 120.
  • the ICAP server 120 may be a server supporting the ICAP protocol, a PC, a terminal, a commercial server supporting the ICAP protocol software, or a carrier-class network node device implementing the ICAP protocol, but is not limited thereto. After performing the related service processing on the ICAP protocol message sent by the ICAP client 110, the ICAP server 120 returns a response message to the ICAP client 110, and carries the relevant resources required by the ICAP client 110.
  • a data processing method based on an Internet content adaptation protocol is provided, which is applied to an ICAP client in the application environment, and includes the following steps:
  • Step S210 sending a data cache request to an Internet Content Adaptation Protocol ICAP server,
  • the data cache request includes a cache data description field, so that the ICAP server returns a corresponding cache response according to the data cache request, and the cache response includes a cache data response description field and service data.
  • the ICAP client has a data cache function switch, which can receive the function switch function or the signal open data cache function.
  • the data cache function When the data cache function is enabled, if the preset condition is met, the data cache request is sent to the ICAP server.
  • the preset condition can be customized according to requirements, such as a startable data cache control timer, and when the preset timing time arrives, the data cache request is automatically sent to the ICAP server. It can also detect the current network status and send a data cache request according to the current network status. If the network is smooth, send a data cache request, cache the service data, and use the cached service data when the network is congested.
  • the data cache request may also be sent according to the trigger of the user, such as setting a virtual button to receive a signal that the user sends a data cache request.
  • the cache data description field is used to describe the service data that needs to be delivered by the ICAP server, so that the ICAP server obtains the service data to be delivered according to the cache data description field, and the content of the cache data description field can be customized according to requirements, such as the cache data description field. It may include the name of the business data, the starting and ending positions of the business data, the number of records of the business data, and the like.
  • the cache response includes the cached data response description field and the service data.
  • the cache data response description field is used to describe the status of the cache response and the service data, and can be customized according to requirements.
  • the cache data response description field includes a service data end flag field, indicating whether the cache data is sent or not, and whether the cache needs to be continuously sent. data.
  • the cached data response description field may also include the number of times the business data continues to be acquired, and the like.
  • the cache data response description field may further include a length field describing the service data, so that the ICAP client can cache the service data according to the cache data response description field. It can be understood that, before the service data is delivered, the service data may be sorted according to preset conditions, such as sorting the service data according to the query heat to generate a service data record set.
  • the cache data description field, the cache data response description field, and the service data may be stored in an extended field, such as an extended field X-Record-Set of the cache response for storing the business data record.
  • Step S220 Save the service data in the local cache according to the cache data response description field.
  • the cache corresponding to the service data may be opened according to the cache data response description field, and the service data is saved in the local cache. It can also judge whether it is still based on the cache data response description field. Need to interact with the ICAP server to continue to obtain business data and the number of times to continue to obtain business data.
  • the service data matching the ICAP service query request may be preferentially obtained in the locally cached service data according to the ICAP service query request, and the service data in the local cache is pre-stored, if there is a match. It can be used directly, speeding up the acquisition of business data and improving the speed of business response.
  • the generation policy of the data cache request and the update of the service data in the local cache may be updated according to the matching usage of the service data in the local cache, thereby improving the utilization of the service data in the local cache and saving the space of the local cache. For example, the business data in the local cache that is not used for a long time can be deleted.
  • the data cache request includes a cache data description field, so that the ICAP server returns a corresponding cache response according to the data cache request, and the cache response includes a cache data response description field.
  • the service data according to the cache data response description field, the service data is saved in the local cache. Since the service data in the local cache has been pre-stored, when there is an ICAP service query, the matching service data can be found in the local cache, if any The matching can be used directly, which speeds up the acquisition of business data and improves the speed of business response.
  • a data processing method based on an Internet content adaptation protocol including the following steps:
  • Step S310 sending an option query request to the ICAP server, where the option query request includes a client cache data support field, so that the ICAP server returns an option query response according to the client cache data support field, and the option query response includes a server cache data capability field.
  • the option query request is sent to the ICAP server, where the client cache data support field is carried, for example, the client cache data support field is an extended field X-Cache-Capability, and the value is 1, indicating that the ICAP client supports the cache cache function or The value is as long as the extension field X-Cache-Capability exists to indicate that the Cache cache function is supported.
  • the option query request message is a request message for multiplexing the ICAP protocol, as long as the required extension field is added in the preset position of the ICAP protocol related request message.
  • the ICAP server receives an option After the query request, the option query request carries the client cache data support field, such as the extended field X-Cache-Capability field, and the option query response returned to the ICAP client carries the server cache data capability field, such as the server cache data.
  • the capability field is the extension field Y-Cache-Capability, which indicates whether the ICAP server supports the Cache cache function. If the value is 1 for support, 0 indicates that it is not supported.
  • the option query response message is a response message related to the multiplexing of the ICAP protocol, as long as the required extension field is added in the preset position of the response message related to the ICAP protocol.
  • step S320 it is determined whether the server cache data capability field is the ICAP server support data cache. If yes, the process proceeds to step S330, otherwise no processing is performed.
  • the ICAP client receives the option query response, and determines whether the server cache data capability field carried in the option query response, such as whether the extended field Y-Cache-Capability is supported, and if the extended field value is 1, it indicates support, then enter Step S330 performs transmission of the data cache request. If the ICAP server does not support data caching, no processing is done and a data caching request cannot be sent to the ICAP server. Before the data cache request is sent, whether the ICAP server supports the data cache query can prevent the ICAP server from sending data cache request to the ICAP server to cause interference to the ICAP server when the data cache is not supported.
  • Step S330 Send a data cache request to the ICAP server, where the data cache request includes a cached description field, so that the ICAP server returns a corresponding cache response according to the data cache request, where the cache response includes a cached data response description field and service data.
  • Step S340 saving the service data in the local cache according to the cache data response description field.
  • the data cache request is a customized data cache request message or a request message for multiplexing the ICAP protocol
  • the cache response is a customized cache response message or a response message for multiplexing the ICAP protocol, a data cache request and a cache response message.
  • the type is the same.
  • the customized data cache request or the cache response message is in a plain text format, and the specific format may be customized as long as the format conforms to the relevant ICAP protocol.
  • the data cache request or the cache response may also be a request message for multiplexing the ICAP protocol, as long as the required extension field is added at a preset location of the ICAP protocol related request message.
  • Data cache request and cache response The message types are the same. For example, if the data cache request is customized, the cache response is also customized.
  • the data cache request is consistent with the message type of the cache response, which facilitates quick resolution between messages.
  • the cache data description field includes a service data request record number field and a service data index field
  • the cache data response description field includes a service data response record number field
  • the service data request record number field is used to describe the number of records of the service data that needs to be delivered by the current request.
  • the data cache request carries the extended field X-Record-Number, so that the current request needs to be delivered by the ICAP server.
  • the service data index field is used to describe the starting position of the service data delivered by the ICAP server, such as the data cache request carrying the extended field X-Record-Index to guide the ICAP server to specify the location from the service data record set. Business data records are issued.
  • the service data index field is used to find the starting location of the service data delivery, and then the service data of the same length as the service data described in the service data request record field is found from the start location, and the target service data delivered by the request is obtained.
  • the service data response record number field is used to describe the number of records of the service data actually delivered by the current ICAP server. The number of records of the service data actually delivered is less than or equal to the number of records of the service data that needs to be delivered this time.
  • the ICAP client can open a corresponding local cache space according to the service data response record field to cache the business data.
  • the cache response carries an extension field X-Record-Number, indicating a service data response record number field.
  • the service data request record field and the service data index field can be used to quickly obtain the target service data, and the service data response record field can quickly determine the size of the local cache.
  • the cache data response description field further includes a service data end flag field,
  • step S220 the method further includes: if the service data end flag field is the continuation data cache, continuing to send the data cache request to the ICAP server.
  • the service data end flag field is used to describe whether the data cache request is completed.
  • the cache response carries the extended field X-Record-Isover, and according to the extended field X-Record-Isover in the cache response, whether to continue with
  • the ICAP server interacts to request service data records. For example, an X-Record-Isover value of 1 indicates that interaction needs to be continued, and an X-Record-Isover value of 0 indicates that it is not required.
  • the service data end flag field is continued data buffer, that is, X-Record - If the value of Isover is 1, the data is sent to the ICAP server. Save the request and continue to obtain the service data that needs to be cached. Otherwise, the cached service data is obtained.
  • the service data end flag field can be used to divide the service data that needs to be cached into multiple times, so that the data transmission adapts to the real-time situation of the network, and the flexibility of the service data transmission is improved.
  • the method further includes: receiving an ICAP service query request, and locally searching for service data matched by the ICAP service query request and directly using the service data.
  • the service data matching the ICAP service query request is preferentially obtained in the locally cached service data. Since the service data in the local cache is pre-stored, if there is a match, the Use, speed up the acquisition of business data, and improve the speed of business response. If no matching service data is found, the service request message is sent to the ICAP server, and the matched service data is obtained from the ICAP server.
  • a data processing method based on an Internet content adaptation protocol is provided, which is applied to an ICAP server in the application environment, and includes the following steps:
  • Step S410 receiving a data cache request sent by an Internet Content Adaptation Protocol ICAP client, where the data cache request includes a cache data description field.
  • the cache data description field is used to describe the service data that needs to be sent by the ICAP server, and the ICAP server can obtain the service data that needs to be delivered according to the cache data description field, and the content of the cache data description field can be customized according to requirements, such as cache data.
  • the description field may include the name of the business data, the starting position and ending position of the business data, the number of records of the business data, and the like.
  • Step S420 Acquire corresponding service data according to the data cache request, and return a corresponding cache response, where the cache response includes a cache data response description field and service data, so that the ICAP client saves the service data locally according to the cache data response description field. Cache.
  • the cache response includes the cached data response description field and the service data.
  • the cache data response description field is used to describe the status of the cache response and the service data, and can be customized according to requirements.
  • the cache data response description field includes a service data end flag field, indicating whether the cache data is sent or not, and whether the cache needs to be continuously sent. data.
  • Cache data response The description field may also include the number of times the business data continues to be acquired, and the like.
  • the cache data response description field may further include a length field describing the service data, so that the ICAP client can cache the service data according to the cache data response description field.
  • the service data may be sorted according to preset conditions, such as sorting the service data according to the query heat to generate a service data record set.
  • the cache data description field, the cache data response description field, and the service data may be stored in an extended field, such as an extended field X-Record-Set of the cache response for storing the business data record.
  • the ICAP client may open a cache corresponding to the service data according to the cache data response description field, and save the service data in the local cache.
  • the cache data response description field may also be used to determine whether it is still necessary to interact with the ICAP server to continue to acquire service data and the number of times the service data is continuously acquired.
  • the service data matching the ICAP service query request may be preferentially obtained in the locally cached service data according to the ICAP service query request, and the service data in the local cache is pre-stored, if there is a match. It can be used directly, speeding up the acquisition of business data and improving the speed of business response.
  • the data cache request includes a cache data description field, and corresponding service data is obtained according to the data cache request, and a corresponding cache response is returned, and the cache response includes a cache.
  • the data response description field and the service data are used to enable the ICAP client to save the service data in the local cache according to the cached data response description field, and the service data in the local cache is used for the ICAP client to preferentially search when performing the ICAP service query.
  • the corresponding service data to be cached is returned, so that the ICAP client caches the received service data, and is used for priority searching and using for the ICAP service query, since the ICAP server has already
  • the business data is sent to the ICAP client in advance for pre-storage. If there is a match, it can be used directly, which speeds up the acquisition of business data and improves the speed of business response.
  • the method before step S410, further includes: receiving an option query request sent by the ICAP client, where the option query request includes a client cache data support field, and the option query response is returned according to the client cache data support field, and the option query response includes The server caches the data capability field.
  • the option query request carries the client cache data support field.
  • the client cache data support field is an extended field X-Cache-Capability, and the value is 1, indicating that the ICAP client supports the cache cache function, or whatever the value is.
  • X-Cache-Capability it means that the Cache cache function is supported.
  • the option query request message is a request message for multiplexing the ICAP protocol, as long as the required extension field is added in the preset position of the ICAP protocol related request message.
  • the ICAP server After receiving the option query request, the ICAP server determines that the option query request carries the client cache data support field, such as the extended field X-Cache-Capability and the value is 1 or only carries the X-Cache-Capability field regardless of its value.
  • the option query response returned to the ICAP client carries the server cache data capability field.
  • the server cache data capability field is an extended field Y-Cache-Capability, indicating whether the ICAP server supports the cache cache function, and if the value is 1, the support is supported. 0 means not supported.
  • the option query response message is a response message related to the multiplexing of the ICAP protocol, as long as the required extension field is added in the preset position of the response message related to the ICAP protocol.
  • the ICAP client receives the option query response and determines whether the server cache data capability field carried in the option query response, such as whether the extended field Y-Cache-Capability is supported. If the extended field value is 1, it indicates that the data cache request is sent. Otherwise, the data cache request cannot be sent to the ICAP server. For an ICAP server that does not support data caching, the ICAP client's query request can return a corresponding response that does not support data caching, thereby preventing the ICAP client from still sending data caching requests to the ICAP server when the ICAP server does not support data caching. Interference from the ICAP server.
  • the data cache request is a customized data cache request message or a request message for multiplexing the ICAP protocol
  • the cache response is a customized cache response message or a response message for multiplexing the ICAP protocol, a data cache request and a cache response message.
  • the type is the same.
  • the customized data cache request or the cache response message is in a plain text format, and the specific format may be customized as long as the format conforms to the relevant ICAP protocol.
  • the data cache request or the cache response may also be a request message for multiplexing the ICAP protocol, as long as the required extension field is added at a preset location of the ICAP protocol related request message.
  • the data cache request is the same as the message type of the cache response. For example, if the data cache request is customized, the cache response is also customized. According to the message type of the cache request and the cache response, it is convenient for quick resolution between messages.
  • the cache data description field includes a service data request record number field and a service data index field
  • the cache data response description field includes a service data response record number field
  • the service data request record number field is used to describe the number of records of the service data that needs to be delivered by the current request.
  • the data cache request carries the extended field X-Record-Number, so that the current request needs to be delivered by the ICAP server.
  • the service data index field is used to describe the starting position of the service data delivered by the ICAP server, such as the data cache request carrying the extended field X-Record-Index to guide the ICAP server to specify the location from the service data record set. Business data records are issued.
  • the service data index field is used to find the starting location of the service data delivery, and then the service data of the same length as the service data described in the service data request record field is found from the start location, and the target service data delivered by the request is obtained.
  • the service data response record number field is used to describe the number of records of the service data actually delivered by the current ICAP server. The number of records of the service data actually delivered is less than or equal to the number of records of the service data that needs to be delivered this time.
  • the ICAP client can open a corresponding local cache space according to the service data response record field to cache the business data. For example, the cache response carries an extension field X-Record-Number, indicating a service data response record number field.
  • the service data request record field and the service data index field can be used to quickly obtain the target service data, and the service data response record field can quickly determine the size of the local cache.
  • the cache data response description field further includes a service data end flag field
  • the method further includes: determining whether the service data sent to the ICAP client is sent, and if not, the service data end flag field is the resume data. Cache, otherwise the business data end flag field is the end data cache.
  • the service data end flag field is used to describe whether the data cache request is completed. If the service data sent to the ICAP client is sent, the extended field X-Record-Isover may be carried in the cache response, and the A value of 0 indicates that no further transmission is required. If the service data sent to the ICAP client has not been sent, the extension field X-Record-Isover is set to a value of 1, indicating that further transmission is required. End with business data
  • the flag field can divide the service data that needs to be cached into multiple times, so that the data transmission adapts to the real-time situation of the network, and the flexibility of the service data transmission is improved.
  • a data processing apparatus based on an Internet content adaptation protocol including:
  • the data cache request sending module 510 is configured to send a data cache request to the Internet content adaptation protocol ICAP server, where the data cache request includes a cache data description field, so that the ICAP server returns a corresponding cache response according to the data cache request, and the cache response includes Cache data response description fields and business data.
  • the caching module 520 is configured to save the service data in a local cache according to the cache data response description field.
  • the device further includes:
  • the option query module 530 is configured to send an option query request to the ICAP server, where the option query request includes a client cache data support field, so that the ICAP server returns an option query response according to the client cache data support field, and the option query response includes the server cache data capability. Field.
  • the data cache request is a customized data cache request message or a request message for multiplexing the ICAP protocol
  • the cache response is a customized cache response message or a response message for multiplexing the ICAP protocol, a data cache request and a cache response message.
  • the type is the same.
  • the cache data description field includes a service data request record number field and a service data index field
  • the cache data response description field includes a service data response record number field
  • the cache data response description field further includes a service data end flag field
  • the data cache request sending module 510 is further configured to continue to send the data cache request if the service data end flag field is a continuation data ICAP server.
  • the apparatus further includes:
  • the querying module 540 is configured to receive an ICAP service query request, and locally search for the service data matched by the ICAP service query request and directly use the service data.
  • a data processing apparatus based on an Internet content adaptation protocol including:
  • the receiving module 610 is configured to receive a data cache request sent by an Internet Content Adaptation Protocol (ICAP) client, where the data cache request includes a cache data description field.
  • ICAP Internet Content Adaptation Protocol
  • the response module 620 is configured to obtain corresponding service data according to the data cache request, and return a corresponding cache response, where the cache response includes a cache data response description field and the service data, so that the ICAP client sends the service data according to the cache data response description field. Save in the local cache.
  • the apparatus further includes:
  • the option query request response module 630 is configured to receive an option query request sent by the ICAP client, the option query request includes a client cache data support field, and the option query response is returned according to the client cache data support field, and the option query response includes the server cache data capability. Field.
  • the data cache request is a customized data cache request message or a request message for multiplexing the ICAP protocol
  • the cache response is a customized cache response message or a response message for multiplexing the ICAP protocol, a data cache request and a cache response message.
  • the type is the same.
  • the cache data description field includes a service data request record number field and a service data index field
  • the cache data response description field includes a service data response record number field
  • the cache data response description field further includes a service data end flag field
  • the response module 620 is further configured to determine whether the service data sent to the ICAP client is sent. If not, the service data end flag field is Continue data caching, otherwise the business data end flag field is the end data cache.
  • a data processing system based on an Internet content adaptation protocol including:
  • the ICAP client 710 is configured to send a data cache request to the Internet Content Adaptation Protocol ICAP server, the data cache request including a cache data description field.
  • the ICAP client has a data cache function switch, which can receive the function switch function or the signal open data cache function.
  • the data cache function When the data cache function is enabled, if the preset condition is met, the data cache request is sent to the ICAP server.
  • the preset condition can be customized according to requirements, such as a startable data cache control timer, and when the preset timing time arrives, the data cache request is automatically sent to the ICAP server. It can also detect the current network status and send a data cache request according to the current network status. If the network is smooth, send a data cache request, cache the service data, and use the cached service data when the network is congested.
  • the data cache request may also be sent according to the trigger of the user, such as setting a virtual button to receive a signal that the user sends a data cache request.
  • the cache data description field is used to describe the service data that needs to be sent by the ICAP server.
  • the content of the cache data description field can be customized according to requirements.
  • the cache data description field may include the name of the service data, the start position and the end position of the service data, The number of records of business data, etc.
  • the ICAP server 720 is configured to receive a data cache request sent by the ICAP client, obtain corresponding service data according to the data cache request, and return a corresponding cache response, where the cache response includes a cache data response description field and service data.
  • the ICAP server obtains the service data to be delivered according to the cache data description field, and generates a corresponding cache response, where the cache response includes a cache data response description field and service data.
  • the cache data response description field is used to describe the status of the cache response and the service data, and can be customized according to requirements.
  • the cache data response description field includes a service data end flag field, indicating whether the cache data is sent or not, and whether the cache needs to be continuously sent. data.
  • the cached data response description field may also include the number of times the business data continues to be acquired, and the like.
  • the cache data response description field may further include a length field describing the service data, so that the ICAP client can cache the service data according to the cache data response description field.
  • the service data may be sorted according to preset conditions, such as sorting the service data according to the query heat to generate a service data record set.
  • the cache data description field, the cache data response description field, and the service data may be stored in an extended field, such as an extended field X-Record-Set of the cache response for storing the business data record.
  • the ICAP client 710 is also used to save the business data in a local cache according to the cache data response description field.
  • the ICAP client may open a cache corresponding to the service data according to the cache data response description field, and save the service data in the local cache.
  • the cache data response description field may also be used to determine whether it is still necessary to interact with the ICAP server to continue to acquire service data and the number of times the service data is continuously acquired.
  • the service data matching the ICAP service query request may be preferentially obtained in the locally cached service data according to the ICAP service query request, and the service data in the local cache is pre-stored, if there is a match. It can be used directly, speeding up the acquisition of business data and improving the speed of business response.
  • the ICAP server can return the corresponding service data to be cached according to the data cache request sent by the ICAP client, so that the ICAP client caches the received service data. It is preferred to find and use the ICAP service query. Since the ICAP server has previously sent the service data to the ICAP client for pre-storage, if there is a match, it can be used directly, which speeds up the acquisition of business data and improves the speed of business response. .
  • the ICAP client 710 is further configured to send an option query request to the ICAP server 720, the option query request including a client cache data support field to cause the ICAP server 720 to return an option query response according to the client cache data support field.
  • the option query response includes the server cache data capability field.
  • the data cache request is a customized data cache request message or a request message multiplexed with an ICAP protocol
  • the cache response is a customized cache response message or a response message multiplexed with an ICAP protocol
  • the data cache request and The message type of the cached response is the same.
  • the cache data description field includes a service data request record number field and a service data index field
  • the cache data response description field includes a service data response record number field
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).
  • Embodiments of the present invention also provide a storage medium.
  • the foregoing storage medium may be configured to store program code for performing the following steps:
  • the service data is saved in the local cache according to the cache data response description field.
  • the storage medium is further arranged to store program code for performing the following steps:
  • the foregoing storage medium may include, but not limited to, a USB flash drive, a Read-Only Memory (ROM), a Random Access Memory (RAM), a mobile hard disk, and a magnetic memory.
  • ROM Read-Only Memory
  • RAM Random Access Memory
  • a mobile hard disk e.g., a hard disk
  • magnetic memory e.g., a hard disk
  • the ICAP server can return the corresponding service data to be cached according to the data cache request sent by the ICAP client through the cooperation of the IAP client and the ICAP server, so that the ICAP client will receive the data.
  • the service data is cached and used for priority search and use in the ICAP service query. Since the ICAP server has previously sent the service data to the ICAP client for pre-storage, if there is a match that can be directly used, the service data acquisition speed is accelerated. Increased the speed of business response.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本发明实施例涉及一种基于因特网内容适配协议的数据处理方法，包括：向因特网内容适配协议ICAP服务器发送数据缓存请求，所述数据缓存请求包括缓存数据说明字段，以使所述ICAP服务器根据所述数据缓存请求返回对应的缓存响应，所述缓存响应包括缓存数据响应说明字段和业务数据；根据所述缓存数据响应说明字段将所述业务数据保存在本地缓存，本地缓存中的业务数据可用于ICAP业务查询时优先查找并使用，提高了业务响应的速度，此外，还提供了一种基于因特网内容适配协议的数据处理装置和系统。

Description

基于因特网内容适配协议的数据处理方法、装置和系统 技术领域
本发明实施例涉及通信领域，特别是涉及一种基于因特网内容适配协议的数据处理方法、装置和系统。
背景技术
ICAP(Internet Content Adaptation Protocol，因特网内容适配协议)设计的目的是使Web内容设备能够互操作、共享数据和控制信息，使得用户能够在分离的设备上实施某种服务，优化所执行的功能。ICAP是轻量级的基于HTTP(HyperText Transfer Protocol，超文本传输协议)的远程过程调用协议，设备可以传送基于HTTP的内容到ICAP服务器进行内容操作。
相关技术中，当ICAP请求访问频率激增或网络状况差的时候，可能导致ICAP服务器负荷增大处理时长变长，也可能导致ICAP请求、应答消息在网络中滞留时间变长，这两种情况都会导致ICAP业务服务提供速度迟缓。
发明内容
基于此，有必要针对上述技术问题，提供一种基于因特网内容适配协议的数据处理方法、装置和系统，提高ICAP业务的响应速度。
一种基于因特网内容适配协议的数据处理方法，所述方法包括：
向因特网内容适配协议ICAP服务器发送数据缓存请求，所述数据缓存请求包括缓存数据说明字段，以使所述ICAP服务器根据所述数据缓存请求返回对应的缓存响应，所述缓存响应包括缓存数据响应说明字段和业务数据；
根据所述缓存数据响应说明字段将所述业务数据保存在本地缓存。
在其中一个实施例中，所述向ICAP服务器发送数据缓存请求的步骤 之前，还包括：
向ICAP服务器发送选项查询请求，所述选项查询请求包括客户端缓存数据支持字段，以使所述ICAP服务器根据所述客户端缓存数据支持字段返回选项查询响应，所述选项查询响应包括服务器缓存数据能力字段。
在其中一个实施例中，所述数据缓存请求为定制的数据缓存请求消息或复用ICAP协议的请求消息，所述缓存响应为定制的缓存响应消息或复用ICAP协议的响应消息，所述数据缓存请求与缓存响应的消息类型一致。
在其中一个实施例中，所述缓存数据说明字段包括业务数据请求记录数字段和业务数据索引字段，所述缓存数据响应说明字段包括业务数据响应记录数字段。
在其中一个实施例中，所述缓存数据响应说明字段还包括业务数据结束标志字段，所述根据所述缓存数据响应说明字段将所述业务数据保存在本地缓存的步骤之后还包括：
如果所述业务数据结束标志字段为继续数据缓存，则向ICAP服务器继续发送数据缓存请求。
在其中一个实施例中，还包括：
接收ICAP业务查询请求；
在所述本地缓存查找所述ICAP业务查询请求匹配的业务数据并直接使用。
一种基于因特网内容适配协议的数据处理装置，所述装置包括：
数据缓存请求发送模块，设置为向因特网内容适配协议ICAP服务器发送数据缓存请求，所述数据缓存请求包括缓存数据说明字段，以使所述ICAP服务器根据所述数据缓存请求返回对应的缓存响应，所述缓存响应包括缓存数据响应说明字段和业务数据；
缓存模块，设置为根据所述缓存数据响应说明字段将所述业务数据保存在本地缓存。
上述基于因特网内容适配协议的数据处理方法和装置，通过向因特网内容适配协议ICAP服务器发送数据缓存请求，数据缓存请求包括缓存数据说明字段，以使ICAP服务器根据数据缓存请求返回对应的缓存响应，缓存响应包括缓存数据响应说明字段和业务数据，根据缓存数据响应说明字段将业务数据保存在本地缓存，由于本地缓存中的业务数据已经预先存储好了，当有ICAP业务查询时可在本地缓存中查找匹配的业务数据，如果有匹配的可直接使用，加快了业务数据的获取速度，提高了业务响应的速度。
一种基于因特网内容适配协议的数据处理方法，所述方法包括：
接收因特网内容适配协议ICAP客户端发送的数据缓存请求，所述数据缓存请求包括缓存数据说明字段；
根据所述数据缓存请求获取对应的业务数据，返回对应的缓存响应，所述缓存响应包括缓存数据响应说明字段和所述业务数据，以使所述ICAP客户端根据所述缓存数据响应说明字段将所述业务数据保存在本地缓存。
在其中一个实施例中，所述接收ICAP客户端发送的数据缓存请求的步骤之前，还包括：
接收ICAP客户端发送的选项查询请求，所述选项查询请求包括客户端缓存数据支持字段，根据所述客户端缓存数据支持字段返回选项查询响应，所述选项查询响应包括服务器缓存数据能力字段。
在其中一个实施例中，所述数据缓存请求为定制的数据缓存请求消息或复用ICAP协议的请求消息，所述缓存响应为定制的缓存响应消息或复用ICAP协议的响应消息，所述数据缓存请求与缓存响应的消息类型一致。
在其中一个实施例中，所述缓存数据说明字段包括业务数据请求记录数字段和业务数据索引字段，所述缓存数据响应说明字段包括业务数据响应记录数字段。
在其中一个实施例中，所述缓存数据响应说明字段还包括业务数据结 束标志字段，所述方法还包括：
判断向ICAP客户端发送的业务数据是否发送完毕，如果没有发送完毕，则所述业务数据结束标志字段为继续数据缓存，否则所述业务数据结束标志字段为结束数据缓存。
一种基于因特网内容适配协议的数据处理装置，所述装置包括：
接收模块，设置为接收因特网内容适配协议ICAP客户端发送的数据缓存请求，所述数据缓存请求包括缓存数据说明字段；
响应模块，设置为根据所述数据缓存请求获取对应的业务数据，返回对应的缓存响应，所述缓存响应包括缓存数据响应说明字段和所述业务数据，以使所述ICAP客户端根据所述缓存数据响应说明字段将所述业务数据保存在本地缓存。
上述基于因特网内容适配协议的数据处理方法和装置，通过接收因特网内容适配协议ICAP客户端发送的数据缓存请求，数据缓存请求包括缓存数据说明字段，根据数据缓存请求获取对应的业务数据，返回对应的缓存响应，缓存响应包括缓存数据响应说明字段和所述业务数据，以使ICAP客户端根据所述缓存数据响应说明字段将业务数据保存在本地缓存，本地缓存中的业务数据用于ICAP客户端在进行ICAP业务查询时优先查找并使用，可根据ICAP客户端发送的数据缓存请求返回对应的需要缓存的业务数据，使得ICAP客户端将接收到的业务数据进行缓存，用于ICAP业务查询时优先查找并使用，由于ICAP服务器已经提前将业务数据发送至ICAP客户端预先存储好了，如果有匹配的可直接使用，加快了业务数据的获取速度，提高了业务响应的速度。
一种基于因特网内容适配协议的数据处理系统，所述系统包括：
ICAP客户端，设置为向因特网内容适配协议ICAP服务器发送数据缓存请求，所述数据缓存请求包括缓存数据说明字段；
ICAP服务器，设置为接收ICAP客户端发送的数据缓存请求，根据所述数据缓存请求获取对应的业务数据，返回对应的缓存响应，所述缓存 响应包括缓存数据响应说明字段和所述业务数据；
所述ICAP客户端还设置为根据所述缓存数据响应说明字段将所述业务数据保存在本地缓存。
在本发明实施例中，还提供了一种计算机存储介质，该计算机存储介质可以存储有执行指令，该执行指令用于执行上述实施例中的基于因特网内容适配协议的数据处理方法。
上述基于因特网内容适配协议的数据处理系统，通过因特网内容适配协议ICAP客户端和ICAP服务器的配合，ICAP服务器可根据ICAP客户端发送的数据缓存请求返回对应的需要缓存的业务数据，使得ICAP客户端将接收到的业务数据进行缓存，用于ICAP业务查询时优先查找并使用，由于ICAP服务器已经提前将业务数据发送至ICAP客户端预先存储好了，如果有匹配的可直接使用，加快了业务数据的获取速度，提高了业务响应的速度。
附图说明
图1为一个实施例中基于因特网内容适配协议的数据处理方法的应用环境图；
图2为一个实施例中基于因特网内容适配协议的数据处理方法的流程图；
图3为另一个实施例中基于因特网内容适配协议的数据处理方法的流程图；
图4为一个实施例中另一种基于因特网内容适配协议的数据处理方法的流程图；
图5为一个实施例中基于因特网内容适配协议的数据处理装置的结构框图；
图6为另一个实施例中基于因特网内容适配协议的数据处理装置的 结构框图；
图7为再一个实施例中基于因特网内容适配协议的数据处理装置的结构框图；
图8为一个实施例中另一种基于因特网内容适配协议的数据处理装置的结构框图；
图9为另一个实施例中另一种基于因特网内容适配协议的数据处理装置的结构框图；
图10为一个实施例中基于因特网内容适配协议的数据处理系统的结构框图。
具体实施方式
图1为一个实施例中基于因特网内容适配协议的数据处理方法运行的应用环境图。如图1所示，该应用环境包括ICAP客户端110、ICAP服务器120，其中ICAP客户端110和ICAP服务器120通过网络进行通信。
ICAP客户端110为支持ICAP协议的客户端可为安装支持ICAP协议软件的PC机、终端，也为实现ICAP协议的电信级网络节点设备，但不局限于此。ICAP客户端110通过向ICAP服务器120发送相关请求消息，以获取相关资源用于业务处理。
ICAP服务器120可为支持ICAP协议的服务器，也可为安装支持ICAP协议软件的PC机、终端、商用服务器，也可为实现ICAP协议的电信级网络节点设备，但不局限于此。ICAP服务器120对ICAP客户端110发送过来的ICAP协议消息进行相关业务处理后，返回给ICAP客户端110应答消息，携带ICAP客户端110所需要的相关资源。
如图2所示，在一个实施例中，提供了一种基于因特网内容适配协议的数据处理方法，以应用于上述应用环境中的ICAP客户端来举例说明，包括如下步骤：
步骤S210，向因特网内容适配协议ICAP服务器发送数据缓存请求， 数据缓存请求包括缓存数据说明字段，以使ICAP服务器根据数据缓存请求返回对应的缓存响应，缓存响应包括缓存数据响应说明字段和业务数据。
具体的，ICAP客户端存在数据缓存功能开关，可接收对功能开关的操作或信号打开数据缓存功能，当数据缓存功能打开时，如果预设条件满足，则向ICAP服务器进行数据缓存请求的发送，预设条件可根据需要自定义，如可启动数据缓存控制定时器，当预设的定时时间到达时，自动向ICAP服务器发送数据缓存请求。也可以检测当前的网络状态，根据当前的网络状态发送数据缓存请求，如网络流畅时，发送数据缓存请求，进行业务数据的缓存，在网络拥塞时就可利用缓存的业务数据。也可根据用户的触发发送数据缓存请求，如设置虚拟按键接收用户发送数据缓存请求的信号。缓存数据说明字段用于描述需要ICAP服务器下发的业务数据，以使得ICAP服务器根据缓存数据说明字段获取需要下发的业务数据，缓存数据说明字段的内容可根据需要自定义，如缓存数据说明字段可包括业务数据的名称、业务数据的起始位置和终止位置、业务数据的记录数等。ICAP服务器获取到需要下发的业务数据后，生成对应的缓存响应，缓存响应中包括了缓存数据响应说明字段和业务数据。其中缓存数据响应说明字段用于描述缓存响应的状态和业务数据，可根据需要自定义，如缓存数据响应说明字段包括业务数据结束标志字段，表示缓存数据下发是否完毕，是否需要继续下发缓存数据。缓存数据响应说明字段还可包括业务数据继续获取的次数等。缓存数据响应说明字段还可包括描述业务数据的长度字段，便于ICAP客户端根据缓存数据响应说明字段进行业务数据的缓存。可以理解的是，在下发业务数据前，可根据预设条件对业务数据进行排序，如按照查询热度对业务数据进行排序生成业务数据记录集合。缓存数据说明字段、缓存数据响应说明字段和业务数据可存放在扩展的字段中，如缓存响应的扩展字段X-Record-Set用来存放业务数据记录。
步骤S220，根据缓存数据响应说明字段将业务数据保存在本地缓存。
具体的，可根据缓存数据响应说明字段开辟与业务数据对应的缓存，将业务数据保存在本地缓存。还可根据缓存数据响应说明字段判断是否还 需要与ICAP服务器交互继续获取业务数据以及继续获取业务数据的次数等。在有ICAP业务查询时，可根据ICAP业务查询请求，优先在本地缓存的业务数据中获取与ICAP业务查询请求匹配的业务数据，由于本地缓存中的业务数据已经预先存储好了，如果有匹配的可直接使用，加快了业务数据的获取速度，提高了业务响应的速度。在一个实施例中，可根据本地缓存中的业务数据的匹配使用情况更新数据缓存请求的生成策略和更新本地缓存中的业务数据，提高本地缓存中的业务数据的利用率和节省本地缓存的空间，如对于长时间不使用的本地缓存中的业务数据可进行删除。
本实施例中，通过向因特网内容适配协议ICAP服务器发送数据缓存请求，数据缓存请求包括缓存数据说明字段，以使ICAP服务器根据数据缓存请求返回对应的缓存响应，缓存响应包括缓存数据响应说明字段和业务数据，根据缓存数据响应说明字段将业务数据保存在本地缓存，由于本地缓存中的业务数据已经预先存储好了，当有ICAP业务查询时可在本地缓存中查找匹配的业务数据，如果有匹配的可直接使用，加快了业务数据的获取速度，提高了业务响应的速度。
在一个实施例中，如图3所示，提供了一种基于因特网内容适配协议的数据处理方法，包括以下步骤：
步骤S310，向ICAP服务器发送选项查询请求，选项查询请求包括客户端缓存数据支持字段，以使ICAP服务器根据客户端缓存数据支持字段返回选项查询响应，选项查询响应包括服务器缓存数据能力字段。
具体的，向ICAP服务器发送选项查询请求，其中携带客户端缓存数据支持字段，如客户端缓存数据支持字段为扩展字段X-Cache-Capability，值为1，表示ICAP客户端支持Cache缓存功能或无论其值为多少，只要存在扩展字段X-Cache-Capability则表示支持Cache缓存功能。选项查询请求这个消息是复用ICAP协议相关的请求消息，只要在ICAP协议相关的请求消息的预设位置加入需要的扩展字段即可。ICAP服务器收到选项 查询请求后，判断选项查询请求中携带了客户端缓存数据支持字段，如扩展字段X-Cache-Capability字段，则向ICAP客户端返回的选项查询响应中携带服务器缓存数据能力字段，如服务器缓存数据能力字段为扩展字段Y-Cache-Capability，表示ICAP服务器是否支持Cache缓存功能，如值为1表示支持，0表示不支持。选项查询响应这个消息是复用ICAP协议相关的响应消息，只要在ICAP协议相关的响应消息的预设位置加入需要的扩展字段即可。
步骤S320，判断服务器缓存数据能力字段是否为ICAP服务器支持数据缓存，如果是，则进入步骤S330，否则不作处理。
具体的，ICAP客户端收到选项查询响应，并判断选项查询响应携带的服务器缓存数据能力字段，如扩展字段Y-Cache-Capability是否为支持，如扩展字段值为1，则表示支持，则进入步骤S330进行数据缓存请求的发送。如果ICAP服务器不支持数据缓存，则不作处理，不能向ICAP服务器发送数据缓存请求。在发送数据缓存请求前，进行ICAP服务器是否支持数据缓存的查询，可避免ICAP服务器不支持数据缓存时，仍然向ICAP服务器发送数据缓存请求造成对ICAP服务器的干扰。
步骤S330，向ICAP服务器发送数据缓存请求，数据缓存请求包括缓存据说明字段，以使ICAP服务器根据数据缓存请求返回对应的缓存响应，缓存响应包括缓存数据响应说明字段和业务数据。
步骤S340，根据缓存数据响应说明字段将业务数据保存在本地缓存。
在一个实施例中，数据缓存请求为定制的数据缓存请求消息或复用ICAP协议的请求消息，缓存响应为定制的缓存响应消息或复用ICAP协议的响应消息，数据缓存请求与缓存响应的消息类型一致。
具体的，定制的数据缓存请求或缓存响应消息为纯文本格式，具体的格式可自定义，只要格式符合相关ICAP协议规定即可。数据缓存请求或缓存响应也可为复用ICAP协议的请求消息，只要在ICAP协议相关的请求消息的预设位置加入需要的扩展字段即可。数据缓存请求与缓存响应的 消息类型一致，比如数据缓存请求为定制的，则缓存响应也为定制的，数据缓存请求与缓存响应的消息类型一致，便于消息之间的快速解析。
在一个实施例中，缓存数据说明字段包括业务数据请求记录数字段和业务数据索引字段，缓存数据响应说明字段包括业务数据响应记录数字段。
具体的，业务数据请求记录数字段用于描述本次请求需要下发的业务数据的记录数，如数据缓存请求中携带扩展字段X-Record-Number，以表示本次请求需要ICAP服务器下发的业务数据记录数。业务数据索引字段用于描述本次请求需要ICAP服务器下发的业务数据的起始位置，如数据缓存请求中携带扩展字段X-Record-Index，以指导ICAP服务器从业务数据记录集合中指定位置的业务数据记录开始下发。通过业务数据索引字段找到业务数据下发的起始位置，然后从起始位置开始找到与业务数据请求记录数字段描述的业务数据长度相同的业务数据，就为本次请求下发的目标业务数据。业务数据响应记录数字段用于描述本次ICAP服务器实际下发的业务数据的记录数，实际下发的业务数据的记录数小于或等于本次请求需要下发的业务数据的记录数。ICAP客户端可根据业务数据响应记录数字段开辟对应大小的本地缓存空间，用于将业务数据进行缓存。如缓存响应中携带扩展字段X-Record-Number，表示业务数据响应记录数字段。通过业务数据请求记录数字段和业务数据索引字段可快速获取目标业务数据，通过业务数据响应记录数字段可快速确定本地缓存的空间大小。在一个实施例中，缓存数据响应说明字段还包括业务数据结束标志字段，
步骤S220之后，还包括：如果业务数据结束标志字段为继续数据缓存，则向ICAP服务器继续发送数据缓存请求。
具体的，业务数据结束标志字段用于描述本次数据缓存请求是否响应完毕，如缓存响应中携带扩展字段X-Record-Isover，根据缓存响应中的扩展字段X-Record-Isover来判断是否继续与ICAP服务器进行交互索要业务数据记录，如X-Record-Isover值为1表示需要继续交互，X-Record-Isover值为0表示不需要，如果业务数据结束标志字段为继续数据缓存，即X-Record-Isover值为1，则向ICAP服务器继续发送数据缓 存请求，继续获取需要缓存的业务数据，否则本次缓存的业务数据获取完毕。通过业务数据结束标志字段可将需要缓存的业务数据分为多次进行下发，使得数据的传输适应网络实时情况，提高了业务数据传输的灵活性。
在一个实施例中，还包括：接收ICAP业务查询请求，在本地缓存查找ICAP业务查询请求匹配的业务数据并直接使用。
具体的，在接收到ICAP业务查询请求后，优先在本地缓存的业务数据中获取与ICAP业务查询请求匹配的业务数据，由于本地缓存中的业务数据已经预先存储好了，如果有匹配的可直接使用，加快了业务数据的获取速度，提高了业务响应的速度。如果没有查找到匹配的业务数据，再向ICAP服务器发送业务请求消息，从ICAP服务器获取匹配的业务数据。
在一个实施例中，如图4所示，提供了一种基于因特网内容适配协议的数据处理方法，以应用于上述应用环境中的ICAP服务器来举例说明，包括如下步骤：
步骤S410，接收因特网内容适配协议ICAP客户端发送的数据缓存请求，数据缓存请求包括缓存数据说明字段。
具体的，缓存数据说明字段用于描述需要ICAP服务器下发的业务数据，ICAP服务器可根据缓存数据说明字段获取需要下发的业务数据，缓存数据说明字段的内容可根据需要自定义，如缓存数据说明字段可包括业务数据的名称、业务数据的起始位置和终止位置、业务数据的记录数等。
步骤S420，根据数据缓存请求获取对应的业务数据，返回对应的缓存响应，缓存响应包括缓存数据响应说明字段和业务数据，以使ICAP客户端根据缓存数据响应说明字段将所述业务数据保存在本地缓存。
具体的，ICAP服务器根据数据缓存请求获取到需要下发的业务数据后，生成对应的缓存响应，缓存响应中包括了缓存数据响应说明字段和业务数据。其中缓存数据响应说明字段用于描述缓存响应的状态和业务数据，可根据需要自定义，如缓存数据响应说明字段包括业务数据结束标志字段，表示缓存数据下发是否完毕，是否需要继续下发缓存数据。缓存数据响应 说明字段还可包括业务数据继续获取的次数等。缓存数据响应说明字段还可包括描述业务数据的长度字段，便于ICAP客户端根据缓存数据响应说明字段进行业务数据的缓存。可以理解的是，在下发业务数据前，可根据预设条件对业务数据进行排序，如按照查询热度对业务数据进行排序生成业务数据记录集合。缓存数据说明字段、缓存数据响应说明字段和业务数据可存放在扩展的字段中，如缓存响应的扩展字段X-Record-Set用来存放业务数据记录。
ICAP客户端接收到缓存响应后，可根据缓存数据响应说明字段开辟与业务数据对应的缓存，将业务数据保存在本地缓存。还可根据缓存数据响应说明字段判断是否还需要与ICAP服务器交互继续获取业务数据以及继续获取业务数据的次数等。在有ICAP业务查询时，可根据ICAP业务查询请求，优先在本地缓存的业务数据中获取与ICAP业务查询请求匹配的业务数据，由于本地缓存中的业务数据已经预先存储好了，如果有匹配的可直接使用，加快了业务数据的获取速度，提高了业务响应的速度。
本实施例中，通过接收因特网内容适配协议ICAP客户端发送的数据缓存请求，数据缓存请求包括缓存数据说明字段，根据数据缓存请求获取对应的业务数据，返回对应的缓存响应，缓存响应包括缓存数据响应说明字段和所述业务数据，以使ICAP客户端根据所述缓存数据响应说明字段将业务数据保存在本地缓存，本地缓存中的业务数据用于ICAP客户端在进行ICAP业务查询时优先查找并使用，可根据ICAP客户端发送的数据缓存请求返回对应的需要缓存的业务数据，使得ICAP客户端将接收到的业务数据进行缓存，用于ICAP业务查询时优先查找并使用，由于ICAP服务器已经提前将业务数据发送至ICAP客户端预先存储好了，如果有匹配的可直接使用，加快了业务数据的获取速度，提高了业务响应的速度。
在一个实施例中，步骤S410之前，还包括：接收ICAP客户端发送的选项查询请求，选项查询请求包括客户端缓存数据支持字段，根据客户端缓存数据支持字段返回选项查询响应，选项查询响应包括服务器缓存数据能力字段。
具体的，选项查询请求中携带客户端缓存数据支持字段，如客户端缓存数据支持字段为扩展字段X-Cache-Capability，值为1，表示ICAP客户端支持Cache缓存功能，或无论其值为多少，只要存在扩展字段X-Cache-Capability则表示支持Cache缓存功能。选项查询请求这个消息是复用ICAP协议相关的请求消息，只要在ICAP协议相关的请求消息的预设位置加入需要的扩展字段即可。ICAP服务器收到选项查询请求后，判断选项查询请求中携带了客户端缓存数据支持字段，如扩展字段X-Cache-Capability且值为1或只要携带了X-Cache-Capability字段无论其值为多少，则向ICAP客户端返回的选项查询响应中携带服务器缓存数据能力字段，如服务器缓存数据能力字段为扩展字段Y-Cache-Capability，表示ICAP服务器是否支持Cache缓存功能，如值为1表示支持，0表示不支持。选项查询响应这个消息是复用ICAP协议相关的响应消息，只要在ICAP协议相关的响应消息的预设位置加入需要的扩展字段即可。ICAP客户端收到选项查询响应，并判断选项查询响应携带的服务器缓存数据能力字段，如扩展字段Y-Cache-Capability是否为支持，如扩展字段值为1，则表示支持，则发送数据缓存请求，否则不能向ICAP服务器发送数据缓存请求。对于不支持数据缓存的ICAP服务器，可向ICAP客户端的查询请求返回不支持数据缓存的对应的响应，从而可避免ICAP服务器不支持数据缓存时，ICAP客户端仍然向ICAP服务器发送数据缓存请求造成对ICAP服务器的干扰。
在一个实施例中，数据缓存请求为定制的数据缓存请求消息或复用ICAP协议的请求消息，缓存响应为定制的缓存响应消息或复用ICAP协议的响应消息，数据缓存请求与缓存响应的消息类型一致。
具体的，定制的数据缓存请求或缓存响应消息为纯文本格式，具体的格式可自定义，只要格式符合相关ICAP协议规定即可。数据缓存请求或缓存响应也可为复用ICAP协议的请求消息，只要在ICAP协议相关的请求消息的预设位置加入需要的扩展字段即可。数据缓存请求与缓存响应的消息类型一致，比如数据缓存请求为定制的，则缓存响应也为定制的，数 据缓存请求与缓存响应的消息类型一致，便于消息之间的快速解析。
在一个实施例中，缓存数据说明字段包括业务数据请求记录数字段和业务数据索引字段，缓存数据响应说明字段包括业务数据响应记录数字段。
具体的，业务数据请求记录数字段用于描述本次请求需要下发的业务数据的记录数，如数据缓存请求中携带扩展字段X-Record-Number，以表示本次请求需要ICAP服务器下发的业务数据记录数。业务数据索引字段用于描述本次请求需要ICAP服务器下发的业务数据的起始位置，如数据缓存请求中携带扩展字段X-Record-Index，以指导ICAP服务器从业务数据记录集合中指定位置的业务数据记录开始下发。通过业务数据索引字段找到业务数据下发的起始位置，然后从起始位置开始找到与业务数据请求记录数字段描述的业务数据长度相同的业务数据，就为本次请求下发的目标业务数据。业务数据响应记录数字段用于描述本次ICAP服务器实际下发的业务数据的记录数，实际下发的业务数据的记录数小于或等于本次请求需要下发的业务数据的记录数。ICAP客户端可根据业务数据响应记录数字段开辟对应大小的本地缓存空间，用于将业务数据进行缓存。如缓存响应中携带扩展字段X-Record-Number，表示业务数据响应记录数字段。通过业务数据请求记录数字段和业务数据索引字段可快速获取目标业务数据，通过业务数据响应记录数字段可快速确定本地缓存的空间大小。
在一个实施例中，缓存数据响应说明字段还包括业务数据结束标志字段，方法还包括：判断向ICAP客户端发送的业务数据是否发送完毕，如果没有发送完毕，则业务数据结束标志字段为继续数据缓存，否则业务数据结束标志字段为结束数据缓存。
具体的，业务数据结束标志字段用于描述本次数据缓存请求是否响应完毕，如果向ICAP客户端发送的业务数据发送完毕，则可在缓存响应中携带扩展字段X-Record-Isover，且设置其值为0表示不需要再进行发送，如果向ICAP客户端发送的业务数据没有发送完毕，则将扩展字段X-Record-Isover设置其值为1，表示还需要继续发送。通过业务数据结束 标志字段可将需要缓存的业务数据分为多次进行下发，使得数据的传输适应网络实时情况，提高了业务数据传输的灵活性。
在一个实施例中，如图5所示，提供了一种基于因特网内容适配协议的数据处理装置，包括：
数据缓存请求发送模块510，设置为向因特网内容适配协议ICAP服务器发送数据缓存请求，数据缓存请求包括缓存数据说明字段，以使ICAP服务器根据所述数据缓存请求返回对应的缓存响应，缓存响应包括缓存数据响应说明字段和业务数据。
缓存模块520，设置为根据缓存数据响应说明字段将业务数据保存在本地缓存。
在一个实施例中，如图6所示，所述装置还包括：
选项查询模块530，设置为向ICAP服务器发送选项查询请求，选项查询请求包括客户端缓存数据支持字段，以使ICAP服务器根据客户端缓存数据支持字段返回选项查询响应，选项查询响应包括服务器缓存数据能力字段。
在一个实施例中，数据缓存请求为定制的数据缓存请求消息或复用ICAP协议的请求消息，缓存响应为定制的缓存响应消息或复用ICAP协议的响应消息，数据缓存请求与缓存响应的消息类型一致。
在一个实施例中，缓存数据说明字段包括业务数据请求记录数字段和业务数据索引字段，缓存数据响应说明字段包括业务数据响应记录数字段。
在一个实施例中，缓存数据响应说明字段还包括业务数据结束标志字段，所述数据缓存请求发送模块510还设置为如果业务数据结束标志字段为继续数据ICAP服务器继续发送数据缓存请求。
在一个实施例中，如图7所示，所述装置还包括：
查询模块540，设置为接收ICAP业务查询请求，在本地缓存查找所述ICAP业务查询请求匹配的业务数据并直接使用。
在一个实施例中，如图8所示，提供了一种基于因特网内容适配协议的数据处理装置，包括：
接收模块610，设置为接收因特网内容适配协议ICAP客户端发送的数据缓存请求，数据缓存请求包括缓存数据说明字段。
响应模块620，设置为根据数据缓存请求获取对应的业务数据，返回对应的缓存响应，缓存响应包括缓存数据响应说明字段和所述业务数据，以使ICAP客户端根据缓存数据响应说明字段将业务数据保存在本地缓存。
在一个实施例中，如图9所示，所述装置还包括：
选项查询请求响应模块630，设置为接收ICAP客户端发送的选项查询请求，选项查询请求包括客户端缓存数据支持字段，根据客户端缓存数据支持字段返回选项查询响应，选项查询响应包括服务器缓存数据能力字段。
在一个实施例中，数据缓存请求为定制的数据缓存请求消息或复用ICAP协议的请求消息，缓存响应为定制的缓存响应消息或复用ICAP协议的响应消息，数据缓存请求与缓存响应的消息类型一致。
在一个实施例中，缓存数据说明字段包括业务数据请求记录数字段和业务数据索引字段，缓存数据响应说明字段包括业务数据响应记录数字段。
在一个实施例中，缓存数据响应说明字段还包括业务数据结束标志字段，响应模块620还设置为判断向ICAP客户端发送的业务数据是否发送完毕，如果没有发送完毕，则业务数据结束标志字段为继续数据缓存，否则业务数据结束标志字段为结束数据缓存。
在一个实施例中，如图10所示，提供了一种基于因特网内容适配协议的数据处理系统，包括：
ICAP客户端710，设置为向因特网内容适配协议ICAP服务器发送数据缓存请求，数据缓存请求包括缓存数据说明字段。
具体的，ICAP客户端存在数据缓存功能开关，可接收对功能开关的操作或信号打开数据缓存功能，当数据缓存功能打开时，如果预设条件满足，则向ICAP服务器进行数据缓存请求的发送，预设条件可根据需要自定义，如可启动数据缓存控制定时器，当预设的定时时间到达时，自动向ICAP服务器发送数据缓存请求。也可以检测当前的网络状态，根据当前的网络状态发送数据缓存请求，如网络流畅时，发送数据缓存请求，进行业务数据的缓存，在网络拥塞时就可利用缓存的业务数据。也可根据用户的触发发送数据缓存请求，如设置虚拟按键接收用户发送数据缓存请求的信号。缓存数据说明字段用于描述需要ICAP服务器下发的业务数据，缓存数据说明字段的内容可根据需要自定义，如缓存数据说明字段可包括业务数据的名称、业务数据的起始位置和终止位置、业务数据的记录数等。
ICAP服务器720，设置为接收ICAP客户端发送的数据缓存请求，根据数据缓存请求获取对应的业务数据，返回对应的缓存响应，缓存响应包括缓存数据响应说明字段和业务数据。
具体的，ICAP服务器根据缓存数据说明字段获取需要下发的业务数据，生成对应的缓存响应，缓存响应中包括了缓存数据响应说明字段和业务数据。其中缓存数据响应说明字段用于描述缓存响应的状态和业务数据，可根据需要自定义，如缓存数据响应说明字段包括业务数据结束标志字段，表示缓存数据下发是否完毕，是否需要继续下发缓存数据。缓存数据响应说明字段还可包括业务数据继续获取的次数等。缓存数据响应说明字段还可包括描述业务数据的长度字段，便于ICAP客户端根据缓存数据响应说明字段进行业务数据的缓存。可以理解的是，在下发业务数据前，可根据预设条件对业务数据进行排序，如按照查询热度对业务数据进行排序生成业务数据记录集合。缓存数据说明字段、缓存数据响应说明字段和业务数据可存放在扩展的字段中，如缓存响应的扩展字段X-Record-Set用来存放业务数据记录。
ICAP客户端710还用于根据缓存数据响应说明字段将业务数据保存在本地缓存。
具体的，ICAP客户端接收到缓存响应后，可根据缓存数据响应说明字段开辟与业务数据对应的缓存，将业务数据保存在本地缓存。还可根据缓存数据响应说明字段判断是否还需要与ICAP服务器交互继续获取业务数据以及继续获取业务数据的次数等。在有ICAP业务查询时，可根据ICAP业务查询请求，优先在本地缓存的业务数据中获取与ICAP业务查询请求匹配的业务数据，由于本地缓存中的业务数据已经预先存储好了，如果有匹配的可直接使用，加快了业务数据的获取速度，提高了业务响应的速度。
本实施例中，通过ICAP客户端和ICAP服务器的配合，ICAP服务器可根据ICAP客户端发送的数据缓存请求返回对应的需要缓存的业务数据，使得ICAP客户端将接收到的业务数据进行缓存，用于ICAP业务查询时优先查找并使用，由于ICAP服务器已经提前将业务数据发送至ICAP客户端预先存储好了，如果有匹配的可直接使用，加快了业务数据的获取速度，提高了业务响应的速度。
在一个实施例中，ICAP客户端710还用于向ICAP服务器720发送选项查询请求，选项查询请求包括客户端缓存数据支持字段，以使ICAP服务器720根据客户端缓存数据支持字段返回选项查询响应，选项查询响应包括服务器缓存数据能力字段。
在一个实施例中，数据缓存请求为定制的数据缓存请求消息或复用ICAP协议的请求消息，所述缓存响应为定制的缓存响应消息或复用ICAP协议的响应消息，所述数据缓存请求与缓存响应的消息类型一致。
在一个实施例中，缓存数据说明字段包括业务数据请求记录数字段和业务数据索引字段，缓存数据响应说明字段包括业务数据响应记录数字段。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计算机程序来指令相关的硬件来完成，所述程序可存储于一计算机可读取存储介质中，如本发明实施例中，该程序可存储于计算机系统的存储介质中，并被该计算机系统中的至少一个处理器执行，以实 现包括如上述各方法的实施例的流程。其中，所述存储介质可为磁碟、光盘、只读存储记忆体(Read-Only Memory，ROM)或随机存储记忆体(Random Access Memory，RAM)等。
以上所述实施例的各技术特征可以进行任意的组合，为使描述简洁，未对上述实施例中的各个技术特征所有可能的组合都进行描述，然而，只要这些技术特征的组合不存在矛盾，都应当认为是本说明书记载的范围。
以上所述实施例仅表达了本发明的几种实施方式，其描述较为具体和详细，但并不能因此而理解为对发明专利范围的限制。应当指出的是，对于本领域的普通技术人员来说，在不脱离本发明构思的前提下，还可以做出若干变形和改进，这些都属于本发明的保护范围。因此，本发明专利的保护范围应以所附权利要求为准。
本发明的实施例还提供了一种存储介质。可选地，在本实施例中，上述存储介质可以被设置为存储用于执行以下步骤的程序代码：
S1，向因特网内容适配协议ICAP服务器发送数据缓存请求，数据缓存请求包括缓存数据说明字段，以使ICAP服务器根据数据缓存请求返回对应的缓存响应，缓存响应包括缓存数据响应说明字段和业务数据；
S2，根据缓存数据响应说明字段将业务数据保存在本地缓存。
可选地，存储介质还被设置为存储用于执行以下步骤的程序代码：
S1，向ICAP服务器发送数据缓存请求的步骤之前，向ICAP服务器发送选项查询请求，选项查询请求包括客户端缓存数据支持字段，以使ICAP服务器根据客户端缓存数据支持字段返回选项查询响应，选项查询响应包括服务器缓存数据能力字段。
可选地，在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
可选地，本实施例中的具体示例可以参考上述实施例及可选实施方式 中所描述的示例，本实施例在此不再赘述。
工业实用性
在本实施例中，通过因特网内容适配协议ICAP客户端和ICAP服务器的配合，ICAP服务器可根据ICAP客户端发送的数据缓存请求返回对应的需要缓存的业务数据，使得ICAP客户端将接收到的业务数据进行缓存，用于ICAP业务查询时优先查找并使用，由于ICAP服务器已经提前将业务数据发送至ICAP客户端预先存储好了，如果有匹配的可直接使用，加快了业务数据的获取速度，提高了业务响应的速度。

Claims (14)

  1. 一种基于因特网内容适配协议的数据处理方法，所述方法包括：
    向因特网内容适配协议ICAP服务器发送数据缓存请求，所述数据缓存请求包括缓存数据说明字段，以使所述ICAP服务器根据所述数据缓存请求返回对应的缓存响应，所述缓存响应包括缓存数据响应说明字段和业务数据；
    根据所述缓存数据响应说明字段将所述业务数据保存在本地缓存。
  2. 根据权利要求1所述的方法，其中，所述向ICAP服务器发送数据缓存请求的步骤之前，还包括：
    向ICAP服务器发送选项查询请求，所述选项查询请求包括客户端缓存数据支持字段，以使所述ICAP服务器根据所述客户端缓存数据支持字段返回选项查询响应，所述选项查询响应包括服务器缓存数据能力字段。
  3. 根据权利要求1所述的方法，其中，所述数据缓存请求为定制的数据缓存请求消息或复用ICAP协议的请求消息，所述缓存响应为定制的缓存响应消息或复用ICAP协议的响应消息，所述数据缓存请求与缓存响应的消息类型一致。
  4. 根据权利要求1所述的方法，其中，所述缓存数据说明字段包括业务数据请求记录数字段和业务数据索引字段，所述缓存数据响应说明字段包括业务数据响应记录数字段。
  5. 根据权利要求1至4任一项所述的方法，其中，所述缓存数据响应说明字段还包括业务数据结束标志字段，所述根据所述缓存数据响应说明字段将所述业务数据保存在本地缓存的步骤之后还包括：
    如果所述业务数据结束标志字段为继续数据缓存，则向ICAP服务器继续发送数据缓存请求。
  6. 根据权利要求1所述的方法，其中，还包括：
    接收ICAP业务查询请求；
    在所述本地缓存查找所述ICAP业务查询请求匹配的业务数据并直接使用。
  7. 一种基于因特网内容适配协议的数据处理方法，所述方法包括：
    接收因特网内容适配协议ICAP客户端发送的数据缓存请求，所述数据缓存请求包括缓存数据说明字段；
    根据所述数据缓存请求获取对应的业务数据，返回对应的缓存响应，所述缓存响应包括缓存数据响应说明字段和所述业务数据，以使所述ICAP客户端根据所述缓存数据响应说明字段将所述业务数据保存在本地缓存。
  8. 根据权利要求7所述的方法，其中，所述接收ICAP客户端发送的数据缓存请求的步骤之前，还包括：
    接收ICAP客户端发送的选项查询请求，所述选项查询请求包括客户端缓存数据支持字段，根据所述客户端缓存数据支持字段返回选项查询响应，所述选项查询响应包括服务器缓存数据能力字段。
  9. 根据权利要求7所述的方法，其中，所述数据缓存请求为定制的数据缓存请求消息或复用ICAP协议的请求消息，所述缓存响应为定制的缓存响应消息或复用ICAP协议的响应消息，所述数据缓存请求与缓存响应的消息类型一致。
  10. 根据权利要求7所述的方法，其中，所述缓存数据说明字段包括业务数据请求记录数字段和业务数据索引字段，所述缓存数据响应说明字段包括业务数据响应记录数字段。
  11. 根据权利要求7至10任一项所述的方法，其中，所述缓存数据响应说明字段还包括业务数据结束标志字段，所述方法还包括：
    判断向ICAP客户端发送的业务数据是否发送完毕，如果没有发送完毕，则所述业务数据结束标志字段为继续数据缓存，否则所述业务数据结束标志字段为结束数据缓存。
  12. 一种基于因特网内容适配协议的数据处理装置，所述装置包括：
    数据缓存请求发送模块，设置为向因特网内容适配协议ICAP服务器发送数据缓存请求，所述数据缓存请求包括缓存数据说明字段，以使所述ICAP服务器根据所述数据缓存请求返回对应的缓存响应，所述缓存响应包括缓存数据响应说明字段和业务数据；
    缓存模块，设置为根据所述缓存数据响应说明字段将所述业务数据保存在本地缓存。
  13. 一种基于因特网内容适配协议的数据处理装置，所述装置包括：
    接收模块，设置为接收因特网内容适配协议ICAP客户端发送的数据缓存请求，所述数据缓存请求包括缓存数据说明字段；
    响应模块，设置为根据所述数据缓存请求获取对应的业务数据，返回对应的缓存响应，所述缓存响应包括缓存数据响应说明字段和所述业务数据，以使所述ICAP客户端根据所述缓存数据响应说明字段将所述业务数据保存在本地缓存。
  14. 一种基于因特网内容适配协议的数据处理系统，所述系统包括：
    ICAP客户端，设置为向因特网内容适配协议ICAP服务器发送数据缓存请求，所述数据缓存请求包括缓存数据说明字段；
    ICAP服务器，设置为接收ICAP客户端发送的数据缓存请求，根据所述数据缓存请求获取对应的业务数据，返回对应的缓存响应，所述缓存响应包括缓存数据响应说明字段和所述业务数据；
    所述ICAP客户端还设置为根据所述缓存数据响应说明字段将所述业务数据保存在本地缓存。
PCT/CN2016/101587 2015-12-08 2016-10-09 基于因特网内容适配协议的数据处理方法、装置和系统 WO2017097027A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510904001.3A CN106856494A (zh) 2015-12-08 2015-12-08 基于因特网内容适配协议的数据处理方法、装置和系统
CN201510904001.3 2015-12-08

Publications (1)

Publication Number Publication Date
WO2017097027A1 true WO2017097027A1 (zh) 2017-06-15

Family

ID=59012710

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/101587 WO2017097027A1 (zh) 2015-12-08 2016-10-09 基于因特网内容适配协议的数据处理方法、装置和系统

Country Status (2)

Country Link
CN (1) CN106856494A (zh)
WO (1) WO2017097027A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113079152A (zh) * 2021-03-26 2021-07-06 山东英信计算机技术有限公司 一种数据传输方法、装置及介质
WO2023185454A1 (zh) * 2022-03-28 2023-10-05 华为技术有限公司 一种数据访问方法及相关装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101478575A (zh) * 2009-01-22 2009-07-08 中兴通讯股份有限公司 基于互联网内容修改协议的wap网关开发系统及方法
US7647417B1 (en) * 2006-03-15 2010-01-12 Netapp, Inc. Object cacheability with ICAP
CN103581144A (zh) * 2012-08-06 2014-02-12 无锡稳捷网络技术有限公司 基于icap协议的网络安全访问控制方法
CN103685377A (zh) * 2012-09-11 2014-03-26 中国移动通信集团公司 一种web优化加速方法和系统
CN104541262A (zh) * 2012-06-29 2015-04-22 茨特里克斯系统公司 用于富因特网应用的透明网络内适配的系统和方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7647417B1 (en) * 2006-03-15 2010-01-12 Netapp, Inc. Object cacheability with ICAP
CN101478575A (zh) * 2009-01-22 2009-07-08 中兴通讯股份有限公司 基于互联网内容修改协议的wap网关开发系统及方法
CN104541262A (zh) * 2012-06-29 2015-04-22 茨特里克斯系统公司 用于富因特网应用的透明网络内适配的系统和方法
CN103581144A (zh) * 2012-08-06 2014-02-12 无锡稳捷网络技术有限公司 基于icap协议的网络安全访问控制方法
CN103685377A (zh) * 2012-09-11 2014-03-26 中国移动通信集团公司 一种web优化加速方法和系统

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113079152A (zh) * 2021-03-26 2021-07-06 山东英信计算机技术有限公司 一种数据传输方法、装置及介质
CN113079152B (zh) * 2021-03-26 2023-01-24 山东英信计算机技术有限公司 一种数据传输方法、装置及介质
WO2023185454A1 (zh) * 2022-03-28 2023-10-05 华为技术有限公司 一种数据访问方法及相关装置

Also Published As

Publication number Publication date
CN106856494A (zh) 2017-06-16

Similar Documents

Publication Publication Date Title
WO2016023357A1 (zh) 访问网页的方法、装置及路由器
US10630757B2 (en) Application sharing method and apparatus
KR101827412B1 (ko) 사용자 디바이스 상에 설치된 다수의 애플리케이션으로 보내지는 통지들을 관리하는 방법, 시스템, 및 매체
WO2018184491A1 (zh) 资源获取方法、装置及系统
AU2012242421B2 (en) Data acquisition method, device and system
CN106534243B (zh) 基于http协议的缓存、请求、响应方法及相应装置
US10110507B2 (en) Push-based transmission of resources and correlated network quality estimation
US8838725B2 (en) Internet cache subscription for wireless mobile users
US9906595B2 (en) Content source discovery
CN107332908B (zh) 一种数据传输方法及其系统
US9954815B2 (en) Domain name collaboration service using domain name dependency server
WO2017063533A1 (zh) 服务账号关联方法、装置、系统及终端设备
CN106453460B (zh) 一种文件分发方法、装置和系统
JP2019503008A (ja) マルチメディアリソースの再生システム、方法及びサーバ
CN105340243B (zh) 用于检测数字媒体设备存在于网络上的方法、系统和介质
RU2738447C1 (ru) Способ кэширования видео и устройство кэширования видео
WO2017166524A1 (zh) 域名解析方法及装置
WO2017097027A1 (zh) 基于因特网内容适配协议的数据处理方法、装置和系统
WO2019196225A1 (zh) 一种反馈资源文件的方法和装置
WO2019019382A1 (zh) 缓存处理方法、装置、计算机设备和存储介质
US11144611B2 (en) Data processing method and apparatus
CN113839982A (zh) 调度方法、装置、调度服务器、边缘服务器及调度系统
WO2018090315A1 (zh) 数据请求的处理方法及缓存系统
CN104378280B (zh) 消息发送和接收方法、服务器、客户端和系统
WO2016106557A1 (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: 16872221

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16872221

Country of ref document: EP

Kind code of ref document: A1