CN110855680A - Internet of things equipment docking method and device - Google Patents

Internet of things equipment docking method and device Download PDF

Info

Publication number
CN110855680A
CN110855680A CN201911125304.XA CN201911125304A CN110855680A CN 110855680 A CN110855680 A CN 110855680A CN 201911125304 A CN201911125304 A CN 201911125304A CN 110855680 A CN110855680 A CN 110855680A
Authority
CN
China
Prior art keywords
interface
equipment
message
internet
protocol
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.)
Granted
Application number
CN201911125304.XA
Other languages
Chinese (zh)
Other versions
CN110855680B (en
Inventor
刘佩云
温秀秀
王楠
窦攀松
杨璧竹
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
CETC Information Science Research Institute
Original Assignee
CETC Information Science Research Institute
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by CETC Information Science Research Institute filed Critical CETC Information Science Research Institute
Priority to CN201911125304.XA priority Critical patent/CN110855680B/en
Publication of CN110855680A publication Critical patent/CN110855680A/en
Application granted granted Critical
Publication of CN110855680B publication Critical patent/CN110855680B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/12Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/08Protocols for interworking; Protocol conversion

Abstract

The invention relates to the technical field of Internet of things, in particular to a method and a device for butting equipment of the Internet of things, wherein the method comprises the following steps: acquiring a first device interface message which is in accordance with a first device interface protocol and aims at a first Internet of things device; determining a docking device interface message for a second internet-of-things device to be docked with the first internet-of-things device; according to a pre-configured interface protocol conversion rule, converting the interface message of the docking equipment into a second equipment interface message which conforms to a second equipment interface protocol applicable to the second networking equipment; and sending the second device interface message to the second networking device. Therefore, the difficulty and complexity of the butt joint of the Internet of things integration platform can be effectively reduced, and the method has the advantages of strong expandability, good maintainability and the like.

Description

Internet of things equipment docking method and device
Technical Field
The invention relates to the technical field of Internet of things, in particular to a method and a device for butting equipment of the Internet of things.
Background
Along with the rapid development of the technology of the internet of things in recent years, the variety of objects in the internet of things is more and more abundant, the number of application systems of the internet of things is also rapidly developed, how to realize the unified access and control of equipment of cross-equipment type cross-system of cross-manufacturer brand at present, and further the realization of the linkage demand among the equipment is a key problem to be solved in the application scheme of the current internet of things industry, such as smart buildings/communities/parks and the like, the construction scheme relates to the integration and management of systems and equipment such as security, fire control and elevators, and the like, and the situation that the entrance guard is in an open state and the elevator is in a non-use state when the fire alarm for fire control needs to be realized is related to the linkage monitoring and execution of fire alarm equipment, entrance guard equipment and elevator equipment, and the precondition for the linkage monitoring and execution is, And (4) integration of a security access control system and elevator equipment.
Nowadays, the unified access and control scheme of the integrated application of the internet of things to the equipment which is cross-manufacturer, cross-type and cross-system has the following problems: at present, a centralized operation management and control system is uniformly planned for cross-industry and cross-system equipment access management and control of the Internet of things, centralized management of subsystems and equipment access management are achieved, and development scenes are customized according to requirements. The scheme has poor compatibility and difficult later expansion. When a new subsystem or a new type or other brands of equipment needs to be accessed, besides the docking development, when the equipment is linked with the equipment accessed before, the operation and maintenance cost of the actual scheme is high because the prior implementation logic needs to be known to complete.
In view of the above problems, there is no better solution in the industry at present.
Disclosure of Invention
The invention aims to provide an Internet of things equipment docking method and device, which are used for at least solving the problem that the Internet of things equipment is difficult to dock across manufacturers, types or systems in the prior art.
In order to achieve the above object, an aspect of the present invention provides an internet of things device docking method, including: acquiring a first device interface message which is in accordance with a first device interface protocol and aims at a first Internet of things device; determining a docking device interface message for a second internet-of-things device to be docked with the first internet-of-things device; according to a pre-configured interface protocol conversion rule, converting the interface message of the docking equipment into a second equipment interface message which conforms to a second equipment interface protocol applicable to the second networking equipment; and sending the second device interface message to the second networking device.
Optionally, the interface protocol conversion rule includes at least one interface protocol conversion rule between the first provisioning device interface protocol and at least one second provisioning device interface protocol, wherein converting the docking device interface message into a second device interface message conforming to the second device interface protocol according to the preconfigured interface protocol conversion rule includes: judging whether the interface message of the docking equipment conforms to the first set equipment interface protocol or not; when the interface message does not accord with the first set equipment interface protocol, converting the interface message of the butt joint equipment into a media message which accords with the first set equipment interface protocol according to a first interface protocol conversion rule; determining a target interface protocol conversion rule from the at least one conversion rule according to the first set equipment interface protocol and a second equipment interface protocol corresponding to the interface message of the docking equipment; and converting the media message into a second equipment interface message according to the target interface protocol conversion rule.
Optionally, the method further comprises: and when the equipment interface message conforms to the first set equipment interface protocol, converting the interface message of the butt joint equipment into the equipment interface message conforming to the second equipment interface protocol according to a second interface protocol conversion rule.
Optionally, the obtaining the interface message of the docking device includes: converting the first equipment interface message into an encapsulation message conforming to the first set equipment interface protocol according to an interface protocol conversion rule aiming at the first equipment interface protocol; sending the encapsulation message to an operation server; and responding to the packaging message, and acquiring the interface message of the docking equipment from the operation server.
Optionally, the first setting device interface protocol includes an HTTP protocol.
Optionally, the second setting device interface protocol includes at least one device interface protocol of the following: TCP/IP protocol, MODBUS TCP/IP protocol, MQTT protocol, ONVIF protocol, and NB-IoT protocol.
Optionally, the device interface message includes device attribute description information and interface description information; the device attribute description information includes at least one of: a device ID, an interface type, a device model, and a device location, the interface description information including at least one of: interface name, interface function information, interface parameter information, device docking verification information, and interface return value information.
Another aspect of the present invention provides an internet of things device docking apparatus, including: the device interface message acquisition unit is configured to acquire a first device interface message which is in accordance with a first device interface protocol and is aimed at a first Internet of things device; a docking message determining unit configured to determine a docking device interface message for a second internet-of-things device to be docked with the first internet-of-things device; the equipment interface protocol conversion unit is configured to convert the interface message of the docking equipment into a second equipment interface message which conforms to a second equipment interface protocol applicable to the second networking equipment according to a pre-configured interface protocol conversion rule; a sending unit configured to send the second device interface message to the second networked device.
Another aspect of an embodiment of the present invention provides an electronic device, including: the device comprises at least one processor and a memory communicatively connected with the at least one processor, wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the steps of the internet of things device docking method.
Another aspect of the embodiments of the present invention provides a storage medium, on which a computer program is stored, where the computer program is executed by a processor to implement the steps of the method for interfacing internet of things device as described above.
In the scheme disclosed by the invention, a first device interface message of a first Internet of things device is obtained, a docking device interface message of a second Internet of things device to be docked with the first Internet of things device is determined, the docking device interface message is converted into a second device interface message conforming to a second device interface protocol applicable to the second Internet of things device according to a preconfigured interface protocol conversion rule, and then the second device interface message is sent to the second Internet of things device. Therefore, data processing operation is carried out based on the interface protocol conversion rule, docking between the Internet of things devices with different device interface protocols can be realized, the problems of uniform access and management and control of the integrated application of the Internet of things to the devices across manufacturers, types and systems are solved, the docking difficulty and complexity of the integrated platform of the Internet of things can be effectively reduced, and the integrated platform of the Internet of things has the advantages of strong expandability, good maintainability and the like.
Additional features and advantages of embodiments of the invention will be set forth in the detailed description which follows.
Drawings
Fig. 1 shows a flowchart of an example of an internet of things device docking method according to an embodiment of the present invention;
fig. 2 shows a signal flow diagram of an example of an internet of things device docking method according to a first embodiment of the present invention;
fig. 3 shows a signal flow diagram of an example of an internet of things device docking method according to a second embodiment of the present invention;
fig. 4 shows a system architecture schematic diagram of an example of an internet of things device docking method suitable for applying an embodiment of the invention;
FIG. 5 illustrates a schematic diagram of an example of a device description configuration for docking in a platform tier in accordance with an embodiment of the present invention;
fig. 6 is a block diagram illustrating an example of an internet of things device docking apparatus according to an embodiment of the present invention.
Detailed Description
The following detailed description of embodiments of the invention refers to the accompanying drawings. It should be understood that the detailed description and specific examples, while indicating the present invention, are given by way of illustration and explanation only, not limitation.
Fig. 1 is a flowchart illustrating an example of a method for interfacing internet of things devices according to an embodiment of the present invention. The implementation subject of the method of the embodiment of the present invention may be a device responsible for docking the internet of things device, such as an internet of things docking platform.
As shown in fig. 1, in step 110, a first device interface message conforming to a first device interface protocol for a first internet of things device is obtained. Here, the device interface message may include device attribute description information and interface description information for interfacing with the corresponding device.
In particular, a first device interface message may be received from the first internet of things device, which is compliant with a first device interface protocol of the first internet of things device, such as a TCP/IP protocol or an MQTT protocol.
In step 120, a docking device interface message of a second internet-of-things device to be docked with the first internet-of-things device is determined.
In one example, the dock interface message may be determined by a local data analysis process, for example, the dock interface message may be determined based on the pre-configuration information (e.g., the pre-set docking configuration) and the first device interface message. In another example, it may also be that a first device interface message is interacted with and received from a third party device (e.g., an operations server), as will be described in more detail below.
In step 130, the dock interface message is converted into a second device interface message conforming to a second device interface protocol applicable to the second networked device according to the preconfigured interface protocol conversion rule.
It should be noted that, an interface protocol conversion rule for converting various interface protocols may be configured in the internet of things docking platform, for example, the interface protocol conversion rule is for a first device interface protocol and a second device interface protocol. In another example, multiple interface protocol conversion rules may be applied, for example, each interface protocol conversion rule is formulated for setting up a device interface protocol (e.g., HTTP protocol), as will be developed in more detail below.
In step 140, a second device interface message is sent to the second networked device. Therefore, the interface message of the docking equipment for the second networking equipment is converted into the interface protocol of the second equipment suitable for the second networking equipment, so that even if the protocols of different pieces of equipment of the Internet of things are not shared, the docking between the pieces of equipment of the Internet of things can be realized, and a convenient condition is provided for the development of the integrated application function of the Internet of things.
Fig. 2 is a signal flow diagram illustrating an example of an internet of things device docking method according to a first embodiment of the present invention.
As shown in fig. 2, in step 210, the first internet of things device 10 sends a first device interface message to the internet of things docking platform 20.
Next, in step 220, the internet of things docking platform 20 uses the pre-set docking configuration to determine a dock interface message for responding to the first device interface message, which may be used to access the second networked device. Here, the docking configuration may be a plurality of sets of device interface message pairs, the device interface messages including device attribute description information and interface description information, so that when one message (i.e., a first device interface message) is received, another matching message (i.e., a docking device interface message) can be invoked to respond.
Illustratively, the device attribute description information includes at least one of: device ID, interface type, device model, and device location. Further, the interface description information includes at least one of: interface name, interface function information, interface parameter information, device docking verification information, and interface return value information. The equipment attribute description information and the interface description information can realize butt-joint communication with the equipment of the Internet of things.
Next, in step 230, the internet of things docking platform 20 determines a second device interface message using the interface protocol conversion rule. Here, the interface protocol corresponding to the dockee interface message may not be applicable to the second networked device, and thus the dockee interface message may be converted into the corresponding device interface protocol by the interface protocol conversion rule.
In some embodiments, the interface protocol conversion rules include at least one interface protocol conversion rule for between a first provisioned device interface protocol and at least one second provisioned device interface protocol. Illustratively, the first device interface protocol is an HTTP protocol, and the second setting device interface protocol includes at least one device interface protocol of the following: TCP/IP protocol, MODBUS TCP/IP protocol, MQTT protocol, ONVIF protocol, and NB-IoT protocol. That is, the interface protocol conversion rules are conversion protocols of other device interface protocols with respect to the HTTP protocol. For example, the determined docking device interface message from the docking configuration is compliant with the HTTP protocol, which can be converted into a second device interface message compliant with the second device interface protocol by the interface protocol conversion rules. However, if the dock interface message is not compliant with the HTTP protocol, multiple protocol conversions may be required to determine the second device interface message.
Specifically, it may be determined whether the interface message of the docking device conforms to a first set device interface protocol, and when the interface message of the docking device does not conform to the first set device interface protocol (for example, the HTTP protocol), the interface message of the docking device is converted into a media message conforming to the first set device interface protocol according to a first interface protocol conversion rule. And then, determining a target interface protocol conversion rule from the at least one conversion rule according to the first set equipment interface protocol and a second equipment interface protocol corresponding to the interface message of the docking equipment. Further, the intermediary message may be converted to a second device interface message according to the target interface protocol conversion rules.
Further, when the first set device interface protocol (e.g., HTTP protocol) is satisfied, the docking device interface message may be converted into a device interface message conforming to the second device interface protocol according to the second interface protocol conversion rule.
Next, in step 240, the internet of things docking platform 20 may send the second device interface message to the second internet of things device 30, so as to implement docking communication between the internet of things devices.
In another example of embodiment of the present invention, the docking configuration may be determined through interaction with the operation server 40.
Fig. 3 shows a signal flow diagram of an example of an internet of things device docking method according to a second embodiment of the present invention.
As shown in fig. 3, in step 310, the first internet of things device sends a first device interface message to the internet of things docking platform 20.
Next, in step 320, the internet of things docking platform 20 may determine an encapsulation message using the first interface protocol conversion rule. Here, the encapsulated message may be compliant with the HTTP protocol.
Next, in step 330, the internet of things docking platform 20 sends the encapsulation message to the operation server 40. In this way, the operation and maintenance staff may analyze the encapsulation message at the operation server 40, thereby determining a second internet-of-things device to be docked with the first internet-of-things device corresponding to the encapsulation message, and determining corresponding device attribute description information and interface description information (i.e., a docking device interface message).
Next, in step 340, the operation server 40 sends a docking device interface message to the internet of things docking platform 20. It will be appreciated that the dock interface message at this time should be compliant with the HTTP protocol.
Next, in step 350, the internet of things docking platform 20 determines a second device interface message using the second interface protocol conversion rule. For example, the internet of things docking platform 20 converts the docking device interface message into a second device interface message corresponding to a second device interface protocol. With respect to the operation of step 350, reference may be made to the description above with reference to step 230 in FIG. 2.
Next, in step 360, the internet of things docking platform 20 sends a second device interface message to the second networked device. Therefore, the first Internet of things equipment and the second Internet of things equipment are in butt joint communication through interactive configuration operation of the operation server.
In the embodiment of the invention, from the interactive interface type of the equipment, the standardized information description is carried out on various interface types based on the description, so that the expansion and the management of the interface equipment of the same type are facilitated.
Fig. 4 shows a schematic diagram of an example system architecture of an internet of things device docking method suitable for applying an embodiment of the present invention.
The system architecture shown in fig. 4 includes an application layer, a platform layer, and a device layer, and by implementing the solution according to the embodiment of the present invention, at least interfacing between different types of internet of things devices in the device layer can be implemented.
The access modes of the equipment in the existing industry internet of things solution can be divided into two major categories, namely direct butt joint equipment and an application system where the butt joint equipment is located. The devices directly connected to each other can be classified into smart devices and non-smart devices. Smart devices are devices that can be directly networked, such as webcams, TCP/IP protocols, NB-IoT, and the like. Non-intelligent devices are devices that must pass through a gateway to be networked; the system equipment realizes the interaction function with the equipment only through an interface provided by an Internet of things application system where the docking equipment is located.
The main function of the platform layer is to realize the docking and interaction of three types of device sources of the device layer, and is also one of the main emphasized parts in the application of the invention. Description information (e.g., protocol conversion rules) for interface protocol types such as HTTP, TCP/IP, MODBUS TCP/IP, MQTT, ONVIF, and NB-IoT are included in the platform layer. Therefore, a uniform HTTP interface is provided for the upper package, and an interface for adapting an interface protocol is provided for the lower package. In particular, device interfaces may be managed, encapsulated, and unified in a description-based manner. Firstly, various interface protocols of the equipment are called and encapsulated, such as HTTP type interface encapsulation get, post, put, delete methods, TCP/IP protocol encapsulation message sending methods and the like. And secondly, extracting according to parameters and return values required by each type of packaged interface, wherein the extracted information is field change information required by calling the type of interface, and describing and storing the information, so that the workload and the cost of operation and maintenance docking can be reduced.
As shown in fig. 5, an example of a configuration is described for a device in a platform layer. It should be understood that the device description given in fig. 5 focuses on information related to the interaction of the device, and not all information considered by the internet of things platform. The device attribute part contains information such as device ID (unique identifier of the device), device name, manufacturer, type, model, device icon, device location, interface type, etc., and some specific information of the device needs to be described according to the interface type of the device, for example, if the device is a network camera, the address, user name and password information of the device need to be described for interaction with the device; in case of a TCP/IP interface, the device also needs information describing the IP address and port number of the device. The interface information part of a device (a device may have multiple interfaces) needs to describe the interface ID (unique identification of an interface), the interface name, the interface direction (up, down, request response), the interface function, the parameter information (incoming parameter information calling the interface, an interface may have multiple parameters), the return value information (return value information calling the interface, resolution rules describing the return value, an interface may have multiple return values).
Further, when interface calling is performed on different internet of things, the interface calling may be performed in conjunction with operations of the device and the operation and maintenance server (such as the operations described in fig. 3 above). That is to say, the call flow of the interface is divided into two directions, where one direction is initiated by a device (i.e., a first internet of things device), for example, device data is reported, and is pushed to a platform layer through an interface provided by the device layer, the platform layer performs operations such as data processing, storage, and pushing to an upper layer subscriber, and an upper layer application receives data for analysis or display. In addition, the other direction is that an upper application or an upper service logic part (namely, an operation server) initiates equipment control or query information, a unified HTTP interface provided by a platform layer is called, equipment ID, interface ID and parameter information are transmitted, the platform layer acquires the interface type and the interface information according to a description file of the equipment, a called lower-layer encapsulated interface is determined, and the equipment interaction is realized through the interface provided by the equipment layer.
In some embodiments, the device ID, the interface ID, and the parameter information (i.e., the docking device interface message) of the second networked device may also be determined by the docking configuration in the internet of things docking platform, and further details may refer to the operations as described in fig. 2, which are not described herein again.
In the embodiment of the invention, a scheme for accessing and controlling the equipment of the Internet of things based on the description rule is provided, so that the problem of unified access and control of the integrated application of the Internet of things to the equipment which is cross-manufacturer, cross-type and cross-system can be solved. Furthermore, the difficulty and the complexity of the butt joint of the integrated platform of the internet of things can be effectively reduced, the integrated platform of the internet of things has the advantages of being high in expandability, good in maintainability and the like, can be applied to a plurality of industry solutions needing integration, such as smart buildings, smart communities, smart offices, smart parks, smart tourism and the like, and can effectively reduce the integration management cost and the difficulty.
Fig. 6 is a block diagram illustrating an example structure of an internet of things device docking apparatus according to an embodiment of the present invention.
As shown in fig. 6, the internet of things device docking apparatus 600 includes a device interface message acquiring unit 610, a docking message determining unit 620, a device interface protocol converting unit 630, and a transmitting unit 640.
The device interface message obtaining unit 610 obtains a first device interface message compliant with a first device interface protocol for a first internet of things device.
The docking message determining unit 620 determines a docking device interface message for a second internet-of-things device to be docked with the first internet-of-things device.
The device interface protocol conversion unit 630 converts the interface message of the docking device into a second device interface message conforming to a second device interface protocol applicable to the second network device according to the preconfigured interface protocol conversion rule.
The sending unit 640 sends the second device interface message to the second networked device.
The apparatus according to the above embodiment of the present invention may be used to execute the corresponding method embodiment of the present invention, and accordingly achieve the technical effect achieved by the method embodiment of the present invention, which is not described herein again.
In the embodiment of the present invention, the relevant functional module may be implemented by a hardware processor (hardware processor).
In another aspect, an embodiment of the present invention provides a storage medium, on which a computer program is stored, where the program is executed by a processor to perform the steps of the internet of things device docking method as above.
The product can execute the method provided by the embodiment of the application, and has the corresponding functional modules and beneficial effects of the execution method. For technical details that are not described in detail in this embodiment, reference may be made to the methods provided in the embodiments of the present application.
The client of the embodiment of the present application exists in various forms, including but not limited to:
(1) mobile communication devices, which are characterized by mobile communication capabilities and are primarily targeted at providing voice and data communications. Such terminals include smart phones (e.g., iphones), multimedia phones, functional phones, and low-end phones, among others.
(2) The ultra-mobile personal computer equipment belongs to the category of personal computers, has calculation and processing functions and generally has the characteristic of mobile internet access. Such terminals include PDA, MID, and UMPC devices, such as ipads.
(3) Portable entertainment devices such devices may display and play multimedia content. Such devices include audio and video players (e.g., ipods), handheld game consoles, electronic books, as well as smart toys and portable car navigation devices.
(4) And other electronic devices with data interaction functions.
The above-described embodiments of the apparatus are merely illustrative, and the units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment.
Through the above description of the embodiments, those skilled in the art will clearly understand that each embodiment can be implemented by software plus a general hardware platform, and certainly can also be implemented by hardware. Based on such understanding, the above technical solutions substantially or contributing to the related art may be embodied in the form of a software product, which may be stored in a computer-readable storage medium, such as ROM/RAM, magnetic disk, optical disk, etc., and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method according to the embodiments or some parts of the embodiments.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and such modifications or substitutions do not depart from the spirit and scope of the corresponding technical solutions in the embodiments of the present application.

Claims (10)

1. An Internet of things equipment docking method comprises the following steps:
acquiring a first device interface message which is in accordance with a first device interface protocol and aims at a first Internet of things device;
determining a docking device interface message for a second internet-of-things device to be docked with the first internet-of-things device;
according to a pre-configured interface protocol conversion rule, converting the interface message of the docking equipment into a second equipment interface message which conforms to a second equipment interface protocol applicable to the second networking equipment;
and sending the second device interface message to the second networking device.
2. The method of claim 1, wherein the interface protocol conversion rules include at least one interface protocol conversion rule for between a first provisioned device interface protocol and at least one second provisioned device interface protocol,
wherein converting the dock interface message into a second device interface message conforming to a second device interface protocol according to the preconfigured interface protocol conversion rule comprises:
judging whether the interface message of the docking equipment conforms to the first set equipment interface protocol or not;
when the first setting device interface protocol is not met,
converting the interface message of the docking equipment into a media message conforming to the first set equipment interface protocol according to a first interface protocol conversion rule;
determining a target interface protocol conversion rule from the at least one conversion rule according to the first set equipment interface protocol and a second equipment interface protocol corresponding to the interface message of the docking equipment;
and converting the media message into a second equipment interface message according to the target interface protocol conversion rule.
3. The method of claim 2, further comprising:
and when the equipment interface message conforms to the first set equipment interface protocol, converting the interface message of the butt joint equipment into the equipment interface message conforming to the second equipment interface protocol according to a second interface protocol conversion rule.
4. The method of claim 2, wherein obtaining the dock interface message comprises:
converting the first equipment interface message into an encapsulation message conforming to the first set equipment interface protocol according to an interface protocol conversion rule aiming at the first equipment interface protocol;
sending the encapsulation message to an operation server;
and responding to the packaging message, and acquiring the interface message of the docking equipment from the operation server.
5. The method of any of claims 2-4, wherein the first provisioning device interface protocol comprises an HTTP protocol.
6. The method of any of claims 2-4, wherein the second provisioned device interface protocol comprises at least one of: TCP/IP protocol, MODBUS TCP/IP protocol, MQTT protocol, ONVIF protocol, and NB-IoT protocol.
7. The method of claim 1 or 2, wherein the device interface message comprises device attribute description information and interface description information;
the device attribute description information includes at least one of: device ID, interface type, device model, and device location,
the interface description information includes at least one of: interface name, interface function information, interface parameter information, device docking verification information, and interface return value information.
8. An internet of things equipment docking device, comprising:
the device interface message acquisition unit is configured to acquire a first device interface message which is in accordance with a first device interface protocol and is aimed at a first Internet of things device;
a docking message determining unit configured to determine a docking device interface message for a second internet-of-things device to be docked with the first internet-of-things device;
the equipment interface protocol conversion unit is configured to convert the interface message of the docking equipment into a second equipment interface message which conforms to a second equipment interface protocol applicable to the second networking equipment according to a pre-configured interface protocol conversion rule;
a sending unit configured to send the second device interface message to the second networked device.
9. An electronic device, comprising: at least one processor, and a memory communicatively coupled to the at least one processor, wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the steps of the method of any one of claims 1-7.
10. A storage medium on which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 7.
CN201911125304.XA 2019-11-18 2019-11-18 Internet of things equipment docking method and device Active CN110855680B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201911125304.XA CN110855680B (en) 2019-11-18 2019-11-18 Internet of things equipment docking method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201911125304.XA CN110855680B (en) 2019-11-18 2019-11-18 Internet of things equipment docking method and device

Publications (2)

Publication Number Publication Date
CN110855680A true CN110855680A (en) 2020-02-28
CN110855680B CN110855680B (en) 2022-03-11

Family

ID=69601716

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201911125304.XA Active CN110855680B (en) 2019-11-18 2019-11-18 Internet of things equipment docking method and device

Country Status (1)

Country Link
CN (1) CN110855680B (en)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111245961A (en) * 2020-03-16 2020-06-05 绿漫科技有限公司 A thing networking edge magic box device for wisdom community system integrated management
CN111343196A (en) * 2020-03-19 2020-06-26 广州市城建开发集团名特网络发展有限公司 Communication system and communication method compatible with multiple communication protocols
CN112379997A (en) * 2020-10-16 2021-02-19 浪潮通用软件有限公司 Server-side equipment integrated control method
CN114449055A (en) * 2021-12-29 2022-05-06 海南同享数字科技有限公司 Method and device for seamless protocol docking between industrial devices and electronic device
CN114978786A (en) * 2022-05-30 2022-08-30 广州宸祺出行科技有限公司 Method and device for converting third-party interface into system standard interface

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102938770A (en) * 2012-11-22 2013-02-20 亚信联创科技(中国)有限公司 Method for realizing uniform interface for multi-protocol messages and related device and system
CN103428627A (en) * 2012-05-22 2013-12-04 中国移动通信集团江苏有限公司 Method for transferring data in internet of things, internet of things system and corresponding device
CN105379219A (en) * 2014-06-06 2016-03-02 华为技术有限公司 Method, apparatus and system for interacting information in access network
CN105516185A (en) * 2015-12-30 2016-04-20 广东顺德中山大学卡内基梅隆大学国际联合研究院 Multi-protocol gateway equipment
CN108769165A (en) * 2018-05-17 2018-11-06 深圳市信锐网科技术有限公司 Data processing method, Internet of Things access system in a kind of Internet of Things
CN109408247A (en) * 2018-09-17 2019-03-01 天津龙拳风暴科技有限公司 Interaction data processing method and device
CN109857569A (en) * 2018-11-08 2019-06-07 深圳壹账通智能科技有限公司 Interface calling processing method and device, storage medium, computer equipment
CN110430219A (en) * 2019-08-24 2019-11-08 深圳旦倍科技有限公司 Method and system of the various protocols internet of things equipment from adaptation

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103428627A (en) * 2012-05-22 2013-12-04 中国移动通信集团江苏有限公司 Method for transferring data in internet of things, internet of things system and corresponding device
CN102938770A (en) * 2012-11-22 2013-02-20 亚信联创科技(中国)有限公司 Method for realizing uniform interface for multi-protocol messages and related device and system
CN105379219A (en) * 2014-06-06 2016-03-02 华为技术有限公司 Method, apparatus and system for interacting information in access network
CN105516185A (en) * 2015-12-30 2016-04-20 广东顺德中山大学卡内基梅隆大学国际联合研究院 Multi-protocol gateway equipment
CN108769165A (en) * 2018-05-17 2018-11-06 深圳市信锐网科技术有限公司 Data processing method, Internet of Things access system in a kind of Internet of Things
CN109408247A (en) * 2018-09-17 2019-03-01 天津龙拳风暴科技有限公司 Interaction data processing method and device
CN109857569A (en) * 2018-11-08 2019-06-07 深圳壹账通智能科技有限公司 Interface calling processing method and device, storage medium, computer equipment
CN110430219A (en) * 2019-08-24 2019-11-08 深圳旦倍科技有限公司 Method and system of the various protocols internet of things equipment from adaptation

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111245961A (en) * 2020-03-16 2020-06-05 绿漫科技有限公司 A thing networking edge magic box device for wisdom community system integrated management
CN111343196A (en) * 2020-03-19 2020-06-26 广州市城建开发集团名特网络发展有限公司 Communication system and communication method compatible with multiple communication protocols
CN112379997A (en) * 2020-10-16 2021-02-19 浪潮通用软件有限公司 Server-side equipment integrated control method
CN114449055A (en) * 2021-12-29 2022-05-06 海南同享数字科技有限公司 Method and device for seamless protocol docking between industrial devices and electronic device
CN114978786A (en) * 2022-05-30 2022-08-30 广州宸祺出行科技有限公司 Method and device for converting third-party interface into system standard interface
CN114978786B (en) * 2022-05-30 2023-08-22 广州宸祺出行科技有限公司 Method and device for converting third party interface into system standard interface

Also Published As

Publication number Publication date
CN110855680B (en) 2022-03-11

Similar Documents

Publication Publication Date Title
CN110855680B (en) Internet of things equipment docking method and device
JP7012836B2 (en) Network slice management method and equipment
US20230144444A1 (en) Virtual Gateway Control and Management
CN107566786B (en) Method and device for acquiring monitoring video and terminal equipment
CN112055024B (en) Authority verification method and device, storage medium and electronic equipment
CN110417783B (en) Data transmission method and device based on Internet of things, storage medium and terminal
CN112188277B (en) Screen projection control method and device, electronic equipment and computer program medium
CN113741762A (en) Multimedia playing method, device, electronic equipment and storage medium
US10204098B2 (en) Method and system to communicate between devices through natural language using instant messaging applications and interoperable public identifiers
US11947640B2 (en) Adaptive, multi-channel, embedded application programming interface (API)
CN111182074A (en) Intelligent device terminal with edge computing capability and computer-readable storage medium
CN103856520B (en) Communication processing method, server and terminal
CN113038192B (en) Video processing method and device, electronic equipment and storage medium
CN111935177B (en) Service control method and device
CN110708293B (en) Method and device for distributing multimedia service
CN106791992A (en) Signal source method for pushing and system
CN112367297B (en) Service control method and device
CN112367296B (en) Service control method and device
US20150046995A1 (en) Media playing system and media playing method for playing media file in different area network groups
CN112188245B (en) Front-end camera real-time video-on-demand method and device and electronic equipment
CN102170439A (en) Application service expansion system
CN112187810A (en) Front-end equipment control method and device
CN116032691B (en) Shooting range interconnection method, electronic equipment and readable storage medium
CN112291207B (en) Method and device for acquiring front-end equipment catalog
CN112188243B (en) Front-end camera real-time video-on-demand method and device and electronic equipment

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