WO2017101346A1 - 客户端数据更新方法、客户端和服务器 - Google Patents

客户端数据更新方法、客户端和服务器 Download PDF

Info

Publication number
WO2017101346A1
WO2017101346A1 PCT/CN2016/088687 CN2016088687W WO2017101346A1 WO 2017101346 A1 WO2017101346 A1 WO 2017101346A1 CN 2016088687 W CN2016088687 W CN 2016088687W WO 2017101346 A1 WO2017101346 A1 WO 2017101346A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
time
request
update
client
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2016/088687
Other languages
English (en)
French (fr)
Inventor
江丹
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Le Holdings Beijing Co Ltd
Lemobile Information Technology (Beijing) Co Ltd
Original Assignee
Le Holdings Beijing Co Ltd
Lemobile Information Technology (Beijing) Co Ltd
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 Le Holdings Beijing Co Ltd, Lemobile Information Technology (Beijing) Co Ltd filed Critical Le Holdings Beijing Co Ltd
Priority to US15/243,781 priority Critical patent/US20170171082A1/en
Publication of WO2017101346A1 publication Critical patent/WO2017101346A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0823—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability
    • H04L41/0826—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability for reduction of network costs
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0823—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability
    • H04L41/0833—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability for reduction of network energy consumption
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/20—Traffic policing

Definitions

  • the embodiments of the present application relate to Internet application technologies, for example, to a client data update method, a method for updating client data, a client, and a server.
  • the functions of intelligent terminals are more and more powerful, and the corresponding application software (Application, APP) is installed as a client on the smart terminal.
  • the client of the application software usually needs to exchange information with the corresponding server, that is, the client sends an API request to the server through an application programming interface (API) to obtain the result of the request from the server, and parses the data in the result of the request, so as to Update the data in the client.
  • API application programming interface
  • the Yellow Pages application software needs to obtain the contact data of each enterprise or individual from the server in time, and update the data of the Yellow Page application client in real time.
  • the client After the client sends an API request to the server and obtains the result of the request, if the data of the server has not been updated, the data in the result of the request is the same as the data obtained in the previous request, and the request not only consumes the terminal traffic but also increases the number of times. The burden on the server.
  • the related art provides a solution that, when the client sends an API request to the server, the server determines whether the data of the current API request and the last API request has changed, and if there is no change, the duplicate data is not returned. To the client.
  • the technical solution provided by the related art saves the amount of data transmitted by the network when the server returns data to the client, reduces the consumption of the terminal traffic, and improves the consumption.
  • the speed of the client API request however, the client still needs to issue API requests to the server frequently, so the number of network transmissions is not reduced, and the burden on the server is not alleviated.
  • the embodiment of the present application provides a client data update method, a method for updating client data, a client, and a server, which reduces network transmission times and relieves server load.
  • an embodiment of the present application provides a client data update method, where the method includes:
  • the embodiment of the present application further provides a method for updating client data, where the method includes:
  • the embodiment of the present application further provides a client that implements a client data update method, where the client includes:
  • a time limit acquisition module configured to obtain a request release time returned by the access server according to the data update request
  • the update request control module is configured to control a time when the data update request is subsequently sent to the access server according to the request limit time.
  • the embodiment of the present application further provides a server for implementing a method for updating client data, where the server includes:
  • An update request receiving module configured to receive a data update request sent by the client
  • a time limit determining module configured to determine a request limit time of the client according to an update rule of the data requested by the data update request
  • the time limit sending module is configured to return the request limit time to the client, so that the client controls a time for subsequently sending a data update request.
  • the embodiment of the present application further provides a non-volatile computer storage medium storing computer executable instructions for performing the client data update method of any of the above-mentioned embodiments of the present application.
  • the embodiment of the present application further provides a non-volatile computer storage medium, where computer executable instructions are stored, and the computer executable instructions are used to perform the update of any of the foregoing The method of client data.
  • the present invention provides a client data update method, a method for updating client data, a client and a server, and the client obtains a request release time returned by the access server according to the data update request, and then controls the subsequent direction according to the request limit time.
  • the client controls the sending time of the data update request by requesting the time limit, and intercepts the unnecessary data update request on the client according to the request limiting time, so that the client reduces the number of times the request is sent to the access server, and correspondingly reduces The number of times the access server transmits data to the client, reducing the number of network transmissions, alleviating the burden on the access server, saving the amount of transmitted data and network overhead.
  • FIG. 1 is a flowchart of a client data update method according to a first embodiment of the present application
  • FIG. 2 is a flowchart of a client data update method according to a second embodiment of the present application.
  • FIG. 3 is a flowchart of a client data update method according to a third embodiment of the present application.
  • FIG. 4 is a flowchart of a method for updating client data according to a fourth embodiment of the present application.
  • FIG. 5A is a schematic diagram 1 of a client for implementing a client data update method according to a fifth embodiment of the present application.
  • FIG. 5B is a schematic diagram 2 of a client for implementing a client data update method according to a fifth embodiment of the present application.
  • 6A is a first schematic diagram of a server for implementing a method for updating client data according to a sixth embodiment of the present application
  • 6B is a second schematic diagram of a server for implementing a method for updating client data according to a sixth embodiment of the present application
  • FIG. 7 is a schematic structural diagram of hardware of a device for performing client data update according to a ninth embodiment of the present application.
  • FIG. 8 is a schematic diagram of a hardware structure of an apparatus for performing a method of updating client data according to a tenth embodiment of the present application.
  • FIG. 1 is a flowchart of a client data update method provided by a first embodiment of the present application
  • the technical solution of this embodiment is applicable to a time when a client controls a data update request sent to an access server to intercept unnecessary
  • the method is performed by the client and the client is configured in the smart terminal.
  • the client sends a data update request
  • the access server is configured to receive the data update request sent by the client and provide a request limit time to the client according to the data update request.
  • the request limiting time is a time determined by the access server to limit the sending of the subsequent data update request of the client, and the client controls the sending of the subsequent data update request according to the request limiting time.
  • the request limit time corresponding to different data update requests may be different.
  • the subsequent data update request is an issued data update request after the data update request in this step.
  • the client after the client sends the data update request, the client obtains the request limiting time returned by the access server according to the data update request, so as to control the request limiting time as the basis for controlling the sending time of the subsequent data update request.
  • the client obtains the request limiting time
  • the known request limiting time is the time that the access server determines to limit the sending of the subsequent data update request of the client, and the client may determine that the sending time does not exceed the request limiting time.
  • the data update request is an unnecessary data update request for the client.
  • the client controls that the data update request generated during the requesting time limit is not issued, that is, the subsequent control is controlled.
  • the time for accessing the data update request sent by the server is greater than the request limit time, thereby realizing the interception of the unnecessary data update request by the client and controlling the sending time of the subsequent data update request, reducing the client sending the request to the access server. frequency.
  • the client When the client detection is greater than the request limit time, the client generates a data update request, the client sends the data update request to the access server, and obtains the access server to return a new request limit time according to the data update request, and then according to the new The request limit time controls the time when a subsequent data update request is sent to the access server.
  • the client controls the time when the data update request is subsequently sent to the access server according to the request limit time, and intercepts the unnecessary data update request.
  • the obtained request limit time can also be applied to limit the transmission of multiple data update requests.
  • the currently obtained request limit time can be used to control the request to be sent within a subsequent period of time or a set number of times.
  • the client data update method provided by the first embodiment of the present application, the client obtains the request limiting time returned by the access server according to the data update request, and then controls the time for sending the data update request to the access server according to the request limiting time. .
  • the client controls the sending time of the data update request by requesting the time limit, and implements the interception of the unnecessary data update request on the client according to the request limiting time, so that the client reduces the number of times the request is sent to the access server.
  • the number of times the access server transmits data to the client is reduced, the number of network transmissions is reduced, the burden on the access server is alleviated, and the amount of transmitted data and network overhead are saved.
  • FIG. 2 is a flowchart of a client data update method provided by a second embodiment of the present application
  • the technical solution of this embodiment is applicable to a time when a client controls a data update request sent to an access server to intercept an unnecessary
  • the method is performed by the client and the client is configured in the smart terminal.
  • the request limiting time is the first request limiting time, and the first request limiting time is one time point.
  • the client generates a data update request to be sent according to an update instruction input by the user and simultaneously acquires a current generation time of the data update request to be transmitted.
  • the current generation time is used as a comparison factor to compare with the first request limiting time, and the client determines whether it can be sent to the access server.
  • the data update request can be saved according to the update instruction of the user. If the network overhead is not considered, the client in this application can also actively generate an update request periodically or according to the rules.
  • S230 Determine whether the current generation time is less than or equal to the first request limiting time, and if the current generation time is less than or equal to the first request limiting time, intercepting the to-be-sent data update request, if the current generation time is greater than the first When the time limit is requested, the data update request to be sent is sent to the access server.
  • the first request limit time is a time defined by the access server, which is essentially the time when the server next updates the data after the previous update of the data. Therefore, before the first request is limited, the access server does not update the data requested by the client, and the client does not need to send a data update request, that is, when it is determined that the current generation time is less than or equal to the first request limit time, The client intercepts the data update request to be sent. After the first request is limited, the access server may update the data requested by the client, and the client may send a data update request, that is, when the current generation time is greater than the first request limit time, the client controls the data to be sent. An update request is issued.
  • the client then controls the time when the data update request is subsequently sent to the access server according to the first request limiting time.
  • the client controls the time when the subsequent data transmission request is subsequently sent according to the request-restricted time that the access server returns the previous time, and intercepts the unnecessary data update request.
  • the client may send the intercepted data update request to the access server when the time of the first request limiting time arrives.
  • the client controls the data update request sent to the access server by first comparing the first request limiting time and the generating time of the data update request to be sent. After the request for the time limit, the data update request generated before the first request limit time is intercepted, which reduces the number of times the request is sent to the access server, and reduces the number of times the access server transmits data to the client, thereby reducing the number of network transmissions. It relieves the burden on the access server and saves the amount of data transferred and network overhead.
  • FIG. 3 is a flowchart of a client data update method provided by a third embodiment of the present application
  • the technical solution of this embodiment is applicable to a time when a client controls a data update request sent to an access server.
  • the method is performed by the client and the client is configured in the smart terminal.
  • the request limiting time is the second request limiting time
  • the second request limiting time is a length of time
  • the update data returned by the access server to the client is the content requested by the client and the last update time of the data of the update data.
  • the last update time of the data refers to the latest update time of the update data in the access server before the return time.
  • the last update time of the data returned by the access server can be in the format of Last-Modified:Tue, 20Oct 2015 18:00:56GMT.
  • S330 Perform local data update according to the update data, and record the last update time of the data, to add the last update time of the data to the subsequent data update request.
  • the client parses the acquired update data and displays it on the page, realizing the local data update of the client.
  • the client then records and caches the parsed update data and the last update time of the data, and adds the last update time of the data to the subsequent data update request for the access server to determine.
  • the format of the last update time of the data added to the subsequent data update request here may be If-Modified-Since:Tue, 20Oct 2015 18:00:56 GMT.
  • the access server returns the last update time of the data of the previous update data
  • the client calculates the difference between the current generation time of the data update request to be sent and the last update time of the data, and the difference is the current generated time distance data.
  • the length of time for the last update time is the length of time for the last update time.
  • the second request limit time is defined by the access server as a length of time, which is substantially the length of time between the last update time of the data returned by the access server and the time of the next update of the data, thereby knowing the length of time
  • the access server does not update the data requested by the client, and the access server updates the data requested by the client when the length of time is exceeded.
  • the client determines that the difference is less than or equal to the time length corresponding to the second request limiting time
  • the client intercepts the to-be-sent data update request, and when the client determines that the difference is greater than the second request limiting time
  • the client sends a data update request to be sent to the access server.
  • the client controls the time when the subsequent data transmission request is sent according to the request-restricted time that the access server returns the previous time, and intercepts the unnecessary data update request.
  • the last update time of the data may also be the time when the access server returns the update data, and the length of time is the length of time between the time when the access server returns the update data and the time when the data is updated next time.
  • a method for updating client data the difference between the last update time of the data calculated by the client and the current generation time of the data update request to be sent is compared with the second request limit time, Controlling the sending time of the data update request sent to the access server, intercepting the data update request generated within the second request limiting time, reducing the number of times the request is sent to the access server, and correspondingly reducing the transmission of the access server to the client.
  • the number of times of data reduces the number of network transmissions, relieves the burden on the access server, and saves the amount of data transferred and network overhead.
  • FIG. 4 is a flowchart of a method for updating client data according to a fourth embodiment of the present application
  • the technical solution in this embodiment is applicable to a situation in which an access server mitigates a burden on an access server by setting a time limit for sending to a client.
  • This method can be performed by the access server.
  • the client is the client that performs the client data update method described in any of the above embodiments, and the client is configured in the smart terminal, and the access server is the client-interacting access described in any of the foregoing embodiments. server.
  • the access server returns the corresponding data according to the data update request.
  • the data update request sent by the client subsequently includes a file whose header is If-Modified-Since, and the access server determines whether the content requested by the client is updated according to the time in the file, and returns the client if the content requested by the client is updated.
  • the requested data does not return the data requested by the client if the content requested by the client is not updated.
  • the access server usually needs to be pulled from the service server, and the rule for the access server to pull data from the service server is usually set to pull data from the service server every X seconds, that is, the update rule.
  • the value of X can be set by an administrative user of the access server, and the access server determines, according to the update rule, that its data is not updated within X seconds after the last time the data was pulled.
  • the access server determines the request limit time of the client according to the update rule, and relieves the burden of the access server by reducing the number of times the client issues the request.
  • the data update rule is used to enable the access server to estimate or determine the time of the next data update, including but not limited to the update rule in this embodiment.
  • the client controls the subsequent time to send the data update request to the access server according to the request limiting time, intercepts the unnecessary data update request, and reduces the client direction. The number of times the server sent the request.
  • the access server When the access server returns the request limit time, it can also return other files to the client, such as the file marked with the Last-Modified attribute, the status code, and if it is determined that the requested data has been updated, the client can also return the request requested by the client. content.
  • step 420 may determine the request limiting time of the client by determining, according to the data requested by the data update request, obtaining the next update time of the data to the service server providing the requested data, to determine A request for a time limit.
  • the access server pulls data from the service server with certain rules, such as timing rule pull or pull according to other rules. Therefore, the access server is known to pull the requested data to the service server for the next pull time.
  • the pull time is the next update time of the requested data, where the next update time is determined by the access server as the first request limit time and returned to the client, and the client performs corresponding operations and control.
  • step 420 can also determine the request of the client in the following manner.
  • Limiting time determining, according to the data requested by the data update request, obtaining the next update time of the data to the service server providing the requested data; and determining the second request limit according to the difference between the next update time of the data and the last update time of the data time.
  • the last update time of the data can be the last updated time of the data, or the current time when the access server obtains the data and returns.
  • the access server may determine the next update time of the data or the next update time of the data from the service server according to the update rule, and the difference between the next update time of the data and the last update time of the data is the second request limit time.
  • the access server determines the time limit for requesting the client by the update rule, and returns the time to the client, so that the client controls the time for sending the data update request according to the request limiting rule.
  • the client intercepts unnecessary data update requests, reduces the number of times the access server processes the request, relieves the burden of accessing the server, and saves the amount of data transferred.
  • FIG. 5 is a schematic diagram of a client that implements a method for updating client data according to a fifth embodiment of the present application.
  • the technical solution of this embodiment is applicable to a time when a client controls a data update request sent to an access server. The situation of updating requests by intercepting unnecessary data.
  • the client is configured to execute the client data update method described in any of the foregoing embodiments, and the client is configured in the smart terminal, and the access server is the access server that performs the method of updating the client data according to any of the foregoing embodiments.
  • the client that implements the client data update method provided by the embodiment includes: a time limit acquisition module 510 and an update request control module 520.
  • the time limit obtaining module 510 is configured to obtain a request limiting time returned by the access server according to the data update request; and the update request control module 520 is configured to control the time for subsequently sending the data update request to the access server according to the request limiting time.
  • the update request control module 520 includes a to-be-sent request generation unit 521 and a first transmission state determination unit 522.
  • the to-be-sent request generating unit 521 is configured to generate a data update request to be sent and obtain a current generation time of the to-be-sent data update request;
  • the first sending state determining unit 522 is configured to determine whether the current generation time is less than or equal to the first request limit. And sending a data update request to be sent to the access server, if the current generation time is greater than the first request limit time, if the current generation time is less than or equal to the first request limit time, request.
  • the yellow page application software on the smart terminal is taken as an example for description, and the client needs To obtain corporate or personal contact data from the access server and update the client's data.
  • the client uses the HyperText Transfer Protocol (HTTP) to request access to the server, which is referred to as an API request.
  • HTTP HyperText Transfer Protocol
  • the return server's return status code is 200
  • the returned content is the update data
  • a Last-Modified attribute is returned.
  • This file is modified at the end of the access service period.
  • the time, time format is Last-Modified: Tue, 20Oct 2015 18:00: 56 GMT, and a first request limit time is returned, the first request limit time identifies the data of the access server for the same API before the time. No change.
  • the client After the client receives the update data and parses and presents the page, the client also caches the parsed update data along with the Last-Modified and the first request limit time.
  • the client determines whether the current generation time T3 of the API request exceeds the first request limit time. If the current generation time T3 does not exceed the first request limit time, the client does not need to make a request to the access server. If the current generation time T3 exceeds the first request limit time, the client sends the API request to the access server, and also transmits an If-Modified-Since header to the access server according to the HTTP protocol, for example, If-Modified-Since :Tue, 20Oct 2015 18:00:56GMT, ask if the data accessed by the server for this API has been updated after this time.
  • the access server checks the Last-Modified. If it is determined that the data requested by the API has not been updated since the last request, the access server directly returns the status code HTTP 304 (Not Changed), and there is no content, which also saves the amount of data transferred. If it is determined that the data requested by the API has been updated since the last request, the corresponding data and file are returned.
  • FIG. 5B is a schematic diagram of a client for implementing a client data update method according to a fifth embodiment of the present application, where the client is configured to execute the client data update method described in any of the foregoing embodiments, and the client The end is configured in the smart terminal, wherein the access server that interacts with the client is the access server that performs the method of updating the client data described in any of the above embodiments.
  • the client, the time limit acquisition module 510 further includes an update data acquisition unit 511 and an update operation execution unit 512.
  • the update data obtaining unit 511 is configured to acquire the update data returned by the access server according to the data update request, and the last update time of the data of the update data, while updating the request limit time returned by the access server according to the data update request;
  • the operation execution unit 512 is set to perform local data update based on the update data, and records the number According to the last update time, the last update time of the data is added to the subsequent data update request.
  • the update request control module 520 may include a to-be-sent request generation unit 523, a time difference calculation unit 524, and a second transmission state determination unit 525.
  • the to-be-sent request generating unit 523 is configured to generate a data update request to be sent and acquire a current generation time of the to-be-sent data update request;
  • the time difference calculation unit 524 is configured to calculate a difference between the current generation time and the last update time of the data.
  • the second transmission status determining unit 525 is configured to determine whether the difference is less than or equal to the length of time corresponding to the second request limiting time, and if the difference is less than or equal to the time length corresponding to the second request limiting time And the data update request to be sent is intercepted, and if the difference is greater than the time length corresponding to the second request limit time, the data update request to be sent is sent to the access server.
  • the difference between the client of FIG. 5B and the client of FIG. 5A is that the request limit time is the second request limit time.
  • the client calculates the time difference between T3 and Last-Modified, and determines whether the difference exceeds the second request limit time. If the difference does not exceed the second request limit time, the client does not need to make a request to the access server. If the difference exceeds the second request limit time, the API request is sent to the access server, and the If-Modified-Since header is also transmitted.
  • the client performs intelligent judgment according to the request-receiving time returned by the access server, so that the client controls the time for sending the data update request to the access server, which greatly reduces the burden of accessing the server and network overhead.
  • FIG. 6 is a schematic diagram of a server for implementing a method for updating client data according to a sixth embodiment of the present application.
  • the technical solution of this embodiment is applicable to an access server by setting a time limit for sending and sending to a client. Alleviate the burden of accessing the server.
  • the server is the access server that performs the method for updating the client data according to any of the foregoing embodiments
  • the client that interacts with the server is the client that executes the client data update method described in any of the foregoing embodiments, and the client Configured in a smart terminal.
  • the server for implementing the method for updating the client data includes: an update request receiving module 610, a time limit time determining module 620, and a time limit time sending module 630.
  • the update request receiving module 610 is configured to receive a data update request sent by the client
  • the limit time determination module 620 is configured to determine a request limit time of the client according to the update rule of the requested data of the data update request
  • the limit time sending module 630 Set to return the request limit time to the client, so that the client controls the time when the data update request is subsequently sent.
  • the time limit determining module 620 includes: a first time limit determining unit 621.
  • the first time limit determining unit 621 is configured to determine, according to the data requested by the data update request, the data to be acquired by the service server that provides the requested data, to determine the time limit for the first request.
  • the yellow page application software on the smart terminal is taken as an example for description
  • the client requests data from the access server
  • the data of the access server is pulled from the service server, so the access server clarifies its own business logic. Update the rules.
  • the access server knows the data of the data requested by the client for the next update time
  • the access server returns the data update time as the first request limit time to the client.
  • the server code changes or the server restarts, the server will re-issue the data.
  • the return process is similar to the process of returning to the first request, which in turn avoids repeatedly sending data to the client, and ensures that the client data can be timely when the server changes. Updated.
  • FIG. 6B is a second schematic diagram of another server for implementing the method for updating client data according to the sixth embodiment of the present application.
  • the server is the access server that performs the method for updating the client data according to any of the foregoing embodiments, and the client that interacts with the server is configured to execute the client data update method described in any of the foregoing embodiments, and the client is configured in the client.
  • the time limit determining module 620 may include: an update time determining unit 622 and a second time limit determining unit 623.
  • the update time determining unit 622 is configured to determine, according to the requested data of the data update request, the data to be acquired by the service server that provides the requested data, and the second update time determining unit 623 is configured to be based on the next update time of the data. The difference between the last update of the data determines the second request limit time.
  • the server of FIG. 6B differs from the server of FIG. 6A in that the request limit time is the second request limit time.
  • the request limit time is the second request limit time.
  • the second request limit time returned by the access server to the client is the difference between the next update time of the data and the last update time of the data, that is, 60 seconds, and also returns the last update time of the data.
  • the client controls the time for subsequent sending of the API request according to the second request limiting time.
  • the last update time of this data can also be defined as the time that the access server returns to the client.
  • the seventh embodiment of the present application provides a non-volatile computer storage medium storing computer executable instructions, which can execute client data in any of the foregoing method embodiments. new method.
  • An eighth embodiment of the present application provides a non-volatile computer storage medium storing computer-executable instructions that can perform the method of updating client data in any of the foregoing method embodiments.
  • FIG. 7 is a schematic diagram of a hardware structure of a device for performing client data update according to a ninth embodiment of the present invention. As shown in FIG. 7, the device includes:
  • processors 710 and memory 720 one processor 710 is taken as an example in FIG.
  • the device may also include an input device 730 and an output device 740.
  • the processor 710, the memory 720, the input device 730, and the output device 740 in the device that executes the client data update method may be connected by a bus or the like, and the bus connection is taken as an example in FIG.
  • the memory 720 is a non-volatile computer readable storage medium, and can be used for storing a non-volatile software program, a non-volatile computer executable program, and a module, as in the client data update method in the embodiment of the present application.
  • Program instructions/modules eg, time-limited time acquisition module 510 and update request control module 520 shown in FIG. 5A.
  • the processor 710 executes various functional applications and data processing of the server by executing non-volatile software programs, instructions, and modules stored in the memory 720, that is, implementing the above-described method embodiment client data update method.
  • the memory 720 can include a storage program area and an storage data area, wherein the storage program area can store an operating system, an application required by at least one function; the storage data area can be stored according to the use of the client that implements the client data update method. Data, etc.
  • memory 720 can include high speed random access memory, and can also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device.
  • memory 720 can optionally include memory remotely located relative to processor 710 that can be connected over a network to a client implementing a client data update method. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
  • Input device 730 can receive input numeric or character information and generate key signal inputs related to user settings and function control of the client implementing the client data update method.
  • Output device 740 A display device such as a display screen may be included.
  • the one or more modules are stored in the memory 720, and when executed by the one or more processors 710, perform a client data update method in any of the above method embodiments.
  • FIG. 8 is a schematic diagram of a hardware structure of a device for performing a method for updating client data according to a tenth embodiment of the present application. As shown in FIG. 8, the device includes:
  • One or more processors 810 and memory 820, one processor 810 is taken as an example in FIG.
  • the device may also include an input device 830 and an output device 840.
  • the processor 810, the memory 820, the input device 830, and the output device 840 in the device performing the method of updating the client data may be connected by a bus or the like, and the bus connection is taken as an example in FIG.
  • the memory 820 can be used for storing a non-volatile software program, a non-volatile computer executable program, and a module, such as a method for updating client data in the embodiment of the present application.
  • the program instructions/modules (for example, the update request receiving module 610, the limit time determination module 620, and the limit time transmission module 630 shown in FIG. 6A).
  • the processor 810 executes various functional applications of the server and data processing by executing non-volatile software programs, instructions, and modules stored in the memory 820, that is, processing methods for implementing the list item operations of the above method embodiments.
  • the memory 820 may include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application required by at least one function; and the storage data area may be stored according to use of a server implementing the method of updating the client data. Data, etc.
  • memory 820 can include high speed random access memory, and can also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device.
  • memory 820 can optionally include memory remotely located relative to processor 810, which can be connected via a network to a server implementing a method of updating client data. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
  • Input device 830 can receive input numeric or character information and generate key signal inputs related to the server implementing the method of updating the client data and function control.
  • the output device 840 can include a display device such as a display screen.
  • the one or more modules are stored in the memory 820, and when executed by the one or more processors 810, perform the method of updating client data in any of the method embodiments described above.
  • the method for updating the client data, the method for updating the client data, the client and the server provided by the embodiment of the present application enable the client to reduce the number of times the request is sent to the access server, and correspondingly reduce the number of times the access server transmits data to the client. , reduce the number of network transmissions, ease the burden on the access server, save the amount of transmitted data and network overhead.

