CN112817773A

CN112817773A - Data processing method, device and system

Info

Publication number: CN112817773A
Application number: CN201911121251.4A
Authority: CN
Inventors: 王昌明
Original assignee: Hitachi Ltd
Current assignee: Hitachi Ltd
Priority date: 2019-11-15
Filing date: 2019-11-15
Publication date: 2021-05-18

Abstract

The invention discloses a data processing method, a data processing device and a data processing system, relates to the technical field of data processing, and aims to solve the problems that upstream and downstream enterprises of a supply chain cannot exchange data or the unified workload of data is overlarge due to non-uniform data formats. The method comprises the following steps: acquiring original information of a data source; converting the original information into information having a target format; and transmitting the information with the target format. The embodiment of the invention can facilitate the data interaction and other operations between upstream and downstream enterprises of an industry chain.

Description

Data processing method, device and system

Technical Field

The present invention relates to the field of data processing technologies, and in particular, to a data processing method, apparatus, and system.

Background

At present, most enterprises rely on an IT system to manage production planning, storage, logistics, production, sales and the like. However, due to the differences in the systems used by different enterprises, the differences in the data formats, and the limitations of conventional systems, most of these systems can only manage the inside of the enterprise, and the data flow across the enterprise is still very limited. Effective information sharing and management across enterprises relies on elaborate upstream and downstream real-time data support, but the management of the supply chain for each enterprise remains relatively extensive and delayed.

CN108090746A discloses a supply chain system management method based on data sharing among different enterprises. In the application, upstream and downstream enterprises jointly construct a system, and data format standardization is realized. However, due to the large number of upstream and downstream enterprises, the types of the used IT systems are different, and the period of constructing the systems together and standardizing the data is long and difficult to realize.

Disclosure of Invention

Embodiments of the present invention provide a data processing method, apparatus, and system, so as to solve the problem that upstream and downstream enterprises in a supply chain cannot exchange data due to non-uniform data formats or the workload of data unification is too large.

In a first aspect, an embodiment of the present invention provides a data processing method, which is applied to a gateway disposed in an enterprise local area, and includes:

acquiring original information of a data source;

converting the original information into information having a target format;

and transmitting the information with the target format.

In the uplink direction, the data source comprises an enterprise information system or a client; in the downstream direction, the data source comprises a cloud platform.

In the uplink direction, the original information is original data to be issued by a message enterprise information system or the client;

the converting the original information into information having a target format includes:

obtaining a message according to the original data;

storing the message into a corresponding message group buffer area;

converting the message packet group stored in the message group buffer into a file with a target format;

the target format comprises an extensible markup language (XML) format or a JS object numbered musical notation (JSON) format.

Wherein, the obtaining of the message according to the original data comprises:

filling the original data into a message template with an identification ID to form a message body;

forming a message header, wherein the message header comprises the ID, a timestamp, a sequence number, and a transmission direction;

and forming the message packet by using the message header and the message body.

Wherein the message header further comprises a priority.

Before obtaining the message packet according to the original data, the method further includes:

configuring a communication protocol under the condition that the data source is an enterprise information system; defining a parameter list to be transmitted; associating the parameter list with a message template;

under the condition that the data source is a client, establishing a table structure in a storage area of the gateway; defining a parameter list to be transmitted in the table structure; and associating the parameter list with a message template.

Wherein the storing the message packet into a corresponding message group buffer comprises:

determining whether a first message group buffer corresponding to the message can store the message;

when the first message group buffer area can not store the message, the message is stored in a corresponding second message group buffer area;

wherein, when any one of the following conditions is satisfied, it is determined that the first message group buffer cannot store the message packet: the timing time of the first message group buffer is up; the number of the message messages stored in the first message group buffer zone reaches a preset value; the first message group buffer zone comprises message messages with the priority meeting the preset requirement.

Wherein after storing the message packet in the corresponding message group buffer, the method further comprises:

in the message group buffer area, sequencing the message messages according to the ID and the serial number of the message messages;

selecting one message from the repeated message messages to be reserved, and deleting other message messages in the repeated message messages, wherein the repeated message messages refer to message messages with the same ID but different message values.

In the uplink direction, the original information is a query request of the client; the converting the original information into information having a target format includes:

converting the query request into a query instruction;

filling the query instruction into a corresponding message template to obtain a query message;

storing the query message in a corresponding message group buffer;

converting the query message group stored in the message group buffer into a file having a target format;

wherein the target format comprises an XML format or a JSON format.

Wherein, in the uplink direction, the method further comprises:

and sending the subscription request of the client to a cloud platform.

In a downlink direction, the original information comprises data returned by the cloud platform according to a query message or data returned by the cloud platform according to a subscription request; the original information is in an XML format or a JSON format;

converting the original information into structural data;

storing the structure data into a corresponding message buffer;

converting the structural data in the message buffer into original data by using a message template;

the sending the information having the target format includes:

and sending the original data to the enterprise information system or the client.

Wherein the original information comprises one or more of:

the method comprises the steps of obtaining part of material main data, enterprise organizational structure topology, capacity generation and planning related data, product research and development related data, inventory data, logistics data, order tracing data, sales data, purchase data and service data.

In a second aspect, an embodiment of the present invention further provides a data processing method applied to a cloud platform, including:

receiving information with a target format sent by a gateway, and storing the information with the target format into a corresponding data pool; or

Acquiring target data to be sent to the gateway, and converting the target data into target data with a target format; and sending the target data with the target format to the gateway.

In a third aspect, an embodiment of the present invention further provides a data processing apparatus, which is applied to a gateway disposed in an enterprise local, and includes:

the acquisition module is used for acquiring original information of a data source;

the conversion module is used for converting the original information into information with a target format;

and the sending module is used for sending the information with the target format.

the conversion module includes:

the first obtaining sub-module is used for obtaining a message according to the original data;

the first storage submodule is used for storing the message into a corresponding message group buffer area;

the first conversion submodule is used for converting the message packet stored in the message packet buffer area into a file with a target format;

wherein the target format comprises an XML format or a JSON format.

Wherein the first obtaining sub-module includes:

the first processing unit is used for filling the original data into a message template with an identification ID (identity) to form a message body;

a second processing unit, configured to form a message header, where the message header includes the ID, a timestamp, a sequence number, and a transmission direction;

and the third processing unit is used for forming the message packet by using the message header and the message body.

Wherein the conversion module further comprises:

the first correlation module is used for configuring a communication protocol under the condition that the data source is an enterprise information system; defining a parameter list to be transmitted; associating the parameter list with a message template;

the second correlation module is used for establishing a table structure in the storage area of the gateway under the condition that the data source is a client; defining a parameter list to be transmitted in the table structure; and associating the parameter list with a message template.

Wherein the first storage submodule comprises:

a first determining unit, configured to determine whether a first message group buffer corresponding to the message packet can store the message packet;

the first storage unit is used for storing the message to a corresponding second message group buffer area when the first message group buffer area can not store the message;

Wherein the first storage submodule further comprises:

the sequencing unit is used for sequencing the message messages in the message group buffer area according to the ID and the serial number of the message messages;

and the deleting unit is used for selecting one message from the repeated message messages to be reserved and deleting other message messages in the repeated message messages, wherein the repeated message messages refer to message messages with the same ID but different message values.

In the uplink direction, the original information is a query request of the client;

the conversion module includes:

the second conversion sub-module is used for converting the query request into a query instruction;

the first filling sub-module is used for filling the query instruction into a corresponding message template to obtain a query message;

the first storage submodule is used for storing the query message into a corresponding message group buffer area;

a third conversion sub-module, configured to convert the query message group stored in the message group buffer into a file having a target format;

wherein the target format comprises an XML format or a JSON format.

The sending module is further configured to send a subscription request of the client to a cloud platform in an uplink direction.

Wherein the conversion module comprises:

the fourth conversion submodule is used for converting the original information into structural data;

the second storage submodule is used for storing the structural data into a corresponding message buffer area;

a fifth conversion sub-module, configured to convert the structure data in the message buffer into original data by using a message template;

the sending module is specifically configured to send the raw data to the enterprise information system or the client.

In a fourth aspect, an embodiment of the present invention further provides a data processing apparatus, which is applied to a cloud platform, and includes:

In a fifth aspect, an embodiment of the present invention further provides a data processing system, including a gateway and a cloud platform that are disposed in an enterprise local; in the uplink direction, the gateway is used for acquiring original information of an enterprise information system or a client, converting the original information into information with a target format, and sending the information with the target format to the cloud platform; in a downlink direction, the gateway is configured to receive target data in a target format sent by the cloud platform, convert the target data into raw data, and send the raw data to the enterprise information system or the client;

in the uplink direction, the cloud platform is configured to receive the information with the target format sent by the gateway, and store the information with the target format in a corresponding data pool; in the downlink direction, the cloud platform is used for acquiring target data to be sent to the gateway and converting the target data into target data with a target format; and sending the target data with the target format to the gateway.

In the embodiment of the invention, the gateway arranged in the enterprise local converts the data of the enterprise information system or the client into the preset format and sends the preset format to the cloud platform, or converts the data sent by the cloud platform and then sends the converted data to the enterprise information system or the client. Therefore, by using the scheme of the embodiment of the invention, the data format can be unified through the local network elements of the enterprises without co-building the upstream and downstream enterprises of the industry chain, thereby solving the problem that the upstream and downstream enterprises of the supply chain cannot exchange data or the data unification workload is overlarge due to non-unified data format, and facilitating the operations of data interaction and the like between the upstream and downstream enterprises of the industry chain.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the description of the embodiments of the present invention will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to these drawings without inventive exercise.

FIG. 1 is a schematic diagram of a data processing system provided by an embodiment of the present invention;

fig. 2 is a structural diagram of a gateway provided in an embodiment of the present invention;

FIG. 3 is a flow chart of a data processing method provided by an embodiment of the invention;

FIG. 4 is a schematic diagram of an association process provided by an embodiment of the invention;

FIG. 5 is a diagram illustrating a data publishing process provided by an embodiment of the invention;

FIG. 6 is a schematic diagram of a data issuing or querying process provided by an embodiment of the present invention;

FIG. 7 is a schematic diagram of a production message group provided by an embodiment of the present invention;

FIG. 8 is a schematic diagram of a development message set provided by an embodiment of the invention;

FIG. 9 is a schematic diagram of a set of inventory messages provided by an embodiment of the invention;

FIG. 10 is a diagram illustrating a set of logistics messages provided by an embodiment of the present invention;

FIG. 11 is a diagram illustrating an order trace message set provided by an embodiment of the present invention;

FIG. 12 is a schematic diagram of a set of sales messages provided by an embodiment of the present invention;

FIG. 13 is a schematic diagram of a set of procurement messages provided by an embodiment of the invention;

FIG. 14 is a schematic diagram of an organization message group provided by an embodiment of the invention;

FIG. 15 is a schematic diagram of an enterprise topology provided by an embodiment of the present invention;

FIG. 16 is a schematic diagram of a service message group provided by an embodiment of the present invention;

fig. 17 is a schematic diagram of a material message group provided by an embodiment of the present invention;

FIG. 18 is a second schematic diagram of an enterprise topology according to an embodiment of the present invention;

fig. 19 is a schematic diagram of a process of generating a message according to an embodiment of the present invention;

FIG. 20 is a diagram illustrating parameter association via configuration provided by an embodiment of the invention;

fig. 21 is a schematic diagram of ordering and de-duplicating message packets according to an embodiment of the present invention;

fig. 22 is a schematic structural diagram of a message provided in the embodiment of the present invention;

fig. 23 is a schematic diagram illustrating an arrangement manner of message packets in a message group buffer according to an embodiment of the present invention;

fig. 24 is a diagram illustrating message packet processing by a message group buffer according to an embodiment of the present invention;

FIG. 25 is a state machine switching diagram provided by an embodiment of the present invention;

fig. 26(a) is a schematic diagram of a message group provided by an embodiment of the present invention;

fig. 26(b) is a schematic diagram of a message in XML format provided by an embodiment of the present invention;

FIG. 27 is a flow chart of message reception provided by an embodiment of the present invention;

FIG. 28 is a flow diagram of message subscription settings provided by an embodiment of the invention;

fig. 29 is a flowchart of a gateway processing data returned by a cloud platform according to an embodiment of the present invention;

FIG. 30 is a block diagram of a data processing apparatus according to an embodiment of the present invention;

FIG. 31 is a schematic diagram of a conversion module provided by an embodiment of the present invention;

FIG. 32 is a schematic diagram of a first acquisition submodule provided in an embodiment of the invention;

FIG. 33 is a second schematic diagram of a conversion module according to an embodiment of the invention;

FIG. 34 is a schematic diagram of a first storage submodule provided in an embodiment of the invention;

FIG. 35 is a third schematic diagram of a conversion module according to an embodiment of the present invention;

FIG. 36 is a fourth schematic diagram of a conversion module according to an embodiment of the present invention;

FIG. 37 is a second block diagram of a data processing apparatus according to an embodiment of the present invention;

FIG. 38 is a third block diagram of a data processing apparatus according to an embodiment of the present invention;

FIG. 39 is a fourth block diagram of a data processing apparatus according to an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. 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 invention.

Referring to fig. 1, fig. 1 is a schematic diagram of a data processing system according to an embodiment of the present invention. In fig. 1, the system may include: a gateway 101 and a cloud platform 102.

In the uplink direction, the gateway 101 is configured to obtain original information of an enterprise information system or a client, convert the original information into information with a target format, and send the information with the target format to the cloud platform; in a downlink direction, the gateway 101 is configured to receive target data with a target format sent by the cloud platform, convert the target data into raw data, and send the raw data to the enterprise information system or the client;

in the uplink direction, the cloud platform 102 is configured to receive the information with the target format sent by the gateway, and store the information with the target format in a corresponding data pool; in the downlink direction, the cloud platform 102 is configured to obtain target data that needs to be sent to the gateway, and convert the target data into target data in a target format; and sending the target data with the target format to the gateway.

Further, the system may also include enterprise information systems, clients, and the like.

In practical application, the gateway collects the original data from the enterprise local information system at regular time and converts the original data into message messages. The message messages are grouped in the gateway and packed into an XML (Extensible Markup Language) file, and then the XML file is sent to the cloud platform according to specific conditions.

The cloud platform opens up an independent data pool for the supply chain system of each industry. And the cloud platform unpacks the XML file and stores the unpacked XML file in a virtual data pool of a supply chain system to which the enterprise belongs. Data in the virtual data pool comes from enterprises upstream and downstream of the supply chain. Members of the enterprise of the supply chain system may access the affiliated virtual data pool to obtain data. If a certain vehicle and enterprise supply chain comprises whole car factories, suppliers at all levels, logistics suppliers, 4S sales shops and even customer or vehicle data from the Internet of vehicles. Multiple independent virtual data pools can be deployed in the cloud platform to serve different supply chain system enterprises simultaneously.

There are two ways for enterprises to obtain data.

One way is data subscription. The enterprise sets the type and sending period of the subscribed messages in the cloud platform, and the cloud platform packages the messages into XML files and sends the XML files to the subscribed gateways after the conditions are met.

The second way is data querying. The client sends a query request through the gateway, and the gateway converts the query request into a query message. And the query message is grouped in the gateway according to the message group and packaged into an XML file to be sent to the cloud platform. And the cloud platform packages the message into an XML file according to the content of the request message and returns the XML file to the gateway sending the query request. And after the XML file returned by the cloud platform reaches the gateway, the gateway converts the XML file into a standard message group and puts the standard message group into a corresponding message group buffer area. Messages in the message group are in turn reverse mapped back to the original data via the message template and returned to the enterprise information system.

The gateway plays a key role in data uploading, data transmission, conversion and storage in the system. Specifically, with reference to fig. 1, the gateway 101 may include: a superior communication protocol stack (or called superior interface driver stack), a data processing module, a subordinate communication protocol stack (or called subordinate interface driver stack), a Web server, etc.

Fig. 2 is a schematic diagram of a specific structure of a gateway in an embodiment of the present invention. Wherein, the data processing module can include: message template, message buffer queue, message group buffer area, XML processing module, etc.

The lower interface drive stack is connected with the enterprise information system, supports various drive protocols, and can read and write original data from the enterprise information system at regular time. The lower driver interface stack provides various Protocol drivers such as OPC (OLE for Process Control ) UA (Unified Architecture), TCP (Transmission Control Protocol)/IP (Internet Protocol), Profinet, etc., and can read and write original data from the enterprise information system in a configuration manner.

The message template in the gateway is the core module of message processing. The message templates are internally provided with a plurality of message formats and are responsible for transmitting the original data to corresponding positions of the message templates and converting the original data into standard message messages or converting the message messages into the original data. After the message template of the cloud platform is updated, the message templates in all the gateways can be automatically updated.

The message template defines multiple types of message messages in advance, and the messages are divided into different message groups according to the message IDs. The message groups are classified according to functions, such as production, research and development, inventory, logistics, purchase, sales, service, material, organizational structure, traceability and the like.

Wherein the structure of a single message is defined in the message template. The message includes a message header and a message body. The message header contains the message ID, message sequence number, timestamp, priority and direction. The message body contains a plurality of data parameters to be transmitted. The message body of each message type contains parameters that have been predefined. The message ID includes a message group number (2-bit 16-ary number) and a message number (2-bit 16-ary number), for example, where the message ID is 010A, the message group number is 01, and the message number is 0A. The message sequence number is represented by a 4-bit 16-system number, and is increased by 1 each time, and the next cycle is entered after the maximum value is reached. The priority is represented by a 1-bit 16-ary number, with a larger value representing a higher priority. The direction is represented by a 1-bit 16-ary number, with 1 representing the input direction and 2 the output direction.

The system allows mapping of raw data through a GUI (Graphical User Interface) into specific parameters of a message template for a specific message ID, a specific direction (incoming or outgoing message), and allows changing the priority of the message. After the original data is filled, the message template automatically adds the current time stamp and the unique message serial number to the message and generates a message.

The message messages enter a message buffer queue in sequence.

The message buffer queue is a FIFO (First Input First Output) buffer queue between the message template and the message group buffer, and is divided into Input and Output queues. And the message buffer queue respectively sends the messages to different message group buffer areas according to the message ID in the message.

The message group buffer zone presets a dynamic buffer zone for each message group, and the messages from the message buffer queue enter the corresponding message group buffer zone according to the message group marks to wait for packing and sending. Meanwhile, the XML message from the upper level enters the buffer area to wait for being sent to the message buffer queue after being converted. Each message group is dynamically allocated with 4 buffers, an input master buffer, an output master buffer, an input slave buffer and an output slave buffer. Wherein the master and slave buffers may be switched to each other by the switching engine.

The message enters a message group buffer area to be sorted and deduplicated. Each message group buffer may individually set transmission or reception trigger conditions such as timing, message quantity overrun, urgency priority, etc. When the condition is satisfied, the message group buffer area for outputting automatically sends all message messages in the group to the XML processing module, and the message group buffer area for inputting automatically sends the message to the message buffer queue.

And the XML processing module packs the message from the message group buffer area into an XML file or unpacks the XML file from the cloud platform and then puts the XML file into the message group buffer area. The XML processing module may also be a JSON (JSON Object Notation) processing module, that is, in the embodiment of the present invention, the data interacted between the gateway and the enterprise may be in an XML format or a JSON format.

The upper-level interface driver stack provides an output buffer and a communication protocol with the platform, and can send the XML file from the XML processing module to the cloud platform or receive the file from the cloud platform and send the file to the XML processing module.

The system of the embodiment of the invention can also comprise a Web Server (Server), thereby supporting the client to publish manually maintained data (such as EXCEL documents) or enterprise information systems (such as supporting only a private communication protocol) which are difficult to access the gateway.

The Web server comprises a data storage area and an instruction processing module. The user leads the data into the Web server of the gateway through the client, and the gateway decomposes the data into message messages and issues the message messages to the platform. Specifically, the Web server may receive a query request from a client. The instruction processing module converts the query request into one or more query instructions and sends the query instructions to the message template. The message template converts the query instruction into a query message and then sends the query message to the message buffer queue. The returned message can be selected to enter the enterprise information system or be stored locally, and the data is returned to the client according to the requirement of the client. The instruction processing module can also send the query instruction to the message template according to the set timing.

Because the information systems, data formats and business processes used by enterprises are different, and it is very difficult to directly access the enterprise systems to the platform, a gateway deployed in the enterprise can be used, and complicated data processing work can be simplified. Meanwhile, the gateway provides a plurality of communication protocol drivers, provides dynamic configuration capacity and data processing capacity, can directly read data from the enterprise information system, convert the data into a standard format required by the cloud platform and send the standard format, and can also convert the data from the platform into an enterprise self-owned data format and push the data into an enterprise IT system. Some data from the cloud platform cannot be directly accessed into the IT system, and needs to be independently processed or exported into standard formats such as Excel, Word and the like for archiving and analysis. Therefore, the gateway is also provided with a local data storage and a Web server, data can be selectively stored in the local storage of the gateway, and a client can view or archive the data on line when needed. Meanwhile, the client can also directly release data to the cloud platform through the Web server.

Referring to fig. 3, fig. 3 is a flowchart of a data processing method according to an embodiment of the present invention, and as shown in fig. 3, the method includes the following steps:

step 301, acquiring original information of a data source.

In the upstream direction, the data source comprises an enterprise information system or a client; in the downstream direction, the data source comprises a cloud platform. The original information may comprise original data or a message, etc.

Step 302, converting the original information into information with a target format.

In the uplink direction, the original information is original data to be published by the message enterprise information system or the client. In this step, a message packet may be obtained according to the original data, and the message packet may be stored in a corresponding message group buffer. Then, converting the message packet stored in the message packet buffer into a file with a target format; wherein the target format comprises an XML format or a JSON format.

In the process of obtaining the message according to the original data, the original data can be filled into a message template with an identification ID to form a message body. And then forming a message header, wherein the message header comprises the ID, the timestamp, the sequence number and the transmission direction, and finally forming the message packet by using the message header and the message body. In addition, the header may also include a priority.

In addition, in order to improve the data processing efficiency, the original data and the template can be associated before the data message is obtained. Specifically, the association process may include: and configuring a communication protocol under the condition that the data source is an enterprise information system. And then, defining a parameter list to be transmitted, and associating the parameter list with the message template. And under the condition that the data source is a client, establishing a table structure in the storage area of the gateway. Then, defining a parameter list to be transmitted in the table structure; and associating the parameter list with a message template.

And determining whether the first message group buffer area corresponding to the message can store the message or not in the process of storing the message into the corresponding message group buffer area. Wherein, when any one of the following conditions is satisfied, it is determined that the first message group buffer cannot store the message packet: the timing time of the first message group buffer is up; the number of the message messages stored in the first message group buffer zone reaches a preset value; the first message group buffer zone comprises message messages with the priority meeting the preset requirement. And when the first message group buffer area can not store the message, storing the message into a corresponding second message group buffer area.

After storing in the message group buffer, the message packet can be further processed. For example, in the message group buffer, message packets are sorted according to their IDs and sequence numbers. Selecting one message from the repeated message messages to be reserved, and deleting other message messages in the repeated message messages, wherein the repeated message messages refer to message messages with the same ID but different message values.

In addition, in the uplink direction, the original information is the query request of the client. In this case, the step may specifically be: and converting the query request into a query instruction, and filling the query instruction into a corresponding message template to obtain a query message. The query message is then stored in a corresponding message group buffer. Then, converting the query message group stored in the message group buffer into a file with a target format; wherein the target format comprises an XML format or a JSON format.

In addition, in the embodiment of the present invention, sending a subscription request of the client to a cloud platform may also be included.

In a downlink direction, the original information comprises data returned by the cloud platform according to the query message or data returned by the cloud platform according to the subscription request; the original information is in an XML format or a JSON format. This step may specifically be to convert the original information into structure data and store the structure data in a corresponding message buffer. And then, converting the structural data in the message buffer into original data by using a message template.

And step 303, sending the information with the target format.

In the uplink direction, the gateway sends information with a target format to the cloud platform; in the downstream direction, the gateway sends information in the target format to the enterprise information system or client.

In the uplink direction, the information in the target format may be, for example, information in an XML or JSON format, and in the downlink direction, the information in the target format is raw data that may be received by an enterprise information system or a client.

In an embodiment of the present invention, the original information includes one or more of the following items:

part of material master data, enterprise organizational structure topology, capacity generation and planning related data, product research and development related data, inventory data, logistics data, sales data, purchase data and service data.

Wherein, partial material main data: if supply chain downstream enterprises need to use manufactured products of upstream enterprises as raw materials, the downstream enterprises need to have information related to the materials, and the upstream enterprises need to upload the information to a cloud platform in advance to serve as basic main data.

Enterprise organizational structure topology: the organization structure of the enterprise comprises a production factory, a workshop, a warehouse and the like. Enterprises need to upload all the hierarchical relationships of production factories, production workshops, warehouses and the like of the enterprises to the platform as basic main data.

Production capacity and plan related data: in order to coordinate production upstream and downstream, each enterprise needs to release its own production capacity, forecast plans, etc. for each material to the platform for other enterprises to view. Other enterprises may be allowed to reserve future capacity for their own use.

Product development related data: the upstream enterprise and the downstream enterprise share the product data, so that the downstream enterprise can conveniently check the design data of the upstream enterprise to adjust own process, and simultaneously can put forward own requirements for the upstream enterprise or carry out collaborative research and development.

Stock data: the downstream enterprise can visually see the inventory of the upstream enterprise to adjust its own production and procurement plans. Meanwhile, the upstream enterprise can also check the warehouse condition of the downstream enterprise in real time to adjust the production plan of the upstream enterprise. For special production modes such as consignment and outsourcing, an enterprise can manage inventory located in other enterprises as well as managing its own local inventory.

Logistics data: the enterprise can visually check the daily available resources of the logistics enterprise and perform a series of processes such as reservation, ordering, order tracking and the like, and the supply of raw materials and the instant transportation of finished products are ensured, so that the JIT production is realized.

Production order tracing data: and finally, a client or a downstream enterprise can trace the production order in real time, know the latest production progress, predict the delivery date and trace the quality and the production of a single product. All product production parameters and quality inspection parameters are associated with order numbers, product serial numbers, batch numbers, and the like.

Sales data: the production enterprise can know the real-time sales condition of the third party sales company or the downstream company so as to adjust the production plan, the storage, the logistics and the like.

And (3) purchasing data: the upstream enterprise can know the purchasing plan and purchasing requirement of the downstream enterprise in time. Downstream enterprises can issue purchasing bidding information, and upstream enterprises can conduct real-time bidding through the system. Meanwhile, purchase orders, purchase agreements, bills, electronic invoices and the like can also be interacted in the system.

Service data: the upstream enterprise knows the service requirement of the downstream enterprise in real time, and the equipment use operation condition, and carries out timely online or offline service on the downstream enterprise. Meanwhile, the spare part requirement condition of a downstream client can be confirmed according to real-time operation data and service records of the equipment, and the capacity, the inventory and the logistics of the spare parts can be adjusted in time.

The embodiment of the invention also provides a data processing method which is applied to a cloud platform and comprises the following steps:

Taking the example that the gateway and the cloud platform of a certain enterprise interact the above information, a data interaction process is described.

The process may include:

(1) gateway data association process:

referring to fig. 4, the association process may include:

it is confirmed whether the data required to send or receive the message is from the enterprise information system or the client. And configuring a communication protocol under the condition that the data source is an enterprise information system. And then, defining a parameter list to be transmitted, and associating the parameter list with the message template. And under the condition that the data source is a client, establishing a table structure in the storage area of the gateway. Then, defining a parameter list to be transmitted in the table structure; and associating the parameter list with a message template.

(2) And (3) data release process:

referring to fig. 5, the data publishing process may include:

first, the relevant configuration process and the data import process are executed. The configuration process includes setting the refresh time of the parameter group read from the enterprise information system, the refresh time of each message group buffer, the maximum message number, the priority setting of each message, and the like. The data import process refers to importing data into a table of a data storage area through a client.

And judging whether the refreshing time is reached. If not, the system continues waiting and receives data. And if so, converting the original data into a message according to the association relation, and storing the message into a message cache queue. And the message messages enter different message group buffers according to the ID.

The message packets are then reassembled in the message group buffer, e.g., sorted, de-duplicated, etc. When the sending condition of the message group buffer is satisfied, the message messages in the message group buffer can be packed. And then, sending the packaged message to the cloud platform.

The sending condition may be, for example: the timing time of the message group buffer is up; the number of the message messages stored in the message group buffer zone reaches a preset value; the message group buffer zone comprises message messages with the priority meeting the preset requirement.

(3) Data distribution or query

The cloud platform may return the queried data to the gateway according to the query request, or may also return the subscribed data according to the subscription.

Referring to fig. 6, the data issuing or querying process may include:

for the message subscription process, first, the gateway may perform message subscription configuration. And the uploaded message is stored in the cloud platform. The gateway can use a message subscription function to configure what messages are sent to a specified gateway at what times. And after the subscription condition is met, the cloud platform automatically sends the subscribed message to the corresponding gateway.

And if the subscription time is up, the cloud platform packs the message messages according to the message groups and sends the packed message messages to the gateway.

For the query request or instruction of the gateway, the gateway may actively send the query request to the cloud platform request message. The query request can be sent by the client, the Web server of the gateway automatically converts the query request into a query instruction after receiving the query request, and then the message template converts the query instruction into a query message and sends the query message to the cloud platform. The Web server of the gateway can also automatically send out a query instruction according to the setting, convert the query instruction into a query message by the message template and send the query message to the cloud platform. And then, the cloud platform packs the query result according to the message group according to the query message and sends the query result to the gateway.

And when the gateway receives the message or the result sent by the cloud platform, unpacking the packed message group and then storing the unpacked message group into a corresponding message group buffer area. And storing the single message into the message buffer queue after the sending condition of the message group buffer is met.

