Equipment identification generation method and vehicle
By desensitizing the vehicle identification code and the unique identifier of the on-board electronic control unit to generate an irreversible device identifier, the problem of the vehicle identification code leaking out of the control boundary of the car manufacturer is solved, and the location service can be opened normally while protecting privacy.
Patent Information
- Application Number
- CN202611532637.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-09-30
- Publication Date
- 2026-11-17
AI Technical Summary
In existing technologies, vehicle identification codes are directly used as identifiers for activating location services, which leads to the leakage of vehicle identification codes out of the control boundaries of car manufacturers. This increases the possibility that the identification codes can be obtained by external systems, makes it difficult to establish a mandatory association with the hardware of the vehicle's electronic control unit, and poses a risk of misuse.
By obtaining the vehicle identification number and the unique identifier of the on-board electronic control unit, and after desensitizing them, an irreversible device identifier is generated based on the desensitized identifier and the unique identifier. This identifier is used to activate the target service, ensuring the uniqueness and irreversibility of the device identifier on the location service platform side.
This reduces the risk of sensitive information leakage caused by directly sharing vehicle identification codes externally, ensures the normal activation of target services, and protects privacy because the device identifier is difficult to restore to the vehicle identification code.
Smart Images

Figure CN123123313A_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to the field of data processing technology, specifically to a method for generating device identifiers and a vehicle. Background Technology
[0002] After the sale of intelligent connected vehicles, users typically enjoy services related to vehicle location. Automakers need to provide a unique identifier for the vehicle to the location service platform in order to establish a service instance and activate the location service. With the increasing demands for refined vehicle service management, how to ensure the normal activation of location services while simultaneously reducing the possibility of the vehicle identification number being directly obtained by external systems has become a pressing technical problem. Summary of the Invention
[0003] In view of this, the present disclosure aims to provide a device identifier generation method and vehicle to solve the problem in the prior art where the direct use of vehicle identification code as the target service activation identifier leads to the leakage of vehicle identification code out of the vehicle manufacturer's control boundary.
[0004] In a first aspect, one embodiment of this disclosure provides a device identifier generation method, including: obtaining the vehicle identification code of a target vehicle and the unique identifier of the vehicle's on-board electronic control unit; desensitizing the vehicle identification code to obtain a desensitized vehicle identifier; and generating a device identifier based on the desensitized vehicle identifier and the unique identifier according to a preset irreversible identifier generation rule, wherein the device identifier is used to activate the target service for the vehicle.
[0005] In conjunction with the first aspect, in certain implementations of the first aspect, obtaining the vehicle identification number (VIN) of the target vehicle and the unique identifier of the on-board electronic control unit (OECU) of the target vehicle includes: in response to a target service activation request, obtaining the VIN of the target vehicle from the target service activation request; querying the sales status of the target vehicle based on the VIN; and if the sales status is "sold out", obtaining the unique identifier of the OECU of the target vehicle.
[0006] In conjunction with the first aspect, in some implementations of the first aspect, the above-mentioned device identifier generation method further includes: sending a prompt message indicating that the target vehicle cannot activate the target service when the sales status is "not actually sold".
[0007] In conjunction with the first aspect, in some implementations of the first aspect, obtaining the unique identifier of the on-board electronic control unit of the target vehicle includes: querying the production system database based on the vehicle identification code to obtain the unique identifier of the on-board electronic control unit bound to the vehicle identification code; wherein, the production system database stores a one-to-one binding relationship between the vehicle identification code and the unique identifier of the on-board electronic control unit, and the binding relationship is stored in the production system database during the production stage of the target vehicle.
[0008] In conjunction with the first aspect, in some implementations of the first aspect, the establishment of the binding relationship includes: collecting the vehicle identification code of the target vehicle and the unique identifier of the on-board electronic control unit of the target vehicle; querying the production system database based on the vehicle identification code; when there is no binding record corresponding to the vehicle identification code in the production system database, verifying the format integrity of the vehicle identification code, the non-empty state of the unique identifier, and that the unique identifier is not duplicated in the production system database, and writing the binding relationship between the vehicle identification code and the unique identifier after the verification is passed.
[0009] In conjunction with the first aspect, in some implementations of the first aspect, a device identifier is generated based on the desensitized vehicle identifier and the unique identifier according to a preset irreversible identifier generation rule, including: combining the desensitized vehicle identifier and the unique identifier to obtain a combined string; and performing irreversible mapping processing on the combined string to obtain the device identifier.
[0010] In conjunction with the first aspect, in some implementations of the first aspect, irreversible mapping processing is performed on the combined string to obtain the device identifier, including: hashing the combined string to obtain the identifier string; extracting the character at the first target position from the identifier string according to the preset character position extraction rules, and combining the extracted characters into the device identifier.
[0011] In conjunction with the first aspect, in some implementations of the first aspect, the vehicle identification code is desensitized to obtain a desensitized vehicle identifier, including: performing character order transformation processing on the string corresponding to the vehicle identification code to obtain a transformed string; removing the characters at the second target position from the transformed string to obtain the desensitized vehicle identifier, wherein the characters at the second target position contain sensitive content, including enterprise information.
[0012] In conjunction with the first aspect, in some implementations of the first aspect, the target service is a location service, and the above-mentioned device identifier generation method further includes: sending location service activation data including the device identifier to the location service platform through an encrypted communication interface; wherein, the location service activation data does not include the vehicle identification number and unique identifier.
[0013] Secondly, one embodiment of this disclosure provides a device identifier generation apparatus, comprising: an acquisition module for acquiring the vehicle identification code of a target vehicle and the unique identifier of the vehicle's on-board electronic control unit; a obtaining module for desensitizing the vehicle identification code to obtain a desensitized vehicle identifier; and a generation module for generating a device identifier based on the desensitized vehicle identifier and the unique identifier, according to a preset irreversible identifier generation rule, wherein the device identifier is used to activate the target service for the target vehicle.
[0014] Thirdly, one embodiment of this disclosure provides a computer-readable storage medium storing a computer program for performing the device identifier generation method described in the first aspect.
[0015] Fourthly, one embodiment of this disclosure provides a vehicle, the vehicle including: a processor; a memory for storing processor-executable instructions; the processor being configured to execute the device identifier generation method described in the first aspect.
[0016] Fifthly, one embodiment of this disclosure provides a computer program product including instructions that, when executed on a vehicle, cause the vehicle to implement the device identifier generation method described in the first aspect.
[0017] In the embodiments of this disclosure, after obtaining the vehicle identification code of the target vehicle and the unique identifier of the vehicle's on-board electronic control unit, the vehicle identification code is first desensitized to obtain a desensitized vehicle identifier. Then, based on the desensitized vehicle identifier and the unique identifier, a device identifier is generated according to a preset irreversible identifier generation rule. This makes it difficult for the device identifier used to activate the target service to be restored to the vehicle identification code, reducing the risk of sensitive information leakage caused by directly sharing the vehicle identification code. At the same time, the device identifier is used as the basis for activating the target service, ensuring the normal activation of the target service while protecting privacy. Attached Figure Description
[0018] The above and other objects, features, and advantages of this disclosure will become more apparent from the more detailed description of the embodiments thereof in conjunction with the accompanying drawings. The drawings are provided to further illustrate the embodiments of this disclosure and form part of the specification. They are used together with the embodiments of this disclosure to explain the disclosure and do not constitute a limitation thereof. In the drawings, the same reference numerals generally represent the same components or steps.
[0019] Figure 1 The diagram shown is a flowchart illustrating a device identifier generation method provided in an embodiment of this disclosure.
[0020] Figure 2 The diagram shown is a schematic representation of the process for establishing a binding relationship according to an embodiment of this disclosure.
[0021] Figure 3 The diagram shown is a flowchart illustrating a device identifier generation method according to another embodiment of this disclosure.
[0022] Figure 4 The diagram shown is a structural schematic of a device identifier generation apparatus provided in an embodiment of this disclosure.
[0023] Figure 5 The diagram shown is a structural schematic of a vehicle provided in an embodiment of this disclosure. Detailed Implementation
[0024] The technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this disclosure, and not all embodiments. Based on the embodiments of this disclosure, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this disclosure.
[0025] Furthermore, to better illustrate this disclosure, numerous specific details are set forth in the following detailed description. Those skilled in the art will understand that this disclosure can be practiced without certain specific details. In some instances, methods and means well-known to those skilled in the art have not been described in detail in order to highlight the main points of this disclosure.
[0026] It should be noted that similar labels and letters in the following figures indicate similar items. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures.
[0027] Furthermore, the terms “first,” “second,” “third,” and “fourth” are used only for distinguishing descriptions and should not be interpreted as indicating or implying relative importance.
[0028] In the field of vehicle location service activation technology, to provide a unique identifier for a vehicle to the location service provider, the relevant technologies typically send the vehicle's 17-digit Vehicle Identification Number (VIN) in plaintext to the location service platform. Specifically, after a vehicle is sold, the dealer submits the VIN for which location services need to be activated. The automaker's location service management platform receives the VIN and forwards it to the location service platform. The location service platform uses this VIN as the unique identifier for establishing a service instance on its platform.
[0029] However, this solution performs poorly when applied to scenarios requiring restrictions on the leakage of vehicle identification numbers (VINs) from the vehicle manufacturer's control boundaries and prevention of service activation identifier misuse. This is primarily because, to meet the location service platform's requirement for a unique vehicle identifier, the solution directly uses the inherent design of the VIN, inevitably causing the VIN to leak in plaintext beyond the vehicle manufacturer's control boundaries. Furthermore, the service activation identifier is only associated with the vehicle itself, failing to establish a direct correspondence with specific onboard electronic control unit (ECU) hardware. Specifically, once the VIN is directly provided to the location service platform, it leaks out of the vehicle manufacturer's control, allowing external systems to obtain the un-anonymized VIN. Using the VIN directly as the activation identifier generally only corresponds to the vehicle itself, making it difficult to establish a mandatory association with specific ECU hardware. This means that after the VIN is leaked, it may be misused by other devices to activate the service. These factors result in a high probability that the VIN can be directly obtained by external systems when activating vehicle location services, leading to a weak binding relationship between the service activation identifier and the ECU hardware.
[0030] To address the aforementioned technical issues, this disclosure provides a device identifier generation method and a vehicle. The method includes obtaining the vehicle identification code (VIC) of a target vehicle and the unique identifier of the vehicle's on-board electronic control unit (OECU); desensitizing the VIC to obtain a desensitized vehicle identifier; and generating a device identifier based on the desensitized vehicle identifier and the unique identifier according to a preset irreversible identifier generation rule. The device identifier is used to activate the target service on the target vehicle. By first desensitizing the VIC to obtain the desensitized vehicle identifier after obtaining the target vehicle's VIC and the unique identifier of the OECU, and then generating the device identifier based on the desensitized vehicle identifier and the unique identifier according to the preset irreversible identifier generation rule, the device identifier ultimately used for activating the target service is difficult to revert to the VIC, reducing the risk of sensitive information leakage caused by directly sharing the VIC. Simultaneously, using the device identifier as the basis for activating the target service ensures the normal activation of the target service while protecting privacy.
[0031] The following is combined Figures 1 to 3 The device identifier generation method provided in this disclosure is described in detail.
[0032] Figure 1 The diagram shown is a flowchart illustrating a device identifier generation method according to an embodiment of this disclosure. This method can be applied to vehicles. Figure 1 As shown in the embodiments of this disclosure, the device identifier generation method may include the following steps.
[0033] Step S110: Obtain the vehicle identification number (VIN) of the target vehicle and the unique identifier of the on-board electronic control unit (OECU) of the target vehicle.
[0034] For example, the target vehicle can be an intelligent connected vehicle, a new energy vehicle, a passenger car, or a commercial vehicle.
[0035] A Vehicle Identification Number (VIN) is a vehicle identification number that uniquely identifies a vehicle. It consists of a standard sequence of characters and can be used to index a vehicle in a vehicle management or service system. For example, a VIN can be a 17-character Vehicle Identification Number. Alternatively, a VIN can be a Vehicle Identification Number (VIN) or other unique vehicle codes assigned during vehicle production or registration.
[0036] An onboard electronic control unit (ECU) can represent an ECU capable of participating in target service identity binding and possessing a readable, unique identifier. An ECU may be, for example, an onboard telematics box (TBOX). In other embodiments, the ECU may also be other ECUs on the vehicle that possess a unique identifier.
[0037] A unique identifier is a logical identifier written or embedded within the vehicle electronic control unit (ECU) during manufacturing, used to uniquely identify the ECU. For example, a unique identifier can be the ECU's unique serial number (UIN), which can be obtained by reading the ECU's internal information through production line tools or software interfaces. It's important to note that this unique identifier does not represent a QR code, barcode, or nameplate label affixed to the hardware surface. The unique identifier is embedded and cannot be altered during manufacturing, thus ensuring the final device identification is resistant to counterfeiting.
[0038] Step S120: De-identify the vehicle identification code to obtain a de-identified vehicle identifier.
[0039] Desensitization processing is used to desensitize vehicle identification numbers (VINs). For example, it can change the original character structure of the VIN or remove some character information so that the desensitized vehicle identification number no longer directly exposes the original VIN and therefore cannot be directly restored to the original VIN.
[0040] Step S130: Based on the desensitized vehicle identifier and unique identifier, generate the device identifier according to the preset irreversible identifier generation rules.
[0041] For example, the device identifier is used to enable vehicle location target services for the target vehicle. For instance, the activation of location services.
[0042] The default irreversible identifier generation rule is a one-way mapping rule from desensitized vehicle identifiers and unique identifiers to device identifiers, making it impossible to recover the desensitized vehicle identifier or unique identifier from the device identifier. In some embodiments, if the target service is a location service, after generating the device identifier, the location service management platform sends the device identifier to the location service platform (such as the location service provider). The location service platform activates vehicle location services based on this device identifier, without using the vehicle identification number (VIN). That is, both the VIN and the unique identifier of the on-board electronic control unit are processed within the vehicle manufacturer's control boundaries.
[0043] For example, the automaker's control boundary includes the production system, production system database, sales system, location service management platform, and internal communication network connecting these systems, all managed by the automaker. Vehicle identification numbers and unique identifiers can be transmitted and stored between these internal systems for establishing binding relationships, querying sales status, and generating irreversible device identifiers, but they will not be sent to the location service platform via encrypted communication interfaces or other means.
[0044] After obtaining the vehicle identification number (VIN) and the unique identifier of the vehicle's on-board electronic control unit (OECU), the VIN is first anonymized to obtain an anonymized vehicle identifier. Then, based on the anonymized vehicle identifier and the unique identifier, a device identifier is generated according to a preset irreversible identifier generation rule. This makes it difficult for the device identifier used to activate the target service to be restored to the VIN, reducing the risk of sensitive information leakage caused by directly sharing the VIN. At the same time, the device identifier is used as the basis for activating the target service, ensuring the normal activation of the target service while protecting privacy.
[0045] In some embodiments, obtaining the vehicle identification number (VIN) of the target vehicle and the unique identifier of the on-board electronic control unit (OECU) of the target vehicle includes: in response to a target service activation request, obtaining the VIN of the target vehicle from the target service activation request; querying the sales status of the target vehicle based on the VIN; and if the sales status is "sold" or "actually sold", obtaining the unique identifier of the OECU of the target vehicle.
[0046] In some embodiments, obtaining the vehicle identification number (VIN) of the target vehicle is contingent upon receiving a vehicle location service activation request. This VIN request may be submitted by the dealer after the vehicle sale, and it must include at least the VIN. In other embodiments, the VIN request may be automatically triggered by the automaker's location service management platform or initiated by the user via a mobile device or in-vehicle system. Upon receiving a target service activation request, the VIN of the target vehicle can be obtained from the request.
[0047] Sales status represents the state of a vehicle during the sales process, used to determine whether the vehicle has been actually sold, i.e., whether it has entered the stage where it can be legally activated for service. Sales status can be, for example, sold, not sold, in inventory, or under testing.
[0048] In some embodiments, the sales status of a target vehicle can be queried from the automaker's sales system based on the vehicle identification number (VIN). The sales system could be, for example, the automaker's sales management system, used to record and manage vehicle sales status information. Obtaining sales status information through an interface with the automaker's sales system ensures the authority and reliability of the information source, avoiding misjudgments caused by inaccurate information sources.
[0049] The sales status query request includes a vehicle identification number (VIN) to locate the corresponding vehicle's sales record in the sales system. Using the VIN as the query key, the system can accurately pinpoint the target vehicle's sales status record, ensuring a one-to-one correspondence between the query results and the vehicle for which the service is being requested. This avoids misjudgments due to ambiguous query conditions. The sales status returned by the sales system can include values such as "sold" and "not sold," allowing the location service management platform to make deterministic process branch decisions based on this status value, thus avoiding decision ambiguity caused by ambiguous statuses.
[0050] In some embodiments, when the sales status is "sold," it indicates that the ownership of the vehicle has been transferred to the user, and the vehicle manufacturer's sales system has marked the vehicle as "sold." By determining the sales status, the generation of device identifiers is strictly limited to vehicles that have been sold, preventing unsold vehicles such as inventory vehicles and test vehicles from occupying location service resources, effectively saving operating costs and avoiding asset management chaos.
[0051] By using the target service activation request as a trigger condition, the vehicle identification number (VIN) is obtained from the request, and the sales status of the target vehicle is queried based on the VIN. The unique identifier of the on-board electronic control unit is only obtained when the sales status is "sold". This limits the activation of the target service to only target vehicles that have been actually sold, avoiding the incorrect activation of the target service for unsold vehicles such as inventory vehicles and test vehicles. It also reduces the ineffective use of target service resources, improves the standardization and controllability of the target service activation process, and reduces unnecessary query and data processing overhead.
[0052] In other embodiments, the device identifier generation method described above further includes: sending a prompt message indicating that the target vehicle cannot activate the target service when the sales status is "not actually sold".
[0053] For example, if the sales status is "not sold," a message indicating that the target vehicle cannot activate the target service can be sent, terminating the device identifier generation process and prohibiting the sending of the device identifier used to activate the vehicle location service to the location service platform. For instance, a message stating "Vehicle not sold, cannot be activated" can be returned. This instantly intercepts requests from vehicles that have not yet been sold, avoiding unnecessary subsequent database queries and calculations, ensuring that the vehicle corresponding to the activation request has been sold while reducing system resource consumption.
[0054] When the sales status is "not sold," a notification message is sent indicating that the target vehicle cannot activate the target service. This allows activation requests for vehicles that have not been sold to be clearly identified and promptly reported. It facilitates the timely detection and location of anomalies during the target service activation process, preventing the continued execution of subsequent processing in cases of data inconsistency or illegal activation. This improves the security and reliability of the target service activation process.
[0055] In some embodiments, obtaining the unique identifier of the on-board electronic control unit of the target vehicle includes: querying the production system database based on the vehicle identification code to obtain the unique identifier of the on-board electronic control unit bound to the vehicle identification code.
[0056] For example, the production system database stores a one-to-one binding relationship between vehicle identification codes and unique identifiers of on-board electronic control units. This binding relationship is stored in the production system database during the production phase of the target vehicle.
[0057] The production system database, for example, could be the database used by the production management system of a vehicle assembly line, to persistently store the binding information between vehicle identification numbers and unique identifiers. Storing the binding relationship in the production system database ensures that the binding information is established and persisted during the vehicle production stage, providing a reliable source of basic data for generating device identifiers when the target service is activated, and avoiding inconsistencies that may arise from dynamic queries or temporary establishment of binding relationships at runtime.
[0058] The binding relationship is the association between a vehicle identification number (VIN) and a unique identifier pre-established during the production phase of the target vehicle. This association is used to determine the corresponding unique identifier based on the VIN. The unique identifier uniquely identifies the corresponding on-board electronic control unit (OECU) hardware. For example, the binding relationship between the VIN and the unique identifier can be a one-to-one relationship. Associating the device identifier with the unique identifier of the OECU ensures that the device identifier not only represents the vehicle's identity but is also bound to specific hardware within the vehicle. If this hardware is replaced, the generated device identifier will change. Unauthorized devices, lacking the correct unique identifier corresponding to the VIN, cannot generate the same device identifier and thus cannot impersonate the target service.
[0059] A one-to-one binding relationship means that a vehicle identification number (VIN) can only be bound to one unique identifier, and a unique identifier can only be bound to one VIN. This one-to-one binding relationship ensures a strict correspondence between vehicle identity and hardware identity, preventing the same VIN from being bound to multiple unique identifiers (leading to multiple device identifiers pointing to the same vehicle) or the same unique identifier from being bound to multiple VINs (leading to hardware identity confusion), thereby guaranteeing the uniqueness of the device identifier on the location service platform side.
[0060] By querying the production system database using the vehicle identification code, and utilizing the one-to-one binding relationship between the vehicle identification code and the unique identifier pre-stored during the production stage, the unique identifier is obtained. This ensures that the correspondence between the obtained unique identifier and the target vehicle is accurate, avoiding equipment identifier errors caused by mismatch between the unique identifier and the vehicle identification code when generating equipment identifiers in the later stage, and guaranteeing the accuracy and uniqueness of equipment identifier generation.
[0061] The process of establishing this binding relationship will be explained further below.
[0062] In some embodiments, establishing a binding relationship includes: collecting the vehicle identification code of the target vehicle and the unique identifier of the on-board electronic control unit of the target vehicle; querying the production system database based on the vehicle identification code; when there is no binding record corresponding to the vehicle identification code in the production system database, verifying the format integrity of the vehicle identification code, the non-empty state of the unique identifier, and the unique identifier not being duplicated in the production system database, and writing the binding relationship between the vehicle identification code and the unique identifier after the verification is passed.
[0063] For example, the vehicle identification number (VIN) marked on the vehicle body can be scanned at a fixed workstation on the vehicle assembly line, and the unique identifier of the on-board electronic control unit to be bound can be read using production line tools. In other embodiments, the VIN can also be obtained manually. Collecting the VIN and unique identifier during the production stage ensures that the binding relationship is established before the vehicle leaves the factory, allowing the device identification generation process to directly rely on the existing binding relationship without having to temporarily establish the binding relationship when the target service is activated.
[0064] After data collection, the production system database is queried based on the vehicle identification number (VIN) to confirm whether the VIN is currently bound to any unique identifier. This query operation, as a pre-processing check in the binding process, avoids duplicate binding operations on already bound VINs and is a key control step to ensure a one-to-one binding relationship.
[0065] When the binding relationship corresponding to a vehicle identification number (VIN) does not exist in the production system database, the data to be written needs to be validated. The validation includes three aspects: First, verifying the format integrity of the VIN. This includes checking the character length (e.g., whether it is 17 characters) and character validity. Format integrity validation ensures that the VIN written to the production system database conforms to standard specifications, preventing errors in subsequent device identifier generation due to incorrectly formatted VINs. Second, verifying the non-empty state of the unique identifier. This ensures that the unique identifier field is not empty, guaranteeing that each binding record contains a valid unique identifier, preventing errors in device identifier generation due to missing unique identifiers. Third, verifying that the unique identifier is not duplicated in the production system database. This ensures that the same unique identifier is not bound to multiple VINs, guaranteeing a one-to-one binding relationship and preventing the same electronic control unit from being incorrectly bound to multiple vehicles. After all three validations pass, the binding relationship between the VIN and the unique identifier is written to the production system database.
[0066] In some embodiments, the binding timestamp can also be written together with the vehicle identification number and unique identifier binding relationship into the production system database, wherein the binding timestamp is used to record the time when the binding relationship is established. The recording of the binding timestamp provides the binding relationship with time-dimensional traceability, which facilitates the auditing and investigation of binding operations, and can also be used to determine the timeliness of the binding relationship.
[0067] It is understood that the order of the steps described above—verifying the format integrity of the vehicle identification number (VIN), verifying the unique identifier's non-emptiness, verifying the unique identifier's non-duplicate status in the production system database, and querying the production system database based on the VIN—is not limited to a fixed method. In one optional implementation, the format integrity of the VIN, the non-emptiness of the unique identifier, and the absence of duplicate unique identifiers in the production system database can be verified first. After these verifications pass, the production system database can be queried based on the VIN. In another optional implementation, the production system database can be queried first based on the VIN. If the query result indicates that no binding record corresponding to the VIN exists in the production system database, then the above verification steps are performed. No specific limitations are imposed here.
[0068] In some embodiments, if a binding relationship corresponding to the vehicle identification code already exists in the production system database, the write operation between the vehicle identification code and the unique identifier will not be performed. Binding to a vehicle identification code that already has a binding record is refused again. This enforces the constraint that a vehicle identification code can only be bound to one unique identifier at the database operation level, preventing the binding relationship from being overwritten or multiple records from being generated due to repeated operations on the production line or system anomalies.
[0069] Through the above-mentioned process of querying, verifying, and rewriting, supplemented by duplicate judgment and validity verification, it is possible to effectively prevent duplicate binding and invalid binding data from being written into the production system database, ensuring that the one-to-one binding relationship between vehicle identification code and unique identifier is complete, valid and traceable, providing basic data guarantee for the reliable generation of device identifiers, and avoiding device identifier generation failure or the generation of incorrect identifiers due to abnormal binding data.
[0070] Figure 2 The diagram illustrates a process for establishing a binding relationship according to an embodiment of this disclosure. Figure 2 As shown, the establishment of the binding relationship provided in this embodiment may include the following steps.
[0071] Step S201: Collect the vehicle identification code of the target vehicle and the unique identifier of the on-board electronic control unit of the target vehicle.
[0072] Step S202: Verify the integrity of the vehicle identification number format.
[0073] Step S203: Check if the unique identifier is non-empty and does not have duplicates. If yes, proceed to step S204; otherwise, proceed to step S207.
[0074] Step S204: Query the production system database based on the vehicle identification code.
[0075] Step S205: Does the vehicle identification code have a corresponding binding relationship? If not, proceed to step S206; if yes, proceed to step S208.
[0076] Step S206: Write the binding relationship between the vehicle identification code and the unique identifier, as well as the binding timestamp, into the production system database and persist the data.
[0077] Step S207: Reject binding and prompt verification failure.
[0078] Step S208: Reject rebinding to ensure a one-to-one binding relationship between the vehicle identification number and the unique identifier.
[0079] The following section further explains the desensitization process for vehicle identification numbers.
[0080] In some embodiments, the vehicle identification code is preprocessed to obtain a desensitized vehicle identifier, including: performing character order transformation processing on the string corresponding to the vehicle identification code to obtain a transformed string; and removing the character at the second target position from the transformed string to obtain the desensitized vehicle identifier.
[0081] For example, the characters at the second target location contain sensitive content, including corporate information, which may represent characters in the vehicle identification number used to identify the company to which the target vehicle belongs.
[0082] In some embodiments, the desensitization process may include two steps: character order transformation and removal. By performing these two steps, the standard structure of the vehicle identification number (VIN) is broken and some sensitive fields are removed before irreversible mapping, creating pre-obfuscation and significantly increasing the difficulty of restoring the VIN using rainbow tables or enumeration.
[0083] Character order transformation processing can characterize the process of changing the original arrangement order of characters in a vehicle identification number (VIN) string. For example, it may include, but is not limited to, complete reversal, partial reversal, rearrangement according to a preset permutation table, random rearrangement, or combinations thereof. In some embodiments, character order transformation processing may, for example, be performing a complete reversal on the string corresponding to the VIN. For example, taking the 17-bit VIN "LSVAM45Z1G2012345" as an example, reversing it yields "5432102G1Z54MAVSL". In other embodiments, character order transformation processing may also employ other preset character rearrangement rules (such as exchanging character positions according to a preset permutation table). Character order transformation breaks the standard encoding structure of the VIN (such as fixed segments in the World Manufacturer Identifier, vehicle description section, and vehicle indication section), making the transformed string no longer conform to the standard format of the VIN. Even if intercepted, it is difficult to directly identify as a VIN, increasing the difficulty of external reverse engineering.
[0084] The removal process can characterize the removal of preset characters or character segments from the transformed string to shorten the string or strip sensitive content. After the character order transformation process, the characters at the second target position are removed from the transformed string to obtain the desensitized vehicle identifier. In some embodiments, the characters at the second target position contain sensitive content, including company information. For example, taking the reversed string as an example, the characters at the second target position (such as the last 5 characters) are removed, and the remaining characters are retained as the desensitized vehicle identifier. For example, after removing the last 5 characters "MAVSL" from the reversed string "5432102G1Z54MAVSL", the desensitized vehicle identifier "5432102G1Z54" is obtained. The purpose of removing sensitive content is to sever the direct association between the desensitized vehicle identifier and the car manufacturer, making it difficult for external parties to reverse-engineer the specific car manufacturer through the company information in the desensitized vehicle identifier, thus further enhancing the desensitization effect.
[0085] By desensitizing the vehicle identification code (VIN) and breaking its original structure, even if the desensitized vehicle identifier is intercepted, it is difficult to directly associate it with the VIN, thus introducing information protection in the pre-generation stage of the device identifier. By removing sensitive information, characters in the VIN that could reflect sensitive information such as the manufacturer's identity are effectively hidden, further reducing the risk of enterprise information leakage while retaining the identifier information that can be used for subsequent generation.
[0086] In some embodiments, a device identifier is generated based on a desensitized vehicle identifier and a unique identifier according to a preset irreversible identifier generation rule, including: combining the desensitized vehicle identifier and the unique identifier to obtain a combined string; and performing irreversible mapping processing on the combined string to obtain the device identifier.
[0087] In some embodiments, a preset irreversible identifier generation rule is used to ensure that the generated device identifier cannot be reverse-engineered to derive a vehicle identification number (VIN) or unique identifier. For example, the preset irreversible identifier generation rule may include combination and irreversible mapping processing. That is, the device identifier generation process includes two sub-steps: combination and irreversible mapping. Through the cascading processing of these two sub-steps, the device identifier integrates both the desensitized vehicle identifier and the unique identifier, and undergoes irreversible mapping processing, significantly enhancing the device identifier's resistance to reverse engineering and collisions.
[0088] In some embodiments, the combination of the desensitized vehicle identifier and the unique identifier can be achieved by concatenating the strings of the desensitized vehicle identifier and the unique identifier. For example, the concatenation method can be specified as desensitized vehicle identifier first, followed by the unique identifier; in other embodiments, it can also be agreed that the unique identifier comes first, followed by the desensitized vehicle identifier, as long as consistency is maintained within the system. Combining the desensitized vehicle identifier and the unique identifier into a single string allows irreversible mapping processing to simultaneously affect the information of both, ensuring that the final device identifier contains fused information of both vehicle identity and hardware identity, and that any change in input will cause the device identifier to change.
[0089] The combined string can represent a string obtained by combining the desensitized vehicle identifier and the unique identifier in a preset order. For example, the combined string can be a concatenation result with the desensitized vehicle identifier first and the unique identifier last. Alternatively, the combined string can also be a concatenation result with the unique identifier first and the desensitized vehicle identifier last, or a concatenation result obtained by connecting the desensitized vehicle identifier and the unique identifier with a separator.
[0090] Irreversible mapping can be achieved, for example, by applying a Secure Hash Algorithm (SHA) 256 to a concatenated string. By performing irreversible mapping on the concatenated string, the device identifier can be obtained.
[0091] By combining the desensitized vehicle identifier with the unique identifier to obtain a combined string, and then performing irreversible mapping processing on the combined string to obtain the device identifier, the device identifier integrates the desensitized vehicle identifier and the unique identifier. At the same time, due to the irreversible mapping processing, it cannot be restored. Thus, while ensuring that the device identifier is associated with the target vehicle, the risk of information leakage is further reduced.
[0092] Furthermore, in some embodiments, performing irreversible mapping processing on the combined string to obtain a device identifier may include: hashing the combined string to obtain an identifier string; extracting the character at the first target position from the identifier string according to a preset character position extraction rule, and combining the extracted characters into a device identifier.
[0093] The identifier string can represent the string obtained by hashing the combined string. For example, it may include, but is not limited to, the hexadecimal string output by the SHA256 algorithm, the hexadecimal or binary string output by other hash algorithms, or a combination thereof. The 256-bit hash value obtained by applying the SHA256 algorithm can be represented as a hexadecimal string, typically 64 characters long. In other embodiments, other secure hash algorithms (such as SHA384, SHA512, etc.) can also be used for hashing. Secure hash algorithms such as SHA256 are one-way and collision-resistant; any small change to the combined string will cause a significant change in the output identifier string, ensuring that the device identifier cannot be reverse-engineered from the original input, and that there is an extremely low probability of collision between device identifiers from different vehicles.
[0094] For example, the device identifier is a 32-character hexadecimal string, corresponding to a 128-bit identifier space. When the vehicle identification number and unique identifier are bound one-to-one and the irreversible mapping process uses a cryptographic hash algorithm with preset security, different vehicles will have different combined strings. The probability of different combined strings generating the same device identifier decreases as the 128-bit identifier space increases. Therefore, the device identifier can reduce the possibility of different vehicles corresponding to the same device identifier while meeting the storage and transmission length requirements of the location service provider.
[0095] Preset character position extraction rules are used to extract the first target position character from the identifier string according to a convention as the final device identifier, rather than directly using the complete identifier string. For example, preset character position extraction rules can be rules that extract characters starting from a preset starting position at a preset extraction interval, rules that extract all even-numbered characters, or rules that extract all odd-numbered characters. Preset character position extraction rules can also be rules that extract consecutive segments and then concatenate them in sequence.
[0096] By further truncating the identifier string through location extraction, the device identifier becomes more compact, facilitating storage and transmission. On the other hand, the extraction operation discards some hash information, further increasing the difficulty of restoring the original input through rainbow tables or enumeration, thus enhancing the desensitization strength.
[0097] Once the device identifier is obtained, it can be sent to the target service platform, enabling the platform to activate the target service for the target vehicle based on this identifier. For example, in activating location services, the device identifier uniquely identifies the vehicle on the location service platform. The platform then uses this identifier to create a service instance within its system, completing the account opening and activation configuration for the location service. By using the device identifier instead of the vehicle identification number (VIN) as the service activation identifier, the location service platform only interacts with the de-identified, hardware-bound device identifier throughout the entire process, avoiding direct access to the original identification information by external systems while activating the vehicle location service.
[0098] By first hashing the combined string to obtain the identifier string, and then extracting the character at the first target position from the identifier string according to the preset character position extraction rules and combining them into the device identifier, the length and format of the device identifier can be adjusted without restoring the vehicle identification code, making it more in line with the requirements of the device identifier length and format in actual applications, thus enhancing the applicability and flexibility of the device identifier.
[0099] In some embodiments, according to a preset character position extraction rule, characters at a first target position are extracted from the identifier string, and the extracted characters are combined into a device identifier, including: extracting characters from a preset starting position of the identifier string according to a preset extraction interval; and concatenating the extracted characters according to their order in the identifier string to obtain the device identifier.
[0100] The preset starting position can be, for example, the second character position of the identifier string (i.e., starting at an even position). In other embodiments, it can also be the first character position (i.e., starting at an odd position) or other preset positions. The choice of the preset starting position determines from which position in the identifier string to begin sampling; different starting positions correspond to different subsets of characters, providing configurable flexibility for the system.
[0101] The preset extraction interval can be, for example, extracting every other character (i.e., an interval of 2). For instance, taking a 64-character hexadecimal identifier string as an example, starting from the 2nd character position, extracting every other character, that is, extracting characters at positions 2, 4, 6, ..., 64, for a total of 32 characters. Another example, taking a 64-character identifier string as an example, starting from the 1st character position, extracting every other character, that is, extracting characters at positions 1, 3, 5, ..., 63, for a total of 32 characters. This evenly spaced extraction method with an interval of 2 samples 32 characters evenly from 64 characters, preserving sufficient identifier uniqueness (32 hexadecimal characters represent 16 bytes, or 128 bits, of identifier space) while reducing the identifier length to half of the original hash value, achieving a balance between uniqueness and compactness.
[0102] The extracted characters are concatenated according to their order in the identifier string, preserving their original relative order, and then concatenated sequentially to form the device identifier. Maintaining the original order ensures the determinism of the device identifier generation process; the same input will always produce the same device identifier.
[0103] In one embodiment, the preset irreversible identifier generation rule may include: concatenating the desensitized vehicle identifier and the unique identifier in the order of the desensitized vehicle identifier first and the unique identifier last to obtain a combined string; performing a SHA256 hash operation on the combined string to obtain a 64-character hexadecimal identifier string; starting from the second character position of the identifier string, extracting every other character, extracting the characters at positions 2, 4, 6...64, and concatenating them in the original order to obtain a 32-character device identifier.
[0104] By extracting characters at preset intervals from a preset starting position and splicing them in the original order, the extraction process becomes deterministic and repeatable. In addition, the equal-interval sampling ensures that the extracted characters are evenly distributed in the identifier string, reducing the output length while preserving the identifier's distinguishability. This reduces the risk of the complete identifier string being deduced or restored, further improving the device identifier's anti-analysis and anti-collision performance.
[0105] In some embodiments, the target service is a location service, and the above-described device identifier generation method may further include: sending location service activation data including the device identifier to the location service platform through an encrypted communication interface.
[0106] For example, the location service activation data does not include vehicle identification numbers and unique identifiers.
[0107] The encrypted communication interface can be, for example, a secure interface based on Transport Layer Security (TLS) 1.3 or later and combined with an authentication mechanism. The authentication mechanism can include certificate authentication, two-way TLS authentication, token authentication, or authentication based on a pre-shared key. Before sending the device identifier to the location service platform, the location service management platform verifies the identity of the location service platform. Upon successful verification, it sends location service activation data including the device identifier, thereby reducing the risk of the device identifier being obtained or tampered with by unauthorized systems during transmission. In other embodiments, other encrypted transmission protocols agreed upon between enterprises can also be used. Employing high-security encrypted communication protocols such as TLS 1.3 ensures that the device identifier is not eavesdropped on or tampered with during transmission, preventing man-in-the-middle attacks that could lead to the leakage or replacement of the device identifier.
[0108] A location service platform can represent an external service provider that offers vehicle location services, manages or activates them, and can receive device identifiers. The location service activation data sent to the location service platform does not include the vehicle identification number (VIN) and unique identifier; that is, the location service platform never accesses the plaintext information of the VIN and unique identifier. By excluding the original identification information at the data level, it ensures that even if the location service provider's system is compromised, attackers cannot obtain the VIN or unique identifier, thus preventing the VIN and unique identifier from being sent to the location service provider along with the device identifier.
[0109] Furthermore, the aforementioned device identifier generation method is universal and can be reused not only in vehicle location service scenarios but also in other scenarios requiring the provision of anonymized vehicle identifiers to external partners, such as insurance data services, remote vehicle diagnostic services, vehicle maintenance data services, or other service scenarios requiring the provision of anonymized vehicle identifiers to external partners. This allows for the formation of a unified vehicle identifier desensitization standard within the enterprise. The unified desensitized device identifier generation scheme can be reused in multiple externally shared scenarios, avoiding the need to design separate desensitization schemes for different scenarios and reducing overall R&D costs and system maintenance complexity.
[0110] By employing encrypted communication interfaces, the risk of device identification being intercepted or tampered with during transmission can be reduced. Furthermore, by excluding vehicle identification codes and unique identifiers from the location service activation data, sensitive identifiers will not leak out of the automaker's control boundaries along with device identifications. This ensures the security of vehicle identity information and on-board electronic control unit identity information at both the transmission link and data content levels, reducing the risk of information leakage caused by sharing vehicle identification codes and unique identifiers with external parties.
[0111] Furthermore, in some embodiments, the location service activation data sent to the location service platform also includes device type information corresponding to the device identifier.
[0112] Device type information can be used to characterize the type of in-vehicle device corresponding to a device identifier. For example, device type information can indicate the type of in-vehicle electronic control unit (such as TBOX) corresponding to that device identifier. Device type information enables the location service platform to know the device type without accessing sensitive information, and to adopt corresponding service configuration strategies (such as different communication protocol parameters, positioning accuracy requirements, etc.) based on different types of in-vehicle devices, thereby improving the targeting and adaptability of location service activation.
[0113] By attaching device type information along with the device identifier, the location service platform can accurately identify the device type and complete the corresponding vehicle location service activation configuration even when only receiving the de-identified device identifier and without touching the vehicle identification code and unique identifier, thereby improving the targeting and adaptability of the location service activation.
[0114] Figure 3 The diagram shown is a flowchart illustrating a device identifier generation method according to another embodiment of this disclosure. Figure 3 As shown in the embodiments of this disclosure, the device identifier generation method may include the following steps.
[0115] Step S301: Send a sales status query request carrying the vehicle identification code to the sales system and receive the sales status returned by the sales system.
[0116] Step S302: Is the sales status "actually sold"? If yes, proceed to step S303; otherwise, proceed to step S308.
[0117] Step S303: Query the binding relationship between vehicle identification number and unique identifier from the production system database.
[0118] Step S304: Does a one-to-one binding relationship exist between the vehicle identification code and the unique identifier? If yes, proceed to step S305; otherwise, proceed to step S309.
[0119] Step S305: Desensitize the vehicle identification code to obtain a desensitized vehicle identifier; and generate a device identifier based on the desensitized vehicle identifier and the unique identifier according to the preset irreversible identifier generation rules.
[0120] Step S306: Send the device identifier to the location service platform.
[0121] Step S307: The location service platform activates target services for the vehicle based on the device identifier.
[0122] Step S308: Send a message indicating that the target vehicle cannot activate the target service.
[0123] Step S309: Terminate device identifier generation.
[0124] For example, when the on-board electronic control unit (OECU) in a vehicle is replaced, the production system or after-sales maintenance system re-collects the vehicle identification number (VIN) and the unique identifier of the replaced OECU. After passing permission verification and unique identifier verification, the system updates the binding relationship in the production system database or generates a new valid binding record. When the location service management platform receives a request to activate or update the vehicle location service, it regenerates the device identifier based on the updated binding relationship and sends the regenerated device identifier to the location service platform so that the location service platform updates the corresponding service instance configuration.
[0125] It should be noted that any parts not fully described in the above examples can be referred to the aforementioned embodiments, and will not be repeated here.
[0126] The above text combined Figures 1 to 3 The present disclosure describes in detail embodiments of the device identifier generation method. The following is a detailed description in conjunction with... Figure 4 This document describes in detail embodiments of the device identifier generation apparatus. It should be understood that the descriptions of the device identifier generation method embodiments correspond to the descriptions of the device identifier generation apparatus embodiments; therefore, any parts not described in detail can be referred to the foregoing method embodiments.
[0127] Figure 4 The diagram shown is a structural schematic of a device identifier generation apparatus provided in an embodiment of this disclosure. Figure 4 As shown, the device identifier generation apparatus 400 provided in this embodiment includes: The acquisition module 410 is used to acquire the vehicle identification code of the target vehicle and the unique identifier of the on-board electronic control unit of the target vehicle. Module 420 is obtained, which is used to de-identify the vehicle identification code to obtain the de-identified vehicle identifier; The generation module 430 is used to generate a device identifier based on the desensitized vehicle identifier and the unique identifier, according to a preset irreversible identifier generation rule. The device identifier is used to activate the target service for the target vehicle.
[0128] In some embodiments, the acquisition module 410 is further configured to: in response to a target service activation request, obtain the vehicle identification code of the target vehicle from the target service activation request; query the sales status of the target vehicle based on the vehicle identification code; and if the sales status is "sold out", obtain the unique identifier of the on-board electronic control unit of the target vehicle.
[0129] In some embodiments, the acquisition module 410 is further configured to: send a prompt message indicating that the target vehicle cannot activate the target service when the sales status is not actually sold.
[0130] In some embodiments, the acquisition module 410 is further configured to: query the production system database based on the vehicle identification code to obtain the unique identifier of the on-board electronic control unit bound to the vehicle identification code; wherein, the production system database stores a one-to-one binding relationship between the vehicle identification code and the unique identifier of the on-board electronic control unit, and the binding relationship is stored in the production system database during the production stage of the target vehicle.
[0131] In some embodiments, establishing a binding relationship includes: collecting the vehicle identification code of the target vehicle and the unique identifier of the on-board electronic control unit of the target vehicle; querying the production system database based on the vehicle identification code; when there is no binding record corresponding to the vehicle identification code in the production system database, verifying the format integrity of the vehicle identification code, the non-empty state of the unique identifier, and the unique identifier not being duplicated in the production system database, and writing the binding relationship between the vehicle identification code and the unique identifier after the verification is passed.
[0132] In some embodiments, the generation module 430 is further configured to: combine the desensitized vehicle identifier with the unique identifier to obtain a combined string; and perform irreversible mapping processing on the combined string to obtain a device identifier.
[0133] In some embodiments, the generation module 430 is further configured to: perform hash processing on the combined string to obtain an identifier string; extract characters at target positions from the identifier string according to preset character position extraction rules, and combine the extracted characters into a device identifier.
[0134] In some embodiments, the obtaining module 420 is further configured to: perform character order transformation processing on the string corresponding to the vehicle identification code to obtain a transformed string; remove the characters at the second target position from the transformed string to obtain a desensitized vehicle identifier, wherein the characters at the second target position contain sensitive content, including enterprise information.
[0135] In some embodiments, the target service is a location service, and the generation module 430 is further configured to: send location service activation data including a device identifier to the location service platform through an encrypted communication interface; wherein the location service activation data does not include the original value of the vehicle identification code and the original value of the unique identifier.
[0136] Below, for reference Figure 5 To describe a vehicle according to an embodiment of this disclosure. Figure 5 The diagram shown is a structural schematic of a vehicle provided in an exemplary embodiment of this disclosure.
[0137] like Figure 5 As shown, vehicle 500 includes one or more processors 501 and memory 502.
[0138] The processor 501 may be a central processing unit (CPU) or other form of processing unit with data processing and / or instruction execution capabilities, and may control other components in the vehicle 500 to perform desired functions.
[0139] The memory 502 may include one or more computer program products, which may include various forms of computer-readable storage media, such as volatile memory and / or non-volatile memory. The volatile memory may include, for example, random access memory (RAM) and / or cache memory. The non-volatile memory may include, for example, read-only memory (ROM), hard disk, flash memory, etc. One or more computer program instructions may be stored on the computer-readable storage medium, and the processor 501 may execute the program instructions to implement the device identifier generation methods of the various embodiments of this disclosure described above and / or other desired functions. The computer-readable storage medium may also store various contents such as vehicle identification numbers, unique identifiers, de-identified vehicle identifiers, and device identifiers.
[0140] In one example, vehicle 500 may also include input device 503 and output device 504, which are interconnected via a bus system and / or other forms of connection mechanism (not shown).
[0141] The input device 503 may include, for example, a keyboard, a mouse, etc.
[0142] The output device 504 can output various information to the outside, including vehicle identification numbers, unique identifiers, de-identified vehicle identifiers, device identifiers, etc. The output device 504 may include, for example, a display, a speaker, a printer, and a communication network and its connected remote output devices, etc.
[0143] Of course, for the sake of simplicity, Figure 5 Only some of the components of the vehicle 500 relevant to this disclosure are shown, omitting components such as buses, input / output interfaces, etc. In addition, the vehicle 500 may include any other suitable components depending on the specific application.
[0144] In addition to the methods and apparatus described above, embodiments of this disclosure may also be computer program products comprising computer program instructions that, when executed by a processor, cause the processor to perform the steps in the device identifier generation methods according to various embodiments of this disclosure described above.
[0145] The computer program product can be written in any combination of one or more programming languages to perform the operations of the embodiments of this disclosure. The programming languages include object-oriented programming languages such as Java and C++, as well as conventional procedural programming languages such as C or similar languages. The program code can be executed entirely on a user's computing device, partially on a user's computing device, as a standalone software package, partially on a user's computing device and partially on a remote computing device, or entirely on a remote computing device or server.
[0146] Furthermore, embodiments of this disclosure may also be computer-readable storage media storing computer program instructions thereon, which, when executed by a processor, cause the processor to perform the steps in the device identifier generation method according to various embodiments of this disclosure described above.
[0147] The computer-readable storage medium may be any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof.
[0148] The basic principles of this disclosure have been described above with reference to specific embodiments. However, it should be noted that the advantages, benefits, and effects mentioned in this disclosure are merely examples and not limitations, and should not be considered as essential features of each embodiment of this disclosure. Furthermore, the specific details disclosed above are for illustrative and facilitative purposes only, and are not limitations. These details do not limit the scope of this disclosure to the necessity of employing the aforementioned specific details for implementation.
[0149] The block diagrams of devices, apparatuses, devices, and systems disclosed herein are merely illustrative examples and are not intended to require or imply that they must be connected, arranged, or configured in the manner shown in the block diagrams. As those skilled in the art will recognize, these devices, apparatuses, devices, and systems can be connected, arranged, and configured in any manner. Words such as “comprising,” “including,” “having,” etc., are open-ended terms meaning “including but not limited to,” and are used interchangeably with them. The terms “or” and “and” as used herein refer to the terms “and / or,” and are used interchangeably with them unless the context clearly indicates otherwise. The term “such as” as used herein refers to the phrase “such as but not limited to,” and is used interchangeably with it.
[0150] It should also be noted that in the apparatus, devices, and methods of this disclosure, the components or steps can be disassembled and / or recombined. These disassemblies and / or recombinations should be considered as equivalent solutions to this disclosure.
[0151] The above description of the disclosed aspects is provided to enable any person skilled in the art to make or use this disclosure. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the aspects shown herein, but rather to be carried out within the widest scope consistent with the principles and novel features disclosed herein.
[0152] The above description has been given for purposes of illustration and description. Furthermore, this description is not intended to limit the embodiments of this disclosure to the forms disclosed herein. Although numerous exemplary aspects and embodiments have been discussed above, those skilled in the art will recognize certain variations, modifications, alterations, additions, and sub-combinations therein.
Claims
1. A device identification generation method characterized by comprising: include: Obtain the vehicle identification number (VIN) of the target vehicle and the unique identifier of the on-board electronic control unit (OECU) of the target vehicle; The vehicle identification code is de-identified to obtain a de-identified vehicle identifier; Based on the desensitized vehicle identifier and the unique identifier, a device identifier is generated according to a preset irreversible identifier generation rule. The device identifier is used to activate the target service for the target vehicle.
2. The method of claim 1, wherein, The acquisition of the vehicle identification number (VIN) of the target vehicle and the unique identifier of the on-board electronic control unit (OECU) of the target vehicle includes: In response to a target service activation request, the vehicle identification number of the target vehicle is obtained from the target service activation request; The sales status of the target vehicle can be queried based on the vehicle identification number; If the sales status is "sold out", obtain the unique identifier of the on-board electronic control unit of the target vehicle.
3. The method of claim 2, wherein, The method further includes: If the sales status is "not sold," a notification message indicating that the target vehicle cannot activate the target service is sent.
4. The method of claim 1, wherein, Obtain the unique identifier of the on-board electronic control unit of the target vehicle, including: Based on the vehicle identification code, the production system database is queried to obtain the unique identifier of the on-board electronic control unit bound to the vehicle identification code; The production system database stores a one-to-one binding relationship between vehicle identification codes and unique identifiers of on-board electronic control units. This binding relationship is stored in the production system database during the production stage of the target vehicle.
5. The method of claim 4, wherein, The establishment of the binding relationship includes: Collect the vehicle identification number (VIN) of the target vehicle and the unique identifier of the on-board electronic control unit (OECU) of the target vehicle; The production system database is queried based on the vehicle identification code; If the binding relationship corresponding to the vehicle identification code does not exist in the production system database, the integrity of the vehicle identification code format, the non-empty state of the unique identifier, and the fact that the unique identifier is not duplicated in the production system database are verified. After the verification is passed, the binding relationship between the vehicle identification code and the unique identifier is written.
6. The method of claim 1, wherein, The process of generating a device identifier based on the desensitized vehicle identifier and the unique identifier, according to a preset irreversible identifier generation rule, includes: The desensitized vehicle identifier is combined with the unique identifier to obtain a combined string; The combined string is subjected to irreversible mapping processing to obtain the device identifier.
7. The method of claim 6, wherein, The process of performing irreversible mapping on the combined string to obtain the device identifier includes: The combined string is hashed to obtain the identifier string; According to the preset character position extraction rules, the character at the first target position is extracted from the identifier string, and the extracted characters are combined to form the device identifier.
8. The method of claim 1, wherein, The process of de-identifying the vehicle identification code to obtain a de-identified vehicle identifier includes: The character order of the string corresponding to the vehicle identification code is transformed to obtain the transformed string; The characters at the second target position are removed from the transformed string to obtain the desensitized vehicle identifier. The characters at the second target position contain sensitive content, including enterprise information.
9. The method according to any one of claims 1 to 8, characterized in that, The target service is a location service, and the method further includes: The location service activation data, including the device identifier, is sent to the location service platform via an encrypted communication interface. The location service activation data does not include the vehicle identification number and the unique identifier.
10. A vehicle characterized by comprising: include: processor; Memory used to store the processor's executable instructions; The processor is configured to execute the device identifier generation method according to any one of claims 1 to 9.
