Face identifier management method and device

Abstract

The invention provides a face identifier management method and device, and is applied to a vehicle-mounted terminal of a vehicle networking system, and the method comprises the steps: sending a management instruction for a face identifier to a management platform based on a preset communication protocol; wherein an instruction set for managing a face identifier is defined in the preset communication protocol, the management instruction is any instruction in the instruction set, and the face identifier is generated based on a face image of a user and is used for identifying the identity of the user; receiving a response message returned by the management platform for the management instruction, wherein the response message is used for indicating a processing strategy for the face identifier; and executing the processing strategy according to the response message.

Description

Technical Field

[0001] This application relates to the field of vehicle technology, and in particular to a method and apparatus for managing facial identifiers. Background Technology

[0002] With the rapid development of vehicle connectivity technology, user identity management has become one of the core means of driving safety control (such as preventing unlicensed driving and monitoring fatigue driving).

[0003] In related technologies, the standard communication protocols commonly used only cover basic positioning and video transmission functions, and cannot provide standardized support for facial feature identifiers. Therefore, most current solutions adopt a single-vehicle closed-loop approach, where facial verification is only completed locally on the vehicle terminal. Facial identifiers and related data cannot be uploaded to the management platform, resulting in the inability to achieve centralized management of facial identifiers. This restricts the large-scale application of vehicles in identity recognition scenarios and the improvement of management efficiency. Summary of the Invention

[0004] In view of this, this application provides a face identifier management method to solve the defects existing in related technologies. The technical solution of this application is as follows: According to an embodiment of the first aspect of this application, a face identifier management method is provided, applied to an in-vehicle terminal of a vehicle-to-everything (V2X) system, the method comprising: Based on a preset communication protocol, management instructions for face identifiers are sent to the management platform; wherein, the preset communication protocol defines a set of instructions for managing face identifiers, the management instructions are any instructions in the instruction set, and the face identifier is generated based on the user's face image and is used to identify the user's identity; The system receives a response message from the management platform in response to the management instruction. The response message is used to indicate the processing strategy for the face identifier. The processing strategy is executed based on the response message.

[0005] According to an embodiment of the second aspect of this application, a face identifier management method is provided, applied to a management platform of a vehicle network system, the method comprising: The system receives a management instruction for a face identifier sent by an in-vehicle terminal based on a preset communication protocol. The preset communication protocol defines a set of instructions for managing face identifiers, and the management instruction is any instruction in the instruction set. The face identifier is generated based on the user's face image and is used to identify the user's identity. Send a response message to the management command so that the vehicle terminal executes a processing strategy for the face identifier based on the response message.

[0006] According to an embodiment of a third aspect of this application, a face identifier management device is provided, comprising: The sending unit is used to send management instructions for face identifiers to the management platform based on a preset communication protocol; wherein, the preset communication protocol defines a set of instructions for managing face identifiers, the management instructions are any instructions in the instruction set, and the face identifier is generated based on the user's face image and is used to identify the user's identity; The receiving unit is configured to receive a response message returned by the management platform in response to the management instruction, wherein the response message is used to indicate the processing strategy for the face identifier; The processing unit is used to execute the processing strategy based on the response message.

[0007] According to an embodiment of the fourth aspect of this application, a face identifier management device is provided, comprising: The receiving unit is configured to receive a management instruction for a face identifier sent by the vehicle terminal based on a preset communication protocol; wherein, the preset communication protocol defines a set of instructions for managing face identifiers, the management instruction is any instruction in the instruction set, and the face identifier is generated based on the user's face image and is used to identify the user's identity. The sending unit is configured to send a response message to the management command, so that the vehicle terminal executes a processing strategy for the face identifier according to the response message.

[0008] According to an embodiment of the fifth aspect of this application, an electronic device is provided, including a memory, a processor, and executable instructions stored in the memory and executable on the processor, wherein the processor executes the executable instructions to implement the method as described in the first aspect.

[0009] According to an embodiment of the sixth aspect of this application, a computer-readable storage medium is provided having computer instructions stored thereon that, when executed by a processor, implement the steps of the method described in the first aspect.

[0010] According to an embodiment of the seventh aspect of this application, a computer program product is provided, including a computer program / instructions that, when executed by a processor, implement the steps of the method described in the first aspect.

[0011] In the technical solution provided in this application, a pre-defined communication protocol defines a set of instructions specifically for managing facial identifiers. The vehicle-mounted terminal of the vehicle-to-everything (V2X) system can send management instructions for facial identifiers to the management platform based on this pre-defined communication protocol. After the management platform returns a response message, the vehicle-mounted terminal can execute processing operations according to the processing strategy indicated in the response message. Applying the technical solution of this application enables standardized transmission of facial identifier management instructions through the pre-defined communication protocol, allowing the vehicle-mounted terminal and the management platform to interact based on unified management instructions without relying on other customized interfaces. Simultaneously, it achieves centralized management of facial identifiers, improving system compatibility and management efficiency. Furthermore, given that facial identifiers can identify user identities, it expands the application breadth of V2X systems in identity recognition scenarios.

[0012] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit the embodiments of this application. Attached Figure Description

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

[0014] Figure 1 This is a schematic diagram of the architecture of a vehicle network system shown in an exemplary embodiment of this application; Figure 2 This is a flowchart illustrating an exemplary embodiment of the present application of a face identifier management method applied to an in-vehicle terminal; Figure 3 This is an exemplary embodiment of the present application illustrating the interaction between an in-vehicle terminal and a management platform; Figure 4 This is a schematic diagram illustrating a face identifier generation process according to an exemplary embodiment of this application; Figure 5 This is a flowchart illustrating an exemplary embodiment of the present application of a face identifier management method applied to an in-vehicle terminal; Figure 6 This is a schematic diagram of an electronic device illustrated in an exemplary embodiment of this application; Figure 7 This is a schematic diagram of a face identifier management device applied to an in-vehicle terminal, as shown in an exemplary embodiment of this application; Figure 8 This is a schematic diagram of a face identifier management device applied to a management platform, as shown in an exemplary embodiment of this application. Detailed Implementation

[0015] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with one or more embodiments of this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of one or more embodiments of this application as detailed in the appended claims.

[0016] It should be noted that the steps of the corresponding methods in other embodiments are not necessarily performed in the order shown and described in this application. In some other embodiments, the methods may include more or fewer steps than those described in this application. Furthermore, a single step described in this application may be broken down into multiple steps in other embodiments; and multiple steps described in this application may be combined into a single step in other embodiments.

[0017] The user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and corresponding operation entry points are provided for users to choose to authorize or refuse.

[0018] With the rapid development of vehicle-to-everything (V2X) technology, user identity management has become one of the core means of driving safety control (such as preventing unlicensed driving and monitoring fatigue driving). In V2X systems, accurate user identification is a prerequisite for achieving functions such as behavior analysis, driving access control, and fatigue warning linkage. Currently, the industry generally adopts JT / T 808 "Communication Protocol for Vehicle-Mounted Terminals of Road Transport Vehicle Satellite Positioning System" (hereinafter referred to as Vehicle-Mounted Terminal Communication Protocol JT / T 808) and JT / T1078 "Video Communication Protocol for Road Transport Vehicle Video Surveillance System" (hereinafter referred to as Video Communication Protocol JT / T 1078) as standard communication specifications between vehicle-mounted terminals and management platforms. However, these protocols mainly cover basic functions such as vehicle positioning, status reporting, and video stream transmission, and do not establish unified protocol specifications for the generation, uploading, synchronization, updating, and lifecycle management of Face Identity Documents (FaceIDs).

[0019] Due to a lack of standardized support, related technologies have significant limitations in managing user identities. Currently, most systems adopt a single-vehicle closed-loop solution: the onboard terminal only completes facial image acquisition, feature extraction, and identity verification locally, without any data interaction with the management platform. In this type of solution, facial identifier data cannot be uploaded to the management platform, making it impossible to achieve unified management of user identities across vehicles and terminals. This restricts the large-scale application of vehicles in identity recognition scenarios and hinders the improvement of management efficiency.

[0020] To address the aforementioned issues, this application proposes a method and apparatus for managing facial identifiers. The technical solution provided in this application enables standardized transmission of facial identifier management commands through a preset communication protocol, allowing the vehicle terminal and management platform to interact based on unified management commands without relying on other customized interfaces. Simultaneously, it achieves centralized management of facial identifiers, improving system compatibility and management efficiency. Furthermore, given that facial identifiers can identify user identities, it expands the application breadth of vehicle-to-everything (V2X) systems in identity recognition scenarios.

[0021] The technical solutions provided by the various embodiments of this application will now be described in detail with reference to the accompanying drawings.

[0022] Figure 1 This is a schematic diagram of a vehicle connectivity system architecture provided in an exemplary embodiment. For example... Figure 1 As shown, the system architecture may include a server 11, a network 12, and several vehicle terminals, such as an FCS forward-facing camera system 13, a VDR vehicle video recorder 14, and a DVR digital hard disk recorder 15.

[0023] Server 11 can be a physical server containing an independent host, or it can be a virtual server hosted by a host cluster. During operation, server 11 can run server-side programs of the vehicle network system to act as the server-side of the vehicle network system, i.e., the management platform. The FCS forward-facing camera system 13, VDR vehicle video recorder 14, and DVR digital hard disk recorder 15 are only some types of vehicle terminals. The vehicle terminals that interact with the management platform may differ in different types of vehicles, and will not be listed here. During operation, the vehicle terminal can launch and run the terminal-side application of the vehicle network system. This program can be a pre-installed native application or other equivalent form, and this application does not impose any restrictions on this. As for the network 12 that enables interaction between the vehicle terminals such as the FCS forward-facing camera system 13, VDR vehicle video recorder 14, and DVR digital hard disk recorder 15 and server 11, communication can be achieved using wired or wireless networks based on the communication methods supported by the respective vehicle terminals, and this application does not impose any restrictions on this. For example, the FCS forward-facing camera system 13 typically supports wireless communication, so a wireless network can be used to achieve communication.

[0024] The aforementioned vehicle-to-everything (V2X) system is designed for both vehicle terminal users and management platform administrators. The management platform centrally manages facial identifier data from the in-vehicle terminals using standardized management commands, while the in-vehicle terminals collect driver facial information and execute platform commands. This solution utilizes dedicated management commands within the communication protocol to achieve standardized transmission of facial identifiers and centralized management, thereby improving system compatibility and management efficiency.

[0025] Figure 2 This is a flowchart illustrating an exemplary embodiment of a face identifier management method applied to an in-vehicle terminal. Figure 3 This is an exemplary embodiment of this application illustrating an interaction diagram. The following will combine... Figure 3 ,right Figure 2 The method shown is explained in detail. See also Figure 2 The method may specifically include the following steps: Step 201: Based on a preset communication protocol, send a management instruction for the face identifier to the management platform; wherein, the preset communication protocol defines a set of instructions for managing face identifiers, the management instruction is any instruction in the instruction set, and the face identifier is generated based on the user's face image and is used to identify the user's identity.

[0026] Step 202: Receive a response message from the management platform in response to the management instruction. The response message is used to indicate the processing strategy for the face identifier.

[0027] Step 203: Execute the processing strategy according to the response message.

[0028] In one embodiment, the preset communication protocol can be a standard communication protocol for data transmission between the vehicle terminal and the management platform, such as the vehicle terminal communication protocol JT / T 808 or the video communication protocol JT / T 1078. Within the preset communication protocol, a dedicated set of instructions for managing face identifiers can be defined in reserved fields. For example, in the vehicle terminal communication protocol JT / T 808, management instructions sent from the vehicle terminal to the management platform can be defined in reserved fields 0x0F00~0x0FFF of the terminal's uplink messages; and management instructions sent from the management platform to the vehicle terminal can be defined in reserved fields 0x8F00~0x8FFF of the platform's downlink messages. This instruction set contains multiple management instructions, any of which is used to implement synchronization operations between the vehicle terminal and the management platform for face identifiers. For example, an input notification instruction informs the management platform that the vehicle terminal has collected a face identifier and synchronized it to the management platform, and a deletion notification instruction informs the management platform that the vehicle terminal has deleted a face identifier, etc.

[0029] In one embodiment, the user can be any user of the vehicle. When it is necessary to identify the driver to prevent unlicensed driving, fatigue detection, or other functions, the user can be the driver; when it is necessary to identify other occupants of the vehicle to adapt to their usage habits, the user can be any occupant other than the driver. This application does not impose any restrictions on this. The facial identifier is a unique identifier that can identify a user and corresponds one-to-one with each user. Different users have completely different facial identifiers, which can be generated based on the user's facial image.

[0030] In one embodiment, the vehicle-mounted terminal can initiate the facial identifier collection and generation process under preset conditions (such as vehicle startup, user command, etc.) to ensure effective identification and management of user identity. The following will combine... Figure 4 The process shown will be explained in detail.

[0031] Step 401: After initiating the facial identifier acquisition and generation process, the user's facial image can be captured in real time using a camera device installed inside the vehicle. To ensure the camera device can adapt to different lighting conditions, infrared technology or a visible light camera can be used to ensure high-quality user facial images can be obtained even in low-light environments.

[0032] Step 402: After acquiring the face image, a quality check can be performed to ensure that the face image meets the processing standards and avoid low-quality images affecting subsequent processing. If the quality check result indicates that the acquired face image is unqualified, return to step 401 and re-acquire the user's face image.

[0033] Step 403: After image acquisition, the acquired face images can be preprocessed, including but not limited to denoising, normalization, and face alignment, to improve the accuracy of subsequent recognition. Denoising reduces image noise caused by the shooting environment; normalization adjusts the face image to a standard size and grayscale level to eliminate differences caused by varying shooting angles or distances; face alignment automatically detects and corrects key facial features (such as eyes, nose, and mouth) using algorithms to ensure each facial feature is in the same position, guaranteeing the accuracy of subsequent user identification.

[0034] Step 404: A locally deployed face recognition algorithm can be used to analyze the preprocessed face image and extract a numerical representation of the unique facial features of an individual, namely, a face feature vector. Here, technicians can set the high-dimensional value of the face feature vector according to actual needs, such as 128 dimensions or 256 dimensions, etc., and this application does not impose any restrictions on this.

[0035] Step 405: Based on the obtained facial feature vector, a facial identifier for that user can be generated by combining the user's unique identifier, the timestamp of the exact moment the data was generated, and the identifier of the vehicle terminal. The facial identifier generated by this method not only contains the user's identity information but also implicitly contains important metadata such as the generation time and terminal device, providing a reliable information foundation for subsequent updates to the facial identifier.

[0036] Step 406: To ensure the security and privacy of data information, the generated facial identifier can be encrypted and stored in the encrypted storage area of ​​the vehicle terminal device, which effectively prevents the risk of unauthorized access or data leakage, and also provides a solid foundation for subsequent data management and synchronization.

[0037] In one embodiment, after obtaining a facial identifier for a specific user, the vehicle-mounted terminal can proactively initiate the facial identifier upload process, sending an input notification instruction from the management command to the management platform to inform the platform that the vehicle-mounted terminal has a facial identifier to be uploaded. This embodiment's method enables proactive reporting of facial identifier data from the vehicle-mounted terminal, ensuring timely data updates.

