Method and system for generating unique device identifier

Abstract

The present invention discloses a method and system for generating a unique device identifier, which generates a unique identifier for a mobile device through software and hardware information, and realizes data sharing between various APPs in the platform through the unique identifier of the mobile device. The technical scheme is as follows: the method includes: step 1: obtaining a device identifier through a cross-application cache, if the device identifier is successfully obtained and it meets the rule of starting with a preset character, then directly jump to step 4; step 2: based on the obtained device identifier, generate a string used as a unique device identifier; step 3: cache the string used as a unique device identifier generated in step 2 through a cross-application cache; step 4: output the string generated in step 2 or obtained in step 1 as a unique device identifier for use by the business party.

Description

Technical Field

[0001] The present invention relates to a technology for generating a device identifier, and specifically to a method and system for generating a unique identifier for a mobile device through software and hardware information, which is applied to the fields of mobile terminal development, mobile payment risk control, user data analysis, etc. Background Art

[0002] As the country and individuals attach great importance to information security, the identifiers that were previously commonly used in the industry to uniquely identify mobile devices, such as IMEI, Mac address, IDFA and other information, are prohibited from being read; and if UUID and other information provided by a third party is used, there may be a risk of being replaced or substituted, or the APP Store refusing to list the product, resulting in the inability to uniquely identify the user's device, and thus the inability to monitor transaction behavior in real time, and the inability to accurately identify fraud and other behaviors, resulting in risks in asset losses and policy supervision.

[0003] In view of this, in order to protect the funds and transaction security of platform users and comply with policy monitoring and regulatory rules, the industry needs to independently develop a set of unique device identifiers that can be shared by various APPs of the company, on the premise of complying with relevant information security laws and regulations, to meet the relevant needs in the fields of mobile terminal development, mobile transaction risk control, and user data analysis. Summary of the invention

[0004] A brief summary of one or more aspects is given below to provide a basic understanding of these aspects. This summary is not an exhaustive overview of all conceived aspects, and is neither intended to identify the key or critical elements of all aspects nor to define the scope of any or all aspects. Its only purpose is to give some concepts of one or more aspects in a simplified form as a prelude to a more detailed description that will be given later.

[0005] The purpose of the present invention is to solve the above-mentioned problems and provide a method and system for generating a unique device identifier. The unique identifier of a mobile device is generated through software and hardware information. The unique identifier of the mobile device is used to share data between various APPs in the platform, help mobile terminal developers to identify mobile devices, and after uploading to the background, it can be used to ensure risk control in payment transactions and analysis of key measurement indicators, including conversion rate (CVR), average revenue per user (ARPU), etc.

[0006] The technical solution of the present invention is: the present invention discloses a method for generating a unique identifier of a device, the method comprising:

[0007] Step 1: Get the device identifier through the cross-application cache. If the device identifier is successfully obtained and it meets the rule of starting with the preset characters, jump directly to step 4.

[0008] Step 2: Based on the obtained device identifier, generate a string used as a unique identifier of the device;

[0009] Step 3: Cache the string used as the device unique identifier generated in step 2 through cross-application caching;

[0010] Step 4: Output the string generated in step 2 or obtained in step 1 as the unique device identifier for use by the business party.

[0011] According to an embodiment of the method for generating a unique device identifier of the present invention, cross-application caching is to cache data including the device identifier into a public keychain through the SecKeychain interface of the IOS system.

[0012] According to an embodiment of the method for generating a unique device identifier of the present invention, step 2 further comprises:

[0013] Generate a universal unique identification code string based on the device identifier obtained in step 1 through the IOS system interface;

[0014] Provide a preset character prefix for the universal unique identifier string;

[0015] Through the IOS system interface, the device code is obtained and appended to the end of the universal unique identifier string, forming a three-part long string with no string separators, starting with a preset character prefix, centered at the universal unique identifier, and ending with the device code, as the device unique identifier string.

[0016] The present invention also discloses a method for generating a unique device identifier, the method comprising:

[0017] Step 1: Read the string content in the specified file of the external storage, and determine whether the read string meets the conditions. If so, synchronize the read string to the specified file and specified keyword in the shared option storage mode, and then return the read string in advance, and the whole process ends;

[0018] Step 2: If the string read in step 1 does not meet the conditions, continue to read the key-value string corresponding to the specified file and the specified keyword in the shared option storage mode. If the key-value string read in step 2 meets the conditions, then synchronously write the key-value string read in step 2 to the external storage specified file. Before writing to the external storage specified file, check whether there is corresponding access permission to the external storage. If there is no permission, do not write, and return the key-value string read in step 2 in advance.

[0019] Step 3: If the key value string read in step 2 does not meet the conditions, create a string starting with preset characters, and based on the device logo obtained from the Android system, concatenate and encrypt multiple fields to form the final device unique identifier format, and synchronize the value of the final format to the specified file directory and specified keyword under the shared option storage method, as well as the specified file in the external storage.

[0020] According to one embodiment of the method for generating a unique device identifier of the present invention, a specified file path is pre-created in an external storage, the specified file path includes a field for a custom keyword, and the key value of the keyword is output in the form of a string. The condition in step 1 is to determine whether the string is empty and conforms to a pre-defined beginning format.

[0021] According to an embodiment of the method for generating a unique device identifier of the present invention, the concatenation and encryption of multiple fields in step 3 further includes:

[0022] First, the fields including the timestamp, model, device hardware name, or the combination of the device hardware identification code and the device logo are first concatenated, and then the content of the first concatenation is encrypted through md5. After the encrypted string is generated, it is concatenated again with the previously created string starting with the preset characters to form the final format of the device unique identifier.

[0023] The present invention also discloses a system for generating a unique device identifier, the system comprising:

[0024] A device identifier acquisition module is configured to acquire a device identifier through a cross-application cache, and if the device identifier is acquired successfully and it meets the rule of starting a field with a preset character, directly jump to a device unique identifier output module;

[0025] A device unique identifier generating module, configured to generate a character string used as a device unique identifier based on the device identifier acquired by the device identifier acquiring module;

[0026] A device unique identifier cache module, configured to cache the character string used as the device unique identifier generated by the device unique identifier generation module through a cross-application cache;

[0027] The device unique identifier output module is configured to output the character string generated by the device unique identifier generation module or acquired by the device identifier acquisition module as the device unique identifier for use by the business party.

[0028] According to an embodiment of the system for generating a unique device identifier of the present invention, cross-application caching is to cache data including the device identifier into a public keychain through the SecKeychain interface of the IOS system.

[0029] According to an embodiment of the system for generating a device unique identifier of the present invention, the device unique identifier generating module is further configured to perform the following processing:

[0030] Generate a universal unique identification code string based on the device identifier obtained by the device identifier obtaining module through the IOS system interface;

[0031] Provide a preset character prefix for the universal unique identifier string;

[0032] Through the IOS system interface, the device code is obtained and appended to the end of the universal unique identifier string, forming a three-part long string with no string separators, starting with a preset character prefix, centered at the universal unique identifier, and ending with the device code, as the device unique identifier string.

[0033] The present invention also discloses a system for generating a unique device identifier, the system comprising:

[0034] The external storage designated file processing module is configured to read the string content in the external storage designated file, determine whether the read string meets the conditions, and if so, synchronize the read string to the designated file and designated keyword in the shared option storage mode, and then return the read string in advance, and the whole process ends;

[0035] The shared option storage processing module is configured to continue reading the key-value string corresponding to the designated file and the designated keyword in the shared option storage mode if the string read by the external storage designated file processing module does not meet the conditions; if the key-value string read in the shared option storage processing module meets the conditions, then synchronously write the key-value string read in the shared option storage processing module to the external storage designated file; before writing to the external storage designated file, first check whether there is corresponding access permission to the external storage; if there is no permission, do not perform the write operation, and return the key-value string read in the shared option storage processing module in advance;

[0036] The device unique identifier creation module is configured to create a string starting with preset characters if the key value string read in the shared option storage processing module does not meet the conditions, and based on the device logo obtained from the Android system, concatenate and encrypt multiple fields to form the final device unique identifier format, and synchronize the value of the final format to the specified file directory and specified keyword under the shared option storage method, as well as the specified file in the external storage.

[0037] According to one embodiment of a system for generating a unique device identifier of the present invention, in an external storage designated file processing module, a designated file path is pre-created in the external storage, the designated file path includes a field for a custom keyword, and the key value of the keyword is output in the form of a string. The condition in the external storage designated file processing module is to determine whether the string is empty and conforms to a pre-defined beginning format.

