Service change method, device, electronic device and storage medium

Abstract

The present application provides a service change method, device, electronic device and storage medium, the method comprising: determining the impact scope of the service change according to the service change application of the user. If the impact scope of the service change is within the user authority of the user, the service change is executed. If the impact scope of the service change exceeds the user authority of the user, the service change is stopped. The user authority of the user represents the impact scope allowed by the service change of the user. By judging whether the impact scope of the service change of the user is within the user authority, it is decided whether to continue the service change, thereby avoiding abnormal changes and achieving efficient, standardized and safe service changes.

Description

Technical Field

[0001] The present application relates to the field of communications, and in particular to a service change method, device, electronic device and storage medium. Background Art

[0002] At present, with the continuous development of the information age, communication technology means are being continuously optimized with the goal of enrichment and diversification to meet the business needs of different users.

[0003] However, current business changes have problems such as low digital implementation, non-standard change processes, lack of identification, analysis and response to change risks, and lack of analysis of change data. These problems will make business changes more prone to abnormal changes and the risk of untimely problem handling.

[0004] Therefore, how to achieve efficient, standardized and secure business changes has become an urgent problem that needs to be solved. Summary of the invention

[0005] The present application provides a service change method, device, electronic device and storage medium for optimizing the service change process.

[0006] In a first aspect, the present application provides a service change method, comprising: determining the scope of impact of the service change based on the user's service change application; if the scope of impact of the service change is within the user rights of the user, executing the service change; if the scope of impact of the service change exceeds the user rights of the user, stopping the service change; wherein the user rights of the user represent the scope of impact allowed by the service change of the user.

[0007] In one possible implementation, determining the impact scope of the business change based on the user's business change application includes: obtaining change application information in the business change application; pushing an operational interface corresponding to the user's user authority to the user, and obtaining the change parameters of the user under the operational interface; performing a multi-factor analysis on the change application information to determine the impact scope of the business change; wherein the factors include the number of affected tariffs, the number of affected users, the impact on tariffs in other provinces, production test consistency, and expected impact consistency.

[0008] In a possible implementation, after obtaining the change parameters of the user in the operational interface, it also includes: performing the following checks on the change parameters: data check, the data check is used to check the data format of the change parameters, the data check includes primary key conflict check, field length check and field type check; business check, the business check is used to check whether the change parameters meet the business rules; permission check, the permission check is used to check whether the change parameters meet the predetermined regional impact rules and parameter quantity rules; record-level lock check, the record-level lock check is used to check whether there are locked statements in the statement of changing the parameters.

[0009] In one possible implementation, the executing business change includes: in a verification environment, verifying and simulating the correctness of the business change, and checking whether it meets the change expectations to obtain the simulated impact scope of the business change; if the change is correct and meets the change expectations and the simulated impact scope is consistent with the impact scope of the business change, then executing the business change.

[0010] In one possible implementation, the method further includes: monitoring user call records and billing bills of subscription charges before and after the service change; and based on the user call records and billing bills of subscription charges before and after the service change, if it is determined that the service change is an abnormal change, performing a change fuse on the abnormal change.

[0011] In one possible implementation, based on the user call records and billing bills of the subscription charges before and after the service change, if the service change is judged to be an abnormal change, a change fuse is performed on the abnormal change, including: organizing the user call records and billing bills of the known abnormal subscription charges into audit points; matching the user call records and billing bills of the subscription charges after the service change with the audit points, if the match is successful, judging that the service change is an abnormal change, and performing a change fuse on the abnormal change.

[0012] In a possible implementation, the method further includes: generating and storing a change record of the business change; mining and analyzing the currently stored business change records, and presenting them through visual statements and reports.

[0013] In a second aspect, the present application provides a business change device, comprising: an acquisition module, used to determine the impact scope of the business change based on the user's business change application; a processing module, used to execute the business change if the impact scope of the business change is within the user authority of the user; the processing module is also used to stop the business change if the impact scope of the business change exceeds the user authority of the user; wherein the user authority of the user represents the impact scope allowed by the user's business change.

[0014] In one possible implementation, the device also includes: an acquisition module, which is specifically used to obtain change application information in the business change application; the acquisition module is also specifically used to push an operational interface corresponding to the user's user authority to the user, and obtain the change parameters of the user under the operational interface; a processing module, which is specifically used to perform a multi-factor analysis on the change application information to determine the impact scope of this business change; wherein the factors include the number of affected tariffs, the number of affected users, the impact on tariffs in other provinces, production test consistency, and expected impact consistency.

[0015] In one possible implementation, the device also includes: a processing module, which is also used to perform the following checks on the change parameters: data verification, the data verification is used to verify the data format of the change parameters, the data verification includes primary key conflict verification, field length verification and field type verification; business verification, the business verification is used to verify whether the change parameters meet business rules; permission verification, the permission verification is used to verify whether the change parameters meet predetermined regional impact rules and parameter quantity rules; record-level lock verification, the record-level lock verification is used to check whether there are locked statements in the statement of changing parameters.

