WO2025241347A1 - Bus communication method and apparatus, and computer device and readable storage medium - Google Patents

Abstract

The present application relates to the technical field of communications, and in particular to a bus communication method and apparatus, and a computer device and a readable storage medium. The method comprises: on the basis of an MQTT protocol, acquiring, by means of a first external interface, service data published by a service provider side; transmitting the service data to a gateway plug-in by means of an internal interface; by means of the internal interface, acquiring plug-in data transmitted by the gateway plug-in, wherein the plug-in data is obtained on the basis of processing of the service data; and on the basis of the MQTT protocol, transmitting the plug-in data to a service platform by means of a second external interface.

Description

Bus communication methods, devices, computer equipment, and readable storage media

Related applications

This application claims priority to Chinese patent application filed on May 23, 2024, with application number 202410648130X, entitled "Bus Communication Method, Apparatus, Computer Equipment and Readable Storage Medium", the entire contents of which are incorporated herein by reference.

Technical Field

This application relates to the field of communication technology, and in particular to a bus communication method, apparatus, computer equipment, and readable storage medium.

Background Technology

A bus messaging system is a communication mechanism used to pass messages and data in distributed systems or microservice architectures.

Existing bus messaging systems, especially in Linux environments, widely adopt the DBUS (Desktop Bus) framework as the core mechanism for inter-process communication (IPC). DBUS is a message bus system for inter-application communication and an important mechanism for IPC. Provided by the freedesktop.org project, it is widely used in Linux desktop environments to implement communication between processes and between processes and the kernel. DBUS's main functions include providing a low-latency, low-overhead, and highly available communication mechanism, supporting service discovery, message routing, and selective message reception through matchers. Furthermore, DBUS has its own protocol, designed based on binary data, ensuring efficient information transmission.

However, DBUS message bodies may contain complex data structures and parameters, which makes message parsing and processing relatively complicated, and makes it impossible to guarantee the quality of data transmission.

Summary of the Invention

Therefore, it is necessary to provide a bus communication method, apparatus, computer device, and readable storage medium to address the aforementioned technical problems.

In a first aspect, this application provides a bus communication method applied to a bus server. The bus server includes a first external interface for connecting to a service provider, a second external interface for connecting to a service platform, and an internal interface for connecting to a gateway plugin. The method includes:

Based on the MQTT protocol, business data published by the service provider is obtained through the first external interface;

Transmit business data to the gateway plugin through the internal interface;

The plugin data transmitted by the gateway plugin is obtained through an internal interface; the plugin data is obtained based on business data processing; and

Based on the MQTT protocol, the plugin data is transmitted to the business platform through a second external interface.

In one embodiment, the number of gateway plugins connected to the internal interface is at least two, and the number of service providers connected to the first external interface is at least two; and

Through the internal interface, business data is transmitted to the gateway plugin, including:

When a business query request initiated by any gateway plugin based on the MQTT protocol is received, the corresponding business data for the business query request is retrieved from the business data provided by each business provider; and

The service data corresponding to the service query request is transmitted to the gateway plugin through the internal interface.

In one embodiment, the method further includes:

Through the internal interface, obtain the first MQTT request initiated by any gateway plugin based on the MQTT protocol; and

When the first MQTT request contains business identification information, the first MQTT request will be used as the business query request corresponding to the gateway plugin.

In one embodiment, the service identification information includes the identifier of the target device corresponding to the service provider and the request. Type and related parameter information.

In one embodiment, the internal interface connects to at least two gateway plugins, and the service platform deploys at least two network interface card (NIC) devices; and

Based on the MQTT protocol, plugin data is transmitted to the business platform through a second external interface, including:

When a plugin query request initiated by any network interface card (NIC) device in the business platform based on the MQTT protocol is received, the plugin data corresponding to the plugin query request is retrieved from the plugin data provided by each gateway plugin; and

Based on the MQTT protocol, the plugin data corresponding to the plugin query request is transmitted to the network card device through a second external interface.

In one embodiment, the method further includes:

Through the internal interface, obtain the second MQTT request initiated by any network interface device based on the MQTT protocol; and

When the second MQTT request contains plugin identification information, the second MQTT request will be used as a plugin query request for the network interface device.

In one embodiment, based on the MQTT protocol, the plugin data corresponding to the plugin query request is transmitted to the network interface device via a second external interface, including:

Add the routing address corresponding to the network interface device to the plugin data corresponding to the plugin query request to obtain the target plugin data; and

Based on the MQTT protocol, the target plug-in data is transmitted to the network card device through a second external interface.

In one embodiment, the second external interface includes a network connection or communication port that supports the MQTT protocol.

In one embodiment, the routing address includes the physical address of the network interface card (NIC) device.

In one embodiment, the routing address also includes the network interface card device's device account data.

In one embodiment, the MQTT protocol uses a publish/subscribe model.

Secondly, this application also provides a bus communication device applied to a bus server. The bus server includes a first external interface for connecting to a service provider, a second external interface for connecting to a service platform, and an internal interface for connecting to a gateway plugin. The device includes:

The acquisition module, used for the MQTT protocol, acquires business data published by the business provider through the first external interface;

The first internal transmission module is used to transmit business data to the gateway plugin through an internal interface;

The second internal transmission module is used to obtain plugin data transmitted by the gateway plugin through an internal interface; wherein, the plugin data is obtained based on business data processing; and

The sending module is used to transmit plugin data to the business platform via a second external interface based on the MQTT protocol.

Thirdly, this application also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

Based on the MQTT protocol, business data published by the service provider is obtained through the first external interface;

Transmit business data to the gateway plugin through the internal interface;

The plugin data transmitted by the gateway plugin is obtained through an internal interface; the plugin data is obtained based on business data processing; and

Based on the MQTT protocol, the plugin data is transmitted to the business platform through a second external interface.

Fourthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, performs the following steps:

Based on the MQTT protocol, business data published by the service provider is obtained through the first external interface;

Transmit business data to the gateway plugin through the internal interface;

The plugin data transmitted by the gateway plugin is obtained through an internal interface; the plugin data is obtained based on business data processing; and

Based on the MQTT protocol, the plugin data is transmitted to the business platform through a second external interface.

Fifthly, this application also provides a computer program product, including a computer program that, when executed by a processor, performs the following steps:

Based on the MQTT protocol, business data published by the service provider is obtained through the first external interface;

Transmit business data to the gateway plugin through the internal interface;

The plugin data transmitted by the gateway plugin is obtained through an internal interface; the plugin data is obtained based on business data processing; and

Based on the MQTT protocol, the plugin data is transmitted to the business platform through a second external interface.

Details of one or more embodiments of this application are set forth in the following drawings and description. Other features, objects, and advantages of this application will become apparent from the specification, drawings, and claims.

Attached Figure Description

To more clearly illustrate the technical solutions in the embodiments of this application or the conventional technology, the drawings used in the description of the embodiments or the conventional technology will be briefly introduced below. Obviously, the drawings described below are only embodiments of this application. For those skilled in the art, other drawings can be obtained based on the disclosed drawings without creative effort.

Figure 1 is an application environment diagram of the bus communication method in one embodiment of this application;

Figure 2 is a flowchart illustrating a bus communication method in one embodiment of this application;

Figure 3 is a flowchart illustrating the steps of transmitting service data corresponding to a service query request to the gateway plugin in one embodiment of this application;

Figure 4 is a flowchart illustrating the step of transmitting the plug-in data corresponding to the plug-in query request to the network card device through a second external interface in one embodiment of this application.

Figure 5 is a flowchart illustrating the step of transmitting the plug-in data corresponding to the plug-in query request to the network card device through a second external interface in another embodiment of this application.

Figure 6 is a structural block diagram of a bus communication device in one embodiment of this application;

Figure 7 is an internal structural diagram of a computer device in one embodiment of this application.

Detailed Implementation

The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

The bus communication method provided in this application embodiment can be applied to the application environment shown in Figure 1. The bus server includes a first external interface (A interface) for connecting to the service provider, a second external interface (B interface) for connecting to the service platform, and an internal interface for connecting to gateway plugins. Each gateway plugin may include a container management plugin, a control plugin, an FTTR (Fiber to the Room) control plugin, and a local web interface plugin.

In an exemplary embodiment, as shown in FIG2, a bus communication method is provided. Taking the application of this method to the bus server in FIG1 as an example, the method includes the following steps 202 to 206. Wherein:

Step 201: Based on the MQTT (Message Queuing Telemetry Transport) protocol, obtain the business data published by the service provider through the first external interface.

The service provider can be an MQTT client or a vendor. The MQTT client (vendor) is the starting point for the data processing and transmission flow; it is responsible for publishing the service data generated by the device to the MQTT network for other systems to subscribe to and use. The service data generated by the device can include device status, sensor readings, and operational results. The vendor needs to ensure that the published data conforms to certain formats and standards so that other systems can correctly parse and use this data.

Specifically, the Message Queuing Telemetry Transport (MQTT) protocol uses a publish/subscribe model, meaning that clients can subscribe to specific topics and receive notifications when new messages are published on those topics. This model decouples message publishers and subscribers, so they do not need to be directly connected to each other or aware of each other's existence.

As is understandable, a topic in the MQTT protocol is a string used to identify a message transmission channel. There is no strictly defined type for MQTT topics because they are string identifiers used to define a message transmission channel. Topics can be customized according to the application scenario to meet specific message delivery needs. For example, a topic... Questions can typically include the following types or naming conventions:

1) command: This type of topic is typically used to send control commands or instructions; 2) reply or response: This type of topic can be used when it is necessary to receive a reply or response after a command is executed; 3) report or status: This type of topic is often used for publishing device or system status reports; 4) config or settings: This type of topic may be used to send or receive configuration information.

Step 202: Transmit business data to the gateway plugin through the internal interface.

A gateway plugin is a software component installed on a gateway that has specific functions for processing, transforming, or monitoring data streams passing through the network gateway. For example, a gateway plugin can process and transform data passing through the gateway. During data transmission, the plugin can perform operations such as encryption, compression, and format conversion to meet the data exchange needs between different systems.

Specifically, the internal interface is defined within the bus server and is used to transfer data between the server and the gateway plugin. The gateway plugin is typically integrated into or deployed on the bus server. When the gateway plugin starts, it establishes a connection with the bus server through the internal interface. Similarly, the gateway plugin can also send data or responses to the bus server through this interface.

In this embodiment, the bus server deploys the gateway plugins using LXC (Linux Containers). LXC provides a lightweight virtualization solution that allows multiple containers to run on a single physical host. This makes the deployment of gateway plugins faster and more flexible. By using LXC, containers containing gateway plugins can be easily created and managed, enabling rapid plugin deployment.

Step 203: Obtain the plugin data transmitted by the gateway plugin through the internal interface.

The plugin data is obtained based on business data processing.

Specifically, these data are transmitted to the gateway plugin via an internal interface. Upon receiving this data, the gateway plugin processes it according to its own functionalities. After processing, the gateway plugin sends the processed data (i.e., plugin data) back to the bus server via the internal interface.

Step 204: Based on the MQTT protocol, transmit the plugin data to the business platform through the second external interface.

Understandably, the plugin data has been properly formatted and encapsulated according to the requirements of the MQTT protocol. This typically involves converting the data into MQTT messages and specifying appropriate topics so that the business platform can correctly subscribe to and receive these messages.

The second external interface serves as the connection point between the bus server and the business platform. Once the plugin data is encapsulated into MQTT messages and published through the second external interface, the business platform can receive this data by subscribing to the corresponding topics.

In the above-mentioned bus communication method, this application uses the MQTT protocol to ensure the consistency and standardization of communication content between the service provider, gateway plugin and service platform, so that different service providers and gateway plugins can be uniformly connected, which improves the bus communication quality and further reduces the bus integration and development costs.

In an exemplary embodiment, as shown in FIG3, the number of gateway plugins connected to the internal interface is at least two, and the number of service providers connected to the first external interface is at least two; step 202 includes steps 301 and 302:

Step 301: When a business query request initiated by any gateway plugin based on the MQTT protocol is obtained, the business data corresponding to the business query request is obtained from the business data provided by each business provider.

In this embodiment, any gateway plugin can publish MQTT requests through the Topic:command topic; subscribe to MQTT replies through the Topic:reply topic; and subscribe to MQTT reports through the Topic:report topic.

In this context, "Topic: command" refers to the gateway plugin publishing MQTT requests to the command topic via the MQTT protocol when it needs to send control commands. These commands may include requests for device configuration, status queries, firmware updates, etc. Messages published to the command topic typically contain the identifier of the target device corresponding to the service provider, the request type, and relevant parameter information.

In this context, subscribing to MQTT replies via the Topic:reply means that the gateway plugin subscribes to a reply topic to receive responses from other system components or devices to previously sent requests. Once other components or devices have processed their requests, they publish the results to this topic. By listening to this topic, the gateway plugin can obtain real-time updates on request processing. As a result, corresponding follow-up operations or decisions are made.

In this context, subscribing to MQTT reports via the Topic:report means that the gateway plugin also subscribes to the report Topic to receive status updates, event notifications, or periodically reported data from other components or devices. This data may include device operating status, sensor readings, error logs, etc. By subscribing to this Topic, the gateway plugin can monitor the overall system operating status in real time and promptly identify and address potential problems.

In this embodiment, the first MQTT request initiated by any gateway plugin based on the MQTT protocol is obtained through an internal interface; when the first MQTT request contains service identification information, the first MQTT request is used as the service query request corresponding to the gateway plugin.

The business identification information refers to the message published to the command topic, which typically includes the identifier of the target device corresponding to the business provider, the request type, and related parameter information.

Step 302: Transmit the business data corresponding to the business query request to the gateway plugin through the internal interface.

Understandably, after obtaining the requested business data, the system transmits this data back to the gateway plugin that initiated the query request via an internal interface. Since the internal interface connects to at least two gateway plugins, the system needs to ensure that the data is accurately sent to the correct gateway plugin.

Specifically, a distribution module is set up within the bus server. This module subscribes to the Local/command Topic to listen for commands from within the system. When a message is received from Local/command, the distribution module parses the data body of the message, particularly the method field, which contains the name of the target plugin. Based on the parsed plugin name, the distribution module forwards the data packet to the corresponding plugin's dedicated Topic. This ensures that each plugin only receives data relevant to it, achieving data isolation between plugins.

In this embodiment, the MQTT broker acts as a message middleware, responsible for receiving and distributing messages. The gateway plugin and other clients communicate and collaborate by publishing and subscribing to different topics. This publish/subscribe pattern allows for loosely coupled communication because senders and receivers do not need to be directly connected or aware of each other's existence; they only need to focus on the same topics.

In an exemplary embodiment, the number of gateway plugins connected to the internal interface is at least two, and at least two network interface card (NIC) devices are deployed in the service platform; as shown in Figure 4, step 203 includes steps 401 and 402:

Step 401: When a plugin query request initiated by any network interface device in the business platform based on the MQTT protocol is obtained, the plugin data corresponding to the plugin query request is obtained from the plugin data provided by each gateway plugin.

Understandably, in a typical network architecture, a service platform usually refers to a system or platform that provides specific business functions or services, while the network interface card (NIC) is the hardware component responsible for network communication within that system; the service platform provides services to the external network through the NIC. For example, a web server platform uses a NIC to receive client requests and send responses through the NIC.

In this embodiment, the network interface card (NIC) device acts as an MQTT client, capable of connecting to the MQTT Broker and participating in the MQTT publish/subscribe model. This enables the NIC device to proactively initiate requests and receive responses, allowing for asynchronous communication with other parts of the business platform.

Specifically, any network interface device can publish MQTT requests through the Topic:command topic; subscribe to MQTT replies through the Topic:reply topic; and subscribe to MQTT reports through the Topic:report topic.

When a network interface card (NIC) device needs to query information about a specific plugin, it publishes a plugin query request via the MQTT protocol on the Topic:command, for example, Topic://command{NIC MAC}. This request includes specific query parameters, such as the plugin name and version number. These parameters help other components in the business platform (such as servers or middleware) locate and provide the corresponding plugin data.

The network interface card (NIC) device also subscribes to the Topic:reply topic, for example, Topic://reply{NIC mac}, to receive responses to its query requests. When components in the business platform find the corresponding plugin data and are ready to respond, they publish the data to this topic. As a subscriber, the NIC device immediately receives this data and processes it accordingly.

The network interface card (NIC) device can also subscribe to the Topic:report, for example, Topic://report{NIC mac}; the NIC device can subscribe to this topic to receive real-time status reports from the gateway plugin, such as CPU usage, memory usage, network traffic, etc.

Furthermore, through the internal interface, a second MQTT request initiated by any network interface device based on the MQTT protocol can be obtained.

Optionally, an MQTT Broker is deployed within the bus server. The MQTT Broker is configured with conversion rules to enable data transmission between the network interface card (NIC) device and the gateway plugin. Specifically, the MQTT Broker converts Topic://command{NIC MAC address} to Topic://{plugin name}command; the MQTT Broker converts Topic://reply{NIC MAC address} to Topic://{plugin name}reply; and the MQTT Broker converts Topic://report{NIC MAC address} to Topic://{plugin name}report.

Accordingly, when the second MQTT request contains plugin identification information, the second MQTT request is used as a plugin query request corresponding to the network interface device.

Step 402: Based on the MQTT protocol, transmit the plugin data corresponding to the plugin query request to the network card device through the second external interface.

Optionally, plugin query requests are published to a topic subscribed to by the network interface card (NIC), typically Topic:reply, as this is the topic the NIC expects to receive responses from. As an MQTT subscriber, the NIC continuously listens for messages on the Topic:reply topic. When the system publishes an MQTT message containing plugin data, the NIC immediately receives it. Upon receiving the message, the NIC parses the message content, extracts the required plugin data, and performs subsequent operations or processing based on this data.

As shown in Figure 5, based on the MQTT protocol, the plugin data corresponding to the plugin query request is transmitted to the network interface device through the second external interface, including steps 501 and 502:

Step 501: Add the routing address corresponding to the network card device to the plugin data corresponding to the plugin query request to obtain the target plugin data.

Specifically, after the business platform processes the plugin query request for the network interface card (NIC) device and finds the corresponding plugin data, the system adds the NIC device's routing address to this data. This routing address is a unique identifier for the NIC device in the network, and may be an IP address, MAC address, or other type of network identifier.

By adding the routing address to the plugin data, the system can ensure that the response message is accurately sent back to the network interface card (NIC) that initiated the request, without confusion even when multiple NICs exist in the network.