Landscapes

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

Abstract

本申请实施例公开了一种客户端数据更新方法、更新客户端数据的方法、客户端和服务器，该客户端数据更新方法包括：获取访问服务器根据数据更新请求返回的请求限发时间；以及根据请求限发时间控制后续向访问服务器发送数据更新请求的时间。

Description

客户端数据更新方法、客户端和服务器
本申请要求在2015年12月15日提交中国专利局、申请号为201510937920.0、发明名称为“客户端数据更新方法、客户端和服务器”的中国专利申请的优先权，该申请的全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及互联网应用技术，例如涉及一种客户端数据更新方法、更新客户端数据的方法、客户端和服务器。
背景技术
随着科技的发展，智能终端的功能越来越多、越来越强大，相应的各种应用软件(Application，APP)作为客户端安装在智能终端上。应用软件的客户端通常需要和相应的服务器交换信息，即客户端通过应用程序编程接口(Application Programming Interface，API)向服务器发送API请求以从服务器获取请求结果，解析该请求结果中的数据，以对客户端中的数据进行更新。例如，黄页应用软件，需要及时的从服务器获取各企业或个人的联系方式数据，对黄页应用软件客户端的数据进行实时更新。
当客户端向服务器发出API请求并得到请求结果后，若服务器的数据还未更新，则该请求结果中的数据与上一次请求得到的数据相同，此时该请求不仅消耗了终端流量还增加了服务器的负担。
因此，相关技术提供的解决方案是，当客户端向服务器发送API请求后，服务器判断当前API请求与上一次API请求时的数据有没有发生变化，如果没有发生变化，则不将重复的数据返回给客户端。
在实现本申请过程中，发明人发现相关技术中至少存在如下问题：相关技术提供的技术方案，节省了服务器向客户端返回数据时网络传输的数据量，减少了终端流量的消耗，也提高了客户端API请求的速度，但是，客户端仍然需要向服务器频繁地发出API请求，因此网络传输次数并没有减少，服务器的负担也没有得到缓解。
发明内容
本申请实施例提供一种客户端数据更新方法、更新客户端数据的方法、客户端和服务器，减少网络传输次数，缓解服务器负担。
第一方面，本申请实施例提供了一种客户端数据更新方法，该方法包括：
获取访问服务器根据数据更新请求返回的请求限发时间；以及
根据所述请求限发时间控制后续向所述访问服务器发送数据更新请求的时间。
第二方面，本申请实施例还提供了一种更新客户端数据的方法，该方法包括：
接收客户端发送的数据更新请求；
根据所述数据更新请求所请求数据的更新规则确定所述客户端的请求限发时间；以及
向所述客户端返回所述请求限发时间，以使所述客户端控制后续发送数据更新请求的时间。
第三方面，本申请实施例还提供了一种实现客户端数据更新方法的客户端，该客户端包括：
限发时间获取模块，设置为获取访问服务器根据数据更新请求返回的请求限发时间；以及
更新请求控制模块，设置为根据所述请求限发时间控制后续向所述访问服务器发送数据更新请求的时间。
第四方面，本申请实施例还提供了一种实现更新客户端数据方法的服务器，该服务器包括：
更新请求接收模块，设置为接收客户端发送的数据更新请求；
限发时间确定模块，设置为根据所述数据更新请求所请求数据的更新规则确定所述客户端的请求限发时间；以及
限发时间发送模块，设置为向所述客户端返回所述请求限发时间，以使所述客户端控制后续发送数据更新请求的时间。
第五方面，本申请实施例还提供了一种非易失性计算机存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行本申请上述任一项的客户端数据更新方法。
第六方面，本申请实施例还提供了一种非易失性计算机存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行本申请上述任一项的更新 客户端数据的方法。
本申请提供的一种客户端数据更新方法、更新客户端数据的方法、客户端和服务器，客户端获取访问服务器根据数据更新请求返回的请求限发时间，再根据该请求限发时间控制后续向访问服务器发送数据更新请求的时间。本申请中客户端通过请求限发时间控制数据更新请求的发送时间，根据请求限发时间在客户端拦截不必要的数据更新请求，使得客户端减少了向访问服务器发送请求的次数，也相应降低了访问服务器向客户端传输数据的次数，减少网络传输次数、缓解访问服务器负担、节省传输数据量和网络开销。
附图说明
图1是本申请第一实施例提供的客户端数据更新方法的流程图；
图2是本申请第二实施例提供的客户端数据更新方法的流程图；
图3是本申请第三实施例提供的客户端数据更新方法的流程图；
图4是本申请第四实施例提供的更新客户端数据的方法的流程图；
图5A是本申请第五实施例提供的一种实现客户端数据更新方法的客户端的示意图一；
图5B是本申请第五实施例提供的一种实现客户端数据更新方法的客户端的示意图二；
图6A是本申请第六实施例提供的一种实现更新客户端数据方法的服务器的示意图一；
图6B是本申请第六实施例提供的一种实现更新客户端数据方法的服务器的示意图二；
图7是本申请第九实施例提供的执行客户端数据更新方法的设备的硬件结构示意图；以及
图8是本申请第十实施例提供的执行更新客户端数据的方法的设备的硬件结构示意图。
具体实施方式
为使本申请的目的、技术方案和优点更加清楚，以下将参照本申请实施例中的附图，通过实施方式清楚、完整地描述本申请的技术方案，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。
如图1所示，为本申请第一实施例提供的客户端数据更新方法的流程图，本实施例的技术方案适用于客户端控制发向访问服务器的数据更新请求的时间以拦截不必要的数据更新请求的情况，该方法由客户端来执行且该客户端配置在智能终端中。
本实施例提供的一种客户端数据更新方法，包括如下步骤：
S110、获取访问服务器根据数据更新请求返回的请求限发时间。
如上所述，客户端发送一个数据更新请求，访问服务器用于接收客户端发送的该数据更新请求并根据该数据更新请求向该客户端提供一个请求限发时间。请求限发时间是访问服务器确定的限制该客户端后续数据更新请求发送的时间，客户端根据该请求限发时间控制后续数据更新请求的发送。访问服务器接收客户端发送的不同数据更新请求时，不同数据更新请求对应的请求限发时间可能不同。后续数据更新请求为该步骤中的数据更新请求之后的发出的数据更新请求。
上述操作中，客户端在发出数据更新请求后，获取到访问服务器根据该数据更新请求返回的请求限发时间，以将该请求限发时间作为控制后续数据更新请求发送时间的依据。
S120、根据请求限发时间控制后续向访问服务器发送数据更新请求的时间。
如上所述，客户端获取请求限发时间，已知请求限发时间是访问服务器确定的限制该客户端后续数据更新请求发送的时间，那么客户端可确定，发送时间不超出该请求限发时间的数据更新请求为客户端的不必要的数据更新请求。此时客户端控制在请求限发时间内产生的数据更新请求不发出，即控制后续向 访问服务器发出的数据更新请求的时间大于请求限发时间，由此实现了客户端对不必要的数据更新请求的拦截和控制后续数据更新请求的发送时间，减少了客户端向访问服务器发送请求的次数。
当客户端检测大于请求限发时间时，客户端产生了数据更新请求，客户端向访问服务器发送该数据更新请求，并获取访问服务器根据该数据更新请求返回新的请求限发时间，再根据新的请求限发时间控制后续向访问服务器发送数据更新请求的时间。由此循环步骤S110～S120，客户端根据请求限发时间控制后续向访问服务器发送数据更新请求的时间，对不必要的数据更新请求进行拦截。或者，获取的一个请求限发时间也可以适用于限制多次数据更新请求的发送。例如，当前获取的请求限发时间，可用于控制后续一段时间内，或设定次数的请求发送。
本申请第一实施例提供的一种客户端数据更新方法，客户端获取访问服务器根据数据更新请求返回的请求限发时间，再根据该请求限发时间控制后续向访问服务器发送数据更新请求的时间。本申请实施例中客户端通过请求限发时间控制数据更新请求的发送时间，实现了根据请求限发时间在客户端拦截不必要的数据更新请求，使得客户端减少了向访问服务器发送请求的次数，也相应降低了访问服务器向客户端传输数据的次数，减少网络传输次数，缓解访问服务器负担，节省传输数据量和网络开销。
如图2所示，为本申请第二实施例提供的客户端数据更新方法的流程图，本实施例的技术方案适用于客户端控制发向访问服务器的数据更新请求的时间以拦截不必要的数据更新请求的情况，该方法由客户端来执行且该客户端配置在智能终端中。
本实施例提供的一种客户端数据更新方法，包括如下步骤：
S210、获取访问服务器根据数据更新请求返回的请求限发时间。
上述操作中，请求限发时间为第一请求限发时间，第一请求限发时间为一个时间点。
S220、产生待发送数据更新请求并获取该待发送数据更新请求的当前产生时间。
如上所述，客户端根据用户输入的更新指令产生待发送数据更新请求并同时获取该待发送数据更新请求的当前产生时间。该当前产生时间用于作为比较因子与第一请求限发时间比较，客户端以此判断是否可向访问服务器发出。根据用户的更新指令产生数据更新请求可以节省网络开销，若不考虑网络开销，则本申请中客户端也可定时或按照规则主动产生更新请求。
S230、判断当前产生时间是否小于或等于第一请求限发时间，若所述当前产生时间小于或等于第一请求限发时间，则拦截待发送数据更新请求，若所述当前产生时间大于第一请求限发时间，则向访问服务器发送待发送数据更新请求。
如上所述，已知第一请求限发时间为访问服务器定义的一个时刻，实质为在前次更新数据之后，访问服务器下一次更新数据的时间。由此可知，第一请求限发时间之前，访问服务器不会更新客户端所请求的数据，客户端无需发送数据更新请求，即当判定该当前产生时间小于或等于第一请求限发时间时，客户端拦截该待发送数据更新请求。第一请求限发时间之后，访问服务器可能更新客户端所请求的数据，客户端可发送数据更新请求，即当判定该当前产生时间大于第一请求限发时间时，客户端控制该待发送数据更新请求发出。由此客户端根据第一请求限发时间控制后续向访问服务器发送数据更新请求的时间。循环步骤S210～S230，客户端根据访问服务器前次返回的请求限发时间控制后续发送数据更新请求的时间，对不必要的数据更新请求进行拦截。可选地，客户端可以在第一请求限发时间的时刻到达时，将拦截的数据更新请求发送至访问服务器。
本申请第二实施例二提供的一种客户端数据更新方法，客户端通过比较第一请求限发时间和待发送数据更新请求的产生时间，控制发向访问服务器的数据更新请求产生于第一请求限发时间之后，拦截产生于第一请求限发时间之前的数据更新请求，减少了向访问服务器发送请求的次数，也相应降低了访问服务器向客户端传输数据的次数，减少了网络传输次数、缓解了访问服务器负担、节省了传输数据量和网络开销。
如图3所示，为本申请第三实施例提供的客户端数据更新方法的流程图，本实施例的技术方案适用于客户端控制发向访问服务器的数据更新请求的时间 以拦截不必要的数据更新请求的情况，该方法由客户端来执行且该客户端配置在智能终端中。
本实施例提供的一种客户端数据更新方法，包括如下步骤：
S310、获取访问服务器根据数据更新请求返回的请求限发时间。
上述操作中，请求限发时间为第二请求限发时间，第二请求限发时间为一个时间长度。
S320、获取访问服务器根据数据更新请求返回的请求限发时间的同时，还获取访问服务器根据该数据更新请求返回的更新数据，以及该更新数据的数据最后更新时间。
如上所述，访问服务器向客户端返回的更新数据为客户端请求的内容以及该更新数据的数据最后更新时间。在此，该数据最后更新时间是指访问服务器中该更新数据在返回时间之前最近的一次更新时间。在此，访问服务器返回的数据最后更新时间的格式可以为Last-Modified：Tue，20Oct 2015 18：00：56GMT。
S330、根据更新数据进行本地数据更新，并记录数据最后更新时间，以将数据最后更新时间添加至后续数据更新请求中。
如上所述，客户端对获取到的该更新数据进行解析再显示在页面中，实现了客户端的本地数据更新。随后客户端对解析后的更新数据和数据最后更新时间进行记录和缓存，并将该数据最后更新时间添加在后续数据更新请求中，以供访问服务器判断。在此添加至后续数据更新请求中的数据最后更新时间的格式可以为If-Modified-Since：Tue，20Oct 2015 18：00：56GMT。
S340、产生待发送数据更新请求并获取该待发送数据更新请求的当前产生时间。
S350、计算当前产生时间与数据最后更新时间之间的差值。
如上所述，访问服务器返回了前次更新数据的数据最后更新时间，则客户端计算待发送数据更新请求的当前产生时间与数据最后更新时间的差值，该差值为该当前产生时间距离数据最后更新时间的时间长度。
S360、判断差值是否小于或等于第二请求限发时间所对应的时间长度，若所述差值小于或等于第二请求限发时间所对应的时间长度，则拦截待发送数据更新请求，若所述差值大于第二请求限发时间所对应的时间长度，则向访问服 务器发送待发送数据更新请求。
如上所述，已知第二请求限发时间被访问服务器定义为一个时间长度，实质为访问服务器返回的数据最后更新时间和下一次更新数据的时间之间的时间长度，由此可知该时间长度之内访问服务器不会更新客户端所请求的数据，超出该时间长度时访问服务器更新客户端所请求的数据。当客户端判定该差值小于或等于第二请求限发时间所对应的时间长度时，客户端拦截该待发送数据更新请求，当客户端判定该差值大于第二请求限发时间所对应的时间长度时，客户端向访问服务器发送待发送数据更新请求。循环步骤S310～S360，客户端根据访问服务器前次返回的请求限发时间控制后续发送数据更新请求的时间，对不必要的数据更新请求进行拦截。
在该实施例中数据最后更新时间还可以为访问服务器返回更新数据的时间，则时间长度为访问服务器返回更新数据的时间到下一次更新数据的时间之间的时间长度。
本申请第三实施例提供的一种客户端数据更新方法，客户端计算数据最后更新时间和待发送数据更新请求当前产生时间之间的差值，并与第二请求限发时间进行比较，以控制发向访问服务器的数据更新请求的发送时间，拦截了产生于第二请求限发时间之内的数据更新请求，减少了向访问服务器发送请求的次数，也相应降低了访问服务器向客户端传输数据的次数，减少了网络传输次数、缓解了访问服务器负担、节省了传输数据量和网络开销。
如图4所示，为本申请第四实施例提供的更新客户端数据的方法的流程图，本实施例的技术方案适用于访问服务器通过设置发送至客户端的限发时间缓解访问服务器负担的情况，该方法可以由访问服务器执行。其中所述客户端为上述任意实施例所述的执行客户端数据更新方法的客户端且该客户端配置在智能终端中，所述访问服务器为上述任意实施例所述的与客户端交互的访问服务器。
本实施例提供的一种更新客户端数据的方法，包括如下步骤：
S410、接收客户端发送的数据更新请求。
如上所述，客户端首次向访问服务器发送的数据更新请求中没有报头为If-Modified-Since的文件，访问服务器根据该数据更新请求返回相应的数据。客 户端后续发送的数据更新请求中含有报头为If-Modified-Since的文件，访问服务器根据该文件中的时间判断客户端请求的内容是否有更新，若客户端请求的内容有更新则返回客户端请求的数据，若客户端请求的内容没有更新则不返回客户端所请求数据。
S420、根据数据更新请求所请求数据的更新规则确定客户端的请求限发时间。
如上所述，客户端所请求的数据，访问服务器通常需要从业务服务器拉取，访问服务器从业务服务器拉取数据的规则通常设定为每隔X秒从业务服务器拉取数据，即为更新规则，其中，X的数值可以由访问服务器的管理用户设置，访问服务器根据更新规则确定在上次拉取数据之后的X秒内其数据不会被更新。那么相应的，访问服务器根据该更新规则确定客户端的请求限发时间，通过减少客户端发出请求的次数来缓解访问服务器负担。数据更新规则用于使访问服务器能够预估或确定下一个数据更新的时间，数据更新规则包括但不限于本实施例中的更新规则。
S430、向客户端返回请求限发时间，以使客户端控制后续发送数据更新请求的时间。
如上所述，访问服务器向客户端返回请求限发时间后，客户端根据该请求限发时间控制后续向访问服务器发送数据更新请求的时间，拦截了不必要的数据更新请求，降低了客户端向服务器发送请求的次数。
访问服务器在返回请求限发时间时，还可以向客户端返回其他文件，如Last-Modified属性标记的文件、状态码，若确定所请求数据已更新则还可以向客户端返回客户端所请求的内容。
在上述技术方案的基础上，步骤420可通过以下方式确定客户端的请求限发时间：根据数据更新请求所请求数据，确定向提供所请求数据的业务服务器获取数据下次更新时间，以确定为第一请求限发时间。如上所述，访问服务器向业务服务器拉取数据有一定的规则，如定时规则拉取或按照其他规则拉取，因此访问服务器内已知向业务服务器拉取所请求数据的下次拉取时间，该拉取时间即为所请求数据的下次更新时间，在此该下次更新时间被访问服务器确定为第一请求限发时间并返回至客户端，客户端进行相应操作和控制。
在上述技术方案的基础上，步骤420还可通过以下方式确定客户端的请求 限发时间：根据数据更新请求所请求数据，确定向提供所请求数据的业务服务器获取数据下次更新时间；以及根据数据下次更新时间与数据最后更新时间的差值，确定第二请求限发时间。如上所述，数据最后更新时间可以为数据最近一次已更新时间，也可以为访问服务器获取数据并返回的当前时间。访问服务器可根据更新规则确定数据下次更新时间或从业务服务器获取数据下次更新时间，那么数据下次更新时间与数据最后更新时间的差值即为第二请求限发时间。
本申请实施例提供的一种更新客户端数据方法，访问服务器通过更新规则确定客户端的请求限发时间并返回至客户端，以使客户端根据请求限发规则控制后续发送数据更新请求的时间，使得客户端拦截了不必要的数据更新请求，减少了访问服务器处理请求的次数，缓解了访问服务器的负担，也节省了传输数据量。
如图5A所示，为本申请第五实施例提供的一种实现客户端数据更新方法的客户端的示意图一，本实施例的技术方案适用于客户端控制发向访问服务器的数据更新请求的时间以拦截不必要的数据更新请求的情况。该客户端用于执行上述任意实施例所述的客户端数据更新方法且该客户端配置在智能终端中，所述访问服务器为上述任意实施例所述的执行更新客户端数据方法的访问服务器。
本实施例提供的一种实现客户端数据更新方法的客户端，包括：限发时间获取模块510和更新请求控制模块520。
其中，限发时间获取模块510设置为获取访问服务器根据数据更新请求返回的请求限发时间；更新请求控制模块520设置为根据请求限发时间控制后续向访问服务器发送数据更新请求的时间。
可选地，更新请求控制模块520包括：待发送请求产生单元521和第一发送状态判断单元522。其中，待发送请求产生单元521设置为产生待发送数据更新请求并获取该待发送数据更新请求的当前产生时间；第一发送状态判断单元522设置为判断当前产生时间是否小于或等于第一请求限发时间，若所述当前产生时间小于或等于第一请求限发时间，则拦截待发送数据更新请求，若所述当前产生时间大于第一请求限发时间，则向访问服务器发送待发送数据更新请求。
在本实施例中，以智能终端上的黄页应用软件为例进行说明，其客户端需 要从访问服务器获取企业或个人的联系方式数据，并对客户端的数据进行更新。在此客户端通过API采用超文本传输协议(HyperText Transfer Protocol，HTTP)请求访问服务器，简称为API请求。过程如下：
客户端第一次发出一个API请求时，访问服务器的返回状态码为200，返回内容是更新数据，还返回一个Last-Modified(最后被修改)的属性标记此文件在访问服务期最后被修改的时间，时间格式为Last-Modified：Tue，20Oct 2015 18：00：56GMT，以及返回一个第一请求限发时间，该第一请求限发时间标识了访问服务器在该时间之前针对同一个API的数据不发生变化。
客户端接收到更新数据后解析并展现页面，客户端还将解析后的更新数据连同Last-Modified以及第一请求限发时间一起缓存。
当客户端在T3时刻预备发送API请求时，客户端判断该API请求的当前产生时间T3是否超过第一请求限发时间。如果当前产生时间T3未超过第一请求限发时间，则客户端无需向访问服务器发出请求。如果当前产生时间T3超过第一请求限发时间，则客户端向访问服务器发出该API请求，还根据HTTP协议的规定，向访问服务器传送一个If-Modified-Since报头，例如，If-Modified-Since：Tue，20Oct 2015 18：00：56GMT，询问该时间之后访问服务器针对该API的数据是否已更新。
访问服务器检查该Last-Modified，若判定该API请求的数据自上次请求之后未被更新，则访问服务器会直接返回状态码HTTP 304(Not Changed)，无内容，这样也节省了传输数据量。若判定该API请求的数据自上次请求之后被已被更新，则返回相应的数据和文件。
如图5B所示，为本申请第五实施例提供的一种实现客户端数据更新方法的客户端的示意图二，该客户端用于执行上述任意实施例所述的客户端数据更新方法且该客户端配置在智能终端中，其中与客户端交互的访问服务器为上述任意实施例所述的执行更新客户端数据方法的访问服务器。
本实施例提供的一种客户端，限发时间获取模块510还可以包括：更新数据获取单元511和更新操作执行单元512。其中，更新数据获取单元511设置为在获取访问服务器根据数据更新请求返回的请求限发时间的同时，获取访问服务器根据该数据更新请求返回的更新数据，以及该更新数据的数据最后更新时间；更新操作执行单元512设置为根据更新数据进行本地数据更新，并记录数 据最后更新时间，以将数据最后更新时间添加至后续数据更新请求中。
更新请求控制模块520可以包括：待发送请求产生单元523，时间差值计算单元524和第二发送状态判断单元525。其中，待发送请求产生单元523设置为产生待发送数据更新请求并获取该待发送数据更新请求的当前产生时间；时间差值计算单元524设置为计算当前产生时间与数据最后更新时间之间的差值；第二发送状态判断单元525，设置为判断差值是否小于或等于第二请求限发时间所对应的时间长度，若所述差值小于或等于第二请求限发时间所对应的时间长度，则拦截待发送数据更新请求，若所述差值大于第二请求限发时间所对应的时间长度，则向访问服务器发送待发送数据更新请求。
图5B的客户端与图5A的客户端的区别在于，请求限发时间为第二请求限发时间。客户端在T3时刻预备发送API请求时，客户端计算T3与Last-Modified的时间差值，并判断该差值是否超过第二请求限发时间。如果该差值未超过第二请求限发时间，则客户端无需向访问服务器发出请求。如果该差值超过第二请求限发时间，则向访问服务器发出该API请求，还传送If-Modified-Since报头。
在本实施例中客户端会根据访问服务器传回的请求限发时间进行智能判断，使得客户端控制向访问服务器发出数据更新请求的时间，大大减少了访问服务器的负担以及网络开销。
如图6A所示，为本申请第六实施例提供的一种实现更新客户端数据方法的服务器的示意图一，本实施例的技术方案适用于访问服务器通过设置限发时间并发送至客户端以缓解访问服务器负担的情况。其中，所述服务器为上述任意实施例所述的执行更新客户端数据方法的访问服务器，与服务器交互的客户端为上述任意实施例所述的执行客户端数据更新方法的客户端且该客户端配置在智能终端中。
本实施例提供的一种实现更新客户端数据方法的服务器，包括：更新请求接收模块610，限发时间确定模块620和限发时间发送模块630。其中，更新请求接收模块610设置为接收客户端发送的数据更新请求；限发时间确定模块620设置为根据数据更新请求所请求数据的更新规则确定客户端的请求限发时间；限发时间发送模块630设置为向客户端返回请求限发时间，以使客户端控制后续发送数据更新请求的时间。
可选地，限发时间确定模块620包括：第一限发时间确定单元621。其中，第一限发时间确定单元621设置为根据数据更新请求所请求数据，确定向提供所请求数据的业务服务器获取数据下次更新时间，以确定为第一请求限发时间。
在本实施例中，以智能终端上的黄页应用软件为例进行说明，客户端向访问服务器请求数据，而访问服务器的数据则是从业务服务器拉取的，因此访问服务器明确自身的业务逻辑即更新规则。在此访问服务器已知客户端所请求数据的数据下次更新时间，则访问服务器将该数据下次更新时间作为第一请求限发时间返回至客户端。
若服务器代码发生改变或者服务器重启时，服务器会重新发出数据，返回过程与返回第一次请求过程类似，依次避免向客户端重复发出数据，也保证了当服务器有变化时，客户端数据能够及时被更新。
如图6B所示，为本申请第六实施例提供的另一种实现更新客户端数据方法的服务器的示意图二。其中，所述服务器为上述任意实施例所述的执行更新客户端数据方法的访问服务器，与服务器交互的客户端用于执行上述任意实施例所述的客户端数据更新方法且该客户端配置在智能终端中。本实施例提供的一种服务器，限发时间确定模块620可以包括：更新时间确定单元622和第二限发时间确定单元623。其中，更新时间确定单元622设置为根据数据更新请求所请求数据，确定向提供所请求数据的业务服务器获取数据下次更新时间；第二限发时间确定单元623设置为根据数据下次更新时间与数据最后更新的差值，确定第二请求限发时间。
图6B的服务器与图6A的服务器的区别在于，请求限发时间为第二请求限发时间。例如访问服务器当前数据的数据最后更新时间为18：30，数据下次更新时间为18：31，则在该间隔为60秒的时间内访问服务器确定不会更新当前的数据。因此访问服务器返回给客户端的第二请求限发时间为数据下次更新时间与数据最后更新时间的差值，即60秒，以及还返回数据最后更新时间。客户端根据该第二请求限发时间控制后续发送API请求的时间。，在此数据最后更新时间还可以定义为访问服务器返回给客户端的时间。
本申请第七实施例提供了一种非易失性计算机存储介质，存储有计算机可执行指令，该计算机可执行指令可执行上述任意方法实施例中的客户端数据更 新方法。
本申请第八实施例提供了一种非易失性计算机存储介质，存储有计算机可执行指令，该计算机可执行指令可执行上述任意方法实施例中的更新客户端数据的方法。
图7是本申请第九实施例提供的执行客户端数据更新方法的设备的硬件结构示意图，如图7所示，该设备包括：
一个或多个处理器710以及存储器720，图7中以一个处理器710为例。
该设备还可以包括：输入装置730和输出装置740。
执行客户端数据更新方法的设备中的处理器710、存储器720、输入装置730和输出装置740可以通过总线或者其他方式连接，图7中以通过总线连接为例。
存储器720作为一种非易失性计算机可读存储介质，可用于存储非易失性软件程序、非易失性计算机可执行程序以及模块，如本申请实施例中的客户端数据更新方法对应的程序指令/模块(例如，附图5A所示的限时时间获取模块510和更新请求控制模块520)。处理器710通过运行存储在存储器720中的非易失性软件程序、指令以及模块，从而执行服务器的各种功能应用以及数据处理，即实现上述方法实施例客户端数据更新方法。
存储器720可以包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需要的应用程序；存储数据区可存储根据实现客户端数据更新方法的客户端的使用所创建的数据等。此外，存储器720可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。在一些实施例中，存储器720可选包括相对于处理器710远程设置的存储器，这些远程存储器可以通过网络连接至实现客户端数据更新方法的客户端。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
输入装置730可接收输入的数字或字符信息，以及产生与实现客户端数据更新方法的客户端的用户设置以及功能控制有关的键信号输入。输出装置740 可包括显示屏等显示设备。
所述一个或者多个模块存储在所述存储器720中，当被所述一个或者多个处理器710执行时，执行上述任意方法实施例中的客户端数据更新方法。
图8是本申请第十实施例提供的执行更新客户端数据的方法的设备的硬件结构示意图，如图8所示，该设备包括：
一个或多个处理器810以及存储器820，图6中以一个处理器810为例。
该设备还可以包括：输入装置830和输出装置840。
执行更新客户端数据的方法的设备中的处理器810、存储器820、输入装置830和输出装置840可以通过总线或者其他方式连接，图8中以通过总线连接为例。
存储器820作为一种非易失性计算机可读存储介质，可用于存储非易失性软件程序、非易失性计算机可执行程序以及模块，如本申请实施例中的更新客户端数据的方法对应的程序指令/模块(例如，附图6A所示的更新请求接收模块610、限发时间确定模块620和限发时间发送模块630)。处理器810通过运行存储在存储器820中的非易失性软件程序、指令以及模块，从而执行服务器的各种功能应用以及数据处理，即实现上述方法实施例列表项操作的处理方法。
存储器820可以包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需要的应用程序；存储数据区可存储根据实现更新客户端数据方法的服务器的使用所创建的数据等。此外，存储器820可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。在一些实施例中，存储器820可选包括相对于处理器810远程设置的存储器，这些远程存储器可以通过网络连接至实现更新客户端数据方法的服务器。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
输入装置830可接收输入的数字或字符信息，以及产生与实现更新客户端数据方法的服务器以及功能控制有关的键信号输入。输出装置840可包括显示屏等显示设备。
所述一个或者多个模块存储在所述存储器820中，当被所述一个或者多个处理器810执行时，执行上述任意方法实施例中的更新客户端数据的方法。
工业实用性
本申请实施例提供的客户端数据更新方法、更新客户端数据的方法、客户端和服务器，使得客户端减少了向访问服务器发送请求的次数，也相应降低了访问服务器向客户端传输数据的次数，减少网络传输次数、缓解访问服务器负担、节省传输数据量和网络开销。

Claims (17)

  1. 一种客户端数据更新方法，包括：
    获取访问服务器根据数据更新请求返回的请求限发时间；以及
    根据所述请求限发时间控制后续向所述访问服务器发送数据更新请求的时间。
  2. 根据权利要求1所述的方法，其中，根据所述请求限发时间控制后续向所述访问服务器发送数据更新请求的时间包括：
    产生待发送数据更新请求并获取该待发送数据更新请求的当前产生时间；以及
    判断所述当前产生时间是否小于或等于第一请求限发时间，若所述当前产生时间小于或等于第一请求限发时间，则拦截所述待发送数据更新请求，若所述当前产生时间大于第一请求限发时间，则向所述访问服务器发送所述待发送数据更新请求。
  3. 根据权利要求1所述的方法，获取访问服务器根据数据更新请求返回的请求限发时间的同时，还包括：
    获取所述访问服务器根据该数据更新请求返回的更新数据，以及该更新数据的数据最后更新时间。
  4. 根据权利要求3所述的方法，获取所述访问服务器根据该数据更新请求返回的更新数据，以及该更新数据的数据最后更新时间之后，还包括：根据所述更新数据进行本地数据更新，并记录所述数据最后更新时间，以将所述数据最后更新时间添加至后续数据更新请求中。
  5. 根据权利要求4所述的方法，其中，根据所述请求限发时间控制后续向所述访问服务器发送数据更新请求的时间包括：
    产生待发送数据更新请求并获取该待发送数据更新请求的当前产生时间；
    计算所述当前产生时间与所述数据最后更新时间之间的差值；以及
    判断所述差值是否小于或等于第二请求限发时间所对应的时间长度，若所述差值小于或等于第二请求限发时间所对应的时间长度，则拦截所述待发送数据更新请求，若所述差值大于第二请求限发时间所对应的时间长度，则向所述访问服务器发送所述待发送数据更新请求。
  6. 一种更新客户端数据的方法，包括：
    接收客户端发送的数据更新请求；
    根据所述数据更新请求所请求数据的更新规则确定所述客户端的请求限发时间；以及
    向所述客户端返回所述请求限发时间，以使所述客户端控制后续发送数据更新请求的时间。
  7. 根据权利要求6所述的方法，其中，根据所述数据更新请求所请求数据的更新规则确定所述客户端的请求限发时间包括：
    根据所述数据更新请求所请求数据，确定向提供所请求数据的业务服务器获取数据下次更新时间，以确定为第一请求限发时间。
  8. 根据权利要求6所述的方法，其中，根据所述数据更新请求所请求数据的更新规则确定所述客户端的请求限发时间包括：
    根据所述数据更新请求所请求数据，确定向提供所请求数据的业务服务器获取数据下次更新时间；以及
    根据所述数据下次更新时间与数据最后更新时间的差值，确定第二请求限发时间。
  9. 一种实现客户端数据更新方法的客户端，包括：
    限发时间获取模块，设置为获取访问服务器根据数据更新请求返回的请求限发时间；以及
    更新请求控制模块，设置为根据所述请求限发时间控制后续向所述访问服务器发送数据更新请求的时间。
  10. 根据权利要求9所述的客户端，其中，所述更新请求控制模块包括：
    待发送请求产生单元，设置为产生待发送数据更新请求并获取该待发送数据更新请求的当前产生时间；以及
    第一发送状态判断单元，设置为判断所述当前产生时间是否小于或等于第一请求限发时间，若所述当前产生时间小于或等于第一请求限发时间，则拦截所述待发送数据更新请求，若所述当前产生时间大于第一请求限发时间，则向所述访问服务器发送所述待发送数据更新请求。
  11. 根据权利要求9所述的客户端，其中，所述限发时间获取模块还包括：
    更新数据获取单元，设置为在获取访问服务器根据数据更新请求返回的请求限发时间的同时，获取所述访问服务器根据该数据更新请求返回的更新数据，以及该更新数据的数据最后更新时间；以及
    更新操作执行单元，设置为根据所述更新数据进行本地数据更新，并记录所述数据最后更新时间，以将所述数据最后更新时间添加至后续数据更新请求中。
  12. 根据权利要求11所述的客户端，其中，所述更新请求控制模块包括：
    待发送请求产生单元，设置为产生待发送数据更新请求并获取该待发送数据更新请求的当前产生时间；
    时间差值计算单元，设置为计算所述当前产生时间与所述数据最后更新时间之间的差值；以及
    第二发送状态判断单元，设置为判断所述差值是否小于或等于第二请求限发时间所对应的时间长度，若所述差值小于或等于第二请求限发时间所对应的时间长度，则拦截所述待发送数据更新请求，若所述差值大于第二请求限发时间所对应的时间长度，则向所述访问服务器发送所述待发送数据更新请求。
  13. 一种实现更新客户端数据方法的服务器，包括：
    更新请求接收模块，设置为接收客户端发送的数据更新请求；
    限发时间确定模块，设置为根据所述数据更新请求所请求数据的更新规则确定所述客户端的请求限发时间；以及
    限发时间发送模块，设置为向所述客户端返回所述请求限发时间，以使所述客户端控制后续发送数据更新请求的时间。
  14. 根据权利要求13所述的服务器，其中，所述限发时间确定模块包括：
    第一限发时间确定单元，设置为根据所述数据更新请求所请求数据，确定向提供所请求数据的业务服务器获取数据下次更新时间，以确定为第一请求限发时间。
  15. 根据权利要求13所述的服务器，其中，所述限发时间确定模块包括：
    更新时间确定单元，设置为根据所述数据更新请求所请求数据，确定向提供所请求数据的业务服务器获取数据下次更新时间；以及
    第二限发时间确定单元，设置为根据所述数据下次更新时间与数据最后更新时间的差值，确定第二请求限发时间。
  16. 一种非易失性计算机存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行权利要求1-5中的任一项的客户端数据更新方法。
  17. 一种非易失性计算机存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行权利要求6-8中的任一项的更新客户端数据的方法。