[0038] Specifically, on the vehicle-mounted terminal side, encryption algorithms can be used locally to encrypt the data information carried by management commands (including the unique identifier of the user corresponding to the facial recognition symbol, timestamp, algorithm version of the facial recognition algorithm used, feature length of the facial recognition symbol, specific content of feature values, etc.), such as... Figure 3 As shown in step 301. Specifically, AES256 encryption algorithm, SM4 encryption algorithm, etc., can be used; this application does not impose any restrictions on this. Additionally, protocol header information, including the communication protocol version number and current timestamp, can be added after encryption. Subsequently, the vehicle terminal encapsulates the above data according to the format of a preset communication protocol, such as... Figure 3 As shown in step 302. This encapsulation structure follows a standard message format, including a message header, message body, and checksum to ensure the integrity and correctness of the data during transmission. After data encapsulation is complete, the vehicle terminal can send the input notification command and the corresponding encapsulated data information to the management platform via the network, such as... Figure 3 As shown in step 303.

[0039] On the management platform side, upon receiving the input notification instruction from the vehicle terminal, the management platform first verifies the message's legitimacy, including verification code verification and instruction permission checks. After successful verification, the management platform decrypts the message body and parses out the data information carried by the input notification instruction sent by the vehicle terminal, including a facial identifier. Subsequently, the management platform stores this facial identifier in the platform database and associates it with other data such as user profiles and vehicle binding relationships, completing centralized management of identity data. It then returns a structured response message to the vehicle terminal, such as... Figure 3 As shown in step 304.

[0040] In one embodiment, the response message returned by the management platform not only confirms successful data reception but also carries specific processing strategies and feedback information for the facial identifier. For example, the response message can explicitly indicate "successful entry," allowing the vehicle terminal to update its local status and send a success notification to the user. If the management platform detects abnormalities such as duplicate entry, it can return "entry failed" along with the reason for the failure, allowing the vehicle terminal to handle the abnormality accordingly. Technical personnel can set the processing strategies corresponding to the response messages based on actual circumstances and needs; this application does not impose any restrictions on this.

[0041] As can be seen from the above embodiments, the technical solution of this application can realize the standardized transmission of face identifier management instructions through a preset communication protocol, enabling the vehicle terminal and the management platform to interact based on unified management instructions without relying on other customized interfaces; at the same time, it realizes centralized management of face identifiers, improves system compatibility and management efficiency, and expands the application breadth of vehicle network system in identity recognition scenarios when face identifiers can identify user identity.

[0042] In one embodiment, the vehicle-mounted terminal can also respond to a data synchronization request sent by the management platform and, based on a preset communication protocol, send a list reporting instruction for face identifiers to the management platform to achieve data synchronization of face identifiers between the vehicle-mounted terminal and the management platform. The synchronization request instructs the vehicle-mounted terminal to upload a list of face identifiers, which is transmitted through the data information carried in the list reporting instruction.

[0043] Specifically, when the management platform needs to synchronize data, it can send a data synchronization request to the vehicle terminal. This request can explicitly indicate the synchronization mode, such as full synchronization or incremental synchronization. Upon receiving the synchronization request, the vehicle terminal can first iterate through all face identifiers in its local encrypted storage area and generate corresponding digest information for each face identifier, forming a hash value list, i.e., a face identifier list. In response to the received synchronization request, the vehicle terminal can send a list reporting instruction to the management platform based on a preset communication protocol. The list reporting instruction carries the face identifier list, including the digest information of each face identifier.

[0044] After receiving the list of face identifiers, the management platform can compare it with the face identifiers that the vehicle terminal should have in the platform database and analyze the data differences between the two. If the management platform lacks data, it can directly update the platform database based on the list of face identifiers; if the management platform has incremental data, it can package the face identifiers to be synchronized to the vehicle terminal, split them according to the packet splitting rules of the preset communication protocol to obtain multiple data packets, and then send each data packet to the vehicle terminal in sequence through the corresponding management command (such as a full synchronization command).

[0045] The vehicle-mounted terminal receives each data packet sequentially, verifies its integrity one by one, and performs an overall consistency check after all packets have been received. Once confirmed to be error-free, the vehicle-mounted terminal updates its locally stored data based on the facial identifier data in the received data packets and returns a response message to the platform indicating that the synchronization operation is complete.

[0046] As can be seen from the above embodiments, the technical solution of this application effectively avoids data inconsistency problems caused by network interruption or device offline through a closed-loop mechanism in which the management platform initiates a synchronization request, the vehicle terminal reports the list of face identifiers, and the management platform compares the differences and sends incremental data. This achieves consistency maintenance of face identifier data between the vehicle terminal and the management platform. At the same time, the packet transmission mechanism effectively avoids data loss when transmitting large data packets and improves the success rate of data synchronization.

[0047] In one embodiment, each facial identifier stored locally on the vehicle terminal has a corresponding expiration date. The expiration date can be associated with rules required in practice, such as the validity period of a user's driver's license or the period of function authorization; this application does not impose any restrictions on this. The vehicle terminal can perform validity checks on all locally stored facial identifiers according to a preset periodic frequency, such as daily or weekly, to determine the validity status of each facial identifier. Specifically, for any facial identifier, the vehicle terminal can compare the current system time with the validity period of the facial identifier. If it finds that the facial identifier has exceeded its expiration date, it is marked as expired and automatically deleted, freeing up local storage space on the vehicle terminal and preventing invalid data from occupying resources for a long time. It should be noted that there are also cases where users actively delete facial identifiers. In this case, regardless of whether the validity period of the facial identifier has expired, the deletion operation can be completed according to the user's instructions.

[0048] After local deletion is completed, the vehicle terminal sends a deletion notification instruction to the management platform through a preset communication protocol. This instruction carries the unique identification information of the deleted face identifier (such as the mobile phone number of the user of the face identifier) ​​and the reason for deletion (such as "expiration" or "user deletion"), which is used to notify the management platform to synchronize and update the corresponding data in the platform database.

[0049] After receiving the deletion notification instruction, the management platform parses its content, marks the corresponding face identifier as invalid in the database or directly performs physical deletion, and returns a confirmation response to the vehicle terminal, forming an operation closed loop.

[0050] As can be seen from the above embodiments, the technical solution of this application avoids the problem of invalid data occupying storage resources through the automatic expiration and cleanup mechanism of face identifiers, while ensuring the consistency of face identifier data between the vehicle terminal and the management platform.

[0051] In one embodiment, the user may interact with the management platform through other electronic devices outside the vehicle terminal, completing the entry and deletion of facial identifiers within the management platform. In this case, to ensure data consistency between the vehicle terminal and the management platform, the management platform can instruct the vehicle terminal to perform addition and deletion operations for facial identifiers by issuing management commands. For example, the management platform can send a facial addition command to the vehicle terminal. Upon receiving the command, the vehicle terminal can parse the facial identifier, user unique identification information, validity period, and other information carried in the command. After passing security verification, the facial identifier is stored in a local encrypted storage area. Simultaneously, the management platform can also send a facial deletion command specifying the user's unique identification information to the vehicle terminal. Upon receiving this command, the vehicle terminal immediately clears the corresponding facial identifier data locally and can determine whether execution is mandatory based on the "mandatory flag" field in the deletion command. After completing the addition or deletion operation, the vehicle terminal can return the execution result to the platform via an uplink command, including status codes such as operation success and storage full, achieving closed-loop feedback of command execution.

[0052] As can be seen from the above embodiments, the mechanism provided by the technical solution of this application ensures that the centralized control of user identity on the management platform can be synchronized to the vehicle terminal in real time, effectively solving the problem of data inconsistency caused by cross-device operation and improving the management reliability and response efficiency of the vehicle network system in multi-terminal collaborative scenarios.

[0053] In one embodiment, to ensure the reliability of face identifier data interaction between the vehicle terminal and the management platform, this application also provides an anomaly handling and recovery mechanism. During the execution of methods such as face identifier uploading and face list synchronization, if network connection interruption, data packet loss, or reception timeout is detected, it can be determined as a transmission anomaly. At this time, the data sender can initiate a retry mechanism, employing an exponential backoff algorithm for a limited number of retransmissions, such as a default of 3 or 5 retries, with the retry interval increasing by 2^n (e.g., 1 second, 2 seconds, 4 seconds, etc.) to avoid exacerbating communication pressure during network congestion and improve the reconnection success rate.

[0054] For scenarios involving the synchronization of large amounts of data, such as synchronizing all face identifiers, a breakpoint resumption mechanism can be used. Specifically, the data sender can record the sequence numbers of successfully sent or received data packets during transmission. When the network connection is restored after an interruption, it can request the data receiver to resume transmission from the sequence number of the last successfully transmitted packet, avoiding duplicate transmission of already successfully transmitted portions, improving transmission efficiency and saving communication resources. After data transmission is complete, the data sender and receiver can use hash verification to check the consistency of the transmitted content, ensuring that the data has not been tampered with or corrupted during transmission.

[0055] If a management command fails to execute after multiple retries, or if an unrecoverable error is detected (such as storage media failure or decryption failure), an exception event log can be generated. This log, along with the exception type, error code, occurrence time, and associated device information, can be reported to the management platform via an exception reporting command in the preset communication protocol. Upon receiving the exception information, the management platform allows maintenance personnel to intervene manually based on the specific error type. This could include remotely diagnosing the status of the vehicle terminal or notifying on-site maintenance, thereby ensuring the stable operation of the vehicle network system and the integrity of its data.

[0056] It should be noted that the encryption methods, encapsulation methods, packet sub-methods, and breakpoint resumption methods described in the above embodiments can be applied to various processes involving data transmission, such as the vehicle terminal notifying the management platform to record or delete face identifiers, face list synchronization, and the management platform instructing the vehicle terminal to record or delete face identifiers, to ensure data security and reliability during transmission, prevent data from being stolen, tampered with, or damaged during transmission, and effectively improve the fault tolerance and maintainability of the vehicle network system in complex environments.

[0057] Figure 5 This is a flowchart illustrating an exemplary embodiment of a face identifier management method applied to a management platform. See also... Figure 5 The method may specifically include the following steps: Step 501: Receive a management instruction for a face identifier sent by the vehicle terminal based on a preset communication protocol; wherein, the preset communication protocol defines a set of instructions for managing face identifiers, the management instruction is any instruction in the instruction set, and the face identifier is generated based on the user's face image and is used to identify the user's identity.

[0058] Step 502: Receive a management instruction for a face identifier sent by the vehicle terminal based on a preset communication protocol; wherein, the preset communication protocol defines a set of instructions for managing face identifiers, the management instruction is any instruction in the instruction set, and the face identifier is generated based on the user's face image and is used to identify the user's identity.

