Mobile terminal data intelligent backup method and device, mobile terminal and storage medium

Abstract

The invention relates to the technical field of data processing, in particular to a mobile terminal data intelligent backup method and device, a mobile terminal and a storage medium. The mobile terminal data intelligent backup method comprises the steps that when a preset triggering condition is monitored, such as an NFC label approaching event and / or at least one additional triggering condition, safety verification is executed, and a backup task is triggered if verification is passed. Wherein the NFC label is only used for waking up the backup application program of the mobile terminal. And after a backup task triggering instruction is received, writing the to-be-backed-up data into the external storage device successfully connected with the mobile terminal according to the intelligent backup strategy. According to the data backup method and device, intelligent triggering is achieved through the NFC near field sensing characteristic, the expansion requirement of the external storage device is considered, backup can be conducted according to the intelligent backup strategy, the personalized backup requirement under the complex scene is met, and the convenience and applicability of data backup are improved.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and in particular to a method, apparatus, mobile terminal, and storage medium for intelligent data backup of mobile terminals. Background Technology

[0002] With the widespread adoption of mobile devices such as smartphones and tablets, the amount of data they store has exploded, encompassing various important information including photos, text messages, contacts, and documents. To prevent data loss and ensure data security and availability, data backup technology has become crucial. Currently, there are various data backup methods, including cloud backup, local wired backup, and backup based on wireless communication technology. Among these, data backup technology based on Near Field Communication (NFC) is gradually gaining attention due to its convenience and speed.

[0003] Existing data backup methods utilize the NFC Handover protocol to establish a data transmission channel between two terminals, such as a Wi-Fi P2P connection. Various types of data from the first terminal, such as photos, SMS messages, and contacts, are transmitted to the second terminal for backup via this established channel. The receiving end automatically imports this data, thus achieving the purpose of switching devices or data migration. However, these existing data backup methods have the following significant limitations: First, NFC is only used as a static data transmission link initialization tool, failing to deeply integrate its near-field sensing characteristics with backup triggering logic. This requires users to manually initiate the transmission process, making it impossible to leverage NFC's instant interaction capabilities for intelligent triggering. Second, the application scenarios are highly focused on cross-device data migration, neglecting the expansion needs of mobile terminal's local external storage devices (such as USB flash drives, SSDs, and dedicated storage cases), making them unsuitable when local storage capacity is insufficient or offline backup is required. Third, they lack diverse triggering conditions and dynamic policy control mechanisms, supporting only a single transmission path. They cannot automatically adjust the backup timing and scope based on user behavior patterns (such as charging status, network environment, and geographical location) or device status (such as storage space and battery level), making it difficult to meet personalized backup needs in complex scenarios. Summary of the Invention

[0004] To overcome the shortcomings of the prior art, the present invention provides a method, device, mobile terminal and storage medium for intelligent backup of mobile terminal data. It utilizes the near-field sensing characteristics of NFC to achieve intelligent triggering, takes into account the expansion needs of external storage devices, and has diverse triggering conditions and intelligent backup strategies to meet the personalized backup needs of complex scenarios.

[0005] A first aspect of this application provides a method for intelligent backup of mobile terminal data, the method comprising: When a preset trigger condition is detected, a security verification operation is performed to determine if the verification passes and trigger the backup task execution. The preset trigger condition includes an NFC tag proximity event and / or at least one additional trigger condition. The NFC tag serves as a trigger signal and is only used to wake up the backup application on the mobile terminal. When a backup task trigger instruction is received, the data to be backed up is written to an external storage device according to the intelligent backup strategy, and the external storage device has been successfully connected to the mobile terminal.

[0006] In an optional implementation, the presence of at least one additional triggering condition is detected, the additional triggering condition being selected from any one or a combination of the following: voice command input event, USB / external storage device insertion or mounting event, power access status change event, Wi-Fi network switching event, timed task triggering event, geofencing triggering event, Bluetooth device connection status change event, and sensor data anomaly event.

[0007] In one optional implementation, the security verification operation includes at least one of domain name verification, NDEF content verification, UID whitelist verification, digital signature verification, password protection verification, two-factor authentication verification, dual-mode condition verification, or other security verification.

[0008] In one optional implementation, the intelligent backup strategy includes at least one of an incremental backup strategy, a conditional filtering strategy, an intelligent scheduling strategy, or an adaptive learning strategy.

[0009] In an optional implementation, the mobile terminal data intelligent backup method further includes: When the first installation command of the backup application is detected, an NFC tag registration function is provided so that the user can bring the NFC tag to be associated close to the mobile terminal to trigger the tag information reading operation; When it is determined that the NFC tag to be associated has completed the binding registration with the backup application, the tag information of the NFC tag is securely stored in the local database so that when an NFC tag proximity event is received, a security verification operation is performed based on the tag information.

[0010] In an optional implementation, the mobile terminal data intelligent backup method further includes: When an NFC tag proximity event is detected, the user is authenticated using Face ID or Touch ID; Once identity verification is confirmed and the current mobile terminal is not on the enterprise whitelist or signature verification fails, the backup task will be executed after waiting for further user action. Once identity verification is successful and the current mobile terminal is on the enterprise whitelist or has passed signature verification, the automatic execution mode is enabled to directly execute the backup task.

[0011] In an optional implementation, the mobile terminal data intelligent backup method further includes: Visualize the backup progress of the backup data while the backup task is in execution state; When the backup task is in a completed state, the system will visualize whether the backup was successful or failed.

[0012] A second aspect of this application provides a mobile terminal data intelligent backup device, the mobile terminal data intelligent backup device comprising: The trigger module is used to perform a security verification operation when a preset trigger condition is detected to determine whether the backup task will be executed when the verification is successful; the preset trigger condition includes an NFC tag proximity event and / or at least one additional trigger condition; the NFC tag serves as a trigger signal and is only used to wake up the backup application on the mobile terminal; The backup module is used to write the data to be backed up to an external storage device according to the intelligent backup strategy when a backup task trigger instruction is received. The external storage device has been successfully connected to the mobile terminal.

[0013] A third aspect of this application provides a mobile terminal, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the mobile terminal data intelligent backup method.

[0014] A fourth aspect of this application provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the steps of the above-described intelligent backup method for mobile terminal data.

[0015] In summary, the mobile terminal data intelligent backup method, apparatus, mobile terminal, and storage medium provided in this application have at least one of the following beneficial effects: 1. Using NFC tag proximity events as one of the preset trigger conditions, a security verification operation is performed when an NFC tag proximity event is detected. After successful verification, the backup task is triggered. Furthermore, the NFC tag is only used to wake up the backup application on the mobile terminal, deeply integrating the near-field sensing characteristics of NFC with the backup triggering logic. This leverages the real-time interaction capabilities of NFC to achieve intelligent triggering, eliminating the need for users to manually initiate the transmission process. 2. When this application receives a backup task trigger instruction, it writes the data to be backed up to the external storage device that has been successfully connected to the mobile terminal according to the intelligent backup strategy. This fully considers the expansion needs of the mobile terminal's local external storage device. When the local storage capacity is insufficient or offline backup is required, the data can be backed up to the external storage device, thus expanding the applicability of the application scenarios. 3. Preset trigger conditions include NFC tag proximity events and / or at least one additional trigger condition, providing diverse trigger conditions; at the same time, according to the intelligent backup strategy, the data to be backed up is written to the external storage device to meet the personalized backup needs in complex scenarios. Attached Figure Description

[0016] Figure 1 This is a flowchart illustrating a method for intelligent backup of mobile terminal data according to an embodiment of this application; Figure 2 This is a functional block diagram of a mobile terminal data intelligent backup device shown in an embodiment of this application; Figure 3 This is a schematic diagram of the structure of a mobile terminal shown in an embodiment of this application. Detailed Implementation

[0017] The present invention will be further described below with reference to the accompanying drawings and embodiments.

[0018] The following will clearly and completely describe the concept, specific structure, and technical effects of the present invention in conjunction with embodiments and accompanying drawings, so as to fully understand the purpose, features, and effects of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, not all of them. Other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative effort are all within the scope of protection of the present invention. Furthermore, all connections / linkages involved in the patent do not simply refer to direct contact between components, but rather to the ability to form a better connection structure by adding or reducing connecting accessories according to specific implementation conditions. The various technical features in this invention can be combined interactively without contradicting each other.

[0019] Reference Figure 1 The diagram shown is a flowchart illustrating a mobile terminal data intelligent backup method according to an embodiment of this application. The mobile terminal data intelligent backup method includes the following steps.

[0020] S11, when a preset trigger condition is detected, a security verification operation is performed to determine if the verification passes and the backup task is triggered.

[0021] The preset triggering conditions include an NFC tag proximity event and / or at least one additional triggering condition; the NFC tag, as a trigger signal, is only used to wake up the backup application on the mobile terminal.

[0022] Compared to using NFC as a data channel, this application uses the NFC tag only as a trigger signal (not a data channel). Sensitive data is transmitted through a controlled local interface (USB-C / Lightning / UIDocumentPicker), reducing the risk of wireless transmission exposure and man-in-the-middle attack surface. It has higher compatibility and stability. After being woken up, the application uses the system API to handle backup in a controlled environment, avoiding problems caused by relying on the other party's device or peer-to-peer connections. It can achieve a controllable user experience. After being woken up, the complete UI can be displayed, avoiding the uncontrollable experience when transferring large files through the NFC data channel. It is low-cost and easy to deploy. It only requires a low-cost NTAG tag on the phone case and the relevant logic to be implemented in the App. The R&D and certification costs are far lower than MFi or proprietary protocols. It can also be expanded into a "multi-trigger fusion" system, combined with various trigger conditions to enhance robustness and scenario coverage.

