Data transmission method and system for secure real-time bus (SRB)

By setting up physical channel isolation between real-time and non-real-time data between the CPU and the secure real-time bus interface device, the problem of real-time data transmission delay caused by resource contention is solved, the system structure is simplified, and the data transmission efficiency is improved.

CN121456930APending Publication Date: 2026-02-03北京傲星科技有限公司
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
CN202512037761.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2025-12-31
Publication Date
2026-02-03

AI Technical Summary

Technical Problem

In existing technologies, the competition for the single physical interface resource between the CPU and the SRB interface device leads to the inability to transmit real-time data in a timely manner, and the priority queue and shared interface increase the system complexity.

Method used

By setting up physical channel isolation between the central processing unit and the secure real-time bus interface device for real-time data and non-real-time data, real-time data and non-real-time data are sent through different physical channels, thus avoiding resource contention and eliminating the priority queue on the CPU side.

Benefits of technology

It enables timely transmission of real-time data, simplifies the SRB interface software, reduces latency, and improves system efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN121456930A_ABST
    Figure CN121456930A_ABST
Patent Text Reader

Abstract

The invention discloses a data transmission method and system for a secure real-time bus (SRB), and the method comprises the steps: enabling a central processing unit to transmit data to be transmitted to a secure real-time bus interface device through a real-time transmission type interface if the data to be transmitted belong to real-time data when the data needs to be transmitted through the secure real-time bus; the secure real-time bus interface device caches the current data to be transmitted to a real-time data queue, and sends the data to be transmitted in the real-time data queue to the secure real-time bus for transmission within the cycle time of the secure real-time bus; and if the to-be-transmitted data belongs to non-real-time data, sending the to-be-transmitted data to the safe real-time bus interface device through the standard Ethernet interface. And the secure real-time bus interface device caches the current data to be transmitted to the non-real-time data queue, and sends the data to be transmitted in the non-real-time data queue to the secure real-time bus for transmission within the non-periodic time of the secure real-time bus.
Need to check novelty before this filing date? Find Prior Art

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of secure real-time bus, and in particular to a data transmission method and system of a secure real-time bus (SRB). BACKGROUND

[0002] The link layer and the physical layer of a secure real-time bus (SRB) comply with the IEEE 802.3 Ethernet protocol specification. To cope with a strong real-time data transmission scenario, the SRB standard adopts a time division multiplexing manner to transmit real-time data on the secure real-time bus in a specific time slice, and to transmit non-real-time data in a non-specific time slice.

[0003] Currently, in order to enable a CPU to perform data transmission through the SRB, an SRB interface device is connected to the CPU through a physical interface, so that the CPU transmits data to the SRB interface device through the interface, and the SRB interface device sends the data to the SPB for transmission. In addition, in order to reduce the delay of data packet transmission, real-time data and non-real-time data are respectively stored in separate hardware caches, and a priority queue manner is used on the CPU side for data transmission in sequence, that is, several independent queues are set, and real-time data is arranged in a queue with a higher priority, so that real-time data can be preferentially transmitted to the SRB interface device, and the transmission time of real-time data between the CPU and the SRB interface device is reduced.

[0004] However, resource competition may occur between the CPU and the SRB interface device through the only physical interface. When non-real-time data is being transmitted through the interface, if real-time data is attempted to be transmitted, the interface resource will be busy and the real-time data needs to be waited for, resulting in that the real-time data cannot be transmitted to the SRB interface device in time, and cannot be transmitted through the SRB in time. In addition, the priority queue may cause additional delay due to the scheduling of the CPU and other hardware interrupts, and may also cause the real-time data to be unable to be transmitted in time. Furthermore, the shared physical interface cannot well adapt to the transmission of non-real-time data, and increases the complexity of the upper software. SUMMARY

[0005] Based on the deficiencies of the prior art, the present application provides a data transmission method and system of a secure real-time bus (SRB) to solve the problems that the prior art cannot transmit real-time data in time and increases the complexity of the system.

[0006] To achieve the above object, the present application provides the following technical solutions.

[0007] The first aspect of the present application provides a data transmission method of a secure real-time bus (SRB), comprising:

[0008] The central processor sends the current to-be-transmitted data to the secure real-time bus interface device through a real-time transmission type interface connected with the secure real-time bus interface device, if the current to-be-transmitted data belongs to real-time data;

[0009] The secure real-time bus interface device caches the current to-be-transmitted data into a real-time data queue;

