A method for connecting and synchronizing cloud data content in an industrial field

Abstract

A cloud data content docking and synchronization method in the industrial field belongs to the technical field of system data transmission docking. The data integration platform selects the interface call information of the upstream and downstream industrial systems for data content docking, and then parses the data content to be circulated in the upstream industrial system, and converts the data content into data content compatible with the downstream system according to the configured interface field conversion scheme, and then calls the interface call information of different downstream systems for data distribution, completes the data content docking and data content synchronization of the upstream and downstream industrial systems, and decouples the data content docking process and data content synchronization process of the upstream and downstream industrial systems for independent maintenance and upgrade. This solution extracts the same business attributes of the manufacturing industry, reconstructs the organization, process, mechanism, etc., realizes the rapid configuration of customers in different industries, builds a parallel open ecological platform, solves the data sharing problem between different systems, and improves the overall system efficiency.

Description

Technical Field

[0001] The present invention belongs to the technical field of system data transmission docking, and specifically relates to a cloud data content docking and synchronization method in the industrial field. Background Art

[0002] In the process of digital transformation and upgrading, manufacturing enterprises use various industrial systems through internal research and development or procurement to meet the different office and production activities of the enterprise. Industrial system is the abbreviation of "industrial application service system", which refers to a management platform based on information technology and systematic management ideas to provide enterprises with R&D design (such as simulation platform CAE), production and manufacturing (such as production scheduling platform APS), business management (such as office automation system OA, enterprise resource planning system ERP), or operation and maintenance services (such as production equipment maintenance management system TPM) and other management platforms related to factory production activities and with data docking needs.

[0003] For traditional solutions, it is difficult to achieve data interconnection between different industrial systems. In traditional solutions, data connection between industrial systems is done point-to-point. Figure 1 This is a schematic diagram of data connection between industrial systems in traditional solutions. Figure 1 As shown in the figure, industrial systems use a 1:1 data docking method. Financial software needs to be docked with the enterprise resource planning system ERP, the production information management system MES, and the office automation system OA separately; the product lifecycle management system PLM and the lathe industrial control system also need to be docked with other industrial systems separately. The docking code is coupled with the respective system code, and only the interaction between the upstream and downstream systems is considered at one time. If there is a scenario where system A is docked with multiple external systems, multiple sets of docking codes need to be maintained in system A. At the same time, since the docking codes are responsible for maintenance and upgrades in their respective systems, the system's interface resources and docking modules are difficult to manage and reuse in a unified manner. The coupling of flexible and changeable docking codes between systems and system business process codes poses a challenge to system stability, and the independent docking modules also make it difficult to uniformly manage system interface resources.

[0004] At the same time, for traditional solutions, it is difficult for newly added industrial systems to connect data with existing industrial systems. In traditional solutions, when a new industrial system is added, the data between the new industrial system and the existing industrial system needs to be connected because the new industrial system has data connection requirements. Typical business scenarios that have been put into use are as follows: SaaS software service providers always encounter the need to connect data with the original business system of the customer company during the software implementation process. For SaaS software service providers, the customer's business system is difficult to determine, and the data interfaces they provide are also in different forms. The traditional development model requires the software product manager and the user's account manager to communicate requirements, determine the personalized requirements for connection, sort out the documents and fields for connection between the two parties, output the connection requirements document, and hand over the document to the developer for development. After receiving the requirements, the developer needs to build a joint debugging environment, develop software code, perform joint debugging tests, and deploy it online. The entire connection process increases the difficulty of software implementation, which not only brings uncertainty to the final implementation progress and quality of the software, but also increases the cost of software procurement for customers.

[0005] Therefore, coordinated actions are needed between multiple industrial systems to truly realize the digital upgrade of manufacturing enterprises. Considering that the industrial systems provided by different software service providers have different forms of data openness, different definitions and usage of business documents, how to achieve data interconnection between different industrial systems, while also meeting the data docking needs of new industrial systems that may be added in the future, is the difficulty and pain point in the digital transformation and upgrade process of current manufacturing enterprises. Summary of the invention

[0006] In view of the current status and shortcomings of the above-mentioned prior art, an object of the present invention is to provide a cloud data content docking and synchronization method in the industrial field.

[0007] A method for connecting and synchronizing cloud data content in the industrial field, building a data integration platform on the cloud, wherein the data integration platform is signal-connected to a factory end where industrial systems are deployed and a cloud application layer;

[0008] The interface call information exposed by each industrial system is uniformly registered on the data integration platform; the data integration platform declares the upstream and downstream industrial systems and their interface call information that need data integration in each data integration task in the form of data integration tasks;

[0009] The data integration platform selects the interface call information of the upstream and downstream industrial systems for data content docking, then parses the data content to be circulated in the upstream industrial system, and converts the data content into data content compatible with the downstream system according to the configured interface field conversion scheme, and then calls the interface call information of different downstream systems for data distribution, completing the data content docking and data content synchronization of the upstream and downstream industrial systems, and decoupling the data content docking process and data content synchronization process of the upstream and downstream industrial systems for independent maintenance and upgrade.

[0010] The data integration platform is provided with connectors and converters;

[0011] The connector is configured with a docking template for the upstream and downstream industrial systems: according to the interface call information of the upstream and downstream industrial systems, it logs in and connects to the upstream and downstream systems, and obtains the data content returned by the upstream system;

[0012] The converter is configured with a data content conversion template of the upstream and downstream industrial systems: the data content of the upstream industrial system acquired by the connector is parsed, and the data content is converted into data content compatible with the downstream industrial system according to the interface field conversion scheme;

[0013] Each time data content is connected, the data integration platform calls the connector. The interaction of the upstream system is deposited in the data integration platform in the form of a connector. If there is a need to connect with the system later, the connector can be reused directly.

[0014] Every time the data content is converted, the data integration platform calls the converter. The interface field conversion solution required by the downstream system is deposited in the data integration platform in the form of a converter. If there is further data content conversion in the future, the converter will be reused directly.

[0015] A method for connecting and synchronizing cloud data content in an industrial field comprises the following steps:

[0016] Step S1, data integration preparation phase, including registration transactions of data transmission interface and registration transactions of data integration tasks;

[0017] Step S1a, data transmission interface registration transaction:

[0018] Step S1a1, tenant management: configure the tenant code of the data integration subject;

[0019] Step S1a2, management of industrial systems: declare the upstream and downstream industrial systems for data integration, and configure the account information of the industrial systems;

[0020] Step S1a3, management of interface call information: configure the interface call information of the upstream and downstream industrial systems; the interface call information includes the interface address information for acquiring data, the document information parsing field in the interface response, the interface response status field, and the interface response status value;

[0021] Step S1b, registration transaction of data integration task:

[0022] Step S1b1, configuration of data integration task: configure basic information of data integration task; select industrial system and interface call information under corresponding tenant according to data integration requirements; basic information of data integration task, including data integration task name and data integration task status;

[0023] Step S1b2, configuration of interface field conversion scheme: confirm the upstream and downstream industrial systems and interface call information according to the data integration requirements, and configure the interface field conversion scheme of the converter; the interface field conversion scheme includes the downstream system interface field list and field processing mode.

[0024] Further, in step S1b2, the field processing mode includes:

[0025] Field processing mode 1: Direct mapping, parsing the data content returned by the interface of the upstream industrial system according to the mapping relationship and directly assigning values;

[0026] Field processing mode 2: Enumeration mapping. When the upstream and downstream industrial systems use different enumerations to represent the same value, configure the enumeration definition mapping of both parties to convert the data enumeration of the upstream industrial system into the enumeration definition of the downstream industrial system.

[0027] Field processing mode 3: association mapping. When the real value in the association field of the document in the upstream industrial system needs to be translated, the type, code and name of the association field are configured, and the interface address of the translation primary key ID is queried based on the code or name.

[0028] Field processing mode 4: default value. When the downstream industrial system requires this field but the upstream industrial system does not define a field with this meaning, the default value is used to fill in the value of the field directly.

[0029] Furthermore, step S1b further includes:

[0030] Step S1b3, configuration of data integration task execution cycle plan: configure the data integration task execution cycle plan according to the real-time requirements of data integration; the time interval for executing the data integration task can be selected as month m, week w, day D or hour H, and the minimum granularity supports the hour H level;

[0031] Step S1b4, configuration of the compensation mechanism for the data integration task: according to the consistency requirements of the data content, configure the compensation mechanism for the data integration task, from low to high including: discard mode, limited retry mode, or infinite retry mode; discard mode, indicating that no processing is performed after the data integration task fails; limited retry mode, indicating that the maximum number of retries needs to be configured, and the data integration task is restarted in the compensation thread after the data integration task fails until the data integration task succeeds or the maximum number of retries is reached; infinite retry mode, the data integration task is retried continuously after failure until it succeeds.

[0032] Furthermore, a method for connecting and synchronizing cloud data content in an industrial field further includes the following steps:

[0033] Step S2, data integration execution phase;

[0034] Step S2a1, scheduling of data integration tasks: the data integration platform is provided with a task manager for triggering and scheduling data integration tasks; when a data integration task is scheduled, the data integration task execution cycle plan and the data integration task matching the current time are selected, and a work thread is created;

[0035] Then, the data integration platform is provided with a task executor for loading and executing the data integration task. The task executor loads the data integration task, configures and initializes various configuration information of the data integration task, including obtaining all configuration information configured in step S1 according to the unique primary key id of the data integration task;

[0036] Step S2a2, obtaining the configuration information required for docking the industrial system: the data integration platform is provided with a connector; the connector receives the task configuration information loaded by the task executor, obtains the account information of the upstream industrial system and the downstream industrial system for data transmission configured in step S1a2 according to the unique primary key ID of the data integration task, initializes the network access client of the upstream industrial system and the downstream industrial system, and then performs a pre-access to the upstream industrial system and the downstream industrial system, and checks whether the data transmission network is normal according to the response code returned by the network request: if the pre-access response request status code is 200, it means that the next step is passed; otherwise, it means that the request fails, and the result is returned and the log is recorded;

[0037] Step S2a3, obtaining login authority of the upstream industrial system and logging in: the connector integrates the interface call information of the upstream and downstream industrial systems according to the data configured in step S1a3, obtains the interface authority token of the calling interface and transmits it to the access client of the upstream industrial system, thereby logging in to the upstream industrial system; if the login is successful, proceed to the next step; if the login fails, return the result and record the log, and wait for the account information to be updated before restarting the task;

[0038] Step S2a4, calling the upstream interface call information and returning the data content: the connector calls the interface call information of the upstream industrial system, obtains the interface response status field and the interface response status value; analyzes the interface response status field, and processes the scheduling task according to the analysis result: if the interface response status value = the interface response status success value, the connector obtains the data content of the upstream industrial system, otherwise, returns the results respectively and records the log;

[0039] Step S2a5, data content conversion: the data integration platform is provided with a converter, which parses the data content of the upstream industrial system acquired by the connector, and converts the data content into data content compatible with the downstream industrial system according to the interface field conversion scheme;

[0040] Step S2a6, obtaining the login authority of the downstream industrial system to be adapted and logging in: the task executor, according to the interface address information of the downstream industrial system configured in step S1a3 to obtain data, logs in to the downstream industrial system to obtain the interface authority token for calling the interface and passes it to the access client of the downstream industrial system, thereby logging in to the downstream industrial system;

[0041] Step S2a7, call the interface address information of the downstream industrial system to be adapted for data distribution synchronization; the task executor executes the data content distribution synchronization task, parses and transforms the data content in step S2a5, calls the interface address information of the downstream system to complete data transmission, and determines whether the interface response is successful.

[0042] Further, in step S2a5,

