Support control method and device based on screen occlusion event in vehicle-mounted scenario

Abstract

This application provides a bracket control method and device based on screen occlusion events in an in-vehicle scenario. The method is applied to the smart cockpit domain controller of a target vehicle. A smartphone bracket is installed in the cockpit of the target vehicle, and the smartphone bracket holds a terminal device. The smart cockpit domain controller is communicatively connected to the smartphone bracket and the terminal device. Through intelligent interaction between the smart cockpit domain controller, the smartphone bracket, and the terminal device, this application can significantly improve the smoothness of the vehicle's smart cockpit domain controller in scenarios where the screen is occluded by the in-vehicle bracket, compared to a single, mechanical bracket adjustment method. This further enhances the targeting and comprehensiveness of the smart cockpit domain controller, and ensures that the area where the terminal is occluded does not affect the driver's operation of the terminal in the in-vehicle scenario.

Description

Technical Field

[0001] This application relates to the field of vehicle mount technology, and in particular to a mount control method and device based on screen occlusion events in vehicle scenarios. Background Technology

[0002] Car owners often place a holder on the side of the steering wheel, such as a phone holder mounted on the air vent, so that the driver can use the phone while driving. However, in general, car mounts such as phone holders will place the support feet on both sides of the phone to prevent it from falling during sudden stops or turns, thus stabilizing the phone and preventing it from falling.

[0003] However, since most phone stands place the support feet or clamping components on both sides of the screen, they may obstruct the phone's screen area. In scenarios where manual interaction is required, such as the WeChat keyboard interface, the obstructed area may block the position that the user needs to click. This may cause the driver to have to shift their gaze and spend time clicking multiple times to reach that position, which can lead to distraction and affect driving safety.

[0004] Furthermore, given that it is an in-vehicle scenario, it is natural to consider relying on in-vehicle algorithms to solve some complex and specific problems. The interconnection between mobile phones and in-vehicle systems is a future trend. Mobile phone manufacturers or application development companies rarely conduct precise identification and optimization for specific problems in in-vehicle scenarios. This also indicates that the intelligentization of various auxiliary components in the vehicle's smart cockpit is also a future trend.

[0005] Therefore, how to ensure that the obscured area of ​​the phone does not affect the driver's operation of the phone when a screen occlusion event occurs in a vehicle setting is an urgent problem to be solved. Summary of the Invention

[0006] This application provides a bracket control method and device based on screen occlusion events in vehicle scenarios. Compared with a single, mechanical bracket adjustment method, this method can greatly improve the smoothness of the vehicle's smart cockpit domain controller in scenarios where the screen is obscured by the vehicle bracket. It further enhances the pertinence and comprehensiveness of the smart cockpit domain controller and ensures that the area where the terminal is obscured does not affect the driver's operation of the terminal in vehicle scenarios.

[0007] In a first aspect, embodiments of this application provide a bracket control method based on screen occlusion events in a vehicle scenario. The method is applied to the smart cockpit domain controller of a target vehicle. A smartphone bracket is installed in the cockpit of the target vehicle, the smartphone bracket holds a terminal device, and the smart cockpit domain controller is communicatively connected to the smartphone bracket and the terminal device. The method includes:

[0008] Send a request message for clamping status information to the terminal device. The clamping status information includes the position of the application interface identifier and the correspondence between the application interface identifier and the clamping position.

[0009] If a positive response message is received from the terminal device, the clamping status information in the positive response message is extracted; based on the clamping status information, the target clamping position corresponding to the target application interface identifier in the application interface identifier is determined, and the smartphone holder is controlled to adjust the clamping position according to the target clamping position;

[0010] If a negative response message is received from the terminal device, then when the user pre-operates on the terminal device, the application interface of the terminal device is obtained, wherein the application interface is the current application interface when the user pre-operates on the terminal device, and the application interface includes one or more application interface identifiers.

[0011] Based on the application interface, determine the location of the target application interface identifier;

[0012] Based on the location of the target application interface identifier, a target clamping position corresponding to the target application interface identifier is generated according to a preset algorithm, and the smartphone holder is controlled to adjust the clamping position according to the target clamping position.

[0013] This method aims to adjust the clamping position of a smartphone holder by interacting with the target vehicle's smart cockpit domain controller, smartphone holder, and terminal device.

[0014] In real-world applications, smartphone holders may hold smartphones, tablets, game consoles, or other devices. Using the most common smartphone holder structure can present some problems. For example, in a car setting, the lower half of the phone is held in place by the holder, obstructing the sides. When a user needs to perform operations on the lower half of the phone—such as swiping right from the lower left edge or left from the lower right edge to go back—the obstructed edges prevent a quick response, leading to more time spent maneuvering and potentially affecting driving safety.

[0015] Specifically, firstly, the smart cockpit domain controller establishes a communication connection with the smartphone holder and the terminal device. Before sending a request message for clamping status information to the terminal device, the smart cockpit domain controller receives a driving mode function synchronization message from the terminal device through the communication connection. This signifies that the smart cockpit domain controller and the terminal device have reached an agreement regarding adjusting the smartphone holder. The terminal device will provide information support to the smart cockpit domain controller. Subsequently, the smart cockpit domain controller sends a request message for clamping status information to the terminal device. However, considering that the terminal device may have poor network communication, application incompatibility, or other reasons that may cause difficulties for the smart cockpit domain controller in executing subsequent steps, therefore, if the request message is sent... After receiving a positive response message from the terminal device, the smart cockpit domain controller extracts the clamping status information from the positive response message and adjusts the clamping position of the smartphone holder according to the information related to holder adjustment sent by the terminal device. If a negative response message is received from the terminal device, it indicates that there may be a poor network or application incompatibility. In this case, information related to holder adjustment can be obtained through devices such as the image acquisition device in the target vehicle to determine the target application interface identifier in the current terminal device. The target application interface identifier is the commonly used virtual button in the current display application interface of the terminal device. Then, by the correspondence between the position of the target application interface identifier and the clamping position of the smartphone holder, the clamping position of the smartphone holder is adjusted.

[0016] Compared to a single, mechanical bracket adjustment method, the above process greatly improves the smoothness of the vehicle's intelligent cockpit domain controller, further enhancing its relevance and comprehensiveness. Moreover, it ensures that areas where the terminal is obstructed in an in-vehicle scenario do not affect the driver's operation of the terminal.

[0017] In another possible implementation of the first aspect, determining the location of the target application interface identifier based on the application interface includes:

[0018] The application interface is input into the first prediction model to obtain the position of the target application interface identifier in the application interface. The first prediction model is trained based on the recorded information of multiple application interfaces in historical scenarios. The recorded information of each application interface includes the position of all identifiers in the application interface and the position of the target application interface identifier corresponding to the recorded information. The position of all identifiers in the application interface is feature data, and the position of the target application interface identifier corresponding to the recorded information is label data. The target application interface identifier is one or more identifiers in the application interface.

[0019] In this embodiment, the location of the target application interface identifier in the current application interface is determined by a pre-trained first prediction model. Generally, an application interface contains one or more icons, each linked to subsequent operations. Therefore, when the number of times a subsequent operation of an icon is triggered reaches a certain value or far exceeds that of other icons on the application interface, that icon can be considered the target application interface icon. In common terminal devices, application interfaces are typically flat. Therefore, the icons in the application interface occupy a certain area, which is the location of the icon. Obviously, the location of an icon in an application interface is visible and easily accessible. Therefore, the training data for the first prediction model consists of the recorded information of multiple application interfaces, which are the historical application interfaces of the terminal device. The recorded information for each application interface includes the locations of multiple icons within that application interface and the location of the target application interface icon. Based on this, the trained first prediction model can accurately determine the location of the target application interface icon in the current application interface, even if the current application interface has never appeared on the terminal device. The generalization ability of the first prediction model can still predict the target application interface icon and its location within the current application interface.

[0020] In another possible implementation of the first aspect, determining the location of the target application interface identifier based on the application interface includes:

[0021] Obtain operation log information of multiple application interfaces in the history of the terminal device. One of the operation log information of the multiple application interfaces includes the application interface, the identifier in the application interface, the position of the identifier, the touched identifier corresponding to the operation log information, and the position of the touched identifier corresponding to the operation log information.

[0022] Based on the number of times the touched identifier appears in the operation log information of the multiple application interfaces, the target application interface identifier corresponding to each of the multiple application interfaces is analyzed and determined, as well as the position of the target application interface identifier on the application interface.

[0023] Specifically, firstly, historical operation log information of multiple terminal devices is obtained. One of the operation log information may include the operation, the application interface corresponding to the operation, one or more icons in the application interface, the position of the icon on the page, and the position of the icon corresponding to the operation. It can be understood that the operation log information is formed based on the user's touch screen of the terminal device. The operation is the user touching an icon on the application interface. The icon is generally a virtual button in the application interface, such as the send button or exit button in the WeChat chat interface.

[0024] The identifier of the operation corresponding to any one of the multiple operation log information and its position in the application interface are marked. The number of times each identifier is marked in each application interface is counted. If the number of times a certain identifier is marked exceeds a preset threshold, the identifier is determined as the target application interface identifier in the application interface corresponding to the identifier, and the position of the target application interface identifier in the application interface is recorded. This also means that an application interface may have one or more target application interface identifiers, or it may not have a target application interface identifier.

[0025] In another possible implementation of the first aspect, generating a target clamping position corresponding to the target application interface identifier according to a preset algorithm based on the position of the target application interface identifier includes:

[0026] The image acquisition device acquires the obscured area of ​​the screen of the terminal device, wherein the obscured area is the area of ​​the screen of the terminal device that is obscured by the smartphone stand.

