Internet of vehicles real name authentication method and device, electronic equipment and storage medium

Abstract

The present disclosure provides a vehicle networking real-name authentication method and device, electronic equipment and storage medium, relating to the technical field of real-name authentication, which comprises: in response to receiving a vehicle networking real-name request, adjusting the download waiting time of the real-name attachment picture and judging the real-name service type; starting a target download process to download and decrypt the real-name attachment picture; if the real-name attachment picture is successfully downloaded and decrypted, performing real-name authentication processing on the real-name attachment picture based on the real-name service type. Thus, the efficiency and success rate of vehicle networking real-name authentication processing are improved, and the method is suitable for optimizing the business processing flow of multiple system interaction with high time requirements.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to the technical field of real-name authentication, and particularly relates to a vehicle networking real-name authentication method and device, electronic equipment and a storage medium. BACKGROUND

[0002] According to the requirements of the Ministry of Industry and Information Technology, the T1 interface is constructed by an operator and the vehicle networking card real-name registration work is completed by the vehicle enterprise together. The vehicle enterprise needs to complete the vehicle networking card real-name registration, transfer, data update and cancellation and the like of personal users and unit users through the interface of the operator.

[0003] The customer manager initiates the real-name registration of the vehicle owner through the vehicle enterprise platform. After the China Mobile vehicle networking card real-name registration management platform receives the request, the real-name verification is performed through the interface calling of the nationwide one certificate and five households platform. After the interface returns successfully, the vehicle enterprise real-name request is sent to the OS platform (ONE-SUPPORT: unified fusion support gateway). The OS forwards the real-name information to the business operation support system or the Internet of Things card management system. After the real-name authentication and the basic verification of the one certificate and five households platform, the vehicle owner real-name authentication process is completed.

[0004] However, when a certain vehicle enterprise initiates batch enterprise real-name authentication, the personal real-name authentication business is easily blocked, and the vehicle networking real-name authentication attachment download fails / upload fails. SUMMARY

[0005] The present disclosure provides a vehicle networking real-name authentication method, device, electronic equipment and storage medium, which aims to at least solve one of the technical problems in the related art to some extent.

[0006] The first aspect embodiment of the present disclosure provides a vehicle networking real-name authentication method, which is executed by an Internet of Things system, and the method comprises the following steps.

[0007] In response to receiving a vehicle networking real-name request, the download waiting time of the real-name attachment picture is adjusted, and the real-name business type is judged.

[0008] A target download process is started to download and decrypt the real-name attachment picture.

[0009] In the case that the real-name attachment picture is successfully downloaded and decrypted, the real-name authentication processing is performed on the real-name attachment picture based on the real-name business type.

[0010] The second aspect embodiment of the present disclosure provides a vehicle networking real-name authentication method, which is executed by a real-name registration management platform, and the method comprises the following steps.

[0011] A real-name registration request initiated by a user through a vehicle enterprise platform is received, wherein the real-name registration request contains a real-name attachment picture.

[0012] perform real-name verification on the target platform based on the real-name registration request;

[0013] send the real-name registration request to a unified fusion support gateway in a case where the verification passes, so that the unified fusion support gateway sends a vehicle network real-name authentication request to an Internet of Things system.

[0014] A third aspect embodiment of the present disclosure provides a vehicle networking real-name authentication device configured in an Internet of Things system, comprising:

[0015] A first receiving module is configured to adjust a download waiting time length of a real-name attachment picture and determine a real-name service type in response to receiving a vehicle networking real-name request.

[0016] A starting module is configured to start a target download process to download and decrypt the real-name attachment picture.

[0017] A processing module is configured to perform real-name authentication processing on the real-name attachment picture based on the real-name service type in a case where the real-name attachment picture is successfully downloaded and decrypted.

[0018] A fourth aspect embodiment of the present disclosure provides a vehicle networking real-name authentication device configured in a real-name registration management platform, comprising:

[0019] A second receiving module is configured to receive a real-name registration request initiated by a user through a vehicle enterprise platform, wherein the real-name registration request contains a real-name attachment picture.

[0020] A verification module is configured to perform real-name verification on a target platform based on the real-name registration request.

[0021] An authentication module is configured to send the real-name registration request to a unified fusion support gateway in a case where the verification passes, so that the unified fusion support gateway sends a vehicle network real-name authentication request to an Internet of Things system.

[0022] A fifth aspect embodiment of the present disclosure provides an electronic device, comprising at least one processor and a memory connected with the at least one processor in communication; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the vehicle networking real-name authentication method of the embodiments of the present disclosure.

[0023] A sixth aspect embodiment of the present disclosure provides a non-transitory computer readable storage medium storing computer instructions, wherein the computer instructions are used to enable the computer to perform the vehicle networking real-name authentication method disclosed by the embodiments of the present disclosure.

[0024] In the embodiments of the present disclosure, the Internet of Things system first adjusts the download waiting time length of the real-name attachment picture in response to receiving the real-name request of the Internet of Vehicles, judges the real-name service type, starts the target download process to download and decrypt the real-name attachment picture, and performs real-name authentication processing on the real-name attachment picture based on the real-name service type in the case of successful download and decryption of the real-name attachment picture. Thus, the decryption coupling technology can be adopted for the real-name authentication of the Internet of Vehicles to realize asynchronous processing of the platform, reduce the time consumption of the overall real-name task, and improve the business processing efficiency. The automatic guarantee technology of the real-name authentication service interface of the Internet of Vehicles in a specific scenario can reduce the problem that the vehicle owner cannot be real-name in the case of system abnormality, and greatly reduces the operation and maintenance workload and difficulty. The real-name authentication processing efficiency and success rate of the Internet of Vehicles are improved, and the technology is suitable for the optimization of the business processing flow of multiple system interactions and high time length requirements.

