Authority management method, electronic equipment and vehicle
By setting up a permission management application in the vehicle, the program permissions of the scene engine are managed in a unified manner, which solves the problem of permission abuse and management chaos caused by silent authorization, realizes standardized permission management, and improves the reliability and transparency of permission management.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-12-23
- Publication Date
- 2026-03-17
AI Technical Summary
In the existing technology, vehicle access control is performed using silent authorization, which leads to the abuse of permissions and chaotic management, failing to meet the needs of standardized management.
By setting up a permission management application, different program permissions required by the scene engine can be managed in a unified manner. Before executing the target program, the permission status is checked. If no authorization is granted, an authorization request is sent. The permission management application then grants the target permission and executes the program.
A standardized access control mechanism has been implemented, which avoids the abuse of access rights and management chaos, and improves the reliability and transparency of access control.
Smart Images
Figure CN121682804A_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to the field of vehicle control technology, and in particular to an access control method, electronic device, and vehicle. Background Technology
[0002] As the field of intelligent vehicles continues to evolve towards deeper intelligence and connectivity, in-vehicle infotainment systems are no longer simple in-car entertainment and navigation tools, but are gradually becoming core carriers that aggregate massive amounts of user information. Therefore, the importance of user privacy and access management in in-vehicle infotainment systems is becoming increasingly prominent.
[0003] In related technologies, the permission management method for scene engines executing vehicle automation programs is silent authorization, which means that all permissions are directly granted to the scene engine. This method can lead to problems such as abuse of permissions and chaotic permission management. Summary of the Invention
[0004] To address the aforementioned technical issues, this disclosure provides an access control method, electronic device, and vehicle that can achieve a standardized access control mechanism.
[0005] A first aspect of this disclosure provides a permission management method, applied to a vehicle, the method comprising: Upon receiving a program execution instruction for the target program, the target permissions corresponding to the target program are determined. The target program is used to instruct the execution of the corresponding target operation when the acquired scenario information satisfies the target scenario information. If the target permission is in an unauthorized state, send an authorization request corresponding to the target permission to the vehicle's permission management application; Based on the authorization request, the permission management application updates the permission status to authorized and sends program execution instructions to the vehicle's scene engine; The scene engine executes the target program based on the program execution instructions.
[0006] Optionally, in some embodiments of this disclosure, before determining the target permissions corresponding to the target program, the method further includes: When the scene engine starts, the scene engine access permission management application is controlled to obtain permission status information; wherein, the permission status information includes the permission status of at least one permission, and the permission status of at least one permission includes the permission status of the target permission.
[0007] Optionally, in some embodiments of this disclosure, when the permission status of the target permission is unauthorized, an authorization request is sent to the permission management application, including: If the target permission status is unauthorized, display an authorization prompt message; In response to the confirmation input of the authorization prompt, an authorization request is sent to the permission management application.
[0008] Optionally, in some embodiments of this disclosure, after determining the target permissions corresponding to the target program, the method further includes: When the target permission includes at least two permission states, determine the timestamps corresponding to at least two permission states respectively; The permission status corresponding to the latest timestamp is determined as the permission status of the target permission.
[0009] Optionally, in some embodiments of this disclosure, before determining the target permissions corresponding to the target program, the method further includes: In response to program editing input, a target program is generated, and the target permissions required to execute the target program are determined; wherein, program editing input is used to edit the target program; Send an authorization request corresponding to the target permission to the permission management application so that the permission status of the target permission can be updated to authorized through the permission management application.
[0010] In some embodiments of this disclosure, optionally, after sending the authorization request corresponding to the target permission to the permission management application, the method further includes: In response to permission cancellation input, a permission cancellation request corresponding to the target permission is sent to the permission management application so that the permission management application can update the permission status of the target permission to unauthorized.
[0011] A second aspect of this disclosure provides a permission management method, applied to an electronic device, the method comprising: In response to program editing input, the target permissions required to execute the target program are determined; wherein, program editing input is used to edit the target program; the target program is used to instruct the vehicle to perform the corresponding target operation when the acquired scenario information meets the target scenario information; Send an authorization request corresponding to the target permission to the vehicle's permission management application; upon receiving the authorization request, the permission management application updates the permission status of the target permission to authorized and sends the corresponding authorization result to the electronic device; Receive authorization result.
[0012] Optionally, in some embodiments of this disclosure, the method further includes: In response to program execution input, an execution command is sent to the vehicle's access control application; wherein, the program execution command is used to instruct the vehicle's scene engine to execute the target program; Receive the execution result of the target program.
[0013] A third aspect of this disclosure provides an access control device applied to a vehicle, the access control device comprising: The first determining module is used to determine the target permissions corresponding to the target program when a program execution instruction for the target program is received. The target program is used to instruct the execution of the corresponding target operation when the acquired scene information satisfies the target scene information. The first sending module is used to send an authorization request corresponding to the target permission to the vehicle's permission management application when the permission status of the target permission is unauthorized. The authorization module is used to control the permission management application to update the permission status to authorized based on the authorization request and send program execution instructions to the vehicle's scene engine; The control module is used to control the scene engine to execute the target program based on the program execution instructions.
[0014] A fourth aspect of this disclosure provides a permission management device applied to an electronic device, the permission management device comprising: The second determining module is used to determine the target permissions required to execute the target program in response to the program editing input; wherein, the program editing input is used to edit the target program; the target program is used to instruct the vehicle to perform the corresponding target operation when the acquired scene information meets the target scene information; The second sending module is used to send an authorization request corresponding to the target permission to the vehicle's permission management application; wherein, upon receiving the authorization request, the permission management application updates the permission status of the target permission to authorized and sends the corresponding authorization result to the electronic device; The receiving module is used to receive the authorization result.
[0015] A fifth aspect of this disclosure provides a vehicle, including: processor; Memory, used to store executable instructions; The processor is used to read executable instructions from memory and execute the executable instructions to implement the permission management method provided in the first aspect above.
[0016] A sixth aspect of this disclosure provides an electronic device, including: processor; Memory, used to store executable instructions; The processor is used to read executable instructions from memory and execute the executable instructions to implement the permission management method provided in the first aspect above.
[0017] A seventh aspect of this disclosure provides a computer-readable storage medium storing a computer program that, when executed by a processor, causes the processor to implement the permission management methods provided in the first and / or second aspects.
[0018] An eighth aspect of this disclosure provides a computer program product comprising a computer program or instructions that, when executed by a processor, implement the access control method provided in the first and / or second aspects described above.
[0019] The technical solution provided in this disclosure has the following advantages compared with the prior art: The permission management method, electronic device, and vehicle provided in this disclosure manage the permissions of different programs that the scene engine needs to execute in a unified manner by setting up a permission management application. When a target program needs to be executed, it is first determined whether the target permission required to execute the target program is available. If the target permission is not available, the permission management application grants the corresponding target permission by sending an authorization request, and the target program is executed after authorization is completed. By using a permission management application, the unlimited silent authorization permission management mode is changed, solving the problems of permission abuse and chaotic permission management, and realizing a standardized permission management mechanism. Attached Figure Description
[0020] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure.
[0021] To more clearly illustrate the technical solutions in the embodiments of this disclosure or the prior art, the accompanying drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0022] Figure 1 One of the flowcharts illustrating a permission management method according to some embodiments of this disclosure is shown; Figure 2 A schematic diagram of one of the program editing interfaces of some embodiments of this disclosure is shown; Figure 3 A second flowchart illustrating a permission management method according to some embodiments of this disclosure is shown; Figure 4 A second schematic diagram showing a program editing interface of some embodiments of this disclosure is provided. Figure 5 One of the structural block diagrams of a permission management device according to some embodiments of the present disclosure is shown; Figure 6 A second structural block diagram of a permission management device according to some embodiments of the present disclosure is shown; Figure 7 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this disclosure. Detailed Implementation
[0023] To better understand the above-mentioned objectives, features, and advantages of this disclosure, the solutions disclosed herein will be further described below. It should be noted that, unless otherwise specified, the embodiments and features described herein can be combined with each other.
[0024] Numerous specific details are set forth in the following description to provide a thorough understanding of this disclosure, but this disclosure may also be implemented in other ways different from those described herein; obviously, the embodiments in the specification are only a part of the embodiments of this disclosure, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this invention without inventive effort are within the scope of protection of this invention.
[0025] Before describing the embodiments of this disclosure in detail, the technical background involved in this disclosure will be described here so that those skilled in the art can have a clearer understanding of the embodiments of this disclosure.
[0026] In related technologies, intelligent vehicle control, through an intelligent system running on the vehicle's infotainment system, enables the intelligent execution of programs. For example, some automated programs include the ability to freely combine rules to execute preset operations when specific target scenarios are met. Examples include opening windows when the vehicle starts or activating the recirculation mode when low ambient air quality is detected.
[0027] The execution of these automated programs requires specific permissions. Taking a car infotainment system running Android as an example, Android's privacy permission management mechanism has significant limitations in scenario adaptation. Its initial design only considered the permission control needs of a single device running independently. However, in a vehicle scenario, the infotainment system needs to coordinate with surrounding devices, such as the user's mobile phone, to initiate permission management. For example, a user can edit automated programs on the infotainment system or on their mobile phone. This results in chaotic permission management and makes cross-device permission management impossible.
[0028] To address these issues, some technologies employ silent authorization, which directly grants the scene engine all permissions. However, this approach is too drastic and fails to meet the requirements for standardized permission management, leading to problems such as unauthorized permission issuance and chaotic permission management.
[0029] In view of this, this disclosure provides an access control method applied to vehicles. Figure 1 One of the flowcharts illustrating a permission management method according to some embodiments of this disclosure is shown, such as... Figure 1 As shown, the method includes: S102, upon receiving a program execution instruction for the target program, determine the target permissions corresponding to the target program. The target program is used to instruct the execution of the corresponding target operation when the acquired scene information satisfies the target scene information.
[0030] In this embodiment, vehicle users can send program execution commands to the vehicle's scene engine by controlling input through either the vehicle's infotainment system or a mobile phone-based management application. The program execution commands instruct the vehicle's scene engine to execute the target program. Specifically, the scene engine is the engine responsible for executing the aforementioned automated program.
[0031] The target program is an automated program; for example, the target program can be a target skill. Automated programs, including the target program, can set or edit freely combinable rules that indicate the mapping relationship between the target scenario in which the vehicle is located and the target operation.
[0032] When the scene information of the vehicle meets the target scene information set by the target program, the corresponding functional module on the vehicle is controlled to perform the corresponding operation.
[0033] Since the target program needs to acquire scene information and perform operations during execution, the scene engine requires corresponding target permissions to execute the target program. For example, the target program corresponds to target scene information and target operations. Acquiring the target scene information requires calling the target sensors on the vehicle, and performing the target operation requires calling the target function modules on the vehicle. Therefore, based on the target scene and target operation associated with the target program, the target permissions required to execute the target program can be determined.
[0034] For example, the target program is set to activate the air conditioning when the interior temperature is greater than or equal to 35°C. After the target program is executed, the vehicle continuously monitors the interior temperature using an internal temperature sensor. When the interior temperature reaches 35°C and there are occupants inside, the air conditioning module is controlled to start operating in cooling mode. In this case, the target permissions required to execute the target program include the permission to access the internal temperature sensor to monitor the interior temperature, and the permission to control the air conditioning module.
[0035] For example, the target program is set to close the windows when it rains. After the target program is executed, the vehicle detects rainfall using a rain sensor. When rain is detected and at least one window is open, the open window is automatically closed. In this case, the target permissions required to execute the target program include the permission to access the rain sensor to detect rainfall and the permission to control the window motors.
[0036] After receiving the control input from the vehicle user, the vehicle-mounted management application or mobile management application that received the control input first determines whether the vehicle's scene engine has the target permissions required to execute the target program.
[0037] For example, the vehicle-mounted management application and the mobile management application simultaneously store the authorization status of different vehicle sensors and different vehicle function modules for the scene engine. This authorization status can be used to determine whether the scene engine has the target permissions.
[0038] If the scene engine already has the necessary permissions for the target program, it is determined that the scene engine meets the conditions for executing the target program, and in this case, the scene engine can be controlled to execute the target program immediately. If the scene engine does not have the necessary permissions, an authorization process is initiated with the vehicle's permission management application.
[0039] S104, if the target permission's permission status is unauthorized, send an authorization request corresponding to the target permission to the vehicle's permission management application.
[0040] After determining the target permissions required to execute the target program, the system checks the permission status of the scene engine to determine if the scene engine already possesses the target permissions. If the permission status is unauthorized, it means the scene engine does not have the target permissions. In this case, an authorization request is sent to the vehicle's permission management application.
[0041] The access control application is configured to manage the permissions required to execute different automated programs in a unified manner.
[0042] S106, the permission management application updates the permission status to authorized based on the authorization request and sends program execution instructions to the vehicle's scene engine.
[0043] In this embodiment of the disclosure, the permission management application can manage the authorization status of different vehicle sensors and different vehicle function modules to the scene engine. For example, the permission management application stores permission data, which includes the permission status of each vehicle sensor and vehicle function module.
[0044] After receiving an authorization request from the vehicle-mounted management application or the mobile management application, the permission management application determines the permission status of the target permission based on the permission data. If the target permission is authorized, it determines that the local permission data of the vehicle-mounted management application or the mobile management application that sent the authorization request has not been updated. In this case, the permission management application returns the updated permission data to the vehicle-mounted management application or the mobile management application that sent the authorization request. Upon receiving the updated permission data, the vehicle-mounted management application or the mobile management application confirms that the target permission is authorized and sends an execution command to the scene engine.
[0045] If the target permission status is unauthorized, a pop-up window can be displayed to remind the vehicle user that running the target program requires authorization. The user can select or cancel authorization via the confirmation or cancellation control in the pop-up window to decide whether to grant the authorization request.
[0046] For example, when the user selects an option in the revoke authorization control, in response to the user input, the authorization status of the target permission is not set to authorized, and an authorization failure message is displayed. At this time, the target program will be unable to be executed.
[0047] After the user selects and inputs their choice on the authorization control, the permission management application, in response to the user's input, sets the permission status of the target permission to authorized. At this point, the scene engine grants the target permission. After completing the permission status update operation for the target permission, the permission management application synchronizes the authorization result with the vehicle-mounted management application and the mobile management application, and sends a program execution command to the scene engine.
[0048] S108, the scene engine executes the target program based on the program execution instructions.
[0049] In this embodiment of the disclosure, after authorization is granted, the scene engine obtains the target permissions required to execute the target program. Upon receiving the program execution instruction, the scene engine begins executing the target program based on the program execution instruction.
[0050] For example, after receiving the program instruction, the scene engine runs the target program based on the program instruction, calls the target sensor indicated by the target program to collect the corresponding sensor data, determines the scene information where the vehicle is currently located based on the sensor data, and judges whether the scene information meets the target scene information indicated by the target application.
[0051] If the scene information does not meet the target scene information, the scene engine continues to run the target program, continuously calls the target sensor to collect sensor data to determine the scene information in real time, and continuously judges whether the scene information meets the target scene information.
[0052] If the scene information matches the target scene information, the scene engine calls the target vehicle function module indicated by the target program to execute the target operation.
[0053] In some implementations, the target operation indicated by the target program is executed only once. That is, when the scene information meets the target scene information, the scene engine stops executing the target program after executing the target operation once.
[0054] In other implementations, the target operation indicated by the target program can be executed multiple times. When the scene information satisfies the target scene information, after executing the target operation once, the scene engine continues to execute the target program and continuously determines whether the scene information satisfies the target scene information. When the scene information satisfies the target scene information again, the target operation is executed again.
[0055] This embodiment of the disclosure manages the permissions of different programs that the scene engine needs to execute uniformly by setting up a permission management application. When a target program needs to be executed, it first determines whether the target permission required to execute the target program is available. If the target permission is not available, the permission management application grants the corresponding target permission by sending an authorization request, and the target program is executed after authorization is completed. By changing the permission management mode of unlimited silent authorization through the permission management application, the problems of permission abuse and chaotic permission management are solved, and a standardized permission management mechanism is achieved.
[0056] Optionally, in some embodiments of this disclosure, before determining the target permissions corresponding to the target program, the method further includes: When the scene engine starts, the scene engine access permission management application is controlled to obtain permission status information; wherein, the permission status information includes the permission status of at least one permission, and the permission status of at least one permission includes the permission status of the target permission.
[0057] In this embodiment of the disclosure, the scene engine starts synchronously when the vehicle's infotainment system starts. During the scene engine startup process, the scene engine obtains the latest permission status information through access permission management applications.
[0058] The permission status information indicates the permission status of one or more permissions required by the scene engine. This includes the permission status for the target permission.
[0059] These permission statuses can be granted to the scene engine through user authorization actions, and can also be revoked through user deauthorization actions. All these permissions are managed uniformly through a permission management application. Users can authorize or revoke permissions through the vehicle's infotainment system, or through their mobile phones or other electronic devices.
[0060] Therefore, when the vehicle's infotainment system starts up, the permission management application is used to synchronize the permission status of the infotainment system with other electronic devices, thereby avoiding the problem of permission status conflicts caused by multiple devices managing permissions separately.
[0061] This embodiment of the disclosure uses a permission management application to uniformly manage the permissions required to run automated programs. Whenever the vehicle infotainment system and scene engine start, the permission management application synchronizes the latest permission status information, ensuring that the permission status on the vehicle infotainment system is consistent with the user's other electronic devices, avoiding permission status conflicts, and improving the reliability of permission management.
[0062] Optionally, in some embodiments of this disclosure, when the permission status of the target permission is unauthorized, an authorization request is sent to the permission management application, including: If the target permission is not authorized, display an authorization prompt message; in response to the confirmation input of the authorization prompt message, send an authorization request to the permission management application.
[0063] In this embodiment of the disclosure, after receiving the program execution instruction, the target permissions required to execute the target program are first determined. By judging the permission status of the target permissions on the scene engine, it is determined whether the scene engine already has the target permissions. If the permission status is unauthorized, it means that the scene engine does not have the target permissions.
[0064] At this time, an authorization prompt message is displayed. For example, the authorization prompt message can be displayed through an in-vehicle display screen. This in-vehicle display screen includes, but is not limited to, vehicle infotainment displays, central control screens, LCD instrument cluster displays, HUDs (Head-Up Displays), and ceiling-mounted displays.
[0065] For example, the authorization prompt could be "Executing the target program requires target permissions. Please confirm authorization." For instance, the target program is to automatically turn on the air conditioning when the interior temperature exceeds 35°C. The target permission is the permission to obtain interior temperature data. The authorization information could then be "Allow the vehicle system to access the interior temperature data?"
[0066] Once the user's confirmation input is received, it is determined that the user has granted permission for this authorization. At this point, an authorization request is sent to the permission management application. After receiving the authorization request, the permission management application sets the permission status of the target permission to authorized, and the vehicle's scene engine is then granted the target permission.
[0067] For example, the aforementioned confirmation input is user input. For example, user input can be touch input from the user on the vehicle's touchscreen. For example, user input can also be input from the user via the smart steering wheel or central control buttons. For example, user input can also be voice input.
[0068] In this embodiment of the disclosure, when the scene engine executing the target program requests authorization for target permissions, an authorization prompt message is displayed, allowing the user to ultimately decide whether to grant authorization. This method enables users to understand the authorization status in real time, improving the transparency of permission management.
[0069] Optionally, in some embodiments of this disclosure, after determining the target permissions corresponding to the target program, the method further includes: If the target permission includes at least two permission states, determine the timestamps corresponding to the at least two permission states respectively; determine the permission state corresponding to the latest timestamp as the permission state of the target permission.
[0070] In this embodiment of the disclosure, users can manage permissions through the vehicle's infotainment system or other electronic devices capable of communicating with the vehicle's infotainment system. For example, a user can set the permission status of a target permission to authorized on the vehicle's infotainment system, and then update the permission status of the target permission to unauthorized via a mobile phone.
[0071] In some scenarios, such as when multiple users simultaneously configure permissions on both the vehicle's infotainment system and their mobile phones, if two users set different permission states for the same permission, a single permission might correspond to two different permission states. If these two permission states differ, a permission state conflict may occur.
[0072] In this scenario, this embodiment of the circuit breaker records a timestamp for each authorization or deauthorization operation. Therefore, whenever a permission status is generated due to an authorization or deauthorization operation, this permission status is associated with a timestamp. This timestamp records the time when the permission status was generated.
[0073] Therefore, when it is detected that the same target permission has two permission states, such as one permission state coming from the authorization operation on the vehicle system and the other permission state coming from the deactivation state on the mobile phone, the timestamp corresponding to each permission state is obtained, and the latest timestamp, that is, the permission state corresponding to the timestamp closest to the current time, is determined as the true permission state of the target permission.
[0074] In some implementations, after determining the permission status corresponding to the latest timestamp as the permission status of the target permission, other permission statuses corresponding to one or more older timestamps are deleted, so that the permission management application ultimately retains only the latest permission status.
[0075] The timestamp-based design of this embodiment avoids authorization conflicts caused by multi-terminal permission operations on mobile phones and in-vehicle systems, ensuring the smoothness of authorization operations and standardizing the permission management process.
[0076] Optionally, in some embodiments of this disclosure, before determining the target permissions corresponding to the target program, the method further includes: In response to program editing input, a target program is generated, and the target permissions required to execute the target program are determined; wherein, program editing input is used to edit the target program; an authorization request corresponding to the target permissions is sent to the permission management application so that the permission status of the target permissions is updated to authorized through the permission management application.
[0077] In this embodiment of the disclosure, the program editing input can be user input to the vehicle's infotainment system. The program editing input is used to generate the target program. For example, a specific program editing interface can be provided on the vehicle's infotainment system. Figure 2 A schematic diagram illustrating one of the program editing interfaces of some embodiments of this disclosure is shown, such as... Figure 2 As shown, the program editing interface 200 includes a condition editing control 202 and an operation editing control 204.
[0078] Users can input or select at least one target scenario information to trigger a target operation through the conditional editing control 202, and input or select at least one target operation to be performed when the target scenario information is met through the operation editing control 204. Figure 2 For example, the user sets the target scenario information as "in-vehicle temperature ≥ 35℃" and sets the target operation as "turn on the air conditioner + air conditioner temperature setting: 25℃".
[0079] Running the aforementioned target program requires specific permissions, such as permissions to obtain the vehicle's interior temperature and permissions to set air conditioning parameters.
[0080] After determining the target permission, a corresponding authorization request is sent to the permission management application. Upon receiving the authorization request, the target permission management application sets the permission status of the target permission to authorized.
[0081] For example, after determining the target permission, a corresponding authorization prompt can be displayed on the vehicle's infotainment screen, allowing the user to choose to confirm or cancel the input. If the user confirms the authorization prompt, it is determined that the user agrees to the authorization, and an authorization request is sent to the permission management application. If the user cancels the authorization prompt, the authorization is revoked.
[0082] The embodiments disclosed herein enable free editing of automated programs and grant necessary permissions during the editing process, thereby improving the efficiency of permission management.
[0083] In some embodiments of this disclosure, optionally, after sending the authorization request corresponding to the target permission to the permission management application, the method further includes: In response to permission cancellation input, a permission cancellation request corresponding to the target permission is sent to the permission management application so that the permission management application can update the permission status of the target permission to unauthorized.
[0084] In this embodiment of the disclosure, a user can grant or revoke the authorization of a target permission. Specifically, a user can revoke the authorization of a target permission by canceling input. After receiving the user's permission cancellation operation, a permission cancellation request is sent to the permission management application.
[0085] Upon receiving a permission cancellation request, the permission management application updates the target permission's status from authorized to unauthorized. At this point, the vehicle's infotainment system and scene engine will no longer hold authorization for the target permission.
[0086] In some implementations, if there is a mobile phone that communicates with the vehicle's infotainment system, or a mobile phone that is logged into the same account as the vehicle's infotainment system, the update result is synchronized to the mobile phone after the permission status of the target permission is updated, thereby ensuring that the permission status of the vehicle's infotainment system and the mobile phone are consistent.
[0087] The embodiments disclosed herein enable free updating of permission status, thereby increasing the flexibility of permission management.
[0088] This disclosure also provides an access control method, which is applied to electronic devices. Figure 3 A second flowchart illustrating a permission management method according to some embodiments of this disclosure is shown, such as... Figure 3 As shown, the method includes: S302, in response to program editing input, determines the target permissions required to execute the target program.
[0089] The program editing input is used to edit the target program; the target program is used to instruct the vehicle to perform the corresponding target operation when the acquired scene information meets the target scene information.
[0090] In this embodiment of the disclosure, the target program is an automation program. Exemplarily, the target program can be a target skill. Automation programs, including the target program, can set or edit freely combinable rules that indicate the mapping relationship between the target scenario in which the vehicle is located and the target operation.
[0091] When the scene information of the vehicle meets the target scene information set by the target program, the corresponding functional module on the vehicle is controlled to perform the corresponding operation.
[0092] For example, the electronic device may be a mobile phone, a tablet computer, an in-vehicle mobile display device, etc. In the following embodiments, a mobile phone will be used as an example to describe the embodiments of this disclosure in detail.
[0093] The electronic device runs a mobile management application that can manage one or more automation programs. Vehicle users can also edit target programs through the mobile management application. For example, editing a target program includes modifying an existing target program and creating a new one.
[0094] Program editing input can be input by the user into the program editing interface on the mobile phone. For example, Figure 4 The second schematic diagram shows a program editing interface of some embodiments of this disclosure, such as... Figure 4 As shown, the program editing interface 400 includes a condition editing control 404 and an operation editing control 404.
[0095] Similar to editing a target program on a vehicle-mounted infotainment system, users can input or select at least one target scenario information to trigger a target operation through the conditional editing control 402 in the program editing interface 400 on their mobile phone, and input or select at least one target operation to be executed when the target scenario information is met through the operation editing control 404. Figure 4 For example, the user sets the target scenario information to "rain" and the target operation to "close the car windows + close the sunroof + turn on the internal circulation".
[0096] S304: Send an authorization request corresponding to the target permission to the vehicle's permission management application.
[0097] When the permission management application receives an authorization request, it updates the permission status of the target permission to authorized and sends the corresponding authorization result to the electronic device.
[0098] For example, the access control application is configured to uniformly manage the permissions required to execute different automation programs. The access control application can manage the authorization status of different onboard sensors and different onboard functional modules for the scene engine.
[0099] After receiving an authorization request from the vehicle-mounted management application, the permission management application determines the permission status of the target permission based on the permission data. If the target permission is already authorized, it checks if the local permission data in the mobile management application has been updated. In this case, the permission management application returns the updated permission data to the mobile management application. Upon receiving the updated permission data, the mobile management application determines that the scene engine already possesses the target permission, and there is no need for repeated authorization.
[0100] If the target permission status is unauthorized, a pop-up window can be displayed to remind the vehicle user that running the target program requires authorization. The user can select or cancel authorization via the confirmation or cancellation control in the pop-up window to decide whether to grant the authorization request.
[0101] For example, when the user selects and enters the option to cancel authorization, in response to the user's input, the authorization status of the target permission is not set to authorized, and an authorization failure message is displayed, prompting the user that the target program cannot be executed.
[0102] After the user selects and enters the confirmation input control, in response to the user's input, the permission management application sets the permission status of the target permission to authorized and returns the authorization result to the mobile management application.
[0103] S306, Receive authorization result.
[0104] In this embodiment of the disclosure, after receiving the authorization result, a "Authorization successful" message can be displayed on the mobile phone screen. At this time, the edited target program can be executed by the vehicle's scene engine.
[0105] This embodiment of the disclosure enables the management of vehicle system permissions through both mobile phones and the vehicle system by setting up a permission management application on the vehicle, thus enriching the application scenarios of permission management.
[0106] Optionally, in some embodiments of this disclosure, the method further includes: In response to program execution input, an execution command is sent to the vehicle's permission management application; wherein, the program execution command is used to instruct the vehicle's scene engine to execute the target program; and the execution result of the target program is received.
[0107] In this embodiment of the disclosure, the user can also control the vehicle to execute the target program via an electronic device such as a mobile phone. For example, taking a mobile phone as an example, the mobile phone displays a program control interface. The program control interface displays at least one automation program that has been edited on the mobile phone or vehicle system, including the target program.
[0108] Users can select the target program and click the "Run" control to input program execution information. After receiving the user's program execution input, the mobile phone sends the execution command to the vehicle's infotainment system via the communication connection. In some implementations, the mobile phone can send the execution command to a cloud server, which then forwards the command to the vehicle's infotainment system logged into with the same account as the mobile phone.
[0109] After receiving the execution command, the vehicle's infotainment system executes the target program through the scene engine. Before executing the target program, the system first determines the required permissions and checks if the scene engine possesses those permissions. If the scene engine has the necessary permissions, it can execute the target program immediately. If the scene engine does not have the required permissions, it initiates an authorization process with the vehicle's access control application; only after authorization is granted will the target program be executed.
[0110] Once the vehicle's infotainment system successfully executes the target program, it sends the execution result to the mobile phone. For example, the execution result could be "Target program successfully executed".
[0111] This embodiment of the disclosure allows remote control of a vehicle by remotely controlling the vehicle's infotainment system via a mobile phone to execute a pre-edited target program.
[0112] This disclosure also provides an access control device for use in vehicles. Figure 5 One of the structural block diagrams of a permission management device according to some embodiments of the present disclosure is shown, such as Figure 5 As shown, the access control device 500 includes: a first determination module 502, a first sending module 504, an authorization module 506, and a control module 508.
[0113] The first determining module 502 is used to determine the target permissions corresponding to the target program when a program execution instruction for the target program is received. The target program is used to instruct the execution of the corresponding target operation when the acquired scene information satisfies the target scene information. The first sending module 504 is used to send an authorization request corresponding to the target permission to the vehicle's permission management application when the permission status of the target permission is unauthorized. The authorization module 506 is used to control the permission management application to update the permission status to authorized based on the authorization request and send program execution instructions to the vehicle's scene engine; The control module 508 is used to control the scene engine to execute the target program based on the program execution instructions.
[0114] This embodiment of the disclosure manages the permissions of different programs that the scene engine needs to execute uniformly by setting up a permission management application. When a target program needs to be executed, it first determines whether the target permission required to execute the target program is available. If the target permission is not available, the permission management application grants the corresponding target permission by sending an authorization request, and the target program is executed after authorization is completed. By changing the permission management mode of unlimited silent authorization through the permission management application, the problems of permission abuse and chaotic permission management are solved, and a standardized permission management mechanism is achieved.
[0115] In some embodiments of this disclosure, optionally, the control module is further configured to control the scene engine access permission management application to obtain permission status information when the scene engine starts; wherein, the permission status information includes the permission status of at least one permission, and the permission status of at least one permission includes the permission status of the target permission.
[0116] This embodiment of the disclosure uses a permission management application to uniformly manage the permissions required to run automated programs. Whenever the vehicle infotainment system and scene engine start, the permission management application synchronizes the latest permission status information, ensuring that the permission status on the vehicle infotainment system is consistent with the user's other electronic devices, avoiding permission status conflicts, and improving the reliability of permission management.
[0117] Optionally, in some embodiments of this disclosure, the permission management device further includes a display module, configured to display an authorization prompt message when the permission status of the target permission is unauthorized; the first sending module is further configured to send an authorization request to the permission management application in response to the confirmation input of the authorization prompt message.
[0118] In this embodiment of the disclosure, when the scene engine executing the target program requests authorization for target permissions, an authorization prompt message is displayed, allowing the user to ultimately decide whether to grant authorization. This method enables users to understand the authorization status in real time, improving the transparency of permission management.
[0119] In some embodiments of this disclosure, optionally, the first determining module is further configured to determine the timestamps corresponding to at least two permission states respectively when the target permission includes at least two permission states; and determine the permission state corresponding to the latest timestamp as the permission state of the target permission.
[0120] The timestamp-based design of this embodiment avoids authorization conflicts caused by multi-terminal permission operations on mobile phones and in-vehicle systems, ensuring the smoothness of authorization operations and standardizing the permission management process.
[0121] In some embodiments of this disclosure, optionally, the permission management device further includes a generation module, configured to generate a target program in response to program editing input and determine the target permissions required to execute the target program; wherein the program editing input is used to edit the target program; the first sending module is further configured to send an authorization request corresponding to the target permission to the permission management application, so as to update the permission status of the target permission to authorized through the permission management application.
[0122] The embodiments disclosed herein enable free editing of automated programs and grant necessary permissions during the editing process, thereby improving the efficiency of permission management.
[0123] Optionally, in some embodiments of this disclosure, the first sending module is further configured to send a permission cancellation request corresponding to the target permission to the permission management application in response to permission cancellation input, so as to update the permission status of the target permission to unauthorized through the permission management application.
[0124] The embodiments disclosed herein enable free updating of permission status, thereby increasing the flexibility of permission management.
[0125] This disclosure also provides an access control device for use in electronic devices. Figure 6 A second structural block diagram of a permission management device according to some embodiments of the present disclosure is shown, such as Figure 6 As shown, the access control device 600 includes: The second determining module 602 is used to determine the target permissions required to execute the target program in response to the program editing input; wherein, the program editing input is used to edit the target program; the target program is used to instruct the vehicle to perform the corresponding target operation when the acquired scene information meets the target scene information; The second sending module 604 is used to send an authorization request corresponding to the target permission to the vehicle's permission management application; wherein, upon receiving the authorization request, the permission management application updates the permission status of the target permission to authorized and sends the corresponding authorization result to the electronic device; The receiving module 606 is used to receive the authorization result.
[0126] This embodiment of the disclosure enables the management of vehicle system permissions through both mobile phones and the vehicle system by setting up a permission management application on the vehicle, thus enriching the application scenarios of permission management.
[0127] In some embodiments of this disclosure, optionally, the second sending module is further configured to send an execution instruction to the vehicle's permission management application in response to program execution input; wherein the program execution instruction is used to instruct the vehicle's scene engine to execute the target program; and the receiving module is further configured to receive the execution result of the target program.
[0128] This embodiment of the disclosure allows remote control of a vehicle by remotely controlling the vehicle's infotainment system via a mobile phone to execute a pre-edited target program.
[0129] Figure 7 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this disclosure.
[0130] In this embodiment of the disclosure, Figure 7 The electronic device shown can be a server or a terminal. Specifically, the terminal includes in-vehicle terminals, computers, or tablets, etc., without limitation.
[0131] like Figure 7 As shown, the electronic device may include a processor 710 and a memory 720 storing computer program instructions.
[0132] Specifically, the processor 710 may include a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits that can be configured to implement the embodiments of this disclosure.
[0133] Memory 720 may include a large-capacity storage for information or instructions. For example, and not limitingly, memory 720 may include a hard disk drive (HDD), a floppy disk drive, flash memory, optical disk, magneto-optical disk, magnetic tape, or a Universal Serial Bus (USB) drive, or a combination of two or more of these. Where appropriate, memory 720 may include removable or non-removable (or fixed) media. Where appropriate, memory 720 may be internal or external to the integrated gateway device. In a particular embodiment, memory 720 is a non-volatile solid-state memory. In a particular embodiment, memory 720 includes read-only memory (ROM). Where appropriate, the ROM may be a mask-programmed ROM, a programmable ROM (PROM), an erasable PROM (Electrically Programmable ROM, EPROM), an electrically erasable programmable PROM (EEPROM), an electrically alterable ROM (EAROM), or flash memory, or a combination of two or more of these.
[0134] The processor 710 reads and executes computer program instructions stored in the memory 720 to perform the steps of the permission management method provided in the embodiments of this disclosure.
[0135] In one example, the electronic device may also include a transceiver 730 and a bus 740. Wherein, as... Figure 7 As shown, the processor 710, memory 720 and transceiver 730 are connected via bus 740 and communicate with each other.
[0136] Bus 740 may include hardware, software, or both. For example, and not limitingly, the bus may include an Accelerated Graphics Port (AGP) or other graphics bus, an Extended Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a Hyper Transport (HT) interconnect, an Industrial Standard Architecture (ISA) bus, an Infinite Bandwidth Interconnect, a Low Pin Count (LPC) bus, a memory bus, a MicroChannel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local Bus (VLB) bus, or other suitable buses, or a combination of two or more of these. Where appropriate, bus 740 may include one or more buses.
[0137] This disclosure also provides a computer-readable storage medium that can store a computer program, which, when executed by a processor, enables the processor to implement the permission management method provided in this disclosure.
[0138] The aforementioned storage medium may, for example, include a memory 720 containing computer program instructions, which can be executed by a processor 710 of an electronic device to complete the permission management method provided in this embodiment. Optionally, the storage medium may be a non-transitory computer-readable storage medium, such as read-only memory (ROM), random access memory (RAM), external cache memory, compact disc ROM (CD-ROM), magnetic tape, floppy disk, flash memory, and optical data storage devices. By way of illustration and not limitation, RAM is available in various forms, such as static random access memory (SRAM) and dynamic random access memory (DRAM).
[0139] This disclosure also provides a vehicle that includes electronic devices that can implement the various processes and effects described in the above embodiments of this disclosure, which will not be elaborated here.
[0140] This disclosure also provides a computer program product, which includes a computer program or instructions. When the computer program or instructions are executed by a processor, they implement the permission management method provided in this disclosure and can achieve the various processes and effects in the above embodiments of this disclosure, which will not be elaborated here.
[0141] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.
[0142] The above description is merely a specific embodiment of this disclosure, enabling those skilled in the art to understand or implement it. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this disclosure. Therefore, this disclosure is not to be limited to the embodiments described herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. A rights management method, characterized by, The method is applied to a vehicle, and the method comprises: In a case where a program execution instruction for the target program is received, a target permission corresponding to the target program is determined, the target program being used to instruct a corresponding target operation to be performed in a case where acquired scene information meets target scene information; In a case where a permission state of the target permission is unauthorized, an authorization request corresponding to the target permission is sent to a permission management application of the vehicle; The permission management application updates the permission state to authorized based on the authorization request, and sends the program execution instruction to a scene engine of the vehicle; The scene engine executes the target program based on the program execution instruction.
2. The method of claim 1, wherein, Before the target permission corresponding to the target program is determined, the method further comprises: When the scene engine is started, the scene engine is controlled to access the permission management application to acquire permission state information; wherein the permission state information comprises a permission state of at least one permission, and the permission state of the at least one permission comprises the permission state of the target permission.
3. The method of claim 1, wherein, The authorization request is sent to the permission management application in a case where the permission state of the target permission is unauthorized, comprising: In a case where the permission state of the target permission is unauthorized, authorization prompt information is displayed; In response to a confirmation input of the authorization prompt information, the authorization request is sent to the permission management application.
4. The method of claim 1, wherein, After the target permission corresponding to the target program is determined, the method further comprises: In a case where the target permission comprises at least two permission states, time stamps corresponding to the at least two permission states are respectively determined; A permission state corresponding to a latest one of the time stamps is determined as the permission state of the target permission.
5. The method according to any one of claims 1 to 4, characterized in that, Before the target permission corresponding to the target program is determined, the method further comprises: In response to a program editing input, the target program is generated, and a target permission required for executing the target program is determined; wherein the program editing input is used to edit the target program; The authorization request corresponding to the target permission is sent to the permission management application, so as to update the permission state of the target permission to authorized by the permission management application.
6. The method of claim 5, wherein, After the authorization request corresponding to the target permission is sent to the permission management application, the method further comprises: In response to a permission canceling input, a permission canceling request corresponding to the target permission is sent to the permission management application, so as to update the permission state of the target permission to unauthorized by the permission management application.
7. A rights management method characterized by, The method is applied to an electronic device, and the method comprises: In response to a program editing input, a target permission required for executing a target program is determined; wherein the program editing input is used to edit the target program; the target program is used to instruct a vehicle to perform a corresponding target operation in a case where acquired scene information meets target scene information; An authorization request corresponding to the target permission is sent to a permission management application of the vehicle; wherein the permission management application updates a permission state of the target permission to authorized in a case where the authorization request is received, and sends a corresponding authorization result to the electronic device; The authorization result is received.
8. The method of claim 7, wherein, The method further includes: sending, in response to a program execution input, an execution instruction to a permission management application of the vehicle; wherein the program execution instruction is used to instruct a scenario engine of the vehicle to execute a target program; receiving an execution result of the target program.
9. A vehicle characterized by comprising: Comprise: a memory; a processor; and executable program code; wherein the executable program code is stored in the memory and is configured to be executed by the processor to implement the method as claimed in any one of claims 1-6.
10. An electronic device, comprising: Comprise: a memory; a processor; and executable program code; wherein the executable program code is stored in the memory and is configured to be executed by the processor to implement the method as claimed in claim 7 or 8.