A method for arranging and fusion generation of digital objects based on digital network

Abstract

The present application provides an orchestration fusion generation method based on digital objects in a digital network, which relates to the technical field of digital objects. The method comprises: in a list interface of an orchestration fusion task process, after receiving a signal sent by an execution button of the orchestration fusion task process, reading the orchestration fusion execution script of the orchestration fusion task process from a database to generate an orchestration fusion execution instance of a digital object; through an execution engine, according to the order in a scheduling stack table in the digital object orchestration fusion execution instance, calling the data and functions of the digital objects bound to each data node, each operation node, and each process control node in the digital object orchestration fusion execution instance to generate a digital object with new data or new capabilities, thereby generating a digital object with new data or new capabilities by calling the function of each node and utilizing existing digital objects, thereby improving the availability of digital objects and the efficiency and flexibility of data processing.

Description

Technical Field

[0001] The present application relates to the technical field of digital objects, and in particular to a method for generating arrangement and fusion of digital objects based on the Internet of Things. Background Art

[0002] A digital object is an abstraction of data resources on the digital internet. Through data abstraction and formatting, heterogeneous data resources can be identified, transmitted, shared, and processed in a unified manner. A digital object primarily consists of three parts: a digital object identifier (DOI), metadata, and a data entity. The DOI uniquely identifies the digital object, enabling unique identification and access across the global network. Metadata represents the multidimensional characteristics of the digital object, describing its business characteristics within the business domain and facilitating its retrieval, discovery, and identification within the digital internet. A data entity represents and carries heterogeneous data, which can be structured or unstructured, facilitating data sharing and processing on the digital internet. Together, these three components constitute the core data of a digital object.

[0003] In the current digital internet, digital objects are widely distributed and diverse. Based on the type of metadata, digital objects can be broadly categorized into three different types: SQL, file, and interface. Many business scenarios require the sequential invocation of multiple digital objects within a single task flow, with necessary conversions performed on the digital objects during this process. When multiple digital objects need to be converted (e.g., joined), the current technical solution is to first obtain multiple digital objects and then write a corresponding processing program for each digital object's specific structure to ensure compatibility and conversion (e.g., joining) with other digital objects. This process requires digital object operators to not only be familiar with the specific business domain but also possess certain programming skills. If a ready-made component with the ability to convert specific data structures (e.g., join) were available, the conversion functionality provided by the component could be directly used, significantly simplifying operations and eliminating tedious programming steps.

[0004] According to the current research field of digital objects in the Internet of Things, there are several problems:

[0005] 1. Digital objects have poor reusability and lack pre-built components for complex processing. Existing technical solutions only allow for simple modification of individual digital objects. They cannot directly reuse the data or functionality of one digital object within another. They also lack pre-built components for complex processing of single or multiple digital objects.

[0006] 2. User operations are complex and lack support for visual components. In the field of digital networking, when operating multiple digital objects simultaneously, there is a lack of visual interfaces and draggable components (data components, calculation components, and process control components). Summary of the Invention

[0007] In view of this, an embodiment of the present application provides an arrangement fusion generation method based on digital objects in the Internet of Things, so as to overcome the above problems or at least partially solve the above problems.

[0008] A first aspect of an embodiment of the present application provides a method for generating an arrangement and fusion of digital objects based on a digital network, the method comprising:

[0009] On the list interface of the orchestration fusion task flow, after receiving the signal sent by the execution button of the orchestration fusion task flow, the orchestration fusion execution script of the orchestration fusion task flow is read from the database to generate a digital object orchestration fusion execution instance;

[0010] By means of an execution engine, data and functions of a digital object bound to each data node, functions of each operation node, and functions of each process control node in the digital object orchestration fusion execution instance are called according to the order in the scheduling stack table in the digital object orchestration fusion execution instance to generate a digital object with new data or new capabilities;

[0011] Among them, the orchestration fusion task process is generated by an orchestration fusion flowchart obtained by connecting multiple pre-built components. The pre-built components are divided into data resource components, computing components and process control components. The data resource components include data nodes for accessing and managing data in digital objects; the computing components include operation nodes for processing and converting data in digital objects; the process control components include process control nodes for defining the logical structure of the orchestration process.

[0012] Optionally, before receiving the signal sent by the execution button of the orchestration fusion task process, the process further includes configuring multiple data resource components according to the following steps:

[0013] According to the business requirements of the digital object generation, multiple data resource components are added to the orchestration and fusion process canvas, and the node name and node description of the data node filled in the property interface of the data node of each data resource component are obtained;

[0014] For each data node, a digital object related to the digital object generation business requirement is bound to the corresponding data node from the digital object list of the digital network system, and the data type of the bound digital object is obtained in the property interface.

[0015] Optionally, before receiving a signal from an execution button of the orchestration fusion task process, the process further includes configuring multiple computing components of different types according to the following steps:

[0016] Generate business requirements based on digital objects and add multiple different types of computing components to the orchestration and fusion process canvas;

[0017] For each operation node, when the computing component is a word segmentation component in an unstructured computing component, obtaining a node name and a node description of the operation node filled in a property interface of the operation node of the word segmentation component; the operation node of the word segmentation component is used to perform a word segmentation operation on data in a digital object whose data type is unstructured data;

[0018] For each operation node, when the computing component is a joint component in a structured computing component, obtaining the node name and the node description of the operation node filled in the property interface of the operation node of the joint component; the operation node of the joint component is used to perform a joint operation on data in two digital objects whose data type is structured data;

[0019] For each operation node, when the computing component is a filtering component in a structured computing component, obtaining the node name and node description of the operation node filled in the property interface of the operation node of the filtering component, as well as the filtering condition expression of the operation node, wherein the operation node of the filtering component is used to filter data in a digital object whose data type is structured data according to the filtering condition expression;

[0020] For each operation node, when the computing component is a deduplication component in a structured computing component, obtaining the node name and node description of the operation node filled in the property interface of the operation node of the deduplication component, as well as the filtering condition expression of the operation node, wherein the operation node of the deduplication component is used to delete duplicate data in data in a digital object whose data type is structured data;

[0021] For each operation node, when the calculation component is a sorting component in a structured calculation component, obtaining the node name and node description of the operation node filled in the property interface of the operation node of the sorting component, as well as the sorting field expression of the operation node, the operation node of the sorting component being used to perform ascending or descending order on the data in the digital object whose data type is structured data according to the sorting field expression;

[0022] For each operation node, when the computing component is a word segmentation statistics component in a hybrid computing component, obtain the node name of the operation node and the node description of the operation node filled in the property interface of the operation node of the word segmentation statistics component. The operation node of the word segmentation statistics component is used to calculate the frequency of occurrence of words in the data of a digital object whose data type is structured data after word segmentation in unstructured data.

[0023] Optionally, before receiving a signal from an execution button of the orchestration fusion task process, the process further includes configuring multiple computing components of different types according to the following steps:

[0024] For each operation node, when the computing component is a connection component in a structured computing component, obtaining the node name and node description of the operation node filled in the property interface of the operation node of the connection component, as well as the connection field expression of the operation node; the operation node of the connection component is used to connect the data in two digital objects whose data type is structured data according to the specified fields in the connection field expression;

[0025] Wherein, the connection component includes a left connection component, a right connection component and an inner connection component;

[0026] The operation node of the left join component is used to left join the data in two digital objects whose data type is structured data according to the specified field;

[0027] The operation node of the right connection component is used to right connect the data in two digital objects whose data type is structured data according to the specified field;

[0028] The operation node of the inner connection component is used to perform inner connection on the data in two digital objects whose data types are structured data according to the specified fields.

[0029] Optionally, after configuring multiple data resource components and multiple different types of computing components, the process further includes configuring a data encapsulation component according to the following steps:

[0030] Generate business requirements based on digital objects and add data encapsulation components in the data component to the orchestration and fusion process canvas;

[0031] For the encapsulation node in the data encapsulation component, obtaining attribute information of the encapsulation node input by the user in the attribute page of the encapsulation node;

[0032] Among them, the attribute information of the encapsulated node includes: node name, node description, and attribute information of the digital object with new data or new functions. The attribute information of the digital object with new data or new functions includes: data asset name, digital object unique identifier, business category, keyword, format type, data format, publisher, data publishing subject, and data resource description.

[0033] Optionally, before adding pre-built components to the orchestration fusion process canvas, also include:

[0034] Setting up pre-built components;

[0035] A visual orchestration and fusion process canvas is created, where the orchestration and fusion process canvas is used to display pre-built components that can be dragged and a blank area for performing orchestration and fusion process operations.

[0036] Optionally, before receiving the signal sent by the execution button of the orchestration fusion task process, the process control component is configured according to the following steps:

[0037] Generate business requirements based on digital objects and add process control components to the orchestration and fusion process canvas;

[0038] For a process control node in the process control component, obtaining attribute information of the process control node input by a user in an attribute page of the process control node;

[0039] Among them, the attribute information of the process control node includes: node name, node description; the process control node is used to control the logic of the orchestration fusion task process; the node type of the process control node includes: conditional branch, parallel branch and process end.

[0040] Optionally, the method further includes:

[0041] Establishing a connection relationship between the data node and the operation node based on the digital object generation business requirement and the in-degree requirement of the operation node, and establishing a connection relationship between the process control node and the data node based on the digital object generation business requirement and the logical control requirement of the process control node; the connection relationship is used to represent the flow direction and processing order of data in the digital object bound to the data node;

[0042] Output the orchestration fusion flow chart corresponding to the orchestration fusion task process according to the connection relationship, and generate an orchestration fusion execution script based on the orchestration fusion flow chart and save it in the database;

[0043] When the in-degree of the operation node is a data node, it is determined that the data nodes connected to the operation node can only run serially;

[0044] When the in-degree of the operation node is two or more data nodes, it is determined that the data nodes connected to the operation node can run in series and / or in parallel.

