Face data delivery method, device and equipment
By acquiring modeling data and deleting images after distributing facial data through the software management platform, the risk of leakage during the facial data distribution process is resolved, enabling fast, secure data transmission and efficient data management.
Patent Information
- Application Number
- CN202210760333.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-06-30
- Publication Date
- 2025-12-05
- Estimated Expiration
- 2042-06-30
AI Technical Summary
Existing technologies are prone to leakage risks during the distribution of facial data, and the management platform and devices need to store facial images, which increases the risk of privacy leaks.
After the facial data is sent to the device in the form of images through the software management platform, the modeling data of the device is obtained and the local facial images are deleted. At the same time, the association between the modeling data and the algorithm version identifier is stored locally on the platform to ensure that the modeling data is only sent to eligible devices.
It effectively reduces the risk of facial data leakage, complies with legal and regulatory requirements, and improves the speed of facial data distribution and application efficiency, while reducing reliance on modeling servers.
Smart Images

Figure CN115061631B_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of data processing technology, and in particular to a method, apparatus, and device for distributing facial data. Background Technology
[0002] Currently, it is becoming increasingly common to use facial data for convenient and quick authorization, unlocking, and payment. However, this also leads to privacy risks due to the lack of proper management of facial data.
[0003] Currently, when management platforms distribute facial data to devices for specific applications, they typically either directly send the corresponding image to the device or send the image to a dedicated modeling server for facial modeling, after which the modeling server distributes the facial data. However, directly sending the image to the device requires the management platform to store the image, and the device also stores the image upon receiving it. Sending the image to the modeling server also requires the management platform to store the image, and the modeling server also stores the image. This greatly increases the risk of user facial data leakage. Summary of the Invention
[0004] The main objective of this invention is to provide a method, apparatus, and device for distributing facial data, aiming to reduce the risk of facial data leakage.
[0005] To achieve the above objectives, the present invention provides a method for distributing facial data, wherein the method is applied to a software management platform, and the method includes the following steps:
[0006] The first face data, which is an image, is sent to the first device, which includes a first face data application device or a face data modeling server.
[0007] After obtaining the modeling data corresponding to the first face data from the first device, a face image deletion command is sent to the first device so that the first device can delete the first face data;
[0008] Delete the first face data locally on the software management platform.
[0009] In one feasible embodiment, the method further includes:
[0010] Obtain the algorithm version identifier of the first device;
[0011] The modeling data obtained from the first device is used as second face data of type modeling data;
[0012] The second face data and the algorithm version identifier are associated and stored locally on the software management platform.
[0013] In one feasible embodiment, the method further includes:
[0014] When it is necessary to send face data to a second face data application device, it is determined whether the second face data application device meets the preset algorithm version conditions, wherein the algorithm version conditions are that the algorithm version identifier of the second face data application device is the same as the algorithm version identifier associated with the second face data.
[0015] If it is determined that the second face data application device meets the algorithm version conditions, then the second face data is sent to the second face data application device;
[0016] If it is determined that the second face data application device does not meet the algorithm version conditions, the second face data will be marked as invalid data and a corresponding prompt will be output.
[0017] In one feasible embodiment, the step of sending the first face data, which is of image type, to the first face data application device includes:
[0018] When it is determined that the software management platform has first face data of image type locally, the first face data is marked as to be deleted locally on the software management platform, and the first face data is sent to the first face data application device.
[0019] In one feasible embodiment, the step of deleting the first face data locally on the software management platform includes:
[0020] After confirming that the first face data has been successfully sent to the first face data application device, the first face data marked as to be deleted is deleted locally on the software management platform.
[0021] In one feasible embodiment, the method further includes:
[0022] When it is determined that sending the first face data to the first face data application device has failed, the deletion mark of the first face data is updated to the non-deletion mark locally on the software management platform.
[0023] In one feasible embodiment, the number of the first face data application devices is greater than one, and the method further includes:
[0024] After sending the first face data to any target device among the first face data application devices, it is determined whether the modeling data corresponding to the first face data is obtained from other first face data application devices that successfully sent the first face data, wherein the other first face data application devices and the target device have the same algorithm version identifier.
[0025] If not, then obtain the modeling data from the target device;
[0026] If so, then the acquisition of the modeling data from the target device is abandoned;
[0027] The step of deleting the first face data locally on the software management platform includes:
[0028] Once it is confirmed that the first face data has been successfully sent to each of the first face data application devices, the first face data is deleted locally on the software management platform.
[0029] Furthermore, to achieve the above objectives, the present invention also provides a face data distribution device, which is applied to a software management platform, and the device includes:
[0030] The face delivery module is used to send first face data, which is an image, to a first device, the first device including a first face data application device or a face data modeling server;
[0031] The face deletion module is used to obtain the modeling data corresponding to the first face data from the first device, send a face image deletion command to the first device so that the first device can delete the first face data; and delete the first face data locally on the software management platform.
[0032] In one feasible embodiment, the device further includes:
[0033] The face modeling acquisition module is used to acquire the algorithm version identifier of the first device; to use the modeling data acquired from the first device as second face data with the data type modeling data; and to associate and store the second face data and the algorithm version identifier locally on the software management platform.
[0034] In one feasible embodiment, the face delivery module is further configured to, when it is necessary to deliver face data to the second face data application device, determine whether the second face data application device meets a preset algorithm version condition, wherein the algorithm version condition is that the algorithm version identifier of the second face data application device is the same as the algorithm version identifier associated with the second face data; if it is determined that the second face data application device meets the algorithm version condition, then the second face data is delivered to the second face data application device; and if it is determined that the second face data application device does not meet the algorithm version condition, then the second face data is marked as invalid data and a corresponding prompt is output.
[0035] In one feasible embodiment, the face data delivery module is further configured to, when determining that a first face data of image type exists locally on the software management platform, mark the first face data as to be deleted locally on the software management platform and deliver the first face data to the first face data application device.
[0036] In one feasible embodiment, the face deletion module is further configured to delete the first face data marked as to be deleted locally on the software management platform after determining that the first face data has been successfully sent to the first face data application device.
[0037] In one feasible embodiment, the device further includes a marker update module, which, when it is determined that sending the first face data to the first face data application device has failed, updates the marker to be deleted to a marker not to be deleted locally on the software management platform.
[0038] In one feasible embodiment, the number of the first face data application devices is greater than one. The face modeling acquisition module is further configured to, after sending the first face data to any target device among the first face data application devices, determine whether modeling data corresponding to the first face data has been obtained from other first face data application devices that successfully sent the first face data, wherein the other first face data application devices and the target device have the same algorithm version identifier; if not, then obtain the modeling data from the target device; and if yes, then abandon the acquisition of the modeling data from the target device.
[0039] The face deletion module is further configured to delete the first face data locally on the software management platform when it is determined that the first face data has been successfully sent to each of the first face data application devices.
[0040] Each functional module of the face data distribution device of the present invention implements the steps of the face data distribution method described above during operation.
[0041] In addition, to achieve the above objectives, the present invention also provides a face data distribution device, which includes: a memory, a processor, and a face data distribution program stored in the memory and executable on the processor. When the face data distribution program is executed by the processor, it implements the steps of the face data distribution method described above.
[0042] In addition, to achieve the above objectives, the present invention also proposes a computer storage medium storing a face data distribution program, wherein the face data distribution program, when executed by a processor, implements the steps of the face data distribution method described above.
[0043] In addition, to achieve the above objectives, embodiments of the present invention also provide a computer program product containing instructions that, when run on a computer, cause the computer to execute the steps of the face data distribution method described above.
[0044] In this embodiment of the invention, when the software management platform sends face data to the face data application device, it first sends the first face data, which is an image, to the first device. The first device includes a first face data application device or a face data modeling server. Then, after obtaining the modeling data corresponding to the first face data from the first device, it sends a face image deletion command to the first device so that the first device can delete the first face data. The first face data is then deleted locally on the software management platform.
[0045] Thus, when the software management platform sends a face image to the first device, the present invention obtains the modeling data of the face image from the first device after the face image is first sent to the first device, and immediately deletes the face image locally on the first device and the management platform, thereby effectively reducing the risk of face data leakage and complying with the requirements of relevant laws and regulations.
[0046] Furthermore, after acquiring the modeling data corresponding to a facial image through a software management platform, this invention can directly and quickly distribute the modeling data when subsequently sending the same facial data to facial data application devices. Therefore, compared to sending facial images to facial data application devices or using a dedicated modeling server to model facial data and then sending the data, this invention achieves a faster facial data distribution speed and eliminates the need for the complexities of using a modeling server, thus effectively improving the efficiency of facial data application. Attached Figure Description
[0047] Figure 1 This is a schematic diagram of the hardware operating environment involved in the embodiments of the present invention;
[0048] Figure 2 This is a flowchart illustrating an embodiment of the face data distribution method of the present invention.
[0049] Figure 3 This is a schematic diagram illustrating the specific application process of an embodiment of the face data distribution method of the present invention;
[0050] Figure 4 This is a schematic diagram of the functional modules involved in an embodiment of the face data distribution device of the present invention.
[0051] The realization of the objective, functional features and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation
[0052] It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.
[0053] like Figure 1 As shown, Figure 1 This is a schematic diagram of the device structure of the hardware operating environment involved in the embodiments of the present invention.
[0054] It should be noted that the face data distribution device in this embodiment of the invention can be integrated as a software management platform to perform the operation of distributing face data to application devices. Specifically, the device can be a smartphone, personal computer, server, or other devices, and no specific limitation is made here.
[0055] like Figure 1 As shown, the device for transmitting facial data may include: a processor 1001, such as a CPU; a network interface 1004; a user interface 1003; a memory 1005; and a communication bus 1002. The communication bus 1002 is used to establish communication between these components. The user interface 1003 may include a display screen or an input unit such as a keyboard; optionally, the user interface 1003 may also include a standard wired interface or a wireless interface. The network interface 1004 may optionally include a standard wired interface or a wireless interface (such as a Wi-Fi interface). The memory 1005 may be high-speed RAM or non-volatile memory, such as a disk drive. Optionally, the memory 1005 may also be a storage device independent of the aforementioned processor 1001.
[0056] Those skilled in the art will understand that Figure 1 The device structure shown does not constitute a limitation on the device for distributing facial data. It may include more or fewer components than shown, or combine certain components, or have different component arrangements.
[0057] like Figure 1 As shown, the memory 1005, serving as a computer storage medium, may include an operating system, a network communication module, a user interface module, and a program for distributing facial data. The operating system is a program that manages and controls the device's hardware and software resources, supporting the facial data distribution program and the operation of other software or programs. Figure 1 In the device shown, the user interface 1003 is mainly used for data communication with the client; the network interface 1004 is mainly used for establishing a communication connection with the server; and the processor 1001 can be used to call the face data distribution program stored in the memory 1005 and perform the following operations:
[0058] The first face data, which is an image, is sent to the first device, which includes a first face data application device or a face data modeling server.
[0059] After obtaining the modeling data corresponding to the first face data from the first device, a face image deletion command is sent to the first device so that the first device can delete the first face data;
[0060] Delete the first face data locally on the software management platform.
[0061] Furthermore, the processor 1001 can also be used to call the face data distribution program stored in the memory 1005, and also perform the following operations:
[0062] Obtain the algorithm version identifier of the first device;
[0063] The modeling data obtained from the first device is used as second face data of type modeling data;
[0064] The second face data and the algorithm version identifier are associated and stored locally on the software management platform.
[0065] Furthermore, the processor 1001 can also be used to call the face data distribution program stored in the memory 1005, and also perform the following operations:
[0066] When it is necessary to send face data to a second face data application device, it is determined whether the second face data application device meets the preset algorithm version conditions, wherein the algorithm version conditions are that the algorithm version identifier of the second face data application device is the same as the algorithm version identifier associated with the second face data.
[0067] If it is determined that the second face data application device meets the algorithm version conditions, then the second face data is sent to the second face data application device;
[0068] If it is determined that the second face data application device does not meet the algorithm version conditions, the second face data will be marked as invalid data and a corresponding prompt will be output.
[0069] Furthermore, the processor 1001 can also be used to call the face data distribution program stored in the memory 1005, and also perform the following operations:
[0070] When it is determined that the software management platform has first face data of image type locally, the first face data is marked as to be deleted locally on the software management platform, and the first face data is sent to the first face data application device.
[0071] Furthermore, the processor 1001 can also be used to call the face data distribution program stored in the memory 1005, and also perform the following operations:
[0072] After confirming that the first face data has been successfully sent to the first face data application device, the first face data marked as to be deleted is deleted locally on the software management platform.
[0073] Furthermore, the processor 1001 can also be used to call the face data distribution program stored in the memory 1005, and also perform the following operations:
[0074] When it is determined that sending the first face data to the first face data application device has failed, the deletion mark of the first face data is updated to the non-deletion mark locally on the software management platform.
[0075] Furthermore, since the number of the first face data application devices is greater than one, the processor 1001 can also be used to call the face data distribution program stored in the memory 1005, and also perform the following operations:
[0076] After sending the first face data to any target device among the first face data application devices, it is determined whether the modeling data corresponding to the first face data is obtained from other first face data application devices that successfully sent the first face data, wherein the other first face data application devices and the target device have the same algorithm version identifier.
[0077] If not, then obtain the modeling data from the target device;
[0078] If so, then the acquisition of the modeling data from the target device is abandoned;
[0079] Processor 1001 can also be used to call the face data delivery program stored in memory 1005, and also perform the following operations:
[0080] Once it is confirmed that the first face data has been successfully sent to each of the first face data application devices, the first face data is deleted locally on the software management platform.
[0081] Based on the above structure, various embodiments of the face data distribution method of the present invention are proposed.
[0082] Please refer to Figure 2 , Figure 2 This is a flowchart illustrating the first embodiment of the method for distributing facial data according to the present invention. It should be noted that although the logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than that shown here.
[0083] Furthermore, in this embodiment, the execution entity of the face data distribution method of the present invention can be the face data distribution device integrated as a software management platform, such as a smartphone, personal computer, server, or other terminal device. This embodiment does not impose any limitations. The following description of each embodiment will directly use the software management platform to represent the aforementioned execution entities.
[0084] Furthermore, in this embodiment, the face data distribution method of the present invention is applied to a software management platform distributing face data to face data application devices, so that the application devices can perform face recognition based on the face data to confirm user authorization or perform applications such as verifying user spending. The application device can specifically be an access control system, a face payment device, or even a smartphone, etc. It should be understood that the face data distribution method of the present invention does not limit the specific type of application device or the specific content of the application performed by the application device based on the face data.
[0085] As shown in Figure 2, the method for distributing facial data according to the present invention includes:
[0086] Step S10: Send the first face data, which is an image, to the first device, which includes a first face data application device or a face data modeling server.
[0087] In one embodiment, when the software management platform needs to send face data to one or more first devices, it immediately sends the first face data to the first device when it determines that the face data stored locally is exactly the first face data with the data type of image.
[0088] It should be noted that, in this embodiment, the first device is one or more of the above-mentioned application devices, and the first device includes: a first face data application device that applies the face data, or a face data modeling server that models the face image to obtain corresponding modeling data.
[0089] Furthermore, in this embodiment, the facial data sent by the software management platform to the first device includes first facial data of image type and / or second facial data of modeling data type. When determining the data type of the facial data to be sent to the first device stored locally, the software management platform receives the start command of the facial data sending process and responds immediately to begin determining whether the data type of the facial data to be sent to the first device is an image or modeling data.
[0090] It should be noted that, in one embodiment, the software management platform can pre-configure the permission set for personnel and application devices. When it receives the start command for the face data distribution process, it can determine the face data of the personnel that need to be distributed to the application devices based on the permission set, and integrate the face data with one or more application devices to form a list. In subsequent steps, the face data will be distributed to the corresponding application devices one by one according to the list.
[0091] Furthermore, in one embodiment, such as Figure 3 As shown in the application process, before responding to the aforementioned startup command to begin determining facial data, the software management platform needs to determine whether the preset GDPR (General Data Protection Regulation) enable option is currently enabled based on the authorization indication carried by the startup command. Only if the enable option is determined to be enabled will the type of facial data be determined to execute the subsequent process of sending the facial data to the application device. This process avoids the risk of facial data leakage while quickly sending the facial data to the application device. Otherwise, if the software management platform determines that the enable option is not enabled, it does not need to continue executing the subsequent process of sending the facial data to the application device, or it can only complete the process of sending the facial data by other means such as sending the facial data through a modeling server.
[0092] Step S20: After obtaining the modeling data corresponding to the first face data from the first device, send a face image deletion command to the first device so that the first device can delete the first face data;
[0093] In this embodiment, after the software management platform sends the first face data to one or more first devices, it further obtains the modeling data corresponding to the first face data from one or more of the first devices. Upon confirming that the first face data has been successfully sent to one or more first devices, it sends a face image deletion command to one or more first devices. Thus, after each first device receives the first face data from the software management platform and performs modeling to obtain the corresponding modeling data, it can further delete the first face data (which is an image in its local data set) upon receiving the face image deletion command. Consequently, each of the one or more first devices retains only the modeling data of the first face data locally.
[0094] Step S30: Delete the first face data locally on the software management platform.
[0095] In this embodiment, after the software management platform obtains the modeling data corresponding to the first face data from one of the first devices or multiple first devices, it further deletes the first face data to be deleted locally on the software management platform while issuing a face image deletion command to the one or multiple first devices (or afterward). In this way, only the modeling data corresponding to the first person data is retained locally on the software management platform.
[0096] In this embodiment, when the software management platform needs to send face data to one or more first devices, it immediately sends the first face data to the first device upon determining that the locally stored face data is indeed image-type first face data. Then, the software management platform further retrieves the modeling data corresponding to the first face data from one or more of the first devices. Furthermore, upon confirming that the sending of the first face data to one or more first devices has been successful, it sends a face image deletion command to one or more first devices. Thus, after each first device receives the first face data from the software management platform and performs modeling to obtain the corresponding modeling data, it can further delete the image-type first face data from its local storage upon receiving the face image deletion command. Consequently, one or more first devices only retain the modeling data of the first face data locally. Finally, the software management platform also deletes the first face data that has been pre-marked for deletion locally, thus retaining only the modeling data corresponding to the first face data locally.
[0097] Thus, when the software management platform sends a face image to the first device, the present invention obtains the modeling data of the face image from the first device after the face image is sent to the first device, and immediately deletes the face image locally on the first device and the management platform, thereby effectively reducing the risk of face data leakage and complying with the requirements of relevant laws and regulations.
[0098] Furthermore, based on the first embodiment of the face data distribution method of the present invention described above, a second embodiment of the face data distribution method of the present invention is proposed.
[0099] In this embodiment, the face data transmission method of the present invention, after the above-described step of "sending the first face data, which is of image type, to the first device", may further include:
[0100] Step A: Obtain the algorithm version identifier of the first device;
[0101] Step B involves using the modeling data obtained from the first device as second face data with the data type "modeling data".
[0102] Step C: Associate the second face data with the algorithm version identifier and store it locally on the software management platform.
[0103] In one embodiment, when the software management platform obtains the modeling data corresponding to the first face data from one of the aforementioned first devices, or when it obtains the modeling data from one of the aforementioned multiple first devices, it also synchronously reads the algorithm version identifier of the face modeling algorithm used by the first device to model the first face data from the running memory provided by the one or more first devices. Then, after obtaining the modeling data and the algorithm version identifier, the software management platform immediately treats the modeling data as second face data with the data type modeling data, and further encrypts and associates the second face data and the algorithm version identifier and stores them locally on the software management platform.
[0104] In this embodiment, when the software management platform obtains the modeling data corresponding to the first face data from the first device, it also simultaneously obtains the algorithm version identifier of the modeling algorithm used by the first device to model the first face data. Thus, the software management platform uses the obtained modeling data as the second face data, encrypts the second face data together with the obtained algorithm version identifier, and stores them locally on the software management platform. In this way, when face data needs to be sent to other application devices in the future, the second face data, which is modeling data, can be sent directly.
[0105] Furthermore, in one embodiment, the method for distributing facial data according to the present invention may further include:
[0106] Step D: When it is necessary to send face data to the second face data application device, determine whether the second face data application device meets the preset algorithm version conditions, wherein the algorithm version conditions are that the algorithm version identifier of the second face data application device is the same as the algorithm version identifier associated with the second face data.
[0107] It should be noted that, in this embodiment, the second face data application device is any face data application device other than the first device mentioned above.
[0108] Furthermore, in this embodiment, the preset algorithm version condition can specifically be: the algorithm version identifier associated with the second face data stored locally on the software management platform must be consistent with the algorithm version identifier of the face modeling algorithm configured on the application device itself. It should be understood that the face modeling algorithm of the application device mentioned in the various embodiments of the face data distribution method of this invention can specifically be any algorithm currently available on the market that converts face data of type face image into modeling data.
[0109] In one embodiment, when the software management platform determines that it needs to send face data to one or more second face data application devices, if it determines that the face data stored locally at this time is second face data of the data type modeling data, it immediately determines whether the one or more second face data application devices meet the preset algorithm version conditions.
[0110] Step E: If it is determined that the second face data application device meets the algorithm version conditions, then the second face data is sent to the second face data application device.
[0111] In this embodiment, the software management platform will only directly send the second face data, which is of the data type of modeling data, stored locally to the corresponding one or more second face data application devices if it determines that one or more of the above-mentioned second face data application devices meet the above-mentioned algorithm version conditions.
[0112] Step F: If it is determined that the second face data application device does not meet the algorithm version conditions, then the second face data is marked as invalid data and a corresponding prompt is output.
[0113] In this embodiment, when the software management platform detects that the algorithm version identifier of the locally stored second face data management is different from the algorithm version identifier of one or more second face data application devices, and thus determines that one or more second face data application devices do not meet the algorithm version conditions, the software management platform marks the second face data as invalid data for the one or more second face data application devices, and outputs a corresponding prompt to send face data to the second face data application device.
[0114] For example, such as Figure 3 The application process shown involves the software management platform determining that the data to be sent to the second face data application device is modeling data. The platform compares the algorithm version identifier associated with the second face data with the algorithm version identifier configured on the second face data application device to determine if the second face data application device meets the aforementioned algorithm version conditions (the illustration shows no human face image, but contains face data based on the current device's algorithm version). In this case, the software management platform directly sends the second face data (the template data shown) to the second face data application device, resulting in a success or failure message.
[0115] Furthermore, when the software management platform compares the algorithm version identifier associated with the second face data with the algorithm version identifier configured on the second face data application device, and determines that the second face data application device does not meet the aforementioned algorithm version conditions, thus confirming that the face data to be sent to the application device does not exist, it outputs a corresponding error message and marks the face data of the personnel with the corresponding permissions for the application device in the aforementioned permission set as invalid face data. Alternatively, when the software management platform sends the second face data to the second face data application device but the result is a failure, the software management platform also outputs a corresponding error message and marks the current second face data as an invalid template.
[0116] In addition, in one embodiment, the software management platform can also directly send the modeling data to the aforementioned application device when it determines that the face data stored locally is second face data of the data type modeling data.
[0117] In this embodiment, when the software management platform obtains the modeling data corresponding to the first face data from the first device, it also simultaneously obtains the algorithm version identifier of the modeling algorithm used by the first device to model the first face data. Thus, the software management platform uses the obtained modeling data as the second face data, encrypts the second face data together with the obtained algorithm version identifier, and stores them locally on the software management platform. In this way, when face data needs to be sent to other application devices in the future, the second face data, which is modeling data, can be sent directly.
[0118] Therefore, compared to sending face images to application devices or sending images to a dedicated modeling server for face data modeling and then having the server send the face data, this invention can achieve a faster face data sending speed and does not require the complexity of sending face data through a modeling server, thereby effectively improving the application efficiency of face data.
[0119] Furthermore, based on the first and / or second embodiments of the face data distribution method of the present invention described above, a third embodiment of the face data distribution method of the present invention is proposed.
[0120] In this embodiment, the step of "sending the first face data, which is of image type, to the first face data application device" in step S10 above may include:
[0121] When it is determined that the software management platform has first face data of image type locally, the first face data is marked as to be deleted locally on the software management platform, and the first face data is sent to the first face data application device.
[0122] In this embodiment, when the software management platform determines that it needs to send first face data of image type to one or more first face data application devices among the first devices, the software management platform first marks the first face data as data to be deleted locally. Then, the software management platform sends the first face data to one or more first face data application devices by transmitting image data.
[0123] Furthermore, in a feasible embodiment, step S30 above, deleting the first face data locally on the software management platform, may include:
[0124] After confirming that the first face data has been successfully sent to the first face data application device, the first face data marked as to be deleted is deleted locally on the software management platform.
[0125] In this embodiment, when the software management platform sends the first face data to one or more first face data application devices, if it determines that the first face data has been successfully sent to one or more first face data application devices by accessing the running memory it provides to those devices, and further obtains the modeling data corresponding to the first face data from one of the first face data application devices, or obtains the modeling data from one of the multiple first face data application devices, the software management platform deletes the first face data that has been marked as data to be deleted and stored locally.
[0126] For example, in this embodiment, when the software management platform determines that it needs to send the first face data 1 of person 1 to the first face data application device 1, the software management platform marks the first face data 1 as data to be deleted locally, and then sends the face data 1 to the first face data application device 1 using a channel for transmitting image data (with wider bandwidth). After receiving the first face data 1, the first face data application device 1 performs face modeling processing on the first face data 1, which is of image data type, locally using its own configured face modeling algorithm to obtain face data 2, which is of modeling data type. Then, the software management platform further obtains face data 2 from the first face data application device 1 as the second face data 3 of person 1, which is of modeling data type. The second face data 3 and the algorithm version identifier of the face modeling algorithm configured by the first face data application device 1 are encrypted and associated and stored locally on the software management platform. Afterwards, the software management platform deletes the first face data 1 of person 1, which has been marked as data to be deleted, locally.
[0127] Furthermore, in a feasible embodiment, the step of "sending a face image deletion instruction to the first device so that the first device can delete the first face data" in step S20 above may include:
[0128] When it is determined that the first face data has been successfully sent to the first face data application device, a face image deletion command is sent to the first face data application device so that the first device can delete the first face data.
[0129] In this embodiment, after the software management platform sends the first face data to one or more application devices in the manner of transmitting image data, if it further determines that the one or more first face data application devices have already performed face modeling on the first face data based on their own configured face modeling algorithm to obtain the corresponding modeling data, and thus determines that the current sending of the first face data to the one or more first face data application devices has been successful, the software management platform further sends a face image deletion command to the one or more first face data application devices, thereby controlling the one or more first face data application devices to delete the first face data of image type locally.
[0130] For example, such as Figure 3 As shown, when the software management platform sends the first face data, which is an image, to the first face data application device, it also marks the first face data as a face image to be deleted. Then, the software management platform can obtain the modeling data corresponding to the first face data from the first face data application device to confirm that the face data has been successfully sent to the first face data application device. After that, the software management platform can further send a face image deletion command to the first face data application device, so that the first face data application device can delete the first face data, which is an image, received previously locally.
[0131] Furthermore, as a feasible embodiment, the method for distributing facial data according to the present invention may further include:
[0132] When it is determined that sending the first face data to the first face data application device has failed, the deletion mark of the first face data is updated to the non-deletion mark locally on the software management platform.
[0133] In this embodiment, after the software management platform sends the first face data to one or more application devices in the manner of transmitting image data, if it further determines that the one or more application devices have not received the first face data, the software management platform determines that the current sending of the first face data to the one or more application devices has failed. Therefore, the software management platform will locally re-mark the first face data, which has already been marked as pending deletion, as not to be deleted, thus updating the pending deletion mark to a non-deletion mark. Subsequently, the software management platform can resend the first face data to the one or more application devices.
[0134] It should be noted that, as one possible implementation, the various face data application devices (including the first face data application device and the second face data application device in the first device and the face data modeling server mentioned above) and the face data modeling server may be unable to receive the first face data or the second face data due to their own network problems.
[0135] In this embodiment, after successfully sending facial data to the application device, the present invention immediately controls the deletion of the facial image received from the receiving facial data and also deletes the facial image locally, thereby effectively reducing the risk of facial data leakage and complying with relevant laws and regulations. Furthermore, even if the current attempt to send a facial image to the application device fails, the software management platform still saves the facial image locally. This ensures that facial images can be successfully resent to the same application device or other application devices in the future, effectively improving the stability of facial data transmission to application devices.
[0136] Furthermore, based on the first, second, and / or third embodiments of the face data distribution method of the present invention described above, a fourth embodiment of the face data distribution method of the present invention is proposed.
[0137] In this embodiment, the number of application devices is greater than one. Based on this, the method for distributing facial data according to the present invention may further include:
[0138] Step F: After sending the first face data to any target device among the first face data application devices, determine whether the modeling data corresponding to the first face data is obtained from other first face data application devices that successfully sent the first face data, wherein the other first face data application devices and the target device have the same algorithm version identifier.
[0139] In this embodiment, when the software management platform sends first face data (of type image) to multiple first face data application devices in batches according to a pre-configured list, the software management platform, after sending the first face data to one of the multiple first face data application devices, accesses the application memory it provides to the multiple first face data application devices to confirm whether it has obtained the modeling data corresponding to the first face data from another first face data application device with the same algorithm version identifier as the target device.
[0140] It should be noted that, in this embodiment, the software management platform can synchronously send first face data to multiple first face data application devices through multi-threaded parallel operation. In this way, the application memory provided by the software management to multiple first face data application devices can be shared memory among multiple processes.
[0141] Furthermore, in one embodiment, when the software management platform simultaneously distributes first face data (of type image) to multiple first face data application devices in batches, it can first detect whether the algorithm version identifiers of the multiple first face data application devices are the same. Then, if the multiple algorithm version identifiers are found to be the same, the first face data is simultaneously distributed to the multiple first face data application devices by transmitting image data. This allows each first face data application device to perform face modeling locally based on its own configured identical face modeling algorithm for the face data it receives. In this way, when the software management platform obtains the modeling data corresponding to the first face data, it can obtain only one set of modeling data from the first device among the multiple first face data application devices that receives the first face data and completes face data modeling, without having to repeatedly obtain modeling data from each device.
[0142] Step G: If not, obtain the modeling data from the target device;
[0143] In this embodiment, if the software management platform determines by accessing the aforementioned running memory that it has not yet obtained the modeling data corresponding to the first face data from other first face data application devices, the software management platform will further obtain the modeling data obtained by the target device through its own configured face modeling algorithm on the first face data, and obtain the algorithm version identifier of the face modeling algorithm. The software management platform will then encrypt and store the obtained modeling data as the second face data and the algorithm version identifier together locally.
[0144] After acquiring the modeling data on the target device, the software management platform can send a face image deletion command to the target device so that the target device can delete the first face data.
[0145] If so, then the acquisition of the modeling data from the target device is abandoned;
[0146] In this embodiment, if the software management platform determines, by accessing the aforementioned running memory, that it has already obtained the modeling data corresponding to the first face data from other first face data application devices, then the software management platform will not repeatedly obtain the same modeling data from the target device. At this time, the software management platform can directly send a face image deletion command to the target device so that the target device can delete the first face data.
[0147] In other words, when there are multiple first face data application devices with the same algorithm version identifier, the method of "obtaining the modeling data corresponding to the first face data from one of the multiple first face data application devices" is used to achieve "obtaining the modeling data corresponding to the first face data from the multiple first face data application devices". Furthermore, after obtaining the modeling data corresponding to the first face data, after successfully sending the data to any first face data application device with the same algorithm version identifier, a face image deletion command is sent to that first face data application device for it to delete the first face data.
[0148] Furthermore, step S30 above, deleting the first face data locally on the software management platform, may further include:
[0149] Once it is confirmed that the first face data has been successfully sent to each of the first face data application devices, the first face data is deleted locally on the software management platform.
[0150] In this embodiment, when the software management platform sends first face data of image type to multiple first face data application devices in batches, the software management platform needs to access the aforementioned running memory to confirm that the first face data has been successfully sent to all the first face data application devices before deleting the first face data that has been marked as to be deleted stored locally on the software management platform.
[0151] In this embodiment, when the software management platform simultaneously distributes first face data (image type) to multiple application devices in batches, it only needs to retrieve the face data (modeling data type) and the algorithm version identifier of the face modeling algorithm from any one of the application devices. Then, it associates and stores the face data (modeling data type) and the algorithm version identifier locally on the software management platform. This effectively avoids the resource consumption caused by the software management platform repeatedly retrieving the same modeling data across multiple application devices with the same face modeling algorithm. Furthermore, when subsequently distributing face data to application devices with the same face modeling algorithm, the locally stored modeling data can be used directly, thereby accelerating the face data distribution speed and significantly improving the efficiency of face data distribution.
[0152] Furthermore, based on the first, second, third, and / or fourth embodiments of the face data distribution method of the present invention described above, a fifth embodiment of the face data distribution method of the present invention is proposed.
[0153] In this embodiment, before sending the first face data, which is of image type, to the first device in step S10 above, the face data sending method of the present invention may further include:
[0154] Facial image data is collected and encrypted and stored locally on the software management platform as first facial data with data type image.
[0155] In this embodiment, before configuring the permission set for personnel and application devices, the software management platform can collect personnel facial image data through its connected hardware devices used to collect personnel facial image data, such as dedicated cameras, smartphones, tablets, or computers with corresponding software applications installed, or data interfaces used to receive facial image data. Afterwards, the software management platform encrypts the collected facial image data and stores it in local memory as the first facial data with the data type image, using the person as an index identifier, for subsequent retrieval.
[0156] Furthermore, it should be noted that in this embodiment and other embodiments of the face data distribution method of the present invention, the encryption algorithm used by the software management platform when encrypting and storing the face data can be any data encryption algorithm currently available on the market, such as AES (Advanced Encryption Standard), etc. It should be understood that, based on different design needs of practical applications, the software management platform can, of course, adopt any different encryption algorithm to encrypt and store the face data in different feasible implementations. The face data distribution method of the present invention does not limit the specific type and usage process of the encryption algorithm adopted by the software management platform.
[0157] In addition, as a feasible implementation method, the software management platform can also collect facial image data of personnel through the aforementioned application device. That is, the personnel use the image acquisition device configured on the application device to take facial image photos. After the application device captures the personnel's facial image data, it further uploads the facial image data to the software management platform. In this way, the software management platform obtains the personnel's facial image data.
[0158] Furthermore, in one feasible embodiment, the aforementioned face modeling data server is only used to perform face modeling on face data of image type to obtain face data of modeling data type. After the software management platform sends the first face data of image type to the pre-connected face modeling data server, it further calls the modeling server to perform face modeling on the first face data, thereby obtaining the second face data of the person of modeling data type. Then, the software management platform encrypts the second face data together with the algorithm version identifier of the face modeling algorithm used by the modeling server to perform face modeling on the first face image data, and stores them locally on the software management platform. In addition, the software management platform further deletes the first face data locally on the software management platform, and similarly sends a face image deletion command to the modeling server so that the modeling server deletes the first face data used in face modeling locally.
[0159] In this embodiment, the software management platform collects facial image data through various channels and directly encrypts and stores the facial image data locally or stores it locally after modeling. By storing the collected facial image data after modeling, the modeling data of the facial image data can be directly and quickly sent to the application device when facial data needs to be sent later, thereby achieving a faster facial data sending speed.
[0160] Furthermore, this invention also proposes a device for distributing facial data. Please refer to... Figure 4 The face data distribution device of the present invention is applied to the software management platform described above. The face data distribution device of the present invention includes:
[0161] The face delivery module 10 is used to send first face data, which is an image, to a first device, the first device including a first face data application device or a face data modeling server;
[0162] The face deletion module 20 is used to obtain the modeling data corresponding to the first face data from the first device, send a face image deletion instruction to the first device so that the first device can delete the first face data; and delete the first face data locally on the software management platform.
[0163] In one feasible embodiment, the face data dissemination device of the present invention further includes:
[0164] The face modeling acquisition module is used to acquire the algorithm version identifier of the first device; to use the modeling data acquired from the first device as second face data with the data type modeling data; and to associate and store the second face data and the algorithm version identifier locally on the software management platform.
[0165] In one feasible embodiment, the face data distribution module 10 of the face data distribution device of the present invention is further configured to determine whether the second face data application device meets a preset algorithm version condition when face data needs to be distributed to the second face data application device, wherein the algorithm version condition is that the algorithm version identifier of the second face data application device is the same as the algorithm version identifier associated with the second face data; if it is determined that the second face data application device meets the algorithm version condition, the second face data is distributed to the second face data application device; and if it is determined that the second face data application device does not meet the algorithm version condition, the second face data is marked as invalid data and a corresponding prompt is output.
[0166] In one feasible embodiment, the face data distribution module 10 of the face data distribution device of the present invention is further configured to mark the first face data as to be deleted on the software management platform when it is determined that the first face data of data type image exists locally on the software management platform, and distribute the first face data to the first face data application device.
[0167] In one feasible embodiment, the face deletion module 20 of the face data distribution device of the present invention is further configured to delete the first face data marked as to be deleted locally on the software management platform after determining that the first face data has been successfully distributed to the first face data application device.
[0168] In one feasible embodiment, the face data dissemination device of the present invention further includes:
[0169] The marker update module is used to update the marker to be deleted of the first face data to a marker not to be deleted on the software management platform when it is determined that the first face data has failed to be sent to the first face data application device.
[0170] In one feasible embodiment, the number of the first face data application devices is greater than one. The face modeling acquisition module of the face data distribution device of the present invention is further configured to, after distributing the first face data to any target device among the first face data application devices, determine whether the modeling data corresponding to the first face data is obtained from other first face data application devices that successfully distributed the first face data, wherein the other first face data application devices and the target device have the same algorithm version identifier; if not, then the modeling data is obtained from the target device; and if yes, then the acquisition of the modeling data from the target device is abandoned.
[0171] The face deletion module 20 of the face data distribution device of the present invention is further configured to delete the first face data locally on the software management platform when it is determined that the first face data has been successfully distributed to each of the first face data application devices.
[0172] The extended content of the specific implementation of the face data distribution device of the present invention is basically the same as the various embodiments of the face data distribution method described above, and will not be repeated here.
[0173] Furthermore, embodiments of the present invention also propose a computer-readable storage medium storing a face data distribution program, wherein when the face data distribution program is executed by a processor, it implements the steps of the face data distribution method described below.
[0174] Furthermore, embodiments of the present invention also provide a computer program product containing instructions that, when run on a computer, cause the computer to execute the steps of the face data distribution method described above.
[0175] The various embodiments of the face data distribution device, computer-readable storage medium, and computer program product of the present invention can all refer to the various embodiments of the face data distribution method of the present invention, and will not be described again here.
[0176] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.
[0177] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.
[0178] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of the present invention.
[0179] The above are merely preferred embodiments of the present invention and do not limit the patent scope of the present invention. Any equivalent structural or procedural transformations made based on the content of the present invention's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of the present invention.
Claims
1. A method for delivering face data, characterized in that, The face data issuing method is applied to a software management platform, and the method comprises the following steps: first face data of a picture type is sent to a first device, the first device comprises a first face data application device, and the first device is used for modeling the first face data to obtain modeling data corresponding to the first face data; after the modeling data corresponding to the first face data is obtained from the first device, a face picture deletion instruction is sent to the first device to delete the first face data; the first face data is deleted locally in the software management platform; wherein the number of the first face data application devices is greater than one, and the method further comprises: after the first face data is issued to any target device of the first face data application devices, it is determined whether the modeling data corresponding to the first face data is obtained from other first face data application devices which successfully issue the first face data, wherein the other first face data application devices have the same algorithm version identifier as the target device; if not, the modeling data is obtained from the target device; if yes, the modeling data is abandoned from the target device; the step of deleting the first face data locally in the software management platform comprises: when it is determined that the first face data is successfully issued to each of the first face data application devices, the first face data is deleted locally in the software management platform; the method further comprises: when a plurality of first face data of a picture type are batched and issued to a plurality of first face data application devices, it is first detected whether the algorithm version identifiers of the plurality of first face data application devices are the same, and in the case that the plurality of algorithm version identifiers are the same, the first face data is issued to the plurality of first face data application devices by transmitting picture data, so that each of the first face data application devices respectively performs face modeling on the face data received by itself based on the same face modeling algorithm configured by itself; when the modeling data corresponding to the first face data is obtained, one copy of the modeling data is obtained from the first device which first receives the first face data and completes face data modeling among the plurality of first face data application devices.
2. The method of claim 1, wherein, the method further comprises: the algorithm version identifier of the first device is obtained; the modeling data obtained from the first device is taken as second face data of a modeling data type; the second face data and the algorithm version identifier are associated and stored locally in the software management platform. 3.The method of Claim 2, wherein, the method further comprises: when it is needed to issue face data to a second face data application device, it is determined whether the second face data application device meets a preset algorithm version condition, wherein the algorithm version condition is that the algorithm version identifier of the second face data application device is the same as the algorithm version identifier associated and stored with the second face data; if it is determined that the second face data application device meets the algorithm version condition, the second face data is issued to the second face data application device; If it is determined that the second face data application device does not meet the algorithm version condition, the second face data is marked as invalid data and a corresponding prompt is output.
4. The method of Claim 1, wherein, The step of sending the first face data of the picture type to the first face data application device comprises: When it is determined that the software management platform locally exists the first face data of the picture type, the first face data is marked as to-be-deleted in the software management platform, and the first face data is sent to the first face data application device.
5. The method of Claim 4, wherein, The step of deleting the first face data in the software management platform comprises: After it is determined that the sending of the first face data to the first face data application device is successful, the first face data marked as to-be-deleted is deleted in the software management platform.
6. The method of claim 4 or 5, wherein, The method further comprises: When it is determined that the sending of the first face data to the first face data application device fails, the to-be-deleted mark of the first face data is updated to a non-deletion mark in the software management platform.
7. A device for delivering face data, characterized in that, The face data sending device is applied to a software management platform, and the device comprises: a face sending module, configured to send first face data of a picture type to a first device, the first device comprising a first face data application device, the first device being configured to model the first face data to obtain modeling data corresponding to the first face data; a face deleting module, configured to, after the face modeling module obtains the modeling data corresponding to the first face data from the first device, send a face picture deleting instruction to the first device to instruct the first device to delete the first face data, and delete the first face data in the software management platform; wherein the number of the first face data application devices is greater than one, the face modeling obtaining module is configured to, after the first face data is sent to any target device among the first face data application devices, determine whether the modeling data corresponding to the first face data is obtained from other first face data application devices in which the sending of the first face data is successful, wherein the other first face data application devices have the same algorithm version identifier as the target device; if not, the modeling data is obtained from the target device; and if yes, the modeling data is abandoned from the target device; the face deleting module is further configured to, after it is determined that the sending of the first face data to each of the first face data application devices is successful, delete the first face data in the software management platform; the face modeling obtaining module is further configured to: In the batch delivery of a first face data of a picture type to a plurality of first face data application devices, first detect whether the algorithm version identifiers of the plurality of first face data application devices are the same, and in the case of detecting that the plurality of algorithm version identifiers are the same, deliver the first face data to the plurality of first face data application devices by transmitting picture data, so that each of the first face data application devices respectively performs face modeling on the respective received face data based on the same face modeling algorithm configured by itself. In the acquisition of the modeling data corresponding to the first face data, obtain a piece of modeling data from a device that first receives the first face data and completes face data modeling among the plurality of first face data application devices. 8.The device for delivering face data according to claim 7, wherein, The device further comprises: The face modeling acquisition module is configured to acquire the algorithm version identifier of the first device, acquire the modeling data from the first device as second face data of a modeling data type, and store the second face data and the algorithm version identifier in association in the local software management platform. The face delivery module is further configured to determine whether the second face data application device meets a preset algorithm version condition when delivering face data to the second face data application device, wherein the algorithm version condition is that the algorithm version identifier of the second face data application device is the same as the algorithm version identifier stored in association with the second face data, deliver the second face data to the second face data application device if it is determined that the second face data application device meets the algorithm version condition, and mark the second face data as invalid data and output a corresponding prompt if it is determined that the second face data application device does not meet the algorithm version condition. The face delivery module is further configured to mark the first face data as to be deleted in the local software management platform and deliver the first face data to the first face data application device when it is determined that there is first face data of a picture type in the local software management platform. The face deletion module is further configured to delete the first face data marked as to be deleted in the local software management platform after it is determined that the delivery of the first face data to the first face data application device is successful. The device further comprises a marking update module configured to update the to-be-deleted marking of the first face data to a non-deletion marking in the local software management platform when it is determined that the delivery of the first face data to the first face data application device fails.
9. A device for delivering face data, characterized in that, The face data delivery device comprises a memory, a processor, and a face data delivery program stored in the memory and executable on the processor, and the face data delivery program, when executed by the processor, implements the steps of the face data delivery method of any one of claims 1 to 6.
Citation Information
Patent Citations
Image processing method, face recognition method and system
CN114550265A
Method for performing payment through identification using facial image and system implementing the same
KR102363313B1