[0023] To facilitate understanding of the inventive concept of this application, the embodiments of this application use NFC tags as trigger conditions so that when a mobile terminal (e.g., a user's mobile phone) is close to any NFC-enabled item (bus card, access control), the system may recognize the NDEF / UID, thereby waking up the backup application of the mobile terminal to perform a backup action. The backup application (hereinafter referred to as the App) supports NFC tag interaction. The App provides a "Register NFC Tag (optional)" function upon first installation to securely store the tag UID or signature information for subsequent authentication.

[0024] In addition to using NFC tags as trigger conditions, other additional trigger conditions are also supported. These additional trigger conditions can include voice command input events (such as "Hey Siri, start backup"), manual button triggering within the app, USB / external storage device insertion (such as microcontroller signal monitoring) or mounting events, power connection status change events, Wi-Fi network switching events, scheduled task triggering events, geofencing triggering events, Bluetooth device connection status change events, physical button triggering events, and sensor data anomaly events (such as automatic execution if the phone has been stationary for more than one hour). Users can select or combine different trigger events according to their actual usage scenarios, thus providing a more flexible backup startup mechanism.Specifically, for voice command input events, by integrating the system's voice assistant interface, when the user's hands are occupied (such as in cooking, driving, etc.), they only need to issue a specific voice command (such as "Hey"). The backup process can be initiated simply by saying "Siri, start backup," eliminating the need to touch the mobile device (such as a phone), achieving hands-free operation and significantly improving accessibility and ease of use. For manual button triggering within the app, i.e., scenarios where users need to immediately back up specific files, an explicit operation button is set in the application interface, providing an intuitive and controllable triggering method, effectively reducing the risk of accidental touches, and serving as a backup for other triggering conditions. For USB insertion detection triggering, based on real-time monitoring of storage device access signals by a microcontroller, when the user inserts the iRe5 storage case or external USB flash drive, the hardware layer instantly senses and triggers backup, offering advantages of low latency and high reliability, achieving hardware-level linkage for "plug and play backup." For external storage mounting event triggering, by listening to operating system file system events, backup is automatically started after the target storage device such as a TF card or SSD is detected as mounted, ensuring execution only when the storage device is ready, enhancing process stability. For power connection triggering, it is deeply bound to the mobile terminal's power status, automatically executing backup when charging is detected, avoiding interruptions due to insufficient power and improving backup task completion rate. For Wi-Fi environment change triggering, based on network... Environmental recognition technology triggers backup when a user enters a preset home or office Wi-Fi network, reducing the risk of accidental operation in unfamiliar scenarios through environmental security verification. For scheduled task triggering, users can customize the backup time (e.g., 22:00 daily), and combined with incremental backup strategies, it achieves fully automated execution without manual intervention. For geolocation triggering, it integrates location services and geofencing technology, automatically triggering backup when a user enters a preset trusted location (e.g., home, office), achieving scenario-based intelligent linkage. For Bluetooth detection triggering, it establishes a pairing connection with the iRe5 case or a matching Bluetooth device, using Bluetooth authentication as a physical binding method, and starts backup when successful pairing is detected, eliminating the possibility of accidental touches. For hardware physical button triggering, a dedicated backup button is set on hardware devices such as the iRe5 phone case, and the backup process is directly triggered when the user presses it, achieving minimal latency response through hardware-level signal transmission, which is especially suitable for emergency backup scenarios. For sensor triggering, it uses an accelerometer or gyroscope to monitor the device's stationary state. When the phone remains stationary for more than a preset time (e.g., 1 hour), it is determined to be an idle period and automatically triggers backup to reduce interference with user operations. The aforementioned triggering conditions, through multi-dimensional perception of user behavior and environmental status, take into account automation, intelligence, and reliability, forming a backup triggering system covering all scenarios.

[0025] In some embodiments, when a mobile terminal (taking an iPhone as an example) triggers operations such as data backup using an NFC tag, there is a risk of accidental touches. For example, a random NFC card, such as a public transport card, might accidentally launch an app and trigger an operation, affecting user experience and data security. To prevent accidental touches, when the mobile terminal detects an NFC tag proximity event, it can verify the legitimacy of the NFC tag proximity event trigger information and employ several security verification strategies to perform security verification on the triggering of the NFC tag proximity event. The security verification strategies include at least one of the following: domain name verification, NDEF content verification, UID whitelist verification, digital signature verification, password protection verification, two-factor authentication verification, dual-mode condition verification, or other security verification.

[0026] (1) Domain name verification: Use Universal Link (HTTPS domain name) and only respond to specific domain names.

[0027] When an NFC tag proximity event is detected, the terminal's built-in NFC reader / writer module reads the data from the NFC tag and parses it according to the NDEF (NFC Data Exchange Format) standard to obtain various information from the NDEF record, including but not limited to record type and payload data. During NFC tag creation, a specific HTTPS domain URL, such as "https: / / backup.ire5.com / now", is written into the NFC tag. This domain must be controlled by the developer to ensure its uniqueness and security. When the mobile terminal detects an NFC tag proximity event, it identifies the URL information in the NFC tag. The mobile terminal (e.g., iPhone) performs Apple App Site Association (AASA) verification. Only when the domain is successfully associated with the corresponding app installed on the iPhone will the app be launched. The AASA file must be placed in the root directory of the server corresponding to the domain and the path must be strictly configured to ensure that the iPhone can correctly read and verify it. Through the above AASA verification, if the domain is successfully associated with the app, the triggering information for this NFC tag proximity event is deemed legitimate, effectively preventing random NFC cards (such as transit cards) from mistakenly identifying it as capable of launching the app. Because ordinary random NFC cards typically do not write to a specific domain URL associated with this app, the accuracy and security of triggering information verification are improved.

[0028] Simultaneously, the mobile terminal can check whether the path parameters following the domain name match predefined rules, such as the path must contain the specific string " / now" and the parameter format must meet the requirements. If both the preset domain name and the path parameters match the predefined rules, the domain name verification is considered successful; otherwise, the domain name verification is considered unsuccessful. In other words, when NFC writes https: / / backup.ire5.com / now, the mobile terminal recognizes it and only activates the app when the domain name is associated with the app, preventing random NFC cards (such as public transport cards) from mistakenly identifying it as capable of activating the app, thus enhancing security.

[0029] (2) NDEF content verification: Verify the NDEF content structure (only respond to specific NDEF record types or records containing specific parameters).

[0030] The mobile terminal can also verify the NDEF content structure (responding only to specific NDEF record types or those containing specific parameters), setting a specific NDEF content format as a trigger condition. Processing will only occur when the NDEF record in the NFC tag contains content of a specific format. Specifically, when the mobile terminal detects an NFC tag proximity event, it reads the NDEF record in the NFC tag; identifies the NDEF record type and payload; and parses the payload data as a string or JSON to check if it contains preset content of a specific format. If it does, the trigger information for the NFC tag is deemed valid; otherwise, the NFC tag proximity event is ignored, and no further processing is performed. For example, the content can contain a specific URI format "ire5: / / backup?tag=xxx" or use a specific MIME type. Since ordinary public transport cards generally do not contain NDEF URLs, this effectively distinguishes between legitimate tags and ordinary cards.

[0031] (3) UID whitelist verification: Tag UID whitelist / device pairing.

[0032] Mobile terminals can also verify the legitimacy of NFC tag proximity event triggering information using a Tag UID whitelist / device pairing method. During the initial pairing or activation phase of the app, the mobile terminal's NFC read / write function reads the unique identifier (UID) of the target NFC tag, and can also read the tag's digital signature (if any). The read UID or digital signature is stored in the mobile terminal's local database, forming a whitelist. In subsequent use, when an NFC tag proximity event is detected, the UID or digital signature of the currently approaching tag is read and compared with the information registered in the local whitelist. Only when the comparison is successful, meaning the current tag's UID or digital signature exists in the whitelist, is the NFC tag proximity event triggering information considered legitimate, and subsequent data backup operations are then performed.

[0033] (4) Digital signature verification: Digital signature / NDEF Signature verification.

[0034] The NFC tag is pre-written with signed NDEF (NFC Forum Signature TLV) data. When the NFC tag is detected to be close to the user, the App in the mobile terminal reads the NDEF data and its signature from the tag and verifies the signature using the built-in public key. Only after the signature verification is successful will subsequent operations be performed, providing high security and effectively preventing the forgery and tampering of tag data. However, the signing operation needs to be performed at the tag writing end, which increases hardware costs and maintenance complexity. In addition, the degree of support for signature reading and writing by the mobile terminal needs to be evaluated.

[0035] (5) Password protection verification: Password protection / Tag key (NTAG password).

[0036] By setting the content of the NFC tag as a protected area and setting a preset password, the app can only access the data by requiring the user to enter the correct password. This effectively prevents unauthorized data writing or random operation by others, thus enhancing the security of the tag data.

[0037] (6) Secondary verification: Secondary verification (UI + biometric authentication) is required.

[0038] When the NFC tag wakes up the app, the app does not immediately perform any operation. Instead, it displays a pop-up window with operation prompts (such as "Start backup?") and requires the user to perform biometric authentication (such as fingerprint or facial recognition). Only after successful authentication will the app perform subsequent operations. This approach balances security and user experience, and it is relatively easy to increase operational security through simple biometric authentication.

[0039] (7) Dual-mode condition verification: Dual-mode trigger (NFC + another condition).

[0040] The operation is triggered by two conditions: an NFC event occurs and another preset trigger condition is met simultaneously (such as external storage being inserted, the phone being charged, or a specific Bluetooth device being connected). This strategy is more flexible than a whitelist and can almost eliminate the risk of accidental touches while retaining the automated operation experience. However, requiring both conditions to occur simultaneously in some scenarios may reduce the ease of operation.

[0041] Other security checks may include: (8) Tap count / long press judgment (throttling + anti-shake).

[0042] A specific trigger method is set, requiring the user to quickly bring the tag close to the terminal twice consecutively or keep it close to the terminal for a longer period of time (e.g., more than 0.5 seconds) before the operation is triggered. This method avoids accidental touches caused by passing a bus card or brief proximity. It requires no additional hardware support and is simple to implement, but may slightly reduce the immediacy of "stick and use".

[0043] (9) App state restriction response: Only responds when the App is in the foreground or in a specific App state.

[0044] Check the current state of the app. If the app is not authorized or running in the foreground, when the NFC tag wakes up the app, do not perform the operation directly. Instead, ask the user to open the app and confirm. Only after confirmation will the subsequent operation be performed. This can avoid accidentally triggering operations such as backup when the screen is locked or in the background, thus improving operation security, but sacrificing some seamless experience.

[0045] (10) Physical and label placement strategies.

[0046] Place the NFC tag in an easily identifiable and user-familiar location on the phone case (such as the lower center of the back cover), and clearly indicate in the product manual, "Do not place your transit card in this location." This method reduces accidental touches through user education and proper tag placement. It is low-cost and requires no complex software or hardware modifications, but relies on user cooperation.

[0047] If a security verification operation is performed according to one of the security verification strategies, the backup task can be triggered only if one of the verification results passes; if a security verification operation is performed according to two of the security verification strategies, the backup task can be triggered only if both verification results pass, and so on.

[0048] To balance user experience (UX), security, and cost, this application provides three different security verification strategy implementation schemes, which users can choose according to their actual needs.

[0049] Option A: Balance user experience and security (default recommended option).

[0050] Use Universal Link (requires a dedicated domain, such as https: / / yourapp.com / backup?token=xxx) to write NDEF data to the NFC tag, predefining the path / parameter format (e.g., fixed prefix + random token) to ensure that only authorized links can trigger the operation. When the mobile app detects an NFC tag proximity event, it first verifies the NDEF content; the NDEF data must contain the predefined path / parameters. Next, it checks if external storage (e.g., USB flash drive / external hard drive) is connected, or if the device is charging (determined via system API). If the conditions are not met, a prompt "Please connect storage device or charge and try again" is displayed. If the above conditions are met, a brief confirmation pop-up appears (e.g., "Backing up to XX device, confirm?"), and Face ID / Touch ID verification is triggered. If verification fails more than 3 times, the current operation is locked and a "Authentication failed" message is displayed.

[0051] Additionally, a preset cooldown time (e.g., 3 seconds) can be set to disable repeated triggering via a timer (e.g., disabling the NFC read button or ignoring repeated NDEF data). That is, if an NFC tag proximity event is detected again within the preset cooldown time, subsequent events are ignored to prevent repeated triggering of the backup task.

[0052] The above solution has almost zero accidental touches and provides a good user experience (requiring only one fingerprint / facial recognition confirmation), making it user-friendly for ordinary consumers and low in implementation costs.

[0053] Option B: High-security solution (enterprise / critical data scenarios).

[0054] Use tag digital signatures (NDEF Signature) or tag UID whitelist + password protection. Specifically, use asymmetric encryption (such as RSA) to sign the NDEF data, and the app verifies the signature validity (requiring embedded public key). For example, the tag data contains {data: "...", signature: "..."}, which the app decrypts and verifies using the public key; pre-register allowed NFC tag UIDs (Unique Identifiers), and the app compares them with the whitelist when reading the data; the tag contains an encrypted password (such as AES-256), which the user must enter in the app to unlock upon first use.

[0055] In addition, no secondary confirmation is required after NFC is activated (it can be done automatically) because strong identity verification has already been performed.

[0056] The above solution is suitable for enterprises or hosted equipment, requiring "instant backup and no accidental touches allowed".

[0057] Combination C: Extremely seamless (sacrificing some safety).

[0058] The NFC tag is only written to the Universal Link (e.g., https: / / yourapp.com / auto-backup), without the need for complex parameters; biometric identification or confirmation pop-ups are eliminated on the app side, for example, the app can show a fast progress prompt and a cancel button, and the backup is triggered directly after the app verifies the legality of the path.

[0059] Additionally, it displays non-blocking progress indicators (such as a banner at the top of the screen) and provides a "Cancel Now" button (which terminates the backup and deletes temporary files when clicked).

[0060] The above solution aims for ultimate convenience with one-tap backup, but the probability of accidental activation exists, making it suitable for scenarios where risks are controllable.

[0061] To facilitate understanding of the inventive concept of this application, pseudocode for a security verification strategy is provided below (taking the recommended combination A above as an example): NFC_Event_Handler(nfcData): # 1. Parsing NDEF if not is_valid_ndef(nfcData): ignore_event() return # 2. Validate URL domain name or predefined parameters if not domain_matches(nfcData.url, "backup.ire5.com"): ignore_event() return # 3. Check additional trigger conditions (external storage / paired tag / Bluetooth / charging) if not (is_storage_mounted() or is_bluetooth_paired("iRe5") or is_charging()): # Allow users to continue, but reduce accidental touches: Display "Backup tag detected. Insert storage or connect via Bluetooth for one-click backup." show_hint() return # 4. Anti-shake logic if recent_nfc_trigger_within(3_seconds): ignore_event() return #5. Pop-up confirmation + biometric authentication show_confirmation("Start backup to iRe5?") if user_confirms(): if biometrics_auth_succeeds(): start_backup_task() else: show_message("Authentication failed") else: cancel() Recommended solution combination A reads the NDEF data of NFC tags by integrating the CoreNFC framework and uses Associated Domains to configure Universal Link to ensure that the URL written to NFC strictly matches the APP's associated domain (AASA), thereby triggering an application pop-up prompt when the iOS screen is locked or in the background. At the same time, it uses the LAContext class of the LocalAuthentication framework to implement FaceID / TouchID biometric authentication to enhance operational security. Finally, it uses the bookmark mechanism of UIDocumentPicker or FileProvider / FileManager to detect the mount path of external storage devices, completing the fully automated control of the entire process from NFC triggering to security verification to data backup.

[0062] The protection mechanism is achieved by using one or more of the above security verification strategies to avoid accidental triggering by other common NFC cards (such as bus cards, access cards, etc.). Users can select or combine different trigger conditions according to the scenario, thereby realizing a more flexible backup startup mechanism to achieve the best balance between "user experience" and "accidental touch tolerance".

[0063] S12, when a backup task trigger instruction is received, the data to be backed up is written to the external storage device according to the intelligent backup strategy.

[0064] The external storage device (TF card, microSD, SSD, or USB flash drive) is successfully connected to the mobile terminal. The mobile terminal can perform backup tasks based on any intelligent backup strategy to address the insufficient storage problem. The intelligent backup strategy includes at least one of incremental backup, conditional filtering, intelligent scheduling, or adaptive learning strategies. NFC is used only as a trigger signal to wake up or activate the backup application, and does not directly carry backup data. After successful security verification, a backup task trigger command is generated. When the mobile terminal receives the backup task trigger command, it transmits the data to be backed up (e.g., photos, videos, documents) through a local controlled interface (such as USB-C, Lightning, or an already connected external storage device) according to the intelligent backup strategy. It also verifies the connection status of the external storage device using the operating system's authorization mechanism (such as UIDocumentPicker or FileProvider), ensuring that the data to be backed up is only written to the storage device successfully connected to the mobile terminal via a physical interface, thereby mitigating the security risks of wireless transmission and improving system compatibility and stability.

[0065] Specifically, after receiving the backup task trigger instruction, the mobile terminal obtains the set of data to be backed up through standardized interfaces provided by the operating system (such as iOS's PHPhotoLibrary framework or Android's MediaStore API), and executes any of the following intelligent backup strategies to perform the backup task: (1) Incremental backup strategy.

[0066] The mobile terminal reads the metadata of backed-up files from the target external storage device (TF card, SSD, or USB flash drive connected via USB-C / Lightning interface) and compares it with the data to be backed up. Specifically, it can perform verification through timestamps (i.e., only copying files whose modification time is later than that of the corresponding file on the external storage device), hash value verification (i.e., calculating the hash value of the file to be backed up (such as SHA-256) and comparing it with the hash value of the corresponding file on the external storage device, copying only when the hash values ​​do not match), and system index verification (i.e., using iOS's PHAsset.localIdentifier or Android's MediaStore._ID as a unique identifier, copying only files on the external storage device that are not indexed), only copying newly added or modified files to avoid duplicate writing and improve efficiency.

[0067] (2) Conditional filtering strategy.

[0068] The mobile terminal filters the data to be backed up according to the user's preset filtering rules, which include, but are not limited to, time range filtering, file type filtering, and file size filtering.

[0069] Among them, the time range filter only backs up files whose shooting time or modification time is within the last 7 days (determined by the PHAsset.creationDate or MediaStore.DATE_MODIFIED fields); the file type filter only backs up video files (by matching the file MIME type or extension, such as ".mp4" or ".mov"); and the file size filter excludes files larger than 1GB (determined by the PHAsset.fileSize or MediaStore.SIZE fields).

[0070] (3) Intelligent scheduling strategy.

[0071] Before performing a backup, the mobile terminal dynamically detects the following environmental parameters and decides whether to perform the backup immediately: Battery status: Obtain the current battery level through UIDevice. If the battery level is ≤50%, the backup will be delayed until the battery level is restored to above 50% or the battery is connected to a power source. Storage space remaining: The remaining available space of the external storage device is obtained through FileManager. If the remaining space is less than 20% of the total size of the files to be backed up, the backup will be paused and a storage shortage warning will be pushed. Network environment (optional): If the backup task involves cloud synchronization (such as synchronizing to a PC via Wi-Fi LAN), check whether the current network is a home Wi-Fi or a trusted enterprise network (verify geographical location or SSID matching via CoreLocation) to avoid execution on a public network.

[0072] (4) Adaptive learning strategy.

[0073] After each backup is completed, the mobile device records user operation habits (such as backup time period and file type preferences) so that it can provide backup prompts or perform automatic backups based on these habits. For example, it can analyze the time distribution of backups performed by users over the past 30 days, identify high-frequency backup time periods (such as 8:00 PM to 10:00 PM on weekends), and prioritize pushing backup prompts during these time periods in subsequent backups; or it can analyze the proportion of videos, photos, and documents in the user's backup files, and if videos account for more than 70%, it can automatically optimize the copying priority of video files in the next backup.

[0074] Upon receiving a backup trigger command that has been verified by security, the system writes the data to be backed up to the connected external storage device through the local interface according to the intelligent backup strategy. This avoids wireless risks, improves compatibility and stability, and the strategy includes incremental, filtering, scheduling and adaptive learning, which can avoid duplicate backups, back up on demand, make dynamic decisions and optimize according to habits, efficiently solve the problem of insufficient storage while meeting the personalized backup needs in complex scenarios.

[0075] In an optional implementation, the mobile terminal data intelligent backup method further includes: When the first installation command of the backup application is detected, an NFC tag registration function is provided so that the user can bring the NFC tag to be associated close to the mobile terminal to trigger the tag information reading operation; When it is determined that the NFC tag to be associated has completed the binding registration with the backup application, the tag information of the NFC tag is securely stored in the local database so that when an NFC tag proximity event is received, a security verification operation is performed based on the tag information.

[0076] In some embodiments, the user searches for the backup application in the mobile terminal's app store, clicks to download and install it. When the installer detects the backup application's first installation instruction, it enters the initialization phase of the NFC tag registration process. At this time, the application pops up a prompt window on the screen, prompting the user to perform an NFC tag registration operation, informing the user that the purpose of this operation is to bind the NFC tag to the backup application so that subsequent security verification and backup operations can be triggered via the NFC tag. The user follows the prompts and brings the NFC tag to be associated close to the NFC sensing area of ​​the smartphone (usually located on the upper back of the phone). When the NFC tag enters the sensing range, the phone automatically triggers a tag information reading operation. The tag information may include the tag UID, signature information, etc. The backup application reads the tag UID or signature information from the NFC tag through the phone's NFC module. This information is the unique identifier of the NFC tag and is used for subsequent security verification. For example, the read tag UID may be a specific code consisting of numbers and letters, such as "1234-5678-90AB-CDEF". After reading the tag information, the backup application binds and registers the NFC tag with itself. Specifically, the application creates a new record in its local database, associating the read tag UID or signature information with relevant application information (such as application ID, installation time, etc.). Simultaneously, a successful binding notification is displayed on the application's user interface, informing the user that the NFC tag has been successfully bound to the backup application. Next, the backup application securely stores the read NFC tag UID or signature information in its local database. The local database uses encrypted storage to ensure the security of the tag information. For example, it uses the AES (Advanced Encryption Standard) algorithm to encrypt the tag information before storage, preventing unauthorized access and tampering. During storage, the database assigns a unique identifier to each tag information record for easy subsequent querying and management.

[0077] When the user brings the bound NFC tag close to the mobile terminal again, the mobile terminal's NFC module detects the NFC tag proximity event and notifies the backup application. Upon receiving the NFC tag proximity event, the backup application reads the tag UID or signature information corresponding to the NFC tag from its local database. Then, it compares the read information with the currently detected NFC tag information. If they match, the NFC tag is considered legitimate, and subsequent backup operations are allowed; if they do not match, the backup operation is rejected, and a security verification failure message is displayed on the screen. If the security verification passes, the backup application backs up the data on the mobile terminal according to the user's preset smart backup strategy. For example, it backs up and stores contact information, SMS messages, photos, and other data according to a specified format and path, while recording the backup time, data type, and other information.

[0078] With the above optional implementation methods, users can easily bind and register the NFC tag with the application when installing the backup application for the first time. In subsequent use, users only need to bring the bound NFC tag close to the mobile phone to quickly trigger the security verification and backup operation, which improves the convenience and security of data backup and prevents accidental contact with other NFC tags (bus cards, access control).

[0079] In an optional implementation, the mobile terminal data intelligent backup method further includes: When an NFC tag proximity event is detected, the user is authenticated using Face ID or Touch ID; Once identity verification is confirmed and the current mobile terminal is not on the enterprise whitelist or signature verification fails, the backup task will be executed after waiting for further user action. Once identity verification is successful and the current mobile terminal is on the enterprise whitelist or has passed signature verification, the automatic execution mode is enabled to directly execute the backup task.

[0080] In some embodiments, Universal Link (HTTPS) is preferred when writing tags, and the path is precisely configured in AASA to reduce unexpected wake-ups. Alternatively, the default UX flow is "Wake-up → Quick Confirmation (Face ID / Touch ID → Execution)," with "Auto-Execution" mode enabled only when the enterprise whitelist or signature verification is successful. The enterprise whitelist is pre-set on the mobile terminal and contains relevant information about enterprises that allow automatic execution mode for data backup, and includes a signature verification mechanism to verify the legitimacy of the mobile terminal or related backup operations.

[0081] Specifically, the mobile terminal's NFC module is constantly monitoring for nearby NFC tags. When a user brings an NFC tag with a specific identifier close to the mobile terminal, the NFC module quickly detects the proximity event and transmits this information to the mobile terminal's backup application. The backup application, based on a preset verification method, prioritizes attempting facial recognition verification via Face ID. If Face ID verification fails for some reason (such as insufficient ambient light or user face obstruction), the system automatically switches to Touch ID for fingerprint verification. Only when Face ID or Touch ID verification is successful is the user's identity considered legitimate, and subsequent operations continue; if verification fails, the user is prompted that authentication has failed, and the backup process terminates. After successful user authentication, the mobile terminal simultaneously performs two key checks: Enterprise whitelist determination: The system queries the internally stored enterprise whitelist information and compares the relevant identifiers of the current mobile terminal (such as device serial number, user account's enterprise information, etc.) with the information in the enterprise whitelist. If the relevant identifiers of the current mobile terminal exist in the enterprise whitelist, the mobile terminal is determined to meet the enterprise whitelist criteria.

[0082] Signature verification: This function verifies the signature of the current mobile terminal or related backup operation. It uses a specific encryption algorithm and verification mechanism to check the validity of the signature. If the signature verification passes, it indicates that the mobile terminal or backup operation is legitimate.

[0083] When user authentication is successful, but the mobile device is not on the enterprise whitelist or signature verification fails, the mobile device will not immediately execute the backup task. At this time, relevant prompts will be displayed on the screen, informing the user that further action is required, such as manually confirming the backup content or selecting a backup storage location. Only after the user completes the corresponding actions will the system execute the data backup task. When user authentication is successful and the mobile device is on the enterprise whitelist or signature verification is successful, the mobile device automatically activates the automatic execution mode. Following the preset intelligent backup strategy, the data backup task will begin directly without user intervention, backing up specified data (such as contacts, photos, documents, etc.) from the mobile device to an external storage device.

[0084] It should be noted that during the testing phase, the accidental touch rate was repeatedly tested in scenarios such as subway cards, stacked multiple NFC cards, short-term wiping of tags, different mobile phone models, and locked screen states. Thresholds such as Tap length, double-tap requirements, and cooling time were also adjusted.

[0085] In an optional implementation, the mobile terminal data intelligent backup method further includes: Visualize the backup progress of the backup data while the backup task is in execution state; When the backup task is in a completed state, the system will visualize whether the backup was successful or failed.

[0086] In some embodiments, the mobile terminal provides users with fully visible interactive feedback. During the backup task execution process according to any of the aforementioned intelligent backup strategies, i.e., while the backup task is in execution, the backup progress of the data is visualized. For example, a progress bar or percentage can dynamically display the number of completed files and the remaining time.

[0087] When the backup task is completed, i.e., when the backup task is in a completed state, regardless of whether the backup was successful or failed, log information is automatically generated, including a timestamp, number of files, success / failure status, and error reason (such as insufficient storage, permission denied, connection interruption), and recorded to a log file (JSON / CSV format) via the local storage module. Simultaneously, the log information is encapsulated into standardized data packets and pushed to the bound iOS / Android / PC applications via cloud synchronization service, supporting real-time viewing, exporting, and historical record tracing across multiple devices. Furthermore, users can modify backup policy parameters (such as trigger condition thresholds, backup range rules) or device whitelist configurations on any terminal. The modified configuration information is uploaded to the cloud server via an encrypted channel and broadcast to other associated terminals in real time, ensuring consistency between multi-terminal backup logic and access control.

[0088] Through the above optional implementation methods, the backup task progress is visualized during execution, and a log with detailed information is generated and pushed to multiple devices upon completion. This supports real-time viewing and tracing on multiple devices and also allows users to modify backup parameters, ensuring that the backup logic and access control are consistent across multiple devices.

