A real-time sharing method and system for electric vehicle data

Abstract

The present application belongs to the technical field of electric vehicle data sharing, and discloses a method and system for real-time sharing of electric vehicle data, which includes the following steps: the master device sends the corresponding device driving information to all slave devices according to the state of the electric vehicle, the slave device generates a first state data packet in real time according to the prescribed unified data format and according to the running state of the electric vehicle, and parses and matches the device driving information; the slave device transmits the first state data packet to the master device, the master device replaces the synchronization byte and the original function byte in the first state data packet, and obtains the second state data packet; the master device cyclically sends the second state data packet to the cloud server within the prescribed sending cycle; the receiving device replaces the function byte of the second state data packet. The running state parameters of the electric vehicle can be obtained from the network in real time, which improves the standardization of various devices of the electric vehicle, and improves the real-time, reliability and security of the electric vehicle data interaction.

Description

Technical Field

[0001] The present invention relates to the technical field of electric vehicle data sharing, and in particular to a method and system for real-time sharing of electric vehicle data. Background Art

[0002] As a convenient means of transportation, electric bicycles have become the most widely used means of transportation.

[0003] At present, the level of informatization, intelligence, and human-computer interaction of electric bicycles is not high. In addition, although standardized hub equipment can solve the problems of complicated wiring and specifications inside electric bicycles, incompatible maintenance between different manufacturers, and inconsistent wiring inside electric vehicles between electric vehicle manufacturers, there are still real-time, reliability, and security issues when different devices perform standardized data exchange. Summary of the invention

[0004] The purpose of the embodiments of the present application is to propose a method and system for real-time sharing of electric vehicle data to solve the real-time, reliability and security problems when the devices inside the electric vehicle perform standardized data interaction.

[0005] In the first aspect, in order to solve the above technical problems, the embodiment of the present application provides a method for real-time sharing of electric vehicle data, which adopts the following technical solution, including:

[0006] Step 100, providing a real-time data sharing system for an electric vehicle, comprising a master control device and a plurality of slave devices configured in the electric vehicle; the slave devices are independent of each other, the sharing system further comprises a cloud server and a plurality of receiving devices, the master control device is connected to the plurality of slave devices via a data line for communication, and the master control device and the receiving device are respectively connected to the cloud server through a network;

[0007] Step 200, the master device obtains the state of the electric vehicle, and sends corresponding device driving information to all slave devices according to the state of the electric vehicle. The slave devices generate a first state data packet in real time according to a prescribed unified data format and the running state of the electric vehicle, and parse and match the device driving information. The first state data packet is indexed by a network address or ID.

[0008] Step 300: After the network address or ID is matched successfully, the slave device transmits the first status data packet to the master device, and the master device configures the first status data packet, inserts a function byte before each data byte in the first status data packet, and obtains a second status data packet;

[0009] Step 400: The main control device cyclically sends the second status data packet to the cloud server within a specified sending period;

[0010] Step 500: The receiving device receives a second status data packet from the cloud server, and replaces the function bytes of the second status data packet to obtain a third status data packet of the electric vehicle device.

[0011] In combination with the electric vehicle data real-time sharing method described in the first aspect of the present invention, in a first possible implementation manner, the master control device is connected to multiple slave devices through data lines, and the master control device and the receiving device are respectively connected to the cloud server through a network, including:

[0012] Step 110, assigning a unique network address or ID to the master device, each slave device, and each receiving device;

[0013] Step 120: Build a shared network using the master device, slave device, cloud server and receiving device, and transmit data through the network address or ID.

[0014] In combination with the electric vehicle data real-time sharing method described in the first aspect of the present invention, in a second possible implementation manner, the master control device obtains the electric vehicle state, and sends corresponding device driving information to all slave devices according to the electric vehicle state, including:

[0015] Step 210, judging the state of the electric vehicle;

[0016] Step 220: If the electric vehicle is in a running state, the driving information of the front control device and the rear control device are sent to all the slave devices respectively;

[0017] Step 230: If the electric vehicle is not in use, the driving information of all slave devices is sent to all slave devices respectively;

[0018] The driver information includes the network address or ID information of the corresponding device.

[0019] In conjunction with the electric vehicle data real-time sharing method described in the first aspect of the present invention, in a third possible implementation manner, the slave device generates a first status data packet in real time according to the running status of the electric vehicle, including:

[0020] Step 240, generating data bytes according to a set data format;

[0021] Step 250: Generate an ID byte or a network address byte at the head of the data byte to obtain the first status data packet;

[0022] The number of the data bytes is less than or equal to a constant N, and the decimal value of the ID bytes or the network address bytes is less than a constant M.

[0023] In combination with the electric vehicle data real-time sharing method described in the first aspect of the present invention, in a fourth possible implementation manner, the slave device generates a first status data packet in real time according to the running status of the electric vehicle, including:

[0024] Step 260: Generate data bytes, synchronization bytes, ID bytes or network address bytes according to the set data format;

[0025] Step 270: Add the synchronization byte, ID byte or network address byte to the header of the data byte in sequence to obtain the first status data packet;

[0026] The number of bytes of the data bytes is less than or equal to a constant N, the decimal value of the ID byte or the network address byte is less than a constant M, and the number of bytes of the first status data packet is less than H.

[0027] In combination with the electric vehicle data real-time sharing method described in the first aspect of the present invention, in a fifth possible implementation manner, parsing and matching the device driving information includes:

[0028] Step 280: Each slave device parses the received drive information to obtain ID or network address information;

[0029] Step 290: Compare the ID or network address information with the ID or network address information of the slave device to determine whether they are the same.

[0030] In conjunction with the method for real-time sharing of electric vehicle data described in the first aspect of the present invention, in a sixth possible implementation manner, the method further includes:

[0031] Step 600: setting the sending period to obtain a maximum sending period, and if the second status data packet is not sent within the maximum sending period, resetting the sending response time;

[0032] Step 700: Obtain the number of resets per minute. If it exceeds a specified threshold, it is determined that the communication reliability is reduced and the communication line is checked.

[0033] In a second aspect, in order to solve the above problem, a real-time sharing system for electric vehicle data is provided, which adopts the above-mentioned real-time sharing method for electric vehicle data, and comprises:

[0034] Main control equipment;

[0035] Multiple slave devices;

[0036] Cloud servers;

[0037] Multiple receiving devices;

[0038] The master control device is connected to multiple slave devices through data lines, and the master control device and the receiving device are connected to the cloud server through a network respectively;

[0039] The master control device is used to obtain the state of the electric vehicle, send corresponding device driving information to all slave devices according to the state of the electric vehicle, configure the first state data packet, insert a function byte before each data byte in the first state data packet, obtain a second state data packet, and cyclically send the second state data packet to the cloud server within a specified sending cycle;

[0040] The slave device is used to generate a first status data packet in real time according to a prescribed unified data format and according to the running status of the electric vehicle, and parse and match the device driving information, wherein the first status data packet is indexed by a network address or ID. After the network address or ID is successfully matched, the slave device transmits the first status data packet to the master control device;

[0041] The receiving device is used to receive a second status data packet from the cloud server, and replace the function bytes of the second status data packet to obtain a third status data packet of the device of the electric vehicle.

[0042] In conjunction with the electric vehicle data real-time sharing system described in the second aspect of the present invention, in a first possible implementation manner, the slave device includes:

[0043] a first generation unit;

[0044] A first acquisition unit;

[0045] The first generating unit is used to generate data bytes according to a set data format;

[0046] The first acquisition unit is used to generate an ID byte or a network address byte at the header of the data byte to obtain the first status data packet.

[0047] In conjunction with the electric vehicle data real-time sharing system described in the first aspect of the present invention, in a second possible implementation manner, the slave device includes:

[0048] A second generation unit;

[0049] A second acquisition unit;

[0050] The second generating unit is used for generating data bytes, synchronization bytes, ID bytes or network address bytes according to a set data format;

[0051] The second acquisition unit is used to add the synchronization byte, ID byte or network address byte to the header of the data byte in sequence to obtain the first status data packet.

[0052] Compared with the prior art, the embodiments of the present application mainly have the following technical effects: by utilizing the master control device to drive the corresponding slave device to upload the status data packet to the cloud server in real time according to the status of the electric vehicle, the receiving device can obtain the operating status parameters of the electric vehicle in real time from the network, thereby improving the standardization of various devices of the electric vehicle, and improving the data interactivity of the electric vehicle through real-time, reliable and secure data transmission. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] In order to more clearly illustrate the scheme in the present application, a brief introduction is given below to the drawings required for use in the description of the embodiments of the present application. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0054] Figure 1 A flowchart of an embodiment of a method for real-time sharing of electric vehicle data according to the present application;

[0055] Figure 2 yes Figure 1 A flowchart of a specific implementation of S100;

[0056] Figure 3 yes Figure 1 Flow chart of a first specific implementation mode of S200;

[0057] Figure 4 yes Figure 1 Flow chart of a second specific implementation manner of S200;

[0058] Figure 5 yes Figure 1 Flow chart of a third specific implementation manner of S200;

[0059] Figure 6 yes Figure 1 A flowchart of a specific implementation of S300;

[0060] Figure 7 yes Figure 1 A flowchart of a specific implementation method after S500;

[0061] Figure 8 It is a structural diagram of an embodiment of a real-time sharing system for electric vehicle data according to the present application. DETAILED DESCRIPTION

[0062] The following will be combined with the accompanying drawings in the invention to clearly and completely describe the technical solutions in the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments in the present invention, other embodiments obtained by ordinary technicians in this field without creative work are all within the scope of protection of the present invention.

[0063] Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0064] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by technicians in the technical field to which this application belongs; the terms used in the specification of the application are only for the purpose of describing specific embodiments and are not intended to limit this application; the terms "including" and "having" in the specification and claims of this application and the above-mentioned figure descriptions and any variations thereof are intended to cover non-exclusive inclusions.

[0065] In addition, the terms "first" and "second" are used for descriptive purposes only and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features. In the description of this application, the meaning of "plurality" is two or more, unless otherwise clearly and specifically defined.

[0066] The purpose of the embodiments of the present application is to propose a method for real-time sharing of electric vehicle data to solve the real-time, reliability and security problems when the devices inside the electric vehicle perform standardized data interaction.

[0067] In order to solve the above technical problems, the present application embodiment provides a method for real-time sharing of electric vehicle data, which adopts the following technical solutions: Figure 1 , Figure 1 A flowchart of an embodiment of a method for real-time sharing of electric vehicle data according to the present application; comprising:

[0068] S100. Provide a real-time sharing system for electric vehicle data, including a master control device 801 and multiple slave devices 802 configured in the electric vehicle; the slave devices 802 are independent of each other, and the sharing system also includes a cloud server 803 and multiple receiving devices 804. The master control device 801 is connected to the multiple slave devices 802 through a data line, and the master control device 801 and the receiving device 804 are respectively connected to the cloud server 803 through a network.

[0069] In this embodiment, the control signals of the devices in the electric vehicle (for example, the hub device) are digitized and standardized, and the status data of each device is formatted and shared on the cloud server 803 (for example, the network data line). All devices in the electric vehicle can be connected to the cloud server 803 and obtain the data of interest therefrom. It is defined as "data communication guided by network address or ID". It takes each independent device as a unit. Each independent device has a unique network address or device ID. Devices are classified by network address or ID, and it is ensured that there are no two devices with the same network address or ID on the data line.

[0070] This embodiment stipulates that the devices are divided into a master device 801 and a slave device 802. There is only one master device 801 in the network, and there can be multiple slave devices 802, which theoretically cannot exceed 255. However, for better real-time performance, it can be set that the number of slave devices 802 with independent IDs cannot exceed 10, that is, the number of devices that can upload data will not exceed 10, but there can be more receiving devices 804. The system is a multi-point communication system, and all devices in the network can receive data and send data to the cloud server 803 in the network.

[0071] In some preferred implementations, the master device 801 is connected to multiple slave devices 802 via data lines, and the master device 801 and the receiving device 804 are connected to the cloud server 803 through a network, such as Figure 2 , Figure 2 yes Figure 1 A flowchart of a specific implementation of S100; comprising:

[0072] S110, assigning a unique network address or ID to the master device 801, each slave device 802, and each receiving device 804;

[0073] S120, using the master device 801, the slave device 802, the cloud server 803 and the receiving device 804 to build a shared network, and transmit data through the network address or ID.

[0074] The network address or ID is a unique identification of a device. A network connection between the master device 801 and the slave device 802 is established through the network address or ID.

[0075] S200, the master control device 801 obtains the state of the electric vehicle, and sends the corresponding device driving information to all slave devices 802 according to the state of the electric vehicle. The slave device 802 generates a first state data packet in real time according to the running state of the electric vehicle, and parses and matches the device driving information. The first state data packet is indexed by the network address or ID.

[0076] The electric vehicle status includes the use status (electric door lock is open) and the unuse status (electric door lock is closed). In the use status, only the status data of the front control device and the rear control device can be shared, and other slave devices 802 remain in the listening state and do not share the status data.

[0077] In some preferred implementations, the master device 801 obtains the electric vehicle state, and sends corresponding device driving information to all slave devices 802 according to the electric vehicle state, such as Figure 3 , Figure 3 yes Figure 1 The flowchart of the first specific implementation mode of S200 is as follows; comprising:

[0078] S210, determine the state of the electric vehicle; S220, if the electric vehicle is in operation, send the driving information of the front control device and the rear control device to all slave devices 802 respectively; S230, if the electric vehicle is not in use, send the driving information of all slave devices 802 to all slave devices 802 respectively; wherein the driving information includes the network address or ID information of the corresponding device.

[0079] In this embodiment, when data is shared, the master device 801 needs to send drive information to the slave device 802, and the slave device 802 performs parsing and matching. The slave device 802 whose network address or ID matches successfully sends a first status data packet.

[0080] All slave devices 802 generate data packets according to the set data format, which includes synchronization bits, network addresses or ID bytes, and data bytes. The format is shown in Table 1:

[0081] Table 1 Data format of the first state data packet

[0082]

[0083] The ID byte cannot be greater than 0XF0 and cannot be set as a synchronization bit.

[0084] In some preferred implementations, the slave device 802 generates a first status data packet in real time according to the running status of the electric vehicle, such as Figure 4 , Figure 4 yes Figure 1A flowchart of the second specific implementation method of S200; including: S240, generating data bytes from device 802 according to the set data format; S250, generating an ID byte or a network address byte at the head of the data byte to obtain a first status data packet; wherein the number of data bytes is less than or equal to a constant N, and the decimal value of the ID byte or the network address byte is less than a constant M.

[0085] When the first status data packet is generated according to the specified data format, when the synchronization bit is not set to 0xaa, the first status data packet is in a single-byte format, as shown in Table 2:

[0086] Table 2 Data format of the first state data packet in this embodiment

[0087]

[0088] In some preferred implementations, the value of N includes the number of data bytes and 1 check byte. The value of N can be 9. In order to achieve the real-time effect of data, the value of M is 10.

[0089] In some preferred embodiments, Figure 5 , Figure 5 yes Figure 1 The flowchart of the third specific implementation mode of S200; the slave device 802 generates a first status data packet in real time according to the running state of the electric vehicle, including:

[0090] S260. Generate data bytes, synchronization bytes, ID bytes or network address bytes from device 802 according to the set data format; S270. Add the synchronization bytes, ID bytes or network address bytes to the header of the data bytes in sequence to obtain a first status data packet; wherein the number of bytes of the data bytes is less than or equal to a constant N, the decimal value of the ID bytes or the network address bytes is less than a constant M, and the number of bytes of the first status data packet is less than H.

[0091] When the first status data packet is generated according to the prescribed data format, when the synchronization bit is set to 0xaa, the first status data packet is in a double-byte format.

[0092] In some preferred implementations, the value of N includes the number of data bytes and 1 check byte. N can be 9. In order to achieve the real-time effect of data, M is 10 and H is 20, that is, the number of bytes in a frame of data packet is less than or equal to 20.

[0093] In some preferred embodiments, Figure 6 , Figure 6 yes Figure 5 A flowchart of a specific implementation of S300; parsing and matching the device driver information, including:

[0094] S280, each slave device 802 parses the received drive information to obtain ID or network address information; S290, compares the ID or network address information with the ID or network address information of the slave device 802 to determine whether they are the same.

[0095] In this embodiment, after receiving the driving information from device 802, the driving information data is parsed to obtain the ID or network address information therein, and a matching judgment is performed. If they are the same, the generated first status data packet is prepared to be transmitted to the main control device 801, and the main control device 801 shares it according to the set period. If they are not the same, the listening state is maintained and no data sharing is performed.

[0096] S300, after the network address or ID matches successfully, the slave device 802 transmits the first state data packet to the master device 801, and the master device 801 configures the first state data packet, inserts a function byte before each data byte in the first state data packet, and obtains a second state data packet, as shown in Table 3:

[0097] Table 3 Data format of the second state data packet in this embodiment

[0098]

[0099] In Table 3, the byte after ID0x11 is the data packet byte, and the function byte is set in the data byte. The function byte is used to prevent the data packet byte from containing synchronization bytes. The ID is an index. In the single data format, the data packet byte is fixed to 9 bytes, and in the double data format, the data packet byte becomes 18 bytes. The function byte is used to replace the synchronization byte in the data. Referring to Table 3, the receiving device 804 needs to process the function byte and restore it to a fixed 9 bytes after receiving the data.

[0100] S400, the main control device 801 cyclically sends the second state data packet to the cloud server 803 within the specified sending period; S500, the receiving device 804 receives the second state data packet from the cloud server 803, and replaces the functional bytes of the second state data packet to obtain the third state data packet of the electric vehicle device.

[0101] Manufacturers can also define and set the data formats of the above-mentioned front control devices and back control devices according to their own needs, as shown in Table 4 and Table 5.

[0102] Table 4 Data format shared by front-end control devices

[0103]

[0104] Table 5 Data format shared by back-end control devices

[0105]

[0106] Further, such as Figure 7 , Figure 7 yes Figure 1 A flowchart of a specific implementation method after S500 in the method; the method also includes: S600, setting the sending cycle to obtain the maximum sending cycle, if the second state data packet is not sent within the maximum sending cycle, resetting the sending response time; S700, obtaining the number of resets per minute, if it exceeds the specified threshold, it is determined that the communication reliability is reduced, and the communication line is checked.

[0107] In this implementation, the transmission rate is set to 2400 byte / s; therefore, after the vehicle is started, only two sets of data are transmitted: the front control device data and the rear control device data. Therefore, the maximum response time of the front and rear control data is T = (1000ms / 2400) * 40 (front control 20, rear control 20) = 16.6ms. Excluding some additional overhead, in this embodiment, each transmission cycle is set to 30ms, and it will be reset if it exceeds the maximum transmission cycle of 50ms. If the number of resets per minute exceeds 30 times, it is judged that the communication reliability is low and the line needs to be checked. For ordinary electric motorcycles, the speed is 51km / std, and the device reaction time is: D / S (vehicle distance per second) = 51000 / 360 = 85 / 6m, then the device reaction distance is (85 / 6) / (1000 / 30) = 0.425m, which means that the reaction distance of an ordinary electric motorcycle at full speed does not exceed 0.425m. The national standard vehicle limits the speed to 15km / std, and the device reaction distance is 0.125 meters, which can fully guarantee driving safety.

