CN117527550A - Vehicle cloud communication data off-network reissue method and device and vehicle - Google Patents

Abstract

The disclosure relates to a vehicle cloud communication data off-network reissue method, a device and a vehicle, wherein the method comprises the following steps: transmitting real-time vehicle state data according to a first frequency in a first time interval after three-level fault occurrence under the condition that the vehicle is detected to be in a three-level fault occurrence state and the vehicle is in a networking state currently, and transmitting real-time vehicle state data according to a second frequency after the first time interval, wherein the first frequency is larger than the second frequency; and transmitting three-level fault supplement data according to the first frequency in idle time of a time interval in which real-time vehicle state data is transmitted according to the second frequency, wherein the three-level fault supplement data is vehicle state data in the second time interval before three-level fault occurs. According to the method and the device, when the vehicle has three-level faults, the vehicle state data in the time period before and after the three-level faults are sent to the cloud, the integrity and timeliness of the sent data are ensured, and the cloud is convenient to play back the data, analyze accidents and the like.

Description

Vehicle cloud communication data off-network reissue method and device and vehicle

Technical Field

The disclosure relates to the field of information technology, and in particular relates to a vehicle cloud communication data network disconnection and reissue method, device and vehicle.

Background

Along with the development of the internet of things of the automobile, the vehicle can configure the vehicle-mounted terminal to interact with the cloud end, and the information interaction between the vehicle-mounted terminal and the cloud end can be interrupted due to the fact that the vehicle runs in a disconnected network or other types of vehicle faults. In the related art, a scheme of storing data in a network disconnection period and performing reissue after network connection is restored is proposed, but the problems of incomplete reissue data and untimely reissue data exist.

Disclosure of Invention

In order to solve at least one technical problem, the disclosure provides a vehicle cloud communication data network disconnection and reissue method, device and vehicle.

According to some embodiments of the present disclosure, there is provided a vehicle cloud communication data off-line reissue method, the method including: transmitting real-time vehicle state data according to a first frequency in a first time interval after three-level fault occurrence under the condition that the vehicle is detected to be in a three-level fault occurrence state and the vehicle is currently in a networking state, and transmitting real-time vehicle state data according to a second frequency after the first time interval, wherein the first frequency is larger than the second frequency; and in the idle time of the time interval for transmitting the real-time vehicle state data according to the second frequency, transmitting the three-level fault complement data according to the first frequency, wherein the three-level fault complement data is the vehicle state data in the second time interval before the three-level fault occurs.

Based on the scheme, when the vehicle has three-level faults, the vehicle state data in the time period before and after the three-level faults are sent to the cloud, the integrity and timeliness of the sent data are ensured, and the cloud is convenient for carrying out subsequent operations such as data playback and accident analysis.

In some possible embodiments, the method further comprises: and under the condition that the vehicle is detected to be in a three-stage fault occurrence state and the vehicle is currently in a network disconnection state, storing vehicle state data according to the first frequency in a first time interval after the three-stage fault occurrence, and storing the vehicle state data according to the second frequency after the first time interval, wherein the stored vehicle state data is the network disconnection reissue data.

Based on the scheme, when the vehicle has three-level faults in the broken network state, the data in the time period after the three-level faults and the general on-off network data are stored respectively, and finally the broken network reissue data are formed by combination, so that the vehicle can completely store the data of the event period before and after the three-level faults under the broken network condition, and the integrity of the reissue data is ensured.

In some possible embodiments, the method further comprises: and in the idle time of a time interval of transmitting real-time vehicle state data according to a second frequency under the condition that the vehicle is currently in a networking state and the vehicle stores network-breaking reissue data, transmitting the network-breaking reissue data according to the first frequency after the transmission of three-level fault reissue data according to the first frequency is completed.

Based on the scheme, after the disconnected network vehicle is reconnected, the third-level fault reissue data is sent preferentially, and then the disconnected network reissue data is sent, so that timeliness of the cloud end for acquiring the third-level fault data is ensured, and meanwhile, the integrity of the reissue data can be ensured.

In some possible embodiments, the three-level fault reissue data is obtained based on the following steps: rolling and storing vehicle state data in a third time interval according to the first frequency, wherein the length of the third time interval is greater than or equal to that of the second time interval; detecting a three-level fault occurrence state according to the first frequency, stopping rolling storage when the three-level fault occurrence is detected, and freezing stored vehicle state data; and acquiring vehicle state data in a second time interval before the occurrence of the three-level fault from the stored vehicle state data to obtain the three-level fault complement data.

Based on the scheme, the vehicle state data in a period of time is recorded in real time in a high-frequency rolling storage mode, so that when a three-level fault occurs to a vehicle, the data loss or insufficient data density in a period of time before the three-level fault occurs can be prevented, the three-level fault data are incomplete, the rolling storage mode is adopted, the capacity requirement required by storage hardware can be reduced, and the vehicle cost is reduced.

In some possible embodiments, the length of the third time interval is equal to the sum of the lengths of the first time interval and the second time interval; the steps further include: when the occurrence of the three-level fault is detected, recording the occurrence time of the three-level fault, and continuing to perform rolling storage; stopping rolling storage and freezing stored vehicle state data when the duration of the three-level fault occurrence state reaches the length of the first time interval; and acquiring vehicle state data in a second time interval before the occurrence of the three-level fault according to the occurrence time of the three-level fault, and obtaining the three-level fault reissue data.

Based on the scheme, the vehicle state data in the time period before and after the occurrence of the three-level fault can be completely stored in a rolling storage mode, the storage of the three-level fault data and the storage of the network breaking and repairing data are not mutually conflicting, when the three-level fault occurs before and after the occurrence of the network breaking event, or when the three-level fault occurs before and after the occurrence of the time period, the network breaking event occurs for a plurality of times, and data loss caused by data cross storage can be avoided.

In some possible embodiments, the method further comprises: detecting a network disconnection event according to the first frequency; when the occurrence of the network breaking event is detected, recording the occurrence time of the network breaking event; and determining the frequency of storing the network breaking concurrent data according to the occurrence time of the network breaking event and the occurrence time of the three-level fault.

Based on the scheme, when the network breaking event and the three-level fault occur in the same time period, the frequency of storing the network breaking reissue data can be determined by recording the occurrence time of the network breaking event and the occurrence time of the three-level fault, so that the three-level fault data and the network breaking reissue data are ensured to be completely stored.

In some possible embodiments, the determining the frequency of storing the outage data according to the outage event occurrence time and the three-level fault occurrence time includes: if the occurrence time of the network outage event is within a first time interval of the occurrence time of the three-level fault, storing the network outage reissue data according to the second frequency; otherwise, storing the network-disconnected concurrent data according to the first frequency.

Based on the scheme, the data in the time periods before and after the occurrence of the three-level fault are stored preferentially by taking the end point of the first time period at the occurrence time of the three-level fault as a limit, so that the influence of the network break event in the time periods before and after the occurrence of the three-level fault is eliminated, and the integrity of the three-level fault data is protected.

In some possible embodiments, the storing the network-disconnected reissue data according to the second frequency includes: and taking the occurrence time of the network break event as the period starting time corresponding to the second frequency.

Based on the scheme, the frequency cycle starting point of the stored data is reset after the network disconnection based on the occurrence time of the network disconnection event, so that the situation that the normal data transmission before the network disconnection and the event interval of the stored data after the network disconnection are overlarge can be avoided, the data loss is avoided, and the timeliness and the integrity of the data are protected.

According to other embodiments of the present disclosure, there is provided a vehicle cloud communication data off-line reissue device, including:

the communication module is used for networking and logging in the cloud platform to send vehicle state data;

the network disconnection storage module is used for storing vehicle state data when the vehicle is disconnected;

the three-level fault storage module is used for storing vehicle state data in a second time interval before the three-level fault occurs;

and the detection module is used for detecting the networking state of the vehicle and the three-level fault occurrence state of the vehicle.

According to other embodiments of the present disclosure, a vehicle is provided, in which a set of instructions is stored, the set of instructions being executed by the vehicle to implement a vehicle cloud communication data off-network reissue method according to any of the above embodiments.

According to other embodiments of the present disclosure, there is provided a computer readable storage medium having at least one instruction or at least one program stored therein, the at least one instruction or at least one program loaded and executed by a processor to implement a vehicle cloud communication data off-network reissue method as described in some embodiments above.

In accordance with further embodiments of the present disclosure, an electronic device is provided that includes at least one processor, and a memory communicatively coupled to the at least one processor; the memory stores instructions executable by the at least one processor, and the at least one processor implements the vehicle cloud communication data network disconnection and reissuing method described in the above embodiments by executing the instructions stored by the memory.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Other features and aspects of the present disclosure will become apparent from the following detailed description of exemplary embodiments, which proceeds with reference to the accompanying drawings.

Drawings

In order to more clearly illustrate the embodiments of the present description or the technical solutions and advantages of the prior art, the following description will briefly explain the drawings used in the embodiments or the description of the prior art, and it is obvious that the drawings in the following description are only some embodiments of the present description, and other drawings may be obtained according to these drawings without inventive effort to a person skilled in the art.

Fig. 1 illustrates a flowchart of a vehicle cloud communication data off-line reissue method according to an embodiment of the present disclosure;

FIG. 2 illustrates a flow chart of a method of acquiring three-level fault reissue data in accordance with an embodiment of the present disclosure;

FIG. 3 illustrates a flow chart of an improved method of acquiring tertiary fault reissue data in accordance with an embodiment of the present disclosure;

fig. 4 illustrates a frequency determination method of storing the off-grid reissue data according to an embodiment of the present disclosure;

FIG. 5 illustrates a flowchart of a software implemented method according to an embodiment of the present disclosure;

fig. 6 shows a block diagram of a vehicle cloud communication data off-line reissue device according to an embodiment of the disclosure;

fig. 7 shows a flow chart of a vehicle transmitting data according to an embodiment of the present disclosure.

Detailed Description

The technical solutions of the embodiments of the present specification will be clearly and completely described below with reference to the drawings in the embodiments of the present specification, and it is apparent that the described embodiments are only some embodiments of the present specification, not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are intended to be within the scope of the present invention based on the embodiments herein.

It should be noted that the terms "first," "second," and the like in the description and the claims of the present invention and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the invention described herein may be implemented in sequences other than those illustrated or otherwise described herein. Furthermore, 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 server that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed or inherent to such process, method, article, or apparatus, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

Various exemplary embodiments, features and aspects of the disclosure will be described in detail below with reference to the drawings. In the drawings, like reference numbers indicate identical or functionally similar elements. Although various aspects of the embodiments are illustrated in the accompanying drawings, the drawings are not necessarily drawn to scale unless specifically indicated.

The word "exemplary" is used herein to mean "serving as an example, embodiment, or illustration. Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments.

The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. In addition, the term "at least one" herein means any one of a plurality or any combination of at least two of a plurality, for example, including at least one of A, B, C, and may mean including any one or more elements selected from the group consisting of A, B and C.