[0025] In the embodiments of the present disclosure, the real-name registration management platform first receives a real-name registration request initiated by a user through a vehicle enterprise platform, wherein the real-name registration request contains a real-name attachment picture, then performs real-name verification on the target platform based on the real-name registration request, and then sends the real-name registration request to the unified fusion support gateway in the case of passing the verification, so that the unified fusion support gateway sends a vehicle network real-name authentication request to the Internet of Things system. Thus, the real-name registration request initiated by the user through the vehicle enterprise platform can be efficiently processed to ensure the authenticity and reliability of the identity of the vehicle network user. The platform can quickly receive the real-name registration request from the vehicle enterprise platform, including the real-name information and the real-name attachment picture of the user, realize fast response and timely processing, accurately judge whether the real-name information provided by the user is real and effective, and ensure that only legal users can complete the real-name registration. Through the processing of the platform, the unified fusion support gateway can send a vehicle network real-name authentication request to the Internet of Things system, further promote the real-name authentication work of the vehicle network user, and improve the security and reliability of the entire vehicle network system.

[0026] It should be understood that the foregoing general description and the following detailed description are only exemplary and explanatory, and cannot limit the present disclosure. BRIEF DESCRIPTION OF DRAWINGS

[0027] The accompanying drawings, which are incorporated into the specification and constitute part of it, illustrate embodiments in accordance with the present disclosure and, together with the specification, serve to explain the principles of the present disclosure, in which:

[0028] Figure 1 is a flow diagram of a real-name authentication method of the Internet of Vehicles provided according to a first embodiment of the present disclosure;

[0029] Figure 2 is a flow diagram of a real-name authentication method of the Internet of Vehicles provided according to a second embodiment of the present disclosure;

[0030] Figure 3 is a vehicle networking real-name service process diagram;

[0031] Figure 4 is a flow diagram of a vehicle networking real-name authentication method according to a third embodiment of the present disclosure;

[0032] Figure 5 is a schematic diagram of a vehicle networking real-name authentication device according to an embodiment of the present disclosure;

[0033] Figure 6 is a schematic diagram of another vehicle networking real-name authentication device according to an embodiment of the present disclosure;

[0034] Figure 7 is a block diagram of an electronic device for implementing the vehicle networking real-name authentication method according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0035] Some embodiments of the present disclosure will be described in detail herein with reference to the drawings, which are presented as examples. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. Various changes, modifications, and equivalents of the methods, devices, and / or systems described herein will become apparent to those skilled in the art after understanding the present disclosure. For example, the order of the operations described herein is merely an example and is not limited to those set forth herein, but can be changed as would be apparent to one skilled in the art after understanding the present disclosure, except for operations that must be performed in a particular order. In addition, the description of features known in the art can be omitted for the sake of clarity and brevity.

[0036] The implementations described in some embodiments of the present disclosure below do not represent all implementations consistent with the present disclosure. Instead, they are merely examples of apparatuses and methods consistent with some aspects of the present disclosure as detailed in the appended claims.

[0037] It should be noted that the vehicle networking real-name request refers to a request for real-name authentication registration of a vehicle networking card. According to the requirements of the Ministry of Industry and Information Technology, all vehicle networking cards of vehicles sold in China must be registered for real-name authentication before accessing the vehicle networking network. The purpose of real-name authentication registration of vehicle networking cards is to strengthen the management and control of vehicle networking services and to ensure the safety of vehicle networking. Since the current development of vehicle networking is still in its initial stage, it mainly provides functions such as traffic and voice networking, therefore, vehicle networking cards need to be registered for real-name authentication in accordance with the security management requirements of Internet of Things cards. The specific process of real-name authentication registration of vehicle networking cards usually includes: the vehicle owner submits personal identity information and vehicle information through a designated channel (such as a vehicle networking service platform, an operator APP, etc.) to complete the real-name authentication registration of the vehicle networking card. After submitting the information, the system will audit the submitted information, and after the audit is passed, the vehicle networking card can be used normally.

[0038] Figure 1 is a flowchart of a vehicle networking real-name authentication method provided according to the first embodiment of the present disclosure.

[0039] It should be noted that the execution subject of the vehicle networking real-name authentication method of the first embodiment of the present disclosure can be an Internet of Things (IOT) system.

[0040] As shown in Figure 1 , the method comprises:

[0041] S101: In response to receiving a vehicle networking real-name request, adjusting the download waiting time length of the real-name attachment picture, and determining the real-name service type.

[0042] As a possible implementation, the vehicle networking real-name attachment picture download waiting time length can be adjusted to 0 seconds, so that after the real-name request is received, the download of the attachment picture will be triggered immediately without any delay, thereby significantly reducing the user waiting time and improving the user experience.

[0043] Optionally, a separate download process can also be added to the remote directory real-name attachment to ensure that each real-name task has a dedicated process to handle attachment download after being received.

