Control method and device of vehicle charger, storage medium and vehicle charger

Abstract

This application provides a control method, device, storage medium, and vehicle charger for an on-board charger. The on-board charger has a receiving cavity for placing a device to be charged. Airbags are embedded in the opposite side walls of the receiving cavity. The method includes: in response to detecting that a device to be charged is placed in the receiving cavity for charging, inflating the airbags to secure the device; after the airbags are fully inflated, acquiring environmental data within a preset distance range in front of the vehicle and acquiring current state data of the device to be charged; based on the environmental data and the current state data, determining the probability that the device to be charged will be removed from the receiving cavity by a user; and based on the removal probability, determining whether to deflate the airbags. The technical solution provided by the embodiments of this application can improve the user experience of the on-board charger.

Description

Technical Field

[0001] This application relates to the field of vehicle charger technology, and more specifically, to a control method, device, storage medium, and vehicle charger for a vehicle charger. Background Technology

[0002] As vehicles become increasingly feature-rich, car chargers are typically installed in vehicles to facilitate charging of devices such as mobile phones. However, it's understandable that if a phone slips or slides during charging, it could be damaged or cause injury to passengers. Therefore, to prevent this, phones are currently secured firmly throughout the charging process. This design increases the resistance for users to handle their phones while charging, thus reducing the user experience of the car charger. Summary of the Invention

[0003] The embodiments of this application provide a control method, device, storage medium, and vehicle charger for a vehicle charger. The technical solutions provided by this application can improve the user experience of vehicle chargers.

[0004] Other features and advantages of this application will become apparent from the following detailed description, or may be learned in part from practice of this application.

[0005] According to a first aspect of the present application, a control method for an on-board charger is provided. The method includes: the on-board charger having a receiving cavity for placing a device to be charged, and airbags embedded in the oppositely disposed side walls of the receiving cavity; the method includes: in response to detecting that the device to be charged is placed in the receiving cavity for charging, inflating the airbags to fix the device to be charged; after the airbags are fully inflated, acquiring environmental data within a preset distance range in front of the vehicle, and acquiring current state data of the device to be charged; based on the environmental data and the current state data, determining the probability of the device to be charged being removed from the receiving cavity by a user; and based on the removal probability, determining whether to deflate the airbags.

[0006] In some embodiments of this application, based on the foregoing scheme, determining the probability of the device to be charged being removed from the receiving cavity by the user based on the environmental data and the current state data includes: determining whether there is a payment scenario in front of the vehicle based on the environmental data, and determining whether the device to be charged has received communication information based on the current state data; if there is a payment scenario in front of the vehicle and the device to be charged has not received communication information, then acquiring the user's first behavior data in a historical time period, the first behavior data including the user's behavior data on whether the device to be charged was removed from the receiving cavity when there was a payment scenario in front of the vehicle; based on the first behavior data, determining a first probability, and using the first probability as the removal probability, the first probability being used to characterize the probability that the device to be charged is removed from the receiving cavity by the user when there is a payment scenario in front of the vehicle.

[0007] In some embodiments of this application, based on the foregoing scheme, the method further includes: if there is no payment scenario in front of the vehicle and the device to be charged receives communication information, then acquiring second behavioral data of the user in a historical time period, the second behavioral data including behavioral data of whether the user moves the device to be charged out of the receiving cavity when the device to be charged receives communication information; based on the second behavioral data, determining a second probability, and using the second probability as the removal probability, the second probability being used to characterize the probability that the device to be charged is moved out of the receiving cavity by the user when the device to be charged receives communication information.

[0008] In some embodiments of this application, based on the foregoing scheme, the method further includes: if there is a payment scenario in front of the vehicle and the charging device receives communication information, then obtaining the first probability and the second probability; and determining the moveout probability based on the first probability and the second probability.

[0009] In some embodiments of this application, based on the foregoing scheme, determining whether to deflate the airbag based on the removal probability includes: if the removal probability is greater than a preset probability threshold, then acquiring the current acceleration data of the vehicle; and determining whether to deflate the airbag based on the current acceleration data.

[0010] In some embodiments of this application, based on the foregoing scheme, the current acceleration data includes the current longitudinal acceleration and the current lateral acceleration. Determining whether to deflate the airbag based on the current acceleration data includes: if the absolute value of the current longitudinal acceleration is less than a first preset threshold and the absolute value of the current lateral acceleration is less than a second preset threshold, then the airbag is deflated.

[0011] In some embodiments of this application, based on the foregoing scheme, after deflating the airbag, the method further includes: detecting whether the device to be charged has been removed from the receiving cavity by the user within a preset time period; if the device to be charged has not been removed from the receiving cavity by the user within the preset time period, then inflating the airbag to re-secure the device to be charged.

[0012] According to a second aspect of the present application, a control device for a vehicle charger is provided. The vehicle charger has a receiving cavity for placing a device to be charged. Airbags are embedded in the opposite side walls of the receiving cavity. The device includes: an inflation unit for inflating the airbags in response to detecting that the device to be charged is placed in the receiving cavity for charging, thereby securing the device to be charged; an acquisition unit for acquiring environmental data within a preset distance range in front of the vehicle and acquiring current state data of the device to be charged after the airbags have been inflated; a first determination unit for determining, based on the environmental data and the current state data, the probability of the device to be charged being removed from the receiving cavity by a user; and a second determination unit for determining, based on the removal probability, whether to deflate the airbags.

[0013] According to a third aspect of the embodiments of this application, a computer-readable storage medium is provided, characterized in that the computer-readable storage medium stores at least one piece of program code, the at least one piece of program code being loaded and executed by a processor to perform the operations performed by the method described in any of the first aspects above.

[0014] According to a fourth aspect of the embodiments of this application, an on-board charger is provided, including one or more processors and one or more memories, wherein the one or more memories store at least one piece of program code, which is loaded and executed by the one or more processors to perform the operations performed by the method described in any of the first aspects above.

[0015] The technical solution of this application provides an on-board charger with a cavity for placing a device to be charged. Airbags are embedded in the opposite side walls of the cavity. During the control of the on-board charger, when the device to be charged is detected being placed in the cavity for charging, the airbags are inflated to secure the device. After the airbags are fully inflated, environmental data within a preset distance range in front of the vehicle and the current state data of the device to be charged are acquired. Then, based on the environmental data and the current state data, the probability of the device being removed from the cavity by the user is determined. Finally, based on the removal probability, it is determined whether to deflate the airbags. Therefore, based on the technical solution of this application, the airbag in the vehicle charger can provide a firm clamping force to the device to be charged when the user does not need to remove the device, thereby preventing the device from slipping or sliding. When the user needs to remove the device, the airbag in the vehicle charger can automatically deflate in advance, thereby reducing the resistance for the user to remove the device from the receiving cavity, making it easier for the user to remove the device from the receiving cavity, and thus improving the user's experience of using the vehicle charger.

[0016] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0017] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application. It is obvious that the drawings described below are merely some embodiments of this application, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort. In the drawings:

[0018] Figure 1 A schematic diagram of the structure of an on-board charger according to an embodiment of this application is shown;

[0019] Figure 2 A schematic flowchart of a control method for an on-board charger according to an embodiment of this application is shown;

[0020] Figure 3 A detailed flowchart illustrating a process for determining whether to deflate the airbag based on the removal probability, according to an embodiment of this application, is shown.

[0021] Figure 4 A block diagram of a control device for an on-board charger according to an embodiment of this application is shown;

[0022] Figure 5 A schematic diagram of the structure of an on-board charger according to an embodiment of this application is shown. Detailed Implementation

[0023] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, these exemplary embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided to make this application more comprehensive and complete, and to fully convey the concept of the exemplary embodiments to those skilled in the art.

[0024] Furthermore, the described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. Numerous specific details are provided in the following description to give a thorough understanding of embodiments of this application. However, those skilled in the art will recognize that the technical solutions of this application can be practiced without one or more of the specific details, or other methods, components, apparatuses, steps, etc., can be employed. In other instances, well-known methods, apparatuses, implementations, or operations are not shown or described in detail to avoid obscuring various aspects of this application.

[0025] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities can be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0026] The flowcharts shown in the accompanying drawings are merely illustrative and do not necessarily include all content and operations / steps, nor do they necessarily have to be performed in the described order. For example, some operations / steps can be broken down, while others can be combined or partially combined; therefore, the actual execution order may change depending on the specific circumstances.

[0027] It should be noted that "multiple" in this article refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0028] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such uses of these terms can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described.

[0029] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0030] Before introducing the control method of the on-board charger in the embodiments of this application, let's first combine... Figure 1 The structure of the vehicle charger provided in this application is described.

[0031] See Figure 1 The diagram shows a structural schematic of an on-board charger according to an embodiment of this application.

[0032] In this application, optionally, the provided vehicle charger 10 can be a wired vehicle charger or a wireless vehicle charger. It is understood that the vehicle charger 10 can provide power to the device to be charged.

[0033] Optionally, in this application, the provided vehicle charger 10 has a receiving cavity 11 for placing the device to be charged. If the vehicle charger 10 is a vehicle wireless charger, the receiving cavity 11 can not only be a cavity for placing the device to be charged, but also a charging cavity for providing power to the device to be charged. It is understood that a charging coil can be provided below the receiving cavity 11. When the device to be charged is placed in the receiving cavity 11, the charging coil charges the device to be charged, thereby realizing wireless charging of the device to be charged.

[0034] Similarly, if the vehicle charger 10 is a wired vehicle charger, then when the device to be charged is charged using the vehicle charger 10, the device to be charged can be placed in the receiving cavity 11.

[0035] Optionally, in this application, airbags 12 are embedded in the oppositely arranged side walls of the receiving cavity 11, from which airbags 12 are inserted. Figure 1 As can be seen, two airbags can be installed in the vehicle charger 10. Additionally, an air pump can be installed in the vehicle charger 10 to input gas into the airbags 12, thereby inflating the airbags 12. Furthermore, a deflation device can be installed in the vehicle charger to release the gas inside the airbags 12, thereby deflating the airbags 12.

[0036] The following detailed description of some embodiments of this application will be provided in conjunction with the accompanying drawings. Unless otherwise specified, the following embodiments and features can be combined with each other.

[0037] See Figure 2 The diagram illustrates a flow chart of a control method for an on-board charger according to an embodiment of this application, specifically including the following steps 210 to 240:

[0038] Step 210: In response to detecting that the device to be charged is placed in the receiving cavity for charging, the airbag is inflated to secure the device to be charged.

[0039] In this application, the device to be charged can be an electronic device that needs to be charged, including but not limited to mobile phones, Bluetooth headsets, tablets, smartwatches, etc.

[0040] In this embodiment, it can be understood that if the vehicle charger is a vehicle wireless charger, when the charging function of the vehicle charger is detected to be turned on, it can be determined that the device to be charged is placed in the receiving cavity and charging has begun.

[0041] In this embodiment, it should be noted that after detecting that the device to be charged is placed in the receiving cavity for charging, the air pump in the vehicle charger can be controlled to deliver gas into the airbag. After the airbag is inflated, it can wrap and clamp the device to be charged, thereby firmly fixing the device to be charged in the receiving cavity. This prevents the device to be charged from colliding with the side wall of the receiving cavity during vehicle operation, which could cause damage to the device. It also prevents the device to be charged from flying out directly in extreme situations such as rapid acceleration / deceleration or vehicle bumps, which could cause more serious damage to the device to be charged, vehicle interior parts, and passengers.

[0042] See also Figure 2 Step 220: After the airbag is fully inflated, acquire environmental data within a preset distance range in front of the vehicle, and acquire the current status data of the device to be charged.

[0043] That is, after the device to be charged is securely fixed in the receiving cavity by the inflated airbag, step 220 is performed.

[0044] Optionally, in this application, the environmental data within a preset distance range in front of the vehicle can be acquired using the equipment configured on the vehicle itself. For example, the environmental data can be acquired using a vehicle-mounted multi-functional camera or a high-precision map configured in the vehicle.

[0045] In this application, if the device to be charged is connected to the vehicle's Bluetooth, the current status data of the device to be charged can be obtained through the vehicle's Bluetooth. If the device to be charged is not connected to the vehicle's Bluetooth, the current status data of the device to be charged can be obtained based on the microphone installed in the vehicle.

[0046] In this application, the current status data of the device to be charged includes, but is not limited to, status data on whether the device to be charged vibrates, status data on whether the device to be charged emits a phone / SMS / video / voice prompt ringtone, status data on whether the device to be charged emits a message receiving prompt signal, etc.

[0047] See also Figure 2 Step 230: Based on the environmental data and the current state data, determine the probability of the device to be charged being removed from the receiving cavity by the user.

[0048] In this application, there are at least three specific implementation methods for step 230.

[0049] The first implementation of step 230 can be performed according to steps 231 to 233 as follows:

[0050] Step 231: Determine whether there is a payment scenario ahead of the vehicle based on the environmental data, and determine whether the device to be charged has received communication information based on the current status data.

[0051] In this embodiment, specifically, the collected environmental data can be analyzed to determine whether there are scenarios ahead of the vehicle, such as highway toll booths or parking lot toll booths, where users might need to stop and use charging devices to scan and pay. This determines whether a payment scenario exists ahead of the vehicle. It is understood that this payment scenario exists in the direction of the vehicle's current travel path.

[0052] In this embodiment, it should be noted that the communication information received by the device to be charged can be a communication request (such as a phone request, video request, voice request, etc.) sent by the communication information sender to the device to be charged, or a communication message (such as SMS, MMS, instant messaging message, etc.) sent by the communication information sender to the device to be charged. Instant messaging messages can be WeChat messages, QQ messages, etc.

[0053] In this embodiment, specifically, if the device to be charged is monitored for receiving communication information via in-vehicle Bluetooth or a microphone installed in the vehicle, then if it is determined that the device to be charged has issued a prompt sound indicating that a communication request has been received, it can be considered that the device to be charged has received communication information; if it is determined that the device to be charged has issued a prompt sound indicating that a communication message has been received, it can be considered that the device to be charged has received communication information.

[0054] Step 232: If there is a payment scenario in front of the vehicle and the charging device does not receive communication information, then the user's first behavior data in the historical period is obtained. The first behavior data includes whether the user moves out of the charging device from the receiving cavity when there is a payment scenario in front of the vehicle.

[0055] Step 233: Based on the first behavioral data, determine a first probability and use the first probability as the removal probability. The first probability is used to characterize the probability that the charging device will be removed from the receiving cavity by the user when there is a payment scenario in front of the vehicle.

[0056] In step 233, at least two of the following implementation methods exist:

[0057] The first implementation method of step 233:

[0058] The data is used to determine the first number of times the user removed the device from the charging cavity and the second number of times the user did not remove the device from the charging cavity. The sum of the first and second counts is then calculated as the first total count. Finally, the ratio of the first count to the first total count is calculated as the first probability.

[0059] For example, assuming the device to be charged is a mobile phone, by obtaining the first behavior data, it is determined that during the historical period, when the mobile phone is being charged using the car charger, the user removed the mobile phone from the cavity 12 times when there was a payment scenario in front of the vehicle, and did not remove the mobile phone from the cavity 8 times when there was a payment scenario in front of the vehicle. Then the first probability is 0.6, that is, 12 / (12+8).

[0060] The second implementation method of step 233:

[0061] The most recent behavior data is determined from the first behavior data. If the most recent behavior data is that the user removed the charging device from the receiving cavity when there was a payment scenario in front of the vehicle, the first probability is determined to be 1. If the most recent behavior data is that the user did not remove the charging device from the receiving cavity when there was a payment scenario in front of the vehicle, the first probability is determined to be 0.

[0062] In summary, the specific implementation method for determining the first probability based on the first row of data can be designed according to the actual situation, and this application does not limit it here.

[0063] See also Figure 2 The second implementation of step 230 specifically includes the following steps 231A to 232A:

[0064] Step 231A: If there is no payment scenario in front of the vehicle and the charging device receives communication information, then the user's second behavior data in the historical period is obtained. The second behavior data includes the user's behavior data of whether the user moved out of the receiving cavity when the charging device received the communication information.

[0065] Step 232A: Based on the second behavioral data, determine the second probability and use the second probability as the removal probability. The second probability is used to characterize the probability that the device to be charged is removed from the receiving cavity by the user when the device to be charged receives communication information.

[0066] In step 232A, the specific implementation methods include at least the following four:

[0067] The first implementation of step 232A:

[0068] If the communication information received by the device to be charged is a communication request, then the third line of data is determined from the second line of data. This third line of data is the behavior data of whether the user removed the device to be charged from the receiving cavity when the device to be charged received the communication request. Then, the third number of times the user removed the device to be charged from the receiving cavity and the fourth number of times the user did not remove the device to be charged from the receiving cavity are determined from the third line of data. Then, the sum of the third number and the fourth number is calculated as the second total number. Finally, the ratio of the third number to the second total number is calculated as the second probability.

[0069] For example, assuming the device to be charged is a mobile phone, by obtaining third-line data, it is determined that during a historical period, when the mobile phone was being charged using a car charger, the user removed the mobile phone from the housing 12 times when the mobile phone received a communication request, and did not remove the mobile phone from the housing 8 times when the mobile phone received a communication request. Then the second probability is 0.6, that is, 12 / (12+8).

[0070] The second implementation of step 232A:

[0071] If the communication information received by the device to be charged is a communication request, then a third set of data is determined from the second set of data. This third set of data is the data on whether the user removed the device from the receiving cavity when the device received the communication request. The most recent set of data is determined from the third set of data. If the most recent set of data is that the user removed the device from the receiving cavity when the device received the communication request, then the second probability is set to 1. If the most recent set of data is that the user did not remove the device from the receiving cavity when the device received the communication request, then the second probability is set to 0.

[0072] It should be noted that if the received communication information is a communication message, the specific implementation method can be similar to that when the communication information is a communication request. Therefore, the implementation method for communication type communication message can be designed with reference to the first and second implementation methods in step 232A above. This application will not elaborate on this further.

[0073] The third implementation of step 232A:

[0074] The fifth number of times the user removed the device from the receiving cavity is determined from the second set of data, and the sixth number of times the user did not remove the device from the receiving cavity is determined from the second set of data; then the sum of the fifth and sixth times is calculated as the third total number; finally, the ratio of the fifth number to the third total number is calculated as the second probability.

[0075] It is understandable that the third implementation of step 232A, compared to the first implementation of step 232A described above, does not take into account the type of communication information received by the device to be charged.

[0076] The fourth implementation of step 232A:

[0077] The most recent behavior data is determined from the second behavior data. If the most recent behavior data is that the user moved the device out of the charging cavity when the device to be charged received the communication information, the second probability is determined to be 1. If the most recent behavior data is that the user did not move the device out of the charging cavity when the device to be charged received the communication information, the second probability is determined to be 0.

[0078] It is understandable that the fourth implementation of step 232A, compared with the second implementation of step 232A above, does not take into account the type of communication information received by the device to be charged.

[0079] See also Figure 2 The third implementation of step 230 specifically includes the following steps 231B to 232B:

[0080] Step 231B: If there is a payment scenario ahead of the vehicle and the charging device receives communication information, then obtain the first probability and the second probability.

[0081] It is understood that the specific implementation method for obtaining the first probability can be executed according to the first implementation method of step 230 above, so it will not be described in detail here. The specific implementation method for obtaining the second probability can be executed according to the second implementation method of step 230 above, so it will not be described in detail here.

[0082] Step 232B: Determine the removal probability based on the first probability and the second probability.

[0083] There are at least two specific implementation methods for step 232B.

[0084] The first implementation of step 232B:

[0085] The product of the first and second removal probabilities can be used as the removal probability.

[0086] For example, assuming the device to be charged is a mobile phone, at the current moment it is determined that there is a payment scenario in front of the vehicle and that the device to be charged has received communication information. Then, after analyzing the first set of data, the first probability is determined to be 0.6, and after analyzing the second set of data, the second probability is determined to be 0.5. Therefore, 0.3 can be used as the probability of being removed.

[0087] The second implementation of step 232B:

[0088] First, a first weight and a second weight can be obtained. The first weight is used to characterize the importance of removing the charging device from the receiving cavity when there is a payment scenario in front of the vehicle, and the second weight is used to characterize the importance of removing the charging device from the receiving cavity when the charging device receives communication information. Then, the first product of the first weight and the first probability is calculated, and the second product of the second weight and the second probability is calculated. Finally, the sum of the first product and the second product is used as the removal probability.

[0089] The first and second weights can be designed according to actual conditions, and this application does not impose any restrictions on them.

[0090] See also Figure 2 Step 240: Based on the removal probability, determine whether to deflate the airbag.

[0091] In this application, the specific implementation of step 240 can be as follows: Figure 3 Perform the steps shown:

[0092] See Figure 3 The diagram illustrates a detailed process for determining whether to deflate the airbag based on the removal probability according to an embodiment of this application, specifically including the following steps 241 to 242:

[0093] Step 241: If the probability of moving out is greater than a preset probability threshold, then obtain the current acceleration data of the vehicle.

[0094] In this embodiment, optionally, the preset threshold can be set to 0.5, or a value near 0.5. Specifically, this application does not limit it.

[0095] In this application, optionally, the current acceleration data of the vehicle can be obtained by an acceleration sensor, or by comparing the vehicle speed at the current moment with the vehicle speed at the previous moment, or by the magnitude of the accelerator / brake pedal press, etc. The specific details are not limited here.

[0096] Optionally, in this application, the current acceleration data of the vehicle may include the current longitudinal acceleration and the current lateral acceleration.

[0097] It should be noted that longitudinal acceleration is the acceleration in the direction of vehicle travel, while lateral acceleration is the acceleration perpendicular to the direction of vehicle travel. This lateral acceleration refers to the acceleration caused by the centrifugal force generated when the vehicle is turning.

[0098] See also Figure 3 Step 242: Based on the current acceleration data, determine whether to deflate the airbag.

[0099] The specific implementation methods for step 242 include the following two:

[0100] The first implementation of step 242 can be performed as follows:

[0101] Step 2421: If the absolute value of the current longitudinal acceleration is less than a first preset threshold and the absolute value of the current lateral acceleration is less than a second preset threshold, then the airbag is deflated.

[0102] In this embodiment, optionally, the first preset threshold can be set to 4 m / s 2 .

[0103] In this embodiment, optionally, the second preset threshold can be set to 2 m / s 2 .

[0104] In this embodiment, optionally, the gas inside the airbag can be released by controlling the venting device.

[0105] Understandably, if it is determined that the user needs to remove the device to be charged from the receiving cavity, and the vehicle is currently in a relatively stable driving state, the gas in the airbag can be released, making it easier for the user to remove the device from the receiving cavity, thus improving the convenience of the on-board charger and enhancing the user's experience with it.

[0106] The second implementation method in step 242 can be performed as follows:

[0107] Step 2422: If the absolute value of the current longitudinal acceleration is greater than or equal to the first preset threshold, or the absolute value of the current lateral acceleration is greater than or equal to the second preset threshold, then deflation of the airbag is prohibited.

[0108] It is understandable that if the absolute value of the current longitudinal acceleration is greater than or equal to the first preset threshold, or the absolute value of the current lateral acceleration is greater than or equal to the second preset threshold, it indicates that the current driving state of the vehicle is relatively unstable. If the airbag is deflated in an unstable driving state, it may cause the charging device to fly out or slip off, which may damage the charging device or injure the driver and passengers. Therefore, deflation of the airbag should be prohibited.

[0109] In this application, after completing step 2421 above, steps 250 to 260 can be performed as follows:

[0110] Step 250: Detect whether the device to be charged has been removed from the receiving cavity by the user within a preset time period.

[0111] Step 260: If the device to be charged is not removed from the receiving cavity by the user within a preset time period, the airbag is inflated to re-secure the device to be charged.

[0112] In this embodiment, the preset duration can optionally be set to 1 minute, 30 seconds, etc. The specific duration can be set according to actual conditions, and this application does not limit it here.

[0113] In this embodiment, it is understood that if the user does not remove the device to be charged from the receiving cavity within a preset time, it means that the user may not need to remove the device. Therefore, re-inflating the deflated airbag can re-secure the device to be charged, thereby preventing the device from flying out, slipping, or sliding, thus avoiding damage to the device and injury to the driver and passengers, and improving the user's experience with the vehicle charger.

[0114] In some embodiments of this application, the provided vehicle charger has a receiving cavity for placing a device to be charged. Airbags are embedded in the opposite side walls of the receiving cavity. During the control of the vehicle charger, when the receiving cavity is detected to be placed for charging, the airbags are inflated to secure the device. After the airbags are fully inflated, environmental data within a preset distance range in front of the vehicle and the current state data of the device to be charged are acquired. Then, based on the environmental data and the current state data, the probability of the device being removed from the receiving cavity by the user is determined. Finally, based on the removal probability, it is determined whether to deflate the airbags. Therefore, based on the technical solution of this application, the airbag in the vehicle charger can provide a firm clamping force to the device to be charged when the user does not need to remove the device, thereby preventing the device from slipping or sliding. When the user needs to remove the device, the airbag in the vehicle charger can automatically deflate in advance, thereby reducing the resistance for the user to remove the device from the receiving cavity, making it easier for the user to remove the device from the receiving cavity, and thus improving the user's experience of using the vehicle charger.

[0115] Based on the same inventive concept, this application provides a control device for an on-board charger, which can be used to execute the control method for an on-board charger in the above embodiments of this application. For details not disclosed in the embodiments of this application, please refer to the embodiments of the control method for an on-board charger described above.

[0116] See Figure 4 This diagram illustrates a block diagram of a control device for an on-board charger according to an embodiment of the present application.

[0117] like Figure 4 As shown, a control device 400 for a vehicle charger according to an embodiment of this application is provided. The vehicle charger has a receiving cavity for placing a device to be charged. Airbags are embedded in the two side walls of the receiving cavity that are disposed opposite to each other. The device 400 includes: an inflation unit 401, an acquisition unit 402, a first determination unit 403, and a second determination unit 404.

[0118] The system includes an inflation unit 401, configured to inflate the airbag in response to detecting that a device to be charged is placed in the receiving cavity for charging, thereby securing the device; an acquisition unit 402, configured to acquire environmental data within a preset distance range in front of the vehicle and the current status data of the device to be charged after the airbag has been inflated; a first determination unit 403, configured to determine the probability of the device to be charged being removed from the receiving cavity by the user based on the environmental data and the current status data; and a second determination unit 404, configured to determine whether to deflate the airbag based on the removal probability.