[0010] The secure real-time bus interface device sends the to-be-transmitted data in the real-time data queue to the secure real-time bus within a cycle time of the secure real-time bus, so as to transmit the to-be-transmitted data through the secure real-time bus;

[0011] The central processor sends the current to-be-transmitted data to the secure real-time bus interface device through a standard Ethernet type interface connected with the secure real-time bus interface device, if the current to-be-transmitted data belongs to non-real-time data;

[0012] The secure real-time bus interface device caches the current to-be-transmitted data into a non-real-time data queue;

[0013] The secure real-time bus interface device sends the to-be-transmitted data in the non-real-time data queue to the secure real-time bus within a non-cycle time of the secure real-time bus, so as to transmit the to-be-transmitted data through the secure real-time bus.

[0014] Optionally, in the data transmission method of the secure real-time bus SRB, the central processor sends the current to-be-transmitted data to the secure real-time bus interface device through a real-time transmission type interface connected with the secure real-time bus interface device, and the method comprises the following steps of:

[0015] The central processor encapsulates the current to-be-transmitted data into a message format corresponding to the type of the to-be-transmitted data;

[0016] The central processor sends the message of the current to-be-transmitted data to the secure real-time bus interface device through an interface corresponding to the type of the to-be-transmitted data in a real-time transmission type interface connected with the secure real-time bus interface device; wherein the real-time transmission type interface at least comprises a CAN interface, an SPI interface, a QSPI interface and an EMIF interface.

[0017] Optionally, in the data transmission method of the secure real-time bus SRB, the central processor sends the current to-be-transmitted data to the secure real-time bus interface device through a standard Ethernet type interface connected with the secure real-time bus interface device, and the method comprises the following steps of:

[0018] The central processor encapsulates the current to-be-transmitted data as a TCP / IP packet or a raw Ethernet packet;

[0019] The central processor sends the packet of the current to-be-transmitted data to the secure real-time bus interface device through an interface corresponding to the type of the to-be-transmitted data in the standard Ethernet interface connected with the secure real-time bus interface device; and the real-time transmission interface at least includes an MII interface, an RMII interface, a GMII interface, and an RGMII interface.

[0020] Optionally, in the data transmission method of the secure real-time bus SRB, the method further includes:

[0021] When the secure real-time bus interface device monitors that the non-real-time data queue is filled in the period of time of the secure real-time bus, the secure real-time bus interface device informs the central processor of link layer collision through a CSMA / CD protocol packet.

[0022] The central processor stops sending data to the secure real-time bus interface device according to the received CSMA / CD protocol packet, and re-performs non-real-time data sending after waiting for a specified time.

[0023] Optionally, in the data transmission method of the secure real-time bus SRB, the central processor stops sending data to the secure real-time bus interface device according to the received CSMA / CD protocol packet, and re-performs non-real-time data sending after waiting for a specified time, including:

[0024] The central processor stops sending non-real-time data to the secure real-time bus interface device after receiving the CSMA / CD protocol packet.

[0025] The central processor re-starts non-real-time data sending after waiting for the current specified time.

[0026] The second aspect of the present application provides a data transmission system of a secure real-time bus SRB, including:

[0027] A central processor and a secure real-time bus interface device;

[0028] The central processor is configured to, when data needs to be transmitted through the secure real-time bus, if the current to-be-transmitted data belongs to real-time data, send the current to-be-transmitted data to the secure real-time bus interface device through a real-time transmission type interface connected to the secure real-time bus interface device, and if the current to-be-transmitted data belongs to non-real-time data, send the current to-be-transmitted data to the secure real-time bus interface device through a standard Ethernet type interface connected to the secure real-time bus interface device.

[0029] The secure real-time bus interface device is configured to cache the current to-be-transmitted data in a real-time data queue, and send the to-be-transmitted data in the real-time data queue to the secure real-time bus within a cycle time of the secure real-time bus, so as to transmit the to-be-transmitted data through the secure real-time bus, and cache the current to-be-transmitted data in a non-real-time data queue, and send the to-be-transmitted data in the non-real-time data queue to the secure real-time bus within a non-cycle time of the secure real-time bus, so as to transmit the to-be-transmitted data through the secure real-time bus.

[0030] Optionally, in the data transmission system of the secure real-time bus SRB, when the central processor sends the current to-be-transmitted data to the secure real-time bus interface device through the real-time transmission type interface connected to the secure real-time bus interface device, the central processor is configured to:

[0031] encapsulate the current to-be-transmitted data into a message format corresponding to the type of the to-be-transmitted data.