Furthermore, numerous specific details are set forth in the following detailed description in order to provide a better understanding of the present disclosure. It will be understood by those skilled in the art that the present disclosure may be practiced without some of these specific details. In some instances, methods, means, elements, and circuits well known to those skilled in the art have not been described in detail in order not to obscure the present disclosure.

It should be noted that, all actions for acquiring signals, information or data in the present disclosure are performed under the condition of conforming to the corresponding data protection rule policy of the country of the location and obtaining the authorization given by the owner of the corresponding device.

In addition, in order to facilitate understanding of the present disclosure, some technical terms appearing in the present disclosure are explained or defined below:

three-level faults are one of the automobile fault grades, and are that the automobile has serious faults, and stopping assistance is needed urgently, and the faults comprise engine faults, power battery faults and the like.

Automobile fault grade, effective value of the current automobile fault grade: 0 to 3 percent of the total weight of the product, wherein,

0: indicating no fault, and displaying 00 bytes of fault codes in the normal running process;

1: representing a first-level fault, namely a fault which does not affect the running of the vehicle, and reporting 01 the data of the byte where the fault code is located;

2: representing a secondary fault, namely a fault affecting the performance of the vehicle and requiring the driver to limit the running, wherein the data is reported 10 (binary representation);

3: representing a three-level fault, namely a serious fault of the highest level of the automobile, wherein the driver should stop immediately or request assistance, and the reported data is 11 (binary representation); the faulty byte sent 0XFE indicates an exception and 0XFF indicates an invalid.

Along with the development of the internet of things of automobiles, more and more automobiles are provided with vehicle-mounted terminals (T-BOXs) which can be used for realizing vehicle cloud communication, and the information interaction between the vehicle terminals and the cloud end improves the use experience of users, meanwhile, the management of the cloud end on the vehicles is enhanced, and the traffic operation efficiency and the traffic operation safety are improved.

Because of the network disconnection or other types of vehicle faults in the running process of the vehicle, the information interaction between the vehicle-mounted terminal and the cloud end is interrupted, for example, the vehicle passes through a road section with poor network signals, the vehicle-mounted terminal is possibly disconnected, the equipment is in an off-line state, a scheme for storing data in the network disconnection period and carrying out reissue after the network connection is restored is proposed in the related technology, namely, the data which are sent in real time according to a certain time period are stored, and when the network is reconnected and the vehicle logs into a cloud platform again, the stored data are reissued while the real-time data transmission is not influenced. However, the related art also has the problems of incomplete reissue data and untimely reissue data, for example, three-level faults occur simultaneously during the network breaking period, and the data storage of a certain period of time before and after the three-level faults cannot be completely transmitted to the cloud.

In order to solve the technical problems, the disclosed embodiments provide a vehicle cloud communication data network interruption and reissue method, which has the core principle that in the process of normally sending data to a cloud end, a vehicle terminal additionally stores vehicle state data in a period of time, when a vehicle has three-level faults, the vehicle state data in a period of time after the three-level faults is sent first, then the vehicle state data in a period of time before the three-level faults is obtained according to the stored vehicle state data, and the vehicle state data in the period of time before the three-level faults is reissued. The method can enable the cloud to receive the data in the time period before and after the complete three-level fault at the first time, and can enable the cloud to perform actions such as data playback, accident analysis, rescue alarm and the like more quickly. In addition, the method can also cope with the situations that the vehicles have network disconnection events and three-level faults simultaneously or successively, and ensure the integrity and timeliness of the real-time data transmission and the data complement of the vehicles.

The embodiment of the disclosure does not limit the vehicle state data, and the vehicle state data can be whole vehicle data; vehicle component data, such as drive motor data, fuel cell data, launch data, etc., may also be used; vehicle information data, such as vehicle position data, extremum data, alarm data, etc., may also be used; user or vendor custom data is also possible. The embodiment of the disclosure is not limited to the form of acquiring the vehicle state data, that is, the vehicle state data may be acquired by the vehicle-mounted terminal through a CAN bus, an ethernet or other forms of whole vehicle communication network, or may be acquired by the vehicle-mounted terminal from other ECUs.

In some embodiments of the present disclosure, a scenario is that a vehicle is experiencing a three-level fault in a normal networked state, the vehicle is sending real-time data normally before the three-level fault occurs, the vehicle is required to send three-level fault data after the three-level fault occurs, and the vehicle state data is reissued for a period of time before the three-level fault occurs. Fig. 1 shows a flowchart of a vehicle cloud communication data outage and reissue method according to an embodiment of the present disclosure, where, as shown in fig. 1, the method includes:

S101: and under the condition that the vehicle is detected to be in a three-level fault occurrence state and the vehicle is currently in a networking state, transmitting real-time vehicle state data according to a first frequency in a first time interval after the three-level fault occurrence, and transmitting real-time vehicle state data according to a second frequency after the first time interval, wherein the first frequency is larger than the second frequency.

In the embodiment of the disclosure, the detection time of the detection is not limited to the three-level fault occurrence time, that is, the detection time may be the three-level fault occurrence time, or may be within the first time interval after the three-level fault occurs, or may be after the first time interval after the three-level fault occurs.

In the embodiment of the present disclosure, the vehicle state data in the period before and after occurrence of the three-level fault is collectively referred to as three-level fault data, and the frequency of transmitting the three-level fault data is the first frequency. Since the vehicle transmits the three-level fault data for data playback and accident analysis by the cloud, the three-level fault data has a data density, which is understood as the data amount per unit time, that should be as large as possible. That is, it is necessary to acquire as much vehicle state data as possible in a period of time before and after occurrence of the three-level fault to ensure as accurate as possible analysis of the cause of occurrence of the three-level fault, and therefore, the corresponding first frequency of transmitting the three-level fault data is increased as much as possible. For example, when an insulation failure (one of three-stage failures) of the power battery occurs, it is necessary to analyze parameters such as the output voltage, the output current, and the temperature response of the power battery and fit time-varying curves, respectively, and at this time, the more the amount of data included in the same time, the finer the fitted time-varying curve, and the more accurate the analysis of the cause of the failure.

