CN114640703A

CN114640703A - Data communication method and device, electronic equipment and storage medium

Info

Publication number: CN114640703A
Application number: CN202210244972.XA
Authority: CN
Inventors: 刘昕; 郑红丽; 刘朝阳; 蔡旭
Original assignee: FAW Group Corp
Current assignee: FAW Group Corp
Priority date: 2022-03-14
Filing date: 2022-03-14
Publication date: 2022-06-17

Abstract

The embodiment of the invention discloses a data communication method, a data communication device, electronic equipment and a storage medium. The method is executed by a Micro Control Unit (MCU) and comprises the following steps: responding to an MCU starting instruction, powering on an SOC (system on chip), and sending a first request message to the MCU after the SOC is powered on; receiving a first request message sent by the SOC, finishing handshaking with the SOC according to a preset MCU handshaking message confirmation rule, and establishing communication connection; and sending message data to the SOC based on the established communication connection according to a preset message type and a message sending rule so as to complete data communication. Through the confirmation of the handshake message and the preset message type and sending rule, the reliability of data communication between the two parties is ensured, and the communication efficiency and safety are improved.

Description

Data communication method and device, electronic equipment and storage medium

Technical Field

The embodiment of the invention relates to the technical field of communication, in particular to a data communication method, a data communication device, electronic equipment and a storage medium.

Background

In an automobile electronic System, an MCU (micro Controller Unit) and an SOC (System on Chip) Chip exist, and the MCU may be responsible for receiving and processing signals such as an automobile CAN (Controller Area Network), a Local Interconnect Network (LIN), a power supply, and the like, and transmitting the signals to the SOC for interface display and sound production, and the like.

The communication between the MCU and the SOC chip is an important module for data transmission, and the communication mode is SPI (Serial Peripheral Interface) or UART (Universal Asynchronous Receiver/Transmitter) communication. During communication, the MCU periodically sends message messages to the SOC, and the message messages can be sent as long as the periodic condition is met, so that the communication reliability and the transmission efficiency are low.

Disclosure of Invention

The embodiment of the invention provides a data communication method, a data communication device, electronic equipment and a storage medium, and aims to improve the reliability and efficiency of data communication.

According to an aspect of the present invention, there is provided a method of data communication, the method being performed by a Micro Control Unit (MCU), the method comprising:

responding to an MCU starting instruction, powering on an SOC (system on chip), and sending a first request message to the MCU after the SOC is powered on;

receiving a first request message sent by the SOC, finishing handshaking with the SOC according to a preset MCU handshaking message confirmation rule, and establishing communication connection;

and sending message data to the SOC based on the established communication connection according to a preset message type and a message sending rule so as to complete data communication.

According to another aspect of the present invention, there is provided a method of data communication, the method being performed by a system on chip SOC, the method comprising:

starting the SOC according to the power-on operation of the MCU on the SOC, and sending a first request message to the MCU;

finishing handshaking with the MCU according to a preset SOC handshaking message confirmation rule, and establishing communication connection;

and receiving the message data sent by the MCU according to the established communication connection so as to complete data communication.

According to another aspect of the present invention, there is provided a data communication apparatus configured to a MCU, the apparatus including:

the SOC power-on module is used for responding to an MCU starting instruction, powering on the SOC, and sending a first request message to the MCU after the SOC is powered on;

the handshake message confirmation module is used for receiving a first request message sent by the SOC, finishing handshake with the SOC according to a preset MCU handshake message confirmation rule, and establishing communication connection;

and the message data sending module is used for sending message data to the SOC based on the established communication connection according to the preset message type and the message sending rule so as to complete data communication.

According to another aspect of the present invention, there is provided an apparatus for data communication, the apparatus being configured in a system on chip SOC, the apparatus comprising:

the first request message sending module is used for starting the SOC according to the power-on operation of the MCU on the SOC and sending a first request message to the MCU;

the communication connection establishing module is used for finishing handshaking with the MCU according to a preset SOC handshaking message confirmation rule and establishing communication connection;

and the message data receiving module is used for receiving the message data sent by the MCU according to the established communication connection so as to complete data communication.

According to another aspect of the present invention, there is provided an electronic apparatus including:

at least one processor; and

a memory communicatively coupled to the at least one processor; wherein the content of the first and second substances,

the memory stores a computer program executable by the at least one processor, the computer program being executable by the at least one processor to enable the at least one processor to perform the method of data communication as described in the embodiments of the first or second aspect of the invention.

According to another aspect of the present invention, there is provided a computer-readable storage medium storing computer instructions for causing a processor to implement a method of data communication as described in embodiments of the first or second aspect of the present invention when executed.

According to the technical scheme of the embodiment of the invention, the SOC is electrified through the MCU, and the SOC sends the first request message to the MCU after being electrified to perform handshaking. And the MCU completes handshaking with the SOC according to a preset handshaking message confirmation rule and establishes reliable communication connection. Different message types and message sending rules can be preset, and for different message types, the MCU and the SOC can transmit message data through the established communication connection, so that the requirements on different services are met. The problems that in the prior art, data with a fast period occupy communication resources and data with a slow period cannot be updated in time are solved, and the diversity of message types is improved. And through the handshake message, the reliability of transmission is ensured, and the efficiency and the precision of message transmission are improved.

It should be understood that the statements in this section do not necessarily identify key or critical features of the embodiments of the present invention, nor do they necessarily limit the scope of the invention. Other features of the present invention will become apparent from the following description.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

Fig. 1 is a flowchart illustrating a method for data communication according to an embodiment of the present invention;

fig. 2 is a schematic diagram of a message format of message data according to an embodiment of the present invention;

fig. 3 is a flowchart illustrating a method for data communication according to a second embodiment of the present invention;

fig. 4 is a flowchart illustrating a method for data communication according to a third embodiment of the present invention;

fig. 5 is a schematic structural diagram of a data communication apparatus according to a fourth embodiment of the present invention;

fig. 6 is a schematic structural diagram of a data communication apparatus according to a fifth embodiment of the present invention;

fig. 7 is a schematic structural diagram of an electronic device implementing a method of data communication according to an embodiment of the present invention.

Detailed Description

In order to make the technical solutions of the present invention better understood, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be obtained by a person skilled in the art without making any creative effort based on the embodiments in the present invention, shall fall within the protection scope of the present invention.

It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the invention described herein are capable of operation in sequences other than those illustrated or described herein. Moreover, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

Example one

Fig. 1 is a flowchart illustrating a method for data communication according to an embodiment of the present invention, where the embodiment is applicable to a case of controlling inter-chip data communication, and the method may be performed by a device for data communication, where the device may be implemented in a form of hardware and/or software, and the device may be configured on an MCU. As shown in fig. 1, the method includes:

s110, responding to the MCU starting instruction, electrifying the SOC, and sending a first request message to the MCU after the SOC is electrified.

The data from the MCU to the SOC are uplink data, and the data from the SOC to the MCU are downlink data. Taking an instrument system as an example, the MCU is responsible for receiving signals of a CAN, a LIN, a power supply, an IO and the like of a vehicle, carrying out certain processing, then sending the processed data to the SOC through SPI or UART communication, and carrying out interface display or sound alarm processing and the like on the data received by the SOC. For systems with higher functional safety requirements such as instruments and the like, the reliability and the transmission efficiency of the communication between the SPI/UART chips are of great importance.

The MCU can be sent with a starting instruction firstly, the starting instruction can be sent manually by a user, and the starting instruction can also be sent at regular time according to preset starting time. And after the MCU is started, the SOC is electrified, and the SOC is started. After the SOC is started, a preset first request message may be sent to the MCU within a preset time, where the first request message is a request message sent by the SOC first in a handshaking process, that is, may be a handshaking request message.

And S120, receiving a first request message sent by the SOC, finishing handshaking with the SOC according to a preset MCU handshaking message confirmation rule, and establishing communication connection.

The MCU can be preset with MCU handshake message confirmation rules, and the MCU handshake message confirmation rules can be used for determining whether the MCU completes handshake with the SOC. For example, the MCU handshake message confirmation rule may be that, in the handshake process, it is determined whether the first request message sent from the received SOC is a preset handshake request message, and if so, it is determined that the handshake process is correct; if not, determining that the handshake process is abnormal. For another example, the MCU handshake message confirmation rule may be that it is determined whether the MCU receives the first request message sent by the SOC within a preset time, and if so, it is determined that the handshake process is correct; if not, determining that the handshake process is abnormal. And the MCU receives a first request message sent by the SOC, determines whether to correctly handshake with the SOC according to the MCU handshake message confirmation rule, and if so, completes the handshake process and establishes normal communication connection with the SOC. If the handshake is not completed, the first request message of the SOC may be acquired again, and the handshake continues.

In this embodiment, optionally, the receiving a first request message sent by the SOC, completing handshake with the SOC according to a preset MCU handshake message confirmation rule, and establishing a communication connection includes: receiving a first request message sent by the SOC, and judging whether the current request message is a handshake request message or not; if yes, sending a first reply message to the SOC, and enabling the SOC to send a second request message after determining that the first reply message is a handshake reply message; receiving a second request message sent by the SOC, and judging whether the second request message is a handshake completion message; if yes, determining that the MCU and the SOC complete handshaking, and establishing communication connection.

Specifically, the MCU receives a first request message sent by the SOC, and determines whether the first request message is a preset handshake request message. If not, according to a preset request message acquisition period, periodically acquiring a new first request message from the SOC until the acquired first request message is a handshake request message. And if the first request message is a handshake request message, the MCU sends a first reply message to the SOC. The first reply message is a message for replying to the handshake request message, that is, may be a handshake reply message.

The SOC is pre-stored with an SOC handshake message confirmation rule, and the SOC handshake message confirmation rule can be used for determining whether the SOC receives a handshake reply message sent by the MCU. After receiving the first reply message, the SOC determines whether the first reply message is a preset handshake reply message according to the SOC handshake message confirmation rule, and if not, the SOC continuously sends a first request message to the MCU; and if so, sending a second request message to the MCU. The second request message is a second request message sent by the SOC during the message process, that is, a handshake completion message. And the MCU receives the second request message, and determines whether the second request message is a preset handshake completion message according to a preset MCU handshake message confirmation rule. That is, the MCU handshake message confirmation rule may be used to determine whether the first request message is a handshake request message, or may be used to determine whether the second request message is a handshake completion message. If the second request message is a handshake completion message, the MCU and the SOC complete handshake, and reliable communication connection is established between the MCU and the SOC.

The method has the advantages that reliable connection between the MCU and the SOC is ensured through the three-way handshaking mode, the three-way handshaking message is only sent at the initial starting stage, and the handshaking message is not sent after the handshaking is successful. The SOC end initiates a handshake request after the service is started, the MCU end replies the handshake request, the SOC sends a handshake completion message after receiving the reply, and the SOC and the MCU establish reliable connection. And the handshake message is in a single-sending mode, the MCU can monitor the handshake state, if the handshake cannot be completed within a certain time, the SOC communication service can be restarted and the handshake is initiated again, so that the establishment of normal communication connection is ensured, the reliability and high availability of communication data are ensured, and the efficiency and precision of data transmission are improved.

And S130, sending message data to the SOC based on the established communication connection according to the preset message type and the message sending rule so as to complete data communication.

Different message types are preset, and the message types can include a handshake message, a periodic message, an event message, a periodic event message and a response message. Different types of messages may correspond to different message sending rules, and the message sending rules may include sending time and message format of the message. For example, the handshake message is sent only at the initial stage of system start; the periodic message is sent once every preset period; the event type message is sent once every time a preset event is triggered. The message type of each service data during communication can be preset, that is, the initial message type of the data can be configured according to the condition of the service data. And when data is sent, determining the message type according to the preset configuration.

Presetting different message sending rules, determining the corresponding message sending rule according to the message type, and generating and sending message data according to the message sending rule. The message data can be sent according to the established communication connection, and the data communication between the MCU and the SOC is completed.

The message format may be preset, in this embodiment, the inter-chip communication protocol is designed in a fixed-length manner, and the specific message length may be designed in combination with the requirements of the communication bandwidth and the load rate. For example, a frame of message data may be designed to be 129 bytes, where the first 113 bytes, i.e., 0 to 112 bytes, are data message fields of the service, and the last 16 bytes, i.e., 113 to 128 bytes, are response message fields, i.e., the response message may be sent as a frame with the data message of the service. Fig. 2 is a schematic diagram of a message format of message data in the embodiment of the present invention. In fig. 2, the API (Application Programming Interface), the session layer, the transmission layer, and the data link layer are designed by referring to a network communication seven-layer protocol, and different layers defined by the API (Application Programming Interface) are responsible for generating corresponding contents for the SPI communication system/the UART communication system, and are software level division and function division. For example, GID, Payload length, and Payload Data are generated in the API layer; MsgType is generated in the session layer; LiveCounter is generated in the transport layer; MsgHead, MsgID and CheckSum are generated in the data link layer. And after each layer generates the content of each message field, obtaining complete message data. Different fields of the message protocol are processed in different layers, so that modular processing can be realized, and the data transmission layer is clear.

