WO2024067757A1

WO2024067757A1 - Cross-terminal-communication device management method, system and apparatus based on bus, and medium

Info

Publication number: WO2024067757A1
Application number: PCT/CN2023/122389
Authority: WO
Inventors: 黄乐; 黄军君
Original assignee: 蔚来软件科技(上海)有限公司
Priority date: 2022-09-30
Filing date: 2023-09-28
Publication date: 2024-04-04
Also published as: CN115622833A; CN115622833B

Abstract

The present invention relates to the technical field of communications. In particular, provided are a cross-terminal-communication device management method, system and apparatus based on a bus, and a medium, which aim to solve the problem of how to effectively manage a physical device of an external network of a bus so as to realize seamless integration and peer-to-peer communication between an internal network and the external network of the bus. For this purpose, the method in the present invention may comprise: on the basis of a connection drive of a physical device of an external network of a bus, establishing a device connection to the physical device, and acquiring a connection event; managing device information of the physical device on the basis of the connection event, and establishing a data link of the physical device; and establishing an interface connection between the physical device of the external network and a preset bus node according to the device information and the data link, such that the physical device is equivalent to a bus node. Therefore, the problem of a physical layer difference between a bus and an external network is solved, thereby realizing seamless integration and peer-to-peer communication between a physical device of the external network and a bus node.

Description

Device management method, system, device and medium based on bus-based cross-end communication

Technical Field

The present invention relates to the field of communication technology, and specifically provides a device management method, system, apparatus and medium for cross-end communication based on a bus.

Background technique

Generally speaking, vehicle body network communication has a relatively stable networking structure, relatively certain data links, unified communication protocols and static device management configuration. With the accelerated integration of the Internet of Things and vehicle networks, static node devices in the vehicle and different dynamic node devices outside the vehicle need to communicate data at the business level. A better method is needed to achieve cross-end heterogeneous network communication between the closed vehicle bus network and the distributed, open external network.

However, in the heterogeneous network scenario of cross-end communication, there are various physical differences between the platforms of different terminal devices, such as differences in communication hardware, operating system, and communication protocol. These differences will make it impossible for cross-end communication devices to directly communicate on the service bus.

Accordingly, the art needs a new cross-end communication device management solution to solve the above problems.

Summary of the invention

In order to overcome the above defects, the present invention is proposed to provide a solution or at least partially solve the problem of how to effectively manage the physical devices of the external network of the bus to achieve seamless integration and peer-to-peer communication between the internal and external networks of the bus.

In a first aspect, the present invention provides a device management method based on bus cross-end communication, the method comprising:

A connection driver of a physical device of an external network of the bus establishes a device connection with the physical device and obtains a connection event of the device connection;

managing device information of the physical device according to the connection event, and establishing a data link of the physical device;

According to the device information and the data link, an interface connection is established between the physical device and a preset bus node of the bus, so as to realize that the physical device is equivalent to a bus node of the bus.

In a technical solution of the above-mentioned bus-based cross-end communication device management method, the device information includes registration management information and status management information, the registration management information is used to manage the registration information and permission information of the physical device, and the status management information is used to manage the device status of the physical device.

In a technical solution of the above-mentioned device management method based on bus cross-end communication, the registration management information includes device registration information, device service registration information and user identity registration information, and the step of "managing the device information of the physical device according to the connection event" includes:

According to the connection event, respectively obtain device registration information, device service registration information and user identity registration information of the physical device;

Managing the device registration information through a preset device registration unit;

Managing the device service registration information through a preset device service registration unit;

The user identity registration information is managed by a preset user identity registration unit.

In a technical solution of the above-mentioned device management method based on bus cross-end communication, the step of "managing the device registration information through a preset device registration unit" includes:

By means of the device registration unit, converting the device registration information into a device registration list;

Synchronize the device registration list to a preset device database to manage the device registration information; and/or,

The device registration information includes the ID, physical address and device type of the physical device; and/or,

The device service registration information includes the service ID, service interface and service parameters of the physical device; and/or,

The user identity registration information includes the user login account of the physical device, The binding relationship between user permissions and users and physical devices.

In a technical solution of the above-mentioned device management method based on bus cross-end communication, the state management information includes device parameter information, device working state information and device resource information of the physical device, and the step of "managing the device information of the physical device according to the connection event" further includes:

According to the connection event, device parameter information, device working status information and device resource information of the physical device are respectively obtained;

Performing configuration management on the device parameter information through a preset device parameter management unit;

Maintaining the device working status information through a preset device status management unit;

The device resource information is managed by a preset device resource management unit.

In a technical solution of the above-mentioned device management method based on bus cross-end communication, the method further includes:

By means of the bus node, based on the network management event of the bus, the device working status information in the device status management unit is modified; and/or,

The device parameter information of the device parameter management unit is reconfigured by applying a preset device configuration list through the bus node.

In a technical solution of the above-mentioned device management method based on bus cross-end communication, the step of "establishing a data link of the physical device" includes:

According to the connection event, establishing a data channel between the physical device and the bus node;

According to the data channel, acquiring a transmission protocol required for communication of the physical device;

According to the transmission protocol, the PDU of the transmission protocol is processed to achieve the establishment of the data link.

According to the processing result of the PDU, the transmission protocol and the transmission data format between the physical device and the bus node are converted to achieve the transmission of the physical device and the bus node. Cross-end communication between online nodes.

Establishing a mapping relationship between the physical device and the bus node according to the address information of the physical device and the address information of the bus node;

According to the mapping relationship, a service channel between the physical device and the bus node is determined.

In a technical solution of the above-mentioned device management method based on bus-based cross-end communication, "establishing an interface connection between the physical device and a preset bus node of the bus according to the device information and the data link" includes:

establishing an interface connection between the physical device and the bus node according to the device information, the data link and the service channel; and/or,

The address information includes a device ID and/or a device port number; and/or,

The method further comprises:

The mapping relationship is saved in a preset service routing table, which is maintained by a preset service router.

In a second aspect, the present invention provides a device management system based on bus-based cross-end communication, the system comprising:

A device connection event acquisition module, which is configured to be a connection driver of a physical device of an external network based on the bus, establish a device connection with the physical device, and acquire a connection event of the device connection;

a device management information and data link determination module, configured to manage device information of the physical device and establish a data link of the physical device according to the connection event;

An interface connection establishment module is configured to establish an interface connection between the physical device and a preset bus node of the bus according to the device information and the data link, so as to realize that the physical device is equivalent to a bus node of the bus.

In a third aspect, a control device is provided, the control device comprising a processor and a storage device, the storage device being adapted to store a plurality of program codes, the program codes being adapted to be loaded and run by the processor to execute the device management method based on bus cross-end communication described in any one of the technical solutions of the device management method based on bus cross-end communication. Law.

In a fourth aspect, a computer-readable storage medium is provided, which stores a plurality of program codes, wherein the program codes are suitable for being loaded and run by a processor to execute the device management method based on cross-end communication based on bus as described in any one of the technical solutions of the above-mentioned technical solution of the device management method based on cross-end communication based on bus.

The above one or more technical solutions of the present invention have at least one or more of the following beneficial effects:

In the technical solution for implementing the present invention, the present invention can establish a device connection of the physical device based on the connection drive of the physical device of the external network of the bus, obtain the connection event, manage the device information of the physical device based on the connection event, and establish the data link of the physical device, and establish the interface connection between the physical device of the external network and the preset bus node according to the device information and the data link, so that the physical device is equivalent to the bus node. Through the above configuration, the present invention can effectively manage the physical devices of the external network that need to be connected to the bus, and make the physical devices of the external network equivalent to the bus node, which solves the problem of physical layer differences between the bus and the external network, shields the physical layer differences between the physical devices of different external networks and the bus, and realizes seamless integration and peer-to-peer communication between the physical devices of the external network and the bus nodes, making the cross-end communication process based on the bus more open and flexible.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosure of the present invention will become more easily understood with reference to the accompanying drawings. It is easy for those skilled in the art to understand that these drawings are only for illustrative purposes and are not intended to limit the scope of protection of the present invention. Among them:

FIG1 is a schematic flow chart of main steps of a device management method based on bus-based cross-end communication according to an embodiment of the present invention;

FIG2 is a schematic diagram of an architecture of bus-based cross-end communication according to an implementation of an embodiment of the present invention;

3 is a schematic diagram of the architecture of a device management method based on bus-based cross-end communication according to an implementation of an embodiment of the present invention;

FIG. 4 is a main structural block diagram of a device management system based on bus-based cross-end communication according to an embodiment of the present invention.

Detailed ways

Some embodiments of the present invention are described below with reference to the accompanying drawings. It should be understood by those skilled in the art that these embodiments are only used to explain the technical principles of the present invention and are not intended to limit the protection scope of the present invention.

In the description of the present invention, "module" and "processor" may include hardware, software or a combination of the two. A module may include hardware circuits, various suitable sensors, communication ports, and memories, and may also include software parts, such as program codes, or a combination of software and hardware. The processor may be a central processing unit, a microprocessor, a digital signal processor, or any other suitable processor. The processor has data and/or signal processing functions. The processor may be implemented in software, hardware, or a combination of the two. Non-temporary computer-readable storage media include any suitable medium that can store program codes, such as a magnetic disk, a hard disk, an optical disk, a flash memory, a read-only memory, a random access memory, and the like. The term "A and/or B" means all possible combinations of A and B, such as only A, only B, or A and B. The term "at least one A or B" or "at least one of A and B" has a similar meaning to "A and/or B", and may include only A, only B, or A and B. The singular terms "one" and "the" may also include plural forms.

Referring to FIG. 1 , FIG. 1 is a schematic flow chart of the main steps of a device management method based on bus cross-end communication according to an embodiment of the present invention. As shown in FIG. 1 , the device management method based on bus cross-end communication in the embodiment of the present invention mainly includes the following steps S101 to S103.

Step S101: A connection driver of a physical device of an external network based on a bus establishes a device connection with the physical device and obtains a connection event of the device connection.

In this embodiment, a physical device connection can be established based on a connection driver of a physical device in an external network, and a connection event can be obtained, wherein the connection event can include a connection process, a connection state, and a connection result of the device connection.

In one implementation, the bus may be a vehicle body bus, such as an Ethernet bus, a CAN bus, etc. The external network may be various IoT networks, and the physical device may be a wifi device, a USB device, a Bluetooth device, etc.

In one implementation, the process of establishing a device connection with a physical device may include: discovering the physical device; connecting and shaking hands with the physical device to obtain information such as services, transmission protocols, and resources of the physical device; authenticating the physical device; generating a link with the physical device; road.

In one implementation, please refer to FIG. 2, which is a schematic diagram of the architecture of bus-based cross-end communication according to an implementation of an embodiment of the present invention. As shown in FIG. 2, the bus can be a vehicle body bus, and the vehicle body bus can be Ethernet, CAN (Controller Area Network) network. The external network can be a WLAN (Wireless Local Area Network) ad hoc network, a Bluetooth ad hoc network, and the physical device can be a Wifi Device, a BT Device, and the like. In the preset cross-end device virtualization management module, connection drivers for various physical devices can be set, such as USB1~n, Wifi1~n, BLE (Bluetooth Low Energy) 1~n, 5G/LTE (Long Term Evolution), V2X (vehicle to everything), NFC (Near Field Communication), and Bluetooth plug-in. These connection drivers can provide physical devices of external networks with access to the cross-end device virtualization management module, so that the cross-end device virtualization management module can simultaneously maintain and manage multiple heterogeneous external networks. Among them, the plug-ins in Figure 2 can all realize "hot plugging", that is, they can realize the effective expansion of device connections.

Step S102: according to the connection event, the device information of the physical device is managed, and a data link of the physical device is established.

In this embodiment, the device information of the physical device can be managed based on the connection event of the physical device of the external network, and the data link of the physical device can be established based on the connection event. The data link refers to the medium for sending and receiving data between the physical device and the bus. The control plane management of the physical device can be achieved based on the management of the device information of the physical device, and the data plane management of the physical device can be achieved based on the data link.

In one implementation, the device information may include registration management information and status management information. The registration management information may be used to manage registration information and permission information of the physical device, and the status management information may be used to manage the device status of the physical device.

In one implementation, the registration management information may include device registration information, device service registration information, and user identity registration information.

In one implementation, the status management information may include device parameter information, device working status information, and device resource information of the physical device.

Step S103: According to the device information and the data link, an interface connection is established between the physical device and the bus node of the preset bus, so as to realize the equivalent of the physical device to the bus. Bus node.

In this embodiment, an interface connection between a physical device and a preset bus node can be established according to the device information and the data link, so as to achieve the connection of the physical device to the bus as a bus node.

Based on the above steps S101-S103, the embodiment of the present invention can establish a device connection of the physical device based on the connection drive of the physical device of the external network of the bus, and obtain the connection event, manage the device information of the physical device based on the connection event, and establish the data link of the physical device, and establish the interface connection between the physical device of the external network and the preset bus node according to the device information and the data link, so that the physical device is equivalent to the bus node. Through the above configuration method, the embodiment of the present invention can effectively manage the physical devices of the external network that need to be connected to the bus, and make the physical devices of the external network equivalent to the bus node, which solves the problem of physical layer differences between the bus and the external network, shields the physical layer differences between the physical devices of different external networks and the bus, and realizes seamless integration and peer-to-peer communication between the physical devices of the external network and the bus nodes, making the cross-end communication process based on the bus more open and flexible.

Step S102 and step S103 are further described below.

In one implementation of the embodiment of the present invention, step S102 may further include the following steps S10201 to S10204:

Step S10201: According to the connection event, the device registration information, device service registration information and user identity registration information of the physical device are respectively obtained.

Step S10202: managing device registration information through a preset device registration unit.

Step S10203: managing the device service registration information through a preset device service registration unit.

Step S10204: managing the user identity registration information through a preset user identity registration unit.

In this embodiment, please refer to FIG. 3, which is a schematic diagram of the architecture of a device management method based on bus cross-end communication according to an embodiment of the present invention. As shown in FIG. 3, the device registration information, device service registration information and user identity registration information of the physical device can be obtained according to the connection event of the physical device, and the device registration information, device service registration information and user identity registration information can be respectively obtained through the preset device registration unit, device service registration unit and user identity registration unit. The device service registration information and user identity registration information are managed. The device registration information may include the ID, physical address (MAC Address) and device type of the physical device. The device service registration information may include the service ID, service interface and service parameters of the physical device. The user identity registration information may include the user login account of the physical device, user permissions and the binding relationship between the user and the physical device.

In one implementation, step S10202 may further include the following steps S102021 and S102022:

Step S102021: The device registration information is converted into a device registration list through the device registration unit.

Step S102022: Synchronize the device registration list to the preset device database to manage the device registration information.

In this embodiment, referring to FIG. 3, the device registration unit can convert the device registration information into a device registration list, and synchronize the device registration list to the device database, which stores and maintains the device registration list. In this way, when connecting a device, the device registration list in the device database can be directly indexed, that is, the device registration information can be obtained without rewriting the device registration information each time the device is connected. At the same time, the device registration list has a unified data structure, which makes the indexing process faster and more convenient, and can also provide relevant device information for subsequent physical device device diagnosis, communication performance optimization, and resource management processes.

In one implementation of the embodiment of the present invention, step S102 may include the following steps S10205 to S10208 in addition to the above steps S10201 to S10204:

Step S10205: According to the connection event, device parameter information, device working status information and device resource information of the physical device are respectively obtained.

Step S10206: Perform configuration management on the device parameter information through a preset device parameter management unit.

Step S10207: Maintain the device working status information through the preset device status management unit.

Step S10208: managing the device resource information through a preset device resource management unit.

In this embodiment, referring to FIG. 3 , as shown in FIG. 3 , the The device parameter information, device working status information and device resource information of the physical device are obtained through the connection event, and the device parameter information, device working status information and device resource information are managed by the device parameter management unit, the device status management unit and the device resource management unit respectively. Among them, the device working status information may include the power mode and communication working mode of the device, and the management of the device working status information may be a state machine for maintaining the power mode and communication working mode of the device. The device parameter information may include parameters such as the broadcast frequency of the physical device, the duration of the connection timeout, the interval of the sleep timer wake-up, etc. The device resource information may include the channel resources, protocol resources, software resources and hardware available resources of the physical device.

In one implementation, the device operating status information in the device status management unit can be modified through the bus node based on the network management events of the bus.

In this embodiment, referring to FIG. 3 , the network management event of the bus can change the working state and communication working mode of the physical device through the device management interface (bus node) and the device state management unit in FIG. 3 to achieve synchronization of the working state between the physical device and other bus nodes of the bus. The network management event refers to the communication or wake-up coordination event of the bus.

In one implementation, the device parameter information of the device parameter unit may be reconfigured by applying a preset device configuration list through the bus node.

In this embodiment, referring to FIG. 3 , the device parameter management unit provides configuration management of device parameter information, and the physical device can change its working behavior according to the configured device parameter information. The changed device parameter information is sent to the device management interface (bus node) through the device configuration list in FIG. 3 , and then further reaches the device parameter management unit to implement the configuration of the device parameters.

In one implementation of the embodiment of the present invention, step S102 may further include the following steps S10209 to S10211:

Step S10209: Establish a data channel between the physical device and the bus node according to the connection event.

In this implementation, a data channel between a physical device and a bus node may be established based on a connection event of a device connection.

In one embodiment, as shown in FIG3 , the process of establishing a data channel between a physical device and a bus node can be implemented by a communication link management unit in FIG3 . The communication link management unit manages the establishment of the data channel and manages the data link layer, the network layer, and the transmission layer. The working status and events of the transport layer, including broadcast, scanning, connection handshake, authentication, binding, disconnection and exception.

Step S10210: According to the data channel, obtain the transmission protocol required for communication of the physical device.

In this implementation, the transmission protocol required for the physical devices to communicate can be acquired based on the data channel.

In one implementation, as shown in FIG3 , the step of obtaining the transmission protocol can be implemented by a communication protocol stack unit. The communication protocol stack unit provides transmission protocols required by different physical devices, such as HTTP (Hyper Text Transfer Protocol), FTP (File Transfer Protocol), RTP (Real-time Transport Protocol), GATT (Generic Attribute Profile) and other protocol stacks. For bus-based cross-end communication, the communication between the bus network and the external network may use different transmission protocols between different networks, or may use the same transmission protocol.

Step S10211: According to the transmission protocol, process the PDU (Protocol Data Unit) of the transmission protocol to establish a data link.

In this implementation, the PDU content of the transmission protocol may be processed according to the transmission protocol, such as serialization, encoding and decoding, compression, decompression, etc., to achieve the establishment of a data link.

In one implementation, the PDU of the transmission protocol may be processed by the data processing unit in FIG. 3 .

In one implementation, the transmission protocol and transmission data format between the physical device and the bus node can be converted according to the processing result of the PDU to achieve cross-end communication between the physical device and the bus node. That is, through the data manager and communication protocol converter in FIG3, the conversion and adaptation of the transmission protocol and transmission data format between the bus and the external network are achieved, thereby achieving bus communication fusion based on service sessions of heterogeneous networks in cross-end communication.

In the first implementation of the embodiment of the present invention, in addition to the above steps S101 and S103, the present invention may also include the following steps S104 and S105:

Step S104: Establishing a mapping relationship between the physical device and the bus node according to the address information of the physical device and the address information of the bus node

Step S105: Determine the relationship between the physical device and the bus node according to the mapping relationship service channel.

In this embodiment, a mapping relationship between the physical device and the bus node can be established according to the address information of the physical device and the bus node, and a service channel between the physical device and the bus node can be established based on the mapping relationship. The address information can include a device ID and a device port number. The service channel refers to a channel through which service information can be transmitted, which uses the bus node as a transmission medium.

In one implementation, the mapping relationship may be saved in a preset service routing table, and the service routing table is maintained by a preset service router.

In this implementation, the service router in FIG. 3 may maintain a service routing table storing mapping relationships between physical devices and bus nodes.

In one implementation, step S103 may be further configured as follows:

According to the device information, data link and service channel, an interface connection between the physical device and the bus node is established.

Generally speaking, in cross-end communication, service communication between different terminals (physical devices) includes service interface calls between service consumers and service providers through service primitives, service discovery and registration, service proxy and other sessions. Service sessions can be forwarded through service routers. The message format of service sessions on the service bus is shown in Table 1 below:

Table 1 Message format of service session

The service router addresses and forwards relevant messages to the destination device based on the destination device ID/source device ID/destination port number/source port number and other information in the message. Specifically, the service router maintains a service routing table. In a unicast scenario, the destination device and the source device can be mapped to a unique bus node in the heterogeneous network topology of cross-end communication based on the relevant ID number, and the service router forwards the relevant session message to the destination device or the relevant bus node based on the service routing table. For multicast and groupcast scenarios, the destination device ID can be a special defined value mapped to the physical devices corresponding to multiple bus nodes. A unique service channel can be determined based on the destination port number and the source port number. There can be multiple service channels between two service nodes.

In one implementation, referring to FIG. 3, as shown in FIG. 3, a device connection between a physical device control plane and a data plane can be established through a device connection driver plug-in (connection driver) in FIG. 3. A device connection management module in FIG. 3 can be used to establish a connection with an external network. The device security management module provides the security functions required for authentication, encryption and decryption during the device connection process, such as random number generator, secure storage, security algorithm engine, digital certificate management, etc.

It should be pointed out that although the various steps in the above embodiments are described in a specific order, those skilled in the art can understand that in order to achieve the effects of the present invention, different steps do not have to be performed in such an order. They can be performed simultaneously (in parallel) or in other orders. These changes are within the scope of protection of the present invention.

Furthermore, the present invention also provides a device management system based on bus-based cross-end communication.

Refer to Figure 4, which is a main structural block diagram of a device management system based on bus-based cross-end communication according to an embodiment of the present invention. As shown in Figure 4, the device management system based on bus-based cross-end communication in the embodiment of the present invention may include a device connection event acquisition module, a device management information and data link determination module, and an interface connection establishment module. In this embodiment, the device connection event acquisition module can be configured as a connection driver for a physical device of an external network based on the bus, establishes a device connection with the physical device, and obtains a connection event of the device connection. The device management information and data link determination module can be configured to manage the device information of the physical device according to the connection event and establish a data link for the physical device. The interface connection establishment module can be configured to establish an interface connection between the physical device and a bus node of a preset bus according to the device information and the data link, so as to realize the equivalence of the physical device to the bus node of the bus.