In some embodiments of the disclosure, the first frequency is selected to be 1Hz, and the corresponding vehicle sends one piece of three-level fault data every second, and the selection of the configuration can ensure that the data density of the three-level fault data meets the requirement of analysis precision, and meanwhile, the difficulty of acquiring the three-level fault data by the vehicle-mounted terminal is not high.

In the embodiment of the disclosure, the frequency of sending the real-time vehicle state data by the vehicle in the normal state is the second frequency, and the vehicle sends the real-time data according to a certain time period in the normal state because the change amplitude of the vehicle state data in the normal state is not large, so that the problems of data repetition and data redundancy can be avoided, the difficulty of acquiring and storing the data by the vehicle-mounted terminal can be reduced, and the occupancy rate of a communication channel between the vehicle end and the cloud end can be reduced. Thus, the second frequency at which the vehicle transmits real-time vehicle state data in a normal state is configured to be smaller than the first frequency at which three-level fault data is transmitted.

S102: and in the idle time of the time interval for transmitting the real-time vehicle state data according to the second frequency, transmitting the three-level fault complement data according to the first frequency, wherein the three-level fault complement data is the vehicle state data in the second time interval before the three-level fault occurs.

In the disclosed embodiments, three levels of fault reissue data may be obtained from stored vehicle state data.

In some specific embodiments, the vehicle terminal records the vehicle state data in real time in the current formation through a random access memory (Random Access Memory, abbreviated as RAM) during each starting operation of the vehicle, and when a three-level fault occurs, the vehicle terminal returns to the gear from the random access memory to read the vehicle state data in a second time interval before the three-level fault occurs.

In other specific embodiments, the vehicle is provided with a cycle memory that stores vehicle state data in a cycle of a fixed period (e.g., one day), and when a three-level fault occurs, the vehicle-mounted terminal reads the vehicle state data from the cycle memory in a second time interval before the occurrence of the three-level fault.

In other embodiments, the vehicle is provided with a rolling memory, the rolling memory is capable of storing a fixed amount of data, and when the storage capacity of the rolling memory is full, the rolling memory stores a piece of data of the latest time and deletes a piece of stored data of the latest time, so that the data stored in the rolling memory are all the latest data.

In the embodiment of the disclosure, the vehicle transmitting the three-level fault reissue data does not affect the vehicle transmitting the real-time data. In a specific embodiment, the first frequency selection is configured to be 1Hz, the second frequency selection is configured to be 0.1Hz, the first time interval selection is configured to be 30s, the second time interval selection is configured to be 30s, based on the above configuration, the data amount of the three-level fault supplement data is 30, 1 real-time vehicle state data is transmitted every 10s by the vehicle, the default time for each transmission of the data is 1s, the remaining 9s in 10s are used for transmitting the three-level fault supplement data, that is, when the vehicle resumes normal transmission of the real-time data, the 10s is taken as a period, 9 three-level fault supplement data and 1 real-time data are transmitted every period in the first three periods, and the remaining 3 three-level fault supplement data are transmitted in the fourth period, and obviously, the supplement action occurrence period is 33s.

In some embodiments of the present disclosure, the second time interval and the first time interval are equal in length, that is, the time periods before and after the three-level fault corresponding to the three-level fault data are consistent. In a specific embodiment, the second time interval and the first time interval are each selected to be configured to be 30s. In another specific embodiment, the second time interval and the first time interval are each selected to be configured to be 60s.

In some embodiments of the present disclosure, the three-level fault reissue data is acquired based on a rolling storage approach. Fig. 2 shows a flowchart of a method for obtaining three-level fault reissue data according to an embodiment of the disclosure, as shown in fig. 2, the steps include:

s201: rolling and storing vehicle state data in a third time interval according to the first frequency, wherein the length of the third time interval is greater than or equal to that of the second time interval;

s202: detecting a three-level fault occurrence state according to a first frequency, stopping rolling storage when the three-level fault occurrence is detected, and freezing stored vehicle state data;

s203: and acquiring vehicle state data in a second time interval before the occurrence of the three-level fault from the stored vehicle state data to obtain three-level fault complement data.

According to the above embodiment, since the storage space required for the rolling storage is fixed, that is, data of a fixed length of time period is stored or a fixed amount of data is stored, the demand for the storage space can be reduced. On the other hand, the action of rolling storage is stopped along with the occurrence of the three-level fault, and at the moment, the rolling storage data, namely the vehicle state data in a period of time before the occurrence of the three-level fault, can be directly read or intercepted without carrying out additional identification or gear returning operation steps on the rolling storage data by the vehicle-mounted terminal.

In the above embodiment, the length of the third time interval may be equal to the length of the second time interval, and the data stored in a rolling manner is three-level fault complement data, that is, the data stored in a rolling manner may be directly sent when the complement data is sent; the length of the third time interval may be greater than that of the second time interval, and the data stored in a rolling manner includes three-level fault reissue data and data in an earlier time period.

