Scene pushing method and device, vehicle, and storage medium

Abstract

The application discloses a scene pushing method and device, a vehicle and a storage medium, and relates to the technical field of vehicles. The method comprises the following steps: acquiring a scene correlation parameter of the current time of the vehicle; if the scene correlation parameter meets the pushing condition of a target pushing scene, and the current punishment parameter of the target pushing scene is smaller than a set parameter threshold, the target pushing scene is pushed, and the target pushing scene comprises at least one vehicle-mounted function; and in response to a refusal instruction for the pushed target pushing scene, the current punishment parameter of the target pushing scene is increased according to a set parameter adjustment strategy. That is to say, when a user refuses a target pushing scene, the real demand of the user for the scene can be fed back by adjusting the punishment parameter of the target pushing scene, so that the problem of frequent interference on the user caused by excessive pushing can be avoided, and thus the scene pushing can be more adapted to the actual demand and preference of the user.

Description

Technical Field

[0001] This application relates to the field of vehicle technology, and in particular to a scene push method, device, vehicle and storage medium. Background Technology

[0002] In the field of scene push notifications for in-vehicle infotainment systems, when a user rejects a certain scene push notification from the system, they can often only restrict the push within a single power cycle. However, in the next power cycle, the system will push the scene again, causing frequent interference to the user and arousing their resentment. Summary of the Invention

[0003] This application proposes a scene push method, device, vehicle, and storage medium to avoid frequent interference to users caused by excessive scene pushes.

[0004] In a first aspect, embodiments of this application provide a scene push method, the method comprising: obtaining scene association parameters of the vehicle at the current moment; if the scene association parameters satisfy the push conditions of a target push scene, and the current penalty parameter of the target push scene is less than a set parameter threshold, then pushing the target push scene, wherein the target push scene includes at least one in-vehicle function; and in response to a rejection instruction for the pushed target push scene, increasing the current penalty parameter of the target push scene according to a set parameter adjustment strategy.

[0005] Secondly, embodiments of this application provide a scene push device, the device comprising: an association parameter acquisition module, a scene push module, and a penalty parameter adjustment module. The association parameter acquisition module is used to acquire scene association parameters of the vehicle at the current moment; the scene push module is used to push the target push scene if the scene association parameters meet the push conditions of the target push scene and the current penalty parameter of the target push scene is less than a set parameter threshold, wherein the target push scene includes at least one in-vehicle function; the penalty parameter adjustment module is used to increase the current penalty parameter of the target push scene according to a set parameter adjustment strategy in response to a rejection command for the pushed target push scene.

[0006] Thirdly, embodiments of this application provide a vehicle, including: one or more processors; a memory; one or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, and the one or more programs are configured to perform the methods described above.

[0007] Fourthly, embodiments of this application provide a computer-readable storage medium storing program code that can be invoked by a processor to execute the methods described above.

[0008] The solution provided in this application obtains the scene association parameters of the vehicle at the current moment; if the scene association parameters meet the push conditions of the target push scene, and the current penalty parameter of the target push scene is less than a set parameter threshold, then the target push scene is pushed, and the target push scene includes at least one in-vehicle function; in response to a rejection command for the pushed target push scene, the current penalty parameter of the target push scene is increased according to a set parameter adjustment strategy. In other words, when a user rejects a target push scene, the penalty parameter of the target push scene is adjusted to reflect the user's actual need for the scene, thereby avoiding frequent interference to the user due to excessive pushing, and making scene push more adaptable to the user's actual needs and preferences. Attached Figure Description

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

[0010] Figure 1 A flowchart illustrating a scene push method provided in an embodiment of this application is shown.

[0011] Figure 2 A flowchart illustrating a scene push method provided in another embodiment of this application is shown.

[0012] Figure 3 A schematic diagram of a parameter adjustment strategy provided in an embodiment of this application is shown.

[0013] Figure 4 A flowchart illustrating a scene push method provided in another embodiment of this application is shown.

[0014] Figure 5 A flowchart illustrating a scene push method provided in another embodiment of this application is shown.

[0015] Figure 6 This is a block diagram of a scene push device according to an embodiment of this application.

[0016] Figure 7 This is a block diagram of a vehicle used to execute the scene push method according to the embodiments of this application.

[0017] Figure 8 This is a storage unit in this application embodiment for storing or carrying program code that implements the scene push method according to this application embodiment. Detailed Implementation

[0018] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are merely some embodiments of the present application, and not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present application without creative effort are within the scope of protection of the present application.

[0019] It should be noted that some processes described in the specification, claims, and accompanying drawings of this application include multiple operations that appear in a specific order. These operations may not be performed in the order they appear herein, or they may be performed in parallel. Operation numbers such as S110, S120, etc., are merely used to distinguish different operations and do not represent any execution order. Furthermore, these processes may include more or fewer operations, and these operations may be performed sequentially or in parallel. Also, the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having”, and any variations thereof, are intended to cover non-exclusive inclusion, such that a process, method, system, product, or server that includes a series of steps or sub-modules is not necessarily limited to those steps or sub-modules that are explicitly listed, but may include other steps or sub-modules that are not explicitly listed or that are inherent to such process, method, product, or device.

[0020] The inventors have proposed a scene push method, device, vehicle, and storage medium. The scene push method provided in the embodiments of this application will be described in detail below.

[0021] Please refer to Figure 1 , Figure 1 This is a flowchart illustrating a scene push method provided in an embodiment of this application. The following will be combined with... Figure 1 The scenario push method provided in the embodiments of this application will be described in detail. The scenario push method may include the following steps:

[0022] Step S110: Obtain the scene-related parameters of the vehicle at the current moment.

[0023] In this embodiment, the scene association parameters may include at least one of the following: road information, weather information, in-vehicle passenger distribution information, passenger status information, time information, vehicle information, driving behavior information, and vehicle location information. Of course, more information may be included, and this embodiment does not limit this. Road information may include highways, urban roads, or rural roads, as well as regular roads, potholes, or speed bumps, and may also include road congestion conditions. Weather information may include sunny, cloudy, overcast, rainy, snowy, or hailous conditions, and may also include ambient temperature, ambient humidity, or air quality information. In-vehicle passenger distribution information may include only the driver, at least one other person besides the driver, children, the elderly, pregnant women, women, or men, etc. Passenger status information may include at least one of the following: passenger action information, passenger fatigue status, and passenger emotions. Passenger action information may include making a phone call, smoking, playing games, or sleeping, passenger fatigue status may be mild, moderate, or moderate, and passenger emotions may be happy, sad, calm, or excited, etc. Time information may include morning, evening, noon, a specific moment, or a specific time period. Vehicle information may include at least one of the following: vehicle fault information, vehicle speed, and battery level. Driving behavior information may include at least one of the following: vehicle acceleration, deceleration, steering information, and driving style. Vehicle location information may include locations such as home, parking lot, shopping mall, office, or tourist attraction.

[0024] In some implementations, step S110 is executed only if both the vehicle's scene-active push function and privacy authorization function are enabled. In this approach, if the vehicle's scene-active push function is enabled but the privacy authorization function is disabled, a privacy authorization prompt message is output to prompt the user to enable the privacy authorization function. Furthermore, in response to an enable command input based on the privacy authorization prompt message, the privacy authorization function is enabled. Of course, if the received command based on the privacy authorization prompt message is to disable the enable command, step S110 is not executed.

[0025] In this method, step S110 can also be executed only when the vehicle's infotainment system account is logged in, the proactive push function is enabled, and the privacy authorization function is enabled. In other words, at this time, the scene association parameters obtained by the vehicle at the current moment are the scene association parameters of the currently logged-in infotainment system account.

[0026] Step S120: If the scene association parameters meet the push conditions of the target push scene, and the current penalty parameter of the target push scene is less than the set parameter threshold, then the target push scene is pushed, and the target push scene includes at least one in-vehicle function.

[0027] In this embodiment, the push conditions for the target push scenario may include standard scenario association parameters. The target push scenario includes at least one in-vehicle function, such as adjusting the in-vehicle air conditioning temperature, activating a nap mode, playing trending news, or playing music. This can be understood as follows: if the scenario association parameters of the vehicle meet the standard scenario association parameters, it indicates that the user currently has a need for the target push scenario. Specifically, the current scenario association parameters are matched with the standard scenario association parameters under the target push scenario. If the current scenario association parameters match the standard scenario association parameters, it is determined that the current scenario association parameters meet the push conditions for the target push scenario; if the current scenario association parameters do not match the standard scenario association parameters, it is determined that the current scenario association parameters do not meet the push conditions for the target push scenario.

[0028] Considering that user needs for specific scenarios often change in practical applications, this application also sets corresponding penalty parameters for target push scenarios. That is, based on the user's feedback actions in response to the push scenario, the current penalty parameter for that scenario is dynamically adjusted to reflect the user's true needs for that scenario. Specifically, a smaller current penalty parameter for the target push scenario reflects a higher level of user demand for that scenario, and vice versa. Based on this, a corresponding threshold parameter is pre-set for the target push scenario, such as 1 or 3. Therefore, while ensuring that the scenario-related parameters meet the push conditions for the target push scenario, it is also necessary to determine whether the current penalty parameter for the target push scenario is less than the set threshold parameter. If it is less, the target push scenario is pushed; otherwise, it indicates that the user has no or very little demand for the target push scenario, and the target push scenario will not be pushed.

[0029] Optionally, the push method for the target push scenario can be a display push on the vehicle's in-vehicle screen, a playback push through the vehicle's speakers, or a combination of both. This embodiment does not limit this.

[0030] In some implementations, the target push scenario can be any of the multiple preset push scenarios pre-stored in the vehicle. Of course, for each preset push scenario, the corresponding push conditions are also pre-stored.

[0031] Step S130: In response to the rejection instruction for the target push scenario, adjust the strategy according to the set parameters and increase the current penalty parameter of the target push scenario.

[0032] Understandably, after the vehicle pushes the target push scenario, the user can determine whether the vehicle needs to execute the in-vehicle functions in the target push scenario based on their actual needs at the current moment. If the user does not need it, they can enter a denial command. Correspondingly, the vehicle can respond to the denial command for the target push scenario, not execute the in-vehicle functions in the target push scenario, and will adjust the strategy according to the set parameters to increase the current penalty parameters of the target push scenario.

[0033] In some implementations, when a target push scenario is pushed for the first time, its current penalty parameter is generally an initial penalty parameter. This initial penalty parameter can be a pre-set value, such as 0 or 0.01, and is generally much smaller than the aforementioned set parameter threshold. That is, if the scenario association parameters meet the push conditions of the target push scenario, and the target push scenario has not yet been pushed, then by default, the target push scenario will be pushed to test the user's true needs for the target push scenario. Then, based on the user's input of the push scenario, the current penalty parameter of the target push scenario will be dynamically adjusted.

[0034] Optionally, in response to a rejection instruction for the target push scenario, the current penalty parameter of the target push scenario can be increased by a first preset value. With the current penalty parameter set to 0.6, the first preset value to 0.5, and the parameter threshold set to 1, upon receiving a rejection instruction for the target push scenario, the current penalty parameter 0.6 will be increased by the first preset value of 0.5, resulting in an increased current penalty parameter of 1.1. Clearly, at this point, the current penalty parameter 1.1 is greater than the set parameter threshold of 1. Therefore, within the time period after step S130, if the scene association parameters obtained again at the current moment meet the push conditions of the target push scenario, since the current penalty threshold of the target push scenario is greater than the set parameter threshold, indicating that the user does not need the vehicle to execute the in-vehicle functions under the target push scenario, to avoid interfering with the user due to frequent pushes of scenarios the user does not need, the vehicle will not push the target push scenario at this time.

[0035] Optionally, after step S120, if the user does indeed need to execute the in-vehicle functions in the target push scenario, they can input a start command. Correspondingly, the vehicle can respond to the start command input for the target push scenario, execute all in-vehicle functions in the target push scenario, and adjust the current penalty parameter of the target push scenario according to the set parameter adjustment strategy. That is to say, even after the user allows the execution of the in-vehicle functions in the target push scenario, the current penalty parameter of the target push scenario will still be dynamically adjusted accordingly.

[0036] Therefore, the current penalty parameter of the target push scenario quantifies the user's demand for the target push scenario to some extent. The smaller the current penalty parameter, the greater the user's demand for the target push scenario; conversely, the larger the current penalty parameter, the smaller the user's demand for the target push scenario. If the current penalty parameter of the target push scenario is greater than the set threshold, it can be understood that the user's demand for the target push scenario is very small or even unnecessary. In this case, there is no need to push the target push scenario to reduce frequent interference with users in the vehicle.

[0037] In this embodiment, when a user rejects a target push scenario, the penalty parameter of the target push scenario is reduced to reflect the user's true needs for the scenario. This avoids problems such as frequent interference to the user caused by excessive pushes, and makes the scenario push more adaptable to the user's actual needs and preferences.

[0038] Please refer to Figure 2 , Figure 2 This is a flowchart illustrating a scene push method according to another embodiment of this application. The following will be combined with... Figure 2 The scenario push method provided in the embodiments of this application will be described in detail. The scenario push method may include the following steps:

[0039] Step S210: Obtain the scene-related parameters of the vehicle at the current moment.

[0040] In this embodiment, the specific implementation of step S210 can be found in the content of the foregoing embodiments, and will not be repeated here.

[0041] Step S220: If the scene association parameters meet the push conditions of the target push scene, and the current penalty factor is less than the set penalty factor threshold and the current penalty count is less than the set penalty count threshold, then the target push scene is pushed.

[0042] In this embodiment, the current penalty parameters include the current penalty factor and the current penalty count. Correspondingly, the set parameter thresholds also include a set penalty factor threshold and a set penalty count threshold. Based on this, when it is determined that the scene association parameters meet the push conditions of the target push scene, it is further determined whether the current penalty factor is less than the set penalty factor threshold and whether the current penalty count is less than the set penalty count threshold. The target push scene is only pushed when both the current penalty factor and the current penalty count are determined to be less than the set penalty factor threshold. The target push scene is not pushed when either the current penalty factor is greater than or equal to the set penalty factor threshold or the current penalty count is greater than or equal to the set penalty count threshold. Both the set penalty factor threshold and the set penalty count threshold are positive numbers, and the set penalty count threshold is a positive integer.

[0043] The determination of whether the scene association parameters meet the push conditions of the target push scene can be found in the content of the aforementioned embodiments, and will not be repeated here.

[0044] Step S230: In response to the rejection instruction, increase the current penalty base and the current penalty factor of the target push scenario according to the parameter increase rule corresponding to the instruction type of the rejection instruction.

[0045] In this embodiment, the current penalty parameter also includes the current penalty base. The aforementioned current penalty count is determined based on the product of the current penalty base and the current penalty factor. That is, current penalty count = current penalty base × current penalty factor. It should be noted that if the product of the current penalty base and the current penalty factor is a decimal, it is rounded down to the nearest integer as the calculated current penalty count. This ensures that the current penalty count is an integer, thereby increasing the tolerance for user input rejection commands and reducing the possibility of problems such as not providing subsequent push notifications for scenarios that the user might need due to excessive penalty counts. For example, if the product of the current penalty base and the current penalty factor is 1.5, then 1 is taken as the current penalty count; or if the product of the current penalty base and the current penalty factor is 0.5, then 0 is taken as the current penalty count.

[0046] Furthermore, the rejection instructions include various types, each with different rejection levels. Correspondingly, the parameter adjustment strategy also includes various parameter increase rules, each with different increase levels. There is a one-to-one correspondence between the various rejection instructions and the various parameter increase rules; that is, the increase level of the parameter increase rule corresponding to a rejection instruction with different rejection levels is also different. It should be noted that the higher the rejection level of the rejection instruction, the greater the increase level of the corresponding parameter increase rule. In other words, a higher rejection level indicates a lower demand from the user for the target push scenario; therefore, a greater increase level is needed to increase the current penalty parameter.

[0047] In some implementations, the multiple rejection instructions may include at least a "stop pushing" instruction, an "ignore pushing" instruction, a "close pushing" instruction, and a "timeout exit" instruction. Specifically, this will be combined with... Figure 3 This section explains how the vehicle increases the current penalty base and current penalty factor in the target push scenario according to the parameter increase rules corresponding to the type of rejection instruction.

[0048] Optionally, if the user clicks "Don't Push Anymore," meaning the user has virtually no further need for the target push scenario (i.e., the vehicle doesn't need to execute the in-vehicle functions within the target push scenario), the vehicle receives a "Don't Push Anymore" command. In response, the vehicle increases the current penalty factor according to the parameter increase rules corresponding to the command, i.e., by the maximum possible parameter increase. The current penalty factor can be increased to a first preset value, such as... Figure 3 As shown, the current penalty factor is directly increased to 99. Of course, the current base number can also be increased at the same time, for example, to 10. This embodiment does not limit this.

[0049] Understandably, after the user inputs the command to stop pushing notifications, the currently logged-in vehicle infotainment account will be prohibited from actively pushing the function. At the same time, if the user does not change the in-vehicle function or push conditions in the target push scenario within a specified period of time (such as 10 days), the target push scenario will be completely deleted, and the pre-trained scenario model will re-analyze and generate a new push scenario.

[0050] Optionally, if the user clicks to turn off push notifications, meaning the user's current need for the target push scenario is almost zero (i.e., the vehicle does not currently need to execute the in-vehicle functions in the target push scenario), the vehicle receives a push notification turn-off command. Therefore, it can respond to the turn-off command and increase the current penalty factor and the current penalty base according to the parameter increase rule corresponding to the turn-off command. Clearly, the rejection level of the turn-off command is less than the rejection level of the aforementioned "stop pushing" command, so a parameter increase rule with a slightly smaller parameter increase level can be used to increase the current penalty base and the current penalty factor. Specifically, the current penalty base can be increased by a second preset value, and the current penalty factor can be increased by a third preset value, such as... Figure 3 As shown, the current penalty base is increased by 2, and the current penalty factor is increased by 1.

[0051] Furthermore, if the user accidentally enters the command to disable push notifications, they will immediately manually enable the in-vehicle function for the target push notification scenario. Correspondingly, if the vehicle receives a start command for the in-vehicle function for the target push notification scenario within a first specified time period, the current penalty base can be set to 0, and the current penalty factor can be reduced by a fourth preset value. For example... Figure 3 As shown, the current penalty factor can be reduced by 1. Thus, since the current penalty base is set to 0, the corresponding calculated current penalty count is also 0. This ensures that when the scene association parameters obtained again at the current moment meet the push conditions of the target scene, the current penalty count is less than the set penalty count threshold and the current penalty factor is less than the set penalty factor threshold, so as to successfully push the target scene.

[0052] Understandably, if the vehicle receives a start command for an in-vehicle function input within a period longer than the first specified time but shorter than the second specified time, this also indicates that the user has a need for the target push scenario. However, this need is not as high as when the start command is input within the first specified time. Therefore, the vehicle can reduce the current penalty count with a relatively small parameter reduction; specifically, such as... Figure 3 As shown, the number of penalties can be reduced by decreasing the current penalty base by the reciprocal of the current penalty factor. It should be noted that the minimum value of both the current penalty factor and the current penalty base is 0. That is, even when the current penalty factor and the current penalty base are reduced to negative numbers, 0 is taken as the adjusted current penalty factor and the current penalty base.

[0053] Optionally, if the user clicks "ignore push notification," meaning the user currently has no need for the target push notification scenario but is highly likely to need to enable the in-vehicle function under that scenario later, the vehicle receives an "ignore push notification" command. Therefore, it can respond to the "ignore push notification" command and increase the current penalty factor and the current penalty base according to the parameter increase rule corresponding to the "ignore push notification" command. Clearly, the rejection level of the "ignore push notification" command is less than the rejection level of the aforementioned "close push notification" command, so a parameter increase rule with a smaller parameter increase level can be used to increase the current penalty base and the current penalty factor. Specifically, the current penalty base can be increased by a fourth preset value, and the current penalty factor can be increased by a fifth preset value, where the fourth preset value is less than the aforementioned second preset value, and the fifth preset value is less than the aforementioned third preset value. Figure 3 As shown, the current penalty base is increased by 1, and the current penalty factor is increased by 0.5.

[0054] Optionally, if the user does not input a command for the target push scenario within a preset time period, the vehicle will default to timeout exit, generate and respond to a timeout exit command, and increase the current penalty factor and current penalty base according to the parameter increase rule corresponding to the timeout exit command. Obviously, this situation might occur when the user is busy with other things in the car, such as listening to music with headphones, and does not perceive the target push scenario and therefore does not respond. Therefore, the rejection level of the timeout exit command is significantly less than the rejection level of ignoring the push command, and the parameter increase rule with the minimum parameter increase level can be used to increase the current penalty base and current penalty factor. Specifically, the current penalty base can be increased by a sixth preset value, and the current penalty factor can be increased by a seventh preset value, where the sixth preset value is less than the aforementioned fourth preset value, and the seventh preset value is less than or equal to the aforementioned fifth preset value. Figure 3As shown, the current penalty base is increased by 0.5, and the current penalty factor is increased by 0.5.

[0055] Step S240: In response to the start command input for the target push scenario, enable all in-vehicle functions in the target push scenario, and reduce the current penalty parameter of the target push scenario according to the set parameter adjustment strategy.

[0056] Optionally, if a user clicks to enable push notifications, meaning the user currently has a need for the target push scenario and will likely continue to have a strong need for it in the future, the vehicle receives an enable command. In response, the vehicle activates all onboard functions within the target push scenario and adjusts its strategy according to predefined parameters to reduce the current penalty parameters for the target push scenario. For details, please refer to [link to relevant documentation]. Figure 3 As shown, the current penalty base can be reduced to its minimum value, i.e., reduced to 0; and the current penalty factor can be reduced to an eighth preset value, for example, the current penalty factor can be reduced by 1.

[0057] In some implementations, if the scene association parameters meet the push conditions of the target push scene, and the current penalty factor is greater than the second penalty factor threshold and the current penalty count is less than the set penalty count threshold, the emotional state of the user in the vehicle can be obtained, and it can be detected whether the user is asleep. Then, if the user's emotional state is good and the user is not asleep, a prompt voice is output to ask the user why they do not need the target push scene. Then, using a pre-trained scene model and the input reason, the in-vehicle functions and / or the push conditions of the target push scene are updated. Furthermore, after updating the target push scene, the updated target push scene, based on the user's input reason, is pushed again. If the user still inputs a rejection command for the updated target push scene, the target push scene is deleted. Of course, if the user's input reason is that they do not need the target push scene, the target push scene can be deleted directly. In this way, the push scene can be updated promptly according to the user's needs.

[0058] In some implementations, if the user actively activates the in-vehicle function for the target push scenario before pushing the target push scenario, that is, if the vehicle receives an activation command for the in-vehicle function under the target push scenario and detects that the current scenario-related parameters meet the push conditions of the target push scenario, it can also reduce the current penalty parameter of the target push scenario according to the set parameter adjustment strategy. Specifically, such as... Figure 3 The aforementioned method can reduce the current number of penalties by decreasing the current penalty base number by the reciprocal of the current penalty factor, thereby enabling subsequent push notifications to the target scenario to be successfully implemented.

[0059] For example, the target push scenario is turning on the nap mode and turning on the active noise cancellation in the vehicle. The push conditions for the target push scenario can be referred to in Table 1 below:

[0060]

[0061] Table 1

[0062] Based on this, if the current scene-related parameters include: weather information indicating a non-rainy day with a temperature greater than 10 degrees Celsius; passenger information indicating only the driver in the vehicle; time information indicating the current time is between 8 PM and 10 PM; vehicle information indicating the gear is in P (park) and the electronic parking brake (EPB) is engaged; and vehicle location information indicating the vehicle's location is either at the company between 6 AM and 3 PM, and the vehicle is currently located at the user's home or parking space, then the current scene-related parameters are deemed to meet the push conditions for the target push scenario. If the current penalty count for the target push scenario is less than the penalty count threshold (e.g., 1) and the current penalty factor is less than the penalty factor threshold (e.g., 3), then the target push scenario will be pushed via voice or central control screen display, prompting the user whether to enable the "open nap mode and active noise cancellation" in-vehicle functions within the target push scenario.

[0063] For example, the target push scenario is to turn on the "Kid Drop-off Mode". The "Kid Drop-off Mode" is associated with in-vehicle functions such as adjusting the rear air conditioning, switching the driving mode to comfort mode, turning off energy recovery, switching the throttle sensitivity to the lowest setting, switching the braking response to gentle mode, turning on the CST function, and playing children's songs. The push conditions for the target push scenario can be found in Table 2 below:

[0064]

[0065] Based on this, if the current scene-related parameters include weather information (temperature greater than 30 degrees Celsius), passenger information (including driver and children in the back seat), time information (current time being the first preset time period within a weekday, such as 6:00 AM to 9:00 AM), and vehicle location information (current location being "my home" or "my parking space"), then the current scene-related parameters are deemed to meet the push conditions for the target push scenario. If the current penalty count for the target push scenario is less than the penalty count threshold (e.g., 1) and the current penalty factor is less than the penalty factor threshold (e.g., 3), then the target push scenario will be pushed via voice or displayed on the central control screen, prompting the user whether to enable the in-vehicle function associated with "turn on child drop-off mode" in the target push scenario.

[0066] For example, the target push scenario is activating the "Commuting Mode," which is associated with in-vehicle functions such as setting the air conditioning to 26°C, playing trending news, adjusting the driving mode to Sport mode, and activating the navigation's "Familiar Route Mode." The push conditions for the target scenario can be found in Table 3 below:

[0067] Based on this, if the current scene-related parameters include weather information (temperature greater than 30 degrees Celsius), passenger information (only the driver), time information (the current time is within the second preset time period of a weekday, such as 6:00 AM to 9:00 AM), and vehicle location information (currently located at "my home" or "my parking space"), then the current scene-related parameters are deemed to meet the push conditions for the target push scenario. If the current penalty count for the target push scenario is less than the penalty count threshold (e.g., 1) and the current penalty factor is less than the penalty factor threshold (e.g., 3), then the target push scenario will be pushed via voice or central control screen display, prompting the user whether to enable the in-vehicle function associated with "turn on commuting mode" in the target push scenario.

[0068] In this embodiment, firstly, based on the scene association parameters of the vehicle at the current moment, it is determined whether the push conditions for the target push scene are met, and if so, the target push scene is actively pushed. Furthermore, a penalty mechanism is also set up: in addition to meeting the push conditions for the target push scene, the push scene is only pushed if the current penalty parameter of the target push scene is less than a set threshold, i.e., if the target push scene represents a genuine user need. Moreover, if the user actively closes or ignores the target push scene, the penalty parameter of the target push scene is reduced to reflect the user's true need for that scene, thereby avoiding frequent interference to the user due to excessive pushes, and making scene pushes more adaptable to the user's actual needs and preferences.

[0069] Please refer to Figure 4 , Figure 4 This is a flowchart illustrating a scene push method provided in another embodiment of this application. The following will be combined with... Figure 4 The scenario push method provided in the embodiments of this application will be described in detail. The scenario push method may include the following steps:

[0070] Step S301: Obtain the historical scene association parameters and historical operation data of this vehicle within the historical time period before the current moment.

[0071] Step S302: Analyze the historical scene association parameters and historical operation data using a pre-trained scene large model.

[0072] Step S303: If some parameters in the historical scene association parameters match the historical operation data within the time period corresponding to the matched parameters, then based on the historical operation data within the time period corresponding to the matched parameters, determine the vehicle function of the historical operation, generate the target push scene based on the vehicle function of the historical operation, and determine the standard scene association parameters under the target push scene based on the matched parameters, as the push conditions of the target push scene.

[0073] In this embodiment, after the vehicle is powered on, historical scene association parameters and historical operation data within a historical time period prior to the current moment can be obtained. Specifically, historical scene association parameters and historical operation data can be extracted from the online count of the vehicle's currently logged-in in-vehicle account. For example, historical scene association parameters and historical operation data for the past 5 days can be extracted. Then, a pre-trained scene model is used to analyze the historical scene association parameters and historical operation data for the past 5 days. If some parameters are the same for 3 days out of the 5 days, and the historical operation data corresponding to the time intervals of these 3 days are matched (close), then the same parameters in these 3 days are determined as the standard scene association parameters for the target push scenario. Furthermore, based on the historical operation data within the time period corresponding to the same parameters in these 3 days, the in-vehicle function of the historical operation is determined, and the target push scenario is generated based on the in-vehicle function of the historical operation. For example, if a user has used multiple driving modes in a given historical in-vehicle function, the driving mode with the highest frequency of use is identified as the target driving mode in the target push scenario. Similarly, if a user has adjusted the air conditioning temperature multiple times in a given historical in-vehicle function, the maximum and minimum temperature values ​​can be removed, and the average of all other temperature values ​​can be obtained as the target temperature value for air conditioning adjustment in the target push scenario.

[0074] Step S304: Obtain the scene-related parameters of the vehicle at the current moment.

[0075] In this embodiment, the specific implementation of step S304 can be found in the content of the foregoing embodiments, and will not be repeated here.

[0076] Step S305: If the scene association parameters meet the push conditions of the target push scene, and the current penalty parameter of the target push scene is less than the set parameter threshold, then output a prompt message. The prompt message is used to indicate that the target push scene is a scene to be pushed.

[0077] In this embodiment, when it is determined that a target push scenario needs to be pushed, a prompt message can be output first to inform the user that the target push scenario is about to be pushed. Specifically, the prompt message can be output in the form of a pop-up window. For example, the prompt message can be "A target push scenario learned by the system has been generated for you. Do you want to view the settings of the target push scenario?" or "A pre-set target push scenario has been obtained for you. Do you want to view the settings of the target push scenario?"

[0078] Step S306: In response to the scene viewing instruction input based on the prompt information, display the scene setting interface, which includes at least all in-vehicle functions in the target push scene.

[0079] Furthermore, users can input scene viewing commands based on prompts. Correspondingly, the vehicle can respond to these commands and display the scene settings interface. Optionally, the scene settings interface includes at least all in-vehicle functions within the target push scene; other in-vehicle functions may also be included. Based on this, users can select whether to change, delete, or add in-vehicle functions in the target push scene within the scene settings interface; and after making the selection, they can input scene modification commands.

[0080] Step S307: In response to the scene modification command input based on the scene setting interface, update the vehicle functions included in the target push scene.

[0081] Step S308: If the scene association parameters meet the push conditions of the target push scene, and the current penalty parameter of the target push scene is less than the set parameter threshold, then the updated target push scene is pushed.

[0082] Furthermore, this vehicle can respond to user-inputted scene modification commands via the scene settings interface and update the in-vehicle functions included in the target push scene. In other words, if a user changes, deletes, or adds an in-vehicle function to the target push scene in the scene settings interface, the vehicle will modify, delete, or add the in-vehicle functions included in the target push scene accordingly; then, it will push the updated target push scene to inform the user of the updated in-vehicle functions.

[0083] For example, if a user adds the in-car music playback function to the target push scene in the scene settings interface, the updated target push scene will then also add the in-car music playback function.

[0084] Step S309: In response to the rejection instruction for the updated target push scenario, adjust the strategy according to the set parameters and increase the current penalty parameter of the target push scenario.

[0085] Step S310: In response to the start command input for the updated target push scenario, enable all in-vehicle functions in the updated target push scenario, and reduce the current penalty parameter of the target push scenario according to the set parameter adjustment strategy.

[0086] In this embodiment, the specific implementation of steps S309 to S310 can be found in the content of the foregoing embodiments, and will not be repeated here.

[0087] In this embodiment, a pre-trained scenario model can be used to automatically learn and generate target push scenarios based on historical scenario association parameters and historical operation data. When push conditions are met and the current penalty parameter is less than a set threshold, the target push scenario is automatically pushed, avoiding the need for users to continuously operate multiple functions and improving convenience. Furthermore, users can customize push scenarios. When a user rejects a target push scenario, the penalty parameter of the target push scenario is reduced to reflect the user's true need for that scenario, thereby avoiding frequent interference caused by excessive pushes. This makes scenario-based pushes more adaptable to the user's actual needs and preferences.

[0088] Please refer to Figure 5 , Figure 5 This is a flowchart illustrating a scene push method provided in another embodiment of this application. The following will be combined with... Figure 5 The scenario push method provided in the embodiments of this application will be described in detail. This scenario push method may include the following:

[0089] First, when the user enables the self-learning scenario's proactive push function, the vehicle can obtain historical scenario-related parameters and historical operation data from the historical time period prior to the current moment. A pre-trained scenario model is then used to analyze these parameters. If some parameters in the historical scenario-related parameters match the corresponding historical operation data within the same time period, the vehicle's in-vehicle function for the historical operation is determined based on this matching data. Based on this function, the target push scenario is generated. Furthermore, based on the matching parameters, standard scenario-related parameters for the target push scenario are determined as the push conditions for that scenario.

[0090] Furthermore, a pop-up window displays a prompt message, such as "A target push scenario learned by the system has been generated for you. Do you want to view and configure the target push scenario?" If the user clicks the pop-up window based on the prompt message, i.e., inputs a scenario viewing command, the vehicle can respond to the scenario viewing command and display the scenario settings interface. Optionally, the scenario settings interface includes at least all in-vehicle functions in the target push scenario, and may also include other in-vehicle functions. Based on this, the user can choose whether to change, delete, or add in-vehicle functions in the target push scenario in the scenario settings interface; and after making the selection, input a scenario modification command. In response to the scenario modification command input based on the scenario settings interface, the in-vehicle functions included in the target push scenario are updated. If the scenario association parameters meet the push conditions of the target push scenario, and the current penalty parameter of the target push scenario is less than a set parameter threshold, then the updated target push scenario is pushed.

[0091] Optionally, in response to an input activation command for the updated target push scenario, all in-vehicle functions in the updated target push scenario are activated, and the current penalty parameter of the target push scenario is reduced according to the set parameter adjustment strategy. Furthermore, if a subsequent automatic activation command is input simultaneously with the user's activation command, the vehicle can automatically execute the in-vehicle functions in the target push scenario during subsequent push notifications without requiring the user to input the activation command again. Of course, during subsequent automatic push activation, the vehicle outputs a prompt message to remind the user to cancel the automatic activation function for the target push scenario.

[0092] Optionally, in response to a rejection command input for the updated target push scenario, an active push penalty mechanism is initiated, that is, the current penalty base and the current penalty factor of the target push scenario are increased according to the parameter increase rule corresponding to the type of rejection command. For details on how to increase the current penalty base and the current penalty factor, please refer to the content in the foregoing embodiments, which will not be repeated here.

[0093] In this embodiment, a pre-trained scenario model can be used to automatically learn and generate target push scenarios based on historical scenario association parameters and historical operation data. When push conditions are met and the current penalty parameter is less than a set threshold, the target push scenario is automatically pushed, avoiding the need for users to continuously operate multiple functions and improving convenience. Furthermore, users can customize push scenarios. When a user rejects a target push scenario, the penalty parameter of the target push scenario is reduced to reflect the user's true need for that scenario, thereby avoiding frequent interference caused by excessive pushes. This makes scenario-based pushes more adaptable to the user's actual needs and preferences.

[0094] Please refer to Figure 6 The diagram illustrates a structural block diagram of a scene push device 400 according to an embodiment of this application. The device 400 may include: an association parameter acquisition module 410, a scene push module 420, and a penalty parameter adjustment module 430.

[0095] The associated parameter acquisition module 410 is used to acquire the scene associated parameters of the vehicle at the current moment.

[0096] The scene push module 420 is used to push the target push scene if the scene association parameters meet the push conditions of the target push scene and the current penalty parameter of the target push scene is less than a set parameter threshold. The target push scene includes at least one in-vehicle function.

[0097] The penalty parameter adjustment module 430 is used to increase the current penalty parameter of the target push scenario in response to a rejection instruction for the target push scenario, according to a set parameter adjustment strategy.

[0098] In some implementations, the current penalty parameter includes a current penalty factor and a current penalty count, and the set parameter threshold includes a set penalty factor and a set penalty count. The penalty parameter adjustment module 430 can be specifically used to push the target push scenario if the scene association parameter meets the push conditions of the target push scenario, and the current penalty factor is less than the set penalty factor threshold and the current penalty count is less than the set penalty count threshold.

[0099] In this approach, the current penalty parameter also includes a current penalty base, and the current penalty count is determined based on the product of the current penalty base and the current penalty factor. The rejection command can be of various types, each with different rejection degrees. The parameter adjustment strategy includes various parameter increase rules, each with different increase degrees. Each rejection command corresponds one-to-one with one of the various parameter increase rules. Specifically, the penalty parameter adjustment module 430 can be used to respond to the rejection command by increasing the current penalty base and current penalty factor of the target push scenario according to the parameter increase rule corresponding to the type of rejection command.

[0100] In other embodiments, the penalty parameter adjustment module 430 may also be used to, in response to an activation command input for the target push scenario after the target push scenario is pushed, activate all in-vehicle functions in the target push scenario and reduce the current penalty parameter of the target push scenario according to the set parameter adjustment strategy.

[0101] In some implementations, the push conditions for the target push scenario include standard scene association parameters. The scene push device 400 may further include a condition judgment module. Specifically, the condition judgment module may be used to match the current scene association parameters with the standard scene association parameters before pushing the target push scenario if the scene association parameters satisfy the push conditions for the target push scenario and the current penalty parameter of the target push scenario is less than a set parameter threshold; if the current scene association parameters match the standard scene association parameters, then it is determined that the current scene association parameters satisfy the push conditions for the target push scenario; if the current scene association parameters do not match the standard scene association parameters, then it is determined that the current scene association parameters do not satisfy the push conditions for the target push scenario.

[0102] In this approach, the scene push device may further include: a historical information acquisition module, an analysis module, a scene generation module, and a standard parameter determination module. The historical information acquisition module can be used to acquire historical scene association parameters and historical operation data of the vehicle within a historical time period prior to the current moment, before matching the current scene association parameters with the standard scene association parameters. The analysis module can be used to analyze the historical scene association parameters and historical operation data using a pre-trained scene model to obtain analysis results. The scene generation module can be used to determine the vehicle function of the historical operation based on the historical operation data within the time period corresponding to the matched historical scene association parameters if some parameters in the historical scene association parameters match the historical operation data within the time period corresponding to the matched parameters, and generate the target push scene based on the vehicle function of the historical operation. The standard parameter determination module can determine the standard scene association parameters under the target push scene based on the matched parameters, as the push condition for the target push scene.

[0103] In some embodiments, the scene push device 400 may further include: a prompting module, a display module, and a scene update module. The prompting module may output a prompt message before pushing the target push scene, the prompt message indicating that the target push scene is a scene to be pushed. The display module may display a scene setting interface in response to a scene viewing command input based on the prompt message, the scene setting interface including at least all in-vehicle functions in the target push scene. The scene update module may update the in-vehicle functions included in the target push scene in response to a scene modification command input based on the scene setting interface. The scene push module 420 may push the updated target push scene if the scene association parameters meet the push conditions of the target push scene and the current penalty parameter of the target push scene is less than a set parameter threshold.

[0104] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the above-described device and module can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0105] In the several embodiments provided in this application, the coupling between modules can be electrical, mechanical, or other forms of coupling.

[0106] Furthermore, the functional modules in the various embodiments of this application can be integrated into one processing module, or each module can exist physically separately, or two or more modules can be integrated into one module. The integrated modules described above can be implemented in hardware or as software functional modules.

[0107] In summary, a pre-trained scenario-based model can be used to automatically learn and generate target push scenarios based on historical scenario association parameters and historical operation data. When push conditions are met and the current penalty parameter is less than a set threshold, the target push scenario is automatically pushed, avoiding the need for users to continuously operate multiple functions and improving convenience. Furthermore, users can customize push scenarios. When a user rejects a target push scenario, the penalty parameter is reduced to reflect the user's true need for that scenario, thus avoiding frequent interference caused by excessive pushes. This allows scenario-based pushes to better adapt to the user's actual needs and preferences.

[0108] The following will combine Figure 7 This application describes one type of vehicle.

[0109] Reference Figure 7 , Figure 7The diagram shows a structural block diagram of a vehicle 500 according to an embodiment of this application. The above-described method provided in this embodiment of the application can be executed by the vehicle 500.

[0110] The vehicle 500 in this application embodiment may include one or more of the following components: processor 501, memory 502, and one or more application programs, wherein the one or more application programs may be stored in memory 502 and configured to be executed by one or more processors 501, and the one or more programs are configured to perform the methods as described in the foregoing method embodiments.

[0111] Processor 501 may include one or more processing cores. Processor 501 connects to various parts within the vehicle 500 using various interfaces and lines, and performs various functions and processes data of the vehicle 500 by running or executing instructions, programs, code sets, or instruction sets stored in memory 502, and by calling data stored in memory 502. Optionally, processor 501 may be implemented using at least one hardware form of Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), or Programmable Logic Array (PLA). Processor 501 may integrate one or more of the following: Central Processing Unit (CPU), Graphics Processing Unit (GPU), and modem. The CPU primarily handles the operating system, user interface, and applications; the GPU is responsible for rendering and drawing the displayed content; and the modem handles wireless communication. It is understood that the aforementioned modem can also be integrated into processor 501 and implemented using a separate communication chip.

[0112] The memory 502 may include random access memory (RAM) or read-only memory (ROM). The memory 502 can be used to store instructions, programs, code, code sets, or instruction sets. The memory 502 may include a program storage area and a data storage area. The program storage area may store instructions for implementing an operating system, instructions for implementing at least one function (such as touch functionality, sound playback functionality, image playback functionality, etc.), and instructions for implementing the various method embodiments described below. The data storage area may also store data created by the vehicle 500 during use (such as the various correspondences described above).

[0113] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working process of the above-described device and module can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0114] In the several embodiments provided in this application, the coupling or direct coupling or communication connection between the modules shown or discussed may be an indirect coupling or communication connection through some interface, device or module, and may be electrical, mechanical or other forms.

[0115] Furthermore, the functional modules in the various embodiments of this application can be integrated into one processing module, or each module can exist physically separately, or two or more modules can be integrated into one module. The integrated modules described above can be implemented in hardware or as software functional modules.

[0116] Please refer to Figure 8 This diagram illustrates a structural block diagram of a computer-readable storage medium provided in an embodiment of this application. The computer-readable medium 600 stores program code that can be called by a processor to execute the methods described in the above method embodiments.

[0117] The computer-readable storage medium 600 may be an electronic memory such as flash memory, EEPROM (Electrically Erasable Programmable Read-Only Memory), EPROM, hard disk, or ROM. Optionally, the computer-readable storage medium 600 includes a non-transitory computer-readable storage medium. The computer-readable storage medium 600 has storage space for program code 610 that performs any of the method steps described above. This program code can be read from or written to one or more computer program products. The program code 610 may be compressed, for example, in a suitable form.

[0118] In some embodiments, a computer program product or computer program is provided, which includes computer instructions stored in a computer-readable storage medium. A processor of an electronic device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the electronic device to perform the steps in the above-described method embodiments.

[0119] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A scenario push method, characterized by, The method comprises: acquiring a scene-related parameter of a current time of a vehicle; if the scene-related parameter meets a push condition of a target push scene, and a current penalty parameter of the target push scene is less than a set parameter threshold, pushing the target push scene, the target push scene comprising at least one vehicle-mounted function; in response to a rejection instruction for the pushed target push scene, increasing the current penalty parameter of the target push scene according to a set parameter adjustment strategy; wherein the current penalty parameter comprises a current penalty base and a current penalty factor, the rejection instruction comprises multiple types, the rejection degree of different types of the rejection instruction is different, the set parameter adjustment strategy comprises multiple parameter increasing rules, the parameter increasing degree under different parameter increasing rules is different, and multiple rejection instructions correspond to the multiple parameter increasing rules one by one; the response to the rejection instruction for the pushed target push scene, the current penalty base and the current penalty factor of the target push scene are increased according to the parameter increasing rule corresponding to the type of the rejection instruction. The current penalty parameter further comprises a current penalty times, which is determined based on the product of the current penalty base and the current penalty factor, and the set parameter threshold comprises a set penalty factor threshold and a set penalty times threshold; 2. The method of claim 1, wherein, if the scene-related parameter meets the push condition of the target push scene, and the current penalty factor is less than the set penalty factor threshold and the current penalty times is less than the set penalty times threshold, the target push scene is pushed. After the target push scene is pushed, the method further comprises: in response to an opening instruction input for the pushed target push scene, opening all vehicle-mounted functions in the target push scene, and reducing the current penalty parameter of the target push scene according to the set parameter adjustment strategy.