[0119] In some embodiments of this application, based on the foregoing scheme, the first determining unit 403 is further configured to: determine whether there is a payment scenario in front of the vehicle based on the environmental data, and determine whether the device to be charged has received communication information based on the current state data; if there is a payment scenario in front of the vehicle and the device to be charged has not received communication information, then obtain the user's first behavior data in a historical period, the first behavior data including the user's behavior data on whether the device to be charged is removed from the receiving cavity when there is a payment scenario in front of the vehicle; based on the first behavior data, determine a first probability, and use the first probability as the removal probability, the first probability being used to characterize the probability that the device to be charged is removed from the receiving cavity by the user when there is a payment scenario in front of the vehicle.

[0120] In some embodiments of this application, based on the foregoing scheme, the first determining unit 403 is further configured to: if there is no payment scenario in front of the vehicle and the device to be charged receives communication information, then acquire second behavioral data of the user in a historical period, the second behavioral data including behavioral data of whether the user moves the device to be charged out of the receiving cavity when the device to be charged receives communication information; based on the second behavioral data, determine a second probability, and use the second probability as the removal probability, the second probability being used to characterize the probability that the device to be charged is moved out of the receiving cavity by the user when the device to be charged receives communication information.

[0121] In some embodiments of this application, based on the foregoing scheme, the first determining unit 403 is further configured to: if there is a payment scenario in front of the vehicle and the charging device receives communication information, then obtain the first probability and the second probability; and determine the moving-out probability based on the first probability and the second probability.

[0122] In some embodiments of this application, based on the foregoing scheme, the second determining unit 404 is further configured to: if the probability of removal is greater than a preset probability threshold, obtain the current acceleration data of the vehicle; and determine whether to deflate the airbag based on the current acceleration data.

[0123] In some embodiments of this application, based on the foregoing scheme, the current acceleration data includes the current longitudinal acceleration and the current lateral acceleration, and the second determining unit 404 is further configured to: deflate the airbag if the absolute value of the current longitudinal acceleration is less than a first preset threshold and the absolute value of the current lateral acceleration is less than a second preset threshold.

[0124] In some embodiments of this application, based on the foregoing scheme, after the airbag is deflated, the second determining unit 404 is further configured to: detect whether the device to be charged has been removed from the receiving cavity by the user within a preset time period; if the device to be charged has not been removed from the receiving cavity by the user within the preset time period, inflate the airbag to re-fix the device to be charged.

[0125] Based on the same inventive concept, embodiments of this application also provide a computer-readable storage medium storing at least one computer program instruction, which is loaded and executed by a processor to perform the operations described above.

[0126] Based on the same inventive concept, this application also provides a vehicle charger.

[0127] See Figure 5 The diagram shows a schematic of a vehicle charger according to an embodiment of the present application. The vehicle charger includes one or more memories 504, one or more processors 502, and at least one computer program (computer program instructions) stored in the memory 504 and executable on the processor 502. When the processor 502 executes the computer program, it implements the method described above.

[0128] Among them, Figure 5 In this document, a bus architecture (represented by bus 500) is used. Bus 500 may include any number of interconnected buses and bridges, linking various circuits including one or more processors represented by processor 502 and memory represented by memory 504. Bus 500 may also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. Bus interface 505 provides an interface between bus 500 and receiver 501 and transmitter 503. Receiver 501 and transmitter 503 may be the same element, i.e., a transceiver, providing a unit for communicating with various other devices over a transmission medium. Processor 502 is responsible for managing bus 500 and general processing, while memory 504 can be used to store data used by processor 502 during operation.

[0129] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored as one or more instructions or codes on or transmitted via a computer-readable medium. Other examples and embodiments are within the scope and spirit of this application and the appended claims. For example, due to the nature of software, the functions described above may be implemented using software executed by a processor, hardware, firmware, hardwired, or any combination thereof. Furthermore, the functional units may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit.

[0130] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For instance, 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, direct coupling, or communication connection may be through some interfaces; the indirect coupling or communication connection between units or modules may be electrical or other forms.

[0131] The units described as separate components may or may not be physically separate. Similarly, the components of the control device may or may not be physical units; they may be located in one place or distributed across multiple units. Some or all of the units can be selected to achieve the purpose of this embodiment, depending on actual needs.