[0027] Based on the positions of the obscured area and the target application interface identifier, it is determined whether the proportion of the target application interface identifier falling into the obscured area is greater than a preset first threshold.

[0028] If the proportion of the target application interface identifier falling into the obscured area is greater than the preset first threshold, then a target clamping position corresponding to the target application interface identifier is determined according to the position of the target application interface identifier, wherein the target clamping position is used to make the proportion of the target application interface identifier falling into the obscured area lower than the preset second threshold.

[0029] One of the key aspects of this method is determining the relationship between the obscured area and the location of the target application interface icon. Based on the aforementioned obscured area, it can be determined whether the location of the target application interface icon overlaps with the obscured area. If they overlap, and the proportion of the target application interface icon falling within the obscured area is greater than a preset first threshold, then it can be considered that the obscured area may cause the driver to spend more time interacting with the terminal device. It should be noted that the preset first threshold can be the optimal proportion obtained by the developers through experiments, or it can be set by the user. Optionally, the preset first threshold is 75%.

[0030] After determining that the proportion of the target application interface icon falling into the obscured area is greater than a preset first threshold, the position of the smartphone stand is adjusted according to the position of the target application interface icon so that the proportion of the target application interface icon falling into the obscured area is lower than a preset second threshold. The preset second threshold can also be the optimal proportion obtained by the developers through experiments, or it can be set by the user. Optionally, the preset second threshold is 25%.

[0031] In yet another possible implementation of the first aspect, determining the obscured area of ​​the terminal device's screen includes:

[0032] Receive pressure distribution information on the screen sent by the terminal device;

[0033] The obscured area of ​​the terminal device's screen is determined based on the pressure distribution information.

[0034] Specifically, there are many ways to determine the obscured area of ​​the terminal device's screen. In this embodiment, the obscured area can be determined by analyzing data obtained from the terminal device's built-in sensors or other devices.

[0035] The pressure distribution information can come from various sources. Optionally, the terminal device is equipped with a pressure sensor, which senses the pressure distribution information on the screen. The terminal device receives the pressure distribution information on the screen sent by the terminal device. The pressure distribution information includes the pressure information of the area of ​​the screen held by the smartphone holder and the pressure information of the area of ​​the screen not held by the smartphone holder. It is understood that the pressure values ​​in the two types of pressure information are significantly different. Therefore, the obstructed area of ​​the screen of the terminal device can be determined based on the pressure distribution information.

[0036] The blocked area is determined by obtaining pressure distribution information through the hardware facilities of the terminal device. In this process, the data information is clearly exchanged. The target vehicle only needs to establish a communication connection with the terminal device to obtain the required data information by using the hardware facilities built into the terminal device.

[0037] In yet another possible implementation of the first aspect, determining the obscured area of ​​the terminal device's screen includes:

[0038] Obtain image information of the location of the smartphone holder;

[0039] The obscured area of ​​the terminal device's screen is determined based on the image information.

[0040] In this embodiment, the obscured area is analyzed and determined using data obtained from devices or components in the target vehicle.

[0041] Specifically, the target vehicle includes an image acquisition device, such as a camera, that is adjustable in the direction of the center console or the shooting direction. The image acquisition device captures image information of the location of the smartphone holder. It is understood that the color or shape of the smartphone holder will be in a distinct area from the terminal device in the image information. Therefore, based on the image information, the obscured area of ​​the screen can be analyzed and determined.

[0042] This implementation can analyze and determine the obstructed area by acquiring data from the target vehicle's built-in device, without establishing a communication connection with the terminal device. This avoids situations where the smartphone holder becomes unadjustable due to poor signal or insufficient battery power, further improving the intelligent cockpit domain controller's processing capabilities and targeting specific scenarios, and enhancing the comprehensiveness of the intelligent cockpit domain controller's problem-solving, thereby improving the driver's driving experience.

[0043] In another possible implementation of the first aspect, the step of determining the target clamping position corresponding to the target application interface identifier based on the position of the target application interface identifier if the proportion of the target application interface identifier falling into the occluded area is greater than the preset first threshold includes:

[0044] If the proportion of the target application interface identifier falling into the occluded area is greater than the preset first threshold, then the position of the target application interface identifier is input into the second prediction model to obtain the target clamping position of the smartphone holder corresponding to the position of the target application interface identifier. The second prediction model is trained based on the position of the target application interface identifier and the clamping position of the smartphone holder corresponding to the position of the target application interface identifier. The position of the target application interface identifier is feature data, and the clamping position is label data.

[0045] One of the key aspects of this method is adjusting the smartphone holder to a position that allows the driver to freely click or use the icons. Since the application interface may contain multiple commonly used icons, using only the position of a single target application interface icon as a reference for adjusting the smartphone holder's position is inappropriate. In this embodiment, a pre-trained second prediction model predicts the target clamping position of the smartphone holder. This target clamping position is the location where the smartphone holder needs to be moved. This means that adjusting the smartphone holder to the target clamping position will allow the driver to use the target application interface icon normally.

[0046] Specifically, the second prediction model is trained based on the position of the target application interface identifier and the adjustment area of ​​the smartphone stand corresponding to the position of the target application interface identifier. The training data includes the following cases: Case 1: There is only one target application interface identifier in the application interface. Therefore, the adjustment area of ​​the smartphone stand corresponding to the position of the target application interface identifier may be higher or lower than the current position of the smartphone stand. The adjusted position of the smartphone stand may fall into the area where the target application interface identifier is located, or it may not fall into it; Case 2: There are multiple target application interface identifiers in the application interface, and the multiple target... The application interface icons are not located all around the screen of the terminal device. Therefore, the adjustment area of ​​the smartphone stand corresponding to the locations of the multiple target application interface icons may be in various positions. However, regardless of the location of the adjustment area, the proportion of the multiple target application interface icons falling into the obscured area is lower than a preset second threshold. Case 3: There are multiple target application interface icons in the application interface, and the multiple target application interface icons are located all around the screen of the terminal device. Therefore, there is no suitable adjustment area of ​​the smartphone stand corresponding to the locations of the multiple target application interface icons. Optionally, the smartphone stand can be reduced in size to make the obscured area on the screen smaller.

[0047] After the above process, the smartphone holder is adjusted to avoid the target application interface logo as much as possible, so as not to affect the driver's use of the target application interface logo.

[0048] In yet another possible implementation of the first aspect, after adjusting the clamping position of the smartphone holder according to the target clamping position, the method further includes:

[0049] It is determined that the user manually adjusts the smartphone holder;

[0050] Obtain the recorded information of the first application interface after the user adjusts the smartphone holder;

[0051] The first prediction model is trained based on the recorded information from the application interface to obtain an updated first prediction model.

[0052] Specifically, due to limitations of the first prediction model obtained through machine learning, there may be errors in judging the target application interface identifier or its location. Therefore, when the driver manually adjusts the smartphone holder, it indicates that the above situation has occurred. Thus, after determining that the driver has manually adjusted the smartphone holder, the positions of one or more identifiers in the application interface of the terminal device, as well as the positions of the identifiers operated on in the application interface, are obtained. Furthermore, the positions of one or more identifiers in the application interface of the terminal device, as well as the positions of the identifiers operated on in the application interface, are used as training data to train the first prediction model to avoid similar situations from occurring.

[0053] In yet another possible implementation of the first aspect, after adjusting the clamping position of the smartphone holder according to the target clamping position, the method further includes:

[0054] It is determined that the user manually adjusts the smartphone holder;

[0055] The position of the target application interface icon after the user adjusts the smartphone holder and the position of the smartphone holder clamped after the user manually adjusts it are obtained.

[0056] The second prediction model is trained based on the location of the target application interface identifier and the position of the smartphone holder clamp after manual adjustment by the user, so as to obtain an updated second prediction model.

[0057] Specifically, due to limitations of the second prediction model obtained through machine learning, there may be issues with the smartphone holder's position adjustment, or the smartphone holder's position may not have been adjusted when it should have been. Therefore, when the driver manually adjusts the smartphone holder, it indicates that the above situation has occurred. Thus, after confirming that the driver manually adjusted the smartphone holder, the location of the operation marker and the location of the smartphone holder after manual adjustment are obtained. Furthermore, the location of the operation marker and the location of the smartphone holder after manual adjustment are used as training data to retrain the second prediction model to avoid the above situation from recurring.

[0058] In another possible implementation of the first aspect, the adjustment method of the smartphone holder is determined according to the target clamping position, including changing the height of the clamping position, reducing the clamping area, or adjusting the clamping direction, or one or more of these.

[0059] Specifically, in this embodiment, the basic structure of the smartphone holder is the same as that of commonly used smartphone holders. However, it should be noted that in order to better avoid the impact of the smartphone holder on the target application interface logo, certain adjustments are made to the structure of the smartphone holder. For example, ball bearings are provided at the connection between the smartphone holders to allow the smartphone holder to move freely up and down. Alternatively, retractable baffles or another smartphone holder are provided at the upper and lower ends of the smartphone holder. This allows for more varied and targeted adjustments to the position of the smartphone holder or the clamping method of the smartphone holder when the area on the screen obscured by the smartphone holder affects the driver's operation of the terminal device.

[0060] Secondly, embodiments of this application provide a bracket control device for vehicle-mounted scenarios based on screen occlusion events. This device includes at least a sending unit, a positive response unit, a first acquisition unit, a first determination unit, and a generation unit. This bracket control device for vehicle-mounted scenarios based on screen occlusion events is used to implement the method described in any embodiment of the first aspect. The sending unit, positive response unit, first acquisition unit, first determination unit, and generation unit are described below:

[0061] The sending unit is used to send a request message for clamping status information to the terminal device. The clamping status information includes the position of the application interface identifier and the correspondence between the application interface identifier and the clamping position.

[0062] A positive response unit is configured to, if a positive response message is received from the terminal device, extract the clamping status information from the positive response message; determine the target clamping position corresponding to the target application interface identifier in the application interface identifier based on the clamping status information; and control the smartphone holder to adjust the clamping position according to the target clamping position.

[0063] The first acquisition unit is configured to acquire the application interface of the terminal device when a negative response message is received from the terminal device and the user is detected to have pre-operated the terminal device, if the application interface is the current application interface when the user pre-operates the terminal device, and the application interface includes one or more application interface identifiers.

[0064] The first determining unit is used to determine the position of the target application interface identifier based on the application interface.

[0065] The generation unit is used to generate a target clamping position corresponding to the target application interface identifier according to the position of the target application interface identifier and according to a preset algorithm, and to control the smartphone holder to adjust the clamping position according to the target clamping position.

[0066] In real-world applications, smartphone holders may hold smartphones, tablets, game consoles, or other devices. Using the most common smartphone holder structure can present some problems. For example, in a car setting, the lower half of the phone is held in place by the holder, obstructing the sides. When a user needs to perform operations on the lower half of the phone—such as swiping right from the lower left edge or left from the lower right edge to go back—the obstructed edges prevent a quick response, leading to more time spent maneuvering and potentially affecting driving safety.

[0067] Specifically, firstly, the smart cockpit domain controller establishes a communication connection with the smartphone holder and the terminal device. Before sending a request message for clamping status information to the terminal device, the smart cockpit domain controller receives a driving mode function synchronization message from the terminal device through the communication connection. This signifies that the smart cockpit domain controller and the terminal device have reached an agreement regarding adjusting the smartphone holder. The terminal device will provide information support to the smart cockpit domain controller. Subsequently, the smart cockpit domain controller sends a request message for clamping status information to the terminal device. However, considering that the terminal device may have poor network communication, application incompatibility, or other reasons that may cause difficulties for the smart cockpit domain controller in executing subsequent steps, therefore, if the request message is sent... After receiving a positive response message from the terminal device, the smart cockpit domain controller extracts the clamping status information from the positive response message and adjusts the clamping position of the smartphone holder according to the information related to holder adjustment sent by the terminal device. If a negative response message is received from the terminal device, it indicates that there may be a poor network or application incompatibility. In this case, information related to holder adjustment can be obtained through devices such as the image acquisition device in the target vehicle to determine the target application interface identifier in the current terminal device. The target application interface identifier is the commonly used virtual button in the current display application interface of the terminal device. Then, by the correspondence between the position of the target application interface identifier and the clamping position of the smartphone holder, the clamping position of the smartphone holder is adjusted.

[0068] Compared to a single, mechanical bracket adjustment method, the above process greatly improves the smoothness of the vehicle's intelligent cockpit domain controller, further enhancing its relevance and comprehensiveness. Moreover, it ensures that areas where the terminal is obstructed in an in-vehicle scenario do not affect the driver's operation of the terminal.

[0069] In another possible implementation of the second aspect, regarding the determination of the location of the target application interface identifier based on the application interface, the first determining unit is specifically used for:

[0070] The application interface is input into the first prediction model to obtain the position of the target application interface identifier in the application interface. The first prediction model is trained based on the recorded information of multiple application interfaces in historical scenarios. The recorded information of each application interface includes the position of all identifiers in the application interface and the position of the target application interface identifier corresponding to the recorded information. The position of all identifiers in the application interface is feature data, and the position of the target application interface identifier corresponding to the recorded information is label data. The target application interface identifier is one or more identifiers in the application interface.

[0071] In this embodiment, the location of the target application interface identifier in the current application interface is determined by a pre-trained first prediction model. Generally, an application interface contains one or more icons, each linked to subsequent operations. Therefore, when the number of times a subsequent operation of an icon is triggered reaches a certain value or far exceeds that of other icons on the application interface, that icon can be considered the target application interface icon. In common terminal devices, application interfaces are typically flat. Therefore, the icons in the application interface occupy a certain area, which is the location of the icon. Obviously, the location of an icon in an application interface is visible and easily accessible. Therefore, the training data for the first prediction model consists of the recorded information of multiple application interfaces, which are the historical application interfaces of the terminal device. The recorded information for each application interface includes the locations of multiple icons within that application interface and the location of the target application interface icon. Based on this, the trained first prediction model can accurately determine the location of the target application interface icon in the current application interface, even if the current application interface has never appeared on the terminal device. The generalization ability of the first prediction model can still predict the target application interface icon and its location within the current application interface.

[0072] In another possible implementation of the second aspect, regarding the determination of the location of the target application interface identifier based on the application interface, the first determination is specifically used for:

[0073] Obtain operation log information of multiple application interfaces in the history of the terminal device. One of the operation log information of the multiple application interfaces includes the application interface, the identifier in the application interface, the position of the identifier, the touched identifier corresponding to the operation log information, and the position of the touched identifier corresponding to the operation log information.

[0074] Based on the number of times the touched identifier appears in the operation log information of the multiple application interfaces, the target application interface identifier corresponding to each of the multiple application interfaces is analyzed and determined, as well as the position of the target application interface identifier on the application interface.

[0075] Specifically, firstly, historical operation log information of multiple terminal devices is obtained. One of the operation log information may include the operation, the application interface corresponding to the operation, one or more icons in the application interface, the position of the icon on the page, and the position of the icon corresponding to the operation. It can be understood that the operation log information is formed based on the user's touch screen of the terminal device. The operation is the user touching an icon on the application interface. The icon is generally a virtual button in the application interface, such as the send button or exit button in the WeChat chat interface.

[0076] The identifier of the operation corresponding to any one of the multiple operation log information and its position in the application interface are marked. The number of times each identifier is marked in each application interface is counted. If the number of times a certain identifier is marked exceeds a preset threshold, the identifier is determined as the target application interface identifier in the application interface corresponding to the identifier, and the position of the target application interface identifier in the application interface is recorded. This also means that an application interface may have one or more target application interface identifiers, or it may not have a target application interface identifier.

[0077] In another possible implementation of the second aspect, in the step of generating a target clamping position corresponding to the target application interface identifier according to a preset algorithm, the generation unit is specifically used for:

[0078] The image acquisition device acquires the obscured area of ​​the screen of the terminal device, wherein the obscured area is the area of ​​the screen of the terminal device that is obscured by the smartphone stand.

[0079] Based on the positions of the obscured area and the target application interface identifier, it is determined whether the proportion of the target application interface identifier falling into the obscured area is greater than a preset first threshold.

[0080] If the proportion of the target application interface identifier falling into the obscured area is greater than the preset first threshold, then a target clamping position corresponding to the target application interface identifier is determined according to the position of the target application interface identifier, wherein the target clamping position is used to make the proportion of the target application interface identifier falling into the obscured area lower than the preset second threshold.

[0081] One of the key aspects of this method is determining the relationship between the obscured area and the location of the target application interface icon. Based on the aforementioned obscured area, it can be determined whether the location of the target application interface icon overlaps with the obscured area. If they overlap, and the proportion of the target application interface icon falling within the obscured area is greater than a preset first threshold, then it can be considered that the obscured area may cause the driver to spend more time interacting with the terminal device. It should be noted that the preset first threshold can be the optimal proportion obtained by the developers through experiments, or it can be set by the user. Optionally, the preset first threshold is 75%.

[0082] After determining that the proportion of the target application interface icon falling into the obscured area is greater than a preset first threshold, the position of the smartphone stand is adjusted according to the position of the target application interface icon so that the proportion of the target application interface icon falling into the obscured area is lower than a preset second threshold. The preset second threshold can also be the optimal proportion obtained by the developers through experiments, or it can be set by the user. Optionally, the preset second threshold is 25%.

[0083] In another possible implementation of the second aspect, the in-vehicle scene bracket control device based on screen occlusion events further includes:

[0084] The second determining unit is used to determine whether the user manually adjusts the smartphone holder;

[0085] The second acquisition unit is used to acquire the recording information of the first application interface after the user adjusts the smartphone holder;

[0086] The first training unit is used to train the first prediction model based on the recorded information of the application interface to obtain an updated first prediction model.

[0087] Specifically, due to limitations of the first prediction model obtained through machine learning, there may be errors in judging the target application interface identifier or its location. Therefore, when the driver manually adjusts the smartphone holder, it indicates that the above situation has occurred. Thus, after determining that the driver has manually adjusted the smartphone holder, the positions of one or more identifiers in the application interface of the terminal device, as well as the positions of the identifiers operated on in the application interface, are obtained. Furthermore, the positions of one or more identifiers in the application interface of the terminal device, as well as the positions of the identifiers operated on in the application interface, are used as training data to train the first prediction model to avoid similar situations from occurring.

[0088] In another possible implementation of the second aspect, the in-vehicle scene bracket control device based on screen occlusion events further includes:

[0089] The third determining unit is used to determine whether the user manually adjusts the smartphone holder;

[0090] The third acquisition unit is used to acquire the position of the target application interface identifier after the user adjusts the smartphone holder and the position of the smartphone holder clamped after the user manually adjusts it.

[0091] The second training unit is used to train the second prediction model based on the position of the target application interface identifier and the position of the smartphone holder clamp after manual adjustment by the user, so as to obtain the updated second prediction model.

[0092] Specifically, due to limitations of the second prediction model obtained through machine learning, there may be issues with the smartphone holder's position adjustment, or the smartphone holder's position may not have been adjusted when it should have been. Therefore, when the driver manually adjusts the smartphone holder, it indicates that the above situation has occurred. Thus, after confirming that the driver manually adjusted the smartphone holder, the location of the operation marker and the location of the smartphone holder after manual adjustment are obtained. Furthermore, the location of the operation marker and the location of the smartphone holder after manual adjustment are used as training data to retrain the second prediction model to avoid the above situation from recurring.

[0093] Thirdly, embodiments of this application provide a target vehicle, which includes a processor, a memory, and a communication interface; the memory stores a computer program; when the processor executes the computer program, the communication interface is used to send and / or receive data, and the target vehicle can perform the method described in the first aspect or any possible implementation of the first aspect.

[0094] It should be noted that the processor contained in the target vehicle described in the third aspect above can be a processor specifically designed to execute these methods (referred to as a dedicated processor for easy distinction), or a processor that executes these methods by calling a computer program, such as a general-purpose processor.

[0095] Optionally, the processor may be just the smart cockpit domain controller, or it may be other processors that include the smart cockpit domain controller.

[0096] Optionally, at least one processor may include both dedicated processors and general-purpose processors.

[0097] Optionally, the computer program described above can be stored in memory. For example, the memory can be a non-transitory memory, such as read-only memory (ROM), which can be integrated with the processor on the same device or disposed on different devices. This application does not limit the type of memory or the arrangement of the memory and the processor.

[0098] In one possible implementation, at least one of the aforementioned memory locations outside the aforementioned target vehicle.

[0099] In yet another possible implementation, at least one of the aforementioned memory is located within the aforementioned target vehicle.

[0100] In another possible implementation, a portion of the memory of the at least one memory is located inside the target vehicle, while another portion of the memory is located outside the target vehicle.

[0101] In this application, the processor and memory may also be integrated into a single device, that is, the processor and memory can be integrated together.

[0102] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program that, when executed on at least one processor, implements the method described in the first aspect or any of the optional solutions of the first aspect.

[0103] Fifthly, this application provides a computer program product comprising a computer program that, when run on at least one processor, implements the method described in the first aspect or any of the optional solutions of the first aspect.

[0104] Optionally, the computer program product can be a software installation package, which can be downloaded and executed on a computing device when the aforementioned method is required.

[0105] The beneficial effects of the technical solutions provided in the third to fifth aspects of this application can be referred to the beneficial effects of the technical solutions in the first and second aspects, and will not be repeated here. Attached Figure Description

[0106] The accompanying drawings used in the description of the embodiments will be briefly introduced below.

[0107] Figure 1 This is a schematic diagram of the architecture of a support control system provided in an embodiment of this application;

[0108] Figure 2This is a flowchart illustrating a bracket control method based on screen occlusion events in a vehicle-mounted scenario, as provided in an embodiment of this application.

[0109] Figure 3 This is a flowchart illustrating a method for determining a target application interface identifier according to an embodiment of this application;

[0110] Figure 4 This is a schematic diagram of a terminal device's screen being obscured by a smartphone stand.

[0111] Figure 5 This is a schematic diagram illustrating how to adjust the clamping position of a smartphone holder.

[0112] Figure 6 This is a diagram illustrating another method for adjusting the clamping position of a smartphone holder.

[0113] Figure 7 This is a schematic diagram of the structure of a bracket control device based on screen occlusion events in a vehicle-mounted scenario, provided in an embodiment of this application.

[0114] Figure 8 This is a schematic diagram of the structure of a target vehicle provided in an embodiment of this application;

[0115] Figure 9 This is a schematic diagram of the structure of a smartphone holder provided in an embodiment of this application.

[0116] Reference numerals: 101, target vehicle; 102, smartphone holder; 103, terminal device; 901, housing; 9011, receiving cavity; 902, moving part; 903, clamping arm; 9031, body; 9032, clamping structure. Detailed Implementation

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

[0118] The terms "first," "second," "third," and "fourth," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to such processes, methods, products, or apparatus.

[0119] The system architecture used in the embodiments of this application is described below. It should be noted that the system architecture and business scenarios described in this application are for the purpose of more clearly illustrating the technical solutions of this application, and do not constitute a limitation on the technical solutions provided in this application. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in this application are also applicable to similar technical problems.

[0120] Please see Figure 1 , Figure 1 This is a schematic diagram of the architecture of a bracket control system provided in an embodiment of this application. The bracket control system includes a target vehicle 101, which includes a smart cockpit domain controller. A smartphone bracket 102 is installed in the cockpit of the target vehicle, and the smartphone bracket 102 holds a terminal device 103. The smart cockpit domain controller is communicatively connected to the smartphone bracket 102 and the terminal device 103, wherein:

[0121] The target vehicle 101 can be a car, bicycle, electric vehicle, or other similar vehicle. The intelligent cockpit domain controller can determine the obscured area on the screen of the terminal device 103 using image acquisition devices such as cameras or industrial cameras built into the target vehicle 101, or by using driving mode synchronization messages sent by the terminal device 103 or pressure distribution information on the screen of the terminal device 103. The intelligent cockpit domain controller has a pre-trained first prediction model and a second prediction model. These models can be trained by the intelligent cockpit domain controller itself, or they can be trained by an external server, and after establishing a communication connection with the external server, the intelligent cockpit domain controller receives data from the server. The controller determines the location of the target application interface identifier of the current application interface through the first prediction model. The current application interface can be sent by the terminal device 103 or acquired by the smart cockpit domain controller itself through an image acquisition device or sensor. The smart cockpit domain controller can determine the target clamping position of the smartphone holder in the smartphone holder 102 through the second prediction model. After the smart cockpit domain controller obtains the target clamping position, it establishes a communication connection with the smartphone holder 102 and sends the target clamping position to the smartphone holder 102. The smartphone holder 102 adjusts the position or clamping method of the smartphone holder according to the target clamping position.

[0122] The smartphone holder 102 can be a phone holder, tablet holder, or other smartphone holder, and is generally placed on the side of the driver's seat.

[0123] Terminal device 103 can be a cellular phone, smartphone, laptop computer, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, navigator, slate PC, tablet PC, wearable device (e.g., smartwatch, smart glasses, head-mounted display (HMD), terminal device in the Internet of Things or the Internet of Vehicles, terminal device in 5G network, terminal device in future evolved public land mobile network (PLMN), and any form of terminal device in future networks, etc.

[0124] Please see Figure 2 , Figure 2 This is a flowchart illustrating a bracket control method based on screen occlusion events in a vehicle scenario, provided in an embodiment of this application. The method is applied to the smart cockpit domain controller of a target vehicle. A smartphone bracket is installed in the cockpit of the target vehicle, holding a terminal device. The smart cockpit domain controller is communicatively connected to the smartphone bracket and the terminal device. The method includes, but is not limited to, the following steps:

[0125] Step S201: Send a request message for clamping status information to the terminal device.

[0126] Before sending a request message for clamping status information to the terminal device, a driving mode function synchronization message is received from the terminal device.

[0127] The driving mode function synchronization message includes a user-set adaptive clamping position adjustment function. The adaptive clamping position adjustment function refers to adjusting the position of the smartphone holder clamping the terminal device to enable the user to smoothly operate the target display area of ​​the application interface currently displayed on the screen of the terminal device.

[0128] Specifically, before the target vehicle is started, the intelligent cockpit domain controller establishes a communication connection with the terminal device and reaches a consensus on whether to adjust the position of the smartphone holder holding the terminal device.

[0129] Upon detecting that the driving mode function synchronization message includes the clamping position adaptive adjustment function, a request message for clamping status information is sent to the terminal device.

[0130] In this embodiment, the clamping state information includes an application interface identifier, the position of the application interface identifier, the clamping position, and the correspondence between the application interface identifier and the clamping position. Simply put, the correspondence between the application interface identifier and the clamping position is the relative positional relationship between the position of the application interface identifier and the area of ​​the clamping position that covers the terminal device, causing the screen to be obscured.

[0131] In one optional implementation, the smart cockpit domain controller establishes a communication connection with the terminal device and receives pressure distribution information on the screen sent by the terminal device. Generally, the pressure on the area of ​​the screen held by the smartphone holder is greater than that on the unheld area. Therefore, the target vehicle can determine whether the target application interface icon falls into the holding position of the smartphone holder based on the pressure distribution information.

[0132] Step S202: If a positive response message is received from the terminal device, the clamping status information in the positive response message is extracted; based on the clamping status information, the target clamping position corresponding to the target application interface identifier in the application interface identifier is determined, and the smartphone holder is controlled to adjust the clamping position according to the target clamping position.

[0133] When communication is in good condition, the terminal device continuously sends positive response messages containing clamping status information to the intelligent cockpit domain control in order to quickly determine the target clamping position.

[0134] In this embodiment, in order to save power, the clamping position of the smartphone holder is adjusted only when the driver of the target vehicle pre-operates the terminal device.

[0135] The process of determining the target clamping position is as follows:

[0136] The intelligent cockpit domain controller can determine the target application interface identifier in the application interface identifier based on the application interface identifier in the clamping status information, thereby determining the position of the target application interface identifier.

[0137] Based on the relative positional relationship between the target application interface identifier and the clamping position, the target clamping position corresponding to the position of the target application interface identifier is obtained, thereby adjusting the clamping position of the smartphone holder.

[0138] In one optional implementation, determining the speed at which the driver of the target vehicle intends to operate the terminal device is crucial for a better user experience. In this implementation, the driver's posture is used to determine whether they intend to operate the terminal device. The driver's posture includes their gaze and arm movement. Possible methods include: gaze focus detection, where the driver is determined to be about to operate the terminal device when their gaze is directed towards the screen of the terminal device using a camera or infrared sensor; and a right arm movement area restriction method, where a target activity area for the driver's right arm is set, such as the width of the target vehicle's cabin from left to right by 1 meter. If the driver's right arm touches or exceeds the boundary of the target activity area, it is determined that the driver intends to operate the terminal device.

[0139] Step S203: If a negative response message is received from the terminal device, then when the user pre-operates on the terminal device, the application interface of the terminal device is obtained.

[0140] The application interface is the current application interface when the user pre-operates the terminal device, and the application interface includes one or more application interface identifiers.

[0141] The application interface is the current application interface when the user operates the terminal device; the application interface of the terminal device can be obtained through the in-vehicle equipment or devices in the target vehicle.

[0142] In one optional implementation, an image of the smartphone holder's location is acquired using a camera inside the target vehicle facing the smartphone holder. Since the terminal device's screen is on while the driver is driving, and the screen is exposed to significant light, especially at night, the intelligent cockpit domain controller, after acquiring the image of the smartphone holder, identifies the terminal device's screen display information within the image based on a pre-loaded image of the smartphone holder, thereby obtaining the terminal device's application interface. Optionally, various image processing toolkits can be used to process the image information during the intelligent cockpit domain controller's image analysis. The application interface of the terminal device can be determined using feature extraction algorithms, including SIFT, SURF, BRISK, FREAK, and MSER. It should be noted that various region segmentation methods, such as region merging, watershed segmentation, or region growing, are also applied when obtaining the application interface. The specific implementation method is not limited in this embodiment.

[0143] Step S204: Determine the location of the target application interface identifier based on the application interface.

[0144] Generally, an application interface contains one or more identifiers. If an application interface contains only one identifier, that identifier is the target application interface identifier. However, if an application interface contains multiple identifiers, it is necessary to determine at least one of the multiple identifiers as the target application interface identifier. In one optional implementation, the process of determining at least one of the multiple identifiers as the target application interface identifier is as follows: Figure 3 The above, Figure 3 The flowchart of a method for determining the identifier of a target application interface is shown below:

[0145] Step S11: Obtain operation log information of multiple application interfaces in the history of the terminal device.

[0146] One of the operation log information from the multiple application interfaces includes the application interface, an identifier within the application interface, the position of the identifier, the touched identifier corresponding to the operation log information, and the position of the touched identifier corresponding to the operation log information. It is understood that this single operation log information is generated based on a single screen touch by the user of the terminal device. The operation is the user touching an identifier on the application interface, causing the terminal device to execute a subsequent command linked to that identifier. The identifier is generally a virtual button in the application interface, such as the send or exit button in a WeChat chat interface. It is understood that the operation log information is sent by the terminal device to the intelligent cockpit domain controller.

[0147] Step S12: Based on the number of times the touched identifier appears in the operation log information of the multiple application interfaces, analyze and determine the target application interface identifier corresponding to each of the multiple application interfaces, and the position of the target application interface identifier on the application interface.

[0148] The identifier of the operation corresponding to any one of the multiple operation log information and its position in the application interface are marked, and the number of times each identifier is marked in each application interface is counted. After the count is completed, the data obtained is detected and analyzed. If the number of times a certain identifier is marked exceeds a preset threshold, the identifier is determined as the target application interface identifier in the application interface corresponding to the identifier, and the position of the identifier in the application interface is recorded.

[0149] In practical applications, there are many ways to obtain operation log information from the application interface. For example, one can set a global keyboard hook in the terminal device to capture and record key press messages; use the GetAsyncKeyState function, which can determine the key state and record whether the key press was performed; or use the original input model to directly obtain data from the input device to record key press information, among other methods.

[0150] It should be noted that there may be multiple target application interface identifiers in the application interface.

[0151] In another alternative implementation, at least one of the identifiers is determined to be a target application interface identifier, and the process of determining the location of the target application interface identifier is as follows:

[0152] The current application interface of the terminal device is obtained; after determining the position of the target application interface identifier in the historical application interfaces, the position of the target application interface identifier in the current application interface is determined according to the obtained current application interface. In an optional embodiment, the current application interface is input into a first prediction model to obtain the position of the target application interface identifier in the current application interface. The current application interface includes multiple identifiers. The first prediction model is trained based on the recorded information of multiple application interfaces in historical scenarios. The recorded information of each application interface includes the positions of multiple identifiers in the application interface and the position of the target application interface identifier in the application interface. The positions of the multiple identifiers in the application interface are feature data, and the position of the target application interface identifier in the application interface is label data. The target application interface identifier belongs to one or more of the multiple identifiers.

[0153] Taking the target application interface identifier as the exit button as an example, the WeChat chat interface is input into the first prediction model. The first prediction model will analyze the identifier set in the WeChat chat interface and the position of the identifier, then determine that the target application interface identifier in the identifier is the exit button, and finally output the position of the exit button in the WeChat chat interface.

[0154] The internal logic of the first prediction model is set according to the style, proportion, habits of page design, and the importance of the icons in the application interface. If the current application interface input to the first prediction model is an application interface that has not appeared in the training data, then the aforementioned exit button may be the target application interface icon in the current application interface. Most application interfaces have their exit buttons located in the corner of the screen, such as the exit button in the WeChat chat interface located in the upper left corner of the screen, and the exit button in the Safari browser located in the lower left corner of the screen. Therefore, the first prediction model will determine the icon located in the corner or the icon with the function of exit in the current application interface as the target application interface icon based on the position or function of the icon in the current application interface, and output the position of the target application interface icon.

[0155] It should be noted that, in this embodiment, the position of the target application interface identifier is a set of coordinates. For example, if the touchable area of ​​the target application interface identifier on the screen is a square, then after dividing the screen into 1000*1000 squares, the position of the target application interface identifier may be the area enclosed by {(100, 500)-(200, 500)}, {(100, 500)-(100, 600)}, {(100, 600)(200, 600)}, and {(200, 600)-(200, 500)}. If the touchable area of ​​the target application interface identifier on the screen is an irregular shape, then the position of the identifier may be the set of all coordinates of the irregular shape on the screen.

[0156] In this embodiment, the first prediction model is mainly used to obtain the location of the target application interface identifier. Therefore, the first prediction model can be a Markov Random Field (MRF) model or a Gibbs Random Field (GRF) model. Optionally, the first prediction model can also be a classification model that has been trained extensively. Since the common application scenario of this model is while the vehicle is in motion, and drivers generally do not perform complex operations on the terminal device while in motion, it is understood that the need to determine the target application interface identifier is relatively common. Therefore, the location of the target application interface identifier is also relatively common. Optionally, the first prediction model is a Rule-based Representation Learner (RRL).

[0157] Furthermore, to improve the accuracy and relevance of the model, after the current driver of the target vehicle enters the cabin, it is determined whether the current driver is a driver who has previously driven the target vehicle through a camera, sound sensor, or fingerprint authentication. If so, an appropriate model is retrieved based on the corresponding information in the database, and each driver of the target vehicle has an appropriate first prediction model; if not, a basic first prediction model is used.

[0158] Furthermore, in order to improve the accuracy of the model, a large amount of training data is obtained through vehicle network data to train and update the basic first prediction model or the first prediction model belonging to a certain driver.

[0159] Step S205: Based on the position of the target application interface identifier, generate a target clamping position corresponding to the target application interface identifier according to a preset algorithm, and control the smartphone holder to adjust the clamping position according to the target clamping position.

[0160] Before adjusting the position of the smartphone holder, it is necessary to first determine whether the driver's control over the target application interface icon will be affected by the smartphone holder. Therefore, it can be determined whether the driver's control over the target application interface icon will be affected by the smartphone holder by whether the target application interface icon falls into the obscured area, or by the proportion of the target application interface icon falling into the obscured area. The obscured area is the part of the terminal device's screen that is obscured by the smartphone holder.

[0161] In one optional embodiment, the obscured portion is the area of ​​the terminal device's screen that is obscured by the clamping structure of the smartphone holder. Optionally, the smartphone holder includes a clamping structure and a back plate. The clamping structure is connected to the back plate. It is understood that the back plate provides back support for the terminal device held by the smartphone holder, and the clamping structure provides lateral support for the terminal device held by the smartphone holder. The clamping structure is horizontally L-shaped. Therefore, in this embodiment, the clamping structure will come into contact with the screen of the terminal device due to its L-shaped structure. The area of ​​contact between the two is the obscured area mentioned above.

[0162] In one optional implementation, image information of the location of the smartphone holder is acquired by a camera inside the target vehicle facing the smartphone holder, thereby obtaining the aforementioned obscured area. It is understood that the smartphone holder and the screen of the terminal device will have a significant color difference. In this implementation, the screen of the terminal device is generally white or light-colored, while the smartphone holder is black or dark-colored, resulting in a noticeable color difference. Therefore, the smart cockpit domain controller can analyze and determine the obscured area of ​​the terminal device based on the pixel ratio and texture features in the image information.

[0163] In one optional implementation, based on the positions of the obscured area and the target application interface icon, it is determined whether the proportion of the target application interface icon falling into the obscured area is greater than a preset first threshold. In this process, the coordinate set of the obscured area and the coordinate set of the target application interface icon are compared. The part with the same coordinates is the part of the target application interface icon falling into the obscured area. Then, the proportion of the part with the same coordinates to the entire touch area of ​​the target application interface icon is determined. When the proportion is greater than the preset first threshold, it can be considered that the driver's control of the target application interface icon is affected by the smartphone holder. Conversely, when the proportion is less than the preset first threshold, it can be considered that the driver's control of the target application interface icon is not affected by the smartphone holder. Optionally, the preset first threshold is 75%. The preset first threshold can be the optimal proportion obtained by the developers through experiments, or it can be set by the driver.

[0164] Specifically Figure 4 Let's take an example to illustrate. Figure 4 This is a schematic diagram of a terminal device whose screen is obstructed by a smartphone stand; Figure 4 In this scenario, the screen of the terminal device displays a WeChat chat interface, where the voice switch button is identified as the target application interface. However, because the floating input method display is obscured by the left clamping structure of the smartphone holder, calculations show that the proportion of the voice switch button icon falling into the obscured area exceeds a preset first threshold. Consequently, the voice switch button icon cannot be used smoothly by the driver. If the driver attempts to force a click, it will cause a brief moment of distraction, which greatly increases the safety risk.

[0165] Furthermore, if the proportion of the target application interface icon falling into the obscured area is greater than the preset first threshold, the position of the smartphone stand is adjusted according to the position of the target application interface icon so that the proportion of the target application interface icon falling into the obscured area is lower than the preset second threshold.

[0166] Since the purpose of adjusting the smartphone holder is to prevent the driver's control over the target application interface icon from being affected by the smartphone holder, it can be considered that the driver's control over the target application interface icon is not affected by the smartphone holder when the proportion of the target application interface icon falling into the obscured area is less than a preset second threshold. However, it should be noted that the application interface may contain one or more target application interface icons. Therefore, how to adjust the position of the smartphone holder so that none of the one or more target application interface icons are affected by the smartphone holder is as follows:

[0167] The location of the target application interface identifier is input into the second prediction model to obtain the target clamping position of the smartphone holder corresponding to the location of the target application interface identifier. The second prediction model is trained based on the location of the target application interface identifier and the adjustment area of ​​the smartphone holder corresponding to the location of the target application interface identifier. The location of the target application interface identifier is feature data, and the adjustment area is label data.

[0168] Adjust the position of the smartphone holder when the current application interface is displayed on the terminal device, based on the target clamping position.

[0169] The training data for the second prediction model mentioned above includes the following types:

[0170] Scenario 1: There is only one target application interface identifier in the application interface. Therefore, the adjustment area of ​​the smartphone stand corresponding to the position of the target application interface identifier may be higher or lower than the current position of the smartphone stand. After such adjustment, the proportion of the target application interface identifier falling into the obscured area will be lower than the preset second threshold. In this case, the smartphone stand may partially overlap with the area where the target application interface identifier is located, or it may not overlap.

[0171] It should be noted that the preset second threshold is generally used when there are multiple target interface icons in the application interface. When there is only one target application interface icon in the application interface, the position output by the second prediction model is the boundary position of the target application interface icon, and the target application interface icon will not be obscured by the smartphone stand after the smartphone stand is adjusted.

[0172] Scenario 2: The application interface contains multiple target application interface icons, and the positions of the multiple target application interface icons are not spread around the screen of the terminal device. Therefore, the adjustment area of ​​the smartphone stand corresponding to the positions of the multiple target application interface icons may be in various positions. However, no matter where the adjustment area is located, the proportion of the multiple target application interface icons falling into the obscured area is lower than the preset second threshold.

[0173] In scenario two, the position output by the second prediction model is preferentially the boundary position of one of the multiple target application interface identifiers, and none of the multiple target application interface identifiers will be obscured by the smartphone holder after the smartphone holder is adjusted.

[0174] Furthermore, in actual testing, there are situations where the distance between the multiple target application interface icons is relatively close. In this case, the position output by the second prediction model is preferentially the boundary position of one of the multiple target application interface icons. However, if the boundary position of one of the multiple target application interface icons is already close to the screen edge of the terminal device, and the smartphone stand cannot fully reach that boundary position, the second prediction model will consider the boundary positions of other target application interface icons with a second priority. If there are many multiple target application interface icons and they are close together, making it impossible to adjust the smartphone stand to the corresponding boundary position, the target clamping position output by the second prediction model is preferentially the area furthest apart among the adjacent target application interface icons, and after the smartphone stand is adjusted, the occluded area of ​​the aforementioned adjacent target application interface icons does not exceed a preset second threshold.

[0175] Scenario 3: The application interface contains multiple target application interface icons, and these multiple target application interface icons are distributed around the screen of the terminal device. Therefore, there is no suitable adjustment area for the smartphone stand that corresponds to the position of the multiple target application interface icons. In actual application, Scenario 3 is very rare. If there is no suitable target clamping position, the smartphone stand will not be adjusted.

[0176] The adjustment method of the smartphone stand is determined based on the target clamping position. In one optional embodiment, in addition to adjusting the position of the smartphone stand according to the target clamping position, the clamping area can also be reduced or the clamping direction adjusted according to the position of the target application interface icon. For example, when there are multiple target application interface icons located on the left and right sides of the screen in the current application interface, causing the position of the smartphone stand to inevitably overlap with the target application interface icon, and the overlap ratio is large, the size of the smartphone stand can be reduced to decrease the overlap ratio.

[0177] Models derived from machine learning are generally limited by the training data and may produce incorrect results. In this embodiment, if the driver manually adjusts the smartphone holder after it has been adjusted, it indicates that a problem has occurred in one or more stages of the process. Therefore, in implementations that utilize models, a self-updating mode needs to be set to prevent the driver from manually adjusting the smartphone holder again. For example, the following two cases illustrate this.

[0178] Case 1: In the implementation of the first prediction model described above, the self-updating mode first determines that the driver manually adjusts the smartphone holder; then, it obtains the position of one or more icons in the application interface of the terminal device after the driver adjusts the smartphone holder, as well as the position of the icon operated on the application interface, and retrains the first prediction model based on the position of one or more icons in the application interface of the terminal device and the position of the icon operated on the application interface.

[0179] Case 2: In the implementation of the second prediction model described above, the self-updating mode first determines that the driver manually adjusts the smartphone holder; secondly, it obtains the position of the operation identifier and the position of the smartphone holder after the driver adjusts the smartphone holder; and then retrains the second prediction model based on the position of the operation identifier and the position of the smartphone holder after the manual adjustment.

[0180] It should be noted that the above training process can occur in the target vehicle, or the target vehicle or the intelligent cockpit domain controller in the target vehicle can establish a communication connection with the server, and the target vehicle or the intelligent cockpit domain controller in the target vehicle can send the above training data to the server. The server can then retrain the model based on the training data. After the training update is completed, the target vehicle or the intelligent cockpit domain controller in the target vehicle can receive the updated model sent by the server to replace the original model.

[0181] It should also be noted that the aforementioned smartphone holder may be included with the target vehicle during production, or it may be produced separately and installed in the target vehicle. Furthermore, the smartphone holder may be a modification of a commonly used smartphone holder, or it may be assembled according to the requirements involved in the above-mentioned process. Its structure may differ from that of a common smartphone holder, but it can still achieve the purpose of supporting and stabilizing the terminal device.

[0182] Finally, the smart cockpit domain controller sends the target clamping position to the smartphone holder, so that the smartphone holder adjusts its clamping position according to the target clamping position.

[0183] The process of adjusting the clamping position. Figure 4 , Figure 5 and Figure 6 To explain, Figure 5 This is a schematic diagram illustrating how to adjust the clamping position of a smartphone holder. Figure 6 This is a diagram illustrating another way to adjust the clamping position of a smartphone holder.

[0184] Depend on Figure 4 It is known that the target application interface identifier is a voice switch button identifier. After determining that the voice switch button identifier falls into the obscured area exceeding the first threshold, it is calculated that the clamping structure of the downward-moving smartphone stand neither obscures the WeChat chat content nor obscures the portion of the voice switch button identifier that is less than the second threshold. Therefore, the target clamping position corresponding to the target application interface identifier is... Figure 4 The specific target clamping position is visible below the clamping structure shown. Figure 5 As shown, in Figure 5 In the diagram, the solid line represents the clamping structure at the target clamping position.

[0185] Furthermore, in the WeChat chat interface, the target application interface is identified as both a voice switch button and a send button, and the process of adjusting the clamping position is as follows: Figure 6 To explain, in Figure 6 In this case, because the area of ​​the voice switch button icon in the target application interface that is obscured by the smartphone holder exceeds the first threshold, but if the target clamping position were below, it would obscure the send button icon in the target application interface, therefore, the generated target clamping position is above the current clamping position, specifically... Figure 6 The clamping structure is represented by a solid line. It should also be noted that the style and shape of the clamping structure are not specifically limited in this embodiment.

[0186] In one alternative implementation, the smartphone holder can not only adjust the clamping position, but also adjust the clamping method, such as reducing the clamping area or adjusting the clamping direction.

[0187] Specifically, in this embodiment, in order to better avoid the impact of the smartphone holder on the target application interface logo, certain adjustments are made to the structure of the smartphone holder. For example, ball bearings are provided at the part where the smartphone holder connects to the smartphone holder so that the smartphone holder can move freely up and down. Alternatively, retractable baffles are provided at the upper and lower ends of the smartphone holder so that when the area on the screen blocked by the smartphone holder affects the driver's operation of the terminal device, the position of the smartphone holder can be adjusted more flexibly and in a more targeted manner, or the clamping method of the smartphone holder can be adjusted.

[0188] In this embodiment, the target vehicle receives information data sent by the terminal device or obtains the required information data through the in-vehicle device. It analyzes the screen occlusion of the terminal device by the smartphone holder using one or more models to determine how to adjust the smartphone holder when occlusion affects the driver's operation of the terminal device. The method is simple and clear. Furthermore, compared to a single, mechanical holder adjustment method, this significantly improves the smoothness of the vehicle's intelligent cockpit domain controller in scenarios where the screen is obstructed by the in-vehicle holder. This further enhances the targeting and comprehensiveness of the intelligent cockpit domain controller, and ensures that the obstructed area of ​​the terminal does not affect the driver's operation of the terminal in in-vehicle scenarios.

[0189] The methods of the embodiments of this application have been described in detail above, and the apparatus of the embodiments of this application is provided below.

[0190] Please see Figure 7 , Figure 7 This is a schematic diagram of a bracket control device based on screen occlusion events in a vehicle scenario provided in an embodiment of this application. The bracket control device 70 based on screen occlusion events in a vehicle scenario can be a device in the target vehicle mentioned above. The bracket control device 70 based on screen occlusion events in a vehicle scenario can include a sending unit 701, a positive response unit 702, a first acquisition unit 703, a first determination unit 707, and a generation unit 705. The detailed description of each unit is as follows.

[0191] The sending unit 701 is used to send a request message for clamping status information to the terminal device. The clamping status information includes the position of the application interface identifier and the correspondence between the application interface identifier and the clamping position.

[0192] The affirmative response unit 702 is used to extract the clamping status information from the affirmative response message if it receives an affirmative response message from the terminal device; to determine the target clamping position corresponding to the target application interface identifier in the application interface identifier according to the clamping status information; and to control the smartphone bracket to adjust the clamping position according to the target clamping position.

[0193] The first acquisition unit 703 is configured to acquire the application interface of the terminal device when a negative response message is received from the terminal device and the user is detected to have pre-operated the terminal device, if the application interface is the current application interface when the user pre-operates the terminal device, and the application interface includes one or more application interface identifiers.

[0194] The first determining unit 707 is used to determine the position of the target application interface identifier based on the application interface.

[0195] The generation unit 705 is used to generate a target clamping position corresponding to the target application interface identifier according to the position of the target application interface identifier and according to a preset algorithm, and to control the smartphone holder to adjust the clamping position according to the target clamping position.

[0196] In one possible implementation, regarding determining the location of the target application interface identifier based on the application interface, the first determining unit 707 is specifically used for:

[0197] The application interface is input into the first prediction model to obtain the position of the target application interface identifier in the application interface. The first prediction model is trained based on the recorded information of multiple application interfaces in historical scenarios. The recorded information of each application interface includes the position of all identifiers in the application interface and the position of the target application interface identifier corresponding to the recorded information. The position of all identifiers in the application interface is feature data, and the position of the target application interface identifier corresponding to the recorded information is label data. The target application interface identifier is one or more identifiers in the application interface.

[0198] In one possible implementation, regarding determining the location of the target application interface identifier based on the application interface, the first determining unit 707 is specifically used for:

[0199] Obtain operation log information of multiple application interfaces in the history of the terminal device. One of the operation log information of the multiple application interfaces includes the application interface, the identifier in the application interface, the position of the identifier, the touched identifier corresponding to the operation log information, and the position of the touched identifier corresponding to the operation log information.

[0200] Based on the number of times the touched identifier appears in the operation log information of the multiple application interfaces, the target application interface identifier corresponding to each of the multiple application interfaces is analyzed and determined, as well as the position of the target application interface identifier on the application interface.

[0201] In one possible implementation, the generation unit 705 is specifically used for generating a target clamping position corresponding to the target application interface identifier according to a preset algorithm, based on the target application interface identifier:

[0202] The image acquisition device acquires the obscured area of ​​the screen of the terminal device, wherein the obscured area is the area of ​​the screen of the terminal device that is obscured by the smartphone stand.

[0203] Based on the positions of the obscured area and the target application interface identifier, it is determined whether the proportion of the target application interface identifier falling into the obscured area is greater than a preset first threshold.

[0204] If the proportion of the target application interface identifier falling into the obscured area is greater than the preset first threshold, then a target clamping position corresponding to the target application interface identifier is determined according to the position of the target application interface identifier, wherein the target clamping position is used to make the proportion of the target application interface identifier falling into the obscured area lower than the preset second threshold.

[0205] In one possible implementation, the in-vehicle scene bracket control device 70 based on screen occlusion events further includes:

[0206] The second determining unit is used to determine whether the user manually adjusts the smartphone holder;

[0207] The second acquisition unit is used to acquire the recording information of the first application interface after the user adjusts the smartphone holder;

[0208] The first training unit is used to train the first prediction model based on the recorded information of the application interface to obtain an updated first prediction model.

[0209] In one possible implementation, the in-vehicle scene bracket control device 70 based on screen occlusion events further includes:

[0210] The third determining unit is used to determine whether the user manually adjusts the smartphone holder;

[0211] The third acquisition unit is used to acquire the position of the target application interface identifier after the user adjusts the smartphone holder and the position of the smartphone holder clamped after the user manually adjusts it.

[0212] The second training unit is used to train the second prediction model based on the position of the target application interface identifier and the position of the smartphone holder clamp after manual adjustment by the user, so as to obtain the updated second prediction model.

[0213] Please see Figure 8 , Figure 8 This is a schematic diagram of the structure of a target vehicle 80 provided in an embodiment of this application. The target vehicle 80 includes a processor 801, a communication interface 802, and a memory 803. The processor 801, communication interface 802, and memory 803 can be connected via a bus or other means; this embodiment takes a bus connection as an example.

[0214] The processor 801 is the computing and control core of the target vehicle 80. It can parse various instructions and data within the target vehicle 80. For example, the processor 801 can be the aforementioned intelligent cockpit domain controller, or it can be a central processing unit (CPU) that can transmit various interactive data between internal structures of the target vehicle 80. The communication interface 802 can optionally include standard wired interfaces and wireless interfaces (such as Wi-Fi, mobile communication interfaces, etc.), and can be used to send and receive data under the control of the processor 801. The communication interface 802 can also be used for the transmission and interaction of internal signaling or instructions within the target vehicle 80. The memory 803 is a memory device in the target vehicle 80 used to store programs and data. It is understood that the memory 803 here can include the built-in memory of the target vehicle 80, or it can include extended memory supported by the target vehicle 80. The memory 803 provides storage space for storing the operating system of the target vehicle 80. The storage space also stores program code or instructions required by the processor to perform corresponding operations. Optionally, the storage space may also store relevant data generated by the processor after performing the corresponding operation.

[0215] In this embodiment, the processor 801 runs executable program code in the memory 803 to perform the following operations:

[0216] Receive a driving mode function synchronization message from the terminal device. The driving mode function synchronization message includes a user-set clamping position adaptive adjustment function. The clamping position adaptive adjustment function refers to adjusting the position of the smartphone holder clamping the terminal device to enable the user to smoothly operate the target display area of ​​the application interface currently displayed on the screen of the terminal device.

[0217] Send a request message for clamping status information to the terminal device. The clamping status information includes the position of the application interface identifier and the correspondence between the application interface identifier and the clamping position.

[0218] If a positive response message is received from the terminal device, the clamping status information in the positive response message is extracted; based on the clamping status information, the target clamping position corresponding to the target application interface identifier in the application interface identifier is determined, and the smartphone holder is controlled to adjust the clamping position according to the target clamping position;

[0219] If a negative response message is received from the terminal device, then when the user pre-operates on the terminal device, the application interface of the terminal device is obtained, wherein the application interface is the current application interface when the user pre-operates on the terminal device, and the application interface includes one or more application interface identifiers.

[0220] Based on the application interface, determine the location of the target application interface identifier;

[0221] Based on the location of the target application interface identifier, a target clamping position corresponding to the target application interface identifier is generated according to a preset algorithm, and the smartphone holder is controlled to adjust the clamping position according to the target clamping position.

[0222] In one alternative embodiment, regarding determining the location of the target application interface identifier based on the application interface, the processor 801 is specifically configured to:

[0223] The application interface is input into the first prediction model to obtain the position of the target application interface identifier in the application interface. The first prediction model is trained based on the recorded information of multiple application interfaces in historical scenarios. The recorded information of each application interface includes the position of all identifiers in the application interface and the position of the target application interface identifier corresponding to the recorded information. The position of all identifiers in the application interface is feature data, and the position of the target application interface identifier corresponding to the recorded information is label data. The target application interface identifier is one or more identifiers in the application interface.

[0224] In one alternative embodiment, the processor 801 is specifically configured to: generate a target clamping position corresponding to the target application interface identifier according to a preset algorithm based on the target application interface identifier;

[0225] The image acquisition device acquires the obscured area of ​​the screen of the terminal device, wherein the obscured area is the area of ​​the screen of the terminal device that is obscured by the smartphone stand.

[0226] Based on the positions of the obscured area and the target application interface identifier, it is determined whether the proportion of the target application interface identifier falling into the obscured area is greater than a preset first threshold.

[0227] If the proportion of the target application interface identifier falling into the obscured area is greater than the preset first threshold, then a target clamping position corresponding to the target application interface identifier is determined according to the position of the target application interface identifier, wherein the target clamping position is used to make the proportion of the target application interface identifier falling into the obscured area lower than the preset second threshold.

[0228] In one alternative embodiment, regarding the determination of the target clamping position corresponding to the target application interface identifier based on the position of the target application interface identifier if the proportion of the target application interface identifier falling into the occluded area is greater than the preset first threshold, the processor 801 is specifically configured to:

[0229] If the proportion of the target application interface identifier falling into the occluded area is greater than the preset first threshold, then the position of the target application interface identifier is input into the second prediction model to obtain the target clamping position of the smartphone holder corresponding to the position of the target application interface identifier. The second prediction model is trained based on the position of the target application interface identifier and the clamping position of the smartphone holder corresponding to the position of the target application interface identifier. The position of the target application interface identifier is feature data, and the clamping position is label data.

[0230] In one alternative embodiment, the processor 801 is further configured to:

[0231] It is determined that the user manually adjusts the smartphone holder;

[0232] Obtain the recorded information of the first application interface after the user adjusts the smartphone holder;

[0233] The first prediction model is trained based on the recorded information from the application interface to obtain an updated first prediction model.

[0234] In one alternative embodiment, the processor 801 is further configured to:

[0235] It is determined that the user manually adjusts the smartphone holder;

[0236] The position of the target application interface icon after the user adjusts the smartphone holder and the position of the smartphone holder clamped after the user manually adjusts it are obtained.

[0237] The second prediction model is trained based on the location of the target application interface identifier and the position of the smartphone holder clamp after manual adjustment by the user, so as to obtain an updated second prediction model.

[0238] It should be noted that the implementation of each operation can also be referenced accordingly. Figure 2 and Figure 3 The corresponding description of the method embodiments shown.

[0239] The target vehicle mentioned above can be a vehicle or a device or equipment inside a vehicle, which can achieve the same process and purpose as described above.

[0240] This application provides a computer-readable storage medium storing a computer program, the computer program including program instructions, which, when executed by a processor, causes the processor to perform the operations described in the above embodiments.

[0241] This application also provides a computer program product that, when run on a processor, implements the operations described in the above embodiments.

[0242] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a program instructing related hardware. This program can be stored in a computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. The aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0243] Please see Figure 9 , Figure 9 This is a schematic diagram of the structure of a smartphone holder provided in an embodiment of this application. The smartphone holder includes a housing 901 with a receiving cavity 9011, a movable member 902 located on the housing and movable up and down relative to the housing, and two clamping arms 903.

[0244] The movable component 902 is used to support the bottom of the terminal device held by the smartphone holder, and the clamping arm 903 is used to clamp the two sides of the terminal device held by the smartphone holder.

[0245] Two clamping arms 903 are located on opposite sides of the housing 901 and are symmetrically arranged. However, it should be noted that the clamping arms 903 are symmetrical when not clamping the terminal device.

[0246] The movable component 902 includes a support portion exposed outside the housing 901.

[0247] The clamping arm 903 includes a body 9031, which is movably connected and fixed to the housing via a servo motor; the body includes a first end and a second end located on both sides of the servo motor.

[0248] The first end is located inside the housing 901, and correspondingly, the servo motor is also located inside the housing 901. The first end is fixedly connected to the joint on the servo motor by a threaded structure. The second end of the body 9031 includes a clamping structure 9032. The clamping structure 9032 includes two fixing plates. The clamping structure 9032 is connected to the second end by a spring structure to ensure that the clamping structure 9032 can be stretched so that the clamped terminal device can be properly placed on the smartphone holder.

[0249] Furthermore, there are two servo motors inside the housing 901, located on both sides of the housing 901, and each is adapted to the corresponding clamping arms 903 on both sides.

[0250] Furthermore, the servo motor is connected to a microcontroller located within the housing 901 cavity 9011.

[0251] The spring constant of the spring structure is between 1.94*10⁵ N / m and 3.94*10⁵ N / m.

[0252] The clamping structures 9032 on the clamping arm 903 are all covered with a cloth material with a high damping coefficient, which is used to increase the clamping stability and avoid scratching the clamped terminal device when the clamping arm 903 clamps the terminal device.

[0253] The control method of the smartphone holder: After receiving the target clamping position from the target vehicle, the microcontroller sends the corresponding movement distance to the servo motor, and the servo motor controls the clamping arm 903 to move up and down according to the movement distance.

[0254] During the adjustment of the clamping arm 903, the two clamping arms 903 are adjusted sequentially. While one clamping arm 903 is being adjusted, the other clamping arm 903 remains stationary to stabilize the state of the terminal device. After one clamping arm 903 is adjusted, the other clamping arm 903 is then adjusted. The fabric material of the clamping structure 9032 is used to ensure that the other clamping arm 903 can stabilize the state of the clamped terminal device while one clamping arm 903 is being adjusted.

[0255] It should be noted that the structure of the smartphone holder provided in this embodiment is merely a simple and exemplary indication of its service to the above-mentioned purposes. Figure 2 and Figure 3 The structure of the smartphone holder shown in the method is not limited in practical applications. The smartphone holder only needs to ensure millimeter-level precise movement of the clamping arm while maintaining a stable state of the clamped terminal device during clamping position adjustments.

Claims

1. A method for controlling a support of a vehicle-mounted scene based on a screen blocking event, the method comprising: receiving a screen blocking event from a screen blocking sensor; determining a type of the screen blocking event; and controlling the support based on the type of the screen blocking event. The method is applied to an intelligent cockpit domain controller of a target vehicle, a smartphone support is arranged in a cockpit of the target vehicle, a terminal device is clamped by the smartphone support, the intelligent cockpit domain controller is in communication connection with the smartphone support and the terminal device, and the method comprises the following steps: sending a request message for clamping state information to the terminal device, the clamping state information comprising a position of an application interface identifier and a corresponding relationship between the application interface identifier and a clamping position; if a positive response message from the terminal device is received, extracting the clamping state information in the positive response message; according to the clamping state information, obtaining a target clamping position corresponding to a target application interface identifier in the application interface identifier, and controlling the smartphone support to adjust the clamping position according to the target clamping position; if a negative response message from the terminal device is received, when a user pre-operates the terminal device is detected, obtaining an application interface of the terminal device, wherein the application interface is a current application interface when the user pre-operates the terminal device, and the application interface comprises one or more application interface identifiers; determining the position of a target application interface identifier according to the application interface; generating a target clamping position corresponding to the target application interface identifier according to the position of the target application interface identifier according to a preset algorithm, and controlling the smartphone support to adjust the clamping position according to the target clamping position.

2. The method of claim 1, wherein, The method comprises the following steps: inputting the application interface into a first prediction model to obtain the position of the target application interface identifier in the application interface, wherein the first prediction model is trained according to record information of multiple application interfaces in a historical scenario, the record information of each application interface comprises the positions of all identifiers in the application interface and the position of a target application interface identifier corresponding to the record information, the positions of all identifiers in the application interface are feature data, the position of the target application interface identifier corresponding to the record information is label data, and the target application interface identifier is one or more identifiers in the application interface.

3. The method of claim 1, wherein, The method comprises the following steps: obtaining an occluded area of a screen of the terminal device according to an image acquisition device, wherein the occluded area is an area of the screen of the terminal device occluded by the smartphone support; determining whether a proportion of the target application interface identifier falling into the occluded area is greater than a preset first threshold value according to a corresponding relationship between the occluded area and the position of the target application interface identifier; if the proportion of the target application interface identifier falling into the occluded area is greater than the preset first threshold value, determining a target clamping position corresponding to the target application interface identifier according to the position of the target application interface identifier, wherein the target clamping position is used to make the proportion of the target application interface identifier falling into the occluded area lower than a preset second threshold value.

4. The method of claim 3, wherein, If the proportion of the target application interface identifier falling into the occluded area is greater than the preset first threshold, the target clamping position corresponding to the target application interface identifier is determined according to the position of the target application interface identifier, and the method comprises the following steps: If the proportion of the target application interface identifier falling into the occluded area is greater than the preset first threshold, the position of the target application interface identifier is input into a second prediction model to obtain the target clamping position of the smartphone support corresponding to the position of the target application interface identifier, wherein the second prediction model is obtained by training according to the position of the target application interface identifier and the clamping position of the smartphone support corresponding to the position of the target application interface identifier, the position of the target application interface identifier is feature data, and the clamping position is label data.

5. The method of claim 2, wherein, After the smartphone support is controlled to adjust the clamping position according to the target clamping position, the method further comprises the following steps: It is determined that the user manually adjusts the smartphone support; Record information of a first application interface after the user adjusts the smartphone support is obtained; The first prediction model is trained according to the record information of the application interface to obtain an updated first prediction model.

6. The method of claim 4, wherein, After the smartphone support is controlled to adjust the clamping position according to the target clamping position, the method further comprises the following steps: It is determined that the user manually adjusts the smartphone support; The position of the target application interface identifier and the position of the smartphone support clamped by the user after manual adjustment are obtained after the user adjusts the smartphone support; The second prediction model is trained according to the position of the target application interface identifier and the position of the smartphone support clamped by the user after manual adjustment to obtain an updated second prediction model.

7. The method according to any one of claims 1 to 6, characterized in that, The adjustment mode of the smartphone support is determined according to the target clamping position, and comprises one or more of changing the height of the clamping position, reducing the clamping area, or adjusting the clamping direction.

8. An in-vehicle scene based on a screen blocking event support device, characterized by, The device comprises: A sending unit configured to send a request message for clamping state information to a terminal device, wherein the clamping state information comprises the position of an application interface identifier and the corresponding relationship between the application interface identifier and a clamping position; A positive response unit configured to, if a positive response message is received from the terminal device, extract the clamping state information in the positive response message, determine a target clamping position corresponding to a target application interface identifier in the application interface identifier according to the clamping state information, and control a smartphone support to adjust the clamping position according to the target clamping position; A first obtaining unit configured to, if a negative response message is received from the terminal device, obtain an application interface of the terminal device when a user pre-operates the terminal device, wherein the application interface is a current application interface when the user pre-operates the terminal device, and the application interface comprises one or more application interface identifiers; A first determining unit configured to determine the position of a target application interface identifier according to the application interface; A positive response unit configured to, if a positive response message is received from the terminal device, extract the clamping state information in the positive response message, determine a target clamping position corresponding to a target application interface identifier in the application interface identifier according to the clamping state information, and control a smartphone support to adjust the clamping position according to the target clamping position; The generating unit is configured to generate a target clamping position corresponding to the target application interface identifier according to a preset algorithm based on the position identified by the target application interface identifier, and control the smart phone support to adjust the clamping position according to the target clamping position.

9. A target vehicle characterized by The target vehicle comprises at least one processor, a communication interface and a memory, the communication interface is configured to send and / or receive data, the memory is configured to store a computer program, and the at least one processor is configured to call the computer program stored in the at least one memory to implement the method according to any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The computer readable storage medium stores a computer program, and when the computer program runs on the processor, the method according to any one of claims 1-7 is implemented.

Images