Data transmission method and system, AutBus converter and medium

Abstract

The invention belongs to the field of industrial communication, and discloses a data transmission method and system, an AutBus converter and a medium, and the method comprises the steps: receiving Profinet protocol data sent by a source device through a first converter, and packaging the Profinet protocol data into a target data packet of an AutBus protocol according to an identifier of a second converter described in a pre-stored mapping table and a physical address of a target device; and verifying the target data packet according to the pre-stored mapping table by using the second converter, and forwarding the target data packet to the target equipment after the verification is passed. The identification of the second converter, the physical address of the target equipment and the Profinet protocol data in the pre-stored mapping table are packaged into the target data packet of the AutBus protocol, so that the Profinet protocol data are loaded by using the AutBus protocol, the replacement of the Profinet equipment is reduced, and the hardware cost is saved.

Description

Technical Field

[0001] The present application relates to the field of industrial communication technology, and in particular to a data transmission method, system, AutBus converter and medium. Background Art

[0002] In the process of localizing industrial protocols, the Profinet (Process Field Network, an automation bus protocol based on industrial Ethernet technology) network will inevitably be gradually replaced. However, if the Profinet network is completely replaced, it will easily lead to waste of Profinet equipment.

[0003] Therefore the prior art still needs to be improved and enhanced. Summary of the invention

[0004] The present application provides a data transmission method, system, AutBus converter and medium, aiming to solve the problem that a complete replacement of the Profinet network in the prior art easily causes waste.

[0005] In a first aspect, an embodiment of the present application provides a data transmission method, including:

[0006] After receiving the Profinet protocol data sent by the source device using the first converter, the Profinet protocol data is encapsulated into a destination data packet of the AutBus protocol according to the identifier of the second converter described in the pre-stored mapping table and the physical address of the destination device;

[0007] The destination data packet is verified by the second converter according to the pre-stored mapping table, and after the verification is passed, the destination data packet is forwarded to the destination device.

[0008] In some embodiments, the step of using the first converter to receive the Profinet protocol data sent by the source device also includes:

[0009] A mapping relationship is established between the identifier of each converter and the physical addresses of all devices connected thereto to obtain an initial mapping table.

[0010] In some embodiments, the obtaining of the initial mapping table further includes:

[0011] Using the initial mapping table as the pre-stored mapping table of each converter;

[0012] Alternatively, the initial mapping tables of all the converters are broadcasted to each other, so as to merge all the initial mapping tables to obtain the pre-stored mapping table.

[0013] In some embodiments, the step of encapsulating the Profinet protocol data into a destination data packet of the AutBus protocol according to the identifier of the second converter described in the pre-stored mapping table and the physical address of the destination device, further comprises:

[0014] The first converter is used to encapsulate the acquired physical address of the source device as the source address into an initial data packet of the AutBus protocol to obtain an intermediate data packet.

[0015] In some embodiments, the step of encapsulating the Profinet protocol data into a destination data packet of the AutBus protocol according to the identifier of the second converter described in the pre-stored mapping table and the physical address of the destination device, further comprises:

[0016] Using the first converter to receive the access instruction sent by the source device, and according to the access instruction, searching the physical address of the destination device and the identifier of the second converter corresponding to the physical address of the destination device from the mapping relationship in the pre-stored mapping table;

[0017] Wherein, the access instruction includes: the target device to be accessed.

[0018] In some embodiments, encapsulating the Profinet protocol data into a destination data packet of the AutBus protocol according to the identifier of the second converter described in the pre-stored mapping table and the physical address of the destination device includes:

[0019] Obtaining an identifier of the second converter described in the pre-stored mapping table and a physical address of the destination device;

[0020] The identifier is used as the node address, the physical address of the destination device is used as the destination address, and the Profinet protocol data is encapsulated into the intermediate data packet as the data payload to obtain the destination data packet.

[0021] In some embodiments, the verifying the destination data packet using the second converter according to the pre-stored mapping table includes:

[0022] According to the pre-stored mapping table, determining whether the destination address of the destination data packet is a physical address of a device in the second converter;

[0023] When the result is yes, it indicates that the destination data packet has passed the verification;

[0024] When it is determined that it is not, the destination data packet is discarded.

[0025] In a second aspect, an embodiment of the present application provides a data transmission system, including:

[0026] A plurality of converters, a plurality of devices and an AutBus bus; the converters are connected to each other via the AutBus bus, and each of the converters is connected to at least one of the devices; wherein the plurality of converters include: a first converter and a second converter; the plurality of devices include: a source device and a destination device; the source device is connected to the first converter, and the destination device is connected to the second converter;

[0027] The first converter is used to encapsulate the Profinet protocol data into a destination data packet of the AutBus protocol according to the identifier of the second converter described in the pre-stored mapping table and the physical address of the destination device after receiving the Profinet protocol data sent by the source device;

[0028] The second converter is used to verify the destination data packet and forward the destination data packet to the destination device after the verification is passed.

[0029] In a third aspect, an embodiment of the present application provides an AutBus converter, comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program implements the steps of the data transmission method described above when executed by the processor.

[0030] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium storing a computer program, which implements the steps of the data transmission method described above when executed by a processor.

[0031] Compared with the prior art, the present application provides a data transmission method, system, AutBus converter and medium. The method encapsulates the identifier of the second converter and the physical address of the destination device in the pre-stored mapping table, as well as the Profinet protocol data sent by the source device into a destination data packet of the AutBus protocol through the first converter. The second converter verifies the destination data packet according to the pre-stored mapping table and forwards it to the destination device after verification, thereby realizing the use of the AutBus bus protocol to carry and forward the Profinet protocol data, thereby realizing the common use of Profinet devices and AutBus networks, avoiding the comprehensive replacement of Profinet devices, thereby effectively saving hardware costs and extending the service life of the remaining Profinet devices. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0033] Figure 1 A schematic diagram of a typical Profinet protocol frame format in the data transmission method provided by this application;

[0034] Figure 2 A schematic diagram of the Profinet RT frame structure in the data transmission method provided in this application;

[0035] Figure 3 A schematic diagram of a Profinet IRT frame structure in the data transmission method provided by the present application;

[0036] Figure 4 A schematic diagram of a structure in which the AutBus carries the Profinet protocol in the data transmission method provided in this application;

[0037] Figure 5 A flow chart of the data transmission method provided by this application;

[0038] Figure 6 A flow chart for obtaining a pre-stored mapping table in the data transmission method provided by the present application;

[0039] Figure 7 A flow chart of encapsulating a destination data packet in the data transmission method provided by the present application;

[0040] Figure 8 This is a diagram of message changes of the AutBus bus carrying the Profinet protocol in the data transmission method provided by this application;

[0041] Fig. 9 A flow chart for verifying a destination data packet in the data transmission method provided in this application. DETAILED DESCRIPTION

[0042] The technical solutions in the embodiments of the present application will be described clearly and completely below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all of the embodiments.

[0043] The components of the embodiments of the present application generally described and shown in the drawings herein may be arranged and designed in various configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the application claimed for protection, but merely represents the selected embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without making creative work belong to the scope of protection of the present application.

[0044] Hereinafter, the terms "including", "having" and their cognates used in various embodiments of the present application are intended only to indicate specific features, numbers, steps, operations, elements, components or a combination of the foregoing items, and should not be understood as first excluding the existence of one or more other features, numbers, steps, operations, elements, components or a combination of the foregoing items or increasing the possibility of one or more features, numbers, steps, operations, elements, components or a combination of the foregoing items. In addition, the terms "first", "second", "third" and the like are only used to distinguish descriptions and cannot be understood as indicating or implying relative importance.

[0045] Unless otherwise defined, all terms (including technical terms and scientific terms) used herein have the same meanings as those generally understood by those skilled in the art to which the various embodiments of the present application belong. The terms (such as those defined in generally used dictionaries) will be interpreted as having the same meanings as the contextual meanings in the relevant technical field and will not be interpreted as having idealized meanings or overly formal meanings unless clearly defined in the various embodiments of the present application.

[0046] AutBus is a time-sensitive broadband bus technology, which is mainly used to solve the problem of low bandwidth of traditional buses in industrial sites and inability to carry real-time and non-real-time at the same time. The AutBus series of standards was developed by the National Industrial Process Measurement, Control and Automation Standardization Technical Committee (SAC / TC124) with the overall support of the Ministry of Industry and Information Technology. It is currently the only two-wire broadband bus international standard based on time-sensitive technology and Internet Protocol Version 6 (IPv6) technology. This series of standards solves the problems of unified addressing and deterministic communication of IPv6, realizes the full IPization of information technology (IT) protocols and operation technology (OT) protocols, supports the interconnection and interoperability of multiple protocols in the field of industrial communications, and the synchronous broadband transmission of big data such as control data, video, and pictures at the control layer, which can effectively meet the communication requirements of intelligent manufacturing such as high bandwidth, low latency, support for TSN, deterministic network, high clock accuracy, and high real-time. At present, chips based on this series of standards have been successfully developed and can be widely used in intelligent manufacturing related fields such as smart factories, industrial robots, ships, rails, smart transportation, petrochemicals, clean energy, automotive electronics, aviation and engineering equipment.

[0047] Profinet is widely used in the field of industrial automation. Profinet aims to achieve high-speed communication between devices while providing deterministic real-time performance to meet the needs of industrial control for time-sensitive data transmission. Profinet has the characteristics of high-speed real-time performance, compatibility, modular communication, time synchronization, easy configuration and diagnosis, security integration and sustainable development. Among them, the typical frame format of the Profinet protocol is as follows Figure 1 As shown. Among them, Figure 1 Pre-ambel is the preamble. TPID is the abbreviation of Tag Protocol Identifier, which is commonly found in the VLAN tag part of Ethernet frames. Its function is to identify whether the frame contains the IEEE 802.1Q (IEEE 802.1Q is an Ethernet frame tag standard, mainly used to define the tagging method of virtual local area networks (VLANs)). It usually occupies 2 bytes (16 bits); the value of TPID is usually '0x8100'.

[0048] The typical frame format of the Profinet protocol includes the following main parts:

[0049] 1. Ethernet Header; 2. Profinet IP Header; 3. Payload.

[0050] The Ethernet header contains the following fields:

[0051] (1) Source MAC Address: MAC address of the sender.

[0052] (2) Destination MAC Address: MAC address of the recipient.

[0053] (3) Type / Length: Identifies the upper-layer protocol type or length. Common values ​​include 0x8892 (for Profinet RT / IRT) and 0x8100 (for VLAN tagging).

[0054] However, in addition to the Profinet protocol, Profinet has two other protocols: Profinet RT and Profinet IRT.

[0055] Among them, Profinet RT enhances the real-time communication capability based on the standard Profinet. Profinet RT (Real-Time) is used for real-time communication data packets; RT (Real Time) mode ensures the time certainty of data transmission through a special communication mechanism, reduces the delay of data transmission, and is suitable for control applications that have high requirements on time but are not extremely strict, such as some scenarios of motion control. It uses priority queues and optimized data transmission scheduling algorithms to achieve faster response times than basic Profinet. The Profinet RT frame structure is as follows Figure 2 As shown. Among them, Figure 2 VLANTag (Virtual Local Area Network Tag) is an identifier used in Ethernet frames to distinguish different VLANs.

[0056] Profinet IRT (Isochronous Real-Time) is used for data packets with higher real-time requirements, such as high-precision robot control. Profinet IRT is the highest level of real-time performance in Profinet technology, specifically for applications that have extremely strict requirements for time synchronization and real-time performance, such as high-precision robot control. IRT not only provides microsecond transmission delay, but also ensures precise synchronization between all devices on the network. It uses a highly accurate synchronization mechanism and reserved bandwidth method to ensure that the data transmission time is completely predictable and maintains high performance even when the network is heavily loaded. Among them, the Profinet IRT frame structure is as follows Figure 3 shown.

[0057] Among them, Figure 3 In the Ethernet, Frame ID is an application identifier, which is used to identify the transmission type of the received data, that is, to identify periodic transmission and non-periodic transmission (alarm and event). FCS is the abbreviation of Frame Check Sequence, which is used to detect errors in Ethernet frames. FCS occupies 4 bytes (32 bits) and is usually located at the end of the frame. It calculates the data in the frame and generates a checksum, which is then recalculated by the receiving end to verify the integrity of the frame.

[0058] With the development of localization of industrial communications, it is very necessary to make the Profinet protocol compatible through localized protocols.

[0059] Therefore, the present application provides a data transmission method, system, AutBus converter and medium. The data transmission method encapsulates the identifier of the second converter in the pre-stored mapping table and the physical address of the destination device, as well as the Profinet protocol data sent by the source device, into a destination data packet of the AutBus protocol through a first converter, and the second converter verifies the destination data packet according to the pre-stored mapping table and forwards it to the destination device after verification, thereby realizing the use of the AutBus bus protocol to carry and forward the Profinet protocol data, thereby realizing the common use of Profinet devices and AutBus networks, avoiding the full replacement of Profinet devices, thereby effectively saving hardware costs and extending the service life of the remaining Profinet devices.

[0060] The data transmission method design is described below through some specific embodiments.

[0061] The present application embodiment provides a data transmission system, including:

[0062] A plurality of converters, a plurality of devices and an AutBus bus; the converters are connected to each other via the AutBus bus, and each converter is connected to at least one device; wherein the plurality of converters include: a first converter and a second converter; the plurality of devices include: a source device and a destination device; the source device is connected to the first converter, and the destination device is connected to the second converter.

[0063] The first converter is used to receive the Profinet protocol data sent by the source device, and encapsulate the Profinet protocol data into a destination data packet of the AutBus protocol according to the identifier of the second converter described in the pre-stored mapping table and the physical address of the destination device; the second converter is used to verify the destination data packet and forward the destination data packet to the destination device after the verification is passed.

[0064] Among them, the converters are all AutBus converters, the devices are all Profinet devices, and the Profinet devices are devices that support the Profinet protocol. The AutBus converter and the AutBus bus are used as a bridge to communicate between several Profinet devices to build the Profinet data transmission system architecture in this application. Please refer to Figure 4 In this application, the source device is Profinet device A, the first converter is AutBus converter 1, the destination device is Profinet device C, and the second converter is AutBus converter 3 as an example.

[0065] Exemplarily, after all devices and converters are powered on, Profinet device A (source device) sends Profinet protocol data to AutBus converter 1 (first converter), and AutBus converter 1 encapsulates the identifier of the second converter described in the pre-stored mapping table and the physical address of the destination device, as well as the Profinet protocol data, into a destination data packet of the AutBus protocol.

[0066] Then, the AutBus converter 1 transmits the destination data packet to the AutBus converter 3 (second converter) via the AutBus bus, and the AutBus converter 3 verifies the destination address in the destination data packet. When the destination address is verified to be the physical address of one of the devices in the second converter, that is, the destination device exists in the devices of the second converter, it means that the verification is successful. Finally, the destination data packet is forwarded to the corresponding destination device.

[0067] Finally, the process of the destination device responding to the source device is similar to the process of the source device sending the destination data to the destination device. It also obtains the physical address of the target device in the pre-stored mapping table and the identifier of its corresponding converter, which will not be introduced in detail here.

[0068] It can be understood that in this application, the first converter encapsulates the Profinet protocol data into the destination data packet of the AutBus protocol according to the identifier of the second converter in the pre-stored mapping table and the physical address of the destination device, and forwards it to the corresponding destination device after the second converter verifies it, so as to make full use of the AutBus bus protocol to carry and forward the Profinet protocol data, thereby reducing the heavy dependence on the Profinet network and the waste caused by replacing all Profinet devices. In addition, multiple Profinet networks can be combined into a new larger network through the AutBus bus protocol.

[0069] Based on the data transmission system of the above embodiment, please refer to Figure 5 , the embodiment of the present application also provides a data transmission method, including steps S100-S200:

[0070] S100: After receiving the Profinet protocol data sent by the source device using the first converter, encapsulate the Profinet protocol data into a destination data packet of the AutBus protocol according to the identifier of the second converter described in the pre-stored mapping table and the physical address of the destination device.

[0071] Exemplarily, after the source device sends Profinet protocol data to the first converter, the first converter obtains the identifier of the second converter connected to the destination device from the pre-stored mapping table, and encapsulates the identifier and the physical address of the destination device, as well as the Profinet protocol data into a destination data packet of the AutBus protocol.

[0072] It can be understood that in the present application, after the first converter obtains the identifier of the second converter and the physical address of the destination device according to the pre-stored mapping table, the identifier and the physical address of the destination device, as well as the Profinet protocol data are encapsulated as the destination data packet of the AutBus protocol, thereby converting the Profinet protocol data into the destination data packet of the AutBus protocol, thereby providing the possibility for the AutBus bus protocol to carry the Profinet protocol data, and providing the possibility for the dual-protocol network architecture of AutBus and Profinet.

[0073] For example, in one implementation method, the first converter is used to receive the Profinet protocol data sent by the source device, and the method also includes:

[0074] S90: Establish a mapping relationship between the identifier of each converter and the physical addresses of all devices connected to it to obtain an initial mapping table.

[0075] Among them, all the devices here are Profinet devices.

[0076] Exemplarily, when the entire system is powered on and a Profinet device is connected to the AutBus converter, each AutBus converter will obtain the physical address of its own Profinet device and generate a mapping table between the AutBus device ID and the source MAC address of the Profinet device, that is, the physical address of the Profinet device on it is bound and mapped with its own identification to obtain the initial mapping table of each converter.

[0077] For example, in one implementation, see Figure 6 , get the initial mapping table, and then include:

[0078] S91. Use the initial mapping table as a pre-stored mapping table for each converter.

[0079] Alternatively, S92, the initial mapping tables of all converters are broadcast to each other, so as to merge all the initial mapping tables to obtain a pre-stored mapping table.

[0080] Exemplarily, there are two ways to carry Profinet protocol data in this application:

[0081] The first carrying mode (mainly carried out in this way in this embodiment): the initial mapping tables of all converters are broadcasted mutually, that is, each converter transmits its own initial mapping table to all other AutBus devices through the AutBus bus by broadcasting, so as to synchronize the AutBus device with the MAC address, that is, to merge all the initial mapping tables to obtain a pre-stored mapping table. At this time, the pre-stored mapping table stores the mapping relationship between all AutBus converters and their corresponding connected Profinet devices, and each converter has mapping tables of all devices.

[0082] by Figure 4 For example, the pre-stored mapping table of all AutBus devices and their respective Profinet devices is shown in Table 1 below.

[0083] Table 1

[0084]

[0085]

[0086] The second carrying mode: the initial mapping table of each converter is not broadcast to each other, but the initial mapping table is directly used as the pre-stored mapping table of each converter, that is, each initial mapping table records the mapping relationship between each AutBus device and the MAC address of the Profinet device connected to it. At this time, the pre-stored mapping table is the initial mapping table, that is, each converter only has the mapping table of its own device. For example, the pre-stored mapping table of AutBus converter 1 only contains the mapping relationship between it and Profinet device A.

[0087] For example, in one implementation method, according to the identifier of the second converter described in the pre-stored mapping table and the physical address of the destination device, the Profinet protocol data is encapsulated into a destination data packet of the AutBus protocol, which also includes:

[0088] The first converter is used to encapsulate the acquired physical address of the source device as the source address into an initial data packet of the AutBus protocol to obtain an intermediate data packet.

[0089] Exemplarily, before obtaining the destination data packet, the process includes:

[0090] After the first converter and the source device are powered on, the first converter obtains the address of the source device connected to it. Then, by expanding the TYPE area of ​​the AutBus bus protocol, the reserved field 0x00 of TYPE is used to carry the Profinet protocol, so the physical address of the source device can be written into the source address in the initial data packet of the AutBus protocol to obtain an intermediate data packet. The data format of the AutBus bus protocol is shown in Table 2 below.

[0091] Table 2

[0092]

[0093] The TYPE values ​​and meanings of DLPDU are shown in Table 3.

[0094] Table 3

[0095]

[0096] The data format of the PAYLOAD (payload) field in the initial data packet of the AutBus protocol is as shown in Table 4. Then, the physical address of the source device is written into the SRC_MAC (source address) area of ​​the PAYLOAD field in the initial data packet.

[0097] Table 4

[0098]

[0099] For example, in one implementation method, according to the identifier of the second converter described in the pre-stored mapping table and the physical address of the destination device, the Profinet protocol data is encapsulated into a destination data packet of the AutBus protocol, which also includes:

[0100] The first converter is used to receive the access instruction sent by the source device, and according to the access instruction, the physical address of the destination device and the identifier of the corresponding second converter are searched from the mapping relationship in the pre-stored mapping table.

[0101] The access instruction includes: a target device to be accessed.

[0102] Exemplarily, after the first converter and the source device are both powered on, the source device sends an access instruction to the first converter, and the first converter parses the destination device to be sent according to the access instruction, and searches for the identifier of the second converter corresponding to the destination device to be sent from the mapping relationship in the pre-stored mapping table, so as to encapsulate the identifier of the second converter.

[0103] In one implementation, see Figure 7, according to the identifier of the second converter described in the pre-stored mapping table and the physical address of the destination device, the Profinet protocol data is encapsulated into a destination data packet of the AutBus protocol, including:

[0104] S101, obtaining an identifier of a second converter described in a pre-stored mapping table and a physical address of a destination device;

[0105] S102: Use the identifier as the node address, and the physical address of the destination device as the destination address, and encapsulate the Profinet protocol data as the data payload into the intermediate data packet to obtain the destination data packet.

[0106] Exemplarily, after the first converter receives the Profinet protocol data, the first converter first searches the pre-stored mapping table for the corresponding identifier of the second converter and the physical address of the destination device according to the destination device to be sent.

[0107] Then, the identifier of the second converter is used as the node address (corresponding to the "Dst_NodeID" area in Table 4), and the physical address of the destination device is used as the destination address (corresponding to the "DST_MAC" area in Table 4), and the Profinet protocol data is encapsulated into the intermediate data packet as the data area in the data payload (corresponding to the "DATA" area in Table 4), thereby obtaining the encapsulated destination data packet.

[0108] It should be noted that in the first bearer mode, it is necessary to find the identifier of the second converter from the pre-stored mapping table of the first converter and encapsulate the identifier of the second converter into the intermediate data packet. Because in the first bearer mode, each converter only has its own pre-stored mapping table between the devices connected to it, and cannot find the identifiers of other converters from its own pre-stored mapping table.