In fig. 2, MsgHead may represent a data packet header, for example, the data packet header may be 0xAA or 0x55, and the response data packet header may be 0x55 or 0 xAA. The MsgHead can be used for positioning message data, and specific header information can be defined by self. The MsgID is the number of times of sending the message data, and every time the link layer sends the service data, the MsgID can be added with 1 as the count of the valid message, and Checksum and ACK/NACK (Acknowledgement/negative Acknowledgement) can be calculated and matched using the MsgID accordingly. The MsgType represents the message types, including handshake messages, periodic messages, event messages, periodic event messages and response messages. LiveCounter represents the traffic data packet traffic count. The GID is a group ID, and may be a group divided in advance according to service and communication needs, for example, alarm lamp information GID is 1, dial plate information GID is 2, and heartbeat information GID is 3. Payload length indicates the transmission effective data length. Payload Data represents the transmitted Data. Reserved represents a complement field. CheckSum denotes the CheckSum check mechanism.

In order to improve the communication efficiency, the response message is formed by participating in each frame as an independent field, namely a certain number of bytes behind each frame of message are response messages and are sent together with the message of the service data. In this embodiment, the event type packet needs to support an ACK/NACK mechanism, and the periodic packet does not need to be sent in the next period even if the data of the periodic packet is not received. The ACK/NACK response message may occupy the last 16 bytes, where the MsgType of the response message is ACK or NACK, and the ACK is replied after the event-type data is correctly received, and the NACK is replied if the event-type data is not correctly received. If the service data is not sent while being sent, the corresponding field of the response message is supplemented with 0, and if the response data is not sent while being sent, the corresponding field of the service data is supplemented with 0.

In this embodiment, multiple exception handling mechanisms may be provided, so as to avoid exception handling in a single dimension, which may cause omission of an exception condition. In this embodiment, 5-dimensional exception handling mechanisms, including a LiveCounter (keep alive) mechanism, a Checksum (Checksum) mechanism, an ACK/NACK mechanism, a Timeout (Timeout) mechanism, and a heartbeat mechanism, may be simultaneously employed to implement multi-angle and omni-directional reliability and high availability of communication data. Wherein, only the event type message can support the ACK/NACK mechanism.

The embodiment of the invention powers on the SOC through the MCU, and the SOC sends a first request message to the MCU after being powered on to perform handshaking. And the MCU completes handshaking with the SOC according to a preset handshaking message confirmation rule and establishes reliable communication connection. Different message types and message sending rules can be preset, and for different message types, the MCU and the SOC can transmit message data through the established communication connection, so that the requirements on different services are met. The problems that in the prior art, data with a fast period occupy communication resources and data with a slow period cannot be updated in time are solved, and the diversity of message types is improved. And through the handshake message, the reliability of transmission is ensured, and the efficiency and the precision of message transmission are improved.

Example two

Fig. 3 is a flowchart illustrating a data communication method according to a second embodiment of the present invention, where this embodiment is an alternative embodiment based on the above-mentioned embodiment, and the method can be executed by a data communication device.

In this embodiment, the packet type includes a periodic packet; correspondingly, according to the preset message type and the message sending rule, based on the established communication connection, the message data is sent to the SOC, and the method can be detailed as follows: judging whether the current time meets the preset sending condition of the periodic message, if so, generating message data to be sent according to a preset message field division rule; and sending message data to the SOC according to the pre-established communication connection.

As shown in fig. 3, the method specifically includes the following steps:

and 310, responding to the MCU starting instruction, electrifying the SOC, and sending a first request message to the MCU after the SOC is electrified.

And step 320, receiving a first request message sent by the SOC, finishing handshaking with the SOC according to a preset MCU handshaking message confirmation rule, and establishing communication connection.

And 330, judging whether the current time meets the preset sending condition of the periodic message, if so, generating message data to be sent according to a preset message field division rule.

The handshake messages are sent when the MCU and the SOC are started, and the event messages, the periodic event messages and the response messages are sent instead of the handshake messages after the communication connection is established.

The message types of different service data are configured in advance, and for a periodic message, the time period for sending the message can be set in advance, for example, the message is sent every second. The current time may be obtained in real time, and whether the current time meets a preset sending condition of the periodic packet is determined, for example, the periodic packet sending condition may be that a time difference between the current time and a time of sending the periodic packet of the same service last time is a preset time period. And if the time difference is a preset time period, determining that the sending condition of the periodic message is met. The message data to be sent can be generated according to the preset message field division rule. The message field division rule may be expressed as a preset message format, for example, the message data may be generated according to the format of the field in fig. 2.

In this embodiment, optionally, the message type includes an event type message; correspondingly, according to the preset message type and the message sending rule, based on the established communication connection, sending message data to the SOC, including: judging whether a preset trigger event for sending an event type message exists or not, if so, generating message data to be sent according to a preset message field division rule; and sending message data to the SOC according to the pre-established communication connection.

Specifically, data with high requirements for security may be sent by using periodic messages, and messages with low requirements for security or triggered by events may be sent by using event messages. For the event type message, a trigger event for sending the event type message may be preset. For example, for the meter information, when the meter information exceeds a preset numerical threshold, it is determined that a trigger event has occurred. After the existence of the preset trigger event is determined, the event type message data to be sent can be generated according to the preset message field division rule. The message field division rule can be that each field in the message is generated according to a preset message format to obtain complete message data. After the message data is obtained, the message data can be sent to the SOC according to the pre-established communication connection. The beneficial effect of the setting is that different message sending rules are set for different message types, if the data security requirement is higher, the data is sent continuously according to the period, and the information omission is avoided; if the data security is low, the data is sent only when the trigger event occurs, so that the resource waste is reduced, and the data transmission efficiency is improved.

In this embodiment, optionally, the message field of the event type message includes a response message field; correspondingly, after sending the message data to the SOC, the method further includes: judging whether a received response message fed back by the SOC is received within a preset time; if yes, the message data is determined to be sent completely.

Specifically, a field with a preset byte number is specified in the message format as a response message field, and for handshake messages and periodic messages, the response message field can be supplemented with 0; for the event type message, the MsgType of the response message may be ACK or NACK, and if the receiver of the message correctly receives the event type data, the receiver may reply to the received response message, and if the receiver incorrectly receives the event type data, the receiver may reply to the unreceived response message. For example, the reply message may occupy the last 16 bytes. In the periodic event type message, a response message field may also be included.

The MCU sends an event type message to the SOC, and after the SOC receives the event type message, if the event type data is correctly received, the SOC can reply the received response message; if the event type data is not correctly received, a non-received response message is replied. The MCU can judge whether a received response message fed back by the SOC is received within a preset time, and if so, the message data is determined to be sent completely; and if the received response message is not received or the non-received response message is received, determining that the message data transmission is abnormal. The beneficial effect of this configuration is that if ACK/NACK is independent 1 frame, the communication efficiency is low, which may result in that the peer end cannot send out data. And the ACK/NACK is used as the field in the message to participate in the frame formation, so that the communication efficiency is greatly improved. And the reply of the receiver can be received in time, and the efficiency and the precision of data communication are improved.

In this embodiment, optionally, the message type includes a periodic event type message; correspondingly, according to the preset message type and the message sending rule, based on the established communication connection, sending message data to the SOC, including: judging whether the current time meets a preset time period condition or not according to the starting time of the current period; if not, judging whether a preset trigger event for sending the periodic event type message exists or not; if so, generating message data to be sent according to a preset message field division rule; sending message data to the SOC according to the pre-established communication connection; and determining the starting time of a new period according to the sending time of the message data, and judging whether the new current time meets the preset time period condition or not according to the starting time of the new period.

Specifically, the message type may further include a periodic event type message, and a periodic event type message with a longer period may be derived as the periodic event type message. The periodic event type message is a message sending period and a message sending trigger event which are preset. And after the current period starts, acquiring the current time in real time, and judging whether the current time meets a preset time period condition or not according to the starting time of the current period. The time period condition refers to determining whether the current time reaches the end time of the current period, i.e., determining whether the current period ends. If the current period is over, generating message data to be sent according to a preset message format, namely according to a preset message field division rule. And if the current period is not finished, continuously judging whether a preset trigger event exists or not. If not, whether the current period is finished or not is continuously monitored, and whether a trigger event exists or not is determined. And if the trigger event exists, generating message data to be sent according to a preset message field division rule. And after the message data are obtained, sending the message data to the SOC according to the pre-established communication connection.

And recording the sending time of the message data, and taking the sending time of the message data as the starting time of a new cycle. And judging a new round according to the starting time of the new round of period. That is, whether the new current time meets the preset time period condition is judged again, and if not, whether a preset trigger event for sending the periodic event type message exists is judged; if so, generating message data to be sent according to a preset message field division rule; and sending message data to the SOC according to the pre-established communication connection.

That is, the periodic event type event is a period in which, in one transmission period, if the period is not ended but a trigger event occurs, the message data is transmitted, the current period is directly ended, and a new cycle is started. The method has the advantages that the periodic event type message is set, so that the periodic transmission of the message can be ensured, data omission is avoided, message data can be transmitted in time, and the efficiency of data communication is improved.

And S340, sending message data to the SOC according to the pre-established communication connection.

After the message data is generated, the message data can be sent to the SOC according to the established communication connection. In this embodiment, the SOC may also generate message data and send the message data to the MCU. That is, the MCU and the SOC may be a transmitter and a receiver for each other.

The embodiment of the invention powers on the SOC through the MCU, and the SOC sends a first request message to the MCU after being powered on to perform handshaking. And the MCU completes handshaking with the SOC according to a preset handshaking message confirmation rule and establishes reliable communication connection. Different message types and message sending rules can be preset, and for different message types, the MCU and the SOC can transmit message data through the established communication connection, so that the requirements on different services are met. The message transmission can be carried out according to the period or the trigger event, and the flexibility of data communication is improved. The problems that in the prior art, data with a fast period occupy communication resources and data with a slow period cannot be updated in time are solved, and the diversity of message types is improved. And through the handshake message, the reliability of transmission is ensured, and the efficiency and the precision of message transmission are improved.

EXAMPLE III

Fig. 4 is a flowchart of a data communication method according to a third embodiment of the present invention, where the present embodiment is applicable to a case of controlling inter-chip data communication, and the method may be executed by a data communication device, where the data communication device may be implemented in a form of hardware and/or software, and the data communication device may be configured on an SOC. As shown in fig. 4, the method includes:

and step 410, starting the SOC according to the power-on operation of the MCU on the SOC, and sending a first request message to the MCU.

And after the MCU is started, the SOC is powered on. After the SOC is electrified and started, a first request message is sent to the MCU, and in the normal handshaking process, the first request message is a handshaking request message. The time between the start of the SOC and the transmission of the first request message may be preset.

After receiving the first request message, the MCU may determine whether the first request message is a handshake request message according to a preset MCU handshake message confirmation rule. And if so, sending a first reply message to the SOC. If not, the first request message of the SOC is continuously acquired regularly. In the normal handshake process, the first reply message is a handshake reply message.

And step 420, finishing handshaking with the MCU according to a preset SOC handshaking message confirmation rule, and establishing communication connection.

After receiving the first reply message, the SOC determines whether the first reply message is a handshake reply message according to a preset SOC handshake message confirmation rule. If not, the first request message is sent to the MCU again; and if so, sending a second request message to the MCU. And the MCU receives the second request message and determines whether the second request message is a handshake reply message or not according to a preset MCU handshake message confirmation rule. And if the second request message is a handshake reply message, determining that the handshake is completed, and establishing communication connection between the MCU and the SOC.

And step 430, receiving the message data sent by the MCU according to the established communication connection so as to complete data communication.

After the communication connection is established, the SOC can receive the message sent by the MCU, and if the received message includes a response message field, the SOC can respond to the MCU. The SOC may also serve as a message sender, that is, the SOC may also send message data to the MCU based on the established communication connection according to a preset message type and a message sending rule, so as to complete data communication.

The delay time for the first transmission of different types of messages may be preset, for example, for a periodic message, the start of the first period may be determined according to the delay time. For example, the first cycle may begin 2 seconds after the handshake is completed.

The embodiment of the invention powers on the SOC through the MCU, and the SOC sends a first request message to the MCU after being powered on to perform handshaking. The MCU and the SOC can complete handshake according to a preset handshake message confirmation rule and establish reliable communication connection. Different message types and message sending rules can be preset, and for different message types, the MCU and the SOC can transmit message data through the established communication connection, so that the requirements on different services are met. The SOC may respond to the received message. The problems that in the prior art, data with a fast period occupy communication resources and data with a slow period cannot be updated in time are solved, and the diversity of message types is improved. And through the handshake message, the reliability of transmission is ensured, and the efficiency and the precision of message transmission are improved.

Example four

Fig. 5 is a schematic structural diagram of a data communication apparatus according to a fourth embodiment of the present invention. As shown in fig. 5, the apparatus includes:

the SOC power-on module 501 is configured to respond to an MCU start instruction, power on the SOC, and enable the SOC to send a first request message to the MCU after powering on;

a handshake message confirmation module 502, configured to receive the first request message sent by the SOC, complete handshake with the SOC according to a preset MCU handshake message confirmation rule, and establish communication connection;

a message data sending module 503, configured to send message data to the SOC based on the established communication connection according to a preset message type and a preset message sending rule, so as to complete data communication.

Optionally, the handshake packet confirmation module 502 includes:

a first request message judging unit, configured to receive a first request message sent by the SOC, and judge whether the current request message is a handshake request message;