[0043] According to the configured interface call information, obtain the document information from the document information parsing field in the interface response;

[0044] Convert and encapsulate the document information according to the configured interface field conversion scheme;

[0045] After selecting the upstream and downstream systems and interface call information, the converter automatically matches according to the information of the upstream and downstream interface fields. The matching rules are arranged from high to low in terms of priority as follows:

[0046] 1. The field encoding is the same;

[0047] 2. The Chinese names of the fields are the same;

[0048] 3. The configuration method selected in the field mapping library;

[0049] 4. The field types are the same;

[0050] After automatic matching of field mapping, fields with no mapping method set and some fields with incorrect mapping need manual intervention to correct.

[0051] Furthermore, a method for connecting and synchronizing cloud data content in an industrial field further includes the following steps:

[0052] Step S2b, the compensation transaction of the abnormal task, includes the following steps:

[0053] Step S2b1, the data integration platform is provided with a log manager; the log manager manages the task log responsible for recording the number of synchronizations; before the data content distribution synchronization task starts, the initial value of the number of synchronizations is 0; the status value of the data content distribution synchronization task is in progress, and the number of synchronizations is +1; if the data content distribution synchronization task is completed and the interface responds successfully, the status of the data content distribution synchronization task is recorded in the task log as completed; if the data content distribution synchronization task is completed and the interface responds unsuccessfully, the status of the data content distribution synchronization task is recorded in the task log as failed; if the data content distribution synchronization task is abnormal or not completed, the task log is not changed, and the status of the data content distribution synchronization task is still in progress;

[0054] Step S2b2, regularly start the data synchronization compensation thread, scan the task log, select the data content distribution synchronization task with the status value in progress, query whether the data content in the downstream system has been successfully synchronized, if successful, return the result and record it in the task log, if the data content is not successfully synchronized, return to step S2b1, and the data content distribution synchronization task enters the compensation task queue and waits for the task to start;

[0055] Step S2b3, regularly start the data synchronization compensation thread, scan the task log, select the data content distribution synchronization task with a failed status, return to step S2b1, and the data content distribution synchronization task directly enters the compensation task queue and waits for the task to start.

[0056] Furthermore, in step S2b2 and step S2b3, the judgment criteria for whether the compensation task queue restarts the task and the restart times are the data integration task compensation mechanism in the background management.

[0057] Furthermore, a cloud data content docking and synchronization method in the industrial field also includes the following steps: Step S2c, data integration upstream and downstream data consistency verification transaction: set an asynchronous thread, regularly query the interface call information of the upstream and downstream systems, obtain the data content of the documents in the upstream and downstream systems, and compare whether the data content of the documents in the upstream and downstream systems within the current synchronization time is consistent. If there is an inconsistency, jump to step S1a2 immediately.

[0058] This solution has the following advantages:

[0059] 1. The docking connectors and converters can be reused, reducing the cost of repeated development and improving efficiency.

[0060] 2. The data integration platform provides a unified operation platform and unified standards for data content docking, data content conversion, and data content distribution, minimizing the intrusion into the systems of both parties.

[0061] 3. Each operation is logged to ensure that the operation behavior is traceable and the data and operations can be traced, which increases the security of the system and data.

[0062] 4. Use system configuration to develop data connection, which reduces the implementation cost of software.

[0063] 5. Regarding how to confirm the data content to be circulated between the upstream and downstream industrial systems, this solution, when first connected, first converts and distributes the full data content to complete the first synchronization, and then performs data integration and upstream and downstream data consistency verification. For the newly modified data content during the operation of the industrial system, it is converted and distributed separately to maintain the consistency of the data content in the upstream and downstream industrial systems.

[0064] Therefore, this solution extracts the same business attributes of the manufacturing industry, reconstructs the organization, process, mechanism, etc., realizes the rapid configuration of customers in different industries, builds a parallel and open ecological platform, and provides a fast and convenient way for data integration between different industrial systems. It is suitable for scenarios where data needs to be connected with software services of multiple suppliers, solves the problem of data sharing between different systems, and improves the overall system efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0065] Figure 1 This is a schematic diagram of data connection between industrial systems in traditional solutions;

[0066] Figure 2 This is a docking diagram of the data integration platform of this solution;

[0067] Figure 3 It is a module diagram of the cloud integration platform;

[0068] Figure 4 This is a flow chart of this program. DETAILED DESCRIPTION

[0069] The present invention will be further described in detail below in conjunction with the accompanying drawings.

[0070] Meaning of terms:

[0071] Industrial system is the abbreviation of "industrial application service system". It refers to a management platform based on information technology and with a systematic management concept, which provides enterprises with R&D design (such as simulation platform CAE), production and manufacturing (such as production scheduling platform APS), business management (such as office automation system OA, enterprise resource planning system ERP), or operation and maintenance services (such as production equipment maintenance management system TPM) that are related to factory production activities and have data docking needs.

[0072] Data connection: Data connection is the transmission of data between different systems. Even if an isolated system has input a lot of data, its own role is limited. Only when it is associated with other systems and data is connected and transmitted between them can its real function and role be brought into play.

[0073] Figure 2 This is a schematic diagram of the connection of the data integration platform of this solution; Figure 2 As shown, this solution changes the traditional point-to-point docking mode between systems. By building a data integration platform, the data docking and integration work is unified to the data integration platform. At the same time, the interface call information exposed by each industrial system is uniformly registered to the cloud data integration platform. The data integration platform selects the interface call information for data content docking. The data content flow between upstream and downstream industrial systems is configured on the data integration platform. The data content docking process and the data content synchronization process of the industrial system are decoupled and independently maintained and upgraded. It can flexibly adapt to docking scenarios with different business needs, for example, the docking of 1 industrial system with N industrial systems, or the docking of N industrial systems with N industrial systems, where N is a natural number less than the total number of industrial systems.

[0074] Figure 3 It is a module diagram of the cloud data integration platform; Figure 3 As shown in the figure, a security firewall and data integration platform are built in the cloud.

[0075] The data integration platform is signal-connected to a factory side and a cloud application layer where industrial systems are deployed.

[0076] Since the industrial system is deployed in the cloud application layer, users no longer need to buy the industrial system and place it on their own server. They no longer need to go through a long installation and implementation cycle. As long as they register and pay, users can use the industrial system through self-configuration, saving users a lot of time and resources.

[0077] The data integration platform integrates a service engine unit responsible for unifying the data transmission interface and executing data integration tasks, and uniformly manages the industrial systems and interface call information that require data integration. It collects the document data content of the factory-side industrial system and / or the document data content of the cloud application layer industrial system through a unified data transmission interface, and transforms and distributes the data by executing data integration tasks, so as to achieve data consistency between upstream and downstream industrial systems and realize data synchronization between the factory-side industrial system and the cloud application layer industrial system.

[0078] The data integration platform includes a service engine unit and a background management unit;

[0079] The service engine module includes a running container, a task executor, a connector, and a converter. The task executor loads task configuration, synchronizes data connection, and compensates for abnormal tasks. The connector connects different industrial systems for different data integration scenarios, processes personalized industrial system connection processes, and returns data content after calling its data interface call information.

[0080] The converter processes the data content to meet the different data requirements of different target industrial systems, including data parsing and repackaging.

[0081] The background management unit includes a task manager, a connector manager, a converter manager, and a log manager.

[0082] The task manager is responsible for the initialization and startup of data integration tasks, including the task startup time, execution frequency, and failure compensation method.

[0083] The connector manager manages connectors in a unified manner, including docking account information, authentication method, interface path, and data format.

[0084] Converter manager, which manages converters in a unified manner, including the configuration of interface field conversion schemes.

[0085] The log manager records the entire life cycle of the scheduling task, providing a basis for the monitoring and compensation operations of subsequent abnormal tasks.

[0086] A method for connecting and synchronizing cloud data content in an industrial field comprises the following steps:

[0087] Step S1, data integration preparation phase, includes registration transactions of data transmission interface and registration transactions of data integration tasks.

[0088] Step S1a, registration transaction of the data transmission interface.

[0089] Step S1a1, tenant management: configure the tenant code of the data integration subject. The tenant is the subject of data integration. In the cloud-based industrial system, different data integration subjects need to be isolated to ensure the confidentiality of data and information.

[0090] Step S1a2, management of industrial systems: declare the upstream and downstream industrial systems for data integration, and configure the account information of the upstream and downstream industrial systems for data transmission. The account information includes the authorization code acquisition address, the system's public domain name (or IP), the login interface address, the login user name and password.

[0091] The authorization code acquisition address is divided into two modes: static authorization code acquisition address and dynamic authorization code acquisition address. When the industrial system to be connected is in static authorization code acquisition address mode, configure the docking system code, application id and application key app_secret; when the industrial system to be connected is in dynamic authorization code acquisition address mode, configure the docking system code and application id to obtain the interface address of the dynamic authorization key.

[0092] Step S1a3, management of interface call information: configure the interface call information of the upstream and downstream industrial systems; the interface call information includes the interface address information for acquiring data, the document information parsing field in the interface response, the interface response status field status, and the interface response status value resultData.status.

[0093] In this step, in order to achieve standardized reuse of data integration, the industrial systems and interface call information that require data integration are uniformly managed. When the 1:N or N:N docking scenario is subsequently implemented, the corresponding industrial system and interface call information can be directly selected to avoid repeated declaration of industrial system and interface call information.

[0094] Step S1b, registration transaction of data integration task:

[0095] In this method, when different industrial systems and interface call information are selected for data integration in different business scenarios, they are declared in the form of data integration tasks. In each data integration task, the industrial systems and interface call information of both parties of the data integration need to be selected. In the data integration task, the system and interface can be selected freely and flexibly, so as to achieve a data integration scenario that satisfies 1 (number of upstream industrial systems): N (number of downstream industrial systems, N is a natural number less than the total number of industrial systems) or N (number of upstream industrial systems): N (number of downstream industrial systems).

[0096] Step S1b1, configuration of data integration task: configure the basic information of data integration task; and select the industrial system and interface call information under the corresponding tenant according to the data integration requirements. The basic information of the data integration task includes the data integration task name and data integration task status. The industrial system has been configured in step S1a2. The interface call information has been configured in step S1a3.

[0097] Step S1b2, configuration of interface field conversion scheme: confirm the upstream and downstream industrial systems and interface call information according to the data integration requirements, and configure the interface field conversion scheme of the converter.

[0098] Interface field conversion scheme, including downstream system interface field list and field processing mode.

[0099] Field processing modes, including:

[0100] Field processing mode 1: Direct mapping, parsing the data content returned by the interface of the upstream industrial system according to the mapping relationship and directly assigning values.

[0101] Field processing mode 2: Enumeration mapping. When the upstream and downstream industrial systems use different enumerations to represent values ​​with the same meaning, configure the enumeration definition mapping of both parties to convert the data enumeration of the upstream industrial system into the enumeration definition of the downstream industrial system.

[0102] Field processing mode 3: association mapping. When the real value in the association field of the document in the upstream industrial system needs to be translated, configure the type, code and name of the association field, and query the interface address of the translation primary key id based on the code or name.

[0103] Field processing mode 4: default value. When the downstream industrial system requires this field but the upstream industrial system does not define a field with this meaning, the default value is used to fill in the value of the field directly.

[0104] Step S1b3, configuration of a data integration task execution cycle plan: configuring a data integration task execution cycle plan according to the real-time requirements of data integration;

[0105] For the periodic plan, select the time interval for executing the data integration task. You can select month m (1-12), week w (1-7), day D (1-31L), or hour H (0-23). ​​The minimum granularity supported is the hour H level. The trigger mechanism of the data integration task is executed according to the periodic plan.

[0106] The month m configuration item of the time interval for executing the task indicates that the month for executing the task is configured based on the month dimension. If you need to select multiple months, you can select multiple months separated by English commas. For example, if the monthly m configuration value is 3,6,9,12, it means that the task needs to be executed in March, June, September and December.

[0107] The week w configuration item of the time interval for executing tasks indicates the days of the week when the tasks are to be executed. If you need to select multiple items, you can select multiple items separated by commas. For example, if the week w configuration value is 6,7, it means that the task needs to be executed on Saturday and Sunday of the current week.

[0108] The D configuration item of the time interval for executing tasks indicates the number of days in the month for executing tasks. If you need to select multiple items, you can select multiple items and separate them with English commas. The letter L is used when the number of days in a month is not fixed and the end of the month is selected for execution. For example, a data integration task needs to be configured to be executed at the end of each month. The days of the month are 28, 29, 30, and 31, which cannot be unified. In this case, you can configure D=1L to indicate execution on the last day of each month.

[0109] The hour H configuration item of the time interval for executing tasks indicates that the time of the day for executing tasks is configured in hours. If you need to select multiple items, you can use English commas to separate them.

[0110] Step S1b4, configuration of compensation mechanism for data integration tasks: configuring compensation mechanism for data integration tasks.

[0111] The compensation mechanism of the data integration task includes: discard mode, limited retry mode, or infinite retry mode. Discard mode means that no processing is performed after the data integration task fails. Limited retry mode means that the maximum number of retries needs to be configured. After the data integration task fails, the data integration task is restarted in the compensation thread until the data integration task succeeds or the maximum number of retries is reached. Infinite retry mode, for the data content with the highest consistency, the data integration task will be retried until it succeeds after failure.

[0112] Step S2, data integration execution phase, includes data integration task execution transactions, abnormal task compensation transactions, and data integration upstream and downstream data consistency verification transactions.

[0113] Step S2a, execution transaction of the data integration task.

[0114] Step S2a1, scheduling of data integration tasks: the data integration platform is provided with a task manager for triggering and scheduling data integration tasks; when a data integration task is scheduled, the data integration task execution cycle plan and the data integration task matching the current time are selected, and a work thread is created;

[0115] Then, the data integration platform is provided with a task executor for loading and executing the data integration task. The task executor loads the data integration task, configures and initializes various configuration information of the data integration task, including obtaining all configuration information configured in step S1 according to the unique primary key id of the data integration task.

[0116] Step S2a2, obtaining the configuration information required for docking with the industrial system: the data integration platform is provided with a connector; the connector accepts the task configuration information loaded by the task executor, obtains the account information of the upstream industrial system and the downstream industrial system of the data transmission configured in step S1a2 according to the unique primary key id of the data integration task, initializes the network access client of the upstream industrial system and the downstream industrial system, and then performs a pre-access to the upstream industrial system and the downstream industrial system, and checks whether the data transmission network is normal according to the response code returned by the network request: if the pre-access response request status code is 200, it means that the next step is passed; otherwise, it means that the request failed, and the result is returned and the log is recorded.

[0117] Step S2a3, obtain the login permission of the upstream industrial system and log in: the connector integrates the interface call information of the upstream and downstream industrial systems according to the data configured in step S1a3, obtains the interface permission token of the calling interface and passes it to the access client of the upstream industrial system, thereby logging in to the upstream industrial system; if the login is successful, proceed to the next step; if the login fails, return the result and record the log, and wait for the account information to be updated before restarting the task.

[0118] Step S2a4, call the upstream interface call information and return the data content: the connector calls the interface call information of the upstream industrial system, obtains the interface response status field status, the interface response status value resultData.status; analyzes the interface response status field status, and processes the scheduling task according to the analysis result: if the interface response status value resultData.status = the interface response status success value "success", the connector obtains the data content of the upstream industrial system, otherwise, returns the results separately and records the log.

[0119] Step S2a5, data content conversion: the data integration platform is provided with a converter, which parses the data content of the upstream industrial system acquired by the connector, and converts the data content into data content compatible with the downstream industrial system according to the interface field conversion scheme.

[0120] According to the interface call information configured in step S1a3, the document information resultData.data is obtained from the document information parsing field in the interface response.

[0121] According to the interface field conversion scheme configured in step S1b2, the document information resultData.data is converted and encapsulated.

[0122] The following is a list of examples of field processing modes for connecting upstream and downstream. In Tables 1 to 4, columns 1 and 2 are lists of downstream system interface fields, columns 4 and 5 are lists of upstream system interface fields, and column 3 is the field processing mode of upstream and downstream fields.

[0123] Table 1. Field processing table of material data

[0124]

[0125] Table 2. Field processing table for purchase order data

[0126]

[0127] Table 3. Field processing table of production order data

[0128]

[0129] Table 4. Field processing table of sales order data

[0130]

[0131] In Tables 1 to 4, the upstream and downstream systems are compared for field names. If they are identical, partially identical, or related synonyms, direct mapping can be used. If the upstream and downstream industrial systems use different enumerations to represent values ​​with the same meaning, enumeration mapping is used. If the attributes are interrelated, associative mapping is used. If one side is undefined, the default value is used.

[0132] There are four types of field processing modes, namely direct mapping, enumeration mapping, association mapping and default value. When the downstream system field processing mode is direct mapping, the value of this field is directly taken from the value of the upstream system field in the same row (i.e., column 4 of Table 1 to Table 4). When the downstream system field processing mode is enumeration mapping, the value of this field is obtained by direct mapping and then converted through enumeration mapping. When the downstream system field processing mode is association mapping, the value of this field is first obtained by directly mapping the field value of the upstream system, and then the primary key id corresponding to the value is queried according to the configured interface address. When the downstream system field processing mode is default value, this field directly takes the configured value, such as enableMto=1.

[0133] After selecting the upstream and downstream industrial systems and interface call information, the converter automatically matches according to the information of the upstream and downstream interface fields. The matching rules are arranged from high to low in terms of priority as follows:

[0134] 1. The field encoding is the same;

[0135] 2. The Chinese names of the fields are the same;

[0136] 3. The configuration method selected in the field mapping library (template for built-in field mapping tables);

[0137] 4. The field types are the same;

[0138] After automatic matching of field mapping, fields that have not been mapped and some fields that are incorrectly mapped need to be corrected through manual intervention.

[0139] Step S2a6, obtain the login authority of the downstream industrial system to be adapted and log in: the task executor, according to the interface address information of the downstream industrial system configured in step S1a3 to obtain data, logs in to the downstream industrial system to obtain the interface authority token for calling the interface and passes it to the access client of the downstream industrial system, thereby logging in to the downstream industrial system;

[0140] Step S2a7, call the interface address information of the downstream industrial system to be adapted for data distribution synchronization; the task executor executes the data content distribution synchronization task, parses and transforms the data content in step S2a5, calls the interface address information of the downstream system to complete data transmission, and determines whether the interface response is successful.

[0141] Step S2b, the compensation transaction of the abnormal task, includes the following steps:

[0142] Step S2b1, the data integration platform is provided with a log manager; the log manager manages the task log responsible for recording the number of synchronizations; before the data content distribution synchronization task starts, the initial value of the number of synchronizations is 0; the status value of the data content distribution synchronization task is in progress, and the number of synchronizations is +1; if the data content distribution synchronization task is completed and the interface responds successfully, the status of the data content distribution synchronization task is recorded in the task log as completed; if the data content distribution synchronization task is completed and the interface responds unsuccessfully, the status of the data content distribution synchronization task is recorded in the task log as failed; if the data content distribution synchronization task is abnormal or not completed, the task log is not changed, and the status of the data content distribution synchronization task is still set to in progress.

[0143] Step S2b2, regularly start the data synchronization compensation thread, scan the task log, select the data content distribution synchronization task with a status value of ongoing, and query whether the data content in the downstream system has been synchronized successfully. If successful, return the result and record it in the task log. If the data content is not synchronized successfully, return to step S2b1, and the data content distribution synchronization task enters the compensation task queue and waits for the task to start.

[0144] Step S2b3, regularly start the data synchronization compensation thread, scan the task log, select the data content distribution synchronization task with a failed status, return to step S2b1, and the data content distribution synchronization task directly enters the compensation task queue and waits for the task to start.

[0145] In step S2b2 and step S2b3, the judgment criteria for whether the compensation task queue restarts the task and the restart times are the data integration task compensation mechanism in the background management; the data integration task compensation mechanism has been configured in step S1b4.

[0146] Step S2c: Data integration upstream and downstream data consistency verification transaction.

[0147] In order to ensure the consistency of upstream and downstream data content, an asynchronous thread is set to regularly query the interface call information of the upstream and downstream systems, obtain the data content of the documents in the upstream and downstream systems, and compare whether the data content of the documents in the upstream and downstream systems within the current synchronization time is consistent. If there is any inconsistency, jump to step S1a2 immediately.

[0148] This solution provides a fast and convenient way for system data integration. After adopting this method, the interaction of the upstream system is deposited in the data integration platform in the form of a connector. If there is a need to connect with the system in the future, the connector can be directly reused to interact with it in a configured manner. The conversion scheme for the mapping required for the document input of the downstream system is saved in the system in the form of a converter. The document input of the system can be directly processed by this solution in the future.

[0149] The traditional method of data docking requires writing customized code each time to meet personalized needs, which is invasive to the original system and will have a certain impact on the stability and security of the original system. This method uses the converter configuration method to convert personalized needs into field configuration mapping. At the same time, each docking requires the intervention of the development process, which will affect the efficiency of software implementation and increase the customer's software procurement cost. This method uses the connector and converter sedimentation method to allow connectors and converters to be reused and reduce the development burden.

[0150] This method is suitable for scenarios where data integration with systems of different service providers is required. It solves the data sharing problem between different systems, reduces the cost of docking between systems, and improves the overall system efficiency.

[0151] Common scenario: Data integration and docking are required between factory local software A and cloud software B.

[0152] For ease of explanation, the configuration items involved in this case are displayed in a table. In actual use, they are completed on the system's backend management page.

[0153] Data integration completes the following docking tasks:

[0154] 1. Synchronize document a from the factory's local industrial system A to the cloud-based industrial system B.

[0155] 2. Push document b from cloud-based industrial system B to the factory's local industrial system A.

[0156] Example analysis:

[0157] Example 1: Synchronize materials in the factory-side ERP software to the cloud-based MES system. Data integration tasks require prefabricated connectors for docking systems and converters for data mapping.

[0158] Step 1.1, configure the information of the ERP system.

[0159] Table 5. Information table of ERP system

[0160]

[0161] Step 1.2, configure the software information of the MES system.

[0162] Table 6. Information table of MES system

[0163]

[0164] Step 1.3, configure the interface call information of the data source interface.

[0165] Table 7. Information table of interface call information of data source interface

[0166]

[0167] Step 1.4, configure the interface call information of the target data interface.

[0168] Table 8. Information table of interface call information of target data interface

[0169]

[0170] Step 1.5, configure the interface field conversion scheme.

[0171] Table 9. Information table of interface field conversion scheme

[0172]

[0173] Step 1.6, configure the data integration task compensation mechanism.

[0174] Table 10. Information table of data integration task compensation mechanism

[0175]

[0176] Step 1.7, actively trigger the data integration task and execute it.

[0177] The ERP system data results are as follows: In order to briefly explain the data transfer process, the following data case only gives some key fields of the document

