CN118151974A - Method and system for upgrading service system - Google Patents
Method and system for upgrading service system Download PDFInfo
- Publication number
- CN118151974A CN118151974A CN202410582814.4A CN202410582814A CN118151974A CN 118151974 A CN118151974 A CN 118151974A CN 202410582814 A CN202410582814 A CN 202410582814A CN 118151974 A CN118151974 A CN 118151974A
- Authority
- CN
- China
- Prior art keywords
- users
- service system
- user
- service
- determining
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 51
- 238000012545 processing Methods 0.000 claims abstract description 22
- 238000012360 testing method Methods 0.000 claims description 58
- 238000012795 verification Methods 0.000 claims description 27
- 238000011156 evaluation Methods 0.000 claims description 12
- 238000004590 computer program Methods 0.000 claims description 6
- 238000003672 processing method Methods 0.000 claims description 3
- 238000012502 risk assessment Methods 0.000 claims description 2
- 230000008569 process Effects 0.000 description 13
- 238000012216 screening Methods 0.000 description 8
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
Landscapes
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention provides a method and a system for upgrading and processing a service system, which belong to the technical field of data processing and specifically comprise the following steps: the updating service module of the service system is determined based on the updating data, the updating service scene of the service system is determined through the updating service module, the historical use data of different users in different updating service scenes is obtained, the updating matching degree and the matching use user of the different users and the service system are determined based on the historical use data, the matching use user is used as a priority pushing user, the service system is pushed to the priority pushing user, and when the service system meets the requirements according to the use data of the priority pushing user, the service system is pushed to all the use users, so that the safety of the updating processing of the service system is ensured.
Description
Technical Field
The invention belongs to the technical field of data processing, and particularly relates to a method and a system for upgrading a service system.
Background
In order to meet the investment seeking of investment users, financial service enterprises often develop a consultation service system meeting the consultation requirements of the investment users, and in order to solve the problem of BUG processing in the use process of the consultation service system, the software upgrading process of the consultation service system needs to be carried out regularly in the prior art, so that how to ensure the data security in the software upgrading process becomes a technical problem to be solved urgently.
In order to solve the technical problems, in the invention patent CN202410160009.2, "a software remote upgrading method, system and storage medium", the software upgrading data packet is subjected to security check, and after the security check is passed, the software is upgraded, and on the basis of improving the software upgrading efficiency, the security of the software remote upgrading is ensured, but the following technical problems are found easily through analysis:
in the process of performing the software upgrading process, the determination of the differentiated pushing sequence by combining the use data of the user is not considered, and specifically, after the software system upgrading process is completed, due to the limitation of the scene of the test process, certain BUG problems are unavoidable and are not found, so that if batch pushing cannot be performed, the reliability of the software system upgrading process cannot be ensured.
Aiming at the technical problems, the invention provides a method and a system for upgrading a service system.
Disclosure of Invention
In order to achieve the purpose of the invention, the invention adopts the following technical scheme:
According to one aspect of the present invention, a person classification recognition method is provided.
The service system upgrading processing method is characterized by comprising the following steps:
S1, determining an update service module of a service system based on upgrade data, and determining an update service scene of the service system through the update service module;
S2, acquiring historical use data of different users in different updated service scenes, determining update matching degrees of the different users and the service system based on the historical use data and matching use users, judging whether the number of the matching use users is larger than a user number limiting value, if so, entering a next step, if not, taking the matching use users as priority pushing users, and entering a step S4;
S3, determining test use risks of different matched use users based on historical use data of the service system, and taking the matched use users as priority pushing users and entering a next step when the overall use risks of the matched use users meet requirements according to the number of the matched use users;
and S4, pushing the service system to a priority pushing user, and pushing the service system to all users when the service system meets the requirements according to the use data of the priority pushing user.
The invention has the beneficial effects that:
1. According to the invention, the update matching degree of different users and the service system is determined based on the historical use data, and the matched use users are realized, so that the accurate evaluation of the update matching condition of the users and the service system is realized from the angle of the historical use data of the service system, a foundation is laid for further carrying out the updated service system pushing of the distribution times, and the technical problem of data safety caused by unified pushing is avoided.
2. In the invention, whether the service system meets the requirement is determined according to the use data of the priority push user, so that not only is the problem in the use data of the priority push user singly considered, but also the difference of the verification depths of different updated service scenes is fully considered by combining the use data of the priority push user, and the safety and the reliability of the updating processing of the service system are ensured.
The further technical scheme is that the updating service module is determined according to the service module with updating in the service system.
The further technical scheme is that the update service scene is determined according to whether an update service module exists in the service scene.
The further technical scheme is that the historical use data comprises the use times of the user in different service scenes and the use time length of the different use times.
The further technical scheme is that the preset user number is determined according to the number of the updated service scenes, wherein the larger the number of the updated service scenes is, the larger the preset user number is.
The further technical scheme is that the matching users are divided into risk users and general risk users through different testing use risks of the matching users and preset risk thresholds, and the method specifically comprises the following steps:
When the test use risk of the matched use user is larger than a preset risk threshold, determining the matched use user as a risk use user;
and when the test use risk of the matched use user is not greater than a preset risk threshold, determining that the matched use user is a general risk user.
The further technical scheme is that whether the total use risk of the matched use user meets the requirement is determined by combining a preset risk limit value, and the method specifically comprises the following steps:
and when the total use risk of the matched use users is smaller than the preset risk limit value, determining that the total use risk of the matched use users meets the requirement.
The method comprises the further technical scheme that when the overall use risk of the matched use users does not meet the requirement, the determination of the priority pushing users is carried out based on the number of the specified users and the test use risks of different matched use users.
The further technical scheme is that the service system meets the requirements, and the method specifically comprises the following steps:
Determining whether the service system has a problem or not according to the use data of the preferential push user, if so, determining that the service system does not meet the requirement, and if not, entering the next step;
determining the use data of different priority pushing users in different updating service scenes based on the use data of the priority pushing users, and determining the verification depth of different updating service scenes according to the number of the used priority pushing users in different updating service scenes and the use data of different priority pushing users;
And determining the comprehensive verification depth of the service system through the test depths of different updated service scenes, and determining whether the service system meets the requirements or not based on the comprehensive verification depth.
The further technical scheme is that whether the service system meets the requirements is determined based on the comprehensive verification depth, and the method specifically comprises the following steps:
And when the comprehensive verification depth is larger than the preset verification depth, determining that the service system meets the requirement.
In a second aspect, the present invention provides a computer system comprising: a communicatively coupled memory and processor, and a computer program stored on the memory and capable of running on the processor, characterized by: the processor executes the method for upgrading the service system when running the computer program.
Additional features and advantages of the invention will be set forth in the description which follows, and in part will be apparent from the description, or may be learned by practice of the invention as set forth hereinafter.
In order to make the above objects, features and advantages of the present invention more comprehensible, preferred embodiments accompanied with figures are described in detail below.
Drawings
The above and other features and advantages of the present invention will become more apparent by describing in detail exemplary embodiments thereof with reference to the attached drawings;
FIG. 1 is a flow chart of a method of customer care service system upgrade processing;
FIG. 2 is a flow chart of a method of determining update match of a user to a customer care service system;
FIG. 3 is a flow chart of a method of determining a test usage risk that matches a user of usage;
FIG. 4 is a flow chart for determining that a customer service system meets a demand;
FIG. 5 is a block diagram of a computer system.
Detailed Description
In order to make the technical solutions in the present specification better understood by those skilled in the art, the technical solutions in the embodiments of the present specification will be clearly and completely described below with reference to the drawings in the embodiments of the present specification, and it is obvious that the described embodiments are only some embodiments of the present specification, not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, shall fall within the scope of the present disclosure.
After the software system upgrading process is completed, due to the limitation of the test process scene, certain BUG problems are inevitably existed and are not found, so that if the software system upgrading process cannot be carried out in batches according to the use conditions of different users, the reliability of the software system upgrading process cannot be ensured. "
In order to solve the technical problems, the method and the device perform differentiated pushing processing on the historical use data of the users updating the service scene according to the use frequency of different users, and push the software system after upgrading processing to all the users when no problem exists.
Further explanation will be made below from two perspectives of the method class embodiment and the system class embodiment.
In order to solve the above-mentioned problems, according to one aspect of the present invention, as shown in fig. 1, there is provided a method for processing upgrade of a service system, which is characterized by comprising:
S1, determining an update service module of a service system based on upgrade data, and determining an update service scene of the service system through the update service module;
Further, the update service module determines according to the service module with update in the service system.
Specifically, the update service scenario is determined according to whether an update service module exists in the service scenario.
S2, acquiring historical use data of different users in different updated service scenes, determining update matching degrees of the different users and the service system based on the historical use data and matching use users, judging whether the number of the matching use users is larger than a user number limiting value, if so, entering a next step, if not, taking the matching use users as priority pushing users, and entering a step S4;
it should be noted that the historical usage data includes the number of times the user uses in different service scenarios and the duration of use of different times.
Specifically, as shown in fig. 2, the method for determining the update matching degree between the user and the service system includes:
determining the use times of the user in different update service scenes and the use time length of the user in different update service scenes according to the historical use data of the user in different update service scenes, and determining update matching coefficients of the user and different update service scenes of the consultation service system based on the use times of the user in different update service scenes and the use time length of the user in different use times;
And determining the update matching degree of the user and the service system according to the update matching coefficients of different update service scenes of the user and the service system.
Further, the value range of the update matching degree is between 0 and 1, wherein when the update matching degree of the user and the consultation service system is greater than a preset matching degree, the user is determined to be a matched user.
In another embodiment, the method for determining the update matching degree between the user and the service system comprises the following steps:
Determining that the user has used updated service scenes according to historical use data of the user in different updated service scenes, taking the updated service scenes as used service scenes, judging whether the number of the used service scenes of the user meets the requirement, if so, entering the next step, and if not, determining that the user does not belong to a matched user;
Determining the total number of times of use of the user in different service use scenes based on the number of times of use of the user in different service use scenes, judging whether the total number of times of use meets the requirement, if so, entering the next step, and if not, determining that the user does not belong to a matched user;
Determining updating matching coefficients of different service scenes of the user and the service system through the use times of the user in different service scenes and the use time of the different service scenes, judging whether the number of the service scenes with the updating matching coefficients not meeting the requirements meets the requirements or not, if so, entering the next step, and if not, determining that the user does not belong to the matched user;
And taking the service scenes with the update matching coefficients not meeting the requirements as unmatched service scenes, and determining the update matching degree of the user and the service system according to the number of the service scenes of the user, the update matching coefficients of different service scenes and the number of the service scenes of the service system.
In another embodiment, the method for determining the update matching degree between the user and the service system comprises the following steps:
determining the update processing complexity of different update service scenes according to the number of corresponding update service modules of different update service scenes, determining the update service scene used by the user according to the historical use data of the user in the different update service scenes, and judging whether the sum of the update processing complexity of the use service scenes meets the requirement or not by taking the update service scene as the use service scene, if so, entering the next step, and if not, determining that the user does not belong to a matched use user;
Determining update matching coefficients of different service scenes of the user and the service system according to the use times of the user in different service scenes and the use time of the different service scenes, judging whether the service scenes with the update matching coefficients not meeting the requirements exist or not, if yes, entering the next step, and if not, determining the update matching degree of the user and the service system according to the update matching coefficients of the user and the different service scenes and the update processing complexity of the different service scenes;
Taking a service scene with an update matching coefficient which does not meet the requirement as a non-matching service scene, judging whether the sum of the update processing complexity of the non-matching service scene meets the requirement, if so, entering the next step, and if not, determining that the user does not belong to a matching user;
and determining the update matching degree of the user and the service system based on the number of the service scenes used by the user, the update matching coefficient of the service scenes used by the user, the number of the service scenes updated by the service system and the update processing complexity of the service scenes updated by the service system.
S3, determining test use risks of different matched use users based on historical use data of the service system, and taking the matched use users as priority pushing users and entering a next step when the overall use risks of the matched use users meet requirements according to the number of the matched use users;
Further, the preset user number is determined according to the number of the updated service scenes, wherein the larger the number of the updated service scenes is, the larger the preset user number is.
Specifically, as shown in fig. 3, the method for determining the test usage risk of the matching usage user is as follows:
Determining updated user data amounts of the matched users under different historical use times based on the historical use data of the consultation service system, and determining risk assessment values of the matched users under different historical use times through the updated user data amounts;
And according to the risk evaluation values of the matching use users under different historical use times, the testing use risk of the matching use users is truly judged.
In another embodiment, the method for determining the test usage risk of the matching usage user is as follows:
Dividing the historical usage data into historical usage data in the updated business scenario and historical usage data in other business scenarios based on the historical usage data at the customer service system;
Dividing the historical usage times into updated usage times and other usage times by whether the usage of the updated service scene is included, and determining an overall risk evaluation value of the user at the updated usage times by the updated user data volume of the updated usage times in the updated service scene, the updated user data volume in the other service scene and the time intervals of different updated usage times;
and determining the total risk evaluation value of the user at the other use times according to the updated user data volume of the other use times in the other service scene and the time interval of different other use times, and combining the total risk evaluation value of the user at the updated use times to truly match the test use risk of the user.
Specifically, determining that the overall use risk of the matched use user meets the requirement specifically includes:
Dividing the matched users into risk users and general risk users through different matched users' test use risks and preset risk thresholds;
Determining the total test risk of the risk using users and the total test risk of the general risk users according to the test using risk of different risk using users, the number of the risk using users, the test using risk of different general risk users and the number of the general risk users respectively;
And determining the overall use risk of the matched use user based on the overall test risk of the risk use user and the overall test risk of the general risk user, and determining whether the overall use risk of the matched use user meets the requirement or not according to a preset risk limit value.
It should be noted that, the matching users are classified into risk users and general risk users by different testing use risks of the matching users and preset risk thresholds, which specifically includes:
When the test use risk of the matched use user is larger than a preset risk threshold, determining the matched use user as a risk use user;
and when the test use risk of the matched use user is not greater than a preset risk threshold, determining that the matched use user is a general risk user.
Further, determining whether the overall use risk of the matched use user meets the requirement according to a preset risk limit value specifically includes:
and when the total use risk of the matched use users is smaller than the preset risk limit value, determining that the total use risk of the matched use users meets the requirement.
Specifically, when the overall use risk of the matched use users does not meet the requirement, determining the priority pushing users based on the number of the specified users and the test use risks of different matched use users.
In a further embodiment, determining that the overall usage risk of the matching usage user meets the requirements specifically comprises:
Determining the sum of the test use risks of the matched users through the test use risks of different matched users and the number of the matched users, judging whether the sum of the test use risks of the matched users meets the requirements, if so, entering the next step, and if not, determining that the overall use risk of the matched users does not meet the requirements;
dividing the matched users into risk users and general risk users through testing use risks of different matched users and preset risk thresholds, judging whether the number of the risk users meets the requirements, if so, entering the next step, and if not, determining that the overall use risks of the matched users do not meet the requirements;
Judging whether the total testing risks of the risk using users meet requirements or not according to the testing using risks of different risk using users and the total testing risks of the risk using users, if so, entering the next step, and if not, determining that the total using risks of the matched using users do not meet the requirements;
And determining the total test risk of the general risk users through the test use risks of different general risk users and the number of the general risk users, determining the total use risk of the matched use users based on the total test risk of the risk use users and the total test risk of the general risk users, and determining whether the total use risk of the matched use users meets the requirement or not according to a preset risk limiting value.
In a further embodiment, determining that the overall usage risk of the matching usage user meets the requirements specifically comprises:
S31, dividing the matched users into different risk intervals through the test use risks of the different matched users, determining the maximum value of the number of users in the different risk intervals through the test use risk ranges of the different risk intervals, and determining the initial evaluation risk of the different risk intervals according to the number of the matched users and the maximum value of the number of the users;
S32, judging whether the number of risk intervals of which the initial evaluation risk does not meet the requirement meets the requirement, if so, entering the next step, and if not, determining that the overall use risk of the matched user does not meet the requirement;
S33, determining the comprehensive use risks of the users in different risk intervals according to the number of the matched use users in different risk intervals and the test use risks of the different matched use users, judging whether the risk intervals with the comprehensive use risks not meeting the requirements of the users exist or not, if so, entering the next step, and if not, entering the step S35;
S34, taking a risk interval of which the comprehensive use risk of the user does not meet the requirement as a screening risk interval, judging whether the number of the screening risk intervals meets the requirement, if so, entering the next step, and if not, determining that the overall use risk of the matched use user does not meet the requirement;
S35, determining weight values of different screening risk intervals according to the testing use risk ranges of the different screening risk intervals, determining interval risk evaluation values of the screening risk intervals by combining comprehensive use risks of users of the different screening risk intervals, judging whether the interval risk evaluation values of the screening risk intervals meet requirements, if yes, entering a next step, and if no, determining that the overall use risk of the matched use users does not meet the requirements;
S36, acquiring comprehensive use risks of users in different risk intervals, determining the overall use risks of the matched use users by combining the number of the matched use users and the interval risk evaluation quantity of the screening risk intervals, and determining whether the overall use risks of the matched use users meet requirements or not by combining a preset risk limiting value.
And S4, pushing the service system to a priority pushing user, and pushing the service system to all users when the service system meets the requirements according to the use data of the priority pushing user.
It should be noted that, as shown in fig. 4, determining that the service system satisfies the requirement specifically includes:
Determining whether the service system has a problem or not according to the use data of the preferential push user, if so, determining that the service system does not meet the requirement, and if not, entering the next step;
determining the use data of different priority pushing users in different updating service scenes based on the use data of the priority pushing users, and determining the verification depth of different updating service scenes according to the number of the used priority pushing users in different updating service scenes and the use data of different priority pushing users;
And determining the comprehensive verification depth of the service system through the test depths of different updated service scenes, and determining whether the service system meets the requirements or not based on the comprehensive verification depth.
Further, determining whether the service system satisfies a requirement based on the comprehensive verification depth specifically includes:
And when the comprehensive verification depth is larger than the preset verification depth, determining that the service system meets the requirement.
In another embodiment, determining that the service system meets the requirements specifically includes:
Determining whether the service system has a problem or not according to the use data of the preferential push user, if so, determining that the service system does not meet the requirement, and if not, entering the next step;
Determining the use data of different priority pushing users in different updating service scenes based on the use data of the priority pushing users, judging whether the number of the used priority pushing users does not meet the required updating service scenes meets the requirements or not, if so, entering the next step, and if not, determining that the service system does not meet the requirements;
Determining verification depths of different update service scenes according to the number of the priority pushing users used by the different update service scenes and the use data of the different priority pushing users, judging whether the update service scenes with the verification depths not meeting the requirements exist or not, if yes, entering the next step, and if not, determining that the service system meets the requirements;
Taking the updated service scene with the verification depth not meeting the requirement as an underverified service scene, judging whether the quantity of the underverified service scenes meets the requirement, if so, entering the next step, and if not, determining that the service system does not meet the requirement;
And determining the comprehensive verification depth of the service system through the test depths of different updated service scenes, and determining whether the service system meets the requirements or not based on the comprehensive verification depth.
System class embodiment
In another aspect, as shown in FIG. 5, the present invention provides a computer system comprising: a communicatively coupled memory and processor, and a computer program stored on the memory and capable of running on the processor, characterized by: the processor executes the method for upgrading the service system when running the computer program.
The service system upgrading processing method specifically comprises the following steps:
determining an update service module of a service system based on the upgrade data, and determining an update service scene of the service system through the update service module;
Acquiring historical use data of different users in different updated service scenes, determining update matching degrees of the different users and the service system and matched users based on the historical use data, and entering a next step when the number of matched users is larger than a limit value of the number of users;
Determining the sum of the test use risks of the matched users through the test use risks of different matched users and the number of the matched users, judging whether the sum of the test use risks of the matched users meets the requirements, if so, entering the next step, and if not, determining that the overall use risk of the matched users does not meet the requirements;
dividing the matched users into risk users and general risk users through testing use risks of different matched users and preset risk thresholds, judging whether the number of the risk users meets the requirements, if so, entering the next step, and if not, determining that the overall use risks of the matched users do not meet the requirements;
Judging whether the total testing risks of the risk using users meet requirements or not according to the testing using risks of different risk using users and the total testing risks of the risk using users, if so, entering the next step, and if not, determining that the total using risks of the matched using users do not meet the requirements;
Determining the total test risk of the general risk users through the test use risks of different general risk users and the number of the general risk users, determining the total use risk of the matched use users based on the total test risk of the risk use users and the total test risk of the general risk users, determining whether the total use risk of the matched use users meets the requirements or not according to a preset risk limiting value, and taking the matched use users as priority pushing users when the total use risk of the matched use users meets the requirements, and entering the next step;
pushing the service system to a priority pushing user, determining whether the service system has a problem or not according to the use data of the priority pushing user, if so, determining that the service system does not meet the requirement, and if not, entering the next step;
Determining the use data of different priority pushing users in different updating service scenes based on the use data of the priority pushing users, judging whether the number of the used priority pushing users does not meet the required updating service scenes meets the requirements or not, if so, entering the next step, and if not, determining that the service system does not meet the requirements;
Determining verification depths of different update service scenes according to the number of the priority pushing users used by the different update service scenes and the use data of the different priority pushing users, judging whether the update service scenes with the verification depths not meeting the requirements exist or not, if yes, entering the next step, and if not, determining that the service system meets the requirements;
Taking the updated service scene with the verification depth not meeting the requirement as an underverified service scene, judging whether the quantity of the underverified service scenes meets the requirement, if so, entering the next step, and if not, determining that the service system does not meet the requirement;
And determining the comprehensive verification depth of the service system through the test depths of different updated service scenes, determining whether the service system meets the requirements or not based on the comprehensive verification depth, and pushing the service system to all users when the service system meets the requirements.
Through the above embodiments, the present invention has the following beneficial effects:
1. According to the invention, the update matching degree of different users and the service system is determined based on the historical use data, and the matched use users are realized, so that the accurate evaluation of the update matching condition of the users and the service system is realized from the angle of the historical use data of the service system, a foundation is laid for further carrying out the updated service system pushing of the distribution times, and the technical problem of data safety caused by unified pushing is avoided.
2. In the invention, whether the service system meets the requirement is determined according to the use data of the priority push user, so that not only is the problem in the use data of the priority push user singly considered, but also the difference of the verification depths of different updated service scenes is fully considered by combining the use data of the priority push user, and the safety and the reliability of the updating processing of the service system are ensured.
In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for apparatus, devices, non-volatile computer storage medium embodiments, the description is relatively simple, as it is substantially similar to method embodiments, with reference to the section of the method embodiments being relevant.
The foregoing describes specific embodiments of the present disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
The foregoing is merely one or more embodiments of the present description and is not intended to limit the present description. Various modifications and alterations to one or more embodiments of this description will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, or the like, which is within the spirit and principles of one or more embodiments of the present description, is intended to be included within the scope of the claims of the present description.
Claims (10)
1. The service system upgrading processing method is characterized by comprising the following steps:
S1, determining an update service module of a service system based on upgrade data, and determining an update service scene of the service system through the update service module;
S2, acquiring historical use data of different users in different updated service scenes, determining update matching degrees of the different users and the service system based on the historical use data and matching use users, judging whether the number of the matching use users is larger than a user number limiting value, if so, entering a next step, if not, taking the matching use users as priority pushing users, and entering a step S4;
S3, determining test use risks of different matched use users based on historical use data of the service system, and taking the matched use users as priority pushing users and entering a next step when the overall use risks of the matched use users meet requirements according to the number of the matched use users;
and S4, pushing the service system to a priority pushing user, and pushing the service system to all users when the service system meets the requirements according to the use data of the priority pushing user.
2. The method of claim 1, wherein the update service module is determined based on a service module in the service system for which an update exists.
3. The method for upgrading a customer service system according to claim 1, wherein the update service scenario is determined according to whether an update service module exists in the service scenario.
4. The method of claim 1, wherein the historical usage data includes a number of uses of the user in different business scenarios and a duration of the different number of uses.
5. The method for processing the upgrade of the customer service system according to claim 1, wherein the method for determining the update matching degree between the user and the customer service system comprises the following steps:
determining the use times of the user in different update service scenes and the use time length of the user in different update service scenes according to the historical use data of the user in different update service scenes, and determining update matching coefficients of the user and different update service scenes of the consultation service system based on the use times of the user in different update service scenes and the use time length of the user in different use times;
And determining the update matching degree of the user and the service system according to the update matching coefficients of different update service scenes of the user and the service system.
6. The method for upgrading a customer service system according to claim 5, wherein the update matching degree has a value ranging from 0 to 1, and wherein the user is determined to be a matched user when the update matching degree of the user and the customer service system is greater than a preset matching degree.
7. The method for processing the upgrade of the customer service system according to claim 1, wherein the preset number of users is determined according to the number of updated service scenes, wherein the larger the number of updated service scenes is, the larger the preset number of users is.
8. The method for processing upgrade of customer service system according to claim 1, wherein the method for determining the test usage risk of the matching usage user is:
Determining updated user data amounts of the matched users under different historical use times based on the historical use data of the consultation service system, and determining risk assessment values of the matched users under different historical use times through the updated user data amounts;
And according to the risk evaluation values of the matching use users under different historical use times, the testing use risk of the matching use users is truly judged.
9. The method for processing the upgrade of the service system according to claim 1, wherein determining that the service system meets the requirements specifically comprises:
Determining whether the service system has a problem or not according to the use data of the preferential push user, if so, determining that the service system does not meet the requirement, and if not, entering the next step;
determining the use data of different priority pushing users in different updating service scenes based on the use data of the priority pushing users, and determining the verification depth of different updating service scenes according to the number of the used priority pushing users in different updating service scenes and the use data of different priority pushing users;
And determining the comprehensive verification depth of the service system through the test depths of different updated service scenes, and determining whether the service system meets the requirements or not based on the comprehensive verification depth.
10. A computer system, comprising: a communicatively coupled memory and processor, and a computer program stored on the memory and capable of running on the processor, characterized by: the processor, when executing the computer program, performs a method of service system upgrade processing as claimed in any one of claims 1-9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410582814.4A CN118151974A (en) | 2024-05-11 | 2024-05-11 | Method and system for upgrading service system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410582814.4A CN118151974A (en) | 2024-05-11 | 2024-05-11 | Method and system for upgrading service system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN118151974A true CN118151974A (en) | 2024-06-07 |
Family
ID=91289009
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202410582814.4A Pending CN118151974A (en) | 2024-05-11 | 2024-05-11 | Method and system for upgrading service system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN118151974A (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017076176A1 (en) * | 2015-11-02 | 2017-05-11 | 阿里巴巴集团控股有限公司 | Service processing method and apparatus |
| CN110493336A (en) * | 2019-08-15 | 2019-11-22 | 问问智能信息科技有限公司 | The method and apparatus at target user end are determined in a kind of gray scale issuing process |
| US20220094605A1 (en) * | 2020-09-18 | 2022-03-24 | Accenture Global Solutions Limited | Targeted content selection using a federated learning system |
| US20220245536A1 (en) * | 2021-01-29 | 2022-08-04 | Boe Technology Group Co., Ltd. | Method and device for updating ai models, and storage medium |
| US20230418584A1 (en) * | 2022-06-28 | 2023-12-28 | Microsoft Technology Licensing, Llc | Controlling operating system upgrades based on usage data of client device |
| CN117573728A (en) * | 2024-01-17 | 2024-02-20 | 杭银消费金融股份有限公司 | Information dimension-increasing processing method and system for data information |
-
2024
- 2024-05-11 CN CN202410582814.4A patent/CN118151974A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017076176A1 (en) * | 2015-11-02 | 2017-05-11 | 阿里巴巴集团控股有限公司 | Service processing method and apparatus |
| CN110493336A (en) * | 2019-08-15 | 2019-11-22 | 问问智能信息科技有限公司 | The method and apparatus at target user end are determined in a kind of gray scale issuing process |
| US20220094605A1 (en) * | 2020-09-18 | 2022-03-24 | Accenture Global Solutions Limited | Targeted content selection using a federated learning system |
| US20220245536A1 (en) * | 2021-01-29 | 2022-08-04 | Boe Technology Group Co., Ltd. | Method and device for updating ai models, and storage medium |
| US20230418584A1 (en) * | 2022-06-28 | 2023-12-28 | Microsoft Technology Licensing, Llc | Controlling operating system upgrades based on usage data of client device |
| CN117573728A (en) * | 2024-01-17 | 2024-02-20 | 杭银消费金融股份有限公司 | Information dimension-increasing processing method and system for data information |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10943186B2 (en) | Machine learning model training method and device, and electronic device | |
| CN110362999B (en) | Method and device for detecting account use abnormity | |
| CN111160749A (en) | Method and device for evaluating information quality and fusing information | |
| CN104125584A (en) | Service index realization prediction method aiming at network service and apparatus thereof | |
| CN113139687B (en) | Method and device for predicting credit card user default | |
| US11250368B1 (en) | Business prediction method and apparatus | |
| CN110888625B (en) | Method for controlling code quality based on demand change and project risk | |
| CN109583731B (en) | Risk identification method, device and equipment | |
| CN111199469A (en) | User payment model generation method and device and electronic equipment | |
| CN109633448A (en) | Identify the method, apparatus and terminal device of cell health state | |
| CN112884569A (en) | Credit assessment model training method, device and equipment | |
| CN112990583A (en) | Method and equipment for determining mold entering characteristics of data prediction model | |
| CN117333290B (en) | Integrated multi-scale wind control model construction method | |
| CN114139931A (en) | Enterprise data evaluation method and device, computer equipment and storage medium | |
| CN109740335A (en) | The classification method and device of identifying code operation trace | |
| CN118151974A (en) | Method and system for upgrading service system | |
| CN112887371A (en) | Edge calculation method and device, computer equipment and storage medium | |
| CN111738824A (en) | Method, device and system for screening financial data processing modes | |
| CN114697127B (en) | Service session risk processing method based on cloud computing and server | |
| CN112712270B (en) | Information processing method, device, equipment and storage medium | |
| CN114298829A (en) | Data processing method and device for credit assessment | |
| CN114298823A (en) | Data processing method and device for model construction | |
| CN114372867A (en) | User credit verification and evaluation method and device and computer equipment | |
| CN110322055B (en) | Method and system for improving grading stability of data risk model | |
| CN112468673A (en) | Online image transmission identification method and system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination |