Method and system for carrying out software batch management and recovery on remote mobile phone

Abstract

The invention relates to the technical field of mobile phone backup management, in particular to a software batch management and recovery method and system for a remote mobile phone, and the method comprises the steps: creating a web background, uploading a software package to the web background, analyzing the software package by the web background, and storing the analyzed data; the web background is remotely connected with the target equipment; installing the uploaded software package in the target equipment in a user-defined manner, recording an installation information record of the current equipment after successful installation, and recording the installation information to an installation record table; triggering an equipment software inspection flow, and executing timed snapshot backup; selecting a backup historical time node at a Web background, constructing a reference version set based on the installation record table, performing dual comparison with the current state of the equipment, and performing data rollback when versions are inconsistent or a target application is missing; cross-device batch management can be achieved through remote device operation, snapshot backup is automatically carried out, and a non-professional user can recover a specified time point through one key.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of mobile phone backup management, in particular to a method and system for batch management and recovery of software of remote mobile phones. BACKGROUND

[0002] Android system recovery scheme refers to a series of methods and tools for recovering or resetting Android devices, aiming to solve various problems encountered by the device, such as system crash, data loss, virus infection and software incompatibility.

[0003] Existing Android system recovery schemes rely on mobile phone manufacturer cloud backup, cannot roll back third-party application versions at time points, and the recovery process needs to be manually operated. Traditional ADB debugging tools need to be connected to the device locally and cannot achieve remote batch management.

[0004] The existing technology has three defects: 1. unable to establish an application version history library; 2. lack of cross-device remote control capability; 3. recovery operation needs to be performed by professional personnel, and the threshold for ordinary users is high. SUMMARY

[0005] In order to overcome the problems in the prior art that the Android system recovery scheme relies on mobile phone manufacturer cloud backup, cannot establish an application version history library, cannot remotely batch roll back application versions, lacks cross-device remote control capability, and has a high operation threshold, the purpose of the present application is to provide a method and system for batch management and recovery of software of remote mobile phones, which can remotely operate devices to achieve cross-device batch management, automatically take snapshots, and enable non-professional users to one-key restore at specified time points.

[0006] The present application adopts the following scheme to achieve:

[0007] A method for batch management and recovery of software of remote mobile phones, the method steps are as follows:

[0008] Step 1: create a web background, upload software packages to the web background, the web background parses the software packages and stores the parsed data;

[0009] Step 2: the web background remotely connects with the target device, performs remote binding and authentication of the target device;

[0010] Step 3: install the software package in step 1 in the connected target device, record the installation information of the current device after success, and record the installation information to the installation record table;

[0011] Step 4: trigger the device software inspection process, perform set difference operation on the current device application list and the installation record table through the database transaction mechanism, and execute timed snapshot backup;

[0012] Step 5: Select the backup history time node in the web background, build a benchmark version set based on the installation record table, and perform a double comparison with the current state of the device. When the version is inconsistent or the target application is missing, data rollback is performed.

[0013] Further, step 1 is specifically: after uploading the software package, the file is encrypted and stored in the specified path, and the aapt command of the Android SDK is automatically triggered to parse the installation package metadata, and the returned information is obtained and a unique constraint is established.

[0014] The application name, package name, version number, and encrypted storage path of the returned information are written into the package management table. The package management table structure includes an auto-increment primary key id, name app_name, unique identifier package_name, internal version number version_code, external version number version_name, encrypted storage path storage_path, record generation time create_time, and last update time update_time.

[0015] Further, step 2 is further specifically: connect the target device through ADB over TCP protocol, collect the device serial number, MAC address and Android version number, generate the device fingerprint through SHA-256 hash operation, store it in the device table and establish a unique identifier.

[0016] Further, step 3 is further specifically: the installation information record includes installation records, saving device id, package id and installation time.

[0017] Further, step 4 is further specifically: obtain the current application list of the device every day, and perform multi-dimensional comparison between the current device application list and the installation record table through database transaction mechanism. First, extract the unique identifier package_name field in the installation record table for the device in the last few days according to the time dimension to form a benchmark set. Then, perform a difference set operation between the obtained real-time package name set and the benchmark set. For newly appeared application packages, automatically search for the latest version record of the same unique identifier package_name in the package management table. If there is a version same entry, a new discovered installation record is supplemented in the installation record table, and the create_time record generation time is the current system time. If no matching is found, the difference item is automatically ignored, the application version record is added, and the last update time update_time of the device is updated.

[0018] Further, step 5 is further specified as follows: first, locking the target device ID, then grouping and screening the installation records of the latest version before the current time point, constructing a benchmark version set, and performing double comparison with the benchmark version set by obtaining the current application state data of the device; when detecting that the application version number is inconsistent or the target application is missing, triggering the rollback condition to generate an operation instruction sequence, the operation instruction sequence executing the command of uninstalling the application and retaining its data and cache files for the application to be downgraded, and then locating the historical version installation package according to the package management table storage path field and issuing the command of silent overlay installation; for the missing application of the device, directly executing the installation operation;

[0019] The recovery process is provided with a whitelist filtering mechanism, and the user can generate an exclusion list by checking the unique identifier package_name, so that the software with the same package_name in the exclusion list is ignored during the execution of the recovery, thereby realizing the accurate space-time restoration of the device software ecology.

[0020] A system for remotely managing and restoring software in batches, the system comprising: a software package processing module, a device connection module, a software package installation module, a data backup module, and a data rollback module;

[0021] The software package processing module is configured to create a web background, upload software packages to the web background, parse the software packages by the web background, and store the parsed data;

[0022] The device connection module is configured to remotely connect the web background to a target device, and perform remote binding and authentication of the target device;

[0023] The software package installation module is configured to install the software packages in the software package processing module in the connected target device, record the installation information of the current device after successful installation, and record the installation information to an installation record table;

[0024] The data backup module is configured to trigger a device software inspection process, perform a difference set operation on the current device application list and the installation record table by a database transaction mechanism, and perform a timed snapshot backup;

[0025] The data rollback module is configured to select a backup historical time node in the web background, construct a benchmark version set based on the installation record table, and perform double comparison with the current state of the device; when the versions are inconsistent or the target application is missing, data rollback is performed.

[0026] Further, the software package processing module is configured to: after uploading the software package, storing the file in an encrypted manner to a specified path, automatically triggering an aapt command of an Android SDK to parse the installation package metadata, obtaining return information, and establishing a unique constraint;

[0027] The application name, package name, version number, and encrypted storage path are written into a package management table, and the table structure includes an auto-increment primary key id, name app_name, unique identifier package_name, internal version number version_code, external version number version_name, encrypted storage path storage_path, record generation time create_time, and last update time update_time.

[0028] Further, the device connection module is further specific to: connecting the target device through ADB over TCP protocol, collecting device serial number, MAC address and Android version number, generating device fingerprint through SHA-256 hash operation of the three, storing to the device table and establishing a unique identifier.

[0029] Further, the software package installation module is further specific to: the installation information record includes an installation record, saving device id, package id and installation time.

[0030] Further, the data backup module is further specific to: obtaining the current application list of the device every day, and performing multi-dimensional comparison between the current device application list and the installation record table through a database transaction mechanism, first extracting the unique identifier package_name field in the installation record table of the device in the recent days to form a reference set, then performing set difference operation between the obtained real-time package name set and the reference set, for the newly appeared application package, automatically searching the latest version record of the same unique identifier package_name in the package management table, if there is a same version entry, a new found installation record is supplemented in the installation record table, and the create_time record generation time is the current system time; if no matching is found, the difference item is automatically ignored, the application version record is added, and the last update time update_time of the device is updated.

[0031] Further, the data rollback module is further specific to: first locking the target device ID, then grouping and screening the latest version installation record before the current time point according to the unique identifier package_name, constructing a reference version set, and performing double comparison between the current application state data of the device and the reference version set: when detecting that the application version number is inconsistent or the target application is missing, triggering the rollback condition to generate an operation instruction sequence, the operation instruction sequence executes the command of uninstalling the application and retaining the data and cache file of the application for the application to be downgraded, then locating the historical version installation package according to the storage path field of the package management table, and issuing the command of silent overlay installation; for the missing application of the device, the installation operation is directly executed;

[0032] The recovery process is provided with a whitelist filtering mechanism, and a user can generate an exclusion list by checking a unique identifier package_name, and when performing recovery, the software with the same package_name in the exclusion list is ignored, so that the accurate space-time restoration of the device software ecology is realized.

[0033] The present application has the following advantages:

[0034] The present application provides a method and system for batch management and recovery of software by remote mobile phone, which realizes cross-device batch management by combining remote device operation based on ADBover TCP protocol; a timing snapshot backup mechanism and a transaction comparison algorithm are used to automatically generate incremental backup and support visual time axis rollback, and by means of data degradation reservation and whitelist filtering mechanism, non-professional users can one-key restore the software ecology at a specified time point. BRIEF DESCRIPTION OF DRAWINGS

[0035] Figure 1 The present application provides a method and system for batch management and recovery of software by remote mobile phone, which realizes cross-device batch management by combining remote device operation based on ADBover TCP protocol; a timing snapshot backup mechanism and a transaction comparison algorithm are used to automatically generate incremental backup and support visual time axis rollback, and by means of data degradation reservation and whitelist filtering mechanism, non-professional users can one-key restore the software ecology at a specified time point.

[0036] Figure 2 The present application provides a method and system for batch management and recovery of software by remote mobile phone, which realizes cross-device batch management by combining remote device operation based on ADBover TCP protocol; a timing snapshot backup mechanism and a transaction comparison algorithm are used to automatically generate incremental backup and support visual time axis rollback, and by means of data degradation reservation and whitelist filtering mechanism, non-professional users can one-key restore the software ecology at a specified time point. DETAILED DESCRIPTION

[0037] The present application will be further described below in conjunction with the drawings.

[0038] Reference Figure 1 A method for batch management and recovery of software by remote mobile phone, the method steps are as follows:

[0039] Step 1: create a web background, upload software packages to the web background, the web background parses the software packages, and stores the parsed data;

[0040] Step 2: the web background is remotely connected with the target device, and the target device remote binding and authentication are performed;

[0041] Step 3: install the software package in step 1 in the connected target device, record the installation information of the current device after success, and record the installation information to the installation record table;

[0042] Step 4: trigger the device software inspection process, and perform set difference operation on the current device application list and the installation record table through the database transaction mechanism to execute timing snapshot backup;

[0043] Step 5: select the backup history time node in the web background, build a reference version set based on the installation record table, and perform double comparison with the current state of the device, and when the versions are inconsistent or the target application is missing, data rollback is performed.

[0044] The present application will be further described below in conjunction with the drawings.

[0045] A method for remote mobile phone software batch management and recovery, the method comprising the following steps:

[0046] Step 1, intelligent analysis and storage of software package

[0047] The APK intelligent analysis and storage process is realized by modular design: after the user enters the "software management" interface from the web background, inputs the software name (such as "software A") and uploads the APK file, the file is encrypted and stored in the specified path (such as / data / repo / upload / 2024 / 0125 / com.example.app_1.2.3.apk), and the aapt command (aapt dump badging / data / repo / upload / 2024 / 0125 / com.example.app_1.2.3.apk) of the Android SDK is automatically triggered to analyze the installation package metadata, and the returned information package:name='com.example.app'versionCode='123'versionName='1.2.3' is obtained, that is, the package name (com.example.app), version number (1.2.3), SDK version and other key information are obtained, and these data are written into the package management table (package_manager) synchronously with the user information. The table uses a composite data structure, and the application name, package name, version number, and encrypted storage path are written into the package management table. The table structure includes an auto-increment primary key id, a name app_name, a unique identifier package_name, an internal version number version_code, an external version number version_name, an encrypted storage path storage_path, a record generation time create_time, and a last update time update_time. The (package_name, version_name) unique constraint prevents duplicate versions from being uploaded.

[0048]

[0049] Step 2, device remote binding and authentication

[0050] The user enters the "mobile management" interface from the web background, inputs the device IP, such as 192.168.1.100, establishes a remote connection through the Android ADB over TCP protocol, first executes the adb tcpip 5555 command on the mobile side to open the network debugging port, and then connects the target device through adb connect 192.168.1.100:5555. After successful connection, the chain ADB command adb-s 192.168.1.100:5555 shell "echo serial number: $(getprop ro.serialno); echo MAC address: $(cat / sys / class / net / wlan0 / address); echo Android version: $(getpropro.build.version.release)" is called to collect the device serial number (such as HT9A0A901234), wireless network card physical address (such as e4:50:eb:32:7a:c9), and version (such as Android 13), which are spliced to generate a unique device fingerprint (such as a3f8c7...9d2b1) through the SHA-256 hashing algorithm as a unique index to prevent duplication. All device information is stored in the database mobile table, which has the following structure.

[0051]

[0052]

[0053] Step 3, Remote installation of software and record tracking

[0054] The user enters the "device installation" interface from the web background, enters from the device bound in step 2, displays the software package uploaded in step 1, selects the target application to be installed, and generates the complete ADB installation command: adb-s 192.168.1.100:5555 install-r / data / repo / upload / 2024 / 0125 / com.example.app_1.2.3.apk. The -s parameter specifies the target device IP and port, and install-r indicates that the installation is performed with data retention. After successful installation, the installation record of the current device is recorded, and the device id, package id, and installation time are saved to the installation record table. The complete table structure is as follows:

[0055]

[0056]

[0057] Step 4: Daily trigger the device software inspection process automatically through the preset task scheduling module, obtain structured application list data based on the adb-s[device address] shell pm list packages--show-versioncode command (example output: package: com.tencent.mm versionCode: 1850; package: com.example.app versionCode: 123). Through the database transaction mechanism, compare the current device application list with the installation record table (install_records) in multiple dimensions: first, extract all unique identifiers package_name fields in the installation record table within the last 30 days for the device to form a reference set according to the time dimension, then perform a difference set operation between the real-time package name set obtained by ADB and the reference set according to the package name dimension, and for newly appeared application packages (such as detecting a new com.ss.android.ugc.aweme version number 456), automatically retrieve the latest version record of the same unique identifier package_name in the package management table (package_manager), if there is an entry with the same version, then generate a new installation record found in the installation record table (obtain structured application list data based on the adb-s[device address] shell pm list packages--show-versioncode command), and the create_time field takes the current time; if no match is found, automatically ignore the difference item. Compare the dates through the last_backup_date field of the device table to ensure that each device performs a full snapshot backup only once a day, and if the device detects that the daily backup flag already exists, it automatically skips the execution process.

[0058] Snapshot backup is a prior art technology that achieves data protection by creating a transient copy of a storage volume, with core advantages such as second-level creation, low resource consumption, fast recovery, and is widely used in database, virtualization, and cloud platform scenarios.

[0059] Step 5: After the user selects a historical time node in the "Recovery Management" interface of the web background, a data query is performed in the installation record table based on the timestamp: first, the target device ID is locked, then the latest version installation record before the current time point is grouped and filtered according to the package_name field, and a reference version set is constructed. The current application state data of the device is obtained through the adb-s 192.168.1.100:5555 shell pm list packages--show-versioncode command, and a double comparison is performed with the reference set - when the application version number is detected to be inconsistent (such as the existing com.example.app version number on the device is 2.0.0, and the historical reference is 1.2.3), or the target application is missing (such as com.company.app in the reference record does not appear in the device list), the rollback condition generation operation instruction sequence is triggered: the adb-s 192.168.1.100:5555 uninstall-k com.example.app command is executed for the application to be downgraded (-k parameter retains application data), and then the historical version installation package is located according to the package management table storage path field, and the adb-s 192.168.1.100:5555 install-r / data / repo / upload / 2024 / 0125 / com.example.app_1.2.3.apk silent override installation is initiated; for the missing application on the device, the installation operation is directly executed. The recovery process has a built-in whitelist filtering mechanism, and the user can generate an exclusion list by checking the unique identifier package_name (such as excluding com.ss.android.ugc.aweme), and when performing recovery, the software with the same package name in the exclusion list will be ignored, finally achieving precise spatiotemporal restoration of the device software ecosystem.

[0060] A system for remotely managing and restoring software in batches, the system comprising: a software package processing module, a device connection module, a software package installation module, a data backup module, and a data rollback module;

[0061] The software package processing module is used to create a web background, upload software packages to the web background, parse the software packages by the web background, and store the parsed data;

[0062] The device connection module is used to remotely connect the web background to the target device, and perform remote binding and authentication of the target device;

[0063] The software package installation module is used to install the software package in the software package processing module in the connected target device, record the installation information of the current device after successful installation, and record the installation information to the installation record table;

[0064] The data backup module is used for triggering a device software inspection process, performing a difference set operation on a current device application list and an installation record table through a database transaction mechanism, and executing a timing snapshot backup.

[0065] The data rollback module is used for selecting a backup history time node in a Web background, constructing a benchmark version set based on the installation record table, performing a double comparison with a current device state, and performing data rollback when the versions are inconsistent or target applications are missing.

[0066] In an embodiment of the application, the software package processing module specifically comprises: after uploading a software package, storing a file in an encrypted manner to a specified path, automatically triggering an aapt command of an Android SDK to analyze an installation package metadata, obtaining return information, and establishing a unique constraint.

[0067] The application name, package name, version number and encrypted storage path are written into a package management table, and the table structure comprises a self-incrementing primary key id, a name app_name, a unique identifier package_name, an internal version number version_code, an external version number version_name, an encrypted storage path storage_path, a record generation time create_time and a last update time update_time.

[0068] In an embodiment of the application, the device connection module is further specifically: connecting a target device through an ADB over TCP protocol, collecting a device serial number, a MAC address and an Android version number, generating a device fingerprint through SHA-256 hash operation of the three, storing the device fingerprint into a device table and establishing a unique identifier.

[0069] In an embodiment of the application, the software package installation module is further specifically: the installation information record comprises an installation record, saving a device id, a package id and an installation time.

[0070] In an embodiment of the application, the data backup module is further specifically: obtaining a current application list of a device every day, performing a multi-dimensional comparison between the current device application list and an installation record table through a database transaction mechanism, first extracting a unique identifier package_name field in the installation record table in the latest several days of the device according to a time dimension to form a benchmark set, then performing a difference set operation between a real-time package name set obtained and the benchmark set according to a package name dimension, automatically searching a latest version record of the same unique identifier package_name in a package management table for a newly appeared application package, if there is a same version entry, then a new found installation record is supplemented and generated in the installation record table, and a create_time record generation time is taken as a current system time; if no matching is performed, then a difference item is automatically ignored, a new application version record is added and a last update time update_time of the device is updated.

[0071] In one embodiment of the present application, the data rollback module is specifically: first locking the target device ID, then grouping and screening the installation records of the latest version before the current time point according to the unique identifier package_name, constructing a reference version set, and through obtaining the current application state data of the device, performing double comparison with the reference version set: when detecting that the application version number is inconsistent or the target application is missing, triggering the rollback condition to generate an operation instruction sequence, the operation instruction sequence executes the command of uninstalling the application and retaining the data and cache file of the application for the application to be downgraded, and then according to the package management table storage path field, locating the historical version installation package, and issuing the command of silent overlay installation; for the missing application of the device, directly executing the installation operation;