[0108] For the transmission of application data, when the electric door lock is closed, the user operates through an application (usually a mobile app or mini program). When the electric door lock is closed, it will determine whether the highest bit of B7 is set to 1. If it is set to 1, the previous data is application data and cannot be parsed as control / status data. It can be parsed according to the customer's own definition. The setting of the check byte: the user can set the rules by himself.

[0109] Through the above methods, it is easy to achieve standardization of electric two-wheeled vehicles, thereby optimizing social and economic benefits and improving product and service quality.

[0110] Furthermore, in order to solve the above problems, a real-time sharing system for electric vehicle data is provided, which adopts the above-mentioned real-time sharing method for electric vehicle data, such as Figure 8 , Figure 8It is a structural diagram of an embodiment of a real-time sharing system of electric vehicle data according to the present application, including: a master control device 801, multiple slave devices 802, a cloud server 803, and multiple receiving devices 804; the master control device 801 is connected to multiple slave devices 802 through data lines, and the master control device 801 and the receiving device 804 are connected to the cloud server 803 through a network.

[0111] The master control device 801 is used to obtain the state of the electric vehicle, send the corresponding device driving information to all slave devices 802 according to the state of the electric vehicle, configure the first state data packet, insert a function byte before each data byte in the first state data packet, obtain the second state data packet, and cyclically send the second state data packet to the cloud server 803 within a specified sending cycle;

[0112] The slave device 802 is used to generate a first status data packet in real time according to a prescribed unified data format and the running status of the electric vehicle, and parse and match the device driving information. The first status data packet is indexed by a network address or ID. After the network address or ID is successfully matched, the slave device 802 transmits the first status data packet to the master device 801;

[0113] The receiving device 804 is used to receive the second state data packet from the cloud server 803, and replace the function bytes of the second state data packet to obtain the third state data packet of the electric vehicle device.

[0114] Furthermore, the slave device 802 includes a first generating unit and a first acquiring unit; the first generating unit is used to generate data bytes according to a set data format; the first acquiring unit is used to generate an ID byte or a network address byte at the head of the data byte to obtain a first status data packet.

[0115] Furthermore, the slave device 802 includes a second generation unit and a second acquisition unit; the second generation unit is used to generate data bytes, synchronization bytes, ID bytes or network address bytes according to the set data format; the second acquisition unit is used to add the synchronization bytes, ID bytes or network address bytes to the header of the data bytes in sequence to obtain a first status data packet.

[0116] Compared with the prior art, the embodiments of the present application mainly have the following technical effects: by utilizing the master control device to drive the corresponding slave device to upload the status data packet to the cloud server in real time according to the status of the electric vehicle, the receiving device can obtain the operating status parameters of the electric vehicle in real time from the network, thereby improving the standardization of various devices of the electric vehicle, and improving the data interactivity of the electric vehicle through real-time, reliable and secure data transmission.

[0117] The above are only preferred embodiments of the present invention and are not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the protection scope of the present invention.

Claims

1. A method for real-time sharing of electric vehicle data, characterized in that: include: Step 100: Provide a real-time data sharing system for an electric vehicle, including a master control device and a plurality of slave devices configured in the electric vehicle; The slave devices are independent of each other, the sharing system further comprises a cloud server and a plurality of receiving devices, the master device is connected to the plurality of slave devices through a data line, and the master device and the receiving device are respectively connected to the cloud server through a network; Step 200, the master device obtains the state of the electric vehicle, and sends corresponding device driving information to all slave devices according to the state of the electric vehicle. The slave devices generate a first state data packet in real time according to a prescribed unified data format and the running state of the electric vehicle, and parse and match the device driving information. The first state data packet is indexed by a network address or ID. The parsing and matching of the device driver information includes: Step 280: Each slave device parses the received drive information to obtain ID or network address information; Step 290: compare the ID or network address information with the ID or network address information of the slave device to determine whether they are the same; Step 300: After the network address or ID is matched successfully, the slave device transmits the first status data packet to the master device, and the master device configures the first status data packet, inserts a function byte before each data byte in the first status data packet, and obtains a second status data packet; Step 400: The main control device cyclically sends the second status data packet to the cloud server within a specified sending period; Step 500: The receiving device receives a second status data packet from the cloud server, and removes the function bytes of the second status data packet to obtain a third status data packet of the electric vehicle device.