3. The method of claim 1, wherein, The push condition of the target push scene comprises a standard scene-related parameter; before the target push scene is pushed if the scene-related parameter meets the push condition of the target push scene, and the current penalty parameter of the target push scene is less than the set parameter threshold, the method further comprises:

4. The method of claim 1, wherein, matching the scene-related parameter of the current time with the standard scene-related parameter; if the scene-related parameter of the current time matches the standard scene-related parameter, it is determined that the scene-related parameter of the current time meets the push condition of the target push scene; if the scene-related parameter of the current time does not match the standard scene-related parameter, it is determined that the scene-related parameter of the current time does not meet the push condition of the target push scene. ​ ​ 5. The method of claim 4, wherein, Before the matching the scene correlation parameter of the current moment with the standard scene correlation parameter, the method further comprises: obtaining historical scene correlation parameters and historical operation data of the vehicle in a historical time period before the current moment; analyzing the historical scene correlation parameters and the historical operation data by using a pre-trained scene large model to obtain an analysis result; if some parameters in the historical scene correlation parameters and historical operation data in a time period corresponding to the some parameters are matched, determining a historical operation vehicle function based on the historical operation data in the time period corresponding to the some parameters, and generating the target push scene based on the historical operation vehicle function; determining the standard scene correlation parameter in the target push scene based on the some parameters, as a push condition of the target push scene.

6. The method according to any one of claims 1 to 5, characterized in that, Before the pushing the target push scene, the method further comprises: outputting prompt information, the prompt information being used to prompt that the target push scene is a scene to be pushed; in response to a scene viewing instruction input based on the prompt information, displaying a scene setting interface, the scene setting interface at least including all vehicle functions in the target push scene; in response to a scene modification instruction input based on the scene setting interface, updating the vehicle functions included in the target push scene; the pushing the target push scene comprises: pushing the updated target push scene.

7. A scenario pushing apparatus characterized by comprising: The device comprises: a correlation parameter acquisition module configured to obtain a scene correlation parameter of the vehicle at the current moment; a scene push module configured to, if the scene correlation parameter meets a push condition of a target push scene, and a current penalty parameter of the target push scene is less than a set parameter threshold, push the target push scene, the target push scene at least including one vehicle function; a penalty parameter adjustment module configured to, in response to a rejection instruction for the pushed target push scene, increase the current penalty parameter of the target push scene according to a set parameter adjustment strategy; wherein the current penalty parameter comprises a current penalty base and a current penalty factor, the instruction type of the rejection instruction comprises multiple types, the rejection degrees of different types of the rejection instruction are different, the set parameter adjustment strategy comprises multiple parameter increase rules, the parameter increase degrees under different parameter increase rules are different, and multiple rejection instructions and the multiple parameter increase rules correspond to each other one by one; the response to the rejection instruction for the pushed target push scene, the increase of the current penalty parameter of the target push scene according to the set parameter adjustment strategy comprises: in response to the rejection instruction, increasing the current penalty base and the current penalty factor of the target push scene according to the parameter increase rule corresponding to the instruction type of the rejection instruction.

8. A vehicle characterized by comprising: The vehicle comprises: one or more processors; a memory; One or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs configured to perform the method of any one of claims 1-6.

9. A computer-readable storage medium, characterized in that, The computer readable storage medium stores program codes, and the program codes can be invoked by the processor to execute the method of any one of claims 1-6.

Images