A method for controlling the state of a camera function and related devices.

By generating operational compliance certificates for cameras and comparing them with compliance requirements, the system makes real-time decisions on the target risk function status, solving the problem of cameras operating illegally under static policies and improving the compliance and security of the equipment.

CN123123702APending Publication Date: 2026-11-17HANGZHOU HUACHENG SOFTWARE TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611390285.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-09-08
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

In existing technologies, the target risk function status control of cameras relies on static platform policies or account permissions, which may lead to the risk that the camera may continue to operate in violation of regulations even after the compliance status changes.

Method used

By acquiring the compliance certification requirements and device operational data corresponding to the target risk functions of the camera, an operational compliance certificate is generated. Based on the comparison results with the compliance certification requirements, the status of the target risk function is decided in real time, including the status of enabling, pending authorization, downgraded, frozen, disabled, and revoked.

Benefits of technology

It enables real-time comparison between the current actual operating status of the equipment and compliance requirements, avoiding the risk that the target risk function will continue to operate in violation of regulations after the compliance status changes, thus improving the compliance and security of the equipment.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123123702A_ABST
    Figure CN123123702A_ABST
Patent Text Reader

Abstract

This application discloses a method and related apparatus for controlling the state of a camera function. The method includes: acquiring the compliance certification requirements corresponding to a target risk function of the camera, and acquiring device operational data related to the target risk function from the camera's local storage; generating an operational compliance certificate for the target risk function based on the device operational data; and controlling the state of the target risk function based on a comparison between the operational compliance certificate and the corresponding compliance certification requirements. Through this method, the application enables the state control of the target risk function to no longer rely on static platform policies or account permissions, but rather to make real-time decisions based on a comparison between the current actual operating state of the device and the compliance requirements, thus avoiding the risk that the target risk function will continue to operate in violation of regulations after the compliance status changes.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of equipment safety technology, and in particular to a method for controlling the status of a camera function and related devices. Background Technology

[0002] Cameras typically possess features designed to mitigate potential risks, such as cloud recording, video playback, human / facial recognition, sound capture, intelligent event recognition, third-party sharing, raw video export, remote diagnostics, and cross-regional access. These features may involve access to home video feeds, personal identification, children's activities, device location, account information, and network access records. Therefore, they are subject to compliance requirements in different countries and regions, including those related to privacy protection, data security, child protection, cross-border transmission, security maintenance, and cybersecurity.

[0003] Currently, these target risk functions are usually controlled by static function switches or platform permission tables. However, in actual operation, the compliance status of cameras may change dynamically. If the functions are still controlled by static function switches or platform permission tables, there may be situations where the target risk functions continue to operate but the actual status of the device is not compliant. Summary of the Invention

[0004] The main technical problem addressed by this application is to provide a method and related apparatus for controlling the status of camera functions, which enables the status control of target risk functions to no longer rely on static platform policies or account permissions, but to make decisions in real time based on the comparison results between the current actual operating status of the device and the compliance requirements, thereby avoiding the risk that the target risk function will continue to operate in violation of regulations after the compliance status changes.

[0005] To address the aforementioned technical problems, the first aspect of this application provides a method for controlling the state of a camera function. This method includes: acquiring compliance certification requirements corresponding to a target risk function of the camera; acquiring device operational data related to the target risk function from the camera's local storage; generating operational compliance certification for the target risk function based on the device operational data; and controlling the state of the target risk function based on a comparison between the operational compliance certification and the corresponding compliance certification requirements.

[0006] The status of the target risk function includes at least one of the following: enabled, pending authorization, downgraded, frozen, disabled, or revoked.

[0007] The states are as follows: the enableable state indicates that the target risk function is fully available; the pending authorization state indicates that the target risk function requires real-time authorization before each activation; the downgraded state indicates that the target risk function provides services with limited capabilities; the frozen state indicates that the target risk function is suspended but retains configuration data; the disabled state indicates that the target risk function is completely unavailable; and the revoked state indicates that the target risk function has been terminated and related permission data has been cleared.

[0008] The operational compliance proof includes multiple first proof items and a first parameter value corresponding to each first proof item; the compliance proof requirement includes multiple second proof items and a second parameter value corresponding to each second proof item.

[0009] The process of determining the status of each target risk function by comparing the operational compliance proof of the target risk function with the compliance proof requirements corresponding to each target risk function includes: determining the status of each second proof item based on the first comparison result between each first proof item and each second proof item, and the second comparison result between each first parameter value and each second parameter value; and determining the status of the target risk function based on the status of each second proof item.

[0010] The step of determining the state of each second proof item based on the first comparison result between each first proof item and each second proof item, and the second comparison result between each first parameter value and each second parameter value, includes: treating each second proof item as a to-be-judged item, and determining whether there is a first proof item identical to the to-be-judged item in the first comparison result; in response to the absence of a first proof item identical to the to-be-judged item in the first comparison result, or in response to the presence of a first proof item identical to the to-be-judged item in the first comparison result and the first parameter value of the first proof item being empty, determining the state of the to-be-judged item as missing; in response to the presence of a first proof item identical to the to-be-judged item in the first comparison result... The same first proof item is used as the first proof item to be determined. In the second comparison result, it is determined whether the first parameter value of the item to be determined is consistent with the second parameter value of the item to be determined. If the first parameter value of the item to be determined is consistent with the second parameter value of the item to be determined, the status of the item to be determined is determined to be passed. If the first parameter value of the item to be determined conflicts with the second parameter value of the item to be determined, the status of the item to be determined is determined to be conflicted. If the first parameter value of the item to be determined is earlier than the validity period, the status of the item to be determined is determined to be expired. If the first parameter value of the item to be determined exceeds a preset reasonable range, the status of the item to be determined is determined to be abnormal.

[0011] The step of determining the state of the target risk function based on the state of each of the second proof items includes: obtaining the triggering conditions corresponding to each state of the target risk function; wherein the triggering conditions characterize the state that each of the second proof items must satisfy in each state of the target risk function; for each triggering condition, determining whether the state of each of the second proof items satisfies the triggering condition; and in response to the state of each of the second proof items satisfying the triggering condition, determining the state of the target risk function as the state corresponding to the triggering condition.

[0012] The method further includes, prior to determining the state of the target risk function based on the state of each of the second proof items, the following steps before determining the state of the target risk function: in response to a conflict in the state of some of the second proof items, selecting a target proof item from the conflicting second proof items according to the priority of each of the second proof items, so as to determine the state of the target risk function based on the state of the target proof item.

[0013] The step of generating the operational compliance certificate for the target risk function based on the equipment operational data includes: standardizing the equipment operational data; and combining the standardized equipment operational data to obtain the operational compliance certificate for the target risk function.

[0014] The compliance proof requirement includes multiple second proof items; the step of obtaining device operating status data related to the target risk function from the camera locality includes: obtaining the first parameter value corresponding to each of the second proof items from the camera locality to obtain the device operating status data related to the target risk function.

[0015] The method further includes, after determining the status of each target risk function by comparing the operational compliance proof of each target risk function with the corresponding compliance proof requirements, the method further includes: obtaining the monitoring result obtained by continuously monitoring the device operational data; in response to the monitoring result indicating that the device operational data has been updated, re-executing the process of generating the operational compliance proof of the target risk function and its subsequent steps based on the device operational data; and / or, re-executing the process of generating the operational compliance proof of the target risk function and its subsequent steps based on the device operational data at preset intervals.

[0016] Before obtaining the compliance certification requirements corresponding to each of the target risk functions and obtaining the device operation data related to the target risk functions of the camera from the camera's local storage, the method further includes: obtaining each function possessed by the camera; and determining whether each function is a target risk function based on a preset set of target risk functions.

[0017] To address the aforementioned technical problems, a second aspect of this application provides a computer device comprising a memory and a processor, wherein the memory stores program instructions and the processor executes the program instructions to implement the method provided above.

[0018] To address the aforementioned technical problems, a third aspect of this application provides a computer-readable storage medium storing program instructions that can be executed by a processor to implement the methods provided above.

[0019] The beneficial effects of this application are as follows: Unlike the prior art, this application obtains the compliance certification requirements corresponding to the target risk function of the camera, and obtains the device operation status data related to the target risk function from the camera itself; based on the device operation status data, it generates the operation status compliance certificate of the target risk function; based on the comparison result between the operation status compliance certificate of the target risk function and the compliance certification requirements corresponding to the target risk function, it controls the status of the target risk function. This enables the status control of the target risk function to no longer rely on static platform policies or account permissions, but to make real-time decisions based on the comparison result between the current actual operating status of the device and the compliance requirements, thus avoiding the risk that the target risk function will continue to operate in violation of regulations after the compliance status changes. Attached Figure Description

[0020] To more clearly illustrate the technical solutions in this application, the accompanying drawings required in the description of the embodiments 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. Among them: Figure 1 This is a flowchart illustrating one embodiment of the camera function status control method provided in this application; Figure 2 This is a schematic diagram of the framework structure of one embodiment of the status control device for the camera function provided in this application; Figure 3 This is a schematic diagram of the framework structure of one embodiment of the computer device provided in this application; Figure 4 This is a schematic diagram of the framework structure of one embodiment of the computer-readable storage medium provided in this application. Detailed Implementation

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

[0022] It should be noted that the embodiments of this application contain descriptions involving "first," "second," etc., which are for descriptive purposes only and should not be construed as indicating or implying their relative importance or implicitly specifying the number of technical features indicated. Therefore, a feature defined with "first" or "second" may explicitly or implicitly include at least one of that feature.

[0023] In the description of this application, "multiple" means at least two, such as two, three, etc., unless otherwise explicitly specified. All directional indications (such as up, down, left, right, front, back, etc.) in the embodiments of this application are only used to explain the relative positional relationships and movement of the components in a specific posture (as shown in the figures). If the specific posture changes, the directional indication will also change accordingly. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or devices.

[0024] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of the invention. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0025] In this document, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship. Furthermore, "several" in this document means two or more. Moreover, the term "at least one" in this document means any combination of at least two of any one or more of a plurality of elements. For example, including at least one of A, B, and C can mean including any one or more elements selected from the set consisting of A, B, and C.

[0026] This application provides the following embodiments, and each embodiment is described in detail below.

[0027] Please see Figure 1 , Figure 1 This is a flowchart illustrating one embodiment of the camera function status control method provided in this application. The method includes: S11: Obtain the compliance certification requirements corresponding to the target risk function of the camera, and obtain the device operating status data related to the target risk function from the camera's local storage.

[0028] In one embodiment, the camera can be a camera in a video camera, a camera in a smart lock, or a camera in a robot, etc. The target risk function can be a user-specified function; for example, the user selects cloud recording as the target risk function. In another embodiment, the target risk function is a function existing in a preset set of target risk functions, which is established in advance as needed. After acquiring the functions possessed by the camera, based on the preset set of target risk functions, it is determined whether each function is a target risk function.

[0029] The preset target risk function set can be determined based on the risk level of each function, with functions of higher risk levels added to the target risk function set. For example, the target risk function set includes the following functions: cloud recording, video playback, human / face recognition, sound capture, intelligent event recognition, third-party sharing, raw video export, remote diagnostics, and cross-regional access.

[0030] In other embodiments, the device may determine whether each function of the camera is a target risk function. Specifically, it may obtain the risk level corresponding to each function of the camera, determine whether the risk level is greater than a preset level, and if so, take the camera's function as a target risk function.

[0031] In one embodiment, compliance proof requirements refer to predefined compliance standards for a specific target risk function, which specify the mandatory proof items, optional proof items, permitted statuses, degradation strategies, and audit requirements that must be met for the function to be enabled or operated.

[0032] In one specific embodiment, the compliance proof requirements corresponding to the target risk function are obtained based on the structured rules corresponding to the target risk function. The structured rules can be displayed in the form of tables or matrices, such as setting a corresponding functional capability matrix for each target risk function. The functional capability matrix can include multiple matrix fields, including but not limited to template number, region where the function is allowed to be used, user type where the function is allowed to be used, camera hardware model, camera firmware version range, function name, function risk level, mandatory proof items, optional proof items, proof item source, status determination rules, validity period, allowed status of the function, downgrade strategy, audit requirements, and gating action mapping. Among them, user type is such as home user, administrator, etc. Mandatory proof items indicate that the status must be a passed proof item, otherwise the function will be directly frozen or disabled; for example, user authorization, transmission encryption, storage encryption, and regional storage policy can be used as mandatory proof items. Optional proof items indicate that the status can be a failed proof item. If it fails, the function can be downgraded or await authorization, but will not be directly frozen. The proof item source defines where the data needs to be obtained when collecting the parameters of a specific proof item. The status determination rules characterize the trigger conditions corresponding to each status. The degradation policy specifies the extent to which a function's capabilities are reduced when it enters a "degraded" state. For example, a cloud recording degradation policy might allow uploading only local event summaries, not original video clips, or only anonymized clips. Gating action mapping represents the mapping relationship between a function's state and specific gating actions; for example, if the state is frozen, the gating action is to reject all system calls. Auditing requirements define what logs must be recorded on the device and in the cloud, and for how long, when the function is enabled, degraded, or rejected.

[0033] Among them, some fields in multiple matrix fields are secondary proof items, such as mandatory proof items and optional proof items. In addition, the regions where the function is allowed to be used, the user types where the function is allowed to be used, the validity period, etc. can also be used as secondary proof items.

[0034] After establishing the capability matrix, the system reads the field values ​​corresponding to at least some of the matrix fields and combines them according to a preset proof template to form the compliance proof requirements corresponding to the target risk function. When the target risk function is enabled or invoked, the system matches the corresponding function record in the capability matrix based on the target risk function name, device region, account region, user type, camera hardware model, and firmware version, and uses the compliance proof requirements generated from that function record.

[0035] For example, compliance requirements for facial recognition functionality may include valid model signature, matching model applicable regions, existence of user authorization, display of privacy prompts, and enabled log anonymization. Compliance requirements for cloud recording functionality may include enabled transmission encryption, enabled storage encryption, matching regional storage policies, existence of user consent records, and availability of deletion capabilities; among these, transmission encryption can be a mandatory proof item. Compliance requirements for remote diagnostic functionality may include the existence of diagnostic work orders, valid temporary authorization, matching of diagnostic tool whitelists, enabled anonymization of diagnostic logs, and controlled debugging ports.

[0036] In one embodiment, the functional capability matrix corresponding to the target risk function can be matched with an existing functional capability matrix based on at least one of the following: the region currently used by the target risk function, the type of user currently targeted, the current hardware model of the camera, the name of the target risk function, and the firmware version number of the camera. The matched functional capability matrix is ​​then used as the functional capability matrix corresponding to the target risk function.

[0037] Device operational data refers to data generated in real time during camera operation that reflects its current technical status and security configuration, including but not limited to at least one of the following fields: firmware version, firmware hash, firmware signature status, model version, model hash, model signature status, privacy masking switch, audio acquisition switch, child mode, neighbor area masking status, transmission encryption status, storage encryption status, debug port status, key area status, log anonymization status, log retention period, area policy version, user authorization identifier, authorization validity period, function call source, function call time, and device health status, etc.