In some embodiments of the present disclosure, a scenario is that a vehicle has a network disconnection event occurring simultaneously in a period of time before and after occurrence of a three-level fault, and in order to solve a problem of vehicle concurrent data in the scenario, a vehicle cloud communication data network disconnection concurrent method of the embodiments of the present disclosure further includes: and under the condition that the vehicle is detected to be in a three-level fault occurrence state and the vehicle is currently in a network disconnection state, storing vehicle state data according to a first frequency in a first time interval after the three-level fault occurrence, and storing the vehicle state data according to a second frequency after the first time interval, wherein the stored vehicle state data is the network disconnection reissue data.

In the embodiment of the present disclosure, the network disconnection should be understood in a broad sense, that is, the network disconnection may be that a vehicle disconnects the internet, or may be that the vehicle fails to log into the cloud platform, or that the vehicle fails to send data is regarded as the network disconnection.

Based on the above-described embodiments, it is understood that the vehicle is provided with a separate memory for storing vehicle state data during a period of time before occurrence of the three-level fault, and that the process of storing data by the separate memory is not affected by disconnection of the vehicle. Therefore, when a vehicle simultaneously generates a network outage event and a three-level fault, in order to ensure the integrity and timeliness of the vehicle transmission data, a problem to be solved is how to store the vehicle state data in a period of time after the three-level fault occurs. In a normal networking state, real-time vehicle state data is sent according to a first frequency in a first time interval after three-level faults occur, and correspondingly, in a broken network state, the vehicle state data is stored according to the first frequency in the first time interval after the three-level faults occur; similarly, in the off-grid state, vehicle state data is stored at a second frequency after a first time interval after the occurrence of the three-level fault. In the off-grid state, the stored vehicle state data is off-grid reissue data, and the off-grid reissue data comprises three-level fault data (data in a first time interval after the occurrence of three-level faults) and common reissue data. It should be understood that the outage and reissue data does not necessarily include three levels of fault data, and the data content included in the outage and reissue data is specifically affected by the occurrence time of the outage event and the occurrence time of the three levels of faults.

In some embodiments of the present disclosure, a vehicle has a network disconnection event before a three-level fault occurs, that is, the vehicle has a three-level fault in a network disconnection state, at this time, the vehicle starts to store network disconnection reissue data, and after the vehicle resumes networking, the vehicle performs data reissue in a sequence of preferentially sending the three-level fault reissue data until the three-level fault reissue data is completed, and then performs reissue of the network disconnection reissue data. That is, in the case where the vehicle is currently in the networking state and the vehicle stores the off-grid reissue data, the off-grid reissue data is transmitted at the first frequency after the completion of the transmission of the three-level fault reissue data at the first frequency in the idle time of the time interval in which the real-time vehicle state data is transmitted at the second frequency. Based on the configuration, after the vehicle is recovered to be networked, the cloud can timely acquire data before and after the occurrence of the three-level fault, so that the accident playback analysis is performed at the first time.

Based on the above embodiments, it can be known that the vehicle state data in the time period before and after the occurrence of the three-level fault is collectively referred to as three-level fault data, where the vehicle state data in the second time period before the occurrence of the three-level fault is three-level fault reissue data, and the vehicle state data in the first time period after the occurrence of the three-level fault may be real-time transmission data or network disconnection reissue data. When the vehicle state data in the first time interval after the occurrence of the three-level fault is the network breaking and repairing data, the sequence of the vehicle sending the three-level fault is that the three-level fault repairing data is sent firstly, and then the vehicle state data part in the first time interval after the occurrence of the three-level fault in the network breaking and repairing data is sent. Because the storage of the three-level fault reissue data and the storage of the off-network reissue data are independent of each other, when the vehicle sends the three-level fault data to the cloud, the three-level fault data need to be respectively obtained from the two memories, so that the risk of data loss caused by data cross storage exists.

To solve the above-mentioned risk, some embodiments of the present disclosure improve the above-mentioned method for acquiring three-level fault reissue data, and set the length of the third time interval to be the sum of the lengths of the first time interval and the second time interval, fig. 3 shows a flowchart of the improved method for acquiring three-level fault reissue data according to an embodiment of the present disclosure, where the method for acquiring three-level fault reissue data further includes:

s301: when the occurrence of the three-level fault is detected, recording the occurrence time of the three-level fault, and continuing to perform rolling storage;

s302: stopping rolling storage and freezing stored vehicle state data when the duration of the three-level fault occurrence state reaches the length of the first time interval;

s303: and acquiring vehicle state data in a second time interval before the occurrence of the three-level fault according to the occurrence time of the three-level fault, and obtaining three-level fault reissue data.

Based on the steps, the data in the second time interval before the occurrence of the three-level fault and the first time interval after the occurrence of the three-level fault, namely the complete three-level fault data, can be completely stored in a rolling storage mode, and when the vehicle sends the three-level fault data, the data can be obtained from a single memory, so that the difficulty of data retrieval can be reduced.

In some embodiments of the present disclosure, the outage event occurs before the occurrence of the three-level fault, and from the time of the outage event occurrence, the vehicle begins to store outage reissue data. According to some embodiments described above, the data content included in the network outage and reissue data is affected by the occurrence time of the network outage and the occurrence time of the three-level fault, and in particular, the frequency of storing the network outage and reissue data is affected by the occurrence time of the network outage and the occurrence time of the three-level fault. Fig. 4 illustrates a frequency determining method for storing the network-disconnected repair data according to an embodiment of the present disclosure, as shown in fig. 4, the method includes:

s401: detecting a network disconnection event according to a first frequency;

s402: when the occurrence of the network breaking event is detected, recording the occurrence time of the network breaking event;

s403: and determining the frequency of storing the network breaking reissue data according to the occurrence time of the network breaking event and the occurrence time of the three-stage fault.

