A vehicle SIM card real-name authentication system and method

Abstract

The present application relates to a kind of vehicle SIM card real-name authentication system and method, belong to automobile technical field, the system includes: receiving module is used to obtain the VIN code and vehicle information of vehicle from real-name authentication request;Query module is used to determine the target host factory corresponding to vehicle SIM card;Encapsulation module is used to encapsulate the identity information of car owner, the VIN code and ICCID of vehicle as authentication request data packet, and authentication request data packet is forwarded to the real-name authentication platform of target host factory by network routing module;State management module is used to obtain the binding operation result returned by real-name authentication platform, and based on binding operation result triggers the channel mode of corresponding vehicle SIM card;Storage module is used to store the vehicle-card binding relationship and full life cycle change record formed after each real-name operation.The system realizes the full-process automation unified management of vehicle SIM card real-name authentication in the environment of multiple host factories by the synergistic cooperation of the above module.

Description

Technical Field

[0001] This invention belongs to the field of automotive technology, and in particular relates to a vehicle SIM card real-name authentication system and method. Background Technology

[0002] In the field of connected vehicles, vehicle-embedded SIM cards must undergo real-name authentication to activate full communication services. The procurement and management authority for vehicle SIM cards belongs to each vehicle manufacturer (OEM), which establishes an independent real-name authentication management platform with the operator. For connected vehicle operators cooperating with multiple OEMs, different batches of vehicles belong to different OEM management systems, and the real-name authentication platforms of each OEM have significant differences in interface protocols, data formats, and field definitions. In existing technologies, SIM card ownership determination relies on manual experience, lacks system support, and is prone to errors leading to submissions to incorrect platforms; repeated switching between multiple platforms results in low efficiency; furthermore, the real-name status and SIM card communication channel mode lack unified linkage and control, and lifecycle change records are stored in a scattered manner, making traceability and auditing difficult and failing to meet compliance management requirements. Summary of the Invention

[0003] In view of the shortcomings of the prior art, the purpose of the invention is to provide a vehicle SIM card real-name authentication system and method.

[0004] A first aspect of the present invention provides a vehicle SIM card real-name authentication system, comprising: a receiving module, configured to receive a real-name authentication request from a vehicle SIM card and obtain the vehicle's VIN code and vehicle information from the real-name authentication request, wherein the vehicle information includes the vehicle owner's identity information or the identity information of the company to which the vehicle belongs; a query module, configured to determine the target OEM corresponding to the vehicle SIM card based on the binding relationship between the vehicle's VIN code and the vehicle's SIM card ICCID; an encapsulation module, configured to extract the configuration rules corresponding to the identifier from an interface adaptation library based on the identifier of the target OEM, and encapsulate the vehicle owner's identity information, the vehicle's VIN code, and the ICCID into an authentication request data packet according to the data format and field definitions specified by the target OEM on the real-name authentication platform, and forward the authentication request data packet to the target OEM's real-name authentication platform through a network routing module; a status management module, configured to obtain the binding operation result returned by the real-name authentication platform and trigger the corresponding channel mode of the vehicle SIM card based on the binding operation result; and a storage module, configured to store the vehicle-SIM card binding relationship and full lifecycle change records formed after each real-name operation.

[0005] A second aspect of the present invention provides a method for real-name authentication of a vehicle SIM card, comprising: receiving a real-name authentication request from a vehicle SIM card, and obtaining the vehicle's VIN code and vehicle information from the real-name authentication request, wherein the vehicle information includes the vehicle owner's identity information or the identity information of the enterprise to which the vehicle belongs; determining the target OEM corresponding to the vehicle SIM card based on the binding relationship between the vehicle's VIN code and the vehicle's SIM card ICCID; extracting the configuration rules corresponding to the identifier from an interface adaptation library based on the identifier of the target OEM, and encapsulating the vehicle owner's identity information, the vehicle's VIN code, and the ICCID into an authentication request data packet according to the data format and field definitions specified by the target OEM on the real-name authentication platform, and forwarding the authentication request data packet to the target OEM's real-name authentication platform through a network routing module; obtaining the binding operation result returned by the real-name authentication platform, and triggering the corresponding channel mode of the vehicle SIM card based on the binding operation result; and storing the vehicle-SIM card binding relationship and full lifecycle change record formed after each real-name operation.

[0006] A third aspect of the present invention provides an electronic device comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the method described in the second aspect of the present invention.

[0007] In a fourth aspect, the present invention provides a non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to cause the computer to perform the method described in the second aspect of the present invention.

[0008] The beneficial effects of this invention are as follows: The vehicle SIM card real-name authentication system and method described in this invention automatically identifies the OEM of the SIM card using the VIN code as the key through a query module, achieving precise positioning of the target platform and eliminating the manual judgment step; through a pre-built multi-OEM interface adaptation library in the encapsulation module, it automatically encapsulates authentication requests according to the protocols and formats specified by the target platform, achieving complete shielding of interface differences between multiple platforms; through a network routing module, it automatically routes requests to the corresponding OEM platform, achieving precise distribution of cross-platform requests; through a status management module, it automatically triggers the SIM card to switch between dual-channel, single-channel, and disabled states based on the binding result, achieving strict linkage between real-name status and communication capability; through a storage module, it persistently records the vehicle-SIM card binding relationship and change history, achieving traceable management of data throughout the entire lifecycle. Through the coordinated operation of the above modules, the system achieves fully automated and unified management of vehicle SIM card real-name authentication in a multi-OEM environment. Attached Figure Description

[0009] The accompanying drawings are for illustrative purposes only and are not intended to limit the invention. Throughout the drawings, the same reference numerals denote the same parts. It is obvious that the drawings described below are merely some embodiments of the present invention, and those skilled in the art can obtain other drawings based on these drawings.

[0010] Figure 1 This is a schematic diagram of a vehicle SIM card real-name authentication system according to an embodiment of the present invention; Figure 2 This is a flowchart of a vehicle SIM card real-name authentication method according to an embodiment of the present invention; Figure 3 This is a structural block diagram of an electronic device according to an embodiment of the present invention. Detailed Implementation

[0011] To enable those skilled in the art to better understand the technical solutions in the embodiments of the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. It should be understood that these descriptions are merely exemplary and are not intended to limit the scope of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0012] Furthermore, descriptions of well-known structures and techniques are omitted in the following description to avoid unnecessarily obscuring the concepts disclosed in this invention.

[0013] In the description of this invention, it should be noted that, unless otherwise explicitly specified and limited, the terms "center," "upper," "lower," "left," "right," "vertical," "horizontal," "inner," and "outer," etc., indicating orientation or positional relationships based on the orientation or positional relationships shown in the accompanying drawings, are only for the convenience of describing the invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of the invention. Furthermore, the terms "first," "second," and "third" are used for descriptive purposes only and should not be construed as indicating or implying relative importance. The terms "installed," "connected," and "linked" should be interpreted broadly; for example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal communication of two components. Those skilled in the art can understand the specific meaning of the above terms in this invention based on the specific circumstances.

[0014] 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 the present invention. Rather, they are merely examples of methods and systems consistent with some aspects of the invention as detailed in the appended claims.

[0015] In the connected vehicle industry, vehicles communicate with cloud servers via a built-in SIM card (also known as a dedicated connected vehicle SIM card or T-SIM card), enabling various services including remote vehicle monitoring, OTA upgrades, fault diagnosis, and connected services.

[0016] SIM cards used in public mobile communication networks must undergo real-name authentication before full communication services can be activated. For connected vehicle scenarios, the procurement, network access, and management authority for vehicle SIM cards belongs to the vehicle manufacturer with complete vehicle production qualifications (referred to as the OEM in this field). The OEM is responsible for applying for and managing SIM card resources from mobile communication operators. Each OEM establishes an independent real-name authentication management platform (referred to as the OEM real-name platform) with the corresponding operator. This platform is the only compliant entry point for completing the real-name binding operation of vehicle SIM cards.

[0017] In practical business contexts, there exists a type of connected vehicle operator (hereinafter referred to as the operator) that does not possess vehicle manufacturing qualifications. Its vehicle SIM cards are procured and managed by multiple OEMs through authorized cooperation agreements. Typical characteristics of this type of operator include: establishing cooperative relationships with multiple car companies and other OEMs simultaneously; different batches of vehicles and their built-in SIM cards belonging to different OEM management systems; and differences in interface protocols, data formats, field definitions, and authentication methods across OEMs' real-name authentication platforms.

[0018] The existing technology has the following four technical problems: Problem 1: Ownership determination relies on manual methods, resulting in a high error rate. When real-name authentication of a vehicle's SIM card is required, operators must first determine which OEM (Original Equipment Manufacturer) the SIM card belongs to before proceeding to the corresponding OEM's real-name authentication platform. This determination process lacks system support, relies on manual experience and paper records, and is prone to submission to the wrong platform due to untimely information updates or human error, causing confusion regarding vehicle-SIM card relationships. Problem 2: Switching between multiple platforms is cumbersome and inefficient. Operating companies must maintain accounts and operating procedures for multiple OEM platforms simultaneously. When handling complex scenarios such as vehicle transfer, SIM card replacement, and batch delivery, repeated switching between different OEM real-name authentication platforms is necessary, resulting in a long overall operation cycle and high labor costs. Problem 3: Lack of a unified SIM card communication status management mechanism. The SIM card's communication capabilities are directly tied to its real-name registration status: after the factory-preset 300M test data is exhausted, the SIM card automatically switches to single-channel mode (public network channel closed); dual-channel mode can only be restored after real-name authentication is completed; after unbinding, the SIM card enters a deactivated state (both channels are closed). Under the existing decentralized operation model, the linkage control between real-name registration status and channel status relies on the independent logic of each OEM platform, making it impossible for operators to establish a unified status awareness and control capability. Problem 4: Dispersed data throughout the entire lifecycle, making traceability difficult. During vehicle use, multiple nodes are involved, such as initial real-name registration, transfer of ownership, SIM card replacement, and vehicle retirement. The relevant real-name change history is stored separately on the real-name registration platforms of various OEMs, making it impossible for operators to trace, query, and audit from a unified perspective, which is difficult to meet compliance management requirements.

[0019] To this end, the present invention proposes a vehicle SIM card real-name authentication system, method and related equipment. Specifically, the vehicle SIM card real-name authentication system, method and related equipment of the present invention are described below with reference to the accompanying drawings.

[0020] Figure 1 This is a schematic diagram of a vehicle SIM card real-name authentication system according to an embodiment of the present invention. It should be noted that the vehicle SIM card real-name authentication system of this embodiment is applicable to the vehicle SIM card real-name authentication method of this embodiment. This vehicle SIM card real-name authentication system can be configured on an electronic device or in a server. This application does not limit the scope of the invention in this regard.

[0021] like Figure 1 As shown, the vehicle SIM card real-name authentication system includes: The receiving module 110 is used to receive the real-name authentication request of the vehicle SIM card and obtain the vehicle's VIN code and vehicle information from the real-name authentication request. The vehicle information includes the identity information of the vehicle owner or the identity information of the company to which the vehicle belongs.

[0022] The query module 120 is used to determine the target OEM corresponding to the vehicle SIM card based on the binding relationship between the vehicle's VIN code and the vehicle's SIM card ICCID.

[0023] The encapsulation module 130 is used to extract the configuration rules corresponding to the identifier from the interface adaptation library based on the identifier of the target OEM, and encapsulate the vehicle owner's identity information, the vehicle's VIN code and ICCID into an authentication request data packet according to the data format and field definition specified by the target OEM on the real-name authentication platform, and forward the authentication request data packet to the target OEM's real-name authentication platform through the network routing module.

[0024] The status management module 140 is used to obtain the binding operation result returned by the real-name authentication platform and trigger the channel mode of the corresponding vehicle SIM card based on the binding operation result.

[0025] Storage module 150 is used to store the vehicle card binding relationship and lifecycle change records formed after each real-name operation.

