Business system fusion management method based on meta-model driving and related device

Abstract

The invention provides a business system fusion management method based on meta-model driving and a related device. The method comprises the following steps: establishing a stable data transmission channel between a group side and each base side; business models of the group side and each base side are defined on the group side based on a meta-model driving mechanism, a standardized meta-model library is generated based on all the business models, and meta-model definitions of the standardized meta-model library are synchronized to each base side; the application developed by the group side is issued to the target base side, and the target base side executes the deployment and integration work of the application and reports the deployment state of the application in real time; managing and controlling data flow between the group side and the target base side based on a data collaboration rule configured by the group side for the application according to the service demand; and monitoring and continuously optimizing the deployed applications at each base side at the group side. According to the invention, on the basis of respecting the existing heterogeneous system, standardized, efficient and automatic unified management and control and collaboration of the multi-base service system by the group can be realized.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of business system management, and in particular to a business system fusion management method based on a meta-model drive and related devices. BACKGROUND

[0002] With the expansion of the group (i.e. group enterprise), its subordinate bases (i.e. production bases) are often distributed in the country and even around the world. In order to realize the unified strategic control and cost reduction and efficiency improvement of the group, the group needs to centrally manage the business systems (such as manufacturing execution systems, warehouse management systems, quality management systems, etc.) of these multi-base. However, under the existing technical conditions, such centralized management mainly faces the following core problems: (1) System heterogeneity and information island problem: the business systems of each base are often constructed by different suppliers in different technical periods, resulting in significant differences (i.e. "heterogeneity") in technical architecture, data model and business process, forming a solid "information island". The group level lacks a unified perspective, making it difficult to implement effective monitoring, analysis and business intervention.

[0003] (2) Low efficiency of business configuration and management: when the group needs to implement new business standards or processes (such as unified material coding, quality inspection specifications), it must repeat and tedious customized configuration, development and deployment for the heterogeneous systems of each base. This process not only consumes time and effort, but also has high coordination costs, and is prone to cause standards to be executed differently in each base due to human understanding bias, making it impossible to achieve true business standardization.

[0004] (3) Insufficient real-time and consistency of data collaboration: traditional data integration solutions (such as point-to-point interface, ESB enterprise service bus) have complex architecture and high system coupling. It is difficult to achieve efficient and low-latency two-way synchronization of the instructions (such as plan adjustment) issued by the group and the data (such as production, inventory) reported by the base. The group's decision is often based on lagging and one-sided information, which cannot meet the needs of real-time scheduling and fine management, hindering the realization of data standardization.

[0005] (4) Difficulty in system scalability and standardized operation and maintenance: each time a base is added or a minor business change is made, a large amount of resources need to be invested in "rebuilding" type customized development and system integration. This mode makes the system scalability very poor, and the operation and maintenance difficulty and cost increase exponentially with the number of bases, making it impossible to standardize operation and maintenance.

[0006] In summary, there is an urgent need for a technical solution that can respect existing heterogeneous systems and achieve standardized, efficient and automated unified control and collaboration of the group's multi-base business systems. SUMMARY

[0007] The embodiment of the application provides a business system fusion management method based on a meta-model driving and related devices to solve the problems in related technologies, and the technical scheme is as follows: In a first aspect, the embodiment of the application provides a business system fusion management method based on a meta-model driving, comprising: Establishing a stable data transmission channel between a group side and each base side, wherein the group side refers to a business fusion management platform of a group, the base side refers to a business system of a base, and the base refers to a subordinate base of the group; Defining, at the group side, business models of the group side and each base side based on a meta-model driving mechanism, generating a standardized meta-model library based on all the business models, and synchronizing meta-model definitions of the standardized meta-model library to each base side through the data transmission channel; Downlinking an application developed by the group side to a target base side through the data transmission channel, performing deployment and integration of the application by the target base side using the standardized meta-model library, and reporting, in real time, a deployment state of the application to the group side through the data transmission channel, wherein the target base side is one or more base sides in each base side; Configuring, at the group side, data collaboration rules for the application according to business requirements, and controlling data flow between the group side and the target base side when the target base side runs the application based on the data collaboration rules; Monitoring and continuously optimizing the deployed application of each base side at the group side to realize comprehensive fusion management of each base side at the group side.

[0008] In an implementation manner, establishing a stable data transmission channel between the group side and each base side comprises: Initializing network connection: using a WebSocket protocol to establish a real-time transmission channel between the group side and each base side, and using an HTTP protocol to establish a non-real-time transmission channel between the group side and each base side; Authentication and security configuration: after the group side is connected with each base side, performing identity authentication on each base side and configuring an encrypted channel; Channel testing and maintenance: testing a connection state between the group side and each base side, and automatically reconnecting when the connection is interrupted.

[0009] In an implementation manner, defining, at the group side, business models of the group side and each base side based on a meta-model driving mechanism, generating a standardized meta-model library based on all the business models, and synchronizing meta-model definitions of the standardized meta-model library to each base side through the data transmission channel comprises: Defining a meta-model structure: using annotations to describe the business services, business objects and their attribute data of the group side and each base side in the code, obtaining the business models of the group side and each base side; Establishing data relationships: using relationship annotations to describe the association relationships between all business models on the group side; Generating a meta-model library: storing all business models defined by annotations into the group meta-model library to generate the standardized meta-model library; Synchronizing meta-models: notifying the meta-model changes of the standardized meta-model library to each base side through the data transmission channel.

[0010] In an embodiment, the application developed by the group side is distributed to the target base side through the data transmission channel, and the target base side performs deployment and integration of the application by using the standardized meta-model library, and reports the deployment status of the application to the group side in real time through the data transmission channel, including: Application packaging and shelving: packaging the application into an application installation package, associating the application installation package with a target business model, and shelving the application on the group side, the target business model being a business model related to the application in the standardized meta-model library; Application distribution: creating an application collaboration scheme of the application on the group side, determining the base side specified in the application collaboration scheme as the target base side, and distributing the application installation package to the target base side through the data transmission channel; Application installation and integration: automatically installing the application by the target base side based on the application installation package, verifying data compatibility of the application by using the target business model during the installation process, and completing the integration of the application; State monitoring and feedback: reporting the deployment status of the application to the group side in real time by the target base side through the data transmission channel, and displaying the application deployment status of each base side on the group side.

[0011] In an embodiment, the group side configures data collaboration rules for the application according to business requirements, and controls the target base side running the application based on the data collaboration rules, and the data flow between the group side and the target base side includes: Rule definition: configuring a sending end policy and a receiving end policy for the business models involved in the application on the group side, obtaining the data collaboration rules, wherein the sending end policy is used to define the trigger condition and content of data pushing, and the receiving end policy is used to define the processing logic after data receiving; Rule publishing and taking effect: publishing the data collaborative rule to the target base side through the data transmission channel, loading the data collaborative rule into the local rule engine by the target base side, and making the data collaborative rule officially take effect; Rule running: running the data collaborative rule in combination with Kafka message queue and PowerJob, and following the predefined DAG task flow; Rule verification: providing a unified monitoring panel on the group side, and through the unified monitoring panel, showing the data flow state between the group side and the target base side when the target base side runs the application, and supporting users to view relevant data to verify whether the data collaborative rule runs as expected.

[0012] In an embodiment, the sending end strategy includes: a synchronization mode, a data range, a filtering condition, and a mapping strategy of data collaboration, wherein the synchronization mode includes real-time synchronization and batch synchronization, the data range is used to specify a business model in the application that needs data collaboration and limit the base side or organization range of source data, the filtering condition is set by using a conditional expression, and the mapping strategy indicates that complex data format mapping, field value calculation, condition judgment, and business rule encapsulation are realized by executing an expression written using AviatorScript and logic. The receiving end strategy includes: a receiving service definition, a data conflict strategy, a data backup strategy, and an abnormal running processing mode of data collaboration, wherein the receiving service definition is used to define the processing mode of data increase, deletion, modification, and query operation of the related business model of the application, the data conflict strategy is used to define the processing strategy when the source end data and the target end data of data collaboration exist primary key conflict, the data backup strategy is used to indicate creating a backup of the original data of the target end before data update, and the abnormal running processing mode is used to define the processing mode when an error occurs in the process of executing the data collaborative rule.

[0013] In an embodiment, the group side monitors and continuously optimizes each base side deployed application to realize comprehensive integration management of each base side on the group side, including: Business operation and monitoring: when each base side runs the deployed application, data exchange is performed between the group side and each base side according to the data collaborative rule of the deployed application, and the group side views the data flow state, application health degree, and system performance of each base side in real time through a unified monitoring panel, wherein the deployed application includes the application. Dynamic adjustment and optimization: according to business changes or monitoring insights, adjusting the data collaboration rules of the related applications or releasing new versions of the related applications on the group side, and synchronizing the data collaboration rules or new versions of the related applications to the related base sides, wherein the related applications are part or all of the deployed applications, and the related base sides are the base sides that deploy the related applications.

[0014] In a second aspect, the embodiments of the present application further provide a meta-model driven business system fusion management device, comprising: A communication unit is configured to establish stable data transmission channels between the group side and each base side, wherein the group side refers to a business fusion management platform of a group, the base side refers to a business system of a base, and the base refers to a subordinate base of the group. A model definition unit is configured to define business models of the group side and each base side based on a meta-model driven mechanism on the group side, generate a standardized meta-model library based on all the business models, and synchronize the meta-model definitions of the standardized meta-model library to each base side through the data transmission channels. An application collaboration unit is configured to distribute applications developed by the group side to a target base side through the data transmission channels, perform deployment and integration of the applications by the target base side using the standardized meta-model library, and report the deployment status of the applications to the group side in real time through the data transmission channels, wherein the target base side is one or more base sides among the base sides. A data collaboration unit is configured to configure data collaboration rules for the applications according to business requirements on the group side, and control data flow between the group side and the target base side when the target base side runs the applications based on the data collaboration rules. A fusion management unit is configured to monitor and continuously optimize the deployed applications of each base side on the group side to achieve comprehensive fusion management of each base side on the group side.

[0015] In a third aspect, the embodiments of the present application further provide an electronic device, which comprises a memory and a processor, the memory stores instructions, the instructions are loaded and executed by the processor to implement the method in any one of the embodiments of the above aspects, wherein the memory and the processor communicate with each other through an internal connection path.

[0016] In a fourth aspect, the embodiments of the present application further provide a computer readable storage medium, which stores a computer program, when the computer program runs on a computer, the method in any one of the embodiments of the above aspects is implemented.

[0017] The advantages or beneficial effects of the above technical solutions at least include: The application realizes the standardization of business elements through the meta-model driving technology, and organically combines the control force of the group side and the flexibility of the base side through the dual coordination mechanism of application and data, so as to realize the standardization, high efficiency and automation of unified control and cooperation of the group to the multi-base business system on the basis of respecting the existing heterogeneous system, and effectively solve the consistency, agility and reliability problems in the fusion of multi-base business systems of large group enterprises.

[0018] The application achieves the following beneficial effects: I. A high-dimensional and unified business semantic layer is constructed, laying a solid foundation for system intelligence and knowledge evolution Through the meta-model driving technology, a unified business semantic layer beyond specific implementation is constructed, which not only greatly improves the understandability and maintainability of the business model itself, but more importantly, this structured knowledge system enables the business data and its complex relationships to be deeply understood and processed by machines. Therefore, the business system can seamlessly and efficiently interface with advanced technologies such as artificial intelligence (AI) analysis and reasoning, knowledge graph construction, etc., providing an indispensable standardized data foundation for intelligent decision-making, business self-optimization and other high-level applications, and promoting the fundamental transition of the business system from traditional process automation to intelligence.

[0019] II. Real "configuration as development" is realized, greatly reducing the technical threshold and collaboration cost By providing a graphical business modeling and rule configuration interface, complex software development and integration work is transformed into intuitive business configuration activities, which enables business experts to directly participate in system construction and adjustment without the need for deep programming knowledge, greatly reducing the technical threshold of development and maintenance, and also revolutionizing the traditional "development-test-deployment" long-cycle mode, realizing rapid definition, immediate release and agile iteration of business, and significantly improving the collaboration efficiency between the group and the multi-base.

[0020] III. Extremely high engineering replication capability is realized, operation and maintenance are simple, and support for rapid business expansion Through standardized unified adapters and centralized management architecture, the deployment mode of each base is highly standardized. Once the deployment and verification are successfully completed in the first base, its configuration and experience can be used as a template and quickly replicated to all subsequent new bases in batches. This "one success, everywhere replication" mode makes the expansion of the system no longer dependent on repeated custom development, the engineering implementation efficiency is improved by orders of magnitude, the operation and maintenance complexity does not increase linearly with the number of bases, and can support the rapid business layout and merger and acquisition integration of the group with extremely low marginal cost.

[0021] The above summary is intended to illustrate only and is not intended to be limiting in any way. Further aspects, implementations, and features of the present application will be apparent to those skilled in the art upon consideration of the drawings and the following detailed description. BRIEF DESCRIPTION OF DRAWINGS

[0022] In the drawings, like reference numerals refer to same or similar components throughout the several views. The drawings are not necessarily to scale. It should be understood that the drawings only depict some embodiments in accordance with the disclosure and should not be considered limiting.

[0023] Figure 1 A flowchart of a business system fusion management method based on a meta-model driven provided by an embodiment of the present application; Figure 2 An example diagram of an inbound management interface provided by an embodiment of the present application; Figure 3 An example diagram of a scheme management interface provided by an embodiment of the present application; Figure 4 An example diagram of a rule detail viewing interface provided by an embodiment of the present application; Figure 5 An example diagram of a log detail interface provided by an embodiment of the present application; Figure 6 A structural block diagram of a business system fusion management apparatus based on a meta-model driven provided by an embodiment of the present application; Figure 7 A structural block diagram of an electronic device provided by an embodiment of the present application. DETAILED DESCRIPTION

[0024] In the following, only some exemplary embodiments are simply described. As those skilled in the art can recognize, the described embodiments can be modified in various different ways without departing from the spirit or scope of the present application. Therefore, the drawings and the description are considered to be exemplary in nature and not limiting.

[0025] In the related art, with the expansion of the group scale, the single factory deployment mode and the system island mode cannot adapt to the future multi-factory planning, and cannot support stable operation, business standardization, data standardization and operation and maintenance standardization of multi-factory.

[0026] Based on this, the present application establishes a unified standard through a group + multi-base super-convergence scheme to solve the core demands of cloud-edge collaboration such as efficient application collaboration and data collaboration, so as to be able to respect the existing heterogeneous systems, and realize the standardized, efficient and automated unified management and collaboration of the group to the multi-base business system.

[0027] In order to facilitate the understanding of the related technical solutions provided by the embodiments of the present application by those skilled in the art, the related terms involved in the present application will be explained accordingly.

[0028] Manufacturing Execution System (MES): an information system located between the upper plan management system and the bottom industrial control, responsible for managing, monitoring and executing production orders.

[0029] Warehouse Management System (WMS): a software system for managing personnel, inventory, space and equipment within the warehouse.

[0030] Quality Management System (QMS): a management system for standardizing and monitoring quality activities throughout the life cycle of a product.

[0031] Enterprise Service Bus (ESB): a traditional integration middleware that realizes service interaction and data integration between different application systems through a centralized bus structure.

[0032] Cloud-edge collaborative architecture: a distributed computing architecture, in which "cloud" represents a centralized group platform responsible for unified control and calculation, and "edge" represents a local system of each base responsible for real-time processing and execution. The two work together to achieve a balance between centralized management and distributed execution.

[0033] Meta-Model: an abstract definition of business objects (such as "equipment", "order", "process"), which describes the attributes, behaviors and mutual relationships of business objects, and is the unified semantic basis between the group and the multi-base.

[0034] Configuration data: including business rules and models defined in a structured format such as JSON (JavaScript Object Notation) that is easy to read and edit, generated by the group side and distributed to each base side, used to guide the behavior of the base side system.

[0035] Data contract: a standardized protocol for regulating all data interactions between the group side and the base side. In the present application, Avro protocol is used as a serialization tool to define the binary format of data transmission, ensuring the efficiency, compactness and cross-language compatibility of the interaction process.

[0036] Operation data: Real-time data generated by the business system during operation (such as device status, production quantity, etc.), collected by the base side and serialized according to the format defined by the Avro protocol and reported to the group side for monitoring and analysis.

[0037] WebSocket protocol: A full-duplex communication protocol based on TCP, providing an efficient and low-latency real-time data channel for the application.

[0038] Unified adapter: A standardized software component deployed on each base side, with built-in meta-model analysis and rule execution engine, responsible for parsing JSON configuration data issued by the group and interacting with local systems, while using Avro protocol for efficient data communication with the group side.

[0039] Graphical interface: A user interface that provides drag-and-drop and configuration-based operations, with the configuration results ultimately generated as JSON configuration data, greatly reducing the technical threshold for business modeling and rule definition, achieving the effect of "configuration as development".

[0040] Big data analysis: Based on the standardized operation data collected from each base side and efficiently transmitted by Avro protocol, global and deep data analysis and mining are performed on the group side to provide data support for strategic decision-making.

[0041] The related technical solutions provided by the embodiments of the application will be described in detail below with reference to the accompanying drawings.

[0042] Figure 1 A flowchart of a meta-model-driven business system integration management method according to an embodiment of the application is shown. As shown in Figure 1 The method can include the following steps: S110, Establish a stable data transmission channel between the group side and each base side.

[0043] In a specific implementation, the group side refers to the business integration management platform of the group, and the base side refers to the business system of the base, which refers to the subordinate base of the group.

[0044] In one embodiment, the implementation process of step S110 can include the following sub-steps: S111, Initialize network connection: Use the WebSocket protocol to establish a real-time transmission channel between the group side and each base side, and at the same time, use the HTTP protocol to establish a non-real-time transmission channel between the group side and each base side.

[0045] That is, the data transmission channel includes the real-time transmission channel and the non-real-time transmission channel.

[0046] In specific implementation, the real-time transmission channel can be used for real-time transmission of synchronous data, event notification and application issuing state monitoring, etc. The non-real-time transmission channel can be used for transmission of non-real-time or bulk data (such as application installation package, configuration data, etc.).

[0047] It can be understood that, in the embodiments of the present application, a persistent connection between the group side and each base side is established by using the WebSocket protocol to realize bidirectional real-time communication, and the HTTP protocol is used as a supplement for transmission of non-real-time or bulk data. That is, the WebSocket protocol is used for real-time communication, and the HTTP protocol is used for asynchronous request.

[0048] In the embodiments of the present application, by performing the sub-step S111, a communication foundation between the group side and each base side can be established to support real-time and asynchronous communication between the group side and each base side.

[0049] S112, authentication and security configuration: after the group side is connected with each base side, identity authentication is performed on each base side, and an encrypted channel is configured.

[0050] In specific implementation, a token mechanism can be used on the group side to perform identity authentication on each base side. The token mechanism can adopt an existing one, which will not be described herein again.

[0051] In specific implementation, the encrypted channel can be a TLS / SSL encrypted channel. The TLS / SSL encrypted channel refers to an encrypted communication link established between the group side and each base side by using the SSL / TLS protocol, which is used to protect the confidentiality and integrity of data transmission.

[0052] In the embodiments of the present application, by performing the sub-step S112, the safety of data transmission between the group side and each base side can be ensured to prevent malicious attacks.

[0053] S113, channel testing and maintenance: test the connection state between the group side and each base side, and automatically reconnect when the connection is interrupted.

[0054] In specific implementation, a heartbeat mechanism can be used to test the connection state between the group side and each base side. If it is detected that the connection between the group side and a base side is interrupted, the group side and the base side are automatically reconnected, for example, by using the real-time transmission channel and the non-real-time transmission channel to connect the group side and the base side.

[0055] As an example, taking the MES manufacturing operation platform as the group side, the group side can provide an inbound management interface as shown in Figure 2 for monitoring the connection state between the group side and each base side. In the interface, Figure 2The site name in the above table is the name of each base side.

[0056] In the embodiments of the present application, by performing the sub-step S113, stable connection between the group side and each base side can be ensured.

[0057] It should be understood that by performing the cooperation between the above-mentioned sub-steps S111-sub-step S113, a stable data transmission channel between the group side and each base side is generated.

[0058] That is, in the embodiments of the present application, by performing the step S110, the basic communication capability for all subsequent collaborative operations can be provided.

[0059] S120, defining the business models of the group side and each base side based on the meta-model driven mechanism at the group side, generating a standardized meta-model library based on all the business models, and synchronizing the meta-model definitions of the standardized meta-model library to each base side through the data transmission channel.

[0060] In one embodiment, the implementation process of step S120 can include the following sub-steps: S121, defining a meta-model structure: using an annotation method to describe the business services, business objects and their attribute data of the group side and each base side in the code at the group side, to obtain the business models of the group side and each base side.

[0061] In specific implementation, the business model can include a business object model and a business service model.

[0062] As an example, the core business objects (such as orders, inventories, etc.) of the group side and each base side can be marked respectively using the @Model annotation at the group side, and the model name and version of the core business objects are defined, and the attribute data (such as order ID, inventory quantity, etc.) of the core business objects are defined using the @Property annotation, and the data type (such as string, number, etc.) and constraint (such as uniqueness) of the attribute data are specified, to obtain the business object model of the group side and each base side.

[0063] As an example, the business services (such as order query service) of the group side and each base side can be defined using the @Service annotation at the group side, and the service interface and logic of the business services are described, to obtain the business service model of the group side and each base side.

[0064] In the embodiments of the present application, by performing the sub-step S121, the business data and business services of the group side and each base side can be abstracted into a describable meta-model, so as to facilitate unified data modeling and management.

[0065] S122, establishing a data relationship: describing the association relationship between all the business models using a relationship annotation at the group side.

[0066] As an example, the association relationship between all business models can be defined using @ManyToMany, @ManyToOne, OneToMany, etc. annotations on the group side, for example, a many-to-many relationship between the "order" business object model on the group side and the "inventory" business object model on the base side.

[0067] As an example, while describing the association relationship between all business models using relationship annotations, the association attribute can be specified. For example, the association attribute of the above many-to-many relationship can be specified as a foreign key.

[0068] In the embodiment of the present application, by performing sub-step S112, the association relationship between business models can be reasonably designed, and the business models on the group side and the base side can be efficiently and uniformly managed.

[0069] S123, generating a meta-model library: storing all business models defined by annotations into the group meta-model library to generate a standardized meta-model library.

[0070] In specific implementation, all business models defined by annotations can be stored into the group meta-model library by code scanning or configuration parsing to generate the standardized meta-model library.

[0071] In the embodiment of the present application, by performing sub-step S113, the standardized meta-model library can be used as a reusable business model template.

[0072] S124, synchronizing the meta-model: synchronizing the meta-model change notification of the standardized meta-model library to each base side through a data transmission channel.

[0073] As an example, the meta-model change notification of the standardized meta-model library can be pushed to each base side in real time through a real-time transmission channel in the data transmission channel to realize synchronization of the meta-model definition from the group side to each base side.

[0074] In the embodiment of the present application, by performing sub-step S124, the consistency between the group side meta-model and the base side meta-model can be ensured.

[0075] That is, in the embodiment of the present application, by performing step S120, the business data and business services on the group side and the base side can be abstracted into a describable meta-model, realizing unified data modeling and management, and through the standardized meta-model library, a unified data structure basis can be provided for subsequent application collaboration and data collaboration.

[0076] S130. The application developed on the group side is distributed to the target base side through the data transmission channel. The target base side uses the standardized meta-model library to perform the deployment and integration of the application, and reports the deployment status of the application to the group side in real time through the data transmission channel.

[0077] In practice, the target base side is one or more of the aforementioned base sides.

[0078] In one implementation, the real-time process of step S130 may include the following sub-steps: S131. Application Packaging and Launch: Package the application into an application installation package, associate the application installation package with the target business model, and launch the application on the group side.

[0079] In practical implementation, the target business model is the business model related to the application in the standardized meta-model library.

[0080] In practice, the application's backend components can be packaged into a JAR file, and the frontend components into a ZIP file to obtain the application's installation package.

[0081] In practice, the application can be listed in the group's application marketplace.

[0082] In this embodiment of the application, a complete application release version can be formed by executing sub-step S131.

[0083] S132. Application Distribution: Create an application collaboration scheme for the application on the group side, determine the base side specified in the application collaboration scheme as the target base side, and distribute the application installation package to the target base side through the data transmission channel.

[0084] In practical implementation, this application collaboration solution can specify the scope of the application collaboration base (such as which base(s) mentioned above) and the distribution strategy (such as immediate distribution or scheduled distribution). The target base can then be determined based on this scope.

[0085] As an example, the application installation package and its installation instructions can be sent to the target base via a non-real-time transmission channel in the data transmission channel.

[0086] In this embodiment of the application, by executing sub-step S132, the application developed on the group side can be securely and controllably deployed to the designated base side.

[0087] S133. Application Installation and Integration: The target base automatically installs the application based on the application installation package. During the installation process, the data compatibility of the application is verified using the target business model, and the integration of the application is completed.

[0088] In a specific implementation, when the target base side receives the application installation package and the installation instruction, the JAR package in the application installation package is deployed to the local running environment based on the installation instruction, and the ZIP package in the application installation package is decompressed and configured into the front-end static resource, thereby realizing the process of automatically executing the installation or update of the application on the target base side.

[0089] In a specific implementation, the integration work can include but is not limited to service registration.

[0090] In the embodiment of the present application, by executing the sub-step S133, the deployment and integration of the application on the target base side can be completed, and the business model of the application is ensured to be consistent with the base side environment, so that the target base side has new business capabilities, and provides an application carrier for subsequent data collaboration.

[0091] S134, state monitoring and feedback: the target base side reports the deployment state of the application to the group side in real time through the data transmission channel, and the application deployment state of each base side is displayed on the group side.

[0092] In a specific implementation, the target base side can report the deployment state of the application (such as "downloading", "installing", "success", "failure", and failure reason, etc.) to the group side through the real-time transmission channel in the data transmission channel.

[0093] In a specific implementation, the application deployment state of each base side can be displayed through the monitoring center of the group side.

[0094] As an example, taking the MES manufacturing operation platform on the group side as an example, the monitoring center of the group side can provide a scheme management interface as shown in Figure 3 for displaying the application deployment state between each base side.

[0095] In the embodiment of the present application, by executing the sub-step S134, a closed-loop management for all base sides can be formed on the group side.

[0096] That is, in the embodiment of the present application, by executing the step S130, the application developed on the group side can be safely and controllably distributed to the specified base side, and the automatic installation and state monitoring of the business are realized, thereby realizing the rapid deployment and unified management of the business.

[0097] S140, the data flow between the group side and the target base side is controlled based on the data collaboration rules configured by the group side for the application according to the business requirements.

[0098] In an implementation, the implementation process of the step S140 can include the following sub-steps: S141, rule definition: on the group side, configure the sending end policy and the receiving end policy for the business model involved in the application, to obtain the data collaboration rule.

[0099] In a specific implementation, the sending end policy is used to define the trigger condition and content of data push, and the receiving end policy is used to define the processing logic after data reception.

[0100] As an example, the sending end policy can include but is not limited to: synchronization mode, data range, filtering condition and mapping strategy of data collaboration. The synchronization mode includes real-time synchronization and batch synchronization, to support the sending end (base side or group side) to select real-time synchronization (triggered through the real-time transmission channel) or batch synchronization (executed at a fixed time through the non-real-time transmission channel) for data push. The data range is used to specify the business model in the application that needs data collaboration, and to limit the base side or organization range (which can be composed of several base sides) of the source data. The filtering condition is set by using a conditional expression (such as "only synchronize orders with a status of 'completed'"). The mapping strategy indicates that complex data format mapping, field value calculation, condition judgment and business rule encapsulation are implemented by executing expressions and logic written using AviatorScript, that is, AviatorScript script technology is integrated in the mapping strategy; the sending end can execute the mapping strategy through a built-in high-performance script engine, thus greatly enhancing the flexibility and dynamic capability of data processing, allowing users to implement complex business logic by writing simple scripts without the need to redeploy the code.

[0101] As an example, the receiving end strategy can include, but is not limited to, a receiving service definition of data collaboration, a data conflict strategy, a data backup strategy, and an abnormal operation processing mode. The receiving service definition is used to define the processing mode of the data add, delete, modify, and query operation of the related business model of the application, such as the data add, delete, modify, and query operation of the related business model of the application that has been issued, providing three processing modes of a native mode (directly performing a standard operation on the related business model), a derivative mode (performing business rules or calculation logic before and after the standard operation), and a custom service mode (completely processing the received data by a predefined@Service annotation to implement complex business logic). The data conflict strategy is used to define the processing strategy when the source data and the target data of the data collaboration exist primary key conflicts, including but not limited to a full coverage strategy (completely covering the target data with the source data), a same update strategy (only when the primary keys are the same, updating the target data with the source data), a same skip strategy (when the primary keys are the same, keeping the target data and skipping synchronization), and a same latest update strategy (comparing the time stamp or version number of the source data and the target data, and updating with the latest data). The data backup strategy is used to indicate creating a backup of the original data of the target end before data update, so as to facilitate error recovery and auditing. The abnormal operation processing mode is used to define the processing mode when an error occurs in the process of executing the data collaboration rule, including but not limited to an abnormal termination (stopping the current synchronization task immediately), an abnormal skip (recording the error and continuing to process subsequent data), and an abnormal rollback (rolling back the current transaction to ensure data consistency).

[0102] As an example, taking the MES manufacturing operation platform on the group side as an example, the group side can provide a rule detail viewing interface as shown in Figure 4 , which is used to support a user to view the set data collaboration rule.

[0103] In the embodiment of the present application, by executing the sub-step S141, the fine and complete data collaboration rule can be defined and configured according to the business demand for the application issued by the group side, so as to realize the strategy management of the sending end and the receiving end.

[0104] S142, rule publishing and taking effect: publishing the data collaboration rule to the target base side through the data transmission channel, loading the data collaboration rule to the local rule engine by the target base side, and making the data collaboration rule formally take effect.

[0105] In a specific implementation, the group side can publish the configured data collaboration rule execution action, such as publishing the data collaboration rule to the application collaboration formulated base side (i.e., the target base side) through a data transmission channel. After the target base side receives the data collaboration rule package, it parses and verifies it (such as checking whether the referenced business model exists), and loads it into the local rule engine to make the data collaboration rule officially effective.

[0106] In the embodiment of the application, by executing sub-step S142, the data collaboration rule can be activated to realize controllable data flow from end to end.

[0107] S143, rule running: the data collaboration rule is run in combination with the Kafka message queue and PowerJob, and a predefined DAG task flow is followed.

[0108] In a specific implementation, for rules in the data collaboration rule set to "real-time synchronization", the execution is triggered in real time by the Kafka message queue, that is, the real-time stream is processed by the Kafka message queue. For rules in the data collaboration rule set to "batch synchronization", the execution is scheduled by PowerJob (integrated in the target base side) in a distributed manner, that is, PowerJob manages the timing task scheduling. In a specific application, batch synchronization tasks can be triggered reliably by PowerJob according to a Cron expression or a fixed frequency, so that the task scheduling in a large-scale distributed environment can be handled, and the timely and stable operation of the task can be ensured.

[0109] In a specific implementation, whether it is real-time or timing task, the execution process follows a predefined DAG task flow and is executed in sequence.

[0110] It should be understood that the running of the data collaboration rule is the execution process of the data collaboration task, which can support the following two main modes: Inter-station collaboration: data reporting or issuing between the group side and the target base side; In-station collaboration: data flow between different business models or data sources within the group side or within the target base side.

[0111] In the embodiment of the application, by executing sub-step S143, the final consistency of data collaboration in a complex business scenario can be ensured.

[0112] S144, rule verification: a unified monitoring panel is provided on the group side, which displays the data flow state between the group side and the target base side in real time when the target base side runs the application, and supports users to view relevant data to verify whether the data collaboration rule is running as expected.

[0113] In implementation, the data flow status can include, but is not limited to, the status of data flow, the number of synchronization and the processing result. In implementation, the related data can include, but is not limited to, the synchronization log and the statistical data.

[0114] As an example, taking the MES manufacturing operation platform on the group side as an example, the unified monitoring panel provided by the group side can provide a log details interface as shown in the figure, which is used to support the user to view the synchronization log and the statistical data to verify whether the data collaboration rule is running as expected. Figure 5

[0115] In the embodiment of the present application, by executing the sub-step S144, the accuracy, consistency and reliability of data flow between the group side and the target base side can be ensured.

[0116] It should be understood that in step S140, the application deployed on the base side is the producer or consumer of data, and the business model of the base side is the structural basis of the data collaboration rule configuration.

[0117] That is, in the embodiment of the present application, by executing step S140, a set of refined and monitorable data collaboration rules can be generated and activated, realizing controllable data flow from end to end, and ensuring the accuracy, consistency and reliability of data flow between the group side and the base side.

[0118] S150, monitoring and continuously optimizing the deployed application on each base side to realize the overall integration management of each base side on the group side.

[0119] In an embodiment, the implementation process of step S150 can include the following sub-steps: S151, business operation and monitoring: when each base side runs the deployed application, data exchange is performed between the base side and the group side according to the data collaboration rule of the deployed application, and the group side views the data flow status, application health degree and system performance of each base side in real time through the unified monitoring panel.

[0120] It should be understood that the deployed application is an application developed and issued by the group side, including the above-mentioned application.

[0121] In the embodiment of the present application, by executing sub-step S151, the business operation of each base side can be monitored on the group side.

[0122] S152, dynamic adjustment and optimization: according to business changes or monitoring insights, the data collaboration rule of the related application or the new version of the related application is adjusted or released on the group side, and the change of the data collaboration rule or the new version of the related application is synchronized to the related base side.

[0123] ​It should be understood that the related application is part or all of the deployed application. The related base side is the base side in which the related application is deployed.

[0124] In the embodiment of the present application, by performing step S152, the deployed applications of each base side can be monitored and continuously optimized, the group side and each base side can be unified in business applications, business models, management processes and monitoring systems, a centralized management and distributed execution integrated business system is formed at the group side, and the purpose of realizing the comprehensive management of each base side at the group side is achieved.

[0125] That is, in the embodiment of the present application, by performing step S150, the data transmission channel in step S110 above is used as a lifeline, the business model in step S120 is used as a cornerstone, the application cooperation in step S130 is used as a functional carrier, and the data cooperation in step S140 is used as an operation context, and a set of efficient, reliable and scalable group + multi-base business system integrated management process is formed at the group side, realizing the agile deployment of applications, intelligent synchronization of data and standardized management of business.

[0126] That is, in the execution process of steps S110-S150 above, each step depends on the execution result of the previous step, realizing the process from establishing a basic connection to finally completing application cooperation and data synchronization.

[0127] In order to further facilitate the understanding of the meta-model driven business system integration management method provided in the present application (hereinafter referred to as the present scheme), the present scheme is compared with other existing schemes by Table 1 below.

[0128] Table 1

[0129] As can be seen from Table 1, compared with other existing schemes, the meta-model driven business system integration management method provided in the present scheme has a fundamental innovation from the architecture concept to the implementation path: by introducing the core design concept of meta-model driven, the management focus is moved from "connecting systems" to "defining business", thereby constructing a new generation of enterprise-level business integration management platform which is standardized, agile, decoupled, low-cost and unlimitedly expandable and inclusive of heterogeneous environments, effectively solving the core pain points of "not unified, not fine, not fast, not scalable" faced by large group enterprises in the process of digital transformation.

[0130] As can be known from the above description, the meta-model driven business system fusion management method provided in the embodiments of the present application establishes a stable data transmission channel between the group side and each base side, and first establishes a communication basis for the business system fusion management of each base; and defines the business models of the group side and each base side based on the meta-model driven mechanism on the group side, generates a standardized meta-model library based on all the business models, synchronizes the meta-model definitions of the standardized meta-model library to each base side through the data transmission channel, and unifies the data semantics of the business systems of each base; and the applications developed on the group side are distributed to the target base side through the data transmission channel, the target base side executes the deployment and integration of the applications by using the standardized meta-model library, and the deployment status of the applications is reported to the group side in real time through the data transmission channel, so that the unified deployment of business functions on the business systems of each base can be realized; and the data collaboration rules are configured for the applications according to the business requirements on the group side, and the data flow between the group side and the target base side when the target base side runs the applications is controlled based on the data collaboration rules, so that the unified configuration of data flow and control strategy on the business systems of each base can be realized; and the applications deployed on each base side are monitored and continuously optimized on the group side, so that the group side can comprehensively manage each base side, and the self-monitoring and continuous optimization of the business systems of each base can be achieved.

[0131] That is, the meta-model driven business system fusion management method provided in the embodiments of the present application realizes the standardization of business elements through the meta-model driven technology, and organically combines the control of the group side and the flexibility of the base side through the dual collaboration mechanism of applications and data, so that the group can realize the standardized, efficient and automatic unified control and collaboration of the multi-base business systems on the basis of respecting the existing heterogeneous systems, and effectively solves the consistency, agility and reliability problems in the fusion of the multi-base business systems of large groups.

[0132] In addition, the meta-model driven business system fusion management method provided in the embodiments of the present application significantly improves the automation level, processing capacity and implementation efficiency of the system by integrating the following four key technologies: (1) PowerJob distributed timing task scheduling technology: provides enterprise-level and highly available scheduling capabilities for batch data synchronization tasks of the system, ensures accurate and reliable execution of timing tasks, and meets the synchronization period requirements in different business scenarios.

[0133] (2) Kafka real-time streaming technology: as the transmission backbone of real-time data flow and control information in the system, its high throughput, low delay and persistence characteristics provide stable and reliable underlying support for real-time collaboration and large-scale data flow.

[0134] (Three), DAG task flow technology: through the directed acyclic graph to model and manage complex collaborative rules and processing flow, clear task execution path and dependency, is the core key to realize business process automation, order and eventual consistency.

[0135] (Four), AviatorScript script technology: embedded in the rule engine high-performance, lightweight expression evaluation engine, for data mapping, conversion and business logic encapsulation provides powerful flexibility and dynamic execution capability, so that complex business rules can be quickly implemented and iterated in a low-code way, greatly enhancing the adaptability and scalability of the system.

[0136] In summary, the meta-model driven business system fusion management method provided by the embodiments of the application has the following significant beneficial effects: I. A high-dimensional, unified business semantic layer is constructed, laying a solid foundation for system intelligence and knowledge evolution Through the meta-model driven technology, a unified business semantic layer beyond specific implementation is constructed, which not only greatly improves the understandability and maintainability of the business model itself, but more importantly, this structured knowledge system enables business data and its complex relationships to be deeply understood and processed by machines. Therefore, the business system can seamlessly and efficiently interface with advanced technologies such as artificial intelligence (AI) analysis and reasoning, knowledge graph construction, etc., providing an indispensable standardized data foundation for intelligent decision-making, business self-optimization, and other high-level applications, and promoting the fundamental transition of the business system from traditional process automation to intelligence.

[0137] II. Achieve true "configuration as development", greatly reduce the technical threshold and collaboration cost By providing a graphical business modeling and rule configuration interface, complex software development and integration work is transformed into intuitive business configuration activities, which enables business experts to directly participate in system construction and adjustment without the need for deep programming knowledge, greatly reducing the technical threshold for development and maintenance, and also revolutionizing the traditional "development-test-deployment" long-cycle mode, enabling rapid definition, immediate release and agile iteration of business, significantly improving the collaboration efficiency between groups and multi-base.

[0138] III. Achieve extreme engineering replication capability, easy operation and maintenance, support rapid expansion of business Through the standardized unified adapter and the centralized management architecture, the deployment mode of each base is highly standardized. Once the deployment and verification are successfully completed in the first base, the configuration and experience thereof can be used as a template and quickly and batch copied to all subsequent new bases. This "one success, everywhere replication" mode makes the expansion of the system no longer dependent on repeated customized development, the engineering implementation efficiency is improved by orders of magnitude, the operation and maintenance complexity does not increase linearly with the number of bases, and the rapid business layout and merger and acquisition integration of the group can be supported at a very low marginal cost.

[0139] Figure 6 A structural block diagram of a business system fusion management apparatus based on a meta-model driving according to an embodiment of the present application is shown. As shown in the figure, Figure 6 The apparatus can include: A communication unit 210 is configured to establish a stable data transmission channel between a group side and each base side, wherein the group side refers to a business fusion management platform of the group, the base side refers to a business system of the base, and the base refers to a subordinate base of the group; A model definition unit 220 is configured to define business models of the group side and each base side based on a meta-model driving mechanism at the group side, generate a standardized meta-model library based on all the business models, and synchronize the meta-models of the standardized meta-model library to each base side through the data transmission channel; An application collaboration unit 230 is configured to distribute an application developed at the group side to a target base side through the data transmission channel, perform deployment and integration of the application by the target base side using the standardized meta-model library, and report the deployment status of the application to the group side in real time through the data transmission channel, wherein the target base side is one or more of the base sides; A data collaboration unit 240 is configured to configure data collaboration rules for the application according to business requirements at the group side, and control the data flow between the group side and the target base side when the target base side runs the application based on the data collaboration rules; A fusion management unit 250 is configured to monitor and continuously optimize the deployed application at each base side at the group side, so as to realize the overall fusion management of each base side at the group side.

[0140] The functions of each unit in the business system fusion management apparatus based on the meta-model driving according to the embodiments of the present application can be referred to the corresponding description in the above method, which will not be repeated here.

[0141] Figure 7 A structural block diagram of an electronic device according to an embodiment of the present application is shown. As shown in the figure, Figure 7As shown, the electronic device includes a memory 310 and a processor 320, the memory 310 stores instructions, the instructions are loaded and executed by the processor 320 to realize the meta-model driven business system fusion management method in the above-mentioned embodiments. The number of the memory 310 and the processor 320 can be one or more.

[0142] The electronic device further includes: A communication interface 330 for communicating with external devices and transmitting data.

[0143] If the memory 310, the processor 320 and the communication interface 330 are independently implemented, the memory 310, the processor 320 and the communication interface 330 can be connected to each other through a bus and complete communication between each other. The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 7 Only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus.

[0144] Optionally, in specific implementation, if the memory 310, the processor 320 and the communication interface 330 are integrated on a chip, the memory 310, the processor 320 and the communication interface 330 can complete communication between each other through an internal interface.

[0145] The embodiment of the present application provides a computer readable storage medium, and the computer readable storage medium stores a computer program. When the computer program runs on a computer, the method provided in the embodiment of the present application is realized.

[0146] The embodiment of the present application further provides a chip, which includes a processor, and the processor is used to call and run instructions stored in a memory, so that a communication device installed with the chip executes the method provided in the embodiment of the present application.

[0147] The embodiment of the present application further provides a chip, which includes an input interface, an output interface, a processor and a memory, the input interface, the output interface, the processor and the memory are connected through an internal connection path, and the processor is used to execute code in the memory. When the code is executed, the processor is used to execute the method provided in the embodiment of the present application.

[0148] It is to be understood that the above-described processor can be a Central Processing Unit (CPU), a general-purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or the like. The general-purpose processor can be a microprocessor or any conventional processor, or the like. It is to be appreciated that the processor can be an Advanced RISC Machines (ARM) architecture processor.

[0149] Further, the memory can include a read-only memory and a random access memory, and can further include a non-volatile random access memory. The memory can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memory. The non-volatile memory can include a read-only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically EPROM (EEPROM), or a flash memory. The volatile memory can include a random access memory (RAM) used as an external cache. By way of example, and not limitation, many forms of RAM can be used. For example, a static RAM (SRAM), a dynamic RAM (DRAM), a synchronous DRAM (SDRAM), a double data rate synchronous DRAM (DDR SDRAM), an enhanced SDRAM (ESDRAM), a synchlink DRAM (SLDRAM), and a direct rambus RAM (DR RAM) can be used.

[0150] In the above-described embodiments, all or part can be implemented by software, hardware, firmware, or any combination thereof. When implemented by software, all or part can be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded on a computer, all or part generates a flow or function according to the present application. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another computer-readable storage medium.

[0151] In the description of the present specification, the description of the terms "one embodiment", "some embodiments", "an example", "a specific example", or "some examples" and the like means that the specific features, structures, materials or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of the present application. Also, the specific features, structures, materials or characteristics described can be combined in any appropriate manner in any one or more embodiments or examples. In addition, a person skilled in the art can combine and combine the different embodiments or examples described in the present specification and the features of the different embodiments or examples without contradiction.

[0152] In addition, the terms "first", "second", etc. are used only for the purpose of description and cannot be understood as indicating or implying relative importance or implicitly indicating the number of the technical features indicated. Therefore, the features defined with "first", "second" can explicitly or implicitly include at least one of the features. In the description of the present application, the meaning of "a plurality of" is two or more, unless otherwise explicitly specified.

[0153] Any process or method descriptions or descriptions in flow charts or otherwise described herein can be understood as representing code modules, segments, or portions of code that include one or more executable instructions for implementing specific logic functions or steps in the process. And the scope of the preferred embodiments of the present application includes additional implementation in which the functions can be performed in different order, including substantially concurrently or in reverse order, according to the functions involved.

[0154] The logic and / or steps represented in the flow chart or otherwise described herein, for example, can be considered as a list of executable instructions for implementing the logic function, which can be specifically implemented in any computer-readable medium for instruction execution system, device or equipment (such as computer-based system, system including processor or other system that can take instructions from instruction execution system, device or equipment and execute instructions) or in conjunction with these instructions execution system, device or equipment.

[0155] It should be understood that each part of the present application can be implemented by hardware, software, firmware or a combination thereof. In the above embodiments, a plurality of steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. All or part of the steps of the above-mentioned embodiment method can be completed by a program instructing the relevant hardware, which can be stored in a computer readable storage medium, and the program includes one of the steps of the method embodiment or a combination thereof when executed.

[0156] In addition, each functional unit in each embodiment of the present application can be integrated in one processing module, or each unit can be physically present separately, or two or more units can be integrated in one module. The above-mentioned integrated module can be realized in the form of hardware or in the form of a software functional module. The above-mentioned integrated module, if realized in the form of a software functional module and sold or used as an independent product, can also be stored in a computer readable storage medium. The storage medium can be a read-only memory, a magnetic disk or an optical disk, etc.

[0157] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of various changes or replacements within the technical scope disclosed in the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A meta-model driven business system fusion management method, characterized in that, The application comprises the following steps: establishing a stable data transmission channel between the group side and each base side, wherein the group side refers to the business integration management platform of the group, the base side refers to the business system of the base, and the base refers to the subordinate base of the group; defining the business models of the group side and each base side based on a meta-model driven mechanism at the group side, generating a standardized meta-model library based on all the business models, and synchronizing the meta-model definitions of the standardized meta-model library to each base side through the data transmission channel; downloading the application developed by the group side to the target base side through the data transmission channel, executing the deployment and integration of the application by the target base side using the standardized meta-model library, and reporting the deployment status of the application to the group side in real time through the data transmission channel, wherein the target base side is one or more base sides among the base sides; configuring data collaboration rules for the application according to business requirements at the group side, and controlling the data flow between the group side and the target base side when the target base side runs the application based on the data collaboration rules; monitoring and continuously optimizing the deployed applications of each base side at the group side to achieve comprehensive integration management of each base side at the group side.

2. The method of claim 1, wherein, The establishment of a stable data transmission channel between the group side and each base side comprises the following steps: initializing network connection: using the WebSocket protocol to establish a real-time transmission channel between the group side and each base side, and using the HTTP protocol to establish a non-real-time transmission channel between the group side and each base side; authentication and security configuration: after the group side is connected with each base side, identity authentication is performed on each base side, and an encrypted channel is configured; channel testing and maintenance: test the connection status between the group side and each base side, and automatically reconnect when the connection is interrupted.

3. The method of claim 1, wherein, Defining the business models of the group side and each base side based on a meta-model driven mechanism at the group side, generating a standardized meta-model library based on all the business models, and synchronizing the meta-model definitions of the standardized meta-model library to each base side through the data transmission channel comprises the following steps: defining the meta-model structure: using annotations to describe the business services, business objects and their attribute data of the group side and each base side in the code at the group side, obtaining the business models of the group side and each base side; establishing data relationships: describing the association relationships between all the business models using relationship annotations at the group side; generating a meta-model library: storing all the business models defined by annotations into the group meta-model library to generate the standardized meta-model library; synchronizing the meta-model: synchronizing the meta-model changes of the standardized meta-model library to each base side through the data transmission channel.

4. The method of claim 1, wherein, Downloading the application developed by the group side to the target base side through the data transmission channel, executing the deployment and integration of the application by the target base side using the standardized meta-model library, and reporting the deployment status of the application to the group side in real time through the data transmission channel comprises the following steps: Application packaging and shelving: packaging the application as an application installation package, associating the application installation package with a target business model related to the application in the standardized meta-model library, and shelving the application on the group side; Application distribution: creating an application collaboration scheme for the application on the group side, determining the base side specified in the application collaboration scheme as the target base side, and distributing the application installation package to the target base side through the data transmission channel; Application installation and integration: automatically installing the application by the target base side based on the application installation package, verifying the data compatibility of the application using the target business model during the installation process, and completing the integration of the application; Status monitoring and feedback: reporting the deployment status of the application to the group side in real time by the target base side through the data transmission channel, and displaying the application deployment status of each base side on the group side.

5. The method of claim 1, wherein, On the group side, data collaboration rules are configured for the application according to business requirements. Based on the data collaboration rules, the data flow between the group side and the target base side when the target base side runs the application includes: Rule definition: on the group side, for the business model involved in the application, configure the sending end strategy and the receiving end strategy to obtain the data collaboration rules, wherein the sending end strategy is used to define the trigger condition and content of data push, and the receiving end strategy is used to define the processing logic after data reception; Rule publishing and taking effect: publish the data collaboration rules to the target base side through the data transmission channel, load the data collaboration rules into the local rule engine by the target base side, and make the data collaboration rules officially effective; Rule running: combine Kafka message queue and PowerJob to run the data collaboration rules and follow the predefined DAG task flow; Rule verification: provide a unified monitoring panel on the group side, and display the data flow state between the group side and the target base side when the target base side runs the application in real time through the unified monitoring panel, support users to view related data to verify whether the data collaboration rules run as expected.

6. The method of claim 5, wherein, The sending end strategy includes: synchronization mode, data range, filtering condition and mapping strategy of data collaboration, wherein the synchronization mode includes real-time synchronization and batch synchronization, the data range is used to specify the business model in the application that needs data collaboration, and limit the base side or organization range of source data, the filtering condition is set by conditional expression, and the mapping strategy indicates that complex data format mapping, field value calculation, condition judgment and business rule encapsulation are realized by executing expressions and logic written using AviatorScript. The receiving end strategy includes: data coordination receiving service definition, data conflict strategy, data backup strategy and running exception handling mode, wherein the receiving service definition is used to define the processing mode of data increment, deletion, modification and query operation of the related business model of the application, the data conflict strategy is used to define the processing strategy when the source end data and the target end data of the data coordination exist primary key conflict, the data backup strategy is used to indicate creating backup for the original data of the target end before data update, and the running exception handling mode is used to define the processing mode when error occurs in the process of executing the data coordination rule.

7. The method according to any one of claims 1 to 6, characterized in that, The group side monitors and continuously optimizes the deployed applications of each base side to achieve the overall integrated management of each base side at the group side, including: Business operation and monitoring: when each base side runs the deployed applications, data exchange is performed between the group side and each base side according to the data coordination rules of the deployed applications, and the group side views the data flow state, application health degree and system performance of each base side in real time through a unified monitoring panel, wherein the deployed applications include the applications; Dynamic adjustment and optimization: according to business changes or monitoring insights, the data coordination rules of related applications are adjusted or new versions of the related applications are released at the group side, and the data coordination rules or new versions of the related applications are changed and synchronized to the related base sides, wherein the related applications are part or all of the deployed applications, and the related base sides are base sides that deploy the related applications.

8. A meta-model driven business system fusion management apparatus, characterized by comprising: It includes: A communication unit is configured to establish a stable data transmission channel between the group side and each base side, wherein the group side refers to a business integration management platform of a group, the base side refers to a business system of a base, and the base refers to a subordinate base of the group; A model definition unit is configured to define business models of the group side and each base side based on a meta-model driven mechanism at the group side, generate a standardized meta-model library based on all business models, and synchronize the meta-model definitions of the standardized meta-model library to each base side through the data transmission channel; An application coordination unit is configured to distribute an application developed by the group side to a target base side through the data transmission channel, perform deployment and integration of the application by the target base side using the standardized meta-model library, and report the deployment state of the application to the group side in real time through the data transmission channel, wherein the target base side is one or more base sides among the base sides; A data coordination unit is configured to configure data coordination rules for the application according to business requirements at the group side, control data flow between the group side and the target base side based on the data coordination rules when the target base side runs the application; An integrated management unit is configured to monitor and continuously optimize the deployed applications of each base side at the group side to achieve the overall integrated management of each base side at the group side.

9. An electronic device, comprising: It includes: a memory having instructions stored therein, the instructions being loaded and executed by a processor to implement the method of any of claims 1-7.

10. A computer-readable storage medium, characterized in that, The computer readable storage medium has stored therein a computer program which, when run on a computer, implements the method of any of claims 1-7.

Images