In the embodiment of the present disclosure, since the sending and storing of the three-level fault data are both the first frequency, and the common real-time data sending and the common concurrent data storing are both the second frequency, the method for determining the frequency of storing the off-network concurrent data includes: if the occurrence time of the network break event is within the first time interval of the occurrence time of the three-level fault, storing the network break reissue data according to the second frequency; otherwise, the network-breaking reissue data are stored according to the first frequency. Based on the configuration, the storage of the off-grid reissue data is started based on the occurrence time of the off-grid event, and the frequency of storing the off-grid reissue data is changed based on the end time of the first time interval after the occurrence time of the three-stage fault. It is not difficult to find that when the network breaking event occurs before the occurrence of the three-level fault, according to the steps, the network breaking reissue data includes data of a period of time before the occurrence of the three-level fault, data of a period of time after the occurrence of the three-level fault, and common reissue data, that is, the network breaking reissue data and the three-level fault data have an intersection, and because the storage of the network breaking reissue data and the storage of the three-level fault data are independent of each other, the three-level fault data contained in the network breaking reissue data can be used as verification data or backup data, and the situation of damage of a memory corresponding to the three-level fault data can be dealt with.

In some embodiments of the present disclosure, since the vehicle sends the normal real-time data and stores the normal complementary data at the second frequency, the periods of sending the normal real-time data and storing the normal complementary data should be identical under normal conditions, for example, when the second frequency is selected to be 0.1Hz, the period is 10s, and assuming that the 1 st s of each period sends data, in a certain period, after the 1 st s sends data, the vehicle breaks the network at the 5 th s, and in the 1 st s of the next period, the vehicle stores a broken network complementary data. It will be appreciated that based on the above configuration, the vehicle, after resuming networking, still transmits ordinary real-time data according to the period before the network disconnection. However, the configuration has the defect that when the distance between the periodic position of the occurrence time of the network disconnection event and the periodic position of the recovery networking time is large, namely the interval between the data stored after the network disconnection and the normal transmission data before the network disconnection is large, the data is incomplete easily caused; on the other hand, when the vehicle has three-level fault in the broken network state, the vehicle stores three-level fault data immediately according to the first frequency, that is, the period for storing three-level fault data is intersected with the period for storing common reissue data, which also increases the difficulty of processing the reissue data in the sun. In order to eliminate the above-mentioned drawbacks, when the network-disconnection repairing data is stored at the second frequency, the occurrence time of the network-disconnection event may be used as the period start time corresponding to the second frequency.

In order to more intuitively illustrate the vehicle cloud communication data network interruption and reissue method of the embodiment of the present disclosure, the present disclosure provides a specific embodiment, where the embodiment may completely show a data processing method of a vehicle in various running states, and in this embodiment, a first frequency is 1Hz, a second frequency is 0.1Hz, a first time interval is 30s, a second time interval is 30s, a third time interval is 30s, and a default detection time for occurrence of a three-level fault is 1s. Fig. 7 is a flowchart illustrating data transmission of a vehicle according to an embodiment of the present disclosure, as shown in fig. 7, in which the vehicle performs integration of vehicle state data at a speed of once per second and stores the vehicle state data for the last 30 seconds by rolling at a speed of one piece per second when the vehicle starts running, and at the same time, the vehicle detects a network outage event and a three-level fault every second and adjusts a data processing strategy according to the detection results of the network outage event and the three-level fault, including:

the method comprises the steps that a network breaking event and a three-level fault are not detected, the state that the network breaking event and the three-level fault do not occur is a normal state, and under the normal state, a piece of real-time vehicle state data is sent to a cloud end every 10 seconds by a vehicle, namely the second frequency of the real-time data sent by the vehicle is 0.1Hz, and the corresponding sending period is 10s;

Only detecting a network disconnection event, and detecting no three-level faults before the vehicle resumes networking, namely only generating a normal network disconnection state of the network disconnection event, storing one piece of vehicle state data every 10s by the vehicle after the network disconnection event, namely, storing the second frequency of the network disconnection reissue data by the vehicle to be 0.1Hz, and sending one piece of real-time vehicle state data to the cloud every 10 seconds after the vehicle resumes networking, and sending the network disconnection reissue data at a speed of 1 piece per second in idle time of a sending period by the vehicle.

Only three-level faults are detected, no network break event is detected within 30s before the occurrence of the three-level faults and within 30s after the occurrence of the three-level faults, namely, the vehicle is in a three-level fault in a networking state, rolling storage is stopped when the occurrence of the three-level faults is detected, stored data, namely, three-level fault reissue data, are frozen, the vehicle transmits real-time vehicle state data to the cloud every 1 second within 30s after the occurrence of the three-level faults, namely, the first frequency of the vehicle transmitting the real-time data is 1Hz, the vehicle transmits real-time vehicle state data to the cloud every 10 seconds after the occurrence of the three-level faults, and the three-level fault reissue data is transmitted at a speed of 1 second within the idle time of a transmission period.

After the network breaking event is detected, and three-level faults are detected before the vehicle is recovered to be networked, namely, the vehicle is in the three-level faults under the network breaking state, when the occurrence of the three-level faults is detected, rolling storage is stopped, stored data, namely, three-level fault reissue data is frozen, and at the moment, the data processing strategy adjustment judgment comprises,

if the vehicle recovery networking is not detected within 30s after the three-level fault occurs, the vehicle stores one piece of vehicle state data every 1 second, namely three-level fault network breaking data, after the three-level fault occurs for 30s, the vehicle stores one piece of vehicle state data every 10 seconds, namely common reissue data, until the vehicle recovers the networking, the vehicle sends one piece of real-time vehicle state data to the cloud every 10 seconds after the vehicle recovers the networking, and in the idle time of a sending period, 30 pieces of three-level fault reissue data, 30 pieces of three-level fault network breaking data and common reissue data are sequentially sent at a speed of 1 piece per second;

