Authorization verification method and device of iOS equipment and electronic equipment

Abstract

The embodiment of the invention provides an authorization verification method for an iOS device. The method comprises the steps of obtaining a system version and model information of the iOS device and a globally unique identifier of an electronic book application; creating a downloading management database file, wherein the downloading management database file stores downloading addresses and equipment storage paths of the metadata file, the database management file, the pre-writing log file and the shared memory file; uploading the downloading management database file to a downloading directory of the iOS equipment in a compressed package file form; and downloading and decompressing the compressed package file, injecting the contained system configuration file into a system directory, and enabling the injected system configuration file to take effect so as to perform authorization verification on the iOS equipment. According to the authorization verification method for the iOS equipment, the authorization difficulty can be effectively solved in a legal user scene, and practicability and safety are both achieved. The embodiment of the invention further provides an authorization verification device of the iOS equipment and electronic equipment.

Description

Technical Field

[0001] This application relates to the field of mobile device security technology, and more specifically, to an authorization verification method, apparatus, and electronic device for iOS devices. Background Technology

[0002] Activation Lock is an authorization and verification mechanism deeply embedded in the iOS system. When a device is erased or reactivated, the system forces verification of the Apple ID and password associated with the original device. Only after successful verification can the device be reactivated and access the operating system. This design plays a crucial role in enhancing device security and combating theft.

[0003] However, this robust mechanism, designed to protect user assets, presents significant authorization verification challenges for legitimate device owners in practice. In numerous scenarios, such as when users forget their Apple ID passwords, when previous owners fail to unbind their devices after purchasing secondhand goods, or when organizations manage test devices in bulk due to procedural oversights, the devices, though physically owned by the legitimate users, are logically permanently locked due to the inability to pass system-level authorization verification, rendering them unusable electronic bricks. This not only results in direct financial losses for individual users but also negatively impacts corporate asset management and environmental protection (electronic waste generated from premature device obsolescence).

[0004] Currently, existing technical solutions to this problem have significant limitations and cannot effectively solve the authorization verification problem for legitimate users. Summary of the Invention

[0005] To address the problems existing in the prior art, this application provides an authorization verification method, device, and electronic device for iOS devices, which can effectively solve the authorization dilemma in legitimate user scenarios and has both practicality and security.

[0006] In a first aspect, embodiments of this application provide an authorization verification method for an iOS device, comprising the following steps: Obtain the system version, model information, and globally unique identifier of the e-book application for the iOS device; Based on the iOS device's system version, model information, and the globally unique identifier of the e-book application, a download management database file is created. The download management database file stores the download addresses and device storage paths of metadata files, database management files, write-ahead log files, and shared memory files. Upload the download management database file as a compressed file to the download directory of the iOS device; and Download and decompress the compressed file, inject the contained system configuration file into the system directory, and make the injected system configuration file effective to perform authorization verification on the iOS device.

[0007] Furthermore, the unique identifier of the e-book application on the iOS device is obtained by parsing the system service response, and is used to guide the determination of the subsequent file download path.

[0008] Furthermore, the step of creating a download management database file based on the iOS device's system version, model information, and the globally unique identifier of the e-book application, wherein the download management database file stores the download addresses and device storage paths of metadata files, database management files, write-ahead log files, and shared memory files, includes: Based on the iOS device's system version, model information, and the globally unique identifier of the e-book application, the download management database file is created using a structured query language script according to a database generation algorithm. The download management database file stores the download addresses and device storage paths of metadata files, database management files, write-ahead log files, and shared memory files.

[0009] Furthermore, the structured query language script is dynamically generated based on the system version and model information of the iOS device, and adaptively generates database scripts containing the paths and download addresses of the metadata file, the database management file, the write-ahead log file, and the shared memory file.

[0010] Furthermore, the database management file includes a download information table, which stores the download address and device storage path of the compressed file.

[0011] Furthermore, the compressed file is generated by packaging the system configuration file and media type file using a compression algorithm, and the iOS device's system automatically decompresses the compressed file to a specified directory.

[0012] Furthermore, the system configuration file contains modified system configuration parameters to overwrite the original system file for authorization verification of the iOS device.