[0089] It's important to note that the same logic is executed across iOS, Android, and PC platforms to ensure consistency and traceability of backup results across multiple devices. For example, the backup application for mobile devices has three versions: iOS, Android, and PC. The iOS version uses PHPhotoLibrary to acquire photos and videos via NFC tags, USB insertion, or Siri Shortcut triggers, then writes them to external storage devices via UIDocumentPicker, providing progress bars, completion and error messages, and saving historical data. The Android version uses the MediaStore API to acquire data via NFC, USB OTG insertion, or scheduled tasks, writing it to external storage devices, with a user interface consistent with iOS. The PC version provides unified management of mobile backup files, scanning memory cards, categorizing and displaying files, generating backup reports, supporting USB-C direct connection or Wi-Fi LAN synchronization, and exporting to a NAS or cloud platform.

[0090] This application uses NFC only as the trigger logic and writes to external storage through a local interface. This not only avoids the risks of wireless transmission, but also achieves high flexibility and efficiency with multiple trigger conditions and intelligent backup strategies. Furthermore, cross-platform (iOS, Android, PC) support brings a consistent user experience.

[0091] Reference Figure 2 The diagram shown is a functional block diagram of a mobile terminal data intelligent backup device according to an embodiment of this application.

[0092] In some embodiments, the mobile terminal data intelligent backup device 20 may include multiple functional modules composed of computer program segments. The computer programs of each program segment of the mobile terminal data intelligent backup device 20 may be stored in the memory of the mobile terminal and executed by at least one processor to perform (see details). Figure 1 (Description) The function of mobile terminal data backup. Based on its function, it can be divided into multiple functional modules. These functional modules may include: a trigger module 201, a backup module 202, a registration module 203, and a visualization module 204. The module referred to in this application is a series of computer program segments that can be executed by at least one processor and perform a fixed function, stored in memory. In this embodiment, the functions of each module will be detailed in subsequent embodiments.