[0044] In the embodiment of the present disclosure, the download process can be recorded as clwcustregister.download. The design of the independent process can improve the concurrent processing capability of the system, so that multiple real-name tasks can perform attachment download at the same time without interfering with each other.

[0045] It should be noted that through the above optimization, the time consumption of each real-name task is reduced by an average of 2-3 seconds, which improves the overall processing efficiency of the system and enables users to complete the real-name process faster.

[0046] It should be noted that on the server side, a multi-threaded or asynchronous processing mechanism can be used to implement the download process to ensure stable performance under high concurrency. The client side can also need corresponding optimization, such as optimizing network requests, cache mechanisms, etc., to further improve user experience.

[0047] Specifically, to ensure the stability and maintainability of the system, monitoring and log recording of the clwcustregister.download process can be added, so that problems can be quickly located and solved when they occur.

[0048] Specifically, a field ISBATCH can be added to the vehicle networking real-name model table (recorded as CS_REC_CUSTREGISTER table), and the data type can be selected according to requirements (for example, integer INT, where 0 represents personal real-name and 1 represents batch unit real-name).

[0049] When receiving the real-name request, first check the corresponding record in the CS_REC_CUSTREGISTER table, and read the value of the ISBATCH field. If the value of the ISBATCH field is 0, it represents a personal real-name service, and if the value of the ISBATCH field is 1, it represents a batch unit real-name service.

[0050] S102: Start the target download process to download and decrypt the real-name attachment picture.

[0051] As an implementation manner, first identify which parts of the real-name authentication request are closely related to the download and decryption of the owner real-name attachment, determine the data exchange, function call or message passing mode between these parts. In order to reduce the coupling degree, an intermediate layer or interface can be introduced to isolate the specific implementation of the real-name authentication request and the download and decryption of the owner real-name attachment. Design patterns such as mediator pattern, event-driven pattern, etc. can also be used to reduce the direct dependency between different components.

[0052] Optionally, the real-name authentication request processing and the owner real-name attachment download and decryption function can be split into independent modules to ensure that each module has clear responsibilities and interface definitions, and to reduce cross-module calls.

[0053] Optionally, a unified interface specification can be defined for the real-name authentication request and the download and decryption function of the owner real-name attachment, and these interface specifications can be used to constrain the interaction between different modules to improve the maintainability and scalability of the system. The encryption and decryption process of the owner real-name attachment should be independent of the real-name authentication request processing flow. A special encryption library or tool can be used to handle the encryption and decryption of the owner real-name attachment to ensure data security.

[0054] It should be noted that in the real-name authentication process of the Internet of Vehicles, the size of a single compressed attachment package of real-name is usually 1-3MB. If the pixel requirement of the real-name attachment is high, the file size may affect the system performance, especially in a high concurrency scenario. In order to optimize performance and reduce the time-consuming of attachment searching, the attachments can be deleted from the operating system (OS) directory after successful download.

[0055] Optionally, the attachments can be deleted from the OS directory immediately after successful download and processing (such as completion of the real-name authentication process). Specifically, a special temporary directory can be used to store the attachments to be processed, and the directory can be emptied after processing. Log records about the attachment processing status (download, processing, deletion) are kept for auditing or troubleshooting when needed.

[0056] Optionally, in the logic for downloading the attachment, specify that the attachment should be saved to a temporary directory. After processing the attachment (e.g. real-name authentication), add logic to delete the file. This could be immediately after the file processing is successful, or in a periodic cleanup task.

[0057] Optionally, in the case of a failed download or upload of the real-name attachment picture, send a notification to the initiator.

[0058] It should be noted that in the code for downloading the attachment picture, any exceptions or errors that could cause the download to fail should be caught. This typically includes network connection problems, server unresponsive, file not found, etc. Similarly, in the code for uploading the attachment picture, exceptions or errors that could cause the upload to fail should also be caught. These could include file size restrictions, file type mismatches, network errors, etc.

[0059] Optionally, after catching an error, first log the error information to the system's log file. This helps with subsequent problem tracking and troubleshooting. Alternatively, a clear and easy-to-understand error message can also be generated based on the type of error caught.

[0060] Optionally, the error message can be sent to the initiator through instant messaging tools such as SMS, email, APP push notifications, etc. In this way, the initiator can immediately know what problem has occurred and take appropriate action. If the initiator initiates the download or upload request through an interface (such as a web page or APP), the error message can be displayed on this interface. In this way, the initiator can immediately see the error message without waiting for other notifications.

[0061] S103: In the case of successful decryption of the real-name attachment picture, perform real-name authentication processing on the real-name attachment picture based on the real-name business type.

[0062] Optionally, in the case of the real-name business type being a personal real-name business, perform real-name authentication processing on the real-name attachment picture based on a first process. In the case of the real-name business type being a batch unit real-name business, perform real-name authentication processing on the real-name attachment picture based on a second process, wherein the first process and the second process are different.

[0063] The first process is an independent process for handling personal real-name businesses, containing all the logic required to handle personal real-name requests, such as verifying personal information, interacting with the authentication system, updating real-name status, etc.

[0064] The second process is an independent process for handling batch unit real-name businesses, containing special logic required to handle batch unit real-name requests, such as handling multiple entities, batch verification, etc.

[0065] If it is a personal real-name service, the request is sent to the first process MTBatchCustRegister for processing.

[0066] If it is a batch unit real-name service, the request is sent to the second process MTBatchCustRegisterBat for processing.

[0067] Optionally, in the real-name authentication processing of the real-name attachment picture based on the second process, any unit real-name information to be processed can be determined from the batch unit real-name task, and online company verification is called once to process the any unit real-name information.

[0068] It should be noted that in the same batch unit real-name task, a unit real-name information is first randomly extracted for online company verification, and the result of this verification is used as a reference for all unit real-name information in the batch (assuming that the unit information similarity in the batch is high). If the verification passes, it is assumed that all units in the batch pass the verification; if the verification fails, further processing (such as individual verification or manual review) may be required.

[0069] It should be noted that by reducing the number of online verification calls, the total processing time can be significantly reduced. If there is a call fee for the online verification interface, this optimization can significantly reduce costs. Reducing network requests can reduce network traffic, which is an important consideration for large systems. Faster processing time can improve user experience, especially for scenarios that require fast response. In practical applications, compared to adjusting the time-consuming ratio before, calling online once for the same batch can save 200 seconds, which can greatly reduce the time-consuming of batch real-name.

[0070] In the embodiments of the present disclosure, the Internet of Things system first responds to receiving a vehicle networking real-name request, adjusts the download waiting time length of the real-name attachment picture, judges the real-name service type, starts the target download process to download and decrypt the real-name attachment picture, and in the case that the real-name attachment picture is successfully downloaded and decrypted, performs real-name authentication processing on the real-name attachment picture based on the real-name service type. Thus, the decryption coupling technology can be adopted for the vehicle networking real-name authentication and authentication of the real-name attachment download, the platform asynchronous processing can be realized, the time-consuming of the overall real-name task can be reduced, and the business processing efficiency can be improved. The vehicle networking real-name authentication business interface automation guarantee technology in a specific scenario reduces the problem that the vehicle owner cannot be real-name in the case of system abnormality, greatly reduces the operation and maintenance workload and difficulty, improves the vehicle networking real-name authentication processing efficiency and success rate, and is suitable for business processing flow optimization for multiple system interactions and high time length requirements.

[0071] Figure 2 is a flowchart of a vehicle networking real-name authentication method according to the second embodiment of the present disclosure.

[0072] It should be noted that the execution subject of the vehicle networking real-name authentication method of the second embodiment of the present disclosure can be an Internet of Things system IOT.

[0073] As shown in Figure 2 The method comprises the following steps:

[0074] S201: In response to receiving a vehicle networking real-name request, adjusting the download waiting time length of the real-name attachment picture, and determining the real-name service type.

[0075] S202: Start the target download process to download and decrypt the real-name attachment picture.

[0076] S203: In the case of successful download and decryption of the real-name attachment picture, perform real-name authentication processing on the real-name attachment picture based on the real-name service type.

[0077] It should be noted that the specific implementation of steps S201-S203 can refer to the above embodiments, which will not be repeated here.

[0078] S204: When an exception occurs in the processing of the image center, switch the connection with the image center to the connection with the online company to perform real-name authentication.

[0079] It should be noted that when the image center cannot provide normal services due to technical failure, network problems or other reasons, the IOT system needs to respond quickly and switch the real-name authentication process originally through the image center to directly connect to the online company through the IOT system for real-name authentication. This can avoid business interruption caused by image center exceptions and ensure that users can successfully complete real-name authentication.

[0080] Specifically, the IOT system can continuously monitor the status of the image center, including service availability, response time and other key indicators. When an exception is detected in the image center, the system automatically triggers an emergency handling mechanism. The system switches the real-name authentication process originally through the image center to directly connect to the online company through the IOT system for real-name authentication. In this process, system configuration may need to be adjusted, routing rules updated, etc. to ensure that data can be correctly transmitted to the online company.

[0081] The IOT system sends user information that needs to be authenticated to the online company. After the online company receives the user information, it performs real-name authentication according to its internal process. After the real-name authentication is completed, the online company returns the result to the IOT system.

[0082] S205: Get the real-name authentication result returned by the online company.

[0083] It should be noted that the IOT system needs to monitor the status of the image center in real time, such as network connection, server running status, etc., and detect whether an exception occurs. When the image center is monitored to have an exception, the IOT system should trigger an emergency handling mechanism. This can be achieved through automated scripts, monitoring systems, etc. The IOT system needs to switch the original communication mode connected to the image center to directly connect to the online company for real-name authentication. This may involve network configuration changes, protocol switching, etc. The IOT system sends a real-name authentication request to the online company by establishing a connection with the online company. After receiving the request, the online company performs real-name authentication and returns the authentication result to the IOT system. After receiving the real-name authentication result returned by the online company, the IOT system processes according to the result, such as recording the authentication result, updating user information, etc.

[0084] S206: According to the fields in the Internet of Vehicles real-name processing table, the real-name authentication result is judged, and the processing state of the intraprovincial real-name process is updated.

[0085] Specifically, after receiving the real-name authentication result returned by the online company, the real-name authentication result can be parsed to obtain the authentication status code (such as UPIMRESULT) and possible additional information (such as error information, etc.).

[0086] Optionally, the next operation can be determined according to the value of the authentication status code UPIMRESULT. For example:

[0087] If UPIMRESULT = 10, it means that the online company verification is successful.

[0088] If UPIMRESULT = 13, it means that it is successful without calling online real-name processing (possibly based on certain preset conditions or local verification).