2. The electric vehicle data real-time sharing method according to claim 1, characterized in that: The master control device is connected to multiple slave devices through data lines, and the master control device and the receiving device are connected to the cloud server through a network, including: Step 110, assigning a unique network address or ID to the master device, each slave device, and each receiving device; Step 120: Build a shared network using the master device, slave device, cloud server and receiving device, and transmit data through the network address or ID.

3. The method for real-time sharing of electric vehicle data according to claim 1, characterized in that: The master control device obtains the electric vehicle state, and sends corresponding device driving information to all slave devices according to the electric vehicle state, including: Step 210, judging the state of the electric vehicle; Step 220: If the electric vehicle is in a running state, the driving information of the front control device and the rear control device are sent to all the slave devices respectively; Step 230: If the electric vehicle is not in use, the driving information of all slave devices is sent to all slave devices respectively; The driver information includes the network address or ID information of the corresponding device.

4. The electric vehicle data real-time sharing method according to claim 1, characterized in that: The slave device generates a first status data packet in real time according to a prescribed unified data format and according to the running status of the electric vehicle, including: Step 240, generating data bytes according to a set data format; Step 250: Generate an ID byte or a network address byte at the header of the data byte to obtain the first status data packet.

5. The electric vehicle data real-time sharing method according to claim 1, characterized in that: The slave device generates a first status data packet in real time according to a prescribed unified data format and according to the running status of the electric vehicle, including: Step 260: Generate data bytes, synchronization bytes, ID bytes or network address bytes according to the set data format; Step 270: Add the synchronization byte, ID byte or network address byte to the header of the data byte in sequence to obtain the first status data packet.

6. The electric vehicle data real-time sharing method according to claim 1, characterized in that: The electric vehicle data real-time sharing method further includes: Step 600: setting the sending period to obtain a maximum sending period, and if the second status data packet is not sent within the maximum sending period, resetting the sending response time; Step 700: Obtain the number of resets per minute. If it exceeds a specified threshold, it is determined that the communication reliability is reduced and the communication line is checked.

7. A real-time sharing system for electric vehicle data, using the real-time sharing method for electric vehicle data according to any one of claims 1 to 6, characterized in that: include: Main control equipment; Multiple slave devices; Cloud servers; Multiple receiving devices; The master control device is connected to multiple slave devices through data lines, and the master control device and the receiving device are connected to the cloud server through a network respectively; The master control device is used to obtain the state of the electric vehicle, send corresponding device driving information to all slave devices according to the state of the electric vehicle, configure the first state data packet, insert a function byte before each data byte in the first state data packet, obtain a second state data packet, and cyclically send the second state data packet to the cloud server within a specified sending cycle; The slave device is used to generate a first status data packet in real time according to a prescribed unified data format and according to the running status of the electric vehicle, and parse and match the device driving information, wherein the first status data packet is indexed by a network address or ID. After the network address or ID is successfully matched, the slave device transmits the first status data packet to the master control device; The receiving device is used to receive a second status data packet from the cloud server, and remove the function bytes of the second status data packet to obtain a third status data packet of the device of the electric vehicle.

8. The electric vehicle data real-time sharing system according to claim 7, characterized in that: The slave device comprises: a first generation unit; A first acquisition unit; The first generating unit is used to generate data bytes according to a set data format; The first acquisition unit is used to generate an ID byte or a network address byte at the header of the data byte to obtain the first status data packet.

9. The electric vehicle data real-time sharing system according to claim 8, characterized in that: The slave device comprises: A second generation unit; A second acquisition unit; The second generating unit is used for generating data bytes, synchronization bytes, ID bytes or network address bytes according to a set data format; The second acquisition unit is used to add the synchronization byte, ID byte or network address byte to the header of the data byte in sequence to obtain the first status data packet.

Images