And the messages in the message buffer queue enter a message template, and original data are disassembled by the message template by utilizing a predefined incidence relation. And for the original data to be sent to the enterprise information system, the original data is sent to the bottom layer protocol stack and sent to the enterprise information system. And for the original data to be sent to the client, the original data is sent into a table structure which is established in advance in a gateway storage area, and then the original data is published to the client through a Web server.

In another embodiment of the present invention, it is assumed that a certain automobile industry integrates a whole industry chain, and it is difficult to achieve a lateral flow of data due to inconsistency of respective enterprise management systems, business processes, data formats, and the like. The automotive industry chain includes the following major types of enterprises: the whole vehicle assembly plant, the primary supplier, the secondary supplier, the raw material supplier, the logistics company and the 4S sales shop. Each enterprise exchanges respective key data through the gateway and the cloud platform, so that the minimum inventory, the maximum equipment utilization rate, the transparentization of orders, the minimum management cost, the minimum delivery period, the configurability of orders and the like are realized. The following description is the case of data interaction of each enterprise through the system. The process may include

Firstly, each enterprise issues and queries productivity through a production message group type message, and the method comprises the following steps:

each enterprise publishes the current capacity condition of the enterprise to the cloud platform, and each message corresponds to one material. Each message group may contain messages of multiple items (message ID 0101).

Each enterprise can release its own short-term, medium-term and long-term available capacity, and the release time N can be freely defined in the message (

message ID

0102, 0103, 0104).

Other enterprises can inquire one or more of current capacity, short-term capacity, medium-term capacity and long-term capacity through the inquiry message. The period N of the query can also be freely defined (message ID 01 FF).

The enterprise can reserve the capacity of the upstream provider (with the message ID 0105), and the upstream provider responds to the confirmation after the reservation is successful (with the message ID 0106).

Fig. 7 is a schematic diagram showing the specific content of each message.

Secondly, each enterprise exchanges material research and development data through research and development message groups, and the research and development data comprises the following steps:

the design file sending and receiving are two-way message messages. Each material constitutes a message, and the message contains the ID and the link of the design file. The receiver can access the design file (message ID 0201) stored on the server through the link.

The downstream enterprise sends a request for a design file change to the upstream enterprise, which may include a plurality of links describing the attributes and the original file. Using the attribute mode description facilitates structured storage at the server (message ID 0202).

The upstream enterprise may respond to the design file change request of the downstream enterprise to confirm whether each description item required by the downstream enterprise can be modified, while sending a link of the original file (message ID 0203). After negotiation, the upstream enterprise sends a design file change confirmation message to the downstream enterprise (message ID 0206).

The upstream enterprise issues an update prompt after updating the design file, and the message includes the updated design file ID and link (message ID is 0204). If necessary, the upstream enterprise can update the change progress of the design file periodically (message ID is 0205).

Authorized enterprises can send design file acquisition requests, acquire design files through different request IDs, and change the progress of the design files. If the request ID is 1: design file, request ID 2: the design file change progress (message ID 0207).

Fig. 8 is a schematic diagram showing the specific content of each message.

Thirdly, each enterprise exchanges inventory data through an inventory message group, and the method comprises the following steps:

the total inventory status generates a message for the current inventory status of each item. The total inventory timing is issued by the inventory owner to the cloud platform (message ID 0301).

The inventory owner may choose to publish the inventory status of each actual warehouse to the cloud platform. The inventory type may be regular inventory, consignment inventory and consignment inventory (message ID 0302).

The inventory owner may choose to publish inventory forecasts within N days to the cloud platform. Inventory forecast calculates all inventory in transit (message ID 0303).

An authorized enterprise may query some inventory holder for inventory (query message ID 0304, return message ID 0302).

An authorized enterprise may query the current total inventory of a material and future N days of inventory that take into account in-transit inventory conditions. (Inquiry message ID 0305 Return message ID 0301, 0303)

Fig. 9 is a schematic diagram showing the specific content of each message.

And fourthly, the logistics enterprise exchanges logistics data with each enterprise through a logistics message group, and the method comprises the following steps:

order information is exchanged between the logistics enterprises and the entrusting parties through messages, and the orders are conveniently stored in a structured mode (the message ID is 0401).

The logistics enterprise updates the order status to the platform in time through the order status message (message ID 0402).

The logistics enterprise and the client can exchange the framework protocol (message ID 0403) by means of message.

After the client sends the logistics order or agreement, the logistics enterprise can confirm the order or agreement with a message (message ID 0405).

After the client checks the available logistics resources of the logistics enterprise, the logistics resources can be reserved (message ID 0406). The logistics enterprise confirms the reservation according to the current resource allocation status (message ID 0407).

Authorized clients can query different logistics resources by querying the ID. If the query ID is 01, querying the logistics order (the return message ID is 0401) and the order status (the return message ID is 0402); query ID 02, query framework protocol (return message ID 0403); query ID 03, query physical distribution resource (return message ID 0404), and the like.

Fig. 10 is a schematic diagram showing the specific content of each message.

Fifthly, the downstream enterprises can track the execution condition of the orders through the order tracing message group, and the method comprises the following steps:

the order progress message is used for order publishing and query feedback. A predicted delivery route including a certain order number, a position currently located on the delivery route, a predicted completion time, an actual completion time, and the like (message ID 0501).

The quality message is used to issue and query all quality check data for a certain order or a certain product number (message ID 0502).

The production operation message is used for publishing and feeding back all production parameters of a certain order, and optionally a certain product serial number. Each message contains parameters for only one process. Multiple procedure parameter transmission and reception requires multiple messages of this type (message ID 0503).

The material message is used to issue and feed back a raw material serial number (message ID 0504) used for a certain product serial number.

The order associated sequence number message is used to associate a sequence number of a certain material used by a certain order with the order number. The same order generates multiple messages if multiple items are needed (message ID 0505).

The product tracing query message can query the order related information according to the query control ID. If the query ID is 1, querying the order progress; inquiring the quality parameter of a certain product serial number when the ID is 2; inquiring the production operation parameters of a certain product serial number if the ID is 3; inquiring the material serial number used by a certain product serial number if the ID is 4; and 4, inquiring all product serial numbers associated with a certain order (the message ID is 05 FF).

Fig. 11 is a schematic diagram showing the specific content of each message.

And sixthly, the upstream enterprise can track the sales condition of the downstream enterprise through the sales message group so as to adjust the productivity. If the whole car factory tracks the sales condition of the 4S shop, the accessory factory tracks the sales condition of the whole car factory.

The sales plan message supports publication and query feedback for any number of months (designated by N) of sales plans (message ID 0601).

The sales inventory message may support inventory number distribution and query feedback for any number of product quantities (specified by N) (message ID 0602).

The sales order message supports interaction of sales orders using messages to facilitate structured storage (message ID 0603).

The material message is used to issue and feed back a raw material serial number (message ID ═ 0604) used by a certain product serial number.

The bill and the invoice are used for sending bill information and electronic invoice. The bill information is directly sent in a message form, and the electronic invoice is sent in a link form (message ID is 0605).

The sales query is used to authorize the enterprise to query the aforementioned information based on the query ID. If the query ID is 01, querying the sales plan of the specified date, and if the query ID is 02, querying the sales inventory of the specified product; inquiring the product configuration of the specified order number and the like when the ID is 03; the inquiry ID is 04, and the bill, invoice, and the like of the specified order are inquired (the message ID is 06 FF).

Fig. 12 is a schematic diagram showing the specific content of each message.

And seventhly, the downstream enterprises can exchange purchase information with the upstream enterprises through the purchase message group.