[0089] For other UPIMRESULT values, it may indicate that the real-name authentication fails or there is other exception.

[0090] Specifically, the processing state of the corresponding record in the Internet of Vehicles real-name processing table can be updated, and the corresponding state field is set according to the value of UPIMRESULT.

[0091] S207: In the case of online company verification success or no need to call online real-name processing, the interface of the online company is called to return a successful record.

[0092] It should be noted that if the real-name authentication result is online company verification success or no need to call online real-name processing, the interface of the online company can be called to return a successful record. Then, the relevant records of the Internet of Vehicles system can be updated, and marked as real-name authentication success. If necessary, send a notification to the front end or related system to inform that the real-name authentication has been completed.

[0093] S208: In the case of a failed real-name authentication result, record error information and complete the process.

[0094] It should be noted that when the real-name authentication result is failed (i.e. UPIMRESULT is not a value indicating success), error information can be recorded, including failure reason, timestamp, etc., and then according to system configuration or business requirements, it is decided whether to display the error information to the user. If necessary, send an alarm notification to the relevant personnel to deal with the problem in time, and then update the relevant records of the Internet of Vehicles system and mark it as a failed real-name authentication.

[0095] Optionally, after the real-name task is completed, the image center is processed asynchronously, and after the image center processing is completed, the successfully uploaded photo stream is backfilled to the order to complete the real-name authentication business in the province.

[0096] It can be understood that when the user's real-name authentication task is completed, the system will trigger a flag or event indicating that the real-name task has been completed. After receiving the signal that the real-name task is completed, the system starts an asynchronous processing task, and the target of the task is to process the related data and photos in the image center. The asynchronous processing task will connect to the image center to obtain the photos and other data related to the real-name task. Necessary processing is performed on these photos, such as format conversion, size adjustment, compression, etc., to meet the requirements of storage and display. At the same time, the system can also perform quality inspection on the photos to ensure that the photos are clear, complete and meet the regulations.

[0097] Further, if the photos meet the requirements, the system will upload the photos to the designated storage location (such as database, file server, etc.). During the uploading process, the system will record the serial number information of the photos, including uploading time, uploader, file path, etc. When the photo is uploaded and stored successfully, the system will backfill the serial number information of the photo to the corresponding order or user record. This means that the order or user record now contains the results of real-name authentication and related photo information. With the results of real-name authentication and photo information, the system can consider that the real-name authentication business in the province has been completed. At this time, the system can send a notification to the front end or related system to inform that the real-name authentication has been completed, and may provide a link for downloading or viewing the photos.

[0098] Figure 3 A flowchart of a real-name business process for a vehicle network is shown schematically in the above steps.

[0099] In the embodiments of the present disclosure, the Internet of Things system IOT first adjusts the download waiting time length of the real-name attachment picture in response to receiving the vehicle networking real-name request, judges the real-name business type, starts the target download process to download and decrypt the real-name attachment picture, performs real-name authentication processing on the real-name attachment picture based on the real-name business type, switches the connection with the image center to the connection with the online company to perform real-name authentication when an exception occurs in the processing of the image center, obtains the real-name authentication result returned by the online company, updates the processing state of the in-province real-name process, judges the real-name authentication result based on the fields in the vehicle networking real-name processing table, calls the interface of the online company to return a successful record in the case of online company verification success or no need to call online real-name processing, and records error information and reports the completion of the processing in the case of failure. Thus, by monitoring the program log, the system automatically switches to direct connection to the online company when an exception occurs, avoiding real-name authentication failure due to image center failure. The decryption coupling technology is adopted to realize platform asynchronous processing and reduce real-name task time consumption. The business processing efficiency is improved, the user waiting time is reduced, the system load is reduced through asynchronous processing, and the system stability is improved. When the process cannot upload / abnormal in processing the uploaded image center platform, the program automatically collects abnormal information and uploads it to the image center for processing, which can quickly and efficiently guarantee business continuity, avoid real-name authentication interruption due to upload failure, reduce manual intervention, and reduce operation and maintenance cost. The system automatically handles emergencies when an exception occurs, generates an exception completion work order, responds to the interface in a timely manner, can reduce user complaint risk, improve user experience, facilitate problem tracking and fault troubleshooting, and improve operation and maintenance efficiency. The vehicle networking real-name request entry channel is optimized (divided into two parts), the serial completion processing is optimized into synchronous completion, the real-name processing time is reduced, the business processing efficiency is improved, the process design is optimized, and the system throughput is improved.

[0100] Figure 4 is a flowchart of a vehicle networking real-name authentication method according to the third embodiment of the present disclosure.

[0101] It should be noted that the execution subject of the vehicle networking real-name authentication method of the third embodiment of the present disclosure can be a real-name registration management platform.

[0102] As shown in Figure 4 , the method comprises:

[0103] S301: receiving a real-name registration request initiated by a user through a vehicle enterprise platform, wherein the real-name registration request contains a real-name attachment picture.

[0104] It should be noted that the customer manager initiates the real-name registration request of the vehicle owner through the vehicle enterprise platform (such as the online system of the automobile dealer). The request contains the real-name information (such as the name and ID number) of the vehicle owner and the real-name attachment picture (such as the scanned copy or photo of the ID card). The real-name registration management platform receives the real-name registration request sent by the vehicle enterprise platform, and the platform starts processing the request and prepares for subsequent real-name verification work.