[0016] In one possible implementation, the device also includes: a processing module, which is specifically used to simulate the business change in a verification environment to obtain a simulated impact range of the business change; the processing module is also specifically used to execute the business change if the simulated impact range is consistent with the impact range of the business change.

[0017] In one possible implementation, the device also includes: a monitoring module, used to monitor user call records and billing bills of subscription charges before and after the service change; the monitoring module is also used to perform a change fuse on the abnormal change if it is determined that the service change is an abnormal change based on the user call records and billing bills of subscription charges before and after the service change.

[0018] In one possible implementation, the device also includes: a monitoring module, which is specifically used to organize user call records and billing bills of known abnormal subscription charges into audit points; the monitoring module is also specifically used to match the user call records and billing bills of the subscription charges after the service change with the audit points. If the match is successful, it is determined that the service change is an abnormal change, and a change fuse is performed on the abnormal change.

[0019] In a possible implementation, the device also includes: a cockpit module, which is used to generate and store change records of the business changes; the cockpit module is also used to mine and analyze the currently stored business change records and display them through visual statements and reports.

[0020] In a third aspect, the present application provides an electronic device comprising: a processor, and a memory communicatively connected to the processor; the memory stores computer-executable instructions; the processor executes the computer-executable instructions stored in the memory to implement any method described in any one of the first aspects.

[0021] In a fourth aspect, the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are executed by a processor as described in any one of the methods in the first aspect.

[0022] The service change method, device, electronic device and storage medium provided in the present application determine the scope of impact of the service change according to the service change application of the user. If the scope of impact of the service change is within the user rights of the user, the service change is executed. If the scope of impact of the service change exceeds the user rights of the user, the service change is stopped. Among them, the user rights of the user represent the scope of impact allowed by the service change of the user. The above scheme determines whether to continue the service change by judging whether the scope of impact of the service change of the user is within the user's rights, thereby avoiding abnormal changes and realizing efficient, standardized and safe service changes. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0024] Figure 1 A schematic diagram of an application scenario of a business change method provided in this application;

[0025] Figure 2 A flowchart of a service change method provided in Example 1 of the present application;

[0026] Figure 3 A flowchart of a service change method provided in Embodiment 2 of the present application;

[0027] Figure 4 A flowchart of a service change method provided in Embodiment 3 of the present application;

[0028] Figure 5 This is a structural example diagram of a service change device provided in Embodiment 4 of the present application;

[0029] Figure 6 A device block diagram of a service change device provided in Embodiment 6 of the present application;

[0030] Figure 7 This is a schematic diagram of the structure of an electronic device provided in Example 7 of the present application.

[0031] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0032] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0033] First, let’s explain the nouns involved:

[0034] Change fuse: After the system receives an abnormal change, if the number of subscribers with abnormal changes exceeds the automatic fuse threshold, the tariff fuse will be triggered

[0035] Figure 1 A schematic diagram of an application scenario of a service change method provided in an embodiment of the present application, such as Figure 1 As shown, the interaction between the terminal 1 and the service change device 2, and the terminal interface during the service change process.

[0036] In actual applications, the service change device can be a server. Take the illustrated scenario as an example: a user submits a service change application through terminal 1, which is automatically sent to service change device 2. Service change device 2 is used to execute the service change if the impact range of the service change is within the user rights of the user, and send the service change result to terminal 1, thereby avoiding abnormal changes and achieving efficient, standardized and safe service changes.

[0037] In actual application, if the service change device 2 detects that the impact scope of the service change exceeds the user authority of the user, the service change is stopped and the service change failure and the service change information that needs to be modified are sent to the user.

[0038] The scheme of the embodiments of the present application is introduced by way of examples in combination with the following embodiments.

[0039] Embodiment 1

[0040] Figure 2 A flowchart of a service change method provided in Embodiment 1 of the present application, the method comprising the following steps:

[0041] S101. Determine the impact scope of the service change based on the user's service change application;

[0042] S102: If the impact scope of the service change is within the user rights of the user, the service change is executed;

[0043] S103. If the impact scope of the current service change exceeds the user rights of the user, stop the service change;

[0044] The user rights of the user represent the scope of influence allowed by the service change of the user.

[0045] As an example, the execution subject of this embodiment may be a service change device, and there are many ways to implement the service change device. For example, it may be program software, or a medium storing relevant computer programs, such as a USB flash drive, etc.; or, the device may also be a physical device integrated or installed with relevant computer programs, such as a chip, a smart terminal, a computer, a server, etc.

[0046] In an example, S101 may specifically include: obtaining change application information in the business change application; pushing an operational interface corresponding to the user's user authority to the user, and obtaining the change parameters of the user under the operational interface; performing a multi-factor analysis on the change application information to determine the impact scope of this business change; wherein the factors include the number of affected tariffs, the number of affected users, the impact on tariffs in other provinces, production test consistency, and expected impact consistency.