if the vehicle recovery networking is detected within 30s after the three-level fault occurs, the vehicle stores one piece of vehicle state data every 1 second in a time interval from the three-level fault occurrence time to the vehicle recovery networking time, namely three-level fault network breaking data, after the vehicle recovery networking, the vehicle sends one piece of real-time vehicle state data to the cloud every 1 second in the time interval from the vehicle recovery networking time to the 30s after the three-level fault occurs, the vehicle sends one piece of real-time vehicle state data to the cloud every 10 seconds after the 30s after the three-level fault occurs, and the three-level fault complement data and the three-level fault network breaking data are sequentially sent at a speed of 1 piece per second in the idle time of a sending period.

After the occurrence of the three-level fault is detected, the occurrence of the network breaking event is detected, namely, the vehicle breaks the network after the occurrence of the three-level fault, if the occurrence time of the network breaking event is within 30s after the occurrence of the three-level fault, the vehicle sends a piece of real-time vehicle state data to the cloud every 1 second after the occurrence time of the three-level fault to the occurrence time of the network breaking event, the vehicle stores a piece of vehicle state data every 1 second, namely, the network breaking data of the three-level fault, and stores a piece of vehicle state data every 10 seconds, namely, ordinary complement data, after the occurrence time of the three-level fault is 30s after the occurrence time of the three-level fault until the vehicle is recovered to the network.

If the occurrence time of the network break event is 30s after the occurrence of the three-level fault, the vehicle sends a piece of real-time vehicle state data to the cloud end every 1 second within 30s after the occurrence of the three-level fault, the vehicle sends a piece of real-time vehicle state data to the cloud end every 10 seconds until the occurrence time of the network break event after the occurrence of the three-level fault, the three-level fault complement data is sent at a speed of 1 piece per second within the idle time of a sending period, the un-sent three-level fault complement data is stored after the vehicle breaks the network, and a piece of vehicle state data, namely ordinary complement data, is stored every 10 seconds until the vehicle is recovered to be networked.

The disclosure also provides a specific embodiment, which realizes the vehicle cloud communication data off-network reissue method through a software application example of the vehicle terminal. Fig. 5 shows a flowchart of a software implemented method according to an embodiment of the present disclosure, as shown in fig. 5, including the steps of:

s501: a setup memory, comprising,

the network breaking data storage is used for storing vehicle state data in a rolling way when the vehicle breaks the network, and can store 360 pieces of data in a rolling way or store 3 days of data in a rolling way;

the three-level fault memory is used for storing the latest 30s data in a rolling way so as to upload the vehicle data 30s before the fault occurrence point when the three-level fault alarm occurs.

S502: the setting judging module comprises a setting judging module, wherein the setting judging module comprises,

the network connection state judging module is used for judging the network connection state of the vehicle-mounted terminal;

the vehicle login state judging module judges whether a vehicle logs in the cloud platform or not;

and the three-level fault alarm state judging module is used for calculating three-level faults and giving an alarm.

Only the vehicle-mounted terminal is connected with the network and the vehicle logs in the cloud platform, the vehicle is in a networking state, and otherwise, the vehicle is in a network disconnection state.

S503: a counter is set, including,

network disconnection storage counter: counting for 10 seconds according to the frequency of 0.1Hz, and storing data by a network disconnection data storage device;

Normal transmission counter: counting according to the frequency of 0.1Hz, counting for 10 seconds, and sending data by the vehicle;

three-stage fault transmission counter: and after the three-level fault occurs, 30s of real-time data are transmitted according to 1Hz, the data in 30 seconds before the fault occurs are reissued in the interval of 30-63 s of the counter, and the transmission period is 9 every 10 seconds.

S504: setting the running flow of the software, including,

a. calling a data transmission function with a second as a period;

b. the real-time data is packaged, and the packaged data is vehicle state data;

c. defining a counter;

d. rolling and storing 30s data by using a three-level fault alarm memory so as to upload vehicle data 30s before a fault occurrence point when three-level fault alarm occurs;

e. judging whether the vehicle is in a networking state or not;

f. according to the networking state judgment result, executing the corresponding steps:

1) If the vehicle is failed to log in or disconnected from the network:

judging condition 1: three-level alarming occurs and the three-level fault count is less than 30; task 1 is performed: the network breaking data is stored once per second, and the three-level fault sending counter counts.

Judging condition 2: the broken network counter counts to 10; task 2 is performed: the off-network data is stored every ten seconds, and the counter is stored to 0.

And finally, executing the task: the off-grid storage counter counts.

2) If the vehicle logs in successfully and is networked:

judging condition 1: three-level alarming occurs and the three-level fault count is less than 30; task 1 is performed: real-time data is sent every second, a counter is normally sent to 0, and a three-level fault sending counter counts.

Judging condition 2: the normal transmission counter counts to 10; task 2 is performed: and sending real-time information data, and normally sending a counter to 0.

Judging condition 3: a step of reissuing alarm data; performing task 3: and (3) data 30 seconds before the reissue alarm, clearing a fault mark after reissuing 30 data, and sending a counter to 0 by three stages of faults.

Judging condition 4: storing data in the presence of a broken network; task 4 is performed: and performing network disconnection storage reissue in a data normal transmission interval.

And finally, executing the task: the normal transmission counter counts.

Some embodiments of the present disclosure further provide a vehicle cloud communication data network interruption and reissue device, as shown in fig. 6, where the device includes:

the communication module 101 is used for networking and logging in the cloud platform to send vehicle state data;

the off-grid storage module 102 is used for storing vehicle state data when the vehicle is off-grid;

a three-level fault storage module 103 for storing vehicle state data in a second time interval before occurrence of a three-level fault;

The detection module 104 is configured to detect a networking state of the vehicle and a three-level fault occurrence state of the vehicle.

Some embodiments of the present disclosure further provide a vehicle, where a set of instruction sets is stored, where the instruction sets are executed by the vehicle, so as to implement a vehicle cloud communication data network disconnection and reissuing method described in the foregoing embodiments.

In some embodiments, functions or modules included in an apparatus provided by the embodiments of the present disclosure may be used to perform a method described in the foregoing method embodiments, and specific implementations thereof may refer to descriptions of the foregoing method embodiments, which are not repeated herein for brevity.

The embodiment of the disclosure also provides a computer readable storage medium, wherein at least one instruction or at least one section of program is stored in the computer readable storage medium, and the at least one instruction or the at least one section of program realizes the method when being loaded and executed by a processor. The computer readable storage medium may be a non-volatile computer readable storage medium.

The embodiment of the disclosure also provides an electronic device, which comprises: a processor; a memory for storing processor-executable instructions; wherein the processor is configured as the method.

The electronic device may be provided as a terminal, server or other form of device.

The foregoing description of the embodiments of the present disclosure has been presented for purposes of illustration and description, and is not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the various embodiments described. The terminology used herein was chosen in order to best explain the principles of the embodiments, the practical application, or the technical improvements in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.

Claims (10)

1. The vehicle cloud communication data network interruption reissue method is characterized by comprising the following steps of:

transmitting real-time vehicle state data according to a first frequency in a first time interval after three-level fault occurrence under the condition that the vehicle is detected to be in a three-level fault occurrence state and the vehicle is currently in a networking state, and transmitting real-time vehicle state data according to a second frequency after the first time interval, wherein the first frequency is larger than the second frequency;

and in the idle time of the time interval for transmitting the real-time vehicle state data according to the second frequency, transmitting the three-level fault complement data according to the first frequency, wherein the three-level fault complement data is the vehicle state data in the second time interval before the three-level fault occurs.

2. The method according to claim 1, wherein the method further comprises:

and under the condition that the vehicle is detected to be in a three-stage fault occurrence state and the vehicle is currently in a network disconnection state, storing vehicle state data according to the first frequency in a first time interval after the three-stage fault occurrence, and storing the vehicle state data according to the second frequency after the first time interval, wherein the stored vehicle state data is the network disconnection reissue data.

3. The method according to claim 1, wherein the method further comprises:

and in the idle time of a time interval of transmitting real-time vehicle state data according to a second frequency under the condition that the vehicle is currently in a networking state and the vehicle stores network-breaking reissue data, transmitting the network-breaking reissue data according to the first frequency after the transmission of three-level fault reissue data according to the first frequency is completed.

4. A method according to any one of claims 1-3, wherein the three-level fault reissue data is obtained based on the steps of:

rolling and storing vehicle state data in a third time interval according to the first frequency, wherein the length of the third time interval is greater than or equal to that of the second time interval;

Detecting a three-level fault occurrence state according to the first frequency, stopping rolling storage when the three-level fault occurrence is detected, and freezing stored vehicle state data;

and acquiring vehicle state data in a second time interval before the occurrence of the three-level fault from the stored vehicle state data to obtain the three-level fault complement data.

5. The method of claim 4, wherein the length of the third time interval is equal to the sum of the lengths of the first time interval and the second time interval;

the steps further include:

when the occurrence of the three-level fault is detected, recording the occurrence time of the three-level fault, and continuing to perform rolling storage;

stopping rolling storage and freezing stored vehicle state data when the duration of the three-level fault occurrence state reaches the length of the first time interval;

and acquiring vehicle state data in a second time interval before the occurrence of the three-level fault according to the occurrence time of the three-level fault, and obtaining the three-level fault reissue data.

6. The method of claim 5, wherein the method further comprises:

detecting a network disconnection event according to the first frequency;

When the occurrence of the network breaking event is detected, recording the occurrence time of the network breaking event;

and determining the frequency of storing the network breaking concurrent data according to the occurrence time of the network breaking event and the occurrence time of the three-level fault.

7. The method of claim 6, wherein determining the frequency of storing the outage reissue data based on the outage event time and the three-level fault time comprises:

if the occurrence time of the network outage event is within a first time interval of the occurrence time of the three-level fault, storing the network outage reissue data according to the second frequency; otherwise, storing the network-disconnected concurrent data according to the first frequency.

8. The method according to claim 7, wherein: the step of storing the network-disconnected reissue data according to the second frequency comprises the following steps:

and taking the occurrence time of the network break event as the period starting time corresponding to the second frequency.

9. The utility model provides a car cloud communication data breaks net and reissues device which characterized in that includes:

the communication module is used for networking and logging in the cloud platform to send vehicle state data;

the network disconnection storage module is used for storing vehicle state data when the vehicle is disconnected;

The three-level fault storage module is used for storing vehicle state data in a second time interval before the three-level fault occurs;

and the detection module is used for detecting the networking state of the vehicle and the three-level fault occurrence state of the vehicle.

10. A vehicle, characterized by comprising:

a storage device for storing computer executable instructions; the method comprises the steps of,

processing means for accessing said storage means and executing said computer executable instructions to perform the operations in the method according to any of claims 1-8.