[0032] send the message of the current to-be-transmitted data to the secure real-time bus interface device through an interface corresponding to the type of the to-be-transmitted data in the real-time transmission type interface connected to the secure real-time bus interface device, wherein the real-time transmission type interface at least includes a CAN interface, an SPI interface, a QSPI interface, and an EMIF interface.

[0033] Optionally, in the data transmission system of the secure real-time bus SRB, when the central processor sends the current to-be-transmitted data to the secure real-time bus interface device through the standard Ethernet type interface connected to the secure real-time bus interface device, the central processor is configured to:

[0034] encapsulate the current to-be-transmitted data into a TCP / IP message or a raw Ethernet message.

[0035] The current message of the to-be-transmitted data is sent to the secure real-time bus interface device through an interface corresponding to the type of the to-be-transmitted data in a standard Ethernet interface connected with the secure real-time bus interface device; wherein the real-time transmission interface at least includes an MII interface, an RMII interface, a GMII interface, and an RGMII interface.

[0036] Optionally, in the above-mentioned data transmission system of the secure real-time bus SRB, the secure real-time bus interface device is further used for:

[0037] When it is monitored that the non-real-time data queue is filled in the period time of the secure real-time bus, a link layer collision is informed to the central processor through a CSMA / CD protocol message, so that the central processor stops sending data to the secure real-time bus interface device according to the received CSMA / CD protocol message, and re-performs non-real-time data sending after waiting for a specified time.

[0038] Optionally, in the above-mentioned data transmission system of the secure real-time bus SRB, when the central processor stops sending data to the secure real-time bus interface device according to the received CSMA / CD protocol message, and re-performs non-real-time data sending after waiting for a specified time, it is used for:

[0039] After receiving the CSMA / CD protocol message, the sending of non-real-time data to the secure real-time bus interface device is stopped;

[0040] After waiting for the current specified time, the sending of non-real-time data is restarted.

[0041] The application provides a data transmission method of a safety real-time bus (SRB). A corresponding physical channel is arranged between a central processing unit and a safety real-time bus interface device. Therefore, when the central processing unit needs to transmit data through the safety real-time bus, if the current to-be-transmitted data belongs to real-time data, the central processing unit sends the current to-be-transmitted data to the safety real-time bus interface device through a real-time transmission type interface connected with the safety real-time bus interface device. The safety real-time bus interface device caches the current to-be-transmitted data into a real-time data queue. The safety real-time bus interface device sends the to-be-transmitted data in the real-time data queue to the safety real-time bus within a cycle time of the safety real-time bus, so as to transmit the to-be-transmitted data through the safety real-time bus. If the current to-be-transmitted data belongs to non-real-time data, the central processing unit sends the current to-be-transmitted data to the safety real-time bus interface device through a standard Ethernet type interface connected with the safety real-time bus interface device. The safety real-time bus interface device caches the current to-be-transmitted data into a non-real-time data queue. The safety real-time bus interface device sends the to-be-transmitted data in the non-real-time data queue to the safety real-time bus within a non-cycle time of the safety real-time bus, so as to transmit the to-be-transmitted data through the safety real-time bus. Therefore, the physical channel isolation of real-time data and non-real-time data between the CPU and the SRB interface device is adopted, and the real-time data and the non-real-time data are sent through different physical channels, so that the non-real-time data and the real-time data transmission do not affect each other due to resource competition. Moreover, a priority queue does not need to be arranged on the CPU side, so as to avoid causing additional delay. Moreover, the non-real-time data is transmitted through the Ethernet, so that the SRB interface software is more simple and efficient. BRIEF DESCRIPTION OF DRAWINGS

[0042] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings needed to be used in the embodiments or prior art description. Obviously, the drawings in the following description only constitute the embodiments of the present application, and for those skilled in the art, other drawings can also be obtained without creative labor on the basis of the provided drawings.

[0043] Figure 1 A flow chart of a data transmission method of a safety real-time bus (SRB) provided by the embodiments of the present application;

[0044] Figure 2 A flow chart of a method for transmitting real-time data to a safety real-time bus interface device provided by the embodiments of the present application;

[0045] Figure 3 An architecture schematic diagram of a central processing unit and a safety real-time bus interface device provided by the embodiments of the present application;

[0046] Figure 4A flow chart of a method for transmitting non-real-time data to a secure real-time bus interface device according to an embodiment of the present application is provided.

[0047] Figure 5 A flow chart of a non-real-time data transmission management method according to an embodiment of the present application is provided.

[0048] Figure 6 A flow chart of a non-real-time data suspension and resumption method according to an embodiment of the present application is provided.