[0093] The trigger module 201 is used to perform a security verification operation when a preset trigger condition is detected to determine whether the backup task will be triggered when the verification is successful. The preset trigger condition includes an NFC tag proximity event and / or at least one additional trigger condition. The NFC tag serves as a trigger signal and is only used to wake up the backup application on the mobile terminal.

[0094] The backup module 202 is used to write the data to be backed up to an external storage device according to the intelligent backup strategy when a backup task trigger instruction is received. The external storage device has been successfully connected to the mobile terminal.

[0095] The registration module 203 is used to provide an NFC tag registration function when the backup application's first installation instruction is detected, so that the user can bring the NFC tag to be associated close to the mobile terminal to trigger a tag information reading operation; when it is determined that the NFC tag to be associated has completed the binding registration with the backup application, the tag information of the NFC tag is securely stored in the local database so that a security verification operation can be performed based on the tag information when an NFC tag proximity event is received.

[0096] The backup module 202 is further configured to: authenticate the user based on Face ID or Touch ID when an NFC tag proximity event is detected; if the authentication is successful and the current mobile terminal is not on the enterprise whitelist or the signature verification fails, then wait for further user operation before executing the backup task; if the authentication is successful and the current mobile terminal is on the enterprise whitelist or the signature verification passes, then enable the automatic execution mode and directly execute the backup task.

[0097] The visualization module 204 is used to: visualize the backup progress of the backup data when the backup task is in the execution state; and visualize the backup success status or backup failure status when the backup task is in the completion state.

[0098] It should be understood that the various variations and specific embodiments of the mobile terminal data intelligent backup method provided in the above embodiments are also applicable to the mobile terminal data intelligent backup device of this embodiment. Through the foregoing detailed description of the mobile terminal data intelligent backup method, those skilled in the art can clearly understand the implementation method of the mobile terminal data intelligent backup device in this embodiment. For the sake of brevity, it will not be described in detail here.