The above-mentioned bus-based cross-end communication device management system is used to execute the bus-based cross-end communication device management method embodiment shown in Figure 1. The technical principles, technical problems solved and technical effects produced by the two are similar. Technical personnel in this technical field can clearly understand that for the convenience and conciseness of description, the specific working process and related instructions of the bus-based cross-end communication device management system can refer to the contents described in the embodiment of the bus-based cross-end communication device management method, which will not be repeated here.

It is understood by those skilled in the art that the present invention can implement all or part of the processes in the method of the above embodiment by instructing the relevant hardware through a computer program, and the computer program can be stored in a computer-readable storage medium. When the computer program is executed by a processor, the steps of the above method embodiments can be implemented. The computer program includes computer program code, which can be source code. The computer-readable storage medium may include any entity or device, medium, USB flash drive, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory, random access memory, electric carrier signal, telecommunication signal, and software distribution medium that can carry the computer program code. It should be noted that the content contained in the computer-readable storage medium may be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction. For example, in some jurisdictions, according to legislation and patent practice, computer-readable storage media do not include electric carrier signals and telecommunication signals.

Furthermore, the present invention also provides a control device. In an embodiment of a control device according to the present invention, the control device includes a processor and a storage device, the storage device can be configured to store a program for executing a device management method based on bus cross-end communication of the above method embodiment, and the processor can be configured to execute the program in the storage device, which includes but is not limited to executing a program for a device management method based on bus cross-end communication of the above method embodiment. For ease of explanation, only the parts related to the embodiment of the present invention are shown. For specific technical details not disclosed, please refer to the method part of the embodiment of the present invention. The control device can be a control device device formed by various electronic devices.

Furthermore, the present invention also provides a computer-readable storage medium. In a computer-readable storage medium embodiment according to the present invention, the computer-readable storage medium can be configured to store a program for executing the device management method based on bus-based cross-end communication of the above-mentioned method embodiment, and the program can be loaded and run by the processor to implement the above-mentioned device management method based on bus-based cross-end communication. For ease of explanation, only the parts related to the embodiment of the present invention are shown. For specific technical details not disclosed, please refer to the method part of the embodiment of the present invention. The computer-readable storage medium can be a storage device formed by various electronic devices. Optionally, the computer-readable storage medium in the embodiment of the present invention is a non-temporary computer-readable storage medium.

Further, it should be understood that since the setting of each module is only for illustrating the functional units of the device of the present invention, the physical devices corresponding to these modules may be the processor itself, or a part of the software in the processor, a part of the hardware, or a part of the combination of software and hardware. Therefore, the number of each module in the figure is only schematic.

Those skilled in the art will appreciate that the modules in the device can be adaptively split or merged. Such splitting or merging of specific modules will not cause the technical solution to deviate from the principle of the present invention, and therefore, the technical solutions after splitting or merging will fall within the protection scope of the present invention.

So far, the technical solutions of the present invention have been described in conjunction with the preferred embodiments shown in the accompanying drawings. However, it is easy for those skilled in the art to understand that the protection scope of the present invention is obviously not limited to these specific embodiments. Without departing from the principle of the present invention, those skilled in the art can make equivalent changes or substitutions to the relevant technical features, and the technical solutions after these changes or substitutions will fall within the protection scope of the present invention.

Claims

A device management method based on bus cross-end communication, characterized in that the method comprises:

A connection driver of a physical device of an external network of the bus establishes a device connection with the physical device and obtains a connection event of the device connection;

According to the connection event, managing device information of the physical device and establishing a data link of the physical device;

According to the device information and the data link, an interface connection is established between the physical device and a preset bus node of the bus, so as to realize that the physical device is equivalent to a bus node of the bus.
According to the device management method based on bus cross-end communication according to claim 1, it is characterized in that the device information includes registration management information and status management information, the registration management information is used to manage the registration information and permission information of the physical device, and the status management information is used to manage the device status of the physical device.
According to claim 2, the device management method based on bus cross-end communication is characterized in that the registration management information includes device registration information, device service registration information and user identity registration information, and the step of "managing the device information of the physical device according to the connection event" includes:

According to the connection event, respectively obtain device registration information, device service registration information and user identity registration information of the physical device;

Managing the device registration information through a preset device registration unit;

Managing the device service registration information through a preset device service registration unit;

The user identity registration information is managed by a preset user identity registration unit.
The device management method based on bus cross-end communication according to claim 3 is characterized in that the step of "managing the device registration information through a preset device registration unit" comprises:

By means of the device registration unit, converting the device registration information into a device registration list;

Synchronize the device registration list to a preset device database to manage the device registration information; and/or,

The device registration information includes the ID, physical address and device type of the physical device; and/or,

The device service registration information includes the service ID, service interface and service parameters of the physical device; and/or,

The user identity registration information includes the user login account of the physical device, user permissions and the binding relationship between the user and the physical device.
According to claim 3, the device management method based on bus cross-end communication is characterized in that the status management information includes device parameter information, device working status information and device resource information of the physical device, and the step of "managing the device information of the physical device according to the connection event" further includes:

According to the connection event, device parameter information, device working status information and device resource information of the physical device are respectively obtained;

Performing configuration management on the device parameter information through a preset device parameter management unit;

Maintaining the device working status information through a preset device status management unit;

The device resource information is managed by a preset device resource management unit.
The device management method based on bus cross-end communication according to claim 5, characterized in that the method further comprises:

By means of the bus node, based on the network management event of the bus, the device working status information in the device status management unit is modified; and/or,

The device parameter information of the device parameter management unit is reconfigured by applying a preset device configuration list through the bus node.
The device management method based on bus cross-end communication according to claim 1 is characterized in that the step of "establishing a data link of the physical device" comprises:

According to the connection event, establishing a data channel between the physical device and the bus node;

According to the data channel, the transmission protocol required for the communication of the physical device is obtained. Discussion;

According to the transmission protocol, the PDU of the transmission protocol is processed to achieve the establishment of the data link.
The device management method based on bus cross-end communication according to claim 7, characterized in that the method further comprises:

According to the processing result of the PDU, the transmission protocol and the transmission data format between the physical device and the bus node are converted to achieve cross-end communication between the physical device and the bus node.
The device management method based on bus cross-end communication according to claim 1, characterized in that the method further comprises:

Establishing a mapping relationship between the physical device and the bus node according to the address information of the physical device and the address information of the bus node;

According to the mapping relationship, a service channel between the physical device and the bus node is determined.
The device management method based on bus-based cross-end communication according to claim 9 is characterized in that "establishing an interface connection between the physical device and a preset bus node of the bus according to the device information and the data link" comprises:

establishing an interface connection between the physical device and the bus node according to the device information, the data link and the service channel; and/or,

The address information includes a device ID and/or a device port number; and/or,

The method further comprises:

The mapping relationship is saved in a preset service routing table, and the service routing table is maintained by a preset service router.
A device management system based on bus-based cross-end communication, characterized in that the system comprises:

The device connection event acquisition module is configured to be a connection driver of a physical device of an external network based on the bus, establish a device connection with the physical device, and acquire the device Connection events for connections;

a device management information and data link determination module, configured to manage device information of the physical device and establish a data link of the physical device according to the connection event;

An interface connection establishing module is configured to establish an interface connection between the physical device and a preset bus node of the bus according to the device information and the data link, so as to realize the equivalence of the physical device to the bus node of the bus.
A control device comprises a processor and a storage device, wherein the storage device is suitable for storing multiple program codes, and is characterized in that the program codes are suitable for being loaded and run by the processor to execute the device management method based on bus cross-end communication as described in any one of claims 1 to 10.
A computer-readable storage medium storing a plurality of program codes, characterized in that the program codes are suitable for being loaded and run by a processor to execute the device management method based on bus cross-end communication as described in any one of claims 1 to 10.