[0109] For further information, see Figure 8 In another embodiment of the present application, the physical address of the source device is used as the source address, the identifier of the second converter is used as the node address, and the Profinet protocol data (corresponding to Figure 8 The Profinet data packet in the data payload) is used as the data area in the data payload, and the physical address of the destination device is used as the destination address, and is encapsulated into the initial data packet of the AutBus protocol (corresponding to Figure 8 The destination data packet is obtained directly from the AutBus data packet in the source file.

[0110] S200: Utilize the second converter to verify the destination data packet according to the pre-stored mapping table, and after the verification is passed, forward the destination data packet to the destination device.

[0111] Exemplarily, after obtaining the destination data packet, if the destination data packet is obtained in the first bearing mode, then at this time, the first converter uses the node address in the destination data packet to directly transmit the destination data packet to the second converter via the AutBus bus alone (ie, unicast mode).

[0112] However, if the destination data packet is obtained in the second carrying mode (without encapsulating the identifier of the second converter), then at this time, the first converter broadcasts the destination data packet to all other converters (including the second converter) via the AutBus bus.

[0113] Then, the second converter verifies the destination data packet to verify whether the physical address of the destination device exists in the pre-stored mapping table of the second converter, and forwards the destination data packet to the destination device when the verification passes.

[0114] It can be understood that by verifying the destination data packet to verify whether the data is transmitted correctly, and sending it to the corresponding destination device after the verification is passed, the accuracy and efficiency of data transmission are improved.

[0115] In one implementation, see Fig. 9 , using the second converter to verify the destination data packet according to the pre-stored mapping table, including:

[0116] S201, judging whether the destination address of the destination data packet is the physical address of the device in the second converter according to the pre-stored mapping table;

[0117] S202, when it is judged that the destination data packet has passed the verification;

[0118] S203: When it is determined that the destination data packet is not received, the destination data packet is discarded.

[0119] Exemplarily, after the second converter receives the destination data packet transmitted by the first converter, the second converter determines, based on its pre-stored mapping table, whether the destination address of the destination data packet is the physical address of a device in the second converter, i.e., verifies whether the destination address of the destination data packet is the same as the physical address of one of the devices on the second converter.

[0120] If the verification result is yes, it means that the destination data packet is verified, so the destination data packet is forwarded to the corresponding device, that is, the destination device. If the verification result is no, the destination data packet is discarded.

[0121] The data transmission method of the embodiment of the present application uses the first converter to encapsulate the Profinet protocol data into a destination data packet of the AutBus protocol according to the identifier of the second converter in the pre-stored mapping table and the physical address of the destination device. The second converter verifies the destination data packet according to the pre-stored mapping table and forwards it to the destination device after the verification is passed, thereby realizing the use of the AutBus bus protocol to carry the Profinet protocol data, avoiding excessive dependence on the Profinet network, and adopting a network architecture that combines AutBus devices and Profinet devices, thereby effectively saving hardware costs.

[0122] An embodiment of the present application also provides an AutBus converter. Exemplarily, the AutBus converter includes a processor and a memory, wherein the memory stores a computer program, and the processor runs the computer program to enable the AutBus converter to execute the functions of each module in the above-mentioned data transmission method or the above-mentioned data transmission system.

[0123] Among them, the processor can be an integrated circuit chip with signal processing capabilities. The processor can be a general-purpose processor, including a central processing unit (CPU), a graphics processing unit (GPU) and a network processor (NP), a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or at least one of other programmable logic devices, discrete gates or transistor logic devices, and discrete hardware components. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc., which can implement or execute the disclosed methods, steps and logic block diagrams in the embodiments of the present application.

[0124] The memory may be, but is not limited to, a random access memory (RAM), a read only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), etc. The memory is used to store a computer program, and the processor may execute the computer program accordingly after receiving an execution instruction.

[0125] The embodiment of the present application also provides a computer-readable storage medium for storing the computer program used in the above-mentioned AutBus converter. For example, the computer-readable storage medium may include but is not limited to: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and other media that can store program codes.

[0126] In several embodiments provided in the present application, it should be understood that the disclosed devices and methods can also be implemented in other ways. The device embodiments described above are merely schematic. For example, the flowcharts and structure diagrams in the accompanying drawings show the possible architecture, functions and operations of the devices, methods and computer program products according to multiple embodiments of the present application. In this regard, each box in the flowchart or block diagram can represent a module, a program segment or a part of a code, and the module, program segment or a part of the code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in an alternative implementation, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two consecutive boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the structure diagram and / or the flow diagram, and the combination of boxes in the structure diagram and / or the flow diagram, can be implemented with a dedicated hardware-based system that performs a specified function or action, or can be implemented with a combination of dedicated hardware and computer instructions.

