Device restart method, electronic device, and vehicle

Abstract

This application provides a device restart method, an electronic device, and a vehicle. The method involves configuring a receiver to parse a location data frame into at least one sub-packet when it receives the frame, and resetting a timer to time the receiver's reporting of the location data frame. During the receiver's sequential reporting of the sub-packets corresponding to the location data frame, each sub-packet corresponds to a maximum reporting duration. This avoids the problem of continuously retrying to report a sub-packet due to reporting failure, which could prevent the sub-packets from being reported within the predetermined total reporting duration for each frame, thus causing the receiver to restart. Specifically, each sub-packet corresponds to a maximum reporting duration to prevent the reporting duration of a sub-packet from being extended indefinitely, thereby reducing the receiver's restart frequency and improving user experience.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and in particular to a device restart method, electronic equipment, and vehicle. Background Technology

[0002] After acquiring positioning data, the positioning service process (mnld process) in the GNSS (Global Navigation Satellite System) module needs to packetize the positioning data and report it to the upper-layer application. This process usually sets a fixed timer. If the report is not successfully reported within the fixed time period, the GNSS module is triggered to time out and restart.

[0003] In practical applications, if the reporting of a packet of positioning data fails due to blockage in the upper-layer application, the GNSS module will keep retrying to report the packet, causing it to time out and restart. This method of reporting packet data, which involves retrying to report packet data without limit, can easily lead to frequent timeouts and restarts of the GNSS module, affecting the user experience. Summary of the Invention

[0004] In view of this, the purpose of this application is to provide a device restart method, electronic device and vehicle to solve or partially solve the problems mentioned in the background art.

[0005] To achieve the above objectives, this application provides a device restart method, comprising:

[0006] In response to the receiver receiving a frame of location data, the location data is parsed into at least one packet of data, and the timer is reset; each packet of data is reported sequentially; in response to determining that the timer has reached a predetermined total reporting time during the reporting of each packet of data, the receiver is restarted; wherein, each frame of location data corresponds to a predetermined total reporting time; the reporting time of each packet of data is less than or equal to its corresponding maximum reporting time; the maximum reporting time is less than the predetermined total reporting time.

[0007] The aforementioned device restart method sets a maximum reporting time for each data packet to prevent continuous retrying of reporting a single data packet due to reporting failure. This avoids situations where the data packets corresponding to the positioning data frame cannot be reported within the predetermined total reporting time for each positioning data frame, thus causing the receiver to restart. In other words, setting a maximum reporting time for each data packet prevents the reporting time of a single data packet from being extended indefinitely, causing the reporting time of the positioning data frame to reach the predetermined total reporting time and resulting in a receiver restart. This method helps reduce the receiver restart frequency and improves the user experience.

[0008] Furthermore, the sequential reporting of each of the sub-packet data includes: The reporting order of each sub-packet data is determined, and each sub-packet data is reported sequentially based on the reporting order; in response to the failure to report a sub-packet data, the reporting of the sub-packet data is retried within the maximum reporting time; in response to the failure to report a sub-packet data within the maximum reporting time, the next sub-packet data is reported; in response to the successful reporting of a sub-packet data within the maximum reporting time, the next sub-packet data is reported.

[0009] The above technical solution can ensure the reporting order of each packet of data and ensure that the maximum reporting time of each packet of data is within the maximum reporting time. This avoids the situation where the reporting time reaches the predetermined total reporting time corresponding to the positioning data of that frame due to the failure of reporting one packet of data, which would cause the receiver to time out and restart. This helps to reduce the probability of the receiver timeout and restart during the reporting of the packet of data.

[0010] Furthermore, determining the reporting order of each of the sub-packet data includes: The reporting order of the at least one sub-packet data is determined based on the data type of each sub-packet data; or, the reporting order of the at least one sub-packet data is determined based on the byte size of the at least one sub-packet data.

[0011] The above technical solution can achieve orderly reporting of data from each sub-package, avoiding congestion of the reporting path.

[0012] Furthermore, the receiver is located on the vehicle, and the method further includes: The vehicle's driving status is obtained; in response to determining that the driving status is driving, the predetermined total reporting time is determined to be a first time; in response to determining that the driving status is parked, the predetermined total reporting time is determined to be a second time; wherein, the first time is less than the second time.

[0013] The above technical solution sets different tolerance levels for location data reporting for vehicles under different driving conditions, reflecting the adaptability of location data reporting to the environment, which is conducive to improving user experience.

[0014] Furthermore, the step of retrying to report the packet data within the maximum reporting duration includes: Determine the network signal quality; determine the number of retries for the packet data based on the network signal quality; retry and report the packet data within the maximum reporting time according to the number of retries; wherein, the stronger the network signal quality, the more retries are made.

[0015] The above technical solution determines the number of times the packet data can be retried within the maximum reporting time based on the network signal quality where the receiver is located. This helps to ensure the orderliness and reliability of the packet data retried and reported, and improves the practicality of the method.

[0016] Furthermore, the method also includes: In response to determining that the timer has not reached the predetermined total reporting duration after each packet of data has been reported, the timer is reset and it is determined whether a new frame of location data has been received; in response to not receiving a new frame of location data and the timer reaching the predetermined total reporting duration, the receiver is restarted.

[0017] In the above technical solution, the timer can time whether the receiver receives a new frame of positioning data after completing the reporting of each packet of data, thereby realizing the turn-by-turn monitoring of the data transmission of the receiver, which is beneficial to improving the continuity and reliability of the data transmission of the receiver.

[0018] Furthermore, the step of retrying to report the packet data within the maximum reporting duration includes: The number of retries is determined based on the data type of the sub-packet data; wherein, the higher the criticality of the data type of the sub-packet data, the more retries are made; the sub-packet data is retried and reported within the maximum reporting time according to the number of retries.

[0019] The above technical solution determines the number of times the sub-packet data can be retried within the maximum reporting time based on the data type of the sub-packet data. This ensures a high success rate for retrying the reporting of critical sub-packet data within the maximum reporting time, thereby improving the practicality of the method.

[0020] Furthermore, the maximum reporting duration is equal to the quotient of the predetermined total reporting duration and the number of sub-package data; or, the maximum reporting duration is a preset duration; or, the maximum reporting duration is less than the quotient of the predetermined total reporting duration and the number of sub-package data.

[0021] The above technical solution provides three methods for determining the maximum reporting time. Each method can reduce the probability of the receiver timeout restarting during the reporting of the packet data to a certain extent. In practical applications, the corresponding method for determining the maximum reporting time can be set according to application needs to meet user needs, improve user experience, and enhance the practicality of the method.

[0022] Based on the same inventive concept, this disclosure also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable by the processor, wherein the processor implements the method described above when executing the computer program.

[0023] Based on the same inventive concept, this disclosure also provides a vehicle including an electronic device as described above.

[0024] As can be seen from the above, the device restart method, electronic device, and vehicle provided in this application involve setting the receiver to parse a frame of positioning data into at least one sub-packet when it receives a frame of positioning data, and resetting the timer to time the receiver's reporting of the frame of positioning data. During the process of the receiver sequentially reporting each sub-packet of positioning data corresponding to the frame of positioning data, each sub-packet of data corresponds to a maximum reporting time. This avoids the problem of continuously retrying to report the sub-packet of data due to the failure of reporting a sub-packet of data, which would prevent the sub-packets of data corresponding to the frame of positioning data from being reported within the predetermined total reporting time corresponding to each frame of positioning data, thus causing the receiver to restart. That is, each sub-packet of data corresponds to a maximum reporting time to avoid the reporting time of a sub-packet of data being extended indefinitely, causing the reporting time of the frame of positioning data to reach the predetermined total reporting time, thus causing the receiver to restart. This helps to reduce the restart frequency of the receiver and improve the user experience. Attached Figure Description

[0025] To more clearly illustrate the technical solutions in this application or related technologies, the drawings used in the description of the embodiments or related technologies will be briefly introduced below. Obviously, the drawings described below are only embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0026] Figure 1 This is a schematic flowchart of a device restart method according to an embodiment of this application; Figure 2 This is a schematic diagram of the structure of a device restart system according to an embodiment of this application; Figure 3 This is a schematic diagram of the structure of an electronic device according to an embodiment of this application. Detailed Implementation

[0027] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with specific embodiments and the accompanying drawings.

[0028] It should be noted that, unless otherwise defined, the technical or scientific terms used in the embodiments of this application should have the ordinary meaning understood by one of ordinary skill in the art to which this application pertains. The terms "first," "second," and similar terms used in the embodiments of this application do not indicate any order, quantity, or importance, but are merely used to distinguish different components. Terms such as "comprising" or "including" mean that the element or object preceding the word encompasses the elements or objects listed after the word and their equivalents, without excluding other elements or objects. Terms such as "connected" or "linked" are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect. Terms such as "upper," "lower," "left," and "right" are only used to indicate relative positional relationships; when the absolute position of the described object changes, the relative positional relationship may also change accordingly.

[0029] As described in the background section, after receiving positioning data, the GNSS module uses the mnld process to divide the positioning data into packets to obtain multiple packets of positioning data. The mnld process typically divides the positioning data into packets based on each frame. Consequently, it limits the reporting time of each frame of positioning data. By identifying the reporting time of each frame of positioning data, it can determine whether there is a data transmission congestion problem. If a data transmission congestion problem is found, the GNSS module can be restarted to resolve the congestion problem.

[0030] However, during the reporting of each data packet, there is no limit to the reporting time of each data packet. When a data packet fails to be reported, it will be retried indefinitely until it is successfully reported. This will cause the reporting time of the data packet to be too long, which will make it easy for the reporting time of the corresponding positioning data frame to reach the time limit. This will easily lead to frequent restarts of the GNSS module, frequent interruptions of the GNSS module's positioning service, and affect the user experience.

[0031] Based on this, this application proposes a device restart method, electronic device, and vehicle. By setting a maximum reporting time for each data packet, the problem of restarting due to excessive reporting time for a single data packet is avoided, which helps to reduce the restart frequency and improve the user experience.

[0032] The embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0033] In some embodiments, such as Figure 1 As shown, this application provides a device restart method applied to a controller, the method comprising: Step S101: In response to the receiver receiving a frame of positioning data, the positioning data is parsed into at least one packet of data, and the timer is reset.

[0034] Specifically, the receiver can be a GNSS module, an MNLD process, or other structures used to receive and packetize data. The transmission unit of the positioning data is a frame. That is, after receiving a frame of positioning data, the receiver will parse the frame of positioning data into packets to obtain at least one packet of data. The basis for packet parsing can be field size or field type. When the receiver receives the positioning data, it resets the timer to count down for reporting the received frame of positioning data.

[0035] Step S102: Report the data of each sub-packet in sequence.

[0036] Specifically, the receiver sorts the at least one data packet to determine the reporting order of each data packet, and reports each data packet sequentially according to this reporting order. During the reporting process, each data packet corresponds to a maximum reporting time for reporting. That is, the reporting time of each data packet can be less than or equal to its corresponding maximum reporting time, but cannot exceed its corresponding maximum reporting time. This avoids the problem of a data packet continuously failing to report and retrying, resulting in an excessively long reporting time for a single data packet, thus limiting the reporting time of a single data packet.

[0037] It should be noted that if a sub-packet of data fails to be successfully reported within its corresponding maximum reporting time, the sub-packet of data is discarded in order to complete the processing of the sub-packet of data and facilitate the reporting of the next sub-packet of data.

[0038] Step S103: In response to determining that the timer has reached a predetermined total reporting duration during the reporting of each packet of data, the receiver is restarted; wherein, each frame of positioning data corresponds to a predetermined total reporting duration; the reporting duration of each packet of data is less than or equal to its corresponding maximum reporting duration; the maximum reporting duration is less than the predetermined total reporting duration.

[0039] Specifically, during the reporting process of each of the sub-packet data, the timer continues to count. If the timer reaches the predetermined total reporting time during the reporting process of each of the sub-packet data, it is determined that the reporting time of the location data corresponding to each sub-packet data has expired, which may be due to data transmission congestion or blockage. The receiver needs to be restarted to resolve the data transmission congestion and blockage problem.

[0040] It should be noted that the reporting duration of each data packet is limited by its corresponding maximum reporting duration. This prevents the receiver from restarting due to the timer reaching the predetermined total reporting duration caused by the failure to report a single data packet, thus reducing the restart probability to a certain extent. Furthermore, the predetermined total reporting duration limits the reporting duration of each frame of positioning data, and the maximum reporting duration limits the reporting duration of a single data packet. Each frame of positioning data includes at least one data packet, therefore the maximum reporting duration is less than the predetermined total reporting duration.

[0041] The predetermined total reporting duration can be a fixed value, meaning the predetermined total reporting duration is the same for each frame of positioning data. Alternatively, the predetermined total reporting duration can be a variable value, meaning the predetermined total reporting duration for each frame of positioning data differs under different conditions. For example, the predetermined total reporting duration for each frame of positioning data is 60 seconds when the vehicle is moving and 70 seconds when the vehicle is parked. The maximum reporting duration for each packet of positioning data corresponding to each frame can be a fixed value or a variable value. When it is a fixed value, the maximum reporting duration for the packet of positioning data corresponding to different frames is the same. When it is a variable value, the maximum reporting duration for the packet of positioning data corresponding to different frames is different.

[0042] The number of data packets corresponding to each frame of positioning data is different. When the maximum reporting time of each data packet corresponding to each frame of positioning data is a fixed value, and the number of data packets corresponding to a frame of positioning data is less than the quotient of the predetermined total reporting time and the maximum reporting time of the data packet, even if the reporting time of each data packet corresponding to the positioning data of that frame is the maximum reporting time, or if all reporting fails, the timer will not reach the predetermined total reporting time during the reporting process of each data packet corresponding to the positioning data of that frame, and thus the receiver will not restart, reducing the restart frequency.

[0043] For example, the number of data packets corresponding to one frame of positioning data is 59, the maximum reporting time for each data packet is 1 second, and the predetermined total reporting time is 60 seconds. When the actual reporting time of the 59 data packets is the maximum reporting time, the reporting time of each data packet is the maximum reporting time of 1 second. 1 second × 59 = 59 seconds. 59 seconds < the predetermined total reporting time of 60 seconds. Since the reporting time of this frame of positioning data does not exceed the predetermined total reporting time, the receiver will not restart.

[0044] The number of data packets corresponding to each frame of positioning data is different. When the maximum reporting time for each data packet corresponding to each frame of positioning data is a variable value, that is, the maximum reporting time for the data packet corresponding to a frame of positioning data is the quotient of the predetermined total reporting time and the number of data packets, the timer will reach the predetermined total reporting time during the reporting process of each data packet corresponding to the frame of positioning data only when the actual reporting time of each data packet corresponding to the frame of positioning data is the maximum reporting time, or when all reporting fails. This will reduce the frequency of receiver restart.

[0045] For example, the maximum reporting time corresponding to the sub-packet data is a variable value. When the vehicle is in a driving state, the predetermined total reporting time is 50 seconds. When the vehicle is in a parked state, the predetermined total reporting time is 60 seconds. In the scenario where one frame of positioning data corresponds to 55 sub-packets and the upper-layer application is blocked and cannot report successfully, the predetermined total reporting time of 50 seconds or 60 seconds will trigger a timeout restart when the timer reaches the predetermined total reporting time, thus keeping the restart probability constant.

[0046] In this embodiment, when the receiver receives a frame of positioning data, it parses the frame into at least one data packet and resets the timer to time the receiver's reporting of the positioning data frame. During the receiver's sequential reporting of the data packets corresponding to the positioning data frame, each data packet corresponds to a maximum reporting duration. This avoids the problem of continuously retrying to report a data packet due to a failure to report it, which would prevent the data packets corresponding to the positioning data frame from being reported within the predetermined total reporting duration for each frame, thus causing the receiver to restart. In other words, each data packet corresponds to a maximum reporting duration to prevent the reporting duration of a data packet from being extended indefinitely, causing the reporting duration of the positioning data frame to reach the predetermined total reporting duration and thus causing the receiver to restart. This helps reduce the receiver's restart frequency and improves the user experience.

[0047] In some embodiments, step S102: the sequential reporting of each of the sub-packet data includes: Step S201: Determine the reporting order of each of the sub-packet data, and report each of the sub-packet data sequentially based on the reporting order.

[0048] Specifically, when the receiver reports each of the sub-packet data in sequence, it first determines the reporting order of each of the sub-packet data, and then reports each of the sub-packet data in sequence according to the reporting order.

[0049] The reporting order of each packet data can be based on the data type of the packet data or the byte size of the packet data.

[0050] In step S202, in response to the failure of reporting one of the sub-packet data, the sub-packet data is retried within the maximum reporting time.

[0051] Specifically, when the receiver reports a packet of data, it determines whether the packet of data has been successfully reported based on whether it receives a successful reporting message from the upper-layer application. Alternatively, it can determine whether the packet of data has been successfully reported based on whether it has been successfully stored in the storage area corresponding to the upper-layer application. Thus, when the receiver reports the packet of data once, it can obtain the reporting result of the packet of data in a timely manner.

[0052] If the receiver determines that the reported sub-packet data has failed to be reported, it will retry reporting the sub-packet data based on the maximum reporting time corresponding to the sub-packet data, in order to make every effort to successfully report the sub-packet data.

[0053] It should be noted that when the receiver reports a packet of data, it starts a timer for reporting the packet to determine the reporting duration of that packet and monitor it to prevent it from exceeding the maximum reporting duration. If the receiver determines that a packet of data has been successfully reported and the reporting duration has not exceeded the maximum reporting duration, it resets the timer to zero to begin timing the reporting duration of the next packet of data.

[0054] The timer is used to determine the reporting duration of a frame of positioning data reported by the receiver, and the timer is used to determine the reporting duration of a packet of data reported by the receiver. The two operate independently and do not affect each other.

[0055] Step S203: In response to the failure to report all of the sub-packet data within the maximum reporting time, the next sub-packet data is reported.

[0056] Specifically, if the receiver reports a packet of data for a maximum duration, and all packets of data fail to be reported, the packet of data is discarded, and the next packet of data is reported in the reporting order. Discarding the packet of data is a way to handle the failed packet of data, so as to process the packet of data and avoid the receiver always having unprocessed packet of data, which would affect the normal reporting of subsequent packet of data.

[0057] It should be noted that discarded sub-package data can be recorded in the logs for subsequent troubleshooting and data analysis.

[0058] Step S204: In response to the successful reporting of one of the sub-packet data within the maximum reporting time, the next sub-packet data is reported.

[0059] Specifically, if the receiver successfully reports a packet of data and the reporting time is less than the maximum reporting time, then the packet of data is determined to have been reported successfully. The processing result of the packet of data is reported, and the receiver then reports the next packet of data in the reporting order to complete the reporting of at least one packet of data.

[0060] It should be noted that the process of the receiver reporting the packet data is the process of reporting the packet data to the upper-layer application or the cache space corresponding to the upper-layer application, so as to realize the transmission of the packet data.

[0061] In addition, the maximum reporting time in this embodiment is the maximum reporting time corresponding to the reported sub-packet data.

[0062] In this embodiment, when the receiver reports a packet of data, if the reporting fails, it retryes reporting the packet of data within the maximum reporting time. If the reporting is successful, it reports the next packet of data in the reporting order. If all packet data reports fail within the maximum reporting time, the packet of data is discarded, and the next packet of data is reported in the reporting order. This achieves processing of the packet of data within the maximum reporting time. The processing result can be successful reporting or discarding, realizing closed-loop processing of each packet of data and avoiding the situation where the processing result is suspended. This avoids the situation where the reporting time reaches the predetermined total reporting time corresponding to the positioning data of the frame due to the failure of reporting a packet of data, causing the receiver to time out and restart. This helps to reduce the probability of the receiver timeout and restart during the reporting of the packet of data.

[0063] In some embodiments, step S201: determining the reporting order of each of the sub-packet data includes: Step S301: Determine the reporting order of the at least one sub-packet data based on the data type of each sub-packet data.

[0064] Specifically, each frame of positioning data includes multiple types of data. When parsing the positioning data, the receiver parses it into at least one data packet according to the type of data in the frame. That is, different data packets correspond to different data types. When determining the reporting order, the receiver determines the criticality of different data types of data packets according to a pre-stored data type and criticality comparison table, and determines that the reporting order of the data packets with higher criticality is prioritized, thereby realizing the determination of the reporting order according to the criticality of the data packets.

[0065] For example, a frame of location data includes data with statement types GGA and GSV. The receiver then parses the frame of location data into packet data with data type GGA and packet data with data type GSV. Based on a pre-stored data type and criticality comparison table, it is determined that GGA has a higher criticality than GSV. Therefore, the reporting order is packet data with data type GGA > packet data with data type GSV.

[0066] Step S302: Determine the reporting order of the at least one packet of data based on the byte size of the at least one packet of data.

[0067] Specifically, each frame of positioning data includes multiple types of data. When parsing the positioning data, the receiver parses it into at least one packet of data according to the type of data in the frame. That is, different packets correspond to different data types. When determining the reporting order, the receiver determines the reporting order according to the byte size of the packet data, that is, the larger bytes are reported first.

[0068] For example, a frame of positioning data includes data of statement type GGA and GSV. Then, the receiver parses the frame of positioning data into packet data of data type GGA and packet data of data type GSV. The byte size of the two packet data is determined, and the byte size of the packet data of data type GGA is 8 bytes and the byte size of the packet data of data type GSV is 10 bytes. Then, the reporting order is packet data of data type GGA < packet data of data type GSV.

[0069] In this embodiment, when determining the reporting order of each packet data, it can be determined according to the data type of the packet data or the byte size of the packet data, so as to achieve orderly reporting of each packet data. This is beneficial to improve the orderliness of the receiver when reporting the packet data, thereby avoiding the situation where the packet data is reported out of order, causing the reporting path to be blocked and resulting in timeout restart.

[0070] In some embodiments, the receiver is located on a vehicle, and the method further includes: Step S401: Obtain the vehicle's driving status.

[0071] Specifically, when the receiver is located on the vehicle, the vehicle controller obtains the vehicle's speed and thus the vehicle's driving status. When the vehicle's speed is 0, the vehicle's driving status is determined to be parked; when the vehicle's speed is not 0, the vehicle's driving status is determined to be moving.

[0072] Step S402: In response to determining that the driving state is driving, the predetermined total reporting time is determined to be the first time.

[0073] Specifically, when the receiver determines that the driving state is in motion, it determines the smaller of the first and second durations as the predetermined total reporting duration. The first duration is less than the second duration. Therefore, when the driving state is in motion, the first duration is determined as the predetermined total reporting duration. This ensures the efficiency of transmitting the positioning data during vehicle operation and avoids increasing the tolerance for the transmission time of each frame of positioning data due to a large predetermined total reporting duration, which would be detrimental to the accuracy of the positioning data application.

[0074] Step S403: In response to determining that the driving state is a stopped state, the predetermined total reporting time is determined to be a second time; wherein, the first time is less than the second time.

[0075] Specifically, when the receiver determines that the driving state is driving, it determines the larger of the first duration and the second duration as the predetermined total reporting duration. The first duration is less than the second duration. Therefore, when the driving state is driving, the second duration is determined as the predetermined total reporting duration, so as to provide the receiver with a larger tolerance for reporting packet data.

[0076] It should be noted that the predetermined total reporting time is determined based on the driving state, which represents the timeliness requirement for the transmission of positioning data under different driving states. When the vehicle is moving, the vehicle position changes rapidly, so the timeliness requirement for positioning is high, and the predetermined total reporting time is relatively short. When the vehicle is parked, the vehicle position does not change, so the timeliness requirement for positioning is low, and the predetermined total reporting time is relatively long.

[0077] In addition, when the maximum reporting time corresponding to the sub-packet data is a fixed value (e.g., 1 second), the size of the predetermined total reporting time can determine its tolerance range for the sub-packet data reported by the receiver, and thus determine the restart probability of the receiver.

[0078] When the maximum reporting duration corresponding to the sub-packet data is a variable value, regardless of the predetermined total reporting duration, the maximum reporting duration corresponding to each sub-packet data changes with the predetermined total reporting duration, and the restart probability of the receiver remains constant.

[0079] For example, the maximum reporting time corresponding to the sub-packet data is a fixed value of 1 second. When the vehicle is in a driving state, the predetermined total reporting time is 50 seconds. When the vehicle is in a parked state, the predetermined total reporting time is 60 seconds. In the scenario where one frame of positioning data corresponds to 55 sub-packets and the upper-layer application is blocked and cannot report successfully, when the predetermined total reporting time is 50 seconds, the receiver will inevitably trigger a timeout restart. However, when the predetermined total reporting time is 60 seconds, the receiver will inevitably not trigger a timeout restart.

[0080] For example, the maximum reporting time corresponding to the sub-packet data is a variable value. When the vehicle is in a driving state, the predetermined total reporting time is 50 seconds. When the vehicle is in a parked state, the predetermined total reporting time is 60 seconds. In the scenario where one frame of positioning data corresponds to 55 sub-packets and the upper-layer application is blocked and cannot report successfully, the predetermined total reporting time of 50 seconds or 60 seconds will trigger a timeout restart when the timer reaches the predetermined total reporting time, thus keeping the restart probability constant.

[0081] In this embodiment, when the receiver is located on the vehicle, that is, when the positioning data is applied to the vehicle, the predetermined total reporting time corresponding to each frame of positioning data is determined by obtaining the vehicle's driving status. Moreover, the predetermined total reporting time when the vehicle is driving is less than the predetermined total reporting time when the vehicle is parked, so as to set different tolerances for positioning data reporting for the vehicle under different driving states, reflecting the adaptability of positioning data reporting to the environment, which is beneficial to improving the user experience.

[0082] In some embodiments, step S202, retrying to report the packet data within the maximum reporting time, includes: Step S501: Determine the network signal quality.

[0083] Specifically, the receiver can determine the network signal quality through the network signal data it transmits. When determining the network signal quality, it determines the network signal quality that matches the network signal data based on a pre-stored network signal data and network signal quality lookup table.

[0084] It should be noted that the network signal data can be either signal strength or signal-to-noise ratio (SINR). When the network signal data is signal strength, the comparison data between signal strength and network signal quality is as follows: Signal strength > -70dBm: Extremely strong network signal quality; Signal strength: -70~-90dBm: Network signal quality is normal; Signal strength: -90~-110dBm: Poor network signal quality; Signal strength < -110dBm: The network signal quality is extremely poor.

[0085] When the network signal data is in the form of signal-to-noise ratio (SINR), the comparison data between SINR and network signal quality are as follows: Signal-to-noise ratio (SINR) > 15dB: Network signal quality: Extremely strong Signal-to-noise ratio (SINR) 8: 5–15 dB; Network signal quality: Normal Signal-to-noise ratio (SINR) < 5dB: Network signal quality: poor.

[0086] Step S502: Determine the number of retries for the packet data based on the network signal quality; wherein, the stronger the network signal quality, the fewer the number of retries.

[0087] Specifically, the stronger the network signal quality, the fewer the number of retries for the packet data. The receiver determines the number of retries for the packet data corresponding to the network signal quality based on a pre-stored network signal quality and retrieval count lookup table.

[0088] Dynamically determining the number of retries for the sub-packet data can balance the reporting latency of the sub-packet data and enhance the reliability of the receiver reporting the sub-packet data.

[0089] For example, when the network signal quality is extremely strong, the number of retries for the packet data is minimized, so that when the packet data reporting fails, the packet data is retried as little as possible within its corresponding maximum reporting time, thus avoiding excessive retries that occupy the network transmission channel, leading to channel congestion and blockage and affecting reporting; when the network signal quality is poor, the number of retries for the packet data is maximized, so that when the packet data reporting fails, the failure to report the packet data is avoided due to network latency.

[0090] Step S503: Within the maximum reporting time, retry reporting the packet data according to the number of retries.

[0091] Specifically, if the number of retries is determined and the packet data fails to be reported on the first attempt, the receiver will retry reporting the packet data according to the number of retries.

[0092] It should be noted that the receiver can retry reporting the packet data within the maximum reporting time. The number of retries is dynamically determined, and the receiver can dynamically determine the retry timing of the packet data to ensure that the number of retries is completed within the maximum reporting time.

[0093] For example, the maximum reporting time is 1 second and the number of retries is 5. After a packet data reporting fails, the receiver will retry reporting the packet data sequentially within the remaining time according to the number of retries 5. If the packet data is successfully reported when the number of retries is 2, the number of retries is invalidated.

[0094] In this embodiment, after a failed report, the packet data needs to be retried within the maximum reporting time to achieve successful reporting. Within the maximum reporting time, the number of times the packet data can be retried within the maximum reporting time is determined based on the network signal quality of the receiver. This helps to ensure the orderliness and reliability of the retried reporting of the packet data and improves the practicality of the method.

[0095] In some embodiments, the method further includes: Step S601: In response to determining that the timer has not reached the predetermined total reporting time after each packet of data has been reported, the timer is reset and it is determined whether a new frame of positioning data has been received.

[0096] Specifically, after the receiver determines that all the packet data corresponding to a frame of positioning data has been reported, the reporting result of the packet data may be successful or it may be discarded. Then, the timer is reset to keep track of whether a new frame of positioning data has been received.

[0097] It should be noted that if the timer reaches the predetermined total reporting time and there is still unreported packet data, the receiver will be triggered to time out and restart.

[0098] Step S602: In response to the failure to receive a new frame of positioning data and the timer reaching the predetermined total reporting duration, the receiver is restarted.

[0099] Specifically, after the receiver completes the reporting of the previous frame of positioning data, the timer starts counting. If the timer reaches the predetermined total reporting time while waiting to receive the new frame of positioning data, it indicates that the receiver has timed out and has not received the new frame of positioning data. If there is congestion on the path for sending positioning data to the receiver, the receiver is triggered to restart after timeout, so as to improve the congestion situation of positioning data transmission of the receiver by restarting.