[0059] The vehicle-mounted terminal in this embodiment is the vehicle-mounted terminal of the vehicle network system described in the previous embodiments, and Figure 2 The illustrated embodiment describes the specific implementation process of the solution in this application from the perspective of the vehicle-mounted terminal of the vehicle network system. Figure 2 Corresponding to the technical solution based on the management platform in the illustrated embodiment, the solution in this application uses the vehicle-mounted terminal of the vehicle network system in conjunction with the management platform to achieve a complete interaction process. Figure 2All descriptions related to the management platform in the illustrated embodiment regarding operations such as adding face identifiers, deleting face identifiers, and synchronizing the face identifier list are also applicable to the same scenarios. Figure 5 The embodiments shown are not described in detail here.

[0060] Furthermore, to achieve standardized and end-to-end management of facial identifiers between the vehicle terminal and the management platform, this application defines a complete set of dedicated management instructions for facial identifiers based on the vehicle terminal communication protocol JT / T 808. This instruction set is divided into terminal uplink instructions (0x0F01~0x0FFF) and platform downlink instructions (0x8F02~0x8FFF), fully utilizing the instruction range reserved in the protocol to avoid conflicts with existing functions, while ensuring compatibility with various terminals and platforms conforming to the JT / T 808 standard.

[0061] As shown in the following series of tables, each type of instruction adopts a unified protocol body structure, which includes clear field definitions, data types, length constraints, and transmission rules.

[0062] The terminal uplink command is used to actively report local status changes of the vehicle terminal, such as face identifier enrollment success notification (0x0F01), face deletion notification (0x0F02), and face list reporting (0x0F03), as shown in Table 1 below: Table 1 Specifically, for the aforementioned tables, this application also lists the specific field formats and communication specifications for each management instruction: Table 2 Face Enrollment Notification Command 0x0F01 Protocol Body (Uplink) Table 3. Face deletion notification instruction 0x0F02 protocol body (uplink) Table 4 Face List Reporting Protocol Body 0x0F03 (Uplink) The platform's downlink commands are used to achieve centralized management and control, such as issuing face addition commands (0x8F02), face deletion commands (0x8F03), and full / incremental synchronization commands (0x8F04), as shown in Table 5 below: Table 5 Specifically, for the aforementioned tables, this application also lists the specific field formats and communication specifications for each management instruction: Table 6 Face Addition Command 0x8F02 Protocol Body (Downlink) Table 7 Face deletion command 0x8F03 protocol body (downlink) Table 8 Full / Incremental Query Command 0x8F04 Protocol Body (Downlink) All of the above management commands require end-to-end encrypted transmission, integrity verification, and execution result feedback mechanisms. Key fields such as algorithm version and validity period are introduced, and the system fully supports the generation, synchronization, secure transmission, lifecycle management, and anomaly handling of face identifiers. This constructs a closed-loop, reliable, and scalable vehicle network system between the vehicle terminal and the management platform.

[0063] By applying the technical solution of this application, a full lifecycle management system for face identifiers based on standard communication protocols is constructed, achieving standardized and closed-loop management of face identifiers between vehicle terminals and the management platform. This system not only supports the generation, uploading, synchronization, validity period control, and automatic cleanup of face identifiers, effectively reducing the storage pressure on vehicle terminals and ensuring the timeliness and accuracy of data on the management platform side; but also, through a unified management command set and feedback mechanism, it achieves closed-loop control of "vehicle terminal reporting—management platform processing—result feedback—vehicle terminal execution," enabling the platform to proactively intervene in and control the processing strategies of vehicle terminals. Overall, this solution eliminates the reliance on customized interfaces, improves the compatibility and management efficiency of vehicle network systems, and achieves centralized management of user identities in multi-terminal, multi-vehicle environments, significantly expanding the application breadth and maintainability of vehicle network systems in identity recognition scenarios such as driving safety and access control.

[0064] Figure 6 This is a schematic structural diagram of a device provided in an exemplary embodiment. Please refer to... Figure 6 At the hardware level, the electronic device includes a processor 602, an internal bus 604, a network interface 606, memory 608, and non-volatile memory 610, and may also include other hardware required for business operations. The processor 602 reads the corresponding computer program from the non-volatile memory 610 into the memory 608 and then runs it, forming a face identifier management device applied to the vehicle terminal or management platform at the logical level. Of course, in addition to the software implementation, this application does not exclude other implementation methods, such as logic devices or a combination of hardware and software, etc. That is to say, the execution subject of the following processing flow is not limited to individual logic units, but can also be hardware or logic devices.

[0065] Corresponding to the above-described method embodiments on the vehicle-mounted terminal side, this application also provides embodiments of a face identifier management device. Please refer to... Figure 7This facial recognition management device can be applied to, for example... Figure 6 The device shown is specifically an in-vehicle terminal used in a vehicle network system to implement the technical solution of this application. The face identifier management device may include a sending unit 71, a receiving unit 72, and a processing unit 73, wherein: The sending unit 71 is used to send management instructions for face identifiers to the management platform based on a preset communication protocol; wherein, the preset communication protocol defines a set of instructions for managing face identifiers, the management instruction is any instruction in the instruction set, and the face identifier is generated based on the user's face image and is used to identify the user's identity. The receiving unit 72 is configured to receive a response message returned by the management platform in response to the management instruction, wherein the response message is used to indicate the processing strategy for the face identifier; The processing unit 73 is used to execute the processing strategy according to the response message.

