Data Interaction Method and Device for Multiple Business Scenarios of Fast-Moving Consumer Goods
Through the separate architecture of the data center system and the execution agent system, basic information of business scenarios is obtained and configured, and business solution agreements are generated and implemented, and the traditional fast-moving consumer goods data management method cannot meet the needs of multiple customers and expand new scenarios, realizing the overall and refined processing of multiple customers.
Patent Information
- Application Number
- CN202410522154.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-04-28
- Publication Date
- 2025-07-11
- Estimated Expiration
- 2044-04-28
AI Technical Summary
Traditional fast-moving consumer goods data management methods cannot meet the needs of multiple customers and coordinate and refined processing, and cannot expand new business scenarios, resulting in low applicability.
Adopt a separate architecture between the data center system and the execution agent system, and configure the execution dimension application data by obtaining the basic information of the business scenario, generating business solution protocols, and implementing services in the execution agent system, using smart components and deserialization technology to handle new business scenarios.
It realizes the overall and refined processing of multiple customer needs, can add business scenarios separately in the data center system, and expand new business scenarios through unified interfaces, improving the applicability of fast-moving consumer goods data management.
Smart Images

Figure CN118469623B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of network information technology, and particularly to a data interaction method and device for multiple business scenarios of fast-moving consumer goods. Background Art
[0002] In the new retail era, there are significant differences in the scale of customers in the fast-moving consumer goods field. The system deployment mode is highly personalized, making it difficult to coordinate and refine the needs of different customers. Only one-to-one services can be provided, and it is impossible to meet the coordinated and refined business scenarios of multiple customers. In addition, the market mode in the fast-moving consumer goods field changes frequently, and the derived execution scenarios are constantly increasing, making it difficult to perform maintenance on the newly added business scenarios and impossible to expand the business scenarios.
[0003] In short, the application scenarios of traditional fast-moving consumer goods data management methods are single, unable to meet the coordinated or refined business scenarios of multiple customers' needs, nor can they expand new business scenarios, resulting in low applicability of traditional fast-moving consumer goods data management methods. Summary of the Invention
[0004] The purpose of the present invention is to address the above deficiencies of the prior art and propose a data interaction method and device for multiple business scenarios of fast-moving consumer goods, which can improve the data processing applicability of fast-moving consumer goods in different business scenarios.
[0005] In a first aspect, the present invention provides a data interaction method for multiple business scenarios of fast-moving consumer goods, which is applied to a data center system; the data interaction device for multiple business scenarios of fast-moving consumer goods includes: the data center system and an execution agent system, and the data interaction method for multiple business scenarios of fast-moving consumer goods includes:
[0006] Obtain the basic information of the to-be-added business scenario, and configure the to-be-added business scenario according to the basic information to obtain execution dimension application data; the basic information includes: a first scenario dimension and the fully qualified class name of the scenario interface implementation class.
[0007] According to the execution dimension application data, obtain the to-be-executed module and multiple first intelligent components, and generate a first business solution protocol for the to-be-added business scenario according to the to-be-executed module and the multiple first intelligent components, and store the first business solution protocol in an execution solution pool.
[0008] Select a second business solution protocol to be implemented from the execution solution pool, and obtain the to-be-executed page of the second business solution protocol, and script-serialize the to-be-executed page to obtain a serialization result.
[0009] Transmit the serialization result to the execution agent system, so that after receiving the serialization result, the execution agent system implements the corresponding business.
[0010] The framework of the data interaction device for multiple business scenarios of fast-moving consumer goods in the present invention is divided into: a data center system and an execution agent system. Transaction segmentation is performed on scene addition and task implementation. According to the data center system, a business scene can be added separately, and the execution agent system implements separately based on the newly added business scene, thereby refining the business granularity of the business scene. Furthermore, the requirements of multiple different customers can be coordinated and refined simultaneously. Moreover, when adding a business separately in the data center system, based on the unified scene interface implementation class, it is convenient to expand new business scenarios. Therefore, based on the system interaction between the two ends, different scenarios can be added and implemented based on the newly added business, thereby improving the applicability of the fast-moving consumer goods data management method to different scenarios.
[0011] Further, configuring the to-be-added business scene according to the basic information to obtain execution dimension application data includes:
[0012] Query the fully qualified class name from the central storage according to the first scene dimension. If the fully qualified class name exists, convert the fully qualified class name into an instance of the scene interface implementation class through reflection, and perform data call on the instance according to the predefined call method to obtain execution dimension application data.
[0013] Further, performing data call on the instance according to the predefined call method to obtain execution dimension application data includes:
[0014] Call the data corresponding to the instance by the scene interface implementation class calling the predefined call method to obtain execution dimension application data; the call method is output in a multi-way balanced search tree.
[0015] Further, obtaining the to-be-executed module and multiple first intelligent components according to the execution dimension application data, and generating a first business plan protocol for the to-be-added business scene according to the to-be-executed module and the multiple first intelligent components includes:
[0016] Select the to-be-executed module from the execution dimension application data to obtain the first application identifier of the application data, and call the predefined intelligent component list acquisition method to obtain multiple first intelligent components corresponding to the to-be-added business scene, and generate a first business plan protocol according to the first application identifier and the multiple first intelligent components.
[0017] Further, generating a first business plan protocol according to the first application identifier and the multiple first intelligent components includes:
[0018] Assemble multiple first intelligent components in sequence and set control parameters to obtain an assembly result. Generate a first business solution protocol bound by the execution dimension and the first application identifier based on the assembly result and the first application identifier.
[0019] Further, the steps of selecting a second business solution protocol to be implemented from the execution solution pool, obtaining the page to be executed of the second business solution protocol, and serializing the script of the page to be executed to obtain a serialization result include:
[0020] Enter the master data of the application scenario to be implemented, and select and parse the second business solution protocol to be implemented from multiple first business protocols through the second application identifier and the second scenario dimension of the master data, render the execution page, and perform the execution on the execution page by serializing the script of the execution page to obtain a serialization result.
[0021] Further, after the execution agent system receives the serialization result, it implements the corresponding business, including:
[0022] After the execution agent system receives the serialization result, it performs script deserialization on the serialization result through a smart component adapter to obtain specific second intelligent components and an execution process, and sets the global context and parameter substitution corresponding to the second intelligent components and the execution process to obtain a parameter environment, and implements the corresponding business according to the parameter environment.
[0023] Further, during the process of implementing the corresponding business, it includes:
[0024] If, according to the execution process, a step fails to execute, put the business into a retry queue, monitor the service resource situation according to a proportional-integral-derivative control algorithm, periodically execute the retry queue, and send the implementation situation of the execution task to a message queue, so that the data center system monitors the implementation situation of the business being re-executed according to the message queue.
[0025] Further, the data center system monitors the implementation situation of the business being re-executed according to the message queue, including:
[0026] The data center system asynchronously monitors the implementation situation of the business being re-executed in the message queue. If a step corresponding to the business being re-executed fails to be implemented, specific failure information is generated, and according to the failure information, a personalized implementation strategy is carried out for the failed step.
[0027] When the data center system obtains feedback on the implementation of the task, the present invention monitors the implementation of the execution plan through the asynchronous listening message queue. When a certain step of the task fails to be implemented, specific failure information will be returned. According to the failure information, a personalized implementation strategy of the step can be customized for the customer, so that fixed-point execution and resource saving can be achieved.
[0028] In a second aspect, the present invention further provides a data interaction device for multiple business scenarios of fast-moving consumer goods, the data interaction device for multiple business scenarios of fast-moving consumer goods comprising: a data center system and an execution agent system; the data center system comprises: a scenario addition and configuration module, a business solution protocol generation module, a serialization module and an interaction module; wherein,
[0029] The scenario addition and configuration module is used to select an execution dimension of a business scenario to be added, obtain basic information of the business scenario, and configure the business scenario to be added according to the basic information to obtain execution dimension application data; the basic information includes: the first scenario dimension and the fully qualified class name of the scenario interface implementation class;
[0030] The business solution protocol generation module is used to obtain a module to be executed and multiple first intelligent components according to the execution dimension application data, and generate a first business solution protocol for the business scenario to be added according to the module to be executed and the multiple first intelligent components;
[0031] The serialization module is used to select a second business solution protocol to be implemented from multiple first business solution protocols, obtain a page to be executed of the second business solution protocol, and script serialize the page to be executed to obtain a serialization result;
[0032] The interaction module is used to transmit the serialization result to the execution proxy system, so that the execution proxy system implements the corresponding business after receiving the serialization result. BRIEF DESCRIPTION OF THE DRAWINGS
[0033] Figure 1 This is a flow chart of a data interaction method for multiple business scenarios of fast-moving consumer goods provided by this embodiment;
[0034] Figure 2 This is a flowchart of another data interaction method for multiple business scenarios of fast-moving consumer goods provided by this embodiment;
[0035] Figure 3 It is a structural diagram of a data interaction device for multiple business scenarios of fast-moving consumer goods provided by this embodiment. DETAILED DESCRIPTION
[0036] Next, the technical solutions in the embodiments of the present invention will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.
[0037] It is worth noting that the existing related technologies can only handle the single business scenario of fast-moving consumer goods, resulting in a low range of business scenarios; they cannot handle the overall planning of the needs of multiple customers or the business scenarios with fine-grained requirements, resulting in insufficiently fine-grained business granularity; nor can they expand new business scenarios in the original business scenario, resulting in poor customization business capabilities and high business maintenance costs. In short, the existing related technologies have low adaptability to the data processing of fast-moving consumer goods and cannot meet the needs of multi-scenario businesses.
[0038] Based on this, the present invention proposes a data interaction method and device for multi-business scenarios of fast-moving consumer goods in the fast-moving consumer goods field to solve the problems of the traditional method, such as a narrow range of business scenarios, insufficiently fine-grained business granularity, poor customization business capabilities, and high business maintenance costs. In the data center system of product management, standard extensible scenario management, scenario application management, and scenario business management are abstracted to complete the formulation of the implementation plan, and personalized scenario execution services are provided for fast-moving consumer goods industry customers. In the customer's private environment, an execution agent service is deployed. The execution agent system executes the business solutions provided by the data center system to complete functions such as the installation and deployment of business function modules, data initialization, customer portrait collection, and data analysis, and completes the execution of the private environment, so as to be applicable to different business scenarios and meet the needs of multi-scenario businesses.
[0039] To more clearly illustrate the technical solutions of the present invention, the following embodiments will be described in detail.
[0040] Embodiment 1
[0041] It is worth noting that the technical problems to be solved in this embodiment are the problems of coarse business granularity, poor customization business implementation capabilities, and poor scalability in traditional business scenarios. Based on this, in some embodiments, by separating transactions between new business scenarios and implemented business scenarios, the framework of the data interaction device for multi-business scenarios of fast-moving consumer goods is divided into: a data center system and an execution agent system. Thus, according to the data center system, business scenarios can be newly added separately, and the execution agent system can be separately implemented based on the newly added business scenarios, which can refine the business granularity of the business scenarios; moreover, when newly adding a business in the data center system alone, based on a unified interface, the business scenarios can be expanded; and personalized settings can be made for the business scenarios when adding new businesses.
[0042] For the specific data processing methods of the data center system and the execution agent system in multi-service scenarios, please refer to Figure 1 , which is a schematic flowchart of a data interaction method for fast-moving consumer goods in multi-service scenarios provided in this embodiment, and is applied to the data center system; the data interaction method for fast-moving consumer goods in multi-service scenarios includes: steps S11 to S14, specifically:
[0043] Step S11, obtain the basic information of the to-be-added business scenario, and configure the to-be-added business scenario according to the basic information to obtain execution dimension application data; the basic information includes: the first scenario dimension and the fully qualified class name of the scenario interface implementation class.
[0044] It should be noted that the first scenario dimension is the scenario dimension of the to-be-added business scenario, and the second scenario dimension is the scenario dimension applied to the to-be-implemented scenario.
[0045] In some embodiments, when adding a task scenario, the executor first selects the execution dimension of a scenario, and based on the selected execution dimension, fills in the basic information of the scenario in the scenario management module.
[0046] In some embodiments, the basic information includes: the scenario dimension scenekey and the fully qualified class name of the scenario interface implementation class SceneService.
[0047] In some embodiments, configuring the to-be-added business scenario according to the basic information to obtain execution dimension application data includes: querying the fully qualified class name from the central storage according to the first scenario dimension. If the fully qualified class name exists, convert the fully qualified class name into an instance of the scenario interface implementation class through reflection, and perform data call on the instance according to the predefined call method to obtain the execution dimension application data.
[0048] In some embodiments, querying the fully qualified class name from the central storage according to the first scenario dimension includes: on the scenario configuration page, select the scenario dimension of the to-be-added business scenario, and query the fully qualified class name by calling the predefined call method; where the call method is to query the corresponding fully qualified class name of the scenario interface implementation class from the central storage according to the selected task scenario dimension.
[0049] In some embodiments, performing data call on the instance according to the predefined call method to obtain the execution dimension application data includes: calling the predefined call method through the scenario interface implementation class to call the corresponding data of the instance to obtain the execution dimension application data; the call method is output in a multi-way balanced search tree.
[0050] In some embodiments, when performing scenario execution configuration, the executor enters the scenario configuration page and selects the newly added scenario dimension. At this time, the configuration page will call the predefined business scenario acquisition method getSceneList. This method will obtain the scenekey of the scenario dimension corresponding to the scenario dimension selected by the executor from the central storage, find the fully qualified class name of the scenario interface implementation class SceneService, then convert the fully qualified class name into an instance through reflection, and finally call the predefined call method for this instance (for example: the scenario tree acquisition method getSceneTree), and return the execution dimension application data to the page of the data center system.
[0051] In some embodiments, the scenario tree acquisition method returns the output using a multi-way balanced search tree, and the multi-way balanced search tree includes at least any one of: B-tree, B+-tree, or B*-tree.
[0052] Step S12: Obtain the module to be executed and multiple first intelligent components according to the execution dimension application data, generate a first business solution protocol for the business scenario to be newly added according to the module to be executed and the multiple first intelligent components, and store the first business solution protocol in the execution solution pool.
[0053] It should be noted that the first business solution protocol is the business solution protocol generated for the business scenario to be newly added, the second business solution protocol is the business solution protocol to be implemented selected from the execution solution pool, and there are multiple business solution protocols in the execution solution pool. The first intelligent component is the intelligent component generated for the business scenario to be newly added when adding a new business scenario and is executed by the data center system; the second intelligent component is the specific intelligent component obtained after deserializing the execution page of the business solution protocol to be implemented and is executed by the execution agent system.
[0054] In some embodiments, the intelligent component can be used for AI recognition, data analysis, remote call, etc.
[0055] In some embodiments, obtaining the module to be executed and multiple first intelligent components according to the execution dimension application data, and generating a first business solution protocol for the business scenario to be newly added according to the module to be executed and the multiple first intelligent components includes: selecting the module to be executed from the execution dimension application data, obtaining the first application identifier of the application data, and calling the predefined intelligent component list acquisition method to obtain multiple first intelligent components corresponding to the business scenario to be newly added, and generating a first business solution protocol according to the first application identifier and the multiple first intelligent components.
[0056] It should be noted that the first application identifier is the application identifier of the module to be executed corresponding to the execution dimension application data of the business scenario to be newly added, and the second application identifier is the application identifier of the master data applied to the scenario to be implemented.
[0057] In some embodiments, a first business solution protocol is generated based on a first application identifier and a plurality of first intelligent components, including: sequentially assembling and setting control parameters for the plurality of first intelligent components to obtain an assembly result, and generating a first business solution protocol in which an execution dimension is bound to the first application identifier according to the assembly result and the first application identifier.
[0058] In some embodiments, when obtaining and storing a business solution protocol, an executor selects a to-be-executed module required from the execution dimension application data. At this time, the configuration page calls the smartComponentList method predefined in the execution agent system, and this method returns a plurality of first intelligent components that can be supported by this business scenario. Then, the plurality of first intelligent components are assembled and the control parameters are set. After clicking the save button, a business solution protocol in which the execution dimension scenekey is bound to the application identifier applyid of the to-be-executed module is generated, and the business solution protocol is stored in the execution solution pool.
[0059] Step S13: Select a second business solution protocol to be implemented from the execution solution pool, obtain the to-be-executed page of the second business solution protocol, and serialize the script of the to-be-executed page to obtain a serialization result.
[0060] In some embodiments, selecting a second business solution protocol to be implemented from the execution solution pool, obtaining the to-be-executed page of the second business solution protocol, and serializing the script of the to-be-executed page to obtain a serialization result includes: entering the master data of the to-be-implemented scenario application, and selecting and parsing the to-be-implemented second business solution protocol from a plurality of first business protocols through the second application identifier and the second scenario dimension of the master data, rendering the execution page, and performing execution on the execution page by serializing the script of the execution page to obtain a serialization result.
[0061] In some embodiments, the master data is a specific product version of the account opening business scenario or a version of a specific module scenario.
[0062] In some embodiments, when presenting a business solution protocol, an executor enters the master data of the to-be-implemented scenario application, and through the application identifier applyid and the execution dimension scenekey of this master data, calls the getSceneApplyProtocol method of the scenario application protocol on any page to obtain and parse the execution solution protocol from the execution solution pool, and renders a general execution page for the scenario.
[0063] In some embodiments, when a business solution protocol needs to be executed, in the data center system, an executor clicks the execution button on the execution page. At this time, the execution page serializes the solution protocol in JSON format and transmits it to the execution agent system.
[0064] Step S14: Transmit the serialized result to the execution agent system so that after receiving the serialized result, the execution agent system implements the corresponding business.
[0065] In some embodiments, after receiving the serialized result, the execution agent system implements the corresponding business, including: after receiving the serialized result, the execution agent system performs script deserialization on the serialized result through the intelligent component adapter to obtain specific second intelligent components and an execution process, and sets the global context and parameter substitution corresponding to the second intelligent components and the execution process to obtain a parameter environment, and implements the corresponding business according to the parameter environment.
[0066] In some embodiments, when a business solution protocol needs to be executed, in the execution agent system, the solution protocol will be deserialized from JSON through the intelligent component adapter, converted into specific intelligent components and an execution process, and the global context and parameter substitution will be set up to obtain a parameter environment, and specific business implementation operations will be performed according to the parameter environment.
[0067] In some embodiments, during the process of implementing the corresponding business, including: if, according to the execution process, a step fails to execute, the business will be placed in a retry queue, and the service resource status will be monitored according to the proportional-integral-derivative control algorithm to periodically execute the retry queue, and the implementation status of the execution task will be sent to a message queue so that the data center system can monitor the implementation status of the re-executed business according to the message queue.
[0068] In some embodiments, the proportional-integral-derivative control algorithm can be a PID (Proportion Integration Differentiation) controller, or an incremental PID controller, a trapezoidal integral PID controller, a PID controller with dead zone, a variable-speed integral PID controller, a PID controller with filter, or a PID controller based on feedforward compensation.
[0069] In some embodiments, when implementing the corresponding business, the execution agent system uses an internal intelligent execution regulator. When a certain step fails to execute, the task will be put into the retry queue, and the PID controller will monitor the service resource status, periodically execute the retry queue tasks, and send the solution implementation status to the message queue in real time.
[0070] In some embodiments, the data center system monitors the implementation status of the re-executed business according to the message queue, including: the data center system asynchronously monitors the implementation status of the re-executed business in the message queue. If the step corresponding to the re-executed business fails to execute, specific failure information will be generated, and according to the failure information, a personalized implementation strategy will be carried out for the failed step.
[0071] In some embodiments, when the data center system obtains feedback on task implementation, the execution plan analysis module of the data center system asynchronously listens to the message queue to monitor the implementation of the execution plan. When a certain step of the task fails, specific failure information will be returned. Based on the failure information, a personalized implementation strategy for this step can be customized for the customer, so as to be able to execute at a fixed point and save resources.
[0072] See Figure 2 , which is a schematic flowchart of another data interaction method for fast-moving consumer goods multi-business scenarios provided by this embodiment. In Figure 2 , the executor first obtains the execution dimension on the data center system, then obtains the corresponding first scenario dimension and fully qualified class name of the execution dimension, configures according to the first scenario dimension and fully qualified class name to obtain the first business solution protocol, and stores the first business solution protocol in the execution plan pool. If a certain business needs to be executed, the executor selects the execution dimension on the execution agent system 22 to obtain the corresponding second application identifier and second scenario dimension of the business scenario to be executed, and queries the second business solution protocol to be executed in the execution plan pool according to the second application identifier and second scenario dimension, and executes the corresponding task according to the second business solution protocol, including executing, adjusting the second business solution protocol, and collecting failure information when the execution fails for the data center system to listen.
[0073] In this embodiment, the framework of the data interaction device for fast-moving consumer goods multi-business scenarios is divided into: a data center system and an execution agent system. The transaction of scenario addition and task implementation is segmented. According to the data center system, a business scenario can be added separately, and the execution agent system implements separately based on the newly added business scenario, so as to refine the business granularity of the business scenario, and then the needs of multiple different customers can be coordinated and refined at the same time; moreover, when adding a business separately in the data center system, based on the unified scenario interface implementation class, it is convenient to expand new business scenarios. Therefore, based on the interaction between the two systems, different scenarios can be added and implemented based on the newly added business, so as to improve the applicability of the fast-moving consumer goods data management method to different scenarios.
[0074] Embodiment 2
[0075] See Figure 3 , which is a schematic structural diagram of a data interaction device for fast-moving consumer goods multi-business scenarios provided by this embodiment. The data interaction device for fast-moving consumer goods multi-business scenarios includes: a data center system 21 and an execution agent system 22. In Figure 3 , the data center system 21 includes: a scenario addition and configuration module 211, a business solution protocol generation module 212, a serialization module 213, and an interaction module 214.
[0076] It should be noted that the scenario addition and configuration module 211 outputs execution dimension application data for the newly added business scenario and transmits the execution dimension application data to the business solution protocol generation module 212; after receiving the execution dimension application data, the business solution protocol generation module 212 generates a first business solution protocol and stores it in the execution solution pool; when a task needs to be executed, the serialization module 213 selects a second business solution protocol from the execution solution pool, outputs the serialization result corresponding to the second business solution protocol, and transmits the serialization result to the interaction module 214, so that the interaction module 214 transmits the serialization result to the execution agent system 22 to execute the corresponding task.
[0077] In some embodiments, the execution agent system 22 includes: a smart component factory 221, a solution processor 222, and an intelligent execution regulator 223; among them, the smart component factory 221 is used to externally provide highly encapsulated smart components based on the policy pattern and factory design pattern, shielding the underlying operation details of the operating system, database, and file stream; the solution processor 222 is used to split the steps of the solution issued by the central execution system and assemble and execute the selected smart components of the general solution to complete the personalized execution solution of the customer; the intelligent execution regulator 223 is used to limit the flow through the token bucket algorithm, retry abnormal steps, and dynamically optimize execution resources to ensure the efficient execution of the execution solution.
[0078] In some embodiments, the execution agent system 22 further includes: an execution container; the execution container includes: the above-mentioned solution processor 222 and intelligent execution regulator 223, as well as a data collector 224.
[0079] In some embodiments, the scenario addition and configuration module 211 includes: a scenario management module 217; among them, the scenario management module 217 is used to define standardized execution scenarios and the required execution dimensions under the scenarios, including: tenant account opening scenario, account upgrade scenario, order management scenario, budget management scenario, tenant module authorization scenario, and module deployment scenario, and the specific implementation of the scenario addition and configuration module 211 is to add business scenarios based on the standardized execution scenarios and the required execution dimensions specified by the scenario management module 217.
[0080] The data center system 21 further includes: a tenant management module 210, an execution solution pool module 215, and an execution solution analysis module 216; among them, the tenant management module 210 is used to uniformly manage the customer information in the fast-moving consumer goods field, and each customer is opened by a certain account opening product version; the execution solution pool module 215 formulates and manages business solution protocols for fast-moving consumer goods field customers with different attributes; the execution solution analysis module 216 is used to feedback and analyze the execution effect of the customer execution solution to provide functional support for formulating a better execution solution.
[0081] In some embodiments, the execution plan pool module 215 manages the service plan protocols generated by the service plan protocol generation module 212. It should be noted that one service plan protocol corresponds to one service plan.
[0082] In some embodiments, the execution plan pool module 215 can store and reconfigure the service plan protocols.
[0083] The scenario addition and configuration module 211 is used to obtain the basic information of the service scenario to be added, and configure the service scenario to be added according to the basic information to obtain the execution dimension application data; the basic information includes: the first scenario dimension and the fully qualified class name of the scenario interface implementation class.
[0084] In some embodiments, configuring the service scenario to be added according to the basic information to obtain the execution dimension application data includes: querying the fully qualified class name from the central storage according to the first scenario dimension, if the fully qualified class name exists, converting the fully qualified class name into an instance of the scenario interface implementation class through reflection, and performing data call on the instance according to the predefined call method to obtain the execution dimension application data.
[0085] In some embodiments, performing data call on the instance according to the predefined call method to obtain the execution dimension application data includes: calling the predefined call method through the scenario interface implementation class to call the data corresponding to the instance to obtain the execution dimension application data; the call method is output in a multi-fork balanced search tree.
[0086] The service plan protocol generation module 212 is used to obtain the module to be executed and multiple first intelligent components according to the execution dimension application data, and generate the first service plan protocol for the service scenario to be added according to the module to be executed and the multiple first intelligent components, and store the first service plan protocol in the execution plan pool.
[0087] In some embodiments, obtaining the module to be executed and multiple first intelligent components according to the execution dimension application data, and generating the first service plan protocol for the service scenario to be added according to the module to be executed and the multiple first intelligent components includes: selecting the module to be executed from the execution dimension application data to obtain the first application identifier of the application data, and calling the predefined intelligent component list obtaining method to obtain multiple first intelligent components corresponding to the service scenario to be added, and generating the first service plan protocol according to the first application identifier and the multiple first intelligent components.
[0088] In some embodiments, a first service solution protocol is generated based on a first application identifier and a plurality of first intelligent components, including: sequentially assembling and setting control parameters for the plurality of first intelligent components to obtain an assembly result, and generating a first service solution protocol in which an execution dimension is bound to the first application identifier according to the assembly result and the first application identifier.
[0089] In some embodiments, the service solution protocol generation module 212 calls the solution processor 222 to assemble a plurality of intelligent components. After the solution processor 222 finishes the assembly, the assembly result is fed back to the service solution protocol generation module 212 to achieve personalized customization for customers.
[0090] The serialization module 213 is configured to select a second service solution protocol to be implemented from the execution solution pool, obtain the page to be executed of the second service solution protocol, and serialize the page to be executed by a script to obtain a serialization result.
[0091] In some embodiments, selecting a second service solution protocol to be implemented from the execution solution pool, obtaining the page to be executed of the second service solution protocol, and serializing the page to be executed by a script to obtain a serialization result includes: entering the master data of the application scenario to be implemented, and selecting and parsing the second service solution protocol to be implemented from a plurality of first service protocols through the second application identifier and the second scenario dimension of the master data, rendering an execution page, and serializing the execution page by a script and executing the execution page to obtain a serialization result.
[0092] The interaction module 214 is configured to transmit the serialization result to the execution agent system, so that after receiving the serialization result, the execution agent system implements the corresponding service.
[0093] In some embodiments, after receiving the serialization result, the execution agent system implements the corresponding service, including: after receiving the serialization result, the execution agent system performs script deserialization on the serialization result through the intelligent component adapter to obtain specific second intelligent components and an execution process, and sets the global context and parameter replacement corresponding to the second intelligent components and the execution process to obtain a parameter environment, and implements the corresponding service according to the parameter environment.
[0094] In some embodiments, the intelligent component factory 221 performs script deserialization on the serialization result through the intelligent component adapter to obtain specific second intelligent components and an execution process, and sets the global context and parameter replacement corresponding to the second intelligent components and the execution process to obtain a parameter environment.
[0095] In some embodiments, during the process of implementing the corresponding service, it includes: when there is a step execution failure according to the execution process, putting the service into a retry queue, monitoring the service resource situation according to the proportional-integral-derivative control algorithm, periodically executing the retry queue, and sending the implementation situation of the execution task to a message queue, so that the data center system monitors the implementation situation of the re-executed service according to the message queue.
[0096] In some embodiments, the scenario processor 222 splits the steps of the real-time service and sends the split result to the intelligent execution regulator 223 for execution.
[0097] In some embodiments, the intelligent execution regulator 223 implements the corresponding service according to the split result transmitted by the scenario processor 222, including: when there is a step execution failure according to the execution process, putting the service into a retry queue, monitoring the service resource situation according to the proportional-integral-derivative control algorithm, periodically executing the retry queue, and sending the implementation situation of the execution task to a message queue, so that the data center system monitors the implementation situation of the re-executed service according to the message queue.
[0098] In some embodiments, the execution scenario analysis module 216 is used to monitor the implementation situation of the re-executed service according to the message queue, including: the data center system asynchronously monitors the implementation situation of the re-executed service in the message queue. If the step implementation corresponding to the re-executed service fails, specific failure information is generated, and according to the failure information, a personalized implementation strategy is carried out for the failed step.
[0099] In this embodiment, the framework of the fast-moving consumer goods multi-scenario data interaction device is divided into: a data center system and an execution agent system. Transaction splitting is performed on scenario addition and task implementation. The data center system can separately add a business scenario, and the execution agent system separately implements based on the added business scenario, thereby refining the business granularity of the business scenario. Furthermore, it can co-ordinate and refine the needs of multiple different customers at the same time; and when adding a business separately in the data center system, it is based on a unified scenario interface implementation class, which is convenient for expanding new business scenarios. Therefore, based on the interaction between the two systems, different scenarios can be added and implemented based on the added business, thereby improving the applicability of the fast-moving consumer goods data management method to different scenarios.
[0100] Those skilled in the art should understand that the embodiments of the present application may also provide a computer program product. Therefore, the present application may be implemented in the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application may be implemented in the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk memory, CD-ROM, optical memory, etc.) containing computer-usable program code.
[0101] The present application is described with reference to the flowcharts and / or block diagrams of methods, apparatuses (systems), and computer program products according to the embodiments of the present application. It should be understood that each flow and / or block in the flowchart and / or block diagram, and the combination of flows and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing devices generate means for implementing the functions specified in Figure 1 one flow or multiple flows and / or blocks Figure 1 one block or multiple blocks.
[0102] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory generate a manufactured article including instruction means, and the instruction means implements the functions specified in Figure 1 one flow or multiple flows and / or blocks Figure 1 one block or multiple blocks.
[0103] These computer program instructions can also be loaded onto a computer or other programmable data processing device, so that a series of operation steps are executed on the computer or other programmable device to generate a computer-implemented process. Therefore, the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in Figure 1 one flow or multiple flows and / or blocks Figure 1 one block or multiple blocks.
[0104] The above is only the preferred embodiment of the present invention. It should be noted that for those of ordinary skill in the art, without departing from the technical principle of the present invention, several improvements and modifications can be made, and these improvements and modifications should also be regarded as the protection scope of the present invention.
Claims
1. A data interaction method for multiple business scenarios of fast-moving consumer goods, applied to a data center system; The data interaction device for multiple business scenarios of fast-moving consumer goods includes: The data center system and the execution agent system, characterized in that the data interaction method for multiple business scenarios of fast-moving consumer goods includes: Obtain the basic information of the business scenario to be added, and configure the business scenario to be added according to the basic information to obtain execution dimension application data; the basic information includes: the first scenario dimension and the fully qualified class name of the scenario interface implementation class; According to the execution dimension application data, obtain the module to be executed and multiple first intelligent components, and generate the first business solution protocol for the business scenario to be added according to the module to be executed and the multiple first intelligent components, and store the first business solution protocol in the execution solution pool; Select the second business solution protocol to be implemented from the execution solution pool, obtain the page to be executed of the second business solution protocol, and script-serialize the page to be executed to obtain a serialization result; Transmit the serialization result to the execution agent system so that after receiving the serialization result, the execution agent system implements the corresponding business; The configuring the business scenario to be added according to the basic information to obtain execution dimension application data includes: Query the fully qualified class name from the central storage according to the first scenario dimension. If the fully qualified class name exists, convert the fully qualified class name into an instance of the scenario interface implementation class through reflection, and perform data call on the instance according to the predefined call method to obtain execution dimension application data.
2. The data interaction method according to claim 1, wherein The performing data call on the instance according to the predefined call method to obtain execution dimension application data includes: Call the predefined call method through the scenario interface implementation class to call the data corresponding to the instance to obtain execution dimension application data; the call method is output in a multi-way balanced search tree.
3. The data interaction method according to claim 1, wherein The obtaining the module to be executed and multiple first intelligent components according to the execution dimension application data, and generating the first business solution protocol for the business scenario to be added according to the module to be executed and the multiple first intelligent components includes: Select the module to be executed from the execution dimension application data to obtain the first application identifier of the application data, and call the predefined intelligent component list obtaining method to obtain the multiple first intelligent components corresponding to the business scenario to be added, and generate the first business solution protocol according to the first application identifier and the multiple first intelligent components.
4. The data interaction method according to claim 3, wherein The generating the first business solution protocol according to the first application identifier and the multiple first intelligent components includes: Assemble and set control parameters for the multiple first intelligent components in sequence to obtain an assembly result, and generate the first business solution protocol bound by the execution dimension and the first application identifier according to the assembly result and the first application identifier.
5. The data interaction method according to claim 1, wherein The selecting the second business solution protocol to be implemented from the execution solution pool, obtaining the page to be executed of the second business solution protocol, and script-serializing the page to be executed to obtain a serialization result includes: Enter the master data for the scenario application to be implemented, and select and parse the second business solution protocol to be implemented from multiple first business protocols through the second application identifier and the second scenario dimension of the master data, render the execution page, serialize the script of the execution page, and execute the execution page to obtain a serialization result.
6. The data interaction method according to claim 1, wherein After receiving the serialization result, the execution agent system implements the corresponding business, including: After receiving the serialization result, the execution agent system performs script deserialization on the serialization result through the intelligent component adapter to obtain specific second intelligent components and an execution process, and sets the global context and parameter replacement corresponding to the second intelligent components and the execution process to obtain a parameter environment, and implements the corresponding business according to the parameter environment.
7. The data interaction method according to claim 6, characterized in that, During the process of implementing the corresponding business, it includes: If a step fails according to the execution process, put the business into the retry queue, monitor the service resource status according to the proportional-integral-derivative control algorithm, periodically execute the retry queue, and send the implementation status of the execution task to the message queue, so that the data center system monitors the implementation status of the re-executed business according to the message queue.
8. The data interaction method according to claim 7, wherein The data center system monitors the implementation status of the re-executed business according to the message queue, including: The data center system asynchronously monitors the implementation status of the re-executed business in the message queue. If the step implementation corresponding to the re-executed business fails, specific failure information is generated, and according to the failure information, a personalized implementation strategy is carried out for the failed step.
9. A data interaction device for multiple business scenarios of fast-moving consumer goods, characterized in that, The data interaction device for multiple business scenarios of fast-moving consumer goods includes: a data center system and an execution agent system; the data center system includes: a scenario addition and configuration module, a business solution protocol generation module, a serialization module, and an interaction module; where The scenario addition and configuration module is used to select an execution dimension of a business scenario to be added, obtain the basic information of the business scenario, and configure the business scenario to be added according to the basic information to obtain execution dimension application data; the basic information includes: the first scenario dimension and the fully qualified class name of the scenario interface implementation class. The business solution protocol generation module is used to obtain the module to be executed and multiple first intelligent components according to the execution dimension application data, and generate the first business solution protocol of the business scenario to be added according to the module to be executed and the multiple first intelligent components. The serialization module is used to select the second business solution protocol to be implemented from multiple first business solution protocols, obtain the execution page of the second business solution protocol, and perform script serialization on the execution page to obtain a serialization result. The interaction module is used to transmit the serialization result to the execution agent system, so that the execution agent system implements the corresponding business after receiving the serialization result. The configuring the business scenario to be added according to the basic information to obtain execution dimension application data includes: Query the fully qualified class name from the central storage according to the first scenario dimension. If the fully qualified class name exists, convert the fully qualified class name into an instance of the scenario interface implementation class through reflection, and perform data calls on the instance according to the predefined call method to obtain the execution dimension application data.
Citation Information
Patent Citations
Remote interface agent calling method and device, computer equipment and storage medium
CN113419876A
Page generation method and device, computing equipment and storage medium
CN115509663A