[0047] Optionally, the change application information includes but is not limited to: reason for change, change classification, purpose of change, change expectation and change requirement code.

[0048] Optionally, the functions of the operational interface include but are not limited to: adding, deleting and modifying; wherein, when the user chooses to add, the system provides an Excel template and generates parameters by importing Excel. When modifying is selected, the system provides modifiable fields and query fields for the user to select in conjunction, and the user enters the parameter value. The system automatically identifies the primary key and primary key value according to the operation table, generates parameters by specific logic, and ensures that one parameter only affects one record. When deleting is selected, the system provides queryable fields for the user to select in conjunction, and the user enters the parameter value. The system automatically identifies the primary key and primary key value according to the operation table, generates parameters by specific logic, and ensures that one parameter only affects one record.

[0049] In one example, after obtaining the change parameters of the user in the operational interface, it also includes: performing the following checks on the change parameters: data check, the data check is used to verify the data format of the change parameters, the data check includes primary key conflict check, field length check and field type check; business check, the business check is used to verify whether the change parameters meet the business rules; permission check, the permission check is used to verify whether the change parameters meet the predetermined regional impact rules and parameter quantity rules; record-level lock check, the record-level lock check is used to check whether there are locked statements in the statement of changing the parameters.

[0050] Based on the above implementation, if the change parameter passes the verification, the change parameter is submitted; if the change parameter does not pass the verification, the service change is stopped.

[0051] In an example, the execution of the business change may specifically include: in a verification environment, verifying the correctness of the business change by simulating it, and checking whether it meets the change expectations to obtain the simulated impact scope of the business change; if the change is correct and meets the change expectations and the simulated impact scope is consistent with the impact scope of the business change, then executing the business change.

[0052] In combination with the scenario example, the factors affecting the tariff number are analyzed to obtain the range of the tariff numbers affected by the current business change simulation; the factors affecting other provinces are analyzed to obtain whether there are businesses that affect other provinces in the current business change simulation; the production test consistency factors are analyzed to obtain whether the businesses affected by the current business change simulation are consistent in the production and test environments; the user number factors are analyzed to obtain the range of the number of users corresponding to the businesses affected by the current business change simulation. If the simulated impact range is consistent with the impact range of the business change, the business change is executed. Otherwise, the business change is stopped.

[0053] For example, assuming that the impact range of the service change simulation is 5 rates, and the impact range of the service change is 3 rates, if the simulated impact range exceeds the impact range of the service change, the service change will be stopped.

[0054] In one example, the business change method further includes: generating and storing a change record of the business change; mining and analyzing the currently stored business change records, and presenting them through visual statements and reports.

[0055] In one example, the business change method further includes: mining and analyzing currently stored business change records, and performing business health analysis of each province through weight calculation.

[0056] In the service change method provided in this embodiment, the scope of influence of the service change is determined according to the service change application of the user. If the scope of influence of the service change is within the user rights of the user, the service change is executed. If the scope of influence of the service change exceeds the user rights of the user, the service change is stopped. By judging whether the scope of influence of the service change of the user is within the user's rights, it is decided whether to continue the service change, thereby avoiding abnormal changes and achieving efficient, standardized and safe service changes.

[0057] Embodiment 2

[0058] Figure 3 A flow chart of a service change method provided in Embodiment 2 of the present application is provided. Based on Embodiment 1, this embodiment illustrates an example of the monitoring process of the service change method. Figure 3 As shown, based on the first embodiment, the method further includes:

[0059] S104, monitoring the user's call records and billing bills of the subscription charges before and after the service change;

[0060] S105. Based on the user call records and billing bills of the subscription charges before and after the service change, if it is determined that the service change is an abnormal change, a change fuse is executed for the abnormal change.

[0061] In actual applications, the user call records and billing bills for the subscription charges before and after the service change include changes in monthly rental discounts, changes without cumulative identification, and changes with cumulative identification. The following is an introduction to the change fuse with multiple examples.

[0062] In one example, the monthly rent discount change specifically includes: obtaining three subscribers of the service as sample users; calling the real-time billing interface to re-bill the monthly rent for the sample users; and returning the user call records, billing bills, and user information of the subscription rates before and after the user change.

[0063] In combination with the scenario example, the monitoring of the change of the monthly rent discount class randomly selects three subscribers from the users of the monthly rent discount class service as sample users. The monthly rent of the sample users is re-issued in real time according to the monthly rent discount class service, and the user call list and billing bill of the user subscription rate before and after the user change and the user information obtained by simulating the monthly rent re-issue are returned. If the user call list and billing bill of the subscription rate before and after the change are normal, the monthly rent discount class service is normal.