[0066] Optionally, the preset communication protocol includes the vehicle terminal communication protocol JT / T 808.

[0067] Optionally, the face identifier is generated in the following manner: The user's facial image is captured by a camera installed in the vehicle to which the terminal device belongs; Based on the face recognition algorithm, the facial feature vector of the face image is extracted; The face identifier is generated based on the face feature vector, user identifier, timestamp, and vehicle terminal identifier.

[0068] Optionally, the management instructions include input notification instructions; The transmitting unit 71 is specifically used for: For any generated face identifier, the face identifier is stored in a local encrypted storage area, and an input notification instruction for the face identifier is sent to the management platform; wherein, the input notification instruction carries the data information of the face identifier, and the input notification instruction is used to instruct the management platform to input the face identifier.

[0069] Optionally, the management instructions include list reporting instructions; The transmitting unit 71 is specifically used for: In response to a data synchronization request sent by the management platform, the vehicle terminal sends a list reporting instruction for face identifiers to the management platform based on a preset communication protocol; wherein, the synchronization request is used to instruct the vehicle terminal to upload the list of face identifiers; the list reporting instruction carries data information of the list of face identifiers.

[0070] Optionally, the management instructions include a deletion notification instruction; the face identifier is stored locally; and the face identifier has a corresponding validity period. The device further includes a period checking unit 74, used for: For any face identifier stored locally, the validity status of the face identifier is determined according to the validity period corresponding to the face identifier at a preset periodic frequency; and, if the validity status indicates that the face identifier is invalid, the face identifier is deleted. The transmitting unit 71 is specifically used for: Send a deletion notification instruction to the management platform for any of the face identifiers. The deletion notification instruction carries the identification information of any of the face identifiers and is used to instruct the management platform to delete any of the face identifiers.

[0071] Optionally, the transmitting unit 71 is specifically used for: The data information carried by the management command is encrypted; The encrypted data is encapsulated based on a preset communication protocol to obtain encapsulated data, and the management command and the encapsulated data corresponding to the management command are sent to the management platform.

[0072] Corresponding to the above-described method embodiments on the management platform side, this application also provides embodiments of a face identifier management device. Please refer to... Figure 8 This facial recognition management device can be applied to, for example... Figure 6 The device shown is specifically a management platform applied to a vehicle network system to implement the technical solution of this application. The face identifier management device may include a receiving unit 81 and a sending unit 82, wherein: The receiving unit 81 is used to receive a management instruction for a face identifier sent by the vehicle terminal based on a preset communication protocol; wherein, the preset communication protocol defines a set of instructions for managing face identifiers, the management instruction is any instruction in the instruction set, and the face identifier is generated based on the user's face image and is used to identify the user's identity. The sending unit 82 is used to send a response message to the management command, so that the vehicle terminal executes the processing strategy for the face identifier according to the response message.

[0073] Optionally, the preset communication protocol includes the vehicle terminal communication protocol JT / T 808.

[0074] Optionally, the management instruction includes an input notification instruction, which carries data information of any face identifier and is used to instruct the management platform to input the any face identifier. The device further includes an input unit 83, which is specifically used to: input the data information carried by the input notification instruction into the platform database according to the received input notification instruction.

[0075] Optionally, the management instructions include list reporting instructions; The device further includes a synchronization processing unit 84, specifically used for: A data synchronization request is sent to the vehicle terminal, so that the vehicle terminal sends a list reporting instruction for face identifiers to the management platform based on a preset communication protocol; wherein, the synchronization request is used to instruct the vehicle terminal to upload the list of face identifiers; the list reporting instruction carries data information of the list of face identifiers.

[0076] Optionally, the management instructions include a deletion notification instruction; the face identifier has a corresponding validity period; The device further includes a deletion unit 85, specifically configured to: receive a deletion notification instruction sent by the vehicle terminal for any face identifier, determine the face identifier to be deleted based on the identification information carried by the deletion notification instruction, and delete the face identifier from the platform database.

[0077] The specific implementation process of the functions and roles of each unit in the above device can be found in the implementation process of the corresponding steps in the above method, and will not be repeated here.

[0078] For the device embodiments, since they basically correspond to the method embodiments, the relevant parts can be referred to in the description of the method embodiments. The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and 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 modules can be selected to achieve the purpose of this application according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0079] Accordingly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the face identifier management method as described in any of the above embodiments.

[0080] Accordingly, this application also provides a computer program product, including a computer program / instructions, which, when executed by a processor, implement the face identifier management method as described in any of the above embodiments.

[0081] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer, which can take the form of a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email sending and receiving device, game console, tablet computer, wearable device, or any combination of these devices.

[0082] In a typical configuration, a computer includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0083] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0084] Computer-readable media, including both permanent and non-permanent, removable and non-removable media, can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, disk storage, quantum memory, graphene-based storage media or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

Claims

1. A method for managing facial identifiers, characterized in that, The method, applied to an in-vehicle terminal in a vehicle-to-everything (V2X) system, includes: Based on a preset communication protocol, management instructions for face identifiers are sent to the management platform; wherein, the preset communication protocol defines a set of instructions for managing face identifiers, the management instructions are any instructions in the instruction set, and the face identifier is generated based on the user's face image and is used to identify the user's identity; The system receives a response message from the management platform in response to the management instruction. The response message is used to indicate the processing strategy for the face identifier. The processing strategy is executed based on the response message.

2. The method according to claim 1, characterized in that, The face identifier is generated in the following manner: The user's facial image is captured by a camera installed in the vehicle to which the terminal device belongs; Based on the face recognition algorithm, the facial feature vector of the face image is extracted; The face identifier is generated based on the face feature vector, user identifier, timestamp, and vehicle terminal identifier.

3. The method according to claim 1, characterized in that, The management instructions include input notification instructions; The step of sending management instructions for face identifiers to the management platform based on a preset communication protocol includes: For any generated face identifier, the face identifier is stored in a local encrypted storage area, and an input notification instruction for the face identifier is sent to the management platform; wherein, the input notification instruction carries the data information of the face identifier, and the input notification instruction is used to instruct the management platform to input the face identifier.

4. The method according to claim 1, characterized in that, The management instructions include list reporting instructions; the sending of management instructions for face identifiers to the management platform based on a preset communication protocol includes: In response to a data synchronization request sent by the management platform, the vehicle terminal sends a list reporting instruction for face identifiers to the management platform based on a preset communication protocol; wherein, the synchronization request is used to instruct the vehicle terminal to upload the list of face identifiers; the list reporting instruction carries data information of the list of face identifiers.

5. The method according to claim 1, characterized in that, The management instructions include a deletion notification instruction; the face identifier is stored locally; the face identifier has a corresponding validity period; The method further includes: For any face identifier stored locally, the validity status of the face identifier is determined according to the validity period corresponding to the face identifier at a preset periodic frequency; and, if the validity status indicates that the face identifier is invalid, the face identifier is deleted. The step of sending management instructions for face identifiers to the management platform based on a preset communication protocol includes: Send a deletion notification instruction to the management platform for any of the face identifiers. The deletion notification instruction carries the identification information of any of the face identifiers and is used to instruct the management platform to delete any of the face identifiers.

6. The method according to any one of claims 3-4, characterized in that, The step of sending management instructions for face identifiers to the management platform based on a preset communication protocol includes: The data information carried by the management command is encrypted; The encrypted data is encapsulated based on a preset communication protocol to obtain encapsulated data, and the management command and the encapsulated data corresponding to the management command are sent to the management platform.

7. A method for managing facial identifiers, characterized in that, The method, applied to a management platform for vehicle network systems, includes: The system receives a management instruction for a face identifier sent by an in-vehicle terminal based on a preset communication protocol. The preset communication protocol defines a set of instructions for managing face identifiers, and the management instruction is any instruction in the instruction set. The face identifier is generated based on the user's face image and is used to identify the user's identity. Send a response message to the management command so that the vehicle terminal executes a processing strategy for the face identifier based on the response message.

8. The method according to claim 7, characterized in that, The management instructions include an input notification instruction, which carries data information of any face identifier and is used to instruct the management platform to input the face identifier. The method further includes: inputting the data information carried by the input notification instruction into the platform database according to the received input notification instruction.

9. The method according to claim 7, characterized in that, The management instructions include list reporting instructions; the method further includes: A data synchronization request is sent to the vehicle terminal, so that the vehicle terminal sends a list reporting instruction for face identifiers to the management platform based on a preset communication protocol; wherein, the synchronization request is used to instruct the vehicle terminal to upload the list of face identifiers; the list reporting instruction carries data information of the list of face identifiers.

10. The method according to claim 7, characterized in that, The management instructions include a deletion notification instruction; the face identifier has a corresponding validity period; the method further includes: The system receives a deletion notification instruction for any face identifier sent by the vehicle terminal, determines the face identifier to be deleted based on the identification information carried in the deletion notification instruction, and deletes the face identifier from the platform database.

11. A facial identifier management device, characterized in that, The in-vehicle terminal used in a vehicle connectivity system includes: The sending unit is used to send management instructions for face identifiers to the management platform based on a preset communication protocol; wherein, the preset communication protocol defines a set of instructions for managing face identifiers, the management instructions are any instructions in the instruction set, and the face identifier is generated based on the user's face image and is used to identify the user's identity; The receiving unit is configured to receive a response message returned by the management platform in response to the management instruction, wherein the response message is used to indicate the processing strategy for the face identifier; The processing unit is used to execute the processing strategy based on the response message.

12. A facial identifier management device, characterized in that, A management platform for vehicle connectivity systems, the device comprising: The receiving unit is configured to receive a management instruction for a face identifier sent by the vehicle terminal based on a preset communication protocol; wherein, the preset communication protocol defines a set of instructions for managing face identifiers, the management instruction is any instruction in the instruction set, and the face identifier is generated based on the user's face image and is used to identify the user's identity. The sending unit is configured to send a response message to the management command, so that the vehicle terminal executes a processing strategy for the face identifier according to the response message.

13. An electronic device, characterized in that, It includes a memory, a processor, and executable instructions stored in the memory and executable on the processor, wherein the processor executes the executable instructions to implement the method as described in any one of claims 1-6 or 7-10.

14. A computer-readable storage medium, characterized in that, It stores computer instructions that, when executed by a processor, implement the steps of the method as described in any one of claims 1-6 or 7-10.

15. A computer program product, characterized in that, Includes a computer program / instructions that, when executed by a processor, implement the steps of the method as described in any one of claims 1-6 or 7-10.

Images