[0127] In addition, the functional modules or units in the various embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.

[0128] If the functions are implemented in the form of software function modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for a computer device (which can be a smart phone, a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the various embodiments of the present application.

[0129] The above description is only a specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application.

Claims

1. A data transmission method, characterized in that: include: After receiving the Profinet protocol data sent by the source device using the first converter, the Profinet protocol data is encapsulated into a destination data packet of the AutBus protocol according to the identifier of the second converter described in the pre-stored mapping table and the physical address of the destination device; The destination data packet is verified by the second converter according to the pre-stored mapping table, and after the verification is passed, the destination data packet is forwarded to the destination device.

2. The data transmission method according to claim 1, characterized in that: The method of using the first converter to receive the Profinet protocol data sent by the source device also includes: A mapping relationship is established between the identifier of each converter and the physical addresses of all devices connected thereto to obtain an initial mapping table.

3. The data transmission method according to claim 2, characterized in that: The initial mapping table is obtained, and then further includes: Using the initial mapping table as the pre-stored mapping table of each converter; Alternatively, the initial mapping tables of all the converters are broadcasted to each other, so as to merge all the initial mapping tables to obtain the pre-stored mapping table.

4. The data transmission method according to claim 1, characterized in that: The method further comprises encapsulating the Profinet protocol data into a destination data packet of the AutBus protocol according to the identifier of the second converter described in the pre-stored mapping table and the physical address of the destination device, wherein: The first converter is used to encapsulate the acquired physical address of the source device as the source address into an initial data packet of the AutBus protocol to obtain an intermediate data packet.

5. The data transmission method according to claim 1, characterized in that: The method further comprises encapsulating the Profinet protocol data into a destination data packet of the AutBus protocol according to the identifier of the second converter described in the pre-stored mapping table and the physical address of the destination device, wherein: Using the first converter to receive the access instruction sent by the source device, and according to the access instruction, searching the physical address of the destination device and the identifier of the second converter corresponding to the physical address of the destination device from the mapping relationship in the pre-stored mapping table; Wherein, the access instruction includes: the target device to be accessed.

6. The data transmission method according to claim 4, characterized in that: The step of encapsulating the Profinet protocol data into a destination data packet of the AutBus protocol according to the identifier of the second converter described in the pre-stored mapping table and the physical address of the destination device comprises: Obtaining an identifier of the second converter described in the pre-stored mapping table and a physical address of the destination device; The identifier is used as the node address, the physical address of the destination device is used as the destination address, and the Profinet protocol data is encapsulated into the intermediate data packet as the data payload to obtain the destination data packet.

7. The data transmission method according to claim 6, characterized in that: The using the second converter to verify the destination data packet according to the pre-stored mapping table includes: According to the pre-stored mapping table, determining whether the destination address of the destination data packet is a physical address of a device in the second converter; When the result is yes, it indicates that the destination data packet has passed the verification; When it is determined that it is not, the destination data packet is discarded.

8. A data transmission system, characterized in that: include: Several converters, several devices and AutBus; The converters are connected via the AutBus bus, and each of the converters is connected to at least one of the devices; wherein the converters include: a first converter and a second converter; the devices include: a source device and a destination device; the source device is connected to the first converter, and the destination device is connected to the second converter; The first converter is used to encapsulate the Profinet protocol data into a destination data packet of the AutBus protocol according to the identifier of the second converter described in the pre-stored mapping table and the physical address of the destination device after receiving the Profinet protocol data sent by the source device; The second converter is used to verify the destination data packet and forward the destination data packet to the destination device after the verification is passed.

9. An AutBus converter, characterized in that: include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the steps of the data transmission method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: A computer program is stored, and when the computer program is executed by a processor, the steps of the data transmission method according to any one of claims 1 to 7 are implemented.

Images