[0045] Optionally, after outputting the orchestration fusion flow chart corresponding to the orchestration fusion task process according to the connection relationship, the method further includes:

[0046] Use multiple proofreading rules to verify the legitimacy of the orchestration fusion flow chart. The proofreading rules include, but are not limited to: whether it is a directed acyclic graph, whether the data node output is correctly connected to the computing component, whether the name identifier of each node is unique, whether it contains the necessary components of the orchestration fusion process, and whether each node contains its required attribute values;

[0047] The verified orchestration fusion flowchart is converted into an orchestration fusion execution script described in a recognizable language and word order and saved in the database.

[0048] Optionally, calling data and functions in a digital object bound to each data node, a function of each operation node, and a function of each process control node in the digital object orchestration fusion execution instance according to an order in a scheduling stack table in the digital object orchestration fusion execution instance to generate a digital object with new data or new capabilities includes:

[0049] According to the scheduling stack table in the digital object orchestration fusion execution instance, the digital object orchestration fusion execution instance is sequentially executed, and corresponding computing models are called for serial type, parallel type, and conditional type data nodes to obtain the digital object with new data or new capabilities;

[0050] Among them, the conditional type data node is a data node connected to the process control node whose node type is a conditional branch, indicating that the data node needs to determine whether the condition of the process control node of the conditional branch is met before executing the next step; the parallel type data node is a data node connected to the process control node whose node type is a parallel branch, indicating that the data node needs to simultaneously execute data processing of the operation nodes of multiple computing components connected to the parallel branch process control node.

[0051] Beneficial effects of this application:

[0052] An embodiment of the present application provides a method for generating orchestration fusion based on digital objects in a digital network. In the list interface of the orchestration fusion task process, after receiving a signal from an execution button of the orchestration fusion task process, the orchestration fusion execution script of the orchestration fusion task process is read from a database to generate a digital object orchestration fusion execution instance; through an execution engine, according to the order in the scheduling stack table in the digital object orchestration fusion execution instance, the data and functions of the digital objects bound to each data node, the functions of each operation node and the functions of each process control node in the digital object orchestration fusion execution instance are called to generate a digital object with new data or new capabilities; the orchestration fusion task process is generated by an orchestration fusion flow chart obtained by connecting multiple pre-built components, and the pre-built components are divided into a data resource component, a computing component and a process control component. The data resource component includes a data node for accessing and managing data in the digital object; the computing component includes an operation node for processing and converting data in the digital object; and the process control component includes a process control node for defining the logical structure of the orchestration process. Thus, by calling the functions of each node and utilizing existing digital objects, digital objects with new data or new functions are generated, thereby improving the availability of digital objects and the efficiency and flexibility of data processing. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] The drawings that constitute a part of this application are used to provide further understanding of this application. The illustrative embodiments of this application and their descriptions are used to explain this application and do not constitute improper limitations on this application.

[0054] In order to more clearly illustrate the technical solution of the present application, the following is a brief introduction to the drawings required for the description of the present application. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0055] Figure 1 This is a flowchart of a method for generating an arrangement and fusion of digital objects based on a digital network, provided by an embodiment of the present application;

[0056] Figure 2 This is an overall flow chart of a method for arranging and fusion generation based on digital objects in the Internet of Things provided by an embodiment of the present application;

[0057] Figure 3 This is a flowchart of a data node attribute information configuration process provided by an embodiment of the present application;

[0058] Figure 4 is a flowchart of a configuration process of an operating node of a computing component of a respective type provided by an embodiment of the present application;

[0059] Figure 5 This is a flowchart of a configuration process of a data encapsulation component provided by an embodiment of the present application;

[0060] Figure 6 This is a schematic diagram of a process for executing an orchestration fusion task provided by an embodiment of the present application;

[0061] Figure 7 This is a schematic diagram of the framework of a device for generating arrangement and fusion of digital objects based on the Internet of Things, provided in one embodiment of the present application. DETAILED DESCRIPTION

[0062] It should be noted that, unless there is any conflict, the embodiments and features in the embodiments of this application can be combined with each other.

[0063] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0064] The Internet of Data (IOD) is a virtual data network based on the Internet. Through open software architecture and standardized protocols, it efficiently connects various data platforms and systems, supports the interconnection, interoperability and multi-domain data sharing of heterogeneous, heterogeneous and heterogeneous data, and forms a data space with "data interconnection, on-demand scheduling, intra-domain autonomy and inter-domain collaboration".

[0065] Digital Object (DO) is a data structure that abstractly describes data resources and organizes and records data in a computer system according to basic elements such as identification, metadata, and data entities.

[0066] Low-code: Low-code is a software development approach that allows developers to quickly build applications using pre-built components and visual tools without having to write extensive code. Low-code platforms enable users or developers to combine these components through a drag-and-drop interface or simple configuration to quickly develop the required applications.

[0067] Digital object encapsulation: Digital object encapsulation is an operation that refers to the encapsulation of multiple heterogeneous data sources outside the Internet (MySQL, DB2, NoSQL, Stream, HDFS, S3, Azure, NFS, API, FTP, etc.), and the generation of digital objects from structured or unstructured data within the heterogeneous data source domain according to digital object specifications.

[0068] This application is to arrange and fuse digital objects in the digital network to generate new digital objects to solve the technical problems mentioned above.

[0069] Digital object orchestration fusion is a process orchestration method that integrates and coordinates the data and capabilities of multiple digital objects in the Internet of Things, and ultimately generates digital objects with new data or capabilities.

[0070] Specifically, it provides a visual, drag-and-drop process orchestration interface and multiple types of pre-built components: data components that can bind data objects (such as data resources and data encapsulation); computing components that support operations on digital objects of different data types (such as union, connection, filtering, sorting, etc.); and process control components that control the orchestration process (such as conditions, branches, and ends).

[0071] On the process orchestration interface, you can execute the corresponding data components, computing components, and control components according to the orchestration operations in serial, parallel, and branching structures, executing the digital object orchestration and fusion task process. Upon completion, a digital object with the target capabilities is generated. During the digital object orchestration and fusion process, the data and capabilities of multiple digital objects need to be combined, orchestrated, and scheduled to complete the orchestration and fusion task process.

[0072] The technical solution of this application will be described in detail below through multiple embodiments.

[0073] Figure 1 This is a flow chart of a method for generating an arrangement and fusion of digital objects based on a digital network provided by an embodiment of the present application. Figure 1 An embodiment of the present application provides a method for generating an arrangement and fusion of digital objects based on a digital network, the method comprising:

[0074] Step S1, in the list interface of the orchestration fusion task flow, after receiving the signal sent by the execution button of the orchestration fusion task flow, the orchestration fusion execution script of the orchestration fusion task flow is read from the database to generate a digital object orchestration fusion execution instance.

[0075] In this embodiment, in this embodiment, first enter the interface of the orchestration and fusion task process, receive the signal that the user clicks the execution button of the orchestration and fusion task process, and then read the orchestration and fusion execution script corresponding to the orchestration and fusion task process from the database. The orchestration and fusion task process is generated by connecting a variety of pre-built components to obtain an orchestration and fusion flowchart, which is used for the generation process of digital objects. The orchestration and fusion execution script is generated based on the orchestration and fusion task process designed by the user in the orchestration and fusion process canvas, and contains the configuration information of all data nodes, operation nodes and process control nodes, as well as the connection relationship and execution order between each node. By parsing the script, it is converted into a specific digital object orchestration and fusion execution instance. The digital object orchestration and fusion execution instance describes in detail the function of each node, the input and output relationship and the execution logic of the entire process, and provides guidance for subsequent task execution.

[0076] Step S2: Through the execution engine, according to the order in the scheduling stack table in the digital object orchestration fusion execution instance, the data and functions in the digital object bound to each data node, the functions of each operation node, and the functions of each process control node in the digital object orchestration fusion execution instance are called to generate a digital object with new data or new capabilities.

[0077] Among them, the orchestration fusion task process is generated by an orchestration fusion flowchart obtained by connecting multiple pre-built components. The pre-built components are divided into data resource components, computing components and process control components. In addition, it also includes a data encapsulation component. The data resource component contains data nodes for accessing and managing data in digital objects; the computing component contains operation nodes for processing and converting data in digital objects; the process control component contains process control nodes for defining the logical structure of the orchestration process.

[0078] The step S2 of "calling the data and functions of the digital object bound to each data node, the function of each operation node, and the function of each process control node in the digital object orchestration fusion execution instance according to the order in the scheduling stack table in the digital object orchestration fusion execution instance to generate a digital object with new data or new capabilities" specifically includes:

[0079] According to the scheduling stack table in the digital object orchestration fusion execution instance, the digital object orchestration fusion execution instance is sequentially executed, and corresponding computing models are called for serial type, parallel type, and conditional type data nodes to obtain the digital object with new data or new capabilities;

[0080] Among them, the conditional type data node is a data node connected to the process control node whose node type is a conditional branch, indicating that the data node needs to determine whether the condition of the process control node of the conditional branch is met before executing the next step; the parallel type data node is a data node connected to the process control node whose node type is a parallel branch, indicating that the data node needs to simultaneously execute data processing of the operation nodes of multiple computing components connected to the parallel branch process control node.

[0081] In this embodiment, during the execution process, the execution engine will execute the orchestration fusion task process in accordance with the predetermined order according to the scheduling stack table in the digital object orchestration fusion execution instance. The scheduling stack table is a planned sequence table for task execution, which records the execution order and dependency relationship of the orchestration fusion task process. The execution engine can call the function of each node in the orchestration fusion task process in sequence according to the information in the scheduling stack table, wherein the data resource component is used to access and manage the data in the digital object, the computing component is used to process and convert the data in the digital object in the data resource component, and the process control component is used to define the logical structure of the orchestration fusion task process. At the same time, in this process, the corresponding computing model can be called for different types of nodes to drive the access to digital objects and computing components. The three components collaborate with each other to utilize the functions of existing digital objects and components to generate digital objects with new data or new capabilities.

