A method and apparatus for adjusting an armrest of a seat

Abstract

The application relates to the technical field of vehicles, and provides a seat armrest adjusting method and device. The method comprises the following steps: determining a pre-stored height corresponding to state information. Then, a target armrest is adjusted to the pre-stored height. In the case that an adjusting instruction is received from the user, the target armrest is adjusted from the pre-stored height to a target height indicated by the adjusting instruction. In this way, the armrest is adjusted to the pre-stored height corresponding to the state information, so that the height meeting the user's demand in the corresponding state is obtained. After the adjusting instruction is received, the target armrest is adjusted to the target height indicated by the adjusting instruction. In this way, the user's demand can be responded to in real time.

Description

Technical Field

[0001] This application relates to the field of vehicle technology, and in particular to a method and device for adjusting a seat armrest. Background Technology

[0002] During vehicle use, the height of the center armrest between the driver and passenger seats is usually a crucial factor affecting the comfort of both. Different users have different needs regarding the armrest.

[0003] Whether the armrest height is kept at a fixed position or manually adjusted, it cannot meet the diverse needs of different users for armrest height, which greatly affects user comfort. Summary of the Invention

[0004] This application provides a method and apparatus for adjusting a seat armrest, used to adjust the armrest height according to status information, and to memorize the adjusted target height after the user adjusts the armrest height via an adjustment command, so as to adjust the armrest according to the target height in subsequent uses under the same status information. This application also provides computer equipment, computer-readable storage media, computer program products, etc.

[0005] The first aspect of this application provides a method for adjusting a seat armrest, the method comprising: determining a pre-stored height corresponding to status information, the status information including at least one of a user identifier, the occupancy status of a seat in a target vehicle, and driving information; adjusting a target armrest to the pre-stored height, the target armrest being associated with a seat; and, upon receiving an adjustment command from a user, adjusting the target armrest from the pre-stored height to the target height indicated by the adjustment command.

[0006] It is understood that status information can include at least one of the following: user identifier, seat occupancy status of the target vehicle, and driving information. That is, status information can include one, two, or all three of these items. Depending on the specific scenario, any combination of different items from the status information can be selected to store the corresponding pre-stored height.

[0007] Specifically, a user identifier refers to an identifier that can be used to identify or distinguish a user, such as account information or user identity information. This is merely illustrative and not restrictive.

[0008] Specifically, the seats in the target vehicle refer to any seat in the vehicle that is associated with the target armrest. Depending on the location of the target armrest, there may be one or more seats. For example, if the target armrest is on one side of a seat and is only associated with that seat, then only the occupancy status of that seat needs to be considered. Or, if the target armrest is between two adjacent seats, then the occupancy status of both seats needs to be considered.

[0009] Specifically, driving information refers to information related to driving modes. For example, driving information may include driving modes, which can include intelligent driving modes and non-intelligent driving modes. Furthermore, in intelligent driving modes, different levels can be distinguished to store corresponding pre-stored levels. For example, levels in intelligent driving modes may include L2, L3, L4, etc.

[0010] In this application, the handrail is adjusted to a corresponding preset height based on status information. Since the preset height is the historical handrail height used under the user's current status, the handrail can be adjusted to a height that meets the user's preferences or needs under the corresponding status. Upon receiving an adjustment command, the handrail height is adjusted based on the height specified in the command, allowing for timely adjustment to meet the user's real-time needs.

[0011] In one possible implementation, the seat includes a first seat and a second seat, the first seat corresponds to a first occupancy state, and the second seat corresponds to a second occupancy state. Determining the pre-stored height corresponding to the state information includes: determining the pre-stored height based on at least one of user identifier, first occupancy state, second occupancy state, and driving information.

[0012] It is understandable that "first seat" and "second seat" here refer to any two adjacent seats in the vehicle. The positional relationship between the target armrest and the two seats can be as follows: the target armrest is on one side of the first seat and is only related to the first seat; the target armrest is on one side of the second seat and is only related to the second seat; or the target armrest is between the first and second seats.

[0013] Furthermore, the pre-stored height is determined by selecting at least one from user identifier, first occupancy state, second occupancy state, and driving information based on different positional relationships. Specific embodiments will be described in detail in the specification, and will not be elaborated further here.

[0014] In this possible implementation, at least one of the four pieces of information is selected to store the corresponding pre-stored height. In this way, different combinations of the four pieces of information can store the corresponding pre-stored height for various scenarios or needs, so that the target handrail can be adjusted to its corresponding pre-stored height in different scenarios to meet user needs.

[0015] In one possible implementation, determining the pre-stored height based on the user identifier, the first occupancy status, and driving information includes: determining the pre-stored height based on driving information when the user identifier indicates the first identifier and the first occupancy status is occupied.

[0016] As you can understand, the first identifier here refers to any known user identifier, not a fixed identifier, such as necessarily referring to account A. In other words, the first identifier can be any account information or any user's identity identifier, without specifically referring to any particular account information or identity identifier.

[0017] "User ID indicator first ID" indicates that the current user has been identified, and all subsequent stored heights are related to that user.

[0018] For example, the first seat can be the driver's seat, and the second seat can be the front passenger seat. The occupancy status of the front passenger seat can be disregarded if the driver's seat is already occupied. This is merely illustrative and not restrictive.

[0019] In this possible implementation, given that the user identifier and the first occupancy state are already determined, it is necessary to further determine the corresponding pre-stored height based on different driving information. In this way, by using three pieces of information (user identifier, first occupancy state, and driving information), the scenario corresponding to the pre-stored height is further refined, thereby improving the alignment accuracy between the scenario and the pre-stored height.

[0020] In one possible implementation, the driving information includes a driving mode. Based on the driving information, a pre-stored height is determined, including: if the driving information is a first driving mode, determining a pre-stored height indicator for a first pre-stored height; and if the driving information is a second driving mode, determining a pre-stored height indicator for a second pre-stored height.

[0021] In one example, the first driving mode could be the intelligent driving mode. In another example, the second driving mode could be the non-intelligent driving mode.

[0022] In this possible implementation, different pre-stored heights are determined by different driving modes, thereby further refining the scenarios corresponding to the pre-stored heights to adapt to different driving modes.

[0023] In one possible implementation, the driving information also includes a level, which is associated with a first driving mode. Based on the driving information, a pre-stored height is determined, including: if the driving information is a first driving mode and the level indicates a first level, determining a third pre-stored height; if the driving information is a first driving mode and the level indicates a second level, determining a fourth pre-stored height, where the second level is higher than the first level; and if the driving information is a first driving mode and the level indicates a third level, determining a fifth pre-stored height, where the third level is higher than the second level.

[0024] For example, the first driving mode could be the intelligent driving mode.

[0025] In this possible implementation, the pre-stored height is further determined by the driving level in the first driving mode. This allows for a more precise mapping of the armrest height across different driving levels, thus accommodating user needs in various scenarios.

[0026] In one possible implementation, the pre-stored height is determined based on the user identifier, the second occupancy status, and driving information, including: when the user identifier indicates the second identifier and the second occupancy status is occupied, the pre-stored height is determined based on the driving information.

[0027] It's understandable that the second identifier here refers to any known user identifier, not a fixed identifier, such as necessarily referring to account H. In other words, the second identifier can be any account information or any user's identity identifier, without specifically referring to any particular account information or identity identifier. The second identifier may be the same as or different from the first identifier.

[0028] In this possible implementation, if the second seat is already occupied, the pre-stored height is further determined based on different driving information.

[0029] For example, the first seat could be the driver's seat, and the second seat could be the front passenger seat. In this example, the occupancy status of the front passenger seat is only considered if the driver's seat is unoccupied. That is, in this example, the case where "the user identifier indicates the second identifier and the second occupancy status is occupied" includes the assumption that the driver's seat is unoccupied. Or, in this example, it is determined that the first occupancy status indicator corresponding to the driver's seat is unoccupied before implementing this possible approach.

[0030] In this possible implementation, given that the user identifier and the second occupancy state are already determined, it is necessary to further determine the corresponding pre-stored height based on different driving information. This refines the scenario corresponding to the pre-stored height by using the user identifier, the second occupancy state, and the driving information, thereby improving the alignment accuracy between the scenario and the pre-stored height.

[0031] In one possible implementation, the driving information includes a driving mode. Based on the driving information, a pre-stored height is determined, including: if the driving information is a first driving mode, determining a sixth pre-stored height indicator; and if the driving information is a second driving mode, determining a seventh pre-stored height indicator.

[0032] It is understandable that the sixth and seventh preset heights can be the same or different. The use of the sixth and seventh preset heights here is to distinguish the preset heights corresponding to the two driving modes, and does not mean that the two preset heights are necessarily different.

[0033] In this possible implementation, the corresponding pre-stored height is determined based on different driving information. Here, only driving information is considered, which expands the adaptability of the pre-stored height. In some cases, the corresponding pre-stored height can also be determined using only driving information.

[0034] In one possible implementation, the driving information also includes a level, which is associated with a first driving mode. Based on the driving information, determining the pre-stored height includes: if the driving information is a first driving mode and the level indicates a first level, determining the pre-stored height to indicate an eighth pre-stored height; if the driving information is a first driving mode and the level indicates a second level, determining the pre-stored height to indicate a ninth pre-stored height; and if the driving information is a first driving mode and the level indicates a third level, determining the pre-stored height to indicate a tenth pre-stored height.

[0035] Similarly, the eighth, ninth, and tenth pre-store heights can be the same or different. The use of eighth, ninth, and tenth pre-store heights here is to distinguish the pre-store heights corresponding to the three levels, and does not imply that these three pre-store heights are necessarily different.

[0036] In this possible implementation, the pre-stored height is determined by further distinguishing the levels in the first driving mode. In the scenario that only considers driving information, the scenario corresponding to the pre-stored height and level is further expanded to adapt to the user's needs for the armrest height under different levels.

[0037] In one possible implementation, determining the pre-stored height based on at least one of user identifier, first occupancy state, second occupancy state, and driving information includes: determining the pre-stored height based on user identifier; or, determining the pre-stored height based on first occupancy state; or, determining the pre-stored height based on second occupancy state; or, determining the pre-stored height based on driving information.

[0038] In this possible implementation, only one piece of information is selected to determine the corresponding pre-stored height, thus expanding the scenarios in which a single piece of information corresponds to a pre-stored height.

[0039] In one possible implementation, determining the pre-stored height based on at least one of user identifier, first occupancy status, second occupancy status, and driving information includes: determining the pre-stored height based on user identifier and first occupancy status, or determining the pre-stored height based on user identifier and second occupancy status.

[0040] In this possible implementation, the pre-stored height is determined based on the user identifier and the first occupancy status, or based on the user identifier and the second occupancy status. Both scenarios only require the user identifier and the seat occupancy status to determine the pre-stored height, without considering driving information. This expands the scenarios corresponding to the pre-stored height and the user identifier and seat occupancy status information.

[0041] In one possible implementation, determining the pre-stored height based on at least one of user identifier, first occupancy status, second occupancy status, and driving information includes: determining the pre-stored height based on user identifier and driving information; or, determining the pre-stored height based on first occupancy status and driving information; or, determining the pre-stored height based on second occupancy status and driving information.

[0042] In this possible implementation, the pre-stored height is determined based on a combination of user identifier, first occupancy status, second occupancy status, and driving information. These three scenarios, taking driving information into account, determine the pre-stored height through user identifier or seat occupancy status, thus expanding the scenarios where the pre-stored height corresponds to two pieces of information.

[0043] In one possible implementation, the first driving mode is an intelligent driving mode.

[0044] In this possible implementation, pre-stored heights are stored by differentiating between intelligent driving modes and other modes. This allows for matching corresponding scenario preferences based on the pre-stored heights in different modes, enhancing cabin comfort and the intelligent driving experience.

[0045] One possible implementation method also includes updating the pre-stored height corresponding to the state information based on the target height.

[0046] In this possible implementation, the pre-stored height under the corresponding state information can be updated based on the adjusted target height. This ensures that the pre-stored height is promptly updated when user requirements change, guaranteeing that the pre-stored height aligns with user needs in a timely manner.

[0047] In one possible implementation, the first seat is the driver's seat, the second seat is the passenger seat, and the target armrest is positioned between the driver's seat and the passenger seat.

[0048] In this possible implementation, the target armrest is the armrest between the driver's seat and the front passenger seat. The armrest between the driver's seat and the front passenger seat is adjusted to meet the user's needs when the front seats are seated.

[0049] A second aspect of this application provides a seat armrest adjustment device, comprising: a determining module for determining a pre-stored height corresponding to status information, the status information including at least one of a user identifier, the occupancy status of a seat in a target vehicle, and driving information; a first adjusting module for adjusting a target armrest to the pre-stored height, the target armrest being associated with a seat; and a second adjusting module for adjusting the target armrest from the pre-stored height to the target height indicated by the adjusting instruction upon receiving an adjustment instruction from a user.

[0050] In one possible implementation, the seat includes a first seat and a second seat, the first seat corresponds to a first occupancy state, and the second seat corresponds to a second occupancy state. The determining module is further used to determine the pre-stored height based on at least one of the user identifier, the first occupancy state, the second occupancy state, and driving information.

[0051] In one possible implementation, the determining module is further configured to determine the pre-stored height based on driving information when the user identifier indicates the first identifier and the first occupancy status is occupied.

[0052] In one possible implementation, the driving information includes a driving mode, and the determining module is further configured to determine a pre-stored height indicator as a first pre-stored height when the driving information is a first driving mode; and to determine a pre-stored height indicator as a second pre-stored height when the driving information is a second driving mode.

[0053] In one possible implementation, the driving information also includes a level, which is associated with a first driving mode. The determining module is further configured to determine a third pre-stored height when the driving information is the first driving mode and the level indicates a first level; determine a fourth pre-stored height when the driving information is the first driving mode and the level indicates a second level, with the second level being higher than the first level; and determine a fifth pre-stored height when the driving information is the first driving mode and the level indicates a third level, with the third level being higher than the second level.

[0054] In one possible implementation, the determining module is further configured to determine the pre-stored height based on driving information when the user identifier indicates the second identifier and the second occupancy status is occupied.

[0055] In one possible implementation, the driving information includes a driving mode, and the determining module is further configured to determine a sixth pre-stored height indicator when the driving information is a first driving mode; and to determine a seventh pre-stored height indicator when the driving information is a second driving mode.

[0056] In one possible implementation, the driving information also includes a level, which is associated with a first driving mode. The determining module is further configured to determine an eighth pre-stored height when the driving information is a first driving mode and the level indicates a first level; to determine a ninth pre-stored height when the driving information is a first driving mode and the level indicates a second level; and to determine a tenth pre-stored height when the driving information is a first driving mode and the level indicates a third level.

[0057] In one possible implementation, the determining module is further configured to determine the pre-stored height based on the user identifier; or, based on a first occupancy state; or, based on a second occupancy state; or, based on driving information.

[0058] In one possible implementation, the determining module is further configured to determine the pre-stored height based on the user identifier and the first occupancy status, or, based on the user identifier and the second occupancy status.

[0059] In one possible implementation, the determining module is further configured to determine the pre-stored height based on the user identifier and driving information; or, based on the first occupancy status and driving information; or, based on the second occupancy status and driving information.

[0060] In one possible implementation, the first driving mode is an intelligent driving mode.

[0061] In one possible implementation, the device further includes an update module for updating the pre-stored height corresponding to the status information based on the target height.

[0062] In one possible implementation, the first seat is the driver's seat, the second seat is the passenger seat, and the target armrest is positioned between the driver's seat and the passenger seat.

[0063] A third aspect of this application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, causes a computer device to perform the first aspect described above and any possible implementation thereof.

[0064] A fourth aspect of this application provides a computer program product comprising code that, when executed, causes a computer device to perform the first aspect described above and any possible implementation thereof.

[0065] The fifth aspect of this application provides a computer device including a processor coupled to at least one memory, the processor being configured to read a computer program stored in the at least one memory, causing the computer device to execute the first aspect described above and any possible implementation thereof.

[0066] The technical effects of the second to fifth aspects can be found in the first aspect or the technical effects of different possible implementations of the first aspect, and will not be repeated here. Attached Figure Description

[0067] Figure 1 A schematic diagram of a control system is shown; Figure 2 A schematic diagram of an example lifting structure for a handrail is shown; Figure 3 A flowchart illustrating a method for adjusting a seat armrest is shown. Figure 4 A schematic diagram illustrating an example of an armrest adjustment method is shown; Figure 5 A schematic diagram showing the positional relationship between a target armrest and a seat is provided. Figure 6 A schematic block diagram of one embodiment of the seat armrest adjustment device provided in this application; Figure 7 A schematic block diagram of an embodiment of the computer device provided in this application; Figure 8 This application provides a schematic diagram of one embodiment of a chip system. Detailed Implementation

[0068] The technical solutions of the embodiments of this application will be described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0069] The terms "first," "second," etc., used 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 terms are interchangeable where appropriate; this is merely a way of distinguishing objects with the same attributes in the description of embodiments of this application. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion, so that a process, method, system, product, or apparatus that comprises a series of elements is not necessarily limited to those elements, but may include other elements not explicitly listed or inherent to such processes, methods, products, or apparatus. References to "embodiment" herein mean that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0070] It should be noted that, in this application, the terms "exemplary" or "for example" are used to indicate that something is being described as an example, illustration, or illustration. Any embodiment or design described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or design solutions. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0071] The following is for reference. Figure 1 The control system is described.

[0072] Figure 1 A schematic diagram of a control system is shown.

[0073] like Figure 1 As shown, the control system receives status information or adjustment commands, and then uses these information or commands to further control the drive module, thereby adjusting the height of the armrest (not shown in the figure). It can be understood that the control system here refers to the vehicle's central control unit. Alternatively, the control system can adjust the armrest height using received adjustment commands. In one example, the adjustment command could be a command received based on user voice input. In another example, the adjustment command could be a command received by the user by triggering a corresponding physical or software component. This is merely exemplary and not restrictive. In practice, adjustment commands can be received in any reasonable manner.

[0074] For example, the drive module could be a Hall motor. This is to be understood as merely exemplary and not limiting. In practice, the drive module could be any device capable of driving the handrail's lifting and lowering.

[0075] For example, status information may include user identification, seat occupancy status, physical button / voice commands, intelligent driving mode, etc. This is merely exemplary and not restrictive.

[0076] User identification refers to information that can identify a user. Examples include user-associated identifiers and user identity identifiers. User identification can be obtained through any reasonable means. In one example, user identification refers to a user identifier, which can be obtained by receiving the user's login identifier in the vehicle system. In another example, user identification is a user identity identifier, which can be obtained through various methods such as facial recognition and fingerprint recognition. It should be understood that this is merely exemplary and not restrictive.

[0077] Seat occupancy status refers to whether the seat is occupied by a user. In this embodiment, we typically only focus on the seat occupancy status related to the armrest. For example, if the armrest is located between the first and second seats, then the seat occupancy status needs to consider the occupancy status of the first and second seats. Similarly, if the armrest is located next to the first seat, then the seat occupancy status needs to consider the occupancy status of the first seat. And if the armrest is located next to the second seat, then the seat occupancy status needs to consider the occupancy status of the second seat. This is merely exemplary and not restrictive.

[0078] Driving information refers to driving modes and levels. For example, driving modes can include intelligent driving modes and non-intelligent driving modes. Furthermore, within intelligent driving modes, intelligent driving levels can also be distinguished.

[0079] In one example, the intelligent driving levels may include L2, L3, L4, etc. It should be understood that this is merely exemplary and not restrictive. The following provides further explanation of these intelligent driving levels.

[0080] Level 2 is a combined driving assistance system, meaning the system simultaneously controls lateral (steering) and longitudinal (acceleration / deceleration) directions, such as highway cruise assist and city NOA. At this level of intelligent driving, the system can follow the car in front, change lanes, and stay in the center of the road. However, the system is only responsible for operation; environmental monitoring and takeover responsibility still lie with the driver. The user needs to constantly pay attention to the road and be ready to take over at any time.

[0081] Level 3 is conditional automated driving, meaning that within a limited designed operating scenario (such as a closed highway), the system can fully execute all dynamic driving tasks (including vehicle control and environmental perception). At this level, the user does not need to continuously monitor the road. However, the user must take over the vehicle promptly when the system issues a takeover request. At this level, when the vehicle exceeds the scenario boundaries, human driving is required.

[0082] Level 4 (L4) is highly automated driving, meaning the system completes all driving tasks within its defined design operating range. In case of anomalies, the system takes over with minimal risk, requiring no user intervention. Examples include driverless shuttle buses in industrial parks and robotaxis operating within designated areas. Outside of the designed scenario, the system will safely pull over without requiring user intervention.

[0083] The following is for reference. Figure 2 An example of a lifting armrest structure is described. It is understood that... Figure 2 This is just one example of an armrest lifting mechanism. In reality, the armrest lifting mechanism can be any other reasonable structure.

[0084] Figure 2 A schematic diagram of an example lifting structure for a handrail is shown.

[0085] like Figure 2 As shown, this example architecture includes a base housing and a target armrest. Specifically, the base housing includes component A1, component A2, component B1, component B2, and a drive module.

[0086] The target handrail is an actuator driven by the drive module.

[0087] The base housing serves as the foundation for the entire vehicle's interior, housing the drive module and other components. The following provides further details about the components within the base housing.

[0088] Components A1 and A2 are two lifting columns (guide rods) arranged symmetrically on the left and right, connecting the handrail body to the slider inside the base, driving the target handrail to move vertically up and down.

[0089] Components B1 and B2 are sliding limit blocks, which are limit sliders at the lower end of the column. They slide up and down on the internal track of the base to limit the lifting stroke of the handrail and prevent it from coming off the base housing.

[0090] The drive module is the power source for raising and lowering the target handrail. It controls the vertical movement of the handrail by outputting linear driving force, or in other words, its up-and-down adjustment. For example, the drive module may include a motor, a lead screw / gear transmission assembly, etc. This is merely exemplary and not limiting.

[0091] The following is for reference. Figure 3 The method for adjusting the seat armrests is explained.

[0092] Figure 3 A flowchart illustrating a method for adjusting a seat armrest is shown. The method includes: S301. Determine the pre-stored height corresponding to the status information.

[0093] In other words, the pre-stored height is stored in the corresponding status information. Therefore, the corresponding pre-stored height can be determined through the status information.

[0094] The status information includes at least one of the following: user identifier, seat occupancy status of the target vehicle, and driving information.

[0095] It is understood that the seat in the target vehicle usually refers to the seat associated with the target armrest. In other words, the seat occupancy status refers to the occupancy status of the seat associated with the target armrest. For example, the target armrest may be located on one side of a seat and only associated with that seat, or the target armrest may be located between two adjacent seats.

[0096] In one possible implementation, the seats include a first seat and a second seat. The first seat and the second seat are any two adjacent seats inside the vehicle. Optionally, the target armrest can also be the armrest between the first seat and the second seat. Optionally, the target armrest can also be the armrest on one side of the first seat, and is only related to the first seat. Optionally, the target armrest can be the armrest on one side of the second seat, and is only related to the second seat. Furthermore, the positions of the two seats can also be further divided into front row and rear row, where the front row refers to the row corresponding to the driver's seat and the front passenger seat, and the rear row refers to the rows of seats after the front row (there may be only one row of rear rows, or there may be multiple rows of rear rows).

[0097] The following explains the cases where the first and second seats are front seats.

[0098] In one possible implementation, the first seat is a driver's seat, the second seat is a front passenger seat, and the target armrest is positioned between the driver's seat and the front passenger seat. In this possible implementation, the target armrest is a central armrest between the driver's seat and the front passenger seat. Optionally, the target armrest can also be an armrest on the driver's side and is only related to the driver's seat. Optionally, the target armrest can also be an armrest on the front passenger side and is only related to the front passenger seat.

[0099] For example, since the driver's seat and passenger seat are in the front row and have a high degree of relevance to driving, the pre-stored height can be stored based on driving information (including driving mode and level) in the status information, whether it is an armrest between the driver's seat and passenger seat, an armrest on the driver's side, or an armrest on the passenger side. Furthermore, the pre-stored height can also be stored by combining driving information with user identification or seat occupancy status, as in implementation methods two and three below. Optionally, in these cases, the pre-stored height can also be stored by combining user identification and seat occupancy status, as in implementation method one below. Optionally, in these cases, the pre-stored height can also be stored by combining driving information, user identification, and seat occupancy status, as in implementation method four below.

[0100] The following explains the situation where the first and second seats are rear seats.

[0101] Optionally, since the rear seats have a low correlation with vehicle driving, the corresponding pre-stored height can be stored by combining the user identifier and the seat occupancy status, as shown in Implementation Method 1 below. Optionally, in this case, the corresponding pre-stored height can also be stored by combining driving information and the user identifier / seat occupancy status, as shown in Implementation Method 2 or 3 below. Optionally, in this case, the corresponding pre-stored height can also be stored by combining driving information, the user identifier, and the seat occupancy status, as shown in Implementation Method 4 below.

[0102] In one possible implementation, the first seat corresponds to a first occupancy state, and the second seat corresponds to a second occupancy state. In another possible implementation, the pre-stored height is determined based on at least one of the user identifier, the first occupancy state, the second occupancy state, and driving information.

[0103] The driving information stored may differ depending on the driving status. The following section further explains the correspondence between driving status information and pre-stored altitude.

[0104] For example, the user identifier can be account information, identity identifier, etc. For example, the first occupancy status and the second occupancy status can include two states: occupied and unoccupied.

[0105] For example, driving information may include driving mode and level. Further, driving mode may include intelligent driving mode (hereinafter referred to as intelligent driving mode) or non-intelligent driving mode (hereinafter referred to as non-intelligent driving mode). Even further, intelligent driving mode may further distinguish intelligent driving levels, such as L2, L3, L4, etc. It should be understood that this is merely exemplary and not restrictive.

[0106] Implementation Method 1: Determine the pre-stored height based on user ID and seat occupancy status. Different combinations of user IDs and different occupancy statuses can determine their corresponding pre-stored heights. That is, the embodiment corresponding to Implementation Method 1 considers both user ID and seat occupancy status simultaneously. Implementation Method 1 includes the following embodiments one through six.

[0107] If the target armrest is located between the first seat and the second seat and the first occupancy state and the second occupancy state are not considered simultaneously, or if the target armrest is on one side of the first seat and is only related to the first seat, the following embodiment can be implemented.

[0108] In one possible implementation, the pre-stored height is determined based on the user identifier and the first occupancy status.

[0109] Example 1: When the user identifier P1 is indicated and the first occupancy status is occupied, the pre-stored height indicator H1 is determined. Here, P1 corresponds to the third identifier in the embodiments of this application.

[0110] The following embodiment two can be implemented when the target armrest is located between the first seat and the second seat and the first occupancy state and the second occupancy state are not considered at the same time, or when the target armrest is on one side of the second seat and is only related to the second seat.

[0111] In one possible implementation, the pre-stored height is determined based on the user identifier and the second occupancy status.

[0112] Example 2: When the user identifier P2 is indicated and the second occupancy status is "occupied", the pre-stored height indicator H2 is determined. Here, P2 corresponds to the fourth identifier in the embodiments of this application.

[0113] It is understood that if Embodiment Two is implemented under the condition that "the target armrest is between the first seat and the second seat and the first occupancy state and the second occupancy state are not considered simultaneously," and the first seat is the driver's seat and the second seat is the passenger seat, then Embodiment Two has a prerequisite that the first occupancy state is an unoccupied state. That is to say, between the driver's seat and the passenger seat, the occupancy state of the driver's seat can be prioritized. It is understood that this is merely exemplary and not restrictive.

[0114] Since the height of the target armrest is usually only considered in relation to the seat, if both the first and second occupancy states are considered simultaneously, the target armrest is typically positioned between the first and second seats. However, it is understandable that even if the target armrest is positioned between two seats, it is possible to choose not to consider both the first and second occupancy states simultaneously (e.g., choosing one as the preferred option).

[0115] The following describes an embodiment of the target armrest located between the first seat and the second seat, taking into account both the first occupancy state and the second occupancy state.

[0116] Example 3: When the user identifier indicator P3, the first occupancy status is occupied, and the second occupancy status is occupied, the pre-stored height indicator H3 is determined.

[0117] Example 4: When the user identifier indicator P4 is in the case that the first occupancy state is unoccupied and the second occupancy state is occupied, the pre-stored height indicator H4 is determined.

[0118] Example 5: When the user identifier indicator P5 is in use, the first occupancy status is occupied, and the second occupancy status is unoccupied, the pre-stored height indicator H5 is determined.

[0119] Example 6: When the user identifier indicator P6 is present, the first occupancy state is unoccupied, and the second occupancy state is unoccupied, the pre-stored height indicator H6 is determined.

[0120] It is understood that any two of the user identifiers P1, P2, P3, P4, P5, and P6 can be the same or different. In other words, the different subscripts are only used to distinguish user identifiers identified in different embodiments, and do not mean that each user identifier necessarily corresponds to a different user.

[0121] It is understood that the values ​​of any two of the above-mentioned pre-stored heights H1, H2, H3, H4, H5, and H6 can be the same or different. In other words, the different subscripts are only used to distinguish the pre-stored heights corresponding to different embodiments, and do not mean that the value of each pre-stored height must be different.

[0122] Implementation Method Two: Determine the pre-stored height based on user identifier and driving information. Different combinations of user identifiers and driving information correspond to different pre-stored heights. That is, the implementation method two considers both user identifier and driving information simultaneously.

[0123] Driving information may include driving modes. Examples of different user identities and driving modes are described below.

[0124] Example 7: When the user identification indicator P7 and the driving mode indicator is the first driving mode, the pre-stored height indicator H7 is determined.

[0125] Example 8: When the user identification indicator P8 and the driving mode indicator is the second driving mode, the pre-stored height indicator H8 is determined.

[0126] It is understood that this only illustrates two example driving modes. In reality, if there are more driving modes, the corresponding preset height can be determined under these more driving modes. The same principle applies to the embodiments involving driving modes below. That is to say, the first and second driving modes here are only examples of driving modes used to illustrate that different driving modes can determine their corresponding preset heights, and do not mean that there are necessarily only two driving modes.

[0127] Furthermore, in the first driving mode, the intelligent driving level (or simply level) can be further distinguished, such as Level 1, Level 2, and Level 3. For example, the first driving mode can be the intelligent driving mode. For example, Level 1 can be L2 in the intelligent driving level, Level 2 can be L3, and Level 3 can be L4. For detailed explanations of L2, L3, and L4, please refer to... Figure 1 The relevant descriptions in the text will not be elaborated upon here.

[0128] Example 9: When the user identifier indicates P9, the driving mode indicates the first driving mode, and the level indicates the first level, the pre-stored altitude indicator H9 is determined.

[0129] Example 10: In the user identification instruction P 10 When the driving mode indicator is set to the first driving mode and the level indicator is set to the second level, the preset altitude indicator H is determined. 10 .

[0130] Example 11: In the user identifier indication P 11 When the driving mode indicator is set to first driving mode and the level indicator is set to third level, the preset altitude indicator H is determined. 11 .

[0131] Similarly, the user identifiers P7, P8, P9, and P... 10 P 11 Any two identifiers can be the same or different. In other words, different subscripts are only used to distinguish user identifiers identified in different embodiments, and do not mean that each user identifier necessarily corresponds to a different user.

[0132] Similarly, the above pre-stored heights H7, H8, H9, and H... 10 H 11 The values ​​of any two heights can be the same or different. In other words, different subscripts are only used to distinguish the pre-stored heights corresponding to different embodiments, and do not mean that the values ​​of each pre-stored height must be different.

[0133] Implementation Method 3: Determine the pre-stored height based on the seat occupancy status and driving information. Different combinations of seat occupancy status and driving information correspond to different pre-stored heights. That is, the implementation method 3 considers both seat occupancy status and driving information simultaneously.

[0134] Under this implementation method, it can be further divided into considering only the first occupancy state, considering only the second occupancy state, or considering both the first and second occupancy states.

[0135] In one possible implementation, the pre-stored height is determined based on the first occupancy state and driving information.

[0136] Driving information can include driving status, which includes a first driving mode and a second driving mode.

[0137] Example 12: When the first occupancy status indicator is occupied and the driving mode indicator is in the first driving mode, determine the pre-stored height indicator H. 12 .

[0138] Example 13: When the first occupancy status indicator is unoccupied and the driving mode indicator is the first driving mode, determine the pre-stored height indicator H. 13 .

[0139] Example 14: When the first occupancy status indicator is occupied and the driving mode indicator is the second driving mode, determine the pre-stored height indicator H. 14 .

[0140] Example 15: When the first occupancy status indicator is unoccupied and the driving mode indicator is the second driving mode, determine the pre-stored height indicator H. 15 .

[0141] Furthermore, in the first driving mode, the corresponding pre-stored height can be determined through different levels. For example, the levels can include a first level, a second level, and a third level. It can be understood that the first, second, and third levels here are just examples; in reality, more levels can be defined, and the corresponding pre-stored height can be determined based on these more levels. The following examples involving levels follow the same principle.

[0142] Example 16: When the first occupancy status indicator is occupied, the driving mode indicator is the first driving mode, and the level is the first level, determine the pre-stored height indicator H. 16 .

[0143] Example 17: When the first occupancy status indicator is occupied, the driving mode indicator is the first driving mode, and the level is the second level, determine the pre-stored height indicator H. 17 .

[0144] Example 18: When the first occupancy status indicator is occupied, the driving mode indicator is the first driving mode, and the level is the third level, determine the pre-stored height indicator H. 18 .

[0145] Example 19: When the first occupancy status indicator is unoccupied, the driving mode indicator is the first driving mode, and the level is the first level, determine the pre-stored height indicator H. 19 .

[0146] Example 20: When the first occupancy status indicator is unoccupied, the driving mode indicator is the first driving mode, and the level is the second level, determine the pre-stored height indicator H. 20 .

[0147] Example 21: When the first occupancy status indicator is unoccupied, the driving mode indicator is the first driving mode, and the level is the third level, determine the pre-stored height indicator H. 21 .

[0148] Similarly, the above pre-stored heights H 12 H 13 H 14 H 15 H 16 H 17 H 18 H 19 H 20 and H 21 The values ​​of any two heights can be the same or different. In other words, different subscripts are only used to distinguish the pre-stored heights corresponding to different embodiments, and do not mean that the values ​​of each pre-stored height must be different.

[0149] In one possible implementation, the pre-stored height is determined based on the second occupancy state and driving information. Here, the embodiment considering only the second occupancy state can also refer to the embodiments listed above that only consider the first occupancy state (embodiments 12 to 21), which will not be listed here again.

[0150] The following describes an embodiment that considers both the first occupancy state and the second occupancy state.

[0151] Example 22: When the first occupancy status indicator is occupied, the second occupancy status indicator is occupied, and the driving mode indicator is the first driving mode, determine the pre-stored height indicator H. 22 .

[0152] Example 23: When the first occupancy status indicates that the vehicle is occupied, the second occupancy status indicates that the vehicle is not occupied, and the driving mode indicates the first driving mode, determine the pre-stored height indicator H. 23 .

[0153] Example 24: When the first occupancy status indicates unoccupied, the second occupancy status indicates occupied, and the driving mode indicates the first driving mode, determine the pre-stored height indicator H. 24 .

[0154] Since the adjustment of the target handrail height is primarily to provide users with a height that meets their needs and ensures user comfort in different scenarios, there is no need to adjust the target handrail when it is not in use. Therefore, the scenario where both the first and second occupied states are unoccupied is not considered here.

[0155] For cases where the driving mode is the second driving mode, please refer to the above examples corresponding to the first driving mode (Examples 22 to 24), which will not be listed here.

[0156] Furthermore, in the first driving mode, different levels can be distinguished to determine the pre-stored height. This can be referred to in the relevant embodiments above, and will not be listed one by one.

[0157] Similarly, the above pre-stored heights H 22 H 23 H 24 The values ​​of any two heights can be the same or different. In other words, different subscripts are only used to distinguish the pre-stored heights corresponding to different embodiments, and do not mean that the values ​​of each pre-stored height must be different.

[0158] Implementation Method 4: Determine the pre-stored height based on user identifier, seat occupancy status, and driving information. Different combinations of user identifiers, seat occupancy status, and driving information correspond to different pre-stored heights. In other words, the implementation method 4 simultaneously considers these three pieces of information: user identifier, seat occupancy status, and driving information.

[0159] Example 25: When the user identifier is P 12 In the case of the first occupancy status indicator being occupied, the second occupancy status indicator being occupied, and the driving mode indicator being the first driving mode, the pre-stored height indicator H is determined. 25 .

[0160] Example 26: When the user identifier is P 13 If the first occupancy status indicates that the vehicle is occupied, the second occupancy status indicates that the vehicle is not occupied, and the driving mode indicates the first driving mode, then the pre-stored height indicator H is determined. 26 .

[0161] Example 27: When the user identifier is P 14If the first occupancy status indicates no occupancy, the second occupancy status indicates occupancy, and the driving mode indicates the first driving mode, then determine the pre-stored height indicator H. 27 .

[0162] For cases where the driving mode is the second driving mode, please refer to the above examples corresponding to the first driving mode (Examples 25 to 27), which will not be listed here one by one.

[0163] Furthermore, different levels are distinguished in the first driving mode.

[0164] Example 28: When the user identifier is P 15 If the first occupancy status indicator is occupied, the second occupancy status indicator is occupied, the driving mode indicator is the first driving mode, and the level indicator is the first level, then the pre-stored height indicator H is determined. 28 .