[0099] See Figure 3 The diagram shown is a schematic representation of the structure of a mobile terminal according to an embodiment of this application. In a preferred embodiment of this application, the mobile terminal 3 includes a memory 31, at least one processor 32, and at least one communication bus 33.

[0100] Those skilled in the art should understand that Figure 3 The structure of the mobile terminal shown does not constitute a limitation of the embodiments of this application. It can be a bus structure or a star structure. The mobile terminal 3 may also include more or fewer other hardware or software than shown, or different component arrangements.

[0101] In some embodiments, the mobile terminal 3 is a device capable of automatically performing numerical calculations and / or information processing according to pre-set or stored instructions. Its hardware includes, but is not limited to, microprocessors, application-specific integrated circuits (ASICs), programmable gate arrays (FPGAs), digital processors, and embedded devices. The mobile terminal 3 may also include user equipment, which includes, but is not limited to, any electronic product capable of human-computer interaction with a user via a keyboard, mouse, remote control, touchpad, or voice control device, such as a personal computer, tablet computer, smartphone, or digital camera.

[0102] In the embodiments provided in this application, it should be understood that the disclosed methods, apparatus, computer-readable storage media, and mobile terminals can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative. For instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple components or modules may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual couplings or direct couplings or communication connections may be indirect couplings or communication connections between devices, components, or modules through some interfaces, and may be electrical, mechanical, or other forms.

[0103] The components described as separate parts may or may not be physically separate. The components shown as components may or may not be physical modules; that is, they may be located in one place or distributed across multiple network modules. Some or all of the components can be selected to achieve the purpose of this embodiment according to actual needs.

[0104] Furthermore, the functional modules in the various embodiments of the present invention can be integrated into one processing module, or each component can exist physically separately, or two or more modules can be integrated into one module. The integrated modules described above can be implemented in hardware or as software functional modules.

[0105] If the integrated module is implemented as a software functional module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the mobile terminal data intelligent backup method described in the various embodiments of the present invention. The aforementioned storage medium includes: USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, optical disks, and other media capable of storing program code.

[0106] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that the present invention is not limited to the described order of actions, because according to the present invention, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to the present invention.

[0107] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0108] The above is a detailed description of the preferred embodiments of the present invention. However, the present invention is not limited to the embodiments described. Those skilled in the art can make various equivalent modifications or substitutions without departing from the spirit of the present invention. All such equivalent modifications or substitutions are included within the scope defined by the claims of this application.

Claims

1. A method for intelligent backup of mobile terminal data, characterized in that, The intelligent backup method for mobile terminal data includes: When a preset trigger condition is detected, a security verification operation is performed to determine if the verification passes and trigger the backup task execution. The preset trigger condition includes an NFC tag proximity event and / or at least one additional trigger condition. The NFC tag serves as a trigger signal and is only used to wake up the backup application on the mobile terminal. When a backup task trigger instruction is received, the data to be backed up is written to an external storage device according to the intelligent backup strategy, and the external storage device has been successfully connected to the mobile terminal.

2. The intelligent backup method for mobile terminal data according to claim 1, characterized in that, The system detects whether at least one additional triggering condition exists, which is selected from any one or a combination of the following: voice command input event, USB / external storage device insertion or mounting event, power access status change event, Wi-Fi network switching event, timed task triggering event, geofencing triggering event, Bluetooth device connection status change event, and sensor data anomaly event.

3. The intelligent backup method for mobile terminal data according to claim 1, characterized in that, The security verification operations include at least one of the following: domain name verification, NDEF content verification, UID whitelist verification, digital signature verification, password protection verification, two-factor authentication verification, dual-mode condition verification, or other security verification.

4. The intelligent backup method for mobile terminal data according to claim 1, characterized in that, The intelligent backup strategy includes at least one of the following: incremental backup strategy, conditional filtering strategy, intelligent scheduling strategy, or adaptive learning strategy.

5. The intelligent backup method for mobile terminal data according to any one of claims 1 to 4, characterized in that, The intelligent backup method for mobile terminal data also includes: When the first installation command of the backup application is detected, an NFC tag registration function is provided so that the user can bring the NFC tag to be associated close to the mobile terminal to trigger the tag information reading operation; When it is determined that the NFC tag to be associated has completed the binding registration with the backup application, the tag information of the NFC tag is securely stored in the local database so that when an NFC tag proximity event is received, a security verification operation is performed based on the tag information.

6. The intelligent backup method for mobile terminal data according to any one of claims 1 to 4, characterized in that, The intelligent backup method for mobile terminal data also includes: When an NFC tag proximity event is detected, the user is authenticated using Face ID or Touch ID; Once identity verification is confirmed and the current mobile terminal is not on the enterprise whitelist or signature verification fails, the backup task will be executed after waiting for further user action. Once identity verification is successful and the current mobile terminal is on the enterprise whitelist or has passed signature verification, the automatic execution mode is enabled to directly execute the backup task.

7. The intelligent backup method for mobile terminal data according to any one of claims 1 to 4, characterized in that, The intelligent backup method for mobile terminal data also includes: Visualize the backup progress of the backup data while the backup task is in execution state; When the backup task is in a completed state, the system will visualize whether the backup was successful or failed.

8. A mobile terminal data intelligent backup device, characterized in that, The mobile terminal data intelligent backup device includes: The trigger module is used to perform a security verification operation when a preset trigger condition is detected to determine whether the backup task will be executed when the verification is successful; the preset trigger condition includes an NFC tag proximity event and / or at least one additional trigger condition; the NFC tag serves as a trigger signal and is only used to wake up the backup application on the mobile terminal; The backup module is used to write the data to be backed up to an external storage device according to the intelligent backup strategy when a backup task trigger instruction is received. The external storage device has been successfully connected to the mobile terminal.

9. A mobile terminal, characterized in that, The method includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the mobile terminal data intelligent backup method according to any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps of the mobile terminal data intelligent backup method according to any one of claims 1 to 7.

Images