A vehicle window control method and device, terminal device, and vehicle
By maintaining and continuously sending window control commands in the window controller until the next window action triggers the event, the problem of window control commands not being recorded in a timely manner in the data management background is solved, achieving high efficiency and accuracy in fault diagnosis.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- GREAT WALL MOTOR CO LTD
- Filing Date
- 2023-04-23
- Publication Date
- 2026-06-05
AI Technical Summary
In existing technologies, window control commands cannot be recorded in a timely manner in the data management backend, making fault diagnosis difficult and making it impossible to quickly locate the source of the fault.
After detecting a window action trigger event, the window controller retains the window control command and continuously sends it to the bus until the next window action trigger event is received. The on-board telematics processor can collect the window control command when uploading the bus command to ensure that the data management background records relevant information.
It improves the efficiency and accuracy of fault diagnosis. By using the window control command information recorded in the data management backend, the source of the fault can be quickly identified.
Smart Images
Figure CN116446758B_ABST
Abstract
Description
Technical Field
[0001] This application belongs to the field of automotive technology, and in particular relates to a window control method and device, terminal equipment, and vehicle. Background Technology
[0002] With the continuous development of automotive technology, cars are increasingly involved in our daily lives, facing a wide variety of application scenarios and needs, and intelligent vehicle services are receiving more and more attention. As automotive intelligence develops rapidly, intelligent control of car windows provides users with window raising and lowering control functions in various scenarios.
[0003] Car window control commands are numerous and complex. During use, windows may suddenly close or open automatically, which can easily lead to user complaints. Upon receiving a complaint, it's crucial to quickly determine the cause of the malfunction and resolve it.
[0004] However, there are currently instances where the data management backend fails to record window raising / lowering commands, which can lead to difficulties in quickly locating the source of the malfunction after receiving user complaints. Summary of the Invention
[0005] This application provides a method and device for controlling vehicle windows, a terminal device, and a vehicle, which enables the data management backend to record the window raising and lowering commands.
[0006] In a first aspect, embodiments of this application provide a method for controlling vehicle windows, including:
[0007] When a window action trigger event is detected, relevant information about the window action trigger event is obtained, including the window control command and the window action trigger source of the window action trigger event.
[0008] The window control command is held to continuously send the window control command to the bus until the next window action trigger event is detected;
[0009] The system continuously sends trigger source signals to the bus based on the window action trigger source until the next window action trigger event is detected.
[0010] In one implementation of the first aspect, the step of continuously sending a trigger source signal to the bus according to the window action trigger source until the next window action trigger event is detected includes:
[0011] Obtain the identifier code of the trigger source for the window action;
[0012] A trigger source signal is generated based on the identifier encoding.
[0013] In one implementation of the first aspect, the information related to the window action triggering event further includes the window action type. After obtaining the relevant information of the window action triggering event upon detection, the process further includes:
[0014] If the window action type is the same as the window action type of the previous window control command, the window control command remains unchanged, and the window control command continues to be processed to continuously send the window control command to the bus.
[0015] If the window action type is different from the window action type of the previous window control command, the window control command is updated, and a hold process is performed on the updated window control command to continuously send the updated window control command to the bus until the next window action trigger event is detected.
[0016] In one implementation of the first aspect, after obtaining relevant information about the window action triggering event upon detecting the window action triggering event, the method further includes:
[0017] If the window action triggering source of the aforementioned window action triggering event is the same as the window action triggering source corresponding to the previous triggering source signal, then the triggering source signal remains unchanged, and the triggering source signal is continuously sent to the bus.
[0018] If the window action trigger source of the window action triggering event is different from the window action trigger source corresponding to the previous trigger source signal, then the trigger source signal is updated, and the updated trigger source signal is continuously sent to the bus.
[0019] In one implementation of the first aspect, the information related to the window action triggering event further includes a signal flag bit. After obtaining the information related to the window action triggering event upon detection, the process further includes:
[0020] The parameters of the signal flag are determined based on the window action type and the window action trigger source of the window action triggering event.
[0021] In one implementation of the first aspect, determining the parameters of the signal flag bit based on the window action type and window action trigger source of the window action triggering event includes:
[0022] If the window action type of the window action triggering event is the same as the window action type of the previous window control command, and the window action triggering source of the window action triggering event is the same as the window action triggering source in the previous triggering source signal, then the signal flag is set to the first state bit.
[0023] In one implementation of the first aspect, after setting the signal flag to the first state bit, if the window action type of the window action triggering event is the same as the window action type of the previous window control command, and the window action triggering source of the window action triggering event is the same as the window action triggering source in the previous triggering source signal, the method further includes:
[0024] When the duration of the signal flag being in the first state position reaches a preset time threshold, the signal flag is set to the initial state position.
[0025] Secondly, embodiments of this application provide a vehicle window control device, the vehicle window control device comprising:
[0026] The acquisition module is used to acquire relevant information about the window action triggering event when a window action triggering event is detected. The relevant information includes the window control command and the window action triggering source of the window action triggering event.
[0027] The first sending module is used to perform holding processing on the window control command to continuously send the window control command to the bus until the next window action trigger event is detected.
[0028] The second sending module is used to continuously send trigger source signals to the bus according to the window action trigger source until the next window action trigger event is detected.
[0029] Thirdly, embodiments of this application provide a terminal device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the window control method as described in any one of the first aspects above.
[0030] Fourthly, embodiments of this application provide a vehicle that includes a window control device as described in the second aspect, or a terminal device as described in the third aspect.
[0031] Fifthly, embodiments of this application provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of the window control method as described in any one of the first aspects above.
[0032] Sixthly, embodiments of this application provide a computer program product that, when run on a terminal device, enables the terminal device to execute the window control method described in any of the first aspects above.
[0033] The beneficial effects of the embodiments in this application compared with the prior art are:
[0034] This application provides a window control method. After detecting a window action trigger event, the window controller retains the window control command triggered by the event and continuously sends it to the bus until a new window action trigger event is received. This allows the onboard telematics processor to collect the window control command when uploading bus commands to the data management backend, enabling the backend to record relevant information about the command. Therefore, upon receiving a user's fault complaint, the source of the fault can be determined through the information recorded in the window control command in the data management backend, thereby improving the efficiency and accuracy of fault diagnosis. Attached Figure Description
[0035] To more clearly illustrate the technical solutions in the embodiments of this application, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0036] Figure 1 This is a schematic diagram illustrating an application scenario of the window control method provided in the embodiments of this application;
[0037] Figure 2 This is a schematic diagram illustrating the implementation process of the window control method provided in the embodiments of this application;
[0038] Figure 3 This is a schematic diagram of the signal transmission timing of the window control method provided in the embodiments of this application;
[0039] Figure 4 This is a schematic diagram of another implementation flow of the window control method provided in one embodiment of this application;
[0040] Figure 5 This is a schematic diagram of another implementation flow of the window control method provided in one embodiment of this application;
[0041] Figure 6 This is a schematic diagram of another implementation flow of the window control method provided in one embodiment of this application;
[0042] Figure 7 This is a schematic diagram of the structure of a window control device provided in one embodiment of this application;
[0043] Figure 8 This is a schematic diagram of the structure of a terminal device provided in an embodiment of this application. Detailed Implementation
[0044] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application may also be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods have been omitted so as not to obscure the description of this application with unnecessary detail.
[0045] It should be understood that, when used in this application specification and the appended claims, the term "comprising" indicates the presence of the described features, integrals, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or a collection thereof.
[0046] It should also be understood that the term “and / or” as used in this application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.
[0047] As used in this application specification and the appended claims, the term "if" may be interpreted, depending on the context, as "when," "once," "in response to determination," or "in response to detection." Similarly, the phrase "if determined" or "if detected [the described condition or event]" may be interpreted, depending on the context, as meaning "once determined," "in response to determination," "once detected [the described condition or event]," or "in response to detection [the described condition or event]."
[0048] Furthermore, in the description of this application and the appended claims, the terms "first," "second," "third," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.
[0049] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.
[0050] With the rapid development of intelligent technology in automobiles, intelligent control of car windows provides users with various window raising and lowering control functions in different scenarios, such as driver / passenger button control of windows, window control via in-vehicle telematics BOX (T-BOX), voice control of windows, window control via keyless entry, remote key control, Bluetooth key control, window control via mobile app, automatic window closing upon leaving the vehicle, automatic window closing based on vehicle speed, automatic window closing while parking, automatic window closing during car wash, one-touch window raising, automatic window closing in rain and snow mode, and automatic window closing in intelligent rest mode, etc.
[0051] There are many and complex commands for controlling car windows. Sometimes, windows may suddenly close or open automatically, which can easily lead to user complaints. After receiving a user complaint, it is necessary to determine the cause of the malfunction as soon as possible in order to resolve the problem.
[0052] However, since the window raising / lowering commands are transmitted on the bus in the form of event frames, after receiving a window action trigger event, the window action trigger source will send a window raising / lowering command to the window controller via the bus, and then send another command 50ms later, for a total of 5 times, taking a total of 250ms. After completion, the command is cleared. There is a time interval between the data transmission between the vehicle telematics processor and the data management backend. Specifically, the data transmission interval between the vehicle telematics processor and the data management backend is 1 second, meaning that the vehicle telematics processor sends a command received by the window controller to the data management backend every 1 second.
[0053] The vehicle-mounted telematics processor acquires instructions transmitted on the bus and uploads the acquired instructions to the data management backend.
[0054] It should be noted that the aforementioned vehicle telematics processor is primarily used to connect with the data management backend, enabling data recording and control between the backend and the vehicle. The data management backend mainly records relevant vehicle data, including data on various vehicle states and commands executed by the vehicle. Because the data transmission time interval between the vehicle telematics processor and the data management backend is greater than the transmission time of the window raising / lowering command on the bus, the data management backend may fail to record window raising / lowering commands. This results in difficulties in quickly locating the source of the fault after receiving user complaints.
[0055] It should be noted that the aforementioned window action trigger sources include, but are not limited to: pulse width modulation (PWM) signal sources, in-vehicle telematics BOX (T-BOX), voice control signal trigger sources, remote keyless entry (RKE), passive keyless entry (PKE), Bluetooth, optical rain sensor (RLS), mobile application, vehicle departure locking signal sources, vehicle speed sensing automatic window closing signal sources, automatic window closing in parking status, automatic window closing during car wash, one-touch window lifting, automatic window closing in rain and snow weather mode, automatic window closing in intelligent rest mode, automatic window closing in "time and space gate" mode, etc.
[0056] The aforementioned PWM signal source can be generated by the driver / passenger controlling the window raising and lowering via buttons.
[0057] To enable the data management backend to accurately record window control commands, this application provides a window control method. After detecting a window action trigger event, the window controller performs hold processing on the window control command of the aforementioned window trigger event and continuously sends the aforementioned window control command to the bus until a new window action trigger event is received. In this way, when the vehicle telematics processor uploads bus commands to the data management backend, it can collect the window control command, allowing the data management backend to record the relevant information of the aforementioned window control command.
[0058] Based on this, when a user's fault complaint is received, the source of the fault can be determined by the relevant information of the window control commands recorded in the data management backend, thereby improving the efficiency and accuracy of fault diagnosis.
[0059] The following is an exemplary description of the application scenarios to which the window control method provided in this application is applicable:
[0060] Please see Figure 1 , Figure 1 A schematic diagram illustrating an application scenario of the window control method provided in this application embodiment is shown. For example... Figure 1 As shown, the vehicle may include a window controller 10 and an onboard telematics processor (T-BOX) 20, wherein the onboard telematics processor 20 is connected to the window controller 10 via a CAN bus and is also connected to the data management backend 30.
[0061] In this embodiment, the window controller has functions such as data processing, data communication and program execution. The window controller can be the vehicle's electronic control unit (ECU), also known as the vehicle computer, or a device with the same or similar functions. This embodiment does not limit this.
[0062] The aforementioned window controller can receive window control commands sent by various window action trigger sources and control the corresponding windows to perform the actions corresponding to the window control commands, thereby realizing intelligent window control. Furthermore, the window controller can send relevant information about window action trigger events to the bus, enabling the on-board telematics processor 20 to collect such information via the bus and upload it to the data management backend. The data management backend retains the data, and when maintenance personnel need to query the data, they can do so through the data recorded in the data management backend to perform vehicle inspection and maintenance.
[0063] The following will describe, with reference to the accompanying drawings, an exemplary method for controlling vehicle windows provided in this application:
[0064] Please see Figure 2 , Figure 2 This is a schematic diagram illustrating the implementation process of a window control method provided in an embodiment of this application. In this embodiment, the executing entity of the above-mentioned window control method can be a window controller.
[0065] S11: When a window action trigger event is detected, obtain relevant information about the vehicle trigger event.
[0066] In this embodiment of the application, the relevant information of the aforementioned window action triggering event may include the window action triggering source corresponding to the window action triggering event and the window control command corresponding to the window action triggering event.
[0067] Here, the aforementioned window action trigger source refers to the object that issues the window control command, and the aforementioned window control command refers to what action the window should perform. The aforementioned window control command may include, but is not limited to, window raise control commands and window lower control commands. The aforementioned window raise control command is used to control the window to rise, and the aforementioned window lower control command is used to control the window to fall.
[0068] Specifically, controlling the window to rise can be done by raising the window at a constant speed, or by executing a corresponding rising strategy based on the type of window action trigger source; no specific restrictions are imposed here. Similarly, controlling the window to fall can be done by lowering the window at a constant speed, or by executing a corresponding falling strategy based on the type of window action trigger source; again, no specific restrictions are imposed here.
[0069] In this embodiment of the application, the aforementioned window action triggering event is triggered by a window action triggering source. When the window action triggering source issues a window control command, and the window controller receives the window control command, it can be determined that the window controller has detected a window action triggering event.
[0070] S12: Perform hold processing on the window control command to continuously send the window control command to the bus until the next window action trigger event is detected.
[0071] Specifically, the window control command holding process can be achieved by recording the current window action triggering event's window control command in the software inside the window controller, and maintaining the window control command unchanged until a new window action triggering event is detected.
[0072] S13: Continuously send trigger source signals to the bus according to the window action trigger source until the next window action trigger event is detected.
[0073] In order for the data management backend to record who issued the window control command, the window controller can query the trigger source of the window action trigger event it detected.
[0074] In this application embodiment, the aforementioned window action triggering sources include, but are not limited to: pulse width modulation (PWM) signal source, in-vehicle telematics BOX (T-BOX), voice control signal triggering source, remote keyless entry (RKE), passive keyless entry (PKE), Bluetooth, optical rain sensor (RLS), mobile application, vehicle departure locking signal source, vehicle speed sensing automatic window closing signal source, automatic window closing in parking status, automatic window closing during car wash, one-touch window lifting, automatic window closing in rain and snow mode, and automatic window closing in intelligent rest mode, etc.
[0075] For example, when the window controller receives a window lift control command at time T1, the window controller can query the trigger source that issued the window lift control command. Assuming that the window lift control command is issued by the trigger source of automatic window closing in rain and snow mode, that is, the window controller detects that the window action trigger source is automatic window closing in rain and snow mode.
[0076] In this embodiment, a unique identifier code can be pre-set for each window action trigger source, allowing identification of different window action trigger sources. For example, the identifier code for a PWM signal source can be set to 01, the identifier code for a T-BOX to 02, the identifier code for a voice control signal trigger source to 03, the identifier code for a remote keyless access control to 04, the identifier code for a passive keyless access control to 05, the identifier code for Bluetooth to 06, the identifier code for an optical rain sensor to 07, the identifier code for a mobile application to 08, the identifier code for an off-vehicle locking signal source to 09, the identifier code for a speed-sensing automatic window closing signal source to 09, the identifier code for automatic window closing in parking status to 10, the identifier code for automatic window closing during car wash to 11, the identifier code for one-touch window lifting to 12, the identifier code for automatic window closing in rain / snow weather mode to 13, the identifier code for automatic window closing in intelligent rest mode to 14, and the identifier code for automatic window closing in "Time and Space Gate" mode to 15, etc.
[0077] It should be noted that the identifier code of the trigger source for the window action can be set according to the actual situation, and this application does not impose specific restrictions on it.
[0078] Based on this, in one embodiment of this application, the above-mentioned S13 may include the following steps:
[0079] Obtain the identifier code of the trigger source for the window action;
[0080] A trigger source signal is generated based on the identifier encoding.
[0081] In practical applications, the above trigger source signal can be represented as: DWC_upkeepSRC = Identifier code of the window action trigger source. For example, if the trigger source is a PWM signal source and the identifier code of the PWM signal source is 01, then the trigger source signal can be represented as: DWC_upkeepSRC = 01.
[0082] After the window controller determines the trigger source for the window action, it can record the current trigger source and continuously send the trigger source signal to the bus. This allows the bus to record the trigger source corresponding to the current window control command. When the T-BOX collects bus data and sends it to the data management backend, the data management backend can record the trigger source corresponding to this window action trigger event. This makes it easier to find the source of the fault when receiving user reports or complaints, thereby improving the efficiency of fault diagnosis.
[0083] To facilitate the explanation of the beneficial effects of the window control method provided in the embodiments of this application, Figure 3 A timing diagram of the window control method provided in an embodiment of this application is shown. Figure 3As shown, at time T1, the actual action of the window is a window raising action, triggered by source 1, and this window raising action is maintained from T1 to T2, after which it returns to a state of no action. The window controller detects the window action trigger event (i.e., source 1 triggering the window raising action) at time T1. At this time, the window controller records the window control command (i.e., the window raising control command) and performs a hold process on this command. That is, the window raising control command is maintained even after the window action ends (after time T2) until a window lowering action is detected at time T3, at which point the window control command is updated to a window lowering control command.
[0084] Meanwhile, after the window controller detects that the trigger source of the window action event is Source 1, it can record that the window action trigger source is Source 1 and continuously output the information that the window action trigger source is Source 1 to the bus until a new window action trigger event is detected. Here, since the trigger source of the window lowering action at time T3 is still Source 1, the trigger source information output after time T3 will still be the information that the trigger source is Source 1, until time T5 when the trigger source changes to Source 2, at which point the trigger source information will change to the information that the trigger source is Source 2.
[0085] In this embodiment of the application, the bus mentioned above includes a CAN bus.
[0086] As can be seen from the above, the window control method provided in this application embodiment maintains the window control command of the above-mentioned window trigger event in the window controller and continuously sends the above-mentioned window control command to the bus until a new window action trigger event is received. In this way, when the vehicle remote information processor uploads the bus command to the data management background, it can collect the window control command, so that the data management background can record the relevant information of the above-mentioned window control command.
[0087] Please see Figure 4 , Figure 4 This illustration shows a schematic diagram of the implementation flow of another window control method provided in an embodiment of this application. Figure 4 As shown in this embodiment, the relevant information of the window action triggering event includes the window action type. In this embodiment, the window action type includes window raising action type and window lowering action type. When a window action triggering event is detected, the window controller can determine the window action type corresponding to the window action triggering event.
[0088] For example, when the window controller receives a window lowering control command from a passenger at time T3, the window controller determines that the window action type is a window lowering action type.
[0089] The above-mentioned window control method may include the following steps:
[0090] S14: Determine whether the window action type is the same as the window action type of the previous window control command. If so, execute S15; otherwise, execute S16.
[0091] S15: Keep the window control command unchanged and continue to perform hold processing on the window control command to continuously send the window control command to the bus.
[0092] S16: Update the window control command and perform a hold process on the updated window control command to continuously send the updated window control command to the bus until the next window action trigger event is detected.
[0093] In this embodiment of the application, when a window action trigger event is detected, the window action type of the current window trigger event is compared with the window action type of the previous window trigger event. If they are the same, the original window action command is maintained. Only if they are different, the window action command recorded by the window controller is changed. This can reduce the number of times the window action command output by the window controller is changed.
[0094] For example, please refer to [the document / reference]. Figure 3 The window controller detects window action trigger events at times T1, T3, and T5. Taking time T3 as an example, the window controller detects a window lowering action triggered by source 1 at time T3. It then compares the window action type (i.e., window lowering action type) of the window action trigger event detected at time T3 with the window action type detected at time T1. Since the window action type detected at time T1 is a window raising action type, the two are different. Therefore, the window controller updates the window raising control command to a window lowering control command and performs a hold process on the window lowering control command so that the window controller continues to output window lowering control commands to the bus. Taking time T5 as an example, when the window controller detects the window lowering action triggered by source 2 at time T5, it compares the window action type (i.e., window lowering action type) of the window action triggering event detected at time T5 with the window action type detected at time T3. Since the window action type detected at time T3 is also the window lowering action type, the two are the same. Therefore, the window controller keeps the window lowering action command unchanged and continues to send the window lowering action command to the bus.
[0095] Please see Figure 5 , Figure 5 This illustration shows a schematic flowchart of another window control method provided in an embodiment of this application. In this embodiment, the above-mentioned window control method may include the following steps:
[0096] S17: Determine whether the window action trigger source of the window action trigger event is the same as the window action trigger source corresponding to the previous trigger source signal. If so, execute S18; otherwise, execute S19.
[0097] S18: Keep the trigger source signal unchanged and continue to send the trigger source signal to the bus.
[0098] S19: Update the trigger source signal and continuously send the updated trigger source signal to the bus.
[0099] In this embodiment of the application, when a window action triggering event is detected, the window action triggering source of the current window triggering event is compared with the window action triggering source of the previous window triggering event. If the two are the same, the original triggering source signal is maintained. Only if the two are different is the triggering source signal changed, which can reduce the number of times the triggering source signal output by the window controller is changed.
[0100] For example, please refer to [the document / reference]. Figure 3 The window controller detects window action trigger events at times T1, T3, and T5. Taking time T3 as an example, the window controller detects a window lowering action triggered by source 1 at time T3. The window action trigger source (source 1) of the window action trigger event detected at time T3 is compared with the window action trigger source detected at time T1. Since the window action trigger source detected at time T1 is also source 1, the two are the same. Therefore, the window controller keeps the trigger source signal DWC_upkeepSRC = 01 unchanged. Taking time T5 as an example, when the window controller detects a window lowering action triggered by source 2 at time T5, it compares the window action triggering source (source 2) of the window action triggering event detected at time T5 with the window action triggering source detected at time T3. Since the window action triggering source detected at time T3 is source 1, the two are different. Therefore, the window controller updates the above triggering source signal from DWC_upkeepSRC=01 to DWC_upkeepSRC=02 and continues to send the triggering source signal of DWC_upkeepSRC=02 to the bus.
[0101] Please see Figure 6 , Figure 6 This illustration shows a schematic diagram of the implementation flow of another window control method provided in an embodiment of this application. In this embodiment, the window controller sends a signal flag bit to the bus. Accordingly, the above-mentioned window control method may further include the following steps:
[0102] S20: Determine the parameters of the signal flag bit based on the window action type and window action trigger source of the window action triggering event.
[0103] In this embodiment of the application, since the window control command and the window action triggering source are kept in a holding process, if the same window action is triggered by the same window action triggering source within a period of time, the bus cannot distinguish between the two window action triggering events. In order to make the window action triggering events distinguishable, this embodiment of the application sets a signal flag bit to record the window action triggering events.
[0104] Specifically, the above-mentioned S20 may include the following steps:
[0105] If the window action type of the window action triggering event is the same as the window action type of the previous window control command, and the window action triggering source of the window action triggering event is the same as the window action triggering source in the previous triggering source signal, then the signal flag position is set to the first state position.
[0106] In this embodiment, since the trigger source of the current window action triggering event is the same as that of the previous window action triggering event, and the window action type of the current event is also the same as that of the previous event, the window controller will not update the window control command and trigger source signal being sent. Therefore, the bus data collected by the T-BOX cannot distinguish between the two window action triggering events and will identify them as a single event, making it difficult to determine the timing of the fault. Therefore, when the trigger source of the current window action triggering event is the same as that of the previous event, and the window action type of the current event is also the same as that of the previous event, the window controller can set the signal flag to a first state bit. The first state bit indicates that a new window action triggering event has been detected.
[0107] In practical applications, the aforementioned signal flag bit can include 2 bits, and the first state bit of the signal flag bit can be 01. The initial state bit of the signal flag bit can be 00. In other cases, the signal flag bit is 00. Only when the trigger source of the current window action triggering event is the same as the trigger source of the previous window action triggering event, and the window action type of the current window action triggering event is also the same as the window action type of the previous window action triggering event, will the window controller set the signal flag bit to 01. In this way, the bus data collected by the T-BOX can distinguish between these two window action triggering events based on the parameters of the signal flag bit.
[0108] It should be noted that the initial state bit and the first state bit of the above signal flag can be set according to the actual situation. For example, the initial state bit can be set to 10 and the first state bit can be set to 00, or the initial state bit can be set to 01 and the first state bit can be set to 11, etc.
[0109] In another embodiment of this application, the above-described S20 may further include the following steps:
[0110] When the duration of the signal flag being in the first state position reaches a preset time threshold, the signal flag is set to the initial state position.
[0111] In this embodiment of the application, the above-mentioned preset time threshold can be set according to the actual situation, such as 20s.
[0112] By keeping the signal flag in the first state position for a preset time threshold duration, the T-BOX can collect the transition status, thereby enabling the background data to record relevant information for each window action trigger event. When the duration of the signal flag in the first state reaches the preset time threshold, the signal flag is set to the initial state position to restore the initial state and avoid misidentification.
[0113] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.
[0114] Corresponding to the window control method in the above embodiment, Figure 7 A structural block diagram of a window control device according to an embodiment of this application is shown. For ease of explanation, only the parts related to the embodiment of this application are shown. (Refer to...) Figure 7 The window control device 70 includes:
[0115] The acquisition module 71 is used to acquire relevant information about the window action triggering event when a window action triggering event is detected. The relevant information includes the window control command and the window action triggering source of the window action triggering event.
[0116] The first sending module 72 is used to perform hold processing on the window control command to continuously send the window control command to the bus until the next window action trigger event is detected.
[0117] The second sending module 73 is used to continuously send a trigger source signal to the bus according to the window action trigger source until the next window action trigger event is detected.
[0118] In one implementation, the second sending module 73 may include an identifier encoding acquisition unit and an encoding generation unit.
[0119] The aforementioned identification encoding acquisition unit is used to acquire the identification encoding of the window action trigger source.
[0120] The aforementioned generation unit is used to generate a trigger source signal based on the identifier encoding.
[0121] In one implementation, the aforementioned window control device may further include a first judgment module.
[0122] The first judgment module is configured to, if the window action type is the same as the window action type of the previous window control command, keep the window control command unchanged and continue to perform hold processing on the window control command to continuously send the window control command to the bus; if the window action type is different from the window action type of the previous window control command, update the window control command and perform hold processing on the updated window control command to continuously send the updated window control command to the bus until the next window action trigger event is detected.
[0123] In one implementation, the aforementioned window control device may further include a second judgment module.
[0124] The second judgment module is used to maintain the trigger source signal unchanged and continuously send the trigger source signal to the bus if the window action trigger source of the window action triggering event is the same as the window action trigger source corresponding to the previous trigger source signal; if the window action trigger source of the window action triggering event is different from the window action trigger source corresponding to the previous trigger source signal, the trigger source signal is updated and the updated trigger source signal is continuously sent to the bus.
[0125] In one implementation, the aforementioned window control device may further include a positioning module.
[0126] The aforementioned setting module is used to determine the parameters of the signal flag bit based on the window action type and window action trigger source of the window action triggering event.
[0127] In one implementation, the aforementioned setting module is specifically used to set the signal flag to the first state bit if the window action type of the window action triggering event is the same as the window action type of the previous window control command, and the window action triggering source of the window action triggering event is the same as the window action triggering source in the previous triggering source signal.
[0128] In one implementation, the setting module is further configured to set the signal flag to the initial state bit when the duration of the signal flag being set to the first state bit reaches a preset time threshold.
[0129] As can be seen from the above, the window control device provided in this application embodiment can also maintain the window control command of the window trigger event in the window controller after detecting the window action trigger event, and continuously send the window control command to the bus until a new window action trigger event is received. In this way, when the vehicle telematics processor uploads bus commands to the data management background, it can collect the window control command, so that the data management background can record the relevant information of the window control command. Based on this, when a user's fault complaint is received, the source of the fault can be determined by the relevant information of the window control command recorded in the data management background, thereby improving the efficiency and accuracy of fault diagnosis.
[0130] Figure 8 This is a schematic diagram of the structure of a terminal device provided in an embodiment of this application. Figure 8 As shown, the terminal device 8 of this embodiment includes: at least one processor 80 ( Figure 8 (Only one is shown) a processor, a memory 81, and a computer program 82 stored in the memory 81 and executable on the at least one processor 80, wherein the processor 80 executes the computer program 82 to implement the steps in any of the above embodiments of the window control method.
[0131] Those skilled in the art will understand that Figure 8 This is merely an example of terminal device 8 and does not constitute a limitation on terminal device 8. It may include more or fewer components than shown in the figure, or combine certain components, or different components, such as input / output devices, network access devices, etc.
[0132] The processor 80 may be a Central Processing Unit (CPU), or it may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor.
[0133] In some embodiments, the memory 81 may be an internal storage unit of the terminal device 8, such as a hard disk or memory of the terminal device 8. In other embodiments, the memory 81 may be an external storage device of the terminal device 8, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the terminal device 8. Furthermore, the memory 81 may include both internal and external storage units of the terminal device 8. The memory 81 is used to store the operating system, applications, bootloader, data, and other programs, such as the program code of the computer program. The memory 81 can also be used to temporarily store data that has been output or will be output.
[0134] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, can implement the steps in any of the above-described embodiments of the window control method.
[0135] This application provides a computer program product that, when run on a terminal device, enables the terminal device to implement the steps in any of the above-described window control method embodiments.
[0136] This application provides a vehicle that includes the device in the above-described window control device embodiment, or the device / unit in the above-described terminal device embodiment.
[0137] It should be noted that the information interaction and execution process between the above-mentioned devices / units are based on the same concept as the method embodiments of this application. For details on their specific functions and technical effects, please refer to the method embodiments section, and they will not be repeated here.
[0138] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is merely an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one first processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the functional units and modules are only for easy differentiation and are not intended to limit the scope of protection of this application. The specific working process of the units and modules in the above system can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.
[0139] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.
[0140] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0141] In the embodiments provided in this application, it should be understood that the disclosed window control method can be implemented in other ways. For example, the device / terminal equipment embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual coupling or direct coupling or communication connection may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.
[0142] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0143] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.
Claims
1. A method for controlling vehicle windows, characterized in that, include: When a window action trigger event is detected, relevant information about the window action trigger event is obtained, including the window control command and the window action trigger source of the window action trigger event. The window control command is held to continuously send the window control command to the bus until the next window action trigger event is detected; The system continuously sends trigger source signals to the bus based on the window action trigger source until the next window action trigger event is detected.
2. The window control method as described in claim 1, characterized in that, The continuous sending of trigger source signals to the bus based on the window action trigger source until the next window action trigger event is detected includes: Obtain the identifier code of the trigger source for the window action; A trigger source signal is generated based on the identifier encoding.
3. The vehicle window control method as described in claim 1, characterized in that, The information related to the window action triggering event also includes the window action type. After obtaining the relevant information of the window action triggering event upon detection, the process further includes: If the window action type is the same as the window action type of the previous window control command, the window control command remains unchanged, and the window control command continues to be processed to continuously send the window control command to the bus. If the window action type is different from the window action type of the previous window control command, the window control command is updated, and a hold process is performed on the updated window control command to continuously send the updated window control command to the bus until the next window action trigger event is detected.
4. The vehicle window control method as described in claim 1, characterized in that, After obtaining relevant information about the window action triggering event upon detection, the method further includes: If the window action triggering source of the aforementioned window action triggering event is the same as the window action triggering source corresponding to the previous triggering source signal, then the triggering source signal remains unchanged, and the triggering source signal is continuously sent to the bus. If the window action trigger source of the window action triggering event is different from the window action trigger source corresponding to the previous trigger source signal, then the trigger source signal is updated, and the updated trigger source signal is continuously sent to the bus.
5. The window control method according to any one of claims 1 to 4, characterized in that, The information related to the window action triggering event also includes a signal flag bit. After obtaining the relevant information of the window action triggering event upon detection, the process further includes: The parameters of the signal flag are determined based on the window action type and the window action trigger source of the window action triggering event.
6. The window control method as described in claim 5, characterized in that, The parameters for determining the signal flag bit based on the window action type and window action trigger source of the window action trigger event include: If the window action type of the window action triggering event is the same as the window action type of the previous window control command, and the window action triggering source of the window action triggering event is the same as the window action triggering source in the previous triggering source signal, then the signal flag is set to the first state bit.
7. The vehicle window control method as described in claim 6, characterized in that, If the window action type of the window action triggering event is the same as the window action type of the previous window control command, and the window action triggering source of the window action triggering event is the same as the window action triggering source in the previous triggering source signal, then after setting the signal flag to the first state bit, the method further includes: When the duration of the signal flag being in the first state position reaches a preset time threshold, the signal flag is set to the initial state position.
8. A vehicle window control device, characterized in that, The window control device includes: The acquisition module is used to acquire relevant information about the window action triggering event when a window action triggering event is detected. The relevant information includes the window control command and the window action triggering source of the window action triggering event. The first sending module is used to perform holding processing on the window control command to continuously send the window control command to the bus until the next window action trigger event is detected. The second sending module is used to continuously send trigger source signals to the bus according to the window action trigger source until the next window action trigger event is detected.
9. A terminal device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the window control method as described in any one of claims 1 to 7.
10. A vehicle comprising a window control device as claimed in claim 8, or a terminal device as claimed in claim 9.