a first reply message sending unit, configured to send a first reply message to the SOC if the first reply message is a handshake reply message, so that the SOC sends a second request message after determining that the first reply message is a handshake reply message;

a second request message determining unit, configured to receive a second request message sent by the SOC, and determine whether the second request message is a handshake completion message;

and the communication connection unit is used for determining that the MCU and the SOC finish handshaking and establishing communication connection if the MCU and the SOC finish handshaking.

Optionally, the message type includes a periodic message;

correspondingly, the message data sending module 503 is specifically configured to:

judging whether the current time meets the sending condition of a preset periodic message, if so, generating message data to be sent according to a preset message field division rule;

and sending the message data to the SOC according to the pre-established communication connection.

Optionally, the message type includes an event type message;

correspondingly, the message data sending module 503 includes:

a trigger event judging unit, configured to judge whether a preset trigger event for sending an event-type message exists, and if yes, generate message data to be sent according to a preset message field division rule;

and the message sending unit is used for sending the message data to the SOC according to the pre-established communication connection.

Optionally, the message type includes a periodic event type message;

judging whether the current time meets a preset time period condition or not according to the starting time of the current period;

if not, judging whether a preset trigger event for sending the periodic event type message exists or not;

if so, generating message data to be sent according to a preset message field division rule;

sending the message data to the SOC according to the pre-established communication connection;

and determining the starting time of a new period according to the sending time of the message data, and judging whether the new current time meets a preset time period condition or not according to the starting time of the new period.

Optionally, the message field of the event type message includes a response message field;

correspondingly, the message data sending module 503 includes:

the received response message receiving unit judges whether a received response message fed back by the SOC is received in preset time after sending message data to the SOC; and if so, determining that the message data is sent completely.

The data communication device provided by the embodiment of the invention can execute the data communication method provided by any embodiment of the invention, is configured on the MCU, and has the corresponding functional modules and beneficial effects of the execution method.

EXAMPLE five

Fig. 6 is a schematic structural diagram of a data communication apparatus according to a fifth embodiment of the present invention. As shown in fig. 6, the apparatus includes:

a first request message sending module 601, configured to start the SOC according to a power-on operation of the MCU on the SOC, and send a first request message to the MCU;

a communication connection establishing module 602, configured to complete handshaking with the MCU according to a preset SOC handshaking message confirmation rule, and establish communication connection;

a message data receiving module 603, configured to receive, according to the established communication connection, the message data sent by the MCU, so as to complete data communication.

The data communication device provided by the embodiment of the invention can execute the data communication method provided by any embodiment of the invention, is configured on the SOC, and has the corresponding functional modules and beneficial effects of the execution method.

EXAMPLE six

FIG. 7 illustrates a schematic diagram of an electronic device 10 that may be used to implement an embodiment of the invention. The electronic device 10 is intended to represent various forms of digital computers, such as laptops, desktops, workstations, personal digital assistants, servers, blade servers, mainframes, and other appropriate computers. The electronic device 10 may also represent various forms of mobile devices, such as personal digital assistants, cellular telephones, smart phones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions, are meant to be exemplary only, and are not meant to limit implementations of the inventions described and/or claimed herein.

As shown in fig. 7, the electronic device 10 includes at least one processor 11, and a memory communicatively connected to the at least one processor 11, such as a Read Only Memory (ROM)12, a Random Access Memory (RAM)13, and the like, wherein the memory stores a computer program executable by the at least one processor, and the processor 11 can perform various suitable actions and processes according to the computer program stored in the Read Only Memory (ROM)12 or the computer program loaded from a storage unit 18 into the Random Access Memory (RAM) 13. In the RAM 13, various programs and data necessary for the operation of the electronic apparatus 10 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other via a bus 14. An input/output (I/O) interface 15 is also connected to bus 14.

A number of components in the electronic device 10 are connected to the I/O interface 15, including: an input unit 16 such as a keyboard, a mouse, or the like; an output unit 17 such as various types of displays, speakers, and the like; a storage unit 18 such as a magnetic disk, an optical disk, or the like; and a communication unit 19 such as a network card, modem, wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information/data with other devices via a computer network such as the internet and/or various telecommunication networks.

The processor 11 may be a variety of general and/or special purpose processing components having processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), various specialized Artificial Intelligence (AI) computing chips, various processors running machine learning model algorithms, a Digital Signal Processor (DSP), and any suitable processor, controller, microcontroller, or the like. The processor 11 performs the various methods and processes described above, such as methods of data communication.