[0038] According to an embodiment of the system for generating a device unique identifier of the present invention, the concatenation and encryption processing of multiple fields in the device unique identifier creation module further includes:

[0039] First, the fields including the timestamp, model, device hardware name, or the combination of the device hardware identification code and the device logo are first concatenated, and then the content of the first concatenation is encrypted through md5. After the encrypted string is generated, it is concatenated again with the previously created string starting with the preset characters to form the final format of the device unique identifier.

[0040] Compared with the prior art, the present invention has the following beneficial effects: in the method of the present invention, on the one hand, the cross-application caching technology is used to realize the sharing of the unique identifier Device ID of the mobile device among various APPs within the platform; on the other hand, in different operating systems, a three-segment character structure with respective preset characters as prefixes, a generated UUID (Universally Unique Identifier) ​​string as the middle segment, and a device code as the end is used to isolate the data cached by other platforms, thereby realizing the unique effect of the platform data itself. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] The above features and advantages of the present invention can be better understood after reading the detailed description of the embodiments of the present disclosure in conjunction with the following drawings. In the drawings, the components are not necessarily drawn to scale, and components with similar related properties or features may have the same or similar reference numerals.

[0042] Figure 1 The flowchart of the first embodiment of the method for generating a unique device identifier of the present invention is shown.

[0043] Figure 2 The flowchart of the second embodiment of the method for generating a unique device identifier of the present invention is shown.

[0044] Figure 3 The structure diagram of the first embodiment of the system for generating a unique device identifier of the present invention is shown.

[0045] Figure 4 The structure diagram of the second embodiment of the system for generating a unique device identifier of the present invention is shown. DETAILED DESCRIPTION

[0046] The present invention is described in detail below in conjunction with the accompanying drawings and specific embodiments. Note that the aspects described below in conjunction with the accompanying drawings and specific embodiments are only exemplary and should not be construed as limiting the scope of protection of the present invention in any way.

[0047] Figure 1 The flow chart of the first embodiment of the method for generating a unique device identifier of the present invention is shown. In this embodiment, the implementation of the present invention in the IOS operating system is used as an example for explanation.

[0048] Step 1: Get the device identifier through the cross-application cache technology. If the device identifier is successfully obtained and it meets the rule of starting with the 'i.' string, jump directly to step 4.

[0049] Cross-application caching technology caches data including device identifiers into the public keychain through the system's SecKeychain interface.

[0050] If the obtained string meets the rule of starting with the string 'i.', it means that the unique identifier of the device, Device ID, is read in this step.

[0051] In this embodiment, the 'i.' character string is used as the starting field for example only. In other embodiments, other preset characters may be used as the starting field.

[0052] Step 2: Based on the acquired device identifier, generate a character string used as the device unique identifier Device ID.

[0053] Step 2 further includes three steps of processing, which are as follows.

[0054] Step 2a: Generate a universal unique identifier (UUID) string based on the device identifier obtained in step 1 through the system interface.

[0055] Specifically, in step 2a, a 32-bit UUID string is generated by calling the IOS system interface CFUUIDCreate.

[0056] Step 2b: Give the UUID string an 'i.' prefix.

[0057] In this embodiment, providing the UUID character string with an 'i.' prefix is ​​only an example. In other embodiments, other preset characters may be used to provide a prefix for the UUID character string.

[0058] Step 2c: Obtain the device code through the system interface and append it to the end of the UUID string, forming a three-part long string with no string separators, starting with 'i.', centered with the UUID, and ending with the device code.

[0059] The device code in step 2c, that is, the model information of the device itself, is obtained through the IOS system API sysctlbyname function, and the result is a string, for example: iPhone11,8.

[0060] The unique device identifier Device ID generated in step 2 is compared to the device identifier obtained in step 1, and has the model information of the device itself (ie, the device code) added thereto.

[0061] Step 3: Use the cross-application cache technology to cache the string generated in step 2 that is used as the device's unique identifier, Device ID.

[0062] Step 4: Output the string generated in step 2 or obtained in step 1 as the device unique identifier DeviceID for use by the business party.

[0063] Figure 2 The flow chart of the second embodiment of the method for generating a unique device identifier of the present invention is shown. In this embodiment, the implementation of the present invention in an Android operating system is used as an example for explanation.

[0064] Step 1: Read the string content in the specified file of external storage, and determine whether the read string meets the conditions (the conditions are "not empty and conform to the pre-defined beginning format"). If so, synchronize the read string to the specified file and the specified keyword (key) under the Shared Preferences storage method, return the read string in advance, and the whole process ends.

[0065] For example, a specified file path is pre-created in the external storage, BUFFERED_FINAL_UDID_KEY in the specified file path is a custom part, and the key value of the keyword key is output in the form of a string, and it is determined whether the string is empty and conforms to a pre-defined beginning format, such as whether it is a string beginning with 'A.' In this embodiment, the 'A.' string is used as the starting field for example only, and in other embodiments, other preset characters may also be used as the starting field.

[0066] If the string read from the above custom keyword (BUFFERED_FINAL_UDID_KEY) as the key value is not empty and conforms to the pre-defined leading format, the key value (i.e. the above string) is synchronized to the specified file and the specified keyword key under the SharedPreferences storage mode, and then the read string is returned in advance, and the whole process ends.

[0067] Shared Preferences is a lightweight storage class on the Android platform that is used to save some common configurations of applications and is suitable for storing lightweight data. It is divided into multiple permissions and can be shared globally.

[0068] In this step, the purpose of synchronizing to the specified file and the specified keyword key under the Shared Preferences storage method is to prevent the external storage content from being deleted by objective circumstances, so that the APP can still obtain the stored content.

[0069] Step 2: If the string read in step 1 does not meet the conditions (that is, it does not meet the condition that "the string is not empty and conforms to the pre-defined beginning format"), continue to read the key-value string corresponding to the specified file and the specified key in the Shared Preferences storage mode. If the key-value string read in step 2 meets the conditions (that is, it meets the condition that "the string is not empty and conforms to the pre-defined beginning format"), then synchronously write the key-value string read in step 2 to the specified file of the external storage. Before writing to the specified file of the external storage, check whether there is corresponding access permission to the external storage. If there is no permission, do not write, and return the key-value string stored in the Shared Preferences read in this step 2 in advance.

[0070] Step 3: If the key value string read in step 2 does not meet the conditions (that is, it does not meet the condition of "the string is not empty and conforms to the pre-defined beginning format"), create a string starting with 'A.', and based on the ANDROID_ID (device identifier, which is the device ID provided by the Android system for easy access to applications) obtained from the system, multiple fields are concatenated and encrypted to form the final device unique identifier format, and the value of the final format is synchronized to the specified file directory and the specified keyword (key) under the SharedPreferences storage method, as well as the specified file in the external storage.

[0071] Similarly, in the above process, the use of the character string 'A.' as the starting field is only an example. In other embodiments, other preset characters may be used as the starting field.

[0072] The value of ANDROID_ID changes with the ANDROID system. It is the unique ID of the ANDROID system. It is a 64-bit number randomly generated when the ANDROID system is started for the first time. It will also change after re-flashing the system. At the same time, bugs in the manufacturer's customized system may cause different devices to generate the same ANDROID_ID, and the ANDROID_ID obtained by some devices is null.

[0073] Taking the above situation into consideration, first concatenate the other fields with ANDROID_ID (other fields such as timestamp, model, device hardware name, and device hardware identification code), then encrypt the concatenated content of the above multiple fields through md5, generate a 32-bit encrypted string, and then concatenate it with the previously created string starting with 'A.' to form the final device unique identifier format: "A. (32-bit string generated by md5 encryption)".

[0074] The purpose of synchronizing to the specified file in the external storage is to enable the use of the SDK (Software Development Kit) or the APP generated in this way to obtain the same unique identifier. The purpose of storing it in the specified file directory and keyword of the SP is to prevent the external storage file from having no content due to permission issues, and then read it from the current private directory.

[0075] Figure 3 The structure of the first embodiment of the system for generating a unique device identifier of the present invention is shown. Figure 3 The system of this embodiment includes: a device identifier acquisition module, a device unique identifier generation module, a device unique identifier cache module, and a device unique identifier output module.

[0076] The device identifier acquisition module is configured to obtain the device identifier through the cross-application cache. If the device identifier is successfully obtained and it meets the rule of starting with a preset character, it will directly jump to the device unique identifier output module. The cross-application cache caches data including the device identifier into the public keychain through the SecKeychain interface of the IOS system.