[0049] Figure 7 An architecture diagram of a secure real-time bus (SRB) data transmission system according to an embodiment of the present application is provided. DETAILED DESCRIPTION

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

[0051] In the present application, the relationship terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply that there is any such actual relationship or order between these entities or operations. Moreover, the terms “include”, “contain” or any other variants thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements not only includes those elements, but also includes other elements not explicitly listed or inherent to such process, method, article or device. Without more limitations, the element defined by the statement “including a…” does not exclude the presence of another identical element in the process, method, article or device including the element.

[0052] The embodiments of the present application provide a secure real-time bus (SRB) data transmission method, as shown in Figure 1 The method comprises the following steps.

[0053] In S101, the central processor determines that data needs to be transmitted through the secure real-time bus.

[0054] Specifically, the central processor generates data to be transmitted in the working process, and some data needs to be transmitted through the secure real-time bus. Therefore, it is determined that the data needs to be transmitted through the secure real-time bus to be sent to the secure real-time bus interface device. That is, whenever data needs to be transmitted through the secure real-time bus, step S102 is executed.

[0055] S102, the central processor determines whether the current to-be-transmitted data to be transmitted through the secure real-time bus is real-time data.

[0056] It should be noted that in the embodiment of the present application, the physical channel isolation between the central processor and the secure real-time bus interface device is adopted for real-time data and non-real-time data, so it is necessary to determine whether the current to-be-transmitted data to be transmitted through the secure real-time bus is real-time data or non-real-time data, so as to be transmitted through the corresponding physical channel.

[0057] If the current to-be-transmitted data belongs to real-time data, step S103 is executed. If the current to-be-transmitted data belongs to non-real-time data, step S106 is executed.

[0058] S103, the central processor sends the current to-be-transmitted data to the secure real-time bus interface device through a real-time transmission type interface connected with the secure real-time bus interface device.

[0059] The real-time transmission type interface is an interface of a type supporting transmission of real-time data, and can include a plurality of types.

[0060] Since the current to-be-transmitted data is real-time data, the central processor sends the current to-be-transmitted data to the secure real-time bus interface device through a real-time transmission type interface connected with the secure real-time bus interface device, without the need for queuing.

[0061] Optionally, in another embodiment of the present application, a specific implementation of step S103 includes, as shown in Figure 2 , comprising:

[0062] S201, the central processor encapsulates the current to-be-transmitted data into a message format corresponding to the type thereof.

[0063] It should be noted that in the embodiment of the present application, the real-time transmission type interface can include a plurality of different interfaces, and can include but is not limited to CAN interface, SPI interface, QSPI interface, and EMIF interface. Therefore, in order to transmit the current to-be-transmitted data to the secure real-time bus interface device through a corresponding real-time transmission type interface, it is necessary to encapsulate the current to-be-transmitted data into a message format corresponding to the type thereof.

[0064] S202, the central processor sends the message of the current to-be-transmitted data to the secure real-time bus interface device through an interface corresponding to the type of the to-be-transmitted data in the real-time transmission type interface connected with the secure real-time bus interface device.

[0065] Since the formats of the to-be-transmitted data and the transmission requirements can be different, an interface corresponding to the type of the to-be-transmitted data in the real-time transmission type interface needs to be selected for transmission.

[0066] In S104, the current to-be-transmitted data is buffered into the real-time data queue by the secure real-time bus interface device.

[0067] It should be noted that, since the real-time data and the non-real-time data are physically separated, when the central processor needs to send data through the secure real-time bus, the to-be-transmitted data can be directly transmitted to the secure real-time bus interface device through the corresponding interface, and there is no need to set a priority queue on the central processor side.

[0068] However, since the real-time data needs to be sent to the secure real-time bus within a period of time, the data transmitted to the secure real-time bus interface device can not be immediately transmitted, and in order to orderly transmit the to-be-transmitted data, a real-time data queue is set for the real-time data on the secure real-time bus interface device side in the embodiment of the present application, so that when the current to-be-transmitted data is received, it is buffered into the real-time data queue first.

[0069] Optionally, the real-time data queue can be a first-in-first-out queue, so that the to-be-transmitted data can be transmitted to the secure real-time bus in order according to the order in which the to-be-transmitted data is received.

[0070] In S105, the to-be-transmitted data in the real-time data queue is transmitted to the secure real-time bus by the secure real-time bus interface device within the period of time of the secure real-time bus, so as to transmit the to-be-transmitted data through the secure real-time bus.

[0071] It should be noted that the real-time data is transmitted within the period of time of the secure real-time bus, and the period of time is equally divided according to the macro period, and the real-time data is transmitted within the period of time slice in each macro period. Therefore, the secure real-time bus interface device transmits the to-be-transmitted data in the real-time data queue FRT_FIFO to the secure real-time bus through the SRB communication scheduling management entity (SRB communication scheduling management entity, SRB_CSME) within the period of time of the secure real-time bus, so as to transmit the to-be-transmitted data through the secure real-time bus.

[0072] Therefore, specifically, as Figure 3As shown, when the central processor needs to transmit real-time data, it transmits the real-time data to the secure real-time bus interface device through a CAN interface, an SPI interface, a QSPI interface, an EMIF interface, etc. The secure real-time bus interface device buffers the real-time data in a real-time data queue FRT_FIFO. Finally, within a period of time, the secure real-time bus interface device sends the real-time data in the FRT_FIFO to the secure real-time bus through an SRB_CSME for transmission.

[0073] S106, the central processor sends the current data to be transmitted to the secure real-time bus interface device through a standard Ethernet interface connected to the secure real-time bus interface device.

[0074] It should be noted that, since physical channel isolation of real-time data and non-real-time data is adopted between the CPU and the SRB interface device, an interface for transmitting non-real-time data is separately provided. Therefore, the non-real-time data is transmitted through the standard Ethernet interface, thereby avoiding unnecessary complexity for the upper software implementation. Alternatively, the standard Ethernet interface can be provided with multiple interfaces, so that various types of non-real-time data can be transmitted.

[0075] Therefore, when the central processor needs to transmit non-real-time data through the secure real-time bus, it directly sends the current data to be transmitted to the secure real-time bus interface device through a standard Ethernet interface connected to the secure real-time bus interface device, and no longer needs to set a priority queue in the central processor for buffering.

[0076] Alternatively, in another embodiment of the present application, a specific implementation of step S106 includes: Figure 4 As shown, it includes:

[0077] S401, the central processor encapsulates the current data to be transmitted into a TCP / IP packet or a raw Ethernet packet.

[0078] Specifically, the current data to be transmitted can be encapsulated into a TCP / IP packet or a raw Ethernet packet according to the format of the current data to be transmitted.

[0079] S402, the central processor sends the packet of the current data to be transmitted to the secure real-time bus interface device through an interface corresponding to the type of the data to be transmitted in the standard Ethernet interface connected to the secure real-time bus interface device.

[0080] The real-time transmission interface can include but is not limited to an MII interface, an RMII interface, a GMII interface, an RGMII interface, etc. The central processor sends the packet of the current data to be transmitted to the secure real-time bus interface device through an interface corresponding to the data to be transmitted.

[0081] S107, the secure real-time bus interface device buffers the current data to be transmitted into the non-real-time data queue.

[0082] Similarly, non-real-time data needs to be transmitted outside of the cycle time. Therefore, non-real-time data transmitted to the secure real-time bus interface device may not be transmitted immediately through the secure real-time bus. In order to transmit non-real-time data in an orderly manner, a non-real-time data queue is set up so that the received data to be transmitted can be buffered in the non-real-time data queue.

[0083] Similarly, the non-real-time data queue can be a first-in-first-out queue, so that the non-real-time data can be sent to the secure real-time bus for transmission in the order in which it is received.

[0084] Optionally, considering that non-real-time data has relatively low importance and may not be able to effectively meet the transmission requirements of non-real-time data, resulting in queue fullness, another embodiment of this application may further include a non-real-time data transmission management method, such as... Figure 5 As shown, it includes:

[0085] When the S501 secure real-time bus interface device detects that the non-real-time data queue is full during the periodic time of the secure real-time bus, it notifies the central processing unit of a link layer collision via a CSMA / CD protocol message.

[0086] Since real-time data is transmitted during the periodic time of the Secure Real-Time Bus, non-real-time data cannot be transmitted. Therefore, the non-real-time data queue will not decrease after it is full, and it cannot buffer newly transmitted non-real-time data. To avoid loss of non-real-time data, the CPU is notified of a link layer collision via a CSMA / CD protocol message to suspend the transmission of non-real-time data from the CPU to the Secure Real-Time Bus interface device.

[0087] S502: The central processing unit stops sending data to the secure real-time bus interface device according to the received CSMA / CD protocol message, and resumes non-real-time data transmission after waiting for a specified time.

[0088] It should be noted that, since the non-real-time data queue can no longer buffer non-real-time data at this point, the central processing unit stops sending data to the secure real-time bus interface device. After waiting for a certain period of time, the non-periodic time will begin, during which data in the non-real-time data queue will be transmitted. Since the queue is no longer full, non-real-time data transmission will resume at this time.

[0089] The specified time is a fixed time according to the transmission protocol. Optionally, the CSMA / CD protocol is processed by the Ethernet MAC hardware, and the retransmission interval follows its standard. Therefore, the specified time can be the time interval specified by the 802.3 protocol, that is, retransmitting non-real-time data packets according to the time interval specified by the 802.3 protocol.

[0090] Optionally, in another embodiment of this application, one specific implementation of step S502 is as follows: Figure 6 As shown, it includes:

[0091] S601: After receiving a CSMA / CD protocol message, the central processing unit stops sending data to the secure real-time bus interface device.

[0092] S602: After waiting for the specified time, the central processing unit restarts the transmission of non-real-time data.

[0093] The specified time is a fixed time according to the transmission protocol. Optionally, it can be the time interval specified by the 802.3 protocol, that is, retransmitting non-real-time data packets according to the time interval specified by the 802.3 protocol.

[0094] S108, the secure real-time bus interface device sends the data to be transmitted from the non-real-time data queue to the secure real-time bus during the non-periodic time of the secure real-time bus, so as to transmit the data to be transmitted through the secure real-time bus.

[0095] Specifically, during the non-periodic time of the secure real-time bus, the secure real-time bus interface device sends the data to be transmitted in the non-real-time data queue to the secure real-time bus in an orderly manner through SRB_CSME, so as to transmit the data to be transmitted through the secure real-time bus.

[0096] Therefore, similarly, as Figure 3 As shown, when the central processing unit (CPU) needs to transmit non-real-time data, it transmits the non-real-time data to the secure real-time bus interface device via interfaces such as MII, RMII, GMII, and RGMII. The secure real-time bus interface device buffers the non-real-time data in the non-real-time data queue NRT_FIFO. Finally, during non-cycle time, the secure real-time bus interface device sends the non-real-time data in NRT_FIFO to the secure real-time bus for transmission via SRB_CSME.

[0097] This application provides a data transmission method for a Secure Real-Time Bus (SRB). A corresponding physical channel is established between the central processing unit (CPU) and the SRB interface device. Therefore, whenever the CPU needs to transmit data via the SRB, if the data to be transmitted is real-time data, the CPU sends the data to the SRB interface device through a real-time transmission interface connected to the SRB interface device. The SRB interface device buffers the data to be transmitted in a real-time data queue. During the SRB's periodic time, the SRB interface device sends the data to be transmitted from the real-time data queue to the SRB to transmit the data. If the data to be transmitted is non-real-time data, the CPU sends the data to the SRB interface device through a standard Ethernet interface connected to the SRB interface device. The SRB interface device buffers the data to be transmitted in a non-real-time data queue. During the SRB's non-periodic time, the SRB interface device sends the data to be transmitted from the non-real-time data queue to the SRB to transmit the data. This approach employs physical channel isolation between the CPU and the SRB interface device, separating real-time and non-real-time data transmission. Real-time and non-real-time data are sent through separate physical channels, preventing resource contention from interfering with each other. Furthermore, it eliminates the need for priority queues on the CPU side, avoiding additional latency. Moreover, transmitting non-real-time data via Ethernet makes the SRB interface software simpler and more efficient.

[0098] Another embodiment of this application provides a data transmission system for a Secure Real-Time Bus (SRB), such as... Figure 7 As shown, it includes:

[0099] Central processing unit 701 and secure real-time bus interface device 702.

[0100] The central processing unit 701 is used to send data to the secure real-time bus interface device through a real-time transmission interface connected to the secure real-time bus interface device whenever data needs to be transmitted via the secure real-time bus. If the data to be transmitted is real-time data, the central processing unit sends the data to be transmitted through a standard Ethernet interface connected to the secure real-time bus interface device.

[0101] The secure real-time bus interface device 702 is used to buffer the current data to be transmitted into the real-time data queue, and send the data to be transmitted in the real-time data queue to the secure real-time bus during the period of the secure real-time bus, so as to transmit the data to be transmitted through the secure real-time bus; and to buffer the current data to be transmitted into the non-real-time data queue, and send the data to be transmitted in the non-real-time data queue to the secure real-time bus during the non-periodic period of the secure real-time bus, so as to transmit the data to be transmitted through the secure real-time bus.