[0105] S302: Real-name verification is performed on the target platform based on the real-name registration request.

[0106] The target platform can be a nationwide one-card five-household platform, which is a platform for verifying whether the ID card information is real and has been used for registration of other five accounts. The real-name registration management platform calls the target platform through an interface to perform real-name verification. The verification content includes the authenticity and validity of the ID number, and whether it matches the name of the vehicle owner. If the interface returns a successful verification result, the subsequent process continues; otherwise, an error message is returned to the vehicle enterprise platform and the process ends.

[0107] S303: In the case where the verification is passed, the real-name registration request is sent to the unified fusion support gateway, so that the unified fusion support gateway sends a vehicle network real-name authentication request to the Internet of Things system.

[0108] After the real-name verification is passed, the real-name registration management platform sends the real-name registration request (containing the real-name information) to the unified fusion support gateway (OS platform). The OS platform is an intermediate layer that integrates communication and data exchange between different systems. The OS platform forwards the received real-name information to the Internet of Things system for real-name authentication.

[0109] In the embodiments of the present disclosure, the real-name registration management platform first receives the real-name registration request initiated by the user through the vehicle enterprise platform, wherein the real-name registration request contains a real-name attachment picture, then performs real-name verification on the target platform based on the real-name registration request, and then sends the real-name registration request to the unified fusion support gateway in the case where the verification is passed, so that the unified fusion support gateway sends a vehicle network real-name authentication request to the Internet of Things system. In this way, the real-name registration request initiated by the user through the vehicle enterprise platform can be efficiently processed, and the identity of the vehicle network user can be ensured to be real and reliable. The platform can quickly receive the real-name registration request from the vehicle enterprise platform, including the real-name information and the real-name attachment picture of the user, realize fast response and timely processing, accurately judge whether the real-name information provided by the user is real and effective, and ensure that only legal users can complete the real-name registration. Through the processing of the platform, the unified fusion support gateway can send a vehicle network real-name authentication request to the Internet of Things system, further promote the real-name authentication work of the vehicle network user, and improve the security and reliability of the entire vehicle network system.

[0110] Figure 5FIG. 1 is a schematic diagram of a vehicle networking real-name authentication device according to an embodiment of the present disclosure. As shown in FIG. 1, the vehicle networking real-name authentication device 500 is configured in an Internet of Things system and includes: Figure 5

[0111] The first receiving module 510 is configured to adjust a download waiting time length of a real-name attachment picture and determine a real-name service type in response to receiving a vehicle networking real-name request.

[0112] The starting module 520 is configured to start a target download process to download and decrypt the real-name attachment picture.

[0113] The processing module 530 is configured to perform real-name authentication processing on the real-name attachment picture based on the real-name service type in a case where the real-name attachment picture is successfully downloaded and decrypted.

[0114] Optionally, the starting module is further configured to:

[0115] In a case where the real-name attachment picture fails to be downloaded or uploaded, a report is made to notify an initiator.

[0116] Optionally, the processing module includes:

[0117] The first processing unit is configured to perform real-name authentication processing on the real-name attachment picture based on a first process in a case where the real-name service type is a personal real-name service.

[0118] The second processing unit is configured to perform real-name authentication processing on the real-name attachment picture based on a second process in a case where the real-name service type is a batch unit real-name service, and the first process and the second process are different.

[0119] Optionally, the second processing unit is specifically configured to:

[0120] determine any unit real-name information to be processed from the batch unit real-name task;

[0121] call an online company verification once to process the any unit real-name information.

[0122] Optionally, the processing module further includes:

[0123] The first authentication unit is configured to switch a connection with an image center to a connection with an online company to perform real-name authentication when an exception occurs in processing an upload image center.

[0124] The acquisition unit is configured to acquire a real-name authentication result returned by the online company.

[0125] Optionally, the acquisition unit is further configured to:

[0126] ​updating the processing state of the real-name registration process in the province;

[0127] judging the real-name authentication result according to the fields in the real-name processing table of the Internet of Vehicles;

[0128] in the case that the real-name authentication result is online company verification success or does not need to call online real-name processing, calling the interface of the online company to return a successful record;

[0129] in the case that the real-name authentication result is failure, recording error information and completing the processing.

[0130] Optionally, the processing module is further configured to:

[0131] after the real-name task is completed, performing asynchronous processing on the image center;

[0132] after the processing of the image center is completed, backfilling the photo serial number of successful upload to the order to complete the real-name authentication business in the province.

[0133] In the embodiments of the present disclosure, the Internet of Things system first responds to the receipt of the real-name request of the Internet of Vehicles, adjusts the download waiting time of the real-name attachment picture, judges the real-name business type, starts the target download process to download and decrypt the real-name attachment picture, and in the case that the real-name attachment picture is successfully downloaded and decrypted, performs real-name authentication processing on the real-name attachment picture based on the real-name business type. Therefore, the decryption coupling technology can be adopted for the real-name authentication of the Internet of Vehicles, the platform asynchronous processing can be realized, the time consumption of the overall real-name task can be reduced, and the business processing efficiency can be improved. The automatic guarantee technology of the real-name authentication business interface of the Internet of Vehicles in a specific scene can reduce the problem that the vehicle owner cannot be real-name in the case of system abnormality, greatly reduces the operation and maintenance workload and difficulty, improves the real-name authentication processing efficiency and success rate of the Internet of Vehicles, and is suitable for the business processing flow optimization of multiple system interaction and high time requirement.