[0165] Example 29: When the user identifier is P 16 If the first occupancy status indicates that the vehicle is occupied, the second occupancy status indicates that the vehicle is not occupied, the driving mode indicates the first driving mode, and the level indicates the second level, then the pre-stored height indicator H is determined. 29 .

[0166] Example 30: When the user identifier is P 17 If the first occupancy status indicates no occupancy, the second occupancy status indicates occupancy, the driving mode indicates the first driving mode, and the level indicates the third level, then the pre-stored height indicator H is determined. 30 .

[0167] Similarly, the user identifiers P above... 12 P 13 P 14 P 15 P 16 P 17 Any two identifiers can be the same or different. In other words, different subscripts are only used to distinguish user identifiers identified in different embodiments, and do not mean that each user identifier necessarily corresponds to a different user.

[0168] Similarly, the above pre-stored heights H 25 H 26 H 27 The values ​​of any two heights can be the same or different. In other words, different subscripts are only used to distinguish the pre-stored heights corresponding to different embodiments, and do not mean that the values ​​of each pre-stored height must be different.

[0169] S302. Adjust the target handrail to the preset height.

[0170] The target armrest is associated with the seat.

[0171] For example, the height of the target handrail is adjusted based on a pre-stored height. This adjustment method is typically performed without user input. If the status information changes, S301 and S302 can be executed again based on the changed status information to adjust the target handrail to the pre-stored height corresponding to the changed status information.

[0172] After the user issues an adjustment command, the height is adjusted to the specified height according to the user's adjustment command, that is, S303 is executed.

[0173] S303. Upon receiving an adjustment instruction from the user, adjust the target handrail from the preset height to the target height indicated by the adjustment instruction.

[0174] It's understandable that the adjusted target height here is the specified height indicated in the adjustment command. The target height is usually a height value selected by the user based on current needs.

[0175] The following is a reference. Figure 4 An example of a handrail adjustment method is described.

[0176] Figure 4 A schematic diagram illustrating an example of an armrest adjustment method is shown.

[0177] Understandable, Figure 4 In the method shown, user identification is described using account information as an example. In reality, account information can be replaced with any information that can identify different users, such as user identity information. Similarly, the example deployment position of the target armrest is shown with the first seat and the second seat in between, where the first seat is the driver's seat and the second seat is the front passenger seat.

[0178] S401. Obtain account information. Here, account information refers to whether the account is logged in. Therefore, account information includes two types of information: account login information or account not logged in.

[0179] Typically, account login information includes identifiers to distinguish different user accounts. Therefore, if a user is already logged into an account, multiple pre-stored heights can be retrieved for that account. These pre-stored heights can correspond to combinations of different driving modes and seat occupancy states.

[0180] However, when the account is not logged in, only one identifier can usually be recognized. In this case, the pre-stored height is not related to any account information and can be understood as local storage information. That is to say, in this case, some commonly used pre-stored heights can also be stored, but these pre-stored heights are not bound to account information.

[0181] S402, Determine the positional relationship between the target armrest and the seat. Because... Figure 4 In the example, the seats include the driver's seat and the front passenger seat. Therefore, the positional relationship between the target armrest and the seats can include the target armrest being on the side of the driver's seat and only related to the driver's seat (hereinafter referred to as position A, see reference). Figure 5 (a) in the text, or, the target armrest is on the side of the passenger seat and is only related to the passenger seat (hereinafter referred to as position B, see reference). Figure 5 (b) of the above, or, the target armrest is between two adjacent driver's and passenger's seats (hereinafter referred to as position C, see reference). Figure 5 (c) in the middle.

[0182] The next step is to obtain the seat occupancy status. For a given seat, there are two occupancy statuses: occupied and unoccupied. In this example, the driver's seat can be either occupied or unoccupied. Similarly, the front passenger seat can also be either occupied or unoccupied. Since the user in the driver's seat typically performs the driving tasks, in one example, the occupancy status of the front passenger seat can be disregarded if the driver's seat is already occupied.

[0183] If the target armrest is in position C and the driver's seat is occupied, or if the target armrest is in position A, then S403 is executed after S402 is completed.

[0184] S403. Based on the occupancy status of the driver's seat and driving information, determine the pre-stored height.

[0185] With the target armrest located at position C and the driver's seat occupied, different driving information corresponds to different preset heights. Driving information can include driving mode and level; driving modes include intelligent driving mode and non-intelligent driving mode. Intelligent driving mode can be further divided into different intelligent driving levels, such as L2, L3, and L4.

[0186] Given that the user identifier, the target armrest is at position C, and the driver's seat is already occupied, the following scenarios apply: L2 intelligent driving level corresponds to the pre-stored height D, L3 intelligent driving level corresponds to the pre-stored height E, L4 intelligent driving level corresponds to the pre-stored height F, and non-intelligent driving mode corresponds to the pre-stored height G.

[0187] Alternatively, if the target armrest is in position C and the driver's seat is unoccupied, or if the target armrest is in position B, then S404 is executed after S402 is completed.

[0188] S404. Based on the occupancy status of the front passenger seat and driving information, determine the pre-stored height.

[0189] When the target armrest is at position C and the driver's seat is unoccupied, or when the target armrest is at position B, different driving information corresponds to different preset heights. Furthermore, driving information can include driving mode and level. Driving modes include intelligent driving mode and non-intelligent driving mode. Intelligent driving mode can be further divided into different intelligent driving levels, such as L2, L3, and L4.

[0190] Once the user identifier and the co-pilot's occupancy status have been determined, the following scenarios apply: L2 intelligent driving level corresponds to the pre-stored height H, L3 intelligent driving level corresponds to the pre-stored height I, L4 intelligent driving level corresponds to the pre-stored height J, and non-intelligent driving mode corresponds to the pre-stored height K.

[0191] S405. Adjust the target armrest to the preset height. It can be understood that S405 can be executed without receiving an adjustment command from the user. In other words, before receiving an adjustment command, the target armrest can be adjusted based on the preset height corresponding to the current state information. After receiving an adjustment command, the target armrest is adjusted based on the adjustment command, i.e., S406 is executed.

[0192] S406. Based on the adjustment command, adjust the target handrail to the target height.

[0193] Optionally, the target height can be updated to the pre-stored height corresponding to the status information. That is, after adjustment based on the adjustment command, the target height can be updated to the pre-stored height under this status information. Subsequently, when this status information is recognized, the target handrail can be adjusted to the target height.

[0194] The following is for reference. Figure 5 A diagram illustrating the positional relationship between the target armrest and the seat is provided.

[0195] Figure 5 This diagram illustrates the positional relationship between a target armrest and a seat.

[0196] The first and second seats shown in the diagram are two adjacent seats in the vehicle. It can be understood that (a)-(c) are simplified diagrams used only to illustrate the positional relationship between the first seat, the second seat, and the target armrest.

[0197] Figure 5 The position shown in (a) is where the target armrest is on one side of the first seat and is only related to the first seat. Under this positional relationship, if we consider the occupancy state of the seats, we only need to consider the first occupancy state of the first seat.

[0198] Figure 5The position shown in (b) is where the target armrest is on one side of the second seat and is only related to the second seat. Under this positional relationship, if we consider the occupancy state of the seats, we only need to consider the second occupancy state of the second seat.

[0199] Figure 5 The position shown in (c) is the target armrest between the first seat and the second seat. In this positional relationship, if the occupancy status of the seats is taken into account, only at least one of the first occupancy status of the first seat and the second occupancy status of the second seat can be considered.

[0200] The following is for reference. Figure 6 The seat armrest adjustment device provided in this application is described.

[0201] Figure 6 This is a schematic block diagram illustrating one embodiment of the seat armrest adjustment device provided in this application. Specifically, the seat armrest adjustment device 600 includes a determining module 601, a first adjustment module 602, and a second adjustment module 603.

[0202] The determination module 601 is used to determine the pre-stored height corresponding to the status information, which includes at least one of the following: user identifier, seat occupancy status of the target vehicle, and driving information. The first adjustment module 602 is used to adjust the target armrest to a preset height, and the target armrest is associated with the seat; The second adjustment module 603 is used to adjust the target handrail from the preset height to the target height indicated by the adjustment command when the user receives an adjustment command.

[0203] In one possible implementation, the seat includes a first seat and a second seat, the first seat corresponds to a first occupancy state, and the second seat corresponds to a second occupancy state. The determining module is further used to determine the pre-stored height based on at least one of the user identifier, the first occupancy state, the second occupancy state, and driving information.

[0204] In one possible implementation, the determining module is further configured to determine the pre-stored height based on driving information when the user identifier indicates the first identifier and the first occupancy status is occupied.

[0205] In one possible implementation, the driving information includes a driving mode, and the determining module is further configured to determine a pre-stored height indicator as a first pre-stored height when the driving information is a first driving mode; and to determine a pre-stored height indicator as a second pre-stored height when the driving information is a second driving mode.

[0206] In one possible implementation, the driving information also includes a level, which is associated with a first driving mode. The determining module is further configured to determine a third pre-stored height when the driving information is the first driving mode and the level indicates a first level; determine a fourth pre-stored height when the driving information is the first driving mode and the level indicates a second level, with the second level being higher than the first level; and determine a fifth pre-stored height when the driving information is the first driving mode and the level indicates a third level, with the third level being higher than the second level.

[0207] In one possible implementation, the determining module is further configured to determine the pre-stored height based on driving information when the user identifier indicates the second identifier and the second occupancy status is occupied.

[0208] In one possible implementation, the driving information includes a driving mode, and the determining module is further configured to determine a sixth pre-stored height indicator when the driving information is a first driving mode; and to determine a seventh pre-stored height indicator when the driving information is a second driving mode.

[0209] In one possible implementation, the driving information also includes a level, which is associated with a first driving mode. The determining module is further configured to determine an eighth pre-stored height when the driving information is a first driving mode and the level indicates a first level; to determine a ninth pre-stored height when the driving information is a first driving mode and the level indicates a second level; and to determine a tenth pre-stored height when the driving information is a first driving mode and the level indicates a third level.

[0210] In one possible implementation, the determining module is further configured to determine the pre-stored height based on the user identifier; or, based on a first occupancy state; or, based on a second occupancy state; or, based on driving information.

[0211] In one possible implementation, the determining module is further configured to determine the pre-stored height based on the user identifier and the first occupancy state, or, based on the user identifier and the second occupancy state.

[0212] In one possible implementation, the determining module is further configured to determine the pre-stored height based on the user identifier and driving information; or, based on the first occupancy status and driving information; or, based on the second occupancy status and driving information.

[0213] In one possible implementation, the first driving mode is an intelligent driving mode.

[0214] In one possible implementation, the device further includes an update module for updating the pre-stored height corresponding to the status information based on the target height.

[0215] In one possible implementation, the first seat is the driver's seat, the second seat is the passenger seat, and the target armrest is positioned between the driver's seat and the passenger seat.

[0216] The determination module 601 can be implemented through software or hardware. The seat armrest adjustment device 600 can also combine with other hardware resources to realize the functions of the above modules. For example, the functions of the determination module 601 can be realized through the computing resources of edge devices (such as industrial gateways or smart terminals equipped with TEE) (such as GPU memory usage or CPU load), local TEE instances, or TEE instances in the cloud.

[0217] For example, the implementation of module 601 will be described below. Similarly, the implementation of the first adjustment module 602 and the second adjustment module 603 can refer to the implementation of module 601.

[0218] As an example of a software functional unit, module 601 may include code running on a computing instance. The computing instance may include at least one of a physical host (computing device), a virtual machine, or a container. Further, the aforementioned computing instance may be one or more. For example, module 601 may include code running on multiple hosts / virtual machines / containers. It should be noted that the multiple hosts / virtual machines / containers used to run the code may be distributed within the same region or in different regions. Further, the multiple hosts / virtual machines / containers used to run the code may be distributed within the same availability zone (AZ) or in different AZs, each AZ including one or more geographically proximate data centers. Typically, a region may include multiple AZs.

[0219] Similarly, multiple hosts / virtual machines / containers used to run this code can be distributed within the same Virtual Private Cloud (VPC) or across multiple VPCs. Typically, a VPC is set up within a region. Communication between two VPCs within the same region, as well as between VPCs in different regions, requires a communication gateway to be set up within each VPC to enable interconnection between VPCs.

[0220] As an example of a hardware functional unit, the determining module 601 may include at least one computing device, such as a terminal. Alternatively, the determining module 601 may also be a device implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD). The PLD may be implemented using a complex programmable logical device (CPLD), a field-programmable gate array (FPGA), generic array logic (GAL), or any combination thereof.

[0221] The multiple computing devices included in module 601 can be distributed in the same region or in different regions. Similarly, the multiple computing devices included in module 601 can be distributed in the same Availability Zone (AZ) or in different AZs. Likewise, the multiple computing devices included in module 601 can be distributed in the same Virtual Private Cloud (VPC) or in multiple VPCs. These multiple computing devices can be any combination of computing devices such as servers, ASICs, PLDs, CPLDs, FPGAs, and GALs.

[0222] The following is for reference. Figure 7 Example diagrams of the computer device in this application are illustrated. The computer device may be, for example, a control system. It is understood that... Figure 7 The computer device shown is an example block diagram of a possible computer device, such as a seat armrest adjustment device 600.

[0223] Figure 7This is a schematic block diagram illustrating an embodiment of the computer device provided in this application. The computer device includes at least one processor 701, a communication bus 702, a memory 703, and at least one communication interface 704. Optionally, the processor 701 is a general-purpose CPU, NP, microprocessor, or one or more integrated circuits for implementing the solutions of this application, such as application-specific integrated circuits (ASICs), programmable logic devices (PLDs), or combinations thereof. The aforementioned PLD is a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), generic array logic (GAL), or any combination thereof.

[0224] The communication bus 702 is used to transmit information between the aforementioned components. The communication bus 702 includes an address bus, a data bus, and a control bus. For ease of illustration, only one thick line is used to represent these components in the figure, but this does not imply that there is only one bus or one type of bus.

[0225] Optionally, memory 703 is read-only memory (ROM) or other types of static storage devices capable of storing static information and instructions. Alternatively, memory 703 is random access memory (RAM) or other types of dynamic storage devices capable of storing information and instructions. Alternatively, memory 703 is electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media, or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures that can be accessed by a computer, but not limited to these. Optionally, memory 703 exists independently and is connected to processor 701 via communication bus 702. Optionally, memory 703 and processor 701 are integrated together.

[0226] Communication interface 704 uses any transceiver-like device for communicating with other devices or communication networks. Communication interface 704 includes a wireless communication interface.

[0227] Optionally, the processor 701 includes one or more CPUs, such as Figure 7 CPU0 and CPU1 are shown in the diagram.

[0228] Optionally, the computer device includes multiple processors, such as Figure 7 The processors 701 and 705 shown are illustrated. Each of these processors is either a single-core processor (SCPU) or a multi-core processor (Multi-CPU). Here, a processor refers to one or more devices, circuits, and / or processing cores used to process data (such as computer program instructions).

[0229] Optionally, the memory 703 is used to store program code 706 that executes the solution of this application, and the processor 701 executes the program code 706 stored in the memory 703. That is, the computer device implements the above-described method embodiment through the processor 701 and the program code 706 in the memory 703.

[0230] The following is for reference. Figure 8 An example chip system in the control system is described.

[0231] Figure 8 This application provides a schematic diagram of one embodiment of a chip system. The chip system 800 (or processing system) includes logic circuitry 810 and an input / output interface 820.

[0232] The logic circuit 810 can be a processing circuit in the chip system 800. The logic circuit 810 can be coupled to a memory unit, calling instructions from the memory unit, enabling the chip system 800 to implement the methods and functions of the embodiments of this application. The input / output interface 820 can be an input / output circuit in the chip system 800, outputting processed information from the chip system 800, or inputting data or signaling information to be processed into the chip system 800 for processing.

[0233] Optionally, the logic circuit 810 may be implemented by one or more processors, including the one or more processors or the processing portion of the one or more processors.

[0234] Optionally, the input / output interface 820 may include transceiver circuitry, a transceiver, input / output circuitry, or a communication interface.

[0235] As one approach, the chip system 800 is used to implement the operations performed by the control system in the various method embodiments described above.

[0236] Specifically, the logic circuit 810 is used to implement the processing-related operations performed by the control system in the above method embodiment; the input / output interface 820 is used to implement the sending and / or receiving-related operations performed by the control system in the above method embodiment.

[0237] This application also provides a computer-readable storage medium storing computer instructions for implementing the methods executed by the control system in the above-described method embodiments.

[0238] For example, when the computer program is executed by the computer, it enables the computer to implement the methods executed by the control system in the various embodiments of the above methods.

[0239] This application also provides a computer program product comprising instructions which, when executed by a computer, implement the methods executed by the control system in the above-described method embodiments.

[0240] This application also provides a communication network, which includes the control system described in the above embodiments. For a description of the control system, please refer to... Figure 1 The corresponding explanations will not be elaborated upon here. Specifically, the communication network is a network used to run the control system, which is used to implement the seat armrest adjustment method. The communication network includes the control system described in the above embodiments.

[0241] This application also provides a network system, which includes a control system for implementing a method executed by the control system.

[0242] The explanations and beneficial effects of the relevant contents in any of the devices provided above can be found in the corresponding method embodiments provided above, and will not be repeated here.

[0243] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces, and the indirect coupling or communication connection of apparatus or units may be electrical, mechanical, or other forms.

[0244] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. For example, the computer can be a personal computer, a server, or a network device, etc. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state disks, SSDs). For example, the aforementioned available media include, but are not limited to, USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks, and other media capable of storing program code.

[0245] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for adjusting a seat armrest, characterized in that, The method includes: Determine the pre-stored height corresponding to the status information, wherein the status information includes at least one of the following: user identifier, seat occupancy status of the target vehicle, and driving information; Adjust the target armrest to the preset height, and the target armrest is associated with the seat; Upon receiving an adjustment instruction from the user, the target handrail is adjusted from the preset height to the target height indicated by the adjustment instruction.

2. The method according to claim 1, characterized in that, The seats include a first seat and a second seat, the first seat corresponds to a first occupancy state, and the second seat corresponds to a second occupancy state. Determining the pre-stored height corresponding to the state information includes: The pre-stored height is determined based on at least one of the user identifier, the first occupancy status, the second occupancy status, and the driving information.

3. The method according to claim 2, characterized in that, Determining the pre-stored height based on the user identifier, the first occupancy status, and the driving information includes: If the user identifier indicates the first identifier and the first occupancy status is occupied, the pre-stored height is determined based on the driving information.

4. The method according to claim 3, characterized in that, The driving information includes the driving mode, and determining the pre-stored altitude based on the driving information includes: When the driving information is a first driving mode, the pre-stored height is determined to be a first pre-stored height; If the driving information indicates a second driving mode, the pre-stored height is determined to be a second pre-stored height.

5. The method according to claim 4, characterized in that, The driving information also includes a level, which is associated with the first driving mode. Determining the pre-stored altitude based on the driving information includes: If the driving information is a first driving mode and the level indicator is a first level, then the pre-stored height indicator is determined to be a third pre-stored height; When the driving information is a first driving mode and the level indicator is a second level, it is determined that the pre-stored height indicator is a fourth pre-stored height, and the second level is higher than the first level; If the driving information is a first driving mode and the level indicator is a third level, then the pre-stored height indicator is determined to be a fifth pre-stored height, where the third level is higher than the second level.

6. The method according to claim 2, characterized in that, Determining the pre-stored height based on the user identifier, the second occupancy status, and the driving information includes: If the user identifier indicates the second identifier and the second occupancy status is occupied, the pre-stored height is determined based on the driving information.

7. The method according to claim 6, characterized in that, The driving information includes the driving mode, and determining the pre-stored altitude based on the driving information includes: If the driving information is in the first driving mode, determine the sixth pre-stored height indicator; If the driving information is in the second driving mode, the pre-stored height indicator is determined to be the seventh pre-stored height.

8. The method according to claim 7, characterized in that, The driving information also includes a level, which is associated with the first driving mode. Determining the pre-stored altitude based on the driving information includes: If the driving information is a first driving mode and the level indicator is a first level, then the pre-stored height indicator is determined to be an eighth pre-stored height; If the driving information is a first driving mode and the level indication is a second level, then the pre-stored height indication is determined to be a ninth pre-stored height; If the driving information is in the first driving mode and the level indication is the third level, then the pre-stored altitude indication is determined to be the tenth pre-stored altitude.

9. The method according to claim 2, characterized in that, Determining the pre-stored height based on at least one of the user identifier, the first occupancy status, the second occupancy status, and the driving information includes: The pre-stored height is determined based on the user identifier; or, Based on the first occupancy status, determine the pre-stored height; or, The pre-stored height is determined based on the second occupancy status; or, Based on the driving information, the pre-stored height is determined.

10. The method according to claim 2, characterized in that, Determining the pre-stored height based on at least one of the user identifier, the first occupancy status, the second occupancy status, and the driving information includes: Based on the user identifier and the first occupancy status, determine the pre-stored height, or... The pre-stored height is determined based on the user identifier and the second occupancy status.

11. The method according to claim 2, characterized in that, Determining the pre-stored height based on at least one of the user identifier, the first occupancy status, the second occupancy status, and the driving information includes: The pre-stored height is determined based on the user identifier and the driving information; or, Based on the first occupancy status and the driving information, the pre-stored height is determined; or, The pre-stored height is determined based on the second occupancy status and the driving information.

12. The method according to claim 4, 5, 7 or 8, characterized in that, The first driving mode is the intelligent driving mode.

13. The method according to any one of claims 1-12, characterized in that, The method further includes: The pre-stored height corresponding to the status information is updated based on the target height.

14. The method according to any one of claims 2-13, characterized in that, The first seat is the driver's seat, the second seat is the passenger seat, and the target armrest is disposed between the driver's seat and the passenger seat.

15. A seat armrest adjustment device, characterized in that, The device includes: The determination module is used to determine the pre-stored height corresponding to the status information, wherein the status information includes at least one of the following: user identifier, seat occupancy status of the target vehicle, and driving information. A first adjustment module is used to adjust the target armrest to the preset height, the target armrest being associated with the seat; The second adjustment module is used to adjust the target handrail from the preset height to the target height indicated by the adjustment instruction when the user receives an adjustment instruction.

16. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the steps of the method according to any one of claims 1 to 14.

17. A computer program product, characterized in that, The computer program product includes code that, when executed, implements the steps of the method according to any one of claims 1 to 14.

18. A computer device, characterized in that, The device includes a processor coupled to at least one memory, the processor being configured to read a computer program stored in the at least one memory, causing the computer device to perform the steps of the method as claimed in any one of claims 1 to 14.

Images