[0102] Optionally, in the data transmission system of the Secure Real-Time Bus (SRB) provided in another embodiment of this application, when the central processing unit sends the current data to be transmitted to the Secure Real-Time Bus interface device through a real-time transmission interface connected to the Secure Real-Time Bus interface device, it is used to:

[0103] Encapsulate the data to be transmitted into a message format corresponding to its type.

[0104] The message of the data to be transmitted is sent to the secure real-time bus interface device via the interface corresponding to the type of data to be transmitted in the real-time transmission class interface connected to the secure real-time bus interface device. The real-time transmission class interfaces include at least CAN, SPI, QSPI, and EMIF interfaces.

[0105] Optionally, in the data transmission system of the Secure Real-Time Bus (SRB) provided in another embodiment of this application, when the central processing unit sends the current data to be transmitted to the SRB interface device through a standard Ethernet interface connected to the SRB interface device, it is used to:

[0106] Encapsulate the current data to be transmitted into a TCP / IP packet or a raw Ethernet packet.

[0107] The message containing the data to be transmitted is sent to the secure real-time bus interface device via the interface corresponding to the type of data to be transmitted in the standard Ethernet class interface connected to the secure real-time bus interface device. The real-time transmission class interfaces include at least the MII interface, RMII interface, GMII interface, and RGMII interface.

[0108] Optionally, in a data transmission system of the Secure Real-Time Bus (SRB) provided in another embodiment of this application, the Secure Real-Time Bus interface device is further used for:

[0109] When the non-real-time data queue is detected to be full during the periodic time of the secure real-time bus, a link layer collision is notified to the central processing unit via a CSMA / CD protocol message. The central processing unit then stops sending data to the secure real-time bus interface device according to the received CSMA / CD protocol message and resumes sending non-real-time data after waiting for a specified time.

[0110] Optionally, in the data transmission system of the Secure Real-Time Bus (SRB) provided in another embodiment of this application, when the central processing unit stops sending data to the SRB interface device according to the received CSMA / CD protocol message, and resumes non-real-time data transmission after waiting for a specified time, it is used for:

[0111] Upon receiving a CSMA / CD protocol message, the transmission of non-real-time data to the secure real-time bus interface device is stopped.

[0112] After waiting for the specified time, resume sending non-real-time data.

[0113] It should be noted that the specific working process of each unit provided in the above embodiments of this application can be referred to the implementation process of the corresponding steps in the above method embodiments, and will not be repeated here.

[0114] Computer storage media, including both permanent and non-permanent, removable and non-removable media, can store information using any method or technology. 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, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0115] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0116] The above description of the disclosed embodiments enables those skilled in the art to make or use this application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this application. Therefore, this application is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A data transmission method for a Secure Real-Time Bus (SRB), characterized in that, include: Whenever the central processing unit needs to transmit data through the secure real-time bus, if the data to be transmitted is real-time data, the central processing unit sends the data to be transmitted to the secure real-time bus interface device through a real-time transmission interface connected to the secure real-time bus interface device. The secure real-time bus interface device caches the current data to be transmitted into the real-time data queue; The secure real-time bus interface device sends the data to be transmitted in the real-time data queue to the secure real-time bus during the period of the secure real-time bus, so as to transmit the data to be transmitted through the secure real-time bus. If the data to be transmitted is non-real-time data, the central processing unit sends the data to be transmitted to the secure real-time bus interface device through a standard Ethernet interface connected to the secure real-time bus interface device. The secure real-time bus interface device buffers the current data to be transmitted into a non-real-time data queue; The secure real-time bus interface device sends the data to be transmitted from the non-real-time data queue to the secure real-time bus during the non-periodic time of the secure real-time bus, so as to transmit the data to be transmitted through the secure real-time bus.

2. The method according to claim 1, characterized in that, The central processing unit sends the current data to be transmitted to the secure real-time bus interface device via a real-time transmission interface connected to the secure real-time bus interface device, including: The central processing unit encapsulates the current data to be transmitted into a message format corresponding to its type. The central processing unit sends the current data to be transmitted to the secure real-time bus interface device through the interface corresponding to the type of data to be transmitted in the real-time transmission class interface connected to the secure real-time bus interface device; wherein, the real-time transmission class interface includes at least a CAN interface, an SPI interface, a QSPI interface, and an EMIF interface.