[0132] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing computer program instructions, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0133] The above description is merely an embodiment of this application and is not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A control method for an on-board charger, characterized in that, The on-board charger has a receiving cavity for placing a device to be charged, and airbags are embedded in the oppositely arranged side walls of the receiving cavity. The method includes: In response to detecting that a device to be charged is placed in the receiving cavity for charging, the airbag is inflated to secure the device to be charged; After the airbag is fully inflated, environmental data within a preset distance range in front of the vehicle and the current status data of the device to be charged are acquired. Based on the environmental data and the current state data, the probability of the device to be charged being removed from the receiving cavity by the user is determined; Based on the removal probability, determine whether to deflate the airbag; Determining the probability of the device to be charged being removed from the receiving cavity by the user based on the environmental data and the current state data includes: Based on the environmental data, it is determined whether there is a payment scene ahead of the vehicle, and based on the current status data, it is determined whether the device to be charged has received communication information; If there is a payment scenario in front of the vehicle and the charging device does not receive communication information, then the user's first behavior data in the historical period is obtained. The first behavior data includes whether the user moves out of the charging device from the receiving cavity when there is a payment scenario in front of the vehicle. Based on the first behavioral data, a first probability is determined and used as the removal probability. The first probability is used to characterize the probability that the charging device will be removed from the receiving cavity by the user when there is a payment scenario in front of the vehicle.

2. The method according to claim 1, characterized in that, The method further includes: If there is no payment scenario in front of the vehicle and the charging device receives communication information, then the user's second behavior data in the historical period is obtained. The second behavior data includes the behavior data of whether the user moved out of the receiving cavity when the charging device received the communication information. Based on the second behavioral data, a second probability is determined and used as the removal probability. The second probability is used to characterize the probability that the device to be charged is removed from the receiving cavity by the user when the device to be charged receives communication information.

3. The method according to claim 2, characterized in that, The method further includes: If there is a payment scenario ahead of the vehicle and the charging device receives communication information, then the first probability and the second probability are obtained; The removal probability is determined based on the first probability and the second probability.

4. The method according to claim 1, characterized in that, The step of determining whether to deflate the airbag based on the removal probability includes: If the probability of being removed is greater than a preset probability threshold, then the current acceleration data of the vehicle is obtained; Based on the current acceleration data, determine whether to deflate the airbag.

5. The method according to claim 4, characterized in that, The current acceleration data includes the current longitudinal acceleration and the current lateral acceleration. Determining whether to deflate the airbag based on the current acceleration data includes: If the absolute value of the current longitudinal acceleration is less than a first preset threshold and the absolute value of the current lateral acceleration is less than a second preset threshold, then the airbag is deflated.

6. The method according to claim 5, characterized in that, After deflating the airbag, the method further includes: Detect whether the device to be charged is removed from the receiving cavity by the user within a preset time period; If the device to be charged is not removed from the receiving cavity by the user within a preset time period, the airbag is inflated to re-secure the device to be charged.

7. A control device for an on-board charger, characterized in that, The on-board charger has a receiving cavity for placing a device to be charged. Airbags are embedded in the oppositely arranged side walls of the receiving cavity. The device includes: An inflation unit is used to inflate the airbag in response to detecting that a device to be charged is placed in the receiving cavity for charging, so as to fix the device to be charged. The acquisition unit is used to acquire environmental data within a preset distance range in front of the vehicle and acquire the current status data of the device to be charged after the airbag has been fully inflated. The first determining unit is configured to determine the probability of the device to be charged being removed from the receiving cavity by the user based on the environmental data and the current state data. The first determining unit is further configured to determine whether there is a payment scene ahead of the vehicle based on the environmental data, and to determine whether the charging device has received communication information based on the current status data; If there is a payment scenario in front of the vehicle and the charging device does not receive communication information, then the user's first behavior data in the historical period is obtained. The first behavior data includes whether the user moves out of the charging device from the receiving cavity when there is a payment scenario in front of the vehicle. Based on the first behavioral data, a first probability is determined and used as the removal probability. The first probability is used to characterize the probability that the charging device is removed from the receiving cavity by the user when there is a payment scenario in front of the vehicle. The second determining unit is used to determine whether to deflate the airbag based on the removal probability.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores at least one piece of program code, which is loaded and executed by a processor to perform the operations performed by the method as described in any one of claims 1 to 6.

9. A vehicle charger, characterized in that, The method includes one or more processors and one or more memories, wherein at least one piece of program code is stored in the one or more memories, and the at least one piece of program code is loaded and executed by the one or more processors to implement the method as claimed in any one of claims 1 to 6.

Images