[0064] Through the method in this example, monthly rental discount services can be monitored in real time, and if there are any abnormal changes, feedback can be given in a timely manner.

[0065] In another example, the non-cumulative identification type change specifically includes: obtaining the subscribers of the target tariff to be monitored for change as sample users; obtaining the detailed bill of the sample user, and matching the tariff code with the batch price track field of the user detailed bill; and returning the matched user detailed bill and billing invoice.

[0066] Combined with the scenario example, for the monitoring of changes without cumulative identification, select the subscribers of the target tariff for change monitoring as sample users. Obtain the traffic details of the sample user after the change is completed, and match the tariff code with the batch price track field of the user details. If it is matched, it means that the user has used this tariff after the tariff is modified. The correctness of the tariff change can be judged by the billing accuracy of this user, and the monthly discount service is normal. The timed collection of user call records and billing bills of the sample user's subscription tariff before and after the change is only triggered regularly during the service idle period.

[0067] In another example, the cumulative identification type change specifically includes: obtaining users whose usage changes in the cumulative table after the change is completed as sample users; the monitoring module obtains the detailed list of the sample user, and the batch price track field of the user detailed list matches the tariff code; and returns the matched user, detailed list and billing bill.

[0068] In combination with the scenario example, the monitoring of cumulative identification changes uses users with usage changes in the cumulative table after the change is completed as sample users. The usage change indicates that the user has used this tariff after the tariff change is completed. The correctness of the tariff change can be judged by the billing accuracy of this user.

[0069] Through the method in this example, changes can be monitored in the current business. By screening the current business, the scope of sample selection can be narrowed to improve efficiency.

[0070] In an example, S105 may specifically include: the monitoring module organizes the user and tariff exception types and scenarios into audit points; the monitoring module matches the user call records and billing bills of the subscription tariffs after the service change with the audit points. If the match is successful, it is determined that the service change is an abnormal change, and a change fuse is executed on the abnormal change.

[0071] In practical applications, the change fuse includes rate-level fuse and user-level fuse. The change fuse is introduced below with examples.

[0072] In one example, the rate-level fuse specifically includes: adding known abnormal rates to an intermediate table, and if the user's services include services in the intermediate table, stopping charging the user who has subscribed to the abnormal rates.

[0073] Taking the scenario example as an example, known abnormal charges are added to the intermediate table, and the user information of the user is matched with the intermediate table. If the match is successful, it is considered that the user has an abnormal change in service, and the charge level fuse is performed on the abnormal change in service; the charge level fuse specifically includes: stopping billing for the user with the abnormal change in charge.

[0074] In another example, the user-level fuse specifically includes: the monitoring module adds known abnormal users into the intermediate table, and the abnormal users refer to users whose abnormal tariffs are normal except for one abnormal billing branch; if the user information of the user who subscribes to the tariff happens to match this abnormal billing branch, only a part of the users will be temporarily blown without blowing the tariff, thereby ensuring that users with normal billing rules are processed normally.

[0075] Taking the scenario example as an example, known abnormal users are added to the intermediate table, and the users are matched with the intermediate table. If the match is successful, the user is considered to be an abnormal user, and a user-level fuse is performed on the user; the user-level fuse specifically includes: marking the user's call record as an error record, and not charging the user for the time being.

[0076] Based on the above implementation, the method of the intermediate table can accurately and quickly identify abnormal change services or abnormal users, and perform circuit breaking in a targeted manner, thereby improving the efficiency of change circuit breaking.

[0077] In the service change method provided in this embodiment, the user call bill and the billing bill of the subscription rate before and after the service change are monitored. According to the user call bill and the billing bill of the subscription rate before and after the service change, if the service change is judged to be an abnormal change, the abnormal change is subjected to a change fuse. By real-time monitoring of the service change, the abnormal change is discovered and the change fuse is subjected to a change fuse.

[0078] Embodiment 3

[0079] Figure 4 A flowchart of a service change method provided in Example 3 of the present application is shown as follows: Figure 4 As shown, this embodiment is described by way of example in combination with the aforementioned implementation manner, and specifically includes the following steps:

[0080] S201. Determine the impact scope of the local service change according to the service change application of the user;

[0081] S202: If the impact scope of the current service change is within the user rights of the user, the service change is executed;

[0082] S203: If the impact scope of the current service change exceeds the user rights of the user, stop the service change;

[0083] S204, monitoring the user's call records and billing bills of the subscription charges before and after the service change;

[0084] S205: Based on the user call records and billing bills of the subscription charges before and after the service change, if it is determined that the service change is an abnormal change, a change fuse is performed on the abnormal change.