[0026] In other words, the query module 120 automatically identifies the OEM of the SIM card using the VIN code as the key, achieving precise positioning of the target platform and eliminating the manual judgment step; the encapsulation module 130 automatically encapsulates the authentication request according to the protocol and format specified by the target platform through a pre-built multi-OEM interface adaptation library, achieving complete shielding of multi-platform interface differences; the network routing module automatically routes the request to the corresponding OEM platform, achieving precise distribution of cross-platform requests; the status management module 140 automatically triggers the SIM card to switch between dual-channel, single-channel, and disabled states based on the binding result, achieving strict linkage between real-name status and communication capability; and the storage module persistently records the vehicle-SIM card binding relationship and change history, achieving traceable management of data throughout the entire lifecycle. Through the coordinated operation of the above modules, the system achieves fully automated and unified management of vehicle SIM card real-name authentication in a multi-OEM environment.

[0027] In embodiments of the present invention, the sources of triggering real-name authentication requests include multiple sources. For example, vehicle owners can proactively submit real-name authentication requests through mobile applications or web pages; after-sales personnel of vehicle networking operators can enter real-name authentication requests through the internal operation support system OSS after completing vehicle delivery or repair services; for large enterprise customers, their bulk-purchased vehicles can have their account managers submit bulk real-name authentication requests uniformly through the back-end management system.

[0028] For example, when receiving a real-name authentication request, the receiving module 110 can extract core key information from the structured or unstructured real-name authentication request, namely the vehicle identification number (VIN) of the vehicle to be authenticated and the identity information of the vehicle owner or the company to which the vehicle belongs. For individual vehicle owners, the identity information includes at least the owner's name and identification number (such as ID card number); for corporate vehicle owners, the identity information includes at least the company name and unified social credit code.

[0029] In an embodiment of the present invention, the query module 120 is further configured to query the binding relationship between the vehicle's VIN code and ICCID from the operator's unified operation and management platform using the vehicle's VIN code as the query key; wherein, if the query for the binding relationship fails, the binding relationship is queried again based on a preset interval and number of retries; wherein, if the binding relationship is not found, an error message is returned and the process is terminated.

[0030] In other words, when the receiving module 110 sends the vehicle's VIN code to the query module 120, the query module 120 uses the VIN code as the query key to send a query request to the operator's unified operation and management platform. This query request checks the real-time matching and binding relationship between the VIN code and the integrated circuit card identifier (ICCID) recorded on the operator's side. As the authoritative source of SIM card data across the entire network, the operator's unified operation and management platform can accurately return the ICCID bound to the current VIN and the target OEM to which the SIM card belongs.

[0031] Since network fluctuations or sudden high system loads may cause query timeouts or failures, the query module 120 incorporates a retry mechanism. In one embodiment, when the initial query fails to receive a valid response, the query module 120 automatically re-initiates the query at preset intervals (e.g., 5 seconds) and with a set number of retries (e.g., 3 times). If no valid data is obtained after reaching the maximum number of retries, or if the operator's unified management platform explicitly returns a result indicating no matching relationship was found, the query module 120 determines that the current VIN code is not bound to a valid SIM card. It then outputs an error message indicating no binding relationship to the operator and terminates the current real-name authentication process, thereby preventing subsequent invalid operations.

[0032] When the binding relationship is obtained, the query module 120 associates the VIN code, ICCID and the identifier of the target OEM and sends them to the encapsulation module 130.

[0033] In embodiments of the present invention, the content of the interface adapter library includes, but is not limited to, interface protocol types (e.g., RESTful API, SOAP Web Service, etc.), data interaction formats (e.g., JSON, XML, etc.), mapping rules for each field, and parameters required for authentication and authorization (e.g., API Key, Token acquisition method, etc.).

[0034] In an embodiment of the present invention, when the encapsulation module 130 receives the association relationship sent by the query module 120, it extracts the identifier of the target OEM and then uses this identifier as an index to dynamically load the corresponding interface specification configuration of the target OEM from the interface adaptation library. Subsequently, the encapsulation module 130 performs format conversion and field mapping on the received vehicle owner identity information, VIN code, and ICCID according to the loaded configuration rules. For example, for OEM A, its platform requires that "vehicle owner name" be mapped to the field "name" in JSON format; while for OEM B, its platform requires that "vehicle owner name" be mapped to the field "legalPerson" in XML format. Through the conversion in the adaptation library, the data encapsulation module ensures that the final output authentication request data packet semantically conforms to the requirements of the target OEM's real-name authentication platform.

[0035] The authentication request data includes the vehicle owner's name, vehicle owner's document type, vehicle owner's document number, vehicle's VIN code, and the vehicle's SIM card ICCID; the identity information of the company to which the vehicle belongs is verified, and the encapsulated content also includes the company name, unified social credit code, and legal representative information.

[0036] In an embodiment of the present invention, when the encapsulation module 130 forwards the authentication request data packet to the real-name authentication platform of the target OEM through the network routing module, the real-name authentication platform performs a binding operation. In this operation, if the real-name authentication platform verifies that the vehicle owner's identity information is valid and the vehicle SIM card is in normal status, it binds the vehicle owner's identity information, the vehicle's VIN code, and the vehicle SIM card; and sends the binding operation result to the status management module 140.

[0037] In an embodiment of the present invention, when the status management module 140 receives the binding operation result returned by the real-name authentication platform, it can determine the binding operation result returned by the real-name authentication platform. Specifically, by parsing the business status code in the binding operation receipt, if the business status code is a success code pre-set by the target OEM on the real-name authentication platform, the binding operation is initially determined to be successful; if the business status code is a failure code, or no valid receipt is received, the binding operation is determined to be failed, and the subsequent channel switching process is terminated; if the binding operation is initially determined to be successful, the failure reason field carried in the binding operation receipt is further read. If the failure reason field is not empty and its content indicates that the binding has not taken effect, the initial determination is overturned, and the binding operation is ultimately determined to be a failure.

[0038] Among these, the content binding failure includes, but is not limited to, incorrect identity information format, non-existent ICCID, ICCID already occupied by another identity, and abnormal SIM card status.

[0039] In an embodiment of the present invention, the state management module 140 triggers the corresponding channel mode of the vehicle SIM card based on the binding operation result. Specifically, if the binding operation is successful, the system automatically sends a command to the network side to switch the vehicle SIM card from its current single-channel mode to a dual-channel mode and activate the preset public network reserved traffic. If the preset public network test traffic is exhausted, the system automatically switches back to single-channel mode. If the binding operation fails, the system determines the reason for the failure and issues an alarm message, while the vehicle SIM card retains its original channel mode.

[0040] Specifically, when the current state is the initial state, the channel mode is the dual-channel mode, and the dual-channel mode is configured with preset public network reserved traffic; when the current state is the disabled state, the channel mode is the dual-channel both-off mode; when the current state is the activated state, the channel mode of the vehicle's SIM card is determined based on the matching of the configuration identifier and / or configuration file returned by the CMP card management platform with the corresponding preset combination configuration.

[0041] Specifically, if the current state is "activated," the system determines the first string of the configuration identifier and the second string of the configuration file. If the first string matches a string in the first preset whitelist and / or the second string matches a string in the second preset whitelist, the channel mode is determined to be dual-channel mode. If the first string matches a string in the third preset whitelist and / or the second string matches a string in the fourth preset whitelist, the channel mode is determined to be single-channel mode. Furthermore, if the preset public network test traffic has been used up, the current state is determined to be "activated." In other words, if the current state is "activated," the system compares the configuration returned by the CMP card management platform to determine the corresponding channel mode. If a dual-channel configuration file is matched, the channel mode is determined to be dual-channel mode; if a single-channel configuration file is matched, the channel mode is determined to be single-channel mode.

[0042] In embodiments of the present invention, the storage module 150 can store data based on a relational database (e.g., MySQL) or a distributed NoSQL database (e.g., MongoDB). After each successful real-name registration operation, the storage module 150 creates or updates a record. The record's fields include at least: VIN code, ICCID, OEM identifier, current real-name registration status (e.g., registered, unregistered), current channel mode (e.g., dual-channel, single-channel, disabled), bound vehicle owner identifier (personal ID number or corporate social credit code), and operation timestamp. Furthermore, the storage module 150 can record a detailed log of each status change. This ensures that any change in vehicle-card binding is traceable, providing a solid data foundation for subsequent compliance audits and problem tracing.

[0043] In an embodiment of the present invention, the system further includes a transfer processing module, which is used to perform vehicle transfer real-name processing operations.

[0044] The system includes: receiving a transfer request and extracting the vehicle's VIN, first owner's identity information, and second owner's identity information based on the request; a query module determining the OEM corresponding to the SIM card based on the binding relationship between the vehicle's VIN and ICCID; submitting an unbinding application request to the OEM's corresponding real-name authentication platform through the network routing module; and triggering the SIM card to enter a deactivated state if the unbinding is successful; and submitting a binding application request to the OEM's corresponding real-name authentication platform through the network routing module for the second owner's identity information. If the binding is successful, the state management module triggers the SIM card to restore dual-channel mode, while the storage module updates the owner identifier and retains the transfer change record.

[0045] In other words, when the ownership transfer processing module receives a ownership transfer request, it first extracts the VIN code, the original owner's identity information (i.e., the first owner's identity information), and the new owner's identity information (i.e., the second owner's identity information) from the request. Then, it calls the query module 120 to determine the OEM manufacturer of the SIM card corresponding to the VIN. In a specific ownership transfer operation embodiment, the ownership transfer processing module initiates an unbinding operation for the original owner to the OEM manufacturer's real-name authentication platform through the network routing module. After receiving a successful unbinding receipt from the real-name authentication platform, the status management module 140 sets the corresponding SIM card to a disabled state to cut off its communication capability.

[0046] Then, the transfer processing module, using the new owner's identity information, initiates a new binding operation again through the network routing module to the same OEM's real-name authentication platform. After the new binding is successful, the status management module 140 restores the SIM card to dual-channel mode, restoring its communication capability. Finally, the storage module updates the owner identifier corresponding to the VIN and fully retains the change history chain from the original owner binding → unbinding → new owner binding.

[0047] In an embodiment of the present invention, the system further includes a card replacement processing module, which is used to perform vehicle card replacement real-name processing operations.

[0048] The system includes the following steps: receiving a SIM card replacement request and extracting the vehicle's VIN code, the first SIM card's ICCID, and the second SIM card's ICCID based on the request; querying module 120 determines the OEM corresponding to the first SIM card based on the binding relationship between the vehicle's VIN code and the first SIM card's ICCID; submitting an unbinding request to the OEM's corresponding real-name authentication platform via a network routing module; and triggering the first SIM card to enter a deactivated state upon successful unbinding. Then, querying module 120 determines the OEM corresponding to the second SIM card based on the binding relationship between the vehicle's VIN code and the second SIM card's ICCID; submitting a binding request to the OEM's corresponding real-name authentication platform via a network routing module; and triggering the SIM card to switch to dual-channel mode upon successful binding, while storage module 150 updates the vehicle-SIM card binding record, establishing the association between the vehicle's VIN code and the second SIM card's ICCID.

[0049] In other words, the card replacement processing module receives a card replacement request containing the VIN code, the old SIM card ICCID (i.e., the first SIM card ICCID), and the new SIM card ICCID (i.e., the second SIM card ICCID). Its core processing logic is to first unbind the old card and then bind the new card. First, the card replacement processing module queries the original manufacturer (OEM) of the old SIM card based on its ICCID and initiates an unbinding request to that platform via the network routing module. After successful unbinding, the old card enters a deactivated state, and its binding relationship with the original VIN is released. Second, it calls the query module 120 to query the OEM corresponding to the new SIM card's ICCID. It should be noted that the new card may belong to the same OEM or a different OEM, and the query module can accurately identify both. Finally, using the vehicle's current legal owner's identity information, the card replacement processing module initiates a binding request to the real-name authentication platform of the OEM to which the new SIM card belongs via the network routing module. After successful binding, the status management module 140 triggers the new SIM card to switch to dual-channel mode, while the storage module 150 establishes the association between the VIN code and the new ICCID and updates all relevant records, thereby completing the entire card replacement process and ensuring seamless connection of vehicle communication services.

[0050] In an embodiment of the present invention, the system further includes a record query module, which uses the vehicle's VIN code as the query dimension to call the query interface of the corresponding target OEM on the real-name authentication platform to obtain the historical real-name change records of the vehicle's SIM card; wherein, the historical real-name change records include: the operation time of each binding and unbinding operation, the operator's identification, the vehicle owner's identity information before and after the change, the vehicle's SIM card ICCID, and the type of real-name status change.

[0051] In an embodiment of the present invention, the system further includes a batch processing module for receiving batch real-name requests and processing them based on the batch real-name requests.

[0052] The batch processing module receives a batch real-name registration request, which is a dataset containing multiple records. Each record corresponds to a vehicle to be authenticated and includes its VIN code and the corresponding vehicle owner's identity information.

[0053] The batch processing module's first step is grouping. It iterates through all records in the request, calling the attribution query module for each record to retrieve the corresponding SIM card's manufacturer. After iteration, the batch processing module groups all records according to their manufacturer, for example, creating groups like "Manufacturer A: 80 records," "Manufacturer B: 50 records," and "Manufacturer C: 20 records."

[0054] After grouping, the batch processing module enters the batch submission phase. For each group, the batch processing module calls the encapsulation module and the network routing module to encapsulate all authentication requests within the group and submit them all at once through the batch interface supported by the corresponding OEM's real-name authentication platform. This parallel processing method greatly reduces the number of cross-platform switches and network interactions, shortening the delivery processing time for hundreds of vehicles from hours to minutes.

[0055] After receiving the batch processing results from each OEM platform, the status management module 140 and storage module 150 work together to process each success and failure record. For successful entries, a channel mode switch is triggered and the binding relationship is stored; for failed entries, detailed reasons for failure are recorded. Finally, the batch processing module generates a batch operation result report containing success and failure details for operations personnel to review. For failed entries, the system automatically marks them and triggers a manual follow-up process.

[0056] In addition, this batch processing module also supports batch unbinding operations. For example, when a company retires a large number of vehicles, it can efficiently remove the real-name relationship of a large number of SIM cards and turn off their communication capabilities.

[0057] In one embodiment of the present invention, the specific working logic of the state management module 140 includes: Initial state: When a vehicle leaves the factory, its built-in SIM card is in dual-channel mode, but only 300M of public network traffic is reserved in this mode. This allows for basic network connectivity verification when the vehicle rolls off the production line, without requiring real-name authentication. When the status management module 140 detects that this reserved test traffic has been used up, it automatically sends a command to the network side to switch the SIM card to "single-channel mode," that is, closing the public network channel and retaining only the enterprise private network channel. This ensures that basic remote diagnostics and other services for the vehicle are not affected, while restricting public network access for unregistered users.

[0058] The status transition after successful real-name authentication: When the network routing module receives the successful binding receipt from the target OEM's real-name authentication platform and sends the result to the status management module 140, the status management module 140 performs the following operations: First, it parses the business status code in the binding operation receipt. If the business status code is a success class code pre-set by the target OEM on the real-name authentication platform, the binding operation is initially determined to be successful. To ensure accuracy, the status management module 140 further reads the failure reason field carried in the receipt. If this field is not empty and its content indicates that the binding has not taken effect (e.g., the platform accepted the application but internal processing was delayed), the initial determination will be overturned, and the final determination will be failure. After the final determination of successful binding, the status management module 140 issues a channel mode switching command to switch the SIM card from single-channel mode to dual-channel mode. In this mode, the enterprise private network channel and the public network channel are activated simultaneously, and the preset reserved traffic on the official public network is automatically opened, thereby restoring the vehicle's full network connectivity service capabilities.

[0059] Post-unbinding status transition: Upon receiving a notification of successful unbinding (e.g., in vehicle ownership transfer or SIM card replacement scenarios), the status management module 140 triggers the SIM card to enter a disabled state. In this state, both the enterprise private network channel and the public network channel are closed, and the vehicle will completely lose its communication capabilities, ensuring the security of communication resources.

[0060] Status recovery: For SIM cards that are in a deactivated state, once they are re-bound through the real-name authentication process, the status management module 140 will restore them from the deactivated state to dual-channel mode and reactivate the reserved public network traffic.

[0061] In the first embodiment of the present invention, a bicycle real-name authentication scenario is taken as an example: Suppose that after delivering a vehicle (VIN: LGHXXXXXXXXX12345) to a customer, the after-sales personnel of a connected vehicle operator receive feedback from the customer that the vehicle's connected services are unavailable. Upon investigation, the after-sales personnel confirm that the vehicle's SIM card is currently in "single-channel mode" because the factory-preset test traffic has been exhausted, and the public network channel is closed. The after-sales personnel then initiate a SIM card real-name authentication request for the vehicle on the company's internal operations support system.

