CN111629026A - MES-based data interaction method and equipment - Google Patents
MES-based data interaction method and equipment Download PDFInfo
- Publication number
- CN111629026A CN111629026A CN202010266171.4A CN202010266171A CN111629026A CN 111629026 A CN111629026 A CN 111629026A CN 202010266171 A CN202010266171 A CN 202010266171A CN 111629026 A CN111629026 A CN 111629026A
- Authority
- CN
- China
- Prior art keywords
- data
- processing unit
- data processing
- interacted
- interaction
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 230000003993 interaction Effects 0.000 title claims abstract description 91
- 238000000034 method Methods 0.000 title claims abstract description 38
- 238000012545 processing Methods 0.000 claims abstract description 232
- 230000002452 interceptive effect Effects 0.000 claims description 10
- 238000004590 computer program Methods 0.000 claims description 3
- 238000007726 management method Methods 0.000 description 17
- 238000004519 manufacturing process Methods 0.000 description 15
- 238000012360 testing method Methods 0.000 description 4
- 230000005540 biological transmission Effects 0.000 description 3
- 230000010354 integration Effects 0.000 description 3
- 238000004458 analytical method Methods 0.000 description 2
- 238000013523 data management Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000013439 planning Methods 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 238000000354 decomposition reaction Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/566—Grouping or aggregating service requests, e.g. for unified processing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism
- G06Q50/04—Manufacturing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/55—Push-based network services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Abstract
The invention discloses a data interaction method and equipment based on MES, which are applied to an MES system comprising a plurality of data processing units, wherein the method comprises the following steps: receiving data to be interacted sent by a source data processing unit, and determining a target data processing unit according to a subscription message path corresponding to the data to be interacted; establishing a scheduling configuration file based on the attributes of the data to be interacted and the interaction data set; judging whether the data to be interacted exists in the target data processing unit or not according to the scheduling configuration file; and when the data to be interacted does not exist in the target data processing unit, pushing the data to be interacted to the target data processing unit according to the subscription rule of the target data processing unit, thereby simply and quickly completing data interaction among different enterprise systems and reducing the cost.
Description
Technical Field
The application relates to the technical field of manufacturing informatization, in particular to a data interaction method and equipment based on MES.
Background
Along with the higher and higher management demand of the current enterprises on the execution of the production process, industrial intelligent manufacturing is widely popularized, and the value of the acquisition and analysis of production data on the improvement of the production process is extremely high in the industrial intelligent manufacturing.
Manufacturing Execution System (MES), i.e. a Manufacturing process Execution System, is a set of production information management System facing to a Manufacturing enterprise workshop Execution layer. The MES can provide management modules for enterprises, such as manufacturing data management, planning and scheduling management, production scheduling management, inventory management, quality management, human resource management, work center/equipment management, tool and tool management, purchasing management, cost management, project bulletin board management, production process control, bottom data integration analysis, upper data integration decomposition and the like, and creates a solid, reliable, comprehensive and feasible manufacturing cooperation management platform for the enterprises.
In addition, enterprises are also continuously applying advanced informatization systems such as ERP (Enterprise Resource Planning), PDM (Product Data Management), PLM (Product lifecycle Management), CRM (Customer Relationship Management), WMS (Warehouse Management System), OA (Office Automation), and these interrelated application systems are developed by different manufacturers, fail to integrate information between systems, and are still in a state of being separated from each other.
In the prior art, a data interaction mode basically belongs to the realization of data interaction and information sharing by making an interface between systems, however, data interface and system integration is a complex system engineering, factors of all aspects are involved, and various problems often occur in actual work, so that the development success rate of a software system is low, the development period is long, and the execution of enterprise projects is not facilitated.
Therefore, how to simply and quickly complete data interaction between different enterprise systems and reduce the cost is a technical problem to be solved at present.
Disclosure of Invention
The invention provides a data interaction method based on MES, which is used in an MES system comprising a plurality of data processing units and used for solving the technical problems of complex data interaction and high cost among different enterprise systems in the prior art, and comprises the following steps:
receiving data to be interacted sent by a source data processing unit, and determining a target data processing unit according to a subscription message path corresponding to the data to be interacted;
establishing a scheduling configuration file based on the attributes of the data to be interacted and an interaction data set, wherein the interaction data set is determined according to a preset subscription interaction standard between the source data processing unit and the target data processing unit, and the interaction data set comprises the data to be interacted;
judging whether the data to be interacted exists in the target data processing unit or not according to the scheduling configuration file;
and when the data to be interacted does not exist in the target data processing unit, pushing the data to be interacted to the target data processing unit according to the subscription rule of the target data processing unit.
Preferably, the establishing of the scheduling configuration file based on the attribute of the data to be interacted and the interaction data set specifically includes:
establishing a writable mark table in a source database corresponding to the source data processing unit according to each data subset in the interactive data set, configuring a main mark in the source database, and configuring an auxiliary mark in a target database corresponding to the target data processing unit;
determining a data sending mode of the source data processing unit and a data receiving mode of the target data processing unit according to the attributes;
and establishing the scheduling configuration file based on the writable flag table, the main flag, the auxiliary flag, the data sending mode and the data receiving mode.
Preferably, the determining, according to the scheduling configuration file, whether the data to be interacted already exists in the target data processing unit includes:
acquiring the primary flag and the secondary flag based on the scheduling configuration file;
judging whether the main mark and the auxiliary mark are the same;
if yes, determining that the data to be interacted exists in the target data processing unit, and stopping data interaction;
if not, determining that the data to be interacted does not exist in the target data processing unit.
Preferably, after pushing the data to be interacted to the target data processing unit according to the subscription rule of the target data processing unit, the method further includes:
judging whether the data to be interacted are pushed successfully or not;
if yes, updating the writable flag table, the main flag and the auxiliary flag;
if not, alarm information is sent out.
Preferably, the attributes are data amount and data type, and the data sending mode of the source data processing unit and the data receiving mode of the target data processing unit are configured according to the attributes of the data to be interacted, specifically:
when the data volume is smaller than a preset threshold or the security level of the data type is lower than a preset level threshold, determining the data sending mode and the data receiving mode based on a UDP protocol;
and when the data volume is not less than the preset threshold or the security level is not lower than the preset level threshold, determining the data sending mode and the data receiving mode based on an HTTP protocol.
Preferably, after determining the target data processing unit according to the subscription message path corresponding to the data to be interacted, the method further includes:
determining an interaction frequency corresponding to the data to be interacted;
and when the interaction frequency is greater than a preset frequency threshold, caching the data to be interacted, and pushing the cached data to be interacted to the target data processing unit at regular time according to the subscription rule.
Preferably, the data processing unit comprises an MES data processing unit, and further comprises at least one of the following data processing units:
the system comprises an ERP data processing unit, a DCS data processing unit, a CRM data processing unit, a PLM data processing unit, a WMS data processing unit, a PDM data processing unit, an HR data processing unit and an OA data processing unit.
Correspondingly, the invention also provides MES-based data interaction equipment, which is applied to an MES system comprising a plurality of data processing units, and comprises the following components:
the determining module is used for receiving data to be interacted sent by the source data processing unit and determining a target data processing unit according to a subscription message path corresponding to the data to be interacted;
the establishing module is used for establishing a scheduling configuration file based on the attributes of the data to be interacted and an interaction data set, wherein the interaction data set is determined according to a preset subscription interaction standard between the source data processing unit and the target data processing unit, and the interaction data set comprises the data to be interacted;
the judging module is used for judging whether the data to be interacted exists in the target data processing unit according to the scheduling configuration file;
and the pushing module is used for pushing the data to be interacted to the target data processing unit according to the subscription rule of the target data processing unit when the data to be interacted does not exist in the target data processing unit.
Accordingly, the present invention also provides a computer-readable storage medium, in which instructions are stored, and when the instructions are executed on a terminal device, the terminal device is caused to execute the MES-based data interaction method as described above.
Correspondingly, the invention also provides a computer program product, which when running on a terminal device, causes the terminal device to execute the MES-based data interaction method.
Compared with the prior art, the invention has the following beneficial effects:
the invention discloses a data interaction method and equipment based on MES, which are applied to an MES system comprising a plurality of data processing units, wherein the method comprises the following steps: receiving data to be interacted sent by a source data processing unit, and determining a target data processing unit according to a subscription message path corresponding to the data to be interacted; establishing a scheduling configuration file based on the attributes of the data to be interacted and the interaction data set; judging whether the data to be interacted exists in the target data processing unit or not according to the scheduling configuration file; and when the data to be interacted does not exist in the target data processing unit, pushing the data to be interacted to the target data processing unit according to the subscription rule of the target data processing unit, thereby simply and quickly completing data interaction among different enterprise systems and reducing the cost.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
FIG. 1 is a flow chart of a MES-based data interaction method according to an embodiment of the present invention;
FIG. 2 is a flow chart of a MES-based data interaction method according to another embodiment of the present invention;
FIG. 3 is a schematic structural diagram of an MES-based data interaction device according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
As described in the background art, data interaction between different enterprise systems in the prior art is complex and high in cost.
In order to solve the above problems, an embodiment of the present application provides a data interaction method based on MES, where a scheduling configuration file is established based on attributes of data to be interacted and an interaction data set; judging whether the data to be interacted exists in the target data processing unit or not according to a scheduling configuration file; and when the data to be interacted does not exist in the target data processing unit, pushing the data to be interacted to the target data processing unit according to the subscription rule of the target data processing unit, thereby simply and quickly completing data interaction among different enterprise systems and reducing the cost.
Fig. 1 shows a flow diagram of a data interaction method based on an MES, which is applied to an MES system including a plurality of data processing units, and includes the following steps:
step S101, receiving data to be interacted sent by a source data processing unit, and determining a target data processing unit according to a subscription message path corresponding to the data to be interacted.
Specifically, the subscription message paths of different data to be interacted may be pre-stored, and are directly invoked when receiving the data to be interacted sent by the source data processing unit, so as to determine the target data processing unit.
In order to improve data interaction efficiency, in a preferred embodiment of the present application, after determining a target data processing unit according to a subscription message path corresponding to the data to be interacted, the method further includes:
determining an interaction frequency corresponding to the data to be interacted;
and when the interaction frequency is greater than a preset frequency threshold, caching the data to be interacted, and pushing the cached data to be interacted to the target data processing unit at regular time according to the subscription rule.
As described above, when the interaction frequency corresponding to the data to be interacted is greater than the preset frequency threshold, the data to be interacted is cached, and the cached data to be interacted is pushed to the target data processing unit at regular time according to the subscription rule, so that the generation of a scheduling configuration file is omitted, and the efficiency of data access is improved.
The technical personnel in the field can flexibly set different preset frequency thresholds and decide whether to cache the data to be interacted according to the actual situation, which does not affect the protection scope of the present application.
Step S102, a scheduling configuration file is established based on the attributes of the data to be interacted and an interaction data set, wherein the interaction data set is determined according to a preset subscription interaction standard between the source data processing unit and the target data processing unit, and the interaction data set comprises the data to be interacted.
Specifically, multiple interactive data may exist between the source data processing unit and the target data processing unit, an interactive data set composed of the multiple interactive data may be determined according to a preset subscription interaction standard between the source data processing unit and the target data processing unit, the interactive data set includes the data to be interacted, a scheduling configuration file may be established according to the attribute of the data to be interacted and the interactive data set, and in a specific application scenario of the present application, the scheduling task configuration file may be used to set which system and which manner to perform data synchronization. In practice, the data synchronization mode may be based on a data log, and may also be based on a table, a view, a stored procedure, and the like.
In order to establish an accurate scheduling configuration file, in a preferred embodiment of the present application, the scheduling configuration file is established based on the attribute of the data to be interacted and the interaction data set, specifically:
establishing a writable mark table in a source database corresponding to the source data processing unit according to each data subset in the interactive data set, configuring a main mark in the source database, and configuring an auxiliary mark in a target database corresponding to the target data processing unit;
determining a data sending mode of the source data processing unit and a data receiving mode of the target data processing unit according to the attributes;
and establishing the scheduling configuration file based on the writable flag table, the main flag, the auxiliary flag, the data sending mode and the data receiving mode.
Specifically, each data processing unit includes a database, a writable flag table is established in a source database corresponding to the source data processing unit according to each data subset in the interaction data set, a main flag is configured in the source database, an auxiliary flag is configured in a target database corresponding to the target data processing unit, and the scheduling configuration file is established based on the writable flag table, the main flag, the auxiliary flag, the data transmission mode and the data reception mode according to a data transmission mode of an attribute source data processing unit of data to be interacted and a data reception mode of the target data processing unit.
It should be noted that the scheme of the above preferred embodiment is only a specific implementation scheme proposed in the present application, and other ways of establishing a scheduling configuration file based on the attribute of the data to be interacted and the interaction data set all belong to the protection scope of the present application.
In order to facilitate reliable transmission of data to be interacted, in a preferred embodiment of the present application, the attributes are a data amount and a data type, and a data sending mode of the source data processing unit and a data receiving mode of the target data processing unit are configured according to the attributes of the data to be interacted, specifically:
when the data volume is smaller than a preset threshold or the security level of the data type is lower than a preset level threshold, determining the data sending mode and the data receiving mode based on a UDP protocol;
and when the data volume is not less than the preset threshold or the security level is not lower than the preset level threshold, determining the data sending mode and the data receiving mode based on an HTTP protocol.
Specifically, in a specific application scenario of the present application, for data with a data size less than 4K or data with low security level requirements, such as basic state information of a data processing unit, current IP and operation information, it is required to be continuously broadcast inside the system. Such data uses the UDP protocol and typically does not require a recipient acknowledgement. If necessary, the receiver confirmation is also supported to realize a handshake mode; for data with a data volume greater than 4K or data with higher security level requirements, such as complex device status information, data from a database, test result information of a file or high-throughput test device, and device control instructions, will be transmitted via the HTTP protocol which is safer but may be less efficient to process. If the requirement on the safety is higher, the SSL encryption can be carried out on the transmitted data, and the internal information can be ensured not to be intercepted by third-party malicious software.
It should be noted that the above solution of the preferred embodiment is only a specific implementation solution proposed in the present application, and other solutions that configure the data sending method of the source data processing unit and the data receiving method of the target data processing unit according to the attribute of the data to be interacted all belong to the protection scope of the present application.
Step S103, judging whether the data to be interacted already exists in the target data processing unit according to the scheduling configuration file.
Specifically, after the scheduling configuration file is established, whether the data to be interacted exists in the target data processing unit may be determined according to the scheduling configuration file.
In order to accurately determine whether the data to be interacted already exists in the target data processing unit, in a preferred embodiment of the present application, determining whether the data to be interacted already exists in the target data processing unit according to the scheduling configuration file specifically includes:
acquiring the primary flag and the secondary flag based on the scheduling configuration file;
judging whether the main mark and the auxiliary mark are the same;
if yes, determining that the data to be interacted exists in the target data processing unit, and stopping data interaction;
if not, determining that the data to be interacted does not exist in the target data processing unit.
As described above, by comparing whether the main flag and the auxiliary flag corresponding to the scheduling configuration file are the same or not, whether the data to be interacted already exists in the target data processing unit can be accurately determined.
It should be noted that the scheme of the above preferred embodiment is only a specific implementation scheme proposed in the present application, and other ways of determining whether the data to be interacted already exists in the target data processing unit according to the scheduling configuration file all belong to the protection scope of the present application.
Step S104, when the data to be interacted does not exist in the target data processing unit, pushing the data to be interacted to the target data processing unit according to the subscription rule of the target data processing unit.
In order to facilitate subsequent processing of data interaction, in a preferred embodiment of the present application, after pushing the data to be interacted to the target data processing unit according to the subscription rule of the target data processing unit, the method further includes:
judging whether the data to be interacted are pushed successfully or not;
if yes, updating the writable flag table, the main flag and the auxiliary flag;
if not, alarm information is sent out.
In a specific application scenario of the present application, it is further determined whether the data is successfully pushed to the target data processing unit, and if the data is not successfully pushed to the target data processing unit, an alarm message is generated. In implementation, the warning message may be notified to the user in the form of a mail, a popup, or the like, and the interaction of the next data is continued while skipping the data for which the interaction fails. And when the data is successfully pushed to the target data processing unit, further updating the main mark and the writable mark table in the source data processing unit and the auxiliary mark in the target data processing unit, and simultaneously recording the synchronous log.
A person skilled in the art may determine whether to perform the above step of determining whether the data to be interacted is successfully pushed according to an actual situation.
For data interaction based on an MES system, in a preferred embodiment of the present application, the data processing unit comprises an MES data processing unit, and further comprises at least one of the following data processing units:
an ERP data processing unit, a DCS (Distributed Control System) data processing unit, a CRM data processing unit, a PLM data processing unit, a WMS data processing unit, a PDM data processing unit, an HR (human resource) data processing unit and an OA data processing unit.
Those skilled in the art can add other different data processing units according to actual needs.
By applying the technical scheme, the data to be interacted sent by a source data processing unit is received, and a target data processing unit is determined according to a subscription message path corresponding to the data to be interacted; establishing a scheduling configuration file based on the attributes of the data to be interacted and the interaction data set; judging whether the data to be interacted exists in the target data processing unit or not according to the scheduling configuration file; and when the data to be interacted does not exist in the target data processing unit, pushing the data to be interacted to the target data processing unit according to the subscription rule of the target data processing unit, thereby simply and quickly completing data interaction among different enterprise systems and reducing the cost.
In order to further illustrate the technical idea of the present invention, the technical solution of the present invention will now be described with reference to specific application scenarios.
The embodiment of the invention provides a data interaction method based on an MES (manufacturing execution system), which is applied to an MES system comprising a plurality of data processing units, wherein a target data processing unit is determined according to a subscription message path corresponding to data to be interacted by receiving data to be interacted sent by a source data processing unit; establishing a scheduling configuration file based on the attributes of the data to be interacted and the interaction data set; judging whether the data to be interacted exists in the target data processing unit or not according to the scheduling configuration file; and when the data to be interacted does not exist in the target data processing unit, pushing the data to be interacted to the target data processing unit according to the subscription rule of the target data processing unit, thereby simply and quickly completing data interaction among different enterprise systems and reducing the cost.
As shown in fig. 2, the method comprises the following specific steps:
step S201, receiving data to be interacted sent by the source data processing unit.
The method is applied to an MES system comprising a plurality of data processing units, comprises an MES data processing unit and further comprises at least one of the following data processing units: the system comprises an ERP data processing unit, a DCS data processing unit, a CRM data processing unit, a PLM data processing unit, a WMS data processing unit, a PDM data processing unit, an HR data processing unit and an OA data processing unit, wherein the source data processing unit can be any one of the processing units, generates data to be interacted, and can receive the data to be interacted sent by the source data processing unit.
Step S202, determining a target data processing unit according to the subscription message path corresponding to the data to be interacted.
The data to be interacted has a corresponding subscription message path, which can be preset and is directly called when the data to be interacted exists, so that the target data processing unit is determined.
Step S203, determining whether the interaction frequency corresponding to the data to be interacted is greater than a preset frequency threshold, if so, performing step S204, and if not, performing step S205.
Step S204, caching the data to be interacted, and pushing the cached data to be interacted to the target data processing unit at regular time according to the subscription rule.
When the interaction frequency corresponding to the data to be interacted is greater than the preset frequency threshold, in order to realize the rapid access of the data, the data to be interacted is cached, and the cached data to be interacted is pushed to the target data processing unit at regular time according to the subscription rule, so that the generation of a scheduling configuration file is omitted, and the data access efficiency is improved.
Step S205, a scheduling configuration file is established based on the attributes of the data to be interacted and the interaction data set.
The interaction data set is determined according to a preset subscription interaction standard between the source data processing unit and the target data processing unit, and the interaction data set comprises the data to be interacted.
Different scheduling task configuration files are established aiming at data synchronization among different data processing units, and the scheduling task configuration files can be used for setting the data synchronization among different systems in which mode. In practice, the data synchronization mode may be based on a data log, and may also be based on a table, a view, a stored procedure, and the like. If a scheduling task configuration file can be established aiming at the data synchronization between the ERP data processing unit and the MES data processing unit, the data synchronization is carried out between the ERP data processing unit and the MES data processing unit in the form of data logs; and if another scheduling task configuration file is established aiming at the data synchronization between the ERP data processing unit and the WMS data processing unit, the data synchronization is carried out between the ERP data processing unit and the WMS data processing unit in a form of a table.
The process of establishing the scheduling configuration file is as follows:
step a, establishing a writable mark table in a source database corresponding to the source data processing unit according to each data subset in the interactive data set, configuring a main mark in the source database, and configuring an auxiliary mark in a target database corresponding to the target data processing unit;
the main mark is used for identifying data; the writable mark table is used for recording interactive data, and when the data is written, changed and deleted, a main mark corresponding to the data can be recorded in the writable mark table; the auxiliary mark is used for recording data interaction information.
B, determining a data sending mode of the source data processing unit and a data receiving mode of the target data processing unit according to the attributes;
the attributes are data quantity and data type, and when the data quantity is smaller than a preset threshold or the security level of the data type is lower than a preset level threshold, the data sending mode and the data receiving mode are determined based on a UDP protocol. For example, data with a data size of less than 4K or data with low security level requirements, such as basic status information of the data processing unit, current IP and operation information, need to be continuously broadcast within the system. Such data uses the UDP protocol and typically does not require a recipient acknowledgement. Receiver acknowledgement is also supported to implement the handshake mode if needed.
And when the data volume is not less than the preset threshold or the security level is not lower than the preset level threshold, determining the data sending mode and the data receiving mode based on an HTTP protocol. For example, data with a data volume greater than 4K or data with a higher security level requirement, which may be complex device status information, data from a database, file or test result information from high throughput test devices, and device control instructions, will be transmitted via the more secure HTTP protocol, which may be somewhat less efficient in processing. If the requirement on the safety is higher, the SSL encryption can be carried out on the transmitted data, and the internal information can be ensured not to be intercepted by third-party malicious software.
And c, establishing the scheduling configuration file based on the writable flag table, the main flag, the auxiliary flag, the data sending mode and the data receiving mode.
Step S206, determining whether the target data processing unit has the to-be-interacted data according to the scheduling configuration file, if yes, performing step S207, and if no, performing step S208.
And acquiring a main mark and an auxiliary mark based on the scheduling configuration file, wherein the main mark and the auxiliary mark can be based on the timestamp, and whether the data to be interacted exists in the target data processing unit can be judged according to the main mark and the auxiliary mark.
Step S207, stopping the data interaction.
And when the main mark is the same as the auxiliary mark, determining that the data to be interacted exists in the target data processing unit, and stopping the data interaction.
Step S208, pushing the data to be interacted to the target data processing unit according to the subscription rule of the target data processing unit.
And when the main mark and the auxiliary mark are different, determining that the data to be interacted does not exist in the target data processing unit, and pushing the data to be interacted to the target data processing unit according to a subscription rule of the target data processing unit.
Step S209, determining whether the data to be interacted is successfully pushed, if so, performing step S211, and if not, performing step S210.
Step S210, sending out alarm information.
And further judging whether the data is successfully pushed to the target data processing unit or not, and if the data is not successfully pushed to the target data processing unit, generating alarm information. In implementation, the warning message may be notified to the user in the form of a mail, a popup, or the like, and the interaction of the next data is continued while skipping the data for which the interaction fails.
Step S211, updating the writable flag table, the primary flag, and the secondary flag.
And when the data is successfully pushed to the target data processing unit, further updating the main mark and the writable mark table in the source data processing unit and the auxiliary mark in the target data processing unit, and simultaneously recording the synchronous log.
In order to achieve the above technical object, an embodiment of the present application further provides an MES-based data interaction apparatus, which is applied in an MES system including a plurality of data processing units, as shown in fig. 3, the apparatus includes:
a determining module 301, configured to receive data to be interacted sent by a source data processing unit, and determine a target data processing unit according to a subscription message path corresponding to the data to be interacted;
an establishing module 302, configured to establish a scheduling configuration file based on an attribute of the to-be-interacted data and an interaction data set, where the interaction data set is determined according to a preset subscription interaction standard between the source data processing unit and the target data processing unit, and the interaction data set includes the to-be-interacted data;
a determining module 303, configured to determine whether the data to be interacted already exists in the target data processing unit according to the scheduling configuration file;
a pushing module 304, configured to, when the data to be interacted does not exist in the target data processing unit, push the data to be interacted to the target data processing unit according to a subscription rule of the target data processing unit.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same; although the present application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not necessarily depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.
Claims (10)
1. An MES-based data interaction method applied to an MES system comprising a plurality of data processing units, the method comprising:
receiving data to be interacted sent by a source data processing unit, and determining a target data processing unit according to a subscription message path corresponding to the data to be interacted;
establishing a scheduling configuration file based on the attributes of the data to be interacted and an interaction data set, wherein the interaction data set is determined according to a preset subscription interaction standard between the source data processing unit and the target data processing unit, and the interaction data set comprises the data to be interacted;
judging whether the data to be interacted exists in the target data processing unit or not according to the scheduling configuration file;
and when the data to be interacted does not exist in the target data processing unit, pushing the data to be interacted to the target data processing unit according to the subscription rule of the target data processing unit.
2. The method of claim 1, wherein the establishing of the scheduling profile based on the attributes of the data to be interacted and the interaction dataset comprises:
establishing a writable mark table in a source database corresponding to the source data processing unit according to each data subset in the interactive data set, configuring a main mark in the source database, and configuring an auxiliary mark in a target database corresponding to the target data processing unit;
determining a data sending mode of the source data processing unit and a data receiving mode of the target data processing unit according to the attributes;
and establishing the scheduling configuration file based on the writable flag table, the main flag, the auxiliary flag, the data sending mode and the data receiving mode.
3. The method according to claim 2, wherein the determining whether the data to be interacted already exists in the target data processing unit according to the scheduling configuration file specifically includes:
acquiring the primary flag and the secondary flag based on the scheduling configuration file;
judging whether the main mark and the auxiliary mark are the same;
if yes, determining that the data to be interacted exists in the target data processing unit, and stopping data interaction;
if not, determining that the data to be interacted does not exist in the target data processing unit.
4. The method of claim 2, after pushing the data to be interacted to the target data processing unit according to the subscription rule of the target data processing unit, further comprising:
judging whether the data to be interacted are pushed successfully or not;
if yes, updating the writable flag table, the main flag and the auxiliary flag;
if not, alarm information is sent out.
5. The method according to claim 2, wherein the attributes are data amount and data type, and the configuring the data sending mode of the source data processing unit and the data receiving mode of the target data processing unit according to the attributes of the data to be interacted specifically includes:
when the data volume is smaller than a preset threshold or the security level of the data type is lower than a preset level threshold, determining the data sending mode and the data receiving mode based on a UDP protocol;
and when the data volume is not less than the preset threshold or the security level is not lower than the preset level threshold, determining the data sending mode and the data receiving mode based on an HTTP protocol.
6. The method of claim 1, wherein after determining a target data processing unit according to a subscription message path corresponding to the data to interact, the method further comprises:
determining an interaction frequency corresponding to the data to be interacted;
and when the interaction frequency is greater than a preset frequency threshold, caching the data to be interacted, and pushing the cached data to be interacted to the target data processing unit at regular time according to the subscription rule.
7. The method of claim 1, wherein the data processing unit comprises an MES data processing unit, further comprising at least one of the following data processing units:
the system comprises an ERP data processing unit, a DCS data processing unit, a CRM data processing unit, a PLM data processing unit, a WMS data processing unit, a PDM data processing unit, an HR data processing unit and an OA data processing unit.
8. An MES-based data interaction device applied to an MES system comprising a plurality of data processing units, the device comprising:
the determining module is used for receiving data to be interacted sent by the source data processing unit and determining a target data processing unit according to a subscription message path corresponding to the data to be interacted;
the establishing module is used for establishing a scheduling configuration file based on the attributes of the data to be interacted and an interaction data set, wherein the interaction data set is determined according to a preset subscription interaction standard between the source data processing unit and the target data processing unit, and the interaction data set comprises the data to be interacted;
the judging module is used for judging whether the data to be interacted exists in the target data processing unit according to the scheduling configuration file;
and the pushing module is used for pushing the data to be interacted to the target data processing unit according to the subscription rule of the target data processing unit when the data to be interacted does not exist in the target data processing unit.
9. A computer-readable storage medium having stored therein instructions that, when run on a terminal device, cause the terminal device to perform the MES-based data interaction method of any of claims 1-7.
10. A computer program product, characterized in that the computer program product, when run on a terminal device, causes the terminal device to execute the MES-based data interaction method of any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010266171.4A CN111629026A (en) | 2020-04-07 | 2020-04-07 | MES-based data interaction method and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010266171.4A CN111629026A (en) | 2020-04-07 | 2020-04-07 | MES-based data interaction method and equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111629026A true CN111629026A (en) | 2020-09-04 |
Family
ID=72272510
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010266171.4A Pending CN111629026A (en) | 2020-04-07 | 2020-04-07 | MES-based data interaction method and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111629026A (en) |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101409706A (en) * | 2007-10-09 | 2009-04-15 | 华为技术有限公司 | Method, system and relevant equipment for distributing data of edge network |
| CN103402018A (en) * | 2013-07-30 | 2013-11-20 | 东莞宇龙通信科技有限公司 | Terminal and data processing method |
| CN105843966A (en) * | 2016-04-22 | 2016-08-10 | 中国银联股份有限公司 | Data processing system and method |
| CN108234541A (en) * | 2016-12-14 | 2018-06-29 | 陕西省地方电力（集团）有限公司 | A kind of service management and system of enterprise's bus platform |
| CN108667740A (en) * | 2017-03-29 | 2018-10-16 | 腾讯科技（深圳）有限公司 | The method, apparatus and system of flow control |
| CN109032747A (en) * | 2018-08-10 | 2018-12-18 | 江苏奇异点网络有限公司 | Data-updating method and device |
| CN109792325A (en) * | 2017-01-24 | 2019-05-21 | 华为技术有限公司 | A kind of data transmission method, device and customer terminal equipment |
| CN110569233A (en) * | 2019-06-30 | 2019-12-13 | 华为技术有限公司 | Hot data management method, device and system |
| CN110753096A (en) * | 2019-10-12 | 2020-02-04 | 北京达佳互联信息技术有限公司 | Message pushing method and system and electronic equipment |
-
2020
- 2020-04-07 CN CN202010266171.4A patent/CN111629026A/en active Pending
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101409706A (en) * | 2007-10-09 | 2009-04-15 | 华为技术有限公司 | Method, system and relevant equipment for distributing data of edge network |
| CN103402018A (en) * | 2013-07-30 | 2013-11-20 | 东莞宇龙通信科技有限公司 | Terminal and data processing method |
| CN105843966A (en) * | 2016-04-22 | 2016-08-10 | 中国银联股份有限公司 | Data processing system and method |
| CN108234541A (en) * | 2016-12-14 | 2018-06-29 | 陕西省地方电力（集团）有限公司 | A kind of service management and system of enterprise's bus platform |
| CN109792325A (en) * | 2017-01-24 | 2019-05-21 | 华为技术有限公司 | A kind of data transmission method, device and customer terminal equipment |
| CN108667740A (en) * | 2017-03-29 | 2018-10-16 | 腾讯科技（深圳）有限公司 | The method, apparatus and system of flow control |
| CN109032747A (en) * | 2018-08-10 | 2018-12-18 | 江苏奇异点网络有限公司 | Data-updating method and device |
| CN110569233A (en) * | 2019-06-30 | 2019-12-13 | 华为技术有限公司 | Hot data management method, device and system |
| CN110753096A (en) * | 2019-10-12 | 2020-02-04 | 北京达佳互联信息技术有限公司 | Message pushing method and system and electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10061578B2 (en) | System and method of configuring a data store for tracking and auditing real-time events across different software development tools in agile development environments | |
| US10268961B2 (en) | Generating predictive models to reconfigure electronic devices | |
| CN110417884B (en) | Message pushing method, device, equipment and storage medium | |
| CN103313289A (en) | Wap system automatic test system and method | |
| US10091672B2 (en) | Fault handling method, apparatus and system | |
| US11061669B2 (en) | Software development tool integration and monitoring | |
| US20230403215A1 (en) | Systems and methods of monitoring and controlling remote assets | |
| CN103118100A (en) | Guarantee method and guarantee system for improving usability of virtual machine application | |
| CN112035344A (en) | Multi-scenario test method, device, equipment and computer readable storage medium | |
| US20210049142A1 (en) | SYSTEM AND METHOD FOR ALERT INSIGHT IN CONFIGURATION MANAGEMENT DATABASES (CMDBs) | |
| CN111258798A (en) | Fault positioning method and device for monitoring data, computer equipment and storage medium | |
| CN110377588B (en) | Database object access monitoring method, server and terminal | |
| CN113472574B (en) | Method, device, medium and electronic device for monitoring user equipment based on 5G private network | |
| US20210344701A1 (en) | System and method for detection promotion | |
| CN111813699B (en) | Data routing test method and device based on intelligent electric meter and computer equipment | |
| CN111629026A (en) | MES-based data interaction method and equipment | |
| CN114090268B (en) | Container management method and container management system | |
| CN112559233B (en) | Method, device, equipment and computer readable medium for identifying fault type | |
| CN113283865A (en) | Industrial production information management and control method and device | |
| CN112788153A (en) | Internet of things equipment upgrade management method, device, equipment and storage medium | |
| CN113157475A (en) | Log processing method and device, storage medium and electronic equipment | |
| CN115795553B (en) | Data processing method, system, equipment and storage medium | |
| CN113301002B (en) | Information processing method, device, electronic equipment and storage medium | |
| CN112737812B (en) | Data transmission method and device | |
| WO2023173939A1 (en) | Configuration data migration method for base station, and computer device and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200904 |
|
| RJ01 | Rejection of invention patent application after publication |