[0085] In the service change method provided in this embodiment, the scope of influence of the service change is determined according to the service change application of the user. If the scope of influence of the service change is within the user rights of the user, the service change is executed. If the scope of influence of the service change exceeds the user rights of the user, the service change is stopped. Monitor the user call records and billing bills of the subscription charges before and after the service change. Based on the user call records and billing bills of the subscription charges before and after the service change, if the service change is determined to be an abnormal change, a change fuse is executed for the abnormal change. By judging whether the scope of influence of the user's service change is within the user's authority, it is decided whether to continue the service change, thereby avoiding abnormal changes and realizing efficient, standardized and safe service changes. Through real-time monitoring of service changes, abnormal changes are discovered and change fuses are executed.

[0086] Embodiment 4

[0087] Figure 5 A schematic diagram of the structure of a service change device provided in Embodiment 4 of the present application, such as Figure 5 As shown, the service change device includes: an acquisition module 61, a processing module 62 and a processing module 63.

[0088] The acquisition module 61 is used to determine the impact scope of the current service change according to the user's service change application;

[0089] The processing module 62 is used to execute the service change if the impact range of the service change is within the user rights of the user;

[0090] The processing module 62 is used to stop the service change if the impact scope of the service change exceeds the user rights of the user;

[0091] The user rights of the user represent the scope of influence allowed by the service change of the user.

[0092] As an example, there are many ways to implement the service change device. For example, it can be a program software, or a medium storing a relevant computer program, such as a USB flash drive, etc.; or, the device can also be a physical device integrated or installed with a relevant computer program, such as a chip, a smart terminal, a computer, a server, etc.

[0093] In an example, the acquisition module 61 is specifically used to: obtain the change application information in the business change application; push the operational interface corresponding to the user's user authority to the user, and obtain the change parameters of the user under the operational interface; perform a multi-factor analysis on the change application information to determine the impact scope of this business change; wherein the factors include the number of affected tariffs, the number of affected users, the impact on tariffs in other provinces, production test consistency, and expected impact consistency.

[0094] Optionally, the change application information includes but is not limited to: reason for change, change classification, purpose of change, change expectation and change requirement code.

[0095] Optionally, the functions of the operational interface include but are not limited to: adding, deleting and modifying; wherein, when the user chooses to add, the system provides an Excel template and generates parameters by importing Excel. When modifying is selected, the system provides modifiable fields and query fields for the user to select in conjunction, and the user enters the parameter value. The system automatically identifies the primary key and primary key value according to the operation table, generates parameters by specific logic, and ensures that one parameter only affects one record. When deleting is selected, the system provides queryable fields for the user to select in conjunction, and the user enters the parameter value. The system automatically identifies the primary key and primary key value according to the operation table, generates parameters by specific logic, and ensures that one parameter only affects one record.

[0096] In one example, the acquisition module 61 is also used to perform the following checks on the change parameters: data check, which is used to check the data format of the change parameters, and the data check includes primary key conflict check, field length check and field type check; business check, which is used to check whether the change parameters meet the business rules; permission check, which is used to check whether the change parameters meet the predetermined regional impact rules and parameter quantity rules; record-level lock check, which is used to check whether there are locked statements in the statement of changing the parameters.

[0097] Based on the above implementation, if the change parameter passes the verification, the change parameter is submitted; if the change parameter does not pass the verification, the service change is stopped.

[0098] In one example, processing module 62 is specifically used to: in a verification environment, verify the correctness of the business change by simulating it, and check whether it meets the change expectations to obtain the simulated impact scope of the business change; if the change is correct and meets the change expectations, and the simulated impact scope is consistent with the impact scope of the business change, the business change is executed.

[0099] Combined with the scenario example, the factors affecting the tariff numbers are analyzed to obtain the range of the tariff numbers affected by the current business change simulation. The factors affecting other provinces are analyzed to obtain whether there are any businesses that affect other provinces in the current business change simulation; the production test consistency factors are analyzed to obtain whether the businesses affected by the current business change simulation are consistent in the production and test environments. The user number factor is analyzed to obtain the range of the number of users corresponding to the businesses affected by the current business change simulation. If the simulation impact range is consistent with the impact range of the business change, the business change is executed. Otherwise, the business change is stopped.

[0100] For example, assuming that the impact range of the service change simulation is 5 rates, and the impact range of the service change is 3 rates, if the simulated impact range exceeds the impact range of the service change, the service change will be stopped.

[0101] In one example, the cockpit module 62 is further used to: generate and store change records of the business changes; mine and analyze the currently stored business change records, and present them through visual statements and reports.

[0102] In one example, the cockpit module 62 is also used to mine and analyze currently stored business change records, and perform business health analysis of each province through weight calculation.

[0103] In the service change method provided in this embodiment, the acquisition module determines the impact scope of the service change according to the service change application of the user. The processing module is used to execute the service change if the impact scope of the service change is within the user rights of the user. The processing module is used to stop the service change if the impact scope of the service change exceeds the user rights of the user. By judging whether the impact scope of the service change of the user is within the user's rights, it is decided whether to continue the service change, thereby avoiding abnormal changes and achieving efficient, standardized and safe service changes.