PCT/CN2016/088687 2015-12-15 2016-07-05 客户端数据更新方法、客户端和服务器 Ceased WO2017101346A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US15/243,781 US20170171082A1 (en) 2015-12-15 2016-08-22 Method and electronic device for updating client data

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510937920.0A CN105871590A (zh) 2015-12-15 2015-12-15 客户端数据更新方法、客户端和服务器
CN201510937920.0 2015-12-15

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/243,781 Continuation US20170171082A1 (en) 2015-12-15 2016-08-22 Method and electronic device for updating client data

Publications (1)

Publication Number Publication Date
WO2017101346A1 true WO2017101346A1 (zh) 2017-06-22

Family

ID=56623762

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/088687 Ceased WO2017101346A1 (zh) 2015-12-15 2016-07-05 客户端数据更新方法、客户端和服务器

Country Status (2)

Country Link
CN (1) CN105871590A (zh)
WO (1) WO2017101346A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113438227A (zh) * 2021-06-23 2021-09-24 平安普惠企业管理有限公司 重复请求的限流方法、装置、设备及存储介质
CN116723100A (zh) * 2023-07-17 2023-09-08 武汉思普崚技术有限公司 一种网络系统业务变更管理方法、装置、设备及存储介质

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106506558A (zh) * 2016-12-29 2017-03-15 东软集团股份有限公司 消息交互的方法、装置及系统
CN106790603A (zh) * 2016-12-29 2017-05-31 东软集团股份有限公司 消息交互的方法、装置及系统
CN107506380B (zh) * 2017-07-21 2019-03-26 北京金堤科技有限公司 一种更新企业数据的方法及服务器
TWI657676B (zh) * 2017-11-09 2019-04-21 和碩聯合科技股份有限公司 通訊裝置更新系統
CN108366092A (zh) * 2018-01-15 2018-08-03 网易（杭州）网络有限公司 一种web即时数据显示的方法和系统
CN113867996B (zh) * 2021-08-18 2024-09-20 广州方硅信息技术有限公司 数据容灾的处理方法、服务器、直播系统及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1909552A (zh) * 2006-08-15 2007-02-07 华为技术有限公司 一种信息访问方法和系统
CN102594859A (zh) * 2011-12-06 2012-07-18 中兴通讯股份有限公司 一种业务数据的呈现方法、终端、服务器及系统
CN103532920A (zh) * 2012-07-06 2014-01-22 腾讯科技（深圳）有限公司 cookie更新方法以及cookie更新系统
CN104219069A (zh) * 2013-05-30 2014-12-17 腾讯科技（深圳）有限公司 访问频率控制方法、装置及控制系统
CN104394128A (zh) * 2014-11-10 2015-03-04 安磊 一种终端访问服务器的控制方法

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040059781A1 (en) * 2002-09-19 2004-03-25 Nortel Networks Limited Dynamic presence indicators
CN1859329A (zh) * 2006-03-29 2006-11-08 华为技术有限公司 一种呈现信息更新通知方法与系统
CN101499901B (zh) * 2008-02-01 2011-08-17 中国移动通信集团公司 触发终端向移动服务器发起请求的方法、终端及广电服务器
CN101640839A (zh) * 2009-06-16 2010-02-03 深圳市科陆电子科技股份有限公司 WebGIS系统及其客户端上更新终端位置的方法
CN101997706B (zh) * 2009-08-28 2012-07-25 中国移动通信集团公司 定时更新方法及终端、以及数据服务器
CN101800931B (zh) * 2009-12-30 2015-01-07 深圳市凯立德科技股份有限公司 一种群组定位方法和用于群组定位的终端设备
CN102075531B (zh) * 2010-12-27 2013-01-30 北京像素软件科技股份有限公司 一种为客户端传输数据的方法
CN102111455A (zh) * 2011-03-11 2011-06-29 深圳市五巨科技有限公司 一种减少移动终端网络访问时间的方法及系统
CN104184546B (zh) * 2013-05-27 2019-04-02 百度在线网络技术（北京）有限公司 一种移动通信网络中减少报文重传的方法及系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1909552A (zh) * 2006-08-15 2007-02-07 华为技术有限公司 一种信息访问方法和系统
CN102594859A (zh) * 2011-12-06 2012-07-18 中兴通讯股份有限公司 一种业务数据的呈现方法、终端、服务器及系统
CN103532920A (zh) * 2012-07-06 2014-01-22 腾讯科技（深圳）有限公司 cookie更新方法以及cookie更新系统
CN104219069A (zh) * 2013-05-30 2014-12-17 腾讯科技（深圳）有限公司 访问频率控制方法、装置及控制系统
CN104394128A (zh) * 2014-11-10 2015-03-04 安磊 一种终端访问服务器的控制方法

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113438227A (zh) * 2021-06-23 2021-09-24 平安普惠企业管理有限公司 重复请求的限流方法、装置、设备及存储介质
CN113438227B (zh) * 2021-06-23 2024-02-27 平安普惠企业管理有限公司 重复请求的限流方法、装置、设备及存储介质
CN116723100A (zh) * 2023-07-17 2023-09-08 武汉思普崚技术有限公司 一种网络系统业务变更管理方法、装置、设备及存储介质