[0134] Figure 6 is a schematic diagram of a real-name authentication device of the Internet of Vehicles according to another embodiment of the present disclosure. As shown in Figure 6 the real-name authentication device 600 of the Internet of Vehicles is configured in a real-name registration management platform, and includes:

[0135] a second receiving module 610 configured to receive a real-name registration request initiated by a user through a vehicle enterprise platform, wherein the real-name registration request contains a real-name attachment picture;

[0136] a verification module 620 configured to perform real-name verification on a target platform based on the real-name registration request;

[0137] The authentication module 630 is configured to send the real-name registration request to the unified converged support gateway if the verification is passed, so that the unified converged support gateway sends a vehicle network real-name authentication request to an Internet of Things system.

[0138] In the embodiments of the present disclosure, the real-name registration management platform first receives a real-name registration request initiated by a user through a vehicle enterprise platform, wherein the real-name registration request contains a real-name attachment picture, then performs real-name verification on a target platform based on the real-name registration request, and then sends the real-name registration request to the unified converged support gateway if the verification is passed, so that the unified converged support gateway sends a vehicle network real-name authentication request to an Internet of Things system. Therefore, the real-name registration request initiated by the user through the vehicle enterprise platform can be efficiently processed, and the identity of the vehicle network user can be ensured to be real and reliable. The platform can quickly receive the real-name registration request from the vehicle enterprise platform, contain the real-name information and the real-name attachment picture of the user, realize fast response and timely processing, accurately judge whether the real-name information provided by the user is real and effective, and ensure that only a legal user can complete the real-name registration. Through the processing of the platform, the unified converged support gateway can send a vehicle network real-name authentication request to an Internet of Things system, further promote the real-name authentication work of the vehicle network user, and improve the security and reliability of the entire vehicle network system.

[0139] According to the embodiments of the present disclosure, the present disclosure further provides an electronic device, a readable storage medium and a computer program product.

[0140] Figure 7 A block diagram of an exemplary computer device suitable for implementing the embodiments of the present disclosure is shown. Figure 7 The computer device 12 shown is merely one example and should not be taken as limiting the functionality or use of the embodiments of the present disclosure.

[0141] As shown in Figure 7 The computer device 12 is in the form of a general-purpose computing device. The components of the computer device 12 can include, but are not limited to, one or more processors or processing units 16, a system memory 28, and a bus 18 that connects the various system components, including the system memory 28 and the processing unit 16.

[0142] Bus 18 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, a graphics acceleration bus, a processor or local bus using any of a variety of bus architectures. By way of example, these architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus.

[0143] Computer device 12 typically includes a variety of computer system readable media. Such media can be any available media that is accessible by computer device 12 and includes both volatile and non-volatile media, removable and non-removable media.

[0144] Memory 28 can include computer system readable media in the form of volatile memory, such as random access memory (RAM) 30 and / or cache memory 32. Computer device 12 can further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, storage system 34 can be provided for reading from and writing to a non-removable, non-volatile magnetic media (not shown and typically called a "hard drive"). Figure 7

[0145] Although Figure 7 not shown in FIG. 1, a disk drive, an optical disk drive and / or a tape drive, a flash memory or other similar medium can also be used. In these instances, computer device 12 can also be provided with one or more interfaces to enable it to communicate with these storage devices. Storage media 28 can include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the disclosure.

[0146] ​Program / utility 40 having a set of program modules 42 can be stored in memory 28 by way of example, such program modules 42 include an operating system, one or more application programs, other program modules, and program data, each or some combination thereof, which can include implementation of the network environment as in each of the above examples or some combination thereof. Program modules 42 generally carry out the functions and / or methodologies of embodiments of the disclosure as described herein.

[0147] Computer device 12 can also communicate with one or more external devices 14 such as a keyboard or pointing device, a display 24, etc. one or more devices that enable a user to interact with computer device 12 and / or one or more devices that enable computer device 12 to communicate with one or more other computing devices. Such communication can be via input / output (I / O) interfaces 22. Further, computer device 12 can communicate with one or more networks such as a local area network (LAN), a wide area network (WAN), and / or the Internet through network adapter 20. As an example, network adapter 20 can include a modem, a network card (wireless or wired), or other well-known interface devices. As depicted, network adapter 20 communicates with the other components of computer device 12 via bus 18. It should be appreciated that although not shown, other hardware and / or software modules could be used in conjunction with computer device 12. Such as, but not limited to, microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data archival storage systems, etc.

[0148] Processing unit 16 performs various function applications and data processing by running programs stored in system memory 28, such as implementing the vehicle networking real-name authentication method mentioned in the foregoing embodiments.

[0149] Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the application disclosed herein. The disclosure is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice in the art to which the disclosure pertains. The specification and examples are to be regarded as illustrative only, and the true scope and spirit of the disclosure are indicated by the following claims.

[0150] It should be understood that the present disclosure is not limited to the precise structures as set forth above and as shown in the attached drawings, and that various modifications and changes can be made without departing from the scope thereof. The scope of the present disclosure is limited only by the claims appended hereto.