[0082] The following is a detailed description of the preparation process before the execution of the orchestration fusion task flow.

[0083] Figure 2 This is an overall flow chart of another method for generating arrangement and fusion of digital objects based on the Internet of Things provided by an embodiment of the present application. Figure 2 An embodiment of the present application provides a method for generating an arrangement and fusion of digital objects based on the Internet of Things, the method comprising steps S11 to S18:

[0084] Step S11, setting pre-built components, the pre-built components are divided into: data components, calculation components, process control components, the data components are divided into data resource components and data encapsulation components.

[0085] In this embodiment, reference Figure 2 ,In order to execute the subsequent orchestration and fusion process, it is necessary to pre-set the ,necessary tools and resources before adding the pre-built components to the ,orchestration and fusion process canvas. Based on this, the basic components for realizing ,the orchestration and fusion of digital objects will be pre-built, i.e. the pre-built components will be ,obtained. The pre-built components will be added to the database corresponding to the ,orchestration and fusion service of the enterprise-level server.

[0086] Among them, pre-built components are divided into three categories, namely data components, computing components, and process control components. Data components are further divided into two categories: data resource components and data encapsulation components.

[0087] Specifically, the data component is used to access and manage data in digital objects. The data resource component is used to bind specific, existing digital objects, such as database tables, files, and APIs, making it easier for users to integrate data sources into the orchestration process. The data encapsulation component encapsulates data processed by the orchestration and fusion process into new digital objects for sharing and use within the digital network.

[0088] The computing component is used to process and transform the data in digital objects, such as operations such as union, filtering, sorting, and word segmentation, to provide rich data processing capabilities to meet the business needs of different digital object generation.

[0089] The process control component is used to define the logical structure of the orchestration process, such as conditional branches, parallel processing, process termination, etc., to ensure that the orchestration fusion process can be executed in a predetermined logical order.

[0090] Pre-built components provide a standardized tool set that facilitates direct calls for each subsequent digital object generation business without the need to develop complex processing programs from scratch.

[0091] Step S12: creating a visual orchestration and fusion process canvas, wherein the orchestration and fusion process canvas is used to display pre-built components that can be dragged and a blank area for performing orchestration and fusion process operations.

[0092] In this embodiment, the orchestration fusion process canvas is a visual interface for displaying pre-built components and providing a blank area for users to use pre-built components and existing digital objects for orchestration operations. In this process, the orchestration fusion process canvas is presented to the user in the form of a panel. The user can place pre-built components on the canvas by dragging and dropping, and configure the connection relationship and attribute information between each pre-built component.

[0093] Step S13, based on the business requirements of digital object generation, multiple data resource components are added to the orchestration fusion process canvas, and the attribute information of the data nodes in the data resource components is configured; the attribute information of the data nodes includes at least: the identifier of the bound digital object and the data type of the bound digital object.

[0094] In this embodiment, based on the business requirements for digital object generation, multiple data resource components are added to the orchestration and fusion process canvas, and the attribute information of each data node needs to be configured. Each data resource component corresponds to a data node, and each data node is used to bind an existing digital object.

[0095] By configuring data nodes, problems such as access and management of digital objects are solved, making it easier for users to flexibly introduce various heterogeneous data.

[0096] Step S14 , generating business requirements based on the digital object, adding multiple different types of computing components to the orchestration fusion process canvas, and configuring attribute information of the operation nodes in the computing components.

[0097] In this embodiment, based on the business requirements for digital object generation, multiple different types of computing components are added to the orchestration and fusion process canvas, and the attribute information of the operation nodes is configured. The computing components provide a rich set of data processing functions. Each computing component corresponds to an operation node, which processes the data of the digital objects bound to one or more data nodes connected to it.

[0098] Step S15 , generating business requirements based on the digital object, adding multiple different types of process control components to the orchestration fusion process canvas, and configuring attribute information of the process control nodes in the process control components.

[0099] In this embodiment, the user adds a process control component to the orchestration fusion process canvas and configures the attribute information of the process control node. The process control node of the process control component is used to define the logical structure of the orchestration fusion task process.

[0100] There are three types of process control nodes:

[0101] Conditional branching: Used to determine the direction of each part of the orchestration and fusion task process based on conditions, such as "When the data node output by a computing component meets condition A, execute operation B; otherwise, execute operation C."

[0102] Parallel branch: used to support multiple data nodes or operation nodes running simultaneously to improve processing efficiency.

[0103] Process End: Used to mark the end of the orchestration fusion task process.

[0104] For example:

[0105] Assume that the user needs to select different processing paths based on the data volume. When the data volume is large, data filtering is performed first, and then subsequent data processing is executed. When the data volume is small, no filtering is required and subsequent data processing is executed directly. Therefore, a process control node with a conditional branch can be added and the configuration condition is "data volume > 1000". If the condition is met, data filtering is performed first, and then subsequent data processing is executed. If not, no filtering is required and subsequent data processing is executed directly.

[0106] Step S16: Add a data encapsulation component to the orchestration fusion process canvas according to the digital object generation business requirements, and configure the attribute information of the encapsulation node in the data encapsulation component.

[0107] In this embodiment, the function of the encapsulation node is to encapsulate the processed data into a new digital object for sharing and use in the digital network. The configured attribute information includes: the digital object identifier (DOID), metadata and data entity of the encapsulated new digital object.

[0108] The digital object identifier is the globally unique identifier of the new digital object obtained after encapsulation. Metadata describes the characteristics of the new digital object obtained after encapsulation, such as data source, data type, business domain, etc. The data entity is the actual data content contained in the new digital object obtained after encapsulation.

[0109] It should be noted that in the process of adding various pre-built components, the data resource component, the calculation component, and the process control component other than the process end type are added first. There is no special restriction on the order of adding these three. Then, the connection relationship between the three is created. Finally, the data encapsulation component and the process control component of the process end type are added.

[0110] Step S17: Establish a connection relationship between the data node and the operation node based on the business requirements of the digital object generation and the in-degree requirements of the operation node, and establish a connection relationship between the process control node and the data node based on the business requirements of the digital object generation and the logical control requirements of the process control node; the connection relationship is used to represent the flow direction and processing order of the data in the digital object bound to the data node.

[0111] According to the connection relationship, an orchestration fusion flowchart corresponding to the orchestration fusion task process is output, and an orchestration fusion execution script is generated based on the orchestration fusion flowchart and saved in a database.

[0112] In this embodiment, based on the business requirements for digital object generation and the in-degree requirements of the operation nodes, the user establishes a connection relationship between the data nodes and the operation nodes. The connection relationship defines the flow direction and processing order of the data.

[0113] For example, if the in-degree of an operation node is 1, the data nodes connected to the operation node can only run serially. If the in-degree of an operation node is 2, the two data nodes connected to the operation node can run in parallel.

[0114] Assume that the user's business requirement for digital object generation is to first filter sales data and then combine it with inventory data:

[0115] Based on the above requirements, the orchestration rules are as follows: the data node bound to the sales data is connected separately to the operation node of the filtering component, and then the data node bound to the filtered sales data connected to the output side of the operation node of the filtering component is connected to the operation node of the joint component. At this time, the input side of the operation node of the joint component is connected to two data nodes, namely the data node bound to the filtered sales data and the data node bound to the inventory data. The output side of the operation node of the joint component is the new data that is ultimately required, which is encapsulated into a new digital object through the new data.

[0116] At the same time, it is also necessary to generate business requirements based on digital objects and establish a connection relationship between process control nodes and data nodes. For example, when a data node needs to execute different branch processing based on the size of the data of the bound digital object, it is necessary to connect a process control node for conditional judgment between the data node and the operation node of the computing component (that is, the process control node of the conditional branch mentioned later).

[0117] And, reference Figure 2 After each configuration of the connection relationship between data nodes and operation nodes and the connection relationship between process control nodes and data nodes, it is necessary to determine whether the orchestration needs to continue. If necessary, repeat the above steps. If not, add the process control component with the node type of process end to the orchestration fusion process canvas, and configure the attribute information of the process control node in the process control component with the node type of process end. Then, output the orchestration fusion flow chart, and convert the orchestration fusion flow chart into an orchestration fusion execution script to obtain the orchestration fusion task process.

[0118] In this embodiment, after completing the design of the orchestration and connection of various pre-built components in the orchestration and fusion flow chart corresponding to the orchestration and fusion task process, the orchestration and fusion flow chart is output and converted into an orchestration and fusion execution script. The orchestration and fusion execution script is a description in a recognizable language and word order, which is used for the subsequent execution of the orchestration and fusion task process, ensuring that the orchestration and fusion task process can be correctly parsed and executed.

[0119] Step S18: calling the data and functions in the digital object bound to each data node, the functions of each operation node, the functions of each process control node, and the functions of the encapsulated components to generate a digital object with new data or new functions.

[0120] In this embodiment, during the execution process, the data and functions in each data node, as well as the functions of each operation node, each process control node and the encapsulation component will be called in the order set by the orchestration and fusion task process, and finally a digital object with new data or new functions will be generated.

[0121] The technical solutions of the above-mentioned embodiments, through the provision of different types of pre-built components, provide a standardized and modular operational foundation for the orchestration and fusion of digital objects in the Internet of Things. By creating a visual orchestration and fusion process canvas, users can intuitively add and configure data resource components, computing components, and process control components by dragging and dropping. They can also flexibly establish connections between data nodes, operation nodes, and process control nodes based on the business needs of digital object generation, thereby efficiently defining the flow of data and the order of processing, solving the current problem of poor reuse of digital objects.

[0122] Furthermore, this visual interface significantly reduces the need for programming skills, enabling even non-professional developers to quickly master and complete complex digital object orchestration tasks. Furthermore, by converting orchestration fusion flowcharts into scripts and executing the task flow, digital objects with new data or functionality are ultimately generated, improving data processing efficiency and flexibility, and enhancing the processing capabilities and application value of digital objects in the Internet of Things.

[0123] Figure 3 This is a flowchart of the data node attribute information configuration process provided by an embodiment of the present application. In combination with the above embodiment, an embodiment of the present application also provides another orchestration fusion generation method based on digital objects in the Internet of Things. In this method, the attribute information of the data node includes: the node name of the data node, the node description, the identifier of the bound digital object, and the data type of the bound digital object; before executing the "receiving the signal sent by the execution button of the orchestration fusion task process" in step S2, it also includes configuring multiple data resource components according to the following steps, specifically including step S2-1-1 and step S2-1-2.

[0124] Step S2-1-1, based on the business requirements of the digital object generation, multiple data resource components are added to the orchestration fusion process canvas, and the node name and node description of the data node filled in the attribute interface of the data node of each data resource component are obtained.

[0125] In this embodiment, reference Figure 3 , you can drag and drop data components of the data resource type (i.e., data resource components) to the panel, select the data node of the data resource component, and when importing the data node, obtain the node name and node description entered by the user in the data node's property page as the attribute information of the data node.

[0126] The node name is a unique identifier assigned by the user to the data node, used to quickly identify and reference the node in orchestration and fusion task flows. The node description briefly explains the data node's function or data source, helping users better understand and manage the role of each node in complex processes.

[0127] For example, a data node can be named "Sales Data Input" and described as "Read sales data from MySQL database". In this way, in subsequent operations, users can clearly understand the function of the node and the data source.

[0128] Step S2-1-2: for each data node, bind the digital object related to the digital object generation business requirement to the corresponding data node from the digital object list of the digital network system, and obtain the data type of the bound digital object in the attribute interface.

[0129] In this embodiment, after obtaining the node name and node description of the data node, a digital object related to the digital object generation business requirements is selected from the existing digital object list of the digital network system and bound to the data node. The data object can be presented in the form of a drop-down box list to bind to the data node imported in the above steps. After binding the digital object, the data type of the digital object is selected in the property interface of the data node.

[0130] Specifically, the binding process involves associating the unique identifier (DOI) of a digital object with a data node and recording the data type of the digital object (such as structured data or unstructured data), ensuring that the data node can accurately access and operate the specified digital object.

[0131] For example, if a user needs to process a sales data table stored in a MySQL database, he or she will find the corresponding digital object from the Internet of Things, bind its DOI to the data node, and mark it as a "structured data" type.

[0132] Through the technical solution of the above embodiment, by obtaining the node name and node description input by the user, a clear identification and functional description is provided for each data node, which improves the readability and manageability of the orchestration and fusion process and reduces the possibility of user errors in complex processes. Secondly, by selecting and binding relevant digital objects and their data types from the digital network system, it ensures that the data nodes can accurately access and operate the required digital objects, while providing the necessary data type information for subsequent computing component operations, thereby improving the efficiency of data processing and enabling users to quickly configure and adjust the orchestration and fusion task process according to different digital object generation business needs.

[0133] refer to Figure 4 , Figure 4 This is a flowchart of the configuration process of the operation nodes of the computing components of different types provided by an embodiment of the present application. In combination with the above embodiment, an embodiment of the present application also provides another method for generating an orchestration fusion based on a digital object of the Internet of Things. In this method, the computing components are divided into: unstructured computing components, structured computing components, and hybrid computing components; before "receiving the signal sent by the execution button of the orchestration fusion task flow" in step S2, it also includes configuring multiple computing components of different types according to the following steps, specifically including steps S2-2-1 to S2-2-7:

[0134] Step S2-2-1, generating business requirements based on digital objects, and adding multiple different types of computing components to the orchestration and fusion process canvas;

[0135] In this embodiment, in order to facilitate the processing of digital objects of different data types, different types of computing components are designed. Each component provides specific operation functions for different types of data objects. When a computing component needs to be inserted, it can be added to the orchestration fusion process canvas by dragging and dropping.

[0136] Computing components include three types: unstructured, structured, and hybrid. Unstructured components include word segmentation components, while structured components include left-join, right-join, inner-join, join, selection, filtering, deduplication, and sorting. Hybrid components include word segmentation statistics.

[0137] Step S2-2-2, for each operation node, when the computing component is a word segmentation component in an unstructured computing component, obtain the node name of the operation node and the node description of the operation node filled in the property interface of the operation node of the word segmentation component; the operation node of the word segmentation component is used to perform word segmentation operations on data in digital objects whose data type is unstructured data.

[0138] In this embodiment, when the computing component is a word segmentation component within an unstructured computing component, the node name and node description entered by the user in the property interface of the word segmentation component operation node are obtained. The word segmentation component operation node is specifically used to perform word segmentation operations on unstructured data (such as text data).

[0139] For example, a user can name an operation node "User Review Segmentation" and describe it as "Perform word segmentation processing on user review text" to facilitate subsequent analysis of keywords and other information in user reviews.

[0140] Step S2-2-3, for each operation node, when the computing component is a joint component in a structured computing component, obtain the node name of the operation node and the node description of the operation node filled in the property interface of the operation node of the joint component; the operation node of the joint component is used to perform joint operations on data in two digital objects whose data type is structured data.

[0141] In this embodiment, when the computing component is a joint component in a structured computing component, the node name and node description filled in by the user in the property interface of the operation node of the joint component are obtained.

[0142] For example, when a user needs to merge multiple sales data from different time periods, the node name of the operation node is set to "sales data union", the node description is set to "union of sales data from different time periods", and the input side of the operation node is connected to two data nodes to merge the data of the digital objects corresponding to the two data nodes (multiple sales data from different time periods) into a complete data (including sales data from multiple time periods).

[0143] Step S2-2-4, for each operation node, when the computing component is a filtering component in a structured computing component, obtain the node name of the operation node and the node description of the operation node filled in the property interface of the operation node of the filtering component, as well as the filtering condition expression of the operation node. The operation node of the filtering component is used to filter the data in the digital object whose data type is structured data according to the filtering condition expression.

[0144] In this embodiment, when the calculation component is a filter component within a structured calculation component, the node name, node description, and filter condition expression entered by the user in the property interface of the operation node of the filter component are obtained. The operation node of the filter component is used to filter digital objects of structured data according to the specified conditions.

[0145] When the data node connected to the input side of the operation node is numbered D3, and the data with the name Zhang San needs to be retrieved, the filter condition expression is where D3.name = "Zhang San".

[0146] For example, when a user needs to filter out orders with a purchase amount greater than 100 yuan from multiple orders, the user can name the operation node "High-value order filtering", describe the node as "Filter orders with a purchase amount greater than 100 yuan", and fill in "Purchase amount > 100" in the filter condition expression to extract data that meets this requirement.

[0147] Step S2-2-5, for each operation node, when the computing component is a deduplication component in a structured computing component, obtain the node name of the operation node and the node description of the operation node filled in the property interface of the operation node of the deduplication component, as well as the filtering condition expression of the operation node. The operation node of the deduplication component is used to delete duplicate data in the data of a digital object whose data type is structured data.

[0148] In this embodiment, the function of the deduplication component is to delete duplicate content in structured data and return only unique records. The input side of the operation node of the deduplication component is a data node, and the input is a digital object of a structured type.

[0149] Step S2-2-6, for each operation node, when the calculation component is a sorting component in a structured calculation component, obtain the node name of the operation node and the node description of the operation node filled in the property interface of the operation node of the sorting component, as well as the sorting field expression of the operation node. The operation node of the sorting component is used to ascend or descend the data in the digital object whose data type is structured data according to the sorting field expression.

[0150] In this embodiment, the sorting component is used to sort structured data in ascending (asc) or descending (desc) order. The input side of the operation node of the sorting component is a data node. The data type of the digital object of the data node is a structured type. When the data node is numbered D4 and the sorting field expression is age:desc, it means that the data in the digital object bound to the data node numbered D4 needs to be sorted in descending order according to age.

[0151] Step S2-2-7, for each operation node, when the computing component is a word segmentation statistics component in a hybrid computing component, obtain the node name of the operation node and the node description of the operation node filled in the property interface of the operation node of the word segmentation statistics component. The operation node of the word segmentation statistics component is used to calculate the frequency of occurrence of words in the data of a digital object whose data type is structured data after word segmentation in unstructured data.

[0152] In this embodiment, when the computing component is a word segmentation statistics component in a hybrid computing component, the node name and node description filled in by the user in the property interface of the operation node of the word segmentation statistics component are obtained. The input side of the operation node of the word segmentation statistics component includes two data nodes, one of which is bound to a digital object with a data type of structured data, and the other is bound to a digital object with a data type of unstructured data. The operation node of the word segmentation statistics component is used to count the frequency of occurrence of a certain structured data in the digital object bound to the data node connected to the input side after word segmentation in the unstructured data.

[0153] For example, the node name of the operation node of the word segmentation statistics component is "Frequency statistics of the keyword "good"", and the node description is "Count the frequency of occurrence of the keyword "good" in user reviews", thereby combining the frequency of occurrence of structured data (keyword "good") in unstructured data (user reviews) to provide richer information for subsequent user review analysis.

[0154] Through the detailed description of various types of computing components in the above embodiments, a clear distinction is made between unstructured computing components, structured computing components and hybrid computing components, and detailed configuration steps are provided for each component. This enables flexible processing of different types of data objects according to user needs, thereby providing more powerful support for complex data processing.

[0155] It should be noted that there is no necessary order relationship between steps S2-2-1 to S2-2-7.

[0156] In combination with the above embodiment, an embodiment of the present application further provides another method for generating orchestration fusion based on digital objects in the Internet of Things, wherein, before "receiving a signal from an execution button of an orchestration fusion task flow" in step S2, the method further includes configuring multiple different types of computing components according to the following steps, specifically including step S2-2-8:

[0157] In this method, the classification of connection components and the functions of their operation nodes are further refined. Connection components include left connection components, right connection components, and inner connection components. Each connection component provides a different connection operation method for digital objects of structured data.

[0158] In step S2-2-8, for each operation node, when the computing component is a connection component in a structured computing component, obtain the node name of the operation node and the node description of the operation node filled in the property interface of the operation node of the connection component, as well as the connection field expression of the operation node; the operation node of the connection component is used to connect the data in two digital objects whose data type is structured data according to the specified field in the connection field expression.

[0159] In this embodiment, when the computation component is a connection component within a structured computation component, the node name, node description, and connection field expression entered by the user in the properties interface of the operation node of the connection component are obtained. The input side of the operation node of the connection component can connect two data nodes, thereby performing a connection operation on two digital objects of structured data according to a specified field.

[0160] When the built-in numbers of two data nodes are D1 and D2, and the connection field expression indicates connecting the digital objects of the two data nodes through the field name name, the connection field expression is D1.name = D2.name;

[0161] For example, when users need to connect the sales data and inventory data of a product, they can set the node name of the operation node to "Connect Sales and Inventory", set the node description to "Connect sales data and inventory data according to product ID", and fill in "Sales data table.product_id = Inventory data table.product_id" in the connection field expression to achieve the association between sales data and inventory data.

[0162] The operation node of the left join component is used to left join the data in two digital objects whose data type is structured data according to the specified field.

[0163] For example, when it is necessary to left-join the data in the digital object bound to the data node numbered D5 and the data in the digital object bound to the data node numbered D6 based on the field name, the join field expression is: D5.name=D6.name.

[0164] The operation node of the right connection component is used to right connect the data in two digital objects whose data type is structured data according to the specified fields.

[0165] For example, when it is necessary to right-join the data in the digital object bound to the data node numbered D7 and the data in the digital object bound to the data node numbered D8 according to the field name, the join field expression is: D7.name=D8.name.

[0166] The operation node of the inner connection component is used to perform inner connection on the data in two digital objects whose data types are structured data according to the specified fields.

[0167] For example, when it is necessary to perform an inner join on the data in the digital object bound to the data node numbered D9 and the data in the digital object bound to the data node numbered D10 according to the field name, the join field expression is: D9.name=D10.name.

[0168] The introduction of left-connected components, right-connected components, and inner-connected components further enriches the functionality of the orchestration and fusion generation method based on digital objects in the Internet of Things. By combining these three connection components, users can flexibly design data processing flows based on different business needs, significantly improving the efficiency and flexibility of orchestration and fusion.

[0169] In combination with the above embodiments, an embodiment of the present application provides another method for generating orchestration fusion based on digital objects in the Internet of Things. In this method, before "receiving a signal from an execution button of an orchestration fusion task process" in step S2, the method further includes configuring a process control component according to the following steps, specifically including steps S2-3-1 to S2-3-2:

[0170] Step S2-3-1, generate business requirements based on digital objects and add process control components to the orchestration fusion process canvas.

[0171] In this embodiment, in order to facilitate the control of the logical structure of the orchestration and fusion task process, a process control component is designed. The process control component can provide different logical structure control functions for the orchestration and fusion task process. When a process control component needs to be inserted, the process control component can also be added to the orchestration and fusion process canvas by dragging and dropping.

[0172] Step S2-3-2: for a process control node in the process control component, obtaining attribute information of the process control node input by the user in the attribute page of the process control node;

[0173] Among them, the attribute information of the process control node includes: node name, node description; the process control node is used to control the logic of the orchestration fusion task process; the node type of the process control node includes: conditional branch, parallel branch and process end.

[0174] In this embodiment, the process control component includes a process control node, which is divided into conditional branch, parallel branch and process end. Corresponding to conditional control, parallel control and process end control, the process control node also needs to set attribute information. The attribute information includes the node name and node description of the process control node, wherein the node description is used to describe the node type and logical control of the process control node. For example, when the node type of the process control node is a conditional branch, for example, when the digital object generates a business requirement indicating that the data in the digital object in the data node needs to be adjusted to determine whether to filter and connect with other digital objects, the node description of the process control node can be to determine whether the amount of data in the digital object bound to the connected data node is greater than a preset threshold. If it is greater than the preset threshold, filtering is performed. At this time, the next step is executed through the operation node of the connected filtering component. If it is not greater than the preset threshold, it is directly connected to other digital objects.

[0175] refer to Figure 5 , Figure 5 This is a flowchart of the configuration process of the data encapsulation component provided by an embodiment of the present application. An embodiment of the present application provides another method for generating an orchestration fusion based on a digital object of a data network. In this method, after configuring multiple data resource components and multiple different types of computing components, the data encapsulation component is further configured according to the following steps, specifically including steps S2-4-1 to S2-4-2:

[0176] Step S2-4-1, generate business requirements based on digital objects, and add the data encapsulation component in the data component to the orchestration fusion process canvas.

[0177] In this embodiment, the data encapsulation component is used to encapsulate the newly generated data to obtain a new digital object. When the data encapsulation component needs to be inserted according to the business needs generated by the digital object, the data encapsulation component can be added to the orchestration fusion process canvas by dragging and dropping.

[0178] Step S2-4-2: for the encapsulation node in the data encapsulation component, obtain the attribute information of the encapsulation node input by the user in the attribute page of the encapsulation node.

[0179] Among them, the attribute information of the encapsulated node includes: node name, node description, and attribute information of the digital object with new data or new functions. The attribute information of the digital object with new data or new functions includes: data asset name, digital object unique identifier, business category, keyword, format type, data format, publisher, data publishing subject, and data resource description.

[0180] In this embodiment, the user can drag and drop data components of the data encapsulation type (i.e., data encapsulation components) to the panel. The data nodes on the data encapsulation components are encapsulation nodes. The node name of the encapsulation node specifies a global name for the encapsulation node, which is used to identify the node in the orchestration and fusion process. The node description is a brief description of the function or content of the encapsulation node to help users understand the role of the node. The data asset name is the name that identifies the encapsulated data asset, which is convenient for management and search in the digital network. The digital object unique identifier (DOI) is used to assign a globally unique identifier to the encapsulated digital object to ensure its uniqueness in the digital network. The business category is used to define the encapsulated digital object. The business field to which the image belongs is convenient for classification management and retrieval. Keywords are used to extract keywords related to the content of the encapsulated digital object to facilitate subsequent search and analysis. The format type is the format type of the data in the encapsulated digital object, such as structured data or unstructured data. The data format is used to describe in detail the specific format of the data in the digital object, such as JSON, CSV, XML, etc. The publisher refers to the executor of the record encapsulation operation, which is convenient for responsibility tracing and management, and generally refers to the user. The data publication subject refers to the publication subject or purpose of the data in the digital object. The data resource description is used to describe the data in the encapsulated digital object in detail, including information such as data source, processing process, application scenario, etc.

[0181] By configuring the attribute information of the encapsulated node in detail, such as node name, description, data asset name, digital object unique identifier, business category, keyword, format type, data format, publisher, data publishing subject and data resource description, etc., it not only provides a detailed metadata description for the encapsulated digital object, but also ensures the uniqueness, searchability and manageability of the digital object in the digital network.

[0182] Then, in this embodiment, after a series of data processing and logical control are performed on the data in the digital objects bound to the data nodes through the computing components and the process control components, the final output operation result will be obtained, and the operation result will be encapsulated through the encapsulation node according to the attribute information of the digital object with new data or new functions to obtain a new digital object, and the new digital object will be added to the digital network for management and application.

[0183] In combination with the above embodiments, an embodiment of the present application provides another method for orchestration and fusion generation of digital objects based on the Internet of Things, which further refines the configuration method of the connection relationship between data nodes and operation nodes. According to the business requirements for digital object generation and the in-degree requirements of the operation nodes, the connection relationship between data nodes and operation nodes can be flexibly configured as a serial or parallel operation mode. In this method, the "establishing the connection relationship between the data node and the operation node according to the business requirements for digital object generation and the in-degree requirements of the operation node" in step S17 specifically includes steps S17-1 and S17-2:

[0184] Step S17-1: When the in-degree of the operation node is a data node, it is determined that the data nodes connected to the operation node can only run serially.

[0185] In this embodiment, if the in-degree of an operation node is a data node, that is, the input side of the operation node is connected to a data node, it means that the operation node only relies on one data source for processing. In this case, the data nodes connected to the operation node can only run serially.

[0186] For example, a filter component's operation node filters out records that meet specific criteria from a data object (such as a data table) within a data node. Because this operation node relies on only one data table as input, the system configures the data nodes corresponding to that table to run serially, ensuring that data is processed sequentially and that the filtering operation is accurate and consistent.

[0187] Step S17-2: When the in-degree of the operation node is two or more data nodes, determine whether the data nodes connected to the operation node can run in series and / or in parallel.

[0188] In this embodiment, if the in-degree of an operation node is two or more data nodes, this means that the operation node needs to process multiple data sources simultaneously. In this case, it is determined whether the data nodes connected to the operation node can run in series and / or in parallel.

[0189] For example, a join component's operation node joins data objects (such as two or more data tables) across multiple data nodes based on specified fields. Because this operation node relies on multiple data tables as input, the system can flexibly configure the nodes corresponding to these tables to run serially or in parallel, depending on business needs and performance optimization requirements.

[0190] Through the above embodiments, in the process of flexibly configuring the connection relationship between data nodes and operation nodes, the orchestration and fusion generation method based on the digital network digital object is further optimized. When the in-degree of the operation node is one data node, the data node is configured to run in series to ensure the order and accuracy of data processing, which is suitable for scenarios that rely on a single data source. When the in-degree of the operation node is two or more data nodes, these data nodes support flexible configuration of serial and parallel operation, which not only meets complex business needs, but also improves the efficiency and performance of the system through parallel processing. This flexible connection relationship configuration method enables users to design efficient and reliable orchestration and fusion task processes based on specific business needs and performance requirements, thereby significantly improving the flexibility and adaptability of data processing in the digital network environment.

[0191] refer to Figure 6 , Figure 6 This is a schematic diagram of the execution orchestration fusion task process provided by an embodiment of the present application. Combined with the above embodiment, an embodiment of the present application provides another orchestration fusion generation method based on digital objects in the Internet of Things, which further refines the execution process of the orchestration fusion task process in step S18.

[0192] Specifically, the method implements the execution of the orchestration fusion task process and generates a digital object with new data or new functions through the following steps. In this method, the method further includes steps S21-1 to S21-3:

[0193] Step S21-1: Establishing a connection relationship between the data node and the operation node based on the digital object generation business requirement and the in-degree requirement of the operation node, and establishing a connection relationship between the process control node and the data node based on the digital object generation business requirement and the logical control requirement of the process control node; the connection relationship is used to represent the flow direction and processing order of data in the digital object bound to the data node;

[0194] According to the connection relationship, an orchestration fusion flowchart corresponding to the orchestration fusion task process is output, and an orchestration fusion execution script is generated based on the orchestration fusion flowchart and saved in a database.

[0195] In this embodiment, after completing the design of the orchestration and connection of various pre-built components in the orchestration and fusion flow chart corresponding to the orchestration and fusion task process, the orchestration and fusion flow chart is output, converted into an orchestration and fusion execution script, and stored in the database. The orchestration and fusion execution script is a recognizable language and word order description used for the subsequent execution of the orchestration and fusion task process, ensuring that the orchestration and fusion task process can be correctly parsed and executed. The database contains the orchestration and fusion execution scripts of multiple orchestration and fusion task processes, which need to be executed in sequence or priority.

[0196] Step S21 - 2 : Based on the execution order of the orchestration fusion task process, the orchestration fusion execution script is read from the database and parsed to generate a digital object orchestration fusion execution instance.

[0197] In this embodiment, first enter the interface of the orchestration and fusion task process and click the execution button of the orchestration and fusion task process. Before actually executing the orchestration and fusion task process, it is necessary to read the orchestration and fusion execution script corresponding to the orchestration and fusion task process from the database. The script is generated based on the orchestration and fusion task process designed by the user in the orchestration and fusion process canvas, and contains the configuration information of all data nodes, operation nodes and process control nodes, as well as the connection relationship and execution order between each node. The script is parsed and converted into a specific digital object orchestration and fusion execution instance. The digital object orchestration and fusion execution instance describes in detail the function of each node, the input and output relationship and the execution logic of the entire process, providing guidance for subsequent task execution.

[0198] In step S21-3, the execution engine sequentially executes the digital object orchestration fusion execution instance according to the scheduling stack table in the digital object orchestration fusion execution instance, and calls the corresponding computing model for the serial type, parallel type, and conditional type nodes to obtain the digital object with new data and / or new functions.

[0199] During execution, the execution engine executes the orchestration-fusion task flow according to the predetermined sequence specified in the scheduling stack table within the digital object orchestration-fusion execution instance. The scheduling stack table is the core plan for task execution, recording the execution order and dependencies of the orchestration-fusion task flow. Based on the information in the scheduling stack table, the execution engine sequentially calls the functions of each node and invokes the corresponding computational model for each node type to drive access to digital objects and computational components, ultimately generating new digital objects.

[0200] Among them, the conditional type data node is a data node connected to the process control node whose node type is a conditional branch, indicating that the data node needs to determine whether the condition of the process control node of the conditional branch is met before executing the next step; the parallel type data node is a data node connected to the process control node whose node type is a parallel branch, indicating that the data node needs to simultaneously execute data processing of the operation nodes of multiple computing components connected to the parallel branch process control node.

[0201] The details are as follows:

[0202] Serial nodes: For nodes that need to be executed sequentially, the execution engine calls each node's function in the order defined in the scheduling stack. For example, the deduplication process of a data node must be executed before the data node is joined to ensure data accuracy.

[0203] Parallel nodes: For nodes that can be executed simultaneously, the execution engine will call the functions of these nodes in parallel to improve the execution efficiency of the task. For example, an operation node can process digital objects in different data nodes at the same time.

[0204] Conditional nodes: For nodes containing conditional logic, the execution engine selectively executes certain branches based on the results of the conditional judgment. For example, if the output of a data node meets a specific condition, the subsequent filtering operation is executed; otherwise, the operation is skipped.

[0205] During the entire execution process, the execution engine will dynamically manage the operating status of each node to ensure that the task is executed smoothly according to the predetermined logic and sequence.

[0206] The encapsulation node is then called through the execution engine to obtain the operation results containing new data or new functions generated during the execution process, and the operation results are submitted to the digital network system as a digital object with new data or new functions.

[0207] In this embodiment, before the execution engine calls the encapsulation node, it obtains the execution results generated during the execution process, including new data or new functions. These results are generated through data processing by a series of computing components and the logical sequence of process control components, representing the new data ultimately output by the orchestration and fusion task process. The encapsulation node encapsulates these results into a new digital object and assigns it the necessary metadata (such as a unique digital object identifier and service category) and a digital object identifier. Finally, the system submits the generated digital object containing the new data or new functions to the digital network system for management, making it accessible and usable by other users or systems.

[0208] Through the above embodiments, the orchestration fusion generation method based on digital objects in the Internet of Things is further optimized, especially in terms of the execution and result generation of orchestration fusion tasks. First, by reading and parsing the orchestration fusion execution script from the database, the digital object orchestration fusion execution instance can be accurately generated, providing a basis for the efficient execution of tasks. Secondly, the execution engine executes tasks in sequence according to the scheduling stack table, and calls the corresponding computing model for different types of nodes, which not only ensures the logic and sequentiality of the task, but also improves the execution efficiency of the task through parallel processing. Finally, by obtaining the running results and submitting new digital objects, the results of the orchestration fusion can be stored and shared in a standardized form, further improving the generation effect of the data object.

[0209] In combination with the above embodiments, an embodiment of the present application provides another method for generating orchestration fusion based on digital objects in a digital network. In this method, after executing step S21-1 of "outputting an orchestration fusion flow chart corresponding to the orchestration fusion task process according to the connection relationship", the method specifically includes steps S31-1 and S31-2:

[0210] In step S31-1, a plurality of proofreading rules are used to verify the legitimacy of the orchestration fusion flowchart. The proofreading rules include but are not limited to: whether it is a directed acyclic graph, whether the data node output is correctly connected to the computing component, whether the name identifier of each node is unique, whether it contains the necessary components of the orchestration fusion process, and whether each node contains its required attribute values.

[0211] In this embodiment, reference Figure 2 ,Before converting the orchestration fusion flowchart into the orchestration fusion ,execution script, in order to ensure the logical correctness and integrity of the ,orchestration fusion flowchart and avoid errors or exceptions during the ,execution process, it is necessary to use multiple proofreading rules to verify the ,legality of the orchestration fusion flowchart.

[0212] Among them, these verification rules include the following:

[0213] 1. Whether it is a directed acyclic graph (DAG): Ensure that the orchestration fusion flowchart must be a directed acyclic graph. There must not be any cyclic relationships between the nodes in the flowchart; otherwise, the process will not be able to complete.

[0214] For example, when the output of an operation node is directly or indirectly connected to its own input, it will cause an infinite loop and make the task unable to complete.

[0215] Data node outputs are correctly connected to compute components: Checks whether each data node's output is correctly connected to the corresponding compute component. For example, if a data node's output data type is structured data, but the connected compute component requires unstructured data input, the connection is illegal. Verifying this rule can prevent task execution failures due to data type mismatches.

[0216] Is each node's name unique? To ensure readability and manageability, the system requires each node's name to be unique. For example, if two operational nodes are both named "Data Deduplication Node," confusion and errors can result. By verifying the uniqueness of node names, each node can be clearly identified and managed.

[0217] Check whether the orchestration and fusion process contains the necessary components: Check whether the orchestration and fusion process diagram contains the necessary components, such as data nodes, computing components, and process control components. For example, a complete orchestration and fusion process requires at least one data node to provide input data and one computing component to process the data, or it must include an encapsulation node. Otherwise, the new digital object cannot be generated. If the necessary components are missing, the process will not execute properly.

[0218] Check that each node contains all required attribute values. For example, a data node must be configured with information about the bound numeric object, and a compute component must be configured with parameters for its operation logic, such as the join field expression of a join component. If some nodes are missing required attribute values, data cannot be processed correctly during task execution.

[0219] Step S31 - 2 : converting the verified arrangement fusion flow chart into an arrangement fusion execution script described in a recognizable language and word order and saving it into a database.

[0220] In this embodiment, after verification, the orchestration fusion flow chart is converted into an orchestration fusion execution script described in a recognizable language and syntax, and saved to a database for direct call during the candidate execution process. The orchestration fusion execution script is the specific execution code for the orchestration fusion task. It describes the execution logic of the entire orchestration fusion process in a recognizable language (such as JSON, XML, or other programming languages), including the configuration of data nodes, the functions of operation nodes, the connection relationships between nodes, and the execution order of the process.

[0221] Through the above embodiments, the legitimacy verification and execution script generation process of the orchestration fusion flowchart are refined, and the reliability and execution efficiency of the digital object generation process of the Internet of Things are significantly improved.

[0222] refer to Figure 7 , Figure 7 This is a schematic diagram of a framework of an arrangement fusion generation device based on a digital network digital object provided by one embodiment of the present application. Based on the same inventive concept, another embodiment of the present application further provides an arrangement fusion generation device based on a digital network digital object, the device comprising:

[0223] The digital object orchestration fusion execution instance generation module 11 is configured to read the orchestration fusion execution script of the orchestration fusion task process from the database upon receiving a signal from an execution button of the orchestration fusion task process in the list interface of the orchestration fusion task process, and generate a digital object orchestration fusion execution instance;

[0224] The orchestration fusion execution module 12 is configured to, through an execution engine, call the data and functions of the digital object bound to each data node, the functions of each operation node, and the functions of each process control node in the digital object orchestration fusion execution instance according to the order in the scheduling stack table in the digital object orchestration fusion execution instance, thereby generating a digital object with new data or new capabilities;

[0225] Among them, the orchestration fusion task process is generated by an orchestration fusion flowchart obtained by connecting multiple pre-built components. The pre-built components are divided into data resource components, computing components and process control components. The data resource components include data nodes for accessing and managing data in digital objects; the computing components include operation nodes for processing and converting data in digital objects; the process control components include process control nodes for defining the logical structure of the orchestration process.

[0226] Optionally, the device further comprises:

[0227] The first adding module is configured to, before receiving a signal from an execution button of the orchestration fusion task process, further include configuring multiple data resource components according to the following steps: generating business requirements based on digital objects, adding multiple data resource components to the orchestration fusion process canvas, and obtaining the node name and node description of the data node filled in the property interface of the data node of each data resource component;

[0228] The first acquisition module is used to bind the digital object related to the business requirement of generating the digital object to the corresponding data node from the digital object list of the digital network system for each data node, and obtain the data type of the bound digital object in the attribute interface.

[0229] Optionally, the device further comprises:

[0230] The second adding module is configured to, before receiving a signal from an execution button of the orchestration fusion task process, further include configuring a plurality of different types of computing components according to the following steps: generating business requirements based on the digital object, and adding the plurality of different types of computing components to the orchestration fusion process canvas;

[0231] a second acquisition module configured to, for each operation node, acquire, when the computing component is a word segmentation component in an unstructured computing component, a node name and a node description of the operation node entered in a property interface of the operation node of the word segmentation component; the operation node of the word segmentation component is used to perform a word segmentation operation on data in a digital object whose data type is unstructured data;

[0232] a third acquisition module configured to, for each operation node, acquire, when the computing component is a joint component in a structured computing component, a node name and a node description of the operation node entered in a property interface of the operation node of the joint component; the operation node of the joint component is used to perform a joint operation on data in two digital objects whose data type is structured data;

[0233] a fourth acquisition module, for each operation node, when the computing component is a filtering component in a structured computing component, acquiring the node name and node description of the operation node entered in the property interface of the operation node of the filtering component, as well as the filtering condition expression of the operation node, wherein the operation node of the filtering component is used to filter data in a digital object whose data type is structured data according to the filtering condition expression;

[0234] a fifth acquisition module, for each operation node, when the computing component is a deduplication component in a structured computing component, acquiring the node name and node description of the operation node entered in the property interface of the operation node of the deduplication component, as well as the filtering condition expression of the operation node, wherein the operation node of the deduplication component is used to delete duplicate data in data of a digital object whose data type is structured data;

[0235] a sixth acquisition module, configured to, for each operation node, acquire, when the computing component is a sorting component in a structured computing component, a node name and a node description of the operation node entered in a property interface of the operation node of the sorting component, as well as a sorting field expression for the operation node, wherein the operation node of the sorting component is configured to perform ascending or descending order on data in a digital object whose data type is structured data according to the sorting field expression;

[0236] The seventh acquisition module is used to obtain, for each operation node, the node name of the operation node and the node description of the operation node filled in the attribute interface of the operation node of the word segmentation statistics component when the calculation component is a word segmentation statistics component in a hybrid calculation component. The operation node of the word segmentation statistics component is used to calculate the frequency of occurrence of words in the data of a digital object whose data type is structured data after word segmentation in unstructured data.

[0237] Optionally, the device further comprises:

[0238] The eighth acquisition module is configured to, before receiving a signal from an execution button of the orchestration fusion task flow, further include configuring multiple different types of computing components according to the following steps: for each operation node, when the computing component is a connection component in a structured computing component, obtain the node name and node description of the operation node filled in the property interface of the operation node of the connection component, as well as the connection field expression of the operation node; the operation node of the connection component is used to connect data in two digital objects whose data type is structured data according to the specified field in the connection field expression;

[0239] Wherein, the connection component includes a left connection component, a right connection component and an inner connection component;

[0240] The operation node of the left join component is used to left join the data in two digital objects whose data type is structured data according to the specified field;

[0241] The operation node of the right connection component is used to right connect the data in two digital objects whose data type is structured data according to the specified field;

[0242] The operation node of the inner connection component is used to perform inner connection on the data in two digital objects whose data types are structured data according to the specified fields.

[0243] Optionally, the device further comprises:

[0244] The third adding module is configured to, after configuring the plurality of data resource components and the plurality of different types of computing components, further include configuring the data encapsulation component according to the following steps: generating business requirements based on the digital object, and adding the data encapsulation component in the data component to the orchestration fusion process canvas;

[0245] a ninth acquisition module, configured to acquire, for the encapsulation node in the data encapsulation component, attribute information of the encapsulation node input by the user in the attribute page of the encapsulation node;

[0246] Among them, the attribute information of the encapsulated node includes: node name, node description, and attribute information of the digital object with new data or new functions. The attribute information of the digital object with new data or new functions includes: data asset name, digital object unique identifier, business category, keyword, format type, data format, publisher, data publishing subject, and data resource description.

[0247] Optionally, the device further comprises:

[0248] A setup module, used to setup pre-built components before adding them to the orchestration fusion process canvas;

[0249] A creation module is used to create a visual orchestration and fusion process canvas, where the orchestration and fusion process canvas is used to display pre-built components that can be dragged and a blank area for performing orchestration and fusion process operations.

[0250] Optionally, the device further comprises:

[0251] The fourth adding module is configured to, before receiving a signal from the execution button of the orchestration fusion task process, further include configuring the process control component to generate business requirements based on the digital object according to the following steps, and adding the process control component to the orchestration fusion process canvas;

[0252] a tenth acquisition module, configured to acquire, for a process control node in the process control component, attribute information of the process control node input by a user in an attribute page of the process control node;

[0253] Among them, the attribute information of the process control node includes: node name, node description; the process control node is used to control the logic of the orchestration fusion task process; the node type of the process control node includes: conditional branch, parallel branch and process end.

[0254] Optionally, the method further includes:

[0255] a connection establishment module, configured to establish a connection relationship between the data node and the operation node based on the business requirements of the digital object generation and the in-degree requirements of the operation node, and to establish a connection relationship between the process control node and the data node based on the business requirements of the digital object generation and the logical control requirements of the process control node; the connection relationship is used to represent the flow direction and processing order of data in the digital object bound to the data node;

[0256] A flowchart output module is used to output the orchestration fusion flowchart corresponding to the orchestration fusion task process according to the connection relationship, and generate an orchestration fusion execution script based on the orchestration fusion flowchart and save it in a database;

[0257] A first determining module is configured to, when the in-degree of the operation node is one data node, determine that the data nodes connected to the operation node can only run in series;

[0258] The second determining module is configured to determine, when the in-degree of the operating node is two or more data nodes, whether the data nodes connected to the operating node can run in series and / or in parallel.

[0259] Optionally, the device further comprises:

[0260] A verification module is used to, after outputting the orchestration fusion flow chart corresponding to the orchestration fusion task process according to the connection relationship, use multiple proofreading rules to verify the legitimacy of the orchestration fusion flow chart, the proofreading rules including but not limited to: whether it is a directed acyclic graph, whether the data node output is correctly connected to the computing component, whether the name identifier of each node is unique, whether it contains the necessary components of the orchestration fusion process, and whether each node contains its necessary attribute values;

[0261] The saving module is used to convert the verified orchestration fusion flow chart into an orchestration fusion execution script described in a recognizable language and word order and save it in a database.

[0262] Optionally, the orchestration fusion execution module 12 includes:

[0263] an execution unit, configured to sequentially execute the digital object orchestration fusion execution instance according to the scheduling stack table in the digital object orchestration fusion execution instance, and invoke corresponding computing models for serial, parallel, and conditional data nodes to obtain the digital object with the new data or new capability;

[0264] Among them, the conditional type data node is a data node connected to the process control node whose node type is a conditional branch, indicating that the data node needs to determine whether the condition of the process control node of the conditional branch is met before executing the next step; the parallel type data node is a data node connected to the process control node whose node type is a parallel branch, indicating that the data node needs to simultaneously execute data processing of the operation nodes of multiple computing components connected to the parallel branch process control node.

[0265] Based on the same inventive concept, another embodiment of the present application also provides an electronic device, including a memory, a processor, and a computer program stored on the memory, wherein the processor executes the computer program to implement the arrangement and fusion generation method based on digital objects in the Internet of Things as described in any of the above embodiments.

[0266] Based on the same inventive concept, another embodiment of the present application further provides a computer program product, including a computer program, which is executed by a processor to implement the arrangement and fusion generation method based on Internet digital objects as described in any of the above embodiments.

[0267] Based on the same inventive concept, another embodiment of the present application further provides a computer-readable storage medium on which a computer program is stored, wherein when the program is executed by a processor, the arrangement and fusion generation method based on digital objects in the Internet of Things as described in any of the above embodiments is implemented.

[0268] As for the device, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0269] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other.

[0270] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, devices, or computer program products. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0271] The embodiments of the present application are described with reference to the flowcharts and / or block diagrams of the methods, terminal devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing terminal device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing terminal device generate instructions for implementing the steps in the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0272] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing terminal device to operate in a specific manner, so that the instructions stored in the computer readable memory produce a manufactured product including an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0273] These computer program instructions can also be loaded onto a computer or other programmable data processing terminal device so that a series of operating steps are executed on the computer or other programmable terminal device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable terminal device to implement the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0274] Although preferred embodiments of the present invention have been described, those skilled in the art may make additional changes and modifications to these embodiments once they become aware of the basic inventive concepts. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the embodiments of the present invention.

[0275] Finally, in this document, relational terms such as first and second are used solely to distinguish one entity or operation from another, and do not necessarily require or imply any actual relationship or order between these entities or operations. Furthermore, the terms "comprise," "include," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or terminal device comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or terminal device. Without further limitation, an element defined by the phrase "comprising a..." does not preclude the presence of other identical elements in the process, method, article, or terminal device comprising the element. The above detailed description of the arrangement, fusion, and generation method based on networked digital objects provided by this application has been presented. This article uses specific examples to illustrate the principles and implementation methods of this application. The description of the above examples is intended only to help understand the method and its core concept. At the same time, for those skilled in the art, based on the concept of this application, there may be variations in the specific implementation methods and scope of application. In summary, the contents of this specification should not be construed as limiting this application.

Claims

1. A method for generating arrangement and fusion of digital objects based on the Internet of Things, characterized in that: The method comprises: On the list interface of the orchestration fusion task flow, after receiving the signal sent by the execution button of the orchestration fusion task flow, the orchestration fusion execution script of the orchestration fusion task flow is read from the database to generate a digital object orchestration fusion execution instance; By means of an execution engine, data and functions of digital objects bound to each data node, functions of each operation node, and functions of each process control node in the digital object orchestration fusion execution instance are called according to the order in the scheduling stack table in the digital object orchestration fusion execution instance to generate a digital object with new data or new capabilities; the digital object with new data or new capabilities is generated by utilizing the functions of one or more existing digital objects and pre-built components; the digital object with new data or new capabilities is used to be submitted to the digital network system for management, so that it can be accessed and used by other users or systems; The step of calling data and functions in a digital object bound to each data node, functions of each operation node, and functions of each process control node in the digital object orchestration fusion execution instance according to the order in the scheduling stack table in the digital object orchestration fusion execution instance to generate a digital object with new data or new capabilities includes: According to the scheduling stack table in the digital object orchestration fusion execution instance, the digital object orchestration fusion execution instance is sequentially executed, and corresponding computing models are called for serial type, parallel type, and conditional type data nodes to obtain the digital object with new data or new capabilities; Among them, the orchestration fusion task process is generated by an orchestration fusion flowchart obtained by connecting multiple pre-built components. The pre-built components are divided into data resource components, computing components and process control components. The data resource components include data nodes for accessing and managing data in digital objects; the computing components include operation nodes for processing and converting data in digital objects; the process control components include process control nodes for defining the logical structure of the orchestration process.

2. The arrangement fusion generation method based on digital objects in the digital network according to claim 1 is characterized in that: Before receiving the signal from the execution button of the orchestration fusion task process, the process also includes configuring multiple data resource components according to the following steps: According to the business requirements of the digital object generation, multiple data resource components are added to the orchestration and fusion process canvas, and the node name and node description of the data node filled in the property interface of the data node of each data resource component are obtained; For each data node, a digital object related to the digital object generation business requirement is bound to the corresponding data node from the digital object list of the digital network system, and the data type of the bound digital object is obtained in the property interface.

3. The arrangement fusion generation method based on digital objects in the digital network according to claim 2 is characterized in that: Before receiving the signal from the execution button of the orchestration fusion task flow, the process also includes configuring multiple different types of computing components according to the following steps: Generate business requirements based on digital objects and add multiple different types of computing components to the orchestration and fusion process canvas; For each operation node, when the computing component is a word segmentation component in an unstructured computing component, obtaining the node name and the node description of the operation node filled in the property interface of the operation node of the word segmentation component; The operation node of the word segmentation component is used to perform word segmentation operation on the data in the digital object whose data type is unstructured data; For each operation node, when the computing component is a joint component in a structured computing component, obtaining the node name and the node description of the operation node filled in the property interface of the operation node of the joint component; the operation node of the joint component is used to perform a joint operation on data in two digital objects whose data type is structured data; For each operation node, when the computing component is a filtering component in a structured computing component, obtaining the node name and node description of the operation node filled in the property interface of the operation node of the filtering component, as well as the filtering condition expression of the operation node, wherein the operation node of the filtering component is used to filter data in a digital object whose data type is structured data according to the filtering condition expression; For each operation node, when the computing component is a deduplication component in a structured computing component, obtaining the node name and node description of the operation node filled in the property interface of the operation node of the deduplication component, as well as the filtering condition expression of the operation node, wherein the operation node of the deduplication component is used to delete duplicate data in data in a digital object whose data type is structured data; For each operation node, when the calculation component is a sorting component in a structured calculation component, obtaining the node name and node description of the operation node filled in the property interface of the operation node of the sorting component, as well as the sorting field expression of the operation node, the operation node of the sorting component being used to perform ascending or descending order on the data in the digital object whose data type is structured data according to the sorting field expression; For each operation node, when the computing component is a word segmentation statistics component in a hybrid computing component, obtain the node name of the operation node and the node description of the operation node filled in the property interface of the operation node of the word segmentation statistics component. The operation node of the word segmentation statistics component is used to calculate the frequency of occurrence of words in the data of a digital object whose data type is structured data after word segmentation in unstructured data.

4. The method for generating arrangement and fusion based on digital objects in the digital network according to claim 3, characterized in that: Before receiving the signal from the execution button of the orchestration fusion task flow, the process also includes configuring multiple different types of computing components according to the following steps: For each operation node, when the computing component is a connection component in a structured computing component, obtaining the node name and node description of the operation node filled in the property interface of the operation node of the connection component, as well as the connection field expression of the operation node; the operation node of the connection component is used to connect the data in two digital objects whose data type is structured data according to the specified fields in the connection field expression; Wherein, the connection component includes a left connection component, a right connection component and an inner connection component; The operation node of the left join component is used to left join the data in two digital objects whose data type is structured data according to the specified field; The operation node of the right connection component is used to right connect the data in two digital objects whose data type is structured data according to the specified field; The operation node of the inner connection component is used to perform inner connection on the data in two digital objects whose data types are structured data according to the specified fields.

5. The arrangement fusion generation method based on digital objects in the digital network according to claim 4 is characterized in that: After configuring multiple data resource components and multiple different types of computing components, you also need to configure the data encapsulation component by following these steps: Generate business requirements based on digital objects and add data encapsulation components in the data component to the orchestration and fusion process canvas; For the encapsulation node in the data encapsulation component, obtaining attribute information of the encapsulation node input by the user in the attribute page of the encapsulation node; Among them, the attribute information of the encapsulated node includes: node name, node description, and attribute information of the digital object with new data or new functions. The attribute information of the digital object with new data or new functions includes: data asset name, digital object unique identifier, business category, keyword, format type, data format, publisher, data publishing subject, and data resource description.

6. The method for generating arrangement and fusion based on digital objects in the digital network according to claim 5, characterized in that: Before adding pre-built components to the orchestration fusion process canvas, also include: Setting up pre-built components; A visual orchestration and fusion process canvas is created, where the orchestration and fusion process canvas is used to display pre-built components that can be dragged and a blank area for performing orchestration and fusion process operations.

7. The method for generating arrangement and fusion based on digital objects in the digital network according to claim 2, characterized in that: Before receiving the signal from the execution button of the orchestration fusion task process, the process control component is configured according to the following steps: Generate business requirements based on digital objects and add process control components to the orchestration and fusion process canvas; For a process control node in the process control component, obtaining attribute information of the process control node input by a user in an attribute page of the process control node; Among them, the attribute information of the process control node includes: node name, node description; the process control node is used to control the logic of the orchestration fusion task process; the node type of the process control node includes: conditional branch, parallel branch and process end.

8. The arrangement fusion generation method based on digital objects in the digital network according to claim 7 is characterized in that: The method further comprises: Establishing a connection relationship between the data node and the operation node based on the digital object generation business requirement and the in-degree requirement of the operation node, and establishing a connection relationship between the process control node and the data node based on the digital object generation business requirement and the logical control requirement of the process control node; the connection relationship is used to represent the flow direction and processing order of data in the digital object bound to the data node; Output the orchestration fusion flow chart corresponding to the orchestration fusion task process according to the connection relationship, and generate an orchestration fusion execution script based on the orchestration fusion flow chart and save it in the database; When the in-degree of the operation node is a data node, it is determined that the data nodes connected to the operation node can only run serially; When the in-degree of the operation node is two or more data nodes, it is determined that the data nodes connected to the operation node can run in series and / or in parallel.

9. The arrangement fusion generation method based on digital objects in the digital network according to claim 8 is characterized in that: After outputting the orchestration fusion flow chart corresponding to the orchestration fusion task process according to the connection relationship, the method further includes: Use multiple proofreading rules to verify the legitimacy of the orchestration fusion flow chart. The proofreading rules include, but are not limited to: whether it is a directed acyclic graph, whether the data node output is correctly connected to the computing component, whether the name identifier of each node is unique, whether it contains the necessary components of the orchestration fusion process, and whether each node contains its required attribute values; The verified orchestration fusion flowchart is converted into an orchestration fusion execution script described in a recognizable language and word order and saved in the database.

10. The arrangement fusion generation method based on digital objects in the digital network according to claim 9 is characterized in that: in, The conditional type data node is a data node connected to a process control node whose node type is a conditional branch, indicating that the data node needs to determine whether the condition of the conditional branch process control node is met before executing the next step; the parallel type data node is a data node connected to a process control node whose node type is a parallel branch, indicating that the data node needs to simultaneously execute data processing of the operation nodes of multiple computing components connected to the parallel branch process control node.

Images