The procurement plan message supports publication and query feedback for any number of weeks (specified by N) of procurement plans (message ID 0701).

The purchase bid message is used for posting and query feedback of the bid. The main attribute of the bid is sent in the message, and the message is accompanied by a bid file link (message ID 0702).

The bid quotation message is used for receiving bid quotation messages from other enterprises, the main attributes of the tender are sent in the messages, and meanwhile, the message messages are attached with tender file links (message ID is 0703).

Alternatively, the enterprise may choose to confirm the tender directly to the network and send a bid offer confirmation message (message ID 0704).

The purchasing party and the supplying party can negotiate and interact through a purchasing framework protocol message and formulate a purchasing framework protocol (message ID is 0705).

The purchasing party and the supply party can directly transmit the purchase order in a message mode, the main attribute of the purchase order is transmitted in the message, and meanwhile, a file link of the purchase order is attached to the message (the message ID is 0706).

The purchasing party may specify configuration attributes, such as different configurations of the vehicle, for a single product in the purchase order (message ID 0707).

The purchasing party and the supplying party can exchange the order and the electronic invoice in a message mode (the message ID is 0708).

The purchasing party and the supplying party can confirm the order or the purchasing agreement in a message mode.

The purchase query actively queries the aforementioned information according to the query ID. If the query ID is 01, querying a purchasing plan; inquiring the purchase bid when the ID is 02; inquiring bid quotations when the inquiry ID is 03; inquiring the purchasing framework protocol when the inquiry ID is 04, inquiring the purchasing order when the inquiry ID is 05; inquiring about the purchased material configuration if the ID is 06; inquiring the ID to be 07, inquiring bills and invoices and the like; (message ID: 07 FF).

Fig. 13 is a schematic diagram showing the specific content of each message.

And eighthly, the organization structure of the enterprise is important main data of the whole supply chain.

Referring to fig. 14, a diagram illustrating the detailed contents of each message of the message group is shown. Referring to fig. 15, a schematic diagram of a node topology is shown. The topology includes root node-current node-father node-child node 1-child node 2- … … -child node N.

Each enterprise will upload its topology as shown in fig. 15. The topological structure is a layered tree structure, the top layer is a company layer or a group company layer, and a branch company, a factory, a warehouse and the like are arranged below the topological structure. Each node needs to be represented by a unique ID. The top company root ID is uniquely assigned in the supply chain, and the IDs of other nodes are encoded by taking the root ID as the start to ensure the uniqueness of the whole supply chain. The organization message group is used for publishing and querying the organization structure of the feedback company.

A node description message is used to publish or feed back to a node in an organizational structure. Each node has a unique ID, a unique following node and one or more child nodes (message ID 0801).

The query message is organized for querying information of one or more nodes. Inquiring information of all nodes when the inquiry ID is 01, and returning all node information under the company ID; and querying the information of the specified single node, wherein the query ID is 02.

And ninthly, the service message group publishes the message related to the feedback service.

The service record message is used to issue and feed back service record information for a certain service ticket (message ID 0901).

The spare part requirement message is used to issue and feed back requirement information for a certain spare part (message ID 0902).

The service requirement message is used to publish and feed back a service requirement message (message ID 0903).

The product use condition message is used for publishing the real-time operation condition of the product, so that a manufacturer can find out the potential service requirement and spare part requirement condition in time, for example, the operation data of the vehicle is fed back in real time through the internet of vehicles (message ID ═ 0904).

The service inquiry provides the authorized party with inquiry information according to the inquiry ID. If the query ID is 01, querying the service record; inquiring the spare part requirement, wherein the ID is 02; inquiring the service requirement when the inquiry ID is 03; inquiring the product use condition when the ID is 04; (message ID 09 FF).

Fig. 16 is a schematic diagram showing the specific content of each message.

And tenthly, releasing and feeding back the material data through a material message group.

The material data is represented by a tree-shaped BOM, and the finished product is a root node. Each manufacturer needs to publish the material data produced by itself to the platform, and optionally, they can choose to publish only the material attribute of the final product or publish the complete material BOM according to the needs.

The material description message is used to publish and feed back an attribute for a certain specific material (message ID 0a 01).

The node description message is used to publish and feed back information containing the material BOM (message ID 0a 02).

The material query message may query for material-related information based on the query ID. If the query ID is 01, querying the complete BOM of a certain material; inquiring the complete attribute of a certain finished product if the ID is 02; inquiring information of all materials of a certain supplier if the inquiry ID is 03; (message ID ═ 0 AFF).

Fig. 17 is a schematic diagram showing the specific content of each message. Referring to fig. 18, a schematic diagram of a node topology is shown. The topology includes root node-current node-father node-child node 1-child node 2- … … -child node N.

The data interaction process of the embodiment of the invention can comprise the following steps:

step 1801, read the data from the local system and reassemble the message.

Referring to fig. 19, the process may include: the driving interface of the gateway supports various protocols for communication with a third-party system (enterprise information system), such as OPC UA and the like. First, the message parameters are associated with the message parameters of the enterprise information system through a configuration interface. In addition, preset parameters of the gateway data storage area can be associated with message parameters through configuration. Each parameter group can set the timing updating time respectively, and the gateway refreshes the value of each variable according to the set timing.

When the timing time is up, the gateway reads the configured parameters from the enterprise information system or the data storage area, fills the read parameters into the corresponding message template with the ID, adds the timestamp and the sequence number into the message template and caches the message template in the message queue. And then, sending the message into a message group buffer according to the ID. Parameter values read from the enterprise information system or local storage are automatically populated into the message template. Each message template has a unique ID, where

bits

1 and 2 of the ID are the message group number and

bits

3 and 4 are the message number. And after the parameter values required by the message template are updated, adding a timestamp and a sequence number to generate a message. And the message enters a corresponding message group buffer area according to the first two message group numbers of the ID.

Fig. 20 is a schematic diagram illustrating parameter association by configuration in the embodiment of the present invention. The data of the respective enterprise system are first mapped to the respective variables via the enterprise information system OPC UA mapping parameters. Each variable is then mapped to a different parameter of a different message template. Finally, mapping each parameter in the message template to a gateway data storage area structure type database.

Step 1802, sort the messages in the message group, and delete duplicate messages.

Referring to fig. 21, this step may include: the new messages are sorted into the message group buffer in the manner shown in figure 23. The messages with the same message ID are arranged from small to large according to the sequence number. In order to save bandwidth and memory space, if the two messages in the message group buffer are identical except for the timestamp and the sequence number, the incoming message is discarded.

Fig. 22 shows a structure of a message packet in the embodiment of the present invention. The message comprises a message head and a message body, wherein the message head comprises a message ID, a message sequence number, a timestamp, a priority, a direction and the like. The message ID includes a message group number (2-bit 16-ary number) and a message number (2-bit 16-ary number), for example, where the message ID is 010A, the message group number is 01, and the message number is 0A. The message sequence number is represented by a 4-bit 16-system number, and is increased by 1 each time, and the next cycle is entered after the maximum value is reached. The priority is represented by a 1-bit 16-ary number, with a larger value representing a higher priority. The direction is represented by a 1-bit 16-ary number, with 1 representing the input direction and 2 the output direction.

Fig. 23 is a schematic diagram showing an arrangement manner of message packets in a message group buffer.

Step 1803, message group buffer processes message.

Referring to fig. 24, this step may include: the timing time of the message group buffer is set according to the type of each message group, and may be from several seconds to several hours. At the same time, to optimize the use of the network, it is possible to allow a limitation of the maximum number of messages carried per template. When the number of messages in a certain message group buffer reaches the maximum value, the messages are sent out even if the timing time is not up. If there are messages in the message group with high response time requirement (the priority is larger than a certain threshold), the buffer can be set to process the messages immediately after the messages appear.

Referring to fig. 25, a diagram of a buffer switch state machine is shown. 2 pairs of buffers are respectively set for each message template in the message buffer, namely a main input buffer, a main output buffer, a slave input buffer and a slave output buffer. Taking output as an example, when the number of messages in the buffer reaches a limit value or a timing time is up or a message with high priority appears, the program needs to process all messages, generate an XML file and send the XML file to an output queue. During this time the master slave buffer switch engine freezes the master buffer and switches the slave buffer to the master buffer in order not to miss new incoming messages. All new messages automatically enter the new main buffer. And after the main buffer finishes processing the message, automatically eliminating the frozen state and switching to the auxiliary buffer. The repeated circulation realizes the uninterrupted processing of the message.

Referring to fig. 26(a) and (b), a schematic diagram of a process for reassembly of message group buffer messages into XML is shown. The message group buffer organizes all messages into an XML file for transmission. Fig. 26(a) is a relatively simple message group including three messages, and the message IDs are 0101, 0101, and 0102, respectively. Messages of the same ID may appear multiple times in a message group, distinguished by different sequence numbers. The messages in the message group are firstly sorted according to the message ID, and when the message IDs are the same, the messages are sorted according to the sequence number. The generated XML file uses the same format as the template stored by the cloud platform, as shown in fig. 26 (b). The first level is a message group, within which a message group ID is defined. The second level is messages, each containing a number of elements including message ID, sequence number, timestamp, priority, direction, and in addition various parameters in the message body. And after the message template in the cloud platform is updated, the XML generation template stored in each gateway can be automatically updated.

And 1804, sending the XML file to the cloud platform.

Referring to fig. 27, a flow chart of message reception according to an embodiment of the present invention includes:

the client sends a query request to the gateway according to the operation condition, and the gateway can also be set to initiate query at regular time to update the local database. And after receiving the query request or the timing time is up, the gateway automatically sends a query instruction to the message template. The message template converts the query instruction into a query message and sends the query message to the message buffer queue. The next steps are the same as the sending process, the query message enters a message group sending buffer area, and when the waiting condition is met, the query message and other messages of the message group are converted into an XML file and sent to the cloud platform.

Referring to fig. 28, a flowchart of message subscription setting according to an embodiment of the present invention includes:

besides actively sending the query message, the client can also directly log in the cloud platform for message subscription. Messages needing to be subscribed are configured in the message list, and the automatic message sending can be triggered to start after the sending time interval is set and the validity period of the subscription is selected. The cloud platform automatically sends corresponding messages to the local gateway according to the set conditions.

Referring to fig. 29, a flowchart of processing data returned by the cloud platform by the gateway according to the embodiment of the present invention includes:

and after receiving the query message or when the subscribed message meets the sending condition, the cloud platform sends the message group to the gateway in an XML mode according to the preset setting.

The XML file is first converted into structured data in the XML processing module and stored in the input message group buffer. And sending the message to the input message buffer queue after the condition is met. During which the master slave buffer switching engine freezes and unfreezes the message group buffers according to the aforementioned mechanism to ensure continuous reception of messages.

The system converts the message into original variable data according to the incidence relation between the original data and the message in the message template, and sends the original variable data to the enterprise information system or stores the original variable data in a local structural database through a protocol stack.

As can be seen from the above, in the embodiment of the present invention, a message mechanism for data uploading and sending by upstream and downstream enterprises of a supply chain through a gateway and a cloud platform is defined, which facilitates data sharing between enterprises. Meanwhile, the gateway processes the data and maps the original data in the enterprises into predefined message messages, thereby solving the problems that the data formats between the enterprises are not uniform so that the exchange is impossible or the workload of data unification is overlarge.

The embodiment of the invention also provides a data processing device which is applied to the gateway arranged in the enterprise local. Referring to fig. 30, fig. 30 is a block diagram of a data processing apparatus according to an embodiment of the present invention. Because the principle of the data processing device for solving the problem is similar to the data processing method in the embodiment of the present invention, the implementation of the data processing device can refer to the implementation of the method, and repeated details are not repeated.

As shown in fig. 30, the data processing apparatus 300 includes: an obtaining module 3001, configured to obtain original information of a data source; a conversion module 3002, configured to convert the original information into information having a target format; a sending module 3003, configured to send the information with the target format.

In the uplink direction, the original information is original data to be published by the message enterprise information system or the client. Referring to fig. 31, the conversion module 3002 includes:

a first obtaining submodule 3021, configured to obtain a message according to the original data; the first storage submodule 3022 is configured to store the message packet in a corresponding message group buffer; a first conversion submodule 3023, configured to convert the message packet stored in the message group buffer into a file having a target format; wherein the target format comprises an XML format or a JSON format.

Referring to fig. 32, the first acquisition sub-module 3021 includes:

a first processing unit 30211, configured to fill the original data into a message template with an identification ID to form a message body; a second processing unit 30212, configured to form a message header, where the message header includes the ID, a timestamp, a sequence number, and a transmission direction; a third processing unit 30213, configured to form the message packet by using the message header and the message body.

Optionally, on the basis of fig. 31, referring to fig. 33, the conversion module 3002 further includes:

a first association module 3024, configured to configure a communication protocol in a case that the data source is an enterprise information system; defining a parameter list to be transmitted; associating the parameter list with a message template;

a second association module 3025, configured to establish a table structure in the storage area of the gateway when the data source is a client; defining a parameter list to be transmitted in the table structure; and associating the parameter list with a message template.

Optionally, referring to fig. 34, the first storage submodule 3022 includes:

a first determining unit 30221, configured to determine whether a first message group buffer corresponding to the message packet can store the message packet; a first storage unit 30222, configured to store the message packet in a corresponding second message group buffer when the first message group buffer cannot store the message packet;

Optionally, the first storage submodule 3022 further includes:

the sequencing unit is used for sequencing the message messages in the message group buffer area according to the ID and the serial number of the message messages; and the deleting unit is used for selecting one message from the repeated message messages to be reserved and deleting other message messages in the repeated message messages, wherein the repeated message messages refer to message messages with the same ID but different message values.

In the uplink direction, the original information is a query request of the client; referring to fig. 35, the conversion module 3002 includes:

a second conversion sub-module 3026, configured to convert the query request into a query instruction; the first filling sub-module 3027, configured to fill the query instruction into a corresponding message template to obtain a query message; a first storage sub-module 3028, configured to store the query message in a corresponding message group buffer; a third converting sub-module 3029, configured to convert the query message group stored in the message group buffer into a file having a target format; wherein the target format comprises an XML format or a JSON format.

Optionally, the sending module 330 is further configured to send, in an uplink direction, a subscription request of the client to the cloud platform.

Referring to fig. 36, the conversion module 3002 includes:

a fourth converting submodule 3031, configured to convert the original information into structural data;

a second storage submodule 3032, configured to store the structural data in a corresponding message buffer;

a fifth converting submodule 3033, configured to convert the structure data in the message buffer into original data by using a message template;

the sending module 3003 is specifically configured to send the raw data to the enterprise information system or the client.

The apparatus provided in the embodiment of the present invention may implement the method embodiments, and the implementation principle and the technical effect are similar, which are not described herein again.

The embodiment of the invention also provides a data processing device which is applied to the cloud platform. Referring to fig. 37, fig. 37 is a block diagram of a data processing apparatus according to an embodiment of the present invention. Because the principle of the data processing device for solving the problem is similar to the data processing method in the embodiment of the present invention, the implementation of the data processing device can refer to the implementation of the method, and repeated details are not repeated.

