CN107562901B - Client data updating method and system - Google Patents
Client data updating method and system Download PDFInfo
- Publication number
- CN107562901B CN107562901B CN201710801242.4A CN201710801242A CN107562901B CN 107562901 B CN107562901 B CN 107562901B CN 201710801242 A CN201710801242 A CN 201710801242A CN 107562901 B CN107562901 B CN 107562901B
- Authority
- CN
- China
- Prior art keywords
- data
- client
- keyword
- updating
- server
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 46
- 230000002452 interceptive effect Effects 0.000 claims abstract description 59
- 238000000605 extraction Methods 0.000 claims description 17
- 238000012545 processing Methods 0.000 claims description 17
- 238000012163 sequencing technique Methods 0.000 claims description 2
- 230000009286 beneficial effect Effects 0.000 abstract description 2
- 230000008569 process Effects 0.000 description 9
- 238000010586 diagram Methods 0.000 description 6
- 230000003993 interaction Effects 0.000 description 6
- 230000004044 response Effects 0.000 description 5
- 230000007246 mechanism Effects 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 238000004891 communication Methods 0.000 description 3
- 238000013461 design Methods 0.000 description 2
- 230000006872 improvement Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 230000008901 benefit Effects 0.000 description 1
- 238000001816 cooling Methods 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 238000013523 data management Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 238000013468 resource allocation Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Landscapes
- Information Transfer Between Computers (AREA)
Abstract
The application discloses a method for updating client data, which comprises the following steps: dividing the client data into interactive data and non-interactive data according to selection information input from the outside; generating a linkage stack in the client according to the identification information of the non-interactive data, and sending the identification information contained in the linkage stack to the server; and judging whether the data corresponding to the identification information is updated, if so, pushing the latest data corresponding to the identification information to the linkage stack through a preset path. According to the updating method, the data items which do not need to be interactively displayed are intensively set in the linkage stack in the client, the data identification information contained in the linkage stack is configured at the server, and when the server senses that the data corresponding to the identification information is updated, the data is timely pushed to the linkage stack without receiving an updating request sent by the client, so that the load of the server can be obviously reduced, and the data can be updated more timely. The application also discloses a system for updating the client data, which has the beneficial effects.
Description
Technical Field
The present application relates to the field of data updating technologies, and in particular, to a method and a system for updating client data.
Background
In the process of software development, a request needs to be issued to a server for updating (refreshing) each data of a page, and the server updates the page after processing. In this mechanism, the refreshing of data is performed in such a manner that a process is requested because all data is refreshed regardless of any data type.
In the prior art, a large number of requests are issued to a server by various pages needing to update data, and if the same page requires too much data and too many pages or a plurality of client requests, the server needs to process a large number of issued requests simultaneously, and needs to execute a set of complete processing flow for each issued request one by one.
The page data are classified according to the refreshing mode by using the linkage stack, and for some data which do not depend on user operation and can be refreshed only by issuing a request, the refreshed data are put into the linkage stack. The server side pushes the latest data to the linkage stack according to whether the data is refreshed or not, the linkage stack is pushed to the client side instantly, the client side does not issue a request in the whole process, and the data can be guaranteed to be updated instantly. Thereby reducing server stress.
Therefore, how to provide a client data updating mechanism that classifies according to data types and updates a type of data updating items that do not need interactive display in time without sending refresh requests one by one is a problem that needs to be solved by those skilled in the art.
Disclosure of Invention
The method and the system for updating the client data are characterized in that data items which do not need to be interactively displayed are intensively set in a linkage stack in the client, data identification information contained in the linkage stack is configured at a server, and when the server senses that data corresponding to the identification information are updated, an updating request sent by the client is not needed to be received and is timely pushed to the linkage stack, so that the load of the server can be obviously reduced, and the data can be updated more timely.
In order to solve the above technical problem, the present application provides an update method of client data, where the update method includes:
dividing the client data into interactive data and non-interactive data according to selection information input from the outside;
generating a linkage stack in a client according to the identification information of the non-interactive data, and sending the identification information contained in the linkage stack to a server;
and judging whether the data corresponding to the identification information is updated, if so, pushing the latest data corresponding to the identification information to the linkage stack through a preset path, so that the client does not need to send a request instruction to acquire the latest data.
Optionally, generating a linkage stack in the client according to the identification information of the non-interactive data includes:
performing recognition keyword extraction operation on the non-interactive data according to a preset extraction rule to obtain recognition keywords;
sorting the identification keywords according to a preset sorting rule to obtain a keyword sorting table so as to be convenient for inquiring from the keyword sorting table;
and generating a linkage stack in the client by utilizing the keyword sorting table.
Optionally, the sending the identification information contained in the linkage stack to the server includes:
sending the keyword sorting table to the server through an IP address;
and configuring the received keyword sorting table at a preset position of the server so as to judge whether the data corresponding to the identification keywords are updated.
Optionally, the determining whether the data corresponding to the identification information is updated includes:
acquiring the updating time of the data corresponding to the identification keywords on the server side and the configuration time of the same identification keywords when the keyword sequencing list is configured;
judging whether the updating time is the same as the configuration time;
if not, judging that the data corresponding to the identification key words are updated, and updating the configuration time into the updating time.
Optionally, the updating method further includes:
and after the linkage stack obtains the pushed latest data, generating a data updating log by using the keyword sorting table.
The present application further provides an update system of client data, including:
the data classification unit is used for classifying the client data into interactive data and non-interactive data according to externally input selection information;
the linkage stack processing unit is used for generating a linkage stack in the client according to the identification information of the non-interactive data and sending the identification information contained in the linkage stack to the server;
and the update judging and processing unit is used for judging whether the data corresponding to the identification information is updated or not, and if so, pushing the latest data corresponding to the identification information to the linkage stack through a preset path so that the client does not need to send a request instruction to acquire the latest data.
Optionally, the linkage stack processing unit includes:
the keyword extraction subunit is used for executing identification keyword extraction operation on the non-interactive data according to a preset extraction rule to obtain an identification keyword;
the sorting subunit is used for sorting the identification keywords according to a preset sorting rule to obtain a keyword sorting table so as to be convenient for inquiring from the keyword sorting table;
and the linkage stack generating subunit is used for generating a linkage stack in the client by utilizing the keyword sorting table.
Optionally, the linkage stack processing unit includes:
the sending subunit is configured to send the keyword sorting table to the server through an IP address;
and the configuration subunit is configured to configure the received keyword ranking table at a preset position of the server, so as to determine whether the data corresponding to the identification keyword is updated.
Optionally, the update determining and processing unit includes:
the time acquisition subunit is configured to acquire update time of data corresponding to the identification keyword on the server and configuration time of the same identification keyword when the keyword sorting table is configured;
the time judging subunit is used for judging whether the updating time is the same as the configuration time;
and the updating judgment subunit is used for judging that the data corresponding to the identification keyword is updated and updating the configuration time into the updating time.
Optionally, the update system further includes:
and the log recording unit is used for generating a data updating log by utilizing the keyword sorting table after the linkage stack obtains the pushed latest data.
According to the method for updating the client data, the client data are divided into interactive data and non-interactive data according to selection information input from the outside; generating a linkage stack in a client according to the identification information of the non-interactive data, and sending the identification information contained in the linkage stack to a server; and judging whether the data corresponding to the identification information is updated, if so, pushing the latest data corresponding to the identification information to the linkage stack through a preset path, so that the client does not need to send a request instruction to acquire the latest data.
Obviously, according to the technical scheme provided by the application, the data items which do not need to be interactively displayed are intensively set in the linkage stack in the client, the data identification information contained in the linkage stack is configured at the server, and when the server senses that the data corresponding to the identification information is updated, the data is timely pushed to the linkage stack without receiving an update request sent by the client, so that the load of the server can be obviously reduced, and the data can be updated more timely. The application also provides a system for updating the client data, which has the beneficial effects and is not repeated herein.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a flowchart of a method for updating client data according to an embodiment of the present disclosure;
FIG. 2 is a flowchart of another client data update method provided in an embodiment of the present application;
fig. 3 is a block diagram illustrating a structure of a client data updating system according to an embodiment of the present disclosure;
FIG. 4 is a diagram illustrating a conventional client data update structure;
fig. 5 is a schematic structural diagram of a client data update provided in an embodiment of the present application.
Detailed Description
The core of the application is to provide a method and a system for updating client data, data items which do not need to be interactively displayed are intensively set in a linkage stack in a client, data identification information contained in the linkage stack is configured at a server, and when the server senses that data corresponding to the identification information is updated, an updating request sent by the client is not needed to be received and is timely pushed to the linkage stack, so that the load of the server can be obviously reduced, and the data can be updated more timely.
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Referring to fig. 1, fig. 1 is a flowchart of a method for updating client data according to an embodiment of the present disclosure.
The method specifically comprises the following steps:
s101: dividing the client data into interactive data and non-interactive data according to selection information input from the outside;
this step is intended to divide the client output into interactive data and non-interactive data according to externally input selection information. Therefore, the client data is divided into two categories, interactive data refers to data which requires real-time interaction between a user and the client, namely, data related to interactive actions with obvious personal tendency can be made according to actual conditions, and non-interactive data refers to data which does not require real-time interaction between the user and the client, but the client can also update data.
In the prior art, all data including interactive data and non-interactive data on a client needs to initiate a data update request from the client to a server when updating, and the server sends the latest data to the client according to the update request, that is, follows a handshake principle from one to the next.
This step can be explained by a relatively visual example of the classification here: in a player client display interface of a large game, a player violently operates a game character to complete a task, and a lot of data may exist in the interface at the same time, and may include a skill releasing CD (delay cooling time), a BUG command requested to a server, a server announcement, friend status inquiry information, real-time consignment information and the like. The server bulletin is information which is directly sent by the game server without a request of a player, and is non-interactive data; the friend state information query and the real-time consignment information need to be obtained by a player through extracting a query request from the game server in real time, and the data is the interaction data.
The step aims to screen out non-interactive data of interactive data according to different classifications of client data, and after knowing the definition and the functions of the non-interactive data, certain changes are made for the non-interactive data in subsequent steps so as to achieve the purpose of reducing the load of a server.
There are many ways how to determine whether various data on the client belongs to interactive data or non-interactive data, which is most easily defined by the client user, and may have other characteristics of the data, such as the data type can be determined to some extent in the acquisition mode. If the data type is defined by a user of the client, the user is required to externally configure the selection determination information on the client; if the data type is defined by the data acquisition mode, a judgment analysis algorithm which takes the data acquisition mode as the key point is configured on the client side from the outside. The external selection information is expressed in various forms, and may be selected comprehensively according to the cost requirement, human resource allocation, client processing performance, and other factors.
S102: generating a linkage stack in the client according to the identification information of the non-interactive data, and sending the identification information contained in the linkage stack to the server;
on the basis that the client data is divided into interactive data and non-interactive data in S101, the step is to generate a linkage stack from the identification information of the classified non-interactive data in the client, and send the identification information of the non-interactive data contained in the linkage stack to the server.
The identification information refers to feature information corresponding to all data files belonging to non-interactive data, that is, the corresponding data files can be uniquely located through the identification information, and the representation forms of the identification information are various, for example, a hash Algorithm, an MD5(Message Digest Algorithm, fifth edition) feature value Algorithm, or other ways capable of uniquely identifying the corresponding identification files may be used, and only the corresponding data files need to be found through the identification information. The method comprises the steps of firstly, independently setting respective identification information of all data files belonging to non-interactive data at a certain position in a client to generate a linkage stack, and then sending the identification information contained in the linkage stack to a server so that the server can judge whether updated data exist in the corresponding data files according to the identification information.
Furthermore, the identification information contained in the linkage stack can be sorted according to a certain principle due to the possible large number of data files belonging to the non-interactive data, and a sorting table is further generated for other parts to inquire or use with other special requirements.
In addition, the specific ways of how to generate the linkage stack by using the identification information and how to send the linkage stack to the server are various, for example, a preset position of a register is used, and the preset position is set as a special area; identification information is uploaded through a channel for information communication between a server and a client in the prior art, and the like, so that specific limitations on how to generate a linkage stack and how to send the linkage stack are not required, and the client design mode, the server equipment model, the operating system version and other influence factors can be comprehensively considered according to actual conditions.
S103: judging whether the data corresponding to the identification information is updated or not;
on the basis of S102, this step is intended to determine whether there is an update in the data corresponding to the identification information. Once the latest data exists in the data, the data is uploaded to the server first, so the server updates and judges the latest data according to the identification information of the non-interactive data configured in the server.
Judging whether the latest data exists in various ways, for example, comparing the latest uploading time of the data with the updating time of the last version, and if the latest uploading time is different from the updating time of the last version, judging that the latest data exists in the data file to be updated; the data updating method can also be used for judging whether the latest data to be updated exists or not directly by means of a common updating identifier which represents that the data file is updated, and the like, wherein the method is not limited to judging whether the data corresponding to the identification information is updated or not, and can be comprehensively formulated according to actual conditions by combining various influence factors such as data management habits, setting habits and the like of a server side.
S104: and pushing the latest data corresponding to the identification information to the linkage stack through a preset path so that the client does not need to send a request instruction to acquire the latest data.
On the basis of S103, this step aims to push the latest data corresponding to the identification information to the linkage stack through a preset path, so that the client can obtain the latest data from the server without sending a request instruction. The preset path may be the same as or different from the manner in which the identification information is sent to the server in S102, for example, communication is achieved through an IP address of a server carried by the server, and communication between information may also be achieved through other manners.
Furthermore, when data is updated each time, the specific data file to be updated and the update information including the size, time or form of the updated data and the like can be recorded, and a data update log can be further generated, so that other parts can be conveniently tracked and used.
Based on the technical scheme, the method for updating the client data provided by the embodiment of the application establishes the data items which do not need to be interactively displayed in the client in a centralized manner in the linkage stack, configures the data identification information contained in the linkage stack in the server, and pushes the data items to the linkage stack in time without receiving an updating request sent by the client after the server senses the data corresponding to the identification information is updated, so that the load of the server can be obviously reduced, and the data can be updated more timely.
Referring to fig. 2, fig. 2 is a flowchart of another client data updating method provided in the embodiment of the present application.
The method specifically comprises the following steps:
s201: dividing the client data into interactive data and non-interactive data according to selection information input from the outside;
s202: executing identification keyword extraction operation on the non-interactive data according to a preset extraction rule to obtain an identification keyword;
s203: sorting the identification keywords according to a preset sorting rule to obtain a keyword sorting table so as to be convenient for inquiring from the keyword sorting table;
s204: generating a linkage stack in the client by utilizing the keyword sorting table;
s202, S203 and S204, extracting keywords from the non-interactive data according to a preset extraction rule, then sorting the extracted recognition keywords according to a preset sorting rule, and finally generating a linkage stack in the client by using the generated keyword sorting table. As described in S102, the contents are substantially the same, but a specific manner is used to describe how to sequentially pass through the preset extraction rule and the preset sorting rule, and finally, the generation of the linkage stack containing the non-interactive data identification information is realized.
S205: sending the keyword sorting table to a server through an IP address;
on the basis of S204, in this step, the keyword sorting table is sent from the client to the server through the IP address of the hardware device carried by the server.
S206: configuring the received keyword sorting table at a preset position of a server so as to judge whether data corresponding to the identified keywords are updated or not;
based on S205, this step aims to configure the received keyword sorting table at a preset position of the server, where the preset position is selected according to a principle that the server can call the received keyword sorting table conveniently or meet other special requirements.
S207: acquiring the updating time of data corresponding to the identification keywords on the server and the configuration time of the same identification keywords in the configuration keyword sorting table;
s208: judging whether the updating time is the same as the configuration time;
s209: judging that the data corresponding to the identification keywords are updated, and updating the configuration time into update time;
s207, S208, and S209 determine whether the update is needed by comparing the update time of the data file corresponding to the identification information located on the server with the configuration time, where the configuration time is equal to the previous version update time described in S103.
S210: and pushing the latest data corresponding to the identification information to the linkage stack through a preset path so that the client does not need to send a request instruction to acquire the latest data.
Based on the technical scheme, the method for updating the client data provided by the embodiment of the application establishes the data items which do not need to be interactively displayed in the client in a centralized manner in the linkage stack, configures the data identification information contained in the linkage stack in the server, and pushes the data items to the linkage stack in time without receiving an updating request sent by the client after the server senses the data corresponding to the identification information is updated, so that the load of the server can be obviously reduced, and the data can be updated more timely.
Because the situation is complicated and cannot be illustrated by a list, those skilled in the art can realize that many examples exist based on the principle of the basic method provided by the present application in combination with the actual situation, and the method is within the scope of the present application without sufficient inventive effort.
Referring to fig. 3, fig. 3 is a block diagram illustrating a structure of a client data updating system according to an embodiment of the present disclosure.
The update system may include:
a data classifying unit 100 for classifying the client data into interactive data and non-interactive data according to selection information inputted from the outside;
the linkage stack processing unit 200 is configured to generate a linkage stack in the client according to the identification information of the non-interactive data, and send the identification information included in the linkage stack to the server;
the update determining and processing unit 300 is configured to determine whether data corresponding to the identification information is updated, and if so, push the latest data corresponding to the identification information to the linkage stack through a preset path, so that the client does not need to send a request instruction to obtain the latest data.
Wherein, linkage stack processing unit 200 includes:
the keyword extraction subunit is used for executing identification keyword extraction operation on the non-interactive data according to a preset extraction rule to obtain an identification keyword;
the sorting subunit is used for sorting the identification keywords according to a preset sorting rule to obtain a keyword sorting table so as to be convenient for inquiring from the keyword sorting table;
the linkage stack generating subunit is used for generating a linkage stack in the client by utilizing the keyword sorting table;
the sending subunit is used for sending the keyword sorting table to the server end through the IP address;
and the configuration subunit is used for configuring the received keyword sorting table at a preset position of the server so as to judge whether the data corresponding to the identified keywords are updated.
The update determining and processing unit 300 includes:
the time acquisition subunit is used for acquiring the updating time of the data corresponding to the identification keywords on the server side and the configuration time of the same identification keywords in the configuration keyword sorting table;
the time judging subunit is used for judging whether the updating time is the same as the configuration time;
and the updating judgment subunit is used for judging that the data corresponding to the identification key words are updated and updating the configuration time into the updating time.
Further, the updating system may further include:
and the log recording unit is used for generating a data updating log by using the keyword sorting table after the linkage stack obtains the pushed latest data.
Referring to fig. 4 and 5, fig. 4 is a schematic structural diagram of a conventional client data update; fig. 5 is a schematic structural diagram of a client data update provided in an embodiment of the present application, where the above units may be applied to one specific practical example of the following:
as shown in fig. 4, in the conventional client data refreshing method, a request must be issued to a server when client data wants to obtain a refresh, the server processes the request after obtaining the request, packages the data into a response body and then returns the response body to the client, and the client refreshes the data according to the content of the request response.
As shown in fig. 5, in the method for refreshing data of the client after introducing the linkage stack, when the server updates the data in the linkage stack, the server directly pushes the data into the linkage stack, the linkage stack receives the updated data, and immediately feeds the data back to the client, so that the data can be refreshed. The client side does not request the data in the linkage stack to the server side any more, and the client side does not access the data in the linkage stack but passively receives the notification and the refreshing of the linkage stack.
And classifying the page data of the client, and selecting different mechanisms for updating the data of the page according to the condition that whether the page data needs to be interacted and can be displayed. The data which can be refreshed only by interaction is refreshed by adopting the traditional method of client request and server response, and the data which can be refreshed without interaction is refreshed by adopting a linkage stack mechanism
In the embodiment, a linkage stack mode is adopted to simplify or omit some operations which originally need client requests and server responses, when data of the server is refreshed, the server directly pushes the latest data to the linkage stack, and the linkage stack instantly refreshes the updated data to the client. In the whole process, the client does not need to issue a request, the server can also respond to other requests of the client at the same time, the page data can keep instantaneity, the linkage stack is used, the requests of fewer clients can be reduced, the frequent interaction quantity of the front end and the back end is reduced, the coupling degree of the client and the server is reduced, and the validity and the instantaneity of the data can be ensured. Increasing the performance of the overall system.
The embodiments are described in a progressive manner in the specification, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other. The device disclosed by the embodiment corresponds to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
The principles and embodiments of the present application are explained herein using specific examples, which are provided only to help understand the method and the core idea of the present application. It should be noted that, for those skilled in the art, it is possible to make several improvements and modifications to the present application without departing from the principle of the present application, and such improvements and modifications also fall within the scope of the claims of the present application.
It is further noted that, in the present specification, relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
Claims (8)
1. A method for updating client data, comprising:
dividing the client data into interactive data and non-interactive data according to selection information input from the outside;
generating a linkage stack in a client according to the identification information of the non-interactive data, and sending the identification information contained in the linkage stack to a server;
judging whether the data corresponding to the identification information is updated, if so, pushing the latest data corresponding to the identification information to the linkage stack through a preset path, so that the client does not need to send a request instruction to acquire the latest data;
generating a linkage stack in the client according to the identification information of the non-interactive data, wherein the linkage stack comprises:
performing recognition keyword extraction operation on the non-interactive data according to a preset extraction rule to obtain recognition keywords;
sorting the identification keywords according to a preset sorting rule to obtain a keyword sorting table so as to be convenient for inquiring from the keyword sorting table;
and generating a linkage stack in the client by utilizing the keyword sorting table.
2. The updating method according to claim 1, wherein sending the identification information contained in the linkage stack to a server side comprises:
sending the keyword sorting table to the server through an IP address;
and configuring the received keyword sorting table at a preset position of the server so as to judge whether the data corresponding to the identification keywords are updated.
3. The updating method according to claim 2, wherein determining whether the data corresponding to the identification information is updated comprises:
acquiring the updating time of the data corresponding to the identification keywords on the server side and the configuration time of the same identification keywords when the keyword sequencing list is configured;
judging whether the updating time is the same as the configuration time;
if not, judging that the data corresponding to the identification key words are updated, and updating the configuration time into the updating time.
4. The updating method according to claim 3, further comprising:
and after the linkage stack obtains the pushed latest data, generating a data updating log by using the keyword sorting table.
5. A system for updating client data, comprising:
the data classification unit is used for classifying the client data into interactive data and non-interactive data according to externally input selection information;
the linkage stack processing unit is used for generating a linkage stack in the client according to the identification information of the non-interactive data and sending the identification information contained in the linkage stack to the server;
the updating judgment and processing unit is used for judging whether the data corresponding to the identification information is updated or not, if so, the latest data corresponding to the identification information is pushed to the linkage stack through a preset path, so that the client does not need to send a request instruction to acquire the latest data;
wherein, linkage stack processing unit includes:
the keyword extraction subunit is used for executing identification keyword extraction operation on the non-interactive data according to a preset extraction rule to obtain an identification keyword;
the sorting subunit is used for sorting the identification keywords according to a preset sorting rule to obtain a keyword sorting table so as to be convenient for inquiring from the keyword sorting table;
and the linkage stack generating subunit is used for generating a linkage stack in the client by utilizing the keyword sorting table.
6. The update system of claim 5, wherein the linkage stack processing unit comprises:
the sending subunit is configured to send the keyword sorting table to the server through an IP address;
and the configuration subunit is configured to configure the received keyword ranking table at a preset position of the server, so as to determine whether the data corresponding to the identification keyword is updated.
7. The update system of claim 6, wherein the update determination and processing unit comprises:
the time acquisition subunit is configured to acquire update time of data corresponding to the identification keyword on the server and configuration time of the same identification keyword when the keyword sorting table is configured;
the time judging subunit is used for judging whether the updating time is the same as the configuration time;
and the updating judgment subunit is used for judging that the data corresponding to the identification keyword is updated and updating the configuration time into the updating time.
8. The update system of claim 7, further comprising:
and the log recording unit is used for generating a data updating log by utilizing the keyword sorting table after the linkage stack obtains the pushed latest data.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710801242.4A CN107562901B (en) | 2017-09-07 | 2017-09-07 | Client data updating method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710801242.4A CN107562901B (en) | 2017-09-07 | 2017-09-07 | Client data updating method and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107562901A CN107562901A (en) | 2018-01-09 |
| CN107562901B true CN107562901B (en) | 2021-02-09 |
Family
ID=60979615
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710801242.4A Active CN107562901B (en) | 2017-09-07 | 2017-09-07 | Client data updating method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107562901B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108681872A (en) * | 2018-03-30 | 2018-10-19 | 平安科技（深圳）有限公司 | Variable information update method, device, computer equipment and storage medium |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105635257A (en) * | 2015-12-24 | 2016-06-01 | 福建天泉教育科技有限公司 | Method and system for automatically detecting data update |
| CN106713497A (en) * | 2017-01-24 | 2017-05-24 | 郑州云海信息技术有限公司 | Server-side message push device and method and message push system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9798827B2 (en) * | 2013-10-25 | 2017-10-24 | Uc Mobile Co., Ltd. | Methods and devices for preloading webpages |
-
2017
- 2017-09-07 CN CN201710801242.4A patent/CN107562901B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105635257A (en) * | 2015-12-24 | 2016-06-01 | 福建天泉教育科技有限公司 | Method and system for automatically detecting data update |
| CN106713497A (en) * | 2017-01-24 | 2017-05-24 | 郑州云海信息技术有限公司 | Server-side message push device and method and message push system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107562901A (en) | 2018-01-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10839038B2 (en) | Generating configuration information for obtaining web resources | |
| US20170099239A1 (en) | System and method for updating information in an instant messaging application | |
| CN109241242B (en) | Live broadcast room topic recommendation method and device, server and storage medium | |
| US20130238657A1 (en) | Optimizing Software Applications | |
| CN108989397B (en) | Data recommendation method and device and storage medium | |
| CN107133309B (en) | Method and device for storing and querying process example, storage medium and electronic equipment | |
| US9578119B2 (en) | Method, server, and client for pushing and displaying splash screen | |
| CN110245069B (en) | Page version testing method and device and page display method and device | |
| CN111339171B (en) | Data query method, device and equipment | |
| US20070266042A1 (en) | Methods and systems for report retrieval and presentation | |
| US20160012074A1 (en) | System and method for providing contextual analytics data | |
| CN111680799B (en) | Method and device for processing model parameters | |
| CN112416991A (en) | Data processing method and device and storage medium | |
| KR102307380B1 (en) | Natural language processing based call center support system and method | |
| CN112825089A (en) | Article recommendation method, article recommendation device, article recommendation equipment and storage medium | |
| CN109409419B (en) | Method and apparatus for processing data | |
| CN108520401B (en) | User list management method, device, platform and storage medium | |
| JP2017500632A (en) | Method and system for providing access to auxiliary information | |
| CN107562901B (en) | Client data updating method and system | |
| CN112115113B (en) | Data storage system, method, device, equipment and storage medium | |
| US10827035B2 (en) | Data uniqued by canonical URL for rest application | |
| KR20150136338A (en) | Method of creating multi tenancy history, server performing the same and storage media storing the same | |
| CN111488386A (en) | Data query method and device | |
| CN109120783A (en) | Information acquisition method and device, mobile terminal and computer readable storage medium | |
| US9692804B2 (en) | Method of and system for determining creation time of a web resource |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20210111 Address after: Building 9, No.1, guanpu Road, Guoxiang street, Wuzhong Economic Development Zone, Wuzhong District, Suzhou City, Jiangsu Province Applicant after: SUZHOU LANGCHAO INTELLIGENT TECHNOLOGY Co.,Ltd. Address before: Room 1601, floor 16, 278 Xinyi Road, Zhengdong New District, Zhengzhou City, Henan Province Applicant before: ZHENGZHOU YUNHAI INFORMATION TECHNOLOGY Co.,Ltd. |
|
| TA01 | Transfer of patent application right | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |