Configuration file based event-driven data flow generation method, system and product

Abstract

The application provides a configuration file-based event-driven data flow generation method, system and product, wherein the method comprises: obtaining a configuration file; parsing the configuration file to obtain a corresponding semantic model; generating event-driven data flow processing logic according to the semantic model; and deploying the event-driven data flow processing logic, including: deploying the event-driven data flow processing logic in combination with the priority order of platform core configuration, field shared template, customized configuration and runtime instance configuration, and the set arbitration rule; and when a specified event trigger corresponding to the event-driven data flow processing logic is listened to, executing a processing flow corresponding to the specified event. The application can be applied to the field of basic network and information security software, can automatically generate event-driven data flow based on a configuration file, can improve development efficiency, reduce maintenance cost, enhance system flexibility and business adaptation capability, and can solve the conflict and inconsistency problems possibly caused by multiple source configurations.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of data processing, in particular to an event-driven data flow generation method, system and product based on a configuration file. BACKGROUND

[0002] With the increasing complexity of business systems, event-driven architecture (EDA) has gradually become a key design pattern for building loosely coupled and highly scalable systems. Under this architecture, various business events, such as order creation, payment success, or device state change, as the core trigger source of system operation, can automatically drive subsequent data processing and business logic execution, covering data persistence, message notification, service invocation, and other operations.

[0003] In traditional implementations, systems usually rely on hardcoding or customized scripts to define event listening, data flow, and business processing flow. This mode limits development efficiency, as each new event or business scenario requires writing corresponding event processing code, making it difficult to quickly respond to business changes. At the same time, events and processing logic are scattered throughout the system, resulting in high maintenance and tracking costs, and making business rules and coding implementations tightly coupled, requiring re-coding and deployment upon rule changes. Additionally, due to the lack of a unified description and configuration model, different teams have different implementation methods, making it difficult to achieve standardization and logic reuse.

[0004] In response to this, some configuration-driven or low-code platform solutions have emerged in the industry, such as using visual tools to orchestrate events and processing flow, defining simple event routing and processing steps using JSON or YAML, and using partial ETL tools or workflow engines to implement configuration-based data flow definition. However, these solutions still have obvious limitations: their configurations mostly remain at the technical parameter level, such as service addresses and parameter names, and are difficult to carry semantic information such as "why to execute" and "in what business context"; in terms of data flow generation, they often only support single-step processing, such as event forwarding and simple processing, lacking the ability to automatically build end-to-end complete operation chains including multiple steps, conditional branches, and exception handling; more critically, there is currently a lack of a unified, structured, and extensible configuration model that can clearly describe events, business logic, and required data flow operations, and drive the system to automatically generate complete executable logic flow. Therefore, the current event-driven data flow operation technical solution still needs further improvement. SUMMARY

[0005] The first object of the present application is to provide an event-driven data flow generation method based on a configuration file, which can reliably and automatically generate complete, flexible, and easy-to-maintain event-driven data flow.

[0006] The second object of the present application is to provide a system for implementing the above-mentioned configuration file-based event-driven data flow generation method.

[0007] The third object of the present application is to provide a computer program product for implementing the above-mentioned configuration file-based event-driven data flow generation method.

[0008] To achieve the above-mentioned first object, the present application provides a configuration file-based event-driven data flow automatic generation method, which comprises the following steps: obtaining a plurality of configuration files, including configuration files in a shared configuration form and configuration files in a specific configuration form; parsing the configuration files to obtain corresponding semantic models; generating event-driven data flow processing logic according to the semantic models; and deploying the event-driven data flow processing logic, including sequentially deploying the event-driven data flow processing logic in the order of a domain shared template, a customized configuration, and a runtime instance configuration, and under the constraint of a set arbitration rule, the domain shared template corresponding to the configuration files in the shared configuration form, the customized configuration and the runtime instance configuration corresponding to the configuration files in the specific configuration form, and the arbitration rule including a set security policy; and when a specified event trigger corresponding to the event-driven data flow processing logic is detected, executing a processing flow corresponding to the specified event. As can be seen from the above scheme, based on the event and operation logic description of various elements in the configuration file, the present application automatically generates a complete event-driven data flow, integrates event definition, business logic, and data flow operation steps through multi-level, structured, and semantic analysis, decouples business semantics and technical implementation, and realizes highly flexible automatic data flow arrangement through the unified medium of the configuration file, supports rapid iteration, flexible adjustment, and multi-scenario reuse, thereby realizing the automatic generation of executable data flow from configuration, and significantly improving development efficiency, reducing maintenance cost, and enhancing system flexibility and business adaptation capability. On this basis, to solve the conflict and inconsistency problems that may be caused by multiple source configurations, the priority order of the platform core configuration, the domain shared template, the customized configuration, and the runtime instance configuration is combined, and a set arbitration rule is set, thereby further improving the flexibility, maintainability, and reusability of the configuration.

[0009] Further, the configuration file includes the following configuration contents: event, condition, operation step, flow control, context, and parameter.

[0010] As can be seen, the required event and operation logic after the event trigger can be fully described. The configuration file not only describes the basic information of the event, but also contains business objectives, context, and expected data flow operations, thereby realizing explicit expression of the operation logic. The configuration file can support multiple types of configuration elements such as event, data extraction, service calling, flow control, exception handling, and notification, and support flexible configuration of complex business scenarios.

[0011] Further, when the configuration file is parsed to obtain the semantic model, the following steps are included: lexical analysis, syntax analysis, and semantic analysis of the configuration file to obtain an internally operable semantic model.

[0012] Therefore, the configuration file can be converted into a corresponding semantic model matching the target system, thereby facilitating subsequent generation of event-driven data flow processing logic.

[0013] Further, after the configuration file is obtained, the configuration file is verified for legality.

[0014] Therefore, the reliability of the configuration can be improved.

[0015] Further, the event-driven data flow processing logic is generated according to the semantic model, including: determining semantic objects and logic units mapped by the semantic model; constructing a flow model based on the semantic model, the semantic objects, and the logic units; and automatically generating executable logic code or a runtime flow according to the flow model.

[0016] Therefore, the operation logic description and technical operation steps in the configuration are parsed and mapped into an executable flow model, supporting semantic-level configuration reuse and orchestration. A complete event-driven data flow including multiple steps, logic control, and exception handling can be automatically constructed according to the configuration content, without the need for manual code writing.

[0017] Further, deploying the event-driven data flow processing logic includes: registering an event listener through a service discovery mechanism.

[0018] Further, after the event-driven data flow processing logic is deployed, when a configuration file update is monitored, the event-driven data flow processing logic is redeployed according to the configuration file.

[0019] Therefore, the data flow logic can be adjusted by modifying the configuration file, without the need for re-development and deployment, greatly improving system iteration efficiency and business response speed.

[0020] To achieve the above-mentioned second purpose, the application provides a configuration file-based event-driven data flow generation system for realizing the above-mentioned method, which comprises a configuration analysis module, an operation semantic generation module, an event registration and deployment module, and an event execution module, wherein the configuration analysis module is connected to the operation semantic generation module, the operation semantic generation module is connected to the event registration and deployment module, and the event registration and deployment module is connected to the event execution module; the configuration analysis module is used to analyze the obtained configuration file to obtain a corresponding semantic model; the operation semantic generation module is used to generate event-driven data flow processing logic according to the semantic model; the event registration and deployment module is used to deploy the event-driven data flow processing logic, including deploying the event-driven data flow processing logic in combination with the priority order of platform core configuration, domain shared template, customized configuration, and runtime instance configuration, and the set arbitration rule; and the event execution module is used to execute a specified event corresponding processing flow when the event-driven data flow processing logic corresponding specified event trigger is listened to.

[0021] To achieve the above-mentioned third purpose, the application provides a computer program product comprising computer instructions, wherein the computer instructions are executed by a processor to realize the above-mentioned configuration file-based event-driven data flow automatic generation method. BRIEF DESCRIPTION OF DRAWINGS

[0022] Figure 1 FIG. 1 is a system framework diagram of a configuration file-based event-driven data flow generation system embodiment of the application.

[0023] Figure 2 FIG. 2 is a flowchart of a configuration file-based event-driven data flow generation method embodiment of the application.

[0024] The application will be further described below in combination with the drawings and embodiments. DETAILED DESCRIPTION

[0025] The configuration file-based event-driven data flow generation method of the application automatically generates complete, flexible and easy-to-maintain event-driven data flow by simultaneously describing events and business operation logic through a configuration file. The application further provides a system for realizing the above-mentioned configuration file-based event-driven data flow generation method.

[0026] Configuration file-based event-driven data flow generation system embodiment:

[0027] Referring to Figure 1The profile-based event-driven data flow generation system 10 of the embodiment includes a configuration parsing module 101, an operation semantic generation module 102, an event registration and deployment module 103, and an event execution module 104. The configuration parsing module 101 is connected to the operation semantic generation module 102, the operation semantic generation module 102 is connected to the event registration and deployment module 103, and the event registration and deployment module 103 is connected to the event execution module 104.

[0028] The profile-based event-driven data flow generation system 10 defines events and operation logic by obtaining a structured configuration file 20 (which can be multiple configuration files), and realizes complete event-driven data flow processing logic in combination with multi-level configuration management, and then listens to specified events according to the event-driven data flow processing logic, and automatically drives the execution of complete data processing and business operation links according to the configuration once the specified events are triggered, without the need for manual code writing or modification.

[0029] The configuration file 20, as an input part of the event-driven data flow generation system 10, includes multiple configuration elements for describing event basic information (such as event type, source, trigger condition, etc.), operation logic description (such as business target, context, expected result, data flow operation step (such as data conversion, service call, condition judgment, exception handling, message notification, etc.), flow control semantics (such as sequential execution, parallel execution, branch judgment, retry mechanism, etc.). Specifically, one configuration file 20 specifically includes the following defined configuration contents: event, condition, operation step, flow control, context and parameter. The event is a trigger under the corresponding condition (such as button click, API call, message arrival, timing task, etc.). The condition is a business rule, a verification condition that needs to be met after triggering. The operation step is a specific operation to be executed (such as data verification, database writing, service call, message notification, etc.). The flow control is the definition of the execution between steps, such as sequential execution, branch judgment, loop, exception handling, retry mechanism, etc. The context and parameter are data carried by the event, variable transmission, environment information, etc.

[0030] The configuration file 20 can include multiple forms. Specifically, the configuration file includes a shared configuration form and a specific configuration form. The shared configuration form is used as a general template to define a general event mode (such as user login, data update, etc.), and contains reusable event structures, dependencies, and default parameters. The specific configuration form is used as an instantiation part to personalize parameters (such as threshold values, trigger conditions, and user roles) for specific scenarios, and supports dynamic overriding of the shared configuration. The intelligent calling mechanism: when an event is generated, the shared configuration form template is matched first, and then specific parameters are injected (similar to object-oriented inheritance and override), so that flexible configuration can be performed. By defining different forms of configuration files, multiple configuration files can be configured, the configuration flexibility is improved, a multi-level configuration management system is supported, and an intelligent configuration parsing and conflict arbitration mechanism is supported.

[0031] The configuration parsing module 101 is configured to read and check the configuration file, and convert the configuration items in the configuration into structured data in the target system, that is, into an internal operational semantic model. Specifically, the configuration file can be read from a local disk, a remote configuration center, or a database, and then the configuration file is subjected to lexical analysis, syntax analysis, and semantic analysis, so that the configuration file is converted from an original structure (such as a key-value pair of JSON / YAML) into an internal operational semantic model of the target system, and is subjected to legality verification, for example, whether a required field exists, whether a field type matches, and whether a reference is valid. If the legality verification is passed, the configuration file can be used for automatic generation of the event-driven data flow, and if the legality verification is not passed, the configuration file cannot be used for automatic generation of the event-driven data flow.

[0032] In the embodiment, the target system is the configuration file-based event-driven data flow generation system 10. In different embodiments, the target system can be a system different from the configuration file-based event-driven data flow generation system, that is, the event execution module 104 is in the target system but not in the configuration file-based event-driven data flow generation system, so that the target system is set by the configuration file-based event-driven data flow generation system.

[0033] Optionally, the configuration parsing module 101 can output an intermediate structure, such as an event definition pair, a condition rule list, an operation step list, and a control flow graph.

[0034] The operation semantic generation module 102 is configured to generate the event or operation logic to be executed based on the parsed data, i.e., generate the event-driven data flow processing logic according to the semantic model. Specifically, first, the semantic objects and logical units mapped by the semantic model in the target system are determined. Then, the flow model is constructed based on the semantic model, the semantic objects and the logical units, which describes: the verification to be performed after the event is triggered; the business operation to be performed after the verification is passed; whether to interrupt, prompt an error or other branch logic if the verification fails; the dependency, parallelism, loop and other relationships between the processing operations. Finally, the logic code or runtime flow for execution is automatically generated according to the flow model, which can be implemented through an existing code generation model, for example, generating a business logic function or class method in Python / Java / JavaScript, etc. Alternatively, a runtime flow (Flow / Pipeline) is generated, in which case no code is generated, but a flow definition object / Directed Acyclic Graph (DAG) is generated, which is scheduled and executed by a runtime event-driven data flow automatic generation engine based on a configuration file.

[0035] The event registration and deployment module 103 is configured to register and deploy the generated event or operation logic in the target system, so that the target system can respond to the registered event and perform the corresponding operation, i.e., deploy the event-driven data flow processing logic. The event listener is registered through a service discovery mechanism, i.e., the generated event processing logic is bound to a specific event source (such as an HTTP request, a message queue, a timer, a front-end button, etc.), so that when the event is triggered in the target system, the target system automatically performs the verification, operation, flow control and other operations according to the generated code or flow definition.

[0036] Optionally, the event registration and deployment module 103 provides extension points to support plug-in extension (such as custom verifier, operation executor, notification channel, etc.), as well as monitoring and logging: recording the execution status, time consumption, exception information of each step, for operation and maintenance and debugging.

[0037] The event registration and deployment module 103 implements the deployment of the event-driven data flow processing logic, including identifying the current running environment, combining the priority order of the platform core configuration, the domain shared template, the customized configuration and the runtime instance configuration, and deploying the event-driven data flow processing logic according to the set arbitration rules.

[0038] The platform core configuration defines the most basic and unchangeable meta-model and standard interface of the target system, such as the fields (id, name, version) that all events / rules must contain, the standard plug-in interface (such as validate(), execute()), the syntax specification of event dependencies, etc. This layer is maintained by platform developers and is the "syntax basis" of the entire configuration system.

[0039] The domain shared template is a group of semi-finished configuration templates organized by business domains (such as user management, order processing, risk control, etc.), which contains common condition structures, default parameters, and best practices in the domain, such as "triggering alarm after user login failure for a certain number of times". This layer is maintained by domain architects and has high reusability. The domain shared template corresponds to the configuration file in the form of shared configuration.

[0040] Customized configuration is project / environment-specific configuration, which is customized for different projects, teams, or deployment environments (such as development, testing, production), and is used to override the default values in the domain template, such as adjusting the failure threshold in the test environment. This layer is maintained by project leaders and has environmental adaptability.

[0041] Runtime instance configuration is dynamically adjusted by users or systems at runtime, such as temporarily modifying a rule threshold or enabling debugging mode. This layer of configuration supports real-time effect and records the source and context of the adjustment for auditing and optimization.

[0042] Customized configuration and runtime instance configuration correspond to configuration files in the form of specific configuration.

[0043] The arbitration rule is determined according to the target system and serves as an internal arbitration rule. When there is a conflict between different levels of the same parameter, the final effective value is automatically selected according to the priority to ensure that the system behavior meets the expected and safe and reliable. For example, the arbitration rule ensures that the event-driven data flow processing logic is deployed in the order of platform core configuration, domain shared template, customized configuration, and runtime instance configuration. On this basis, the security policy further ensures the security of the configuration, such as setting limits for the triggering of some events, such as setting a security upper limit and a security lower limit for some trigger conditions.

[0044] As a result, when deploying the driven data flow processing logic, the event registration and deployment module 103 loads and superimposes in order from the platform core configuration, the domain shared template, the customized configuration, and the runtime instance configuration, and the configuration in the later layer can override the default values in the previous layer, thereby achieving precise control and flexible combination of the configuration.

[0045] Specifically, it includes: automatically identifying current running environment (such as production / test), project identification, user role and other information when receiving deployment request; four-layer configuration retrieval and superposition: retrieving platform core configuration (obtaining meta model), domain shared template (obtaining general structure), customized configuration (obtaining environment customized value), and runtime instance (obtaining user real-time adjustment value) in turn, and superposing them layer by layer according to priority to form the final effective configuration; when there is a conflict in the same parameter at different levels, the final effective value is automatically selected according to the priority to ensure that the system behavior meets the expectation and is safe and reliable. Therefore, in a complex configuration environment, the final execution configuration that is legal, reasonable, personalized and conflict-free can be intelligently synthesized.

[0046] The event execution module 104 is configured to output results, wait for event triggering, and execute operation data flow. Specifically, when a specified event corresponding to the event-driven data flow processing logic is triggered, the processing flow corresponding to the specified event is executed.

[0047] The event-driven data flow automatic generation method based on the configuration file comprises the following steps:

[0048] The embodiment based on the configuration file event-driven data flow generation system is realized based on the above embodiment. The following introduces the specific steps Figure 2

[0049] First, step S1 is executed to obtain the configuration file. The configuration file is edited according to the specific requirements and the set format.

[0050] Then, step S2 is executed to determine whether the configuration file passes the legality verification. If the determination result of step S2 is yes, step S3 is executed, otherwise step S7 is executed.

[0051] After the configuration file passes the legality verification, step S3 is executed to parse the semantic model corresponding to the configuration file. Thus, the configuration file is read and converted into structured data, and semantic modeling and verification are performed.

[0052] Then, step S4 is executed to generate event-driven data flow processing logic according to the semantic model. Specifically, the generated event-driven data flow processing logic includes: event listener automatic generation, i.e. automatically generating event listener code according to event definition; data flow operation logic automatic generation, i.e. automatically generating data conversion, filtering, aggregation and other operation logic according to event and operation logic description; data flow path automatic planning, i.e. automatically planning the path of data from source to target according to data flow operation definition, and selecting the optimal processing node; and exception handling mechanism automatic generation, i.e. automatically generating retry, degradation, alarm and other exception operation logic according to exception handling strategy.

[0053] ​Then step S5 is performed, and the event-driven data flow processing logic is deployed. Thus, the automatically generated event-driven data flow processing logic is deployed into the target system.

[0054] Then step S6 is performed, and it is determined whether the configuration file needs to be updated. During the use of the target system, the change of the related configuration can be continuously detected for hot updating. The target system needs to update the related configuration partially or entirely, and the updating is implemented by updating the configuration file or replacing the original configuration file. Thus, the configuration file can be dynamically updated and hot deployed, the configuration change detection is implemented, that is, the change of the configuration file is monitored in real time, and the re-parsing and generation process is triggered; the incremental updating mechanism is implemented, that is, only the changed part is re-generated and deployed, and the system overhead is reduced; the version management is implemented, that is, the version management of the configuration file is supported, and the rollback to the historical version is supported; and the gray release is implemented, that is, the gray release of the new configuration is supported, the old configuration is gradually replaced, and the change risk is reduced. If the determination result of step S6 is yes, step S1 is performed. It needs to be explained that the configuration file obtained at this time can be a new configuration file or the content of a part of the original configuration file. If the determination result of step S6 is no, step S7 is performed.

[0055] Finally, step S7 is performed, and when the specified event corresponding to the event-driven data flow processing logic is triggered, the processing process corresponding to the specified event is performed.

[0056] The above-described configuration file-based event-driven data flow generation system can be used as a basic class of network and information security software and run on a computer device, and the computer device includes a processor and a memory. The memory stores a computer program, and the processor implements each step of the above-described configuration file-based event-driven data flow generation method embodiment when executing the computer program.

[0057] The computer device can include, but is not limited to, a processor and a memory. Those skilled in the art can understand that the computer device can include more or fewer components, or combine certain components, or different components, for example, the computer device can also include an input / output device, a network access device, a bus, etc. For example, the processor can be a central processing unit (CPU), and can also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microcontroller or the processor can also be any conventional processor, etc. The processor is the control center of the computer device, and connects various parts of the entire computer device through various interfaces and lines.

[0058] The computer program product embodiment includes computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer readable storage medium, and the processor executes the computer instructions to make the computer device execute the steps of the above-mentioned configuration file-based event-driven data flow generation method embodiment.

[0059] The computer program product of the embodiment includes computer instructions stored in a computer readable storage medium. The processor of the computer device reads the computer instructions from the computer readable storage medium, and the processor executes the computer instructions to make the computer device execute the steps of the above-mentioned configuration file-based event-driven data flow generation method embodiment.

[0060] In summary, based on the event and operation logic description of various elements in the configuration file, the complete event-driven data flow is automatically generated, the event definition, business logic and data flow operation steps are integrated, the business semantics and technical implementation are decoupled, and the highly flexible automatic data flow arrangement is realized through the configuration file, which supports rapid iteration, flexible adjustment and multi-scenario reuse, thereby realizing the automatic generation from configuration to executable data flow, and significantly improving the development efficiency, reducing the maintenance cost, and enhancing the system flexibility and business adaptation ability. On this basis, in order to solve the conflict and inconsistency problem caused by multiple source configurations, by combining the priority order of the platform core configuration, the domain shared template, the customized configuration and the runtime instance configuration, and the set arbitration rules, the flexibility, maintainability and reusability of the configuration are further improved.

[0061] Finally, it should be noted that the above description is only the preferred embodiment of the present application, and is not intended to limit the present application. For those skilled in the art, the present application can have various changes and modifications, and any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A method for automatically generating event-driven data streams based on configuration files, characterized in that, include: Retrieve multiple configuration files, including configuration files with shared configuration formats and configuration files with specific configuration formats; Parsing the configuration file to obtain the corresponding semantic model includes: performing lexical analysis, syntactic analysis, and semantic parsing on the configuration file to obtain an internally operable semantic model; Generate event-driven data flow processing logic based on the semantic model, including: determining the semantic objects and logical units mapped by the semantic model in the target system, constructing a process model based on the semantic model, the semantic objects and the logical units, and automatically generating the logic code or runtime process to be executed based on the process model through a code generation model. Deploying the event-driven data stream processing logic includes: sequentially deploying the event-driven data stream processing logic according to the order of domain shared template, customized configuration, and runtime instance configuration, and under the constraints of set arbitration rules. The domain shared template corresponds to a configuration file in the form of a shared configuration, and the customized configuration and the runtime instance configuration correspond to configuration files in the form of a specific configuration. The arbitration rules include set security policies. When a specified event corresponding to the event-driven data stream processing logic is detected, the processing flow corresponding to the specified event is executed.

2. The method for automatically generating event-driven data streams based on configuration files as described in claim 1, characterized in that: The configuration file includes the following configuration contents: events, conditions, operation steps, flow control, context and parameters.

3. The method for automatically generating event-driven data streams based on configuration files as described in claim 1, characterized in that, Also includes: After obtaining the configuration file, its validity is verified.

4. The method for automatically generating event-driven data streams based on configuration files as described in claim 1, characterized in that: Deploying the event-driven data stream processing logic includes registering event listeners through a service discovery mechanism.

5. The automatic generation method for event-driven data streams based on configuration files as described in any one of claims 1 to 4, characterized in that: After deploying the event-driven data stream processing logic, when the configuration file is detected to be updated, the event-driven data stream processing logic is redeployed according to the configuration file.

6. A system for implementing the configuration file-based event-driven automatic data stream generation method according to any one of claims 1 to 5, characterized in that, include: The system includes a configuration parsing module, an operation semantics generation module, an event registration and deployment module, and an event execution module. The configuration parsing module is connected to the operation semantics generation module, the operation semantics generation module is connected to the event registration and deployment module, and the event registration and deployment module is connected to the event execution module. The configuration parsing module is used to parse the obtained configuration file to obtain the corresponding semantic model; The operation semantic generation module is used to generate the event-driven data stream processing logic based on the semantic model. The event registration and deployment module is used to deploy the event-driven data stream processing logic, including: deploying the event-driven data stream processing logic by combining the priority order of platform core configuration, domain shared template, customized configuration, runtime instance configuration, and set arbitration rules; The event execution module is used to listen for the triggering of the specified event corresponding to the event-driven data stream processing logic and execute the processing flow corresponding to the specified event.

7. A computer program product comprising computer instructions, characterized in that: When the computer instructions are executed by the processor, they implement the configuration file-based event-driven data stream automatic generation method according to any one of claims 1 to 5.

Images