[0038] Obtaining device operational data related to the target risk function from the camera's local storage includes: obtaining all device operational data related to the target risk function, or obtaining the first parameter value corresponding to each second proof item from the camera's local storage to obtain the device operational data related to the target risk function. In other words, after determining the target risk function, first obtain the compliance certification requirements corresponding to the target risk function, obtain each second proof item from the compliance certification requirements, and then obtain the first parameter value corresponding to each second proof item from the camera's local storage, without needing to obtain all device operational data related to the target risk function.

[0039] For example, the format of device runtime data related to the cloud recording function is as follows: current firmware hash `fw_hash`, firmware signature status `fw_sig=valid`, cloud recording related configuration `cloud_recording_config`, transmission encryption switch `tls_enabled=true`, storage encryption policy version `storage_policy_v3`, user authorization record `consent_id`, device region `region=EU`, and delete interface status `delete_api_enabled=true`. If a certain field cannot be collected, for example, if the user authorization record is empty, that field will still be written into the device runtime data, but its corresponding parameter value will be empty.

[0040] S12: Based on the equipment's operational status data, generate operational compliance proof for the target risk function.

[0041] In one embodiment, the device's operational data can be directly combined according to a preset proof template to generate operational compliance proof for the target risk function.

[0042] In other embodiments, the device runtime data can be standardized first; the standardized runtime data can then be combined to obtain the runtime compliance proof for the target risk function. The standardization process includes at least one of the following: normalization, hashing, signing, and version binding of the device runtime data. The generated runtime compliance proof includes at least one of the following: proof number, device identifier, proof time, proof template number, function capability matrix version, firmware proof item, model proof item, privacy configuration proof item, security configuration proof item, log proof item, regional policy proof item, authorization proof item, function call proof item, proof item status set, and signature verification value. In a preferred embodiment, the runtime compliance proof does not directly contain a key, original authorization certificate, or complete log content, but only a verifiable digest, status code, and evidence index.

[0043] The standardization process includes, but is not limited to, unifying the version number format, converting the switch status to a boolean value, converting the authorization validity period to a timestamp, and converting the policy version to a policy digest. Then, a hash digest is generated for the key fields, and a signature verification value is generated using the device key or security zone key.

[0044] In one specific embodiment, standardized device operational data is combined into a structured proof digest according to a preset proof template, and the proof digest serves as proof of operational compliance. Specifically, the device operational data includes the first parameter value corresponding to each second proof item in the proof template. The parameter values ​​of each standardized second proof item are filled into the corresponding proof item positions in the template one by one to obtain the structured proof digest. After obtaining the structured proof digest, the device's private key stored in the secure zone or trusted execution environment can be used to digitally sign the key fields in the digest (such as proof number, device identifier, function identifier, status values ​​of each proof item, timestamp, etc.) to generate a signature verification value. This signature verification value serves as the last component of the proof digest and is stored or reported along with the digest. The final generated runtime compliance certificate is a complete structured document, which includes: the certificate number, the device identifier that generated the certificate, the time of certificate generation, the target risk function, the certificate template used, and the version of the function capability matrix; the certificate items record: firmware hash value, transmission encryption status, storage encryption status, user authorization identifier and its validity period timestamp, regional policy version summary, deletion interface status, and client prompt version; finally, a signature verification value generated by the device private key is attached.

[0045] For example, the proof digest can adopt the following structure: proof_id (proof number), device_id (device identifier that generated the proof), function_id (target risk function), template_id (proof template number used when generating the proof), matrix_version (feature matrix version number referenced when generating the proof), proof_items (set of proof items, i.e., the first parameter value of each proof item collected by this function), item_status (set of proof item statuses, which is empty in the proof digest), timestamp (timestamp of proof generation), and signature (digital signature verification value). Among these, proof_items does not store the original key or complete log; it only stores the status digest and evidence index.

[0046] S13: Based on the comparison results between the operational compliance proof of the target risk function and the corresponding compliance proof requirements of the target risk function, control the state of the target risk function.

[0047] In one embodiment, the operational compliance proof includes multiple first proof items and a first parameter value corresponding to each first proof item; the compliance proof requirement corresponding to the target risk function includes multiple second proof items and a second parameter value corresponding to each second proof item. Taking the second proof item as an authorization-type proof item as an example, the second parameter value includes whether the authorization record exists and whether the authorization record is within its validity period.

[0048] Each first proof item is compared with each second proof item to obtain a first comparison result; then each first parameter value is compared with each second parameter value to obtain a second comparison result. In one specific embodiment, the state of the target risk function can be determined directly based on the consistency between the first and second comparison results. In another specific embodiment, the state of each second proof item can be determined first based on the first and second comparison results; then, the state of the target risk function can be determined based on the state of each second proof item.

[0049] The second comparison result may only include the comparison results of the parameter values ​​corresponding to the same first and second proof items. For example, if both the first and second proof items are regions, then the comparison results of their corresponding parameter values ​​are obtained. If the first proof item is a region and the second proof item is a user type, then the comparison results of their corresponding parameter values ​​are not obtained.

[0050] In one embodiment, a proof item status determination rule can also be obtained, which specifies the details of the first comparison result and the second comparison result for each state of the proof item. For example, if the proof item is passed, the first comparison result and the second comparison result must be completely consistent. If the proof item is expired, the first comparison result is consistent, the second comparison result is inconsistent, and the first parameter value is earlier than the expiration date. In this case, the expiration date can be the second parameter value, or it can be something other than the second parameter value.

[0051] In one specific embodiment, determining the state of each second proof item based on the first comparison result between each first proof item and each second proof item, and the second comparison result between each first parameter value and each second parameter value, includes: treating each second proof item as a to-be-judged item, and determining whether there is a first proof item identical to the to-be-judged item in the first comparison result; in response to the absence of a first proof item identical to the to-be-judged item in the first comparison result, or in response to the presence of a first proof item identical to the to-be-judged item in the first comparison result and the first parameter value of the first proof item being empty, determining the state of the to-be-judged item to be missing; in response to the presence of a first proof item identical to the to-be-judged item in the first comparison result... The first proof item is the same as the item to be judged, which is taken as the item to be determined. In the second comparison result, it is determined whether the first parameter value of the item to be determined is consistent with the second parameter value of the item to be judged. If the first parameter value of the item to be determined is consistent with the second parameter value of the item to be judged, the status of the item to be judged is determined to be passed; if the first parameter value of the item to be determined conflicts with the second parameter value of the item to be judged, the status of the item to be judged is determined to be conflicted; if the first parameter value of the item to be determined is earlier than the validity period, the status of the item to be judged is determined to be expired; if the first parameter value of the item to be determined exceeds the preset reasonable range, the status of the item to be judged is determined to be abnormal.

[0052] For example, if both the first and second proof items are regions, but the first parameter value is the United States and the second parameter value is the United Kingdom, then the two parameter values ​​conflict, and the region item's status is conflicted. If both the first and second proof items are validity periods, with the first parameter value being 2025-01-01 and the second parameter value being from 2026-01-01 to 2026-03-01, then the validity period item's status is expired. If both the first and second proof items are firmware hashes, with the first parameter being the current hash value and the second parameter being the hash value in the official signature library, and the two are inconsistent, then the firmware hash item's status is abnormal.

[0053] In one embodiment, determining the state of the target risk function based on the state of each second proof item includes: obtaining the triggering conditions corresponding to each state of the target risk function; wherein the triggering conditions characterize the state that each second proof item must satisfy in each state of the target risk function; for each triggering condition, determining whether the state of each second proof item satisfies the triggering condition; and in response to the state of each second proof item satisfying the triggering condition, determining the state of the target risk function as the state corresponding to the triggering condition.

[0054] The status of a target risk function includes at least one of the following: Enabled, Pending Authorization, Downgraded, Frozen, Disabled, and Revoked. Among them, the Enabled status indicates that the target risk function is fully available; the Pending Authorization status indicates that the target risk function requires real-time authorization before each activation; the Downgraded status indicates that the target risk function provides services with limited capabilities; the Frozen status indicates that the target risk function is suspended but retains configuration data; the Disabled status indicates that the target risk function is completely unavailable; and the Revoked status indicates that the target risk function has been terminated and related permission data has been cleared.

[0055] For example, the target risk function can be in an enabled state, triggered by all second proofs being passed; or in a pending authorization state, triggered by the authorization-related proofs being missing and all other second proofs being passed. A downgraded state can be triggered by the privacy configuration item failing and the security item passing in each second proof; a frozen state can be triggered by the mandatory proofs being missing in each second proof; and a disabled state can be triggered by the existence of conflicting second proofs.

[0056] When a user enables facial recognition in the United States, if the model signature is valid but the applicable region of the model does not include the United States, the facial recognition function will be set to rejected or frozen locally, and a reason code will be output to the client. The reason code indicates that the applicable region of the model does not include the United States. If the user is only missing user authorization records when enabling cloud recording, the cloud recording function will be set to pending authorization, the client will display the authorization process, and the certificate will be regenerated after authorization is completed.

[0057] The above method obtains the compliance certification requirements corresponding to the target risk function of the camera, and acquires the device operation status data related to the target risk function from the camera's local storage; based on the device operation status data, it generates the operation status compliance certificate of the target risk function; based on the comparison result between the operation status compliance certificate of the target risk function and the corresponding compliance certification requirements, it controls the status of the target risk function. This enables the status control of the target risk function to no longer rely on static platform policies or account permissions, but to make real-time decisions based on the comparison result between the current actual operating status of the device and the compliance requirements, thus avoiding the risk that the target risk function will continue to operate in violation of regulations after the compliance status changes.

[0058] In one embodiment, before determining the state of the target risk function based on the state of each second proof item, the method further includes: determining whether there is a conflict between the states of each second proof item; in response to a conflict between the states of some second proof items, selecting a target proof item from the conflicting second proof items according to the priority of each second proof item, so as to determine the state of the target risk function based on the state of the target proof item. The priority can be set according to the category of the proof item. For example, regional policy proof items take precedence over authorization proof items, security baseline proof items take precedence over configuration proof items, and privacy configuration proof items take precedence over experience proof items. Regional policy proof items include device region, model applicable region, etc.; authorization proof items include authorization identifier, authorization validity period, etc.; security baseline proof items include firmware hash, debug port status, etc.; configuration proof items include transmission encryption status, storage encryption status, etc.; privacy configuration proof items include privacy masking switch, log anonymization status, etc.; and experience proof items include client prompt text version, function call time, etc.

[0059] For example, if a user has authorized cloud recording, but the current regional policy does not allow cross-region storage, the final functional status will be downgraded or rejected; if the platform policy allows remote diagnostics, but the device debug port status is abnormal, the final functional status will be frozen.

[0060] In one embodiment, after determining the status of each target risk function based on the comparison results between the operational compliance proof of each target risk function and the corresponding compliance proof requirements, the method further includes: obtaining the monitoring results obtained by continuously monitoring the device operational data; in response to the monitoring results indicating that the device operational data has been updated, re-executing the generation of the operational compliance proof of the target risk function and its subsequent steps based on the device operational data; and / or, re-executing the generation of the operational compliance proof of the target risk function and its subsequent steps based on the device operational data at preset intervals.

[0061] Updates to device runtime data include, but are not limited to, firmware upgrades or rollbacks, AI algorithm replacements, privacy configuration changes, user authorization revocations, log anonymization configuration failures, changes in debug interface status, and changes in device or account region.

[0062] In this embodiment, upon detecting an update to the device's operational data and / or at a preset interval, the generation of operational compliance proof for the target risk function and subsequent steps are re-executed. This ensures that the compliance status reflects the current actual situation in real time during device operation, avoiding compliance risks caused by status changes.

[0063] In one embodiment, the method provided in this application further includes: after controlling the state of the target risk function, outputting function information. The function information includes the function name, current state, most recent proof time, proof digest number, reason code, missing proof item, and remedial action. For example, the function information might be: "Face recognition unavailable: Current area policy does not allow it." Another example is: "Cloud recording pending authorization: Lack of user consent record." Yet another example is: "Remote diagnostics frozen: Debug port status abnormal." And yet another example is: "Video export downgrade: Only desensitized segments are allowed to be exported."

[0064] Understandably, users with different permissions may see different functional information. Regular users can see the functional status and remediation entry; customer service personnel can see the reason code and the most recent verification time; R&D or compliance personnel can see the verification template number, failure verification items, and functional capability matrix version.

[0065] Furthermore, each of the following steps is performed: verifying the compliance requirements corresponding to the target risk function of the camera, and obtaining device operational data related to the target risk function from the camera's local storage; generating operational compliance proof for the target risk function based on the device operational data; controlling the status of the target risk function based on the comparison between the operational compliance proof and the corresponding compliance requirements, and generating an audit record. The audit record includes at least the proof number, function name, request source, request time, proof item status, gating result, reason code, differences before and after status change, and client confirmation record. Audit records can be saved as a hash chain or append-only log for easy tracing of proof status changes.

[0066] In one embodiment, the generation of operational compliance proof for the target risk function is executed locally. After the operational compliance proof is generated, it can be sent to the platform for verification. The platform can verify the proof summary signature to confirm that the summary was indeed generated by the corresponding camera or security zone; verify whether the device identity, device certificate, and binding relationship are consistent with the platform registration; verify whether the proof template number and functional capability matrix version are platform-approved versions; verify the proof timestamp, random number, or serial number to prevent old proofs from being replayed; verify whether the mandatory proof items are complete and whether the proof item status conforms to the template rules; verify whether the device region, account region, user authorization, package permissions, and regional policies are consistent with the platform records; and verify whether the proof chain or audit chain is continuous to prevent key gating events from being skipped or tampered with.

[0067] In a specific implementation scenario, a user attempts to enable cloud recording in the United States. The camera's local acquisition module first obtains information such as firmware hash, transmission encryption switch, storage encryption policy version, user authorization record, and device region. The compliance proof generation module generates a status digest containing the above information based on the cloud recording proof template and signs it. The functional capability matrix stipulates that enabling cloud recording for home users in the United States requires proof items such as user authorization, transmission encryption, storage encryption, and regional storage policy matching. The system comparison finds that if the user authorization record exists and is valid, and transmission and storage encryption are enabled, but the regional storage policy indicates that US data should be stored locally, while the current configuration is cloud storage, then the regional policy proof item is conflicting or abnormal. At this time, the gating module, according to the gating rules, sets the cloud recording status to downgrade, only allowing the upload of local event summaries, not the original video clips, and outputs a reason code (such as REGION_STORAGE_MISMATCH) and remedial actions (such as adjusting the storage policy) to the client. If the user subsequently withdraws the authorization, the dynamic re-verification module triggers re-verification. If the authorization verification item is found to be missing, the gating module switches the cloud recording status from downgraded to revoked, stops data uploading, and generates an audit record.

[0068] Please see Figure 2, Figure 2 This is a schematic diagram of the framework structure of one embodiment of the status control device for the camera function provided in this application.

[0069] The camera function status control device 20 includes an acquisition module 21, a generation module 22, and a control module 23. The acquisition module 21 is used to acquire the compliance certification requirements corresponding to the target risk function of the camera, and to acquire the device operation status data related to the target risk function from the camera's local storage. The generation module 22 is used to generate the operation status compliance certificate of the target risk function based on the device operation status data. The control module 23 is used to control the status of the target risk function based on the comparison result between the operation status compliance certificate of the target risk function and the compliance certification requirements corresponding to the target risk function.

[0070] It should be noted that the apparatus and method provided in the above embodiments belong to the same concept, and the specific ways in which each module and unit performs operations have been described in detail in the method embodiments, and will not be repeated here. In practical applications, the apparatus provided in the above embodiments can be assigned to different functional modules as needed, that is, the internal structure of the apparatus can be divided into different functional modules to complete all or part of the functions described above, and this is not a limitation.

[0071] Please see Figure 3 , Figure 3 This is a schematic diagram of the framework structure of one embodiment of the computer device provided in this application.

[0072] The computer device 30 includes a memory 31 and a processor 32 coupled to each other. The processor 32 is used to execute program instructions stored in the memory 31 to implement the steps of any of the above method embodiments.

[0073] In one embodiment, the computer device 30 may be a computer device, including but not limited to microcomputers, servers, laptops, tablets, mobile phones, etc., which are not limited here.

[0074] When the computer device 30 is a computer device, the processor 32 of the computer device 30 can also be called a CPU (Central Processing Unit). Alternatively, the processor 32 can also be an integrated circuit chip with signal processing capabilities; the processor 32 can also be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. A general-purpose processor can be a microprocessor or any conventional processor, etc.

[0075] In one embodiment, the computer device 30 may also be a processing chip, including but not limited to embedded processing chips, dedicated computing chips, and other chips with program parsing, instruction execution, and data processing capabilities, etc., which are not limited here.

[0076] When the computer device 30 is a processing chip, the processor 32 can be a control circuit or logic operation circuit integrated inside the control chip, and the memory 31 can be a storage unit built into the control chip.

[0077] Please see Figure 4 , Figure 4 This is a schematic diagram of the framework structure of one embodiment of the computer-readable storage medium provided in this application.

[0078] The computer-readable storage medium 40 stores program instructions 41 that can be executed by a processor, the program instructions 41 being used to implement the steps in any of the above method embodiments.

[0079] The storage media mentioned in this article include: USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks or optical disks, and other media that can store program code.

[0080] This application also provides a computer program product comprising a computer program that, when executed by a processor, can implement the steps described in any of the foregoing method embodiments. Specifically, the computer program product can be a software or program product containing a computer program, capable of running on a computing device or stored on any available medium.

[0081] In some embodiments, the functions or modules of the apparatus provided in this disclosure can be used to perform the methods described in the above method embodiments. The specific implementation can be referred to the description of the above method embodiments, and for the sake of brevity, it will not be repeated here.

[0082] The description of the various embodiments above tends to emphasize the differences between the various embodiments. The similarities or similarities between them can be referred to, and for the sake of brevity, they will not be repeated here.

[0083] In the several embodiments provided in this application, it should be understood that the disclosed methods and apparatus can be implemented in other ways. For example, the apparatus implementations 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, units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection of devices or units may be electrical, mechanical, or other forms.

[0084] 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, depending on actual needs.

[0085] Furthermore, the functional units in the various embodiments of this application 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. 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, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods in the various embodiments of this application.

[0086] Obviously, those skilled in the art should understand that the modules or steps of this application described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. Optionally, they can be implemented using computer-executable program code, and thus stored in a computer-readable storage medium for execution by a computing device, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Therefore, this application is not limited to any particular hardware and software combination.

[0087] If the technical solution of this application involves personal information, the product using this technical solution has clearly informed the user of the personal information processing rules and obtained the user's voluntary consent before processing the personal information. If the technical solution of this application involves sensitive personal information, the product using this technical solution has obtained the user's separate consent before processing the sensitive personal information, and also meets the requirement of "express consent". For example, at personal information collection devices such as cameras, clear and prominent signs are set up to inform users that they have entered the scope of personal information collection and that personal information will be collected. If an individual voluntarily enters the collection scope, it is deemed that they have agreed to the collection of their personal information; or on the personal information processing device, with clear signs / information informing users of the personal information processing rules, authorization is obtained from the individual through pop-up information or by asking the individual to upload their personal information; wherein, the personal information processing rules may include information such as the personal information processor, the purpose of personal information processing, the processing method, and the types of personal information processed.

[0088] The above description is merely an embodiment of this application and does not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.

Claims

1. A method of controlling a state of a camera function, characterized by, include: Obtain the compliance certification requirements corresponding to the target risk function of the camera, and obtain the device operation status data related to the target risk function from the camera's local storage; Based on the device's operational data, an operational compliance certificate for the target risk function is generated; Based on the comparison between the operational compliance proof of the target risk function and the corresponding compliance proof requirements, the state of the target risk function is controlled.

2. The method of claim 1, wherein, The status of the target risk function includes at least one of the following: enableable, pending authorization, downgraded, frozen, disabled, or revoked. The states are as follows: the enableable state indicates that the target risk function is fully available; the pending authorization state indicates that the target risk function requires real-time authorization before each activation; the downgraded state indicates that the target risk function provides services with limited capabilities; the frozen state indicates that the target risk function is suspended but retains configuration data; the disabled state indicates that the target risk function is completely unavailable; and the revoked state indicates that the target risk function has been terminated and related permission data has been cleared.

3. The method of claim 1, wherein, The operational compliance proof includes multiple first proof items and a first parameter value corresponding to each first proof item; the compliance proof requirement includes multiple second proof items and a second parameter value corresponding to each second proof item. The comparison between the operational compliance proof of the target risk function and the compliance proof requirements corresponding to each target risk function determines the status of each target risk function, including: Based on the first comparison result between each of the first proof items and each of the second proof items, and the second comparison result between each of the first parameter values ​​and each of the second parameter values, the state of each of the second proof items is determined. Based on the state of each of the second proof items, the state of the target risk function is determined.

4. The method of claim 3, wherein, The determination of the state of each second proof item based on the first comparison result between each first proof item and each second proof item, and the second comparison result between each first parameter value and each second parameter value, includes: Each of the second proof items is taken as a judgment item, and it is determined whether there is a first proof item in the first comparison result that is the same as the judgment item; In response to the absence of a first proof item identical to the item to be judged in the first comparison result, or in response to the presence of a first proof item identical to the item to be judged in the first comparison result and the first parameter value of the first proof item being empty, the state of the item to be judged is determined to be missing; In response to the presence of a first proof item identical to the item to be judged in the first comparison result, the first proof item identical to the item to be judged is taken as an item to be determined. In the second comparison result, it is determined whether the first parameter value of the item to be determined is consistent with the second parameter value of the item to be judged. In response to the consistency between the first parameter value of the item to be determined and the second parameter value of the item to be judged, the status of the item to be judged is determined to be passed. In response to a conflict between the first parameter value of the item to be determined and the second parameter value of the item to be judged, the status of the item to be judged is determined to be conflicted. In response to the first parameter value of the item to be determined being earlier than the expiration date, the status of the item to be judged is determined to be expired. In response to the first parameter value of the item to be determined exceeding a preset reasonable range, the status of the item to be judged is determined to be abnormal.

5. The method of claim 4, wherein, Determining the state of the target risk function based on the state of each of the second proof items includes: Obtain the triggering conditions corresponding to each state of the target risk function; wherein, the triggering conditions represent the states that each second proof item of the target risk function must satisfy in each state; For each of the aforementioned triggering conditions, determine whether the state of each of the second proof items satisfies the triggering condition; In response to the state of each of the second proof items satisfying the triggering condition, the state of the target risk function is determined to be the state corresponding to the triggering condition.

6. The method of claim 3, wherein, Before determining the state of the target risk function based on the state of each of the second proof items, the method further includes: In response to a conflict in the state of some of the second proof items, a target proof item is selected from the conflicting second proof items according to the priority of each second proof item, so as to determine the state of the target risk function based on the state of the target proof item.

7. The method of claim 1, wherein, The process of generating operational compliance proof for the target risk function based on the device's operational data includes: The operational data of the equipment is standardized. By combining the standardized equipment operational data, operational compliance proof for the target risk function is obtained.

8. The method of claim 1, wherein, The compliance verification requirements include multiple secondary verification items; The step of acquiring device operational data related to the target risk function from the camera's local storage includes: The device operating status data related to the target risk function is obtained by acquiring the first parameter value corresponding to each of the second proof items from the camera locality.

9. The method of claim 1, wherein, After determining the status of each target risk function based on the comparison results between the operational compliance proof of each target risk function and the corresponding compliance proof requirements of each target risk function, the method further includes: Obtain the monitoring results obtained by continuously monitoring the device's operational data; in response to the monitoring results indicating that the device's operational data has been updated, re-execute the process of generating the operational compliance certificate for the target risk function based on the device's operational data and subsequent steps. And / or, at preset intervals, re-execute the process based on the device's operational data to generate operational compliance proof for the target risk function and its subsequent steps.

10. The method of claim 1, wherein, Before obtaining the compliance certification requirements corresponding to each of the target risk functions, and before obtaining the device operating status data related to the target risk functions of the camera from the camera's local storage, the method further includes: Obtain the various functions possessed by the camera; Based on a preset set of target risk functions, determine whether each function is a target risk function.

11. A computer device, comprising: The method includes a memory and a processor, wherein the memory stores program instructions and the processor executes the program instructions to implement the method according to any one of claims 1 to 10.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores program instructions that can be executed by a processor to implement the method of any one of claims 1 to 10.