[0100] It should be noted that the timer is used to monitor the data transmission status of the receiver, and to identify in a timely manner whether there is a timeout in the data transmission path with the receiver, and thus identify whether there is congestion. The timer times the process of the receiver reporting the location data, which monitors the data transmission path of the receiver. The timer also times the process of the receiver receiving the location data, which monitors the data reception path of the receiver. Thus, the timer can be used to monitor the congestion of the data transmission link of the receiver.

[0101] In this embodiment, after all the sub-packets of location data corresponding to a frame have been reported, i.e., after each sub-packet has been successfully reported or discarded, if the timer has not reached the predetermined total reporting duration, i.e., the receiver has not been triggered to time out and restart, the timer is reset to start timing for the receiver to receive a new frame of location data. After receiving a new frame of location data, timing is started for the receiver to send the new frame of location data, thereby realizing the turn-by-turn monitoring of the receiver's data transmission, which is beneficial to improving the continuity and reliability of the receiver's data transmission.

[0102] In some embodiments, step S202, retrying to report the packet data within the maximum reporting time, includes: Step S701: Determine the number of retries based on the data type of the sub-packet data; wherein, the higher the criticality of the data type of the sub-packet data, the more retries are made.

[0103] Specifically, after determining that the packet data reporting has failed, the receiver will retry reporting the packet data. When determining the number of times to retry reporting the packet data, the receiver will determine the number of times based on the data type of the packet data. That is, the higher the criticality of the data type of the packet data, the more times the retry will be performed.

[0104] For example, if the criticality of the packet data with data type GGA is greater than that of the packet data with data type GSV, then according to the pre-stored data type and retry count comparison table, it can be determined that after both types of packet data fail to be reported, the retry count for the packet data with data type GGA is 5, and the retry count for the packet data with data type GSV is 4.

[0105] Step S702: Retry reporting the packet data within the maximum reporting time according to the number of retries.

[0106] Specifically, if the number of retries is determined and the packet data fails to be reported on the first attempt, the receiver will retry reporting the packet data according to the number of retries.

[0107] It should be noted that the receiver can retry reporting the packet data within the maximum reporting time. The number of retries is determined according to the data type of the packet data. Thus, the receiver can dynamically determine the retry timing of the packet data to ensure that the number of retries is completed within the maximum reporting time.

[0108] For example, the maximum reporting time is 1 second and the number of retries is 5. After the packet data reporting fails, the receiver will retry reporting the packet data sequentially according to the number of retries 5 within the remaining time. If the packet data is successfully reported when the number of retries is 2, the number of retries is invalidated.

[0109] In this embodiment, after a failed report, the packet data needs to be retried within the maximum reporting time. If the packet data is successfully reported, the number of times the packet data can be retried within the maximum reporting time is determined according to the data type of the packet data. This ensures a high success rate for retrying the reporting of critical packet data within the maximum reporting time, which improves the practicality of the method.

[0110] In some embodiments, the maximum reporting duration is equal to the quotient of the predetermined total reporting duration and the number of data packets; or, The maximum reporting duration is a preset duration; or, The maximum reporting time is less than the quotient of the predetermined total reporting time and the number of data packets.

[0111] Specifically, there are three ways to determine the maximum reporting time corresponding to the packet data. The first is that the minimum reporting time is the quotient of the predetermined total reporting time and the number of packet data corresponding to the location data frame, so that the sum of the maximum reporting times of each packet data corresponding to the location data frame is the same as the predetermined total reporting time of the location data frame. Therefore, if the reporting time of one packet data does not reach the maximum reporting time, the receiver will not time out and restart during the reporting process of the location data frame, resulting in a low probability of the receiver timeout restart. The second is to make the maximum reporting time of each packet data a preset time, so that the probability of the receiver timeout restart is related to the number of packet data corresponding to each location data frame. When the number of packet data corresponding to a location data frame is less than the quotient of the predetermined total reporting time and the preset time, even if none of the packet data corresponding to the location data frame is successfully reported (i.e., all are discarded), the receiver will not time out and restart, and the restart probability in this case is 0. However, If the number of packets corresponding to a frame of positioning data is greater than or equal to the quotient of the predetermined total reporting time and the preset time, the receiver will trigger a timeout restart when the reporting time of the packets corresponding to the frame of positioning data reaches a specific number that is equal to the maximum reporting time. The restart probability is greater than when the number of packets is small. Therefore, setting the maximum reporting time to the preset time can identify scenarios with a specific number of packets, such as scenarios where the packets are large and reporting fails. In such scenarios, the timeout restart can provide users with a constant restart opportunity, thereby improving the user experience. The third approach is to make the maximum reporting time less than the quotient of the predetermined total reporting time and the number of packets corresponding to the frame of positioning data. In this way, even if the reporting time of all packets corresponding to the frame of positioning data is equal to the maximum reporting time, the reporting time of all packets of the frame of positioning data will not reach the predetermined time, and the receiver will not time out restarting, making the timeout restart probability of the receiver during the reporting of packets zero.

[0112] For example, when the maximum reporting duration is a preset duration, the maximum reporting duration corresponding to each data packet is 1 second, the predetermined total reporting duration is 60 seconds, and the number of data packets corresponding to one frame of positioning data is 59. When the actual reporting duration of these 59 data packets is the maximum reporting duration, the reporting duration of each data packet is the maximum reporting duration of 1 second. 1 second × 59 = 59 seconds. 59 seconds < the predetermined total reporting duration of 60 seconds. Since the reporting duration of this frame of positioning data does not exceed the predetermined total reporting duration, the receiver will not restart. The number of data packets corresponding to one frame of positioning data is 70. If the reporting duration of 60 data packets is the maximum reporting duration, the receiver will be triggered to time out and restart.

[0113] For another example, when the maximum reporting duration = the predetermined total reporting duration / the number of data packets, and the number of data packets is 60, and the predetermined total reporting duration is 60 seconds, then the maximum reporting duration is 1 second. If the actual reporting duration of all 60 data packets is the maximum reporting duration, then when the actual reporting duration of the 60th data packet reaches the maximum reporting duration, the receiver is triggered to time out and restart. If the actual reporting duration of any data packet is less than the maximum reporting duration, the receiver will not be triggered to time out and restart.

[0114] For another example, when the maximum reporting duration is less than the predetermined total reporting duration / the number of data packets, and the number of data packets is 59, the predetermined total reporting duration is 60 seconds, and the maximum reporting duration is 1 second, then the maximum reporting duration of 1 second is less than the predetermined total reporting duration / the number of data packets = 60 seconds / 59 = 1.02 seconds. In this case, when the actual reporting duration of each of the 59 data packets is the maximum reporting duration, the sum of the actual reporting durations of the 59 data packets is still less than the predetermined total reporting duration, and therefore the receiver will not be triggered to time out and restart. The probability of the receiver to time out and restart is 0.

[0115] In this embodiment, there are three ways to determine the maximum reporting time. Each method can reduce the probability of the receiver restarting due to timeout during the reporting of the packet data to a certain extent. In practical applications, the corresponding method for determining the maximum reporting time can be set according to the application needs to meet user needs, improve user experience, and enhance the practicality of the method.

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

[0117] It should be noted that the above description describes some embodiments of this application. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in a different order than that shown in the above embodiments and still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require a specific or sequential order to achieve the desired result. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0118] Based on the same inventive concept, corresponding to any of the above embodiments, this application also provides a device restart system.

[0119] refer to Figure 2 The device restarts the system, including: The parsing module 100 is configured to, in response to the receiver receiving a frame of positioning data, parse the positioning data into at least one packet of data and reset the timer; The reporting module 200 is configured to report the data of each sub-packet sequentially. The restart module 300 is configured to restart the receiver in response to determining that the timer has reached a predetermined total reporting duration during the reporting process of each packet of data; wherein each frame of positioning data corresponds to a predetermined total reporting duration; the reporting duration of each packet of data is less than or equal to its corresponding maximum reporting duration; and the maximum reporting duration is less than the predetermined total reporting duration.

[0120] In some embodiments, the reporting module 200 is further configured to determine the reporting order of each of the sub-packet data, and to report each of the sub-packet data sequentially based on the reporting order; in response to a sub-packet data reporting failure, to retry reporting the sub-packet data within the maximum reporting time; in response to a sub-packet data failing to be reported within the maximum reporting time, to report the next sub-packet data; and in response to a sub-packet data successfully being reported within the maximum reporting time, to report the next sub-packet data.

[0121] In some embodiments, the reporting module 200 is further configured to determine the reporting order of the at least one sub-packet data based on the data type of each sub-packet data; or, to determine the reporting order of the at least one sub-packet data based on the byte size of the at least one sub-packet data.

[0122] In some embodiments, the device further includes a determining module configured to acquire the driving status of the vehicle; in response to determining that the driving status is driving, determining the pre-determined total reporting time as a first time; in response to determining that the driving status is parked, determining the pre-determined total reporting time as a second time; wherein the first time is less than the second time.

[0123] In some embodiments, the reporting module 200 is further configured to determine network signal quality; determine the number of retries for the packet data based on the network signal quality; and retry reporting the packet data according to the number of retries within the maximum reporting duration; wherein, the stronger the network signal quality, the fewer the number of retries.

[0124] In some embodiments, the apparatus further includes a reset module configured to reset the timer and determine whether a new frame of location data is received in response to determining that the timer has not reached a predetermined total reporting duration after each packet of data has been reported; and to restart the receiver in response to not receiving a new frame of location data and the timer reaching the predetermined total reporting duration.

[0125] In some embodiments, the reporting module 200 is further configured to determine the number of retries based on the data type of the sub-packet data, wherein the higher the criticality of the data type of the sub-packet data, the more retries are made; and the sub-packet data is retried and reported according to the number of retries within the maximum reporting time.

[0126] In some embodiments, the maximum reporting duration is equal to the quotient of the predetermined total reporting duration and the number of sub-package data; or, the maximum reporting duration is a preset duration; or, the maximum reporting duration is less than the quotient of the predetermined total reporting duration and the number of sub-package data.

[0127] For ease of description, the above devices are described in terms of function, divided into various modules. Of course, in implementing this application, the functions of each module can be implemented in one or more software and / or hardware.

[0128] The system described above is used to implement the corresponding device restart method in any of the foregoing embodiments, and has the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0129] Based on the same inventive concept, corresponding to the methods of any of the above embodiments, this application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the device restart method described in any of the above embodiments.

[0130] Figure 3 This embodiment illustrates a more specific hardware structure of an electronic device. The device may include a processor 1010, a memory 1020, an input / output interface 1030, a communication interface 1040, and a bus 1050. The processor 1010, memory 1020, input / output interface 1030, and communication interface 1040 are interconnected internally via the bus 1050.

[0131] The processor 1010 can be implemented using a general-purpose CPU (Central Processing Unit), microprocessor, application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this specification.

[0132] The memory 1020 can be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage device, dynamic storage device, etc. The memory 1020 can store the operating system and other applications. When the technical solutions provided in the embodiments of this specification are implemented by software or firmware, the relevant program code is stored in the memory 1020 and is called and executed by the processor 1010.

[0133] The input / output interface 1030 is used to connect input / output modules to realize information input and output. Input / output modules can be configured as components within the device (not shown in the figure) or externally connected to the device to provide corresponding functions. Input devices may include keyboards, mice, touchscreens, microphones, various sensors, etc., while output devices may include displays, speakers, vibrators, indicator lights, etc.

[0134] The communication interface 1040 is used to connect a communication module (not shown in the figure) to enable communication between this device and other devices. The communication module can communicate via wired means (such as USB, Ethernet cable, etc.) or wireless means (such as mobile network, WIFI, Bluetooth, etc.).

[0135] Bus 1050 includes a pathway for transmitting information between various components of the device, such as processor 1010, memory 1020, input / output interface 1030, and communication interface 1040.

[0136] It should be noted that although the above-described device only shows the processor 1010, memory 1020, input / output interface 1030, communication interface 1040, and bus 1050, in specific implementations, the device may also include other components necessary for normal operation. Furthermore, those skilled in the art will understand that the above-described device may only include the components necessary for implementing the embodiments of this specification, and not necessarily all the components shown in the figures.

[0137] The electronic devices described above are used to implement the corresponding device restart methods in any of the foregoing embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0138] Based on the same inventive concept, corresponding to the methods of any of the above embodiments, this application also provides a non-transitory computer-readable storage medium storing computer instructions for causing the computer to execute the device restart method as described in any of the above embodiments.

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

[0140] The computer instructions stored in the storage medium of the above embodiments are used to cause the computer to execute the device restart method as described in any of the above embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0141] Based on the same concept, corresponding to any of the above embodiments, this application also provides a computer program product, including computer program instructions, which, when run on a computer, cause the computer to perform the method described in any of the above embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0142] It is understood that before using the technical solutions of the various embodiments in this disclosure, users will be informed of the type, scope of use, and usage scenarios of the personal information involved in an appropriate manner, and user authorization will be obtained.

[0143] For example, upon receiving a user's active request, a prompt message is sent to the user to explicitly inform them that the requested operation will require the acquisition and use of the user's personal information. This allows the user to independently choose, based on the prompt message, whether to provide personal information to the software or hardware such as electronic devices, applications, servers, or storage media performing the operations of this disclosed technical solution.

[0144] As an optional but not limited implementation, in response to a user's active request, sending a prompt message to the user can be done via a pop-up window, where the prompt message can be presented in text format. Furthermore, the pop-up window can also include a selection control allowing the user to choose "agree" or "disagree" to provide personal information to the electronic device.

[0145] It is understood that the above notification and user authorization process are merely illustrative and do not constitute a limitation on the implementation of this disclosure. Other methods that comply with relevant laws and regulations may also be applied to the implementation of this disclosure.

[0146] Those skilled in the art should understand that the discussion of any of the above embodiments is merely exemplary and is not intended to imply that the scope of this application is limited to these examples; under the concept of this application, the technical features of the above embodiments or different embodiments can also be combined, the steps can be implemented in any order, and there are many other variations of different aspects of the embodiments of this application as described above, which are not provided in detail for the sake of brevity.

[0147] Additionally, to simplify the description and discussion, and to avoid obscuring the embodiments of this application, the well-known power / ground connections to integrated circuit (IC) chips and other components may or may not be shown in the provided drawings. Furthermore, the apparatus may be shown in block diagram form to avoid obscuring the embodiments of this application, and this also takes into account the fact that the details of the implementation of these block diagram apparatuses are highly dependent on the platform on which the embodiments of this application will be implemented (i.e., these details should be fully understood by those skilled in the art). While specific details (e.g., circuits) have been set forth to describe exemplary embodiments of this application, it will be apparent to those skilled in the art that the embodiments of this application can be implemented without these specific details or with variations thereof. Therefore, these descriptions should be considered illustrative rather than restrictive.

[0148] Although this application has been described in conjunction with specific embodiments thereof, many substitutions, modifications, and variations of these embodiments will be apparent to those skilled in the art from the foregoing description. For example, other memory architectures (e.g., dynamic RAM (DRAM)) may be used with the embodiments discussed.

[0149] The embodiments of this application are intended to cover all such substitutions, modifications, and variations that fall within the broad scope of the claims of this application. Therefore, any omissions, modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the embodiments of this application should be included within the protection scope of this application.

Claims

1. A device restart method, comprising: include: In response to the receiver receiving a frame of location data, the location data is parsed into at least one packet of data, and the timer is reset; Report the data of each sub-package in sequence; In response to determining that the timer has reached a predetermined total reporting duration during the reporting of each of the sub-packet data, the receiver is restarted; Each frame of positioning data corresponds to a predetermined total reporting duration; the reporting duration of each packet of data is less than or equal to its corresponding maximum reporting duration; the maximum reporting duration is less than the predetermined total reporting duration.

2. The method of claim 1, wherein, The sequential reporting of each of the sub-packet data includes: Determine the reporting order of each of the sub-packet data, and report each of the sub-packet data sequentially based on the reporting order; In response to a failure to report one of the sub-packet data, the report of the sub-packet data shall be retried within the maximum reporting time. If all of the aforementioned packet data fails to be reported within the maximum reporting time, then the next packet data is reported. If a packet of data is successfully reported within the maximum reporting time, the next packet of data is reported.

3. The method of claim 2, wherein, Determining the reporting order of each of the sub-packet data includes: The reporting order of the at least one sub-packet data is determined based on the data type of each sub-packet data; or, The reporting order of the at least one packet of data is determined based on the byte size of the at least one packet of data.

4. The method of claim 1, wherein, The receiver is located on the vehicle, and the method further includes: Obtain the vehicle's driving status; In response to determining that the driving state is driving, the predetermined total reporting time is determined to be a first time. In response to determining that the driving state is a parking state, the pre-determined total reporting time is determined to be the second time. The first duration is shorter than the second duration.

5. The method of claim 2, wherein, The retrying to report the packet data within the maximum reporting time includes: Determine network signal quality; The number of retries for the packet data is determined based on the network signal quality. Within the maximum reporting time, the packet data shall be retried and reported according to the number of retries. The stronger the network signal quality, the fewer the number of retries.

6. The method of claim 1, wherein, Also includes: In response to determining that the timer has not reached the predetermined total reporting time after each packet of data has been reported, the timer is reset and it is determined whether a new frame of location data has been received; If no new frame of location data is received and the timer reaches the predetermined total reporting duration, the receiver is restarted.

7. The method of claim 2, wherein, The retrying to report the packet data within the maximum reporting time includes: The number of retries is determined based on the data type of the sub-package data; wherein, the higher the criticality of the data type of the sub-package data, the more retries are made. Within the maximum reporting time, the packet data is retried and reported according to the number of retries.

8. The method of claim 1, wherein, The maximum reporting duration is equal to the quotient of the predetermined total reporting duration and the number of data packets; or, The maximum reporting duration is a preset duration; or, The maximum reporting time is less than the quotient of the predetermined total reporting time and the number of data packets.

9. An electronic device comprising a memory, a processor, and a computer program stored on the memory and running on the processor, characterized in that, When the processor executes the program, it implements the method as described in any one of claims 1 to 8.

10. A vehicle characterized by comprising: Including an electronic device as described in claim 9.

Images