[0178] {

[0179] "status":"success",

[0180] "data": {

[0181] "allcount": 2,

[0182] "retcount": 1,

[0183] "datas":[

[0184] {

[0185] "parentvo": {

[0186] "invcode": "010102",

[0187] "invname": "Seamless Steel Pipe 0125",

[0188] "invspec": "1*6",

[0189] "invclcode": "0101",

[0190] "invclname": "Finished Product"

[0191] },

[0192] "childrenvo": [

[0193] {

[0194] "meascode": "05",

[0195] "measname": "tons",

[0196] "fixedflag": true,

[0197] "mainmeasrate": 6

[0198] } ]

[0200] } ]

[0202] }

[0203] }

[0204] After data mapping, the cloud MES system interface input parameters are as follows:

[0205] . {

[0206] "materials": [

[0207] {

[0208] "enableBatch": 0,

[0209] "enableFifo": 0,

[0210] "enableMto": 1,

[0211] "materialCode": "010102",

[0212] "materialName": "Seamless Steel Pipe 0125",

[0213] "materialTypeId": 1110001,

[0214] "unitGroupId": 1100001,

[0215] "unitId": 1120001,

[0216] "useStatus": 1

[0217] } ]

[0219] }

[0220] This example briefly describes the whole process of using this solution configuration to synchronize the data of the industrial system on the factory side with the industrial system on the cloud side.

[0221] The method of precipitating system docking connectors and converters mentioned in this solution is to extract the system connection and personalized data assignment process in the traditional system docking process as a docking template prefabricated in the system, and use the background configuration input method to shield the personalized difference part for the uncertain part of the docking process or the part that changes with the docking scenario.

[0222] It is understandable that those skilled in the art can make equivalent substitutions or changes based on the technical solution and inventive concept of the present invention, and all these changes or substitutions should fall within the protection scope of the claims attached to the present invention.

Claims

1. A method for connecting and synchronizing cloud data content in an industrial field, characterized in that: Building a data integration platform in the cloud, wherein the data integration platform is connected to a factory end where industrial systems are deployed and a cloud application layer; the data integration platform is provided with connectors and converters; The data integration platform selects the interface call information of the upstream and downstream industrial systems for data content docking, then parses the data content to be circulated in the upstream industrial system, and converts the data content into data content compatible with the downstream system according to the configured interface field conversion scheme, and then calls the interface call information of different downstream systems for data distribution, completing the data content docking and data content synchronization of the upstream and downstream industrial systems, and decoupling the data content docking process and data content synchronization process of the upstream and downstream industrial systems for independent maintenance and upgrade; The method comprises the following steps: Step S1, data integration preparation stage: the interface call information exposed by each industrial system is uniformly registered on the data integration platform; the data integration platform declares the upstream and downstream industrial systems and their interface call information that need data integration in each data integration task in the form of data integration tasks; this step includes the registration transaction of the data transmission interface and the registration transaction of the data integration task; Step S2, data integration execution phase; Step S2a1, scheduling of data integration tasks: the data integration platform is provided with a task executor for loading and executing data integration tasks; Step S2a2, obtaining the configuration information required for docking the industrial system: Step S2a3, obtaining the login authority of the upstream industrial system and logging in; Step S2a4, calling the upstream interface call information and returning the data content: the connector calls the interface call information of the upstream industrial system, obtains the interface response status field and the interface response status value; analyzes the interface response status field, and processes the scheduling task according to the analysis result: if the interface response status value = the interface response status success value, the connector obtains the data content of the upstream industrial system, otherwise, returns the results respectively and records the log; Step S2a5, data content conversion: the converter parses the data content of the upstream industrial system acquired by the connector, and converts the data content into data content compatible with the downstream industrial system according to the interface field conversion scheme; Step S2a6, obtaining the login authority of the downstream industrial system to be adapted and logging in: the task executor, according to the configured interface address information of the downstream industrial system for acquiring data, logs in to the downstream industrial system to obtain the interface authority token for calling the interface and passes it to the access client of the downstream industrial system, thereby logging in to the downstream industrial system; Step S2a7, call the interface address information of the downstream industrial system to be adapted for data distribution synchronization; the task executor executes the data content distribution synchronization task, parses and transforms the data content, calls the interface address information of the downstream system to complete the data transmission, and determines whether the interface response is successful.

2. The method for connecting and synchronizing cloud data content in an industrial field according to claim 1, characterized in that: The connector is configured with a docking template for the upstream and downstream industrial systems: according to the interface call information of the upstream and downstream industrial systems, it logs in and connects to the upstream and downstream systems, and obtains the data content returned by the upstream system; The converter is configured with a data content conversion template of the upstream and downstream industrial systems: the data content of the upstream industrial system acquired by the connector is parsed, and the data content is converted into data content compatible with the downstream industrial system according to the interface field conversion scheme; Each time data content is connected, the data integration platform calls the connector. The interaction of the upstream system is deposited in the data integration platform in the form of a connector. If there is a need to connect with the system later, the connector can be reused directly. Every time the data content is converted, the data integration platform calls the converter. The interface field conversion solution required by the downstream system is deposited in the data integration platform in the form of a converter. If there is further data content conversion in the future, the converter will be reused directly.

3. A method for connecting and synchronizing cloud data content in an industrial field according to claim 1 or 2, characterized in that: Step S1, comprising: Step S1a, data transmission interface registration transaction: Step S1a1, tenant management: configure the tenant code of the data integration subject; Step S1a2, management of industrial systems: declare the upstream and downstream industrial systems for data integration, and configure the account information of the industrial systems; Step S1a3, management of interface call information: configuring interface call information of upstream and downstream industrial systems; The interface call information includes the interface address information for acquiring data, the document information parsing field in the interface response, the interface response status field, and the interface response status value; Step S1b, registration transaction of data integration task: Step S1b1, configuration of data integration task: configure basic information of data integration task; select industrial system and interface call information under corresponding tenant according to data integration requirements; basic information of data integration task, including data integration task name and data integration task status; Step S1b2, configuration of interface field conversion scheme: confirm the upstream and downstream industrial systems and interface call information according to the data integration requirements, and configure the interface field conversion scheme of the converter; the interface field conversion scheme includes the downstream system interface field list and field processing mode.