[0104] Embodiment 5

[0105] Embodiment 5 of the present application provides a service change device. Based on embodiment 4, the device further includes:

[0106] A monitoring module, used to monitor the user call records and billing bills of the subscription charges before and after the service change;

[0107] The monitoring module is further used to perform a change fuse on the abnormal change if it is determined that the service change is an abnormal change based on the user call records and billing bills of the subscription charges before and after the service change.

[0108] In actual applications, the user call records and billing bills for the subscription charges before and after the service change include changes in monthly rental discounts, changes without cumulative identification, and changes with cumulative identification. The following is an introduction to the change fuse with multiple examples.

[0109] In an example, the monthly rent discount change specifically includes: the monitoring module obtains three subscribers of the service as sample users; the monitoring module calls the real-time billing interface to re-bill the monthly rent for the sample users; the monitoring module returns the user call records, billing bills and user information of the subscription charges before and after the user change.

[0110] In conjunction with the scenario example, the monitoring of the monthly rent discount change randomly selects three subscribers from the users of the monthly rent discount service as sample users. The sample users are re-issued monthly rent in real time according to the monthly rent discount service, and the user call list, billing bill and user information of the user subscription rate before and after the user change obtained by simulating the monthly rent re-issue are returned. If the user call list and billing bill of the subscription rate before and after the change are normal, the monthly rent discount service is normal.

[0111] Through the method in this example, monthly rental discount services can be monitored in real time, and if there are any abnormal changes, feedback can be given in a timely manner.

[0112] In another example, the change without cumulative identification specifically includes: the monitoring module obtains the subscribed users of the target tariff to be monitored for change as sample users; the monitoring module obtains the detailed bill of the sample user, and the batch price track field of the user detailed bill matches the tariff code; the monitoring module returns the matched user detailed bill and billing invoice.

[0113] In combination with the scenario example, for the monitoring of changes without cumulative identification, the subscribers of the target tariff for change monitoring are selected as sample users. The traffic details of the sample users are obtained after the change is completed, and the price track field of the user details matches the tariff code. If it is matched, it means that the user has used this tariff after the tariff is modified. The correctness of the tariff change can be judged by the billing accuracy of this user, and the monthly discount service is normal. The timed collection of the user details of the sample users' subscription tariffs before and after the change is only triggered regularly during the service idle period.

[0114] In another example, the cumulative identification type change specifically includes: the monitoring module obtains users whose usage changes in the cumulative table after the change is completed as sample users; the monitoring module obtains the detailed list of the sample users, and the batch price track field of the user detailed list matches the tariff code; the monitoring module returns the matched user, detailed list and billing bill.

[0115] In combination with the scenario example, the monitoring of cumulative identification changes uses users with usage changes in the cumulative table after the change is completed as sample users. The usage change indicates that the user has used this tariff after the tariff change is completed. The correctness of the tariff change can be judged by the billing accuracy of this user.

[0116] Through the method in this example, changes can be monitored in the current business. By screening the current business, the scope of sample selection can be narrowed to improve efficiency.

[0117] In one example, the monitoring module is specifically used for: the monitoring module organizes the user and tariff exception types and scenarios into audit points; the monitoring module matches the user call records and billing bills of the subscription tariffs after the service change with the audit points. If the match is successful, the service change is judged to be an abnormal change, and a change fuse is performed on the abnormal change.

[0118] In practical applications, the change fuse includes rate-level fuse and user-level fuse. The change fuse is introduced below with examples.

[0119] In one example, the rate-level fuse specifically includes: the monitoring module adds the known abnormal rates to an intermediate table, and if the user's services include services in the intermediate table, the user who subscribes to the abnormal rates is stopped from being charged.

[0120] Taking the scenario example as an example, known abnormal charges are added to the intermediate table, and the user information of the user is matched with the intermediate table. If the match is successful, it is considered that the user has an abnormal change in service, and the charge level fuse is performed on the abnormal change in service; the charge level fuse specifically includes: stopping billing for the user with the abnormal change in charge.

[0121] In another example, the user-level fuse specifically includes: the monitoring module adds known abnormal users into the intermediate table, and the abnormal users refer to users whose abnormal tariffs are normal except for one abnormal billing branch; if the user information of the user who subscribes to the tariff happens to match this abnormal billing branch, only a part of the users will be temporarily blown without blowing the tariff, thereby ensuring that users with normal billing rules are processed normally.

[0122] Taking the scenario example as an example, known abnormal users are added to the intermediate table, and the users are matched with the intermediate table. If the match is successful, the user is considered to be an abnormal user, and a user-level fuse is performed on the user; the user-level fuse specifically includes: marking the user's call record as an error record, and not charging the user for the time being.

[0123] Based on the above implementation, the method of the intermediate table can accurately and quickly identify abnormal change services or abnormal users, and perform circuit breaking in a targeted manner, thereby improving the efficiency of change circuit breaking.

[0124] In the service change device provided in this embodiment, the monitoring module is used to monitor the user call bills and billing bills of the subscription charges before and after the service change. The monitoring module is used to perform a change fuse on the abnormal change if it is determined that the service change is an abnormal change based on the user call bills and billing bills of the subscription charges before and after the service change. By real-time monitoring of the service change, the abnormal change is discovered and the change fuse is performed.

[0125] Embodiment 6

[0126] Figure 6 It is a device block diagram of a service change device according to an exemplary embodiment. The device may be a mobile phone, a computer, a digital broadcast terminal, a message transceiver, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.

[0127] The device 800 may include one or more of the following components: a processing component 802 , a memory 804 , a power component 806 , a multimedia component 808 , an audio component 810 , an input / output (I / O) interface 812 , a sensor component 814 , and a communication component 816 .

[0128] The processing component 802 generally controls the overall operation of the device 800, such as operations associated with display, phone calls, data communications, camera operations, and recording operations. The processing component 802 may include one or more processors 820 to execute instructions to complete all or part of the steps of the above-mentioned method. In addition, the processing component 802 may include one or more modules to facilitate the interaction between the processing component 802 and other components. For example, the processing component 802 may include a multimedia module to facilitate the interaction between the multimedia component 808 and the processing component 802.

[0129] The memory 804 is configured to store various types of data to support operations on the device 800. Examples of such data include instructions for any application or method operating on the device 800, contact data, phone book data, messages, pictures, videos, etc. The memory 804 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0130] The power supply component 806 provides power to the various components of the device 800. The power supply component 806 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device 800.

[0131] The multimedia component 808 includes a screen that provides an output interface between the device 800 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundaries of the touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 808 includes a front camera and / or a rear camera. When the device 800 is in an operating mode, such as a shooting mode or a video mode, the front camera and / or the rear camera may receive external multimedia data. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.

[0132] The audio component 810 is configured to output and / or input audio signals. For example, the audio component 810 includes a microphone (MIC), and when the device 800 is in an operating mode, such as a call mode, a recording mode, and a speech recognition mode, the microphone is configured to receive an external audio signal. The received audio signal can be further stored in the memory 804 or sent via the communication component 816. In some embodiments, the audio component 810 also includes a speaker for outputting audio signals.

[0133] I / O interface 812 provides an interface between processing component 802 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include but are not limited to: home button, volume button, start button, and lock button.

[0134] The sensor assembly 814 includes one or more sensors for providing various aspects of the status assessment of the device 800. For example, the sensor assembly 814 can detect the open / closed state of the device 800, the relative positioning of components, such as the display and keypad of the device 800, and the sensor assembly 814 can also detect the position change of the device 800 or a component of the device 800, the presence or absence of user contact with the device 800, the orientation or acceleration / deceleration of the device 800, and the temperature change of the device 800. The sensor assembly 814 may include a proximity sensor configured to detect the presence of a nearby object without any physical contact. The sensor assembly 814 may also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 814 may also include an accelerometer, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

[0135] The communication component 816 is configured to facilitate wired or wireless communication between the device 800 and other devices. The device 800 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 816 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 816 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

[0136] In an exemplary embodiment, the apparatus 800 may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors or other electronic components to perform the above method.

[0137] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 804 including instructions, and the instructions can be executed by the processor 820 of the device 800 to perform the above method. For example, the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

[0138] Embodiment 7

[0139] Figure 7 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application is shown in FIG. Figure 7 As shown, the electronic device includes:

[0140] The electronic device includes a processor 291 and a memory 292; it may also include a communication interface 293 and a bus 294. The processor 291, the memory 292, and the communication interface 293 may communicate with each other through the bus 294. The communication interface 293 may be used for information transmission. The processor 291 may call the logic instructions in the memory 294 to execute the method of the above embodiment.

[0141] In addition, the logic instructions in the above-mentioned memory 292 can be implemented in the form of software functional units and can be stored in a computer-readable storage medium when sold or used as an independent product.

[0142] The memory 292 is a computer-readable storage medium that can be used to store software programs and computer executable programs, such as program instructions / modules corresponding to the methods in the embodiments of the present application. The processor 291 executes functional applications and data processing by running the software programs, instructions, and modules stored in the memory 292, that is, implementing the methods in the above method embodiments.

[0143] The memory 292 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and an application required for at least one function; the data storage area may store data created according to the use of the terminal device, etc. In addition, the memory 292 may include a high-speed random access memory and may also include a non-volatile memory.

[0144] An embodiment of the present application provides a non-temporary computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed by a processor, they are used to implement the method described in the above embodiment.

[0145] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the invention disclosed herein. The present application is intended to cover any modification, use or adaptation of the present application, which follows the general principles of the present application and includes common knowledge or customary techniques in the art that are not disclosed in the present application. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present application are indicated by the following claims.

[0146] It should be understood that the present application is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A service change method, characterized in that: include: Determine the impact scope of this business change based on the user's business change application; If the impact of this service change is within the user rights of the user, the service change is executed; If the impact of this service change exceeds the user rights of the user in question, the service change will be stopped; The user rights of the user represent the scope of influence allowed by the service change of the user; Obtaining change application information in the business change application; Pushing an operable interface corresponding to the user's user authority to the user, and obtaining the changed parameters of the user in the operable interface; Perform a multi-factor analysis on the change application information to determine the impact scope of the service change; the factors include the impact on the number of tariffs, the impact on the number of users, the impact on tariffs in other provinces, the consistency of production testing, and the consistency of expected impact; Monitor the user call records and billing invoices of the subscription charges before and after the service change; According to the user call records and billing bills of the subscription charges before and after the service change, if it is determined that the service change is an abnormal change, a change fuse is performed on the abnormal change.

2. The method according to claim 1, characterized in that After obtaining the changed parameters of the user in the operable interface, the method further includes: The following checks are performed on the changed parameters: data check, which is used to check the data format of the changed parameters, and the data check includes primary key conflict check, field length check and field type check; business check, which is used to check whether the changed parameters meet the business rules; permission check, which is used to check whether the changed parameters meet the predetermined regional impact rules and parameter quantity rules; record-level lock check, which is used to check whether there are locked statements in the statement for changing the parameters.

3. The method according to claim 1, characterized in that The execution of business changes includes: In the verification environment, verify the correctness of this business change and check whether it meets the change expectations; If the change is correct and meets the change expectations, the business change is executed.

4. The method according to claim 1, characterized in that: If the service change is determined to be an abnormal change based on the user call records and billing bills of the subscription charges before and after the service change, then a change fuse is performed on the abnormal change, including: Organize the rules of the user's call records and billing bills with known abnormal subscription rates into audit points; The user call record and the billing bill of the subscription fee after the service change are matched with the audit point. If the match is successful, it is determined that the service change is an abnormal change, and a change fuse is performed on the abnormal change.

5. The method according to any one of claims 1 to 4, characterized in that The method further comprises: Generate and store a change record of the business change; Mine and analyze currently stored business change records and present them through visual statements and reports.

6. A service change device, characterized in that: include: The acquisition module is used to determine the impact scope of the current business change based on the user's business change application; A processing module, configured to execute the service change if the impact scope of the service change is within the user rights of the user; The processing module is further used to stop the service change if the impact scope of the service change exceeds the user authority of the user; The user rights of the user represent the scope of influence allowed by the service change of the user; The acquisition module is specifically used to obtain the change application information in the business change application; The acquisition module is further configured to push an operable interface corresponding to the user's user authority to the user, and to acquire the changed parameters of the user in the operable interface; The processing module is specifically used to perform a multi-factor analysis on the change application information to determine the impact scope of the current service change; wherein the factors include the impact on the tariff number, the impact on the number of users, the impact on other provinces' tariffs, the consistency of production testing, and the consistency of expected impact; A monitoring module, used to monitor the user call records and billing bills of the subscription charges before and after the service change; The monitoring module is further used to perform a change fuse on the abnormal change if it is determined that the service change is an abnormal change based on the user call records and billing bills of the subscription charges before and after the service change.

7. The device according to claim 6, characterized in that The processing module is further used to perform the following checks on the changed parameters: data check, the data check is used to check the data form of the changed parameters, the data check includes primary key conflict check, field length check and field type check; Business verification, which is used to verify whether the changed parameters meet the business rules; Permission verification, which is used to verify whether the changed parameters meet the predetermined regional impact rules and parameter quantity rules; The record-level lock check is used to check whether there are any locked statements in the statement for changing parameters.

8. The device according to claim 7, characterized in that The processing module is specifically used to verify the correctness of the business change in a verification environment, and to check whether it meets the change expectations and obtain the simulated impact scope of the business change; The processing module is further specifically used to execute the business change if the change is correct and meets the expected simulated impact scope of the change and is consistent with the impact scope of the business change.

9. The device according to claim 6, characterized in that The monitoring module is specifically used to organize the user call records and billing bills of users with known abnormal subscription rates into audit points; The monitoring module is specifically used to match the user call record and billing bill of the subscription fee after the service change with the audit point. If the match is successful, it is determined that the service change is an abnormal change, and the change fuse is executed for the abnormal change.

10. The device according to any one of claims 6 to 9, characterized in that: The device also includes: A cockpit module, used for generating and storing a change record of the business change; The cockpit module is also used to mine and analyze currently stored business change records and present them through visual statements and reports.

11. An electronic device, characterized in that: include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory to implement the method according to any one of claims 1 to 5.

12. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, which are used to implement the method according to any one of claims 1 to 5 when executed by a processor.

Images