[0013] Secondly, embodiments of this application also provide an authorization verification device for an iOS device, comprising: The information acquisition module is used to acquire the system version, model information of the iOS device, and the globally unique identifier of the e-book application; The file creation module is used to create a download management database file based on the system version and model information of the iOS device and the globally unique identifier of the e-book application. The download management database file stores the download addresses and device storage paths of metadata files, database management files, write-ahead log files, and shared memory files. The file upload module is used to upload the download management database file as a compressed file to the download directory of the iOS device; and The authorization verification module is used to load and decompress the compressed file, inject the contained system configuration file into the system directory, and finally restart the iOS device to make the injected system configuration file take effect in order to perform authorization verification on the iOS device.

[0014] Thirdly, embodiments of this application also provide an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the authorization verification method for an iOS device according to the first aspect described above.

[0015] Fourthly, embodiments of this application also provide a computer-readable storage medium having a computer program stored thereon, the computer program being used to implement the authorization verification method for an iOS device according to the first aspect described above.

[0016] Fifthly, embodiments of this application also provide a computer program product having a computer program stored thereon, the computer program being used to implement the authorization verification method for an iOS device according to the first aspect described above.

[0017] The embodiments of this application bring the following beneficial effects: The iOS device authorization verification method in this application achieves efficient and non-intrusive device authorization management through multi-step collaborative processes. First, it obtains the device system version, model information, and the globally unique identifier (GUID) of the e-book application, providing accurate information for subsequent file path location. Second, the server dynamically generates a Structured Query Language (SQL) script based on the above information, creating a download management database file. This file integrates the download addresses and device storage paths of the storage metadata file, database management file, and auxiliary log files (write-ahead log files and shared memory files), ensuring a high degree of compatibility between resource configuration and the device environment. Next, by uploading the database file as a compressed package to the device's download directory and triggering a device restart, the system automatically downloads the specified file, achieving seamless file management. Finally, after restarting the device again, the system automatically downloads and decompresses the compressed package, injecting the contained system configuration file into the system directory, overriding the original verification logic, and making the configuration file effective, thereby completing the authorization verification. In the iOS device authorization verification method of this application embodiment, information acquisition lays the foundation for file generation, database files guide the download process, and file injection depends on the decompression mechanism, forming a closed-loop control system. This improves device availability, avoids device failure due to authorization verification failure, and ensures operational reliability through file integrity verification. This method effectively solves the authorization dilemma in legitimate user scenarios, combining practicality and security. Attached Figure Description

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

[0019] Figure 1 A flowchart illustrating the authorization verification method for iOS devices provided in this application embodiment; Figure 2 A structural block diagram of the authorization verification device for an iOS device provided in the embodiments of this application; Figure 3 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application.

[0020] The realization of the purpose, functional features and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0021] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of this application.

[0022] In the specification, claims, and accompanying drawings of this application, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this application, unless otherwise stated, "a plurality of" means two or more. Those skilled in the art can understand the specific meaning of the above terms in this application according to the specific circumstances.

[0023] Figure 1 This is a flowchart of an authorization verification method for an iOS device according to an embodiment of this application. Figure 1 As shown, the authorization verification method for an iOS device according to an embodiment of this application includes the following steps: S101: Obtain the system version, model information, and globally unique identifier of the e-book application for the iOS device; S102: Based on the system version and model information of the iOS device and the globally unique identifier of the e-book application, create a download management database file. The download management database file stores the download addresses and device storage paths of metadata files, database management files, write-ahead log files, and shared memory files. S103: Upload the download management database file as a compressed file to the download directory of the iOS device; and S104: Download and decompress the compressed file, inject the contained system configuration file into the system directory, and make the injected system configuration file effective to perform authorization verification on the iOS device.

[0024] Specifically, in the iOS device authorization verification method of this application embodiment, firstly, in step S101, a connection is established with the iOS device through Apple Mobile Device Service to automatically obtain the device's system version and model information; then, the device is restarted, and the system tracing relay service (com.apple.os_trace_relay) is called to obtain the globally unique identifier (GUID) of the e-book application (Books application). This identifier is used to accurately locate the internal file path of the device, ensuring that subsequent operations are targeted. In step S102, the server executes a specific Structured Query Language (SQL) script based on the obtained device information (e.g., system version and model) to execute a database generation algorithm to create a download management database file (e.g., downloads.28.sqlitedb). This database file contains resource tables, which record in detail the metadata files (e.g., iTunesMetadata.plist), database management files (e.g., BLDatabaseManager.sqlite), and their auxiliary log files, including the download address and device storage path of the write-ahead log file (e.g., BLDatabaseManager.sqlite-wal) and the shared memory file (e.g., BLDatabaseManager.sqlite-shm). This adaptive generation mechanism ensures a high degree of matching between file paths and device environments, laying the foundation for subsequent automated file management. This process fully utilizes system service interactions and database operation algorithms to achieve non-intrusive information collection and resource allocation.

[0025] In step S103, the system uploads the download management database file as a compressed package to the iOS device's download directory (e.g., / Downloads). The iOS device automatically downloads the metadata file and database management file specified in the database file. Specifically, BLDatabaseManager.sqlite is generated from a specific SQL statement. The download information table (e.g., ZBLDOWNLOADINFO table) stores the download address and storage path of the asset.epub compressed package file on the device. The asset.epub file is generated by packaging the com.apple.MobileGestalt.plist system configuration file and the MIME type media type file into a zip archive. The downloads.28.sqlitedb file is also uploaded to the download directory ( / Downloads directory).

[0026] In step S104, a compressed file (such as asset.epub, which is generated by packaging system configuration files and media type files using a ZIP algorithm) is downloaded, and the compressed file is decompressed using the built-in decompression mechanism of iOS. The system configuration file (such as com.apple.MobileGestalt.plist) is released to the system directory to achieve the injection and overwriting of key files and make the injected system configuration file effective. This system configuration file contains modified authorization verification parameters, which can directly interfere with the native iOS verification process, thereby completing the authorization verification process for the device.

[0027] Therefore, the iOS device authorization verification method in this application achieves efficient and non-intrusive device authorization management through multi-step collaborative processes. First, it obtains the device system version, model information, and the globally unique identifier (GUID) of the e-book application, providing accurate information for subsequent file path location. Second, the server dynamically generates a Structured Query Language (SQL) script based on the above information, creating a download management database file (e.g., downloads.28.sqlitedb). This file integrates the download addresses and device storage paths of storage metadata files, database management files, and their auxiliary log files (write-ahead log files and shared memory files), ensuring a high degree of compatibility between resource configuration and the device environment. Next, by uploading the database file as a compressed package to the device's download directory and triggering a device restart, the system automatically downloads the specified file, achieving seamless file management. Finally, after restarting the device again, the system automatically downloads and decompresses the compressed package, injecting the contained system configuration file into the system directory, overriding the original verification logic, making the configuration file effective, and thus completing the authorization verification. In the iOS device authorization verification method of this application embodiment, information acquisition lays the foundation for file generation, database files guide the download process, restart operations trigger automated execution, and file injection depends on decompression mechanisms, forming a closed-loop control system. This improves device availability, avoids device failure due to authorization verification failure, and ensures operational reliability through file integrity verification. This method effectively solves the authorization dilemma in legitimate user scenarios, combining practicality and security.

[0028] For example, in one embodiment of this application, the authorization verification method for an iOS device includes the following process: Step 1: Connect the device and communicate with Apple Mobile Device Service to obtain information such as system version and device model.

[0029] Step 2: Reboot the device, connect to the device's com.apple.os_trace_relay (system tracing relay service), and obtain the Books application's unique identifier (GUID), which is used to locate the file path on the device.

[0030] Step 3: Connect to the server. The server executes specific SQL to generate the downloads.28.sqlitedb file. The asset table stores the download addresses and device storage paths for the iTunesMetadata.plist, BLDatabaseManager.sqlite, BLDatabaseManager.sqlite-wal, and BLDatabaseManager.sqlite-shm files. BLDatabaseManager.sqlite is generated by specific SQL. The ZBLDOWNLOADINFO table stores the download address and device storage path for asset.epub. The asset.epub file is a zip archive generated by packaging the com.apple.MobileGestalt.plist and MIME type files. Upload the downloads.28.sqlitedb file to the / Downloads directory.

[0031] Step 4: Restart your device. The system will download the files stored in downloads.28.sqlitedb. After the download is complete, an iTunesMedadata.plist file will appear in the / iTunes_Control / iTunes directory. Copy the file to the / Books folder.

[0032] Step 5: Restart the device. The system will automatically download the asset.epub file. After the download is complete, the asset.epub file will appear in the / Books directory. The system will automatically decompress the asset.epub package and extract the com.apple.MobileGestalt.plist file contained within it to the specified directory, thus achieving the injection of system files.

[0033] Step 6: Restart the device. The com.apple.MobileGestalt.plist file will automatically take effect, thus completing the authorization verification of the iOS device.

[0034] Furthermore, in some embodiments of this application, the unique identifier of the e-book application on the iOS device is obtained by parsing the system service response, and is used to guide the determination of the subsequent file download path.

[0035] In some embodiments of this application, obtaining the globally unique identifier (GUID) of the e-book application on the iOS device is a crucial step in implementing the authorization verification process. This process is achieved by calling underlying system services (such as com.apple.os_trace_relay). For example, after a device restart, communication is established with the service, the response data returned by the system is parsed, and the unique identifier corresponding to the e-book application (e.g., the system's built-in "Books" application) is extracted. This identifier has a clear path-pointing characteristic in the iOS file system, providing the necessary path location basis for subsequent file downloads and injections.

[0036] Specifically, the system uses the acquired GUID to determine the sandbox path of the e-book application within the device, thereby guiding the download management database to determine the storage location of various resource files (such as metadata files, database management files, etc.) and ensuring that the compressed system configuration file can be accurately decompressed to the target directory. In this way, the iOS device authorization verification method provided in this application embodiment achieves accurate identification and access to system file paths without jailbreaking or modifying core system components, laying a technical foundation for subsequent authorization verification processing and improving the overall reliability and automation of the solution.

[0037] Furthermore, in some embodiments of this application, the step of creating a download management database file based on the system version and model information of the iOS device and the globally unique identifier of the e-book application, wherein the download management database file stores the download addresses and device storage paths of metadata files, database management files, write-ahead log files, and shared memory files, includes: Based on the iOS device's system version, model information, and the globally unique identifier of the e-book application, the download management database file is created using a structured query language script according to a database generation algorithm. The download management database file stores the download addresses and device storage paths of metadata files, database management files, write-ahead log files, and shared memory files.

[0038] In some embodiments of this application, the process of creating the download management database file demonstrates a high degree of adaptability and automation. Specifically, the system first integrates the obtained iOS device system version, model information, and globally unique identifier (GUID) of the e-book application as input parameters. The server dynamically executes a specific database generation algorithm based on these device characteristic information. The core of this algorithm lies in automatically constructing a lightweight database file—the download management database file (e.g., downloads.28.sqlitedb)—using a pre-built Structured Query Language (SQL) script.

[0039] This database file is not a simple data container, but a designed instruction set and path mapping table. Internally, it uses SQL scripts to create specific data table structures (such as the asset table) to systematically store and manage metadata for several key system files. These files include, but are not limited to: metadata files (such as iTunesMetadata.plist), database files that serve as the core management unit (such as BLDatabaseManager.sqlite), and auxiliary log files that ensure the integrity of database transactions—write-ahead log files (WAL files) and shared memory files (SHM files). The database file precisely records the network download address (URL) of each of the above files and its predetermined storage path within the iOS device.

[0040] The advantage of this design lies in its dynamic adaptability. Because the generated SQL script fully considers the differences in device models and system versions, it ensures that the file path ultimately written to the database perfectly matches the environment of the specific device, avoiding file injection failures due to incorrect paths. This step lays a solid foundation for the subsequent automated process, enabling the system to accurately guide the device to download the required files and place them in the correct location. It is one of the key technical aspects of achieving non-intrusive, automated authorization verification processing.

[0041] Furthermore, in some embodiments of this application, the structured query language script is dynamically generated based on the system version and model information of the iOS device, and adaptively generates database scripts containing the paths and download addresses of the metadata file, the database management file, the write-ahead log file, and the shared memory file.

[0042] Specifically, in some embodiments of this application, the generation process of the Structured Query Language (SQL) script possesses a high degree of dynamic adaptability. The server dynamically constructs and executes the corresponding SQL script based on the precise system version and specific model information of the obtained iOS device. This mechanism ensures that the generated download management database file accurately records resource information that perfectly matches the current device environment. Specifically, the script adaptively determines and writes the exact storage paths and corresponding network download addresses of metadata files, database management files, write-ahead log files, and shared memory files in the device's file system. Through this script generation logic strongly correlated with device information, subsequent operation failures caused by file path or resource version mismatches are effectively avoided, laying the foundation for the automation and reliability of the entire authorization verification process and demonstrating the flexibility and robustness of the solution design.

[0043] Furthermore, in some embodiments of this application, the database management file includes a download information table, which stores the download address and device storage path of the compressed file.

[0044] Specifically, in some embodiments of this application, the database management file dynamically generates its internal structure using a Structured Query Language (SQL) script. The download information table (ZBLDOWNLOADINFO table) contained in this file is the core control unit for the system's automated process. This table accurately records the network download address (URL) of the compressed file (asset.epub) and its target storage path within the iOS device (e.g., the / Books directory). Through this design, the system can automatically read the information in this table after restarting the device, triggering the download and storage of the compressed file without manual intervention in path configuration. This improves operational efficiency and avoids process interruptions due to incorrect paths, demonstrating the technological advantages of data-driven automation.

[0045] Furthermore, in some embodiments of this application, the compressed file is generated by packaging the system configuration file and media type file using a compression algorithm, and the iOS device's system automatically decompresses the compressed file to a specified directory.

[0046] Specifically, the compressed file is generated by packaging system configuration files (such as com.apple.MobileGestalt.plist) and media type files (such as MIME types) using a specific compression algorithm (such as ZIP format). Its file structure is optimized to ensure compatibility with iOS's automatic processing mechanisms. When a device downloads the compressed file, the system uses its built-in decompression function (such as the Books app's automatic parsing capability for EPUB format) to extract its contents to a designated directory (such as the system configuration area). This process relies on iOS's own file management features, ensuring system integrity while enabling silent injection of configuration files, providing the necessary foundation for subsequent authorization verification processing.

[0047] Furthermore, in some embodiments of this application, the system configuration file contains modified system configuration parameters to overwrite the original system file for authorization verification of the iOS device.

[0048] Specifically, the system configuration file contains modified system configuration parameters (such as device hardware identifiers or verification switch status). Its function is to enable the authorization verification process during device startup by overwriting the original system file (such as com.apple.MobileGestalt.plist in iOS). In particular, the modified parameters can cause the system to misjudge the device status (e.g., simulate a verified environment), thereby skipping the activation lock verification step. This file is injected into a critical system directory after decompression and is automatically loaded and activated by the system after a device restart. This mechanism does not require modification of the core system code; it achieves legitimate verification logic through resource replacement, balancing technical feasibility and operational security.

[0049] Figure 2 This is a structural block diagram of the authorization verification device 200 for an iOS device according to an embodiment of this application. Figure 2 As shown, the authorization verification device 200 for an iOS device according to this application embodiment includes: an information acquisition module 210, a file creation module 220, a file upload module 230, a file decompression module 240, and an authorization verification module 250, wherein: The information acquisition module 210 is used to acquire the system version, model information of the iOS device, and the globally unique identifier of the e-book application; The file creation module 220 is used to create a download management database file based on the system version and model information of the iOS device and the globally unique identifier of the e-book application. The download management database file stores the download addresses and device storage paths of metadata files, database management files, write-ahead log files, and shared memory files. The file upload module 230 is used to restart the iOS device and upload the download management database file to the download directory of the iOS device in the form of a compressed file. File decompression module 240 is used to restart the iOS device, download and decompress the compressed file, and inject the contained system configuration files into the system directory; and The authorization verification module 250 is used to finally restart the iOS device to make the injected system configuration file take effect, so as to perform authorization verification on the iOS device.

[0050] The iOS device authorization verification device provided in this application embodiment achieves efficient and non-intrusive device authorization management through multi-step collaborative processes. First, it obtains the device system version, model information, and the globally unique identifier (GUID) of the e-book application, providing accurate basis for subsequent file path location. Second, the server dynamically generates a Structured Query Language (SQL) script based on the above information, creating a download management database file (e.g., downloads.28.sqlitedb). This file integrates the download addresses and device storage paths of storage metadata files, database management files, and their auxiliary log files (write-ahead log files and shared memory files), ensuring a high degree of compatibility between resource configuration and the device environment. Next, by uploading the database file as a compressed package to the device's download directory and triggering a device restart, the system automatically downloads the specified file, achieving seamless file management. Finally, after restarting the device again, the system automatically downloads and decompresses the compressed package, injecting the contained system configuration file into the system directory, overwriting the original verification logic, making the configuration file effective, and thus completing the authorization verification. In the iOS device authorization verification method of this application embodiment, information acquisition lays the foundation for file generation, database files guide the download process, restart operations trigger automated execution, and file injection depends on decompression mechanisms, forming a closed-loop control system. This improves device availability, avoids device failure due to authorization verification failure, and ensures operational reliability through file integrity verification. This method effectively solves the authorization dilemma in legitimate user scenarios, combining practicality and security.

[0051] It should be noted that the specific implementation of the authorization verification device for the iOS device in this application embodiment is similar to the specific implementation of the authorization verification method for the iOS device in this application embodiment. Please refer to the description in the method section for details, which will not be repeated here.

[0052] Figure 3 This is a schematic diagram of the structure of the electronic device 300 according to an embodiment of this application.

[0053] like Figure 3 As shown, the electronic device 300 includes a central processing unit (CPU) 301, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 302 or a program loaded from the storage section 302 into a random access memory (RAM) 303. The RAM 303 also stores various programs and data required for the operation of the electronic device 300. The CPU 301, ROM 302, and RAM 303 are interconnected via a bus 304. An input / output (I / O) interface 305 is also connected to the bus 304.

[0054] The following components are connected to I / O interface 305: an input section 306 including a keyboard, mouse, etc.; an output section 307 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 308 including a hard disk, etc.; and a communication section 309 including a network interface card such as a LAN card, modem, etc. The communication section 309 performs communication processing via a network such as the Internet. A drive 310 is also connected to I / O interface 305 as needed. Removable media 311, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., are installed on drive 310 as needed so that computer programs read from them can be installed into storage section 308 as needed.

[0055] Specifically, according to embodiments of this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this application include a computer program product comprising a computer program carried on a machine-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 309, and / or installed from removable medium 311. When the computer program is executed by central processing unit (CPU) 301, it performs the functions defined in the electronic device of this application.

[0056] It should be noted that the computer-readable medium shown in this application may be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium may be, for example,—but not limited to—an electronic device, apparatus, or device that is electrical, magnetic, optical, electromagnetic, infrared, or semiconductor, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer 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.

[0057] In this application, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used or combined with an electronic device, apparatus, or device by instructions. In this application, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use or combined with an electronic device, apparatus, or device by instructions. The program code contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to: wireless, wireline, optical fiber, RF, etc., or any suitable combination thereof.

[0058] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of processing and receiving devices, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based electronic device that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0059] The units or modules described in the embodiments of this application can be implemented in software or hardware. The described units or modules can also be housed in a processor, which, when executing the program, implements the authorization verification method for the iOS device. Obtain the system version, model information, and globally unique identifier of the e-book application for the iOS device; Based on the iOS device's system version, model information, and the globally unique identifier of the e-book application, a download management database file is created. The download management database file stores the download addresses and device storage paths of metadata files, database management files, write-ahead log files, and shared memory files. Upload the download management database file as a compressed file to the download directory of the iOS device; and Download and decompress the compressed file, inject the contained system configuration file into the system directory, and make the injected system configuration file effective to perform authorization verification on the iOS device.

[0060] In another aspect, this application also provides a computer-readable storage medium, which may be included in the electronic device described in the above embodiments; or it may exist independently and not assembled into the electronic device. The aforementioned computer-readable storage medium stores one or more programs, which, when used by one or more processors, execute the authorization verification method for the iOS device described in this application: Obtain the system version, model information, and globally unique identifier of the e-book application for the iOS device; Based on the iOS device's system version, model information, and the globally unique identifier of the e-book application, a download management database file is created. The download management database file stores the download addresses and device storage paths of metadata files, database management files, write-ahead log files, and shared memory files. Upload the download management database file as a compressed file to the download directory of the iOS device; and Download and decompress the compressed file, inject the contained system configuration file into the system directory, and make the injected system configuration file effective to perform authorization verification on the iOS device.

[0061] In another aspect, this application also provides a computer program product, which may be included in the electronic device described in the above embodiments; or it may exist independently and not assembled into the electronic device. The computer program product stores one or more programs, which, when used by one or more processors, execute the authorization verification method for the iOS device described in this application: Obtain the system version, model information, and globally unique identifier of the e-book application for the iOS device; Based on the iOS device's system version, model information, and the globally unique identifier of the e-book application, a download management database file is created. The download management database file stores the download addresses and device storage paths of metadata files, database management files, write-ahead log files, and shared memory files. Upload the download management database file as a compressed file to the download directory of the iOS device; and Download and decompress the compressed file, inject the contained system configuration file into the system directory, and make the injected system configuration file effective to perform authorization verification on the iOS device.

[0062] The above description is merely a preferred embodiment of this application and does not limit the patent scope of this application. Any equivalent structural transformations made based on the content of this application's specification and drawings under the concept of this application, or direct / indirect applications in other related technical fields, are included within the patent protection scope of this application.

Claims

1. An authorization verification method for an iOS device, characterized in that, Includes the following steps: Obtain the system version, model information, and globally unique identifier of the e-book application for the iOS device; Based on the iOS device's system version, model information, and the globally unique identifier of the e-book application, a download management database file is created. The download management database file stores the download addresses and device storage paths of metadata files, database management files, write-ahead log files, and shared memory files. Upload the download management database file to the download directory of the iOS device in the form of a compressed file; and Download and decompress the compressed file, inject the contained system configuration file into the system directory, and make the injected system configuration file effective to perform authorization verification on the iOS device.

2. The method as described in claim 1, characterized in that, The unique identifier of the e-book application on the iOS device is obtained by parsing the system service response and is used to guide the determination of the subsequent file download path.

3. The method as described in claim 1, characterized in that, The step involves creating a download management database file based on the iOS device's system version, model information, and the globally unique identifier of the e-book application. This download management database file stores the download addresses and device storage paths of metadata files, database management files, write-ahead log files, and shared memory files, including: Based on the iOS device's system version, model information, and the globally unique identifier of the e-book application, the download management database file is created using a structured query language script according to a database generation algorithm. The download management database file stores the download addresses and device storage paths of metadata files, database management files, write-ahead log files, and shared memory files.

4. The method as described in claim 3, characterized in that, The structured query language script is dynamically generated based on the system version and model information of the iOS device, and adaptively generates database scripts containing the paths and download addresses of the metadata file, the database management file, the write-ahead log file, and the shared memory file.

5. The method as described in claim 4, characterized in that, The database management file includes a download information table, which stores the download address and device storage path of the compressed file.

6. The method as described in claim 1, characterized in that, The compressed file is generated by packaging the system configuration file and media type file using a compression algorithm, and the iOS device's system automatically decompresses the compressed file to a specified directory.

7. The method as described in claim 1, characterized in that, The system configuration file contains modified system configuration parameters, which are used to overwrite the original system files for authorization verification of the iOS device.

8. An authorization verification device for an iOS device, characterized in that, include: The information acquisition module is used to acquire the system version, model information of the iOS device, and the globally unique identifier of the e-book application; The file creation module is used to create a download management database file based on the system version and model information of the iOS device and the globally unique identifier of the e-book application. The download management database file stores the download addresses and device storage paths of metadata files, database management files, write-ahead log files, and shared memory files. The file upload module is used to upload the download management database file as a compressed file to the download directory of the iOS device. and The authorization verification module is used to load and decompress the compressed file, inject the contained system configuration file into the system directory, and finally restart the iOS device to make the injected system configuration file take effect for authorization verification of the iOS device.

9. An electronic device, characterized in that, It includes a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor is configured to implement the authorization verification method for an iOS device according to any one of claims 1-7 when executing the program.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program for implementing the authorization verification method for an iOS device according to any one of claims 1-7.

Images