Step 502: Based on the MQTT protocol, transmit the target plug-in data to the network card device through the second external interface.

Optionally, once the routing address is added to the original plugin data, this data becomes "target plugin data." This means that this data has been specifically marked as being sent to the network interface card (NIC) device with that routing address. Next, based on the MQTT protocol, the target plugin data is sent to the NIC device via a second external interface. In this process, the "second external interface" may refer to a network connection or communication port that supports MQTT. The target plugin data is packaged into an MQTT message and published with an appropriate topic specified (usually a topic subscribed to by the NIC device, such as Topic:reply).

Accordingly, the network interface card (NIC) device, as an MQTT subscriber, will receive this MQTT message containing the target plugin data. Since the message includes the NIC device's routing address, the NIC device can confirm that this message is specifically prepared for it. After receiving the data, the NIC device will parse and process it, performing corresponding operations based on the content of the plugin data.

In one implementation, the routing address includes the physical address of the network interface card (NIC). Based on the MQTT Broker's translation rules, the routing address corresponding to the NIC can also be added to the plugin data corresponding to the plugin query request to obtain the target plugin data; based on the MQTT protocol, the target plugin data is transmitted to the NIC via a second external interface.

The conversion rules for MQTT Broker are as follows:

1) Internal Topic: //{plugin name}/report sends data to Interface B Topic: report/{network card MAC address}.

2) Internal Topic: //{plugin name}/reply sends a message to Interface B Topic: reply/{network card MAC address}.

3) Send the internal Topic: //{plugin name}/command to the B interface Topic: command/{network card MAC}.

In another possible implementation, the routing address includes the physical address of the network interface card (NIC) device and the device account data of the NIC device.

The conversion rules for the MQTT Broker are as follows:

1) Internal Topic: //{Plugin Name}/report sends data to Interface B Topic: report/{Network Card MAC}{Account Data}

2) Internal Topic: //{plugin name}/reply sends data to Interface B Topic: reply/{network card MAC}{account data}.

3) Send the internal Topic: //{plugin name}/command to the B interface Topic: command/{network card MAC}{account data}.

In this embodiment, by limiting the communication between the gateway plugin and the business platform to only three topics, the number and complexity of MQTT messages can be significantly reduced, thereby lowering the platform's processing load. This design simplifies the message flow, enabling the platform to process each message more efficiently. The introduction of a configuration module ensures that each gateway device is correctly configured and authenticated before connecting to the MQTT Broker. The configuration module manages and verifies the device's identity, access permissions, and the topics that can be published, thus enhancing device security. Furthermore, intelligent message routing through the distribution module ensures that sensitive information is not mistakenly sent to unauthorized devices or systems.

The distribution module acts like a message router, distributing MQTT messages to the correct gateway or plugin based on message type, target device, or other rules. This ensures message isolation, meaning each plugin only receives messages relevant to its function and is not affected by other unrelated messages. This isolation not only improves system reliability and efficiency but also reduces potential security risks, as malicious messages find it more difficult to infiltrate parts that shouldn't receive them.

The MQTT Broker, acting as a message broker, is responsible for receiving and forwarding MQTT messages. It is the core of the entire messaging system. The configuration module is responsible for device access configuration, permission management, and Topic subscription and publication rules. It ensures that devices meet security requirements and are correctly configured with their communication parameters before accessing the system. The distribution module intelligently distributes messages to the correct destinations according to the rules set by the configuration module. It acts as a message filter and router, ensuring that messages reach their intended destinations accurately and efficiently.

In summary, this design, by limiting the number of topics and introducing configuration and distribution modules, effectively reduces the platform's workload and improves device security and the isolation of MQTT messages. These measures together constitute an efficient, secure, and scalable messaging system.

It should be understood that although the steps in the flowcharts of the above embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the above embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

Based on the same inventive concept, this application also provides a bus communication device for implementing the bus communication method described above. The solution provided by this device is similar to the implementation described in the above method; therefore, the specific limitations in one or more bus communication device embodiments provided below can be found in the limitations of the bus communication method described above, and will not be repeated here.

In an exemplary embodiment, as shown in FIG6, a bus communication device is provided, applied to a bus server. The bus server includes a first external interface for connecting to a service provider, a second external interface for connecting to a service platform, and an internal interface for connecting to a gateway plugin. The device includes: an acquisition module 11, a first internal transmission module 12, a second internal transmission module 13, and a sending module 14, wherein...

Module 11 is used to obtain business data published by the service provider through the first external interface based on the MQTT protocol.

The first internal transmission module 12 is used to transmit business data to the gateway plug-in through an internal interface;

The second internal transmission module 13 is used to obtain plugin data transmitted by the gateway plugin through an internal interface; wherein, the plugin data is obtained based on business data processing.

The sending module 14 is used to transmit plug-in data to the business platform through a second external interface based on the MQTT protocol.

In one embodiment, the number of gateway plugins connected to the internal interface is at least two, the number of service providers connected to the first external interface is at least two, and the first internal transmission module 12 is further configured to: when any... When a gateway plugin initiates a business query request based on the MQTT protocol, it retrieves the business data corresponding to the business query request from the business data provided by each business provider.

The internal interface is used to transmit the business data corresponding to the business query request to the gateway plugin.

In one embodiment, the device further includes a first request module, the first request module being configured to:

The internal interface is used to obtain the first MQTT request initiated by any gateway plugin based on the MQTT protocol.

When the first MQTT request contains business identification information, the first MQTT request is used as the business query request corresponding to the gateway plugin.

In one embodiment, the number of gateway plugins connected to the internal interface is at least two, and the service platform has at least two network interface card devices deployed.

Correspondingly, the second internal transmission module 13 is also used to: when a plugin query request initiated by any network card device in the service platform based on the MQTT protocol is obtained, the plugin data corresponding to the plugin query request is obtained from the plugin data provided by each gateway plugin;

Based on the MQTT protocol, the plugin data corresponding to the plugin query request is transmitted to the network card device through the second external interface.

In one embodiment, the device further includes a second request module for:

The internal interface is used to obtain a second MQTT request initiated by any network interface device based on the MQTT protocol.

When the second MQTT request contains plugin identification information, the second MQTT request is used as a plugin query request corresponding to the network interface device.

In one embodiment, the step of transmitting the plugin data corresponding to the plugin query request to the network interface card device via the second external interface based on the MQTT protocol includes:

Add the routing address corresponding to the network card device to the plugin data corresponding to the plugin query request to obtain the target plugin data;

Based on the MQTT protocol, the target plug-in data is transmitted to the network card device through the second external interface.

In one embodiment, the routing address includes the physical address of the network interface card (NIC) device.

In one embodiment, the routing address also includes the device account data of the network interface card (NIC).

Each module in the aforementioned bus communication device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can call and execute the operations corresponding to each module.

In an exemplary embodiment, a computer device is provided, which can be a server, specifically the bus server described in this application, and its internal structure can be as shown in Figure 7. The computer device includes a processor, memory, input/output interfaces (I/O), and a communication interface. The processor, memory, and I/O interfaces are connected via a system bus, and the communication interface is connected to the system bus via the I/O interfaces. The processor of the computer device provides computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The database of the computer device stores bus communication method data. The I/O interfaces of the computer device are used for exchanging information between the processor and external devices. The communication interface of the computer device is used for communicating with external terminals via a network connection. When the computer program is executed by the processor, it implements a bus communication method.

Those skilled in the art will understand that the structure shown in Figure 7 is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

In one exemplary embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

Based on the MQTT protocol, business data published by the service provider is obtained through the first external interface;

Transmit business data to the gateway plugin through the internal interface;

The plugin data transmitted by the gateway plugin is obtained through an internal interface; the plugin data is based on business data processing. Arrived;

Based on the MQTT protocol, the plugin data is transmitted to the business platform through a second external interface.

In one embodiment, when the processor executes the computer program, it further implements the following steps: the number of gateway plugins connected to the internal interface is at least two, and the number of service providers connected to the first external interface is at least two; transmitting the service data to the gateway plugin through the internal interface includes: when a service query request initiated by any gateway plugin based on the MQTT protocol is obtained, the service data corresponding to the service query request is obtained from the service data provided by each service provider; and transmitting the service data corresponding to the service query request to the gateway plugin through the internal interface.

In one embodiment, when the processor executes the computer program, it further performs the following steps: obtaining a first MQTT request initiated by any gateway plugin based on the MQTT protocol through the internal interface; when the first MQTT request contains business identification information, the first MQTT request is used as the business query request corresponding to the gateway plugin.

In one embodiment, when the processor executes the computer program, it further implements the following steps: the number of gateway plugins connected to the internal interface is at least two, and at least two network interface card (NIC) devices are deployed in the service platform; the step of transmitting the plugin data to the service platform through the second external interface based on the MQTT protocol includes: when a plugin query request initiated by any NIC device in the service platform based on the MQTT protocol is obtained, the plugin data corresponding to the plugin query request is obtained from the plugin data provided by each gateway plugin; and the plugin data corresponding to the plugin query request is transmitted to the NIC device through the second external interface based on the MQTT protocol.

In one embodiment, when the processor executes the computer program, it further performs the following steps: obtaining a second MQTT request initiated by any network interface card device based on the MQTT protocol through the internal interface; when the second MQTT request contains plugin identification information, the second MQTT request is used as a plugin query request corresponding to the network interface card device.

In one embodiment, when the processor executes the computer program, it further implements the following steps: transmitting the plugin data corresponding to the plugin query request to the network card device through the second external interface based on the MQTT protocol, including: adding the routing address corresponding to the network card device to the plugin data corresponding to the plugin query request to obtain target plugin data; transmitting the target plugin data to the network card device through the second external interface based on the MQTT protocol.

In one embodiment, the routing address includes the physical address of the network interface card (NIC) device.

In one embodiment, the routing address may also include the device account data of the network interface card (NIC).

In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, the computer program performing the following steps when executed by a processor:

Based on the MQTT protocol, business data published by the service provider is obtained through the first external interface;

Transmit business data to the gateway plugin through the internal interface;

The plugin data transmitted by the gateway plugin is obtained through the internal interface; the plugin data is obtained based on business data processing.

Based on the MQTT protocol, the plugin data is transmitted to the business platform through a second external interface.

In one embodiment, when the computer program is executed by the processor, it further implements the following steps: the number of gateway plugins connected to the internal interface is at least two, and the number of service providers connected to the first external interface is at least two; transmitting the service data to the gateway plugin through the internal interface includes: when a service query request initiated by any gateway plugin based on the MQTT protocol is obtained, the service data corresponding to the service query request is obtained from the service data provided by each service provider; and transmitting the service data corresponding to the service query request to the gateway plugin through the internal interface.

In one embodiment, when the computer program is executed by the processor, it further performs the following steps: obtaining a first MQTT request initiated by any gateway plugin based on the MQTT protocol through the internal interface; when the first MQTT request contains business identification information, the first MQTT request is used as the business query request corresponding to the gateway plugin.

In one embodiment, when the computer program is executed by the processor, it further implements the following steps: the number of gateway plugins connected to the internal interface is at least two, and at least two network interface card (NIC) devices are deployed in the business platform; the step of transmitting the plugin data to the business platform through the second external interface based on the MQTT protocol includes: when a plugin query request initiated by any NIC device in the business platform based on the MQTT protocol is received, then in each gateway plugin... From the provided plugin data, obtain the plugin data corresponding to the plugin query request; based on the MQTT protocol, transmit the plugin data corresponding to the plugin query request to the network card device through the second external interface.

In one embodiment, when the computer program is executed by the processor, it further performs the following steps: obtaining a second MQTT request initiated by any network interface card device based on the MQTT protocol through the internal interface; when the second MQTT request contains plugin identification information, the second MQTT request is used as a plugin query request corresponding to the network interface card device.

In one embodiment, when the computer program is executed by the processor, it further implements the following steps: transmitting the plugin data corresponding to the plugin query request to the network card device through the second external interface based on the MQTT protocol, including: adding the routing address corresponding to the network card device to the plugin data corresponding to the plugin query request to obtain the target plugin data; transmitting the target plugin data to the network card device through the second external interface based on the MQTT protocol.

In one embodiment, the routing address includes the physical address of the network interface card (NIC) device.

In one embodiment, the routing address may also include the device account data of the network interface card (NIC).

In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, performs the following steps:

Based on the MQTT protocol, business data published by the service provider is obtained through the first external interface;

Transmit business data to the gateway plugin through the internal interface;

The plugin data transmitted by the gateway plugin is obtained through the internal interface; the plugin data is obtained based on business data processing.

Based on the MQTT protocol, the plugin data is transmitted to the business platform through a second external interface.

In one embodiment, when the computer program is executed by the processor, it further implements the following steps: the number of gateway plugins connected to the internal interface is at least two, and the number of service providers connected to the first external interface is at least two; transmitting the service data to the gateway plugin through the internal interface includes: when a service query request initiated by any gateway plugin based on the MQTT protocol is obtained, the service data corresponding to the service query request is obtained from the service data provided by each service provider; and transmitting the service data corresponding to the service query request to the gateway plugin through the internal interface.

In one embodiment, when the computer program is executed by the processor, it further performs the following steps: obtaining a first MQTT request initiated by any gateway plugin based on the MQTT protocol through the internal interface; when the first MQTT request contains business identification information, the first MQTT request is used as the business query request corresponding to the gateway plugin.

In one embodiment, when the computer program is executed by the processor, it further implements the following steps: the number of gateway plugins connected to the internal interface is at least two, and at least two network interface card (NIC) devices are deployed in the business platform; the step of transmitting the plugin data to the business platform through the second external interface based on the MQTT protocol includes: when a plugin query request initiated by any NIC device in the business platform based on the MQTT protocol is obtained, the plugin data corresponding to the plugin query request is obtained from the plugin data provided by each gateway plugin; and the plugin data corresponding to the plugin query request is transmitted to the NIC device through the second external interface based on the MQTT protocol.

