CN110753075B - Method and system for processing abstract and simulation behaviors of remote equipment - Google Patents
Method and system for processing abstract and simulation behaviors of remote equipment Download PDFInfo
- Publication number
- CN110753075B CN110753075B CN201810819733.6A CN201810819733A CN110753075B CN 110753075 B CN110753075 B CN 110753075B CN 201810819733 A CN201810819733 A CN 201810819733A CN 110753075 B CN110753075 B CN 110753075B
- Authority
- CN
- China
- Prior art keywords
- cloud server
- network
- virtual
- intermediary
- network packet
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/562—Brokering proxy services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/14—Network analysis or design
- H04L41/145—Network analysis or design involving simulating, designing, planning or modelling of a network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Health & Medical Sciences (AREA)
- Computing Systems (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The application discloses a method and a system for processing abstract and simulated behaviors of remote equipment, which are characterized in that the connection identification and operation of the remote equipment are controlled, and the method comprises the steps that a gateway network is connected with a cloud server and at least one intermediary device; receiving the device information of the intermediary equipment by the gateway and forwarding the device information to the cloud server; the cloud server generates a corresponding virtual communication interface according to the device information; the virtual communication interface establishes at least one virtual device and sets a virtual access model of the virtual device; selecting any one of the virtual devices, and loading the selected virtual device as a remote device by the cloud server; the cloud server sends the device command to the gateway and the intermediary device through the virtual access model; the intermediary equipment converts the received network packet into an equipment command; the intermediary equipment sends the reply response of the terminal equipment to the cloud server; the virtual access model converts the network packet into a reply response.
Description
Technical Field
A behavior processing method and system for electronic devices, and more particularly, to a method and system for processing abstract and simulated behaviors of remote devices.
Background
With the rise of issues such as factory intelligence and Internet of Things (IoT), manufacturers want to collect messages of operating devices (devices) from a control end (e.g., a backend host or a cloud) in real time so as to apply the collected messages to big data analysis. How to connect the terminal device to the network is the primary work of crossing into the cloud.
The communication Protocol adopted by the conventional terminal device is not compatible with the existing Ethernet (Ethernet) and TCP/IP (Transmission Control Protocol/Internet Protocol, TCP/IP for short), so that the information cannot be directly uploaded to the cloud. The field bus (Filed bus) refers to a communication network used by a terminal device, for example: the field bus of the Modbus protocol is RS-485. Generally, the transmission distance of the field bus of the terminal device in the prior art is limited, and the installation mode of the field bus is fixed. For example: cyclic, daisy chain, or star, etc. Therefore, when a new terminal device is added, the topology structure of the existing field bus is not easy to adjust by a worker.
Taking the Modbus-TCP protocol as an example, the Modbus-TCP protocol originally uses Master/save architecture (Master/save) to communicate via TCP. When the Master (i.e. the control end) and any Slave (i.e. the terminal device) poll (polling), other terminal devices can only connect after waiting for the Master to release. When the number of terminal devices is increased, the Master polling time is increased. This is because the Modbus-TCP protocol does not change the control behavior of the terminal device accordingly. Therefore, when a large number of terminal devices are installed, the number of times of sending the interrupt request is increased. However, the time of each visit is still fixed, so the total visit time is too long. And the newly added terminal equipment can additionally increase the workload of the control end.
In addition, the staff member needs to set parameters of the terminal device itself and also needs to set a network Address (IP Address for short). The control end of the Modbus-TCP protocol defines the connected terminal device through a look-up table (table) and the UID. The operator needs to set the relevant parameters of the detecting device. When setting wrong parameters, the control end cannot control the terminal device smoothly. Although each manufacturer develops a terminal device according to the Modbus-TCP protocol, the setting method of each manufacturer differs.
In addition, other types of terminal devices may be connected to the communication protocol, such as: EtherNet/IP or Profinet. When there are multiple different communication protocols in the same factory, the difficulty of field bus configuration will increase. For the upper layer developers, the conversion and data capture between multiple communication protocols is a very complicated task.
Based on the problems of wiring and equipment parameters of various protocols, the control end is not easy to be connected to the terminal equipment at the bottom layer, so that data acquisition of the equipment at the bottom layer is not easy, and the Internet of things and big data analysis cannot be further promoted.
Disclosure of Invention
The technical problem that this application will solve lies in: 1. the terminal equipment in the area network lacks flexibility in deployment; 2. the complexity of setting can be increased along with the increase of the number of the terminal equipment setting and configuration; 3. the cloud server cannot acquire data of the bottom-layer terminal device quickly.
In order to solve the above problems, the present application provides a method for processing abstraction and simulation behavior of a remote device, which is characterized by controlling connection identification and operation of the remote device. The processing method for the abstraction and the simulation behavior of the remote equipment comprises the following steps that a gateway network is connected with a cloud server and at least one intermediary equipment; receiving a device information of each intermediary device by the gateway and forwarding the device information to the cloud server; the cloud server generates a corresponding virtual communication interface according to the device information; establishing at least one virtual device for the virtual communication interface, and setting a virtual access model of the virtual device; selecting any one of the virtual devices, and loading the selected virtual device as a remote device by the cloud server; the cloud server encapsulates an equipment command into a first network packet through the virtual access model; the gateway receives the first network packet and forwards the first network packet to the corresponding intermediary device, and the intermediary device converts the received first network packet into the device command; the intermediary device converting a reply response into a second network packet; sending the second network packet to the gateway, and forwarding the second network packet to the cloud server by the gateway; converting the second network packet into the reply response by the virtual access model.
The application further provides a processing system for abstracting and simulating behaviors of remote devices, which includes an intermediary device, a cloud server and a gateway. The intermediary equipment comprises a first processing unit, a first network unit, a first storage unit and an entity communication interface, wherein the first processing unit is electrically connected with the first network unit, the first storage unit and the entity communication interface, the entity communication interface is electrically connected with a terminal device, the first processing unit converts a first network packet into an equipment command and sends the equipment command to the terminal device, the first processing unit converts a reply response of the terminal device into a second network packet, the first storage unit stores device information, and the device information records the type and the number of the entity communication interface of the intermediary equipment;
the cloud server comprises a second processing unit, a second network unit and a second storage unit, wherein the second processing unit is electrically connected with the second network unit and the second storage unit, the second network unit is connected with the intermediary equipment, the second processing unit establishes a connection list according to the connected intermediary equipment, the second processing unit establishes a corresponding virtual communication interface according to the device information, the second processing unit establishes at least one virtual equipment for the virtual communication interface, the second processing unit mounts the selected virtual equipment as a remote equipment, the second processing unit sets a virtual access model corresponding to the remote equipment, and the second processing unit transmits the equipment command or the reply response through the virtual access model; the gateway comprises a third processing unit, a third network unit, a fourth network unit and a third storage unit, wherein the third processing unit is electrically connected to the third network unit, the fourth network unit and the third storage unit, the third network unit is connected to the cloud server, the fourth network unit is connected to the intermediary device through a network, the third processing unit is used for converting identification information of the first network packet and the second network packet, and the third storage unit temporarily stores the identification information.
Compared with the prior art, the application can obtain the following technical effects:
1) the control system provided by the application can realize the establishment of the field bus without moving the position of the terminal equipment again or setting related network parameters.
2) The mediation device of the application can provide device objectification and event enumeration processing, so that the control end does not need device terminal equipment one by one.
Of course, it is not necessary for any one product to achieve all of the above-described technical effects simultaneously.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application.
FIG. 1 is a schematic diagram of a system architecture according to the present application.
FIG. 2A is a schematic diagram of the operation process of the present application.
FIG. 2B is a schematic diagram of a mediation device identification of the present application.
Fig. 3A is a schematic diagram illustrating transmission of a cloud server to an intermediary device according to the present application.
Fig. 3B is a schematic diagram illustrating a hierarchical control between a cloud server and a mediation device according to the present application.
FIG. 3C is a schematic diagram illustrating the operation of the virtual access model of the present application.
FIG. 4A is a schematic diagram of a connection of the processing system of the present application.
FIG. 4B is a schematic diagram of a processing system according to the present application.
FIG. 4C is a control schematic of the processing system of the present application.
FIG. 5A is a schematic diagram of the middleware of the present application before replacement.
FIG. 5B is a schematic diagram of the present application after replacing the middleware.
Detailed Description
Embodiments of the present application will be described in detail with reference to the drawings and examples, so that how to implement technical means to solve technical problems and achieve technical effects can be fully understood and implemented.
The system for processing abstract and simulated behavior of remote devices disclosed in the present application comprises an intermediary device 110, a cloud server 120, a gateway 130, and a terminal device 140. Please refer to fig. 1, which is a schematic diagram of a system architecture of the present application. The mediation device 110 is network-connected to the gateway 130. In addition, the mediation device 110 may select whether to electrically connect to the terminal device 140. The gateway 130 is network-connected to the cloud server 120. In the present application, the gateway 130 is used to distinguish between two different network segments. The gateway 130 and the mediation device 110 are configured as an area network segment in the present application, and the gateway 130 and the cloud server 120 are configured as an external network segment. The network packets sent by the cloud server to the gateway 130 and the intermediary 110 are defined as a first network packet, and the network packets sent by the intermediary 110 or the gateway 130 to the cloud server 120 are defined as a second network packet.
The intermediary device 110 comprises a first processing unit 111, a first network unit 112, a first storage unit 113, a first output buffer unit 114 and a physical communication interface 115. The first processing unit 111 is electrically connected to the first network unit 112, the first storage unit 113, the first output buffer unit 114, and the physical communication interface 115. The first network unit 112 is connected to the gateway 130. The first network unit 112 and the gateway 130 encapsulate the transmitted network packet by a Media Access Control Address Layer (MAC Layer for short).
The first storage unit 113 stores a first management program 116 and device information 117. The first processing unit 111 runs a first hypervisor 116. The first hypervisor 116, in addition to providing the device information 117 of the middleware 110, also converts the device command or the reply response into a network packet. The device information 117 describes the model information of the middleware 110 and the installed physical communication interface 115 (type and number). The device information 117 also records address information of at least one set of interface channels and the mediation apparatus 110. The address information in the LAN is a MAC address.
The physical communication interface 115 is electrically connected to the terminal device 140, and the terminal device 140 receives the device command or sends a reply response. The physical communication interface 115 may be, but is not limited to, a Serial interface (Serial), parallel interface (parallel), analog input/output interface (analog I/O), digital I/O (digital I/O), or Universal Serial Bus (USB). Each set of interface channels of the device information 117 corresponds to a physical communication interface 115. For example, the first set of interface channels corresponds to RS-232 and the second set of interface channels corresponds to serial interfaces. In addition, other sets of interface channels may also correspond to the existing physical communication interfaces 115.
The cloud server 120 includes a second processing unit 121, a second network unit 122, a second output buffer unit 123 and a second storage unit 124. The second processing unit 121 is electrically connected to the second network unit 122, the second output buffer unit 123 and the second storage unit 124.
The second network element 122 is network connected to the gateway 130. The second storage unit 124 stores an operating system 125, a second hypervisor 126, and a connection list 127. The connection list 127 records the connected gateway 130 and the affiliated mediation device 110. The second processing unit 121 is used to run an operating system 125 and execute a second hypervisor 126. The operating system 125 may be a windows operating system 125 from Microsoft (Microsoft) or a UNIX-related operating system 125. The second processing unit 121 further generates a corresponding virtual communication interface and a virtual access model according to the connected middleware 110 and the selected interface channel. The second output buffer unit 123 is used for buffering the related data sent to the middleware 110, so as to ensure the integrity of the data sent to the middleware 110. The cloud server 120 and the gateway 130 encapsulate the transmitted network packets in a Transmission Control Protocol/Internet Protocol (TCP/IP) manner. In other words, the packet identification between the cloud server 120 and the gateway 130 is through the IP address. The packet identification between the gateway 130 and the mediation device 110 is through the MAC address.
The gateway 130 may be implemented in various forms such as a Personal Computer (PC) or a single chip microcomputer (ASIC). The gateway 130 includes a third processing unit 131, a third network unit 132, a fourth network unit 133 and a third storage unit 134. The third processing unit 131 is electrically connected to the third network unit 132 and the third storage unit 134. The third network unit 132 is connected to the cloud server 120, and the fourth network unit 133 is connected to the intermediary device 110. The third processing unit 131 is used for converting the identification information of the first network packet and the second network packet. The third storage unit 134 stores identification information and temporarily stores network packets passing through the gateway 130. Therefore, the identification information is the MAC address in the local network segment and the IP address in the external network segment.
For the external network segment, the gateway 130 sends a connection request to the cloud server 120 when it is connected to the network for the first time. For the LAN segment, the gateway 130 queries the MAC address of the corresponding mediation device 110 according to the identification information, and resets the queried MAC address to the header of the first network packet. The header of the first network packet of the cloud server 120 only provides the IP address and the MAC address of the gateway 130. The gateway 130 cannot directly map the MAC address of the first network packet header to the MAC address of the mediation device 110. When the packet from the external segment is sent to the local segment, the third processing unit 131 parses the identification information of the destination mediation device 110 from the first network packet text and repackages the packet header. When the middleware 110 sends the second network packet to the gateway 130, the gateway 130 repacks the header and related information of the second network packet according to the address of the cloud server.
To further explain the processing flow of the middleware 110 and the cloud server 120, please refer to fig. 2A, which is a schematic operation flow diagram of the present application. The method for processing the abstract and the simulation behaviors of the remote equipment comprises the following steps:
step S210: the gateway network is connected with the cloud server and at least one intermediary device;
step S220: receiving the device information of each intermediary equipment by the gateway and forwarding the device information to the cloud server;
step S230: the cloud server generates a corresponding virtual communication interface according to the device information;
step S240: establishing at least one virtual device for the virtual communication interface, and setting a virtual access model of the virtual device;
step S250: selecting any one from the virtual equipment, and loading the selected virtual equipment into remote equipment by the cloud server;
step S260: the cloud server encapsulates the equipment command into a first network packet through the virtual access model;
step S270: the gateway receives the first network packet and forwards the first network packet to corresponding intermediary equipment, and the intermediary equipment converts the received first network packet into an equipment command;
step S280: the intermediary equipment converts the reply response into a second network packet;
step S290: sending the second network packet to a gateway, and forwarding the second network packet to a cloud server by the gateway; and
step S300: the virtual access model converts the second network packet into a reply response.
First, the mediation apparatus 110 may select whether to connect the terminal apparatus 140. The gateway 130 is respectively connected to the cloud server 120 and the mediation device 110 via a network. The gateway 130 defines two connected segments as an area segment and an external segment, respectively. In the LAN, the mediation device 110 and the gateway 130 use the MAC address as a means for device discovery and packet transmission. In the external segment, the gateway 130 and the cloud server 120 use IP addresses as the transmission method of network packets.
When the mediation device 110 connects to the gateway 130, the gateway 130 will start broadcasting the identification request, as shown in fig. 2B. The intermediate device 110 receives the identification request, and the intermediate device 110 transmits the information to the gateway 130 in the form of a second network packet. The gateway 130 forwards the device information 117 to the cloud server 120, and the cloud server 120 adds the middleware 110 to the connection list 127 according to the device information 117. When any of the middleware 110 is replaced, the cloud server 120 also updates the connection list 127 and the related environment parameters according to the new middleware 110. The device information 117 records the type and number of the physical communication interfaces 115 installed in the middleware 110.
In addition, when the cloud server 120 receives the device information 117, the second processing unit 121 loads the virtual communication interface in the operating system 125 according to the interface channel and the type of the device information 117. The second processing unit 121 establishes at least one virtual device and a corresponding virtual access model according to the virtual communication interface. During the loading of the virtual communication interface, the second hypervisor 126 generates a corresponding virtual access model according to the type of the virtual communication interface. The process of creating each virtual communication interface and virtual access model is referred to as objectification (Object) in the present application. The virtual access model is used for configuring the access setting of the remote device.
For example, the device information 117 describes an RS-232 interface and an RS-485 interface. The second hypervisor 126 loads the aforementioned RS-232 and RS-485 virtual communication interfaces in the OS 125 based on the interface types loaded by the device information 117. In other embodiments, the device information 117 may also record multiple sets of the same interface. For example, in another embodiment, the device information 117 may record two (or more) sets of identical communication interfaces.
In other words, the virtual access model may be configured to control the equipment of the physical communication interface 115 and to relate to the data transmission. In particular, access, connection maintenance (connection main), management, data transmission handshake (handshake), data retransmission, and exception reporting between the middleware 110 and the cloud server 120. The user can select one of the virtual communication interfaces through the cloud server 120, and map (mapping) the selected remote device to the terminal device 140. The mapping is performed by establishing a transmission channel between the terminal device 140 and the remote device through a combination of the operating system 125, the driver, and the second hypervisor 126.
Then, the second processing unit 121 establishes at least one virtual device for the virtual communication interface. The second hypervisor 126 provides a list of remote devices according to the type and number of virtual communication interfaces. For example: the virtual communication interface of the RS-232 may correspond to a virtual device such as a barcode reader 522(barcode reader) or a printer (printer), respectively. The user may select any one from the list of virtual devices. The selected virtual device is further defined in this specification as a remote device. Based on the transmission pipeline, the second management program 126 abstracts various processing behaviors of the device command and the reply response into a virtual communication interface, so that a worker can directly operate the virtual remote device.
The second hypervisor 126 defines the addressing mechanism for access according to the mediation device 110 and the remote devices, as shown in FIG. 3A. In the present application, the relative addresses (addresses) of the intermediary device 110 and the remote device are defined by channel (channel) and offset (offset). For the cloud server 120, each different remote device may be considered a different object. In fig. 3A, the cloud server 120 designates a channel according to the virtual communication interface of the middleware 110, and uses the displacement of the memory in the designated channel as a different remote device. The cloud server 120 of fig. 3A is based on "GW _ x: dev _ m: the channel and displacement of CH _ n "represents the identity of the mediation device 110110 and the remote device (designated devices are indicated by black dashed lines), where" GW _ x "represents the gateway 130," Dev _ m "represents the device number of the mediation device 110, and" CH _ n "represents the mth displacement amount (i.e., the remote device).
FIG. 3B is a diagram illustrating the object and physical communication interface 115 according to the present application. In fig. 3B, the left side represents the cloud server 120, the right side represents the middleware 110, and the cloud server 120 and the middleware 110 are used as a transmission medium via the ethernet network. The upper layer of the cloud server 120 has a plurality of objects, and the upper layer of the intermediary device 110 also has a plurality of corresponding physical communication interfaces 115. Both parties in FIG. 3B have two objects and two physical communication interfaces 115. The object of the cloud server 120 and the ethernet network can be further divided into a data transform layer (data transform layer). The data conversion layer is used for processing the conversion of the network packet of the equipment command and the response. Each object at the cloud server 120 corresponds to the physical communication interface 115, and in fig. 3B, the object a and the object B correspond to the physical communication interface 115 and the physical communication interface 115, respectively.
In addition, the virtual access model defines the corresponding processing mechanisms for the control of the equipment and the access of the data as event (event), command (command) and data (data), and please match with fig. 3C. The "event" is used for an interrupt processing request of the mediation apparatus 110 to the cloud server 120. The "instruction" is used for the cloud server 120 to control the operation of the intermediary apparatus 110. The data is used for data transmission and exchange between the middleware 110 and the cloud server 120. The mediation device 110 of the present application reports the event type to the cloud server 120 in real time when receiving the event. Compared with the communication protocol of the terminal device 140 in the prior art, the cloud server 120 does not need to wait for all the terminal devices 140 to be polled to know that an event occurs in one terminal device 140. When the cloud server 120 wants to operate the remote device, the cloud server 120 may forward the command to the gateway 130 and the intermediary device 110 through the virtual access model, and the intermediary device 110 sends the command to the terminal device 140.
To ensure the integrity of the network packet during transmission, the first processing unit 111 pre-stores the second network packet in the first output buffer unit 114 before the first management program 116 sends the second network packet. The first output buffer unit 114 loads the new second network packet after the existing second network packet is sent. Therefore, the first management program 116 adjusts the data sending rate of the first output buffer unit 114 according to the transmission status of the network, so as to avoid the data overflow (overflow) of the cloud server 120.
The data overflow occurs mainly when the network transmission rate is unstable, the buffer unit of the receiver has not processed the received packet, but the subsequent network packets are received continuously. This causes the network packet at the receiving end to be converted back to data (or instructions), resulting in missing pieces of data (or instructions) or incorrect translations. Similarly, before the second hypervisor 126 sends the first network packet, the second processing unit 121 pre-stores the first network packet in the second output buffer unit 123.
The first processing unit 111 determines to sequentially send the corresponding device commands to the corresponding terminal devices 140 according to the priority of the "event", "data", or "instruction" translated by the first network packet. Generally, "events" are prioritized over "instructions" and "data". The priority of the "instruction" is higher than that of the "data". When the mediation apparatus 110 receives the "event", the mediation apparatus 110 interrupts the "instruction" or "material" currently being processed to preferentially execute the "event".
After the terminal device 140 executes the received device command, the terminal device 140 may return the reply response after completing the relevant operation. The middleware 110 converts the reply response into a second network packet and transmits the second network packet to the cloud server 120. For example, when the card reader 522 of terminal device 140 is reading a card, a reply response is returned when the card is read. The end device 140 transmits the reply response to the cloud server 120 through the mediation device 110 and the gateway 130.
During the transmission between the middleware 110 and the cloud server 120, both sides monitor whether the packet receiving integrity rates match. The packet reception integrity rate is the integrity of the network packet. Because the network packet may be collided or disconnected during transmission, the sender sends excessive network packets to make the receiver not in time to process the packets, thereby causing the packets to overflow. When the packet receiving integrity rate of either party exceeds the traffic threshold, the data throughput of the middleware 110 or the cloud server 120 is adjusted. The packet reception integrity rate is the integrity of the first network packet to the device command or the integrity of the second network packet to the response.
During the process of sending the device command, the cloud server 120 converts the device command into a plurality of first network packets. The mediation device 110 may determine the reception integrity rate of the device command with respect to the number of first network packets. When the processing speed of the receiver cannot catch up with the packet transmission, the packet transmitted by the transmitter may not be received by the receiver. Therefore, when the situation occurs, the sending party can reduce the transmission speed of the packet, so that the receiving party can ensure the analysis processing of the packet. Since the middleware 110, the gateway 130, and the cloud server 120 may be a sender or a receiver, the middleware 110, the gateway 130, and the cloud server 120 configure the cache processing mechanism.
For clarity of the overall operation of the present application, the operations of the cloud server 120, the gateway 130, the mediation device 110 and the connected terminal device 140 are described below. Please refer to fig. 4A-4C, which are schematic diagrams illustrating connection, configuration and control of a plurality of local area network processing systems according to the present application. In fig. 4A, two different area networks are provided, which are connected to the cloud server 120 through a first gateway 411 and a second gateway 412, respectively. The first gateway 411 connects the first mediation device 511 and the second mediation device 512, and the second gateway 412 connects the third mediation device 513.
The first intermediate device 511 is electrically connected to the two terminal devices 140, which are assumed to be a warning light 521(RS-485) and a card reader 522(RS-232), respectively. The second mediation device 512 is connected to a thermometer 523(Digital I/O). The third intermediary device 513 is electrically connected to an electronic scale 524(RS-232), which is shown in parentheses to represent the physical communication interface 115 to which the end device 140 is connected.
First, when the first gateway 411 is connected to an external network segment, the first gateway 411 sends a connection request to the cloud server 120 for establishing a connection between the first gateway 411 and the cloud server 120. In addition, when the first gateway 411 is connected to the local area network, the first gateway 411 broadcasts an identification request to the mediation device 110. When any one of the middleware 110 receives the identification request, the middleware 110 replies the device information 117 to the cloud server 120 according to the identification request. Assuming that the first middleware 511 receives the identification request, the first middleware 511 will return the device information 117 to the cloud server 120. The cloud server 120 will add the first mediation device 511 to the existing connection list 127. Similarly, the cloud server 120 also adds the second intermediary 512 and the third intermediary 513 to the connection list 127. If an illegal middleware 110 is installed in the network segment, the cloud server 120 also receives the corresponding device information 117. Cloud server 120 may determine whether to add intermediary device 110 to existing wiring list 127. If the cloud server 120 does not add the intermediary apparatus 110 to the connection list 127, the cloud server 120 will not establish a network connection with the intermediary apparatus 110.
Then, the cloud server 120 loads the virtual communication interfaces according to the device information 117 of different middleware 110. In other words, the virtual communication interface of the middleware 110 is loaded in the operating system 125 of the cloud server 120. In this example, the cloud server 120 loads the virtual communication interfaces of RS-485, RS-232 and Digital I/O. Each virtual communication interface may be assigned a different virtual access model for distinguishing between various types of remote devices. The user can select different virtual access models and adjust the relevant attributes of the virtual access models according to the requirements of the remote device. For example, the virtual access model of RS-232 requires a set transfer Rate (Baud Rate) to properly drive the card reader 522. However, for the thermometer 523, the virtual access model of the Digital I/O can obtain the temperature value without setting the transfer rate. Thus, for different types of remote devices, the user can configure various attributes of the virtual access model to fit various remote devices and physical communication interfaces 115.
After the loading of the virtual communication interface is completed, the connected middleware 110 is displayed in the screen of the second hypervisor 126, as shown in FIG. 4B. The first mediation device 511, the second mediation device 512, and the third mediation device 513 are respectively displayed in the second hypervisor 126 of fig. 4B. Since the associated virtual access model is not set, only the connected middleware 110 is displayed in the second hypervisor 126.
The user selects the first mediation device 511 at the interface of the second hypervisor 126 and designates corresponding remote devices for the various virtual communication interfaces of the first mediation device 511, respectively. In the process of configuring the remote device, the user only needs to assign the name, type and configuration virtual access model of the remote device to complete the related loading and configuration of the remote device, and the interface of the second hypervisor 126 is shown in fig. 4C. The same selection process is also performed for the second mediation apparatus 512 and the third mediation apparatus 513.
After the user completes the related settings of the remote device, the second hypervisor 126 will control the data access or command of the virtual communication interface through the remote device and the virtual access model. In fig. 4C, the first mediation device 511 and the thermometer 523 are selected, and the thermometer 523 of the remote device obtains the actual value of the terminal device 140 through the virtual access model in the display screen of the second management program 126 and displays the actual value in the screen of the second management program 126. In fig. 4C, when the user selects the thermometer 523, the right screen shows the relationship between the temperature and the time.
In addition, the present application may also achieve the goal of fast deployment when a new mediation device 110 is replaced. As mentioned above, when installing a new middleware 110, the cloud server 120 adds the new middleware 110 to the connection list 127. In addition, the connection list 127 also records the relevant environment parameters of the intermediary apparatus 110 and the connected terminal apparatus 140, as shown in fig. 5A. Therefore, the user can export (export) the connection list 127 at any time. Assume that mediation devices a, b, c are present in any one of the regional network segments and that mediation device b is malfunctioning. When the worker replaces the middleware b, the cloud server 120 disables (disable) the replacement target middleware b. The worker simply removes the old mediation device b and replaces it with the new mediation device d. After replacing the new middleware d, the gateway 130 also obtains the device information 117 of the middleware d and transmits it to the cloud server 120. The connection list 127 of the cloud server 120 also adds a new intermediary device d, as shown in fig. 5B. The user can retrieve the environmental parameters of the replaced mediation device b from the existing connection list 127 and apply the environmental parameters to the newly added mediation device d and the terminal device 140.
For the manufacturer of the development system, the manufacturer only needs to provide various communication interfaces and corresponding virtual access models, and does not need to establish all the terminal devices 140 and related parameters. Therefore, the manufacturer can set the actual terminal device 140 by the user by only providing the corresponding virtual access model for the communication interface. On the side of the cloud server 120, the user only needs to provide various parameters for the terminal device 140 to connect to, and set the corresponding virtual access model, so as to drive the operation of the remote device. The processing system and method of the ethernet-based remote device targeting and control mechanism of the present application can provide the cloud server 120 with a fast deployment infrastructure, and can also achieve data access and device control for the terminal device 140.
The method and the system for processing the abstract and simulated behaviors of the remote equipment provide a data transmission pipeline from a cloud server to the terminal equipment, and are used for meeting the requirements of data acquisition and equipment control of the Internet of things. The background staff does not need to set the terminal equipment on the working site to finish the operation, and the cloud control terminal can select the connected terminal equipment. When the middleware is damaged, a worker only needs to replace the damaged middleware with new middleware and then loads the corresponding environment profile at the cloud server to drive the newly installed middleware.
The device corresponds to the description of the method flow, and the description of the method flow is referred for the deficiency, and is not repeated. The foregoing description shows and describes several preferred embodiments of the present application, but as aforementioned, it is to be understood that the application is not limited to the forms disclosed herein, but is not to be construed as excluding other embodiments and is capable of use in various other combinations, modifications, and environments and is capable of changes within the scope of the inventive concept as expressed herein, commensurate with the above teachings, or the skill or knowledge of the relevant art. And that modifications and variations may be effected by those skilled in the art without departing from the spirit and scope of the application, which is to be protected by the claims appended hereto.
Claims (10)
1. A processing method for the abstraction and simulation behaviors of a remote device is characterized in that the connection identification and operation of the remote device are controlled, and the processing method for the abstraction and simulation behaviors of the remote device comprises the following steps:
a gateway network connected to a cloud server and at least one intermediary device;
receiving device information of each intermediary equipment by the gateway, wherein the device information records the type and the number of a physical communication interface of the intermediary equipment and forwards the device information to the cloud server;
the entity communication interface is electrically connected with the terminal equipment;
the cloud server generates a corresponding virtual communication interface according to the device information;
establishing at least one virtual device for the virtual communication interface, and setting a virtual access model of the virtual device according to the attribute of the terminal device;
selecting any one of the virtual devices, and loading the selected virtual device as a remote device by the cloud server;
the cloud server encapsulates an equipment command into a first network packet through the virtual access model;
the gateway receives the first network packet and forwards the first network packet to the corresponding intermediary equipment, and the intermediary equipment converts the received first network packet into the equipment command;
the intermediary equipment converts a reply response into a second network packet;
sending the second network packet to the gateway, and forwarding the second network packet to the cloud server through the gateway; and
converting the second network packet into the reply response by the virtual access model:
if the intermediary device is damaged, the intermediary device can be replaced independently, the relevant information of the device is updated through the gateway and is transmitted to the cloud server, and the original environment parameters are applied to the replaced intermediary device and the terminal device, so that the control of the terminal device can be simplified under the condition of not changing field bus wiring.
2. The method of claim 1, wherein the encapsulating the device command by the virtual access model further comprises: setting an operation attribute of the equipment command, wherein the operation attribute is an instruction, data and an event.
3. The method of claim 2, wherein converting the reply response into the second network packet further comprises: and setting an operation attribute of the reply response, wherein the operation attribute is an instruction, data and an event.
4. The method according to claim 3, wherein the receiving the reply response by the virtual access model comprises: the virtual access model determines an order of the reply responses based on the operation attributes, wherein events are prioritized over instructions and instructions are prioritized over data.
5. The method of claim 1, wherein the second network packet is encapsulated and identified by a media access control layer.
6. The method of claim 1, wherein the step of processing the abstracted and simulated behavior of the remote device prior to sending the first network packet further comprises:
the cloud server and the intermediary device respectively detect a packet receiving integrity rate of a transmission process;
when the packet receiving integrity rate exceeds a traffic threshold, the cloud server reduces the data output of the first network packet; and
when the packet receiving integrity rate exceeds the traffic threshold, the intermediary device reduces the data throughput of the second network packet.
7. A system for processing abstract and simulated behavior of a remote device, the system for processing abstract and simulated behavior of a remote device for connection and control of the remote device, the system comprising:
an intermediary device, it includes a first processing unit, a first network unit, a first storage unit and a entity communication interface, the first processing unit is connected to the first network unit, the first storage unit and the entity communication interface electrically, the entity communication interface connects a terminal installation electrically, the first processing unit changes a first network packet into an equipment order and sends to the terminal installation, the first processing unit changes a reply response of the terminal installation into a second network packet, the first storage unit stores a device information, the device information records a kind and quantity of an entity communication interface of the intermediary device;
a cloud server, which includes a second processing unit, a second network unit and a second storage unit, wherein the second processing unit is electrically connected to the second network unit and the second storage unit, the second network unit is connected to the intermediary device, the second processing unit establishes a connection list according to the connected intermediary device, the second processing unit establishes a corresponding virtual communication interface according to the device information, the second processing unit establishes at least one virtual device for the virtual communication interface, the second processing unit mounts the selected virtual device as a remote device, the second processing unit sets a virtual access model corresponding to the remote device, and the second processing unit transmits the device command or the reply response through the virtual access model; and
a gateway, which includes a third processing unit, a third network unit, a fourth network unit and a third storage unit, wherein the third processing unit is electrically connected to the third network unit, the fourth network unit and the third storage unit, the third network unit is connected to the intermediary equipment, the fourth network unit is connected to the cloud server via a network, the third processing unit is used for converting an identification information of the first network packet and the second network packet, and the third storage unit temporarily stores the identification information.
8. The system according to claim 7, wherein the gateway repackages the first network packet with a media access control layer and the gateway repackages the second network packet with a transport control layer according to the intermediary device to be sent.
9. The system as claimed in claim 7, wherein the intermediary device further comprises a first output buffer unit electrically connected to the first output buffer unit, the first output buffer unit being configured to buffer the second network packet to be transmitted, the cloud server comprises a second output buffer unit electrically connected to the second output buffer unit, the second output buffer unit being configured to buffer the first network packet to be transmitted.
10. The system of claim 7, wherein the cloud server and the intermediary monitor a packet integrity rate of both parties, and when the packet integrity rate is higher than a traffic threshold, the cloud server and the intermediary adjust the throughput of network packets.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810819733.6A CN110753075B (en) | 2018-07-24 | 2018-07-24 | Method and system for processing abstract and simulation behaviors of remote equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810819733.6A CN110753075B (en) | 2018-07-24 | 2018-07-24 | Method and system for processing abstract and simulation behaviors of remote equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110753075A CN110753075A (en) | 2020-02-04 |
| CN110753075B true CN110753075B (en) | 2022-06-17 |
Family
ID=69275428
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810819733.6A Active CN110753075B (en) | 2018-07-24 | 2018-07-24 | Method and system for processing abstract and simulation behaviors of remote equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110753075B (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102197370A (en) * | 2008-11-03 | 2011-09-21 | 国际商业机器公司 | Maintaining storage area network ('SAN') access rights during migration of operating systems |
| CN102281180A (en) * | 2011-07-14 | 2011-12-14 | 冶金自动化研究设计院 | Virtual network interface card (NIC) communication device applied in mutual communication of terminals in different local area networks |
| CN103412519A (en) * | 2013-04-24 | 2013-11-27 | 昆山三泰新电子科技有限公司 | Remote peripheral control system, method and remote server thereof |
| CN103425479A (en) * | 2012-04-25 | 2013-12-04 | 威睿公司 | User interface for remote device virtualization |
| CN104090650A (en) * | 2014-05-30 | 2014-10-08 | 昆山三泰新电子科技有限公司 | Control system for multi-user operation in single computer, and control method for multi-user operation in single computer |
| TW201442464A (en) * | 2013-04-24 | 2014-11-01 | Sunix Co Ltd | The controlling system and the method of the remote device and the server |
| CN105874744A (en) * | 2013-12-18 | 2016-08-17 | 瑞典爱立信有限公司 | System and method for virtualizing a remote device |
| CN105933165A (en) * | 2016-06-28 | 2016-09-07 | 合肥润东通信科技股份有限公司 | Wireless routing management application system special for Internet of things |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR101495862B1 (en) * | 2011-05-18 | 2015-03-13 | 한국전자통신연구원 | Virtual server and virtual machine management method for supporting zero client |
| US20150156266A1 (en) * | 2013-11-29 | 2015-06-04 | Qualcomm Incorporated | Discovering cloud-based services for iot devices in an iot network associated with a user |
-
2018
- 2018-07-24 CN CN201810819733.6A patent/CN110753075B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102197370A (en) * | 2008-11-03 | 2011-09-21 | 国际商业机器公司 | Maintaining storage area network ('SAN') access rights during migration of operating systems |
| CN102281180A (en) * | 2011-07-14 | 2011-12-14 | 冶金自动化研究设计院 | Virtual network interface card (NIC) communication device applied in mutual communication of terminals in different local area networks |
| CN103425479A (en) * | 2012-04-25 | 2013-12-04 | 威睿公司 | User interface for remote device virtualization |
| CN103412519A (en) * | 2013-04-24 | 2013-11-27 | 昆山三泰新电子科技有限公司 | Remote peripheral control system, method and remote server thereof |
| TW201442464A (en) * | 2013-04-24 | 2014-11-01 | Sunix Co Ltd | The controlling system and the method of the remote device and the server |
| CN105874744A (en) * | 2013-12-18 | 2016-08-17 | 瑞典爱立信有限公司 | System and method for virtualizing a remote device |
| CN104090650A (en) * | 2014-05-30 | 2014-10-08 | 昆山三泰新电子科技有限公司 | Control system for multi-user operation in single computer, and control method for multi-user operation in single computer |
| CN105933165A (en) * | 2016-06-28 | 2016-09-07 | 合肥润东通信科技股份有限公司 | Wireless routing management application system special for Internet of things |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110753075A (en) | 2020-02-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP6073287B2 (en) | Method and apparatus for sending a device description file to a host | |
| CN108847979B (en) | Self-adaptive configuration system and method based on SCADA | |
| CN111656336B (en) | PCIE sending and receiving method, device, equipment and system | |
| US11128726B2 (en) | Transmission method | |
| CN108351859B (en) | Direct memory access for endpoint devices | |
| JP2019515375A (en) | Connection unit for monitoring automation system, monitoring system, and operation method | |
| US20090177289A1 (en) | Block-orientated control system having wireless gateway for communication with wireless field devices | |
| WO2006091040A1 (en) | Layer structure of network control protocol and interface method | |
| US20100205600A1 (en) | Simulation method for realizing large batches and different kinds of baseboard management controllers using a single server | |
| US20140334490A1 (en) | Communication device, management device, processing method, and computer-readable recording medium having processing program stored therein | |
| CN103685580A (en) | Software-defined-network-based northbound interface access system and method | |
| CN112640386B (en) | Method and simulation system for simulating the handling of reservation requests for multicast data streams in a communication network | |
| US6738829B1 (en) | System and method for implementing a generic enhanced network driver | |
| CN110753075B (en) | Method and system for processing abstract and simulation behaviors of remote equipment | |
| US8891405B2 (en) | Integrated device management over Ethernet network | |
| JP5185383B2 (en) | Control node for a network consisting of multiple control nodes | |
| CN110750075B (en) | System and method for regional data acquisition and equipment control of Internet of things | |
| TWI659632B (en) | THE CONTROL SYSTEM AND THE METHOD FOR THE DATA FETCHING OF THE LAN IN THE IoT | |
| TWI673981B (en) | The processing method and the system of the remote device about the abstraction and behavior simulation | |
| TWI669981B (en) | The process system and the method of the remote device objectification and control mechanism base on the ethernet | |
| US11973652B2 (en) | Field detection device for a fieldbus network | |
| WO2022254953A1 (en) | Control system and control method | |
| US9081743B2 (en) | Communication system and communicaton method | |
| TWI755049B (en) | The processing system of the controlling iot equipment, the method and the gateway | |
| US20030065822A1 (en) | Switch box appliance |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |