Data transmission method based on open interconnection bus and related equipment

Abstract

The invention provides a data transmission method based on an open interconnection bus and related equipment. The method comprises the following steps: receiving a first data request from a first data platform via a first platform agent, wherein the first data request is used for requesting first target data about a second data platform; in response to the first data request, the open interconnection bus sends the first data request to a second data platform through a second platform agent; the open interconnection bus receives first target data aiming at the first data request from the second data platform through the second platform agent; and sending the first target data to the first data platform through the first platform agent.

Description

Technical Field

[0001] The present disclosure relates to the field of Internet of Things communication, and in particular to a data transmission method based on an open interconnection bus and related devices. Background Art

[0002] Existing charging piles and charging platforms may adopt different communication protocols and interface standards, resulting in data being unable to communicate with each other, making it impossible to achieve unified management and scheduling, and restricting the application and popularization of charging facilities. Summary of the Invention

[0003] The present disclosure proposes a data transmission method based on an open interconnection bus and related devices to solve the above-mentioned technical problems to a certain extent.

[0004] In a first aspect of the present disclosure, a data transmission method based on an open interconnection bus is provided, including:

[0005] Receiving, via a first platform agent, a first data request from a first data platform, where the first data request is used to request first target data about a second data platform;

[0006] In response to the first data request, the open interconnection bus sends the first data request to the second data platform via a second platform agent;

[0007] The open interconnection bus receives, via the second platform agent, the first target data from the second data platform in response to the first data request; and sends the first target data to the first data platform via the first platform agent.

[0008] In some embodiments, the first data request is generated by a first device connected to the first data platform and is sent to the first data platform via a first internal network of the first data platform by a first device agent corresponding to the first device.

[0009] In some embodiments, the method further includes:

[0010] In response to the first platform agent receiving the first target data, storing the first target data in a first data buffer of the first data platform and sending it to the first device agent via the first internal network.

[0011] In some embodiments, the first data request is sent to a second device agent via the second platform agent and is sent by the second device agent to a corresponding second device, and the second device is connected to the second data platform;

[0012] The second device processes the first data request and returns the first target data.

[0013] In some embodiments, the method further includes:

[0014] In response to the second platform agent receiving the first data request, retrieve the second data buffer of the second data platform;

[0015] In response to the first target data existing in the second data buffer, return the first target data to the open interconnect bus;

[0016] In response to the first target data not existing in the second data buffer, send the first data request to the second device agent.

[0017] In some embodiments, the method further includes:

[0018] Send a second data request to the first internal network via the first device agent, the second data request being generated based on the first device and for requesting second target data about a third device; the third device is connected to the first data platform;

[0019] The second data request is sent to the third device via the first internal network and the third device agent corresponding to the third device;

[0020] The third device processes the second data request and returns the second target data.

[0021] The second target data is sent to the first device via the third device agent, the first internal network, and the first device agent.

[0022] In some embodiments, the first data request is a subscription request; the method further includes:

[0023] Determine whether a target data queue for the target data exists in the existing data queue of the second data platform;

[0024] In response to the target data queue existing in the existing data queue, return the target data queue to the open interconnect bus; and periodically add updated data corresponding to the subscription request to the target data queue and send it to the first device via the open interconnect bus;

[0025] In response to the target data queue not existing in the existing data queue, establish a target data queue and retrieve whether the target data queue exists in the second data buffer;

[0026] In response to the target data existing in the second data buffer, add the target data to the target data queue and return it to the open interconnect bus;

[0027] In response to the target data not existing in the second data buffer, the update data corresponding to the subscription request is periodically added to the target data queue and sent to the first device via the open interconnect bus;

[0028] In response to receiving an unsubscribe request, the open interconnect bus suspends the target data queue and returns the data in the target data queue to the second data buffer.

[0029] In a second aspect of the present disclosure, there is provided a data transmission device based on an open interconnect bus, including:

[0030] A bus receiving module, configured to receive, via a first platform agent, a first data request from a first data platform, where the first data request is used to request first target data about a second data platform;

[0031] A bus sending module, configured to, in response to the first data request, send the first data request to the second data platform via a second platform agent;

[0032] The bus receiving module is further configured to receive, via the second platform agent, the first target data from the second data platform for the first data request;

[0033] The bus sending module is further configured to send the first target data to the first data platform via the first platform agent.

[0034] In some embodiments, the first data request is generated by a first device connected to the first data platform;

[0035] The device further includes: a first device agent corresponding to the first device, configured to send the first data request to the first data platform via a first internal network of the first data platform.

[0036] In some embodiments, the first platform agent is further configured to, in response to receiving the first target data, store the first target data in a first data buffer of the first data platform and send it to the first device agent via the first internal network.

[0037] In some embodiments, the device further includes:

[0038] A second device agent, configured to receive the first data request from the second platform agent and send it to a corresponding second device, where the second device is connected to the second data platform;

[0039] The second device is further configured to process the first data request and return the first target data.

[0040] In some embodiments, the second platform agent is further configured to retrieve a second data buffer of the second data platform in response to receiving the first data request;

[0041] The second data buffer is further configured to return the first target data to the open interconnect bus in response to the existence of the first target data;

[0042] The second data buffer is further configured to forward the first data request to the second device agent in response to the non-existence of the first target data.

[0043] In some embodiments, the first device agent is further configured to send a second data request to the first internal network, where the second data request is generated based on the first device and is used to request second target data about a third device; the third device is connected to the first data platform;

[0044] The apparatus further includes:

[0045] A third device agent corresponding to the third device, configured to receive the second data request from the first internal network and send it to the third device;

[0046] The third device is further configured to process the second data request and return the second target data;

[0047] The third device agent is further configured to send the second target data to the first internal network and send it to the first device via the first device agent.

[0048] In some embodiments, the first data request is a subscription request; the apparatus further includes:

[0049] A judgment module, configured to judge whether there is a target data queue about the target data in the existing data queue of the second data platform;

[0050] A target queue module, configured to return the target data queue to the open interconnect bus in response to the existence of the target data queue in the existing data queue; and regularly add updated data corresponding to the subscription request to the target data queue and send it to the first device via the open interconnect bus;

[0051] The target queue module is further configured to, in response to the non-existence of the target data queue in the existing data queue, establish a target data queue and retrieve whether the target data queue exists in the second data buffer; in response to the existence of the target data in the second data buffer, add the target data to the target data queue and return it to the Open Connectivity Bus; and, in response to the non-existence of the target data in the second data buffer, periodically add the updated data corresponding to the subscription request to the target data queue and send it to the first device via the Open Connectivity Bus.

[0052] The bus receiving module is further configured to, in response to receiving an unsubscribe request, pause the target data queue and return the data in the target data queue to the second data buffer.

[0053] In a third aspect of the present disclosure, an electronic device is provided, including one or more processors and a memory; and one or more programs, wherein the one or more programs are stored in the memory and executed by the one or more processors, and the programs include instructions for executing the method according to the first aspect.

[0054] In a fourth aspect of the present disclosure, a non-volatile computer-readable storage medium containing a computer program is provided, which, when executed by one or more processors, causes the processors to execute the method according to the first aspect.

[0055] In a fifth aspect of the present disclosure, a computer program product is provided, including computer program instructions, which, when executed on a computer, cause the computer to execute the method according to the first aspect.

[0056] As can be seen from the above, a data transmission method and related devices provided by the present disclosure establish a device data proxy above the charging facility and platform application, which is responsible for collecting and storing data and periodically interacting with the platform where it is located; establish a platform data proxy between the platform and the Open Connectivity Bus, which is responsible for sending and subscribing to the data required by the platform and internal devices and periodically interacting with the Open Connectivity Bus; each level of data proxy and the Open Connectivity Bus are interconnected through the TCP / IP protocol to solve the problem of heterogeneous protocol adaptation between different devices. Through the various data platforms in the Open Connectivity Bus, the data proxy and devices will jointly operate in a heterogeneous protocol adaptation mode that supports vehicle-to-grid interaction data sharing, realizing data subscription and collection between different platforms and devices, thereby achieving interoperability between heterogeneous protocols, reducing data transmission pressure and resource occupation, and ensuring the reliability and efficiency of data transmission. Description of the Drawings

[0057] To more clearly illustrate the technical solutions in the present disclosure or related technologies, the following will briefly introduce the drawings required for use in the embodiments or the description of related technologies. Obviously, the drawings in the following description are only the embodiments of the present disclosure. For those of ordinary skill in the art, without creative efforts, other drawings can be obtained based on these drawings.

[0058] Figure 1 Schematic diagram of a data transmission scenario based on an open interconnect bus according to an embodiment of the present disclosure.

[0059] Figure 2 Schematic diagram of a data transmission architecture based on an open interconnect bus according to an embodiment of the present disclosure.

[0060] Figure 3 Schematic flowchart of a data transmission method based on an open interconnect bus according to an embodiment of the present disclosure.

[0061] Figure 4 Schematic diagram of a data subscription process between different data platforms according to an embodiment of the present disclosure.

[0062] Figure 5 Schematic diagram of a data subscription process between devices of different data platforms according to an embodiment of the present disclosure.

[0063] Figure 6 Schematic diagram of a data subscription process between devices within a platform according to an embodiment of the present disclosure.

[0064] Figure 7 Schematic diagram of a data transmission device based on an open interconnect bus according to an embodiment of the present disclosure. Detailed implementation manners

[0065] To make the purpose, technical solutions and advantages of the present disclosure clearer and more understandable, the following further details the present disclosure in combination with specific embodiments and with reference to the drawings.

[0066] It should be noted that, unless otherwise defined, the technical terms or scientific terms used in the embodiments of the present disclosure should have the ordinary meanings understood by those of ordinary skill in the field to which the present disclosure belongs. The "first", "second" and similar terms used in the embodiments of the present disclosure do not denote any order, quantity or importance, but are only used to distinguish different components. Words such as "including" or "comprising" mean that the elements or objects appearing before the word cover the elements or objects listed after the word and their equivalents, without excluding other elements or objects. Words such as "connected" or "coupled" are not limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect. "Upper", "lower", "left", "right", etc. are only used to indicate relative position relationships, and when the absolute position of the object being described changes, the relative position relationship may also change accordingly.

[0067] It can be understood that, before using the technical solutions disclosed in the embodiments of the present disclosure, the types, usage scopes, usage scenarios, etc. of the personal information involved in the present disclosure should be informed to the user and the user's authorization should be obtained in an appropriate manner in accordance with relevant laws and regulations.

[0068] For example, when responding to receiving an active request from a user, a prompt message is sent to the user to clearly prompt the user that the operation requested by the user will require obtaining and using the user's personal information. Thus, the user can autonomously choose whether to provide personal information to software or hardware such as an electronic device, an application program, a server or a storage medium that executes the operation of the technical solution of the present disclosure according to the prompt message.

[0069] It can be understood that the above process of notifying and obtaining user authorization is only illustrative and does not limit the implementation manner of the present disclosure, and other manners that meet relevant laws and regulations can also be applied to the implementation manner of the present disclosure.

[0070] In the current field of electric vehicle charging facilities, with the popularization of electric vehicles and the rapid development of charging facility construction, the problem of interoperability between charging piles and charging platforms has become increasingly prominent. Existing charging piles and charging platforms may adopt different communication protocols and interface standards, resulting in data being unable to be interchanged, and unified management and scheduling cannot be achieved, which restricts the application and promotion of charging facilities. Existing solutions mainly include protocol conversion gateways, interface adapters, and proprietary data format conversion tools to achieve. Among them, the protocol conversion gateway realizes the conversion and compatibility between different protocols by deploying a protocol conversion gateway between the charging pile and the charging platform; the interface adapter realizes data interchange by adapting and unifying the interface specifications of different charging piles and charging platforms. The data format conversion tool converts and unifies the data formats collected by different charging piles and charging platforms in the cloud.

[0071] However, the existing technologies have problems such as complex solutions, poor scalability, and insufficient security. The existing solutions require the deployment of additional devices or tools, which increases system complexity and maintenance costs and makes it difficult to adapt to the ever-changing development needs of charging facilities. At the same time, it is difficult to ensure the security of data transmission, and there are risks of data leakage and security attacks.

[0072] Therefore, how to solve the protocol compatibility problem between charging piles and charging platforms, achieve heterogeneous data interconnection, and improve the interconnection level of charging data has become a technical problem that needs to be solved urgently.

[0073] In view of this, the embodiments of the present disclosure provide a data transmission method and related devices based on an open interconnection bus. By establishing a device data proxy above the charging facilities and platform applications, it is responsible for collecting and storing data and interacting with the platform where it is located regularly; a platform data proxy is established between the platform and the open interconnection bus, which is responsible for sending and subscribing to the data required by the platform and internal devices and interacting with the open interconnection bus regularly; the data proxies at all levels are interconnected with the open interconnection bus through the TCP / IP protocol to solve the problem of heterogeneous protocol adaptation between different devices. As Figure 1 shown, Figure 1 shows a schematic diagram of a data transmission scenario based on an open interconnection bus according to an embodiment of the present disclosure. Through the data platforms, data proxies, and devices in the open interconnection bus, they will jointly operate in a heterogeneous protocol adaptation mode that supports vehicle-to-grid interaction data sharing, realize data subscription and collection between different platforms and devices, thereby achieving interconnection between heterogeneous protocols, reducing data transmission pressure and resource occupancy, and ensuring the reliability and efficiency of data transmission.

[0074] See Figure 2 , Figure 2 shows a schematic diagram of a data transmission architecture based on an open interconnection bus according to an embodiment of the present disclosure. Figure 2 In, the data transmission architecture based on the open interconnection bus includes: a data platform, a data user that exchanges data with the open interconnection bus; a platform data proxy, which is responsible for the unified scheduling and subscription of data from different platforms; a device, a data user that runs inside the data platform; a device data proxy, which realizes the unified scheduling and subscription of data from different devices inside the data platform; an open interconnection bus, a communication link that runs between data platforms and is responsible for data exchange.

[0075] In some embodiments, the data platform includes a power grid platform and a charging facility platform, and there is an internal data network or Internet application inside, which can be used for data uploading and downloading. The power grid platform mainly includes a power grid data information processing platform and other data platforms that convert charging data into power grid data, and the charging facility platform mainly includes an internal data exchange network composed of devices such as charging piles.

[0076] In some embodiments, the platform data proxy includes a data platform link, a bus interface, a sending data queue, a data subscription number, and a data buffer; according to different requirements, it can receive data from the data platform and form a data queue, and send the data in the data queue to the open interconnect bus as needed, or subscribe to relevant data from the open interconnect bus.

[0077] In some embodiments, the device includes attributes such as a device number, a device type, a device data address, a device subscription number, etc.; preferably, the device is responsible for services such as vehicle charging, continuously generates charging data, and needs to send data regularly.

[0078] In some embodiments, the device data proxy includes a device link, a data platform interface, a sending data queue, a data subscription number, and a data buffer; according to different requirements, it can receive data from the device and form a data queue, and send the data in the data queue to the platform data proxy as needed, or subscribe to relevant data from the platform data proxy.

[0079] In some embodiments, the open interconnect bus includes a data proxy list, a data platform list, a data queue, and a data subscription number list; the open interconnect bus is responsible for obtaining data according to the subscription number, finding relevant subscription numbers according to data requirements, receiving data from the data proxy, and sending data to the data proxy.

[0080] In the above architecture, each component constitutes a "service - bus - queue - data" structure in heterogeneous protocol adaptation. The open interconnect bus provides heterogeneous protocol adaptation services and a data bus, the data queues are implemented by the platform - side and device - side data proxies, and the relevant data is stored by the device and the platform.

[0081] Based on the above architecture, the heterogeneous protocol adaptation services of the open interconnect bus can be implemented, including:

[0082] 1. Platform internal device data subscription service: The platform internal device data subscription service provides a data subscription service for the devices inside the platform through the internal network of the data platform and the device data proxy inside the platform, and realizes the data sharing and protocol adaptation process of heterogeneous protocol devices inside the data platform.

[0083] 2. Inter - platform data subscription service: The inter - platform data subscription service provides a data subscription service for different data platforms through the open interconnect bus, the platform data proxy, and the data buffer inside the data platform, and realizes the heterogeneous protocol data sharing and protocol adaptation process between data platforms.

[0084] 3. Inter-platform internal device data subscription service: The inter-platform data subscription service provides data subscription services for different devices within different data platforms through the open interconnection bus, device data proxy, platform data proxy, and data buffer within the data platform, realizing the heterogeneous protocol data sharing and protocol adaptation process from devices within one data platform to devices within another data platform.

[0085] See Figure 3 , Figure 3 which shows a schematic flowchart of a data transmission method based on an open interconnection bus according to an embodiment of the present disclosure. The data transmission method based on an open interconnection bus according to an embodiment of the present disclosure can be deployed on a terminal or a server side. Figure 3 In, the data transmission method 300 based on an open interconnection bus may further include the following steps.

[0086] In step S310, the open interconnection bus receives a first data request from a first data platform via a first platform proxy, and the first data request is used to request first target data about a second data platform.

[0087] In step S320, in response to the first data request, the open interconnection bus sends the first data request to the second data platform via a second platform proxy.

[0088] In step S330, the open interconnection bus receives the first target data from the second data platform for the first data request via the second platform proxy; and sends the first target data to the first data platform via the first platform proxy.

[0089] Among them, the first data platform sends a data request to the first platform proxy, and this request clearly indicates the first target data in the second data platform that needs to be obtained. After receiving the request, the first platform proxy performs necessary processing through the open interconnection bus, such as routing selection, permission verification, data format conversion, etc. After the processing is completed, the open interconnection bus forwards the request to the second data platform to obtain the required first target data. The second data platform responds to the request and returns the first target data to the open interconnection bus. The open interconnection bus then returns the data to the first platform proxy, and finally the first platform proxy delivers the data to the first data platform.

[0090] However, due to drawbacks such as hard - coding dependency, poor scalability, high maintenance costs, lack of flexibility, performance issues, complexity, security risks, lack of standardization, and difficulty in monitoring and management, traditional heterogeneous protocol adaptation technologies are difficult to adapt to the rapidly changing and diverse integration requirements of charging facilities, resulting in low interaction efficiency between systems, increasing technical burdens and operational risks. Compared with traditional heterogeneous protocol adaptation technologies, according to the method of the embodiments of the present disclosure, each data platform, data proxy, and device in the open interconnection bus will jointly operate in a heterogeneous protocol adaptation mode that supports vehicle - to - grid interaction data sharing. This mode uses distributed operation as the device framework, and each device performs shared adaptation as needed. Among them, distributed operation means that devices, services, and data proxies at all levels run on relevant underlying devices. As the main body of data connection, the open interconnection bus will actually run on devices and data platforms at all levels. As part of protocol adaptation, through physical network connections and application connections between devices at all levels, the data exchange function of the open interconnection bus is realized. On - demand shared adaptation means that platforms and devices at all levels on the open interconnection bus will perform data sharing adaptation according to needs. During operation, data proxies at all levels meet regular data requirements by establishing subscriptions, and no relevant data transmission occurs between devices and platforms that have not subscribed, reducing data transmission pressure and resource occupancy on the entire open interconnection bus.

[0091] In some embodiments, before step S310, method 300 may further include: establishing a platform proxy and / or a device proxy; connecting the platform proxy and / or the device proxy to the open interconnection bus.

[0092] Specifically, after a new data platform joins the open interconnection bus, a data proxy is established for it. The open interconnection bus assigns a platform number and a data subscription number to it, and adds this platform to the data platform list and data subscription number list inside the open interconnection bus.

[0093] Establishing a data connection between the data platform and the open interconnection bus, the steps include: the data platform requests to establish a connection with the platform data proxy through its own transmission protocol; the platform data proxy sends a connection establishment request to the open interconnection bus through the TCP / IP protocol; the platform data proxy starts asynchronous two - way communication with the open interconnection bus and other data proxies, and regularly detects the network connection status.

[0094] In some embodiments, method 300 may further include:

[0095] Internal devices of the first data platform regularly send device data to the corresponding device proxy;

[0096] The device proxy sends the device data to the platform proxy;

[0097] The platform agent stores the device data in different queues to obtain data queues, processes the data queues into data packets, adds subscription numbers, platform numbers, and device number information to the data packets, and periodically sends the data in the data queues to the open interconnect bus.

[0098] In some embodiments, method 300 may further include:

[0099] The first data request is generated by a first device connected to the first data platform and sent to the first data platform via a first internal network of the first data platform by a first device agent corresponding to the first device.

[0100] In some embodiments, method 300 may further include:

[0101] In response to the first platform agent receiving the first target data, the first target data is stored in a first data buffer of the first data platform and sent to the first device agent via the first internal network.

[0102] Specifically, specifically, refer to Figure 4 , Figure 4 which shows a schematic diagram of the data subscription process between different data platforms according to an embodiment of the present disclosure. Figure 4 In, data platform 1 communicates with its platform data agent 1 through the HTTP protocol and sends its data subscription requirements to the open interconnect bus. Platform data agent 1 forwards the relevant data subscription requirements to the open interconnect bus. Platform data agent 2 of data platform 2 receives the data subscription requirements from the open interconnect bus through the HTTP protocol. Platform data agent 2 initiates communication with data platform 2 through the HTTP protocol to request to obtain its relevant data. Data platform 2 sends the relevant data to the data buffer of platform data agent 2. Platform data agent 2 establishes a data queue and sends the relevant data to the open interconnect bus. The open interconnect bus receives the relevant data and forwards it to platform data agent 1 through the HTTP protocol. Platform data agent 1 receives the relevant data and forwards it to data platform 1 through the HTTP protocol to complete the data subscription requirements..

[0103] In some embodiments, method 300 may further include:

[0104] The first data request is sent to a second device agent connected via the second platform agent and sent by the second device agent to the corresponding second device, and the second device is connected to the second data platform;

[0105] The second device processes the first data request and returns the first target data.

[0106] In some embodiments, method 300 may further include:

[0107] Upon receiving the first data request by the second platform agent, retrieve the second data buffer of the second data platform;

[0108] Upon the existence of the first target data in the second data buffer, return the first target data to the open interconnect bus;

[0109] Upon the non - existence of the first target data in the second data buffer, forward the first data request to the second device agent.

[0110] Specifically, referring to Figure 5 , Figure 5 shows a schematic diagram of the device - to - device data subscription process of different data platforms according to embodiments of the present disclosure. Figure 5 In, device 1 - A inside data platform 1 communicates with its device data agent 1 - A through the SOAP protocol and sends its data subscription requirements to the data platform. The device data agent 1 - A forwards the relevant data subscription requirements to data platform 1. Data platform 1 forwards the relevant data subscription requirements to platform data agent 1. Platform data agent 1 forwards the relevant data subscription requirements to the open interconnect bus. The open interconnect bus forwards the relevant data subscription requirements to platform data agent 2 of data platform 2. Platform data agent 2 sends data subscription requirements to data platform B through the HTTP protocol, requesting to obtain relevant data of its internal device 2 - A. Data platform B sends data subscription requirements to device data agent 2 - A through the HTTP protocol, requesting to obtain relevant data of its internal device 2 - A. Device data agent 2 - A sends data subscription requirements to device 2 - A through the SOAP protocol, requesting to obtain relevant data of its internal device B1. The device data agent 2 - A of the internal device 2 - A of the platform receives the data subscription requirements. Device 2 - A sends the relevant data to the data buffer of device data agent 2 - A. Device data agent 2 - A sends the relevant data to data platform 2 through the HTTP protocol. Data platform 2 sends the relevant data to platform data agent 2 through the HTTP protocol. Platform data agent 2 sends the relevant data to the open interconnect bus. The open interconnect bus sends the relevant data to platform data agent 1 of subscriber 1. Platform data agent 1 sends the relevant data to the data buffer of device data agent 1 - A. Device data agent 1 - A receives the relevant data and forwards it to internal device 1 - A of the platform through the SOAP protocol, completing the data subscription requirements.

[0111] It can be seen that the open interconnection bus establishes an open and extensible data exchange communication link. As the hub for data transmission between different platforms and devices, it can solve the problem of heterogeneous protocol adaptation, achieve data format conversion and unification, provide data subscription and publishing services, support on-demand sharing adaptation, and reduce data transmission pressure and resource occupancy. The device data proxy is responsible for collecting and storing device data and interacting with the platform data proxy. The data proxy is responsible for sending / subscribing to the data required by the platform and internal devices and interacting with the open interconnection bus. It realizes data interaction between devices and platforms, and between platforms and platforms, provides data buffering and queue management functions, and ensures the reliability and efficiency of data transmission. Each device, service, and data proxy runs on the relevant underlying devices, enabling flexible deployment and expansion. Each platform and device subscribes to and publishes data according to requirements, reducing data transmission pressure and resource occupancy. It improves system efficiency and flexibility, and reduces system costs and operation and maintenance difficulties.

[0112] In some embodiments, method 300 may further include:

[0113] Sending a second data request to the first internal network via the first device proxy, the second data request being generated based on the first device and for requesting second target data about a third device; the third device being connected to the first data platform;

[0114] The second data request is sent to the third device via the first internal network and the third device proxy corresponding to the third device;

[0115] The third device processes the second data request and returns the second target data.

[0116] The second target data is sent to the first device via the third device proxy, the first internal network, and the first device proxy.

[0117] Specifically, referring to Figure 6 , Figure 6 shows a schematic diagram of the data subscription process between internal devices of a platform according to an embodiment of the present disclosure. Figure 6In this case, the internal device A1 of the platform subscribes to data from the internal device A2 of the heterogeneous protocol, including: The internal device 1-A of the platform communicates with its device data proxy 1-A through the SOAP protocol and sends its data subscription requirements to the internal network of the data platform. The device data proxy 1-A forwards the relevant data subscription requirements to the internal network of the data platform. The device data proxy 1-B of the internal device 1-B of the platform receives the data subscription requirements. The device data proxy 1-B initiates communication with the internal device 1-B of the platform through the modbus protocol to request relevant data. The internal device 1-B sends the relevant data to the data buffer of the device data proxy 1-B. The data proxy 1-B establishes a data queue and sends the relevant data to the internal data network of the platform. The device data proxy 1-A receives the relevant data and forwards it to the internal device 1-A through the SOAP protocol to complete the data subscription requirements.

[0118] It can be seen that according to the method of the embodiments of the present disclosure, effective communication and data transmission between devices, between platforms, and between cross-platform devices are achieved, improving the interaction efficiency between systems and reducing the technical burden and operation risks.

[0119] In some embodiments, the first data request is a subscription request; Method 300 may further include: determining whether there is a target data queue for the target data in the existing data queue of the second data platform;

[0120] In response to the existence of the target data queue in the existing data queue, returning the target data queue to the open interconnect bus; and regularly adding the updated data corresponding to the subscription request to the target data queue and sending it to the first device via the open interconnect bus;

[0121] In response to the non-existence of the target data queue in the existing data queue, establishing a target data queue and retrieving whether the target data queue exists in the second data buffer;

[0122] In response to the existence of the target data in the second data buffer, adding the target data to the target data queue and returning it to the open interconnect bus;

[0123] In response to the non-existence of the target data in the second data buffer, regularly adding the updated data corresponding to the subscription request to the target data queue and sending it to the first device via the open interconnect bus;

[0124] In response to receiving an unsubscribe request, the open interconnect bus suspends the target data queue and returns the data in the target data queue to the second data buffer.

[0125] Among them, the first platform agent can send a data query / subscription application to the open interconnection bus according to the first platform's data requirements to obtain the required data in a heterogeneous protocol environment. Specifically, after logging in to the open interconnection bus, the platform data agent sends a data query / subscription instruction to the open interconnection bus according to the data platform requirements. The open interconnection bus forwards the corresponding instruction to the target platform data agent through a network connection. After the target platform data agent receives the relevant instruction, it will judge the instruction type:

[0126] If it is a data query instruction, it will check whether the relevant data exists in the data buffer. If so, the data will be passed to the open interconnection bus; if not, the instruction will be sent to the relevant device data agent inside the data platform, and the device data agent will upload the relevant data to the platform data agent, and then the platform data agent will upload the data to the open interconnection bus.

[0127] If it is a data subscription instruction, the following judgments will be made according to the existing data queue and buffer status:

[0128] If there is a data queue in the existing data queue with the same target as the subscription instruction party, the relevant data will be sent to the open interconnection bus and forwarded by the open interconnection bus to the subscriber. After that, this data queue will continue to run, and the relevant data will be regularly sent to the open interconnection bus and forwarded by the open interconnection bus to the subscriber.

[0129] If there is no data queue in the existing data queue with the same target as the subscription instruction party, a data queue with this subscription instruction party as the target will be established, and the data buffer will be retrieved.

[0130] If the relevant data exists in the data buffer, the relevant data will be added to this data queue, and then the data in this data queue will be sent to the open interconnection bus and forwarded by the open interconnection bus to the subscriber. After that, this data queue will continue to run, and the relevant data will be regularly sent to the open interconnection bus and forwarded by the open interconnection bus to the subscriber.

[0131] If the relevant data does not exist in the data buffer, this data queue will continue to run, monitor the relevant data inside the data platform, and regularly send the relevant data to the open interconnection bus and forwarded by the open interconnection bus to the subscriber.

[0132] If it is an unsubscribe instruction, the open interconnection bus will pause this data queue and return the relevant data to the data buffer.

[0133] After receiving the required data, each data platform and device will perform the required processing on its own data.

[0134] It can be seen that according to the method of the embodiments of the present disclosure, data subscription can be achieved in different scenarios. For exampleFigure 4 The data subscription process between the data platforms shown Figure 5 The data subscription process between devices of the data platform shown Figure 6 The data subscription process between internal devices of the platform shown. In different embodiments, the devices respectively adopt the SOAP protocol, the HTTP protocol, and the Modbus protocol to demonstrate the heterogeneous protocol adaptation effect achieved by the method of the embodiments of the present disclosure. By solving the protocol compatibility problem between different charging piles and charging platforms, heterogeneous data interconnection is realized, and the utilization rate of charging facilities is improved. Promote the interconnection and interoperability of charging infrastructure, build a more perfect charging network, and provide strong support for the popularization and development of electric vehicles. The open interconnection bus provides a unified interface specification, which is convenient for the access and conversion of different protocols, reduces the system development difficulty, and shortens the development cycle. The open interconnection bus can be reused for different charging piles and charging platforms, reducing the development cost and improving the efficiency. The open interconnection bus can provide a data transmission security guarantee mechanism to ensure the integrity and security of data transmission, and prevent data loss or tampering. The open interconnection bus can provide a user identity authentication and permission management mechanism to ensure the security and privacy protection of user data.

[0135] It should be noted that the method of the embodiments of the present disclosure can be executed by a single device, such as a computer or a server, etc. The method of this embodiment can also be applied to a distributed scenario, and multiple devices cooperate with each other to complete it. In this case of a distributed scenario, one of the multiple devices can only execute one or more steps of the method of the embodiments of the present disclosure, and these multiple devices will interact with each other to complete the described method.

[0136] It should be noted that some embodiments of the present disclosure have been described above. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be executed in a different order than in the above embodiments and still achieve the desired results. Additionally, the processes depicted in the drawings do not necessarily require the specific order or sequential order shown to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0137] Based on the same inventive concept, corresponding to the method of any of the above embodiments, the present disclosure also provides a data transmission device based on an open interconnection bus. The data transmission device based on the open interconnection bus, as Figure 7 shown, the device includes:

[0138] A bus receiving module, configured to receive a first data request from a first data platform via a first platform proxy, where the first data request is used to request first target data about a second data platform;

[0139] A bus sending module, configured to, in response to the first data request, send the first data request to a second data platform via a second platform agent;

[0140] The bus receiving module is further configured to receive, via the second platform agent, first target data from the second data platform for the first data request;

[0141] The bus sending module is further configured to send the first target data to the first data platform via the first platform agent.

[0142] In some embodiments, the first data request is generated by a first device connected to the first data platform;

[0143] The apparatus further includes: a first device agent corresponding to the first device, configured to send the first data request to the first data platform via a first internal network of the first data platform.

[0144] In some embodiments, the first platform agent is further configured to, in response to receiving the first target data, store the first target data in a first data buffer of the first data platform and send it to the first device agent via the first internal network.

[0145] In some embodiments, the apparatus further includes:

[0146] A second device agent, configured to receive the first data request from the second platform agent and send it to the corresponding second device, where the second device is connected to the second data platform;

[0147] The second device is further configured to process the first data request and return the first target data.

[0148] In some embodiments, the second platform agent is further configured to, in response to receiving the first data request, retrieve a second data buffer of the second data platform;

[0149] The second data buffer is further configured to, in response to the existence of the first target data, return the first target data to the Open Connectivity Bus;

[0150] The second data buffer is further configured to, in response to the non - existence of the first target data, send the first data request to the second device agent.

[0151] In some embodiments, the first device agent is further configured to send a second data request to the first internal network, where the second data request is generated based on the first device and is used to request second target data about a third device; the third device is connected to the first data platform;

[0152] The device further includes:

[0153] A third device agent corresponding to the third device, configured to receive the second data request from the first internal network and send it to the third device;

[0154] The third device is further configured to process the second data request and return the second target data;

[0155] The third device agent is further configured to send the second target data to the first internal network and send it to the first device via the first device agent.

[0156] In some embodiments, the first data request is a subscription request; the device further includes:

[0157] A judgment module, configured to judge whether there is a target data queue for the target data in the existing data queue of the second data platform;

[0158] A target queue module, configured to, in response to the existing data queue having the target data queue, return the target data queue to the open interconnection bus; and regularly add the updated data corresponding to the subscription request to the target data queue and send it to the first device via the open interconnection bus;

[0159] The target queue module is further configured to, in response to the existing data queue not having the target data queue, establish a target data queue and retrieve whether the target data queue exists in the second data buffer; in response to the second data buffer having the target data, add the target data to the target data queue and return it to the open interconnection bus; and, in response to the second data buffer not having the target data, regularly add the updated data corresponding to the subscription request to the target data queue and send it to the first device via the open interconnection bus;

[0160] The bus receiving module is further configured to, in response to receiving an unsubscribe request, pause the target data queue and return the data in the target data queue to the second data buffer.

[0161] For the convenience of description, when describing the above device, various modules are described separately according to their functions. Of course, when implementing the present disclosure, the functions of each module can be implemented in one or more software and / or hardware.

[0162] The device in the above embodiments is used to implement the corresponding data transmission method based on the open interconnection bus in any of the foregoing embodiments, and has the beneficial effects of the corresponding method embodiments, which will not be elaborated herein.

[0163] Based on the same inventive concept, corresponding to the method of any of the above embodiments, the present disclosure also provides a non-transitory computer-readable storage medium storing computer instructions for causing the computer to execute the data transmission method based on an open interconnect bus as described in any of the foregoing embodiments.

[0164] The computer-readable medium of this embodiment includes permanent and non-permanent, removable and non-removable media, and information storage can be implemented by any method or technology. The information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassette tapes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device.

[0165] The computer instructions stored in the storage medium of the above embodiment are used to cause the computer to execute the data transmission method based on an open interconnect bus as described in any of the foregoing embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be elaborated here.

[0166] Those of ordinary skill in the art should understand that the discussion of any of the above embodiments is only exemplary and is not intended to imply that the scope of the present disclosure (including the claims) is limited to these examples; under the concept of the present disclosure, the technical features in the above embodiments or different embodiments can also be combined, the steps can be implemented in any order, and there are many other variations in different aspects of the embodiments of the present disclosure as described above. For the sake of brevity, they are not provided in detail.

[0167] In addition, for simplicity of explanation and discussion, and so as not to make the embodiments of the present disclosure difficult to understand, well-known power / ground connections to integrated circuit (IC) chips and other components may or may not be shown in the provided drawings. Further, the devices may be shown in block diagram form in order to avoid making the embodiments of the present disclosure difficult to understand, and this also takes into account the fact that details of the implementation of these block diagram devices are highly dependent on the platform on which the embodiments of the present disclosure are to be implemented (i.e., these details should be fully within the understanding of those skilled in the art). In cases where specific details (such as circuits) are set forth to describe exemplary embodiments of the present disclosure, it will be apparent to those skilled in the art that the embodiments of the present disclosure may be practiced without these specific details or with variations of these specific details. Accordingly, these descriptions should be regarded as illustrative rather than restrictive.

[0168] Although the present disclosure has been described in connection with specific embodiments thereof, many alternatives, modifications, and variations of these embodiments will be apparent to those of ordinary skill in the art based on the foregoing description. For example, other memory architectures (such as dynamic RAM (DRAM)) may be used with the embodiments discussed.

[0169] Embodiments of the present disclosure are intended to cover all such alternatives, modifications, and variations that fall within the broad scope of the appended claims. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc., made within the spirit and principle of the embodiments of the present disclosure shall be included within the protection scope of the present disclosure.

Claims

1. A data transmission method based on an open interconnect bus, comprising: The open interconnect bus receives a first data request from a first data platform via a first platform agent, and the first data request is used to request first target data about a second data platform; In response to the first data request, the open interconnect bus sends the first data request to the second data platform via a second platform agent; The open interconnect bus receives the first target data from the second data platform for the first data request via the second platform agent; And sends the first target data to the first data platform via the first platform agent.

2. The method according to claim 1, wherein, The first data request is generated by a first device connected to the first data platform, and is sent to the first data platform via a first internal network of the first data platform by a first device agent corresponding to the first device.

3. The method according to claim 2, further comprising: In response to the first platform agent receiving the first target data, storing the first target data in a first data buffer of the first data platform, and sending it to the first device agent via the first internal network.

4. The method according to claim 1, wherein, The first data request is sent to a second device agent via the second platform agent and is sent by the second device agent to the corresponding second device, and the second device is connected to the second data platform; The second device processes the first data request and returns the first target data.

5. The method according to claim 4, further comprising: In response to the second platform agent receiving the first data request, retrieving a second data buffer of the second data platform; In response to the first target data existing in the second data buffer, returning the first target data to the open interconnect bus; In response to the first target data not existing in the second data buffer, sending the first data request to the second device agent.

6. The method according to claim 2, further comprising: Sending a second data request to the first internal network via the first device agent, the second data request is generated based on the first device and is used to request second target data about a third device; The third device is connected to the first data platform; The second data request is sent to the third device via the first internal network and a third device agent corresponding to the third device; The third device processes the second data request and returns the second target data; The second target data is sent to the first device via the third device agent, the first internal network and the first device agent.

7. The method according to claim 5, wherein, The first data request is a subscription request; further comprising: Judging whether there is a target data queue about the target data in the existing data queue of the second data platform; In response to the target data queue existing in the existing data queue, returning the target data queue to the open interconnect bus; and regularly adding updated data corresponding to the subscription request to the target data queue and sending it to the first device via the open interconnect bus; In response to the non - existence of the target data queue in the existing data queue, a target data queue is established, and it is retrieved whether the target data queue exists in the second data buffer; In response to the existence of the target data in the second data buffer, the target data is added to the target data queue and returned to the Open Connectivity Bus; In response to the non - existence of the target data in the second data buffer, the updated data corresponding to the subscription request is periodically added to the target data queue and sent to the first device via the Open Connectivity Bus; In response to receiving an unsubscribe request, the Open Connectivity Bus pauses the target data queue and returns the data in the target data queue to the second data buffer.

8. A data transmission device based on an Open Connectivity Bus, comprising: A bus receiving module, configured to receive, via a first platform agent, a first data request from a first data platform, where the first data request is used to request first target data about a second data platform; A bus sending module, configured to, in response to the first data request, send the first data request to the second data platform via a second platform agent; The bus receiving module is further configured to receive, via the second platform agent, the first target data from the second data platform for the first data request; The bus sending module is further configured to send the first target data to the first data platform via the first platform agent.

9. The device according to claim 8, wherein, The first data request is generated by a first device connected to the first data platform; The device further includes: a first device agent corresponding to the first device, configured to send the first data request to the first data platform via a first internal network of the first data platform.

10. The apparatus according to claim 9, wherein, The first platform agent is further configured to, in response to receiving the first target data, store the first target data in a first data buffer of the first data platform and send it to the first device agent via the first internal network.

11. The apparatus according to claim 8, further comprising: A second device agent, configured to receive the first data request from the second platform agent and send it to the corresponding second device, where the second device is connected to the second data platform; The second device is further configured to process the first data request and return the first target data.

12. The apparatus according to claim 11, wherein, The second platform agent is further configured to, in response to receiving the first data request, retrieve a second data buffer of the second data platform; The second data buffer is further configured to, in response to the existence of the first target data, return the first target data to the Open Connectivity Bus; The second data buffer is further configured to, in response to the non - existence of the first target data, send the first data request to the second device agent.

13. The apparatus according to claim 9, wherein, The first device agent is further configured to send a second data request to the first internal network, where the second data request is generated based on the first device and is used to request second target data about a third device; The third device is connected to the first data platform; The device further includes: A third device proxy corresponding to the third device, configured to receive the second data request from the first internal network and send it to the third device; The third device is further configured to process the second data request and return the second target data; The third device proxy is further configured to send the second target data to the first internal network and send it to the first device via the first device proxy.

14. The apparatus according to claim 12, wherein, The first data request is a subscription request; the apparatus further includes: A judgment module, configured to judge whether there is a target data queue for the target data in the existing data queue of the second data platform; A target queue module, configured to, in response to the existing data queue having the target data queue, return the target data queue to the open interconnection bus; and regularly add the updated data corresponding to the subscription request to the target data queue and send it to the first device via the open interconnection bus; The target queue module is further configured to, in response to the existing data queue not having the target data queue, establish a target data queue and retrieve whether the target data queue exists in the second data buffer; in response to the second data buffer having the target data, add the target data to the target data queue and return it to the open interconnection bus; and, in response to the second data buffer not having the target data, regularly add the updated data corresponding to the subscription request to the target data queue and send it to the first device via the open interconnection bus; The bus receiving module is further configured to, in response to receiving an unsubscribe request, suspend the target data queue and return the data in the target data queue to the second data buffer.

15. An electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor implements the method according to any one of claims 1 to 7 when executing the program.

16. A non-transitory computer-readable storage medium, where the non-transitory computer-readable storage medium stores computer instructions for causing a computer to execute the method according to any one of claims 1 to 7.

Images