Method for managing device usage permissions and electronic device

Abstract

The application is suitable for the technical field of intelligent terminals, and provides a device usage permission management method and an electronic device, including: in response to a permission request of a ward received at a first time, acquiring a first confidence degree of a voice event corresponding to the first time; wherein the permission request is used for requesting to run a target function of a device; the voice event corresponding to the first time is an event of recognizing a guardian voice before the first time; the first confidence degree is used for representing a confidence degree of the guardian being present for guardianship; and the permission request is processed according to the first confidence degree of the voice event to allow or prohibit running the target function. Through the above method, the flexibility of electronic device permission management can be improved.

Description

Technical Field

[0001] This application belongs to the field of smart terminal technology, and in particular relates to a method for managing device usage rights and an electronic device. Background Technology

[0002] With the widespread use of electronic devices, personalized access control has become an important requirement in the use of these devices. For example, in some application scenarios, there is an increasing number of situations where children and other wards have independent access to electronic devices, and guardians need to set access permissions for these wards.

[0003] Currently, most electronic devices use a fixed permission configuration scheme for permission management, which means that a list of functions that are allowed or prohibited is pre-defined. However, this method is not very flexible and cannot be adapted to various monitoring scenarios. Summary of the Invention

[0004] This application provides a method for managing device usage permissions and an electronic device, which can improve the flexibility of electronic device permission management.

[0005] In a first aspect, embodiments of this application provide a method for managing device usage rights, including: In response to a permission request received from the ward at a first moment, a first confidence level of the voice event corresponding to the first moment is obtained; wherein, the permission request is used to request the operation of the target function of the device; the voice event corresponding to the first moment is an event in which the guardian's voice is recognized before the first moment; the first confidence level is used to characterize the credibility of the guardian's presence during monitoring; The permission request is processed based on a first confidence level of the voice event to allow or deny the operation of the target function.

[0006] In this embodiment, permission requests are processed based on a first confidence level. Since the first confidence level characterizes the credibility of the guardian's presence, it is equivalent to dynamically controlling the device's usage permissions based on the credibility of the guardian's presence. This approach achieves dynamic adaptive adjustment of operating permissions according to the credibility of the guardian's presence, solving the problem that fixed permission policies are difficult to adapt to changes in the monitoring scenario and improving the flexibility of electronic device permission management.

[0007] In one possible implementation of the first aspect, obtaining the first confidence level of the voice event corresponding to the first moment includes: Obtain all voice events within a preset time window prior to the first moment to obtain an event set; Obtain the first event from the event set; wherein the first event is a voice event with a similarity greater than a first threshold, and the similarity of the voice event is used to represent the similarity between the voiceprint feature corresponding to the voice event and the voiceprint feature of the guardian; Calculate a second confidence level for each of the first events; wherein the second confidence level is used to characterize the credibility of the guardian's presence during monitoring; The first confidence level is determined based on the second confidence level of each first event.

[0008] In the above implementation, the first event with qualified voiceprint similarity is selected from all voice events within a preset time window before the first moment. The time window constrains the range of historical voice events, and voiceprint similarity filters invalid recognition results, eliminating interference events such as noise and non-target voices, ensuring the validity of the data used in the confidence calculation. Furthermore, a second confidence level, representing the credibility of the guardian's presence, is calculated for each first event. The final first confidence level is then obtained by combining the second confidence levels. This improves the accuracy and stability of the quantification of the guardian's presence credibility, making subsequent guardianship status determination and permission set matching more closely resemble real-world guardianship scenarios, further enhancing the reliability of permission control.

[0009] In one possible implementation of the first aspect, calculating the second confidence level for each of the first events includes: Calculate the time decay value of the first event based on the time difference between the time corresponding to the first event and the first time. The second confidence level of the first event is calculated based on the time decay value and similarity of the first event.

[0010] In the above implementation, a time decay value is obtained by combining the time difference between the occurrence of the voice event and the initiation of the permission request, and the confidence score is calculated by integrating the voiceprint similarity corresponding to the voice event. This method relies on the time decay mechanism to reflect objective laws, namely, the greater the time difference from the first moment, the lower the credibility of the guardian's presence. At the same time, voiceprint similarity is introduced to characterize the recognition reliability of the voice event. By combining the recognition reliability with the credibility decay caused by the passage of time, the final calculated confidence score can more objectively and accurately reflect the credibility of the guardian's presence, providing a reliable basis for subsequent processing.

[0011] In one possible implementation of the first aspect, processing the permission request based on a first confidence level of the voice event includes: A set of permissions is determined based on the first confidence level; wherein the set of permissions includes at least one function of the device; The validity of the target function is verified based on the set of permissions to obtain the verification result. The target function may be allowed or prohibited from running based on the verification result.

[0012] In the above implementation method, the permission set is determined based on the confidence level, and the permission request of the ward is verified according to the permission set. This realizes the dynamic adaptive adjustment of operation permissions as the credibility of the guardian's presence changes, solves the problem that fixed permission policies are difficult to adapt to changes in the guardianship scenario, and helps to improve the flexibility of electronic device permission management.

[0013] In one possible implementation of the first aspect, determining the permission set based on the first confidence level includes: If the first confidence level is greater than the second threshold, then the permission set is determined according to the first set and the second set; wherein, the first set includes the basic permissions of the ward; and the second set includes the extended permissions of the ward. If the first confidence level is less than the second threshold, then the permission set is determined based on the first set.

[0014] In the above implementation, different monitoring states are divided based on a first confidence level, and different permission configurations are applied to different monitoring states. When the first confidence level is greater than a second threshold, a permission set is generated by combining a first set of basic permissions and a second set of extended permissions, and both basic and extended permissions are enabled. When the first confidence level is less than the second threshold, only the first set containing basic permissions is used, and the use of extended permissions is restricted. Through the above method, a clear division of monitoring states is achieved based on the confidence level threshold, so that the scope of permission opening is accurately matched with the credibility of the guardian's presence. When the credibility level is high, the richness of operations is guaranteed, and when the credibility level is insufficient, the higher-risk extended operations are proactively restricted, thereby achieving hierarchical and dynamic permission control.

[0015] In one possible implementation of the first aspect, determining the permission set based on the first set and the second set includes: Obtain a third set; wherein the third set includes the prohibited permissions of the ward; The first permission is determined based on the union of the first set and the second set; Delete the permissions that belong to the third set from the first set of permissions to obtain the permission set.

[0016] In the above implementation method, a separate blacklist of prohibited permissions is introduced for secondary filtering. While opening up basic and extended permissions, high-risk and prohibited operations are accurately blocked. This constructs a two-layer control mechanism of "permission opening + blacklist constraint". This ensures the richness of normally available functions and can accurately block the most risky prohibited operations. It further refines the granularity of permission control, effectively avoids the risk of high-risk instructions being executed, and helps to improve the security and control precision of permission management.

[0017] In one possible implementation of the first aspect, determining the first permission based on the union of the first set and the second set includes: Determine the preset time period to which the first moment belongs; Obtain the fourth set corresponding to the preset time period; wherein, the fourth set includes the permissions of the ward within the preset time period; The second permission is determined based on the intersection of the first set and the fourth set; The first permission is determined based on the union of the second permission and the second set.

[0018] In the above implementation, a fourth set of time-based permissions is introduced to impose time constraints on basic permissions. This enables the configuration of permissions to be superimposed with time-dimensional control rules. Only basic permissions that can be executed in the current time period are opened. This allows permissions to not only rely on the trustworthiness of the monitoring, but also to be dynamically adjusted over time. This builds a multi-layered permission screening mechanism that takes into account both trustworthiness and time constraints, further refines the granularity of permission control, conforms to the usage norms of different time periods, and improves the flexibility of permission control.

[0019] In one possible implementation of the first aspect, determining the first permission based on the union of the first set and the second set includes: Based on the voice event corresponding to the first moment, identify the temporary permissions granted by the guardian to the ward; The first permission is determined based on the union of the first set, the second set, and the temporary permission.

[0020] In the above implementation method, temporary permissions are merged with basic and extended permissions to generate the first permission; temporary permissions are dynamically granted based on natural voice interaction, and guardians do not need to manually configure the permission list in advance. They can issue temporary operation permissions in real time simply through voice commands, so that the normalized fixed permissions and voice-delegated temporary permissions can work together to improve the flexibility of permission management; in addition, obtaining temporary permissions through voice recognition makes the permission granting method more natural and convenient, and can respond to temporary use needs in an instant, improving the real-time nature of permission issuance and the smoothness of human-computer interaction.

[0021] In one possible implementation of the first aspect, the method further includes: The temporary permission will be deleted when the expiration time and / or cumulative duration of the temporary permission are reached.

[0022] In the above implementation, temporary permissions granted by the guardian via voice are subject to constraints such as expiration time and / or cumulative duration. The effectiveness status of temporary permissions is continuously monitored, and the temporary permission is automatically cleared when the set expiration time is reached or the cumulative usage time is exhausted. This achieves automatic expiration control of temporary permissions, avoiding the risk of uncontrolled permissions due to long-term retention of temporary permissions. It accurately matches short-term authorization scenarios and improves the complete lifecycle management of temporary permissions from granting, activation to automatic revocation, thereby enhancing the security and automation of permission control. In addition, this method eliminates the need for the guardian to revoke permissions again via voice or manually, reducing the cumbersome operation for the guardian.

[0023] Secondly, embodiments of this application provide a device for managing device usage rights, including: The acquisition unit is configured to, in response to a permission request received from the ward at a first moment, acquire a first confidence level of the voice event corresponding to the first moment; wherein, the permission request is used to request the operation of a target function of the device; the voice event corresponding to the first moment is an event in which the guardian's voice was recognized before the first moment; and the first confidence level is used to characterize the degree of credibility of the guardian's presence during monitoring. The processing unit is configured to process the permission request based on a first confidence level of the voice event, so as to allow or prohibit the operation of the target function.

[0024] Thirdly, embodiments of this application provide an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements a device usage permission management method as described in any one of the first aspects above.

[0025] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program that, when executed by a processor, implements the device usage permission management method as described in any one of the first aspects above.

[0026] Fifthly, embodiments of this application provide a computer program product that, when run on a terminal device, causes the terminal device to execute the device usage permission management method described in any of the first aspects above.

[0027] It is understood that the beneficial effects of the second to fifth aspects mentioned above can be found in the relevant descriptions in the first aspect mentioned above, and will not be repeated here. Attached Figure Description

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

[0029] Figure 1 This is a flowchart illustrating the device usage permission management method provided in an embodiment of this application; Figure 2 This is a schematic diagram of the process for obtaining the first confidence level provided in an embodiment of this application; Figure 3 This is a schematic diagram of the permission processing flow provided in the embodiments of this application; Figure 4 This is a structural block diagram of the device for managing device usage rights provided in the embodiments of this application; Figure 5 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0030] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application may also be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods have been omitted so as not to obscure the description of this application with unnecessary detail.

[0031] It should be understood that, when used in this application specification and the appended claims, the term "comprising" indicates the presence of the described features, integrals, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or a collection thereof.

[0032] It should also be understood that the term “and / or” as used in this application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0033] As used in this application specification and the appended claims, the term "if" may be interpreted, depending on the context, as "when," "once," "in response to determination," or "in response to detection." Similarly, the phrase "if determined" or "if detected [the described condition or event]" may be interpreted, depending on the context, as meaning "once determined," "in response to determination," "once detected [the described condition or event]," or "in response to detection [the described condition or event]."

[0034] Furthermore, in the description of this application and the appended claims, the terms "first," "second," "third," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0035] References to "one embodiment" or "some embodiments" in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized.

[0036] With the widespread use of electronic devices, personalized access control has become an important requirement in the use of these devices. For example, in some application scenarios, there is an increasing number of situations where children and other wards have independent access to electronic devices, and guardians need to set access permissions for these wards.

[0037] Currently, most electronic devices use a fixed permission configuration scheme for permission management, which means that a list of functions that are allowed or prohibited is pre-defined. However, this method is not very flexible and cannot be adapted to various monitoring scenarios.

[0038] Based on this, embodiments of this application provide a method for managing device usage permissions. In this embodiment, permission requests are processed based on a first confidence level, where the first confidence level characterizes the credibility of a guardian's presence. This is equivalent to dynamically controlling device usage permissions based on the credibility of the guardian's presence. In this way, operational permissions are dynamically and adaptively adjusted according to the credibility of the guardian's presence, solving the problem that fixed permission policies are difficult to adapt to changes in monitoring scenarios and improving the flexibility of electronic device permission management.

[0039] See Figure 1 This is a flowchart illustrating a method for managing device usage rights provided in an embodiment of this application. It is intended as an example and not a limitation. The method may include the following steps: S101, in response to the permission request received from the ward at the first moment, obtain the first confidence level of the voice event corresponding to the first moment.

[0040] In this embodiment, the permission request is used to request the execution of a target function of the device. In this application embodiment, the device can be an electronic device. The function of the device can refer to the system functions built into the electronic device, such as telephone, messaging, and settings. The function of the device can also refer to applications installed on the electronic device, such as video applications, shopping applications, music applications, and search applications. It should be noted that in this application embodiment, the permission request can be used to request one target function or multiple target functions.

[0041] Optionally, the permission request can be text, such as the ward entering text into the electronic device to indicate the requested function, and the electronic device receiving the text and recording it as a permission request. Alternatively, the permission request can be voice, such as the ward uttering voice to indicate the requested function, and the electronic device receiving the voice and recording it as a permission request.

[0042] The first moment corresponds to the voice event that occurs before the first moment when the guardian's voice is detected. It is understood that the electronic device can continuously monitor voice in the current environment, and when the guardian's voice is detected, it is recorded as a voice event. Each voice event may include a segment of speech and the moment the voice event was detected.

[0043] The first confidence level is used to characterize the credibility of the guardian's presence during monitoring. It can be understood that the higher the first confidence level, the higher the credibility of the guardian's presence during monitoring; conversely, the lower the first confidence level, the lower the credibility of the guardian's presence during monitoring.

[0044] It should be noted that the guardian in this application embodiment can refer to a specific person or multiple people with guardianship authority. For example, if only the mother has guardianship authority, the guardian can refer to the mother; if both the mother and the father have guardianship authority, the guardian can refer to both the mother and the father.

[0045] In some embodiments, see Figure 2 This is a schematic diagram illustrating the process of obtaining the first confidence level provided in an embodiment of this application. For example... Figure 2 As shown, S101 includes steps S201-S204, as detailed below.

[0046] S201: Obtain all voice events within the preset time window before the first moment to obtain the event set.

[0047] Understandably, voice events in the event set may include voices from non-guardians.

[0048] S202, retrieve the first event in the event set.

[0049] The first event is a voice event with a similarity greater than a first threshold. The similarity of the voice event is used to represent the similarity between the voiceprint features corresponding to the voice event and the voiceprint features of the guardian.

[0050] Understandably, when there are multiple guardians, for any given voice event, if the similarity between the voiceprint feature corresponding to the voice event and the voiceprint feature of any one of the guardians is greater than a first threshold, then the voice event is recorded as the first event.

[0051] Optionally, the voiceprint features of a segment of speech corresponding to a voice event, as well as the voiceprint features of the guardian, can be extracted using a preset feature model. The guardian's voiceprint features can be pre-collected. For example, the guardian can input voice into the electronic device beforehand; in response, the electronic device extracts and saves the guardian's voiceprint features based on the voice. During access control, the electronic device can directly access the saved voiceprint features of the guardian.

[0052] Optionally, a first feature vector can be generated from the voiceprint features of the speech event, and a second feature vector can be generated from the voiceprint features of the guardian. The similarity between the first and second feature vectors is then calculated, which is the similarity of the speech event. For example, cosine similarity or Euclidean distance can be used to calculate the similarity.

[0053] S203, calculate the second confidence level for each first event.

[0054] The second confidence level is used to characterize the credibility of the guardian's presence during supervision.

[0055] In some implementations, S203 includes: The time decay value of the first event is calculated based on the time difference between the corresponding time of the first event and the first time; the second confidence level of the first event is calculated based on the time decay value of the first event and the similarity.

[0056] Among them, the greater the time difference between the time corresponding to the first event and the first moment, the greater the time decay value, indicating that the time of occurrence of the guardian's voice is longer than the first moment, and the lower the confidence of the guardianship.

[0057] For example, according to the formula e^( λ·(t t_k) calculates the time decay rate. Here, is a preset decay parameter, t is the first time point, and t_k is the time point corresponding to the kth first event.

[0058] Optionally, the weighted sum of the time decay value of the first event and the similarity is recorded as the second confidence level of the first event.

[0059] Optionally, the product of the time decay value of the first event and the similarity is recorded as the second confidence level of the first event.

[0060] Optionally, the similarity can be normalized so that the similarity value falls within a specific range, such as [0,1].

[0061] For example, see Table 1, which is an example of the second confidence level provided in the embodiments of this application.

[0062] Table 1

[0063] As shown in Table 1, the first time point is 16:00:00, and the first threshold is 0.75. For voice event E_1, its occurrence time (i.e., the time when voice event E_1 is detected) is 15:57:00, and its time difference with the first time point is 180s, with a similarity of 0.95. Since the similarity of 0.95 is greater than the first threshold of 0.75, voice event E_1 is recorded as the first event. The similarity of 0.95 is normalized to 1, and the time decay value of voice event E_1 is calculated to be 0.5. The product of the similarity of 1 and the time decay value of 0.5, 0.5, is recorded as the second confidence of the first event E_1. For voice event E_2, its occurrence time (i.e., the time when voice event E_2 is detected) is 15:58:50, and its time difference with the first time point is 70s, with a similarity of 0.72. Since the similarity of 0.72 is less than the first threshold of 0.75, voice event E_2 is an invalid event and is not included in the confidence calculation. For voice event E_3, its occurrence time (i.e. the time when voice event E_3 is detected) is 15:59:30, the time difference between it and the first time is 30s, and the similarity is 0.83. Since the similarity of 0.83 is greater than the first threshold of 0.75, voice event E_3 is recorded as the first event. The similarity of 0.83 is normalized to 1, and the time decay value of voice event E_3 is calculated to be 0.891. The product of the similarity of 1 and the time decay value of 0.891, 0.891, is recorded as the second confidence level of the first event E_1.

[0064] In the above implementation, a time decay value is obtained by combining the time difference between the occurrence of the voice event and the initiation of the permission request, and the confidence score is calculated by integrating the voiceprint similarity corresponding to the voice event. This method relies on the time decay mechanism to reflect objective laws, namely, the greater the time difference from the first moment, the lower the credibility of the guardian's presence. At the same time, voiceprint similarity is introduced to characterize the recognition reliability of the voice event. By combining the recognition reliability with the credibility decay caused by the passage of time, the final calculated confidence score can more objectively and accurately reflect the credibility of the guardian's presence, providing a reliable basis for subsequent processing.

[0065] S204, determine the first confidence level based on the second confidence level of each first event.

[0066] Optionally, the first confidence level can be determined based on the statistical value of the second confidence level for each first event.

[0067] For example, the average of the second confidence levels for each first event can be denoted as the first confidence level. Alternatively, the maximum value among the second confidence levels for each first event can be denoted as the first confidence level.

[0068] In one example, based on an application scenario in Table 1, at 15:57 on Sunday afternoon, the mother discusses dinner with the grandmother in the living room. The system records E_1, sim ≈ 0.95, which is valid and recorded as the first event. At 15:58:50, a voice resembling the mother is identified, sim ≈ 0.72, which is invalid and discarded. At 15:59:30, the mother responds to Xiaoming's question with "Mmm," which is recorded as E_3, sim ≈ 0.83, which is valid and recorded as the first event. At 16:00:00, Xiaoming requests to "play cartoons." According to the data calculated in Table 1, the first confidence level is max(0.891, 0.5) = 0.891. If the mother does not speak for the next 10 minutes, the first confidence level becomes e^( ln2 × 600 / 180) ≈ 0.099.

[0069] Figure 2 In this embodiment, a first event with acceptable voiceprint similarity is selected from all voice events within a preset time window prior to the first moment. The time window constrains the range of historical voice events, and voiceprint similarity filters invalid recognition results, eliminating interference events such as noise and non-target voices, ensuring the validity of the data used in the confidence calculation. Furthermore, a second confidence level, representing the credibility of the guardian's presence, is calculated for each first event. The final first confidence level is then obtained by combining all the second confidence levels. This improves the accuracy and stability of the quantification of the guardian's presence credibility, making subsequent guardianship status determination and permission set matching more closely resemble real-world guardianship scenarios, further enhancing the reliability of permission control.

[0070] S102, process the permission request based on the first confidence level of the voice event to allow or deny the operation of the target function.

[0071] In some embodiments, see Figure 3 This is a schematic diagram of the permission processing flow provided in an embodiment of this application. It is intended as an example and not a limitation. Figure 3 As shown, S102 includes S301-S303, as detailed below.

[0072] S301, determine the permission set based on the first confidence level.

[0073] The permission set includes at least one function of the device.

[0074] S302, perform validity verification on the target function based on the permission set, and obtain the verification result.

[0075] Specifically, if the permission set includes the target function, the verification result indicates that the verification has passed; if the permission set does not include the target function, the verification result indicates that the verification has failed.

[0076] S303, allow or disable the target function based on the verification result.

[0077] Specifically, if the verification result indicates that the target function passes, then the target function is allowed to run; if the verification result indicates that the target function fails, then the target function is prohibited from running.

[0078] Figure 3 In this embodiment, the set of permissions is determined based on the confidence level, and the permission requests of the ward are verified according to the set of permissions. This realizes the dynamic adaptive adjustment of operation permissions as the credibility of the guardian's presence changes, which solves the problem that fixed permission policies are difficult to adapt to changes in the guardianship scenario and helps to improve the flexibility of electronic device permission management.

[0079] In some implementations, S301 includes two cases, as detailed below.

[0080] Case 1: If the first confidence level is greater than the second threshold, then the permission set is determined based on the first set and the second set.

[0081] The first set includes the basic permissions of the ward. The second set includes the extended permissions of the ward. It is understood that the first set may include at least one basic permission, each basic permission corresponding to a function of the device. The second set may include at least one extended permission, each extended permission corresponding to a function of the device.

[0082] The first and second sets can be pre-set. Optionally, if there are multiple wards, a dedicated first and second set can be set for each ward; or, the multiple wards can be grouped, and a dedicated first and second set can be set for each group.

[0083] In the above implementation, different monitoring states are divided based on a first confidence level, and different permission configurations are applied to different monitoring states. When the first confidence level is greater than a second threshold, a permission set is generated by combining a first set of basic permissions and a second set of extended permissions, and both basic and extended permissions are enabled. When the first confidence level is less than the second threshold, only the first set containing basic permissions is used, and the use of extended permissions is restricted. Through the above method, a clear division of monitoring states is achieved based on the confidence level threshold, so that the scope of permission opening is accurately matched with the credibility of the guardian's presence. When the credibility level is high, the richness of operations is guaranteed, and when the credibility level is insufficient, the higher-risk extended operations are proactively restricted, thereby achieving hierarchical and dynamic permission control.

[0084] In some implementations, the steps for determining the permission set based on the first set and the second set include: Obtain the third set; whereby the third set includes the prohibited permissions for the ward; The first authority is determined based on the union of the first set and the second set; Remove the permissions that belong to the third set from the first set of permissions to obtain the permission set.

[0085] Understandably, the third set may include at least one prohibited permission, with each prohibited permission corresponding to a function of the device.

[0086] The third set can be pre-set. Optionally, if there are multiple wards, a dedicated third set can be set up for each ward; or, the multiple wards can be grouped, and a dedicated third set can be set up for each group.

[0087] In the above implementation method, a separate blacklist of prohibited permissions is introduced for secondary filtering. While opening up basic and extended permissions, high-risk and prohibited operations are accurately blocked. This constructs a two-layer control mechanism of "permission opening + blacklist constraint". This ensures the richness of normally available functions and can accurately block the most risky prohibited operations. It further refines the granularity of permission control, effectively avoids the risk of high-risk instructions being executed, and helps to improve the security and control precision of permission management.

[0088] In some implementations, the steps for determining the first permission based on the union of the first set and the second set include: Determine the preset time period to which the first moment belongs; Obtain the fourth set corresponding to the preset time period; wherein, the fourth set includes the permissions of the ward within the preset time period; The second permission is determined based on the intersection of the first set and the fourth set; The first permission is determined by the union of the second permission and the second set.

[0089] It is understandable that the fourth set may include at least one permission, each permission corresponding to a function of the device.

[0090] Optionally, multiple preset time periods and a corresponding fourth set for each preset time period can be pre-set. For example, 16:00-18:00 can be set as the study period, 18:00-22:00 as the leisure period, and 22:00-08:00 as the bedtime period. The fourth set corresponding to the study period is {learning query, search}, the fourth set corresponding to the leisure period is {listen to stories, learning query, play nursery rhymes, alarm clock}, and the fourth set corresponding to the bedtime period is {emergency call, alarm clock}.

[0091] Understandably, the fourth set can be pre-set. Optionally, in the case of multiple wards, a dedicated fourth set can be set up for each ward; or, the multiple wards can be grouped, and a dedicated fourth set can be set up for each group.

[0092] In the above implementation, a fourth set of time-based permissions is introduced to impose time constraints on basic permissions. This enables the configuration of permissions to be superimposed with time-dimensional control rules. Only basic permissions that can be executed in the current time period are opened. This allows permissions to not only rely on the trustworthiness of the monitoring, but also to be dynamically adjusted over time. This builds a multi-layered permission screening mechanism that takes into account both trustworthiness and time constraints, further refines the granularity of permission control, conforms to the usage norms of different time periods, and improves the flexibility of permission control.

[0093] In other implementations, the step of determining the first permission based on the union of the first set and the second set includes: The temporary permissions granted by the guardian to the ward are identified based on the corresponding voice event at the first moment. The first permission is determined by the union of the first set, the second set, and the temporary permission.

[0094] Understandably, a voice event can identify at least one temporary permission, with each temporary permission corresponding to a function of the device. For example, if the guardian's voice in a voice event is "Watch 30 minutes of animation," a temporary permission is identified, corresponding to the function "animation." As another example, if the guardian's voice in a voice event is "Study for 1 hour, then you can watch 30 minutes of animation," two temporary permissions are identified, corresponding to the functions "study" and "animation," respectively.

[0095] In the above implementation method, temporary permissions are merged with basic and extended permissions to generate the first permission; temporary permissions are dynamically granted based on natural voice interaction, and guardians do not need to manually configure the permission list in advance. They can issue temporary operation permissions in real time simply through voice commands, so that the normalized fixed permissions and voice-delegated temporary permissions can work together to improve the flexibility of permission management; in addition, obtaining temporary permissions through voice recognition makes the permission granting method more natural and convenient, and can respond to temporary use needs in an instant, improving the real-time nature of permission issuance and the smoothness of human-computer interaction.

[0096] In some implementations, the steps for determining the first permission based on the union of the first set and the second set include: Determine the preset time period to which the first moment belongs; Obtain the fourth set corresponding to the preset time period; wherein, the fourth set includes the permissions of the ward within the preset time period; The temporary permissions granted by the guardian to the ward are identified based on the corresponding voice event at the first moment. The second permission is determined based on the intersection of the first set and the fourth set; The first permission is determined by the union of the second permission, the second set, and the temporary permission.

[0097] In the above implementation method, the first permission is determined by combining the inherent permissions of the time period and the temporary permissions granted by the guardian through voice. The normal permissions of the time period and the temporary authorization by the guardian in real time are distinguished by the layered intersection and union operations, so as to realize the collaborative management of static permission rules of the time period and dynamic temporary authorization by voice. It can not only automatically adapt the basic usage permissions of different time periods based on preset time periods, avoiding the irrationality of uniform permission management throughout the day, but also flexibly add temporary permissions by capturing the guardian's on-site voice commands in real time. The permission combination logic is clear, taking into account the stability of normal time period management and the flexibility of temporary authorization by voice. It finely distinguishes between long-term fixed permissions, time period effective permissions, and immediate temporary permissions, so that the permission management strategy of electronic devices is more in line with diverse application scenarios, improving the precision of permission management and scenario adaptability.

[0098] In some implementations, the method further includes: Delete temporary permissions when the expiration time and / or cumulative duration are reached.

[0099] Optionally, the voice corresponding to the temporary permission is recognized to obtain the expiration time and / or cumulative duration of the temporary permission.

[0100] Optionally, for the cumulative duration, the total duration of the temporary permission during its operation can be calculated; if the total duration reaches the cumulative duration, then the temporary permission is considered to have reached the cumulative duration. It is understood that the pause time of the temporary permission is not included in the total duration.

[0101] For example, see Table 2, which provides an example of the duration of temporary permissions provided in the embodiments of this application.

[0102] Table 2

[0103] As shown in Table 2, if the guardian's voice message in the voice event is "Watch animation for 30 minutes," then the cumulative duration of this temporary permission is identified as 1800 seconds (30 minutes). The expiration time for this temporary permission is not identified; it can be set to empty or a default value (e.g., a fallback time of current time + 1 hour). If the guardian's voice message in the voice event is "Watch until 9 PM," then the expiration time of this temporary permission is identified as 9 PM. The cumulative duration of this temporary permission is not identified; it can be set to empty or a default value (e.g., a default of 2 hours). If the guardian's voice message in the voice event is "Watch for half an hour, latest until 9 PM," then the expiration time of this temporary permission is identified as 9 PM, and the cumulative duration of this temporary permission is 1800 seconds.

[0104] In the above implementation, temporary permissions granted by the guardian via voice are subject to constraints such as expiration time and / or cumulative duration. The effectiveness status of temporary permissions is continuously monitored, and the temporary permission is automatically cleared when the set expiration time is reached or the cumulative usage time is exhausted. This achieves automatic expiration control of temporary permissions, avoiding the risk of uncontrolled permissions due to long-term retention of temporary permissions. It accurately matches short-term authorization scenarios and improves the complete lifecycle management of temporary permissions from granting, activation to automatic revocation, thereby enhancing the security and automation of permission control. In addition, this method eliminates the need for the guardian to revoke permissions again via voice or manually, reducing the cumbersome operation for the guardian.

[0105] Scenario 2: If the first confidence level is less than the second threshold, then the permission set is determined based on the first set.

[0106] In some implementations, the steps for determining the permission combination based on the first set include: Obtain the third set; whereby the third set includes the prohibited permissions for the ward; Remove permissions from the first set that belong to the third set to obtain the permission set.

[0107] In the above implementation method, a separate blacklist of prohibited permissions is introduced for secondary filtering. While granting basic permissions, high-risk and prohibited operations are precisely blocked. This constructs a two-layer control mechanism of "permission granting + blacklist constraint". This ensures the richness of normally available functions and can accurately block the most risky prohibited operations. It further refines the granularity of permission control, effectively avoids the risk of high-risk instructions being executed, and helps to improve the security and control precision of permission management.

[0108] In other implementations, the steps for determining the permission set based on the first set include: Determine the preset time period to which the first moment belongs; Get the fourth set corresponding to the preset time period; The permission set is determined based on the intersection of the first set and the fourth set.

[0109] In the above implementation, a fourth set of time-based permissions is introduced to impose time constraints on basic permissions. This enables the configuration of permissions to be superimposed with time-dimensional control rules. Only basic permissions that can be executed in the current time period are opened. This allows permissions to not only rely on the trustworthiness of the monitoring, but also to be dynamically adjusted over time. This builds a multi-layered permission screening mechanism that takes into account both trustworthiness and time constraints, further refines the granularity of permission control, conforms to the usage norms of different time periods, and improves the flexibility of permission control.

[0110] In some implementations, the steps for determining the permission set based on the first set include: The temporary permissions granted by the guardian to the ward are identified based on the corresponding voice event at the first moment. The permission set is determined by the union of the first set and the temporary permissions.

[0111] In the above implementation method, temporary permissions and basic permissions are merged to generate a permission set; temporary permissions are dynamically granted based on natural voice interaction, and guardians do not need to manually configure the permission list in advance. They can issue temporary operation permissions in real time simply through voice commands, so that the normalized fixed permissions and voice-delegated temporary permissions can work together to improve the flexibility of permission management; in addition, obtaining temporary permissions through voice recognition makes the permission granting method more natural and convenient, and can respond to temporary use needs in an instant, improving the real-time nature of permission issuance and the smoothness of human-computer interaction.

[0112] In some implementations, the steps for determining the permission set based on the first set include: Determine the preset time period to which the first moment belongs; Get the fourth set corresponding to the preset time period; The temporary permissions granted by the guardian to the ward are identified based on the corresponding voice event at the first moment. The second permission is determined based on the intersection of the first set and the fourth set; The third permission is determined by the union of the second permission and the temporary permission; Remove permissions belonging to the third set from the third set of permissions to obtain the permission set.

[0113] In the above implementation method, the first permission is determined by combining the inherent permissions of the time period and the temporary permissions granted by the guardian through voice. The normal permissions of the time period and the temporary authorization by the guardian in real time are distinguished by the layered intersection and union operations, so as to realize the collaborative management of static permission rules of the time period and dynamic temporary authorization by voice. It can not only automatically adapt the basic usage permissions of different time periods based on preset time periods, avoiding the irrationality of uniform permission management throughout the day, but also flexibly add temporary permissions by capturing the guardian's on-site voice commands in real time. The permission combination logic is clear, taking into account the stability of normal time period management and the flexibility of temporary authorization by voice. It finely distinguishes between long-term fixed permissions, time period effective permissions, and immediate temporary permissions, so that the permission management strategy of electronic devices is more in line with diverse application scenarios, improving the precision of permission management and scenario adaptability.

[0114] It should be noted that the permission set in this application embodiment matches the ward who initiates the permission request. For example, when ward A initiates a permission request, the permission set is determined based on the first set, second set, third set, and / or fourth set set for ward A. When ward B initiates a permission request, the permission set is determined based on the first set, second set, third set, and / or fourth set set for ward B.

[0115] As an example, see Table 3, which is an example of the permissions provided in the embodiments of this application.

[0116] Table 3

[0117] In one scenario, assuming the first confidence level C(t) for this permission request is 0.891 and the second threshold is 0.65, then the first confidence level is greater than the second threshold, and the guardianship state is extended. That is, the permission set is determined based on the first and second sets. Specifically, according to the formula P_eff = (P_normal ∩ R_time) ∪ P_guarded ∪ P_temp P_safety_block determines the permission set. Based on the sets shown in Table 3, the final determined permission set P_eff is {listen to stories, learn and query, play nursery rhymes, alarm clock, play cartoons, turn on the projector, video call, science videos}.

[0118] In another scenario, assuming the first confidence level C(t) for this permission request is 0.5 and the second threshold is 0.65, then the first confidence level is less than the second threshold, and the monitoring state is normal. That is, the permission set is determined based on the first set. Specifically, according to the formula P_eff = (P_normal ∩ R_time) ∪ P_temp P_safety_block determines the permission set. Based on the sets shown in Table 3, the final determined permission set P_eff is {listen to stories, learn to query, play nursery rhymes, alarm clock, science videos}.

[0119] As shown in Table 3, the cumulative duration of the science videos in the temporary permissions is 900 seconds. Therefore, when the total duration of the science videos running on the electronic device reaches 900 seconds, the temporary permissions for the science videos will be deleted.

[0120] Figure 1 In this embodiment, permission requests are processed based on a first confidence level. Since the first confidence level characterizes the trustworthiness of the guardian's presence, this is equivalent to dynamically controlling the device's usage permissions based on the trustworthiness of the guardian's presence. In this way, operational permissions are dynamically and adaptively adjusted according to the trustworthiness of the guardian's presence, solving the problem that fixed permission policies are difficult to adapt to changes in the monitoring scenario and improving the flexibility of electronic device permission management.

[0121] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0122] Corresponding to the device usage permission management method described in the above embodiments, Figure 4 This is a structural block diagram of the device for managing device usage rights provided in the embodiments of this application. For ease of explanation, only the parts related to the embodiments of this application are shown.

[0123] Reference Figure 4 The device 4 includes: The acquisition unit 41 is configured to, in response to a permission request received from the ward at a first moment, acquire a first confidence level of the voice event corresponding to the first moment; wherein, the permission request is used to request the operation of the target function of the device; the voice event corresponding to the first moment is an event in which the guardian's voice was recognized before the first moment; and the first confidence level is used to characterize the degree of trustworthiness of the guardian's presence during monitoring.

[0124] Processing unit 42 is configured to process the permission request based on a first confidence level of the voice event in order to allow or prohibit the operation of the target function.

[0125] Optionally, the acquisition unit 41 is also used for: Obtain all voice events within a preset time window prior to the first moment to obtain an event set; Obtain the first event from the event set; wherein the first event is a voice event with a similarity greater than a first threshold, and the similarity of the voice event is used to represent the similarity between the voiceprint feature corresponding to the voice event and the voiceprint feature of the guardian; Calculate a second confidence level for each of the first events; wherein the second confidence level is used to characterize the credibility of the guardian's presence during monitoring; The first confidence level is determined based on the second confidence level of each first event.

[0126] Optionally, the acquisition unit 41 is also used for: Calculate the time decay value of the first event based on the time difference between the time corresponding to the first event and the first time. The second confidence level of the first event is calculated based on the time decay value and similarity of the first event.

[0127] Optionally, the processing unit 42 is also used for: A set of permissions is determined based on the first confidence level; wherein the set of permissions includes at least one function of the device; The validity of the target function is verified based on the set of permissions to obtain the verification result. The target function may be allowed or prohibited from running based on the verification result.

[0128] Optionally, the processing unit 42 is also used for: If the first confidence level is greater than the second threshold, then the permission set is determined according to the first set and the second set; wherein, the first set includes the basic permissions of the ward; and the second set includes the extended permissions of the ward. If the first confidence level is less than the second threshold, then the permission set is determined based on the first set.

[0129] Optionally, the processing unit 42 is also used for: Obtain a third set; wherein the third set includes the prohibited permissions of the ward; The first permission is determined based on the union of the first set and the second set; Delete the permissions that belong to the third set from the first set of permissions to obtain the permission set.

[0130] Optionally, the processing unit 42 is also used for: Determine the preset time period to which the first moment belongs; Obtain the fourth set corresponding to the preset time period; wherein, the fourth set includes the permissions of the ward within the preset time period; The second permission is determined based on the intersection of the first set and the fourth set; The first permission is determined based on the union of the second permission and the second set.

[0131] Optionally, the processing unit 42 is also used for: Based on the voice event corresponding to the first moment, identify the temporary permissions granted by the guardian to the ward; The first permission is determined based on the union of the first set, the second set, and the temporary permission.

[0132] Optionally, the processing unit 42 is also used for: The temporary permission will be deleted when the expiration time and / or cumulative duration of the temporary permission are reached.

[0133] It should be noted that the information interaction and execution process between the above-mentioned devices / units are based on the same concept as the method embodiments of this application. For details on their specific functions and technical effects, please refer to the method embodiments section, and they will not be repeated here.

[0134] in addition, Figure 4 The device access control management device shown can be a software unit, hardware unit, or a combination of software and hardware built into an existing terminal device, or it can be integrated into the terminal device as an independent component, or it can exist as an independent terminal device.

[0135] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is merely an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the functional units and modules are only for easy differentiation and are not intended to limit the scope of protection of this application. The specific working process of the units and modules in the above system can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0136] Figure 5 This is a schematic diagram of the structure of the electronic device provided in an embodiment of this application. For example... Figure 5 As shown, the electronic device 5 of this embodiment includes: at least one processor 50 ( Figure 5(Only one is shown in the image) a processor, a memory 51, and a computer program 52 stored in the memory 51 and executable on the at least one processor 50, wherein the processor 50 executes the computer program 52 to implement the steps in the above embodiments of the management method for access rights of any of the devices.

[0137] The electronic device may be a desktop computer, laptop, handheld computer, or cloud server, etc. This electronic device may include, but is not limited to, a processor and memory. Those skilled in the art will understand that... Figure 5 This is merely an example of electronic device 5 and does not constitute a limitation on electronic device 5. It may include more or fewer components than shown in the figure, or combine certain components, or different components. For example, it may also include input / output devices, network access devices, etc.

[0138] The processor 50 can be a Central Processing Unit (CPU), or it can be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor.

[0139] In some embodiments, the memory 51 may be an internal storage unit of the electronic device 5, such as a hard disk or memory of the electronic device 5. In other embodiments, the memory 51 may be an external storage device of the electronic device 5, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the electronic device 5. Furthermore, the memory 51 may include both internal and external storage units of the electronic device 5. The memory 51 is used to store the operating system, applications, boot loader, data, and other programs, such as the program code of the computer program. The memory 51 can also be used to temporarily store data that has been output or will be output.

[0140] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, can implement the steps in the above-described method embodiments.

[0141] This application provides a computer program product that, when run on a terminal device, enables the terminal device to implement the steps described in the various method embodiments.

[0142] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments of this application can be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include at least: any entity or device capable of carrying computer program code to a device / terminal equipment, a recording medium, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electrical carrier signal, a telecommunication signal, and a software distribution medium. Examples include USB flash drives, portable hard drives, magnetic disks, or optical disks. In some jurisdictions, according to legislation and patent practice, computer-readable media cannot be electrical carrier signals or telecommunication signals.

[0143] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0144] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0145] In the embodiments provided in this application, it should be understood that the disclosed devices / terminal equipment and methods can be implemented in other ways. For example, the device / terminal equipment embodiments described above are merely illustrative. For instance, the division of modules or 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 displayed or discussed mutual coupling or direct coupling or communication connection may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0146] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

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

Claims

1. A method for managing device usage rights, characterized in that, include: In response to a permission request received from the ward at a first moment, a first confidence level of the voice event corresponding to the first moment is obtained; wherein, the permission request is used to request the operation of the target function of the device; the voice event corresponding to the first moment is an event in which the guardian's voice is recognized before the first moment; the first confidence level is used to characterize the credibility of the guardian's presence during monitoring; The permission request is processed based on a first confidence level of the voice event to allow or deny the operation of the target function.

2. The method for managing device usage rights as described in claim 1, characterized in that, The step of obtaining the first confidence level of the voice event corresponding to the first moment includes: Obtain all voice events within a preset time window prior to the first moment to obtain an event set; Obtain the first event from the event set; wherein the first event is a voice event with a similarity greater than a first threshold, and the similarity of the voice event is used to represent the similarity between the voiceprint feature corresponding to the voice event and the voiceprint feature of the guardian; Calculate a second confidence level for each of the first events; wherein the second confidence level is used to characterize the credibility of the guardian's presence during monitoring; The first confidence level is determined based on the second confidence level of each first event.

3. The method for managing device usage rights as described in claim 2, characterized in that, The calculation of the second confidence level for each of the first events includes: Calculate the time decay value of the first event based on the time difference between the time corresponding to the first event and the first time. The second confidence level of the first event is calculated based on the time decay value and similarity of the first event.

4. The method for managing device usage rights as described in any one of claims 1 to 3, characterized in that, The step of processing the permission request based on the first confidence level of the voice event includes: A set of permissions is determined based on the first confidence level; wherein the set of permissions includes at least one function of the device; The validity of the target function is verified based on the set of permissions to obtain the verification result. The target function may be allowed or prohibited from running based on the verification result.

5. The method for managing device usage rights as described in claim 4, characterized in that, The step of determining the permission set based on the first confidence level includes: If the first confidence level is greater than the second threshold, then the permission set is determined according to the first set and the second set; wherein, the first set includes the basic permissions of the ward; and the second set includes the extended permissions of the ward. If the first confidence level is less than the second threshold, then the permission set is determined based on the first set.

6. The method for managing device usage rights as described in claim 5, characterized in that, Determining the permission set based on the first set and the second set includes: Obtain a third set; wherein the third set includes the prohibited permissions of the ward; The first permission is determined based on the union of the first set and the second set; Delete the permissions that belong to the third set from the first set of permissions to obtain the permission set.

7. The method for managing device usage rights as described in claim 6, characterized in that, The step of determining the first permission based on the union of the first set and the second set includes: Determine the preset time period to which the first moment belongs; Obtain the fourth set corresponding to the preset time period; wherein, the fourth set includes the permissions of the ward within the preset time period; The second permission is determined based on the intersection of the first set and the fourth set; The first permission is determined based on the union of the second permission and the second set.

8. The method for managing device usage rights as described in claim 6, characterized in that, The step of determining the first permission based on the union of the first set and the second set includes: Based on the voice event corresponding to the first moment, identify the temporary permissions granted by the guardian to the ward; The first permission is determined based on the union of the first set, the second set, and the temporary permission.

9. The method for managing device usage rights as described in claim 8, characterized in that, The method further includes: The temporary permission will be deleted when the expiration time and / or cumulative duration of the temporary permission are reached.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the method as described in any one of claims 1 to 9.

Images