In one embodiment, when the computer program is executed by the processor, it further performs the following steps: obtaining a second MQTT request initiated by any network interface card device based on the MQTT protocol through the internal interface; when the second MQTT request contains plugin identification information, the second MQTT request is used as a plugin query request corresponding to the network interface card device.

In one embodiment, when the computer program is executed by the processor, it further implements the following steps: transmitting the plugin data corresponding to the plugin query request to the network card device through the second external interface based on the MQTT protocol, including: adding the routing address corresponding to the network card device to the plugin data corresponding to the plugin query request to obtain the target plugin data; transmitting the target plugin data to the network card device through the second external interface based on the MQTT protocol.

In one embodiment, the routing address includes the physical address of the network interface card (NIC) device.

In one embodiment, the routing address may also include the device account data of the network interface card (NIC).

It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data must comply with relevant regulations.

Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this patent application should be determined by the appended claims.

Claims (15)

A bus communication method is applied to a bus server, the bus server including a first external interface for connecting to a service provider, a second external interface for connecting to a service platform, and an internal interface for connecting to a gateway plugin; the method includes: Based on the MQTT (Message Queuing Telemetry Transport) protocol, the service data published by the service provider is obtained through the first external interface; The service data is transmitted to the gateway plugin through the internal interface. The plugin data transmitted by the gateway plugin is obtained through the internal interface; wherein, the plugin data is obtained based on the business data processing; and Based on the MQTT protocol, the plugin data is transmitted to the business platform through the second external interface. According to the method of claim 1, the number of gateway plugins connected to the internal interface is at least two, and the number of service providers connected to the first external interface is at least two; and The transmission of the service data to the gateway plugin through the internal interface includes: When a service query request initiated by any gateway plugin based on the MQTT protocol is received, the corresponding service data for the service query request is retrieved from the service data provided by each service provider; and The internal interface is used to transmit the business data corresponding to the business query request to the gateway plugin. The method according to claim 2, wherein the method further comprises: Through the internal interface, obtain the first MQTT request initiated by any gateway plugin based on the MQTT protocol; and When the first MQTT request contains business identification information, the first MQTT request is used as the business query request corresponding to the gateway plugin. According to the method of claim 3, the service identification information includes the identifier of the target device corresponding to the service provider, the request type, and related parameter information. According to the method of claim 1, the number of gateway plugins connected to the internal interface is at least two, and the service platform has at least two network interface card (NIC) devices deployed; and The step of transmitting the plugin data to the business platform via the second external interface based on the MQTT protocol includes: When a plugin query request initiated by any network interface card (NIC) device in the service platform based on the MQTT protocol is received, the plugin data corresponding to the plugin query request is retrieved from the plugin data provided by each gateway plugin; and Based on the MQTT protocol, the plugin data corresponding to the plugin query request is transmitted to the network card device through the second external interface. The method according to claim 5, wherein the method further comprises: The internal interface is used to obtain a second MQTT request initiated by any network interface device based on the MQTT protocol. When the second MQTT request contains plugin identification information, the second MQTT request is used as a plugin query request corresponding to the network interface device. According to the method of claim 5, wherein transmitting the plugin data corresponding to the plugin query request to the network interface card device via the second external interface based on the MQTT protocol includes: Add the routing address corresponding to the network interface card (NIC) device to the plugin data corresponding to the plugin query request to obtain the target plugin data; and Based on the MQTT protocol, the target plug-in data is transmitted to the network card device through the second external interface. According to the method of claim 7, the second external interface includes a network connection or communication port that supports the MQTT protocol. According to the method of claim 7, the routing address includes the physical address of the network interface card device. According to the method of claim 9, the routing address further includes the device account of the network interface card (NIC) device. data. The method according to any one of claims 1 to 10, wherein the MQTT protocol adopts a publish/subscribe pattern. A bus communication device is applied to a bus server, the bus server including a first external interface for connecting to a service provider, a second external interface for connecting to a service platform, and an internal interface for connecting to a gateway plugin; the device includes: The acquisition module is used for the MQTT protocol to acquire business data published by the service provider through the first external interface; The first internal transmission module is used to transmit the service data to the gateway plugin through the internal interface; The second internal transmission module is used to obtain plugin data transmitted by the gateway plugin through the internal interface; wherein the plugin data is obtained based on the business data processing; and The sending module is used to transmit the plug-in data to the business platform through the second external interface based on the MQTT protocol. A computer device includes a memory and a processor, the memory storing a computer program, the processor executing the computer program to implement the steps of the method according to any one of claims 1 to 11. A computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the method according to any one of claims 1 to 11. A computer program product comprising a computer program that, when executed by a processor, implements the steps of the method according to any one of claims 1 to 11.