[0072] The recovery process is built-in with a whitelist filtering mechanism, and the user can generate an exclusion list by checking the unique identifier package_name. When the recovery is executed, the software with the same package_name in the exclusion list will be ignored, so as to realize the accurate space-time restoration of the device software ecology.

[0073] The above only describes the preferred embodiments of the present application, and any changes and modifications made within the scope of the present application should be included in the scope of the present application.

Claims

1. A method for remotely managing and restoring software batches on a mobile phone, characterized in that: The method steps are as follows: Step 1: Create a web backend, upload the software package to the web backend, and the web backend parses the software package and stores the parsed data; Step 2: The web backend remotely connects to the target device to perform remote binding and authentication of the target device; Step 3: Install the software package described in step 1 on the connected target device. If successful, record the installation information of the current device and save the installation information to the installation record table. Step 4: Trigger the device software inspection process, perform a difference operation on the current device application list and the installation record table through the database transaction mechanism, and perform a scheduled snapshot backup; Step 5: Select the historical time node for backup in the web backend, build a baseline version set based on the installation record table, and compare it with the current status of the device. If the versions are inconsistent or the target application is missing, roll back the data.

2. The method for remotely managing and restoring software batches on a mobile phone according to claim 1, characterized in that: Step 1 specifically involves: after uploading the software package, encrypting the file and storing it in the specified path, automatically triggering the Android SDK's aapt command to parse the installation package metadata, obtain the returned information, and establish a unique constraint; The application name, package name, version number, and encrypted storage path of the returned information are written into the package management table. The package management table structure includes the auto-increment primary key id, the name app_name, the unique identifier package_name, the internal version number version_code, the external version number version_name, the encrypted storage path storage_path, the record generation time create_time, and the last update time update_time.

3. The method for remotely managing and restoring software batches on a mobile phone according to claim 1, characterized in that: Step 2 is further specified as follows: connect to the target device via the ADB over TCP protocol, collect the device serial number, MAC address, and Android version number, perform a SHA-256 hash operation on the three, generate a device fingerprint, store it in the device table, and establish a unique identifier.

4. The method for remotely managing and restoring software batches on a mobile phone according to claim 1, characterized in that: Step 3 is further specified as follows: the installation information record includes an installation record, which stores the device ID, package ID and installation time.

5. The method for remotely managing and restoring software batches on a mobile phone according to claim 2, characterized in that: Step 4 is further specified as follows: daily obtain the device's current application list, perform a multi-dimensional comparison between the current device application list and the installation record table through the database transaction mechanism, first extract the unique identifier package_name field of the device in the installation record table in the last few days according to the time dimension to form a benchmark set, and then perform a difference operation with the obtained real-time package name set according to the package name dimension. For newly appeared application packages, automatically retrieve the latest version record of the same unique identifier package_name in the package management table. If there is an entry with the same version, a newly discovered installation record is generated in the installation record table, and the create_time record generation time is the current system time; if no match is found, the difference item is automatically ignored, a new application version record is added, and the device's last update time update_time is updated.

6. The method for remotely managing and restoring software batches on a mobile phone according to claim 2, characterized in that: Step 5 is further specified as follows: first, the target device ID is locked, then the installation records of the latest version before the current time point are grouped by the unique identifier package_name and filtered to construct a baseline version set. The current application status data of the device is obtained and double-compared with the baseline version set: when an inconsistent application version number or the target application is missing is detected, a rollback condition is triggered to generate an operation instruction sequence, which executes a command to uninstall the application to be downgraded while retaining its data and cache files, then locates the historical version installation package according to the storage path field of the package management table, and initiates a silent overwrite installation command; if the device lacks the application, the installation operation is directly executed; The recovery process has a built-in whitelist filtering mechanism. Users can generate an exclusion list by checking the unique identifier package_name. When performing recovery, software with the same package name in the exclusion list will be ignored, achieving accurate temporal and spatial restoration of the device software ecosystem.

7. A system for remotely managing and restoring software batches on mobile phones, characterized in that: The system includes: a software package processing module, a device connection module, a software package installation module, a data backup module and a data rollback module; The software package processing module is used to create a web backend, upload the software package to the web backend, and the web backend parses the software package and stores the parsed data; The device connection module is used to remotely connect the web backend with the target device and perform remote binding and authentication of the target device; The software package installation module is used to install the software package described in the software package processing module in the connected target device, and after success, record the installation information record of the current device and record the installation information in the installation record table; The data backup module is used to trigger the device software inspection process, perform a difference set operation on the current device application list and the installation record table through the database transaction mechanism, and perform a scheduled snapshot backup; The data rollback module is used to select a historical time node for backup in the Web background, build a baseline version set based on the installation record table, and perform a double comparison with the current status of the device. When the versions are inconsistent or the target application is missing, the data is rolled back.

8. A system for remotely managing and restoring software batches on mobile phones according to claim 7, characterized in that: The software package processing module specifically: after uploading the software package, it encrypts the file and stores it in the specified path, automatically triggers the Android SDK's aapt command to parse the installation package metadata, obtains the return information, and establishes a unique constraint; Write the application name, package name, version number, and encrypted storage path into the package management table. The table structure includes the auto-increment primary key id, the name app_name, the unique identifier package_name, the internal version number version_code, the external version number version_name, the encrypted storage path storage_path, the record generation time create_time, and the last update time update_time.

9. The system for remotely managing and restoring software batches on mobile phones according to claim 7, characterized in that: The device connection module is further specified as follows: connecting to the target device through the ADB over TCP protocol, collecting the device serial number, MAC address and Android version number, and performing a SHA-256 hash operation on the three to generate a device fingerprint, which is stored in the device table and establishes a unique identifier.

10. The system for remotely managing and restoring software batches on mobile phones according to claim 7, characterized in that: The software package installation module is further specified as follows: the installation information record includes an installation record, which stores the device ID, package ID and installation time.

11. The system for remotely managing and restoring software batches on mobile phones according to claim 8, characterized in that: The data backup module is further specified as follows: daily acquisition of the device's current application list, multi-dimensional comparison of the current device application list with the installation record table through the database transaction mechanism, first extracting the unique identifier package_name field of the device in the installation record table within the last few days according to the time dimension to form a baseline set, and then performing a difference operation with the obtained real-time package name set according to the package name dimension. For newly appearing application packages, the latest version record of the same unique identifier package_name in the package management table is automatically retrieved. If there is an entry with the same version, a newly discovered installation record is generated in the installation record table, and the create_time record generation time is the current system time; if no match is found, the difference item is automatically ignored, and the new application version record is added and the device's last update time update_time is updated.

12. The system for remotely managing and restoring software batches on mobile phones according to claim 8, characterized in that: The data rollback module is further specified as follows: first, the target device ID is locked, then the installation records of the latest version before the current time point are grouped by the unique identifier package_name and filtered to construct a baseline version set. The current application status data of the device is then double-compared with the baseline version set. When an inconsistent application version number or missing target application is detected, the rollback condition is triggered to generate an operation instruction sequence. The operation instruction sequence executes a command to uninstall the application to be downgraded while retaining its data and cache files. The historical version installation package is then located according to the storage path field of the package management table and a silent overwrite installation command is initiated. If the device has missing applications, the installation operation is directly executed. The recovery process has a built-in whitelist filtering mechanism. Users can generate an exclusion list by checking the unique identifier package_name. When performing recovery, software with the same package name in the exclusion list will be ignored, achieving accurate temporal and spatial restoration of the device software ecosystem.

Images