As shown in fig. 37, the data processing apparatus 370 includes:

the processing module 371 is configured to receive the information with the target format sent by the gateway, and store the information with the target format in a corresponding data pool; or

An obtaining module 372, configured to obtain target data that needs to be sent to the gateway, and convert the target data into target data in a target format; a sending module 373, configured to send the target data with the target format to the gateway.

As shown in fig. 38, which is a schematic diagram of a data processing apparatus according to an embodiment of the present invention, the data processing apparatus includes: a processor 381, a network interface 382, a memory 383, a user interface 384, and a bus interface, wherein:

in this embodiment of the present invention, the data processing device 380 further includes: 383 stored in a memory and executable on the processor 381, which when executed by the processor 381, performs the steps of:

acquiring original information of a data source;

converting the original information into information having a target format;

and transmitting the information with the target format.

In fig. 38, the bus architecture may include any number of interconnected buses and bridges, with various circuits linking one or more processors, represented by processor 381, and memory, represented by memory 383. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The network interface 382 may be a wired or wireless network card device that implements data transceiving functions over a network. The user interface 384 may also be an interface capable of interfacing externally to a desired device for different user devices, including but not limited to a keypad, display, speaker, microphone, joystick, etc.

The processor 381 is responsible for managing the bus architecture and general processing, and the memory 383 may store data used by the processor 381 in performing operations.

In the upstream direction, the data source comprises an enterprise information system or a client; in the downstream direction, the data source comprises a cloud platform.

Optionally, in the uplink direction, the original information is original data to be published by the message enterprise information system or the client; the computer program when executed by the processor 383 may also implement the steps of:

obtaining a message according to the original data;

storing the message into a corresponding message group buffer area;

The computer program when executed by the processor 383 may also implement the steps of:

Optionally, the message header further includes a priority.

Optionally, in the uplink direction, the original information is a query request of the client; said converting said original information into information having a target format, said computer program when executed by the processor 383 further implementing the steps of:

converting the query request into a query instruction;

storing the query message in a corresponding message group buffer;

wherein the target format comprises an XML format or a JSON format.

and sending the subscription request of the client to a cloud platform.

Optionally, in a downlink direction, the original information includes data returned by the cloud platform according to the query message or data returned by the cloud platform according to the subscription request; the original information is in an XML format or a JSON format; the computer program when executed by the processor 383 may also implement the steps of:

converting the original information into structural data;

storing the structure data into a corresponding message buffer;

Optionally, the original information includes one or more of the following:

As shown in fig. 39, which is a schematic diagram of a data processing apparatus according to an embodiment of the present invention, the data processing apparatus includes: a processor 391, a network interface 392, a memory 393, a user interface 394, and a bus interface, wherein:

in the embodiment of the present invention, the data processing apparatus 390 further includes: a computer program stored on the memory 393 and executable on the processor 391, the computer program when executed by the processor 391 performing the steps of:

In FIG. 39, the bus architecture may include any number of interconnected buses and bridges, with one or more processors, represented by processor 391, and various circuits of memory, represented by memory 393, linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, power management circuits, and the like, which are well known in the art, and therefore, will not be described any further herein. The bus interface provides an interface. The network interface 392 may be a wired or wireless network card device for performing data transmission and reception functions on a network. The user interface 394 may also be an interface capable of interfacing externally to a desired device for different user devices, including but not limited to a keypad, display, speaker, microphone, joystick, etc.

The processor 391 is responsible for managing the bus architecture and general processing, and the memory 393 may store data used by the processor 391 in performing operations.

The embodiment of the present invention further provides a computer-readable storage medium, where a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program implements each process of the data processing method embodiment, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here. The computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. With such an understanding, the technical solutions of the present invention may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the methods according to the embodiments of the present invention.

While the present invention has been described with reference to the embodiments shown in the drawings, the present invention is not limited to the embodiments, which are illustrative and not restrictive, and it will be apparent to those skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope of the invention as defined in the appended claims.

Claims

1. A data processing method is applied to a gateway arranged in an enterprise local, and is characterized by comprising the following steps:

acquiring original information of a data source;

converting the original information into information having a target format;

and transmitting the information with the target format.

2. The method of claim 1, wherein in an upstream direction, the data source comprises an enterprise information system or a client; in the downstream direction, the data source comprises a cloud platform.

3. The method of claim 2, wherein in an upstream direction, the raw information is raw data to be published by a message enterprise information system or the client;

obtaining a message according to the original data;

storing the message into a corresponding message group buffer area;

4. The method of claim 3, wherein obtaining the message from the raw data comprises:

5. The method of claim 4, wherein the message header further comprises a priority.

6. The method of claim 3, wherein prior to said obtaining a message packet from said raw data, said method further comprises:

7. The method of claim 3, wherein storing the message packet in a corresponding message group buffer comprises:

8. The method of claim 7, wherein after said storing said message packet in a corresponding message group buffer, said method further comprises:

9. The method of claim 2, wherein in an uplink direction, the original information is a query request of the client; the converting the original information into information having a target format includes:

converting the query request into a query instruction;

storing the query message in a corresponding message group buffer;

wherein the target format comprises an XML format or a JSON format.

10. The method of claim 2, wherein in an uplink direction, the method further comprises:

and sending the subscription request of the client to a cloud platform.

11. The method according to claim 2, wherein in a downstream direction, the original information comprises data returned by the cloud platform according to a query message or data returned by the cloud platform according to a subscription request; the original information is in an XML format or a JSON format;

converting the original information into structural data;

storing the structure data into a corresponding message buffer;

the sending the information having the target format includes:

12. The method of claim 1, wherein the original information comprises one or more of:

13. A data processing method is applied to a cloud platform and is characterized by comprising the following steps:

14. A data processing device is applied to a gateway arranged in an enterprise local area, and is characterized by comprising:

15. The apparatus of claim 14, wherein in an upstream direction, the data source comprises an enterprise information system or a client; in the downstream direction, the data source comprises a cloud platform.

16. The apparatus of claim 15, wherein in an upstream direction, the raw information is raw data to be published by a message enterprise information system or the client;

the conversion module includes:

wherein the target format comprises an XML format or a JSON format.

17. The apparatus of claim 16, wherein the first acquisition submodule comprises:

18. The apparatus of claim 16, wherein the conversion module further comprises:

19. The apparatus of claim 16, wherein the first storage submodule comprises:

20. The apparatus of claim 19, wherein the first storage submodule further comprises:

21. The apparatus of claim 15, wherein in an uplink direction, the original information is a query request of the client;

the conversion module includes:

wherein the target format comprises an XML format or a JSON format.

22. The apparatus of claim 15, wherein the sending module is further configured to send a subscription request of the client to a cloud platform in an upstream direction.

23. The apparatus of claim 15, wherein the conversion module comprises:

24. A data processing device is applied to a cloud platform and is characterized by comprising:

the processing module is used for receiving the information with the target format sent by the gateway and storing the information with the target format into a corresponding data pool; or

The acquisition module is used for acquiring target data to be sent to the gateway and converting the target data into target data with a target format; a sending module, configured to send the target data with the target format to the gateway.

25. A data processing system comprises a gateway and a cloud platform which are arranged in an enterprise local; it is characterized in that the preparation method is characterized in that,

in the uplink direction, the gateway is used for acquiring original information of an enterprise information system or a client, converting the original information into information with a target format, and sending the information with the target format to the cloud platform; in a downlink direction, the gateway is configured to receive target data in a target format sent by the cloud platform, convert the target data into raw data, and send the raw data to the enterprise information system or the client;