Also Published As

Publication number Publication date
CN105871590A (zh) 2016-08-17

Similar Documents

Publication Publication Date Title
WO2017101346A1 (zh) 客户端数据更新方法、客户端和服务器
US10397360B2 (en) Systems and methods for caching HTTP POST requests and responses
US9043383B2 (en) Stream processing using a client-server architecture
CN103370917B (zh) 消息处理方法及服务器
US20130073609A1 (en) Mobile resource accelerator
CN108920703B (zh) 一种http缓存优化方法与装置
US8516041B1 (en) Pre-fetching asynchronously requested content
WO2017045538A1 (zh) 基于http协议的缓存、请求、响应方法及相应装置
CN114189559B (zh) 基于Axios的接口重复请求处理方法及系统
WO2017185633A1 (zh) Cdn服务器及其缓存数据的方法
CN103914568A (zh) 调度http代理的方法和装置
CN105354258B (zh) 一种更新网站数据缓存的装置及方法
CN113079210A (zh) 一种跨区数据自动同步的配置方法、终端设备及存储介质
US20170171082A1 (en) Method and electronic device for updating client data
WO2020077765A1 (zh) 网页加载方法、中间服务器和网页加载系统
CN113301050B (zh) 网页页面多用户实时登录登出管理方法、系统、终端及介质
US20150271009A1 (en) Latency virtualization data accelerator
EP3901790A1 (en) Determining method for a common component of pages, server and storage medium
CN104219277A (zh) 重排服务器响应
CN117938506A (zh) 一种访问权限配置策略更新方法、装置、设备及存储介质
CN104168274A (zh) 数据获取请求的处理方法、客户端及服务器
US8595320B2 (en) If-none-match for aggregated page distribution
US20090327404A1 (en) Uncached data control in server-cached page
US9049180B2 (en) Method for providing a signal output on the basis of a main file and at least one secondary file, and motor vehicle
JP5637406B2 (ja) データ送信装置、およびプログラム

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

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

Country of ref document: EP

Kind code of ref document: A1