3. The method according to claim 1, characterized in that, The central processing unit sends the current data to be transmitted to the secure real-time bus interface device via a standard Ethernet interface connected to the secure real-time bus interface device, including: The central processing unit encapsulates the current data to be transmitted into a TCP / IP packet or a raw Ethernet packet; The central processing unit sends the current data to be transmitted to the secure real-time bus interface device through the interface corresponding to the type of data to be transmitted in the standard Ethernet class interface connected to the secure real-time bus interface device; wherein, the real-time transmission class interface includes at least MII interface, RMII interface, GMII interface, and RGMII interface.

4. The method according to claim 1, characterized in that, Also includes: When the secure real-time bus interface device detects that the non-real-time data queue is full during the periodic time of the secure real-time bus, it notifies the central processing unit of a link layer collision via a CSMA / CD protocol message. The central processing unit stops sending data to the secure real-time bus interface device according to the received CSMA / CD protocol message, and resumes non-real-time data transmission after waiting for a specified time.

5. The method according to claim 4, characterized in that, The central processing unit, according to the received CSMA / CD protocol message, stops sending data to the secure real-time bus interface device, and resumes non-real-time data transmission after waiting for a specified time, including: After receiving the CSMA / CD protocol message, the central processing unit stops sending non-real-time data to the secure real-time bus interface device. After waiting for the specified time, the central processing unit restarts the transmission of non-real-time data.

6. A data transmission system for a Secure Real-Time Bus (SRB), characterized in that, include: Central processing unit and secure real-time bus interface device; The central processing unit (CPU) is configured to, whenever data needs to be transmitted via the secure real-time bus, send the data to be transmitted to the secure real-time bus interface device via a real-time transmission interface connected to the secure real-time bus interface device if the data to be transmitted is real-time data, and send the data to be transmitted to the secure real-time bus interface device via a standard Ethernet interface connected to the secure real-time bus interface device if the data to be transmitted is non-real-time data. The secure real-time bus interface device is configured to cache the current data to be transmitted in a real-time data queue, and send the data to be transmitted in the real-time data queue to the secure real-time bus during the periodic time of the secure real-time bus, so as to transmit the data to be transmitted through the secure real-time bus; and to cache the current data to be transmitted in a non-real-time data queue, and send the data to be transmitted in the non-real-time data queue to the secure real-time bus during the non-periodic time of the secure real-time bus, so as to transmit the data to be transmitted through the secure real-time bus.

7. The system according to claim 6, characterized in that, When the central processing unit sends the current data to be transmitted to the secure real-time bus interface device via a real-time transmission interface connected to the secure real-time bus interface device, it is used for: Encapsulate the current data to be transmitted into a message format corresponding to its type; The message of the data to be transmitted is sent to the secure real-time bus interface device through the interface corresponding to the type of data to be transmitted in the real-time transmission class interface connected to the secure real-time bus interface device; wherein, the real-time transmission class interface includes at least a CAN interface, an SPI interface, a QSPI interface, and an EMIF interface.

8. The system according to claim 6, characterized in that, When the central processing unit sends the current data to be transmitted to the secure real-time bus interface device via a standard Ethernet interface connected to the secure real-time bus interface device, it is used for: Encapsulate the data to be transmitted into a TCP / IP packet or a raw Ethernet packet; The current data to be transmitted is sent to the secure real-time bus interface device via the interface corresponding to the type of data to be transmitted in the standard Ethernet class interface connected to the secure real-time bus interface device; wherein, the real-time transmission class interface includes at least MII interface, RMII interface, GMII interface, and RGMII interface.

9. The system according to claim 6, characterized in that, The secure real-time bus interface device is also used for: When the non-real-time data queue is detected to be full during the periodic time of the secure real-time bus, the central processing unit is notified of a link layer collision via a CSMA / CD protocol message. The central processing unit then stops sending data to the secure real-time bus interface device according to the received CSMA / CD protocol message and resumes non-real-time data transmission after a specified waiting time.

10. The system according to claim 9, characterized in that, When the central processing unit stops sending data to the secure real-time bus interface device according to the received CSMA / CD protocol message, and resumes non-real-time data transmission after waiting for a specified time, it is used to: Upon receiving a CSMA / CD protocol message, the transmission of non-real-time data to the secure real-time bus interface device is stopped. After waiting for the specified time, resume sending non-real-time data.

Citation Information

Patent Citations

  • Method and interface for high-speed communication on bus

    CN101483646A

  • Industrial Internet field layer broadband bus architecture system

    CN106209542A

  • Development board based on SRB chip

    CN119828531A

  • Data transmission control method and device of SRB, electronic equipment and storage medium

    CN120602257A

  • [interface and system for transmitting real-time data ]

    US20050268019A1