A method to prevent inter-module request loss

Abstract

The present invention discloses a method for preventing inter-module request loss, comprising: a source module sending a request value to a target module according to a monitored user operation; the target module receiving the request value sent by the source module, and feeding back a corresponding feedback value to the source module according to the request value; the source module comparing the feedback value with the request value sent last time, if the feedback value does not correspond to the request value sent last time, then repeatedly sending the last request value to the target module, if the feedback value corresponds to the request value sent last time, then sending the current valid request value to the target module according to the validity of the current request value. The method for preventing inter-module request loss can enable the request sent by the source module to be correctly received by the target module, prevent the loss of requests between modules that run independently in two different cycles, and ensure that the vehicle computer makes a correct response.

Description

Technical Field

[0001] The present invention relates to a method for preventing request loss between modules, in particular to a method for preventing request loss between modules with different operation cycles. Background Art

[0002] The source module is the trigger module of the operation. It monitors the user's operation on the instrument side, determines the action to be triggered, and sends a request to the target module. After receiving the request sent by the source module, the target module responds to the request and executes the corresponding logic. For example, the user switches the navigation mode of the instrument through key operation. The source module detects the key operation and determines that it needs to switch to full-screen or non-full-screen mode. After receiving this operation request, the target module feeds back the event to the car computer to determine the projection content sent by the car computer to the instrument side. The projection content can be the corresponding projection image of full-screen navigation or non-full-screen navigation.

[0003] The specific implementation method of the traditional source module sending a request to the target module is that the source module monitors the corresponding operation triggered by the key operation and sends a request to the target module. After receiving the operation request, the target module feeds back the event to the vehicle computer to determine the screen projection content sent by the vehicle computer to the instrument end. Because the source module and the target module operate independently in different cycles, it takes a period of time for the source module to be received by the target module after sending the request, that is, there is a time difference between the sending and receiving of the request. Since the inconsistent operating cycles of the two modules will cause the time difference between the sending and receiving of the request, the valid request sent by the source module will have a probability of being lost under the influence of this time difference. In particular, under extreme operating conditions, such as when the request sent by the source module is quickly switched, the probability of losing the valid request will increase. Once the request is lost, the final operation responded by the target module will be inconsistent with the triggered event, thereby affecting the user experience. Summary of the invention

[0004] The present invention aims to provide a method capable of preventing inter-module request loss caused by inconsistent operation cycles, so as to improve user experience.

[0005] The method for preventing inter-module request loss of the present invention comprises:

[0006] The source module sends a request value to the target module according to the monitored user operation;

[0007] The target module receives the request value sent by the source module, and feeds back the corresponding feedback value to the source module according to the request value;

[0008] The source module compares the feedback value with the request value sent last time;

[0009] If the feedback value does not correspond to the request value sent last time, the last request value is sent to the target module repeatedly;

[0010] If the feedback value corresponds to the request value sent last time, the current request value is sent to the target module.

[0011] The method for preventing inter-module request loss described in the present invention is as follows: when the last request value and the feedback value correspond, the last operation request has been received by the target module, and the current new request value can be sent; when the feedback value does not correspond to the last request value, the last request value has not been received by the target module, and the last request value needs to be sent. By establishing feedback logic between the source module and the target module, the two modules can run independently, and requests between modules in different cycles can be received, thereby preventing inter-module request loss and ensuring that the vehicle computer makes a correct response. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Figure 1 The following is a timing diagram of inter-module request loss under extreme operating conditions.

[0013] Figure 2 This is a timing diagram of the method for preventing inter-module request loss according to the present invention. DETAILED DESCRIPTION

[0014] A method for preventing inter-module request loss, comprising:

[0015] The source module sends a request value to the target module according to the monitored user operation;

[0016] The target module receives the request value sent by the source module, and feeds back the corresponding feedback value to the source module according to the request value;

[0017] The source module compares the feedback value with the request value sent last time;

[0018] If the feedback value does not correspond to the request value sent last time, the last request value is sent to the target module repeatedly;

[0019] If the feedback value corresponds to the request value sent last time, the current request value is sent to the target module.

[0020] The source module determines the request value (0 for request 0, 1 for request 1, and 3 for invalid request) according to the trigger condition of the request, and sends the request value to the target module. Among them, the valid request (request 0 and request 1) is an event-triggered request, that is, request 0 and request 1 are triggered when an event occurs, and the invalid request 3 is sent by default at other times. The target module responds to the operations corresponding to different request values ​​according to the request value sent by the source module. When a valid request (request 0 and request 1) is received, the operation corresponding to the event is responded; when an invalid request is received, no operation is performed. Under extreme operation conditions, if the request sent by the source module is quickly switched between "request 0" and "request 1", the probability of losing a valid request will increase. When the request of the source module switches quickly between "request 0" and "request 1", and the final valid request is "request 1", the final valid request received by the target module is "request 0" due to the time difference caused by the difference in the operating cycles, resulting in the final operation responded by the target module being inconsistent with the triggered event, such as Figure 1 As shown. Therefore, when the feedback value corresponds to the request value sent last time, the source module needs to determine whether the current request value is a valid request value. If the current request value is a valid request value, the current request value is sent to the target module. If the current request value is not a valid request value, the last valid request value is sent to the target module. This effectively avoids the loss of valid requests and ensures that valid requests can be received by the target module. It also ensures that when the trigger operation of the source module ends, the corresponding response of the target module also ends. For example, the source module quickly triggers 20 switches. Affected by the cycle, the time it takes for the target module to respond to 20 switches is much longer than the time required for the trigger. This logic ensures that while filtering repeated requests in the middle of quick operations, the request to which the target module responds for the last time is consistent with the request to which the source module sends for the last time (such as Figure 2 As shown in the figure, the number of triggered requests does not have to be equal to the number of responded requests, but the final triggered request and the final responded request are consistent. For example, the source module quickly triggers 20 switching requests, the last request is request 1, and the target module actually responds 10 times, the last request to respond is request 1.

[0021] The above contents are further detailed descriptions of the present invention in combination with specific preferred embodiments, and it cannot be determined that the specific implementation of the present invention is limited to these descriptions. For ordinary technicians in the technical field to which the present invention belongs, several simple deductions or substitutions can be made without departing from the concept of the present invention, which should be regarded as falling within the protection scope of the present invention.

Claims

1. A method for preventing inter-module request loss, characterized in that: include: The source module sends a request value to the target module according to the monitored user operation; The target module receives the request value sent by the source module, and feeds back the corresponding feedback value to the source module according to the request value; The source module compares the feedback value with the request value sent last time; If the feedback value does not correspond to the request value sent last time, the last request value is sent to the target module repeatedly; If the feedback value corresponds to the request value sent last time, the current request value is sent to the target module; If the feedback value corresponds to the request value sent last time, the source module determines whether the current request value is a valid request value; If the current request value is a valid request value, the current request value is sent to the target module; If the current request value is not a valid request value, the last valid request value is sent to the target module.

Images