[0062] Step 101, Request Reception: The system's receiving module receives this request and parses out the VIN code "LGHXXXXXXXXX12345" and the customer's (vehicle owner's) name, ID number, and other identity information.

[0063] Step 102, Attribution Inquiry: The query module initiates a query to the operator's unified operation and management platform using "LGHXXXXXXXXX12345" as the key. The operator platform returns the result, confirming that the SIM card ICCID currently bound to this VIN is "89860624400013XXXXX", and its attribution OEM is "A Automobile Group Co., Ltd."

[0064] Step 103, request encapsulation: The encapsulation module uses "A" as an index to retrieve its interface specification from the interface adaptation library. Following this specification, the module maps the vehicle owner's name, ID number, VIN code, and ICCID to corresponding fields and encapsulates them into a JSON format data packet that conforms to the requirements of the A real-name authentication platform.

[0065] Step 104, Request Routing and Submission: The network routing module establishes a secure connection with the A real-name authentication platform and submits the encapsulated data packet to the platform's real-name binding interface.

[0066] Step 105, Result Reception and Status Switching: The A real-name authentication platform processes the request and returns a "Binding Successful" receipt. Upon receiving this receipt, the status management module sends an instruction to the network side to switch the SIM card channel mode (ICCID "89860624400013XXXXX") from single-channel to dual-channel and activate the reserved public network traffic. At this point, the vehicle network service is restored.

[0067] Step 106, Data Persistence: The storage module creates a new record, storing the VIN code, ICCID, OEM manufacturer, real-name status (already real-name registered), channel mode (dual channel), and vehicle owner information, and records the current operation timestamp.

[0068] In the second embodiment of the present invention, a scenario of real-name processing for vehicle ownership transfer is taken as an example: Suppose a vehicle (VIN: LJXXXXXXXXXX67890) needs to be transferred from its original owner A to a new owner B. The operations staff initiates the transfer process through the system.

[0069] Step 201, Request Reception and Information Extraction: The transfer processing module receives the transfer request and extracts the VIN "LJXXXXXXXXXX67890", the identity information of the original owner A, and the identity information of the owner B.

[0070] Step 202, Attribution Inquiry: The query module confirms that the SIM card (ICCID: 89860317XXXXXXXXXXX) corresponding to this VIN belongs to "Zhang San Automobile Co., Ltd."

[0071] Step 203, Initiate Unbinding: The transfer processing module initiates an unbinding request to Zhang San's vehicle real-name authentication platform through the network routing module. The platform returns a successful unbinding response.

[0072] Step 204, State Switching and Storage Update: The state management module sets the SIM card to a disabled state and cuts off communication. The storage module records this A unbinding operation.

[0073] Step 205, Initiate New Binding: The transfer processing module, using the new vehicle owner B's identity information, initiates a new binding request to Zhang San's vehicle real-name authentication platform again via the network routing module. The platform returns a successful binding response.

[0074] Step 206, Status Restoration and Storage Update: The status management module restores the SIM card to dual-channel mode, resuming communication. The binding relationship storage module updates the vehicle owner identifier to B and appends the B binding record, fully preserving the transfer history.

[0075] In the third embodiment of the present invention, a scenario of bulk delivery to large enterprise customers is taken as an example: Suppose a corporate customer purchases 150 vehicles at once, and real-name authentication needs to be completed in batches upon delivery.

[0076] Step 301, Receive Batch Request: The batch processing module receives a batch request file containing 150 records.

[0077] Step 302, Grouping by Affiliation: The batch processing module iterates through each record and calls the query module to find its affiliated OEM. Based on the query results, the 150 records are automatically grouped, for example: Group XX (80 vehicles), Group CC (50 vehicles), Group ZZ (20 vehicles).

[0078] Step 303, Batch Submission: The batch processing module executes three batch submission tasks in parallel. Task 1 submits 80 requests from group XX to the XX real-name authentication platform via the network routing module; Task 2 submits 50 requests from group CC to the CC real-name authentication platform; Task 3 submits 20 requests from group ZZ to the ZZ real-name authentication platform.

[0079] Step 304, Result Processing and Report Generation: Each platform returns the batch processing results. The status management module processes each result individually; if successful, it switches channels; if unsuccessful, it records the reason. The module summarizes all results and generates a master report showing 148 successful vehicles and 2 unsuccessful vehicles, along with the VIN codes and specific reasons for the unsuccessful vehicles, for manual follow-up.

[0080] In the fourth embodiment of the present invention, the scenario of vehicle card replacement real-name processing is taken as an example: Suppose that the SIM card of the vehicle (VIN: LCXXXXXXXX09876) needs to be replaced due to physical damage.

[0081] Step 401, Receive Card Replacement Request: The card replacement processing module receives a request containing VIN "LCXXXXXXXX09876", old ICCID "89860XXXXXXXXXXXXXXXXX1" and new ICCID "89860XXXXXXXXXXXXXXXXX2".

[0082] Step 402, Unbinding the Old Card: The query module confirms that the old card belongs to the GG Bus platform and initiates an unbinding request to it through the network routing module. After successful unbinding, the old card enters a deactivated state.

[0083] Step 403, New Card Binding: The query module is invoked to check the ownership of the new ICCID "89860XXXXXXXXXXXXXXXXX2", confirming that it also belongs to "GG Bus". Subsequently, the card replacement processing module, using the existing legal owner's identity information of the vehicle, initiates a binding request for the new card to the GG Bus real-name platform through the network routing module. After successful binding, the new card switches to dual-channel mode.

[0084] Step 404, Storage Relationship Update: The storage module updates the vehicle card binding record, unlinks the VIN from the old ICCID, establishes the binding relationship between the VIN and the new ICCID, and records the card replacement change log. At this point, the card replacement process is complete, and vehicle communication returns to normal.

[0085] As can be seen from the above description of specific embodiments, the system provided by the present invention effectively solves the problems of fragmented operation, low efficiency, disconnected status, and difficulty in data traceability faced by vehicle SIM card real-name authentication under the multi-OEM cooperation model through modular design, automated process, and unified interface adaptation. The vehicle SIM card real-name authentication system according to embodiments of the present invention eliminates the manual step of determining SIM card ownership. By calling the VIN-ICCID matching query interface of the operator's unified operation and management platform, the system automatically completes the identification and confirmation of the OEM, completely eliminating the problem of incorrect platform submission caused by human error. It achieves unified adaptation of real-name platform interfaces from multiple OEMs. Through a pre-configured multi-OEM platform interface adaptation library and data encapsulation mechanism, the differences in interface protocols, data formats, and field definitions of various OEM real-name platforms are shielded from upper-layer services, achieving a unified entry point for multiple OEMs with a single operating procedure. An automatic linkage mechanism between real-name status and SIM card channel mode is established. The rules and triggering conditions for the transition between four states of the SIM card—initial dual-channel at the factory, single-channel after activation, dual-channel after real-name registration, and deactivated after unbinding—are clearly defined. Channel switching is automatically executed through the status management module, ensuring a strict correspondence between real-name status and communication capabilities. It fully covers the business scenarios throughout the entire lifecycle of the vehicle SIM card. Standardized processing procedures exist for scenarios such as vehicle real-name registration, ownership transfer and binding, physical card replacement, batch delivery, batch retirement, and historical tracing, forming a complete real-name management system. Batch operations are submitted in parallel after being grouped by ownership, significantly improving the processing efficiency of batch delivery scenarios for large enterprise customers. Compared to manual operation one vehicle at a time, the real-name processing time for batch deliveries of hundreds of vehicles can be reduced to minutes. The ability to query the entire lifecycle change record at the VIN level enables operating companies to have unified traceability and compliance audit capabilities for vehicle communication assets, meeting regulatory compliance requirements.

[0086] This invention also provides a method for real-name authentication of vehicle SIM cards, such as... Figure 2 As shown, the vehicle SIM card real-name authentication method includes: S210 receives a real-name authentication request from the vehicle SIM card and obtains the vehicle's VIN code and vehicle information from the real-name authentication request. The vehicle information includes the vehicle owner's identity information or the identity information of the company to which the vehicle belongs.

[0087] S220 determines the target OEM corresponding to the vehicle SIM card based on the binding relationship between the vehicle's VIN code and the vehicle's SIM card ICCID.

[0088] S230, based on the target OEM's identifier, extracts the configuration rules corresponding to the identifier from the interface adaptation library, and encapsulates the vehicle owner's identity information, vehicle's VIN code, and ICCID into an authentication request data packet according to the data format and field definitions specified by the target OEM on the real-name authentication platform. The authentication request data packet is then forwarded to the target OEM's real-name authentication platform through the network routing module.

[0089] S240: Obtain the binding operation result returned by the real-name authentication platform, and trigger the channel mode of the corresponding vehicle SIM card based on the binding operation result.

[0090] S250 stores the vehicle-card binding relationship and full lifecycle change records formed after each real-name registration operation.

[0091] The vehicle SIM card real-name authentication method according to embodiments of the present invention achieves precise positioning of the target platform by automatically identifying the OEM of the SIM card using the VIN code as the key, eliminating the manual judgment step; it achieves complete shielding of interface differences between multiple platforms by automatically encapsulating authentication requests according to the protocols and formats specified by the target platform through a pre-built multi-OEM interface adaptation library; it achieves strict linkage between real-name status and communication capability by automatically triggering the SIM card to switch between dual-channel, single-channel, and deactivated states based on the binding result; and it achieves traceable management of data throughout the entire lifecycle by persistently recording the vehicle-SIM card binding relationship and change history. This method realizes fully automated and unified management of vehicle SIM card real-name authentication in a multi-OEM environment.

[0092] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods of the various embodiments of this application.

[0093] According to one aspect of the present invention, an electronic device is provided.

[0094] Figure 3 This is a schematic diagram of the structure of an electronic device according to an embodiment of the present invention. Figure 3 As shown, an electronic device may include one or more ( Figure 3 Only one is shown in the image. A processor 102 (which may include, but is not limited to, a microprocessor unit (MPU) or a programmable logic device (PLD)) and a memory 104 for storing data are also shown. In one exemplary embodiment, the electronic device may further include a transmission device 106 for communication functions and an input / output device 108. Those skilled in the art will understand that... Figure 3 The structure shown is for illustrative purposes only and does not limit the structure of the terminal device described above. For example, the terminal device may also include components that are more... Figure 3 The more or fewer components shown, or having the same Figure 3 Equivalent functions or ratios shown Figure 3 The functions shown have more different configurations.

[0095] The memory 104 can be used to store computer programs, such as application software programs and modules, like the computer program corresponding to the vehicle SIM card real-name authentication method in this embodiment of the invention. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, thereby implementing the above-described method. The memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories can be connected to the terminal device via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0096] The transmission device 106 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by the communication provider of the switching device. In one example, the transmission device 106 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 106 may be a Radio Frequency (RF) module used for wireless communication with the Internet.

[0097] This invention proposes a non-transitory computer-readable storage medium storing computer instructions, which are used to cause the computer to execute a vehicle SIM card real-name authentication method.

[0098] The applicant of this invention has provided a detailed description of the embodiments of the invention in conjunction with the accompanying drawings. However, those skilled in the art should understand that the above embodiments are merely preferred embodiments of the invention. The detailed description is only intended to help readers better understand the spirit of the invention and is not intended to limit the scope of protection of the invention. On the contrary, any improvements or modifications made based on the inventive spirit of the invention should fall within the scope of protection of the invention.

[0099] Furthermore, the functional units in the various embodiments of the present invention can be integrated into a processing module, or each unit can exist physically separately, or two or more units can be integrated into a module. The integrated module can be implemented in hardware or as a software functional module. If the integrated module is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium.

[0100] The storage medium mentioned above can be a read-only memory, a disk, or an optical disk, etc. Although embodiments of the present invention have been shown and described above, it is to be understood that the above embodiments are exemplary and should not be construed as limiting the present invention. Those skilled in the art can make changes, modifications, substitutions, and variations to the above embodiments within the scope of the present invention.

[0101] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the embodiments of the present invention, and are not intended to limit them. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention. Any changes or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in the present invention should be included within the protection scope of the present invention.

Claims

1. A vehicle SIM card real-name authentication system, characterized in that, include: The receiving module is used to receive the real-name authentication request of the vehicle SIM card and obtain the vehicle's VIN code and vehicle information from the real-name authentication request, wherein the vehicle information includes the vehicle owner's identity information or the identity information of the company to which the vehicle belongs. The query module is used to determine the target OEM corresponding to the vehicle SIM card based on the binding relationship between the vehicle's VIN code and the vehicle's SIM card ICCID. The encapsulation module is used to extract the configuration rules corresponding to the identifier from the interface adaptation library based on the identifier of the target OEM, and encapsulate the vehicle owner identity information, the vehicle's VIN code and the ICCID into an authentication request data packet according to the data format and field definition specified by the target OEM on the real-name authentication platform, and forward the authentication request data packet to the target OEM's real-name authentication platform through the network routing module. The status management module is used to obtain the binding operation result returned by the real-name authentication platform, and trigger the channel mode corresponding to the vehicle SIM card based on the binding operation result; The storage module is used to store the vehicle-card binding relationship and the full lifecycle change records formed after each real-name registration operation.

2. The vehicle SIM card real-name authentication system according to claim 1, characterized in that, The query module is also used to query the binding relationship between the vehicle's VIN code and the ICCID from the operator's unified operation and management platform using the vehicle's VIN code as the query key; In the event that the query for the binding relationship fails, the binding relationship is queried again based on a preset interval and a number of retries; If the binding relationship is not found, an error message will be returned and the process will be terminated.

3. The vehicle SIM card real-name authentication system of claim 1, wherein, The system also includes a binding module for performing binding operations based on the real-name authentication platform; The binding operation based on the real-name authentication platform includes: If the real-name authentication platform verifies that the vehicle owner's identity information is valid and the vehicle SIM card is in normal status, it will bind the vehicle owner's identity information, the vehicle's VIN code, and the vehicle SIM card. The determination of the binding operation result returned by the real-name authentication platform includes: The business status code in the binding operation receipt is parsed. When the business status code is a success code pre-set by the target OEM on the real-name authentication platform, the binding operation is initially determined to be successful. When the business status code is a failure code, or no valid receipt is received, the binding operation is determined to be failed, and the subsequent channel switching process is terminated. If the binding operation is initially determined to be successful, the failure reason field carried in the binding operation receipt is further read. If the failure reason field is not empty and the content points to the binding not taking effect, the initial determination is overturned and the binding operation is finally determined to be a failure.

4. The vehicle SIM card real-name authentication system according to claim 1, characterized in that, Based on the binding operation result, the corresponding channel mode of the vehicle SIM card is triggered, including: If the binding operation is successful, the system automatically sends a command to the network side to switch the vehicle SIM card from the current single-channel mode to the dual-channel mode and activate the preset public network reserved traffic. When the preset public network test traffic is used up, the system automatically switches back to the single-channel mode. If the binding operation fails, the cause of failure is determined and an alarm message is issued, while the vehicle SIM card maintains its original channel mode.

5. The vehicle SIM card real-name authentication system according to claim 4, characterized in that, Based on the current status of the vehicle's SIM card, determine the channel mode corresponding to the vehicle's SIM card, including: When the current state is the initial state, the channel mode is the dual-channel mode, and the dual-channel mode is configured with the preset public network reserved traffic; When the current state is disabled, the channel mode is a dual-channel both-off mode; When the current state is activated, the channel mode of the vehicle's SIM card is determined based on the matching of the configuration identifier and / or configuration file returned by the CMP card management platform with the corresponding preset combination configuration.

6. The vehicle SIM card real-name authentication system of claim 1, wherein, The system also includes a transfer processing module for performing vehicle transfer real-name processing operations; The process of processing vehicle ownership transfer under the real name includes: Receive a transfer request, and extract the vehicle's VIN code, the first owner's identity information, and the second owner's identity information based on the transfer request; The query module determines the OEM corresponding to the SIM card based on the binding relationship between the vehicle's VIN code and ICCID. The network routing module submits an unbinding request to the real-name authentication platform corresponding to the OEM. If the unbinding is successful, the status management module triggers the SIM card to enter a deactivated state. The second vehicle owner's identity information submits a binding application request to the real-name authentication platform corresponding to the OEM through the network routing module. If the binding is successful, the status management module triggers the SIM card to restore dual-channel mode, and the storage module updates the vehicle owner's identifier and retains the transfer change record.

7. The vehicle SIM card real-name authentication system according to claim 1, characterized in that, The system also includes a card replacement processing module, which is used to perform real-name card replacement processing for vehicles; The process of processing vehicle card replacements under real-name registration includes: Receive a card replacement request, and extract the vehicle's VIN code, first SIM card ICCID, and second SIM card ICCID based on the card replacement request; The query module determines the OEM corresponding to the first SIM card based on the binding relationship between the vehicle's VIN code and the first SIM card's ICCID. The network routing module submits an unbinding request to the real-name authentication platform corresponding to the OEM. If the unbinding is successful, the status management module triggers the first SIM card to enter a deactivated state. The query module determines the OEM corresponding to the second SIM card based on the binding relationship between the vehicle's VIN code and the second SIM card's ICCID. The network routing module submits a binding application request to the real-name authentication platform corresponding to the OEM. If the binding is successful, the status management module triggers the SIM card to switch to dual-channel mode. At the same time, the storage module updates the vehicle card binding record and establishes the association between the vehicle's VIN code and the second SIM card's ICCID.

8. The vehicle SIM card real-name authentication system according to claim 1, characterized in that, It also includes a record query module, which uses the vehicle's VIN code as the query dimension to call the query interface of the corresponding target OEM on the real-name authentication platform to obtain the historical real-name change records of the vehicle's SIM card; The historical real-name change record includes: the operation time of each binding and unbinding operation, the operator's identification, the vehicle owner's identity information before and after the change, the vehicle's SIM card ICCID, and the type of real-name status change.

9. The vehicle SIM card real-name authentication system according to claim 1, characterized in that, The authentication request data includes the vehicle owner's name, vehicle owner's document type, vehicle owner's document number, the vehicle's VIN code, and the vehicle's SIM card ICCID. The system requires real-name authentication of the vehicle's owner's identity information, including the company name, unified social credit code, and legal representative information.

10. A method for real-name authentication of a vehicle SIM card, characterized in that, include: Receive a real-name authentication request from the vehicle SIM card, and obtain the vehicle's VIN code and vehicle information from the real-name authentication request, wherein the vehicle information includes the vehicle owner's identity information or the identity information of the company to which the vehicle belongs; Based on the binding relationship between the vehicle's VIN code and the vehicle's SIM card ICCID, the target OEM corresponding to the vehicle's SIM card is determined; Based on the identifier of the target OEM, the configuration rules corresponding to the identifier are extracted from the interface adaptation library. In accordance with the data format and field definition specified by the target OEM on the real-name authentication platform, the vehicle owner's identity information, the vehicle's VIN code, and the ICCID are encapsulated into an authentication request data packet. The authentication request data packet is then forwarded to the target OEM's real-name authentication platform through the network routing module. Obtain the binding operation result returned by the real-name authentication platform, and trigger the corresponding channel mode of the vehicle SIM card based on the binding operation result; Stores the vehicle-card binding relationship and full lifecycle change records formed after each real-name registration operation.

Images