[0077] The device unique identifier generating module is configured to generate a character string used as the device unique identifier based on the device identifier acquired by the device identifier acquiring module.

[0078] The device unique identifier generation module is further configured to perform the following processing: through the IOS system interface, generate a universal unique identification code string based on the device identifier obtained by the device identifier acquisition module; provide a preset character prefix for the universal unique identification code string; through the IOS system interface, obtain the device code and append it to the end of the universal unique identification code string, forming a three-segment long string with no string separators, starting with the preset character prefix, centered with the universal unique identification code, and ending with the device code, as the device unique identifier string.

[0079] The device unique identifier cache module is configured to cache the character string used as the device unique identifier generated by the device unique identifier generation module through a cross-application cache.

[0080] The device unique identifier output module is configured to output the character string generated by the device unique identifier generation module or acquired by the device identifier acquisition module as the device unique identifier for use by the business party.

[0081] Figure 4 The structure of the second embodiment of the system for generating a unique device identifier of the present invention is shown. Figure 4 The system of this embodiment includes: an external storage designated file processing module, a shared option storage processing module, and a device unique identifier creation module.

[0082] The external storage designated file processing module is configured to read the string content in the external storage designated file, determine whether the read string meets the conditions, and if so, synchronize the read string to the designated file and designated keyword under the shared option storage mode, and then return the read string in advance, and the whole process ends.

[0083] In the external storage designated file processing module, a designated file path is pre-created in the external storage. The designated file path includes a field for a custom keyword, and the key value of the keyword is output in the form of a string. The condition in the external storage designated file processing module is to determine whether the string is empty and conforms to a pre-defined beginning format.

[0084] The shared option storage processing module is configured to continue reading the key value string corresponding to the specified file and the specified keyword under the shared option storage mode if the string read by the external storage specified file processing module does not meet the conditions. If the key value string read in the shared option storage processing module meets the conditions, the key value string read in the shared option storage processing module is synchronously written to the external storage specified file. Before writing to the external storage specified file, check whether there is corresponding access permission to the external storage. If there is no permission, do not perform the write operation, and return the key value string read in the shared option storage processing module in advance.

[0085] The device unique identifier creation module is configured to create a string starting with preset characters if the key value string read in the shared option storage processing module does not meet the conditions, and based on the device logo obtained from the Android system, concatenate and encrypt multiple fields to form the final device unique identifier format, and synchronize the value of the final format to the specified file directory and specified keyword under the shared option storage method, as well as the specified file in the external storage.

[0086] The concatenation and encryption process of multiple fields in the device unique identifier creation module further includes:

[0087] First, the fields including the timestamp, model, device hardware name, or the combination of the device hardware identification code and the device logo are first concatenated, and then the content of the first concatenation is encrypted through md5. After the encrypted string is generated, it is concatenated again with the previously created string starting with the preset characters to form the final format of the device unique identifier.

[0088] Although the above methods are illustrated and described as a series of actions for simplicity of explanation, it should be understood and appreciated that these methods are not limited by the order of the actions, because according to one or more embodiments, some actions may occur in a different order and / or concurrently with other actions from those illustrated and described herein or not illustrated and described herein but understandable to those skilled in the art.

[0089] Those skilled in the art will further appreciate that the various illustrative logic blocks, modules, circuits, and algorithm steps described in conjunction with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or a combination of the two. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps are generally described above in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. The technician may implement the described functionality in different ways for each specific application, but such implementation decisions should not be interpreted as resulting in a departure from the scope of the present invention.

[0090] The various illustrative logic blocks, modules, and circuits described in conjunction with the embodiments disclosed herein may be implemented or performed with a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in cooperation with a DSP core, or any other such configuration.

[0091] The steps of the method or algorithm described in conjunction with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. The software module may reside in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to a processor so that the processor can read and write information from / to the storage medium. In an alternative, a storage medium may be integrated into a processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In an alternative, the processor and the storage medium may reside in a user terminal as discrete components.

[0092] In one or more exemplary embodiments, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented as a computer program product in software, each function may be stored on or transmitted by a computer-readable medium as one or more instructions or codes. Computer-readable media include both computer storage media and communication media, including any medium that facilitates the transfer of a computer program from one place to another. Storage media may be any available medium that can be accessed by a computer. As an example and not limitation, such a computer-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of an instruction or data structure and can be accessed by a computer. Any connection is also properly referred to as a computer-readable medium. For example, if the software is transmitted from a website, a server, or other remote source using a coaxial cable, a fiber optic cable, a twisted pair, a digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwaves, the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwaves are included in the definition of the medium. Disk and disc as used herein include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc, wherein disk often reproduces data magnetically, while disc reproduces data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0093] The previous description of the disclosure is provided to enable any person skilled in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the spirit or scope of the disclosure. Thus, the disclosure is not intended to be limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for generating a unique device identifier, characterized in that: Methods include: Step 1: Read the string content in the specified file of the external storage, and determine whether the read string meets the conditions. If so, synchronize the read string to the specified file and specified keyword in the shared option storage mode, and then return the read string in advance, and the whole process ends; Step 2: If the string read in step 1 does not meet the conditions, continue to read the key-value string corresponding to the specified file and the specified keyword in the shared option storage mode. If the key-value string read in step 2 meets the conditions, then synchronously write the key-value string read in step 2 to the external storage specified file. Before writing to the external storage specified file, check whether there is corresponding access permission to the external storage. If there is no permission, do not write, and return the key-value string read in step 2 in advance. Step 3: If the key value string read in step 2 does not meet the conditions, create a string starting with preset characters, and based on the device logo obtained from the Android system, concatenate and encrypt multiple fields to form the final device unique identifier format, and synchronize the value of the final format to the specified file directory and specified keyword under the shared option storage method, as well as the specified file in the external storage.

2. The method for generating a unique device identifier according to claim 1, characterized in that: A specified file path is pre-created in the external storage. The specified file path includes a field of a custom keyword. The key value of the keyword is output in the form of a string. The condition in step 1 is to determine whether the string is empty and conforms to a pre-defined beginning format.

3. The method for generating a unique device identifier according to claim 1, characterized in that: The concatenation and encryption of multiple fields in step 3 further includes: First, the fields including the timestamp, model, device hardware name, or the combination of the device hardware identification code and the device logo are first concatenated, and then the content of the first concatenation is encrypted through md5. After the encrypted string is generated, it is concatenated again with the previously created string starting with the preset characters to form the final format of the device unique identifier.

4. A system for generating a unique device identifier, characterized in that: The system includes: The external storage designated file processing module is configured to read the string content in the external storage designated file, determine whether the read string meets the conditions, and if so, synchronize the read string to the designated file and designated keyword in the shared option storage mode, and then return the read string in advance, and the whole process ends; The shared option storage processing module is configured to continue reading the key-value string corresponding to the designated file and the designated keyword in the shared option storage mode if the string read by the external storage designated file processing module does not meet the conditions; if the key-value string read in the shared option storage processing module meets the conditions, then synchronously write the key-value string read in the shared option storage processing module to the external storage designated file; before writing to the external storage designated file, first check whether there is corresponding access permission to the external storage; if there is no permission, do not perform the write operation, and return the key-value string read in the shared option storage processing module in advance; The device unique identifier creation module is configured to create a string starting with preset characters if the key value string read in the shared option storage processing module does not meet the conditions, and based on the device logo obtained from the Android system, concatenate and encrypt multiple fields to form the final device unique identifier format, and synchronize the value of the final format to the specified file directory and specified keyword under the shared option storage method, as well as the specified file in the external storage.

5. The system for generating a unique device identifier according to claim 4, characterized in that: In the external storage designated file processing module, a designated file path is pre-created in the external storage. The designated file path includes a field for a custom keyword, and the key value of the keyword is output in the form of a string. The condition in the external storage designated file processing module is to determine whether the string is empty and conforms to a pre-defined beginning format.

6. The system for generating a unique device identifier according to claim 4, characterized in that: The concatenation and encryption process of multiple fields in the device unique identifier creation module further includes: First, the fields including the timestamp, model, device hardware name, or the combination of the device hardware identification code and the device logo are first concatenated, and then the content of the first concatenation is encrypted through md5. After the encrypted string is generated, it is concatenated again with the previously created string starting with the preset characters to form the final format of the device unique identifier.

Images