CN115174543B - Version update release time determining method and device - Google Patents
Version update release time determining method and device Download PDFInfo
- Publication number
- CN115174543B CN115174543B CN202210905717.5A CN202210905717A CN115174543B CN 115174543 B CN115174543 B CN 115174543B CN 202210905717 A CN202210905717 A CN 202210905717A CN 115174543 B CN115174543 B CN 115174543B
- Authority
- CN
- China
- Prior art keywords
- service
- information
- update
- timeliness
- importance
- 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 61
- 238000004590 computer program Methods 0.000 claims description 15
- 238000003860 storage Methods 0.000 claims description 11
- 230000002123 temporal effect Effects 0.000 claims description 10
- 238000009826 distribution Methods 0.000 claims description 8
- 238000010586 diagram Methods 0.000 description 11
- 238000012544 monitoring process Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 5
- 238000012545 processing Methods 0.000 description 5
- 238000011156 evaluation Methods 0.000 description 4
- 230000008569 process Effects 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 238000013500 data storage Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000007547 defect Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides a version update release time determining method and device, relates to the technical field of data update, and can be used in the financial field or other technical fields. The method comprises the following steps: receiving service information sent by a server side and receiving problem information of a user using a service sent by a client side; the service information carries a service update content label, and the problem information carries a problem reason and problem occurrence time; determining service importance information and service timeliness information according to the service updating content label, the problem reason and the problem occurrence time; and sending the service importance information and the service timeliness information to the client so that the client can determine version update release time according to the service importance information and the service timeliness information. The apparatus performs the above method. The method and the device provided by the embodiment of the invention can reasonably determine the release time of version update.
Description
Technical Field
The invention relates to the technical field of data updating, in particular to a version update release time determining method and device.
Background
The server side provides an accessible URL address of HTTP or HTTPS, and the client side interacts with the server side through HTTP protocol or HTTPS protocol. The developers of the server side and the client side are often different, and if the server side updates some information (such as URL address information, request parameters, resource files, etc.), the client side needs to be notified to the developers to update.
On the one hand, the prior art has the defect that the update version of the notification client is not timely, so that the user cannot use the service; on the other hand, the client is informed of updated versions too frequently, workload of client developers is increased, and working efficiency is low.
Disclosure of Invention
Aiming at the problems in the prior art, the embodiment of the invention provides a version update release time determining method and device, which can at least partially solve the problems in the prior art.
In one aspect, the present invention provides a method for determining release time of version update, including:
receiving service information sent by a server side and receiving problem information of a user using a service sent by a client side; the service information carries a service update content label, and the problem information carries a problem reason and problem occurrence time;
Determining service importance information and service timeliness information according to the service updating content label, the problem reason and the problem occurrence time;
and sending the service importance information and the service timeliness information to the client so that the client can determine version update release time according to the service importance information and the service timeliness information.
Wherein the service update content tag comprises a resource file update, and the problem reason comprises that the resource file is not updated; correspondingly, the determining service importance information and service timeliness information according to the service update content tag, the problem reason and the problem occurrence time includes:
acquiring the occurrence time of the resource file which is not updated in a preset period, and calculating the occurrence frequency of the resource file which is not updated;
and if the occurrence frequency of the non-updated resource file is greater than or equal to a first preset frequency threshold, determining that the service importance information corresponding to the updated resource file is first importance information and the service timeliness information is first timeliness information.
The version update release time determining method further comprises the following steps:
If the occurrence frequency of the non-updated resource file is smaller than a first preset frequency threshold, determining that service importance information corresponding to the updated resource file is first importance information and service timeliness information is second timeliness information; wherein the second timeliness information has a lower temporal urgency than the first timeliness information.
The service updating content label comprises a newly added service, and the problem reasons comprise web page name identification updating failure; correspondingly, the determining service importance information and service timeliness information according to the service update content tag, the problem reason and the problem occurrence time includes:
acquiring the occurrence time of the update failure of the webpage name identification in a preset period, and calculating the occurrence frequency of the update failure of the webpage name identification;
if the occurrence frequency of the web page name identification updating failure is greater than or equal to a second preset frequency threshold, determining that the service importance information corresponding to the newly added service is first importance information and the service timeliness information is first timeliness information.
The version update release time determining method further comprises the following steps:
If the occurrence frequency of the web page name identification updating failure is smaller than a second preset frequency threshold, determining that service importance information corresponding to the newly added service is first importance information and service timeliness information is second timeliness information; wherein the second timeliness information has a lower temporal urgency than the first timeliness information.
The service update content label comprises a webpage name identification update or a service parameter update; correspondingly, the version update release time determining method further comprises the following steps:
if the service updating content label is determined to be the web page name identification update or the service parameter update, directly determining that the service importance information corresponding to the web page name identification update and the service parameter update are first importance information and service timeliness information is first timeliness information.
The receiving the service information sent by the server side includes:
and receiving service information to be updated or service information to be distributed, which are sent by the server side.
In one aspect, the present invention provides a version update release time determining apparatus, including:
the receiving unit is used for receiving the service information sent by the server side and receiving the problem information of the user using the service sent by the client side; the service information carries a service update content label, and the problem information carries a problem reason and problem occurrence time;
A determining unit, configured to determine service importance information and service timeliness information according to the service update content tag, the problem cause, and the problem occurrence time;
and the sending unit is used for sending the service importance information and the service timeliness information to the client so that the client can determine version update release time according to the service importance information and the service timeliness information.
In still another aspect, an embodiment of the present invention provides an electronic device, including: a processor, a memory, and a bus, wherein,
the processor and the memory complete communication with each other through the bus;
the memory stores program instructions executable by the processor, the processor invoking the program instructions capable of performing the method of:
receiving service information sent by a server side and receiving problem information of a user using a service sent by a client side; the service information carries a service update content label, and the problem information carries a problem reason and problem occurrence time;
determining service importance information and service timeliness information according to the service updating content label, the problem reason and the problem occurrence time;
And sending the service importance information and the service timeliness information to the client so that the client can determine version update release time according to the service importance information and the service timeliness information.
Embodiments of the present invention provide a non-transitory computer readable storage medium comprising:
the non-transitory computer readable storage medium stores computer instructions that cause the computer to perform the method of:
receiving service information sent by a server side and receiving problem information of a user using a service sent by a client side; the service information carries a service update content label, and the problem information carries a problem reason and problem occurrence time;
determining service importance information and service timeliness information according to the service updating content label, the problem reason and the problem occurrence time;
and sending the service importance information and the service timeliness information to the client so that the client can determine version update release time according to the service importance information and the service timeliness information.
The version update release time determining method and device provided by the embodiment of the invention are used for receiving the service information sent by the server side and the problem information of the user using the service sent by the client side; the service information carries a service update content label, and the problem information carries a problem reason and problem occurrence time; determining service importance information and service timeliness information according to the service updating content label, the problem reason and the problem occurrence time; and sending the service importance information and the service timeliness information to the client so that the client can determine version update release time according to the service importance information and the service timeliness information, the version update release time can be reasonably determined, the timely and normal service use of a user is ensured, and the working efficiency of a developer of the client is improved.
Drawings
In order to more clearly illustrate the embodiments of the invention or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the invention, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art. In the drawings:
fig. 1 is a flowchart of a version update distribution time determining method according to an embodiment of the present invention.
Fig. 2 is a schematic structural diagram of a version update release time determining method according to an embodiment of the present invention.
Fig. 3 is a schematic structural diagram of a version update distribution time determining apparatus according to an embodiment of the present invention.
Fig. 4 is a schematic diagram of an entity structure of an electronic device according to an embodiment of the present invention.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the embodiments of the present invention will be described in further detail with reference to the accompanying drawings. The exemplary embodiments of the present invention and their descriptions herein are for the purpose of explaining the present invention, but are not to be construed as limiting the invention. It should be noted that, in the case of no conflict, the embodiments and features in the embodiments may be arbitrarily combined with each other.
Fig. 1 is a flowchart of a version update release time determining method according to an embodiment of the present invention, where, as shown in fig. 1, the version update release time determining method according to the embodiment of the present invention includes:
step S1: receiving service information sent by a server side and receiving problem information of a user using a service sent by a client side; the service information carries a service update content tag, and the problem information carries a problem reason and problem occurrence time.
Step S2: and determining service importance information and service timeliness information according to the service updating content label, the problem reason and the problem occurrence time.
Step S3: and sending the service importance information and the service timeliness information to the client so that the client can determine version update release time according to the service importance information and the service timeliness information.
In the step S1, the device receives service information sent by the server side and receives problem information of the user using the service sent by the client side; the service information carries a service update content tag, and the problem information carries a problem reason and problem occurrence time. The apparatus may be a computer device performing the method, for example, a registration listening server. It should be noted that, the data acquisition and analysis according to the embodiments of the present invention are authorized by the user.
As shown in fig. 2, the registration listening server 2 in the embodiment of the present invention may implement data interaction with the client 1 and the server 3, where the client 1 implements data interaction with a user terminal, i.e. the user terminal 0.
The receiving service information sent by the server side includes:
and receiving service information to be updated or service information to be distributed, which are sent by the server side. The service information carries a service update content tag, and the specific carrying content is shown in table 1:
TABLE 1
| Corresponding service | Updating content | Service detailed information |
| Service 1 | URL update | A URL; uploading parameters; return parameters |
| Service 2 | Service parameter update | A URL; uploading parameters; return parameters |
| Service 3 | Resource file update | A URL; uploading parameters; return parameters |
| Service 4 | New addition of | A URL; uploading parameters; return parameters |
The problem information of the user's usage of the service may be issued by the user terminal and forwarded via the client 1 to the registration listening server 2.
The specific contents of the problem information of the user using the service are shown in table 2 (the problem occurrence time is not shown):
TABLE 2
| Description of the problem | Cause of problem | Question type |
| Web page display errors | URL update failure | Server problem |
| Display error of web page picture | Resource file not updated | Server problem |
It should be noted that, the problem information of the user using the service may be fed back multiple times by the same client, or may be fed back once or multiple times by different clients.
In the step S2, the device determines service importance information and service timeliness information according to the service update content tag, the problem cause, and the problem occurrence time. The service update content label comprises resource file update, and the problem reason comprises that the resource file is not updated; correspondingly, the determining service importance information and service timeliness information according to the service update content tag, the problem reason and the problem occurrence time includes:
acquiring the occurrence time of the resource file which is not updated in a preset period, and calculating the occurrence frequency of the resource file which is not updated; the preset period can be set independently according to actual conditions, and can be selected to be 2 hours. The following are illustrated: between 7 points and 9 points, the occurrence time of the non-update of the resource file is 7 points, 10 minutes, 7 points, 15 minutes, 7 points, 20 minutes and 7 points, 25 minutes. The time of occurrence of the resource file not updated may be accurate to seconds, milliseconds, etc., and is conveniently selected to be accurate to minutes for example.
Referring to the above example, the occurrence frequency of the resource file non-update is 4 times.
And if the occurrence frequency of the non-updated resource file is greater than or equal to a first preset frequency threshold, determining that the service importance information corresponding to the updated resource file is first importance information and the service timeliness information is first timeliness information. The first preset frequency threshold may be set independently according to actual conditions, and may be selected to be 3 times. Referring to the above example, it is determined that the service importance information corresponding to the update of the resource file is the first importance information and the service timeliness information is the first timeliness information.
The first importance information may be of higher importance than the second importance information, i.e. the first importance information may be important and the second importance information may be general.
The time urgency of the first timeliness information is higher than that of the second timeliness information, namely the first timeliness information can be urgent, and the second timeliness information can be general.
The version update release time determining method further comprises the following steps:
if the occurrence frequency of the non-updated resource file is smaller than a first preset frequency threshold, determining that service importance information corresponding to the updated resource file is first importance information and service timeliness information is second timeliness information; wherein the second timeliness information has a lower temporal urgency than the first timeliness information. If the occurrence frequency of the update of the resource file is 2 times, determining that the service importance information corresponding to the update of the resource file is the first importance information and the service timeliness information is the second timeliness information, which can be referred to the above description and will not be repeated.
The service updating content label comprises a newly added service, and the problem reasons comprise web page name identification updating failure; the web page name identifier is the URL, and the web page name identifier is the update failure corresponding to "URL update failure" in table 2.
Correspondingly, the determining service importance information and service timeliness information according to the service update content tag, the problem reason and the problem occurrence time includes:
acquiring the occurrence time of the update failure of the webpage name identification in a preset period, and calculating the occurrence frequency of the update failure of the webpage name identification; the preset period can be set independently according to actual conditions, and can be selected to be 2 hours. The following are illustrated: between 7 points and 9 points, the web page name identification failure time is 8 points, namely 10 points, 15 points, 20 points and 25 points. The web page name identification update failure time may be accurate to seconds, milliseconds, etc., with the accuracy of minutes chosen for ease of illustration.
If the occurrence frequency of the web page name identification updating failure is greater than or equal to a second preset frequency threshold, determining that the service importance information corresponding to the newly added service is first importance information and the service timeliness information is first timeliness information. The second preset frequency threshold value may be the same as the first preset frequency threshold value, or may be different, and taking the same as an example, and selecting for 3 times, determining service importance information corresponding to the newly added service as first importance information, namely importance; and the service timeliness information is first timeliness information, namely emergency.
The version update release time determining method further comprises the following steps:
if the occurrence frequency of the web page name identification updating failure is smaller than a second preset frequency threshold, determining that service importance information corresponding to the newly added service is first importance information and service timeliness information is second timeliness information; wherein the second timeliness information has a lower temporal urgency than the first timeliness information. If the occurrence frequency of the web page name identification update failure is 2 times, determining service importance information corresponding to the newly added service as first importance information, namely importance; and the service timeliness information is second timeliness information, namely general. Reference is made to the above description and will not be repeated.
The service update content label comprises a webpage name identification update or a service parameter update; the web page name identifies the update, i.e., URL update.
Correspondingly, the version update release time determining method further comprises the following steps:
if the service updating content label is determined to be the web page name identification update or the service parameter update, directly determining that the service importance information corresponding to the web page name identification update and the service parameter update are first importance information and service timeliness information is first timeliness information. Summarizing the above, some example content is shown in table 3:
TABLE 3 Table 3
In the step S3, the device sends the service importance information and the service timeliness information to the client, so that the client determines version update release time according to the service importance information and the service timeliness information. The content information of table 3 may be sent to the client, which may determine a version update publication time according to predefined rules, for example: for important and urgent services, immediately updating the version to update the version and issuing the version; for other cases, the version update may be performed together and released at the next version update.
As shown in fig. 2, the method of the embodiment of the present invention may be implemented based on modularization, and specifically includes a user terminal 0, a client 1, a registration listening server 2, and a server 3. Wherein:
user terminal 0: the service providing module 14 for operating the client 1 performs the relevant service usage.
Client 1: mainly for providing services to the user terminal 0; monitoring registration is carried out at a registration monitoring server 2; updating the related information according to the information importance degree of the service updating information; the problems occurring in the user operation are collected and fed back to the registration listening server 2. The method specifically comprises the following steps:
Listening registration module 11: registering and monitoring with a service subscription module 26 in the registration and monitoring server 2, and receiving update information of the service subscription module 26 when the service of the server 3 is registered or updated; the update information is sent to the update evaluation module 12. The update information is shown in table 3.
Update evaluation module 12: according to importance and effectiveness (such as important and urgent immediate update version and release, otherwise release after next version update), evaluating version update release effectiveness of the update client 1; and sent to the update module 13.
Update module 13: the service provided by the service providing module 14 of the client 1 is updated and released according to the version update release timeliness of the update evaluation module 12.
Service providing module 14: providing a service to the user terminal 0; collect the questions of the user terminal 0 during operation and send the questions to the question collection module 15, and the questions are forwarded by the question collection module 15 to the question feedback module 16. The problem forms are shown in table 2 above, for example.
The problem feedback module 16: the collected questions of the user terminal 0 during operation are sent to the question storage module 24.
Registration listening server 2: providing service release and update to the server 3; determining the importance of the service update related information according to the service label of the server 3 and the user operation problem fed back by the client 1; the client 1 is provided with a snoop registration.
Service distribution module 21: the service registration module 32 of the receiving server 3 receives the service to be published and sends it to the service update receiving module 22. The service information form is shown in table 1 above, for example.
Service update receiving module 22: receiving a service to be updated of the service update module 33 of the server side 3; receiving a service to be distributed of the service distribution module 21; the service to be updated or the service to be released is then sent to the information importance setting module 23.
The information importance degree setting module 23: receiving the service to be updated or the service to be issued sent by the service update receiving module 22, and counting the problems (according to the problem reasons, counting the frequency of occurrence of the problems in a period of time (such as within 2 hours) near a certain time) in the operation process of the user terminal 0 in the problem storage module 24; then, evaluating the importance of the service information according to the service label in the service to be updated or the service to be distributed and the counted problem of the user terminal 0 in the operation process; the importance and timeliness information is then added to the service to be updated or to the service to be published and sent to the service importance update module 25. The service information importance evaluation method is exemplified as follows:
1. If the service tag is URL update or service parameter update, the importance of the service information is important, and the timeliness is urgent.
2. If the service label is updated by the resource file and the frequency of the resource file which is not updated is greater than or equal to a first preset frequency threshold, the importance of the service information is important and the timeliness is urgent.
3. If the service label is updated by the resource file, the problem is that the frequency of the resource file which is not updated is smaller than a first preset frequency threshold, the importance of the service information is important, and the timeliness is general.
4. If the service tag is newly added and the frequency of URL updating failure is greater than or equal to a second preset frequency threshold value, the importance of the service information is important and the timeliness is urgent.
5. If the service tag is newly added and the frequency of URL update failure is smaller than a second preset frequency threshold value, the importance of the service information is important and the timeliness is general.
Problem storage module 24: the problems of the user terminal 0 during operation are stored for use by the information importance setting module 23.
The service importance update module 25: the receiving information importance setting module 23 updates service information by the service to be updated or the service to be released, and service importance and timeliness information; the updated service information is sent to the service subscription module 26 and stored to the data storage module 27. The updated service information form is shown in table 3 above, for example.
Service subscription module 26: the monitoring registration module 11 of the client 1 registers monitoring, and the received service importance update module 25 transmits updated service information.
Data storage module 27: and storing the updated service information.
Server 3: registering a service and updating the service with the registration listening server 2; and setting and updating the service tag.
Service tag setting module 31: setting a service tag. The label setting method is exemplified as follows:
1. if the server-side service is an update URL, the service tag is a URL update;
2. if the server-side service is the update parameter, the service label is the parameter update;
3. if the server-side service is to update the resource file, the service label is to update the resource file;
4. if the server-side service is a newly added service, the service tag is the newly added service.
Service registration module 32: when a service is newly added, the service is registered with the service issuing module 21 of the registration listening server 2.
Service update module 33: when updating the service, the updated service is registered with the service update receiving module 22 of the registration listening server 2.
The version update release time determining method provided by the embodiment of the invention receives the service information sent by the server side and the problem information of the user using the service sent by the client side; the service information carries a service update content label, and the problem information carries a problem reason and problem occurrence time; determining service importance information and service timeliness information according to the service updating content label, the problem reason and the problem occurrence time; and sending the service importance information and the service timeliness information to the client so that the client can determine version update release time according to the service importance information and the service timeliness information, the version update release time can be reasonably determined, the timely and normal service use of a user is ensured, and the working efficiency of a developer of the client is improved.
Further, the service update content tag comprises a resource file update, and the problem reason comprises that the resource file is not updated; correspondingly, the determining service importance information and service timeliness information according to the service update content tag, the problem reason and the problem occurrence time includes:
acquiring the occurrence time of the resource file which is not updated in a preset period, and calculating the occurrence frequency of the resource file which is not updated; reference is made to the above description and will not be repeated.
And if the occurrence frequency of the non-updated resource file is greater than or equal to a first preset frequency threshold, determining that the service importance information corresponding to the updated resource file is first importance information and the service timeliness information is first timeliness information. Reference is made to the above description and will not be repeated.
The version update release time determining method provided by the embodiment of the invention can reasonably determine the version update release time of the service update content updated for the resource file, thereby ensuring that a user can use the service normally in time and improving the working efficiency of a client developer.
Further, the version update release time determining method further includes:
if the occurrence frequency of the non-updated resource file is smaller than a first preset frequency threshold, determining that service importance information corresponding to the updated resource file is first importance information and service timeliness information is second timeliness information; wherein the second timeliness information has a lower temporal urgency than the first timeliness information. Reference is made to the above description and will not be repeated.
The version update release time determining method provided by the embodiment of the invention can reasonably determine the version update release time of the service update content updated for the resource file, thereby ensuring that a user can use the service normally in time and improving the working efficiency of a client developer.
Further, the service update content label comprises a newly added service, and the problem reasons comprise web page name identification update failure; correspondingly, the determining service importance information and service timeliness information according to the service update content tag, the problem reason and the problem occurrence time includes:
acquiring the occurrence time of the update failure of the webpage name identification in a preset period, and calculating the occurrence frequency of the update failure of the webpage name identification; reference is made to the above description and will not be repeated.
If the occurrence frequency of the web page name identification updating failure is greater than or equal to a second preset frequency threshold, determining that the service importance information corresponding to the newly added service is first importance information and the service timeliness information is first timeliness information. Reference is made to the above description and will not be repeated.
The version update release time determining method provided by the embodiment of the invention can reasonably determine the version update release time of the newly added service as the service update content, thereby ensuring that the user can use the service normally in time and improving the working efficiency of the client developer.
Further, the version update release time determining method further includes:
if the occurrence frequency of the web page name identification updating failure is smaller than a second preset frequency threshold, determining that service importance information corresponding to the newly added service is first importance information and service timeliness information is second timeliness information; wherein the second timeliness information has a lower temporal urgency than the first timeliness information. Reference is made to the above description and will not be repeated.
The version update release time determining method provided by the embodiment of the invention can reasonably determine the version update release time of the newly added service as the service update content, thereby ensuring that the user can use the service normally in time and improving the working efficiency of the client developer.
Further, the service update content tag comprises a web page name identification update or a service parameter update; correspondingly, the version update release time determining method further comprises the following steps:
if the service updating content label is determined to be the web page name identification update or the service parameter update, directly determining that the service importance information corresponding to the web page name identification update and the service parameter update are first importance information and service timeliness information is first timeliness information. Reference is made to the above description and will not be repeated.
The version update release time determining method provided by the embodiment of the invention can reasonably determine the version update release time of the service update content for the web page name identification update or the service parameter update, thereby ensuring that a user can use the service normally in time and improving the working efficiency of a client developer.
Further, the receiving the service information sent by the server side includes:
and receiving service information to be updated or service information to be distributed, which are sent by the server side. Reference is made to the above description and will not be repeated.
The version update release time determining method provided by the embodiment of the invention can further reasonably determine the service information to be updated or the version update release time of the service information to be released, thereby ensuring that users can use the service normally in time and improving the working efficiency of client developers.
It should be noted that, the version update release time determining method provided by the embodiment of the present invention may be used in the financial field, and may also be used in any technical field other than the financial field.
Fig. 3 is a schematic structural diagram of a version update distribution time determining apparatus according to an embodiment of the present invention, and as shown in fig. 3, the version update distribution time determining apparatus according to an embodiment of the present invention includes a receiving unit 301, a determining unit 302, and a transmitting unit 303, where:
The receiving unit 301 is configured to receive service information sent by a server, and receive problem information of a user using a service sent by a client; the service information carries a service update content label, and the problem information carries a problem reason and problem occurrence time; the determining unit 302 is configured to determine service importance information and service timeliness information according to the service update content tag, the problem cause, and the problem occurrence time; the sending unit 303 is configured to send the service importance information and the service timeliness information to the client, so that the client determines version update release time according to the service importance information and the service timeliness information.
Specifically, the receiving unit 301 in the device is configured to receive service information sent by a server, and receive problem information of a user using a service sent by a client; the service information carries a service update content label, and the problem information carries a problem reason and problem occurrence time; the determining unit 302 is configured to determine service importance information and service timeliness information according to the service update content tag, the problem cause, and the problem occurrence time; the sending unit 303 is configured to send the service importance information and the service timeliness information to the client, so that the client determines version update release time according to the service importance information and the service timeliness information.
The version update release time determining device provided by the embodiment of the invention receives the service information sent by the server side and the problem information of the user using the service sent by the client side; the service information carries a service update content label, and the problem information carries a problem reason and problem occurrence time; determining service importance information and service timeliness information according to the service updating content label, the problem reason and the problem occurrence time; and sending the service importance information and the service timeliness information to the client so that the client can determine version update release time according to the service importance information and the service timeliness information, the version update release time can be reasonably determined, the timely and normal service use of a user is ensured, and the working efficiency of a developer of the client is improved.
Further, the service update content tag comprises a resource file update, and the problem reason comprises that the resource file is not updated; accordingly, the determining unit 302 is specifically configured to:
acquiring the occurrence time of the resource file which is not updated in a preset period, and calculating the occurrence frequency of the resource file which is not updated;
And if the occurrence frequency of the non-updated resource file is greater than or equal to a first preset frequency threshold, determining that the service importance information corresponding to the updated resource file is first importance information and the service timeliness information is first timeliness information.
The version update release time determining device provided by the embodiment of the invention can reasonably determine the version update release time of the service update content updated for the resource file, thereby ensuring that a user can use the service normally in time and improving the working efficiency of a client developer.
Further, the version update release time determining device is further configured to:
if the occurrence frequency of the non-updated resource file is smaller than a first preset frequency threshold, determining that service importance information corresponding to the updated resource file is first importance information and service timeliness information is second timeliness information; wherein the second timeliness information has a lower temporal urgency than the first timeliness information.
The version update release time determining device provided by the embodiment of the invention can reasonably determine the version update release time of the service update content updated for the resource file, thereby ensuring that a user can use the service normally in time and improving the working efficiency of a client developer.
Further, the service update content label comprises a newly added service, and the problem reasons comprise web page name identification update failure; accordingly, the determining unit 302 is specifically configured to:
acquiring the occurrence time of the update failure of the webpage name identification in a preset period, and calculating the occurrence frequency of the update failure of the webpage name identification;
if the occurrence frequency of the web page name identification updating failure is greater than or equal to a second preset frequency threshold, determining that the service importance information corresponding to the newly added service is first importance information and the service timeliness information is first timeliness information.
The version update release time determining device provided by the embodiment of the invention can reasonably determine the version update release time of the newly added service as the service update content, thereby ensuring that a user can use the service normally in time and improving the working efficiency of a client developer.
Further, the version update release time determining device is further configured to:
if the occurrence frequency of the web page name identification updating failure is smaller than a second preset frequency threshold, determining that service importance information corresponding to the newly added service is first importance information and service timeliness information is second timeliness information; wherein the second timeliness information has a lower temporal urgency than the first timeliness information.
The version update release time determining device provided by the embodiment of the invention can reasonably determine the version update release time of the newly added service as the service update content, thereby ensuring that a user can use the service normally in time and improving the working efficiency of a client developer.
Further, the service update content tag comprises a web page name identification update or a service parameter update; correspondingly, the version update release time determining device is further used for:
if the service updating content label is determined to be the web page name identification update or the service parameter update, directly determining that the service importance information corresponding to the web page name identification update and the service parameter update are first importance information and service timeliness information is first timeliness information.
The version update release time determining device provided by the embodiment of the invention can reasonably determine the version update release time of the service update content for the web page name identification update or the service parameter update, thereby ensuring that a user can use the service normally in time and improving the working efficiency of a client developer.
Further, the receiving unit 301 is specifically configured to:
and receiving service information to be updated or service information to be distributed, which are sent by the server side.
The version update release time determining device provided by the embodiment of the invention can further reasonably determine the service information to be updated or the version update release time of the service information to be released, thereby ensuring that a user can use the service normally in time and improving the working efficiency of a client developer.
The embodiment of the version update release time determining apparatus provided in the embodiment of the present invention may be specifically used to execute the processing flow of each method embodiment, and the functions thereof are not described herein in detail, and may refer to the detailed description of the method embodiment.
Fig. 4 is a schematic diagram of an entity structure of an electronic device according to an embodiment of the present invention, as shown in fig. 4, where the electronic device includes: a processor (processor) 401, a memory (memory) 402, and a bus 403;
wherein, the processor 401 and the memory 402 complete the communication with each other through the bus 403;
the processor 401 is configured to call the program instructions in the memory 402 to perform the methods provided in the above method embodiments, for example, including:
receiving service information sent by a server side and receiving problem information of a user using a service sent by a client side; the service information carries a service update content label, and the problem information carries a problem reason and problem occurrence time;
Determining service importance information and service timeliness information according to the service updating content label, the problem reason and the problem occurrence time;
and sending the service importance information and the service timeliness information to the client so that the client can determine version update release time according to the service importance information and the service timeliness information.
The present embodiment discloses a computer program product comprising a computer program stored on a non-transitory computer readable storage medium, the computer program comprising program instructions which, when executed by a computer, are capable of performing the methods provided by the above-described method embodiments, for example comprising:
receiving service information sent by a server side and receiving problem information of a user using a service sent by a client side; the service information carries a service update content label, and the problem information carries a problem reason and problem occurrence time;
determining service importance information and service timeliness information according to the service updating content label, the problem reason and the problem occurrence time;
And sending the service importance information and the service timeliness information to the client so that the client can determine version update release time according to the service importance information and the service timeliness information.
The present embodiment provides a computer-readable storage medium storing a computer program that causes the computer to execute the methods provided by the above-described method embodiments, for example, including:
receiving service information sent by a server side and receiving problem information of a user using a service sent by a client side; the service information carries a service update content label, and the problem information carries a problem reason and problem occurrence time;
determining service importance information and service timeliness information according to the service updating content label, the problem reason and the problem occurrence time;
and sending the service importance information and the service timeliness information to the client so that the client can determine version update release time according to the service importance information and the service timeliness information.
It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In the description of the present specification, reference to the terms "one embodiment," "one particular embodiment," "some embodiments," "for example," "an example," "a particular example," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the invention. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiments or examples. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
The foregoing description of the embodiments has been provided for the purpose of illustrating the general principles of the invention, and is not meant to limit the scope of the invention, but to limit the invention to the particular embodiments, and any modifications, equivalents, improvements, etc. that fall within the spirit and principles of the invention are intended to be included within the scope of the invention.
Claims (10)
1. A version update distribution time determining method, characterized by comprising:
receiving service information sent by a server side and receiving problem information of a user using a service sent by a client side; the service information carries a service update content label, and the problem information carries a problem reason and problem occurrence time;
determining service importance information and service timeliness information according to the service updating content label, the problem reason and the problem occurrence time;
and sending the service importance information and the service timeliness information to the client so that the client can determine version update release time according to the service importance information and the service timeliness information.
2. The version-update-release-time determination method according to claim 1, wherein the service-update-content tag includes a resource file update, and the problem cause includes a resource file not updated; correspondingly, the determining service importance information and service timeliness information according to the service update content tag, the problem reason and the problem occurrence time includes:
acquiring the occurrence time of the resource file which is not updated in a preset period, and calculating the occurrence frequency of the resource file which is not updated;
And if the occurrence frequency of the non-updated resource file is greater than or equal to a first preset frequency threshold, determining that the service importance information corresponding to the updated resource file is first importance information and the service timeliness information is first timeliness information.
3. The version-update-release-time determination method according to claim 2, characterized in that the version-update-release-time determination method further comprises:
if the occurrence frequency of the non-updated resource file is smaller than a first preset frequency threshold, determining that service importance information corresponding to the updated resource file is first importance information and service timeliness information is second timeliness information; wherein the second timeliness information has a lower temporal urgency than the first timeliness information.
4. The version-up release time determining method according to claim 1, wherein the service-up content tag includes a newly added service, and the problem cause includes a web-page-name-identification-up failure; correspondingly, the determining service importance information and service timeliness information according to the service update content tag, the problem reason and the problem occurrence time includes:
Acquiring the occurrence time of the update failure of the webpage name identification in a preset period, and calculating the occurrence frequency of the update failure of the webpage name identification;
if the occurrence frequency of the web page name identification updating failure is greater than or equal to a second preset frequency threshold, determining that the service importance information corresponding to the newly added service is first importance information and the service timeliness information is first timeliness information.
5. The version-up release time determination method according to claim 4, further comprising:
if the occurrence frequency of the web page name identification updating failure is smaller than a second preset frequency threshold, determining that service importance information corresponding to the newly added service is first importance information and service timeliness information is second timeliness information; wherein the second timeliness information has a lower temporal urgency than the first timeliness information.
6. The version-up release time determination method according to any one of claims 1 to 5, wherein the service-up content tag includes a web-page-name-identification update or a service-parameter update; correspondingly, the version update release time determining method further comprises the following steps:
If the service updating content label is determined to be the web page name identification update or the service parameter update, directly determining that the service importance information corresponding to the web page name identification update and the service parameter update are first importance information and service timeliness information is first timeliness information.
7. The method for determining release time of version update according to any one of claims 1 to 5, wherein the receiving service information sent by the server side includes:
and receiving service information to be updated or service information to be distributed, which are sent by the server side.
8. A version update distribution time determining apparatus, comprising:
the receiving unit is used for receiving the service information sent by the server side and receiving the problem information of the user using the service sent by the client side; the service information carries a service update content label, and the problem information carries a problem reason and problem occurrence time;
a determining unit, configured to determine service importance information and service timeliness information according to the service update content tag, the problem cause, and the problem occurrence time;
and the sending unit is used for sending the service importance information and the service timeliness information to the client so that the client can determine version update release time according to the service importance information and the service timeliness information.
9. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the steps of the method of any one of claims 1 to 7 when the computer program is executed by the processor.
10. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210905717.5A CN115174543B (en) | 2022-07-29 | 2022-07-29 | Version update release time determining method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210905717.5A CN115174543B (en) | 2022-07-29 | 2022-07-29 | Version update release time determining method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115174543A CN115174543A (en) | 2022-10-11 |
| CN115174543B true CN115174543B (en) | 2024-01-30 |
Family
ID=83476927
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210905717.5A Active CN115174543B (en) | 2022-07-29 | 2022-07-29 | Version update release time determining method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115174543B (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103841155A (en) * | 2012-11-26 | 2014-06-04 | 腾讯科技（深圳）有限公司 | Software download method and software download device |
| CN105808274A (en) * | 2014-12-30 | 2016-07-27 | 航天信息股份有限公司 | Software upgrading method and system as well as corresponding clients and servers |
| CN106201552A (en) * | 2016-07-22 | 2016-12-07 | 北京智能管家科技有限公司 | A kind of method for upgrading software, client, server and system |
| CN106502688A (en) * | 2016-11-01 | 2017-03-15 | 网易（杭州）网络有限公司 | The processing method and processing device that resource is issued |
| CN110825408A (en) * | 2019-10-30 | 2020-02-21 | 中国农业银行股份有限公司 | Program version updating method, self-service equipment and version control server |
| KR102192313B1 (en) * | 2019-11-20 | 2020-12-17 | (주) 와이즈스톤 | An Integrated Management Solution System for Developing Software |
| CN112905928A (en) * | 2021-05-07 | 2021-06-04 | 杭州米络星科技(集团)有限公司 | Webpage refreshing method and device, electronic equipment and storage medium |
| CN113055723A (en) * | 2019-12-27 | 2021-06-29 | 中兴通讯股份有限公司 | Version debugging and upgrading method, device, equipment and storage medium |
-
2022
- 2022-07-29 CN CN202210905717.5A patent/CN115174543B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103841155A (en) * | 2012-11-26 | 2014-06-04 | 腾讯科技（深圳）有限公司 | Software download method and software download device |
| CN105808274A (en) * | 2014-12-30 | 2016-07-27 | 航天信息股份有限公司 | Software upgrading method and system as well as corresponding clients and servers |
| CN106201552A (en) * | 2016-07-22 | 2016-12-07 | 北京智能管家科技有限公司 | A kind of method for upgrading software, client, server and system |
| CN106502688A (en) * | 2016-11-01 | 2017-03-15 | 网易（杭州）网络有限公司 | The processing method and processing device that resource is issued |
| CN110825408A (en) * | 2019-10-30 | 2020-02-21 | 中国农业银行股份有限公司 | Program version updating method, self-service equipment and version control server |
| KR102192313B1 (en) * | 2019-11-20 | 2020-12-17 | (주) 와이즈스톤 | An Integrated Management Solution System for Developing Software |
| CN113055723A (en) * | 2019-12-27 | 2021-06-29 | 中兴通讯股份有限公司 | Version debugging and upgrading method, device, equipment and storage medium |
| CN112905928A (en) * | 2021-05-07 | 2021-06-04 | 杭州米络星科技(集团)有限公司 | Webpage refreshing method and device, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115174543A (en) | 2022-10-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112286806B (en) | Automatic test method and device, storage medium and electronic equipment | |
| US8078922B2 (en) | Internal server error analysis | |
| US9369521B2 (en) | Naming of distributed business transactions | |
| US20080154758A1 (en) | Systems and methods for maintaining credit information about an entity | |
| WO2016201176A1 (en) | Data quality analysis | |
| CN111355622A (en) | Container traffic monitoring method, system and computer readable storage medium | |
| CN113806191B (en) | A data processing method, device, equipment and storage medium | |
| CN110737655B (en) | Method and device for reporting data | |
| CN117336135A (en) | Data transmission method, device, storage medium and electronic equipment | |
| CN112214510B (en) | Dynamic source searching method, device and system for purchasing demand and storage medium | |
| US20100036762A1 (en) | System and Method for Tracking a Billing Cycle | |
| CN108628901A (en) | A kind of data-updating method and device | |
| CN115174543B (en) | Version update release time determining method and device | |
| CN111190625A (en) | APP version upgrading method, server, client and computer readable storage medium | |
| CN112650657A (en) | Business system analysis method and device based on stream computing | |
| CN115080366A (en) | Alarm method, alarm device, computer equipment and storage medium | |
| CN110968475A (en) | Method and device for monitoring webpage, electronic equipment and readable storage medium | |
| CN111679899B (en) | Task scheduling method, device, platform equipment and storage medium | |
| CN114064408A (en) | Monitoring method, device, device and storage medium based on MD5 value verification | |
| CN112596974A (en) | Full link monitoring method, device, equipment and storage medium | |
| US20210400122A1 (en) | System for processing coherent data | |
| US20230376469A1 (en) | Flow-based data quality monitoring | |
| CN115268943A (en) | Deployment method, device, electronic device and storage medium of service to be tested | |
| CN114090311A (en) | A data processing method and device | |
| CN116150037B (en) | Method and device for managing user login state in use case |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |