Key business scenario detection systems, methods, storage media and products

Abstract

This invention discloses a key business scenario detection system, comprising: a scenario initiation subsystem for acquiring pending data corresponding to a target scenario type and determining an initial model based on the pending data; a model slice management container for training the initial model and determining a target model based on the trained model, task execution data, and scenario business processing data; an intelligent scenario generator for determining a list of key scenarios for each scenario type based on the target model; and a scenario task closed-loop subsystem for determining key scenarios to be created and creating target tasks based on the target models of the key scenarios to be created. This invention also discloses a key business scenario detection method, storage medium, and computer program product. This invention enables various business personnel to select key scenarios through the key business scenario detection system, thereby expanding the range of key scenario selection and enriching the selection of key scenarios.

Description

Technical Field

[0001] This invention relates to the field of mobile communication technology, and in particular to a key business scenario detection system, method, storage medium, and product. Background Technology

[0002] In existing technologies, when implementing scenario-based management, managers often encounter a large number of scenarios in their work. Due to the sheer number of scenarios, managers can only focus their limited energy on the scenarios that require key attention in order to achieve business goals.

[0003] Currently, key scenario screening models are typically generated by providing indicators and tools for filtering based on these indicators. Managers can adjust these models as needed based on observed results to address the most pressing issues. However, this approach requires significant daily effort from managers, who may easily overlook crucial scenarios due to their own schedules, resulting in an incomplete selection of key scenarios.

[0004] The above content is only used to help understand the technical solution of the present invention and does not represent an admission that the above content is prior art. Summary of the Invention

[0005] The main objective of this invention is to provide a key business scenario detection system, method, storage medium, and product, aiming to solve the technical problem of incomplete screening of key scenarios in the existing scenario-based management process.

[0006] To achieve the above objectives, the present invention provides a key business scenario detection system, which includes a scenario initiation subsystem, a modeling management subsystem, and a scenario task closed-loop subsystem; wherein,

[0007] The scenario initiation subsystem is used to obtain the data to be processed corresponding to the target scenario type from the basic database, and to determine the initial model based on the data to be processed.

[0008] The modeling management subsystem includes:

[0009] The model slice management container is used to train the initial model based on the scenario business indicator data and scenario business processing data of the data to be processed, so as to obtain the trained model, and to determine the target model based on the trained model, the task execution data of the data to be processed, and the scenario business processing data.

[0010] An intelligent scene generator is used to determine a list of key scenes for each scene type based on the target model.

[0011] The scenario task closed-loop subsystem is used to determine the key scenario to be created corresponding to the task creation request in the key scenario list when a task creation request is received, and to create a target task based on the target model of the key scenario to be created.

[0012] Furthermore, the scenario initiation subsystem includes:

[0013] The scenario analysis module is used to obtain the data to be processed corresponding to the target scenario type from the basic database, analyze and process the data to be processed and display the data after analysis and processing, and when a key scenario application request is received, store the key scenario information corresponding to the key scenario application request.

[0014] The scene evaluation module is used to determine the key scene to be modeled based on the evaluation information and the key scene information that has not been modeled when it receives the evaluation information corresponding to the key scene information that has not been modeled, and to determine the initial model corresponding to the key scene to be modeled.

[0015] Furthermore, the scenario analysis module is also used to filter and display the scenario business indicator data, task execution data, and scenario business processing data of the data to be processed, as well as to overlay customer group filtering and scenario customer group composition analysis on the classified customer group residence data of the data to be processed, and display the analyzed classified customer group residence data.

[0016] Furthermore, the scenario evaluation module is also used to verify whether the user account corresponding to the evaluation information has evaluation permissions when the evaluation information is received. If the user account has evaluation permissions, the module determines the key scenarios to be modeled based on the evaluation information and the key scenario information that has not been modeled, and determines the initial model corresponding to the key scenarios to be modeled.

[0017] Furthermore, the model slice management container is also used to generate scene type slices corresponding to the initial models of each scene type; to train the initial models based on scene business indicator data and scene business processing data using the scene type slices to obtain trained models; to train the trained models based on task execution data and scene business processing data to obtain loss function values; and to determine the target model based on the loss function values.

[0018] Furthermore, the scenario task closed-loop subsystem includes:

[0019] A scene task generator is used to determine the key scene to be created corresponding to the task creation request in the key scene list when a task creation request is received, and to create a target task based on the target model of the key scene to be created.

[0020] The task execution dual closed-loop module is used to acquire and store the scenario business processing data and task execution data of the target task.

[0021] Furthermore, the model slice management container is also used to update the target model based on the scenario business processing data and task execution data of the target task, so as to obtain the updated target model;

[0022] The intelligent scene generator is used to update the list of key scenes based on the updated target model.

[0023] Furthermore, to achieve the above objectives, the present invention also provides a method for detecting key business scenarios, applied to the aforementioned key business scenario detection system, the method comprising the following steps:

[0024] Obtain the data to be processed corresponding to the target scene type from the basic database, and determine the initial model based on the data to be processed;

[0025] The initial model is trained based on the scenario business indicator data and scenario business processing data of the data to be processed to obtain the trained model, and the target model is determined based on the trained model, the task execution data of the data to be processed, and the scenario business processing data.

[0026] Based on the target model, determine the list of key scenarios for each scenario type;

[0027] When a task creation request triggered by a list of key scenarios is received, the key scenario to be created corresponding to the task creation request is determined in the list of key scenarios, and a target task is created based on the target model of the key scenario to be created.

[0028] In addition, to achieve the above objectives, the present invention also provides a storage medium storing a key business scenario detection program, which, when executed by a processor, implements the steps of the aforementioned key business scenario detection method.

[0029] In addition, to achieve the above objectives, the present invention also provides a computer program product, including a computer program, which, when executed by a processor, implements the steps of the aforementioned key business scenario detection method.

[0030] This invention uses a scenario initiation subsystem to determine the initial model, a modeling management subsystem to train and optimize the initial model to obtain the target model, and a scenario task closed-loop subsystem to create the target task corresponding to the target model. This allows business personnel to select key scenarios through a key business scenario detection system, thereby expanding the range of key scenarios and enriching their selection. Simultaneously, it expands the user base of data analysis tools from traditionally analysts to a broad range of business personnel, effectively solving the problem that traditional analysis tools' results and objectives are too loosely defined and difficult to utilize effectively. Furthermore, it avoids the drawbacks of centralized data analysis, such as slow response times that fail to meet the needs of business development. Attached Figure Description

[0031] Figure 1 This is a schematic diagram of the structure of a key business scenario detection device in the hardware operating environment involved in the embodiments of the present invention;

[0032] Figure 2 This is a schematic diagram of the functional modules of an embodiment of the key business scenario detection system of the present invention;

[0033] Figure 3 This is a functional module diagram of another embodiment of the key business scenario detection system of the present invention.

[0034] Figure 4 This is a flowchart illustrating an embodiment of the key business scenario detection method of the present invention.

[0035] The realization of the objective, functional features and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0036] It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

[0037] like Figure 1 As shown, Figure 1 This is a schematic diagram of the structure of a key business scenario detection device in the hardware operating environment involved in the embodiments of the present invention.

[0038] The detection device for key business scenarios in this embodiment of the invention can be a PC, or a smartphone or tablet.

[0039] like Figure 1As shown, the key business scenario detection device may include: a processor 1001, such as a CPU; a network interface 1004; a user interface 1003; a memory 1005; and a communication bus 1002. The communication bus 1002 is used to enable communication between these components. The user interface 1003 may include a display screen and an input unit such as a keyboard; optionally, the user interface 1003 may also include a standard wired interface or a wireless interface. The network interface 1004 may optionally include a standard wired interface or a wireless interface (such as a Wi-Fi interface). The memory 1005 may be high-speed RAM or stable non-volatile memory, such as a disk storage device. Optionally, the memory 1005 may also be a storage device independent of the aforementioned processor 1001.

[0040] Optionally, the detection equipment for key business scenarios may also include cameras, RF (Radio Frequency) circuits, sensors, audio circuits, WiFi modules, etc. Among these, sensors include light sensors, motion sensors, and other sensors.

[0041] Those skilled in the art will understand that Figure 1 The terminal structure shown does not constitute a limitation on the detection equipment for key business scenarios. It may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0042] like Figure 1 As shown, the memory 1005, which serves as a computer storage medium, may include an operating system, a network communication module, a user interface module, and a key business scenario detection program.

[0043] exist Figure 1 In the key business scenario detection device shown, the network interface 1004 is mainly used to connect to the backend server and communicate with the backend server; the user interface 1003 is mainly used to connect to the client (user end) and communicate with the client; and the processor 1001 can be used to call the key business scenario detection program stored in the memory 1005.

[0044] In this embodiment, the key business scenario detection device includes: a memory 1005, a processor 1001, and a key business scenario detection program stored in the memory 1005 and executable on the processor 1001. When the processor 1001 calls the key business scenario detection program stored in the memory 1005, it executes the steps of the key business scenario detection method in the following embodiments.

[0045] This invention provides a key business scenario detection system, referring to... Figure 2 , Figure 2 This is a schematic diagram of the functional modules of an embodiment of the key business scenario detection system of the present invention.

[0046] In this embodiment, the key business scenario detection system 10 includes a scenario initiation subsystem 100, a modeling management subsystem 200, and a scenario task closed-loop subsystem 300.

[0047] The scenario initiation subsystem 100 is used to obtain the data to be processed corresponding to the target scenario type from the basic database, and to determine the initial model based on the data to be processed. The scenario initiation subsystem 100 can also be called the Data Driven Scenario Initiation Subsystem 100 (DVSIS).

[0048] Specifically, users (business personnel) can select a target scenario type through the key business scenario detection system 10. Upon receiving the user's selected target scenario type, the scenario initiation subsystem 100 retrieves the pending data corresponding to the target scenario type from the basic database and determines an initial model based on the pending data. Specifically, the scenario initiation subsystem 100 can also perform corresponding data processing operations on the pending data and then display the processed pending data for the user to view. The user can initiate a key scenario application based on the currently displayed processed pending data. Upon receiving a key scenario application request corresponding to the key scenario application, the scenario initiation subsystem 100 determines an initial model based on the processed pending data. To improve the accuracy of key scenarios, an initial model modeling review mechanism can be set. Specifically, upon receiving a key scenario application request corresponding to the key scenario application, the scenario initiation subsystem 100 can display the processed pending data corresponding to the key scenario application request. Users with review permissions can review and evaluate the key scenario application request and input the corresponding evaluation result. After receiving the evaluation result, if the evaluation result is passed, the scenario initiation subsystem 100 models based on the processed pending data to obtain the initial model. Among them, the data to be processed is the historical data stored in the key business scenario detection system 10, namely the scenario business indicator data, task execution data and scenario business processing data of historical tasks.

[0049] The modeling management subsystem 200, also known as the Intelligent Scenario Modelling Subsystem (ISMS), primarily functions to generate selection models for specified key scenarios and embed these models into the system, thereby continuously updating the list of key scenarios as data is updated. This modeling management subsystem 200 includes a model slice management container 210 and an intelligent scene generator 220.

[0050] The Model Slice Management Container 210 (MSMC) is used to train the initial model based on the scenario business indicator data and scenario business processing data of the data to be processed, so as to obtain the trained model, and to determine the target model based on the trained model, the task execution data of the data to be processed, and the scenario business processing data.

[0051] In this embodiment, the model slice management container 210 obtains scene business indicator data, task execution data, and scene business processing data from the data to be processed. The scene business processing data is the scene business processing data related to the task execution data. Preferably, after the scene initiation subsystem 100 preprocesses the data to be processed, the model slice management container 210 obtains the scene business indicator data, task execution data, and scene business processing data from the preprocessed data to be processed.

[0052] Subsequently, the model slice management container 210 trains the initial model based on scenario business indicator data and scenario business processing data. Specifically, the model slice management container 210 uses the scenario business indicator data and scenario business processing data as input data for model training, and the trained initial model becomes the trained model. Finally, the model slice management container 210 determines the target model based on the trained model, task execution data, and scenario business processing data. Specifically, it inputs the task execution data and scenario business processing data into the trained model to obtain the loss function of the trained model. When the loss function converges (e.g., the loss function is less than a preset threshold), the trained model is used as the target model.

[0053] The Intelligent Scene Generator 220 (ISG) is used to determine a list of key scenes for each scene type based on the target model. In this embodiment, after the model slice management container 210 generates the target model, the Intelligent Scene Generator 220 determines a list of key scenes for each scene type based on the target model. Specifically, if a list of key scenes exists, it is updated based on the target model to add the target model to the list. For example, the target model is added to a preset area corresponding to the scene type of the target model in the list of key scenes. If a list of key scenes does not exist, the Intelligent Scene Generator 220 obtains all the target models generated by the model slice management container 210 and generates a list of key scenes based on all the target models and their corresponding scene types. Preferably, the Intelligent Scene Generator 220 is also used to generate a list of key scenes based on the target models of each scene type, or to update the list of key scenes based on the target models.

[0054] Preferably, in one embodiment, the model slice management container 210 is further used to generate scene type slices corresponding to the initial models of each scene type; to train the initial models based on scene business indicator data and scene business processing data using the scene type slices to obtain trained models; to train the trained models based on task execution data and scene business processing data to obtain loss function values; and to determine the target model based on the loss function values.

[0055] In this embodiment, the model slice management container 210 generates scene type slices corresponding to the initial models of each scene type. The model slice management container 210 can generate a scene type slice for each key scene type so as to independently manage the initial models related to each key scene type through the scene type slices. Furthermore, the initial model corresponding to each scene type is trained and optimized through the corresponding scene type slice.

[0056] The 300STCS-Scenario Task Closed-loop Subsystem is used to determine the key scenario to be created corresponding to the task creation request in the key scenario list when a task creation request is received, and to create a target task based on the target model of the key scenario to be created.

[0057] In this embodiment, the main function of the scenario task closed-loop subsystem 300 is to establish target tasks, such as marketing tasks, around key scenarios. Specifically, users with character creation permissions can submit task creation requests based on the list of key scenarios. For example, a user triggers a request to display the list of key scenarios through the key business scenario detection system 10. The key business scenario detection system 10 displays the list of key scenarios, and the user triggers a task creation request by selecting a key scenario to be created from the list. The key business scenario detection system 10 verifies whether the user account corresponding to the task creation request has task creation permissions. If it does, the scenario task closed-loop subsystem 300 determines the key scenario to be created selected by the user based on the task creation request and creates a target task based on the target model of the key scenario to be created.

[0058] The key business scenario detection system 10 in this embodiment determines an initial model through a scenario initiation subsystem 100, and the modeling management subsystem 200 trains and optimizes the initial model to obtain a target model. The scenario task closed-loop subsystem 300 then creates target tasks corresponding to the target model, enabling various business personnel to select key scenarios through the key business scenario detection system 10, thereby expanding the range of key scenarios and enriching the selection. Simultaneously, it expands the user group of data analysis tools from traditionally dedicated to analysts to a broad range of business personnel, effectively solving the problem that traditional analysis tools' results and targets are too loosely defined and difficult to utilize effectively; it also avoids the drawbacks of slow response times caused by centralized data analysis, which are unable to meet the needs of business development.

[0059] Furthermore, in one embodiment, reference is made to... Figure 3 The scenario initiation subsystem 100 includes a scenario analysis module 110 and a scenario evaluation module 120.

[0060] The scenario analysis module 110, also known as the geo-based interactive scenario analysis module 110 (GBISAM-Geo-BasedInteractive Scenario Analysis Module), is used to obtain the data to be processed corresponding to the target scenario type from the basic database, analyze and process the data to be processed and display the data after analysis and processing, and store the key scenario information corresponding to the key scenario application request when a key scenario application request is received.

[0061] The scenario evaluation module 120, also known as the Collective Augmented Scenario Evaluation Module 120 (CASEM), is used to determine the key scenario to be modeled based on the evaluation information and the key scenario information to be modeled when it receives the evaluation information corresponding to the key scenario information that has not been modeled, and to determine the initial model corresponding to the key scenario to be modeled.

[0062] Preferably, the scenario analysis module 110 is also used to filter and display the scenario business indicator data, task execution data and scenario business processing data of the data to be processed, and to overlay the categorized customer group residence data of the data to be processed to filter customer groups and analyze the scenario customer group composition, and display the analyzed categorized customer group residence data.

[0063] In this embodiment, upon receiving a key scenario application request corresponding to a key scenario application, the scenario analysis module 110 retrieves the data to be processed corresponding to the target scenario type from the basic database. It then filters the scenario business indicator data, task execution data, and scenario business processing data of the data to be processed. Specifically, the scenario analysis module 110 performs classification and indicator filtering on the scenario business indicator data, task execution data, and scenario business processing data to obtain data that meets user needs (matches the key scenario application request). For example, it filters out data that matches the indicators and scenario type set by the user, and then displays the filtered data. For instance, it uses the geographic attributes of the filtered data to color-code the data. Simultaneously, the scenario analysis module 110 overlays customer group filtering and scenario customer group composition analysis on the classified customer group residence data of the data to be processed, and displays the analyzed classified customer group residence data. Upon receiving a request for a key scenario application, the scenario analysis module 110 stores the key scenario information corresponding to the request to facilitate modeling based on this information. In this embodiment, key scenario applications can be enabled only for authorized users. For example, upon receiving a key scenario application request, the scenario analysis module 110 verifies whether the user account corresponding to the request has key scenario application permissions. If it does, the module stores the key scenario information. In this embodiment, a scenario slice is constructed for each key scenario type, and a complete scenario dataset is provided for each slice to support the needs of scenario modeling and optimization.

[0064] Then, the key business scenario detection system 10 can display information on key scenarios that are not currently modeled. Users can select the scenario they need to model from this list. Specifically, the system evaluates the displayed key scenarios to determine if they meet the modeling conditions. For example, users can submit evaluation information based on the displayed key scenarios. Upon receiving the evaluation information corresponding to the key scenario information, the scenario evaluation module 120 determines the key scenario to be modeled based on the evaluation information and the key scenario information, and determines the initial model corresponding to the key scenario to be modeled. For example, if the evaluation information is satisfactory, the scenario evaluation module 120 determines the key scenario to be modeled corresponding to the evaluation information from the key scenario information and determines the initial model corresponding to the key scenario to be modeled. Preferably, to improve the accuracy of key scenarios, an approval authority for the initial model can be set. Specifically, when receiving evaluation information corresponding to key scenario information that has not been modeled, the scenario evaluation module 120 verifies whether the user account corresponding to the evaluation information has key evaluation authority. If it has evaluation authority, the scenario evaluation module 120 determines the key scenario to be modeled based on the evaluation information and the key scenario information that has not been modeled.

[0065] Furthermore, in one embodiment, reference is made to... Figure 3 The scene task closed-loop subsystem 300 includes a scene task generator 310 and a task execution dual closed-loop module 320.

[0066] The scenario task generator 310, also known as the augmented scenario task generator 310ASTG-AugmentedScenario Task Generator, is used to determine the key scenario to be created corresponding to the task creation request in the key scenario list when a task creation request is received, and to create a target task based on the target model of the key scenario to be created.

[0067] The task execution dual-loop module 320, also known as the task execution dual-loop module 320TEDM-TaskExecution Dual-loop Module, is used to acquire and store the scenario business processing data and task execution data of the target task.

[0068] In this embodiment, a user with character creation permissions can submit a task creation request based on a list of key scenarios. For example, a user triggers a request to display the list of key scenarios through the key business scenario detection system 10. The key business scenario detection system 10 displays the list of key scenarios. When the user selects a key scenario to be created in the list of key scenarios to trigger a task creation request, the scenario task generator 310 determines the key scenario to be created corresponding to the task creation request in the list of key scenarios and creates a target task based on the target model of the key scenario to be created. Preferably, when selecting a key scenario to be created in the list of key scenarios to trigger a task creation request, the scenario task generator 310 first verifies whether the user account corresponding to the task creation request has task creation permissions. If it has task creation permissions, the scenario task generator 310 determines the key scenario to be created selected by the user based on the task creation request and creates a target task based on the target model of the key scenario to be created.

[0069] After the target task is created, the task execution dual closed-loop module 320 obtains the scenario business processing data and task execution data of the target task, and stores the scenario business processing data and task execution data of the target task, so as to update the target model corresponding to the target task based on the scenario business processing data and task execution data of the target task.

[0070] Preferably, the model slice management container 210 is further used to update the target model based on the scenario business processing data and task execution data of the target task to obtain the updated target model; the intelligent scenario generator 220 is further used to update the list of key scenarios according to the updated target model.

[0071] In this embodiment, after the task execution dual closed-loop module 320 stores the scenario business processing data and task execution data of the target task, the model slice management container 210 updates the target model based on the scenario business processing data and task execution data of the target task. Specifically, the model slice management container 210 trains the target model according to the scenario business processing data and task execution data of the target task to obtain the updated target model. The intelligent scene generator 220 updates the key scene list according to the updated target model, thereby realizing the updating of the target model according to the task data, so as to realize the closed-loop update of the model and enable the continuous iterative optimization of the scene model.

[0072] Preferably, the task execution dual closed-loop module 320 is further configured to send the evaluation information to the scene initiation subsystem 100 when the evaluation information corresponding to the target task is obtained; the scene evaluation module 120 of the scene initiation subsystem 100 is configured to determine the adjustment requirement information corresponding to the target scene type based on the evaluation information, and update the initial model based on the adjustment requirement information.

[0073] In this embodiment, after completing a task, the user can choose to evaluate the target task, for example, by submitting evaluation information on the interface of the key business scenario detection system 10. The task execution dual closed-loop module 320 receives the evaluation information submitted by the user and sends the evaluation information to the scenario initiation subsystem 100. The scenario evaluation module 120 of the scenario initiation subsystem 100 is used to determine the adjustment requirement information corresponding to the target scenario type based on the evaluation information, and update the initial model based on the adjustment requirement information to achieve real-time adjustment of the model.

[0074] It should be noted that after the initial model is updated, the model slice management container 210 updates the target model according to the updated initial model to obtain the updated target model; the intelligent scene generator 220 updates the key scene list according to the updated target model, and at the same time, the scene task closed-loop subsystem 300 updates the target task based on the updated target model.

[0075] This invention also provides a method for detecting key business scenarios, referring to... Figure 4 In this embodiment, the key business scenario detection method includes the following steps:

[0076] Step S101: Obtain the data to be processed corresponding to the target scene type from the basic database, and determine the initial model based on the data to be processed;

[0077] Step S102: Train the initial model based on the scenario business indicator data and scenario business processing data of the data to be processed to obtain the trained model, and determine the target model based on the trained model, the task execution data of the data to be processed, and the scenario business processing data.

[0078] Step S103: Determine the list of key scenes for each scene type based on the target model;

[0079] Step S104: When a task creation request triggered by a list of key scenarios is received, the key scenario to be created corresponding to the task creation request is determined in the list of key scenarios, and a target task is created based on the target model of the key scenario to be created.

[0080] This embodiment can be referred to in various embodiments of the key business scenario detection system of the present invention, which will not be repeated here.

[0081] The present invention also provides a storage medium, namely a computer-readable storage medium. The storage medium stores a key business scenario detection program, which, when executed by a processor, implements the steps of the key business scenario detection method described above.

[0082] The method implemented when the key business scenario detection program running on the processor is executed can be referred to in various embodiments of the key business scenario detection method of the present invention, and will not be repeated here.

[0083] Furthermore, this invention also proposes a computer program product that includes a key business scenario detection program. When the key business scenario detection program is executed by a processor, it implements the steps of the key business scenario detection method described above.

[0084] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or system. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or system that includes that element.

[0085] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0086] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) as described above, and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of the present invention.

[0087] The above are merely preferred embodiments of the present invention and do not limit the scope of the patent. Any equivalent structural or procedural transformations made based on the description and drawings of the present invention, or direct or indirect applications in other related technical fields, are similarly included within the scope of patent protection of the present invention.

Claims

1. A key business scenario detection system, characterized in that, The key business scenario detection system includes a scenario initiation subsystem, a modeling management subsystem, and a scenario task closed-loop subsystem; among which... The scenario initiation subsystem is used to obtain the data to be processed corresponding to the target scenario type from the basic database, and to determine the initial model based on the data to be processed. The modeling management subsystem includes: The model slice management container is used to train the initial model based on the scenario business indicator data and scenario business processing data of the data to be processed, so as to obtain the trained model, and to determine the target model based on the trained model, the task execution data of the data to be processed, and the scenario business processing data. An intelligent scene generator is used to determine a list of key scenes for each scene type based on the target model. The scenario task closed-loop subsystem is used to determine the key scenario to be created corresponding to the task creation request in the key scenario list when a task creation request is received from the key scenario list, and to create a target task based on the target model of the key scenario to be created. The scenario initiation subsystem includes: The scenario analysis module is used to obtain the data to be processed corresponding to the target scenario type from the basic database, analyze and process the data to be processed, and display the data after analysis and processing. When a key scenario application request is received, the module stores the key scenario information corresponding to the key scenario application request. The module also filters and displays the scenario business indicator data, task execution data, and scenario business processing data of the data to be processed, and performs customer group filtering and scenario customer group composition analysis on the classified customer group residence data of the data to be processed, and displays the analyzed classified customer group residence data. The scene evaluation module is used to determine the key scene to be modeled based on the evaluation information and the key scene information that has not been modeled when it receives the evaluation information corresponding to the key scene information that has not been modeled, and to determine the initial model corresponding to the key scene to be modeled.

2. The key business scenario detection system as described in claim 1, characterized in that, The scenario evaluation module is also used to verify whether the user account corresponding to the evaluation information has evaluation permissions when the evaluation information is received. If the user account has evaluation permissions, the module determines the key scenarios to be modeled based on the evaluation information and the key scenario information that has not been modeled, and determines the initial model corresponding to the key scenarios to be modeled.

3. The key business scenario detection system as described in claim 1, characterized in that, The model slice management container is also used to generate scene type slices corresponding to the initial models of each scene type; the initial models are trained based on scene business indicator data and scene business processing data through the scene type slices to obtain trained models; The trained model is trained based on task execution data and scenario business processing data to obtain a loss function value, and the target model is determined based on the loss function value.

4. The key business scenario detection system as described in any one of claims 1 to 3, characterized in that, The scenario task closed-loop subsystem includes: A scene task generator is used to determine the key scene to be created corresponding to the task creation request in the key scene list when a task creation request is received, and to create a target task based on the target model of the key scene to be created. The task execution dual closed-loop module is used to acquire and store the scenario business processing data and task execution data of the target task.

5. The key business scenario detection system as described in claim 4, characterized in that, The model slice management container is also used to update the target model based on the scenario business processing data and task execution data of the target task, so as to obtain the updated target model. The intelligent scene generator is used to update the list of key scenes based on the updated target model.

6. A method for detecting key business scenarios, characterized in that, The key business scenario detection method, applied to the key business scenario detection system according to any one of claims 1 to 5, comprises the following steps: Obtain the data to be processed corresponding to the target scene type from the basic database, and determine the initial model based on the data to be processed; The initial model is trained based on the scenario business indicator data and scenario business processing data of the data to be processed to obtain the trained model, and the target model is determined based on the trained model, the task execution data of the data to be processed, and the scenario business processing data. Based on the target model, determine the list of key scenarios for each scenario type; When a task creation request triggered by a list of key scenarios is received, the key scenario to be created corresponding to the task creation request is determined in the list of key scenarios, and a target task is created based on the target model of the key scenario to be created.

7. A storage medium, characterized in that, The storage medium stores a key business scenario detection program, which, when executed by the processor, implements the steps of the key business scenario detection method as described in claim 6.

8. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the steps of the key business scenario detection method as described in claim 7.

Images