In some embodiments, the method of data communication may be implemented as a computer program tangibly embodied in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and/or installed onto the electronic device 10 via the ROM 12 and/or the communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the method of controlling a plant growing environment described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured by any other suitable means (e.g., by means of firmware) to perform a method of data communication.

Various implementations of the systems and techniques described here above may be implemented in digital electronic circuitry, integrated circuitry, Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), Application Specific Standard Products (ASSPs), system on a chip (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and/or combinations thereof. These various embodiments may include: implemented in one or more computer programs that are executable and/or interpretable on a programmable system including at least one programmable processor, which may be special or general purpose, receiving data and instructions from, and transmitting data and instructions to, a storage system, at least one input device, and at least one output device.

A computer program for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the computer programs, when executed by the processor, cause the functions/acts specified in the flowchart and/or block diagram block or blocks to be performed. A computer program can execute entirely on a machine, partly on a machine, as a stand-alone software package partly on a machine and partly on a remote machine or entirely on a remote machine or server.

In the context of the present invention, a computer-readable storage medium may be a tangible medium that can contain, or store a computer program for use by or in connection with an instruction execution system, apparatus, or device. A computer readable storage medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. Alternatively, the computer readable storage medium may be a machine readable signal medium. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

To provide for interaction with a user, the systems and techniques described here can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to a user; and a keyboard and a pointing device (e.g., a mouse or a trackball) by which a user can provide input to the electronic device. Other kinds of devices may also be used to provide for interaction with a user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form, including acoustic, speech, or tactile input.

The systems and techniques described here can be implemented in a computing system that includes a back-end component (e.g., as a data server), or that includes a middleware component (e.g., an application server), or that includes a front-end component (e.g., a user computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described here), or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: local Area Networks (LANs), Wide Area Networks (WANs), blockchain networks, and the internet.

The computing system may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other. The server can be a cloud server, also called a cloud computing server or a cloud host, and is a host product in a cloud computing service system, so that the defects of high management difficulty and weak service expansibility in the traditional physical host and VPS service are overcome.

It should be understood that various forms of the flows shown above may be used, with steps reordered, added, or deleted. For example, the steps described in the present invention may be executed in parallel, sequentially, or in different orders, and are not limited herein as long as the desired result of the technical solution of the present invention can be achieved.

The above-described embodiments should not be construed as limiting the scope of the invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions may be made in accordance with design requirements and other factors. Any modification, equivalent replacement, and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.

Claims

1. A method of data communication, characterized in that the method is performed by a micro control unit, MCU, the method comprising:

2. The method of claim 1, wherein receiving a first request message sent by the SOC, completing handshake with the SOC according to a preset MCU handshake message confirmation rule, and establishing a communication connection comprises:

receiving a first request message sent by the SOC, and judging whether the current request message is a handshake request message;

if yes, sending a first reply message to the SOC, so that the SOC sends a second request message after determining that the first reply message is a handshake reply message;

receiving a second request message sent by the SOC, and judging whether the second request message is a handshake completion message;

and if so, determining that the MCU and the SOC finish handshaking and establishing communication connection.

3. The method of claim 1, wherein the packet type comprises a periodic packet;

correspondingly, according to a preset message type and a message sending rule, based on the established communication connection, sending message data to the SOC, including:

judging whether the current time meets the preset sending condition of the periodic message, if so, generating message data to be sent according to a preset message field division rule;

4. The method of claim 1, wherein the message type comprises an event-type message;

judging whether a preset trigger event for sending an event type message exists or not, if so, generating message data to be sent according to a preset message field division rule;

5. The method of claim 1, wherein the packet type comprises a periodic event type packet;

6. The method according to claim 4, wherein the message field of the event message comprises a response message field;

correspondingly, after sending the message data to the SOC, the method further includes:

judging whether a received response message fed back by the SOC is received within a preset time; and if so, determining that the message data is sent completely.

7. A method of data communication, the method being performed by a System On Chip (SOC), the method comprising:

8. An apparatus for data communication, wherein the apparatus is configured to a MCU, the apparatus comprising:

9. An apparatus for data communication, the apparatus configured to a system on a chip (SOC), the apparatus comprising:

10. An electronic device, characterized in that the electronic device comprises:

at least one processor; and

the memory stores a computer program executable by the at least one processor to enable the at least one processor to perform the method of data communication of any of claims 1-6 or claim 7.

11. A computer-readable storage medium storing computer instructions for causing a processor to perform the method of data communication of any one of claims 1-6 or claim 7 when executed.