4. The method for connecting and synchronizing cloud data content in an industrial field according to claim 3, characterized in that: In step S1b2, the field processing modes include: field processing mode 1: direct mapping, directly assigning values ​​to the data content returned by the interface of the upstream industrial system according to the mapping relationship; Field processing mode 2: Enumeration mapping. When the upstream and downstream industrial systems use different enumerations to represent the same value, configure the enumeration definition mapping of both parties to convert the data enumeration of the upstream industrial system into the enumeration definition of the downstream industrial system. Field processing mode 3: association mapping. When the real value in the association field of the document in the upstream industrial system needs to be translated, the type, code and name of the association field are configured, and the interface address of the translation primary key ID is queried based on the code or name. Field processing mode 4: default value. When the downstream industrial system requires this field but the upstream industrial system does not define a field with this meaning, the default value is used to fill in the value of the field directly.

5. The method for connecting and synchronizing cloud data content in an industrial field according to claim 3, characterized in that: Step S1b further includes: Step S1b3, configuration of data integration task execution cycle plan: configure the data integration task execution cycle plan according to the real-time requirements of data integration; the time interval for executing the data integration task can be selected as month m, week w, day D or hour H, and the minimum granularity supports the hour H level; Step S1b4, configuration of the compensation mechanism for data integration tasks: according to the consistency requirements of the data content, configure the compensation mechanism for the data integration tasks, from low to high, including: discard mode, limited retry mode and infinite retry mode; discard mode, indicating that no processing is performed after the data integration task fails; limited retry mode, indicating that the maximum number of retries needs to be configured, and the data integration task is restarted in the compensation thread after the data integration task fails until the data integration task succeeds or the maximum number of retries is reached; infinite retry mode, the data integration task is retried continuously after failure until it succeeds.

6. The method for connecting and synchronizing cloud data content in an industrial field according to claim 3, characterized in that: In step S2a1, the data integration platform is provided with a task manager for triggering and scheduling data integration tasks; when a data integration task is scheduled, the data integration task execution cycle plan and the data integration task matching the current time are selected, and a work thread is created; Then, the task executor loads the data integration task, configures and initializes various configuration information of the data integration task, including obtaining all configuration information configured in step S1 according to the unique primary key id of the data integration task; In step S2a2, the connector accepts the task configuration information loaded by the task executor, obtains the account information of the upstream industrial system and the downstream industrial system of the data transmission configured in step S1a2 according to the unique primary key ID of the data integration task, initializes the network access client of the upstream industrial system and the downstream industrial system, and then performs a pre-access to the upstream industrial system and the downstream industrial system, and checks whether the data transmission network is normal according to the response code returned by the network request: if the pre-access response request status code is 200, it means that the next step is passed; otherwise, it means that the request fails, and the result is returned and the log is recorded; In step S2a3, the connector integrates the interface call information of the upstream and downstream industrial systems according to the data configured in step S1a3, obtains the interface authority token of the calling interface and transmits it to the access client of the upstream industrial system, thereby logging in to the upstream industrial system; if the login is successful, proceed to the next step; if the login fails, return the result and record the log, and wait for the account information to be updated before restarting the task.

7. The method for connecting and synchronizing cloud data content in an industrial field according to claim 6, characterized in that: In step S2a5, according to the configured interface call information, the document information is obtained from the document information parsing field in the interface response; Convert and encapsulate the document information according to the configured interface field conversion scheme; After selecting the upstream and downstream systems and interface call information, the converter automatically matches according to the information of the upstream and downstream interface fields. The matching rules are arranged from high to low in terms of priority as follows: 1) The field encoding is the same; 2) The Chinese names of the fields are the same; 3) The configuration method selected in the field mapping library; 4) The field types are the same; After automatic matching of field mapping, fields with no mapping method set and some fields with incorrect mapping need manual intervention to correct.

8. The method for connecting and synchronizing cloud data content in an industrial field according to claim 6, characterized in that: The following steps are also included: Step S2b, compensation transaction for abnormal task: Step S2b1, the data integration platform is provided with a log manager; the log manager manages the task log responsible for recording the number of synchronizations; before the data content distribution synchronization task starts, the initial value of the number of synchronizations is 0; the status value of the data content distribution synchronization task is in progress, and the number of synchronizations is +1; if the data content distribution synchronization task is completed and the interface responds successfully, the status of the data content distribution synchronization task is recorded in the task log as completed; if the data content distribution synchronization task is completed and the interface responds unsuccessfully, the status of the data content distribution synchronization task is recorded in the task log as failed; if the data content distribution synchronization task is abnormal or not completed, the task log is not changed, and the status of the data content distribution synchronization task is still in progress; Step S2b2, regularly start the data synchronization compensation thread, scan the task log, select the data content distribution synchronization task with the status value in progress, query whether the data content in the downstream system has been successfully synchronized, if the data content has been successfully synchronized, return the result and record it in the task log, if the data content has not been successfully synchronized, return to step S2b1, and the data content distribution synchronization task enters the compensation task queue and waits for the task to start; Step S2b3, regularly start the data synchronization compensation thread, scan the task log, select the data content distribution synchronization task with a failed status, and return to step S2b1. The data content distribution synchronization task directly enters the compensation task queue and waits for the task to start.

9. The method for connecting and synchronizing cloud data content in an industrial field according to claim 8, characterized in that: In step S2b2 and step S2b3, the judgment criteria of whether the compensation task queue restarts the task and the restart times are the data integration task compensation mechanism in the background management.

10. The method for connecting and synchronizing cloud data content in an industrial field according to claim 8, characterized in that: The following steps are also included: Step S2c, data integration upstream and downstream data consistency verification transaction: set up an asynchronous thread, regularly query the interface call information of the upstream and downstream systems, obtain the data content of the documents in the upstream and downstream systems, and compare whether the data content of the documents in the upstream and downstream systems within the current synchronization time is consistent. If there is any inconsistency, jump to step S1a2 immediately.

Images