[0151] It should be noted that in the description of the present disclosure, the terms "first", "second", etc. are only used for descriptive purposes and cannot be understood as indicating or implying relative importance. In addition, in the description of the present disclosure, the meaning of "a plurality of" is two or more, unless otherwise stated.

[0152] Any process or method descriptions in flow charts or described elsewhere herein can be understood as representing code modules, segments, or portions of code that include one or more executable instructions for implementing specific logic functions or other processes. The various embodiments of the present disclosure can include additional or fewer steps or processes, and the order of the steps or processes can be changed, including according to the function involved, without departing from the scope of the embodiments of the present disclosure, which should be understood by those skilled in the art.

[0153] It should be understood that various parts of the present disclosure can be implemented in hardware, software, firmware, or a combination thereof. In the above-described embodiments, a plurality of steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented by any one or a combination of the following technologies known in the art: discrete logic circuit with logic gate circuit for implementing logic functions on data signals, application specific integrated circuit with suitable combination logic gate circuit, programmable gate array (PGA), field programmable gate array (FPGA), etc.

[0154] Those skilled in the art of the present technology can understand that all or part of the steps carried out by the above-mentioned embodiments can be completed by programs instructing related hardware, and the programs can be stored in a computer readable storage medium, which includes one or a combination of steps of the method embodiments when executed.

[0155] In addition, each functional unit in each embodiment of the present disclosure can be integrated in one processing module, or each unit can exist physically, or two or more units can be integrated in one module. The above-mentioned integrated module can be realized in the form of hardware or in the form of software functional module. The integrated module, if realized in the form of software functional module and sold or used as an independent product, can also be stored in a computer readable storage medium. The above-mentioned storage medium can be read-only memory, disk or optical disk, etc.

[0156] In the description of the specification, the description of the terms "one embodiment", "some embodiments", "an example", "a specific example", or "some examples" etc. means that the specific features, structures, materials or characteristics described in connection with the embodiment or example are included in at least one embodiment or example of the present disclosure. In the specification, the illustrative expressions of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described can be combined in any suitable manner in one or more embodiments or examples.

[0157] Although the embodiments of the present disclosure have been shown and described above, it is understood that the above-described embodiments are exemplary and are not to be construed as limiting the present disclosure, and those skilled in the art can make changes, modifications, replacements and variations to the above-described embodiments within the scope of the present disclosure.

Claims

1. A method for real-name authentication in the Internet of Vehicles, characterized in that, Performed by an Internet of Things (IoT) system, the method includes: Upon receiving a vehicle-to-everything (V2X) real-name registration request, the download waiting time for the real-name registration attachment image is adjusted, and the type of real-name registration service is determined. Start the target download process to download and decrypt the real-name attachment image; If the real-name attachment image is successfully downloaded and decrypted, and the real-name service type is personal real-name service, the real-name attachment image is processed for real-name authentication based on the first process; When the real-name service type is a batch unit real-name service, the real-name authentication process is performed on the real-name attachment image based on the second process, wherein the first process and the second process are different.

2. The method according to claim 1, characterized in that, After initiating the target download process to download the real-name attachment image, the process further includes: If the download or upload of the attached image fails, a notification will be sent to the initiator.

3. The method according to claim 1, characterized in that, The real-name authentication process for the attached image based on the second process includes: Determine any unit's real-name information to be processed from the batch unit real-name tasks; The system invokes an online company verification function to process the real-name information of any of the entities.

4. The method according to claim 1, characterized in that, After performing real-name authentication processing on the real-name attachment image based on the real-name service type, the method further includes: When an error occurs while processing the uploaded image center, the connection to the image center will be switched to a connection to the online company for real-name authentication. Obtain the real-name authentication result returned by the online company.

5. The method according to claim 4, characterized in that, After obtaining the real-name authentication result returned by the online company, the process also includes: Update the processing status of the real-name registration process within the province; The real-name authentication result is judged based on the fields in the vehicle network real-name processing table; If the real-name authentication result is that the online company has successfully verified the identity or if there is no need to call the online real-name processing, then the interface of the online company is called to return a success record; If the real-name authentication result fails, the error message will be recorded and the process will be completed.

6. The method according to claim 4, characterized in that, Also includes: After the real-name registration task is completed, the image center is processed asynchronously; After the image center completes the processing, the successfully uploaded photo's transaction history is populated back into the order to complete the provincial real-name authentication process.

7. A vehicle-to-everything (V2X) real-name authentication device, characterized in that, Configured in Internet of Things (IoT) systems, including: The first receiving module is used to respond to the received vehicle network real-name request, adjust the download waiting time of the real-name attachment image, and determine the real-name service type; The startup module is used to start the target download process to download and decrypt the real-name attachment image; The processing module is used to perform real-name authentication processing on the real-name attachment image based on the real-name service type when the real-name attachment image is successfully downloaded and decrypted. The processing module includes: The first processing unit is used to perform real-name authentication processing on the real-name attachment image based on the first process when the real-name service type is personal real-name service. The second processing unit is used to perform real-name authentication processing on the real-name attachment image based on a second process when the real-name service type is a batch unit real-name service, wherein the first process and the second process are different.

8. An electronic device, comprising: At least one processor; as well as A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the method of any one of claims 1-6.

9. A non-transitory computer-readable storage medium storing computer instructions, wherein, The computer instructions are used to cause the computer to perform the method according to any one of claims 1-6.

Images